Cabletron Systems 04-0053-01 3.2 MULTI-LEVEL PNNI TOPOLOGY

SmartSwitch ATM User Guide 3-3

PNNI Routing Multi-level PNNI Topology

Use the show pnninode command to view ATM SmartSwitch PNNI node parameters. For example:

SmartSwitch # show pnninode

NodeIndex(1) :

================================================================================

Node Index : 1

Node Level : 80

Node Id : 50:a0:39:00:00:00:00:00:00:00:00:00:83:91:e5:00:20:d4:29:0e:ff:00

Lowest : True

Admin Status : Up

Oper Status : Up

Node ATM Addr: 39:00:00:00:00:00:00:00:00:00:83:91:e5:00:20:d4:29:0e:ff:00

Peer Group Id: 50:39:00:00:00:00:00:00:00:00:00:00:00:00

Rst Transit : False

Complex Rep : False

Rst Branching: False

DB Overload : False

Ptse : 2

SmartSwitch #

Note Keep in mind that the Node ATM Address is not the same as the ATM address of

the switch client (if any). The Node ATM Address is used by PNNI to identify

PNNI nodes and does not correspond to LANE entities.

3.2 MULTI-LEVEL PNNI TOPOLOGY

Having all ATM switches on your network in the same peer group is a simple way of assuring connectivity between

all nodes. However, depending on the size and complexity of your network, there are advantages to dividing your

PNNI network into different peer groups and levels. The basic steps for creating multiple peer groups and multiple

levels are as follows:

•Set the peer group IDs of ATM SmartSwitches to differentiate their peer group membership.

•Select one (or more) ATM SmartSwitch within each peer group as the Peer Group Leader (PGL).

•Add a higher-level PNNI node to each PGL switch. This higher-level node represents its peer group

as a Logical Group Node (LGN) within the next highest (parent) peer group. Connectivity between

the peer groups is established within the parent peer group.

•Communicate the PGL’s existence to the rest of the peer group by setting its leadership priority.

•Physically connect the two peer groups.

3.2.1 Connecting Multiple Peer Groups

This section presents a practical, step-by-step example of creating a multi-level, multiple peer group topology. The

example is based on the following components and organization (see Figure3-1).

•Six ATM SmartSwitches divided into two peer groups:

-Three ATM SmartSwitches in peer group A (switches SWA1, SWA2, and SWA3)

-Three ATM SmartSwitches in peer group B (switches SWB1, SWB2, and SWB3)

Contents

