No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

ME60 V800R010C10SPC500 Configuration Guide - Virtual Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - Virtual Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Profile-based HQoS

Configuring Profile-based HQoS

Profile-based HQoS can classify traffic flows on multiple interfaces into an SQ for scheduling. It implements uniform scheduling for traffic flows on multiple interfaces by applying a QoS profile to multiple interfaces.

Usage Scenario

To implement uniform scheduling for incoming traffic flows on multiple interfaces, traffic management by user levels is required. Interface-based HQoS can classify traffic flows on one interface into an SQ for scheduling but does not implement uniform scheduling for traffic flows on multiple interfaces. Profile-based HQoS can classify traffic flows on multiple interfaces into an SQ for scheduling. It implements uniform scheduling for traffic flows on multiple interfaces by applying a QoS profile to multiple interfaces. Profile-based HQoS is mainly used on the access devices deployed at the edge of a MAN.

The difference between an MF-classification-based traffic policy and profile-based HQoS is as follows:

The traffic policy based on MF classification identifies the 5-tuple information of packets and performs traffic policing, traffic shaping, traffic statistics, and information modification for packets in a specific direction. In this manner, the traffic in a specific direction and the bandwidth consumed by the traffic are controlled. The configuration of queue scheduling is not involved. Traffic policing in the traffic policy identifies and matches the 5-tuple information of packets to restrict the rate of the incoming traffic and discard the excess traffic. In this manner, the network resources and the interests of carriers can be protected. Traffic policing is unaware of users and service priorities. This method is applicable to the case where traffic in a specific direction is to be restricted.

Profile-based HQoS adjusts the scheduling policy and traffic control of various services in different queues and at different scheduling levels by configuring a QoS profile to control the bandwidth and priorities of packets from different users and interfaces. This method is applicable to the case where differentiated services are required by users.
NOTE:

The GQ scheduling does not take effect in virtual access scenarios. The command can be configured, but it does not take effect.

The differences between the traffic policy and QoS profile are as follows.

Compared Item

Traffic Policy

QoS Profile

Identification of packets

In-depth identification of the 5-tuple information of packets, such as the source/destination MAC address, source/destination IP address, user group number, protocol type, and TCP/UDP port number of the application program.

Identification of users and packet types.

Action taken on the packets

Various actions, including packet filtering, traffic policing, re-marking of packet priorities, re-marking of packet types, setting forwarding actions, and load balancing.

Traffic policing, traffic shaping, and queue scheduling.

Traffic control

There is no cache; the excess packets are discarded; traffic scheduling is implemented in a uniform manner.

Packets in different queues are hierarchically scheduled and then cached. Traffic is scheduled and restricted in a more granular manner.

Applied object

Traffic that is in the same direction and shares the same 5-tuple information.

Traffic that is sent by different users and belongs to different services.

Applied interface

This function is configured on the inbound interface.

This function can be configured on both inbound and outbound interfaces and is mostly configured on the outbound interface.

Association with packet suppression

Traffic policing and packet suppression cannot be configured on an inbound interface at the same time.

Traffic policing and packet suppression can be configured at the same time using the QoS profile.

Pre-configuration Tasks

Before configuring template-based HQoS, complete the following tasks:

  • Configuring the physical parameters and link attributes of interfaces for them to work properly

  • Assigning IP addresses to interfaces

  • Configuring IP routes on the ME device to make devices on the link reachable

Configuration Procedures

Figure 2-22 Configuring profile-based HQoS

(Optional) Specifying a Resource Pool of Queues for an Interface

This section describes how to specify a resource pool of queues for an interface.

Context

Perform the following steps on the ME device:

The SQs that are available for incoming or outgoing traffic on an interface are limited. To resolve the problem that the available SQs are insufficient for an interface, you can specify a resource pool of queues for an interface.

