ADTRAN-AOS-Y1731-MIB

File: ADTRAN-AOS-Y1731-MIB.mib (6346 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
ADTRAN-MIB ADTRAN-AOS IEEE8021-CFM-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE Unsigned32
MODULE-COMPLIANCE OBJECT-GROUP TEXTUAL-CONVENTION
adIdentity adGenAOS adGenAOSMef
adGenAOSConformance dot1agCfmMdIndex dot1agCfmMaIndex

Defined Types

AdGenAosY1731Alarms  
A MEP can detect and report a number of defects, and multiple defects can be present at the same time. These defects are: bDefY1731CcmRxRDIAlarm(0) A remote MEP is reported the RDI bit in its last CCM. bDefY1731CcmLossOfContinuityAlarm (1) The MEP is not receiving valid CCMs from at least one of the remote MEPs. bDefY1731CcmUnexpectedMepAlarm (2) The MEP has received at least one invalid CCM whose CCM Interval has not yet timed out. bDefY1731CcmUnexpectedPeriodAlarm (3) The MEP has received at least one CCM from either another MAID or a lower MD Level whose CCM Interval has not yet timed out. bDefY1731CcmMismergeAlarm(4) Either some remote MEP is reporting its Interface Status TLV as not isUp, or all remote MEPs are reporting a Port Status TLV that contains some value other than psUp. bDefY1731CcmUnexpectedMegLevelAlarm (5) If a CCM frame with the same MEG level but a MEG ID different than the receiving MEP's own MEG ID is received.
TEXTUAL-CONVENTION    
  BITS bDefY1731CcmRxRDIAlarm(0), bDefY1731CcmLossOfContinuityAlarm(1), bDefY1731CcmUnexpectedMepAlarm(2), bDefY1731CcmUnexpectedPeriodAlarm(3), bDefY1731CcmMismergeAlarm(4), bDefY1731CcmUnexpectedMegLevelAlarm(5)  

AdGenAosY1731LocalMepEntry  
SEQUENCE    
  adGenAosY1731LocalMepId Unsigned32
  adGenAosY1731Alarms AdGenAosY1731Alarms

Defined Values

adGenAosY1731Mib 1.3.6.1.4.1.664.6.10000.53.9.9
The MIB module defines Y.1731 alarms implementation for AdtranOS and its products.
MODULE-IDENTITY    

adGenAosY1731 1.3.6.1.4.1.664.5.53.9.9
OBJECT IDENTIFIER    

adGenAosY1731Conformance 1.3.6.1.4.1.664.5.53.99.34
OBJECT IDENTIFIER    

adGenAosY1731Groups 1.3.6.1.4.1.664.5.53.99.34.1
OBJECT IDENTIFIER    

adGenAosY1731Compliances 1.3.6.1.4.1.664.5.53.99.34.2
OBJECT IDENTIFIER    

adGenAosY1731LocalMepTable 1.3.6.1.4.1.664.5.53.9.9.1
The Local Maintenance End Point Group (MEP) table.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    AdGenAosY1731LocalMepEntry

adGenAosY1731LocalMepEntry 1.3.6.1.4.1.664.5.53.9.9.1.1
The Y1731 Local MEP table entry The indexes used in this table are similar to indexes in dot1agCfmMepTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  AdGenAosY1731LocalMepEntry  

adGenAosY1731LocalMepId 1.3.6.1.4.1.664.5.53.9.9.1.1.1
Local MEP Identifier also known as LMEP ID.
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32 1..8191  

adGenAosY1731Alarms 1.3.6.1.4.1.664.5.53.9.9.1.1.2
A vector of Boolean error conditions, any of which may be true: DefY1731CcmRxRDIAlarm (0), DefY1731CcmLossOfContinuityAlarm (1), DefY1731CcmUnexpectedMepAlarm (2), DefY1731CcmUnexpectedPeriodAlarm (3), DefY1731CcmMismergeAlarm (4), DefY1731CcmUnexpectedMegLevelAlarm (5)
Status: current Access: read-only
OBJECT-TYPE    
  AdGenAosY1731Alarms  

adGenAosY1731FullCompliance 1.3.6.1.4.1.664.5.53.99.34.2.1
The compliance statement for SNMP entities which implement version 1 of the adGenAosY1731 MIB. When the implementation of this MIB supports adGenAosY1731Group, then such an implementation can claim full compliance.
Status: current Access: read-only
MODULE-COMPLIANCE    

adGenAosY1731Group 1.3.6.1.4.1.664.5.53.99.34.1.1
Objects for adGenAosY1731 Group
Status: current Access: read-only
OBJECT-GROUP