POLICY-MIB: View SNMP OID List / Download MIB

This 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

The information concerning one of the IP policy lists

The slot-id (AKA module-id / box number) to which this list relates

The 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).

Name of this list. Default name is: list #N

Validity 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. Enumeration: 'partiallyValid': 2, 'valid': 1, 'validationInProgress': 4, 'invalid': 3.

Checksum 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).

Used 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 list

The 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. Enumeration: 'deny': 10, 'denyAndNotify': 11, 'forwardPriority1': 2, 'forwardPriority0': 1, 'forwardPriority3': 4, 'forwardPriority2': 3, 'forwardPriority5': 6, 'forwardPriority4': 5, 'forwardPriority7': 8, 'forwardPriority6': 7, 'forward': 9, 'layer2Switching': 12.

A 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.

Counts 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.

The entity that configured this list

Free 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).

This table is used to add/delete/modify/monitor individual policy rules in a policy list.

Controls all the conditional fields and its parameters for a policy rule.

The slot-id (AKA module-id / box number) to which this rule relates

The ID of the list this rule is part of. Lists 150-199 are for RNR use.

Number 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.

The IP address of the source station. A value of 255.255.255.255 in ipPolicyRuleSrcAddrWild indicates this is a DON'T CARE field.

This 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.*.254

The IP address of the destination station. A value of 255.255.255.255 in ipPolicyRuleDstAddrWild indicates this is a DON'T CARE field.

This 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.*.254

The IP protocol to which this rule relates. Use 256 to specify IP (i.e. don't care)

The 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.

The 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.

The 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.

The 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.

This field indicates the value of the established bit in the TCP header. If protocol is not TCP this values is not used. Enumeration: 'yes': 1, 'dontCare': 2.

The 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. Enumeration: 'deny': 10, 'denyAndNotify': 11, 'forwardPriority1': 2, 'forwardPriority0': 1, 'forwardPriority3': 4, 'forwardPriority2': 3, 'forwardPriority5': 6, 'forwardPriority4': 5, 'forwardPriority7': 8, 'forwardPriority6': 7, 'forward': 9, 'layer2Switching': 12.

This 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.

Used 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. Enumeration: 'notApplicable': 3, 'applicable': 1, 'partiallyApplicable': 2, 'unknown': 4.

Used 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) Enumeration: 'dynamic': 3, 'quasiStatic': 2, 'static': 1, 'unknown': 4.

Free 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)

Used 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 rule

The New DSCP value that should be applied to packets that meatch this rule. A value of 64 means no change.

This table activates & monitors the policy application

Each entry relates to one slot (AKA module / box) in the stack

The slot-id (AKA module-id / box number) to which this control entry relates

The 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 active

Specify 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. Enumeration: 'remote': 2, 'local': 1.

Checksum 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.

The 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).

The 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).

This 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

The information concerning one of the IP policy lists

The slot-id (AKA module-id / box number) to which diff-serv table relates

The DSCP value to which this entry relates.

The 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. Enumeration: 'deny': 10, 'denyAndNotify': 11, 'forwardNoChange': 9, 'forwardPriority1': 2, 'forwardPriority0': 1, 'forwardPriority3': 4, 'forwardPriority2': 3, 'forwardPriority5': 6, 'forwardPriority4': 5, 'forwardPriority7': 8, 'forwardPriority6': 7.

Name of this DSCP entry. This fields is used only for documentation purposes. Default name is: DSCP #N

Index 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.

This 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..

Used 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. Enumeration: 'notApplicable': 3, 'applicable': 1, 'partiallyApplicable': 2, 'unknown': 4.

Used 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) Enumeration: 'dynamic': 3, 'quasiStatic': 2, 'static': 1, 'unknown': 4.

Free 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)

This 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

Each entry relates to one slot (AKA module / box) in the stack

The slot-id (AKA module-id / box number) to which this rule relates

The ID of the list used to check the simulated packet.

The IP address of the source station in the packet

The IP address of the destination station in the packet

The IP protocol in the packet. Use 256 to specify IP (i.e. don't care)

The 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.

The 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.

The value of the TCP Establish bit in simulated packet. This fields is applicable only when ipPolicyQueryProtocol is TCP(6) Enumeration: 'yes': 1, 'no': 2.

The 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.

The operation that would be applied to the simulated packet. Some of the values are Access Control operations and some are priority operations. Enumeration: 'deny': 10, 'error': 99, 'denyAndNotify': 11, 'forwardNoChange': 9, 'forwardPriority1': 2, 'forwardPriority0': 1, 'forwardPriority3': 4, 'forwardPriority2': 3, 'forwardPriority5': 6, 'forwardPriority4': 5, 'forwardPriority7': 8, 'forwardPriority6': 7, 'layer2Switching': 12, 'notEnoughInfo': 13.

ID 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 ipPolicyListDefaultOperation

The New DSCP value that of the simulated packet A value of 64 means the DSCP field will not be changed.

The 802.1p priority in the simulated packet. When the priority is dontCare, the result maybe forwardNoChange. Enumeration: 'forwardPriority1': 2, 'forwardPriority0': 1, 'forwardPriority3': 4, 'forwardPriority2': 3, 'forwardPriority5': 6, 'forwardPriority4': 5, 'forwardPriority7': 8, 'forwardPriority6': 7, 'dontCare': 99.

This table activates & monitors the Diff Serv application

Each entry relates to one slot (AKA module / box) in the stack

The slot-id (AKA module-id / box number) to which this control entry relates

Checksum 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).

Specify 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. Enumeration: 'cos-dscp': 3, 'cos': 1, 'untrust': 4, 'dscp': 2.

Validity 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. Enumeration: 'valid': 1, 'invalid': 2.

Free 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).

This table contains infomations raerding the last packet (per module) for which ipPolicyAccessControlViolationTrap was sent.

An entry conatins the information regarding the last packet for which ipPolicyAccessControlViolationTrap was sent by the specific module.

The slot-id (AKA module-id / box number) for which the trap was vsent

The IP address of the source station in the packet

The IP address of the destination station in the packet

The IP protocol in the packet. Use 256 to specify IP (i.e. don't care)

The 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.

The 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.

This 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. Enumeration: 'yes': 1, 'dontCare': 2, 'no': 3.