A count of Protection Switch Byte Failure conditions.
This condition occurs when either an inconsistent APS
byte or an invalid code is detected. An inconsistent
APS byte occurs when no three consecutive K1 bytes of
the last 12 successive frames are identical, starting
with the last frame containing a previously consistent
byte. An invalid code occurs when the incoming K1 byte
contains an unused code or a code irrelevant for the
specific switching operation (e.g., Reverse Request
while no switching request is outstanding) in three
consecutive frames. An invalid code also occurs when
the incoming K1 byte contains an invalid channel number
in three consecutive frames.
Parsed from file CISCO-APS-MIB.mib
Module: CISCO-APS-MIB
A count of Protection Switch Byte Failure conditions.
This condition occurs when either an inconsistent APS
byte or an invalid code is detected. An inconsistent
APS byte occurs when no three consecutive K1 bytes of
the last 12 successive frames are identical, starting
with the last frame containing a previously consistent
byte. An invalid code occurs when the incoming K1 byte
contains an unused code or a code irrelevant for the
specific switching operation (e.g., Reverse Request
while no switching request is outstanding) in three
consecutive frames. An invalid code also occurs when
the incoming K1 byte contains an invalid channel number
in three consecutive frames.
A count of Protection Switch Byte Failure conditions.
This condition occurs when either an inconsistent APS
byte or an invalid code is detected. An inconsistent
APS byte occurs when no three consecutive K1 bytes of
the last 12 successive frames are identical, starting
with the last frame containing a previously consistent
byte. An invalid code occurs when the incoming K1 byte
contains an unused code or a code irrelevant for the
specific switching operation (e.g., Reverse Request
while no switching request is outstanding) in three
consecutive frames. An invalid code also occurs when
the incoming K1 byte contains an invalid channel number
in three consecutive frames.
Parsed from file CISCO-APS-MIB.my.txt
Company: None
Module: CISCO-APS-MIB
A count of Protection Switch Byte Failure conditions.
This condition occurs when either an inconsistent APS
byte or an invalid code is detected. An inconsistent
APS byte occurs when no three consecutive K1 bytes of
the last 12 successive frames are identical, starting
with the last frame containing a previously consistent
byte. An invalid code occurs when the incoming K1 byte
contains an unused code or a code irrelevant for the
specific switching operation (e.g., Reverse Request
while no switching request is outstanding) in three
consecutive frames. An invalid code also occurs when
the incoming K1 byte contains an invalid channel number
in three consecutive frames.
cApsStatusPSBFs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Protection Switch Byte Failure conditions. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames." ::= { cApsStatusEntry 6 }
cApsStatusPSBFs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "A count of Protection Switch Byte Failure conditions. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames." ::= { cApsStatusEntry 6 }
Vendor: Cisco
Module: CISCO-APS-MIB
[Automatically extracted from oidview.com]
cApsStatusPSBFs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Protection Switch Byte Failure conditions. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames." ::= { cApsStatusEntry 6 }
cApsStatusPSBFs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of Protection Switch Byte Failure conditions. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames." ::= { cApsStatusEntry 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.71.1.2.1.1 | cApsStatusK1K2Rcv | 0 | 0 | The current value of the K1 and K2 bytes received on the protection channel. |
| 1.3.6.1.4.1.9.10.71.1.2.1.2 | cApsStatusK1K2Trans | 0 | 0 | The current value of the K1 and K2 bytes transmitted on the protection channel. |
| 1.3.6.1.4.1.9.10.71.1.2.1.3 | cApsStatusCurrent | 0 | 0 | The current status of the APS group. modeMismatch Modes other than 1+1 unidirectional monitor protection line K2 bit 5, which in… |
| 1.3.6.1.4.1.9.10.71.1.2.1.4 | cApsStatusModeMismatches | 0 | 0 | A count of Mode Mismatch conditions. |
| 1.3.6.1.4.1.9.10.71.1.2.1.5 | cApsStatusChannelMismatches | 0 | 0 | A count of Channel Mismatch conditions. |
| 1.3.6.1.4.1.9.10.71.1.2.1.7 | cApsStatusFEPLFs | 0 | 0 | A count of Far-End Protection-Line Failure conditions. This condition is declared based on receiving SF on the protection line in… |
| 1.3.6.1.4.1.9.10.71.1.2.1.8 | cApsStatusSwitchedChannel | 0 | 0 | This field is set to the number of the channel that is currently switched to protection. The value 0 indicates no channel is swit… |