AT-QOS-MIB: View SNMP OID List / Download MIB

This MIB file contains definitions of managed objects for the handling QoS on Allied Telesis switches. There are a number of tables designed to be generic to all ATR switches supporting QoS in silicon, and well as tables for specific AT switches or switch familes.

Generic port configuration for QoS, indexed by port index.

A single switch port entry for QoS.

Port index of the port entry. This index is the same port number used in CLI commands, and the same index as appears in other MIB tables related to switch ports.

Policy index of the policy for this port. Policy index numbers for CLI commands start at 0, while SNMP indexes must start at 1. This means that the policy index in this MIB variable is 1 more than the index for the same policy as entered for CLI commands.

QoS policy configuration, indexed by policy index.

A policy entry containing configuration information for a single policy.

The index of this policy entry. Policy index numbers for CLI commands start at 0, while SNMP indexes must start at 1. This means that the policy index in this MIB variable is 1 more than the index for the same policy as entered for CLI commands.

An optional description for the policy, as entered via the CLI.

Specifies whether traffic that exceeds the bandwidth for the default traffic class be dropped or not. The bandwidth limit is the combined total of the variables qosSwitchPolicyDefaultTCMaxBandwidth and qosSwitchPolicyDefaultTCMaxBurstSize. A value of yes(1) indicates that traffic exceeding the bandwidth limit is dropped immediately. A value of no(0) indicates that the excess traffic is marked as bandwidth class 3 and is therefore eligible for dropping by the RED curve settings. Enumeration: 'yes': 1, 'no': 0.

Specifies whether the traffic metering stage acknowledges any bandwidth class assigned to flows processed by the default traffic class. If set to yes(1), previously assigned bandwidth classes will be ignored will be ignored and the bandwidth class of the traffic will be set according to the meter conformance level of the flow. Enumeration: 'yes': 1, 'no': 0.

When the qosSwitchPolicyDefaultTCPremarking variable is set to usemarkvalue(1), this variable specifies the index into the DSCP MAP table to use for remarking. A value in the range 0 to 63 indicates the DSCP to use, the value 256 indicates that no DSCP value has been defined for the default traffic class for this policy.

Specifies the maximum bandwidth available to the default traffic class. Traffic under this bandwidth will be designated as bandwidth class 2. The value 2147483647 indicates that there is no limit on the maximum bandwidth for the default traffic class for this policy.

Specifies the maximum bandwidth above the bandwidth specified by qosSwitchPolicyDefaultTCMaxBandwidth before traffic is marked as bandwidth class 3.

Specifies the minimum bandwidth reserved for the default traffic class. Traffic under this bandwidth will be marked as bandwidth class 1. The value 2147483647 indicates that there is no limit on the minimum bandwidth for the default traffic class for this policy.

Specifies the maximum amount of data above the bandwidth specified in the variable qosSwitchPolicyDefaultTCMinBandwidth before traffic is marked as bandwidth class 2.

Specifies the QoS action to take on traffic in the default traffic class before metering actions are taken. If none(0) is specified, the traffic is passed to the metering stage. If usemarkvalue(1) is specified, the QoS settings are taken from the variable qosSwitchPolicyDefaultTCMarkValue used as an index into the DCSP MAP table. If usedscp(2) is specified, the DSCP value in the data frames is used as an index into the DSCP MAP table. Enumeration: 'usemarkvalue': 1, 'none': 0, 'usedscp': 2.

Specifies the action to take after the metering stage for traffic in the default traffic class. The metering stage assigns a temporary value of bandwidth class to the flow which is used to determine its per-hop behaviour. If this variable is set to bwclass(2) or bwclass-priority(4), the temporary bandwidth class becomes the new bandwidth class for the flow. If priority(3) or bwclass-priority(4) is specified, the currently assigned queue for frames in this traffic class is used in conjunction with the temporary bandwidth class to determine the new value of the VLAN Tag User Priority field. If usedscpmap(1) is specified, the temporary value is used (in conjunction with the DSCP of the frame) as an index into the DSCP MAP table, which then assigns the actual, new values for bandwidth class, DSCP, Egress Queue and VLAN Tag User Priority. A value of none(0) for this variable means that no remarking of the packet is done after the metering stage. Enumeration: 'bwclass': 2, 'priority': 3, 'none': 0, 'usedscpmap': 1, 'bwclass-priority': 4.

Traffic class configuration, indexed by traffic class index.

A traffic class entry containing configuration information for a single traffic class.

The index of this traffic class entry. Traffic class index numbers for CLI commands start at 0, while SNMP indexes must start at 1. This means that the traffic class index in this MIB variable is 1 more than the index for the same traffic class as entered for CLI commands.

Policy index of the policy to which this traffic class belongs. Policy index numbers for CLI commands start at 0, while SNMP indexes must start at 1. This means that the policy index in this MIB variable is 1 more than the index for the same policy as entered for CLI commands. A value of 0 for this variable means that the traffic class has not been added to a policy yet.

An optional description for this traffic class.

Specifies whether traffic that exceeds the bandwidth for this traffic class be dropped or not. The bandwidth limit is the combined total of the variables qosSwitchTrafficClassMaxBandwidth and qosSwitchTrafficClassMaxBurstSize A value of yes(1) indicates that traffic exceeding the bandwidth limit is dropped immediately. A value of no(0) indicates that the excess traffic is marked as bandwidth class 3 and is therefore eligible for dropping by the RED curve settings. Enumeration: 'yes': 1, 'no': 0.

