PDN-ENTITY-REDUNDANCY-MIB

TEXTUAL-CONVENTION

This textual convention lists the possibles alarm status. The status are: noAlarm --------------------------- This is the normal status when there is no alarm condition. linkDefect ---------------------------- This alarm is detected when there is an abnormal condition in the link (e.g., LOS, LOF, etc.) of this redundant unit. hwFailure ---------------------------- This alarm is detected when there is a hardware failure on this redundant unit. hwMissing ---------------------------- This alarm is detected when there is an expected piece of hw that is missing on this redundant unit. hwIncompatible ---------------------------- This alarm is detected when the modules in a redundancy configuration present hardware incompatibilities. fwIncompatible ---------------------------- This alarm is detected when the modules in a redundancy configuration present firmware incompatibilities. cfgIncompatible ----------------------------- This alarm is detected when the modules in a redundancy configuration present configuration incompatibilities.

TEXTUAL-CONVENTION

This list of commands allows an user to perform actions on the redundancy entities. The commands are: noCmd ----- This value should be returned by a read request when no previous command has been issue. This value may not be used in a write operation. A wrongValue error shall be returned in this case. switch ------ This is the *Normal* switch. shall be directed to an entity in the Active, Active/Alarm, Standby or Standby/Alarm state. Will cause an entity and its redundant mate to switch roles unless the Standby entity is in a failed state or redundancy is disabled. A switch shall result in the Active or Active/Alarm entity going into a Standby or Standby/Alarm state and the Standby or Standby/Alarm entity going into the Active or Active/Alarm state. forceswitch ----------- This is the *Forced* switch. shall be directed to an entity in the Active, Active/Alarm, Standby or Standby/Alarm state. Will cause an entity and its redundant mate to switch roles regardless of the state of the entities or if redundancy is enabled. A switch shall result in the Active or Active/Alarm entity going into a Standby or Standby/Alarm state and the Standby or Standby/Alarm entity going into the Active or Active/Alarm state.

TEXTUAL-CONVENTION

This textual convention lists the possibles alarm status that are general to the redundancy feature; which are not associated to a particular redundant module. The status are: noAlarm --------------------------- This is the Normal status with no General alarm condition. noActiveModule --------------------------- This alarm is detected when no module is in the Active State. standbyAlarmOrReset ---------------------------- This alarm is detected when on of the modules configured for redundancy is either in the Standby-Alarm or Reset Test state.

TEXTUAL-CONVENTION

This textual Convention describes the valid states relevant to the redundancy feature that an entity module can be. The possibles states are: activeState ----------- the module is currently performing its main functions in the system, including communicating with other modules, monitoring the operation of itself and other standby modules. activeAlarmState ---------------- the same as an activeState except an Alarm condition has been detected on the module. standbyState ------------ the module is primarily in a dormant state until an event is triggered that requires its activation. While in this state, the module only performs background tests to verify that its hardware is operating properly and monitor the active module for proper operation. standbyAlarmState ---------------- the same as an standbyState except a Alarm condition has been detected on the module.

OBJECT-IDENTITY

OBJECT-TYPE

This object is used to enable or disable the redundancy feature on this device.

OBJECT-TYPE

This object is used to configure the Y-cable presence used for tx and rx of data between the redundant units. When the selection is enabled (1), it indicates that the tx and rx signals of each redundant unit are sharing a single common pair to tx and rx data to the network. When the selection is disable (2), it indicates that the tx and rx signals of each redundant unit has a separate (independant) pair to tx and rx data to the network.

OBJECT-TYPE

This object provides status of any General Alarm detected by the redundancy feature.

OBJECT-TYPE

This table contains one row per entity module being used for redundancy.

OBJECT-TYPE

Commands that can be performed on a particular entity module used for redundancy.

OBJECT-TYPE

This object allows users to command an entity module, configured for redundancy to perform an action such as switch (2). Reading this object should return the last command issued on this interface or noCmd (1) if no command has been issued since last reset.

OBJECT-TYPE

This table contains configuration and status information related to events in entity modules used for redundancy.

OBJECT-TYPE

Configuration and Status information for a particular entity module used for redundancy.

OBJECT-TYPE

This object is used to display the current state on an entity that is used for redundancy.

OBJECT-TYPE

This object provides status of any Alarm detected in a redundant entity.

OBJECT-TYPE

This object provides the ability to enable and disable the following notifications: o pdnRedunEventHwIncompatible o pdnRedunEventFwIncompatible o pdnRedunEventCfgIncompatible o pdnRedunEventLinkDefect o pdnRedunEventHwFailure o pdnRedunEventHwMissingHwFailure

OBJECT-TYPE

This object provides the ability to enable and disable the following general notifications: o pdnRedunEventNoActiveModule o pdnRedunEventStandbyAlarmOrReset

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY