OID reference

hm2L3Action

1.3.6.1.4.1.248.11.79.1.3.2.1.1.8

Description

The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matc…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.248.11.79.1.3.2.1.1 (hm2L3RuleEntry)
Node code
8
Node name
hm2L3Action
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.248.11.79.1.3.2.1.1.8
URN notation
urn:oid:1.3.6.1.4.1.248.11.79.1.3.2.1.1.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hm2ConfigurationMibs(11) hm2FwMib(79) hm2FwObjects(1) hm2L3Fw(3) hm2L3RuleTables(2) hm2L3RuleTable(1) hm2L3RuleEntry(1) hm2L3Action(8)}
OID-IRI notation
  • /1/3/6/1/4/1/248/11/79/1/3/2/1/1/8
  • /ISO/Identified-Organization/6/1/4/1/248/11/79/1/3/2/1/1/8
  • /ISO/3/6/1/4/1/248/11/79/1/3/2/1/1/8
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/identified-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/identified-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/org/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/org/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/org/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/org/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-identified-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-identified-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-organization/dod/internet/private/enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-organization/dod/internet/private/enterprises/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action
  • /iso/iso-organization/dod/internet/private/vendor-objects/hirschmann/hm2ConfigurationMibs/hm2FwMib/hm2FwObjects/hm2L3Fw/hm2L3RuleTables/hm2L3RuleTable/hm2L3RuleEntry/hm2L3Action

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Belden, GarrettCom and Hirschmann IT official standalone MIBs

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Variant 2 — Hirschmann MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs

Value type
INTEGER
Maximum access defined by MIB
read-create
Status in MIB
current

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1accept1, 2
2drop1, 2
3reject1, 2
4enforce-modbus1, 2
5enforce-opc1, 2
6enforce-iec1041, 2
7enforce-ethernetip1, 2
8enforce-dnp31, 2
9enforce-amp1
10enforce-goose1
11enforce-s71

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 HM2-FW-MIB, the row index hm2L3RuleIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.248.11.79.1.3.2.1.1.8.<hm2L3RuleIndex>. 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.248.11.79.1.3.2.1.1.8

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.

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

Show 3 published definitions

hm2L3Action · current

hm2L3Action OBJECT-TYPE
 	 SYNTAX INTEGER {
			accept(1),
			drop(2),
			reject(3),
			enforce-modbus(4),
			enforce-opc(5),
			enforce-iec104(6),
			enforce-ethernetip(7),
			enforce-dnp3(8),
			enforce-amp(9),
			enforce-goose(10),
			enforce-s7(11)
 	 }
 	 MAX-ACCESS read-create
 	 STATUS current
 	 DESCRIPTION
 	 	 "The action of the corresponding rule:
 	 	 o accept(1): Packets matching this rule are accepted and will 
 	 	   be forwarded
 	 	 o drop(2): Packets matching this rule will be silently 
 	 	   discarded
 	 	 o reject(3): Packets matching this rule will be dropped and
 	 	   the originator gets informed by an ICMP message
 	 	 o enforce-modbus(4): Packets matching this rule are enforced by
	 	   modbus enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp or udp
	 	 o enforce-opc(5): Packets matching this rule are enforced by
	 	   opc enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-iec104(6): Packets matching this rule are enforced by
	 	   IEC104 enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-ethernetip(7): Packets matching this rule are enforced by
	 	   EtherNet/IP enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-dnp3(8): Packets matching this rule are enforced by
	 	   dnp3 enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp.
		 o enforce-amp(9): Packets matching this rule will be forwarded or
		   discarded based on AMP enforcer rules.
		   The selected protocol must be TCP.
		 o enforce-goose(10): Packets matching this rule will be forwarded or
		   discarded based on GOOSE enforcer rules.
		 o enforce-s7(11): Packets matching this rule will be forwarded or
		   discarded based on S7 enforcer rules.
		   The selected protocol should be tcp."
 	 ::= { hm2L3RuleEntry 8 }

hm2L3Action · current

hm2L3Action OBJECT-TYPE
 	 SYNTAX INTEGER {
			accept(1),
			drop(2),
			reject(3),
			enforce-modbus(4),
			enforce-opc(5),
			enforce-iec104(6),
			enforce-ethernetip(7),
			enforce-dnp3(8)
 	 }
 	 MAX-ACCESS read-create
 	 STATUS current
 	 DESCRIPTION
 	 	 "The action of the corresponding rule:
 	 	 o accept(1): Packets matching this rule are accepted and will 
 	 	   be forwarded
 	 	 o drop(2): Packets matching this rule will be silently 
 	 	   discarded
 	 	 o reject(3): Packets matching this rule will be dropped and
 	 	   the originator gets informed by an ICMP message
 	 	 o enforce-modbus(4): Packets matching this rule are enforced by
	 	   modbus enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp or udp
	 	 o enforce-opc(5): Packets matching this rule are enforced by
	 	   opc enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-iec104(6): Packets matching this rule are enforced by
	 	   IEC104 enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-ethernetip(7): Packets matching this rule are enforced by
	 	   EtherNet/IP enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-dnp3(8): Packets matching this rule are enforced by
	 	   dnp3 enforcer and will be forwarded or discarded.
		   The selected protocol should be tcp"
 	 ::= { hm2L3RuleEntry 8 }

hm2L3Action · current

