Services are created in the administratively down (shutdown) state. When a
no shutdown command is entered, the service becomes administratively up and then tries to enter the operationally up state. Default administrative states for services and service entities is described below in Special Cases.
The no form of this command places the entity into an administratively enabled state.
This command creates a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
apipe service-id [customer
customer-id] [vpn
vpn-id] [vc-type
{atm-vcc
| atm-sdu
| atm-vpc
| atm-cell
}] [vc-switching
]
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
cpipe service-id [customer
customer-id] [vpn
vpn-id] [vc-type
{satop-e1
| satop-t1 | satop-e3 | satop-t3
[vc-switching
] | cesopsn
| cesopsn-cas
}] [vc-switching
] [create
]
This command configures a Circuit Emulation Services instance. When a service is created, the customer keyword and
customer-id must be specified and associates the service with a customer. The
customer-id must already exist having been created using the
customer command in the service context. Once a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect
customer-id specified will result in an error.
The no form of this command deletes the service instance with the specified
service-id. The service cannot be deleted until the service has been shutdown.
|
Values
|
service-id: 1 — 2147483648 svc-name: Specifies an existing service name up to 64 characters in length.
|
|
Values
|
satop-e1: unstructured E1 circuit emulation service satop-t1: unstructured DS1 circuit emulation service satop-e3: unstructured E3 circuit emulation service satop-t3: unstructured DS3 circuit emulation service cesopsn: basic structured n*64 kbps circuit emulation service c esopsn-cas: structured n*64 kbps circuit emulation service with signaling
|
epipe service-id customer
customer-id [vpn
vpn-id] [vc-switching
] [create
]
This command configures an Epipe service instance. This command is used to configure a point-to-point epipe service. An Epipe connects two endpoints defined as Service Access Points (SAPs). Both SAPs may be defined in one 7750 SR or they may be defined in separate devices connected over the service provider network. When the endpoint SAPs are separated by the service provider network, the far end SAP is generalized into a Service Distribution Point (SDP). This SDP describes a destination and the encapsulation method used to reach it.
When a service is created, the customer keyword and
customer-id must be specified and associates the service with a customer. The
customer-id must already exist having been created using the
customer command in the service context. Once a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.
Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect
customer-id specified will result in an error.
The no form of this command deletes the epipe service instance with the specified
service-id. The service cannot be deleted until the service has been shutdown.
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
fpipe service-id [customer
customer-id] [vpn
vpn-id] [vc-type
{fr-dlci
}] [vc-switching
]
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
ipipe service-id [customer
customer-id] [create
] [vpn
vpn-id] [vc-switching
]
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
The no form of this command removes the string from the configuration.
The tools perform commands can be used to control the application of changes in pw-template for BGP-VPWS.
The no form of the command removes the values from the configuration.
Format: Six bytes, other 2 bytes of type will be automatically generated.
route-target {ext-community|{[export
ext-community][import
ext-community]}}
The no form of the command removes the configured remote-ve-name from the bgp vpws node. It can be used when the BGP VPWS status is either shutdown or “no shutdown”.
The no form of the command removes the configured ve-id. It can be used just when the BGP VPWS status is shutdown. Command “no shutdown” cannot be used if there is no ve-id configured.
The no form of the command removes the ve-name.
The no form of the command enables the BGP VPWS addressing and the related BGP advertisement. The associated BGP VPWS MP-REACH-NLRI will be advertised in an update message and the corresponding received NLRIs must be considered to instantiate the data plane.
The no form of the command removes the name from the configuration.
The no form of the command reverts the default.
The no form of the command removes the SAP ID from the configuration.
The no form of the command removes the value from the configuration.
[no
] ce-address-discovery
[ipv6
]
The ipv6 keyword enables IPv6 CE address discovery support on the Ipipe so that both IPv4 and IPv6 address discovery are supported. If the
ipv6 keyword is not included, then only IPv4 address discovery is supported and IPv6 packets are dropped. This feature requires IOM2 or better. It requires chassis mode C or above. If any Ipipe services require IPv6 support, then all network ports on the node must be configured on 7750 IOM-3-XPs.
[no
] stack-capability-signaling
When enabled, the 7750 includes the stack capability TLV with the IPv6 stack bit set according to the ce-address-discovery ipv6 keyword, and also checks the value of the stack-capability TLV received from the far end.
This command must be blocked if no ce-address-discovery is specified, or the
ipv6 keyword is not included with the
ce-address-discovery command.
This feature requires IOM2 or better. It requires chassis mode C or above. If any Ipipe services require IPv6 support, then all network ports on the node must be configured on 7750 IOM-3-XPs.
[no
] endpoint
endpoint-name
The no form of this command implies the use of existing hashing options.
tunnel service-id backbone-dest-mac
ieee-address isid
ISID
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
By default, when the MC-LAG transitioned the LAG subgroup which hosts the SAP for this VLL endpoint from active to
standby, the node sends immediately new T-LDP status bits indicating the new value of "standby" over the spoke SDPs which are on the mate-endpoint of the VLL. The same applies when any object in the endpoint changes an operational state from up to down.
0 — A value of zero means that when the MC-LAG transitioned the LAG subgroup which hosts the SAP for this VLL endpoint from active to
standby, the node sends immediately new T-LDP status bits indicating the new value of
standby over the spoke SDPs which are on the mate-endpoint of the VLL. The same applies when any object in the endpoint changes an operational state from up to down.
[no
] standby-signaling-master
[no
] standby-signaling-slave
none (Interworking must be configured before adding a Frame-Relay SAP to an Apipe service.)
The service MTU and a SAP’s service delineation encapsulation overhead (4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, then the SAP will be placed in an inoperative state. If the
required MTU is equal to or less than the port or channel MTU, the SAP will be able to transition to the operative state.
When binding an SDP to a service, the service MTU is compared to the path MTU associated with the SDP. The path MTU can be administratively defined in the context of the SDP. The default or administrative path MTU can be dynamically reduced due to the MTU capabilities discovered by the tunneling mechanism of the SDP or the egress interface MTU capabilities based on the next hop in the tunnel path. If the service MTU is larger than the path MTU, the SDP binding for the service will be placed in an inoperative state. If the service MTU is equal to or less than the path MTU, then the SDP binding will be placed in an operational state.
In the event that a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, then all associated SAP and SDP binding operational states are automatically re-evaluated.
The no form of this command returns the default
service-mtu for the indicated service type to the default value.
The override command is not allowed on Apipe VLL service of vc-type value other than atm-cell. It is also not allowed on a VLL service with the vc-switching option enabled since signaling of the PW FEC in a Multi-Segment PW (MS-PW) is controlled by the T-PE nodes. Thus for this feature to be used on a MS-PW, it is required to configure an Apipe service of vc-type atm-cell at the T-PE nodes with the signaled-vc-type-override enabled, and to configure a Apipe VLL service of vc-type atm-vcc at the S-PE node with the vc-switching option enabled.
The no form of this command returns the Apipe VLL service to signal its default pseudowire type
The no form of this command deletes the profile from the configuration.
The no form of this command deletes the member from the configuration..
sap sap-id [create
] [no-endpoint
]
sap sap-id [create
] endpoint
endpoint-name
Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the service in which it was created.
The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all configuration parameters for the SAP will also be deleted. For Internet Enhanced Service (IES), the IP interface must be shutdown before the SAP on that interface may be removed.
A SAP can be defined with Ethernet ports, SONET/SDH or TDM channels. At most, only one sdp-id can be bound to an VLL service. Since a VLL is a point-to-point service, it can have, at most, two end points. The two end points can be one SAP and one SDP or two SAPs. Up to 49 SDPs can be associated with a service in a single router. Each SDP must have a unique router destination or an error will be generated.
The port-id must reference a valid port type. When the
port-id parameter represents SONET/SDH and TDM channels, the port ID must include the channel ID. A period “.” separates the physical port from the
channel-id. The port must be configured as an access port.
*A:bksim2801>config>service>apipe>sap$
=================================================================
ATM PVCs, Port 1/1/1
=================================================================
VPI/VCI Owner Type Ing.TD Egr.TD Adm OAM Opr
-----------------------------------------------------------------
2/102 SAP PVC 1 1 up ETE-AIS dn
10/100 SAP PVC 1 1 up ETE-AIS dn
=================================================================
*A:bksim2801#
[no
] sap eth-tunnel
-tunnel-id[:eth-tunnel-sap-id] [create
]
An Ethernet tunnel control SAP has the format eth-tunnel-tunnel-id and is not configured with an Ethernet tunnel SAP ID. No Ethernet tunnel tags can be configured under a control SAP since the control SAP uses the control tags configured under the Ethernet tunnel port. This means that at least one member port and control tag must be configured under the Ethernet tunnel port before this command is executed. The control SAP is needed for carrying G.8031 and 802.1ag protocol traffic. This SAP can also carry user data traffic.
An Ethernet tunnel same-fate SAP has the format eth-tunnel-tunnel-id:eth-tunnel-sap-id. Same-fate SAPs carry only user data traffic. Multiple same-fate SAPs can be configured on one Ethernet tunnel port and share the fate of that port, provided the SAPs are properly configured with corresponding tags.
The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.
This command defines a maximum total rate for all egress queues on a service SAP or multi-service site. The agg-rate-limit command is mutually exclusive with the egress scheduler policy. When an egress scheduler policy is defined, the
agg-rate-limit command will fail. If the
agg-rate-limit command is specified, at attempt to bind a
scheduler-policy to the SAP or multi-service site will fail.
The no form of the command removes the aggregate rate limit from the SAP or multi-service site.
agg-rate-limit agg-rate [queue-frame-based-accounting
] (Epipe services)
This command defines a maximum total rate for all egress queues on a service SAP or multi-service site. The agg-rate-limit command is mutually exclusive with the egress scheduler policy. When an egress scheduler policy is defined, the
agg-rate-limit command will fail. If the
agg-rate-limit command is specified, at attempt to bind a
scheduler-policy to the SAP or multi-service site will fail.
The no form of the command removes the aggregate rate limit from the SAP or multi-service site.
The no form of the command removes any existing policer-control-policy overrides and the policer-control-overrides node from the SAP.
The no form of the command removes the override and allows the mbs-contribution setting from the policer-control-policy to control the parent policer’s priority level’s burst tolerance.
On the SAP side, an instance of a policy is created each time a policy is applied. When applied to a sub-profile, an instance of the policy is created each time a subscriber successfully maps one or more hosts to the profile per ingress SAP.
Each instance of the policer-control-policy manages the policers associated with the object that owns the policy instance (SAP or subscriber). If a policer on the object is parented to an appropriate arbiter name that exists within the policy, the policer will be managed by the instance. If a policer is not parented or is parented to a non-existent arbiter, the policer will be orphaned and will not be subject to bandwidth control by the policy instance.
The no form of the command removes a non-associated policer control policy from the system. The command will not execute when policer-name is currently associated with any SAP context.
The no form of the command is used to remove any existing policer overrides.
The no form of the command is used to remove any existing overrides for the specified policer-id.
The no form of this command returns the CBS size to the default value.
mbs size [bytes
| kilobytes
]
The no form of the command is used to restore the policer痴 mbs setting to the policy defined value.
The no packet-byte-offset command is used to restore the policer痴 packet-byte-offset setting to the policy defined value.
percent-rate pir-percent [cir
cir-percent] [port-limit
|local-limit
]
rate {rate | max
} [cir
{max
| rate}]
The no rate command is used to restore the policy defined metering and profiling rate to a policer.
no-stats — Counter resource allocation: 0
The no-stats mode is the default stat-mode for the policer. The policer does not have any forwarding plane counters allocated and cannot provide offered, discard and forward statistics. A policer using no-stats cannot be a child to a parent policer and the policers parent command will fail.
When collect-stats is enabled, the lack of counters causes the system to generate the following statistics:
minimal — Counter resource allocation: 1 The minimal mode allocates 1 forwarding plane offered counter and one traffic manager discard counter. The forwarding counter is derived by subtracting the discard counter from the offered counter. The counters do not differentiate possible offered types (soft or hard profile) and do not count green or yellow output. This does not prevent the policer from supporting different offered packet types and does not prevent the policer from supporting a CIR rate.
offered-profile-no-cir — Counter resource allocation: 2
The offered-profile-no-cir mode allocates two forwarding plane offered counters and two traffic manager discard counters.
The offered-profile-no-cir mode is most useful when profile based offered, discard and forwarding stats are required from the ingress policer, but a CIR is not being used to recolor the soft in-profile and out-of-profile packets. This mode does not prevent the policer from being configured with a CIR rate.
The counters are used in the following manner:
When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When the enabled, only the P-bits/DEI bit in the top Q-tag are marked.
This command associates the SAP with a customer-site-name. If the specified
customer-site-name does not exist in the context of the service customer ID an error occurs and the command will not execute. If
customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) will attempt to use the scheduler hierarchies created within
customer-site-name as parent schedulers.
The no form of the command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future queues to enter an orphaned state.
The no form of the command removes the name from the configuration.
The no form of the command removes the transit policy ID from the spoke SDP configuration.
An Ipipe VLL service with the ce-address-discovery command enabled forwards unicast IP packets using the broadcast MAC address until the ARP cache is populated with a valid entry for the CE IP and MAC addresses.
The no form of this command enables the user of a of broadcast MAC on SAP.
The no form of this command returns the MAC address of the SAP to the default value.
The no form of this command restores mac-refresh to the default value.
The no form of this command removes the accounting policy association from the SAP, and the acccounting policy reverts to the default.
The no form of the command reverts to the default value.
This command is mutually exclusive with no pw-status-signaling, and
standby-signaling-slave. It is not applicable to spoke SDPs forming part of an MC-LAG or spoke SDPs in an endpoint.
When the no collect-stats command is issued the statistics are still accumulated by the IOM cards. However, the CPU will not obtain the results and write them to the billing file. If a subsequent
collect-stats command is issued then the counters written to the billing file include all the traffic while the
no collect-stats command was in effect.
cpu-protection policy-id [mac-monitoring
] | [eth-cfm-monitoring [aggregate][car]]
If no CPU protection policy is assigned to a service SAP then a the default policy is used to limit the overall-rate.
This command enables Link Loss Forwarding (LLF) on an Ethernet port or an ATM port. This feature provides an end-to-end OAM fault notification for Ethernet VLL serviceand for ATM VLL service of vc-type atm-cell. It brings down the Ethernet port (Ethernet LLF) or sends a SONET/SDH Path AIS (ATM LLF) towards the attached CE when there is a local fault on the Pseudowire or service, or a remote fault on the SAP or pseudowire, signaled with label withdrawal or T-LDP status bits. It ceases when the fault disappears.
The no form of the command removes the ECID from the configuration.
[no
] report-alarm
[stray
] [malformed
] [pktloss
] [overrun
] [underrun
] [rpktloss
] [rfault
] [rrdi
]
The no form of the command removes the parameter from the configuration.
path path-index tag
qtag[.qtag]
The no form of the command removes the values from the configuration.
mep mep-id domain
md-index association
ma-index [direction
{up
| down
}]
no mep mep-id domain
md-index association
ma-index primary-valn-enable
[vlan
vlan-id]
The no form of the command reverts to the default values.
The no form of the command disables the generation of CCM messages.
The no form of the command removes the priority value from the configuration.
The no form of the command means the receiving MEP will process all recognized TLVs in the CCM PDU.
oam eth-cfm eth-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [data-length
data-length]
config>service>epipe>sap>eth-cfm>mep>eth-test-enable
config>service>ipipe>sap>eth-cfm>mep>eth-test-enable
The no form of the command removes the values from the configuration.
cconfig>service>ipipe>sap>eth-cfm>mep
The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke SDP).
mip [mac
mac-address] primary-vlan-enable
[vlan
vlan-id]
Using the no command deletes the MIP. If the operator wants to change the mac back to the default mac without having to delete the MIP and reconfiguring this command is useful.
accept (SAP Level for Epipe and VPLS)
[no
] force-vlan-vc-forwarding
The no version of this command sets default behavior.
The filter command is used to associate a filter policy with a specified
filter-id with an ingress or egress SAP. The
filter-id must already be defined before the
filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use
scope command within the filter definition to change the scope to
local or
global. The default scope of a filter is
local.
Note that IPv6 filters are not supported on a Layer 2 SAP that is configured with QoS MAC criteria. Also, MAC filters are not supported on a Layer 2 SAP that is configured with QoS IPv6 criteria.
[no
] hsmda-queue-override
The no form of the command removes any accounting size changes to packets handled by the queue. The command does not effect overrides that may exist on SAPs or subscriber profiles associated with the queue.
The add keyword is mutually exclusive with the subtract keyword. Either the add or subtract keyword must be specified. The add keyword is used to indicate that the following byte value should be added to the packet for queue and queue group level accounting functions. The corresponding byte value must be specified when executing the packet-byte-offset command.
The subtract keyword is mutually exclusive with the add keyword. Either the add or subtract keyword must be specified. The subtract keyword is used to indicate that the following byte value should be subtracted from the packet for queue and queue group level accounting functions. The corresponding byte value must be specified when executing the packet-byte-offset command.
The no form of the command restores the defined queue-id to its default parameters. All HSMDA queues having the queue-id and associated with the QoS policy are re-initialized to default parameters.
Specifies the HSMDA queue to use for packets in this forwarding class. This mapping is used when the SAP is on a HSMDA MDA.
The no form of the command returns the weight value for the queue to the default value.
The no form of the command removes the specified HSMDA slope policy from the configuration. If the HSMDA slope policy is currently associated with an HSMDA queue, the command will fail.
no filter [ip
ip-filter-id] [ipv6
ipv6-filter-id]
The filter command is used to associate a filter policy with a specified
ip-filter-id with an ingress or egress SAP. The
ip-filter-id must already be defined before the
filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use
scope command within the filter definition to change the scope to
local or
global. The default scope of a filter is
local.
qos policy-id [shared-queuing] [fp-redirect-group queue-group-name instance instance-id]
The qos command, when used under the ingress context, is used to associate ingress QoS policies. The
qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.
The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the
multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit queue-id parameters.
qos policy-id [port-redirect-group queue-group-name instance instance-id]
The qos command, when used under the egress context, is used to associate egress QoS policies.
The qos command only allows ingress policies to be associated on SAP ingress and egress policies on SAP egress. Attempts to associate a QoS policy of the wrong type returns an error.
The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>egress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>egress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
The no form of the command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific
adaptation-rule is removed, the default constraints for
rate and
cir apply.
The pir parameter defines the constraints enforced when adapting the PIR rate defined within the
queue queue-id rate command. The
pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the
rate command is not specified, the default applies.
The cir parameter defines the constraints enforced when adapting the CIR rate defined within the
queue queue-id rate command. The
cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the
cir parameter is not specified, the default constraint applies.
|
Values
|
max — The max (maximum) keyword is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
|
min — The
min (minimum) keyword is mutually exclusive with the
max and
closest options. When
min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the
rate command.
closest — The
closest parameter is mutually exclusive with the
min and
max parameter. When
closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the
rate command.
The no form of this command restores the average frame overhead parameter for the queue to the default value of 0 percent. When set to 0, the system uses the packet based queue statistics for calculating port scheduler priority bandwidth allocation. If the no avg-frame-overhead command is executed in a queue-override queue id context, the avg-frame-overhead setting for the queue within the sap-egress QoS policy takes effect.
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>egress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>egress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
The queue burst-limit command is used to define an explicit shaping burst size for a queue. The configured size defines the shaping leaky bucket threshold level that indicates the maximum burst over the queue’s shaping rate.
The burst-limit command is supported under the sap-ingress and sap-egress QoS policy queues. The command is also supported under the ingress and egress queue-group-templates queues.
The no form of this command
is used to restore the default burst limit to the specified queue. This is equivalent to specifying burst-limit default within the QoS policies or queue group templates. When specified within a queue-override queue context, any current burst limit override for the queue will be removed and the queue’s burst limit will be controlled by its defining policy or template.
The bytes qualifier is used to specify that the value given for size must be interpreted as the burst limit in bytes. The byte qualifier is optional and mutually exclusive with the kilobytes qualifier.
The kilobyte qualifier is used to specify that the value given for size must be interpreted as the burst limit in Kilobytes. The kilobyte qualifier is optional and mutually exclusive with the bytes qualifier. If neither bytes nor kilobytes is specified, the default qualifier is kilobytes.
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>egress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>egress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
The no form of this command returns the CBS size to the default value.
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>egress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>egress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
This command can be used to override specific attributes of the specified queue’s high-prio-only parameters. The high-prio-only command configures the percentage of buffer space for the queue, used exclusively by high priority packets.
The defined high-prio-only value cannot be greater than the MBS size of the queue. Attempting to change the MBS to a value smaller than the high priority reserve will generate an error and fail execution. Attempting to set the
high-prio-only value larger than the current MBS size will also result in an error and fail execution.
The no form of this command restores the default high priority reserved size.
The percent parameter is the percentage reserved for high priority traffic on the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that none of the MBS of the queue will be reserved for high priority traffic. This does not affect RED slope operation for packets attempting to be queued.
mbs size [bytes
|kilobytes
]
config>service>ipipe>sap>ingress>hsmda-queue-override>queue
config>service>epipe>sap>ingress>hsmda-queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
The no form of this command
returns the MBS size assigned to the queue to the default value.
parent {[weight
weight] [cir-weight
cir-weight]}
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
Checks are not performed to see if a scheduler-name exists when the parent command is defined on the queue. Scheduler names are configured in the
config>qos>scheduler-policy>tier level context. Multiple schedulers can exist with the
scheduler-name and the association pertains to a scheduler that should exist on the egress SAP as the policy is applied and the queue created. When the queue is created on the egress SAP, the existence of the
scheduler-name is dependent on a scheduler policy containing the
scheduler-name being directly or indirectly applied (through a multi-service customer site) to the egress SAP. If the
scheduler-name does not exist, the queue is placed in the orphaned operational state. The queue will accept packets but will not be bandwidth limited by a virtual scheduler or the scheduler hierarchy applied to the SAP. The orphaned state must generate a log entry and a trap message. The SAP which the queue belongs to must also depict an orphan queue status. The orphaned state of the queue is automatically cleared when the
scheduler-name becomes available on the egress SAP.
The no form of the command removes a child association with a parent scheduler. If a parent association does not currently exist, the command has no effect and returns without an error. Once a parent association has been removed, the former child queue attempts to operate based on its configured rate parameter. Removing the parent association on the queue within the policy takes effect immediately on all queues using the SAP egress QoS policy.
These optional keywords are mutually exclusive to the keyword level.
weight defines the relative weight of this queue in comparison to other child schedulers and queues while vying for bandwidth on the parent
scheduler-name. Any queues or schedulers defined as weighted receive no parental bandwidth until all strict queues and schedulers on the parent have reached their maximum bandwidth or are idle. In this manner, weighted children are considered to be the lowest priority.
All weight values from all weighted active queues and schedulers with a common parent scheduler are added together. Then, each individual active weight is divided by the total, deriving the percentage of remaining bandwidth provided to the queue or scheduler after the strict children are serviced. A weight is considered to be active when the pertaining queue or scheduler has not reached its maximum rate and still has packets to transmit. All child queues and schedulers with a weight of 0 are considered to have the lowest priority level and are not serviced until all strict and non-zero weighted queues and schedulers are operating at the maximum bandwidth or are idle.
config>service>epipe>sap>egress>queue-override>queue
The percent-rate command supports a queue’s shaping rate and CIR rate as a percentage of the egress port’s line rate. When the rates are expressed as a percentage within the template, the actual rate used per instance of the queue group queue-id will vary based on the port speed. For example, when the same template is used to create a queue group on a 1-Gigabit and a 10-Gigabit Ethernet port, the queue’s rates will be 10 times greater on the 10 Gigabit port due to the difference in port speeds. This enables the same template to be used on multiple ports without needing to use port based queue overrides to modify a queue’s rate to get the same relative performance from the queue.
The no form of this command returns the queue to its default shaping rate and cir rate. When
no percent-rate is defined within a port egress queue group queue override, the queue reverts to the defined shaping and CIR rates within the egress queue group template associated with the queue.
The percent-of-line-rate parameter is used to express the queue’s shaping rate as a percentage of line rate. The line rate associated with the queue’s port may dynamically change due to configuration or auto-negotiation. The line rate may also be affected by an egress port scheduler defined max-rate.
The cir keyword is optional and when defined the required
percent-of-line-rate CIR parameter expresses the queue’s committed scheduling rate as a percentage of line rate. The line rate associated with the queue’s port may dynamically change due to configuration or auto-negotiation. The line rate may also be affected by an egress port scheduler defined max-rate.
rate pir-rate [cir
cir-rate]
config>service>apipe>sap>egress>queue-override>queue
config>service>apipe>sap>ingress>queue-override>queue
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
config>service>fpipe>sap>egress>queue-override>queue
config>service>fpipe>sap>ingress>queue-override>queue
config>service>ipipe>sap>egress>queue-override>queue
config>service>ipipe>sap>ingress>queue-override>queue
config>service>epipe>sap>egress>queue-override>queue
config>service>epipe>sap>ingress>queue-override>queue
The CIR can be used by the queue’s parent commands cir-level and
cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.
The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the
queue-id.
The no form of the command returns all queues created with the
queue-id by association with the QoS policy to the default PIR and CIR parameters (
max, 0).
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The
max value is mutually exclusive to the
pir-rate value.
The cir parameter overrides the default administrative CIR used by the queue. When the
rate command is executed, a CIR setting is optional. When the
rate command has not been executed or the
cir parameter is not explicitly specified, the default CIR (0) is assumed.
Fractional values are not allowed and must be given as a positive integer. The
sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers or queues.
[no
] scheduler
scheduler-name
config>service>apipe
>sap>egress>sched-override
config>service>apipe
>sap>ingress>sched-override
config>service>cpipe
>sap>egress>sched-override
config>service>cpipe
>sap>ingress>sched-override
config>service>fpipe
>sap>egress>sched-override
config>service>fpipe
>sap>ingress>sched-override
config>service>ipipe
>sap>egress>sched-override
config>service>ipipe
>sap>ingress>sched-override
config>service>epipe
>sap>ingress>sched-override
Each scheduler must have a unique name within the context of the scheduler policy; however the same name can be reused in multiple scheduler policies. If scheduler-name already exists within the policy tier level (regardless of the inclusion of the keyword create), the context changes to that scheduler name for the purpose of editing the scheduler parameters. Modifications made to an existing scheduler are executed on all instantiated schedulers created through association with the policy of the edited scheduler. This can cause queues or schedulers to become orphaned (invalid parent association) and adversely affect the ability of the system to enforce service level agreements (SLAs).
If the scheduler-name exists within the policy on a different tier (regardless of the inclusion of the keyword create), an error occurs and the current CLI context will not change.
If the scheduler-name does not exist in this or another tier within the scheduler policy, it is assumed that an attempt is being made to create a scheduler of that name. The success of the command execution is dependent on the following:
3.
The create keyword is entered with the command if the system is configured to require it (enabled in the
environment create command).
rate pir-rate [cir
cir-rate]
config>service>apipe
>sap>egress>sched-override>scheduler
config>service>apipe
>sap>ingress>sched-override>scheduler
config>service>cpipe
>sap>egress>sched-override>scheduler
config>service>cpipe
>sap>ingress>sched-override>scheduler
config>service>fpipe
>sap>egress>sched-override>scheduler
config>service>fpipe
>sap>ingress>sched-override>scheduler
config>service>ipipe
>sap>egress>sched-override>scheduler
config>service>ipipe
>sap>ingress>sched-override>scheduler
config>service>epipe
>sap>egress>sched-override>scheduler
config>service>epipe
>sap>ingress>sched-override>scheduler
This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s ‘within CIR’ distribution phase.
When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.
The no form of this command returns all queues created with this
queue-id by association with the QoS policy to the default PIR and CIR parameters.
The pir parameter accepts a step multiplier value that specifies the multiplier used to determine the PIR rate at which the queue will operate. A value of 0 to 100000000 or the keyword
max or
sum is accepted. Any other value will result in an error without modifying the current PIR rate.
The cir parameter accepts a step-multiplier value that specifies the multiplier used to determine the CIR rate at which the queue will operate. A value of 0 to 250 or the keyword max is accepted. Any other value will result in an error without modifying the current CIR rate.
scheduler-policy scheduler-policy-name
The no form of this command removes the configured ingress or egress scheduler policy from the multi-service customer site. When the policy is removed, the schedulers created due to the policy are removed also making them unavailable for the ingress SAP queues associated with the customer site. Queues that lose their parent scheduler association are deemed to be orphaned and are no longer subject to a virtual scheduler. The SAPs that have ingress queues reliant on the removed schedulers enter into an operational state depicting the orphaned status of one or more queues. When the
no scheduler-policy command is executed, the customer site ingress or egress node will not contain an applied scheduler policy.
The scheduler-policy-name parameter applies an existing scheduler policy that was created in the
config>qos>scheduler-policy scheduler-policy-name context to create the hierarchy of ingress or egress virtual schedulers. The scheduler names defined within the policy are created and made available to any ingress or egress queues created on associated SAPs.
The no version of the command sets the default value and no action will be taken.
The match-qinq-dot1p command allows the top or bottom PBits to be used when evaluating the applied sap-ingress QoS policy’s Dot1P entries. The
top and
bottom keywords specify which position should be evaluated for QinQ encapsulated packets.
The no form of this command reverts the dot1p and de bits matching to the default tag.
The dot1p dot1p-value command must be configured without the qinq-mark-top-only parameter to remove the TopQ PBits only marking restriction.
The no form of the command disables the use of FRF12 headers.
The no form of the command reverts to the default.
The no form of this command restores the default mode of operation.
spoke-sdp sdp-id[:
vc-id] [vc-type
{ether
| vlan
}] [no-endpoint]
spoke-sdp sdp-id[:
vc-id] [vc-type
{ether
| vlan
}] endpoint endpoint-name [icb
]
The SDP must already be defined in the config>service>sdp context in order to associate an SDP with an Epipe,VPLS, VPRN, VPRN service. If the
sdp sdp-id is not already configured, an error message is generated. If the
sdp-id does exist, a binding between that
sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
No sdp-id is bound to a service.
At most, only one sdp-id can be bound to an Epipe service. Since an Epipe is a point-to-point service, it can have, at most, two end points. The two end points can be one SAP and one SDP or two SAPs. Vc-switching VLLs are an exception. If the VLL is a “vc-switching” VLL, then the two endpoints must both be SDPs.
Defines the VC type as Ethernet. The ethernet and
vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings. Defining Ethernet is the same as executing
no vc-type and restores the default VC type for the spoke SDP binding.
Defines the VC type as VLAN. The ethernet and
vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke SDP bindings.
The VLAN VC-type requires at least one dot1Q tag within each encapsulated Ethernet packet transmitted to the far end.
spoke-sdp sdp-id[:vc-id] endpoint
endpoint-name [icb
]
The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a service. If the
sdp sdp-id is not already configured, an error message is generated. If the
sdp-id does exist, a binding between that
sdp-id and the service is created.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
No sdp-id is bound to a service.
This command enables the use of the hash label on a VLL, VPRN or VPLS service bound to LDP or RSVP SDP as well as to a VPRN service using the autobind mode with the
ldp,
rsvp-te, or
mpls options. This feature is not supported on a service bound to a GRE SDP or for a VPRN service using the autobind mode with the gre option. This feature is also not supported on multicast packets forwarded using RSVP P2MP LPS or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance. It is, however, supported when forwarding multicast packets using an IES/VPRN spoke-interface.
The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp, or an IES/VPRN spoke interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following are the procedures:
|
•
|
The 7750 SR local PE will insert the flow label interface parameters sub-TLV with F=1 in the PW ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.
|
|
–
|
If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW packets received by the local PE will have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which will result in the insertion of the hash label by both PE nodes.
|
|
–
|
If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW received by the local PE will not have the hash label included.
|
The no form of this command disables the use of the hash label.
The no form of the command resets the configuration to ignore the AAL5 EOM as an indication to complete the cell concatenation.
The no form of the command resets the configuration to ignore the CLP change as an indication to complete the cell concatenation.
The no form of this command sets max-cells to the value ’1’ indicating that no concatenation will be performed.
The no form of this command resets max-delay to its default value.
The control word command provides the option to add a control word as part of the packet encapsulation for pseudowire types for which the control word is optional. These are Ethernet pseudowires (Epipe). ATM N:1 cell mode pseudowires (apipe vc-types atm-vcc and atm-vpc) and VT pseudowire (apipe vc-type atm-cell).
The configuration for the two directions of the pseudowire must match because the control word negotiation procedures described in Section 6.2 of RFC 4447 are not supported. The C-bit in the pseudowire FEC sent in the label mapping message is set to 1 when the control word is enabled. Otherwise, it is set to 0.
The pw-path-id only configurable if all of the following is true:
The no form of the command deletes the PW path ID.
[no
] control-channel-status
The no form of this command renoves control channel status signaling form a spoke-sdp. It can only be removed if control channel status is shutdown.
The no form of this command disables the use of the hash label.
The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp, or an IES/VPRN spoke interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following are the procedures:
|
•
|
The 7750 SR local PE will insert the flow label interface parameters sub-TLV with F=1 in the PW ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.
|
|
–
|
If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW packets received by the local PE will have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which will result in the insertion of the hash label by both PE nodes.
|
|
–
|
If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW received by the local PE will not have the hash label included.
|
The no form of this command disables the use of the hash label.
The filter command is used to associate a filter policy with a specified
ip-filter-id with an ingress or egress spoke SDP. The
ip-filter-id must already be defined before the
filter command is executed. If the filter policy does not exist, the operation will fail and an error message returned.
IP filters apply only to RFC 2427-routed IP packets. Frames that do not contain IP packets will not be subject to the filter and will always be passed, even if the filter's default action is to drop.
The no form of this command removes any configured filter ID association with the SDP. The filter ID itself is not removed from the system unless the scope of the created filter is set to local. To avoid deletion of the filter ID and only break the association with the service object, use
the scope command within the filter definition to change the scope to
local or
global. The default scope of a filter is
local.
qos network-policy-id port-redirect-group
queue-group-name [instance
instance-id]
The no version of this command removes the redirection of the PW to the queue-group.
qos network-policy-id fp-redirect-group
queue-group-name instance
instance-id
The no version of this command removes the redirection of the PW to the queue-group.
This command specifies the operational group to be monitored by the object under which it is configured. The oper-group name must be already configured under the
config>service context before its name is referenced in this command.
The no form of the command removes the association.
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding will begin to forward traffic.
The no form of the command returns the precedence value to the default.
The no form of the command disables the status signaling.
The no form of this command disables the command
spoke-sdp-fec spoke-sdp-fec-id [fec
fec-type] [aii-type
aii-type] [create
]
spoke-sdp-fec spoke-sdp-fec-id [fec
fec-type] [aii-type
aii-type] [create
] endpoint
name [icb
]
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
The auto-config command is blocked in CLI if signaling active has been enabled for this spoke-SDP. It it is only applicable to spoke SDPs configured under the Epipe, IES and VPRN interface context.
The no form of the command means that the 7x50 T-PE either acts as the active T-PE (if signaling active is configured) or automatically determines which 7x50 will initate MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke-SDP. If the SAII has the greater prefix value, then the 7x50 will initiate MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, then the 7x50 will assume that the far end T-PE will intiate MS-PW signaling and will wait for that label mapping message beforeresponding with a T-LDP label mapping message for the MS-PW in the reverse direction.
The no form of the command returns the precedence value to the default.
The no form of the command removes the values from the configuration.
The no form of this command reverts the parameter to the default value.
The no form of this command reverts the timer to its default value.
The no form of the command means that the 7x50 T-PE automatically selects the which 7x50 will initate MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke-SDP, as described above.
[no
] standby-signaling-slave
This command specifies the data encapsulation for an ATM PVCC delimited SAP. The definition references RFC 2684, Multiprotocol Encapsulation over ATM AAL5, and to the ATM Forum LAN Emulation specification. Ingress traffic that does not match the configured encapsulation will be dropped.
|
Values
|
aal5snap-routed — Routed encapsulation for LLC encapsulated circuit (LLC/SNAP precedes protocol datagram) as defined in RFC 2684. aal5mux-ip — Routed IP encapsulation for VC multiplexed circuit as defined in RFC 2684
|
The no form of the command reverts the traffic descriptor to the default traffic descriptor profile.
The no command disables alarm-cells functionality for a PVCC. When alarm-cells functionality is disabled, a PVCC’s operational status is no longer affected by a PVCC’s OAM state changes due to AIS/RDI processing (Note that when alarm-cells is disabled, a PVCC will change operational status to UP due to alarm-cell processing) and RDI cells are not generated as result of the PVCC going into AIS or RDI state. The PVCC’s OAM status, however, will record OAM faults as described above.
When configured to not terminate (the default is no terminate), the SAP will pass OAM cells through the VLL without inspecting them. The SAP will respond to OAM loopback requests that are directed to the local node by transmitting a loopback reply. Other loopback requests are transparently tunneled through the pseudowire. In this mode, it is possible to launch a loopback request towards the directly-attached ATM equipment and see the results of the reply.
The terminate option for OAM is the only and default mode of operation supported for an ATM SAP which is part of Epipe, Ipipe, VPLS, and IES/VPRN. This is because the ATM and AAL5 layers are terminated.
The terminate option for OAM is the only and default mode of operation supported for an ATM SAP which is part of Epipe, Ipipe, VPLS, and IES/VPRN. This is because the ATM and AAL5 layers are terminated.
[no]
endpoint endpoint-name
sap sap-id [no-endpoint
] [create
]
sap sap-id endpoint
endpoint-name [create
]
Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the service in which it was created.
The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all configuration parameters for the SAP will also be deleted.
The port-id must reference a valid port type. When the
port-id parameter represents SONET/SDH and TDM channels, the port ID must include the channel ID. A period “.” separates the physical port from the
channel-id. The port must be configured as an access port.
bundle-id: bundle-type-slot-id/mda-slot.bundle-num
bundle-id value range: 1 — 128
bpgrp-id: bpgrp-
type-bpgrp-num
type: ima
bpgrp-num value range: 1 — 1280
[no
] report-alarm
[stray
] [malformed
] [pktloss
] [overrun
] [underrun
] [rpktloss
] [rfault
] [rrdi
]
The no form of the command removes the parameter from the configuration.
This command defines a maximum total rate for all egress queues on a service SAP or multi-service site. The agg-rate-limit command is mutually exclusive with the egress scheduler policy. When an egress scheduler policy is defined, the
agg-rate-limit command will fail. If the
agg-rate-limit command is specified, at attempt to bind a
scheduler-policy to the SAP or multi-service site will fail.
The no form of the command removes the aggregate rate limit from the SAP or multi-service site.
When enabled (the encapsulation type of the access port where this SAP is defined as qinq), the qinq-mark-top-only command specifies which P-bits/DEI bit to mark during packet egress. When disabled, both set of P-bits/DEI bit are marked. When the enabled, only the P-bits/DEI bit in the top Q-tag are marked.
The qos command is used to associate both ingress and egress QoS policies. The
qos command only allows ingress policies to be associated on SAP or IP interface ingress and egress policies on SAP or IP interface egress. Attempts to associate a QoS policy of the wrong type returns an error.
The no form of this command removes the QoS policy association from the SAP or IP interface, and the QoS policy reverts to the default.
This keyword can only be specified on SAP ingress. The
shared-queueing keyword specifies the shared queue policy will be used by this SAP. When the value of this object is null, the SAP will use individual ingress QoS queues, instead of the shared ones.
[no]
queue queue-id [
create]
The pir parameter defines the constraints enforced when adapting the PIR rate defined within the
queue queue-id rate command. The
pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the
rate command is not specified, the default applies.
The cir parameter defines the constraints enforced when adapting the CIR rate defined within the
queue queue-id rate command. The
cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the
cir parameter is not specified, the default constraint applies.
|
Values
|
max — The max (maximum) keyword is mutually exclusive with the min and closest options. When max is defined, the operational PIR for the queue will be equal to or less than the administrative rate specified using the rate command.
|
min — The
min (minimum) keyword is mutually exclusive with the
max and
closest options. When
min is defined, the operational PIR for the queue will be equal to or greater than the administrative rate specified using the
rate command.
closest — The
closest parameter is mutually exclusive with the
min and
max parameter. When
closest is defined, the operational PIR for the queue will be the rate closest to the rate specified using the
rate command.
The no form of this command restores the average frame overhead parameter for the queue to the default value of 0 percent. When set to 0, the system uses the packet based queue statistics for calculating port scheduler priority bandwidth allocation. If the no avg-frame-overhead command is executed in a queue-override queue id context, the avg-frame-overhead setting for the queue within the sap-egress QoS policy takes effect.
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
The no form of this command returns the CBS size to the default value.
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
This command can be used to override specific attributes of the specified queue’s high-prio-only parameters. The high-prio-only command configures the percentage of buffer space for the queue, used exclusively by high priority packets.
The defined high-prio-only value cannot be greater than the MBS size of the queue. Attempting to change the MBS to a value smaller than the high priority reserve will generate an error and fail execution. Attempting to set the
high-prio-only value larger than the current MBS size will also result in an error and fail execution.
The no form of this command restores the default high priority reserved size.
The percent parameter is the percentage reserved for high priority traffic on the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that none of the MBS of the queue will be reserved for high priority traffic. This does not affect RED slope operation for packets attempting to be queued.
config>service>cpipe>sap>egress>queue-override>queue
The no form of this command returns the MBS size assigned to the queue.
mbs {size-in-kbytes | default
}
config>service>cpipe>sap>ingress>queue-override>queue
The no form of this command
returns the MBS size assigned to the queue to the default value.
rate pir-rate [cir
cir-rate]
config>service>cpipe>sap>egress>queue-override>queue
config>service>cpipe>sap>ingress>queue-override>queue
The CIR can be used by the queue’s parent commands cir-level and
cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.
The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the
queue-id.
The no form of the command returns all queues created with the
queue-id by association with the QoS policy to the default PIR and CIR parameters (
max, 0).
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The
max value is mutually exclusive to the
pir-rate value.
The cir parameter overrides the default administrative CIR used by the queue. When the
rate command is executed, a CIR setting is optional. When the
rate command has not been executed or the
cir parameter is not explicitly specified, the default CIR (0) is assumed.
Fractional values are not allowed and must be given as a positive integer. The
sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers or queues.
config>service>cpipe
>sap>egress>sched-override
config>service>cpipe
>sap>ingress>sched-override
Each scheduler must have a unique name within the context of the scheduler policy; however the same name can be reused in multiple scheduler policies. If scheduler-name already exists within the policy tier level (regardless of the inclusion of the keyword create), the context changes to that scheduler name for the purpose of editing the scheduler parameters. Modifications made to an existing scheduler are executed on all instantiated schedulers created through association with the policy of the edited scheduler. This can cause queues or schedulers to become orphaned (invalid parent association) and adversely affect the ability of the system to enforce service level agreements (SLAs).
If the scheduler-name exists within the policy on a different tier (regardless of the inclusion of the keyword create), an error occurs and the current CLI context will not change.
If the scheduler-name does not exist in this or another tier within the scheduler policy, it is assumed that an attempt is being made to create a scheduler of that name. The success of the command execution is dependent on the following:
3.
The create keyword is entered with the command if the system is configured to require it (enabled in the
environment create command).
This keyword createsa scheduler with the given scheduler-name. If the
create keyword is omitted,
scheduler-name is not created when the system environment variable create is set to true. This safeguard is meant to avoid accidental creation of system objects (such as schedulers) while attempting to edit an object with a mistyped name or ID. The keyword has no effect when the object already exists.
rate pir-rate [cir
cir-rate]
config>service>cpipe
>sap>egress>sched-override>scheduler
config>service>cpipe
>sap>ingress>sched-override>scheduler
This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s ‘within CIR’ distribution phase.
When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.
The no form of this command returns all queues created with this
queue-id by association with the QoS policy to the default PIR and CIR parameters.
The pir parameter accepts a step multiplier value that specifies the multiplier used to determine the PIR rate at which the queue will operate. A value of 0 to 100000000 or the keyword
max or
sum is accepted. Any other value will result in an error without modifying the current PIR rate.
The cir parameter accepts a step-multiplier value that specifies the multiplier used to determine the CIR rate at which the queue will operate. A value of 0 to 250 or the keyword max is accepted. Any other value will result in an error without modifying the current CIR rate.
scheduler-policy scheduler-policy-name
The no form of this command removes the configured ingress or egress scheduler policy from the multi-service customer site. When the policy is removed, the schedulers created due to the policy are removed also making them unavailable for the ingress SAP queues associated with the customer site. Queues that lose their parent scheduler association are deemed to be orphaned and are no longer subject to a virtual scheduler. The SAPs that have ingress queues reliant on the removed schedulers enter into an operational state depicting the orphaned status of one or more queues. When the
no scheduler-policy command is executed, the customer site ingress or egress node will not contain an applied scheduler policy.
The scheduler-policy-name parameter applies an existing scheduler policy that was created in the
config>qos>scheduler-policy scheduler-policy-name context to create the hierarchy of ingress or egress virtual schedulers. The scheduler names defined within the policy are created and made available to any ingress or egress queues created on associated SAPs.
This command associates the SAP with a customer-site-name. If the specified
customer-site-name does not exist in the context of the service customer ID an error occurs and the command will not execute. If
customer-site-name exists, the current and future defined queues on the SAP (ingress and egress) will attempt to use the scheduler hierarchies created within
customer-site-name as parent schedulers. See
multi-service-site.
The no form of the command removes the SAP from any multi-service customer site the SAP belongs to. Removing the site can cause existing or future queues to enter an orphaned state.
The service MTU and a SAP’s service delineation encapsulation overhead (i.e., 4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, then the SAP will be placed in an inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP will be able to transition to the operative state.
When binding an SDP to a service, the service MTU is compared to the path MTU associated with the SDP. The path MTU can be administratively defined in the context of the SDP. The default or administrative path MTU can be dynamically reduced due to the MTU capabilities discovered by the tunneling mechanism of the SDP or the egress interface MTU capabilities based on the next hop in the tunnel path.
The no form of this command returns the default
service-mtu for the indicated service type to the default value.
The no form of the command removes the name from the configuration.
spoke-sdp sdp-id[:
vc-id] [no-endpoint] [create
]
spoke-sdp sdp-id:vc-id [create
] endpoint
endpoint-name [icb
]
The SDP must already be defined in the config>service>sdp context. If the
sdp sdp-id is not already configured, an error message is generated. If the
sdp-id does exist, a binding between that
sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. Once removed, no packets are forwarded to the far-end router.
No sdp-id is bound to a service.
no vc-label
[egress-vc-label]
no vc-label
[ingress-vc-label]
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding will begin to forward traffic.
The no form of the command returns the precedence value to the default.
