Omni Switch Router User Manual Rel 4.5 R4 5

Omni Switch/Router OmniSwitch - Router User Manual R4-5

SwitchRouter to the manual 6cd15a27-b48b-4338-9a7b-c8627ca8b792

User Manual: OmniSwitch - Router User Manual R4-5

Open the PDF directly: View PDF .
Page Count: 1100

Download
Open PDF In Browser	View PDF

Part No. 060166-10, Rev. C
March 2005

Omni Switch/Router ™
User Manual
Release 4.5

www.alcatel.com

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. Additionally, with 24-hour-a-day access to Alcatel’s Service and
Support web page, you’ll be able to view and update any case (open or closed) that you have reported
to Alcatel’s technical support, open a new case or access helpful release notes, technical bulletins, and
manuals. For more information on Alcatel’s Service Programs, see our web page at
www.ind.alcatel.com, call us at 1-800-995-2696, or email us at support@ind.alcatel.com.

This Manual documents Release 4.5 Omni Switch/Router hardware and software.
The functionality described in this Manual is subject to change without notice.

Copyright© 2005 by Alcatel Internetworking, Inc. All rights reserved. This document may not be reproduced in
whole or in part without the express written permission of Alcatel Internetworking, Inc.
Alcatel® and the Alcatel logo are registered trademarks of Alcatel. Xylan®, OmniSwitch®, PizzaSwitch® and
OmniStack® are registered trademarks of Alcatel Internetworking, Inc.
AutoTracker™, OmniAccess™, OmniCore™, Omni Switch/Router™, OmniVista™, PizzaPort™, PolicyView™,
RouterView™, SwitchManager™, SwitchStart™, VoiceView™, WANView™, WebView™, X-Cell™, X-Vision™
and the Xylan logo are trademarks of Alcatel Internetworking, Inc.
All-In-OneSM is a service mark of Alcatel Internetworking, Inc. All other brand and product names are trademarks
of their respective companies.

26801 West Agoura Road
Calabasas, CA 91301
(818) 880-3500 FAX (818) 880-3505
info@ind.alcatel.com
US Customer Support–(800) 995-2696
International Customer Support–(818) 878-4507
Internet–http://eservice.ind.alcatel.com

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. Operation of this equipment in a residential area is likely to cause interference, in
which case the user will be required to correct the interference at his own expense.
The user is cautioned that changes and modifications made to the equipment without approval of the
manufacturer could void the user’s authority to operate this equipment. It is suggested that the user
use only shielded and grounded cables to ensure compliance with FCC Rules.
This equipment does not exceed Class A limits per radio noise emissions for digital apparatus, set out
in the Radio Interference Regulation of the Canadian Department of Communications.
Avis de conformité aux normes du ministére des Communications du Canada
Cet équipement ne dépasse pas les limites de Classe A d’émission de bruits radioélectriques pour les
appareils numériques, telles que prescrites par le Réglement sur le brouillage radioélectrique établi
par le ministére des Communications du Canada.
Lithium Batteries Caution: There is a danger of explosion if the Lithium battery in your chassis is
incorrectly replaced. Replace the battery only with the same or equivalent type of battery
recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s
instructions. The manufacturer’s instructions are as follows:

Return the module with the Lithium battery to Alcatel. The Lithium battery will
be replaced at Alcatel’s factory.

page iii

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Omni Switch/Router Applications and Configurations . . . . . . . . . . . . . . . . . . . . . . 1-5
Omni Switch/Router as the Backbone Connecting Several Networks . . . . . . . . 1-5
Omni Switch/Router as the Central Backbone Switch/Router and
in the Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Omni Switch/Router Chassis and Power Supplies . .
OmniS/R-3 . . . . . . . . . . . . . . . . . . . . . . . . . . .
OmniS/R-3 Chassis Technical Specifications
OmniS/R-5 . . . . . . . . . . . . . . . . . . . . . . . . . . .
OmniS/R-5 Technical Specifications . . . . . .
OmniS/R-9 and OmniS/R-9P . . . . . . . . . . . . . .
OmniS/R-9 Technical Specifications . . . . . .
OmniS/R-9P Technical Specifications . . . . .
OmniS/R-9P-48V Technical Specifications . .
Omni Switch/Router Power Requirements . . . .
Grounding a Chassis . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.

. 1-7
. 1-8
. 1-9
1-10
1-12
1-13
1-15
1-16
1-17
1-18
1-21

The Omni Switch/Router Hardware Routing Engine (HRE-X) . . . . . . . . . . . . . . . 1-22
Valid HRE-X Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
HRE-X Router Registers versus Feature Limitations . . . . . . . . . . . . . . . . . . . . 1-23
Connecting a DC Power Source to an OmniS/R-PS5-DC375 . . . . . . . . . . . . . . . . 1-24
Installing DC Power Source Wire Leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Connecting a DC Power Source to an OmniS/R-PS9-DC725 . . . . . . . . . . . . . . . . 1-27
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Installing DC Power Source Wire Leads . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Replacing Power Supplies (9-Slot Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

2 The Omni Switch/Router MPX

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Omni Switch/Router Management Processor Module (MPX) Features . . . . . . . . . . 2-1
MPX Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
MPX Serial and Ethernet Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Ethernet Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring MPX Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Flash Memory and Omni Switch/Router Software . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Flash Memory Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

page v

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Installing a Switching Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Removing a Switching Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Hot Swapping a Switching Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Handling Fiber and Fiber Optic Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Gigabit Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
GSX-K-FM/FS/FH-2W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
GSX-K-FM/FS/FH-2W Technical Specifications . . . . . . . . . . . . . . . . . . . . 3-13
Auto-Sensing 10/100 Ethernet Modules . . . . . . .
Ethernet RJ-45 Pinouts . . . . . . . . . . . . . .
Ethernet RJ-45 Specifications . . . . . . . . .
ESX-K-100C-32W . . . . . . . . . . . . . . . . . . . . .
ESX-K-100C-32W Technical Specifications

.
.
.
.
.

3-15
3-15
3-15
3-15
3-17

Fast (100 Mbps) Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
ESX-K-100FM/FS-16W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
ESX-K-100FM/FS-16W Technical Specifications . . . . . . . . . . . . . . . . . . . . 3-20
WAN Modules . . . . . . . . . . . . . . . . . . . . . . . . . . .
WAN Pinouts . . . . . . . . . . . . . . . . . . . . . . .
WAN BRI Port Specifications (S/T Interface)
WAN BRI Port Specifications (U Interface) .
WAN T1/E1 Port Specifications . . . . . . . . . .
WAN Serial Port Specifications . . . . . . . . . .
WSX-S-2W . . . . . . . . . . . . . . . . . . . . . . . . . . .
WSX-S-2W Technical Specifications . . . . . .
WSX-SC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WSX-SC Technical Specifications . . . . . . . .
WSX-FT1/E1-SC . . . . . . . . . . . . . . . . . . . . . . . .
WSX-FT1/E1-SC Technical Specifications . .
WSX-FE1-SC Cabling/Jumper Settings . . . . .
WSX-BRI-SC . . . . . . . . . . . . . . . . . . . . . . . . . .
WSX-BRI-SC Technical Specifications . . . . .

page vi

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

3-22
3-22
3-23
3-23
3-24
3-25
3-27
3-27
3-29
3-30
3-32
3-33
3-35
3-36
3-37

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 . . . . . . . . . . . . . .
Hardware Table . . . . . . . . . . . . . . . .
Basic Switch Management Commands . .
Basic Switch Management Table . . . .
Network Management Commands . . . . .
Network Management Table . . . . . .
Layer II Switching Commands . . . . . . . .
Layer II Switching Table . . . . . . . . . .
Groups, VLANs, Policies Commands . . .
Groups, VLANs, Policies Table . . . . .
Routing Commands . . . . . . . . . . . . . . . .
Routing Table . . . . . . . . . . . . . . . . .
WAN Access Commands . . . . . . . . . . . .
WAN Access Table . . . . . . . . . . . . . .
Troubleshooting Diagnostics Commands
Troubleshooting/Diagnostics Table . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. 4-4
. 4-4
. 4-4
. 4-4
. 4-5
. 4-6
. 4-6
. 4-7
. 4-7
. 4-8
. 4-8
4-10
4-10
4-11
4-11
4-13
4-13

User Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Main Menu Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
General User Interface Guidelines . . . . . . . . . . . . . . . . . .
Entering Command Names . . . . . . . . . . . . . . . . . . . .
Quitting a Command . . . . . . . . . . . . . . . . . . . . . . . . .
Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The UI Configuration Menu . . . . . . . . . . . . . . . . . . . .
Configuring the System Prompt . . . . . . . . . . . . . .
Configuring More Mode for the User Interface . . .
Setting Verbose/Terse Mode for the User Interface
Configuring the Auto Logout Time . . . . . . . . . . . . . . .
Viewing Commands . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . .
Command History and Re-Executing Commands . . . .
Abbreviating IP Addresses . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.

4-16
4-16
4-17
4-17
4-17
4-18
4-19
4-22
4-24
4-25
4-25
4-26
4-28

User Interface Display Options . . . . . . . . . .
Setting Echo/NoEcho for User Entry . . . .
Setting the Login Banner . . . . . . . . . . . .
Creating a new Banner . . . . . . . . . .
Permanent Banner . . . . . . . . . . . . . .
Banners for Different Access Methods

.
.
.
.
.
.

4-30
4-31
4-31
4-32
4-32
4-32

.
.
.
.
.
.

page vii

Table of Contents
Multiple User Sessions . . . . . . . . . . . . . .
Listing Other Users . . . . . . . . . . . . .
Communicating with Other Users . . .
Deleting Other Sessions . . . . . . . . . .
Advanced Kill Command Options

.
.
.
.
.

4-33
4-34
4-35
4-35
4-37

UI Table Filtering (Using Search and Filter Commands)
The Search Command . . . . . . . . . . . . . . . . . . . . . .
Renewing a Search . . . . . . . . . . . . . . . . . . . . .
The Filter Command . . . . . . . . . . . . . . . . . . . . . . .
Combining Search and Filter Commands . . . . . . . .
Using Wildcards with Search and Filter Commands .
Wildcard Command Options . . . . . . . . . . . . . .

.
.
.
.
.
.
.

4-38
4-39
4-40
4-41
4-42
4-44
4-44

5 Installing Switch Software

.
.
.
.
.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Using FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Using FTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Using ZMODEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Using ZMODEM with the load Command . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Using ZMODEM With the Boot Line Prompt . . . . . . . . . . . . . . . . . . . . . . . 5-5

6 Configuring Management Processor Modules

. . . . . . . . . . . . . . . . . . . . 6-1

Changing Serial Port Communication Parameters . . . . . . . . . . . . . . . . . . .
Changing Port Speed When Communication With The Switch Lost
Configuring the Modem Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modem Port Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring SLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.

6-2
6-3
6-3
6-3
6-4

Configuring the Ethernet Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Ethernet Management Ports and Redundant Management Processor Modules . . . . 6-7
The MPM Command/Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying MPX Redundancy . . . . . . . . . . . . . . . . . . . . . . .
MPM Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using MPM Commands with Software Release 3.2 and Later

.
.
.
.

. 6-9
. 6-9
. 6-9
6-10

Listing the Secondary MPX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Transferring a File to the Secondary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Replacing a File on the Secondary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Loading a File from the Secondary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Removing a File from the Secondary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Giving Up Control to the Secondary MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Setting the Load Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Setting Automatic Config Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Enabling Automatic Config Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Disabling Automatic Config Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

page viii

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Displaying and Setting the Swap State
Displaying the Swap State . . . . . .
Enabling the Swap Mode . . . . . . .
Disabling the Swap Mode . . . . . .

7 Managing Files

.
.
.
.

6-20
6-20
6-20
6-21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Displaying the Current Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Configuration and Log File Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Changing Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Listing Switch Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Deleting Switch Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Deleting Multiple Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Deleting All Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Copying System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Displaying Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Editing Text Files . . . . . . . . . . . . . . . . . . . . . . . .
Clearing the Text Buffer . . . . . . . . . . . . . . . . .
Loading an ASCII File into the Text Buffer . . .
Listing the Contents of the Text Buffer . . . . . .
Adding Lines of Text to the Text Buffer . . . . .
Deleting a Line of Text from the Text Buffer .
Inserting a Line of Text into the Text Buffer . .
Editing a Line Name of Text in the Text Buffer
Creating a File Name for the Text Buffer . . . .
Creating a Text File from the Text Buffer . . . .

.
.
.
.
.
.
.
.
.
.

. 7-7
. 7-7
. 7-8
. 7-8
. 7-8
. 7-9
. 7-9
. 7-9
7-10
7-10

Real-World Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Real-World Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Real-World Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
System Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Checking the Flash File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Creating a New File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

8 Switch Security

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Rebooting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

page ix

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 . . . . . . . . . . .

.
.
.
.
.
.
.

. 8-4
. 8-4
. 8-7
. 8-9
. 8-9
. 8-9
8-10

Managing User Login Accounts . . . . . . . . . . . . . . . . . . . . . . . .
Partition Management Requirements . . . . . . . . . . . . . . . . . .
Default Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a User Account Using the UI Command Mode . . . .
Adding a User Account Using the CLI Command Mode . . . .
Assigning Account Privileges Using the CLI Command Mode
Assigning Account Privileges Using the UI Command Mode
Command Family Table . . . . . . . . . . . . . . . . . . . . . . . .
Global Family Table . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a User Account . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.

8-11
8-11
8-12
8-12
8-13
8-13
8-16
8-18
8-19
8-20
8-20

9 Configuring Switch-Wide Parameters

.
.
.
.
.
.
.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Summary Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Displaying the MIB-II System Group Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Displaying the Chassis Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Displaying Current Router Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
System Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Displaying Basic System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Setting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Viewing Slot Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Viewing System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Clearing System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Viewing Task Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Viewing Memory Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Viewing MPX Memory Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
Checking the Flash File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Checking the SIMM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Creating a New File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Creating a SIMM File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Configuring System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Viewing CAM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Configuring CAM Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Configuring the HRE-X Router Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Configuring and Displaying the HRE-X Hash Table . . . . . . . . . . . . . . . . . . . . 9-29
page x

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10-1

Logging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Configuring the Syslog Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Configuring Switch Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Displaying the Command History Entries in the MPM Log . . . . . . . . . . . . . . . . . . 10-9
Displaying the Connection Entries in the MPM Log . . . . . . . . . . . . . . . . . . . . . . .10-10
Displaying Screen (Console) Capture Entries in the MPM Log . . . . . . . . . . . . . . .10-11
Displaying Debug Entries in the MPM Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-13
Displaying Secure Access Entries in the MPM Log . . . . . . . . . . . . . . . . . . . . . . . .10-13

11 Health Statistics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

The Health Statistics Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Setting Resource Thresholds . . . . . .
Setting Bandwidth Thresholds . .
Setting Miscellaneous Thresholds
Setting the Sampling Interval . . .

.
.
.
.

11-2
11-3
11-4
11-6

View Switch-Level Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
View Module-Level Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
View Port-Level Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Reset Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

12 Network Time Protocol

.
.
.
.
.

.
Introduction . . . . . . . . . .
Stratum . . . . . . . . . . . . . .
Using NTP in a Network .
NTP and Authentication . .

.
.
.
.
.

12-1
12-1
12-2
12-2
12-4

Network Time Protocol Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
NTP Configuration Menu . . . . . . . . . . . . . . .
Configuring an NTP Client . . . . . . . . . . .
Configuring an NTP Client/Server . . . . .
Configuring Client/Server Authentication
Configuring a New Peer Association . . . .
Configuring a New Server . . . . . . . . . . .
Configuring a Broadcast Time Service . .
Unconfigure Existing Peer Associations .
Set the Server’s Advertised Precision . . .

.
.
.
.
.
.
.
.
.

. 12-6
. 12-6
. 12-8
. 12-9
.12-12
.12-13
.12-13
.12-14
.12-14

page xi

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

.
.
.
.
.
.
.

.12-15
.12-15
.12-16
.12-17
.12-18
.12-20
.12-21

NTP Statistics Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Local Server Statistics . . . . . . . . . . . . . . . . . . . . . . .
Display Server Statistics Associated with Particular Peer(s) . .
Display Loop Filter Information . . . . . . . . . . . . . . . . . . . . .
Display Peer Memory Usage Statistics . . . . . . . . . . . . . . . . .
Display I/O Subsystem Statistics . . . . . . . . . . . . . . . . . . . . .
Display Event Timer Subsystem Statistics . . . . . . . . . . . . . .
Reset Various Subsystem Statistics Counters . . . . . . . . . . . .
Reset Stat Counters Associated With Particular Peer(s) . . . . .
Display Packet Count Statistics from the Control Module . . .
Display the Current Leap Second State . . . . . . . . . . . . . . . .
Turn the Server's Monitoring Facility On or Off . . . . . . . . . .
Display Data The Server's Monitor Routines Have Collected

.
.
.
.
.
.
.
.
.
.
.
.
.

.12-23
.12-23
.12-24
.12-26
.12-26
.12-27
.12-28
.12-28
.12-28
.12-29
.12-30
.12-31
.12-31

NTP Administration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set the Primary Receive Timeout . . . . . . . . . . . . . . . . . . . . .
Set the Delay Added to Encryption Time Stamps . . . . . . . . .
Specify the Host Whose NTP Server We Talk To . . . . . . . . .
Specify a Password to Use for Authenticated Requests . . . . .
Set Key ID to Use for Authenticated Requests . . . . . . . . . . . .
Set Key Type to Use for Authenticated Requests (DES|MD5)
Set a System Flag (Auth, Bclient, Monitor, Stats) . . . . . . . . . .
Clear a System Flag (Auth, Bclient, Monitor, Stats) . . . . . . . .

.
.
.
.
.
.
.
.
.

.12-33
.12-33
.12-33
.12-34
.12-34
.12-34
.12-35
.12-35
.12-35

NTP Access Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . .
Change the Request Message Authentication Key ID . . . . .
Change the Control Message Authentication Key ID . . . . .
Add One or More Key ID's to the Trusted List . . . . . . . . .
Display the Trusted Key ID List . . . . . . . . . . . . . . . . . . . .
Remove One or More Key ID's from the Trusted List . . . .
Display the State of the Authentication Code . . . . . . . . . .
Create Restrict Entry/Add Flags to Entry . . . . . . . . . . . . . .
View the Server's Restrict List . . . . . . . . . . . . . . . . . . . . . .
Remove Flags from a Restrict Entry . . . . . . . . . . . . . . . . .
Delete a Restrict Entry . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure a Trap in the Server . . . . . . . . . . . . . . . . . . . . .
Display the Traps Set in the Server . . . . . . . . . . . . . . . . . .
Remove a Trap (Configured or Otherwise) from the Server

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.12-36
.12-36
.12-37
.12-37
.12-37
.12-38
.12-38
.12-39
.12-40
.12-41
.12-41
.12-41
.12-42
.12-42

.
.
.
.
.
.
.
.
.
.
.
.
.
.

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Trap Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11
SNMP Standard Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-15
Extended Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-27

14 DNS Resolver and RMON

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Configuring the DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
The Names Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Remote Network Monitoring (RMON)
Probes and Events . . . . . . . . . . . .
Ethernet Probes . . . . . . . . . . .
History Probes . . . . . . . . . . . .
Alarm Probes . . . . . . . . . . . . .
Monitoring Probes . . . . . . . . . . . .
Monitoring Events . . . . . . . . . . . .

.
.
.
.
.
.
.

14-3
14-3
14-3
14-3
14-3
14-4
14-5

Configuring Router Port MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Restoring Router Port Mac Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

15 Managing Ethernet Modules

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Overview of Omni Switch/Router Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . 15-1
Kodiak Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
The Ethernet Management Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Configuring 10/100 Auto-Sensing Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Connecting Kodiak Modules to Non-Auto-Negotiating Links . . . . . . . . . . 15-6
Configuring Kodiak Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Viewing Configurations for 10/100 Ethernet Modules . . . . . . . . . . . . . . . . . . . . . 15-8
OmniChannel . . . . . . . . . . . . . . . . . . . .
The Server Channel Feature . . . . . . .
Server Channel Limitations . . . . .
Creating an OmniChannel . . . . . . . .
Adding Ports to an OmniChannel . . .
Deleting an OmniChannel . . . . . . . .
Deleting Ports from an OmniChannel
Viewing OmniChannel Parameters . .

.
.
.
.
.
.
.
.

. 15-9
.15-10
.15-11
.15-11
.15-13
.15-13
.15-14
.15-14

page xiii

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Configuring 802.1Q on 10/100 Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Configuring 802.1Q on Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . .16-11
Modifying 802.1Q Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-12
Modifying 802.1Q Groups for 10/100 Ports . . . . . . . . . . . . . . . . . . . . . . . . . .16-12
Modifying 802.1Q Groups for Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . .16-14
Viewing 802.1Q Groups in a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-16
Viewing 802.1Q Statistics for 10/100 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-17
Deleting 802.1Q Groups from a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-18

17 Configuring Bridging Parameters

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Bridge Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Selecting a Default Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Using the + or - to Change Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Bridging Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Bridge Forwarding Table . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a Static Bridge Address . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Static Bridge Address . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Static Bridge Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Static Bridge Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Bridge Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Media Access Control (MAC) Information for a Specific MAC
address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Media Access Control (MAC) Information for all MAC
addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Statistics of Bridge MAC Addresses . . . . . . . . . . . . . . . . . . . . . .
Clear Statistics of Bridge MAC Addresses . . . . . . . . . . . . . . . . . . . . . . .
Display Remote Trunking Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . .
View the Domain Bridge Mapping Table . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.

. 17-8
. 17-8
.17-10
.17-11
.17-12
.17-13
.17-14

. . . .17-16
.
.
.
.
.

.
.
.
.
.

.17-17
.17-17
.17-18
.17-18
.17-19

Setting Flood Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-21
Setting Flood Limits for a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-21
Displaying Group Flood Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-22
Configuring Spanning Tree . . . . . . . . . . . . . . .
Configuring Spanning Tree Parameters . . . .
Display Spanning Tree Bridge Parameters .
Configuring Spanning Tree Port Parameters
Displaying Spanning Tree Port Parameters .

page xiv

.
.
.
.
.

.17-23
.17-25
.17-28
.17-30
.17-32

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 . . . . . . . . . . . .
Disabling Fast Spanning Tree Port Parameters . . . . . . . . . . .

.
.
.
.
.
.
.
.

.17-34
.17-35
.17-35
.17-35
.17-35
.17-36
.17-38
.17-39

Configuring Source Routing . . . .
SAP Filtering . . . . . . . . . . . .
Enabling SAP Filtering . .
Disabling SAP filtering . .
Configuring SAP Filtering
Viewing SAP Filtering . .

.
.
.
.
.
.

.17-40
.17-40
.17-40
.17-41
.17-41
.17-42

Configuring Source Route to Transparent Bridging
Enabling SRTB for a Group . . . . . . . . . . . . . .
Disabling SRTB for a Group . . . . . . . . . . . . . .
Viewing the RIF Table . . . . . . . . . . . . . . . . . .
Clearing the RIF Table . . . . . . . . . . . . . . . . . .

.
.
.
.
.

.17-43
.17-44
.17-45
.17-46
.17-47

18 Configuring Frame Translations

.
.
.
.
.
.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Any-to-Any Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Translating the Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
The MAC Header . . . . . . . . . . . . . . . .
Canonical versus Non-Canonical . .
Abbreviated Addresses . . . . . . . . .
Functional Addresses and Multicasts

.
.
.
.

18-4
18-4
18-4
18-4

The RIF Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Source Route Termination by Proxy Not Supported . . . . . . . . . . . . . . . . . . . 18-5
Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocols other than IP and IPX . . . . . . . . . . . . . . . . . . . .
The SNAP Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of Non-IPX Encapsulation Transformation Rules
IPX Encapsulation Transformation Rules . . . . . . . . . . . . . .

.
.
.
.
.
.

The Network Header . . . . . . . . . . .
Address Mapping . . . . . . . . . .
Address Mapping in IP: ARP
Address Mapping in IPX . .

.
.
.
.

18-6
18-6
18-7
18-7
18-7
18-8

.
.
.
.

. 18-9
. 18-9
. 18-9
.18-10

Frame Size Requirements . . . . . . . . . . . . . . . . . . . . .
Insertion of Frame Padding . . . . . . . . . . . . . . . . .
Stripping of Padding for all IEEE 802.3 Frames.
No stripping of non-IPX Ethertype Frames . . .
IPX Specific Stripping . . . . . . . . . . . . . . . . . .

.
.
.
.
.

.18-11
.18-11
.18-11
.18-11
.18-11

page xv

Table of Contents
MTU Handling . . . . . . . . . . . .
IP Fragmentation . . . . . . . .
ICMP Based MTU Discovery
IPX Packet Size Negotiation
Other Protocols . . . . . . . . .

.
.
.
.
.

.18-12
.18-12
.18-12
.18-12
.18-12

Banyan Vines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-13
Configuring Encapsulation Options . . . . . . . . . . . . . . . . . .
Forwarding versus Flooding . . . . . . . . . . . . . . . . . . . . .
Port Based Translation Options . . . . . . . . . . . . . . . . . .
MAC Address Based Translation Options . . . . . . . . . . .
“Native” versus “Non-Native” on Ethernet . . . . . . . . . . .
“Native” versus “Non-Native” on FDDI and Token Ring
No Translation on Trunk or PTOP ports . . . . . . . . . . . .
The Proprietary Token Ring IPX Option . . . . . . . . . . . .

.
.
.
.
.
.
.
.

.18-14
.18-14
.18-14
.18-14
.18-15
.18-15
.18-15
.18-15

The User Interface . . . . . . . . . . . . . . . . . . . . .
The addvp, modvp and crgp Commands . .
The Default Translation Option . . . . . . . . .
Ethernet Factory Default Translations . .
FDDI Factory Default Translations . . . .
Token Ring Factory Default Translations
ATM LANE Factory Default Translations
The Ethertype Option . . . . . . . . . . . . .
The SNAP Option . . . . . . . . . . . . . . . .
The LLC Option . . . . . . . . . . . . . . . . . .
Interaction with the new interface . . . .
The “vi” Command . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.

.18-16
.18-17
.18-17
.18-18
.18-18
.18-19
.18-19
.18-20
.18-21
.18-23
.18-24
.18-24

The Switch Menu . . . . . . . . . . . . . . . . . . .
Proprietary IPX Token Ring . . . . . . . . .
Factory Defaults . . . . . . . . . . . . . . . . .
Default Ethernet Translations . . . . . . . .
Default FDDI Translations . . . . . . . . . .
Default Token Ring Translations . . . . .
Port Translations . . . . . . . . . . . . . . . . .
Configuring Additional Ports . . . . .
Displaying Ethernet Switch Statistics . . .
Displaying Token Ring Switch Statistics
Any to Any MAC Translations . . . . . . .
Default Autoencapsulation . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.

.18-25
.18-25
.18-25
.18-26
.18-27
.18-28
.18-30
.18-31
.18-31
.18-35
.18-39
.18-40

.
.
.
.
.
.
.
.
.
.
.
.

Translational Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-41
Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-41
Translations across Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-41
Dissimilar LAN Switching Capabilities . . . . . . . . . . . . . . . . . . . . .
Switching Between Similar LANs . . . . . . . . . . . . . . . . . . . . . .
Switching Between Ethernet LANs Across a Trunked Backbone
Switching Between Similar LANs across a Native Backbone . . .
page xvi

.
.
.
.

.18-42
.18-42
.18-43
.18-44

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 . . . . . . .

.
.
.
.

19-2
19-2
19-2
19-3

Mobile Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Mobile Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Turning Group Mobility On or Off . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding Port Membership in Mobile Groups . . . . . . . . . . . . . . . . . .
How a Device Is Dropped from the Default Mobile Group (def_group)
How a Port’s Primary Mobile Group Changes (move_from_def) . . . . .
How a Port Ages Out of a Mobile Group (move_to_def) . . . . . . . . . . .
Configuring Switch-Wide Group Mobility Variables . . . . . . . . . . . . . . . . . .
Viewing Ports in a Mobile Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing a Port’s Mobile Group Affiliations . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.

. 19-5
. 19-5
. 19-6
. 19-7
. 19-9
.19-10
.19-11
.19-12
.19-14
.19-14

Non-Mobile Groups and AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . .19-15
Routing in a Non-Mobile Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-15
Spanning Tree and Non-Mobile Groups . . . . . . . . . . . . . . . . . . . . . . . . .19-16
Group and Port Software Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-17
Creating a New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1. Entering Basic Group Information . . . . . . . . . . . . . . . . .
Step 2. Configuring the Virtual Router Port (Optional) . . . . . . . .
Step 3. Set Up Group Mobility and User Authentication . . . . . .
Step 4. Configuring Virtual Ports . . . . . . . . . . . . . . . . . . . . . . .
Step 5. Configuring AutoTracker Policies (Mobile Groups Only)

.
.
.
.
.
.

.19-18
.19-19
.19-21
.19-27
.19-28
.19-34

Creating a WAN Routing Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-35
Viewing Current Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-38
Modifying a Group or VLAN . . . . . .
Viewing Your Changes . . . .
Saving Your Changes . . . . . .
Canceling Your Changes . . .
Changing the IP Address . . .
Changing the IP Subnet Mask
Enabling IP or IPX Routing .

.
.
.
.
.
.
.

.19-40
.19-41
.19-41
.19-41
.19-41
.19-41
.19-42

Deleting a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-43
Adding Virtual Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-44
Modifying a Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-45
Deleting a Virtual Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-46
Viewing Information on Ports in a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-47
Viewing Detailed Information on Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-50
Viewing Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-53
Viewing Port Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19-55
page xvii

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 . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.

.19-57
.19-57
.19-57
.19-58
.19-60
.19-60

Port Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Monitoring Menu . . . . . . . . . . . . . . . . . . .
RAM Disk System for Data Capture Files . . . . .
Configuring RAM Drive Resources (pmcfg) .
Changing the Default System Directory (cd)
Starting a Port Monitoring Session (pmon) . . . .
If You Chose Dump to Screen . . . . . . . . . .
If You Did Not Choose Dump to Screen . . .
Ending a Port Monitoring Session . . . . . . . .
Viewing Port Monitoring Statistics (pmstat) . . . .

.
.
.
.
.
.
.
.
.
.

.19-61
.19-61
.19-62
.19-62
.19-62
.19-63
.19-64
.19-64
.19-65
.19-65

Port Mapping . . . . . . . . . . . . . . . . . . . . . . .
Groups/VLANs and Port Mapping . . .
The Details of Port Mapping . . . . . . . . .
Who Can Talk to Whom? . . . . . . . . .
Port Mapping Limitations . . . . . . . . . . . .
Creating a Port Mapping Set . . . . . . . . . .
Adding Ports to a Port Mapping Set . . . .
Removing Ports from a Port Mapping Set
Viewing a Port Mapping Set . . . . . . . . . .
Deleting a Port Mapping Set . . . . . . . . .

.
.
.
.
.
.
.
.
.
.

.19-66
.19-66
.19-67
.19-68
.19-68
.19-69
.19-70
.19-71
.19-72
.19-72

Priority VLANs . . . . . . . . . . . . . . . . . . . . . .
Mammoth vs. Kodiak Priority VLANs
Configuring VLAN Priority . . . . . . . . . . .
Viewing VLAN Priority . . . . . . . . . . . . . .

.
.
.
.

.19-73
.19-73
.19-74
.19-74

20 Configuring Group and VLAN Policies

. . . . . . . . . . . . . . . . . . . . . . . . . 20-1

AutoTracker Policy Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Defining and Configuring AutoTracker Policies .
Where These Procedures Start . . . . . . . .
Defining a Port Policy . . . . . . . . . . . . . . . . .
Defining a MAC Address Policy . . . . . . . . . .
Defining a MAC Address Range Policy . . . . .
Defining a Protocol Policy . . . . . . . . . . . . . .
Defining a Network Address Policy . . . . . . .
Defining Your Own Rules . . . . . . . . . . . . . .
Defining a Port Binding Policy . . . . . . . . . . .
Defining a DHCP Port Policy . . . . . . . . . . . .
Defining a DHCP MAC Address Policy . . . . .
Defining a DHCP MAC Address Range Policy

.
.
.
.
.
.
.
.
.
.
.
.

. 20-4
. 20-4
. 20-5
. 20-6
. 20-7
. 20-8
.20-11
.20-13
.20-15
.20-20
.20-21
.20-22

Viewing Mobile Groups and AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . .20-23
page xviii

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 . . . .

.
.
.
.

.20-27
.20-27
.20-28
.20-29

21 Interswitch Protocols

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Interswitch Protocol Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

XMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
XMAP Transmission States . . . . . . . . . . . . . .
Discovery Transmission State . . . . . . . . .
Common Transmission State . . . . . . . . .
Passive Reception State . . . . . . . . . . . . .
Common Transmission and Remote Switches

.
.
.
.
.
.

21-2
21-3
21-3
21-4
21-4
21-4

Configuring XMAP . . . . . . . . . . . . . . . . . . . . . . .
Enabling or Disabling XMAP . . . . . . . . . . . . .
Viewing a List of Adjacent Switches . . . . . . . .
Configuring the Discovery Transmission Time
Configuring the Common Transmission Time .

.
.
.
.
.

21-5
21-5
21-5
21-6
21-7

VLAN Advertisement Protocol (VAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
VAP and Port Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Configuring VAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
GMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GMAP Updating Rules . . . . . . . . . . . . . . . .
Configuring GMAP . . . . . . . . . . . . . . . . . .
Enabling and Disabling GMAP . . . . . . . . . .
Configuring the Gap Time . . . . . . . . . . . . .
Configuring the Interpacket Update Time . .
Configuring the Hold Time . . . . . . . . . . . .
Displaying GMAP Statistics by MAC Address

22 Managing AutoTracker VLANs

.
.
.
.
.
.
.
.

.21-10
.21-10
.21-11
.21-11
.21-11
.21-12
.21-12
.21-13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

The AutoTracker Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AutoTracker VLAN Policies . . . . . . . . . . . . . . . . . . . . . .
The Default VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Devices are Assigned to AutoTracker VLANs . . . . .
The defvl Command . . . . . . . . . . . . . . . . . . . . . . . .
Devices that Generate a Secondary Traffic Type . . . .
Router Traffic in IP and IPX Network Address VLANs
Port Policy Functionality . . . . . . . . . . . . . . . . . . . . .
Frame Flooding in AutoTracker VLANs . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.

. 22-3
. 22-3
. 22-4
. 22-5
. 22-5
. 22-6
. 22-7
. 22-9
.22-15

page xix

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
.22-16
.22-18
.22-19

Modifying an AutoTracker VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-24
Deleting an AutoTracker VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-26
Viewing AutoTracker VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-27
Viewing Policy Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-28
Viewing Virtual Ports’ VLAN Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-29
View VLAN Membership of MAC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-30
Creating a VLAN for Banyan Vines Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22-31

23 Multicast VLANs

.......................
How Devices are Assigned to Multicast VLANs
Multicast VLANs and Multicast Claiming . . . . .
Frame Flooding in Multicast VLANs . . . . . . . .

.
.
.
.

23-1
23-2
23-2
23-3

Creating Multicast VLANs . . . . . . . . . . . . . . . . . . . . . .
Step A. Entering Basic Information . . . . . . . . . . . .
Step B. Defining the Multicast Address . . . . . . . . .
Step C. Defining the Recipients of Multicast Traffic
Defining Recipients By Port . . . . . . . . . . . . . .
Defining Recipients By MAC Address . . . . . . .

.
.
.
.
.
.

23-4
23-5
23-6
23-7
23-7
23-8

Modifying Multicast VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-9
Deleting a Multicast VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-11
Modifying a Multicast Address Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-12
Viewing Multicast VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-13
Viewing Multicast VLAN Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23-14
Viewing the Virtual Interface of Multicast VLANs . . . . . . . . . . . . . . . . . . . . . . . .23-15

24 AutoTracker VLAN Application Examples

. . . . . . . . . . . . . . . . . . . . . . 24-1

Application Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
VLANs Based on Logical Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2
Application Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4
VLANs in IPX Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4
IPX VLAN Assignment at Bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-5
Application Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7
IPX Network Address VLANs and Translated Frames . . . . . . . . . . . . . . . . . . . 24-7
Application Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
Routing in IPX Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-8
Application Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-10
Traversing a Backbone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24-10
page xx

Table of Contents

25 IP Routing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1
IP Routing Overview . . . . . . . .
Routing Protocols . . . . . . .
Transport Protocols . . . . . .
Application-Layer Protocols
Additional IP Protocols . . .

.
.
.
.
.

25-2
25-2
25-3
25-3
25-3

Setting Up IP Routing on the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-4
The Networking Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-6
The IP Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-7
Viewing the Address Translation (ARP) Table . . . . . . . . .
Displaying All Entries in the ARP Table . . . . . . .
Adding Entries to the ARP Table . . . . . . . . . . . . .
Deleting Entries from the ARP Table . . . . . . . . . .
Flushing Temporary Entries from the ARP Table .
Finding a Specific IP Address in the ARP Table . .
Finding a Specific MAC Address in the ARP Table

.
.
.
.
.
.
.

. 25-8
. 25-8
. 25-9
.25-10
.25-10
.25-10
.25-11

Viewing IP Statistics and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-12
Viewing the IP Forwarding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-15
Adding an IP Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-17
Removing an IP Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-19
Viewing ICMP Statistics and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-20
Using the PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-22
Viewing UDP Statistics and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-24
Viewing the UDP Listener Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-25
Viewing RIP Statistics and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-26
Viewing TCP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-27
Viewing the TCP Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-29
Using the TELNET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-30
Cancelling a Telnet request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-30
Tracing an IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-31
Flushing the RIP Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-32
Configuring IP RIP Filters . . . . . . . . . . . . . . . . . . .
Adding a “Global” IP RIP Filter . . . . . . . . . .
Adding an IP RIP Filter For a Specific Group
IP RIP Filter Precedence . . . . . . . . . . . . . . . . .
Deleting IP RIP Filters . . . . . . . . . . . . . . . . . . .

.......
.......
or VLAN
.......
.......

.
.
.
.
.

.25-33
.25-33
.25-34
.25-35
.25-36

page xxi

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 . . . . . . . . . . . . .
Displaying All Entries in the IP-to-MAC Table . .
Displaying Information for a Specific IP Address
Flushing Entries from the Table . . . . . . . . . . . .

.
.
.
.

.25-39
.25-39
.25-40
.25-40

Enabling/Disabling Directed Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-41
Path MTU Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25-42

26 UDP Forwarding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
UDP Relay and RIF Stripping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1
UDP Relay Hardware/Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2

UDP Relay Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-3
BOOTP/DHCP Relay . . . . . . . . . . . . . . . . . . . . . . . .
Overview of DHCP . . . . . . . . . . . . . . . . . . . . . .
DHCP and the OmniS/R . . . . . . . . . . . . . . . . . .
BOOTP/DHCP Relay and Source Routing . . . . . .
BOOTP/DHCP Relay and Authentication . . . . . .
External BOOTP Relay . . . . . . . . . . . . . . . . . . .
Internal BOOTP/DHCP Relay . . . . . . . . . . . . . . .
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling BOOTP/DHCP Relay . . . . . . . . . . . . . .
Configuring BOOTP/DHCP Relay Parameters

.
.
.
.
.
.
.
.
.
.
.

. 26-4
. 26-4
. 26-4
. 26-5
. 26-5
. 26-6
. 26-7
. 26-7
. 26-8
. 26-9
.26-10

NetBIOS Relays . . . . . . . . . . . . . . . . . . . . .
Overview of NetBIOS . . . . . . . . . . . . .
NetBIOS Relay Application . . . . . . . . .
Configuring NBNS Relay . . . . . . . . . . .
Next-Hop Addresses for NBNS . . . .
Forwarding VLANs for NBNS Relay .
Configuring NBDD Relay . . . . . . . . . . .
Next-Hop Addresses for NBDD . . .
Forwarding VLANs for NBDD Relay

.
.
.
.
.
.
.
.
.

.26-11
.26-11
.26-12
.26-13
.26-14
.26-15
.26-16
.26-17
.26-18

Generic Service UDP Relay . . . .
Generic Services Menu . . . .
Adding a Generic Service . . .
Modifying a Generic Service
Deleting a Generic Service . .

.
.
.
.
.

.26-19
.26-19
.26-19
.26-21
.26-22

.
.
.
.
.

Viewing UDP Relay Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26-23

page xxii

Table of Contents

27 IPX Routing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1

Introduction . . . . . . . . . . . . . . . . . . . . . .
IPX Routing Overview . . . . . . . . . . . .
IPX Protocols . . . . . . . . . . . . . . . .
Setting Up IPX Routing on the Switch

.
.
.
.

27-1
27-2
27-2
27-3

The IPX Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-4
Viewing the IPX Routing Table . . . . . . . . . . . . . . . .
Displaying All Entries in the IPX Routing Table .
Using IPXR with Frame Relay or ISDN Boards
Displaying a List of Specific IPX Routes . . . . . . .

...
...
..
...

.
.
.
.

27-5
27-5
27-6
27-7

Viewing IPX Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-8
Viewing the IPX SAP Bindery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-10
Using IPXSAP with Frame Relay or ISDN Boards . . . . . . . . . . . . . . . . . . .27-11
Displaying a List of Specific SAP Servers . . . . . . . . . . . . . . . . . . . . . . . . .27-11
Adding an IPX Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-12
Removing an IPX Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-13
Turning the IPX Router Complex On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . .27-14
Flushing the IPX RIP/SAP Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-15
Using the IPXPING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-16
Configuring IPX RIP/SAP Filtering . . . . . . . . . . . .
Adding a “Global” IPX RIP/SAP Filter . . .
Adding an IPX RIP/SAP Filter for a Specific
Deleting an IPX RIP/SAP Filter . . . . . . . . . . . .
Displaying IPX RIP/SAP Filters . . . . . . . . . . . .
Displaying a List of All IPX Filters . . . . . . .
Displaying a List of “Global” IPX Filters . .
Displaying a List of Specific IPX Filters . . .
IPX RIP/SAP Filter Precedence . . . . . . . . . . . .

.............
.............
Group or VLAN
.............
.............
.............
.............
.............
.............

.
.
.
.
.
.
.
.
.

.27-18
.27-19
.27-20
.27-22
.27-23
.27-23
.27-24
.27-24
.27-25

Configuring IPX Serialization Packet Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . .27-26
Enabling IPX Serialization Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-26
Disabling IPX Serialization Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-27
Configuring IPX Watchdog Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-28
Enabling IPX Watchdog Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-28
Disabling IPX Watchdog Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-29
Configuring SPX Keepalive Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-30
Enabling SPX Keepalive Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-30
Disabling SPX Keepalive Spoofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-31
Controlling IPX Type 20 Packet Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-32
Configuring NetWare to Minimize WAN Connections . . . . . . . . . . . . . . . . . . . . .27-33
Configuring RIP and SAP Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-35
Adding a RIP and SAP Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-35
Viewing RIP and SAP Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27-36
page xxiii

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 . . . . . . . . .

28 Managing WAN Switching Modules
Introduction . . . . . . . . . . . . . . .
Type of Service (ToS) . . . . .
ToS and QoS Interaction
DTR Dial Backup . . . . . . . .

.
.
.
.

.27-38
.27-38
.27-38
.27-38

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-1

.
.
.
.

28-1
28-2
28-4
28-5

Supported Physical Interfaces . . .
Universal Serial Port . . . . . . .
ISDN Basic Rate Interface Port
Fractional T1 Port . . . . . . . . .
Fractional E1 Port . . . . . . . . .

.
.
.
.
.

28-6
28-6
28-6
28-6
28-6

Supported Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28-7
Application Examples . . . . . . . . . . . . . . . . . .
Frame Relay WSX Using Serial Ports . . . . .
Back-to-Back WSX Using T1 Ports . . . . . .
Combined Frame Relay with ISDN Backup

.
.
.
.

28-7
28-7
28-8
28-9

Omni Switch/Router WAN Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28-10
Cable Interfaces for Universal Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28-11
DTE/DCE Type and Transmit/Receive Pins . . . . . . . . . . . . . . . . . . . . . . . . . .28-11
Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28-12
Loopback Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28-13
The WAN Port Software Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISDN-BRI Port Example . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fractional T1 Port Example . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Configuration Parameters for the WSX . . . . . . . . . . . .
Viewing Parameters for all Submodules in the Chassis . . . . .
Viewing Parameters for all Ports in a Single Submodule . . .
Viewing Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining Status and Statistical Information . . . . . . . . . . . . . . .
Obtaining Information on All Boards in a Switch . . . . . . . .
Obtaining Information on the Ports for a Single WSX Board
Viewing Information on a Single Port . . . . . . . . . . . . . . . . .
Configuring 31 Timeslots on a WAN E1 Port . . . . . . . . . . . . . . .
page xxiv

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.28-14
.28-14
.28-14
.28-15
.28-21
.28-24
.28-27
.28-27
.28-28
.28-29
.28-37
.28-38
.28-38
.28-40
.28-42
.28-45

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-5
Virtual Circuits and DLCIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-6
WSX Self-Configuration and Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29-7
Congestion Control . . . . . . . . . . . . . . . . . . . . . . .
Regulation Parameters . . . . . . . . . . . . . . .
Discard Eligibility (DE) Flag . . . . . . . . . . .
Interaction Among Congestion Parameters
Notification By BECN . . . . . . . . . . . . . . . .
Notification By FECN . . . . . . . . . . . . . . . .

.
.
.
.
.
.

. 29-8
. 29-8
. 29-9
. 29-9
.29-11
.29-12

Frame Formats Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-13
Bridging Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-14
Frame Relay IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-15
The Frame Relay Subnet and “Split Horizon” . . . . . . . . . . . . . . . . . . . . .29-16
Frame Relay IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-18
Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-19
Frame Relay Fragmentation Interleaving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-20
The Frame Relay Software Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-21
Setting Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-22
Modifying a Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-22
Modifying a Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-29
Adding a Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-32
Viewing Configuration Parameters for the WSX . . . . . .
Viewing Parameters for all WSXs in the Chassis
Viewing Port Parameters . . . . . . . . . . . . . . . . .
Viewing Virtual Circuit Parameters . . . . . . . . . .

.
.
.
.

.29-33
.29-33
.29-34
.29-35

Deleting Ports and Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-36
Deleting a Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-36
Deleting a Port and Its Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . .29-37
Obtaining Status and Statistical Information . . . . . . .
Information on All Boards in a Switch . . . . .
Information on the Ports for One WSX Board
Information on One Port . . . . . . . . . . . . . . .
Information on One Virtual Circuit . . . . . . . .

.
.
.
.
.

.29-38
.29-38
.29-42
.29-43
.29-51

Resetting Statistics Counters .
Resetting Statistics for
Resetting Statistics for
Resetting Statistics for

.
.
.
.

.29-54
.29-54
.29-54
.29-54

..................
a WSX Board . . . . . . .
a WSX Port . . . . . . . . .
a Virtual Circuit (DLCI)

page xxv

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 . . . . . . . . . . . . . . . . . . . . .29-60
Configuring a Trunking Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-62
Viewing Frame Relay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-64
Modifying a Frame Relay Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-65
Deleting a Frame Relay Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29-66

30 Point-to-Point Protocol

..............
PPP Connection Phases . . . . . . . . . . . . . . .
Data Compression . . . . . . . . . . . . . . . . . . .
Multi-Link PPP . . . . . . . . . . . . . . . . . . . . .
Multilink Modes of Operation . . . . . . . .
PPP Fragmentation Interleaving . . . . . . . . .
Overview of PPP Configuration Procedures

.
.
.
.
.
.
.

30-1
30-1
30-2
30-2
30-3
30-3
30-4

The PPP Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-6
PPP Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-6
Setting Global PPP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-7
Adding a PPP Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30-9
Modifying a PPP Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30-15
Viewing PPP Entity Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30-16
Displaying the Configuration of All PPP Entities . . . . . . . . . . . . . . . . . . .30-16
Displaying the Configuration of a Specific PPP Entity . . . . . . . . . . . . . . .30-17
Displaying PPP Entity Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30-18
Displaying the Status of All PPP Entities . . . . . . . . . . . . . . . . . . . . . . . . .30-18
Displaying the Status of a Specific PPP Entity . . . . . . . . . . . . . . . . . . . . .30-19
Deleting a PPP Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30-21

31 WAN Links

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-1
Configuring WAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-1
The Link Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-2
Adding a WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-3
Adding WSX Port Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-3
Adding ISDN Call Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-4
Modifying a WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-9
Modifying ISDN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31-9
Modifying WSX Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-10
Deleting WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-11

page xxvi

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .31-15
Displaying Status for a Specific WAN Link . . . . . . . . . . . . . . . . . . . . . . .31-16

32 Managing ISDN Ports

................................
Overview of ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic Rate Interface (BRI) Versus Primary Rate Interface (PRI)
“U”, “S/T” , and “R” Interfaces . . . . . . . . . . . . . . . . . . . . . . .
The “B,” “D,” and “H” Channels . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.

32-1
32-1
32-1
32-2
32-2

The ISDN Submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-3
Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-3
Modifying an ISDN Configuration Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-4
Deleting an ISDN Configuration Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-5
Viewing an ISDN Configuration Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32-6
Displaying ISDN Configuration Entry Status .
Displaying Status of All ISDN Ports . . . .
Displaying Status of a Specific ISDN Slot
Displaying Status of a Specific ISDN Port

33 Managing T1 and E1 Ports

.
.
.
.

32-7
32-7
32-8
32-9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-1

T1 and E1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-2
The T1/E1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-3
Configuring a T1 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-4
Configuring an E1 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33-8
Viewing T1/E1 Configuration and Alarm Information . . .
Viewing Information for all T1/E1 Ports in the Switch
Viewing Information for T1/E1 Ports on One Module
Viewing Information For a T1 Port . . . . . . . . . . . . . .
Viewing Information For an E1 Port . . . . . . . . . . . . .

.
.
.
.
.

.33-11
.33-11
.33-12
.33-13
.33-15

Viewing T1/E1 Local Statistics . . . . .
Viewing Total Local Statistics . . .
Viewing Current Local Statistics .
Viewing Local Historical Statistics

.
.
.
.

.33-17
.33-17
.33-18
.33-19

Viewing T1 Remote Statistics . . . . . . . . . . . . . . .
Viewing Total Remote Statistics . . . . . . . . . .
Viewing Current Remote Statistics . . . . . . . .
Viewing Remote Historical Statistics . . . . . . .
Clearing the Framer Statistics for a T1/E1 Port

.
.
.
.

.
.
.
.
.

.33-20
.33-20
.33-21
.33-21
.33-22

page xxvii

Table of Contents

34 Backup Services

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34-1
Backup Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the Backup Services Menu . . . . . . . . . . . . . . . . . . . . . .
Adding a Backup Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a backup for a Physical Port . . . . . . . . . . . . . . . . . . . .
Backing Up a Frame Relay PVC . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Backup Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a backup for a Physical Port . . . . . . . . . . . . . . . . . .
Modifying a Frame Relay PVC Backup Service . . . . . . . . . . . .
Viewing Backup Service(s) Configurations . . . . . . . . . . . . . . . . . .
Viewing the Configurations of All Backup Services . . . . . . . . .
Viewing the Configuration of a Single Backup Service (bsview
Command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Backup Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Backup Service Statistics . . . . . . . . . . . . . . . . . . . . . . . . .
Clearing Backup Service Statistics . . . . . . . . . . . . . . . . . . . . . .

35 Troubleshooting

.
.
.
.
.
.
.
.
.
.

. 34-2
. 34-2
. 34-3
. 34-3
. 34-6
. 34-9
. 34-9
.34-10
.34-11
.34-11

.
.
.
.

.34-11
.34-11
.34-12
.34-13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-1

Detecting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-1
Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-3
Report Hardware Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-3
Report Software Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-4
Understanding Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-5
Software Installation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35-5
Operational Problems . . . . . . . . .
Deadlocked VLAN . . . . . . . . .
Probable Cause . . . . . . . .
Solution . . . . . . . . . . . . . .
Problems with IP Applications
Probable Cause . . . . . . . .
Solution . . . . . . . . . . . . . .
Protocol Problems . . . . . . . . .
Probable Cause . . . . . . . .
Solution . . . . . . . . . . . . . .

page xxviii

.
.
.
.
.
.
.
.
.
.

35-6
35-6
35-7
35-7
35-7
35-7
35-7
35-8
35-8
35-8

Hardware Problems . . . . . . . . . . . . .
LEDs Do Not Light on All Modules
Probable Cause . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . .
Amber Color in LEDs . . . . . . . . . .
Probable Cause . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . .
Non-Blinking OK2 LED . . . . . . . .
Probable Cause . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.

35-9
35-9
35-9
35-9
35-9
35-9
35-9
35-9
35-9
35-9

Table of Contents
TEMP LED is Amber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STA LED Is Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Does Not Boot When Flash File System Is Full and Trying To Create
the mpm.cnf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding Error Messages . . . . . . . . . . . .
Correcting Errors . . . . . . . . . . . . . . . . . . . . . .
Module Startup/Shutdown Error Messages
Serial Port Configuration Errors . . . . . . . .
Module Connection Errors . . . . . . . . . . . .
Chassis Error Messages . . . . . . . . . . . . . .
Chassis Error Messages Table . . . . . . . . . .

.
.
.
.
.
.
.
.

.35-10
.35-10
.35-10
.35-10
.35-10
.35-10
.35-10
.35-10
.35-11
.35-11
.35-11
.35-11
.35-12
.35-12
.35-13
.35-13

36 Running Hardware Diagnostics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-1
Running Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-2

Login to Run Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-3
Resetting a Switching Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-4
Disabling a Switching Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-4
Temperature Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-5
Running Hardware Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Halting Diagnostic Tests in Progress . . . . . . . . . . . . . . . . . . . .
Port Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Omni Switch/Router Port Test Wrap Cable/Plug Requirements
Sample Test Session: Ethernet Module . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.

. 36-6
. 36-9
. 36-9
. 36-9
.36-10
.36-12

Displaying Available Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36-15
Configuring the Diagnostic Test Environment . . . . . . . . . . . . . . . . . . . . . . . . . . .36-16
Configuring Tests for Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . .36-17
Running Frame Fabric Tests on Omni Switch/Routers . . . . . . . . . . . . . . . . . . . . .36-18
Running Diagnostics on an Entire Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36-20
Diagnostic Test Cable Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36-22

page xxix

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) . . . .
Listing Available Files in the Flash Memory (L)
Deleting All Files in the Flash Memory (P) . . .
Deleting Specific Files in the Flash Memory (R)
Saving Configuration Changes (S) . . . . . . . . . .
Viewing Version Number (V) . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.

A-3
A-3
A-4
A-4
A-5
A-5
A-5
A-6
A-6

Configuring a Switch with an MPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

B Custom Cables

.............................................
V.35 DTE Cable (For WSX-to-DCE Device Connection) . . . . . . . . . . . . .
V.35 DCE Cable (For WSX-to-DTE Device Connection) . . . . . . . . . . . . .
RS232 DTE Cable (For WSX-to-DCE Device Connection) . . . . . . . . . . . .
RS232 DCE Cable (For WSX-to-DTE Device Connection) . . . . . . . . . . . .
RS530 DTE Cable (For WSX-to-DCE Device Connection) . . . . . . . . . . . .
RS530 DCE Cable (For WSX-to-DTE Device Connection) . . . . . . . . . . . .
X.21 DTE Cable (For WSX-to-DCE Device Connection) . . . . . . . . . . . . .
X.21 DCE Cable (For WSX-to-DTE Device Connection) . . . . . . . . . . . . .
RS449 DTE Cable (For WSX-to-DCE Device Connection) . . . . . . . . . . . .
RS-449 DCE Cable Assembly (For WSX-to-DTE Device 75W Connection)
RJ-45 to DB15F Cable Assembly (For T1/E1 Port 120W Connections) . . .
RJ-45 to BNC Cable Assembly (For E1 75W Port Connections) . . . . . . . .

Index

page xxx

.
.
.
.
.
.
.
.
.
.
.
.
.

. B-1
. B-2
. B-3
. B-4
. B-5
. B-6
. B-7
. B-8
. B-9
B-10
B-11
B-12
B-13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1

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.5, ATM, Token
Ring, M013, and Mammoth-based Ethernet Modules are
no longer supported.
Omni Switch/Router modules can be distinguished
from older OmniSwitch modules by the X in the
module name. For example, the ESM-100C-32W is an
OmniSwitch module whereas the ESX-100C-32W is an
Omni Switch/Router module.
Omni Switch/Router has a distributed switching fabric. In a 9-slot chassis operating at full
duplex, Omni Switch/Router offers an aggregate 22 Gigabit per second (Gbps) distributed
switching fabric. In addition, Omni Switch/Router offers new high density switching modules,
including auto-sensing 10/100 Ethernet modules that offer high speed network connections to
servers and desktops. (See Omni Switch/Router Applications and Configurations on page 1-5
for examples.)
The Omni Switch/Router Management Processor Module (MPX) module provides the core
routing, VLAN MAC learning, SNMP, and file management functions for the entire Omni
Switch/Router. In addition, the MPX has an Ethernet plug-in port for managing the switch.
Only one MPX is required per Omni Switch/Router, but you can add another MPX for
redundancy. See Chapter 2, “The Omni Switch/Router MPX,” for more information on
the MPX.
♦ Important Note ♦
Omni Switch/Router switching modules require an
MPX. You cannot install any version of the MPM (i.e.,
MPM-C, MPM 1G, MPM II, or original MPM) in a chassis
with an MPX.
An Omni Switch/Router Hardware Routing Engine (HRE-X). 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 The Omni Switch/Router Hardware Routing Engine (HRE-X) on page 1-22 for
more information on the HRE-X.
Omni Switch/Router switching modules perform software filtering, translations between
dissimilar network interfaces, and hardware-based switching. Omni Switch/Router switching
modules have an additional on-board interface connector for the HRE-X.

Page 1-1

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). Do not
install an Omni Switch/Router module in an
OmniSwitch chassis and do not install an OmniSwitch
module in an Omni Switch/Router chassis.

Omni Switch/Router User Interface (UI) Software
Omni Switch/Router hardware uses the same User Interface (UI) commands and Network
Management Software (NMS) as OmniSwitch hardware. Omni Switch/Router modules support
broadcast management, multicast management, any-to-any switching, virtual LANs (VLANs),
firewalls, user authentication, WAN access, and policy-based configuration.
♦ 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. Chapter 4, “The User Interface,” includes documentation on changing from CLI mode to UI mode.

Omni Switch/Router Network Management Software (NMS)
You need Release 3.4, or higher, of Alcatel’s X-Vision Network Management Software (NMS)
to operate with Omni Switch/Router hardware.

Page 1-2

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).
Central Switching Engine
Note: Unlike distributed switch
fabric, data is forced to cross
switch fabric twice.