Procedure

  • Specifying a resource pool of queues in mode2.
    1. Run system-view

      The system view is displayed.

    2. Run qos scheduling-mode mode2 slot slot-id

      The scheduling mode is set to mode2 on a board.

      NOTE:

      The queue resource pool configuration takes effect only when the scheduling mode is set to mode2.

    3. Run interface interface-type interface-number

      The interface view is displayed.

    4. Run qos queue-resource pool id { inbound | outbound }

      A resource pool of queues is specified on the interface.

    5. Run commit

      The configuration is committed.

  • Specifying a resource pool of queues in mode3.
    1. Run system-view

      The system view is displayed.

    2. Run qos scheduling-mode mode3 slot slot-id

      The scheduling mode is set to mode3 on a board.

    3. Run commit

      The configuration is committed.

(Optional) Configuring an FQ WRED Object

You can set the high threshold percentage, low threshold percentage, and drop probability for a flow-wred object. In this case, when the queue length exceeds the threshold, the device randomly discards packets by using the WRED mechanism.

Context

Do as follows on the ME device:

NOTE:
  • When no flow-wred objects are set, the system adopts the default tail-drop policy.
  • The high and low limit percentages for red packets can be set to the minimum; those for yellow packets can be greater; those for green packets can be set to the maximum.
  • In the actual configuration, the low limit percentage of WRED is recommended to begin with 50% and be adjusted based on different colors of packets. 100% is recommended for the drop probability.

By configuring a flow-wred object, users can set the high limit percentage, low limit percentage, and drop probability for queues.

  • When the percentage of the actual length of a queue over the length of a FQ is less than the low limit percentage, the system does not drop packets.
  • When the percentage of the actual length of a queue over the length of a FQ is between the low limit percentage and the high limit percentage, the system drops packets through the WRED mechanism. The longer the queue length, the higher the drop probability.
  • When the percentage of the actual length of a queue over the length of a FQ is greater than the high limit percentage, the system drops all subsequent packets.

You can create multiple flow-wred objects for being referenced by FQs as required. You can configure up to 511 flow-wred objects in the system.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-wred flow-wred-name

    The flow-wred is created and the flow-wred view is displayed.

  3. Run color { green | yellow | red } low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage-value

    The high and low limit percentages and the drop probability are set for different colors of packets.

  4. (Optional) Run queue-depth queue-depth-value

    The depth is set for the FQs in the flow-wred objects to decrease the delay.

  5. Run commit

    The configuration is committed.

(Optional) Configuring Scheduling Parameters of an FQ

You can define an FQ profile rather than adopt the default profile to configure WFQ scheduling weights, traffic shaping, the shaping rate, and the way of dropping packets.

Context

Do as follows on the ME device:

You can configure scheduling parameters in one flow queue profile for the eight FQs of a subscriber respectively.

If you do not configure a flow queue, the system uses the default flow queue profile.

  • By default, the system performs PQ scheduling on the FQs with the priorities of EF, CS6, and CS7.
  • The system defaults the FQs with the priorities of BE, AF1, AF2, AF3, and AF4 to WFQ. The scheduling weight proportion is 10:10:10:15:15.
  • By default, the system performs no traffic shaping.
  • The default discarding policy is the tail drop.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-queue flow-queue-name [ priority-mode ]

    The FQ view is displayed.

    If priority-mode is specified in the command, the priority-mode FQ view is displayed.

  3. (Optional) Run priority priority-value { pq | wfq }

    The scheduling mode of priority-mode flow queues on the same scheduler is set to PQ or WFQ in the priority-mode flow queue view.

    NOTE:
    This command can be configured only in the flow queue view in which the flow-queue flow-queue-name priority-mode command has been configured.

  4. (Optional) Run share-shaping [ shap-id ] { af1 | af2 | af3 | af4 | be | cs6 | cs7 ef } * [ pq | wfq weight weight-value | lpq ] shaping-value [ pbs pbs-value ]

    Share shaping for the overall traffic of multiple FQs is configured.

    After queues configured with share shaping are shaped, the queues are scheduled together with other user queues. If no scheduling mode is specified for share shaping, share shaping uses the same scheduling mode as that of sub-schedulers.

    NOTE:
    In the priority-mode FQ view, the command format is share-shaping [ shap-id ] cos-value &<2–8> [ pq [ weight weight-value ] | wfq [ weight weight-value ] ] shaping-value [ pbs pbs-value ].

  5. Run queue queue-name { { pq | wfq weight weight-value | lpq } | { shaping { shaping-value | shaping-percentage shaping-percentage-value } [ pbs pbs-value ] | car { car-value | car-percentage car-percentage-value } [ pbs pbs-value ] } | flow-wred wred-name | low-latency | low-jitter } *

    A queue scheduling policy for a class is set.

  6. Run quit

    Return to the system view.

  7. Run qos flow-queue low-latency enable

    The low-latency function is enabled for flow queues in PQ scheduling mode.

    This command is supported only on the Admin VS.

  8. Run slot slot-id

    The slot view is displayed.

  9. (Optional) Run qos user-queue burst-size bytes bytes-value time time-value

    The minimum default burst size and burst time are configured.

  10. (Optional) Run qos cos { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } burst-size burst-size-value

    The burst size of the eTM chip is set.

  11. Run commit

    The configuration is committed.

