NTN-QOS-POLICY-EXT-PIB: View SNMP OID List / Download MIB

The Nortel Network's PIB module containing extensions to the base PIB modules (Framework, IP QoS, 802 QoS) produced by the IETF.

Supports the assignment of 802.1D user priority values to a queue for each interface with a specific role combination. There will be 8 instances of this class for each supported role combination.

An instance of the ntnQosIfPriAssignment class.

An index that is used to uniquely identify the instance of the ntnQosIfPriAssignment class.

The role combination with which an interface must be configured to support the Pri-to-queue assignment described by this instance. The specified role combination must be defined in the qosInterfaceType table prior to being referenced by this entry. Otherwise a 'priAssociationUnknown(3)' error code will be returned.

The 802.1D user priority to which this class instance applies.

The specific queue, within the queue set that is associated with the interface set identified by the ntnQosIfPriAssignmentRoles tag, on which traffic with the specified user priority, dictated by the ntnQosIfPriAssignmentPri value, is placed. Failure to specify an appropriate queue results in a 'priAssociationConflict(4)' error indication being returned.

The storage type for this conceptual row. Conceptual rows having the value permanent(4) need not allow write-access to any columnar objects in the row. This object may not be modified if the associated ntnQosIfPriAssignmentStatus object is equal to active(1).

The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Row creation using only default values is supported.

Supports augmenting the information regarding the interface roles and queue set assignments.

An instance of the ntnQosInterfaceTypeExt class.

A value describing the overall classification of traffic received on interfaces with the given role combination. Traffic received on core (i.e., trusted) interfaces may be processed differently and be subject to different restrictions that traffic received on access (i.e., non-trusted) interfaces. The treatment of traffic based on interface class is implementation dependent. Enumeration: 'access': 2, 'core': 1.

Supports augmenting the information regarding the mapping of DSCP values to 802.1p user priority and drop precedence values.

An instance of the ntnQosIfDscpMappingExt class.

The drop precedence value to use for traffic with the associated DSCP value.

Contains the current set of configured general action extensions. The actions are associated with all types ACLs during operation.

General action extensions. Each entry specifies an instance of the ntnQosActionExt class which describes (potentially) several distinct action attributes. Each action is taken individually regarding the data in question. Several actions can be taken for a single frame. An instance of this class can not be deleted while the correspond qosActionTable instance exists.

This action attribute, when specified, will cause the packet being evaluated to be associated with the specified flow identifier. Flow identifiers may be used to facilitate traffic shaping and other implementation specific operations at the egress interface. Setting this attribute to -1 indicates that flow identification is not in use at the present time.

This action attribute, when specified, will cause the packet being evaluated to be sent to the CPU for further processing. Extreme care should be taken when setting this object to 'true(1)' since this action may adversely affect resource availability in the system impacting overall system operation. A value of 'false(2)' indicates that this action will not be initiated.

This action attribute, when specified, will cause the packet being evaluated to be sent to a predefined egress port for transmission in addition to the normal processing associated with the packet. Specification of the egress port or ports that will serve as the destination for mirrored data is beyond the scope of this document. Furthermore, note that data mirroring can potentially consume substantial resources at the egress. Oversubscription issues should be considered prior to specifying this action. Also note that the mirroring direction attribute in this same ntnQosActionExt entry determines the data that is mirrored. The packet that was 'received' by the device will be mirrored (i.e., packet modifications that may occur during processing will not appear in the mirrored data) when the mirroring direction attribute has the value 'ingress(1)'. The packet that is to be 'transmitted' by the device will be mirrored (i.e., packet modifications that may occur during processing will appear in the mirrored data) when the mirroring direction attribute has the value 'egress(2)'. A value of 'false(2)' indicates that this action will not be initiated.

This action attribute, when specified, will cause the packet being evaluated to be associated with the specified relative drop precedence. The relative drop precedence may be used to determine traffic precedence relative to other traffic being processed by the device and other implementation specific operations at the egress interface. A low value for drop precedence equates to the traffic receiving a higher priority in terms of processing. In other words, traffic with a drop precedence of 1 is treated with the highest processing priority while traffic with a drop precedence of 8 receives the lowest processing priority. Specifying a value equal to useDefault(9) means that the value for this attribute will be assigned based on default information maintained in the system. The value specified in the 'UpdateDSCP' attribute will be used to determine the default drop precedence. Note that specifying useDefault(9) means that assignment of a value for this attribute is implementation dependent. Specifying a value equal to ignore(10) means that no action will be taken related to this attribute. Note that the results of classification where actions specifying ignore(10) are applied are implementation dependent. Specifying a value equal to useEgressMap(11) means that the value for this attribute will be assigned based on DSCP-to-drop precedence egress map information maintained in the system. The DSCP value in received traffic will be used to determine the drop precedence. Note that specifying useEgressMap(11) means that assignment of a value for this attribute is implementation dependent. Enumeration: 'dropPrec8': 8, 'dropPrec6': 6, 'dropPrec7': 7, 'dropPrec4': 4, 'dropPrec5': 5, 'dropPrec2': 2, 'dropPrec3': 3, 'dropPrec1': 1, 'ignore': 10, 'useEgressMap': 11, 'useDefault': 9.