➋

➊

Switch Fabric

I/O Port

➌

I/O Port

❹

Traditional Shared Memory Architecture
In contrast, Omni Switch/Router switches use a distributed switching fabric. As shown in the
figure below, data enters the input port and crosses the switching fabric only once before
exiting the appropriate output port. Compared to the shared memory architecture, only half
as much bandwidth is required since data just crosses the switching fabric once.
Switch Fabric

I/O Port

Omni Switch/Router Distributed Switching Fabric

Page 1-3

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. As shown in the figure below, an OmniS/R-9 with an MPX and
eight (8) Omni Switch/Router switching modules provides 22 Gbps of switching capacity. An
an OmniS/R-5 with an MPX and four (4) Omni Switch/Router switching modules provides 12
Gbps of switching capacity, while an OmniS/R-3 with an MPX and two (2) Omni
Switch/Router switching modules provides 7 Gbps of switching capacity.
Fabric Capacity
(Gbps)
22

OmniS/R-9

OmniS/R-5
12
OmniS/R-3
7

MPX

Omni Switch/Router Switching Modules

Omni Switch/Router Fabric Capacity in OmniS/R-3, OmniS/R-5 and OmniS/R-9 Chassis

Page 1-4

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 as the Backbone Connecting Several Networks
The figure below shows how Omni Switch/Router Gigabit Ethernet and 10/100 Ethernet
modules can be used as a network backbone. In this example, two networks on two different floors need high speed access to a server farm on the first floor.
Server

10/100 Ethernet

3rd Floor

OmniSwitch

Fast Ethernet
(OmniChannel)
2nd Floor
10/100 Ethernet
OmniStack

Gigabit Ethernet
Fast Ethernet
(OmniChannel)

Gigabit Ethernet
1st Floor

Omni Switch/Router
Server Farm

Using Omni Switch/Router in a Network Backbone

The servers each have dedicated Gigabit Ethernet connections to Omni Switch/Router
modules on the first floor. The Omni Switch/Router chassis on the first floor is connected to
the network on the second floor via a Gigabit Ethernet link to the OmniStack on the second
floor. The Omni Switch/Router chassis on the first floor is connected via a 10/100 Ethernet
link, using OmniChannel, to the OmniSwitch chassis on the third floor containing a Fast
Ethernet module, such as the ESM-100C-12. See Chapter 15, “Managing Ethernet Modules,” for
more information on OmniChannel.

Page 1-5

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. In addition, this Omni Switch/Router chassis
connects the workstations to a local server with a Gigabit Ethernet module. On the second
floor, an Omni Switch/Router connects legacy Token Ring workstations. On the first floor, the
Omni Switch/Router connects the networks on the upper floors to the server farm using a
Gigabit Ethernet module.
Server

3rd Floor
10/100 Ethernet
Omni Switch/Router

2nd Floor
Token Ring
Omni Switch/Router
Gigabit Ethernet

Gigabit Ethernet
1st Floor
Omni Switch/Router
Server Farm

Using Omni Switch/Router in the Wiring Closet

Page 1-6

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. (See Chapter 3, “Omni Switch/Router Switching Modules,”
for more information on hot swapping switching modules.)
There are three (3) different versions of the Omni Switch/Router chassis. The OmniS/R-3, a
three-slot version, is documented in OmniS/R-3 on page 1-8. The OmniS/R-5, a five-slot
version, is documented in OmniS/R-5 on page 1-10. A nine-slot version called the OmniS/R-9
is documented in OmniS/R-9 and OmniS/R-9P on page 1-13. The OmniS/R-3, OmniS/R-5 and
OmniS/R-9 chassis, the MPX module, and several switching modules have met FCC Class B
requirements.
♦ Note ♦
In the current release, a maximum of seven (7) 32-port
switching modules (e.g., ESX-100C-32W) is supported in
9-slot Omni Switch/Router chassis.
Slot 1 is reserved for the MPX; you cannot install a switching module in Slot 1. You can install
a switching module in Slot 2 (if an MPX is installed in Slot 1) or an MPX. When dual-redundant MPXs are installed, one of them must be installed in Slot 1 and the other in Slot 2. On the
OmniS/R-3, Slot 3 is reserved for a switching module. On the OmniS/R-5, Slots 3 through 5
are reserved for switching modules. On the OmniS/R-9, Slots 3 through 9 are reserved for
switching modules.
♦ Important Note ♦
You must have an MPX acting as the management
module; you cannot use any version of the MPM.
Warning
If you have any empty switching module slots in either
an OmniS/R-3 (3-slot) or OmniS/R-5 (5-slot) chassis,
you must cover them with blank panels (available from
Alcatel) to prevent your chassis from overheating.
Covering empty slots forces air to flow directly over the
power supplies, thereby cooling them. If the power
supplies are not properly cooled, they will overheat
and shut down.

