Cisco Systems Network Router manual Pnni Internetworking with Aini, Border Nodes

Page 40

Chapter 1 Introduction to PNNI

PNNI Internetworking with AINI

The advantage to complex node representation is that it provides more information to other peer groups, and this can lead to better route selection. The disadvantage of complex node representation is that it adds to the size of the database in remote peer groups. Complex node representation also requires more processing resources on the LGN that represents a peer group as a complex node.

Border Nodes

Border nodes are nodes that participate in a PNNI peer group and maintain links to other peer groups. A border node is a member of only one peer group. Links to other nodes within a peer group are called inside links, and links to nodes in other peer groups are called outside links. A border node is any node that is configured for outside links.

PNNI automatically determines whether or not a node is a border node by examining the PNNI peer group ID at each end of a PNNI link. (The PNNI peer group ID is described in the “Selecting the PNNI Peer Group ID” section of Chapter 3, “Address and Closed User Group Planning.”) If the peer group IDs are different, both nodes are border nodes for their respective peer groups.

When planning for border nodes, you might want to avoid routing internal peer group traffic through border nodes so that border nodes have more processing resources for supporting traffic traveling in and out of the peer group.

Hierarchical PNNI Network Benefits

The primary benefit of a hierarchical PNNI network is scalability. Single peer group networks are limited to 160 nodes, but hierarchical networks can support many more nodes.

For networks with less than 100 nodes, a single peer group will usually provide superior performance over a hierarchical network because an originating node is aware of all routes and can choose the best route. In hierarchical networks, the higher level processes that route calls between peer groups are aware of the peer group structure, but they are not aware of the routes available within the peer groups.

Hierarchical networks will always adhere to call requirements, but they may not always route calls over the most optimum route.

PNNI Internetworking with AINI

ATM Inter-Network Interface (AINI) is an industry standard protocol for enabling static routing between separate PNNI networks. AINI only advertises ATM addresses and address groups that are manually configured on AINI links, so the manual configuration makes AINI links more expensive to configure than PNNI links. AINI provides network security and independence by blocking all PNNI advertisements across AINI links. AINI is typically used to enable select communications between two independent networks. For example, AINI links might be used to interconnect two different companies or between a company and a service provider. Figure 1-6shows an example of PNNI networking with AINI.

Note AINI networking is not supported on Cisco MGX 8850 switches before Release 2.1.60 and is not supported on the SES PNNI Controller before Release 1.1.60.

 

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

1-8

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

Page 39 Page 41
Image 40
Page 39 Page 41
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 Audience ObjectivesOrganization 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 XxviiChapter Changes Changes to This DocumentXxviii Obtaining Technical Assistance Documentation FeedbackCisco TAC Website Opening a TAC CaseTAC Case Priority Definitions Obtaining Additional Publications and InformationXxx 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 RepresentationBorder Nodes Pnni Internetworking with AiniHierarchical 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 SpvcParallel Links Between Adjacent Switches Install Redundant Hardware in 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 Peer Group Leaders Planning Guidelines for Hierarchical NetworksPlanning 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 Spvc Address Prefix Selecting the Ilmi 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 ExampleSelecting an Interlock Code Planning CUG Configuration SettingsSelecting 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 How MGX and SES Nodes Select Routes Administrative WeightLink and Route Metrics Cell Delay Variation Cell Transfer DelayAvailable Cell Rate Maximum Cell Rate Shortest Path Table RoutingShortest 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 SPTsOn-Demand Routing How MGX and SES Nodes Select LinksLoad 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
Top Page Image Contents