CISCO-ATM-DUAL-PHY-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-ATM-DUAL-PHY-MIB and use it to monitor vendor specific OID's.

CISCO-ATM-DUAL-PHY-MIB file content

Object view of CISCO-ATM-DUAL-PHY-MIB:

Scalar Object
cadpStatEntry	.1.3.6.1.4.1.9.9.60.1.1.1.1
An Atm Phy table entry, containing information about a phy on this ATM module.
cadpStatOperActivePhy	.1.3.6.1.4.1.9.9.60.1.1.2
Returns the ifIndex of the phy which is currently the active phy. A value of 0 indicates that no phy is currently active.
cadpStatAdminActivePhy	.1.3.6.1.4.1.9.9.60.1.1.3
Returns the ifIndex of the phy which is the preferred active phy. A value of 0 indicates that no phy is currently active. Setting this object to a value different from its current value causes the ATM module to make the indicated phy active, and the active phy inactive. Setting this object to its current value has no effect. After performing the phy change, the agent will update all phy information (including cadpStatOperActivePhy) and send a ciscoAtmDualPhyChange trap.
Tabular Object
cadpStatLossOfSignal	.1.3.6.1.4.1.9.9.60.1.1.1.1.1
Set to true if the phy is currently experiencing a loss of signal (LOS) from its connected port. Set to false if the phy is not experiencing a loss of signal.
cadpStatFarEndReceiveFailure	.1.3.6.1.4.1.9.9.60.1.1.1.1.2
Set to true if the phy is currently experiencing a far end receive failure (FERF) with its connected port. Set to false if the phy is not experiencing a far end receive failure.
cadpStatActive	.1.3.6.1.4.1.9.9.60.1.1.1.1.5
Set to true when this phy is currently the active phy. Set to false when this phy is not the currently active phy.
cadpStatSectionBIP8Errors	.1.3.6.1.4.1.9.9.60.1.1.1.1.6
The Bit Interleaved Parity 8 is an error checking code applied for quick isolation of faults. Each bit in the B octets is set to 1 or 0 as necessary to obtain even parity over the previous frame. The calculated BIP-8 code for frame N is compared with the BIP-8 code extracted from the B1 byte of frame N+1. Differences indicate that a section level bit error has occurred. Count of Section BIP-8 (Bit Interleaved Parity) errors that have been detected on this phy.
cadpStatLineBIP824Errors	.1.3.6.1.4.1.9.9.60.1.1.1.1.7
The Bit Interleaved Parity 8/24 is an error checking code based on even parity. The calculated BIP code for frame N is compared with the BIP-8/24 code extracted from the B2 byte(s) of frame N+1. Any differences indicate that a line layer bit error has occurred. Count of line bit interleaved partiy (BIP-8/24) errors on this phy.
cadpStatLineFEBErrors	.1.3.6.1.4.1.9.9.60.1.1.1.1.8
The number of bits (binary 000 to 1000) in the previous BIP-8 that didn't match the even parity check are inserted by the transmitter. The receiver checks for this in the M0/M1 byte of the frame. A non-zero value (legal range is binary 0000 - 1000) indicates a line layer error in the remote end. Any other value is treated as no error. Count of Line Far End Bit Errors (FEBE) on this phy.
cadpStatPathBIP8Errors	.1.3.6.1.4.1.9.9.60.1.1.1.1.9
The Bit Interleaved Parity 8 is an error checking code applied for quick isolation of faults. Each bit in the B octets is set to 1 or 0 as necessary to obtain even parity over the previous frame. The calculated BIP-8 code for frame N is compared with the BIP-8 code extracted from the B3 byte of frame N+1. Differences indicate that a Path level bit error has occurred. Count of Path BIP-8 (Bit Interleaved Parity) errors that have been detected on this phy.
cadpStatPathFEBErrors	.1.3.6.1.4.1.9.9.60.1.1.1.1.10
The number of B3 errors in the previous frame inserted by the transmitter. The receiver checks for this in the G1 byte of the frame. A non-zero value (legal range is binary 0000 - 1000) indicates a line layer error in the remote end. Any other value is treated as no error. Count of Path Far End Bit Errors (FEBE) on this phy.
cadpStatCorrectableHCSErrors	.1.3.6.1.4.1.9.9.60.1.1.1.1.11
The Header Checksum (HCS) is a CRC-8 calculation over the first 4 octets of the ATM cell header. The received HCS is verified using the polynomial x^8 + x^2 + x + 1. The coset polynomial x^6 + x^4 + x^2 + 1, is added (modulo 2) to the received HCS octet before comparison with the calculated result. Cells with single bit error in the HCS byte are corrected. Cells with more than one bit error in the HCS byte are uncorrectable. Count of incoming cells on this phy with single bit error in the Header Checksum (HCS) byte
cadpStatUncorrectableHCSErrors	.1.3.6.1.4.1.9.9.60.1.1.1.1.12
The Header Checksum (HCS) is a CRC-8 calculation over the first 4 octets of the ATM cell header. The received HCS is verified using the polynomial x^8 + x^2 + x + 1. The coset polynomial x^6 + x^4 + x^2 + 1, is added (modulo 2) to the received HCS octet before comparison with the calculated result. Cells with single bit error in the HCS byte are corrected. Cells with more than one bit error in the HCS byte are uncorrectable. Count of uncorrectable Header Checksum (HCS) errors on this phy.
Table
cadpStatTable	.1.3.6.1.4.1.9.9.60.1.1.1
A table of status information about ATM phy.
Trap
ciscoAtmDualPhyChange	.1.3.6.1.4.1.9.9.60.2.0.1
A ciscoAtmDualPhyChange trap is sent when the active phy changes either because of a failure or because of user intervention (setting cadpStatAdminActivePhy, for example).
Object Identifier
ciscoAtmDualPhyMIB	.1.3.6.1.4.1.9.9.60
Initial version of this MIB module. Phy definition Throughout this document phy is used as an abbreviation for Physical Interface. In particular it refers to a physical ATM jack on a Catalyst 5000 ATM card. This card can be fitted with either one or two physical jacks, only one of which may be active at any given moment. The second phy serves as a redundant connector to the ATM backbone. Note, however, that for logistical reasons, each phy has a separate ifIndex. Support of the phy by ifTable The dual phy entity on the c5K ATM line card is managed using the ifTable. Specific interpretations of ifTable for the dual phy entity are as follows. Object Use for dual phy entity ====== ======================= ifIndex Each phy entity is represented by an ifEntry. ifDescr Description of the phy entity. ifType The value for the phy entity is other(1). ifSpeed See [1]. ifPhysAddress An octet string of zero length, per [1]. ifAdminStatus See [1]. ifOperStatus See [1]. In addition, note that a phy can be in the up state but still not be the active phy. However, the active phy will always be up. ifLastChange See [1]. ifName See [1]. ifLinkUpDownTrapEnable disabled(2). ifHighSpeed See [1]. ifConnectorPresent true(1). References [1] McCloghrie, K. and F. Kastenholz, Evolution of the Interfaces Group of MIB-II, RFC 1573, Hughes LAN Systems, FTP Software, January 1994.
ciscoAtmDualPhyMIBObjects	.1.3.6.1.4.1.9.9.60.1
cadpStatistics	.1.3.6.1.4.1.9.9.60.1.1
ciscoAtmDualPhyMIBTrapPrefix	.1.3.6.1.4.1.9.9.60.2
ciscoAtmDualPhyMIBTraps	.1.3.6.1.4.1.9.9.60.2.0
ciscoAtmDualPhyMIBConformance	.1.3.6.1.4.1.9.9.60.3
ciscoAtmDualPhyMIBCompliances	.1.3.6.1.4.1.9.9.60.3.1
ciscoAtmDualPhyMIBGroups	.1.3.6.1.4.1.9.9.60.3.2
Group
ciscoAtmDualPhyMIBGroup	.1.3.6.1.4.1.9.9.60.3.2.1
A collection of objects providing ATM dual phy monitoring.