Page 1-7

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. You can view all cabling, power supplies, module interfaces, and LEDs at the front of the chassis.
The OmniS/R-3 uses a built-in AC power supply that has a capacity of 32.8 Amps at 5 volts
and 3 amps at 12 volts for 200 Watts of output power. The OmniS/R-3 does not support a
Backup Power Supply (BPS).
♦ Caution ♦
Do not connect the power connector on the back of
the OmniS/R-3 to data communication equipment.

Management
Processor
Module (MPX)

R
E
TH
E

A LIN C
O
C
T K L

C
O
N
S
O
LE

M
O
D
E
M

T
S PR EM
E
C I
P

P
S PS
2
1

MPX 10

2
X

GSX-K sm

Switching
Modules

B
T_
A
T_

2
62
TM

X
R

R
R
E
C _B
D
E
R _A
D
E

Y
E
L,F
E
R
F

A
LA
R
M

ASX 622 sm

OmniS/R-3 Chassis

♦ Important Note ♦
Slot 1 (the top slot) on the OmniS/R-3 is reserved for
an MPX module. Slot 2 can accommodate either a
second (optional) MPX module or a Switching module.
Slot 3 (the bottom slot) is reserved for a Switching
module. Contact your Alcatel sales representative for
information regarding module availability.

Page 1-8

Omni Switch/Router Chassis and Power Supplies

OmniS/R-3 Chassis Technical Specifications
Total Module Slots

Total Slots for Switching Modules

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.7 Amps at 230 VAC

Watts (Output)

200

Current Provided

32.8 Amps at +5 Volts
3 Amps at +12 Volts

Heat Generation

Approximately 1020 BTUs per hour

Temperature Operating Range

0 to 45 degrees Celsius
32 to 113 degrees Fahrenheit

Humidity

5% to 90% Relative Humidity (Operating)
0% to 95% Relative Humidity (Storage)

Altitude

Sea level to 10,000 feet (3 km)

Agency Listings

UL 1950
CSA-C22.2
EN60950
FCC Part 15, Subpart B (Class A)
EN55022, 1987/EN50081
FCC Class B
C.I.S.P.R. 22: 1985
EN50082-1, 1992
IEC 801-2, 1991
IEC 801-3, 1984
IEC 801-4, 1988
VCCI V-3/94.04 (Class A & Class B)
EN 61000-4-2: 1995
EN 61000-4-3: 1995
EN 61000-4-4: 1995
EN 61000-4-5: 1995
EN 61000-4-6: 1996
EN 61000-4-8: 1993
EN 61000-4-11: 1994
ENV 50204: 1996

Page 1-9

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. In addition, if you have any empty switching
module slots in an OmniS/R-5, you must cover them
with blank panels (available from Alcatel) to prevent
your chassis from overheating.
Covering empty slots forces air to flow directly over the
power supplies, thereby cooling them. If the power
supplies are not properly cooled, they will overheat
and shut down.
The entire chassis can be wall-mounted or rack-mounted. You can view all cabling, power
supplies, module interfaces, and LEDs at the front of the chassis.
Omni Switch/Router
Management Processor
Module (MPX)

Switching Modules

PS1 (Power Supply 1)

PS2 (Power Supply 2)

The OmniS/R-5

The OmniS/R-5 uses the MPX. Slot 1 is reserved for the MPX; you cannot install a switching
module in Slot 1. You can install a switching module in Slot 2 (if an MPX is installed in Slot 1)
or an MPX. When dual-redundant MPXs are installed, one of them must be installed in Slot 1
and the other in Slot 2. Slots 3 through 5 are reserved for switching modules.

Page 1-10

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. See OmniS/R-5 Technical Specifications on page 1-12 for more information.
The OmniS/R-5 uses one of the following power supplies:
OmniS/R-PS5-375

The standard power supply. It can provide 375 Watts of power.

OmniS/R-PS5-DC375 A -48 volt (input voltage) DC version of the OmniS/R-PS5-375 power
supply. This power supply can provide 375 Watts of power. It requires
the use of 12 to 14 gauge wire for connections to the DC power source.
See Connecting a DC Power Source to an OmniS/R-PS5-DC375 on page
1-24 for more information.
♦ Caution ♦
This unit may be equipped with two power connections. To reduce the risk of electrical shock, disconnect
both power connections before servicing the unit.
♦ VORSICHT ♦
Das Gerat kann mit zwei Netzanschlussen ausgestattet
sein. Um einen elektrischen Schlag zu vermeiden,
immer beide Anschlusse vor der Wartung vom Netz
trennen.

Page 1-11

Omni Switch/Router Chassis and Power Supplies

OmniS/R-5 Technical Specifications
Total Module Slots

Total Slots for Switching Modules

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.

Current Draw

6 Amps at 100/115 VAC; 3 Amps at 230 VAC

Watts (Output)

375

Current Provided

60 Amps at 5 Volts (V1)
5 Amps at 12 Volts (V2)
3 Amps at 3.3 Volts (V3)
5.1 Amps at 1.5 Volts (V4)

Temperature Operating Range

0 to 45 degrees Celsius
32 to 113 degrees Fahrenheit

Humidity

5% to 90% Relative Humidity (Operating)
0% to 95% Relative Humidity (Storage)

Altitude

Sea level to 10,000 feet (3 km)

Heat Generation

1280 BTUs per hour (one power supply)

Agency Listings

Page 1-12

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.
Switching Modules

Omni Switch/Router
Management Processor
Module (MPX)

Fan Tray

Lifting Handle

PS1 (Power Supply 1)
PS2 (Power Supply 2)

The OmniS/R-9
A fully loaded OmniS/R-9 weighs nearly 100 lbs. Therefore, it is recommended that if you are
rack-mounting the chassis you use a rack mount shelf instead of just brackets. Using a shelf
will ensure that the weight of the chassis can be supported. In addition, the OmniS/R-9
contains side handles to make lifting and installation easier.
The OmniS/R-9 uses the MPX. Slot 1 is reserved for the MPX; you cannot install a switching
module in Slot 1. You can install a switching module in Slot 2 (if an MPX is installed in Slot 1)
or an MPX. When dual-redundant MPXs are installed, one of them must be installed in Slot 1
and the other in Slot 2. Slots 3 through 9 are reserved for switching modules.
♦ Important Note ♦
You must have an MPX acting as the management
module; you cannot use any version of the MPM. See
Chapter 2, “The Omni Switch/Router MPX,” for more
information on the MPX.

Page 1-13

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. See Chapter 1, “Omni
Switch/Router Chassis and Power Supplies,” for additional information on installing and
removing power supplies.
The OmniS/R-9 uses the following power supply:
OmniS/R-PS9-650

The standard power supply. It can provide 650 Watts of power.

The OmniS/R-9P uses the following power supply:
OmniS/R-PS9-725

This power supply can provide 725 Watts of power.

The OmniS/R-9P-48V uses the following power supply:
OmniS/R-PS9-DC725 A -48 Volt (input voltage) DC version of the OmniS/R-PS9-725 power
supply. This power supply can provide 725 Watts of power. It requires
the use of 12 to 14 gauge wire for connections to the DC power source.
See Connecting a DC Power Source to an OmniS/R-PS9-DC725 on page
1-27 for more information.
For additional information, see OmniS/R-9 Technical Specifications on page 1-15, OmniS/R-9P
Technical Specifications on page 1-16 and OmniS/R-9P-48V Technical Specifications on page
1-17.
♦ Caution ♦
This unit may be equipped with two power
connections. To reduce the risk of electrical shock,
disconnect both power connections before servicing
the unit.
♦ VORSICHT ♦
Das Gerat kann mit zwei Netzanschlussen ausgestattet
sein. Um einen elektrischen Schlag zu vermeiden,
immer beide Anschlusse vor der Wartung vom Netz
trennen.

Page 1-14

Omni Switch/Router Chassis and Power Supplies

OmniS/R-9 Technical Specifications
Total Module Slots

Total Slots for Switching Modules

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

90-264 VAC, 47 to 63 Hz

Current Draw

12 Amps at 100/115 VAC; 6 Amps at 230 VAC

Watts (Output)

650

Current Provided

120 Amps at 5 Volts
4 Amps at 12 Volts
6 Amps at 3.3 Volts
8 Amps at 1.5 Volts

Temperature Operating Range

0 to 45 degrees Celsius
32 to 113 degrees Fahrenheit

Humidity

5% to 90% Relative Humidity (Operating)
0% to 95% Relative Humidity (Storage)

Altitude

Sea level to 10,000 feet (3 km)

Heat Generation

2219 BTUs per hour (one power supply)

Agency Listings

Page 1-15

Omni Switch/Router Chassis and Power Supplies

OmniS/R-9P Technical Specifications
Total Module Slots

Total Slots for Switching Modules

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

85-270 VAC, 47 to 63 Hz

Current Draw

12 Amps at 100/115 VAC; 6 Amps at 230 VAC

Watts (Output)

725

Current Provided

120 Amps at 5 Volts
6 Amps at 12 Volts
6 Amps at 3.3 Volts
8 Amps at 1.5 Volts

Temperature Operating Range

0 to 70 degrees Celsius
32 to 158 degrees Fahrenheit

Humidity

5% to 90% Relative Humidity (Operating)
0% to 95% Relative Humidity (Storage)

Altitude

Sea level to 10,000 feet (3 km)

Heat Generation

2219 BTUs per hour (one power supply)

Agency Listings

UL 1950; CSA-C22.2 #950-M90; TUV EN60950; CB
Certification IEC 950; FCC Title 47 CRF Part 15, Subpart B
(Class A & Class B); IEC EN55022, 1995 (Class A & Class B)
CISPR 22, 1995; IEC 1000-3-2; IEC 1000-3-3 (EN60555-2); IEC
1000-4-2 (EN61000-4-2, per EN50082-1, 1992); IEC 1000-4-3
(EN61000-4-3, per EN50082-1, 1992); IEC 1000-4-4
(EN61000-4-4) Level 4; IEC 1000-4-5 (EN61000-4-5) Level 4;
IEC 1000-4-6 (EN61000-4-6); IEC 1000-4-8 (EN61000-4-8);
IEC 1000-4-11 (EN61000-4-11); EN50204: 1996.

Page 1-16

Omni Switch/Router Chassis and Power Supplies

OmniS/R-9P-48V Technical Specifications
Total Module Slots

Total Slots for Switching Modules

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.15 VDC
6 Amps at 12 VDC
6 Amps at 3.3 VDC
8 Amps at 1.5 VDC

Temperature Operating Range

0 to 70 degrees Celsius
32 to 158 degrees Fahrenheit

Humidity

5% to 90% Relative Humidity (Operating)
0% to 95% Relative Humidity (Storage)

Altitude

Sea level to 10,000 feet (3 km)

Heat Generation

2219 BTUs per hour (one power supply)

Agency Listings

UL 1950; CSA-C22.2 #950-M90; TUV EN60950; CB
Certification IEC 950; FCC Title 47 CRF Part 15, Subpart B
(Class A & Class B); IEC EN55022, 1995 (Class A & Class B)
CISPR 22, 1995; IEC 1000-3-2; IEC 1000-3-3 (EN60555-2); IEC
1000-4-2 (EN61000-4-2, per EN50082-1, 1992); EN55024 IEC
1000-4-3 (EN61000-4-3, per EN50082-1, 1992); IEC 1000-4-4
(EN61000-4-4) Level 4; IEC 1000-4-5 (EN61000-4-5) Level 4;
IEC 1000-4-6 (EN61000-4-6); IEC 1000-4-8 (EN61000-4-8);
IEC 1000-4-11 (EN61000-4-11); ENV 50204: 1996.

Page 1-17

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.
The total power consumption of all your modules should be below the current provided by
your power supply, which is listed in OmniS/R-3 on page 1-8 for the OmniS/R-3, OmniS/R-5
on page 1-10 for the OmniS/R-5 and OmniS/R-9 and OmniS/R-9P on page 1-13 for the
OmniS/R-9 and OmniS/R-9P. For power consumption and FCC compliance information for
Omni Switch/Router VoIP modules, consult your VoIP User Manual.
♦ Caution ♦
It is possible, but not recommended, to have a
configuration in which the current draw of the installed
modules exceeds the power provided by a single
power supply. However, such a configuration would
require two power supplies and would not allow you to
have power redundancy.

Page 1-18

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

ESX-K-100C-32W

Advanced auto-Sensing 10/100 Ethernet
module with thirty-two (32) RJ-45 ports.

10.25

ESX-K-100FM/FS-16W

Advanced Fast Ethernet (100 Mbps) module
with sixteen (16) fiber MT-RJ ports.

9.75

GSX-K-FM/FS-2W

Advanced Gigabit Ethernet module with two
(2) fiber SC ports.

5.25

B (STP cable)
A (UTP cable)

WSX-S-2W

WAN module with 2 serial ports

4.75

WSX-SC-4W

WAN module with 4 serial ports

6.25

WSX-SC-8W

WAN module with 8 serial ports

8.25

WSX-BRI-SC-1W

WAN ISDN module with 1 serial and 1 BRI
port

5.75

WSX-BRI-SC-2W

WAN ISDN module with 2 serial and 2 BRI
ports

7.25

WSX-FT1-SC-1W

WAN module with 1 serial and 1 T1 or E1
port

5.75

WSX-FE1-SC-1W

WAN module with 1 serial and 1 T1 or E1
port

5.75

WSX-FT1-SC-2W

WAN module with 2 serial and 2 T1 or E1
ports

7.25

WSX-FE1-SC-2W

WAN module with 2 serial and 2 T1 or E1
ports

7.25

Page 1-19

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

ESX-K-100C-32W-L3

Advanced auto-Sensing 10/100 Ethernet
module with thirty-two (32) RJ-45 ports.

11.75

ESX-FM-24W-L3

10 Mbps Ethernet module with twenty-four
(24) fiber VF-45 ports

14.5

ESX-K-100FM/FS16W-L3

Advanced Fast Ethernet (100 Mbps) module
with sixteen (16) fiber MT-RJ ports.

11.25

GSX-K-FM/FS-2W-L3

Advanced Gigabit Ethernet module with two
(2) fiber SC ports.

6.75

B (STP cable)
A (UTP cable)

WSX-S-2W-L3

WAN module with 2 serial ports

6.25

B (STP cable)
A (UTP cable)

WSX-SC-4W-L3

WAN module with 4 serial ports

7.75

B (STP cable)
A (UTP cable)

WSX-SC-8W-L3

WAN module with 8 serial ports

9.75

B (STP cable)
A (UTP cable)

WSX-BRI-SC-1W-L3

WAN ISDN module with 1 serial and 1 BRI
port

7.25

B (STP cable)
A (UTP cable)

WSX-BRI-SC-2W-L3

WAN ISDN module with 2 serial and 2 BRI
ports

8.75

B (STP cable)
A (UTP cable)

WSX-FT1-SC-1W-L3

WAN module with 1 serial and 1 T1 or E1
port

7.25

B (STP cable)
A (UTP cable)

WSX-FE1-SC-1W-L3

WAN module with 1 serial and 1 T1 or E1
port

7.25

B (STP cable)
A (UTP cable)

WSX-FT1-SC-2W-L3

WAN module with 2 serial and 2 T1 or E1
ports

8.75

B (STP cable)
A (UTP cable)

WSX-FE1-SC-2W-L3

WAN module with 2 serial and 2 T1 or E1
ports

8.75

B (STP cable)
A (UTP cable)

Page 1-20

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. They are located approximately four (4) inches from the bottom of the chassis
and approximately one (1) inch from the left-hand side of the rear of the chassis.

Lifting Handle

Grounding Screw Holes

Grounding Screw Holes on an OmniS/R-9
On an OmniS/R-5, the grounding screw holes are located approximately one (1) inch from
the bottom of the chassis and approximately one (1) inch from the left-hand side of the rear
of the chassis.
On an OmniS/R-3, they are located approximately four (4) inches from the bottom of the
chassis and approximately one (1) inch from the left-hand side of the rear of the chassis.

Page 1-21

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. If a frame needs to be routed, the HRE-X will automatically add
the appropriate routing information.

Backplane Connector

HRE-X

Module Front Panel

MPX with an HRE-X

The HRE-X has the following restrictions:
• You must have Release 3.4.4 software, or later, on your Omni Switch/Router.
• Do not install an HRE-X on an MPX unless it is Revision A10, or later.
• Do not install an HRE-X on a GSX-FM/FS-4W unless it is Revision B04, or later.

Page 1-22

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.

Valid HRE-X Configurations
You can configure an Omni Switch/Router chassis in one of two ways: with an HRE-X on
every single Omni Switch/Router switching module (distributed routing) or a single HRE-X on
the MPX (centralized routing).
In this configuration, you must install an HRE-X on every single switching
module in the chassis. In addition, you cannot install an HRE-X on the MPX. For example, in
an OmniS/R-9 with a single MPX, you would need eight (8) HRE-Xs for all the switching
modules. As a general rule, this configuration is recommended in networks of more than four
subnets from any one switch.
Distributed Routing.

Centralized Routing. In this configuration, you must install the HRE-X on the MPX but not on
any Omni Switch/Router switching modules. The HRE-X will perform routing for all Omni
Switch/Router switching modules in the chassis. As a general rule, this configuration is recommended for networks of two to four subnets from any one switch.

HRE-X Router Registers versus Feature Limitations
The HRE-X has three (3) registers that can be programmed with a MAC address and mask that
allows it to recognize which destination MAC addresses it should act as a router for. IP Routing, Virtual Router Redundancy Protocol (VRRP), ATM Classical IP (CIP), and Channelized DS3
(i.e., M013) utilize at least one of these registers for their operation. This leads to a restriction
of the combination of these features that can be supported on an Omni Switch/Router at any
given time.
♦ Important Note ♦
ATM and M013 are not supported in Release 4.5.

The HRE-X registers are programmed on a first come, first served basis. Any attempt to
program more than three registers fails. In current release, the order which these features
program the HRE-X is as follows:
1. ATM CIP
2. IP Routing (Note: If there is a second base MAC configured on the MPX, then it will also
take a second register.)
3. M013
4. VRRP
For example, if a switch has two base MACs and a CIP group, then no other features can be
configured. Any combination of the above features will work given the available HRE-X registers. IP routing always takes one register (two in the dual base MAC case), leaving the other
features to compete for the remaining two (one in the dual base MAC case). The other
features attempt to program a register only if they are enabled.
♦ Note ♦
ATM CIP is limited to 128 end node route cache entries.

Page 1-23

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.
OmniS/R-PS5-DC375

(-)/(+)/GND

GND =
OmniS/R-5 DC Power Supply Connector Style

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—12 gauge—that will plug into the power supply. First, make
sure they are not plugged into the 48-volt power source.
2. Next, use a wire stripper to carefully strip about a half-inch off the end of each wire,
removing the outer insulation to expose the copper core.
3. Twist the loose strands of copper wire together so that they form a tight braid. If possible, solder the entire braid of wire together for better conductivity.
4. Open the wire bay door for one of the three (3) power connector holes. The front of this
connector contains a row of square holes. It also contains three (3) circular holes on top
that contain screws; you loosen the screws in these holes to open the wire bay doors
(square holes) on the connector front so that you can insert the wire lead.
a. Insert a small flat-tip screwdriver into one of the top three (3) screw holes.
b. Loosen the screw so that the door for the wire bay on the connector front opens.

Page 1-24

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., negative to negative, positive to positive, ground to ground).
♦ Warning ♦
You must plug DC wire leads into the correct holes in
the DC power connector. Use the labels above the DC
power connector as a guide to positive, negative, and
ground connections.
If you plug wire leads into wrong holes the power
supply will not work and could result in damage.
Push the wire in far enough such that it reaches the back wall of the connector, about a
half inch inside.

(-)/(+)/GND

This end would plug into the
negative (-) power source. The
middle lead would plug into
the positive (+) power source
and the rightmost lead would
plug into the ground (GND).

Inserting the Wire Lead Into the Circular Hole

6. Close the wire bay. 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. You should be able to pull on the wire and not dislodge it.
Page 1-25

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).

Page 1-26

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.
OmniS/R-PS9-DC725

GND/(+)/(-)

GND =
OmniS/R-9P DC Power Supply Connector Style

Installation Requirements
Caution: To reduce the risk of electric shock or energy hazards:
• The branch circuit overcurrent protection must be rated at a minimum of 30 A (amperes)
for the OmniS/R-9P PS9-DC725.
• Use 10 gauge (AWG - American Wire Gauge) solid copper conductors only for the
OmniS/R-9P PS9-DC725.
• A readily-accessible disconnect device that is suitably approved and rated shall be incorporated in the field wiring.
• This device is to be installed in a restricted access area in accordance with the NEC
(National Electrical Code) or the authority having jurisdiction.
• Connect this device to a reliably grounded SELV (Safety Extra Low Voltage) or a centralized DC source.

Page 1-27

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. Next, use a wire stripper to carefully strip about a half-inch off the end of each wire,
removing the outer insulation to expose the copper core.
3. Twist the loose strands of copper wire together so that they form a tight braid. If possible, solder the entire braid of wire together for better conductivity.
4. Open the wire bay door for one of the three (3) power connector holes. The front of the
power connector contains a row of square holes. It also contains three (3) circular holes
(located directly above the square holes) that contain screws; you loosen the screws in
these holes to open the wire bay doors (square holes) on the connector front so that you
can insert the wire leads into the power connector.
a. Insert a small flat-tip screwdriver into one of the three (3) screw holes.
b. Loosen the screw so that the door for the wire bay on the connector front opens.

Loosen Screw.

GND/(+)/(-)

Door inside square hole will
open when screw is loosened in
circular hole directly above it.

Opening Wire Bay on DC Power Supply Connector
5. Insert the appropriate wire lead into the open circular hole. The silkscreen above each
hole indicates which power lead—ground (GND), positive (+), or negative (-)—to plug
into which hole. The lead you insert must match the lead attached to the 48-volt power
source (i.e., ground to ground, positive to positive, negative to negative).
♦ Warning ♦
You must plug DC wire leads into the correct holes in
the DC power connector. Use the labels above the DC
power connector as a guide to ground, positive and
negative connections.
If you plug wire leads into the wrong holes, the power
supply will not work and could result in damage.
Push the wire in far enough so that it reaches the back wall of the connector, about a half
inch inside.

Page 1-28

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. You should be able to pull on the wire and not
dislodge it.
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.,
ground to ground, positive to positive, negative to negative).

Page 1-29

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. Failure to turn the power switch off during
the swapping operation may cause the data switch to
reset and restart.

Replacing Power Supplies (9-Slot Chassis)

Page 1-30

If One of Two
Power Supplies
Fails

Revision

Replace

With

650-watt

Pre-M1

Both
Power
Supplies

Two 650-watt (Revision M1+)
or two 725-watt Power
Supplies

650-watt

M1 or later

Failed
Power
Supply

One 650-watt (Revision M1+)
or one 725-watt Power
Supply

725-watt

Any

Failed
Power
Supply

One 725-watt Power Supply

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.
♦ Important Note ♦
If you have a single MPX in your chassis, it must be
installed in Slot 1.
With the optional HRE-X, which is described in Chapter 1, “Omni Switch/Router Chassis and
Power Supplies,” you can increase routing performance to 1.5 million packets per second.

MPX Technical Specifications
Flash Memory

8 MB (32 MB maximum); 16 MB required for Release 4.4 and
later

SIMM (DRAM) Memory

32 MB (128 MB maximum); 64 MB required for Release 4.4 and
later

SDRAM Memory

16 MB

MAC Addresses Supported

4096

Switching Backplane

Up to 22 Gbps (aggregate) switching fabric capacity

Serial Ports

2 (1 male DB9 modem connector and 1 female DB9 console
connector)

Ethernet (10 Mbps) Switch
Management Ports

1 copper RJ-45 or fiber (ST) port for switch management
functions.

Current Draw

3.75 amps without an HRE-X
5.25 amps with an HRE-X

♦ Warning ♦
Do not install any version of the MPM (i.e, MPM-C,
MPM-1G, MPM-II, MPM-III, or original MPM) in a chassis
with an MPX or any OmniSwitch switching module.
Installing an MPM in a chassis with an MPX can cause
physical damage.

Page 2-1

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).

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).
This dual-state LED is on Green

when the switch is receiving the
proper voltage from Power Supply 1. It is on Amber when
Power Supply 1 is on, but not
supplying the correct amount of
voltage to power the switch, or is
installed and turned off. The PS1
LED is Off when the Power SupModule ply 1 is not present.
Status
PS2 (Power Supply 2 Status).
LEDs
This dual-state LED is on Green
when the Omni Switch/Router is
receiving the proper voltage from
Power Supply 2. It is on Amber
when Power Supply 2 is on, but
not supplying the correct amount
of voltage to power the switch,
or is installed and turned off. The
PS2 LED is Off when Power Supply 2 is not present.

M
TE
I
PR
C

OK1 (Hardware Status). This dualstate LED is on Green when the MPX
has passed power-on hardware diagnostics successfully. On Amber when
the hardware has failed diagnostic
tests. If the OK1 LED is alternating
Green and Amber, then file system
compaction is in progress.

P
M
O
D
EM

Caution

Module
Status
LEDs
C
O
N
SO
LE

Do not power down the Omni
Switch/Router or insert any
modules while the OK1 LED is
alternating Green and Amber.
If you do, file corruption may
result and you will not be able
to restart the switch.

L
O
C
K
N
LI T
AC

OK2 (Software Status). Blinking Green
ET
H

N
ET

Caution

Do not insert or remove any
modules while the MPX OK2
LED is blinking Amber. If you
do, file corruption may result
and you will not be able to
restart the switch.

when the MPX has successfully loaded software to the switching modules.
Blinking Amber when the MPX is in a
transitional state, such as when it first
boots up. If the OK2 LED blinks
Amber for an extended period of time
(i.e., more than a minute), then you
should reboot the switch.

TEMP (Temperature). On Yellow to warn that the internal
switch temperature is approaching maximum operating limits.
Note that this LED comes on
before the temperature limit is
reached.
PRI (Primary MPX). On Green

when this MPX is the active, or
controlling, MPX. It is also on
Green when this is the only MPX
installed in the switch.
SEC (Secondary MPX). On Green
when this MPX is the secondary
MPX in a redundant MPX configuration. As the secondary MPX,
this module is in hot standby
mode.

Omni Switch/Router Management Processor Module (MPX) Status LEDs

Page 2-2

Omni Switch/Router Management Processor Module (MPX) Features

MPX 10
K1 K2
O
O
1
PS
2

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). On Yellow
when a collision has been
detected on the port.

L
O
C
K
N
LI T
AC

ACT (Activity). On Green when
data is transmitted or received
on the Ethernet management
port.
Port
LEDs
LINK (Link Status/Disabled).
On Green continuously when a
good cable connection exists.
Off when a good connection
does not exist.

Ethernet Management Port. Copper
RJ-45 (shown here) and fiber ST
ports are available for rapid switch
file transfers and network management functions.

MPX Management Connectors

Page 2-3

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.
The modem port is a Data Terminal Equipment (DTE) connector, which is typically connected
to a modem. You can also connect directly from this port to a PC or terminal with a standard
null-modem cable available in most computer equipment stores.
♦ Note ♦
The modem port is hard-wired for DTE communication; you do not need to set any jumpers.
The console port is a Data Communication Equipment (DCE) connector, which can be directly
connected to a PC, terminal, or printer.

MPX Console Port Specifications

Pin Number

Standard Signal
Name

Not Used

From MPX

To MPX

Not Used

GND

Not Used

Shell

Shield GND

MPX Console Port

Page 2-4

Direction

MPX Serial and Ethernet Management Ports

MPX Modem Port Specifications

Pin Number

Standard Signal
Name

Direction

Not Used

To MPX

From MPX

DTR

From MPX

GND

DSR

To MPX

RTS

From MPX

CTS

To MPX

Not used

Shell

Shield GND

MPX Modem Port

Ethernet Management Port
The MPX also supports an out-of-band Ethernet port for high-speed uploads and switch
management functions. With this port, you can access the Omni Switch/Router over a
network via Telnet or FTP.
You can use the Boot prompt to configure an IP address for the Ethernet management port or
you can use the ethernetc command, which is described in Chapter 6, “Configuring Management Processor Modules.” After you have assigned an IP address to the Ethernet management port, you can use it to Telnet into the UI.
See Appendix A, “The Boot Line Prompt,” for documentation on configuring the Ethernet
management port with the boot prompt.
♦ Important Note ♦
On some revisions of the MPX, you must configure the
Ethernet management port with the boot prompt before
you can use the ethernetc command.
See the table on the following page for available Ethernet management port types.

Page 2-5

MPX Serial and Ethernet Management Ports

MPX Model

Ethernet Management Port
Type (Cable Type)

Max. Cable
Distance

MPX-T

RJ-45 (UTP)

100 meters

MPX-FL

ST (Multimode fiber)

2 kilometers

Configuring MPX Serial Ports
The serial communications parameters for the two MPX serial ports are set by default to the
following:
•
•
•
•
•

9600 bits per second (bps)
8 data bits
1 stop bit
no parity
no hardware flow control (Windows 95)

Each serial port supports serial data rates of 1200, 9600, 19200, and 38400 bps. However, you
must remove the default baud rate shunt (E1), which fixes the baud rate at 9600 bps, before
you can change the baud rate. This shunt is located near the front end of the MPX’s circuit
board, just to the right of the Ethernet management port.
To change the serial port configuration parameters, use the ser command, which is described
in detail in Chapter 6, “Configuring Management Processor Modules.”

Page 2-6

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.
The following table lists Omni Switch/Router image files that may be present in MPX flash
memory along with the module(s) or feature with which the file is used.
File Name

Modules/Function Used With

mpx.img
mpx.cmd
mpm.cfg
mpm.cnf

MPX

desx.img

Ethernet port stress test software

diagx.img

Diagnostics software

esx.img

All GSX and ESX modules

fwdx.img

IP Fastpath and Firewall software

gated.img

Advanced Routing software

ipcntrl.img

IP control software

ipms.img

IPMS software

isdn.img

WSX-BRI-SC

mrd.img

Advanced Routing software

ntp.img

Network Time Protocol (NTP) software

policy.conf

PolicyManager file comprised of a MAC address and time that uniquely
identifies the switch(es) to which the policy applies

policy.img

PolicyView software

qos.img

Quality of Service (QOS) software

rav.img

RADIUS authentication software

t1e1drv.img

WSX-FT1/E1-SC

text_cfg.img

Text-based configuration software

vrrp.img

VRRP software

vsmboot.asc

Boot file for Voice Over IP (VOIP) modules

vsx.img

Voice Over IP (VOIP) modules

web.img

HTTP browser client software

wsx.img

WSX-S-2W, WSX-SC-4W, WSX-SC-8W (Frame Relay and PPP software)

Page 2-7

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. In a switch with 8 MB of flash memory, for example, the images in flash should
never exceed 7.45 MB. (You can view how much flash memory is available through the ls
command.) This will allow enough room in flash for booting and configuration file expansions. If your flash memory exceeds this amount, then you need to delete some images from
flash.
In addition, the flash file system has a limit of 256 files, including configuration, logging, and
other files. When this 256-file limit is reached, configuration file expansions will cease and
new files will not be able to be loaded. This file limit applies even if there is enough memory
available in flash.
Not all image files in flash memory are required—only those that must be used with the
switching modules in your Omni Switch/Router. You can remove any files that are not
required for your Omni Switch/Router configuration by using the rm command. For example,
if you do not have T1/E1 ports, you could remove the t1e1drv.img file.

