Page 1 9A656-04/9A686-04 Configuration Guide 9032598-02...
Page 3: Fcc Notice
Only qualiﬁed personnel should perform installation procedures. NOTICE Enterasys Systems reserves the right to make changes in speciﬁcations and other information contained in this document without prior notice. The reader should in all cases consult Enterasys Systems to determine whether any such changes have been made.
Page 4: Industry Canada Notice
Before utilizing this product, carefully read this License Agreement. This document is an agreement between you, the end user, and Enterasys Systems, Inc. (“Enterasys”) that sets forth your rights and obligations with respect to the Enterasys software program (the “Program”) contained in this package. The Program may be contained in ﬁrmware, chips or other media.
Page 5 Acquisition Regulations, Section 52.227-7013 (c) (1) (ii) and its successors, and use, duplication, disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at 252.227-7013. Enterasys Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867-0505.
Page 6: Safety Information
Notice SAFETY INFORMATION CLASS 1 LASER TRANSCEIVERS THE FE-100F3 FAST ETHERNET INTERFACE MODULE, FPIM-05 AND FPIM-07 FDDI PORT INTERFACE MODULES, APIM-29 AND APIM-29LR ATM PORT INTERFACE MODULES, ANIM-29/3 , ANIM-29/3LR AND ANIM-39/2 ATM NETWORK INTERFACE MODULES USE CLASS 1 LASER TRANSCEIVERS. READ THE FOLLOWING SAFETY INFORMATION BEFORE INSTALLING OR OPERATING THESE MODULES.
Page 7 Notice DECLARATION OF CONFORMITY Application of Council Directive(s): 89/336/EEC 73/23/EEC Manufacturer’s Name: Enterasys Systems, Inc. Manufacturer’s Address: 35 Industrial Way PO Box 5005 Rochester, NH 03867 European Representative Name: Mr. J. Solari European Representative Address: Enterasys Systems Limited Nexus House, Newbury Business Park...
Page 8 Notice 9A656-04/9A686-04 Conﬁguration Guide...
Page 9: Table Of Contents
CONTENTS CHAPTER 1 INTRODUCTION Using This Guide ..................1-1 Document Conventions ................1-2 Overview....................... 1-3 1.3.1 Distributed Management Framework ..........1-4 1.3.2 ATM Forum Specifications .............. 1-4 1.3.3 ATM Traffic Types................1-4 1.3.4 MIB Support ..................1-5 1.3.5 Distributed Clocking ................ 1-5 1.3.6 ATM Adaptation Layer (AAL) Support..........
Page 10 Contents SNMP Traps Screen ................... 2-13 2.8.1 Configuring the Trap Table............2-14 The Chassis Power Screen................. 2-15 2.10 The Module Selection Screen ..............2-17 2.10.1 Selecting a Module ................ 2-17 2.11 The Module Menu Screen for the 9A686-04 ..........2-18 2.12 The Module Configuration Menu Screen ............
Page 11 Contents 2.25 SPVC Destination Creation Screen ............2-53 2.25.1 SPVC Destination Creation Screen Fields........2-53 2.25.2 Creating the Destination End of an SPVP........2-55 2.25.3 Creating the Destination End of a SPVC ........2-56 2.26 LAN Emulation Menu Screen ..............2-57 2.26.1 LAN Emulation Client Menu Screen Fields ........
Page 12 Contents CHAPTER 4 SIGNALLING AND ROUTING Persistence ....................4-1 Signalling Overview..................4-2 4.2.1 Stack Types..................4-2 4.2.2 Configuration ................... 4-2 4.2.3 Setting Types................... 4-3 4.2.4 Setting Sides ................... 4-5 Routing Overview..................4-7 4.3.1 PNNI Overview ................4-7 4.3.2 Peer Groups ..................4-8 4.3.3 Crankback ..................
Page 13 Contents APPENDIX C SUPPORTED MIBS C.1 MIB, SMI, MIB Files and Internet MIB Hierarchy..........C-1 C.2 SmartSwitch 9500 MIB Hierarchy ..............C-3 9A656-04/9A686-04 Conﬁguration Guide...
Page 14 Contents 9A656-04/9A686-04 Conﬁguration Guide...
Page 15: Chapter 1 Introduction
NOTE local management screens will be added to the next revision. Welcome to the Enterasys Systems 9A656-04/9A686-04 Conﬁguration Guide. This guide describes the management features of the 9A656-04/9A686-04 and how to conﬁgure the modules and SmartSwitch 9500 chassis via Local Management screens and MIBs, and includes information concerning network requirements and troubleshooting.
Page 16: Document Conventions
Chapter 1: Introduction Chapter Basic System Conﬁguration , provides instructions on setting the In-Band, Out-Of-Band, and SMB-10 IP Addresses, setting SNMP Community Names and SNMP Traps, viewing chassis power supply information, creating PVCs and SPVCs, conﬁguring PNNI for the SmartSwitch 9500, setting ILMI parameters, conﬁguring the management LEC, and conﬁguring the Environmental Module of the SmartSwitch 9500 chassis.
Page 17: Overview
ATM Network Interface Modules (ANIMs) of any type can be installed in the 9A656-04 to provide front panel connectivity to the network. Enterasys Systems ANIMs can support up to 622 Mbps of bandwidth per port. The 9A656-04 switches data between the ANIMs and the Cell Transfer Matrix (CTM) backplane in the SmartSwitch 9500 chassis.
Page 18: Distributed Management Framework
Chapter 1: Introduction 1.3.1 Distributed Management Framework Through its distributed management framework, the 9A686-04 allows all the modules in the chassis to appear as a single entity, managed through a single IP address. The individual modules are transparent to the network manager and management applications. A fully loaded SmartSwitch 9500 chassis appears as a single switch, with one IP address.
Page 19: Mib Support
Overview 1.3.4 MIB Support The 9A686-04 provides support for a variety of Industry Standard and Enterasys Systems speciﬁc MIBs. Details on these MIBs are provided in later chapters of this Guide. The MIBs supported are as follows: • MIB2 (RFC 1573) •...
Page 20: Atm Adaptation Layer (Aal) Support
Chapter 1: Introduction 1.3.6 ATM Adaptation Layer (AAL) Support The 9A686-04 support all ATM Adaptation Layers, (AAL 1, AAL 3/4 and AAL 5). 1.3.7 Management LAN Emulation Client The SmartSwitch 9500 system creates a default management LEC upon ﬁrst initialization. The LEC automatically joins the default ELAN.
Page 21: Default Settings Upon First Initialization
Default Settings Upon First Initialization CTM interfaces may be recognized by the following CTM ANIM #: • If the ANIM number of the interface numbering scheme is 08 through 15. For example, if the interface number is 11402. This means that the 9A686-04 is installed in slot 1.
Page 22 Chapter 1: Introduction The 9A686-04 will always assign itself the default NSAP prefix shown in Figure 1-1. The section of the address following the NSAP prefix will be the last 4 bytes of the base MAC address of the module. The End System Identifier (ESI) will always be the base MAC address of the module.
Page 23: Additional Default Settings
Default Settings Upon First Initialization 1.5.2 Additional Default Settings The 9A686-04 also has the following additional default settings upon ﬁrst initialization. • A maximum of 128 k connections are allowed. • Bandwidth is given to any requested connection on a ﬁrst come, ﬁrst served basis (i.e., no Quality of Service (QoS) is given precedence to any particular request).
Page 24: Configurable Options
Chapter 1: Introduction CONFIGURABLE OPTIONS The 9A686-04 functions as a plug-and-play device, with minimal setup required by the user, however, the module also provides a high degree of customization. The following sections provide brief descriptions of the functions that may be customized depending on the requirements of the network administrator, and the ATM network.
Page 25 Conﬁgurable Options Environmental Module Conﬁguration Local Management provides access to the Environmental Module screen. This screen allows the user to view current operating conditions of the Environmental Module (EM), conﬁgure the COM ports of the EM, and download a new ﬁrmware image for the EM to FLASH memory.
Page 26: Local Management Screen Elements
Chapter 1: Introduction LOCAL MANAGEMENT SCREEN ELEMENTS This section describes the conventions that are used when describing the Local Management screens used to conﬁgure the SmartSwitch 9500 chassis and the 9A686-04 in later chapters of this guide. There are ﬁve types of screens used in Local Management: password, menu, conﬁguration, status, and warning screens.
Page 27 Local Management Screen Elements Only the password, conﬁguration and status screens have event message ﬁelds. NOTE Table 1-4 describes the most common event messages. Event messages related to speciﬁc Local Management applications are described with those applications throughout this manual. Table 1-4 Event Messages Message What it Means...
Page 28: Local Management Keyboard Conventions
Chapter 1: Introduction 1.7.1 Local Management Keyboard Conventions All key names appear in this manual as capital letters. For example, the Enter key appears as ENTER and the Backspace key appears as BACKSPACE. Table 1-5 explains the keyboard conventions used in this manual as well as the key functions. Table 1-5 Keyboard Conventions Function ENTER Key and RETURN Key...
Page 29: Getting Help
A description of any action(s) already taken to resolve the problem (e.g., changing mode switches, rebooting the unit, etc.) • The serial and revision numbers of all involved Enterasys Systems products in the network • A description of your network environment (layout, cable type, etc.) •...
Page 30: Related Manuals
Chapter 1: Introduction RELATED MANUALS Use the following manuals to supplement the procedures and other technical data provided in this manual. Enterasys Systems 9A656-04 Hardware and Installation Guide Enterasys Systems 9A686-04 Hardware and Installation Guide SmartSwitch 9000 Operations Guide Enterasys Systems SmartSwitch 9000 9C300-1 Environmental Module User’s Guide...
Page 31: Chapter 2 System Configuration
CHAPTER 2 SYSTEM CONFIGURATION This is a draft manual for the 9A686-04 only. Additional information regarding PNNI NOTE local management screens will be added to the next revision. The SmartSwitch 9500 is, by default, an SVC only switch. To create PVCs, the ILMI NOTE parameters must be changed from the default settings.
Page 32: Selecting Local Management Menu Screen Items
Chapter 2: System Conﬁguration • Viewing current SmartSwitch 9500 power supply information via the Chassis Power Screen. • Conﬁguring ILMI to set minimum and maximum VCI and VPI levels of SVCs and SVPCs and to reserve VCI/VPI pairs for PVCs. •...
Page 33: Accessing The Main Menu Screen
Accessing the Main Menu Screen The user can also exit Local Management screens by pressing ESC twice. This exit NOTE method does not warn about unsaved changes and all unsaved changes will be lost. Exit from Local Management by repeating steps 1 or 2 until the Main Menu screen displays.
Page 34: The Main Menu Screen
Chapter 2: System Conﬁguration To proceed to the Main Menu screen enter the community name “public” or press ENTER, the Main Menu screen, Figure 2-2, displays. Figure 2-2 The Main Menu Screen THE MAIN MENU SCREEN The Main Menu screen is the access point for all Local Management screens for all modules, the Environmental Module and the SmartSwitch 9500 chassis.
Page 35: The Chassis Menu Screen
The Chassis Menu Screen THE CHASSIS MENU SCREEN The Chassis Menu screen contains four menu items. These menu items open screens that are used to conﬁgure the SmartSwitch 9500 chassis. To access the Chassis Menu screen, perform the following steps: Use the arrow keys to highlight the CHASSIS option of the Main Menu screen.
Page 36: Chassis Configuration Screen
Chapter 2: System Conﬁguration SNMP TRAPS The SNMP Traps screen provides display and conﬁguration access to the table of IP addresses used for trap destinations and associated community names. For details, refer to the Section 2.8. CHASSIS POWER The Chassis Power screen provides access to chassis power supply status, power supply redundancy status and chassis fan tray status.
Page 37 Chassis Conﬁguration Screen The following list brieﬂy describes each of the Chassis Conﬁguration screen ﬁelds: MAC Address (Read-only) Displays the base physical address of the chassis. In-Band IP Address (Modiﬁable) Allows the In-Band IP address to be set for the SmartSwitch 9500 chassis. The In-Band IP Address is the address used by the LAN Emulation Client of the system that was described in Section 1.3.7.
Page 38: Setting The Ip Address
Chapter 2: System Conﬁguration Screen Update Time (Modiﬁable) Contains the rate at which the screens are updated. This setting determines how frequently (in seconds) information is updated on the screen. To enter a new update time, refer to Section 2.6.4. SAVE (Command) Saves all changes to memory.
Page 39: Setting The Chassis Date
Chassis Conﬁguration Screen 2.6.2 Setting the Chassis Date The SmartSwitch 9500 chassis is year 2000 compliant, so the Chassis Date may be set beyond the year 1999. To set the chassis date, perform the following steps: Use the arrow keys to highlight the Chassis Date field. Enter the date in this format: MMDDYYYY It is not necessary to add separators between month, day, and year numbers.
Page 40: Entering A New Screen Update Time
Chapter 2: System Conﬁguration Upon saving the new chassis time, all 9A686-04 modules installed in the chassis NOTE recognize the new value as the current time. 2.6.4 Entering a New Screen Update Time The screen update time is set from 3 to 99 seconds, with a default of 3 seconds. To set a new screen update time, perform the following steps: Use the arrow keys to highlight the Screen Update Time field.
Page 41: Snmp Community Names Screen
SNMP Community Names Screen SNMP COMMUNITY NAMES SCREEN The SNMP Community Names screen allows the user to set Local/Remote Management community names. Community names act as passwords to Local/Remote Management and provide security access to the SmartSwitch 9500. Access to the chassis is controlled by enacting any of three different levels of security authorization (read-only, read-write, and super-user).
Page 42: Establishing Community Names
Chapter 2: System Conﬁguration Access Policy (Read-only) Indicates the access accorded each community name. Possible selections are as follows: • read-only - This community name allows read-only access to the chassis MIB objects, and excludes access to security-protected ﬁelds of read-write or super-user authorization. This community name allows read and write access to the chassis MIB •...
Page 43: Snmp Traps Screen
SNMP Traps Screen SNMP TRAPS SCREEN Since the SmartSwitch 9500 is an SNMP compliant device, it can send messages to multiple Network Management Stations to alert users of status changes. The Chassis SNMP Traps screen is shown in Figure 2-6. Access the Chassis SNMP Traps screen from the Chassis Menu screen by using the arrow keys to highlight the SNMP TRAPS ﬁeld and pressing ENTER.
Page 44: Configuring The Trap Table
Chapter 2: System Conﬁguration 2.8.1 Conﬁguring the Trap Table To conﬁgure the Trap table, proceed as follows: Using the arrow keys, highlight the appropriate Trap Destination field. Enter the IP Address of the workstation that is to receive traps. IP address entries must follow the DDN format.
Page 45: The Chassis Power Screen
The Chassis Power Screen THE CHASSIS POWER SCREEN The Chassis Power screen allows the user to view current chassis power supply information. Access the Chassis Power screen from the Chassis Menu screen by using the arrow keys to highlight the CHASSIS POWER ﬁeld and pressing ENTER. The Chassis Power screen, Figure 2-7, displays.
Page 46 Chapter 2: System Conﬁguration PS1 Input Pwr Displays the total input power of power supply one. PS1 Output Pwr (Read-only) Displays the total output power of power supply one. PS1 FW Revision (Read-only) Displays the ﬁrmware revision of power supply one. PS1 HW Revision (Read-only) Displays the hardware revision of power supply one.
Page 47: The Module Selection Screen
The Module Selection Screen 2.10 THE MODULE SELECTION SCREEN The Module Selection screen is the access point to Local Management for all modules installed in the SmartSwitch 9500 chassis. By selecting a module, the user is taken to the ﬁrst Module Menu screen for the selected device.
Page 48: The Module Menu Screen For The 9A686-04
Chapter 2: System Conﬁguration 2.11 THE MODULE MENU SCREEN FOR THE 9A686-04 The Module Menu screen is the access point for all Local Management screens speciﬁc to the 9A686-04. Access the Module Menu screen by performing the following steps: Use the arrow keys to highlight the 9A686-04 you wish to manage from the Module Selection screen.
Page 49: The Module Configuration Menu Screen
The Module Conﬁguration Menu Screen 2.12 THE MODULE CONFIGURATION MENU SCREEN The Module Conﬁguration Menu screen provides access to Local Management screens that allow you to conﬁgure and monitor operating parameters, and access the Module Speciﬁc Conﬁguration screen. Access the Module Conﬁguration Menu screen from the Module Menu screen by using the arrow keys to highlight the MODULE CONFIGURATION ﬁeld and pressing ENTER.
Page 50: The General Configuration Screen
Chapter 2: System Conﬁguration 2.13 THE GENERAL CONFIGURATION SCREEN The General Conﬁguration screen allows the user to set the module date and time, set the screen refresh and lockout time, and to assign addresses for the default gateway and default interface.
Page 51: Entering A New Screen Refresh Time
The General Conﬁguration Screen Screen Refresh Time (Modiﬁable) Contains the rate at which the screens are updated. This setting determines how frequently (in seconds) information is updated on the screen. To enter a new update time, refer to Section 2.13.1. Screen Lockout Time (Modiﬁable) Contains the maximum number of minutes that the Local Management application displays a module’s screen while awaiting input or action from a user.
Page 52: Setting The Screen Lockout Time
Chapter 2: System Conﬁguration Use the arrow keys to highlight the SAVE command at the bottom of the screen and press ENTER. If the time entered is within the 3 to 99 seconds range, the Event Message Line at the top of the screen displays “SAVED OK”.
Page 53: Setting The Default Gateway
The General Conﬁguration Screen 2.13.4 Setting the Default Gateway If the SNMP management station is located on a different IP subnet than the 9A686-04, a default gateway must be speciﬁed. When an SNMP Trap is generated, the 9A686-04 sends the Trap to the default gateway.
Page 54: The Module Specific Configuration Screen
Management Interface (ILMI), and to enable/disable ATM diagnostics that are performed when power to the SmartSwitch 9500 is cycled. Since the SmartSwitch 9500 utilizes the Enterasys Systems Distributed Management Framework (DMF), system level conﬁguration may be performed via any 9A686-04 installed in the chassis. Any system level conﬁgurations that are performed will automatically be distributed to all other 9A686-04s installed in the chassis.
Page 55 The Module Speciﬁc Conﬁguration Screen MODULE CONFIGURATION The Module Conﬁguration menu item opens the Module Conﬁguration menu screen. This screen provides access to an additional screen that displays the current port status of all front panel (ANIM) and backplane (CTM) interfaces, and to a second screen that displays information on any errors that have occurred on any front panel or backplane interfaces.
Page 56: System Configuration Menu Screen
Chapter 2: System Conﬁguration 2.15 SYSTEM CONFIGURATION MENU SCREEN The System Conﬁguration Menu screen contains three menu items that open screens that are used to perform the following tasks: • Conﬁgure the 9A686-04/SmartSwitch 9500 to operate in a PNNI network. •...
Page 57: The Pnni Configuration Screen
The PNNI Conﬁguration Screen The following explains each ﬁeld of the System Conﬁguration Menu screen PNNI CONFIGURATION The PNNI Conﬁguration menu item opens the PNNI Conﬁguration Menu screen. This screen is used to conﬁgure the SmartSwitch 9500 to operate in a PNNI network. For details, refer to Section 2.16.
Page 58: Pnni Configuration Screen Fields
Chapter 2: System Conﬁguration Figure 2-14 The PNNI Conﬁguration Screen 2.16.1 PNNI Conﬁguration Screen Fields The following section explains each of the PNNI Conﬁguration screen ﬁelds: PNNI Mode Toggles between AUTO USING MAC, AUTO USING BOARD #, and MANUAL, with a default setting of AUTO USING MAC.
Page 59 The PNNI Conﬁguration Screen This mode is useful for plug and play operation of the SmartSwitch 9500 when it is in an environment with one or more SmartSwitch 9500 chassis. Each 9A686-04 has a unique Node ID, but has a PNNI Level configured (72) that will allow it to peer with all other 9A686-04s in the chassis, and any other SmartSwitch 9500s to which it is connected via front panel interfaces.
Page 60 Chapter 2: System Conﬁguration • MANUAL - In this mode the PNNI Level ﬁeld is defaulted to 104. This mode allows the user to modify the entire 13 byte (104 bits) NSAP preﬁx of the system. Refer to Figure 2-17. End System Modifable 104 Bits of NSAP Prefix Identifier (ESI)
Page 61: Setting The Pnni Mode
The PNNI Conﬁguration Screen 2.16.2 Setting the PNNI Mode To set the PNNI Mode, perform the following steps: After completing the following steps, the entire SmartSwitch 9500 will reset and all current switching being performed by the system will be halted. CAUTION Use the arrow keys to highlight the PNNI Mode field.
Page 62: The Ilmi Configuration Menu Screen
Chapter 2: System Conﬁguration Use the arrow keys to highlight the SAVE command at the bottom of the screen. Press ENTER. The changes are saved, and the system resets. 2.17 THE ILMI CONFIGURATION MENU SCREEN The ILMI Conﬁguration menu item opens the ILMI Conﬁguration Menu screen. This screen is used to specify minimum and maximum values for VCI and VPIs for all SVCs and SPVCs that the SmartSwitch 9500 will use while switching trafﬁc.
Page 63: Ilmi Configuration Menu Screen Fields
The ILMI Conﬁguration Menu Screen 2.17.1 ILMI Conﬁguration Menu Screen Fields The following section provides deﬁnitions of each ﬁeld of the ILMI Conﬁguration Menu screen. MIN SVCC VCI Used to set the minimum value that ILMI will use to assign VCIs to SVCs. This ﬁeld has a range from 33 to 16383.
Page 64: Setting The Max Svcc Vpi Field
Chapter 2: System Conﬁguration 2.17.3 Setting the MAX SVCC VPI Field To set the maximum value that the SmartSwitch 9500 will use for VPIs on SVCs, proceed as follows: Use the arrow keys to highlight the MAX SVCC VCI field. Enter a value between 0 and 4095 and press ENTER.
Page 65: The Atm Diagnostics Screen
The ATM Diagnostics Screen 2.18 THE ATM DIAGNOSTICS SCREEN The ATM diagnostics screen allows the user to enable or disable the power up diagnostics that the SmartSwitch 9500 system will perform when power is cycled to the chassis. Figure 2-19 Diags Conﬁguration Menu Screen 2.18.1 Enabling/Disabling ATM Diagnostics To enable or diable the power-up ATM Diagnostics, perform the following steps: Use the arrow keys to highlight the POWER UP DIAGS field.
Page 66: Module Configuration Menu Screen
Chapter 2: System Conﬁguration 2.19 MODULE CONFIGURATION MENU SCREEN The Module Conﬁguration screen contains ﬁve menu items that allow for the viewing of the current status of all front panel interfaces, and any errors that have occurred on front panel interfaces.
Page 67 Module Conﬁguration Menu Screen EPD/PPD Opens the EPD/PPD Conﬁguration Menu screen. This screen is used to enable and disable Early Packet Discard (EPD) and Partial Packet Discard (PPD) for this 9A686-04. It also allows the user to set the percentage that, when exceeded in the buffers, the 9A686-04 will begin dropping packets.
Page 68: Port Status Screen
Chapter 2: System Conﬁguration 2.20 PORT STATUS SCREEN The Port Status is a read-only screen that allows the user to view on the current status of all interfaces of each individual 9A686-04 installed in the SmartSwitch 9500. To access the Port Status screen, perform the following steps: Use the arrow keys to highlight the PORT STATUS menu item of the Module Configuration Menu screen.
Page 69 Port Status Screen ILMI State Indicates whether ILMI is currently operating on the interface. This ﬁeld may display the following items: Indicates ILMI is operating on this interface • UP - Indicates that ILMI is not operating on this interface •...
Page 70 Chapter 2: System Conﬁguration • PNNI 1.0 L - Indicates that port is using for PNNI 1.0 for Signalling. The “L” signiﬁes that the PNNI Node ID for this interface is less than (Lower) the adjacent Node ID. Indicates that the port is using IISP 3.0 with UNI 3.0 for inter-switch •...
Page 71 Port Status Screen • DSto (Deferred Stop Signalling) - Indicates that Signalling is attempting to stop, but is waiting until a previous Signalling stack is started on this interface. Indicates the interface is waiting for PNNI to start. • WStaP (Wait for Start PNNI) - •...
Page 72: Port Errors Screen
Chapter 2: System Conﬁguration 2.21 PORT ERRORS SCREEN The Port Errors screen is a read-only screen that is used to view all errors that have occurred on each interface. The screen displays errors that have been both received and transmitted from the interface.
Page 73 Port Errors Screen IN ERRORS Displays, in hexadecimal format, any errors that have been received by the applicable interface. Detailed information on these errors may be found by using MIB-II commands. OUT ERRORS Displays, in hexadecimal format, any errors that have been transmitted by the applicable interface.
Page 74: Epd/Ppd Configuration Menu Screen
Chapter 2: System Conﬁguration 2.22 EPD/PPD CONFIGURATION MENU SCREEN The EPD/PPD Conﬁguration Menu screen is only available for the 9A686-04. NOTE The EPD/PPD Conﬁguration Menu Screen is used to enable and disable Early Packet Discard (EPD) and Partial Packet Discard (PPD) for this 9A686-04. It also allows the user to set the percentage which, when exceeded in the buffers, the 9A686-04 will begin dropping packets.
Page 75: Configuring Epd/Ppd
EPD/PPD Conﬁguration Menu Screen PERCENTAGE (Modiﬁable) Allows the user to set the percentage which, when exceeded, will force the 9A686-04 to begin dropping packets. This ﬁeld has a range between 0 (drop packets immediately) through 100 (buffers must be completely full before dropping packets). 2.22.2 Conﬁguring EPD/PPD To set up this 9A686-04 to use the EPD/PPD feature, perform the following steps: Use the arrow keys to highlight the EPD PPD field.
Page 76: Spvc Connection Management Menu Screen
Chapter 2: System Conﬁguration 2.23 SPVC CONNECTION MANAGEMENT MENU SCREEN The SPVC Connection Management screen provides two menu items that open screens used to create SPVCs and SPVPs. To access the SPVC Connection Management screen, perform the following steps: Use the arrow keys to highlight the SPVC CONNECTIONS menu item from the Module Configuration Menu screen.
Page 77: Spvc Source Creation Screen
SPVC Source Creation Screen 2.24 SPVC SOURCE CREATION SCREEN The SPVC Source Creation Screen is used to conﬁgure the source end of a SPVC or SPVP connection. It also provides screen ﬁelds to enter the destination end values of the SPVC or SPVP.
Page 78 Chapter 2: System Conﬁguration SOURCE VPI ENTRY (Modiﬁable) Used to enter the VPI of the source end of the SPVC. If the 9A686-04 is using the default ILMI settings, the available range for this ﬁeld is between 33 and 4095. If the ILMI settings have been changed from the default values, the available range NOTE of this ﬁeld depends on the current ILMI settings.
Page 79: Creating The Source End Of An Spvp
SPVC Source Creation Screen CREATE SPVP (Command) Creates the source end of the SPVP using the values entered in the SOURCE INTERFACE, SOURCE VPI, DESTINATION VPI and SOURCE ATM ADDR ﬁelds. CREATE SPVC (Command) Creates the source end of the SPVC using the values entered in all of the ﬁelds on the screen. TOGGLE PERSISTENCE (Toggle) Sets the Atom Persistence is: ﬁeld to either “ON”...
Page 80 Chapter 2: System Conﬁguration The device that will support the destination end of this SPVP MUST have the same VPI value assigned as the one entered in step 8. If the destination device does not CAUTION have the same VPI value assigned, the SPVP will NOT be created. If the device that will support the destination end of this SPVP is another 9A686-04, refer to Section 2.25...
Page 81: Creating The Source End Of A Spvc
SPVC Source Creation Screen 2.24.3 Creating the Source End of a SPVC To create the source end of a SPVC, perform the following steps: Use the arrow keys to highlight the SOURCE INTERFACE field. Enter a valid interface number. For example, Figure 2-25 displays a screen shot of a 9A686-04 installed in slot 7 of the SmartSwitch 9500.
Page 82 Chapter 2: System Conﬁguration The device that will support the destination end of this SPVC MUST have the same ATM address assigned as the one entered in the DESTINATION ATM ADDR ﬁeld. CAUTION If the destination device does not have a destination ATM address assigned, or has a different ATM address assigned, the SPVC will NOT be created.
Page 83: Spvc Destination Creation Screen
SPVC Destination Creation Screen 2.25 SPVC DESTINATION CREATION SCREEN The SPVC Destination Creation screen is used to conﬁgure the applicable settings required for a 9A686-04 interface to support the destination end of a SPVC (VCL) or SPVP (VPL). To access the SPVC Destination Creation screen, perform the following steps: Use the arrow keys to highlight the CREATE DESTINATION menu item from the SPVC Connection Management screen.
Page 84 Chapter 2: System Conﬁguration VCI (Modiﬁable) Used to enter the VCI of the source end of the SPVC (VCL). If the 9A686-04 is using the default ILMI settings, the available range for this ﬁeld is between 33 and 16k. If the ILMI settings have been changed from the default values, the available range NOTE for this ﬁeld depends on the current ILMI settings.
Page 85: Creating The Destination End Of An Spvp
SPVC Destination Creation Screen 2.25.2 Creating the Destination End of an SPVP To create the destination end of an SPVP, perform the following steps: Use the arrow keys to highlight the INTERFACE field. Enter a valid interface number. For example, Figure 2-26 displays a screen shot of a 9A686-04 installed in slot 7 of the SmartSwitch 9500.
Page 86: Creating The Destination End Of A Spvc
Chapter 2: System Conﬁguration Press ENTER. If all the values entered in the applicable fields are valid, the destination end of the SPVP is created. 2.25.3 Creating the Destination End of a SPVC To create the destination end of a SPVC, perform the following steps: Use the arrow keys to highlight the INTERFACE field.
Page 87: Lan Emulation Menu Screen
LAN Emulation Menu Screen Press ENTER to toggle between the options until the desired setting displays in the ATOM Persistence is: field. Use the arrow keys to highlight the CREATE VCL command at the bottom of the screen. Press ENTER. If all the values entered in the applicable fields are valid, the SPVC is created.
Page 88: Lan Emulation Client Menu Screen Fields
Chapter 2: System Conﬁguration Press ENTER, the LAN Emulation Client Menu screen, Figure 2-28, displays. Figure 2-28 The LAN Emulation Client Menu Screen 2.26.1 LAN Emulation Client Menu Screen Fields The following section provides brief description of each LAN Emulation Client Menu screen ﬁeld: PROPERTIES The Properties menu item opens the LAN Emulation Client Properties screen.
Page 89: Lan Emulation Client Properties Screen
LAN Emulation Client Properties Screen 2.27 LAN EMULATION CLIENT PROPERTIES SCREEN The LAN Emulation Client Properties screen is a read-only screen that is used to view current information on multiple LAN Emulation components of the management LEC. To access the LAN Emulation Client Properties screen from the LAN Emulation Client Menu screen, perform the following steps: Use the arrow keys to highlight the PROPERTIES menu item of the LAN Emulation Client Menu screen.
Page 90 Chapter 2: System Conﬁguration LEC ID (Read-Only) Displays the LAN Emulation Client Identiﬁer of the active chassis LEC. The value displayed in this ﬁeld signiﬁes the slot number of the 9A686-04 on which the LEC resides. If the LEC ID ﬁeld reads “0”, it signiﬁes that this LEC is not a member of an emulated LAN, and is not connected to a LAN Emulation Server.
Page 91 LAN Emulation Client Properties Screen Admin State (Read-Only) Displays the current status of the LEC. This ﬁeld will display “Running” if the LEC is operational or “NotInService” if the LEC has been stopped via management. LANE Version (Read-Only) Displays the current version of LAN Emulation being used. This ﬁeld reads [1.0] only. LEC ATM ADDR (Read-Only) Displays the ATM Address of the LEC.
Page 92 Chapter 2: System Conﬁguration BUS Multicast Send VCC (Read-Only) Displays the VPI and VCI of the Multicast Send Virtual Channel Connection (VCC) that the LEC has with the BUS. This connection is used by the LEC and the BUS to send all broadcast transmissions for address resolution.
Page 93: Lan Emulation Client Administration Screen
LAN Emulation Client Administration Screen 2.28 LAN EMULATION CLIENT ADMINISTRATION SCREEN The LEC Administration screen is used to modify the management LAN Emulation Client (LEC). A new LEC can be conﬁgured by the user, or this function can be performed automatically by the SmartSwitch 9500.
Page 94 Chapter 2: System Conﬁguration Conﬁgure ELAN (Toggle) Used to specify if the LEC is created manually by user, or automatically by the SmartSwitch 9500. This ﬁeld toggles between Automatic and Manual. For instructions on how to conﬁgure the LEC automatically and manually, refer to Section 2.28.2 Section 2.28.3.
Page 95: Configuring The Lec Automatically
LAN Emulation Client Administration Screen SET WELLKNOWN (Command) This command, when performed, sets the LEC Status, the Conﬁgure ELAN, ELAN Name and LECS Address ﬁelds to the following values: • Conﬁgure ELAN is set to Automatic • ELAN Name is empty •...
Page 96: Configuring The Lec Manually
Chapter 2: System Conﬁguration 2.28.3 Conﬁguring the LEC Manually To conﬁgure a new LEC manually, perform the following steps: Use the arrow keys to highlight the LEC Status field. Press the SPACE bar until the “Active” option displays. Use the arrow keys to highlight the Configure ELAN field. Use the SPACE bar to toggle between the options until Manual displays.
Page 97: Network Tools
Network Tools 2.29 NETWORK TOOLS The Network Tools function resides on both the 9A686-04 and SmartSwitch 9500 chassis and allows the user to access and manage network devices. Some Network Tools commands, although executable, will not return any NOTE information because they do not apply to ATM technology. Access the Network Tools screen by using the arrow keys to highlight the NETWORK TOOLS ﬁeld in the Module Menu screen and pressing ENTER.
Page 98: Built-In Commands
Chapter 2: System Conﬁguration The conventions used here to describe Network Tools are as follows: NOTES Information entered by user is in bold helvetica font Arguments enclosed by [ ] are required Arguments enclosed by < > are optional To abort the output or interrupt a process, press the CONTROL key and c key simultaneously.
Page 99 Network Tools You can specify the arp command without options, or with one of the following options: Options: -a View cache data -d Delete an IP address entry. Requires additional arguments: <Interface Number> <IP address> -s Adds a static entry. Requires additional arguments: <Interface Number>...
Page 100 Chapter 2: System Conﬁguration Options: Not Applicable Example: NetTools-> bridge disable all NetTools-> bridge enable 1 NetTools-> bridge disable 1 051468 defroute: Syntax: defroute [interface number] [IP address] Description: The defroute command allows the user to view, set or delete the default IP route to a managed device through the speciﬁed interface.
Page 101 Network Tools netstat: Syntax: netstat [option] Description: The netstat command provides a display of general network statistics for the managed device. The netstat command must be used with one of the two display options. Options: -i Displays status and capability information for each interface -r Displays routing information for each interface Example: NetTools->...
Page 102 Chapter 2: System Conﬁguration reset: Syntax: reset Description: The reset command allows a soft reset of the device. The user will be queried to conﬁrm the reset command to insure against unwanted resets. The Network Tools connection to the module will be terminated upon execution of NOTE this command.
Page 103 Network Tools Options: Not Applicable Example: NetTools-> show Appletalk interfaces AdminStatus # Interface OperStatus Forwarding Framing enabled enabled 1500 enabled ethernet disabled disabled 1500 disabled ethernet NetTools-> show IP ARP MediaType # Interface PhysicalAddress NetworkAddress 3 (dynamic) 00:00:1d:04:40:5d 123.456.40.1 3 (dynamic) 08:00:20:0e:d8:31 123.456.40.30 174246...
Page 104: Special Commands
Chapter 2: System Conﬁguration The Network Tools connection to the module will be terminated upon execution of NOTE this command. Options: Not Applicable Example: NetTools-> soft-reset 174266 2.29.2 Special Commands done, quit, exit: Syntax: done Description: The done command enables the user to exit from Network Tools and return to the Main Menu screen.
Page 105: The Environmental Module Screen
The Environmental Module Screen 2.30 THE ENVIRONMENTAL MODULE SCREEN The Environmental Module screen allows the user to view current chassis temperature and humidity conditions, check the current operating status of the environmental module fans, set the applications for the COM ports of the environmental module, and download a new image into Flash memory.
Page 106 Chapter 2: System Conﬁguration Chassis Ext. Temp (Read-only) Displays the temperature, in Fahrenheit and Centigrade, of the area where the chassis is installed. This is followed by a general temperature condition in relation to the Fahrenheit and Centigrade values. Board Revision (Read-only) Displays the board revision of the environmental module.
Page 107: Setting The Fan Speeds
The Environmental Module Screen COM2 (Toggle) Displays the current conﬁguration of the COM2 port on the environmental module. This ﬁeld toggles between ENABLED and DISABLED. To change the setting of the COM2 port refer to Section 2.30.2. Application (Selectable) Displays the current application assigned to the COM2 port. This ﬁeld contains the following options: •...
Page 108: Changing The Com2 Application
Chapter 2: System Conﬁguration The COM1 Port is reserved for Local Management. If you disable the COM1 Port, and the COM2 Port is not set up for Local Management, you will no longer be able CAUTION to manage this device via Local Management. Use the arrow keys to highlight the SAVE command at the bottom of the screen.
Page 109: Creating A Pvc
These sections provide two example formats to perform this task. The ﬁrst will be examples of performing the task via Enterasys Systems Spectrum MIB Tools Utility. The second will present the MRMIT command line interface version of the command to perform the task.
Page 110 Chapter 2: System Conﬁguration Figure 2-33 ILMI Conﬁguration Screen In this example, the ILMI Conﬁguration screen is used to set the following parameters: • The MIN SVCC VCI ﬁeld is set to 100 • The MAX SVCC VPI ﬁeld is set to 0 With this conﬁguration entered and saved, the SmartSwitch 9500 will reserve VCI values 33 through 100, with the VPI value of 0 for PVCs.
Page 111: Setting The Instance Of The First Interface
Creating a PVC 2.31.3 Setting the Instance of the First Interface This section provides instructions on setting the Instance of the interfaces. Refer to Figure 2-34. Figure 2-34 Setting the Instance Figure 2-34 contains 3 callouts that display status information, and the conﬁguration ﬁelds necessary to set the instance of the ﬁrst interface.
Page 112: Setting The Traffic Descriptor For The Receive Side Of The Interfaces
Chapter 2: System Conﬁguration After these steps have been completed for the ﬁrst interface, the same conﬁguration must be performed for the second interface. In this case, the SNMP command line would be: snmpset -h 134.141.87.75 1.3.6.1.2.1.37.1.7.1.13.70102.2.50 Integer 5 2.31.4 Setting the Trafﬁc Descriptor for the Receive Side of the Interfaces This section provides instructions on setting the trafﬁc descriptors for the receive side of both interfaces.
Page 113: Setting The Traffic Descriptor For The Transmit Side Of The Interfaces
Creating a PVC Conﬁrmation that the selected interface and VPI/VCI pair has been assigned to the trafﬁc descriptor value 10. After these steps have been completed for the receive side of the ﬁrst interface, the same conﬁguration must be performed for the receive side of the second interface. In this case, the SNMP command line would be: snmpset -h 134.141.87.75 1.3.6.1.2.1.37.1.7.1.6.70102.2.50 Integer 10 2.31.5 Setting the Trafﬁc Descriptor for the Transmit...
Page 114: Setting The Vcl Status To Active
Chapter 2: System Conﬁguration Displays the name of the MIB command used to perform this procedure (atmVclTransmitTrafﬁcDescrIndex) and the OID string the SNMP application is using to access this information (1.3.6.1.2.1.37.1.7.1.7). Displays the instance that has been entered for this PVC (70101.2.50) This indicates that the interface selected is 70101, and it has been assigned a VPI/VCI pair of 2.50.
Page 115: Getting The Cross-Connect Identifier (Ccid)
Creating a PVC Figure 2-37 contains 3 callouts that display status information, and the conﬁguration ﬁelds necessary to set the VCL Status of the ﬁrst interface. The deﬁnitions for the callouts are as follows: Displays the name of the MIB command used to perform this procedure (atmVclRowStatus) and the OID string the SNMP application is using to access this information (1.3.6.1.2.1.37.1.7.1.13).
Page 116: Activating The Pvc
Chapter 2: System Conﬁguration 2.31.8 Activating the PVC This section describes the ﬁnal step that, when completed, will make the PVC operational on the device. Refer to Figure 2-39. Figure 2-39 Activating the PVC Figure 2-39 contains 3 callouts that display status information, and the conﬁguration ﬁelds necessary to activate the PVC.
Page 117 Creating a PVC The command line for this task is as follows: snmpset -h134.141.87.75.1.3.6.1.2.1.37.1.11.1.13.3596.70101.2.50.70102.2.50 Integer 4 After these steps have been completed, conﬁrm that the PVC is active. Refer to Figure 2-40. Figure 2-40 Conﬁrming that the PVC is Active Figure 2-40 contains 2 callouts that display the status information necessary to conﬁrm the PVC has been created.
Page 118 Chapter 2: System Conﬁguration 2-88 9A656-04/9A686-04 Conﬁguration Guide...
Page 119: Chapter 3 Ilmi 4.0 And The Smartswitch 9500 System
CHAPTER 3 ILMI 4.0 AND THE SMARTSWITCH 9500 SYSTEM This chapter provides an overview of how the SmartSwitch 9500 system uses ILMI 4.0 to provide a ﬂexible, multi-protocol ATM switch. The auto-conﬁguration features of ILMI 4.0 allow the SmartSwitch 9500 to support all standard ATM Signalling and Routing protocols on both front panel and backplane interfaces on an interface by interface basis.
Page 120 The Ethernet to ATM LEC provides Ethernet users with access to the ATM backbone that the SmartSwitch 9500 is a part of. In this example, the bridge is a Enterasys Systems SmartSwitch 2200 (24 port Ethernet Switch) with an HSIM-A6DP (ATM uplink device) installed.
Page 121 Port 2 of the ANIM-21/3 is connected to another ATM Switch. In this example, the other switch is a Enterasys Systems SmartSwitch 2500. Since both of these switches support the latest version of PNNI (1.0), they have auto-negotiated to use this Signalling stack. The “H”...
Page 122 Chapter 3: ILMI 4.0 and the SmartSwitch 9500 System Example 3 In this example, the ANIM installed in slot 3 of the 9A686-04 is an ANIM-22/4. This ANIM provides 4 OC-3 (155 Mbps) switched ports that use Category 5 UTP cabling. This ANIM is used to connect 4 servers to the ATM backbone.
Page 123: Port Status Screen
Port Status Screen Example 5 This example describes the interconnections between 9A686-04s installed in the same chassis. Each 9A686-04 has seven CTM ASICs. These ASICs are, essentially, ANIMs with two ports. Each ASIC uses the two ports for connections to two slots in the chassis. This results in a fault-tolerant, full mesh switch fabric between all 9A686-04s.
Page 124 Chapter 3: ILMI 4.0 and the SmartSwitch 9500 System Figure 3-2 is an example of an individual 9A686-04 board in a SmartSwitch 9500. In this example, there are six front panel interfaces with physical connections to other devices. All devices are using UNI 3.1 for Signalling. The “N” to the right of each UNI 3.1 indicates that these are UNI 3.1 Network Connections, (i.e., each port is physically connected to another ATM device).
Page 125: Ilmi Configuration Screen
ILMI Conﬁguration Screen ILMI CONFIGURATION SCREEN Local management of the SmartSwitch 9500 allows the user to specify minimum and maximum values for VCI and VPIs for all SVCs and SPVCs that the SmartSwitch 9500 will use while establishing connections. Table 3-1 provides the default settings ILMI uses when ﬁrst connected to the ATM network.
Page 126 Chapter 3: ILMI 4.0 and the SmartSwitch 9500 System Max SVCC VPI=4095 4095 Reserved by the 0-32 ATM Forum 0-4095 VCI Values 33-16K VCI 33-16K VPI Values 0-4095 VPI 0-4095 Available for Use by SVCs ONLY VPI Range VCI Range Min SVCC VCI=33 Figure 3-3 Default ILMI Settings Figure 3-3...
Page 127 ILMI Conﬁguration Screen Figure 3-4 Modiﬁed ILMI Conﬁguration Screen Changing the values of the ILMI Conﬁguration screen will cause all current connections on the system to be dropped. CAUTION If the SmartSwitch 9500 is in a mixed environment, check with the other ATM switch vendors to discover their maximum VCI values before changing any ILMI settings.
Page 128 Chapter 3: ILMI 4.0 and the SmartSwitch 9500 System 4095 Reserved by the 0-32 ATM Forum 0-4095 VCI Values 33-16K VCI 33-16K VPI Values 5-4095 VPI 5-4095 Available for Use by PVCs Only 33-199 VCI Values 33-199 0-4095 VPI Values 0-4095 Available for Use by VPI Range PVCs Only...
Page 129: Chapter 4 Signalling And Routing
CHAPTER 4 SIGNALLING AND ROUTING This chapter discusses the Signalling protocols supported by the SmartSwitch 9500, and provides details on default settings and conﬁguration options. In addition, this chapter provides instructions on manually conﬁguring the Signalling stacks and creating static routes using MIBs.
Page 130: Signalling Overview
Chapter 4: Signalling and Routing SIGNALLING Overview The SmartSwitch 9500 supports all ATM Forum ratiﬁed speciﬁcations of the User-Network Interface (UNI) as well as IISP and PNNI. UNI Signalling is used by ATM devices to set up SVCs for trafﬁc transport. 4.2.1 Stack Types The SmartSwitch 9500 supports all ATM Forum Signalling Stack Types.
Page 131: Setting Types
Signalling Overview 4.2.3 Setting Types This section describes how to use the AToM MIB to specify which version of Signalling stack the individual front panel interface will use. Once this value is set, this interface will not use any other kind of Signalling stack on this interface until the user sets the Signalling type back to autoconﬁg (ILMI 4.0), or the NVRAM of the entire 9A686-04 is cleared.
Page 132 Chapter 4: Signalling and Routing Figure 4-1 contains three callouts that are deﬁned as follows: Displays the name of the MIB command used to perform this procedure (atmIntfConﬁgType) and the OID string the SNMP application is using to access this information (1.3.6.1.2.1.37.14.1.14.1.1).
Page 133: Setting Sides
Signalling Overview 4.2.4 Setting Sides The UNI or IISP Signalling stack must ﬁrst be set before setting the side of the NOTE interface. PNNI Signalling does not allow network or user side conﬁguration. This section describes how to use the AToM MIB to specify which side of UNI Signalling this individual front panel interface will support (Network side or User side).
Page 134 Chapter 4: Signalling and Routing Figure 4-2 contains three callouts which are deﬁned as follows: This section of the screen displays the name of the MIB command used to perform this procedure (atmIntfConﬁgSide) and the OID string the SNMP application is using to access this information (1.3.6.1.2.1.37.14.1.14.1.3).
Page 135: Routing Overview
Routing Overview ROUTING OVERVIEW The following sections cover the following topics: • Provides an overview of the PNNI 1.0 support of the 9A686-04 • Provides an overview of IISP support of the 9A686-04 • Provides instructions on creating a static route using MIBs 4.3.1 PNNI Overview For a detailed overview of PNNI, refer to Chapters 1 through 4 of the ATM Forum’s NOTE...
Page 136: Peer Groups
Chapter 4: Signalling and Routing 4.3.2 Peer Groups PNNI Networks are composed of switches assigned to peer groups. The switches describe what peer group they belong to by advertising their peer group ID. Switches with the same peer group ID are in the same peer group. Switches in the same peer group exchange topology databases and update the database as signiﬁcant changes occur.
Page 137: Crankback
Routing Overview 4.3.3 Crankback Crankback occurs when a requested connection exceeds the services currently available for the desired path. When this occurs, the ﬁrst switch in the desired path will attempt to re-route the requested connection. refer to Figure 4-3. Peer Group 1 Rejected Connection Request...
Page 138: Gcac
Chapter 4: Signalling and Routing 4.3.4 GCAC GCAC (generic Call Admission Control) is used by switches supporting PNNI to increase the chances that a requested connection can be supported by all switches in the determined path. Since each ATM switch in the path may perform CAC in a different way, it is necessary for a generic CAC to examine the current state of the network topology (via current topology state information provided by the PNNI protocol) to determine if the switches will be able to support a requested connection.
Page 139: Configuring Iisp
Conﬁguring IISP CONFIGURING IISP The following subsections provide an example of conﬁguring IISP. This example describes how to set one side (the user side) of the IISP interface. For NOTE the interface to become fully operational, the same conﬁguration must be take place on the switch to which this switch will connect, the only difference being the other switch’s interface should be set up as the network side.
Page 140: Signalling Configuration
Chapter 4: Signalling and Routing 4.5.1 Signalling Conﬁguration The following two subsections provide instructions on conﬁguring the IISP Signalling stacks and sides of the applicable interface. 4.5.1.1 Step 1: Set the IISP Signalling Version and Type The ﬁrst step in conﬁguring IISP is to assign which Signalling stack type the individual front panel interface will use for the connection, (IISP UNI 3.0, 3.1, or 4.0).
Page 141 Conﬁguring IISP Displays the current MIB command selected (atmIntfConﬁgType), the interface selected (70101, or port 1 of ANIM 1 of the 9A686-04 installed in slot 7), and the type of Signalling stacks available for this interface. Currently, this interface is set to use ILMI 4.0 for auto conﬁguration of the Signalling stack (autoConﬁg).
Page 142: Step 2: Set The Iisp Side
Chapter 4: Signalling and Routing 4.5.1.2 Step 2: Set the IISP Side The IISP Signalling stack type must be set before setting the side of the interface. NOTE The next step in conﬁguring IISP is to assign which side of UNI the individual front panel interface will use for the connection, (network or user).
Page 143 Conﬁguring IISP This section of the screen displays the current MIB command selected (atmIntfConﬁgSide), the interface selected (70101, or port 1 of ANIM 1 of the 9A686-04 installed in slot 7), and the type of side available for this interface. Currently, this interface is not set to be on either the network or user side of the stack (other).
Page 144: Creating And Configuring A Reachable Address (Static Route)
Chapter 4: Signalling and Routing CREATING AND CONFIGURING A REACHABLE ADDRESS (STATIC ROUTE) The following four subsections explain the steps required to create a static route. These steps apply to any interface (e.g., a PNNI, IISP or UNI). In this example, the static route established will route ALL connection requests for the reachable address conﬁgured on the interface to the other interface.
Page 145: Step 1: Create A Row In The Pnnirouteaddrtable
Creating and Conﬁguring a Reachable Address (Static Route) 4.6.1 Step 1: Create a Row in the pnniRouteAddrTable This section provides an example of how to create a new row in the PNNI Route Address Table. Refer to Figure 4-6. Figure 4-6 Creating an Entry in the pnniRouteAddr Table Figure 4-6 contains 4 callouts that display status information, and the conﬁguration ﬁelds necessary to create an entry in the pnniRouteAddr table.
Page 146 Chapter 4: Signalling and Routing Displays the entry the user will create, and the conﬁguration option (createAndGo) that will add the desired entry. In this example, the instance in this ﬁeld has been set to the wellknown LAN Emulation Service (LES) address, deﬁned as follows: 7000001.71.0.121.0.0.0.0.0.0.0.0.0.0.0.160.62.0.0.1.152.2 This decimal address format can be broken into several identifying parts, deﬁned as follows: •...
Page 147: Step 2: Associate The Reachable Address With Its Advertising Node Id
Creating and Conﬁguring a Reachable Address (Static Route) 4.6.2 Step 2: Associate the Reachable Address with Its Advertising Node ID To have the row become active, it is necessary to conﬁgure the pnniRouteAddrAdvertisingNodeId entered in the pnniRouteAddressTable covered in Section 4.6.1.
Page 148 Chapter 4: Signalling and Routing This ﬁeld displays that the instance has been successfully set, and the Node ID screen updates to show that the instance has been created. See the highlighted section of the screen in Figure 4-8. Figure 4-8 Updated Node ID screen Page 4-20 9A656-04/9A686-04 Conﬁguration Guide...
Page 149: Step 3: Associate The Reachable Address With A Port Id
Creating and Conﬁguring a Reachable Address (Static Route) 4.6.3 Step 3: Associate the Reachable Address with a Port ID The next step in conﬁguring the route is to associate the address with the Port ID where it can be reached. This is accomplished using the pnniRouteAddrAdvertisePortId MIB command. Refer to Figure 4-9.
Page 150 Chapter 4: Signalling and Routing Figure 4-10 Assigning an interface for the Reachable Address (screen 2) Figure 4-10 contains two callouts that are deﬁned as follows: This ﬁeld displays the instance that has been created. Directly to the right of the instance is the interface that has been assigned to this instance (70101, or port 1 of ANIM 1 of the 9A686-04 installed in slot 7 of the chassis).
Page 151: Step 4: Associate The Reachable Address With An Interface
Creating and Conﬁguring a Reachable Address (Static Route) 4.6.4 Step 4: Associate the Reachable Address with an Interface The next step in conﬁguring the route is to associate the address with the interface where it can be reached. This is accomplished using the pnniRouteAddrIfIndex MIB command. Refer Figure 4-11.
Page 152 Chapter 4: Signalling and Routing This section of the screen displays the instance that is being conﬁgured. Currently, the value is set to “0”, which indicates that an interface has not yet been assigned to this instance. Figure 4-12 displays the screen after an interface has been assigned to this instance. Figure 4-12 Setting the IfIndex for the Static Route (screen 2) Figure 4-12 contains two callouts that are deﬁned as follows:...
Page 153: Appendix A Acronyms
APPENDIX A ACRONYMS ATM Adaptation Layer AAL - ATM Adaptation Layer Type 1 AAL1 - ATM Adapter Layer Type 2 AAL2 - ATM Adapter Layer Type 3/4 AAL3/4 - ATM Adapter Layer Type 5 AAL5 - ATM Adaptation Layer Mux AALM - Available Bit Rate ABR -...
Page 154 Appendix A: Acronyms Call Admission Control CAC - Campus Area Network CAN - Category 5 unshielded twisted pair cable CAT-5 - Constant Bit Rate CBR - Comite Consultatif Internationale de Telegraphique et Telephonique (Consultative CCITT - Committee on International Telegraphy and Telephony) Current Cell Rate CCR - Cell Delay Variation...
Page 155 Acronyms European standard for digital transmission service at 2 Mb/s. E-1 - European standard for digital transmission service at 34.4 Mb/s (transports 16 E1 circuits) E-3 - Ethernet ENET - Explicit Forward Congestion Indicator EFCI - Extended Industry Standard Architecture EISA - Emulated Local Area Network ELAN -...
Page 156 Appendix A: Acronyms Institute of Electrical and Electronic Engineers IEEE - Internet Control Message Protocol ICMP - Identiﬁcation Number ID - Information Element IE - Internet Engineering Task Force IETF - Interim Inter-Switch Signaling Protocol IISP - Integrated Local Management Interface ILMI - Input/Output I/O -...
Page 157 Acronyms Media Access Control MAC - Metropolitan Area Network MAN - Megabits per second Mbps - Maximum Burst Size MBS - Minimum Cell Rate MCR - Management Information Base MIB - Multi-Mode Fiber MMF - Multi-Point MP - Main Switch Module MSM - Maximum Transfer Unit MTU -...
Page 158 Appendix A: Acronyms Personal Computer PC - Priority Control PC - Peripheral Component Interconnect PCI - Peak Cell Rate PCR - Protocol Data Unit PDU - Physical Media Dependent Sub-layer PMD - Point-to-Multipoint PMP - Private Network Node Interface or Private Network-to-Network Interface PNNI - Partial Packet Discard PPD -...
Page 159 Acronyms Signaling ATM Adaptation Layer SAAL - Segmentation And Reassembly SAR - SAR Protocol Data Unit SAR-PDU - System Bus Error SBE - Sustainable Cell Rate SCR - Synchronous Digital Hierarchy SDH - Simple Efﬁcient Adaptation Layer SEAL - Single Mode Fiber SMF - Switched Multimegabit Data Service SMDS -...
Page 160 Appendix A: Acronyms Unspeciﬁed Bit Rate UBR - UNI Management Entity UME - User-Network Interface UNI - Unnumbered Poll UP - Usage Parameter Control UPC - Universal Test and Operations Physical Interface for ATM UTOPIA - Unshielded Twisted Pair UTP - Variable Bit Rate/Real Time VBR/RT - Variable Bit Rate/Non-real Time...
Page 161: Appendix B Default Settings
APPENDIX B DEFAULT SETTINGS This appendix details the factory default settings that the 9A686-04 will use when ﬁrst initialized. B.1 SMARTSWITCH 9500 SYSTEM SETTINGS This section details the basic system settings that are set by default on the system upon ﬁrst initialization.
Page 162: Ilmi Settings
Appendix B: Default Settings B.1.5 ILMI Settings By default, the SmartSwitch 9500 will accept all connection requests on a ﬁrst come, ﬁrst serve basis. No priority is given to any speciﬁc connection request. For example, a UBR SVC will be given the same priority as a CBR SVC. The SmartSwitch 9500 will use the entire range of available VPI/VCI pairs for SVCs only.
Page 163: C.1 Mib, Smi, Mib Files And Internet Mib Hierarchy
These branches and those that fall below each category have short text strings and integers to identify them. Text strings describe object names, while integers allow computer software to create compact, encoded representations of the names. For example, the Enterasys Systems MIB variable atmSpvcMIBObjects is an object name and is also represented by the number one.
Page 164 Appendix C: Supported MIBs root joint CCITT ISO/CCITT internet private directory experimental mgmt MIB2 Label from the root to this point is 1.3.6.1.2.1 Figure C-1 Internet MIB Hierarchy Page C-2 9A656-04/9A686-04 Conﬁguration Guide...
Page 165: C.2 Smartswitch 9500 Mib Hierarchy
SmartSwitch 9500 MIB Hierarchy SMARTSWITCH 9500 MIB HIERARCHY The location of all MIBs supported in the Internet hierarchy is shown in Figure C-2. Entries that are shaded represent Enterasys systems proprietary MIBs. MIB2 internet AToM MIB AToM MIB objects private...
Page 166 Appendix C: Supported MIBs Tables through C-16 provide more detailed information on each of the supported MIBs contained in Figure C-2. These tables indicate all of the leaves that are supported in each individual MIB. In this appendix, tables that are that are titled “Distributed” provide information on NOTE MIB commands that have effect on the entire SmartSwitch 9500 system.
Page 167 SmartSwitch 9500 MIB Hierarchy Table C-3 Distributed AToM MIB (OID String: 1.3.6.1.2.1.37.1) Branch Branch.Leaf atmIntfCfgTable .2.1.1-8 atmIntfCfgTable .2.1.11-12 atmIntfTCTable (PVC) .4.1.1-2 atmVplTable(SVC and PVC) .6.1.1-10 atmVclTable(SVC and PVC) .7.1.1-7 .7.1.12-15 atmVPCrossConnect-Table .9.1.1-11 (PVC) atmVCCrossCon-nectTable .11.1.1-13 (PVC) Table C-4 Non-Distributed AToM MIB (OID String: 1.3.6.1.2.1.37.1) Branch Branch.Leaf atmTrafdesc-ParmTable...
Page 168 Branch.Leaf ILMI Branch .1.1 .1.2 .1.4 .2.4-11 Table C-7 Distributed PNNI MIB (OID String: 1.3.6.1.2.1.353.5.4.1.1) Branch Branch.Leaf PNNI Branch .1.19. all leaves Table C-8 Distributed Enterasys MIBs (OID String: 1.3.6.1.4.1.52) Branch Branch.Leaf chassisPower .4.1.1.7.1.1-10 boardPowerSlotStatus .4.1.1.7.2.1.1.1-8 boardPowerSlotEntry .4.1.1.7.2.2.1.1-9 termPower .4.1.1.7.5.1-5 chEnv .4.1.1.8.1.1-12...
Page 169 SmartSwitch 9500 MIB Hierarchy Table C-8 Distributed Enterasys MIBs (OID String: 1.3.6.1.4.1.52) Branch Branch.Leaf contLogicalToPhysicalMapEntry .4.1.1.9.3.2.1.1-2 contCommStr .4.1.1.9.5.1-3 contNetAddressTable .4.1.1.9.6.1.1.1-3 upsSystem .4.1.1.10.1 ctATMConﬁg .4.1.2.10.1.1. .4.1.2.10.1.3-5. sfcsSystem .4.1.2.11.1.1.1.1-3 sfcsEngine . 4.1.2.11.1.1.2.1-4 sfcsANIMConﬁg .4.1.2.11.1.1.3.1. sfcsANIMStatistics .4.1.2.11.1.1.3.2. sfcsANIMPic .4.1.2.11.1.1.3.3.1.1.1-23. .4.1.2.11.1.1.3.3.1.1.26-27. sfcsInterface .4.1.2.11.1.1.4.1-2 sfcsQueue .4.1.2.11.1.1.5.1-2...
Page 170 Appendix C: Supported MIBs Table C-9 Non-Distributed Enterasys MIBs Branch Branch.Leaf contPhysical .4.1.1.9.3.1.1.1-6 contLogicalToPhysicalMapEntry .4.1.1.9.3.2.1.1-2 contCommStr .4.1.1.9.5.1-3 sysResourceInstalled .4.1.1.12.1.1-2 Table C-10 Non-Distributed ctNetwork MIB (OID String: 1.3.6.1.4.1.52.4.1.3) Branch Branch.Leaf nwRevisionLevel .1.1.1 Table C-11 Distributed and Non-Distributed ctPIC MIB (OID String: 1.3.6.1.4.1.52.4.1.5.9) Branch Branch.Leaf...
Page 171 SmartSwitch 9500 MIB Hierarchy Table C-13 Non-Distributed nwRouter MIB (OID String: 1.3.6.1.4.1.52.4.2.2.2) Branch Branch.Leaf nwlpComponents .3.1.1 .3.1.2.1-2 nwlpHostToMedia .3.1.2.6.3.1.1.1-7 nwlpEventLogConﬁg .3.1.2.10.1.1-3 Table C-14 Distributed ctron Mib2 MIB (OID String: 1.3.6.1.4.1.52.4.3.3) Branch Branch.Leaf commonDev .1.1-3 ctIfCp .4.1.1.1-4 Table C-15 Non-Distributed ctron Mib2 MIB (OID String: 1.3.6.1.4.1.52.4.3.3) Branch Branch.Leaf ctlf...
Page 172 Appendix C: Supported MIBs Page C-10 9A656-04/9A686-04 Conﬁguration Guide...

This manual is also suitable for:

9a686-049a686-04

Cabletron Systems 9A656-04 Configuration Manual

Chapter 1 Introduction

Chapter 2 System Configuration

Chapter 3 Ilmi 4.0 and the Smartswitch 9500 System

Chapter 4 Signalling and Routing

Appendix A Acronyms

Appendix B Default Settings

Quick Links

Related Manuals for Cabletron Systems 9A656-04

Summary of Contents for Cabletron Systems 9A656-04

This manual is also suitable for:

Table of Contents