Part No. 060166-10, Rev. C March 2005 Omni Switch/Router ™ User Manual Release 4.5 www.alcatel.
An Alcatel service agreement brings your company the assurance of 7x24 no-excuses technical support. You’ll also receive regular software updates to maintain and maximize your Alcatel product’s features and functionality and on-site hardware replacement through our global network of highly qualified service delivery partners.
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. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions in this guide, may cause interference to radio communications.
page iv
Table of Contents 1 Omni Switch/Router Chassis and Power Supplies . . . . . . . . . . . . . . . . 1-1 Omni Switch/Router User Interface (UI) Software . . . . . . . . . . . . . . . . . . . 1-2 Omni Switch/Router Network Management Software (NMS) . . . . . . . . . . . 1-2 Omni Switch/Router Distributed Switching Fabric . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Omni Switch/Router Fabric Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents MPX Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Change-Over Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 MPX Redundancy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 3 Omni Switch/Router Switching Modules . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Required Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 4 The User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Overview of Command Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Changing Between the CLI and UI Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Exit the Command Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 UI to CLI Command Cross Reference . . . . . . Hardware Commands .
Table of Contents Multiple User Sessions . . . . . . . . . . . . . . Listing Other Users . . . . . . . . . . . . . Communicating with Other Users . . . Deleting Other Sessions . . . . . . . . . . Advanced Kill Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Synchronizing Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Synchronizing Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Loading a File From the Primary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Gaining Control from the Primary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Resetting a Secondary MPX . . . . . . . . . . . . . . . . . . .
Table of Contents Secure Switch Access . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Secure Switch Access Filter Database Configuring Secure Access Filter Points . . . . . . . . . . Enabling/Disabling Security Parameters . . . . . . . Adding Filters . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Filters . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Secure Access Violations Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Duplicate MAC Address Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30 Multicast Claiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32 Disabling Flood Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32 Saving Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33 10 Switch Logging . . . . . . . . . .
Table of Contents NTP Information Menu . . . . . . . . . . . . . . . . . . . . . . . . Display List of Peers the Server Knows About . . . . . Display Peer Summary Information . . . . . . . . . . . . Display Alternate Peer Summary Information . . . . . Display Detailed Information for One or More Peers Print Version Number . . . . . . . . . . . . . . . . . . . . . . Display Local Server Information . . . . . . . . . . . . . . page xii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 13 SNMP (Simple Network Management Protocol) . . . . . . . . . . . . . . . . 13-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 Configuring SNMP Parameters and Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Configuring a New Network Management Station . . . . . . . . . . . . . . . . . . 13-4 Viewing SNMP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 16 Managing 802.1Q Groups ............ IEEE 802.1Q Sections Not Implemented Application Example . . . . . . . . . . . . . . . . . Single vs. Multiple Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1 16-2 16-3 16-4 Assigning an 802.1Q Group to a Port . . . . . . . . . . . . . . . .
Table of Contents Configuring Fast Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . Truncating Tree Timing & Speedy Tree Protocol . . . . . . . . . . Truncating Tree Timing . . . . . . . . . . . . . . . . . . . . . . . . . Speedy Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Truncating Tree Timing & Speedy Tree Protocol Displaying Fast Spanning Tree Port Parameters . . . . . . . . . . . Enabling Fast Spanning Tree Port Parameters . . . . . . . . . . . .
Table of Contents MTU Handling . . . . . . . . . . . . IP Fragmentation . . . . . . . . ICMP Based MTU Discovery IPX Packet Size Negotiation Other Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 19 Managing Groups and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1 How Ports Are Assigned to Groups . . . . . . . . . . . . Static Port Assignment . . . . . . . . . . . . . . . . Dynamic Port Assignment (Group Mobility) How Dynamic Port Assignment Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How Port Mirroring Works . . . . . . . . . . . . . . . . . What Happens to the Mirroring Port . . . . . . . . . . Using Port Mirroring With External RMON Probes Setting Up Port Mirroring . . . . . . . . . . . . . . . . . . . . . Disabling Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Viewing Policy Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-24 Viewing Virtual Ports’ Group/VLAN Membership . . . . . . . . . . . . . . . . . . . . . . . .20-25 View VLAN Membership of MAC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20-26 Application Example: DHCP Policies The VLANs . . . . . . . . . . . . . DHCP Servers and Clients . . DHCP Port and MAC Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Routing Between AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-15 Creating AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . Step A. Entering Basic VLAN Information . . . . . . . . . . Step B. Defining and Configuring VLAN Policies . . . . . Step C. Configuring the Virtual Router Port (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-16 .
Table of Contents 25 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1 IP Routing Overview . . . . . . . . Routing Protocols . . . . . . . Transport Protocols . . . . . . Application-Layer Protocols Additional IP Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Displaying IP RIP Filters . . . . . . . . . . . . . . . . Displaying a List of All IP RIP Filters . . . . . Displaying a List of “Global” IP RIP Filters Displaying a List of Specific IP RIP Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-37 .25-37 .25-38 .25-38 Viewing the IP-to-MAC Address Table . . . . . . . . . . . . .
Table of Contents 27 IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1 Introduction . . . . . . . . . . . . . . . . . . . . . . IPX Routing Overview . . . . . . . . . . . . IPX Protocols . . . . . . . . . . . . . . . . Setting Up IPX Routing on the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 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 . . . . . . . . . . . . . . . . . . . . . .27-37 Configuring an IPX Default Route . . . . . . . . . . Adding an IPX Default Route . . . . . . . . . . . Viewing the Status of an IPX Default Route Disabling an IPX Default Route . . . . . . . . .
Table of Contents 29 Managing Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-1 Back-to-Back Frame Relay Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 29-3 Universal Serial Port Cable Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4 “Physical” and “Logical” Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-4 Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Managing Frame Relay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-55 Configuring a Bridging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-57 Configuring a WAN Routing Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-59 Step 1. Set Up a Frame Relay Routing Group . . . . . . . . . . . . . . . . . . . . .29-59 Step 2. Set Up a Frame Relay Routing Service . . . . . . . . . . . . . . . . .
Table of Contents Viewing WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-12 Displaying All Existing WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-12 Displaying Information for a Specific WAN Link . . . . . . . . . . . . . . . . . . .31-13 Displaying Link Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-15 Displaying Status for All WAN Links . . . . . . . . . . . . . . . . . . . . .
Table of Contents 34 Backup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-1 Backup Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Backup Services Menu . . . . . . . . . . . . . . . . . . . . . . Adding a Backup Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents TEMP LED is Amber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STA LED Is Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents A The Boot Line Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Entering the Boot Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Boot Prompt Basics . . . . . . . . . . . . . . . . . . . . . . . . . . Resuming Switch Boot (@) . . . . . . . . . . . . . . . Displaying Current Configuration (p) . . . . . . . Loading the Last Configured Boot File (l) . . . .
1 Omni Switch/Router Chassis and Power 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. With Omni Switch/Router, network administrators can replace aging FDDI or Fast Ethernet backbones with high capacity Gigabit Ethernet backbones. ♦ Important Notes ♦ Beginning with Release 4.4, FDDI is no longer supported. Beginning with Release 4.
Currently, Omni Switch/Router switching modules consist of Gigabit Ethernet modules, autosensing 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. ♦ Important Note ♦ Omni Switch/Router modules require the use of an Omni Switch/Router chassis (see Omni Switch/Router Chassis and Power Supplies on page 1-7).
Omni Switch/Router Distributed Switching Fabric Omni Switch/Router Distributed Switching Fabric Many switches in the market employ a shared memory architecture, which uses a central switching engine to send data to the appropriate port. As shown in the figure below, data enters the input port (➊ below), crosses the switching fabric on its way to the central switching engine(➋ below), and again crosses the switching fabric (➌ below) before exiting the appropriate output port (❹ below).
Omni Switch/Router Distributed Switching Fabric Omni Switch/Router Fabric Capacity In a chassis with Omni Switch/Router modules only, each Omni Switch/Router module provides 2.4 Gbps of switching capacity in full-duplex mode. In a chassis with all Omni Switch/Router modules, the Omni Switch/Router architecture provides up to a 22 Gbps distributed switching fabric.
Omni Switch/Router Applications and Configurations Omni Switch/Router Applications and Configurations Omni Switch/Router hardware is ideally suited to meet the most demanding server and backbone needs. In addition, Omni Switch/Router hardware can be integrated easily with OmniSwitches and with OmniStack workgroup switches. The examples that follow show how the Omni Switch/Router can be used as a network backbone and as the central switch/router in a wiring closet.
Omni Switch/Router Applications and Configurations Omni Switch/Router as the Central 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. On the third floor, an Omni Switch/Router chassis connects a mixture of 10BaseT and 100BaseTx workstations with an auto-sensing Ethernet module.
Omni Switch/Router Chassis and Power Supplies Omni Switch/Router Chassis and Power 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. The Omni Switch/Router chassis also offer such failure resistant features as redundant MPXs, redundant power supplies, and hot swapping of switching modules.
Omni Switch/Router Chassis and Power Supplies 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. A built-in power supply is located on the right side of the chassis, and a fan cooling system is located on the left side of the chassis. The chassis can be rack-mounted.
Omni Switch/Router Chassis and Power Supplies OmniS/R-3 Chassis Technical 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. (8.18 kg), fully populated with modules and power supplies. Switching Backplane Up to 7 Gbps (aggregate) switching fabric capacity Voltage Range 85-270 VAC, 47 to 63 Hz, auto-ranging and auto-sensing Current Draw 3.8 Amps at 100/115 VAC 1.
Omni Switch/Router Chassis and Power Supplies 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. ♦ Warning ♦ If you have an OmniS/R-5 with a single power supply, do not remove the cover on the empty power supply slot.
Omni Switch/Router Chassis and Power Supplies 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. If one should fail, the remaining power supply automatically takes up the load without any disruption to the operation. See Chapter 1, “Omni Switch/Router Chassis and Power Supplies,” for more information on installing and removing power supplies.
Omni Switch/Router Chassis and Power Supplies OmniS/R-5 Technical 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. (24.09 kg), fully populated with modules and power supplies. Switching Backplane Up to 12 Gbps (aggregate) switching fabric capacity Voltage Range 90-265 VAC, 47 to 63 Hz auto-ranging and auto-sensing.
Omni Switch/Router Chassis and Power Supplies 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. Slots for two power supplies are located at the bottom of the chassis. A separate, removable fan tray containing four fans is located above the power supply module bays.
Omni Switch/Router Chassis and Power Supplies 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. If one should fail, the remaining power supply automatically takes up the load without any disruption to the operation.
Omni Switch/Router Chassis and Power Supplies OmniS/R-9 Technical 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. (43.55 kg), fully populated with modules and power supplies.
Omni Switch/Router Chassis and Power Supplies OmniS/R-9P Technical 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. (43.55 kg), fully populated with modules and power supplies.
Omni Switch/Router Chassis and Power Supplies OmniS/R-9P-48V Technical 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. (43.55 kg), fully populated with modules and power supplies. Switching Backplane Up to 22 Gbps (aggregate) switching fabric capacity Voltage Range 40-60 VDC Current Draw 23 Amps Watts (Output) 725 Current Provided 120 Amps at 5.
Omni Switch/Router Chassis and Power Supplies Omni Switch/Router Power Requirements Always make sure that the total power requirements of the modules in your chassis do not exceed the limits of your power supply. To check the power consumption of your configuration, refer to the tables on the following pages and add up the DC Current Draw of all modules in your switch. The tables beginning on page 1-19 list modules without an HRE-X and the tables beginning on page 1-20 list modules with an HRE-X.
Omni Switch/Router Chassis and Power Supplies 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. 10.25 B ESX-K-100FM/FS-16W Advanced Fast Ethernet (100 Mbps) module with sixteen (16) fiber MT-RJ ports. 9.75 B GSX-K-FM/FS-2W Advanced Gigabit Ethernet module with two (2) fiber SC ports. 5.
Omni Switch/Router Chassis and Power Supplies 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. 11.75 B ESX-FM-24W-L3 10 Mbps Ethernet module with twenty-four (24) fiber VF-45 ports 14.5 B ESX-K-100FM/FS16W-L3 Advanced Fast Ethernet (100 Mbps) module with sixteen (16) fiber MT-RJ ports. 11.
Omni Switch/Router Chassis and Power Supplies Grounding a Chassis Omni Switch/Routers have two grounding screw holes on the back of the chassis. These holes use 10-32 screws and are approximately 1 inch apart. In addition, these holes do not have paint and are surrounded by a small paint-free rectangular section, which provides for a good connection contact. The figure below shows the location of the grounding screw holes on the back of an OmniS/R-9.
The Omni Switch/Router Hardware Routing Engine (HRE-X) The Omni Switch/Router Hardware 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 HRE-X is a submodule, which plugs into an Omni Switch/Router module, that provides high speed Layer 3 distributed routing for IP and IPX traffic. The HRE-X intercepts frames from the switching logic and determines if a frame should be switched or routed.
The Omni Switch/Router Hardware Routing Engine (HRE-X) 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 Connecting a DC Power Source 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. This supply requires the use of 12 gauge wire. A clamp inside each connector keeps the power wire tightly in place during operation. This connector has side screws that can be used to remove the connector.
Connecting a DC Power Source to an OmniS/R-PS5-DC375 Loosen Screw. (-)/(+)/GND Door inside square hole will open when screw is loosened in top circular hole. 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. The lead you insert must match the lead attached to the 48-volt power source (i.e.
Connecting a DC Power Source to an OmniS/R-PS5-DC375 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 Connecting a DC Power Source 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. This supply requires the use of 10 gauge wire. A clamp inside each connector keeps the power wire tightly in place during operation.
Connecting a DC Power Source to an OmniS/R-PS9-DC725 Installing DC Power Source Wire 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. 1. Prepare the three (3) wires—10 gauge—that will plug into the power supply. First, make sure they are not plugged into the 48-volt power source. 2.
Connecting a DC Power Source to an OmniS/R-PS9-DC725 GND/(+)/(-) This end would plug into the ground (GND). The middle lead would plug into the positive (+) power source and the rightmost lead would plug into the negative (-) power source. 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. The wire lead should be securely attached inside the connector.
Replacing Power Supplies (9-Slot Chassis) Replacing Power 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. ♦ Note ♦ In all cases, swapping operations must be made with the power switch of the replacement power supply turned OFF.
2 The Omni Switch/Router MPX Omni Switch/Router Management Processor Module (MPX) Features The MPX provides such system services as maintenance of user configuration information, downloading of switching module software, basic bridge management functions, basic routing functions, the SNMP management agent, access to the User Interface software, and Advanced Routing. In addition, the MPX can operate in a redundant configuration with another MPX.
Omni Switch/Router Management Processor Module (MPX) Features Label . This label will indicate the Warning Label. This label indicates Ethernet management port type. It will read either MPX 10 mm (multimode fiber Ethernet port) or MPX 10 (copper RJ-45 Ethernet port). PS K1 K2 O O 1 PS 2 MPX 10 mm CLASS 1 LASER PRODUCT that the module contains an optical transceiver (on the MPXs with fiber ST Ethernet ports only). PS1 (Power Supply 1 Status).
Omni Switch/Router Management Processor Module (MPX) Features MPX 10 K1 K2 O O 1 PS 2 PS SE M TE I PR C Modem Connector. A male serial DB9 DTE connector for switch file transfers and network management functions. P M O Console Connector. A female serial DB-9 DCE connector for switch file transfers and network management functions. D EM The MPX module includes one row of LEDs for the Ethernet management port. C O N SO LE ET H ER N ET COL (Collision).
MPX Serial and Ethernet Management Ports MPX Serial and Ethernet Management Ports 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. One port, called the “modem” port, is male and the other, called the “console” port, is female. See MPX Management Connectors on page 2-3 for illustrations of these ports.
MPX Serial and Ethernet Management Ports MPX Modem Port Specifications 1 Pin Number Standard Signal Name Direction 1 Not Used 2 RD To MPX 3 TD From MPX 4, DTR From MPX 5 GND 6 DSR To MPX 7 RTS From MPX 8 CTS To MPX 9 Not used Shell Shield GND 5 6 9 MPX Modem Port Ethernet Management Port The MPX also supports an out-of-band Ethernet port for high-speed uploads and switch management functions.
MPX Serial and Ethernet Management Ports MPX Model Ethernet Management Port Type (Cable Type) Max.
Flash Memory and Omni Switch/Router Software Flash Memory and Omni Switch/Router Software Flash memory on the MPX holds the Omni Switch/Router’s executable images and configuration data. When a switching module comes online, the MPX downloads the appropriate image file for that module to that module’s memory. Image files (those with the img extension) contain executable code for different switching modules and software features.
Flash Memory and Omni Switch/Router Software 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. These operations require available space in flash memory. In general the flash memory on the switch should always have at least 75000 bytes available at all times.
MPX Redundancy MPX Redundancy In order to provide greater reliability, Omni Switch/Router supports two MPXs in a primary/secondary redundant configuration. If the primary MPX fails, the secondary MPX takes over without any operator intervention. ♦ Warning ♦ Do not install any version of the MPM (i.e, MPM-C, MPM 1G, MPM II, or original MPM) in a chassis with an MPX. Installing an MPM in a chassis with an MPX can cause physical damage.
MPX Redundancy MPX State Requirement for State Redundant Both MPXs are running the same version of software and the configurations are in sync. Configuration Fallback Both MPXs are running the same version of software but the configurations are different. Software Fallback The MPXs are running different versions of software, and their configurations may be the same or different. None There is only one MPX installed in the chassis.
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.
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. ♦ Important Note ♦ Omni Switch/Router switching modules require an MPX. You cannot install any version of the MPM (i.e, MPM-III, MPM-C, MPM-1G, MPM-II, or original MPM) in a chassis with an MPX.
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.img, fpx.img ESX-K-100C-32W esx.img ESX-K-100FM/FS-16W esx.img GSX-K-FM/FS/FH-2W esx.img VSX-VSA vsx.img, text_cfg.img, vsmboot.asc VSX-VSD vsx.img, text_cfg.img, vsmboot.asc WSX-S-2W wsx.img WSX-SC-4W wsx.img WSX-SC-8W wsx.
Installing a Switching Module 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 installing and removing switching modules. You can also hot swap modules of the same type while the switch is active. Switching modules may be installed in any slot other than Slot 1. (Slot 1 is reserved for an MPX.
Installing a Switching Module 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. The screws should be tight enough such that a screwdriver would be necessary to loosen the screws.
Installing a Switching Module 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. ♦ Anti-Static Warning ♦ Before handling a switching module, free your hands of static by wearing a grounding strip, or by grounding yourself properly. Static discharge can damage the components on your switching module. 1.
Hot Swapping a Switching Module Hot Swapping 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. For example, if you remove an ESX switching module you must replace it with another ESX switching module. ♦ Note ♦ You cannot hot swap a module into a previously empty slot.
Hot Swapping a Switching Module 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. In addition, the swap time will reset to its original value. (For example, if you set the swap time to 15 minutes in step 1, you will have 15 minutes again, regardless of how much time has elapsed.
Diagnostic Tests 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. Swap is OFF, timeout is 5 minutes usage swap { ON [ minutes ] | OFF [ minutes ] } Diagnostic Tests All switching modules are subjected to extensive power-on diagnostics during the Power-On Self-Test cycle (POST).
Handling Fiber and Fiber Optic Connectors Handling Fiber and Fiber Optic Connectors Using fiber is extremely simple, but a few important rules should always be followed: Step 1. Use Premium Grade Jumper Cables with Duplex SC Connectors There are many brands of fiber optic jumper cables, with a wide range of quality between each manufacturer. Premium cables do three things well: • They provide a good polish on the fiber optic connector endface (where the light exits the cable).
Handling Fiber and Fiber Optic Connectors 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). The connector is now clean. 3. Release the cloth-forwarding lever, allowing it to return to its initial position. A cleaning cloth reel can enable over 400 cleanings and is replaceable.
Gigabit Ethernet Modules 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 backbone connections using fiber (SC) connectors. This module is described and illustrated in the following sections. ♦ Note ♦ Wait at least five (5) seconds after a cable is pulled from a GSX module before reinserting it.
Gigabit Ethernet Modules GSX-K-FM/FS/FH-2W Technical Specifications Number of ports 2 Connector Type SC Standards Supported 802-3z, 1000Base-LX, and 1000Base-SX Data Rate 1 Gigabit per second (full duplex) Maximum Frame Size 1,518 bytes MAC Addresses Supported 8,192 Connections Supported 1000Base-LX or 1000Base-SX connection to backbone or server Cable Supported Multimode and single mode Output Optical Power -9.5 to -4 dBm (Multimode) -9.
Gigabit Ethernet Modules Module Label. This label will indicate GSX-K sm CLASS 1 LASER PRODUCT Warning Label. This label indicates that the module contains an optical transceiver. O the GSX-K-FM/FS/FH-2W type. It will read either GSX-K mm (multimode cable), GSX-K sm (intermediate-reach single mode cable), or GSX sm K long reach ( long-reach single-mode cable). K1 O K2 1 2 X R TX K N LI This Gigabit Ethernet module includes one row of LEDs for each port.
Auto-Sensing 10/100 Ethernet Modules Auto-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. The following Omni Switch/Router 10/100 and Fast Ethernet modules are available: • ESX-K-100C-32W Advanced switching module with thirty-two (32) auto-sensing 10/100 Mbps desktop connections using RJ-45 ports. This module is described and illustrated in the following sections.
Auto-Sensing 10/100 Ethernet Modules The 32 RJ-45 ports may connect to unshielded or shielded twisted pair (UTP) cable (see ESXK-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. The ESX-K-100C-32W can be used in the wiring closet with a mix of 100 Mbps Ethernet devices and 10 Mbps Ethernet devices that are transitioning to higher speed connections.
Auto-Sensing 10/100 Ethernet Modules ESX-K-100C-32W Technical Specifications Number of ports 32 Connector Type RJ-45 Standards Supported IEEE 802.
Auto-Sensing 10/100 Ethernet Modules ESX-K 10/100 OK1 A C 7 1 3 4 5 6 8 7 8 8 6 7 5 4 5 6 8 2 3 3 1 4 6 7 1 4 5 2 2 3 2 B D Each LED corresponds to a port on the module. When an LED is on Port Green continuously, a good cable LEDs connection exists. The LED will blink Green when traffic is transmitted or received on the port.
Fast (100 Mbps) Ethernet Modules Fast (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. The following Omni Switch/Router Fast Ethernet modules are available: • ESX-K-100FM/FS-16W Advanced switching module with sixteen (16) Fast Ethernet (100 Mbps) backbone connections using MT-RJ ports. This module is described and illustrated in the following sections.
Fast (100 Mbps) Ethernet Modules ESX-K-100FM/FS-16W Technical Specifications Page 3-20 Number of ports 16 Connector Type MT-RJ Standards Supported IEEE 802.3; IAB RFCs 826, 894 Data Rate 100 Mbps (full duplex) Maximum Frame Size 1,518 bytes MAC Addresses Supported 8,192 Connections Supported 100Base-Fx connection to backbone or server Cable Supported Multimode: 62.
Fast (100 Mbps) Ethernet Modules Module Label. This label will indicate ESX-K 100 sm CLASS 1 LASER PRODUCT Warning Label. This label indicates that the module contains an optical transceiver). O K1 O K2 9 5 1 13 14 15 16 2 Module O K 1 ( H a r d w a r e S t a t u s ) . O n Green when the module has LEDs passed diagnostic tests successfully. On Red when the hardware has failed diagnostics. 3 4 8 12 Each LED corresponds to a port on the module.
WAN Modules WAN 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. • WSX-FT1/E1-SC Provides one or two T1/E1 ports and one or two serial ports that support Frame Relay or PPP with data compression.
WAN Modules WAN BRI Port Specifications (S/T Interface) 1 8 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 Not Used WAN BRI Port Specifications (U Interface) 1 8 Pin Number Standard Signal Name 1 Not Used 2 Not Used 3 Xmt to /Rcv from Network 4, Xmt to /Rcv from Network 5 Not Used 6 Not Used 7 Not Used 8 Not Used Page 3-23
WAN Modules WAN T1/E1 Port Specifications 1 8 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.) 8 Chassis GND (A jumper is provided for connecting Pins 7 and 8 to the chassis ground, if required.
WAN Modules WAN Serial Port 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 AB 7 SG 19 Transmitted Data DTE TD(A) 2 BA(A) 2 SD(A) 4 TD(B) 14 BA(B) 14 SD(B) 22 Received Data DCE RD(A) 3 BB(A) 3 RD(A) 6 RD(B) 16 BB(B) 16 RD(B) 24 TC(A) 15 DB(A) 15 ST(A) 5 TC(B) 12 DB(B) 12 ST(B) 23 TC(A) 17 DD(A) 17 RT(A) 8 TC(B) 9 DD(B) 9 RT(
WAN Modules WAN Serial Port Specifications (cont.) X.21/X.26 RS232 Generic Signal Name Source Mnemonic Pin Mnemonic Pin Mnemonic Pin Shield -- -- 1 -- A -- 1 Signal Ground -- G 8 102 B AB 7 Transmitted Data DTE T(A) 2 103(A) P BA 2 T(B) 9 103(B) S Received Data DCE R(A) 4 104(A) R BB 3 R(B) 11 104(B) T -- -- 114(A) Y DB 15 114(B) AA DD 17 DA 24 Transmit Clock DCE Receive Clock Page 3-26 V.
WAN Modules 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. ♦ Note ♦ The WSX-S-2W does not support hardware compression. The WSX-S-2W can sense and auto-configure for any of five serial cable types (RS-232, V.35, X.21, RS-530, and RS-449).
WAN Modules WSX O K1 O TX X R A OK2 (Software Status). Blinking 1 2 Green when the module software was downloaded successfully and the module is communicating with the MPX . Blinking Amber when the module is in a transitional state. On solid Amber if the module failed to download software from the MPX. 1 TX (Transmit). On “half- ST tinuously when the port connection is operational. Off when the port is disabled or the cable is detached.
WAN Modules 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). See WSX-SC Technical Specifications on page 3-30 for more information. The WSX-SC can sense and auto-configure for any of five serial cable types (RS-232, V.35, X.
WAN Modules WSX-SC Technical 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.6, 19.
WAN Modules WSX O 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 contains two sets of four rows of LEDs. The second set of LEDs are located above the second set of ports. K1 Please refer to 2-Port WAN Module Frame Relay Switching Module on page 3-28 for further LEDs information on these LEDs.
WAN Modules 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; the E1 version is referred to as the WSX-FE1-SC. You can configure these ports to run either Frame Relay or the Point-to-Point Protocol (PPP). See WSX-FT1/E1-SC Technical Specifications on page 3-33 for more information.
WAN Modules WSX-FT1/E1-SC Technical 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 Standards Supported RFCs 1406, 1213, 1659 Frame Formats T1: Superframe, Extended Superframe, Unframed E1: E1, E1-CRC, E1-MF, E1-CRC-MF, Unframed Line Coding T1: B8ZS or AMI E1: HDB3 or AMI Data Rates Supported T1: 1.544 Mbps E1: 2.
WAN Modules WSX 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 contains two sets of LEDs. The second set of LEDs are located above the third and fourth ports. O K1 O K2 Please refer to 2-Port WAN Module Frame Relay Switching Module on page 3-28 for further LEDs information on these LEDs. STA (Status).
WAN Modules 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. For more detailed information on the types of cables to use with this module, see Appendix B, “Custom Cables.” The illustration below shows the correct jumper positions. ♦ Note ♦ JP3 is reserved. Do not set a jumper across JP3.
WAN Modules 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. The version with 1 serial port and 1 BRI port is referred to as the WSX-BRI-SC-1W; the version with 2 serial ports and 2 BRI ports is referred to as the WSX-BRI-SC-2W. See WSX-BRI-SC Technical Specifications on page 3-37 for more information.
WAN Modules WSX-BRI-SC Technical 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 serial BRI Connector Type RJ-45 Protocols Supported Point-to-Point Protocol (PPP); Frame Relay (supported on the serial port only) Data Rates Supported 2 “B” Channels at 56/64 Kbps 1 “D” Channel at 16 Kbps Compression Hardware-based using STAC 9705 MAC Addresses Supported 4,096 Serial Port Connections Suppo
WAN Modules WSX O K1 O K2 Please refer to 2-Port WAN Module Frame Relay Switching Module on page 3-28 for further LEDs information on these LEDs. X ST AC 1 A TX R ST 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 Jumper Configuration for the “U” Interface (this is how the board is shipped) This is a simplified view of the bottom lower-right quadrant of the WSX-BRI submodule. Immediately above the BRI port are three jumper blocks labelled J14, J15, and J16. About two inches above and to the right is another jumper labeled J13. J13, J14, and J16 are used to switch between the “U” and “S/T” interfaces. J15 is used to set transmit and receive termination for the “S/T” interface.
WAN Modules Page 3-40
4 The User 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. When a switch boots up, the boot monitor handles the loading of this executable image and system startup. Once the image is loaded and initialized, the CLI starts. You access the command interfaces through a connection with the switch.
Overview of Command Interfaces Changing Between the CLI and UI Modes Once you log on to the switch, the following screen displays. You must press the key to start the command interface. ************************************************************************************* Alcatel Omni Switch/Router Copyright (c), 1994-2002 Alcatel Internetworking, Inc. All rights reserved.
Overview of Command Interfaces 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 . Your session is immediately terminated. ♦ Note ♦ If you forget which command interface mode you are in, type the ? character. If you are in the UI mode, the Main Menu will display as shown above. If you are in the CLI mode, the switch will show the following display. ^NO, SHOW, VOICE, SYSTEM, ACCOUNTING, . . .
UI to CLI Command Cross Reference UI to CLI Command Cross 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. The CLI commands are fully documented in the Text-Based Configuration CLI Reference Guide.
UI to CLI Command Cross Reference Basic Switch Management Table Chapter UI Command Equivalent CLI Commands PM Family 4, “The User Interface” alert, echo, history, kill, ping, pwd, timeout, who alert, echo, history, kill, ping, password, timeout, who No PM Support lookup, save, summary, uic, write Unsupported 5, “Installing Switch Software” ftp load primary, secondary ftp load primary, secondary GF-Ftp GF-File 6, “Configuring Management Processor Modules” configsync ethernetc imgsync mpm mpmg
UI to CLI Command Cross Reference Basic Switch Management Table (continued) Chapter UI Command Equivalent CLI Commands PM Family 9, “Switch-Wide Parameters” cacheconfig camstat dt hrexassign hrexdisplay hrexhashopt hrexutil info memstat modvp newfs saveconfig slot syscfg systat configuration cache camstat dt hrexassign hrexdisplay hrexhashopt hrexutil info memstat modvp newfs configuration cache save slot syscfg systat No PM Support camcfg, fsck, sc, si, ss, taskstat Unsupported secdefine secappl
UI to CLI Command Cross Reference 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 Groups, VLANs, Policies Commands The table beginning on page 4-8 summarizes the features supported in the UI and the CLI for Chapters 19 through 24. Groups, VLANs, Policies Table Chapter UI Command Equivalent CLI Commands PM Family 19, “Managing Groups and Ports” swch vi port encapsulation view group rules 2-Group autoencaps, ethdef, facdef, propipx, swchmac, trdef Unsupported 20, “Group and VLAN Policies” addqgp addvp cas cats group num 802.
UI to CLI Command Cross Reference Group, VLANs, Policies Table (continued) Chapter UI Commands Equivalent CLI Commands PM Family 22, “Managing AutoTracker VLANs” gmap, gmapst gmapgaptime gmapholdtime gmapuptime xmapst xmapls xmapcmntime xmapdisctime gmap gmap gap time gmap hold time gmap up time xmap, view xmap status view xmap, view xmap xmap common time xmap discovery time 6-Group 23, “Multicast VLANs” cats cratvl 6-Group rmatvl vag vats viatrl vimcvl vivl vpl group elan vlan, vlan router ip,
UI to CLI Command Cross Reference 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 Table Chapter UI Command Equivalent CLI Commands PM Family 25, “IP Routing” All IP Routing commands are supported in the CLI. All IP Routing commands are supported in the CLI.
UI to CLI Command Cross Reference WAN Access 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 WAN Access Table (continued) Chapter UI Command Equivalent CLI Commands PM Family 31, “WAN Links” linkadd, linkmodify interface dialer status description inactivity-timer min call duration max call duration direction organization carrier delay timeout max retries retry delay failure delay phone number speed caller-id 10-WAN 32, “Managing ISDN Ports” isdnm interface bri switch-type spid1 phone 1 spid2 phone2 10-WAN 33, “Managing T1 and E1 Ports” temod, teccfg,
UI to CLI Command Cross Reference Troubleshooting 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 User Interface Menu This menu provides a top-level view of all UI menus. The commands are grouped together in the form of sub-menus. Within each sub-menu there is a set of commands and/or another sub-menu.
Main Menu Summary 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. This menu is fully described in Chapter 7, “Managing Files.” Summary. Provides very basic information on the physical switch, such as its name, MAC address, and resets.
General User Interface Guidelines Diag. This menu, fully available to the diag login account, contains commands to run diagnostic tests. It is described in Chapter 36, “Running Hardware Diagnostics.” Quit. ? Logs you out of the UI. You can also enter logout to exit. Displays the options for current menu. General User Interface Guidelines You can monitor and configure your switch in the following various ways: • The User Interface (UI): The UI is the original method of switch configuration.
General User Interface Guidelines ♦ 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 key to regain the prompt. Quitting a Command Many of the commands give you a list of parameters to change. With most commands you can enter in quit if you want to exit the command without making changes. If the quit parameter is not available, press Ctrl-d to abort the command without making changes.
General User Interface Guidelines Configuring the System Prompt 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 information, or a combination of the two. Literal information means that the prompt will reflect exactly what you type at the uic submenu. For example, Marketing 1 or Enter command:.
General User Interface Guidelines Configuring More Mode for the User 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. However, before you can specify the maximum number of lines that can be displayed, you must first verify that the more mode is enabled. To enable the more mode, type uic at the user prompt and press . A screen similar to the following will be displayed.
General User Interface Guidelines A screen similar to the following will be displayed. UI Configuration 1) Prompt 2) More 21) Lines 3) Verbose 4) Timeout : ‘$Menu-Path% ’ : on : 22 lines : off : 5 minutes Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) : Type 21=, followed by the maximum number of lines to be displayed, and press . (The value may range from 0 to 2147483647.) For example: 21=2000. After you press , the screen will be redrawn.
General User Interface Guidelines Disabling More Mode To disable more mode, type uic at the user prompt and press . A screen similar to the following will be displayed. UI Configuration 1) Prompt 2) More 21) Lines 3) Verbose 4) Timeout : ‘$Menu-Path% ’ : on : 22 lines : off : 5 minutes Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) : Next, type 2=off at the submenu prompt and press . The screen will be redrawn. Note that more mode is now set to off.
General User Interface Guidelines Setting Verbose/Terse Mode for the User Interface Enabling Verbose 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 Disabling Verbose 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. To display a current menu when verbose mode is disabled, you must type a question mark (?) and then press . To disable verbose mode, type uic at the user prompt and press .
General User Interface Guidelines Configuring the Auto Logout Time When the switch detects no user activity on the UI for a certain period of time, it automatically logs the user out of the system. By default, this automatic logout occurs after 4 minutes of console inactivity. You can configure the automatic logout to range from 1 minute to 35,791,394 minutes. To set a new automatic logout time, type uic at the user prompt and press . A screen similar to the following will be displayed.
General User Interface Guidelines 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 submenus. You can go directly to any sub-menu in the list. You can specify whether the full menu will be displayed when you enter a command for a menu or sub-menu and the amount of information you receive when you run the help command.
General User Interface Guidelines 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. 1: view mpx.cmd 2: vlan 3: at 4: atvl 5: vimcvl 6: mcvl 7: vivl 8: fwtvl 9: xlat 10: history In the example above, the history command is listed last because it is the one that was executed most recently.
General User Interface Guidelines 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 beginning of this section, entering !vim would re-execute the vimcvl command. Entering !vi however, would re-execute the vivl command because it is the most recently executed command beginning with vi.
General User Interface Guidelines Abbreviating IP Addresses 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 Internet interpretation. Several examples of abbreviated IP addresses are shown in the table below. The first column of the table lists examples of abbreviated IP addresses, and the second column shows how the system interprets the abbreviated address.
General User Interface Guidelines 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.2 at the system prompt. After you answer a few prompts (see Chapter 25, “IP Routing” for more information on the ping command), something similar to the following will be displayed. Ping starting, hit to stop PING 198.0.0.
User Interface Display Options User 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 Setting Echo/NoEcho for User 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. Everything you enter will be displayed. For example, if you enter history at the system prompt, it will be displayed on your terminal, as shown in the example below.
User Interface Display Options Creating a new 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.cmd file. • Enable the feature by executing the alert {console | telnet | ftp} command. To create the text file containing your banner you may use the create file command in the UI’s edit buffer sub-menu.
Login Accounts Login Accounts 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 Administrator account is admin. The Diagnostics login also has full access to all switch functions plus a special sub-menu with a set of switching module tests. The initial login name for Diagnostics is diag. The User login has read-only privileges to the switch.
Multiple User Sessions Listing Other Users 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. SESSION 3 4 USER READ admin 000000008007fffd (123.456.78.910) rrtest1 000000008007fffd (123.456.78.
Multiple User Sessions Communicating with Other Users 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. The switch would then display Enter message. (End with CTRL-D or 'exit') Everything you type now will by sent to the user connected on the console port until you press CTRL-D or enter exit on a line by itself.
Multiple User Sessions 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 to cancel. Trying...............................................................................
Multiple User Sessions Advanced 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. In addition, this option will end the user’s sessions without waiting for him to press . This option can be used to log off a user with the write privilege who forgot to log out and then gain the write privilege for yourself.
UI Table Filtering (Using Search and Filter Commands) UI Table Filtering (Using Search 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. The user can locate specific information in these large tables through the More? UI prompt.
UI Table Filtering (Using Search and Filter Commands) The Search 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). The first line containing the pattern is brought to the top of the page, followed by any remaining lines in the table. Searches cannot be limited to a specific column or heading.
UI Table Filtering (Using Search and Filter Commands) 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 . A screen similar to the following will be displayed: Searching ........
UI Table Filtering (Using Search and Filter Commands) 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). Once the Filter command has been executed, the Filter mode remains active until the end of the UI table has been reached, or until the user exits the current UI table. Like the Search command, the Filter command cannot be limited to a specific column or heading.
UI Table Filtering (Using Search and Filter Commands) 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 . A screen similar to the following will be displayed: Filtering ....... 2 /1 2 /1 /% /Lne /Lne /1 /2 1 111 1 1 Note that only those lines containing Lane services are now displayed on the screen.
UI Table Filtering (Using Search and Filter Commands) 1. Type ipr and press . A table similar to the following will be displayed: IP ROUTING TABLE ----------------------------128 routes in routing table Group:VLAN Network Mask Gateway Metric Id Protocol -------------------------------------------------------------------------------------------------------------------------155.5.0.0 255.255.0.0 155.5.4.33 1 1:5 DIRECT 155.6.0.0 255.255.0.0 155.6.4.33 1 1:6 DIRECT 155.155.0.0 255.255.0.0 155.155.4.
UI Table Filtering (Using Search and Filter Commands) 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.206.2 Press . A screen similar to the following is displayed: Filtering and Searching ... 198.206.200.0 255.255.255.0 198.206.201.0 255.255.255.0 198.206.202.0 255.255.255.0 198.206.
UI Table Filtering (Using Search and Filter Commands) Single Characters A question mark (?) is used as a wildcard for a single character in a text pattern. For example, the Search pattern f/127.?.0.1 will locate the first line in a UI table containing 127. followed by any single character, and then the remaining text pattern .0.1. For example: 127.0.0.1.
UI Table Filtering (Using Search and Filter Commands) Page 4-46
5 Installing Switch Software 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. The method you use depends on your hardware configuration and the condition of the switch. These methods are: • FTP Server - The Omni Switch/Router has a built-in FTP server. If you have FTP client software, you can FTP to the switch and load new software.
Using FTP Server Using 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 software package. The following are general instructions on how to FTP to the switch. 1. You will need to configure the IP address in the switch. If you have not done this, refer to the Getting Started Guide that came with your switch. 2.
Using FTP Client Using 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. 2. The system will prompt for a host. It saves the last host name or IP address used. If it’s the one you want, press or enter the new address. 3.
Using ZMODEM Using 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. If the switch is up and running, you can use the File commands to load software. • You have deleted the image software files in the switch.
Using ZMODEM Using 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. If there is no software available in the switch, then it cannot boot until you reload the software. Using ZMODEM with the boot prompt is similar to using it with the load command.
Using ZMODEM 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. You can perform many of the functions that the MPX software does; however, the purpose of these commands are to reload software in order to get the switch up and running. To see a list of the boot commands, type ? at the [boot]: prompt.
Using ZMODEM Starting a ZMODEM Transfer 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 ‘.’ = clear field; ‘-’ = go to previous field; ^D = quit Boot device : zm 2. Type zm at this prompt. You will be prompted for more parameters. Just hit to accept the defaults. Boot file : /flash/mpx.img Local SLIP adr : Startup script: /flash/mpx.
Using ZMODEM Page 5-8
6 Configuring Management Processor Modules The management processor module (MPX on the Omni Switch/Router) coordinates control of the Omni Switch/Router by providing access to the User Interface (UI) software, maintaining user configuration information, downloading switching module software, managing basic bridge functions, maintaining basic routing functions, and managing the SNMP management agent.
Changing Serial Port Communication Parameters Changing Serial Port Communication Parameters The serial communications parameters for the two MPX ports are set by default to the following: • • • • 9600 bits per second (bps) 8 data bits 1 stop bit no parity To change the serial port configuration parameters, follow the steps below: 1. Log into the switch. For instructions on logging in, see your Getting Started Guide. 2. At the system prompt, type ser. 3.
Changing Serial Port Communication Parameters Enter the port mode and press . 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 carefully. See Configuring the Modem Port on page 6-3 for further information. ♦ Important Note ♦ You cannot configure the console port as an auxiliary port (AuxConsole). 9.
Changing Serial Port Communication Parameters 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. If you could not use the modem port for some reason, you would have to reboot the switch to get back, or—if the cable connection were the problem—use a cross-over cable to connect through a PC.
Configuring the Ethernet Management Port Configuring the Ethernet Management Port 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. Ethernet Port Configuration 1) Port Admin status UP 2) IP Address 3) Subnet Mask 4) Bcast Address 5) Gateway Address 6) Remote Host Address 7) RIP Mode : Yes : 198.206.184.175 : 255.255.255.0 : 198.206.184.255 : 198.206.184.
Configuring the Ethernet Management Port 2) IP Address Enter an IP address for the Ethernet management port in dotted decimal or hexadecimal notation (the default is 192.168.11.1). For example, to change the Ethernet management port’s IP address to 198.206.184.170, enter 2=198.206.184.170 at the prompt. ♦ Note ♦ This IP address must not be on the same subnet as any other IP router on the switch. 3) Subnet Mask Enter an IP subnet mask in dotted decimal or hexadecimal notation (the default is 255.255.255.0).
Ethernet Management Ports and Redundant Management Processor Modules Ethernet Management Ports and Redundant Management Processor 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. If both EMPs are plugged into the same subnet, the UI will show that there are duplicate IP addresses on the network.
Ethernet Management Ports and Redundant Management Processor Modules 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 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. Displaying MPX Redundancy You can display the number of MPXs, their location in the switch, and the MPX redundancy configuration of the switch by entering mpm at the system prompt.
The MPM Command/Menu 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. Command mpmget takeover Redundancy Menu Get file from Primary MPM Become Primary All of the mpm commands are described in the sections that follow. Using MPM Commands with Software Release 3.2 and Later In Release 3.
Listing the Secondary MPX Files 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. The following is a typical example. /flash/esm.img /flash/mesm.img /flash/mpm.img /flash/rav.img /flash/mpm.cnf /flash/mpm.log /flash/mpm.cfg /flash/mpm.cmd /flash/gated.
Replacing a File on the Secondary MPX 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 described in Removing a File from the Secondary MPX on page 6-13, and mpmstore, which is described in Transferring a File to the Secondary MPX on page 6-11. To use this command, enter mpmreplace, followed by a space, a slash (/), the name of the flash directory, another slash (/), and the name of the file you want to replace.
Removing a File from the Secondary MPX Removing 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. ♦ Note ♦ You can only remove a single file with the mpmrm command. You cannot use wildcards to remove multiple files. For example, to remove the file mpm.
Giving Up Control to the Secondary MPX Giving Up Control 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. You must be logged into the primary MPX to use this command. If you are logged into the secondary MPX, use the takeover command, which is described in Gaining Control from the Primary MPX on page 6-18.
Setting Automatic Config Synchronization Setting Automatic 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. This means that when the configuration file (mpm.cfg) is updated in the primary MPX, it will automatically be updated in the secondary MPX, keeping the two MPXs in sync.
Synchronizing Configuration Data Synchronizing 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. For example, to copy the configuration file from the primary MPX to the secondary MPX, you would enter configsync at the system prompt. Something similar to the following will be displayed.
Loading a File From the Primary MPX Loading a File From the Primary MPX The mpmget command loads a file from the primary MPX and copies it into the secondary MPX. This command is only available and can only be run from a secondary MPX. To use this command, enter mpmget, followed by a space, a slash (/), the name of the flash directory, another slash (/), and the name of the file you want to transfer. For example, to load the file mpm.
Gaining Control from the Primary MPX Gaining Control 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. If you are logged into the primary MPX, use the renounce command, which is described in Giving Up Control to the Secondary MPX on page 614.
Resetting a Secondary MPX 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. To reset a secondary MPX, enter secreset at the system prompt. Messages similar to the following will display: Module 1 changed while Swap OFF Syncing configuration data with secondary 1 ..
Displaying and Setting the Swap State Displaying and Setting the Swap 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. Therefore, the swap state should only be turned on when you want to hot swap modules. See Chapter 3, “Omni Switch/Router Switching Modules,” for instructions on hot swapping a switching module.
Displaying and Setting the Swap State 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 performance of the switch can be adversely affected if the swap mode is enabled. To turn the swap mode off immediately, enter swap off at the system prompt. The swap mode will be disabled and something similar to the following will be displayed.
Displaying and Setting the Swap State Page 6-22
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. Through the User Interface (UI), you can load, copy, and delete any of these files types. In addition, the UI has commands for displaying, creating, and editing ASCII (text-based) files.
Displaying the Current Directory Displaying the Current 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 corresponding directory information will be displayed: /flash Configuration and Log File Generation The mpm.cnf, mpm.cfg, and mpm.log files are generated automatically by the switch and placed in flash memory during the boot process; you do not have to load them.
Listing Switch Files 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 mpm.log mpx.img esx.img mpm.cfg mpm.cnf 18 18072 1573617 24289 1024 32768 05/30/98 13:04 06/15/98 17:57 06/18/98 12:16 06/18/98 12:18 01/01/70 00:00 06/18/98 12:27 1858057 bytes free.
Deleting Switch Files 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.log, you would enter rm mpm.log at the UI prompt. The following screen will be displayed: File system compaction in progress... The switch will take a few seconds to delete the file and compact the flash memory.
Deleting Switch Files 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 .img extension). ♦ Important ♦ You should only use the imgcl command during network down times and when you are connected to the switch through the serial port. To use this command, enter imgcl at the system prompt.
Copying System Files Copying 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 original file you want to copy, and then by the name that you wish to give the duplicate file. For example, to make a duplicate of the file mpx.cmd that is to be called mpx.bak, enter cp mpx.cmd mpx.bak at the system prompt. The following information will be displayed: /flash/mpx.
Editing Text Files Editing Text 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. If verbose mode is enabled, the following list of commands will be displayed automatically. If verbose mode is disabled, press the question mark (?) to display the following list of commands.
Editing Text Files Loading an ASCII File into the Text 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. For example, to edit the mpx.cmd file, enter rb mpx.cmd at the system prompt. ♦ Loading Binary Files ♦ You can load a binary file into the Edit buffer but you will not be able to edit it.
Editing Text Files Deleting a Line of Text from the Text 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. For example, to delete the third line of text in the text buffer, enter db 3 at the system prompt. Enter the lb command again to view the contents of the buffer. Note that the text that appeared at line 3 has been deleted.
Editing Text Files Creating a File Name for the Text Buffer If no file name has been created for the text buffer, the following message is displayed whenever the lb command is executed: Work buffer is unnamed Use the nb command to create a name for the text buffer. To use this command, enter nb, followed by the name you wish to give the text buffer. For example, if you want to name the buffer mpx.cmd, enter nb mpx.cmd at the system prompt.
Real-World Examples Real-World Examples As noted on page 10-7, when you edit text files, you will normally use several of the Edit submenu commands to produce the results you want. The following two examples, Real-World Example 1 and Real-World Example 2, are actual multi-command procedures that you may encounter as you work with your switch. Real-World Example 1 cp mpx.cmd mpx.bak rb mpx.cmd lb 00: cmDoDump=1 01: cmInit nb mpx.cmd Work buffer name is: /flash/mpx.
Real-World Examples Real-World 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.cmd wb /flash/mpx.cmd exists in /flash. Overwrite it? (y) File system compaction in progress... view mpx.
System Menu System 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. If verbose mode is disabled, press the question mark (?) to display the following list of commands. (For information on enabling verbose mode, refer to the uic command description in Chapter 4, “The User Interface.
Checking the Flash File System Checking the Flash File System 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. The command also provides diagnostic information in the event of file corruption. To perform a file system check of flash memory, enter fsck at the system prompt.
Creating a New File System Creating a New 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. To create a new file system and re-initialize the flash memory, enter newfs at the system prompt. The following will be displayed.
Creating a New File System Page 7-16
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 Changing Passwords The switch provides three types of login accounts by default—Administrator, User and Diagnostics. The Administrator login provides full READ/WRITE access to all command families. The login name for the Administrator account is admin. The login name for the default User account is user and provides READ ONLY access to the switch’s command families except for the global family, and NO WRITE privileges.
Rebooting the Switch 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 information has been saved first. Note that the reboot command is only available to the admin and the diag logins. ♦ Caution ♦ Rebooting the switch will disconnect a Telnet connection to the User Interface and will interrupt the network connections on the switching modules.
Secure Switch Access Secure 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. Filter points operate on IP protocols that include FTP, Telnet, SNMP, TFTP, HTTP, and a custom IP protocol.
Secure Switch Access 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.b.c.d] ) : Enter MAC Address ( [XXYYZZ: AABBCC] ) : Is this MAC in Canonical or Non-Canonical (C or N) [C] : Enter Slot : Enter Port : After you have created a filter, the information is automatically saved in the secure access database, and the secdefine submenu re-displays.
Secure Switch Access 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. For example: Source IP Source MAC Slot Port Filter Name Address Address # # ----------------------------------------------------------------------------------------------------------Test ANY 10.2.8.13 5 2 Enter IP Address ( [a.b.c.
Secure Switch Access Configuring Secure Access Filter Points 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 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. Disabled indicates that secure access is not enabled for FTP services, and all users can access the switch through FTP. 2) Telnet Security Indicates whether or not secure access is enabled for Telnet service on the switch.
Secure Switch Access 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. If you wish to set a different value for Telnet Security, for example, enter the line number for Telnet, followed by an equal sign (=) and the new value.
Secure Switch Access Viewing Secure 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.” To view the secure access violations log, enter seclog The following is a sample display: Secure Access Violations Log Time -----------------------12:49:02 03:15:34 Protocol ------------FTP Telnet Source IP -------------172.23.8.
Managing User Login Accounts Managing User 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. Software release 4.4 contains a partition management feature that enhances the privilege capability with an authorization scheme based on the functional capacity assigned to each user.
Managing User Login Accounts 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. If you are logged into an account with the WRITE privilege to the USER command you may create or delete login accounts as described in this section. You may also create new user accounts.
Managing User Login Accounts Adding a User Account Using the CLI Command Mode To add a user account from the CLI mode, you must be logged into an account with administrative privileges. Enter the following at the command prompt. user user_name where user_name is the new user login account name and user_password is the new user login account password. Both these values are specified by the user.
Managing User Login Accounts User Write Privileges To assign privileges to a user account, you must be logged into an account with WRITE privileges to the USER family of commands. Enter the following command at the system prompt. user userId [write list-of-families] where userId indicates the name assigned to the user account for which you want to assign READ and WRITE privileges.
Managing User Login Accounts 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. • To create a new user login account, use the following command: user user_name [password user-password] where user_name is the new user login account name and user-password is the new user password. Both these values are defined by the user.
Managing User Login Accounts Assigning Account Privileges Using 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. To add privileges to a user account, you must be logged into an account with administrative privileges. From the system prompt enter the usermod command.
Managing User Login Accounts 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. To set WRITE privileges for a single family of commands, enter 1 and press .
Managing User Login Accounts Command Family Table Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Command Family Configuration Group IP Routing IPX Routing Bridge SNMP QOS Policy HRE Filter ATM Service WAN CSM PNNI ATM Accounting Voice Over IP MPOA MPLS (unsupported) User The global family contains commands that apply globally to the switch rather than to individual applications or services.
Managing User Login Accounts Global Family Table Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Global Family System Status Slot Timeout Prompt Define Prefix Reboot Telnet FTP Ping Swap Reset CD LS RM File Interface Ethernet Gated UI 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. NO 1.
Managing User Login Accounts Modifying a User 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. A prompt similar to the following displays: Enter Username: ( ) : 2. Enter the name assigned to the user account you want to modify. A screen similar to the following displays where the account name is TechPubs1.
9 Configuring Switch-Wide Parameters 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 Displaying the MIB-II System Group Variables 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. To display the MIB-II system group variables, enter ss at the system prompt. A screen similar to the following will be displayed. System description: Alcatel Omni Switch/Router System Object ID: 1.3.6.1.4.1.800.3.1.1.2.
Displaying the Chassis Summary 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: Chassis ID: Description: Backplane: Master MPM Serial No.: Physical Changes: Logical Changes: Number of Resets: Base MAC Address: Free Slots: Omni Switch/Router XFRAME 9-slot Alcatel DESCRIPTION NOT SET. 5 SLOT 52601675 7 0 26 00:20:da:02:04:80 0 The fields displayed by the sc command are described below. Type.
Displaying Current Router Interface Status Displaying Current Router Interface Status To display current interface status information, enter si at the system prompt. A screen similar to the following will be displayed.
System Menu System 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 to display the commands in the system menu, as shown below.
Displaying Basic System Information Displaying Basic System 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 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. In addition, it also displays whether automatic configuration synchronization is enabled.
Setting the System Date and Time Setting the System 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. To view or make changes to date, time, time zone, and DST for the switch, enter dt at the System prompt.
Setting the System Date and Time 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. The local time remains active for all User Interface commands and other subsystems that require the local time.
Setting the System Date and Time 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. at 2:00 a.m. Last Sunday in March at 3:00 a.m. 1:00 GST Guam +10:00 No default No default No default ACST Australia Central Time +9:30 Last Sunday in Oct.
Setting the System Date and Time 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 West Africa -1:00 No default No default No default ZM2 No standard name -2:00 No default No default No default ZM3 No standard name -3:00 No default No default No default NST Newfoundland -3:30 1st Sunday in April at 2:00 a.m. Last Sunday in Oct. at 2:00 a.m.
Setting the System Date and Time 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. To set the month when DST should start, enter the sequential number of the month (January=1, February=2, . . . December=12).
Setting the System Date and Time 46) DST End Week Indicates which week in a month DST ends. To set the week DST should end, enter the sequential number of the week. The possible values are 1st (1), 2nd (2), 3rd (3), 4th (4), and Last. For example, if you want DST to end on the last Tuesday of a month, you would enter the line number for DST End Week (46) and the week, as follows: 46=Last 47) DST End Day Indicates which day of the week DST ends.
Viewing Slot Data Viewing 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. You can also view information on all slots in the switch at the same time in a table. To view data, for all slots in the switch, enter slot at the system prompt. A table similar to the following will be displayed.
Viewing System Statistics Viewing 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. System Uptime MPM Transmit Overruns MPM Receive Overruns MPM total memory MPM free memory MPM CPU Utilization ( 5 sec) MPM CPU Utilization ( 60 sec) Power Supply 1 State Power Supply 2 State Temperature Sensor 1 days, 12:09:22.
Clearing System Statistics Clearing System 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 Viewing Task Utilization Statistics The taskstat command displays the task utilization statistics of the switch. To display the task utilization statistics, enter taskstat at the system prompt. The is an optional number of tasks and the is an optional sample period of 1 to 60 seconds. You must enter the if you want to enter the .
Viewing Task Utilization Statistics 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. ERRNO. DELAY. Page 9-18 Error number indicator. The time elapsed between task routines.
Viewing Memory Utilization Viewing 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. To start the utility, enter leakstart at the system prompt.
Viewing MPX Memory Statistics Viewing 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. To view the MPX’s memory statistics, enter memstat at the system prompt. A screen similar to the following will be displayed.
Checking the Flash File System Checking the Flash File System 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. It also provides diagnostics in the case of file corruption. To perform a file system check of flash memory, enter fsck at the system prompt. A screen similar to the following will be displayed.
Creating a New File System Creating a New 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. You can use this command when you want to reload all files in the file system from a readily-accessible backup device or in the unlikely event that the flash file system becomes corrupted. ♦ Important Note♦ Before you execute the newfs command you should preserve your configuration file by saving it to another host.
Configuring System Information Configuring System 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. To enter or modify the switch descriptions, perform the following steps. 1.
Viewing CAM Information Viewing 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. Something similar to the following will be displayed.
Configuring CAM Distribution 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. See Viewing CAM Information on page 9-24 for more information on the camstat command. The Omni Switch/Router supports approximately 31.25 K of usable CAM among all the switching modules in a chassis.
Configuring CAM Distribution 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. For this reason, you may want to configure the CAM for all modules in this system. Reboot the system and check the updated CAM configurations through the camstat command.
Configuring the HRE-X Router Port Configuring the HRE-X Router Port Various services in the switch use the HRE-X router port MAC registers. The registers are allocated as the services are loaded at startup. The hrex submenu contains five commands for use with the Hardware Routing Engines (HREs). The hrexassign command allows you to configure the switch so that registers are reserved for particular services. The hrexdisplay command allows you to view your current configuration.
Configuring the HRE-X Router Port 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. As indicated on the screen, the register assignment will not take effect until the switch is rebooted. If you use the hrexdisplay command after making a the register assignment shown in the above example, a screen similar to the following is displayed.
Configuring the HRE-X Router Port Configuring and Displaying the HRE-X Hash Table The HRE-Xs 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 environments. In rare cases, you may want to change the hash table configuration to optimize it for your particular data flow. This should be done with care because the data population will change over time.
Duplicate MAC Address Support Duplicate MAC Address 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. It sends one trap for a device move within the same Group and another trap for a device move outside of the home Group. A station move trap is normally sent after an actual station move.
Duplicate MAC Address Support 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 destination address is located. If duplicate MAC addresses are treated as separate addresses, then the same MAC address may have to be stored in the CAM of multiple switching modules, not just the module that originally learned the address.
Multicast Claiming 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. When multicast claiming is enabled, the switch “claims” destination multicast addresses and places them in the CAMs of all switching modules in the switch. You can enable multicast claiming by adding the following line to the mpx.
Saving Configurations Saving Configurations 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. When you use the UI to enter multiple configurations, periodically the switch will display the following message. File system compaction in progress . . .
Saving Configurations 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 following messages. Cache Configuration is currently on. or Cache Configuration is currently off. To turn off the cache configuration mode, enter the following command at the system prompt. cacheconfig off The following message will display. File system compaction in progress . . .
10 Switch Logging Logging Overview 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. To enter the logging submenu, enter logging at the system prompt.
Configuring the Syslog Parameters Configuring the Syslog Parameters 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. The syslog command allows you to control how these messages will be handled. You can designate what kinds of messages you will see and where the messages will be sent.
Configuring the Syslog Parameters 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. The default is local0.
Configuring the Syslog Parameters Syslog Priority Codes Level Value Meaning LOG_EMERG 0 FATAL system event LOG_ALERT 1 FATAL subsystem event LOG_CRIT 2 Problem, subsystem unstable LOG_ERR 3 Problem, bad event, recoverable LOG_WARNING 4 Unexpected, non-fatal event LOG_NOTICE 5 normal but significant condition LOG_INFO 6 info LOG_DEBUG 7 Internal debug messages Override internals This field will force all syslog messages to use the default priority mask specified instead of their o
Configuring the Syslog Parameters Log Task ID Determines whether or not you want to see the task ID that can be included in the syslog message. Use Task Name This allows the user to display descriptive task names for syslog messages (see the Display sub-menu above) instead of numeric codes. internals Message tag Text of up to 10 characters that is added to every message leaving the switch. It is useful when multiple switches send messages to the same host.
Configuring Switch Logging Configuring Switch Logging Switch logging is a feature that allows you to activate and configure the logging of various types of switch information. Once you activate logging for a specific facility through the switch logging command, you may also decide whether the log output should display on the console, be saved to a file, or be both displayed and saved to a file. To enter the switch logging submenu, enter swlogc at the system prompt.
Configuring Switch Logging 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. To disable flash file logging, enter 3=disable. Flash file logging messages cannot be saved in the mpm.log file, but flash file logging messages may be displayed on the console by entering 31=yes.
Configuring Switch Logging 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 sending log messages to this file. (This option is not available for flash file logging or screen capture.) Output to Console Set to yes to display the log messages on the console screen.
Displaying the Command History Entries in the MPM Log 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). To display this data, enter cmdlog at the system prompt. The following is a sample display. User ----------admin admin admin admin admin admin admin Line ----------------------198.206.187.113 198.206.187.113 198.
Displaying the Connection Entries in the MPM Log 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). To display this data, enter conlog at the system prompt. A screen similar to the following will be displayed.
Displaying Screen (Console) Capture Entries in the MPM Log Displaying Screen (Console) Capture Entries in the MPM Log The caplog command displays the screen capture entries in the mpm.log file. (Note: This feature is not yet implemented.) In order to view screen capture entries through this command, you must first enable the Screen Capture log facility through the swlogc command (see Configuring Switch Logging on page 10-6). To display screen capture entries in the log, enter caplog at the system prompt.
Displaying Screen (Console) Capture Entries in the MPM Log 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. 6) Telnet (3). session.
Displaying Debug Entries in the MPM Log 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
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. With the health statistics, the user can set specific threshold levels for consumable resources in the switch. Such resources include bandwidth capacity, CAM and CPU usage, and RAM memory usage.
Setting Resource Thresholds Setting Resource 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. To set the threshold level for a switch’s consumable resources, enter the hdcfg command at the system prompt.
Setting Resource Thresholds Setting Bandwidth Thresholds Bandwidth is a measure of the amount of traffic a switch can handle for receiving, sending, and on the backplane. The health statistics allow you to sent a percentage of available bandwidth, at which an SNMP trap is generated to alert the network administrator that the threshold has been exceeded. To set the threshold levels for switch bandwidth: 1. Enter health at a system prompt. The health menu (described above) displays. 2.
Setting Resource Thresholds 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.e., data enters a module port and is transmitted from a port on the same module) is employed, the backplane threshold reading will not be correct.
Setting Resource Thresholds 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. For the switch level, the CAM threshold separately monitors the MPX and the HRE-X daughtercard (if it is installed) CAM tables. For the module level, it monitors the switching module CAM tables. CAM thresholds are not available on the port level.
View Switch-Level Statistics Setting the Sampling Interval 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. Enter health at a system prompt. The health menu (described above) displays. 2. Enter a 3 at the health menu prompt. The following menu displays: Resource Monitoring Interval Configuration 1) Sampling Interval :5 3.
View Module-Level Statistics 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. If a single packet is sent through a port, for example, the receive resource usage is represented as one percent. The following section describes the statistics displayed using the hdstat command.
View Port-Level Statistics 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. View Port-Level Statistics To view port-level statistics, type the hpstat command at a system prompt as shown: hpstat / where is the slot number and is the port number.
12 Network Time Protocol Introduction 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. It provides client time accuracies within a millisecond on LANs, and up to a few tens of milliseconds on WANs relative to a primary server synchronized to Coordinated Universal Time (UTC) (via a Global Positioning Service receiver, for example).
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.) An NTP client or server connected to a stratum 1 source would be stratum 2. A client or server connected to a stratum 2 machine would be stratum 3, and so on, as demonstrated in the diagram below.
Time Source (UTC) 1a NTP Servers 1b Stratum 1 Peer Association 2b 2a NTP Client/ Servers Stratum 2 Peer Association Stratum 3 3b 3a NTP Clients Peer Association 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.
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 the same stratum), unless the latter is receiving time updates from a source that has a lower stratum then from where the former is receiving time updates. This minimizes common points of failure. • Peer associations should only be configured between servers at the same stratum level.
Network Time Protocol Management Menu Network Time Protocol 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 NTP Configuration 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 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. The default is 8000 milliseconds. 2) Authentication delay This field sets a specified time interval that is added to timestamps included in requests to the server that required authentication.
NTP Configuration Menu 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 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. Setting this field to 0 allows an unlimited number of clients to connect to the server. 62) Client limit period This field allows you to set the client limit time period (in seconds).
NTP Configuration Menu 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: = For example, to change the Response timeout to 10, you would enter 1 (the line number for Response timeout), an equal sign (=), and the number 10 (the new value), as shown: 1=10 3. Enable authentication by entering a 3, and equal sign (=), and a key file name at the prompt, as shown: 3=ntp.
NTP Configuration Menu Field Descriptions The following section describes the expanded menu options. 31) Configuration info authentication key The number of the key in the key file used to authenticate configuration information. Configuration information sets configuration parameters. For more information on the key file, see NTP and Authentication on page 12-4. 32) Control request authentication key The number of the key in the key file used authenticate control requests.
NTP Configuration Menu Configuring a New Peer Association When you have configured the NTP client and/or server, you will need to set at least one peer association for the switch. An NTP peer is a machine of the same stratum that will compare and check time information sent from the switch, and in turn send time information to the switch.
NTP Configuration Menu Configuring a New Server For the switch to synchronize its time, you must specify a server, or servers, from which the switch receives time information. This is done with the ntpaddserv command. To add a synchronization server to a switch, use the command that follows: ntpaddserv
[] [prefer] where is the either the domain name or IP address of the server. The optional configuration items are described below: .NTP Configuration Menu 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 . A brief message appears confirming the addition of a new server. Unconfigure Existing Peer Associations You can remove server, peer, or reference clock associations for this switch using the ntpuncommand.
NTP Information Menu 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 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. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not be synchronized by the peer. Broadcast (5) A host operating in this mode sends periodic messages regardless of the reachability state or stratum of the peers.
NTP Information Menu 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 0.0.0.0, then the local address has yet to be determined. remote association. If this address is St. The stratum level of the remote peer. If this number is 16, the remote peer has not been synchronized. Poll. The polling interval, in seconds. Reach.
NTP Information Menu Display Detailed Information for One or More Peers The ntpshowpeer command allows you to view detailed NTP information about any remote associations of this switch. To view detailed NTP information about a remote association enter the ntpshowpeer command in the following manner: ntpshowpeer
where is the either the domain name or IP address of the remote association. For example, to show information for a peer with IP address 1.1.1.4, enter: ntpshowpeer 1.1.1.NTP Information Menu 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. Leap. The status of leap second insertion for this association. Leap seconds are seconds that are added to the timestamp of an NTP entity to correct accumulated time errors. The possible values are: 00 No warning.
NTP Information Menu 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. If the local clock has never been synchronized, the value is zero. Originate Timestamp. This is the local time, in timestamp format, of the peer when its last NTP message was sent.
NTP Information Menu 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. A screen similar to the following is shown: system peer: system peer mode: leap indicator: stratum: precision: root distance: root dispersion: reference ID: reference time: system flags: frequency: stability: broadcastdelay: authdelay: 0.0.0.0 unspec 11 16 -7 0.
NTP Information Menu 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. Frequency. A number indicating the local clock’s frequency in relation to a reference clock’s Pulse per Second (PPS). If the clock is running in perfect synchronization, this number should be 1.
NTP Statistics Menu 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 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. bad stratum in packet. The number of NTP packets received that had a corrupted stratum bit in the data of the packet. old version packets.
NTP Statistics Menu 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 address is 0.0.0.0, then the local address has yet to by NTP to the remote association. If this be determined. time last received. The number of seconds since the last NTP message packet was received from another NTP entity in the network.
NTP Statistics Menu 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. To view the statistics of the loop filter, enter the ntploop command at the system prompt. A screen similar to the following is shown: offset: frequency: poll adjust: watchdog timer: 0.000000 s 0.
NTP Statistics Menu calls to findpeer. The number of times the switch sent an NTP packet of any kind to a configured NTP association. new peer allocations. The number of new NTP associations created since the last restart. peer demobilizations. The number NTP associations lost since the last restart. hash table counts. The number of peer tables hashed to the index.
NTP Statistics Menu Display Event Timer Subsystem 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. A screen similar to the following is displayed: time since reset: alarms handled: alarm overruns: calls to transmit: 0 0 0 0 Field Descriptions The following section describes the fields displayed using the ntptimer command. time since reset.
NTP Statistics Menu 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.1.1.5, you would enter: ntppreset 1.1.1.4 1.1.1.5 A brief message is displayed confirming the command.
NTP Statistics Menu 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. bad version packets. The number of packets received where the version number of NTP was undefinable. This is usually caused by packet corruption. data in pkt too short.
NTP Statistics Menu 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. leap happened. The date of the last leap second insertion. Turn the Server's Monitoring Facility On or Off The Server Monitoring Facility keeps track of all NTP association for this switch.
NTP Statistics Menu 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. ♦ Note ♦ This is the TCP and UDP definition of a port, not a switch interface port. local address. The local interface address for this association as created by the NTP configuration on the switch. count. m.
NTP Administration Menu NTP Administration 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 Specify the Host Whose NTP Server We Talk To 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). To change the NTP server for the switch, enter the ntphost command as shown: ntphost
where is the either the domain name or IP address of the NTP server. For example, to configure the switch to use an NTP server with an IP address of 1.1.1.NTP Administration Menu Set Key Type to Use 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. To specify an encryption type enter the ntpkeytype command as shown: ntpkeytype where is either DES or MD5.
NTP Access Control Menu NTP Access 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 Change the Control Message Authentication Key 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 fashion. It is possible to change the authentication key identifier for control messages sent from the switch to another NTP entity. To change the authentication key ID, enter the ntpctlk command as shown: ntpctlk where is the new key ID.
NTP Access Control Menu Remove One or More Key ID's from the Trusted List The trusted list in the key file is a list of all keys that are considered authentic and uncompromised. Messages from an NTP entity using one of these keys are accepted and acted upon. It is possible to remove a key from the trusted list. To remove a key ID from the trusted list, enter the ntpdkey command as shown: ntpdkey where is the new key ID to be remove from the trusted list.
NTP Access Control Menu Create Restrict Entry/Add Flags to Entry It is possible to place restriction flags on specific NTP entities in relation to the switch. Restriction flags prevent messages or information coming from the NTP entity from affecting the switch.
NTP Access Control Menu 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.). Only the first client limit hosts that have shown up at the server and that have been active during the last client limit period (in seconds) are accepted. Requests from other clients from the same net are rejected. Only time request packets are taken into account.
NTP Access Control Menu Remove Flags from a Restrict Entry It is possible to place restriction flags on specific NTP entities in relation to the switch. Restriction flags prevent messages or information coming from the NTP entity from affecting the switch.
NTP Access Control Menu Display the Traps 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.0.0.1, port 18447 interface: 0.0.0.5, configured set for 0 seconds, last set 0 seconds ago sequence 1, number of resets 1 Field Descriptions The following section describes the fields shown with the ntpvtrap command. address. port.
13 SNMP (Simple Network Management Protocol) Introduction 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. Network administrators use SNMP to monitor network performance and to solve network problems. An SNMP-managed network is comprised of three fundamental parts: agents, managed devices, and network management systems (NMSs).
Configuring SNMP Parameters and Traps Configuring SNMP Parameters and Traps 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. The snmpc command is listed under the Networking menu. For more information about the networking menu, see Chapter 25, “IP Routing.
Configuring SNMP Parameters and Traps 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. If you want to specify a Set Community Name password, enter a 2, an equal sign (=), and the new Set Community Name.
Configuring SNMP Parameters and Traps 6) Broadcast Traps 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. The default for broadcast traps is disabled. To enable broadcast traps, enter the following command: 5=enabled The following prompt displays: UDP destination port (162): Enter the UDP destination port for the traps.
Configuring SNMP Parameters and Traps Here is a sample configuration for setting a combination of traps.
Configuring SNMP Parameters and Traps 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. Without special access, an NMS can only update its own entry. If you choose the default, no, simply press at the prompt. Save your configuration by typing save and then . f.
Configuring SNMP Parameters and Traps 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 configuration and re-enter the snmpc command at the prompt, the screen refreshes to include the new NMS entry.
Configuring SNMP Parameters and Traps 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. It also displays a list of the current traps. The snmps command is listed on the Networking menu. For more information about the networking menu, see Chapter 25, “IP Routing.
Configuring SNMP Parameters and Traps Bad Type Discards The total number of SNMP entries discarded because the request type was not recognized. ASN Parse Errors The total number of ASN.1 or BER errors encountered by the SNMP protocols entity when decoding received SNMP Messages. Too Big Errors The total number of SNMP PDUs delivered to the SNMP protocol entity with a value in the error-status field of ‘tooBig’.
Configuring SNMP Parameters and Traps Get Next Requests The total number of SNMP Get-Next PDUs accepted and processed by the switch SNMP protocol entity. Set Requests The total number of SNMP Set-Request PDUs which have been accepted and processed by the switch SNMP protocol entity. Get Responses The total number of SNMP Response PDUs accepted and processed by the switch SNMP protocol entity.
Trap Tables Trap Tables The following table is a summary list of the supported SNMP traps and their values. Trap or Mask Name Object ID Bit Position Hex Value Page coldStart 1.3.6.1.2.1.11.0 (word 0) 0 (word 0) 1 13-15 warmStart 1.3.6.1.2.1.11.1 (word 0) 1 (word 0) 2 13-16 linkDown 1.3.6.1.2.1.11.2 (word 0) 2 (word 0) 4 13-16 linkUp 1.3.6.1.2.1.11.3 (word 0) 3 (word 0) 8 13-17 authentication failure 1.3.6.1.2.1.11.4 (word 0) 4 (word 0) 10 13-17 egpNeighborLoss 1.3.6.1.2.1.11.
Trap Tables Trap or Mask Name Object ID Bit Position Hex Value Page 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.1.800.3.1.1.4.0.4 (word 1) 3 (word 1) 8 13-30 loginViolation 1.3.6.1.4.1.800.3.1.1.4.0.5 (word 1) 4 (word 1) 10 13-31 macVlanViolation 1.3.6.1.4.1.800.3.1.1.4.0.
Trap Tables Trap or Mask Name Object ID Bit Position Hex Value Page 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.3.6.1.4.1.800.3.1.1.4.0.40 (word 2) 7 (word 2) 80 13-55 xylanXIPXMAPPort StatusChange 1.3.6.1.4.1.800.3.1.1.4.0.
Trap Tables Trap or Mask Name Object ID Bit Position Hex Value Page Under1Event 1.3.6.1.4.1.800.3.1.1.4.0.88 (word 3) 23 (word 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 (word 3) 25 (word 3) 200 0000 13-80 Over3Alarm 1.3.6.1.4.1.800.3.1.1.4.0.91 (word 3) 26 (word 3) 400 0000 13-80 Under3Event 1.3.6.1.4.1.800.3.1.1.4.0.92 (word 3) 27 (word 3) 8000 0000 13-81 NoDeviceAlarm 1.3.6.1.4.1.
Trap Tables SNMP Standard Traps 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. The object name of the trap as it is defined in the corresponding MIB (Management Information Base). Alcatel supports standardized and proprietary MIBS. Object ID. The SNMP object identifier (OID) for this trap. Description.
Trap Tables 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. Bit Position (Word 0) 1 Hex Value (Word 0) 2 Trap Text and Variable Descriptions Warm Start Trap linkDown Object ID 1.3.6.1.2.1.11.2 Description The sending protocol entity recognizes a failure in one of the communication links represented in the agent’s configuration.
Trap Tables 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 (Word 0) 3 Hex Value (Word 0) 8 Trap Text and Variable Descriptions Link Up (port 1) Port Index. The physical port number that identifies where the communication link has come up. Trap authenticationFailure Object ID 1.3.6.1.2.1.11.
Trap Tables Trap egpNeighborLoss 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 (Word 0) 5 Hex Value (Word 0) 20 Trap Text and Variable Descriptions Neighbor Loss (neigh addr 192.168.10.1) Neighbor IP Address. The IP address of this entry’s EGP neighbor. Trap frDLCIStatusChange Object ID 1.3.6.1.2.1.11.
Trap Tables Trap ipxTrapCircuitDown 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 (Word 0) 8 Hex Value (Word 0) 100 Variable Description ipxCircSysInstance - The identifier of this instance of IPX. ipxCircIndex - The identifier of this circuit, for this instance Trap ipxTrapCircuitUp Object ID 1.3.6.1.4.1.23.2.5.5.2 Description This trap indicates that the specified circuit has come up.
Trap Tables Trap topologyChange Object ID 1.3.6.1.2.1.17.0.2 Description A bridge’s configured ports either transitioned from Learning state to Forwarding state or from Forwarding state to Blocking state. This trap will not be sent if a newRoot trap was sent for the same transition. Bit Position (Word 0) 11 Hex Value (Word 0) 800 Trap Text and Variable Descriptions Page 13-20 Spanning Tree: A configured port’s state has transitioned.
Trap Tables Trap atmfVpcChange 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. Bit Position (Word 0) 12 Hex Value (Word 0) 1000 Trap Text and Variable Descriptions A permanent VPC has been added or deleted at this ATM Interface, or the attributes of an existing VPC have been modified (index 0, Vpi 2, Status 3) Port Index. The port number of this ATM interface. Valid values range from 0 to 2147483647.
Trap Tables Trap atmfVccChange 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. Bit Position (Word 0) 13 Hex Value (Word 0) 2000 Trap Text and Variable Descriptions A permanent VCC has been added or deleted at this ATM Interface, or the attributes of an existing VPC have been modified (index 0, Vpi 2, Vci 6, status 3) Operational Status . The present operational status of the VCC.
Trap Tables 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 Ethernet statistics group as defined by RFC 1757) has exceeded its rising threshold. The variable’s rising threshold and whether it will generate an SNMP trap for this condition are configured by a network management station running RMON. Bit Position (Word 0) 14 Hex Value (Word 0) 4000 Trap Text and Variable Descriptions Variable.
Trap Tables 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 Ethernet statistics group as defined by RFC 1757) has dipped below its falling threshold. The variable’s falling threshold and whether it will generate an SNMP trap for this condition are configured by a network management station running RMON. Bit Position (Word 0) 15 Hex Value (Word 0) 8000 Trap Text and Variable Descriptions Variable.
Trap Tables Trap Type dsx3LineStatusChange Object ID 1.3.6.1.2.1.10.30.15.0.1 Description The value of an instance dsx3LineStatus changed. Bit Position (Word 0) 16 Hex Value (Word 1) 1 0000 Trap Text and Variable Descriptions Line Status Change (line status 1, last change 4) DSX3 Line Status. The line status of the interface. It contains loopback, failure, received alarm, and transmitted alarm information. Valid values range from 1 to 8191. Last Change.
Trap Tables Trap dsx1LineStatusChange Object ID 1.3.6.1.2.1.10.18.15.0.1 Description The value of an instance dsx1LineStatus changed. Bit Position (Word 0) 17 Hex Value (Word 1) 2 0000 Trap Text and Variable Descriptions Line Status Change (line status 1, last change 2) DSX1 Line Status. The line status of the interface. It contains loopback, failure, received alarm, and transmitted alarm information. Valid values range from 1 to 8191. Last Change.
Trap Tables Extended Traps 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. These sensors are physically located on the MPX module, but can detect temperature changes throughout the chassis.
Trap Tables 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. In some cases, this trap may also be generated when a module is reset. Bit Position (Word 1) 1 Hex Value (Word 1) 2 Trap Text and Variable Descriptions Module was inserted or removed from chassis (slot 4, subunit 1, type 10) Slot Number . The slot number on the front of the chassis where this module was inserted or removed. Submodule Type.
Trap Tables 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. Bit Position (Word 1) 2 Hex Value (Word 1) 4 Trap Text and Variable Descriptions Power Supply was inserted or removed from chassis or has a problem (ps1 3, ps2 2) Power Supply Status.
Trap Tables Trap Type controllerEvent 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 (Word 1) 3 Hex Value (Word 1) 8 Trap Text and Variable Descriptions Chassis controller (MPX) lost or gained master control (slot 1, state 3) Slot . The slot number of the MPX that has lost or gained master control. Valid values are: 1 Slot Number 1 2 Slot Number 2 State . The current state of the MPX in the slot.
Trap Tables Trap Type loginViolation 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. Bit Position (Word 1) 4 Hex Value (Word 1) 10 Trap Text and Variable Descriptions Login Attempt failed due to invalid ID or password. Trap Type macVlanViolation Object ID 1.3.6.1.4.1.800.3.1.1.4.0.
Trap Tables Trap Type macDuplicatePort 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 different from the port where the frame previously was received although they both ports belong to the same VLAN. Bit Position (Word 1) 6 Hex Value (Word 1) 40 Trap Text and Variable Descriptions VLAN Receiving Port has changed (bridge address 00145221cd02) MAC Address.
Trap Tables 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. And if you enable a logical port, such as an ATM service, associated virtual ports will be enabled.
Trap Tables 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 disabled through the UI or Switch Manager. Note that if you disable a physical port, any associated logical and virtual ports will also be disabled. And if you disable a logical port, such as an ATM service, associated virtual ports will also be disabled.
Trap Tables 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 Trap Type portRecordMismatch 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. Typically this trap is generated when a NIC of one type is swapped for a different type (i.e., Ethernet for FDDI, ATM for Token Ring, etc.). Bit Position (Word 1) 10 Hex Value (Word 1) 400 Trap Text and Variable Descriptions Port configuration different than previously detected (slot 2, IF 2, type 203, instance 1) Slot number .
Trap Tables Trap Type groupChange 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 (Word 1) 13 Hex Value (Word 1) 2000 Trap Text and Variable Descriptions Group created or deleted (vlan 2 admin status 4) Group number. The Group number that has been created or deleted. Administrative Status . The administrative status for this group. Possible options are: 1 Disabled. All ports in this Group are disabled.
Trap Tables 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 (Word 1) 14 Hex Value (Word 1) 4000 Trap Text and Variable Descriptions VLAN Change created or deleted (group 2, admin status 4) Group number. The Group number to which this VLAN belongs. Administrative status. The administrative sta- tus are 1 2 3 4 5 Page 13-38 for this VLAN. The following integers valid values: Enabled.
Trap Tables 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. Bit Position (Word 1) 15 Hex Value (Word 1) 8000 Trap Text and Variable Descriptions Port VLAN, group or configuration change (slot 2, IF 8, type 4, instance 1) Slot number . The slot number for the module that contains this port. Port number. The port number on this module that was changed. Port Type. The physical type of this port.
Trap Tables Trap moduleResetReload 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. A reload may occur during a firmware download. Bit Position (Word 1) 16 Hex Value (Word 1) 1 0000 Trap Text and Variable Descriptions Submodule Type. Indicates the submodule that was reset or reloaded. Typically this value will be 1, meaning the base module was reset or reloaded. If this value is 2, then HSX module 1 was affected.
Trap Tables 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 (Word 1) 17 Hex Value (Word 1) 2 0000 Trap Text and Variable Descriptions Potentially fatal error occurred (trap 10) Event Trap Type . A number that identifies the specific error that occurred in the system.
Trap Tables Trap Type vlanRouteTableFull 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 Position (Word 1) 18 Hex Value (Word 1) 4 0000 Trap Text and Variable Descriptions IP or IPX route table is full on insertion. Trap Type sapTableFull Object ID 1.3.6.1.4.1.800.3.1.1.4.0.20 Description The SAP table is full upon insertion.
Trap Tables Trap Type atmSSCOPstate Object ID 1.3.6.1.4.1.800.3.1.1.4.0.21 Description A specified port changed. Bit Position (Word 1) 20 Hex Value (Word 1) 10 0000 Trap Text and Variable Descriptions Signalling state changed (slot 3 port 1) S l o t n u m b e r . The slot number where this ASM module is located. Port number . The port number on this ASM module where the signalling state has changed. Trap Type ilmiState Object ID 1.3.6.1.4.1.800.3.1.1.4.0.
Trap Tables 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 (Word 1) 22 Hex Value (Word 1) 40 0000 Trap Text and Variable Descriptions ATM VCC created or deleted (slot 3, port 1, Vpi 0, Vci 100, admin status 2) Slot Number . The slot number where this ASM module is located. Port Number. The port number on the ASM module where this VCC was created or deleted. VPI Number .
Trap Tables Trap Type atmService 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 Emulation, etc.) was created or deleted. Bit Position (Word 1) 23 Hex Value (Word 1) 80 0000 Trap Text and Variable Descriptions ATM service created or deleted (slot 3, port 1, service 2, admin status 2) Slot Number . The slot number where this ASM module is located. Port Number.
Trap Tables 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 (Word 1) 26 Hex Value (Word 1) 400 0000 Trap Text and Variable Descriptions Frame Relay DLCI created (slot 3 port 1 DLCI Number 100) S l o t n u m b e r . The slot number where this Frame Relay module is located. Port number . The port number on this Frame Relay module where the DLCI was created. DLCI Number. The number of the DLCI that was created.
Trap Tables 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 (Word 1) 27 Hex Value (Word 1) 800 0000 Trap Text and Variable Descriptions Frame Relay DLCI deleted (slot 3 port 1 DLCI Number 100) S l o t n u m b e r . The slot number where this Frame Relay module is located. Port number . The port number on this Frame Relay module where the DLCI was deleted. DLCI number. The number of the DLCI that was just deleted.
Trap Tables 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 (Word 1) 28 Hex Value (Word 1) 1000 0000 Trap Text and Variable Descriptions Frame Relay DLCI Changed to Active (slot 3 port 1 DLCI Number 100) Slot Number . The slot number where this Frame Relay module is located. Port Number . The port number on this Frame Relay module where the DLCI was activated. DLCI Number.
Trap Tables 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 (Word 1) 29 Hex Value (Word 1) 2000 0000 Trap Text and Variable Descriptions Frame Relay DLCI Changed to Inactive (slot 3 port 1 DLCI Number 100) Slot Number . The slot number where this Frame Relay module is located. Port Number . The port number on this Frame Relay module where the DLCI was de-activated. DLCI Number.
Trap Tables Trap Type portManualForwardingMode 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. Bit Position (Word 1) 30 Hex Value (Word 1) 4000 0000 Trap Text and Variable Descriptions Slot Number . The slot number Port number . The port number on the module. where this port is located. Port placed into manual mode forwarding (slot 3, port 1, type 1, instance 1 Port Type . The physical type of this port.
Trap Tables Trap Type fddiCFStateChange 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. Bit Position (Word 1) 31 Hex Value (Word 1) 8000 0000 Trap Text and Variable Descriptions FDDI physical port changes from wrap configuration state (index 1, state 2) SMT Index. A unique value for each SMT (Station Management Station).
Trap Tables Trap Type duplicateIPaddress 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 (Word 2) 2 Hex Value (Word 2) 4 Trap Text and Variable Descriptions IP Address. The IP address of the station that reported the duplicate IP address. MAC Address. The MAC address of the station that reported the duplicate IP address. Duplicate IP address detected (IP addr 192.168.10.
Trap Tables Trap Type duplicateMACaddress 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. Bit Position (Word 2) 3 Hex Value (Word 2) 8 Trap Text and Variable Descriptions Duplicate MAC address detected (Mac 00145221cd02, slot 2, IF 3, time 4 MAC Address . The router port’s MAC address for which the last duplicate S l o t . The slot MAC address was detected. number where the duplicate MAC address was last received.
Trap Tables Trap Type healthThresholdRising 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 (Word 2) 4 Hex Value (Word 2) 10 Trap Text and Variable Descriptions Thresh-hold rising trap Trap Type healthThresholdFalling Object ID 1.3.6.1.4.1.800.3.1.1.4.0.38 Description At least one of the user-specified thresholds was exceeded during the previous cycle and none of them are exceeded in the current cycle.
Trap Tables Trap Type healthThresholdDevice 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 (Word 2) 6 Hex Value (Word 2) 40 Trap Text and Variable Descriptions Device-level threshold crossing is detected (Data 0a 09 0d 53 00 00 00 00 00 00 00 00 00 00 00 00) Data . An octet string that represents the contents of device-level rising/falling threshold trap. Trap Type healthThresholdModule Object ID 1.3.6.1.4.1.
Trap Tables Trap Type xylanXIPXMAPPortStatusChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.41 Description An XMAP turned on or off. Bit Position (Word 2) 8 Hex Value (Word 2) 100 Trap Text and Variable Descriptions The status of an XMAP-tracked virtual port has changed (port 1, reason 2) Port Number. The virtual port number of the port that most recently changed. Reason. The reason for the last port status change. The following integers are valid values: 0 No trap was sent. 1 A port was added.
Trap Tables Trap Type xylanXIPXMAPPortStateChange Object ID 1.3.6.1.4.1.800.3.1.1.4.0.42 Description An XMAP turned on or off. Bit Position (Word 2) 9 Hex Value (Word 2) 200 Trap Text and Variable Descriptions The state of the XMAP agent has changed to (state 1) Operating State . The XMAP’s operating state.
Trap Tables 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 (Word 2) 16 Hex Value (Word 2) 1 0000 Trap Text and Variable Descriptions User. The last user who made an authen- tication attempt. The last VLAN authentication attempt was: (user 1, event 2, MAC 0036589adf01, port 4, slot 5) Event Type. The last authorizaMAC Address. The last MAC address to make an authentication attempt. tion attempt type.
Trap Tables Trap Type xylanXIPGMAPFailedUpdate 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. Bit Position (Word 2) 11 Hex Value (Word 2) 800 Trap Text and Variable Descriptions Reason. The reason for the last GMAP update was not applied. The following integers are valid values: 1 The target group is an authenticated group. 2 The update would conflict with a binding rule.
Trap Tables Trap Type clkBusLineStateChange 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. Bit Position (Word 2) 10 Hex Value (Word 2) 400 Trap Text and Variable Descriptions Bus Line’s status changed (bus line 1, operating state 1) or clock switching has occurred. Operating State. The bus line’s Bus Line. The specific bus line where the status change occurred.
Trap Tables 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 (Word 2) 23 Hex Value (Word 2) 80 0000 Trap Text and Variable Descriptions IP Address. The IP address for which this binding is configured. VLAN ID . The VLAN ID for which this rule is configured. Group ID . The group ID of the VLAN for which this rule is configured. A binding rule has been violated (groupId 1, vlanId 2, IP 192.168.10.
Trap Tables Trap Type mpcStatisticsOverflow Object ID 1.3.6.1.4.1.800.3.1.1.4.0.47 Description An entry in the mpcStatisticsTable reached the threshold value. Bit Position (Word 2) 18 Hex Value (Word 2) 4 0000 Trap Text and Variable Descriptions MPC: Statistics threshold value reached (MpcIndex, Insufficient resources replies.) MPC Index. A unique number that identi- fies a conceptual row in the mpcConfigTable. Insufficient resources replies.
Trap Tables Trap Type fddiLerFlagChange 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 (Word 3) 0 Hex Value (Word 3) 1 Trap Text and Variable Descriptions FDDI: Link Error Rate on a port is set (SMTIndex 1, port 2, LerFlag 3) SMT Index . A unique value for each SMT (Station Management).
Trap Tables Trap Type fddiLCTFailCntIncr Object ID 1.3.6.1.4.1.800.3.1.1.1.0.66 Description The LCT (Link Confidence Test) flag on a port incremented. Bit Position (Word 3) 1 Hex Value (Word 3) 2 Trap Text and Variable Descriptions Fddi: Link Confidence Test flag on a port incremented (SMTIndex 1, port index 2, failure counts 3 Port Index . A unique value for each port within a given SMT, which is the same as the corresponding resource index in SMT.
Trap Tables Trap Type mpcStatisticsOverflow Object ID 1.3.6.1.4.1.800.3.1.1.1.0.67 Description The statisticsNum value of the mpcStatisticsTable reached the threshold value. Bit Position (Word 2) 18 Hex Value (Word 2) 4 0000 Variables mpcIndex mpcStatRxMpoaResolveReplyInsufECResources Trap Text and Variable Descriptions GMAP is unable to update the forwarding database (index 1, MPOA replies 3) MPC Index . A unique number that identifies a conceptual row in the mpcConfigTable.
Trap Tables 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. Bit Position (Word 2) 19 Hex Value (Word 2) 8 0000 Variables mpcRowStatus lecControlDirectVci mpcFlowDetectProtocol mpcIngressCacheDestAddr, mpcIngressCacheDestAtmAddr mpcIndex mpcMpsIndex Trap Text and Variable Descriptions Row Status . This object allows creation and deletion of MPOA clients.
Trap Tables Trap Type mpcIngressRetryTimeOut 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 (Word 2) 20 Hex Value (Word 2) 10 0000 Variables mpcIndex mpcRetryTimeMaximum mpcIngressCacheDestAddr mpcIngressCacheDestAtmAddr mpcFlowDetectProtocol mpcMpsIndex Trap Text and Variable Descriptions Maximum Retry MPC Index. A unique number that identi- Time. The MPC-p5 fies a conceptual row in the mpcConfig- cumulative maximum value for Table.
Trap Tables Trap Type vrrpTrapNewMaster 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. Bit Position (Word 2) 21 Hex Value (Word 2) 20 0000 Trap Text and Variable Descriptions Agent has transitioned from Backup to Master state (If index 1, vrid 2) Interface Index Number . A unique value that identifies the sending agent. Virtual Router ID . The number that identifies the virtual router on this VRRP.
Trap Tables Trap Type vrrpAuthFailure 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 authentication type conflicts with this router’s authentication key or type. Bit Position (Word 2) 22 Hex Value (Word 2) 40 0000 Trap Text and Variable Descriptions A packet with a wrong authentication key or type is received (If index 1, vrid 2, source 192.168.10.1, error type 3) Interface Index Number . A unique Packet Source IP.
Trap Tables 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 (Word 3) 10 Hex Value (Word 3) 400 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex xylanOamF5VCVciIndex Trap Text and Variable Descriptions The specified connection is in VC-AIS state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables 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 (Word 3) 11 Hex Value (Word 3) 800 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex xylanOamF5VCVciIndex Trap Text and Variable Descriptions The specified connection is in VC-RDI state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables Trap Type oamVCLOC 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 (Word 3) 12 Hex Value (Word 3) 1000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex xylanOamF5VCVciIndex Trap Text and Variable Descriptions The specified connection is in VC-LOC state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables 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. Bit Position (Word 3) 13 Hex Value (Word 3) 2000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex xylanOamF5VCVciIndex Trap Text and Variable Descriptions The specified connection is in VC-UnsuccessLoop state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables Trap Type oamVPAIS 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 (Word 3) 14 Hex Value (Word 3) 4000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex Trap Text and Variable Descriptions The specified connection is in VP-AIS state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number . The port number for the specified connection. VPI .
Trap Tables 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 (Word 3) 15 Hex Value (Word 3) 8000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex Trap Text and Variable Descriptions The specified connection is in VP-LOC state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number . The port number for the specified connection. VPI .
Trap Tables Trap Type oamVPLOC 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 (Word 3) 16 Hex Value (Word 3) 1 0000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex Trap Text and Variable Descriptions The specified connection is in VPUnsuccessLoop state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables 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. Bit Position (Word 3) 17 Hex Value (Word 3) 2 0000 Variables xylanOamF5VCSlotIndex xylanOamF5VCPortIndex xylanOamF5VCVpiIndex Trap Text and Variable Descriptions The specified connection is in VP-RDI state. (Slot 1, Port 2, VPI 2, VCI 1) Slot Number. The slot number for the specified connection. Port Number .
Trap Tables 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 (Word 3) 21 Hex Value (Word 3) 20 0000 Variable Description chasAccountName - Path name of the most recently terminated account- ing file. chasAccountFileCount - The number of terminated accounting files await- ing collection and removal by an external accounting collection agent.
Trap Tables 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 threshold. This event is for information only. Bit Position (Word 3) 23 Hex Value (Word 3) 80 0000 Variable Description - The amount of buffer taken up by accounting data. Value shown as a percentage of the buffer size. chasAccountThreshold1 - The first filling level of the intermediate storage area for accounting data.
Trap Tables 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 second threshold. Bit Position (Word 3) 25 Hex Value (Word 3) 200 0000 Variable Description - The amount of buffer taken up by accounting data. Value shown as a percentage of the buffer size. chasAccountThreshold2 - The second filling level of the intermediate storage area for accounting data. Crossing this threshold generates a warning.
Trap Tables 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 (Word 3) 27 Hex Value (Word 3) 8000 0000 Variable Description - The amount of buffer taken up by accounting data. Value shown as a percentage of the buffer size. chasAccountThreshold3 - The third filling level of the intermediate storage area for accounting data. Crossing this threshold generates a warning.
Trap Tables 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. Bit Position (Word 3) 29 Hex Value (Word 3) 2000 0000 Variable Description chasAccountFileCount - The number of terminated accounting files await- Trap Type fantrayEvent Object ID 1.3.6.1.4.1.800.3.1.1.4.0.1 Description A fantrayEvent trap occurs when a problem condition is recognized on a chassis fan tray.
Trap Tables Trap Type ldpPeerCreate 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. Bit Position (Word 3) 5 Hex Value (Word 3) 20 Variables mplsLdpEntityID mplsLpdPeerIndex mplsLdpPeerID Trap Text and Variable Descriptions Peer Entity is Created. (EntityId 1, PeerIndex 2, PeerId 3) EntityId . The identification number assigned to the new entity. PeerIndex . The index number assigned to the peer. PeerId.
Trap Tables Trap Type ldpPeerDelete 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 (Word 3) 6 Hex Value (Word 3) 40 Variables mplsLdpEntityID mplsLpdPeerIndex mplsLdpPeerID Trap Text and Variable Descriptions Peer Entity is Deleted. (EntityId 1, PeerIndex 2, PeerId 3) EntityId . The identification number of the deleted entity. PeerIndex. The index number of the deleted peer. PeerId.
Trap Tables Trap Type ldpSessionCreate 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 created. Bit Position (Word 3) 17 Hex Value (Word 3) 80 Variables mplsLdpEntityID mplsLpdPeerIndex mplsLdpPeerID mplsLdpSessionIndex Trap Text and Variable Descriptions LDP Session Created. (EntityId 1, PeerIndex 2, PeerId 3, Session Id 4) EntityId . The identification number assigned to the newentity. PeerIndex.
Trap Tables 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. Bit Position (Word 3) 8 Hex Value (Word 3) 100 Variables mplsLdpEntityID mplsLpdPeerIndex mplsLdpPeerID mplsLdpSessionIndex Trap Text and Variable Descriptions LDP Session Deleted. (EntityId 1, PeerIndex 2, PeerId 3, Session Id 4) EntityId. The identification number of the deleted entity. PeerIndex.
Trap Tables Trap Type lecStateChangeEvent 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 Trap Text and Variable Descriptions Service Instance. The specific instance of E L A N N a m e . The name of the ELAN whose status changed to generate this trap. this service. In most cases this value will be 1 but an ATM port may have multiple instances LEC Status Change (ELAN Name, Service Instance, New state, previous state). New State. The new, current status of the LEC that changed to generate this trap. Displayed as an integer as shown below in the State List. State List 1. 2. 3. 4.
14 DNS Resolver and RMON Introduction 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. The commands for these features are available from the Networking submenu, which is described in Chapter 25, “IP Routing.” Configuring the DNS Resolver The Names Submenu The Names command takes you to the Names submenu.
Configuring the DNS Resolver To enable the resolver function, enter 1=y. A screen similar to the following then displays: DNS Resolver Configuration 1) Resolver Enabled 2) Domain 3) Server Address 1 4) Server Address 2 5) Server Address 3 : Yes : UNSET : UNSET : UNSET : UNSET Command {Item=Value/?/Help/Quit/Redraw/Save} (Redraw) : The prompts allow you to enter a Domain Name and up to three Domain Name Servers (identified by their IP addresses).
Remote Network Monitoring (RMON) Remote Network Monitoring (RMON) Remote Network Monitoring (RMON) allows you to set up remote monitoring within your Omni Switch/Router. RMON consists of “probes” and “events.” There are two commands in the Networking menu, probes and events, which you can use to monitor, activate and inactivate probes and events. Be aware that you cannot create probes from within the switch’s User Interface; to do so requires a network application such as HP ProbeView.
Remote Network Monitoring (RMON) 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. However, if the variable moves back inside the limit, then out again, another alarm will not be generated unless the opposite limit is exceeded.
Remote Network Monitoring (RMON) Time Time since the last change in status. System Resources 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 Configuring Router Port MAC Addresses 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. To use this command, enter chngmac followed by the number of the group you want to modify (the default group number is 1). ♦ Important Note ♦ You must add chngmacFlag=1 to the end of the mpx.cmd file and then reboot the switch to use the chngmac command.
15 Managing Ethernet Modules Overview 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 Ethernet modules. For documentation on Command Line Interface (CLI) commands to manage Ethernet modules, see the Text-Based Configuration CLI Reference Guide. ♦ Important Notes ♦ In Release 4.
Overview of Omni Switch/Router Ethernet Modules Variety 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. On the Omni Switch/Router, 10/100 Ethernet modules use copper RJ-45 connectors and the ESX-100FM/FS12W Fast Ethernet module uses fiber MT-RJ connectors.
Overview of Omni Switch/Router Ethernet Modules Kodiak Ethernet Modules Ethernet Module (Chassis Type) Speed Supported (per port) Software Configurable? Commands Available OmniChannel Supported? ESX-K-100C-32W (Omni Switch/Router) 10/100 Mbs Yes 10/100cfg 10/100vc Yes ESX-K-100FM/FS-16W (Omni Switch/Router) 100 Mbs Yes 10/100cfg 10/100vc Yes GSX-K-FM/FS-2W (Omni Switch/Router) 1000 Mbs Yes 10/100cfg 10/100vc No ESX-K Series Modules and Optimized Ports Kodiak-based modules will flood pa
The Ethernet Management Menus The Ethernet Management Menus The eth100 and 10/100 sub-menus are described in this chapter.
Configuring 10/100 Auto-Sensing Ports Configuring 10/100 Auto-Sensing Ports 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. Follow these steps to configure a 10/100 port: 1. Enter 10/100cfg at the system prompt and press . 2.
Configuring 10/100 Auto-Sensing Ports 6. Since you have enabled auto-negotiation, the port will automatically sense the line speed of the connection. You can also further enable auto-negotiation for the link mode. When the following prompt displays: Link Mode [Half or Auto] (Currently (H)alf Duplex) : select whether you want the port to auto-sense the duplex mode (Auto) or whether you want the port to default to half-duplex mode (Half). Enter an A for auto-sensing or enter an H for half-duplex.
Configuring Kodiak Ethernet Ports Configuring Kodiak Ethernet Ports 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. Follow these steps to configure a Kodiak Ethernet port: 1. Enter 10/100cfg at the system prompt and press . 2.
Viewing Configurations for 10/100 Ethernet Modules Viewing 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. Ethernet 10/100 ports (e.g., ESX-K-100C-32) can auto-sense the connection speed of the attached device.
OmniChannel 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 operates within Spanning Tree as one virtual port, and can provide up to 800 Mbps (in full-duplex mode) of bandwidth. (In full-duplex mode, 400 Mbps is supported in each direction of the OmniChannel.
OmniChannel ♦ 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. The first MAC address learned will transmit and receive data on the first link.
OmniChannel 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. • Each Server Channel can support up to 4 ports. • Within one Server Channel, all of channel ports must be on the same slot. • Within one Server Channel, all of channel ports must be in one VLAN.
OmniChannel 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. For eg. 2/1 is used to select Physical Port 1 on Slot 2 Secondary Slot/Port: Enter the other ports that will be used in this OmniChannel.
OmniChannel Adding Ports 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. Follow these steps: 1. Enter addprtchnl. 2. The following prompt displays: Channel Number : Enter the channel number to which you want to add secondary ports.
OmniChannel Deleting Ports 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. You can check the current port assignments for a given OmniChannel by using the chnlinfo command, which is described in Viewing OmniChannel Parameters on page 15-14. 3.
OmniChannel 3. A screen similar to the following displays: Displaying channel 2 Channel Id Phy. Port Port Status Mac Count ===================================================================== 2 5/6 5/7 Inactive Inactive 0 0 3 5/3 5/4 5/5 Active Active Active 35 34 34 The following sections describe the variables in this table. Channel Id. The identification number assigned to this OmniChannel during the crechnl configuration procedure. Phy. Port.
OmniChannel Page 15-16
16 Managing 802.1Q Groups This chapter documents User Interface (UI) commands to manage 802.1Q groups. For documentation on Command Line Interface (CLI) commands to manage 802.1Q groups, see the Text-Based Configuration CLI Reference Guide. ♦ Important Notes ♦ In Release 4.4 and later, the Omni Switch/Router is factory-configured to boot up in CLI (Command Line Interface) mode, rather than in UI (User Interface) mode.
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. This tunneling mode of operation involves the Token Ring Encapsulation Flag in the 802.1Q header. It is not set or interpreted in the Alcatel Omni S/R implementation.
Application Example The following diagram illustrates a simple 802.1Q application: Group 2 Group 2 E A B 12345678 123456 Switch X Groups 2 and 3 F 12345678 123456 Switch Y G C Group 3 Group 3 H D 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.1Q group (Group 2 for endstations A, B, E, and F, and Group 3 for endstations C, D, G, and H).
Single vs. Multiple Spanning Tree 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. If a network is passing both untagged and IEEE tagged frames, single spanning tree support could lead to packets being lost. Lost packets could occur if a port specifically assigned to handle one type of traffic (e.g., IEEE 802.
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. The cas, das, mas, and vas commands create, delete, modify, and view trunk services created to handle 802.1Q traffic over an Ethernet backbone.
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.1Q tagged traffic. Both types of frames can now pass through the same port. ♦ Important Notes ♦ Since a trunk is a service, and Alcatel switches have a 16 (10/100) or 15 (Gigabit) services per port limit, only 15 or 14 802.1Q groups can be added to the same port. In both cases, a default bridge service occupies one of the service slots.
Assigning an 802.1Q Group to a Port Assigning an 802.1Q Group to a Port 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. These commands were invalidated in the 4.1 release and replaced by the cas, mas, vas, and das service commands. The procedure for assigning an 802.
Assigning an 802.1Q Group to a Port Configuring 802.1Q on 10/100 Ethernet Ports Use the cas command to assign 802.1Q groups to 10/100 ports. To use this command, follow the steps below. 1. Enter cas at the system prompt, as shown: cas / where is the slot of the module, and is the port number that is to be added to the group. For example, to add port 3 on slot 5, you would enter: cas 5/3 2.
Assigning an 802.1Q Group to a Port 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. Group ID The number of the group to which the port is to be added. Tag A simple identifier that is added to 802.1Q packets for identification. This value can be any number between 1 and 4094.
Assigning an 802.1Q Group to a Port 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. When you set the Mode of the service, the cas screen changes to accommodate the selection and allows you to set the priority of the service.
Assigning an 802.1Q Group to a Port Configuring 802.1Q on Gigabit Ethernet Ports Use the cas command to assign 802.1Q groups to Gigabit ports. To use this command, follow the steps below. 1. Enter cas at the system prompt, as shown: cas / where is the slot of the module, and is the port number that is to be added to the group. For example, to add port 3 on slot 5, you would enter: cas 5/3 2.
Modifying 802.1Q Groups Modifying 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 for 10/100 Ports To modify the configuration of an 802.
Modifying 802.1Q Groups The ESX-K and GSX-K modules can also remap incoming 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. 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.
Modifying 802.1Q Groups Modifying 802.1Q Groups for Gigabit Ethernet Ports To modify the configuration of an 802.1Q group for Gigabit ports, use the mas command as shown: mas / where is the slot number of the module on the switch, is the port number where the service was created, and is the identifier for the service on this port. For example, to modify 802.
Modifying 802.1Q Groups 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. ♦ Note ♦ Tags (field number 1) do not apply if proprietary tagging is used on this port.
Viewing 802.1Q Groups in a Port Viewing 802.1Q Groups in a Port To view which ports use which 802.1Q groups, enter the vas command at the system prompt, as shown: vas / where is the slot number of the module on the switch and is the port number where the service was created. For example, to view an 802.
Viewing 802.1Q Statistics for 10/100 Ports Viewing 802.1Q Statistics for 10/100 Ports The viqs command provides a display of statistics for 802.1Q groups assigned to 10/100 ports. Enter the viqs command, as shown: viqs / where is the slot number of the module on the switch, is the port number where the service was created, and is the number of the group that the port belongs to. For example, to view an 802.
Deleting 802.1Q Groups from a Port Deleting 802.1Q Groups from a Port 802.1Q groups for both 10/100 and Gigabit Ethernet ports can be deleted using the das command. The procedure is slightly different in each case. To delete an 802.
17 Configuring Bridging Parameters 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 transparent bridging, source route bridging, or source route to transparent bridging. Bridges primarily operate at Layer 2 of the OSI reference model, which controls data flow, transmission errors, physical addressing, and access to physical medium.
• Source Route to Transparent Bridging. Used in mixed Ethernet and Token Ring environments, this protocol provides easy translation between transparent and source route bridging. A mixed ethernet and token ring environment is shown in the diagram below: SRTB Bridge Segment 1 Segment 2 Spanning tree and fast spanning tree are also used to prevent physical loops in the network from creating excess traffic by blocking packet transmission on one or more ports.
Configuration Overview Configuration Overview 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). You can select a group with the selgp command. For information on using these commands, see Selecting a Default Group on page 17-7. Step 2.
Bridge Management Menu 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 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. Commands in this section include fwt, fs, fc, bps, macinfo, macstat, macclrstat, rts, and dbrmap.
Bridge Management Menu 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 Selecting a Default Group 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. ♦ Note ♦ You can view the current groups in the switch by entering gp at any prompt.
Bridging Commands Bridging Commands The Bridge Management menu provides several commands that are useful in pinpointing problems in the network. The commands allow you to lookup specific MAC addresses and where they were learned, create and view static bridge addresses, view information on remote trunking stations, view MAC address statistics for a group or a port, or look up information on domain mappings.
Bridging Commands 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). For example, a bridge service on port 1 of slot 3 would be: 3/1/Brg/1 Services provide connection options for switches in a LAN, between LANs, or in a WAN. Other possible services include trunking, routing, and LANE.
Bridging Commands Configuring a Static Bridge Address 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. Enter the fc command as follows: fc where is the number of the group for which you want to create a static bridge MAC address.
Bridging Commands 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. Slot/Intf/Service/Inst. The slot number, interface (port) number, type of service, and service instance. For example, a bridge service on port 1 of slot 3 would be: 3/1/Brg/1 Static Status.
Bridging Commands 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 Displaying Static Bridge Addresses You can view static bridge address information by entering the fs command. To display the information, enter the fs command as follows: fs where is the number of the group for which you want to view static bridge MAC addresses.
Bridging Commands Displaying Bridge Port Statistics You can display statistics on bridge ports with the bps command. To view bridge port statistics enter the bps command as follows: bps where is the number of the group for which you want to view bridge port statistics.
Bridging Commands 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. The forwarding database holds all known MAC address for this bridge and is used to learn the next hop MAC address for the packet(s) in question. Slot/Intf/Service/Inst.
Bridging Commands Displaying Media Access Control (MAC) Information for a Specific MAC 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. To view MAC information for a specific address: 1. Enter macinfo at the system prompt and press . 2.
Bridging Commands Displaying Media Access Control (MAC) Information for all MAC 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. To view MAC information for all addresses: 1. Enter macinfo at the system prompt and press . You will be prompted with the following message: Enter MAC address ([XXYYZZ:AABBCC] or return for none): 2. Press .
Bridging Commands 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. Aged. The number of MAC addresses that have exceeded the age limit and been removed from the CAM by this slot. Learned. The number of MAC address that have been learned on this slot. in CAM.
Bridging Commands 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. For example, to list the trunking station at port 1 of slot 3, you would enter: 3/1 If you do not enter a specific slot and station, the system automatically sends information on all services for the remote trunking stations associated with this group. 3.
Bridging Commands 3. A screen similar to the following is shown: DOMAIN BRIDGE MAPPING Group 2 Destination MAC 00:20:da:7d:ef:44 00:20:da:7d:ef:45 00:20:da:7d:ef:46 Group ID 2 2 2 Age 14 120 220 Slot / Intf 8/ 1 8/ 1 8/ 1 Domain MAC 00:20:da:6c:fb:85 00:20:da:6c:fb:85 00:20:da:6c:fb:86 Field Descriptions The fields displayed by the dbrmap command are described below. Destination MAC. Group ID. Age. The destination MAC address learned from a domain bridge port. The destination MAC’s group number.
Setting Flood Limits 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. You can change this default by configuring the flood limit on a per port or a per Group basis.
Setting Flood Limits 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 where is the number of the group for which you are viewing the flood limit.
Configuring Spanning Tree Configuring Spanning Tree 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 physically configured with loops. If packets are broadcast to all ports (or flooded) in an attempt to deliver the data, networks with physical loops will rebroadcast packets repeatedly and cause a network to become severely congested.
Configuring Spanning Tree • 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. The FA for IBM Spanning Tree is programmed into the MPX CAM, and all data frames with this FA are claimed by the MPX.
Configuring Spanning Tree Configuring Spanning Tree Parameters The stc command allows you to configure parameters for the spanning tree, and enable or disable the Fast Spanning Tree feature for a VLAN. To configure these parameters: 1. Enter the stc command as follows: stc where is the number of the group in the switch for which you are configuring spanning tree. For example, to configure spanning tree for Group 2, you would enter: stc 2 2.
Configuring Spanning Tree 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 . Answering Yes (y) changes the setting of Fast Spanning Tree to the status not currently in use for this Group. ♦ Important Note ♦ Read the prompt carefully before responding.
Configuring Spanning Tree 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 to accept the default listed in parenthesis. This time value controls how fast a port changes its spanning state when moving toward the Forwarding state.
Configuring Spanning Tree Display Spanning Tree Bridge Parameters The sts command allows you to display spanning tree bridge parameters. To display spanning tree parameters, enter the sts command as shown: sts where is the number of the group in the switch for which you want to view spanning tree bridge parameters.
Configuring Spanning Tree 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. The cost of the path to the root bridge as seen from this bridge. Cost represents the distance of the group from the root bridge, in number of hops. If this is the root bridge, this number is 0. The slot number, port number, and service type of the root port.
Configuring Spanning Tree Configuring Spanning Tree Port Parameters The stpc commands allows you to configure port parameters (as opposed to bridge parameters) for spanning tree. To configure port parameters 1. Enter the stpc command as shown: stpc where is the number of the group in the switch for which you want to configure spanning tree port parameters.
Configuring Spanning Tree 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). For example, a bridge service on port 1 of slot 3 would be: 3/1/Brg/1 Services provide connection options for switches in a LAN, between LANs, or in a WAN.
Configuring Spanning Tree 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 nonToken Ring (e.g., FDDI or Ethernet) ports that do not support this IBM Spanning Tree.
Configuring Spanning Tree 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. Pri. The service type and instance of the service connected to the port. The value (from 0 to 256) of the priority of the port, 0 being the highest priority. State. The port's current state as defined by application of the spanning tree protocol.
Configuring Fast Spanning Tree Configuring Fast Spanning Tree 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. By automatically identifying and utilizing alternative secondary links, Fast Spanning Tree can rapidly converge backup connections between network devices within as little as 1 second.
Configuring Fast Spanning Tree Truncating Tree Timing & Speedy Tree Protocol Two additional enhancements are also included with the Fast Spanning Tree feature for improved performance: Truncating Tree Timing and Speedy Tree Protocol. Truncating Tree Timing Truncating Tree Timing allows Designated Ports attached to Point-to-Point links to change to Forwarding mode faster, by utilizing two extra bits in the Configuration BPDU for communication between neighboring bridges.
Configuring Fast Spanning Tree Displaying Fast Spanning Tree Port Parameters The fstps command allows you to view the current Fast Spanning Tree port parameters on a selected group or VLAN. To view the port parameters, enter the fstps command as shown: fstps where is the number of the group in the switch for which you want to view Fast Spanning Tree port parameters.
Configuring Fast Spanning Tree Role. The port’s current Role values include: role as defined by application of the fast spanning tree protocol. The 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. DESIGNATED The Designated Port on a Bridge provides an attached LAN the best path to the Root Bridge, and connects the LAN through the Bridge to the Root Bridge, forwarding frames between them.
Configuring Fast Spanning Tree Enabling Fast Spanning Tree Port Parameters The actfstps command allows you to activate Fast Spanning Tree port parameters on a selected group or VLAN. To enable Fast Spanning Tree, enter the actstps command as shown: actfstps where is the number of the group in the switch for which you want to view Fast Spanning Tree port parameters.
Configuring Fast Spanning Tree Disabling Fast Spanning Tree Port Parameters The actfstps command allows you to disable Fast Spanning Tree port parameters on a selected group or VLAN. To disable Fast Spanning Tree, enter the actstps command as shown: actfstps where is the number of the group in the switch for which you want to view Fast Spanning Tree port parameters.
Configuring Source Routing Configuring Source Routing The srs and src commands allow you to display and configure the source routing parameters for the selected group. SAP Filtering The Service Advertising Protocol (SAP) filter is a method for allowing the user to decide what type of source routed packets are allowed to be transmitted out of the switch.
Configuring Source Routing 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 . 3. The following message is displayed: Remove all SAP Filter values? (n) : Enter a y to remove the configured filters, or an n to keep configured filters, and press .
Configuring Source Routing 4. Press . 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. Excepting the default of 0000 is the same as not having a filter. 5. Press . The first permit filter prompt is displayed: Output SAP Permit Filter 1 (0000): Enter the SAP value that the first permit filter should screen.
Configuring Source Route to Transparent Bridging Configuring Source Route to Transparent 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.1d Spanning Tree), commands have been provided in the bridging menu to enable Source Route to Transparent Bridging (SRTB) on a configured group basis. It is important not to confuse SRTB with source-route transparent (SRT) bridging.
Configuring Source Route to Transparent Bridging Enabling SRTB for a Group 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 6. Once you have selected the frame type, you are returned to the menu prompt.
Configuring Source Route to Transparent Bridging Viewing the RIF Table A Routing Information Field (RIF) is stored for each MAC address learned on a token ring port. One RIF is stored for each MAC address. The maximum size of each RIF is 32 bytes (long enough to traverse 15 bridge hops) Once a RIF is learned for a MAC address, it is maintained until the MAC address is aged out of the CAM. You can view a list of RIFs using the srtbrif command. To view the RIF table follow these steps: 1.
Configuring Source Route to Transparent Bridging Clearing the RIF Table 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. To clear an entry in the RIF table: 1. Enter the srtbclrrif command at the system prompt.
Configuring Source Route to Transparent Bridging Page 17-48
18 Configuring Frame Translations Any-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. For example, an Ethernet frame onto a Token Ring. This feature is referred to as Any to Any Switching. Normally, the only way for data to get from one media type to another is via routing.
Any-to-Any Switching 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. This material is also required if you are trying to determine the applicability of any to any switching to a protocol not described in the reference material. ♦ Important Notes ♦ In Release 4.
Translating the Frame Translating the Frame 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. MAC Header RIF Encapsulation Network Header Data The Essential Parts of Frame MAC Header Consists of a source and destination address specifying the transmitting station in the broadcast domain and the intended recipient(s), as well as other media specific fields.
The MAC Header The MAC Header MAC Header RIF Encapsulation Network Header Data 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 versus Non-Canonical The first requirement of the switch transformation is the bit ordering of the address fields. For Token Ring and FDDI, this is the so called non-canonical ordering or most significant bit first.
The RIF Field The RIF Field MAC Header RIF Encapsulation Network Header Data 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. However, if you enable “RIF Stripping” you can switch source route frames with RIFs less than 2 bytes long.
Encapsulation Encapsulation MAC Header RIF Encapsulation Network Header Data 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. Additionally, the methodology of these encapsulations vary from protocol to protocol. An ideal protocol would dictate a single encapsulation which would be the same on all media.
Encapsulation The SNAP Conversion The intent of the 802.2 committee is that Ethertype frames are transformed to SNAP on crossing from Ethernet media to 802 media and restored to Ethertype in the reverse direction. The Omni Switch/Router could follow this rule for all protocols including IP; however, this would prevent AppleTalk interworking between Ethernet and FDDI. The Omni Switch/Router explicitly checks for the AppleTalk protocol. If found, the rule is not applied.
Encapsulation IPX Encapsulation Transformation 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. Novell places its network header and data within a raw IEEE 802.3 Ethernet frame with no intervening IEEE 802.2 LLC header.
The Network Header The Network Header MAC Header RIF Encapsulation Network Header Data There are essentially two requirements for the any to any switching transformation function to address the network header fields: • Network Address to MAC Address Mapping In every protocol there is a mechanism for mapping global network wide addresses to the MAC addresses required in the local broadcast domain.
The Network Header 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. The router would then use the bit swapped form in the MAC address of subsequent frames to the FDDI ring and the switch would bit swap these MAC header address as it transformed the frame onto Ethernet, resulting in the correct representation to be received by the original station.
Frame Size Requirements Frame 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. This requires that padding is inserted on frames switched to it which are below the minimum size and stripped from frames switched from it. • All media have different maximum frame size requirements.
Frame Size Requirements 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 Banyan 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. The Banyan Vines protocol only uses one frame format per network type—no user configuration of translations is necessary. This protocol uses Ethernet II frames on Ethernet, SNAP frames on FDDI, and IEEE 802.2 (LLC) frames on Token Ring.
Configuring Encapsulation Options Configuring Encapsulation Options You will configure frame encapsulation based on the destination MAC address or the destination 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. Forwarding versus Flooding Such frames will be handled in two ways: • Forwarded Frames.
Configuring Encapsulation Options “Native” versus “Non-Native” 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. Such frames are referred to as Native frames.
The User Interface The User 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. ♦ Important Note ♦ In Release 4.4 and later, the Omni Switch/Router is factory-configured to boot up in CLI (Command Line Interface) mode, rather than in UI (User Interface) mode.
The User Interface The addvp, modvp and crgp 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. Each of these represents a set of translation options for the IP and IPX protocols. The names chosen for these sets basically represent the translations for IPX with the translation for IP being implied.
The User Interface Ethernet Factory Default Translations For Ethernet switching module ports the factory default is set to the following: Ethernet Media - Default Mode No translation is performed on outbound Ethernet frames where the inbound interface was Ethernet. IP frames of any encapsulation are transmitted as Ethernet II frames. IPX frames are transmitted as IEEE 802.3 Proprietary as the default setting. The only exception is when LLC passthrough mode is enabled, then the IEEE 802.
The User Interface Token Ring Factory Default Translations For Token Ring switching module ports the factory default is set to the following: Token Ring Media - Default Mode IP of any encapsulation is encapsulated SNAP IPX encapsulations are encapsulated SNAP except for IEEE 802.2 which is forwarded as is. Banyan Vines of any type are transmitted as LLC. All other Ethertype and SNAP encapsulated protocols are sent as for IP. All other LLC encapsulated protocols are forwarded as is.
The User Interface 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. IP frames are transmitted as Ethernet II frames. All IPX frames are transmitted as Ethernet II frames. The only exception is when LLC passthrough mode is enabled, then the IEEE 802.2 (LLC) frames are forwarded as is.
The User Interface The SNAP Option This option can be applied to all media type ports and is set to the following: Ethernet Media - SNAP Mode No translation is performed on outbound Ethernet frames where the inbound interface was Ethernet. IP frames are transmitted as SNAP frames. All IPX frames are transmitted as SNAP frames. No translation is performed on Appletalk frames, and we currently support only Appletalk Phase II (SNAP format).
The User Interface ATM 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 exception is Banyan Vines frames from FDDI, which are translated to Ethertype. All other LLC frames are left as is. The exception is Banyan Vines from Token Ring, which is translated to Ethertype.
The User Interface The LLC Option This option can be applied to all media type ports and is set to the following: Ethernet Media - LLC Mode No translation is performed on outbound Ethernet frames where the inbound interface was Ethernet. IP frames are transmitted as Ethernet II frames. All IPX frames are transmitted as IEEE 802.2 (LLC) frames. No translation is performed on Appletalk frames, and we currently support only Appletalk Phase II (SNAP format).
The User Interface ATM LANE - LLC Mode IPX frames are translated to 802.2 LLC. All other SNAP frames from FDDI, Token Ring, and Ethernet SNAP are translated to Ethertype. However, Appletalk ARP SNAP frames from Token Ring and FDDI are left as SNAP; Banyan Vines frames from FDDI are translated to Ethertype. All other LLC frames are not translated.
The Switch Menu 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. If you are in verbose mode, the following screen is displayed.
The Switch Menu Default Ethernet Translations 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. All Ethernet ports currently set to default will inherit these new translation options. It will thenreset the forwarding table translation options for all addresses learnt on those ports to those port defaults.
The Switch Menu Default FDDI Translations 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. All FDDI ports currently set to default will inherit these new translation options. It will thenreset the forwarding table translation options for all addresses learnt on those ports to those port defaults.
The Switch Menu ♦ 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.3 frames, which referred to as “FDDI raw.” The fddidef command will accept your input and will not return an error message if you try to change an IPX translation option to Ethertype or Ethernet 802.3.
The Switch Menu 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.2 or LLC 3 Ethernet 802.3 For example, if you wanted to translate incoming IPX SNAP frames to LLC frame, then you would enter 6=2 4. When you are done changing translations, enter save to save all of your settings.
The Switch Menu Port Translations 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 translations to all ports for a particular media type, swch applies translations only to the port you specify. To specify translation for a single port: 1.
The Switch Menu 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. Ethernet ports allow all frame translation options, but FDDI and Token Ring ports have limitations. See Default FDDI Translations on page 18-27 and Default Token Ring Translations on page 18-28 for more information on media limitations.
The Switch Menu 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 Transmitted Good Octets Received Bad Octets 0 Total Octets 0 Received Unicasts 0 Transmitted Unicasts Received Multicasts 0 Transmitted Multicasts Received Broadcasts 0 Transmitted Broadcasts Received Buffer Discards 0 Transmitted Buffer Discards Received Collision Count 0 Transmitted Retry Count Received Runt Count 0 Transmit
The Switch Menu Transmitted Broadcasts. The number of frames transmitted on this port whose destination address is the broadcast address. Note that these statistics merely indicate the format of the destination address of frames transmitted/received on this port, not that the addressed device and/or devices necessarily reside on that port. For example, unknown unicast addressed frames are flooded to many ports. Received Buffer Discards.
The Switch Menu 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., stations should always collide within 64 bytes due to propagation times.
The Switch Menu Displaying Token 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.g., TSM-CD-16W, TSX-CD-16W, and TSX-C-32W). For example, if you want to display the switch statistics for a Token Ring port on Port 1 on Slot 4, enter: swch 4/1 at the system prompt. Press r and then press at the prompt.
The Switch Menu 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. Tx Unicast Packets. The number of packets transmitted on this port whose destination address is a unicast format. Rx Multicast Packets.
The Switch Menu 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. Internal Errors. The total number of times this port detects a recoverable internal error. Line Errors. The total number of errors caused by problems with the physical links (code violations, Frame Check Sequence (FCS) errors inside a frame). Burst Errors.
The Switch Menu 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. Received 512_1023 byte Pkts. The total number of packets received on this port that were at least 512 bytes (octets) long and less than or equal to 1023 bytes long. Received 1024_2047 byte Pkts. The total number of packets received on this port that were at least 1024 bytes (octets) long and less than or equal to 2047 bytes long.
The Switch Menu Any to Any MAC Translations 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. Enter the MAC for which you want to view translations. The following prompt displays: Is this MAC in Canonical or Non-Canonical (C or N) [C] : 3.
The Switch Menu 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. Normally all devices attached to a switch port receive frames translated according to the translation options defined for that port. However, some devices attached to the same port may require different frame formats.
Translational Bridging Translational Bridging Translational Bridging enables internetworking between FDDI, Ethernet, and Token Ring LANs. There is no standard which encompasses this. The Omni Switch/Router’s features focus on bridging of frames between media and translating the MAC and LLC headers into the appropriate “native” frame formats. This provides media-independent internetworking.
Dissimilar LAN Switching Capabilities 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. To fully explain the various changes possible we need to define the portion of the frame where changes could occur. Media Specific fields and MAC address fields are different for Token Ring, FDDI, and Ethernet.
Dissimilar LAN Switching Capabilities Switching Between Ethernet LANs Across a Trunked Backbone Frames that are switched between like media across a Trunked backbone will only be translated at the egress port of the egress Omni Switch/Router. For example in the figure below, frames switched from Station A to Station B will be translated at point 4, where point 4 is the egress port of Switch 2.
Dissimilar LAN Switching Capabilities Switching Between Similar LANs across a Native Backbone Switched traffic between similar LANs across a non-trunked or native backbone will have translations performed at each egress point. In the figure below, for traffic originating from Station A destined to Station B, point 1 represents the ingress (input) port of Switch 1.
Dissimilar LAN Switching Capabilities 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. This table is representative of the IP and IPX protocol only.
Dissimilar LAN Switching Capabilities Page 18-46
19 Managing Groups and Ports In a traditional hub-based network, a broadcast domain is confined to a single network interface, such as Ethernet, or even a specific physical location, such as a department or building floor. In a switch-based network, such as one comprised on Omni Switch/Routers, (OmniS/Rs) a broadcast domain—or Group— can span multiple physical switches and can include ports using multiple network interfaces.
How Ports Are Assigned to Groups How Ports Are Assigned to Groups 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. The two methods are described in this section.
How Ports Are Assigned to Groups How Dynamic Port Assignment Works Initially each port is assigned to the default Group. In this example, all three ports have workstations that belong to three different IP subnets (130.0.0.0, 138.0.0.0, and 140.0.0.0). All three ports start out in the default Group. Group Mobility examines traffic coming from OmniS/R ports. Three mobile groups are defined on the switch and each uses a different IP policy.
How Ports Are Assigned to Groups 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. The ports are moved to the Group with policies matching the subnet of the workstation. OmniS/R 12345678 123456 Group 2 IP Network 130.0.0.0 Group 4 IP Network 140.0.0.0 Group 1 Default Group Group 3 IP Network 138.0.
Mobile Groups Mobile Groups 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. In contrast, AutoTracker rules are assigned to the VLANs within a non-mobile group. No AutoTracker VLANs are contained within a mobile Group, and each mobile group constitutes a single spanning tree.
Mobile Groups Turning Group 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. The group you specify must previously have been created through the crgp command.
Mobile Groups 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 Understanding Port Membership in Mobile Groups Switch ports can belong to multiple mobile groups. A port becomes a member of a mobile group as long as one of its attached devices matches the policy criteria for that group.
Mobile Groups 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. Any subsequent mobile groups to which a port gains membership beyond the primary group are “secondary” mobile groups. A port can age out of these secondary groups if the move_to_def variable is enabled (see diagram on page 19-11).
Mobile Groups How a Device Is Dropped from the Default Mobile Group (def_group) Default Group 1 Group 3 Device sends traffic that is forwarded to the MPX for processing. If the traffic matches the policies of an existing mobile group, then it will become a member of that group. If the device does not match the policies of any mobile group, then the def_group variable determines whether that device becomes a member of the default group. If def_group is enabled.... If def_group is disabled....
Mobile Groups How a Port’s Primary Mobile Group Changes (move_from_def) Default/Primary Mobile Group 1 Port assigned to default group 1 or another group through crgp or addvp. If move_from_def is enabled.... Default/Pri Mobile Group 1 Default Group 1 Primary Group 3 Device on port matches policy in another mobile group (3). Group 3 becomes primary group. Helpful Hints: • Reduces broadcasts to the default group. • Best used when only one device is attached to each port.
Mobile Groups How a Port Ages Out of a Mobile Group (move_to_def) Default Mobile Group Primary Group 2 Default Mobile Group Secondary Group 3 Port becomes a member of other mobile groups when it matches their policies. These groups may be primary or secondary groups. Port assigned to default group. If move_to_def is enabled.... Default Mobile Group If move_to_def is disabled....
Mobile Groups Configuring Switch-Wide Group Mobility Variables 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. These variables are illustrated through diagrams on pages 19-9 to 19-11. Follow these steps to use the gmcfg command: 1. Enter gmcfg.
Mobile Groups 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. The prompt will always show the current status of def_group and then ask if you want to change that status. If you want to change the current status, then enter a y at this prompt and press . To keep the current status, simply press .
Mobile Groups Viewing Ports 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. Ports will only display in this screen for secondary groups (i.e., not default or primary groups).
Non-Mobile Groups and AutoTracker VLANs Non-Mobile Groups and AutoTracker VLANs Non-mobile Groups are comprised of physical entities—switch ports. Groups can span multiple switches, but they are still made up of physical ports that you can see and touch. But just as physically-based broadcast domains are limited, entirely port-based Groups can also be limiting. In a large, flat, switched network, broadcast traffic can overload the network. There needs to be a method for subdividing traffic even further.
Non-Mobile Groups and AutoTracker VLANs Spanning Tree and Non-Mobile Groups 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. Ports that are in Blocked state, or in another non-Forwarding state, will not receive frames from the router port. The figure below illustrates this concept.
Group and Port Software Commands Group and Port Software Commands Group and Virtual Port commands are part of the VLAN menu within the User Interface. Entering vlan at any prompt displays the following menu: Command VLAN Management Menu gp crgp modvl rmgp View the list of Groups currently defined Create a Group Modify a VLANs configuration/availability Remove a Group addqgp delqgp viqgp via vi vs ve Add 802.1q group/s to a port Delete 802.1q group/s from a port Display 802.
Creating a New Group Creating a New 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. This section starts on page 19-19. 2. Configure the Virtual Router Port (Optional). This section starts on page 19-21. 3. Enable/disable Group Mobility and User Authentication. This section starts on page 19-27. 4. Configure Virtual Ports.
Creating a New Group Step 1. Entering Basic Group 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. Enter the Group number or accept the number shown in parentheses. Each Group must have a unique number, which may range from 2 to 65,535. (Group 1 is the default switch Group. It does not need to be created and it cannot be deleted.
Creating a New Group 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. Configuring the Virtual Router Port (Optional) on page 19-21. ♦ Note ♦ MPLS is not supported in Release 4.5 and later.
Creating a New Group Step 2. Configuring the Virtual Router Port (Optional) You can now optionally configure the virtual router port that the default VLAN in this Group will use to communicate with other VLANs. When you define a virtual router, a virtual router port for the default VLAN in the Group is created. If you do not define a virtual router, no virtual router port is created and the default VLAN in the new Group will be “firewalled,” unable to communicate with other VLANs.
Creating a New Group 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 . f. The following prompt displays: Disable routing? (n) : Indicate whether you want to disable routing in the group. You can enable routing later through the modvl command. g.
Creating a New Group 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. If the default VLAN contains devices using encapsulation types other than those defined here, the switching modules must translate those frames, which slows throughput.
Creating a New Group 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. l. The following prompt displays: Description (30 chars max): Enter a useful description for this virtual IPX router port using alphanumeric characters.
Creating a New Group 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.3 SNAP (2), Novell Ethernet 802.
Creating a New Group 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. VLAN priority can be set from 0 to 7, with 7 being the level with the most priority. Modifying and displaying a group’s priority is described in Priority VLANs on page 19-73.
Creating a New Group Step 3. Set Up Group Mobility and User 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. In a non-mobile group, ports are statically defined and AutoTracker policies are assigned to individual VLANs within the Group. In most cases, you will want to set up a mobile group. The following steps show you how. a.
Creating a New Group Step 4. Configuring Virtual Ports 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. In addition, if the port you are configuring is Ethernet (10/100 Mbps), you can also configure port mirroring. Prompts for configuring virtual ports follow directly after Group Mobility prompts.
Creating a New Group d. The virtual port configuration menu displays: Modify Ether/8 Vport 2/8 Configuration 1) Vport 2) Description 3) Bridge Mode 31) Switch Timer 4) Flood Limit 5) Output Format Type 6) Ethernet 802.2 Pass Through 7) Admin, Operational Status 8) Mirrored Port Status 9) MAC address :9 : : Auto-Switched : 60 : 192000 : Default (IP-Eth II, IPX-802.
Creating a New Group Auto-Switch. The default setting for all Ethernet ports. This mode is appropriate for dedicated 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). The port will remain in Optimized Device Switching mode until a Spanning Tree BPDU is detected or more than one MAC address transmits data.
Creating a New Group 4) Flood Limit The flood limit allows you to tune a virtual port to limit the flooding of broadcast, multicast, and unknown destination packets. This feature is useful for controlling broadcast storms on your network. While each network is different, in general the amount of flooded traffic represents a relatively small percentage of network traffic. The flood limit is actually a “transmit credit” that is issued every five (5) seconds.
Creating a New Group OmniS/R 12345678 123456 Virtual Router Group 2 Ports 1 and 2 VLAN 1 (default VLAN #1) Ethernet Port 1: Format set to Ethernet II Ethernet Port 2: Format set to SNAP Server Receives frames in Ethernet II format. Workstation Receives frames in SNAP format. The Output Format Type you set for each port determines the type of frames that devices attached to that port receive.
Creating a New Group 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. When you disable a port, the port will not transmit or receive data even if a cable is connected and the physical connection is operational.
Creating a New Group Step 5. Configuring AutoTracker Policies (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. Instructions for configuring these rules can be found in Chapter 20, “Configuring Group and VLAN Policies.” Please refer to that chapter for instructions on configuring each policy type.
Creating a WAN Routing Group Creating a WAN Routing Group After entering basic Group information as described in Step 1. Entering Basic Group Information on page 19-19, you should have answered Yes to the following prompt: Enable WAN Routing? (n): if you want to enable WAN Routing. WAN Routing Groups are treated differently than other Groups, as described earlier. The following steps complete the configuration of the WAN Routing Group. a.
Creating a WAN Routing Group 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. The RIP mode can be set to one of the following: Silent. The default setting shown in parentheses.
Creating a WAN Routing Group 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 and SAP triggered (t)} (a): Select how you want the IPX protocols, RIP (router internet protocol) and SAP (service access protocol), to be configured for the default VLAN in this Group. RIP is a networklayer protocol that enables this VLAN to learn routes.
Viewing Current Groups Viewing Current Groups 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 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. For each Group or VLAN listed, the top field is the Protocol supported by this virtual router port. Possible values in the field are: IP (IP router), IPX (IPX router), and CIP (Classical IP Group with CIP router).
Modifying a Group or VLAN Modifying 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. In addition, if you did not set up a virtual router port (IP or IPX) during the initial Group or VLAN configuration, you can set one up with modvl. To use this command, enter modvl followed by the Group number and VLAN number to change.
Modifying a Group or VLAN Viewing Your 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. The modvl screen will refresh. Saving Your Changes Once you have entered all your modifications and you want to save them, type save at the colon prompt. You will exit the modvl command and your changes will take effect.
Modifying a Group or VLAN 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. The router defaults are as follows: IP Router IP Network Address IP Subnet Mask IP Broadcast Address Router Description Routing Disabled RIP Mode Default Framing Type 0.0.0.0 0.0.0.0 0.0.0.
Deleting a Group Deleting a Group You can delete a Group as long as it does not contain any virtual ports. The default Group, Group #1, cannot be deleted. To delete a Group, enter rmgp followed by the Group number you want to delete. For example, if you wanted to delete Group 5, you would enter: rmgp 5 If the Group does not contain any virtual ports, then a confirmation message displays: GROUP 5 removed.
Adding Virtual Ports Adding Virtual Ports 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 familiar. To use addvp, enter the command followed by the Group number to which you want to add the port. Next, specify the port or ports you want to add.
Modifying a Virtual Port Modifying a Virtual Port 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. To use modvp, enter the command, followed by the Group number for the port, and the physical slot and port number for the port: modvp / You can specify only one port at a time.
Deleting a Virtual Port Deleting a Virtual Port 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. For example, if you configured a port with a special flood limit and customized translation settings and you then removed the port, you would lose those port settings.
Viewing Information on Ports in a Group Viewing Information on Ports 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. You can also display virtual interface attachments for a specific Group by specifying the Group ID after the via command.
Viewing Information on Ports in a Group • • • • • • • • Rtr Brg Tnk T10 FRT Lne CIP Vlc Virtual router port Virtual bridge port Virtual trunk port (used for WAN) 802.10 FDDI service port Frame Relay trunk port LAN Emulation service port Classical IP service port VLAN Clusters (X-LANE) service port Protocol. The bridging protocol for virtual ports and services or the routing protocol for virtual router ports. Possible values are: • Tns • SR • SRT • IP • IPX • FR Page 19-48 Transparent bridge.
Viewing Information on Ports in a Group 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. When Disabled, the port will not transmit or receive data even if a cable is connected and the physical connection is operational. You can set the Admin Status during port configuration phase of the crgp, addvp, or modvp commands.
Viewing Detailed Information on Ports Viewing Detailed Information on Ports 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. For example, to view information only for ports in Group 6, you would enter vi 6 The same type of information is displayed for a single Group as is displayed for all Groups.
Viewing Detailed Information on Ports 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. The service number (Srvc) is port-specific. If a port has more than one service configured on it, then each service will be identified by a different service number. MAC Address. The MAC address for this virtual port.
Viewing Detailed Information on Ports 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. If it is Inactive, then it may not have a good physical connection and it is not capable of passing data at this time. Spn Tr. The port’s current state as defined by the Spanning Tree Protocol.
Viewing Port Statistics Viewing Port 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. For example, to view statistics only for ports in Group 6, you would enter vs 6 You can also display statistics for a specific port by entering the slot and port number after the vs command.
Viewing Port Statistics Service Type values are as follows: • • • • • • • • Rtr Brg Tnk T10 FRT Lne Vlc CIP Virtual router port Virtual bridge port Virtual trunk port (used for WAN) 802.10 FDDI service port Frame Relay trunk port LAN Emulation service port VLAN clusters (X-LANE) service port Classical IP service port The Instance (Inst) is an identifier of this type of service within the switch.
Viewing Port Errors Viewing Port Errors 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. For example, to view errors only for ports in Group 6, you would enter ve 6 You can also display error statistics for a specific port by entering the slot and port number after the ve command.
Viewing Port Errors 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. Buffer Discards In/Out. For transmit (Out) and receive (In), the number of frames discarded due to a lack of buffer space. Buffer discard information is not provided for virtual router ports. Error Discards In/Out.
Port Mirroring Port 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. When you enable port mirroring, the active, or “mirrored,” port transmits and receives network traffic normally, and the “mirroring” port receives a copy of all transmit and receive traffic to the active port.
Port Mirroring where is the slot number of the module containing the mirrored port, and 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. If a cable is not attached to the Mirrored port, port mirroring will not take place.
Port Mirroring Mirrored Port Mirroring Port probe frames sent ➊ RMON from the Mirroring Port. probe frames from ➋ RMON the Mirroring Port appear to RMON Probe come from the Mirrored Port when the NMS workstation receives them. NMS Workstation Mirrored Port Mirroring Port mirroring sends cop➍ Port ies of management frames to the Mirroring Port. frames from the ➌ Management NMS workstation are sent to the Mirrored Port.
Port Mirroring Setting Up Port 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. Follow the steps below to set up port mirroring. 1. Start the addvp or modvp command for the virtual port that you want to mirror. 2.
Port Monitoring Port 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. Understanding data flow in a VLANbased switch presents unique challenges primarily because traffic takes place inside the switch, especially on dedicated devices.
Port Monitoring RAM Disk System for Data Capture 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. You can copy files between the /ram disk system and the standard /flash file system. In addition, files in the RAM disk system are retrievable via FTP.
Port Monitoring Starting a Port 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. For example, to monitor a port that is the first port in the fourth slot of the switch, you would enter pmon 4/1 You can only monitor Ethernet 10BaseT ports. If a port is already being mirrored (enabled through the addvp or modvp command) you cannot monitor it.
Port Monitoring If You 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 Ending a Port 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 monitoring capture done. Current capture files listed: Current working directory ‘/ram’. PM0302.ENC PM0303.
Port Mapping Port 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. Virtual LANs, or VLANs, were introduced to segment traffic such that devices could only engage in switched communication with other devices in the same VLAN. Some applications today require a further degree of traffic segmentation than that provided by VLANs.
Port Mapping 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. This configuration restricts each port to communication only with the other four ports in the opposite port mapping subset within the same group. For example, port 2/1 can only send traffic to ports 5/1, 5/2, 5/3, and 5/4.
Port Mapping Who Can Talk 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 Creating a Port 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. This is done by entering the line number, an equal sign, and the port (or ports) to be added.
Port Mapping Adding Ports to a Port 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 where is the map set number shown when the map set was created. (To view a list of all existing map sets, see Viewing a Port Mapping Set on page 19-72.) For example, to modify map set 5, you would enter the following: pmapmod 5 2.
Port Mapping Removing Ports from a Port 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 where is the map set number shown when the map set was created. (To view a list of all existing map sets, see Viewing a Port Mapping Set on page 19-72.) For example, to modify map set 5, you would enter the following: pmapmod 5 2.
Port Mapping Viewing a Port Mapping Set You can view a port mapping set using the vpmap command. Enter the pmapv command as shown: pmapv where is the map set number shown when the map set was created.
Priority VLANs Priority VLANs Prioritizing VLANs allows you to set a value for traffic based on the destination VLAN of packets. 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 Configuring VLAN Priority To configure the priority of a VLAN: 1. Enter the prty_mod command at the system prompt, as shown: prty_mod where is the group number associated with the VLAN whose priority is being set. For example, to modify the priority of the VLAN for Group 2, you would enter the following: prty_mod 2 The following prompt is shown: Enter a priority value which is between 0 and 7: 0 2.
20 Configuring Group and VLAN Policies 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. You can define multiple policies—also referred to as “rules”—for a mobile Group or an AutoTracker VLAN. A port or device is included in a mobile Group or AutoTracker VLAN if it matches any one AutoTracker rule.
AutoTracker Policy Types AutoTracker Policy 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 maximum number of policies for the Group is not exceeded. A port or device is included in a mobile group or AutoTracker VLAN if it matches any one rule. You can define the following types of rules: Port Policies. Port policies enable you to define membership on the basis of ports.
AutoTracker Policy Types You must specify a separate binding policy for each device, but you can specify an unlimited number of such policies. Binding policies take precedence over all other AutoTracker policies. DHCP Port Policies. These policies are similar to standard port policies, but apply to switch ports to which DHCP client workstations are attached. DHCP MAC Address Policies.
Defining and Configuring AutoTracker Policies Defining and Configuring AutoTracker Policies 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. A port or device is included in a mobile group or AutoTracker VLAN if it matches any one rule.
Defining and Configuring AutoTracker Policies Defining a Port Policy 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. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Press .
Defining and Configuring AutoTracker Policies Defining a MAC Address Policy 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. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Enter 2 and press . 2.
Defining and Configuring AutoTracker Policies Defining a MAC Address Range Policy 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. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Enter 21 and press . 2.
Defining and Configuring AutoTracker Policies Defining a Protocol Policy 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. Protocol Rule 4. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Press 3 and press . 2.
Defining and Configuring AutoTracker Policies If you want to define a protocol other than IP, IPX, AppleTalk, or DECNet, 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. The following three sections describe how to specify these protocol types. If you are not specifying one of these special protocol types, continue with Step 4 below.
Defining and Configuring AutoTracker Policies Protocol Specified by Ether-Type a. To specify a protocol by Ethernet type, enter 5 at the Select Protocol: menu. The following prompt displays: Enter the Ether-type value in hex: b. Enter the desired Ethernet type in hex. You must enter two bytes of data. For example, enter 0800 to specify IP or enter 0806 to specify ARP. All devices that use the specified Ethernet type will be members of the mobile group or AutoTracker VLAN. c. Go on to Step 4 below.
Defining and Configuring AutoTracker Policies Defining a Network Address Policy 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. Protocol Rule 4. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Press 4 and press . 2.
Defining and Configuring AutoTracker Policies Set Up an IPX Address 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. IPX addresses consist of eight hex digits and you can enter a minimum of one hex digit in this field.
Defining and Configuring AutoTracker Policies Defining Your 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. Each userdefined rule requires an Offset, a Value, and a Mask; you will be prompted for each of these values. The Offset specifies the location of the pattern within the frame. The Value specifies the pattern.
Defining and Configuring AutoTracker Policies For example, if you enter FFEF as the value and FFFF as the mask: Binary Hex 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. When a bit in the mask is set to 0, the corresponding bit in the value is ignored and can be either a 0 or a 1.
Defining and Configuring AutoTracker Policies Defining a Port Binding Policy 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). 2. The device can attach to a specific switch port and use a specific MAC address and use a specific IP network address 3.
Defining and Configuring AutoTracker Policies 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. Protocol Rule 4. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8. DHCP MAC Rule 81) DHCP MAC Range Rule Enter rule type (1): 1. Enter a 6 and press . 2.
Defining and Configuring AutoTracker Policies 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. You should first enter the slot for the module, then a slash (/), then the port number. If you selected binding policy 1 or 5, then continue with step 5.
Defining and Configuring AutoTracker Policies If you want to define a protocol other than IP, IPX, AppleTalk, or DECNet, 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. The following three sections describe how to specify these protocol types. If you are not specifying one of these special protocol types, continue with Step 8 below.
Defining and Configuring AutoTracker Policies Protocol Specified by Ether-Type a. To specify a protocol by Ethernet type, enter 5 at the Select Protocol: menu. The following prompt displays: Enter the Ether-type value in hex: b. Enter the desired Ethernet type in hex. You must enter two bytes of data. For example, enter 0800 to specify IP or enter 0806 to specify ARP. All devices that use the specified Ethernet type will be members of the mobile group or AutoTracker VLAN. c. Go on to Step 8 below.
Defining and Configuring AutoTracker Policies Defining a DHCP Port Policy 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. DHCP port policies differ fundamentally from standard port policies.
Defining and Configuring AutoTracker Policies Defining a DHCP MAC Address Policy 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. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3. Protocol Rule 4. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8.
Defining and Configuring AutoTracker Policies Defining a DHCP MAC Address Range Policy 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. Port Rule 2. MAC Address Rule 21) MAC Address Range Rule 3. Protocol Rule 4. Network Address Rule 5. User Defined Rule 6. Binding Rule 7. DHCP PORT Rule 8.
Viewing Mobile Groups and AutoTracker VLANs Viewing Mobile Groups and AutoTracker 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 Viewing Policy Configurations 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 Viewing Virtual Ports’ Group/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. Type vivl and a Virtual Interface Table displays similar to the one that follows.
View VLAN Membership of MAC Devices View VLAN Membership of MAC Devices 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. The following prompt displays: Enter Slot/Interface (return for all ports) : Enter the slot and port for which you want to view MAC Address/VLAN information. You can also press to view information on all ports in the switch. 3.
Application Example: DHCP Policies Application Example: DHCP Policies This application example shows how Dynamic Host Configuration Protocol (DHCP) port and MAC address policies can be used in a DHCP-based network. DHCP is built on a client-server model in which a designated DHCP server allocates network addresses and delivers configuration parameters to dynamically configured clients. Since DHCP clients initially have no IP address, placement of these clients in an AutoTracker VLAN presents a problem.
Application Example: DHCP Policies DHCP Servers 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. However, if the network configuration does not lend itself to this solution (as the Production VLAN does not in this application example), then the server and clients can communicate through a router with Bootp relay enabled.
Application Example: DHCP Policies DHCP Port and MAC Rules Omni Switch/Router 12345678 123456 Group 3 Client 1 DHCP Port Rule Server 1 10.15.14.16 Test VLAN IP Subnet 10.15.X.X DHCP Port Rules Client 2 DHCP Port Rule Client 3 DHCP Port Rule Router 1 No Bootp Relay Production VLAN IP Subnet 10.15.128.X DHCP Port Rules Router 2 Bootp Relay On Client 4 DHCP Port Rule Client 5 DHCP Port Rule Server 2 10.13.15.17 Branch VLAN IP Subnet 10.13.X.
Application Example: DHCP Policies Page 20-30
21 Interswitch Protocols 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 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 adjacent to it by sending and responding to Hello update packets.
XMAP XMAP Transmission 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. ♦ Note ♦ All Hello packet transmissions are sent to a well-known MAC address (0020DA000003). The transmission states are illustrated here. No Hello packets received after 3 discovery transmission timeouts.
XMAP Common Transmission 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. To avoid synchronization with adjacent switches, the common transmission time is jittered randomly by plus or minus ten percent.
Configuring XMAP 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. Enabling or Disabling XMAP To display whether or not XMAP is active or inactive, or to activate or deactivate XMAP, enter the following command: xmapst A screen displays similar to the following: XMAP is currently ACTIVE.
Configuring XMAP A visual illustration of these connections is shown here: REMOTE OSR B 0020DA:032C40 VPN 1 OSR A (LOCAL) VPN 1 VPN 3 VPN 4 HUB VPN 1 VPN 3 REMOTE OSR C 0020DA:999660 VPN 4 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. Rem VPN. The MAC address of the MPX in the adjacent switch. The remote virtual port number in the adjacent switch. Pri Group.
Configuring XMAP 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. Configuring the Common Transmission Time Use the xmapcmntime command to view or change the time between sending Hello update packets in the common transmission state.
VLAN Advertisement Protocol (VAP) VLAN Advertisement Protocol (VAP) 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. VAP is useful when you want all VLANs to communicate over a backbone, but do not want locally connected devices to receive all backbone traffic. In order for a switch to participate in VAP exchanges, VAP must be enabled through a software configuration command.
VLAN Advertisement Protocol (VAP) VAP and Port Policies 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 backbones to ensure that connectivity is established and maintained. When you use port policies, all devices heard through a port will become a member of the VLAN.
GMAP 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. Using GMAP the switch sends a complete list of learned MAC addresses and associated group/protocol information to all interconnected switches in the network. Update and retention times are configurable.
GMAP 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. Enabling and Disabling GMAP Use the gmapst command to display or change the state of GMAP. A prompt similar to the following displays: GMAP is currently INACTIVE.
GMAP 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 configured interval. For example, if the default of 300 seconds is used, the jitter is plus or minus 75 seconds. To view the current update time, enter the following: gmapupdttime A message similar to the following displays: GMAP Update Time is 300 seconds.
GMAP Displaying GMAP Statistics by MAC Address To display GMAP statistics for all MAC addresses, use the gmapls command.
GMAP Page 21-14
22 Managing AutoTracker VLANs In a large, flat, switched network, broadcast traffic can overload a network based primarily on port-based Groups. Through the use of AutoTracker VLANs, you can control broadcast traffic such that it is forwarded only to those VLANs where it needs to be sent. VLANs are created within a Group to subdivide network traffic based on specific criteria. The criteria you use to define a VLAN are called AutoTracker policies.
The AutoTracker Menu The AutoTracker 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 AutoTracker VLANs AutoTracker VLANs enable you to control communications between end stations in your network. You define policies that determine membership in the VLAN and AutoTracker automatically locates ports or devices within the Group that fit the policies and places them into the VLAN. You can define physical policies or logical policies (or combinations thereof) to determine membership in AutoTracker VLANs.
AutoTracker VLANs 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. Or, you can specify that all IPX users in a specific network address area using a certain encapsulation type be included in the VLAN.
AutoTracker VLANs How Devices are Assigned to AutoTracker 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. Source learning logic on the MPX module examines the entire frame to determine the VLAN or VLANs in which the originating device should be a member.
AutoTracker VLANs Devices that Generate a Secondary Traffic 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. When a device generates secondary traffic that does not match any existing VLAN policy, that traffic is grouped into the primary VLAN of which the device is a member.
AutoTracker VLANs How Devices are Assigned to AutoTracker VLANs (continued) Router Traffic in IP and IPX Network Address VLANs Prior to release 2.1, AutoTracker handled VLAN assignments for router traffic in IP and IPX network address VLANs in the same manner as normal traffic. In release 2.1 and later, AutoTracker differentiates router traffic from normal traffic and can distinguish traffic that is routed through a router from traffic that is generated by a router.
AutoTracker VLANs How Routed Frames can Confuse VLAN Assignment router receives the frame on the interface for Network 2 and ➋ The routes the frame to the interface for Network 3. To do this, the router strips the MAC header from the frame and inserts the MAC address of its interface for Network 3. The Frame frame now specifies its source from Network 2, MAC address Y as Network 2, MAC address Y.
AutoTracker VLANs How Devices are Assigned to AutoTracker VLANs (continued) Port Policy Functionality In release 2.1 and later, AutoTracker’s VLAN port policy can be set to operate in either of two distinct modes: • In the original mode, wherein membership in all VLANs active on a port is inherited by all devices connected to that port. Original port policy functionality is explained on page 22-10.
AutoTracker VLANs Original Port Policy Functionality (reg_port_rule = 1) Omni Switch/Router 1 87654321 654321 Device Source Port VLAN Membership Group 1 VLAN 2 port rules Ports 2-1 (Device B) and 3-1 (Devices A & D) Slot 2 Port 1 A B C D VLAN 3 port rules Ports 2-2 (Device C) and 3-1 (Devices A & D) Slot 3 Port 1 Device B 3-1 2-1 2-2 3-1 2 and 3 2 3 2 and 3 Slot 2 Port 2 Device C Because 3-1 (slot 3 port 1) on switch 2, the backbone port, is a member of VLANs 2 and 3 on switch 2, VLANs 2 and 3
AutoTracker VLANs Current Port Policy Functionality (reg_port_rule = 0) Omni Switch/Router 1 87654321 654321 Device Source Port VLAN Membership Group 1 VLAN 2 port rules Ports 2-1 (no devices) and 3-1 (no devices) Slot 2 Port 1 Slot 3 Port 1 Device B Device Source Port VLAN Membership 2-1 3-1 3-1 2-2 default default default default Slot 2 Port 2 VLAN VLAN VLAN VLAN #1 #1 #1 #1 3-1 2-1 2-2 3-1 default default default default VLAN VLAN VLAN VLAN #1 #1 #1 #1 With current port policy functionali
AutoTracker VLANs The Usefulness of Port Policies 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. Current port policy functionality – as illustrated on page 22-11 – neither contributes to nor participates in VLAN assignments. Port policies, either original or current, are in fact not useful in the creation of consistent VLAN membership across multiple switches.
AutoTracker VLANs So How Do I Get Devices Assigned to VLANs Over a Backbone? The way to get devices assigned to VLANs 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. The network on the facing page uses port policies (and current port policy functionality) to assign the backbone port to VLANs on each switch so that traffic can flow out onto the backbone from these VLANs.
AutoTracker VLANs An Example of VLAN Assignment Using Logical Policies and Current Port Policy Functionality (reg_port_rule = 0) Omni Switch/Router 1 87654321 654321 Device Source Port VLAN Membership Group 1 VLAN 2 Protocol rule: IPX (assigns devices A & B) Port rule: 3-1 (assigns no devices) Slot 2 Port 1 Device B IPX VLAN 3 Protocol rule: IP (assigns devices C & D) Port rule: 3-1 (assigns no devices) Slot 3 Port 1 Slot 2 Port 2 Because the backbone port, port 31, is assigned to VLAN s 2 and 3 in
AutoTracker VLANs Frame Flooding in AutoTracker 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. However, this is not true with VLANs as VLANs segment the network into smaller broadcast domains.
Creating AutoTracker VLANs Creating AutoTracker VLANs You create AutoTracker VLANs 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. See Step A. Entering Basic VLAN Information on page 22-16 for instructions on this step. B. Define policies that define membership in the VLAN. See Step B. Defining and Configuring VLAN Policies on page 22-18 for instructions on this step. C.
Creating AutoTracker VLANs 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. A disabled VLAN is still defined (name, number, policies intact), but the switch keeps the VLAN disabled. The enable/disable status may be changed at a later time using the modatvl command.
Creating AutoTracker VLANs Step B. Defining and Configuring VLAN Policies 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. A port or device is included in a AutoTracker VLAN if it matches any one rule. For example, you can define rules based on ports, rules based on MAC address, and rules based on protocol in the same AutoTracker VLAN.
Creating AutoTracker VLANs Step C. Configuring the Virtual Router Port (Optional) You can now optionally configure the virtual router port that this VLAN will use to communicate with other AutoTracker VLANs. A virtual router port for the VLAN is created within the switch. If you do not define a virtual router port for this VLAN, devices within the VLAN will only be able to communicate with devices in other VLANs through an external router.
Creating AutoTracker VLANs 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. RIP (Router Information Protocol) is a network-layer protocol that enables this VLAN to learn and advertise routes. The RIP mode can be set to one of the following: Silent. The default setting shown in parentheses.
Creating AutoTracker VLANs Omni Switch/Router 12345678 123456 Virtual Router SNMP AGENT RIP Virtual Router Port Group VLAN The Default Router Framing Type determines the type of frame transmitted through the Virtual Router Port to the VLAN. Workstation A Workstation B 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 if you want to enable IPX Routing on this virtual router port.
Creating AutoTracker VLANs 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. RIP is a network-layer protocol that enables this VLAN to learn routes.
Creating AutoTracker VLANs 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. The choices are: ARE broadcasts. All Routes Explorer, the default setting. Broadcasts are transmitted over every possible path on inter-connected source-routed rings.
Modifying an AutoTracker VLAN Modifying an AutoTracker VLAN After you set up a VLAN you can modify its Admin Status, description, rules, and the Admin Status of each of the rules. You use the modatvl command to modify a VLAN as follows: modatvl : You must specify the Group and VLAN numbers and they must be separated by a colon.
Modifying an AutoTracker VLAN Changing a VLAN’s Description 1. At the Option= prompt enter a 2 and press . 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. Press when you have completed the new description. The system returns to the Available Options menu. You can modify more attributes for this VLAN, or quit modifying the VLAN by typing a 6. Adding More Policies for This VLAN 1.
Modifying an AutoTracker VLAN Changing the Admin Status for a VLAN Policy 1. At the Option= prompt enter a 5 and press . 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. Find the number corresponding to the rule you want to change and enter it at this prompt and press . 3.
Viewing AutoTracker VLANs Viewing AutoTracker VLANs You can view the current status of all AutoTracker VLANs in the switch using the atvl command. Enter atvl and a table similar to the following displays.
Viewing Policy Configurations Viewing Policy Configurations Typing viatrl brings up the Policy Configuration Table, which shows the policies defined for the VLAN specified.
Viewing Virtual Ports’ VLAN Membership Viewing Virtual Ports’ 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. Type vivl and a Virtual Interface Table displays similar to the one that follows. You can also specify just the slot and port number to narrow the range of ports displayed.
View VLAN Membership of MAC Devices View VLAN Membership of MAC Devices 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. The following prompt displays: Enter Slot/Interface (return for all ports) : Enter the slot and port for which you want to view MAC Address/VLAN information. You can also press to view information on all ports in the switch. 3.
Creating a VLAN for Banyan Vines Traffic Creating a VLAN for Banyan Vines Traffic Banyan Vines uses a fixed encapsulation for each network interface. For this reason, it is straightforward to create a VLAN for Banyan Vines traffic. For Ethernet traffic, Banyan Vines uses Ethernet II encapsulation; Token Ring uses LLC; FDDI uses SNAP. This procedure describes how to create a VLAN for Ethernet, Token, and FDDI traffic. Follow these steps to create a Banyan Vines VLAN: 1. Type cratvl at any prompt. 2.
Creating a VLAN for Banyan Vines Traffic 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 . 9. The following prompt displays: Enter the Ether-type value in hex: 10. Enter 0bad as the Ether-type value for Ethernet II encapsulation. 11.
Creating a VLAN for Banyan Vines Traffic 15. The following prompt displays Enter the DSAP value in hex: Enter bc as the destination service access protocol (DSAP) value and press . 16. The following prompt displays: Enter the SSAP value in hex: Again, enter bc as the source service access protocol (SSAP) value and press . 17. The following prompt displays: Configure more rules for this vlan (y/n): Enter a Y. You still need to set up a rule for SNAP traffic. 18.
Creating a VLAN for Banyan Vines Traffic 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 following displays: VLAN 1:2 created successfully 23. The following prompt displays: Enable IP (y): Enter an N. 24. The following prompt displays: Enable IPX (y): Enter an N. The Banyan Vines traffic VLAN is complete.
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. You define the multicast traffic to be transmitted by specifying a multicast address. You define the recipients of the multicast traffic by specifying ports and/or specific MAC addresses.
How Devices 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. If the recipients of the multicast traffic were defined using the MAC address rule to specify the MAC addresses of the receiving devices, no action is taken until a frame is received from one of those devices.
Frame Flooding in Multicast VLANs Multicast traffic is flooded as follows in an environment that includes multicast VLANs: • If the destination address is a multicast address, and • if the destination multicast address is in the filtering database, and • if the destination multicast address is a specified multicast address for a multicast VLAN, then flood the traffic on all ports that have at least one multicast VLAN in common with the destination multicast address. This is illustrated below.
Creating Multicast VLANs Creating Multicast VLANs You create multicast VLANs 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. See Step A. Entering Basic Information on page 23-5 for instructions on this step. B. Defining the multicast address. You define one or more multicast addresses that define the multicast stream(s) for the multicast VLAN. See Step B.
Creating Multicast VLANs 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.You can create up to 32 multicast VLANs and up to 31 AutoTracker VLANs in a single Group. 3.
Creating Multicast VLANs Step B. Defining the Multicast Address 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. The source port does not need to be a member of the same Group as recipient ports. Note that the source port does not become a member of the multicast VLAN. 1.
Creating Multicast VLANs Step C. Defining the Recipients of Multicast Traffic 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. You can use both rules within a single multicast VLAN. For example, you might want to flood multicast traffic to all devices attached to one switch port, but only a few devices attached to other switch ports.
Creating Multicast VLANs Defining Recipients By MAC Address 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 . 2. The following prompt displays: Set Rule Admin Status to ((e)nable/(d)isable): Indicate whether or not you want to enable this rule. Type e to enable or d to disable.
Modifying Multicast VLANs Modifying 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. You use the modmcvl command to modify a multicast VLAN as follows: modmcvl : You must specify the Group and multicast VLAN number and they must be separated by a colon.
Modifying Multicast VLANs Changing a VLAN’s Description 1. At the Option= prompt enter a 2 and press . 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. Press when you have completed the new description. The system returns to the Available Options menu. You can modify more attributes for this multicast VLAN, or quit modifying the multicast VLAN by typing an 6.
Modifying Multicast VLANs Changing the Admin Status for a VLAN Policy 1. At the Option= prompt enter a 5 and press . 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. Find the number corresponding to the rule you want to change and enter it at this prompt and press . 3.
Modifying a Multicast Address Policy Modifying a Multicast Address Policy 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 multicast address. Follow the steps outlined in Modifying Multicast VLANs on page 23-9 and the steps for Adding More Policies for This VLAN on page 23-10. Continue with the procedure below. The following menu displays: Select rule type: 1. Port Rule 2.
Viewing Multicast VLANs Viewing Multicast VLANs You can view the current status of all multicast VLANs in the switch using the mcvl command.
Viewing Multicast VLAN Policies Viewing Multicast VLAN Policies You can view the current multicast VLAN policies and their status using the vimcrl command.
Viewing the Virtual Interface of Multicast VLANs Viewing 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. However, when multiple services are set up for a virtual port, then each service may be split into one or more instances. Type vimcvl and a Virtual Interface Table displays similar to the one that follows.
Viewing the Virtual Interface of Multicast VLANs Page 23-16
24 AutoTracker VLAN Application Examples This chapter provides specific examples of AutoTracker VLANs in various network configurations. These examples illustrate basic concepts about AutoTracker and highlight issues that can arise when AutoTracker is used in different network situations. • Application Example 1 illustrates a network organized according to logical policies and explains the benefits of a logical network organization.
Application Example 1 Application Example 1 VLANs Based on Logical Policies 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. The use of logical policies provides the flexibility of moving IP users from segment to segment and preserving their original VLAN membership – without reconfiguring AutoTracker or the workstations.
Application Example 1 Omni Switch/Router 12345678 123456 Group 2 Ports 1, 2, 3, and 4 VLAN A IP Nnetwork 125.0.0.0 Port 1 .35 .0.0 125 Port 2 125.0.0.1 125.0.0.2 125.0.0.3 Internal 1 30.0 IP .0.2 2 Router VLAN B IP Network 130.0.0.0 Port 3 Port 4 130.0.0.10 IP Workstation IP Workstations 130.0.0.12 125.0.0.33 125.0.0.34 130.0.0.11 IP Workstations IP Workstation Workstation 130.0.0.11 has been moved from the segment connected to port 4 to the segment connected to port 2.
Application Example 2 Application Example 2 VLANs in IPX Networks Example 2 illustrates the use of AutoTracker VLANs in IPX networks – specifically, VLANs based on IPX network address rules. IPX networks have unique characteristics that must be considered when configuring VLANs based on network address rules. Encapsulation Type in IPX Networks The encapsulation type a MAC station uses is very important in IPX networks, because a close relationship exists between encapsulation type and IPX network number.
Application Example 2 IPX VLAN Assignment at Bootup Omni Switch/Router 12345678 123456 Group 3 Ports 1 – 10 network 50 network 40 network 30 network 20 network 10 Internal IPX Router Server 1 Network 10 Ethernet-II encap Port 1 IPX Network 10 Ethernet-II encap Server 2 Network 20 Ethernet-II encap Port 2 IPX Network 20 Ethernet-II encap Server 3 Network 30 802.2 encap Port 3 IPX Network 30 Server 4 Network 40 SNAP encap Port 4 Server 5 Network 50 802.
Application Example 2 In this example one Group was created – Group 3 – that includes all ports to which IPX servers and clients are connected. Within this Group five VLANs were created, one for each server: VLAN B VLAN C VLAN D VLAN E VLAN F IPX Network 10 Ethernet-II encap IPX Network 20 Ethernet-II encap IPX Network 30 IPX Network 40 SNAP encap IPX Network 50 IPX 802.3 encap 802.
Application Example 3 Application Example 3 IPX Network Address VLANs and Translated Frames Application Example 3 shows two IPX networks connected over a bridged FDDI ring spanning two Omni Switch/Routers. VLAN B exists in both switches and specifies an IPX network address policy of network number 100 and Ethernet-II encapsulation.
Application Example 4 Application Example 4 Routing in IPX Networks How Routing Works 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. If a VLAN has a logical policy, AutoTracker assigns the first port to the VLAN when a frame is received from a source device that matches the VLAN’s policy.
Application Example 4 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. When the internal IPX router sends out broadcasts on VLAN 1, they are flooded out all ports in the Group because, by default, all ports in the Group are members of VLAN 1.
Application Example 5 Application Example 5 Traversing 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. This necessity arises because, as explained in How Routing Works Generally on page 24-8, AutoTracker does not activate a VLAN – or its internal router interface – until a port is assigned to that VLAN. AutoTracker assigns ports to VLANs with port policies immediately.
Application Example 5 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. If VLAN D has a port policy that includes port 2 on Switch 1 and port 1 on Switch 2 – the ports to which the backbone is connected – VLAN D and its internal router will activate immediately in both Switch 1 and Switch 2. Traffic (i.e.
Application Example 5 Page 24-12
25 IP Routing Introduction 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. For information about configuring virtual router ports, see Chapter 19, “Managing Groups and Ports.
IP Routing Overview IP Routing Overview 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 Transport 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 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). The steps for setting up IP routing on the switch are given here: Step 1.
Setting Up IP Routing on the Switch 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. Other features are available as optional switch software and are described in separate user manuals. The features are listed here: • UDP forwarding—Forwards UDP broadcasts/multicasts across groups/VLANs. See Chapter 26, “UDP Forwarding.
The Networking Menu The Networking Menu The Networking menu contains commands that control, and are related to, the routing protocols that are run on the switch. To switch to, and to display, the Networking menu, enter the following commands: networking ? If you have enabled the verbose mode, you do not need to enter the question mark (?).
The IP Submenu 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 Viewing the Address Translation (ARP) Table 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 Adding Entries to the ARP Table 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. Follow the steps below to add an address to the ARP Table. 1. Enter add. The following prompt displays: Host name or IP addr to add: Enter the name of the host or its IP address. 2.
Viewing the Address Translation (ARP) Table Deleting Entries from the ARP Table 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. The following prompt displays: Host name or IP addr to delete: Enter the host name or address that you wish to delete. 2. The system will then confirm the deletion from the table (an example is shown below). ARP table entry for host 198.206.184.
Viewing the Address Translation (ARP) Table Finding a Specific MAC Address in the ARP Table 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). Follow the steps below to display a specific MAC address in the ARP Table. 1. Enter ipfind. The following prompt displays: Hostname or IP address to find: 2.
Viewing IP Statistics and Errors Viewing IP Statistics and Errors 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 Fastpath Datagrams Forwarded (Displays for Omni S/R) The number of IP datagrams forwarded to their destination without using the MPX. Fastpath Inbound Discards (Displays for Omni S/R) The number of bad packets received and discarded. Typically this value should be zero. Fastpath Utilization (Displays for Omni S/R) The percentage of total datagrams received that are forwarded by the fastpath code.
Viewing IP Statistics and Errors PDUs Needing Reassembly The number of IP datagram fragments that needed to be reassembled by this switch. PDUs Successfully Reassembled The number of IP datagrams successfully reassembled by this switch. PDUs Needing Fragmentation The number of IP datagrams requiring fragmentation by this switch. Fragments created The number of IP datagram fragments that have been generated as a result of fragmentation by this switch.
Viewing the IP Forwarding Table Viewing the IP Forwarding Table 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 protocols, and the static routes that you may have entered manually. You can also add to, or remove static routes from, the IP Forwarding Table (see Adding an IP Static Route on page 25-17 and Removing an IP Static Route on page 25-19).
Viewing the IP Forwarding Table The fields on the IP Forwarding Table have the following meanings: Network The destination network IP address. Mask The IP subnet mask. Gateway The network address of the gateway (the router from which this address was learned). Metric The metric associated with this network. Generally, this is a RIP “hop” count, or the number of hops the network is away from this router. Group VLAN Id The group and VLAN number from which this IP address was learned.
Adding an IP Static Route Adding 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. In order to add a static route, you will need to know the host/net IP address and the gateway IP address which will be used to route traffic to the external IP address.
Adding an IP Static Route 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 Removing 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. For more information about routing domains, see Chapter 14, “Routing Domains,” in the Advanced Routing User Manual.
Viewing ICMP Statistics and Errors Viewing ICMP Statistics and Errors The icmps command is used to monitor ICMP activity.
Viewing ICMP Statistics and Errors Address 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. Address Mask Reply Messages The number of Address Mask Reply messages that were sent/received by this switch. Errors The number of ICMP messages this switch sent/received but was unable to process because something was wrong (for example, a checksum failure).
Using the PING Command Using 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. Follow the steps below to issue an IP ping request. 1. Enter ping. A screen similar to the following displays: Host () : Enter the IP address of the host that you want to “ping.” 2.
Using the PING Command 5. After answering the previous prompt, a screen similar to the following displays: Ping starting, hit to stop PING 198.206.184.18: 64 data bytes [0 [50 [100 [150 [200 [250 ] ] ] ] ] ] ..... . . . T. ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ... ..... ..... ..... ..... ..... ..
Viewing UDP Statistics and Errors Viewing UDP Statistics and Errors 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 Viewing the UDP Listener Table 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 datagrams. The UDP Listener Table shows the local IP addresses for each UDP listener and the local port number for this listener. An IP address of zero (0.0.0.0) indicates that it is listening on all interfaces.
Viewing RIP Statistics and Errors Viewing RIP Statistics and Errors The rips command is used to display RIP statistics and errors. This command displays cumulative statistics since the last time the switch was powered on, or since the last reset of the switch was executed. To display information about RIP statistics and errors, enter the following command: rips A screen similar to the following displays: RIP Statistics Rtr (Group ID:VLAN ID 1:1) IP Address 198.206.182.
Viewing TCP Statistics Viewing TCP Statistics The tcps command is used to monitor TCP traffic activity and check TCP configuration parameters. To reconfigure TCP parameters, see Viewing the TCP Connection Table on page 25-29.
Viewing TCP Statistics 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”. Total Segments Received The total number of segments received, including those received in error. This count includes segments received on currently established connections.
Viewing the TCP Connection Table Viewing the TCP Connection Table The tcpc command is used to check the current TCP connections available in the TCP Connection Table. To display the TCP Connection Table, enter the following command: tcpc A screen similar to the following displays: TCP Connection/Listener Table Local Address/Port ----------------------------------127.0.0.1 / 1090 127.0.0.1 / 1091 198.206.184.42 / 23 0.0.0.0 / 23 0.0.0.
Using the TELNET Command Using 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. To initiate a TELNET session, enter the following command: telnet A screen similar to the following displays: telnet> To display a listing of the TELNET commands, enter the following command: ? A screen similar to the following displays: Commands may be abbreviated.
Tracing an IP Route Tracing 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. When using the traceroute command, you must enter the name of the destination as part of the command line. As an example, we might want to trace the route to “corporate.com.” To do so, we would enter this command: traceroute corporate.
Flushing the RIP Routing Tables Flushing the RIP Routing Tables 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. To flush the RIP Routing Table, enter the following command: ripflush No message is displayed; the system prompt simply reappears.
Configuring IP RIP Filters Configuring IP RIP Filters 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. By using IP RIP filters, you can minimize the number of entries that are put into the IP Forwarding Table as well as improve overall network performance by eliminating unnecessary traffic.
Configuring IP RIP Filters 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). If you choose the default you will not be prompted for the network mask (as is shown in the next step). 5. The following prompt displays: IP network mask (default: 255.255.255.
Configuring IP RIP Filters 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.255.255.0). Note that the default mask will vary depending on the class of the IP address you entered above. 6.
Configuring IP RIP Filters Deleting IP RIP Filters 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. 2. A screen similar to the following displays: Displaying all filters: # --1 2 Type -------------RIP OUT RIP IN Network -----------------99.0.0.0 99.0.0.0 Mask Md ---------------- -----255.0.0.0 A 255.0.0.
Configuring IP RIP Filters 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 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 to the following displays: Displaying global filters: # --1 Type -------------RIP OUT Network -----------------99.99.99.99 Mask Md ---------------- -----255.0.0.
Viewing the IP-to-MAC Address Table Viewing the IP-to-MAC Address Table 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. The information in this table is learned from ARP (Address Resolution Protocol) messages received on “leaf” ports.
Viewing the IP-to-MAC Address Table Slot/Intf The slot number and interface number from which the IP and MAC addresses were learned. Displaying Information for a Specific IP Address To display the entry in the IP-to-MAC table for a specific IP address, enter the desired IP address after the command. For example, to locate the entry for IP address 192.168.10.1, enter the following command: ipmac 192.168.10.1 A screen similar to the following displays: IP to MAC ADDRESS ASSOCIATION TABLE IP Address 192.168.
Enabling/Disabling Directed Broadcasts Enabling/Disabling Directed 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. The datagram is routed through the network as a unicast packet. When it arrives at the subnet, it is converted into a broadcast packet. Directed broadcasts are used in denial-of-service smurf attacks.
Path MTU Discovery Path MTU Discovery All Gigabit Ethernet modules and all Mammoth-based Ethernet modules on the Omni Switch/Router in Release 4.0 and later support path Maximum Transmission Unit (MTU) discovery. In path MTU discovery, the Ethernet frame (datagram) size is set to the largest size that does not require fragmentation anywhere along the path from a source host to its destination. This frame size, known as a Path MTU (PMTU), is thus equal to the minimum of the MTUs of each hop in the path.
26 UDP Forwarding 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. This chapter describes the UDP relay function in the switch, which allows UDP broadcast packets to be forwarded across groups and VLANs that have IP routing enabled. The UDP relay allows you to use nonroutable protocols in a routing environment.
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.3 LANE anywhere along the path between the client and the DHCP server. RIF stripping should be enabled on the first non-token ring port in the path. The number of bridges on the path does not matter.
UDP Relay Configuration Screen UDP Relay Configuration 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 BOOTP/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 authenticated groups as well. See BOOTP/DHCP Relay and Authentication on page 26-5 and the Authentication Services chapter of the Switched Network Solutions User Manual.
BOOTP/DHCP Relay 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 environments. The first is the IP protocol policy that puts all IP type frames into a single VLAN regardless of network address. The second is the IP network policy that groups IP users based on their specific IP address.
BOOTP/DHCP Relay External BOOTP Relay The BOOTP relay may be configured on a router that is external to the switch. In this application 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. The DHCP server resides behind an external network router, which supports the BOOTP relay functionality.
BOOTP/DHCP Relay 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. All network clients are DHCP-ready and the DHCP server resides on just one of the groups.
BOOTP/DHCP Relay 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. All the DHCP-ready clients in group 3 must be members of the same VLAN, and the switch must have the BOOTP relay function configured.
BOOTP/DHCP Relay 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. ♦ Note ♦ This configuration works if you require only one DHCP subnet. All clients received on the same router port will be assigned to the same VLAN.
BOOTP/DHCP Relay Forward 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. This value may range from 1 to 65535. Maximum Hops The maximum number of relays that a packet can go through while traversing the network. This limit keeps packets from “looping” through the network.
NetBIOS Relays NetBIOS Relays The switch supports a UDP relay function that allows Network Basic Input/Output System (NetBIOS) messages to be sent across groups or VLANs. Overview of NetBIOS NetBIOS is an applications interface that allows computers on Ethernet or token ring LANs to communicate with one another. An enhanced version of the protocol is used by networking operating systems such as LAN Manager and Windows NT. With NetBIOS, each client and host in the LAN has a unique NetBIOS name.
NetBIOS Relays NetBIOS Relay Application The UDP relay function in the switch extends b-node functionality across the internet. An example application is shown here. Omni Switch/Router 12345678 123456 UDP Relay Group 2 VLAN 10 VLAN 20 IP Network 125.0.0.0 125.0.0.1 125.0.0.2 NBNS server NBDD server IP Network 130.0.0.0 125.0.0.3 b-node 130.0.0.1 130.0.0.2 b-node b-node 130.0.
NetBIOS Relays 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. The relays are enabled from the UDP Relay Configuration screen and are configured in similar ways. The UDP Relay Configuration screen is displayed using the relayc command described in UDP Relay Configuration Screen on page 26-3.
NetBIOS Relays Next-Hop Addresses 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. To add a next-hop address for NBNS relay: 1. On the UDP Relay Configuration screen command, enter the following: 21=l A screen similar to the following displays: FORWARD TO Server List Item 1) Server address 172. 28. Server Name (if known) 5.
NetBIOS Relays Forwarding 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. To select forwarding VLANs for NBNS relay: 1. On the command line of the UDP Relay Configuration screen, enter the following: 22=l A screen similar to the following displays: Available/Selected VLANS Item Group ID:VLAN ID MASK 1) 1:1 255.255. 0. 0 * = selected for forwarding IP ADDR 172. 23. 9.
NetBIOS Relays 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 Next-Hop Addresses 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. To add a next-hop address for NBDD relay: 1. At the command prompt for the UDP Relay Configuration screen, enter the following: 32=a A screen similar to the following displays: FORWARD TO Server List Item 1) Server address 172. 28. Server Name (if known) 5.
NetBIOS Relays Forwarding VLANs for NBDD Relay You may select or deselect VLANs to which the NBDD relay will forward. At least one forwarding VLAN (or a next-hop address as described in Next-Hop Addresses for NBDD on page 26-17) must be configured for the relay. To select forwarding VLANs for NBDD relay: 1. On the command line of the UDP Relay Configuration screen, enter the following: 32=a A screen similar to the following displays: Available/Selected VLANS Item Group ID:VLAN ID MASK 1) 1:1 255.255. 0.
Generic Service UDP Relay 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. You will need to know the well-known UDP port number if you want to configure these services. Generic Services Menu To configure a relay for a generic service, on the command line for the UDP Relay Configuration screen, enter 4.
Generic Service UDP Relay Forward 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. You can list forwarding VLANs, or add or delete VLANs from the forwarding list by entering 434=l, 434=a, or 434=d on the command line. To configure a generic service: 1. On the Add new Generic Service menu, enter a description of the generic service.
Generic Service UDP Relay Modifying 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: Item (1) State enabled Configured Generic Services Port Number Description 80 TFTP Servers/Vlans 198.172. 5. 4 Enter item number of service to be modified [‘h’ for help/ to exit] : The parameters are defined here.
Generic Service UDP Relay 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. The Configured Generic Services screen displays similar to the following: Item (1) State enabled Configured Generic Services Port Number Description 80 TFTP Servers/Vlans 198.172. 5.
Viewing UDP Relay Statistics Viewing 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 Chapter 25, “IP Routing.” The screen display for UDP statistics is similar to the following: UDP RELAY PACKETS RECEIVED/TRANSMITTED SERVICE PORT 1 67/68 2 137 PKTS RCVD 0 6 RCV RATE(pkts/s) 0.000 0.010 PKTS XMTD XMT RATE(pkts/s) 0 0.000 0 0.
Viewing UDP Relay Statistics Page 26-24
27 IPX Routing Introduction 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. IPX is a layer 3 protocol developed by Novell for interconnecting NetWare clients and servers. (NetWare is Novell’s network server operating system.
Introduction IPX Routing Overview In IPX routing, the switch builds routing tables to keep track of optimal destinations for traffic it receives that is destined for remote IPX networks. The switch sends and receives routing messages, or advertisements, to/from other routers in the network. When the switch receives an IPX packet, it looks up the destination network number in its routing table. If the network is directly connected to the switch, the switch also checks the destination node address.
Introduction 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 steps for setting up IPX routing on the switch are given here: Step 1.
The IPX Submenu 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.” To display the IPX submenu, enter the following commands: IPX ? If you have enabled the verbose mode, you don’t need to enter the question mark (?).
Viewing the IPX Routing Table Viewing the IPX Routing Table 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 manually. All entries in the table are sorted by destination network. The IPX Routing Table can contain a maximum of 2,010 routes.
Viewing the IPX Routing Table 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. GP:VL The first number is the Group associated with this entry; the second number is the VLAN associated with this entry. This identifies the interface used when sending traffic to the destination network.
Viewing the IPX Routing Table 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. (The examples shown below came from a switch that contained a Frame Relay board and an ISDN board.
Viewing IPX Statistics Viewing IPX Statistics The ipxs command is used to display data on IPX statistics and errors.
Viewing IPX Statistics 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). pkts discarded: The number of discarded packets. The number of packets that could not be forwarded because a route to the destination IPX network could not be found.
Viewing the IPX SAP Bindery Viewing the IPX SAP Bindery The ipxsap command is used to display a listing of the servers in the SAP Bindery, sorted by server name. To display a list of SAP servers, enter the following command: ipxsap A screen similar to the following displays: Displaying all (3) entries in the SAP bindery: Server Name Develop Finance Marketing Type 0004 026b 0278 Address 67.000000000001 67.000000000001 67.
Viewing the IPX SAP Bindery Using IPXSAP with Frame 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 Peer ID The Slot, Port and Virtual Connection (i.e., DLCI) identifiers or the PPP Peer ID of the interface on which the server information was received.
Adding an IPX Static Route Adding an IPX Static Route The aipxsr command is used to add IPX static routes to the switch’s IPX Routing Table. You might want to add a static route to send traffic from a node in an Omni Switch/Router VLAN to an external IPX network address (such as an address reached through an external network router attached to the switch). In order to add a static route, you will need to know the host/net and the gateway which will be used to route traffic there.
Removing an IPX Static Route Removing 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. Enter y at this prompt (or press ) to display the current routing table.
Turning the IPX Router Complex On and Off Turning 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. The ipxon command is used to turn on the IPX Router Complex, which enables IPX routing on the switch.
Flushing the IPX RIP/SAP Tables Flushing the IPX RIP/SAP Tables The ipxflush command is used to flush the IPX RIP Routing and SAP Bindery Tables. Follow the steps below to flush both the IPX tables. 1. Enter ipxflush. A screen similar to the following displays: Flush tables (RIP routing and SAP bindery) in: { RIP and SAP(b), RIP only(r), SAP only(s)} (b) : 2. Enter b (or just press Enter) to flush both tables. Enter r to flush just the Routing Table. Enter s to flush just the SAP Bindery Table.
Using the IPXPING Command Using the IPXPING Command The ipxping command is used to test the reachability of certain types of IPX nodes. The software 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.NLM. This type cannot be used to reach NetWare workstations running IPXODI. Novell uses a unique type of ping for this purpose (implemented by their IPXPNG.
Using the IPXPING Command 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. The default is the Novell type. 7. After answering the previous prompt, a message similar to the following displays: IPX Ping starting, hit to stop PING 304.00:20:da:05:f6:94: 64 data bytes [0 [50 [100 [150 [200 ] ] ] ] ] ..... .....
Configuring IPX RIP/SAP Filtering 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. By using IPX RIP/SAP filters, you can minimize the number of entries put in the IPX RIP Routing and SAP Bindery Tables, improve overall network performance by eliminating unnecessary traffic, and control users’ access to NetWare services.
Configuring IPX RIP/SAP Filtering Adding a “Global” IPX RIP/SAP Filter Follow the steps below to add a “global” 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 a (or just press ) to select to add a filter. 2.
Configuring IPX RIP/SAP Filtering 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 to use the default of all services). 9. A message will confirm the addition of the filter: ipxfilter successfully added Adding an IPX RIP/SAP Filter for a Specific Group or VLAN Follow the steps below to add an IPX RIP or SAP Output or Input filter for a specific Group or VLAN. 1.
Configuring IPX RIP/SAP Filtering 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 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. 8.
Configuring IPX RIP/SAP Filtering 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. 2.
Configuring IPX RIP/SAP Filtering Displaying IPX RIP/SAP Filters 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. You can enter optional parameters with the ipxf command to display specific filters.
Configuring IPX RIP/SAP Filtering GP:VL (s/p/vc) or (Peer 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.” If an entry refers to a Frame Relay interface, column headings for slot, port, and virtual circuit (s/p/vc) may be displayed when the filter is applied to a particular virtual circuit rather than to the entire VLAN.
Configuring IPX RIP/SAP Filtering 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: Displaying all global RIP INPUT filters: # Type Net/Mask Node/Mask ------ ------------ ---------------------- ----------------------------------3 RIP IN 67/ffffffff GP:VL (s/p/vc) Svc Md (Peer ID) ------ ---- -------------------B global IPX RIP/SAP Filter Precedence Whenever you use multiple “allow” filters you must first defi
Configuring IPX Serialization Packet Filtering Configuring IPX Serialization Packet Filtering The ipxserialf command is used to enable and disable IPX Serialization Packet filtering on any or all WAN routing services. This feature can be used to reduce traffic on WAN links by preventing the transmission of NetWare serialization packets. Novell uses a serialization mechanism to make sure that licensed copies of NetWare are not improperly copied to multiple servers.
Configuring IPX Serialization Packet Filtering 5. Filtering will then become active. A message will appear indicating that IPX Serialization Filtering is enabled, either on all WAN routing services or for a specific Group: IPX Serialization Filtering is now enabled on all WAN routing services Disabling IPX Serialization Filtering Follow the steps below to disable IPX Serialization Packet Filtering. 1. Enter ipxserialf.
Configuring IPX Watchdog Spoofing Configuring IPX Watchdog Spoofing The ipxspoof command is used to enable and disable IPX Watchdog Spoofing on any or all WAN routing services. The use of this feature is explained below: Novell’s IPX Watchdog Protocol, which is used by NetWare to maintain network node and server connections, can consume significant network bandwidth and thereby incur costs on expensive dial-on-demand, pay-per-packet WAN links.
Configuring IPX Watchdog Spoofing 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. 5. IPX Spoofing will then become active.
Configuring SPX Keepalive Spoofing Configuring SPX Keepalive Spoofing The spxspoof command is used to enable and disable SPX Keepalive Spoofing on any or all WAN routing services. The use of this feature is explained below: Novell’s SPX Keepalive Protocol, which is used by NetWare to maintain SPX connections between end nodes, can also consume significant network bandwidth and thereby incur unnecessary costs on expensive dial-on-demand, pay-per-packet WAN links.
Configuring SPX Keepalive Spoofing 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. This example prompt asks if you want to enable SPX spoofing on all WAN routing services. If you had entered a specific Group number, the prompt would refer to that particular Group.
Controlling IPX Type 20 Packet Forwarding Controlling IPX Type 20 Packet Forwarding The ipxtype20 command is used to control the forwarding of IPX Type 20 packets. The default setting is to not forward IPX Type 20 packets. You can use the ipxtype20 command to explicitly enable the forwarding of Type 20 packets for individual interfaces routing IPX traffic. Type 20 packets contain the value 20 (14 hex) in the “packet type” field of the IPX header.
Configuring NetWare to Minimize WAN Connections Configuring NetWare to Minimize WAN 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. Doing so will reduce the costs associated with each connection that is made. Some suggested approaches are described below. 1. NetWare Directory Services (NDS), included in NetWare 4.x, includes a time synchronization protocol.
Configuring NetWare to Minimize WAN Connections 6. Novell has developed a workaround that can be used to disable the SPX Watchdog mechanism. This workaround could be used instead of enabling the SPX Spoofing feature on your switch. SPWXDOG.NLM is a patch that is used to disable NetWare’s SPX Watchdog mechanism on 3.x and 4.x servers. The patch adds the following file server set parameter: “set spx watchdogs=ON/OFF” (The default is ON.
Configuring RIP and SAP Timers Configuring RIP and SAP Timers 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. Adding a RIP and SAP Timer 1. To adjust the time between RIP and SAP messages, enter the following command at the system prompt: ipxtimer The following prompt displays: Add or delete entry {add(a), delete(d)} (a) : 2.
Configuring RIP and SAP Timers Viewing RIP and SAP Timers To view the RIP and SAP timers that have been configured through the ipxtimer command, enter the following command: ipxt A screen similar to the following displays: # === 1 2 Group ====== 1 global RIP Timer (secs) SAP Timer (secs) ============== =============== 30 15 45 45 The fields are defined as follows: Group Displays the group number or global to indicate all groups.
Configuring Extended RIP and SAP Packets Configuring Extended RIP and SAP Packets 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. Use the ipxext command to enable or disable extended packets or to view the current status of extended packet transmission.
Configuring an IPX Default Route 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. Use the ipxdrt command to add a default route, view the status of a default route, or disable the default route. Adding an IPX Default Route To configure a default route, use the ipxdrt command with the relevant network ID.
28 Managing WAN Switching Modules Introduction 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. These modules support a variety of protocols, including Frame Relay, synchronous Point to Point Protocol (PPP), and Integrated Services Digital Network (ISDN).
Introduction Type of Service (ToS) 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. This can be done by assigning a priority value for the Voice Data and Voice Signaling Data fields. There are two methods of specifying the ToS priority: IP Precedence and Differentiated Services Code Point (DSCP).
Introduction 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: Hexadecimal Settings IP Precedence Value Hexadecimal Value DSCP Value Hexadecimal Value 0 0 0 0 1 20 10 (AF11) 28 2 40 18 (AF21) 48 3* 60 26 (AF31)* 68 4** 80 34 (AF41)** 88 5*** a0 46 (EF)*** b8 6 c0 54 d8 7 e0 62 f8 *Default settings for signalling data.
Introduction ToS 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. WAN ToS policies are supported when bridging or routing; ToS policies configured through the QoS Manager are only supported for routing.
Introduction 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. The DTR Dial Backup feature will allow another synchronous serial interface to be used for the backup purpose. The process is analogous to the ISDN backup feature.
Supported Physical Interfaces Supported Physical Interfaces The WSX family of products support numerous physical interface (port) types. The port types available with the WSX family are: Universal Serial Port The Universal Serial Port (USP) provides connectivity to legacy synchronous serial port devices. With the addition of an adapter cable, it supports RS-232, RS-449, RS-530, V.35 and X.21 Data Terminal Equipment (DTE) and Data Carrier Equipment (DCE) interfaces at speeds up to 2.048 Mbps.
Supported Protocols Supported Protocols 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.” For more details on implementing these protocols, see Chapter 29, “Managing Frame Relay,” and chapter 30, “Point-to-Point Protocol.
Application Examples 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. Extensive statistics are provided at each level, including a breakdown of traffic by frame type (Ethernet, IP, IPX, or BPDU) at the virtual circuit or PPP connection level.
Application Examples Combined Frame 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. The WSX connects to a DSU/CSU or T1 multiplexer through a serial cable.
Omni Switch/Router WAN Modules Omni Switch/Router WAN 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. In addition, hardware compression is also supported.
Cable Interfaces for Universal Serial Ports Cable Interfaces for Universal Serial Ports 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.35 • X.21 (European) All cable types (except RS-232) are capable of access rates from 9.6 kbps to 2 Mbps. The RS232 cable is not compatible with speeds greater than 64 kbps.
Data Compression Data Compression 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. In addition, the compression processor (STAC 9705) has its own memory (DRAM) that can store up to 100 compression histories (on a 4-port WSX) without degrading performance. An 8-port WSX can store up to 200 compression histories without performance degradation.
Loopback Detection 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, loopback detection involves periodically transmitting a message and looking for that message to be received.
The WAN Port Software Menu The WAN Port Software Menu User interface commands for the WSX board are on a separate menu that is accessed through the wan command. The WAN Port menu is a submenu of the Interface menu.
The WAN Port Software Menu Serial Port 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 ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS .................................................................................
The WAN Port Software Menu If the interface was using PPP, the following screen would display: 1) Admin Status ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS ................................................................................. 2048000 {9600, 19200, 56000, 64000, 128000, 256000, 512000, 768000} {1024000, 1544000, 2048000} 3) Clocking ........................................................................................
The WAN Port Software Menu 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.e., DCE cable plugged into the submodule port). If the submodule port is a physical DTE port, clocking will default to External.
The WAN Port Software Menu 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 submodule then uses this signal to clock in data from the external DTE device.
The WAN Port Software Menu TOS for Voice 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). Enter 0 to disable this feature. See Type of Service (ToS) on page 28-2 above for a more detailed explanation of ToS. TOS Mask for both TOS Value Set the mask bits for both voice data and signaling data. Enter 0 to disable this feature.
The WAN Port Software Menu 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 valid range is 0-255. Connection Function On serial ports using PPP, it is possible to configure the port to be a DTR dial backup port.
The WAN Port Software Menu ISDN-BRI Port 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 ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS .................................................................................
The WAN Port Software Menu 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. A full T1 line would have an access rate of 1,544,000 bps, and a full E1 line would have an access rate of 2,048,000 bps.
The WAN Port Software Menu You can set up the external DCE this way by configuring its DTE, or dataport, configuration options. Set the “Transmit Clock Source” to “External.” In this mode of operation, the transmit clock is output by the DCE device and the submodule turns it around on the external transmit clock back to the DCE, eliminating any phase misalignment between transmit clock and transmit data.
The WAN Port Software Menu TOS for Voice 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). Enter 0 to disable this feature. See Type of Service (ToS) on page 28-2 above for a more detailed explanation of ToS. TOS Mask for both TOS Value Set the mask bits for both voice data and signaling data. Enter 0 to disable this feature.
The WAN Port Software Menu If the interface was using PPP, the following screen would display: 1) Admin Status ................................................................................. UP {(U)p, (D)own} 2) Speed in BPS ................................................................................. 1544000 3) Clocking ........................................................................................ External {(I)nternal, (E)xternal, (S)plit} 4) Protocol Type ..................................
The WAN Port Software Menu 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. T1/E1 Number of Time Slots This field specifies the total number of 64 kbps time slots to use on the T1 or E1 connection. For a full T1, set this number to 24.
The WAN Port Software Menu KeepAlive 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. 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 valid range is 0-255.
The WAN Port Software Menu Viewing Parameters for all Ports 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 Viewing Port Parameters To view port parameters, enter the following command: wpview 3/ where 3 is the slot number for WAN uplinks, and is the port number for which you want to view information (either 1 or 2). The following three examples show the configuration setup screens for a fractional T1 port, a universal serial port, and an ISDN-BRI port. The display is slightly different depending upon the encapsulation type, either Frame Relay or PPP.
The WAN Port Software Menu 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. 1) Admin Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2) Protocol Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3) T1/E1 Starting Time Slot . . . . . . . . . . . . . . . . . . . . . . . . . .
The WAN Port Software Menu 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. TOS for Voice Signaling Data Shows the priority for voice signaling data streams.
The WAN Port Software Menu Universal Serial Port 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. 1) Admin Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2) Speed in BPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The WAN Port Software Menu 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. Receive Clock Often, due to delays added to timestamps in when running through switch hardware, the receive clock time is significantly different than expected from the transmitting data source. To correct the problem, it is possible to set the receive clock to invert the delay information.
The WAN Port Software Menu 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 millisecond increments that the pulse lasts. This only displays if the port is using PPP as its encapsulation type. DTR Pulse Count 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 WAN Port Software Menu ISDN-BRI Port 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. 1) Admin Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2) Speed in BPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3) Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The WAN Port Software Menu 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. TOS for Voice Signaling Data Shows the priority for voice signaling data streams.
The WAN Port Software Menu Deleting Ports 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. To delete a port configuration, enter the following command: wpdelete slot/port in which slot is the slot number for the WSX board and port is the port number on the WSX board that you want to delete.
The WAN Port Software Menu 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 wpstatus command is used to provide this information. This information includes types of physical interface, access rate of the Frame Relay line, and errors. In addition, the wpstatus command can display the number of frames received and transmitted.
The WAN Port Software Menu 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: (V.35 DTE cable) (V.35 DCE cable) 232DTE (RS-232 DTE cable) 232DCE (RS-232 DCE cable) X21DTE (X.21 DTE cable) X21DCE (X.
The WAN Port Software Menu 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. Virtual circuits on this port share this bandwidth. Usually, the WSX port will be a physical DTE device and the speed will be determined by the DSU.
The WAN Port Software Menu 8-Port WSX Board Example In this example, the board in slot 5 is an 8-port WSX board.
The WAN Port Software Menu 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. Please refer to this section for detailed information. Frames In The total number of frames received on this port since the last time the switch was initialized.
The WAN Port Software Menu Frame Relay Example 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: Frame Relay Status for slot 4, port 1: Applicable to all port types. Physical Level Information. Displays for serial ports only Logical (Frame Relay) Information Administrative/Operational Status ..................Up/Up Port Type .......................................
The WAN Port Software Menu 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: ......... UP/UP Port Type ............................................ Universal Serial Port Protocol ..............................................
The WAN Port Software Menu ♦ 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
29 Managing Frame 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.9. The WSX supports all three major DLCMI management protocols. WSX frame relay extends the power and flexibility of LAN switching over large geographic distances using a Frame Relay network or a leased line, such as a T1.
The WSX supports automatic detection of cable types attached to universal serial ports. It also supports three types of DLCMI management: LMI Rev. 1.0, ANSI T1.617 Annex D, and CCITT/ ITU-T Q.933 Annex A. Software in the switch allows you to configure access rate, clocking, DLCMI type, compression, and congestions controls, such as the Committed Information Rate (CIR). Additional software commands allow you to view the status of the Frame Relay connection at the WSX board, port, or virtual circuit level.
Back-to-Back Frame 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. No special user configuration is necessary for back-to-back connections. The WSX software automatically detects that a Frame Relay Logical DCE (i.e.
Universal Serial Port Cable Interfaces Universal Serial Port 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 following interfaces: • RS-232 • RS-449 • RS-530 • V.35 • X.21 (European) All cable types, except RS-232, are capable of access rates from 9.6 Kbps to 2 Mbps. The RS232 cable is not compatible with speeds greater than 64 Kbps.
Compression Compression 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. In addition, the compression processor (STAC 9705) has its own DRAM that can store up to 100 virtual circuits (on a 4-port WSX) without performance degradation. An 8-port WSX can store up to 200 virtual circuits without performance degradation.
Virtual Circuits and DLCIs Virtual Circuits 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). Static PVCs are user-configured and consist of Management, or Control, PVCs and any configured Data PVCs. Management VCs are used by the WSX to communicate with the Frame Relay network.
WSX Self-Configuration and Virtual Circuits WSX Self-Configuration and Virtual Circuits The following diagram summarizes the self-configuration features of the WSX. This example assumes no configuration parameters are entered for the WSX. Default bridging is set up on Group 1, and no Routing or Trunking are configured. WSX Cable plugs into WSX serial port. WSX ➊ The WSX sends STATUS ENQUIRY ➌ message to Frame Relay network.
Congestion Control Congestion Control 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. However, Frame Relay uses several software-configurable parameters and techniques to control congestion and to avoid data loss on the network during these heavy periods. These software parameters are set on a VC-by-VC basis. This section describes these parameters.
Congestion Control 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). If congestion in the network nears saturation, those frames tagged with the DE bit will be dropped before untagged frames. Unless totally congested, data below the CIR level on all virtual circuits is usually guaranteed delivery.
Congestion Control 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. The shaded area just above the white area contains frames that are stamped for Discard Eligibility that will get through as long as the VC is not congested.
Congestion Control Notification 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. When a queue is full, due to congestion, frames will be dropped. The senders of this data (Bridge/Router or WSX) may not be aware of the congestion.
Congestion Control Notification 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. However, it is set by the Frame Relay network in frames that are actually experiencing congestion.
Frame Formats Supported Frame 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. The following standard 1490 frame types are supported: • BPDU • Ethernet 802.3 • Token Ring 802.
Bridging Services 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. However, configuration is necessary for a VC to support Frame Relay Routing, Trunking, or Bridging on a Group other than Group 1. For bridging there is a one-to-one map between Frame Relay virtual circuits and switch virtual ports.
Frame Relay IP Routing Frame 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. In fact, the only address in a routed Frame Relay frame is the DLCI, or virtual circuit identifier. The DLCI is the main indentifier for source and destination addresses.
Frame Relay IP Routing An InARP message is sent between the two routers indicating their IP addresses and associated 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 routing of RIP frames, etc. The Frame Relay Subnet and “Split Horizon” The IP protocol must account for the Frame Relay network in making routing decisions.
Frame Relay IP Routing 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. Subnet 1.1.1.X WSX New virtual circuit added for routing to Subnet 4.4.4.x. Subnet 2.2.2.X WSX R Subnet 4.4.4.X Subnet 3.3.3.X How will Subnets 4.4.4.x and 3.3.3.x route to each other? Adding A New Router Raises New Questions The new WSX attached to Subnet 4.4.4.
Frame Relay IPX Routing Frame 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 “gleaning” to determine routing information. In gleaning, the IPX routing protocol on one end of a virtual circuit obtains the network node number for the router at other end of the virtual circuit. A WSX or router continuously receives RIP and SAP updates on a given virtual circuit.
Trunking Trunking 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. The WSX in Los Angeles has two trunk ports, one to Chicago and one to New York. Omni Switch/Router Chicago Gp. 3 WSX Trunk port attaches to VC to Los Angeles. Groups 3 and 4 Trunked. Gp.
Frame Relay Fragmentation Interleaving Frame Relay Fragmentation Interleaving The fragmentation interleaving feature allows for the transmission of higher priority traffic to be expedited by setting a maximum frame size. If lower priority traffic exceeds the set frame size value, it is fragmented into smaller pieces less than or equal to the set maximum frame size. When the fragmentation feature is enabled, frame traffic is examined for priority. High priority traffic is not fragmented.
The Frame Relay Software Menu The Frame Relay Software Menu User interface commands for Frame Relay are on a separate menu that you can access through the fr command. The Frame Relay menu is a sub-menu of the Interface/WAN menu.
Setting Configuration Parameters Setting Configuration Parameters 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. Commands generic to the WSX module can be found in Chapter 49. By default the WSX frame relay software uses ANSI T1.617 Annex D for the Data Link Control Management Interface (DLCMI) and uses a Committed Information Rate (CIR) of 0.
Setting Configuration Parameters 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 ……………………………………..……….. = Up {(U)p, (D)own} 3) DLCMI Type ………………………………………………………….. = ANSI T1.617 Annex D {(L)MI Rev. 1.0, T1.617 Annex (D), Q.933 Annex (A), (N)one } 31) LMI Procedure Type ................................................
Setting Configuration Parameters 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. The following sections describe the options you can alter through this menu.
Setting Configuration Parameters 31) LMI Procedure Type This field specifies the Local Management Interface (LMI) procedure type for this Frame Relay port. You have three choices for the LMI procedure type. The letters used in the frmodify screen correspond to the following: B Bidirectional U User (the default) N Network Enter your choice by specifying the letter corresponding to your choice.
Setting Configuration Parameters 6) Error Threshold 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. These errors may include timeouts from STATUS ENQUIRY polls and invalid STATUS messages returned from the Frame Relay network. By default, this threshold is set to 3, which is the standard Frame Relay default value.
Setting Configuration Parameters 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. If you set this value to 0 (the default value), then virtual circuits will not perform Routing unless specifically assigned to a Routing service. This option is intended to simplify Routing configuration if you do not need to route many Groups over a Frame Relay physical port.
Setting Configuration Parameters 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. The number of retries can range from 3 to 255. The default is 10. This default can be by using the frmodify command on an individual virtual circuit.
Setting Configuration Parameters Modifying a Virtual Circuit To modify a virtual circuit, enter the following command: frmodify // where is the slot number where the WSX board is located, is the port number on the WSX board, and is the number used to identify the virtual circuit that you want to modify.
Setting Configuration Parameters 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. This option should only be modified by experienced Frame Relay network administrators.
Setting Configuration Parameters 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 negotiation messages as many times as you indicate in the Compression PRetry Count. The time between these tries in indicated in this field. The number of seconds between retries may range between 1 and 10 seconds. The default is 3 seconds.
Adding a Virtual Circuit Adding a Virtual Circuit Data virtual circuits and their DLCIs 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. In such a case you will need to use the fradd command to set parameters for the virtual circuit. The information for the virtual circuit will be stored in the WSX database.
Viewing Configuration Parameters for the WSX Viewing Configuration Parameters for the WSX You can view all current parameters for a WSX port or an individual virtual circuit using the frview command. These parameters will be either the default parameters or parameters you modified using the frmodify command or network management software. You have a choice of viewing parameters at the chassis, port or DLCI (virtual circuit) level.
Viewing Configuration Parameters for the WSX Viewing Port Parameters To view port parameters, enter the following command frview / where is the slot number where the WSX board is located, and is the port number on the WSX board on which you want to view information.
Viewing Configuration Parameters for the WSX Viewing Virtual Circuit Parameters To view virtual circuit parameters, enter the following command frview // where is the slot number where the WSX board is located, is the port number on the WSX board, and is the number used to identify the virtual circuit that you want to view.
Deleting Ports and Virtual Circuits Deleting Ports 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. You can use the frdelete command to delete: • a single virtual circuit, or • a port and all of its associated virtual circuits The frdelete command always requires you to indicate at least a slot and port number.
Deleting Ports and Virtual Circuits Deleting a Port 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. The port is not logically deleted, and can still be reconfigured after the delete. To truly “delete” a port you must disconnect its cable or set its Administrative Status to Disable.
Obtaining Status and Statistical Information 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. The frstatus command is used to provide this information. This information includes types of physical interface, access rate of the Frame Relay line, and errors.
Obtaining Status and Statistical Information 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 display in this column • • • • • • • • • • (V.35 DTE cable) (V.35 DCE cable) 232DTE (RS-232 DTE cable) 232DCE (RS-232 DCE cable) X21DTE (X.21 DTE cable) X21DCE (X.
Obtaining Status and Statistical Information Clocking This field indicates the type of clocking used to clock transmit and receive data in and out of the serial port. When the clock is out-of-phase, you receive errors. If this value is set to External, then clocking is controlled by the external DCE (a DSU or other DCE device on the other end of the cable from the WSX port). External clocking is the default option when the WSX is a physical DTE device (i.e., controlled by an external DCE device).
Obtaining Status and Statistical Information VCs Active/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. The first number is the number of active VCs and the second is the number of inactive VCs. An Active virtual circuit is one that is operationally Up and capable of transmitting data; it may not necessarily be transmitting at this time.
Obtaining Status and Statistical Information Information on the Ports for One WSX Board 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 where is the slot number where the WSX board is installed.
Obtaining Status and Statistical Information Information on One Port To obtain status information on a single WSX port, you enter the frstatus command along with the slot number for the WSX board and the port number for which you want to receive information, as follows: frstatus / where is the slot number where the WSX board is installed and is the port number on the WSX board.
Obtaining Status and Statistical Information Frame Relay Status for slot 3, port 1: Administrative/Operational Status …………………………………….. Up/Up Physical Level Information Speed BPS ======= 2048000 Control Signal Logical (Frame Relay) Information Intf.
Obtaining Status and Statistical Information Physical 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. The status indicator before the slash refers to the Administrative Status. If UP, then the port has been enabled and can transmit data as long as its Operational Status is also UP.
Obtaining Status and Statistical Information 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.) • RTS (Request To Send.) • DSR (Data Set Ready.) • CTS (Clear To Send.) • DCD (Data Carrier Detect.) The ON/OFF indicator below the signal name tells you the current status of the signal.
Obtaining Status and Statistical Information 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. The third row shows the cumulative number of octets that have passed through the port (sent and received). This statistic includes the data and Frame Relay header fields, but does not include CRC or flag characters.
Obtaining Status and Statistical Information 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 standard Frame Relay error types. Receive Short The receive frame was not long enough to allow demultiplexing. The address field was incomplete, or the protocol identifier was missing or incomplete.
Obtaining Status and Statistical Information DLCI Layer 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. This value is only valid locally; the same virtual circuit on the other end of the Frame Relay line may or may not use the same DLCI for this VC.
Obtaining Status and Statistical Information 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. Frag Size The maximum size of a frame if fragmentation is enabled. Frag Status Whether fragmentation is enabled or disable. In Frag The number of frame fragments received on this virtual circuit.
Obtaining Status and Statistical Information Information on One Virtual Circuit To obtain status information on a single virtual circuit, you enter the frstatus command along with the slot number for the WSX board, the port number, and DLCI number for the virtual circuit on which you want information, as follows: frstatus // where is the slot number where the WSX board is installed, is the port number on the WSX board, and is the virtual circuit identifier.
Obtaining Status and Statistical Information 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. The final table provides information on compressed data on this virtual circuit. The following sections describe information in the table.
Obtaining Status and Statistical Information 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. These frames experienced congestion coming over the virtual circuit. Statistics are given only for Frames In for FECN Bit since the Frame Relay network sets it. See Notification By FECN on page 29-12 for more information on the FECN bit.
Resetting Statistics Counters Resetting Statistics Counters 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. The frclear command is used to reset statistics.
Managing Frame Relay Services Managing Frame 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. See Setting Configuration Parameters on page 29-22 for information on the frmodify command. To extend your control over a Frame Relay service, you can use Service menu commands.
Managing Frame Relay Services 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. • Trunking See Trunking on page 29-19. The decision to set up one service over another is determined by your network configuration and amount of traffic.
Configuring a Bridging Service 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. The frmodify command allows you to change the default Bridging Group from Group 1 to another Group or to turn off bridging completely.
Configuring a Bridging Service 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. Enter a 4, an equal sign (=), and the DLCI number for the virtual circuit. The example below includes the virtual circuit with DLCI 16 in the bridging service: 4=16 Press . 6.
Configuring a WAN Routing Service Configuring a WAN 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.) 2. Set up a WAN routing service through the cas command. Both of these steps are described in the next two sections. Step 1.
Configuring a WAN Routing Service Step 2. Set Up a Frame Relay Routing Service You create a Frame Relay routing service using the cas command. Follow the steps below to set up a routing service. 1. Enter the cas command followed the slot number, a slash (/), the port number, and then the service number for the routing service: cas 2/3 1 A screen similar to the following displays: Slot 1 Port 2 Service 3 Configuration 1) Description ...................................................................
Configuring a WAN Routing Service 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 . You must have previously configured this Group as a Frame Relay Routing Group through the crgp command. If you have not configured the Group for Frame Relay routing, then the following message displays: Given Vlan Group is not a Frame-Relay Router Group See the section, Step 1.
Configuring a Trunking Service Configuring a Trunking Service To configure a Frame Relay Trunking service, you must use the cas command. Perform the following steps: 1. Enter the cas command followed the slot number, a slash (/), the port number, and then the service number for the Trunking service: cas 2/3 1 A screen similar to the following displays: Slot 1 Port 2 Service 3 Configuration 1) Description ...................................................................
Configuring a Trunking Service 5. You need to specify the DLCI for virtual circuit that will be used to trunk traffic over the Frame Relay network. Only one virtual circuit may be specified for each Trunking service. Enter a 4, an equal sign (=), and the DLCI number for the virtual circuit similar to the example below: 4=16 Press . 6. Specify the Group number or numbers that you want to be Trunked over the specified virtual circuit.
Viewing Frame Relay Services Viewing Frame Relay Services You can view all Frame Relay services for an entire switch, a single WSX board, or a single WSX port. Use the vas command with the following parameters: vas / The , and parameters are not required but may be specified to narrow the range of the information displayed.
Modifying a Frame Relay Service 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. For trunking services, multiple virtual ports can map to a single virtual circuit. Description The textual description given to this service when you set it up through the cas or mas command.
Deleting a Frame Relay Service Deleting a Frame 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. You can obtain the service number by using the vas command. See Viewing Frame Relay Services on page 29-64.
30 Point-to-Point Protocol The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. The base protocol is specified in RFC 1661. Many other RFCs define additional capabilities for network protocol negotiation, management information databases (MIBs), and PPP operation over different kinds of serial channels. PPP is comprised of three main components.
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. Compression is negotiated during the Network phase using Compression Control Protocol (CCP), which includes the negotiation of a data compression algorithm and any parameters specific to the algorithm. Once negotiated, all data packets (i.e.
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 • switched connection only Note One important thing to remember when setting up multilinks is that all links to be bundled must exist on the same slot. Permanent Connection Only This mode allows multiple links to be joined into a single bundle. Permanent connections can be universal serial ports or fractional T1/E1 ports.
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. As complete frames are received they will be forwarded to the normal PPP processing. When high priority frames are received, since they will always be sent complete, they will immediately be forwarded to the normal PPP processing. The only configurable parameter that has been added is the maximum delay.
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.” Step 2.
The PPP Submenu The PPP Submenu The WAN menu contains a submenu, named PPP, containing commands specific to the Pointto Point-Protocol (PPP).
Setting Global PPP Parameters Setting Global PPP Parameters 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. These global settings are not tied to a specific peer (i.e., a PPP Entity; see Adding a PPP Entity on page 30-9).
Setting Global PPP Parameters Default Compression Type 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. See Data Compression on page 30-2 for a description of STAC-LZS data compression. Default Bridge Config Admin Status Specifies whether the bridging function is to be negotiated for incoming calls.
Adding a PPP Entity Adding 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. When you enter the pppadd command, you may enter a Peer ID number with the command like this: pppadd Alternatively, you can enter the command alone and you will be prompted for a Peer ID. The prompt will identify the next available, unique ID number.
Adding a PPP Entity 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {(E)nable, (D)isable} 3) PPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {(N)ormal, (M)ultilink} 4) Compression Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a PPP Entity 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 convenience to you. The fields on the pppadd configuration screen have the following meanings: Description A textual description for this PPP Entity. You can enter any text you like (up to 30 characters). Administrative Status Indicates the Administrative Status of this PPP Entity. Enabled will allow the PPP Entity to operate.
Adding a PPP Entity Enabling Routing expands the menu with the following suboptions: 6) Routing Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {1-65535 or 0 if no Routing} 60) IP Config Admin Status . . . . . . . . . . . . . . . . . . . . . . . . . {(E)nabled, (D)isabled} 61) Remote IP Address (Only valid if IP is enabled) . . . . . {Valid IP address notation e.g., x.x.x.x} 62) IPX Config Admin Status . . . . . . . . . . . . . . . . . . . . . . . .
Adding a PPP Entity User ID sent to remote for Authentication Used to specify the User ID to be sent to the remote end during PAP or CHAP authentication. 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). Password sent to remote for Authentication Used to specify the password to be sent to the remote end during PAP or CHAP authentication. This parameter is used only for outgoing calls.
Adding a PPP Entity 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 Modifying 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, enter the following command: pppmodify p1 A screen similar to the following displays: Modify PPP for communication to Peer ID: 1 Enter PPP parameters: 1) Description : {Enter text up to 30 characters} 2) Administrative Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {(E)nable, (D)isable} 3) PPP Mode . . .
Viewing PPP Entity Configurations Viewing PPP Entity Configurations The pppview command is used to view the configuration parameters of existing PPP Entities.
Viewing PPP Entity Configurations 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 the Configuration of a Specific PPP Entity To view configuration information on a specific PPP Entity, you must enter a Peer ID number with the pppview command.
Displaying PPP Entity Status Displaying PPP Entity Status The pppstatus command is used to view the operational status of one or more PPP Entities.
Displaying PPP Entity Status 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. The reasons why the state may be closed are: 1) the call has been disconnected, 2) the protocol is in the process of making a connection, or 3) the Bridging option was not configured. CCP Oper State The operational state of the compression control protocol option.
Displaying PPP Entity Status 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. BCP Pkts IN/OUT The total number of BCP packets received (In) and transmitted (Out) for this PPP connection. CCP Pkts IN/OUT The total number of CCP packets received (In) and transmitted (Out) for this PPP connection.
Deleting a PPP Entity 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”). If you try to delete a PPP Entity that still has links associated with it, the following message will be displayed: Delete PPP Peer ID: 1 aborted because the following link(s) attach to it.
Deleting a PPP Entity Page 30-22
31 WAN Links Introduction 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 procedures described in this chapter comprise the third and final step in the three-step process for configuring the operation of PPP on your Omni Switch/Router (the complete three-step process was also described in Chapter 30).
The Link Submenu 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 interfaces. WAN links can either be “fixed” (i.e., configured for a serial port or T1/E1 port), or dialbased (i.e., configured for an ISDN port). The link UI commands also provide a means of modifying and viewing existing WAN Links and displaying their operational status.
Adding a WAN Link Adding a WAN 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). When the linkadd command is used to create links over WSX ports, all of the parameters needed to create the link are contained on one screen. However, when you select to create a link over an ISDN port, a second screen will be displayed after you enter and save the initial parameters on the first screen.
Adding a WAN Link Administrative 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. The options are “WSM Port,” which means a serial or Fractional T1/E1 connection and “ISDN,” which means an ISDN call will be used to make the connection. Link Slot Specifies the switch slot number to be used by this WAN Link.
Adding a WAN Link 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) 2) 3) 4) 5) Link Description : {Enter text up to 31 characters} Link Administrative Status . . . . . . . . . . . . . . . . . . . . . . . . . . {(E)nabled, (D)isabled} Link Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . {(W)SM Port, (I)SDN call} Link Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a WAN Link 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) 2) 3) 4) 5) 6) 7) Link Description : Link Entry: 1, Peer ID: 1 {Enter text up to 30 characters} Link Administrative Status . . . . . . . . . . . . . . . . . . . . . . . . . . = Enabled {(E)nabled, (D)isabled} Inactivity Timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a WAN Link 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. Maximum Call Duration The maximum call duration in seconds. An entry of zero (0) means “unlimited.” Outgoing Calls Sets whether outgoing calls can be made by this WAN Link.
Adding a WAN Link 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. You can also make changes to any of the other fields on this screen if they are needed to provide ISDN call information this WAN Link.
Modifying a WAN Link Modifying a WAN 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 subheading (Modifying ISDN Links) below shows the sequence of screens when modifying a link over a WSX port. The second subheading below (Modifying WSX Links on page 31-10) shows the sequence of screens when modifying a link over an ISDN port.
Modifying a WAN Link 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. Modifying WSX Links 1. To modify a WAN Link, you must enter its Link Index with the command. For example, to modify Link Index 2 which uses a WSX physical port (serial or Fractional T1/E1), you would enter the following command: linkmodify L2 A screen similar to the following displays: Modify Serial Port Link configuration.
Deleting WAN Links Deleting WAN 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. 1.
Viewing WAN Links Viewing WAN Links The linkview command is used to view information on existing WAN Link records. Displaying All Existing WAN Links To view information on all existing WAN Links, enter the following command: linkview A screen similar to the following displays: List of ISDN Port Type: Peer Link Link Link Id Index Mode Slot ==== ===== ===== ==== 1 1 DEM 4 2 2 BKP 4 Link Port ==== 2 2 Outgoing Incoming Called Num. Caller Id.
Viewing WAN Links Incoming Caller ID The phone number reported by the Caller ID service, if available. Peer 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. “Useful data” refers to forwarding packets (routing information) but not encapsulator maintenance frames. Zero (0) specifies no disconnection due to inactivity.
Viewing WAN Links Example of WSX 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) 2) Link Description : Link Entry: 1, Peer ID: 1 {Enter text up to 31 characters} Link Administrative Status . . . . . . . . . . . . . . . . . . . . . . . . . . = Enabled {(E)nabled, (D)isabled} The fields on this screen provide the same information as those on the linkadd screen.
Displaying Link Status Displaying Link Status The linkstatus command is used to display the operational status of WAN Links. Displaying Status for All WAN Links To view information on all WAN Links, enter the following command: linkstatus A screen similar to the following displays: Link Idx ==== 1 2 Peer Id ===== 1 2 Slot/Port ======== 4/2 4/2 Active Session: Setup Link Peer Time Index Id ==== ===== ==== 00:00 1 1 00:00 2 1 Last Setup Time ============== 00:00:00 03/97 00:00:00 03/97 Peer Conn.
Displaying Link Status 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. Call State The current call state.
Displaying Link Status 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. This field will be updated whenever a call is started or accepted.
Displaying Link Status Page 31-18
32 Managing ISDN Ports 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). The BRI interface can support only PPP. The Universal Serial Port on a WSX-BRI board is operationally identical to the USPs found on the 4- or 8-port WSX-S board. The ISDN BRI port is an RJ-45 connector.
“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 following are the main BRI reference points: The U interface is a two-wire (single pair) interface that supports full-duplex data transfer from the phone switch. Only a single device can be connected to a U interface. This device is called a Network Termination 1 (NT1) which converts the U interface to the S/T interface (described below).
The ISDN Submenu The ISDN Submenu The WAN menu contains a submenu, ISDN, containing commands specific to WSX-BRI ISDN ports.
Modifying an ISDN Configuration Entry Modifying an ISDN Configuration Entry The isdnm command is used to modify the parameters for a selected ISDN port. These parameters are typically provided by the telephone carrier or other service provider at the time the ISDN line is installed. 1. To modify a specific port, for example in Slot 4, Port 1, enter the following command: isdnm 4/1 A screen similar to the following displays: 1) 2) 3) 4) 5) Switch Type . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an ISDN Configuration Entry Deleting an ISDN Configuration 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. Although you cannot delete a physical ISDN port from the switch, you can remove the configuration entry that was recorded for a port. 1.
Viewing an ISDN Configuration Entry Viewing 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 Displaying ISDN Configuration 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 Displaying Status of a Specific ISDN Slot To view status information on all ISDN channels on a specific ISDN slot, for example, slot 4, enter the following command: isdns 4 A screen similar to the following displays: Status for ISDN D channel on slot: 4, Port: 1: LAPD OperStatus: Layer 1: Active, Layer 2 DataLink: Established. The number of incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying ISDN Configuration Entry Status 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. Connected means an incoming call is currently in the process of validation. Active means a call is currently active. Peer Address Indicates the ISDN address to which the current or last call is or was connected.
Displaying ISDN Configuration Entry Status Page 32-10
33 Managing T1 and E1 Ports 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. The following switching modules contain T1 or E1 ports: • WSX-FT1/E1 Ports on these modules share a common set on of physical level attributes and a common set of software configuration commands. T1/E1 configuration options include frame format, line coding, and Facility Datalink Protocol.
T1 and E1 Overview T1 and E1 Overview 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. Digital wide-area data networking uses the same digital services that were originally designed for digitized voice.
The T1/E1 Menu 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 Configuring a T1 Port 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. To configure a T1 port, enter the following command temod / where is the slot number where the board is located, and is the T1 port number on the board that you want to modify.
Configuring a T1 Port 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 application, this option must be chosen when configuring an “unstructured” circuit emulation service. Important Note You cannot use the unframed format on WAN modules. 3) Line Build Out Indicate whether the T1 port supports short haul or long haul interfaces.
Configuring a T1 Port 5) Facility Datalink Facility Datalink (FDL) gathers performance statistics every second and stores them in the 24hour 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). In order to obtain far-end, or remote, performance statistics (viewed through the terts, tercs, and teris commands), you must enable an FDL protocol.
Configuring a T1 Port 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. Framing functionality assembles T1 frames into SuperFrames and Extended SuperFrames, depending on how the port is configured. Possible values are as follows: none The port is not in a loopback state. This is the typical live network state for a T1 port.
Configuring an E1 Port Configuring an E1 Port 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 2) Frame Format 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 framing. E1-MF E1 frame using framing bits in both time slot 0 and time slot 16 multiframe for framing. E1-CRC-MF E1 frame using framing bits in time slot 0, time slot 16 multiframe, and CRC-4 multiframe for framing.
Configuring an E1 Port 6) Transmit 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 PLLs) is used as the transmit clock. The transmit clock source is related to the clocking mode used in circuit emulation services. In synchronous clock mode, both sides of the E1 connection will use a local clock source.
Viewing T1/E1 Configuration and Alarm Information Viewing 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. You have a choice of viewing parameters at the chassis or port level. You receive different displays depending upon which level you choose.
Viewing T1/E1 Configuration and Alarm Information 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. RcvLOMF This port is receiving loss of multiframe (LOMF) alarms from the far-end port.
Viewing T1/E1 Configuration and Alarm Information Viewing Information For a T1 Port To view T1 port parameters, enter the following command tes / where is the slot number where the board is located, and is the T1 port number on the board on which you want to view information.
Viewing T1/E1 Configuration and Alarm Information Out of Frame Events. The total number of out of frame events that have been detected on this port. An out of frame event occurs when two or more framing errors occur within a 3 microsecond period for Extended SuperFrame signals, or when two or more errors occur out of five or fewer consecutive framing bits. The signal will be back in frame when there have been fewer than two frame bit errors within a 3 microsecond period for Extended SuperFrame signals.
Viewing T1/E1 Configuration and Alarm Information Viewing Information For an E1 Port To view E1 port parameters, enter the following command tes / where is the slot number where the board is located, and is the E1 port number on the board for which you want to view information.
Viewing T1/E1 Configuration and Alarm Information 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. The signal will be back in frame when frame alignment signalling is normal for three consecutive frames. Red Alarm Events. The number of times this port has been in a Red alarm state.
Viewing T1/E1 Local Statistics Viewing 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. The following sections describe these commands.
Viewing T1/E1 Local Statistics 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). CSS. Controlled Slip Seconds. A one-second interval with one or more controlled slip errors. Controlled slip errors are the replication or deletion of the payload bits on a frame.
Viewing T1/E1 Local Statistics Viewing Local Historical Statistics The telis command allows you to display historical statistics for the past 96 15-minute intervals. Enter the following command telis / where is the slot number where the board is located, and is the port number on the board on which you want to view statistics.
Viewing T1 Remote Statistics Viewing 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. Note Because there is no FDL standard for E1 configurations, remote statistics are not supported on E1 ports.
Viewing T1 Remote Statistics Viewing Current Remote Statistics You can view remote statistics for the current 15-minute interval on a single port by entering the following command tercs / where is the slot number where the board is located, and is the port number on the board on which you want to view statistics.
Viewing T1 Remote Statistics Clearing the Framer Statistics for a T1/E1 Port The tecls command enables you to clear the accumulated physical-layer (Framer) statistics for a T1 or E1 port. To clear statistics, enter tecls / where is the slot number where the board is located, and is the port number on the board on which you want to clear statistics.
34 Backup Services Introduction 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. Initially, the primary entity may be either a physical port (any physical port type in the system), or a frame relay Private Virtual Circuit (PVC). The backup is via an ISDN BRI running Point-to-Point Protocol (PPP).
Backup Services Commands 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.g. bsadd or bsa may be used to create a backup service). Accessing the Backup Services Menu The Backup Services menu is a submenu to the Interface menu.
Backup Services Commands 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 Physical Port To add a backup service for a physical port: 1. Enter the bsadd command with no parameters, followed by .
Backup Services Commands : 30=2 : 31=1 : 40=5 : ? 1) Description: Backup 1 2) Admin Status { (E)nabled, (D)isabled } 3) Primary Type { Physical Port (1), Frame Relay PVC DLCI (2) } 30) Slot 31) Port 4) Backup Type { PPP Peer (1) } 40) Peer ID 5) Startup Timer Value { Time in Seconds after System Startup to wait for Primary to come up before activating Backup } 6) Activate Timer Value { Time in Seconds after Primary Failure to activate Backup } 7) Restore Timer Value { Time in Seconds after Primary restoral
Backup Services Commands 5) Startup Timer Value 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. Acceptable values are in the range of 0-65535 seconds. The default value is 300 seconds. 6) Activate Timer Value This field sets the amount of time that the primary entity must remain in a failed state before the backup entity is activated.
Backup Services Commands 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. To add a backup service for a frame relay PVC: 1.
Backup Services Commands : 3=2 1) Description 2) Admin Status { (E)nabled, (D)isabled } 3) Primary Type { Physical Port (1), Frame Relay PVC (2) } 30) Slot 31) Port 32) DLCI 4) Backup Type { PPP Peer (1) } 40) Peer ID 5) Startup Timer Value { Time in Seconds after System Startup to wait for Primary to come up before activating Backup } 6) Activate Timer Value { Time in Seconds after Primary Failure to activate Backup } 7) Restore Timer Value { Time in Seconds after Primary restoral to disable Backup } (sav
Backup Services Commands : 30=3 : 31=3 : 32=32 : 40=1 : ? 1) Description 2) Admin Status { (E)nabled, (D)isabled } 3) Primary Type { Physical Port (1), Frame Relay PVC (2) } 30) Slot 31) Port 32) DLCI 4) Backup Type { PPP Peer (1) } 40) Peer ID 5) Startup Timer Value { Time in Seconds after System Startup to wait for Primary to come up before activating Backup } 6) Activate Timer Value { Time in Seconds after Primary Failure to activate Backup } 7) Restore Timer Value { Time in Seconds after Primary restora
Backup Services Commands Modifying 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 Physical Port To modify a backup service for a physical port: 1. Enter the bsmodify command, followed by the index of the Backup service, followed by .
Backup Services Commands Modifying a Frame Relay PVC Backup Service To modify a backup service for a frame relay PVC: 1.
Backup Services Commands Viewing Backup Service(s) Configurations With the bsview command, you can view the configuration of either all backup services, or a single backup service.
Backup Services Commands Viewing Backup Service Statistics To view the statistics of a back service, enter the bsstatus command in the following manner: bsstatus b where b is the service index number assigned to the service when it was created. For example, to see the statistics for a backup service with an index number of 1, enter: bsstatus b1 A screen similar the following displays: Status for Backup Index: 1.
Backup Services Commands 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. The available options are Physical Port and Frame Relay PVC DLCI. Slot/Port/Dlci. The slot, port number, and DLCI number (if applicable) attached to this backup service. Bkp Type.
Backup Services Commands Page 34-14
35 Troubleshooting This chapter provides information that will help you troubleshoot Omni Switch/Router hardware and software problems. The sections within this chapter describe problems or errors you may encounter during switch hardware and software installation, configuration, or operation. Subsections within these categories reflect unique problems and provide the recommended corrective action(s). Common problems installing switch software and possible solutions are described on page 35-5.
Detecting Problems 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. Refer to Chapter 36, “Running Hardware Diagnostics,” for documentation on diagnostics software. And refer to the Text-Based Configuration CLI Reference Guide for documentation on CLI commands.
Reporting Problems Reporting Problems In some cases, you will not be able to correct the problem that occurs (for instance, a module failure). In such cases, you should contact Alcatel Technical Support at one of the following locations: West Coast: Alcatel Technical Support 26801 West Agoura Road Calabasas, CA 91301 Telephone: 1-800-995-2696 (Domestic) 818-878-4507 (International) Fax: 818-878-3505 Web: www.ind.alcatel.com/support Email: support@ind.alcatel.
Reporting Problems Report Software Details When reporting problems you should be ready to report the following software details to Alcatel Technical Support: • Software revision (e.g., 3.4.8, 4.3.
Understanding Problems Understanding Problems The following self-questions can be used to get a better idea on the nature of the problem: • Has this functionality ever worked? • What changes have occurred in the network? Was software upgraded? Were device(s) added? • Are all users affected or are the problems related to a single port, module, or switch? • Are statistics (as reported by UI commands such vs, ve, bps, and rmon) incrementing on the affected port(s)? • Are all protocols (routed or switched) fai
Operational Problems Operational 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. If, for example, you have a setup with three switches, as shown in the following figure, the VLAN can enter a deadlock.
Operational Problems To determine if this problem has occurred in your setup, you can use the vi command to display information about a specific port. (See Chapter 19, “Managing Groups and Ports,” for more information on the vi command.) The syntax for this command is as follows: vi / The system will show the port in Blocking mode and not in Forwarding mode. Probable Cause You did not configure the network from the point furthest away from the point of connection.
Operational Problems Protocol Problems You may notice an abnormal number of errors in a particular protocol. You can view protocol errors by using the networking commands. Refer to Chapter 25, “IP Routing,” for more information on the networking commands. Probable Cause Incompatible versions of the protocol are running on stations in the network. Solution Check the version of the protocol and verify that you are using the same version on all stations in the network.
Hardware Problems Hardware 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. Probable Cause The power supply has blown a fuse. Solution Call Alcatel Technical Support. Amber Color in LEDs During power-up, the switch goes through a Power-On Self Test (POST).
Hardware Problems TEMP LED is Amber If the TEMP LED is amber, the internal temperature of the switch has exceeded the operational limit. Solution Perform the following steps: 1. Turn off the switch and wait until it has completely cooled down. 2. Check the immediate environment and ensure that the switch is not located in an area where it can be overheated by other heat-producing devices. 3. Ensure that the switch is located in an area where there is ample room for air flow around the chassis.
Error Messages Error Messages This section provides error messages that you may encounter in the UI. Understanding Error Messages Error messages reflect hardware or software problems that the switch encountered during initialization, configuration, or operation. In some instances, the messages that display on the UI show the C program function name. For example: cmSetTTY(): Illegal port requested where cmSetTTY represents the function, and ( ) indicates that parameters are passed.
Error Messages Serial Port Configuration Errors 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”). Can’t modify SLIP if it’s not up! current mode=xxx Reconnect the SLIP line; reconfigure using the slipc command. Problem changing remote IP addr to xxx Check the remote IP address by using the slipc command at the UI.
Error Messages 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. Chassis Error Messages Table 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”). Unknown mod type xxx in slot Remove the module from the slot.
Error Messages Chassis Error Messages Table (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.
36 Running Hardware 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. The Omni Switch/Router have a variety of switching modules interconnected by a frame backplane and a management backplane. When a hardware failure occurs, the problem may be related to a number of different failures.
• 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 SUNI Register Test • tellreg Telluride Register Test • whsreg Whistler Register Test • wsmcable WSX Cable Connection Test • xcam Alcatel CAM Off-Board Test Running Diagnostics You must log in to the diag account to access the hardware diagnostics functionality or use the framefab and command.
Login to Run Diagnostics 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. The default password for the diag user is switch. Once logged in as a diag user, the Main Menu will display as follows.
Resetting a Switching Module 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. ♦ Notes ♦ Some NI modules do not support the reset command. The primary MPX module cannot be reset.
Temperature Masking Temperature 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. By default, temperature masking is disabled. To enable temperature masking, enter maskta enable This command masks the temperature alarm completely.
Running Hardware Diagnostics Running Hardware 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 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. The MPX verifies the packets on a bit by bit basis. See the description for stress test on page 36-8. If Ethernet type switch is tested, this test requires the desx.img file to be in the flash memory. mamcam Tests the Mammoth CAM.
Running Hardware Diagnostics 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. Once the packets are returned, modifications in the packets’ destination address allows the packets to continuously circulate between the NI CPU and the external cables or wrap plugs for a predefined period.
Running Hardware Diagnostics 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. The following command: test all 100 vram would run the VRAM test on all the modules in the chassis that are capable of executing the VRAM test for 100 times.
Running Hardware Diagnostics The table below provides specific cable/plug information for Omni Switch/Router switching modules. Omni Switch/Router Port Test Wrap 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. Port/Stress (Half Duplex) test: Multi-mode fiber optic cable with SC connectors. GSX-K-FS-2W Port (Full and Half Duplex) and Stress tests: Single-mode fiber optic cable with SC connectors.
Running Hardware Diagnostics Omni Switch/Router Port Test Wrap 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. WSX-SC-8W Twisted pair 28GA serial cable with HD50-26 connectors – DCE to DTE. WSX-BRI-SC-2W BRI S/T Crossover Wrap Cable.
Running Hardware Diagnostics Sample Test 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. The command to start this test is: test 3 After you enter the test command line, the following displays: Port Tests are available for the selected slot(s). These tests require external cabling.
Running Hardware Diagnostics 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 display the following pattern: OFF RED OFF GREEN OFF AMBER OFF - Passed Test In Progress: VRAM Test - Passed Test In Progress: CAMOFFBRD Test(1K) - Passed Loading dni.img... Test In Progress: BOARDUP Test - Passed Test In Progress: CAMONBRD Test(1K) - Passed Test In Progress: VBUS Test - Passed Restoring slot 3...
Running Hardware Diagnostics 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. And the Failure Summation section displays only the first three failures when you request multiple test iterations. You should now disconnect the cables used in the external loopback tests.
Displaying Available Diagnostic Tests Displaying Available Diagnostic Tests The testdisp command provides the user with a display of applicable tests for a particular slot or for the entire chassis configuration. To display available diagnostic tests for a switching module, enter the testdisp command followed by the slot number for the module.
Configuring the Diagnostic Test Environment Configuring the Diagnostic Test 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. The slot number is an integer ranging from 1 to the number of slots in the chassis (3 for 3-slot Omni Switch/Routers; 5 for 5-slot Omni Switch/Routers and 9 for 9-slot Omni Switch/Routers).
Configuring the Diagnostic Test Environment Configuring Tests for Ethernet Modules Tailoring of applicable Ethernet modules includes selection of Port Speeds and of Port Modes. To configure applicable diagnostic tests for an Ethernet 10/100 switching module in slot 3, enter: testcfg 3 The following is a sample display of the test configuration for an Ethernet 10/100 switching module.
Running Frame Fabric Tests on Omni Switch/Routers Running Frame Fabric Tests 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. The syntax for this command is as follows: framefab [ | ilb ] The option lets you set the number of times to run the test, which can be from 0 to 999. If you enter 0, the framefab test will continue indefinitely.
Running Frame Fabric Tests on Omni Switch/Routers 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 Outputs tested Fabric in slot 3 (ESX-C12) has 9 inputs (0-8) and 1 output (0) All inputs tested All Outputs tested Fabric in slot 4 (ESX-C12) has 9 inputs (0-8) and 1 output (0) All inputs tested All Outputs tested Fabric in slot 5 (ESX-C12) has 9 inputs (0-8) and 1 output (0) All inputs tested All Outputs tested Fabric i
Running Diagnostics on an Entire Chassis Running Diagnostics on an Entire 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.) For example, to configure diagnostic tests for an entire chassis, enter: testcfg all A screen similar to the following will be displayed.
Running Diagnostics on an Entire Chassis 2) Stop on Failure 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. Setting this field to 2 can be used to further troubleshoot problems. However, setting this field to 2 requires more user intervention during a test.
Diagnostic Test Cable Schematics Diagnostic Test Cable Schematics The figures below and on the following pages provide information on port test cables and plugs.
Diagnostic Test Cable Schematics RJ-48 (RJ-45) 1 2 3 4 5 6 7 8 RJ-48 (RJ-45) 1 2 4 3 6 5 7 8 BRI S/T Crossover Wrap Cable — Category 5 UTP Copper Cable with RJ-48 (RJ-45) Connectors Page 36-23
Diagnostic Test Cable Schematics Page 36-24
A The Boot Line Prompt 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. You can only access the Boot Line configuration through an ASCII terminal. Customizing parameters can be helpful when troubleshooting your system.
Entering the Boot Prompt Entering the Boot Prompt 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. The default communication parameters are: • 9600 bps • 8 data bits • 1 stop bit • no parity • no hardware flow control (Microsoft Windows 95) 2. Turn on the switch. 3. You should see text scrolling on the terminal, indicating that the boot is starting.
Boot Prompt Basics Boot Prompt Basics To get a list of commands enter a question mark (?).
Boot Prompt Basics Displaying Current Configuration (p) To display the current configuration, enter a p at the Boot prompt. A screen similar to the following will be displayed. Boot device Boot file Eth IP addr[:mask] Startup script Console params Modem params Boot flags Other : ffs : /flash/mpx.img : 192.168.11.1 : /flash/mpx.cmd : 9600,n81c : 9600,n81 : 0xb : dvip:no-name,192.168.10.1,255.255.255.0,192.168.10.
Boot Prompt Basics Listing Available 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.cmd mpm.log esx.img mpx.img mpm.cnf mpm.cfg switch.ascii [Boot]: Deleting All Files in the Flash Memory (P) To delete all flash memory files, enter the P command at the prompt.
Boot Prompt Basics 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...done [Boot]: Viewing Version Number (V) To view the version number of the bootstrap shell, enter the V command at the prompt.
Configuring a Switch with an MPX 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. A prompt similar to the following displays. '.' = clear field; Boot device '-' = go to previous field; : ffs ^D = quit 2. To change the switch’s boot device, (i.e.
Configuring a Switch with an MPX 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. A screen prompt similar to the following displays. Remote password : 10. You can enter a password for a remote host. 11. A screen prompt similar to the following displays. Startup script : /flash/mpx.
Configuring a Switch with an MPX 14. To accept the default (oxb) and perform a normal boot, press the 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. • 0x04 Do not autoboot. • 0x08 Quick autoboot (no countdown). • 0x20 Disable login security. • 0x40 Use bootp to get the boot parameters. • 0x80 Use tftp to get the boot image.
Configuring a Switch with an MPX Page A-10
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.
V.35 DTE Cable (For WSX-to-DCE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
V.35 DCE Cable (For WSX-to-DTE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. V35-F • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS232 DTE Cable (For WSX-to-DCE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS232 DCE Cable (For WSX-to-DTE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS530 DTE Cable (For WSX-to-DCE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS530 DCE Cable (For WSX-to-DTE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
X.21 DTE Cable (For WSX-to-DCE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
X.21 DCE Cable (For WSX-to-DTE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS449 DTE Cable (For WSX-to-DCE Device Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26 Pin HD50 Connector-male • AMP 750850-6 26 Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RS-449 DCE Cable Assembly (For WSX-to-DTE Device 75Ω Connection) The following parts are recommended for the end of the cable connected to the WSX. • AMP 750833-1 26-Pin HD50 Connector-male • AMP 750850-6 26-Pin HD50 Backshell Parts for the customer end of the cable can be of any industry-standard manufacturer. Use of a shielded-type connector is recommended.
RJ-45 to DB15F Cable Assembly (For T1/E1 Port 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 manufacturer. Use of a shielded-type DB-15 female connector is recommended.
RJ-45 to BNC Cable Assembly (For E1 75Ω Port Connections) The following parts are recommended for manufacturing the cable: • For the switch side of the cable assembly (P1): 8-conductor RJ-45 round connector (MTP-88U or equivalent) • For the cable: RG-187A coaxial cable (Belden 83267 or equivalent) • For the customer end of the cable assembly (P2 and P3): Coaxial BNC connector, 75Ω (Amp 413760-8, or equivalent). The figure below shows the pinouts for the cable assembly.
Page B-14
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.1Q 15-1, 16-1 802.
Index C cacheconfig command D 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 Frame Relay routing 29-60 Frame Relay trunking 29-62 cats command 19-2 cb command 7-7 cd command 7-2, 19-62 chassis grounding 1-21 chngmac command 14-6 chnlinfo command 15-14 Class B 1-7 clearstat command 9-16 cmdlog command 10-9 command families 8-13, 8-17 command history 4-26 Command Line Interface 4-1 Committed Inform
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-6, 18-8 error messages 35-11 ESX-K-100C-32W 3-15, 15-5, 15-8 ESX-K-100FM/FS-16W 3-19, 15-8 eth100 command 15-4 ethdef command 18-26 Ethernet 10/100 ports 15-5 802.
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-59 self-configuration 29-7 split clocking 29-40 statistics 29-38 translations 29-13 trunking 29-19, 29-62 viewing parameters 29-33 Virtual Circuit 29-6, 29-14 Virtual Circuit configuration 29-32 virtual ports 29-14 Frame Relay boards ipxsap command with, 27-11 framefab command 36-2, 36-18 frclear command 29-54 frdelete c
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 limitations 1-23 valid configurations 1-23 hrex command 9-27 hrexassign command 9-27 hrexdisplay command 9-27 hrexhashopt command 9-29 hrexutil command 9-29 displaying global filters 25-38 displaying specific filters 25-38 filter precedence 25-35 IP Routing 19-21 adding an IP address to ARP table 25-9 adding IP static r
Index IPX RIP/SAP Filtering adding global filters 27-19 adding specific filters 27-20 configuring NetWare for WAN links 27-33 default setting of filters 27-18 deleting filters 27-22 displaying all filters 27-23 displaying global filters 27-24 displaying specific filters 27-24 filter precedence 27-25 uses for filters 27-18 IPX routing adding an IPX static route 27-12 configuring IPX Serialization Packet Filtering 27-26 configuring IPX Watchdog Spoofing 27-28 configuring NetWare for WAN links 27-33 configurin
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 restoring 14-6 MAC devices VLAN membership 20-26, 22-30 main menu 4-15 mas command 16-12 Frame Relay 29-65 maskta command 36-5 mcvl command 23-13 MD5 12-4 media access control - see MAC memory management 9-20 memory threshold 11-5 memory utilization statistics 9-19 memstat command 9-20 Mobile Groups 19-1, 19-5 aging out devic
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 command 12-5, 12-15 NTP advertised precision 12-14 client/server 12-8 client/server authentication 12-9 current leap second 12-30 event timer subsystem 12-28 I/O subsystem 12-27 key ID 12-34 key type 12-35 list of peers 12-15 local server information 12-21 local server statistics 12-23 loop filter information 12-26 packet co
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 WAN modules 3-22 pmapcr command 19-17 pmapdel command 19-17 pmapmod command 19-17 pmapv command 19-17 pmcfg command 19-62 pmdelete command 19-64 pmon command 19-63 pmpause command 19-64 pmstat command 19-65 PMTU 25-42 Point-to-Point Protocol (PPP) accessing the PPP menu 30-6 adding a PPP entity 30-9 deleting a PPP entity 30-21 displaying PPP entity status 30-18 m
Index R rb command reboot 8-3 7-8 - see also boot reboot command 8-3 11-3 receive threshold redundancy MPX 1-7, 1-10, 1-13, 2-9, 6-9 power supply 1-11, 1-14 re-executing commands 4-26 reg_port_rule variable 22-9 relayc command 26-2, 26-3 relays command 26-23 remote trunking stations 17-18 renounce command 6-14 res command 14-1 reset command 36-4 resource thresholds 11-2 RIF stripping and UDP relay 26-1 RIP protocol 25-2 ripflush command 25-32 rips command 25-26 ripxsr command 27-13 risr command 25-19 rm
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 switch command 4-15, 18-25 switch menu 18-25 switch software Boot prompt 5-5 loading with FTP 5-2 loading with ZMODEM 5-4 switching modules 2-7, 3-12, 3-15, 3-19, 3-22 disabling 36-4 hot swapping 3-7 power consumption 1-19, 1-20 removing 3-6 resetting 36-4 swlogc command 10-6 syncctl command 6-15 syscfg command 9-2, 9-23 syslog command 10-2 systat c
Index SNAP 18-21 Token Ring 18-19 transmission states XMAP 21-3 transmit credit 19-31 transmit/receive threshold traps configuring 13-2 trdef command 18-28 troubleshooting 35-1 Truncating Tree Timing description 17-35 11-3 U UDP 25-3 UDP relay 26-1 udpl command 25-25 udps command 25-24 UI Table Filtering 4-38 Filter Command 4-41 combining Search Command with 4-42 more mode and 4-38 Search Command 4-39 combining Filter Command with 4-42 more mode and 4-38 renewing a search 4-40 wildcards and 4-44 uic comma
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 WAN Links accessing the LINK menu 31-2 adding a link record 31-3 deleting link records 31-11 displaying link status 31-15 modifying a link record 31-9 viewing link records 31-12 WAN modules 3-22 cables B-1 pinouts 3-22 WSX-BRI-SC 3-36 WSX-FT/E1-SC 33-1 WSX-FT1/E1-SC 3-32 WSX-S-2W 3-27 WSX-SC 3-29 WAN routing 19-19, 19-35 warning hot swapping and file corruption 2-2 power down an
Index Page I-14