Specifies whether the traffic metering stage acknowledges any bandwidth class assigned to flows processed by this traffic class. If set to yes(1), previously assigned bandwidth classes will be ignored will be ignored and the bandwidth class of the traffic will be set according to the meter conformance level of the flow. Enumeration: 'yes': 1, 'no': 0.

When the qosSwitchTrafficClassPremarking variable is set to usemarkvalue(1), this variable specifies the index into the DSCP MAP table to use for remarking. A value in the range 0 to 63 indicates the DSCP to use, the value 256 indicates that no DSCP value has been defined for this traffic class.

Specifies the maximum bandwidth available to this traffic class. Traffic under this bandwidth will be designated as bandwidth class 2. The value 2147483647 indicates that there is no limit on the maximum bandwidth for this traffic class.

Specifies the maximum bandwidth above the bandwidth specified by qosSwitchTrafficClassMaxBandwidth before traffic is marked as bandwidth class 3.

Specifies the minimum bandwidth reserved for this traffic class. Traffic under this bandwidth will be marked as bandwidth class 1. The value 2147483647 indicates that there is no limit on the minimum bandwidth for this traffic class.

Specifies the maximum amount of data above the bandwidth specified in the variable qosSwitchTrafficClassMinBandwidth before traffic is marked as bandwidth class 2.

Specifies the QoS action to take on traffic in this traffic class before metering actions are taken. If none(0) is specified, the traffic is passed to the metering stage. If usemarkvalue(1) is specified, the QoS settings are taken from the variable qosSwitchTrafficClassMarkValue used as an index into the DCSP MAP table. If usedscp(2) is specified, the DSCP value in the data frames is used as an index into the DSCP MAP table. Enumeration: 'usemarkvalue': 1, 'none': 0, 'usedscp': 2.

Specifies the action to take after the metering stage for traffic in this traffic class. The metering stage assigns a temporary value of bandwidth class to the flow which is used to determine its per-hop behaviour. If this variable is set to bwclass(2) or bwclass-priority(3), the temporary bandwidth class becomes the new bandwidth class for the flow. If priority(3) or bwclass-priority(4) is specified, the currently assigned queue for frames in this traffic class is used in conjunction with the temporary bandwidth class to determine the new value of the VLAN Tag User Priority field. If usedscpmap(1) is specified, the temporary value is used (in conjunction with the DSCP of the frame) as an index into the DSCP MAP table, which then assigns the actual, new values for bandwidth class, DSCP, Egress Queue and VLAN Tag User Priority. A value of none(0) for this variable means that no remarking of the packet is done after the metering stage. Enumeration: 'bwclass': 2, 'priority': 3, 'none': 0, 'usedscpmap': 1, 'bwclass-priority': 4.

Port configuration, indexed by port index.

A single switch port entry.

The total number of bytes classified by the default traffic class on this port.

The number of bytes classified by the default traffic class on this port conforming to bandwidth class 1.

The number of bytes classified by the default traffic class on this port conforming to bandwidth class 2.

The number of bytes classified by the default traffic class on this port conforming to bandwidth class 3.

The number of bytes dropped by the default traffic class on this port.

The total number of packets currently queued for transmission on this port.

The number of packets currently queued for transmission on this port in queue 0. The numbering of queues indicates the priority of handling the traffic in that queue, with the higher queue number getting higher priority. The priority values in packets are mapped to queues via a priority to queue mapping. The default priority to queue mapping is as follows: Priority Queue value number 7 7 6 6 5 5 4 4 3 3 2 1 1 0 0 2 This mapping allows the default priority value of 0 to map to a queue which is not the lowest priority queue, allowing traffic classes to be assigned a lower priority queue than the default.

The number of packets currently queued for transmission on this port in queue 1. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 2. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 3. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 4. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 5. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 6. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

The number of packets currently queued for transmission on this port in queue 7. See the description for qosSwitch8948PortQueue0Length to understand the meaning of queue numbers.

Traffic class counters indexed by port, policy and traffic class.

A traffic class counters entry containing QOS counters for a particular port, policy and traffic class.

The index of the port for this entry in the traffic class counter table. This index is the same as the port index in the port table and is the same as the port number of the port in user commands.

The index of the policy for this entry in the traffic class counter table. Each port can only have one policy assigned at a time. Policy index numbers for CLI commands start at 0, while SNMP indexes must start at 1. This means that the policy index in this MIB variable is 1 more than the index for the same policy as entered for CLI commands.

The index of the traffic class for this entry in the traffic class counter table. The index is one of the indices defined for traffic classes for this port and policy. Traffic class indices for CLI commands start at 0, while SNMP indices must start at 1. This means that the traffic class index in this MIB variable is 1 more than the index for the same traffic class as entered for CLI commands.

The total number of bytes classified by this traffic class for this policy on this port.

The number of bytes classified by this traffic class for this policy on this port conforming to bandwidth class 1.

The number of bytes classified by this traffic class for this policy on this port conforming to bandwidth class 2.

The number of bytes classified by this traffic class for this policy on this port conforming to bandwidth class 3.

The number of bytes dropped by this traffic class for this policy on this port.