Alcatel-Lucent OMNISWITCH 8800 Users Guide

OmniSwitch

Getting Started Guide

®

8800

060182-10, Rev. D
March 2005

Warning. Only personnel knowledgeable in basic electrical and mechanical procedures should install or maintain this
equipment.

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.

The features and specifications described in this guide are 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
Alcatel OmniVista

OmniAccess™, Omni Switch/Router™, PolicyView™, RouterView™, SwitchManager™, VoiceView™, WebView™,
X-Cell™, X-Vision™, and the Xylan logo are trademarks of Alcatel Internetworking, Inc.

This OmniSwitch product contains components which may be covered by one or more of the following U.S. Patents:

and the Alcatel logo are registered trademarks of Alcatel. Xylan®, OmniSwitch®, OmniStack®, and

®

are registered trademarks of Alcatel Internetworking, Inc.

• U.S. Patent No. 6,339,830

• U.S. Patent No. 6,070,243

• U.S. Patent No. 6,061,368

• U.S. Patent No. 5,394,402

• U.S. Patent No. 6,047,024

• U.S. Patent No. 6,314,106

• U.S. Patent No. 6,542,507

[phone] FAX [phone]

Alcatel Internetworking

26801 West Agoura Road

Calabasas, CA 91301

US Customer Support: [phone]

International Customer Support: [phone]

Internet: http://eservice.ind.alcatel.com

Table of Contents

OmniSwitch 8800. . . . . . . . . . . . . . . . . . . . . . . . 1

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Hardware Features . . . . . . . . . . . . . . . . . . . . . . . 1

Availability Features . . . . . . . . . . . . . . . . . . . . . . 2

Installing the Hardware . . . . . . . . . . . . . . . 3

Items Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Environmental Requirements . . . . . . . . . . . . . . . 3

Electrical Requirements . . . . . . . . . . . . . . . . . . . 3

Weight Considerations . . . . . . . . . . . . . . . . . . . . 4

Items Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Unpacking and Installing the Switch . . . . . . . . . . . . 5

Unpacking the Chassis . . . . . . . . . . . . . . . . . . . . 5

Recommendations . . . . . . . . . . . . . . . . . . . . 5

Chassis Removal Instructions . . . . . . . . . . . 5

Power Supply Removal Instructions . . . . . . 6

Lifting the Chassis . . . . . . . . . . . . . . . . . . . . . . . 7

Mounting the Switch . . . . . . . . . . . . . . . . . . . . . 7

Airflow Considerations . . . . . . . . . . . . . . . . 7

Module Access Considerations . . . . . . . . . . 8

Rack-Mounting . . . . . . . . . . . . . . . . . . . . . . 8

Stand-Alone . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing Power Supplies . . . . . . . . . . . . . . . . . 10

Using the Grounding Wrist Strap and Chassis

Grounding Lug . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing the Network Interface (NI) and

Chassis Management Modules (CMMs) . . . . . .13

NI Modules . . . . . . . . . . . . . . . . . . . . . . . . .13

CMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installing MiniGBIC Connectors . . . . . . . . . . .16

Installing Xenpak Modules . . . . . . . . . . . . . . . .17

Installing SFMs . . . . . . . . . . . . . . . . . . . . . . . . .18

Blank Cover Plates . . . . . . . . . . . . . . . . . . . . . .19

Connections and Cabling . . . . . . . . . . . . . 20

Serial Connection to the Console/Modem

Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Serial Connection Default Settings . . . . . .20

EMP Cable Requirements . . . . . . . . . . . . . . . . .21

Booting the Switch . . . . . . . . . . . . . . . . . . . . . . 22

Component LEDs . . . . . . . . . . . . . . . . . . . . . . .22

Your First Login Session . . . . . . . . . . . . . . . 23

Logging In to the Switch . . . . . . . . . . . . . . . . . . . . . 23

Setting IP Address Information for the EMP . . . . . 24

Unlocking Session Types . . . . . . . . . . . . . . . . . . . . 25

Unlocking All Session Types . . . . . . . . . . .25

Unlocking Specified Session Types . . . . . .25

How many sessions are allowed? . . . . . . . .26

Changing the Login Password . . . . . . . . . . . . . . . . 26

Setting the System Time Zone . . . . . . . . . . . . . . . . 27

March 2005 iii

Setting the Date and Time . . . . . . . . . . . . . . . . . . . 27

Setting Optional System

Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Specifying an Administrative Contact . . . . . . . 28

Specifying a System Name . . . . . . . . . . . . . . . . 28

Specifying the Switch’s Location . . . . . . . . . . . 28

Viewing Your Changes . . . . . . . . . . . . . . . . . . . . . 29

Saving Your Changes . . . . . . . . . . . . . . . . . . . . . . . 29

Modifying the Serial Connection Settings . . . . . . . 29

CLI Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CLI Assistance Features . . . . . . . . . . . . . . . . . . . . . 31

Syntax Checking . . . . . . . . . . . . . . . . . . . . . . . . 31

Command Line (?) Help . . . . . . . . . . . . . . . . . . 32

Partial Keyword Completion . . . . . . . . . . . . . . 32

Deleting Characters . . . . . . . . . . . . . . . . . . . . . 32

Inserting Characters . . . . . . . . . . . . . . . . . . . . . 33

Previous Command Recall . . . . . . . . . . . . . . . . 33

Prefix Recognition . . . . . . . . . . . . . . . . . . . . . . 33

Prefix Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Command History . . . . . . . . . . . . . . . . . . . . . . . 34

Command Logging . . . . . . . . . . . . . . . . . . . . . . 35

Enabling Command Logging . . . . . . . . . . . 35

Common CLI Commands . . . . . . . . . . . . . . . . . . . . 36

Offline Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Syntax Checking . . . . . . . . . . . . . . . . . . . . . . . . 37

Scheduling a Configuration File to be Applied

at a Later Time . . . . . . . . . . . . . . . . . . . . . . . . . 37

Generating Snapshots of the

Current Configuration . . . . . . . . . . . . . . . . . . . . . . 37

Files and Directories . . . . . . . . . . . . . . . . . . . . 38

Boot and Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

boot.params File . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

boot.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Working and Certified Directories . . . . . . . . . . . . . . . . 40

Working Directory . . . . . . . . . . . . . . . . . . .40

Certified Directory . . . . . . . . . . . . . . . . . . .40

How can I tell which directory the switch is

currently using? . . . . . . . . . . . . . . . . . . . . .41

Can I save changes to the Certified

directory? . . . . . . . . . . . . . . . . . . . . . . . . . .41

What happens when the switch boots? . . . .41

Working and Certified Are Identical . . . . .41

Working and Certified Are Different . . . . .42

My Working and Certified directories are

different. Can I force a reboot from the

Working directory? . . . . . . . . . . . . . . . . . .42

Loading Software . . . . . . . . . . . . . . . . . . . . . . . 43

Non-Redundant Configurations . . . . . . . . . . . . . . . 43

Redundant Configurations . . . . . . . . . . . . . . . . . . . 44

Using WebView. . . . . . . . . . . . . . . . . . . . . . . . . . 46

Browser Compatibility . . . . . . . . . . . . . . . . . . . . . . 46

Required Image Files . . . . . . . . . . . . . . . . . . . . . . . 46

Logging In to WebView . . . . . . . . . . . . . . . . . . . . . 47

Navigating WebView . . . . . . . . . . . . . . . . . . . . . . . 47

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Additional Information . . . . . . . . . . . . . . . . . . . . . . 49

iv March 2005

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

The WebView login screen does not

display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

The login screen displays, but my login

attempt fails. . . . . . . . . . . . . . . . . . . . . . . . 49

Hardware Basics . . . . . . . . . . . . . . . . . . . . . . . . 50

Chassis Slot Numbering . . . . . . . . . . . . . . . . . . . . . 50

Chassis Management Module (CMM) . . . . . . . . . . . . . 51

CMM Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . 52

CMM Slot Locations . . . . . . . . . . . . . . . . . . . . . . . 52

CMM Front Panel . . . . . . . . . . . . . . . . . . . . . . . 53

Switch Fabric Module (SFM) . . . . . . . . . . . . . . . . . . . . 54

SFM Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . 54

SFM Slot Locations . . . . . . . . . . . . . . . . . . . . . . . . 54

SFM Front Panel . . . . . . . . . . . . . . . . . . . . . . . . 55

Network Interface (NI) Modules . . . . . . . . . . . . . . . . . . 56

ENI Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

GNI Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Miniature Gigabit Interface Converters

(MiniGBICs) . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

10GNI Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Xenpaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

OS8-ENI-C24 Front Panel . . . . . . . . . . . . . . . . . . . 58

OS8-GNI-U8 Front Panel . . . . . . . . . . . . . . . . . . . . 59

OS8-GNI-C8 Front Panel . . . . . . . . . . . . . . . . . . . . 60

OS8-GNI-U24 Front Panel . . . . . . . . . . . . . . . . . . 61

OS8-GNI-C24 Front Panel . . . . . . . . . . . . . . . . . . . 62

OS8-10GNI-UR1 Front Panel . . . . . . . . . . . . . . . . 63

User Documentation on CD. . . . . . . . . . . 64

General Information . . . . . . . . . . . . . . . . . . . . . . . . 65

March 2005 v

vi March 2005

OmniSwitch 8800

Features

Alcatel’s OmniSwitch 8800 switches offer high performance
10/100 Ethernet and Gigabit Ethernet capabilities, as well as
embedded server load balancing for enterprise requirements.

Both half-duplex and full-duplex modes are supported on all
10/100 Ethernet ports; full-duplex mode is supported on
Gigabit Ethernet and 10 Gigabit Ethernet ports.

Hardware Features

The OmniSwitch 8800 is an 18-slot switch designed for the
medium enterprise core or large wiring closet. The
OmniSwitch 8800 offers up to 384 10/100 Ethernet ports, up
to 384 Gigabit Ethernet ports, or up to 16 10 Gigabit Ethernet
ports for use as a core switch.

The OmniSwitch 8800 chassis contains the following major
components:

• 16 Network Interface (NI) module slots

• Two Chassis Management Module (CMM) slots

• Five Switch Fabric Module (SFM) slots

• Two chassis (front) fan trays

• One fabric (rear) fan tray

• Power supply slot holding up to four power supplies

OS-ENI-C24

O
K
1

OS-ENI-C24

O
K
2

2

O
K
1

OS-ENI-C24

O
K
2

2

1

O
K
1

OS-ENI-C24

O
K
2

3

2

1

O
K
1

5

OS8800-CMM

O
K
2

3

2

1

7

O
K
1

5

OS-ENI-C24

O
K
2

3

9

1

7

O
K

1

5

1

1

1
2

1

9

4

1

1

1
2

1
4

1
3

1
2

1
5

1

4
1
3

1
7

1
5

1
9

1
7

2
1

1
9

2

3
2
4

2
1

2

3
2
4

2
4

OS-GNI-C8

O
K
1

OS-GNI-C8

O
K
2

A

O

C

K

T

1

L

O

IN

K

K

2

A
C

1

T

A

L

O

IN

C

K

T

1

K

L

O

I

A

N

K

C

K

2

2

T

A

L
I

C

N

1

T

K

A

L
I

C

A

N

T

C

K

3

T

L
I

A

L

N

IN

C

K

2

T

K

A

L
I

C

N

1

T

K

4

L
I

A

N

C

K

3

T

A

L
I

C

N

2

T

K

L
I
N

K

4

A
C

3
T

L
I
N

K

A

4

C
T

L
IN
K

A
C

5

T

A

L
IN

C
T

K

L

IN
A
C

K

6

T

A

L
IN

C

5

T
K

A

L

IN

C

A

T

C

K

7

T

L
I

A

L

N

I

C

K

N

6

T
K

A

L

IN

C

5

T

K

8

L

IN
A
C

K

7

T

A

L
IN

C

6

T
K

L

IN

K

8

A

C

7
T

L
IN
K

8

OS-ENI-C24

O
K

2

3

P
R
I

2

7

O
K

1
S
E
C

5

OS-ENI-C24

O
K

2

9

2

1

7

T
E
M

O

P

K

1
1
1

S
T
A

9

T
U
S

1

1

1

1
2

1

2

4

1

F

3

A
N

3

1
5

1

C

3

O
N

S
/
M

O

L

O

E
D
E
M

1
7

1
5

1
9

1
7

2
1

1
9

2
3

E
N
E

T

2
1

2

3
2
4

L
IN

K

A
C

T

OS-GNI-C8

OS-GNI-C8

O
K
1

O
K
2

A

O

C

K

T

1

L

O
I
N

K

K

2

A
C

1

T

L
I
N

K

A
C

2

T

P

R

I
L
I
N

K

A
C

S

3

T

E

C

L
I
N

K

4

T

E

M

P

S

T

A

T
U
S

1

2

F

A

N
A
C

T

3
L
IN

K

A
C

5

T

C

O

N
L

S

/
IN

O

M

L

K

O

E
D
E
M

A
C

6

T

L
IN

K

A
C

7

T

L
IN

K

8

E
N
E

T

L
IN

K

A
C

T

OS-ENI-C24

O
K

2

3

2

1

O
K

1

5

O
K

2

3

2

1

7

5

3

9

1

7

5

1

1

1

2

3

1

9

4

7

5

1

1

1

2

1

9

4
1
3

7

1

1

1

2
1
5

1

9

4

1
3

1
7

1

1

1

2
1
5

1

4

1

3
1
9

1
7

1

5
2
1

1

3
1
9

1

7
2
3

2

4

1

5
2
1

1
9

1

7
2
3

2

4

2
1

1

9

2
3

2

4

2

1

2

3

2

4

OS8800-CMM

OS-GNI-U8

O
K

1

OS-GNI-U8

O
K

2

O
K

1

A

OS-GNI-U8

C

1

O

T

K

2

L
I
N

K

O
K

1

A

OS-GNI-U8

C

1

O

A

T

K

2

C

2

T

L
IN

K
L
I
N

O

K

K

1
A
C

1

O

A

T

K

2

C

2

A

T

L

C

IN
K

3

T

L
IN

K

A
L
I
N

C

K

1

A

T

C

2

A

T

L

C

I
N

K

3

A

T

L

C

IN
K

4

T

L
IN

K

A
L
I
N

C

K

2

A

T

C

3

A

T

L

C

I
N

K

4

A

T

L

C

IN
K

5

T

L
IN

K

A
L
I
N

C

K

3

A

T

C

4

T

A

L

C

I
N

K

5

A

T

L

C

IN
K

6

T

L
IN

K

A
L
IN

C

K

4

A

T

C

5

T

A

L

C

I
N

K

6

A

T

L

C

IN
K

7

T

L
IN

K

A
L
I
N

C

K

5

A

T

C

6

A

T

L

C

I
N

K

7

A

