OID reference

pegasusLeanTrapModule

1.3.6.1.4.1.6368.2.5

Description

Pegasus is an SDSL system manufactured by Schmid Telecom Zurich. The information base is defined in PEGASUS-MIB. This MIB singles out the definitions of notification types from that MIB. This allows us to keep the base MIB clearer, and also to have alternative sets of notifications as separate MIBs. The notification t…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6368.2 (pegasusMibModule)
Node code
5
Node name
pegasusLeanTrapModule
Numeric OID
1.3.6.1.4.1.6368.2.5
URN notation
urn:oid:1.3.6.1.4.1.6368.2.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6368 2 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) schmidtelecom(6368) pegasusMibModule(2) pegasusLeanTrapModule(5)}
OID-IRI notation
  • /1/3/6/1/4/1/6368/2/5
  • /ISO/Identified-Organization/6/1/4/1/6368/2/5
  • /ISO/3/6/1/4/1/6368/2/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/enterprises/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/vendor-objects/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/identified-organization/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/enterprise/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/enterprise/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/enterprises/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/enterprises/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/ldap-enterprise/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/ldap-enterprise/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/vendor-objects/6368/pegasusMibModule/pegasusLeanTrapModule
  • /iso/org/dod/internet/private/vendor-objects/schmidtelecom/pegasusMibModule/pegasusLeanTrapModule
  • Additional combinations skipped.

The displayed source records contain one distinct definition. Compare its source records.