hm2L3Action OBJECT-TYPE
 	 SYNTAX INTEGER {
			accept(1),
			drop(2),
			reject(3),
			enforce-modbus(4),
			enforce-opc(5),
			enforce-iec104(6),
			enforce-ethernetip(7),
			enforce-dnp3(8)
 	 }
 	 MAX-ACCESS read-create
 	 STATUS current
 	 DESCRIPTION
 	 	 "The action of the corresponding rule:
 	 	 o accept(1): Packets matching this rule are accepted and will 
 	 	   be forwarded
 	 	 o drop(2): Packets matching this rule will be silently 
 	 	   discarded
 	 	 o reject(3): Packets matching this rule will be dropped and
 	 	   the originator gets informed by an ICMP message
 	 	 o enforce-modbus(4): Packets matching this rule are enforced by
	 	   modbus enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp or udp
	 	 o enforce-opc(5): Packets matching this rule are enforced by
	 	   opc enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-iec104(6): Packets matching this rule are enforced by
	 	   IEC104 enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-ethernetip(7): Packets matching this rule are enforced by
	 	   EtherNet/IP enforcer and will be forwarded or discarded.
	 	   The selected protocol should be tcp
	 	 o enforce-dnp3(8): Packets matching this rule are enforced by
	 	   dnp3 enforcer and will be forwarded or discarded.
		   The selected protocol should be tcp"
 	 ::= { hm2L3RuleEntry 8 }

Meaning

Descriptions

2 unique

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

Description 1

The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp. o enforce-amp(9): Packets matching this rule will be forwarded or discarded based on AMP enforcer rules. The selected protocol must be TCP. o enforce-goose(10): Packets matching this rule will be forwarded or discarded based on GOOSE enforcer rules. o enforce-s7(11): Packets matching this rule will be forwarded or discarded based on S7 enforcer rules. The selected protocol should be tcp.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp

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

2 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

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

Status in source: current.

Names: hm2L3Action

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hm2L3Action",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "accept",
    "(",
    "1",
    ")",
    ",",
    "drop",
    "(",
    "2",
    ")",
    ",",
    "reject",
    "(",
    "3",
    ")",
    ",",
    "enforce-modbus",
    "(",
    "4",
    ")",
    ",",
    "enforce-opc",
    "(",
    "5",
    ")",
    ",",
    "enforce-iec104",
    "(",
    "6",
    ")",
    ",",
    "enforce-ethernetip",
    "(",
    "7",
    ")",
    ",",
    "enforce-dnp3",
    "(",
    "8",
    ")",
    ",",
    "enforce-amp",
    "(",
    "9",
    ")",
    ",",
    "enforce-goose",
    "(",
    "10",
    ")",
    ",",
    "enforce-s7",
    "(",
    "11",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp. o enforce-amp(9): Packets matching this rule will be forwarded or discarded based on AMP enforcer rules. The selected protocol must be TCP. o enforce-goose(10): Packets matching this rule will be forwarded or discarded based on GOOSE enforcer rules. o enforce-s7(11): Packets matching this rule will be forwarded or discarded based on S7 enforcer rules. The selected protocol should be tcp.\"",
    "::=",
    "{",
    "hm2L3RuleEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "accept",
            1
          ],
          [
            "drop",
            2
          ],
          [
            "reject",
            3
          ],
          [
            "enforce-modbus",
            4
          ],
          [
            "enforce-opc",
            5
          ],
          [
            "enforce-iec104",
            6
          ],
          [
            "enforce-ethernetip",
            7
          ],
          [
            "enforce-dnp3",
            8
          ],
          [
            "enforce-amp",
            9
          ],
          [
            "enforce-goose",
            10
          ],
          [
            "enforce-s7",
            11
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp. o enforce-amp(9): Packets matching this rule will be forwarded or discarded based on AMP enforcer rules. The selected protocol must be TCP. o enforce-goose(10): Packets matching this rule will be forwarded or discarded based on GOOSE enforcer rules. o enforce-s7(11): Packets matching this rule will be forwarded or discarded based on S7 enforcer rules. The selected protocol should be tcp."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Belden, GarrettCom and Hirschmann IT official standalone MIBs, Hirschmann MIB copies (LibreNMS/Observium Community)1 record · 4 sources

Description 2

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

Status in source: current.

Names: hm2L3Action

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hm2L3Action",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "accept",
    "(",
    "1",
    ")",
    ",",
    "drop",
    "(",
    "2",
    ")",
    ",",
    "reject",
    "(",
    "3",
    ")",
    ",",
    "enforce-modbus",
    "(",
    "4",
    ")",
    ",",
    "enforce-opc",
    "(",
    "5",
    ")",
    ",",
    "enforce-iec104",
    "(",
    "6",
    ")",
    ",",
    "enforce-ethernetip",
    "(",
    "7",
    ")",
    ",",
    "enforce-dnp3",
    "(",
    "8",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp\"",
    "::=",
    "{",
    "hm2L3RuleEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "accept",
            1
          ],
          [
            "drop",
            2
          ],
          [
            "reject",
            3
          ],
          [
            "enforce-modbus",
            4
          ],
          [
            "enforce-opc",
            5
          ],
          [
            "enforce-iec104",
            6
          ],
          [
            "enforce-ethernetip",
            7
          ],
          [
            "enforce-dnp3",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The action of the corresponding rule: o accept(1): Packets matching this rule are accepted and will be forwarded o drop(2): Packets matching this rule will be silently discarded o reject(3): Packets matching this rule will be dropped and the originator gets informed by an ICMP message o enforce-modbus(4): Packets matching this rule are enforced by modbus enforcer and will be forwarded or discarded. The selected protocol should be tcp or udp o enforce-opc(5): Packets matching this rule are enforced by opc enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-iec104(6): Packets matching this rule are enforced by IEC104 enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-ethernetip(7): Packets matching this rule are enforced by EtherNet/IP enforcer and will be forwarded or discarded. The selected protocol should be tcp o enforce-dnp3(8): Packets matching this rule are enforced by dnp3 enforcer and will be forwarded or discarded. The selected protocol should be tcp"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.248)

Nisi Heinz

Siblings (15)