Lucent Technologies Stinger, Administration Manual

Page: 63 / 374

Stinger® Administration Guide 2-1
2
Working with Stinger Shelves
and Modules
a
For information about how to configure a particular module, see the module guide
for your device at
http://www.lucentdocs.com/ins . For information about managing
the Stinger system, see Chapter 1, “Administering a Stinger System.”
Understanding physical addressing on Stinger units
On modular Stinger units, the True Access™ Operating System (TAOS) software uses
the physical address to provide configuration and administration access to a shelf or
module’s functions. Because TAOS associates module functions with the same slot
numbers on all Stinger units, the functions are grouped into
virtual slots on the
Stinger MRT chassis. In this document, Stinger MRT refers to both the Stinger MRT 23
and Stinger MRT 19 chassis.
The chassis of Stinger FS, Stinger FS+, Stinger LS, Stinger RT, or Compact Remote
units have slots that accept plug-in modules with different functions. The smaller
Stinger MRT units integrate the functions of the control module, line interface
modules (LIMs), and line protection modules (LPMs) into the chassis, and have a
single trunk module slot. Each module has a physical address composed of its shelf
number, slot number, and item number in the format
{ shelf-
N
slot-
N
item-
N
} .
On hosted Stinger MRT systems, the value of shelf is defined by the SHELF ID switch
on that shelf. On hosted Compact Remote systems, the value for shelf is assigned.
Figure 2-1 shows the modules on the front panel of a Stinger FS or Stinger FS+ unit.
The slots are numbered from left to right, with the middle slots reserved for the
control modules. On a Stinger LS or Stinger RT unit, which has fewer slots, the
control modules are on the right.
Understanding physical addressing on Stinger units . . . . . . . . . . . . . . . . . . . . . . 2-1
Viewing system components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Opening a session with a module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Changing a module’s state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Changing the state of a module’s interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Removing a module and its configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Recovering from a failed module installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18