(Optional) Configuring a Mapping from an FQ to a CQ

You can define a mapping from an FQ to a CQ rather than adopt the default mapping to set the priority of a type of service in an SQ entering a CQ.

Context

Do as follows on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-mapping mapping-name

    The flow mapping view is displayed.

  3. Run map flow-queue cos-value to port-queue cos-value

    The priority mapping from a flow queue to a CQ is set.

    NOTE:

    You can configure eight mappings from flow queues to port queues in one flow queue mapping profile.

    When no mapping from the flow queue to the CQ is set, the system defaults the one-to-one mapping.

    Users can create multiple flow-mapping profiles for being referenced by SQs as required. You can configure up to 15 flow-mapping profiles in the system.

  4. Run commit

    The configuration is committed.

(Optional) Configuring Scheduling Parameters for a GQ

The shaping rate can be set for a GQ to limit the volume of GQ traffic and prevent GQ traffic burst. In this case, traffic can be evenly sent.

Context

Do as follows on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run user-group-queue group-name

    The specified GQ view is displayed.

  3. Run shaping shaping-value [ pbs pbs-value ] { inbound | outbound }

    The shaping value is set for the GQ.

    NOTE:
    When traffic shaping is not configured for the GQ, the system performs no traffic shaping by default.

  4. (Option) Run mode template

    The Group Queue (GQ) shares QoS resources according to the keyword group in the qos-profile (interface view) command.

    NOTE:

    After a GQ is created, the GQ applies for QoS resources only when the qos-profile (interface view) command is run in the interface view. If the mode template command is configured, GQs consume resources based on the keyword group of the qos-profile (interface view) command in the interface view; if the mode template command is not configured, GQs share the same QoS resources. Even though group is defined differently in multiple qos-profile (interface view) commands in the interface view, GQs share the same QoS resources.

  5. Run commit

    The configuration is committed.

Defining a QoS Profile and Configuring Scheduling Parameters

A QoS profile is the aggregate of QoS scheduling parameters. Configurable scheduling parameters for subscriber queues (SQs) include the committed information rate (CIR), peak information rate (PIR), flow queue profile, and network header length for service profiles.

Context

Perform the following steps on the ME device to be configured with HQoS:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Configure scheduling parameters in a common QoS profile.
    1. Run qos-profile qos-profile-name

      A QoS profile is defined and the QoS profile view is displayed.

    2. You can choose to configure scheduling parameters for SQs or traffic assurance for users as required.

      • Run user-queue cir-value [ cbs cbs-value ] [ [ pir pir-value [ pbs pbs-value ] [ pir-priority high ] ] | [ flow-queue flow-queue-name ] | [ queue-4cos-mapping queue-mapping-name ] | [ flow-mapping mapping-name ] | [ user-group-queue group-name ] ] * [ inbound | outbound ] [ service-template service-template-name [ adjust-on-card ] ]

        Scheduling parameters are configured to implement HQoS for user services.

        The parameter queue-4cos-mapping is supported only on the Admin-VS.

      • Run car { cir cir-value [ pir pir-value ] | cir cir-percentage cir-percentage-value [ pir pir-percentage pir-percentage-value ] } [ cbs cbs-value [ pbs pbs-value ] ] [ green { discard | pass [ service-class class color color ] } | yellow { discard | pass [ service-class class color color ] } | red { discard | pass [ service-class class color color ] } ]* [ inbound | outbound ] [ color-aware ]

        CAR is configured.

      • (Optional) Run weight value [ outbound | inbound ]

        A weight value is set.

      • Run broadcast-suppression cir cir-value [ cbs cbs-value ] [ inbound | outbound ]

        Broadcast suppression is configured.

      • Run multicast-suppression cir cir-value [ cbs cbs-value ] [ inbound | outbound ]

        Multicast suppression is configured.

      • Run unknown-unicast-suppression cir cir-value [ cbs cbs-value ] [ inbound | outbound ]

        Unknown unicast suppression is configured.

      • Run bu-suppression cir cir-value [ cbs cbs-value ] inbound

        broadcast and unknown unicast suppression is configured.

      • Run bum-suppression cir cir-value [ cbs cbs-value ] inbound

        broadcast, unknown unicast, and multicast suppression is configured.

      NOTE:
      • If the qos-profile command has been configured on an interface, you cannot configure the car command, or the suppression command on the interface.

      • A corresponding service profile must have been globally configured before HQoS is configured in a QoS profile.

  3. Run commit

    The configuration is committed.

