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.
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.
ies service-id customer
customer-id [vpn
vpn-id] [create]
The ies command is used to create or maintain an Internet Enhanced Service (IES). If the
service-id does not exist, a context for the service is created. If the
service-id exists, the context for editing the service is entered.
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 IES service instance with the specified
service-id. The service cannot be deleted until all the IP interfaces defined within the service ID have been shutdown and deleted.
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
[no
] disable-router-alert-check
The no form of the command disables the router alert check.
The no form of the command removes the values from the configuration.
The no form of the command disables the check..
The no form of this command disables the check.
The no form of the command removes the policy association from the SAP.
no import — No import policy is specified.
[no
] redundant-interface
ip-int-name
address {ip-address/mask | ip-address netmask} [remote-ip
ip-address]
[no
] subscriber-interface
ip-int-name
Use the no form of the command to remove the subscriber interface.
group-interface ip-int-name [
create]
lns
group-interface ip-int-name [
create]
softgre
no group-interface ip-int-name [
create]
Use the no form of the command to remove the group interface from the subscriber interface.
The no form of this command removes the policy name from the group interface configuration.
The no form of the command removes an SRRP instance from a group IP interface. Once removed, the group interface ignores ARP requests for the SRRP gateway IP addresses that may exist on subscriber subnets associated with the group IP interface. Then the group interface stops routing using the redundant IP interface associated with the group IP interface and will stop routing with the SRRP gateway MAC address. Ingress packets destined to the SRRP gateway MAC will also be silently discarded. This is the same behavior as a group IP interface that is disabled (shutdown).
[no
] bfd-enable
[service-id] interface
interface-name dst-ip
ip-address
|
Values
|
service-id: 1 — 2147483648
svc-name: Specifies an existing service name up to 64 characters in length. No service ID indicates a network interface.
|
The no form of the command removes the explicit SRRP gateway MAC address from the SRRP instance. The SRRP gateway MAC address can only be changed or removed when the SRRP instance is shutdown.
The no form of the command restores the default interval.
The no form of the command can only be executed when the SRRP instance is shutdown. Executing no message-path allows the existing SAP to be used for subscriber management functions. A new message-path SAP must be defined prior to activating the SRRP instance.
[no
] policy
vrrp-policy-id
The no form of the command removes the association with vrrp-policy-id from the SRRP instance.
The no form of the command restores the default base priority to the SRRP instance. If a VRRP policy is associated with the SRRP instance, it will use the default base priority as the basis for any modifications to the SRRP instances in-use priority.
[no
] subscriber-interface
ip-int-name
Use the no form of the command to remove the subscriber interface.
[no
] group-interface
ip-int-name
The no form of this command removes the policy name from the group interface configuration.
The no form of the command removes an SRRP instance from a group IP interface. Once removed, the group interface ignores ARP requests for the SRRP gateway IP addresses that may exist on subscriber subnets associated with the group IP interface. Then the group interface stops routing using the redundant IP interface associated with the group IP interface and will stop routing with the SRRP gateway MAC address. Ingress packets destined to the SRRP gateway MAC will also be silently discarded. This is the same behavior as a group IP interface that is disabled (shutdown).
The no form of the command removes the explicit SRRP gateway MAC address from the SRRP instance. The SRRP gateway MAC address can only be changed or removed when the SRRP instance is shutdown.
The no form of the command restores the default interval.
The no form of the command can only be executed when the SRRP instance is shutdown. Executing no message-path allows the existing SAP to be used for subscriber management functions. A new message-path SAP must be defined prior to activating the SRRP instance.
[no
] policy
vrrp-policy-id
The no form of the command removes the association with vrrp-policy-id from the SRRP instance.
The no form of the command restores the default base priority to the SRRP instance. If a VRRP policy is associated with the SRRP instance, it will use the default base priority as the basis for any modifications to the SRRP instances in-use priority.
The interface command, under the context of services, is used to create and maintain IP routing interfaces within IES service IDs. The
interface command can be executed in the context of an IES service ID. The IP interface created is associated with the service core network routing instance and default routing table. The typical use for IP interfaces created in this manner is for subscriber internet access. An IP address cannot be assigned to an IES interface. Multiple SAPs can be assigned to a single group interface.
Interface names are case sensitive and must be unique within the group of defined IP interfaces defined for config router interface and
config service ies interface (that is, the network core router instance). Interface names must not be in the dotted decimal notation of an IP address. For example, the name “1.1.1.1” is not allowed, but “int-1.1.1.1” is allowed. Show commands for router interfaces use either interface names or the IP addresses. Use unique IP address values and IP address names to maintain clarity. It could be unclear to the user if the same IP address and IP address name values are used. Although not recommended, duplicate interface names can exist in different router instances.
The available IP address space for local subnets and routes is controlled with the config router service-prefix command. The
service-prefix command administers the allowed subnets that can be defined on IES IP interfaces. It also controls the prefixes that may be learned or statically defined with the IES IP interface as the egress interface. This allows segmenting the IP address space into
config router and
config service domains.
The no form of this command removes IP the interface and all the associated configuration. The interface must be administratively shutdown before issuing the
no interface command.
For IES services, the IP interface must be shutdown before the SAP on that interface may be removed. IES services do not have the
shutdown command in the SAP CLI context. IES service SAPs rely on the interface status to enable and disable them.
If ip-int-name already exists within the service ID, the context will be changed to maintain that IP interface. If
ip-int-name already exists within another service ID or is an IP interface defined within the
config router commands, an error will occur and context will not be changed to that IP interface. If
ip-int-name does not exist, the interface is created and context is changed to that interface for further command processing.
address {ip-address/mask|ip-address netmask} [broadcast all-ones | host-ones] [track-srrp srrp-instance]
In the IES subscriber interface context, this command is used to assign one or more host IP addresses and subnets. This differs from a normal IES interfaces where the secondary command creates an additional subnet after the primary address is assigned. A user can then add or remove addresses without having to keep a primary address.
The local subnet that the address command defines must be part of the services address space within the routing context using the
config router service-prefix command. The default is to disallow the complete address space to services. Once a portion of the address space is allocated as a service prefix, that portion can be made unavailable for IP interfaces defined within the
config router interface CLI context for network core connectivity with the
exclude option in the
config router service-prefix command.
Use the no form of this command to remove the IP address assignment from the IP interface.
The no form of this command will cause ptp-hw-assist to be disabled.
The IP address of the IP interface. The ip-address portion of the
address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP addresses in the range 1.0.0.0 – 223.255.255.255 (with support of /31 subnets).
The forward slash is a parameter delimiter and separates the ip-address portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the
ip-address, the “
/” and the
mask-length parameter. If a forward slash is not immediately following the
ip-address, a dotted decimal mask must follow the prefix.
The optional broadcast parameter overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is
host-ones which indictates a subnet broadcast address. Use this parameter to change the broadcast address to
all-ones or revert back to a broadcast address of
host-ones.
The all-ones keyword following the
broadcast parameter specifies the broadcast address used by the IP interface for this IP address will be 255.255.255.255, also known as the local broadcast.
The host-ones keyword following the
broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be the subnet broadcast address. This is an IP address that corresponds to the local subnet described by the
ip-address and the
mask-length or
mask with all the host bits set to binary one. This is the default broadcast address used by an IP interface.
The broadcast parameter within the
address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the
broadcast type to
host-ones after being changed to
all-ones, the
address command must be executed with the
broadcast parameter defined.
[no
] address
{ip-address/mask | ip-address netmask} [gw-ip-address
ip-address] [populate-host-routes
]
Defining an SRRP gateway IP address on a subscriber subnet is not optional when the subnet is associated with a group IP interface with SRRP enabled. Enabling SRRP (no shutdown) will fail if one or more subscriber subnets do not have an SRRP gateway IP address defined. Creating a new subscriber subnet without an SRRP gateway IP address defined will fail when the subscriber subnet is associated with a group IP interface with an active SRRP instance. Once SRRP is enabled on a group interface, the SRRP instance will manage the ARP response and routing behavior for all subscriber hosts reachable through the group IP interface.
The no form of the command removes the address from a subscriber subnet. The address command for the specific subscriber subnet must be executed without the
gw-address parameter. To succeed, all SRRP instances associated with the subscriber subnet must removed or shutdown.
The no form of the command removes the command from the active configuration and removes the delay in activating the associated IP interface. If the configuration is removed during a delay period, the currently running delay will continue until it expires.
[no
] allow-directed-broadcasts
A directed broadcast is a packet received on a local router interface destined for the subnet broadcast address on another IP interface. The allow-directed-broadcasts command on an IP interface enables or disables the transmission of packets destined to the subnet broadcast address of the egress IP interface.
The no form of this command disables the forwarding of directed broadcasts out of the IP interface.
no allow-directed-broadcasts — Directed broadcasts are dropped.
The no form of the command disables anti-spoof filtering on the SAP.
The no form of the command disables anti-spoof filtering on the SAP.
arp-limit limit [log-only] [threshold
percent]
The no form of the command removes the
arp-limit.
The no form of this command removes the command from the active configuration and returns the ARP retry timer to its default value of 5 seconds.
When the arp-populate and
lease-populate commands are enabled on an IES interface, the ARP table entries will no longer be dynamically learned, but instead by snooping DHCP ACK message from a DHCP server. In this case the configured
arp-timeout value has no effect.
The no form of this command restores
arp-timeout to the default value.
bfd transmit-interval [receive
receive-interval] [multiplier
multiplier [echo-receive echo-interval] [type
cpm-np
]
The no form of the command removes BFD from the interface.
Important notes: On the 7750-SR, the
transmit-interval, receive receive-interval, and echo-receive echo-interval values can only be modified to a value less than 100 when:
|
1.
|
The type cpm-np option is explicitly configured.
|
To remove the type cpm-np option, re-issue the
bfd command without specifying the
type parameter.
cflowd is used for network planning and traffic engineering, capacity planning, security, application and user profiling, performance monitoring, usage-based billing, and SLA measurement.
At a minimum, the sampling command must be configured within this context in order to enable cflowd sampling, otherwise traffic sampling will not occur.
config>service>ies>if>cflowd-parameters
If cflowd is enabled without either egress-only or
both specified or with the
ingress-only keyword specified, then only ingress sampling will be enabled on the associated IP interface.
The no form of the command disables the associated type of traffic sampling on the associated interface.
Specifies that the sampling command will control the sampling of unicast traffic on the associated interface/SAP.
Specifies that the sampling command will control the sampling of multicast traffic on the associated interface/SAP.
If no cpu-protection policy is assigned to a service interface, then the default policy is used to limit the overall-rate. The default policy is policy number 254 for access interfaces and 255 for network interfaces.
The no form of the command removes the association of the CPU protection policy from the associated interface and reverts to the default policy values.
The configuration of no cpu-protection returns the interface/SAP to the default policies as shown above.
cpu-protection policy-id [mac-monitoring
]|[eth-cfm-monitoring
[aggregate
][car
]] |[ip-src-monitoring
]
The no form of the command removes the association of the CPU protection policy from the associated interface and reverts to the default policy values.
[no
] router-advertisements
[no
] managed-configuration
[no
] other-stateful-configuration
The no form of the command returns the default value.
The no form of this command includes both source and destination parameters.
no dns [ip-address] [secondary
ip-address]
The no form of the command deletes either the specified primary DNS address, secondary DNS address or both addresses from the IPCP extension peer-ip-address configuration.
The no form of the command deletes the IPCP extension peer-ip-address configuration.
The no form of this command includes both source and destination parameters.
The no form disables the SPI function.
Note that you can configure an IES interface as a loopback interface by issuing the loopback command instead of the
sap command. The loopback flag cannot be set on an interface where a SAP is already defined and a SAP cannot be defined on a loopback interface.
The no form of this command restores default configuration.
The no form of the command returns the MAC address of the IP interface to the default value.
The no form of the command removes the association from the configuration.
The no form of command disables efficient multicast replication to a network domain for a spoke SDP and traffic is replicated to all forwarding complexes.
secondary {ip-address/mask | ip-address netmask} [broadcast all-ones
| host-ones
] [igp-inhibit
]
The IP address of the IP interface. The ip-address portion of the
address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP addresses in the range 1.0.0.0 – 223.255.255.255 (with support of /31 subnets).
The optional broadcast parameter overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is
host-ones which indictates a subnet broadcast address. Use this parameter to change the broadcast address to
all-ones or revert back to a broadcast address of
host-ones.
The all-ones keyword following the
broadcast parameter specifies the broadcast address used by the IP interface for this IP address will be 255.255.255.255, also known as the local broadcast.
The host-ones keyword following the
broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be the subnet broadcast address. This is an IP address that corresponds to the local subnet described by the
ip-address and the
mask-length or
mask with all the host bits set to binary one. This is the default broadcast address used by an IP interface.
The broadcast parameter within the
address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the
broadcast type to
host-ones after being changed to
all-ones, the
address command must be executed with the
broadcast parameter defined.
The optional igp-inhibit parameter signals that the given secondary IP interface should not be recognized as a local interface by the running IGP. For OSPF and IS-IS, this means that the specified secondary IP interfaces will not be injected and used as passive interfaces and will not be advertised as internal IP interfaces into the IGP’s link state database. For RIP, this means that these secondary IP interfaces will not source RIP updates.
The no form of the command removes a static ARP entry.
The no tos-marking-state command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.
Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.
The no form of the command disables unicast RPF (uRPF) Check on this interface.
vas-if-type {to-from-access
| to-from-network
| to-from-both
}
The no form of the command removes VAS interface type configuration.
mode {strict
| loose
| strict-no-ecmp
}
The no form of the command reverts to the default (strict) mode.
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when
urpf-check is enabled.
The vpls command, within the IP interface context, is used to bind the IP interface to the specified service name (VPLS or I-VPLS).
The system does not attempt to resolve the service name provided until the IP interface is placed into the administratively up state (no shutdown). Once the IP interface is administratively up, the system will scan the available VPLS services that have the allow-ip-int-binding flag set for a VPLS service associated with the name. If the service name is bound to the service name when the IP interface is already in the administratively up state, the system will immediately attempt to resolve the given name.
The no form of the command on the IP interface is used to remove the service name binding from the IP interface. If the service name has been resolved to a VPLS service context and the IP interface has been attached to the VPLS service, the IP interface will also be detached from the VPLS service.
The no form of the command is used to remove the IPv4 routed override filter from the ingress IP interface. When removed, the IPv4 ingress routed packets within a VPLS service attached to the IP interface will use the IPv4 ingress filter applied to the packets virtual port when defined.
The no form of the command removes the sap-egress QoS policy used for reclassification from the egress IP interface. When removed, IP routed packets will not be reclassified on the egress SAPs of the VPLS service attached to the IP interface.
[no
] proxy-arp
policy-name [policy-name...(up to 5 max)]
The no form of this command disables the proxy ARP capability.
If the optional destination parameter is specified and the destination address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the destination address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If the optional source parameter is specified and the source address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the source address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If neither the optional source or
destination parameter is present, then the default is
destination address matching.
The no form of the command reverts to the default.
The no form of the command reverts to the default and disabled SeND.
[no
] allow-unsecured-msgs
The no form of the command disables accepting unsecured messages.
The no form of the command removes the stale-time value.
The no form of the command removes the static value and allows the TCP MSS value to be calculated based on the IP MTU value by subtracting the base IP and TCP header lengths from the IP MTU value (tcp_mss = ip_mtu – 40).
prefix ipv6-address/prefix-length [pd
] [wan-host
]
[no
] allow-unmatching-prefixes
[no
] delegated-prefix-length
prefix-length
Enabling the arp-populate command will remove any dynamic ARP entries learned on this interface from the ARP cache.
The arp-populate command will fail if an existing static ARP entry exists for this interface. The
arp-populate command will fail if an existing static subscriber host on the SAP does not have both MAC and IP addresses specified.
Once arp-populate is enabled, creating a static subscriber host on the SAP without both an IP address and MAC address will fail.
When arp-populate is enabled, the system will not send out ARP requests for hosts that are not in the ARP cache. Only statically configured and DHCP learned hosts are reachable through an IP interface with
arp-populate enabled. The
arp-populate command can only be enabled on IES and VPRN interfaces supporting Ethernet encapsulation.
Use the no form of the command to disable ARP cache population functions for static and dynamic hosts on the interface. All static and dynamic host information for this interface will be removed from the system’s ARP cache.
The port’s mode must be set to
access in
config>port>sonet-sdh>path>mode access context.
The port’s encapsulation type must be set to frame-relay in the
config>port>sonet-sdh>path>encap-type frame-relay context.
The no form of this command removes the Frame Relay LMI operational parameters.
The no form of the command deletes the backup-destination address from the tunnel configuration.
The no form of the command deletes the delivery-service from the tunnel configuration.
This command configures a private IPv4 or IPv6 address of the remote tunnel endpoint. A tunnel can have up to 16 dest-ip commands. At least one
dest-ip address is required in the configuration of a tunnel. A tunnel does not come up operationally unless all
dest-ip addresses are reachable (part of a local subnet).
Note: Unnumbered interfaces are not supported.
The no form of the command deletes the destination IP of the tunnel.
|
Values
|
be, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cs1, cp9, af11, cp11, af12, cp13, af13, cp15, cs2, cp17, af21, cp19, af22, cp21, af23, cp23, cs3, cp25, af31, cp27, af32, cp29, af33, cp31, cs4, cp33, af41, cp35, af42, cp37, af43, cp39, cs5, cp41, cp42, cp43, cp44, cp45, ef, cp47, nc1, cp49, cp50, cp51, cp52, cp53, cp54, cp55, nc2, cp57, cp58, cp59, cp60, cp61, cp62, cp63
|
If the no form of the command is configured then the tunnel is a simple IP-IP tunnel.
The no form of the command deletes the source address from the tunnel configuration. The tunnel must be administratively shutdown before issuing the
no source command.
The no form of the command deletes the destination address from the tunnel configuration.
The no form of this command restores the default mode of operation.
[no
] scheduling-class
class-id
[no
] host
ip
ip-address [mac
ieee-address]] [subscriber
sub-ident-string] [sub-profile
sub-profile-name] [sla-profile
sla-profile-name] [ancp-string
ancp-string]
no host {[ip
ip-address] [mac
ieee-address]}
Use the no form of the command to remove a static entry from the system. The specified
ip-address and
mac-address must match the host’s exact IP and MAC addresses as defined when it was created. When a static host is removed from the SAP, the corresponding anti-spoof entry and/or ARP cache entry is also removed.
|
•
|
For VPRN SAPs with arp-reply-agent enabled with the optional sub-ident parameter, the static subscriber host’s sub-ident-string is used to determine whether an ARP request received on the SAP is sourced from a host belonging to the same subscriber as the destination host. When both the destination and source hosts from the ARP request are known on the SAP and the subscriber identifications do not match, the ARP request may be forwarded to the rest of the VPRN destinations.
|
If sub-ident is not enabled on the SAP arp-reply-agent, subscriber identification matching is not performed on ARP requests received on the SAP.
The no form of the command removes flowspec filtering from an IP interface.
The no form of the command removes the server client type from the configuration.
action {replace
| drop
| keep
}
The no form of this command returns the system to the default value.
circuit-id [ascii-tuple | ifindex | sap-id | vlan-ascii-tuple
]
If disabled, the circuit-id suboption of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
When the match-circuit-id command is enabled, it is used as part of the key to guarantee correctness in our lookup. This is really only needed when we are dealing with an IP aware DSLAM that proxies the client HW mac address.
The no form of this command returns the system to the default.
When enabled, the router sends the MAC address of the remote end (typically the DHCP client) in the remote-id suboption of the DHCP packet. This command identifies the host at the other end of the circuit.
If disabled, the remote-id suboption of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
[no
] vendor-specific-option
The no form of the command disables the sending of the MAC address in the vendor specific suboption of the DHCP relay packet.
The no form of the command disables the sending of the SAP ID in the vendor specific suboption of the DHCP relay packet.
The no form of the command disables the sending of the service ID in the vendor specific suboption of the DHCP relay packet
.
The no form of the command returns the default value.
The no form of this command reverts to the default setting. The local proxy server will not become operational without the emulated-server address being specified.
lease-time [days
days] [hrs
hours] [min
minutes] [sec
seconds] [radius-override
]
The no form of this command disables the use of the lease-time command. The local-proxy-server will use the lease-time offered by either a RADIUS or DHCP server.
server server1 [server2...(up to 8 max)]
According to RFC 3046, DHCP Relay Agent Information Option, a DHCP request where the giaddr is 0.0.0.0 and which contains a Option 82 field in the packet, should be discarded, unless it arrives on a "trusted" circuit. If trusted mode is enabled on an IP interface, the Relay Agent (the router) will modify the request's giaddr to be equal to the ingress interface and forward the request.
The no form of this command returns the system to the default.
The no form of the command removes the value from the configuration.
The no form of the command disables the feature.
If an authentication policy is also configured, pppoe-access-method must be set to none in this authentication policy to use the local user database (in that case RADIUS authentication will not be used for PPPoE hosts).
If a local node sends an ICMP mask request to the router interface, the mask-reply command configures the router interface to reply to the request.
The no form of this command disables replies to ICMP mask requests on the router interface.
mask-reply — Reply to ICMP mask requests.
The redirects command enables the generation of ICMP redirects on the router interface. The rate at which ICMP redirects is issued can be controlled with the optional
number and
seconds parameters by indicating the maximum number of redirect messages that can be issued on the interface for a given time interval.
The no form of this command disables the generation of icmp redirects on the router interface.
redirects 100 10 — Maximum of 100 redirect messages in 10 seconds
The no form of this command disables the limiting the rate of TTL expired messages on the router interface.
The unreachables command enables the generation of ICMP destination unreachables on the router interface. The rate at which ICMP unreachables is issued can be controlled with the optional
number and
time parameters by indicating the maximum number of destination unreachable messages which can be issued on the interface for a given time interval.
The no form of this command disables the generation of icmp destination unreachable messages on the router interface.
Each single operation of the admin-group command allows a maximum of five (5) groups to be specified at a time. However, a maximum of 32 groups can be added to a given interface through multiple operations. Once an admin group is bound to one or more interface, its value cannot be changed until all bindings are removed.
It should be noted that only the admin groups bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.
The no form of this command deletes one or more of the admin-group memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.
srlg-group group-name [group-name...(up to 5 max)
]
An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of five (5) groups to be specified at a time. Once an SRLG group is bound to one or more interface, its value cannot be changed until all bindings are removed.
It should be noted that only the SRLGs bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.
The no form of this command deletes one or more of the SRLG memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.
address ipv6-address/prefix-length [eui-64
]
When the eui-64 keyword is specified, a complete IPv6 address from the supplied prefix and 64-bit interface identifier is formed. The 64-bit interface identifier is derived from MAC address on Ethernet interfaces. For interfaces without a MAC address, for example ATM interfaces, the Base MAC address of the chassis is used.
The no form of the command turns off
dad-disable on the interface.
The no form of the command disables DHCPv6 relay.
The no form of the command disables neighbor resolution.
The no form of the command disables DHCPv6 relay information options.
The no form of the command disables the sending of interface ID options in the DHCPv6 relay packet
The no form of the command disables the sending of remote ID option in the DHCPv6 relay packet.
server ipv6z-address [ipv6z-address...(up to 8 max)]
The no form of the command disables the DHCPv6 server.
The no form of the command returns the value to the default.
The no form of the command disables prefix-delegation.
[no
] prefix
ipv6-address/prefix-length
The no form of the command reverts to the default value.
The no form of the command reverts to the default value.
The no form of the command disables the sending of ICMPv6 “packet-too-big” messages.
The no form of the command disables the sending of “parameter-problem” ICMPv6 messages.
The no form of the command disables local proxy neighbor discovery.
The no form of the command removes the
neighbor-limit.
The no form of the command returns the MAC address of the IP interface to the default value.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
The ping-reply command is only available in non-owner vrrp virtual-router-id nodal context. If the ping-reply command is not executed, ICMP echo requests to the virtual router instance IP addresses will be silently discarded.
The no form of this command restores the default operation of discarding all ICMP echo request messages destined to the non-owner virtual router instance IP addresses.
The policy command is only available in the non-owner vrrp virtual-router-id nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed by VRRP priority control policies. For non-owner virtual router instances, if the policy command is not executed, the base-priority will be used as the in-use priority.
The no form of this command removes any existing VRRP priority control policy association from the virtual router instance. All such associations must be removed prior to the policy being deleted from the system.
The no form of this command restores the default value of 100 to base-priority.
The no form of the command specifies that a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address.
The telnet-reply command is only available in non-owner VRRP
nodal context. If the telnet-reply command is not executed, Telnet packets to the virtual router instance IP addresses will be silently discarded.0
The no form of this command restores the default operation of discarding all Telnet packets destined to the non-owner virtual router instance IP addresses.
[no
] spoke-sdp
sdp-id[:
vc-id] [vc-type {ether | ipipe
}] [create
]
The SDP must already be defined in the config>service>sdp context in order to associate an SDP with an IES 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. The spoke SDP must be shut down first before it can be deleted from the configuration.
No sdp-id is bound to a service.
qos network-policy-id port-redirect-group
queue-group-name [instance
instance-id]
The no version of this command removes the redirection of the pseudowire to the queue-group.
This optional parameter specifies that the queue-group-name will be used for all egress forwarding class redirections within the network QoS policy ID. The specified
queue-group-name must exist as a port egress queue group on the port associated with the IP interface.
[no
] vc-label
egress-vc-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 no form of the command removes flowspec filtering from an IP interface.
qos network-policy-id fp-redirect-group
queue-group-name instance
instance-id]
b
a queue-group policer followed by the per-FP ingress shared queues referred to as policer-output-queues if the ingress context of the network IP interface from which the packet is received is redirected to a queue-group (csc-policing). The only exceptions to this behavior are for packets received from a IES/VPRN spoke interface and from an
R-VPLS spoke-SPD, which is forwarded to the R-VPLS IP interface. In these two cases, the ingress network shared queue for the packet FC defined in the network-queue policy applied to the ingress of the MDA/FP is used.
The no version of this command removes the redirection of the pseudowire to the queue-group.
[no
] vc-label
ingress-vc-label
[no
] control-channel-status
The no form of this command removes control channel status signaling from a spoke-SDP. It can only be removed if control channel status is shut down.
request-timer timer1 retry-timer
timer2 timeout-multiplier
multiplier
The no form of the command removes the association of the policy to the service.
Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the service in which it was created.
Note that you can configure an IES interface as a loopback interface by issuing the loopback command instead of the
sap sap-id command. The loopback flag cannot be set on an interface where a SAP is already defined and a SAP cannot be defined on a loopback interface.
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. The no form of this command causes the ptp-hw-assist to be disabled.
Command syntax: sap ipsec-
id.
private|
public:
tag associates an IPSec group SAP with this interface. This is the public side for an IPSec tunnel. Tunnels referencing this IPSec group in the private side may be created if their local IP is in the subnet of the interface subnet and the routing context specified matches with the one of the interface.
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.
The no form of the command removes the association.
|
Values
|
dual-homed — the primary dual homed aa-subscriber side service point of an aarp instance, only supported for IES and VPRN SAP and spoke-sdp dual-homed-secondary — One of the secondary dual homed aa-subscriber side service points of an aarp instance, only supported for IES and VPRN SAP and spoke-sdp.
|
The no form of the command deletes the specified IP/GRE or IP-IP tunnel from the configuration. The tunnel must be administratively shutdown before issuing the no ip-tunnel command.
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.
The no form of this command restores default configuration.
This command creates a new customer site or edits an existing customer site with the customer-site-name parameter. A customer site is an anchor point to create an ingress and egress virtual scheduler hierarchy. When a site is created, it must be assigned to a chassis slot or port. When scheduler policies are defined for ingress and egress, the scheduler names contained in each policy are created according to the parameters defined in the policy. Multi-service customer sites exist for the sole purpose of creating a virtual scheduler hierarchy and making it available to queues on multiple Service Access Points (SAPs).
Each customer site must have a unique name within the context of the customer. If customer-site-name already exists for the customer ID, the CLI context changes to that site name for the purpose of editing the site scheduler policies or assignment. Any modifications made to an existing site will affect all SAPs associated with the site. Changing a scheduler policy association may cause new schedulers to be created and existing queues on the SAPs to no longer be orphaned. Existing schedulers on the site may cease to exist, causing queues relying on that scheduler to be orphaned.
If the customer-site-name does not exist, it is assumed that an attempt is being made to create a site of that name in the customer ID context. The success of the command execution depends on the following:
|
•
|
The customer-site-name is valid.
|
|
•
|
The create keyword is included in the command line syntax (if the system requires it).
|
If the customer-site-name is invalid, a syntax error occurs; the command will not execute and the CLI context will not change.
route {ip-prefix/length |i p-prefix netmask} [create
]
no route {ip-prefix/length | ip-prefix netmask}
The no form of the command removes the respective route. Per default, there are no managed-routes configured.
The no form of the command removes the association of the policy to the service.
The pw-path-id is only configurable if all of the following is true:
The no form of the command deletes the PW path ID.
The no form of this command includes both source and destination parameters.
[no
] enable-mac-accounting
The no form of the command disables MAC accounting functionality on this interface.
The no form of the command removes IPv4 flowspec filtering from an IP interface.
The no form of the command removes IPv6 flowspec filtering from an IP interface.
host-connectivity-verify [source
{vrrp | interface
}] [interval
interval] [action
{remove
| alarm
}] [timeout
retry-timeout] [retry-count
count]
host-connectivity-verify [interval
interval] [action
{remove
| alarm
}] [timeout
retry-timeout] [retry-count
count] [family
family]
Specifies the source to be used for generation of subscriber host connectivity verification packets. The
interface keyword forces the use of the interface mac and ip addresses. Note that there are up to 16 possible subnets on a given interface, therefore subscriber host connectivity verification tool will use always an address of the subnet to which the given host is pertaining. In case of group-interfaces. one of the parent subscriber-interface subnets (depending on host's address) will be used.
This command configures the primary destination IPv4 or IPv6 address to use for an IP tunnel. This configuration applies to the outer IP header of the encapsulated packets. The source address,
remote-ip address and
backup-remote-ip address of a tunnel must all belong to the same address family (IPv4 or IPv6). When the remote-ip address contains an IPv6 address it must be a global unicast address.
This command configures the alternate destination IPv4 or IPv6 address to use for an IP tunnel. This destination address is used only if the primary destination configured with the remote-ip command is unreachable in the delivery service. The source address, remote-ip address and backup-remote-ip address of a tunnel must all belong to the same address family (IPv4 or IPv6). When the backup-remote-ip address contains an IPv6 address it must be a global unicast address.
The no form of the command removes the default SLA profile from the SAP configuration.
The no form of the command removes the default SLA profile from the SAP configuration.
The no form of the command removes the default subscriber identifcation policy from the SAP configuration.
The no form of this command returns the default value.
This command configures non-subscriber traffic profiles. It is used in conjunction with the profiled-traffic-only command on single subscriber SAPs and creates a subscriber host which is used to forward non-IP traffic through the single subscriber SAP without the need for SAP queues.
The no form of the command removes removes the profiles and disables the feature.
|
•
|
For VPRN SAPs with arp-reply-agent enabled with the optional sub-ident parameter, the static subscriber host’s sub-ident-string is used to determine whether an ARP request received on the SAP is sourced from a host belonging to the same subscriber as the destination host. When both the destination and source hosts from the ARP request are known on the SAP and the subscriber identifications do not match, the ARP request may be forwarded to the rest of the VPRN destinations.
|
If sub-ident is not enabled on the SAP arp-reply-agent, subscriber identification matching is not performed on ARP requests received on the SAP.
[no
] profiled-traffic-only
The no form of the command disables the command.
The no form of this command removes the accounting policy association from the SAP, and the acccounting policy reverts to the default.
When the no collect-stats command is issued the statistics are still accumulated by the IOMCFM 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.
This command enables the inclusion of the calling-station-id attribute in RADIUS authentication requests and RADIUS accounting messages. The value inserted is set at the SAP level. If no value is set at the SAP level, an empty string is included.
cpu-protection policy-id [mac-monitoring
]|[eth-cfm-monitoring
[aggregate
] [car
]] |[ip-src-monitoring
]
The configuration of no cpu-protection returns the interface/SAP to the default policies as shown above.
The no form of the command removes the values from the configuration.
The no form of the command disables and deletes the counters for this SAP or MPLS SDP binding.
mep mep-id domain
md-index association
ma-index [direction
{up
| down
}]
no mep mep-id domain
md-index association
ma-index
[no
] interface-support-enable
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.
[no
] ccm-padding-size
ccm-padding
oam eth-cfm eth-test mac-address mep
mep-id domain
md-index association
ma-index [priority
priority] [data-length
data-length
The no form of the command removes the values from the configuration.
The no form of the command removes the silent discarding of previously matching ETH-CFM PDUs.
accept (SAP Level for Epipe and VPLS)
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 or ipv6-filter-id with an ingress or egress SAP. The
filter policy 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. 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.
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 in the
configure>filter context 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.
[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.
config>service>ies>if>sap>egress>hsmda-queue-over>queue
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.
config>service>ies>if>sap>egress>hsmda-queue-overider>queue
The no form of the command returns the weight value for the queue to the default value.
config>service>ies>if>sap>egress>hsmda-queue-overider
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 the command restores the default dot1p evaluation behavior for the SAP.
By default, the bottom most service delineating Dot1Q tags Dot1P bits are used. Table 4 defines the default behavior for Dot1P evaluation when the
match-qinq-dot1p command is not executed.
no match-qinq-dot1p — No filtering based on p-bits.
top
or bottom
must be specified to override the default QinQ dot1p behavior.
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.
[no
] limit-unused-bandwidth
[no
] queue-frame-based-accounting
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.
qos policy-id [port-redirect-group
queue-group-name instance
instance-id]
qos policy-id [shared-queuing
|multipoint-shared
] [fp-redirect-group queue-group-name instance instance-id]
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.
A queue must be created as multipoint. The multipoint designator cannot be defined after the queue is created. If an attempt is made to modify the command to include the multipoint keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a pre-existing multipoint queue to edit queue-id parameters.
The no form of the command removes 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 max (maximum) option 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.
The min (minimum) option 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.
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 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.
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.
The no form of this command returns the CBS size to the default value.
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-in-kbytes | default
}
The no form of this command returns the MBS size assigned to the queue.
The no form of the command removes queue depth monitoring for the specified queue.
Weight defines the relative weight of this scheduler in comparison to other child schedulers and queues at the same strict
level defined by the level parameter in the applied scheduler olicy. Within the level, all weight values from active children at that level are summed and the ratio of each active child’s weight to the total is used to distribute the available bandwidth at that level. A weight is considered to be active when the queue or scheduler the weight pertains to has not reached its maximum rate and still has packets to transmit.
A 0 (zero) weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict level.
The cir-weight keyword defines the relative weight of this scheduler in comparison to other child schedulers and queues at the same
cir-level defined by the
cir-level parameter in the applied scheduler policy. Within the strict
cir-level, all
cir-weight values from active children at that level are summed and the ratio of each active child’s
cir-weight to the total is used to distribute the available bandwidth at that level. A
cir-weight is considered to be active when the queue or scheduler that the
cir-weight pertains to has not reached the CIR and still has packets to transmit.
A 0 (zero)
cir-weight value signifies that the child scheduler will receive bandwidth only after bandwidth is distributed to all other non-zero weighted children in the strict cir-level.
rate pir-rate [cir
cir-rate]
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.
For egress>queue-override>queue and
ingress>queue-override>queue:
For egress>sched-override>scheduler and
ingress>sched-override>scheduler:
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.
For egress>queue-override>queue and
ingress>queue-override>queue:
For egress>sched-override>scheduler and
ingress>sched-override>scheduler:
[no
] scheduler
scheduler-name
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).
|
|
Default
|
None. Each scheduler must be explicitly created.
|
rate pir-rate [cir
cir-rate]
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 is accepted. Any other value will result in an error without modifying the current PIR rate.
For egress>sched-override>scheduler and
ingress>sched-override>scheduler:
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 configures RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5, encapsulation for an ATM PVCC delimited SAP.
|
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. aal5snap-bridged — Bridged encapsulation for LLC encapsulated circuit (LLC/SNAP precedes protocol datagram) as defined in RFC 2684. aal5mux-bridged-eth-nofcs — Bridged 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.
The no form of the command sets the value back to the default.
This command enables the inclusion of the calling-station-id attribute in RADIUS authentication requests and RADIUS accounting messages. The value inserted is set at the SAP level. If no value is set at the SAP level, an empty string is included.
vrrp virtual-router-id [owner
]
The no form of this command removes the specified VRID from the IP interface. This terminates VRRP participation for the virtual router and deletes all references to the vrid. The VRID does not need to be shutdown in order to remove the virtual router instance.
The authentication-key command, within the
vrrp virtual-router-id context, is used to assign a simple text password authentication key to generate master VRRP advertisement messages and validating received VRRP advertisement messages.
The no form of this command restores the default null string to the value of key.
The key parameter identifies the simple text password used when VRRP Authentication Type 1 is enabled on the virtual router instance. Type 1 uses a string eight octets long that is inserted into all transmitted VRRP advertisement messages and compared against all received VRRP advertisement messages. The authentication data fields are used to transmit the key.
The key parameter is expressed as a string consisting up to eight alpha-numeric characters. Spaces must be contained in quotation marks ( “ ” ). The quotation marks are not considered part of the string.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is
not used, the less encrypted hash form is assumed.
[no
] bfd-enable
[service-id] interface
interface-name dst-ip
ip-address
The no form of this command removes BFD from the configuration.
The no form of the command returns the MAC address of the IP interface to the default value.
The message-interval command is available in both non-owner and owner vrrp virtual-router-id nodal contexts. If the message-interval command is not executed, the default message interval of 1 second will be used.
The no form of this command restores the default message interval value of 1 second to the virtual router instance.
The ping-reply command is only available in non-owner vrrp virtual-router-id nodal context. If the ping-reply command is not executed, ICMP Echo Requests to the virtual router instance IP addresses will be silently discarded.
The no form of this command restores the default operation of discarding all ICMP Echo Request messages destined to the non-owner virtual router instance IP addresses.
The policy command is only available in the non-owner vrrp virtual-router-id nodal context. The priority of owner virtual router instances is permanently set to 255 and cannot be changed by VRRP priority control policies. For non-owner virtual router instances, if the policy command is not executed, the base-priority will be used as the in-use priority.
The no form of this command removes any existing VRRP priority control policy association from the virtual router instance. All such associations must be removed prior to the policy being deleted from the system.
The no form of this command prevents a non-owner virtual router instance from preempting another, less desirable virtual router. Use the preempt command to restore the default mode.
The no form of this command restores the default value of 100 to base-priority.
The no form of the command specifies that a standby router should not forward traffic sent to virtual router's MAC address. However, the standby router should forward traffic sent to the standby router’s real MAC address.
The no form of this command restores the default operation of discarding all SSH packets destined to the non-owner virtual router instance IP addresses.
The telnet-reply command is only available in non-owner VRRP nodal context. If the telnet-reply command is not executed, Telnet packets to the virtual router instance IP addresses will be silently discarded.
The no form of this command restores the default operation of discarding all Telnet packets destined to the non-owner virtual router instance IP addresses.
|
Values
|
service-id: 1 — 2147483648 svc-name: An existing service name up to 64 characters in length.
|
The no form of the command reverts to the default.
tms-interface interface-name [create
] [off-ramp-vprn
off-ramp-svc] [mgmt-vprn
mgmt-svc]
The no form of the command removes the interface name from the configuration.
|
Values
|
service-id: 1 — 2148007978 svc-name: An existing service name up to 64 characters in length.
|
|
Values
|
service-id: 1 — 2148007978 svc-name: An existing service name up to 64 characters in length.
|
address {ip-address/mask|ip-address netmask}
The no form of the command removes the IP address information from the interface configuration.
The no form of the command removes the description from the interface configuration.
The no form of the command removes the IP address information from the interface configuration.
The no form of the command removes the password.