This action attribute, when specified, will cause the value contained in the user priority field of the 802.1Q frame to be updated based on the value of this object. No action is taken if the frame is untagged. Specifying a value equal to useDefault(9) means that the value for this attribute will be assigned based on default information maintained in the system. The value specified in the 'UpdateDSCP' attribute will be used to determine the default drop precedence. Note that specifying useDefault(9) means that assignment of a value for this attribute is implementation dependent. Specifying a value equal to ignore(10) means that no action will be taken related to this attribute. Note that the results of classification where actions specifying ignore(10) are applied are implementation dependent. Specifying a value equal to useEgressMap(11) means that the value for this attribute will be assigned based on DSCP-to-drop precedence egress map information maintained in the system. The DSCP value in received traffic will be used to determine the drop precedence. Note that specifying useEgressMap(11) means that assignment of a value for this attribute is implementation dependent. Enumeration: 'ignore': 10, 'useDefault': 9, 'useEgressMap': 11, 'markAsPriority2': 3, 'markAsPriority3': 4, 'markAsPriority0': 1, 'markAsPriority1': 2, 'markAsPriority6': 7, 'markAsPriority7': 8, 'markAsPriority4': 5, 'markAsPriority5': 6.

This action attribute, when specified, will determine where a snapshot of a packet being mirrored will be taken for mirroring purposes. The packet that was 'received' by the device will be mirrored (i.e., packet modifications that may occur during processing will not appear in the mirrored data) when the direction attribute has the value 'ingress(1)'. The packet that is to be 'transmitted' by the device will be mirrored (i.e., packet modifications that may occur during processing will appear in the mirrored data) when the direction attribute has the value 'egress(2)'. Note that the value of this attribute is only considered if the ntnQosActionExtMirrorFrame attribute is 'true'. Enumeration: 'ingress': 1, 'egress': 2.

Contains the current set of configured 802 filter extensions.

Global (802) filter extensions. Each entry specifies an instance of the ntnQos802FilterExt class which describes (potentially) several distinct filter attributes. An instance of this class can not be deleted while the correspond qos802AceTable instance exists.

The value that the DSCP in the packet can have and match this filter. A value of -1 indicates that a specific DSCP value has not been defined and thus all DSCP values are considered a match.

The IP protocol to match against the packet's protocol. Valid only when applied against IP traffic. A value of zero means match all.

The minimum value that the packet's layer 4 destination port number can have and match this filter. Valid only when applied against IP traffic flows. The value of this attribute must be less-than-or-equal-to the value of the corresponding ntnQos802FilterDstL4PortMax attribute.

The maximum value that the packet's layer 4 destination port number can have and match this filter. Valid only when applied against IP traffic flows. The value of this attribute must be greater-than-or-equal-to the value of the corresponding ntnQos802FilterDstL4PortMin attribute.

The minimum value that the packet's layer 4 source port number can have and match this filter. Valid only when applied against IP traffic flows. The value of this attribute must be less-than-or-equal-to the value of the corresponding ntnQos802FilterSrcL4PortMax attribute.

The maximum value that the packet's layer 4 source port number can have and match this filter. Valid only when applied against IP traffic flows. The value of this attribute must be greater-than-or-equal-to the value of the corresponding ntnQos802FilterSrcL4PortMin attribute.

This attribute is used to specify a set of VLAN IDs against which the traffic being classified is compared. Packets that contain a VLAN ID equal to one of the VLAN IDs in this set match this component of an 802 filter. The format of this octet string is a series of two-byte (16 bit) values with each octet tuple identifying a single VLAN ID in the set. Therefore, the length of the octet string value of this object is always either zero or an even number of octets (e.g., 2, 4, 6, 20). As with most sets, ordering within the set (octet string) is unimportant. For example, a set specifying three VLAN IDs (8, 35 and 4012) might be specified as follows: Octets: 1 | 2 | 3 | 4 | 5 | 6 ------------------------------------------------ Values: 0x00 | 0x23 | 0x00 | 0x08 | 0x0F | 0xAC ------------------------------------------------ VLAN ID: 35 | 8 | 4012 The supported maximum length of this attribute depends on the maximum number of VLANs that may be included in a set for filtering purposes. This length is thus implementation dependent. Note that this attribute and the qos802AceVlanId attribute are mutually exclusive. The value of the qos802AceVlanId component of the augmented filter entry must be set to 'ignore' (i.e., -1) if the length of this set is non-zero. Otherwise entry creation will fail.

Describes the requirements for conformance to the Nortel Networks QoS Policy Extension PIB.

Objects from the ntnQosIfPriAssignmentTable.

Objects from the ntnQosInterfaceTypeExtTable.

Objects from the ntnQosIfDscpMappingExtTable.

Objects from the ntnQosActionExtTable.

Objects from the ntnQos802FilterExtTable.