Applying a QoS Profile to a Virtual Access Interface

Different QoS profiles can be defined and applied to an interface to implement QoS scheduling for access users.

Context

Perform the following steps on the ME device on which HQoS is required:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ .subinterface-number ]

    The virtual access interface or sub-interface view is displayed.

    The virtual access interface is a virtual agent interface established on a master for an AP's external communication interface. For example, GigabitEthernet1025/1/0/1 corresponds to the external communication interface GigabitEthernet 1/0/1 on the AP with the ID being 1025.

  3. Apply a QoS profile to the virtual access interface.

    • Run the qos-profile profile-name { inbound | outbound }[ identifier { none | vid | ce-vid | vid-ce-vid } ] [ group group-name ] command.

  4. Run commit

    The configuration is committed.

(Optional) Configuring a CQ WRED Object

You can set the high threshold percentage, low threshold percentage, and drop probability for a port-wred object. In this case, when the queue length exceeds the threshold, the device randomly discards packets by using the WRED mechanism.

Context

Do as follows on the ME device:

If no WRED objects are created, the default WRED scheduling configuration takes effect.

You can configure a port-WRED object to set the upper and lower limits and discarding probability for queues. When the percentage of the actual length of a queue in the queue length is lower than the lower limit, no packets are dropped. When the percentage of the actual length of a queue in the queue length ranges between the lower and upper limits, WRED randomly drops packets. The longer the queue, the higher the discarding probability. When the percentage of the actual length of a queue in the queue length is higher than the upper limit, all packets are dropped.

You can create multiple port-WRED objects as required. The system supports a maximum of 127 port-WRED objects and a default port-WRED object.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run port-wred port-wred-name

    A port-wred object is created, and the port-wred view is displayed.

  3. Run color { green | yellow | red } low-limit low-limit-value high-limit high-limit-value discard-percentage discard-percentage-value

    The low limit percentage, high limit percentage, and drop probability are set.

  4. (Option) Run queue-depth queue-depth-value

    The depth is set for the CQs in the port-wred objects to decrease the delay.

  5. Run commit

    The configuration is committed.

(Optional) Configuring Scheduling Parameters of a CQ

In upstream HQoS scheduling on an Ethernet interface, CQs adopt the default scheduling setting of the system. To prevent congestion on the backbone network, you need to configure the downstream CQ on the Ethernet interface.

Context

In upstream HQoS scheduling on an Ethernet interface, CQs adopt the default scheduling setting of the system and is not configured by users.

Configuring the downstream CQ on an Ethernet interface is recommended so that the backbone network is not congested.

