Cisco Systems Network Router manual Closed User Group Overview, Closed User Group Example

Page 64

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. Figure 3-7shows an example of closed user groups in a network.

Figure 3-7 Closed User Group Example

CPE A,

CUGs 1 & 2

Switch W

Switch Y

Switch Z

CPE C,

CUG 2CPE D, CUG 2

CPE B,

CUG 1

Switch X

CPE E

116412

A network user may be associated with one, multiple, or no CUGs. In Figure 3-7, CPE A is a CUG member of CUGs 1 and 2. CPE B, C, and D are members of either CUG 1 or CUG 2. Members of a specific CUG can communicate typically among themselves, but in general not with network users outside of the CUG. In the example, CPE A can communicate with CPE B, C, and D because it is a member of both CUGs. This section will also show how CPE A can be enabled for communications with CPE E.

Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG. For example, CPE B can be configured so that it cannot originate calls to other CUG 1 members, but it can accept calls from other members.

Configuration options allow a network user to be further restricted when originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user. In Figure 3-7, CPE E is not a member of any CUG and the default configuration for CUG members will prevent communications between CPE E and the other CPE. Using configuration options, however, CPE1 can be allowed to originate calls to CPE E, and CPE D can be configured to accept calls from CPE E.

The user within a CUG is actually a UNI ATM End Station Address (AESA) or an ATM address prefix, and this address or address prefix can be assigned to more than one interface on a switch. When an ATM address is assigned to more than one CUG, the CPE that use that address must specify the CUG for a connection or accept a configured default CUG called the preferential CUG.

CUG membership is evaluated only when setting up connections. CUG membership is an independent feature and does not interoperate with the address filtering feature.

The CUG feature follows the ITU-T Q.2955.1 recommendation and supports point-to-point and point-to-multipoint connections.

CUGs are managed with the switch CLI. Cisco MGX switches and Cisco LS1010 switches can participate in CUGs. The Cisco WAN Manager (CWM) program does not currently support CUGs.

 

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

3-14

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

Page 63 Page 65
Image 64
Page 63 Page 65
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