Cisco Systems Network Router Physical Network Planning, Install Redundant Hardware in Switches

Page 47

Chapter 2 Interoperability and Performance Planning

Physical Network Planning

Table 2-3identifies 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.

The real issue is what happens if you configure a CWM-managed switch with only DAX SPVCs. In this example, the switch can support 250K DAX SPVCs, but CWM can support only 125K DAX SPVCs.

To determine the actual connection limits for a CWM-managed switch, multiply the number of each connection type by the unit cost in each column of Table 2-3. The total for each column must not exceed 250K.

Physical Network Planning

The PNNI switches described in this guide can reroute connections and adjust to equipment or link failures only when the physical network has been designed to use redundant hardware and links. When designing a PNNI network, consider doing the following:

Install redundant hardware in switches

Install parallel links between adjacent switches

Set up multiple links between adjacent peer groups

Use multiple links when connecting to an external network

Provide multiple communication paths between any two nodes that will communicate with each other

The following sections provide additional information on these guidelines.

Install Redundant Hardware in Switches

The switches described in this guide support redundant power supplies, Processor Switch Module (PXM) cards, line cards, and trunk cards. Although PNNI can reroute calls, using redundant hardware can improve network stability and performance by preventing reroutes caused by hardware failure.

Parallel Links Between Adjacent Switches

When there are two or more links between adjacent switches, those links are called parallel links. Parallel links support more traffic than single links and provide link redundancy for each other. If one link fails, the other is still available. Another way to provide link redundancy is to use the Automatic Protection System (APS), which provides link redundancy for optical interfaces.

By default, MGX switches load balance across parallel links. Load balancing uses one of four methods to balance the traffic load over parallel links. The goal is to prevent any single link from being overloaded when other links have available bandwidth. Load balancing is described in more detail in Chapter 4, “Planning Intermediate Route Selection.”

 

 

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

 

 

 

 

 

 

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

 

 

2-5

 

 

 

 

 

Image 47
Contents Text Part Number OL-3847-01 Rev. D0 Corporate HeadquartersCopyright 2003, Cisco Systems, Inc All rights reserved Iii N T E N T SCompatible Standards Worksheets Part Number OL-3847-01 Rev. D0, April Vii G U R E SViii B L E S Part Number OL-3847-01 Rev. D0, April Organization ObjectivesAudience Xii ConventionsXiii DocumentationDocumentation Notes for the April 2004 Product Releases Related DocumentationXiv Technical Manual Order of UseTerms Technical Manual Titles and DescriptionsXvi Xvii Xviii Xix Reference Guides Xxi Xxii Document Title DescriptionXxiii Xxiv Xxv Xxvi Xxvii Obtaining DocumentationCisco.com Ordering DocumentationXxviii Changes to This DocumentChapter Changes Opening a TAC Case Obtaining Technical AssistanceDocumentation Feedback Cisco TAC WebsiteXxx Obtaining Additional Publications and InformationTAC Case Priority Definitions Xxxi Xxxii Pnni Network Database Introduction to PnniSingle Peer Group Topology Example Single Peer Group Topology Hierarchical Pnni Network TopologyPeer group Ppeer Simple Node Representation Peer Group LeadersSimple Node Representation Complex Node RepresentationHierarchical Pnni Network Benefits Pnni Internetworking with AiniBorder Nodes Example Pnni Internetworking with Aini Topology Pnni Internetworking with IispPart Number OL-3847-01 Rev. D0, April Compatible Standards SpecificationsPXM45/B PXM45Capabilities PXM1ESES Capabilities SESDAX Spvc Connection Limit AdjustmentsConnection Type Switch Connections CWM Endpoints SVCPhysical Network Planning Install Redundant Hardware in SwitchesParallel Links Between Adjacent Switches Multiple Paths Between Network Nodes Planning Guidelines for Individual Peer GroupsMultiple Links Between Adjacent Peer Groups Multiple Links to an External NetworkPlanning Guidelines for Border Nodes Planning Guidelines for Hierarchical NetworksPlanning Guidelines for Peer Group Leaders Part Number OL-3847-01 Rev. D0, April Address Planning Overview Address and Closed User Group PlanningPnni Addressing Example Selecting an ATM Address Format Planning Address Configuration SettingsESI SEL IDP DSP Supported Address FormatsGuidelines for Selecting an Address Format ATM Field Description Default ValuesDCC Selecting a Pnni LevelAddress Registration Authorities Category Type Authorities4shows an example topology of a Pnni MPG WAN Part Number OL-3847-01 Rev. D0, April Level Peer Group ID Portion of ATM Address Bytes LengthSelecting the Pnni Peer Group ID Default Peer Group ID20-byte Node Address Selecting the ATM AddressPlanning Address Prefixes for Aini and Iisp Links Selecting the Ilmi Address PrefixSelecting the Spvc Address Prefix Additional Guidelines for Creating an Address Plan Selecting Static Addresses for UNI PortsClosed User Group Example Closed User Group OverviewSelecting an Index Planning CUG Configuration SettingsSelecting an Interlock Code Selecting CPE Addresses Selecting Internal CUG Access OptionsSpecifying a Preferential CUG Selecting External CUG Access OptionsWorksheets Selecting a Default CUG AddressCUG Part Number OL-3847-01 Rev. D0, April Link and Route Metrics Administrative WeightHow MGX and SES Nodes Select Routes Available Cell Rate Cell Transfer DelayCell Delay Variation Shortest Path Tables Shortest Path Table RoutingMaximum Cell Rate Traffic Metric Class of Service TablesService Class Acronym Definition Guidelines CTD CDVHow SPVCs and SPVPs use the SPTs How SVCs and SVPs use the SPTsLoad Balancing for SPT and On-Demand Routing How MGX and SES Nodes Select LinksOn-Demand Routing CLR0+12 Additional Routing Features in MGX and SES NodesService Preferred RoutingGrooming Priority RoutingNodal Point-to-Multipoint Branch Restriction Soft ReroutingPriority Bumping Blocking Pass-Through ConnectionsAXSM-XG AXSM/AAXSM/B AXSM-EFarthest Node Branching Part Number OL-3847-01 Rev. D0, April Ansi APS ABRAesa AiniIN-2 P2MPCBR CTDIN-3 CUGCWM DININ-4 IN-5 PGLPnni MGX SESIN-6 IN-7 UBRUNI TACIN-8