T

L

C

I
N
K

8

T

L
IN

K

A
L
I
N

C

K

6

A

T

C

7

A

T

L

C

I
N

K

8

T

L
IN

K
L
I
N

K

A
C

7

A

T

C

8

T

L
I
N

K
L
IN
K

A
C

8

T

L
I
N

K

OmniSwitch 8800

March 2005 OmniSwitch 8800 1

Availability Features

Availability ensures that your switch is consistently opera­tional for your day-to-day networking needs. This added reli­ability is provided through redundant components for critical
hardware and software subsystems. OmniSwitch 8800
switches provide a broad variety of availability features,
including:

• Software Redundancy

• Hardware Redundancy

• Configuration Redundancy

• Link Redundancy

• Smart Continuous Switching

• NI Module Forwarding During CMM Failover

• Image Rollback

• Hot Swapping

• Hardware Monitoring

• Power Checking Sequence

For more information on Availability features, refer to the

OmniSwitch 8800 Hardware Users Guide, the OmniSwitch
7700/7800/8800 Switch Management Guide, and the
OmniSwitch 7700/7800/8800 Network Configuration Guide.

2 OmniSwitch 8800 March 2005

Installing the Hardware

Items Required

• Grounding wrist strap (included)

• Phillips screwdriver (not included)

• Flat-blade screwdriver (not included)

• Serial cable (not included)

Site Preparation

Environmental Requirements

OmniSwitch 8800 switches have the following environmental
and airflow requirements:

• The installation site must maintain a temperature

between 0° and 45° Celsius (32° and 122° Fahrenheit)
and not exceed 95 percent maximum humidity
(noncondensing) at any time.

• Be sure to allow adequate room for proper air ventila-

tion at the front, back, and sides of the switch. Refer to

“Mounting the Switch” on page 7 for minimum clear-

ance requirements. No clearance is necessary at the top
or bottom of the chassis.

Electrical Requirements

OmniSwitch 8800 switches have the following general electri­cal requirements:

• Each switch requires one grounded AC outlet for each

power supply (up to four) installed in the chassis.
OmniSwitch 8800 switches offer both AC and DC
power supply support. Refer to the OmniSwitch 8800
Hardware Users Guide for more information.

• For switches using AC power connections, each

supplied AC power cord is 2 meters (approximately

6.5 feet) long. Do not use extension cords.

Caution. In North America, OmniSwitch 8800 power
supplies require 220 Volt power cords connected to 220
Volt power receptacles. Do not use 110 Volt power cords
or receptacles.

Redundant AC Power. If possible, it is recommended
that each AC outlet resides on a separate circuit. With
redundant AC, if a single circuit fails, the switch’s remain­ing power supplies (on separate circuits) will likely be
unaffected and can therefore continue operating.

March 2005 Installing the Hardware 3

Weight Considerations

• Hardcopy OmniSwitch 8800 Getting Started Guide

When fully-populated (i.e., with all CMM, SFM, and NI
modules, fan trays and power supplies installed), the
OmniSwitch 8800 weighs approximately 220 lbs (100 Kgs).

Items Included

Your OmniSwitch 8800 order includes the following items:

• OmniSwitch chassis with factory-installed power

supplies per order

• CMM module(s) per order

• Factory-installed SFM modules per order

• NI modules per order

• MiniGBICs per order, if applicable

• Xenpaks per order, if applicable

• Blank cover panels, if applicable

• Grounding wrist strap

• Documentation CD containing the following manuals:

OmniSwitch 8800 Getting Started Guide

OmniSwitch 8800 Hardware Users Guide

OmniSwitch CLI Reference Guide

OmniSwitch 7700/7800/8800 Switch Management
Guide

OmniSwitch 7700/7800/8800 Network
Configuration Guide

OmniSwitch 7700/7800/8800 Advanced Routing
Configuration Guide

• Power cord(s) per order, if applicable

4 Installing the Hardware March 2005

Unpacking and Installing the Switch

Unpacking the Chassis

Caution. Do not attempt to lift the chassis with the white
plastic inserts.

To protect your switch components from electrostatic
discharge (ESD) and physical damage, read all unpacking
recommendations and instructions carefully before beginning.

Recommendations

• Unpack your OmniSwitch chassis as close as possible

to the location where it will be installed.

• Network Interface (NI) modules and Chassis Manage-

ment Modules (CMMs) are packaged in separate
boxes. In order to greatly reduce exposure to electro­static discharge (ESD) and physical damage, do not
unpack these boxes until the CMMs and NI modules
are ready to be installed.

Chassis Removal Instructions

1 Begin by carefully cutting the tape along the seam

marked “OPEN HERE FIRST.”

2 Lift the box’s top flaps. Remove the smaller boxes that

are enclosed and set them aside. These smaller boxes
contain the Ship Kit.

3 Next, completely remove the four white plastic inserts

(two on the front and two on the back) from the sides of
the box. Removing these inserts allows the overpack to be
removed.

4 The overpack is the outer shell of the packaging. Lift

the overpack straight up until it slides free from the rest of
the packaging. This allows easy access to the chassis.

5 Remove the two rack-mounting brackets for 19-inch

racks.

Note. See “Rack-Mounting” on page 8 for more informa-
tion on installing the rack-mounting brackets.

6 Carefully remove the protective plastic from the switch

chassis.

7 In order to reduce the weight of the chassis, it is

recommended that you remove all factory-installed power
supplies prior to lifting it from the packaging.

8 Continue to “Power Supply Removal Instructions” on

page 6.

Note. The subsection below applies to power supplies that
are newly-shipped in the switch chassis. They have no
power cords attached and the on/off switches are in the off
( O ) position. For instructions on removing power
supplies that are currently operating in an existing switch,
refer to your OmniSwitch 8800 Hardware Users Guide.

March 2005 Installing the Hardware 5

Power Supply Removal Instructions

D
E

D
E

1 Loosen the four captive screws, located at the four

corners of the power supply’s front panel. If necessary,
use a flat-blade screwdriver to loosen the screws. Be sure
that all captive screws are completely disengaged from the
threaded holes in the chassis before continuing.

OK1

OK2

TEMP
FAIL
DC OK

AC OK

C
A

U

W

TIO

I

T
H

T

F

H

N:

O
E
R

U

A

T

L

R

I

H

S
L

P

IS

K

P

S

O

O

O

E

U

W

W

R

F

N

E

V

E

E

I
T

R

I

R

L

C

M

E

S

I

S

N

C

U

A

U

G

Y

T

P

P

R

B

P

U

P

!

IC

L

E

N

LY

I
E

I

A

E

T

L

.

Q

C

C

S

O

O

U

H

IP

R

R

O

D

D

P

C

S

S

E

K

B

.

D

,

T

E

D

O

F

I
S

R

O

C

E

R

O

D

E

N

U

N

C

E

E

A

C

TT

T

P

E

L

NT

U

S
P
R

D

IO

E

'U

V
T

N

N

E

O

:

N

C

U

C

I

O

S
F

R

E

A

R

L

T

L

I

D

E

R

E

A

O

S

E

S

P

N

L

C

P

C

A

O

A

D

H

R

'A

R

R

O

E

D

E

L

C

I

I

P

O

L

S

M

A

N

E

C

E

R

S

O

N

L

A

E

D

M

T

T

A

C

'

I

P

A

O

T

T

O

L

I

N

R

O

I

R

M

.

I

N

Q

T

E

.

E

U

NT

A

E

F

S

A

I
N

T

,
D

I

D

O

E

E

N

B

A

RA

V

A

N

N

C

T

H

E

E

D

E

CA

UT

W
I

T

IO

H

T

F

H

N

O

E

:

R

U

A

T

L

R

IS

H

L

P

P

IS

K

S

O

O

O

E

U

W

W

R

F

N

E

V

E

E

IT

R

IC

R

L

M

E

S

S

IN

C

U

A

U

G

Y

T

P

P

U

R

B

P

P

IC

L

E

N

LY

IE

IT

A

E

L

.

Q

C

C

S

O

O

U

H

I

R

R

P

O

D

D

P

C

S

S

E

K

.

D

B

,

T

E

D

O

F

I
S

R

O

C

E

R

O

E

N
N

2 With one hand, grasp the handle at the front of the

power supply and slowly pull the power supply out of the
power supply bay. Do not pull the power supply
completely out of the bay with one hand.

O

K
1

O

K
2

TEM

P

FAIL
DC OK

AC OK

CA

U

WITH FOUR PO

TIO

THE RISK OF ELECTR

N

:

ALL POWER

THIS UNIT MAY BE EQ

SERVICING UNIT

WER SU
SUPPL

PP

!

ICAL

LIE CORDS. T

Y

CO

.

SHOCK, DISCONNECT

UIPPED

RDS BEFO

O
REDUCE

RE

A
TTE

PLU

NT

S D'UN CO

PREVENIR LES CHOCS ELECTRIQUES, DEBRANCHE

IO

TOUS LES

N
:

CET

FAIRE LA REPARATION.

R
DON D'ALIMENT

APPAREIL COMPO

CORDON

S D

ATION. AFIN

'ALIMENT

R
TE

ATION

D

E
A
VANTE DE

2
3

0

V
5
0

/
6

0

H

z
,

8

.
0

A

C
AUT

WITH FO

IO

THE RIS

N:

UR POWER SUPP

ALL

THIS UNIT
POW
K OF

SERVICING UNIT

ER SUPPL

ELECTRICAL

M

AY

B

LIE CORDS.

E E

Y

CORDS BEFO

.

QUIP

SHOCK, DISC

PED
TO
RE

RE

O
NN

2
3

0

V
5
0

/

6

0
H

z
,

8

.
0

A

230V
50/60H

z, 8.0 A

3 When the power supply is pulled out far enough (about

10 inches), place your other hand under the power supply

230V
50/60H

z, 8.0 A

casing to support its weight.

4 Continue pulling the power supply out until it is

removed from the chassis.

5 Set the power supply aside on a clean, static-free

Note. Alcatel provides factory-installed blank cover plates

surface. You will need to re-install it later.
for empty module slots. Do not remove these cover plates
as they play an important role in chassis ventilation.

6 Remove all remaining power supplies by repeating

steps 1 through 5.

7 Continue to “Lifting the Chassis” on page 7.

6 Installing the Hardware March 2005

Lifting the Chassis

Mounting the Switch

Once its weight has been reduced by removing the power
supplies, the chassis can be lifted from the packaging material
and moved to the location where it is to be installed (see
important note below).

Important. Two people are required when lifting the
chassis. Due to its weight, lifting the chassis unassisted
can cause personal injury.

Continue to the next section, “Mounting the Switch.”

Note. Due to their weight, access, and airflow require-

ments, OmniSwitch 8800 switches cannot be wall-

mounted.

Airflow Considerations

Be sure that your switch is placed in a well-ventilated, static­free environment. Always allow adequate clearance at the
front and sides of the switch, as well as behind the switch’s fan
unit (located at the top-rear of the chassis). The following top­view diagram shows recommended minimum clearances for
adequate airflow.

Rear. 6 inches
minimum at rear
of chassis fan

}

unit.

Sides. 2 inches
minimum at left and
right sides.

Front. 6 inches
minimum at front
of chassis.

}

Chassis Top View

March 2005 Installing the Hardware 7

Never obstruct the air intake vents located at the bottom-front
and bottom-sides of the chassis or the fan unit’s air output
vents located at the rear of the chassis.

Rack-Mounting

Refer to the important guidelines below before installing the
OmniSwitch chassis in a rack.

Note. Clearance is not required at the top and bottom of
the chassis.

Module Access Considerations

If the switch will be mounted in rack that is immobile, make
sure that you have adequate clearance to install and remove
modules on the front and rear of the chassis. Please allow
enough clearance to install and remove the front fan trays,
which are approximately 15.8 inches long, are the longest
modules on the front. And please allow enough clearance to
remove the Switch Fabric Modules (SFMs) and power
supplies, which are approximately 6 inches long.

• Rack-mounting the chassis requires three people—two

people to hold the chassis and position it in the rack
and a third person to secure the chassis to the rack
using the attachment screws.

• Alcatel does not provide rack-mount screws. Use the

screws supplied by the rack vendor.

• To prevent a rack from becoming top heavy, it is

recommended that you install the switch at the bottom
of the rack whenever possible.

• If you are installing the switch in a relay rack, be sure

to install and secure the rack per the rack manufac­turer’s specifications.

• Refer to page 7 for important chassis airflow recom-

mendations before installing.

To rack-mount the switch, follow the steps below.

1 Using the rack-mounting brackets as a template, mark

the holes on the rack where the chassis is to be installed.

2 Attach one rack-mounting bracket to the front end of

the chassis using the Phillips-head screws that came with

the chassis. See the figure below for the positioning and

placement of these brackets and screws.

8 Installing the Hardware March 2005

6 Once the holes are aligned, use a third person to insert

a screw through the bottom hole on each bracket. Tighten

both screws until they are secure.

3 Attach the second bracket to the opposite front side of

the chassis using the remaining screws.

4 Using two people, lift and position the chassis until the

rack-mount brackets are flush with the rack post.

5 Align the holes in the brackets with the rack holes you

marked in step 1.

March 2005 Installing the Hardware 9

Note. Be sure to install the screws in the bottom hole of

each bracket, as shown, before proceeding.

7 Once the screws at the bottom of each bracket are

secure, install the remaining screws. Be sure that all

screws are securely tightened.

Stand-Alone

D
E

Installing Power Supplies

The OmniSwitch 8800 can be installed unmounted as a stand­alone unit. Be sure that the installation location is a stable, flat
surface that can accommodate the fully-populated weight of all
switches being installed. One fully-populated OmniSwitch
8800 weighs approximately 220 lbs (100 Kgs).

Note. OmniSwitch 8800 switches must be installed “right
side up.” Never attempt to operate a switch while it is
lying on its side.

To install the switch as a stand-alone unit, follow the steps
below:

1 Use two or more people to move and position the

unpopulated chassis upright on the floor or bench where it
is to be installed.

2 Be sure that adequate clearance has been provided for

chassis airflow and that you have placed the chassis within
reach of all required AC outlets. For recommended
airflow allowances, refer to page 7. For environmental and
electrical requirements, refer to page 3.

Reinstall the power supplies in the chassis power supply bays
by following the steps below.

1 Be sure that you do not install the power supply upside

down. When orienting the power supply, note that the on/

off switch and power cord socket are located at the bottom

of the power supply and the fan is located at the top of the

power supply.

2 With one hand, grasp the handle at the front of the

power supply. Place your other hand under the power

supply casing to support its weight.

3 Carefully insert the rear of the casing into the power

supply bay and slide the power supply back until its

connector meets the chassis backplane connector.

OK1

OK2

T
E

M

P
F
A

I

L
D
C

O

