![]() |
COMMAND DESCRIPTION 14/190 82-CRA 119 1170/1-V1 Uen A | ![]() |
Copyright
© Copyright Ericsson AB 2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
Trademark List
SmartEdge | is a registered trademark of Telefonaktiebolaget L M Ericsson. | |
NetOp | is a trademark of Telefonaktiebolaget L M Ericsson. |
Commands starting with “pp” through commands starting “q” are included.
ppp delay lcp-confreq value
default delay lcp-confreq
Sets the delay between sending a Point-to-Point Protocol over Ethernet (PPPoE) Active Discovery Session (PADS) packet and a Link Control Protocol (LCP) Configuration Request packet if the Point-to-Point Protocol (PPP) peer has not started the LCP.
global configuration
value |
Time, in seconds, that the LCP negotiation request is delayed. The range of values is 1 to 30 seconds; the default value is 3 seconds. |
The default value for the LCP negotiation request time delay is 3 seconds.
Use the ppp delay lcp-confreq command to delay sending
the PPP LCP Configuration Request to the peer after sending the PPPoE
PADS packet. If the SmartEdge OS receives the LCP Configuration
Request of the PPP peer before this delay is satisfied, the SmartEdge
OS sends its own LCP Configuration Request immediately.
The default form of this command sets the delay to 3 seconds when the SmartEdge router sends the LCP Configuration Request.
The following example shows how to set the delay to 5 seconds:
[local]Redback(config)#ppp delay lcp-confreq 5
ppp ipcp disconnect invalid-ip-address
Sends a Point-to-Point Protocol (PPP) termination request to subscribers when they do not negotiate a valid IP address during the PPP Internet Protocol Control Protocol (IPCP) negotiation process.
This command has no keywords or arguments.
None.
Use the ppp ipcp disconnect invalid-ip-address command to send a PPP termination request to subscribers when they do not negotiate a valid IP address during the IPCP negotiation process.
The following example shows how to enable the PPP termination request feature:
[local]Redback(config)#ppp ipcp disconnect invalid-ip-address
ppp ipcp peer-address ip-address
Configures a static IP address that the SmartEdge system can provide to the static point-to-point protocol (PPP) peer devices during the establishment of PPP links.
Interface configuration
ip-address |
The static IP address provided to the static PPP peer devices during the establishment of PPP links. ip-address should belong to the same subnet as the interface. |
No IP address is provided to the PPP peer device.
Use the ppp ipcp peer-address command to configure a static IP address that the SmartEdge system can provide to the PPP peer devices during the establishment of PPP links.
The following example illustrates how the IP address offered in the IPCP phase of PPP negotiations is configured for an interface:
[local]Redback(config)#context blue [local]Redback(config-ctx)#interface yellow [local]Redback(config-if)#ip address 10.0.0.1/24 [local]Redback(config-if)#ppp ipcp peer-address 10.0.0.2
The first time you run this command in a context, the command syntax is:
ppp keepalive check-interval {minutes | seconds} time
After you specify the check interval for a context, the command syntax is:
ppp keepalive {[data-check] [response-timeout seconds] [retries retry-num]}
no ppp keepalive [check-interval] [data-check]
default ppp keepalive {response-timeout | retries}
Enables Point-to-Point Protocol (PPP) keepalive checks and specifies PPP timing attributes.
check-interval |
Sets the time interval between PPP keepalive checks. Optional after you have specified the initial check interval. |
minutes |
Specifies that the unit of measure for the time argument is minutes. |
seconds |
Specifies that the unit of measure for the time argument is seconds. |
time |
Time, in either minutes or seconds (depending on the preceding keyword), between keepalive checks. |
data-check |
Optional. Specifies that after the PPP keepalive check interval timer expires and before a Link Control Protocol (LCP) echo request message is sent, a check is performed to determine if data has been received on the circuit since the last check interval timer expiration. |
response-timeout seconds |
Optional. Amount of time the system is to wait for a response to an LCP echo request message before incrementing the PPP keepalive retries counter. The range of values is 3 to 60 seconds; the default value is 10. |
retries retry-num |
Optional. Number of times the system is to retry an unsuccessful PPP keepalive check. The range of values is 2 to 10; the default value is 2. |
Keepalive checks are not enabled, except in the case of circuits using PPP over Ethernet (PPPoE), for which the period between keepalive checks is 5 minutes (300 seconds).
Use the ppp keepalive command to enable PPP keepalive checks and specify PPP timing attributes. The command keywords work together to configure when and how keepalives are sent, and what action is taken as a result of the response, or lack of response.
Keepalive checks are LCP echo request messages sent over PPP sessions in the context to detect abnormal session disconnects that the system would not otherwise know about. The check-interval keyword must be entered before the other command keywords are available.
The check-interval keyword sets the time between LCP echo requests, in either minutes or seconds. When this time expires, an LCP echo request is sent to the PPP peer and a response timer is started. The length of the response timer is determined by the value of the response-timeout seconds construct. If a valid LCP echo is received before the response timer expires, the response timer is canceled, and the check interval timer is reset.
If the response timer expires without a valid LCP echo being received, an optional check, specified by the data-check keyword, is performed to see if any data has been received on the circuit since the LCP echo request was sent. Only valid PPP packets are considered data. If data has been received since the LCP echo request was sent, the check interval timer is reset. If no data has been received, the retry counter is incremented and another LCP echo request message is sent. When the configured number of retries has been reached, set by the value of the retries retry-num construct, without a valid echo or data being received, the session is considered to be no longer alive and is torn down.
The data-check keyword specifies that after the check interval timer expires and before an LCP echo request message is sent, a check is performed to determine if data has been received on the circuit since the last check interval timer expiration. If data has been received, the check interval timer is simply reset, skipping the LCP echo request message altogether. This option is recommended when it is preferred to limit the overhead for PPP keepalive processing. The tradeoff is that using the data-check keyword to determine that a session is no longer active can take longer than using the PPP keepalive feature without the data-check keyword. For an example illustrating this tradeoff, see PPP Keepalive Checks in PPP Keepalive Checks.
Although the default period between keepalive checks for PPPoE circuits is 5 minutes (300 seconds) if keepalive checks are not enabled, PPPoE circuits take on the configured period between checks when keepalive checks are enabled.
Use the no form of this command without options to disable all command options.
Use the default form of this command to specify the default value for the response timer or the number of retries.
The following example shows how to enable the PPP keepalive feature, sets the length of the response timer and the number of retries, and specifies the data check option to minimize LCP echo traffic:
[local]Redback(config-ctx)#ppp keepalive check-interval seconds 500 [local]Redback(config-ctx)#ppp keepalive data-check response-timeout 30 retries 3
ppp mtu mtu
Sets the maximum transmission unit (MTU) used by Point-to-Point Protocol (PPP) for a subscriber’s circuit.
mtu |
Maximum transmission unit in bytes. The range of values is 256 to 12800. |
None
Use the ppp mtu command to set the MTU used by PPP for a subscriber circuit. The effect of this command is strictly local to the SmartEdge router, and therefore, does not force the router to negotiate a particular PPP MRU.
Use the ppp mtu command to lower the size of data packets being sent over that subscriber link from the MRU value that has been negotiated between the SmartEdge router and the PPP client. You cannot make the size any larger than the negotiated MRU. If an MRU value lower than the value of the mtu argument in the ppp mtu command has been negotiated, the MRU value takes precedence and the ppp mtu command setting is ignored.
On a normal Ethernet interface, the standard MTU is 1500. For Point-to-Point Protocol over Ethernet (PPPoE) implementation, the negotiated MTU uses the physical interface, minus eight bytes as the default.
The following example shows how to set the PPP MTU to 768 bytes:
[local]Redback(config-sub)#ppp mtu 768
ppp multilink
no ppp multilink
Enables multilink Point-to-Point Protocol (PPP) for subscriber sessions on PPP-encapsulated Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs), PPPoE over Ethernet (PPPoE)-encapsulated 802.1Q PVCs, 802.1Q tunnels, untagged Ethernet traffic, and Layer 2 Tunneling Protocol (L2TP) tunnels.
This command has no keywords or arguments.
Multilink PPP (MP) is disabled for subscriber sessions on PPP-encapsulated ATM PVCs, PPPoE-encapsulated 802.1Q PVCs and tunnels, untagged Ethernet traffic, and L2TP tunnels.
Use the ppp multilink command to enable MP for subscriber sessions on ATM PVCs, PPPoE-encapsulated 802.1Q PVCs and tunnels, untagged Ethernet traffic, and L2TP tunnels.
Use the no form of this command to specify the default condition.
The following example shows how to enable MP:
[local]Redback(config)#ppp multilink
ppp multilink lfi fragment-threshold value [priority-threshold value]
no ppp multilink lfi
Enables Point-to-Point Protocol (PPP) Link Fragmentation and Interleaving (LFI) within the specified priority or fragmentation threshold value for subscriber sessions on PPP-encapsulated Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs), PPP over Ethernet (PPPoE)-encapsulated 802.1Q PVCs and tunnels, untagged Ethernet traffic, and Layer 2 Tunneling Protocol (L2TP) tunnels.
fragment-threshold value |
Fragmentation on outgoing traffic. The range of values is 258 to 16,320; the default value is 0. |
priority-threshold value |
Optional. Multiprotocol encapsulation priority level. The range of values is 0 to 7; the default value is 0. |
The default does not enable LFI priority and fragmentation thresholds for subscriber sessions on PPP-encapsulated ATM PVCs, PPPoE-encapsulated 802.1Q PVCs and tunnels, untagged Ethernet traffic, and L2TP tunnels.
Use the ppp multilink lfi command to enable PPP LFI with the specified priority or fragmentation threshold values for subscriber sessions on PPP-encapsulated ATM PVCs, PPPoE-encapsulated 802.1Q PVCs and tunnels, untagged Ethernet traffic, and L2TP tunnels.
Use the fragment-threshold value construct to set the fragmentation threshold on outgoing traffic. The range of values is 258 to 16,320. The threshold size is not to exceed the value specified by the user, but does not necessarily need to be the same as the fragment threshold. The default value is 0, with no packets becoming fragmented.
Use the optional priority-threshold value construct to define the multiprotocol encapsulation priority level. The packet is encapsulated only if it is of lower or equal priority than the configured threshold. If the packet is not multiprotocol encapsulated, it is not fragmented, regardless of the size. All packets are multiprotocol encapsulated if their priority is lower than or equal to the threshold. The default value of 0 results in all packets being multiprotocol encapsulated.
Use the no form of this command to disable LFI priority and fragmentation thresholds.
The following example shows how to enable PPP LFI with a specified fragmentation threshold value of 258:
[local]Redback(config)#ppp multilink lfi fragment-threshold 258
The following example shows how to enable PPP LFI with a specified priority threshold value of 7:
[local]Redback(config)#ppp multilink lfi priority-threshold 7
pppoe always-send-padt
{no | default} pppoe always-send-padt
Configures a Point-to-Point Protocol (PPP)-encapsulated (PPPoE) option that terminates the PPPoE session by sending a PPPoE Active Discovery Terminate (PADT) packet after the PPP session is terminated.
global configuration
This command has no keywords or arguments.
The PPPoE option does not terminate the PPPoE session when the PPP session is terminated.
Use the pppoe always-send-padt command to configure a PPPoE option that terminates the PPPoE session after a PPP session is terminated.
Use this command if the PPPoE client requires explicit termination of the PPPoE session.
The PPPoE option is a global and will be applied to all PPPoE sessions that are currently established and for all future sessions.
Use the no or default form of this command to disable the PPPoE option that terminates the PPPoE session once the PPP session has terminated.
The following example shows how to configure the PPPoE option to terminate the PPPoE session after the PPP session has terminated:
[local]Redback(config)#pppoe always-send-padt [local]Redback(config)#end
pppoe circuit padi per-mac count padi-num allow-time allow-interval drop-time drop-interval
{no | default} pppoe circuit padi per-mac
Limits the number of Point-to-Point Protocol over Ethernet Active Discovery Initialization (PADI) messages that the system accepts in a specified interval for each medium access control (MAC) address.
count padi-num |
Number of PADI messages allowed per MAC address on each circuit during the specified interval. The range of values is 1 to 255. |
allow-time allow-interval |
Interval, in seconds, during which the system counts PADI messages. The range of values is 1 to 127. |
drop-time drop-interval |
Number of seconds during which PADI messages are dropped, if the allowed number of PADI messages was exceeded in the previous interval. The range of values is 1 to 127. |
The SmartEdge router does not limit the outstanding PADI message that the router accepts in a specified interval for each MAC address.
Use the pppoe circuit padi per-mac command to limit the number of PPPoE PADI messages that the system accepts in an interval for each MAC address.
This command applies only to PPPoE-encapsulated circuits on the following traffic cards:
Use the no or default form of this command to specify the default condition.
The following example shows how to accept 150 PADI messages per MAC address in every 2-second interval. If more than 150 PADI messages are received during the interval, all PADI messages are dropped for 3 seconds following the interval. Following that, 150 PADI messages are allowed per MAC address for the next 2-second interval:
[local]Redback(config)#pppoe circuit padi per-mac count 150 allow-time 2 drop-time 3
pppoe circuit padr per-mac count padr-num allow-time allow-interval drop-time drop-interval
{no | default} pppoe circuit padr per-mac
Limits the number of Point-to-Point Protocol over Ethernet Active Discovery Request (PADR) messages that the system accepts in a specified interval for each medium access control (MAC) address.
count padr-num |
Number of PADR messages allowed per MAC address on each circuit during the specified interval. The range of values is 1 to 255; the default value is 1. |
allow-time allow-interval |
Interval, in seconds, during which the system counts PADR messages. The range of values is 1 to 127; the default value is 1. |
drop-time drop-interval |
Number of seconds during which PADR messages are dropped, if the allowed number of PADR messages was exceeded in the previous interval. The range of values is 1 to 127; the default value is 1. |
The PPPoE session limits the outstanding PADR message count to 1 for each MAC address until it receives a PPPoE Active Discovery Session (PADS) reply for that session.
Use the pppoe circuit padr per-mac command to limit the number of PPPoE PADR messages that the system accepts in an interval for each MAC address.
This command applies only to PPPoE-encapsulated circuits on the following traffic cards:
Use the no or default form of this command to specify the default condition.
The following example shows how to accept 200 PADR messages per MAC address in every 2-second interval. If more than 200 PADR messages are received during the interval, all PADR messages are dropped for 3 seconds following the interval. Following that, 200 PADR messages are allowed per MAC address for the next 2-second interval:
[local]Redback(config)#pppoe circuit padr per-mac count 200 allow-time 2 drop-time 3
pppoe client route ip-addr netmask metric
no pppoe client route ip-addr netmask metric
Configures routes to be installed on the subscriber’s PC when multiple Point-to-Point Protocol over Ethernet (PPPoE) sessions exist.
ip-addr |
IP address of the destination host. |
netmask |
Network mask for the route entry. |
metric |
Cost (number of hops) to this destination. |
Routes are not sent to the subscriber’s PPPoE client.
Use the pppoe client route command to configure the SmartEdge router to provide different routes for different PPPoE sessions. For each PPPoE session, a route is sent in a PPPoE Active Discovery Network (PADN) message, and installed on the subscriber’s PC. In this way, subscribers are enabled with seamless client route provisioning on a per-PPPoE session basis. The subscriber’s PC client must support PADN. If the PPPoE client ignores the routes, they have no effect.
As an example of this feature, one PPPoE session could provide Internet connectivity, while another session connects corporate headquarters to a remote office site. Routes to the business site might be of a very different nature than the routes that provide access to the Internet.
Use the no form of this command to remove the specified route from the configuration.
The following example shows how to specify that a route at 200.1.1.0 255.255.255.0 is to be used for concurrent multiple PPPoE sessions. This route has a metric, or hop count, of 1:
[local]Redback(config-sub)#pppoe client route 200.1.1.0 255.255.255.0 1
pppoe motm text
no pppoe motm
Creates and enables the sending of a message of the minute (MOTM) to a subscriber when logging on.
subscriber configuration
text |
Text of the MOTM to be sent to a newly authenticated subscriber. The maximum length of an MOTM is 256 characters. Only one MOTM can be active at a time. |
None
Use the pppoe motm command to create and enable the sending of a message to the subscriber when logging on. You can use this command to send any information of general use to subscribers; for example, information about system downtime.
Use the no form of this command to delete the MOTM so that the message is no longer sent to the subscriber after logging on.
The following example establishes an MOTM:
[local]Redback(config-sub)#pppoe motm Network will be down for maintenance from 0100-0400 Saturday.
The following example deletes the active MOTM:
[local]Redback(config-sub)#no pppoe motm
pppoe pado delay delay-value
no pppoe pado delay
Sets the Point-to-Point Protocol over Ethernet Active Discovery Offer (PADO) delay timer to the specified number of seconds.
delay-value |
Delay value, in seconds. The range of values is 1 to 3. |
No PPPoE PADO delay value is set.
Use the pppoe pado delay command to set the PPPoE PADO delay timer to the specified value, in number of seconds.
Use the no form of this command to delete the PPPoE PADO delay timer value.
The following example shows how to set the 802.1Q blue profile to have a PADO delay time of 3 seconds:
[local]Redback(config)#dot1q profile blue [local]Redback(config-dot1q-profile)#pppoe pado delay 3
pppoe service-name accept-all
no pppoe service-name accept-all
Enables the SmartEdge router to accept any service name tag that is included in a Point-to-Point Protocol over Ethernet (PPPoE) Active Discovery Initiation (PADI) or PPPoE Active Discovery Request (PADR) message and include it among the advertised services in a PPP Active Discovery Offer (PADO) or PPPoE Active Discovery Session (PADS) message, respectively.
This command has no keywords or arguments.
The SmartEdge router accepts and advertises only those services (domains) that have been configured through the SmartEdge router.
Use the pppoe service-name accept-all command to enable the SmartEdge router to accept any service name tag that is included in a PPPoE PADI message, and include it among the advertised services in PPP PADO messages. It also accepts any service name tag that is included in a PPPoE PADR message and includes it in a PPPoE PADS message.
Use the no form of this command to disable the acceptance and advertisement of service name tags that are not configured through the SmartEdge router.
The following example shows how to enable the acceptance of all service names that might be included in PADI or PADR messages:
[local]Redback(config)#pppoe service-name accept-all
pppoe services {all-domains | marked-domains}
{no | default} pppoe services
Specifies which domains (services) are advertised to Point-to-Point Protocol over Ethernet (PPPoE) clients.
global configuration
all-domains |
Specifies that all domains are advertised. |
marked-domains |
Specifies that only domains that have the advertise keyword as part of their definition are advertised. |
No domains are advertised to PPPoE clients.
Use the pppoe services command to specify which domains (services) are advertised to PPPoE clients and make public the services that the SmartEdge router provides.
Use the no or default form of this command to disable domain advertisement.
The following example shows how to enable the advertisement of marked domains to PPPoE clients:
[local]Redback(config)#pppoe services marked-domains
pppoe tag {ac-name string | ac-cookie}
{no | default} pppoe tag {ac-name | ac-cookie}
Replaces the default access concentrator (AC)-Name PPPoE tag value with the specified string or enables AC-Cookie tag support.
global configuration
ac-cookie |
Enables AC-Cookie tag support. |
ac-name string |
Alphanumeric string to replace the default value for the AC-Name PPPoE tag. |
The SmartEdge router uses an automatically generated (and guaranteed to be unique) value for the AC-Name PPPoE tag and AC-cookie tag support is disabled.
RFC 2516, Transmitting PPP Over Ethernet, specifies that the AC-Name PPPoE tag sent in PPPoE Active Discovery Offer (PADO) messages must have a unique value. The SmartEdge router ensures that this value is unique by creating it from a combination of the backplane serial number and the hostname of the AC device sending the PADO message. When it is preferred to override this default, use this command to establish an alternate value for the AC-Name tag. After you change the default, the SmartEdge router can no longer guarantee that the value is unique.
SmartEdge router also supports the AC-Cookie tag described in RFC 2516 to allow the AC to uniquely regenerate the tag value based on the PADR source address. Using this feature, the AC can ensure that the PADI source address is indeed reachable and can then limit concurrent sessions for that address.
Use the no or default form of this command to return the AC-Name value to the automatically generated default name or to disable AC-Cookie tag support.
The following example replaces the AC-Name PPPoE tag with fortune-1:
[local]Redback(config)#pppoe tag ac-name fortune-1
pppoe url url
no pppoe url
Sets the subscriber’s Point-to-Point Protocol over Ethernet (PPPoE) client to automatically point the web browser to a specified URL as soon as the session is established.
subscriber configuration
url |
URL to which the subscriber’s browser is pointed after the subscriber’s PPP session is established. For special-character sequences that can be used in the url argument, see Table 1. |
None
Use the pppoe url command to set the subscriber’s PPPoE client to point the subscriber’s browser to a specific location after the subscriber’s PPP session is established.
This command can be configured in each subscriber record, in a named subscriber profile, or in the subscriber default profile.
The url argument is a standard URL that can contain the special-character sequences listed in Table 1.
Character Sequence |
Expands to: |
---|---|
%U |
The entire subscriber name used in PPP authentication. |
%u |
The user portion of the subscriber name used in PPP authentication. This is the portion of the subscriber name that precedes the first @ or other divider character. If there is no divider character, then %u expands to the entire subscriber name. |
%d |
The domain portion of the subscriber name used in PPP authentication. This is the portion of the subscriber name that follows the first @ or other divider character. If there is no divider character, %d expands to a zero length string. |
%D |
The name of the context to which the subscriber was authenticated. This may be different than the domain portion of the subscriber name. |
%% |
Single % character. |
The SmartEdge router expands these sequences prior to inclusion in a PPP Active Discovery Message (PADM) and can be used to personalize the URL to the subscriber.
Use the no form of this command to remove the URL association from the subscriber record.
For a subscriber, joe, in the context, local, the following example allows a PADM containing the URL http://www.loe.com/members/joe@local to be sent to the PPPoE client when the PPP session is established:
[local]Redback(config-ctx)#subscriber name joe [local]Redback(config-sub)#pppoe url http://www.loe.com/members/%U
For every subscriber to which the subscriber default value is applied, the following example sends a PADM containing http://www.loe.com/members/name to the PPPoE client when the PPP session is established:
[local]Redback(config-ctx)#subscriber default [local]Redback(config-sub)#pppoe url http://www.loe.com/members/%u
ppp our-options mru initial initial-mru maximum max-mru
default ppp our-options mru
Specifies the range for the maximum receive unit (MRU) with which the SmartEdge router negotiates Link Control Protocol (LCP) option values for the SmartEdge router end of the Point-to-Point Protocol (PPP) session.
initial initial-mru |
MRU value at which negotiation begins. The range of values is 256 to 12,800; the default value is 1,500 for PPP circuits, and 1,492 for PPP over Ethernet (PPPoE) circuits. |
maximum max-mru |
Maximum MRU value that the SmartEdge router can negotiate. The range of values is 256 to 12,800; the default value is 12,800. |
If you do not use this command, the SmartEdge router uses the default values described in the Syntax Description section of this command.
Use the ppp our-options mru command to specify the range for the MRU with which the SmartEdge router negotiates LCP option values for the SmartEdge router end of PPP sessions.
Currently, the options available are the initial and maximum MRU values. When these values are specified, the SmartEdge router begins negotiation for its MRU at the value of the initial-mru argument, and does not exceed the value of the max-mru argument. The resulting size guidelines are reflected in all packets sent to the SmartEdge router by the remote peer.
If, after 10 attempts, an agreement with the peer can not be reached as to a local MRU between the configured initial and maximum values, the SmartEdge router establishes the PPP session without negotiating the local MRU. In that case, the SmartEdge router uses an MRU of 1,500 for PPP circuits and 1,492 for PPPoE circuits.
Use the default form of this command to return the LCP options for MRU to their default values.
The following example shows how to set the local initial and maximum MRU values:
[local]Redback(config)#ppp our-options mru initial 1800 maximum 11000
ppp our-options multilink endpoint-discriminator [addr]
{no | default} ppp our-options multilink endpoint-discriminator
Specifies the address for the SmartEdge router end of multilink Point-to-Point Protocol (MP) bundles.
endpoint-discriminator |
Specifies the endpoint discriminator for the SmartEdge router end of MP bundles. |
addr |
Optional. Address, either IP or medium access control (MAC), for the SmartEdge router, according to one of the constructs or keywords listed in Table 2. |
If you do not use this command, the SmartEdge router uses the hostname and IP address of the SmartEdge router.
Use the ppp our-options multilink command to specify the address for the SmartEdge router end of MP bundles. This command is not available until you have enabled MP using the ppp multilink command (in global configuration mode).
Table 2 lists the address types and their constructs for the addr argument.
addr Argument |
Description |
---|---|
class-1 text |
Locally assigned address consisting of up to 20 characters. |
class-2 ip-addr |
IP address. |
class-3 mac-addr |
MAC address. |
class-5 text |
Public-switched network directory number consisting of up to 15 characters. |
local-ip-address |
IP address of the Ethernet management port on the controller card. |
local-mac-address |
MAC address of the SmartEdge router; this is the default address. |
Use the no or default form of this command to specify the local MAC address of the SmartEdge router.
The following example shows how to specify the IP address of the Ethernet management port on the controller card as the endpoint discriminator:
[local]Redback(config)#ppp our-options multilink endpoint-discriminator local-ip-address
ppp peer-options mru minimum min-mru maximum max-mru
default ppp peer-options mru
Specifies the range for the maximum receive unit (MRU) with which the SmartEdge router negotiates Link Control Protocol (LCP) option values for the remote end of the Point-to-Point Protocol (PPP) session.
minimum min-mru |
Minimum MRU value for the remote peer. The range of values is 128 to 16,384; the default value is 128. |
maximum max-mru |
Maximum MRU value for the remote peer. The range of values is 128 to 16,384; the default value is 16,384. |
The SmartEdge router negotiates LCP options with the default values.
Use the ppp peer-options mru command to specify the range for the MRU with which the SmartEdge router negotiates LCP option values for the remote end of PPP sessions.
Currently, the options available are the minimum and maximum MRU values. When these values are specified, the SmartEdge router negotiates the remote peer’s MRU value to be at least the value specified by the min-mru argument, and not greater than the value specified by the max-mru argument. The resulting size guidelines are reflected in all packets that the SmartEdge router sends to the remote peer.
If, after 10 attempts, the SmartEdge router has not reached an agreement with the peer regarding the value of the peer’s MRU between the specified minimum and maximum values, the SmartEdge router establishes the PPP session without negotiating the peer’s MRU. In that case, the SmartEdge router uses the standard MRU of 1,500 for PPP circuits, and 1,492 for PPP over Ethernet (PPPoE) circuits.
Use the default form of this command to return the options to their default values.
The following example shows how to set the peer’s minimum and maximum MRU values:
[local]Redback(config)#ppp peer-options mru minimum 200 maximum 2000
ppp pppoe-large-mru
no ppp pppoe-large-mru
Enables the negotiation of the maximum receive unit (MRU) larger than 1492 bytes for Point-to-Point Protocol over Ethernet (PPPoE) circuits as described in RFC 4638.
This command has no keywords or arguments.
MRU negotiation is disabled.
Use the ppp pppoe-large-mru command to enable the negotiation of a MRU larger than 1492 bytes for PPPoE circuits as described in RFC 4638. If the SmartEdge router is configured with this command, an MRU larger than 1492 bytes is allowed only when the PPPoE PPP-Max-Payload tag is received from the client and the client initiates MRU negotiation.
The MRU negotiation is decided in described in RFC 4638. These negotiations are based on the PPPoE PPP-Max-Payload tag value received, and the subscribers and ports MTU value.
Use the no form of this command to disable MRU negotiation. When MRU negotiation is disabled, the MRU is set to 1,492 bytes.
The following example shows how to enable MRU negotiation:
[local]Redback(config)#ppp pppoe-large-mru
preempt [hold-time interval]
{no | default} preempt [hold-time interval]
Enables a higher priority Virtual Router Redundancy Protocol (VRRP) backup router to preempt a lower priority VRRP master.
VRRP configuration
hold-time interval |
Specifies a hold time, in seconds, for which a higher-priority VRRP backup router must wait before preempting a lower-priority VRRP master. This construct is supported on backup (non-owner) VRRP routers only. |
Preemption is enabled.
Use the preempt command to enable a VRRP backup router that has a higher priority to preempt a lower priority VRRP master. Use the optional hold-time interval construct to specify a hold time, in seconds, for which a higher-priority VRRP backup router must wait before preempting a lower-priority VRRP master. Configure the preemption hold time when you want the higher-priority server to wait before trying to preempt the current master while the system completely converges.
When preemption is disabled, a higher priority VRRP backup router does not preempt a lower priority VRRP master.
The master VRRP router can never be preempted by another router, and it always advertises a VRRP priority of 255. The priority of 255 is reserved for the master VRRP router. If a failure occurs in the master VRRP router, a backup router takes over until the master VRRP router comes back up. In such cases, the master VRRP router immediately preempts the backup router; a preempt hold time is ignored if it is configured on the master VRRP router.
Use the no or default form of this command to disable preemption.
The following example disables preemption on the VRRP backup router with virtual ID 23:
[local]Redback(config-if)#vrrp 23 backup [local]Redback(config-vrrp)#no preempt [local]Redback(config-vrrp)#
preferred-lifetime preferred-lifetime
{no | default} preferred-lifetime
Specifies the value for the Preferred Lifetime field.
preferred-lifetime |
Value for the Preferred Lifetime field (in seconds). The range of values is 0 to 4,294,967,295; the default value is 604,800 seconds (7 days). |
The preferred lifetime is seven days.
Use the preferred-lifetime command to specify the value for the Preferred Lifetime field. In ND router configuration mode, this command specifies the global value for all interfaces; in ND router interface mode, it specifies the value for this Neighbor Discovery (ND) router interface. If specified, the setting for the interface overrides the global setting.
Use the no or default form of this command to specify the default value.
The following example specifies a preferred lifetime of 43200 seconds (12 hours) for all interfaces for this ND router:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd-if)#preferred-lifetime 43200
The following example specifies a preferred lifetime of 2880 seconds (48 minutes) for the int1 ND router interface, which overrides the global setting:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd)#interface int1 [local]Redback(config-nd-if)#preferred-lifetime 2880
prefix ipv6-prefix/length [no-autoconfig] [no-onlink] [preferred-lifetime preferred-lifetime] [valid-lifetime valid-lifetime]
{no | default} prefix ipv6-prefix/length
Configures a prefix to be advertised for this Neighbor Discovery (ND) router interface.
ipv6-prefix |
Prefix for the IPv6 address for this ND router interface in the format A:B:C:D:E:F:G:H. |
length |
Number of prefix bits. The range of values is 0 to 128. |
no-autoconfig |
Optional. Sets the autonomous address configuration flag to not use this prefix for automatic configuration; this is the default. |
no-onlink |
Optional. Sets the on-link flag to not use this prefix for on-link determination; this is the default. |
preferred-lifetime preferred-lifetime |
Optional. Preferred lifetime for this prefix (in seconds). The range of values is 0 to 4,294,967,295; the default value is 604,800 seconds (7 days). |
valid-lifetime valid-lifetime |
Optional. Valid lifetime for this prefix (in seconds). The range of values is 0 to 4,294,967,295; the default value is 2,592,000 seconds (30 days). |
No prefix is configured for any ND router interface.
Use the prefix command to configure a prefix to be advertised for this ND router interface. Enter this command multiple times to configure more than one prefix.
Use the optional keywords and constructs to define the fields in the Prefix Information option for this prefix:
The values for the preferred-lifetime preferred-lifetime and valid-lifetime valid-lifetime constructs override the values for the interface that you specified with the preferred-lifetime and valid-lifetime commands (in ND router interface configuration mode).
Use the no or default form of this command to delete the specified prefix from this interface configuration.
The following example configures the 5555:bbbb::22/64 prefix for the int1 ND router interface:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd)#interface int1 [local]Redback(config-nd-if)#prefix 5555:bbbb::22/64 no-autoconfig no-onlink preferred-lifetime 360 valid-lifetime 360
prefix-list pl-name {in | out}
no prefix-list pl-name {in | out}
Filters Border Gateway Protocol (BGP) routes from or to the neighbor address family or peer group address family.
pl-name |
Name of the prefix list. |
in |
Applies the prefix list to incoming updates from the neighbor. |
out |
Applies the prefix list to outgoing updates to the neighbor. This keyword can only be applied in BGP neighbor address family configuration mode. |
There are no preconfigured prefix lists.
Use the prefix-list command to filter BGP routes from or to the neighbor address family or peer group address family. Use this command in conjunction with the ip prefix-list command in context configuration mode, which creates the conditions of the filter.
Use the in keyword to filter incoming BGP routes from the specified neighbor or peer. Use the out keyword to filter outgoing BGP routes to the specified neighbor.
Currently, prefix list changes automatically take effect, and issuing the clear bgp neighbor ip-addr soft [in | out] command in exec mode to update a prefix list can cause updates to be unnecessarily sent; therefore, it is not recommended.
To aggregate multiple policy changes, such as the prefix list, the operating system performs the automatic update 15 seconds after any routing policy has changed.
Use the no form of this command to remove the application of a prefix list.
The following example denies incoming unicast BGP routes 10.0.0.0/8 (and more-specific routes) from the unicast neighbor at IP address 102.210.210.1. Outgoing multicast BGP routes 204.16.16.0/24 can be sent to the multicast neighbor at IP address 68.68.68.68:
[local]Redback(config-ctx)#ip prefix-list prefix-101 [local]Redback(config-prefix-list)#deny 10.0.0.0/8 le 32 [local]Redback(config-prefix-list)#permit 0.0.0.0/0 le 32 [local]Redback(config-prefix-list)#exit [local]Redback(config-ctx)#ip prefix-list prefix-202 [local]Redback(config-prefix-list)#permit 204.16.16.0/24 . . . [local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#neighbor 102.210.210.1 external [local]Redback(config-bgp-neighbor)#remote-as 200 [local]Redback(config-bgp-neighbor)#address-family ipv4 unicast [local]Redback(config-bgp-peer-af)#prefix-list prefix-101 in [local]Redback(config-bgp-peer-af)#exit [local]Redback(config-bgp-neighbor)#exit [local]Redback(config-bgp)#neighbor 68.68.68.68 external [local]Redback(config-bgp-neighbor)#remote-as 300 [local]Redback(config-bgp-neighbor)#address-family ipv4 multicast [local]Redback(config-bgp-peer-af)#prefix-list prefix-202 out
priority priority
no priority
Configures the priority of the interface when the maximum bandwidth in the service profile has been exhausted.
IGMP service profile configuration
priority |
Priority setting for the interface. The range of values is 0 to 10. |
The interface has no priority setting.
Use the priority command to configure the priority of the interface when the maximum bandwidth in the service profile has been exhausted.
When the addition of a new group would cause the maximum bandwidth, as specified by the igmp maximum-bandwidth command, to be exceeded on the port, the router searches for subscribers joined on the same port with a lower priority. The router drops the lower priority subscribers and reclaims their bandwidth until it gets enough bandwidth to service the higher priority subscriber. If it cannot reclaim enough bandwidth the new group join will be dropped.
Use the no form of this command to delete the priority setting for the interface.
The following example configures a priority of 8 for the interface:
[local]Redback(config-ctx)#igmp service-profile bar [local]Redback(config-igmp-service-profile)#priority 8
priority priority [level-1 | level-2]
no priority
Configures the Intermediate System-to-Intermediate System (IS-IS) designated router priority setting for the specified LAN interface.
IS-IS interface configuration
priority |
Priority setting. The range of values is 0 to 127; the default value is 64. Higher numbers signify a higher priority. |
level-1 |
Optional. Sets the priority for IS-IS level 1 routing independently. |
level-2 |
Optional. Sets the priority for IS-IS level 2 routing independently. |
The priority setting is 64.
Use the priority command to configure the IS-IS designated router priority setting for the specified LAN interface.
A priority value determines which router on a network is the first router chosen for sending and receiving traffic. The priority value is advertised in Hello packets. The router with the highest priority becomes the Designated Intermediate System (DIS).
In IS-IS, there is no backup designated router. If a router is set to priority 0, it has a smaller chance of becoming the DIS, but it may not be prevented from becoming the DIS. When a router with a higher priority becomes available on the network, it takes over as the current DIS. In the case of equal priorities, the highest medium access control (MAC) address breaks the tie.
Use the no form of this command to restore the default priority.
The following example sets the priority for the fa4/1 interface to 80, making it more likely to become the DIS for IS-IS level-1 routing:
[local]Redback(config-ctx)#router isis ip-backbone [local]Redback(config-isis)#interface fa4/1 [local]Redback(config-isis-if)#priority 80 level-1
priority level
no priority
Sets the priority of loop-prevention blocking on the assigned circuit.
level |
Priority of loop-prevention blocking on the assigned circuit (0 to 5). |
0 (never blocked)
Use the priority command to set the priority of loop-prevention blocking on the assigned circuit. The default is 0 (unblockable). Except for circuits with priority 0, circuits with higher priority are blocked before circuits with lower priority. Circuits with priority 0 are never blocked.
Use the no form of this command to return the priority of loop-detection of the assigned circuit to its default.
The following example creates the bridge profile, plow, and sets the loop-detection priority for circuits associated with that bridge profile to the value 2:
[local]jeudi.lab(config)#bridge profile plow [local]jeudi.lab(config-bridge-profile)#loop-detection [local]jeudi.lab(config-bridge-profile-ld)#priority 2
priority setup-priority [hold-priority]
no priority
For Constrained Shortest Path First (CSPF), specifies the preemptive characteristics of the label-switched path (LSP).
setup-priority |
Setup priority. The range of values is 0 to 7, where the lower the number, the greater the priority. |
hold-priority |
Optional. Hold priority. The range of values is 0 to 7, where the lower the number, the greater the priority. |
Setup priority is 7. Hold priority is 0.
For CSPF, specifies the preemptive characteristics of the LSP. The setup priority specifies whether a new LSP can preempt an existing LSP. The hold priority determines whether the LSP can preserve its session reservation after being established. If the setup priority of the new LSP has a higher priority (a lower number) than the hold priority of an existing LSP, and resource contention exists between two LSPs, they preempt each other forever because neither LSP can preserve its session reservation. The system prevents you from configuring the hold priority to a higher priority (lower number) than the setup priority.
The following scenario illustrates what happens when two LSPs are configured with the same setup priority but with a lower hold priority, and resource contention exists between both LSPs. In this case, both LSP1 and LSP2 have a setup priority of 6 and a hold priority of 7:
Use the no form of this command to remove the tunnel priority.
The following example shows how to configure an LSP with a setup priority of 2 and a hold priority of 2:
[local]Redback#configure [local]Redback(config)#context sj1 [local]Redback(config-ctx)#router rsvp [local]Redback(config-rsvp)#constraint constraint1 [local]Redback(config-rsvp-constr)#priority 2 2
priority level
{no | default} priority
Sets the priority of the bridge.
level |
Priority of the bridge. The range of values is 0 to 61,440, in multiples of 4096. |
The default priority level is 32768.
Use the priority command to set the priority of the bridge (0 to 61,440). The lower the priority of the bridge, the more likely it is to be elected as the root bridge.
In the Spanning Tree Protocol, the bridge identifier consists of the bridge MAC address and the bridge priority. These attributes can optionally be set by the bridge-mac-address command (in bridge configuration mode) and the priority command, respectively.
An example of the bridge priority follows:
[local]Redback(config-bridge-stp)#priority 8192
priority priority
no priority
Configures the Virtual Router Redundancy Protocol (VRRP) election priority for the backup virtual router.
VRRP configuration
priority |
Priority setting for the backup virtual router. The range of values is 1 to 254. |
The priority is set to 100.
Use the priority command to configure the VRRP priority for the backup virtual router.
Use the no form of this command to return the priority setting to its default value.
The following example configures VRRP backup routers for two separate routers, Router_A and Router_B, on the same LAN. Both VRRP backup routers have the same virtual ID, 2. The VRRP backup router on Router_A, which has a priority of 100, is preferred over the VRRP backup router on Router_B, which has a priority of 200.
The configuration for Router_A is as follows:
[local]Router_A(config)#context local [local]Router_A(config-ctx)#interface foo [local]Router_A(config-if)#ip address 1.1.1.100/24 secondary [local]Router_A(config-if)#vrrp 2 backup [local]Router_A(config-vrrp)#virtual-address 1.1.1.111 [local]Router_A(config-vrrp)#priority 100
The configuration for Router_B is as follows:
[local]Router_B(config)#context local [local]Router_B(config-ctx)#interface foo [local]Router_B(config-if)#ip address 1.1.1.200/24 secondary [local]Router_B(config-if)#vrrp 2 backup [local]Router_B(config-vrrp)#virtual-address 1.1.1.111 [local]Router_B(config-vrrp)#priority 200
privilege mode [inherit] level level command
{no | default} privilege mode command
Assigns a different privilege level to the specified command.
global configuration
mode |
Mode of the command. |
inherit |
Optional. Assigns the specified privilege level to all keywords that follow the last keyword specified in the command argument. |
level level |
Minimum privilege level required to generate the specified command. The range of values is 0 to 15. |
command |
Command keyword (or keywords). |
For the default minimum privilege level, see the individual commands. In general, most exec mode commands require privilege level 3, and most configuration mode commands require privilege level 10.
Use the privilege command to assign a different privilege level to a specific command or set of commands.
Use the inherit keyword to modify the privilege level of all commands that begin with one or more keywords within a particular mode. For example, to modify all commands that begin with the snmp keyword (snmp server, snmp target, and so on) in global configuration mode, specify configuration for the mode argument, the inherit keyword, and snmp for the command argument; the command appears as follows:
[local]Redback(config)#privilege config inherit snmp
If you are an administrator at privilege level 15, you can determine the privilege level of any given command by recursively applying the enable and show ? commands at level 15, level 14, level 13, and so on. Initially, all commands at privilege level 15 and lower are listed, then all commands at privilege level 14 and lower, and do on. Be aware that this method yields the current privilege levels, which could be different from the default privilege levels.
Use the no or default form of this command to return a command to the default privilege level.
The following example assigns the minimum privilege level to the abort and commit commands (in exec mode) to 15:
[local]Redback(config)#privilege exec abort level 15 [local]Redback(config)#privilege exec commit level 15
The following example assigns the minimum privilege level, 12, to all global configuration mode commands that start with the snmp keyword:
[local]Redback(config)#privilege configuration inherit level 12 snmp
privilege max level
default fault privilege max
Specifies the maximum privilege level for the administrator.
administrator configuration
level |
Maximum privilege level for an administrator. The range of values is 0 to 15; the default value is 15. |
The maximum privilege level is 15.
Use the privilege max command to specify the maximum privilege level for the administrator.
Using the enable command (in exec mode), an administrator can change the privilege level of the current exec session up to the maximum privilege level specified by this command for the administrator.
Use the default form of this command to return the maximum privilege level to the default value.
The following command configures administrator fred to a maximum privilege level of 13:
[local]Redback(config-ctx)#administrator fred [local]Redback(config-administrator)#privilege max 13
privilege start level
default privilege start
Specifies the initial privilege level for exec sessions initiated by an administrator.
administrator configuration
level |
Initial privilege level for exec sessions initiated by an administrator. The range of values is 0 to 15; the default value is 6. |
The initial privilege level is set to 6.
Use the privilege start command to specify the initial privilege level for any exec session initiated by the administrator.
When an administrator logs on to the system, the exec session runs at the initial privilege level specified by this command for the administrator.
Use the default form of this command to return the initial privilege level for an administrator to the default value.
The following command configures administrator fred with an initial privilege level of 11:
[local]Redback(config-ctx)#administrator fred [local]Redback(config-administrator)#privilege start 11
probablecause probable-cause-value
no probablecause probable-cause-value
Identifies the probable cause of the event as defined by IANAItuProbableCause in IANA-ITU-ALARM-MIB.
probable-cause-value |
Value from 1–1,024, based on IANA ITU ALARM-MIB. See Usage Guidelines for values for this argument |
None
Identifies the probable cause of the event as defined by IANAItuProbableCause in ASNA-ITU-ALARM-MIB. The value identifies the event type. The following are possible values for the probable-cause-value argument:
1—aIS
2—callSetUpFailure
3—degradedSignal
4—farEndReceiverFailure
5—framingError
6—lossOfFrame
7—lossOfPointer
8—lossOfSignal
9—payloadTypeMismatch
10—transmissionError
11—remoteAlarmInterface
12—excessiveBER
13—pathTraceMismatch
14—unavailable
15—signalLabelMismatch
16—lossOfMultiFrame
17—receiveFailure
18—transmitFailure
19—modulationFailure
20—demodulationFailure
21—broadcastChannelFailure
22—connectionEstablishmentError
23—invalidMessageReceived
24—localNodeTransmissionError
25—remoteNodeTransmissionError
26—routingFailure
51—backplaneFailure
52—dataSetProblem
53—equipmentIdentifierDuplication
54—externalIFDeviceProblem
55—lineCardProblem
56—multiplexerProblem
57—nEIdentifierDuplication
58—powerProblem
59—processorProblem
60—protectionPathFailure
61—receiverFailure
62—replaceableUnitMissing
63—replaceableUnitTypeMismatch
64—synchronizationSourceMismatch
65—terminalProblem
66—timingProblem
67—transmitterFailure
68—trunkCardProblem
69—replaceableUnitProblem
70—realTimeClockFailure
71—antennaFailure
72—batteryChargingFailure
73—diskFailure
74—frequencyHoppingFailure
75—iODeviceError
76—lossOfSynchronisation
77—lossOfRedundancy
78—powerSupplyFailure
79—signalQualityEvaluationFailure
80—tranceiverFailure
81—protectionMechanismFailure
82—protectingResourceFailure
101—airCompressorFailure
102—airConditioningFailure
103—airDryerFailure
104—batteryDischarging
105—batteryFailure
106—commercialPowerFailure
107—coolingFanFailure
108—engineFailure
109—fireDetectorFailure
110—fuseFailure
111—generatorFailure
112—lowBatteryThreshold
113—pumpFailure
114—rectifierFailure
115—rectifierHighVoltage
116—rectifierLowFVoltage
117—ventilationsSystemFailure
118—enclosureDoorOpen
119—explosiveGas120—fire
121—flood
122—highHumidity
123—highTemperature
124—highWind
125—iceBuildUp
126—intrusionDetection
127—lowFuel
128—lowHumidity
129—lowCablePressure
130—lowTemperatue
131—lowWater
132—smoke
133—toxicGas
134—coolingSystemFailure
135—externalEquipmentFailure
136—externalPointFailure
151—storageCapacityProblem
152—memoryMismatch
153—corruptData
154—outOfCPUCycles
155—sfwrEnvironmentProblem
156—sfwrDownloadFailure
157—lossOfRealTimel
158—applicationSubsystemFailure
159—configurationOrCustomisationError
160—databaseInconsistency
161—fileError
162—outOfMemory
163—softwareError
164—timeoutExpired
165—underlayingResourceUnavailable
166—versionMismatch
201—bandwidthReduced
202—congestion
203—excessiveErrorRate
204—excessiveResponseTime
205—excessiveRetransmissionRate
206—reducedLoggingCapability
207—systemResourcesOverload
500—adapterError
501—applicationSubsystemFailture
502—bandwidthReducedX733
503—callEstablishmentError
504—communicationsProtocolError
505—communicationsSubsystemFailure
506—configurationOrCustomizationError
507—congestionX733
508—coruptData
509—cpuCyclesLimitExceeded
510—dataSetOrModemError
511—degradedSignalX733
512—dteDceInterfaceError
513—enclosureDoorOpenX733
514—equipmentMalfunction
515—excessiveVibration
516—fileErrorX733
517—fireDetected
518—framingErrorX733
519—heatingVentCoolingSystemProblem
520—humidityUnacceptable
521—inputOutputDeviceError
522—inputDeviceError
523—lanError
524—leakDetected
525—localNodeTransmissionErrorX733
526—lossOfFrameX733
527—lossOfSignalX733
528—materialSupplyExhausted
529—multiplexerProblemX733
530—outOfMemoryX733
531—ouputDeviceError
532—performanceDegraded
533—powerProblems
534—pressureUnacceptable
535—processorProblems
536—pumpFailureX733
537—queueSizeExceeded
538—receiveFailureX733
539—receiverFailureX733
540—remoteNodeTransmissionErrorX733
541—resourceAtOrNearingCapacity
542—responseTimeExecessive
543—retransmissionRateExcessive
544—softwareErrorX733
545—softwareProgramAbnormallyTerminated
546—softwareProgramError
547—storageCapacityProblemX733
548—temperatureUnacceptable
549—thresholdCrossed
550—timingProblemX733
551—toxicLeakDetected
552—transmitFailureX733
553—transmiterFailure
554—underlyingResourceUnavailable
555—versionMismatchX733
600—authenticationFailure
601—breachOfConfidentiality
602—cableTamper
603—delayedInformation
604—denialOfService
605—duplicateInformation
606—informationMissing
607—informationModificationDetectede
608—informationOutOfSequence
609—keyExpired
610—nonRepudiationFailure
611—outOfHoursActivity
612—outOfServic
613—proceduralError
614—unauthorizedAccessAttempt
615—unexpectedInformation
1024—other
Use the no form of this command to remove the probable cause of the event.
The following example shows how to configure the probable cause for the alarm model event as thresholdCrossed (549).
[local]jazz#config [local]jazz(config)#snmp alarm model 1 state clear [local]jazz(config-snmp-alarmmodel)#probablecause 549 [local]jazz(config-snmp-alarmmodel)#exit
process coredump {proc-name | - proc-id}
Interrupts the specified process and saves the core dump file.
proc-name |
Process name for which a core dump is to be generated. The value of the proc-name argument can be any one of the keywords listed in Table 3. |
- proc-id |
Dash (-) followed by the process identification number (PID). The range of values is 1 to 65,535. |
None
Use the process coredump command to interrupt a specified process and save the core dump file. You can specify the process either by its process name or PID.
Caution! | ||
Risk of data loss. Generating a core dump interrupts the specified
process for a brief period, the length of which depends on the size
of the binary and the amount of memory used by the process, before
the process is automatically restarted by the system. To reduce the
risk, do not initiate a core dump while the system is experiencing
heavy traffic.
|
Caution! | ||
Risk of system crash. Allow sufficient time after entering the process coredump command to allow the SmartEdge router to stabilize. Monitor the SmartEdge router and wait for it to stabilize
before entering the process restart command. Contact
technical support before you start and restart multiple processes.
|
For an overview of core dumps, crash files, and a guide to their management, see Performing Core Dump and Crash File Management Tasks in Managing Files for additional information.
Table 3 lists the keywords for the processes supported by this command.
Keyword |
Process |
---|---|
aaad |
authentication, authorization, and accounting (AAA) process |
arp |
Address Resolution Protocol (ARP) process |
atm |
Asynchronous Transfer Mode (ATM) process |
bgp |
Border Gateway Protocol (BGP) process |
bridge |
bridge process |
clips |
clientless IP service selection process |
cls |
Classifier Manager process |
csm |
Controller State Manager (CSM) process |
cpustats |
Display CPU statistics |
dhcp |
Dynamic Host Configuration Protocol (DHCP) relay/proxy process |
dhelperd |
DHCP helper daemon |
dlm |
Download Manager (DLM) process |
dns |
Domain Name System (DNS) process |
dot1q |
802.1Q encapsulation process(1) |
flowd |
flow process(2) |
fr |
Frame Relay process (3) |
gsmp |
General Switch Management Protocol (GSMP) process |
hr |
HTTP redirect process |
igmp |
Internet Group Management Protocol (IGMP) process |
isis |
Intermediate System-to-Intermediate System (IS-IS) process |
ism |
Interface and Circuit State Manager (ISM) process |
l2tp |
Layer 2 Tunneling Protocol (L2TP) process |
ldp |
Label Distribution Protocol (LDP) process |
lg |
link group (LG) process |
lm |
Label Manager (LM) process |
mip |
Mobile IP process |
mpls_static |
Multiprotocol Label Switching (MPLS) static process |
msdp |
Multicast Source Discovery Protocol (MSDP) process |
nat |
IP Network Address Translation (NAT) process |
nd |
neighbor discovery (ND) process |
netopd |
NetOp process daemon |
ntp |
Network Time Protocol (NTP) process |
odd |
on-demand diagnostics (ODD) process |
ospf |
Open Shortest Path First (OSPF) protocol process |
ospf3 |
OSPF Version 3 (OSPF3) protocol process |
ped_parse |
process execution descriptor (PED) parse process |
pem |
privacy-enhanced mail (PEM) process |
pim |
Protocol Independent Multicast (PIM) process |
ppaslog |
Packet Processing ASIC (PPA) syslog process |
ppp |
Point-to-Point Protocol (PPP) process |
pppoe |
PPP over Ethernet (PPPoE) process |
qos |
quality of service (QoS) process |
rcm |
Router Configuration Manager (RCM) process |
rib |
Routing Information Base (RIB) process |
rip |
Routing Information Protocol (RIP) process |
rpm |
Routing Policy Manager (RPM) process |
rsvp |
Resource Reservation Protocol Traffic Engineering (RSVP-TE) process |
snmp |
Simple Network Management Protocol (SNMP) process |
static |
static routing process |
stats |
statistics process |
sysmon |
system monitor process |
tap |
Lawful Intercept (LI) process |
tunnel |
tunnel management process |
vrrp |
Virtual Router Redundancy Protocol (VRRP) process |
xcd |
cross-connect process daemon |
(1) The SmartEdge 100 router
does not support 802.1Q.
(2) Not all controller cards support flow.
(3) The SmartEdge 100 router does
not support Frame Relay.
The following example initiates a core dump and creates a crash file for the BGP process:
[local]Redback#process coredump bgp
process restart proc-name [delay]
Restarts a process that has been stopped.
proc-name |
Process to be restarted. The value of the proc-name argument can be any one of the keywords listed in Table 4. |
delay |
Optional. Delay, in seconds, before a process is restarted. The range of values is 0 to 4,294,967,295; the default value is 2. |
The default for the optional delay is two seconds.
Use the process restart command to restart a process that has been stopped.
Table 4 lists the keywords for the processes supported by this command.
Keyword |
Process |
---|---|
aaad |
authentication, authorization, and accounting (AAA) process |
arp |
Address Resolution Protocol (ARP) process |
atm |
Asynchronous Transfer Mode (ATM) process |
bgp |
Border Gateway Protocol (BGP) process |
bridge |
bridge process |
clips |
clientless IP service selection process |
cls |
Classifier Manager process |
csm |
Controller State Manager (CSM) process |
cpustats |
Display CPU statistics |
dhcp |
Dynamic Host Configuration Protocol (DHCP) relay/proxy process |
dhelperd |
DHCP helper daemon |
dlm |
Download Manager (DLM) process |
dns |
Domain Name System (DNS) process |
dot1q |
802.1Q encapsulation process(1) |
flowd |
flow process(2) |
fr |
Frame Relay process (3) |
gsmp |
General Switch Management Protocol (GSMP) process |
hr |
HTTP redirect process |
igmp |
Internet Group Management Protocol (IGMP) process |
isis |
Intermediate System-to-Intermediate System (IS-IS) process |
ism |
Interface and Circuit State Manager (ISM) process |
l2tp |
Layer 2 Tunneling Protocol (L2TP) process |
ldp |
Label Distribution Protocol (LDP) process |
lg |
link group (LG) process |
lm |
Label Manager (LM) process |
mip |
Mobile IP process |
mpls_static |
Multiprotocol Label Switching (MPLS) static process |
msdp |
Multicast Source Discovery Protocol (MSDP) process |
nat |
IP Network Address Translation (NAT) process |
nd |
neighbor discovery (ND) process |
netopd |
NetOp process daemon |
ntp |
Network Time Protocol (NTP) process |
odd |
on-demand diagnostics (ODD) process |
ospf |
Open Shortest Path First (OSPF) protocol process |
ospf3 |
OSPF Version 3 (OSPF3) protocol process |
ped_parse |
process execution descriptor (PED) parse process |
pem |
privacy-enhanced mail (PEM) process |
pim |
Protocol Independent Multicast (PIM) process |
ppaslog |
Packet Processing ASIC (PPA) syslog process |
ppp |
Point-to-Point Protocol (PPP) process |
pppoe |
PPP over Ethernet (PPPoE) process |
qos |
quality of service (QoS) process |
rcm |
Router Configuration Manager (RCM) process |
rib |
Routing Information Base (RIB) process |
rip |
Routing Information Protocol (RIP) process |
rpm |
Routing Policy Manager (RPM) process |
rsvp |
Resource Reservation Protocol Traffic Engineering (RSVP-TE) process |
snmp |
Simple Network Management Protocol (SNMP) process |
static |
static routing process |
stats |
statistics process |
sysmon |
system monitor process |
tap |
Lawful Intercept (LI) process |
tunnel |
tunnel management process |
vrrp |
Virtual Router Redundancy Protocol (VRRP) process |
xcd |
cross-connect process daemon |
(1) The SmartEdge 100 router
does not support 802.1Q.
(2) Not all controller cards support flow.
(3) The SmartEdge 100 router does
not support Frame Relay.
The following example restarts the BGP process after a five-minute delay (300 seconds):
[local]Redback#process restart bgp 300
process set proc-name {heart-beat {on | off} | kill-time seconds | max-crashes num-crashes [within seconds] | spawn-time [seconds]}
Sets process management parameters.
proc-name |
Process for which you are setting management parameters. The value of the proc-name argument can be any one of the keywords listed in Table 5. |
heart-beat |
Specifies that a heartbeat setting follows. |
on |
Turns the process heartbeat on. |
off |
Turns the process heartbeat off. |
kill-time seconds |
Number of seconds from issuing the process set command after which the Process Manager (PM) kills the specified process. The range of values is 1 to 429,496,729. |
max-crashes num-crashes |
Maximum number of crashes allowed within the time interval specified by the within seconds construct. The range of values is 0 to 10; the default value is 5. |
within seconds |
Optional. Number of seconds within which the maximum number of crashes is allowed. If not specified, the system uses the default value of 86,400 (24 hours). |
spawn-time |
Specifies that a spawn time setting follows. If used without the optional seconds argument, sets the spawn time to the default value of two seconds. |
seconds |
Optional with the spawn-time keyword. Number of seconds delay between the crash of a process and the subsequent spawn by the PM. The range of values is 1 to 300; the default value is 2. |
The heartbeat is on; the maximum number of crashes allowed is five per process within a 24 hour period; the spawn time is two seconds.
Use the process set command to set process management parameters including whether the heartbeat is turned on or off, the kill time, the maximum number of crashes allowed within a configurable period of time, and the amount of time between the crash of a process and the subsequent spawn by the PM (spawn time).
Table 5 lists the keywords for the processes supported by this command.
Keyword |
Process |
---|---|
aaad |
authentication, authorization, and accounting (AAA) process |
arp |
Address Resolution Protocol (ARP) process |
atm |
Asynchronous Transfer Mode (ATM) process |
bgp |
Border Gateway Protocol (BGP) process |
bridge |
bridge process |
clips |
clientless IP service selection process |
cls |
Classifier Manager process |
csm |
Controller State Manager (CSM) process |
cpustats |
Display CPU statistics |
dhcp |
Dynamic Host Configuration Protocol (DHCP) relay/proxy process |
dhelperd |
DHCP helper daemon |
dlm |
Download Manager (DLM) process |
dns |
Domain Name System (DNS) process |
dot1q |
802.1Q encapsulation process(1) |
flowd |
flow process(2) |
fr |
Frame Relay process (3) |
gsmp |
General Switch Management Protocol (GSMP) process |
hr |
HTTP redirect process |
igmp |
Internet Group Management Protocol (IGMP) process |
isis |
Intermediate System-to-Intermediate System (IS-IS) process |
ism |
Interface and Circuit State Manager (ISM) process |
l2tp |
Layer 2 Tunneling Protocol (L2TP) process |
ldp |
Label Distribution Protocol (LDP) process |
lg |
link group (LG) process |
lm |
Label Manager (LM) process |
mip |
Mobile IP process |
mpls_static |
Multiprotocol Label Switching (MPLS) static process |
msdp |
Multicast Source Discovery Protocol (MSDP) process |
nat |
IP Network Address Translation (NAT) process |
nd |
neighbor discovery (ND) process |
netopd |
NetOp process daemon |
ntp |
Network Time Protocol (NTP) process |
odd |
on-demand diagnostics (ODD) process |
ospf |
Open Shortest Path First (OSPF) protocol process |
ospf3 |
OSPF Version 3 (OSPF3) protocol process |
ped_parse |
process execution descriptor (PED) parse process |
pem |
privacy-enhanced mail (PEM) process |
pim |
Protocol Independent Multicast (PIM) process |
ppaslog |
Packet Processing ASIC (PPA) syslog process |
ppp |
Point-to-Point Protocol (PPP) process |
pppoe |
PPP over Ethernet (PPPoE) process |
qos |
quality of service (QoS) process |
rcm |
Router Configuration Manager (RCM) process |
rib |
Routing Information Base (RIB) process |
rip |
Routing Information Protocol (RIP) process |
rpm |
Routing Policy Manager (RPM) process |
rsvp |
Resource Reservation Protocol Traffic Engineering (RSVP-TE) process |
snmp |
Simple Network Management Protocol (SNMP) process |
static |
static routing process |
stats |
statistics process |
sysmon |
system monitor process |
tap |
Lawful Intercept (LI) process |
tunnel |
tunnel management process |
vrrp |
Virtual Router Redundancy Protocol (VRRP) process |
xcd |
cross-connect process daemon |
(1) The SmartEdge 100 router
does not support 802.1Q.
(2) Not all controller cards support flow.
(3) The SmartEdge 100 router does
not support Frame Relay.
The heartbeat is a message that each process sends to the PM to identify itself as an active process. If the heartbeat ceases, the PM considers the process a candidate for automatic restart. It can be useful for debugging processes to turn the heartbeat off so that a hung process is not restarted automatically by the PM.
The following example sets process management parameters for the BGP process:
[local]Redback#process set bgp kill-time 100 [local]Redback#process set bgp max-crashes 3 within 43200 [local]Redback#process set bgp spawn-time 10
process start proc-name
Instructs the Process Manager (PM) to start the specified process.
proc-name |
Process to be started. The value of the proc-name argument can be any one of the keywords listed in Table 6. |
None
Use the process start command to instruct the PM to start the specified process.
Caution! | ||
Risk of system crash. If more than one process has been stopped,
you must restart each process individually, monitoring the SmartEdge router and waiting for it to
stabilize before trying to restart the stopped process. Contact technical
support before stopping and restarting multiple processes.
|
Table 6 lists the keywords for the processes supported by this command.
Keyword |
Process |
---|---|
aaad |
authentication, authorization, and accounting (AAA) process |
arp |
Address Resolution Protocol (ARP) process |
atm |
Asynchronous Transfer Mode (ATM) process |
bgp |
Border Gateway Protocol (BGP) process |
bridge |
bridge process |
clips |
clientless IP service selection process |
cls |
Classifier Manager process |
csm |
Controller State Manager (CSM) process |
cpustats |
Display CPU statistics |
dhcp |
Dynamic Host Configuration Protocol (DHCP) relay/proxy process |
dhelperd |
DHCP helper daemon |
dlm |
Download Manager (DLM) process |
dns |
Domain Name System (DNS) process |
dot1q |
802.1Q encapsulation process(1) |
flowd |
flow process(2) |
fr |
Frame Relay process (3) |
gsmp |
General Switch Management Protocol (GSMP) process |
hr |
HTTP redirect process |
igmp |
Internet Group Management Protocol (IGMP) process |
isis |
Intermediate System-to-Intermediate System (IS-IS) process |
ism |
Interface and Circuit State Manager (ISM) process |
l2tp |
Layer 2 Tunneling Protocol (L2TP) process |
ldp |
Label Distribution Protocol (LDP) process |
lg |
link group (LG) process |
lm |
Label Manager (LM) process |
mip |
Mobile IP process |
mpls_static |
Multiprotocol Label Switching (MPLS) static process |
msdp |
Multicast Source Discovery Protocol (MSDP) process |
nat |
IP Network Address Translation (NAT) process |
nd |
neighbor discovery (ND) process |
netopd |
NetOp process daemon |
ntp |
Network Time Protocol (NTP) process |
odd |
on-demand diagnostics (ODD) process |
ospf |
Open Shortest Path First (OSPF) protocol process |
ospf3 |
OSPF Version 3 (OSPF3) protocol process |
ped_parse |
process execution descriptor (PED) parse process |
pem |
privacy-enhanced mail (PEM) process |
pim |
Protocol Independent Multicast (PIM) process |
ppaslog |
Packet Processing ASIC (PPA) syslog process |
ppp |
Point-to-Point Protocol (PPP) process |
pppoe |
PPP over Ethernet (PPPoE) process |
qos |
quality of service (QoS) process |
rcm |
Router Configuration Manager (RCM) process |
rib |
Routing Information Base (RIB) process |
rip |
Routing Information Protocol (RIP) process |
rpm |
Routing Policy Manager (RPM) process |
rsvp |
Resource Reservation Protocol Traffic Engineering (RSVP-TE) process |
snmp |
Simple Network Management Protocol (SNMP) process |
static |
static routing process |
stats |
statistics process |
sysmon |
system monitor process |
tap |
Lawful Intercept (LI) process |
tunnel |
tunnel management process |
vrrp |
Virtual Router Redundancy Protocol (VRRP) process |
xcd |
cross-connect process daemon |
(1) The SmartEdge 100 router
does not support 802.1Q.
(2) Not all controller cards support flow.
(3) The SmartEdge 100 router does
not support Frame Relay.
The following example starts the BGP process:
[local]Redback#process start bgp
process stop proc-name
Stops the specified process.
exec (10)
proc-name |
Process to be stopped. The value of the proc-name argument can be any one of the keywords listed in Table 7. |
None
Use the process stop command to the specified process.
Table 7 lists the keywords for the processes supported by this command.
Keyword |
Process |
---|---|
aaad |
authentication, authorization, and accounting (AAA) process |
arp |
Address Resolution Protocol (ARP) process |
atm |
Asynchronous Transfer Mode (ATM) process |
bgp |
Border Gateway Protocol (BGP) process |
bridge |
bridge process |
clips |
clientless IP service selection process |
cls |
Classifier Manager process |
csm |
Controller State Manager (CSM) process |
cpustats |
Display CPU statistics |
dhcp |
Dynamic Host Configuration Protocol (DHCP) relay/proxy process |
dhelperd |
DHCP helper daemon |
dlm |
Download Manager (DLM) process |
dns |
Domain Name System (DNS) process |
dot1q |
802.1Q encapsulation process(1) |
flowd |
flow process(2) |
fr |
Frame Relay process (3) |
gsmp |
General Switch Management Protocol (GSMP) process |
hr |
HTTP redirect process |
igmp |
Internet Group Management Protocol (IGMP) process |
isis |
Intermediate System-to-Intermediate System (IS-IS) process |
ism |
Interface and Circuit State Manager (ISM) process |
l2tp |
Layer 2 Tunneling Protocol (L2TP) process |
ldp |
Label Distribution Protocol (LDP) process |
lg |
link group (LG) process |
lm |
Label Manager (LM) process |
mip |
Mobile IP process |
mpls_static |
Multiprotocol Label Switching (MPLS) static process |
msdp |
Multicast Source Discovery Protocol (MSDP) process |
nat |
IP Network Address Translation (NAT) process |
nd |
neighbor discovery (ND) process |
netopd |
NetOp process daemon |
ntp |
Network Time Protocol (NTP) process |
odd |
on-demand diagnostics (ODD) process |
ospf |
Open Shortest Path First (OSPF) protocol process |
ospf3 |
OSPF Version 3 (OSPF3) protocol process |
ped_parse |
process execution descriptor (PED) parse process |
pem |
privacy-enhanced mail (PEM) process |
pim |
Protocol Independent Multicast (PIM) process |
ppaslog |
Packet Processing ASIC (PPA) syslog process |
ppp |
Point-to-Point Protocol (PPP) process |
pppoe |
PPP over Ethernet (PPPoE) process |
qos |
quality of service (QoS) process |
rcm |
Router Configuration Manager (RCM) process |
rib |
Routing Information Base (RIB) process |
rip |
Routing Information Protocol (RIP) process |
rpm |
Routing Policy Manager (RPM) process |
rsvp |
Resource Reservation Protocol Traffic Engineering (RSVP-TE) process |
snmp |
Simple Network Management Protocol (SNMP) process |
static |
static routing process |
stats |
statistics process |
sysmon |
system monitor process |
tap |
Lawful Intercept (LI) process |
tunnel |
tunnel management process |
vrrp |
Virtual Router Redundancy Protocol (VRRP) process |
xcd |
cross-connect process daemon |
(1) The SmartEdge 100 router
does not support 802.1Q.
(2) Not all controller cards support flow.
(3) The SmartEdge 100 router does
not support Frame Relay.
Caution! | ||
Risk of system crash. If more than one process has been stopped,
you must restart each process individually, monitoring the SmartEdge router and waiting for it to
stabilize before trying to restart the stopped process. Contact technical
support before stopping and restarting multiple processes.
|
Caution! | ||
Risk of data loss. The process stop command causes
the specified process to terminate and the services provided by the
process to become unavailable until the process is restarted using
the process start command. To reduce the risk, do not
stop a process unless you intend to restart the process immediately.
|
The following example stops the BGP process:
[local]Redback#process stop bgp
profile prof-name
no profile
Assigns an existing named profile to the subscriber.
prof-name |
Existing profile. |
The default profile is assigned to the subscriber.
Use the profile command to assign an existing named profile to the subscriber.
If this subscriber will be a user of clientless IP service selection (CLIPS), adhere to the following guidelines:
Use the no form of this command to assign the default profile to the subscriber.
The following example assigns the existing profile, hi-perf, to subscriber joe in the isp1 context:
[local]Redback(config)#context ips1 [isp1]Redback(config-ctx)#subscriber name joe [isp1]Redback(config-sub)#profile hi-perf
profile prof-name [pw-id pw-num | pw-name pw-name]
no profile prof-name
In VPLS configuration mode, applies an existing Virtual Private LAN Services (VPLS) profile to a VPLS instance.
In port pseudowire configuration mode, applies an existing port pseudowire profile to a pseudowire connection.
prof-name |
Name of the VPLS profile that contains the neighbor attributes for establishing the pseudowires (maximum 40 characters). |
pw-id pw-num |
Optional. Pseudowire number. The value of the pw-num argument is a 4-byte number. The remote provider edge (PE) device uses the pseudowire number and the local IP address to identify the pseudowire and the associated VPLS instance. |
pw-name pw-name |
Optional. Pseudowire name. The remote PE device uses the pseudowire name and the local IP address to identify the pseudowire and the associated VPLS instance. |
None
Use the profile command to apply an existing VPLS profile to a VPLS instance or an existing port pseudowire profile to port pseudowire connection. When a VPLS profile is applied, a VPLS peer instance is created for each neighbor defined in the profile, and a pseudowire connection is established using the attributes defined for the neighbor.
A VPLS profile must be configured using the vpls profile command (in global configuration mode) before it can be applied.
A port pseudowire profile must be configured using the port pseudo-wire profile command (in global configuration mode) before it can be applied.
Use the pw-id pw-num construct or pw-name pw-name construct to optionally specify a pseudowire ID (number or name) to signal the ID for pseudowires to the neighbor defined in the profile. If a pseudowire ID is not configured for a VPLS profile, then the VPLS instance-level default pseudowire ID is used.
Multiple VPLS profiles can be applied to the same VPLS instance. If two or more profiles reference the same PE (same IP address), then the neighbor from the first profile is used. The same profile cannot be applied multiple times even if the pseudowire IDs are different.
Use the no form of this command to delete a VPLS or port pseudowire profile.
The following example applies the foo VPLS profile to the VPLS instance on the to-pe4 bridge:
[local]Redback#config [local]Redback(config)#context local [local]Redback(config-ctx)#bridge to-pe4 [local]Redback(config-bridge)#vpls [local]Redback(config-vpls)#profile foo pw-id 20 [local]Redback(config-vpls)#
The following example applies the foo port pseudowire profile name and port pseudowire profile ID 20 to the current port pseudowire connection:
[local]Redback#config [local]Redback(config)#port pseudowire connect1 ethernet [local]Redback(config-port)#profile foo pw-id 20 [local]Redback(config-port)#
propagate qos from ethernet [class-map map-name]
no propagate qos from ethernet [class-map map-name]
For incoming packets, propagates Ethernet 802.1p user priority bits to packet descriptor (PD) quality of service (QoS) bits.
dot1q profile configuration
class-map map-name |
Optional. Name of an ingress Ethernet classification map for mapping Ethernet 802.1p user priority bits to quality of service (QoS) packet descriptor (PD) values. |
Ethernet 802.1p user priority bits are not propagated to DSCP bits.
Use the propagate qos from ethernet command to propagate Ethernet 802.1p user priority bits to PD QoS bits.
You can use the qos class-map command to define an optional mapping schema. If you specify the class-map map-name construct for the propagate qos from ethernet command, only the PD QoS values are affected. If the class-map map-name construct is not specified, the Ethernet 802.1p bits are also copied to the priority bits of the DSCP field in the IP header.
Use the no form of this command to disable the propagation of Ethernet 802.1p bits to PD QoS bits.
The following example propagates Ethernet 802.1p user priority bits to DSCP bits for incoming packets for all 802.1Q PVCs that reference the 802.1Q profile, 8021p-on:
[local]Redback(config)#dot1q profile 8021p-on [local]Redback(config-dot1q-profile)#propagate qos from ethernet
propagate qos from ip class-map map-name
no propagate qos from ip class-map map-name
Specifies a custom value mapping for propagating the Differentiated Services Code Point (DSCP) bits in the IP packet header to the packet descriptor (PD) priority bits for incoming IP packets.
class-map map-name |
Name of the schema for mapping DSCP bits to PD priority bits. |
DSCP values are copied to the PD values using a default mapping.
Use the propagate qos from ip command to specify a custom value mapping for propagating the DSCP bits in the IP packet header to the PD priority bits for incoming IP packets. The DSCP bits are modified in the received IP packet according to the specified classification map. In subscriber configuration mode, this command allows you to customize the mapping for traffic received on a specific subscriber session. In interface configuration mode, this command allows you to customize the mapping for all IP traffic received through the interface. The SmartEdge router propagates classification values and marks packets before it applies any metering policy.
Custom classification mappings configured for either a subscriber or an interface affect Layer 3 (IP-routed) circuits only.
Use the qos class-map command with the ip in keywords (in global configuration mode) to define a mapping schema to be referenced by the propagate qos from ip command.
You can use the propagate qos from subscriber command (in L2TP peer configuration mode) to copy DSCP bits to PD values for Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC) sessions, then use the propagate qos from ip command to specify a custom value mapping.
Use the no form of this command to remove a customized DSCP-to-PD mapping.
The following example customizes the propagation of IP header DSCP values to PD values for incoming packets of all subscriber sessions in the local context:
[local]Redback(config-sub)#qos class-map ip-to-pd ip in [local]Redback(config-class-map)#ip df to qos af43 [local]Redback(config-class-map)#exit [local]Redback(config)#context local [local]Redback(config-ctx)#subscriber default [local]Redback(config-sub)#propagate qos from ip class-map ip-to-pd
propagate qos from l2tp [class-map map-name]
no propagate qos from l2tp [class-map map-name]
If no classification map is specified, propagates the packet descriptor (PD) priority bits to the Differentiated Services Code Point (DSCP) bits of the inner (subscriber) IP header for incoming Layer 2 Tunneling Protocol (L2TP) packets when the SmartEdge router is configured as an L2TP network server (LNS).
L2TP peer configuration (default peer only)
class-map map-name |
Optional. Name of an ingress IP classification map for mapping DSCP values in the IP packet header to quality of service (QoS) PD values. |
The DSCP bits in the incoming L2TP IP packet headers are not propagated to the DSCP bits in subscriber IP packet headers.
Use the propagate qos from l2tp command to propagate the PD priority bits to the DSCP bits of the inner (subscriber) IP header if no classification map is specified for incoming L2TP packets when the SmartEdge router is configured as an LNS. Propagation occurs after the outer IP DSCP bits have been propagated to the PD priority bits as part of IP forwarding. If you specify a classification map, this command customizes the default mapping from the outer IP header DSCP value to the PD QoS value and leaves the inner IP header DSCP value unmodified.
You can use the qos class-map command to define an optional mapping schema. If you do not specify the class-map map-name construct with the propagate qos from l2tp command, the SmartEdge router overwrites the value in the inner IP header with the DSCP value from the received outer IP header. If you specify the class-map map-name construct, the SmartEdge router customizes the default mapping from the outer IP header DSCP value to the PD QoS value and leaves the inner IP header DSCP value unmodified.
L2TP tunnels are User Datagram Protocol (UDP)/IP-encapsulated circuits that carry subscriber-based IP traffic encapsulated in Point-to-Point (PPP) sessions between routers. The LNS is the IP termination point for subscriber traffic. DSCP bits from the L2TP IP packet header can be propagated into subscriber traffic.
Use the no form of this command to disable the propagation of DSCP bits to the inner (subscriber) IP header or to remove the customized propagation to the QoS PD value.
The following example propagates DSCP bits from outer L2TP IP packet headers to DSCP bits in inner IP packet headers:
[local]Redback(config-ctx)#l2tp-peer default [local]Redback(config-l2tp)#propagate qos from l2tp
propagate qos from mpls [class-map map-name] [l2vpn class-map map-name]
no propagate qos from mpls [class-map map-name] [l2vpn class-map map-name]
Enables mapping Multiprotocol Label Switching (MPLS) experimental (EXP) bits to Differentiated Services Code Point (DSCP) bits in the IP header or enables customized mapping of EXP to packet descriptor (PD) quality of service (QoS) values for incoming packets when the SmartEdge router is configured as a MPLS egress router.
MPLS router configuration
class-map map-name |
Optional. Name of the ingress MPLS classification map for mapping MPLS EXP values to QoS PD values. |
l2vpn class-map map-name |
Optional. Name of the ingress MPLS classification map for mapping packets received from Layer 2 MPLS VPNs. |
MPLS EXP bits are not mapped to DSCP bits.
Use the propagate qos from mpls command to enable mapping MPLS EXP bits to DSCP bits in the IP header or enable customized mapping of EXP to PD QoS values for incoming packets when the SmartEdge router is configured as a MPLS egress router. If the optional class-map map-name construct is not specified, the EXP bits are also copied to the priority bits of the DSCP field in the IP header.
If you specify the optional class-map map-name construct, the propagate qos from mpls command specifies a custom value mapping for MPLS EXP bits to PD values. The DSCP bits are unaffected. In this case, use the qos class-map command to define a mapping schema, then reference the schema using the class-map map-name construct. If you do not specify a Layer 2 virtual private network (L2VPN) classification map, the standard classification map applies to both Layer 2 and Layer 3 traffic.
If you specify the optional l2vpn class-map map-name construct with the class-map map-name construct, the L2VPN classification map applies to Layer 2 traffic and Layer 3 traffic uses the default 8P0D mapping schema. If you specify both the l2vpn class-map map-name construct and the class-map map-name construct, Layer 2 traffic uses the L2VPN classification map and Layer 3 traffic uses the standard classification map.
If you use the mpls use-ethernet command to perform a secondary lookup and the encapsulated packet contains no virtual LAN (VLAN) header, the PD value is determined by mapping the MPLS EXP value using the default 8P0D schema.
Use the no form of this command to disable the mapping of MPLS EXP bits to DSCP bits or remove a customized EXP-to-PD mapping.
The following example enables the mapping of MPLS EXP bits to DSCP bits for outgoing packets:
[local]Redback(config-ctx)#router mpls [local]Redback(config-mpls)#propagate qos from mpls
The following example specifies a customized mapping of MPLS EXP bits to PD values by referencing the existing MPLS ingress classification map exp-to-pd:
[local]Redback(config-ctx)#router mpls [local]Redback(config-mpls)#propagate qos from mpls class-map exp-to-pd
propagate qos from subscriber [{upstream | downstream | both}]
no propagate qos from subscriber [{upstream | downstream | both}]
For incoming packets when the SmartEdge router is configured as a Layer 2 Tunneling Protocol (L2TP) access concentrator (LAC), propagates the Differentiated Services Code Point (DSCP) bits in the subscriber’s IP packet header to the packet descriptor (PD) priority bits.
L2TP peer configuration (default peer only)
upstream |
Optional. Performs the propagation on inbound packets from the subscriber. |
downstream |
Optional. Performs the propagation on inbound packets from the L2TP network server (LNS). |
both |
Optional. Performs the propagation on inbound packets from the subscriber and inbound packets from the LNS. |
DSCP bits are not propagated from the incoming subscriber IP packet header to the PD for the subscriber IP packet.
For incoming packets when the SmartEdge router is configured as a LAC, use the propagate qos from subscriber command to propagate the DSCP bits in the subscriber’s IP packet header to the PD priority bits.
Use the upstream keyword to propagate from inbound packets from the subscriber. Use the downstream keyword to propagate from inbound packets from the network. Use the both keyword to propagate in both directions.
The SmartEdge router performs a deep packet inspection of inner IP packet headers and copies the DSCP bits in the IP header. L2TP tunnels are User Datagram Protocol (UDP)/IP-encapsulated circuits that carry subscriber-based Point-to-Point Protocol (PPP) sessions between routers. On L2TP tunnels, subscriber IP packets are encapsulated in PPP packets, which themselves are encapsulated in L2TP packets. DSCP bits can be propagated from inner IP packet headers to outer L2TP IP packet headers, and vice versa. DSCP bits are propagated between layers of encapsulated packets so that any Layer 3 device located between an LNS and a LAC can recognize and apply DSCP settings.
Use the no form of this command to disable the propagation of DSCP bits in the specified direction or, if neither keyword is specified, in both directions.
The following example propagates the DSCP bits in a subscriber IP packet header to the PD for the subscriber IP packet header in the upstream direction only:
[local]Redback(config-ctx)#l2tp-peer default [local]Redback(config-l2tp)#propagate qos from subscriber upstream
The following example propagates the DSCP bits from subscriber IP packet headers to DSCP bits in L2TP IP packet headers in both directions:
[local]Redback(config-ctx)#l2tp-peer default [local]Redback(config-l2tp)#propagate qos from subscriber
propagate qos to ethernet [class-map map-name]
no propagate qos to ethernet [class-map map-name]
Propagates packet descriptor (PD) priority values to Ethernet 802.1p user priority bits for outgoing packets.
dot1q profile configuration
class-map map-name |
Optional. Name of the egress Ethernet classification map for mapping quality of service (QoS) PD values to Ethernet 802.1p user priority bits. |
Differentiated Services Code Point (DSCP) bits are not propagated to Ethernet 802.1p user priority bits.
Use the propagate qos to ethernet command to propagate PD priority values to Ethernet 802.1p user priority bits for outgoing packets.
You can use the qos class-map command to define an optional mapping schema. If you do not specify the class-map map-name construct for the propagate qos to ethernet command, the default 8P0D mapping is used.
Use the no form of this command to disable the propagation of DSCP bits.
The following example propagates DSCP bits from IP packets to Ethernet 802.1p user priority bits for 802.1Q PVCs that reference the 802.1Q profile, 8021p-on:
[local]Redback(config)#dot1q profile 8021p-on [local]Redback(config-dot1q-profile)#propagate qos to ethernet
propagate qos to ip [class-map map-name]
no propagate qos to ip [class-map map-name]
Propagates packet descriptor (PD) priority values in subscriber IP packets to Differentiated Services Code Point (DSCP) bits in the IP packet header for outgoing IP packets.
class-map map-name |
Optional. Name of the schema for mapping PD priority bits to DSCP bits in the IP packet header. |
PD values are not propagated to the DSCP bits in the IP packet header.
Use the propagate qos to ip command to propagate PD priority values in the subscriber IP packet to DSCP bits in the IP packet header for outgoing IP packets. In subscriber configuration mode, this command allows you to enable propagation or customize mapping for traffic sent on a specific subscriber session. In interface configuration mode, this command affects all IP traffic transmitted through the interface. The SmartEdge router propagates classification values and marks packets before it applies any metering policy.
If you specify the optional class-map map-name construct, the propagate qos to ip command maps PD values to DSCP bits in the IP packet header. In this case, use the qos class-map command (in global configuration mode) to define a mapping schema, then reference the schema using the optional class-map map-name construct.
If you do not specify the class-map map-name construct, PD values are copied directly to DSCP values.
Use the no form of this command to disable the propagation of PD values to DSCP bits.
Custom classification mappings configured for either a subscriber or an interface affect Layer 3 (IP-routed) circuits only.
propagate qos to l2tp [class-map map-name]
no propagate qos to l2tp [class-map map-name]
For a SmartEdge router configured as a Layer 2 Tunneling Protocol (L2TP) network server (LNS) or an L2TP access concentrator (LAC), propagates the packet descriptor (PD) priority bits to the outer Differentiated Services Code Point (DSCP) bits in the IP packet header for outgoing packets.
L2TP peer configuration (default peer only)
class-map map-name |
Optional. Name of the egress IP classification map for mapping quality of service (QoS) PD values to DSCP values in the IP packet header. |
DSCP bits are not propagated from the PD to an L2TP IP packet header.
For a SmartEdge router configured as an L2TP LNS or an LAC, use the propagate qos to l2tp command to propagates the PD priority bits to the outer DSCP bits for outgoing packets. For the LNS configuration, the DSCP bits are propagated from the incoming network packet headers, and for the LAC configuration, the DSCP bits are propagated from the incoming subscriber packet headers.
As an LNS, the PD priority is derived from the subscriber’s inner DSCP value as part of IP forwarding. As a LAC, the PD priority defaults to a low priority. If you configure the propagate qos from subscriber command (in L2TP peer configuration mode) with the upstream keyword, the PD priority is derived from subscriber’s inner DSCP value.
L2TP tunnels are User Datagram Protocol (UDP)/IP-encapsulated circuits that carry subscriber-based Point-to-Point (PPP) sessions between routers. On L2TP tunnels, subscriber IP packets are encapsulated in PPP packets, which themselves are encapsulated in L2TP packets. DSCP bits are propagated between layers of encapsulated packets so that any Layer 3 device located between an LNS and a LAC can recognize and apply DSCP settings.
You can use the qos class-map command (in global configuration mode) to define an optional mapping schema. If you do not specify the class-map map-name construct for the propagate qos to l2tp command, the unmodified PD QoS value is copied to the outer DSCP field in the IP header.
Use the no form of this command to disable the propagation of DSCP bits.
The following example propagates DSCP bits from incoming network or subscriber IP packet headers to L2TP IP packet headers:
[local]Redback(config-ctx)#l2tp-peer default [local]Redback(config-l2tp)#propagate qos to l2tp
propagate qos to mpls [class-map map-name] [l2vpn class-map map-name]
no propagate qos to mpls [class-map map-name] [l2vpn class-map map-name]
When the SmartEdge router is configured as a Multiprotocol Label Switching (MPLS) ingress router, enables the mapping of packet descriptor (PD) quality of service (QoS) priority values to the MPLS experimental (MPLS EXP) bits for outgoing packets.
MPLS router configuration
class-map map-name |
Optional. Name of the egress MPLS classification map for mapping QoS PD values to MPLS EXP bits. |
l2vpn class-map map-name |
Optional. Name of the egress MPLS classification map for mapping packets received from Layer 2 Virtual Private Networks (L2VPNs). |
PD priority values are mapped to the MPLS EXP bits.
When the SmartEdge router is configured as an MPLS ingress router, use the propagate qos to mpls command to enable the mapping of PD QoS priority values to the MPLS EXP bits for outgoing packets. If you do not specify the optional class-map map-name construct, the default mapping is used.
If you specify the optional class-map map-name construct, the propagate qos to mpls command specifies a custom value mapping for PD values to MPLS EXP bits. The Differentiated Services Code Point (DSCP) values are unaffected. In this case, use the qos class-map command to define a mapping schema, then reference the schema using the class-map map-name construct. If you do not specify an L2VPN classification map, the standard classification map applies to both Layer 2 and Layer 3 traffic.
If you specify the optional l2vpn class-map map-name construct without the class-map map-name construct, the L2VPN classification map applies to Layer 2 traffic. Layer 3 traffic uses the default 8P0D mapping schema. If you specify both the l2vpn class-map map-name construct and the class-map map-name construct, Layer 2 traffic uses the L2VPN classification map and Layer 3 traffic uses the standard classification map.
Use the no form of this command to disable the mapping of PD priority values to MPLS EXP bits.
The following example enables the mapping of the PD values to the MPLS EXP bits at the ingress router:
[local]Redback(config-ctx)#router mpls [local]Redback(config-mpls)#propagate qos to mpls
propagate qos transport {in | out | both} use-vlan-header {inner | outer | both}
no propagate qos transport {in | out | both} use-vlan-header {inner | outer | both}
Specifies whether propagation between packet descriptor (PD) values and Ethernet uses the 802.1p value from the outer permanent virtual circuit (PVC) header or the inner PVC header, when both are present.
dot1q profile configuration
in |
Uses the specified VLAN header 802.1p value when propagating 802.1p to PD for incoming packets. |
out |
Uses the specified VLAN header 802.1p value when propagating 802.1p to PD for outgoing packets. |
both |
Uses the specified VLAN header 802.1p value for both incoming and outgoing packets. |
inner |
Uses the 802.1p value from the inner PVC header. This is the default value. |
outer |
Uses the 802.1p value from the outer PVC header. |
both |
Modifies both the inner PVC 802.1p field and the outer PVC 802.1p field with the same value, if both fields are present. Valid only when the out keyword is specified (egress propagation only). |
The 802.1p value from the inner PVC header is used.
Use the propagate qos transport use-vlan-header command to specify whether propagation between PD values and Ethernet uses the 802.1p value from the outer PVC header or the inner PVC header, when both are present. This command applies only to transport ranges defined for 802.1Q PVCs.
Use the no form of this command to revert values.
propagate qos use-vlan-ethertype tunl-type
{no | default} propagate qos use-vlan-ethertype tunl-type
Specifies the virtual LAN (VLAN) Ethernet type field that determines whether the packet is examined for an enclosed IP header and Differentiated Services Code Point (DSCP) value or for an inner VLAN header and 802.1p value for incoming Multiprotocol Label Switching (MPLS) packets that encapsulate 802.1q Ethernet frames.
MPLS router configuration
tunl-type |
Type of incoming 802.1Q traffic according to one of the following argument or keywords (in hexadecimal format):
|
The 8100 packet type is used.
Use the propagate qos use-vlan-ethertype command to specify the VLAN Ethernet type field that determines whether the packet is examined for an enclosed IP header and DSCP value or for an inner VLAN header and 802.1p value for incoming MPLS packets that encapsulate 802.1q Ethernet frames. In addition to packets with the specified VLAN Ethernet type field, packets with Ethernet type of 0x8100 are also examined for enclosed header values. The SmartEdge router either maps packets with other outer PVC Ethernet types based on the outer PVC 802.1p value (for the mpls use-ethernet command in class map configuration mode) or uses the default 8P0D mapping based on the MPLS EXP value (for the mpls use-ip command in class map configuration mode).
Use the mpls use-ethernet or mpls use-ip command to enable propagation.
Use the no form of this command to disable the use of VLAN header values to identify incoming packets for propagation.
Use the default form of this command to revert to the default setting.
propagate qos use-vlan-header {inner | outer}
{no | default} propagate qos use-vlan-header {inner | outer}
Specifies whether 802.1p-to-packet descriptor (PD) propagation uses the 802.1p value from the outer permanent virtual circuit (PVC) header or the inner PVC header, when both values are present, for incoming Multiprotocol Label Switching (MPLS) packets that encapsulate 802.1q Ethernet frames.
MPLS router configuration
inner |
Uses the 802.1p value from the inner PVC header. |
outer |
Uses the 802.1p value from the outer PVC header. |
The 802.1p value from the inner PVC header is used.
Use the propagate qos use-vlan-header command to specify whether 802.1p-to-PD propagation uses the 802.1p value from the outer PVC header or the inner PVC header, when both values are present, for incoming MPLS packets that encapsulate 802.1q Ethernet frames.
Use the mpls use-ethernet command (in class map configuration mode) to enable propagation.
Use the no or default form of this command to revert to the default setting, which uses the inner PVC 802.1p value.
propagate ttl ip-to-mpls
no propagate ttl ip-to-mpls
Enables the propagation of the IP time-to-live (TTL) to the Multiprotocol Label Switching (MPLS) tunnel label TTL at the ingress router.
MPLS router configuration
This command has no keywords or arguments.
The IP TTL is propagated to the MPLS tunnel label TTL at the ingress router.
Use the propagate ttl ip-to-mpls command to enable the propagation of the IP TTL to the MPLS tunnel label TTL at the ingress router.
Use the no form of this command to disable the propagation of the IP TTL to the MPLS tunnel label TTL at the ingress router.
The following example enables the propagation of the IP TTL to the MPLS tunnel label TTL:
[local]Redback(config-ctx)#router mpls 234 [local]Redback(config-mpls)#propagate ttl ip-to-mpls [local]Redback(config-mpls)#
propagate ttl mpls-to-ip
no propagate ttl mpls-to-ip
Enables the propagation of the Multiprotocol Label Switching (MPLS) tunnel label time-to-live (TTL) to the IP TTL at the egress router.
MPLS router configuration
This command has no keywords or arguments.
The MPLS TTL tunnel label is propagated to the IP TTL at the egress router.
Use the propagate ttl mpls-to-ip command to enable the propagation of the MPLS tunnel label TTL to the IP TTL at the egress router.
Use the no form of this command to disable the propagation of the MPLS tunnel label TTL to the IP TTL at the egress router.
The following example enables the propagation of the MPLS tunnel label TTL to the IP TTL at the egress router:
[local]Redback(config-ctx)#router mpls 234 [local]Redback(config-mpls)#propagate ttl mpls-to-ip [local]Redback(config-mpls)#
protect-group {round-robin | incoming-port}
default protect-group
Specifies the selection algorithm by which a port in the access link group is chosen for outgoing subscriber traffic.
link group configuration
round-robin |
Uses the ports in the link group in round-robin order; this is the default. |
incoming-port |
Uses the first port on which the control protocol packets were received. |
The round-robin algorithm is used to select the port for outgoing subscriber traffic.
Use the protect-group command to specify the selection algorithm by which a port in the access link group is chosen for outgoing subscriber traffic. The selection algorithm determines how the SmartEdge OS load balances outgoing traffic.
The following example shows how to specify the incoming port as the selection algorithm for the link group foo:
[local]Redback(config)#link-group foo access [local]Redback(config-link-group)#protect-group incoming-port
protocol {protocol-name | protocol-number} port start-port-number [end-port-number]]
no protocol {protocol-name | protocol-number}
Specifies the protocol and, optionally, port numbers for the application under which this command is entered.
flow IP application configuration
protocol-name |
Identifies a protocol. Use one of the following keywords to specify the desired protocol:
|
protocol-number |
Number that identifies a particular protocol. |
port start-port-number |
(Optional) Individual port or the starting port in a range of ports within the specified IP protocol. If you specify ports, protocol statistics are collected for the specified ports only. Range is 1 through 65535. |
end-port-number |
(Optional) Ending port in a range of ports. Range is 1 through 65535. |
Statistics are collected for all ports that support the specified protocol.
Use the protocol command to specify the protocol and, optionally, port numbers for the application under which this command is entered.
[local]Redback(config-flow-ip-app-list)# application app-tcp
[local]Redback(config-flow-ip-app)#protocol 6 port 5200 5400
[local]Redback(config-flow-ip-app-list)# application app-udp
[local]Redback(config-flow-ip-app)#protocol 6 port 5225
The following example shows how to use the protocol command to add port number 25 in the tcp protocol:
[local]Redback# configure [local]Redback(config)# flow ip application-list app-list1 [local]Redback(config-flow-ip-app-list)# application app1 [local]Redback(config-flow-ip-app)# protocol tcp port 25
protocol maintenance isis [downtime]
Stops the Intermediate System-to-Intermediate System (IS-IS) process for a brief period without affecting IP forwarding in the network, enabling the system to prepare information about IS-IS operations up to that point.
exec (10)
downtime |
Optional. Number of seconds of down time. The range of values is 30 to 900 seconds; the default value is 600. |
The command is disabled.
Use the protocol maintenance isis command to stop the IS-IS process for a brief period without affecting IP forwarding in the network, enabling the system to prepare information about IS-IS operations up to that point.
The following examples stops the IS-IS process for a period of two minutes (or 120 seconds):
[local]Redback#protocol maintenance isis 120
protocol trigger isis [instance-name] csnp [level-1 | level-2] [interface if-name] [re-start]
Forces Intermediate System-to-Intermediate System (IS-IS) complete sequence number protocol data units (CSNPs) to be sent out through all interfaces or through a particular interface.
exec (10)
instance-name |
Optional. IS-IS instance name. Forces CSNPs to be sent for only the specified instance. |
level-1 |
Optional. Forces CSNPs to be sent for IS-IS level 1 only. |
level-2 |
Optional. Forces CSNPs to be sent for IS-IS level 2 only. |
interface if-name |
Optional. Interface name. Forces CSNPs to be sent for only the specified interface. |
re-start |
Optional. Forces the triggered Hello packets to be sent out with Restart Request bit set inside the restart type-length-value (TLV). |
None
Use the protocol trigger isis csnp command to force CSNPs to be sent out through all interfaces or through a particular interface. This command is useful for lab testing, network troubleshooting, or to manually synchronize the IS-IS database across point-to-point links.
Use the re-start keyword to trigger the neighbors to consider this router as restarted. It may receive the CSNPs and link-state protocol data units (LSPs) from the neighbors.
The following example triggers an IS-IS level-2 CSNP packet to be sent out through all interfaces:
[local]Redback#protocol trigger isis csnp level-2
protocol trigger isis [instance-name] hello [level-1 | level-2] [interface if-name] [padding] [re-start]
Forces an Intermediate System-to-Intermediate System (IS-IS) Hello packet to be sent out through a particular interface or out through all interfaces.
exec (10)
instance-name |
Optional. IS-IS instance name. Forces a Hello packet to sent for only the specified instance. |
level-1 |
Optional. Forces a Hello packet to be sent for IS-IS level 1 only. |
level-2 |
Optional. Forces a Hello packet to be sent for IS-IS level 2 only. |
interface if-name |
Optional. Interface name. Forces a Hello packet to be sent for only the specified interface. |
padding |
Optional. Enables Hello packet padding. Forced Hello packets are padded to the maximum transmission unit (MTU) of the interface over which the packets are sent. By default, triggered Hello packets are not padded. |
re-start |
Optional. Forces the triggered Hello packets to be sent out with Restart Request bit set inside the restart type-length-value (TLV). |
Forced Hello packets are not padded.
Use the protocol trigger isis hello command to force an IS-IS Hello packet to be sent out through a particular interface or out through all interfaces. This command is useful for lab testing, network troubleshooting, or to manually synchronize the IS-IS database across point-to-point links.
Use the re-start keyword to trigger the neighbors to consider this router is restarted. It may receive the complete sequence number protocol data unit (CSNP) and link-state protocol data units (LSPs) from the neighbors.
The following example forces an IS-IS level-2 Hello packet to be sent out the pos3/2 interface:
[local]Redback#protocol isis hello level-2 interface pos3/2
protocol trigger isis [instance-name] lsp [level-1 | level-2] [interface if-name] [all | local | lsp-id lsp-id] [update] [re-start]
Forces an Intermediate System-to-Intermediate System (IS-IS) link-state protocol data unit (LSP) to be sent out a particular interface or out all interfaces.
exec (10)
instance-name |
Optional. IS-IS instance name. Triggers an event for only the specified instance. |
level-1 |
Optional. Triggers an LSP event for IS-IS level 1 only. |
level-2 |
Optional. Triggers an LSP event for IS-IS level 2 only. |
interface if-name |
Optional. Interface name. Triggers an event for only the specified interface. |
all |
Optional. Sends all LSPs in the database. |
local |
Optional. Sends only locally generated LSPs. This is the default setting. |
lsp-id lsp-id |
Optional. LSP ID. Sends only the specified LSP. The ID is in xxxx.xxxx.xxxx format or it can be the hostname. |
update |
Optional. Updates all local LSPs and sends them out. |
re-start |
Optional. Forces the triggered Hello packets to be sent out with Restart Request bit set inside the restart type-length-value (TLV). |
If this command is enabled without using any options, only locally generated LSPs are sent out.
Use the protocol trigger isis lsp command to force an IS-IS LSP to be sent out a particular interface or out all interfaces. This command is useful for lab testing, network troubleshooting, or to manually synchronize the IS-IS database across point-to-point links.
Use the re-start keyword to trigger the neighbors to consider this router is restarted. It may receive the complete sequence number protocol data unit (CSNP) and LSPs from the neighbors.
The following example triggers an IS-IS level-1 LSP to be refreshed and sent out on all interfaces:
[local]Redback#protocol trigger isis lsp level-1 update lsp-id core3.00-01
protocol trigger isis [instance-name] psnp [level-1 | level-2] [interface if-name]
no protocol trigger isis [instance-name] psnp [level-1 | level-2] [interface if-name]
Forces Intermediate System-to-Intermediate System (IS-IS) partial sequence number protocol data units (PSNPs) to be sent out through all interfaces or through a particular interface.
exec (10)
instance-name |
Optional. IS-IS instance name. Forces PSNPs to be sent for only the specified instance. |
level-1 |
Optional. Forces PSNPs to be sent for IS-IS level 1 only. |
level-2 |
Optional. Forces PSNPs to be sent for IS-IS level 2 only. |
interface if-name |
Optional. Interface name. Forces PSNPs to be sent for only the specified interface. |
None
Use the protocol trigger isis csnp command to force PSNPs to be sent out through all interfaces or through a particular interface. The content of the PSNP packets should include all the current version of the link state database. This can be useful during lab testing or network troubleshooting.
The following example triggers an IS-IS level-1 PSNP packet to be sent out over all the interfaces:
[local]Redback#trigger isis psnp level-1
protocol trigger isis [instance-name] spf [level-1 | level-2] [re-start]
Forces an Intermediate System-to-Intermediate System (IS-IS) Shortest Path First (SPF) calculation to run immediately instead of waiting for the next interval.
exec (10)
instance-name |
Optional. IS-IS instance name. Triggers an SPF calculation for only the specified instance. |
level-1 |
Optional. Triggers an SPF calculation for IS-IS level 1 only. |
level-2 |
Optional. Triggers an SPF calculation for IS-IS level 2 only. |
re-start |
Optional. Forces the triggered Hello packets to be sent out with Restart Request bit set inside the restart type-length-value (TLV). |
None
Use the protocol trigger isis spf command to force an IS-IS SPF calculation to run immediately instead of waiting for the next interval.
Use the re-start keyword to trigger the neighbors to consider this router is restarted. It may receive the complete sequence number protocol data unit (CSNP) and link-state protocol data units (LSPs) from the neighbors.
The following example triggers an IS-IS level-2 SPF calculation to run immediately:
[local]Redback#protocol trigger isis spf level-2
proxy-reporting
no proxy-reporting
Enables proxy reporting on a bridge.
This command has no keywords or arguments.
Proxy reporting is disabled by default.
Use the proxy-reporting command to enable proxy reporting on a bridge. The IGMP proxy manages IGMP host tracking, messages, and queries. By default, the IGMP proxy is disabled, and the router is passive and does not suppress IGMP messages. When the IGMP proxy is disabled, the router queries only IGMP messages.
Use the no form of this command to return the bridge to the default setting in which proxy reporting is disabled.
The following example shows how to enable proxy reporting on a bridge called sj1:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#bridge sj1 [local]Redback(config-bridge)#igmp snooping [local]Redback(config-igmp-snooping)#proxy-reporting
pseudowire ignore-mtu
no pseudowire ignore-mtu
The pseudowire ignore-mtu command overrides RFC 4447 compliance with regard to MTU matching.
global configuration
This command has no keywords or arguments.
RFC 4447 compliance with regard to MTU matching.is the default system behavior.
Use the pseudowire ignore-mtu command to override RFC 4447 compliance with regard to MTU matching.
LDP-based L2VPN pseudowires (except ATM AAL2 pseudowires) are defaulted to RFC 4447 compliance with regard to MTU matching. The MTUs across the endpoints are compared and must be same for the pseudowire to be operational. The pseudowire ignore-mtu command is provided to override this default behavior. When the pseudowire ignore-mtu command is enabled, the SmartEdge system falls into non-RFC 4447 compliance mode with regard to MTU matching; and when disabled, adheres to RFC 4447 compliance with regard to MTU matching.
RFC 4447 compliance with regard to MTU matching.is the default system behavior.
Use the no form of this command to return the system to default behavior.
[local]Redback(config)#pseudowire ignore-mtu
pseudowire multi-path
{no | default} pseudowire multi-path
Balances traffic from individual IPTV channels in a PW to multiple paths based on source and destination information.
global configuration
This command has no keywords or arguments.
The legacy load balancing scheme is enabled and traffic from all channels of a PW traverses the same path.
Use the pseudowire multi-path command to balance traffic from individual IPTV channels in a PW to multiple paths based on source and destination information.
Use the no form of this command to disable the balancing of traffic from individual IPTV channels in a PW to multiple paths.
Use the default form of this command to return the router to the default setting in which the balancing of traffic from individual IPTV channels in a PW to multiple paths is disabled.
The following example shows how to balance traffic from individual IPTV channels in a PW to multiple paths based on source and destination information:
[local]Redback#configure [local]Redback(config)#pseudowire multi-path
pseudowire multi-path
{no | default} pseudowire multi-path
Balances traffic from individual IPTV channels in a PW to multiple paths based on source and destination information.
global configuration
This command has no keywords or arguments.
The legacy load balancing scheme is enabled and traffic from all channels of a PW traverses the same path.
Use the pseudowire multi-path command to balance traffic from individual IPTV channels in a PW to multiple paths based on source and destination information.
Use the no form of this command to disable the balancing of traffic from individual IPTV channels in a PW to multiple paths.
Use the default form of this command to return the router to the default setting in which the balancing of traffic from individual IPTV channels in a PW to multiple paths is disabled.
The following example shows how to balance traffic from individual IPTV channels in a PW to multiple paths based on source and destination information:
[local]Redback#configure [local]Redback(config)#pseudowire multi-path
public-key {DSA | RSA} [{after-key existing-key} | {position key-position}] {new-key | ftp url}
no public-key {DSA |RSA} {all | position key-position}
Specifies public key authentication for any administrator accessing the SmartEdge command-line interface (CLI) through Secure Shell (SSH).
administrator configuration
DSA |
Identifies the Digital Signature Algorithm (DSA). |
RSA |
Identifies the Rivest-Shamir-Adelman (RSA) algorithm. |
after-key existing-key |
Optional. Existing key string after which the new key string should follow. |
position key-position |
Optional. Position in which the new key is to be placed within a string of keys. When used with the no form of this command, it is not optional, and it deletes the key in the specified position. The range of values is 1 to 100,000. |
new-key |
New DSA or RSA key string. |
ftp url |
URL for the file that contains DSA or RSA keys. The file resides on an File Transfer Protocol (FTP) server. The url of the file argument is //admin-name[:passwd]@ip-addr [//directory]/filename.ext. |
all |
Deletes all DSA or RSA keys. Used only with the no form of this command. |
None
Use the public-key command to specify public key authentication for administrators accessing the SmartEdge router CLI through SSH.
Use the // if the pathname to the directory on the remote server is an absolute pathname; use a single / if it is a relative pathname (under the hierarchy of username account home directory).
SSH uses cryptographic keys instead of relying on a password scheme. A key is a digital identity based on a unique string of binary data. By using keys, the SSH client can prove to the SSH server on the SmartEdge router that the client is genuine and can prove its identity.
SSH uses a pair of keys—a public key and a private key. The private key, known only to the SSH client, is used to prove the client’s identity. The public key is known by all parties. The public key can be stored on the SmartEdge router if the administrator has an account on the router.
When an administrator logs on to the CLI, the SSH client and the SSH server on the SmartEdge router both compare the private key of the client with the public key on the SmartEdge router. If the keys match, the administrator is authenticated by the SmartEdge router.
An administrator can have multiple RSA and DSA keys. The SmartEdge router maintains the list of keys in the preferred order of the administrator. This is also the order in which the keys are searched when each administrator attempts to log on to the SmartEdge router.
SSH-1 uses the RSA cryptographic algorithm. SSH-2 uses the DSA. For more information, see the Internet Draft, Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and CRL Profile, draft-ietf-pkix-ipki-pkalgs-05.txt.
Use the no form of this command to disable public key authentication.
The following example configures a public RSA key for the administrator jewel:
[local]Redback(config-administrator)#public-key RSA Enter public key for the user $053136276382193869961246761 admin@local % adding public key 1024 35 138778925487550112496264060257494473953477802145777234711904931356017804253563842290930011054450485363243280246400199717731319844418831089264593496852809170833789839891527385879500645266732532498938549779362601026271493734075903025216457395231727858414474890514861688652497950829684053136276382193869961246761 to user jewel
For the following example, the administrator jenny configures a public RSA key from the file, nextkey.pub, located on an FTP server at IP address, 155.53.36.231:
[local]Redback(config-administrator)#public-key RSA ftp//jenny@155.53.36.231/.ssh/nextkey.pub Connected to 155.53.36.231. 220- 220 pepper.redback.com FTP server (NetBSD-ftpd 20000723) ready. Remote system type is UNIX. Using binary mode to transfer files. 331 Password required for jenny. Password: 230- NetBSD 1.5.1_ALPHA (NETZUUL) #34: Mon Jan 27 19:22:08 PST 2003 Welcome to NetBSD! 230 User jenny logged in. 200 Type set to I. 250 CWD command successful. local: /tmp/tmp_public_key remote: nextkey.pub 227 Entering Passive Mode (155,53,36,231,219,44) 150 Opening BINARY mode data connection for 'nextkey.pub' (326 bytes). 100% |*************************************| 326 780.29 KB/s 00:00 ETA 226 Transfer complete. 326 bytes received in 00:00 (1.67 KB/s) 221- Data traffic for this session was 326 bytes in 1 file. Total traffic for this session was 1030 bytes in 1 transfer. 221 Thank you for using the FTP service on pepper.corpA.com. key added 1024 41 106550588489651853198387942858555137190150221510677201916940579736947912236774865600704984815328288560583788592878872188050874678597142562885007685976641197404862724563782974798054110263241761648218460956869243973768579522783213091212849871241135162384999782579058690696235490214548641915001425565861448893991
pwd
Displays the current working directory.
exec (10)
This command has no keywords or arguments.
None
Use the pwd command to display the current working directory.
The following example displays the current working directory:
[local]Redback#pwd
/flash/config
pw-encap {ether | vlan}
{no | default} pw-encap
Specifies the pseudowire encapsulation type.
VPLS profile neighbor configuration
ether |
Specifies the encapsulation type as Ethernet encapsulation. |
vlan |
Specifies the encapsulation type as Ethernet virtual LAN (VLAN) encapsulation. |
The default pseudowire encapsulation type is Ethernet encapsulation.
Use the pw-encap command to specify the pseudowire encapsulation type.
Use the no or default form of this command to specify the default encapsulation type.
The following example specifies the pseudowire encapsulation type as Ethernet VLAN encapsulation:
[local]Redback#config [local]Redback(config)#vpls profile foo [local]Redback(config-vpls-profile)#neighbor 10.10.10.1 [local]Redback(config-vpls-profile-neighbor)#pw-encap vlan [local]Redback(config-vpls-profile-neighbor)#
pw-id pw-num
no pw-id pw-num
Configures a default pseudowire number for use with all the pseudowires signaled by the Virtual Private LAN Services (VPLS) instance.
VPLS configuration
pw-num |
Default pseudowire number, used to identify the pseudowire endpoints when signaling using Label Distribution Protocol (LDP). Valid values are 1 to 4,294,967,295. |
None
Use the pw-id command to configure a default pseudowire number for use with all the pseudowires signaled by the VPLS instance. The default pseudowire number is used for VPLS profiles that do not have a pseudowire ID (number or name) specified.
Remote provider edge (PE) devices use the pseudowire ID and the local IP address to identify the pseudowire and the associated VPLS instance.
A VPLS instance can have only one default pseudowire ID, either a number or a name. If a default pseudowire ID (name or number) has been configured for a VPLS instance and a new one is configured, the previous pseudowire ID is replaced with the new one.
Use the no form of this command to remove the default pseudowire number.
The following example configures the default pseudowire number, 1234, for use with all the pseudowires signaled by the VPLS instance:
[local]Redback#config [local]Redback(config)#context local [local]Redback(config-ctx)#bridge to-pe4 [local]Redback(config-bridge)#vpls [local]Redback(config-vpls)#pw-id 1234 [local]Redback(config-vpls)#
pw-label in in-label-num out out-label-num
no pw-label
Configures pseudowire labels for a static pseudowire.
in in-label-num |
Number of the incoming (ingress) pseudowire label. The range of values is 4,096 to 65,535. |
out out-label-num |
Number of the outgoing (egress) pseudowire label. The range of values is 4,096 to 65,535. |
No pseudowire labels are configured.
Use the pw-label command to configure pseudowire labels for a static pseudowire. When the pseudowire labels are configured, the pseudowire is not signaled using a targeted LDP session to the neighbor. Instead, a static mapping for the pseudowire is created using the specified pseudowire labels. A pseudowire label can be used only once. Trying to configure a pseudowire label that is already in use causes the pw-label command to be rejected. Pseudowire labels must be configured on both ends of the VPLS peering session for the static pseudowire to operate properly.
When the outer tunnel is broken or no next hop to the peer exists, the static pseudowire is marked down, and a standby pseudowire is used if it has been configured.
Use the no form of this command to delete the pseudowire labels.
The following example creates ingress and egress pseudowire labels, with the values 5000 and 15000, respectively, for a static pseudowire to the VPLS profile neighbor, 10.10.10.1:
[local]Redback#config [local]Redback(config)#vpls profile foo [local]Redback(config-vpls-profile)#neighbor 10.10.10.1 [local]Redback(config-vpls-profile-neighbor)#pw-label in 5000 out 15000 [local]Redback(config-vpls-profile-neighbor)#
pw-mtu bytes
{no | default} pw-mtu
Configures the maximum transmission unit (MTU) for a static pseudowire.
bytes |
MTU size in bytes. Enter a value from 1200 to 9198. |
MTU default is 1500.
Use the pw-mtu command to configure the MTU for a static pseudowire.
Use the no or default form of this command to set the pseudowire MTU to its default value.
The following example shows how to set the pseudowire MTU to 9198 bytes:
[local]Redback(config)#vpls profile hub [local]Redback(config-vpls-profile)#neighbor 4.4.4.4 [local]Redback(config-vpls-profile-neighbor)#pw-mtu 9198
pw-name pw-name
no pw-name pw-name
Configures a default pseudowire name for use with all the pseudowires signaled by the Virtual Private LAN Services (VPLS) instance.
VPLS configuration
pw-name |
Name of the default pseudowire, used to identify the pseudowire endpoints when signaling using Label Distribution Protocol (LDP). |
None
Use the pw-name command to configure a default pseudowire name for use with all the pseudowires signaled by the VPLS instance. The default pseudowire name is used for VPLS profiles that do not have a pseudowire ID (number or name) specified.
Remote provider edge (PE) devices use the pseudowire ID and the local IP address to identify the pseudowire and the associated VPLS instance.
A VPLS instance can have only one default pseudowire ID, either a number or a name. If a default pseudowire ID (name or number) has been configured for a VPLS instance and a new one is configured, the previous pseudowire ID is replaced with the new one.
Use the no form of this command to remove the default pseudowire name.
The following example configures the default pseudowire name, pw-foo, for use with all the pseudowires signaled by the VPLS instance:
[local]Redback#config [local]Redback(config)#context local [local]Redback(config-ctx)#bridge to-pe4 [local]Redback(config-bridge)#vpls [local]Redback(config-vpls)#pw-name pw-foo [local]Redback(config-vpls)#
qos {pd-value | all} class class-name
{no | default} qos {pd-value | all} [class class-name]
Assigns an internal packet descriptor (PD) classification v alue to a class name.
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard Differentiated Services Code Point (DSCP) marking label as defined in DSCP Class Keywords in the mark dscp command. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. |
all |
Assigns all valid PD values for the source value to the specified class. Any existing configuration for the class definition is overridden. |
class-name |
An alphanumeric string of up to 39 characters that specifies the class name. Optional only for the no form of this command. |
The PD value is not assigned to any class.
Use the qos class command to assign an internal PD classification value to a class name. The PD value can be referenced in policing or metering policies. The SmartEdge router creates the class when you assign the first PD value in the class definition to the class. Subsequent PD values assigned to this class join the existing class. Removing or modifying the last class-definition entry that references a class deletes the class. Remove all metering and policing policy references to the class definition before you delete a class.
Each class definition can define up to eight metering or policing classes based on PD classification values. Multiple class-definition entries can reference the same class.
The SmartEdge router processes class definitions and assigns packet classes before it applies any metering or policing policy that references the class definition. Use the qos class-definition command (in global configuration mode) to create the class definition.
Use the no or default form of this command to return the PD value to the default state.
qos class-definition class-definition-name
no qos class-definition class-definition-name
Specifies or creates a class definition and enters class definition configuration mode.
global configuration
class-definition-name |
An alphanumeric string of up to 39 characters that specifies the class- definition name. If a class definition with the specified name does not exist, it is created. |
No class definition is defined.
Use the qos class-definition command to specify or create a class definition and enter class definition configuration mode. Class definitions define metering and policing classes using internal packet priority and drop precedence values. You can create up to 15 class definitions; each class definition can define up to eight metering or policing classes based on packet descriptor (PD) classification values.
Use the qos class command (in class definition configuration mode) to edit the contents of a class definition.
Use the no form of this command to delete a class definition. Remove all metering and policing policy references to the class definition before you delete it.
qos class-map map-name marking-type {in | out}
no qos class-map map-name marking-type {in | out}
Defines a configurable schema for customized packet mappings to and from the SmartEdge router internal packet descriptor (PD) markings, and accesses class map configuration mode.
map-name |
Name of the classification map, an alphanumeric string of up to 39 characters. The name must be unique. You can configure up to 128 classification maps for all marking types and directions. If the classification map does not exist, the SmartEdge router creates it. |
marking-type |
Marking type for this classification map, according to one of the following keywords:
|
in |
Maps incoming packets as they are received. This type of classification map can be applied to propagate qos from commands. |
out |
Maps outgoing packets as they are prepared for transmission. This type of classification map can be applied to propagate qos to commands. |
None
Use the qos class-map command to create and configure customized mappings between internal and external packet priority and drop precedence values.
You can use the mapping-schema command to define a set of default values for all mapping entries, then override that value for a subset of entries by entering subsequent mapping commands. The mapping commands that are available depend on the direction and marking-type values specified by this command. For example, if you enter the qos class-map command with the my_class_map ethernet out keywords, only the mapping-schema, qos to ethernet, and qos use-ip commands are available. The classification map can then be applied using the propagate qos to ethernet command with the class-map my_class_map keywords.
A classification map can function either as a primary or secondary classification map, or both. For ingress mappings, a secondary classification map must have a value of ip for the marking-type argument, and a value of in specified for the mapping direction. For egress mappings, a secondary classification map must have the same values for the marking-type argument and mapping direction as the primary classification map.
The SmartEdge router uses primary classification maps during the initial packet inspection. If a secondary classification map is configured, the SmartEdge router performs a second mapping for packets containing the specified primary value. When configured for the ethernet use-ip or mpls use-ip commands, secondary classification maps translate Differentiated Services Code Point (DSCP) values to PD priority values. When configured for the qos use-ip commands, secondary classification maps translate DSCP values to external Multiprotocol Label Switching (MPLS) experimental (EXP) values or 802.1p priority values.
Use the no form of this command to remove the classification map. Remove all dependent configuration entries, such as propagation commands and other classification maps, before you remove the classification map.
The following example creates a classification map exp-to-pd that maps MPLS EXP values to quality of service (QoS) PD values on ingress:
[local]Redback(config)#qos class-map exp-to-pd mpls in
qos congestion-avoidance-map map-name pol-type
no qos congestion-avoidance-map map-name pol-type
Creates a quality of service (QoS) congestion avoidance map and accesses congestion map configuration mode.
map-name |
Name of the congestion avoidance map. |
pol-type |
Policy type to which this congestion avoidance map will be assigned, according to one of the following keywords:
|
None
Use the qos congestion-avoidance-map command to create a QoS congestion avoidance map and access congestion map configuration mode.
You can create up to 256 congestion avoidance maps.
Use the or queue redcommand (in congestion map configuration mode) to configure the map.
To assign a map to a policy, use the congestion-map command (in ATMWFQ, MDRR, or PWFQ policy configuration mode).
Use the no form of this command to delete the specified map from the configuration.
The following example creates a congestion avoidance map, map-red4a:
[local]Redback(config)#qos congestion-avoidance-map map-red4a [local]Redback(config-congestion-map)#
qos hierarchical mode strict
{no | default} qos hierarchical mode
Specifies the strict priority quality of service (QoS) scheduling algorithm for the traffic-managed port, 802.1Q tunnel, 802.1Q permanent virtual circuit (PVC), hierarchical node group, or hierarchical node on a traffic-managed port.
This command has no keywords or arguments.
Gigabit Ethernet ports on traffic-managed cards are the top level in the traffic management hierarchy.
Use the qos hierarchical mode strict command to specify the strict priority QoS scheduling algorithm for the traffic-managed port, 802.1Q tunnel, 802.1Q PVC, hierarchical node group, or hierarchical node on a traffic-managed port. You can also use the qos rate or qos weight commands (in port or dot1q PVC configuration mode) to create a node in the QoS hierarchy with the default strict priority mode.
A QoS traffic-managed port is always a node at the top of the hierarchy. The scheduling algorithms service the QoS queues defined by the priority weighted fair queuing (PWFQ) policy attached to the port, 802.1Q tunnel, or 802.1Q PVC according to the priority assigned to each queue with the queue priority command (in PWFQ policy configuration mode). The priority determines the servicing order, and the relative maximum rate or weight determines the amount of traffic that is transmitted.
For 802.1Q PVCs, you can use this command to configure both static and on-demand PVCs. If you do not enter this command for an 802.1Q tunnel or PVC, the tunnel or PVC is not part of the QoS traffic management hierarchy. In this case, a tunnel inherits only the PWFQ policy attached to its port and a PVC inherits the policy attached to its tunnel, unless you apply a more specific PWFQ policy to the tunnel or PVC.
Use the no or default form of this command to remove the tunnel or PVC from the hierarchy.
The following example enables an 802.1Q PVC tunnel as a traffic-managed hierarchical node, with strict scheduling algorithm:
[local]Redback(config)#port ethernet 9/1 [local]Redback(config-port)# dot1q pvc 10 encapsulation 1qtunnel [local]Redback(config-dot1q-pvc)#qos hierarchical mode strict
qos mode {alternate | normal | strict}
{no | default} qos mode
Defines the mode of the quality of service (QoS) enhanced deficit round-robin (EDRR) policy algorithm.
alternate |
Indicates that in every other round, either queue 0 or one of the other queues configured on the port is serviced, in alternating fashion. |
normal |
Indicates that queue 0 is treated like all other queues on the port. Each queue receives its share of the port’s bandwidth according to the configured weights. This is the default mode for EDRR policies. |
strict |
Indicates that queue 0 has strict priority over all other queues configured on the port. |
The mode is normal.
Use the qos mode command to define the mode of the EDRR policy algorithm.
Use the no or default form of this command to return EDRR queuing to normal mode.
The following example configures a strict mode for each configured port on the Ethernet traffic card in slot 4:
[local]Redback(config)#qos policy qos-edrr-test edrr [local]Redback(config-policy-edrr)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos mode strict [local]Redback(config-port)#exit [local]Redback(config)#port ethernet 4/2 [local]Redback(config-port)#qos mode strict [local]Redback(config-port)#exit [local]Redback(config)#port ethernet 4/3 [local]Redback(config-port)#qos mode strict
qos mode {priority | strict | wrr}
no qos mode{priority | strict | wrr}
Specifies the scheduling algorithm for this modified deficit round-robin (MDRR) policy.
priority |
Specifies the priority queuing (PQ) strict priority mode. |
strict |
Specifies the MDRR strict mode. |
wrr |
Specifies the MDRR weighted round-robin (WRR) mode. |
MDRR policies use the WRR mode scheduling algorithm.
Use the qos mode command to specify the scheduling algorithm for this MDRR policy. The following restrictions apply when selecting the mode and configuring the policy:
Use the default queue weight command (in MDRR policy configuration mode) to remove the weight configurations.
Use the no form of this command to specify the default algorithm.
The following example specifies the MDRR strict mode as the scheduling algorithm:
[local]Redback(config)#qos policy example2 mdrr [local]Redback(config-policy-mdrr)#qos mode strict
qos node node-name idx-start [through idx-end]
no qos node node-name
Creates one or more quality of service (QoS) hierarchical nodes as aggregation points for applying traffic shaping and accesses hierarchical node configuration mode.
node-name |
Name of the node. |
idx-start |
Initial index number. |
through idx-end |
Optional. Final index number. |
No nodes are created.
Use the qos node command to create one or more QoS hierarchical nodes as aggregation points for applying traffic shaping and access hierarchical node configuration mode.
Each node is uniquely referenced by its name, its node index, its node group, and the index for the node group.
Use the no form of this command to delete one or more nodes from the configuration.
The following example creates 10 hierarchical node groups and 50 hierarchical nodes, with 5 nodes in each node group; the name of each node group is home and the name of each node is dslam:
[local]Redback(config)#port ethernet 5/1 [local]Redback(config-port)#qos node-group home 1 through 10 [local]Redback(config-h-node)#qos node dslam 1 through 5 [local]Redback(config-h-node)#
qos node-group group-name idx-start [through idx-end]
no qos node-group group-name
Creates one or more quality of service (QoS) hierarchical node groups as aggregation points for applying traffic shaping and accesses hierarchical node group configuration mode.
group-name |
Name of the node groups. |
idx-start |
Initial index number. |
through idx-end |
Optional. Final index number. |
No node groups are created.
Use the qos node-group command to create one or more QoS hierarchical node groups as aggregation points for applying traffic shaping and accesses hierarchical node group configuration mode. This command is available only for traffic-managed ports.
Each node group is uniquely referenced by its name and its index.
Use the no form of this command to delete the node group from the configuration.
The following example creates 10 hierarchical node groups; the name of each group is home:
[local]Redback(config)#port ethernet 5/1 [local]Redback(config-port)#qos node-group home 1 through 10 [local]Redback(config-h-node)#
qos node-reference node-name node-idx group-name group-idx
no qos node-reference node-name
Creates a reference to a quality of service (QoS) hierarchical node in the subscriber record, named subscriber profile, or default subscriber profile.
node-name |
Name of the node. |
node-idx |
Node index number. |
group-name |
Name of the node group. |
group-idx |
Node group index number. |
No node references are created in any subscriber record, named subscriber profile, or default subscriber profile.
Use the qos node-reference command to create a reference to a QoS hierarchical node in the subscriber record, named subscriber profile, or default subscriber profile.
Use the no form of this command to delete the reference from the subscriber record, named subscriber profile, or default subscriber profile.
The following example creates a reference to the hierarchical node group, home, with index 1, in which was created the node, dslam, with index 5, in the subscriber record, joe:
[local]Redback(config)#context subs [local]Redback(config-ctx)#subscriber joe [local]Redback(config-sub)#qos node-reference home 1 dslam 5
qos policy pol-name atmwfq
no qos policy pol-name atmwfq
Creates or selects a quality of service (QoS) Asynchronous Transfer Mode weighted fair queuing (ATMWFQ) policy and enters ATMWFQ policy configuration mode.
global configuration
pol-name |
Name of the ATMWFQ policy to be created or selected. |
No ATMWFQ policy is created.
Use the qos policy atmwfq command to create or select a QoS ATMWFQ policy and enter ATMWFQ policy configuration mode. An ATMWFQ policy defines QoS for outbound packets on the circuit to which the policy is attached. Up to eight queues per circuit can be serviced.
To attach an ATMWFQ policy to the circuit, use the qos policy queuing command (in ATM PVC configuration mode).
Caution! | ||
Risk of dropping packets. Modifying the parameters of an ATMWFQ
policy will momentarily interrupt the traffic on all ATM PVCs using
the policy. To reduce the risk, use caution when modifying ATMWFQ
policy parameters.
|
Use the no form of this command to delete an ATMWFQ policy from the configuration.
The following example creates the ATMWFQ policy, example1, configures 4 queues, and assigns a congestion map:
[local]Redback(config)#qos policy example1 atmwfq [local]Redback(config-policy-atmwfq)#num-queues 4 [local]Redback(config-policy-atmwfq)#congestion-map red4
qos policy pol-name edrr
no qos policy pol-name edrr
Creates or selects a quality of service (QoS) enhanced deficit round-robin (EDRR) policy and enters EDRR policy configuration mode.
global configuration
pol-name |
Name of the EDRR policy to be created or selected. |
No EDRR policy is configured.
Use the qos policy edrr command to create a QoS EDRR policy and enter EDRR policy configuration mode. An EDRR policy defines QoS for outgoing packets on the port or circuit to which the policy is attached. Up to eight queues per circuit can be serviced.
To attach an EDRR policy, enter the qos policy queuing command (in the appropriate port or circuit configuration mode).
Use the no form of this command to remove an EDRR policy from the configuration.
The following example configures the EDRR policy, example1, and attaches the policy to an Ethernet port:
[local]Redback(config)#qos policy example1 edrr [local]Redback(config-policy-edrr)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy queuing example1
qos policy pol-name mdrr
no qos policy pol-name mdrr
Creates or selects a quality of service (QoS) modified deficit round-robin (MDRR) policy and enters MDRR policy configuration mode.
global configuration
pol-name |
Name of the MDRR policy to be created or selected. |
No MDRR policy is configured.
Use the qos policy mdrr command to create a QoS MDRR policy and enter MDRR policy configuration mode. An MDRR policy defines QoS for outgoing packets on the port or circuit to which the policy is attached. Up to eight queues per circuit can be serviced.
To attach an MDRR policy to a port or circuit, enter the qos policy queuing command (in the appropriate port or circuit configuration mode).
Use the no form of this command to remove an MDRR policy from the configuration.
The following example configures the MDRR policy, example1, and attaches the policy to a 10 Gigabit Ethernet (10GE) port:
[local]Redback(config)#qos policy example1 mdrr [local]Redback(config-policy-edrr)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy queuing example1
qos policy metering pol-name [acl-counters] [inherit] [hierarchical]
no qos policy metering pol-name
Attaches a metering policy to the specified circuit, or port, or subscriber record to be enforced on outbound packets.
pol-name |
Name of the metering policy to be attached. |
acl-counters |
Optional. Enables per-rule access control list (ACL) statistics for a policy ACL associated with the policy. Available in all listed configuration modes, except global configuration. |
inherit |
Optional. Attaches the specified policy as follows:
This keyword is available only for Ethernet ports, 802.1Q tunnels, and 802.1Q PVCs, and ATM PVCs. |
hierarchical |
Optional. Attaches the specified policy as follows:
This keyword is available only for Ethernet ports, 802.1Q tunnels and PVCs, and ATM PVCs. |
No metering policy is attached to outbound packets on the specified circuit, or port, or subscriber record.
Use the qos policy metering command to attach a metering policy to a specified circuit, or port, or subscriber record to be enforced on outbound packets in any of the listed configuration modes, except link group configuration mode.
Use the qos policy metering command in link group configuration mode to attach the policy to an MP or MFR bundle; use it in port configuration mode to attach the policy to an Ethernet or 802.1Q link group. When you attach the policy to any type of link group, you effectively attach it to all ports or circuits in the link group (MP, MFR, Ethernet, or 802.1Q).
For 802.1Q PVCs, this command can be used to configure both static and on-demand PVCs.
Child circuits can inherit the QoS metering and policing policies attached to the parent circuit on which the child circuits are configured if the keyword inherit or hierarchical is specified on the parent binding. If you attach a different metering or policing policy to a child circuit, those policies override the metering or policing policy attached to the parent circuit unless the parent policy applied is configured with the keyword hierarchical.
By default, using the optional keyword inherit when configuring a metering or policing policy for a parent circuit results in all of the children of the parent circuit inheriting the parent circuit policy, unless the children have a more specific policy configured. In this case, rate limiting is applied collectively to the child circuit and the parent circuit, which means all circuits to which the parent policy is to be applied are collectively subject to the rate limitations specified in the parent circuit’s metering or policing policy.
Using the optional keyword hierarchical when configuring a metering or policing policy for a parent circuit results in applying both the child circuit policy and the parent circuit policy to the traffic on the child circuit. With hierarchical metering or policing policy, rate limiting is applied on the packets destined for the child circuit first using the child policy. If the child metering or policing policy includes a drop policy, then the SmartEdge router drops the appropriate packets if the traffic rate exceeds the rate limit. Those packets that were not dropped are processed and rate-limited once again, along with all the other packets destined for the parent circuit, using the parent policy.
Essentially, the child circuit traffic is processed and rate-limited twice and the parent circuit’s native traffic is processed and rate-limited once. With hierarchical metering or policing policy enabled, a child is subject to its own specified rate limitations and then is collectively subject to the rate limitations specified in the parent circuit metering or policing policy, along with its parent and peers.
Use the no form of this command to remove a metering policy from outbound packets on a circuit, port, subscriber record, or link group (of any type).
The following example creates the metering policy, example2, and attaches it to an Ethernet port:
[local]Redback(config)#qos policy example2 metering [local]Redback(config-policy-metering)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-metering)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy metering example2
The following example configures an outbound rate limit for all traffic on a particular port and an individual rate-limit for each 802.1Q VLAN configured under the port:
[local]Redback(config)#qos policy port-hierarchical-policy metering [local]Redback(config-policy-metering)#rate 500 burst 50000 [local]Redback(config-policy-rate)#exceed mark priority 6 [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-metering)#exit [local]Redback(config)#qos policy vlan-individual-policy metering [local]Redback(config-policy-metering)#rate 100 burst 10000 [local]Redback(config-policy-rate)#conform mark priority 0 [local]Redback(config-policy-rate)#exceed mark priority 5 [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-metering)#exit . . [local]Redback(config)#port ethernet 12/2 [local]Redback(config-port)#encapsulation dot1q [local]Redback(config-port)#qos policy metering port-hierarchical-policy hierarchical [local]Redback(config-port)#dot1q pvc 30 thr 40 encapsulation [local]Redback(config-port)#qos policy metering vlan-individual-policy
qos policy pol-name metering [radius-guided]
no qos policy pol-name metering
Creates or selects a quality of service (QoS) metering policy and enters metering policy configuration mode.
pol-name |
Name of the metering policy. |
radius-guided |
Optional. Allows this policy to be modified by dynamic access control lists (ACLs). |
No metering policy is created.
Use the qos policy metering command to create or select a metering policy and enter metering policy configuration mode.
Use the radius-guided keyword to allow a dynamic policy ACL to modify this policy. You cannot remove a dynamic policy ACL from the policy after you have configured it, nor can you change the type of the policy from static to RADIUS-guided. To remove the dynamic policy ACL or to change the type of the policy, delete the policy and then recreate it as a static policy.
Use the no form of this command in global configuration mode to delete a metering policy.
The following example creates the metering policy, example2, and attaches it to an Ethernet port:
[local]Redback(config)#qos policy example2 metering [local]Redback(config-policy-metering)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-metering)#exit
qos policy policing pol-name [acl-counters] [inherit | hierarchical]
no qos policy policing pol-name
Attaches a policing policy to the specified circuit, port, or subscriber record to be enforced on inbound packets.
pol-name |
Name of the policing policy to be attached. |
acl-counters |
Optional. Enables per-rule access control list (ACL) statistics for a policy ACL associated with the policy. Available in all configuration modes, except global configuration. |
inherit |
Optional. Attaches the specified policy as follows:
This keyword is available only for Ethernet ports, 802.1Q tunnels, and 802.1Q PVCs, and ATM PVCs. |
hierarchical |
Optional. Attaches the specified policy as follows:
This keyword is available only for Ethernet ports, 802.1Q tunnels and PVCs, and ATM PVCs. |
No policing policy is attached to inbound packets on the port, or circuit, or subscriber record.
Use the qos policy policingg command to attach a policing policy to inbound packets on a specific port, or circuit, or subscriber record in any of the listed configuration modes, except link group configuration mode.
Use the qos policy policing command in link group configuration mode to attach the policy to a multilink Point-to-Point Protocol (MP) or Multilink Frame Relay (MFR) bundle; use it in port configuration mode to attach the policy to an Ethernet or 802.1Q link group. When you attach the policy to any type of link group, you effectively attach it to all ports or circuits in the link group (MP, MFR, Ethernet, or 802.1Q).
For 802.1Q PVCs, you can use this command to configure both static and on-demand PVCs.
Use the no form of this command to remove a policing policy from inbound packets on a port, circuit, subscriber record, or link group (of any type).
The following example creates the example2 policing policy and attaches it to an Ethernet port:
[local]Redback(config)#qos policy example2 policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy policing example2
The following example attaches the WholePort policing policy to a Gigabit Ethernet port, and then attaches the OneVC policing policy to one of the 802.1Q PVCs. The policy attached to the PVC supersedes the policy attached to the port. For all the other PVCs on the port, the policy attached to the port takes effect:
[local]Redback(config)#qos policy OneVC policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#conform mark dscp ef [local]Redback(config-policy-rate)#exceed mark dscp df [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#qos policy WholePort policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#encapsulation dot1q [local]Redback(config-port)#qos policy policing WholePort [local]Redback(config-port)#dot1q pvc 100 [local]Redback(config-dot1q-pvc)#bind interface if_100 local [local]Redback(config-dot1q-pvc)#qos policy policing OneVC
The following example configures an inbound rate limit to be enforced on all traffic on a particular 802.1Q tunnel SVLAN and an individual rate limit for each CVLAN configured under SVLAN:
[local]Redback(config)#qos policy svlan-hierarchical-policy policing [local]Redback(config-policy-policing)#rate 1000 burst 50000 [local]Redback(config-policy-rate)#exceed mark priority 6 [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#qos policy cvlan-individual-policy policing [local]Redback(config-policy-policing)#rate 100 burst 10000 [local]Redback(config-policy-rate)#conform mark priority 0 [local]Redback(config-policy-rate)#exceed mark priority 5 [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#port ethernet 12/2 [local]Redback(config-port)#encapsulation dot1q [local]Redback(config-port)#dot1q pvc 30 encapsulation 1qtunnel [local]Redback(config-dot1q-pvc)#$svlan-hierarchical-policy hierarchical [local]Redback(config-dot1q-pvc)#exit [local]Redback(config-port)#dot1q pvc 30:1 through 100 [local]Redback(config-dot1q-pvc)#qos policy policing cvlan-individual-policy
qos policy pol-name policing [radius-guided]
no qos policy pol-name policing
Creates or selects a quality of service (QoS) policing policy and enters policing policy configuration mode.
pol-name |
Name of the policing policy to be attached. |
radius-guided |
Optional. Allow this policy to be modified by dynamic access control lists (ACLs). |
No policing policy is created.
Use the qos policy policing command to create or select a policing policy and enter policing policy configuration mode.
Use the radius-guided keyword to allow a dynamic policy ACL to modify this policy. You cannot remove a dynamic policy ACL from the policy after you have configured it, nor can you change the type of the policy from static to RADIUS-guided. To remove the dynamic policy ACL or to change the type of the policy, delete the policy and then recreate it as a static policy.
Use the no form of this command to delete a policing policy.
The following example creates the example2 policing policy:
[local]Redback(config)#qos policy example2 policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit
The following example creates the WholePort policing policy for an Ethernet port and the OneVC policing policy for an 802.1Q PVC on that port. When the OneVC policy is attached to the PVC, it supersedes the WholePort policy attached to the port for that PVC; for all the other PVCs on the port, the policy attached to the port takes effect:
[local]Redback(config)#qos policy OneVC policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#conform mark dscp ef [local]Redback(config-policy-rate)#exceed mark dscp df [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit [local]Redback(config)#qos policy WholePort policing [local]Redback(config-policy-policing)#rate 10000 burst 100000 [local]Redback(config-policy-rate)#exceed drop [local]Redback(config-policy-rate)#exit [local]Redback(config-policy-policing)#exit
qos policypol-nameprotocol-rate-limit
no qos policy pol-name protocol-rate-limit
Creates a named rate-limiting policy that can be applied to protocol specific packets.
global configuration
subscriber configuration
port configuration
link group configuration
link PVC configuration
dot1q PVC configuration
pol-name |
Specifies the policy name |
protocol-rate-limit |
The named policy is applicable to protocol-specific packets. |
No protocol-specific rate-limiting policies exist.
The qos policy (protocol-rate-limit) command creates a named rate-limiting policy that can be applied to protocol-specific packets.
For information on how to use this command, see Configuring ARP .
The following example shows the use of the arp rate command to rate-limit incoming ARP packets from the Ethernet port 5/1:
[local]Redback(config)#qos policy ARPDOS protocol-rate-limit [local]Redback(config-policy-protocol)#arp rate 5000 burst 100000 [local]Redback(config-policy-protocol)#exit [local]Redback(config)#port ether 5/1 [local]Redback(config-port)#qos policy protocol-rate-limit ARPDOS
The following example shows the use of the arp rate command to rate-limit incoming ARP packets from subscriber circuits where the default subscriber profile is applied:
[local]Redback(config)#qos policy ARPDOS protocol-rate-limit [local]Redback(config-policy-protocol)#arp rate 5000 burst 100000 [local]Redback(config-policy-protocol)#exit [local]Redback(config)#subscriber default [local]Redback(config-sub)#qos policy protocol-rate-limit ARPDOS
qos policy pol-name pq
no qos policy pol-name pq
Creates or selects a quality of service (QoS) priority queuing (PQ) policy and enters PQ policy configuration mode.
pol-name |
Name of the PQ policy to be configured. |
No PQ policy is created.
Use the qos policy pq command to create a PQ policy and enter PQ policy configuration mode.
A PQ policy defines QoS for outgoing packets on the port or circuit to which the policy is attached. Up to eight queues per circuit can be serviced.
To attach a PQ policy, use the qos policy queuing command (in the appropriate port or circuit configuration mode).
Use the no form of this command to delete the named policy from the configuration.
The following example creates the PQ policy, example1, and attaches the policy to an Ethernet port:
[local]Redback(config)#qos policy example1 pq [local]Redback(config-policy-pq)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy queuing example1
The following example enables per-virtual LAN (VLAN) queuing on a Gigabit Ethernet port by defining a PQ policy with a single queue, and then attaching that policy to each VLAN on the port:
[local]Redback(config)#qos policy PerVcQueuing pq [local]Redback(config-policy-pq)#num-queues 1 [local]Redback(config-policy-pq)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#encapsulation dot1q [local]Redback(config-port)#dot1q pvc 100 [local]Redback(config-dot1q-pvc)#bind interface if_100 local [local]Redback(config-dot1q-pvc)#qos policy queuing PerVcQueuing
qos policy pol-name pwfq
no qos policy pol-name pwfq
Creates or selects quality of service (QoS) priority weighted fair queuing (PWFQ) policy and enters PWFQ policy configuration mode.
pol-name |
Name of the policy to be created. |
No PWFQ policy is created.
Use the qos policy pwfq command to create a QoS PWFQ policy and enter PWFQ policy configuration mode.
Use the no form of this command to delete the named QoS PWFQ policy.
The following example creates a QoS PWFQ policy, ge3, with two queues and attaches the policy to a Gigabit Ethernet 3 (GE3) port:
[local]Redback(config)#qos policy ge3 pwfq [local]Redback(config-policy-pwfq)#num-queues 2 [local]Redback(config-policy-pwfq)#exit [local]Redback(config)#port ethernet 5/1 [local]Redback(config-port)#qos policy queuing ge3
qos policy queuing pol-name
no qos policy queuing pol-name
Attaches a quality of service (QoS) scheduling policy to the port, circuit, or hierarchical node, or subscriber record.
pol-name |
Name of the scheduling policy to be attached. |
No queuing policy is not attached to the circuit or port.
Use the qos policy queuing command to attach a QoS scheduling policy to the port, circuit, or hierarchical node, or subscriber record.
The specified QoS scheduling policy must already exist. The types of scheduling policies are Asynchronous Transfer Mode weighted fair queuing (ATMWFQ), enhanced deficit round-robin (EDRR), modified deficit round-robin (MDRR), priority queuing (PQ), and priority weighted fair queuing (PWFQ).
Use this command in link group configuration mode to attach the policy to a Multilink Point-to-Point Protocol (MP) or Multilink Frame Relay (MFR) bundle; use it in port configuration mode to attach the policy to an Ethernet or 802.1Q link group.
For 802.1Q permanent virtual circuits (PVCs), this command can be used to configure both static and on-demand PVCs.
Caution! | ||
Risk of data loss. Modifying the parameters of an ATMWFQ policy
will momentarily interrupt the traffic on all ATM PVCs using the policy.
To reduce the risk, modify an ATMWFQ policy only when traffic is light.
|
Slot redundancy is not supported; if an LNS subscriber session moves to a traffic-managed port in a different slot, it will no longer be governed by the PWFQ policy attached to the LNS subscriber session. If the session moves to a different port in the same slot, the PWFQ policy will resume queuing after a temporary traffic disruption.
Use the no form of this command to remove a QoS scheduling policy from the port, circuit, or hierarchical node, or subscriber record.
The following example creates a PQ policy and then attaches the policy to a GE3 port:
[local]Redback(config)#qos policy example1 pq [local]Redback(config-policy-pq)#exit [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#qos policy queuing example1
The following example attaches two PWFQ policies, pwfq1 and pwfq2, to a GE3 port, an 802.1Q tunnel on that port, and an 802.1Q PVC within that tunnel:
[local]Redback(config)#port ethernet 5/1 [local]Redback(config-port)#encapsulation dot1q [local]Redback(config-port)#qos policy queuing pwfq1 [local]Redback(config-port)#dot1q pvc 10 encapsulation 1qtunnel [local]Redback(config-dot1q-pvc)#qos policy queuing pwfq1 [local]Redback(config-dot1q-pvc)#exit [local]Redback(config-port)#dot1q pvc 10:20 [local]Redback(config-dot1q-pvc)#qos policy queuing pwfq2 [local]Redback(config-dot1q-pvc)#exit
qos port-map port-group-map-name
no qos port-map
Applies a predefined or a user-defined port group map to the traffic card you are configuring.
port-group-map-name |
The port-group-map-name argument specifies the name of the port group map to apply to the card. You have at least 2 options, and these are the predefined and default port map names. If you configured one or more user-defined port maps, then these port maps are also valid options. A list of valid predefined and user-defined port group map names depends on card type and can be obtained by entering "?" after the qos port-map command. |
Name of the default port group map to which to apply to the card. The name that displays as an option varies depending on the type of traffic card you are configuring and is one of the following:
|
(1) The ge-5-port card does not have a predefined port group
map.
The default port group map is applied.
Use the qos port-map command to apply a predefined or a user-defined port group map to the traffic card you are configuring. Type "?" after qos port-map command to obtain a list of applicable port group maps.
For more information about port group maps, see Port Grouping for Traffic Scheduling .
Use the no form of this command to remove a port group map from the card and revert to the default port-map.
The following example shows how to apply the predefined port group map named fwd_max_perf to the ge3-4-port card in slot 2:
[local]Redback(config)#card ge3-4-port 2 [local]Redback(config-card)#qos port-map fwd_max_perf
qos port-mapport-map-namecard-typecard-type-name
no qos port-map port-map-name card-type card-type-name
Defines the name of a port group map for a specified traffic card type and enters port group map configuration mode.
port-map-name |
Specifies the name of the port group map, which can be up to 39 alphanumeric characters long. |
card-type card-type-name |
Specifies the name of the card type to associate with the port group map. The following are the supported values:
|
None
Use the qos port-map command to define the name of a port group map for a specified traffic card type and enter port group map configuration mode.
Use the no form of this command to remove a port group map configuration.
For more information about port group maps, see Port Grouping for Traffic Scheduling .
The following example shows how to define a qos port map named portmap7 for the ge-10-port card type:
[local]Redback(config)#qos port map portmap7 card-type ge-10-port [local]Redback(config-port-group-map)#
qos priority group-num
no qos priority group-num
Classifies all traffic, including non-IP traffic, on the ingress circuit with a quality of service (QoS) priority group number.
group-num |
Priority group number. The range of values is 0 to 7. |
By default, no QoS priority is configured and no priority group is assigned to any traffic.
Use the qos priority command to classify all traffic, including non-IP traffic, on the ingress circuit with a QoS priority group number.
A priority group is an internal value used by the SmartEdge router to determine into which egress queue the inbound packet should be placed. The type of service (ToS) value, IP Differentiated Services Code Point (DSCP) value, and Multiprotocol Label Switching (MPLS) experimental (EXP) bits are not changed by this command. The actual queue number depends upon the number of queues configured on the circuit; see the num-queues command in Configuring Scheduling.
This command is not supported for dynamic 802.1Q permanent virtual circuits (PVCs).
Use the no form of this command to remove a QoS priority configuration and to stop assigning traffic to the priority group.
The following example configures a priority of 2 to port 1 on the Ethernet traffic card in slot 13:
[local]Redback(config)#port ethernet 13/1 [local]Redback(config-port)#no shutdown [local]Redback(config-port)#bind interface eth-pc05 local [local]Redback(config-port)#qos priority 2
qos profile profile-name overhead
no qos profile profile-name overhead
Creates or selects a quality of service (QoS) overhead profile and enters overhead profile configuration mode.
This command has no keywords or arguments.
No overhead profile is created.
Use the qos profile overhead command to create or select a QoS overhead profile and enter overhead profile configuration mode.
Use the no form of this command to delete an overhead profile.
The following example creates the example1 overhead profile:
[local]Redback(config)#qos profile example1 overhead
qos profile overhead profile-name [inherit]
no qos profile overhead profile-name [inherit]
Attaches an overhead profile to a port, or an 802.1Q permanent virtual circuit (PVC), or a subscriber record.
profile-name |
Name of the existing overhead profile to be attached to the port or PVC. |
inherit |
Optional. Applies the overhead profile to any child circuit configured on an 802.1Q PVC that is configured on this Ethernet port (unless it is overridden by a quality of service [QoS] overhead profile attached to that circuit). This keyword is available only for Ethernet ports and 802.1Q PVCs. |
No overhead profile is attached to a port, or an 802.1Q PVC, or a subscriber record.
Use the qos profile overhead command to attach a overhead profile to the port, or 802.1Q PVC, or a subscriber record.
Use the inherit keyword to apply the overhead profile to any child circuit configured on an 802.1Q PVC that is configured on this Ethernet port (unless it is overridden by a QoS overhead profile attached to that circuit). If you do not specify the inherit keyword, the child circuits do not inherit the overhead profile of the parent.
Use the no form of this command to delete an overhead profile from the port, or 802.1Q PVC, or a subscriber record.
The following example allows the child circuits of the 802.1Q PVC to inherit the example1 overhead profile:
[local]Redback(config)#port ethernet 2/1 [local]Redback(config-port)#dot1q pvc 100 encapsulation 1qtunnel [local]Redback(config-port)#qos profile overhead example1 inherit [local]Redback(config-port)#exit
qos queue-map map-name
no qos queue-map map-name
Creates a quality of service (QoS) queue map and enters queue map configuration mode.
global configuration
map-name |
Queue map name. |
The SmartEdge router assigns priority groups to queues as listed in the Usage Guidelines section.
Use the qos queue-map command to create a QoS queue map and enter queue map configuration mode. You can create up to three customized queue maps.
By default, the SmartEdge router maps priority groups, Differentiated Services Code Point (DSCP) classes, IP precedence values, Multiprotocol Label Switching (MPLS) experimental (EXP) bits, and Ethernet 802.1p bits to the specified number of queues as shown in Table 8.
Priority Group |
DSCP Value(1) |
IP Prec |
MPLS EXP |
802.1p |
8 Queues |
4 Queues |
2 Queues |
1 Queue |
---|---|---|---|---|---|---|---|---|
0 |
Network control |
7 |
7 |
7 |
Queue 0 |
Queue 0 |
Queue 0 |
Queue 0 |
1 |
Reserved |
6 |
6 |
6 |
Queue 1 |
Queue 1 |
Queue 1 |
Queue 0 |
2 |
Expedited Forwarding (EF) |
5 |
5 |
5 |
Queue 2 |
Queue 1 |
Queue 1 |
Queue 0 |
3 |
Assured Forwarding (AF) level 4 |
4 |
4 |
4 |
Queue 3 |
Queue 2 |
Queue 1 |
Queue 0 |
4 |
AF level 3 |
3 |
3 |
3 |
Queue 4 |
Queue 2 |
Queue 1 |
Queue 0 |
5 |
AF level 2 |
2 |
2 |
2 |
Queue 5 |
Queue 2 |
Queue 1 |
Queue 0 |
6 |
AF level 1 |
1 |
1 |
1 |
Queue 6 |
Queue 2 |
Queue 1 |
Queue 0 |
7 |
Default Forwarding (DF) |
0 |
0 |
0 |
Queue 7 |
Queue 3 |
Queue 1 |
Queue 0 |
(1) For more information about DSCP values, see RFC
2474, Definition of the Differentiated Services Field (DS Field)
in the IPv4 and IPv6 Headers and RFC 2475, An Architecture
for Differentiated Services.
Use the num-queues command (in queue map configuration mode) to specify the number of queues for the queue map, and then use the queue priority command (in num-queues configuration mode) to customize the mapping of one or more priority groups to each queue. Finally, use the queue-map command (in ATMWFQ policy, EDRR policy, PQ policy, or PWFQ policy configuration mode) to assign the queue map to a scheduling policy.
Use the no form of this command to remove the QoS queue map from the configuration.
The following example configures the QoS queue map, qmap, and changes the default mapping of priority groups to queues when 4 queues are configured:
[local]Redback(config)#qos queue-map qmap [local]Redback(config-queue-map)#num-queues 4 [local]Redback(config-num-queues)#queue 0 priority 0 1 [local]Redback(config-num-queues)#queue 1 priority 2 3 4 5 [local]Redback(config-num-queues)#queue 2 priority 6 [local]Redback(config-num-queues)#queue 3 priority 7
For traffic-managed ports, or the 802.1Q tunnels or permanent virtual circuits (PVCs) configured on them, the syntax is:
qos rate {maximum | minimum} kbps
no qos rate {maximum | minimum}
For all other Gigabit Ethernet ports, the syntax is:
qos rate maximum mbps burst bytes
no qos rate maximum
Sets the rate for outgoing traffic on a Gigabit Ethernet port, or on an 802.1Q tunnel, 802.1Q PVC, or hierarchical node group or node configured on a traffic-managed port.
maximum |
Specifies the maximum rate for the port, tunnel, PVC, or hierarchical node group, or hierarchical node. |
minimum |
Specifies the minimum rate for the port; available only for traffic-managed ports and the 802.1Q tunnels, PVCs, and hierarchical node groups, and hierarchical nodes configured on them. |
kbps |
Rate in kbps for traffic-managed ports, tunnels, PVCs, and hierarchical node groups. In hierarchical node and hierarchical node group configuration modes, the range of values is 64 to 1,000,000; in dot1q PVC and port configuration modes, the range of values is 10,000 to 1,000,000. |
mbps |
Rate in Mbps for all other Gigabit Ethernet ports. The range of values is 100 to 1,000; the default value is 1,000 (the full speed of the port). |
burst bytes |
Burst tolerance in bytes. For all other Gigabit Ethernet ports except traffic-managed ports, the range of values is 1 to 1,250,000,000. This construct is not available for traffic-managed ports. |
Outgoing traffic is transmitted at the full speed of the port.
Use the qos rate command to set the maximum rate for outgoing traffic on a Gigabit Ethernet port, or an 802.1Q tunnel, 802.1Q PVC, or hierarchical node group or node configured on a traffic-managed port. You can set the burst for any Gigabit Ethernet port, except for a traffic-managed port.
If you have not already entered the qos hierarchical mode strict command (in port or dot1q PVC configuration mode) for this tunnel or PVC, this command also makes the tunnel or PVC a node in the hierarchy. A Gigabit Ethernet 3 port is always a node at the top of the hierarchy.
Use the no form of this command to set the port, tunnel, or PVC to the default port rate.
The following example sets the maximum rate for outgoing traffic for port 1 on the Gigabit Ethernet traffic card in slot 14 to 600 Mbps with a burst size of 1,000 bytes:
[local]Redback(config)#port ethernet 14/1 [local]Redback(config-port)#qos rate maximum 600 burst 1000
qos {pd-value | all} to atm clp-value
{no | default} qos {clp-value | all}
Translates packet descriptor (PD) quality of service (QoS) values to Asynchronous Transfer Mode (ATM) cell loss priority (CLP) values on egress.
class map configuration
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard Differentiated Services Code Point (DSCP) marking label as defined in DSCP Class Keywords. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
clp-value |
Either 0 or 1. In case of network congestion, ATM cells marked with a value of 1 have been tagged to be dropped ahead of those with a value of 0. |
Egress ATM classification map entries use the default PD-to-CLP mapping described in Table 9.
Use the qos to atm command to translate PD QoS values to ATM CLP values on egress.
If you specify the all keyword, all valid PD values are mapped to the specified CLP value. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
Use the no or default form of this command to revert values for one or all map entries to their default values defined in Table 9.
ATM CLP Bit |
PD Priority Value |
PD Drop-Precedence Value |
AF Label |
QoS PD Value |
---|---|---|---|---|
0 |
1 |
2 |
AF11 |
10 |
1 |
0 |
0 |
DF |
0 |
qos {pd-value | all} to ethernet 802.1p-value
default qos {pd-value | all}
Translates packet descriptor (PD) quality of service (QoS) values to Ethernet 802.1p values on egress.
class map configuration
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard Differentiated Services Code Point (DSCP) marking label as defined in DSCP Class Keywords. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
802.1p-value |
An integer from 0 (lowest priority) to 7 (highest priority) representing the contents of the three user priority bits in the 802.1p virtual LAN (VLAN) Tag Control Information (TCI) field. |
None
Use the qos to ethernet command to define egress mappings from PD QoS values to Ethernet 802.1p values.
If you specify the all keyword, all valid PD values are mapped to the specified 802.1p value. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
Use the default form of this command to revert one or all Ethernet 802.1p values to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
The following example defines the classification map pd-to-8021p for Ethernet 802.1p values on egress, then maps the af33 and af21 PD QoS values to Ethernet 802.1p values 1 and 7, respectively:
[local]Redback(config)#qos class-map pd-to-8021p ethernet out [local]Redback(config-class-map)#qos af33 to ethernet 1 [local]Redback(config-class-map)#qos af21 to ethernet 7
qos {pd-value | all} to ip dscp-value
default qos {dscp-value | all}
Translates packet descriptor (PD) quality of service (QoS) values to Differentiated Services Code Point (DSCP) values in the IP header on egress.
class map configuration
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard DSCP marking label as defined in DSCP Class Keywords. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
dscp-value |
An integer from 0 to 63 representing the contents of the most significant six bits of the Type of Service (ToS) field in the IP header. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard DSCP marking label as defined in DSCP Class Keywords. |
None
Use the qos to ip command to translate PD QoS values to DSCP values in the IP header on egress.
If you specify the all keyword, all valid PD values are mapped to the specified IP header values. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
Use the default form of this command to revert values for one or all map entries to their default values, where each PD QoS value is mapped to the equivalent DSCP value.
The following example defines the classification map pd-to-dscp for IP values on egress, then maps the af13 PD QoS value to all DSCP values. It then overrides this mapping for PD QoS values 25 and df, which are mapped to DSCP values af21 and 1, respectively:
[local]Redback(config)#qos class-map pd-to-dscp ip out [local]Redback(config-class-map)#qos all to ip af13 [local]Redback(config-class-map)#qos 25 to ip af21 [local]Redback(config-class-map)#qos df to ip 1
qos {pd-value | all} to mpls exp-value
default qos {exp-value | all}
Translates packet descriptor (PD) quality of service (QoS) values to Multiprotocol Label Switching (MPLS) experimental (EXP) values on egress.
class map configuration
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard Differentiated Services Code Point (DSCP) marking label as defined in DSCP Class Keywords. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
exp-value |
An integer from 0 (lowest priority) to 7 (highest priority) representing the contents of the three EXP bits in the MPLS label header. |
None
Use the qos to mpls command to define egress mappings from PD QoS values to MPLS EXP values.
If you specify the all keyword, all valid PD values are mapped to the specified MPLS EXP value. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
Use the default form of this command to revert one or all MPLS EXP values to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
The following example defines the classification map pd-to-exp for MPLS values on egress, then maps the ef and df PD user priority bits to MPLS EXP bits 7 and 1, respectively:
[local]Redback(config)#qos class-map pd-to-exp mpls out [local]Redback(config-class-map)#qos ef to mpls 7 [local]Redback(config-class-map)#qos df to mpls 1
qos {pd-value | all} use-ip [class-map map-name]
default qos {pd-value | all}
For IP packets, determines packet descriptor (PD) values by mapping Differentiated Services Code Point (DSCP) values rather than quality of service (QoS) values on egress.
class map configuration
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard DSCP marking label as defined in DSCP Class Keywords. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
use-ip |
Enables a secondary mapping lookup using the packet’s DSCP bits as input. If no classification map is specified for the secondary lookup, the default DSCP-to-target mapping is used. When configuring a classification map for use as a secondary classification map on egress, omit the use-ip keyword. |
class-map map-name |
Optional. Name of the classification map. |
None
Use the qos use-ip command to determine the final 802.1p or Multiprotocol Label Switching (MPLS) experimental (EXP) value based on the DSCP value IP header for a packet with the specified PD QoS value on egress. Each packet is scheduled according to the PD value, but the MPLS or Ethernet header is marked with the egress packet’s DSCP values rather than the PD values.
If you specify the all keyword, all PD value entries use DSCP-based mappings. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
If you specify the optional class-map map-name construct, the DSCP values are mapped to 802.1p values according to the specified secondary classification map. The SmartEdge router interprets QoS-to-Ethernet or Qos-to-MPLS entries as if the QoS value actually specified a DSCP value. For example, the entry qos 1 to ethernet 2 actually maps DSCP value 1 to 802.1p value 2.
The secondary classification map must have the same values for the marking-type argument and mapping direction as the primary classification map and cannot include any use-ip classification map entries. If you do not specify a secondary classification map, the default DSCP-to-target mapping is used.
Use the default form of this command to revert one or all PD values to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
The following example defines the classification map pd-to-exp for MPLS values on egress and specifies 6P2D as the default mapping schema. Then, it specifies to map PD values to DSCP values rather than QoS values, using the secondary classification map dscp-to-exp for translation. Finally, it maps PD bit af33 to MPLS bit 4, and QoS bit to the corresponding DSCP value:
[local]Redback(config)#qos class-map pd-to-exp mpls out [local]Redback(config-class-map)#mapping-schema 6P2D [local]Redback(config-class-map)#qos all use-ip dscp-to-exp [local]Redback(config-class-map)#qos af33 to mpls 4 [local]Redback(config-class-map)#qos 13 use-ip
qos weight weight
no qos weight weight
Assigns to this circuit a relative weight that is used to calculate a traffic ratio for all circuits configured on a traffic-managed port.
weight |
Relative weight that is assigned to this circuit. The range of values is 1 to 4096. |
All circuits configured on this port have the same weight.
Use the qos weight command to assign to this circuit a relative weight that is used to calculate a traffic ratio for all circuits configured on a traffic-managed port.
You can assign a relative weight, or you can set a minimum absolute rate, for the circuit, using the qos rate command (in dot1q PVC, hierarchical node, or hierarchical node group configuration mode), but you cannot do both; the relative weight and minimum absolute rate are mutually exclusive.
You can assign a relative weight (using this command) and set a maximum absolute rate for the circuit, using the qos rate command (in dot1q PVC, hierarchical node, or hierarchical node group configuration mode).
For 802.1Q permanent virtual circuits (PVCs), this command can be used to configure both static and on-demand PVCs.
Use the no form of this command to specify the default condition.
The following example specifies a weight of 3 for the hierarchical nodes dslam 1 through dslam 5:
[local]Redback(config)#port ethernet 5/2 [local]Redback(config-port)#qos rate maximum 100000000 [local]Redback(config-port)#qos node-group home 1 [local]Redback(config-h-node)#qos hierarchical mode strict [local]Redback(config-h-node)#qos node dslam 1 through 5 [local]Redback(config-h-node)#qos weight 3
query-interval interval
Configures the interval at which IGMP group-specific host query messages are sent on a specified bridge.
IGMP snooping bridge configuration
interval |
Interval at which IGMP group-specific host query messages are sent. The interval ranges from 1 through 65535 seconds. The default interval is 125 seconds. |
The default interval is 125 seconds.
Use the query-interval command to configure the interval at which IGMP group-specific host query messages are sent on a specified bridge. Range is from 1 through 65535 seconds.
The following example shows how to configure a bridge called sj1 to send IGMP group-specific host query messages every 185 seconds:
[local]Redback(config-ctx)#bridge sj1 [local]Redback(config-bridge)#igmp snooping [local]Redback(config-igmp-snooping)#query-interval 185
query-solicitation
no query-solicitation
Enables and disables the generation of IGMP query solicitation messages by a bridge.
This command has no keywords or arguments.
The generation of IGMP query solicitation messages by a bridge is enabled.
Use the query-solicitation command to enable the generation of IGMP query solicitation messages by a bridge. Note that the generation of IGMP query solicitation messages by a bridge is enabled on all bridges by default; use the query-solicitation command only if IGMP query solicitation was disabled on the bridge with the no query-solicitation command.
Bridges that have IGMP snooping enabled forward query solicitation messages to all IGMP routers in a system. If the interface over which an IGMP query solicitation message is received has IGMP query solicitation enabled, the router responds to IGMP query messages with an IGMP general query message.
Use the no form of this command to disable the generation of IGMP query solicitation messages by a bridge.
The following example shows how to enable the generation of IGMP query solicitation messages by a bridge (br-sj-1) on which the generation of IGMP query solicitation messages was disabled:
[local]Redback(config-ctx)#bridge br-sj-1 [local]Redback(config-bridge)#igmp snooping [local]Redback(config-igmp-snooping)#query-solicitation
queue 0 mode {alternate | strict}
default queue 0 mode
Defines the mode of the Asynchronous Transfer Mode weighted fair queuing (ATMWFQ) algorithm for queue 0.
ATMWFQ policy configuration
alternate |
Services queue 0 and the other queues configured on the circuit in alternating fashion. |
strict |
Indicates that queue 0 always has priority over all other queues configured on the circuit. |
The default mode is alternate.
Use the queue 0 mode command to define the mode of the ATMWFQ policy algorithm for queue 0.
In alternate mode, the servicing of queues alternates between queue 0 and the remaining queues. Queue 0 is served, then the next queue is served. Queue 0 is served again, and the next queue in turn is served, and so on. For example, if there are 4 queues configured, the order of servicing will be q0, q1, q0, q2, q0, q3, q0, q1, and so on.
In strict mode, high-priority queue 0 is serviced immediately and other queues are serviced in a round-robin fashion; in other words, queue 0 always has priority over all other queues configured on the circuit.
Use the default form of this command to return the ATMWFQ algorithm to alternate mode.
The following example configures the ATMWFQ policy to use strict mode:
[local]Redback(config)#qos policy atm-wfq-1 atmwfq [local]Redback(config-policy-atmwfq)#queue 0 mode strict
queue queue-num congestion epd threshold max
{no | default} queue queue-num congestion epd
Configure early packet discard (EPD) parameters for this quality of service (QoS) Asynchronous Transfer Mode weighted fair queuing (ATMWFQ) policy.
queue-num |
Queue number. The range of values is 0 to 7. |
threshold max |
EPD threshold value. The number of packets (equivalent to six ATM cells) that can be in the queue before new incoming packets begin to be discarded. The range of values is 2 to 10,000; the default value is 26. |
Random early discard (RED) is enabled for Asynchronous Transfer Mode (ATM) permanent virtual circuits (PVCs) (on ATM DS-3 or second-generation ATM OC traffic cards only) that reference the ATMWFQ policy.
Use the queue congestion epd command to configure EPD parameters for the specified ATMWFQ policy.
With EPD, a threshold is set for the number of packets (equivalent to 6 ATM cells) that can be in the queue before any new incoming packets begin to be discarded. Incoming packets are broken into cells as they are being placed in the queue. If there is enough space in the queue to accept the first cell of a packet, the remaining cells in the packet are admitted. If not, the entire packet is dropped. When an entire packet is dropped, the queue is placed into EPD mode until enough packets have been sent out such that the number of packets in the queue is below the threshold max value.
Use the no or default form of this command to use the default EPD value.
Caution! | ||
Risk of dropping packets. Modifying the parameters of an ATMWFQ
policy will momentarily interrupt the traffic on all ATM PVCs using
the policy. To reduce the risk, use caution when modifying ATMWFQ
policy parameters.
|
The following example specifies the EPD threshold for the atmwfq-1 policy for queue 4:
[local]Redback(config)#qos policy atmwfq-1 atmwfq [local]Redback(config-policy-atmwfg)#queue 4 congestion epd threshold 5200
queue queue-num congestion {epd threshold max | red max-threshold max min-threshold min probability prob weight weight-exp}
queue queue-num congestion {epd | red}
Configure early packet discard (EPD) parameters or modify the weighted random early detection (RED) for this quality of service (QoS) Asynchronous Transfer Mode (ATM) weighted-fair queueing (WFQ) policy.
queue-num |
Queue number. The range of values is 0 to 7. |
epd threshold max |
EPD threshold value. The number of packets (equivalent to six ATM cells) that can be in the queue before new incoming packets begin to be discarded. Incoming packets are broken into cells as they are being placed in the queue. If there is enough space in the queue to accept the first cell of a packet, the remaining cells in the packet are admitted. If not, the entire packet is dropped. When an entire packet is dropped, the queue is placed into EPD mode until enough packets have been sent out such that the number of packets in the queue is below the threshold max value. |
red |
Specifies that RED parameters are to be modified. |
min-threshold min |
Average queue occupancy in packets below which no packets are dropped. The range of values is 1 to 9,999; the default value is eight packets. |
max-threshold max |
Average queue occupancy in packets above which all packets are dropped. As the average occupancy approaches the maximum threshold value, packets are dropped with increasing probability, as a function of the value of the probability prob value. The range of values is 2 to 10,000; the default value is 26 packets. |
probability prob |
Inverse of the probability of dropping a packet as the average queue occupancy approaches the maximum threshold. The higher the value of the prob argument, the lower the probability of a packet being dropped. The resulting probability (1/prob) is the fraction of packets dropped when the average queue depth is at the maximum threshold. The range of values is 8 to 32,768; the default value is 16. |
weight weight-exp |
Exponent representing the inverse of the exponentially weighted moving average of traffic. The average queue occupancy is computed as a moving average of the instantaneous queue occupancy. Traffic weight is expressed as a unit of average packet size. The average packet size is equivalent to 6 ATM cells. The larger the value of the weight-exp argument, the longer term the average. The range of values is 7 to 10; the default value is 9. |
RED is enabled for ATM PVCs (ATM DS-3 or second-generation ATM OC cards only) that reference the ATM WFQ policy.
Use the queue congestion command to configure EPD parameters or to modify RED parameters for the specified ATM WFQ policy.
With EPD, a threshold is set for the number of packets (equivalent to 6 ATM cells) that can be in the queue before any new incoming packets begin to be discarded. Incoming packets are broken into cells as they are being placed in the queue. If there is enough space in the queue to accept the first cell of a packet, the remaining cells in the packet are admitted. If not, the entire packet is dropped. When an entire packet is dropped, the queue is placed into EPD mode until it enough packets have been sent out such that the number of packets in the queue is below the threshold.
RED signals to sources of traffic that the network is on the verge of entering a congested state. This signaling is accomplished by dropping packets with a probability that varies as a function of how many packets are waiting in a queue at any particular time, and of the values of the threshold max, threshold min, probability prob, and weight weight-exp values.
Use the default or no form of this command to use the default EPD or RED value.
Caution! | ||
Risk of dropping packets. Modifying the parameters of an ATMWFQ
policy will momentarily interrupt the traffic on all ATM PVCs using
the policy. To reduce the risk, use caution when modifying ATMWFQ
policy parameters.
|
The following example specifies the RED parameters for an existing profile, atm-pro:
[local]Redback(config)#qos policy atmwfq-1 atmwfq [local]Redback(config-policy-atmwfg)#queue congestion red min-threshold 1 max-threshold 255 probability 15 weight 10
queue queue-num depth packets count
{no | default} queue queue-num depth
Specifies the depth for the specified queue.
queue-num |
Queue number. The range of values is 0 to 7. |
packets count |
Depth of the queue, expressed as the number of packets. The range of values depends on the command mode:
|
In EDRR and PQ policy configuration modes, if you do not configure a depth, the default value for the port type is used; see Table 10. In congestion map configuration mode for a priority weighted fair queuing (PWFQ) policy, the default value is 4,000.
Use the queue depth command to specify the depth for the specified queue.
The queue that you specify in the queue-num argument is the one to which the depth is applied. You can enter this command multiple times to set the depth for each queue. Use the num-queues command (in EDRR policy or PQ policy configuration mode) to specify the number of queues available; the number of queues is always eight in congestion map configuration mode.
For EDRR and PQ policy configuration modes, the default and maximum allowable values are functions of the port type to which the policy is attached. The port type, and therefore the default and maximum allowable values, are not known at the time the queue depth command is entered.
Table 10 lists the default and maximum queue depth values for the various port types.
Port Type(1) |
Default Depth Value |
Maximum Depth Value |
---|---|---|
First-generation ATM OC-3 |
1,024 |
4,064 |
First-generation ATM OC-12 |
4,064 |
4,064 |
DS-0 |
256 |
4,064 |
DS-1 |
256 |
4,064 |
DS-3 |
1,024 |
4,064 |
E1 |
256 |
4,064 |
E3 |
1,024 |
4,064 |
Ethernet |
1,024 |
4,064 |
Gigabit Ethernet (GE) |
4,064 |
4,064 |
POS OC-3c |
1,024 |
4,064 |
POS OC-12c |
4,064 |
32,736 |
POS OC-48c |
32,736 |
32,736 |
(1) PQ and EDRR policies are not supported on ATM
DS-3 or second-generation ATM OC traffic cards.
Caution! | ||
Risk of performance loss. Because some traffic cards queue a maximum
of 4,064 packets, it is possible to configure a depth that is inappropriate
for the type of port to which the policy is later attached. In that
case, the system displays a warning message when you attach the policy
to the port. To reduce the risk, consider the queue depth allowed
per port type.
|
Use the no or default form of this command to specify the default value.
The following example sets the depth for queue 5. The depth is rounded to the nearest increment of 32:
[local]Redback(config-policy-pq)#queue 5 depth packets 550
queue queue-num exponential-weight weight-exp
no queue queue-num exponential-weight
Specifies a weight for the specified queue.
queue-num |
Queue number. The range of values is 0 to 7. |
weight-exp |
Exponent representing the inverse of the exponentially weighted moving average. The range of values depends on the type of congestion avoidance map:
|
The exponential weight is assigned the default value, depending on the type of congestion map.
Use the queue exponential-weight command to specify a weight for the specified queue. The queue must be one that you have configured with random early detection (RED) parameters. The weight that you specify applies to every RED profile (default, profile-1, profile-2) for this queue.
The average queue occupancy is computed as a moving average of the instantaneous queue occupancy. Use the weight-exp argument to set the inverse of the exponential moving average. The larger the value of the weight-exp argument, the longer term the average.
The average queue size is based on the previous average and the current size of the queue according to the following formula:
average = (old_average * (1 - 0.5**w)) + (current_queue_size * ½**w)
where w is the value of the weight-exp argument * is the multiplication operator ** is the exponential operator
Use the no form of this command to specify the default exponential weight for the type of congestion map.
The following example specifies the weights for the default profile in the map-red8 congestion avoidance map:
[local]Redback(config)#qos congestion-avoidance-map map-red8 [local]Redback(config-congestion-map)#queue 0 exponential-weight 1 [local]Redback(config-congestion-map)#queue 1 exponential-weight 2 [local]Redback(config-congestion-map)#queue 2 exponential-weight 1 [local]Redback(config-congestion-map)#queue 3 exponential-weight 1 [local]Redback(config-congestion-map)#queue 4 exponential-weight 10 [local]Redback(config-congestion-map)#queue 5 exponential-weight 1 [local]Redback(config-congestion-map)#queue 6 exponential-weight 1 [local]Redback(config-congestion-map)#queue 7 exponential-weight 1
queue-map map-name
no queue-map map-name
Assigns a queue map to the quality of service (QoS) scheduling policy.
map-name |
Queue map name. |
No queue map is assigned to any QoS scheduling policy.
Use the queue-map command to assign a queue map to the specified QoS scheduling policy.
To create a queue map, enter the qos queue-map command (in global configuration mode). To specify the number of queues for the queue map, enter the num-queues command (in queue map configuration mode). Use the queue priority command (in num-queues configuration mode) to customize the mapping of a priority group to each queue.
Use the no form of this command to delete the queue map from the QoS policy.
The following example assigns the queue map, q-queue-map, to the enhanced deficit round-robin (EDRR) configuration policy, qos-edrr-test:
[local]Redback(config)#qos policy qos-edrr-test edrr [local]Redback(config-policy-edrr)#queue-map q-queue-map
In num-queues configuration mode, the syntax is:
queue queue-num priority group-num [group-num2[...]]
no queue queue-num priority
In PWFQ policy configuration mode, the syntax is:
queue queue-num priority group-num weight weight
no queue queue-num priority
In num-queues configuration mode, customizes the mapping of quality of service (QoS) priority groups to the specified queue. In PWFQ policy configuration mode, assigns a priority group number and relative weight inside the assigned priority group to the specified queue.
queue-num |
Queue number. The range of values is 0 to 7. |
group-num |
Priority group number. The range of values is 0 to 7. |
group-num2 group-num3.. |
Optional. Additional priority group numbers separated by spaces. The range of values is 0 to 7. |
weight weight |
Relative weight that is assigned to this queue for the specified priority group; available only for queues defined in priority weighted fair queuing (PWFQ) policies. The range of values is 5 to 100. |
In num-queues configuration mode, the SmartEdge router assigns a preset mapping of priority groups to queues; for information about the default values, see the qos queue-map command in the Command List. In PWFQ policy configuration mode, there is no default.
Use the queue priority command in num-queues configuration mode to customize the mapping of one or more priority groups to the specified queue. In PWFQ policy configuration mode, use this command to assign a priority group number and relative weight inside the assigned priority group to the specified queue.
For queue maps:
For PWFQ policies:
The following example defines 4 queues for the PWFQ policy, pwfq4, and assigns them to priority groups 0 and 1 with relative weights 70, 30, 60, 40:
[local]Redback(config)#qos policy pwfq4 pwfq [local]Redback(config-policy-pwfq)#num-queues 4 [local]Redback(config-policy-pwfq)#queue 0 priority 0 weight 70 [local]Redback(config-policy-pwfq)#queue 1 priority 0 weight 30 [local]Redback(config-policy-pwfq)#queue 2 priority 1 weight 60 [local]Redback(config-policy-pwfq)#queue 3 priority 1 weight 40 [local]Redback(config-policy-pwfq)#
In this example, in priority group 0 queue 0 receives 70% traffic share and queue 1 receives 30% traffic share; in priority group 1 queue 2 receives 60% traffic share and queue 3 receives 40% traffic share.
The following example configures the queue maps, Custom2, Custom4, Custom8, to customize the mapping of priority groups to queues. The assignment of priority group to queue number varies according to the number of queues configured. The custom mapping for 4 queues is referenced by the QoS policy, myPolicyPQ:
[local]Redback(config)#qos queue-map Custom2 [local]Redback(config-queue-map)#num-queues 2 [local]Redback(config-num-queues)#queue 0 priority 0 [local]Redback(config-num-queues)#queue 1 priority 1 2 3 4 5 6 7 [local]Redback(config-num-queues)#exit [local]Redback(config)#qos queue-map Custom4 [local]Redback(config-queue-map)#num-queues 4 [local]Redback(config-num-queues)#queue 0 priority 0 [local]Redback(config-num-queues)#queue 1 priority 1 2 [local]Redback(config-num-queues)#queue 2 priority 3 4 5 6 [local]Redback(config-num-queues)#queue 3 priority 7 [local]Redback(config-num-queues)#exit [local]Redback(config)#qos queue-map Custom8 [local]Redback(config-queue-map)#num-queues 8 [local]Redback(config-num-queues)#queue 0 priority 0 [local]Redback(config-num-queues)#queue 1 priority 1 [local]Redback(config-num-queues)#queue 2 priority 2 [local]Redback(config-num-queues)#queue 3 priority 3 [local]Redback(config-num-queues)#queue 4 priority 4 [local]Redback(config-num-queues)#queue 5 priority 5 [local]Redback(config-num-queues)#queue 6 priority 6 [local]Redback(config-num-queues)#queue 7 priority 7 [local]Redback(config-num-queues)#exit [local]Redback(config)#qos policy MyPolicy pq [local]Redback(config-policy-pq)#queue-map Custom4 [local]Redback(config-policy-pq)#num-queues 4 [local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#bind interface BackboneOne local [local]Redback(config-port)#qos policy queuing MyPolicy
queue priority-group group-num {rate kbps [exceed] | rate percentage value}
no queue priority-group group-num
Sets the rate for the specified priority group.
group-num |
Priority group number. The range of values is 0 to 7. |
rate kbps |
Absolute rate in kilobits per second for the specified priority group; the range of values is 64 to 1,000,000. |
exceed |
Optional. Allows the traffic rate to be exceeded for the specified priority group. The default condition is to not allow the traffic rate to be exceeded. |
rate percentage value |
Relative rate, as a percentage of the policy rate, for the specified priority group; the range of values is 1 to 100. |
None
Use the queue priority-group command to set the rate for the specified priority group. You enter this command for each priority group created for this priority weighted fair queuing (PWFQ) policy.
A priority group is a set of queues that all have the same priority group number assigned to them with the queue priority command (in PWFQ policy configuration mode). You enter this command for each priority group.
Use the rate kbps construct to specify an absolute rate for the priority group; use the rate percentage construct to specify a relative rate. You specify the policy rate using the rate command (in PWFQ policy configuration mode).
Use the no form of this command to delete the priority group from the policy.
The following example sets the rate and burst tolerance for the priority groups in the PWFQ policy, pwfq4:
[local]Redback(config)#qos policy pwfq4 pwfq [local]Redback(config-policy-pwfq)#num-queues 4 [local]Redback(config-policy-pwfq)#queue 0 priority 0 weight 70 [local]Redback(config-policy-pwfq)#queue 1 priority 0 weight 30 [local]Redback(config-policy-pwfq)#queue 2 priority 1 weight 60 [local]Redback(config-policy-pwfq)#queue 3 priority 1 weight 40 [local]Redback(config-policy-pwfq)#queue priority-group 0 rate 1800 [local]Redback(config-policy-pwfq)#queue priority-group 1 rate 1600 [local]Redback(config-policy-pwfq)#
The following example sets relative rates for the priority groups in the PWFQ policy, pwfq-percent:
[local]Redback(config)#qos policy pwfq2 pwfq [local]Redback(config-policy-pwfq)#rate maximum 6000 [local]Redback(config-policy-pwfq)#num-queues 4 [local]Redback(config-policy-pwfq)#queue 0 priority 0 weight 100 [local]Redback(config-policy-pwfq)#queue 1 priority 1 weight 100 [local]Redback(config-policy-pwfq)#queue 2 priority 2 weight 60 [local]Redback(config-policy-pwfq)#queue 3 priority 2 weight 40 [local]Redback(config-policy-pwfq)#queue priority-group 0 rate percentage 10 [local]Redback(config-policy-pwfq)#queue priority-group 1 rate percentage 20 [local]Redback(config-policy-pwfq)#
queue queue-num rate kbps burst bytes [no-exceed]
no queue queue-num rate
Establishes the rate limit and burst tolerance for the specified quality of service (QoS) priority queuing (PQ) policy queue.
queue-num |
Number of the priority queue for which you are setting the rate limit and burst tolerance. The range of values is 0 to 7. |
rate kbps |
Rate in kilobits per second. The range of values is 56 to 1,000,000. |
burst bytes |
Burst tolerance in bytes. The range of values is 1 to 1,250,000,000. |
no-exceed |
Optional. Specifies that the rate is not to be exceeded, even if there are no other traffic classes waiting to be sent. |
No limit is placed on the rate of any individual queue.
Use the queue rate command to establish the rate limit and burst tolerance for the specified PQ policy queue. A reasonable guideline for burst tolerance is 10 times the link maximum transmission unit (MTU), or approximately 15,000 to 20,000 bytes. For a DS-1 circuit, the minimum rate is 56 kbps; for all other circuits, the minimum rate is 1,000 kbps.
Use the no form of this command to return the rate limit and burst tolerance to their default values.
The following example sets the rate limit and burst tolerance for queue 4 for the PQ policy:
[local]Redback(config-policy-pq)#queue 4 rate 10000 burst 12000 no-exceed
In congestion map configuration mode, the command syntax is:
queue queue-num red profile [dscp class1[class2[...]]] max-threshold max min-threshold min probability prob weight weight-exp
no queue queue-num red profile
In EDRR and PQ policy configuration modes, the command syntax is:
queue queue-num red max-threshold max min-threshold min probability prob weight weight-exp
no queue queue-num red
In congestion map configuration mode, sets the random early detection (RED) parameters for the specified queue in the specified RED drop profile for the congestion avoidance map. In EDRR and PQ policy configuration modes, sets the RED parameters for the specified quality of service (QoS) queue.
queue-num |
Queue number. The range of values is 0 to 7. |
profile |
Specifies the RED profile in the congestion avoidance map, according to one of the following keywords:
|
dscp class1 class2.... |
Optional. Differentiated Services Code Point (DSCP) classes, separated by spaces; the range of values is: |
max-threshold max |
Average queue occupancy in packets above which all packets are dropped. The range of values is:
|
min-threshold min |
Average queue occupancy in packets below which no packets are dropped. The range of values is:
|
probability prob |
Inverse of the probability of dropping a packet as the average queue occupancy approaches the maximum threshold. The resulting probability (1/prob) is the fraction of packets dropped when the average queue depth is at the maximum threshold. The range of values is:
|
weight weight-exp |
Exponent representing the inverse of the exponentially weighted moving average. The range of values is:
|
For EDRR and PQ policies, RED is disabled. For a congestion avoidance map, none; you must enter a value for each argument and construct.
Use the queue red command in congestion map configuration mode to set the RED parameters for the specified queue in the RED drop profile for the congestion avoidance map. Use the queue red command in EDRR or PQ policy configuration mode to set the RED parameters for the specified QoS queue.
RED parameters specify how buffer utilization is to be managed under congestion by signaling to the sources of traffic that the network is on the verge of entering a congested state. This signaling is accomplished by dropping packets with a probability that varies as a function of how many packets are waiting in a queue at any particular time, and of the values of the max, min, and weight-exp arguments.
Use the profile argument to specify one of three RED profiles for the RED parameters for this queue. Each queue supports up to three RED profiles.
Use the dscp class1 class2... construct to specify a list of DSCP classes for which the RED parameters pertain. Table 11 lists the keywords for the DSCP classes.
DSCP Class |
Keyword |
DSCP Class |
Keyword |
---|---|---|---|
Assured Forwarding (AF) Class 1/ Drop precedence 1 |
af11 |
Class Selector 0 (same as default forwarding) |
cs0 (same as df) |
AF Class 1/Drop precedence 2 |
af12 |
Class Selector 1 |
cs1 |
AF Class 1/Drop precedence 3 |
af13 |
Class Selector 2 |
cs2 |
AF Class 2/Drop precedence 1 |
af21 |
Class Selector 3 |
cs3 |
AF Class 2/Drop precedence 2 |
af22 |
Class Selector 4 |
cs4 |
AF Class 3/Drop precedence 3 |
af23 |
Class Selector 5 |
cs5 |
AF Class 3/Drop precedence 1 |
af31 |
Class Selector 6 |
cs6 |
AF Class 3/Drop precedence 2 |
af32 |
Class Selector 7 |
cs7 |
AF Class 3/Drop precedence 3 |
af33 |
Default Forwarding (same as Class Selector 0) |
df (same as cs0) |
AF Class 4/Drop precedence 1 |
af41 |
Expedited Forwarding |
ef |
AF Class 4/Drop precedence 2 |
af42 |
|
|
AF Class 4/Drop precedence 3 |
af43 |
|
|
Use the max-threshold max construct to set the average queue occupancy in packets above which the probability of a packet being dropped is 100%. As the average occupancy approaches the maximum threshold value, packets are dropped with increasing probability, as a function of the value of the prob argument. For EDRR and PQ policies, the value of the max argument must be less than the value of the count argument in the queue depth command.
Use the min-threshold min construct to set the average queue occupancy in packets at or below which the probability of a packet being dropped is 0%. The value of the min argument must be less than the value of the max argument in this command, and, for EDRR and PQ policies, less than the value of the count argument in the queue depth command.
Use the probability prob construct to establish the probability of a packet being dropped as the average queue occupancy approaches the maximum threshold value. The value of the prob argument is the inverse of the probability of a packet being dropped. The higher the value of the prob argument, the lower the probability of a packet being dropped.
The average queue occupancy is computed as a moving average of the instantaneous queue occupancy. Use the weight weight-exp construct to set the inverse of the exponential moving average. The larger the value of the weight-exp argument, the longer term the average.
The average queue size is based on the previous average and the current size of the queue according to the following formula:
average = (old_average * (1 - 0.5**w)) + (current_queue_size * ½**w)
where w is the value of the weight-exp argument * is the multiplication operator ** is the exponential operator
In congestion map configuration mode, use the no form of this command to remove the queue from the specified profile. In EDRR and PQ policy configuration modes, use the no form of this command to disable RED parameters.
The following example creates the PQ policy, red, and establishes RED parameters for each of the eight queues, so that higher priority traffic has a lower probability of being dropped, while lower priority traffic has a higher probability of being dropped. The example then attaches the policy to a Packet over SONET/SDH (POS) port:
[local]Redback(config)#qos policy red pq [local]Redback(config-policy-pq)#queue 0 red probability 10 weight 12 min-threshold 1900 max-threshold 5200 [local]Redback(config-policy-pq)#queue 1 red probability 9 weight 12 min-threshold 1850 max-threshold 5200 [local]Redback(config-policy-pq)#queue 2 red probability 8 weight 12 min-threshold 1800 max-threshold 5200 [local]Redback(config-policy-pq)#queue 3 red probability 7 weight 12 min-threshold 1750 max-threshold 5200 [local]Redback(config-policy-pq)#queue 4 red probability 6 weight 12 min-threshold 1700 max-threshold 5200 [local]Redback(config-policy-pq)#queue 5 red probability 5 weight 12 min-threshold 1650 max-threshold 5200 [local]Redback(config-policy-pq)#queue 6 red probability 4 weight 12 min-threshold 1600 max-threshold 5200 [local]Redback(config-policy-pq)#queue 7 red probability 1 weight 12 min-threshold 1550 max-threshold 5200 [local]Redback(config-policy-pq)#exit [local]Redback(config)#port pos 2/1 [local]Redback(config-port)#qos policy queuing red
The following example specifies the RED parameters for the default profile and queues 0 through 7 in the congestion avoidance map, map-red:
[local]Redback(config)#qos congestion-avoidance-map map-red8 atmwfq [local]Redback(config-congestion-map)#queue 0 red default probability 10 weight 12 min-threshold 1900 max-threshold 5200 [local]Redback(config-congestion-map)#queue 1 red default probability 9 weight 12 min-threshold 1850 max-threshold 5200 [local]Redback(config-congestion-map)#queue 2 red default probability 8 weight 12 min-threshold 1800 max-threshold 5200 [local]Redback(config-congestion-map)#queue 3 red default probability 7 weight 12 min-threshold 1750 max-threshold 5200 [local]Redback(config-congestion-map)#queue 4 red default probability 6 weight 12 min-threshold 1700 max-threshold 5200 [local]Redback(config-congestion-map)#queue 5 red default probability 5 weight 12 min-threshold 1650 max-threshold 5200 [local]Redback(config-congestion-map)#queue 6 red default probability 4 weight 12 min-threshold 1600 max-threshold 5200 [local]Redback(config-congestion-map)#queue 7 red default probability 1 weight 12 min-threshold 1550 max-threshold 5200
queue queue-num weight traffic-weight
default queue queue-num weight
Specifies the weight of the specified Asynchronous Transfer Mode weighted fair queuing (ATMWFQ), enhanced deficit round-robin (EDRR), or modified deficit round-robin (MDRR) queue.
queue-num |
Queue number. The range of values is 0 to 7. |
traffic-weight |
For ATMWFQ policies, the traffic weight is expressed as a unit of average packet size. The average packet size is equivalent to 6 ATM cells. For example, a traffic weight of 2,000 is equivalent to 12,000 ATM cells. The range of values is 1 to 5,461; the default value is 2. For EDRR and MDRR policies, the traffic weight is expressed as a percentage of bandwidth. The range of configurable values is 5 to 100%. The default value for an EDRR policy is either 5% of the line capacity of the port or, if you have configured the circuit using the rate command (in EDRR policy configuration mode), 5% of the value you specified for the kbps argument. The default value for MDRR is 0%. |
Default values for the traffic-weight argument are specified in the Syntax Description section.
Use the queue weight command to specify the weight of the specified ATMWFQ, EDRR, or MDRR queue.
Caution! | ||
Risk of packet loss. Modifying the parameters of an ATMWFQ policy
will momentarily interrupt the traffic on all Asynchronous Transfer
Mode (ATM) permanent virtual circuits (PVCs) using the policy. To
reduce the risk, use caution when modifying ATMWFQ policy parameters.
|
Caution! | ||
Risk of performance loss. For EDRR and MDRR policies, you must
assign a weight to each queue that is in use, as specified by either
the default queue map or a customized queue map. To reduce the risk,
ensure that you assign a weight to each queue.
|
Use the default form of this command to return the queue to its default weight.
The following example provides queue number 3 with 30% of the bandwidth of the circuit to which the EDRR policy, scheduling1, is attached:
[local]Redback(config)#qos policy scheduling1 edrr [local]Redback(config-policy-edrr)#queue 3 weight 30