Reference record for OID 1.3.6.1.4.1.9.9.601.1.2.2.1



parent
1.3.6.1.4.1.9.9.601.1.2.2 (crepInterfaceStatsTable)
node code
1
node name
crepInterfaceStatsEntry
dot oid
1.3.6.1.4.1.9.9.601.1.2.2.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoResilientEthernetProtocolMIB(601) ciscoRepMIBObjects(1) crepInterfaceConfig(2) crepInterfaceStatsTable(2) crepInterfaceStatsEntry(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoResilientEthernetProtocolMIB/ciscoRepMIBObjects/crepInterfaceConfig/crepInterfaceStatsTable/crepInterfaceStatsEntry
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/601/1/2/2/1

    Description by circitor

    The counter entries are not persistent. This is because
    once REP is un-configured on the interface the row would be
    deleted and hence they will restart if REP is configured
    once again on the interface. NMS need to check for
    'crepCounterDiscontinuityTime' to see if the counters have
    restarted.

    Parsed from file CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB.mib
    Module: CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

    Description by cisco_v1

    The counter entries are not persistent. This is because
    once REP is un-configured on the interface the row would be
    deleted and hence they will restart if REP is configured
    once again on the interface. NMS need to check for
    'crepCounterDiscontinuityTime' to see if the counters have
    restarted.

    Description by mibdepot

    The counter entries are not persistent. This is because
    once REP is un-configured on the interface the row would be
    deleted and hence they will restart if REP is configured
    once again on the interface. NMS need to check for
    'crepCounterDiscontinuityTime' to see if the counters have
    restarted.

    Parsed from file CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB.my.txt
    Company: None
    Module: CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

    Description by cisco

    The counter entries are not persistent. This is because
    once REP is un-configured on the interface the row would be
    deleted and hence they will restart if REP is configured
    once again on the interface. NMS need to check for
    'crepCounterDiscontinuityTime' to see if the counters have
    restarted.

    Information by circitor

    crepInterfaceStatsEntry OBJECT-TYPE SYNTAX CrepInterfaceStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The counter entries are not persistent. This is because once REP is un-configured on the interface the row would be deleted and hence they will restart if REP is configured once again on the interface. NMS need to check for 'crepCounterDiscontinuityTime' to see if the counters have restarted." AUGMENTS { crepInterfaceConfigEntry } ::= { crepInterfaceStatsTable 1 }

    Information by cisco_v1

    crepInterfaceStatsEntry OBJECT-TYPE SYNTAX CrepInterfaceStatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The counter entries are not persistent. This is because once REP is un-configured on the interface the row would be deleted and hence they will restart if REP is configured once again on the interface. NMS need to check for 'crepCounterDiscontinuityTime' to see if the counters have restarted." INDEX { crepIfIndex } ::= { crepInterfaceStatsTable 1 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    crepInterfaceStatsEntry OBJECT-TYPE SYNTAX CrepInterfaceStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The counter entries are not persistent. This is because once REP is un-configured on the interface the row would be deleted and hence they will restart if REP is configured once again on the interface. NMS need to check for 'crepCounterDiscontinuityTime' to see if the counters have restarted." AUGMENTS { crepInterfaceConfigEntry } ::= { crepInterfaceStatsTable 1 }

    Information by cisco

    crepInterfaceStatsEntry OBJECT-TYPE SYNTAX CrepInterfaceStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The counter entries are not persistent. This is because once REP is un-configured on the interface the row would be deleted and hence they will restart if REP is configured once again on the interface. NMS need to check for 'crepCounterDiscontinuityTime' to see if the counters have restarted." AUGMENTS { crepInterfaceConfigEntry } ::= { crepInterfaceStatsTable 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Children (17)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.601.1.2.2.1.1 crepCounterDiscontinuityTime 0 0 The value of sysUpTime on the most recent occasion at which
    REP counters suffered a discontinuity on this interface.
    If no such d…
    1.3.6.1.4.1.9.9.601.1.2.2.1.2 crepLslRxPdus 0 0 This object indicates the number of link status layer PDUs
    received on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.3 crepLslTxPdus 0 0 This object indicates the number of link status layer PDUs
    transmitted on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.4 crepHflRxPdus 0 0 This object indicates the number of hardware flood layer PDUs
    received on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.5 crepHflTxPdus 0 0 This object indicates the number of hardware flood layer PDUs
    transmitted on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.6 crepBpaTlvRxPackets 0 0 This object indicates the number of blocked port advertisement
    TLVs received on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.7 crepBpaTlvTxPackets 0 0 This object indicates the number of blocked port advertisement
    TLVs transmitted on the port.
    1.3.6.1.4.1.9.9.601.1.2.2.1.8 crepBpaStcnLslRxPackets 0 0 This object indicates the number of segment topology change
    notifications received as blocked port advertisement through
    link sta…
    1.3.6.1.4.1.9.9.601.1.2.2.1.9 crepBpaStcnLslTxPackets 0 0 This object indicates the number of segment topology change
    notifications transmitted as blocked port advertisement through
    link …
    1.3.6.1.4.1.9.9.601.1.2.2.1.10 crepBpaStcnHflRxPackets 0 0 This object indicates the number of segment topology change
    notifications received as blocked port advertisement
    through hardware…
    1.3.6.1.4.1.9.9.601.1.2.2.1.11 crepBpaStcnHflTxPackets 0 0 This object indicates the number of segment topology change
    notifications transmitted as blocked port advertisement
    through hardw…
    1.3.6.1.4.1.9.9.601.1.2.2.1.12 crepEpaElectionTlvRxPackets 0 0 This object indicates the number of end port advertisement
    election TLVs received that are used for determining the
    role, namely …
    1.3.6.1.4.1.9.9.601.1.2.2.1.13 crepEpaElectionTlvTxPackets 0 0 This object indicates the number of end port advertisement
    election TLVs transmitted that are used for determining the
    role, name…
    1.3.6.1.4.1.9.9.601.1.2.2.1.14 crepEpaCommandTlvRxPackets 0 0 This object indicates the number of end port advertisement
    command TLVs received that are used to authorize a port to
    takeover th…
    1.3.6.1.4.1.9.9.601.1.2.2.1.15 crepEpaCommandTlvTxPackets 0 0 This object indicates the number of end port advertisement
    command TLVs transmitted that are used to authorize a port to
    takeover…
    1.3.6.1.4.1.9.9.601.1.2.2.1.16 crepEpaInfoTlvRxPackets 0 0 This object indicates the number of end port advertisement
    information TLVs received on the port. These messages are sent
    by the…
    1.3.6.1.4.1.9.9.601.1.2.2.1.17 crepEpaInfoTlvTxPackets 0 0 This object indicates the number of end port advertisement
    information TLVs transmitted on the port. These messages are
    sent by …