K
A
C

O

K

C

A
U

W

T

IT

IO

H
T
H

F

N

O

E

:

U

A

R

T

L

R

I

H

S

L

P

I

K

P

S

S

O

O

O

E

U

W

R

W

F

N

E

V

E

E

I
T

R

I

R

L

C

M

E

S

I

S

N

C

A

U

U

G

Y

T

P

P

R

B

P

U

!

P

I

L

E

N

C

L

I

Y

E

I

A

E

T

L

.

C

Q

C

S

O

O

U

H

R

I

R

P

O

D

D

P

C

S

S

E

K

.

D

B

T

,

E

D

O

F

I

S

R

O

C

E

R

O

D

E

N

U

N

C

E

E

A

C

T

T

T

P

E

L

N

U
S

P

T

R

D

I
O

E

'
U

V

T

N

N

O

E

:

N

C

U

C

I

O

S

F

R

E

A

R

L

T

L

I

D

E

R

E

A

O

S

E

S

P

N
C
L

P

C

A

O

A

D

H

R

R

'

R

O

A

E

D

E

L
C

I

I

P

O

L

S

M

A

N

C

E

E

R

S

O

N

L

A

E

D

M

T

T

A

C

I

'

P
A
O

T
T

O

L

I
N

R

O

I

R

M

.

I

N

Q

T

E

.

E

U

N

A

E

T

F

S

A

I

N

T

,
D

I

D

O

E

E

N

B

A

R

V

A

A

N
N
C
T

H

E

E

D

E

C
A

U

W

T

I
T

IO

H
T
H

F

N

O

E

:

U

A

R

T

L

R

I

H

S
L

P

I

K

P

S

S

O

O

O

E

U

W

R

W

F

N

E

V

E

E

I
T

R

I

R

L

C

M

E

S

I

S

N

C

A

U

U

G

Y

T

P

P

R

P

U

B

P

I

L

E

N

C

L

I

Y

E

I

A

E

T

L

.

C

Q

C

S

O

O

U

H

R

I

R

P

O

D

D

P

C

S

S

E

K

.

D

B

T

,

E

D

O

F

I
S

R

O

C

E

R

O

E

N
N

230

V

50/60Hz, 8.0 A

230V
50/60Hz, 8.0 A

10 Installing the Hardware March 2005

4 Continue sliding the power supply back until the front

0/60

panel meets the front of the chassis. Do not force the
power supply into the bay. Otherwise you can damage the
connectors.

5 Tighten the four captive screws, located at the four

corners of the power supply’s front panel. Be sure not to
overtighten the captive screws. If you use a screwdriver,
the torque used to tighten the screws must not exceed 2.3
inch pounds.

O

K

1

O

K

2

TEMP
FAIL
DC OK

AC OK

6 Verify that the power supply’s on/off switch is in the

off ( O ) position.

7 Remove the two screws on the top of the power cord

retainer with a Phillips-head screwdriver. Do not discard
these screws; you will need to reinstall them later.

Retainer Screws

8 Slide the end of the power cord through the top portion

of the retainer until it stops.

Hz, 8.0 A

9 Plug the other end of the power cord into the power

supply’s socket. Make sure that the power cord is attached
securely to the outlet.

March 2005 Installing the Hardware 11

10 Use a Phillips-head screwdriver to attach the top

portion of the retainer with the two Phillips-head screws.

11 Once the power cord is secured in the retainer, plug

the power cord into an easily-accessible, properly
grounded outlet. Do not use an extension cord.

12 Install all remaining power supplies by repeating steps

1 through 11 for each power supply.

Using the Grounding Wrist Strap and Chassis Grounding Lug

Because electrostatic discharge (ESD) can damage switch
components such as the Network Interface (NI) and Chassis
Management Modules, you must ground yourself properly
before continuing with the hardware installation.

For this purpose, Alcatel provides a grounding wrist strap and
a grounding lug located near the bottom-right of the chassis.
To properly ground yourself, follow the steps below.

1 Fasten the provided grounding strap to your wrist.

2 Insert the wrist strap’s connector pin (located at the end

of the strap’s tether) into the grounding lug near the
bottom-right of the chassis, as shown.

Note. For OmniSwitch 8800 switches using DC power,
the power cord connector snaps into the connector socket.
A cable retainer is not used.

Important. Do not turn on the power supplies at this time.

12 Installing the Hardware March 2005

Chassis
Grounding Lug

Installing the Network Interface (NI) and Chassis Management Modules (CMMs)

Once you are properly grounded, you may begin installing the
Network Interface (NI) and CMM(s).

Note. See “Installing SFMs” on page 18 for information
on installing SFMs.

NI Modules

NI modules may be installed in any slot position from 1
through 16 in OS8800 switches.

CMMs

CMMs may be installed in slots A or B in OS8800 switches. A
minimum of one CMM is required for switch operations; the
second CMM provides redundancy.

In non-redundant configurations, the CMM may be installed in
either slot A or B. In redundant configurations, the CMM
installed in slot A will be designated primary by default. For
more information on redundancy, refer to page 52 or, for
detailed information, refer to your OmniSwitch 8800 Hard-
ware Users Guide.

Important. For the grounding wrist strap to be effective
in eliminating ESD, the power supplies must be installed

NI modules cannot be installed in CMM slots A or B; like­wise, CMMs cannot be installed in any NI slot position.

in the chassis and plugged into grounded AC outlets as
described on page 10.

More Information on Slot Numbering. For a diagram
showing the chassis layout and slot positions, refer to

“Chassis Slot Numbering” on page 50.

March 2005 Installing the Hardware 13

Note. To further reduce exposure to electrostatic discharge
(ESD) and physical damage, do not remove more than one
module at a time from the factory packaging. Unpack one
module, immediately install the module in the chassis,
then repeat the sequence for another module.

Before beginning, note that the CMM modules and NI
modules slide into the chassis card guides differently. With
CMMs, the back of the module’s printed circuit board (which
is wider than the front side) initially provides the glide path.
When the printed circuit board narrows a sheet metal flange
continues the remaining glide path. With NIs, the edges of the
module’s printed circuit board slide into the guides.

To install an NI or CMM module, follow the steps below.

1 Holding the module in both hands, carefully slide it

into the chassis card guide. The component side of the
board should face right.

2 The module should slide in easily. Do not force the

module into the slot. If any resistance is encountered,
ensure the module is aligned properly in the card guide.

CMM Glide Path

14 Installing the Hardware March 2005

Also, see the important note regarding chassis card guides
on page 14.

3 When the module is nearly seated in the slot, be sure

that the two extractor levers—one on top of the module
and one on the bottom—are slightly opened (approxi­mately 30 degrees). This allows the notch on each extrac­tor lever to grasp the rail on the chassis. Once the notches
have grasped the rail, press both extractor levers simulta­neously until the module is firmly seated.

4 Once the module is firmly seated, secure the module to

the chassis by tightening the two captive screws. Be sure
not to overtighten the captive screws. If you use a screw­driver, the torque used to tighten the screws must not
exceed 2.3 inch pounds.

5 Install all remaining modules by repeating steps 1

through 4 for each module.

March 2005 Installing the Hardware 15

Installing MiniGBIC Connectors

TX

RX

K

If you are installing an OS8-GNI-U8 or OS8-GNI-U24
module, you must install Miniature Gigabit Interface Convert­ers (MiniGBICs) as required. These MiniGBICs are packaged
separately.

3 Push the MiniGBIC into the slot until it clicks into

place.

GNI Module

6

LIN

A

C

T

MiniGBIC Slot

MiniGBIC Module

7

LINK

A

C

T

8

LINK

A

C

T

LINK

A

C

T

MiniGBIC Module

Note. There is a small removal handle at the front of the

MiniGBIC transceiver. To remove a MiniGBIC, carefully

To install a MiniGBIC follow the steps below.

lift this handle; then, grasp the handle and carefully pull
the MiniGBIC from the module.

1 Be sure you have eliminated ESD by using the

provided grounding wrist strap. Refer to “Using the

Grounding Wrist Strap and Chassis Grounding Lug” on
page 12 for more information.

2 Holding the MiniGBIC by its sides, carefully slide it

into the desired GNI module universal MiniGBIC slot.

16 Installing the Hardware March 2005

Caution. The MiniGBIC should slide in easily. Do not
force it into the slot. If any resistance is encountered,
ensure the MiniGBIC is aligned properly. Forcing the
MiniGBIC into the slot can damage the unit, as well as
components on your GNI module.

Installing Xenpak Modules

If you are installing an OS8-10GNI-UR1, you must install
Xenpaks (10 Gigabit Ethernet modules) as required. These
Xenpaks are packaged separately.

3 Align the groove on the XENPAK module with the

guide rails on the OS8-10GNI-UR1’s circuit board as
shown below:

10GNI Module

OK1

OK2

1

T

X

Tx

R

X

Rx

Link

Port

Redundancy

Tx

Rx

Link

Xenpak Slot

2

Xenpak Module

Xenpak Module

T

X

R

X

To install a Xenpak follow the steps below.

1 Be sure you have eliminated ESD by using the

provided grounding wrist strap. Refer to “Using the

4 Holding the Xenpak by its sides, carefully slide it into

the desired Xenpak slot.

Grounding Wrist Strap and Chassis Grounding Lug” on
page 12 for more information.

Caution. The Xenpak should slide in easily. Do not force

2 Remove the blank slot cover plate from the OS8-

10GNI-UR1’s front face and set the cover plate and
screws aside.

it into the slot. If any resistance is encountered, ensure the

Xenpak is aligned properly. Forcing the Xenpak into the

slot can damage the unit, as well as components on your

module.

March 2005 Installing the Hardware 17

Installing SFMs

5

To install an SFM, follow the steps here.

Once you are properly grounded, you may begin installing the
Switch Fabric Modules (SFMs) on the back side of the chas­sis. Because electrostatic discharge (ESD) can damage switch
components such as the Switch Fabric Modules, you must
always ground yourself properly before removing or adding a
module. Refer to page 12 for more information.

Note. See “Installing the Network Interface (NI) and

Chassis Management Modules (CMMs)” on page 13 for

information on installing CMMs and NIs.

SFMs may be installed in SFM slots 1 through 5. A minimum
of four (4) SFMs are required for switch operations; the fifth
SFM provides redundancy. For more information on redun­dancy, refer to page 52 or, for detailed information, refer to
your OmniSwitch 8800 Hardware Users Guide.

More Information on Slot Numbering. For a diagram
showing the chassis layout and slot positions, refer to page

51.

Note. To further reduce exposure to electrostatic discharge

(ESD) and physical damage, do not remove more than one

SFM at a time from the factory packaging. Unpack one

SFM, immediately install the SFM in the chassis, then

repeat the sequence for another SFM.

1 Holding the SFM in both hands, carefully slide it into

the chassis card guide. The component side of the board

should face up.

2 The SFM should slide in easily. Do not force the SFM

into the slot. If any resistance is encountered, ensure the

SFM is aligned properly in the card guide.

OS8800-SFM

O

K

1

O

K

2

1

2

3

TEMP
FAIL
DC OK

AC

OK

4

18 Installing the Hardware March 2005

3 When the SFM is nearly seated in the slot, be sure that

4

K

3

the two extractor levers—one on the left of the SFM and
one on the right—are slightly opened (approximately 30
degrees). This allows the notch on each extractor lever to
grasp the rail on the chassis. Once the notches have
grasped the rail, press both extractor levers inward simul­taneously until the SFM is firmly seated.

4 Once the SFM is firmly seated, secure the SFM to the

chassis by tightening the two captive screws. Be sure not

to overtighten the captive screws. If you use a screw-

driver, the torque used to tighten the screws must not

exceed 2.3 inch pounds.

OS8800-SFM

OS8800-SFM

1

2

OK1

OK1

O

O

S

88

0

0-S

F

M

O
K

1

O
K
2

1

2

T
E

M

F

P

A

I

L
D
C

O

K
A
C

O

K

T
E
M
F

P
A
I

L
D
C

O

K
A
C

O

1

K

3

4

5

2

3

5 Install all remaining SFMs by repeating steps 1

through 4 for each module.

Blank Cover Plates

Blank cover plates are factory-installed in the chassis and are
used to cover empty CMM, SFM, and NI slots, as well as
empty power supply bays.

These cover plates play an important role in chassis airflow
and temperature management. They also provide protection for
module processor boards and other sensitive internal switch
components by closing off a chassis that is not fully populated.

Because they regulate airflow and help protect internal chassis
components, blank cover plates should remain installed at
empty module slots and power supply bays at all times.

March 2005 Installing the Hardware 19

Connections and Cabling

Once your switch is properly installed, you should connect all
network and management cables required for your network
applications. Connections may include:

• Serial cable to the console port

• Ethernet cable to the Ethernet Management Port

(EMP) on the CMM

• Fiber cables to all required MiniGBICs and Xenpaks

• Ethernet cables to all required RJ-45 ports on copper

ENI and GNI modules.

Serial Connection to the Console/Modem Port

The console port, located on the CMM module, provides a
serial connection to the switch and is required when logging
into the switch for the first time. By default, this female DB-9
connector provides a DCE console connection. However, by
changing the onboard jumper setting, the port can be changed
to a DTE modem connection.

Modem Connections. If you require a modem connec­tion to the switch, you must convert the console port to
support modem connections by installing a hardware
jumper on the CMM. Refer to your OmniSwitch 8800
Hardware Users Guide for details.

Serial Connection Default Settings

The factory default settings for the serial connection are as
follows:

baud rate 9600

parity none

data bits (word size) 8

stop bits 1

For information on modifying these settings, refer to

“Modifying the Serial Connection Settings” on page 29.

20 Connections and Cabling March 2005

EMP Cable Requirements

There are specific cable type requirements (i.e., straight­through or crossover) based on the location of the EMP port
and the type of device to which it is connecting. Refer to the
information below:

Refer to the diagram below for console/modem port and EMP
locations.

EMP to a Switch Straight-

through

EMP to a Computer or

Crossover

Workstation

Note. For information on manually configuring Ethernet

ports for cabling requirements, refer to “Configuring
Ethernet Ports” in the OmniSwitch 7700/7800/8800
Network Configuration Guide.

OS-ENI-C24

O
K
1

OS-ENI-C24

O
K
2

2

O
K
1

OS-ENI-C24

O
K
2

2

1

O

K
1

OS-ENI-C24

O

K

2

FAN

3

13

CONSOLE
/ MODEM

15

17

19

21

ENET

2

3

2

1

O
K
1

5

OS8800-CMM

O
K
2

3

2

1

7

O
K
1

5

OS-ENI-C24

O
K
2

3

9

1

7

O
K

1

5

1

1

1
2

1
4

1
2

1
4

1

3

1

5

1

7

1

9

2

1

2

3
2
4

2
4

OS-GNI-C8

O
K
1

O
K
2

A
C
T

L
I
N
K

A
C

1

T

A

L
IN

C
T

K

L

IN
A
C

K

2

T

A

L
IN

C
T

K

L

IN
A
C

K

3

T

A

L
IN

C
T

K

L

IN

K

4

A

C
T

L

IN

K

A
C
T

L
I
N
K

A
C

5

T

A

L
IN

C
T

K

L

I
A

N

C

K

6

T

A

L
IN

C
T

K

L

I
A

N

C

K

7

T

A

L
I

C

N

T

K

L

I

N
K

8

A

C
T

L

I

N
K

OS-ENI-C24

O
K

2

3

P

9

R
I

2

7

O
K

1
S
E
C

5
1
1

1
3

1
5

1
7

1
9

2
1

2
3

OS-GNI-C8

O
K
1

O
K
2

1

A
C
T

L
I
N
K

2

A
C
T

L
I
N
K

3

A
C
T

L
IN
K

4

A
C
T

L
IN
K

5

A
C
T

L
IN
K

6

A
C
T

L
IN
K

7

A
C
T

L
IN
K

8

A
C
T

L
IN
K

OS-ENI-C24

O
K

2

9

2

1

7

T
E
M

O

P

K

1

1

1

1
2

1
4

1

1

1

3

1

5

1

7

1

9

2

1

2

3
2
4

2

OS-GNI-C8

O

K
1

O

K
2

1

A
C
T

L
I
N
K

2

A
C
T

L
IN
K

3

A
C
T

L
I
N
K

4

A
C
T

L
I
N
K

5

A
C
T

L
IN
K

6

A
C
T

L
IN
K

7

A
C
T

L
I
N
K

8

A
C
T

L
IN
K

OS-ENI-C24

O
K

2

S

3
T
A

9

T
U
S

2

1

O

K
1

5
1

1

1

2

O

K
2

3

2

4

F
A

2

N

1

7
3

5

3
C
O

9

N

1

S
/

3

O
M
L
O

E

D

1
E
M

7

5

1

1

1

2

1

5

3

1

9

4

7

1

7

5

1

1

1
2

1

9

4

1
3

1

9

7

E
N

1

E

1

1

T

2
1
5

2

1

1

9

4

1
3

1
7

2

3

4

1

1

1

2
1
5

1

L

4

I
N

1

K

3
1
9

A
C

1

T

7

1

5
2
1

1

3
1
9

1

7
2
3

2
4

1

5
2
1

1

9

1

7
2
3

2
4

2

1

1

9

2

3
2
4

2
1

2
3

2

4

OS-GNI-C8

O
K
1

OS8800-CMM

O
K
2

O
K
1

OS-GNI-U8

O
K
2

1

O
K

1

OS-GNI-U8

O
K

2

2
P
R
I

O
K

1

S

3

A
E
C

OS-GNI-U8

C

1

O

T

K

2

L
IN
K

4

T
E
M

O

P

K

1

A

OS-GNI-U8

C

1

O

T

A

K

2

S

C
T
A

2

T

T
U
S

L
I
N

K
L
I
N

O

K

K
1

A

1

C

1

O

A

T

K
2

C

2

2

T

A

F

L

A

C

I

N

N
K

3

T

L

I

3

N

K

A
L
I
N

C
K

1

A

T

C

5

2

C

T

A
O
N
/

L
S
M

C

IN
O
O
L

K

3

D

E

A

T
E
M

L

C

I
N
K

4

T

L

6

I
N
K

A
L
I
N

C
K

2

A

T

C

3

A

T

7

L

C

IN

K

4

A

T

L

C

I
N
K

5

T

L
I
N
K

8

A
L
I
N

C
K

3

T

A
C

4

A

T

L

E

C

IN

N

K

E

5

T

T

A

L

C

I
N
K

6

T

L
IN
K

A
L
I
N

C
K

4

A

T

C

5

T

A

L

C

I

N
K

6

L

A

T
I
N

L

K

C

I
N
K

7

T

L
I
N

A

K
C
T

A
L
IN

C
K

5

T

A
C

6

A

T

L

C

I

N
K

7

A

T

L

C

IN
K

8

T

L
I
N
K

A
L
I
N

C
K

6

T

A
C

7

A

T

L

C

I

N
K

8

T

L
I
N

K
L
IN
K

A
C

7

A

T

C

8

T

L
I

N

K
L
IN
K

A
C

8

T

L
IN

K

23

LINK

ACT

March 2005 Connections and Cabling 21

Booting the Switch

Now that you have installed the switch components and
connected all required cables, you can boot the switch. To boot
the switch, simply turn the on/off switch for all installed power
supplies to the on ( | ) position.

Note. If you have more than one power supply installed,
be sure to turn on each power supply in rapid succession,
(i.e., within a few seconds of each other). This ensures that
there will be adequate power for all NI modules when they
boot.

Component LEDs

The boot process takes a few moments to complete. During
this process, the LEDs on the CMM, SFM, and NI modules
may flash and change color, indicating different stages of the
boot.

Following a successful boot, the LEDs on all switch compo­nents, including power supplies, should display as follows:

CMM OK1 Solid Green

CMM OK2 Blinking Green

CMM TEMP Solid Green

CMM FAN 1 Solid Green

CMM FAN 2 Solid Green

CMM FAN 3 Solid Green

SFM OK1 Solid Green

SFM OK2 Blinking Green

NI OK1 Solid Green

NI OK2 Blinking Green

Power Supply TEMP Fail Off

Power Supply DC OK Solid Green

Power Supply AC OK Solid Green

If the LEDs do not display as indicated, make sure the boot
process is completed. Again, the boot process takes several
moments to complete. If the LEDs do not display as indicated
following a complete boot sequence, contact Alcatel Customer
Support.

For descriptions of CMM, SFM, and NI LED states, see pages

53 through 63. For information on power supply LED states,

refer to the OmniSwitch 8800 Hardware Users Guide.

Once the switch has completely booted and you have accessed
your computer’s terminal emulation software via the console
port, you are ready to log in to the switch’s Command Line
Interface (CLI) and configure basic information. Continue to

“Your First Login Session” on page 23.

22 Booting the Switch March 2005

Your First Login Session

In order to complete the setup process for the switch, you
should complete the following steps during your first login
session:

• Log in to the switch

• Set IP address information for the Ethernet

Management Port (EMP)

• Unlock session types

• Change the login password

• Set the date and time

• Set optional system information

• Save your changes

Important. You must be connected to the switch via the

console port before initiating your first login session.

Logging In to the Switch

When you first log in to the switch, you will be prompted for a
login (i.e., user) name and password. During this first login
session, only one user name option and one password option is
available:

• Login (i.e., user name)—admin

• Password—switch

To log in to the switch, enter admin at the login prompt:

login: admin

Next, enter the factory default password, switch, at the pass­word prompt:

password: switch

The default welcome banner, which includes information such
as the current software version and system date, displays—
followed by the CLI command prompt:

Welcome to the Alcatel OmniSwitch 8000

Software Version 5.1.5, June 13, 2004.

Copyright(c), 1994-2004 Alcatel Internetworking, Inc.
All Rights reserved.

OmniSwitch(TM) is a trademark of Alcatel Internetwork­ing, Inc. registered in the United States Patent and
Trademark Office.

March 2005 Your First Login Session 23

More Information On User Accounts. A user account
includes a login name, password, and user privileges.
Privileges determine whether the user has read or write
access to the switch and which commands the user is
authorized to execute.

For detailed information on setting up and modifying user
accounts and user privileges, refer to the “Managing
Switch User Accounts” chapter of your OmniSwitch 7700/

7800/8800 Switch Management Guide.

1 Enter modify boot parameters at the CLI prompt. The

boot prompt displays:

Boot >

2 At the boot prompt, enter boot empipaddr, followed

by the new default IP address for the EMP. For example:

Boot > boot empipaddr 168.22.2.120

3 Next, enter boot empgatewayipaddr, followed by the

new default gateway address for the EMP. For example:

Setting IP Address Information for

Boot > boot empgatewayipaddr 168.22.2.254

the EMP

4 Verify your current changes by entering show at the

The Ethernet Management Port (EMP) is located on the CMM
module. The EMP allows you to bypass the Network Interface
(NI) modules and manage the switch over the network directly
through the CMM.

In order to ping the switch through the EMP Ethernet connec­tion, you must change the port’s default IP and gateway
addresses.

To change the default IP and gateway addresses, refer to the
following steps.

Note. You must be connected to the switch via the console
port before attempting to change IP address information.
Otherwise, an error message will display.

24 Your First Login Session March 2005

boot prompt:

Boot > show
Edit buffer contents:
EMP IP Address : 168.22.2.120
EMP Gateway IP Address : 168.22.2.254

(additional table output not shown)

Subnet Mask. The default subnet mask is Class C
(255.255.255.0). If you must change this default value,
use the boot empnetmask command at the boot prompt.

Access to the EMP. By default, only devices in the same
subnet as the EMP will be able to manage the switch
through that port. For information on allowing devices in
other subnets to manage the switch via the EMP, refer to
the OmniSwitch 8800 Hardware Users Guide.

5 Save these changes to the switch’s running memory by

entering commit system at the boot prompt:

Boot > commit system

Unlocking Session Types

Security is a key feature on OmniSwitch 8800 switches. As a
result, when you access the switch for the first time, you must
use a direct console port connection. All other session types
(Telnet, FTP, WebView, SNMP, etc.) are “locked out” until
they are manually unlocked by the user.

The CLI command used to unlock session types is

aaa authentication.

This will immediately enable your changes and allow
users to ping the EMP. Note, however, that these changes
have not yet been saved to the switch’s boot.params file
and will be lost if the switch is rebooted.

6 To permanently save these changes to the

boot.params file, enter commit file at the boot prompt:

Boot > commit file

Changes will be preserved following a switch reboot.

7 Return to the CLI prompt by entering exit at the boot

prompt.

Important. Although you have configured the EMP with
valid IP address information, you will not be able to
access the switch through this port for Telnet, FTP,
WebView, or SNMP sessions until you have unlocked
these remote session types. See “Unlocking Session

Types” for more information.

Note. When you unlock session types, you are granting
switch access to non-local sessions (e.g., Telnet). As a
result, users who know the correct user login and pass­word will have remote access to the switch. For more
information on switch security, refer to the “Managing
Switch Security” chapter of your OmniSwitch 7700/7800/

8800 Switch Management Guide.

Unlocking All Session Types

To unlock all session types, enter the following command
syntax at the CLI prompt:

-> aaa authentication default local

Unlocking Specified Session Types

You can also unlock session types on a one-by-one basis. For
example, to unlock Telnet sessions only, enter the following
command:

-> aaa authentication telnet local

March 2005 Your First Login Session 25

To unlock WebView (HTTP) sessions only, enter the follow­ing command:

-> aaa authentication http local

Changing the Login Password

Change the login password for admin user sessions by follow­ing the steps below:

You cannot specify more than one session type in a single
command line. However, you can still unlock multiple session
types by using the aaa authentication command in succes­sion. For example:

-> aaa authentication http local

-> aaa authentication telnet local

-> aaa authentication ftp local

How many sessions are allowed?

Once a session type has been unlocked, the following number
of sessions is allowed for each type:

Telnet sessions allowed 4 concurrent sessions

FTP sessions allowed 4 concurrent sessions

HTTP (Web browser) ses-

4 concurrent sessions

sions allowed

Secure Shell and Secure

8 concurrent sessions

Shell FTP sessions allowed

Total sessions (Telnet, FTP,

21 concurrent sessions
HTTP, Secure Shell and
Secure Shell FTP, console)

1 Be sure that you have logged into the switch as user

type admin (see “Logging In to the Switch” on page 23).

2 Enter the keyword password and press <Enter>.

3 Enter your new password (up to 47 characters long) at

the prompt (refer to the note below).

Note. Typically, the password should be a string of non­repeating characters. The CLI uses the first occurrence of
the character series to uniquely identify the password. For
example, the password engrengr is the same as engr. A
better password might be engr2735.

4 You will be prompted to re-enter the password. Enter

the password a second time.

Note. Be sure to remember or securely record all new
passwords; overriding configured passwords on
OmniSwitch 8800 switches is restricted.

SNMP sessions allowed 50 concurrent sessions

26 Your First Login Session March 2005

New password settings are automatically saved in real time to
the local user database; the user is not required to enter an
additional command in order to save the password informa­tion. Also note that new password information is retained
following a reboot.

All subsequent login sessions—including those through the
console port—will require the new password in order to access
the switch.

User Accounts. The switch allows a maximum of 50 user
accounts in the local user database. For information on
creating additional user types and assigning individual
passwords, refer to the “Managing Switch User Accounts”
chapter of your Switch Management Guide.

Setting the System Time Zone

The switch’s default time zone is UTC (also referred to as
Greenwich Mean Time).

If you require a time zone that is specific to your region—or if
you need to enable Daylight Savings Time (DST) on the
switch—you can configure these settings via the system time-
zone and system daylight savings time commands. For exam­ple, to set the system clock to run on Pacific standard time,
enter the following command.

To enable Daylight Savings time, enter the following
command.

-> system daylight savings time enable

Many other time zone variables are supported. For detailed
information on configuring a time zone for the switch, refer to
your OmniSwitch 7700/7800/8800 Switch Management Guide.

Setting the Date and Time

Set the current time for the switch by entering system time,
followed by the current time in hh:mm:ss. For example:

-> system time 18:35:00

The switch uses a 24-hour clock; the time value shown in the
above example would set the time to 6:35 PM.

To set the current date for the switch, enter system date,
followed by the current date in mm/dd/yyyy. For example:

-> system date 12/27/2002

-> system timezone pst

March 2005 Your First Login Session 27

Setting Optional System Information

This section provides information on configuring optional
system parameters, including:

• the switch’s administrative contact

• a system name

Specifying a System Name

The system name is a simple, user-defined text description for
the switch.

To specify a system name, enter system name, followed by a
text description of up to 254 characters. If you include spaces
between words in the text string, be sure to enclose the string
in quotes (" ").

• the switch’s physical location

Specifying an Administrative Contact

An administrative contact is the person or department in
charge of the switch. If a contact is specified, users can easily
find the appropriate network administrator if they have ques­tions or comments about the switch.

To specify an administrative contact, enter system contact,
followed by a text string of up to 254 characters. If you
include spaces between words in the text string, be sure to
enclose the string in quotes (" ").

For example:

-> system contact "JSmith X477 [e-mail]"

For example:

-> system name "Engineering Switch 3"

Specifying the Switch’s Location

It is recommended that you use a physical labeling system for
locating and identifying your switch(es). Examples include
placing a sticker or placard with a unique identifier (e.g., the
switch’s default IP address) on each chassis.

