POLICY-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for POLICY-MIB.
87
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
87 total| Object Name |
|---|
ipPolicyMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.81.36 |
RFC1155-SMI Unknown .1.3.6.1.4.1.81.36 |
ipPolicyListTableThis table is used to add/delete/monitor policy lists.
This table maintains a list of policy lists in the system.
Each POLICY list is made up of a group of policy rules.
The policy rules are stored in the ipPolicyRuleTable.
Number of lists in a device (both in run-time and in NVRAM) is not
part of the syntax of this mib.
This is a device issue that should be agreed between the device and
the managment applications and should be specified in the
device and/or managment Spec.
RNR for example needs 3 lists : 1 for validation + 2 for activation SEQUENCE OF IpPolicyListEntry .1.3.6.1.4.1.81.36.1 |
ipPolicyListEntryThe information concerning one of the IP policy lists IpPolicyListEntry .1.3.6.1.4.1.81.36.1.1 |
ipPolicyListSlotThe slot-id (AKA module-id / box number) to which this list relatesro INTEGER .1.3.6.1.4.1.81.36.1.1.1 |
ipPolicyListIDThe ID of the list.
Lists 100-149 are for a local policy manager use (for example CLI or
Routing Manager).
Lists 150-199 are for a remote policy manager use (for example RNR).ro INTEGER .1.3.6.1.4.1.81.36.1.1.2 |
ipPolicyListNameName of this list.
Default name is: list #Nrw DisplayString .1.3.6.1.4.1.81.36.1.1.3 |
ipPolicyListValidityStatusValidity status of this list:
valid - For all rules in the list:
ipPolicyRuleApplicabilityStatus = applicable
partiallyValid - in One or more rules in the list
ipPolicyRuleApplicabilityPrecedence < 9999 (not mandatory) and
ipPolicyRuleApplicabilityStatus != applicable
In all other rules (if any) :
ipPolicyRuleApplicabilityStatus=applicable
invalid - In One or more rules in the list
ipPolicyRuleApplicabilityPrecedence=9999 (mandatory) and
ipPolicyRuleApplicabilityStatus != applicable
validationInProgress - The current validity of the list is currently
computed. Managment station should poll the device until one of
the definitive values is returned.ro Enumeration .1.3.6.1.4.1.81.36.1.1.4 |
ipPolicyListChecksumChecksum of all the configurable (read/write) mib items that are
part of this list or part of any rule that belongs to this list.
Addition/deletion/modification of a rule in this list shall result in
a checksum change.
This field can be used by the management application to discover this
list has changed (instead of polling all the rules of the list).roobsolete INTEGER .1.3.6.1.4.1.81.36.1.1.5 |
ipPolicyListRowStatusUsed for creation/deletion of a list and for monitoring list status.
Use CreateAndWait (5) to create a list.
Destroy (6) to destroy a list. The active list can NOT
be destroyed. Destroying a list automatically removes all
the rules in this list.
active (1) is returned when a list is the active list
NotInService is returned when the list is not the active listrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.81.36.1.1.6 |
ipPolicyListDefaultOperationThe operation that should be applied to a packet in case the packet
does not match any of the user specified rules. Some of the values
are Access Control operations and some are priority operations.rw Enumeration .1.3.6.1.4.1.81.36.1.1.7 |
ipPolicyListCookieA cookie to be associated with this list. This mib item can be used
by the management application as a unique ID of the list.
Note: The Agent is not aware of the contents of this cookie.
Its only purpose is to help the managment application.
Changing this cookie resets ipPolicyListTrackChanges to notChanged state.
A value of 0 means Cookie not available.rw INTEGER .1.3.6.1.4.1.81.36.1.1.8 |
ipPolicyListTrackChangesCounts the number of changes made to the configuration of the list
including changes to the rules that are part of the list.
This counters is set to 0 when the list is being created.
It is also set to 0 when ipPolicyListCookie is changed.
This mib item together with the ipPolicyListCookie can be used by the
management application to determine if this policy list was changed,
and if two instances of this list on different devices are the same.ro INTEGER .1.3.6.1.4.1.81.36.1.1.9 |
ipPolicyListOwnerThe entity that configured this listrw DisplayString .1.3.6.1.4.1.81.36.1.1.10 |
ipPolicyListErrMsgFree text describing the reason why the list is not valid.
When the list is valid returns NULL string.
The values returned for this MIB are not affected by the list
status (active/inactive).ro DisplayString .1.3.6.1.4.1.81.36.1.1.11 |
ipPolicyRuleTableThis table is used to add/delete/modify/monitor individual policy rules
in a policy list. SEQUENCE OF IpPolicyRuleEntry .1.3.6.1.4.1.81.36.2 |
ipPolicyRuleEntryControls all the conditional fields and its parameters for
a policy rule. IpPolicyRuleEntry .1.3.6.1.4.1.81.36.2.1 |
ipPolicyRuleSlotThe slot-id (AKA module-id / box number) to which this rule relatesro INTEGER .1.3.6.1.4.1.81.36.2.1.1 |
ipPolicyRuleListIDThe ID of the list this rule is part of.
Lists 150-199 are for RNR use.ro INTEGER .1.3.6.1.4.1.81.36.2.1.2 |
ipPolicyRuleIDNumber of rule within its list. Each list may contain many rule.
Lists work in a First Match manner. A rule with a lower ID would
be preferred over a rule with a higher ID.ro INTEGER .1.3.6.1.4.1.81.36.2.1.3 |
ipPolicyRuleSrcAddrThe IP address of the source station. A value of 255.255.255.255
in ipPolicyRuleSrcAddrWild indicates this is a DON'T CARE field.rw IpAddress .1.3.6.1.4.1.81.36.2.1.4 |
ipPolicyRuleSrcAddrWildThis field specifies the wildcard of the source IP address.
Note that a the mask for a single host is 0.0.0.0 and the mask for all
hosts is 255.255.255.255. This field can has any combination of bits
set allowing all kind of rules.
For example ipPolicyRuleSrcAddr=192.168.0.254,
ipPolicyRuleSrcAddrWild=0.0.255.0
matches all packets with source ip address 192.168.*.254rw IpAddress .1.3.6.1.4.1.81.36.2.1.5 |
ipPolicyRuleDstAddrThe IP address of the destination station.
A value of 255.255.255.255 in ipPolicyRuleDstAddrWild indicates this
is a DON'T CARE field.rw IpAddress .1.3.6.1.4.1.81.36.2.1.6 |
ipPolicyRuleDstAddrWildThis field specifies the wildcard of the destination IP address.
Note that a the mask for a single host is 0.0.0.0 and the mask for
all hosts is 255.255.255.255. This field can has any combination of
bits set allowing all kind of rules.
For example ipPolicyRuleDstAddr=192.168.0.254,
ipPolicyRuleDstAddrWild=0.0.255.0
matches all packets with destination ip address 192.168.*.254rw IpAddress .1.3.6.1.4.1.81.36.2.1.7 |
ipPolicyRuleProtocolThe IP protocol to which this rule relates.
Use 256 to specify IP (i.e. don't care)rw INTEGER .1.3.6.1.4.1.81.36.2.1.8 |
ipPolicyRuleL4SrcPortMinThe minimal source port number.
This fields is applicable only when ipPolicyRuleProtocol is TCP(6)
UDP(17). In all other cases its values is not used.rw INTEGER .1.3.6.1.4.1.81.36.2.1.9 |
ipPolicyRuleL4SrcPortMaxThe maximal source port number.
This fields is applicable only when ipPolicyRuleProtocol is TCP(6) or
UDP(17). In all other cases its values is not used.rw INTEGER .1.3.6.1.4.1.81.36.2.1.10 |
ipPolicyRuleL4DestPortMinThe minimal destination port number.
This fields is applicable only when ipPolicyRuleProtocol is TCP(6)
or UDP(17). In all other cases its values is not used.rw INTEGER .1.3.6.1.4.1.81.36.2.1.11 |
ipPolicyRuleL4DestPortMaxThe maximal destination port number.
This fields is applicable only when ipPolicyRuleProtocol is TCP(6)
or UDP(17). In all other cases its value is not used.rw INTEGER .1.3.6.1.4.1.81.36.2.1.12 |
ipPolicyRuleEstablishedThis field indicates the value of the established bit in
the TCP header. If protocol is not TCP this values is not used.rw Enumeration .1.3.6.1.4.1.81.36.2.1.13 |
ipPolicyRuleOperationThe operation that should be applied to a packet in case the packet
matches the rule. Some of the values are Access Control operations
and some are priority operations.rw Enumeration .1.3.6.1.4.1.81.36.2.1.14 |
ipPolicyRuleApplicabilityPrecedenceThis field indicates how important is it to enforce this rule.
The higher the number the more important it is to enforce this rule.
The value 9999 has a special meaning of Mandatory which means this
rule MUST be enforced.
Note: Access control rules are probably Mandatory rule where as QoS rules
might be configured by the user as optional rules in some cases.
Device may choose to support only a subset of these values.
P333R supports two values:
9999 - Mandatory rule
0 - Optional rule.rw INTEGER .1.3.6.1.4.1.81.36.2.1.15 |
ipPolicyRuleApplicabilityStatusUsed to monitor if a rule is currently applicable (for the active list)
or would be applicable (if the list becomes active).
The values returned for this MIB are not affected by the list status
active/inactive)
applicable - This rule is/would be applicable
partiallyApplicable - This rule is/would be applicable for some
packets/sessions but might not be applicable for other
packets/sessions
notApplicable - This rule is NOT/would NOT be applicable
unknown - Status is temporary unknown. This may be because the list
validation is inProgress. Querying this item triggeres list
validation if not already triggered.ro Enumeration .1.3.6.1.4.1.81.36.2.1.16 |
ipPolicyRuleApplicabilityTypeUsed to monitor the ApplicabilityStatus of the rule in the context of
this list. The values returned for this MIB are not affected by the
list status (active/inactive)
static - The applicabilityStatus of this rule is guaranteed
regardless of the ApplicabilityPrecedence of this rule
or of other rules in the list.
quasiStatic - The applicability status of this rule is
guaranteed if no configuration changes are made,
BUT changes of ApplicabilityPrecedence of this rule or
other rules in this list may change the applicabilityStatus
of this rule.
dynamic - The applicabilityStatus of this rule can change
depending on network conditions (i.e. localization) or
other conditions such as (but not limited to) changes of
ApplicabilityPrecedence of this rule or other rules in
this list.
unknown - Status is temporary unknown. This may be because the
list validation is inProgress. Querying this item triggeres
list validation if not already triggered.
The values returned for this MIB are not affected by the list
status (active/inactive)ro Enumeration .1.3.6.1.4.1.81.36.2.1.17 |
ipPolicyRuleErrMsgFree text describing the reason why the rule is not Applicable.
When rule is Applicable returns NULL string.
The values returned for this MIB are not affected by the list status
(active/inactive)ro DisplayString .1.3.6.1.4.1.81.36.2.1.18 |
ipPolicyRuleStatusUsed to configure and monitor one rule.
Use CreateAndWait (4) to create a rule.
Destroy (6) to destroy a rule
active (1) is returned when a rule is complete and is configured
into device HW
NotReady (3) is returned when not all mandatory fields in the
rule have been configured or the rule is not valid.
Not In Service (2) is returned when the rule is not active
because the list is not active or device lacks resources
to support the rulerw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.81.36.2.1.19 |
ipPolicyRuleDSCPOperationThe New DSCP value that should be applied to packets that meatch this rule.
A value of 64 means no change.rw INTEGER .1.3.6.1.4.1.81.36.2.1.20 |
ipPolicyControlTableThis table activates & monitors the policy application SEQUENCE OF IpPolicyControlEntry .1.3.6.1.4.1.81.36.3 |
ipPolicyControlEntryEach entry relates to one slot (AKA module / box) in the stack IpPolicyControlEntry .1.3.6.1.4.1.81.36.3.1 |
ipPolicyControlSlotThe slot-id (AKA module-id / box number) to which this control entry
relatesro INTEGER .1.3.6.1.4.1.81.36.3.1.1 |
ipPolicyControlActiveGeneralListThe ipPolicyListID of the Active general policy List on this slot.
A value of Zero means there is no active list.
If the new list can not be activated the old list continues to be
activerw INTEGER .1.3.6.1.4.1.81.36.3.1.2 |
ipPolicyControlAllowedPolicyManagersSpecify if who is allowed to configure policy on the device.
local - a local policy manager is allowed to configure
(using CLI or SNMP)
remote - A remote policy manger is allowed to configure
(using CLI or SNMP)
The distinction between local & remote managers is done according to the
List ID. Local & Remote managers use different ranges.
When changing the value of this item, device may choose from resources
or other reasons to automatically remove all or some of the lists
that were configured bt the previous type of manager.rw Enumeration .1.3.6.1.4.1.81.36.3.1.3 |
ipPolicyControlCurrentChecksumChecksum of the entire CURRENT Policy Database including (but not
limited to) the following :
o ipPolicyControlActiveGeneralList
o ipPolicyControlAllowedPolicyManagers
o ipPolicyListCookie &
ipPolicyListTrackChanges of the active list (if exists)
o ipPolicyDiffServControlChecksum
o routeGroupRouterMode
additional configuration fields that are important enough to cause
re-configuration by RNR.
Any change in any of the above policy parmeters shall result in a
change in the value of this field. Polling of this value shall reveal
any change of policy configuration without the need for polling of
the entire policy database.ro INTEGER .1.3.6.1.4.1.81.36.3.1.4 |
ipPolicyControlMinimalPolicyManagmentVersionThe minimal policy management version that this device inter operates
with as verified by actual testing.
For example: The P330R/340/130 shall return 1.1 (if testing succeeds).
The special value 'none' means that the device does not know of any
RNR version with which it works (because there was no RNR release with
which testing actually succeeded).ro OCTET STRING .1.3.6.1.4.1.81.36.3.1.5 |
ipPolicyControlMaximalPolicyManagmentVersionThe maximal policy management version that this device inter operates
with as verified by actual testing.
For example: The P330R/340/130 shall return 1.1 (if testing succeeds).
P360 for example may return 2.0 because it shall support features that
are only supported in RNR 2.0.
The special value 'none' means that the device does not know of any
RNR version with which it works (because there was no RNR release with
which testing actually succeeded).ro OCTET STRING .1.3.6.1.4.1.81.36.3.1.6 |
ipPolicyDiffServTableThis table is used to configure the policy that is associated with
differntiated services. For each DSCP value the table contain the
operation that should applied to packets that match this DSCP value.
Note that in this version of this mib, allowed policies are restricted
to prioirty levels and access control.
Note: The ietf notion of PHB (per-hop forwarding behaviors) is not
yet supported SEQUENCE OF IpPolicyDiffServEntry .1.3.6.1.4.1.81.36.4 |
ipPolicyDiffServEntryThe information concerning one of the IP policy lists IpPolicyDiffServEntry .1.3.6.1.4.1.81.36.4.1 |
ipPolicyDiffServSlotThe slot-id (AKA module-id / box number) to which diff-serv table relatesro INTEGER .1.3.6.1.4.1.81.36.4.1.1 |
ipPolicyDiffServDSCPThe DSCP value to which this entry relates.ro INTEGER .1.3.6.1.4.1.81.36.4.1.2 |
ipPolicyDiffServOperationThe operation that should be applied to a packet with the specified DSCP
value. Some of the values are Access Control operations and some are
priority operations.rw Enumeration .1.3.6.1.4.1.81.36.4.1.3 |
ipPolicyDiffServNameName of this DSCP entry. This fields is used only for documentation
purposes. Default name is:
DSCP #Nrw DisplayString .1.3.6.1.4.1.81.36.4.1.4 |
ipPolicyDiffServAggIndexIndex of the aggregated group this DSCP entry belongs too.
Management station may use this mib item to classify the DSCP entries
to groups with the same behaviour.
The defval for this mib item is device specific.rwobsolete INTEGER .1.3.6.1.4.1.81.36.4.1.5 |
ipPolicyDiffServApplicabilityPrecedenceThis field indicates how important is it to enforce this entry.
The higher the number the more important it is to enforce this entry.
The value 9999 has a special meaning of Mandatory which means this
entry MUST be enforced.
Device may choose to support only a subset of these values..rw INTEGER .1.3.6.1.4.1.81.36.4.1.6 |
ipPolicyDiffServApplicabilityStatusUsed to monitor if a DSCP entry is currently applicable
or would be applicable (if the table becomes active).
The values returned for this MIB are not affected by the table status
active/inactive)
applicable - This entry is/would be applicable
partiallyApplicable - This entry is/would be applicable for some
packets/sessions but might not be applicable for other
packets/sessions
notApplicable - This entry is NOT/would NOT be applicable
unknown - Status is temporary unknown. This may be because the table
validation is inProgress. Querying this item triggeres table
validation if not already triggered.ro Enumeration .1.3.6.1.4.1.81.36.4.1.7 |
ipPolicyDiffServApplicabilityTypeUsed to monitor the ApplicabilityStatus of the entry in the context of
this table. The values returned for this MIB are not affected by the
table status (active/inactive).
static - The applicabilityStatus of this entry is guaranteed
regardless of the ApplicabilityPrecedence of this entry
or of other entries in the list.
quasiStatic - The applicability status of this entry is
guaranteed if no configuration changes are made,
BUT changes of ApplicabilityPrecedence of this entry or
other entries in this table may change the
applicabilityStatus of this entry.
dynamic - The applicabilityStatus of this entry can change
depending on network conditions (i.e. localization) or
other conditions such as (but not limited to) changes of
ApplicabilityPrecedence of this entry or other entries
in this table.
unknown - Status is temporary unknown. This may be because the
table validation is inProgress. Querying this item triggeres
table validation if not already triggered.
The values returned for this MIB are not affected by the table
status (active/inactive)ro Enumeration .1.3.6.1.4.1.81.36.4.1.8 |
ipPolicyDiffServErrMsgFree text describing the reason why the entry is not Applicable.
When entry is Applicable returns NULL string.
The values returned for this MIB are not affected by the list status
(active/inactive)ro DisplayString .1.3.6.1.4.1.81.36.4.1.9 |
ipPolicyQueryTableThis table is used to query the policy application for different types
of information. The first use is to query about the operation that would
be applied to a given packet.
This table can be used by a managment application to supply the user an
interactive dialugue for looking ahead at the outcomes of the policy
defined SEQUENCE OF IpPolicyQueryEntry .1.3.6.1.4.1.81.36.5 |
ipPolicyQueryEntryEach entry relates to one slot (AKA module / box) in the stack IpPolicyQueryEntry .1.3.6.1.4.1.81.36.5.1 |
ipPolicyQuerySlotThe slot-id (AKA module-id / box number) to which this rule relatesro INTEGER .1.3.6.1.4.1.81.36.5.1.1 |
ipPolicyQueryListIDThe ID of the list used to check the simulated packet.rw INTEGER .1.3.6.1.4.1.81.36.5.1.2 |
ipPolicyQuerySrcAddrThe IP address of the source station in the packetrw IpAddress .1.3.6.1.4.1.81.36.5.1.3 |
ipPolicyQueryDstAddrThe IP address of the destination station in the packetrw IpAddress .1.3.6.1.4.1.81.36.5.1.4 |
ipPolicyQueryProtocolThe IP protocol in the packet. Use 256 to specify IP (i.e. don't care)rw INTEGER .1.3.6.1.4.1.81.36.5.1.5 |
ipPolicyQueryL4SrcPortThe source port of the packet.
This fields is applicable only when ipPolicyQueryProtocol is TCP(6) or UDP(17).
In all other cases its values is not used.rw INTEGER .1.3.6.1.4.1.81.36.5.1.6 |
ipPolicyQueryL4DestPortThe destination port of the packet.
This fields is applicable only when ipPolicyRuleProtocol is TCP(6) or UDP(17).
In all other cases its values is not used.rw INTEGER .1.3.6.1.4.1.81.36.5.1.7 |
ipPolicyQueryEstablishedThe value of the TCP Establish bit in simulated packet.
This fields is applicable only when ipPolicyQueryProtocol is TCP(6)rw Enumeration .1.3.6.1.4.1.81.36.5.1.8 |
ipPolicyQueryDSCPThe DSCP value in the simulated packet.
The value 64 is used to specify DONT CARE. In this case the result
maybe forwardNoChange
If a specifc value is specified the result would be the exact prioirty
associated with the packet after consulting the DSCP table.rw INTEGER .1.3.6.1.4.1.81.36.5.1.9 |
ipPolicyQueryOperationThe operation that would be applied to the simulated packet.
Some of the values are Access Control operations and
some are priority operations.ro Enumeration .1.3.6.1.4.1.81.36.5.1.10 |
ipPolicyQueryRuleIDID of the rule of the list that resulted in the ipPolicyQueryOperation for the query.
A value of 0 means that ipPolicyQueryOperation is a result of the ipPolicyListDefaultOperationro INTEGER .1.3.6.1.4.1.81.36.5.1.11 |
ipPolicyQueryDSCPOperationThe New DSCP value that of the simulated packet
A value of 64 means the DSCP field will not be changed.rw INTEGER .1.3.6.1.4.1.81.36.5.1.12 |
ipPolicyQueryPriorityThe 802.1p priority in the simulated packet.
When the priority is dontCare, the result maybe forwardNoChange.rw Enumeration .1.3.6.1.4.1.81.36.5.1.13 |
ipPolicyDiffServControlTableThis table activates & monitors the Diff Serv application SEQUENCE OF IpPolicyDiffServControlEntry .1.3.6.1.4.1.81.36.6 |
ipPolicyDiffServControlEntryEach entry relates to one slot (AKA module / box) in the stack IpPolicyDiffServControlEntry .1.3.6.1.4.1.81.36.6.1 |
ipPolicyDiffServControlSlotThe slot-id (AKA module-id / box number) to which this control entry
relatesro INTEGER .1.3.6.1.4.1.81.36.6.1.1 |
ipPolicyDiffServControlChecksumChecksum of all the configurable (read/write) DiffServ mib items
including the Diff Serv table.
This field can be used by the management application to discover that
Diff Serv configuration has changed (instead of polling all the
Diff Serv mib items).ro INTEGER .1.3.6.1.4.1.81.36.6.1.2 |
ipPolicyDiffServControlTrustedFieldsSpecify which fields in the incoming packet might be trausted when the
policy decision should be based in the incoming packet itself.
Policy decision depend on the active policy list.
In cases that there is no active policy list or that the result of the
active policy list is Permit, then the outgoing packet prioirty may be
based on the incoming packet instead of an the user specification.
Trusting COS (802.1p) means that the outgoing packet prioirty (802.1p)
should equal the incoming packet prioirty.
Trusting DSCP means that the outgoing packet prioirty (802.1p)
should be taken from ipPolicyDiffServTable using the incoming packet
DSCP value.
Trusting COS + DSCP means that both fields should be used.
The behavior of the device when both COS + DSCP should be trusted
is outside the scope of the current version of the MIB.
(Note: P333R uses the max between incoming COS & DSCP-to-COS mapping)
Some devices might support only a subset of the values.rw Enumeration .1.3.6.1.4.1.81.36.6.1.3 |
ipPolicyDiffServControlValidityStatusValidity status of the DSCP table:
valid - All the entries in the DSCP table can be executed
invalid - One or more of the entries in the DSCP table
can NOT be EXECUTED.ro Enumeration .1.3.6.1.4.1.81.36.6.1.4 |
ipPolicyDiffServControlErrMsgFree text describing the reason why the table is not valid.
When the table is valid returns NULL string.
The values returned for this MIB are not affected by the table
status (active/inactive).ro DisplayString .1.3.6.1.4.1.81.36.6.1.5 |
ipPolicyAccessControlViolationTableThis table contains infomations raerding the last packet (per module)
for which ipPolicyAccessControlViolationTrap was sent. SEQUENCE OF IpPolicyAccessControlViolationEntry .1.3.6.1.4.1.81.36.7 |
ipPolicyAccessControlViolationEntryAn entry conatins the information regarding the last packet for which
ipPolicyAccessControlViolationTrap was sent by the specific module. IpPolicyAccessControlViolationEntry .1.3.6.1.4.1.81.36.7.1 |
ipPolicyAccessControlViolationSlotThe slot-id (AKA module-id / box number) for which the trap was vsentro INTEGER .1.3.6.1.4.1.81.36.7.1.1 |
ipPolicyAccessControlViolationSrcAddrThe IP address of the source station in the packetro IpAddress .1.3.6.1.4.1.81.36.7.1.2 |
ipPolicyAccessControlViolationDstAddrThe IP address of the destination station in the packetro IpAddress .1.3.6.1.4.1.81.36.7.1.3 |
ipPolicyAccessControlViolationProtocolThe IP protocol in the packet. Use 256 to specify IP (i.e. don't care)ro INTEGER .1.3.6.1.4.1.81.36.7.1.4 |
ipPolicyAccessControlViolationL4SrcPortThe source port of the packet.
This fields is applicable only when
ipPolicyAccessControlViolationProtocol is TCP(6) or UDP(17).
In all other cases its values is not used.ro INTEGER .1.3.6.1.4.1.81.36.7.1.5 |
ipPolicyAccessControlViolationL4DstPortThe destination port of the packet.
This fields is applicable only when
ipPolicyAccessControlViolationProtocol is TCP(6) or UDP(17).
In all other cases its values is not used.ro INTEGER .1.3.6.1.4.1.81.36.7.1.6 |
ipPolicyAccessControlViolationEstablishedThis field indicates the value of the established bit in the TCP header
of the packet. This fields is applicable only when \
ipPolicyAccessControlViolationProtocol is TCP(6) or UDP(17).
In all other cases its values is not used.ro Enumeration .1.3.6.1.4.1.81.36.7.1.7 |