OID reference

hmITTraps

1.3.6.1.4.1.248.100.1.2.2

Description

All the successor object identifiers of Hirschmann.traps are the same as those of Hirschmann.products, which represent the source device type of traps. When Hirschmann Agent send out traps, it should set the 'enterprise' field to an OID which indicates the device type, so that when a NMS receive the trap, it could loo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.248.100.1.2 (hmITTrapObject)
Node code
2
Node name
hmITTraps
Numeric OID
1.3.6.1.4.1.248.100.1.2.2
URN notation
urn:oid:1.3.6.1.4.1.248.100.1.2.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 248 100 1 2 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmVendor(100) hmITSwitch(1) hmITTrapObject(2) hmITTraps(2)}
OID-IRI notation
  • /1/3/6/1/4/1/248/100/1/2/2
  • /ISO/Identified-Organization/6/1/4/1/248/100/1/2/2
  • /ISO/3/6/1/4/1/248/100/1/2/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/identified-organization/dod/internet/private/enterprises/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/identified-organization/dod/internet/private/vendor-objects/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/org/dod/internet/private/enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/org/dod/internet/private/enterprises/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/org/dod/internet/private/ldap-enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/org/dod/internet/private/vendor-objects/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-identified-organization/dod/internet/private/enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-identified-organization/dod/internet/private/enterprises/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-organization/dod/internet/private/enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-organization/dod/internet/private/enterprises/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps
  • /iso/iso-organization/dod/internet/private/vendor-objects/hirschmann/hmVendor/hmITSwitch/hmITTrapObject/hmITTraps

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

hmITTraps	OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"All the successor object identifiers of Hirschmann.traps are the 
		same as those of Hirschmann.products, which represent the source
		device type of traps. When Hirschmann Agent send out traps, it 
		should set the 'enterprise' field to an OID which indicates the 
		device type, so that when a NMS receive the trap, it could 
		lookup such field to identify different device.
       
       		For example: if 'enterprise' = 1.3.6.1.4.1.248.100.1.1.102.393, 
			then NMS could know that it is sent from a MTS8003."
	::= { hmITTrapObject 2 }

Meaning

Descriptions

1 unique

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

All the successor object identifiers of Hirschmann.traps are the same as those of Hirschmann.products, which represent the source device type of traps. When Hirschmann Agent send out traps, it should set the 'enterprise' field to an OID which indicates the device type, so that when a NMS receive the trap, it could lookup such field to identify different device. For example: if 'enterprise' = 1.3.6.1.4.1.248.100.1.1.102.393, then NMS could know that it is sent from a MTS8003.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

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 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

hmITTraps · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: hmITTraps

Technical details
{
  "smi_kind": "OBJECT-IDENTITY",
  "definition": [
    "hmITTraps",
    "OBJECT-IDENTITY",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"All the successor object identifiers of Hirschmann.traps are the same as those of Hirschmann.products, which represent the source device type of traps. When Hirschmann Agent send out traps, it should set the 'enterprise' field to an OID which indicates the device type, so that when a NMS receive the trap, it could lookup such field to identify different device. For example: if 'enterprise' = 1.3.6.1.4.1.248.100.1.1.102.393, then NMS could know that it is sent from a MTS8003.\"",
    "::=",
    "{",
    "hmITTrapObject",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "All the successor object identifiers of Hirschmann.traps are the same as those of Hirschmann.products, which represent the source device type of traps. When Hirschmann Agent send out traps, it should set the 'enterprise' field to an OID which indicates the device type, so that when a NMS receive the trap, it could lookup such field to identify different device. For example: if 'enterprise' = 1.3.6.1.4.1.248.100.1.1.102.393, then NMS could know that it is sent from a MTS8003."
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.248)

Nisi Heinz

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.248.100.1.2.2.8 hmITIpAddrCol00

Siblings (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.248.100.1.2.1 hmITTrap55