Instead of entering Type/Net/Node/Socket directly,
you could fill in the server name here. The
Type/Net/Node/Socket fields will then be looked
up in the ipxDestServTable. If a service of this
name exists, the values of this rule will be set.
Caution: the Brick IPX does not use this name field
for filtering. It is just meant for easier usage.
Only Type/Net/Node/Socket fields above
will be checked (according to the dont_verify/verify fields)
Parsed from file mibbipx.mib.txt
Company: None
Module: BIANCA-BRICK-IPX-MIB
Instead of entering Type/Net/Node/Socket directly,
you could fill in the server name here. The
Type/Net/Node/Socket fields will then be looked
up in the ipxDestServTable. If a service of this
name exists, the values of this rule will be set.
Caution: the Brick IPX does not use this name field
for filtering. It is just meant for easier usage.
Only Type/Net/Node/Socket fields above
will be checked (according to the dont_verify/verify fields)
Parsed from file BIANCA-BRICK-IPX-MIB.mib
Module: BIANCA-BRICK-IPX-MIB
Vendor: BinTec Communications GmbH
Module: BIANCA-BRICK-IPX-MIB
[Automatically extracted from oidview.com]
sapDenyName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..48)) ACCESS read-write STATUS mandatory DESCRIPTION " Instead of entering Type/Net/Node/Socket directly, you could fill in the server name here. The Type/Net/Node/Socket fields will then be looked up in the ipxDestServTable. If a service of this name exists, the values of this rule will be set. Caution: the Brick IPX does not use this name field for filtering. It is just meant for easier usage. Only Type/Net/Node/Socket fields above will be checked (according to the dont_verify/verify fields) " ::= { sapDenyEntry 12 }
sapDenyName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..48)) ACCESS read-write STATUS mandatory DESCRIPTION " Instead of entering Type/Net/Node/Socket directly, you could fill in the server name here. The Type/Net/Node/Socket fields will then be looked up in the ipxDestServTable. If a service of this name exists, the values of this rule will be set. Caution: the Brick IPX does not use this name field for filtering. It is just meant for easier usage. Only Type/Net/Node/Socket fields above will be checked (according to the dont_verify/verify fields) " ::= { sapDenyEntry 12 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.9.6.1.1 | sapDenyIfIndexMode | 0 | 0 | dont_verify: the interface index is not verified verify: the interface index is not verified delete: delete this rul… |
| 1.3.6.1.4.1.272.4.9.6.1.2 | sapDenyIfIndex | 0 | 0 | This rule is applied to services originating and/or (see sapDenyDirection) destined for the interface with this index. |
| 1.3.6.1.4.1.272.4.9.6.1.3 | sapDenyDirection | 0 | 0 | dont_verify: the direction is not verified outgoing: this rule is applied to services being sent incoming: this rule is … |
| 1.3.6.1.4.1.272.4.9.6.1.4 | sapDenyTypeMode | 0 | 0 | dont_verify: don't check service type verify: check service type |
| 1.3.6.1.4.1.272.4.9.6.1.5 | sapDenyType | 0 | 0 | The service type to be checked. Examples: 4: file server 7: print server |
| 1.3.6.1.4.1.272.4.9.6.1.6 | sapDenyNetMode | 0 | 0 | dont_verify: don't check network number verify: check network number |
| 1.3.6.1.4.1.272.4.9.6.1.7 | sapDenyNet | 0 | 0 | the service's network number to be checked |
| 1.3.6.1.4.1.272.4.9.6.1.8 | sapDenyNodeMode | 0 | 0 | dont_verify: don't check node number verify: check node number |
| 1.3.6.1.4.1.272.4.9.6.1.9 | sapDenyNode | 0 | 0 | the service's node number to be checked |
| 1.3.6.1.4.1.272.4.9.6.1.10 | sapDenySockMode | 0 | 0 | dont_verify: don't check socket number verify: check socket number |
| 1.3.6.1.4.1.272.4.9.6.1.11 | sapDenySock | 0 | 0 | the service's socket number to be checked |