However, if no labeling system has been implemented or if
you need to determine a switch’s location from a remote site,
entering a system location can be very useful.

To specify a system location, enter system location, followed
by a text description of up to 254 characters. If you include
spaces between words in the text string, be sure to enclose the
string in quotes (" ").

For example:

-> system location "NMS Lab--NE Corner Rack"

28 Your First Login Session March 2005

Viewing Your Changes

To view your current changes, enter show system at the CLI
prompt.

Saving Your Changes

Modifying the Serial Connection Settings

The switch’s serial connection defaults are listed on page 20.
If you wish to modify the default serial connection settings
(i.e., baud rate, parity, data bits, and stop bits), refer to the
following steps.

Once you have configured this basic switch information, save
your changes by entering write memory at the CLI command
prompt.

When the write memory command is entered, changes are
automatically saved to the main configuration file (boot.cfg)
and placed in the /flash/working directory. For more informa­tion on the boot.cfg file, refer to page 38.

Note. If the switch reboots following a write memory
command entry, the switch will run from the
/flash/certified directory. As a result, subsequent configu­ration changes cannot be saved using the write memory
command until the switch is once again running from the
/flash/working directory. See page 40 for important infor-
mation on these directories.

Note. You must be connected to the switch via the console
port before attempting to change serial connection
settings. Otherwise, an error message will display.

1 Enter modify boot parameters at the CLI prompt. The

boot prompt displays:

Boot >

2 To change the baud rate, enter boot serialbaudrate,

followed by the desired baud rate value. Options include
1200, 2400, 4800, 9600 (default), 19200, 38400, 57600,
76800, and 115200. For example:

Boot > boot serialbaudrate 19200

Note. Setting the console port to speeds above 9600 baud
can cause problems with Zmodem uploads.

3 To change the parity value, enter boot serialparity,

followed by the desired parity value. Options include none
(default), even, and odd. For example:

March 2005 Your First Login Session 29

Boot > boot serialparity even

4 To change the data bits (i.e., word size) value, enter

boot serialwordsize, followed by the number of data bits.
Options include 7 and 8 (default). For example:

8 You can also save your changes in real time to the

switch’s running memory by entering commit system at
the boot prompt:

Boot > commit system

Boot > boot serialwordsize 7

5 To change the stop bits value, enter boot serialstop-

bits, followed by the number of stop bits. Options include

1 (default) and 2. For example:

Boot > boot serialstopbits 2

6 Verify your current changes by entering show at the

boot prompt:

Boot > show
Edit buffer contents:
Serial (console) baud : 19200
Serial (console) parity : even
Serial (console) stopbits : 2
Serial (console) wordsize : 7

(additional table output not shown)

7 You can save your changes to the boot.params file by

entering commit file at the boot prompt:

Boot > commit file

Caution. There are two important things to consider when
using the commit system command to save serial connec­tion changes:

• Output to the terminal may become illegible due to

incompatible serial connection settings between the
switch and the terminal emulation software.

• If you use the commit system command only, changes

will not be saved to the switch’s boot.params file and
will be lost if the switch is rebooted. To save changes
to the boot.params file, refer to step 7.

9 Return to the CLI prompt by entering exit at the boot

prompt.

This completes the initial setup process. Your Alcatel
OmniSwitch 8800 switch is now ready for additional configu­ration and network operation. Refer to the following sections
for more information on using your switch, as well as addi­tional built-in features.

When the commit file command is used, changes will not
be enabled until after the next switch reboot.

30 Your First Login Session March 2005

CLI Basics

The Command Line Interface (CLI) allows you to configure
and monitor your switch by entering single-line commands.
The CLI can be accessed through terminal or Telnet sessions.

Note. Configuring the switch using the CLI is also
referred to as “online configuration.”

The following section provides basic information on CLI
assistance features. For detailed information on the CLI,
including syntax conventions, usage rules, command docu­mentation, and a quick reference card, refer to the OmniSwitch

CLI Reference Guide and the OmniSwitch 7700/7800/8800
Switch Management Guide.

CLI Assistance Features

The CLI provides built-in features that assist you while enter­ing commands. These features include:

• Syntax checking

• Command line help

• Partial keyword completion

• Deleting and inserting characters

• Previous command recall

• Prefix recognition

• Prefix prompt

• Command history

Note. The software supports vt100 terminal emulation;

CLI assistance features may be limited if your terminal

emulation software is using a setting other than vt100.

Syntax Checking

If you make a mistake while entering command syntax, the
CLI provides clues about how to correct the error. Whenever a
command error is entered, two indicators are displayed:

• An Error message describing the type of error.

• A carat (^) character indicating where the error

occurred.

For example, the syntax

-> show vlan router port mac status

results in the following error:

-> show vlan router port mac status
^
ERROR: Invalid entry: "port"

Because port is not valid syntax for the command, the error
message shows it as an invalid entry and the carat indicates
where the problem has occurred. For this example, the valid
command syntax is

-> show vlan router mac status

March 2005 CLI Basics 31

Command Line (?) Help

Partial Keyword Completion

The CLI provides additional help in the form of the question
mark (?) character. The ? character provides information that
helps you build your command syntax. For example, if you
enter

-> show vlan router

at the command line and are unsure of the next keyword, you
can enter the ? character for additional options (be sure to
include a space between the last keyword and the ? character):

-> show vlan router ?
^

MAC IP
(Vlan Manager Command Set)

The carat character (^) indicates the point where you invoked
the command line help. Possible keyword options, along with
the corresponding command set, are displayed. Here, you can
continue building the command by entering either mac or ip.

Some command completion options may indicate user-defined
information. For example: <string>, <slot/port>,
<hh:mm:ss>, etc. The option <cr> indicates that the
command can be completed by pressing <Enter>.

The CLI has a partial keyword recognition feature. Instead of
typing an entire keyword, you can type only the minimum
number of characters needed to uniquely identify the keyword,
then press the Tab key. The CLI will complete the keyword
and place the cursor at the end of the command line.

If you do not enter enough characters to uniquely identify the
keyword, pressing the Tab key will have no effect.

If you enter characters that do not belong to an applicable
keyword, pressing the Tab key will remove the characters and
place the cursor back to its previous position.

Deleting Characters

You can delete CLI command characters by using the Back­space key or the Delete key. The Backspace key deletes each

character in the line, one at a time, from right to left.

To change incorrect syntax with the Delete key, use the Left
Arrow key to move the cursor to the left of the character to be
deleted, then use the Delete key to remove characters to the
right of the cursor.

Note. The ? character can be entered at any time. In addi­tion, you can type the ? character alone at the CLI prompt
to display root keywords for all command sets.

32 CLI Basics March 2005

Inserting Characters

Prefix Recognition

To insert a character between characters that are already typed,
use the Left and Right Arrow keys to place the cursor into
position, then type the new character. Once the syntax is
correct, execute the command by pressing <Enter>. In the
following example, the user enters the wrong syntax to execute
a command. The result is an error message.

-> show micrcode
^
ERROR: Invalid entry: "micrcode"

To correct the syntax without retyping the entire command
line, use the !! command to recall the previous syntax. Then,
use the Left Arrow key to position the cursor between the “r”
and the “c” characters. To insert the missing character for this
example, type “o” as shown:

-> !!

-> show microcode

Previous Command Recall

To recall the last command executed by the switch, press the
Up Arrow key at the prompt and the previous command will
display on your screen. You can execute the command again
by pressing <Enter> or you can edit it first by deleting or
inserting characters.

Prefix recognition is a CLI feature that reduces redundant
command line entry by storing commonly-used prefix infor­mation for certain commands. The CLI assumes this stored
prefix information when the next command is entered. For
example, if you enter

-> vlan 32

at the command line, the CLI will store the vlan 32 prefix
information.

The following command families support prefix recognition:

• AAA

• Interface

• Link Aggregation

• Quality of Service (QoS)

• Spanning Tree

• VLAN Management

March 2005 CLI Basics 33

Prefix Prompt

You can set the CLI to display the current command prefix as
the command prompt by entering the following command:

-> prompt prefix

11 modify boot parameters
12 show history

Note that the most recent commands are displayed lower in the
list. For this reason, the show history command will always be
listed last.

After entering this command, your command prompt will
include current stored prefix information until a new prompt is
specified. For example, the following is a prompt for a user
who has begun configuring VLAN 32:

-> vlan 32

To set the prompt back to the default arrow ( -> ), enter the
following syntax, exactly as shown, at the prefix prompt:

prompt string ->

Command History

You can view a list of up to 30 of the most recently executed
commands via the show history command. For example:

-> show history
1 aaa authentication default local
2 password
3 system timezone pst
4 system daylight savings time enable
5 system time 14:58:00
6 system date 11/06/2002
7 system contact "JSmith [e-mail]"
8 system name EngSwitch3
9 system location "NMS Lab--NE Rack"
10 show system

You can recall commands from the history list by entering an
exclamation point ( ! ). For example:

-> !4

-> show temperature

The CLI prints the fourth command from the history list (in
this case, show temperature) at the CLI prompt.

You can also recall the last command in the history list by
entering two exclamation points ( !! ). For example:

-> !!

-> show history

To specify the number of commands displayed in the history
list (1 - 30), use the history size command. For example:

-> history size 10

To view the current history list settings, use the show history
parameters command. For example:

-> show history parameters
History size: 30
CurrentSize: 10
Index Range: 1-10

34 CLI Basics March 2005

Command Logging

OmniSwitch 8800 switches provide command logging. This
feature allows users to record up to 100 of the most recent
commands entered via Telnet and console sessions. In addi­tion to a list of commands entered, the results of each
command entry are recorded. Results include information such
as whether a command was executed successfully, or whether
a syntax or configuration error occurred.

Note. The command history feature differs from the
command logging feature in that command history buff-

ers up to 30 of the most recent commands. The command
information is not written to a separate log file. Also, the
command history feature includes only general keyword
syntax (i.e., it does not record full syntax, date and time,
session IP address, and entry results). For more informa­tion on command history, refer to page 34.

Refer to the sections below for more information on configur­ing and using CLI command logging. For detailed information
related to command logging commands, refer to the
OmniSwitch CLI Reference Guide.

When command logging is enabled via the command-log
enable syntax, a file called command.log is automatically
created in the switch’s /flash directory. Once enabled, configu­ration commands entered on the command line will be
recorded to this file until command logging is disabled.

The command.log file has a 66402 byte capacity. This capac­ity allows up to 100 of the most recent commands to be
recorded. Because all CLI command logging information is
archived to the command.log file, command history informa­tion will be lost if the file is deleted.

Note. The command.log file cannot be deleted while the

command logging feature is enabled. Before attempting to

remove the file, be sure to disable command logging.

For detailed information on command logging, refer to the
OmniSwitch 7700/7800/8800 Switch Management Guide.

Enabling Command Logging

By default, command logging is disabled. To enable command
logging on the switch, enter the following command:

-> command-log enable

March 2005 CLI Basics 35

Common CLI Commands

The following table lists some basic CLI commands that will
help you get acquainted with the CLI interface. Enter each
command exactly as shown. For complete descriptions of
these commands, refer to your OmniSwitch CLI Reference
Guide.

write memory Saves current configuration

changes to the /flash/working
directory’s boot.cfg file. For more
information, refer to page 38.

show running-directory Displays the current running direc-

tory. For more information, refer to

page 40.

vlan Creates a new VLAN.

show vlan Displays a list of VLANs config-

ured on the switch.

ip interface Configures an IP interface to

enable IP routing on a VLAN.

show chassis Displays basic configuration and

status information for the switch
chassis.

show module Displays basic information for all

modules installed in the chassis.
Modules include primary and sec­ondary CMMs and Network Inter­face (NI) modules.

show ni Displays basic hardware and status

information for NI modules
installed in the switch.

show cmm Displays basic hardware and status

information for CMM modules in
the chassis.

show fabric Displays the status and configura-

tion of Switch Fabric Modules
(SFMs).

show system Displays basic information about

the switch.

show microcode Displays the version of software

currently installed on the switch.

exit Ends the current Telnet or console

session.

session timeout Modifies the amount of time before

Telnet and console sessions will
time out.

36 CLI Basics March 2005

Offline Configuring

Scheduling a Configuration File to be Applied at a Later Time

You can configure OmniSwitch 8800 switches using an
ASCII-based text file. This is referred to as offline configur-
ing. With offline configuring, CLI commands may be typed
into a text document (referred to as a text-based configuration
file) and then uploaded and applied to the switch.

An ASCII-based configuration file can be viewed or edited at
any time using a standard text editor (e.g., WordPad). The
switch also offers its own text editing buffer, so a file can be
edited in the flash file directory without having to be down­loaded to a workstation.

Because they are portable, stand-alone documents, configura­tion files allow users to easily clone switch configurations.
Moreover, the ability to store a broad range of network infor­mation in a single text file facilitates troubleshooting, testing,
and overall network readability.

Syntax Checking

Offline configuration includes a syntax check feature. This
function will report syntax errors or typos that might cause a
command to be rejected by the switch when a configuration
file is applied.

You can apply a file to the switch immediately, or you can
schedule a file to be applied either at a specific date and time
or after a specific amount of time has passed. Timer sessions
can greatly facilitate maintenance tasks such as synchronized
batch updates.

Generating Snapshots of the Current Configuration

A generated snapshot captures the switch’s current configura­tion settings in a single text file. Captured configuration
settings can then be viewed or edited offline at any time. Trou­bleshooting is greatly facilitated, as aggregate network infor­mation can be read at a glance.

Snapshot files can be used as configuration files for a single
switch or for multiple switches. This allows easy cloning of
switch configurations for networks requiring multiple, simi­larly-configured switches. Simply place the snapshot file in the
appropriate directory of the switch(es) you want to configure
and use the CLI to apply the file.

For detailed information on offline configuring and the
features described above, refer to the “Working with Configu­ration Files” chapter in the OmniSwitch 7700/7800/8800
Switch Management Guide.

March 2005 CLI Basics 37

Files and Directories

Boot and Image Files

Although the switch’s flash memory can contain many file
types (e.g., log and snapshot files), there are three specific file
types that provide key switch and network functions. These
files include the boot.cfg file, the boot.params file, and image
(.img) files.

boot.params File

The boot.params file provides IP address, gateway, and mask
information for the switch’s Ethernet Management Port
(EMP). This information is required for direct Ethernet
connections to the switch’s primary CMM.

This file also contains default console port parameters (baud
rate, etc.) and can be modified via the modify boot parame-
ters CLI command.

In order to be read by the switch, the boot.params file must be
placed in the /flash directory. If the file is deleted for any
reason, a new boot.params file will be automatically gener­ated on the next system boot. However, all user-configured
information, such as IP address, gateway, and mask informa­tion, will be lost. Therefore, it is recommended that you keep a
backup copy of this file at all times.

