IPF-MIB: View SNMP OID List / Download MIB
VENDOR: SBE
Home | MIB: IPF-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
sbe | 1.3.6.1.4.1.1055 | |||
ipf | 1.3.6.1.4.1.1055.5 | |||
ipfMIBVersion | 1.3.6.1.4.1.1055.5.1 | integer | read-only |
Version number of the IPF MIB. This number will be bumped up whenever there is a change in this MIB. Backward compatibility is a must. The current value = 1 |
ipfVersion | 1.3.6.1.4.1.1055.5.2 | integer | read-only |
Version number of the IPF. This number will be bumped up whenever there is a new release of IPF. Especially important if the FDL syntax changes or when keywords are added. (Deletion not recommended unless backward compatibility is not an issue.) The current value = 1 |
ipfState | 1.3.6.1.4.1.1055.5.3 | integer | read-only |
Whether IP-Filtering is active or not. The factory default is INACTIVE. Enumeration: 'active': 2, 'inactive': 1. |
ipfCommand | 1.3.6.1.4.1.1055.5.4 | integer | read-write |
UPDATE - the rule set is updated. Use the new rules. If there are any parse errors, the UPDATE operation would fail. If there are no parse errors, the parse buffer is emptied. ie. parserRules (see below) will be an empty table. DISABLE - disable all IP-Filter & NAT activities ENABLE - enable IP-Filter & NAT activities with the current set of rules. DELETE - discard the set of rules from the parse buffer. ie. parserRules (see below) will be an empty table. CLEAR - discard the loaded rules. ie. the ipfCurrRules and natCurrRules (see below) will be empty tables. NOTE: A get or get next operation is meaningless on this variable and hence the value returned is always 42. Enumeration: 'clear': 5, 'enable': 3, 'disable': 2, 'update': 1, 'delete': 4. |
ipfDefAction | 1.3.6.1.4.1.1055.5.5 | integer | read-write |
The default action of IP-Filter when a packet does not match any rules. The factory default is to block. Enumeration: 'block': 1, 'pass': 2. |
ipfParseTable | 1.3.6.1.4.1.1055.5.6 | no-access |
Parse buffer. Rules are accumulated here before being applied using an ipfCommand - UPDATE |
|
1.3.6.1.4.1.1055.5.6.2 | no-access |
An IP-Filter or NAT ParseEntry |
||
ipfParseEntryStatus | 1.3.6.1.4.1.1055.5.6.2.1 | integer | read-write |
Indication of whether or not a valid entry. NOTE: A row cannot be modified. You can create or delete a row, but not modify. NOTE: Parsing is done when the status changes to valid. The ipfParseEntryError field (see below) would contain any parse errors. Enumeration: 'create-request': 2, 'valid': 1, 'invalid': 4, 'under-creation': 3. |
ipfParseEntryNumber | 1.3.6.1.4.1.1055.5.6.2.2 | integer | read-only |
Indicates the rule sequence number. The rules are inserted in the ascending sequence number order. NOTE: A set operation will fail if the attempt is to modify the rule number. |
ipfParseEntryText | 1.3.6.1.4.1.1055.5.6.2.3 | displaystring | read-write |
Text string corresponding to a rule. The rule specification language is described else where. NOTE: A set operation will fail if the row is not under creation. |
ipfParseEntryError | 1.3.6.1.4.1.1055.5.6.2.4 | displaystring | read-only |
The parse error. This field is available if the ipfParseEntryStatus field above has a value = valid |
ipfCurrRules | 1.3.6.1.4.1.1055.5.7 | no-access |
The set of rules currently used by IP-Filter |
|
1.3.6.1.4.1.1055.5.7.2 | no-access |
An IP-Filter rule. |
||
ipfCurrRuleStatus | 1.3.6.1.4.1.1055.5.7.2.1 | integer | read-only |
Returns valid(1) always - dummy entry Enumeration: 'create-request': 2, 'valid': 1, 'invalid': 4, 'under-creation': 3. |
ipfCurrRuleNumber | 1.3.6.1.4.1.1055.5.7.2.2 | integer | read-only |
Indicates the rule sequence number |
ipfCurrRuleText | 1.3.6.1.4.1.1055.5.7.2.3 | displaystring | read-only |
Text string corresponding to a rule. The rule specification language is described else where. |
ipfCurrRuleFlags | 1.3.6.1.4.1.1055.5.7.2.4 | integer | read-only |
A bit mapped flags field. Defined values are: FR_BLOCK 0x0001 FR_PASS 0x0002 FR_OUTQUE 0x0004 FR_INQUE 0x0008 FR_LOG 0x0010 /* Log */ FR_LOGB 0x0021 /* Log-fail */ FR_LOGP 0x0022 /* Log-pass */ FR_LOGBODY 0x0040 /* Log the body */ FR_LOGFIRST 0x0080 FR_RETRST 0x0100 FR_RETICMP 0x0200 FR_NOMATCH 0x0400 FR_ACCOUNT 0x0800 /* count packet bytes */ FR_KEEPFRAG 0x1000 FR_KEEPSTATE 0x2000 FR_INACTIVE 0x4000 FR_QUICK 0x8000 |
ipfCurrRuleHits | 1.3.6.1.4.1.1055.5.7.2.5 | integer | read-only |
Number of times this rule was hit - ie. matched. NOTE: Doesn't mean passed or blocked, it just means this rule evaluated as a match for the packet |
ipfCurrRuleBytes | 1.3.6.1.4.1.1055.5.7.2.6 | integer | read-only |
Number of bytes of data seen by this rule. Same as Hits - but in terms of bytes of data. |
natCurrRules | 1.3.6.1.4.1.1055.5.8 | no-access |
The set of rules currently used by NAT |
|
1.3.6.1.4.1.1055.5.8.2 | no-access |
A NAT rule. |
||
natCurrRuleStatus | 1.3.6.1.4.1.1055.5.8.2.1 | integer | read-only |
Returns valid(1) always - dummy entry Enumeration: 'create-request': 2, 'valid': 1, 'invalid': 4, 'under-creation': 3. |
natCurrRuleNumber | 1.3.6.1.4.1.1055.5.8.2.2 | integer | read-only |
Indicates the rule sequence number |
natCurrRuleText | 1.3.6.1.4.1.1055.5.8.2.3 | displaystring | read-only |
Text string corresponding to a rule. The rule specification language is described else where. |
natCurrRuleHits | 1.3.6.1.4.1.1055.5.8.2.4 | integer | read-only |
Indicates the number of packets mapped by this rule |
natCurrRulePend | 1.3.6.1.4.1.1055.5.8.2.5 | integer | read-only |
Indicates the number of packets mapped by this rule |