Reference record for OID 1.3.6.1.4.1.2011.5.25.36.2.14



parent
1.3.6.1.4.1.2011.5.25.36.2 (hwRPRTraps)
node code
14
node name
hwRPRMateErr
dot oid
1.3.6.1.4.1.2011.5.25.36.2.14
type
NOTIFICATION-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) huaweiMgmt(5) huaweiDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) huaweiMgmt(5) hwDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) huaweiMgmt(5) huaweiDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) huaweiMgmt(5) hwDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) huaweiMgmt(5) huaweiDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) huaweiMgmt(5) hwDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) huaweiMgmt(5) huaweiDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) huaweiMgmt(5) hwDatacomm(25) hwRPR(36) hwRPRTraps(2) hwRPRMateErr(14)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/huaweiMgmt/huaweiDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/huaweiMgmt/hwDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/iMAP/huaweiMgmt/huaweiDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • /iso/org/dod/internet/private/enterprise/iMAP/huaweiMgmt/hwDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • /iso/org/dod/internet/private/enterprises/huawei/huaweiMgmt/huaweiDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • /iso/org/dod/internet/private/enterprises/huawei/huaweiMgmt/hwDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/iMAP/huaweiMgmt/huaweiDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • /iso/iso-identified-organization/dod/internet/private/enterprises/iMAP/huaweiMgmt/hwDatacomm/hwRPR/hwRPRTraps/hwRPRMateErr
  • Description by mibdepot

    In double RPR operating mode, east and west directions
    of one RPR node lay on two RPR cards, These two cards are
    internally connected by Gigaibit Ethernet, which is called
    MATE interface. The RPR nodes cannot work normaly under
    condition of MATE error.!

    Parsed from file HUAWEI-RPR-MIB.mib.txt
    Company: huawei
    Module: HUAWEI-RPR-MIB

    Information by mibdepot

    hwRPRMateErr NOTIFICATION-TYPE OBJECTS { ifName } STATUS current DESCRIPTION "In double RPR operating mode, east and west directions of one RPR node lay on two RPR cards, These two cards are internally connected by Gigaibit Ethernet, which is called MATE interface. The RPR nodes cannot work normaly under condition of MATE error.!" ::= { hwRPRTraps 14 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.2011)

    Lwu Zhao

    Brothers (17)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.2011.5.25.36.2.1 hwRPRexcessReservedRateDefect 0 0 This defect indicates that the amount of reserved
    bandwidth on a ringlet exceeds the available LINK_RATE.
    When an excess reserved…
    1.3.6.1.4.1.2011.5.25.36.2.2 hwRPRprotMisconfigDefect 0 0 A critical severity defect that indicates the presence
    of mismatched-protection-configuration stations, based
    on the value return…
    1.3.6.1.4.1.2011.5.25.36.2.3 hwRPRtopoChange 0 0 When an topology change is present,
    a notification may be generated.
    1.3.6.1.4.1.2011.5.25.36.2.4 hwRPRtopoInvalidDefect 0 0 A critical severity defect indicating that an
    invalid entry has been found within the scope
    of the topology, the stations on the …
    1.3.6.1.4.1.2011.5.25.36.2.5 hwRPRduplicateMacAddressDefect 0 0 A critical severity defect indicating that a
    duplicate MAG address has been found on the ring.
    When a duplicate MAC address defec…
    1.3.6.1.4.1.2011.5.25.36.2.6 hwRPRtopoInstabilityDefect 0 0 The critical severity Instable topology defect.
    When an Instable topology defect is present,
    a notification may be generated.
    1.3.6.1.4.1.2011.5.25.36.2.7 hwRPRtopoStabilityRestore 0 0 The critical severity Instable topology restore.
    When an stable topology is present,
    a notification may be generated.
    1.3.6.1.4.1.2011.5.25.36.2.8 hwRPRPhyIfEventTrap 0 0 The critical severity physical interface defect.
    When an physical interface defect is present,
    a notification may be generated.
    1.3.6.1.4.1.2011.5.25.36.2.9 hwRPRLogicIfEventTrap 0 0 The critical severity Logic interface defect.
    When an logic interface defect that caused
    by physical interface event is present,…
    1.3.6.1.4.1.2011.5.25.36.2.10 hwRPRNodeConErr 0 0 On RPR ring, to detect the connection, a kind of packet
    is send between neighbor RPR nodes, This kind of packet
    is SC(Single-Chok…
    1.3.6.1.4.1.2011.5.25.36.2.11 hwRPRNodeConErrResume 0 0 On RPR ring, to detect the connection, a kind of packet
    is send between neighbor RPR nodes, This kind of packet
    is SC(Single-Chok…
    1.3.6.1.4.1.2011.5.25.36.2.12 hwRPRNodeMisCabling 0 0 Optical fiber is connected in error. i.e. the east direction
    of one node is connected with east direction of another node,
    or the…
    1.3.6.1.4.1.2011.5.25.36.2.13 hwRPRNodeMisCablingResume 0 0 when phenomena that Optical fiber is connected in error disappears,
    this notification is sent!
    1.3.6.1.4.1.2011.5.25.36.2.15 hwRPRMateErrResume 0 0 In double RPR operating mode, east and west directions
    of one RPR node lay on two RPR cards, These two cards are
    internally conne…
    1.3.6.1.4.1.2011.5.25.36.2.16 hwRPRLOS 0 0 On RPR physical layer, link connection is detected
    through physical signal. When can't receive physical
    signal, then local node f…
    1.3.6.1.4.1.2011.5.25.36.2.17 hwRPRLOSResume 0 0 On RPR physical layer, link connection is detected
    through physical singal. When can't receive physical
    singal, then local node f…
    1.3.6.1.4.1.2011.5.25.36.2.18 hwRPRtopoInvalidRestore 0 0 The critical severity Invalid topology restore.
    When an stable and valid topology is present,
    a notification may be generated.