Do as follows on the downstream interface of the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run port-queue cos-value { { pq | wfq weight weight-value | lpq } | shaping { shaping-value | shaping-percentage shaping-percentage-value } [ pbs pbs-value ] | port-wred wred-name | low-latency } * outbound

    A queue scheduling policy for different CQs is set.

    NOTE:

    You can configure eight CQ scheduling parameters respectively on one interface.

    When no CQ is configured, the system adopts the default CQ profile.

    • By default, the system performs PQ on the flow queues with the priorities of EF, CS6, and CS7.
    • By default, the system performs WFQ on the flow queues with the priorities of BE, AF1, AF2, AF3, and AF4. The scheduling weight proportion is 10:10:10:15:15.
    • By default, the system performs no traffic shaping.
    • The discarding policy defaults to Tail drop.

  4. Run commit

    The configuration is committed.

(Optional) Configuring the Service Traffic of Users in a Domain Not to Participate in the QoS Scheduling for Family Users

You can exclude the traffic of users in a domain from the family-based traffic scheduling. Instead, service-specific bandwidth management is implemented on the traffic of these users.

Context

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run aaa

    The AAA view is displayed.

  3. Run domain domain-name

    A domain is created and the AAA domain view is displayed.

  4. Run session-group-exclude [ car | user-queue ] { inbound | outbound }

    The service traffic of users in a domain is configured not to participate in the QoS scheduling for family users.

    • Using the session-group-exclude car command, you can exclude the service traffic of users in a domain from participating in the CAR operation for family users.

    • Using the session-group-exclude user-queue command, you can exclude the service traffic of users in a domain from participating in SQ scheduling for family users.

  5. Run commit

    The configuration is committed.

(Optional) Configuring a Channel Profile for User Queues and Applying It to a Board

This section describes how to configure a channel profile to optimize bandwidth allocation.

Context

Perform the following steps on the ME device:

This configuration is supported only on the Admin VS.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run qos channel-profile channel-profile name

    A channel profile is created, and the channel profile view is displayed.

  3. Run channel channel-id bandwidth bandwidth-value quantity quantity-value

    The bandwidth granularity and quantity are configured for a specific channel.

  4. Run quit

    Return to the system view.

  5. Run slot slot-id

    The slot view is displayed.

  6. (Optional) Run qos pir-precision user-queue precision

    The allowed deviation between the actual user queue bandwidth and the configured one is set.

  7. Run qos channel-profile channel-profile name

    The channel profile is applied to the board.

  8. Run commit

    The configuration is committed.

  9. Run reset slot slot-id

    The board is restarted.

(Optional) Configuring Dynamic Update of a QoS Profile

When the QoS profile applied by online users is changed, the previously configured QoS profile for the domain to which the online users belong does not take effect.

Context

NOTE:

This configuration task is supported only on the Admin-VS.

To enable an online user to modify the in-use QoS profile, you need to configure dynamic update of the QoS profile. After this function is configured, the QoS profile being used by the user is changed to the profile defined in the update qos-profile command and the original QoS profile applied to the user domain no longer takes effect.

Dynamic update of the QoS profile takes effect for only service traffic of the user. The QoS profile for family users cannot be updated. That is only the QoS profile applied in domain can be updated but the QoS profile applied in interface cannot be updated.

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run aaa

    The AAA view is displayed.

  3. Run update qos-profile user-id user-id profile qos-profile-name { inbound | outbound }

    Dynamic update of the QoS profile is configured.

  4. Run commit

    The configuration is committed.

(Optional) Configuring the Shared Threshold of Buffer Resources

This section describes how to configure the shared threshold of buffer resources.

Context

Perform the following steps on the ME device:

Queues share buffer resources. If the buffer resources are exhausted, packet loss occurs even if the queues are not congested. To prevent buffer resources from being exhausted by some queues, control flow-wred scheduling. If the flow-wred value is set to a small value, packet loss occurs in traffic bursts. To resolve this problem, run the qos global-buffer command to set the shared threshold of buffer resources. Before the shared buffer resources are exhausted, flow-wred configurations do not take effect to prevent packet loss.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run slot slot-id

    The slot view is displayed.

  3. Run qos global-buffer { share-threshold share-value | { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } share } { inbound | outbound }

    Flow-wred scheduling is controlled on a board. Before the buffer resources shared by queues are exhausted, the flow-wred configurations for specific queues do not take effect.

  4. Run commit

    The configuration is committed.

(Optional)Configuring Grade-based Bandwidth Adjustment

You can configure grade-based bandwidth adjustment to optimize SQ resource usage.

