mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}]
no mesh-sdp sdp-id[:vc-id]
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command binds a VPLS service to an existing Service Distribution Point (SDP). Mesh SDPs bound to a service are logically treated like a single bridge ‟port” for flooded traffic where flooded traffic received on any mesh SDP on the service is replicated to other ‟ports” (spoke-SDPs and SAPs) and not transmitted on any mesh SDPs.
This command creates a binding between a service and an SDP. The SDP has an operational state, which determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already be defined in the config>service>sdp context to associate the SDP with a valid service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. When the SDP binding is removed, no packets are forwarded to the far-end router.
no sdp-id is bound to a service
Specifies that several SDPs can be bound to a VPLS. Each SDP must be destined to a different router. If two sdp-id bindings terminate on the same router, an error occurs and the second SDP binding is rejected.
Specifies the SDP identifier.
Specifies the virtual circuit identifier. This value is used to validate the VC ID portion of each mesh SDP binding defined in the service. The default value of this object is equal to the service ID.
Overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value that represents the type of VC. The signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the binding VC type causes the binding to signal the new VC type to the far end when signaling is enabled.
VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
Defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding.
Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for mesh SDP bindings.
spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] [split-horizon-group group-name] [use-evpn-default-shg]
no spoke-sdp sdp-id[:vc-id]
config>service>vpls
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command binds a service to an existing Service Distribution Point (SDP). A spoke-SDP is treated like the equivalent of a traditional bridge ‟port” on which flooded traffic received on the spoke-SDP is replicated on all other ‟ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port on which it was received.
The operational state of the SDP determines the SDP state within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
SDPs must be explicitly associated and bound to a service to allow far-end devices to participate in the service. The SDP must already exist in the config>service>sdp context before it can be associated with a VPLS service. If the sdp-id is not already configured, an error message is generated. If the sdp-id exists, a binding between the specific sdp-id and service is created.
The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the SDP binding is removed, no packets are forwarded to the far-end router.
Several SDPs can be bound to a VPLS service. Each SDP must use a unique vc-id. An error message is generated if two SDP bindings with an identical vc-id terminate on the same router. Split-horizon groups can only be created in the scope of a VPLS service.
Specifies the SDP identifier.
Specifies the virtual circuit identifier.
Mandatory keyword to create a spoke-SDP.
Keyword to define the VC type as Ethernet. The ether and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding (hex 5).
Keyword to define the VC type as VLAN. The ether and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings.
The VLAN VC type requires at least one dot1q tag within each encapsulated Ethernet packet transmitted to the far end.
Specifies the name of the split horizon group to which the SDP belongs.
Keyword to override the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value that represents the VC type. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. If signaling is enabled, a change of the bindings VC type causes the binding to signal the new VC type to the far end.
VC types are derived in accordance with IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
Keyword to add the spoke SDP to the default SHG, which causes the spoke SDP to behave as a mesh SDP. See Note for more information. This keyword is supported only on the 7210 SAS-Sx/S 1/10GE operating in standalone mode.
This option is not blocked in a VPLS service, but it can be configured only for an EVPN-VPLS service. The default SHG is created when EVPN is enabled in the service, and all EVPN bindings are added to it by default.
egress
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure egress SDP.
ingress
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Commands in this context configure ingress SDP.
[no] force-vlan-vc-forwarding
config>service>epipe>spoke-sdp
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command forces vc-vlan-type forwarding in the datapath for spoke/mesh SDPs which have either vc-type. This command is not allowed on vlan-vc-type SDPs.
The no form of this command reverts to the default value.
disabled
hash-label [signal-capability]
no hash-label
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
7210 SAS-Mxp, 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, 7210 SAS-R12 IMM-c, and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC)
This command enables the use of a hash label on a VLL or VPLS service bound to LDP or RSVP SDP, using the autobind mode with the ldp, rsvp-te, or mpls options. When this command is enabled, the ingress datapath is modified such that the result of the hash on the packet header is communicated to the egress datapath for use, as the value of the label field of the hash label. Only the hash-2 parameters are used to compute the hash label, even if the SDP is over a lag (with load-balancing set as hash-1 or hash-2) or a port. The egress datapath adds the hash label at the bottom of the stack (BoS) and sets the S-bit to one.
On the 7210 SAS, the hash label is not used on the local node for ECMP hashing and LAG hashing. It is available for use by LSR nodes, through which the traffic flows and which are capable of using the labels for hashing.
Packets generated in CPM and that are forwarded labeled within the context of a service (for example, OAM packets) must also include a Hash Label at the BoS and set the S-bit accordingly.
The TTL of the hash label is set to a value of 0.
The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following procedures apply when the hash-label option and the signal-capability option are enabled on the local PE:
The 7210 local PE inserts the Flow Label Interface Parameters sub-TLV with T=1 and R=1 in the PW ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.
If remote PE does not send the Flow Label sub-TLV in the PW ID FEC element, or sends a Flow Label sub-TLV in the PW ID FEC element with T=FALSE and R=FALSE, then the local node disables the hash label capability. Therefore local PE node does not insert a hash label in user and control plane packets it forwards on the spoke-sdp or mesh-sdp. It also drops user and control plane packets received from remote PE if they include a hash label. Note that the latter may be caused by a remote 7210 PE which does not support the hash-label option, or which has the hash-label option enabled but does not support the signal-capability option, or does support both options but the user did not enable them due to a mis-configuration.
If remote PE sends Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, then the local PE enables the hash label capability. Therefore local PE inserts a hash label in user and control plane packets it forwards on the spoke-sdp or mesh-sdp. It also accepts user and control plane packets remote PE with or without hash label
If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire packets received by the local PE have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which results in the insertion of the hash label by both PE nodes.
If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire received by the local PE does not have the hash label included.
The user can enable or disable the signal-capability option in CLI as needed. When doing so, the router must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.
This feature is supported only for VLL and VPLS services. It not supported for VPRN services. It is also not supported on multicast packets forwarded using RSVP P2MP LPS or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance.
In 7x50 and possibly other vendor implementations, to allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. This means that the value of the hash label is always in the range [524,288 - 1,048,575] and does not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label does not match a value in the reserved label range. This is not supported on 7210 for service traffic (for MPLS OAM traffic the MSB bit is set). That is, 7210 SAS devices do not set the MSB bit in the hash label value for service traffic. Therefore, user must ensure that both the ends are correctly configured to either process hash labels or disable it.
The no form of this command disables the use of the hash label.
no hash-label
Enables the signaling and negotiation of the use of the hash label between the local and remote PE nodes.
[no] vc-label vc-label
config>service>vpls>mesh-sdp>egress
config>service>vpls>spoke-sdp>egress
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the egress VC label.
Specifies the VC egress value that indicates a specific connection.
[no] vc-label vc-label
config>service>vpls>mesh-sdp>ingress
config>service>vpls>spoke-sdp>ingress
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command configures the ingress VC label.
Specifies the VC ingress value that indicates a specific connection.
vlan-vc-tag 0..4094
no vlan-vc-tag [0..4094]
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
This command specifies an explicit Dot1q value used when encapsulating to the SDP far end. When signaling is enabled between the near and far end, the configured Dot1q tag can be overridden by a received TLV specifying the Dot1q value expected by the far end. This signaled value must be stored as the remote signaled Dot1q value for the binding.
The provisioned local Dot1q tag must be stored as the administrative Dot1q value for the binding.
When the Dot1q tag is not defined, the default value of zero is stored as the administrative dot1q value. Setting the value to zero is equivalent to not specifying the value.
The no form of this command disables the command.
no vlan-vc-tag
Specifies a valid VLAN identifier to bind an 802.1Q VLAN tag ID.