HM2-FW-MIB
SNMP interface for Hirschmann Firewall modules. Copyright (C)
Main OID:
hm2FwMib.1.3.6.1.4.1.248.11.79
142
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
142 total| Object Name |
|---|
hm2FwMibSNMP interface for Hirschmann Firewall modules. Copyright (C) MODULE-IDENTITY .1.3.6.1.4.1.248.11.79 |
hm2FwNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.0 |
hm2DynFwRuleAppliedTrapA rule of the dynamic firewall was applied. The rule is identified by the given rule index of the rule table. NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.79.0.1 |
hm2DynFwRuleAppliedAndLoggedTrapA rule of the dynamic firewall was applied and logged according to the current logging mechanism. The rule is identified by the given rule index of the rule table. NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.79.0.2 |
hm2L3RuleAppliedTrapA rule of the L3 firewall was applied. The rule is identified by the given rule index of the rule table. NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.79.0.3 |
hm2L3RuleAppliedAndLoggedTrapA rule of the L3 firewall was applied and logged according the current logging mechanism. The rule is identified by the given rule index of the rule table. NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.79.0.4 |
hm2FwObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1 |
hm2FwGeneralSettings OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.1 |
hm2DynFwMaxRulesMaximum number of allowed rules for dynamic firewalling.ro Integer32 .1.3.6.1.4.1.248.11.79.1.1.1 |
hm2L3MaxRulesMaximum number of allowed rules for L3 firewalling.ro Integer32 .1.3.6.1.4.1.248.11.79.1.1.2 |
hm2ResetStatisticsSetting this value to action(2) will reset the statistics of the whole firewall module. It will be set to noop(1) automatically after reset.rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.1.3 |
hm2FlushTablesSetting this value to action(2) will flush all connection tracking states. It will be set to noop(1) automatically after table flush.rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.1.4 |
hm2DefaultPolicyThe default policy for forwarding packets: 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 messagerw Enumeration .1.3.6.1.4.1.248.11.79.1.1.5 |
hm2ConnTrackValidateCheckSumThis value describes, whether the Firewall connection tracking in the Linux kernel shall validate the protocol checksums. Disable this validation (false) improves routing throughput.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.1.6 |
hm2DynFw OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2 |
hm2DynFwRuleObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2.1 |
hm2DynFwRuleCountNumber of current dynamic firewalls rulesro Integer32 .1.3.6.1.4.1.248.11.79.1.2.1.1 |
hm2DynFwIfMappingRuleCountNumber of current DynFw IF mapping entries.ro Integer32 .1.3.6.1.4.1.248.11.79.1.2.1.2 |
hm2DynFwRulePendingActionsThis value describes, whether the DynFW rule table was modified but not yet written to the firewall implementation (set to true). After writing all modifications to the firewall, the value switches automatically back to false.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.2.1.3 |
hm2DynFwCommitPendingActionsSetting this value to action(2) writes not yet committed changes to the firewall (DynFW and Interface Mapping Table). After writing all modifications, the value switches automatically back to noop(1).rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.2.1.4 |
hm2DynFwRuleTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2.2 |
hm2DynFwRuleTableThe list of rules for this dynamic firewall SEQUENCE OF Hm2DynFwRuleEntry .1.3.6.1.4.1.248.11.79.1.2.2.1 |
hm2DynFwRuleEntryDynamic firewall rule entry. Hm2DynFwRuleEntry .1.3.6.1.4.1.248.11.79.1.2.2.1.1 |
hm2DynFwRuleIndexRule index of this dynamic firewall rulero Integer32 ( 1..512 ) .1.3.6.1.4.1.248.11.79.1.2.2.1.1.1 |
hm2DynFwSourceAddressThe source address of the packet to filter. Allowed formats are: - keyword 'any' - single address ('10.0.0.1') - CIDR address range ('10.0.0.0/8') - netobject ('$name')rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.2 |
hm2DynFwSourcePortThe source port of the packet to filter. Allowed formats are: - keyword 'any' - single port ('10') - port range with first and last port separated by hyphen ('10-15') - comma separated list of ports ('1235,25,123') - combination of the points above ('10,25-30,125,1993') The number of named ports (1 for each individual port, 2 for port ranges) must not exceed 15.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.3 |
hm2DynFwTargetAddressThe destination address of the packet to filter. Allowed formats are: - keyword 'any' - single address ('10.0.0.1') - CIDR address range ('10.0.0.0/8') - netobject ('$name')rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.4 |
hm2DynFwTargetPortThe destination port of the packet to filter. Allowed formats are: - keyword 'any' - single port ('10') - port range with first and last port separated by hyphen ('10-15') - comma separated list of ports ('1235,25,123') - combination of the points above ('10,25-30,125,1993') The number of named ports (1 for each individual port, 2 for port ranges) must not exceed 15.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.5 |
hm2DynFwProtoThe IP protocol (RFC 791) for protocol-independent filtering. The following values are currently supported: o icmp(1): internet control message protocol (RFC 792) o igmp(2): internet group management protocol o ipip(3): IP in IP tunnelling (RFC 1853) o tcp(4): transmission control protocol (RFC 793) o udp(5): user datagram protocol (RFC 768) o esp(6): IPsec encapsulated security payload (RFC 2406) o ah(7): IPsec authentication header (RFC 2402) o icmpv6(8): internet control message protocol for IPv6 o any(9): apply to all protocolsrw Enumeration .1.3.6.1.4.1.248.11.79.1.2.2.1.1.6 |
hm2DynFwRuleParamsAdditional parameters to this rule as string. A parameter has the syntax: <param>=<val> Parameters are separated by a comma. If more than one value is given for a parameter, values are separated by a |-sign Following paramters are defined based on the different protocols: o icmp: type=<ICMP type> (specify ICMP type to filter) code=<ICMP code> (specify ICMP code to filter) o tcp: frag=<true/false> (apply to fragments) flags=<SYN/ACK/FIN> (apply to packets with give flags o udp/tcp: state=<new/rel/est> (apply to packets according current state of connection> o general: mac=<MAC> (specify source MAC address for this rule)rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.7 |
hm2DynFwActionThe 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 messagerw Enumeration .1.3.6.1.4.1.248.11.79.1.2.2.1.1.8 |
hm2DynFwLogSet to true if application of this rule shall be loggedrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.2.2.1.1.9 |
hm2DynFwTrapSet to true if application of this rule shall send a trap.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.2.2.1.1.10 |
hm2DynFwRowStatusThis is a standard row status value: - active(1): The rule is active. Note that until committed, the rule will not be applied. - notInService(2): The rule is inactive because of user action. - notReady(3): The rule is inactive because of agent action. - createAndGo(4): Create the rule with default parameters activated. - createAndWait(5): Create the rule inactive. - destroy(6): Delete the rule. You cannot delete a rule with interface mappings to it.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.2.2.1.1.11 |
hm2DynFwDescriptionUser defined textual description related to this rule.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.2.2.1.1.12 |
hm2DynFwRuleIfMappingTableTable for mapping L3 rules to interfaces SEQUENCE OF Hm2DynFwRuleIfMappingEntry .1.3.6.1.4.1.248.11.79.1.2.2.2 |
hm2DynFwRuleIfMappingEntryEntry in rule interface mapping table Hm2DynFwRuleIfMappingEntry .1.3.6.1.4.1.248.11.79.1.2.2.2.1 |
hm2DynFwIfmRuleIndexThe index of the DynFw rule this mapping entry is assigned to. The DynFw rule must exist before creation of mapping entry. Integer32 .1.3.6.1.4.1.248.11.79.1.2.2.2.1.1 |
hm2DynFwIfmDirectionMeanings: - 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. Enumeration .1.3.6.1.4.1.248.11.79.1.2.2.2.1.2 |
hm2DynFwIfmPriorityThe priority is the sorting key for rules in to this interface. They don't need to be unique, but no clear order can be assumed among rules with the same priority. Priorities are processed in ascending order (0 highest priority).rw Unsigned32 .1.3.6.1.4.1.248.11.79.1.2.2.2.1.3 |
hm2DynFwIfmInterfaceThe interface this mapping entry is applied to. This has to be either an hm2AgentSwitchIpInterfaceIfIndex or an hm2AgentSwitchIpVlanIfIndex. Note that for physical interfaces this only works if the corresponding hm2AgentSwitchIpInterfaceRoutingMode is set to enable. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.248.11.79.1.2.2.2.1.4 |
hm2DynFwIfmRowStatusThe RowStatus value for this entry with the usual meanings: - active(1): The interface mapping is in place - notInService(2): The interface mapping is not in place because the user said so - notReady(3): The interface mapping is not in place because the agent said so - createAndGo(4): Create this mapping with the default priority and activate it. - createAndWait(5): Create this mapping deactivated. - destroy(6): Destroy this interface mapping.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.2.2.2.1.5 |
hm2DynFwStats OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2.4 |
hm2DynFwGeneralStats OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2.4.1 |
hm2DynFwStatsTtPckTotal number of packets processed by the dynamic firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.1.1 |
hm2DynFwStatsTtPckSizeTotal number of bytes processed by the dynamic firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.1.2 |
hm2DynFwStatsTtPckDenDropTotal number of packets dropped or denied by the dynamic firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.1.3 |
hm2DynFwStatsTtPckAcceptedTotal number of packets accepted by the dynamic firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.1.4 |
hm2DynFwStatsTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.2.4.2 |
hm2DynFwStatsRuleTableTable of per-rule statistics of the dynamic firewall SEQUENCE OF Hm2DynFwStatsRuleEntry .1.3.6.1.4.1.248.11.79.1.2.4.2.1 |
hm2DynFwStatsRuleEntryStatistics table entry for the dynamic firewall Hm2DynFwStatsRuleEntry .1.3.6.1.4.1.248.11.79.1.2.4.2.1.1 |
hm2DynFwStatsPacketCountNumber of packets matched by this rulero Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.2.1.1.1 |
hm2DynFwStatsPacketSizeNumber of bytes processed by this rulero Counter64 .1.3.6.1.4.1.248.11.79.1.2.4.2.1.1.2 |
hm2DynFwStatsLastAppliedLocal system time (hm2SystemLocalTime) when the rule was applied the last timero HmTimeSeconds1970 (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.2.4.2.1.1.3 |
hm2L3Fw OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3 |
hm2L3RuleObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.1 |
hm2L3RuleCountNumber of current L3 rulesro Integer32 .1.3.6.1.4.1.248.11.79.1.3.1.1 |
hm2L3IfMappingRuleCountNumber of current L3 IF mapping entries.ro Integer32 .1.3.6.1.4.1.248.11.79.1.3.1.2 |
hm2L3RulePendingActionsThis value describes, whether the L3 rule table was modified but not yet written to the firewall implementation (set to true). After writing all modifications to the firewall, the value switches automatically back to false.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.1.3 |
hm2L3CommitPendingActionsSetting this value to action(2) writes not yet committed changes to the firewall (L3 and Interface Mapping Table). After writing all modifications, the value switches automatically back to noop(1).rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.3.1.4 |
hm2L3RuleTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.2 |
hm2L3RuleTableThe list of L3 rules for this firewall SEQUENCE OF Hm2L3RuleEntry .1.3.6.1.4.1.248.11.79.1.3.2.1 |
hm2L3RuleEntryL3 rule entry. Hm2L3RuleEntry .1.3.6.1.4.1.248.11.79.1.3.2.1.1 |
hm2L3RuleIndexRule index of this L3 rulero Integer32 ( 1..2048 ) .1.3.6.1.4.1.248.11.79.1.3.2.1.1.1 |
hm2L3SourceAddressThe source address of the packet to filter. Allowed formats are: - keyword 'any' - single address ('10.0.0.1') - CIDR address range ('10.0.0.0/8') - netobject ('$name') - a prepending '!' selects the complement setrw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.2 |
hm2L3SourcePortThe source port of the packet to reroute. Allowed formats are: - keyword 'any' - single port ('10') - port range with first and last port separated by hyphen ('10-15') - comma separated list of ports ('1235,25,123') - combination of the points above ('10,25-30,125,1993') The number of named ports (1 for each individual port, 2 for port ranges) must not exceed 15.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.3 |
hm2L3TargetAddressThe destination address of the packet to filter. Allowed formats are: - keyword 'any' - single address ('10.0.0.1') - CIDR address range ('10.0.0.0/8') - netobject ('$name')rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.4 |
hm2L3TargetPortThe destination port of the packet to. Allowed formats are: - keyword 'any' - single port ('10') - port range with first and last port separated by hyphen ('10-15') - comma separated list of ports ('1235,25,123') - combination of the points above ('10,25-30,125,1993') The number of named ports (1 for each individual port, 2 for port ranges) must not exceed 15.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.5 |
hm2L3ProtoThe IP protocol (RFC 791) for protocol-independent filtering. The following values are currently supported: o icmp(1): internet control message protocol (RFC 792) o igmp(2): internet group management protocol o ipip(3): IP in IP tunnelling (RFC 1853) o tcp(4): transmission control protocol (RFC 793) o udp(5): user datagram protocol (RFC 768) o esp(6): IPsec encapsulated security payload (RFC 2406) o ah(7): IPsec authentication header (RFC 2402) o icmpv6(8): internet control message protocol for IPv6 o any(9): apply to all protocolsrw Enumeration .1.3.6.1.4.1.248.11.79.1.3.2.1.1.6 |
hm2L3RuleParamsAdditional parameters to this rule as string. A parameter has the syntax: <param>=<val> Parameters are separated by a comma. If more than one value is given for a parameter, values are separated by a |-sign (pipe). Following parameters are defined based on the different protocols: o icmp: type=<ICMP type> (specify ICMP type to filter) code=<ICMP code> (specify ICMP code to filter) o tcp: flags=<SYN/ACK/FIN> (apply to packets with given flags) o general: state=<new/rel/est> (apply to packets according to current state of connection>) mac=<MAC> (specify source MAC address for this rule) frag=<true/false> (apply to fragments)rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.7 |
hm2L3ActionThe 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 tcprw Enumeration .1.3.6.1.4.1.248.11.79.1.3.2.1.1.8 |
hm2L3LogSet to true if application of this rule shall be loggedrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.2.1.1.9 |
hm2L3TrapSet to true if application of this rule shall send a trap.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.2.1.1.10 |
hm2L3RowStatusThis is a standard row status value: - active(1): The rule is active. Note that until committed, the rule will not be applied. You cannot activate the rule if an enforcer mappings to an inactive profile. - notInService(2): The rule is inactive because of user action. - notReady(3): The rule is inactive because of agent action. - createAndGo(4): Create the rule with default parameters activated. - createAndWait(5): Create the rule inactive. - destroy(6): Delete the rule. You cannot delete a rule with interface mappings to it.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.2.1.1.11 |
hm2L3DescriptionUser defined textual description related to this rule.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.2.1.1.12 |
hm2DPIProfileIndexThe index of the DPI profile this rule is assigned to depending on enforcer action. Value 0 no DPI profile this rule is assigned to. You cannot assign the rule to an inactive profile if an active enforcer will mapping to it.rw Integer32 .1.3.6.1.4.1.248.11.79.1.3.2.1.1.13 |
hm2L3RuleIfMappingTableTable for mapping L3 rules to interfaces SEQUENCE OF Hm2L3RuleIfMappingEntry .1.3.6.1.4.1.248.11.79.1.3.2.2 |
hm2L3RuleIfMappingEntryEntry in rule interface mapping table Hm2L3RuleIfMappingEntry .1.3.6.1.4.1.248.11.79.1.3.2.2.1 |
hm2L3IfmRuleIndexThe index of the L3 rule this mapping entry is assigned to. The rule must exist before the mapping entry can be created. Integer32 .1.3.6.1.4.1.248.11.79.1.3.2.2.1.1 |
hm2L3IfmDirectionMeanings: - 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. Enumeration .1.3.6.1.4.1.248.11.79.1.3.2.2.1.2 |
hm2L3IfmPriorityThe priority is the sorting key for rules in to this interface. They don't need to be unique, but no clear order can be assumed among rules with the same priority. Priorities are processed in ascending order (0 highest priority.rw Unsigned32 .1.3.6.1.4.1.248.11.79.1.3.2.2.1.3 |
hm2L3IfmInterfaceThe interface this mapping entry is assigned to. This has to be either an hm2AgentSwitchIpInterfaceIfIndex or an hm2AgentSwitchIpVlanIfIndex. Note that for physical interfaces this only works if the corresponding hm2AgentSwitchIpInterfaceRoutingMode is set to enable. InterfaceIndex (IF-MIB) .1.3.6.1.4.1.248.11.79.1.3.2.2.1.4 |
hm2L3IfmRowStatusThe RowStatus value for this entry with the usual meanings: - active(1): The interface mapping is in place - notInService(2): The interface mapping is not in place because the user said so - notReady(3): The interface mapping is not in place because the agent said so - createAndGo(4): Create this mapping with the default priority and activate it. - createAndWait(5): Create this mapping deactivated. - destroy(6): Destroy this interface mapping.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.2.2.1.5 |
hm2L3Stats OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.4 |
hm2L3GeneralStats OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.4.1 |
hm2L3StatsTotalPckTotal number of packets processed by the L3 firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.1.1 |
hm2L3StatsTotalPckSizeTotal number of bytes processed by the L3 firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.1.2 |
hm2L3StatsTotalPckDenDropTotal number of packets dropped or denied by the L3 firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.1.3 |
hm2L3StatsTotalPckAcceptedTotal number of packets accepted by the L3 firewallro Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.1.4 |
hm2L3StatsTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.4.2 |
hm2L3StatsRuleTableTable of per-rule statistics of the L3 firewall SEQUENCE OF Hm2L3StatsRuleEntry .1.3.6.1.4.1.248.11.79.1.3.4.2.1 |
hm2L3StatsRuleEntryStatistics table entry for the L3 firewall Hm2L3StatsRuleEntry .1.3.6.1.4.1.248.11.79.1.3.4.2.1.1 |
hm2L3StatsPacketCountNumber of packets matched by this rulero Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.2.1.1.1 |
hm2L3StatsPacketSizeNumber of bytes processed by this rulero Counter64 .1.3.6.1.4.1.248.11.79.1.3.4.2.1.1.2 |
hm2L3StatsLastAppliedTime of last application of the rule in seconds since the Unix epoch.ro HmTimeSeconds1970 (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.3.4.2.1.1.3 |
hm2DPIProfileModbusObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.11 |
hm2DPIProfileModbusPendingActionsThis value describes, whether the DPI MODBUS profile table was modified but not yet written to the enforcer implementation (set to true). After writing all modifications to the enforcer, the value switches automatically back to false.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.11.1 |
hm2DPIProfileModbusCommitPendingActionsSetting this value to action(2) writes not yet committed changes to the enforcer (DPI MODBUS Profile Table). After writing all modifications, the value switches automatically back to noop(1).rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.3.11.2 |
hm2DPIProfileOpcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.12 |
hm2DPIProfileOpcPendingActionsThis value describes, whether the L3 OPC profile table was modified but not yet written to the enforcer implementation (set to true). After writing all modifications to the enforcer, the value switches automatically back to false.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.12.1 |
hm2DPIProfileOpcCommitPendingActionsSetting this value to action(2) writes not yet committed changes to the enforcer (DPI OPC Profile Table). After writing all modifications, the value switches automatically back to noop(1).rw HmActionValue (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.3.12.2 |
hm2DPIProfileTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.3.21 |
hm2DPIProfileModbusTableThe list of DPI MODBUS profiles for this enforcer SEQUENCE OF Hm2DPIProfileModbusEntry .1.3.6.1.4.1.248.11.79.1.3.21.1 |
hm2DPIProfileModbusEntryDPI MODBUS profile entry. Hm2DPIProfileModbusEntry .1.3.6.1.4.1.248.11.79.1.3.21.1.1 |
hm2DPIProfileModbusIndexProfile index of this DPI MODBUS profilero Integer32 ( 1..32 ) .1.3.6.1.4.1.248.11.79.1.3.21.1.1.1 |
hm2DPIProfileModbusDescriptionUser defined textual description related to this profile.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.21.1.1.2 |
hm2DPIProfileModbusFunctionTypeThe function types of the corresponding function codes: o readonly(1): Selects read only function codes for the function code list. o readwrite(2): Selects read write function codes for the function code list. o programming(3): Selects programming function codes for the function code list. o all(4): Selects all possible function codes for the function code list. Any function code will be allowed. o advanced(5): Keeps the function code list from the previous selection and makes it editable by the user.rw Enumeration .1.3.6.1.4.1.248.11.79.1.3.21.1.1.3 |
hm2DPIProfileModbusFunctionCodeListThe function codes for this enforcer as string. A function code has the syntax: <val> Function codes are separated by a comma. If more than one value is given for a function code, values are separated by a | -sign (pipe). Following function codes are defined: <1..255>|<0-65535>|<0-65535> (apply to packets with given function codes <1..255>, address range <0-65535>, address range <0-65535>) 1|<0-65535> (apply to packets with given function code read coils, coil address range <0-65535>) 2|<0-65535> (apply to packets with given function code read discrete inputs, input address range <0-65535>) 3|<0-65535> (apply to packets with given function code read holding registers, register address range <0-65535>) 4|<0-65535> (apply to packets with given function code read input registers, register address range <0-65535>) 5|<0-65535> (apply to packets with given function code write single coil, coil address range <0-65535>) 6|<0-65535> (apply to packets with given function code write single register, register address range <0-65535>) 7 (apply to packets with given function code read exception status) 8 (apply to packets with given function code diagnostic) 11 (apply to packets with given function code get com event counter) 12 (apply to packets with given function code get comm event log) 13 (apply to packets with given function code program (584/984)) 14 (apply to packets with given function code poll (584/984)) 15|<0-65535> (apply to packets with given function code write multiple coils, coil address range <0-65535>) 16|<0-65535> (apply to packets with given function code write multiple registers, register address range <0-65535>) 17 (apply to packets with given function code report slave id) 20 (apply to packets with given function code read file record) 21 (apply to packets with given function code write file record) 22|<0-65535> (apply to packets with given function code mask write register, register address range <0-65535>) 23|<0-65535>|<0-65535> (apply to packets with given function code read/write multiple registers, read address range <0-65535>, write address range <0-65535>) 24|<0-65535> (apply to packets with given function code read fifo queue, pointer address range <0-65535>) 40 (apply to packets with given function code program (concept)) 42 (apply to packets with given function code concept symbol table) 43 (apply to packets with given function code encapsulated interface transport) 48 (apply to packets with given function code advantech co. ltd. - management functions) 66 (apply to packets with given function code scan data inc. - expanded read holding registers) 67 (apply to packets with given function code scan data inc. - expanded write holding registers) 90 (apply to packets with given function code unity programming/ofs) 100 (apply to packets with given function code scattered register read) 125 (apply to packets with given function code schneider electric - firmware replacement) 126 (apply to packets with given function code schneider electric - program)rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.21.1.1.4 |
hm2DPIProfileModbusUnitIdentifierListUnit identifiers for this enforcer as string. A unit identifier has the syntax: <val> To specify no options, the value 'none' must be given. Unit identifiers are separated by a comma. Following unit identifiers are defined: <0..255> (apply to packets for which a unit identifier is set)rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.21.1.1.5 |
hm2DPIProfileModbusSanityCheckSet to true if apply to packets for which a sanity check including format and specification shall be donerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.1.1.6 |
hm2DPIProfileModbusExceptionSet to true if apply to packets for which a device exception message shall be sentrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.1.1.7 |
hm2DPIProfileModbusResetSet to true if apply to packets for which a reset connection message shall be sentrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.1.1.8 |
hm2DPIProfileModbusRowStatusThis is a standard row status value: - active(1): The profile is active. You cannot modify it. - notInService(2): The profile is inactive because of user action. You cannot inactivate the profile if an active enforcer mappings to it. - notReady(3): The profile is inactive because of agent action. - createAndGo(4): Create the profile with default parameters activated. - createAndWait(5): Create the profile inactive. - destroy(6): Delete the profile. You cannot delete the active profile or if an enforcer mappings to it.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.1.1.9 |
hm2DPIProfileOpcTableThe list of DPI OPC profiles for this enforcer SEQUENCE OF Hm2DPIProfileOpcEntry .1.3.6.1.4.1.248.11.79.1.3.21.2 |
hm2DPIProfileOpcEntryDPI OPC profile entry. Hm2DPIProfileOpcEntry .1.3.6.1.4.1.248.11.79.1.3.21.2.1 |
hm2DPIProfileOpcIndexProfile index of this DPI OPC profilero Integer32 ( 1..32 ) .1.3.6.1.4.1.248.11.79.1.3.21.2.1.1 |
hm2DPIProfileOpcDescriptionUser defined textual description related to this profile.rw DisplayString ( SIZE .1.3.6.1.4.1.248.11.79.1.3.21.2.1.2 |
hm2DPIProfileOpcSanityCheckSet to true if apply to packets for which a sanity check including format and specification shall be donerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.2.1.3 |
hm2DPIProfileOpcFragmentCheckSet to true if apply to packets for which a fragment check shall be donerw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.2.1.4 |
hm2DPIProfileOpcTimeoutConnectSet to nonzero if apply to packets for which a timeout at connect in seconds shall be done. Value 0 disables this match criteria.rw Unsigned32 .1.3.6.1.4.1.248.11.79.1.3.21.2.1.5 |
hm2DPIProfileOpcRowStatusThis is a standard row status value: - active(1): The profile is active. You cannot modify it. - notInService(2): The profile is inactive because of user action. You cannot inactivate the profile if an active enforcer mappings to it. - notReady(3): The profile is inactive because of agent action. - createAndGo(4): Create the profile with default parameters activated. - createAndWait(5): Create the profile inactive. - destroy(6): Delete the profile. You cannot delete the active profile or if an enforcer mappings to it.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.3.21.2.1.6 |
hm2FwLearningMode OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.4 |
hm2FLMObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.4.1 |
hm2FLMAdminStateEnable or disable the Firewall Learning Mode.rw HmEnabledStatus (HM2-TC-MIB) .1.3.6.1.4.1.248.11.79.1.4.1.1 |
hm2FLMActionActions to control the Firewall Learning Mode.rw Enumeration .1.3.6.1.4.1.248.11.79.1.4.1.2 |
hm2FLMAppStateState of running FLM Application.ro Enumeration .1.3.6.1.4.1.248.11.79.1.4.1.3 |
hm2FLMAppInfoEnumMemory status of FLM Application.ro Enumeration .1.3.6.1.4.1.248.11.79.1.4.1.4 |
hm2FLMAppInfoStringSpecial status message.ro SnmpAdminString .1.3.6.1.4.1.248.11.79.1.4.1.5 |
hm2FLML3EntriesNumber of Layer 3 entries in the connection table.ro Unsigned32 .1.3.6.1.4.1.248.11.79.1.4.1.6 |
hm2FLMFreeMemFree memory(%) for learning data.ro Unsigned32 .1.3.6.1.4.1.248.11.79.1.4.1.7 |
hm2FLMMaxEntriesNumber of maximum interface entries that can be selected.ro Unsigned32 .1.3.6.1.4.1.248.11.79.1.4.1.8 |
hm2FLMTables OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.1.4.2 |
hm2FLMInterfaceTableThe list of interfaces selected for Firewall Learning Mode. SEQUENCE OF Hm2FLMInterfaceEntry .1.3.6.1.4.1.248.11.79.1.4.2.1 |
hm2FLMInterfaceEntryInterface selected for Firewall Learning Mode. Hm2FLMInterfaceEntry .1.3.6.1.4.1.248.11.79.1.4.2.1.1 |
hm2FLMInterfaceIndexInterface index of the entry.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.248.11.79.1.4.2.1.1.1 |
hm2FLMInterfaceRowStatusThis is a standard row status value: - active(1): The interface is active. - notInService(2): The interface is inactive because routing was disabled. - notReady(3): The interface is inactive because of agent action. - createAndGo(4): Create the interface with default parameters activated. - createAndWait(5): Create the interface inactive. - destroy(6): Delete the interface.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.79.1.4.2.1.1.2 |
hm2FwConformance OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.2 |
hm2FwCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.2.1 |
hm2FwComplianceThe compliance statement for an SNMP entity which implements the Hirschmann firewall MIB. Unknown .1.3.6.1.4.1.248.11.79.2.1.1 |
hm2FwGroups OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.79.2.2 |
hm2FwGeneralGroupA collection of all Hirschmann objects provided by the firewall module. Unknown .1.3.6.1.4.1.248.11.79.2.2.1 |
hm2FwNotificationsGroupA collection of all Hirschmann notifications provided by the firewall module. Unknown .1.3.6.1.4.1.248.11.79.2.2.2 |