Cisco Systems Network Router manual Selecting the Pnni Peer Group ID, Default Peer Group ID

Page 60

Chapter 3 Address and Closed User Group Planning

Planning Address Configuration Settings

Selecting the PNNI Peer Group ID

As described in the previous section, the PNNI level selects the number of ATM address bits that are unique within the peer group ID. After you select a PNNI level for a peer group, you need to define the peer group ID using the PNNI level, the number of address bits defined by the PNNI level, and trailing zeros. Figure 3-5shows the format of the default peer group ID for the Cisco MGX and SES switch products.

Figure 3-5 Default Peer Group ID

56: 47.00.9181.0000.0000.0000.0000.00

Default peer

Cisco

group level

ICD

 

 

Default ATM

address format

89685

As Figure 3-5shows, the peer group ID begins with the PNNI level, followed by a colon. The unique portion of the peer group ID follows next. The unique portion of the ID, which is the first 7 bytes by default, corresponds with the left-most or most-significant bytes of the ATM address. The Cisco default PNNI level is 56, so the first 7 bytes of the default ATM address make up the unique portion of the peer group ID: 47.009181000000.

The total length of a peer group ID is 14 bytes, so the bytes that follow the unique portion of the peer group ID are all set to 0. Therefore, the complete default peer group ID for all Cisco MGX and SES switch products is: 56:47.00.9181.0000.0000.0000.0000.00. The periods within the peer group ID are used to make it easier to read the peer group ID. To create a second peer group at the same default level, you must modify the unique portion of the peer group ID. For example: 56:47.00.9181.0000.01.

Note Only the unique portion of the peer group ID, which is defined by the PNNI level, is used to identify the peer group. In the example of the default level 56, the first 7 bytes of the ATM address define the peer group ID. Although up to 13 bytes can be used for the peer group ID, all bytes beyond what is specified by the PNNI level are ignored with respect to the peer group ID. Although the nonunique bits in the first 13 bytes appear as zeros in the peer group ID display, they do not have to be set to 0 for ATM addresses.

The peer group ID is used to identify ATM addresses that are part of the same PNNI peer group. For example, the following PNNI addresses are all in the same default PNNI peer group:

47.009181000000112233445566.778899101112.01

47.009181000000112233445566.778899101113.01

47.009181000000112233445566.778899101114.01

47.009181000000778899101112.112233445566.01

The above addresses are all in the same peer group because the PNNI level for all addresses is the default level (56 bits or 7 bytes) and the first 7 bytes of all these addresses are the same.

When planning peer group IDs for your WAN, consider the following:

All peer group IDs within a peer group must be identical.

Each peer group must have its own ID that is unique within the WAN.

 

Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5

3-10

Part Number OL-3847-01 Rev. D0, April, 2004

Image 60
Contents Corporate Headquarters Text Part Number OL-3847-01 Rev. D0Copyright 2003, Cisco Systems, Inc All rights reserved N T E N T S IiiCompatible Standards Worksheets Part Number OL-3847-01 Rev. D0, April G U R E S ViiViii B L E S Part Number OL-3847-01 Rev. D0, April Objectives AudienceOrganization Conventions XiiDocumentation Documentation Notes for the April 2004 Product ReleasesRelated Documentation XiiiTechnical Manual Order of Use XivTechnical Manual Titles and Descriptions TermsXvi Xvii Xviii Xix Reference Guides Xxi Document Title Description XxiiXxiii Xxiv Xxv Xxvi Obtaining Documentation Cisco.comOrdering Documentation XxviiChanges to This Document Chapter ChangesXxviii Obtaining Technical Assistance Documentation FeedbackCisco TAC Website Opening a TAC CaseObtaining Additional Publications and Information TAC Case Priority DefinitionsXxx Xxxi Xxxii Introduction to Pnni Pnni Network DatabaseSingle Peer Group Topology Hierarchical Pnni Network Topology Example Single Peer Group TopologyPeer group Ppeer Peer Group Leaders Simple Node RepresentationComplex Node Representation Simple Node RepresentationPnni Internetworking with Aini Border NodesHierarchical Pnni Network Benefits Pnni Internetworking with Iisp Example Pnni Internetworking with Aini TopologyPart Number OL-3847-01 Rev. D0, April Specifications Compatible StandardsPXM45 CapabilitiesPXM1E PXM45/BCapabilities SES SESConnection Limit Adjustments Connection Type Switch Connections CWM EndpointsSVC DAX SpvcInstall Redundant Hardware in Switches Parallel Links Between Adjacent SwitchesPhysical Network Planning Planning Guidelines for Individual Peer Groups Multiple Links Between Adjacent Peer GroupsMultiple Links to an External Network Multiple Paths Between Network NodesPlanning Guidelines for Hierarchical Networks Planning Guidelines for Peer Group LeadersPlanning Guidelines for Border Nodes Part Number OL-3847-01 Rev. D0, April Address and Closed User Group Planning Address Planning OverviewPnni Addressing Example Planning Address Configuration Settings Selecting an ATM Address FormatSupported Address Formats ESI SEL IDP DSPATM Field Description Default Values Guidelines for Selecting an Address FormatSelecting a Pnni Level Address Registration AuthoritiesCategory Type Authorities DCC4shows an example topology of a Pnni MPG WAN Part Number OL-3847-01 Rev. D0, April Length Level Peer Group ID Portion of ATM Address BytesDefault Peer Group ID Selecting the Pnni Peer Group IDSelecting the ATM Address 20-byte Node AddressSelecting the Ilmi Address Prefix Selecting the Spvc Address PrefixPlanning Address Prefixes for Aini and Iisp Links Selecting Static Addresses for UNI Ports Additional Guidelines for Creating an Address PlanClosed User Group Overview Closed User Group ExamplePlanning CUG Configuration Settings Selecting an Interlock CodeSelecting an Index Selecting Internal CUG Access Options Selecting CPE AddressesSelecting External CUG Access Options Specifying a Preferential CUGSelecting a Default CUG Address WorksheetsCUG Part Number OL-3847-01 Rev. D0, April Administrative Weight How MGX and SES Nodes Select RoutesLink and Route Metrics Cell Transfer Delay Cell Delay VariationAvailable Cell Rate Shortest Path Table Routing Maximum Cell RateShortest Path Tables Class of Service Tables Service Class Acronym Definition GuidelinesCTD CDV Traffic MetricHow SVCs and SVPs use the SPTs How SPVCs and SPVPs use the SPTsHow MGX and SES Nodes Select Links On-Demand RoutingLoad Balancing for SPT and On-Demand Routing Additional Routing Features in MGX and SES Nodes ServicePreferred Routing CLR0+12Priority Routing GroomingSoft Rerouting Priority BumpingBlocking Pass-Through Connections Nodal Point-to-Multipoint Branch RestrictionAXSM/A AXSM/BAXSM-E AXSM-XGFarthest Node Branching Part Number OL-3847-01 Rev. D0, April ABR AesaAini Ansi APSP2MP CBRCTD IN-2CUG CWMDIN IN-3IN-4 PGL PnniMGX SES IN-5IN-6 UBR UNITAC IN-7IN-8