Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 Release 5 April 14, 2004 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Text Part Number: OL-3847-01 Rev.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS About This Guide Objectives Audience xi xi xi Organization xi Conventions xii Documentation xiii Documentation Notes for the April 2004 Product Releases xiii Related Documentation xiii Technical Manual Order of Use xiv Technical Manual Titles and Descriptions xv Obtaining Documentation xxvii Cisco.
Contents CHA PTER 2 Interoperability and Performance Planning Compatible Standards Specifications 2-1 2-1 2-1 Connection Limit Adjustments 2-4 Physical Network Planning 2-5 Install Redundant Hardware in Switches 2-5 Parallel Links Between Adjacent Switches 2-5 Multiple Links Between Adjacent Peer Groups 2-6 Multiple Links to an External Network 2-6 Multiple Paths Between Network Nodes 2-6 Planning Guidelines for Individual Peer Groups 2-6 Planning Guidelines for Hierarchical Networks 2-7 Planning
Contents Planning CUG Configuration Settings 3-15 Selecting an Interlock Code 3-15 Selecting an Index 3-15 Selecting CPE Addresses 3-16 Selecting Internal CUG Access Options 3-16 Selecting External CUG Access Options 3-17 Specifying a Preferential CUG 3-17 Selecting a Default CUG Address 3-18 Worksheets CHA PTER 4 3-18 Planning Intermediate Route Selection 4-1 How MGX and SES Nodes Select Routes 4-1 Link and Route Metrics 4-1 Administrative Weight 4-1 Cell Transfer Delay 4-2 Cell Delay Variation 4-2
Contents Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 vi Part Number OL-3847-01 Rev.
F I G U R E S Figure 1-1 Example Single Peer Group Topology Figure 1-2 Example Hierarchical PNNI Network Topology Showing Multiple Peer Groups Figure 1-3 Example Hierarchical PNNI Network Topology Showing a Two-Level Hierarchy Figure 1-4 Simple Node Representation Figure 1-5 Complex Node Representation Figure 1-6 Example PNNI Internetworking with AINI Topology Figure 3-1 PNNI Addressing Example Figure 3-2 Supported ATM Address Formats 3-4 Figure 3-3 PNNI Network Physical Topology 3-7 Fi
Figures Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 viii Part Number OL-3847-01 Rev.
T A B L E S Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) xvi Table 2 Documents that Ship with Multiservice Switch Products Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products Table 4 Changes to This Book Since the Previous Release Table 2-1 PNNI Networking Specifications for MGX Switches and the MGX 8880 Media Gateway Table 2-2 PNNI Networking Specifications for SES Equip
Tables Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 x Part Number OL-3847-01 Rev.
About This Guide This preface describes the objectives, audience, organization, and conventions of the Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5. Objectives This guide describes how to plan a PNNI network before for installing and configuring the following products: • Cisco MGX 8830 Release 3.0 and higher • Cisco MGX 8850 (PXM1E) Release 3.0 and higher • Cisco MGX 8850 (PXM45) Release 2.0 and higher • Cisco MGX 8880 Media Gateway Release 5.
About This Guide Conventions • Chapter 3, “Address and Closed User Group Planning,” describes how to implement network plans using ATM addresses that help define the network structure. • Chapter 4, “Planning Intermediate Route Selection,” describes how PNNI network nodes select routes and provides guidelines for influencing route selection. Conventions This publication uses the following conventions. Command descriptions use these conventions: • Commands and keywords are in boldface.
About This Guide Documentation Documentation A Guide to Cisco Multiservice Switch and Media Gateway Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.
About This Guide Documentation Technical Manual Order of Use Use the technical manuals listed here in the following order: Step 1 Refer to the documents that ship with your product. Observe all safety precautions. • Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES)—This document familiarizes you with safety precautions for your product.
About This Guide Documentation Note Manual titles may be different for earlier software releases. The titles shown in Table 1 are for the April 2004 release. Technical Manual Titles and Descriptions Table 1 lists the technical manuals and release notes that support the April 2004 multiservice switch product releases. Books and release notes in Table 1 are listed in order of use and include information about which multiservice switch or media gateway the document supports.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 — Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) Document Title and Part Number MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 — Cisco ATM and Frame Relay Services (MPSM-T3E3-155) Configuration Guide and Command Reference for MGX Switches, Release 5 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) (continued) MGX MGX BPX with SES 8230 Rel. 8250 Rel. 1.3 1.3 Rel. 4 MGX 8850 (PXM1) Rel. 1.3 MGX 8830 Rel. 5 MGX 8850 (PXM1E) Rel. 5 MGX 8850 (PXM45) Rel. 5 MGX 8950 Rel. 5 MGX 8880 Rel. 5.
About This Guide Documentation Table 1 also lists the latest documentation available for the Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches. These switches use the PXM1 processor card. Although there are new features in MGX Release 1.3 for these switches, only the release notes were updated.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 Explains how to configure the AXSM cards and provides a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM-XG, AXSM/A, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX 8800 Series Switch Command Reference, Release Provides detailed information on the general command line 1.1.3 for the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 edge concentrators. DOC-7811210= Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switch.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Cisco WAN Manager Installation Guide, Release 15 Provides procedures for installing Release 5 of the CWM network management system.
About This Guide Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Description Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00 Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies. OL-4627-01 Release Notes for Cisco WAN Manager, Release 15.0.
About This Guide Documentation Finding Documentation for Cisco MGX, BPX, SES, and CWM Products The previous “Ordering Documentation” section applies to other Cisco documentation. Starting in 2003, all documents listed in the “Related Documentation” section are available online only unless stated otherwise. You can find the documents listed in Table 1 online as follows: • In your browser’s URL field, enter www.cisco.com.
About This Guide Obtaining Technical Assistance Documentation Feedback You can submit e-mail comments about technical documentation to bug-doc@cisco.com. You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.
About This Guide Obtaining Additional Publications and Information For a complete listing of Cisco TAC contacts, go to this URL: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml TAC Case Priority Definitions To ensure that all cases are reported in a standard format, Cisco has established case priority definitions. Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations.
About This Guide Obtaining Additional Publications and Information • Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL: http://www.cisco.com/ipj • Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL: http://www.cisco.
About This Guide Obtaining Additional Publications and Information Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 xxxii Part Number OL-3847-01 Rev.
C H A P T E R 1 Introduction to PNNI Private Network-to-Network Interface (PNNI) is a suite of network protocols that can be used to discover an ATM network topology, create a database of topology information, and route calls over the discovered topology. With proper planning, setting up a PNNI network is much easier and faster than manually configuring connections through an ATM network.
Chapter 1 Introduction to PNNI The Single Peer Group Topology Tip A node is a network device that communicates with other network devices. Cisco PNNI-compatible devices serve as nodes in a PNNI network. In this document, the terms node and switch are often used interchangeably. However, in most cases, the PNNI node is a component of a Cisco PNNI-compatible device. For example, some Cisco MGX switches, Release 2.0 and later, can operate as both a PNNI node and as an MPLS device.
Chapter 1 Introduction to PNNI The Hierarchical PNNI Network Topology Example Single Peer Group Topology 66057 Figure 1-1 PNNI network A single peer group topology is the easiest to set up. Since all communications are between nodes in the same peer group, you do not have to configure connections to other peer groups or to other network types. If the network will never connect to a public network, you can use most of the default PNNI configuration settings.
Chapter 1 Introduction to PNNI The Hierarchical PNNI Network Topology Note Hierarchical PNNI networks are not supported on Cisco MGX 8850 switches before Release 2.1.60, and they are not supported on the SES PNNI Controller before Release 1.1.60.
Chapter 1 Introduction to PNNI The Hierarchical PNNI Network Topology Figure 1-3 Example Hierarchical PNNI Network Topology Showing a Two-Level Hierarchy Level 40 Peer group 2 peer Peer group 5 Level 56 Peer group 1 Peer group 4 PNNI networks 66059 Peer group 3 In a hierarchical PNNI network, logical levels are used to manage the portions of the PNNI database that describe communications paths between individual peer groups.
Chapter 1 Introduction to PNNI The Hierarchical PNNI Network Topology Hierarchical networks can support thousands of nodes because each higher level summarizes information for all lower levels. For example, suppose a level 64 peer group were added below Peer Group 2 in Figure 1-3. All nodes in the new level 64 peer group would be summarized by the peer group leader for Peer Group 2.
Chapter 1 Introduction to PNNI The Hierarchical PNNI Network Topology Figure 1-4 Simple Node Representation Outside link 2 Outside link 1 Peer Group A Outside link 3 Outside link 4 Other peer groups receive information about the outside links leading to the local peer group, but no internal peer group information is advertised to other peer groups. The advantage of simple node representation is that it keeps the PNNI database within each node smaller than that for complex node representation.
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.
Chapter 1 Introduction to PNNI PNNI Internetworking with IISP Figure 1-6 Example PNNI Internetworking with AINI Topology AINI PNNI network PNNI network 66061 AINI PNNI Internetworking with IISP Interim Inter-Switch Protocol (IISP) is the predecessor to AINI and serves the same purpose as AINI, which is to link two independent PNNI networks. Unlike AINI, IISP does not support all UNI 4.0 features. Note Standards-based IISP supports SVC and SVP connections.
Chapter 1 Introduction to PNNI PNNI Internetworking with IISP Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 1-10 Part Number OL-3847-01 Rev.
C H A P T E R 2 Interoperability and Performance Planning This chapter describes the standards supported by the Cisco switches covered in this guide and provides performance specifications for these switches. Compatible Standards The Cisco switches described in this guide are designed to interoperate with switches that support the following standards: • Private Network-to-Network Interface (PNNI) Version 1 • User-Network Interface (UNI) 3.0 • UNI 3.1 • UNI 4.
Chapter 2 Interoperability and Performance Planning Specifications Table 2-1 PNNI Networking Specifications for MGX Switches and the MGX 8880 Media Gateway MGX 8850, MGX 8880 & MGX 8950 (PXM45) Capabilities 2.1.
Chapter 2 Interoperability and Performance Planning Specifications Table 2-1 PNNI Networking Specifications for MGX Switches and the MGX 8880 Media Gateway (continued) MGX 8850, MGX 8880 & MGX 8950 (PXM45) MGX 8830 & MGX 8850 (PXM1E) Capabilities 2.1.7 3 4 5 3 4 5 SVC connections per switch (maximum)3 50 K 250 K 250 K 250 K 13.5 K 13.5 K 13.
Chapter 2 Interoperability and Performance Planning Connection Limit Adjustments Table 2-2 PNNI Networking Specifications for SES Equipped BPX Switches (continued) BPX/SES Capabilities SES 1.0 SES 1.
Chapter 2 Interoperability and Performance Planning Physical Network Planning Table 2-3 identifies some important differences between the way connections are counted on the switch and in CWM. For example, although all connection types are counted as one connection on the switch, SVCs and pass-through connections are not included when calculating the connection limit for CWM. DAX SPVCs, however, are counted as two connections when calculating the connection limit for CWM.
Chapter 2 Interoperability and Performance Planning Planning Guidelines for Individual Peer Groups Multiple Links Between Adjacent Peer Groups Communications between two peer groups takes place through two border nodes. Parallel links between two border nodes improves reliability. Adding additional border nodes to handle communications between two peer groups provides alternative routing paths and prevents network outages caused by a single node failure.
Chapter 2 Interoperability and Performance Planning Planning Guidelines for Hierarchical Networks • Although the number of network nodes in your network might not dictate a hierarchical topology, other network requirements can. For example, an anticipated network expansion might be easier later if you plan for it now. • Consider future growth when planning peer groups.
Chapter 2 Interoperability and Performance Planning Planning Guidelines for Hierarchical Networks Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 2-8 Part Number OL-3847-01 Rev.
C H A P T E R 3 Address and Closed User Group Planning Proper address planning can greatly increase the performance of a PNNI WAN. Although a PNNI WAN can support almost any addressing scheme, an uncoordinated address scheme can cause excessive address advertisement and needless rerouting, both of which reduce network performance. A good addressing plan is one which is hierarchical in nature and thus summarizes simply and efficiently.
Chapter 3 Address and Closed User Group Planning Address Planning Overview Furthermore, PNNI switches exchange data with all other nodes in the peer group, so lots of address information would be transmitted constantly throughout the network as PNNI monitors the network topology. Now let’s consider a more efficient example. Figure 3-1 shows a PNNI network with some simplified addresses in place of the 20-byte ATM addresses. Figure 3-1 PNNI Addressing Example A3 A5 A.21 A.11 A1 A2 Peer group A A.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings connections as it attempts to locate the correct node. A better design would use the longest possible prefix to represent all the interfaces on a node, and then a longer prefix on each interface that uniquely defines each interface. At the end of this chapter, there are two worksheets (Table 3-4 and Table 3-5) into which you can enter your WAN address values.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Supported Address Formats The Cisco MGX and SES switch products support the following standard ATM formats: • Native E.164 • Data Country Code (DCC) • International Code Designator (ICD) • AESA-embedded E.164 • Local AESA The native E.164 address specifies an Integrated Services Digital Network (ISDN) number and is used by Public Switched Telephone Networks (PSTNs). A native E.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Table 3-1 ATM Address Components ATM Field Description Default Values AFI Authority Format Identifier (1 byte). 47 ICD International Code Designator (2 bytes) The default value is the ICD assigned to Cisco Systems. 0091 IDI Initial Domain Identifier (8 bytes). The contents of this field vary depending on the value of the AFI.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Address Registration Authorities Table 3-2 lists the address registration authorities. Table 3-2 Category Address Registration Authorities Type Authorities ATM Service ICD Providers (ASPs) DCC 1. US—American National Standards Institute (ANSI). 2. UK—British Standards Institution (BSI). Identifiers for Organizations for Telecommunications Addressing (IOTA) http://www.bsi-global.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Figure 3-3 PNNI Network Physical Topology 38622 PNNI network The topology shown in Figure 3-3 becomes a Single Peer Group (SPG) PNNI WAN if no hierarchy is applied. In an SPG WAN, every node stores information about every other node and the CPE that connect to it.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings The network shown in Figure 3-4 uses the same physical topology as that shown in Figure 3-3 for an SPG WAN. The difference is that the physical network has been divided into five peer groups at level 56. The level will be explained later in this section. What is important to understand now is that the physical topology is still the same as when all nodes were in a single peer group.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Table 3-3 Recommended PNNI Level Values Level Peer Group ID Portion of ATM Address Peer Group ID Length (Bytes) 8 11 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 1 16 11 22 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 2 24 11 22 33 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 3 32 11 22 33 44 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 4 40 11 22 33 44 55 xx xx xx xx xx
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.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings • If you change the address format, you need to change the peer group ID. • If you change any of the identifiers within the unique portion of the peer group ID (for example, the ICD), you must change the peer group ID. Enter the peer group ID into the Nodal Address Worksheet, Table 3-4, which appears at the end of this chapter.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings Selecting the ILMI Address Prefix Although ILMI is not part of the PNNI specification, ILMI addressing should be coordinated with PNNI addressing to minimize the number of PNNI advertised ATM addresses. The Cisco MGX and SES switch products support ILMI dynamic addressing on UNI ports. When dynamic addressing is enabled, one or more ILMI prefixes can be used to generate ATM addresses for CPE as follows: 1.
Chapter 3 Address and Closed User Group Planning Planning Address Configuration Settings To enable communications over AINI and IISP links, static addresses must be configured on the end of each link as described in the following guides: • Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 • Cisco SES PNNI Controller Software Configuration Guide, Release 3 There is no default prefix for AINI and IISP links, and because these protocols are us
Chapter 3 Address and Closed User Group Planning Closed User Group Overview • Confirm that each reconfigured node ID and node address are unique. The switch software does not detect configuration errors caused by duplicate ATM addresses. • Use summary port prefixes wherever possible to reduce overhead. Closed User Group Overview The PNNI Closed User Group (CUG) feature allows network users to form a closed community within a PNNI network.
Chapter 3 Address and Closed User Group Planning Planning CUG Configuration Settings CUG membership is supported as follows: Note • An ATM address or ATM address prefix can be a member of up to 100 CUGs. • CUGs can be provisioned on up to 200 ATM addresses or prefixes. • The maximum number of CUGs is 65535. • An ATM address to which a CUG is assigned can use either the NSAP or E.164 address format. The CUG feature is not supported on nodes which are configured with right-justified E.
Chapter 3 Address and Closed User Group Planning Planning CUG Configuration Settings The CPE must be configured to specify a particular CUG index during call setup when any of the following conditions exist: • One or more CUGs are defined for the CPE prefix or address and no preferential CUG is defined. • Multiple CUGs are defined for the prefix or address and the CPE intends to use a CUG other than the preferential CUG.
Chapter 3 Address and Closed User Group Planning Planning CUG Configuration Settings Note The network administrator can set the internal access during the initial CUG member configuration, or change the configuration later. There is no option to simultaneously block incoming and outgoing communications. If the administrator needs to block incoming and outgoing communications, the member should be removed from the CUG.
Chapter 3 Address and Closed User Group Planning Worksheets Selecting a Default CUG Address A default CUG address is a default address that is assigned to a switch to be used for CUG validation when the connected CPE does not signal a calling party ATM address. The default CUG address does not have to match any addresses or prefixes assigned on the switch. It is not used for PNNI routing. It is simply a default address to which a CUG can be assigned.
Chapter 3 Address and Closed User Group Planning Worksheets Table 3-5 Port Address Worksheet Port AINI and IISP Prefixes and Addresses ILMI Prefixes UNI Addresses Table 3-6 is a worksheet for planning a single closed user group on a single switch. Use a copy of this table for each CUG on a switch. Remember that only one address or prefix can serve as the default CUG address on a switch, and there can be only one preferred CUG per address or prefix.
Chapter 3 Address and Closed User Group Planning Worksheets Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 3-20 Part Number OL-3847-01 Rev.
C H A P T E R 4 Planning Intermediate Route Selection When a PNNI network node receives a call request, there can be multiple routes available that meet the quality of service (QoS) requirements for the call. This chapter describes how PNNI selects a route from multiple acceptable routes, and it describes parameters that you can modify to control route selection.
Chapter 4 Planning Intermediate Route Selection How MGX and SES Nodes Select Routes You can change the AW on links to control network traffic. For example, you can reduce traffic on a backup link by increasing the AW to more than that on the desirable link. If the desirable link fails, the backup link becomes the lowest cost link and becomes available. When AW is applied to a route, it is sometimes called the cumulative AW and is the sum of the AW values assigned to all links along a route.
Chapter 4 Planning Intermediate Route Selection How MGX and SES Nodes Select Routes route more calls for the link. Of course, if link users suddenly start using all link resources, some user-compliant traffic may be discarded when congestion occurs. Bandwidth overbooking can be configured on a per-service-class-basis for each interface in the node. Note Beginning with Release 3.0, Cisco MGX and SES nodes also support connection overbooking, which is configured with the addcon command.
Chapter 4 Planning Intermediate Route Selection How MGX and SES Nodes Select Routes an external network, the use of the 0-length prefix allows the administrator to specify that all calls that do not match a longer prefix should be routed to the external network. If the 0-length prefix is not used, the administrator must manually configure static addresses for all external destinations. MGX and SES nodes generate routing tables using PTSE information from other nodes and the Dijkstra SPF Algorithm.
Chapter 4 Planning Intermediate Route Selection How MGX and SES Nodes Select Routes Each class of service SPT is simply a list of the shortest paths for a particular routing metric to all known destinations. AW SPTs list the shortest paths or routes based on the lowest cumulative AW, and CTD SPTs list the shortest routes based on the lowest cumulative CTD. The number of shortest paths stored in a SPT for any destination depends on whether there are multiple routes with the lowest routing metric value.
Chapter 4 Planning Intermediate Route Selection How MGX and SES Nodes Select Links Any route selected from the SPTs must conform to all specified metrics. If a conforming route is not available in chosen SPT, on demand routing is used to find a conforming route. On PXM1E cards and service modules, you can change this with the addcon command. On-Demand Routing When the SPTs cannot produce a route for a connection, the switch performs on-demand routing.
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes Table 4-3 Link Selection Parameters Required for Various Classes of Service Service Class Address AW maxCR AvCR CTD CDV CLR01 CLR0+12 CBR Required Required Required Required Required Required Required Required rt-VBR Required Required Required Required Required Required Required Required nrt-VBR Required Required Required Required Required — Required Required ABR Required
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes Note In all Release 3 software, the preferred routing feature specifies a route within a single peer group. Release 3 software does not support preferred routes that span multiple peer groups. Release 4 and later software does support preferred routes that span multiple peer groups. The preferred route and directed route for an SPVC or SPVP is defined when the connection is created.
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes The grooming feature can be implemented at any time. Grooming is not configured at the same time as connections, so there is no penalty if you do not include grooming in the initial plan for a PNNI network. Soft Rerouting The soft reroute feature is new in Release 5 and minimizes reroute times by establishing a new connection before releasing the rerouted connection.
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes Figure 4-1 P2MP Root, Leaf, and Party Components Leaf endpoint Party 1 Party 2 Party 3 Party 4 Leaf endpoint Party 5 Party 6 Party 7 Party 8 75690 Root endpoint The simplest P2MP connection takes place through a single node. One endpoint serves as the root of a simple tree topology and is labeled the root end point. The data traffic is uni-directional.
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes The farthest-node branch option is a PNNI enhancement that allows PNNI to use network links more efficiently. Figure 4-2 demonstrates farthest-node branching.
Chapter 4 Planning Intermediate Route Selection Additional Routing Features in MGX and SES Nodes Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 4-12 Part Number OL-3847-01 Rev.
INDEX AINI Numerics MGX 8850 support 0-length prefix 4-3 planning address prefixes SES support version ABR 1-8 2-1 American National Standards Institute description ANSI 4-4 route selection parameter addcon command 4-7 APS 3-6 2-5 default address 1-6 address formats AINI prefix default formats planning selection 3-12 ILMI prefix static 3-13 3-11 3-12 3-13 See AESA 3-6 route selection parameter 4-7 ATM public network, PNNI level limitation audience, for this document 3-11 3
Index AW Cisco MGX 8850 4-1 default value 5040 definition AINI support 4-1 1-8 hierarchical PNNI support 4-1 route selection parameter 4-7 1-4 Cisco MGX 8880 Media Gateway Cisco MGX switches 1-1 1-1 Cisco Service Expansion Shelf B See SES bandwidth overbooking best fit 4-2, 4-3 See TAC 4-6 Cisco WAN Manager border nodes definition See CWM 1-8 planning guidelines BPX 8600 class of service 2-7 See CUG farthest-node CLR0+1, route selection parameter 4-11 CLR0, route selection
Index CUG calls barred 3-16 configuration worksheet default address explicit 3-19 ordering xxvii xi that ships with products 3-17 3-15 xiv xxii E 3-15 internal access control overview selection 3-16 E.
Index I ICD 3-4 4-6 parallel links 2-5 route selection option IISP 4-7 logical group node Cisco enhanced 1-9 See LGN planning address prefixes topology definition version 3-12 logical nucleus 1-9 logical spokes 2-1 LOS ILMI version 1-2 1-2 3-12 2-1 implicit CUG inside link M 3-16 index, CUG 3-15 MAC address 1-8 3-11 manuals Interim Inter-Switch Protocol See documentation See IISP master endpoint, connection interlock code 3-15 3-1 maxCR international code designator
Index N network database 1-1 nodal address worksheet nodal transit restriction 2-5 3-18 party, P2MP 4-10 paths 4-9 4-9 2-6 peer group ID 3-10 peer group leader node See PGL 1-8 peer groups complex node representation definition 1-7 ID selection 1-2 leaders simple node representation 1-6 1-6 See hierarchical PNNI See nrt-VBR single note symbol, defined xii PGL nrt-VBR 1-2 1-5 definition description 4-4 1-6 planning guidelines route selection parameter 4-7 priority 1
Index PNNI topology state packets Point-to-Multipoint 1-2 root 4-10 route See P2MP port address worksheet 3-19 CDV 4-2 CTD 4-2 port multicasting 4-10 directed 4-7 preferential CUG 3-16, 3-17 maxCR 4-3 metrics 4-1 preferred route 4-7 routing preferred preferred route selection 4-1 prefix AvCR AINI AW 3-12 IISP 3-12 ILMI 3-12 SPVC priority bumping PTSP 1-2 best fit 4-6 first fit 4-6 4-7 4-7 on-demand 1-2 preferred 1-1 SPT 4-6 4-7 4-3 routing control channe
Index single peer group definition topology AINI topology definition 1-2 planning guidelines PNNI level hierarchical PNNI 2-6 benefits 3-7 slave endpoint, connection slot multicasting soft reroute planning source address 3-7 See hierarchical PNNI 3-1 single peer group 3-1 Traffic Management 4.
Index Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 IN-8 Part Number OL-3847-01 Rev.
