OID reference

asamTechSupportActionEvent

1.3.6.1.4.1.637.61.1.9.53.4.1.2

Description

Indicate which action to trigger. The Following scenarios are possible: - Generate an On Demand TS File A set with the below fields specified will generate an on-demand Tech Support file generation for a dedicated board. It will result in the creation of a row in the asamTechSupportSessionTable by which the progress o…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.637.61.1.9.53.4.1 (asamTechSupportActionEntry)
Node code
2
Node name
asamTechSupportActionEvent
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.637.61.1.9.53.4.1.2
URN notation
urn:oid:1.3.6.1.4.1.637.61.1.9.53.4.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 637 61 1 9 53 4 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) alcatel(637) asd(61) asam(1) asamSystemMIB(9) techSupport(53) asamTechSupportActionTable(4) asamTechSupportActionEntry(1) asamTechSupportActionEvent(2)}
OID-IRI notation
  • /1/3/6/1/4/1/637/61/1/9/53/4/1/2
  • /ISO/Identified-Organization/6/1/4/1/637/61/1/9/53/4/1/2
  • /ISO/3/6/1/4/1/637/61/1/9/53/4/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/enterprise/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/enterprises/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/enterprises/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/vendor-objects/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/identified-organization/dod/internet/private/vendor-objects/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/enterprise/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/enterprise/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/enterprises/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/enterprises/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/ldap-enterprise/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/ldap-enterprise/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/vendor-objects/alcatel/61/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • /iso/org/dod/internet/private/vendor-objects/alcatel/asd/asam/asamSystemMIB/techSupport/asamTechSupportActionTable/asamTechSupportActionEntry/asamTechSupportActionEvent
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Default value
generate

Enumerated values

ValueName
1generate
2clear

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In ASAM-SYSTEM-MIB, the row index asamTechSupportActionId is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.637.61.1.9.53.4.1.2.<asamTechSupportActionId>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.637.61.1.9.53.4.1.2

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

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

asamTechSupportActionEvent OBJECT-TYPE
   SYNTAX INTEGER
          {
             generate (1),
             clear    (2)
          }
      ACCESS          read-write
      STATUS          mandatory
      DESCRIPTION
        "Indicate which action to trigger.
         The Following scenarios are possible:
         - Generate an On Demand TS File
           A set with the below fields specified will generate an on-demand
           Tech Support file generation for a dedicated board.
           It will result in the creation of a row in the
           asamTechSupportSessionTable by which the progress of the generation
           can be followed. When the Session goes into done state, then the
           corresponding file can be retrieved from /pub/TS/ONDEMAND
           The Mandatory fields to be set in one PDU are
             asamTechSupportActionEvent : MUST be generate (1)
             asamTechSupportActionType : MUST be boardOnDemand (2)
             asamTechSupportActionObject : Equipment Slot ID
             asamTechSupportActionFile : filename to write
           In case a dedicated SessionId is wanted, it can be set via the following
           optional field:
             asamTechSupportActionSessionId : requested session id
           asamTechSupportActionServerIP is also an optional fields which if
           set should be fixed to value 0
         - Clear an On Demand TS File
           A set with the below fields will results in the removal of the entry
           from the asamTechSupportSessionTable and the corresponding file from disk.
           The Mandatory fields to e set in 1 PDU are
             asamTechSupportActionEvent : MUST be clear(2)
             asamTechSupportActionSessionId : SessionId to remove

          ALCATEL NOTE:
             SUPPORT: YES     INSRVMOD: NA           RANGE: 1..2
             PERSIST: YES     DEFVALUE: 1            UNITS: NA"
     DEFVAL { generate }
     ::=  { asamTechSupportActionEntry 2 }

Meaning

Descriptions

1 unique

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

