vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
no vpls service-id
config>service
Supported on all 7210 SAS platforms as described in this document
This command creates or edits a 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 as 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 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 another service of any type. The service-idmust 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 is optional for service editing or deleting.
Specifies a management VPLS.
Specifies to associate this VPLS instance with an IP interface to provide RVPLS functionality.
Specifies to allow the users to reserve resources for xSTP, L2PT, and BPDU services. Only if the service is created with this parameter, can the user later turn on the xSTP, L2PT, and BPDU features in the service. If not, all attempts to use these features fails.
Mandatory keyword while creating a VPLS service. The create keyword requirement can be enabled or disabled using the environment>create context.
Specifies the VPN ID number, which allows you to identify virtual private networks (VPNs).
Defines the dot1q VLAN ID to be specified while creating the local dot1q SAP for the svc-sap-type dot1q-preserve command.
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
Commands in this context configure the BGP-related parameters 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
This command enables blocking (brings the entity to an operationally down state) after all configured mesh-SDPs are in operationally down state. This event is signaled to corresponding T-LDP peers by withdrawing the service label (status-bit-signaling non-capable peer) or by setting the ‟PW not forwarding” status bit in the T-LDP message (status-bit-signaling capable peer).
disabled
bpdu-translation {auto | pvst | stp}
no bpdu-translation
config>service>vpls>spoke-sdp
config>service>vpls>sap
Supported on all 7210 SAS platforms as described in this document
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 value.
no bpdu-translation
Keyword to specify the format is detected automatically, based on the type of BPDUs received on the port.
Keyword to specify the BPDU format as PVST. The correct VLAN tag is included in the payload, depending on the encapsulation value of the outgoing SAP.
Keyword to specify the BPDU format as STP.
l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
no l2pt-termination
config>service>vpls>sap config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specific SAP. L2PT termination is supported for CDP, DTP, PAGP, STP, UDLD and VTP PDUs.
This feature can be enabled only if STP is disabled in the context of the specific VPLS service.
no l2pt-termination
Keyword to specify the Cisco discovery protocol.
Keyword to specify the dynamic trunking protocol.
Keyword to specify the port aggregation protocol.
Keyword to specify all spanning tree protocols: stp, rstp, mstp, pvst (default).
Keyword to specify unidirectional link detection.
Keyword to specify the VLAN trunking protocol.
[no] disable-aging
config>service>vpls
config>service>vpls>sap
config>template>vpls-template config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
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 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 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
Supported on all 7210 SAS platforms as described in this document
This command disables learning of new MAC addresses in the VPLS FDB for the service instance.
When disable-learning is enabled, new source MAC addresses are not entered in the VPLS service forwarding database.
When disable-learning is disabled, new source MAC addresses are learned or entered into the VPLS forwarding database.
This command is mainly used in conjunction with the disable-learning command.
The no form of this command enables learning of MAC addresses.
no disable-learning
[no] discard-unknown
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
By default, packets with unknown destination MAC addresses are flooded. If this command is enabled at the VPLS level, packets with unknown destination MAC address are dropped instead (even when the 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
no vpls-sap-bidir
vpls-sap-bidir
config>service>vpls>eth-cfm
7210 SAS-R6 and 7210 SAS-R12 IMMv2
This command links the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary VLAN functions. This must be configured as part of the creation step and can be changed only by deleting the MEP and recreating it.
This command is used to enable both the ingress and egress MIP functionality for a VPLS SAP.
Before enabling both Ingress and egress MIP functionality, the user must allocate sufficient resources in the egress-internal-tcam resource pool using the configure system resource-profile egress-internal-tcam eth-cfm bidir-mip-egress command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.
The following describes the behavior for this command:
MIP creation (without PVLAN enabled) is enabled under SAP with vpls-sap-bidir enabled and with either default or explicit mode configured for mhf-creation
In this case, both ingress MIP and egress MIP are created; a MIP (ingress and egress) is created at the level greater than the highest level MEP configured for the VPLS SAP.
MIP creation (without PVLAN enabled) is enabled under SAP with vpls-sap-bidir disabled and with either default or explicit mode configured for mhf-creation
In this case, only an ingress MIP is created; a MIP (ingress only) is created at the level greater than the highest level MEP configured for the VPLS SAP.
MIP creation (without PVLAN enabled) is enabled under SDP-Binding (that is, spoke-SDP/mesh-SDP) with vpls-sap-bidir enabled or disabled and with either default or explicit mode configured for mhf-creation
In this case, only ingress MIP is created; a MIP (ingress only) is created at the level greater than the highest level MEP configured for the VPLS SDB binding.
MIP creation (with PVLAN enabled) is enabled under SAP with vpls-sap-bidir enabled or disabled and with either default or explicit mode configured for mhf-creation
In this case, both ingress MIP and egress MIP are created; a MIP (ingress and egress) is created at the level greater than the highest level MEP configured for the VPLS SAP.
vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs (without PVLAN enabled) for any SAPs configured in the service
In this case, those MIPS are automatically converted to ingress and egress MIPs, assuming sufficient resources are allocated in the egress-internal-tcam resource pool for this feature. If sufficient resources are not available, attempting to enable the vpls-sap-bidir command fails.
vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs (without PVLAN enabled) for any SDP bindings configured in the service
In this case, those MIPS continue to function as ingress MIPs. That is, the vpls-sap-bidir has no effect on MIPs configured on SDP bindings.
vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs with PVLAN enabled for any SAP configured in the service
In this case, those MIPS continue to function as both ingress MIP and egress MIP. That is, the vpls-sap-bidir setting has no effect on MIPs with primary VLAN enabled and configured on SAPs.
no vpls-sap-bidir
endpoint endpoint-name [create]
no endpoint
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command configures a service endpoint.
Specifies an endpoint name up to 32 characters.
Mandatory keyword for creating a service endpoint.
description description-string
no description
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document
This command creates a text description stored in the configuration file for a configuration context.
The no form of this command removes the string from the configuration.
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, and so on), 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
When this command is enabled, the node ignores 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 the endpoint level and at the 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 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
This command configures the time to wait before reverting to primary spoke-SDP.
In a regular endpoint, the revert-time setting affects only 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 case where 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.
Keyword that makes the endpoint non-revertive.
split-horizon-group group-name [create]
config>service>vpls config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command creates a new split horizon group (SHG) for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this SHG are not copied to other SAPs or spoke SDPs in the same SHG.
An 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 instance. The same group name can be reused in different VPLS instances.
On the 7210 SAS-R6 with IMM (v1 cards) and IMM-c cards, service-based SHGs and mesh-SDPs are mutually exclusive in a VPLS service.
On the 7210 SAS-R6 and 7210 SAS-R12 with IMM-b cards, 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 split horizon group to which the SAP or spoke-SDP belongs.
Mandatory keyword to create a split-horizon group.
static-mac ieee-address [create]
no static-mac
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document
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. This value cannot be all zeros.
Mandatory keyword for creating a static MAC.
[no] suppress-standby-signaling
config>service>vpls>endpoint
Supported on all 7210 SAS platforms as described in this document
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] fdb-table-high-wmark high-water-mark
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
This command specifies the upper threshold value for FDB entries. The high-water-mark is configured as a percentage of the FDB. When the number of FDB entries exceeds the high-water-mark, the system raises a log event.
Specifies the upper threshold for FDB entries, which when exceeded, causes the system to raise a log event.
[no] fdb-table-low-wmark low-water-mark
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
This command specifies the lower threshold value for FDB entries. The low-water-mark is configured as a percentage of the FDB. When the number of FDB entries drops below the low-water-mark, the system raises a log event.
Specifies the lower threshold for FDB entries, which when dropped below, causes the system to raise a log event.
fdb-table-size table-size
no fdb-table-size [table-size]
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
This command specifies the maximum number of MAC entries in the FDB for the VPLS instance on this node.
The fdb-table-size specifies the maximum number of FDB entries for both learned and static MAC addresses for the VPLS instance.
The no form of this command reverts to the default value.
fdb-table-size 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
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
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
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 extended community can have the same formats as the VPLS ID: a two-octet AS-specific extended community, or an IPv4-specific extended community.
The following rules apply.
If BGP AD VPLS-id is configured and no RT is configured under the BGP node: RT = VPLS-ID.
If BGP AD VPLS-id is not configured, an RT value must be configured under the 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 the 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-bind policy-id
config>service>vpls>bgp-ad
config>service>vpls>bgp
Supported on all 7210 SAS platforms as described in this document
This command binds the advertisements received with the RT that match 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 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; x and y are 16-bit integers.
route-distinguisher [rd]
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
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 and no RD is configured under BGP node: RD = VPLS-ID.
If BGP AD VPLS-id is not configured, 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
The values and format consist of 6 bytes, where the other 2 bytes of type is automatically generated.
Specifies the RD component in one of the following forms:
ip-addr:comm-val
2byte-asnumber:ext-comm-val
4byte-asnumber:comm-val
local-age aging-timer
no local-age
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
This command specifies the aging time for locally learned MAC addresses in the FDB for the 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 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). 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
Specifies the aging time for local MACs, in seconds.
[no] mac-move
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
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 command is an alternative way to protect your network against loops.
When enabled in a VPLS, the mac-move command 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. A SAP can be marked as non-blockable using 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; 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) the mac-move command disables one of the VPLS ports when 5 relearns were detected during the 5-second interval, because the average move-frequency of 1 relearn per second has been reached. This can occur in the first second if the real relearn rate is 5 relearns per second or higher.
The no form of this command disables the mac-move command.
move-frequency frequency
no move-frequency
config>service>vpls>mac-move
config>template>vpls-template>mac-move
Supported on all 7210 SAS platforms as described in this document
This command indicates 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.
move-frequency 2
Specifies the rate, in 5-second intervals, for the maximum number of relearns.
retry-timeout timeout
no retry-timeout
config>service>vpls>mac-move
config>template>vpls-template>mac-move
Supported on all 7210 SAS platforms as described in this document
This command configures the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.
Nokia recommends that the retry-timeout value be 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.
retry-timeout 10
Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.
[no] mfib-table-high-wmark high-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command specifies the multicast FIB (MFIB) high watermark. When the percentage filling level of the MFIB exceeds the configured value, a trap is generated and a log entry is added.
Specifies the MFIB 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
This command specifies the MFIB low watermark. When the percentage filling level of the MFIB drops below the configured value, the corresponding trap is cleared and a log entry is added.
Specifies the multicast FIB low watermark as a percentage.
mfib-table-size table-size
no mfib-table-size
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command specifies the maximum number of (s,g) entries in the MFIB database for this VPLS instance.
The 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 that is lower than the current number of dynamic entries present in the MFIB, 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 MFIB.
remote-age seconds
no remote-age
config>service>vpls
config>template>vpls-template
Supported on all 7210 SAS platforms as described in this document
This command specifies the aging time for remotely learned MAC addresses in the FDB for the VPLS instance. In a VPLS service, MAC addresses are associated with a SAP or an SDP. MACs associated with a SAP are called local MACs, and MACs associated with an SDP are called 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 with a value 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, in seconds.
[no] send-flush-on-failure
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command enables sending out ‟flush-all-from-ME” messages to all LDP peers included in the affected VPLS, in the event of physical port failures or ‟oper-down” events of individual SAPs.
This command 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 the send-flush-on-failure command is enabled, flush-all-from-me messages are 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
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 command defines the payload capabilities of the service and 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 (that is, 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, 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.
When a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, all associated SAP and SDP binding operational states are automatically reevaluated.
The no form of this command reverts the service-mtu value for the indicated service type to the default.
To disable service MTU check, run the no service-mtu-check command. Disabling service MTU check allows the packets to pass to the egress if the packet length is less than or equal to the MTU configured on the port.
service-mtu 1514
Specifies the size of the MTU in octets, expressed as a decimal integer. 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 |
[no] service-mtu-check
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command, when disabled, allows the packets to pass to the egress if the packet length is less 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).
The no form of this command disables the service MTU check.
enabled
[no] root-guard
config>service>vpls>sap>stp
Supported on all 7210 SAS platforms as described in this document
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 the 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.
vsi-id
config>service>vpls>bgp-ad
Supported on all 7210 SAS platforms as described in this document
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
This command specifies the low-order 4 bytes used to compose the VSI-ID to use for NLRI in BGP auto-discovery in the specified VPLS service.
If no value is set, the system IP address is used.
no prefix
Specifies a unique VSI-ID.