vpls service-id [customer customer-id] [create] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
vpls service-id [customer customer-id] [create] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve}]
vpls service-id [customer customer-id] [create] [m-vpls] [svc-sap-type {any | dot1q-range}] [r-vpls]
vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | 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 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 together 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 must be specified and must 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 is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer-id 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.
7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T support local service.
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C support both local and distributed service.
The no form of this command deletes the VPLS service instance with the specified service-id. The service cannot be deleted until all SAPs defined within the service ID have been shutdown and deleted, and the service has been shut down.
Specifies the unique service 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.
This keyword is mandatory while creating a VPLS service. Keyword used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
Specifies the dot1q VLAN ID for creating the local dot1q SAP for svc-sap-type dot1q-preserve.
Keyword to specify the type of access SAPs and access-uplink SAPs allowed in the service.
Allows this VPLS instance to be associated with an IP interface to provide R-VPLS functionality. This parameter is supported only on the 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
bgp
config>service>vpls
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables blocking after all configured SDPs or endpoints are in operationally down state.
Blocking brings the entity to an operationally down state. This event is signaled to corresponding T-LDP peer by withdrawing the 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 (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C) config>service>vpls>sap
Supported on all 7210 SAS platforms as described in this document
This command enables the translation of bridge protocol data units (BPDUs) to a specific format, meaning that all BPDUs transmitted on a specific SAP or spoke-SDP will have a specified format.
The no form of this command reverts to the default value.
no bpdu-translation
Keyword to specify that the appropriate format will be detected automatically, based on type of BPDUs received on such port.
Keyword to specify the BPDU format as PVST. The correct VLAN tag is included in the payload (depending on encapsulation value of 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 (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specific SAP. L2PT termination is supported for STP, CDP, DTP, PAGP, UDLD, and VTP PDUs.
This command can be enabled only if STP is disabled in the context of the specific VPLS service.
no l2pt-termination
Keyword that specifies the Cisco discovery protocol.
Keyword that specifies the dynamic trunking protocol.
Keyword that specifies the port aggregation protocol.
Keyword that specifies all spanning tree protocols: stp, rstp, mstp, pvst (default).
Keyword that specifies unidirectional link detection.
Keyword that specifies the VLAN trunking protocol.
[no] disable-aging
config>service>vpls
config>service>vpls>spoke-sdp (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
config>service>vpls>sap
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.
Similar to 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 a VPLS service instance, the local age timer is applicable to both the local learned and remote learned MAC entries in the VPLS forwarding database (FDB). The disable-aging command at the service level 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>vpls>sap
config>service>vpls>spoke-sdp (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
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 be entered in the VPLS service forwarding database.
When disable-learning is disabled, new source MAC addresses are learned and entered into the VPLS forwarding database.
This command is mainly used in conjunction with the discard-unknown 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
This command enables, at the VPLS level, packets with unknown destination MAC address to be dropped instead of flooded (even when configured FIB size limits for VPLS or SAP are not yet reached). By default, packets with unknown destination MAC addresses are flooded.
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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures a service endpoint.
Specifies an endpoint name, up to 32 characters.
Keyword that is mandatory while creating a service endpoint.
description description-string
no description
config>service>vpls>endpoint
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command creates a text description stored in the configuration file for a configuration context.
This 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.
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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 available at the endpoint level and 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 will become 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
split-horizon-group group-name [create]
config>service>vpls
config>service>pw-template (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command creates a 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.
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.
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] fdb-table-high-wmark high-water-mark
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
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
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
This command specifies the maximum number of MAC entries in the FDB for the VPLS instance on this node.
This command 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 the table size to the default value.
250
Specifies the maximum number of MAC entries in the FDB.
[no] bgp-ad
config>service>vpls
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures BGP auto-discovery.
vpls-id vpls-id
config>service>vpls>bgp-ad
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the VPLS ID component that will be signaled in one of the extended community attributes (ext-comm). Values and format (6 bytes, other 2 bytes of type-subtype will be automatically generated).
Specifies a globally unique VPLS ID for BGP auto-discovery in this VPLS service.
vsi-export policy-name [policy-name...(up to 5 max)]
no vsi-export
config>service>vpls>bgp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command specifies the name of the VSI export policies to be used for BGP auto-discovery, when this command 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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command specifies the name of the VSI import policies used for BGP auto-discovery, when this command 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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the route target (RT) component that is signaled in the related MPBGP attribute to be used for BGP auto-discovery, when this command 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 the BGP AD VPLS ID is configured and no RT is configured under BGP node, RT = VPLS-ID.
If the 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 the BGP AD VPLS ID is configured and an RT value is also configured under BGP node, the configured RT value prevails.
Specifies the communities allowed to be sent to remote PE neighbors.
Specifies the 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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command binds the advertisements received with the 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.
This command 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 a group name that overrides the split horizon group template settings.
Specifies communities allowed to be accepted from remote PE neighbors. An extended BGP community is expressed 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.
local-age [aging-timer]
no local-age
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command configures 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 SAP. MACs associated with a SAP are classified as local MACs, and MACs associated with are remote MACs QinQ / access uplink SAPs.
Similar to 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 the local aging timer to the default value.
local age 300
Specifies the aging time for local MACs, in seconds.
[no] mac-move
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure 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, 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 using the config>service>vpls>sap> context. This means that when the relearn 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, because 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 will be 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 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
This command configures 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)
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
This command configures the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is reenabled.
It is recommended that the retry-timeout value be larger than 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 value of zero indicates that the SAP will not be automatically reenabled after being disabled. If, after the SAP is reenabled 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
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 MFIB 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
This command specifies the maximum number of (s,g) entries in the MFIB for this VPLS instance.
The 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 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
Supported on all 7210 SAS platforms as described in this document
This command configures 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. MACs associated with a SAP are classified as local MACs.
Similar to 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 value larger than the local-age timer.
The no form of this command reverts the remote aging timer to the default value.
remote age 900
Specifies the aging time for remote MACs, in seconds.
[no] send-flush-on-failure
config>service>vpls
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 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 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
7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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. 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 (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.
In the event that 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 default service-mtu for the indicated service type to the default value.
To disable the service MTU check, execute 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.
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] root-guard
config>service>vpls>sap>stp
config>service>vpls>spoke-sdp>stp (only supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C)
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 a 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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command specifies the low-order 4 bytes used to compose the 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
This command configures an optional service name, up to 64 characters, that adds a name identifier to a specific service to then use that service name in configuration references and in show commands throughout the system. This helps service providers and administrators identify and manage services.
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 to 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] allow-ip-int-bind
config>service>vpls
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
This command sets a flag on the VPLS service that enables the ability to attach an IP interface to the VPLS service to make the VPLS service routable. When the allow-ip-int-bind command is not enabled, the VPLS service cannot be attached to an IP interface.
On the 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T, the VPLS can be bound to only an IES IP interface. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the VPLS can be bound to an IES or VPRN IP interface. Only IPv4 addressing and forwarding is supported in the R-VPLS context.
When attempting to set the allow-ip-int-bind VPLS flag, the system first checks to see if the correct configuration constraints exist for the VPLS service and the network ports. In Release 5.0 the following VPLS features must be disabled or not configured to set the allow-ip-int-bind flag:
SAP ingress QoS policies applied to the VPLS SAPs cannot have MAC match criteria defined
VPLS service type cannot be M-VPLS
MVR from routed VPLS and to another SAP is not supported
When the VPLS allow-ip-int-bind flag is set on a VPLS service, the preceding features cannot be enabled on the VPLS service.
When a service name is applied to a VPLS service and that service name is also bound to an IP interface but the allow-ip-int-bind flag has not been set on the VPLS service context, the system attempt to resolve the service name between the VPLS service and the IP interface fails.
After the allow-ip-int-bind flag is successfully set on the VPLS service, either the service name on the VPLS service must be removed and reapplied, or the IP interface must be reinitialized using the shutdown or no shutdown commands. This causes the system to reattempt the name resolution process between the IP interface and the VPLS service.
The no form of this command resets the allow-ip-int-bind flag on the VPLS service. If the VPLS service currently has an IP interface attached, the no allow-ip-int-bind command fails. When the allow-ip-int-bind flag is reset on the VPLS service, the configuration restrictions associated with setting the flag are removed.