Page 2-8

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. If you want to configure an
Omni Switch/Router chassis in a redundant configuration, you must use two MPXs.
When you have two MPXs in one chassis, they must be installed in Slots 1 and 2, and only
one can be active. MPXs will assume one of the following roles.
• Primary - The MPX that is currently active and processing commands. It is also the MPX that
is communicating via Telnet, FTP, etc.
• Secondary - An MPX that is currently not the primary. It has sufficient software to communicate with the primary MPX. (For full redundancy, the secondary MPX should also have
the same software version as the primary and its configuration should be in sync with the
primary.) In this state, it is capable at any time of assuming the primary role.
The LEDs on each MPX reflect the same status with the exception that the primary’s PRI LED is
on whereas the secondary’s SEC LED is on. Also, the secondary MPX’s OK2 LED will not flash
amber during board transitions. See Omni Switch/Router Management Processor Module
(MPX) Status LEDs on page 2-2 for locations of the LEDs.
♦ Important Note ♦
To support redundancy, your MPX must be Revision
A14 or higher.

Change-Over Procedure
The secondary MPX continuously monitors the primary MPX. This monitoring serves two
purposes: 1) to notify the secondary MPX that the primary is alive and processing, and 2) to
update the configuration and thus keep the two MPXs in sync. If the secondary MPX detects
that the primary is no longer operational, it will begin to take over as primary. When a
secondary MPX becomes primary it resets all the other modules in the chassis and performs a
primary MPX initialization.
There are four states for an MPX configuration. You can view the current MPX state through
the slot command. These states are described in the table below. Note that for a
primary/secondary configuration to be in a “redundant” state, the relationship between the
two MPXs must meet the conditions shown in the table.

Page 2-9

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.

The primary MPX has the ability to transfer files to and from the secondary MPX. In the condition where the secondary MPX has an older version of software (Software Fallback), it is not
desirable to update the configuration file of the secondary. It is therefore the default not to
update the configuration file on the secondary if the secondary is running an earlier version
of software. You can force the update using appropriate commands in the mpm menu. (See
Chapter 6, “Configuring Management Processor Modules,” for more information on commands
in the mpm menu.)
♦ Note ♦
Do not remove a primary MPX without performing a
renounce command (described in Chapter 6, “Configuring Management Processor Modules”) first.

MPX Redundancy Commands
A set of commands exists to monitor the primary and secondary MPXs. These commands are
covered in detail in Chapter 6, “Configuring Management Processor Modules.” Note that you
can attach a terminal to both MPXs in a chassis; however, you will see a different responses
depending on which is primary and which is secondary. You should execute all UI
commands from the primary MPX except for those commands specifically addressing the
secondary MPX. For example, commands are available to control and monitor the secondary
MPX from the primary MPX (e.g., the sls command lists files on the secondary MPX from the
primary MPX).

Page 2-10

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.
Currently, Omni Switch/Router switching modules consist of Gigabit Ethernet modules, autosensing 10/100 Ethernet modules, Fast (100 Mbps) Ethernet modules, 10 Mbps Ethernet
modules, Voice Over IP (VOIP) modules, and WAN modules.
♦ Important Note ♦
Omni Switch/Router modules require the use of an
Omni Switch/Router chassis (see Chapter 1, “Omni
Switch/Router Chassis and Power Supplies”). Do not
install an Omni Switch/Router module in an
OmniSwitch chassis and do not install an OmniSwitch
module in an Omni Switch/Router chassis.
Gigabit Ethernet Modules
• GSX-K-FM/FS/FH-2W

Advanced 2-port Gigabit Ethernet switching module

10/100 Ethernet Modules
• ESX-K-100C-32W

Advanced 32-port auto-sensing 10/100 Ethernet switching
module

Fast (100 Mbps) Ethernet Modules
• ESX-K-100FM/FS-16W

Advanced 16-port Fast Ethernet (100 Mbps) switching module

WAN Modules
• WSX-S-2W

2 serial ports that support the frame relay or PPP protocol.

• WSX-SC-4W/8W

4 or 8 serial ports that support the frame relay or PPP protocol.

• WSX-FT1/E1-SC-1W/2W

1 or 2 T1/E1 ports and one or two serial ports that support the
frame relay or PPP protocol

• WSX-BRI-SC-1W/2W

1 or 2 UPS (Universal Serial Port) and 1 or 2 ISDN-BRI ports that
support Frame Relay or PPP

Voice Over IP Modules
Voice Over IP (VOIP) modules for the Omni Switch/Router are listed below and are documented in the VoIP User Manual.
• VSX-A

4, 6, 8, 14, or 16 analog RJ-11 ports supporting FXS and FXO
interfaces, including T.38 FAX

• VSX-VSD

2 or 4 digital T1 or E1 (Euro PRI and Qsig) ports, including
T.38 FAX

Page 3-1

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. See Chapter 2, “The Omni
Switch/Router MPX,” for more information on the MPX.

Page 3-2

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.img

WSX-BRI-SC-1W/2W

wsx.img, isdn.img

WSX-FT1-SC-1W/2W

wsx.img, t1e1drv.img

WSX-FE1-SC-1W/2W

wsx.img, t1e1drv.img

Page 3-3

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.) In a setup with redundant MPX modules, Slots 1 and 2 are reserved for the MPXs. Additional modules can be installed in any available slot. (OmniS/R-3 slots are numbered 1 to 3
starting from the topmost slot. OmniS/R-5 slots are numbered 1 to 5 starting from the topmost
slot. OmniS/R-9 slots are numbered 1 to 9 starting from the left.)
♦ 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 the switching module.
To insert a switching module follow these instructions:
1. Holding the module firmly in both hands, carefully slide it into the card guide. The front
panel connectors and LEDs should face outward. In a 9-slot Omni Switch/Router, the
component side of the board should face right (toward the power supply). In a 3- or 5slot Omni Switch/Router, the component side should face up.
The module should slide in easily. A large amount of force is not necessary and should
not be used. If any resistance is encountered, check to be sure that the module is aligned
properly in the card guide.

Switch Module

Slide Card In

Card Guides

Page 3-4

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.

Page 3-5

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. Loosen the screw fasteners at the top and bottom of the switching module using a standard screwdriver.
2. Gently unlock the two card ejectors by pulling them out away from the module.
3. With both hands, carefully pull the module free of the chassis enclosure.

Page 3-6

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. To use an empty slot, you must power
down your chassis.
Perform the following steps to safely hot swap a switching module. (You cannot hot swap a
primary MPX module.) Since this procedure could possibly disrupt the network, it is best to
hot swap during network down times.
1. At the system prompt, enter
swap on

where minutes is the number of minutes you want the switch to be in swap mode (the
default is 5 minutes). A message similar to the following will be displayed.
Swap is ON for 5 minutes

The swap mode must be enabled (ON) to insert a switching module. If not, the system
may halt or restart. (See Chapter 6, “Configuring Management Processor Modules,” for
more information on the swap command.)
♦ Caution ♦
Modules can only be reset and hot-swapped when the
MPX’s OK2 light is in its normal flashing green state.
2. Enter reset, followed by the slot number of the switching module you want to hot swap,
then followed by the word disable. (See Chapter 36, “Running Hardware Diagnostics,” for
more information on the reset command.) For example, if you want to hot swap the
switching module in slot 4, you would enter
reset 4 disable

at the system prompt. Next, the switch will prompt you to confirm the reset. The following is an example of the display for an ESX module. The display for other types of switching modules will be similar.
Resetting slot of type F-Ether/M may crash system
Attempt reset anyway {Y/N}? (N) :

Press y and then press . If the switching module is in slot 4, a message similar to
the following will be displayed.
resetting slot 4 to disable

3. The MPX’s OK2 LED will flash amber 1 or 2 times, then return to normal flashing green.
The switching module’s OK1 LED will turn amber and the OK2 LED will not be illuminated. Remove all cables attached to ports on the switching module that you are going to
swap out.

Page 3-7

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.)
♦ Warning ♦
Removing or inserting the switching module while the
MPX’s OK2 LED is flashing amber can cause the system
to reset.
5. Carefully insert the new switching module into the chassis. (See Installing a Switching
Module on page 3-4 for instructions on inserting a switching module.)
♦ Caution ♦
When re-installing a module during a hot swap, it must
make a proper connection to the switch backplane.
The connection is made when you close the card ejectors. Always close the card ejectors firmly and briskly,
without hesitation. Closing them too slowly can cause
the switch to halt or restart.
The MPX’s OK2 LED will flash amber 1 or 2 times, then return to normal flashing green. If,
after hot-swapping modules, the MPX’s OK2 LED continues to flash amber for more than
about 8 seconds, it means that the switch needs to be reset.
The swap time will again reset to its original value.
6. Re-insert the cables that were removed in step 3 into the new switching module.
7. Enter reset followed by the slot number for the new switching module. For example, if
the new switching module is in slot 4, you would enter
reset 4

Press y and then press . If the switching module is in slot 4, a message similar to
the following will be displayed.
resetting slot 4 to enable

8. The MPX’s OK2 LED will flash amber 1 or 2 times, then return to normal flashing green.
The switching module’s OK1 LED will turn from amber to solid green and the OK2 LED
will be blinking green. If the OK1 LED on the switching module is amber, then the hardware has failed diagnostics or the corresponding image file for the module is not in flash
memory. If the OK2 LED on the switching module is solid amber, then the module failed
to download software from the MPX.

Page 3-8

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). These diagnostics are designed to be as extensive as possible without
causing disruption to external networks or requiring special test connections. While the diagnostics are running, the MPX OK2 LED will be flashing green. LEDs on the switching module
can provide information on the success or failure of these tests. Also refer to Chapter 35,
“Troubleshooting,” for information on error conditions reflected in the LED displays.
More extensive diagnostic tests are available for off-line testing of switching modules. See
Chapter 36, “Running Hardware Diagnostics,” for further information.

Page 3-9

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). Endface geometries must be exceptionally precise and aligned to extremely tight
tolerances. The better the endface geometry, the lower the loss and more consistent the
connection. Poor connector interfaces will reflect light back into the laser, causing an
increase in laser noise.
• They mate well with other connector interfaces. Chances are the manufacturer of the
jumper cable will not be the same as the manufacturer of the transceiver connector interface. Premium jumper cables mechanically align themselves well into most transceiver
interfaces. This provides both better performance as well as better repeatability. You will
always see a variance in transceiver power due to connector alignment, often as much as
0.3 to 0.7 dB. Good jumper cables help reduce this variance.
• They continue to mate well after many insertions and removals. Premium grade jumper
use premium connectors that maintain their mechanical integrity up to and beyond 2000
insertion cycles.
For better repeatability, always use duplex (two connectors fused together and terminated to
two cables) SC connectors on your jumper cables when connecting to a fiber-optic transceiver. Two simplex connectors inserted into a transceiver interface will often have up to 3
dB greater variation in repeatability compared to duplex connectors.
Never bend the fiber optic cable beyond its recommended minimum bend radius (1.2 inches
minimum). This introduces bend losses and reflections that will degrade the performance of
your system. It can also damage the fiber, although fiber is much tougher than most would
assume. Still, it is highly recommended to buy only jumper cables with 3mm Kevlar jacketing, which offer superior protection and longer life.

Step 2. Keep Your Fiber Optic Connectors Clean
Unlike electrical connectors, fiber-optic connectors need to be extremely clean to ensure
good system performance. Microscopic particles on the connector endface (where the light
exits the connector) can degrade the performance of your system, often to the point of failure. If you have low-power output from a fiber-optic transceiver or a fault signal from your
equipment, cleaning your fiber-optic connectors should always be done before trouble shooting.
Follow the steps below to clean your fiber optic connector:
1. Hold the connector cleaner tool in the palm of your left hand and, with the silver shutter
upwards, rotate the cloth-forwarding lever (located on the right side of the tool) with your
thumb away from your body. As the lever winds the cleaning cloth inside the case, it
simultaneously opens the silver shutter located at the top of the unit.

Page 3-10

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. When cables are not
being used, always put the plastic or rubber endcaps back on the connector to ensure cleanliness.

Step 3. Keep the Transceiver Interface Clean
If you have cleaned your connectors, but still experience low-power output from a fiber-optic
transceiver or a fault signal from your equipment, you should clean the transceiver interface
by blowing inert dusting gas inside the transceiver interface. This removes dust and other
small particles that may block the optical path between the optics of the transceiver and the
connector’s endface.

Step 4. Attenuate Properly
Often equipment using laser-based transceivers need to have the optical path attenuated
when performing loop-back testing or testing between two pieces of equipment. Too much
optical power launched into the receiver will cause saturation and result in system failure. If
you are using single mode fiber and you do not know the power output of the laser, it is
always best to use a 10 dB attenuator when testing. Using the wrong type of attenuator will
introduce problems, most notably reflection of light back into the laser, often resulting in
excess noise and causing system failure.
Inline attenuators eliminate the need for additional jumper cables and thus reduce the number
of connection interfaces. This increases the integrity of the optical path resulting in a more
accurate test.

Page 3-11

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. This will
prevent packets from being dropped.

GSX-K-FM/FS/FH-2W
The GSX-K-FM/FS/FH-2W Gigabit Ethernet backbone switching module contains two fiber SC
connectors that support two fully switched 1000Base-LX (long-distance fiber transmissions) or
1000Base-SX (short-distance fiber transmission ports). The GSX-K-FM/FS/FH-2W can be used as
a backbone connection in networks where Gigabit Ethernet is used as the backbone media.
The GSX-K-FM/FS/FH-2W can be factory configured with intermediate-reach single mode or
multimode fiber ports (see GSX-K-FM/FS/FH-2W Technical Specifications on page 3-13 for
more information). The intermediate-reach single mode version is referred to as the GSX-K-FS2W; the long-reach single mode version is referred to as the GSX-K-FH-2W; and the multimode
version is referred to as the GSX-K-FM-2W.
The ports are color coded to differentiate the mode: multimode connectors are black, longhaul single mode connectors are yellow, and intermediate-reach single mode connectors are
blue. (See Handling Fiber and Fiber Optic Connectors on page 3-10 for proper handling of SC
connectors and fiber-optic cable.)
The GSX-K-FM/FS/FH-2W takes advantage of new Gigabit Ethernet/Fast Ethernet ASIC technology known as “Kodiak.” This module provides 4 priority levels and 256 queues per Kodiak
ASIC.
♦ Note ♦
Kodiak-based modules support up to 4 levels of priority (0-1, 2-3, 4-5, 6-7). This is not compatible with the
implementation of VLAN priority of Mammoth-based
modules. Kodiak based priority VLANs can only be
used with other Kodiak based priority VLANs.
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-12

Gigabit Ethernet Modules

GSX-K-FM/FS/FH-2W Technical Specifications
Number of ports

Connector Type

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.5 to -3 dBm (Intermediate-reach single mode)
0 to +5 dBm (Long-reach single mode)

Input Optical Power

-17 to 0 dBm (Multimode)
-20 to -3 dBm (Intermediate-reach single mode)
-24 to -3 dBm (Long-reach single mode)

Cable Distance

Multimode fiber: ≈ 220 m
Intermediate-reach single mode fiber: ≈ 10 km
Long-reach single mode fiber: ≈ 70 km

Current Draw

5.25 amps without an HRE-X
6.75 amps with an HRE-X

♦ Special Note ♦
The single mode version of this module has been
deemed:
CLASS 1 LASER PRODUCT
LASER KLASSE 1
LUOKAN 1 LASERLAITE
APPAREIL A LASER DE CLASSE 1

to IEC 825:1984/CENELEC HD 482 S1.

Page 3-13

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.

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

This Gigabit Ethernet module
includes one row of LEDs for each
port. The LEDs for a given port dis- Port
play in the row labeled with the LEDs
port number. Definitions for the
LEDs are given below.

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.
OK2 (Software Status). Blinking

RX (Receive). On Green when
TX

the corresponding port is
receiving data.
1

TX (Transmit). On Green when

the corresponding port is transmitting data.
LINK (Link Status/Disabled).

2
R
X

On Green when the corresponding port has a valid physical link and a signal is present.
Under normal conditions, this
LED should always be on when
a cable is connected.

Green when the module software was downloaded successfully and the module is
communicating with the MPX .
Blinking Red when the module is
in a transitional state. On solid
Red if the module failed to
download software from the
MPX.

SC connectors will be color
coded to indicate multimode
(Black) or intermediate-reach
single mode (Blue).

2-Port Advanced Gigabit Ethernet Switching Module

Page 3-14

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.

Ethernet RJ-45 Pinouts
The figure and table below illustrate the pinouts used on RJ-45 ports in Omni Switch/Router
10/100 Ethernet modules.

Ethernet RJ-45 Specifications

Pin Number

Standard Signal Name

RD +

RD –

TD +

Not Used

TD –

Not Used

ESX-K-100C-32W
The ESX-K-100C-32W Omni Switch/Router 10/100 Ethernet switching module contains 32 ports
that each support a fully switched 10 or 100 Mbps connection in full- or half-duplex mode.
This module offers high density 10/100 connectivity for desktop connections. Each port can
auto-sense the connection speed and automatically switch at that speed. You configure
whether you want to use the auto-sensing functionality through the 10/100cfg command.
By default, each port is configured to operate in half-duplex, auto-sensing mode. You can
configure full-duplex mode on each port through 10/100cfg. Auto-sensing may be disabled to
allow you to manually configure ports through the 10/100cfg command. An additional software command, 10/100vc, allows you to view the current line speed and link mode of each
port connection. The 10/100cfg and 10/100vc commands are described in Chapter 15, “Managing Ethernet Modules.”

Page 3-15

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.
Module ports are divided into four (4) banks of eight (8) ports. Ports are numbered from 1 to
8 within each of the four banks. The four banks are labelled A, B, C, and D. This grouping
simplifies the display of LEDs, which are organized as a matrix (see 32-Port Advanced AutoSensing 10/100 Ethernet Switching Module on page 3-18). Software commands will number
these ports 1 through 32, with Port A1 as 1, Port B1 as 9, C1 as 17, D1 as 25, etc.
The ESX-K-100C-32W takes advantage of new Gigabit Ethernet/Fast Ethernet ASIC technology
known as “Kodiak.” This module provides 4 priority levels and 256 queues per Kodiak ASIC.
♦ Note ♦
Kodiak-based modules support up to 4 levels of priority (0-1, 2-3, 4-5, 6-7). This is not compatible with the
implementation of VLAN priority of Mammoth-based
modules. Kodiak based priority VLANs can only be
used with other Kodiak based priority VLANs.
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-16

Auto-Sensing 10/100 Ethernet Modules

ESX-K-100C-32W Technical Specifications
Number of ports

Connector Type

RJ-45

Standards Supported

IEEE 802.3; IAB RFCs 826, 894

Data Rate

10 or 100 Mbps (full or half duplex)

Maximum Frame Size

1,518 bytes

MAC Addresses Supported

ESX-K-100C-32W: 1,024
ESX-K-100C-32W4: 4,096

Connections Supported

10BaseT hub or device
100BaseTx hub or device

Cable Supported

10BaseT
Unshielded twisted-pair (UTP)
100BaseTx
Unshielded twisted-pair:
Category 5, EIA/TIA 568
Shielded twisted-pair
Category 5, 100 ohm

Maximum Cable Distance

100 m

Current Draw

10.25 amps without an HRE-X
11.75 amps with an HRE-X

Page 3-17

Auto-Sensing 10/100 Ethernet Modules

ESX-K 10/100

OK1
A

7 1
3

8 2

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.

3x A 5x

3x B 5x

3x C 5x

3x D 5x

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.

OK2 (Software Status). Blinking

OK2

OK1 (Hardware Status). On Green
when the module has passed diagnostic tests successfully. On Amber
when the hardware has failed diagnostics or if the corresponding Module
image file for the module is not in LEDs
flash memory.

6x
B
6x
C
6x
D
6x

32-Port Advanced Auto-Sensing 10/100 Ethernet Switching Module

Page 3-18

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.

ESX-K-100FM/FS-16W
The ESX-K-100FM/FS-16W Omni Switch/Router Fast Ethernet switching module has sixteen (16)
fiber MT-RJ ports that each support a fully-switched 100 Mbps connection in full-duplex mode.
This module provides high-speed backbone connectivity. It also supports backbone features
such as 802.1q and OmniChannel. Each port uses the full 100 Mbps of bandwidth in each
direction (see ESX-K-100FM/FS-16W Technical Specifications on page 3-20). The single mode
version is referred to as the ESX-K-100FS-16W; the multimode version is referred to as the ESXK-100FM-16W. Multimode and single mode connectors are differentiated by color: multimode
connectors are black and single mode connectors are blue.
♦ Note ♦
If your network currently uses SC connectors, you can
order MT-RJ-to-SC cables from Alcatel.
The MT-RJ fiber port supports full-duplex operation. You can configure half-duplex mode on
each port through 10/100cfg. An additional software command, 10/100vc, allows you to view
the current line speed and link mode of each port connection. The 10/100cfg and 10/100vc
commands are described in Chapter 15, “Managing Ethernet Modules.”
The ESX-K-100FM/FS-16W is best used as a backbone connection in networks where Fast Ethernet is used as the backbone media. Each 100Base-Fx port may also connect to a single hightraffic device, such as a mail or file server.
The ESX-K-100FM/FS-16W takes advantage of new Gigabit Ethernet/Fast Ethernet ASIC technology known as “Kodiak.” This module has provides 4 priority levels and 256 queues per
Kodiak ASIC.
♦ Note ♦
Kodiak-based modules support up to 4 levels of priority (0-1, 2-3, 4-5, 6-7). This is not compatible with the
implementation of VLAN priority of Mammoth-based
modules. Kodiak based priority VLANs can only be
used with other Kodiak based priority VLANs.
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-19

Fast (100 Mbps) Ethernet Modules

ESX-K-100FM/FS-16W Technical Specifications

Page 3-20

Number of ports

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.5/125 micron multimode fiber
Single mode: single mode fiber

Optical output power

Multimode: -19 to -14 dBm
Single-mode: -20 to -14 dBm

Optical receiver sensitivity

Multimode: -31 dBm Max.
Single-mode: -31 dBm Max.

Cable Distance

Multimode: approximately 2 km
Single-mode: approximately 15 km

Current Draw

9.75 amps without an HRE-X
11.25 amps with an HRE-X

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

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

Each LED corresponds to a port on
the module. When an LED is on Port
Green continuously, a good cable
connection exists. The LED will LEDs
blink Green when traffic is transmitted or received on the port.

the ESX-100FM/FS-16W type. It will
read either ESX-K 100 mm (multimode
cable) or ESX-K 100 sm (single mode
cable).

OK2 (Software Status). Blinking

1
2
3
4

5
6
7
8
9

MT-RJ connectors will be color
coded to indicate multimode
(Black) or single mode (Blue).

10
11
12
13
14
15
16

16-Port Advanced Fast Ethernet Switching Module

Page 3-21

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.

• WSX-BRI-SC

Provides one or two Universal Serial Ports (USPs) ports and one or two
ISDN-BRI ports that support Frame Relay or PPP with data compression.

All of these modules are described and illustrated in the sections beginning on page 3-27.
A WSX switching module is actually a submodule, or daughtercard, that attaches to an Omni
Switch/Router High-Speed Module (HSX). The HSX contains RISC processors, RAM for holding
software image files, ASICs for performing switching, and Content Addressable Memory (CAM)
for storing MAC addresses. You plug your cable into the WSX submodule, but it is the HSX
module that connects to the switch’s backplane.

WAN Pinouts
The figures and tables on the following pages illustrate the pinouts used on Omni
Switch/Router WAN modules. Please note that the signal commonly knows as “remote loopback” (LL) is not supported on the WAN serial port (see WAN Serial Port Specifications on
page 3-25). In addition, CTP2, CTP1, and CTP0 are assigned to CS(B), DR(B), and CD(B),
respectively, on the serial port. The later are not used in the cable configurations that require
the former.
See Appendix B, “Custom Cables,” for information on cables used to connect the serial
connector to different interface types.

Page 3-22

WAN Modules

WAN BRI Port Specifications
(S/T Interface)

Pin Number

Standard Signal Name

Not Used

Rcv + from TE

Rcv - from TE

Xmt + from TE

Xmt - from TE

Not Used

WAN BRI Port Specifications
(U Interface)

Pin Number

Standard Signal Name

Not Used

Xmt to /Rcv from Network

Not Used

Page 3-23

WAN Modules

WAN T1/E1 Port Specifications

Pin Number

Standard Signal Name

Rx_Ring

Rx_Tip

Chassis GND

Tx_Ring

Tx_Tip

Chassis GND

Chassis GND
(A jumper is provided for
connecting Pins 7 and 8 to the
chassis ground, if required.)

WAN Serial Port Numbering

Page 3-24

WAN Modules

WAN Serial Port Specifications
Alcatel SPI

EIA-530

RS-449

Generic
Signal Name

Source

Mnemonic Pin

Shield

Signal Ground

Transmitted
Data

DTE

TD(A)

BA(A)

SD(A)

TD(B)

BA(B)

SD(B)

Received Data

DCE

RD(A)

BB(A)

RD(A)

RD(B)

BB(B)

RD(B)

TC(A)

DB(A)

ST(A)

TC(B)

DB(B)

ST(B)

TC(A)

DD(A)

RT(A)

TC(B)

DD(B)

RT(B)

XC(A)

DA(A)

TT(A)

XC(B)

DA(B)

TT(B)

RS(A)

CA(A)

RS(A)

RS(B)

CA(B)

RS(B)

CS(A)

CB(A)

CS(A)

CS(B)

CB(B)

CS(B)

DR(A)

CC(A)

DM(A)

DR(B)

CC(B)

DM(B)

TR(A)

CD(A)

TR(A)

TR(B)

CD(B)

TR(B)

CD(A)

CF(A)

RR(A)

CD(B)

CF(B)

RR(B)

Local Loopback DTE

Remote
Loopback

DTE

Ring Indicator

DCE

RI/TM

Test Mode

DCE

RI/TM

Cable Type 4

CTP4

n/c

Cable Type 3

CTP3

n/c

Cable Type 2

CTP2

Cable Type 1

CTP1

Cable Type 0

CTP0

Transmit Clock DCE
Receive Clock

DCE

Ext. Transmit
Clock

DTE

Request To
Send

DTE

Clear To Send

DCE

Data Set Ready DCE
Data Terminal
Ready

DTE

Data Carrier
Detect

DCE

continued on next page...

Page 3-25

WAN Modules

WAN Serial Port Specifications (cont.)
X.21/X.26

RS232

Generic
Signal Name

Source

Mnemonic Pin

Shield

Signal Ground

102

Transmitted
Data

DTE

T(A)

103(A)

T(B)

103(B)

Received Data

DCE

R(A)

104(A)

R(B)

104(B)

114(A)

114(B)

AA
DD

Transmit Clock DCE
Receive Clock

Page 3-26

V.35

DCE

S(A)

115(A)

S(B)

115(B)

B(A)

113(A)

B(B)

113

C(A)

105

C(B)

Ext. Transmit
Clock

DTE

Request To
Send

DTE

Clear To Send

DCE

106

Data Set Ready DCE

107

Data Terminal
Ready

DTE

108

Data Carrier
Detect

DCE

I(A)

109

I(B)

Local Loopback DTE

141

Remote
Loopback

DTE

140

Ring Indicator

DCE

125

Test Mode

DCE

142

Cable Type 4

n/c

Cable Type 3

n/c

Cable Type 2

Cable Type 1

Cable Type 0

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). A WSX-S-2W port is normally considered a physical DTE device. It
can be turned into a physical DCE device—for speed or clocking purposes— by plugging in a
DCE cable. The WSX-S-2W senses whether a DCE or DTE cable is connected.
Software in the switch allows you to configure parameters for the Frame Relay or Point-toPoint Protocol (PPP). Software commands allow you to view the status of the WAN connection at the WSX-S-2W board, port, or virtual circuit level. Extensive statistics are provided at
each level. Software commands for Frame Relay are described in Chapter 29, “Managing
Frame Relay”; commands for PPP are described in Chapter 30, “Point to Point Protocol.”
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

WSX-S-2W Technical Specifications
Number of ports

Connector Type

High-density 26-pin shielded serial

Protocols Supported

Frame Relay and Point-to-Point (PPP)

Data Rates Supported

9.6, 19.2, 56, 64, 128, 256, 512,
768, 1024, 1536, 2048 Kbps

Clocking

Internal, External, or Split

Virtual Circuits Supported

Permanent Virtual Circuits (PVCs)

MAC Addresses Supported

4,096

Connections Supported

Physical Data Terminal Equipment (DTE) or
Data Communication Equipment (DCE)

Cable Supported

DTE or DCE in the following types:
R2-232, V.35, X.21, RS-530, RS-449

Power Consumption

5.25 amps (without an HRE-X)
6.75 amps (with an HRE-X)

Page 3-27

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.

TX (Transmit). On “half-

tinuously when the port connection is operational. Off
when the port is disabled or
the cable is detached. Blink- Port
ing On/Off if cable is attached LEDs
but receive control data is
detected as down.
This LED also blinks during
initialization, diagnostics, or
when invalid data is being
exchanged on the port.

STA (Status). On Green con-

OK1 (Hardware Status). On
Green when the module has
Module passed diagnostic tests successfully. On Amber when the
LEDs
hardware has failed diagnostics or if the corresponding
image file for the module is not
in flash memory.

bright” Green when idle and
Green with occasional flickers
when the port is transmitting
data.
2

RX (Receive). On “half-bright”

Green when idle and Green
with occasional flickers when
the corresponding port is
receiving data.

2-Port WAN Frame Relay Switching Module

Page 3-28

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.21,
RS-530, and RS-449). A WSX-SC port is normally considered a physical DTE device. It can be
turned into a physical DCE device—for speed or clocking purposes— by plugging in a DCE
cable. The WSX-SC board senses whether a DCE or DTE cable is connected.
Software in the switch allows you to configure parameters for the Frame Relay or Point-toPoint Protocol (PPP). Software commands allow you to view the status of the WAN connection at the WSX-SC board, port, or virtual circuit level. Extensive statistics are provided at each
level. Software commands for Frame Relay are described in Chapter 29, “Managing Frame
Relay”; commands for PPP are described in Chapter 30, “Point to Point Protocol.”
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-29

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.2, 56, 64, 128, 256, 512,
768, 1024, 1536, 2048 Kbps

Compression

Hardware-based using STAC 9705

Clocking

Internal, External, or Split

Virtual Circuits Supported

Permanent Virtual Circuits (PVCs)

MAC Addresses Supported

4,096

Connections Supported

Physical Data Terminal Equipment (DTE) or
Data Communication Equipment (DCE)

Cable Supported

DTE or DCE in the following types:
R2-232, V.35, X.21, RS-530, RS-449

Power Consumption

WSX-SC-4W without an HRE-X: 6.25 amps
WSX-SC-4W with an HRE-X: 7.75 amps
WSX-SC-8W without an HRE-X: 8.25 amps
WSX-SC-8W with an HRE-X: 9.75 amps

Page 3-30

WAN Modules

WSX

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.

Please refer to 2-Port WAN
Module Frame Relay Switching Module on page 3-28 for further
LEDs
information on these LEDs.

O
K2
TX
X
R
A

1
2
3
4

Ports 1 through 4
3

STA (Status). On Green con-

TX
X
R
A

5
6
7
8

tinuously when the port connection is operational. Off
when the port is disabled or
the cable is detached. Blinking On/Off if cable is attached
but receive control data is
detected as down.
This LED also blinks during
initialization, diagnostics, or
when invalid data is being
Port
exchanged on the port.
LEDs
TX (Transmit). On “halfbright” Green when idle and
Green with occasional flickers
when the port is transmitting
data.
RX (Receive). On “half-bright”

Ports 5 through 8
3

Green when idle and Green
with occasional flickers when
the corresponding port is
receiving data.

