pw-routing
config>service
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure dynamic multi-segment pseudowire (MS-PW) routing. Pseudowire routing must be configured on each node that is a T-PE or an S-PE.
disabled
boot-timer timer-value
no boot-timer
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command configures a hold-off timer for MS-PW routing advertisements and signaling and is used at boot time.
The no form of this command removes a previously configured timer and reverts it to the default value.
boot-timer 10
Specifies the value of the boot timer in seconds.
local-prefix local-prefix [create]
no local-prefix local-prefix
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command configures one or more node prefix values to be used for MS-PW routing. At least one prefix must be configured on each node that is an S-PE or a T-PE.
The no form of this command removes a previously configured prefix, and causes the corresponding route to be withdrawn if it has been advertised in BGP.
no local-prefix
Specifies a 32-bit prefix for the AII. One or more prefix values, up to a maximum of 16, may be assigned to the node. The global ID can contain the 2-octet or 4-octet value of the provider Autonomous System Number (ASN). The presence of a global ID based on the provider ASN ensures that the AII for spoke-SDPs configured on the node are globally unique.
4294967295
4294967295
advertise-bgp route-distinguisher rd [community community]
no advertise-bgp route-distinguisher rd
config>service>pw-routing>local-prefix
Supported on all 7210 SAS platforms as described in this document
This command enables a specific prefix to be advertised in MP-BGP for dynamic MS-PW routing.
The no form of this command explicitly withdraws a route if it has been previously advertised.
no advertise-bgp
Specifies a 32-bit prefix for the AII. One or more prefix values, up to a maximum of 16, may be assigned to the node. The global ID can contain the 2-octet or 4-octet value of the provider Autonomous System Number (ASN). The presence of a global ID based on the provider ASN ensures that the AII for spoke-SDPs configured on the node is globally unique.
Specifies an optional BGP community attribute associated with the advertisement. To delete a previously advertised community, advertise-bgp route-distinguisher must be run again with the same value for the RD but excluding the community attribute.
path name [create]
no path name
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command configures an explicit path between this 7210 SAS T-PE and a remote 7210 SAS T-PE. For each path, one or more intermediate S-PE hops must be configured. A path can be used by multiple multisegment pseudowires. Paths are used by a 7210 T-PE to populate the list of Explicit Route TLVs included in the signaling of a dynamic MS-PW.
A path may specify all or only some of the hops along the route to reach a T-PE.
The no form of this command removes a specified explicit path from the configuration.
no path
Specifies a locally unique, case-sensitive alphanumeric name label for the MS-PW path of up to 32 characters.
hop hop-index ip-address
no hop hop-index
config>service>pw-routing>path
Supported on all 7210 SAS platforms as described in this document
This command configures each hop on an explicit path that can be used by one or more dynamic MSPWs. It specifies the IP addresses of the hops that the MS-PE should traverse. These IP addresses can correspond to the system IP address of each S-PE, or the IP address on which the T-LDP session to a specific S-PE terminates.
The no form of this command deletes hop list entries for the path. All the MS-PWs currently using this path are unaffected. Additionally, all services actively using these MS-PWs are unaffected. The path must be shut down first to delete the hop from the hop list. The no hop hop-index command does not result in an action, except for a warning message on the console indicating that the path is administratively up.
no hop
Specifies a locally significant numeric identifier for the hop. The hop index is used to order the hops specified. The LSP always traverses from the lowest hop index to the highest. The hop index does not need to be sequential.
Specifies the system IP address or terminating IP address for the T-LDP session to the S-PE corresponding to this hop. For a specific IP address on a hop, the system chooses the SDP.
retry-count [10..10000]
no retry-count
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This optional command specifies the number of attempts software should make to reestablish the spoke-SDP after it has failed. After each successful attempt, the counter is reset to zero.
When the specified number is reached, no more attempts are made, and the spoke-SDP is put into the shutdown state. Use the no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts to the default value.
30
Specifies the maximum number of retries before putting the spoke-SDP into the shutdown state.
retry-timer secs
no retry-timer
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command specifies a retry timer for the spoke-SDP. This is a configurable exponential back-off timer that determines the interval between retries to reestablish a spoke-SDP if it fails and a label withdraw message is received with the status code ‟AII unreachable”.
The no form of this command reverts the timer to its default value.
retry-timer 30
Specifies the initial retry timer value in seconds.
10 to 480
spe-address global-id:prefix
no spe-address
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command configures a single S-PE address for the node, which is used for dynamic MS-PWs. This value is used for the PW switching point TLV used in LDP signaling and is the value used by PW status signaling to indicate the PE that originates a PW status message. Configuring this parameter is mandatory to enable dynamic MS-PW support on a node.
If the S-PE address is not configured, spoke-SDPs that use dynamic MS-PWs and pw-routing localprefixes cannot be configured on a T-PE. Also, a 7210 SAS node sends a label release for any label mappings received for FEC129 AII type 2.
The S-PE address cannot be changed unless the dynamic ms-pw configuration is removed.
Changing the S-PE address also results in all dynamic MS-PWs for which this node is an S-PE being released. Nokia recommends that the S-PE address be configured for the life of an MS-PW configuration after reboot of the 7210 SAS.
The no form of this command removes the configured S-PE address.
no spe-address
Specifies a 4-octet value that is unique to the service provider. For example, the global ID can contain the 2-octet or 4-octet value of the provider Autonomous System Number (ASN).
Syntax: <global-id:prefix>: <global-id>:{<prefix>|<ipaddress>} global-id 1 to 4294967295 prefix 1 to 4294967295 ipaddress a.b.c.d
[no] static-route route-name
config>service>pw-routing
Supported on all 7210 SAS platforms as described in this document
This command configures a static route to a next-hop S-PE or T-PE. Static routes may be configured on either S-PEs or T-PEs.
A default static route is entered as follows:
static-route 0:0:next_hop_ip_addresss
or
static-route 0:0.0.0.0:next_hop_ip_address
The no form of this command removes a previously configured static route.
no static-route
Specifies the static pseudowire route.
4294967295 prefix a.b.c.d | 0— 4294967295 ip_addr a.b.c.d
[no] pw-template policy-id [use-provisioned-sdp] [create]
config>service
Supported on all 7210 SAS platforms as described in this document
This command configures an SDP template.
Specifies whether to use an already provisioned SDP. When specified, the tunnel manager is consulted for an existing active SDP. Otherwise, the default SDP template is used for instantiation of the SDP.
This keyword is required when creating the configuration context. When the context is created, it is possible to navigate to the context without the create keyword.
[no] control-word
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the control word on pseudowire packets in VPLS and enables the use of the control word individually on each mesh-sdp or spoke-SDP. By default, the control word is disabled. When the control word is enabled, all VPLS packets, including the BPDU frames, are encapsulated with the control word when sent over the pseudowire. The T-LDP control plane behavior is the same as in the implementation of the control word for VLL services. The configuration for the two directions of the Ethernet pseudowire should match.
The no form of this command reverts the mesh SDP or spoke-SDP to the default behavior of not using the control word.
no control-word