SmartSwitch ATM Switch User Guide 35 Industrial Way Rochester, NH 03866 USA (603) 332-9400 Part Number 04-0053-01 Rev.
NOTICE Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, firmware, and software described in this manual are subject to change without notice.
FCC CLASS A NOTICE This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note Caution This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules.
DECLARATION OF CONFORMITY ADDENDUM Application of Council Directive(s): 89/336/EEC 73/23/EEC Manufacturer’s Name: Cabletron Systems, Inc. Manufacturer’s Address: 35 Industrial Way P. O. Box 5005 Rochester, NH 03866 Product Name: SmartSwitch ATM switches European Representative Name: Mr. J.
SAFETY INFORMATION CLASS 1 LASER TRANSCEIVERS The connectors on I/O modules containing the part numbers IOM-29-4-MIX, IOM-29-4-IR, IOM-29-4-LR, IOM-39-1 and IOM-39-1-LR use Class 1 Laser transceivers. Read the following safety information before installing or operating one of these modules. The Class 1 Laser transceivers use an optical feedback loop to maintain Class 1 operation limits. This control loop eliminates the need for maintenance checks or adjustments.
FIBER OPTIC PROTECTIVE CAPS Warning READ BEFORE REMOVING FIBER OPTIC PROTECTIVE CAPS. Cable assemblies and MMF/SMF ports are shipped with protective caps to prevent contamination. To avoid contamination, replace port caps on all fiber optic devices when not in use. Cable assemblies and MMF/SMF ports that become contaminated may experience signal loss or difficulty inserting and removing cable assemblies from MMF/SMF ports. Contamination can be removed from cable assemblies by: 1.
REGULATORY COMPLIANCE SUMMARY SAFETY SmartSwitch ATM switches meet the safety requirements of UL 1950, CSA C22.2 No. 950, EN 60950, IEC 950, and 73/23/EEC. EMC SmartSwitch ATM switches meet the EMC requirements of FCC Part 15, EN 55022, CSA C108.8, VCCI V-3/93.01, EN 50082-1, and 89/336/EEC.
REVISION HISTORY Document Name: Document Part Number: Document Order Number: SmartSwitch ATM Switch User Guide 04-0053-01 Rev.
Table of Contents TABLE OF CONTENTS 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1 Contents of the User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2 SmartSwitch ATM Switch Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 2 IP Over ATM and LANE . . . . . . . . . . . . . . . . . .
Table of Contents 5 Virtual Ports and Static Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1 5.1 5.1.1 5.1.2 5.1.3 PVC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Point-to-Point PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Point-to-Multipoint PVCs . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 9.4 9.4.1 9.4.2 9.4.3 Troubleshooting Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Diagnosing Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Global Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Port Congestion . . . . . . . . . . . . .
Table of Contents xii SmartSwitch ATM User Guide
List of Figures LIST OF FIGURES Figure 2-1 Single PVP connection between clients and LANE services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Figure 2-2 Multiple PVP connection between clients and LANE services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 Figure 2-3 LNNI Redundant LECSs on same network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 Figure 2-4 LNNI call set up load sharing . . . . . . . . . . . .
List of Figures xiv SmartSwitch ATM User Guide
List of Tables LIST OF TABLES Table 2-1 ELAN Join Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Table 6-1 Traffic descriptor type number explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Table 7-1 Bootline commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Tables xvi SmartSwitch ATM User Guide
1 INTRODUCTION Welcome to the SmartSwitch ATM User Guide. This manual provides instructions and information about switch use, maintenance, and problem solving for all SmartSwitch ATM switches. These include • • • • SmartSwitch 2500 Workgroup and Backbone ATM switches SmartSwitch 6A000 ATM switch modules SmartSwitch 9A100 ATM switch modules SmartSwitch 6500 ATM switch Note 1.
SmartSwitch ATM Switch Differences 1.2 Introduction SMARTSWITCH ATM SWITCH DIFFERENCES Not all features are supported on all SmartSwitch ATM switches. The SmartSwitch 6500 has capabilities that are not supported by the other SmartSwitch ATM switches.
2 IP OVER ATM AND LANE This chapter describes working with the SmartSwitch ATM switch IP over ATM VLAN and emulated LAN capabilities. At the end of this chapter you will be able to use your SmartSwitch ATM switch to: • • Create an IP over ATM VLAN Create an emulated Ethernet LAN (LANE) 2.1 CREATING AN IP OVER ATM VLAN This section describes implementing IP over ATM on your SmartSwitch ATM switch.
Creating an IP over ATM VLAN 3. IP Over ATM and LANE Enter the show client command to make sure the client is operational and to obtain the 20-byte ATM address of the ARP server.
IP Over ATM and LANE Note 2.1.1 Creating an IP over ATM VLAN If configured devices fail to join the VLAN, see Chapter 4, "Routing." Section 4.3. Also, see Chapter 9, "Troubleshooting." Default ATM Addressing for IP over ATM ATM SmartSwitches provide a default format for ATM addresses used by IP over ATM. Note SmartSwitch 2500 family ATM switches and SmartSwitch 6500 switches use different methods for producing the default netprefix.
Creating an Emulated LAN 2.2 IP Over ATM and LANE CREATING AN EMULATED LAN This section describes the steps for implementing an Emulated LAN (ELAN) on your SmartSwitch ATM switch. Note If LANE services are to be reached through a virtual port on an ATM SmartSwitch, this switch must be a SmartSwitch 6500. Only the SmartSwitch 6500 supports logical multicasting. If LANE services are NOT reached through a virtual port, LANE services can reside on any ATM SmartSwitch.
IP Over ATM and LANE Creating an Emulated LAN Note When you create a client, it automatically finds the LECS address using ILMI. Note The command add laneclient always prompts you with a subnet mask that is appropriate for the IP address. However, if necessary, you can change the subnet mask to correspond to the strategy employed within your networks. As the local client joins the ELAN, the following messages are sent to the Event Log (see Chapter 9, "Troubleshooting." Section 9.
Creating an Emulated LAN IP Over ATM and LANE acquire the LECS address through ILMI or use the Well Known Address as the address for the LECS. For details on the ATM SmartSwitch automatic addressing scheme for LANE, see Section 2.2.1. 7. As each end device registers with the LES and BUS, messages are sent to the event log of the ATM SmartSwitch containing the LECS. You can check connectivity by pinging between end nodes. Note If configured devices fail to join the ELAN, see Chapter 4, "Routing.
IP Over ATM and LANE Creating an Emulated LAN The LECS address is constructed from: netprefix + CPU MAC address + selector byte of 01 For example netprefix = 39:00:00:00:00:00:00:00:00:00:14:41:89 chassis MAC address = 00:20:D4:14:41:80 then, default LECS address = 39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:80:01 The LES and BUS have the same ATM address.
Creating an Emulated LAN IP Over ATM and LANE The LECS address is constructed from: netprefix + chassis MAC address + selector byte of 01 For example netprefix = 39:00:00:00:00:00:00:00:00:00:A3:87:0B chassis MAC address = 00:00:1D:A3:87:0B then, default LECS address = 39:00:00:00:00:00:00:00:00:00:A3:87:0B:00:00:1D:A3:87:0B:01 The LES and BUS have the same ATM address.
IP Over ATM and LANE 2.2.3 Creating an Emulated LAN Switch Clients It is important to understand the concept of ATM SmartSwitch client connections. A switch client connection is actually a VLAN connection to the ATM SmartSwitch’s CPU (Here, we use the term VLAN to mean any type of “virtual LAN,” whether LANE or IP over ATM.). This CPU connection appears as if the switch is an end station on the virtual LAN. The ATM SmartSwitch uses local clients to connect itself to the VLANs that it supports.
Creating an Emulated LAN 2. Use the add leselan IP Over ATM and LANE command to create an LES on switch SW2: SW2 # add leselan ELANNumber(0) : 1 ELANName(ELAN001) : mis1 ConnectMethod(SVC) : ELANType(802.3) : Multipoint(YES) : MTU(1516) : ErrorLogEnable(NO) : MinimumTDEnable(NO) : ForwardPeakCellRate(0) : BackwardPeakCellRate(0) : Distribute(PROXY) : BUSATMAddress(39:00:00:00:00:00:00:00:00:00:14:41:80:00:20:D4:14:41:81:02): — Created by add buselan SW2 # 3.
IP Over ATM and LANE 6. Creating an Emulated LAN Use the show client command on SW1 to see that the client has reached all the distributed LANE services and has successfully joined ELAN mis1. SW1 # show client ClientNumber(ALL) : Client Type IP Address Server Type Server Conn Status ============================================================================== 1 LANE 90.1.1.
Creating an Emulated LAN Note IP Over ATM and LANE If the default ELAN (ELAN 0) has been deleted, the client is dropped. By using ELAN join policies, clients attempting to join LANE services can be assigned to specific ELANs. Table 2-1 lists the ELAN join policies that can be configured on an ATM SmartSwitch. Table 2-1 ELAN Join Policies Policy No. ELAN Join Policy 1 Best Effort Information Source Checked Default ELAN policy.
IP Over ATM and LANE Creating an Emulated LAN Use the add lecselanpolicy command to create ELAN join policies. The following is an example of creating an ELAN join policy based on the By Packet Size policy. SmartSwitch # add lecselanpolicy PolicyIndex() : 2 — Can be any value other than one (1) Type() : ? — Use ? to see possible types ELAN Policy Type (Values from 1 to 7 representing, in order, the policies BestEffort, byATMAddress, byMacAddress, byRouteDescriptor, byLANType, byPacketSize and byELANName).
Creating an Emulated LAN IP Over ATM and LANE In the following example, a client is identified by its ATM address and IP address, and associates it with ELAN number 1. SmartSwitch # add lecselanlec AtmAddress() MACAddress/RouteDesc() Layer3Address[IP]() ELANNumber(0) TLVSet() : 39:00:00:00:00:00:00:00:00:00:44:55:66:11:22:33:44:55:66:00 : — No MAC address is specified : 204.123.91.
IP Over ATM and LANE Creating an Emulated LAN Any Smar tSwitch AT M S w i t c h Single V i r t u a l Po r t Single V i r t u a l Po r t LANE S e r ve r (elan1) Single PVP ATM WAN SW1 Client Join Requests Single PVP SW2 Single P hy s i c a l Po r t Single P hy s i c a l Po r t Figure 2-1 Single PVP connection between clients and LANE services Physical BUS multicasting implies that the BUS performs multicasting according to physical ports.
Creating an Emulated LAN IP Over ATM and LANE Currently, the SmartSwitch 6500 is the only SmartSwitch ATM switch that supports logical multicasting. For this reason, if you are connecting to LANE services across an ATM WAN using multiple PVPs and if client join requests for the same ELAN are received over different PVPs, you must use a SmartSwitch 6500 as the LANE services switch.
IP Over ATM and LANE Creating an Emulated LAN LECS 0 LECS 1 Figure 2-3 LNNI Redundant LECSs on same network LANE Load Sharing Running multiple LECSs, alleviates the bottleneck of a single LECS supporting all clients on all ELANs. Under LNNI, a client requesting a call setup is serviced by the LECS, LES and BUS on the switch that it’s directly connected to, leaving other SmartSwitch ATM switches free to service the call setups from their directly attached clients (see Figure 2-4).
Creating an Emulated LAN IP Over ATM and LANE SW1 1 CLIENT Client attempts ELAN join through switch SW1. LES/BUS (LNNI) SW1 2 SW2 LECS (LNNI) SW2 Netprefix of SW1? CLIENT 3 LES/BUS (LNNI) LECS (LNNI) SW1 SW2 LECS checks SW1's netprefix. Is it known to contain an LES/BUS, and is it participating in LNNI? If yes, tell client to use SW1 as its LES/BUS. CLIENT Client now uses SW1 for its call setups.
IP Over ATM and LANE Creating an Emulated LAN Client A Client D Client B LES/BUS LES/BUS LECS 0 LECS 1 Logical full mesh among LES/BUS switches LES/BUS Client C Figure 2-5 How LNNI handles ELAN join requests Setting up LNNI LECs The procedure for setting up LNNI on a SmartSwitch ATM switch is performed by executing the following basic steps: • • • • Shut down all LANE services — LECS, LES and BUS Configure LNNI Enable LNNI Start LANE services The following is an example of enabling LNNI on a ne
Creating an Emulated LAN 1. IP Over ATM and LANE On both SW1 and SW2, enter the stop lecs command to make sure each LECS is down SW1 # stop lecs Confirm(y/n)?:y NOTICE - 'LECS' ***** LECS shutdown ***** SW1 # 2. On both SW1 and SW2, enter the stop les command to stop each switch’s LES and BUS SW1 # stop les STOPPING LES/BUS Confirm(y/n)?:y NOTICE - 'ZLESSRV' ***** LES shutdown ***** SW1 # 3. On both SW1 and SW2, enter the set lnniinfo command to assign a number to each switch’s LECS.
IP Over ATM and LANE 6. Creating an Emulated LAN On SW1, create an ELAN; in this example, we create elan1: SW1 # add elan ELANNumber(0) ELANName(ELAN001) ConnectMethod(SVC) ELANType(802.3) Multipoint(YES) MTU(1516) ErrorLogEnable(NO) MinimumTDEnable(NO) Distribute(PROXY) : 1 : elan1 : : : : : : : SW1 # Similarly, create the same ELAN (elan1) on SW2: SW2 # add elan ELANNumber(0) ELANName(ELAN001) ConnectMethod(SVC) ELANType(802.
Creating an Emulated LAN Similarly, enter the show IP Over ATM and LANE elan 1 command on SW2 to obtain SW2’s LECS address SW2 # show elan 1 ELAN 1 ============================================================================== ELAN Number : 1 LECS Address : 39:00:00:00:00:00:00:00:00:00:BF:BA:26:00:00:1D:BF:BA:26:01 — LECS address on SW2 LES Address : 39:00:00:00:00:00:00:00:00:00:BF:BA:26:00:00:1D:BF:BA:26:03 ELAN Name : elan1 ELAN Type : 802.
IP Over ATM and LANE Creating an Emulated LAN connected by a logical full-mesh topology. In this case, the term “logical” means only that all LNNI switches participating within a particular domain should be able to reach each other. Typically, a full-mesh topology is satisfied by PNNI, and does not require all LES/BUS switches to be directly connected. The following is an example of configuring a distributed LNNI LES/BUS on SW3.
Creating an Emulated LAN 6. IP Over ATM and LANE On switch SW3, use the set Synchronization Protocol). SW3 # set lnnistatus LNNIStatus(Disabled) SCSPStatus(Disabled) SW3 # Note 7. lnnistatus command to enable LNNI and SCSP (Server Cache : enable : enable SCSP does not have to be enabled for an LES to take part in LNNI. However, without SCSP enabled, ARP server information is not shared.
IP Over ATM and LANE Creating an Emulated LAN To see a list of servers (LES/BUS or SMS servers) known to a particular LNNI LECS, enter the show command on a switch running an LNNI LECS: SW1 # show lecsserverlist ELANNumber(ALL) lecsserverlist : 1 LES/SMS servers known for ELAN 1 ============================================================================== ATM Address : Learned From (LECS): Type : Alive Time (secs) : Locally Attached : Config Direct VCC : Server ID : LECID Range : 39:00:00:00:00:00:00
Creating an Emulated LAN 2-26 SmartSwitch ATM User Guide IP Over ATM and LANE
3 PNNI ROUTING All ATM SmartSwitches use PNNI version 1.0 as their default routing protocol. PNNI provides automatic and dynamic connectivity among all PNNI nodes within the same peer group. By configuring multi-level PNNI topologies and peer group leaders, full hierarchical PNNI routing can be established with connectivity between different peer groups. Note 3.1 For a complete explanation of all PNNI related commands, see the SmartSwitch ATM Reference Manual.
PNNI Node Addressing Note PNNI Routing If the node does not have a child node, and the node is also at the lowest level, the second byte is assigned the constant value A0 (160 decimal). For example, for a node at the lowest level (80), the level and address length bytes are 50 (80 in hexadecimal) and a0 (160 in hexadecimal), respectively.
PNNI Routing Use the show Multi-level PNNI Topology pnninode command to view ATM SmartSwitch PNNI node parameters.
Multi-level PNNI Topology 1. PNNI Routing Physically connect switches SWA1, SWA2, and SWA3. Similarly, physically connect switches SWB1, SWB2, and SWB3 (see Figure 3-1). Peer Group A Peer Group B Peer Group Leader Peer Group Leader SWA3 SWB3 SWA2 SWB2 SWA1 SWB1 Peer Group A = 50:39:00:00:00:00:00:00:00:00:01:00:00:00 Peer Group B = 50:39:00:00:00:00:00:00:00:00:00:00:00:00 Figure 3-1 Physical connectivity for multi-peer group example 2.
PNNI Routing Multi-level PNNI Topology Note 3. The first byte of the peer group ID indicates the peer group’s level. It also indicates the number of significant bits used in the peer group ID. For example, if the level indicator is 50 (80 decimal), then 80 bits / 8 = 10 bytes; and only 10 of the 13 bytes are significant (39:00:00:00:00:00:00:00:00:00). If you create a new peer group ID, make sure that the bytes you change are within the range of significant bytes for the peer group’s level.
Multi-level PNNI Topology PNNI Routing Do the same on switch SWB3: SWB3 # set pnnipglelection NodeIndex(1) LeadershipPriority(0) ParentNodeIndex(0) InitTime(15) OverrideDelay(30) ReElectTime(15) : : 205 : 2 : : : — Highest priority in election process — Node 2 will represent the peer group B in the parent group SWB3 # 7. Use the show pnnipglelection command to verify that switches SWA3 and SWB3 have become the PGLs of their respective peer groups.
PNNI Routing Multi-level PNNI Topology Connectivity is now established between the two peer groups. For example, if LANE services are running on a switch within peer group A, LANE clients can exist in group B. The clients in group B will traverse the link between the two groups, find the LANE server in group A, and join the ELAN. Figure 3-2 shows a logical representation of the topology created in the example.
Multi-level PNNI Topology PNNI Routing 2. Add a third node (at level 64) to either switch SWA3 or SWB3. 3. Use the set pnnipglelection command to designate the switch’s second node (not third) as the PGL for the parent peer group, and specify the third node as the parent node of the second. 4. Perform steps 2 and 3 for switches with the same role in the other level 72 parent groups.
PNNI Routing 3.3 Managing Parallel PNNI Links MANAGING PARALLEL PNNI LINKS ATM SmartSwitches can be connected by more than one physical link. PNNI treats these connections as parallel physical links. By default, parallel links are considered to have equal capabilities with regard to call set ups. For example, if a second link is added between switch SWA3 and switch SWB3 (from the example above), this parallel link can be seen using the show pnnilink command.
Managing Parallel PNNI Links PNNI Routing Use the set pnniinterface command to set the administrative weight of a physical link originating from a particular port.
PNNI Routing Managing Parallel PNNI Links The physical connection from switch SWA2 to switch SWB2 is now advertised as a second logical link within the parent peer group (see Figure 3-4). Second Logical Link First Logical link Level 72 First Physical Link SWA1 SWA3 SWB3 SWB1 SWA2 SWB2 Second Physical Link Aggregation Token = 0 Aggregation Token = 1 Figure 3-4 Aggregation token values and parallel links 3.3.
Managing Parallel PNNI Links PNNI Routing However, certain time-sensitive implementations of PNNI may require that link fail occur either immediately or after a period of time longer than three seconds. Use the set linkmonitortimeout command to control the time required for the SmartSwitch ATM switch to assume a link has failed. For example, two SmartSwitch ATM switches are connected with parallel PNNI links.
4 ROUTING 4.1 ADDITIONAL ROUTING PROTOCOLS Along with PNNI, all ATM SmartSwitches support additional ATM routing protocols: • • IISP — Use to connect with devices that do not support PNNI UNI — Use to connect end stations (also to connect devices whose implementation of ILMI is incompatible with the ATM SmartSwitch) Note 4.2 Both IISP and UNI routes are created and modified using the ATMRoute command. The proper route type is determined by the ATM SmartSwitch through interface signaling information.
IISP Routes 5. Routing Note For IISP routes, always set the Type parameter of the add atmroute command to external. This indicates that the route is external to the PNNI domain. Note The add atmroute command allows you to specify a set of metrics to be used with the route. Metrics are created using the add pnnimetric command, and are assigned to routes by metric tag numbers.
Routing IISP Routes IISP Routing Example One In Figure 4-1 Switch A is an IISP device connected to the PNNI domain through Switch B. Switch A contains an LEC, which is a member of an ELAN whose LECS is on Switch C (within the PNNI domain). If the LEC on Switch A is to make contact with the LECS on Switch C, Switch A must contain an IISP route directly to switch C. Furthermore, Switch B must contain a route to switch A over the physical link that connects the two switches.
IISP Routes Routing Figure 4-2 Routes needed for a second IISP switch 4.2.2 IISP Link Timing By default, if an IISP link loses connectivity, the link fails after three (3) seconds. This short amount of time is designed as a buffer in case of minor latency. By waiting three seconds before releasing resources and tearing down the connection, a minor latency occurrence (less than three seconds) will not bring down the route.
Routing 4.3 UNI Routes UNI ROUTES Use the add atmroute command to create UNI routes. For example, connect an end station adapter (with MAC address 00:11:22:33:44:55) to port 7A2 of a SmartSwitch 6500. If the adapter does not support ILMI or its ILMI is incompatible with the SmartSwitch 6500, you must create a static UNI route between the adapter and port 7A2 of the SmartSwitch 6500.
UNI Routes 4. Routing Enter the show atmroute command to check that the UNI route was added. SmartSwitch # show atmroute AddressNumber(ALL) : No.
Routing Route Metrics Caution 4.4 Remember that while some special network configurations may require the TimeoutValue to be zero (0), setting TimeoutValue to less than three seconds may cause a UNI route to fail unnecessarily. For this reason, care should be taken when setting the TimeoutValue to less than three seconds. ROUTE METRICS Route metrics are assigned to routes using a metric tag (one of the input parameters for add atmroute).
Route Metrics 1.
Routing IP Routing for Management Once the metric is created, we can specify its metric tag number within the definition of a route. In this example, an IISP route is being created: SmartSwitch # add atmroute PortNumber() AtmAddress() PrefixLength(104) Index(0) Type(Internal) Scope(0) MetricsTag(0) Advertising(NO) SmartSwitch # 4.
IP Routing for Management Routing To see the route, enter the show route command on SW2 SmartSwitch # show route ROUTE NET TABLE destination gateway flags Refcnt Use Interface -----------------------------------------------------------------------0.0.0.0 0.0.0.0 1 0 0 zn0 90.1.1.0 90.1.1.33 1 0 1688 zn1 128.205.99.0 90.1.1.
5 VIRTUAL PORTS AND STATIC CONNECTIONS 5.1 PVC CONNECTIONS ATM SmartSwitches support Permanent Virtual Circuits (PVCs), both point-to-point and point-to-multipoint. Use PVCs to connect devices (that do not support SVCs) to a switch’s local client. Also, use PVCs to make connections through an ATM SmartSwitch between devices that support only PVCs. Use point-to-point PVCs to connect one end node to another for two-way communication.
PVC Connections Virtual Ports and Static Connections For this example, we specify CBR as the traffic type, then take the remaining defaults. Enter the show trafficdescriptor command to obtain the index number of the new traffic descriptor. In this example, the index number is two (2).
Virtual Ports and Static Connections PVC Connections Example: Create a point-to-multipoint connection between a broadcasting workstation on port 7a1 and three other workstations connected to ports 7a2, 7a3, and 7a4. 1. Use add trafficdescriptor to create two new traffic descriptors, one for the forward direction, the other for the backward direction. For this example, for the forward traffic descriptor, we select UBR and accept the defaults.
PVC Connections Virtual Ports and Static Connections 5. Connect the workstations to their respective ports. 6. Configure the workstations for the same subnet and VPCI/VCI pair = 0/101. The broadcasting workstation on port 7a1 can send traffic to the receiving workstations on ports 7a2, 7a3, and 7a4. 5.1.3 Connecting to Local Switch Client Through a PVC All PVC connections to an ATM SmartSwitch local client use the CPU port.
Virtual Ports and Static Connections 5.2 PVP Connections PVP CONNECTIONS Note PVP connections are supported only on the SmartSwitch 6500. However, because all ATM SmartSwitches support virtual ports, PVPs can be terminated using any SmartSwitch ATM switch. The SmartSwitch 6500 supports the creation of Permanent Virtual Path (PVP) connections. The basic process for creating a PVP is as follows: • • Create a traffic descriptor for the PVP that meets its bandwidth and service category requirements.
PVP Connections 2.
Virtual Ports and Static Connections 5.2.1 Virtual Ports Connecting PVPs PVPs are physically connected to other devices in the following two ways: • Physically connecting the PVP port to another PVP switch When connecting to another PVP switch, the VPI numbers assigned to the ports carrying the PVP on each switch must match.
Virtual Ports 5.3.1 Virtual Ports and Static Connections Creating Virtual Ports Virtual ports are created on physical ports by first allocating a range of Virtual Path Identifiers (VPIs), and then distributing the VPIs among the virtual ports. The number of VPIs used depends on the number of virtual ports needed and the range of VPIs controlled by each virtual port. When creating virtual ports, it’s important to remember that the virtual port number represents the Base VPI used by the virtual port.
Virtual Ports and Static Connections Note Virtual Ports For PNNI, the number of VPIs used by each virtual port should be one (1). For virtual UNI, the number of VPIs used by each virtual port should correspond to the number of VPIs on the user side of the UNI connection (For information on virtual UNI, refer to the ATM Forum specification for ILMI 4.0.). The following is a practical, step-by-step example of creating a virtual port on physical port 7A1 that controls a single VPI. 1.
Virtual Ports 3. Virtual Ports and Static Connections Use the PortNumber and MaxVpiBits parameters of the add ports. SmartSwitch # add port PortNumber() PortAdminStatus(up) IlmiAdminStatus(up) SigType(autoConfig) SigRole(other) InterfaceType(private) MaxVpiBits(0) MaxVciBits(10) MaxSvcVpci(1) MinSvcVci(32) MaxVccs(2048) TrafficDescriptorIndex() port command to create the virtual : 7a1.1 — The .
Virtual Ports and Static Connections Soft PVC and PVP Connections Things To Watch Out For When Creating Virtual Ports • Make certain that the virtual port number (Base VPI) plus the VPIs designated by MaxVpiBits does not exceed the Available VPIs as specified by MaxVpiBits in the set portconfig command. • If you create more than one virtual port on a particular physical port, make certain that you do not run out of Available VPIs as specified by MaxVpiBits in the set portconfig command.
Soft PVC and PVP Connections 5.4.2 Virtual Ports and Static Connections Making Soft PVC and PVP Connections Creating soft PVC and PVP connections consists of the following general steps: • • • Configure a target port and ATM target address on the target switch Create a traffic descriptor to be used by the connection Add a soft PVC (or PVP) on the source switch that specifies the port on the target switch as its end point 5.4.
Virtual Ports and Static Connections 1. Soft PVC and PVP Connections Define a target ATM address to be used on the target switch. The target ATM address can be any address that is either eight (8) or twenty (20) bytes long and must not be identical to any address currently listed in the ATM routing table. Use the show atmroute command to check which addresses are currently defined.
Soft PVC and PVP Connections 5.
Virtual Ports and Static Connections 5.4.4 Soft PVC and PVP Connections Creating a Soft PVP Note Soft PVPs are supported only on the SmartSwitch 6500 ATM switch. The following is an example of creating a soft PVP between port 7a1 on the source switch and port 6b3 on the target switch. 1. Use the set portconfig command on the target switch to increase the MaxVpiBits.
Soft PVC and PVP Connections 3. Use the add Virtual Ports and Static Connections spvcaddress command on the target switch to specify the target port and ATM address. SmartSwitch # add spvcaddress PortNumber() AtmAddress() : 6b3 — Port on target switch : 22:22:22:22:22:22:22:22:22:22:22:22:22:22:22:22:22:22:22:22 Added SPVC Address successfully. SmartSwitch # Note 4. Use the show Both soft PVCs and Soft PVPs use the add spvcaddress command to specify the target switch’s target ATM address.
Virtual Ports and Static Connections Enter the show spvp Soft PVC and PVP Connections command on the target switch to see the soft PVP and its current state: SmartSwitch # show spvp PortNumber(ALL) SourceVpi(0) :7a1 : 3 ====================================================== Port Src VPI Leaf Ref Operation Status ====================================================== 7A1 0 1 connected Total number of SPVCs = 1 SmartSwitch # SmartSwitch ATM User Guide 5-17
Soft PVC and PVP Connections 5-18 SmartSwitch ATM User Guide Virtual Ports and Static Connections
6 TRAFFIC MANAGEMENT 6.1 TRAFFIC MANAGEMENT CAPABILITIES ATM SmartSwitches have extensive abilities for managing traffic flow. Traffic management includes all operations performed by the ATM SmartSwitch that ensures optimum switch throughput, where throughput is based on rate of packet loss, available bandwidth, and traffic processing overhead. Under most conditions, an ATM SmartSwitch can efficiently and automatically manage switch traffic.
Traffic Management Capabilities Traffic Management ATM SmartSwitch user data cells are classified according to the state of a cell loss priority (CLP) bit in the header of each cell. A CLP 1 cell has a lower priority than a CLP 0 cell and is discarded first. Source traffic descriptors can specify CLP 0 cell traffic, CLP 1 cell traffic, or the aggregate CLP 0+1 traffic. Use the trafficdescriptor commands to view, create, and delete traffic descriptors.
Traffic Management Traffic Management Capabilities A user-defined PVC must have user-defined traffic descriptors. For instance, if a video link over a PVC requires a peak cell rate of 8000 kb/s, create a traffic descriptor for CBR traffic that specifies 8000 as the peak cell rate. SmartSwitch # add trafficdescriptor TrafficType(UBR) TrafficDescriptorType(2) PCRCLP01(100) QOSCLASS(1) AalType(5) : cbr :3 :8000 : : SmartSwitch # Each traffic descriptor is identified by a unique index number.
Traffic Management Capabilities Use the command show service.
Traffic Management 6.1.3 Traffic Management Capabilities Queue Buffers ATM SmartSwitches perform buffering using a shared-memory architecture. Buffer space is divided into queues for each class of service. In turn, ports are allocated a portion of each of the service class queues. This allocation is controlled on a per-port basis by the porttrafficcongestion commands. Quality of service is defined on an end-to-end basis in terms of cell loss ratio, cell transfer delay, and cell delay variation.
Traffic Management Capabilities • • Traffic Management Queue 4 — Available Bit Rate (ABR) Queue 5 — Unspecified Bit Rate (UBR) If calls of a particular service class are being dropped on a particular port, use the set command to raise the port’s queue Min threshold.
Traffic Management 6.1.4 Traffic Management Capabilities EFCI, EPD, and RM Cell Marking To control switch congestion, ATM SmartSwitches implement standard resource management cell (RM-cell) marking, explicit forward congestion indicator cell marking (with backward RM cell marking), and early packet discard (EPD). These congestion control schemes are triggered when the number of cells within shared memory reaches user-definable thresholds.
Traffic Management Capabilities 6-8 SmartSwitch ATM User Guide Traffic Management
7 FIRMWARE UPGRADES AND BOOTLINE COMMANDS 7.1 UPDATE FIRMWARE COMMANDS You can upgrade the operating firmware of an ATM SmartSwitch while the switch is running its current firmware. This procedure is known as a hot upgrade and is accomplished by the update firmware command. When an ATM SmartSwitch is started (or rebooted), it copies its operating firmware from flash RAM to the CPU’s program memory. When a hot upgrade is performed, the image in flash RAM is erased and replaced with the new firmware image.
Bootline Commands If possible, determine why the update • • Firmware Upgrades and Bootline Commands firmware command failed. Possible causes are: The ATM SmartSwitch lost network connectivity before it finished its download The wrong file or a corrupt file was downloaded into memory If you can correct the problem, enter the update firmware command to continue with the upgrade process.
Firmware Upgrades and Bootline Commands • • • Bootline Commands Load switch firmware upgrades Set whether power-on system tests (POST) are automatically run at start-up Change the master/slave relationship for TSM/CPUs and CSMs on SmartSwitch 6500s 7.2.1 Accessing the Bootline Prompt Bootline commands are executed from the bootline prompt. The bootline prompt is not part of the switch console, and is accessible only after a reboot and before the switch firmware is loaded.
Bootline Commands 7.2.2 Firmware Upgrades and Bootline Commands Bootline Commands Explanations The following table describes the commands available from the bootline prompt, their use, and their associated parameters. Table 7-1 Bootline commands Command Action Parameters chpi Change default boot load image: chpi 0 = set boot load image 0 as default Sets one of two images of the boot load firmware as the default. Default boot load image is executed at start-up.
Firmware Upgrades and Bootline Commands Table 7-1 Bootline Commands Bootline commands (Continued) Command Action Parameters scsm Switch to the redundant CSM: none Tells the SmartSwitch 6500 to transfer CSM mastership to the slave CSM. swms Switches CPU mastership to other TSM/CPU: none Changes the slave TSM/CPU to the master.
Bootline Commands 7.2.3 Firmware Upgrades and Bootline Commands Upgrading Boot Load firmware Two images of the boot load firmware reside in flash RAM. The two images are identified as boot load image 0 and boot load image 1. Both boot load images can be upgraded by using a TFTP/Bootp server. However, an upgrade is always written over the boot load image that is not currently running. This insures that if a boot load upgrade fails, there is still one good boot load image to fall back on.
Firmware Upgrades and Bootline Commands Bootline Commands Changing the Default Boot Load Image Continuing with the example above, perform the following steps to set boot load image 0 back to being the default. 1. Reboot the ATM SmartSwitch. 2. When the following message appears “Preparing to run Default Primary Image: 1 Enter 0 or 1 to override and force one of these primary image sectors to run:” press the zero (0) key. The ATM SmartSwitch loads boot load image 0. 3.
Bootline Commands Firmware Upgrades and Bootline Commands ............................................................................ ............................................................................ ............................................................................ ....................................... Validity checks of POST software Downloaded file... All Validity checks OK Programming downloaded image into POST Software section, please wait...
Firmware Upgrades and Bootline Commands Bootline Commands ................................................... Validity checks of the Switch Software Downloaded file... All Validity checks OK Programming downloaded image into Switch Software section, please wait... New Switch Software programmed successfully => 9. Start the ATM SmartSwitch by entering the go command.
Bootline Commands 7-10 SmartSwitch ATM User Guide Firmware Upgrades and Bootline Commands
8 ATM FILTERING AND CLOCKING 8.1 PORT ATM ADDRESS FILTERS SmartSwitch ATM switches support ATM address filtering. Address filtering provides a way to control call setups through SVCs. Filtering is a process of stating whether entities with particular ATM source or destination addresses (or ranges of addresses) are admitted or denied access through a port or set of ports. Note 8.1.1 Address filters can be created that include only a source or destination address.
Port ATM Address Filters 8.1.3 ATM Filtering and Clocking ATM Address Filter Example The following is an example of creating a filter, a filter set, and assigning the filter set to an incoming and outgoing port. 1.
ATM Filtering and Clocking Port Clock Configuration By setting the mask appropriately, a filter could either admit or deny access to all but a few addresses within a range. For example, if a filter’s mask is set to 00:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF, the filter disregards the first byte when comparing addresses.
Port Clock Configuration ATM Filtering and Clocking By default, the clock mode for all SmartSwitch 6500 ports is local. Use the set portclockmode command to change a ports clocking source. For example, the following sets port 5a3 into loopback mode. SmartSwitch # set portclockmode PortNumber(ALL) PortClkMode(local) : 5a3 : loop SmartSwitch # Note 8.2.1 Never configure two connecting port to both be in loopback mode.
9 TROUBLESHOOTING This chapter provides basic troubleshooting for diagnosing and fixing problems with VLAN, emulated LANs, PNNI links, and ATM traffic congestion. 9.1 TROUBLESHOOTING IP OVER ATM You have configured an IP over ATM VLAN, but your network applications are not working. Use these questions and tests to help determine the cause of the problem. 1. Check for connectivity: Try pinging between end nodes and from the ATM SmartSwitch (using ping) to its end nodes.
Troubleshooting LAN Emulation 5. Troubleshooting If working through these questions does not solve the problem, contact Cabletron Systems Customer Service. (see Appendix B, "Technical Support"). 9.2 TROUBLESHOOTING LAN EMULATION You have configured an Emulated LAN and your network applications are not working. Use these questions and tests to help determine the cause of the problem. 1. Check for connectivity. Try pinging between end nodes. Ping from the ATM SmartSwitch (using ping) to its end nodes.
Troubleshooting - Troubleshooting PNNI Links Do devices begin to register with the LES and BUS once multi-point signaling is turned off? 7. Check whether BUS is connected. • Use show busclient to check whether devices are registered with the BUS. If clients are registered, check end node configuration. If not registered, check multi-point signaling. • Use set • to turn off multi-point signaling on a per-ELAN basis.
Troubleshooting Congestion Troubleshooting 2. Make certain that the switches in the other peer group support multi-level PGLs and border nodes. If not, the other switches must be placed in the same peer group as the ATM SmartSwitch if you want them to connect. 3. Are the switches within the peer groups communicating with each other? If not, fix the connectivity problem within the peer group (see Section 9.3.1). 4.
Troubleshooting Troubleshooting Congestion Table 9-1 Settings for Class of Service Queues (Continued) Service Class Recommended Settings rt-VBR Bandwidth* utilization less than 20%: Min = 16, Max = 1024 rt-VBR Bandwidth* utilization greater than 20%: Min = 128, Max = 4096 Nrt-VBR Min = 256, Max = 4096 UBR Min = 256, Max = 8192 ABR Min = 256, Max = 8192 *Use the show portconfig command to view bandwidth utilization 3. Has the congestion subsided? • • If yes, you are done. 4.
Events and Alarms Troubleshooting • • If yes, the switch is improperly set up. Check the switch configuration. 2. Enter the show cacinfo command for this port. Note the bandwidth allocated for each Quality of Service on this port. 3. For each class of service, enter the set porttrafficcongestion command. Set the MaxValue to the value recommended in Table 9-1, “Setting for Class of Service Queues.” 4. Have you performed step 3 for every class of service for this port? • • If no, go to step 3. 5.
Troubleshooting Events and Alarms Both events and alarms are stored within circular memory buffers. When the buffers become full, older events and alarms are overwritten by newer entries. Both events and alarms are stored in shared RAM. However, the 40 most recent alarms are also stored in flash RAM. Storing these 40 alarms in flash RAM makes them persistent between reboots of the ATM SmartSwitch, and provides information about the state of the switch prior to reboot. Note 9.5.
Events and Alarms Note Use the show alarms Troubleshooting Depending on the activity of your ATM SmartSwitch, the appearance of events on the ATM SmartSwitch may be too frequent to use the console comfortably. It is recommended that you turn on the automatic display of events only when troubleshooting. command to view a list of the currently logged alarms.
Troubleshooting 9.6 Saving Core Dumps SAVING CORE DUMPS The ATM SmartSwitch core dump feature allows you to specify a local Ethernet host where, in the event of a system failure, the ATM SmartSwitch sends a copy of its memory. ATM SmartSwitch system memory is saved to two files, one containing CPU memory (core_cpu), the other common memory (core_cmn). These files can then be sent to Cabletron customer support for analysis.
Saving Core Dumps Troubleshooting If a system failure occurs while the core dump feature is enabled, the ATM SmartSwitch console appears similar to the example below. The ATM SmartSwitch then begins sending images of its memory to the core dump files on the TFTP server. Illegal access. Bus Error.
APPENDIX A AGENT SUPPORT This appendix briefly describes the support provided for managing an ATM SmartSwitch using Simple Network Management Protocol (SNMP). A.1 MIB, SMI, MIB FILES AND INTERNET MIB HIERARCHY A MIB (Management Information Base) is the term used to represent a virtual store of management data on a device. Given the structure of management data, it can be operated upon (retrieved, created or modified) using the SNMP protocol.
MIB, SMI, MIB Files and Internet MIB Hierarchy Agent Support t root CCITT 0 ISO 1 joint ISO/CCITT 2 org 3 DOD 6 internet 1 directory 1 mgmt 2 experimental 3 private 4 MIB 1 Label from the root to this point is 1.3.6.1.2.1 Figure A-1 Internet MIB hierarchy A.1.1 CSI ZeitNet Proprietary MIBs The location of some of ZeitNet proprietary MIBs in the Internet hierarchy is shown in Figure A-2. All nodes starting with “zn” represent Zeitnet objects.
Agent Support MIB, SMI, MIB Files and Internet MIB Hierarchy . internet 1 Label from the root to this point is 1.3.6.1 atomMIB 37 Private 4 enterprise 1 atmForum 353 CTRON 52 znCommonMIB 199 CSI ZeitNet starts here znSwitchObjedcts 3333 ZeitNet 1295 znProducts 1 znCommonObjs 300 znManagedObjects 2 znTrapObjs 301 znAdminPolicyVal 202 znIpAtm 200 Figure A-2 CSI ZeitNet Private MIBs In Figure A-2, the ZeitNet proprietary group is identified by 1.3.6.1.4.1.
MIB, SMI, MIB Files and Internet MIB Hierarchy Agent Support : Label from the root to this point is 1.3.6.1.4.1.1295 znManagedObjects 2 znIpATM (1295.2.200) znCommon (1295.2.300) znTrap (1295.2.301) znIisp (1295.2.3333) znLec (1295.2.3333.9.1.1) znLecDDCount (.1.1) Figure A-3 Cabletron ATM SmartSwitch object identifier example A.1.3 Supported protocols All ATM SmartSwitches support Simple Network Management Protocol (SNMP). Both the SNMPv1 and SNMPv2c formats of the protocol are supported. A.1.
Agent Support MIB, SMI, MIB Files and Internet MIB Hierarchy Table A-1 Name CSI Zeitnet proprietary MIB groupings (Continued) Object Identifier Function znIpAtmServer 1.3.6.1.4.1.1295.2.200.2 IP ATM Server Services znCommonObjs 1.3.6.1.4.1.1295.2.300 Zeitnet Specific Information znTrapObjs 1.3.6.1.4.1.1295.2.301 ZeitNet Traps znSwitchObjects 1.3.6.1.4.1.1295.2.3333 Switch/hardware specific information znSystem 1.3.6.1.4.1.1295.2.3333.
MIB, SMI, MIB Files and Internet MIB Hierarchy A.1.6 Agent Support ATM SmartSwitch MIB Support The ATM SmartSwitch is shipped with the following MIBs: • • • • • • • • • • MIB II (RFC 1213) Interface Table MIB (RFC 1573) AToM MIB (RFC 1695) AToM2 MIB LANE MIB (ATM Forum) ILMI 4.0 MIB (ATM Forum) PNNI MIB (ATM Forum) IP over ATM MIB ATM SmartSwitch MIBs (proprietary) Soft PVC MIB Note A.1.7 Along with the MIBs, the CD-ROM also contains a README file and the release note.
Agent Support • • Managing an ATM SmartSwitch p2mpRoot p2mpLeaf atmVplReceiveTrafficDescrIndex — Doesn’t accept ABR traffic descriptor atmVplTransmitTrafficDescrIndex — Doesn’t accept ABR traffic descriptor Not Supported The following MIB objects are not supported. If used, these objects return either the value zero or the message, “Not supported.
Managing an ATM SmartSwitch • • • • Community: Sets the community strings for the ATM SmartSwitch TrapCommunity: Specifies the NMS to which traps are sent MyNMAddr: Specifies the IP address through which the switch is managed TrustedNMS:Specifies the IP address of the NMS allowed to perform the following commands: A.2.
APPENDIX B TECHNICAL SUPPORT This appendix tells you what to do if you need technical support for your ATM SmartSwitch. Cabletron offers several support and service programs that provide high-quality support to our customers. For technical support, first contact your place of purchase. If you need additional assistance, contact Cabletron Systems, Inc. There are several easy ways to reach Cabletron Customer Support and Service. B.
Hardware Warranty • Technical Support Hardware model number, software version, and switch configuration (that is, what part types are in what slots) B.5 HARDWARE WARRANTY Cabletron warrants its products against defects in the physical product for one year from the date of receipt by the end user (as shown by Proof of Purchase). A product that is determined to be defective should be returned to the place of purchase.
INDEX A accessing the boot load prompt ................ 7-3 address filters ........................................... 8-1 example.............................................. 8-2 address masking ....................................... 8-2 administrative weight ............................... 3-9 agent support ........................................... A-1 aggregation tokens ................................. 3-10 alarm categories ....................................... 9-7 alarms ........................
Index add spvcaddress ......................5-13, 5-16 add spvp ........................................... 5-16 add trafficdescriptor........................... 6-3 create portfilterset .............................. 8-2 reboot ................................................. 7-2 set caceqbwallocscheme .................... 6-4 set cacserviceclassbw......................... 6-4 set coredump...................................... 9-9 set eventdisplay..................................
Index identifying clients ............................ 2-14 index number ................................... 2-13 priority value.................................... 2-13 ELANs across multiple switches ............. 2-8 Emulated LAN ......................................... 2-4 enabling EFCI marking ............................ 6-7 enabling RM cell marking........................ 6-7 EPD .......................................................... 6-7 EPD threshold ..........................................
Index LES/BUS connectivity...................................... 2-19 LES/BUS load sharing ...........................2-17 LGN.......................................................... 3-3 link timing ............................... 3-11, 4-4, 4-6 LNNI ......................................................2-16 configuring....................................... 2-19 distributed LES/BUS servers........... 2-22 full-mesh topology...........................2-19 LANE service redundancy...............
Index physical multicasting.............................. 2-14 PNN managing parallel links...................... 3-9 PNNI adding higher-level peer groups ........ 3-7 adding nodes ...................................... 3-5 administrative weight ........................ 3-9 aggregation tokens........................... 3-10 class of service................................... 3-9 connecting multiple peer groups........ 3-3 controlling fail-over timing ............. 3-12 default node ATM address .............
Index S scsm.......................................................... 7-5 SCSP .............................................2-22, 2-24 security ..................................................... 9-9 SmartSwitch 6500 SNMP agent...................................... A-1 supported MIBs ................................ A-6 traffic management ............................ 6-1 SmartSwitch ATM Administrator default community strings ................ A-8 SMI Formats supported...........................
Index update firmware ....................................... 7-8 upgrades ................................................... 7-1 upgrading boot load firmware............................. 7-6 changing default boot load image...... 7-7 POST diagnostics .............................. 7-7 switch operating firmware ................. 7-8 unsuccessful update ........................... 7-1 update firmware................................. 7-1 Upgrading and Changing Firmware......... 7-1 V VCI...................