Main NOTICE FCC CLASS A NOTICE DOC CLASS A NOTICE DECLARATION OF CONFORMITY ADDENDUM Page FIBER OPTIC PROTECTIVE CAPS Page REVISION HISTORY Date Revision Description TABLE OF CONTENTS 7 Firmware Upgrades and Bootline Commands . . . . . . . . . . . . . . . . . . . . . . .7-1 Page Page LIST OF FIGURES Page Page Page 1 INTRODUCTION 1.1 CONTENTS OF THE USER GUIDE 1.2 SMARTSWITCH ATM SWITCH DIFFERENCES 2 IP OVER ATM AND LANE 2.1 CREATING AN IP OVER ATM VLAN Page 2.1.1 Default ATM Addressing for IP over ATM Default Netprefix for SmartSwitch 2500 Family Switches Default Netprefix for SmartSwitch 6500 Default IP Over ATM Local Client Address 2.2 CREATING AN EMULATED LAN Page 2.2.1 ATM Addressing for LAN Emulation SmartSwitch 2500 Family Default LANE Addressing SmartSwitch 6500 Default LANE Addressing 2.2.2 ELANs Across Multiple Switches 2.2.3 Switch Clients 2.2.4 Distributed LANE Services 2. Use the add leselan command to create an LES on switch SW2: 3. Use the show leselan command on SW2 to obtain the ATM address of the LES: 4. On switch SW1, use the command add lecselan to create the LECS: 5. Use the add laneclient command on SW1 to add a client to the ELAN: 2.2.5 ELAN Join Policies Effort Best Effort Elan Join Test - Page The LECSELANLEC Table 2.2.6 LANE Over WAN Circuits Physical Versus Logical BUS Multicasting Page 2.2.7 Using LNNI LANE Service Redundancy Page Page Setting up LNNI LECs Page 6. On SW1, create an ELAN; in this example, we create elan1: Similarly, create the same ELAN (elan1) on SW2: 7. On SW1, enter the show elan 1 command to obtain the ATM address of the LECS on that switch Configuring LNNI Distributed LES/BUS Servers Page Page Page Page 3 PNNI ROUTING 3.1 PNNI NODE ADDRESSING 3.1.1 Default PNNI Addressing SmartSwitch 2500 Family Default Node ID SmartSwitch 6500 Family Default Node ID SmartSwitch 2500 Family Default Node ATM Address SmartSwitch 6500 Default Node ATM Address 3.2 MULTI-LEVEL PNNI TOPOLOGY 3.2.1 Connecting Multiple Peer Groups - - Page Page Do the same on switch SWB3: 7. Use the show pnnipglelection command to verify that switches SWA3 and SWB3 have become Applicable). Logical entities do not have IP addresses. the PGLs of their respective peer groups. For example, on switch SWA3, enter the following: Note Notice that the IP address entry for the logical link between the LGNs is N/A (Not 3.2.2 Physical Connections Between Peer Groups Adding Higher-level Peer Groups Parent Group of Group A and B Page 3.3 MANAGING PARALLEL PNNI LINKS 3.3.1 Aggregation Tokens 3.3.2 PNNI Link Timing Page 4ROUTING 4.1 ADDITIONAL ROUTING PROTOCOLS 4.2 IISP ROUTES 4.2.1 IISP Routing Considerations IISP Routing Example One IISP Routing Example Two 4.2.2 IISP Link Timing 4.3 UNI ROUTES 4.3.1 UNI Link Timing 4.4 ROUTE METRICS 4.4.1 Administrative Weights 4.4.2 Creating Rout e Met ric s 1. Create the outgoing member of the metric pair: The newly created metric pair appears at the top of the list as metrics 1 and 2. 2. Create the incoming member of the metric pair: 3. Enter show pnnimetric to view the newly created metric pair: 4.5 IP ROUTING FOR MANAGEMENT Page 5 VIRTUAL PORTS AND STATIC CONNECTIONS 5.1 PVC CONNECTIONS 5.1.1 Point-to-Point PVCs 5.1.2 Point-to-Multipoint PVCs 4. Perform step 3 for ports 7a3 and 7a4. 2. Use show trafficdescriptor to obtain the new traffic descriptors index numbers. 3. Use add pvc to successively create point-to-multipoint PVCs for ports 7a2, 7a3, and 7a4. 5.1.3 Connecting to Local Switch Client Through a PVC 5.2 PVP CONNECTIONS 2. Use the set portconfig command to turn off signaling and ILMI and to specify bits for VPIs on port 7b1: 3. Use the add pvp command to create the pvp connection: 5.2.1 Connecting PVPs 5.3 VIRTUAL PORTS 5.3.1 Creating Virtual Ports Page 3. Use the PortNumber and MaxVpiBits parameters of the add port command to create the virtual ports. 1. Use the set portconfig command to turn off signaling and set the MaxVpiBits to 4: 2. Use the add port command to create the port and to specify the number of VPIs: 5.4 SOFT PVC AND PVP CONNECTIONS 5.4.2 Making Soft PVC and PVP Connections 5.4.3 Creating a soft PVC 1. Define a target ATM address to be used on the target switch. The target ATM address can be any 2. Use the add spvcaddress command on the target switch to specify the target port and ATM address. 3. Use the show spvcaddress command to see the soft PVC port and ATM address on the target switch: Page 5.4.4 Creating a Soft PVP Note Soft PVPs are supported only on the SmartSwitch 6500 ATM switch. 1. Use the set portconfig command on the target switch to increase the MaxVpiBits. Page Enter the show spvp command on the target switch to see the soft PVP and its current state: Page 6 TRAFFIC MANAGEMENT 6.1 TRAFFIC MANAGEMENT CAPABILITIES Page 6.1.2 Call Admission Control Policy Page 6.1.3 Queue Buffers 6.1.4 EFCI, EPD, and RM Cell Marking Page 7 FIRMWARE UPGRADES AND BOOTLINE COMMANDS 7.1 UPDATE FIRMWARE COMMANDS Unsuccessful Update 7.2 BOOTLINE COMMANDS 7.2.1 Accessing the Bootline Prompt 7.2.2 Bootline Commands Explanations Page 7.2.3 Upgrading Boot Load firmware - Changing the Default Boot Load Image 7.2.4 Upgrading POST Diagnostic firmware - 7.2.5 Upgrading Switch Operating firmware - 9. Start the ATM SmartSwitch by entering the go command. Page 8 ATM FILTERING AND CLOCKING 8.1 PORT ATM ADDRESS FILTERS 8.1.1 Creating ATM Address Filters 8.1.2 How ATM Address Filters Work 8.1.3 ATM Address Filter Example 1. Use the add atmfilter command to create filters on source and/or destination addresses 2. Use the add atmfilterset command to create a filter set that uses the filters domain1 and domain2 3. Use the create portfilterset command to assign the filter set to an incoming and outgoing port. Source and Destination Address Masks 8.2 PORT CLOCK CONFIGURATION 8.2.1 Network Clocking 9 TROUBLESHOOTING 9.1 TROUBLESHOOTING IP OVER ATM 9.2 TROUBLESHOOTING LAN EMULATION 9.3 TROUBLESHOOTING PNNI LINKS - 9.4 TROUBLESHOOTING CONGESTION 9.4.1 Diagnosing Congestion 9.4.2 Global Co ng esti o n 9.4.3 Port Congestion 9.5 EVENTS AND ALARMS 9.5.2 Viewing Events and Alarms 9.5.3 Deleting Events and Alarms 9.6 SAVING CORE DUMPS Page APPENDIX A AGENT SUPPORT A.1 MIB, SMI, MIB FILES AND INTERNET MIB HIERARCHY Figure A-1 Internet MIB hierarchy A.1.1 CSI ZeitNet Proprietary MIBs tt Label from the root to this point is 1.3.6.1.2.1 A.1.2 Relation Between Object Identifier and the Represented Value A.1.3 Supported protocols A.1.4 Supported SMI Formats A.1.5 CSI ZeitNet Proprietary MIB Groups Table A-1 CSI Zeitnet proprietary MIB groupings (Continued) Name Object Identifier Function Page A.2 MANAGING AN ATM SMARTSWITCH Page APPENDIX B TECHNICAL SUPPORT B.1 TELEPHONE ASSISTANCE B.2 FAX SERVICE B.3 ELECTRONIC SERVICES B.4 PLACING A SUPPORT CALL B.5 HARDWARE WARRANTY B.6 SOFTWARE WARRANTY B.7 REPAIR SERVICES INDEX A B C D E F G H I L M N O P Q R S T U V W