pegasusLeanTrapModule MODULE-IDENTITY
  LAST-UPDATED "200502020000Z"  -- 2 Feb, 2005
  ORGANIZATION "Schmid Telecom, Zurich"
  CONTACT-INFO
    "Schmid Telecom AG
     Binzstrasse 35, CH-8048 Zurich
     Switzerland

     Email: xdslsupport@schmid-telecom.ch"
  DESCRIPTION
    "Pegasus is an SDSL system manufactured by Schmid Telecom Zurich.
    The information base is defined in PEGASUS-MIB. This MIB singles out
    the definitions of notification types from that MIB. This allows us to
    keep the base MIB clearer, and also to have alternative sets of
    notifications as separate MIBs.
    The notification types defined in this module are centered around the
    idea of having a minimal set of notification types, and add the information
    to the varbindings list of the notification. Here are some examples. The
    first two were caused by interrupting the DSL line of an running Iad (DSL
    link and card both unlocked). The third and fourth are generated when the
    DSL line is restored.

     sysUpTime.0             0:0:42:36.21
     snmpTrapOID.0           pegasusAlarm
     sender                  dslInterfaceAvailabilityStatus.5.1.ltu
     senderObjectName        LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5
     senderDescription       dslInterface 5.1.ltu
     probableCause           dslLoswFailure
     probableCauseText       DSL_LOSW_FAILURE
     perceivedSeverity       minor
     perceivedSeverityText   MINOR

     sysUpTime.0             0:0:42:36.22
     snmpTrapOID.0           pegasusAlarm
     sender                  dslLinkActiveLoop.5.1
     senderObjectName        LineCard:DSLLinkId=0,slotId=5
     senderDescription       dslLink 5.1
     probableCause           dslUserService
     probableCauseText       DSL_USER_SERVICE
     perceivedSeverity       minor
     perceivedSeverityText   MINOR

     sysUpTime.0             0:0:42:56.21
     snmpTrapOID.0           pegasusAlarm
     sender                  dslInterfaceAvailabilityStatus.5.1.ltu
     senderObjectName        LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5
     senderDescription       dslInterface 5.1.ltu
     probableCause           dslLoswFailure
     probableCauseText       DSL_LOSW_FAILURE
     perceivedSeverity       cleared
     perceivedSeverityText   CLEARED

     sysUpTime.0             0:0:42:59.21
     snmpTrapOID.0           pegasusAlarm
     sender                  dslLinkActiveLoop.5.1
     senderObjectName        LineCard:DSLLinkId=0,slotId=5
     senderDescription       dslLink 5.1
     probableCause           dslUserService
     probableCauseText       DSL_USER_SERVICE
     perceivedSeverity       cleared
     perceivedSeverityText   CLEARED

    Note

    - If the Dsl link (or the DSL card) is locked, the traps would have been
      suppressed.
    - Two traps are for the DSL interface, with probableCause dslLoswFailure,
      indicating a condition of loss of synchronization word. The first has
      perceivedSeverity minor, the second cleared, to show that the condition
      has ceased and synchronization regained.
    - Likewise, for the DSL link, a pair of probableCause dslUserService is
      sent, with severity minor and then again cleared.
    - The 'affected managed object' is identified by the JMX object name in
      senderObjectName, and also be the variable name (OID) in sender. The
      choice of the variable is arbitrary, usually it is the variable with the
      lowest OID value (the first variable) of tha 'affected managed object'.
    - The JMX senderObjectName contains a domain (LineCard in our examples), and
      a list of attributes, e.g. link, interface and slot numbers. The numbers
      usually start at zero, while the SNMP index values start at one, as is
      usual with SNMP. To get the SNMP index value, add one to the JMX value."

  REVISION "200502020000Z"  -- 2 Feb, 2005
  DESCRIPTION
    "Added new probableCause values."
  REVISION "200412170000Z"  -- 17 Dec, 2004
  DESCRIPTION
    "Updated probableCause values."
  REVISION "200403180000Z"  -- 15 Mar, 2004
  DESCRIPTION
    "Updated probableCause. Added some new values and modified existing 
     values."
  REVISION "200401150000Z"  -- 15 Jan, 2004
  DESCRIPTION
    "Updated probableCause. New value writeError(77)."
  REVISION "200311110000Z"  -- 11 Nov, 2003
  DESCRIPTION
    "Updated probableCause. New last value is m16ProgramTransfer(76)."
  REVISION "200303210000Z"  -- 21 Mar, 2003
  DESCRIPTION
    "Appended five new literals into enumeration ProbableCause:
    - unsupported2ndV5Card(47),
    - currentLimit(48),
    - watsonDTRFailed(49),
    - softwareMismatch(50),
    - hardwareProblem(51)"
  REVISION "200209190000Z"  -- 19 Sep, 2002
  DESCRIPTION
    "Inserted four new literals into enumeration ProbableCause:
    - iadDCContinuity(34),
    - v5InterfaceIDFailure(44),
    - v5InterfaceProvisMismatch(45),
    - v5LinkIdFailure(46)
    Warning: dslConfig and all other old literals defined after it have
    changed their ordinal values!"
  REVISION "200204250000Z"  -- 25 Apr, 2002
  DESCRIPTION
    "Added senderDescription. Renamed 'alarm' to 'pegasusAlarm', to help with
    name conflicts. Made corresponding changes to trap examples above."
  REVISION "200204020000Z"  -- 2 Apr, 2002
  DESCRIPTION
    "Added missing import of DisplayString."
  REVISION "200203140000Z"  -- 14 Mar, 2002
  DESCRIPTION
    "Added some trap example dumps and explanation to the module description."
  REVISION "200202180000Z"  -- 18 Feb, 2002
  DESCRIPTION
    "The two trap types were collapsed into one. The former changedAlarm is now
    represented by an 'alarm' with exactly the same parameters. The former
    newAlarm was used when the perceivedSeverity changed from CLEARED (i.e.
    alarm not present) to other than cleared. This is now also reported through
    the single trap type 'alarm'.
    The senderText variable was removed. Each of sender and senderObjectName
    alone exactly identifies the object affected, and senderText was redundant."
  REVISION "200202140000Z"  -- 14 Feb, 2002
  DESCRIPTION
    "Initial revision."
  ::= { pegasusMibModule 5 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Pegasus is an SDSL system manufactured by Schmid Telecom Zurich. The information base is defined in PEGASUS-MIB. This MIB singles out the definitions of notification types from that MIB. This allows us to keep the base MIB clearer, and also to have alternative sets of notifications as separate MIBs. The notification types defined in this module are centered around the idea of having a minimal set of notification types, and add the information to the varbindings list of the notification. Here are some examples. The first two were caused by interrupting the DSL line of an running Iad (DSL link and card both unlocked). The third and fourth are generated when the DSL line is restored. sysUpTime.0 0:0:42:36.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:36.22 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:56.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity cleared perceivedSeverityText CLEARED sysUpTime.0 0:0:42:59.21 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity cleared perceivedSeverityText CLEARED Note - If the Dsl link (or the DSL card) is locked, the traps would have been suppressed. - Two traps are for the DSL interface, with probableCause dslLoswFailure, indicating a condition of loss of synchronization word. The first has perceivedSeverity minor, the second cleared, to show that the condition has ceased and synchronization regained. - Likewise, for the DSL link, a pair of probableCause dslUserService is sent, with severity minor and then again cleared. - The 'affected managed object' is identified by the JMX object name in senderObjectName, and also be the variable name (OID) in sender. The choice of the variable is arbitrary, usually it is the variable with the lowest OID value (the first variable) of tha 'affected managed object'. - The JMX senderObjectName contains a domain (LineCard in our examples), and a list of attributes, e.g. link, interface and slot numbers. The numbers usually start at zero, while the SNMP index values start at one, as is usual with SNMP. To get the SNMP index value, add one to the JMX value.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

pegasusLeanTrapModule · unspecifiedMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: unspecified.

Names: pegasusLeanTrapModule

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "pegasusLeanTrapModule",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303530323032303030305a22"
    ],
    "ORGANIZATION",
    "\"Schmid Telecom, Zurich\"",
    "CONTACT-INFO",
    "\"Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch\"",
    "DESCRIPTION",
    "\"Pegasus is an SDSL system manufactured by Schmid Telecom Zurich. The information base is defined in PEGASUS-MIB. This MIB singles out the definitions of notification types from that MIB. This allows us to keep the base MIB clearer, and also to have alternative sets of notifications as separate MIBs. The notification types defined in this module are centered around the idea of having a minimal set of notification types, and add the information to the varbindings list of the notification. Here are some examples. The first two were caused by interrupting the DSL line of an running Iad (DSL link and card both unlocked). The third and fourth are generated when the DSL line is restored. sysUpTime.0 0:0:42:36.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:36.22 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:56.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity cleared perceivedSeverityText CLEARED sysUpTime.0 0:0:42:59.21 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity cleared perceivedSeverityText CLEARED Note - If the Dsl link (or the DSL card) is locked, the traps would have been suppressed. - Two traps are for the DSL interface, with probableCause dslLoswFailure, indicating a condition of loss of synchronization word. The first has perceivedSeverity minor, the second cleared, to show that the condition has ceased and synchronization regained. - Likewise, for the DSL link, a pair of probableCause dslUserService is sent, with severity minor and then again cleared. - The 'affected managed object' is identified by the JMX object name in senderObjectName, and also be the variable name (OID) in sender. The choice of the variable is arbitrary, usually it is the variable with the lowest OID value (the first variable) of tha 'affected managed object'. - The JMX senderObjectName contains a domain (LineCard in our examples), and a list of attributes, e.g. link, interface and slot numbers. The numbers usually start at zero, while the SNMP index values start at one, as is usual with SNMP. To get the SNMP index value, add one to the JMX value.\"",
    "REVISION",
    [
      "literal",
      "223230303530323032303030305a22"
    ],
    "DESCRIPTION",
    "\"Added new probableCause values.\"",
    "REVISION",
    [
      "literal",
      "223230303431323137303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated probableCause values.\"",
    "REVISION",
    [
      "literal",
      "223230303430333138303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated probableCause. Added some new values and modified existing values.\"",
    "REVISION",
    [
      "literal",
      "223230303430313135303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated probableCause. New value writeError(77).\"",
    "REVISION",
    [
      "literal",
      "223230303331313131303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated probableCause. New last value is m16ProgramTransfer(76).\"",
    "REVISION",
    [
      "literal",
      "223230303330333231303030305a22"
    ],
    "DESCRIPTION",
    "\"Appended five new literals into enumeration ProbableCause: - unsupported2ndV5Card(47), - currentLimit(48), - watsonDTRFailed(49), - softwareMismatch(50), - hardwareProblem(51)\"",
    "REVISION",
    [
      "literal",
      "223230303230393139303030305a22"
    ],
    "DESCRIPTION",
    "\"Inserted four new literals into enumeration ProbableCause: - iadDCContinuity(34), - v5InterfaceIDFailure(44), - v5InterfaceProvisMismatch(45), - v5LinkIdFailure(46) Warning: dslConfig and all other old literals defined after it have changed their ordinal values!\"",
    "REVISION",
    [
      "literal",
      "223230303230343235303030305a22"
    ],
    "DESCRIPTION",
    "\"Added senderDescription. Renamed 'alarm' to 'pegasusAlarm', to help with name conflicts. Made corresponding changes to trap examples above.\"",
    "REVISION",
    [
      "literal",
      "223230303230343032303030305a22"
    ],
    "DESCRIPTION",
    "\"Added missing import of DisplayString.\"",
    "REVISION",
    [
      "literal",
      "223230303230333134303030305a22"
    ],
    "DESCRIPTION",
    "\"Added some trap example dumps and explanation to the module description.\"",
    "REVISION",
    [
      "literal",
      "223230303230323138303030305a22"
    ],
    "DESCRIPTION",
    "\"The two trap types were collapsed into one. The former changedAlarm is now represented by an 'alarm' with exactly the same parameters. The former newAlarm was used when the perceivedSeverity changed from CLEARED (i.e. alarm not present) to other than cleared. This is now also reported through the single trap type 'alarm'. The senderText variable was removed. Each of sender and senderObjectName alone exactly identifies the object affected, and senderText was redundant.\"",
    "REVISION",
    [
      "literal",
      "223230303230323134303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial revision.\"",
    "::=",
    "{",
    "pegasusMibModule",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200502020000Z"
    ],
    [
      "ORGANIZATION",
      "Schmid Telecom, Zurich"
    ],
    [
      "CONTACT-INFO",
      "Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch"
    ],
    [
      "DESCRIPTION",
      "Pegasus is an SDSL system manufactured by Schmid Telecom Zurich. The information base is defined in PEGASUS-MIB. This MIB singles out the definitions of notification types from that MIB. This allows us to keep the base MIB clearer, and also to have alternative sets of notifications as separate MIBs. The notification types defined in this module are centered around the idea of having a minimal set of notification types, and add the information to the varbindings list of the notification. Here are some examples. The first two were caused by interrupting the DSL line of an running Iad (DSL link and card both unlocked). The third and fourth are generated when the DSL line is restored. sysUpTime.0 0:0:42:36.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:36.22 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:56.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity cleared perceivedSeverityText CLEARED sysUpTime.0 0:0:42:59.21 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity cleared perceivedSeverityText CLEARED Note - If the Dsl link (or the DSL card) is locked, the traps would have been suppressed. - Two traps are for the DSL interface, with probableCause dslLoswFailure, indicating a condition of loss of synchronization word. The first has perceivedSeverity minor, the second cleared, to show that the condition has ceased and synchronization regained. - Likewise, for the DSL link, a pair of probableCause dslUserService is sent, with severity minor and then again cleared. - The 'affected managed object' is identified by the JMX object name in senderObjectName, and also be the variable name (OID) in sender. The choice of the variable is arbitrary, usually it is the variable with the lowest OID value (the first variable) of tha 'affected managed object'. - The JMX senderObjectName contains a domain (LineCard in our examples), and a list of attributes, e.g. link, interface and slot numbers. The numbers usually start at zero, while the SNMP index values start at one, as is usual with SNMP. To get the SNMP index value, add one to the JMX value."
    ],
    [
      "Revisions",
      [
        [
          "200502020000Z",
          [
            "DESCRIPTION",
            "Added new probableCause values."
          ]
        ],
        [
          "200412170000Z",
          [
            "DESCRIPTION",
            "Updated probableCause values."
          ]
        ],
        [
          "200403180000Z",
          [
            "DESCRIPTION",
            "Updated probableCause. Added some new values and modified existing values."
          ]
        ],
        [
          "200401150000Z",
          [
            "DESCRIPTION",
            "Updated probableCause. New value writeError(77)."
          ]
        ],
        [
          "200311110000Z",
          [
            "DESCRIPTION",
            "Updated probableCause. New last value is m16ProgramTransfer(76)."
          ]
        ],
        [
          "200303210000Z",
          [
            "DESCRIPTION",
            "Appended five new literals into enumeration ProbableCause: - unsupported2ndV5Card(47), - currentLimit(48), - watsonDTRFailed(49), - softwareMismatch(50), - hardwareProblem(51)"
          ]
        ],
        [
          "200209190000Z",
          [
            "DESCRIPTION",
            "Inserted four new literals into enumeration ProbableCause: - iadDCContinuity(34), - v5InterfaceIDFailure(44), - v5InterfaceProvisMismatch(45), - v5LinkIdFailure(46) Warning: dslConfig and all other old literals defined after it have changed their ordinal values!"
          ]
        ],
        [
          "200204250000Z",
          [
            "DESCRIPTION",
            "Added senderDescription. Renamed 'alarm' to 'pegasusAlarm', to help with name conflicts. Made corresponding changes to trap examples above."
          ]
        ],
        [
          "200204020000Z",
          [
            "DESCRIPTION",
            "Added missing import of DisplayString."
          ]
        ],
        [
          "200203140000Z",
          [
            "DESCRIPTION",
            "Added some trap example dumps and explanation to the module description."
          ]
        ],
        [
          "200202180000Z",
          [
            "DESCRIPTION",
            "The two trap types were collapsed into one. The former changedAlarm is now represented by an 'alarm' with exactly the same parameters. The former newAlarm was used when the perceivedSeverity changed from CLEARED (i.e. alarm not present) to other than cleared. This is now also reported through the single trap type 'alarm'. The senderText variable was removed. Each of sender and senderObjectName alone exactly identifies the object affected, and senderText was redundant."
          ]
        ],
        [
          "200202140000Z",
          [
            "DESCRIPTION",
            "Initial revision."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6368)

Poltera Gian Lucas

Direct children (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6368.2.5.1 leanTrapObjects77
1.3.6.1.4.1.6368.2.5.2 leanNotifications12

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6368.2.1 dsl571
1.3.6.1.4.1.6368.2.2 v5573
1.3.6.1.4.1.6368.2.3 data220
1.3.6.1.4.1.6368.2.4 pegasusSystem2222
1.3.6.1.4.1.6368.2.7 perf318
1.3.6.1.4.1.6368.2.8 pegasusSdhMibModule663