boot.cfg File

The boot.cfg file stores your network configuration parame­ters. When you first boot the switch, no boot.cfg file is
present. This file is automatically generated when you first
issue a write memory command to save your configuration
changes. The file is then automatically placed in the

/flash/working directory.

Important. Your switch must be running from the

/flash/working directory in order to save changes to the

boot.cfg file. Refer to “Working and Certified Directo-

ries” on page 40 for more information.

Once the configuration parameters stored in the boot.cfg file
are considered tested and reliable, the file can be copied to the
/flash/certified directory and become part of the “last known
good” software for the switch.

If all copies of this file are deleted and a system boot occurs,
your network configuration will be lost. Therefore, it is recom­mended that you keep a backup copy of this file at all times.

38 Files and Directories March 2005

Image Files

Image files (those files with .img extensions) contain execut-
able code that provides support for the system, NI modules,
and network functions. In other words, they serve as essential
drivers for switch and network operations.

Although these files may be backed up to the root flash direc­tory or any user-defined subdirectory, they must be present in
the /flash/working and /flash/certified directories for the
switch to operate and pass traffic.

If you delete all copies of an image file, you will be required to
contact Alcatel Customer Support for replacements. There­fore, it is recommended that you keep backup copies on your
computer’s hard drive or a locally-accessible server.

For a complete list of OmniSwitch 8800 image files, along
with their functions, refer to the table below.

Eos.img Contains the OmniSwitch 8800 operating

system software.

Ebase.img Contains base code for the switch.

Erelease.img Contains release number information for

the system software package.

El2eth.img Provides support for Layer 2 switching

functions.

Erout.img Provides support for Layer 3 routing

functions.

Eqos.img Provides Quality of Service (QoS) func-

tionality.

Eeni.img Provides support for 10/100, Fast Ether-

net, and Gigabit Ethernet.

Ediag.img Provides enhanced hardware diagnostics

for the switch.

Eadvrout.img Alcatel’s Advanced Routing software

package.

Esecu.img Provides enhanced security features for

