hit counter script
Cisco Network Router User Manual
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Network Router
  5. Network Router
  6. User manual
Cisco Network Router User Manual

Cisco Network Router User Manual

Cisco systems network router user manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
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. D0

Advertisement

Table of Contents
loading

Related Manuals for Cisco Network Router

Summary of Contents for Cisco Network Router

  • Page 1 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 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100...
  • Page 2 CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE,...
  • Page 3 About This Guide Objectives Audience Organization Conventions Documentation Documentation Notes for the April 2004 Product Releases Related Documentation Technical Manual Order of Use Technical Manual Titles and Descriptions Obtaining Documentation Cisco.com Ordering Documentation Finding Documentation for Cisco MGX, BPX, SES, and CWM Products Changes to This Document Documentation Feedback Obtaining Technical Assistance...

  • Page 4: Table Of Contents

    Interoperability and Performance Planning C H A P T E R Compatible Standards Specifications Connection Limit Adjustments Physical Network Planning Install Redundant Hardware in Switches Parallel Links Between Adjacent Switches Multiple Links Between Adjacent Peer Groups Multiple Links to an External Network Multiple Paths Between Network Nodes Planning Guidelines for Individual Peer Groups Planning Guidelines for Hierarchical Networks...
  • Page 5 Planning CUG Configuration Settings Selecting an Interlock Code Selecting an Index Selecting CPE Addresses Selecting Internal CUG Access Options Selecting External CUG Access Options Specifying a Preferential CUG Selecting a Default CUG Address Worksheets Planning Intermediate Route Selection C H A P T E R How MGX and SES Nodes Select Routes Link and Route Metrics Administrative Weight...
  • Page 6 Contents Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 Part Number OL-3847-01 Rev. D0, April, 2004...
  • Page 7 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...
  • Page 8 Figures Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 viii Part Number OL-3847-01 Rev. D0, April, 2004...
  • Page 9 Table 1 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) 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...
  • Page 10 Tables Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 Part Number OL-3847-01 Rev. D0, April, 2004...

  • Page 11: About This Guide

    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 •...
  • Page 12 Conventions Chapter 3, “Address and Closed User Group Planning,” • using ATM addresses that help define the network structure. • Chapter 4, “Planning Intermediate Route Selection,” 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.

  • Page 13: Related Documentation

    About This Guide 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. Documentation Notes for the April 2004 Product Releases The April 2004 release includes new hardware or features for the following releases: Cisco MGX Release 5 for the MGX 8880 Media Gateway •...
  • Page 14 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 •...
  • Page 15 About This Guide Manual titles may be different for earlier software releases. The titles shown in Note 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.
  • Page 16 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 Overview and Safety Documents Guide to Cisco Multiservice Switch and Media Gateway Documentation DOC-7814807= Installation Warning Card DOC-7812348= Regulatory Compliance and Safety...
  • Page 17 About This Guide 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 Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 OL-4536-01...
  • Page 18 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 Planning and Configuration Guides Cisco PNNI Network Planning Guide for MGX and SES Products OL-3847-01 Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX...
  • Page 19 About This Guide 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 Service Module Configuration and Reference Guides Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 78-12510-02 Cisco Frame Relay Software...
  • Page 20 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 Cisco ATM and Frame Relay Services (MPSM-T3E3-155) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4554-01 Cisco Voice Switch Services...
  • Page 21 About This Guide 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 Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3 DOC-7811240= Cisco SES PNNI Controller Command Reference, Release 3 DOC-7814260=...
  • Page 22 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. And the following books contain some information about configuring the MPSM-8-T1E1 card for use in these switches: Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for...
  • Page 23 About This Guide Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4548-01 Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-0453-01...
  • Page 24 Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3 DOC-7811210= Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3 DOC-7811240= Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 OL-4545-01...
  • Page 25 About This Guide Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 OL-5087-01 Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 78-12510-02 Cisco PNNI Network Planning Guide for MGX and SES...
  • Page 26 Documentation Table 3 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products (continued) Document Title Cisco WAN Manager Installation Guide, Release 15 OL-4550-01 Cisco WAN Manager SNMP Service Agent, Release 15 OL-4551-01 Cisco WAN Manager User’s Guide, Release 15 OL-4552-01 Cisco Frame Relay Software Configuration Guide and Command Reference for the Cisco MGX 8850 (PXM45)

  • Page 27: Obtaining Documentation

    Nonregistered Cisco.com users can order documentation through a local account representative by • calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387). Part Number OL-3847-01 Rev. D0, April, 2004...
  • Page 28 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 In your browser’s URL field, enter www.cisco.com.

  • Page 29: 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.

  • Page 30: Obtaining Additional Publications And Information

    • to this URL to visit the company store: http://www.cisco.com/go/marketplace/ The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as • ordering and customer support services. Access the Cisco Product Catalog at this URL: http://cisco.com/univercd/cc/td/doc/pcat/ Cisco Press publishes a wide range of general networking, training and certification titles.
  • Page 31 About This Guide 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...
  • Page 32 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. D0, April, 2004...
  • Page 33 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.
  • Page 34 The Single Peer Group Topology 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.
  • Page 35 Chapter 1 Introduction to PNNI Figure 1-1 Example Single Peer Group Topology 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.
  • Page 36 The Hierarchical PNNI Network Topology Hierarchical PNNI networks are not supported on Cisco MGX 8850 switches before Release 2.1.60, and Note they are not supported on the SES PNNI Controller before Release 1.1.60. Figure 1-2 Example Hierarchical PNNI Network Topology Showing Multiple Peer Groups Peer group 2 Peer...
  • Page 37 Chapter 1 Introduction to PNNI Figure 1-3 Example Hierarchical PNNI Network Topology Showing a Two-Level Hierarchy Peer Peer group 2 group 2 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.
  • Page 38 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 leader for Peer Group 2. The impact on the hierarchical network would be the following: Peer Group 2 would support one less physical node because it would have to add one LGN to •...
  • Page 39 Chapter 1 Introduction to PNNI Figure 1-4 Simple Node Representation Outside link 1 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.
  • Page 40 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.
  • Page 41 Chapter 1 Introduction to PNNI Figure 1-6 Example PNNI Internetworking with AINI Topology PNNI network 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.
  • Page 42 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. D0, April, 2004...

  • Page 43: Chapter 2 Interoperability And Performance Planning

    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 •...
  • Page 44 Specifications Table 2-1 PNNI Networking Specifications for MGX Switches and the MGX 8880 Media Gateway Capabilities PNNI nodes per SPG PNNI network (maximum recommended) Hierarchical levels per MPG PNNI network (maximum/recommended) Visible PNNI peer groups per network (recommended) PNNI nodes per lowest level MPG peer group (recommended) PNNI links per switch (maximum) PXM1E...
  • Page 45 Chapter 2 Interoperability and Performance Planning Table 2-1 PNNI Networking Specifications for MGX Switches and the MGX 8880 Media Gateway (continued) Capabilities SVC connections per switch (maximum) SPVC connections per switch (maximum) Total connections per switch (SVCs and SPVCs) Border ports per complex node ATM prefixes per interface (maximum) ATM addresses per interface...

  • Page 46: Connection Limit Adjustments

    Connection Limit Adjustments Table 2-2 PNNI Networking Specifications for SES Equipped BPX Switches (continued) Capabilities Total connections per switch (SVCs and SPVCs) Physical ATM interfaces per switch (maximum) Preferred routes per switch (maximum) P2MP root connections per switch P2MP branches per switch P2MP parties allowed per root connection P2MP parties per switch...

  • Page 47: Physical Network Planning

    Chapter 2 Interoperability and Performance 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.

  • Page 48: Multiple Links Between Adjacent Peer Groups

    The following list summarizes the capabilities and guidelines for a single peer group: For networks with less than 100 nodes, Cisco Systems recommends using a single peer group • topology.

  • Page 49: Planning Guidelines For Hierarchical Networks

    Chapter 2 Interoperability and Performance Planning 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.
  • Page 50 Chapter 2 Interoperability and Performance Planning Planning Guidelines for Hierarchical Networks Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 Part Number OL-3847-01 Rev. D0, April, 2004...

  • Page 51: Chapter 3 Address And Closed User Group Planning

    All Cisco MGX and SES switch products ship with default addresses. These defaults are provided for Note lab evaluations of these products. Before the switch is deployed, Cisco Systems advises you to reconfigure the default addresses using the address plan guidelines in this chapter.

  • Page 52: Chapter 3 Addres 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. addresses in place of the 20-byte ATM addresses.

  • Page 53: Planning Address Configuration Settings

    Chapter 3 Address and Closed User Group Planning 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.

  • Page 54: Supported Address Formats

    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).

  • Page 55: Guidelines For Selecting An Address Format

    Authority Format Identifier (1 byte). International Code Designator (2 bytes) The default value is the ICD assigned to Cisco Systems. Initial Domain Identifier (8 bytes). The contents of this field vary depending on the value of the AFI. For example, with a DCC AESA (AFI=39), the IDI value of Hex 840F identifies the United States.

  • Page 56: Address Registration Authorities

    Planning Address Configuration Settings Address Registration Authorities Table 3-2 lists the address registration authorities. Table 3-2 Address Registration Authorities Category Type Authorities ATM Service Providers (ASPs) E.164 International Telecommunications Union (ITU), the National Numbering Authority. Private ASP Addresses Private ATM networks can apply to their ATM Service Provider for addresses. networks Identifiers for Organizations for Telecommunications Addressing (IOTA) http://www.bsi-global.com/DISC/Working+Withyou/Naming+Addressing.xalter.
  • Page 57 Chapter 3 Address and Closed User Group Planning Figure 3-3 PNNI Network Physical Topology The topology shown in applied. In an SPG WAN, every node stores information about every other node and the CPE that connect to it. To distribute information about all the nodes in the WAN, the PNNI switches send PNNI Topology State Element (PTSE) messages to each other on a regular basis.
  • Page 58 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.
  • Page 59 Chapter 3 Address and Closed User Group Planning Table 3-3 Recommended PNNI Level Values Level Peer Group ID Portion of ATM Address 11 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 11 22 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 11 22 33 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 11 22 33 44 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx...

  • Page 60: Selecting The Pnni Peer Group Id

    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.

  • Page 61: Selecting The Atm Address

    Chapter 3 Address and Closed User Group Planning 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.

  • Page 62: Selecting The Ilmi Address Prefix

    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.

  • Page 63: Selecting Static Addresses For Uni Ports

    Chapter 3 Address and Closed User Group Planning 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 •...

  • Page 64: Closed User Group Overview

    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.

  • Page 65: Planning Cug Configuration Settings

    Chapter 3 Address and Closed User Group Planning CUG membership is supported as follows: • 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. •...

  • Page 66: Selecting Cpe Addresses

    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. •...

  • Page 67: Selecting External Cug Access Options

    Chapter 3 Address and Closed User Group Planning The network administrator can set the internal access during the initial CUG member configuration, or Note 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.

  • Page 68: Selecting A Default Cug Address

    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.
  • Page 69 Chapter 3 Address and Closed User Group Planning Table 3-5 Port Address Worksheet Port ILMI Prefixes 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.
  • Page 70 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. D0, April, 2004...

  • Page 71: Chapter 4 Planning Intermediate Route Selection

    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. How MGX and SES Nodes Select Routes MGX and SES nodes provide for the following PNNI route sources: Manually defined preferred routes (Release 3 and later)

  • Page 72: Cell Transfer Delay

    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.

  • Page 73: Maximum Cell Rate

    Chapter 4 Planning Intermediate Route Selection 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. Beginning with Release 3.0, Cisco MGX and SES nodes also support connection overbooking, which is Note configured with the addcon command.
  • Page 74 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.

  • Page 75: How Svcs And Svps Use The Spts

    Chapter 4 Planning Intermediate Route Selection 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.

  • Page 76: On-Demand Routing

    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.

  • Page 77: Additional Routing Features In Mgx And Ses Nodes

    Chapter 4 Planning Intermediate Route Selection Table 4-3 Link Selection Parameters Required for Various Classes of Service Service Class Address Required Required rt-VBR Required Required nrt-VBR Required Required Required Required Required Required 1. CLR is the cell loss ratio for cells with the Cell Loss Priority bit set to 0. 2.

  • Page 78: Priority Routing

    Additional Routing Features in MGX and SES Nodes In all Release 3 software, the preferred routing feature specifies a route within a single peer group. Note 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.

  • Page 79: Soft Rerouting

    Chapter 4 Planning Intermediate Route Selection 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.

  • Page 80: Cisco Pnni Network Planning Guide For Mgx And Ses Products, Release 5

    Additional Routing Features in MGX and SES Nodes Figure 4-1 P2MP Root, Leaf, and Party Components 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. All data flows from the root endpoint to the destination endpoints.
  • Page 81 Chapter 4 Planning Intermediate Route Selection The farthest-node branch option is a PNNI enhancement that allows PNNI to use network links more efficiently. Figure 4-2 Figure 4-2 Farthest Node Branching Switch 1 Root Figure 4-2, Switch 2 supports branching and Switch 3 does not. When PNNI sets up the P2MP connection to parties 1 through 4, it determines that the Switch 2 outgoing interface supports branching, so PNNI establishes 1 SVC between Switch 1 and 2.

  • Page 82: Part Number Ol-3847-01 Rev. D0, April, 2004

    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. D0, April, 2004...
  • Page 83 Numerics 0-length prefix description route selection parameter addcon command 4-3, 4-5, 4-8 addpnni-node command address AINI prefix 3-12 default 3-10 destination formats IISP prefix 3-12 ILMI prefix 3-12 plan guidelines 3-13 planning registration authorities route selection parameter selection 3-11 source SPVC prefix 3-12 static...
  • Page 84 default value 5040 definition route selection parameter bandwidth overbooking 4-2, 4-3 best fit border nodes definition planning guidelines BPX 8600 branching farthest-node 4-11 P2MP British Standards Institution calls barred 3-16 caution symbol, defined description route selection parameter definition route selection parameter cell delay variation See CDV cells per second...
  • Page 85 calls barred 3-16 configuration worksheet 3-19 default address 3-18 explicit 3-16 external access control 3-17 implicit 3-16 index 3-15 interlock code 3-15 internal access control 3-16 overview 3-14 preferential 3-16, 3-17 selection 3-15 specifications 3-15 user 3-14 cumulative AW 3-14 database PNNI PNNI network...
  • Page 86 Index IISP Cisco enhanced planning address prefixes 3-12 topology definition version ILMI address prefix 3-12 version implicit CUG 3-16 index, CUG 3-15 inside link Interim Inter-Switch Protocol See IISP interlock code 3-15 international code designator SeeICD International Telecommunications Union IOTA ISO National Administrative Authority leaf, P2MP 4-10...
  • Page 87 network database network planning, physical network nodal address worksheet 3-18 nodal transit restriction node border complex node representation definition simple node representation non-real-time variable bit rate See nrt-VBR note symbol, defined nrt-VBR description route selection parameter nucleus on-demand routing 4-1, 4-6 outside link overbooking factor P2MP...
  • Page 88 Index PNNI topology state packets Point-to-Multipoint See P2MP port address worksheet 3-19 port multicasting 4-10 preferential CUG 3-16, 3-17 preferred route routing preferred prefix AINI 3-12 IISP 3-12 ILMI 3-12 SPVC 3-12 priority bumping 4-8, 4-9 priority routing processor switch module protocol, link state PTSE 1-2, 3-7...
  • Page 89 single peer group definition planning guidelines PNNI level slave endpoint, connection slot multicasting 4-10 soft reroute software, PNNI support source address source endpoint, connection specifications spokes definition introduction routing SPVC and SPVP usage SVC and SVP usage SPVC address prefix 3-12 standards static ATM addresses, planning...
  • Page 90 Index Cisco PNNI Network Planning Guide for MGX and SES Products, Release 5 IN-8 Part Number OL-3847-01 Rev. D0, April, 2004...

Table of Contents

Save PDF