8-Port WAN Frame Relay Switching Module

Page 3-31

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.
This module includes an integrated CSU/DSU to enable direct connection to a T1/E1 device,
such as a PBX, or a T1/E1 line to a service provider.
You can configure physical port parameters through software commands. Configuration
options include frame format, facility datalink, and line coding. In addition, the switch can
store up to 24 hours of local and remote statistics. See Chapter 33, “Managing T1 and E1
Ports,” for more information on software-configurable parameters.
The WSX-FT1/E1-SC also supports STAC hardware compression.
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-32

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.048 Mbps
Serial: 56, 64, 128, 256, 384, 512, 768, 1024, 1536,
1544, 2048 Kbps

Compression

Hardware-based using STAC 9705

Facility Datalink Protocol

ANSI T1.403 and AT&T 54016

MAC Addresses Supported

4,096

Connections Supported

Physical Data Terminal Equipment (DTE) or
Data Communication Equipment (DCE)

Cable Supported

Serial Ports
DTE or DCE of the following types:
R2-232, V.35, X.21, RS-530, RS-449

Cable Distance

T1/E1 (short haul): 200 meters
T1/E1 (long haul): 1829 meters

Power Consumption

WSX-FT1/E1-SC-1W without an HRE-X: 5.75 amps
WSX-FT1/E1-SC-1W with an HRE-X: 7.25 amps
WSX-FT1/E1-SC-2W without an HRE-X: 7.25 amps
WSX-FT1/E1-SC-2W with an HRE-X: 8.75 amps

Page 3-33

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). On Green conM
AL
T

1
2
X

tinuously when the port connection is operational. Off
when the port is disabled or Serial
the cable is detached. Blink- Port
ing On/Off if cable is attached LEDs
but receive control data is
detected as down.
This LED also blinks during
initialization, diagnostics, or
when invalid data is being
exchanged on the port.

TX (Transmit). On “half-

bright” Green when idle and
Green with occasional flickers
when the port is transmitting
data.

Port 1: T1 or E1

Port 2: Serial

RX (Receive). On “half-bright”

Green when idle and Green
with occasional flickers when
the corresponding port is
receiving data.

ALM (Alarm). On Green when the

M
AL
T
AC
A

1
2

Port 3: T1 or E1

Port 4: Serial

T1/E1
Port
LEDs

port is enabled and a signal is
present. On Yellow when an error
has occurred on the port.
ACT (Activity). On Green when
the T1 or E1 port is transmitting or
receiving data.

STA (Status). On Green continuously when the port connection is
operational. Off when the port is
disabled or the cable is detached.

WAN 2-Port Serial and 2-Port Fractional T1/E1 Switching Module

Page 3-34

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.

Coax Twisted
Pair

JP4

JP2

Cable Termination Jumpers for WSX-FE1-SC

Page 3-35

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.
The serial port on a WSX-BRI-SC module is essentially the same as the serial ports found on
the WSX-SC module. A WSX-BRI-SC serial port can detect, and configure itself, for any of five
serial cable types (RS-232, V.35, X.21, RS-530, and RS-449). A WSX-BRI-SC serial port is normally
considered a physical DTE device, but it can be turned into a physical DCE device—for speed
or clocking purposes—by simply plugging in a DCE cable. The WSX-BRI-SC internally senses
whether a DCE or DTE cable is connected and configures itself appropriately.
The BRI port on the WSX-BRI-SC board can be configured as either a “U” or an “S/T” type of
interface (the board is shipped set to “U”). Either type of interface supports two “B” channels
operating at 56/64 Kbps and one “D” channel operating at 16 Kbps.
Software running in the switch allows you to configure the operation of the Point-to-Point
Protocol (PPP) over the serial port or the BRI port. The serial port can also support the Frame
Relay protocol. The software commands used to configure PPP are described in Chapter 30,
“Point-to-Point Protocol.” The software commands used to configure Frame Relay are
described in Chapter 29, “Managing Frame Relay.” The software commands used to configure
the WAN “links” that support PPP connections are described in Chapter 31, “WAN Links.”
Finally, the software commands used to manage the ISDN ports are described in Chapter 32,
“Managing ISDN Ports.”
With the optional HRE-X you can increase routing performance to 1.5 million packets per
second per module and up to 12 Mpps in a fully-loaded 9-slot chassis.

Page 3-36

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
Supported

Physical Data Terminal Equipment (DTE) or Data
Communication Equipment (DCE)

Serial Cables Supported

DTE or DCE in the following types:
R2-232, V.35, X.21, RS-530, RS-449

BRI Port Connections
Supported

“U” interface or “S/T” interface
(jumper-selectable; “U” is shipping default)

Maximum Cable Distance

BRI: 100 m

Switch Types Supported

National ISDN-1, AT&T 5ESS, Northern Telecom
DMS100, ETSI Euro-ISDN Net3

ISDN Standards Supported

Q.921, Q.931, I.430, T1.601

Power Consumption

WSX-BRI-SC-1W without an HRE-X: 4.75 amps
WSX-BRI-SC-1W with an HRE-X: 6.25 amps
WSX-BRI-SC-2W without an HRE-X: 5.25 amps
WSX-BRI-SC-2W with an HRE-X: 6.75 amps

Page 3-37

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.

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. If
the HSX module contains two WSXBRI daughter cards, the second set
of ports (one Serial and one BRI)
are numbered as Ports 3 and 4
respectively, and include their own
separate set of LEDs that function
exactly like those related to Ports 1
and 2.

2
U

IF
T

STA (Status). On Green con-

Port 1: Serial Port

Port 2: BRI Port (“U” or “S/T”)

TX (Transmit). On “half-

bright” Green when idle and
Green with occasional flickers
when the port is transmitting
data.
RX (Receive). On “half-bright”
A

1
2
IF
U
T
AC
A
ST

Green when idle and Green
with occasional flickers when Port
the corresponding port is LEDs
receiving data.
ACT (Activity). On Green

when the ISDN-BRI port is
sending or receiving data.
1
2

UIF (“U” Interface). On Green
when the ISDN-BRI port is
configured as a “U” type of
interface. Off when the port is
configured as an “S/T” type of
interface.

Port 3: Serial Port

Port 4: BRI Port (“U” or “S/T”)

STA (Port 2/4 Status). On

Green continuously when the
port connection is operational. Off when the BRI port is
disabled or the cable is
detached. This LED blinks
during initialization.

WAN 2-Port Serial and 2-Port BRI-ISDN Switching Module

Page 3-38

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.

U S

J13

Part Number and
Serial Number label
J16

J15

J14

The gray boxes are the jumper blocks

S U

RT
TT

S U

BRI Port
U S

The small labels next to the
jumper pins at J13, J14, and
J16 indicate which pins must
be bridged to set the BRI port
to either the “U” or the “S/T”
interface.

J13

Part Number and
Serial Number label
J16

Small labels under the pins at
J15 indicate which pins must
be bridged to set Transmit
Termination (tt) and Receive
Termination (rt) to the “on” or
“off” position (the two sets of
letters with a line over them
indicate the “off” settings).

S U

J15

S U

J14

S U

TT
TT

S U

BRI Port

Jumper Configuration for the “S/T” Interface
(transmit/receive termination are set to “on”)

Page 3-39

WAN Modules

Page 3-40

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. This connection
can be made directly to the serial port, through a modem, or over a network via Telnet. You
can have up to four simultaneous connections to an Omni Switch/Router. (Please see Multiple User Sessions on page 4-33 for further details.) For Telnet access, you must first set up an
IP address for the switch. See the Getting Started Guide that came with your switch for information on setting up an IP address and logging in.

Overview of Command Interfaces
The Alcatel Omni Switch/Router has two different command interfaces available for configuring parameters and viewing statistics. They are the User Interface (UI) and the Command Line
Interface (CLI). Prior to software Release 4.4, the switch automatically booted up in the UI
mode. In Release 4.4 and later, the Omni Switch/Router is factory-configured to boot up in
the CLI mode.
♦ Terminology Notes♦
Command interface generically refers to any mechanism resident in the software that allows a user to
change switch configurations or to display statistics.
The UI is the original command interface used exclusively on all Alcatel Omni Switch/Router and OmniAccess products. The UI has its commands grouped
into functional menus. Prior to software Release 4.1, the
UI was the only command interface supported on the
Omni Switch/Router products.
The CLI is Alcatel’s text-based configuration interface
that allows you to configure Omni Switch/Router and
OmniAccess products using single-line text commands.
The CLI was implemented in software Release 4.1 and
higher. In release 4.4 and later it is the default interface.

Page 4-1

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.
Omni Switch/Router is a trademark of Alcatel Internetworking, Incorporated,
registered in the United States Patent and Trademark Office.
Press ENTER to start
->

After you press , the CLI starts automatically and the following text displays.
Entering command line interface.
->

At this point, you are in the CLI mode and may configure the switch or display statistics using
the commands described in the Text-Based Configuration CLI Reference Guide. If you want to
use the UI command interface, type ui and press . This causes the switch to leave the
CLI mode and enter the UI mode, provided you are using a login with Read/Write privileges.
You can verify that you are in the UI mode by typing ? to display the top-level menu for the
UI as shown below.
/ %?
Command
--------------File
Summary
VLAN
Networking
Interface
Security
System
Services
Switch
Help
Diag
Quit/Logout
?

Main Menu
-------------------------------------------------------------------------------------------Manage system files
Display summary info for VLANs, bridge, interfaces, etc.
VLAN management
Configure/view network parameters such as routing, etc.
View or configure the physical interface parameters
Configure system security parameters
View/set system-specific parameters1
View/set service parameters
Enter Any to Any Switching menu
Help on specific commands
Display diagnostic level commands
Log out of this session
Display the current menu contents

To change from the UI mode back to the CLI mode, type cli and press .
♦ Note ♦
Note the default command prompt for the UI is / %. The
default command prompt for the CLI is ->. You can
change the UI system prompt by using the uic
command.

Page 4-2

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, . . .
->

Page 4-3

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.
This section presents the key UI commands that are explained in this User’s Manual along
with their CLI equivalents. Where the CLI commands support partition management, these
tables also list the partition management family to which the commands belong.

Hardware Commands
The hardware section of this manual set consists of Chapters 1 through 3. There are relatively
few UI commands in this section because these chapters cover the hardware elements of the
switch. The commands defined in these chapters are listed in the Hardware Table beginning
on page 4-4.

Hardware Table
Chapter

UI Command

Equivalent CLI Commands

PM Family

1, “OSR
Chassis/Power
Supplies”

No UI commands are defined in
this chapter.

N/A

2, “MPX”

ethernetc

ethernet management port
view ethernet manage port

GF-interface

3, “OSR
Switching
Modules

10/100cfg
10/100vc

ethernet
view interface fastethernet

GF-interface

Basic Switch Management Commands
The table beginning on page 4-5 summarizes the features supported in the UI and the CLI for
Chapters 4 through 11.

Page 4-4

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

GF-Ftp
GF-File

6,
“Configuring
Management
Processor
Modules”

configsync
ethernetc
imgsync
mpm
mpmget
mpmload
mpmreplace
mpmrm
mpmstore
renounce
secreset
slipc
sls
swap
syncctl
takeover

configuration copy
ethernet management port
image copy
view mpm command
load primary mpm file
load secondary mpm file
replace secondary mpm file
remove secondary mpm file
store secondary mpm file
takeover
reload secondary mpm
slip
view secondary mpm file
swap
configuration auto-copy
takeover

GF-File

7,
“Managing
Files”

cd
cp
load
newfs
ftp
ls
pwd
rm
imgcl

cd
copy
load
newfs
ftp
ls
password
rm
imgcl

GF-CD
GF-System
GF-System
GF-System
GF-FTP
GF-LS
18-User
GF-RM
GF-System

8, “Switch
Security”

pw
reboot
useradd
userdel
usermod
userview
asacfg
secdefine

password
reboot now
user
no user
user
view user
ldap server
secure access filter
secure access no filter
view secure access filter
security
security custom
security no custom

18-User
GF-Reboot
18-User
18-User
18-User
18-User
1-Configuration
GF-System
GF-System
GF-System
GF-System
GF-System
GF-System

Unsupported

No PM Support

secapply

layer2auth, privs, secapply,
secdefine, seclog, security

continued on next page...

Page 4-5

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
secapply

secure access filter
secure access no filter
view secure access filter
security
security custom
security no custom

caplog, cmdlog, syslog,
conlog, debuglog, swlogc

Unsupported

hdcfg
health
hmstat
hpstat
hreset

health threshold
view health statistics
view health statistics
view health statistics
health statistics reset

10,
“Switch
Logging”

11, “Health
Statistics”

GF-System

Network Management Commands
The table on page 4-6 summarizes the commands supported in the UI and the CLI for
Chapters 12 through 14.

Network Management Table
Chapter

UI Command

Equivalent CLI Commands

PM Family

12, “Network
Time Protocol”

ntconfig, ntstats, ntadmin,
ntaccess

Unsupported

No PM Support

13,
“Configuring
SNMP”

snmpc
snmps

view snmp
set snmp

6-SNMP

14, “RMON
and DNS
Resolver”

res
probes
events
names

res
view rmon probes
view rmon events
view dns

GF-System

chngmac

Unsupported

Page 4-6

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.

Layer II Switching Table
Chapter

UI Commands

Equivalent CLI Commands

PM Family

15,
“Managing
Ethernet
Modules”

addprtcnl
chnlinfo
crechnl
delchnl
delprtchnl
eth10/100vc
eth10/100cfg

static agg
view statis linkagg number
static linkagg number type
no static linkgg number
static agg no
view interface fastethernet
interface ethernet

GF-Interface

16, “Managing
802.1Q
Groups”

cas, das, mas, vas

All commands used to create,
delete, modify and view a
service, plus the message
command are supported.

GF-System

17,
“Configuring
Bridging
Parameters”

fddi, fsmt, fsid, fsmtc,
fsstatus, fmac, fmaddr,
fmstats, fmctrs, fport,
fportstatus, fportctrs, fportc,
macstat, slipc

Supported

5-Bridge

maccirstat, selgp, srsf,
srtbcfg, srtbclrrif, srtbrif

Unsupported

actfstps, bps, dbrmap, fc, flc,
fls, fs, fstps, fwt, macinfo,
modvp, rts, srtbrif, stc, sts,
stpc, stps, swchmac

Supported

autoencaps, ethdef, facdef,
propipx, swchmac, trdef

Unsupported

18,
“Configuring
Frame
Translations”

5-Bridge

Page 4-7

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.1q
group num interface
fddi svc, group 802.1q
atm service
group elan
group
group num no 802.1q
group no elan
group mobility
group mobility
view group
group router, vlan router
port mapping ingress
no port mapping
port mapping
view port mapping
port monitor configuration
port monitor
view port monitor
resume port monitor
group priority num
view group priority
no group
group no interface
view group auto
view group virtual errors
view group rules
view ethernet
view group virtual statistics
view group virtual (ports)
view group mobility

crgp
dats
delqgp
gmcfg
gmstat
gp
modvl
pmapcr
pmapdel
pmapmod
pmapv
pmcfg
pmon
pmstat
pmp
prty_mod
prty_disp
rmgp
rmvp
vats
ve
vi
viqgp
vs
via
vpl

21,
“InterSwitch
Protocols”

at, br, pmd, prty_mod, vlan,
vigl, viqgp

Unsupported

atvl
fwtvl
modatvl

view vlan rules
view group mac
group mac, vlanmac, vlan
user,
vlan port, vlan chcp port,
vlan dhcp mac, vlan protocol,
vlan binding ip, vlan binding
vap
port
vlan ip, vlan ipx
view vlan rules
view vlan rules
vlap

vap
viatrl
vivl
vlap

2-Group

6-Group

GF-System

continued on next page...

Page 4-8

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, vlan router ipx,
vlan mac, vlan user, vlan dhcp port
vlan dhcp nac, vlan protocol,
vlan binding ip, vlan binding mac,
vlan binding port vlan ip, vlan ipx
multicast vlan, multicast vlan port
multicast vlan mac, vlan protocol
vlan binding ip, vlan binding mac
vlan binding port, multicast vlan descr
vlan default
view group mac
view group authenticated
group mobility
group authentication,
group authentication protocol
view multicast vlan
group mac, group mac range,
group user, group port,
group dhcp port, group dhcp mac,
group dhcp range group protocol,
group binding ip, group protocol mac,
group binding port, group ip,
group ipx, vlan mac, vlan user,
vlan port, vlan dhcp port,
vlan dhcp mac, vlan protocol, vlan
binding protocol, vlan binding mac,
vlan binding port, vlan ip, vlan ipx
no vlan
view group authenticated
view group auto
view vlan rules
view multicast vlan ports
view group ports, view group vports
view group mobility

atvl, vigl, xip

Unsupported

crmcvl, modmcvl
rmmcvl
vimcrl
vimcvl

multicast vlan
no multicast vlan
view multicast vlan rules
view multicast vlan

crmcvl

defvl
fwtvl
gmcfg
gmstat
mag
mcvl
modatvl

24,
“AutoTracker
VLAN
Examples”

GF-System

Page 4-9

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.

3-IP Routing
GF-System

26,
”UDP
Forwarding”

aisr
events
icmps
ipfilter
ipmac
ipr
ips
names
ping
probes
ripflush
rips
risr
snmpc

iproute
view rmon events
view icmp
rip filter
view mac
view ip route
view ip traffic
ip [no] domain-lookup
ping
view rmon probes
ripflush
rips
no ip route
snmp config, snmp community, snmp trap, broadcast,
snmp trap unicast
snmp station
view snmp
telnet ip-address
view tcp users
view tcp
trace
view udp users
view ucp
arp, clear arp-cache, view arp

3-IP Routing

snmps
telnet
tcpc
tcps
traceroute
udpl
udps
xlat

27,
“IPX Routing”

Page 4-10

chngmac, flush, flconfig,
ipclass, ipdirbrcast, names,
probes

Unsupported

relayc
relays

ip helper
view ip helper stats

avlbootmode, edit

Unsupported

No PM Support

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.

WAN Access Table
Chapter

UI Command

Equivalent CLI Commands

PM Family

28, “WAN
Switching
Modules”

wpadd
wpdelete

aaa

10-WAN

29,
“Managing
Frame Relay”

fradd, frmodify

dlci
description
status
cir bc be
bridge-group
bridgepmode
bridge check fcs strip
routing-group
trunking-group
payload-compress FRF9 stac
interface
clock source
clock rate
lmi-type
intf-type
lmi-t391 dte
lmi-n391 dte
lmi-n392 dte
lmi-n393 dte
lmi-n392 dce
lmi-n393 dce

10-WAN

ppp-global authentication
ppp-global sent-username
ppp-global compress
ppp-global bridging status
ppp-global ip config admin
status
ppp-global ipx-status
interface
encapsulation ppp
description
status
multilink
compression
bridge-group
bridging
bridge-mode
bridge-check fcs strip
routing-group
ip status
remote ip
ip-address
ipx-status
authentication
local-username
sent-username
max failure
max configure
max terminate
retry timeout value

10-WAN

frmodify

30,
“Point-to-Point
Protocol (PPP)”

pppglobal

pppadd, pppmodify

continued on next page...

Page 4-11

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, tecfg

channel-group
description
framing
cablelength
linecode
fdl
clock source
loopback
signalmode
snmp trap link-status
yellow
send code
non-facility signaling

10-WAN

tebcfg

bert pattern

UI commands only.

Unsupported

34, “Backup
Services”

Page 4-12

No PM Support

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.

Troubleshooting/Diagnostics Table
Chapter/
Appendices

UI Command

Equivalent CLI Commands

PM Family

35,
“Troubleshooting”

uic

Unsupported

No PM Support

36,
“Running
Hardware
Diagnostics”

diag

Unsupported

No PM Support

A,
“Boot Line
Prompt”

ethernetc

ethernet manager port

No PM Support

B,
“Custom
Cables”

No UI commands in this
Appendix.

No CLI commands in this
Appendix

No PM Support

Page 4-13

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.
Command
--------------File
Summary
VLAN
Networking
Interface
Security
System
Services
Switch
Help
Diag
Quit/Logout
?

♦ Note ♦
Although the commands are grouped in a sub-menu
structure, any command may be entered from any submenu. You are not restricted to the commands listed in
the current sub-menu.

Page 4-14

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. It also provides options for viewing the virtual interface and information
on the MIB. This menu is described in Chapter 9, “Switch-Wide Parameters.”
VLAN. The main menu for configuring Groups, virtual ports, and AutoTracker VLANs. This
menu also contains a sub-menu for configuring bridging parameters, such as Spanning Tree.
Groups and ports are described in Chapter 19, “Managing Groups and Ports.” VLANs are
described in Chapter 22, “Managing AutoTracker VLANs” and Chapter 23, “Multicast VLANs.”
Bridging parameters are described in Chapter 17, “Configuring Bridging Parameters.”
Networking.

Contains menu options for managing internetworking protocols, such as SNMP
and RMON (described in Chapters 13 and 14, respectively), IP (described in Chapter 25, “IP
Routing,”) and IPX (described in Chapter 27, “IPX Routing”).
Interface.

The main menu for configuring parameters and viewing statistics for switching
modules. This menu has sub-menus for managing Frame Relay and Fast Ethernet switching
modules. In addition it includes a sub-option for configuring SLIP. These sub-menus are
described in Chapters 15 through 16 and Chapter 29.
Security. This menu contains options for changing a password and rebooting the system. It is
described in Chapter 8, “Switch Security.”
System. Contains a wide array of options for configuring and viewing information on a variety of switch functions. Options include displays of switch slot contents, configuring serial
ports, and viewing CAM information. Commands used to configure User Interface display
options are described in User Interface Display Options on page 4-30. Other System menu
commands are described in Chapter 9, “Configuring Switch-Wide Parameters.” The System
menu also includes a sub-menu option that provides additional commands for configuring the
MPX module. This sub-menu is described in Chapter 6, “Configuring Management Processor
Modules.”
Services. Provides options for creating, modifying, viewing, and deleting Frame Relay
services. Frame Relay services include bridging, routing, and trunking. Frame Relay services
are described in Chapter 29, “Managing Frame Relay.”
Switch. Provides options to precisely define frame translations. A MAC-layer type (Ethernet,
Token Ring, etc.) may have more than one type of frame format, such as Ethernet or 802.3.
But, by default, each MAC-layer type defaults to certain frame format upon translation. This
menu allows you to define translations for each frame format. This menu is described in
Chapter 18, “Configuring Frame Translations.”
Help. Provides textual help on how to use the UI and on each menu or sub-menu. For the
item of interest, enter
help

Page 4-15

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. It is a textbased and menu-driven interface to which you can connect through the serial port,
through a modem, or over a network via Telnet. You can have up to four simultaneous UI
connections to an Omni Switch/Router. For Release 4.4 and later, the default for switch
monitoring and configuration is the CLI mode. If you are using a login account with
permission to use the UI command, you can enter the UI mode by entering the ui
command at the CLI system prompt.
• X-Vision: This purchasable network management software program consists of several
powerful sub-applications that help you manage and monitor your network. X-Vision
allows you to connect and configure multiple switches simultaneously. For more information, refer to X-Vision’s on-line help.
• The Command Line Interface (CLI): The CLI is a new feature included with Release 4.1 that
allows you to configure Omni Switch/Routers using single-line text-based commands that
are entered through the local console. Improved readability, easy text editing of the configuration files, and simple cloning of switch configurations are among some of the advantages of the CLI. For more information, refer to the Text-Based Configuration CLI Reference
Guide.

Entering Command Names
The UI is not case sensitive for commands, meaning that you may enter upper or lower case
as you desire. However, command line assignments, configuration input, and logins are case
sensitive.
Except for the logout and quit commands, you only need to enter as much of the command
that is unique. For example, if you want to execute the switch command you need only enter
swi. If you enter only sw, the system will respond with a choice of the following:
switch

swch

swchmac

swap

If you set the switch to the verbose mode you will see additional information on the screen
(see Setting Verbose/Terse Mode for the User Interface on page 4-22).
Non-unique command match, possible commands:
switch
Enter Any to Any Switching Menu
swch
Configure Any To Any Switching Port Translations
swchmac
View Per Mac Translation Options
swap
Change swap status of chassis
swlogc
Configure Switch Logging source/destination mapping and
priority levels

Page 4-16

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.

Scrolling
If the screen scrolls up too far to read you can stop the incoming data by pressing Ctrl-s. The
screen will stop and allow you to read the data. Press Ctrl-q to continue the data transmission.

The UI Configuration Menu
The User Interface (UI) Configuration menu consolidates the following UI commands into a
single, easy-to-use menu:
• chpr
• more
• ver
• ter
• timeout
♦ Note ♦
The switch’s prompt, more, verbose/terse, and timeout
functions remain fully supported. However, if you enter
any of the commands listed above, you will be redirected to the UI Configuration menu.
To access the UI Configuration menu, type
uic

at the system prompt and press . The following screen 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) :

Refer to the following sections for information on using the UI Configuration menu.

Page 4-17

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:.
System variable information means that the prompt will reflect the switch’s variable information, such as the current menu-path or the system name. Use $Menu-Path (case sensitive) to
have the system prompt display the current menu-path name. Use $SysName to have the
system prompt display the system name.
You can also mix variables and literals such as $Menu-Path -> or $SysName Enter command:.
♦ Note ♦
The default system prompt is ->.
To change the system prompt, 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 1=, followed by the desired prompt information, and press . For example:
1=$SysName ->

After you press , the screen will be redrawn. Note that the prompt information at line
1 of the uic submenu has been changed.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$SysName -> ’
: on
: 22 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Type save at the submenu prompt and press . The system prompt has been successfully changed.

Page 4-18

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.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: off
: 22 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Next, type 2=on at the submenu prompt and press . The screen will be redrawn. Note
that more mode is now set to on.
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) :

The switch’s default output display is 22 lines. If you want to change this value, type 21=,
followed by the maximum number of lines to be displayed, and press . For example:
21=50.

After you press , the screen will be redrawn. Note that the output display value at line
21 of the uic submenu has been changed.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: on
: 50 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Be sure to type save at the submenu prompt and press . More mode is now enabled.
Changing the More Mode Line Value
If the switch’s more mode has already been enabled and you want to change the maximum
number of lines to be displayed on your workstation, type uic at the user prompt and press
.

Page 4-19

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. Note that the output display value at line
21 of the uic submenu has been changed.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: on
: 2000 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Type save at the submenu prompt and press . The more mode line value has been
successfully changed.

Page 4-20

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.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: off
: 22 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Type save at the submenu prompt and press . More mode is now disabled.
♦ Reminder ♦
The switch’s table filtering feature cannot be used
when the more mode is disabled. For more information on UI table filtering, refer to UI Table Filtering
(Using Search and Filter Commands) on page 4-38.

Page 4-21

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. For example, if verbose mode is enabled and you enter
summary

at the user prompt, the Summary menu will be displayed automatically, as shown below:
Command
ss
sc
si

Summary Menu
Display MIB-II System group variables
OmniSwitch chassis summary
Current interface status

Main
File
Interface Security

Summary VLAN
System
Services

Networking
Help

The switch’s default verbose mode setting is off, or disabled. To enable verbose 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 3=on at the submenu prompt and press . The screen will be redrawn. Note
that verbose mode is now set to on.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: on
: 22 lines
: on
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Type save at the submenu prompt and press . You will be returned to the user
prompt. Verbose mode is now enabled.

Page 4-22

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 .
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
: on
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Next, type 3=off at the submenu prompt and press . The screen will be redrawn. Note
that verbose mode is now set to off.
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 save at the submenu prompt and press . Verbose mode is now disabled.

Page 4-23

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.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: off
: 22 lines
: off
: 5 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Next, type 4=on, followed by the desired automatic logout time, and press . For example:
4=15.

After you press , the screen will be redrawn. Note that the automatic logout time at
line 4 of the uic submenu has been changed.
UI Configuration
1) Prompt
2) More
21) Lines
3) Verbose
4) Timeout

: ‘$Menu-Path% ’
: on
: 22 lines
: off
: 15 minutes

Command {Item=Value/?/Help?Quit?Redraw?Save} (Redraw) :

Be sure to type save at the submenu prompt and press . The automatic logout time
has been successfully changed.
♦ Note ♦
The automatic logout value you enter takes effect
immediately; you do not have to reboot the switch. In
addition, the timeout parameter you enter is saved.
Later sessions using this account will have the same
automatic logout parameter until you change it.

Page 4-24

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. (Refer to Setting Verbose/Terse Mode for the User Interface on page 4-22 for more
information.) Additionally, there is a lookup facility to assist with administrative tasks. You
can look up any command name or prefix as follows:
lookup vlans

or to see all commands starting with v use:
lookup v*

To see all commands available, enter:
lookup *

Changing Passwords
The pw command is used to change passwords and is described in Chapter 8, “Switch Security.”

Page 4-25

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. If you want to re-execute the last command, enter two exclamation
points (!!). In the example above, you could re-execute the history command by entering
!!

at the system prompt.
You can also display a specific number of commands by entering history followed by a
number less than or equal to the number of commands in the history buffer. For example, if
you entered
history 5

in the example above you would see the following:
7: vivl
8: fwtvl
9: xlat
10: history
11:history 5

The UI also provides several other ways to re-execute earlier commands. For example, you
can re-execute a specific command shown in the history list by entering an exclamation point
(!) followed by the number to the left of that command shown in the history list. In the example at the beginning of this section, entering
!2

would re-execute the vlan command.
You can also re-execute a command a set number of commands back by entering an exclamation point and a minus sign (!-) followed by that set number of commands back. In the
example at the beginning of this section, entering
!-3

would re-execute the fwtvl command.

Page 4-26

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.
You can also re-execute the most recently executed command containing a string of characters by entering an exclamation point and a question mark (!?), followed by the string of
characters, and an optional question mark (?) which acts as a “wild card.” In the example at
the beginning of this section, entering
!?lan?

at the system prompt would re-execute the vlan command. Entering
!?la?

however, would re-execute the xlat command because it is the most recently executed
command containing la.
Commands in the history buffer can be modified by adding a parameter, when it is applicable. For example, if you entered
!7 3/1

in the example at the beginning of this section you would execute the command vivl 3/1.

Page 4-27

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.

Abbreviated IP Address Formats
Sample User Entry

IP Address

198

0.0.0.198

198.

198.0.0.0

198..

198.0.0.0

198...

198.0.0.0

198.206

198.0.0.206

198..206

198.0.0.206

198..206.

198.0.206.0

198...206

198.0.0.206

198.206.

198.206.0.0

198.206..

198.206.0.0

198.206.182

198.206.0.182

198..206.182

198.0.206.182

198.206..182

198.206.0.182

198.206.182.

198.206.182.0

198.206.182.158

As shown in the table above, the system performs two important steps to ensure that the IP
address is valid. First, it puts zeroes when you do not specify the number. Second, the system
will insert as many zeroes as needed to the right of a period.

Page 4-28

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.2: 64 data bytes
[0

] T

----198.0.0.2 PING Statistics---1 packets transmitted, 0 packets received, 100% packet loss

In addition, the IP subnet mask 255.255.0.0 can be abbreviated in the following ways:
• 255.255.
• 255.255..

Page 4-29

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.
Command
info
dt
ser
mpm
slot
systat
taskstat
memstat
fsck
newfs
syscfg
uic
camstat
camcfg
hrex
ver/ter
echo/noecho
chpr
logging
health
cli/exit
saveconfig
cacheconfig

