sdp sdp-id [mpls] [create]
no sdp sdp-id
config>service
Supported on all 7210 SAS platforms as described in this document
This command creates or edits a Service Distribution Point (SDP). SDPs must be explicitly configured.
An SDP is a logical mechanism that ties a far-end 7210 SAS device to a particular service without having to specifically define far-end SAPs. Each SDP represents a method to reach a far-end 7210 SAS router.
The 7210 SAS supports only MPLS encapsulation as the method to reach the far-end router It does not support GRE or other encapsulation methods. A 7210 SAS router supports both signaled and non-signaled LSPs through the network. Non-signaled paths are defined at each hop through the network. Signaled paths are communicated by protocol from end to end using Resource ReserVation Protocol (RSVP). Paths may be manually defined or a constraint-based routing protocol (such as OSPF-TE or CSPF) can be used to determine the best path with specific constraints. An LDP LSP can also be used for an SDP when the encapsulation is MPLS. The use of an LDP LSP type or an RSVP/Static LSP type are mutually exclusive except when the mixed-lsp option is enabled on the SDP.
SDPs are created, then bound to services. Many services may be bound to a single SDP. The operational and administrative state of the SDP controls the state of the SDP binding to the service.
If the sdp-id parameter does not exist, a new SDP is created. When creating an SDP, the mpls keyword must be specified. SDPs are created in the admin down state (shutdown) and the no shutdown command must be run when all relevant parameters are defined and before the SDP can be used.
If the sdp-id parameter exists, the current CLI context is changed to that SDP for editing and modification. For editing an existing SDP, the mpls keyword is specified. If a keyword is specified for an existing sdp-id, an error is generated and the context of the CLI is not changed to the specified sdp-id.
The no form of this command deletes the specified SDP. Before an SDP can be deleted, it must be administratively down (shutdown) and not bound to any services. If the specified SDP is bound to a service, the no sdp command fails, generating an error message specifying the first bound service found during the deletion process. If the specified sdp-id does not exist, an error is generated.
Specifies the SDP identifier.
accounting-policy acct-policy-id
no accounting-policy
config>service>sdp
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command enables the accounting policy context that can be applied to an SDP. An accounting policy must be defined before it can be associated with a SDP. If the policy-id does not exist, an error message is generated.
A maximum of one accounting policy can be associated with a SDP at one time. Accounting policies are configured in the config>log context.
The no form of this command removes the accounting policy association from the SDP, and the accounting policy reverts to the default.
Specifies the accounting policy-id, as configured in the config>log>accounting-policy context.
[no] collect-stats
config>service>sdp
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command enables accounting and statistical data collection for the SDP. When applying accounting policies, the data, by default, is collected in the appropriate records and written to the designated billing file.
When the no collect-stats command is issued, the statistics are still accumulated by the IOM cards; however, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued, the counters written to the billing file include all the traffic while the no collect-stats command was in effect.
no collect-stats
hash-label [signal-capability]
no hash-label
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command configures the hash label on VLL or VPLS services that are bound to an LDP or RSVP SDP using the auto-bind 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. The egress datapath appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).
On 7210 SAS devices, the hash label is not used on the local node for ECMP and LAG hashing. It is available for use by LSR nodes, through which the traffic flows, that are capable of using the labels for hashing.
Packets generated in the CPM that are forwarded with a label 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.
Signaling of the hash label capability is enabled by adding the signal-capability option under the VLL spoke-SDP, VPLS spoke-SDP, or mesh-SDP interface, or PW template instance. In this case, the decision of the local PE to insert the hash label on the user and control plane packets is determined by the outcome of the signaling process and can override the local PE configuration. The following process flow applies when the hash-label and the signal-capability options are enabled on the local PE.
The 7210 SAS 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 the specific spoke-SDP or mesh-SDP.
If a 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, the local node disables the hash label capability. Consequently, the local PE node does not insert a hash label in the user and control plane packets that it forwards on the spoke-SDP or mesh-SDP. The local PE node also drops user and control plane packets received from remote PE if they include a hash label. The dropped packets may be caused by any of the following:
a remote 7210 SAS PE that does not support the hash-label command
a remote 7210 SAS PE that has the hash-label command enabled but does not support the signal-capability option
a remote 7210 SAS PE that supports the hash-label command and the signal-capability option, but the user did not enable them due to a misconfiguration
If the remote PE sends Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, the local PE enables the hash label capability. Consequently, the local PE node inserts a hash label in the user and control plane packets that it forwards on the spoke-SDP or mesh-SDP. The local PE node also accepts user and control plane packets from the remote PE with or without the hash label.
If the hash-label command is enabled on the local PE with signal-capability option configured and on the remote PE without the signal-capability option configured on the spoke-SDP or mesh-SDP, the hash label is included in the pseudowire packets received by the local PE node. These packets must be dropped. To resolve this situation, disable the signaling-capability option on the local node, which results in the insertion of the hash label by both the local and remote PE nodes.
If the hash-label option is not supported or is not enabled on the local configuration of the spoke-SDP or mesh-SDP at the remote PE, the hash label is not included in the pseudowire received by the local PE.
If the signal-capability option is enabled or disabled in the CLI, 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 is 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.
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 to 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 SAS 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, the user must ensure that both the ends are correctly configured to either process hash labels or disable them.
The no form of this command disables the use of the hash label.
no hash-label
Keyword that enables the signaling and negotiation of hash label use between the local and remote PE nodes.
vc-type {ether | vlan}
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command overrides the default VC type signaled for the binding to the far-end SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vctype command can still be used to define the dot1q value expected by the far-end provider equipment.
A change of the bindings 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 ether and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding. (hex 5)
Defines the VC type as VLAN. The ether and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings.
vlan-vc-tag vlan-id
no vlan-vc-tag
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
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 specifying no 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.
[no] adv-mtu-override
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command overrides the advertised VC-type MTU of all spoke-SDPs of Layer 2 services using this SDP-ID. When enabled, the router signals a VC MTU equal to the service MTU, which includes the Layer 2 header. It also allows this router to accept an MTU advertised by the far-end PE which value matches either its advertised MTU or its advertised MTU minus the Layer 2 headers.
By default, the router advertises a VC-MTU equal to the Layer 2 service MTU minus the Layer 2 header and always matches its advertised MTU to the one signaled by the far-end PE router, otherwise the spoke-SDP goes operationally down.
When this command is enabled on the SDP, it has no effect on a spoke-SDP of an IES/VPRN spoke interface using this SDP-ID. The router continues to signal a VC MTU equal to the net IP interface MTU, which is min (ip-mtu, sdp operational path mtu - Layer 2 headers). The router also continues to ensure that the advertised MTU values of both PE routers match or the spoke-SDP goes operationally down.
The no form of this command disables the VC-type MTU override and reverts to the default behavior.
no adv-mtu-override
[no] bgp-tunnel
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command enables BGP route tunnels available in the tunnel table to reach SDP far-end nodes. Use of BGP route tunnels are available only with MPLS-SDPs. Only one of the transport methods is allowed per SDP - LDP, RSVP-LSP or BGP-Tunnel (BGP-Tunnel is not supported on multimode LSP).
The 7210 SAS provides an option to install labels for only those BGP 3107 labeled routes that are in use by services. For more information about this option, refer to the 7210 SAS-Mxp, R6, R12, S, Sx, T Routing Protocols Guide.
The no form of this command disables resolving BGP route tunnel LSP for SDP far-end.
no bgp-tunnel
far-end ip-address node-id node-id [global-id global-id]
no far-end
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command configures the system IP address of the far-end destination 7210 SAS-R6 and 7210 SAS-R12 router for the Service Distribution Point (SDP) that is the termination point for a service.
The far-end IP address must be explicitly configured. The destination IP address must be a 7210 SAS device system IP address.
If the SDP uses MPLS encapsulation, the far-end ip-address is used to check LSP names when added to the SDP. If the ‟to IP address” defined within the LSP configuration does not exactly match the SDP far-end ip-address, the LSP is not added to the SDP and an error is generated.
If the SDP uses MPLS encapsulation, the far-end ip-address is used to check LSP names when added to the SDP. If the ‟to IP address” defined within the LSP configuration does not exactly match the SDP far-end ip-address, the LSP is not added to the SDP and an error is generated. Alternatively, an SDP that uses MPLS can have an MPLS-TP node with an MPLS-TP node-id and (optionally) global-id. In this case, the SDP must use an MPLS-TP LSP and the SDP signaling parameter must be set to off.
An SDP cannot be administratively enabled until a far-end ip-address or MPLS-TP node-id is defined. The SDP is operational when it is administratively enabled (no shutdown) and the far-end ip-address is contained in the IGP routing table as a host route. OSPF ABRs should not summarize host routes between areas. This can cause SDPs to become operationally down. Static host routes (direct and indirect) can be defined in the local device to alleviate this issue.
The no form of this command removes the currently configured destination IP address for the SDP. The ip-address parameter is not specified and will generate an error if used in the no far-end command. The SDP must be administratively disabled using the config service sdp shutdown command before the no far-end command can be executed. Removing the far end IP address causes all lsp-name associations with the SDP to be removed.
Specifies the system address of the far-end 7210 SAS devices for the SDP in dotted-decimal notation.
Specifies the MPLS-TP Node ID of the far-end system for the SDP, either in dotted-decimal notation (a.b.c.d) or an unsigned 32-bit integer (1 – 4294967295). This parameter is mandatory for an SDP using an MPLS-TP LSP.
Specifies the MPLS-TP Global ID of the far-end system for the SDP, in an unsigned 32-bit integer. This parameter is optional for an SDP using an MPLS-TP LSP. If not entered, a default value for the Global ID of ‟0” is used, which indicates that the far-end node is in the same domain as the local node. The user must explicitly configure a Global ID if its value is non-zero.
metric metric
no metric
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command specifies the metric used within the tunnel table manager for decision-making purposes. When multiple SDPs going to the same destination exist, this value is used as a tie-breaker by tunnel table manager users such as MP-BGP to select the route with the lower value.
Specifies the SDP metric.
[no] mixed-lsp-mode
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command enables the use by an SDP of the mixed-LSP mode of operation. This command indicates to the service manager that it must allow a primary LSP type and a backup LSP type in the same SDP configuration. For example, the lsp and ldp commands are allowed concurrently in the SDP configuration. The user can configure one or two types of LSPs under the same SDP. Without this command, these commands are mutually exclusive.
The user can configure an RSVP LSP as a primary LSP type with an LDP LSP as a backup type. The user can also configure a BGP RFC 3107 BGP LSP as a backup LSP type.
If the user configures an LDP LSP as a primary LSP type, the backup LSP type must be an RFC 3107 BGP labeled route.
At any time, the service manager programs only one type of LSP in the linecard that can activate it to forward service packets according to the following priority order:
RSVP LSP type. One RSVP LSP can be configured per SDP. This is the highest priority LSP type.
LDP LSP type. One LDP FEC is used per SDP. 7210 SAS does not support LDP ECMP.
BGP LSP type. One RFC 3107-labeled BGP prefix programmed by the service manager.
In the case of the RSVP/LDP SDP, the service manager programs the NHLFEs for the active LSP type preferring the RSVP LSP type over the LDP LSP type. If no RSVP LSP is configured or all configured RSVP LSPs go down, the service manager reprograms the linecard with the LDP LSP, if available. If not, the SDP goes operationally down.
When a higher priority LSP type becomes available, the service manager reverts back to this LSP at the expiry of the sdp-revert-time timer or the failure of the currently active LSP, whichever comes first. The service manager then reprograms the linecard accordingly. If the infinite value is configured, the SDP reverts to the highest priority LSP type only if the currently active LSP failed.
LDP uses a tunnel down damp timer that is set to three seconds by default. When the LDP LSP fails, the SDP reverts to the RSVP LSP type after the expiry of this timer. For an immediate switchover, this timer must be set to zero. Use the configure router ldp tunnel-down-damp-time command. For more information about the configure router ldp tunnel-down-damp-time command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T MPLS Guide.
If the user changes the value of the sdp-revert-time timer, it takes effect only at the next use of the timer. Any timer that is outstanding at the time of the change is restarted with the new value.
In the case of the LDP/BGP SDP, the service manager prefers the LDP LSP type over the BGP LSP type. The service manager reprograms the linecard with the BGP LSP if available, otherwise it brings down the SDP operationally.
Also, the following difference in behavior exists for the LDP/BGP SDP compared to that of an RSVP/LDP SDP. For a specific /32 prefix, only a single route exists in the routing table: the IGP route or the BGP route; therefore, either the LDP FEC or the BGP label route is active at any specific time. The impact of this is that the tunnel table needs to be reprogrammed each time a route is deactivated and the other is activated. Also, the SDP revert-time cannot be used because there is no situation where both LSP types are active for the same /32 prefix.
The no form of this command disables the mixed-LSP mode of operation. The user first has to remove one of the LSP types from the SDP configuration or the command fails.
no mixed-lsp-mode
revert-time {revert-time | infinite}
no revert-time
config>service>sdp>mixed-lsp-mode
Supported on all 7210 SAS platforms as described in this document
This command configures the delay period the SDP must wait before it reverts to a higher priority LSP type when one becomes available.
The no form of this command resets the timer to the default value of 0. This means the SDP reverts immediately to a higher priority LSP type when one becomes available.
0
Specifies the delay period, in seconds, that the SDP must wait before it reverts to a higher priority LSP type when one becomes available. A value of zero means the SDP reverts immediately to a higher priority LSP type when one becomes available.
This keyword forces the SDP to never revert to another higher priority LSP type unless the currently active LSP type is down.
[no] ldp
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command enables LDP-signaled LSPs on MPLS-encapsulated SDPs.
In MPLS SDP configurations either one LSP can be specified or LDP can be enabled. The SDP ldp and lsp commands are mutually exclusive. If an LSP is specified on an MPLS SDP, LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already specified, the LSP must be removed from the configuration using the no lsp lsp-name command.
Alternatively, if LDP is already enabled on an MPLS SDP, an LSP cannot be specified on the SDP. To specify an LSP on the SDP, the LDP must be disabled. The LSP must have already been created in the config>router>mpls context using a valid far-end IP address. The preceding rules are relaxed when the mixed-lsp option is enabled on the SDP.
no ldp
lsp lsp-name
no lsp lsp-name
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command creates associations between one LSP and an Multi-Protocol Label Switching (MPLS) Service Distribution Point (SDP). This command is implemented only on MPLS-type encapsulated SDPs.
In MPLS SDP configurations either one LSP can be specified.
The LSP must have already been created in the config>router>mpls context using a valid far-end IP address. RSVP must be enabled.
If no LSP is associated with an MPLS SDP, the SDP cannot enter the operationally up state. The SDP can be administratively enabled (no shutdown) with no LSP associations. The lsp-name may be shutdown, causing the association with the SDP to be operationally down (the LSP is not used by the SDP).
If an exact match of lsp-name does not already exist as a defined LSP, an error message is generated. If the lsp-name exists and the LSP to IP address matches the SDP far-end IP address, the association is created.
The no form of this command deletes one LSP association from an SDP. If the lsp-name does not exist as an association or as a configured LSP, no error is returned. An lsp-name must be removed from all SDP associations before the lsp-name can be deleted from the system. The SDP must be administratively disabled (shutdown) before the last lsp-name association with the SDP is deleted.
Specifies the name of the LSP to associate with the SDP. An LSP name is case-sensitive and is limited to 32 ASCII 7-bit printable characters with no spaces.
signaling {off | tldp}
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command specifies the signaling protocol used to obtain the ingress and egress pseudowire labels in frames transmitted and received on the SDP. When signaling is off, labels are manually configured when the SDP is bound to a service. The signaling value can only be changed while the administrative status of the SDP is down.
To modify the signaling configuration, the SDP must be administratively shut down, then the signaling parameter can be modified and reenabled.
tldp
Specifies that ingress and egress signal auto-labeling is not enabled. If this keyword is selected, each service using the specified SDP must manually configure VPN labels. This configuration is independent of the SDP transport type, MPLS (RSVP or LDP).
Specifies that ingress and egress pseudowire signaling using T-LDP is enabled.
path-mtu bytes
no path-mtu
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command configures the Maximum Transmission Unit (MTU) in bytes that the Service Distribution Point (SDP) can transmit to the far-end device router without packet dropping or IP fragmentation overriding the SDP-type default path-mtu.
The default SDP-type path-mtu can be overridden on a per SDP basis. Dynamic maintenance protocols on the SDP like RSVP may override this setting.
If the physical mtu on an egress interface indicates the next hop on an SDP path cannot support the current path-mtu, the operational path-mtu on that SDP is modified to a value that can be transmitted without fragmentation. By default, the default path-mtu defined on the system for the type of SDP is used.
The no form of this command removes any path-mtu defined on the SDP, and the SDP uses the system default for the SDP type.
[no] sr-isis
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command configures the IS-IS segment routing LSP type for an MPLS SDP. The SDP of LSP type sr-isis can be used with the far-end command. The signaling protocol for the service labels for an SDP using an SR tunnel can be configured to static (off), T-LDP (tldp), or BGP (bgp).
The no form of this command disables the use of the IS-IS segment routing LSP type for an MPLS SDP.
no sr-isis
[no] sr-ospf
config>service>sdp
Supported on all 7210 SAS platforms as described in this document
This command configures an OSPF segment routing LSP type for an MPLS SDP. The SDP of LSP type sr-ospf can be used with the far-end command. The signaling protocol for the service labels for an SDP using an SR tunnel can be configured to static (off), T-LDP (tldp), or BGP (bgp).
The no form of this command disables the use of the OSPF segment routing LSP type for an MPLS SDP.
no sr-ospf