vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
no vpls service-id
config>service
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
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.
A VPLS service connects multiple customer sites, acting like a zero-hop Layer 2 switched domain. A VPLS is always a logical full mesh.
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 parameter must be specified to associate the service with a customer. The customer-id value must already exist, having been created using the customer command in the service context. When 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.
When a service is created, the use of the customer customer-id command is optional for navigating into the service configuration context. Editing a service with the incorrect customer-id value specified results in an error.
More than one VPLS service may be created for a single customer ID.
By default, no VPLS instances exist until they are explicitly created.
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 shut down and deleted, and the service has been shut down.
Specifies the unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.
Specifies the customer ID number to be associated with the service. This parameter is required on service creation and optional for service editing or deleting.
Specifies a management VPLS.
Specifies a PBB backbone-VPLS service, which can only be configured with SAPs. This keyword is supported only on 7210 SAS-T operating in network mode.
Specifies a PBB I-VPLS service, which can only be configured with SAPs. This keyword is only supported when the svc-sap-type value any is configured. This keyword is supported only on 7210 SAS-T operating in network mode.
Mandatory keyword while creating a VPLS service. Create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Specifies the type of service and allowed SAPs in the service.
Specifies the VLAN ID to use when the svc-sap-type value is set to dot1q-preserve. This parameter is supported only when the b-vpls keyword and svc-sap-type value dot1q-preserve are configured.
Specifies the VPLS instance to be associated with an IP interface to provide routed VPLS (R-VPLS) functionality. When configured with the svc-sap-type values null-star, dot1q-preserve, and any, this keyword instantiates an R-VPLS service that can be configured only with SAPs.
The r-vpls keyword is not supported in access-uplink mode (that is, in access-uplink mode, a routed VPLS service can be configured without using this parameter).
vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
no vpls service-id
config>service
Supported only on platforms configured in the access-uplink operating mode
This command creates or maintains a virtual private LAN services (VPLS) instance. 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.
A VPLS service connects multiple customer sites, acting like a zero-hop, Layer 2 switched domain. A VPLS is always a logical full mesh.
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 parameter must be specified to associate the service with a customer. The customer-id value must already exist, having been created using the customer command in the service context. When 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.
When a service is created, the use of the customer customer-id command is optional for navigating into the service configuration context. Editing a service with the incorrect customer-id value specified results in an error.
More than one VPLS service may be created for a single customer ID.
By default, no VPLS instances exist until they are explicitly created.
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 shut down and deleted, and the service has been shut down.
Specifies the unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.
Specifies the customer ID number to be associated with the service. This parameter is required on service creation and optional for service editing or deleting.
Mandatory keyword when creating a VPLS service. This keyword is used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Defines the dot1q VLAN ID to be specified while creating the local dot1q SAP for the svc-sap-type value dot1q-preserve. This parameter is supported only on platforms operating in access-uplink mode.
Specifies the type of service and allowed SAPs in the service.
bgp
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure the parameters related to BGP.
bgp-ad
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure the parameters related to BGP AD.
[no] block-on-mesh-failure
config>service>vpls>spoke-sdp
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command enables blocking (brings the entity to an operationally down state) after all configured mesh-SDPs are in the operationally down state. This event is signaled to corresponding T-LDP peer by withdrawing service label (status-bit-signaling non-capable peer) or by setting ‟PW not forwarding” status bit in T-LDP message (status-bit-signaling capable peer).
disabled
bpdu-translation {auto | pvst | stp}
no bpdu-translation
config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)
config>service>vpls>sap
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command enables the translation of BPDUs to a specific format, meaning that all BPDUs transmitted on a specific SAP or spoke-SDP have a specified format.
The no form of this command reverts to the default setting.
no bpdu-translation
Specifies that appropriate format is detected automatically, based on type of bpdus received on such port.
Specifies the BPDU-format as PVST. Note that the correct VLAN tag is included in the payload (depending on encapsulation value of outgoing SAP).
Specifies the BPDU-format as STP.
l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp] [lldp]
no l2pt-termination
config>service>vpls>sap
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
The config>service>vpls>spoke-sdp context is not supported on 7210 SAS platforms configured in the access-uplink operating mode.
This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specific SAP or spoke-SDP. L2PT termination is supported for CDP, DTP, PAGP, STP, UDLD, VTP, and LLDP PDUs.
This feature can be enabled only if STP is disabled in the context of the specific VPLS service.
no l2pt-termination
Specifies the Cisco Discovery Protocol.
Specifies the Dynamic Trunking Protocol.
Specifies the Port Aggregation Protocol.
Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default) values.
Specifies Unidirectional Link Detection.
Specifies the VLAN Trunking Protocol.
Specifies Link Layer Discovery Protocol (LLDP). This keyword is supported only on the 7210 SAS-Mxp.
[no] disable-aging
config>service>vpls
config>service>vpls>spoke-sdp
config>service>vpls>sap
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
The config>service>vpls>spoke-sdp and config>service>pw-template contexts are not supported on platforms configured in the access-uplink operating mode.
This command disables MAC address aging across a VPLS service or on a VPLS service SAP.
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 specific 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 is ignored.
The no form of this command enables aging on the VPLS service.
no disable-aging
[no] disable-learning
config>service>vpls
config>service>pw-template
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
The config>service>pw-template context is not supported on platforms configured in the access-uplink operating mode.
This command disables learning of new MAC addresses in the VPLS forwarding database (FDB) for the service instance.
When disable-learning is enabled, new source MAC addresses is not entered in the VPLS service forwarding database.
When disable-learning is disabled, new source MAC addresses is learned and entered into the VPLS forwarding database.
This parameter is mainly used in conjunction with the discard-unknown command.
The no form of this command enables learning of MAC addresses.
no disable-learning (Normal MAC learning is enabled)
[no] discard-unknown
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
By default, packets with unknown destination MAC addresses are flooded. If discard-unknown is enabled at the VPLS level, packets with unknown destination MAC address is dropped instead (even when configured FIB size limits for VPLS or SAP are not yet reached).
The no form of this command allows flooding of packets with unknown destination MAC addresses in the VPLS.
no discard-unknown
endpoint endpoint-name [create]
no endpoint
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures a service endpoint.
Specifies an endpoint name up to 32 characters.
Mandatory keyword to create a service endpoint.
description description-string
no description
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command creates a text description stored in the configuration file for a configuration context.
The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
no description
Specifies the description character string. Allowed values are any string up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
[no] ignore-standby-signaling
config>service>vpls>endpoint
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command causes the node to ignore the standby-bit received from TLDP peers for the specific spoke-SDP and performs internal tasks without taking it into account.
This command is present at endpoint level as well as spoke-SDP level. If the spoke-SDP is part of the explicit-endpoint, it is not possible to change this setting at the spoke-SDP level. The existing spoke-SDP becomes part of the explicit-endpoint only if the setting is not conflicting. The newly created spoke-SDP which is a part of the specific explicit-endpoint inherits this setting from the endpoint configuration.
disabled
revert-time revert-time | infinite
no revert-time
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the time to wait before reverting to primary spoke-SDP.
In a regular endpoint the revert-time setting affects just the pseudowire defined as primary (precedence 0). For a failure of the primary pseudowire followed by restoration the revert-timer is started. After it expires the primary pseudowire takes the active role in the endpoint. This behavior does not apply for the case when both pseudowires are defined as secondary. For example, if the active secondary pseudowire fails and is restored it stays in standby until a configuration change or a force command occurs.
Specifies the time to wait, in seconds, before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP.
Specifies that the endpoint is non-revertive.
static-mac ieee-address [create]
no static-mac
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command assigns a static MAC address to the endpoint. In the FDB, the static MAC is then associated with the active spoke-SDP.
Specifies the static MAC address to the endpoint.
Mandatory keyword while creating a static MAC.
[no] suppress-standby-signaling
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
When this command is enabled, the pseudowire standby bit (with value 0x00000020) is not sent to T-LDP peer when the specific spoke is selected as a standby. This allows faster switchover as the traffic is sent over this SDP and discarded at the blocking side of the connection. This is particularly applicable to multicast traffic.
enabled
[no] propagate-mac-flush
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies whether MAC flush messages received from the specific LDP are propagated to all spoke and mesh SDPs within the context of this VPLS service. The propagation follows the split-horizon principle and any datapath blocking to avoid the looping of these messages.
no propagate-mac-flush
[no] fdb-table-high-wmark high-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the value to send logs and traps when the threshold is reached.
Specifies the value to send logs and traps when the threshold is reached.
[no] fdb-table-low-wmark low-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the value to send logs and traps when the threshold is reached.
Specifies the value to send logs and traps when the threshold is reached.
fdb-table-size table-size
no fdb-table-size [table-size]
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the maximum number of MAC entries in the Forwarding Database (FDB) for the VPLS instance on this node.
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 reverts to the default value.
250
Specifies the maximum number of MAC entries in the FDB.
vsi-export policy-name [policy-name...(up to 5 max)]
no vsi-export
config>service>vpls>bgp-ad
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies the name of the VSI export policies to be used for BGP auto-discovery, if this feature is configured in the VPLS service. If multiple policy names are configured, the policies are evaluated in the order they are specified. The first policy that matches is applied.
The policy name list is handled by the SNMP agent as a single entity.
vsi-import policy-name [policy-name...(up to 5 max)]
no vsi-import
config>service>vpls>bgp-ad>vsi-id
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies the name of the VSI import policies to be used for BGP auto-discovery, if this feature is configured in the VPLS service. If multiple policy names are configured, the policies are evaluated in the order they are specified. The first policy that matches is applied.
The policy name list is handled by the SNMP agent as a single entity.
route-target {ext-community | {[export ext-community] | [import ext-community]}}
no route-target
config>service>vpls>bgp-ad
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the route target (RT) component that is signaled in the related MPBGP attribute to be used for BGP auto-discovery, if this feature is configured in the VPLS service.
If this command is not used, the RT is built automatically using the VPLS ID. The ext-comm can have the same two formats as the VPLS ID, a two-octet AS-specific extended community, IPv4 specific extended community.
The following rules apply:
If BGP AD VPLS-id is configured and no RT is configured under BGP node - RT = VPLS-ID.
If BGP AD VPLS-id is not configured, an RT value must be configured under BGP node.
(this is the case when only BGP VPLS is configured)
If BGP AD VPLS-id is configured and an RT value is also configured under BGP node, the configured RT value prevails
Specifies communities allowed to be sent to remote PE neighbors.
Specifies communities allowed to be accepted from remote PE neighbors.
pw-template-binding policy-id [split-horizon-group group-name] [import-rt {ext-community,...(up to 5 max)}]
no pw-template-binding policy-id
config>service>vpls>bgp-ad
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command binds the advertisements received with the route target (RT) that matches the configured list (either the generic or the specified import) to a specific pw-template. If the RT list is not present the pw-template is used for all of them.
The pw-template-binding applies to BGP-AD, if this feature is configured in the VPLS service.
The tools perform commands can be used to control the application of changes in pw-template for BGP-AD.
The no form of this command removes the values from the configuration.
Specifies an existing policy ID.
Specifies the group-name that overrides the split horizon group template settings.
Specifies the communities allowed to be accepted from remote PE neighbors. An extended BGP community in the type:x:y format. The value x can be an integer or IP address.
The type can be the target or origin, and x and y are 16-bit integers.
route-distinguisher [ip-addr:comm-val | as-number:ext-comm-val]
no route-distinguisher
config>service>vpls>bgp-ad>vsi-id
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the Route Distinguisher (RD) component that is signaled in the MPBGP NLRI for L2VPN AFI. This value is used for BGP-AD, if this feature is configured in the VPLS service.
If this command is not configured, the RD is automatically built using the BGP-AD VPLS ID. The following rules apply:
If BGP AD VPLS-id is configured & no RD is configured under BGP node - RD = VPLS-ID.
If BGP AD VPLS-id is not configured then an RD value must be configured under BGP node (this is the case when only BGP VPLS is configured).
If BGP AD VPLS-id is configured and an RD value is also configured under BGP node, the configured RD value prevails Values and format (6 bytes, other 2 bytes of type is automatically generated)
Specifies the IP address.
local-age aging-timer
no local-age
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures the aging time for locally learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance. In a VPLS service, MAC addresses are associated with a Service Access Point (SAP). MACs associated with a SAP are classified as local MACs, and MACs associated with are remote MACsQinQ / access-uplink SAPs.
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). The local-age timer specifies the aging time for local learned MAC addresses.
The no form of this command reverts to the default value.
local age 300 — Local MACs aged after 300 seconds.
Specifies the aging time for local MACs expressed in seconds.
[no] mac-move
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures MAC move attributes. A sustained high relearn rate can be a sign of a loop somewhere in the VPLS topology. Typically, STP detects loops in the topology, but for those networks that do not run STP, the mac-move feature is an alternative way to protect your network against loops.
When enabled in a VPLS, mac-move monitors the relearn 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 specific SAP was disabled. You have the option of marking a SAP as non-blockable in the config>service>vpls>sap>limit-mac-move context. This means that when the relearn rate has exceeded the limit, another (blockable) SAP is disabled instead.
The mac-move command enables the feature at the service level for SAPs, as only those objects can be blocked by this feature.
The operation of this feature is the same on the SAP. For example, if a MAC address moves from SAP to SAP, one is blocked to prevent thrashing.
The mac-move command disables 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 disables 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.
move-frequency frequency
no move-frequency
config>service>vpls>mac-move
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the maximum rate at which MACs can be relearned in the VPLS service, before the SAP where the moving MAC was last seen is automatically disabled to protect the system against undetected loops or duplicate MACs.
The no form of this command reverts to the default value.
2 (when mac-move is enabled). For example, 10 relearns in a 5 second period.
Specifies the rate, in 5-second intervals for the maximum number of relearns.
retry-timeout timeout
no retry-timeout
config>service>vpls>mac-move
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.
It is recommended that the retry-timeout value is larger or equal to 5s * cumulative factor of the highest priority port so that the sequential order of port blocking is not disturbed by reinitializing lower priority ports.
A zero value indicates that the SAP is not automatically re-enabled after being disabled. If, after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.
The no form of this command reverts to the default value.
10 (when mac-move is enabled)
Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is reenabled.
[no] mfib-table-high-wmark high-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the multicast FIB high watermark. When the percentage filling level of the multicast FIB exceeds the configured value, a trap is generated and/or a log entry is added.
Specifies the multicast FIB high watermark as a percentage.
[no] mfib-table-low-wmark low-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the multicast FIB low watermark. When the percentage filling level of the Multicast FIB drops below the configured value, the corresponding trap is cleared and/or a log entry is added.
Specifies the multicast FIB low watermark as a percentage.
mfib-table-size size
no mfib-table-size
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the maximum number of (s,g) entries in the multicast forwarding database (MFIB) for this VPLS instance.
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 maximum MFIB table size.
Specifies the maximum number of (s,g) entries allowed in the Multicast FIB.
remote-age seconds
no remote-age
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies the aging time for remotely learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance. In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.
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 FDB. The remote-age timer specifies the aging time for remote learned MAC addresses. To reduce the amount of signaling required between switches configure this timer larger than the local-age timer.
The no form of this command reverts to the default value.
remote age 900
Specifies the aging time for remote MACs expressed in seconds.
[no] send-flush-on-failure
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command enables sending out ‟flush-all-from-ME” messages to all LDP peers included in affected VPLS, in the event of physical port failures or ‟oper-down” events of individual SAPs. This feature provides an LDP-based mechanism for recovering a physical link failure in a dual-homed connection to a VPLS service. This method provides an alternative to RSTP solutions where dual homing redundancy and recovery, in the case of link failure, is resolved by RSTP running between a PE router and CE devices. If the endpoint is configured within the VPLS and send-flush-on-failure is enabled, flush-all-from-me messages is sent out only when all spoke-SDPs associated with the endpoint go down.
This feature cannot be enabled on management VPLS.
no send-flush-on-failure
service-mtu octets
no service-mtu
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the service payload (Maximum Transmission Unit – MTU), in bytes, for the service. This MTU value overrides the service-type default MTU. The service-mtu defines the payload capabilities of the service. It is used by the system to validate the SAP and SDP binding operational state within the service.
The service MTU and a SAP service delineation encapsulation overhead (i.e., 4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, then the SAP is placed in an inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP is able to transition to the operative state.
In the event that a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, then all associated SAP and SDP binding operational states are automatically reevaluated.
The no form of this command reverts to the default value.
To disable service MTU check execute the command no service-mtu-check. Disabling service MTU check allows the packets to pass to the egress if the packet length is lesser than or equal to the MTU configured on the port.
VPLS: 1514
The following table displays MTU values for specific VC types.
VC-type |
Example service MTU |
Advertised MTU |
|---|---|---|
Ethernet |
1514 |
1500 |
Ethernet (with preserved dot1q) |
1518 |
1504 |
VPLS |
1514 |
1500 |
VPLS (with preserved dot1q) |
1518 |
1504 |
VLAN (dot1p transparent to MTU value) |
1514 |
1500 |
VLAN (QinQ with preserved bottom Qtag) |
1518 |
1504 |
Specifies the size of the MTU in octets, expressed as a decimal integer.
[no] service-mtu-check
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Disabling service MTU check allows the packets to pass to the egress if the packet length is lesser than or equal to the MTU configured on the port. The length of the packet sent from a SAP is limited only by the access port MTU. In case of a pseudowire the length of a packet is limited by the network port MTU (including the MPLS encapsulation).
If TLDP is used for signaling, the configured value for service-mtu is used during pseudowire setup.
The no form of this command disables the service MTU check.
enabled
service-name service-name
no service-name
config>service>epipe
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used o identify and reference a specific service when it is initially created.
Specifies a unique service name to identify the service. Service names may not begin with an integer (0-9).
[no] split-horizon-group [group-name] [create]
config>service>vpls
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command creates a new split-horizon group (SHG) for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this SHG is not copied to other SAPs or spoke-SDPs in the same SHG.
The SHG must be created before SAPs and spoke-SDPs can be assigned to the group.
The SHG is defined within the context of a single VPLS. The same group name can be reused in different VPLS instances.
The split-horizon-group command is only supported on 7210 SAS platforms operating in the network mode.
Service-based SHGs are only supported on the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE operating in the network mode. On these platforms, service-based SHGs and mesh-SDPs are mutually exclusive in a VPLS service.
On the 7210 SAS-Mxp, an SHG can be used with spoke-SDPs or mesh SDPs configured in the service.
Service-based SHGs are not supported in an R-VPLS service.
The no form of this command removes the group name from the configuration.
Specifies the name of the SHG to which the SAP or spoke-SDP belongs.
Mandatory keyword to create an SHG.
[no] root-guard
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp (not supported in access-uplink operating mode)
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.
no root-guard
tod-suite tod-suite-name
no tod-suite
config>service>vpls>sap
Supported on all 7210 SAS platforms as described in this document
This command applies a time-based policy (filter or QoS policy) to the service SAP. The suite name must already exist in the config>cron context.
no tod-suite
Specifies collection of policies (ACLs, QoS) including time-ranges that define the full or partial behavior of a SAP. The suite can be applied to more than one SAP.
vpls-id vpls-id
config>service>vpls>bgp-ad
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the VPLS ID component that is signaled in one of the extended community attributes (ext-comm).
Values and format (6 bytes, other 2 bytes of type-subtype are automatically generated).
Specifies a globally unique VPLS ID for BGP auto-discovery in this VPLS service.
vsi-id
config>service>vpls>bgp-ad
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure the Virtual Switch Instance Identifier (VSI-ID).
prefix low-order-vsi-id
no prefix
config>service>vpls>bgp-ad>vsi-id
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies the low-order 4 bytes used to compose the Virtual Switch Instance Identifier
(VSI-ID) to use for NLRI in BGP auto-discovery in this VPLS service.
If no value is set, the system IP address is used.
no prefix
Specifies a unique VSI-ID.
service-name service-name
no service-name
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used o identify and reference a specific service when it is initially created.
Specifies a unique service name to identify the service. Service names may not begin with an integer (0 to 9).