System Menu
Basic info on this system
Set system date and time
View or configure the DTE or DCE port
Configure a Management Processor Module
View Slot Table information
View system stats related to system, power and environment
View task utilization stats
View memory use statistics
Perform a file system check on the flash file system
Erase all files from /flash & create a new file system
View/Configure info related to this system
UI configuration; change - prompt, timeout, more, verbose.
View CAM info and usage
Configure CAM info and usage
Enter HRE-X management command sub-menu
Enables/disables automatic display of menus on entry (obsolete,
use ‘uic’ command)
Enable/disable character echo
Change the prompt for the system (obsolete, use ‘uic’ command)
View system logs.
Set health parameters or view health statistics
Enter command line interface
Dump the cache configuration content to the mpm.cfg file.
Set the flag to use cache configuration only.

Main
File
Interface Security

Summary VLAN
System
Services

Networking
Help

For information on the info, dt, ser, slot, systat, taskstat, memstat, fsck, newfs, syscfg, camstat,
and hrex commands, refer to Chapter 9, “Switch-Wide Parameters.” The mpm
command is described in Chapter 6, “Configuring Management Processor Modules.” The ver/
ter and chpr commands are described earlier in Setting Verbose/Terse Mode for the User
Interface on page 4-22. The echo/noecho command is described in the following section. The
cli command is described earlier in Changing Between the CLI and UI Modes on page 4-2.
The logging command is described in Chapter 10, “Switch Logging.”
camcfg,

♦ Note ♦
The ver/ter, and chpr commands now appear as items
in the UI Configuration menu (displayed through the
uic command). If you enter the ver/ter and chpr
commands, a message will advise you to use the uic
command, and the UI Configuration menu will automatically display. For more information on the UI
Configuration menu, refer to The UI Configuration
Menu on page 4-17.

Page 4-30

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.
/ %history

If your terminal echoes characters locally it is a good idea to set the UI to noecho to avoid
repeated characters. To disable the echo, enter
noecho

at the system prompt. For example, if your terminal echoes characters locally, you would see
something like the following if you entered history.
/ %history

If your terminal does not echo characters locally, nothing you enter will be displayed. For
example, if you enter
history

at the system prompt, it will not be displayed on your terminal, as shown in the example
below.
/%

Setting the Login Banner
The login banner feature allows you to change the banner that displays whenever someone
logs into the UI. This feature can be used to display messages about user authorization and
security. You can display the same message for all login sessions or you can display different
messages for login sessions initiated by the console, ftp or Telnet access. The default login
message looks like this:
This product includes software developed by the University of California
Berkeley and its contributors.
Welcome to the Alcatel Omni Switch/Router ! Version 4.4
login:

Here is an example of a banner that has been changed:
This product includes software developed by the University of California
Berkeley and its contributors.

* * * LOGIN ALERT * * *
This is a secure device. Unauthorized use of this switch will result
in criminal prosecution.
login:

Page 4-31

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. This method allows you to create the file in the flash directory without
leaving the UI console session. You can also create the text file in an external editor (such as
MS Wordpad) and ftp the file to the switch’s flash directory. In either case, be sure to remember the name of your file.
To add the ui_add_do_alert() command syntax to the switch’s mpx.cmd file, use the edit
command of the UI’s file sub-menu. (For information on using the file sub-menu, refer to
Chapter 7, “Managing Files”).
To enable the new login banner, add the alert {console |telnet | ftp} syntax to the mpx.cmd file,
using the edit command of the UI’s file sub-menu. This command will cause the banner
message to display at each login until the switch is rebooted. After a reboot, the switch will
not display the banner unless the alert command is executed again.

Permanent Banner
If you want the banner message to display after the system has been rebooted, you must add
additional lines to the mpx.cmd file. The following example lists the commands you must add
to the mpx.cmd file. This example uses a banner text file with the name “banner.txt”.
cmDoDump=1
cmInit
ui_add_do_alert()
change_prompt_file(“console”, “banner.txt”)
change_prompt_file(“telnet”, “banner.txt”)

♦ Note ♦
Any commands added to the mpx.cmd file must be
added after the lines cmDoDump=1 and cmInit. If the
commands in the mpx.cmd file are not in the proper
order the switch may not boot properly.

Banners for Different Access Methods
You may use different banners for sessions accessed by console, Telnet or ftp methods. To do
this, create different text files for each banner with unique filenames. When you add the
commands to the mpx.cmd file, use the filenames to associate the banner with the session
access methods. Here is an example:
cmDoDump=1
cmInit
ui_add_do_alert()
change_prompt_file(“console”, “console_banner.txt”)
change_prompt_file(“telnet”, “telnet_banner.txt”)
change_prompt_file(“ftp”, “telnet_banner.txt”)

Page 4-32

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. The initial login name for a User
account is user. The password for each of these default login accounts is switch.
♦ Note ♦
In software release 4.3, the user login account with
read-only privileges is not included automatically.
♦ Note ♦
You can configure new and delete existing login
accounts with the useradd UI command, that is
described in Chapter 8, “Switch Security.”

Multiple User Sessions
You can have up to four simultaneous connections to an Omni Switch/Router. One connection can be made to the console port, two can be made through Telnet, and one connection
can be made to the modem port if you are connecting to an Omni Switch/Router.
♦ Note ♦
For software Releases 4.4 and later, more than one
login account with write privileges can be active at the
same time.
For software Release 4.3 and earlier, only one login account with write privileges was allowed
on the switch at the same time. In this case, the first switch user who logged on as either
admin or diag would be the only user with the write privilege. Subsequent users who logged
on as either admin or diag would not have the write privilege and would be unable to
perform any functions that change switch parameters. These users would also see a message
that informs them they do not have the write privilege when they log on. For example, a user
who logs on as admin when another user already has the write privilege will see the following message:
You are logged in as 'admin' without the WRITE privilege.
The WRITE privilege is currently in use by another user.

However, users who log on as either admin or diag without the write privilege can “kill” the
session of the user with the write privilege and gain that privilege for themselves. This is
described in Deleting Other Sessions on page 4-35.
If you try to log on when the limit of user has been reached (e.g., you attempt a Telnet
connection when there are two users currently connected through Telnet), you will see the
following message:
Sorry, reached maximum number of sessions.

Page 4-33

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.910)

PRIVILEGES
WRITE
000000008007fffd

GLOBAL
00000000007fffff

TTY

000000008007fffd

0000000000000000 /pty/telnetB

/pty/telnetA

You can also display information about just your session by typing
who am i

at the system prompt. The following is a typical example of the output.
SESSION
3

USER

READ
admin 000000008007fffd
(123.456.78.910)

PRIVILEGES
WRITE
000000008007fffd

TTY
GLOBAL
00000000007fffff

/pty/telnetA

The following sections describe the parameters shown by the who command.
SESSION. The session number of the user. A 0 indicates that the user is connected through the
console port, a 1 indicates that the user is connected through the modem port, and a 2 or 3
indicates that the user is connected through Telnet. The session number is used with the write
and kill commands described in Communicating with Other Users on page 4-35 and Deleting
Other Sessions on page 4-35, respectively.
USER.

The administrative level of the user. This will be admin, user or diag.

PRIVILEGES. The privilege level of the user. The READ, WRITE and GLOBAL privileges are indicated in hexadecimal numbers.
TTY. Type of connection. This shows whether the user is connected by Telnet, the modem
port, or the console port. If the connection is via Telnet, the IP address of the connecting
workstation is also shown.

Page 4-34

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. Here is an example of the write command:
write 0
I need the write privilege
exit

The user receiving the message would see the following:
Message from user 'admin' on session 3.
I need the write privilege
End of message.

If you enter an invalid session number, the switch will display an error message. For example, if you entered
write 1

at the system prompt and no user was connected through the modem port (session 1), the
switch would display
ERROR: Session 1 is an invalid session number.

Note
After you have received a message or after you have
written a message you must press the key to
regain the system prompt.

Deleting Other Sessions
If you are logged on as admin or diag, you can kill the session of another user. For example, if
you want the write privilege and you are logged on as diag or admin, you must end the
session of the user who currently has the write privilege with the kill command. The syntax
for the kill command is as follows:
kill [[-t ] -f]

The session_number is assigned by the switch and can be displayed with the who command,
which is described in Listing Other Users on page 4-34. If you do not use the -f option, then
the system will wait until the other user presses or finishes his current command. If
you do use this option, then the other user’s session will be terminated immediately.
The -t option can be used with the -f option to set the amount of time before the other user’s
session is terminated. See Advanced Kill Command Options on page 4-37 for descriptions of
the -f and -t options.

Page 4-35

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...............................................................................

The user losing the write privilege would see something similar to the following:
Your session will be killed by user 'admin' on session 3
as soon as you finish this command or press return.

After the user with the session being killed has finished his work, he will be logged off. If the
user who was logged off had the write privilege, you will gain the write privilege and a
message similar to the following will be displayed.
Done.
You have gained the WRITE privilege

You can use the who command to confirm that you now have the write privilege.
In addition, the session number used in the kill command must be valid. If, for example, you
entered
kill 1

and no user was connected to the modem port (session 1), the system would display the
following:
ERROR: Session 1 is an invalid session number.

Also, you cannot use the kill command to end your own session. For example, if your session
number is 3 and you entered
kill 3

the system would display the following:
ERROR: You cannot kill your own session.

Instead, use the quit or logout command if you want to log out.

Page 4-36

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.
If you wanted to kill the session of the user with a session number of 2 immediately, you
would enter
kill -f 2

at the system prompt.
The default timeout for the kill command is 2 seconds. You can modify the duration of the
timeout by using -t option in conjunction with the -f option. To use the timeout option, enter
kill, followed by -t, the number of seconds for the timeout, -f, and the session number of the
user. For example, if you wanted to kill the session of the user with a session number of 2 in
15 seconds, you would enter
kill -t15 -f 2

at the system prompt. The valid range for the timeout is 1 to 240 seconds.
♦ Note ♦
You cannot use the timeout option (-t) unless you also
use the -f option.

Page 4-37

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.
The More? prompt appears whenever the maximum number of table entries designated by the
more command has been reached (the more command’s default is 22 lines). Note that if a
table exceeds 22 lines, and the more mode has been configured to display more than 100
lines, the following message appears:
Screen Size larger than 100 Lines, Displaying with 22 Lines (Press Any Key)

After pressing any key, only the page of the table is displayed, followed by the More? prompt.
♦ Important Note ♦
The switch’s more mode is active by default. If the more
mode is turned off, the Search and Filter commands
cannot be used. For more information on the more
command, see The UI Configuration Menu on page 417.
A typical More? UI prompt will look like this:
1 4/6 Brg/ 1/ na 0020da:030995 Tns DFLT Enabld Inactv Disabl AutoSw
1 4/7 Brg/ 1/ na 0020da:030996 Tns DFLT Enabld Inactv Disabl AutoSw
1 4/8 Brg/ 1/ na 0020da:030997 Tns DFLT Enabld Inactv Disabl AutoSw
1 5/1 Brg/ 1/ na 0020da:854050 Tns DFLT Enabld Inactv Disabl AutoSw
More? [,,/,F,N,Q,?]

At the More? prompt, the user is given a list of options, which includes the Search (/) and
Filter (F) commands:

Press (space bar) to display the next page of information.

Press (character return) to display the next line of information.

Press / to enter the Search mode.

Press F to enter the Filter mode.

Press N to renew the search, starting from the next line in the UI table.

Press Q to exit the More? prompt.

Press ? to enter the More? command Help Menu.

These commands are available for admin and diag login sessions. Please refer to the following
sections for more information on the Search and Filter commands, as well as renewing a
search, combining Search and Filter commands, and using wildcards.

Page 4-38

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.
To use the Search command, type / at the More? prompt, followed by the text pattern you are
looking for, then press .
♦ Important Note ♦
The Search command is case sensitive. When using this
command, be sure to type the text pattern exactly as it
would appear in the UI table.
Real World Example
The following example uses the Search command to locate a specific MAC address in the
table. (Before using this example, be sure that the more mode is enabled and the
default is set at 22 lines. For more information, refer to page 4-38.)
macinfo

1. Type macinfo and press . The following screen will be displayed:
Enter MAC address ([XXYYZZ:AABBCC] or return for none) :

Press again. A screen similar to the following will be displayed:
Enter Slot Number (1-5) :

Type the slot number for the module containing the relevant MAC address information
(e.g. 3), then press . A table similar to the following will be displayed:
Total number of MAC addresses learned for this slot: 58
Non-Canonical
Group CAM
Sl/ If/ Service/ In
MAC Address
MAC Address
T ID
Indx
----------------------- -------------------------- ------------------------ --- -------- -------3/ 1/ Brg/ 1 00A0C9:064D04 000593:60B220 E
1 7024
3/ 1/ Brg/ 1 006008:C1D7C2 000610:83EB43 E
1 7030
3/ 1/ Brg/ 1 0020DA:88F110 00045B:118F08 E
1 70E6
3/ 1/ Brg/ 1 0020DA:B6FF12 00045B:6DFF48 E
1 7094
3/ 1/ Brg/ 1 0020DA:8A7DC0 00045B:51BE03 E
1 705A
3/ 1/ Brg/ 1 0020DA:A67FA2 00045B:65FE45 E
1 7120
3/ 1/ Brg/ 1 0020DA:024F75 00045B:40F2AE E
1 710C
3/ 1/ Brg/ 1 0020DA:9B88E4 00045B:D91127 E
1 70EE
3/ 1/ Brg/ 1 0020DA:9C062B 00045B:3960D4 E
1 7074
3/ 1/ Brg/ 1 0020DA:79F062 00045B:9E0F46 E
1 70D2
3/ 1/ Brg/ 1 006008:991CA7
000610:9938E5 E
1 701C
3/ 1/ Brg/ 1 0020DA:936A8F 00045B:C956F1 E
1 712A
3/ 1/ Brg/ 1 0020DA:9CEAC5 00045B:3957A3 E
1 70CC
3/ 1/ Brg/ 1 0020DA:9B9B54 00045B:D9D92A E
1 70D6
3/ 1/ Brg/ 1 0020DA:7AAE24 00045B:5E7524 E
1 70B8
3/ 1/ Brg/ 1 0020DA:A9EEB3 00045B:9577CD E
1 710A
3/ 1/ Brg/ 1 0020DA:8DB20B 00045B:B14DD0 E
1 7080
3/ 1/ Brg/ 1 0020DA:9F6B82 00045B:F9D641 E
1 70F4
3/ 1/ Brg/ 1 0020DA:8762A3 00045B:E146C5 E
1 7126
3/ 1/ Brg/ 1 006008:C1D7C2 000610:83EB43 E
1 7030
More? [,,/,F,N,Q,?]

Last
Exp
S Seen
Timer
---- --------- ----------T
134
300
T
115
300
T
46
300
T
66
300
T
83
300
T
27
300
T
34
300
T
45
300
T
76
300
T
52
300
T
117
300
T
23
300
T
53
300
T
50
300
T
58
300
T
34
300
T
72
300
T
42
300
T
24
300
T
115
300

Note that, because the information in the table exceeds the more command’s default page size
of 22 lines, the More? prompt appears at the bottom of the screen.

Page 4-39

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 ........
3/
3/
3/
3/
3/
3/
3/
3/
3/
3/

1/
1/
1/
1/
1/
1/
1/
1/
1/
1/

Brg/
Brg/
Brg/
Brg/
Brg/
Brg/
Brg/
Brg/
Brg/
Brg/

1
1
1
1
1
1
1
1
1
1

0020DA:9E479D
0020DA:9D0D1B
0020DA:97CDE0
00A0C9:8DED5B
0020DA:92A152
0020DA:8528D5
0020DA:93BF73
0020DA:B956B5
0020DA:730F03
0020DA:8BA710

00045B:79E2B9
00045B:B9B0D8
00045B:E9B307
000593:B1B7DA
00045B:49854A
00045B:A114AB
00045B:C9FDCE
00045B:9D6AAD
00045B:CEF0C0
00045B:D1E508

E
E
E
E
E
E
E
E
E
E

1
1
1
1
1
1
1
1
1
1

702C
7030
70E6
7094
705A
7120
710C
70EE
7074
70D2

T
T
T
T
T
T
T
T
T
T

138
67
122
114
97
102
130
56
68
99

300
300
300
300
300
300
300
300
300
300

Note that the line containing information for the specified MAC address (0020DA:9E479D) now
appears at the top of the screen, followed by any remaining lines in the UI table. (In this case,
the last line of the macinfo UI table contains MAC address 0020DA:8BA710, as shown).

Renewing a Search
If you execute the Search command and the resulting page still exceeds the maximum
number of table entries designated by the more command, you can renew the Search. Do this
by typing n at the More? prompt. The Search command will scan the remainder of the table
and display the next line containing the desired text pattern at the top of the screen.

Page 4-40

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.
To use the Filter command, type f at the More? prompt, followed by the text pattern you want
displayed in the UI table, then press .
♦ Important Note ♦
The Filter command is case sensitive. When using this
command, be sure to type the text pattern exactly as it
would appear in the UI table.
Real World Example
The following example uses the Filter command to display only those lines containing Lane
services in the vivl table. (Before using this example, be sure that the more mode is enabled
and the default is set at 22 lines. For more information, refer to page 4-38.)
1. Type vivl and press . A table similar to the following will be displayed:
Virtual Interface VLAN Membership
Slot / Intf / Service / Instance Group
Member of VLAN#
----------------------------------------- --------------------------------1
/1
/Rtr
/1
1
1
1
/1
/Rtr
/2
33
1
1
/1
/Rtr
/3
111
1
1
/1
/Rtr
/4
33
2
1
/1
/Rtr
/5
1
3
1
/1
/Rtr
/6
1
4
1
/1
/Rtr
/7
33
7
1
/1
/Rtr
/8
33
3
1
/1
/Rtr
/9
1
5
1
/1
/Rtr
/10
1
6
1
/1
/Rtr
/11
33
5
1
/1
/Rtr
/12
33
6
1
/1
/Rtr
/13
999
1
2
/1
/Lne
/1
1
1
2
/1
/Lne
/2
111
1
3
/1
/Brg
/1
33
14
3
/2
/Brg
/1
1
1
3
/3
/Brg
/1
1
1
3
/4
/Brg
/1
1
1
More? [,,/,F,N,Q,?]

Note that, because the information in the table exceeds the more command’s default of 22
lines, the More? prompt appears at the bottom of the screen.

Page 4-41

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. All
other table entries have been filtered from the UI.

Combining Search and Filter Commands
If you receive a More? prompt after using the Filter command, the filtered information still
exceeds the maximum number of table entries designated by the more command. To further
refine your results, you can combine the Search and Filter commands.
To combine the Search and Filter commands, type / at the Filter mode’s More? prompt,
followed by a revised text pattern of up to 80 characters. Note that you can combine the
Search and Filter commands only after you have executed a Filter command and received a
More? prompt at the bottom of the resulting page.
♦ Reminder ♦
Both the Search and Filter commands are case sensitive. When using these commands, be sure to type the
text pattern exactly as it would appear in the text UI
table.
Real World Example
The following example combines the Search and Filter commands to find specific IP address
information in the ipr table. (Before using this example, be sure that the more mode is
enabled and the default is set at 22 lines. For more information, refer to page 4-38.)

Page 4-42

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.33
1
1:1
DIRECT
172.17.0.0
255.255.0.0
172.17.6.122
1
999:1
DIRECT
172.31.0.0
255.255.0.0
172.31.4.33
1
33:3
DIRECT
172.32.0.0
255.255.0.0
172.32.4.33
1
33:2
DIRECT
172.33.0.0
255.255.0.0
172.33.4.33
1
33:1
DIRECT
172.35.0.0
255.255.0.0
172.35.4.33
1
33:5
DIRECT
172.36.0.0
255.255.0.0
172.36.4.33
1
33:6
DIRECT
172.37.0.0
255.255.0.0
172.37.4.33
1
33:7
DIRECT
172.111.0.0
255.255.0.0
172.111.4.33
1
111:1
DIRECT
198.168.12.0 255.255.0.0
192.168.12.1
1
1:1
DIRECT
198.168.13.0 255.255.0.0
192.168.13.1
1
1:1
DIRECT
More? [,,/,F,N,Q,?]

Note that, because the information in the table exceeds the more command’s default of 22
lines, the More? prompt appears at the bottom of the screen.
2. Use the Filter command to display all IP network addresses within the IP Routing table that
contain 198. To do this, type f at the More? prompt, followed by the specified text pattern:
f/198

Press . A screen similar to the following is displayed:
Filtering .......
198.168.12.0
255.255.0.0
198.168.13.0
255.255.0.0
198.168.236.0 255.255.0.0
198.168.237.0 255.255.0.0
198.168.238.0 255.255.0.0
198.168.239.0 255.255.0.0
198.168.240.0 255.255.0.0
198.168.241.0 255.255.0.0
198.168.242.0 255.255.0.0
198.206.181.0 255.255.255.0
198.206.183.0 255.255.255.0
198.206.184.0 255.255.255.0
198.206.185.0 255.255.255.0
198.206.186.0 255.255.255.0
198.206.187.0 255.255.255.0
198.206.188.0 255.255.255.0
198.206.189.0 255.255.255.0
198.206.190.0 255.255.255.0
198.206.191.0 255.255.255.0
198.206.192.0 255.255.255.0
198.206.193.0 255.255.255.0
198.206.194.0 255.255.255.0
More? [,,/,F,N,Q,?]

198.168.12.1
198.168.13.1
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254

1
1
4
4
4
4
4
4
4
2
3
3
3
2
2
2
3
2
2
2
2
2

1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1
1:1

DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT
DIRECT

Because the filtered information in the table still exceeds the more command’s default of
22 lines, the More? prompt appears at the bottom of the screen.

Page 4-43

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.203.0 255.255.255.0
/Networking/IP %

172.16.255.254
172.16.255.254
172.16.255.254
172.16.255.254

2
2
2
2

1:1
1:1
1:1
1:1

DIRECT
DIRECT
DIRECT
DIRECT

Note that the IP address, 198.206.200.0, now appears at the top of the screen, followed by
any remaining lines in the table. (In this case, the last line of the ipr table contains information for IP address 198.206.203.0, as shown).

Using Wildcards with Search and Filter Commands
Wildcards allow users to substitute symbols (* or ?) for text patterns while using the Search
and Filter commands.
Any number of wildcards can be used within a single search string. In addition, multiple character (*) and single character (?) wildcards can be combined within a single search string.

