The no form of the command removes the explicit description string from the named pool policy.
The no form of the command removes a specific named pool policy from the system. If the named pool policy is currently associated with an ingress or egress MDA or port, the command will fail. If the named pool policy does not exist, the command has no effect and does not return an error.
The no form of the command removes an explicit description string from the named pool policy.
The no form of the command resets all values to the default value.
The no form of the command removes a specific named pool from the policy. If an instance of the named pool is currently associated with a created queue, the queue will be moved to the appropriate default pool. Once the pool is deleted, the pool is removed from both the policy and any instance of the pool on an MDA or port is removed. The pool buffers are freed and may be available other named pools.
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
The no form of the command returns the pools network allocation weight to the default value of 50.
The no access-allocation-weight command is used to return the pools access allocation weight to the default value of 50.
The no form of the command restores the default slope policy to the named pool.
resv-cbs percentage-of-pool-size amber-alarm-action step
percent max
[1..100]
The no form of the command restores the default reserved CBS size of 30%.
[no
] sap-ingress
policy-id
Policies in effect are templates that can be applied to multiple services as long as the scope of the policy is template. Queues defined in the policy are not instantiated until a policy is applied to a service SAP.
It is possible that a SAP ingress policy will include the dscp map command, the
dot1p map command and an IP or MAC match criteria. When multiple matches occur for the traffic, the order of precedence will be used to arrive at the final action. The order of precedence is as follows:
The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other policy is explicitly specified. The system SAP ingress policy can be modified but not deleted. The
no sap-ingress command restores the factory default settings when used on
policy-id 1. The default SAP ingress policy defines one queue associated with the best effort (
be) forwarding class, with CIR of zero and PIR of line rate.
The no sap-ingress policy-id command deletes the SAP ingress policy. A policy cannot be deleted until it is removed from all services where it is applied. The system default sap-ingress policy is a special case; the
no command restores the factory defaults to policy-id 1.
The no sap-ingress policy-id bw-reserved command removes the bandwidth reservation attribute from the sap-ingress policy.
The policy-id uniquely identifies the policy.
queue queue-id [multipoint
] [queue-type] [queue-mode] pool pool-name
queue queue-id [multipoint
] [queue-type] pool pool-name
Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware schedulers. The expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
The queue command allows the creation of multipoint queues. Only multipoint queues can receive ingress packets that need flooding to multiple destinations. By separating the unicast for multipoint traffic at service ingress and handling the traffic on separate multipoint queues special handling of the multipoint traffic is possible. Each queue acts as an accounting and (optionally) shaping device offering precise control over potentially expensive multicast, broadcast and unknown unicast traffic. Only the back-end support of multipoint traffic (between the forwarding class and the queue based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Queues must be defined as multipoint at the time of creation within the policy.
When an ingress SAP QoS policy with multipoint queues is applied to an Epipe SAP, the multipoint queues are not created. When an ingress SAP QoS policy with multipoint queues is applied to an IES SAP, a multipoint queue will be created when PIM is enabled on the IES interface.
The no form of this command removes the queue-id from the SAP ingress QoS policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.
The queue-id for the queue, expressed as an integer. The
queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.
The expedite,
best-effort and
auto-expedite queue types are mutually exclusive to each other. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the SAP ingress policy. If an attempt to change the keyword after the queue is initially defined, an error is generated.
This keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit queue-id parameters.
Values
|
profile-mode: When the queue is operating in the profile mode (or, the color aware mode), the queue tries to provide the appropriate bandwidth to the packets with different profiles. The profiles are assigned according to the configuration of the forwarding class or the sub-forwarding class.
|
priority-mode: The queue is capable of handling traffic differently with two distinct priorities. These priorities are assigned by the stages preceding the queueing framework in the system. In priority mode, the queue does not have the functionality to support the profiled traffic and in such cases the queue will have a degraded performance. However, the converse is not valid and a queue in profile mode should be capable of supporting the different priorities of traffic.
The no form of the command removes a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool.
[no
] sap-egress
policy-id
The no form of the command deletes the sap-egress policy. A policy cannot be deleted until it is removed from all service SAPs where it is applied. When a sap-egress policy is removed from a SAP, the SAP will revert to the default sap-egress policy-id 1.
queue queue-id [queue-type] [profile-mode | priority-mode
] [multipoint
] pool
pool-name
queue queue-id [queue-type] [multipoint
] pool
pool-name
Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware schedulers. The expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
The queue-id for the queue, expressed as an integer. The
queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.
The expedite,
best-effort and
auto-expedite queue types are mutually exclusive to each other. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the SAP ingress policy. If an attempt to change the keyword after the queue is initially defined, an error is generated.
This keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit queue-id parameters.
The no form of the command removes a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool.
[no] network-queue policy-name
queue queue-id [multipoint
] [queue-type] [queue-mode] pool pool-name
queue queue-id [multipoint
] [queue-type] pool pool-name
Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue allows support for multiple forwarding classes. The default behavior automatically chooses the expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware schedulers. The expedited hardware schedulers are used to enforce expedited access to internal switch fabric destinations. The hardware status of the queue must be defined at the time of queue creation within the policy.
The queue command allows the creation of multipoint queues. Only multipoint queues can receive ingress packets that need flooding to multiple destinations. By separating the unicast for multipoint traffic at service ingress and handling the traffic on separate multipoint queues, special handling of the multipoint traffic is possible. Each queue acts as an accounting and (optionally) shaping device offering precise control over potentially expensive multicast, broadcast and unknown unicast traffic. Only the back-end support of multipoint traffic (between the forwarding class and the queue based on forwarding type) needs to be defined. The individual classification rules used to place traffic into forwarding classes are not affected. Queues must be defined as multipoint at the time of creation within the policy.
The no form of this command removes the queue-id from the network-queue policy and from any existing SAPs using the policy. If any forwarding class forwarding types are mapped to the queue, they revert to their default queues. When a queue is removed, any pending accounting information for each SAP queue created due to the definition of the queue in the policy is discarded.
The queue’s pool association may only be removed by either re-executing the queue command without the
pool keyword or by executing the
no pool command within the queue’s CLI context. When the pool name is removed, the queue will be placed on the appropriate default pool.
The queue-id for the queue, expressed as an integer. The
queue-id uniquely identifies the queue within the policy. This is a required parameter each time the queue command is executed.
The expedite,
best-effort and
auto-expedite queue types are mutually exclusive to each other. Each defines the method that the system uses to service the queue from a hardware perspective. While parental virtual schedulers can be defined for the queue, they only enforce how the queue interacts for bandwidth with other queues associated with the same scheduler hierarchy. An internal mechanism that provides access rules when the queue is vying for bandwidth with queues in other virtual schedulers is also needed. A keyword must be specified at the time the queue is created in the network-queue policy. If an attempt is made to change the keyword after the queue is initially defined, an error is generated.
This keyword specifies that this queue-id is for multipoint forwarded traffic only. This queue-id can only be explicitly mapped to the forwarding class multicast, broadcast, or unknown unicast ingress traffic. If you attempt to map forwarding class unicast traffic to a multipoint queue, an error is generated and no changes are made to the current unicast traffic queue mapping.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit queue-id parameters.
Values
|
profile-mode: When the queue is operating in the profile mode (or, the color aware mode), the queue tries to provide the appropriate bandwidth to the packets with different profiles. The profiles are assigned according to the configuration of the forwarding class or the sub-forwarding class.
|
priority-mode: The queue is capable of handling traffic differently with two distinct priorities. These priorities are assigned by the stages preceding the queueing framework in the system. In priority mode, the queue does not have the functionality to support the profiled traffic and in such cases the queue will have a degraded performance. However, the converse is not valid and a queue in profile mode should be capable of supporting the different priorities of traffic.
The no form of the command removes a named pool association for the queue. When the pool name is removed, the queue will be placed on the appropriate default pool.
show qos named-pool-policy
===============================================================================
Named-Pool Policies
===============================================================================
Policy Name Description
-------------------------------------------------------------------------------
test (not-specified)
test57 (not-specified)
B:SR7-10# show qos sap-ingress 2 detail
===============================================================================
QoS Sap Ingress
-------------------------------------------------------------------------------
Sap Ingress Policy (2)
-------------------------------------------------------------------------------
Policy-id : 2 Scope : Template
Default FC : be Priority : Low
Criteria-type : None
Description : for ingress traffic
-------------------------------------------------------------------------------
Queue Mode CIR Admin PIR Admin CBS HiPrio PIR Lvl/Wt Parent
CIR Rule PIR Rule MBS CIR Lvl/Wt
Named-Buffer Pool
-------------------------------------------------------------------------------
1 Prio 0 max def def 1/1 None
closest closest def 0/1
port_1
2 Prio 0 max def def 1/1 None
closest closest def 0/1
port_2
3 Prio 0 max def def 1/1 None
closest closest def 0/1
pool_50
A:ALA-A>show>qos# shared-queue default detail
===============================================================================
QoS Shared Queue Policy
-------------------------------------------------------------------------------
Shared Queue Policy (default)
-------------------------------------------------------------------------------
Policy : default
Description : Default Shared Queue Policy
-------------------------------------------------------------------------------
Queue CIR PIR CBS MBS HiPrio Multipoint Pool-Name
-------------------------------------------------------------------------------
1 0 100 1 50 10 FALSE pool1
...
-------------------------------------------------------------------------------
A:ALA-A>show>qos#
A:ALA-A>show>qos#
..
-------------------------------------------------------------------------------
Named-Pool Associations
-------------------------------------------------------------------------------
Policy-Name Pool-Name
-------------------------------------------------------------------------------
test p1
testOrig p1
===============================================================================
..
A:ALA-A>show>qos#
card card-slot detail | match “Named Pool Mode”
show card 1 detail | match "Named Pool Mode"
======================================================
Named Pool Mode : Configured (Enabled)
======================================================
mda slot qos
[ingress | egress] buffer-allocation
[detail
]
mda slot qos
[ingress | egress] orphaned-queues
show mda 1/2 detail
-------------------------------------------------------------------------------
QOS Settings
-------------------------------------------------------------------------------
Ing. Named Pool Policy : test
Egr. Named Pool Policy : test
===============================================================================
A:SR7-10# show mda 1/2 qos ingress buffer-allocation
Total buffer space: 122605 kBytes
Total default buffer space (kBytes): Access: 8171 Network: 12256
Total mda buffer space (kBytes): Access: 16347 Network: 61306
===============================================================================
Port Allocation Weights
===============================================================================
Port Percent Total Bw Total Buffer Default % Mda % Port %
-------------------------------------------------------------------------------
1/2/1 100 1000000 12260 16 33 50
1/2/2 100 1000000 12260 16 33 50
1/2/3 100 1000000 12260 16 33 50
1/2/4 100 1000000 12260 16 33 50
1/2/5 100 1000000 12260 16 33 50
1/2/6 100 1000000 12260 16 33 50
1/2/7 100 1000000 12260 16 33 50
1/2/8 100 1000000 12260 16 33 50
1/2/9 100 1000000 12260 16 33 50
1/2/10 100 1000000 12260 16 33 50
===============================================================================
Named Pool Information
===============================================================================
Mda/Port Pool Name Pool Size
-------------------------------------------------------------------------------
1/2 p2 11093
1/2 p3 11093
1/2 port_1 11093
1/2 port_2 11093
A:SR7-10# show mda 1/2 qos ingress buffer-allocation detail
Total buffer space: 122605 kBytes
Total default buffer space (kBytes): Access: 8171 Network: 12256
Total mda buffer space (kBytes): Access: 16347 Network: 61306
===============================================================================
Port Allocation Weights
===============================================================================
Port Percent Total Bw Total Buffer Default % Mda % Port %
Acc/Net Acc/Net Acc/Net Buffer Space
-------------------------------------------------------------------------------
1/2/1 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
1/2/2 100 1000000 12260 16 33 50
Access 1000000 12260 2042 4086 6130
Network 0 0 0 0 0
1/2/3 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
1/2/4 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
1/2/5 100 1000000 12260 16 33 50
Access 1000000 12260 2042 4086 6130
Network 0 0 0 0 0
1/2/6 100 1000000 12260 16 33 50
Access 1000000 12260 2042 4086 6130
Network 0 0 0 0 0
1/2/7 100 1000000 12260 16 33 50
Access 1000000 12260 2042 4086 6130
Network 0 0 0 0 0
1/2/8 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
1/2/9 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
1/2/10 100 1000000 12260 16 33 50
Access 0 0 0 0 0
Network 1000000 12260 2042 4086 6130
===============================================================================
Named Pool Information
===============================================================================
Mda/Port Pool Name Pool Size
Access Network
Weight Total Buffer Space Weight Total Buffer Space
-------------------------------------------------------------------------------
1/2 p2 11093
50 350 2334 50 350 8754
1/2 p3 11093
50 350 2334 50 350 8754
1/2 port_1 11093
50 350 2334 50 350 8754
1/2 port_2 11093
50 350 2334 50 350 8754
1/2 port_3 11093
50 350 2334 50 350 8754
show port 1/2/10 detail
============================
Ing. Pool Policy : n/a
Egr. Pool Policy : test
============================
show port 1/2/10 detail
==========================================================================
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
==========================================================================
A:SR7-10# show pools 1/2
===============================================================================
Type Id App. Pool Name Actual ResvCBS PoolSize
Admin ResvCBS
-------------------------------------------------------------------------------
MDA 1/2 Acc-Ing default 4096 8192
50%
MDA 1/2 Acc-Ing MC Path Mgnt 10240 20480
50%
MDA 1/2 Acc-Egr default 7168 14336
50%
MDA 1/2 Net-Ing default 5120 12288
40%
MDA 1/2 Net-Egr default 12288 24576
50%
MDA 1/2 Ingress p1 0 0
Policy: test 30%
MDA 1/2 Ingress p2 4096 12288
Policy: test 30%
MDA 1/2 Ingress p3 4096 12288
Policy: test 30%
===============================================================================