Reference record for OID 1.3.6.1.4.1.562.36.2.1.12.5.4.10.1.1



parent
1.3.6.1.4.1.562.36.2.1.12.5.4.10.1 (mscLpDS3PlcpOperationalEntry)
node code
1
node name
mscLpDS3PlcpLofAlarm
dot oid
1.3.6.1.4.1.562.36.2.1.12.5.4.10.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nortel(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nt(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nortel(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) northernTelecom(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nt(562) msCarrier(36) mscPassport(2) mscComponents(1) mscLp(12) mscLpDS3(5) mscLpDS3Plcp(4) mscLpDS3PlcpOperationalTable(10) mscLpDS3PlcpOperationalEntry(1) mscLpDS3PlcpLofAlarm(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/nortel/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • /iso/identified-organization/dod/internet/private/enterprise/northernTelecom/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/northernTelecom/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • /iso/org/dod/internet/private/enterprise/nt/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • /iso/org/dod/internet/private/enterprises/nortel/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • /iso/org/dod/internet/private/enterprises/northernTelecom/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/northernTelecom/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • /iso/iso-identified-organization/dod/internet/private/enterprises/nt/msCarrier/mscPassport/mscComponents/mscLp/mscLpDS3/mscLpDS3Plcp/mscLpDS3PlcpOperationalTable/mscLpDS3PlcpOperationalEntry/mscLpDS3PlcpLofAlarm
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/562/36/2/1/12/5/4/10/1/1

    Description by mibdepot

    This attribute displays whether a PLCP Loss Of Frame (LOF)
    failure alarm state has been entered. An LOF failure is declared
    when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect
    occurs when an OOF (Out of Frame) state persists for more than 1
    ms. If the OOF events are intermittent, the LOF defect counter is
    decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3
    PLCP) of the incrementing rate, with all measurements based on a
    200 ms polling cycle. An OOF event (also known as a PLCP SEF
    event) is declared when an error is detected in both the A1 and A2
    octets, or when two consecutive POHIDs are found in error.
    OOF is removed when two valid sets of framing octets and two
    valid and sequential POHID octets have been found. The LOF
    defect is removed when the defect counter reaches zero, i.e. when
    OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms
    (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is
    absent for 10.0 s +/- 0.5 s
    The DS3 or E3 component goes into an operational state of disabled
    until the LOF failure alarm is cleared. The terminal declaring the
    LOF failure alarm will transmit a PLCP RAI signal to the far-end
    for the duration of the alarm.
    The lofAlarm attribute is always set to off when the DS3 or E3
    component has been locked and left offline.

    Parsed from file nortelPC-logicalProcessorV1.mib.txt
    Company: None
    Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB

    Description by circitor

    This attribute displays whether a PLCP Loss Of Frame (LOF)
    failure alarm state has been entered. An LOF failure is declared
    when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect
    occurs when an OOF (Out of Frame) state persists for more than 1
    ms. If the OOF events are intermittent, the LOF defect counter is
    decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3
    PLCP) of the incrementing rate, with all measurements based on a
    200 ms polling cycle. An OOF event (also known as a PLCP SEF
    event) is declared when an error is detected in both the A1 and A2
    octets, or when two consecutive POHIDs are found in error.
    OOF is removed when two valid sets of framing octets and two
    valid and sequential POHID octets have been found. The LOF
    defect is removed when the defect counter reaches zero, i.e. when
    OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms
    (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is
    absent for 10.0 s +/- 0.5 s
    The DS3 or E3 component goes into an operational state of disabled
    until the LOF failure alarm is cleared. The terminal declaring the
    LOF failure alarm will transmit a PLCP RAI signal to the far-end
    for the duration of the alarm.
    The lofAlarm attribute is always set to off when the DS3 or E3
    component has been locked and left offline.

    Parsed from file Nortel-MsCarrier-MscPassport-LogicalProcessorMIB.mib
    Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB

    Information by oid_info

    Vendor: Northern Telecom, Ltd.
    Module: Nortel-MsCarrier-MscPassport-LogicalProcessorMIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    mscLpDS3PlcpLofAlarm OBJECT-TYPE SYNTAX INTEGER { on(0), off(1) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute displays whether a PLCP Loss Of Frame (LOF) failure alarm state has been entered. An LOF failure is declared when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect occurs when an OOF (Out of Frame) state persists for more than 1 ms. If the OOF events are intermittent, the LOF defect counter is decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3 PLCP) of the incrementing rate, with all measurements based on a 200 ms polling cycle. An OOF event (also known as a PLCP SEF event) is declared when an error is detected in both the A1 and A2 octets, or when two consecutive POHIDs are found in error. OOF is removed when two valid sets of framing octets and two valid and sequential POHID octets have been found. The LOF defect is removed when the defect counter reaches zero, i.e. when OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is absent for 10.0 s +/- 0.5 s The DS3 or E3 component goes into an operational state of disabled until the LOF failure alarm is cleared. The terminal declaring the LOF failure alarm will transmit a PLCP RAI signal to the far-end for the duration of the alarm. The lofAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline." DEFVAL { off } ::= { mscLpDS3PlcpOperationalEntry 1 }

    Information by circitor

    mscLpDS3PlcpLofAlarm OBJECT-TYPE SYNTAX INTEGER { on(0), off(1) } ACCESS read-only STATUS mandatory DESCRIPTION "This attribute displays whether a PLCP Loss Of Frame (LOF) failure alarm state has been entered. An LOF failure is declared when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect occurs when an OOF (Out of Frame) state persists for more than 1 ms. If the OOF events are intermittent, the LOF defect counter is decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3 PLCP) of the incrementing rate, with all measurements based on a 200 ms polling cycle. An OOF event (also known as a PLCP SEF event) is declared when an error is detected in both the A1 and A2 octets, or when two consecutive POHIDs are found in error. OOF is removed when two valid sets of framing octets and two valid and sequential POHID octets have been found. The LOF defect is removed when the defect counter reaches zero, i.e. when OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is absent for 10.0 s +/- 0.5 s The DS3 or E3 component goes into an operational state of disabled until the LOF failure alarm is cleared. The terminal declaring the LOF failure alarm will transmit a PLCP RAI signal to the far-end for the duration of the alarm. The lofAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline." DEFVAL { off } ::= { mscLpDS3PlcpOperationalEntry 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Sharon Chisholm

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.562)

    Mike Bobbitt

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.562.36.2.1.12.5.4.10.1.2 mscLpDS3PlcpRxRaiAlarm 0 0 This attribute displays whether a PLCP Remote Alarm Indication
    (RAI) failure alarm state has been entered. An RAI failure alarm
    o…