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.g
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.
vpls service-id customer
customer-id vpn vpn-id [m-vpls
] [bvpls | i-vpls
] [etree] [create
]
This command creates or edits a Virtual Private LAN Services (VPLS) instance. The vpls command is used to create or maintain a VPLS service. 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 create keyword must be specified if the
create command is enabled in the
environment context. 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 VPLS service instance with the specified
service-id. The service cannot be deleted until all SAPs and SDPs defined within the service ID have been shutdown and deleted, and the service has been shutdown.
|
Values
|
service-id: 1 — 2147483648 svc-name: 64 characters maximum
|
The no form of the command disables STP on the backbone VPLS service.
[no
] block-on-mesh-failure
The no form of this command reverts to the default setting.
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.
[no
] def-mesh-vc-id
vc-id
The no form of this command disables the VC-ID.
The no form of the command reverts to the default.
The no form of the command removes the name from the configuration.
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.
Like in a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the VPLS forwarding database (FDB). The
disable-aging command turns off aging for local and remote learned MAC addresses.
When no disable-aging is specified for a VPLS, it is possible to disable aging for specifc SAPs and/or spoke SDPs by entering the
disable-aging command at the appropriate level.
When the disable-aging command is entered at the VPLS level, the
disable-aging state of individual SAPs or SDPs will be ignored.
The no form of this command enables aging on the VPLS service.
When disable-learning is enabled, new source MAC addresses will not be entered in the VPLS service forwarding database. This is true for both local and remote MAC addresses.
When disable-learning is disabled, new source MAC addresses will be learned and entered into the VPLS forwarding database.
The no form of this command enables learning of MAC addresses.
The no form of this command allows flooding of packets with unknown destination MAC addresses in the VPLS.
no discard-unknown — Packets with unknown destination MAC addresses are flooded.
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.
[no
] auto-learn-mac-protect
The no form of the command disables the automatic population of the MAC protect list.
[no
] ignore-standby-signaling
[no
] suppress-standby-signaling
[no
] fdb-table-high-wmark
high-water-mark
This command specifies the value to send logs and traps when the threshold is reached.
[no
] fdb-table-low-wmark
low-water-mark
This command specifies the value to send logs and traps when the threshold is reached.
The fdb-table-size specifies the maximum number of forwarding database entries for both learned and static MAC addresses for the VPLS instance.
The no form of this command returns the maxium FDB table size to default.
250 — Forwarding table of 250 MAC entries.
[no
] interface
ip-int-name
address ip-address[/mask]> [netmask]
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. When the
no address command is entered, the interface becomes operationally down.
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 netmask
When the arp-populate and
lease-populate commands are enabled on an 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 default value for arp-timeout is 14400 seconds (4 hours).
The no form of this command restores
arp-timeout to the default value.
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.
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 a static ARP entry.
isid-policy allows finer control of ISID multicast but is not typically required for SPBM operation. Use of ISID policies can cause additional flooding of multicast traffic.
The no advertise-local option prevents the advertisement of any locally defined I-VPLS ISIDs or static-isids in the range in a B-VPLS. For I-VPLS services or static-isids that are primarily unicast traffic, the use-def-mcast and no advertise-local options allows the forwarding of ISID based multicast frames locally using the default multicast. The
no advertise-local option also suppresses this range of ISIDs from being advertised in ISIS. When using the
use-def-mcast and
no advertise-local policies, the ISIDs configured under this
static-isid declarations SPBM treats the ISIDs as belonging to the default tree.
The use-def-mcast option prevents local installation of the ISIDs in the range in the MFIB and uses the default multicast tree instead for a B-VPLS. In a node that does not have I-VPLS or static-isids, this command prevents the building of an MFIB entry for this ISID when received in a SPBM TLV and allows the broadcast of ISID based traffic on the default multicast tree. If an
isid-policy exists, the core nodes can have this policy to prevent connectivity problems when some nodes are advertizing an ISID and others are not. In a I-VPLS service if the customer MAC (C-MAC) is unknown, a frame will have the Multicast DA for an ISID (PBB-OUI + ISID) flooded on the default multicast tree and not pruned.
The no form of this command implies the use of existing hashing options.
The no form disables the SPI function.
The no form of this command returns the local aging timer to the default value.
local age 300 — Local MACs aged after 300 seconds.
When enabled in a VPLS, mac-move monitors the re-learn rate of each MAC. If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. The SAP can be disabled permanently (until a
shutdown/
no shutdown command is executed) or for a length of time that grows linearly with the number of times the given SAP was disabled. You have the option of marking a SAP as non-blockable in the
config>service>vpls>sap>limit-mac-move or
config>service>vpls>spoke-sdp>limit-mac-move contexts. This means that when the re-learn rate has exceeded the limit, another (blockable) SAP will be disabled instead.
The mac-move command enables the feature at the service level for SAPs and spoke SDPs, as only those objects can be blocked by this feature. Mesh SDPs are never blocked, but their re-learn rates (sap-to-mesh/spoke-to-mesh or vice versa) are still measured.
mac-move will disable a VPLS port when the number of relearns detected has reached the number of relearns needed to reach the move-frequency in the 5-second interval. For example, when the move-frequency is configured to 1 (relearn per second) mac-move will disable one of the VPLS ports when 5 relearns were detected during the 5-second interval because then the average move-frequency of 1 relearn per second has been reached. This can already occur in the first second if the real relearn rate is 5 relearns per second or higher.
The no form of this command disables MAC move.
The no form of this command switches back to full MAC lookup.
The no form of the command reverts to the default value.
sap [split-horizon-group
group-name] [create
] [capture-sap
]
[no
] cumulative-factor
factor
The no form of the command reverts to the default value.
[no
] mfib-table-high-wmark
high-water-mark
[no
] mfib-table-low-wmark
low-water-mark
The mfib-table-size parameter specifies the maximum number of multicast database entries for both learned and static multicast addresses for the VPLS instance. When a table-size limit is set on the mfib of a service which is lower than the current number of dynamic entries present in the mfib then the number of entries remains above the limit.
The no form of this command removes the configured maxium MFIB table size.
The no form of this command returns the remote aging timer to the default value.
remote age 900 — Remote MACs aged after 900 seconds
[no
] send-flush-on-bvpls-failure
The no form of this command disables the generation of LDP MAC flush in I-VPLS on failure of SAP/endpoint/spoke-SDP in the related B-VPLS.
[no
] propagate-mac-flush-from-bvpls
The no form of this command disables the propagation of LDP MAC Flush in I-VPLS from the related B-VPLS.
[no
] send-flush-on-failure
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 resets the allow-ip-int-bind flag on the VPLS service. If the VPLS service currently has an IP interface from an IES or VPRN service attached, the no allow-ip-int-bind command will fail. Once the allow-ip-int-bind flag is reset on the VPLS service, the configuration and hardware restrictions associated with setting the flag are removed. The port network mode hardware restrictions are also removed.
The no form of the command reverts the default.
The no form of reverts the default.
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.
The no form of the command removes the SAP ID from the configuration.
This command configures the BGP multi-homing site minimum down time. When set to a non-zero value, if the site goes operationally down it will remain operationally down for at least the length of time configured for the site-min-down-timer, regardless of whether other state changes would have caused it to go operationally up. This timer is restarted every time that the site transitions from up to down. Setting this parameter to zero allows the minimum down timer to be disabled for this service.
|
•
|
If the site-min-down-timer is active and a BGP multi-homing update is received from the designated forwarder indicating its site has gone down, the site-min-down-timer is immediately terminated and this PE becomes the designated forwarder if the BGP multi-homing algorithm determines it should be the designated forwarder.
|
The no form of this command reverts to the default value.
Taken from the value of site-min-down-timer configured for Multi-Chassis BGP Multi-Homing under the
configure>redundancy>bgp-multi-homing context.
The no form of the command reverts the default.
The no form of the command removes the parameter from the configuration.
The no form of the command to reverts to the default value.
Each LSP received is maintained in an LSP database until the lsp-lifetime expires unless the originating router refreshes the LSP. By default, each router refreshes its LSP’s every 20 minutes (1200 seconds) so other routers will not age out the LSP.
The no form of the command reverts to the default value.
1200 — LSPs originated by the router should be valid for 1200 seconds (20 minutes).
lsp-wait lsp-wait [lsp-initial-wait [lsp-second-wait]]
The no overload command does not affect the
overload-on-boot function.
This state can be cleared with the config>router>isis>no overload command.
The no form of the command removes the overload-on-boot functionality from the configuration.
Use show router ospf status and/or
show router isis status commands to display the administrative and operational state as well as all timers.
The overload command can be useful in circumstances where the router is overloaded or used prior to executing a
shutdown command to divert traffic around the router.
The no form of the command causes the router to exit the overload state.
The no form of the command reverts to the default value.
100 — LSPs are sent in 100 millisecond intervals.
The no form of the command reverts to the default value.
[no
] split-horizon-group
[group-name] [residential-group]
The no form of the command removes the group name from the configuration.
The no version of the command means a SAP over a LAG that is not operational will be removed from the forwarding process.
[no
] auto-learn-mac-protect
When the restrict-protected-src is enabled on an SHG the action only applies to the associated SAPs (no action is taken by default for spoke SDPs in the SHG). In order to enable this function for spoke SDPs within a SHG, the
restrict-protected-src must be enabled explicitly under the spoke-SDP. If required,
restrict-protected-src can also be enabled explicitly under specific SAPs within the SHG.
The use of “restrict-protected-src discard-frame” is mutually exclusive with both the “
restrict-protected-src [
alarm-only]” command and with the configuration of manually protected MAC addresses within a given VPLS.
Note that the alarm-only parameter is not supported on the 7750 SR-a or “restrict-protected-src discard-frame” can only be enabled on SAPs on FP2 or later hardware or on SDPs where all network interfaces are on FP2 or later hardware.
The no form of this command removes the specified ranges and deletes the pre-provisioned VPLS instances and related SAPs. The command will fail if any of the VPLS instances in the affected ranges have a provisioned SAP.
The no form of this command removes the binding and deletes the related VPLS instances. The command will fail if any of the affected VPLS instances have either a provisioned SAP or an active MVRP declaration/registration or if the related vpls-group id is in no shutdown state. Any changes to the vpls-template-binding require the vpls-group to be in shutdown state.
The no form of this command removes the binding and deletes the related SAP instances. The command will fail if any of the affected VPLS instances have either a provisioned SAP or an active MVRP declaration/registration registration or if the related vpls-group is in no shutdown state. Any changes to the vpls-sap-template-binding require the vpls-group to be in shutdown state. New control SAP additions to the management VPLS are allowed as long as data VPLS instantiations/removals for vpls-groups are not in progress. Control SAPs can be removed at any time generating the removal of related data SAPs from the data VPLS. The shutdown or no shutdown state for the control SAPs does not have any effect on data SAPs instantiated with this command.
The no form of this command disallows MVRP control over this VPLS. The VPLS will be created with a regular FIB and will become as a result active upon creation time. Command change is allowed only when the related vpls-group is in shutdown state.
The no form of this command disables tracking of the operational status for the last active SAP in the VPLS. MVRP will stop declaring the VLAN only when the last provisioned customer (UNI) SAP associated locally with the service is deleted. Also MVRP will declare the associated VLAN attribute as soon as the first provisioned SAP is created in the associated VPLS instance, regardless of the operational state of the SAP.
The no form of the command removes the specified group id.
[no
] interface
ip-int-name
address {ip-address/mask | ip-address netmask}
[no
] dynamic-topology-discover
The no form of this command disables the feature.
The no form of this command disables the feature.
The no form of this command disables the feature.
|
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
|
This command enables and disables dynamic host lease state management for VPLS SAPs. For VPLS, DHCP snooping must be explicitly enabled (using the snoop command) at all points where DHCP messages requiring snooping enter the VPLS instance (both from the DHCP server and from the subscribers). Lease state information is extracted from snooped DHCP ACK messages to populate lease state table entries for the SAP.
The no form of this command returns the system to the default.
The no form of this command returns the system to the default value.
replace — In the upstream direction (from the user), the Option 82 field from the router is inserted in the packet (overwriting any existing Option 82 field). In the downstream direction (towards the user) the Option 82 field is stripped (in accordance with RFC 3046).
drop — The DHCP packet is dropped if an Option 82 field is present, and a counter is incremented.
keep — The existing information is kept in the packet and the router does not add any additional information. In the downstream direction the Option 82 field is not stripped and is sent on towards the client.
When enabled, the router sends an ASCII-encoded tuple in the circuit-id suboption of the DHCP packet. This ASCII-tuple consists of the access-node-identifier, service-id, and SAP-ID, separated by “|”. If no keyword is configured, then the circuit-id suboption will not be part of the information option (Option 82).
If disabled, the circuit-id suboption of the DHCP packet will be left empty.
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 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.
Use the no form of the command to disable DHCP snooping on the specified VPLS SAP or SDP binding.
The no form of this command returns the auto-detection setting to the default value.
This command configures the SAP or SDP as an edge or non-edge port. If auto-edge is enabled for the SAP, this value will be used only as the initial value.
NOTE: The function of the edge-port command is similar to the
rapid-start command. It tells RSTP that it is on the edge of the network (for example, there are no other bridges connected to that port) and, as a consequence, it can immediately transition to a forwarding state if the port becomes available.
The no form of this command returns the edge port setting to the default value.
|
•
|
in rstp or mstp mode, but only when the SAP or spoke SDP has not fallen back to legacy STP operation, the value configured by the hello-time command is used;
|
The no form of this command returns the hello time to the default value.
The no form of this command returns the hold count to the default value
This command instructs STP on the maximum number of bridges behind this SAP or spoke SDP. If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast transitions). If more than two bridges are connected via a shared media, their SAP or spoke SDPs should all be configured as shared, and timer-based transitions are used.
The no form of this command returns the link type to the default value.
The no form of this command sets port-priority to its default value.
The no form of this command sets port-priority to its default value.
The no form of this command returns the max ageto the default value.
mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
The no form of this command returns the STP variant to the default.
[no
] mst-instance
mst-inst-number
This command specifies the bridge priority for this specific Multiple Spanning Tree Instance for this service. The bridge-priority value reflects likelihood that the switch will be chosen as the regional root switch (65535 represents the least likely). It is used as the highest 4 bits of the Bridge ID included in the MSTP BPDU's generated by this bridge.
The no form of this command sets the bridge-priority to its default value.
[no
] vlan-range
[vlan-range]
Every VLAN range that is not assigned within any of the created mst-instance is automatically assigned to mst-instance 0. This instance is automatically maintained by the software and cannot be modified. Changing the VLAN range value can be performed only when the given mst-instance is shutdown.
The no form of this command removes the
vlan-range from given
mst-instance.
The no form of this command sets the
hops-count to its default value.
The no form of this command removes
region-name from the configuration.
The no form of this command returns MST configuration revision to its default value.
STP suggests that the path cost is defined as a function of the link bandwidth. Since SAPs and spoke SDPs are controlled by complex queuing dynamics, in the
7750 SR, and the STP path cost is a purely static configuration.
The no form of this command returns the path cost to the default value.
[no
] port-num
virtual-port-number
The no form of this command returns the bridge priority to the default value.
STP computes the actual priority by taking the input value and masking out the lower four bits.The result is the value that is stored in the SDP priority parameter.
For instance, if a value of 0 is entered, masking out the lower 4 bits results in a parameter value of 0. If a value of 255 is entered, the result is 240.
The no form of this command returns the STP priority to the default value.
sap sap-id [split-horizon-group
group-name][capture-sap] [create
] [eth-ring ring-index] [root-leaf-tag | leaf-ac]
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 VPLS SAP can be defined with Ethernet ports, SONET/SDH or TDM channels. The limits of the number of SAPs and SDPs supported in a VPLS service depends on the hardware used. Each SDP must have a unique destination or an error will be generated. Split horizon groups can only be created in the scope of a VPLS service.
specified after root-leaf-tag to replace the outer SAP-ID for leaf traffic. The leaf tag VID is only significant between peering VPLS but the values must be consistent on each end.
[no
] discard-unknown-source
The no form of this command causes packets with an unknown source MAC addresses to be forwarded by destination MAC addresses in VPLS.
The no form of this command removes eth-ring from this SAP
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
}] primary-valn-enable
[vlan
vlan-id]
no mep mep-id domain
md-index association
ma-index
mip [mac
mac-address] primary-vlan-enable
[vlan
vlan-id]
[no
] interface-support-enable
config>service>vpls>spoke-sdp>eth-cfm>mep>ais-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.
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 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).
accept (SAP Level for Epipe and VPLS)
The no form of the command reverts to the default values. This is not applicable to a VPLS contexts that is not B-VPLS based.
The no form of the command reverts to the default values.
This command indicates whether or not the mac-move agent, when enabled using config>service>vpls>mac-move or
config>service>epipe>mac-move, will limit the MAC re-learn (move) rate on this SAP.
The no form of the command restores the global MAC learning limitations for the SAP or spoke SDP.
The no form of this command removes the endpoint from the MC-EP. Single chassis behavior applies.
The no form of this command removes the MC-Endpoint object.
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.
This command is mutually exclusive with the SAP ingress and egress scheduler-policy commands. If a
scheduler-policy has been applied to either the ingress or egress nodes on the SAP, the
multi-service-site command will fail without executing. The locally applied scheduler policies must be removed prior to executing the
multi-service-site command.
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.
[no] static-isid range entry-id isid [to isid] [create]
[no
] static-mac
ieee-mac-address [create]
The no form of this command deletes the static MAC entry with the specified MAC address associated with the SAP from the VPLS forwarding database.
The no form of the command removes the default SAP to the managed VLAN list.
|
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, the PVCC’s operational status is no longer affected by the 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 from DOWN due to alarm-cell processing). RDI cells are not generated as result of PVCC going into an AIS or RDI state, however, the PVCC’s OAM status will record OAM faults as described above.
[no
] limit-unused-bandwidth
[no
] queue-frame-based-accounting
encap-group group-name [type
group-type] [qos-per-member
] [create
]
The user can configure one or more encap-groups in the egress context of the same B-SAP, thus defining different ISID values and applying each a different SAP egress QoS policy, and optionally a different scheduler policy/agg-rate. Note that ISID values are unique within the context of a B-SAP. The same ISID value cannot be re-used in another encap-group under the same B-SAP but can be re-used in an encap-group under a different B-SAP. Finally, if the user adds to an encap-group an ISID value which is already a member of this encap-group, the command causes no effect. The same if the user attempts to remove an ISID value which is not a member of this encap-group.
The keyword qos-per-member allows the user to specify that a separate queue set instance and scheduler/agg-rate instance will be created for each ISID value in the encap-group. By default, shared instances will be created for the entire encap-group.
Note that when the B-SAP is configured on a LAG port, the ISID queue instances defined by all the encap-groups applied to the egress context of the SAP will be replicated on each member link of the LAG. The set of scheduler/agg-rate instances will be replicated per link or per IOM depending if the adapt-qos option is set to link/port-fair mode or distribute mode. This is the same behavior as that applied to the entire B-SAP in the current implementation.
The no form of this command deletes the encap-group.
[no
] member
encap-id [to
encap-id]
The no form of this command removes the single or range of ISID values from the encap-group.
no filter [ip
ip-filter-id] [mac
mac-filter-id] [ipv6
ipv6-filter-id]
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.
[no
] hsmda-queue-override
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 SAP from any egress multicast group in which it may currently have membership. The SAP will be removed from all efficient multicast replication chains and normal replication will apply to the SAP. A momentary gap in replications to the SAP destination while it is being moved is possible. If the SAP is not currently a member in an egress multicast group, the command has no effect.
The group-name is required when specifying egress multicast group membership on a SAP. An egress multicast group with the specified egress-multicast-group-name must exist and the SAP must pass all common requirements or the command will fail.
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 enabled, only the P-bits/DEI bit in the top Q-tag are marked.
The no form of this command disables the command.
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
The no form of the command removes any existing policer-control-policy overrides and the policer-control-overrides node from the SAP.
config>service>vpls>sap>egress
config>service>vpls>sap>ingress
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.
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 or subscriber management sub-profile 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.
cbs size [bytes
| kilobytes]
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.
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:
qos policy-id [shared-queuing | multipoint-shared] [fp-redirect-group queue-group-name instance instance-id]
This keyword can only be specified on SAP ingress. Multipoint shared queuing is a superset of shared queuing. When multipoint shared queuing keyword is set, in addition to the unicast packets, multipoint packets also used shared queues.
qos policy-id [port-redirect-group
queue-group-name instance
instance-id]
The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.
config>service>vpls>sap>ingress>queue-override
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>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.
The no form of this command returns the CBS size to the default value.
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>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>vpls>sap>egress>queue-override>queue
config>service>vpls>sap>ingress>queue-override>queue
config>service>vpls>sap>egress>hsmda-queue-override>queue
The no form of this command returns the MBS size assigned to the queue.
For sap>egress>queue-override>queue and sap
>ingress>queue-override>queue
For sap>egress>hsmda-queue-override>queue
mbs {size-in-kbytes | default
}
config>service>vpls>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>vpls>sap>egress>queue-override>queue
config>service>vpls>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.
For egress>queue-override>queue and
ingress>queue-override>queue:
For egress>hsmda-queue-over>queue:
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:
config>service>vpls>sap>ingress>queue-override
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>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.
The no form of this command returns the CBS size to the default value.
config>service>vpls>sap>egress>queue-override>queue
config>service>vpls>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-in-kbytes | default
}
config>service>vpls>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>vpls>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>vpls>sap>egress>queue-override>queue
config>service>vpls>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>vpls>sap>egress>queue-override>queue
The no form of the command removes the slope policy override for the WRED queue on the egress SAP.
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).
parent [weight
weight] [cir-weight
cir-weight]
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]
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.
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 — 10000000 or the keyword
max or
sum 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 form of this 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 removes a non-associated policer control policy from the system. The command will not execute when policer-name is currently associated with any SAP or subscriber management sub-profile context.
This command creates the accounting policy context that can be applied to a SAP or SDP.
An accounting policy must be defined before it can be associated with a SAP or SDP.
If the policy-id does not exist, an error message is generated.
A maximum of one accounting policy can be associated with a SAP or SDP at one time. Accounting policies are configured in the
config>log context.
The no form of this command removes the accounting policy association from the SAP or SDP, and the acccounting policy reverts to the default.
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.
[no
] vpls-template
name/id
[no
] vpls-sap-template
name/id
The no form of the command disables the temporary flooding behavior.
After the user performs a no shutdown under the context of the inclusive node and the expiration of a delay timer, BUM packets will be forwarded over an automatically signaled mLDP P2MP LSP or over an automatically signaled instance of the RSVP P2MP LSP specified in the LSP template.
The root-and-leaf command is required otherwise this node will behave as a leaf only node by default. When the node is leaf only for the I-PMSI of type P2MP RSVP LSP, no PMSI Tunnel Attribute is included in BGP-AD route update messages and thus no RSVP P2MP LSP is signaled but the node can join RSVP P2MP LSP rooted at other PE nodes participating in this VPLS/B-VPLS service. Note that the user must still configure a LSP template even if the node is a leaf only. For the I-PMSI of type mLDP, the leaf-only node will join I-PMSI rooted at other nodes it discovered but will not include a PMSI Tunnel Attribute in BGP-AD route update messages. This way a leaf only node will forward packets to other nodes in the VPLS/B-VPLS using the point-to-point spoke-sdp’s.
The no version of this command re-instates the default value for this delay timer.
The no version of this command re-instates the default value.
The no version of this command removes the P2MP LSP template from the I-PMIS configuration.
mesh-sdp sdp-id[:
vc-id] [
vc-type {
ether |
vlan}]
[root-leaf-tag | leaf-ac]
no mesh-sdp sdp-id[:
vc-id]
The SDP must already be defined in the config>service>sdp context in order to associate the SDP with a valid 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.
Several SDPs can be bound to a VPLS. Each SDP must be destined to a different router. If two sdp-id bindings terminate on the same router, an error occurs and the second SDP is binding is rejected.
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. (hex 5)
spoke-sdp sdp-id[:
vc-id] [vc-type
{ether
| vlan
}] [split-horizon-group
group-name] endpoint [no-endpoint
] [root-leaf-tag | leaf-ac]
The SDP must already be defined in the config>service>sdp context in order to associate an SDP with a VPLS 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.
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. (hex 5)
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 inserts one dot1Q tag within each encapsulated Ethernet packet transmitted to the far end and strips one dotQ tag, if a tag is present, from traffic received on the pseudowire.
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.
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. 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.
The allowed-mda-destinations node and the corresponding mda command are used on spoke and mesh SDP bindings to provide a list of MDA destinations in the chassis that are allowed as destinations for multicast streams represented by [*,g] and [s,g] multicast flooding records on the VPLS service. The MDA list only applies to IP multicast forwarding when IGMP snooping is enabled on the VPLS service. The MDA list has no effect on normal VPLS flooding such as broadcast, L2 multicast, unknown destinations or non-snooped IP multicast.
[no
] static-mac
ieee-mac-address
The no form of this command deletes the static MAC entry with the specified MAC address associated with the SDP from the VPLS forwarding database.
The no form of the command removes the transit policy ID from the spoke SDP configuration.
The no form of this command disables the command.
This command specifies a default destination string for all subscribers associated with the SAP. The command also accepts the use-top-q flag that automatically derives the string based on the top most delineating Dot1Q tag from the SAP’s encapsulation.
The no form of the command removes the default subscriber identification string from the 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 SLA profile 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 the profiles and disables the feature.
|
•
|
For 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 service 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 the command removes the default subscriber identifcation policy from the SAP configuration.
This command adds a static multicast group as a (*, g) or as one or more (s,g) records. When a static MLD or IGMP group is added, multicast data for that (*,g) or (s,g) is forwarded to the specific SAP or SDP without receiving any membership report from a host.
The no form of the command removes the policy association from the VPLS configuration.
The no form of the command removes the specified MAC name or MAC address from the list of Fault Propagation BMAC addresses associated with the SAP (or SDP).
[no
] force-qinq-vc-forwarding
This command forces two VLAN tags to be inserted and removed for spoke and mesh SDPs that have either vc-type ether or
vc-type vlan. The use of this command is mutually exclusive with the
force-vlan-vc-forwarding command.
The VLAN identifiers and dot 1p/DE bits inserted in the two VLAN tags are taken from the inner tag received on a qinq SAP or qinq mesh/spoke SDP, or from the VLAN tag received on a dot1q SAP or mesh/spoke SDP (with vc-type vlan or
force-vlan-vc-forwarding), or taken from the outer tag received on a qtag.* SAP or 0 if there is no service delimiting VLAN tag at the ingress SAP or mesh/spoke SDP. The VLAN identifiers in both VLAN tags can be set to the value configured in the
vlan-vc-tag parameter in the
pw-template or under the mesh/spoke SDP configuration. In the received direction, the VLAN identifiers are ignored and the dot1p/DE bits are not used for ingress classification. However, the inner dot1p/DE bits are propagated to the egress QoS processing.
The no form of this command sets default behavior.
[no
] force-vlan-vc-forwarding
This command forces vc-vlan-type forwarding in the data path for spoke/mesh SDPs which have
ether vc-type. This command is not allowed on vlan-vc-type SDPs.
The no form of this command sets default behavior.
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, and local PE will insert the flow label interface parameters sub-TLV with F=1 in the pseudowire 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 pseudowire 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 pseudowire 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.
[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 removes the values from the configuration.
The no form of the command removes the values from the configuration.
The no form of the command removes the value from the configuration.
The no form of this command disables the check.
The no form of the command removes the policy association from the SAP or SDP.
no import — No import policy is specified.
This command configures the bandwidth for the interface's multicast CAC policy traffic. When disabled (no unconstrained-bw) there will be no checking of bandwidth constraints on the interface level. When enabled and a policy is defined, enforcement is performed. The allocated bandwidth for optional channels should not exceed the
unconstrained-bw minus the
mandatory-bw and the mandatory channels have to stay below the specified value for the
mandatory-bw. After this interface check, the bundle checks are performed.
If the bandwidth value is 0, no mandatory channels are allowed. If
bandwith is not configured, then all mandatory and optional channels are allowed.
If the value of mandatory-bw is equal to the value of
bandwidth, then all the unconstrained bandwidth on a given interface is allocated to mandatory channels configured through multicast CAC policy on that interface and no optional groups (channels) are allowed.
The value of mandatory-bw should always be less than or equal to that of
bandwidth, An attempt to set the value of
mandatory-bw greater than that of
bandwidth, will result in inconsistent value error.
level level-id bw
bandwidth
The no form of this command disables the check.
The no form of this command disables the check.
If the send-queries command is enabled on this SAP or spoke SDP, the
mrouter-port parameter can not be set.
This command configures the IGMP query interval. If the send-queries command is enabled, this parameter specifies the interval between two consecutive general queries sent by the system on this SAP or SDP. The configured query-interval must be greater than the configured query-response-interval. If send-queries is not enabled on this SAP or SDP, the configured query-interval value is ignored.
This command configures the IGMP query response interval. If the send-queries command is enabled, this parameter specifies the maximum response time advertised in IGMPv2/v3 queries.
If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If this SAP or SDP is expected to be 'lossy', this parameter may be increased. IGMP snooping on this SAP or SDP is robust to (robust-count-1) packet losses.
[no
] attribute-table-size
value
[no
] attribute-table-size
value
[no
] attribute-table-high-wmark
high-water-mark
[no
] attribute-table-low-wmark
low-water-mark
[no
] leave-all-time
value
The no form of the command removes the PIM snooping configuration.
This command associates the context to which it is configured to the opeational group specified in the name. The oper-group
name must be already configured under config>service before its name is referenced in this command.
The no form of the command removes the association.
[no
] monitor-oper-group
name
The no form of the command removes the association.
This command sets the PIM snooping mode to proxy or plain snooping.
The no form of the command removes the source from the configuration.
The no form of the command removes the starg entry from the configuration.
When the send-query command is configured, all type of queries generate ourselves are of the configured
version. If a report of a version higher than the configured version is received, the report gets dropped and a new “wrong version” counter is incremented.
If the send-query command is not configured, the
version command has no effect. The version used on that SAP or SDP will be the version of the querier. This implies that, for example, when there is a v2 querier, a v3 group or group-source specific query when a host wants to leave a certain group will never be sent.
The no form of the command disables anti-spoof filtering on the SAP.
The no form of the command returns the value to the default.
The no form of the command returns the value to the default.
ARP replies and requests received on a SAP with arp-reply-agent enabled will be evaluated by the system against the anti-spoof filter entries associated with the ingress SAP (if the SAP has anti-spoof filtering enabled). ARPs from unknown hosts on the SAP will be discarded when anti-spoof filtering is enabled.
Static hosts can be defined on the SAP using the host command. Dynamic hosts are enabled on the system by enabling the
lease-populate command in the SAP’s
dhcp context. In the event that both a static host and a dynamic host share the same IP and MAC address, the VPLS ARP reply agent will retain the host information until both the static and dynamic information are removed. In the event that both a static and dynamic host share the same IP address, but different MAC addresses, the VPLS ARP reply agent is populated with the static host information.
The arp-reply-agent command will fail if an existing static host on the SAP does not have both MAC and IP addresses specified. Once the ARP reply agent is enabled, creating a static host on the SAP without both an IP address and MAC address will fail.
The no form of the command disables ARP-reply-agent functions for static and dynamic hosts on the SAP.
|
•
|
When sub-ident is not configured, the arp-reply-agent does not attempt to identify the subscriber information for the destination or originating host and will not discard an ARP request based on subscriber information.
|
The no form of the command disables FRF12 headers.
The no form of the command rremoves the value.
The no form of this command restores the default mode of operation.
Specifies the source MAC address to be used for generation of subscriber host connectivity verification packets.
Further subcategories are created for an IGMP (s,g) flooding list. A Layer 2 (s,g) record is created in a specific VPLS instance (the instance the (s,g) flow ingresses). SAPs within that VPLS context that join the (s,g) record are considered native SAPs within the flooding list. SAPs that join the (s,g) flooding list through the multicast VPLS registration process (MVR) from another VPLS context using the from-vpls command are considered alien SAPs. The distinction between native and alien in the list is maintained to allow the forwarding plane to enforce or suspend split-horizon-group (SHG) squelching. When the source of the (s,g) matching packet is in the same SHG as a native SAP, the packet must not be replicated to that SAP. For a SAP in another VPLS context, the source SHG of the packet has no meaning and the forwarding plane must disregard SHG matching between the native source of the packet and the alien destination. Because the SHG squelch decision is done for the whole chain based on the first SAP in the chain, all SAPs in the chain must be all native or all alien SAPs. Chains for IGMP (s,g) flooding lists are created using the following rules:
The no form of the command removes a specific egress multicast group. Deleting an egress multicast group will only succeed when the group has no SAP members. To remove SAP members, use the
no multicast-group group-name command under each SAP’s egress context.
Note: Efficient multicast replication will only be performed on IOMs that support chassis mode b If an IOM does not support mode b operation, egress-multicast-group membership is ignored on that IOM’s egress forwarding planes. The chassis need not be placed into mode b for efficient multicast replication to be performed on the capable IOMs.
The no form of the command removes an existing description string from egress-multicast-group.
The no form of the command restores the default value.
The destinations per pass parameter can be modified at any time. Be aware that when changing the maximum chain length, the system will rebuild the chains according to the new limit. When this happens, it is possible that packets will not be replicated to a destination while it is being reorganized in the flooding list’s chains. Only the chains associated with the egress-multicast-group context the command is executed in will be affected by changing the parameter.
Setting the destinations per pass parameter to a value of 0 has the effect of removing from all egress forwarding planes all chains with members from the egress-multicast-group. Replication to each destination SAP from the group is performed using the normal method (non-efficient replication). The value 0 is not considered a normal value for dest-chain-limit and is provided for debugging purposes only. Setting the value to 0 is persistent between reboots of the system.
Setting the destinations per pass parameter to a value of 1 has the effect of placing each egress-multicast-group member SAP into a chain with a single SAP. The value 1 is not considered a normal value for the
dest-chain-limit and is provided for debugging purposes only. Setting the value to 1 is persistent between reboots of the system.
Changing the egress-filter parameters within the
sap-common-requirements node automatically changes the egress filter applied to each member SAP. If the filter cannot be changed on the SAP due to resource constraints, the modification will fail.
The no form of the command removes the egress-filter removes the egress filter from each member SAP. The
no egress-filter command specifies that an egress filter (IP, IPv6 or MAC) is not applied to a new member SAP within the egress-multicast-group.
no filter. The egress filter ID must be defined with the associated
ip or
mac keyword. If an egress-filter is not specified or the no egress-filter command is executed in the sap-common-requirements node, a new member SAP does not have an egress IP or MAC filter defined.
This command specifies the encapsulation type that must exist on the SAP’s access port to allow the SAP membership within the egress-multicast-group. The config>port>ethernet>access>encap-type command is used to define the encapsulation type for the Ethernet port. The allowed encapsulation type values are dot1q and null. If the SAP does not exist on a port with the specified encap-type, it will not be allowed into the egress-multicast-group.
If at least one SAP is currently a member of the efficient-multicast-group, the encap-type cannot be changed within the sap-common-requirements node. If the efficient-multicast-group does not contain any member SAPs, the
encap-type may be changed at any time.
The no form of the command returns the egress-multicast-group required encapsulation type for SAPs to dot1q. If the current encap-type is set to null, the command cannot be executed when SAPs exist within the egress-multicast-group.
dot1q — For an egress-multicast-group.
null — If member SAPs are on a null encapsulated access port.
The null keyword is mutually exclusive with the
dot1q keyword. When the encap-type within the sap-common-requirements is specified to be null, the encapsulation type for the access ports associated with all SAPs within the egress-multicast-group must be set to null.
The dot1q keyword is mutually exclusive with the
null keyword. When the encap-type within the sap-common-requirements is specified to be dot1q, the encapsulation type for the access ports associated with all SAPs within the egress-multicast-group must be set to dot1q.
This command specifies the dot1q EtherType that must exist on the SAP’s access port to allow the SAP membership within the egress-multicast-group. The config>port>ethernet>access>
dot1q-etype command is used to define the EtherType used when encapsulating a packet with a dot1q tag on the Ethernet port. Any valid EtherType is allowed on the port.
The no form of the command returns the egress-multicast-group dot1q EtherType to the default value of 0x8100. If the current encap-type is set to a value other then 0x8100, the command cannot be executed when SAPs exist within the egress-multicast-group.
The no form of this command sets the max-ve-id to un-configured. The BGP VPLS status should be administratively down for “no max-ve-id” to be used.
The no form of the command removes the configured ve-name from the bgp vpls node. It can be used only when the BGP VPLS status is shutdown. Command “no shutdown” cannot be used if there is no ve-name configured.
The no form of the command removes the configured ve-id. It can be used just when the BGP VPLS status is shutdown. Command “no shutdown” cannot be used if there is no ve-id configured.
The no form of the command enables the BGP VPLS addressing and the related BGP advertisement. The associated BGP VPLS MP-REACH-NLRI will be advertised in an update message and the corresponding received NLRIs must be considered to instantiate the data plane. RT, RD usage: same like in the BGP AD solution, if the values are not configured here, the value of the VPLS-id from under the bgp-ad node is used. If VPLS-id value is not configured either the MH site cannot be activated – i.e. no shutdown returns an error. Same applies if a pseudowire template is not specified under the bgp node.
pw-template-binding policy-id [split-horizon-group
group-name] [import-rt
{ext-community, ...(up to 5 max)}]
The no form of the command removes the values from the configuration.
|
Values
|
target:{ip-addr:comm-val| 2byte-asnumber:ext-comm-val| 4byte-asnumber:comm-val} ip-addr a.b.c.d comm-val 0 — 65535 2byte-asnumber 0 — 65535 ext-comm-val 0 — 4294967295 4byte-asnumber 0 — 4294967295
|
The no form of this command removes BFD from the associated IGP/BGP protocol adjacency.
This command associates the context to which it is configured to the operational group specified in the group-name. The
oper-group group-name must be already configured under
config>service context before its name is referenced in this command.
The no form of the command removes the association.
route-target {ext-community|{[export
ext-community][import
ext-community]}}
vsi-export policy-name [policy-name...(up to 5 max)]
Alternatively, the auto-rd option allows the system to automatically generate an RD based on the
bgp-auto-rd-range command configured at service level.
vsi-import policy-name [policy-name...(up to 5 max)]
If no retry is configured, this implies that, once mac-duplication is detected, mac updates for that mac will be held down till the user intervenes or a network event (that flushes the mac) occurs.
