OID reference

hm2DynFwIfmDirection

1.3.6.1.4.1.248.11.79.1.2.2.2.1.2

Description

Meanings: - ingress(1): Apply this rule to packets arriving on this interface - egress(2): Apply this rule to packets leaving from this interface - both(3): Apply this rule to packets coming in and going out on this interface. If an ingress and an egress interface are given, this is taken to mean that the rule shall a…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.248.11.79.1.2.2.2.1 (hm2DynFwRuleIfMappingEntry)
Node code
2
Node name
hm2DynFwIfmDirection
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.248.11.79.1.2.2.2.1.2
URN notation
urn:oid:1.3.6.1.4.1.248.11.79.1.2.2.2.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 248 11 79 1 2 2 2 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2DynFw(2) hm2DynFwRuleTables(2) hm2DynFwRuleIfMappingTable(2) hm2DynFwRuleIfMappingEntry(1) hm2DynFwIfmDirection(2)}
OID-IRI notation
  • /1/3/6/1/4/1/248/11/79/1/2/2/2/1/2
  • /ISO/Identified-Organization/6/1/4/1/248/11/79/1/2/2/2/1/2
  • /ISO/3/6/1/4/1/248/11/79/1/2/2/2/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/identified-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/identified-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/org/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/org/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/org/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/org/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-identified-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-identified-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection
  • /iso/iso-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2DynFw/hm2DynFwRuleTables/hm2DynFwRuleIfMappingTable/hm2DynFwRuleIfMappingEntry/hm2DynFwIfmDirection

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
not-accessible
Status in MIB
current

Enumerated values

ValueName
1ingress
2egress
3both

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. The index encoding is not inferred here.

Published row index: hm2DynFwIfmInterface, hm2DynFwIfmDirection, hm2DynFwIfmRuleIndex.

A query example is omitted because the source variants do not establish compatible read access.

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

hm2DynFwIfmDirection · current

hm2DynFwIfmDirection OBJECT-TYPE
	SYNTAX INTEGER {
			ingress(1),
			egress(2),
			both(3)
	}
	MAX-ACCESS not-accessible
	STATUS current
	DESCRIPTION
        "Meanings:
            - ingress(1): Apply this rule to packets arriving on this interface
            - egress(2): Apply this rule to packets leaving from this interface
            - both(3): Apply this rule to packets coming in and going out on this
              interface.

        If an ingress and an egress interface are given, this is taken to mean
        that the rule shall apply to packets arriving on the ingress interface
        AND to be leaving on the egress interface. A rule without ingress
        interface matches on all packets going out to the egress interface
        given, and vice versa."
		::={ hm2DynFwRuleIfMappingEntry 2 }

hm2DynFwIfmDirection · current

hm2DynFwIfmDirection OBJECT-TYPE
	SYNTAX INTEGER {
			ingress(1),
			egress(2),
			both(3)
	}
	MAX-ACCESS not-accessible
	STATUS current
	DESCRIPTION
        "Meanings:
            - ingress(1): Apply this rule to packets arriving on this interface
            - egress(2): Apply this rule to packets leaving from this interface
            - both(3): Apply this rule to packets coming in and going out on this
              interface.

        If an ingress and an egress interface are given, this is taken to mean
        that the rule shall apply to packets arriving on the ingress interface
        AND to be leaving on the egress interface. A rule without ingress
        interface matches on all packets going out to the egress interface
        given, and vice versa."
		::={ hm2DynFwRuleIfMappingEntry 2 }

Meaning

Descriptions

1 unique

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

Meanings: - ingress(1): Apply this rule to packets arriving on this interface - egress(2): Apply this rule to packets leaving from this interface - both(3): Apply this rule to packets coming in and going out on this interface. If an ingress and an egress interface are given, this is taken to mean that the rule shall apply to packets arriving on the ingress interface AND to be leaving on the egress interface. A rule without ingress interface matches on all packets going out to the egress interface given, and vice versa.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBsHirschmann 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 1Belden, GarrettCom and Hirschmann IT official standalone MIBs, Hirschmann MIB copies (LibreNMS/Observium Community)1 record · 5 sources

Description 1

hm2DynFwIfmDirection · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs, Hirschmann MIB copies (LibreNMS/Observium Community)5 sources

Status in source: current.

Names: hm2DynFwIfmDirection

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hm2DynFwIfmDirection",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "ingress",
    "(",
    "1",
    ")",
    ",",
    "egress",
    "(",
    "2",
    ")",
    ",",
    "both",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Meanings: - ingress(1): Apply this rule to packets arriving on this interface - egress(2): Apply this rule to packets leaving from this interface - both(3): Apply this rule to packets coming in and going out on this interface. If an ingress and an egress interface are given, this is taken to mean that the rule shall apply to packets arriving on the ingress interface AND to be leaving on the egress interface. A rule without ingress interface matches on all packets going out to the egress interface given, and vice versa.\"",
    "::=",
    "{",
    "hm2DynFwRuleIfMappingEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "ingress",
            1
          ],
          [
            "egress",
            2
          ],
          [
            "both",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Meanings: - ingress(1): Apply this rule to packets arriving on this interface - egress(2): Apply this rule to packets leaving from this interface - both(3): Apply this rule to packets coming in and going out on this interface. If an ingress and an egress interface are given, this is taken to mean that the rule shall apply to packets arriving on the ingress interface AND to be leaving on the egress interface. A rule without ingress interface matches on all packets going out to the egress interface given, and vice versa."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.248)

Nisi Heinz

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.248.11.79.1.2.2.2.1.1 hm2DynFwIfmRuleIndex00
1.3.6.1.4.1.248.11.79.1.2.2.2.1.3 hm2DynFwIfmPriority00
1.3.6.1.4.1.248.11.79.1.2.2.2.1.4 hm2DynFwIfmInterface00
1.3.6.1.4.1.248.11.79.1.2.2.2.1.5 hm2DynFwIfmRowStatus00