Indicate which action to trigger. The Following scenarios are possible: - Generate an On Demand TS File A set with the below fields specified will generate an on-demand Tech Support file generation for a dedicated board. It will result in the creation of a row in the asamTechSupportSessionTable by which the progress of the generation can be followed. When the Session goes into done state, then the corresponding file can be retrieved from /pub/TS/ONDEMAND The Mandatory fields to be set in one PDU are asamTechSupportActionEvent : MUST be generate (1) asamTechSupportActionType : MUST be boardOnDemand (2) asamTechSupportActionObject : Equipment Slot ID asamTechSupportActionFile : filename to write In case a dedicated SessionId is wanted, it can be set via the following optional field: asamTechSupportActionSessionId : requested session id asamTechSupportActionServerIP is also an optional fields which if set should be fixed to value 0 - Clear an On Demand TS File A set with the below fields will results in the removal of the entry from the asamTechSupportSessionTable and the corresponding file from disk. The Mandatory fields to e set in 1 PDU are asamTechSupportActionEvent : MUST be clear(2) asamTechSupportActionSessionId : SessionId to remove ALCATEL NOTE: SUPPORT: YES INSRVMOD: NA RANGE: 1..2 PERSIST: YES DEFVALUE: 1 UNITS: NA

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Nokia networking 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), Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

asamTechSupportActionEvent · mandatoryMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Nokia networking MIB copies (LibreNMS/Observium Community)2 sources

Status in source: mandatory.

Names: asamTechSupportActionEvent

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "asamTechSupportActionEvent",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "generate",
    "(",
    "1",
    ")",
    ",",
    "clear",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Indicate which action to trigger. The Following scenarios are possible: - Generate an On Demand TS File A set with the below fields specified will generate an on-demand Tech Support file generation for a dedicated board. It will result in the creation of a row in the asamTechSupportSessionTable by which the progress of the generation can be followed. When the Session goes into done state, then the corresponding file can be retrieved from /pub/TS/ONDEMAND The Mandatory fields to be set in one PDU are asamTechSupportActionEvent : MUST be generate (1) asamTechSupportActionType : MUST be boardOnDemand (2) asamTechSupportActionObject : Equipment Slot ID asamTechSupportActionFile : filename to write In case a dedicated SessionId is wanted, it can be set via the following optional field: asamTechSupportActionSessionId : requested session id asamTechSupportActionServerIP is also an optional fields which if set should be fixed to value 0 - Clear an On Demand TS File A set with the below fields will results in the removal of the entry from the asamTechSupportSessionTable and the corresponding file from disk. The Mandatory fields to e set in 1 PDU are asamTechSupportActionEvent : MUST be clear(2) asamTechSupportActionSessionId : SessionId to remove ALCATEL NOTE: SUPPORT: YES INSRVMOD: NA RANGE: 1..2 PERSIST: YES DEFVALUE: 1 UNITS: NA\"",
    "DEFVAL",
    "{",
    "generate",
    "}",
    "::=",
    "{",
    "asamTechSupportActionEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "generate",
            1
          ],
          [
            "clear",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Indicate which action to trigger. The Following scenarios are possible: - Generate an On Demand TS File A set with the below fields specified will generate an on-demand Tech Support file generation for a dedicated board. It will result in the creation of a row in the asamTechSupportSessionTable by which the progress of the generation can be followed. When the Session goes into done state, then the corresponding file can be retrieved from /pub/TS/ONDEMAND The Mandatory fields to be set in one PDU are asamTechSupportActionEvent : MUST be generate (1) asamTechSupportActionType : MUST be boardOnDemand (2) asamTechSupportActionObject : Equipment Slot ID asamTechSupportActionFile : filename to write In case a dedicated SessionId is wanted, it can be set via the following optional field: asamTechSupportActionSessionId : requested session id asamTechSupportActionServerIP is also an optional fields which if set should be fixed to value 0 - Clear an On Demand TS File A set with the below fields will results in the removal of the entry from the asamTechSupportSessionTable and the corresponding file from disk. The Mandatory fields to e set in 1 PDU are asamTechSupportActionEvent : MUST be clear(2) asamTechSupportActionSessionId : SessionId to remove ALCATEL NOTE: SUPPORT: YES INSRVMOD: NA RANGE: 1..2 PERSIST: YES DEFVALUE: 1 UNITS: NA"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "generate"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.637)

Douglas E. Johnson

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.637)

Jean Rojnic

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.637.61.1.9.53.4.1.1 asamTechSupportActionId00
1.3.6.1.4.1.637.61.1.9.53.4.1.3 asamTechSupportActionSessionId00
1.3.6.1.4.1.637.61.1.9.53.4.1.4 asamTechSupportActionType00
1.3.6.1.4.1.637.61.1.9.53.4.1.5 asamTechSupportActionObject00
1.3.6.1.4.1.637.61.1.9.53.4.1.6 asamTechSupportActionServerIP00
1.3.6.1.4.1.637.61.1.9.53.4.1.7 asamTechSupportActionFile00