Wildcard Command Options
Multiple Characters
An asterisk (*) is used as a wildcard for multiple characters in a text pattern. For example, the
Filter pattern
/*.img

will filter out all lines from the UI table except those containing any text followed by .img.
This wildcard can also be used within a specific text pattern. For example, the Filter pattern
/1*6

will filter out all lines from the UI table except those containing 1, followed by any number of
characters, then 6. For example:
1:3/6

or
33:3/1

or
16.

Page 4-44

Virtual port (#66)

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.

♦ Note ♦
If you use a wildcard at the Search command and the
resulting page still exceeds the maximum number of
table entries designated by the more command, you can
renew the search, starting from the next line containing the text pattern. Do this by typing n at the More?
prompt. Note that you can renew a search only while
in Search and Search/Filter modes.

Page 4-45

UI Table Filtering (Using Search and Filter Commands)

Page 4-46

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.
• FTP Client - The Omni Switch/Router can also be an FTP client. You can use this by
connecting a terminal to the switch and using the set of FTP commands in the User Interface. You can also do this through a telnet session.
• ZMODEM - You can load software directly through the serial port with any terminal emulator that supports the ZMODEM protocol. You can do this using the file commands in the
User Interface or through the boot line prompt. Note that a ZMODEM transfer of larger files
can take several minutes to complete.
Do Not Mix Software Versions
When loading software, ensure that the versions of software for all the modules are from the
same release. Mixing earlier versions of software with current versions can cause the switch to
reset or hang.
File Transfer/Corruption Problems
If at anytime, a file transfer fails, a fragment of the file may be left on your system. This
remaining file is corrupted. You should delete the file fragment and reload the file before
continuing. If the MPX image file (mpx.img) is corrupted, you will receive a message during
the boot sequence requesting you to delete the file. You should delete the file and reload it
using ZMODEM through the boot line prompt. See Using ZMODEM With the Boot Line Prompt
on page 5-5 for information on loading through the boot prompt.

Page 5-1

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. Use your FTP client software just as you would with any FTP server. When you connect to
the switch you will be able to see the files contained in the flash directory. It is the only
directory in the switch.
3. Note that because of the organization of files in the switch, any time a file is deleted, the
flash memory is compacted. Depending on the number of files in the switch and where
they are located in memory, this compaction can take anywhere from a few seconds to a
couple of minutes.
4. When you transfer a file to the switch and one of the same name exists, the old file must
first be deleted. You first delete the old file, then the compaction takes place, and then
you can transfer the new file. When you begin your transfer, you may not see anything
happening for approximately 2 minutes due the file compaction procedure. After compaction, the file will be transferred.

Page 5-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. The system will prompt for a user name. It saves the last user name. If it’s the one you
want, press or enter the new user name.
4. The system will prompt for a password. Enter your password.
5. After logging onto the system you will receive the ftp> prompt. Type a question mark (?)
to review the ftp commands. These commands are described in Chapter 7, “Managing
Files.” The following screen displays:
Supported commands:
ascii
binary
bye
dir
get
help
put
pwd
quit
lpwd

cd
hash
remotehelp

delete
ls
user

ascii

Set transfer type to ASCII (7-bit).

binary

Set transfer type to binary (8-bit).

bye

Close gracefully.

Change to a new directory on the remote machine.

delete

Delete a file on the remote machine.

dir

Obtain a long listing on the remote machine.

get

Retrieve a file from the remote machine.

hash

Print the hash symbol (#) for every block of data transferred. This
command toggles hash enabling and disabling.

Summary listing of the current directory on the remote host.

put

Send a file to the remote machine.

pwd

Display the current (present) working directory on the remote host.

quit

Close gracefully.

remotehelp

List the commands that the remote FTP server supports.

user

Send new user information.

lpwd

Display the current (present) working directory on the local host.

Summarize this list.

If you lose communications while running ftp, you may receive the following message:
Waiting for reply (Hit ^C to abort)...........

6. You may press to abort the ftp or wait until the communication failure is resolved
and the ftp transfer will continue. Note that Sun OS systems lose echo when you use the
cntl-c key combination.

Page 5-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. If you are in this situation, the
only way to load software is using ZMODEM with the boot line prompt.
To use ZMODEM, you must have a terminal emulator that supports the ZMODEM protocol.
There are many packages on the market and they operate differently; therefore instructions
on how to use them are beyond the scope of this document. Consult the user manual which
came with your terminal emulation software.
Before doing a serial port transfer, you should set the baud rate to the highest possible
(however, it is not recommended that you run it at 38.4 Kbps). Running at 19200 is twice as
fast as 9600. To set the baud rate, use the ser command. For more information on the ser
command, see Chapter 6, “Configuring Management Processor Modules.”
Note
If a file you are transferring already exists in the
switch’s flash memory, you must remove the file before
transferring the new file via ZMODEM.

Using ZMODEM with the load Command
If your switch is up and running, log on to the switch. Type ls to list the files in flash
memory. If the file you are going to transfer exists, you must delete it first with the rm
command.
From the File menu, type ? to list the file commands. The command you use to start the
ZMODEM process is load. The load command does not support speeds greater than 19,200

bauds.
/File % load
The Console (DCE) port is currently running at 19200 baud
Type ‘y’ to start ZMODEM download, ‘q’ to quit (y) : y
Upload directory: /flash
ZMODEM ready to receive file, please start upload (or send 5 CTRL-X’s to abort).
**B0100000023be50

Activate the ZMODEM transfer according to the instructions that came with your terminal
emulation software. When the transfer is completed use ls again to list the file or files you
have loaded.

Page 5-4

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. This
section covers only specific step-by-step instructions to load a file using ZMODEM at the
[boot]: prompt. Before doing this you may want to familiarize yourself with the boot line
commands. See Appendix A, “Boot Line Prompt,” for more information.
♦ Important Note ♦
Loading software through the boot prompt should only
be done when the switch is off line and not being used
for normal network traffic.
Set Up the Correct Baud Rate
1. Connect a terminal to the console port. The terminal must be set to the last values set in
the switch before it was powered down. For example if you were running at 19200,8,n,1,
you must set your terminal to these values.
Note
If you have deleted or lost your configuration file
(mpm.cfg), the console port values will revert back to
the factory settings which are 9600,8,n,1.
If you are not sure what baud rate your switch is running, try the last known value. If
your terminal displays garbage, keep changing the baud rate on your terminal emulator
until you see normal ASCII characters.
2. If the switch is on, switch it off for a few seconds, then back on. You should see the boot
start up on your screen. You will see the following:
System Boot
Press any key to stop auto-boot...
2

The number 2 shown above counts down to 0. To stop the boot, you must press a key
before the number counts down to 0. If you miss this, simply turn the switch off for a few
seconds, then back on to restart the process. Note that if there is no software in the switch
it will not be able to boot and will eventually end up at the [boot] prompt anyway.

Page 5-5

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. The following screen
displays:
[Boot]: ?
?
- print this list
Q
- boot (load and go)
p
- print boot params
c
- change boot params
l
- load boot file
g adrs
- go to adrs
d adrs [,n]
- display memory
m adrs
- modify memory
f adrs, nbytes, value
- fill memory
t adrs, adrs, nbytes
- copy memory
e
- print fatal exception
n netif
- print network interface device address
L
- list ffs files
P
- Purge system: remove ALL ffs files
R file [files]
- remove ffs file(s)
S
- save boot configuration
V
- display bootstrap version
$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pwr=passwd] f=#
tn=targetname s=script o=other
Boot flags:
0x02 - load local system symbols
0x04 - don’t autoboot
0x08 - quick autoboot (no countdown)
0x20 - disable login security
0x40 - use bootp to get boot parameters
0x80 - use tftp to get boot image
0x100 - use proxy arp
0x1000 - factory reset
available boot devices: sl ffs zm
[Boot:]

Note that these commands are all case sensitive.
Type L to lists the files in flash memory. This will help you determine what files may be missing. If the file you are going to transfer exists, you must delete it first with the R command.
You may want to purge memory and reload all the files. To purge the flash memory, type in
the P command.
Warning
After using the P command, there will be no files in
flash and you will have to reload them all with
ZMODEM.

Page 5-6

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.cmd
Console params : 9600,n8lc
Modem params : 9600,n8l
Boot flags :0xb
Other: dvip:no_name, 198.206.183.253, 255.255.255.0, 198.206.183.255;
[Boot]:

3. When you complete the command, the system will return to the [Boot]: prompt. Type in
the “at” command (@ ) to load the boot parameters.
[Boot]: @
Boot device : zm
Boot file : /flash/mpx.img
Startup script: /flash/mpx.cmd
Console params : 9600,n8lc
Modem params : 9600,n8l
Boot flags :0xb
Other: dvip:no_name, 198.206.183.253, 255.255.255.0, 198.206.183.255;
Attaching network interface lo0... done.
Disk load or Boot load (D/B/Q)? -> d

4. At the Disk load or Boot load {D/B/Q}? -> prompt, type in d to tell the system to load from a
disk. The system is prepared to accept a ZMODEM transfer, and displays the following:
Upload directory: /flash
ZMODEM ready to receive file, please start upload (or send 5 CTRL-X’s to abort).
**B0100000023be50

5. Activate the ZMODEM transfer according to the instructions that came with your terminal
emulation software.
6. When the transfer is completed use L (case sensitive) to list the files you have loaded.
7. Repeat this procedure for every file that you want to load.

Page 5-7

Using ZMODEM

Page 5-8

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. Switching modules are dependent on the MPX for downloading software and for
receiving initialization and configuration information. In addition, the Network Management
System (NMS) depends on the MPX to send and receive SNMP messages for managing the
switch.
♦ Important Note ♦
All of the UI commands described in this chapter also
work with the Omni Switch/Router MPX.
The Omni Switch/Router also support two MPXs with one acting as the primary and with one
acting as the secondary. If the primary MPX fails, the secondary MPX can take over automatically. Operating with redundant MPXs can also help avoid network downtime.
♦ Note ♦
When you have two MPXs in one chassis, they must be
installed in slots 1 and 2, and only one will be active.
The primary MPX executes all the commands and, when needed, sends requests to the
secondary MPX. The secondary MPX continuously monitors the primary MPX. For more information on MPXs, see Chapter 2, “The Omni Switch/Router MPX.”
The UI provides commands to configure the serial port, to configure the Ethernet management port, and a set of commands to monitor and configure primary and secondary MPXs.
These commands are described in the pages that follow.

Page 6-1

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. You will see the following message:
Port to configure? {(C)onsole,(M)odem} (Console) :

Press C if you want to configure the console port (female, DCE) parameters, or type M to
configure the modem port (male, DTE) parameters. The default is the Console Port (C).
4. The current port values are shown, followed by a prompt to change the speed value.
Current Console (DCE) configuration:
9600 bps, 8 data bits, None parity, 1 stop bit, running Console (shell)
Speed (9600):

Enter the speed (in bits per second) at which you want the port to operate, or simply
press to accept the default in parentheses. Valid values are 1200, 9600, 19200, and
38400 bps.
5. The following prompt displays:
Data size {7/8} bits (8) :

Enter the data size in bits (7 or 8). The default is 8. Press to accept the default in
parentheses.
6. The following prompt displays:
Parity { (N)one/(E)ven/(O)dd } (None) :

Enter the parity (none, even, odd) and press . The default is None.
7. The following prompt displays:
Stop bits {0/1/2} (1):

Enter the number of stop bits (0, 1, or 2) and press . The default is 1.
8. The following prompt displays:
Mode {(D)own,(C)onsole,(A)uxConsole,(S)LIP} (C) :

Page 6-2

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. The following prompt displays:
Set (and save) these settings {(S)ave/(Q)uit) (Save) :

Enter save to accept the parameters you entered and exit, or enter quit to exit this
command without saving your changes.

Changing Port Speed When Communication With The Switch Lost
When you cannot communicate with the switch, there is an alternative method you can use to
toggle through the various serial port speed options. The port defaults to 9600 bps. But if you
send a Break signal (by pressing the BREAK key), the port speed will change to the next
higher speed. When it reaches the highest speed (38400 bps), it toggles back to the lowest
speed (1200 bps). You cycle through the port speeds in the following order: 9600–19200––
38400–1200.
♦ Note ♦
On the MPX you must remove the default baud rate
shunt (E1), which fixes the baud rate at 9600 bps,
before you can change the baud rate. This shunt is
located near the front end of the circuit board, just to
the right of the Ethernet management port.

Configuring the Modem Port
If you plan to use the modem port as your main connection to User Interface software, then
you need to make sure its mode and jumper settings are configured correctly.

Modem Port Mode
The ser command allows you to configure an active modem port to SLIP, console, or auxiliary console mode. When using a modem, it is recommended that you configure the two
ports as follows:
modem port mode=SLIP
console port mode=console
This configuration allows you to use the modem port to access User Interface software
through a SLIP connection. The console port is used as an optional way to access software.
♦ Please Note ♦
You need Release 3.2 or above to use the modem and
console ports simultaneously.
Another valid configuration is as follows:
modem port mode=console
console port mode=down

Page 6-3

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.
A third valid configuration that keeps both ports active is:
modem port mode=console
console port mode=SLIP
This configuration allow you to use the modem port regularly and use a SLIP connection to
access switch software through the console port.
A fourth valid configuration that keeps both ports active is:
modem port mode=auxiliary
console port mode=console
This configuration allow you to use the console and modem ports simultaneously to access
switch software.

Configuring SLIP
To configure SLIP, enter the slipc command. If you enter the command and SLIP is not running
on any ports, the system displays the following message:
Current SLIP configuration
SLIP not running on any ports, do you want to configure it?
Yes, No {Y/N} (Y) :

Enter y to display current information. Enter n to skip the display. To configure the required
SLIP parameters, complete the following steps:
1. Type slipc at the prompt and press .
2. Enter a valid IP address.
3. Enter a valid remote IP address.
You can use the ping command to validate the connection’s integrity.

Page 6-4

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.254
: UNSET
: Inactive

Command {Item=Value/?/Help/Quit/Redraw/Save} (Redraw) :

The question mark option (?) and the Help option provide reference and instructional information on using this command. The Redraw option refreshes the screen.
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. If you do not
want to save the changes enter quit or Ctrl-D.
♦ Important Note ♦
On some revisions of the MPX, you must configure the
Ethernet management port with the boot prompt before
you can use the ethernetc command. See Appendix A,
“The Boot Prompt,” for more information on configuring the Ethernet management port with the boot
prompt.
The configurable options displayed by the ethernetc command are described below.
1) Port Admin status UP
Enter 1=Yes (the default) to enable the Ethernet management port or 1=No to disable it.

Page 6-5

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). If no mask is provided, the switch will try to determine the mask using Internet Control Message Protocol (ICMP) requests. For example, to change the subnet mask to
255.255.255.254, enter
3=255.255.255.254

at the prompt.
4) Bcast Address
The default broadcast address is automatically derived from the default VLAN IP address class
(the default is 192.255.255.255). You can enter a new address in dotted decimal or hexadecimal notation. For example, to change the broadcast address to 198.206.184.255, enter
4=198.206.184.255

at the prompt.
5) Gateway Address
You can enter an IP address for the first hop router to a remote host (if the host is on a different IP net) in dotted decimal or hexadecimal notation. The default is 192.168.1.1. For example, to change this address to 198.206.184.170, enter
5=198.206.184.170

at the prompt.
6) Remote Host Address
You can enter an IP address for a a remote host (if the host is on a different IP net) in dotted
decimal or hexadecimal notation. The default is 192.168.1.1. For example, to change this
address to 198.206.184.170, enter
5=198.206.184.170

at the prompt.
7) RIP Mode
This parameter is an informational field, which shows that the RIP mode is inactive. You
cannot modify this parameter.

Page 6-6

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.
To get around this duplicate IP address problem, you must disable automatic file synchronization and then you must configure different IP addresses for the two EMPs. To do this, perform
the following steps:
1. On the primary management module, enter
syncctl

at the system prompt. (See Setting Automatic Config Synchronization on page 6-15 for
more information on the syncctl command.)
2. If automatic file synchronization is already disabled, simply press . If it is enabled,
enter disable at the prompt.
3. Enter
ethernetc

at the prompt. (See Configuring the Ethernet Management Port on page 6-5 for more
information on the ethernetc command.)
4. Enter 2= followed by the IP address for the EMP on the primary management module.
5. Enter
save

at the prompt to save the IP address.
6. Enter
renounce

at the prompt to make the primary management module the secondary module and the
secondary module primary.
7. Log into the now primary management module.
8. On the now primary management module, enter
syncctl

at the system prompt.
9. If automatic file synchronization is already disabled, simply press . If it is enabled,
enter disable at the prompt.
10. Enter
ethernetc

at the prompt.
11. Enter 2= followed by the IP address for the EMP on the management module.

Page 6-7

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.

Page 6-8

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 following is a typical example of the message that displays when
you enter mpm for a switch without a redundant MPX.
Currently this slot 1 holds the Primary MPM; there is no secondary MPM.

The following is a typical example of the message that displays when you enter mpm for a
switch with redundant MPXs on the primary MPX.
Currently this slot 1 holds the Primary MPM and slot 2 holds the secondary.

The following is a typical example of the message that displays when you enter mpm for a
switch with redundant MPXs on the secondary MPX.
Currently slot 1 holds the Primary MPM; this slot 2, holds the secondary MPM.

MPM Menu Commands
The mpm command also takes you to the mpm menu which contains the commands needed
to configure single and redundant MPXs. With a serial or modem connection, you can
communicate with either the primary or secondary MPX by connecting to the respective RS232
connectors. With a telnet connection, however, you can only communicate with the primary
MPX.
Type a ? to list the mpm commands. One set of commands will be displayed if you are
connected to the primary MPX and another command will be displayed if you are connected
to the secondary MPX. If you are connected to the primary MPX, you will see the following.
Command
sls
mpmstore
mpmreplace
mpmload
mpmrm
renounce
nisuf
syncctl
configsync
imgsync
secreset
swap

Redundancy Menu
List the contents of the Secondary /flash and /simm directories
Store file to Secondary /flash or /simm directory
Replace file on Secondary /flash or /simm directory
Load file from Secondary MPM
Remove file from Secondary MPM
Give up control to Secondary
Set load suffix for NI image files
Enable/Disable synchronization of configuration data
Synchronize configuration data
Synchronize Image (Executable) files
Reset Secondary MPM
Change swap status of chassis

Page 6-9

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.2 and later, the commands in the mpm menu support the use of more than one
flash directory. Since more than one flash directory can exist, you must indicate which flash
directory you want to use when you access a secondary MPX from a primary MPX and when
you access a primary MPX from a secondary MPX. All of these commands begin with the
prefix mpm and are listed below.
mpmstore
mpmreplace
mpmload
mpmrm
mpmget

To indicate which flash directory you want to use, enter a slash (/), the name of the directory, and another slash (/) before the file name in all commands that begin with the prefix
mpm. For example, to transfer the asm.img file from the /simm directory on the secondary MPX
to the primary MPX when you have logged into the secondary MPX, enter
mpmget /simm/asm.img

at the system prompt.
♦ Important Note ♦
In the current release, you must indicate the name of
the flash directory in commands that begin with the
prefix mpm even if you have just one flash directory on
both MPXs.

Page 6-10

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.img

27204
27561
1790889
83588
32768
18072
32768
32
547041

7/14/99
7/14/99
7/14/99
7/14/9
1/ 1/70
7/30/99
7/30/99
1/ 1/70
8/27/9

11:39
11:39
11:39
11:39
00:00
13:51
14:40
00:00
16:01

/flash has
1071449 bytes free.
/simm Not present.

The sls command lists every file in the secondary MPX’s flash memory followed by its size (in
bytes), creation date, and creation time. The three-letter file name suffix indicates the type of
file which includes configuration (cnf and cfg), command (cmd), and image (img). The image
file suffix can be changed for both the primary and secondary MPXs with the nisuf command,
which is described in Setting the Load Suffix on page 6-14.

Transferring a File to the Secondary MPX
The mpmstore command transfers a file in the flash memory of the primary MPX to the flash
memory of the secondary MPX. To use this command, enter mpmstore, 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 transfer the file mpm.log from the /flash directory on the primary MPX to the
secondary MPX, for example, you would enter
mpmstore /flash/mpm.log

at the system prompt. The following will be displayed.
Transferring...

If the file already exists on the target MPX, something similar to the following message will be
displayed.
File mpm.log exists on slot 2

Use the mpmreplace command, which is described in Replacing a File on the Secondary MPX
on page 6-12, to replace a file that already exists.

Page 6-11

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.
For example, to replace the file mpm.log on the secondary MPX with the file mpm.log from the
/flash directory on the primary MPX, for example, you would enter
mpmreplace /flash/mpm.log

at the system prompt. The following will be displayed.
Deleting.
Transferring

If the file already exists on the target MPX and it is identical to the one you are transferring,
something similar to the following message.
File mpm.log is identical on Primary and Secondary 2

If the files are identical, the mpmreplace command will terminate and the file will not be
replaced.

Loading a File from the Secondary MPX
The mpmload command loads a file from the flash memory of the secondary MPX into the
flash memory of the primary MPX. To use this command, enter mpmload, followed by a space,
a slash (/), the name of the flash directory, another slash (/), and the name of the file you
want to load.
For example, to load the file mpm.log from the /flash directory on the secondary MPX into the
primary MPX, for example, you would enter
mpmload /flash/mpm.log

at the system prompt.

Page 6-12

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.log from the /flash directory on the secondary MPX in
slot 2, for example, you would enter
mpmrm /flash/mpm.log

at the system prompt. Something similar to the following will be displayed.
Checking for /flash/mpm.log on slot 2

After a brief moment, the file will be deleted from the secondary MPX and something similar
to the following will be displayed.
Deleting /flash/mpm.log on slot 2 . Done.

♦ Warning ♦
You cannot recover a file once it has been deleted with
the mpmrm command.

Page 6-13

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.
♦ Warning ♦
The renounce command should only be used during
network down times since it could cause network interruptions.
To transfer control from primary MPX to the secondary MPX, enter
renounce

at the system prompt. The following prompt will display.
Confirm? (n):

Press y to transfer control to the secondary MPX or press n to cancel the command (the
default is n). If you enter y, the switch will reset after displaying the following message.
System going down immediately...

The switch will reboot and the original secondary MPX will be the primary once the switch
comes back up.

Setting the Load Suffix
The nisuf command sets the load suffix for the switch’s executable image files. (The factory
default suffix is img.)
♦ Warning ♦
The nisuf command should only be used when it is
necessary to have two versions of the software on the
switch at the same time and the user is directly
connected to the console for reboot.
You can change it by typing the nisuf command followed by the new suffix. For example, to
change the load suffix from img to bin, enter
nisuf bin

at the system prompt. The following message will then be displayed.
Changing load suffix from img to bin

You should create or load new image files with the new suffix as soon as possible because
the switch will not recognize the files with the old suffix as image files. See Chapter 5,
“Installing Switch Software,” and Chapter 7, “Managing Files,” for information on loading and
creating files.

Page 6-14

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.

Enabling Automatic Config Synchronization
To enable synchronization between the primary and secondary MPXs, enter
syncctl

at the system prompt. The following prompt will then be displayed if synchronization is not
enabled.
Desired state (enable):

Press to enable synchronization or enter disable to cancel. If you enabled synchronization, the following will be displayed.
Configuration synchronization is now Enabled

Note that automatic configuration synchronization is disabled unless all image (img) and
Programmable Gate Array (PGA) files in the switch are synchronized first. See Synchronizing
Image Files on page 6-16 for information on the imgsync command, which synchronizes
image and PGA files.
The interval between updates is 5 minutes. The primary MPX will copy any changes to the
secondary MPX after 5 minutes have elapsed since the last update.

Disabling Automatic Config Synchronization
To disable synchronization between the primary and secondary MPXs, enter
syncctl

at the system prompt. The following prompt will then be displayed if synchronization is
enabled.
Desired state (disable):

Press to disable synchronization or enter enable to cancel. If you disabled synchronization, the following will be displayed.
Configuration synchronization is now Disabled

If automatic config synchronization is Disabled, the configuration file in the secondary MPX
will be unaffected if you change the configuration file in the primary MPX.

Page 6-15

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.
Syncing Config file
Config files are currently synchronized.

See Setting Automatic Config Synchronization on page 6-15 for information on setting automatic config synchronization.

Synchronizing Image Files
The imgsync command copies all of the image (executable) files in the primary MPX to the
secondary MPX. When used in conjunction with the configsync command, it ensures that the
two MPXs are running exactly the same versions of software and are in sync (i.e., have the
same configuration). To synchronize all the image files, enter
imgsync

at the system prompt. When you run imgsync you will be asked if you want to synchronize
the cmd file and/or PGA files if they are found to be different.
♦ Note ♦
If any PGA file is being used by a Token Ring module
and you choose to sync the cmd file, then the PGA file
that is in use will be synced even if you do not choose
to synchronize PGA files.
Something similar to the following prompt will be displayed.
Sync cmd file (y) :

Press y to sync the cmd file or press n to skip this file (the default is y). If you have any PGA
files, you will be asked if you want to sync those files. In addition, if the secondary MPX has
any additional image, then the following prompt will be displayed.
Remove Additional images from Secondary (n) :

Press y to remove any extra image on the secondary MPX or press n to keep these files (the
default is n). After you answer all the prompts, something similar to the following will be
displayed.
8 files to be synchronized
1 file to be synchronized
Syncing
Deleting /flash/mpx.cmd..................
Replacing /flash/mpx.cmd.....

Page 6-16

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.log from the /flash directory on the primary MPX to the
secondary MPX you would enter
mpmget /flash/mpm.log

at the system prompt. After a brief moment, the file will be transferred into the secondary
MPX. The following would then be displayed.
Transferring .. Complete

Page 6-17

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.
♦ Warning ♦
The takeover command should only be used during
network down times since it could cause network interruptions.
To transfer control from primary MPX to the secondary MPX, enter
takeover

at the system prompt. The following prompt will display.
Confirm? (n):

Press y to transfer control to the secondary MPX or press n to cancel the command (the
default is n). If you enter y, the switch will reset after displaying the messages similar to the
following.
System going down immediately...
Please standby, chassis configuration changing (Hit ^C to abort).....Taking over
as Primary
...
Alcatel SNMP Agent Operational.

The switch will reboot and the original secondary MPX will be the primary once the switch
comes back up.

Page 6-18

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 .. complete

♦ Note ♦
To reset a switching module, use the reset command,
which is described in Chapter 36, “Running Hardware
Diagnostics.”

Page 6-19

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 the Swap State
To display the current swap state of the chassis, enter
swap

at the system prompt. If the swap mode is OFF (the default for the switch), something similar
to the following will be displayed.
Swap is OFF, timeout is 5 minutes
usage swap { ON [ minutes ] | OFF [ minutes ] }

If the swap mode is ON, something similar to the following will be displayed.
Swap is ON, expires in 4 minutes
usage swap { ON [ minutes ] | OFF [ minutes ] }

The swap mode must be enabled (ON) to hot swap a switching module. If not, the system
may halt or restart. See the subsection below for instructions on enabling the swap mode.

Enabling the Swap Mode
To turn the swap mode ON, enter
swap on

at the system prompt. (The default for swap mode is 5 minutes). Something similar to the
following will be displayed.
Swap is ON for 5 minutes

When you turn the swap state on, you set a timer which determines how long the system will
remain in swap state. After the timer expires, the system will automatically turn off the swap
state.
If you want to vary the amount of time that the swap mode is enabled, enter swap on
followed by the number of minutes you want the swap mode enabled. You can set the swap
state from 1 to 227,055 minutes. To set the swap mode on for 10 minutes, for example, enter
swap on 10

at the system prompt. The following will then be displayed.
Swap is ON for 10 minutes
Save minutes value {Y/N}? (N) :

Press y and then press to save the new value. If you don’t want save, just press
and the default value will not change. You can also turn off the swap immediately as
shown in Disabling the Swap Mode on page 6-21.

Page 6-20

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.
Swap is OFF, timeout is 5 minutes

Page 6-21

Displaying and Setting the Swap State

Page 6-22

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.
All commands described in this chapter will work with files located in the /flash directory on
either the primary or secondary MPX. However, these commands work only with the files that
reside on the MPX to which you are connected. See Chapter 6, “Configuring Management
Processor Modules,” for more information on commands for working with redundant MPXs.
UI commands for file maintenance are grouped into two menus: the File menu and System
menu. File menu commands are listed below. For a list of System menu commands, see
System Menu on page 7-13.

File Menu
The File menu contains commands for loading, listing, copying, and deleting individual
switch files. To access the File menu, enter
file

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.”)
Command
--------------load
ftp
pwd
ls
rm
cp
view
edit
imgcl
Main
Interface

File Menu
----------------------------------------------------------------------------------Download system software using the serial interface
Download from an FTP server
Display the current working directory
List the contents of the current working directory (default
working directory is /flash)
Remove a file
Copy a file
View an ASCII file
Edit buffer locally
Remove all image files
File
Security

Summary
System

VLAN
Services

Networking
Help

All commands in the File menu, except for the load and ftp commands, are described in the
following sections. For instructions on using the ftp and load commands, refer to Chapter 5,
“Installing Switch Software.”
♦ Note ♦
If you want to use the rm, cp, imgcl, and the edit submenu commands, you must be logged in as admin or
diag. See Chapter 4, “The User Interface,” for more
information on login accounts.

Page 7-1

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.
♦ Important ♦
If you remove the configuration files (mpm.cnf and
mpm.cfg) from your switch, all of your switch’s nondefault configuration settings will be deleted at the next
boot sequence. Use caution when removing configuration files and be sure to create backup copies if you
want to safeguard your current configuration.

Changing Directories
You can change the working directory with the cd command. For example:
cd test

at the system prompt. To change the working directory back to /flash file system, enter
cd flash

at the system prompt.

Page 7-2

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.

The ls command lists all the files in the current working directory of the primary MPX’s flash
memory, followed by its size (in bytes), creation date, and creation time. The three-letter file
extension indicates the type of file. Examples include configuration (cnf and cfg), command
(cmd), image (img), Programmable Gate Array (.pga), etc. The ls command also lists the total
number of bytes of free memory in flash memory.
♦ Note ♦
If you are connected to the primary MPX and you want
to display the files in a secondary MPX, use the sls
command, which is further detailed in Chapter 6,
“Configuring Management Processor Modules.”

Page 7-3

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.
♦ Note ♦
If you are connected to the primary MPX and you want
to remove files from a secondary MPX, use the mpmrm
command, which is described in Chapter 6, “Configuring Management Processor Modules.”

Deleting Multiple Files
You can remove multiple files either by entering multiple file names in the command line or
by using wildcards.
When entering multiple file names, be sure to include a space between each file name you
want to delete. For example, to remove both the mpm.cfg and mpm.cnf files, you would enter
the following:
rm mpm.cfg mpm.cnf

Wildcards let you substitute an asterisk (*) for file name text. You can remove all files with
the same extension by entering rm, followed by an asterisk (*), a period (.), and the file
extension. For example, if you want to delete all the files with the log extension, enter
*.old

at the UI prompt. The following message will be displayed:
Remove the following?
/flash/mpm.log.old
/flash/mpm.old
Are you sure you want to remove this? (n)

Press the y key to delete the selected files or press to cancel. If you press the y key,
the following will be displayed:
...2 files removed

The switch will take a few seconds to delete the file and compact the flash memory.
♦ Note ♦
If you want to delete all the image files (i.e., files with
the img extension), you can use the imgcl command,
which is described in Deleting All Image Files on page
7-5.

Page 7-4

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. A screen similar to the one shown below will be displayed.
Remove the following?
/flash/esx.img
/flash/mpx.img
Are you sure you want to remove them? (n)

Press the y key to delete all the image files or press to cancel. If you press the y key,
the switch will spend several minutes deleting the image files.
♦ Note ♦
If you want to delete all files in flash memory, you can
use the newfs command, which is described in Creating a New File System on page 7-15.
After you have deleted all the old image files, you must load new image files using FTP or
ZMODEM so the switch can function. See Chapter 5, “Installing Switch Software,” for instructions on using the ftp and load commands.

Page 7-5

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.cmd -> /flash/mpx.bak : 100%

Displaying Text Files
You can use the view command to display the contents of ASCII (text-based) files. To use this
command, enter view, followed by the name of the file you want to display. To display the
mpx.cmd file, for example, enter
view mpx.cmd

at the system prompt. A screen similar to the one shown below will be displayed.
cmDoDump=1
cmInit

Note that if you try to view a file with non-ASCII characters, an error message will be
displayed. For example, if you use the view command on the file mpm.cfg, the following error
message will appear:
The file mpm.cfg has non-printable characters, can't view

♦ Note ♦
You can edit text files with the edit sub-menu
commands, which are described in Editing Text Files
on page 7-7.

Page 7-6

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. (For information on enabling verbose mode, refer to the uic command description in Chapter 4, “The User Interface.”)
Command
--------------ab
cb
db
eb
ib
lb
nb
rb
wb
Main
Interface

Edit Menu
-------------------------------------------------------Append line(s) to the buffer
Clear the buffer
Delete line from the buffer
Edit a buffer line
Insert buffer line
List contents of the buffer
Name file for buffer
Read file into buffer
Write buffer to file
File
Security

Summary
System

VLAN
Services

Networking
Help

The Edit sub-menu commands are outlined in the following sections. You can edit up to 100
lines of text. Each line of text can be up to 97 characters long.
♦ Note ♦
When you edit text files, you will normally use several
of the Edit sub-menu commands to produce the results
you want. SeeReal-World Example 1 on page 7-11 or
Real-World Example 2 on page 7-12 for examples of
how to use multiple commands from the Edit submenu.

Clearing the Text Buffer
You can use the cb command to clear the Edit buffer’s memory so you can create a new text
file. To use the cb command, enter
cb

at the system prompt.

Page 7-7

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.

Listing the Contents of the Text Buffer
The lb command is used to list the contents of the Edit buffer’s memory. To use this
command, enter
lb

at the system prompt. If there is something in the buffer, the system will display the contents
numbered from the zero. The following display is a typical example:
00: cmDoDump=1
01: cmInit

If there is nothing in the buffer, nothing will be displayed.

Adding Lines of Text to the Text Buffer
You can use the ab command to manually add lines of text to the Edit sub-menu. Note that
the lines you enter are appended at the end of the buffer. For example, if there are 10 lines of
text in the buffer, you will begin entering text at the 11th line. If the buffer is empty, the line
of text you enter will be the first line of text in the buffer.
To add text to the buffer, enter
ab

at the system prompt. A screen similar to the one shown below will be displayed:
02 :

Enter your text and press the key to add the text to the buffer. If the buffer is not full,
the system will prompt you to enter another line of text. If the buffer is full (i.e., there are 100
lines in the text buffer), the following message will be displayed.
Buffer Full!

To exit the ab command, type a period (.) and press .

Page 7-8

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.

Inserting a Line of Text into the Text Buffer
You can use the ib command to insert a line of text between two existing lines in the buffer.
To use this command, enter ib, followed by the number of the line where you want the new
text to appear. For example, if you want to add the text, atm_use_mbus=3, between lines 00
and 01 in the buffer, enter
ib 1

at the system prompt. The following screen will be displayed:
01:

Enter the line of text, atm_use_mbus=3.
At the system prompt, enter the lb command to view the contents of the buffer. If the original text buffer looked like this,
00: cmDoDump=1
01: cmInit

the revised text buffer, with the inserted text, will now appear as follows:
00: cmDoDump=1
01: atm_use_mbus=3
02: cmInit

Editing a Line Name of Text in the Text Buffer
You can use the eb command to edit an existing line of text in the buffer. To use this
command, enter eb, followed by the line number of the text you want to edit. For example, if
you want to edit the text at line 01, enter
eb 1

at the system prompt. The following screen will be displayed:
01:

Enter the text as you want it to appear and press .
Enter the lb command again to list the contents of the text buffer. Note that the buffer now
reflects the edited line of text.

Page 7-9

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. The following screen is displayed, showing the current working directory (/flash), followed by the new name for the text buffer (/mpx.cmd):
Work buffer name is: /flash/mpx.cmd

Creating a Text File from the Text Buffer
The wb command is used to create—or write—a text file from the text buffer. To use this
command, enter wb followed by the name of the output file. For example, if you want to
create the file switch.txt, enter
wb switch.txt

at the system prompt. The following screen is displayed:
Work buffer name is: /flash/switch.txt

Writing Changes to Existing Files
You can also use the wb command to overwrite changes to an existing file. For example, if
you want to overwrite changes to the file mpx.cmd, enter
wb mpx.cmd

at the system prompt. The following screen is displayed:
/flash/mpx.cmd exists in /flash. Overwrite it? (y)

Press to create the text file from the text buffer. The computer will take a few seconds
as it overwrites the file, and the following information is displayed:
File system compaction in progress...

At the system prompt, enter the lb command to view the name of the buffer. Note that the
work buffer is now named /flash/mpx.cmd.

Page 7-10

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.cmd
ab
02 :
02 : reg_port_rule=1
03 :
No line 3 inserted
lb
00: cmDoDump=1
01: cmInit
02: reg_port_rule=1
Work buffer name is: /flash/mpx.cmd
wb
/flash/mpx.cmd exists in /flash. Overwrite it? (y)
File system compaction in progress...
view mpx.cmd
cmDoDump=1
cmInit
reg_port_rule=1

Page 7-11

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.cmd
cmDoDump=1
cmInit
rifStripping=1

Page 7-12

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.”)
Command
--------------info
dt
ser
mpm
slot
systat
taskstat
memstat
fsck
newfs
syscfg
uic
camstat
camcfg
hrex
ver/ter
echo/noecho
chpr
logging
health
cli
saveconfig
cacheconfig
Main
Interface

System Menu
----------------------------------------------------------------------------------Basic info on this system
Set system date and time
View or configure the DTE or DCE port
Configure a Management Processor Module
View Slot Table information
View system stats related to system, power and environment
View task utilization stats
View memory use statistics
Perform a file system check on the flash file system
Erase all file from /flash and create a new file system
Configure info related to this system
UI configuration; change - prompt, timeout, more, verbose.
View CAM info and usage
Configure CAM info and usage
Enter HRE-X management command sub-menu
Enables/disables automatic display of menus on entry (obsolete)
Enable/disable character echo
Change the prompt for the system (obsolete, use ‘uic’ command
View system logs.
Set health parameters or view health statistics
Enter command line interface
Dump the cache configuration content to the mpm.cnf file.
Set the flag to use cache configuration only.
File
Security

Summary
System

VLAN
Services

Networking
Help

Page 7-13

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. A screen similar to the following will be displayed:
Your bootroms support Flash File System Version 2 and greater.
Out of 16 file descriptors in use, 0 of these are opened on the /flash device.
Performing a file system check using manual mode. If a file is encountered
with a potential problem, you may wish to consider preserving it for technical
support analysis...
Flash file system check in progress...
Checking root file system... OK
Performing file consistency check...
Done.
There doesn't appear to be a system problem related to the Flash File
system or kernel file system data structures. If you are experiencing
problems with the flash file system, perhaps try using the "info",
"systat", or "memstat" commands. They may indicate some other condition
(such as low memory) which could prohibit correct operation of the
file system.

If the fsck command detects a problem with the flash file system, a message will be displayed
indicating the problem, along with any steps needed to resolve it.
Each logical file system must be checked independently.

Page 7-14

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.
You are about to destroy all files on file system /flash. If you
are experiencing problems with the flash file system, you might
want to use the "fsck" command to help determine where problems
may exist.
Are you absolutely sure you want to strip the current file
system and create a new one? (n)

Press to cancel, or enter y to create a new file system. If you enter y, you will have to
load new software into the switch.
♦ Warning ♦
Do not power-down the switch after running the newfs
command until you reload your image and configuration files. Otherwise, you will have to reload the image
files at the boot monitor prompt using the serial interface (e.g., ZMODEM), which can take several minutes.
Also, before you execute the newfs command, you
may also want to preserve your configuration file by
saving it to another host.
You can now download new files via FTP or ZMODEM.

Page 7-15

Creating a New File System

Page 7-16

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. Press ? to see the following list of commands:
Command
pw
reboot
timeout
layer2auth
seclog
secdefine
secapply
useradd
usermod
userdel
asacfg
userview
auth

Security Menu
Set a new password for a login account
Reboot this system (allowed if the user is “admin”)
Configure Auto Logout Time (obsolete, use “uic” command)
Enable/Disable layer2 user authentication
Display Secure Access log file entries
Define Secure Access filter(s)
Apply Secure Access filter(s)
Create a new user for a login account
Modify a user’s privileges
Remove a user
Configure Authenticated Switch Access
View the users in the local user database
Enter the Authentication menu

Main
File
Interface Security

Summary VLAN
System
Services

Networking
Help

The pw, reboot, seclog, secdefine, and secapply commands are described in this chapter. The
useradd, usermod, userview and userdel commands are also described in this chapter.
For information about the layer2auth and asacfg command as well as the authentication (auth)
submenu, see the Switched Network Services User Manual.

Page 8-1

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. The Diagnostics login has full READ/WRITE access
to all command families plus a command for running switching module tests. The login name
for Diagnostics is diag.
The initial password for all three accounts is switch. If you log in as diag you can change the
passwords for the diag and admin login accounts. If you log in as admin, however, you can
only change the password for the admin login account. To change the password, complete the
following steps. Remember that the User Interface does not echo (display) the password characters.
1. From the prompt, type
pw

The is the user login name (diag, admin) for which you want to change
the password. The following prompt displays:
Changing password for account:
Old password:

2. Enter the old password and press . If you enter the old password incorrectly, the
following message displays:
Authentication failure

and the command will terminate. You will then need to start over from Step 1 above.
If you answered the old password correctly, the following prompt displays:
New password:

3. Enter the new password (you are allowed up to 18 characters) and press . The
following prompt displays:
Retype new:

4. Re-enter the new password to confirm it and press .
♦ Note♦
It is recommended that you change the password from
the default for all login accounts.
The passwords are stored encrypted in the mpm.cnf file. If you forget your password, you will
have to delete the mpm.cnf file which will cause the passwords to revert to the default.
♦ Caution ♦
Deleting the mpm.cnf file will also remove all of your
configuration data and restore everything back to
factory settings.

Page 8-2

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.
To reboot the switch from the command line, enter
reboot

at the prompt and press . The following prompt will display:
Confirm? (n)

Enter Y. The following message displays:
Locking file system...locked
System going down immediately...
switch[489917b0]: System rebooted by admin

The switch will now take at least a minute to start up again. (If you are connected to the User
Interface with a serial connection, the console displays start-up related information.) The login
message displays when the reboot is complete:
Welcome to the Alcatel Omni Switch/Router! (Serial # xxxx)
login :

Page 8-3

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. Whenever any of these
filter points is enabled, all filters configured for that protocol are applied to incoming traffic
using the filter point protocol.
All access violations are logged. If a filtering point is not enabled, it is accessible to all users.

Configuring the Secure Switch Access Filter Database
Use the secdefine command to view and configure the database of secure access filters. This
database includes information on filter names, source IP addresses, source MAC addresses,
and the physical ports receiving data.
The following is a sample secdefine display:
Secure Access Filter Database
List
(l) :
Create (c):
Delete (d):
Modify (m):
Find
(f):
Help
(h):
Quit
(q):
Enter selection:

Select an option by entering the relevant letter at the selection prompt. To exit this menu,
enter q (quit). Descriptions and sample displays for each of the options are as follows:
List
This is a list of all defined filters. A filter determines what traffic is allowed on the switch. The
list includes information on the filter’s name, IP Address, MAC Address, and physical port
receiving the user’s data. The following is a sample display:
Source IP
Source MAC
Slot Port
Filter Name
Address
Address
#
#
--------------------------------------------------------------------------------------------------------Engineering
198.34.56.10
0:23:da:67:97:e4 4
1
Test
ANY
ANY
7
3
Accounting
172.14.25.13
0:32:e4:a3:6f:e4
2
1
HR
198.34.56.15
ANY
ANY ANY

The value ANY displays if a field is left blank when configuring filter information through the
Create (c) option. The ANY value signifies a “don’t care” condition. When an inbound packet is
checked against a Filter Name to establish authorized access, the ANY fields are not checked.

Page 8-4

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. To review your new configuration, simply
select the list (l) option. Descriptions of the fields are as follows:
The name of the new filter. The name is required and must be at least one
character long and no more than 25 characters.
Enter Filter Name:

Enter IP Address ( [a.b.c.d] ): The allowed IP address. The address must be in the displayed
format ( [a.b.c.d] ). If you enter a value here, the user may access the switch only from this IP
address. If you leave this field blank, a value of ANY will display in the secure access list,
allowing access to the switch from any IP address.
Enter MAC Address ( ( [XXYYZZ: AABBCC] )): The allowed MAC address. The address must be in
the displayed format (( [XXYYZZ: AABBCC] ) ). If you enter a value here, a user may access the
switch only from this source MAC address. If you leave this field blank, a value of ANY will
display in the secure access list, allowing this user access to the switch from any MAC address.
Is this MAC in Canonical or Noncanonical (C or N) [C] : The

format of the specified MAC address.
Typically, ethernet MAC addresses are in canonical format while token ring and addresses are
in noncanonical format. The default is canonical (C). This parameter is not required.
Enter Slot:

The module on the switch receiving data from the specified IP or MAC address. If
you leave this field blank, a value of ANY will display in the secure access list, allowing data
from the specified IP or MAC address to be sent through any module on the switch.
Enter Port:

The port on the module receiving data from the specified IP or MAC address. If you
enter a value here, you should also specify a slot in the above field. If you leave this field
blank, a value of ANY will display in the secure access list, allowing data from the specified IP
or MAC address to be sent through any port on the module (if one is specified) or on the
switch (if no slot is specified).
Delete
This option allows you to delete a filter from the secure access list. The screen displays similar to the following:
Delete Filter
-----------------Enter Filter Name:

If you enter a filter name here, that filter will be immediately deleted from the secure access
database.

Page 8-5

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.d] ) :
Enter MAC Address ( [XXYYZZ: AABBCC] ) :
Is this MAC in Canonical or Non-Canonical (C or N) [C] :
Enter Slot :
Enter Port :

To change a value, type in the new value at the prompt. If you do not wish to modify a
particular field, press Enter and the existing user information will remain unchanged. To
change a field to ANY privilege, enter a value of 0, an asterisk (*), or ANY at the prompt.
Descriptions of the fields in the above display are provided earlier under the option ‘‘List’’ on
page 8-4.
Find
This option allows you to find information about a specified filter in the secured access database. You must know the filter’s name in order to use this search feature. The following is a
sample display:
Find Filter
-------------Filter Name: Test

To find a filter in the database, enter the name of the filter at the prompt. If the filter you
enter is a valid one, information on that filter will display similar to the following:
Source IP
Source MAC
Slot
Port
Filter Name
Address
Address
#
#
----------------------------------------------------------------------------------------------------------Test
ANY
10.2.8.13
5
2

Page 8-6

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. To use this command, enter:
secapply

A screen similar to the following displays:
Secure Access Filter Points
1) FTP Security
11) Filter List
2) Telnet Security
21) Filter List
3) SNMP Security
31) Filter List
4) TFTP Security
41) Filter List
5) HTTP Security
51) Filter List
6) Custom Security
61) Filter List
62) Protocol
63) Port Service
7) One-touch Global Security :
71) One-touch Filter List

: Enabled
: Test, Engineering
: Disabled
: Test
: Enabled
:
: Enabled
: Manufacturing
: Disabled
:
: Enabled
: HR
:
:
:

Command { Item=Value/?/Help?Quit/Redraw/Save}

(Redraw)

♦ Note ♦
If security is enabled for a filter point and there are no
names defined on its list, then the filter point is essentially inaccessible to all users. For example, in the
above sample display, SNMP is not accessible to any
user.
You can enter commands by entering just the first letter of the command. For example, select
by entering q and pressing .The question mark option (?) and the Help option
provide reference and instructional information on using this command. The Quit option exits
this command without saving configuration changes. The Redraw option refreshes the screen.
Quit

When you are done entering new values, type save at the prompt and all new settings will be
saved.
The following option is available for all filter points:
Filter List
Applies the filter name(s) defined through the secdefine command for this filter point.
Filter points are disabled by default. The different filter points are defined as follows:

Page 8-7

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. Enabled
means secure access is enabled, and only filters on Telnet’s filter list have authorization.
Disabled indicates that secure access is not enabled for Telnet service, and all users can access
the switch through Telnet.
3) SNMP Security
Indicates whether or not security is enabled for Simple Network Management Protocol (SNMP)
on the switch. Enabled means security is enabled for SNMP services, and only filters on SNMP’s
filter list are authorized. Disabled indicates that secure access is not enabled for SNMP services,
and all users can access the switch through SNMP.
4) TFTP Security
Indicates whether or not security is enabled for Trivial File Transfer Protocol on the switch.
means security is enabled for TFTP services, and only users on TFTP’s filter list are
authorized. Disabled indicates that security is not enabled for TFTP services, and all users can
access the switch through TFTP.
Enabled

5) HTTP Security
Indicates whether or not security is enabled for HyperText Transfer Protocol (HTTP) on the
switch. Enabled means that security is enabled for HTTP, and only filters on HTTP’s filter list
are authorized. Disabled indicates that security is not enabled for HTTP, and all users can
access the switch through HTTP.
6) Custom Security
Configures whether or not security is enabled for the custom IP protocol specified in line 62.
Enabled means that security is enabled for the custom IP protocol, and only filters on that
protocol’s filter list are authorized. Disabled indicates that security is not enabled for the
custom IP protocol, allowing all users access to the switch through that protocol.
62) Protocol
(Available for Custom Security only.) The IP protocol number to be included as a secured
access protocol (IP protocol field in the IP header). You may define only one custom IP
protocol.
63) Port Service
(Available for Custom Security only.) The Custom IP protocol’s destination port (port field
in the IP header)

Page 8-8

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.
71) One-touch Filter List
Configures a single filter list for all security filter points.

Enabling/Disabling Security Parameters
To change any of the Security values, enter the line number for the parameter, followed by an
equal sign (=), and then enabled or e for enable or disabled or d for disable at the prompt. For
example, to enable security for Telnet, enter the following:
2=e

Adding Filters
To add a filter, at the command prompt, enter the line number for the parameter, followed by
an equal sign (=), and then the filter’s name at the prompt. For example:
21=Test

♦ Note ♦
If the filter does not exist in the secure access database, the system prompts you to create the filter. To
view the list of secure access filters, use the secdefine
command. For more information, see ‘‘Configuring the
Secure Switch Access Filter Database’’ on page 8-4.
Enter save to save the new filter.

Deleting Filters
To remove an existing filter from a filter list, at the command prompt, enter the line number
for the parameter, followed by an equal sign (=), a negative sign (-), and then the filter’s name
as follows:
11= -Engineering

To remove all filters in a list, include an asterisk after the negative sign. For example:
4= -*

Enter save to save the change.

Page 8-9

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.801
198.20.2.101

Attempts
-------------1
10

Slot/
Intf
------5/1
2/3

Elapsed Time
(secs)
------------------23
240

Descriptions of the fields are as follows:
Time.

The first time the access violation occurred.

Protocol.

The IP protocol for which the violation occurred.

Source IP.

The source IP address of the unauthorized user.

Attempts. The number of access attempts made by this user within the sample period (5
minutes).
Slot/Intf.

The physical port that received the unauthorized user information.

Elapsed Time (secs).

The duration (in seconds) from the first unauthorized access to the end of
the sampling period. Secure access violations will take 5 minutes to display in the log file.

Page 8-10

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.
The purpose of partition management is to provide a mechanism in the switch operating
system for system administrators to control access while maintaining enough flexibility to use
the switch’s full range of services. This is normally done for security reasons. System administrators can partition access to the switch by restricting a user’s ability to perform certain switch
commands or to use certain command groups.
♦ Terminology Notes♦
A user account refers to the user’s ability to log onto
the switch and perform certain functions. From the
user’s perspective, it consists of the login name and a
password.
A privilege refers to the user’s ability or permission from
the system administrator to execute a command.

Partition Management Requirements
Partition management is available only for user login accounts that have no permission to use
the UI command mode. Where a user account has permission to use the UI mode, partition
management is effectively destroyed for that user account. To maintain partition management
capability for a user account, that account must be restricted to using the CLI mode only.
Refer to ‘‘Assigning Account Privileges Using the UI Command Mode’’ on page 8-16 or
‘‘Assigning Account Privileges Using the CLI Command Mode’’ on page 8-13 for information
on restricting use UI commands.
♦ Note♦
Not all UI commands have CLI equivalents. Also, not all
CLI commands support partition management. For
detailed information, refer to the UI to CLI Cross Reference Tables in Chapter 4 of this manual.

Page 8-11

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.
♦ Note♦
At least one user account with WRITE privileges to use
the USER family of commands is required on the switch
at all times. If you attempt to remove or modify the
only user account to READ-ONLY privilege, the switch
will reject the modification command.
There are several commands available for modifying the user login accounts on the switch.
To see a list of all user accounts currently available on the switch, use the userview command
in the UI mode.

Adding a User Account Using the UI Command Mode
To add a user account you must be logged into an account with administrative privileges.
1. At the system prompt enter the

useradd

command. The following prompt displays:

Enter Username: ( ) :

2. Enter the desired user name. The following prompt displays:
Force Password change on next login [y/n] ? (y) :

3. Press to force a password change at the next login for this user, or enter n to keep
the configured password. The following prompt displays:
Enter password: ( ) :

4. Enter the desired password. The following prompt displays:
Enter new password again: ( ) :

5. Enter the desired password again. In this example, the username “TechPubs1” is entered.
A message similar to the following displays:
User TechPubs1 user privileges (0:0:0) :

The user login account “TechPubs1” is now active on the switch.
At this point the new account has permission to log onto and off of the switch. To add
other privileges refer to ‘‘Assigning Account Privileges Using the UI Command Mode’’ on
page 8-16 or to ‘‘Assigning Account Privileges Using the CLI Command Mode’’ on page 813.

Page 8-12

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. For the user name
“Techpubs1”, the following message is displayed:
User Techpubs1 created.

If you do not specify a password when you create the new account, switch becomes the
default password.
♦ Note♦
It is recommended that you change the password from
the default for all login accounts.
Both the user account name and the password are limited to 16 text characters. The new
login account and password will take effect at the user’s next login session.

Assigning Account Privileges Using the CLI Command Mode
A user account’s READ and WRITE privileges can be assigned for all commands or for various
subsets of commands. The command subsets referred to as command families are shown
here:
config, vlan, iprout, ipxrout, bridge, snmp, xswitch, hrefilter, atmser, atmup, cem, csm, pnni, atmacct,
voip, mpoa, mpls and user.

In addition to assigning privileges according to command families, an administrator can
restrict the user account’s ability to execute specific commands. Here is a list of commands
that can be restricted from a user account.
system, status, slot, timeout, prompt, define, prefix, reboot, telnet, ftp, ping, swap, reset, cd, ls, rm, file,
interface, ethernet, gated, and ui.

♦ Warning♦
If partition management is intended for a user account,
that account cannot have permission to use the UI
command or the UI mode.

Page 8-13

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. The list-of-families parameter indicates the switch command families and the specific commands for which the user account will receive READ and WRITE privileges. Command families must be separated by commas.
User Read Privileges
To assign READ-ONLY 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 [read list-of-families]

where userId indicates the name assigned to the new login account for which you want to
assign READ-ONLY privileges. The list-of-families parameter indicates the switch command
families and the specific commands for which the user account will receive READ-ONLY privileges. For a list of command families and specific commands, refer to the ‘‘Assigning Account
Privileges Using the UI Command Mode’’ section on page 8-16 or to ‘‘Adding a User Account
Using the CLI Command Mode’’ on page 8-13.
Removing Privileges
You can remove READ and WRITE privileges from a user created login account if you are
logged into an account with WRITE privileges to the USER command family. Use the following command:
user userId no write list-of-families

You can remove READ-ONLY privileges from a user created login account by using the following command:
user userId no read list-of-families

For both these commands, the userId parameter indicates the name assigned to the user
created login account for which you want to remove privileges. The list-of-families parameter
indicates the switch command families and the specific commands from which you want to
remove READ or WRITE privileges.

Page 8-14

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.
• To set or change the password of the current user account, use the following command:
password password

Where password is the new password for this user account.
• To delete a login account, use the following command:
no user user_name

where user_name is the current login you want to delete.
• To view user privileges for a specific user login account, use the following command:
view user [user_name]

where user_name is the name of the user login account for which you will view privileges.

Page 8-15

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. The following prompt
displays:
Enter Username : ( ) :

Enter the login name of the user account you are modifying. The following screen will
display.
- CONFIG
: NO
- GROUP
: NO
- IPROUT
: NO
- IPXROUT
: NO
- BRIDGE
: NO
- SNMP
: NO
- XSWITCH
: NO
- HREFILTER
: NO
- ATMSER
: NO
- ATMUP
: NO
- CEM
: NO
- CSM
: NO
- PNNI
: NO
- ATMACCT
: NO
- VOIP
: NO
- MPOA
: NO
- MPLS
: NO
- USER
: NO
Subsets of the global family:
- SYSTEM
: NO
- STATUS
: NO
- SLOT
: NO
- TIMEOUT
: NO
- PROMPT
: NO
- DEFINE
: NO
- PREFIX
: NO
- REBOOT
: NO
- TELNET
: NO
- FTP
: NO
- PING
: NO
- SWAP
: NO
- RESET
: NO
- CD
: NO
- LS
: NO
- FM
: NO
- FILE
: NO
- INTERFACE
: NO
- ETHERNET
: NO
- GATED
: NO
- UI
: NO
1. MODIFY ONE FAMILY RIGHTS
2. SET ALL READ RIGHTS
3. SET ALL WRITE RIGHTS
4. SET NO READ RIGHTS
5. SET NO WRITE RIGHTS
6. MODIFY ONE GLOBAL SUBSET
7. SET NO GLOBAL SUBSET
8. SET ALL GLOBAL SUBSET
[ 1 TO 8, (c)ancel or (s)sav] ( ) :

Page 8-16

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 . The display will prompt you for the
family number as shown here:
Give the family number : ( ) :

Enter the number of the command family for which you want to set WRITE privileges. Refer to
the ‘‘Command Family Table’’ on page 8-18 for the number.
For example, if you wanted to enable WRITE privileges for the Bridge command family, enter
the number 5 as shown here.
Give the family number : ( ) : 5

The following will display.
Give rights on family BRIDGE
0.
NO
1.
READ
2.
WRITE
3.
READ&WRITE
():

Enter the number 2 at the prompt to assign WRITE privileges. The following shows a portion
of the display.
User ‘TechPubs1’ user privileges (0:0X20:0) :
- CONFIG
: NO
- GROUP
: NO
- IPROUT
: NO
- IPXROUT
: NO
- BRIDGE
: READ & WRITE
- SNMP
: NO
- XSWITCH
: NO
(Continued)

The privilege listed next to Bridge shows WRITE. This indicates that the user ‘‘TechPubs1’’
now has WRITE privileges for the Bridge family of commands.

Page 8-17

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. Privileges for global family commands can be set on an individual command basis or altogether so the privilege applies to the whole global family. If you
want to set privileges for the global commands, you must enter 6, 7 or 8 when the screen
prompt displays the following:
1. MODIFY ONE FAMILY RIGHTS
2. SET ALL READ RIGHTS
3. SET ALL WRITE RIGHTS
4. SET NO READ RIGHTS
5. SET NO WRITE RIGHTS
6. MODIFY ONE GLOBAL SUBSET
7. SET NO GLOBAL SUBSET
8. SET ALL GLOBAL SUBSET
[ 1 TO 8, (c)ancel or (s)save] ( ) :

To give the user account the privilege to set all global commands, enter the numeral 8. To
deny the user the privilege to set any of the global commands, enter the numeral 7. To set
individual global commands, enter the number 6. If you are assigning privileges on an individual command basis the display will look like this:
[ 1 TO 8, (c)ancel or (s)sav] ( ) : 6
Give the subset number : ( ) :

Enter the number of the command for which you want to set WRITE privileges. Refer to the
‘‘Global Family Table’’ on page 8-19 for the number.

Page 8-18

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.
YES
():

If you enter 1, all the command families will display and the DEFINE command under the
global family will be shown as follows:
- DEFINE

: YES

After you set the user account privileges, the switch displays the current configuration. At this
point you may enter s to save your configuration or c to cancel.
♦ Warning♦
If partition management is implemented on a user
account, that account must have the UI command
family set to NO privilege. If an account has the privilege to use the UI command, partition management is
effectively destroyed for that account.

Page 8-19

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.
User ‘TechPubs1’ is configured with the following privileges:
READ
1. READ
2. WRITE
3. ADMIN
4. FORCE new password
Select the privilege(s) number to add/remove.
[ 1, 2, 3 (c)ancel or (s)ave] (c) :

♦ Note ♦
See ‘‘Managing User Login Accounts’’ on page 8-11 for
definitions of the privileges.
3. Enter the number for the privilege you want to add or remove. The entry acts as a toggle
to turn the privilege on or off for the user. In the current example, if you enter 2 at the
prompt, a screen similar to the following displays:
User ‘TechPubs1’ is configured with the following privileges:
READ
WRITE

4. After modifying the privileges for the user, enter s at the selection prompt to save the
change(s).

Deleting a User
To delete a user from the user database, you must be logged into an account with administrative privileges.
1. At the system prompt, enter the userdel command. The following prompt displays:
Enter Username to remove: ( ) :

2. Enter the username for the user you want to delete. A message similar to the following
displays:
User ‘TechPubs1’ was removed.

♦ Note ♦
All users but one may be deleted from the switch,
provided that the one remaining user is configured with
all privileges.

Page 8-20

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.
In addition, this chapter contains documentation for configuring HRE-X ports (described in
Configuring the HRE-X Router Port on page 9-27) duplicate MAC address support (described
in Duplicate MAC Address Support on page 9-30), multicast claiming (described in Multicast
Claiming on page 9-32), disabling flood limits (described in Disabling Flood Limits on page 932), and saving configurations (described in Saving Configurations on page 9-33).

Summary Menu
The Summary menu consists of commands for displaying summary switch information. To
access this menu, enter
summary

at the UI prompt. Type the question mark (?) to see the following list of commands.
Command
ss
sc
si

Summary Menu
Display MIB-II System group variables
Display a summary of the chassis (type, id, serial no., base mac, etc.)
Current interface status

Main
File
Interface Security

Summary VLAN
System
Services

Networking
Help

The Summary menu commands are described in the sections that follow.

Page 9-1

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.
Agent Up Time:
5 days, 00:28:14.38
Contact:
Administrator
Name:
TechWrite
Location:
Bldg 46
Device Services:
DataLink/Subnetwork Layer
Internetwork Layer
Host Layernetwork Layer
Application Layer (Rlogin, Telnet, FTP)

The fields displayed by the ss command are described below.
System description.

The specific type of chassis, which can be an OmniSwitch, OmniAccess, or
Omni Switch/Router. This field is set by the syscfg command, which is described in Configuring System Information on page 9-23.
System Object ID. The MIB entry for the switch (where the object ID starts). This is read only.
This value helps you locate Alcatel-specific variables in the MIB tree.
Agent Up Time.

The time (in days, hours, minutes, and seconds) since the switch was re-initial-

ized.
Contact.

The name of a person to contact about this switch. This field is set by the syscfg
command, which is described in Configuring System Information on page 9-23.

Name.

The name the system administrator assigned to this switch (the node’s fully qualified
domain name, by convention). This field is set by the syscfg command, which is described in
Configuring System Information on page 9-23.

Location. The physical location of the switch. This field is set by the syscfg command, which
is described in Configuring System Information on page 9-23.
Device Services.

The type of services provided by the switch. Supported service types are

listed below:
• Data Link /Subnetwork Layer
• Internetwork Layer
• Host Layer
• Application Layer (Rlogin Telnet, FTP)

Page 9-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.

The description of the specific type of chassis or device.

Chassis ID.

The chassis ID for this switch.

Description.

The description of this chassis. This field is set by the syscfg command, which is
described in Configuring System Information on page 9-23.

Backplane.

The style of backplane in this chassis.

Master MPM Serial No.
Physical Changes.

The serial number for the primary MPX.

The number of physical changes that has occurred since the last reset or

power-on.
Logical Changes.

The number of logical changes that has occurred since the last reset or

power-on.
Number of Resets. The number
(mpm.cnf) was first removed.
Base MAC Address.
Free Slots.

of times this switch has been reset since the configuration file

The base MAC address for the primary MPX.

The number of front panel slots not occupied by a switching module.

Page 9-3

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.
Interface Summary Status
4 Interfaces
Logical
Interface
-------------1
2
3
4

Interface
Type
---------------------------Slip
Virtual Router
Virtual Router
SoftwareLoopback

Administrative
Status
----------------------Enabled
Enabled
Enabled
Enabled

Operational
Status
--------------------Enabled
Active
Active
Enabled

The fields displayed by the si command are described below.
Logical Interface.
Interface Type.

A number, in sequence, that has been assigned to the virtual router port.

The type of interface, which can be virtual router (the standard interface type),

SLIP, and software loopback.
Administrative Status. Whether the administrator has enabled or disabled the port. The port can
be enabled by the administrator but still be made inactive by the system.
Operational Status.

system software.

Page 9-4

Whether the port is active (operational) or inactive. This status is set by the

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.
Command
info
dt
ser
mpm
slot
systat
taskstat
taskshow
memstat
fsck
newfs
syscfg
uic
camstat
camcfg
hrex
ver/ter
echo/noecho
chpr
logging
health
cli
saveconfig
cacheconfig

System Menu
Basic info on this system
Set system date and time
View or configure the DTE or DCE port
Configure a Management Processor Module
View Slot Table information
View system stats related to system, power and environment
View task utilization stats
View detailed task information
View memory use statistics
Perform a file system check on the flash file system
Erase all file from /flash and create a new file system
View/Configure info related to this system
UI configuration; change - prompt, timeout, more, verbose.
View CAM info and usage
Configure CAM info and usage
Enter HRE-X management command sub-menu
Enables/disables automatic display of menus on entry (obsolete)
Enable/disable character echo
Change the prompt for the system (obsolete, use ‘uic’ command
View system logs.
Set health parameters or view health statistics
Enter command line interface
Dump the cache configuration content to the mpm.cnf file.
Set the flag to use cache configuration only.

Main
File
Interface Security

Summary VLAN
System
Services

Networking
Help

All of the System menu commands—except for the mpm, ver, ter, echo, noecho, chpr, logging,
health, and cli commands—are described in the following sections. The uic, ver/ter, echo,
noecho, chpr, and cli commands are described in Chapter 4, “The User Interface.” The mpm
command is described in Chapter 6, “Configuring Management Processor Modules.”
♦ Note ♦
The ver, ter, and chpr commands now appear as items
in the UI Configuration menu (displayed through the
uic command). If you enter the ver/ter and chpr
commands, a message will advise you to use the uic
command, and the UI Configuration menu will automatically display. For more information on the UI
Configuration menu, refer to Chapter 4, “The User
Interface.”

Page 9-5

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.
Backplane: 9 SLOT

Bus Speed: 1200 XFRAME

Physical changes to the system since power-up or reset:
Logical changes to the system since power-up or reset:
Number of Resets to this system:

2
0
8

The attached MPM, slot 1, is the Primary
Automatic configuration synchronization is enabled
System base MAC Address:
Number of Free Slots:
Action on Cold Start:
Action on Reset:

00:20:da:04:21:f0
0
Load & go
Restart

VBus Mode :

Mode 1

Script File:
Boot File:
Ni Image Suffix:

/flash/mpx.cmd
/flash/mpx.img
img

The fields displayed by the info command are described below.
System Make.

The description of the specific type of chassis or device.

System Type.

The OmniSwitch type.

Description.

A description of the chassis and product. This field is set by the syscfg command,
which is described in Configuring System Information on page 9-23.

Backplane.

The style of backplane used in this chassis.

Bus Speed.

The speed of backplane, in Mbs, used in this chassis.

Physical Changes to the system since power-up or reset.

The number of physical changes that has

occurred since the last reset or power-on.
Logical Changes to the system since power-up or reset.

occurred since the last reset or power-on.

Page 9-6

The number of logical changes that has

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. See Chapter 6, “Configuring
Management Processor Modules,” for more information
on redundant MPXs and automatic configuration
synchronization.
System Base MAC Address.
Number of Free Slots.
Action on Cold Start.
Action on Reset.

The base MAC address for the primary MPX in chassis.

The number of slots not occupied by a module.

The action taken when you switch the power on.

The action taken when you reboot.

Script File. The name of the command file (mpx.cmd is the default) containing user-configurable commands.
Boot File.

The boot file (mpx.img is the default) used by the switch when it boots up or

reboots.
Ni Image Suffix. The name of the file extension (img is the default) indicating that the file is an
executable binary file. See Chapter 6, “Configuring Management Processor Modules,” to
change this suffix.

Page 9-7

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. This command displays a screen similar to the following:
Modify Date and Time Configuration
1) Local time
2) Local date
3) Timezone (-13 . . 12, name)
4) Daylight Savings Time active
{Item=Value/?/Help/Quit/Redraw/Save}

: 1:45:41
:01/15/01
: MST UTC-7 hrs
: DisabledCommand
(Redraw)

To use the dt command, you must have UI write privileges. Enter the line number for the variable that you would like to change, an equal sign (= ), and then the new value for the variable. For example, to set a new date, you would enter:
2=4/20/99

After you have made changes, enter
save

to save your changes and to exit the dt menu. If you do not wish to make any changes, enter
quit

at the system prompt. The following sections describe the variables on this screen.
1) Local time
Indicates the current and local time. To set the time, enter the line number for Local Time (1)
followed by the new time. The time format is as follows:
HH:MM:SS

where HH is the hour to be set based on a 24 hour (military) clock, MM is the minutes to be
set, and SS is the seconds to be set. For example, if you wanted to set the time to 3:15 p.m.,
you would enter:
1=15:15:00

2) Local date
The current and local date. To set the date, enter the line number for Local Date (2) followed
by the new date. The date format is as follows:
MM/DD/YY

where MM is the month to be set, DD is the day to be set, and YY is the last two digits of the
year to be set. Remember to include a slash (/) between the month and the day and between
the day and the year. For example, if you wanted to set the date to January 15, 2001, you
would enter:
2=01/15/01

Page 9-8

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. To set the time zone for the switch, you may use one
of two methods:
a. Enter the line number for Timezone (3) followed by the hour(s) offset from UTC. This can
be a number from -13 to +12. The number you enter will set the system clock x hours from
the local time. For example, if the local time, 1:45:00, is seven hours behind UTC time, you
would enter:
3=-7

This specification sets the UTC time to 8:45:00, seven hours ahead of the local time, 1:45:00.
b. Enter the line number for Timezone (3) followed by the time zone name. There is a limited
number of time zone names available. For example, if the local time zone name is Mountain Standard Time (MST), you would enter:
3=MST

This specification automatically sets the switch to -7 hours, the number of hours MST is offset
from UTC.
Daylight Savings Time. The

software will automatically configure DST values for a specified time
zone. However, the user can manually modify DST values.

Non-integer Offsets. Non-integer

offsets are acceptable for Timezone. Some parts of the world
are offset from UTC by increments of 15, 30, or 45 minutes. India, for example, is offset from
UTC by 5 hours and 30 minutes. If you wanted to enter the time zone offset for India, for
example, you would type the line number for Timezone (3), followed by the non-integer
hour offset in the HH:MM format, as follows:
3=05:30

where the value of 05:30 is five hours and thirty minutes offset from UTC.
♦ Note ♦
The switch automatically enables UTC. However, if you
do not want your system clock to run on UTC, simply
enter the offset +0 for the Timezone parameter. This sets
UTC to run on local time.
The table on the following page lists the options available for Timezone names:

Page 9-9

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

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

ACST

Australia
Central Time

+9:30

Last Sunday in
Oct. at 2:00 a.m.

Last Sunday in
March at 3:00 a.m.

1:00

JST

Japan

+9:00

No default

KST

Korea

+9:00

No default

AWST

Australia
West Time

+8:00

No default

ZP8

China,
Manila,
Philippines

+8:00

No default

ZP7

Bangkok

+7:00

No default

ZP6

No standard
name

+6:00

No default

ZP5

No standard
name

+5:00

No default

ZP4

No standard
name

+4:00

No default

MSK

Moscow

+3:00

Last Sunday in
March at 2:00 a.m.

Last Sunday in
Oct. at 3:00 a.m.