the switch (e.g., Authenticated VLANs
(AVLANs).

Eweb.img Provides support for the WebView soft-

ware application.

Ewebl2eth.img Provides WebView configuration of

Layer 2 features.

Ewebrout.img Provides WebView configuration of

basic routing features.

Ewebqos.img Provides WebView configuration of

Quality of Service (QoS) features.

Ewebadvrout.img Enables WebView configuration of Alca-

tel’s Advanced Routing.

Ewebsecu.img Provides WebView configuration of

enhanced security features for the switch.

March 2005 Files and Directories 39

Working and Certified Directories

Once the /flash/working directory’s configuration and image
files are road-tested and considered valid and reliable for your
network, they can be copied to the /flash/certified directory.

OmniSwitch 8800 switches are shipped with 32 MB of flash
memory. This memory is used to store files, including boot
and image files, that are used for switch operations.

The /flash directory contains two subdirectories: /working and
/certified. These directories work together to provide the
image rollback resiliency feature. Image rollback allows the
switch to return to a prior “last known good” version of soft­ware in the event of a system software problem.

Working Directory

Working Directory

Intended for: Files that are being configured
and tested. Once these files are considered
valid and reliable, they can be copied to
the Certified directory.

On reload: If the Working and Certified
directories are identical, the switch will
automatically run from software in this
directory. If the two directories are not
identical, you can instruct the switch to run
from the Working directory by issuing the
reload working command.

Saving changes: You can save config­uration changes to the Working directory
via the write memory command.

Certified Directory

Certified Directory

Intended for: Reliable, Tested configuration
and image files. The switch will roll back
to this software in the event of a system
software error.

On reload: By default, the switch will use
the software in this directory if there are
any differences between the Working and
Certified directories.

Saving changes: You cannot save config­uration changes to the Certified directory.
To save your changes, be sure that your
switch is operating from the Working
directory.

The software in the /flash/certified directory should be treated
as the “gold master” for the switch. When you place configu­ration and image files in this directory, you are “certifying”
them as tested and reliable. If the switch is running from the
/flash/working directory and experiences a software problem,
it will “roll back” to the last known good software in the
/flash/certified directory on the next reboot.

The /flash/working directory is intended for software that is
still being configured for your network. Changes made while
configuring your switch are saved to the boot.cfg file in the
/flash/working directory.

40 Files and Directories March 2005

How can I tell which directory the switch is currently using?

When you first boot the switch, the /flash/working directory is
used; this allows you to save your initial configuration changes
to the boot.cfg file. However, subsequent boots may result in
your switch running from the /flash/certified directory. There­fore, verifying the current running directory is a key step any
time you are configuring or monitoring the switch.

View the current directory by entering the show running-
directory command. For example:

tested, the contents of the /flash/working directory can be
copied to the /flash/certified directory via the copy working
certified command.

What happens when the switch boots?

During the boot process, the switch compares the contents of
the /flash/working and /flash/certified directories. Based on
this comparison, the switch determines which directory to use
as its running software.

Working and Certified Are Identical

-> show running-directory

CONFIGURATION STATUS

Running CMM : PRIMARY,
CMM Mode : DUAL CMMs,

If the software in the /flash/working and /flash/certified
directories are completely identical, the switch considers the
software in both directories to be equally reliable. In this case,
the switch will run from the /flash/working directory.

Current CMM Slot : A,
Running configuration : WORKING,
Certify/Restore Status : CERTIFY NEEDED

SYNCHRONIZATION STATUS

Flash Between CMMs : NOT SYNCHRONIZED,
Running Configuration : SYNCHRONIZED,
NIs Reload On Takeover : ALL NIs

In this example, the switch is using the /flash/working direc-
tory.

Can I save changes to the Certified directory?

Working and Certified
contents are identical.

Wor king
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

The switch runs
from Working.

Wor king
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

No. The /flash/certified directory is intended to store only
tested, reliable configuration and image files. Configuration
changes must be saved to the boot.cfg file in the
/flash/working directory. Once those changes have been road-

March 2005 Files and Directories 41

When the switch is running from the /flash/working directory
software, configuration changes can be saved via the
write memory command.

Working and Certified Are Different

If the software in the /flash/working directory differs even
slightly from the software in the /flash/certified directory, the

switch will automatically run from the /flash/certified direc-
tory

Working and Certified
contents are different.

Wor king
Directory

revised_boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

The switch runs
from Certified.

Wor king
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

When the switch runs from the /flash/certified directory,
configuration changes cannot be saved via the write memory
command

My Working and Certified directories are different. Can I force a reboot from the Working directory?

Yes. If its configuration and image files are known to be reli­able, you can override the default and initiate a reboot from the

/flash/working directory. This is done via the reload work-
ing command. For more information, refer to your

OmniSwitch CLI Reference Guide.

The reload working
command overrides
the default; the
switch runs from
Working.

Wor king
Directory

revised_boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

Working and Certified
contents are different.

Work ing
Directory

revised_boot.cfg
Ebase.img
Erelease.img
Etc.

Certified
Directory

boot.cfg
Ebase.img
Erelease.img
Etc.

Note. For detailed information on using directories, refer

to the “Managing CMM Directory Content” chapter in the

OmniSwitch 7700/7800/8800 Switch Management Guide.

42 Files and Directories March 2005

Loading Software

The following section describes the procedure for loading new
release software to your switch. Note that the procedure varies
slightly for non-redundant (single CMM) and redundant (dual
CMM) configurations. Follow the steps that apply to your
system.

Note. For detailed information on loading software and
working with directories in both non-redundant and redun­dant CMM configurations, refer to the “Managing CMM
Directory Content” chapter in the OmniSwitch 7700/7800/
8800 Switch Management Guide.

Non-Redundant Configurations

1 Verify that all required image files from the new soft-

ware release are located on your computer’s hard drive or
a locally-accessible server.

2 Establish an FTP session to the switch, then access the

/flash/working directory.

Note. Before attempting to establish an FTP session, be

sure that you have first unlocked the FTP session type via
the aaa authentication command. Otherwise, an FTP
login error will occur. See “Unlocking Session Types” on

page 25 for more information.

3 Using your FTP client or the CLI’s rm command,

delete all .img files from the /flash/working directory.

You can use the asterisk (*) wildcard to delete all .img

files at once. For example:

-> rm working/*.img

Important. Do not delete the boot.cfg file. Otherwise,

any configuration changes you have saved will be lost.

Also, do not delete files from the /flash/certified direc-

tory.

4 Using your FTP client, upload all required .img files

from the new software release to the /flash/working direc-

tory.

/flash/

FTP

Working Directory

boot.cfg

Ebase.img
Eos.img
Erelease.img
Eeni.img
Additional

required files

March 2005 Loading Software 43

5 Use the install command after the software files have

been transferred to the switch via FTP. For example:

-> install /flash/working/*.img

Redundant Configurations

1 Verify that the OK1 LED is solid green and the OK2

LED is flashing green on both the primary and secondary

CMM modules.

Note. For more information on the install command, refer
to the OmniSwitch 7700/7800/8800 Switch Management
Guide or the OmniSwitch CLI Reference Guide.

6 Reload the switch from the /flash/working directory.

To do this, enter

-> reload working no rollback-timeout

at the CLI prompt.

Note. This reload process will take a few moments to
complete.

Following the reload, the switch will come up running
from the /flash/working directory (i.e., the new release
software) until the next system reboot. Meanwhile, the
software in the /flash/certified directory remains
unchanged and available as a last known good version if
an error should occur with the new software.

Once the release software is considered valid and reliable
with your network configuration, the contents of the

/flash/working directory can be copied to the
/flash/certified directory via the copy working certified

command.

2 Next, verify that all required image files from the new

software release are located on your computer’s hard drive

or a locally-accessible server.

3 Establish an FTP session to the switch, then access the

/flash/working directory.

Note. Before attempting to establish an FTP session, be

sure that you have first unlocked the FTP session type via

the aaa authentication command. Otherwise, an FTP

login error will occur. See “Unlocking Session Types” on

page 25 for more information.

4 Using your FTP client or the CLI’s rm command,

delete all .img files from the /flash/working directory on

the primary CMM. (To determine whether you are logged

into the primary CMM, use the show running-directory

command.) You can use the asterisk (*) wildcard to delete

all .img files at once. For example:

-> rm working/*.img

Important. Do not delete the boot.cfg file. Otherwise,

any configuration changes you have saved will be lost.

Also, do not delete files from the /flash/certified direc-

tory.

44 Loading Software March 2005

5 Using your FTP client, upload all required .img files

from the new software release to the primary CMM’s
/flash/working directory.

6 Use the install command after the software files have

been transferred to the switch via FTP. For example:

-> install /flash/working/*.img

Note. For more information on the install command, refer
to the OmniSwitch 7700/7800/8800 Switch Management
Guide or the OmniSwitch CLI Reference Guide.

7 Reload the switch from the /flash/working directory.

To do this, enter

-> reload working no rollback-timeout

at the CLI prompt.

Note. This reload process will take a few moments to
complete.

During this reload, the secondary CMM takes over the primary
role and the switch runs from the /flash/working directory
(i.e., the new release software) until the next system reboot.
Meanwhile, the software in the /flash/certified directory
remains unchanged and available as a last known good version
if an error should occur with the new software.

Once the release software is considered valid and reliable with
your network configuration, the contents of the /flash/work-
ing directory can be copied to the /flash/certified directory of
each CMM by entering the following command:

-> copy working certified flash-synchro

This command provides two functions. It copies all contents
from /flash/working to the /flash/certified directory on the
primary CMM, and it copies all directory contents from the
primary CMM to the secondary CMM and synchronizes the
two modules. This helps to ensure effective CMM redundancy.

Note. The process initialized by the copy working

certified flash-synchro command will take a few

moments to complete.

March 2005 Loading Software 45

Using WebView

The switch can be configured and monitored using WebView,
Alcatel’s Web-based device management tool. WebView soft­ware is pre-installed in the switch; you are not required to load
additional software.

Note. Although WebView software is pre-installed, you
must first enable HTTP sessions for your switch before
you can log in. Refer to “Unlocking Session Types” on

page 25 for more information.

Browser Compatibility

WebView has been tested on the following Web browsers:

• Internet Explorer 6.0 for Windows 2000, Windows NT,

Windows XP

• Netscape 4.79 for Solaris 2.8, HP-UX 11.0

• Netscape 7.1 for Windows 2000, Windows NT,

Solaris 2.8

Required Image Files

In order to access WebView, the following image files must be
present in the current running directory:

• Eweb.img

• Ewebl2eth.img

• Ewebrout.img

• Ewebqos.img

• Ewebadvrout.img

• Ewebsecu.img

Refer to “Image Files” on page 39 for more information.

46 Using WebView March 2005

Logging In to WebView

3 Enter the user name and password at the login prompt.

Note. Before attempting to establish a WebView session,
be sure that you have first unlocked the HTTP session
type via the aaa authentication command. Otherwise, a
login error will occur. See “Unlocking Session Types” on

page 25 for more information.

To access WebView and log in to a switch:

1 Open any Alcatel-tested Web browser (see page 46).

2 Enter the switch’s IP address in the browser’s

“Address” text field (“Location:” for Netscape users). The
login screen displays:

Remember, if you have already changed the user name and
password for your switch, be sure to use the new information.
If you have not changed your user name or password, the
factory defaults are admin and switch, respectively. Refer to
the “Managing Switch User Accounts” chapter of your
OmniSwitch 7700/7800/8800 Switch Management Guide for
information on modifying the default user name and password.

Navigating WebView

After you have successfully logged in, the Chassis Manage­ment home page displays:

The Chassis Management home page provides a physical
representation of the switch, as well as basic system informa­tion. This is the main launching point for WebView.

March 2005 Using WebView 47

Navigate the application by clicking on the “Configuration
Group” buttons in the left-hand toolbar

Main “Configuration
Group” Toolbar.

(In this case, the group
“Health” has been selected.)

Refine your navigation by selecting “Configuration Options”
for each group from the items displayed in the grey, horizon­tal navigation bar:

“Configuration
Options” Toolbar.

Site Maps. WebView also provides site maps for each

configuration group. Site maps allow you to view

complete page contents under each feature. By providing

quick, easy access to specific pages, site maps can reduce

time spent searching through the WebView application.

To access site maps, click the “Site Map” link included on

each configuration group Home page, (e.g., Health).

(In this case, the option
“Device” has been selected.)

48 Using WebView March 2005

Online Help

Troubleshooting

General online help is available through the main Help link
located in the top WebView banner:

General Help Link

Detailed, context-based help is provided for each status table
and configuration dialog window:

Context-specific Help
button.

(In this case, for the VLAN
Administration table.)

Additional Information

The WebView login screen does not display.

This suggests either a physical or network connection issue.
Try the following options:

• Be sure that you have a good physical Ethernet cable

connection to the Ethernet port used for managing the
switch (EMP or NI port).

• Be sure your computer has a valid Ethernet connection

and IP address. See page 24 for information on config­uring the IP address for the EMP.

• Verify that all required WebView image files are

installed in the current running directory. See page 46
for more information.

The login screen displays, but my login attempt fails.

This suggests either a user name and password or Authenti­cated Switch Access error. Try the following options:

• Check that you are using the correct user name and

password. If you have already changed the user name
and password for your switch, be sure to use the new
information. If you have not changed the user name
and password, the factory defaults are admin and
switch, respectively.

• Be sure that you have “unlocked” HTTP sessions on

the switch. To unlock HTTP sessions, enter the follow­ing command:

For more information on using WebView, refer to “Using

-> aaa authentication http local

WebView” in the OmniSwitch 7700/7800/8800 Switch
Management Guide.

March 2005 Using WebView 49

See page 25 for information on unlocking session types.

Hardware Basics

Chassis Slot Numbering

The term “slot” refers to the position at which a module is
installed in the chassis. On the front side of the chassis, CMM
slot positions are designated as Slot A and Slot B. NI slot
numbers range from 1 to 16.

On the back side of the chassis SFM slots are numbered 1
through 5, from top to bottom. Power supply bays are also
given specific slot numbers. Slot numbers are designated PS-1
through PS-4, from left to right.

1234

5678

A

B

1314 15 169101112

OmniSwitch 8800 Front Slot Numbering

50 Hardware Basics March 2005

Chassis Management Module (CMM)

The Chassis Management Module (CMM) is the management
unit for OmniSwitch 8800 switches. In its role as the manage­ment unit, the CMM provides key system services, including:

• Console, modem, and Ethernet management port

connections to the switch

• Software and configuration management, including the

Command Line Interface (CLI)

• Web-based management (WebView)

1
2
3
4
5

PS1 PS2 PS3 PS4

1

2

3

4

5

• SNMP management

• Power management

• Temperature management

• Switch diagnostics

• Important availability features, including redundancy

(when used in conjunction with another CMM) and

PS-1 PS-2 PS-3 PS-4

image rollback.

OmniSwitch 8800 Back Slot Numbering

March 2005 Hardware Basics 51

CMM Redundancy

CMM redundancy is an important resiliency feature. For
CMM redundancy, two fully-operational CMM modules must
be installed in the chassis at all times.

When two CMMs are running in the switch, one CMM has the
primary role and one CMM has the secondary role at any
given time. The primary CMM manages the current switch
operations while the secondary CMM provides backup (also
referred to as “failover”).

Note. By default, the CMM in slot A automatically
assumes the primary role. Refer to pages 50 or 52 for
CMM slot A and B positions.

CMM Slot Locations

CMM Slot A

OS8800-CMM

OS-ENI-C24

OS-ENI-C24

OS-ENI-C24

OS-ENI-C24

OK1

OK1

OK2

OK2

2

2

1

1

3

3

5

5

7

7

9

9

11

11

12

12

14

14

13

13

15

15

17

17

19

19

21

21

23

23

24

24

OK1

OK1

OK1

OK2

OK2

OK2

2

2

1

1

PRI

SEC

3

3

5

5

TEMP

STATUS

7

7

9

9

1

FAN

2

11

11

3

12

12

CONSOLE

14

14

/ MODEM

13

13

15

15

17

17

ENET

19

19

21

21

LINK

23

23

ACT

24

24

OK1

OK2

2

1

3

5

7

9

11

12

14

13

15

17

19

21

23

24

OK2

OK2

OK2

2

2

2

1

1

1

3

3

3

5

5

5

7

7

7

9

9

9

11

11

11

12

12

12

14

14

14

24

13

13

13

15

15

15

17

17

17

19

19

19

21

21

21

23

23

23

24

24

OS-ENI-C24

OS-ENI-C24

OS-ENI-C24

OS-ENI-C24

OK1

OK1

OK1

If the primary CMM fails or goes offline for any reason, the
secondary CMM is notified. The secondary CMM then auto­matically assumes the primary role.

For important information on CMM redundancy, refer to your
OmniSwitch 8800 Hardware Users Guide.

OS-GNI-U8

OS8800-CMM

OS-GNI-C8

OK1

OK2

ACT

ACT

1

LINK

LINK

ACT

ACT

2

LINK

LINK

ACT

ACT

3

LINK

LINK

ACT

ACT

4

LINK

LINK

ACT

ACT

5

LINK

LINK

ACT

ACT

6

LINK

LINK

ACT

ACT

7

LINK

LINK

ACT

ACT

8

LINK

LINK

OS-GNI-C8

OS-GNI-C8

OS-GNI-C8

OK1

OK1

OK2

OK2

ACT

1

1

LINK

ACT

2

2

LINK

ACT

3

3

LINK

ACT

4

4

LINK

ACT

5

5

LINK

ACT

6

6

LINK

ACT

7

7

LINK

ACT

8

8

LINK

OK1

OK1

OK1

OK2

OK2

OK2

1

ACT

LINK

ACT

LINK

ACT

LINK

ACT

LINK

ACT

LINK

ACT

LINK

ACT

LINK

ACT

LINK

A

A

1

C

C

PRI

T

T

LINK

2

SEC

2

A

A

C

C

3

T

T

TEMP

LINK

4

STATUS

3

A

A

C

C

T

T

LINK

1

2

FAN

4

3

A

A

C

C

T

T

LINK

CONSOLE
/ MODEM

5

5

A

A

C

C

T

T

LINK

6

6

A

A

7

C

C

T

T

LINK

ENET

8

7

A

A

C

C

T

T

LINK

LINK

8

ACT

A

A

C

C

T

T

LINK

OS-GNI-U8

OS-GNI-U8

OS-GNI-U8

OK1

OK1

OK1

OK2

OK2

OK2

1

1

1

A

A

C

C

T

T

LINK

LINK

LINK

2

2

2

A

A

C

C

T

T

LINK

LINK

LINK

3

3

3

A

A

C

C

T

T

LINK

LINK

LINK

4

4

4

A

A

C

C

T

T

LINK

LINK

LINK

5

5

5

A

A

C

C

T

T

LINK

LINK

LINK

6

6

6

A

A

C

C

T

T

LINK

LINK

LINK

7

7

7

A

A

C

C

T

T

LINK

LINK

LINK

8

8

8

A

A

C

C

T

T

LINK

LINK

LINK

CMM Slot B

52 Hardware Basics March 2005

CMM Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid green when powered on
and the CMM has passed hardware diagnostic tests. Displays
solid amber when powered on and the CMM has failed hardware
diagnostic tests.

OK2. Software Status. Blinks green when the CMM is opera­tional. Displays solid amber when a system software failure
occurs. Blinks amber when the software is in a transitional state
(e.g., when software is being downloaded to the switch).

Temperature/Fan Status LEDs

TEMP. Displays solid green when the CMM is operating within
the allowed ambient temperature range. Displays solid amber if a
temperature error occurs (i.e., the CMM is operating outside the
temperature range).

STATUS. Displays solid green when the Switch Fabric Modules
(SFMs) and power supplies are operating normally. Displays solid
amber if there is an error in an SFM or power supply.

FAN 1. Displays solid green when the two fans in the left front
fan tray are running at normal speed. Displays solid amber if a fan
error occurs (i.e., one or more fans are not running at normal
speed).

FAN 2. Displays solid green when the two fans in the right front
fan tray are running at normal speed. Displays solid amber if a fan
error occurs (i.e., one or more fans are not running at normal
speed).

FAN 3. Displays solid green when the three fans in the rear fan
tray are running at normal speed. Displays solid amber if a fan
error occurs (i.e., one or more fans are not running at normal
speed).

Module
Status
LEDs

OK1

OK2

PRI

SEC

TEMP

STATUS

1

2

3

CONSOLE
/ MODEM

ENET

LINK

ACT

FAN

OS8800-CMM

Module
Status
LEDs

Redundancy LEDs
PRI. Displays solid green when the CMM is the

primary (active) management module.

SEC. Displays solid green when the CMM is the
secondary (backup) management module.

Ethernet Management Port LEDs
LINK. Link Integrity Status. Displays solid green

when an Ethernet cable connection exists at the
CMM’s Ethernet Management Port.

ACT. Flashes green as data is transmitted or
received on the CMM’s Ethernet Management Port.

Console/Modem Port. The CMM’s front panel
provides one RS232 port for console or modem
connections. By default, this female DB-9 connec­tor provides a DCE console connection. However,
by changing the onboard jumper setting, the port
can be changed to a DTE modem connection.

Ethernet Management Port (EMP). The CMM’s
front panel also provides one Ethernet 10/100BaseT
port (copper RJ-45). This port provides out-of-band
network management and can be used for Telnet
sessions, switch diagnostics, and for downloading
software to the switch.

This 10/100BaseT port supports both 10BaseT and
100BaseT with auto-negotiation through the RJ-45
connector.

March 2005 Hardware Basics 53

Switch Fabric Module (SFM)

OS8800-SFM Switch Fabric Modules (SFMs) allow for
communication between modules such as Network Interfaces
(NIs) and CMMs on the OmniSwitch 8800 product. SFMs are
the link between the other removable components of a switch.
A complete fabric consists of four SFM modules plus one
optional module for redundancy

SFMs are located in the rear of the switch in numbered slots
specifically designed for SFMs. NIs or CMMs will not func­tion in SFM slots.

The fabric board slots are numbered 1 to 5. In order for the
switch to function, slots 1 through 4 must contain an SFM.
Slot 5 is used for SFM redundancy, in the event one of the
other SFMs fail. The switch will function if slot 5 is empty.

SFM Redundancy

The OmniSwitch 8800 allows for redundancy in the Switch
Fabric Modules. In order for the switch to operate, there must
be four working SFMs in place. A fifth SFM can be added in
case one of the four fails.

If an SFM fails, and a redundant SFM is in place, then the
redundant SFM takes over for the failed SFM, with no loss of
switch running time. A warning message is sent to notify the
switch administrator that a failure has occurred and that the
redundant SFM has taken over.

For important information on SFM redundancy, refer to the
“Switch Fabric Module (SFM)” chapter in your OmniSwitch
8800 Hardware Users Guide.

.

SFM Slot Locations

OS8800-SFM

OS8800-SFM

OS8800-SFM

OS8800-SFM

OS8800-SFM

CAUTION:THIS UNIT MAY BE EQUIPPED

WITH FOUR POWER SUPPLIE CORDS. TO REDUCE
THE RISK OF ELECTRICAL SHOCK, DISCONNECT
ALL POWER SUPPLY CORDS BEFORE
SERVICING UNIT.

230V
50/60Hz, 8.0 A

OS8800-SFM

OS8800-SFM

OS8800-SFM

OS8800-SFM

OS8800-SFM

OK1 OK2

OK1 OK2

OK1 OK2

OK1 OK2

OK1 OK2

TEMP

TEMP

FAIL

FAIL

DC OK

DC OK

AC OK

AC OK

!

!

ATTENTION: CET APPAREIL COMPORTE

PLUS D'UN CORDON D'ALIMENTATION. AFIN DE
PREVENIR LES CHOCS ELECTRIQUES, DEBRANCHE
TOUS LES CORDONS D'ALIMENTATION AVANTE DE
FAIRE LA REPARATION.

CAUTION:THIS UNIT MAY BE EQUIPPED

WITH FOUR POWER SUPPLIE CORDS. TO REDUCE
THE RISK OF ELECTRICAL SHOCK, DISCONNECT
ALL POWER SUPPLY CORDS BEFORE
SERVICING UNIT.

230V
50/60Hz, 8.0 A

ATTENTION: CET APPAREIL COMPORTE

PLUS D'UN CORDON D'ALIMENTATION. AFIN DE
PREVENIR LES CHOCS ELECTRIQUES, DEBRANCHE
TOUS LES CORDONS D'ALIMENTATION AVANTE DE
FAIRE LA REPARATION.

CAUTION:THIS UNIT MAY BE EQUIPPED

WITH FOUR POWER SUPPLIE CORDS. TO REDUCE
THE RISK OF ELECTRICAL SHOCK, DISCONNECT
ALL POWER SUPPLY CORDS BEFORE
SERVICING UNIT.

230V
50/60Hz, 8.0 A

OK1 OK2

OK1 OK2

OK1 OK2

OK1 OK2

OK1 OK2

TEMP
FAIL

DC OK

AC OK

1

2

3

4

5

TEMP

TEMP

FAIL

FAIL

DC OK

DC OK

AC OK

AC OK

!

!

CAUTION:THIS UNIT MAY BE EQUIPPED

ATTENTION: CET APPAREIL COMPORTE

ATTENTION: CET APPAREIL COMPORTE

WITH FOUR POWER SUPPLIE CORDS. TO REDUCE

PLUS D'UN CORDON D'ALIMENTATION. AFIN DE

PLUS D'UN CORDON D'ALIMENTATION. AFIN DE

THE RISK OF ELECTRICAL SHOCK, DISCONNECT

PREVENIR LES CHOCS ELECTRIQUES, DEBRANCHE

PREVENIR LES CHOCS ELECTRIQUES, DEBRANCHE

ALL POWER SUPPLY CORDS BEFORE

TOUS LES CORDONS D'ALIMENTATION AVANTE DE

TOUS LES CORDONS D'ALIMENTATION AVANTE DE

SERVICING UNIT.

FAIRE LA REPARATION.

FAIRE LA REPARATION.

230V
50/60Hz, 8.0 A

TEMP
FAIL

DC OK

AC OK

TEMP
FAIL

DC OK

AC OK

SFM Slots. The Slots 1
through 5, occupied, are
shown.

1

2

3

4

5

TEMP
FAIL

DC OK

AC OK

54 Hardware Basics March 2005

SFM Front Panel

OS8800-SFM

OK1 OK2

Module
Status
LEDs

Module Status LEDs

OK1. Hardware Status. Displays solid green when powered on
and the SFM has passed hardware diagnostic tests. Displays
solid amber when powered on and the SFM has failed hardware
diagnostic tests.

OK2. Software Status. Blinks green when the SFM is opera­tional. Displays solid amber when a system software failure
occurs. Displays blinking amber when the SFM unit is a redun­dant unit.

March 2005 Hardware Basics 55

Network Interface (NI) Modules

The following section outlines front panel information for
Network Interface (NI) modules, including LED and port
descriptions. For detailed information on OS8-ENI-C24, OS8­GNI-U8, OS8-GNI-C8, OS8-GNI-U24, OS8-GNI-C24, and
OS8-10GNI-UR1 modules, refer to your OmniSwitch 8800
Hardware Users Guide.

ENI Modules

Ethernet Network Interface (ENI) modules provide Ethernet
connectivity and are available in the following port configura­tion:

• OS8-ENI-C24. Provides 24 twisted-pair RJ-45 ports,

auto-negotiating and individually configurable as 10BaseT
or 100BaseTX.

GNI Modules

The Gigabit Ethernet Network Interface (GNI) module
provides up to eight 1000 Mbps (1 Gbps) connections per
module. GNI modules can be used for backbone connections
in networks where Gigabit Ethernet is used as the backbone
media. GNI modules can also be used in the wiring closet for
connections to workstations and other devices.

• OS8-GNI-C8. Provides 8 wire-rate twisted-pair 1 Gbps

RJ-45 ports.

• OS8-GNI-U24. Provides 24 high-density 1 Gbps Mini-

GBIC ports that use LC connectors.

• OS8-GNI-C24. Provides 24 high-density twisted-pair

10/100/1000 Mbps RJ-45 ports.

Miniature Gigabit Interface Converters (MiniGBICs)

The OS8-GNI-U8 module provides 8 Miniature Gigabit Inter­face Converters (MiniGBIC) slots and the OS8-GNI-U24
provides 24 MiniGBIC slots. A MiniGBIC is a Gigabit Ether­net port module that is hot-pluggable—i.e., it can be installed
or removed while the GNI is powered on and operating with­out the risk of damage to the MiniGBIC module or the host
circuitry.

When a MiniGBIC is installed, the switch automatically gath­ers basic MiniGBIC information via the connector’s serial
EEPROM interface. This information includes the Mini­GBIC’s capabilities, standard interfaces, manufacturer, and
other information.

• OS8-GNI-U8. Provides 8 wire-rate 1 Gbps MiniGBIC

ports that use LC connectors.

56 Hardware Basics March 2005

The following MiniGBIC types are available for OS8-GNI-U8
and OS8-GNI-U24 modules:

• MINIGBIC-SX—1000BaseSX multimode fiber,

supports distances up to 550 meters; uses LC connectors

• MINIGBIC-LX—1000BaseLX single mode fiber,

supports distances up to 10 km; uses LC connectors

• MINIGBIC-LH-70—1000BaseLH long haul single

mode fiber, supports distances up to 70 km; uses LC
connectors

Customers should use only Alcatel-provided MiniGBIC
modules. Third party MiniGBIC modules not provided by
Alcatel are not guaranteed to work properly.

10GNI Modules

OmniSwitch 8800 10 Gigabit Network Interface (10GNI)
modules provide one redundant wire-rate 10000 Mbps (10
Gbps) connection per module. In addition, 10GNI modules can
be used in enterprise applications including backbone connec­tions in networks where 10 Gigabit Ethernet is used as the
backbone media.

• OS8-10GNI-UR1. Provides two redundant Xenpak

slots acting as one port. (Only one port can be active at a
time.)

Xenpaks

The OS8-10GNI-UR1 provides two Xenpak slots acting as one
redundant port. A Xenpak is a 10 Gigabit Ethernet port
module that is hot-pluggable—i.e., it can be installed or
removed while the NI is powered on and operating without the
risk of damage to the MiniGBIC module or the host circuitry.

The following Xenpak types are available for OS8-10GNI­UR1 module:

• OM-10GNI-SR— 10GBASE-S multimode 850 nanom-

eters (nm) fiber with a serial (one color of wavelength)
transceiver, supports distances up to 300 meters over multi­mode fiber; uses SC connectors (high modal bandwidth
fiber is required to reach 300 meters)

• OM-10GNI-LR— 10GBASE-L single mode 1310 nm

fiber with a serial transceiver, supports distances up to 10
km over single mode fiber; uses SC connectors

• OM-10GNI-ER—10GBASE-E single mode 1550 nm

fiber with a serial transceiver, supports distances up to 40
km over single mode fiber; uses SC connectors

Customers should use only Alcatel-provided Xenpak modules.
Third party Xenpak modules not provided by Alcatel are not
guaranteed to work properly.

March 2005 Hardware Basics 57

OS8-ENI-C24 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid green when powered
on and the ENI has passed hardware diagnostic tests. Dis­plays solid amber when powered on and the ENI has failed
hardware diagnostic tests.

OK2. Software Status. Blinks green when the ENI is opera­tional and has successfully loaded software. Displays solid
amber when powered on and the ENI has failed to load soft­ware.

Ethernet Port LEDs

Each Ethernet port has a built-in corresponding LED. This
LED indicates the link and activity status for each Ethernet
port. The LED displays green when a valid Ethernet cable
connection exists. Flashes green as data is transmitted or
received on the port.

Refer to the illustration below for the LED locations on each
Ethernet port.

Module
Status
LEDs

OS-ENI-C24

OK1

OK2

2

1

3

5

7

9

11

12

14

13

15

17

19

21

23

24

Ethernet Ports

The OS8-ENI-C24 module provides 24 Ethernet ports.
These ports are twisted-pair and are individually con­figurable as 10BaseT or 100BaseTX. The ports use
RJ-45 connectors.

LED Location

Ethernet Port

58 Hardware Basics March 2005

OS8-GNI-U8 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid
green when powered on and the GNI has
passed hardware diagnostic tests. Displays
solid amber when powered on and the GNI
has failed hardware diagnostic tests.

OK2. Software Status. Blinks green when
the GNI is operational and has successfully
loaded software. Displays solid amber
when powered on and the GNI has failed to
load software.

Gigabit Ethernet Port LEDs

ACT. Activity Status. Flashes green when
data is transmitted or received on the corre­sponding Gigabit Ethernet port.

LINK. Link Integrity Status. Displays solid
green when a fiber cable connection exists
at the corresponding Gigabit Ethernet port.

Module
Status
LEDs

OS-GNI-U8

OK1

OK2

1

A
C
T

LINK

2

A
C
T

LINK

3

A
C
T

LINK

4

A
C
T

LINK

5

A
C
T

LINK

6

A
C
T

LINK

7

A
C
T

LINK

8

A
C
T

LINK

Gigabit Ethernet Ports

The OS8-GNI-U8 module provides eight (8) Mini­GBIC slots. These slots support the following Mini­GBIC types:

• MINIGBIC-SX—1000BaseSX multimode fiber,

supports distances up to 550 meters; uses LC
connectors

• MINIGBIC-LX—1000BaseLX single mode

fiber, supports distances up to 10 km; uses LC
connectors

• MINIGBIC-LH-70—1000BaseLH long haul

fiber, supports distances up to 70 km; uses LC
connectors.

Note

Refer to your OmniSwitch 8800 Hardware Users
Guide for information on proper handling of LC con-

nectors and fiber-optic cable.

March 2005 Hardware Basics 59

OS8-GNI-C8 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid
green when powered on and the module has
passed hardware diagnostic tests. Displays
solid amber when powered on and the mod­ule has failed hardware diagnostic tests.

OK2. Software Status. Blinks green when
the GNI is operational and has successfully
loaded software. Displays solid amber
when powered on and the module has failed
to load software.

Gigabit Ethernet Port LEDs

ACT. Activity Status. Flashes green when
data is transmitted or received on the corre­sponding Gigabit Ethernet port.

LINK. Link Integrity Status. Displays solid
green when a fiber cable connection exists
at the corresponding Gigabit Ethernet port.

Module
Status
LEDs

OS-GNI-C8

OK1

OK2

ACT

1

LINK

ACT

2

LINK

ACT

3

LINK

ACT

4

LINK

Ethernet Ports

The OS8-GNI-C8 module provides eight 1000BaseT
Gigabit Ethernet ports. The ports use RJ-45 connectors.

ACT

5

LINK

ACT

6

LINK

ACT

7

LINK

ACT

8

LINK

60 Hardware Basics March 2005

OS8-GNI-U24 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid
green when powered on and the GNI has
passed hardware diagnostic tests. Displays
solid amber when powered on and the GNI
has failed hardware diagnostic tests.

OK2. Software Status. Blinks green when
the GNI is operational and has successfully
loaded software. Displays solid amber
when powered on and the GNI has failed to
load software.

Gigabit Ethernet Port LEDs

ACT. Activity Status. Flashes green when
data is transmitted or received on the corre­sponding Gigabit Ethernet port.

LINK. Link Integrity Status. Displays solid
green when a fiber cable connection exists
at the corresponding Gigabit Ethernet port.

Module
Status
LEDs

OS8-GNI-U24

OK1

OK2

113

214

315

416

517

618

719

820

921

10 22

11 23

24

12

Gigabit Ethernet Ports

The OS8-GNI-U24 module provides twenty-four (24)
MiniGBIC slots. These slots support the following
MiniGBIC types:

• MINIGBIC-SX—1000BaseSX multimode fiber,

supports distances up to 550 meters; uses LC
connectors

• MINIGBIC-LX—1000BaseLX single mode

fiber, supports distances up to 10 km; uses LC
connectors

• MINIGBIC-LH-70—1000BaseLH long haul

fiber, supports distances up to 70 km; uses LC
connectors.

Note

Refer to your OmniSwitch 8800 Hardware Users
Guide for information on proper handling of LC con-

nectors and fiber-optic cable.

March 2005 Hardware Basics 61

OS8-GNI-C24 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid
green when powered on and the module has
passed hardware diagnostic tests. Displays
solid amber when powered on and the mod­ule has failed hardware diagnostic tests.

OK2. Software Status. Blinks green when
the GNI is operational and has successfully
loaded software. Displays solid amber
when powered on and the module has failed
to load software.

Gigabit Ethernet Port LEDs

Each Gigabit Ethernet port has two built-in
corresponding LEDs. The top LED indi­cates 10/100 Mbps link and activity status
for the port while the bottom LED indicates
1 Gigabit link and activity status for the
port. The appropriate LED displays green
when a valid Ethernet cable connection
exists. Flashes green as data is transmitted
or received on the port.

Refer to diagram on the bottom of the NI
for locations of the two (10/100 or Gigabit)
LEDs.

Module
Status
LEDs

OK1

OK2

2x

12x

14x

24x

10/100 10/100

OS8-GNI-C24

1x

3x

5x

7x

9x

11x

13x

15x

17x

19x

21x

23x

Gigabit Ethernet Ports

The OS8-GNI-C24 module provides 24 10/100/1000
Ethernet ports. These ports are twisted-pair and are
individually configurable as 10BaseT, 100BaseTX, or
1000BaseT. The ports use RJ-45 connectors.

10001000

62 Hardware Basics March 2005

OS8-10GNI-UR1 Front Panel

Module Status LEDs

OK1. Hardware Status. Displays solid
green when powered on and the 10GNI has
passed hardware diagnostic tests. Displays
solid amber when powered on and the
10GNI has failed hardware diagnostic tests.

OK2. Software Status. Blinks green when
the 10GNI is operational and has success­fully loaded software. Displays solid amber
when powered on and the 10GNI has failed
to load software.

Gigabit Ethernet Port LEDs

Tx. Transmit Status. On the active port this
will LED will blink green when it is trans­mitting data. On the inactive port this LED
will always be off.

Rx. Receive Status. On the active port this
will LED will blink green when it is receiv­ing data. On the inactive port this LED will
always be off.

Link. Link Status. This LED will be solid
green if there is a Xenpak module plugged
into the port.

Module
Status
LEDs

OS8-10GNI-UR1

OK1

OK2

Tx

Rx

Link

1

Port
Redundancy

Tx

Rx

Link

2

10 Gigabit Ethernet Ports

The OS8-10GNI-UR1 module provides 2 Xenpak
slots, which act as one redundant port. These slots sup­port the following Xenpak types:

• OM-10GNI-SR—10GBASE-S Multimode fiber,

supports distances up to 300 meters; uses SC
connectors.

• OM-10GNI-LR—10GBASE-L Single mode

fiber, supports distances up to 10 km; uses SC
connectors.

• OM-10GNI-ER—10GBASE-E single mode

long haul fiber, supports distances up to 40 km;
uses SC connectors.

Note

Refer to your OmniSwitch 8800 Hardware Users
Guide for information on proper handling of SC con-

nectors and fiber-optic cable.

March 2005 Hardware Basics 63

User Documentation on CD

The CD that accompanies this Getting Started Guide contains
comprehensive Alcatel user documentation, including the
following manuals:

• OmniSwitch 8800 Getting Started Guide

Describes the hardware and software procedures for
getting an OmniSwitch 8800 up and running. Also
provides information on fundamental aspects of
OmniSwitch hardware components and software archi­tecture.

• OmniSwitch 8800 Hardware Users Guide

Complete technical specifications and procedures for
all OmniSwitch 8800 chassis, power supplies, fans,
Chassis Management Modules (CMMs), Switch Fabric
Modules (SFMs), and Network Interface (NI) modules.

• OmniSwitch CLI Reference Guide

Complete reference to all CLI commands supported on
the OmniSwitch 8800. Includes syntax definitions,
default values, examples, usage guidelines, and CLI­to-MIB variable mappings.

• OmniSwitch 7700/7800/8800 Switch Management

Guide

Includes procedures for readying an individual switch
for integration into a network. Topics include the soft­ware directory architecture, image rollback protec­tions, authenticated switch access, managing switch
files, system configuration, using SNMP, and using
web management software (WebView).

• OmniSwitch 7700/7800/8800 Network Configuration

Guide

Includes network configuration procedures and
descriptive information on all the major software
features and protocols included in the base software
package. Chapters cover Layer 2 information (Ether­net and VLAN configuration), Layer 3 information
(routing protocols, such as RIP and IPX), security
options (authenticated VLANs), Quality of Service
(QoS), link aggregation, and server load balancing.

64 User Documentation on CD March 2005

• OmniSwitch 7700/7800/8800 Advanced Routing

Configuration Guide

Includes network configuration procedures and
descriptive information on all the software features and
protocols included in the advanced routing software
package. Chapters cover multicast routing (DVMRP
and PIM-SM) and OSPF.

General Information

To load the CD and access the user documentation, refer to the
instructions printed on the CD packaging.

If you cannot locate a button with the document image behind
the binoculars (as shown), then the global search feature is not
available in the version of Acrobat Reader you are currently
using.

Printing PDFs. When printing pages from the documen-

tation PDFs, de-select Fit to Page if it is selected in your

print dialog. Otherwise pages may print with slightly

smaller margins.

All documentation is in
Acrobat Reader program for viewing. Acrobat Reader free­ware is available at www.adobe.com.

Global Search. In order to take advantage of the docu­mentation CD’s global search feature, it is recommended
that you select the option for searching PDF files when
downloading Acrobat Reader freeware from the Adobe
Website.

To verify that you are using Acrobat Reader with the global
search option, look for the following button in the toolbar:

March 2005 User Documentation on CD 65

PDF format and requires the Adobe

66 User Documentation on CD March 2005