Manuale d’uso / di manutenzione del prodotto Switch/Router del fabbricante Alcatel Carrier Internetworking Solutions
Vai alla pagina of 1100
Par t No. 060166-10, Rev . C March 2005 Omni Switch/Router ™ User Manual Release 4.5 www .alcatel.com.
Copyright © 2005 by Alcatel Internetworking, Inc. All rights reserved. This document may not be reproduced in whole or in part without the express written permission of Alcatel Internetworking, Inc. Alcatel ® and the Alcatel logo are registered trademarks of Alcatel.
page iii Cautions FCC Compliance : This equipment has been tested and found to comply with the limits for Class A digital device pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
page iv.
page v T able of Contents 1 Omni Switch/Router Chassis and P ow er Supplies . . . . . . . . . . . . . . . . 1-1 Omni Switch/Router User Interface (UI) Software . . . . . . . . . . . . . . . . . . . 1-2 Omni Switch/Router Network Management Software (NMS) .
T able of Contents page vi MPX Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Change-Over Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 MPX Redundancy Commands .
T able of Contents page vii 4 The U ser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Overview of Command Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Changing Between the CLI and UI Modes .
T able of Contents page viii Multiple User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33 Listing Other Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34 Communicating with Other Users .
T able of Contents page ix Synchronizing Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Synchronizing Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Loading a File From the Primary MPX .
T able of Contents page x Secure Switch Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Configuring the Secure Switch Access Filter Database . . . . . . . . . . . . . . . . . . . 8-4 Configuring Secure Access Filter Points .
T able of Contents page xi Duplicate MAC Address Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30 Multicast Claiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32 Disabling Flood Limits .
T able of Contents page xii NTP Information Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15 Display List of Peers the Server Knows About . . . . . . . . . . . . . . . . . . . . . . . . 12-15 Display Peer Summary Information .
T able of Contents page xiii 13 SNMP (Simple Netw ork Management Protocol) . . . . . . . . . . . . . . . . 13-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 Configuring SNMP Parameters and Traps .
T able of Contents page xiv 16 Managing 802.1Q Gr oups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1 IEEE 802.1Q Sections Not Implemented . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 Application Example . . .
T able of Contents page xv Configuring Fast Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34 Truncating Tree Timing & Speedy Tree Protocol . . . . . . . . . . . . . . . . . . . . . . 17-35 Truncating Tree Timing .
T able of Contents page xvi MTU Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12 IP Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12 ICMP Based MTU Discovery .
T able of Contents page xvii 19 Managing Groups and P orts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1 How Ports Are Assigned to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2 Static Port Assignment .
T able of Contents page xviii Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57 How Port Mirroring Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57 What Happens to the Mirroring Port .
T able of Contents page xix Viewing Policy Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-24 Viewing Virtual Ports’ Group/VLAN Membership . . . . . . . . . . . . . . . . . . . . . . . . 20-25 View VLAN Membership of MAC Devices .
T able of Contents page xx Routing Between AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-15 Creating AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-16 Step A. Entering Basic VLAN Information .
T able of Contents page xxi 25 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T able of Contents page xxii Displaying IP RIP Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-37 Displaying a List of All IP RIP Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-37 Displaying a List of “Global” IP RIP Filters .
T able of Contents page xxiii 27 IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T able of Contents page xxiv Configuring Extended RIP and SAP Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-37 Enabling or Disabling Extended RIP and SAP Packets . . . . . . . . . . . . . . . . . . 27-37 Viewing the Current Status of Extended Packets .
T able of Contents page xxv 29 Managing Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1 Back-to-Back Frame Relay Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3 Universal Serial Port Cable Interfaces .
T able of Contents page xxvi Managing Frame Relay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-55 Configuring a Bridging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-57 Configuring a WAN Routing Service .
T able of Contents page xxvii Viewing WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-12 Displaying All Existing WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-12 Displaying Information for a Specific WAN Link .
T able of Contents page xxviii 34 Backup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T able of Contents page xxix TEMP LED is Amber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-10 Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-10 STA LED Is Off .
T able of Contents page xxx A The Boot Line Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Entering the Boot Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Boot Prompt Basics .
Page 1-1 1 Omni Switch/Router Chassis and P o w er Supplies Alcatel's Omni Switch/Router (OmniS/R) is an advanced, multi-layer switching platform (Layer 2 and 3) that supports the most demanding switch requirements.
Page 1-2 Currently, Omni Switch/Router switching modules consist of Gigabit Ethernet modules, auto- sensing Ethernet modules, Fast 10/100 Ethernet modules, 10 Mbps Ethernet modules, WAN modules, and Voice Over IP ( VOIP ) modules. See Chapter 3, “Omni Switch/Router Switching Modules,” for documentation.
Omni Switch/Router Distributed Switching Fabric Page 1-3 Omni Switch/Router Distributed Switching F abric Many switches in the market employ a shared memory architecture, which uses a central switching engine to send data to the appropriate port.
Omni Switch/Router Distributed Switching Fabric Page 1-4 Omni Switch/Router Fabric Capacity In a chassis with Omni Switch/Router modules only, each Omni Switch/Router module provides 2.
Omni Switch/Router Applications and Configurations Page 1-5 Omni Switch/Router Applications and Configur ations Omni Switch/Router hardware is ideally suited to meet the most demanding server and back- bone needs. In addition, Omni Switch/Router hardware can be integrated easily with OmniSwitches and with OmniStack workgroup switches.
Omni Switch/Router Applications and Configurations Page 1-6 Omni Switch/Router as the Centr al Backbone Switch/Router and in the Wiring Closet The figure below shows Omni Switch/Router chassis used in the wiring closet and as a network backbone switch/router connecting the wiring closets and server farm.
Omni Switch/Router Chassis and Power Supplies Page 1-7 Omni Switch/Router Chassis and P ow er Supplies The Omni Switch/Router chassis houses the MPX , switching modules, and one or two power supplies. The modular design of the chassis provides the ability to configure your Omni Switch/Router to meet your networking needs.
Omni Switch/Router Chassis and Power Supplies Page 1-8 OmniS/R-3 The OmniS/R-3 chassis features three slots for an MPX and specific switching modules (contact your Alcatel sales representative for information on module availability). Slots are numbered from 1 to 3 starting with the topmost slot.
Omni Switch/Router Chassis and Power Supplies Page 1-9 OmniS/R-3 Chassis T echnical Specifications Total Module Slots 3 Total Slots for Switching Modules 2 Physical Dimensions 5.25” (13.34 cm) high, 17.13” (43.51 cm) wide, 13.00” (33.02 cm) deep Weight 18 lb.
Omni Switch/Router Chassis and Power Supplies Page 1-10 OmniS/R-5 The OmniS/R-5 chassis has five slots for an MPX and switching modules (see figure below). Slots are numbered from 1 to 5 starting with the topmost slot. Slots for two power supplies are located at the bottom of the chassis.
Omni Switch/Router Chassis and Power Supplies Page 1-11 The OmniS/R-5 provides bays for two power supplies. The power supplies are self-enclosed to allow safe hot-insertion and hot-removal. When two power supplies are installed, they share the electrical load.
Omni Switch/Router Chassis and Power Supplies Page 1-12 OmniS/R-5 T echnical Specifications Total Module Slots 5 Total Slots for Switching Modules 4 Physical Dimensions 12.25” (31.12 cm) high, 17.14” (43.54 cm) wide, 13” (33.02 cm) deep Weight approximately 55 lb.
Omni Switch/Router Chassis and Power Supplies Page 1-13 OmniS/R-9 and OmniS/R-9P The OmniS/R-9 and OmniS/R-9P chassis have nine slots for an MPX and switching modules (see figure below). Slots are numbered from 1 to 9 starting with the left-most slot.
Omni Switch/Router Chassis and Power Supplies Page 1-14 The OmniS/R-9 and OmniS/R-9P provide bays for two power supplies. The power supplies are self-enclosed to allow safe hot-insertion and hot-removal. When two power supplies are installed, they share the electrical load.
Omni Switch/Router Chassis and Power Supplies Page 1-15 OmniS/R-9 T echnical Specifications Total Module Slots 9 Total Slots for Switching Modules 8 Physical Dimensions 24.50” (62.23 cm) high, 16.60” (42.16 cm) wide, 13.25” (36.66 cm) deep Weight 96 lb.
Omni Switch/Router Chassis and Power Supplies Page 1-16 OmniS/R-9P T echnical Specifications Total Module Slots 9 Total Slots for Switching Modules 8 Physical Dimensions 24.50” (62.23 cm) high, 16.60” (42.16 cm) wide, 13.25” (36.66 cm) deep Weight 96 lb.
Omni Switch/Router Chassis and Power Supplies Page 1-17 OmniS/R-9P-48V T echnical Specifications Total Module Slots 9 Total Slots for Switching Modules 8 Physical Dimensions 24.50” (62.23 cm) high, 16.60” (42.16 cm) wide, 13.25” (36.66 cm) deep Weight 96 lb.
Omni Switch/Router Chassis and Power Supplies Page 1-18 Omni Switch/Router P ow er Requirements Always make sure that the total power requirements of the modules in your chassis do not exceed the limits of your power supply.
Omni Switch/Router Chassis and Power Supplies Page 1-19 Module Power Requirements without an HRE-X Module Description DC Current Draw (Amps) FCC Class Approval MPX Management Processor Module. 3.75 B ESX-K-100C-32W Advanced auto-Sensing 10/100 Ethernet module with thirty-two (32) RJ-45 ports.
Omni Switch/Router Chassis and Power Supplies Page 1-20 Module Power Requirements with an HRE-X Module Description DC Current Draw (Amps) FCC Class Approval MPX-L3 Management Processor Module. 5.25 B ESX-K-100C-32W-L3 Advanced auto-Sensing 10/100 Ethernet module with thirty-two (32) RJ-45 ports.
Omni Switch/Router Chassis and Power Supplies Page 1-21 Grounding a Chassis Omni Switch/Routers have two grounding screw holes on the back of the chassis.
The Omni Switch/Router Hardware Routing Engine (HRE-X) Page 1-22 The Omni Switch/Router Har dwar e Routing Engine (HRE-X) The Omni Switch/Router Hardware Routing Engine ( HRE-X ) is available for the MPX and all Omni Switch/Router switching modules.
The Omni Switch/Router Hardware Routing Engine (HRE-X) Page 1-23 Each HRE-X routes up to 1.5 million packets per second. In an OmniS/R-9 with an HRE-X on every switching module, for example, you could have up to 12 Mpps routed throughput. On a per switch basis, the HRE-X also supports over 256,000 route entries and 64,000 Next Hop destinations.
Connecting a DC Power Source to an OmniS/R-PS5-DC375 Page 1-24 Connecting a DC P ow er Sour ce to an OmniS/R-PS5-DC375 The OmniS/R-5 can use a DC power supply called the OmniS/R-5-DC375. This power supply contains a female power connector as shown in the figure below.
Connecting a DC Power Source to an OmniS/R-PS5-DC375 Page 1-25 Opening Wire Bay on Screw-Style Connector 5. Insert the appropriate wire lead into the open circular hole. The silkscreen above each hole indicates which power lead—negative (-), positive (+), or ground (GND)—to plug into which hole.
Connecting a DC Power Source to an OmniS/R-PS5-DC375 Page 1-26 7. Repeat Steps 4 through 6 for the remaining two wire leads. Be sure that the end of each lead attaches to the same power source that you connected to on the power supply (i.e., negative to negative, positive to positive, ground to ground).
Connecting a DC Power Source to an OmniS/R-PS9-DC725 Page 1-27 Connecting a DC P ow er Sour ce to an OmniS/R-PS9-DC725 The OmniS/R-9P can use a DC power supply called the OmniS/R-PS9-DC725. This power supply contains a female power connector as shown in the figure below.
Connecting a DC Power Source to an OmniS/R-PS9-DC725 Page 1-28 Installing DC P ow er Source Wir e Leads These instructions describe how to connect your 3-wire DC power source to the power connector on your DC power supply. A small flat-tip screwdriver and a wire stripper are required for this procedure.
Connecting a DC Power Source to an OmniS/R-PS9-DC725 Page 1-29 Inserting the Wire Lead Into the Circular Hole 6. Close the wire bay door. Use the small screwdriver (from Step 4a) to tighten the screw above the wire bay into which you inserted the wire lead.
Replacing Power Supplies (9-Slot Chassis) Page 1-30 Replacing P ow er Supplies (9-Slot Chassis) If a power supply ever needs to be replaced in an Omni Switch/Router 9-slot Chassis (e.g., OmniS/R-9 or OmniS/R-9p), it is strongly recommended that power supplies not be mixed, except under the conditions and exceptions shown in the following table.
Page 2-1 2 The Omni Switch/Router MPX Omni Switch/Router Management Pr ocessor Module (MPX) F eatures The MPX provides such system services as maintenance of user configuration information, downloadin.
Omni Switch/Router Management Processor Module (MPX) Features Page 2-2 Omni Switch/Router Management Processor Module (MPX) Status LEDs MPX 10 mm MODEM CONSOLE PRI SEC TEMP PS1 PS2 OK2 OK1 ACT COL LINK ETHERNET OK1 (Hardware Status). This dual- state LED is on Green when the MPX has passed power-on hardware diag- nostics successfully.
Omni Switch/Router Management Processor Module (MPX) Features Page 2-3 MPX Management Connectors COL (Collision). On Yellow when a collision has been detected on the port. ACT (Activity). On Green when data is transmitted or received on the Ethernet management port.
MPX Serial and Ethernet Management Ports Page 2-4 MPX Serial and Ethernet Management P orts You can gain access to switch management software through one of the two serial ( RS-232 ) ports on the MPX or the Ethernet management port. The two serial ports are configured with 9-pin “D” connectors ( DB-9 ) per the IBM AT serial port specification.
MPX Serial and Ethernet Management Ports Page 2-5 MPX Modem Port Ethernet Management P ort The MPX also supports an out-of-band Ethernet port for high-speed uploads and switch management functions. With this port, you can access the Omni Switch/Router over a network via Telnet or FTP .
MPX Serial and Ethernet Management Ports Page 2-6 Configuring MPX Serial P orts The serial communications parameters for the two MPX serial ports are set by default to the following: • 9600 bits pe.
Flash Memory and Omni Switch/Router Software Page 2-7 Flash Memory and Omni Switch/Router Softw are Flash memory on the MPX holds the Omni Switch/Router’s executable images and configura- tion data. When a switching module comes online, the MPX downloads the appropriate image file for that module to that module’s memory.
Flash Memory and Omni Switch/Router Software Page 2-8 Flash Memory Guidelines The switch alters flash memory contents when a software command requests a configuration change, when a remote administrator downloads a new executable image, or when the switch fails and a record of the failure is written to flash memory.
MPX Redundancy Page 2-9 MPX Redundanc y In order to provide greater reliability, Omni Switch/Router supports two MPX s in a primary/secondary redundant configuration. If the primary MPX fails, the secondary MPX takes over without any operator intervention.
MPX Redundancy Page 2-10 The primary MPX has the ability to transfer files to and from the secondary MPX . In the condi- tion where the secondary MPX has an older version of software (Software Fallback), it is not desirable to update the configuration file of the secondary.
Page 3-1 3 Omni Switch/Router Switching Modules Omni Switch/Router switching modules perform software filtering, translations between dissimilar network interfaces, and hardware-based switching. Omni Switch/Router switching modules have an additional on-board interface connector for the HRE-X .
Page 3-2 Omni Switch/Router Hardware Routing Engine The HRE-X offers high-speed Layer 3 switching from 1.5 to 12.0 million packets per second (Mpps) in a fully loaded chassis. See Chapter 1, “Omni Switch/Router Chassis and Power Supplies,” for more information on the HRE-X .
Page 3-3 Required Image Files See the table below for the required images files for the MPX and switching modules. You must load the image file (or files) listed for the corresponding module or it will not run. Required Image Files Module Image File(s) MPX mpx.
Installing a Switching Module Page 3-4 Installing a Switching Module All switching modules can be inserted and removed from the switch chassis while power is on or off without disrupting the other modules. A standard screwdriver is required for install- ing and removing switching modules.
Installing a Switching Module Page 3-5 2. Once the module is in the slot, close the two card ejectors (one on each end of the module) by pressing them in toward the module until they snap into place. 3. Use a standard screwdriver to tighten the two screw fasteners to secure the module inside the chassis.
Installing a Switching Module Page 3-6 Removing a Switching Module To remove a switching module, follow the instructions below. If you are “hot swapping” the modules (i.e., removing and inserting while power is on), see Hot Swapping a Switching Module on page 3-7.
Hot Swapping a Switching Module Page 3-7 Hot Sw apping a Switching Module You may remove and insert switching modules while the switch is running. This technique is referred to as “hot swapping.” When you hot swap, you must replace the module with the same module type as the one you removed.
Hot Swapping a Switching Module Page 3-8 4. Carefully remove the switching module from the chassis and put it in a safe place. (See Removing a Switching Module on page 3-6 for instructions on removing a switching module.) The MPX’s OK2 LED will flash amber 1 or 2 times, then return to normal flashing green.
Diagnostic Tests Page 3-9 9. If the hot swapping mode has not timed out, enter swap off at the system prompt. Something like the following will then be displayed.
Handling Fiber and Fiber Optic Connectors Page 3-10 Handling Fiber and Fiber Optic Connector s Using fiber is extremely simple, but a few important rules should always be followed: Step 1.
Handling Fiber and Fiber Optic Connectors Page 3-11 2. Keeping your thumb pressed on the cloth-forwarding lever, press the optical plug ferrule endface against the cleaning cloth and drag the plug down toward your body (there should be arrows on the top of the tool that indicate the proper wiping direction).
Gigabit Ethernet Modules Page 3-12 Gigabit Ethernet Modules Gigabit Ethernet connections can be used as network backbones or in a wiring closet. The following Omni Switch/Router Gigabit Ethernet modules are available: • GSX-K-FM/FS/FH-2W Advanced switching module with two (2) Gigabit Ethernet back- bone connections using fiber ( SC ) connectors.
Gigabit Ethernet Modules Page 3-13 ♦ Special Note ♦ The single mode version of this module has been deemed: CLASS 1 LASER PRODUCT LASER KLASSE 1 LUOKAN 1 LASERLAITE APPAREIL A LASER DE CLASSE 1 to IEC 825:1984/CENELEC HD 482 S1 .
Gigabit Ethernet Modules Page 3-14 2-Port Advanced Gigabit Ethernet Switching Module Port LEDs LINK TX RX 1 2 RX TX RX TX 1 2 LINK (Link Status/Disabled). On Green when the corre- sponding port has a valid phys- ical link and a signal is present. Under normal conditions, this LED should always be on when a cable is connected.
Auto-Sensing 10/100 Ethernet Modules Page 3-15 A uto-Sensing 10/100 Ethernet Modules Alcatel’s Omni Switch/Router 10/100 Ethernet modules can be used to connect networks with a mix of 10 Mbps and 100 Mbps workstations or as a network backbone.
Auto-Sensing 10/100 Ethernet Modules Page 3-16 The 32 RJ-45 ports may connect to unshielded or shielded twisted pair ( UTP ) cable (see ESX- K-100C-32W Technical Specifications on page 3-17 for more information). Each port may connect to a single high-speed device or a hub serving multiple devices.
Auto-Sensing 10/100 Ethernet Modules Page 3-17 ESX-K-100C-32W T echnical Specifications Number of ports 32 Connector Type RJ-45 Standards Supported IEEE 802.
Auto-Sensing 10/100 Ethernet Modules Page 3-18 32-Port Advanced Auto-Sensing 10/100 Ethernet Switching Module 1 6 2 3 4 57 8 OK2 OK1 ESX-K 10/100 Module LEDs D C B A 1x 6x 2x 3x 4x 5x 7x 8x 1x 6x 2x 3x 4x 5x 7x 8x 1 6 2 3 4 57 8 1 6 2 3 4 57 8 1 6 2 3 4 57 8 D D Port LEDs Each LED corresponds to a port on the module.
Fast (100 Mbps) Ethernet Modules Page 3-19 F ast (100 Mbps) Ethernet Modules Alcatel’s Omni Switch/Router Fast Ethernet modules can be used to connect networks with 100 Mbps workstations or as a network backbone.
Fast (100 Mbps) Ethernet Modules Page 3-20 ESX-K-100FM/FS-16W T echnical Specifications Number of ports 16 Connector Type MT-RJ Standards Supported IEEE 802.
Fast (100 Mbps) Ethernet Modules Page 3-21 16-Port Advanced Fast Ethernet Switching Module 1 2 3 4 OK1 OK2 Port LEDs 8 5 6 7 4 1 2 3 MT-RJ connectors will be color coded to indicate multimode (Black) or single mode (Blue). ESX-K 100 sm Warning Label .
WAN Modules Page 3-22 W AN Modules The Omni Switch/Router currently supports the following Wide Area Network ( WAN ) modules: • WSX-S-2W Provides two serial ports that support Frame Relay or PPP . • WSX-SC Provides four or eight serial ports that support Frame Relay or PPP with data compression .
WAN Modules Page 3-23 W AN BRI P ort Specifications (S/T Interface) Pin Number Standard Signal Name 1 Not Used 2 Not Used 3 Rcv + from TE 4, Rcv - from TE 5 Xmt + from TE 6 Xmt - from TE 7 Not Used 8.
WAN Modules Page 3-24 WAN Serial Port Numbering W AN T1/E1 P ort Specifications Pin Number Standard Signal Name 1 Rx_Ring 2 Rx_Tip 3 Chassis GND 4, Tx_Ring 5 Tx_Tip 6 Chassis GND 7 Chassis GND (A jumper is provided for connecting Pins 7 and 8 to the chassis ground, if required.
WAN Modules Page 3-25 W AN Serial P ort Specifications Alcatel SPI EIA-530 RS-449 Generic Signal Name Source Mnemonic Pin Mnemonic Pin Mnemonic Pin Shield -- Shield 1 -- 1 -- 1 Signal Ground -- AB 7 .
WAN Modules Page 3-26 W AN Serial P ort Specifications (cont.) X.21/X.26 V.35 RS232 Generic Signal Name Source Mnemonic Pin Mnemonic Pin Mnemonic Pin Shield -- -- 1 -- A -- 1 Signal Ground -- G 8 102.
WAN Modules Page 3-27 WSX-S-2W The WSX-S-2W supports two (2) serial ports, which can provide access rates from 9.6 Kbps to 2 Mbps. The WSX-S-2W also supports three types of clocking (internal, external, and split). See WSX-S-2W Technical Specifications on page 3-27 for more information.
WAN Modules Page 3-28 2-Port WAN Frame Relay Switching Module STA (Status). On Green con- tinuously when the port con- nection is operational. Off when the port is disabled or the cable is detached. Blink- ing On/Off if cable is attached but receive control data is detected as down.
WAN Modules Page 3-29 WSX-SC The WSX-SC supports 4 or 8 serial ports, each of which can provide access rates from 9.6 Kbps to 2 Mbps. The 4-port version is referred to as the WSX-SC-4W , and the 8-port version is referred to as the WSX-SC-8W . The WSX-SC supports STAC hardware compression and three types of clocking (internal, external, and split).
WAN Modules Page 3-30 WSX-SC T echnical Specifications Number of ports 4 or 8 Connector Type High-density 26-pin shielded serial Protocols Supported Frame Relay and Point-to-Point (PPP) Data Rates Supported 9.
WAN Modules Page 3-31 8-Port WAN Frame Relay Switching Module 1 2 3 STA RX TX 4 3 1 2 The module includes one row of LEDs for each port. The LEDs for a given port are located in the row labeled with the port number. If the WSX module includes a total of eight ports, then the module con- tains two sets of four rows of LEDs.
WAN Modules Page 3-32 WSX-FT1/E1-SC The WSX-FT1/E1-SC module contains one or two T1 or E1 ports and one or two serial ports. T1 and E1 ports use RJ-48C connectors. The T1 version of this module is referred to as the WSX-FT1-SC; t he E1 version is referred to as the WSX-FE1-SC.
WAN Modules Page 3-33 WSX-FT1/E1-SC T echnical Specifications Number of ports 1 or 2 T1 or E1 ports 1 or 2 Universal Serial ports Connector Types T1/E1: RJ-48C Serial: High-density, 26-pin shielded S.
WAN Modules Page 3-34 WAN 2-Port Serial and 2-Port Fractional T1/E1 Switching Module This module includes one set of LEDs for each port. The LEDs for a given port are located above the port. If the WSX module includes four ports, then the module con- tains two sets of LEDs.
WAN Modules Page 3-35 WSX-FE1-SC Cabling/Jumper Settings The WSX-FE1-SC supports both twisted pair (120 Ohm) and coaxial (75 Ohm) cable types. The default is 120 Ohm. You must set a pair of jumpers ( JP2 and JP4 ) on the back of the board to correspond to the type of cable you are using.
WAN Modules Page 3-36 WSX-BRI-SC The ISDN Basic Rate Interface WAN Switching Module ( WSX-BRI-SC ) supports either one (1) serial port and one (1) BRI port or two (2) serial ports and two (2) BRI ports.
WAN Modules Page 3-37 WSX-BRI-SC T echnical Specifications Number of ports 1 or 2 pairs of a serial port and an ISDN Basic Rate Interface (BRI) port Serial Connector Type High-density 26-pin shielded.
WAN Modules Page 3-38 WAN 2-Port Serial and 2-Port BRI-ISDN Switching Module 1 2 STA RX TX The WSX-BRI module includes one set of LEDs for each port. The LEDs for a given port are located in the set labeled with the port number.
WAN Modules Page 3-39 J16 S U S U J15 TT TT RT RT J14 S U S U J13 S U BRI P or t Jumper Conf iguration for the “U” Interface The gr ay bo xes ar e the jumper bloc ks This is a simplified view of the bottom lower-right quadrant of the WSX-BRI submodule.
WAN Modules Page 3-40.
Page 4-1 4 The U ser Interface In order to configure parameters and statistics on the switch, you may connect it to a terminal, such as a PC or UNIX workstation, using terminal emulation software. The command interfaces used on the switch are part of the MPX executable image.
Overview of Command Interfaces Page 4-2 Changing Between the CLI and UI Modes Once you log on to the switch, the following screen displays. You must press the <Enter> key to start the command interface.
Overview of Command Interfaces Page 4-3 Exit the Command Interface To exit your current session with the switch from the CLI or the UI mode, type either quit or logout at the prompt, then press <Enter> . Your session is immediately terminated. ♦ Note ♦ If you forget which command interface mode you are in, type the ? character.
UI to CLI Command Cross Reference Page 4-4 UI to CLI Command Cr oss Reference The chapters in this Users Guide are organized around the UI commands as they are grouped into menus and sub-menus. Even though the Omni Switch/Router software has been changed to boot up in the CLI mode, the Users Guide conforms to its original design.
UI to CLI Command Cross Reference Page 4-5 Basic Switch Management T able Chapter UI Command Equivalent CLI Commands PM Family 4, “The User Interface” alert, echo, history, kill, ping, pwd, timeou.
UI to CLI Command Cross Reference Page 4-6 Netw ork Management Commands The table on page 4-6 summarizes the commands supported in the UI and the CLI for Chapters 12 through 14.
UI to CLI Command Cross Reference Page 4-7 Layer II Switching Commands The table on page 4-7 summarizes the features supported in the UI and the CLI for Chapters 15 through 18.
UI to CLI Command Cross Reference Page 4-8 Groups , VLANs, P olicies Commands The table beginning on page 4-8 summarizes the features supported in the UI and the CLI for Chapters 19 through 24.
UI to CLI Command Cross Reference Page 4-9 Group, VLANs , P olicies T able (continued) Chapter UI Commands Equivalent CLI Commands PM Family 22, “Managing AutoTracker VLANs” gmap, gmapst gmapgapti.
UI to CLI Command Cross Reference Page 4-10 Routing Commands The table beginning on page 4-10 summarizes the features supported in the UI and the CLI for Chapters 25 through 27. Routing T able Chapter UI Command Equivalent CLI Commands PM Family 25, “IP Routing” All IP Routing commands are supported in the CLI.
UI to CLI Command Cross Reference Page 4-11 W AN A ccess Commands The table beginning on page 4-11 summarizes the features supported in the UI and the CLI for Chapters 28 through 34.
UI to CLI Command Cross Reference Page 4-12 W AN Access T able (continued) Chapter UI Command Equivalent CLI Commands PM Family 31, “WAN Links” linkadd, linkmodify interface dialer status descript.
UI to CLI Command Cross Reference Page 4-13 Tr oubleshooting Diagnostics Commands The table beginning on page 4-13 summarizes the features supported in the UI and the CLI for Chapters 35 and 36 and Appendices A and B.
User Interface Menu Page 4-14 U ser Interface Menu This menu provides a top-level view of all UI menus. The commands are grouped together in the form of sub-menus.
Main Menu Summary Page 4-15 Main Menu Summary These menus, their sub-menus, and sub-options are described in this manual. The following provides a brief overview of each item on this main menu. File . Contains options for downloading system software, listing software files, copying files, editing files, and deleting files.
General User Interface Guidelines Page 4-16 Diag . This menu, fully available to the diag login account, contains commands to run diagnos- tic tests. It is described in Chapter 36, “Running Hardware Diagnostics.” Quit . Logs you out of the UI . You can also enter logout to exit.
General User Interface Guidelines Page 4-17 ♦ Note ♦ If you cannot see a UI command confirmation prompt or if you do not get the command prompt after the completion of a command, press the <Enter> key to regain the prompt. Quitting a Command Many of the commands give you a list of parameters to change.
General User Interface Guidelines Page 4-18 Configuring the System Pr ompt The uic submenu is listed under the system menu. The uic submenu allows you to change the system prompt. The prompt can be made up of literal information, system variable informa- tion, or a combination of the two.
General User Interface Guidelines Page 4-19 Configuring More Mode for the U ser Interface Enabling More Mode The more mode allows you to specify the maximum number of lines that will be scrolled to your workstation’s display.
General User Interface Guidelines Page 4-20 A screen similar to the following will be displayed. UI Configuration 1) Prompt : ‘$Menu-Path% ’ 2) More : on 21) Lines : 22 lines 3) Verbose : off 4) T.
General User Interface Guidelines Page 4-21 Disabling More Mode To disable more mode, type uic at the user prompt and press <Enter> . A screen similar to the following will be displayed.
General User Interface Guidelines Page 4-22 Setting V erbose/T erse Mode for the U ser Interface Enabling V erbose Mode When verbose mode is enabled, you are not required to enter a question mark in order to view the switch’s configuration menus. Instead, menus are displayed automatically.
General User Interface Guidelines Page 4-23 Disabling V erbose Mode Although the terse command is no longer supported as of Release 4.1, disabling verbose mode via the uic submenu is the command equivalent. When verbose mode is disabled, configuration menus will not be displayed automatically.
General User Interface Guidelines Page 4-24 Configuring the Auto Logout Time When the switch detects no user activity on the UI for a certain period of time, it automati- cally logs the user out of the system. By default, this automatic logout occurs after 4 minutes of console inactivity.
General User Interface Guidelines Page 4-25 Viewing Commands If at any time you are not sure of the commands available, enter ? and you will be given a list of the commands in the current sub-menu. Following each list of commands is a list of sub- menus.
General User Interface Guidelines Page 4-26 Command History and Re-Executing Commands The history command displays up to 50 commands numbered in order with the most recently executed command listed last. The following is a typical example of the history command.
General User Interface Guidelines Page 4-27 In addition, you can re-execute a command by entering an exclamation point ( ! ) followed by the first character(s) of the most recently executed command. In the example at the begin- ning of this section, entering !vim would re-execute the vimcvl command.
General User Interface Guidelines Page 4-28 Abbre viating IP Addr esses The Omni Switch/Router software provides the user with a more concise way to enter the dotted decimal format of a 32-bit IP address. The new syntax conforms to the traditional Inter- net interpretation.
General User Interface Guidelines Page 4-29 This abbreviated IP address format can be used with the ftp , telnet , crgp , modvl , ping , snmpc , and xlat commands. For example, to ping the IP address 198.0.0.2, you can abbreviate this IP address by entering ping 198.
User Interface Display Options Page 4-30 U ser Interface Display Options The System menu several commands to configure help information, character display, and the system prompt for the UI . Enter system at the system prompt to enter the System menu. Press the question mark ( ? ) to see the System menu commands, as shown below.
User Interface Display Options Page 4-31 Setting Echo/NoEcho for U ser Entry You can determine whether your entries will appear by enabling the echo for user entries. The default is to echo all characters. To enable the echo, enter echo at the system prompt.
User Interface Display Options Page 4-32 Creating a ne w Banner Three steps are required to change the login banner. They are listed here. • Create a text file containing the new banner in the switch’s flash directory. • Add the UI_add_do_alert() command syntax to the switch’s mpx.
Login Accounts Page 4-33 Login A ccounts The UI provides three default login accounts—Administrator, User and Diagnostics. The Administrator login provides full access to all functions. The initial login name for an Adminis- trator account is admin .
Multiple User Sessions Page 4-34 Listing Other U sers To display all the users currently logged on to the switch, type who at the system prompt. The following is an example of the display shown where two Telnet sessions are logged in, one as admin and the other as user .
Multiple User Sessions Page 4-35 Communicating with Other U sers If you want to send a message to another user, enter write followed by the user’s session number. If you wanted to send a message to a user connected on the console port (session 0), you would enter write 0 at the system prompt.
Multiple User Sessions Page 4-36 For example, to end the session of the user connected to the console port (session 0) and let him finish his current command, you would enter kill 0 at the system prompt. The system would then display something similar to the following: Press <Enter> to cancel.
Multiple User Sessions Page 4-37 Adv anced Kill Command Options You can also kill the session of a user immediately by adding the parameter -f followed by the session number of the user. This option will kill the user’s session before he can finish his current command.
UI Table Filtering (Using Search and Filter Commands) Page 4-38 UI T able Filtering (U sing Sear ch and Filter Commands) The amount of information displayed in UI tables can be extensive, especially with larger networks. Common UI commands, such as ipr , vivl , macinfo , and fwt , often return multi-page tables.
UI Table Filtering (Using Search and Filter Commands) Page 4-39 The Sear ch Command Starting from the page being displayed, the Search command ( / ) searches all lines of a UI table for a specified text pattern (up to 80 characters).
UI Table Filtering (Using Search and Filter Commands) Page 4-40 2. Type / at the More? prompt. The Search prompt ( / ) will appear automatically. At the Search prompt, enter the text pattern for the desired MAC address. For example: /0020DA:9E479D Press <Enter> .
UI Table Filtering (Using Search and Filter Commands) Page 4-41 The Filter Command The Filter command filters unwanted information from a UI table by displaying only those lines containing a specified text pattern (up to 80 characters).
UI Table Filtering (Using Search and Filter Commands) Page 4-42 2. Type f at the More? prompt. The Filter prompt ( f/ ) will appear automatically. At the Filter prompt, enter the desired text pattern (remember to type the text pattern exactly as it would appear in the UI table): f/Lne Press <Enter> .
UI Table Filtering (Using Search and Filter Commands) Page 4-43 1. Type ipr and press <Enter> . A table similar to the following will be displayed: Note that, because the information in the table exceeds the more command’s default of 22 lines, the More? prompt appears at the bottom of the screen.
UI Table Filtering (Using Search and Filter Commands) Page 4-44 3. In order to further refine your results, you can now combine the Search and Filter commands. In this example, you will search for IP addresses beginning 198.206.2 . To do this, enter / at the Filter mode’s More? prompt, followed by the specified text pattern: /198.
UI Table Filtering (Using Search and Filter Commands) Page 4-45 Single Character s A question mark ( ? ) is used as a wildcard for a single character in a text pattern. For exam- ple, the Search pattern f/127.?.0.1 will locate the first line in a UI table containing 127.
UI Table Filtering (Using Search and Filter Commands) Page 4-46.
Page 5-1 5 Installing Switch Softw ar e User Interface software comes pre-loaded on your MPX . You do not have to reload unless you are upgrading, backing up, or reloading due to file corruption. There are different methods for loading software into your switch.
Using FTP Server Page 5-2 U sing FTP Server The Omni Switch/Router is an FTP server. Using any compatible FTP client software you can load software to and from the switch. Consult the manual that came with your FTP client soft- ware package. The following are general instructions on how to FTP to the switch.
Using FTP Client Page 5-3 U sing FTP Client The User Interface contains several FTP commands. Using these commands is similar to using FTP on a UNIX system. Follow the steps below to start the FTP Client. 1. Log on to the switch and type ftp . For instructions on logging into the switch see the Getting Started Guide that came with your switch.
Using ZMODEM Page 5-4 U sing ZMODEM Normally you use FTP to transfer files to and from the switch. It is faster than using the serial port. A ZMODEM transfer can take several minutes. There are generally two situations which would require you to use the serial port to load software: • You do not have access to an FTP client or server program.
Using ZMODEM Page 5-5 U sing ZMODEM With the Boot Line Prompt If you encounter the situation where you have deleted some or all of the files in your switch, you may need to load files through the boot line prompt. This load procedure is done before the switch has booted.
Using ZMODEM Page 5-6 The [boot] Prompt The [boot] prompt has its own set of commands that are built into the switch. You do not need to have files or software loaded to use this set of commands.
Using ZMODEM Page 5-7 Starting a ZMODEM Tr ansfer at the [boot] Prompt 1. Type c to change boot parameters. You will be changing the boot device to zm . This will tell the system to load files from a ZMODEM connection instead of flash memory. [Boot]: c ‘.
Using ZMODEM Page 5-8.
Page 6-1 6 Configuring Management Pr ocessor Modules The management processor module ( MPX on the Omni Switch/Router) coordinates control of the Omni Switch/Router by providing access to the User Int.
Changing Serial Port Communication Parameters Page 6-2 Changing Serial P ort Communication P ar ameter s The serial communications parameters for the two MPX ports are set by default to the follow- in.
Changing Serial Port Communication Parameters Page 6-3 Enter the port mode and press <Enter> . This option defaults to console for a console connection and down for a modem connection. You can also configure the port for SLIP. If you are configuring the modem port, you should plan the mode configuration care- fully.
Changing Serial Port Communication Parameters Page 6-4 This configuration does not allow you to use the console port as an optional access method since it is configured down. Using a cross-over cable, you could access the modem port through an attached PC.
Configuring the Ethernet Management Port Page 6-5 Configuring the Ethernet Management P ort To configure the Ethernet management port, you use the ethernetc command. To use this command, enter ethernetc at the system prompt. A screen similar to the following will be displayed.
Configuring the Ethernet Management Port Page 6-6 2) IP Addr ess Enter an IP address for the Ethernet management port in dotted decimal or hexadecimal nota- tion (the default is 192.168.11.1 ). For example, to change the Ethernet management port’s IP address to 198.
Ethernet Management Ports and Redundant Management Processor Modules Page 6-7 Ethernet Management P orts and Redundant Management Pr ocessor Modules If redundant MPXs both have Ethernet management ports ( EMPs ), both EMPs in the switch will have the same IP address if automatic file synchronization is enabled.
Ethernet Management Ports and Redundant Management Processor Modules Page 6-8 12. Enter save at the prompt to save the IP address. 13. Enter renounce at the prompt to make the management module that was originally the primary one primary again.
The MPM Command/Menu Page 6-9 The MPM Command/Menu The mpm command has two functions: displaying the MPX redundancy configuration and entering the mpm menu. Displaying the MPX redundancy is described below and the mpm menu is described in MPM Menu Commands on page 6-9.
The MPM Command/Menu Page 6-10 All of the mpm menu commands, except for the nisuf and swap commands, function only if you have redundant MPXs . If you are connected to the secondary MPX , type a ? to list the mpm commands shown below.
Listing the Secondary MPX Files Page 6-11 Listing the Secondary MPX Files The sls command lists the files in the secondary MPX module. This is similar to the ls command; however, it lists files in the secondary MPX . To list files in the secondary MPX , enter sls at the system prompt.
Replacing a File on the Secondary MPX Page 6-12 Replacing a File on the Secondary MPX The mpmreplace command replaces a file on the secondary MPX . It works like a combination of mpmrm , which is desc.
Removing a File from the Secondary MPX Page 6-13 Remo ving a File from the Secondary MPX The mpmrm command removes (deletes) a file from the flash memory of the secondary MPX . To use this command, enter mpmrm , followed by a space, a slash ( / ), the name of the flash directory, another slash ( / ), and the name of the file you want to remove.
Giving Up Control to the Secondary MPX Page 6-14 Giving Up Contr ol to the Secondary MPX The renounce command tells the primary MPX to give up control and become the secondary MPX . It does this by issuing a request to the secondary MPX to take control.
Setting Automatic Config Synchronization Page 6-15 Setting A utomatic Config Synchronization The syncctl command sets the automatic configuration synchronization to Enabled or Disabled. If it is Enabled, then the MPX primary/secondary pair will continue to maintain synchronization automatically.
Synchronizing Configuration Data Page 6-16 Synchr onizing Configuration Data The configsync command copies the configuration files ( mpm.cnf and mpm.cfg ) in the primary MPX to the secondary MPX . You can run this command whether or not automatic config synchronization is on.
Loading a File From the Primary MPX Page 6-17 Loading a File Fr om the Primary MPX The mpmget command loads a file from the primary MPX and copies it into the secondary MPX .
Gaining Control from the Primary MPX Page 6-18 Gaining Contr ol from the Primary MPX The takeover command tells the secondary MPX to take control and become the primary MPX . It does this by issuing a request to the primary MPX to relinquish control. You must be logged into the secondary MPX to use this command.
Resetting a Secondary MPX Page 6-19 Resetting a Secondary MPX The secreset command initiates a soft reset on the secondary MPX . Conceptually, resetting a secondary MPX with this command is similar to switching off power to the module; the MPX will be in the same state after a reset as it is after a power on.
Displaying and Setting the Swap State Page 6-20 Displaying and Setting the Sw ap State The swap command displays or alters the swap state of the chassis. The swap state must be on in order to hot swap modules. If not, the system may halt or restart. While the swap state is on, performance may decrease.
Displaying and Setting the Swap State Page 6-21 Disabling the Swap Mode Normally, the swap mode will timeout and no user intervention is required. However, you can manually turn the swap mode off. This function is particularly useful since the perfor- mance of the switch can be adversely affected if the swap mode is enabled.
Displaying and Setting the Swap State Page 6-22.
Page 7-1 7 Managing Files Depending on the model type and configuration, an Alcatel switch has anywhere from 8 or 16 MB of usable flash memory. This memory is used to store files, including executable files (used to operate switching modules), configuration files, and switch usage log files.
Displaying the Current Directory Page 7-2 Displaying the Curr ent Directory To display the switch’s current directory, enter pwd at the system prompt. The working directory will be the /flash memory system and the corre- sponding directory information will be displayed: /flash Configuration and Log File Gener ation The mpm.
Listing Switch Files Page 7-3 Listing Switch Files You can use the ls command to list the files in the primary MPX ’s flash memory. To use this command, enter ls at the system prompt. A screen similar to the following will be displayed. mpx.cmd 18 05/30/98 13:04 mpm.
Deleting Switch Files Page 7-4 Deleting Switch Files You can use the rm command to delete files in the primary MPX’s flash memory. To use this command, enter rm , followed by the name of the file you want to delete. For example, to delete the file mpm.
Deleting Switch Files Page 7-5 Deleting All Image Files You can use the imgcl command to delete all executable (image) files. The files deleted by the imgcl command include the MPX boot file ( mpx.img ), and all executable switching module files (the factory default is all files ending with the .
Copying System Files Page 7-6 Cop ying System Files You can use the cp command to copy files. This is particularly useful if you want to make backups of important files. To use this command, enter cp , followed by the name of the origi- nal file you want to copy, and then by the name that you wish to give the duplicate file.
Editing Text Files Page 7-7 Editing T ext Files The commands in the Edit sub-menu (also called the Text Buffer or Edit Buffer) are used to create new text files and to modify existing text files. To enter the edit sub-menu, enter edit at the system prompt.
Editing Text Files Page 7-8 Loading an ASCII File into the T ext Buffer You can use the rb command to load—or read —an existing ASCII file in flash memory to the Edit buffer’s memory. To use this command, enter rb , followed by the file you wish to edit.
Editing Text Files Page 7-9 Deleting a Line of T ext fr om the T ext Buffer You can use the db command to delete a specific line in the text buffer. To use this command, enter db , followed by line number of the line of text you want delete, which is shown by the lb command.
Editing Text Files Page 7-10 Creating a File N ame for the T ext Buffer If no file name has been created for the text buffer, the following message is displayed when- ever the lb command is executed: Work buffer is unnamed Use the nb command to create a name for the text buffer.
Real-World Examples Page 7-11 Real-W orld Examples As noted on page 10-7, when you edit text files, you will normally use several of the Edit sub- menu commands to produce the results you want.
Real-World Examples Page 7-12 Real-W orld Example 2 cp mpx.cmd mpx.bak rb mpx.cmd lb 00: cmDoDump=1 01: cmInit 02: reg_port_rule=1 nb mpx.cmd Work buffer name is: /flash/mpx.cmd db 2 lb 00: cmDoDump=1 01: cmInit ib 1 01 : 01 : rifStripping=1 lb 00: cmDoDump=1 01: rifStripping=1 02: cmInit Work buffer name is: /flash/mpx.
System Menu Page 7-13 Sy stem Menu The System menu contains two commands, fsck and newfs , for checking and deleting all files in the flash memory. To access the System menu, enter system at the UI prompt. If verbose mode is enabled, the following list of commands will be displayed automatically.
Checking the Flash File System Page 7-14 Checking the Flash File Sy stem The fsck command performs a file system check of flash memory, which consists of the flash file system. All image files are stored in flash memory and loaded into system memory when the switch boots up.
Creating a New File System Page 7-15 Cr eating a Ne w File System The newfs command removes a complete flash file system and all files within it, replacing it with a new empty flash file system. Use this command when you want to reload all files in the file system, or in the unlikely event that the flash file system becomes corrupted.
Creating a New File System Page 7-16.
Page 8-1 8 Switch Security Commands listed in the Security menu are for configuring system security parameters such as the password and logout time. The menu also provides a command for rebooting the switch. Enter security at the prompt to enter the Security menu.
Changing Passwords Page 8-2 Changing P asswor ds The switch provides three types of login accounts by default—Administrator, User and Diag- nostics. The Administrator login provides full READ/WRITE access to all command families. The login name for the Administrator account is admin .
Rebooting the Switch Page 8-3 Rebooting the Switch The reboot command should only be executed during network down time and when no data is being transmitted across the network. Also, you should ensure that all configuration infor- mation has been saved first.
Secure Switch Access Page 8-4 Secur e Switch Access Secure Switch Access is a filtering program that prevents unauthorized access to the switch by allowing you to define a list of filters and filter points . For Secure Switch Access, filters are lists of source traffic that are allowed onto the switch.
Secure Switch Access Page 8-5 Create This option allows you to create a new filter in the secure access database. The following is a sample display: Create Filter ------------------ Enter Filter Name: Enter IP Address ( [a.
Secure Switch Access Page 8-6 Modify This option allows you to modify information about an existing secured access filter. Enter the name of the filter you wish to modify, as follows: Modify Filter ----------------- Filter Name: Test The filter’s existing information will display.
Secure Switch Access Page 8-7 Configuring Secure A ccess Filter P oints The secapply command allows you to view the list of secure access filter points, to enable/ disable security globally or for a specific IP protocol filter point, and to define a filter list for each filter point.
Secure Switch Access Page 8-8 1) FTP Security Indicates whether or not secure access is enabled for File Transfer Protocol ( FTP ) on the switch. Enabled means secure access is enabled for FTP services, and only filters on FTP ’s filter list have authorization.
Secure Switch Access Page 8-9 7) One-touch Security Configures the same Security value for all secure access protocols. Enabled enables security for all secure access filter points. Disabled disables security for all secure access filter points. Any value configured for individual security parameters overrides the global setting.
Secure Switch Access Page 8-10 Viewing Secur e Access Violations Log The seclog command displays a log of all secure access violations. ♦ Note ♦ To log access violations on the switch, use the swlogc command. For more information on the swlogc command, see Chapter 10, “Switch Logging.
Managing User Login Accounts Page 8-11 Managing U ser Login Accounts Prior to software release 4.4, the switch provided security in the form of privilege control for individual login accounts by allocating each user accounts READ or WRITE privileges. Soft- ware release 4.
Managing User Login Accounts Page 8-12 Default Accounts Initially each switch is preconfigured with three default logins ( admin, user and diag ). See Chapter 4, “The User Interface,” for more information about login accounts.
Managing User Login Accounts Page 8-13 Adding a U ser Account U sing the CLI Command Mode To add a user account from the CLI mode, you must be logged into an account with adminis- trative privileges.
Managing User Login Accounts Page 8-14 U ser Write Privileges To assign privileges to a user account, you must be logged into an account with WRITE privi- leges to the USER family of commands.
Managing User Login Accounts Page 8-15 Miscellaneous CLI Privileges Commands The following is a list of privileges-related CLI commands. For more details on these commands and other CLI commands, refer to the Text-Based Configuration CLI Reference Guide .
Managing User Login Accounts Page 8-16 Assigning Account Privileges U sing the UI Command Mode When you add a new user login account, the account has permission to log in and to log out. If you want the new account to have additional privileges you must add them separately.
Managing User Login Accounts Page 8-17 This screen displays the default privileges for a new user login account. Note that the default privileges give the new user neither read nor write permission. To grant privileges to the user account, enter a number from 1 to 5 as indicated in the display.
Managing User Login Accounts Page 8-18 The global family contains commands that apply globally to the switch rather than to individ- ual applications or services. Privileges for global family commands can be set on an individ- ual command basis or altogether so the privilege applies to the whole global family.
Managing User Login Accounts Page 8-19 For example, if you wanted to assign the user account the privilege to use the define command, enter the number 6 as shown here. Give the family number : ( ) : 6 The following will display. Give rights on subset DEFINE 0.
Managing User Login Accounts Page 8-20 Modi fying a U ser Account You can use the usermod command to modify account privileges as shown here. You must be logged into a user account with administrative privileges. 1. At the system prompt enter the usermod command.
Page 9-1 9 Configuring Switch-Wide P ar ameter s The switch provides commands to display and configure parameters on a switch-wide basis. These commands are grouped into two menus: the Summary menu and the System menu. Descriptions for commands in the Summary menu begin below; descriptions for commands in the System menu begin on page 9-5.
Displaying the MIB-II System Group Variables Page 9-2 Displaying the MIB-II Sy stem Group V ariables MIB-II is a core set of definitions created to define the SNMP -based management framework. This MIB module contains definitions for both end systems and routers using the Internet protocol suite.
Displaying the Chassis Summary Page 9-3 Displaying the Chassis Summary To display the chassis summary information, enter sc at the system prompt. A screen similar to the following will be displayed. Type: Omni Switch/Router XFRAME 9-slot Chassis ID: Alcatel Description: DESCRIPTION NOT SET.
Displaying Current Router Interface Status Page 9-4 Displaying Curr ent Router Interface Status To display current interface status information, enter si at the system prompt.
System Menu Page 9-5 Sy stem Menu The System menu contains commands to view or set system-specific parameters. To access this menu, enter system at the UI prompt to enter the System menu. If you are not in verbose mode, press a question mark ( ? ) and then press <Enter> to display the commands in the system menu, as shown below.
Displaying Basic System Information Page 9-6 Displaying Basic Sy stem Information To display basic information on the switch, enter info at the system prompt. The following display is a typical example. System Make: Alcatel OmniSwitch System Type: 5-slot OmniSwitch Description: DESCRIPTION NOT SET.
Displaying Basic System Information Page 9-7 No. of Resets to the System . The number of times this switch has been reset since the last cold start. ♦ Note ♦ The info command will also display the number of MPXs , their location in chassis, and which one is the primary and which one is the secondary.
Setting the System Date and Time Page 9-8 Setting the Sy stem Date and Time The dt command allows you to set the local date, time, and time zone. Additionally, you can set the system clock to run on Universal Time Coordinate ( UTC or GMT ). If applicable, you can also configure Daylight Savings Time ( DST ) parameters.
Setting the System Date and Time Page 9-9 3) Timezone This parameter specifies the time zone for the switch and sets the system clock to run on UTC time (or Greenwich Mean Time). Additionally, if Daylight Savings Time is enabled (see option 4 below), the clock automatically sets up default DST parameters (if applicable) for the local time zone.
Setting the System Date and Time Page 9-10 Timezone and DST Parameters Abbr. Name Hours from UTC DST Start DST End DST Change NZST New Zealand +12:00 1st Sunday in Oct. at 2:00 a.m. 3rd Sunday in March at 3:00 a.m. 1:00 ZP11 No standard name +11:00 No default No default No default AEST Australia East +10:00 Last Sunday in Oct.
Setting the System Date and Time Page 9-11 Timezone and DST Parameters Con’t Abbr. Name Hours from UTC DST Start DST End DST Change GMT Greenwich Mean Time +0:00 No default No default No default WAT.
Setting the System Date and Time Page 9-12 4) Daylight Savings Time active Enables and disables DST (Daylight Savings Time). To enable DST , enter: 4=Enable To disable DST , enter: 4=Disable If DST is disabled, options 41-49 will not be displayed. 41) DST Start Month Indicates which month of the year DST starts.
Setting the System Date and Time Page 9-13 46) DST End W eek Indicates which week in a month DST ends. To set the week DST should end, enter the sequential number of the week.
Viewing Slot Data Page 9-14 Vie wing Slot Data You can view slot table information by entering the slot command. To view information on a particular slot, enter the slot command together with the slot number. For example, to view information for slot 1, enter slot 1 at the system prompt.
Viewing System Statistics Page 9-15 Vie wing System Statistics The systat command displays statistics related to system, power, and environment. To view these parameters, enter systat at the system prompt. A screen similar to the following will be displayed.
Clearing System Statistics Page 9-16 Clearing Sy stem Statistics You may want to clear statistics for a specific module, port or service for dialogistic or accounting purposes. To clear switch statistics enter clearstat at the system prompt. A screen similar to the following will display.
Viewing Task Utilization Statistics Page 9-17 Vie wing T ask U tilization Statistics The taskstat command displays the task utilization statistics of the switch. To display the task utilization statistics, enter taskstat <task-number> <sample-period> at the system prompt.
Viewing Task Utilization Statistics Page 9-18 PRI . Priority of the specified task. STATUS . Current status of the specified task. PC . Program Counter. The program counter identifies the routing code as it enters the stack. SP . Stack pointer. The stack pointer points to the code being loaded when the status is taken.
Viewing Memory Utilization Page 9-19 Vie wing Memory Utilization The leak monitor diagnostic utility is used to display information about memory utilization. This utility requires the use of three UI commands: leakstart , leakstop and leakdumpall . ♦ Note ♦ You may want to log this operation to a text file to make it easier to view the data.
Viewing MPX Memory Statistics Page 9-20 Vie wing MPX Memory Statistics The memstat command displays the MPX’s memory statistics. The statistics will tell you how memory is currently being used and help determine if memory problems exist, such as memory exhaustion.
Checking the Flash File System Page 9-21 Checking the Flash File Sy stem The fsck command performs a file system check of flash memory, which consists of the flash file system. Image files are stored in flash memory and loaded into system memory when the switch boots up.
Creating a New File System Page 9-22 Cr eating a Ne w File System The newfs command removes a complete flash file system and all files within it. It then creates a new flash file system, which is empty.
Configuring System Information Page 9-23 Configuring Sy stem Information You can enter or modify a description of a switch, its location, and a contact person. Although this information is not required, you may find it helpful in managing the switch.
Viewing CAM Information Page 9-24 Vie wing CAM Information The camstat command displays information and usage about the content addressable memory ( CAM ) on each switching module in the chassis. To view this CAM information, enter camstat at the system prompt.
Configuring CAM Distribution Page 9-25 Configuring CAM Distribution CAM (Content Addressable Memory) on switching modules is used to look up the MAC address of endstations attached to the modules. You can use the camstat command to display each module’s CAM usage.
Configuring CAM Distribution Page 9-26 A message similar to the following will display: Slot 3 Configured to learn 256 MACs will round up to 256 MACs This configuration will take effect only after system reboot 3. The new CAM configuration will take effect after you reboot the system.
Configuring the HRE-X Router Port Page 9-27 Configuring the HRE-X Router P ort Various services in the switch use the HRE-X router port MAC registers. The registers are allo- cated as the services are loaded at startup. The hrex submenu contains five commands for use with the Hardware Routing Engines ( HRE s).
Configuring the HRE-X Router Port Page 9-28 For example, to assign register 3 to the Classical IP service enter hrexassign 3 cip at the system prompt. A screen similar to the following is displayed. HRE-X RPM 3 configured for “CIP”; reboot to make effective.
Configuring the HRE-X Router Port Page 9-29 Configuring and Displaying the HRE-X Hash T able The HRE-X s use a hardware implemented hash table to route packets for transmission. The switch employs a default hash function that works well in a broad range of data environ- ments.
Duplicate MAC Address Support Page 9-30 Duplicate MA C Addr ess Support When the switch sees the same MAC address sending traffic on a different switch port (a Duplicate MAC Address), it assumes the original network device moved. The switch sends a trap notifying network management of this station move event.
Duplicate MAC Address Support Page 9-31 If your network supports duplicate MAC addresses, there may be a significant performance impact due to the following reasons: •A MAC address is usually stored only in the CAM of the switching module where its desti- nation address is located.
Multicast Claiming Page 9-32 Multicast Claiming Multicast claiming can be enabled for networks with heavy multicast traffic. When enabled, multicast claiming frees the MPX from processing multicast packets by off-loading this traffic to the switching modules.
Saving Configurations Page 9-33 Saving Configur ations Under normal conditions, configurations you make using the UI are written into cache and automatically saved into the switch’s flash memory. In this case, it is not necessary to issue a special command to save your configurations.
Saving Configurations Page 9-34 To determine whether you are in the cache configuration mode, enter the cacheconfig command. If cache config is operational the following message will display one of the follow- ing messages. Cache Configuration is currently on.
Page 10-1 10 Switch Logging Logging Ov erview Whether you are troubleshooting, configuring, or simply monitoring the switch, you may find it useful to view a history of various switch activities. The Logging submenu contains a list of commands for viewing and configuring logging on the system.
Configuring the Syslog Parameters Page 10-2 Configuring the Sy slog P arameter s Syslog messages are messages generated by individual processes in the switch. These messages contain information for conditions that range from debugging to emergency error conditions.
Configuring the Syslog Parameters Page 10-3 Default facility code The facility code is used to identify which sub-system generated the syslog message. Note that this code is used only as a default for tasks that do not have a facility code. See the table below for a list of the facility codes.
Configuring the Syslog Parameters Page 10-4 Override internals This field will force all syslog messages to use the default priority mask specified instead of their own predefined priority masks. Display internals This field allows the user to display the task log level.
Configuring the Syslog Parameters Page 10-5 Log T ask ID Determines whether or not you want to see the task ID that can be included in the syslog message. U se T ask Name This allows the user to display descriptive task names for syslog messages (see the Display internals sub-menu above) instead of numeric codes.
Configuring Switch Logging Page 10-6 Configuring Switch Logging Switch logging is a feature that allows you to activate and configure the logging of various types of switch information.
Configuring Switch Logging Page 10-7 3) Flash File Logging Flash file logging records debug information from the code that manages the switch logging feature itself (previously called “flash file system logging”). To enable flash file logging, enter 3=enable .
Configuring Switch Logging Page 10-8 In addition to enabling or disabling each type of logging, you can also specify whether to output the log to a file or to the console: Output to File Set to yes ( y ) to store the log messages in the mpm.log file. Set to no ( n ) to disable send- ing log messages to this file.
Displaying the Command History Entries in the MPM Log Page 10-9 Displaying the Command History Entries in the MPM Log The cmdlog command displays a list commands executed since User Interface (UI) facility logging was activated by the swlogc command (described in Configuring Switch Logging on page 10-6).
Displaying the Connection Entries in the MPM Log Page 10-10 Displaying the Connection Entries in the MPM Log The conlog command displays a list of connections made since console event, FTP , or Telnet logging was activated by the swlogc command (described in Configuring Switch Logging on page 10-6).
Displaying Screen (Console) Capture Entries in the MPM Log Page 10-11 Displaying Scr een (Console) Capture Entries in the MPM Log The caplog command displays the screen capture entries in the mpm.
Displaying Screen (Console) Capture Entries in the MPM Log Page 10-12 4) Telnet (1) . Displays screen capture entries for the user logged in from the second telnet session. 5) Telnet (2) . Displays screen capture entries for the user logged in from the third telnet session.
Displaying Debug Entries in the MPM Log Page 10-13 Displaying Debug Entries in the MPM Log The debuglog command displays the debug entries in the mpm.log file. ( Note: Currently there are no facilities using debugging. ) Below is a sample display of the debuglog command.
Displaying Secure Access Entries in the MPM Log Page 10-14.
Page 11-1 11 Health Statistics The health statistics feature monitors the consumable resources of a switch, and provides a single integrated source for Network Management Software ( NMS ), such as X-Vision, to use in obtaining statistics on switch performance.
Setting Resource Thresholds Page 11-2 Setting Resour ce Thresholds The health statistics software operates by monitoring set threshold levels on consumable resources. When a resource exceeds a set level, a trap is generated and sent. These threshold levels are set for the entire switch (or device) by using the hdcfg command.
Setting Resource Thresholds Page 11-3 Setting Bandwidth Thr esholds Bandwidth is a measure of the amount of traffic a switch can handle for receiving, sending, and on the backplane.
Setting Resource Thresholds Page 11-4 Backplane Threshold The backplane threshold sets a percentage of total backplane bandwidth of the switch, module, or port. When backplane usage exceeds this percentage, an SNMP trap is sent. ♦ Note ♦ When “U-turn” switching (i.
Setting Resource Thresholds Page 11-5 CAM Threshold (MPM/HRE or NI) The CAM threshold sets a percentage of the total amount of space available for storing the cache tables. Cache tables maintain associations between received MAC addresses and the ports they were received on.
View Switch-Level Statistics Page 11-6 Setting the Sampling Interv al The sampling interval is the time interval between polls of the switch’s consumable resources to see if it is performing within the set thresholds. To set the amount of time between polls: 1.
View Module-Level Statistics Page 11-7 For field descriptions of the device resources column, see Setting Bandwidth Thresholds on page 11-3 and Setting Miscellaneous Thresholds on page 11-4 above. ♦ Note ♦ When calculating percentages, the health statistics cannot display less than one percent.
View Port-Level Statistics Page 11-8 For descriptions of the statistics, see View Switch-Level Statistics on page 11-6. ♦ Note ♦ The CPU and memory resources are not applicable to the module level statistics display, and therefore are not shown.
Page 12-1 12 N etw ork Time Pr otocol Intr oduction The Network Time Protocol ( NTP ) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver.
Page 12-2 Stratum Stratum is the term used to define the relative proximity of a node in a network to a time source (such as a radio clock). Stratum 1 is the server connected to the time source itself. (In most cases the time source and the stratum 1 server are in the same physical location.
Page 12-3 Servers 1a and 1b receive time information from, or synchronize with, a UTC time source such as a radio clock. (In most cases, these servers would not be connected to the same UTC source, though it is shown this way for simplicity.
Page 12-4 When planning your network, it is helpful to use the following general rules: • It is usually not a good idea to synchronize a local time server with a peer (in other words, a server at th.
Network Time Protocol Management Menu Page 12-5 N etwork Time Pr otocol Management Menu To access the NTP management menu, connect to a switch via a console or telnet session and enter NTP at the system prompt.
NTP Configuration Menu Page 12-6 NTP Configur ation Menu To view the NTP configuration menu, enter the ntconfig command at the system prompt. If you are in verbose mode the NTP configuration menu is displayed.
NTP Configuration Menu Page 12-7 Field Descriptions The following section describes the fields displayed using the ntpconfig command. 1) Response timeout This field sets the timeout period for responses to server queries. Server queries come from the server responsible for providing this client with NTP time information.
NTP Configuration Menu Page 12-8 Configuring an NTP Client/Server A switch can be configured to act both as a client and a server. If you want to run both the client and server portions of the NTP software, follow the steps below: 1.
NTP Configuration Menu Page 12-9 Field Descriptions The following section describes the expanded menu options. 61) Client limit This field allows you to set a specific number of clients that are allowed to make requests of the server during a specified time period.
NTP Configuration Menu Page 12-10 2. Adjust the configurable variables for this NTP client as needed by entering the line number, and equal sign, and a new value at the system prompt, as shown: <li.
NTP Configuration Menu Page 12-11 Field Descriptions The following section describes the expanded menu options. 31) Configuration info authentication ke y The number of the key in the key file used to authenticate configuration information. Config- uration information sets configuration parameters.
NTP Configuration Menu Page 12-12 Configuring a Ne w P eer Association When you have configured the NTP client and/or server, you will need to set at least one peer association for the switch.
NTP Configuration Menu Page 12-13 Configuring a Ne w Server For the switch to synchronize its time, you must specify a server, or servers, from which the switch receives time information.
NTP Configuration Menu Page 12-14 For example, to add broadcast address 1.1.1.1 with a key identifier of 5, using version 3 of NTP , and a minimum poll time of 16 seconds, you would enter the following: ntpbcast 1.1.1.1 5 3 4 When you have finished press <return> .
NTP Information Menu Page 12-15 NTP Information Menu To view the NTP configuration menu, enter the ntinfo command at the system prompt. If you are using verbose mode, the NTP configuration menu is displayed.
NTP Information Menu Page 12-16 Server (4) This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved.
NTP Information Menu Page 12-17 Field Descriptions The following sections describe the fields displayed using the ntppeers command Remote . The IP address of the remote association. Local . The local interface address assigned by NTP to the remote association.
NTP Information Menu Page 12-18 Display Detailed Information for One or Mor e P eers The ntpshowpeer command allows you to view detailed NTP information about any remote associations of this switch.
NTP Information Menu Page 12-19 Precision . The advertised precision of this association, which is a number from -4 to -20. For information on setting the advertised precision, see Configuring an NTP Client on page 12-6 and Set the Server’s Advertised Precision on page 12-14.
NTP Information Menu Page 12-20 Flags Config . This counter lists what flags have been configured for this NTP entity. For more information about setting flags, see Set a System Flag (Auth, Bclient, Monitor, Stats) on page 12-35. Reference Time . This is the local time, in timestamp format, when the local clock was last updated.
NTP Information Menu Page 12-21 Display Local Server Information The ntpinfo command is used to display information about the local switch’s implementation of NTP . To view local switch NTP information, enter the ntpinfo command at the system prompt.
NTP Information Menu Page 12-22 Reference time . This is the local time at which the local clock was last set or corrected. System Flags . This counter lists what flags have been configured for this NTP entity. For more information about setting flags, see Set a System Flag (Auth, Bclient, Monitor, Stats) on page 12-35.
NTP Statistics Menu Page 12-23 NTP Statistics Menu To view the NTP Statistics Menu, enter the ntstats command at the system prompt. If you are in verbose mode the NTP configuration menu is displayed.
NTP Statistics Menu Page 12-24 Field Descriptions The following section describes the fields displayed using the ntpstat command. system uptime . The number of seconds the local NTP server has been associated with the switch. time since reset . The number of seconds since the last time the local NTP server was restarted.
NTP Statistics Menu Page 12-25 Field Descriptions The following section describes the fields displayed using the ntppstat command. remote host . The IP address of the host whose statistics you are viewing. local interface . The local interface address assigned by NTP to the remote association.
NTP Statistics Menu Page 12-26 Display Loop Filter Information The loop filter is used to control and correct the phase of timestamps as processed by the local clock. The loop filter examines timestamps sent to and from the local clock and can adjust them to account for natural wander and jitter.
NTP Statistics Menu Page 12-27 calls to findpeer . The number of times the switch sent an NTP packet of any kind to a config- ured NTP association. new peer allocations . The number of new NTP associations created since the last restart. peer demobilizations .
NTP Statistics Menu Page 12-28 Display Event Timer Subs ystem Statistics The ntptimer command allows you to view significant NTP events that have occurred on this switch. To view significant NTP events, enter the ntptimer command at the system prompt.
NTP Statistics Menu Page 12-29 It is possible to reset the statistics for more than one NTP association at a time by adding more than one address to the command. For example, to reset statistics for a peer with IP address 1.1.1.4 and a peer with IP address 1.
NTP Statistics Menu Page 12-30 bad offset on input . The number of NTP timestamps received that the switch disallowed because the added time offset parameter appeared to be incorrect. This can occur if an NTP entity becomes unsynchronized and generates false timestamp information.
NTP Statistics Menu Page 12-31 leap less than month away . A scheduled leap second insertion less than a month away. leap less than day away . A scheduled leap second insertion less than a day away. leap in less than 2 hours . A scheduled leap second insertion less than two hours away.
NTP Statistics Menu Page 12-32 Field Descriptions The following section describes the fields displayed using the ntpmlist command. remote address . The IP address of the remote association. port . The port the association was learned on and on which the association communicates with the switch.
NTP Administration Menu Page 12-33 NTP A dministration Menu To view the NTP Administration Menu, enter the ntadmin command at the system prompt. If you are using verbose mode the NTP configuration menu is displayed.
NTP Administration Menu Page 12-34 Speci fy the Host Whose NTP Server W e T alk T o The ntphost command specifies the name of the NTP server to which server queries are sent. This can be a domain name or an IP address. The default is localhost (the local server).
NTP Administration Menu Page 12-35 Set Ke y Type to U se for Authenticated Requests (DES|MD5) NTP supports two types of encryption: DES or MD5. If you decide to use encryption to authenticate NTP information and configuration requests, you must specify which type of encryption to use.
NTP Access Control Menu Page 12-36 NTP A ccess Control Menu To view the NTP Access Control Menu, enter the ntaccess command at the system prompt. If you are using verbose mode the NTP configuration menu is displayed.
NTP Access Control Menu Page 12-37 Change the Contr ol Message Authentication K ey ID There are two types of messages an NTP entity can send to another NTP entity: request and control. Control messages attempt to change the configuration of the NTP entity in some fash- ion.
NTP Access Control Menu Page 12-38 Remov e One or More K ey ID's fr om the Trusted List The trusted list in the key file is a list of all keys that are considered authentic and uncompro- mised. Messages from an NTP entity using one of these keys are accepted and acted upon.
NTP Access Control Menu Page 12-39 Create Restrict Entry/A dd Flags to Entry It is possible to place restriction flags on specific NTP entities in relation to the switch. Restric- tion flags prevent messages or information coming from the NTP entity from affecting the switch.
NTP Access Control Menu Page 12-40 limited These hosts are subject to a limitation of the number of clients from the same net. Net in this context refers to the IP notion of net (class A , class B , class C , etc.
NTP Access Control Menu Page 12-41 Remov e Flags from a Restrict Entry It is possible to place restriction flags on specific NTP entities in relation to the switch. Restric- tion flags prevent messages or information coming from the NTP entity from affecting the switch.
NTP Access Control Menu Page 12-42 Display the Tr aps Set in the Server The ntpvtrap command allows you to view a list of trap receivers set for the server. To view the trap list, enter the ntpvtrap command at the system prompt. A display similar to the following is shown: address 127.
Page 13-1 13 SNMP (Simple N etw ork Management Pr otocol) Intr oduction Simple Network Management Protocol ( SNMP ) is an application layer protocol that allows network devices to exchange management information. SNMP works by sending messages, called protocol data units ( PDUs ), to network devices.
Configuring SNMP Parameters and Traps Page 13-2 Configuring SNMP P arameter s and T r aps The snmpc command allows you to configure SNMP parameters and set traps that will be sent to network management stations. The snmpc command also enables you to add, modify, or delete SNMP parameters.
Configuring SNMP Parameters and Traps Page 13-3 3) Set Community Name The Set Community Name variable is a password (up to 16 characters) that enables NMS stations to read and write objects through SNMP . The default Set Community Name is “public,” which allows all NMS stations read access to readable objects.
Configuring SNMP Parameters and Traps Page 13-4 6) Broadcast T raps When broadcast traps are enabled, the switch transmits traps to all NMS stations in the default group. If you enable this parameter, unicast traps (see option 6 below) will automatically be disabled.
Configuring SNMP Parameters and Traps Page 13-5 Here is a sample configuration for setting a combination of traps. Bit Configurations for Setting Traps Example: T o set a combination of trap types, ad.
Configuring SNMP Parameters and Traps Page 13-6 e. The following prompt displays: Special Access? (no): yes Select whether or not this Network Management Station has special access. If you enter yes , this NMS will have administrative privileges such as modifying, deleting, or adding to other trap entries as well as its own.
Configuring SNMP Parameters and Traps Page 13-7 Please note that any additional NMS entries must have a unique IP address. Repeat steps b through f to continue configuring additional NMS entries. Once you save your configura- tion and re-enter the snmpc command at the prompt, the screen refreshes to include the new NMS entry.
Configuring SNMP Parameters and Traps Page 13-8 Viewing SNMP Statistics The snmps command is used to display SNMP statistics. The command displays the SNMP activities since the last time the switch was powered on, or since the last Reset was executed.
Configuring SNMP Parameters and Traps Page 13-9 Bad Type Discar ds The total number of SNMP entries discarded because the request type was not recognized. ASN P arse Error s The total number of ASN.1 or BER errors encountered by the SNMP protocols entity when decoding received SNMP Messages.
Configuring SNMP Parameters and Traps Page 13-10 Get Ne xt Requests The total number of SNMP Get-Next PDUs accepted and processed by the switch SNMP proto- col entity. Set Requests The total number of SNMP Set-Request PDUs which have been accepted and processed by the switch SNMP protocol entity.
Trap Tables Page 13-11 T rap T ables The following table is a summary list of the supported SNMP traps and their values. Trap or Mask Name Object ID Bit Position Hex V alue Page coldStart 1.3.6.1.2.1.1 1.0 (word 0) 0 (word 0) 1 13-15 warmStart 1.3.6.1.
Trap Tables Page 13-12 tempAlarm 1.3.6.1.4.1.800.3.1.1.4.0.1 (word 1) 0 (word 1) 1 13-27 moduleChange 1.3.6.1.4.1.800.3.1.1.4.0.2 (word 1) 1 (word 1) 2 13-28 powerEvent 1.3.6.1.4.1.800.3.1.1.4.0.3 (word 1) 2 (word 1) 4 13-29 controllerEvent 1.3.6.1.4.
Trap Tables Page 13-13 healthThresholdRising 1.3.6.1.4.1.800.3.1.1.4.0.37 (word 2) 4 (word 2) 10 13-54 healthThresholdFalling 1.3.6.1.4.1.800.3.1.1.4.0.38 (word 2) 5 (word 2) 20 13-54 healthThresholdDevice 1.3.6.1.4.1.800.3.1.1.4.0.39 (word 2) 6 (word 2) 40 13-55 healthThresholdModule 1.
Trap Tables Page 13-14 Under1Event 1.3.6.1.4.1.800.3.1.1.4.0.88 (wor d 3) 23 (wor d 3) 80 0000 13-79 Over2Alarm 1.3.6.1.4.1.800.3.1.1.4.0.89 (word 3) 24 (word 3) 100 0000 13-79 Under2Event 1.3.6.1.4.1.800.3.1.1.4.0.90 (wor d 3) 25 (wor d 3) 200 0000 13-80 Over3Alarm 1.
Trap Tables Page 13-15 SNMP Standar d Tr aps This section lists the standard traps that are defined within RFC ( MIB ) documents. These traps signify events as they occur on common network devices. The following information on traps is provided in the tables.
Trap Tables Page 13-16 Trap warmStart Object ID 1.3.6.1.2.1.11.1 Description The sending protocol entity is re-initializing itself such that neither the agent’s configuration nor the protocol entity implementation may be altered.
Trap Tables Page 13-17 Trap linkUp Object ID 1.3.6.1.2.1.11.3 Description The sending protocol entity recognizes that one of the communication links represented in the agent’s configuration has come up. Bit Position (W ord 0) 3 Hex V alue (W ord 0) 8 Trap T ext and V ariable Descrip- tions Trap authentica tionFailur e Object ID 1.
Trap Tables Page 13-18 Trap eg pNeighborLoss Object ID 1.3.6.1.2.1.11.5 Description An EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship no longer exists. Bit Position (W ord 0) 5 Hex V alue (W ord 0) 20 Trap T ext and V ariable Descrip- tions Trap frDL CIStatusChang e Object ID 1.
Trap Tables Page 13-19 Trap ipxT ra pCircuitDown Object ID 1.3.6.1.4.1.23.2.5.5.1 Description This trap indicates that the specified circuit has gone down. Bit Position (W ord 0) 8 Hex V alue (W ord 0) 100 V ariable Description ipxCircSysInstance - The identifier of this instance of IPX.
Trap Tables Page 13-20 Trap topologyChang e Object ID 1.3.6.1.2.1.17.0.2 Description A bridge’s configured ports either transitioned from Learning state to For- warding state or from Forwarding state to Blocking state. This trap will not be sent if a newRoot trap was sent for the same transition.
Trap Tables Page 13-21 Trap a tmfVpcChange Object ID 1.3.6.1.4.1.353.0.1 Description Either a permanent VPC was added or deleted at this ATM interface, or an existing VPC was modified.
Trap Tables Page 13-22 Trap a tmfVccChange Object ID 1.3.6.1.4.1.353.0.2 Description Either a permanent VCC was added or deleted at this ATM interface, or an existing VCC was modified.
Trap Tables Page 13-23 Trap risingAlarm Object ID 1.3.6.1.2.1.16.0.1 Description The value of an Ethernet statistical variable (i.e., a member of the Ether- net statistics group as defined by RFC 1757) has exceeded its rising threshold.
Trap Tables Page 13-24 Trap fallingAlarm Object ID 1.3.6.1.2.1.16.0.2 Description The value of an Ethernet statistical variable (i.e., a member of the Ether- net statistics group as defined by RFC 1757) has dipped below its falling threshold.
Trap Tables Page 13-25 Trap Type dsx3LineStatusChang e Object ID 1.3.6.1.2.1.10.30.15.0.1 Description The value of an instance dsx3LineStatus changed. Bit Position (W ord 0) 16 Hex V alue (W ord 1) 1 0000 Trap T ext and V ariable Descrip- tions Line Status Change (line status 1, last change 4) DSX3 Line Status .
Trap Tables Page 13-26 Trap dsx1LineSta tusChange Object ID 1.3.6.1.2.1.10.18.15.0.1 Description The value of an instance dsx1LineStatus changed. Bit Position (W ord 0) 17 Hex V alue (W ord 1) 2 0000 Trap T ext and V ariable Descrip- tions Line Status Change (line status 1, last change 2) DSX1 Line Status .
Trap Tables Page 13-27 Extended Tr aps This section lists Alcatel-specific traps. These extended traps are generated specifically by Alcatel switch devices. Trap Type tempAlarm Object ID 1.3.6.1.4.1.800.3.1.1.4.0.1 Description The temperature sensor(s) have detected a temperature in the chassis that exceeds the threshold.
Trap Tables Page 13-28 Trap Type moduleChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.2 Description A module was either inserted or removed from the chassis.
Trap Tables Page 13-29 Trap Type powerEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.3 Description A power supply was either inserted or removed from the chassis, or there is a problem with the power supply. This trap is also generated when a power supply is switched on or off.
Trap Tables Page 13-30 Trap Type contr ollerEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.4 Description A chassis controller ( MPX ) lost or gained the state of the master. Bit Position (W ord 1) 3 Hex V alue (W ord 1) 8 Trap T ext and V ariable Descrip- tions Chassis controller (MPX) lost or gained master control (slot 1, state 3) Slot .
Trap Tables Page 13-31 Trap Type loginViola tion Object ID 1.3.6.1.4.1.800.3.1.1.4.0.5 Description A login attempt for the User Interface (UI) failed due to an incorrect login ID or an invalid password. Three (3) consecutive unsuccessful attempts will trigger this alarm.
Trap Tables Page 13-32 Trap Type macDuplicateP or t Object ID 1.3.6.1.4.1.800.3.1.1.4.0.7 Description Data from a MAC address that previously came from a source port differ- ent from the port where the frame previously was received although they both ports belong to the same VLAN.
Trap Tables Page 13-33 Trap Type portLinkUpEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.8 Description A physical, logical, or virtual port was enabled. These ports may be enabled through the UI or Switch Manager. Note that if you enable a physical port, any associated logical and virtual ports will also be enabled.
Trap Tables Page 13-34 Trap Type portLinkDownEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.9 Description A physical, logical, or virtual port was disabled. These ports may be dis- abled through the UI or Switch Manager. Note that if you disable a phys- ical port, any associated logical and virtual ports will also be disabled.
Trap Tables Page 13-35 Trap Type portPartitioned Object ID 1.3.6.1.4.1.800.3.1.1.4.0.10 Description The physical port detected jabber (i.e., the port has transitioned through enable/disable states more than 50 times in the past 200 ms). Jabber may be produced by a bad port connection, such as a faulty cable.
Trap Tables Page 13-36 Trap Type portRecor dMismatc h Object ID 1.3.6.1.4.1.800.3.1.1.4.0.11 Description The port configuration is different from the previous configuration. Typi- cally this trap is generated when a NIC of one type is swapped for a dif- ferent type (i.
Trap Tables Page 13-37 Trap Type gr oupChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.14 Description A Group was either created or deleted through the UI or Switch Manager. Bit Position (W ord 1) 13 Hex V alue (W ord 1) 2000 Trap T ext and V ariable Descrip- tions Group created or deleted (vlan 2 admin status 4) Group number .
Trap Tables Page 13-38 Trap Type vlanChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.15 Description A VLAN was either created or deleted through the UI or Switch Manager. Bit Position (W ord 1) 14 Hex V alue (W ord 1) 4000 Trap T ext and V ariable Descrip- tions VLAN Change created or deleted (group 2, admin status 4) Group number .
Trap Tables Page 13-39 Trap Type portMove Object ID 1.3.6.1.4.1.800.3.1.1.4.0.16 Description The specified port has moved from a Group or has had its configuration changed.
Trap Tables Page 13-40 Trap moduleR esetReload Object ID 1.3.6.1.4.1.800.3.1.1.4.0.17 Description The specified module has been either reset or reloaded.
Trap Tables Page 13-41 Trap Type systemEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.18 Description A potentially fatal error occurred in the system. Bit Position (W ord 1) 17 Hex V alue (W ord 1) 2 0000 Trap T ext and V ariable Descrip- tions Potentially fatal error occurred (trap 10) Event Trap Type .
Trap Tables Page 13-42 Trap Type vlanRouteT ableFull Object ID 1.3.6.1.4.1.800.3.1.1.4.0.19 Description The IP or IPX route table is full. Bit Posi- tion (W ord 1) 18 Hex V alue (W ord 1) 4 0000 Trap T ext and V ariable Descrip- tions IP or IPX route table is full on insertion.
Trap Tables Page 13-43 Trap Type atmSSCOPsta te Object ID 1.3.6.1.4.1.800.3.1.1.4.0.21 Description A specified port changed. Bit Posi- tion (W ord 1) 20 Hex V alue (W ord 1) 10 0000 Trap T ext and V ariable Descrip- tions Trap Type ilmiState Object ID 1.
Trap Tables Page 13-44 Trap Type atmConnection Object ID 1.3.6.1.4.1.800.3.1.1.4.0.23 Description The specified ATM VCC was created or deleted. Bit Position (W ord 1) 22 Hex V alue (W ord 1) 40 0000 Trap T ext and V ariable Descrip- tions ATM VCC created or deleted (slot 3, port 1, Vpi 0, Vci 100, admin status 2) Slot Number .
Trap Tables Page 13-45 Trap Type atmSer vice Object ID 1.3.6.1.4.1.800.3.1.1.4.0.24 Description The specified ATM service (Port-to-Port Bridging, Trunking, LAN Emula- tion, etc.
Trap Tables Page 13-46 Trap Type dlciNew Object ID 1.3.6.1.4.1.800.3.1.1.4.0.27 Description Frame Relay DLCI was created. Bit Position (W ord 1) 26 Hex V alue (W ord 1) 400 0000 Trap T ext and V ariable Descrip- tions Frame Relay DLCI created (slot 3 port 1 DLCI Number 100) DLCI Number .
Trap Tables Page 13-47 Trap Type dlciDel Object ID 1.3.6.1.4.1.800.3.1.1.4.0.28 Description Frame Relay DLCI was deleted. Bit Position (W ord 1) 27 Hex V alue (W ord 1) 800 0000 Trap T ext and V ariable Descrip- tions Frame Relay DLCI deleted (slot 3 port 1 DLCI Number 100) DLCI number .
Trap Tables Page 13-48 Trap Type dlciUp Object ID 1.3.6.1.4.1.800.3.1.1.4.0.29 Description Frame Relay DLCI changed to active state. Bit Position (W ord 1) 28 Hex V alue (W ord 1) 1000 0000 Trap T ext and V ariable Descrip- tions Frame Relay DLCI Changed to Active (slot 3 port 1 DLCI Number 100) DLCI Number .
Trap Tables Page 13-49 Trap Type dlciDn Object ID 1.3.6.1.4.1.800.3.1.1.4.0.30 Description Frame Relay DLCI changed to inactive state. Bit Position (W ord 1) 29 Hex V alue (W ord 1) 2000 0000 Trap T ext and V ariable Descrip- tions Frame Relay DLCI Changed to Inactive (slot 3 port 1 DLCI Number 100) DLCI Number .
Trap Tables Page 13-50 Trap Type portManualF orwardingMode Object ID 1.3.6.1.4.1.800.3.1.1.4.0.31 Description The specified port was placed into manual mode forwarding as its default setting.
Trap Tables Page 13-51 Trap Type fddiCFStateChang e Object ID 1.3.6.1.4.1.800.3.1.1.4.0.32 Description The specified FDDI physical port changed from wrap configuration state.
Trap Tables Page 13-52 Trap Type duplicateIP address Object ID 1.3.6.1.4.1.800.3.1.1.4.0.35 Description The switch detected a duplicate IP address. Bit Position (W ord 2) 2 Hex V alue (W ord 2) 4 Trap T ext and V ariable Descrip- tions Duplicate IP address detected (IP addr 192.
Trap Tables Page 13-53 Trap Type duplicateMA Caddress Object ID 1.3.6.1.4.1.800.3.1.1.4.0.36 Description The switch detected a duplicate MAC address of one of its own router ports.
Trap Tables Page 13-54 Trap Type healthThr esholdRising Object ID 1.3.6.1.4.1.800.3.1.1.4.0.37 Description At least one of the user-specified thresholds was exceeded. Bit Position (W ord 2) 4 Hex V alue (W ord 2) 10 Trap T ext and V ariable Descrip- tions Thresh-hold rising trap Trap Type healthThr esholdFalling Object ID 1.
Trap Tables Page 13-55 Trap Type healthThr esholdDevice Object ID 1.3.6.1.4.1.800.3.1.1.4.0.39 Description At least one of the device-level threshold crossing was detected. Bit Position (W ord 2) 6 Hex V alue (W ord 2) 40 Trap T ext and V ariable Descrip- tions Trap Type healthThr esholdModule Object ID 1.
Trap Tables Page 13-56 Trap Type xylanXIPXMAPP or tSta tusChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.41 Description An XMAP turned on or off. Bit Position (W ord 2) 8 Hex V alue (W ord 2) 100 Trap T ext and V ariable Descrip- tions The status of an XMAP-tracked virtual port has changed (port 1, reason 2) Port Number .
Trap Tables Page 13-57 Trap Type xylanXIPXMAPP or tSta teChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.42 Description An XMAP turned on or off. Bit Position (W ord 2) 9 Hex V alue (W ord 2) 200 Trap T ext and V ariable Descrip- tions The state of the XMAP agent has changed to (state 1) Operating State .
Trap Tables Page 13-58 Trap Type avlAuthAttempt Object ID 1.3.6.1.4.1.800.3.1.1.4.0.43 Description Indicates the last authenticated VLAN attempt. Bit Position (W ord 2) 1 6 Hex V alue (W ord 2) 1 0000 Trap T ext and V ariable Descrip- tions The last VLAN authentication attempt was: (user 1, event 2, MAC 0036589adf01, port 4, slot 5) User .
Trap Tables Page 13-59 Trap Type xylanXIPGMAPFailedUpda te Object ID 1.3.6.1.4.1.800.3.1.1.4.0.44 Description GMAP is unable to update the forwarding database to reflect information in its internal database.
Trap Tables Page 13-60 Trap Type clkBusLineSta teChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.45 Description Either the bus line’s status changed (active or inactive) or clock switching occurred.
Trap Tables Page 13-61 Trap Type bind-violation Object ID 1.3.6.1.4.1.800.3.1.1.1.0.46 Description A configured binding rule was violated. Bit Position (W ord 2) 23 Hex V alue (W ord 2) 80 0000 Trap T ext and V ariable Descrip- tions A binding rule has been violated (groupId 1, vlanId 2, IP 192.
Trap Tables Page 13-62 Trap Type mpcStatisticsOv erflow Object ID 1.3.6.1.4.1.800.3.1.1.4.0.47 Description An entry in the mpcStatisticsT able reached the threshold value. Bit Position (W ord 2) 18 Hex V alue (W ord 2) 4 0000 Trap T ext and V ariable Descrip- tions MPC Index .
Trap Tables Page 13-63 Trap Type fddiLerFlagChang e Object ID 1.3.6.1.4.1.800.3.1.1.1.0.65 Description The LER (Link Error Rate) flag on a port changed from CLEAR to SET . Bit Position (W ord 3) 0 Hex V alue (W ord 3) 1 Trap T ext and V ariable Descrip- tions FDDI: Link Error Rate on a port is set (SMTIndex 1, port 2, LerFlag 3) LER Flag .
Trap Tables Page 13-64 Trap Type fddiL CTFailCntIncr Object ID 1.3.6.1.4.1.800.3.1.1.1.0.66 Description The LCT (Link Confidence T est) flag on a port incremented.
Trap Tables Page 13-65 Trap Type mpcStatisticsOv erflow Object ID 1.3.6.1.4.1.800.3.1.1.1.0.67 Description The statisticsNum value of the mpcStatisticsT able reached the threshold value.
Trap Tables Page 13-66 Trap Type mpcShortCut Object ID 1.3.6.1.4.1.800.3.1.1.4.0.68 Description The established shortcut path either closed or failed to complete the path.
Trap Tables Page 13-67 Trap Type mpcIngr essRetryTimeOut Object ID 1.3.6.1.4.1.800.3.1.1.4.0.69 Description The retry time exceeded the MPC -p5 time. Bit Position (W ord 2) 20 Hex V alue (W ord 2) 10 .
Trap Tables Page 13-68 Trap Type vrrpT rapNe wMaster Object ID 1.3.6.1.2.1.46.1.3.1.0.3 Description The sending agent has transitioned from “Backup” state to “Master” state.
Trap Tables Page 13-69 Trap Type vrrpAuthF ailure Object ID 1.3.6.1.2.1.46.1.3.1.0.4 Description A packet was received from a router whose authentication key or authen- tication type conflicts with this router’s authentication key or type.
Trap Tables Page 13-70 Trap Type oamVCAIS Object ID 1.3.6.1.4.1.800.3.1.1.1.0.71 Description The specified connection is in the VC-AIS state. Bit Position (W ord 3) 10 Hex V alue (W ord 3) 400 V aria.
Trap Tables Page 13-71 Trap Type oamVCRDI Object ID 1.3.6.1.4.1.800.3.1.1.1.0.72 Description The specified connection is in the VC-RDI state. Bit Position (W ord 3) 11 Hex V alue (W ord 3) 800 V aria.
Trap Tables Page 13-72 Trap Type oamVCL OC Object ID 1.3.6.1.4.1.800.3.1.1.1.0.73 Description The specified connection is in the VC-LOC state. Bit Position (W ord 3) 12 Hex V alue (W ord 3) 1000 V ar.
Trap Tables Page 13-73 Trap Type oamVCUnsuccessLoop Object ID 1.3.6.1.4.1.800.3.1.1.4.0.74 Description The specified connection is in the Unsuccessful Loopback state.
Trap Tables Page 13-74 Trap Type oamVP AIS Object ID 1.3.6.1.4.1.800.3.1.1.4.0.75 Description The specified VP connection is in the VP-AIS state. Bit Position (W ord 3) 14 Hex V alue (W ord 3) 4000 V.
Trap Tables Page 13-75 Trap Type oamVPRDI Object ID 1.3.6.1.4.1.800.3.1.1.4.0.76 Description The specified VP connection is in the VP-RDI state. Bit Position (W ord 3) 15 Hex V alue (W ord 3) 8000 V .
Trap Tables Page 13-76 Trap Type oamVPL OC Object ID 1.3.6.1.4.1.800.3.1.1.4.0.77 Description The specified VP connection is in the VP-LOC state. Bit Position (W ord 3) 16 Hex V alue (W ord 3) 1 0000.
Trap Tables Page 13-77 Trap Type oamVPUnsuccessLoop Object ID 1.3.6.1.4.1.800.3.1.1.4.0.78 Description The specified VP connection is in the unsuccessful loopback state.
Trap Tables Page 13-78 Trap accountEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.86 Description An account event is generated to signal that a new accounting file is available on the switch Bit Position (W ord 3) 21 Hex V alue (W ord 3) 20 0000 V ariable Description chasAccountName - Path name of the most recently terminated account- ing file.
Trap Tables Page 13-79 Trap Type Under1Event Object ID 1.3.6.1.4.1.800.3.1.1.4.0.88 Description This event is generated when the filling level goes below the first thresh- old.
Trap Tables Page 13-80 Trap Under2Event Object ID 1.3.6.1.4.1.800.3.1.1.4.0.90 Description This event is generated when the filling level is lowered below the sec- ond threshold. Bit Position (W ord 3) 25 Hex V alue (W ord 3) 200 0000 V ariable Description chasAccountFilingLevel - The amount of buffer taken up by accounting data.
Trap Tables Page 13-81 Trap Under3Event Object ID 1.3.6.1.4.1.800.3.1.1.4.0.92 Description This event is generated when the filling level goes below the third threshold. Bit Position (W ord 3) 27 Hex V alue (W ord 3) 8000 0000 V ariable Description chasAccountFilingLevel - The amount of buffer taken up by accounting data.
Trap Tables Page 13-82 Trap FileAlarm Object ID 1.3.6.1.4.1.800.3.1.1.4.0.94 Description This alarm is generated when too many files are awaiting collection.
Trap Tables Page 13-83 Trap Type ldpP eerCrea te Object ID 1.3.6.1.4.1.800.3.1.1.4.0.80 Description A LDP peer is identified by the LDP hello mechanism and a peer entry is created.
Trap Tables Page 13-84 Trap Type ldpP eerDelete Object ID 1.3.6.1.4.1.800.3.1.1.1.0.81 Description An LDP peer is lost and the peer entry is deleted. Bit Position (W ord 3) 6 Hex V alue (W ord 3) 40 V ariables mplsLdpEntityID mplsLpdPeerIndex mplsLdpPeerID Trap T ext and V ariable Descrip- tions Peer Entity is Deleted.
Trap Tables Page 13-85 Trap Type ldpSessionCrea te Object ID 1.3.6.1.4.1.800.3.1.1.4.0.82 Description An LDP session with the peer is established and a session entry is cre- ated.
Trap Tables Page 13-86 Trap Type ldpSessionDelete Object ID 1.3.6.1.4.1.800.3.1.1.4.0.83 Description An LDP session with the peer is lost and the session entry is deleted.
Trap Tables Page 13-87 Trap Type lecStateChang eEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.96 Description A trap message is sent to a network manager when a LEC status changes.
Trap Tables Page 13-88 Trap T ext and V ariable Descrip- tions LEC Status Change (ELAN Name, Service Instance, New state, previous ELAN Name . The name of the ELAN whose status changed to generate this trap. state). Previous State . The previous status of the LEC that changed to generate this trap.
Page 14-1 14 DNS Resolv er and RMON Intr oduction This chapter describes commands related to the Domain Name Server ( DNS ) resolver and remote network monitoring ( RMON) feature in the switch. This chapter also describes how to configure router port MAC addresses with the chngmac command.
Configuring the DNS Resolver Page 14-2 To enable the resolver function, enter 1=y . A screen similar to the following then displays: DNS Resolver Configuration 1) Resolver Enabled : Yes 2) Domain : UN.
Remote Network Monitoring (RMON) Page 14-3 Remote N etwork Monitoring (RMON) Remote Network Monitoring ( RMON ) allows you to set up remote monitoring within your Omni Switch/Router.
Remote Network Monitoring (RMON) Page 14-4 The Alarm probe attempts to prevent a flood of alarms from being generated by fluctuating values. It does so by continuously comparing the upper and lower limits. What this means is that the first time either an upper or lower limit is exceeded, an alarm will be generated.
Remote Network Monitoring (RMON) Page 14-5 Time Time since the last change in status. System Resour ces Amount of memory that has been allocated to this probe. To see the detail for each of the probes enter the probes command followed by the entry number as shown below.
Configuring Router Port MAC Addresses Page 14-6 Configuring Router P ort MA C A ddr esses You can use the chngmac command if you want to configure a locally administered address ( LAA ) for a group that has an IP router port, IPX router port, or both.
Page 15-1 15 Managing Ethernet Modules Ov erview of Omni Switch/Router Ethernet Modules This chapter describes User Interface commands for Ethernet, Fast Ethernet, and Gigabit Ethernet modules. This chapter documents User Interface ( UI ) commands to manage Omni Switch/Router Ether- net modules.
Overview of Omni Switch/Router Ethernet Modules Page 15-2 V ariety of Connector Options Ethernet and Fast Ethernet modules are available in a variety of connector types. On the OmniSwitch, Fast Ethernet modules use copper RJ-45 and fiber SC connectors.
Overview of Omni Switch/Router Ethernet Modules Page 15-3 Kodiak Ethernet Modules ESX-K Series Modules and Optimized P orts Kodiak-based modules will flood packets with unknown destination addresses on ports configured for optimized device mode. To prevent this condition, the following command can be entered into the mpx.
The Ethernet Management Menus Page 15-4 The Ethernet Management Menus The eth100 and 10/100 sub-menus are described in this chapter. These sub-menus are part of the physical interface sub-menu, which .
Configuring 10/100 Auto-Sensing Ports Page 15-5 Configuring 10/100 A uto-Sensing P orts The 10/100cfg command allows you to enable auto-negotiation, as well as configure link speed (10 or 100 Mbps) and the link mode (full or half-duplex) on 10/100 Ethernet ports on the ESX-K-100C-32W modules on the Omni Switch/Router.
Configuring 10/100 Auto-Sensing Ports Page 15-6 6. Since you have enabled auto-negotiation, the port will automatically sense the line speed of the connection.
Configuring Kodiak Ethernet Ports Page 15-7 Configuring K odiak Ethernet P orts The 10/100cfg command allows you to configure the link mode (full or half-duplex) for ports on newer Kodiak Ethernet modules. This procedure describes how to configure Ethernet modules on the Omni Switch/Router.
Viewing Configurations for 10/100 Ethernet Modules Page 15-8 Vie wing Configurations for 10/100 Ethernet Modules The 10/100vc command allows you to view the current status of newer Ethernet modules (see Kodiak Ethernet Modules on page 15-3). These modules support 100 Mbps, or 1000 Mbps Ethernet.
OmniChannel Page 15-9 OmniChannel OmniChannel allows you to increase the bandwidth of Fast backbones by combining the capacity of up to four (4) Fast Ethernet ports into one channel. The combined channel oper- ates within Spanning Tree as one virtual port, and can provide up to 800 Mbps (in full-duplex mode) of bandwidth.
OmniChannel Page 15-10 ♦ Note ♦ For Kodiak-based 10/100 Ethernet modules, 802.1Q is supported over OmniChannel. See Chapter 16, “Managing 802.1Q Groups” for more information. OmniChannel balances the traffic load among links by MAC address. MAC addresses are assigned to physical links in the OmniChannel in a round-robin fashion.
OmniChannel Page 15-11 Server Channel Limitations The following are limitations to creating a server channel on the Omni Switch/Router: • The maximum number of Server Channels in the whole box is not fixed; however, it is suggested that no more than 16 be created on the same switch.
OmniChannel Page 15-12 If the port you enter is already part of another OmniChannel, then it cannot be used in a second OmniChannel. The following message displays for those ports that are already part of another OmniChannel: Primary port in use 5. The following prompt displays: To select a port, use the convention - Slot/Physical Port.
OmniChannel Page 15-13 Adding P orts to an OmniChannel After you create an OmniChannel with the crechnl command, you can add more secondary ports to the same channel as long as the channel contains less than 4 ports. You use the addprtchnl command to add ports to an OmniChannel.
OmniChannel Page 15-14 Deleting P orts from an OmniChannel You can delete ports from an OmniChannel using the delprtchnl command. Follow these steps: 1. Enter delprtchnl . 2. The following prompt displays: Channel Number : Enter the channel number on which you want to delete ports.
OmniChannel Page 15-15 3. A screen similar to the following displays: Displaying channel 2 Channel Id Phy. Port Port Status Mac Count ===================================================================== 2 5/6 Inactive 0 5/7 Inactive 0 3 5/3 Active 35 5/4 Active 34 5/5 Active 34 The following sections describe the variables in this table.
OmniChannel Page 15-16.
Page 16-1 16 Managing 802.1Q Gr oups This chapter documents User Interface ( UI ) commands to manage 802.1Q groups. For docu- mentation on Command Line Interface ( CLI ) commands to manage 802.1Q groups, see the Text-Based Configuration CLI Reference Guide .
Page 16-2 IEEE 802.1Q Sections Not Implemented Some portions of the 802.1Q specification have not yet been implemented in the Omni Switch/Router. These include the following: • The tunneling of non-canonical 802.5 frames is not supported, since the Alcatel Omni S/R handles such traffic by frame translations.
Page 16-3 Application Example The following diagram illustrates a simple 802.1Q application: Simple 802.1Q Application In the above diagram, the PC devices (endstations) need to be segmented into different 802.1Q VLANs . The switch port to which each device attaches is assigned to an 802.
Page 16-4 Single vs . Multiple Spanning Tr ee In previous releases of the Omni Switch/Router software (4.0 and earlier), spanning tree support was done on a per port basis. In other words, a physical port could only participate in one instance of a spanning tree on the network.
Page 16-5 while VLAN 2 traffic is allowed to pass. The reverse is true for Switch 1 and Switch 3 (i.e., VLAN 2 traffic is blocked, while VLAN 1 traffic is allowed to pass). Service commands are used in Ethernet modules to assign groups to 10/100 and Gigabit ports.
Page 16-6 Since spanning tree is group based, the physical port in the above diagram participates in three spanning tree instances: one for untagged traffic and two for 802.
Assigning an 802.1Q Group to a Port Page 16-7 Assigning an 802.1Q Gr oup to a P ort Previous versions of the Omni Switch/Router (version 4.0 and earlier) only allowed for single spanning tree configured 802.1Q groups using the addqgp , viqgp , and delqgp menu commands.
Assigning an 802.1Q Group to a Port Page 16-8 Configuring 802.1Q on 10/100 Ethernet P orts Use the cas command to assign 802.1Q groups to 10/100 ports.
Assigning an 802.1Q Group to a Port Page 16-9 The following sections describe the parameters shown in the screen on the preceding page. Description A textual description (up to thirty characters) for the service created when adding the port to a group.
Assigning an 802.1Q Group to a Port Page 16-10 For example, suppose that Port 3/1 is assigned to be in Group 2, and to use single spanning tree. If the port were to be assigned to another group, it would automatically set itself to use single spanning tree for that group as well.
Assigning an 802.1Q Group to a Port Page 16-11 Configuring 802.1Q on Gigabit Ethernet P orts Use the cas command to assign 802.1Q groups to Gigabit ports.
Modifying 802.1Q Groups Page 16-12 Modi fying 802.1Q Groups 802.1Q groups for both 10/100 and Gigabit Ethernet ports can be modified using the mas command. The procedure is slightly different in each case. The screens for the mas command change, depending on whether you have a legacy Ethernet board or a Kodiak ASIC-based Ethernet board.
Modifying 802.1Q Groups Page 16-13 The ESX-K and GSX-K modules can also remap incom- ing priority on an ingress port. If priority remapping has been configured, the new priority will be carried across the backplane. The priority information is used to queue the packet, and is sent out in the packet if the egress port is tagged.
Modifying 802.1Q Groups Page 16-14 Modi fying 802.1Q Groups for Gigabit Ethernet P orts To modify the configuration of an 802.1Q group for Gigabit ports, use the mas command as shown: mas <slot>.
Modifying 802.1Q Groups Page 16-15 Remember to save the changes to the service by entering save at the system prompt when finished. To find the instance of a port service, use the vas command. See Viewing 802.1Q Groups in a Port on page 16-16 for more information.
Viewing 802.1Q Groups in a Port Page 16-16 Vie wing 802.1Q Groups in a P ort To view which ports use which 802.1Q groups, enter the vas command at the system prompt, as shown: vas <slot>/<port> where <slot> is the slot number of the module on the switch and <port> is the port number where the service was created.
Viewing 802.1Q Statistics for 10/100 Ports Page 16-17 Vie wing 802.1Q Statistics for 10/100 P orts The viqs command provides a display of statistics for 802.
Deleting 802.1Q Groups from a Port Page 16-18 Deleting 802.1Q Gr oups from a P ort 802.1Q groups for both 10/100 and Gigabit Ethernet ports can be deleted using the das command.
Page 17-1 17 Configuring Bridging P ar ameter s This chapter describes how to configure and maintain bridging parameters. Bridges are devices that interconnect LANs using one (or more) of the available standards such as trans- parent bridging, source route bridging, or source route to transparent bridging.
Page 17-2 • Source Route to Transparent Bridging . Used in mixed Ethernet and Token Ring environ- ments, this protocol provides easy translation between transparent and source route bridg- ing.
Configuration Overview Page 17-3 Configur ation Overvie w When configuring bridging parameters, you will need to perform at least some of the following steps: Step 1. Select a group The bridging menu commands operate only on the currently selected group (or, for certain commands, VLAN).
Bridge Management Menu Page 17-4 Bridge Management Menu To view the Bridge Management Menu, enter the br command at the system prompt. If you are in verbose mode, the following table appears outlining the commands available to you. If you are not in verbose mode, enter a ? at the prompt to display the Bridge Management Menu.
Bridge Management Menu Page 17-5 Bridging Commands . These commands allow you to view bridge forward tables, create and view static address tables, display bridge port statistics, view MAC address information, view remote trunking stations, and view the domain bridge mapping table.
Bridge Management Menu Page 17-6 Configuring Fast Spanning Tree . These commands allow you to configure and view Fast Spanning Tree for a specific group or VLAN, and include the actfstps and fstps commands. Information is also included on configuring the Truncating Tree Timing and Speedy Tree Protocol features.
Selecting a Default Group Page 17-7 Selecting a Default Gr oup Most commands in the Bridge Management Menu allow you to specify a group when entering the command at the system prompt. If you do not specify a group when entering a command, the bridge operations are performed on the currently selected group.
Bridging Commands Page 17-8 Bridging Commands The Bridge Management menu provides several commands that are useful in pinpointing problems in the network.
Bridging Commands Page 17-9 Field Descriptions The following section explains the fields displayed with the fwt command. Sl/In/Srvc/In . The slot number ( Sl ), interface (port) number ( In ), type of service ( Src ), and service instance ( In ).
Bridging Commands Page 17-10 Configuring a Static Bridge Addr ess You can configure static bridge address information by entering the fc command. A static bridge address is a fixed MAC address bridge that does not change or age out. To configure a static MAC address follow these steps: 1.
Bridging Commands Page 17-11 Field Descriptions The following section describes the fields in the fc command table. Index. A number assigned to the row to identify a previously created static bridge address, when modifying the address. MAC address. The canonical MAC address for this static bridge.
Bridging Commands Page 17-12 2. To modify an entry, use the index number for the specific static bridge address (listed in the leftmost column), the column letter for the column you want to change, an equal sign, and a new value.
Bridging Commands Page 17-13 Displaying Static Bridge Addr esses You can view static bridge address information by entering the fs command. To display the information, enter the fs command as follows: fs <group number> where <group number> is the number of the group for which you want to view static bridge MAC addresses.
Bridging Commands Page 17-14 Displaying Bridge P ort Statistics You can display statistics on bridge ports with the bps command. To view bridge port statis- tics enter the bps command as follows: bps <group number> where <group number> is the number of the group for which you want to view bridge port statistics.
Bridging Commands Page 17-15 Field descriptions The following section describes the fields displayed in the above table. Frames discarded to full Forwarding Database . The number of frames that were not transmitted because the forwarding database is full.
Bridging Commands Page 17-16 Displaying Media Access Contr ol (MA C) Information for a Specific MA C address Media Access Control (MAC) information for the switch can be examined by using the macinfo command. You can view specific MAC address information, or choose a slot and view all MAC addresses associated with the selected slot.
Bridging Commands Page 17-17 Displaying Media Access Contr ol (MA C) Information for all MA C addresses Media Access Control (MAC) information for the switch can be examined by using the macinfo command. You can view all MAC addresses associated with the selected slot.
Bridging Commands Page 17-18 Field Descriptions The following section describes the fields displayed using the macstat command. Slot . The slot number of the switch to which the MAC address statistics apply. Discarded . The number of MAC addresses that have been discarded on this slot due to the CAM being full.
Bridging Commands Page 17-19 2. The following prompt is shown: Enter service’s Slot/Station (return for all services): Enter the slot and station (port) number for the local switch for which you wish to view remote trunking services.
Bridging Commands Page 17-20 3. A screen similar to the following is shown: DOMAIN BRIDGE MAPPING Group 2 Destination MAC Group ID Age Slot / Intf Domain MAC 00:20:da:7d:ef:44 2 14 8 / 1 00:20:da:6c:f.
Setting Flood Limits Page 17-21 Setting Flood Limits The flood limit is the number of bytes per second of flooded data that may be transmitted on a port on a group. This limit is a mechanism for controlling broadcast storms on the network. The default flood limit for a port, regardless of the media type, is 192,000 bytes per second.
Setting Flood Limits Page 17-22 Displaying Group Flood Limits The fls command allows you to view the current flood limits set for groups. The limits are set using the flc command. To display flood limits for all Groups, enter fls <groupNumber> where <groupNumber> is the number of the group for which you are viewing the flood limit.
Configuring Spanning Tree Page 17-23 Configuring Spanning T ree Spanning Tree is an algorithm developed to help prevent the occurrence of broadcast storms in a network. A packet can be broadcast multiple times in a network if the network is physi- cally configured with loops.
Configuring Spanning Tree Page 17-24 • IBM SRT bridges send an IEEE-style STE RIF over Token Ring networks. The Omni Switch/Router does not support this frame, and any frame of this type received by the switch is discarded. • The OmniSwitch/Router does not support using the same Functional Address (FA) for both data and spanning tree frames.
Configuring Spanning Tree Page 17-25 Configuring Spanning T ree P arameter s The stc command allows you to configure parameters for the spanning tree, and enable or disable the Fast Spanning Tree feature for a VLAN.
Configuring Spanning Tree Page 17-26 4. The following prompt is displayed asking whether you would like to use the Fast Spanning Tree feature: Fast Spanning Tree is OFF for this Group, set to ON? (y/n) : Enter n to leave Fast Spanning Tree disabled, or y to enable Fast Spanning Tree, and press <return> .
Configuring Spanning Tree Page 17-27 8. The following prompt is displayed allowing you to set the Bridge Forward Delay: New Bridge Forward Delay (4..30 secs) (current value is 4) : Enter the Forward Delay Time as a number between 4 and 30, or press <return> to accept the default listed in parenthesis.
Configuring Spanning Tree Page 17-28 Display Spanning Tr ee Bridge P arameter s The sts command allows you to display spanning tree bridge parameters. To display spanning tree parameters, enter the st.
Configuring Spanning Tree Page 17-29 Designated Root. The bridge identifier of the root of the spanning tree as determined by the spanning tree protocol. It is created by concatenating the root bridge Priority with its six-byte MAC address. Cost to Root Bridge.
Configuring Spanning Tree Page 17-30 Configuring Spanning T ree P ort P arameter s The stpc commands allows you to configure port parameters (as opposed to bridge parame- ters) for spanning tree.
Configuring Spanning Tree Page 17-31 Field Descriptions The following section explains the fields displayed by the stpc command. Index A number assigned as an identifier for the port. Slot/Intf/Service/Inst The slot number ( Slot ), interface (port) number ( Intf ), type of service ( Service ), and service instance ( Inst ).
Configuring Spanning Tree Page 17-32 Manual Mode Allows you to manually set the state for each port (forwarding or blocking) or defer the port’s state configuration to the spanning tree protocol, which will either be IEEE 802.1d or IBM. This column is especially helpful if you are using the IBM Spanning Tree protocol with non- Token Ring (e.
Configuring Spanning Tree Page 17-33 Field Descriptions The following section explains the fields displayed by the stps command. Slot/Intf . The slot and interface (port) number of the port. Service/Inst . The service type and instance of the service connected to the port.
Configuring Fast Spanning Tree Page 17-34 Configuring F ast Spanning Tr ee The Fast Spanning Tree (Rapid Reconfiguration) feature is designed to help provide an 802.1D standards-based method of quick recovery in the event of link, port and device failures in an Ethernet local area network.
Configuring Fast Spanning Tree Page 17-35 Truncating T ree Timing & Speedy T ree Pr otocol Two additional enhancements are also included with the Fast Spanning Tree feature for improved performance: Truncating Tree Timing and Speedy Tree Protocol.
Configuring Fast Spanning Tree Page 17-36 Displaying Fast Spanning T ree P ort P arameter s The fstps command allows you to view the current Fast Spanning Tree port parameters on a selected group or VLAN .
Configuring Fast Spanning Tree Page 17-37 Role. The port’s current role as defined by application of the fast spanning tree protocol. The Role values include: DISABLED The port has been disabled. ROOT The Root Port on a Bridge has the best path to the Root Bridge, and connects the Bridge to the Root Bridge.
Configuring Fast Spanning Tree Page 17-38 Enabling Fast Spanning T ree P ort P arameter s The actfstps command allows you to activate Fast Spanning Tree port parameters on a selected group or VLAN .
Configuring Fast Spanning Tree Page 17-39 Disabling Fast Spanning T ree P ort P arameter s The actfstps command allows you to disable Fast Spanning Tree port parameters on a selected group or VLAN .
Configuring Source Routing Page 17-40 Configuring Sour ce Routing The srs and src commands allow you to display and configure the source routing parameters for the selected group.
Configuring Source Routing Page 17-41 Disabling SAP filtering To disable the SAP feature, use the srsf command as shown: 1. Enter the srsf at the system prompt. 2. The following message is displayed: SAP Filter support is ON, set it to OFF? (n) : Enter y and press <return> .
Configuring Source Routing Page 17-42 4. Press <return> . The second deny filter prompt is displayed: Output SAP Deny Filter 2 (0000): Enter the SAP value that the first deny filter should screen. Any packet matching this filter will be rejected.
Configuring Source Route to Transparent Bridging Page 17-43 Configuring Sour ce Route to Tr ansparent Bridging In order to provide switching between source-routed token ring networks supporting the IBM Spanning Tree, and transparently bridged networks (primarily Ethernet supporting 802.
Configuring Source Route to Transparent Bridging Page 17-44 Enabling SRTB for a Gr oup The srtbcfg command allows you to display configured groups and the status of SRTB (either on or off ), and to enable or disable SRTB for a specific group. To display groups and the status of SRTB: 1.
Configuring Source Route to Transparent Bridging Page 17-45 6. Once you have selected the frame type, you are returned to the menu prompt. By reenter- ing the srtbcfg command as you did in step 1, you.
Configuring Source Route to Transparent Bridging Page 17-46 Viewing the RIF T able A Routing Information Field (RIF) is stored for each MAC address learned on a token ring port.
Configuring Source Route to Transparent Bridging Page 17-47 Clearing the RIF T able If there is a topology change in your network, you most likely will need to clear one or more RIFs from the table so that SRTB can relearn them. You can clear specific entries for MAC addresses in the RIF table, or flush the entire table with the srtbclrrif command.
Configuring Source Route to Transparent Bridging Page 17-48.
Page 18-1 18 Configuring Fr ame T r anslations An y-to-Any Switching Because the Omni Switch/Router is a LAN switch that carries frames from multiple media types on its backplane fabric, it offers the facility to switch frames from any media to any other media.
Any-to-Any Switching Page 18-2 In order to understand why these options and limitations arise and to better understand the configuration options available, it is advisable to understand as background the theory of operation of any to any switching.
Translating the Frame Page 18-3 T ranslating the Fr ame In order to discuss these issues independent of particular media and protocols, consider that every frame, of any protocol, on any media, consists of the following parts.
The MAC Header Page 18-4 The MA C Header The format and values defined for the MAC header are covered in the media standards but even here a variety of choices which are dictated by the upper layer protocol can be found. Canonical ver sus Non-Canonical The first requirement of the switch transformation is the bit ordering of the address fields.
The RIF Field Page 18-5 The RIF Field The same source routing standard is supported by FDDI and Token Ring so the RIF fields can be switched without problems between these media. Ethernet does not support source routing thus frames with RIF fields cannot be switched onto these media.
Encapsulation Page 18-6 Encapsulation Encapsulation is the biggest problem for implementing a transformation algorithm in support of any to any switching. All of the media provide a choice of more than one encapsulation and not all encapsulations are available on all media.
Encapsulation Page 18-7 The SNAP Conv ersion The intent of the 802.2 committee is that Ethertype frames are transformed to SNAP on cross- ing from Ethernet media to 802 media and restored to Ethertype in the reverse direction.
Encapsulation Page 18-8 IPX Encapsulation Tr ansformation Rules For IPX the encapsulation problems described above are compounded by the introduction of a fourth encapsulation on Ethernet media. Novell introduced a frame format when the IEEE 802.3 standards committee produced its version of Ethernet which was incompatible with Ethernet.
The Network Header Page 18-9 The N etwork Header There are essentially two requirements for the any to any switching transformation function to address the network header fields: • Network Address t.
The Network Header Page 18-10 Given this model of implementation a station responding with an ARP on Ethernet which was switched to FDDI would result in the same representation of the MAC address in the ARP table of the router.
Frame Size Requirements Page 18-11 Fr ame Size Requirements The frame size requirement for the different media cause two problem areas which have to be addressed by the any to any switching transformation function. • Ethernet has a minimum frame size requirement.
Frame Size Requirements Page 18-12 MTU Handling Routers address the problem of maximum frame size limitations with the notion found in many protocols of a Maximum Transmission Unit (MTU) size. Protocols use this notion in two possible ways. • PDU Fragmentation/Reassembly The router is configured with the MTU of each port.
Banyan Vines Page 18-13 Ban yan Vines Banyan Vines supports Ethernet, FDDI, and Token Ring networks. Each type of network generates a different frame format, so the Omni Switch/Router performs translations for frames moving from one network type to another.
Configuring Encapsulation Options Page 18-14 Configuring Encapsulation Options You will configure frame encapsulation based on the destination MAC address or the destina- tion switch port. Whether a frame is encapsulated based on the destination MAC or the port depends whether the frame has a unicast, multicast, or broadcast destination.
Configuring Encapsulation Options Page 18-15 “Nativ e” ver sus “Non-N ative” on Ethernet For the Ethernet one further distinction is made. If the frame received from the backplane is an Ethernet media type frame from another Ethernet switching module in the same chassis, then no encapsulation translations are applied .
The User Interface Page 18-16 The U ser Interface This chapter documents User Interface ( UI ) commands to configure encapsulation options. For documentation on Command Line Interface ( CLI ) commands to configure encapsulation options, see the Text-Based Configuration CLI Reference Guide .
The User Interface Page 18-17 The addvp, modvp and cr gp Commands All of these commands include in their dialogue an Output Format question for ports and a subsidiary IEEE 802.2 Pass through option. The options offered are: • a default, • Ethertype, • SNAP and • LLC.
The User Interface Page 18-18 Ethernet Factory Default T ranslations For Ethernet switching module ports the factory default is set to the following: FDDI Factory Default T ranslations For FDDI switch.
The User Interface Page 18-19 T oken Ring Factory Default T ranslations For Token Ring switching module ports the factory default is set to the following: A TM LANE Factory Default Tr anslations For A.
The User Interface Page 18-20 The Ethertype Option This option can only be applied to Ethernet switching module ports. It is set to the following: Ethernet Media - Ethernet II Mode No translation is performed on outbound Ethernet frames where the inbound interface was Ethernet.
The User Interface Page 18-21 The SNAP Option This option can be applied to all media type ports and is set to the following: In the modvp or addvp commands for FDDI and Token Ring the only choices other than default are SNAP or LLC and the default must be one of these.
The User Interface Page 18-22 A TM LANE - SNAP Mode All IPX frames are translated to SNAP unless they are already SNAP, in which case they are forwarded as is. All Ethertype or SNAP frames from Ethernet and SNAP frames from Token Ring or FDDI are translated to SNAP or left as SNAP.
The User Interface Page 18-23 The LLC Option This option can be applied to all media type ports and is set to the following: In the modvp or addvp commands for FDDI and Token Ring the only choices other than default are SNAP or LLC and the default must be one of these.
The User Interface Page 18-24 Interaction with the ne w interface If the port to which these commands are being applied has been configured with the new interface commands its encapsulation will be displayed as SWCH in the vi command output.
The Switch Menu Page 18-25 The Switch Menu The switch menu contains commands that allow you to set translation options discussed earlier in this chapter. It also contains commands to change the default values. To view the switch menu, enter switch at the prompt.
The Switch Menu Page 18-26 Default Ethernet Tr anslations The ethdef allows you to set up default translations for all Ethernet ports. To do so: 1. Enter ethdef at the system prompt. The following screen displays: This will reset the default translations for Ethernet media to a new value.
The Switch Menu Page 18-27 Default FDDI T ranslations The fddidef command allows you to set up default translations for all FDDI ports. To do this: 1. Enter the fddidef command at the system prompt. The following screen displays: This will reset the default translations for FDDI media to a new value.
The Switch Menu Page 18-28 ♦ Important Note ♦ The IP Translation Options allow only SNAP ( s ). The IPX translations allow SNAP ( s ), and LLC ( 2 ) for all frame types. The Ethertype ( e ) translation is not allowed for FDDI. The Ethernet 802.3 translation ( 3 ) is allowed only on incoming Ethernet 802.
The Switch Menu Page 18-29 3. You change an outgoing frame type by entering its line number, an equal sign (=) and a frame type indicator ( e , s , 2 , or 3 ). The frame type indicators represent the following frames: e Ethernet II or Ethertype s SNAP 2 802.
The Switch Menu Page 18-30 P ort Tr anslations The swch command allows you configure translations on a port-by-port basis. Its translation options are similar to those for ethdef , fddidef , and trdef . However, instead of applying transla- tions to all ports for a particular media type, swch applies translations only to the port you specify.
The Switch Menu Page 18-31 5. When are done changing translations, enter save to save all your settings. If you enter quit , you will exit the swch command without saving your changes. Please note that valid translation options depend on the media type of the port.
The Switch Menu Page 18-32 If the port selected is an Ethernet based port, something like the following would be displayed: Ethernet Statistics for Ethernet port 3/4/Brg/1 Received Good Octets 0 Trans.
The Switch Menu Page 18-33 Transmitted Broadcasts . The number of frames transmitted on this port whose destination address is the broadcast address. Note that these statistics merely indicate the for.
The Switch Menu Page 18-34 Received Late Collision, Transmitted Late Collisions . A late collision is a collision which occurs in a frame when more than 64 bytes have been received/transmitted. On a correctly configured network, which doesn't exceed physical limits of size, impedance, station spacing, etc.
The Switch Menu Page 18-35 Displaying T oken Ring Switch Statistics In Release 3.4 and later, you can display statistics for the new generation of Token Ring modules known as “Bigfoot” (e.
The Switch Menu Page 18-36 Rx LLC Errored Octets . The total number of bytes received in bad LLC packets. The next group of statistics are the types of packets being transmitted and received. Rx Unicast Packets . The number of packets received on this port whose destination address is a unicast format.
The Switch Menu Page 18-37 the normal ring state or ring purge state to elect a new active monitor. Claim Token Packets . The total number of claim packets transmitted by this port. The next group describe error statistics for token, MAC, and LLC packets.
The Switch Menu Page 18-38 Received 256_511 byte Pkts . The total number of packets received on this port that were at least 256 bytes (octets) long and less than or equal to 511 bytes long.
The Switch Menu Page 18-39 Any to An y MA C Tr anslations The swchmac command allows you to view the current frame translation settings for a given MAC address. Follow these steps: 1. Enter swchmac and the following prompt displays: Enter MAC address ([XXYYZZ:AABBCC] or return for none : 2.
The Switch Menu Page 18-40 Default Autoencapsulation Autoencapsulation is a technique employed by AutoTracker software to learn the protocol and encapsulation type used by a source MAC address and automatically translate frames bound to that MAC address to the appropriate encapsulation type.
Translational Bridging Page 18-41 T ranslational Bridging Translational Bridging enables internetworking between FDDI, Ethernet, and Token Ring LANs. There is no standard which encompasses this.
Dissimilar LAN Switching Capabilities Page 18-42 Dissimilar LAN Switching Capabilities Switching traffic between like media requires no changes to the frame, whereas switching traffic between unlike media requires some level of change to the frame.
Dissimilar LAN Switching Capabilities Page 18-43 Switching Between Ethernet LANs A cross a T runked Backbone Frames that are switched between like media across a Trunked backbone will only be trans- lated at the egress port of the egress Omni Switch/Router.
Dissimilar LAN Switching Capabilities Page 18-44 Switching Between Similar LANs acr oss a Nativ e Backbone Switched traffic between similar LANs across a non-trunked or native backbone will have translations performed at each egress point.
Dissimilar LAN Switching Capabilities Page 18-45 The following table shows interoperability between dissimilar LANs with two switches where the client and server are resident on like media types and the connection is switched over various LAN backbone types.
Dissimilar LAN Switching Capabilities Page 18-46.
Page 19-1 19 Managing Gr oups and P orts In a traditional hub-based network, a broadcast domain is confined to a single network inter- face, such as Ethernet, or even a specific physical location, such as a department or building floor.
How Ports Are Assigned to Groups Page 19-2 Ho w P orts Are Assigned to Gr oups There are two methods for assigning physical OmniS/R ports to a Group. One method is static and requires manual configuration by the network administrator; the other method is dynamic and requires only the configuration of AutoTracker rules for port assignment to occur.
How Ports Are Assigned to Groups Page 19-3 How Dynamic P ort Assignment W orks Initially each port is assigned to the default Group. In this example, all three ports have work- stations that belong to three different IP subnets (130.0.0.0, 138.0.0.0, and 140.
How Ports Are Assigned to Groups Page 19-4 As the illustration below shows, the three ports are each moved from the default Group to a Group with a policy that matches the subnet address of the workstation attached to the port. AutoTracker IP address policies have been set up in Groups 2, 3, and 4.
Mobile Groups Page 19-5 Mobile Gr oups Switch ports can be dynamically assigned to mobile groups through AutoTracker policies. Support for dynamic port assignment is one of the main differences between mobile groups and non-mobile groups. AutoTracker rules are assigned directly to a mobile group.
Mobile Groups Page 19-6 Turning Gr oup Mobility On or Off The gmstat command turns group mobility on or off for a Group that you specify. Essentially, you can change a non-mobile group into a mobile group and a mobile group back into a non-mobile group through gmstat .
Mobile Groups Page 19-7 If you decided not to turn group mobility on, you would enter n at the group mobility prompt and the following message would display: Group Mobility Status unchanged Under standing P ort Membership in Mobile Gr oups Switch ports can belong to multiple mobile groups.
Mobile Groups Page 19-8 Secondary Group Switch ports and devices may become members of multiple mobile groups. A switch port starts in its default group, which initially is also its primary group. The primary group may change if the move_from_def variable is enabled.
Mobile Groups Page 19-9 How a De vice Is Dropped fr om the Default Mobile Group (def_group) If def_group is enabled.... The device that does not match any policies becomes a member of the default group. Default Group 1 Group 3 Why enable def_gr oup? • Ensure that all network devices will be a member of at least one mobile group.
Mobile Groups Page 19-10 How a P ort’s Primary Mobile Gr oup Changes (mov e_from_def) Default/Primary Port assigned to default group 1 or another group through crgp or addvp. Mobile Group 1 If mov e_from_def is enabled.... Device on port matches poli- cy in another mobile group (3).
Mobile Groups Page 19-11 How a P ort Ages Out of a Mobile Gr oup (mov e_to_def) If the port is in “optimized mode,” then the MAC does not age out and the port would stay in the mobile group even if move_to_def is enabled. Default Port assigned to default group.
Mobile Groups Page 19-12 Configuring Switch-Wide Gr oup Mobility V ariables There are several switch-wide group mobility variables that you can configure through the gmcfg command. These variables control the status of group mobility on all groups in a switch as well as the use of the default group.
Mobile Groups Page 19-13 By default the def_group variable is Enabled. If you want to disable it (devices that do not meet criteria for mobile group membership will not be part of any mobile group), then you need to indicate that choice at this prompt.
Mobile Groups Page 19-14 Viewing P orts in a Mobile Group The vpl command lists all the Groups in the switch currently configured as mobile Groups and the ports currently assigned to those Groups. Since ports are assigned to mobile groups dynamically, this display is helpful to find out which ports the switch already sees in each group.
Non-Mobile Groups and AutoTracker VLANs Page 19-15 N on-Mobile Groups and A utoTr acker VLANs Non-mobile Groups are comprised of physical entities—switch ports. Groups can span multi- ple switches, but they are still made up of physical ports that you can see and touch.
Non-Mobile Groups and AutoTracker VLANs Page 19-16 Spanning Tr ee and Non-Mobile Gr oups Each Group uses one Spanning Tree for bridging. The OmniS/R supports both 802.1d and IBM Spanning Tree protocols. The Spanning Tree state for the port is Forwarding.
Group and Port Software Commands Page 19-17 Gr oup and P ort Softwar e Commands Group and Virtual Port commands are part of the VLAN menu within the User Interface.
Creating a New Group Page 19-18 Cr eating a Ne w Group There are several steps involved in creating a new Group. Note that some steps apply only to mobile groups. These steps are as follows: 1. Enter Basic Group Information, such as the Group number and type.
Creating a New Group Page 19-19 Step 1. Entering Basic Gr oup Information a. Type crgp at any prompt. b. The following prompt displays: GROUP Number (5): By default the Group number you entered or the next available Group number is displayed in parentheses.
Creating a New Group Page 19-20 f. The following prompt displays: Enable MPLS? (n): Multi-Protocol Label Switching (MPLS) must be enabled if this group is going to be used for machines in the network that communicate via MPLS. Answer n at this prompt and skip ahead to Step 2.
Creating a New Group Page 19-21 Step 2. Configuring the Virtual Router P ort (Optional) You can now optionally configure the virtual router port that the default VLAN in this Group will use to communicate with other VLAN s. When you define a virtual router, a virtual router port for the default VLAN in the Group is created.
Creating a New Group Page 19-22 e. The following prompt displays: Description (30 chars max): Enter a useful description for this virtual IP router port using alphanumeric characters. The description may be up to 30 characters long. Press <Enter> .
Creating a New Group Page 19-23 Select the default framing type for the frames that will be generated by this router port and propagated over the default VLAN to the outbound ports. Set the framing type to the encapsulation type that is most prevalent in the default VLAN .
Creating a New Group Page 19-24 k. After selecting to enable IPX , the following prompt displays: IPX Network: Enter the IPX network address. IPX addresses consist of eight hex digits and you can enter a minimum of one hex digit in this field. If you enter less than eight hex digits, the system prefixes your entry with zeros to create eight digits.
Creating a New Group Page 19-25 o. After selecting the RIP and SAP configuration, the following prompt displays the default router framing type options: Default router framing type for : { Ethernet Media: Ethernet II (0), Ethernet 802.3 LLC (1), Ethernet 802.
Creating a New Group Page 19-26 q. The following prompt displays: Enter a priority level (0...7)(0): Prioritizing VLANs allows to you set a value for traffic based on the destination VLAN of packets. Traffic with the higher priority destination will be delivered first.
Creating a New Group Page 19-27 Step 3. Set Up Group Mobility and U ser Authentication A mobile group offers more flexibility than a non-mobile group. With a mobile group, ports are assigned dynamically to the group based on AutoTracker policies that you configure.
Creating a New Group Page 19-28 Step 4. Configuring Virtual P orts You can now enter configuration parameters for each switch port to be included in this Group. These configuration parameters include the bridging mode, output format type, and administrative state.
Creating a New Group Page 19-29 d. The virtual port configuration menu displays: Modify Ether/8 Vport 2/8 Configuration 1) Vport : 9 2) Description : 3) Bridge Mode : Auto-Switched 31) Switch Timer : 60 4) Flood Limit : 192000 5) Output Format Type : Default (IP-Eth II, IPX-802.
Creating a New Group Page 19-30 Auto-Switch . The default setting for all Ethernet ports. This mode is appropriate for dedi- cated connections requiring a switch-over to bridge mode when multiple devices are detected. A port in Auto-Switch mode will start in Optimized Device Switching mode (see description above).
Creating a New Group Page 19-31 4) Flood Limit The flood limit allows you to tune a virtual port to limit the flooding of broadcast, multi- cast, and unknown destination packets. This feature is useful for controlling broadcast storms on your network.
Creating a New Group Page 19-32 Output Framing Type on Physical Ports Note that for Ethernet, the default output format option is Ethernet II for IP frames and 802.3 for IPX frames. You can customize your frame translation settings even further through the Switch menu.
Creating a New Group Page 19-33 7) Admin, Operational Status Select whether to administratively enable or disable this port. When you enable the port, the port can transmit and receive data as long as a cable is connected and no physical or operational problems exist.
Creating a New Group Page 19-34 Step 5. Configuring AutoT racker P olicies (Mobile Groups Only) When you have completed configuring mobile group and auto-activated LANE services, you can begin configuring AutoTracker policies for this mobile group.
Creating a WAN Routing Group Page 19-35 Cr eating a W AN Routing Group After entering basic Group information as described in Step 1. Entering Basic Group Informa- tion on page 19-19, you should have answered Yes to the following prompt: Enable WAN Routing? (n): if you want to enable WAN Routing.
Creating a WAN Routing Group Page 19-36 f. The following prompt displays: IP RIP Mode {Deaf (d), Silent (s), Active (a), Inactive (i)} (s): Define the RIP mode in which the virtual router port will operate. RIP (Router Information Protocol) is a network-layer protocol that enables the default VLAN in this Group to learn and advertise routes.
Creating a WAN Routing Group Page 19-37 k. After entering a description, the following prompt displays: IPX RIP and SAP mode {RIP and SAP active (a) RIP only active (r) RIP and SAP inactive (i)} RIP a.
Viewing Current Groups Page 19-38 Vie wing Current Gr oups The gp command provides information on all currently defined Groups in a switch including Group number, network address, protocol type, and encapsulation type.
Viewing Current Groups Page 19-39 A second address is displayed below the Network address. For IP, this address is the IP Subnet Mask, which is normally derived from the default VLAN IP address class. For IPX , this address is the IPX Node Address. Proto/Encaps .
Modifying a Group or VLAN Page 19-40 Modi fying a Group or VLAN After creating a Group (through crgp ) or VLAN ( through cratvl , see Chapters 20 and 22 ) , you can change any of their parameters through the modvl command.
Modifying a Group or VLAN Page 19-41 Viewing Y our Changes When you enter a change at the colon prompt, the modvl screen does not normally refresh. If you want to see the current Group or VLAN settings, including any changes you made, enter a question mark ( ? ) at the colon prompt.
Modifying a Group or VLAN Page 19-42 Enabling IP or IPX Routing If you enable IP or IPX routing by setting the corresponding modvl lines from N to Y , then the screen automatically refreshes with additional lines for the new router port parameters. All lines are set to router defaults.
Deleting a Group Page 19-43 Deleting a Gr oup You can delete a Group as long as it does not contain any virtual ports. The default Group, Group #1, cannot be deleted.
Adding Virtual Ports Page 19-44 A dding Virtual P orts You can add virtual ports to a Group at any time after the Group is created. The addvp command allows you to add one or more ports to a Group you specify. If you have used the crgp command to add virtual ports, then you will find the addvp command fields very famil- iar.
Modifying a Virtual Port Page 19-45 Modi fying a Virtual P ort You can modify a virtual port through the modvp command. The modvp command is very similar to the addvp command and the port configuration phase of the crgp command.
Deleting a Virtual Port Page 19-46 Deleting a Virtual P ort You can delete a virtual port from its existing Group by using the rmvp command. When you remove a virtual port, the port is moved to the default switch Group, Group #1, and all port parameters are reset to defaults except for the port name.
Viewing Information on Ports in a Group Page 19-47 Vie wing Information on P orts in a Group The via command allows you to view port attachments associated with a specified Group or all Groups in a switch. Entering via displays summary information for all virtual ports in the switch.
Viewing Information on Ports in a Group Page 19-48 • Rtr Virtual router port • Brg Virtual bridge port • Tnk Virtual trunk port (used for WAN ) • T10 802.10 FDDI service port • FRT Frame Relay trunk port • Lne LAN Emulation service port • CIP Classical IP service port • Vlc VLAN Clusters ( X-LANE ) service port Protocol .
Viewing Information on Ports in a Group Page 19-49 Admin Status . Indicates whether the port is administratively Enabled or Disabled . When Enabled , the port can transmit and receive data as long as a cable is connected and no physical or operational problems exist.
Viewing Detailed Information on Ports Page 19-50 Vie wing Detailed Information on P orts The vi command displays detailed information about virtual ports. Entering vi displays information for all virtual ports in the switch. You can also display information for only ports in a specific Group by specifying the Group ID after the vi command.
Viewing Detailed Information on Ports Page 19-51 The Instance ( Inst ) is an identifier of this type of service within the switch. For example, if more than one virtual router port is configured in the switch, then each “instance” of a router will be given a different number.
Viewing Detailed Information on Ports Page 19-52 Oper . Indicates the current Operational Status of the port. The port will be Active ( Active ) or Inactive ( Inactv ). If the port is Active, then the port can pass data and has a good physical connection.
Viewing Port Statistics Page 19-53 Vie wing P ort Statistics The vs command displays transmit and receive statistics for ports in the switch. Entering vs displays statistics for all virtual ports in the switch. You can also display statistics for only ports in a specific Group by specifying the Group ID after the vs command.
Viewing Port Statistics Page 19-54 Service Type values are as follows: • Rtr Virtual router port • Brg Virtual bridge port • Tnk Virtual trunk port (used for WAN ) • T10 802.
Viewing Port Errors Page 19-55 Vie wing P ort Error s The ve command displays port error statistics for ports in the switch. Entering ve displays error statistics for all virtual ports in the switch. You can also display errors statistics for only ports in a specific Group by specifying the Group ID after the ve command.
Viewing Port Errors Page 19-56 The Instance ( Inst ) is an identifier of this type of service within the switch. For example, if more than one virtual router port is configured in the switch, then each “instance” of a router will be given a different number.
Port Mirroring Page 19-57 P ort Mirroring You can set up Port Mirroring for any pair of Ethernet (10 or 10/100 Mbps) within the same switch chassis. Ethernet ports supporting port mirroring include10BaseT ( RJ-45 ), 10BaseFL (fiber), 10Base2 ( BNC ), and 10Base5 ( AUI ) connectors.
Port Mirroring Page 19-58 where <slot> is the slot number of the module containing the mirrored port, and <port> is the port number of the mirrored port. For example, if the Admin Status of a port displayed as M 3 02 then you would know this port is mirroring traffic for Port 2 on the module in Slot 3.
Port Mirroring Page 19-59 Port Mirroring Using an External RMON Probe ♦ Important Note ♦ The Mirroring Port is not accessible from the NMS device. From the NMS station, the Mirroring Port will appear disabled or down.
Port Mirroring Page 19-60 Setting Up P ort Mirroring You set up port mirroring when you add or modify a port through the addvp or modvp commands. The switch software senses the type of port you are configuring, so it will only prompt you for port mirroring when configuring an Ethernet port.
Port Monitoring Page 19-61 P ort Monitoring An essential tool of the network engineer is a network packet capture device. A packet capture device is usually a PC-based computer, such as the Sniffer ® , that provides a means for understanding and measuring data traffic of a network.
Port Monitoring Page 19-62 RAM Disk System for Data Captur e Files Port monitoring uses a RAM disk for fast temporary storage of data capture files. The RAM disk has a separate directory designation of /ram . RAM -based files are created in DOS-FAT format and they are displayed in UPPERCASE .
Port Monitoring Page 19-63 Starting a P ort Monitoring Session (pmon) You enable a port monitoring session through the pmon command. To start a session, enter pmon followed by the slot and port number that you want to monitor.
Port Monitoring Page 19-64 If Y ou Chose Dump to Screen If you selected the Dump to screen option, then a real-time synopsis of the session displays on your terminal screen. The following shows an example of this data Enter 'p' to pause, 'q' to quit.
Port Monitoring Page 19-65 Ending a P ort Monitoring Session After you quit a port monitoring session, the default directory changes to /ram and the current files on the RAM drive are listed. The screen below shows an example of the display at the completion of a monitoring session.
Port Mapping Page 19-66 P ort Mapping The OmniS/R began as an any-to-any switching device, connecting different LAN interfaces, such as Ethernet As networks grew and the traffic on them increased, a need arose for controlling some traffic, such as broadcasts.
Port Mapping Page 19-67 Port communication is uni-directional. A mapping between an ingress port and an egress port can only pass data from the ingress port to the egress port. To allow traffic to flow the from the egress port to the ingress port, it is necessary to create a new mapping.
Port Mapping Page 19-68 Who Can T alk to Whom? The following matrix outlines which ports can communicate with each other in the example shown on the previous page assuming all ports are part of the same group or VLAN . A port can only communicate with ports in the opposite subset within the port mapping set.
Port Mapping Page 19-69 Creating a P ort Mapping Set Use the pmapcr command to create a port mapping set. Follow these steps: 1. Enter pmapcr at a system prompt. 2. The following screen displays: Port Map Configuration 1. Ingress List : 2. Egress List : Enter the ingress ports and egress ports for this map set.
Port Mapping Page 19-70 Adding P orts to a P ort Mapping Set You can add ports to a port map set once it has been created using the pmapmod command. Follow these steps: 1. Enter the pmapmod command at a system prompt, as shown: pmapmod <pmap id> where <pmap id> is the map set number shown when the map set was created.
Port Mapping Page 19-71 Removing P orts from a P ort Mapping Set You can remove ports to a port map set once it has been created using the pmapmod command. Follow these steps: 1. Enter the modpmap command at a system prompt, as shown: pmapmod <pmap id> where <pmap id> is the map set number shown when the map set was created.
Port Mapping Page 19-72 Viewing a P ort Mapping Set You can view a port mapping set using the vpmap command. Enter the pmapv command as shown: pmapv <pmap id> where <pmap id> is the map set number shown when the map set was created.
Priority VLANs Page 19-73 Priority VLANs Prioritizing VLANs allows you to set a value for traffic based on the destination VLAN of pack- ets. Traffic with the higher priority destination will be delivered first. VLAN priority can be set from 0 to 7, with 7 being the level with the most priority.
Priority VLANs Page 19-74 Configuring VLAN Priority To configure the priority of a VLAN: 1. Enter the prty_mod command at the system prompt, as shown: prty_mod <groupId> where <groupId> is the group number associated with the VLAN whose priority is being set.
Page 20-1 20 Configuring Gr oup and VLAN P olicies AutoTracker policies subdivide network traffic based on specific criteria. AutoTracker policies can be defined by port, MAC address, protocol, network address, user-defined, port binding, DHCP port, or DHCP MAC address policy.
AutoTracker Policy Types Page 20-2 A utoTr acker P olic y Types You can define a maximum of 32 AutoTracker policies of each type per Group. There is no restriction on the number of rules you can define per AutoTracker VLAN , as long as the maxi- mum number of policies for the Group is not exceeded.
AutoTracker Policy Types Page 20-3 You must specify a separate binding policy for each device, but you can specify an unlimited number of such policies.
Defining and Configuring AutoTracker Policies Page 20-4 Defining and Configuring A utoTr acker P olicies You can define AutoTracker policies by port, MAC address, protocol, network address, user definition, or port binding. You can define multiple policies for a mobile group or AutoTracker VLAN if you wish.
Defining and Configuring AutoTracker Policies Page 20-5 Defining a P ort P olicy After you enter the Administrative Status, the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3. Protocol Rule 4.
Defining and Configuring AutoTracker Policies Page 20-6 Defining a MA C Addr ess P olicy After you enter the Administrative Status, the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3. Protocol Rule 4.
Defining and Configuring AutoTracker Policies Page 20-7 Defining a MA C Addr ess Range P olicy After you enter the Administrative Status, the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3. Protocol Rule 4.
Defining and Configuring AutoTracker Policies Page 20-8 Defining a Protocol P olicy After you enter the Administrative Status for this mobile group or AutoTracker VLAN , the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3.
Defining and Configuring AutoTracker Policies Page 20-9 If you want to define a protocol other than IP , IPX , AppleTalk, or DECN et, you can do so by specifying an Ethernet type, or by specifying source and destination SAP (service access protocol) header values, or by specifying a SNAP (sub-network access protocol) type.
Defining and Configuring AutoTracker Policies Page 20-10 Protocol Speci fied by Ether-Type a. To specify a protocol by Ethernet type, enter 5 at the Select Protocol: menu. The follow- ing prompt displays: Enter the Ether-type value in hex: b. Enter the desired Ethernet type in hex.
Defining and Configuring AutoTracker Policies Page 20-11 Defining a Netw ork Addr ess P olicy After you enter the Administrative Status for this mobile group or AutoTracker VLAN , the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3.
Defining and Configuring AutoTracker Policies Page 20-12 Set Up an IPX Addr ess a. To specify an IPX address, enter a 2 at the Select the Network Protocol: prompt. b. The following prompt displays: Enter the IPX Network Number: Enter an IPX network number to define the network devices you want included in the mobile group or AutoTracker VLAN .
Defining and Configuring AutoTracker Policies Page 20-13 Defining Y our Own Rules A user-defined rule enables you to include all devices in the mobile group or AutoTracker VLAN that originate frames containing a specified pattern at a specified location.
Defining and Configuring AutoTracker Policies Page 20-14 For example, if you enter FFEF as the value and FFFF as the mask: Hex Binary Value= FFEF = 1111 1111 1110 1111 Mask= FFFF = 1111 1111 1111 1111 When a bit in the mask is set to 1, the corresponding bit of the value must be literal.
Defining and Configuring AutoTracker Policies Page 20-15 Defining a P ort Binding P olicy Port binding polices require devices to match two or three criteria. The criteria can be one of six combinations: 1. The device can attach to a specific switch port and use a specific MAC address and use a specific protocol (IP or IPX).
Defining and Configuring AutoTracker Policies Page 20-16 After you indicate you want to set up rules for this mobile Group or AutoTracker VLAN (using the cratvl command) , the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3.
Defining and Configuring AutoTracker Policies Page 20-17 4. The following prompt displays: Enter the port in the form of slot/interface: Enter the switch port to which this device must be attached. If the device is not attached to this port, it will not be included in this mobile Group or AutoTracker VLAN.
Defining and Configuring AutoTracker Policies Page 20-18 If you want to define a protocol other than IP , IPX , AppleTalk, or DECN et, you can do so by specifying an Ethernet type, or by specifying source and destination SAP (service access protocol) header values, or by specifying a SNAP (sub-network access protocol) type.
Defining and Configuring AutoTracker Policies Page 20-19 Protocol Speci fied by Ether-Type a. To specify a protocol by Ethernet type, enter 5 at the Select Protocol: menu. The follow- ing prompt displays: Enter the Ether-type value in hex: b. Enter the desired Ethernet type in hex.
Defining and Configuring AutoTracker Policies Page 20-20 Defining a DHCP P ort P olicy DHCP port polices simplify network configurations requiring DHCP clients and servers to be in the same mobile group or AutoTracker VLAN. You can see how DHCP port policies were used in an application example on page 20-27.
Defining and Configuring AutoTracker Policies Page 20-21 Defining a DHCP MA C Addr ess P olicy You can see how DHCP MAC address policies were used in an application example on page 20-27. After you enter the Administrative Status for this mobile group or AutoTracker VLAN , the following menu displays: Select rule type: 1.
Defining and Configuring AutoTracker Policies Page 20-22 Defining a DHCP MA C Addr ess Range P olicy You can see how DHCP MAC address policies were used in an application example on page 20-27. After you enter the Administrative Status for this mobile group or AutoTracker VLAN , the following menu displays: Select rule type: 1.
Viewing Mobile Groups and AutoTracker VLANs Page 20-23 Vie wing Mobile Groups and A utoTr acker VLANs You can view the current status of all mobile groups or AutoTracker VLANs in the switch using the atvl command. Enter atvl and a table similar to the following displays.
Viewing Policy Configurations Page 20-24 Vie wing P olicy Configur ations Typing viatrl brings up the Policy Configuration Table, which shows the policies defined for the mobile Group or VLAN specified.
Viewing Virtual Ports’ Group/VLAN Membership Page 20-25 Vie wing Virtual P orts’ Group/VLAN Member ship You can view the VLAN membership of each virtual interface in the switch. For physical LAN ports, the virtual interface is the same as a virtual port.
View VLAN Membership of MAC Devices Page 20-26 Vie w VLAN Membership of MA C De vices The fwtvl command displays a table of learned MAC addresses and the VLAN membership of those MAC addresses. Follow these steps to view this table. 1. Enter fwtvl . 2.
Application Example: DHCP Policies Page 20-27 Application Ex ample: DHCP P olicies This application example shows how Dynamic Host Configuration Protocol ( DHCP ) port and MAC address policies can be used in a DHCP -based network.
Application Example: DHCP Policies Page 20-28 DHCP Server s and Clients DHCP clients must be able to communicate with a DHCP server at initialization. The most reli- able way to ensure this communication is for the server and its associated clients to share the same VLAN or mobile group.
Application Example: DHCP Policies Page 20-29 12345678 123456 Omni Switch/Router Client 1 DHCP Port Rule Client 2 DHCP Port Rule Client 3 DHCP Port Rule Client 4 DHCP Port Rule Client 5 DHCP Port Rule Server 1 10.
Application Example: DHCP Policies Page 20-30.
Page 21-1 21 Inter switch Pr otocols This chapter describes Interswitch Protocols, which are used to discover adjacent switches, and track VLAN membership and retain mobile group information across switches. They include two new protocols and one existing protocol that is updated for release 4.
XMAP Page 21-2 XMAP The Mapping Adjacency Protocol ( XMAP ) is used to discover the topology of OmniS/Rs in a particular installation. Using this protocol, each switch determines which OmniS/Rs are adja- cent to it by sending and responding to Hello update packets.
XMAP Page 21-3 XMAP Tr ansmission States XMAP switch ports are either in the discovery transmission state , common transmission state , or passive reception state . Ports transition to these states depending on whether or not they receive Hello responses from adjacent switches.
XMAP Page 21-4 Common Tr ansmission State In the common transmission state, ports detect adjacent switch failures or disconnects by sending Hello packets and waiting for Hello responses. Ports in this state send out Hello packets at a configurable interval (the default is 5 minutes) called the common transmission time .
Configuring XMAP Page 21-5 Configuring XMAP XMAP is active by default. In addition to disabling or enabling XMAP , you can view a list of adjacent switches or configure the timeout intervals for Hello packet transmission/reception.
Configuring XMAP Page 21-6 A visual illustration of these connections is shown here: XMAP Network Example The fields in xmapls table are defined as follows: VPN . The local virtual port number which is connected to an adjacent switch. Rem Switch ID . The MAC address of the MPX in the adjacent switch.
Configuring XMAP Page 21-7 A message similar to the following displays: XMAP Discovery Phase Timeout Interval is 30 seconds. To change the interval, enter the command with the desired value (any value between 1 and 65535). For example: xmapdisctime 20 A message similar to the following displays: XMAP Discovery Phase Timeout Interval is 20 seconds.
VLAN Advertisement Protocol (VAP) Page 21-8 VLAN A dvertisement Pr otocol (V AP) The VLAN Advertisement Protocol ( VAP ) is an interswitch protocol that keeps the VLAN membership databases stored on switches in sync and enables the auto-discovery of network nodes.
VLAN Advertisement Protocol (VAP) Page 21-9 V AP and P ort P olicies One of the main purposes of VAP is to advertise the connectivity of devices attached to the switch via AutoTracker port policies. VAP eliminates the need to apply port policies to back- bones to ensure that connectivity is established and maintained.
GMAP Page 21-10 GMAP The Group Mobility Advertisement Protocol ( GMAP ) enables workstation users to move from port to port among interconnected switches and still retain all learned mobile group and protocol information.
GMAP Page 21-11 Configuring GMAP GMAP is inactive by default. In addition to enabling and disabling GMAP , you can configure the time between packet transmissions (when multiple packets are required for an update), the time between updates, and the length of time GMAP will retain its current information.
GMAP Page 21-12 Configuring the Interpacket Update Time Use the gmapupdtime command to display or change the time between sending updates. ♦ Note ♦ The switches avoid synchronization by jittering the update time by plus or minus one quarter of the config- ured interval.
GMAP Page 21-13 Displaying GMAP Statistics by MA C Addr ess To display GMAP statistics for all MAC addresses, use the gmapls command. The screen displays similar to the following: GMAP Table =========.
GMAP Page 21-14.
Page 22-1 22 Managing A utoT r acker VLANs In a large, flat, switched network, broadcast traffic can overload a network based primarily on port-based Groups. Through the use of AutoTracker VLAN s, you can control broadcast traffic such that it is forwarded only to those VLAN s where it needs to be sent.
The AutoTracker Menu Page 22-2 The A utoTr acker Menu All software commands for configuring AutoTracker policies and AutoTracker/multicast VLANs are in the AutoTracker menu. This menu is a submenu of the VLAN menu. You can access the AutoTracker menu by typing at any prompt.
AutoTracker VLANs Page 22-3 A utoTr acker VLANs AutoTracker VLAN s enable you to control communications between end stations in your network. You define policies that determine membership in the VLAN and AutoTracker auto- matically locates ports or devices within the Group that fit the policies and places them into the VLAN .
AutoTracker VLANs Page 22-4 Network Address Policies . Network address policies enable you to define membership in the VLAN on the basis of network address criteria. For example, you can specify that all IP users with a specific subnet mask be included in the VLAN .
AutoTracker VLANs Page 22-5 How De vices are Assigned to A utoTr acker VLANs When a broadcast frame, a multicast frame, or a unicast frame from an unknown device is received at a switching module, the frame is forwarded to the MPX for processing.
AutoTracker VLANs Page 22-6 Devices that Gener ate a Secondary Tr affic Type Source devices sometimes generate more than one traffic type; for example, a device could generate IP traffic primarily but also generate a secondary stream of AppleTalk.
AutoTracker VLANs Page 22-7 How De vices are Assigned to A utoTr acker VLAN s (continued) Router Tr affic in IP and IPX Network A ddress VLAN s Prior to release 2.1, AutoTracker handled VLAN assignments for router traffic in IP and IPX network address VLAN s in the same manner as normal traffic.
AutoTracker VLANs Page 22-8 12345678 123456 VLAN 3 Network 3 Group 2 VLAN 2 Network 2 Device B Network 3 MAC address = B Device A Network 2 MAC address = A Interface for Network 2 MAC address = X Interface for Network 3 MAC address = Y ➋ ➍ Let’s say that the next transmission is a RIP update from the router interface for network 3.
AutoTracker VLANs Page 22-9 How De vices are Assigned to A utoTr acker VLAN s (continued) P ort P olicy Functionality In release 2.1 and later, AutoTracker’s VLAN port policy can be set to operate i.
AutoTracker VLANs Page 22-10 12345678 123456 Omni Switch/Router 2 1 2 3 4 5 6 7 8 1 2 3 4 5 6 Omni Switch/Router 1 FDDI Backbone Group 1 Device D Slot 2 Port 2 Slot 2 Port 1 Device A Slot 3 Port 1 Ori.
AutoTracker VLANs Page 22-11 12345678 123456 Omni Switch/Router 2 1 2 3 4 5 6 7 8 1 2 3 4 5 6 Omni Switch/Router 1 FDDI Backbone Group 1 Device D Slot 2 Port 2 Slot 2 Port 1 Device A Slot 3 Port 1 Cur.
AutoTracker VLANs Page 22-12 The U sefulness of P ort P olicies As has been explained – and as illustrated on page 22-10 – original port policy functionality is not well-suited to the creation of consistent VLAN membership in a multi-switch environment.
AutoTracker VLANs Page 22-13 So How Do I Get De vices Assigned to VLAN s Ov er a Backbone? The way to get devices assigned to VLAN s over a backbone is to define logical VLAN policies that so assign them. An example is shown on the facing page utilizing IP and IPX protocol policies.
AutoTracker VLANs Page 22-14 12345678 123456 Omni Switch/Router 2 1 2 3 4 5 6 7 8 1 2 3 4 5 6 Omni Switch/Router 1 FDDI Backbone Device D IP Device A IPX Slot 3 Port 1 Device Source P ort VLAN Members.
AutoTracker VLANs Page 22-15 Frame Flooding in A utoTr acker VLANs Flooding occurs when a frame is received addressed to a device that is unknown to the switch or broadcast or multicast frames are received addressed to multiple users. In a typical bridged environment, the frame would be forwarded out all ports.
Creating AutoTracker VLANs Page 22-16 Cr eating AutoT racker VLANs You create AutoTracker VLAN s through the AutoTracker menu options. Creating an AutoTracker VLAN includes the following steps: A. Enter basic information such as the name and number for the VLAN .
Creating AutoTracker VLANs Page 22-17 5. The following prompt displays: Enter the Admin Status for this vlan (Enable (e) / Disable (d): Enter whether or not you want the Administrative Status for this VLAN to be enabled or disabled. Once enabled, the switch begins using the policies you defined.
Creating AutoTracker VLANs Page 22-18 Step B . Defining and Configuring VLAN P olicies You can define AutoTracker policies by port, MAC address, protocol, network address, user definition, or port binding. You can define multiple policies for a AutoTracker VLAN if you wish.
Creating AutoTracker VLANs Page 22-19 Step C. Configuring the Virtual Router P ort (Optional) You can now optionally configure the virtual router port that this VLAN will use to communi- cate with other AutoTracker VLAN s. A virtual router port for the VLAN is created within the switch.
Creating AutoTracker VLANs Page 22-20 7. The following prompt displays: Enable NHRP? (n) : Indicate whether you want to enable NHRP. 8. The following prompt displays: IP RIP Mode {Deaf (d), Silent (s), Active (a), Inactive (i)} (s): Define the RIP mode in which the virtual router port will operate.
Creating AutoTracker VLANs Page 22-21 Default Framing Type and the Virtual Router Port 10. You can now configure IPX routing on this port. The following message displays: Enable IPX? (y) : Press <Enter> if you want to enable IPX Routing on this virtual router port.
Creating AutoTracker VLANs Page 22-22 13. After entering a description, the following prompt displays: IPX RIP and SAP mode {RIP and SAP active (a) RIP only active (r) RIP and SAP inactive (i)} (a): Select how you want the IPX protocols, RIP (router internet protocol) and SAP (service access protocol), to be configured for this VLAN .
Creating AutoTracker VLANs Page 22-23 15. If you chose a Source Routing frame format in the last step (options 5, 7, 9, or b), the an additional prompt displays: Default source routing broadcast type : { ARE broadcasts(a), STE broadcasts(s)} (a) : Select how broadcasts will be handled for Source Routing.
Modifying an AutoTracker VLAN Page 22-24 Modi fying an AutoT racker VLAN After you set up a VLAN you can modify its Admin Status, description, rules, and the Admin Status of each of the rules.
Modifying an AutoTracker VLAN Page 22-25 Changing a VLAN’s Description 1. At the Option= prompt enter a 2 and press <Enter> . 2. The following prompt displays: Enter a new description: Type in the revised description for this VLAN . The description can be up to 30 characters long.
Modifying an AutoTracker VLAN Page 22-26 Changing the Admin Status for a VLAN P olicy 1. At the Option= prompt enter a 5 and press <Enter> . 2. The following menu displays: Enter rule number: The rule number is listed with other information on the VLAN just after you entered the modatvl command.
Viewing AutoTracker VLANs Page 22-27 Vie wing AutoT racker VLANs You can view the current status of all AutoTracker VLANs in the switch using the atvl command.
Viewing Policy Configurations Page 22-28 Vie wing P olicy Configur ations Typing viatrl brings up the Policy Configuration Table, which shows the policies defined for the VLAN specified.
Viewing Virtual Ports’ VLAN Membership Page 22-29 Vie wing Virtual P orts’ VLAN Membership You can view the VLAN membership of each virtual interface in the switch. For physical LAN ports, the virtual interface is the same as a virtual port. However, when multiple services are set up for a physical port, then each service has a virtual port.
View VLAN Membership of MAC Devices Page 22-30 Vie w VLAN Membership of MA C De vices The fwtvl command displays a table of learned MAC addresses and the VLAN membership of those MAC addresses. Follow these steps to view this table. 1. Enter fwtvl . 2.
Creating a VLAN for Banyan Vines Traffic Page 22-31 Cr eating a VLAN for Bany an Vines Tr affic Banyan Vines uses a fixed encapsulation for each network interface.
Creating a VLAN for Banyan Vines Traffic Page 22-32 8. The following prompt displays: Select Protocol: 1. IP 2. IPX 3. DECNET 4. APPLETALK 5. Protocol specified by ether-type 6. Protocol specified by DSAP and SSAP 7. Protocol specified by SNAP Enter protocol type (1): Enter a 5 to define a protocol by ether-type and press <Enter> .
Creating a VLAN for Banyan Vines Traffic Page 22-33 15. The following prompt displays Enter the DSAP value in hex: Enter bc as the destination service access protocol ( DSAP ) value and press <Enter> .
Creating a VLAN for Banyan Vines Traffic Page 22-34 22. The following prompt displays: Configure more rules for this vlan (y/n): Enter an N . You are done setting up rules for this VLAN . A prompt similar to the follow- ing displays: VLAN 1:2 created successfully 23.
Page 23-1 23 Multicast VLANs Multicast VLANs enable you to control the flooding of multicast traffic in your network. For example, you can define a multicast VLAN for all users that want to receive CNN Newscasts or any other video feed or combination of feeds.
Page 23-2 How De vices are Assigned to Multicast VLANs If the recipients of the multicast traffic were defined using the port rule, each specified port is then marked as a member of the multicast VLAN .
Page 23-3 Frame Flooding in Multicast VLAN s Multicast traffic is flooded as follows in an environment that includes multicast VLAN s: • If the destination address is a multicast address, and • if.
Creating Multicast VLANs Page 23-4 Cr eating Multicast VLANs You create multicast VLAN s through the AutoTracker menu options. Creating a multicast VLAN includes the following steps: A. Entering basic information such as the name and number for the multicast VLAN .
Creating Multicast VLANs Page 23-5 Step A. Entering Basic Information 1. To begin setting up a multicast VLAN type crmcvl at any prompt. 2. The following prompt displays: Enter the VLAN Group id for this VLAN ( 1): Enter the number for the Group to which this multicast VLAN will belong.
Creating Multicast VLANs Page 23-6 Step B . Defining the Multicast Addr ess The multicast address is an address that identifies a multicast traffic stream, such as CNN News. ♦ Please Take Note ♦ The source port of the multicast traffic (i.e., the port through which multicast traffic enters the switch) can be a member of any Group.
Creating Multicast VLANs Page 23-7 Step C. Defining the Recipients of Multicast Tr affic You can define the recipients of multicast traffic by virtual port or MAC address. You define these recipients as policies for this multicast VLAN . The available policies for recipients are Port and MAC Address.
Creating Multicast VLANs Page 23-8 Defining Recipients By MA C Addr ess After you define the multicast address, the following menu displays: Select rule type: 1. Port Rule 2. MAC Address Rule 3. Multicast Address Rule Enter rule type (1): 1. Press 2 and <Return> .
Modifying Multicast VLANs Page 23-9 Modi fying Multicast VLANs After you set up a multicast VLAN you can modify its Admin Status, description, rules, and the Admin Status of each of the rules.
Modifying Multicast VLANs Page 23-10 Changing a VLAN’s Description 1. At the Option= prompt enter a 2 and press <Enter> . 2. The following prompt displays: Enter a new description: Type in the revised description for this multicast VLAN . The description can be up to 30 characters long.
Modifying Multicast VLANs Page 23-11 Changing the Admin Status for a VLAN P olicy 1. At the Option= prompt enter a 5 and press <Enter> . 2. The following menu displays: Enter rule number: The rule number is listed with other information on the multicast VLAN just after you entered the modmcvl command.
Modifying a Multicast Address Policy Page 23-12 Modi fying a Multicast Addr ess P olic y After you create a multicast VLAN , you can modify the multicast address policy by adding more addresses through the modmcvl command. However, you can not add an existing multi- cast address.
Viewing Multicast VLANs Page 23-13 Vie wing Multicast VLANs You can view the current status of all multicast VLAN s in the switch using the mcvl command.
Viewing Multicast VLAN Policies Page 23-14 Vie wing Multicast VLAN P olicies You can view the current multicast VLAN policies and their status using the vimcrl command.
Viewing the Virtual Interface of Multicast VLANs Page 23-15 Vie wing the Virtual Interface of Multicast VLANs You can view the multicast VLAN membership of each virtual interface in the switch. In most cases the virtual interface is the same as a virtual port.
Viewing the Virtual Interface of Multicast VLANs Page 23-16.
Page 24-1 24 A utoT r acker VLAN Application Ex amples This chapter provides specific examples of AutoTracker VLAN s in various network configura- tions. These examples illustrate basic concepts about AutoTracker and highlight issues that can arise when AutoTracker is used in different network situations.
Application Example 1 Page 24-2 Application Ex ample 1 VLAN s Based on Logical P olicies Example 1 shows a network organized logically. The network is organized according to IP networks, but this organization is achieved through the application of logical policies rather than physical segmentation.
Application Example 1 Page 24-3 Omni Switch/Router 12345678 123456 VLAN A Internal IP Router 1 2 5 .0 .0 .3 5 1 3 0 .0 .0 .2 2 IP Nnetwork 125.0.0.0 VLAN B IP Network 130.0.0.0 Group 2 P orts 1, 2, 3, and 4 IP Workstations IP Workstations 125.0.0.1 125.
Application Example 2 Page 24-4 Application Ex ample 2 VLAN s in IPX Netw orks Example 2 illustrates the use of AutoTracker VLAN s in IPX networks – specifically, VLAN s based on IPX network address rules. IPX networks have unique characteristics that must be considered when configuring VLAN s based on network address rules.
Application Example 2 Page 24-5 12345678 123456 Omni Switch/Router IPX Client VLAN Membership Client 1 both B & C initially, then either B or C when net- work number is known Client 2 both B &.
Application Example 2 Page 24-6 In this example one Group was created – Group 3 – that includes all ports to which IPX serv- ers and clients are connected.
Application Example 3 Page 24-7 Application Ex ample 3 IPX Netw ork Addr ess VLAN s and Tr anslated Frames Application Example 3 shows two IPX networks connected over a bridged FDDI ring span- ning two Omni Switch/Routers.
Application Example 4 Page 24-8 Application Ex ample 4 Routing in IPX N etworks How Routing W orks Generally AutoTracker “activates” a VLAN – and its internal router interface – when the first port is assigned to the VLAN . If a VLAN has a port policy, AutoTracker assigns the specified port(s) and activates the VLAN immediately.
Application Example 4 Page 24-9 Important Note If you enable routing for a Group, you are actually enabling routing for that Group’s default VLAN #1. For this reason, do not enable routing for any Group in which an IPX server is a member of an IPX network address VLAN .
Application Example 5 Page 24-10 Application Ex ample 5 Tr aver sing a Backbone Application Example 5 illustrates why port-based policies may be required to establish communications in some network situations, such as traversing a backbone.
Application Example 5 Page 24-11 The Solution The recommended solution is to add a port policy to VLAN D , as is shown in the figure below. A port policy can be defined in addition to any other policies defined for a VLAN .
Application Example 5 Page 24-12.
Page 25-1 25 IP Routing Intr oduction This chapter gives an overview of IP routing and includes information about configuring static routes and viewing/configuring TCP/IP protocols such as Telnet and the Routing Information Protocol ( RIP ). IP routing requires at least one virtual router port to be configured on the switch.
IP Routing Overview Page 25-2 IP Routing Ov erview In switching, traffic may be transmitted from one media type to another within the same broadcast domain (or group/ VLAN ). Switching happens at layer 2, the physical layer; routing happens at layer 3, the network layer.
IP Routing Overview Page 25-3 Tr ansport Protocols IP is both connectionless (it routes each datagram separately) and unreliable (it does not guarantee delivery of datagrams). This means that a datagram may be damaged in transit, or thrown away by a busy router, or simply never make it to its destination.
Setting Up IP Routing on the Switch Page 25-4 Setting Up IP Routing on the Switch IP routing is enabled on a per-port basis by creating a virtual IP router port for a group/ VLAN . The switch does not do any routing unless the virtual router port has IP routing enabled (routing is enabled by default).
Setting Up IP Routing on the Switch Page 25-5 Step 3. Configuring Other IP Routing Features There are several optional features that may be used with IP routing. Some features are included as part of the base code and are described in this user manual.
The Networking Menu Page 25-6 The N etworking Menu The Networking menu contains commands that control, and are related to, the routing proto- cols that are run on the switch.
The IP Submenu Page 25-7 The IP Submenu The ip command in the Networking menu is used to display the IP submenu. To display the IP submenu, enter the following commands: ip ? If you have enabled the verbose mode, you don’t need to enter the question mark ( ? ).
Viewing the Address Translation (ARP) Table Page 25-8 Vie wing the Addr ess Tr anslation (ARP) T able The xlat command is used to access the ARP (Address Resolution Protocol) Table. This table contains a listing of IP addresses and their corresponding translations to MAC addresses (or slot/port for WAN interfaces).
Viewing the Address Translation (ARP) Table Page 25-9 Adding Entries to the ARP T able The add subcommand is used to manually add an IP address entry to the ARP Table. To be able to manage your switch over an IP network connection, you will need at least one IP address configured for the switch.
Viewing the Address Translation (ARP) Table Page 25-10 Deleting Entries from the ARP T able The Delete subcommand is used to delete a “permanent” IP address from the ARP Table. Follow the steps below to delete an address from the ARP Table. 1. Enter delete .
Viewing the Address Translation (ARP) Table Page 25-11 Finding a Specific MA C Addr ess in the ARP T able The Ipfind subcommand is used to locate a specific MAC address in the ARP Table based on a known IP address or host name . (The Macfind subcommand, discussed above, is used to find a specific IP address based on a known MAC address).
Viewing IP Statistics and Errors Page 25-12 Vie wing IP Statistics and Error s The ips command is used to monitor IP datagram traffic and errors. The ips command displays cumulative IP statistics and errors. The statistics show the cumulative totals since the last time the switch was powered on or since the last reset of the switch was executed.
Viewing IP Statistics and Errors Page 25-13 Fastpath Datagr ams Forwar ded (Displays for Omni S/R) The number of IP datagrams forwarded to their destination without using the MPX . Fastpath Inbound Discar ds (Displays for Omni S/R) The number of bad packets received and discarded.
Viewing IP Statistics and Errors Page 25-14 PDU s Needing Reassembly The number of IP datagram fragments that needed to be reassembled by this switch. PDU s Successfully Reassembled The number of IP datagrams successfully reassembled by this switch. PDU s Needing Fragmentation The number of IP datagrams requiring fragmentation by this switch.
Viewing the IP Forwarding Table Page 25-15 Vie wing the IP Forw arding T able The ipr command is used to display the IP Forwarding Table. The entries in the table show the routes entered by a routing protocol, if the switch is running any of the supported proto- cols, and the static routes that you may have entered manually.
Viewing the IP Forwarding Table Page 25-16 The fields on the IP Forwarding Table have the following meanings: Netw ork The destination network IP address. Mask The IP subnet mask. Ga tewa y The network address of the gateway (the router from which this address was learned).
Adding an IP Static Route Page 25-17 A dding an IP Static Route The aisr command is used to add IP static routes to the switch’s IP Forwarding Table. You might want to add a static route to send traffic to a router other than the one determined by the routing protocols.
Adding an IP Static Route Page 25-18 5. The following prompt displays: IP address of next hop : Enter the IP address of the next hop (the gateway) router to the destination IP address. The gateway address must be on the same network as one of the VLANs (that is, it must be a directly connected network).
Removing an IP Static Route Page 25-19 Remo ving an IP Static Route The risr command is used to remove IP static routes from the switch’s IP Forwarding Table. Follow the steps below to remove an IP static route. 1. Enter risr. The prompt that displays depends on whether routing domains are configured on the switch.
Viewing ICMP Statistics and Errors Page 25-20 Vie wing ICMP Statistics and Error s The icmps command is used to monitor ICMP activity. To display information about ICMP statistics and errors, enter th.
Viewing ICMP Statistics and Errors Page 25-21 Addr ess Mask Messages The number of Address Mask Reply messages that were sent/received by this switch in an attempt to determine the subnet mask for a network. Addr ess Mask Reply Messages The number of Address Mask Reply messages that were sent/received by this switch.
Using the PING Command Page 25-22 U sing the PING Command The ping command is used to test the reachability of IP network destinations. A fast ping command ( fping ) is also available for repeating the last ping request sent from the switch. The commands sends an ICMP echo request to a destination and then waits for a reply.
Using the PING Command Page 25-23 5. After answering the previous prompt, a screen similar to the following displays: Ping starting, hit <RETURN> to stop PING 198.206.184.18: 64 data bytes [0 ] . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing UDP Statistics and Errors Page 25-24 Vie wing UDP Statistics and Error s The udps command is used to display a listing of UDP statistics and errors. The udps command displays cumulative statistics since the last time the switch was powered on or since the last reset of the switch was executed.
Viewing the UDP Listener Table Page 25-25 Vie wing the UDP Listener T able The udpl command is used to display the UDP Listener Table. This table contains information about the switch’s UDP end-points on which a local application is currently accepting data- grams.
Viewing RIP Statistics and Errors Page 25-26 Vie wing RIP Statistics and Error s The rips command is used to display RIP statistics and errors. This command displays cumula- tive statistics since the last time the switch was powered on, or since the last reset of the switch was executed.
Viewing TCP Statistics Page 25-27 Vie wing TCP Statistics The tcps command is used to monitor TCP traffic activity and check TCP configuration param- eters.
Viewing TCP Statistics Page 25-28 Established Resets The number of times TCP connections have made a direct transition to the “closed” state from either the “established” state or the “closeWait” state. Currently Established The number of TCP connections for which the current state is either “established” or “closeWait”.
Viewing the TCP Connection Table Page 25-29 Vie wing the TCP Connection T able The tcpc command is used to check the current TCP connections available in the TCP Connection Table.
Using the TELNET Command Page 25-30 U sing the TELNET Command The telnet command is used to connect to another system. All of the standard TELNET commands are supported by the software in the switch.
Tracing an IP Route Page 25-31 T racing an IP Route The traceroute command is used to find the IP route from the local switch to a specified IP address destination. This command displays the individual hops to the destinations as well as some timing information.
Flushing the RIP Routing Tables Page 25-32 Flushing the RIP Routing T ables The ripflush command is used to flush all entries in the RIP Routing Table. All existing routes, with the exception of static and direct routes, are removed from the table by entry of the ripflush command.
Configuring IP RIP Filters Page 25-33 Configuring IP RIP Filter s The ipfilter command is used to add or delete an IP RIP Output or Input filter. The IP RIP Filtering feature gives you a means of controlling the operation of the IP RIP protocol.
Configuring IP RIP Filters Page 25-34 4. The following prompt displays: IP address (default: all networks) : Enter the IP address of the network that is to be allowed or blocked by the filter (or just press Enter to use the default of all networks).
Configuring IP RIP Filters Page 25-35 5. The following prompt displays: IP network mask (default: 255.255.255.0) : Enter the IP network mask of the network that is to be allowed or blocked by the filter (or just press Enter to use the default mask of 255.
Configuring IP RIP Filters Page 25-36 Deleting IP RIP Filter s Follow the steps below to delete an existing IP RIP Output or Input filter. 1. Enter ipfilter. A screen similar to the following displays: Selecting global IP filter: Add or delete entry {add(a), delete(d)} (a) : Enter d to select to delete a filter.
Configuring IP RIP Filters Page 25-37 Displaying IP RIP Filters The ipf command is used to display a list of all existing IP RIP Output and Input filters. See Configuring IP RIP Filters on page 25-33 for complete information on creating these filters.
Configuring IP RIP Filters Page 25-38 Displaying a List of “Global” IP RIP Filters To display a listing of just the global IP RIP filters, enter the following command: ipf global A screen similar .
Viewing the IP-to-MAC Address Table Page 25-39 Vie wing the IP-to-MA C Addr ess T able The ipmac command is used to display the IP-to-Mac Address Association Table. This table contains a listing of IP addresses and their associated MAC (Media Access Control) addresses together with the slot/port from which the information was learned.
Viewing the IP-to-MAC Address Table Page 25-40 Slot/Intf The slot number and interface number from which the IP and MAC addresses were learned. Displaying Information for a Specific IP A ddress To display the entry in the IP-to-MAC table for a specific IP address, enter the desired IP address after the command.
Enabling/Disabling Directed Broadcasts Page 25-41 Enabling/Disabling Dir ected Broadcasts An IP directed broadcast is an IP datagram that has all zeroes or all 1’s in the host portion of the destination IP address. The packet is sent to the broadcast address of a subnet to which the sender is not directly attached.
Path MTU Discovery Page 25-42 P ath MTU Discov ery All Gigabit Ethernet modules and all Mammoth-based Ethernet modules on the Omni Switch/Router in Release 4.
Page 26-1 26 UDP F orw ar ding UDP is a connectionless transport protocol that is used for applications that do not require the establishment of a session and end-to-end error checking, such as email and file transfer.
Page 26-2 In non-source route environments, RIF stripping may be required if DHCP clients are token ring stations. Token ring stations may have packets with RIFs even though source routing is not enabled on the station. RIF stripping is required if there is bridging to Ethernet, FDDI , or 802.
UDP Relay Configuration Screen Page 26-3 UDP Relay Configur ation Screen To configure any of the UDP relays, use the relayc command. The relayc command is listed in the IP submenu. (For more information about IP commands, see Chapter 25, “IP Routing.
BOOTP/DHCP Relay Page 26-4 BOO TP/DHCP Relay The switch supports a UDP relay function that allows Bootstrap Protocol ( BOOTP ) and Dynamic Host Configuration Protocol ( DHCP ) packets to pass between AutoTracker Groups. ♦ Note ♦ A BOOTP / DHCP relay may be configured for authenti- cated groups as well.
BOOTP/DHCP Relay Page 26-5 In multiple group configurations, AutoTracker rules can be deployed to strategically support the relay function. Two types of AutoTracker IP policies are appropriate for DHCP environ- ments. The first is the IP protocol policy that puts all IP type frames into a single VLAN regard- less of network address.
BOOTP/DHCP Relay Page 26-6 External BOOTP Relay The BOOTP relay may be configured on a router that is external to the switch. In this applica- tion example the switched network has a single AutoTracker Group configured with multiple segments. All of the network hosts are DHCP -ready, meaning they obtain their network address from the DHCP server.
BOOTP/DHCP Relay Page 26-7 Internal BOOTP/DHCP Relay The internal BOOTP/DHCP relay is configured using the UDP forwarding feature in the switch, available through the relayc command. See UDP Relay Configuration Screen on page 26-3. Example 1 This application example shows a network with two AutoTracker Groups, each with multiple segments.
BOOTP/DHCP Relay Page 26-8 Because the clients in group 3 are not on the same segment as the DHCP server, they must request an IP address via the BOOTP relay routing entity in the switch. When a DHCP request frame is received by the BOOTP relay entity, it will be forwarded from group 3 to group 2.
BOOTP/DHCP Relay Page 26-9 In this example, the VLAN defined by an IP protocol policy is used as a mechanism to group the DHCP server and associated clients . The DHCP server is local, so all clients requesting an IP address will be allocated an IP address on the same subnet.
BOOTP/DHCP Relay Page 26-10 Forw ard Delay The amount of time (typically in seconds, but determined by the client) the BOOTP/DHCP relay will wait before forwarding a request to the server address. This delay gives a local server a chance to respond to a client before the relay forwards it further out in the network.
NetBIOS Relays Page 26-11 N etBIOS Relays The switch supports a UDP relay function that allows Network Basic Input/Output System ( NetBIOS ) messages to be sent across groups or VLANs . Overvie w of NetBIOS NetBIOS is an applications interface that allows computers on Ethernet or token ring LANs to communicate with one another.
NetBIOS Relays Page 26-12 NetBIOS Relay Application The UDP relay function in the switch extends b-node functionality across the internet. An example application is shown here. NetBIOS Relay Application In this example, NBNS and NBDD relays should be configured to forward to VLAN 10 and VLAN 20.
NetBIOS Relays Page 26-13 Configuring NBNS Relay Each NetBIOS PC has a name unique for its local network. If you are using NetBIOS broadcast queries to resolve names and NetBIOS clients are located in different groups or VLANs , you should configure UDP relay for NBNS .
NetBIOS Relays Page 26-14 Ne xt-Hop Addr esses for NBNS At least one next-hop address (or a forwarding VLAN as described in Forwarding VLANs for NBNS Relay on page 26-15) must be configured.
NetBIOS Relays Page 26-15 Forw arding VLANs for NBNS Relay At least one forwarding VLAN (or a next-hop address as described in Next-Hop Addresses for NBNS on page 26-14) must be configured for NBNS relay.
NetBIOS Relays Page 26-16 Configuring NBDD Relay If you want to send NetBIOS datagrams across networks, you should enable the NBDD relay. To enable the NBDD relay, enter 3=y at the command prompt of the UDP Relay Configuration screen.
NetBIOS Relays Page 26-17 Ne xt-Hop Addr esses for NBDD At least one next-hop address ( or a forwarding VLAN as described in Forwarding VLANs for NBDD Relay on page 26-18) must be configured for the relay.
NetBIOS Relays Page 26-18 Forw arding VLANs for NBDD Relay You may select or deselect VLANs to which the NBDD relay will forward. At least one forward- ing VLAN (or a next-hop address as described in Next-Hop Addresses for NBDD on page 26-17) must be configured for the relay.
Generic Service UDP Relay Page 26-19 Generic Service UDP Relay UDP relay may be configured for generic services. Generic services may include applications such as Trivial File Transfer Protocol ( TFTP ), Domain Name System ( DNS ), IEN-116 Name Server.
Generic Service UDP Relay Page 26-20 Forw ard to VLANs Use this parameter to list, add, or delete VLANs to which the NBNS UDP relay will forward. This default is UNSET . This value redisplays as SET when at least one VLAN is configured. Up to 32 VLANs may be configured.
Generic Service UDP Relay Page 26-21 Modi fying a Generic Service Use the Configured Generic Services screen to modify an existing generic service. On the Generic Services Menu, enter 41 . A screen similar to the following displays: Configured Generic Services Item State Port Number Description Servers/Vlans (1) enabled 80 TFTP 198.
Generic Service UDP Relay Page 26-22 4. Enter d to return to the UDP Relay Configuration screen. 5. Enter s to save the changes and reinitialize the relay. Deleting a Generic Service To delete a generic service: 1. On the Generic Services Menu, enter 42 .
Viewing UDP Relay Statistics Page 26-23 Vie wing UDP Relay Statistics Use the relays command to display statistics about configured UDP relays. The relays command is listed in the IP submenu. For information about other IP commands, see Chap- ter 25, “IP Routing.
Viewing UDP Relay Statistics Page 26-24.
Page 27-1 27 IPX Routing Intr oduction This chapter gives an overview of Internetwork Packet Exchange (IPX) routing and includes information about configuring static IPX routes as well as configuring Routing Information Protocol ( RIP ) and Service Advertising Protocol ( SAP ) filters and timers.
Introduction Page 27-2 IPX Routing Overvie w In IPX routing, the switch builds routing tables to keep track of optimal destinations for traf- fic it receives that is destined for remote IPX networks. The switch sends and receives rout- ing messages, or advertisements, to/from other routers in the network.
Introduction Page 27-3 Setting Up IPX Routing on the Switch IPX routing is enabled on a per-port basis by creating a virtual IPX router port for a group/ VLAN. The switch does not do any routing unless the virtual IPX router port has IPX routing enabled (routing is enabled by default).
The IPX Submenu Page 27-4 The IPX Submenu The ipx command in the Networking menu is used to access a submenu containing all the IPX-related commands. For more information about the Networking menu, see Chapter 25, “IP Routing.
Viewing the IPX Routing Table Page 27-5 Vie wing the IPX Routing T able The ipxr command is used to display the IPX Routing Table. The entries in the table show the routes entered by the IPX RIP protocol and the static routes that you may have entered manu- ally.
Viewing the IPX Routing Table Page 27-6 Chg The information in this route has recently been updated, but the new information has not yet been forwarded to neighbor routers. Dir Indicates that this is a local interface (direct route) as opposed to a route to a destination network.
Viewing the IPX Routing Table Page 27-7 Displaying a List of Specific IPX Routes You can limit the number of routes that are displayed by the ipxr command by using an extra argument along with the command. To find out if a route to a particular destination network is known, simply include the network number on the command line.
Viewing IPX Statistics Page 27-8 Vie wing IPX Statistics The ipxs command is used to display data on IPX statistics and errors. To display information about IPX statistics and errors, enter the follow.
Viewing IPX Statistics Page 27-9 IPX Output Statistics pkts sent: The number of packets forwarded (not including fast path routed packets). pkts generated locally: The number of packets forwarded that were generated by local IPX applications (RIP and SAP).
Viewing the IPX SAP Bindery Page 27-10 Vie wing the IPX SAP Bindery The ipxsap command is used to display a listing of the servers in the SAP Bindery, sorted by server name.
Viewing the IPX SAP Bindery Page 27-11 U sing IPXSAP with Fr ame Relay or ISDN Boards The following additional column heading appears in the ipxsap display when a Frame Relay or ISDN board is installed in the switch. s/p/vc or P eer ID The Slot, Port and Virtual Connection (i.
Adding an IPX Static Route Page 27-12 A dding an IPX Static Route The aipxsr command is used to add IPX static routes to the switch’s IPX Routing Table.
Removing an IPX Static Route Page 27-13 Remo ving an IPX Static Route The ripxsr command is used to remove IPX static routes from the switch’s IPX Routing Table. Follow the steps below to remove an IPX static route. 1. Enter ripxsr. A screen similar to the following displays: Do you want to see the current route table? (y or n) (y) : y 2.
Turning the IPX Router Complex On and Off Page 27-14 T urning the IPX Router Complex On and Off The ipxoff command is used to turn off the IPX Router Complex, which disables IPX routing on the switch. To turn off IPX routing, enter the following command: ipxoff A screen similar to the following displays: IPX turned off.
Flushing the IPX RIP/SAP Tables Page 27-15 Flushing the IPX RIP/SAP T ables The ipxflush command is used to flush the IPX RIP Routing and SAP Bindery Tables.
Using the IPXPING Command Page 27-16 U sing the IPXPING Command The ipxping command is used to test the reachability of certain types of IPX nodes. The soft- ware supports two different types of IPX pings: • Novell-defined, which can test the reachability of NetWare servers currently running the NetWare Loadable Module called IPXRTR.
Using the IPXPING Command Page 27-17 5. The following prompt displays: Timeout (1) : Enter the number of seconds to wait for a response. The default timeout is 1. 6. The following prompt displays: Type (n for Novell, x for Xylan) (n) : Enter the type of IPX ping to be issued.
Configuring IPX RIP/SAP Filtering Page 27-18 Configuring IPX RIP/SAP Filtering The ipxfilter command is used to add or delete an IPX RIP or SAP Output or Input filter. The IPX RIP/SAP Filtering feature give you a means of controlling the operation of the IPX RIP/ SAP protocols.
Configuring IPX RIP/SAP Filtering Page 27-19 Adding a “Global” IPX RIP/SAP Filter Follow the steps below to add a “global” IPX RIP or SAP filter.
Configuring IPX RIP/SAP Filtering Page 27-20 8. The following prompt displays: SAP service type (default: all services) : Enter the SAP service type (in hexadecimal format) as defined by NetWare (or press <Enter> to use the default of all services).
Configuring IPX RIP/SAP Filtering Page 27-21 7. The following prompt displays: IPX node mask (default: all F's) : Enter the IPX node mask (in hexadecimal format) to be used (or just press <Enter> to use the default mask of all F's). If you selected the default of “all nodes” in the previous step, this step is skipped.
Configuring IPX RIP/SAP Filtering Page 27-22 Deleting an IPX RIP/SAP Filter Follow the steps below to delete an existing IPX RIP or SAP filter. 1. Enter ipxfilter . A screen similar to the following displays: Selecting global IPX filter: Add or delete entry {add(a), delete(d)} (a) : Enter d to select to delete a filter.
Configuring IPX RIP/SAP Filtering Page 27-23 Displaying IPX RIP/SAP Filter s The ipxf command is used to display a list of all existing IPX RIP and SAP filters. See Adding a “Global” IPX RIP/SAP Filter on page 27-19 for complete information on creating these filters.
Configuring IPX RIP/SAP Filtering Page 27-24 GP:VL (s/p/vc) or (P eer ID) The first number ( GP ) is the Group associated with this entry. The second number ( VL ) is the VLAN associated with this entry. When a filter applies to all interfaces, this field will say “global.
Configuring IPX RIP/SAP Filtering Page 27-25 As another example, to display a list of all global RIP Input filters, you would enter: ipxf ri global A screen similar to the following displays: Displayi.
Configuring IPX Serialization Packet Filtering Page 27-26 Configuring IPX Serialization P acket Filtering The ipxserialf command is used to enable and disable IPX Serialization Packet filtering on any or all WAN routing services.
Configuring IPX Serialization Packet Filtering Page 27-27 5. Filtering will then become active. A message will appear indicating that IPX Serialization Filtering is enabled, either on all WAN routing .
Configuring IPX Watchdog Spoofing Page 27-28 Configuring IPX W atchdog Spoofing The ipxspoof command is used to enable and disable IPX Watchdog Spoofing on any or all WAN routing services.
Configuring IPX Watchdog Spoofing Page 27-29 This example prompt asks if you want to enable spoofing on all WAN routing services. If you had entered a specific Group number, the prompt would refer to that particular Group. Enter y to enable IPX Watchdog Spoofing.
Configuring SPX Keepalive Spoofing Page 27-30 Configuring SPX K eepalive Spoofing The spxspoof command is used to enable and disable SPX Keepalive Spoofing on any or all WAN routing services.
Configuring SPX Keepalive Spoofing Page 27-31 Enter y to proceed to enable spoofing. 4. The following prompt displays: Enable SPX Spoofing on all WAN routing services? (y or n) (n) : y This prompt requires you to verify that you want to enable spoofing in order to avoid the situation of accidental spoofing of SPX packets.
Controlling IPX Type 20 Packet Forwarding Page 27-32 Contr olling IPX Type 20 P acket F orw arding The ipxtype20 command is used to control the forwarding of IPX Type 20 packets.
Configuring NetWare to Minimize WAN Connections Page 27-33 Configuring N etW ar e to Minimize W AN Connections If you have access to NetWare’s control parameters, you can “fine-tune” your network to minimize traffic on WAN links such as ISDN connections or Frame Relay lines.
Configuring NetWare to Minimize WAN Connections Page 27-34 6. Novell has developed a workaround that can be used to disable the SPX Watchdog mech- anism. This workaround could be used instead of enabling the SPX Spoofing feature on your switch. SPWXDOG.
Configuring RIP and SAP Timers Page 27-35 Configuring RIP and SAP Timer s The standard time between broadcasts of RIP and SAP messages is 60 seconds. This default may be modified in order to alleviate network congestion or facilitate the discovery of network resources.
Configuring RIP and SAP Timers Page 27-36 Viewing RIP and SAP Timer s To view the RIP and SAP timers that have been configured through the ipxtimer command, enter the following command: ipxt A screen .
Configuring Extended RIP and SAP Packets Page 27-37 Configuring Extended RIP and SAP P ackets Larger RIP and SAP packets may be transmitted so that congestion in the network is reduced. Other switches and routers in the network must support larger packet size if this feature is configured on the switch.
Configuring an IPX Default Route Page 27-38 Configuring an IPX Default Route A default IPX route may be configured for packets destined for networks unknown to the switch. If RIP messages are disabled, packets can still be forwarded to a router that knows where to send them.
Page 28-1 28 Managing W AN Switching Modules Intr oduction The Omni Switch/Router WAN Switching Modules (WSXs) are a family of modules that enable the creation of WANs by providing connectivity between geographically-distanced LANs.
Introduction Page 28-2 Type of Service (T oS) The Type of Service (ToS) settings allow you to prioritize voice data and voice signaling data. Since voice data is time critical, and requires steady throughput, it should be given higher priority than other forms of data.
Introduction Page 28-3 If you feel that changing the default values is imperative to the working of the network, the following table is provided to give the hexadecimal values for various settings: A bit mask is also set with the UI in hexadecimal form.
Introduction Page 28-4 T oS and QoS Interaction On the Omni Switch/Router and OmniSwitch, ToS policies may only be configured through WAN commands. The WAN UI/CLI commands allow a higher priority of service for voice and voice signalling data.
Introduction Page 28-5 DTR Dial Backup Currently, a feature is available to use a dynamic ISDN call as a backup WAN connection for a primary WAN connection. The primary WAN connection is a permanent virtual circuit (PVC) with upper layer protocol of Frame Relay or PPP.
Supported Physical Interfaces Page 28-6 Supported Ph ysical Interfaces The WSX family of products support numerous physical interface (port) types. The port types available with the WSX family are: Univ ersal Serial P ort The Universal Serial Port (USP) provides connectivity to legacy synchronous serial port devices.
Supported Protocols Page 28-7 Supported Pr otocols The WAN switching modules support both Frame Relay and synchronous Point-To-Point Protocol (PPP). For ISDN signalling protocols, the modules support D-channel signalling (see Chapter 32, “Managing ISDN Ports.
Application Examples Page 28-8 Software in the switch allows you to configure access rate, clocking and protocol-related parameters. Additional software commands allow you to view status at the WSX board, port, or protocol level.
Application Examples Page 28-9 Combined Fr ame Relay with ISDN Backup In a typical configuration, the WSX occupies either a slot in a switch chassis or a submodule on an OmniAccess 512. Because it is compatible with Omni Switch/Router any-to-any switching and VLAN architecture, you can switch other topologies in the LAN to Frame Relay or PPP.
Omni Switch/Router WAN Modules Page 28-10 Omni Switch/Router W AN Modules The Omni Switch/Router currently supports four Wide Area Network modules: • WSX-S-2W Provides two serial ports that support the frame relay or PPP protocol. • WSX-SC Provides 4 or 8 serial ports that support the frame relay or PPP protocol.
Cable Interfaces for Universal Serial Ports Page 28-11 Cable Interfaces for U niver sal Serial P orts The WSX automatically senses the cable type that you plug into one of its Universal Serial Ports. It can sense whether the cable type is DCE or DTE and whether it is one of the following interfaces: • RS-232 • RS-449 • RS-530 • V.
Data Compression Page 28-12 Data Compr ession Data compression allows you to get more data through the Frame Relay pipeline, further enhancing cost benefits.
Loopback Detection Page 28-13 Loopback Detection Loopback Detection is a common method for Carrier Service Providers to test clients’ circuits in the event of suspected line transmission problems. For both Frame Relay and PPP, loop- back detection involves periodically transmitting a message and looking for that message to be received.
The WAN Port Software Menu Page 28-14 The W AN P ort Softwar e Menu User interface commands for the WSX board are on a separate menu that is accessed through the wan command.
The WAN Port Software Menu Page 28-15 Serial P ort Example In this example, port 1 on slot 3 is a serial port, using Frame-Relay. To modify serial port 3/1, enter: wpm 3/1 A screen similar to following displays: 1) Admin Status .......................
The WAN Port Software Menu Page 28-16 If the interface was using PPP, the following screen would display: 1) Admin Status ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS .............
The WAN Port Software Menu Page 28-17 Clocking This field sets the type of clocking used to clock transmit and receive data on the serial port. If the clock goes out-of-phase, you will receive errors. Note The clocking value is only relevant if the port is a physical DCE port (i.
The WAN Port Software Menu Page 28-18 Split Clocking Split clocking, which is also known as “loop timing,” uses an additional control signal ( TXCE ) to keep the submodule and external DTE clocking synchronized. In split clocking, the external DTE takes the incoming transmit clock from the submodule and loops it back to TXCE.
The WAN Port Software Menu Page 28-19 TOS for V oice Signaling Data Set the priority for voice signaling data streams. The value must be entered in hexadecimal format translated from binary, and can use either IP Precedence or Differentiated Services Code Point (DSCP).
The WAN Port Software Menu Page 28-20 Loopback Timeout Sets the transition time between proprietary messages sent over the link. These messages are analyzed to determine whether the link is in a loopback state. This only displays if the port is using Frame Relay as its encapsulation type.
The WAN Port Software Menu Page 28-21 ISDN-BRI P ort Example In this example: port 2 on slot 3 is an ISDN-BRI port. To modify ISDN-BRI port 2/2, enter: wpm 3/2 A screen similar to following displays: 1) Admin Status ...................................
The WAN Port Software Menu Page 28-22 Speed in BPS This option specifies the access rate for the Frame Relay or PPP line to the service provider. This parameter is the speed of the entire connection, not an individual virtual circuit. For example, if you have a 56 kbps line to your service provider, this field should be set to 56000.
The WAN Port Software Menu Page 28-23 You can set up the external DCE this way by configuring its DTE, or dataport, configura- tion options. Set the “Transmit Clock Source” to “External.
The WAN Port Software Menu Page 28-24 TOS for V oice Signaling Data Set the priority for voice signaling data streams. The value must be entered in hexadecimal format translated from binary, and can use either IP Precedence or Differentiated Services Code Point (DSCP).
The WAN Port Software Menu Page 28-25 If the interface was using PPP, the following screen would display: 1) Admin Status ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS .............
The WAN Port Software Menu Page 28-26 T1/E1 Starting Time Slot This field specifies the first time slot number to use on a T1 or E1 port. For a full T1 or E1 connection, specify time slot 1. For a fractional T1 or E1 connection, set this field to the starting time slot number as specified by your service provider.
The WAN Port Software Menu Page 28-27 KeepAliv e Timeout The number of 100 millisecond increments between generated echo message requests. This only displays if the port is using PPP as its encapsulation type. The valid range is 0-255. Loopback Timeout Sets the transition time between proprietary messages sent over the link.
The WAN Port Software Menu Page 28-28 Viewing P arameter s for all P orts in a Single Submodule To view port parameters for all ports on a particular submodule , enter the wpview command, followed by the number of the slot. In the following three examples, the port parameters are displayed for an ISDN-BRI board, a serial board, and a T1 board.
The WAN Port Software Menu Page 28-29 Viewing P ort P arameter s To view port parameters, enter the following command: wpview 3/<port> where 3 is the slot number for WAN uplinks, and <port> is the port number for which you want to view information (either 1 or 2 ).
The WAN Port Software Menu Page 28-30 This next example displays the configuration view screen for a fractional T1 port (port 1) using PPP. To view 3/1, enter: wpview 3/1 or wpv 3/1 A screen similar to following displays: Configuration View for Slot 3, Port 1.
The WAN Port Software Menu Page 28-31 TOS for Voice Data Shows the priority for voice data streams. The value must be entered in hexadecimal format translated from binary, and can use either IP Precedence or Differentiated Services Code Point (DSCP). See Type of Service (ToS) on page 28-2 above for a more detailed explanation of ToS.
The WAN Port Software Menu Page 28-32 Univ ersal Serial P ort Example The following example displays the configuration view screen for a universal serial port (port 2). To view 3/2, enter: wpview 3/2 or wpv 3/2 If the serial port is using Frame-Relay, a screen similar to following displays: Configuration View for Slot 3, Port 2.
The WAN Port Software Menu Page 28-33 Clocking This field displays either External , Internal , or Split . For a more detailed discussion of clocking, see Clocking under Modifying a Port on page 28-14.
The WAN Port Software Menu Page 28-34 DTR Pulse Width A Data Terminal Ready (DTR) Pulse is sent at the hardware level to determine a port is still synchronized with its far end connection. The Pulse Width is the number of 100 milli- second increments that the pulse lasts.
The WAN Port Software Menu Page 28-35 ISDN-BRI P ort Example The following example displays the configuration view screen for an ISDN-BRI port (port 2). To view 3/2, enter: wpview 3/2 or wpv 3/2 A screen similar to following displays: Configuration View for Slot 3, Port 2.
The WAN Port Software Menu Page 28-36 TOS for Voice Data Shows the priority for voice data streams. The value must be entered in hexadecimal format translated from binary, and can use either IP Precedence or Differentiated Services Code Point (DSCP). See Type of Service (ToS) on page 28-2 above for a more detailed explanation of ToS.
The WAN Port Software Menu Page 28-37 Deleting P orts The wpdelete command allows you to delete configuration information for a WSX port. When you delete a this information, all WAN configuration parameters for the selected port revert back to default settings.
The WAN Port Software Menu Page 28-38 Obtaining Status and Statistical Information You can obtain general and detailed WAN port statistical information on all WSX boards in the switch, a single WSX board, individual ports, and Frame Relay and PPP protocols.
The WAN Port Software Menu Page 28-39 Intf Type This column indicates the physical cable type connected to this port. This cable type is automatically sensed by the WSX hardware. This column indicates the cable type and whether it is DCE or DTE . The following values may appear in this column: • V35DTE (V.
The WAN Port Software Menu Page 28-40 Speed BPS This column indicates the speed, or access rate, between the WSX serial port and DSU or other physical DTE device. The speed is expressed in bits per second (bps). This speed is the total bandwidth available on the line connected to this port.
The WAN Port Software Menu Page 28-41 8-P ort WSX Board Ex ample In this example, the board in slot 5 is an 8-port WSX board. To view the status of slot 5, enter: wpstatus 5 or wps 5 This command disp.
The WAN Port Software Menu Page 28-42 Field Descriptions The following section explains the fields and their corresponding values. PT The port number on the WSX board for which statistics are displayed. Admin/Oper Status , Int Type , Speed Bps These columns are described in the section, Obtaining Information on All Boards in a Switch on page 28-38.
The WAN Port Software Menu Page 28-43 Frame Relay Ex ample In the following example, port 1 on slot 4 is configured for Frame Relay. To obtain status information for this port, enter: wpstatus 4/1 A screen similar to the following will be displayed: This command displays three (3) layers of information.
The WAN Port Software Menu Page 28-44 PPP Example In the following example, port 1 on slot 4 is configured for Point-To-Point Protocol (PPP). To obtain status information for this port, enter: wpstatus 5/1 A screen similar to the following will display: /Interface/WAN % wps 5/1 WAN Port Status for slot 5, port 1: Administrative/Operation Status: .
The WAN Port Software Menu Page 28-45 ♦ Note ♦ The section devoted to compressed data traffic statistics will be displayed only if the port has been configured for STAC-LZS compression. For detailed descriptions of the fields, refer to Chapter 30, “Point-to-Point Protocol.
The WAN Port Software Menu Page 28-46.
Page 29-1 29 Managing Fr ame Relay The WAN Switching Module ( WSX ) family supports Frame Relay on universal serial, T1 or E1 ports. Management, data handling, compression, and multi-protocol encapsulation are compatible with current Frame Relay standards, such as RFC 1490 and FRF.
Page 29-2 The WSX supports automatic detection of cable types attached to universal serial ports. It also supports three types of DLCMI management: LMI Rev.
Page 29-3 Back-to-Back Fr ame Relay Configurations Frame Relay switching modules may be connected “back-to-back” without an intervening Frame Relay network or switch. Such connections are made by using private leased lines, such as T1 lines, instead of public Frame Relay networks usually over large geographic distances.
Universal Serial Port Cable Interfaces Page 29-4 U niver sal Serial P ort Cable Interfaces The WSX automatically senses the cable type that you plug into one of its universal serial ports. It can sense whether the cable type is DCE or DTE and whether it is one of the follow- ing interfaces: • RS-232 • RS-449 • RS-530 • V.
Compression Page 29-5 Compr ession Data compression allows you to get more data through the Frame Relay pipeline, further enhancing cost benefits. A typical data compression ratio on the WSX board at the hardware level is 4:1.
Virtual Circuits and DLCIs Page 29-6 Virtual Cir cuits and DLCIs The WSX supports Permanent Virtual Circuits ( PVCs ), but not Switched Virtual Circuits ( SVCs ). Most service carriers do not currently offer SVCs . PVCs are either static (configured) or dynamic (learned).
WSX Self-Configuration and Virtual Circuits Page 29-7 W SX Self-Configuration and Virtual Cir cuits The following diagram summarizes the self-configuration features of the WSX . This example assumes no configuration parameters are entered for the WSX .
Congestion Control Page 29-8 Congestion Contr ol Use of Frame Relay lines tends to be “bursty,” with heavy use at times and light use at others. During heavy periods of congestion, data may be discarded.
Congestion Control Page 29-9 Discard Eligibility (DE) Flag The Frame Relay network keeps track of data that is eligible for discard by using a single bit within each frame. When the data rate exceeds the CIR, frames are tagged (i.e., the DE bit is set to 1).
Congestion Control Page 29-10 Frames are shown as broken lines below the Access Rate line. The space between frames indicates the delay between the transmission of each frame. For each second, frames sent within the white zone below the diagonal Access Rate line get through.
Congestion Control Page 29-11 Noti fication By BECN Each data link header contains a congestion control flag called BECN (Backwards Explicit Congestion Notification), which is usually pronounced “beckon.” Normally this flag is turned off. As with other WAN packet-based networks, frames in Frame Relay may build up in queues at certain points.
Congestion Control Page 29-12 Noti fication By FECN Frame Relay headers also contain a congestion control bit called FECN (Forwards Explicit Congestion Notification), which is usually pronounced “Feckon.” Like BECN , the FECN bit also notifies a WSX or Bridge/Router of congestions problems.
Frame Formats Supported Page 29-13 Fr ame Formats Supported Frames coming in from the Frame Relay network are not translated, but they are manipulated to be compatible for transport over the switch’s VBUS . Incoming frames must contain RFC 1490 headers.
Bridging Services Page 29-14 Bridging Services All Frame Relay Virtual Circuits (VCs) belong to a service, whether it be a Bridge, Router, or Trunk service. By default, a virtual circuit belongs to a bridge service. No configuration is necessary for a VC to support bridging on Group 1.
Frame Relay IP Routing Page 29-15 Fr ame Relay IP Routing Frame Relay routing is different than standard LAN IP Routing. In normal LAN IP Routing MAC addresses are used as source and destination addresses. In Frame Relay IP Routing, no MAC addresses are included in a routed frame.
Frame Relay IP Routing Page 29-16 An InARP message is sent between the two routers indicating their IP addresses and associ- ated VC. Once they know each other’s IP address and the DLCI of the VC on each end of the link (the same VC may have a different DLCIs on each end), then they can begin normal rout- ing of RIP frames, etc.
Frame Relay IP Routing Page 29-17 If an additional Router and Subnet were added to the network and a new VC was added to connect the new location, then much of the WAN routing load would fall on the WSX attached to Subnet 1.1.1.x. Adding A New Router Raises New Questions The new WSX attached to Subnet 4.
Frame Relay IPX Routing Page 29-18 Fr ame Relay IPX Routing Frame Relay IPX and IP routing differ in the way they determine the address of a router at each end of a virtual circuit. Instead of using Inverse ARP , IPX uses a process called “glean- ing” to determine routing information.
Trunking Page 29-19 T runking A trunking service must be set up for each virtual circuit that will support trunking. When trunking is set up, you specify the slot, port, DLCI , and Groups that are going to be trunked over the virtual circuit. The illustration below shows a sample trunking configuration.
Frame Relay Fragmentation Interleaving Page 29-20 Fr ame Relay Fragmentation Interleaving The fragmentation interleaving feature allows for the transmission of higher priority traffic to be expedited by setting a maximum frame size.
The Frame Relay Software Menu Page 29-21 The Fr ame Relay Softwar e Menu User interface commands for Frame Relay are on a separate menu that you can access through the fr command.
Setting Configuration Parameters Page 29-22 Setting Configur ation P arameter s When you plug in a WSX board it is automatically configured with default settings. The WSX board will default the WAN port protocol to frame relay for WSX serial ports, T1 and E1 ports.
Setting Configuration Parameters Page 29-23 A screen similar to the following displays: Modifying Frame Relay port for Slot 2, Port 1. 1) Description....................................…………………………....... = {Enter Up to 30 Characters} 2) Administrative Status …………………………………….
Setting Configuration Parameters Page 29-24 You make changes by entering the line number for the option you want to change, an equal sign (=), and then the value for the new parameter. When you are done entering all new values, type save at the colon prompt (:) and all new parameters will be saved.
Setting Configuration Parameters Page 29-25 31) LMI Procedur e Type This field specifies the Local Management Interface ( LMI ) procedure type for this Frame Relay port.
Setting Configuration Parameters Page 29-26 6) Error Thr eshold N392/nN2 The number of DLCMI protocol errors that will be tolerated before determining the Frame Relay line is down and all associated virtual circuits are inactive.
Setting Configuration Parameters Page 29-27 10) Default Routing Group The default Group for bridging any virtual circuits (user-configured or learned from the Frame Relay network) that are not specifically assigned to a Routing service.
Setting Configuration Parameters Page 29-28 13) Default Compression PRetry Count This option sets the total number of compression negotiation messages that will be sent before giving up and not running compression. You enter the time between these retries in the Default Compression PRetry Time field.
Setting Configuration Parameters Page 29-29 Modifying a Virtual Cir cuit To modify a virtual circuit, enter the following command: frmodify <slot>/<port>/<DLCI> where <slot> is.
Setting Configuration Parameters Page 29-30 Committed Information Rate (CIR) This field sets the Committed Information Rate (CIR) for this virtual circuit. See Congestion Control on page 29-8 for further information on the CIR. ♦ Important Note ♦ The CIR that you enter must match that used by your service provider.
Setting Configuration Parameters Page 29-31 Compression PRetry Time This option sets the number of seconds between compression negotiation messages on this virtual circuit. If compression negotiation is enabled, the WSX will send compression negotia- tion messages as many times as you indicate in the Compression PRetry Count.
Adding a Virtual Circuit Page 29-32 A dding a Virtual Circuit Data virtual circuits and their DLCI s are normally learned through status messages with the Frame Relay network. However, it may be convenient to pre-configure these virtual circuits before connecting to a live network.
Viewing Configuration Parameters for the WSX Page 29-33 Vie wing Configuration P ar ameter s for the WSX You can view all current parameters for a WSX port or an individual virtual circuit using the frview command.
Viewing Configuration Parameters for the WSX Page 29-34 Viewing P ort P arameter s To view port parameters, enter the following command frview <slot>/<port> where <slot> is the slot number where the WSX board is located, and <port> is the port number on the WSX board on which you want to view information.
Viewing Configuration Parameters for the WSX Page 29-35 Viewing Virtual Cir cuit P arameters To view virtual circuit parameters, enter the following command frview <slot>/<port>/<DLCI&g.
Deleting Ports and Virtual Circuits Page 29-36 Deleting P orts and Virtual Circuits You can delete a WSX port or virtual circuit. When you delete a port or virtual circuit all configuration parameters revert back to default settings.
Deleting Ports and Virtual Circuits Page 29-37 Deleting a P ort and Its Virtual Circuits You can delete a port as well as all of its associated virtual circuits. Deleting a port means that all configuration parameters on the port and all learned virtual circuits will revert back to default settings.
Obtaining Status and Statistical Information Page 29-38 Obtaining Status and Statistical Information You can obtain general and detailed Frame Relay statistical information on all WSX boards in the switch, a single WSX board, individual ports, and individual virtual circuits.
Obtaining Status and Statistical Information Page 29-39 Intf Type This column indicates the physical cable type connected to this port. This cable type is auto- matically sensed by the WSX hardware. This column indicates the cable type and whether it is DCE or DTE .
Obtaining Status and Statistical Information Page 29-40 Clocking This field indicates the type of clocking used to clock transmit and receive data in and out of the serial port.
Obtaining Status and Statistical Information Page 29-41 VCs Activ e/Inactive Each port will have one or more associated virtual circuits. This column tells you the current status of Data virtual circuits. These counts do not apply to management virtual circuits.
Obtaining Status and Statistical Information Page 29-42 Information on the P orts for One WSX Boar d To obtain status information on a single WSX board, you enter the frstatus command along with the slot number for the WSX board, as follows: frstatus <slot> where <slot> is the slot number where the WSX board is installed.
Obtaining Status and Statistical Information Page 29-43 Information on One P ort To obtain status information on a single WSX port, you enter the frstatus command along with the slot number for the WS.
Obtaining Status and Statistical Information Page 29-44 This command displays three (4) layers of information. The top section provides information on the physical interface. The middle section provides information on the logical, or Frame Relay, interface.
Obtaining Status and Statistical Information Page 29-45 Phy sical Layer Information The statistics shown in this section are taken at the physical, or serial, interface level. Administrative/Operational Status This field shows the Administrative and Operational Status of this WSX port.
Obtaining Status and Statistical Information Page 29-46 Control Signal This table (which displays only for serial ports, not T1 or E1 ports) lists two or more control signals along with their current state. If a V.35 , RS-232 , RS-530 , or RS-449 cable is attached then this table lists the following signals: • DTR (Data Terminal Ready.
Obtaining Status and Statistical Information Page 29-47 Frame Relay Information The statistics shown in the section are gathered at the Frame Relay protocol level. Octets The total octets, or bytes, received (first row) and sent (second row) on this port.
Obtaining Status and Statistical Information Page 29-48 Last Error Type The last type of Frame Relay DLCMI protocol error received on this port. The following list describes the error types displayed: Unknown Error An error occurred but it can not be classified into one of the stan- dard Frame Relay error types.
Obtaining Status and Statistical Information Page 29-49 DLCI Lay er Information The information in this section of the display provides statistics on virtual circuits. Each row in this table corresponds to one virtual circuit. DLCI Num The DLCI number assigned to this virtual circuit.
Obtaining Status and Statistical Information Page 29-50 Fragmentation Information The information in this section of the display provides statistics on fragmentation. Each row in this table corresponds to one virtual circuit. DCLI The virtual circuit that the fragmentation statistics apply to.
Obtaining Status and Statistical Information Page 29-51 Information on One Virtual Circuit To obtain status information on a single virtual circuit, you enter the frstatus command along with the slot .
Obtaining Status and Statistical Information Page 29-52 The Frame Relay Fragmentation Information gives a break down of the fragmented traffic received and sent by this virtual circuit, with indications if fragmentation is currently enabled and the maximum frame size.
Obtaining Status and Statistical Information Page 29-53 FECN Bit This value indicates the total number of frames received from the network indicating forward congestion. This occurs when the Frame Relay network sets the frame’s Forward Discard Eligibility ( FECN ) flag.
Resetting Statistics Counters Page 29-54 Resetting Statistics Counter s You can reset the statistics counters for a single WSX board, a WSX port, or a specific DLCI . The statistics that are cleared on those that are displayed through the frstatus commands.
Managing Frame Relay Services Page 29-55 Managing Fr ame Relay Services By default, all virtual circuits on a WSX port have a Bridging service and are assigned to Group 1. The frmodify command allows you to change this default bridging service to another Group and to set up a default routing service for the port.
Managing Frame Relay Services Page 29-56 An overview of each type of service and how each operates in a Frame Relay environment can be found earlier in this chapter in the following sections: • Bridging See Bridging Services on page 29-14. • Routing See Frame Relay IP Routing on page 29-15 and Frame Relay IPX Routing on page 29-18.
Configuring a Bridging Service Page 29-57 Configuring a Bridging Service Frame Relay traffic is automatically bridged for Group 1 in a switch. You can alter this default through two different commands: frmodify and cas .
Configuring a Bridging Service Page 29-58 5. You need to specify the DLCI for the virtual circuit to include in this bridging service. Only one virtual circuit may be specified for each bridging service. There is a one-to-one mapping between the Group and the virtual circuit.
Configuring a WAN Routing Service Page 29-59 Configuring a W AN Routing Service There are two main steps to configuring WAN routing for frame relay: 1. Enable and configure routing for a specific WAN Routing group with the crgp command. (Frame Relay Groups are different from other Groups as far as router configurations are concerned.
Configuring a WAN Routing Service Page 29-60 Step 2. Set Up a Frame Relay Routing Service You create a Frame Relay routing service using the cas command.
Configuring a WAN Routing Service Page 29-61 6. Specify the Group number to which this router port belongs. Enter a 5, an equal sign (=), and the Group number. The example below includes Group 4 in the routing service: 5=4 Press <Enter> . You must have previously configured this Group as a Frame Relay Routing Group through the crgp command.
Configuring a Trunking Service Page 29-62 Configuring a T runking Service To configure a Frame Relay Trunking service, you must use the cas command. Perform the following steps: 1.
Configuring a Trunking Service Page 29-63 5. You need to specify the DLCI for virtual circuit that will be used to trunk traffic over the Frame Relay network.
Viewing Frame Relay Services Page 29-64 Vie wing Frame Relay Services You can view all Frame Relay services for an entire switch, a single WSX board, or a single WSX port.
Modifying a Frame Relay Service Page 29-65 Vport The virtual port associated with this service. For bridging services, there is a one-to-one mapping between a virtual port and a virtual circuit. For routing services, multiple virtual circuits may map to a single virtual port.
Deleting a Frame Relay Service Page 29-66 Deleting a Fr ame Relay Service You can delete a Frame Relay service using the das command as follows: 1. Enter das followed by the slot, port and service number for the Frame Relay service that you want to delete.
Page 30-1 30 P oint-to-P oint Pr otocol The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links.
Page 30-2 Data Compression RFC 1974 specifies the use of STAC-LZS compression with PPP. Data compression allows the payload of a PPP packet, including the protocol ID, to be compressed, saving valuable bandwidth.
Page 30-3 Multilink Modes of Operation Multilink PPP supports combinations of both permanent and switched connections. This results in two possible modes of operation: • permanent connection only .
Page 30-4 On the receiving side, as low priority frames are being received they will be put into the MLPPP reassembly queue, as supported by the existing software.
Page 30-5 The configuration of a T1/E1 interface is described in Chapter 33 titled “Managing T1 and E1 Ports.” The configuration of a universal serial port (USP) on a WSX-S board is described in Chapter 28 titled “Managing WAN Switching Modules.
The PPP Submenu Page 30-6 The PPP Submenu The WAN menu contains a submenu, named PPP , containing commands specific to the Point- to Point-Protocol (PPP).
Setting Global PPP Parameters Page 30-7 Setting Global PPP P arameter s The pppglobal command is used to set global configuration parameters that are used by the PPP protocol. These parameters are termed “global” because they are the default settings used by the switch to establish connections with incoming calls.
Setting Global PPP Parameters Page 30-8 Default Compression T ype Specifies the type of compression that is to be expected on incoming calls. The options are None and STAC-LZS . If you set this parameter to None and your callers are using compression, the caller’s connection request may be refused.
Adding a PPP Entity Page 30-9 A dding a PPP Entity The pppadd command is used to add a PPP Entity configuration record. The PPP Entities you create are identified by numbers called Peer IDs.
Adding a PPP Entity Page 30-10 A screen similar to the following will display: Adding PPP configuration record for Peer ID: 1 Enter PPP parameters: 1) Description : {Enter text up to 30 characters} 2) Administrative Status . . . . . . . . . . . . . . .
Adding a PPP Entity Page 30-11 Note You can add the link needed for a PPP Entity later if you decide not to do so now. The automatic execution of the linkadd command is done here only as a conve- nience to you. The fields on the pppadd configuration screen have the following meanings: Description A textual description for this PPP Entity.
Adding a PPP Entity Page 30-12 Enabling Routing expands the menu with the following suboptions: 6) Routing Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 {1-65535 or 0 if no Routing} 60) IP Config Admin Status . . . . .
Adding a PPP Entity Page 30-13 User ID sent to remote for Authentication Used to specify the User ID to be sent to the remote end during PAP or CHAP authentica- tion. This parameter is used only for outgoing calls. Incoming calls use the global defaults (see Setting Global PPP Parameters on page 30-7 for details).
Adding a PPP Entity Page 30-14 Limit Maximum number of fragments to 16 This flag is set to make the interface compatible with Cisco products. When set to Yes , a PPP packet is never fragmented into more than 16 smaller packets.
Modifying a PPP Entity Page 30-15 Modi fying a PPP Entity The pppmodify command is used to modify the parameters of an existing PPP Entity. To modify a specific PPP Entity, for example Peer ID 1, ente.
Viewing PPP Entity Configurations Page 30-16 Vie wing PPP Entity Configurations The pppview command is used to view the configuration parameters of existing PPP Entities.
Viewing PPP Entity Configurations Page 30-17 Routing Group Indicates the VLAN Group to be used for PPP Routing of the IP and IPX protocols. A value of zero ( 0 ) indicates that this PPP Entity will not perform a routing service and will discard all routed format packets received or transmitted.
Displaying PPP Entity Status Page 30-18 Displaying PPP Entity Status The pppstatus command is used to view the operational status of one or more PPP Entities.
Displaying PPP Entity Status Page 30-19 BCP Oper State Indicates the operational state of the Bridging Control Protocol option. Open means that the bridging operation is active. Closed means that the bridging operation has not yet reached the open state.
Displaying PPP Entity Status Page 30-20 IPCP Pkts IN/OUT The total number of IP Control Protocol (IPCP) packets received ( In ) and transmitted ( Out ) on this PPP connection. IPCP Pkts IN/OUT The total number of IP Control Protocol (IPCP) packets received ( In ) and transmitted ( Out ) on this PPP connection.
Deleting a PPP Entity Page 30-21 Deleting a PPP Entity The pppdelete command is used to delete an existing PPP Entity. 1. Before you can delete a PPP Entity, you must first delete all the links associated with it. You do so using the linkdelete command (see Chapter 31 titled “WAN Links”).
Deleting a PPP Entity Page 30-22.
Page 31-1 31 W AN Links Intr oduction This chapter describes the procedures for configuring a “WAN link” between an already created PPP Entity (see Chapter 30, Point-to-Point Protocol ) and the physical interface that will be used to carry PPP traffic.
The Link Submenu Page 31-2 The Link Submenu The WAN menu contains a submenu named link which contains commands for creating the WAN Links needed to support the Point-to-Point Protocol (PPP) over various hardware inter- faces. WAN links can either be “fixed” (i.
Adding a WAN Link Page 31-3 A dding a W AN Link The linkadd command is used to add link configuration records, or “WAN Links” to the switch. This command defaults to a WSX physical port (serial or Fractional T1/E1).
Adding a WAN Link Page 31-4 Administr ative Status Sets the Administrative Status of this WAN Link. The options are “ Enabled, ” which will enabled this link and “ Disabled, ” which will disable the link but not delete it. Link Type Specifies the type of physical connection that will carry the link.
Adding a WAN Link Page 31-5 2. You must now change the Link Type to ISDN. To do so, enter the following commands: : 3=I : ? A screen similar to the following displays: 1) Link Description : {Enter text up to 31 characters} 2) Link Administrative Status .
Adding a WAN Link Page 31-6 A screen similar to the following displays: Modify ISDN call record configuration. Peer ID: 1 Link Index: 1 Type: ISDN Call Slot: 4 Port: 2 1) Link Description : Link Entry: 1, Peer ID: 1 {Enter text up to 30 characters} 2) Link Administrative Status .
Adding a WAN Link Page 31-7 Minimum Call Duration The minimum duration of a call, in seconds, starting from the time the call is connected until the call is disconnected. If you enable this field by entering a nonzero value, the Inactivity Timer will be disabled until the time set in the Minimum Call Duration field has passed.
Adding a WAN Link Page 31-8 4. You must now enter a value in at least the Remote Phone Number field under Outgoing Calls . If you do not make an entry in this field, an error will be returned by the system when you attempt to save and exit the screen.
Modifying a WAN Link Page 31-9 Modi fying a W AN Link The linkmodify command is used to modify the parameters of an existing WAN Link. Different parameters will be displayed by the command based on the type of link. The first subhead- ing ( Modifying ISDN Links ) below shows the sequence of screens when modifying a link over a WSX port.
Modifying a WAN Link Page 31-10 2. Make the desired changes to each of the fields on this screen, then enter the save command to implement your changes. The system prompt will then reappear. Modi fying WSX Links 1. To modify a WAN Link, you must enter its Link Index with the command.
Deleting WAN Links Page 31-11 Deleting W AN Links The linkdelete command is used to delete one or more existing WAN Link records. Note Before you can delete a PPP Entity, you must first delete all WAN Links that have been associated with it. See Deleting a PPP Entity in Chapter 30 for complete information.
Viewing WAN Links Page 31-12 Vie wing W AN Links The linkview command is used to view information on existing WAN Link records. Displaying All Existing W AN Links To view information on all existing W.
Viewing WAN Links Page 31-13 Incoming Caller ID The phone number reported by the Caller ID service, if available. P eer Speed The specified calling speed for this link. The options are 56000 and 64000 bits/second. Inactivity Timer Specifies the time period (in seconds) after which the connection will be terminated if it is not carrying useful data.
Viewing WAN Links Page 31-14 Example of W SX Serial or T1/E1 Link An example of a link over a WSX serial or Fractional T1/E1 port would look like this: View ISDN Link configuration. Index: 2 Link Peer ID: 3 Type: WSM port Slot: 5 Port: 2 1) Link Description : Link Entry: 1, Peer ID: 1 {Enter text up to 31 characters} 2) Link Administrative Status .
Displaying Link Status Page 31-15 Displaying Link Status The linkstatus command is used to display the operational status of WAN Links. Displaying Status for All W AN Links To view information on all .
Displaying Link Status Page 31-16 Peer Call Address The number to which this call is connected. Zero (0) means the number is not available. Connection Time The value of “sysUpTime” (the time of day) when the call was connected. Zero (0) means the call is not currently connected.
Displaying Link Status Page 31-17 Refused Calls The number of calls from the Peer ID that were refused, or any reason, since system start-up. Last Setup Time The value of “sysUpTime” (the time of day) when the last call to this peer was started. For ISDN, this will be the time when the setup message was received from or sent to the network.
Displaying Link Status Page 31-18.
Page 32-1 32 Managing ISDN P orts The WAN Switching Module for the Basic Rate Interface (WSX-BRI) supports 1 or 2 Universal Serial Ports (USP) and 1 or 2 ISDN Basic Rate Interfaces (BRI). The USPs can support Frame Relay or Point-to-Point Protocol (PPP).
Page 32-2 “U”, “S/T” , and “R” Interfaces The ISDN specification defines a limited set of user-to-network interfaces, including reference points for the BRI access method.
The ISDN Submenu Page 32-3 The ISDN Submenu The WAN menu contains a submenu, ISDN , containing commands specific to WSX-BRI ISDN ports. To switch to, and to display, the ISDN menu, enter the following.
Modifying an ISDN Configuration Entry Page 32-4 Modi fying an ISDN Configuration Entry The isdnm command is used to modify the parameters for a selected ISDN port. These param- eters are typically provided by the telephone carrier or other service provider at the time the ISDN line is installed.
Deleting an ISDN Configuration Entry Page 32-5 Deleting an ISDN Configur ation Entry The isdnd command is used to delete one or more ISDN configuration entries. Deleting the configuration entry is equivalent to returning the ISDN port to its default settings.
Viewing an ISDN Configuration Entry Page 32-6 Vie wing an ISDN Configuration Entry The isdnv command is used to view the configuration of existing ISDN configuration entries. You can either view a configuration summary for all ISDN ports on a specified slot, or display the configuration for a single ISDN port.
Displaying ISDN Configuration Entry Status Page 32-7 Displaying ISDN Configur ation Entry Status The isdns command is used to view the operational status of existing ISDN configuration entries. You can select to view the status of all ISDN ports, or select to display the status of a single ISDN port.
Displaying ISDN Configuration Entry Status Page 32-8 Displaying Status of a Speci fic ISDN Slot To view status information on all ISDN channels on a specific ISDN slot, for example, slot 4, enter the.
Displaying ISDN Configuration Entry Status Page 32-9 Oper Status Indicates the current call control state for this interface. The possible entries are: Idle means the B Channel is idle: no call or call attempt is in progress. Connecting means a connection attempt (outgoing call) is being made.
Displaying ISDN Configuration Entry Status Page 32-10.
Page 33-1 33 Managing T1 and E1 P orts T1 and E1 ports are supported on a variety of switching modules. In the Omni Switch/Router, T1 and E1 are used as standard WAN access portss.
T1 and E1 Overview Page 33-2 T1 and E1 Ov erview Carrier digital services were designed primarily to support digitized voice over long distances. Digital services are the primary method for carrying voice between two endpoints using two pairs of copper wire.
The T1/E1 Menu Page 33-3 The T1/E1 Menu The commands for configuring and monitoring T1 and E1 ports are contained in the te submenu. This submenu displays as shown below and may be accessed (when in verbose mode) by entering te at a system prompt.
Configuring a T1 Port Page 33-4 Configuring a T1 P ort The temod command configures a T1 port at the physical level and is generic to all such ports regardless of the logical level service, such as circuit emulation, that controls them.
Configuring a T1 Port Page 33-5 If you choose the unframed format, then the framer will not look for Channel Associated Signalling ( CAS ). Data is treated as a data stream. When used in a circuit emulation applica- tion, this option must be chosen when configuring an “unstructured” circuit emulation service.
Configuring a T1 Port Page 33-6 5) Facility Datalink Facility Datalink ( FDL ) gathers performance statistics every second and stores them in the 24- hour local statistical database. It also sends local performance statistics to the remote T1 port depending on the type of FDL chosen and the “role” of the FDL (specified in the next field).
Configuring a T1 Port Page 33-7 8) Loopback Mode The loopback configuration for this port. Loopback configurations describe the relation between the device attached to a T1 port and the framing functionality within the T1 port.
Configuring an E1 Port Page 33-8 Configuring an E1 P ort The temod command configures an E1 port at the physical level and is generic to all such ports regardless of the logical level service, such as circuit emulation, that controls them. You configure the circuit emulation service that controls this port through the cemodify command.
Configuring an E1 Port Page 33-9 2) Frame F ormat Specify the E1 frame format to be used on this port. The choices are as follows: E1 Standard E1 frame format using the framing bits in time slot 0 for framing. E1-CRC E1 frame using framing bits in both time slot 0 and CRC-4 multiframe for fram- ing.
Configuring an E1 Port Page 33-10 6) Tr ansmit Clock Source The source of the transmit clock. Loop timing means the receive clock (recovered from receive data) is used as the transmit clock. Local timing indicates the local clock source (generated from PLL s) is used as the transmit clock.
Viewing T1/E1 Configuration and Alarm Information Page 33-11 Vie wing T1/E1 Configuration and Alarm Information You can view all current parameters and alarms for a T1 or E1 port using the tes command. These parameters will be either the default parameters or parameters you modified through the temod command or network management software.
Viewing T1/E1 Configuration and Alarm Information Page 33-12 LossOfSignal The port has experienced a Loss of Signal ( LOS ), or Loss of Carrier. An LOS event occurs after 175 contiguous pulse positions with no pulses (10 absent pulses on E1 ports). An LOS failure is cleared after the switch observes a single pulse.
Viewing T1/E1 Configuration and Alarm Information Page 33-13 Viewing Information F or a T1 P ort To view T1 port parameters, enter the following command tes <slot>/<port> where <slot> is the slot number where the board is located, and <port> is the T1 port number on the board on which you want to view information.
Viewing T1/E1 Configuration and Alarm Information Page 33-14 Out of Frame Events . The total number of out of frame events that have been detected on this port.
Viewing T1/E1 Configuration and Alarm Information Page 33-15 Viewing Information F or an E1 P ort To view E1 port parameters, enter the following command tes <slot>/<port> where <slot> is the slot number where the board is located, and <port> is the E1 port number on the board for which you want to view information.
Viewing T1/E1 Configuration and Alarm Information Page 33-16 Out of Frame Events . The total number of out of frames events that have been detected on this port. An out of frame event occurs when three consecutive frame alignment signals have been received with an error.
Viewing T1/E1 Local Statistics Page 33-17 Vie wing T1/E1 Local Statistics There are a number of commands available for viewing local T1 and E1 statistics. These commands provide statistics for the past 24 hours, the current 15-minute interval, or the past 96 15-minute intervals.
Viewing T1/E1 Local Statistics Page 33-18 SEFS . Severe Errored Framing Second. A second with one or more out-of-frame errors or an AIS error. LES . Line Errored Seconds. The number of seconds during which one or more Line Code Violation errors have occurred (see also the definition of Line Code Violation below).
Viewing T1/E1 Local Statistics Page 33-19 Viewing Local Historical Statistics The telis command allows you to display historical statistics for the past 96 15-minute inter- vals.
Viewing T1 Remote Statistics Page 33-20 Vie wing T1 Remote Statistics To receive and monitor remote statistics on T1 ports you must enable the Facility Datalink ( FDL ) protocol through the temod command. These statistics will not be available if you do not enable FDL .
Viewing T1 Remote Statistics Page 33-21 Viewing Curr ent Remote Statistics You can view remote statistics for the current 15-minute interval on a single port by entering the following command tercs &l.
Viewing T1 Remote Statistics Page 33-22 Clearing the Framer Statistics for a T1/E1 P ort The tecls command enables you to clear the accumulated physical-layer (Framer) statistics for a T1 or E1 port.
Page 34-1 34 Backup Services Intr oduction Backup Services are intended to be an integral part of a well-designed Wide Area Network (WAN). The purpose of a backup service is to provide an alternate route for data to take in the event of failure of the Primary port or Virtual Circuit.
Backup Services Commands Page 34-2 Backup Services Commands Backup services provides commands to view and configure your backup services. All commands start with “bs” for “Backup Service” followed by the function desired. All backup commands may be typed in full, or a three character abbreviation may be used (e.
Backup Services Commands Page 34-3 Adding a Backup Service With the bsadd command, you can: • Add a backup for a physical port • Back up a frame relay PVC Adding a backup for a Ph ysical P ort To add a backup service for a physical port: 1. Enter the bsadd command with no parameters, followed by <return> .
Backup Services Commands Page 34-4 : 30=2 : 31=1 : 40=5 : ? 1) Description: Backup 1 2) Admin Status { (E)nabled, (D)isabled } : Enabled 3) Primary Type { Physical Port (1), Frame Relay PVC DLCI (2) }.
Backup Services Commands Page 34-5 5) Startup Timer V alue This field sets the time after system startup to wait for the primary entity to come up. If the primary entity fails to come up within the defined time after system startup, the backup entity will be activated.
Backup Services Commands Page 34-6 Backing Up a Frame Relay PVC Adding a backup service for a frame relay PVC is basically the same as for a physical port. The only differences are that you must specify Primary Type as Frame Relay , and you must specify a DLCI number.
Backup Services Commands Page 34-7 : 3=2 1) Description : Backup 2 2) Admin Status { (E)nabled, (D)isabled } : Enabled 3) Primary Type { Physical Port (1), Frame Relay PVC (2) } : Frame Relay PVC 30) .
Backup Services Commands Page 34-8 : 30=3 : 31=3 : 32=32 : 40=1 : ? 1) Description : Backup 2 2) Admin Status { (E)nabled, (D)isabled } : Enabled 3) Primary Type { Physical Port (1), Frame Relay PVC (.
Backup Services Commands Page 34-9 Modi fying a Backup Service With the bsmodify command, you can modify: • A backup for a physical port • A frame relay PVC. Modifying a backup for a Ph ysical P ort To modify a backup service for a physical port: 1.
Backup Services Commands Page 34-10 Modifying a Fr ame Relay PVC Backup Service To modify a backup service for a frame relay PVC: 1. First, enter the bsmodify command, followed by the index of backup .
Backup Services Commands Page 34-11 Viewing Backup Service(s) Configur ations With the bsview command, you can view the configuration of either all backup services, or a single backup service.
Backup Services Commands Page 34-12 Viewing Backup Service Statistics To view the statistics of a back service, enter the bsstatus command in the following manner: bsstatus b<backupIndex> where b<backupIndex> is the service index number assigned to the service when it was created.
Backup Services Commands Page 34-13 Idx . The index number of the backup service. Description . Enter a description of the backup service in this field. Your description may consist of a maximum of 30 ASCII characters. Primary Type . This field shows the type of entity that will be backed up in the case of network failure.
Backup Services Commands Page 34-14.
Page 35-1 35 T r oubleshooting This chapter provides information that will help you troubleshoot Omni Switch/Router hard- ware and software problems. The sections within this chapter describe problems or errors you may encounter during switch hardware and software installation, configuration, or operation.
Detecting Problems Page 35-2 This chapter lists UI error messages. Refer to the appropriate hardware chapters for a complete description of LED states. Refer to NMS online documentation for explanations of NMS error messages. Refer to Chapter 25, “ IP Routing,” for procedures to use the ping command.
Reporting Problems Page 35-3 Reporting Pr oblems In some cases, you will not be able to correct the problem that occurs (for instance, a module failure).
Reporting Problems Page 35-4 Report Softwar e Details When reporting problems you should be ready to report the following software details to Alcatel Technical Support: • Software revision (e.
Understanding Problems Page 35-5 U nderstanding Pr oblems The following self-questions can be used to get a better idea on the nature of the problem: • Has this functionality ever worked? • What c.
Operational Problems Page 35-6 Oper ational Problems The following paragraphs describe operational problems you may encounter. Deadlocked VLAN Occasionally, a VLAN may deadlock. This may be a result of the configuration process you used when you set up the VLANs .
Operational Problems Page 35-7 To determine if this problem has occurred in your setup, you can use the vi command to display information about a specific port.
Operational Problems Page 35-8 Protocol Pr oblems You may notice an abnormal number of errors in a particular protocol. You can view proto- col errors by using the networking commands. Refer to Chapter 25, “IP Routing,” for more information on the networking commands.
Hardware Problems Page 35-9 Har dwar e Problems The following sections describe problems you may encounter with switch hardware. LEDs Do Not Light on All Modules You have turned on the power supply to the switch, but the LEDs on the modules do not light.
Hardware Problems Page 35-10 TEMP LED is Amber If the TEMP LED is amber, the internal temperature of the switch has exceeded the opera- tional limit. Solution Perform the following steps: 1. Turn off the switch and wait until it has completely cooled down.
Error Messages Page 35-11 Err or Messages This section provides error messages that you may encounter in the UI . Under standing Error Messages Error messages reflect hardware or software problems that the switch encountered during initialization, configuration, or operation.
Error Messages Page 35-12 Serial P ort Configuration Err ors Message Corrective Action Problem deleting SLP port xxx , errno= xx Reboot the system, then use the Boot Line configuration to force SLIP down at the boot line (refer to Appendix A “The Boot Line Prompt”).
Error Messages Page 35-13 Chassis Error Messages The slots in the messages within the following table are all zero based. That is, Slot 1 will be displayed as “Slot 0,” Slot 2 will be displayed as “Slot 1,” etc.
Error Messages Page 35-14 Chassis Error Messages T able (Cont.) Message Corrective Action Couldn’t read chassis description, setting default Enter a new chassis description with the syscfg command. cmSavePortInfo( ) successful This message does not indicate an error.
Page 36-1 36 Running Har dw ar e Diagnostics Hardware diagnostics provide you with software tools for diagnosing hardware-related problems on Omni Switch/Router switching modules. These diagnostics allow you to test switching modules off-line during network down time.
Page 36-2 • mvbus Mammoth VBUS Test • pcam Pseudo CAM Test • port Port Traffic Test • stress Port Stress Test (available for Ethernet modules) • submem Submodule Local Memory Test • suni S.
Login to Run Diagnostics Page 36-3 Login to Run Diagnostics You must log in to the diag account to access the hardware diagnostics functionality. The diag user is a superset of the admin user. The diag user can run all hardware diagnostics in addition to all of the capabilities available to the admin user.
Resetting a Switching Module Page 36-4 Resetting a Switching Module The reset command initiates a soft reset on the module in a specified slot. Conceptually, resetting a switching module with this command is similar to switching off power to the module; the module will be in the same state after a reset as it is after a power on.
Temperature Masking Page 36-5 T emperatur e Masking The maskta command provides a way of modifying the behavior of the temperature alarm to mask the effect of the temperature sensor. By masking the temperature alarm bits, you can ensure that the MPX ’s TEMP LED doesn’t signal or that it resets after a specified delay time.
Running Hardware Diagnostics Page 36-6 Running Har dwar e Diagnostics The test command initiates one or more test routines on a switching module that you specify. You can also optionally test all switching modules in one test session. Test status, instructions, and a summary of results are provided as output.
Running Hardware Diagnostics Page 36-7 ilbstress Performs a stress test using the internal loopback at the PHY or framer interface. Packets are generated by the MPX and sent out to the port and returned through an internal loopback within the PHY or framer.
Running Hardware Diagnostics Page 36-8 stress Functional testing of physical ports with continuous full-wire traffic. The data packets are initially generated by the MPX , sent out the physical port, and looped back through external cables or wrap plugs.
Running Hardware Diagnostics Page 36-9 Sample Command Lines There are numerous ways to specify a test session through the test command. The following are some sample command lines along with a description of what they test.
Running Hardware Diagnostics Page 36-10 The table below provides specific cable/plug information for Omni Switch/Router switching modules. Omni Switch/Router P ort T est Wr ap Cable/Plug Requirements Module Type Cable Type GSX-K-FM-2W Port/Stress (Full Duplex) test: Multi-mode fiber optic wrap plug with SC connectors.
Running Hardware Diagnostics Page 36-11 Omni Switch/Router P ort T est Wr ap Cable/Plug Requirements (cont.) Module Type Cable Type WSX-S-2W (no compression) Twisted pair 28GA serial cable with HD50-26 connectors – DCE to DTE. WSX-SC-4W Twisted pair 28GA serial cable with HD50-26 connectors – DCE to DTE.
Running Hardware Diagnostics Page 36-12 Sample T est Session: Ethernet Module Test sessions and results will vary among the various switching modules. This section shows the output from a test session on an ESX-C-12 . The module is in slot 3 and all tests were requested to be run one time.
Running Hardware Diagnostics Page 36-13 The module is reset, and then the rest of the tests will run. Testing Slot 3 - Ether/12 Resetting slot 3... Test In Progress: CSR Test OK1, OK2 LEDS will displa.
Running Hardware Diagnostics Page 36-14 The tests are complete at this point. A summary of the test results and failures is displayed at the end of the test sequence. In this example, the module passed all tests except the port test. The ESX-K-C-32 module in slot 3 should have a red OK2 LED to indicate diagnostics failure.
Displaying Available Diagnostic Tests Page 36-15 Displaying A vailable Diagnostic T ests The testdisp command provides the user with a display of applicable tests for a particular slot or for the entire chassis configuration.
Configuring the Diagnostic Test Environment Page 36-16 Configuring the Diagnostic T est Environment The testcfg command allows the user to tailor diagnostic testing characteristics per slot module. To configure diagnostic tests for a switching module, enter the testcfg command followed by the slot number for the module.
Configuring the Diagnostic Test Environment Page 36-17 Configuring T ests for Ethernet Modules Tailoring of applicable Ethernet modules includes selection of Port Speeds and of Port Modes.
Running Frame Fabric Tests on Omni Switch/Routers Page 36-18 Running Fr ame Fabric T ests on Omni Switch/Routers You can test the Omni Switch/Router Multi VBUS ( MVBUS ) backplane and the frame fabric ASIC of every switching module with the framefab command.
Running Frame Fabric Tests on Omni Switch/Routers Page 36-19 Test Coverage: All Fabric Inputs/Outputs not tested: Fabric in slot 2 (ESX-C12) has 9 inputs (0-8) and 1 output (0) All inputs tested All O.
Running Diagnostics on an Entire Chassis Page 36-20 Running Diagnostics on an Entir e Chassis The testcfg command allows you to tailor diagnostic testing characteristics by module or for an entire chassis. (Please refer to Configuring the Diagnostic Test Environment on page 36-16 for configuring tests for a single module.
Running Diagnostics on an Entire Chassis Page 36-21 2) Stop on Failur e Enter 2 to halt diagnostics in an active state when a failure occurs or 1 (the default) to exit diagnostics and display the Test Summation and Failure Summation sections of the test command output.
Diagnostic Test Cable Schematics Page 36-22 Diagnostic T est Cable Schematics The figures below and on the following pages provide information on port test cables and plugs.
Diagnostic Test Cable Schematics Page 36-23 BRI S/T Crossover Wrap Cable — Category 5 UTP Copper Cable with RJ-48 (RJ-45) Connectors RJ-48 (RJ-45) 1 2 3 4 5 6 7 8 RJ-48 (RJ-45) 1 2 4 3 6 5 7 8.
Diagnostic Test Cable Schematics Page 36-24.
Page A-1 A The Boot Line Pr ompt When the switch boots, it requires basic information so that it can configure itself. The switch is delivered with factory default configuration parameters that provide basic information; however, you can change or customize the configuration parameters using the Boot Line prompt.
Entering the Boot Prompt Page A-2 Entering the Boot Pr ompt Perform the following steps to reach the Boot prompt. 1. Connect an ASCII terminal (or computer with a terminal emulator) to the console port on the MPX .
Boot Prompt Basics Page A-3 Boot Pr ompt Basics To get a list of commands enter a question mark ( ? ). A screen similar to the following is shown: ? - print this list @ - boot (load and go) p - print .
Boot Prompt Basics Page A-4 Displaying Current Configur ation (p) To display the current configuration, enter a p at the Boot prompt. A screen similar to the following will be displayed. Boot device : ffs Boot file : /flash/mpx.img Eth IP addr[:mask] : 192.
Boot Prompt Basics Page A-5 Listing A vailable Files in the Flash Memory (L) To list all of the available files in the flash memory that you could load onto the switch, enter the L command. A screen similar to the following is shown: Files available in "/flash": mpx.
Boot Prompt Basics Page A-6 Saving Configuration Changes (S) To save any changes to the configuration parameters, enter the S command at the prompt. The following message appears to confirm when the process is complete: Saving boot information.
Configuring a Switch with an MPX Page A-7 Configuring a Switch with an MPX Perform the following steps to configure an Omni Switch/Router ( MPX ). You can press Ctrl-D at any time to return to the Boot prompt. 1. At the Boot prompt, enter a lowercase c to begin configuring parameters.
Configuring a Switch with an MPX Page A-8 8. You can enter an IP address for the first hop router to a remote host (if the host is on a different IP net). A screen prompt similar to the following displays. User : 9. You can enter a log-in name for a remote host.
Configuring a Switch with an MPX Page A-9 14. To accept the default ( oxb ) and perform a normal boot, press the <Enter> key. To restore the factory-configured boot process, enter 0x1000 . The following flags should only be used for internal debugging or Customer Service diagnosis: • 0x02 Load the local system symbols.
Configuring a Switch with an MPX Page A-10.
Page B-1 B Custom Cables This appendix provides detailed information, including illustrations and pin diagrams, for the cables that can be used with Omni Switch/Router Submodules. These custom cables are available from Alcatel, but you can use the following information to manufacture them.
Page B-2 V .35 DTE Cable (F or WSX-to-DCE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-3 V .35 DCE Cable (For W SX-to-DTE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-4 RS232 DTE Cable (F or WSX-to-DCE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-5 RS232 DCE Cable (For W SX-to-DTE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-6 RS530 DTE Cable (F or WSX-to-DCE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-7 RS530 DCE Cable (For W SX-to-DTE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-8 X.21 DTE Cable (F or WSX-to-DCE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-9 X.21 DCE Cable (For W SX-to-DTE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-10 RS449 DTE Cable (F or WSX-to-DCE De vice Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connec- tor-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-11 RS-449 DCE Cable Assembly (For W SX-to-DTE De vice 75 Ω Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26-Pin HD50 Connec- tor-male • AMP 750850-6 26-Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufac- turer.
Page B-12 RJ-45 to DB15F Cable Assembly (For T1/E1 P ort 120 Ω Connections) The following parts are recommended for the ends of the cable: • For the switch side of the cable assembly (P1): 8-conductor RJ-45 round connector (MTP-88U or equivalent) • Parts for the customer end of the cable (P2) can be of any industry-standard manu- facturer.
Page B-13 RJ-45 to BNC Cable Assembly (For E1 75 Ω P ort Connections) The following parts are recommended for manufacturing the cable: • For the switch side of the cable assembly (P1): 8-conductor.
Page B-14.
Page I-1 Index ! commands 4-26 + or - commands 17-7 ? command 4-16 , 4-25 10/100 16-1 , 16-8 10/100 command 15-4 10/100 ports 15-5 , 15-8 10/100cfg command 3-15 , 15-5 , 15-7 10/100vc command 15-8 802.
Page I-2 Index C cacheconfig command 9-33 CAM configuring 9-25 CAM threshold 11-5 camcfg command 9-25 camstat command 9-24 caplog command 10-11 cas command 16-8 , 16-11 Frame Relay bridging 29-57 Fr.
Page I-3 Index E E1 configuring 31 timeslots 28-45 fractional 28-6 framing 33-2 eb command 7-9 echo command 4-31 edit command 7-7 edit commands tutorial 7-11 , 7-12 encapsulation 18-6 IP 18-6 IPX 18-.
Page I-4 Index control signals 29-46 Discard Eligibility 29-9 DLCI 29-6 DLCMI 29-24 errors 29-48 FECN 29-12 IP routing 29-15 IPX routing 29-18 polling 29-25 port configuration 29-22 Routing Group 29-.
Page I-5 Index Hello messages and XMAP 21-2 help command 4-15 history command 4-26 hmstat command 11-7 hot swapping 1-11 , 1-14 , 3-7 hpstat command 11-8 hreset command 11-8 HRE-X 1-22 router register.
Page I-6 Index IPX RIP/SAP Filtering adding global filters 27-19 adding specific filters 27-20 configuring NetW are for W AN links 27-33 default setting of filters 27-18 deleting filters 27-22 d.
Page I-7 Index load command 5-4 login accounts 4-33 , 8-2 login alert banner 4-31 logout command 4-16 lookup command 4-25 ls command 5-4 , 7-3 M MAC 17-16 , 17-17 MAC addresses configuring 14-6 resto.
Page I-8 Index nisuf command 6-14 noecho command 4-31 non-Ethernet ports 19-29 Non-mobile Groups 19-1 , 19-15 ntaccess command 12-5 , 12-36 ntadmin command 12-5 , 12-33 ntconfig command 12-5 ntinfo c.
Page I-9 Index P partition management 8-11 , 8-19 password 4-33 , 8-2 changing 8-2 path MTU discovery 25-42 ping command 25-22 pinouts Ethernet modules 3-15 W AN modules 3-22 pmapcr command 19-17 pmap.
Page I-10 Index R rb command 7-8 reboot 8-3 - see also boot re boot command 8-3 receive threshold 11-3 redundancy MPX 1-7 , 1-10 , 1-13 , 2-9 , 6-9 power supply 1-11 , 1-14 re-executing commands 4-26 .
Page I-11 Index stc command 17-25 , 17-38 , 17-39 sts command 17-28 , 17-38 , 17-39 summary command 4-15 , 9-1 swap command 6-20 swch command 18-30 , 18-31 switch software 2-7 switc h command 4-15 , 1.
Page I-12 Index SNAP 18-21 T oken Ring 18-19 transmission states XMAP 21-3 transmit credit 19-31 transmit/receive threshold 11-3 traps configuring 13-2 tr def command 18-28 troubleshooting 35-1 T run.
Page I-13 Index secondary traffic 22-6 translated frames 24-7 viewing 20-23 , 22-27 vlap command 21-9 vs command 19-53 W wan command 28-14 W AN Links accessing the LINK menu 31-2 adding a link record.
Page I-14 Index.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Alcatel Carrier Internetworking Solutions Switch/Router è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Alcatel Carrier Internetworking Solutions Switch/Router - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Alcatel Carrier Internetworking Solutions Switch/Router imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Alcatel Carrier Internetworking Solutions Switch/Router ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Alcatel Carrier Internetworking Solutions Switch/Router, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Alcatel Carrier Internetworking Solutions Switch/Router.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Alcatel Carrier Internetworking Solutions Switch/Router. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Alcatel Carrier Internetworking Solutions Switch/Router insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
