Alcatel-Lucent 1850 TSS-320 User Provisioning Manual page 121

Menu bar
............................................................................................................................................................................................................................................................
Secondary State - Specifies the secondary state to which the equipment is set. The
•
values are:
– AINS Autonomous in service - The module is in the AINS state and changes to in
– FLT Fault - The module has a Hardware Failure condition.
– MEA Mismatch of Equipment and Attributes - An incompatible module is
– PSI Protection Switching Inhibited, by operator command
– SGEO Supporting Entity Outage - Reported for an XFP, SFP or PIM module if the
– SDEE Supported Entities Existing - Reported for IOC, PIM, SFP and XFP
– Facilities. Reported for all the IOCs modules that don't support directly any
– STBYC Standby-Cold - The module is to back up another module, but is not
– STBYH Standby-Hot - The module is to back-up another entity and is normally
– SWDL Software Download - The module is out of service because it is in the
– UAS Unassigned - No equipment is provisioned in the addressed position.
– UEQ Unequipped - There is no module in the addressed position.
Protection Status - Specifies the status of the unit ("Working", "StandbyHot" or "--
•
").
Click on one of the displayed item in the Access Identifier column as shown in
Figure
............................................................................................................................................................................................................................................................
8DG08136EAAA
Issue 3 July 2009
service when plugged in.
physically present in a provisioned slot.
supporting IO card is in a OOS primary state. SGEO Supporting Entity Outage.
modules that directly supports provisioned.
Facilities but that hosts provisioned Equipment entities that support directly
provisioned Facilities.
synchronized with the backed-up module. A module with a cold standby status
will not be immediately able to take over the role of the backed-up module, and
will require some initialization activity.
synchronized with the backed-up module. When In-Service, a module with a hot
standby status will be immediately able to take over the role of the backed-up
module without the need for initialization activity. Note that STBYH state is
maintained even when the entity is OOS. Mutually exclusive with WRK and
STBYC.
process of acquiring, loading, and/or initializing its software.
3-54.
Protection menu
3 - 6 1