Context

The allowed sum of CIRs or PIRs of SQs on a device cannot be infinite. Therefore, if the sum of CIRs or PIRs of SQs has reached the maximum processing performance of the device, the user that is applying for SQ resources is prone to request denies. To resolve such problems, you can configure grade-based bandwidth adjustment to supplement bandwidth or reclaim bandwidth in real time so that SQ resource usage is optimized and bandwidth is guaranteed.

Perform the following steps on the ME device:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run slot slot-id

    The slot view is displayed.

  3. Run qos bandwidth-adjustment { degrade-cycle cycle-num | upgrade-cycle cycle-num | monitor-number monitor-number | adjust-number adjust-number | disable-percent disable-value enable-percent enable-value | upgrade-threshold upgrade-value degrade-threshold degrade-value [ inbound | outbound ] }

    Parameters for grade-based bandwidth adjustment are configured.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of Profile-based HQoS

After profile-based HQoS is configured on an interface, you can view information about queues and packet statistics on the interface.

Procedure

  • Run the display flow-mapping configuration [ verbose [ mapping-name ] ] command to check the configurations of a flow queue mapping object and the referential relationships of the object.
  • Run the display flow-queue configuration [ verbose [ flow-queue-name ] ] command to check the configuration of a flow queue template.
  • Run the display flow-wred configuration [ verbose [ flow-wred-name ] ] command to check the configurations of a flow queue WRED object.
  • Run the display user-group-queue configuration [ verbose [ group-name ] ] command to check the configurations of a user group queue and its referential relationships.
  • Run the display user-group-queue statistics user-group-name statistics [ group group-name ] [ slot slot-id ] { inbound | outbound } command to check statistics on a GQ.
  • Run the display port-wred configuration [ verbose [ port-wred-name ] ] command to check the configurations of a class queue WRED object.
  • Run the display port-queue configuration interface interface-type interface-number outbound command to check the configurations of a class queue.
  • Run the display qos-profile configuration [ profile-name ] command to check the configurations of a QoS profile.
  • Run the display qos-profile application profile-name command to check the applications of a QoS profile.
  • Run the display qos-profile statistics interface interface-type interface-number [ [ vlan vlan-id ] | [ pe-vid pe-vid ce-vid ce-vid ] ] { inbound | outbound } command to check the statistics about a QoS profile.
  • Run the monitor qos-profile statistics interface { interface-name | interface-type interface-number } [ vlan vlan-id | pe-vid pe-vid ce-vid ce-vid | vid vid-id | ce-vid ce-vid | vid vid-id ce-vid ce-vid ] { inbound | outbound } [ interval seconds [ repeat repeat ] command to monitor QoS profile statistics.
  • Run the display port-queue statistics [ slot slot-id | interface interface-type interface-number ] [ cos-value ] outbound command to check the statistics of a CQ.
  • Run the display user-group-queue statistics interface interface-type interface-number [ vlan vlan-id |pe-vid pe-vid ce-vid ce-vid ] { inbound | outbound } command to display user group queue statistics.
  • Run the display qos resource user-group-queue slot slot-id { inbound | outbound }} command to display the usage of user group queues on an LPU.
  • Run the display qos resource user-queue slot slot-id { inbound | outbound } command to display the usage of user queues on an LPU.
  • Run the display qos resource sub-port-queue slot slot-id { inbound | outbound } command to check the usage of sub-interface queues.
  • Run the display sub-port-queue configuration [ verbose [ sub-port-queue-name ] ] command to check information about sub-interface queues.
  • Run the display sub-port-queue statistics interface interface-type interface-number outbound command to check statistics about sub-interface queues.
  • Run the display qos scheduling-mode slot slot-id to check the scheduling mode of a board.
  • Run the display queue-4cos-mapping configuration [ verbose ] command to check configurations of 4-CoS flow queue profiles, including the number and names of used profiles.

    This command is supported only on the Admin VS.

  • Run the display qos bandwidth-adjustment information [ verbose ] command to check information about the resource usage and bandwidth adjustment on a specific board.

    This command is supported only on the Admin VS.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059451

Views: 3779

Downloads: 18

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next