IPv6 Segment Routing Traffic Engineering (SRv6 TE) policies apply to scenarios where multiple paths exist between a source node and a destination node on an SRv6 network. The device can use an SRv6 TE policy to flexibly steer traffic to a proper forwarding path.

SRv6 TE policy identification

An SRv6 TE policy is identified by the following items:

· BSID—SID of the ingress node (source node).

· Color—Color attribute for the forwarding path. You can use the color attribute to distinguish an SRv6 TE policy from other SRv6 TE policies that are configured for the same source and destination nodes.

· End-point—IPv6 address of the egress node (destination node).

SRv6 TE policy contents

As show in Figure 1, an SRv6 TE policy consists of candidate paths with different preferences. Each candidate path can have one or multiple subpaths identified by segment lists (also called SID lists).

· Candidate path

An SRv6 TE policy can have multiple candidate paths. Candidate paths are uniquely identified by their preference values. An SRv6 TE policy chooses a candidate path from all its candidate paths based on the preference values to forward traffic.

Two SRv6 TE policies cannot share the same candidate path.

· SID list

A SID list is a list of SIDs that indicates a packet forwarding path. Each SID is the IPv6 address of a node on the forwarding path.

A candidate path can have a single SID list or multiple SID lists that use different weight values. After an SRv6 TE policy chooses a candidate path with multiple SID lists, the traffic will be load shared among the SID lists based on weight values.

Figure 1 SRv6 TE policy contents

SRv6 TE policy creation

An SRv6 TE policy can be created in the following modes:

· Manual configuration from CLI

In this method, you need to manually configure the candidate settings for the SRv6 TE policy, such as candidate path preferences, SID lists and weights.

· Learning from an BGP IPv6 SR policy route

To support SRv6 TE policy, MP-BGP defines the BGP IPv6 SR policy address family and the SRv6 TE policy Network Layer Reachability Information (NLRI). The SRv6 TE policy NLRI is called the BGP IPv6 SR policy route. A BGP IPv6 SR policy route contains SRv6 TE policy settings, including the BSID, color, endpoint, candidate preferences, SID lists, and SID list weights.

The device can advertise its local SRv6 TE policy settings to its BGP IPv6 SR policy peer through a BGP IPv6 SR policy route. The peer device can create an SRv6 TE policy according to the received BGP IPv6 SR policy route.

SRv6 TE policy validity

An SRv6 TE policy must be valid in order to ensure successful traffic forwarding.

The following describes the rules for identifying the validity of an SRv6 TE policy:

1. An SRv6 TE policy is valid only if it has valid candidate paths.

2. A candidate path is valid only if it has a valid SID list.

3. A SID list is valid if none of the following situations exists:

¡ The SID list is empty.

¡ The weight of the SID list is 0.

¡ An SR node and the first IPv6 address in the SID list cannot reach each other.

Figure 2 SRv6 TE policy validity determination

Traffic steering to an SRv6 TE policy

The following modes are available to steer traffic to an SRv6 TE policy:

· Color—The device searches for an SRv6 TE policy that has the same color and end-point address as the color and nexthop address of a BGP route. If such an SRv6 TE policy exists, the device recurse the BGP route to that SRv6 TE policy. Then, when the device receives packets that match the BGP route, it forwards the packets through the SRv6 TE policy.

· Tunnel policy—In an MPLS L3VPN, EVPN L3VPN, EVPN VPLS, or EVPN VPWS network, use an SRv6 TE policy as the public tunnel to carry the packets of a VPN instance. For more information about the tunnel policy configuration, see MPLS Configuration Guide.

SRv6 TE policy path selection

After traffic is steered in to an SRv6 TE policy, the SRv6 TE policy selects a forwarding path for the traffic as follows:

1. Selects the valid candidate path that has the highest preference.

2. Performs Weighted ECMP (WECMP) load sharing among the SID lists of the selected candidate path. The load of SID list x is equal to Weight x/(Weight 1 + Weight 2 + … + Weight n).

For example, as shown in Figure 3, Device A first selects a valid SRv6 TE policy by BSID. Then, the device selects a candidate path by preference. The candidate path has two valid SID lists: SID list 1 and SID list 2. The weight value of SID list 1 is 20 and the weight value of SID list 2 is 80. One fifth of the traffic will be forwarded through the subpath identified by SID list 1. Four fifth of the traffic will be forwarded through the subpath identified by SID list 2.

Figure 3 SRv6 TE policy path selection

SRv6 TE policy forwarding procedure

As shown in Figure 4, the SRv6 TE policy forwarding procedure is as follows (BSID-based traffic steering as an example):

1. After Device A receives a packet with destination address 100::1, it searches its IPv6 routing table and determines that the address is a BSID. Then, Device A encapsulates the packet with an SRH header according to the SRv6 TE policy of the BSID. The SRH header contains SID list {10::2, 20::2, 30::2}, where 10::2 is the SID for Device B, 20::2 is the SID for Device C, and 30::2 is the SID for Device D.

2. Device A forward the packet to the next hop Device B.

3. After Device B receives the packet, it obtains the next hop Device C from the SRH, and then forwards the packet to Device C.

4. After Device C receives the packet, it obtains the next hop Device D from the SRH, and then forwards the packet to Device D.

5. After Device D receives the packet, it identifies that the SL value is 0 in the SRH. So Device D decapsulates the packet. Device D deletes the SRH header and forwards the packet according to the destination address of the packet.

Figure 4 SRv6 TE policy forwarding diagram

SBFD for SRv6 TE policy

An SRv6 TE policy cannot maintain its status by exchanging messages between devices. You can configure seamless BFD (SBFD) to verify the connectivity of an SRv6 TE policy to implement fast failover in milliseconds.

As shown in Figure 5, configure an SRv6 TE policy on Device A and use SBFD to detect the SRv6 TE policy. The detection process is as follows:

1. The source node (Device A, the initiator) and sends SBFD packets that encapsulate the SID lists of the primary and backup candidate paths of the SRv6 TE policy.

2. After the destination node (Device E, the reflector) receives an SBFD packets, it checks whether the remote discriminator carried the packet is the same as the local discriminator. If yes, the reflector sends the SBFD response packet to the initiator by using the IPv6 routing table. If no, the reflector drops the SBFD packet.

3. If the source node can receive the SBFD response within the detection timeout time, it determines the corresponding SID list (forwarding path) of the SRv6 TE policy is available. If no response is received, the device determines that the SID list is faulty. If all the SID lists for the primary path are faulty, SBFD triggers a primary-to-back path switchover.

Figure 5 SBFD for SRv6 TE policy procedure

NOTE:

Because SBFD responses are forwarded according to the IPv6 routing table lookup, all SBFD sessions for the SRv6 TE policies that have the same source and destination nodes use the same path to send responses. A failure of the SBFD response path will cause all the SBFD sessions to be down. Consequently, all the associated SRv6 TE policies will be unable to forward packets.

‌

SRv6 TE policy hot standby

If an SRv6 TE policy has multiple valid candidate paths, the device chooses the candidate path with the greatest preference value. If the chosen path fails, the SRv6 TE policy must select another candidate path. During path reselection, packet loss might occur and thus affect service continuity.

The SRv6 TE hot standby feature can address this issue. This feature takes the candidate path with the greatest preference value as the primary path and that with the second greatest preference value as the backup path in hot standby state. As shown in Figure 6, when the forwarding paths corresponding to all SID lists of the primary path fails, the standby path immediately takes over to minimize service interruption.

Figure 6 SRv6 TE policy hot standby

‌

You can configure both the hot standby and SBFD features for an SRv6 TE policy. Use SBFD to detect the availability of the primary and standby paths specified for hot standby. If all SID lists of the primary path become unavailable, the standby path takes over and a path recalculation is performed. The standby path becomes the new primary path, and a new standby path is selected. If both the primary and standby paths fail, the SRv6 TE policy will calculate new primary and standby paths.

SRv6 TE policy tasks at a glance

To configure an SRv6 TE policy, perform the following tasks:

1. Configuring an SRv6 TE policy and configure basic settings for the policy:

a. Creating an SRv6 TE policy

b. Configuring a candidate path and the SID lists of the path

c. (Optional.) Enabling the device to distribute SRv6 TE policy candidate path information to BGP-LS

d. (Optional.) Shutting down an SRv6 TE policy

2. (Optional.) Configuring BGP to advertise BGP IPv6 SR policy routes

a. Enabling BGP to advertise BGP IPv6 SR policy routes

b. Configuring BGP to redistribute BGP IPv6 SR policy routes

c. (Optional.) Enabling advertising BGP IPv6 SR policy routes to EBGP peers

d. (Optional.) Enabling Router ID filtering

e. (Optional.) Configuring BGP to control BGP IPv6 SR policy route selection and advertisement

f. (Optional.) Maintaining BGP sessions

3. Configuring SRv6 TE policy traffic steering

4. (Optional.) Configuring high availability features for SRv6 TE policy

¡ Enabling SBFD for SRv6 TE policies

¡ Enabling hot standby for SRv6 TE policies

¡ Configuring path switchover and deletion delays for SRv6 TE policies

¡ Configuring path connectivity verification for SRv6 TE policies

5. (Optional.) Configuring advanced settings for SRv6 TE policies

¡ Specifying the packet encapsulation type preferred in optimal route selection

6. (Optional.) Maintaining an SRv6 TE policy

¡ Configuring SRv6 TE policy resource usage alarm

¡ Enabling SRv6 TE policy logging

¡ Enabling SNMP notifications for SRv6 TE policies

Creating an SRv6 TE policy

Manually creating an SRv6 TE policy and configuring its attributes

About this task

An SRv6 TE policy is identified by a BSID, color, and end-point.

You can bind a BSID to the policy manually, or set only the color and end-point attributes of the policy so the system automatically assigns a BSID to the policy. If you use both methods, the manually bound BSID takes effect.

Restrictions and guidelines

The configured BSID must be on the locator specified for SRv6 TE policies in SRv6 TE view. Otherwise, the SRv6 TE policy cannot forward packets. For more information about the locator configuration, see "Configuring SRv6."

Different SRv6 TE policies cannot have the same color and end-point configuration.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Specify a locator for SRv6 TE.

srv6-policy locator locator-name

By default, no locator is specified for SRv6 TE.

5. Enter SRv6 TE policy view.

policy policy-name

6. Configure a BSID for the policy.

binding-sid ipv6 ipv6-address

7. Set the color and endpoint attributes.

color color-value end-point ipv6 ipv6-address

By default, the color and endpoint attributes of an SRv6 TE policy are not configured.

Configuring a candidate path and the SID lists of the path

Restrictions and guidelines

Do not configure an SRv6 TE policy candidate path to use both manually configured SID lists and PCE-computed SID lists.

Configuring a candidate path to use manually configured SID lists

About this task

Before you specify a SID list for a candidate path, you need to create the SID list and add nodes to the SID list.

After you add nodes to a SID list, the system will sort the nodes in ascending order of node index. The node with the smallest index represents the next hop of the source node on the forwarding path.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Create a SID list and enter SID list view.

segment-list segment-list-name

5. Add a node to the SID list.

¡ Add a normal 128-bit SRv6 SID.

index index-number ipv6 ipv6-address

6. Return to SRv6 TE view.

quit

7. Enter SRv6 TE policy view.

policy policy-name

8. Create and enter SRv6 TE policy candidate path view.

candidate-paths

9. Set the preference for a candidate path and enter SRv6 TE policy path preference view.

preference preference-value

By default, no candidate path preferences are set.

Each preference represents a candidate path.

10. Specify an explicit path for the candidate path.

explicit segment-list segment-list-name [ source-ipv6 ipv6-address | weight weight-value ] *

A candidate path can have multiple SID lists.

Enabling the device to distribute SRv6 TE policy candidate path information to BGP-LS

About this task

After this feature is enabled, the device distributes SRv6 TE policy candidate path information to BGP-LS. BGP-LS advertises the SRv6 TE policy candidate path information in routes to meet application requirements.

Prerequisites

Before you configure this feature, enable the device to exchange LS information with the related peer or peer group. For more information about the LS exchange capability, see the BGP LS configuration in Layer 3—IP Routing Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Enable the device to distribute SRv6 TE policy candidate path information to BGP-LS.

distribute bgp-ls

By default, the device cannot distribute SRv6 TE policy candidate path information to BGP-LS

Shutting down an SRv6 TE policy

About this task

This feature controls the administrative state of an SRv6 TE policy.

If multiple SRv6 TE policies exist on the device, you can shut down unnecessary SRv6 TE policies to prevent them from affecting traffic forwarding.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Enter SRv6 TE policy view.

policy policy-name

5. Shut down the SRv6 TE policy.

shutdown

By default, an SRv6 TE policy is not administratively shut down.

Configuring BGP to advertise BGP IPv6 SR policy routes

Restrictions and guidelines for BGP IPv6 SR policy routes advertisement

For more information about BGP commands, see Layer 3—IP Routing Commands.

Enabling BGP to advertise BGP IPv6 SR policy routes

1. Enter system view.

system-view

2. Configure a global router ID.

router id router-id

By default, no global router ID is configured.

3. Enable a BGP instance and enter its view.

bgp as-number [ instance instance-name ]

By default, BGP is disabled and no BGP instances exist.

4. Configure a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } as-number as-number

5. Create the BGP IPv6 SR policy address family and enter its view.

address-family ipv6 sr-policy

6. Enable BGP to exchange BGP IPv6 SR policy routing information with the peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } enable

By default, the device cannot use BGP to exchange BGP IPv6 SR policy routing information with a peer or peer group.

Configuring BGP to redistribute BGP IPv6 SR policy routes

About this task

After you configure BGP to redistribute BGP IPv6 SR policy routes, the system will redistribute the local BGP IPv6 SR policy routes to the BGP routing table and advertise the routes to peers. Then, the peers can forward traffic based on the SRv6 TE policy.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP IPv6 SR policy address family view.

address-family ipv6 sr-policy

4. Enable BGP to redistribute BGP IPv6 SR policy routes.

import-route sr-policy

By default, BGP does not redistribute BGP IPv6 SR policy routes.

Enabling advertising BGP IPv6 SR policy routes to EBGP peers

About this task

By default, BGP IPv6 SR policy routes are advertised among IBGP peers. To advertise BGP IPv6 SR policy routes to EBGP peers, you must perform this task to enable the advertisement capability.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP IPv6 SR policy address family view.

address-family ipv6 sr-policy

4. Enable advertising BGP IPv6 SR policy routes to EBGP peers.

advertise ebgp enable

By default, BGP IPv6 SR policy routes are not advertised to EBGP peers.

Enabling Router ID filtering

About this task

For the device to process only part of the received BGP IPv6 SR policy routes, you can perform this task to enable filtering the routes by Router ID.

This feature enables the device to check the Route Target attribute of a received BGP IPv6 SR policy route. The device accepts the route only if the Route Target attribute contains the Router ID of the local device.

Restrictions and guidelines

To use Router ID filtering, make sure you add Route Target attributes to BGP IPv6 SR policy routes properly by using routing policy or other methods. Otherwise, Router ID filtering might learn or drop BGP IPv6 SR policy routes incorrectly.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP IPv6 SR policy address family view.

address-family ipv6 sr-policy

4. Enable Router ID filtering.

router-id filter

By default, Router ID filtering is disabled.

Configuring BGP to control BGP IPv6 SR policy route selection and advertisement

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP IPv6 SR policy address family view.

address-family ipv6 sr-policy

4. Specify the local router as the next hop for routes sent to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } next-hop-local

By default, BGP sets the local router as the next hop for all routes sent to an EBGP peer or peer group. BGP does not set the local router as the next hop for routes sent to an IBGP peer or peer group.

5. Allow a local AS number to exist in the AS_PATH attribute of routes from a peer or peer group, and to set the number of times the local AS number can appear.

peer { group-name | ipv6-address [ prefix-length ] } allow-as-loop [ number ]

By default, the local AS number is not allowed to exist in the AS_PATH attribute of routes from a peer or peer group.

6. Specify a preferred value for routes received from a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } preferred-value value

By default, the preferred value is 0 for routes received from a peer or peer group.

7. Set the maximum number of routes that can be received from a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *

By default, the number of routes that can be received from a peer or peer group is not limited.

8. Configure the device as a route reflector and specify a peer or peer group as a client.

peer { group-name | ipv6-address [ prefix-length ] } reflect-client

By default, neither the route reflector nor the client is configured.

9. Specify an IPv6 prefix list to filter routes received from or advertised to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } prefix-list ipv6-prefix-list-name { export | import }

By default, no prefix list based filtering is configured.

10. Apply a routing policy to routes incoming from or outgoing to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } route-policy route-policy-name { export | import }

By default, no routing policy is applied to routes incoming from or outgoing to a peer or peer group.

11. Advertise the COMMUNITY attribute to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } advertise-community

By default, BGP does not advertise the COMMUNITY attribute to any peers or peer groups.

12. Advertise the extended community attribute to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } advertise-ext-community

By default, BGP does not advertise the extended community attribute to any peers or peer groups.

13. Advertise the Large Community attribute to a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } advertise-large-community

By default, BGP does not advertise the Large Community attribute any peers or peer groups.

14. Assign a peer or peer group a high priority in BGP route selection.

peer { group-name | ipv6-address [ prefix-length ] } high-priority

By default, a peer or peer group does not have a high priority in BGP route selection.

15. Configure the route selection delay time.

route-select delay delay-value

By default, the route selection delay time is 0 seconds, which means no route selection delay.

Maintaining BGP sessions

To maintain BGP sessions, execute the following commands in user view:

· Reset BGP sessions for the BGP IPv6 SR policy address family.

reset bgp [ instance instance-name ] { as-number | ipv6-address [ prefix-length ] | all | external | group group-name | internal } ipv6 sr-policy

· Soft-reset BGP sessions for the BGP IPv6 SR policy address family.

refresh bgp [ instance instance-name ] { ipv6-address [ prefix-length ] | all | external | group group-name | internal } { export | import } ipv6 sr-policy

Configuring SRv6 TE policy traffic steering

Configuring the SRv6 TE policy traffic steering mode

Prerequisites

To use color-based traffic steering, you need to add the color extended community to IPv6 unicast routes by using routing policy or other methods. For information about the routing policy configuration, see Layer 3—IP Routing Configuration Guide.

To use tunnel policy-based traffic steering, you need to configure a bound tunnel, preferred tunnel, or load sharing tunnel policy that uses an SRv6 TE policy. For more information about the tunnel policy configuration, see MPLS Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Configure the traffic steering mode for SRv6 TE policies.

sr-policy steering [ disable | policy-based ]

By default, the device steering data packets to SRv6 TE policies based on colors of the packets.

If you specify the policy-based keyword, the device steers traffic based on the bound policy, color, and tunnel load sharing policy in a descending order of priority.

Configuring color-based traffic steering

About this task

To steer traffic to an SRv6 TE policy based on colors, you can configure a color extended community for routes that do not carry a color extended community in the following methods:

· Configure a routing policy to add a color value to routes.

· Configure a default color value.

The color value specified in the routing policy is preferred.

Restrictions and guidelines

The default color value applies only to the VPN routes or public network routes learned from a remote PE.

The default color value is used only for SRv6 TE policy traffic steering. It does not used in route advertisement.

Procedure

1. Enter system view.

system-view

2. Enter routing policy node view.

route-policy route-policy-name { deny | permit } node node-number

3. Set the color extended community attribute for BGP routes.

apply extcommunity color color [ additive ]

By default, no color extended community attribute is set for BGP routes.

4. Return to system view.

quit

5. Enter BGP instance view.

bgp as-number [ instance instance-name ]

6. Enter a BGP address family view as needed:

¡ Enter BGP IPv4 unicast address family view.

address-family ipv4 [ unicast ]

¡ Enter BGP IPv6 unicast address family view

address-family ipv6 [ unicast ]

¡ Enter BGP VPNv4 address family view.

address-family vpnv4

¡ Enter BGP VPNv6 address family view.

address-family vpnv6

¡ Enter BGP EVPN address family view.

address-family l2vpn evpn

7. Apply the routing policy to filter routes advertised to or received from a peer or peer group.

peer { group-name | ipv6-address [ prefix-length ] } route-policy route-policy-name { export | import }

By default, no routing policy is applied to a peer or peer group.

Configuring a default color value for VPN routes

1. Enter system view.

system-view

2. Enter VPN instance view.

ip vpn-instance vpn-instance-name [ index vpn-index ]

3. Enter IPv4 address family view or IPv6 address family view of the VPN instance.

¡ Enter VPN instance IPv4 address family view.

address-family ipv4

¡ Enter VPN instance IPv6 address family view.

address-family ipv6

4. Configure a default color value for L3VPN route recursion to an SRv6 TE policy.

default-color color-value [ evpn ]

By default, no default color is configured for L3VPN route recursion to an SRv6 TE policy.

Configuring a default color value for public network routes

1. Enter system view.

system-view

2. Enter pubic instance view.

ip public-instance

3. Enter public instance IPv4 or IPv6 address family view.

¡ Enter public instance IPv4 address family view

address-family ipv4

¡ Enter public instance IPv6 address family view.

address-family ipv6

4. Configure a default color value for public network route recursion to an SRv6 TE policy.

default-color color-value

By default, no default color value is configured for public network route recursion to an SRv6 TE policy.

Configuring tunnel policy-based traffic steering

Configuring a tunnel policy

1. Enter system view.

system-view

2. Create a tunnel policy and enter tunnel policy view.

tunnel-policy tunnel-policy-name [ default ]

3. Configure the tunnel policy. Choose the following tasks as needed:

¡ Specify an SRv6 TE policy to be bound with the specified destination IPv6 address.

binding-destination dest-ipv6-address srv6-policy { name policy-name | end-point ipv6 ipv6-address color color-value } [ ignore-destination-check ] [ down-switch ]

By default, no SRv6 TE policy is specified for a tunnel policy.

¡ Specify an SRv6 TE policy as a preferred tunnel of the tunnel policy.

preferred-path srv6-policy name srv6-policy-name

By default, no preferred tunnel is specified for a tunnel policy.

¡ Configuring SRv6 TE policy load sharing for the tunnel policy.

select-seq srv6-policy load-balance-number number

By default, no load sharing tunnel policy is configured.

For more information about the tunnel policy commands, see MPLS Command Reference.

Specifying the tunnel policy for a VPN instance

1. Enter system view.

system-view

2. Enter a VPN instance view as needed.

¡ Enter VPN instance view.

ip vpn-instance vpn-instance-name

¡ Execute the following commands in sequence to enter VPN instance IPv4 address family view:

ip vpn-instance vpn-instance-name

address-family ipv4

¡ Execute the following commands in sequence to enter VPN instance IPv6 address family view:

ip vpn-instance vpn-instance-name

address-family ipv6

3. Specify a tunnel policy for the VPN instance.

tnl-policy tunnel-policy-name

By default, no tunnel policy is specified for a VPN instance.

For more information about this command, see MPLS L3VPN commands in MPLS Command Reference.

Specifying the tunnel policy for a PW

1. Enter system view.

system-view

2. Enter cross-connect group view.

xconnect-group group-name

3. Enter cross-connect view.

connection connection-name

4. Create an EVPN PW and specify a tunnel policy for this PW.

evpn local-service-id local-service-id remote-service-id remote-service-id tunnel-policy tunnel-policy-name

Specifying the tunnel policy for an EVPN instance

1. Enter system view.

system-view

2. Enter VSI view.

vsi vsi-name

3. Enter EVPN instance view.

evpn encapsulation srv6

4. Specify a tunnel policy for the EVPN instance.

tunnel-policy tunnel-policy-name

By default, no tunnel policy is specified for an EVPN instance.

For more information about this command, see EVPN Command Reference.

Enabling SBFD for SRv6 TE policies

Restrictions and guidelines

You can enable SBFD for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

The remote discriminator specified on the device (initiator) must be the same as that specified in the sbfd local-discriminator command on the reflector. Otherwise, the reflector will not send responses to the initiator. If you do not specify a remote discriminator when you execute the sbfd command for an SRv6 TE policy, you must enable SBFD for SRv6 TE policies globally in SRv6 TE view. If you do not enable SBFD globally for SRv6 TE policies, the SBFD session cannot be established for that SRv6 TE policy.

Procedure

1. Enter system view.

system-view

2. Configure the encapsulation mode as Encap for SBFD packets.

bfd srv6-encapsulation-mode encap

By default, the SRv6 TE policy encapsulation mode for SBFD packets is the Insert mode.

3. Configure the source IPv6 address used by the initiator to send SBFD packets.

sbfd source-ipv6 ipv6-address

By default, no source IPv6 address is configured for SBFD packets.

4. Enter SRv6 view.

segment-routing ipv6

5. Enter SRv6 TE view.

traffic-engineering

6. Enable SBFD for all SRv6 TE policies and configure the SBFD session parameters.

srv6-policy sbfd remote remote-id [ template template-name ] [ backup-template backup-template-name ]

By default, SBFD is disabled for all SRv6 TE policies.

7. Enter SRv6 TE policy view.

policy policy-name

8. Configure SBFD for the SRv6 TE policy.

sbfd { disable | enable [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ] [ oam-sid sid ] }

By default, SBFD is not configured for an SRv6 TE policy.

9. (Optional.) Enable BFD session down events to trigger the SRv6 TE policy path switchover.

bfd trigger path-down enable

By default, a BFD session down event cannot trigger SRv6 TE policy path switchover.

Enabling hot standby for SRv6 TE policies

Restrictions and guidelines

You can enable hot standby for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Enable hot standby for all SRv6 TE policies.

srv6-policy backup hot-standby enable

By default, hot standby is disabled for all SRv6 TE policies.

5. Enter SRv6 TE policy view.

policy policy-name

6. Configure hot standby for the SRv6 TE policy.

backup hot-standby { disable | enable }

By default, hot standby is not configured for an SRv6 TE policy, and the hot standby configuration in SRv6 TE view applies.

Configuring path switchover and deletion delays for SRv6 TE policies

About this task

The switchover delay and deletion delay mechanism is used to avoid traffic forwarding failure during a forwarding path (SID list) switchover.

When updating an SRv6 TE policy forwarding path, the device first establishes the new forwarding path before it deletes the old one. During the new path setup process, the device uses the old path to forward traffic until the switchover delay timer expires. When the switchover delay timer expires, the device switches traffic to the new path. The old path is deleted when the deletion delay timer expires.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Configure the switchover delay time and deletion delay time for the SRv6 TE policy forwarding path.

srv6-policy switch-delay switch-delay-time delete-delay delete-delay-time

By default, the switchover delay time and deletion delay time for the SRv6 TE policy forwarding path is 5000 milliseconds and 20000 milliseconds, respectively.

Configuring path connectivity verification for SRv6 TE policies

About this task

Typically, the controller deploys the SID list of an SRv6 TE policy. Without BFD configured, the first node cannot immediately detect path failures in the SRv6 TE policy. It only changes the SID list of the SRv6 TE policy as instructed by the controller that completes path recalculation upon detecting a topology change. If the controller or the link to the controller fails, the first node will be unable to detect failures and change SID lists, resulting in traffic loss.

For fast traffic switchover and high availability, you can enable path connectivity verification for the first node of the SRv6 TE policy. This feature enables the first node to collect network topology information, and verify all SID lists in the SRv6 TE policy as follows:

· If all SRv6 SIDs exist in the topology and the associated locator prefixes are routable, the SID list is valid.

· If any SRv6 SIDs do not exist in the topology or any of the associated locator prefixes are not routable, the SID list is invalid.

Upon detecting an invalid SID list (SID list failure), the first node changes paths as follows:

· If the valid candidate paths of the SRv6 TE policy contain multiple SID lists, and one of the SID list fails, traffic is distributed to other valid SID lists.

· If the SRv6 TE policy has valid primary and backup candidate paths, and all SID lists for the primary candidate path fail, traffic is distributed to the backup candidate path.

· If all valid candidate paths of the SRv6 TE policy fail, the SRv6 TE policy is faulty and an associated protection action is taken (for example, MPLS L3VPN FRR).

Restrictions and guidelines

You must perform this task on the first node of the SRv6 TE policy.

You can configure SRv6 TE policy path connectivity verification in both SRv6 TE view and SRv6 TE policy view. The configuration in SRv6 TE policy view takes precedence over the configuration in SRv6 TE view. If path connectivity verification is not configured for an SRv6 TE policy, the configuration in SRv6 TE applies.

The first node must have all SRv6 SIDs and routes in the IGP domain to detect their status through the following settings:

· Enable the IGP domain to forward routing information through IPv6 IS-IS.

· Use the distribute link-state command in IS-IS view for the first node to report link status. For more information about the command, see IS-IS commands in Layer 3—IP Routing Command Reference.

If a BSID exists in the segment list path, path connectivity verification will fail because the BSID cannot be flooded in the IGP topology. Do not perform this task in the scenario where BSID is deployed.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Enable path connectivity verification for all SRv6 TE policies.

srv6-policy path verification enable

By default, path connectivity verification is disabled for all SRv6 TE policies.

5. Enter SRv6 TE policy view.

policy policy-name

6. Configure path connectivity verification for an SRv6 TE policy.

path verification { enable | disable }

By default, path connectivity verification is not configured for an SRv6 TE policy. The setting configured in SRv6 TE view applies.

Specifying the packet encapsulation type preferred in optimal route selection

About this task

As shown in Figure 7, PE 4 is the RR, and it establishes an IBGP connection with PE 1, PE 2, and PE 3, respectively. PE 1 and PE 3 support SRv6. PE 2 does not support SRv6. Both an MPLS L3VPN connection and an EVPN L3VPN over SRv6 connection exist between PE 1 and PE 3.

In this case, you can perform this task to specify the preferred encapsulation type (SRv6 encapsulation or MPLS encapsulation) for BGP optimal route selection in the L3VPN. Then, BGP prefers the routes with the specified encapsulation type when routes have the same Preferred-value and LOCAL_PREF attributes. The subsequent route selection steps are the same as those in the original BGP route select procedure. For more information about BGP route selection, see BGP overview in Layer 3—IP Routing Configuration Guide.

Figure 7 MPLS L3VPN and EVPN L3VPN over SRv6 coexist

Procedure

1. Enter system view.

system-view

2. Enter BGP instance view.

bgp as-number [ instance instance-name ]

3. Enter BGP-VPN instance view.

ip vpn-instance vpn-instance-name

4. Specify the packet encapsulation type preferred in optimal route selection.

bestroute encap-type { mpls | srv6 }

By default, BGP does not select optimal routes according to the packet encapsulation type.

Configuring SRv6 TE policy resource usage alarm thresholds

About this task

After you configure this feature, when the number of SRv6 TE policy resources equals to or exceeds the upper threshold or drops to or below the lower threshold, the device generates log and alarm information. The administrator can then obtain the resource usage status of SRv6 TE policies.

SRv6 TE policy resources include the following:

· Number of valid forwarding paths for all SRv6 TE policies.

· Number of entries of the SRv6Policy type in the SRv6 forwarding table.

· Number of entries of the SRv6PSIDList type in the SRv6 forwarding table.

To view SRv6 forwarding table information, use the display segment-routing ipv6 forwarding command.

Restrictions and guidelines

To view resource usage for the current SRv6 TE policy, use the display segment-routing ipv6 te policy statistics command.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Configure the alarm thresholds for resource usage of SRv6 TE policies.

srv6-policy { forwarding-path | policy | segment-list } alarm-threshold upper-limit upper-limit-value lower-limit lower-limit-value

By default, the upper and lower alarm thresholds are 80% and 75% for all resources of SRv6 TE policies.

Enabling SRv6 TE policy logging

About this task

This feature enables the device to generate logs for SRv6 TE policy state changes and resource usage anomalies. The administrator can use the logging information to audit SRv6 TE policies. The device delivers logs to its information center. The information center processes the logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see the network management and monitoring configuration guide for the device.

Procedure

1. Enter system view.

system-view

2. Enter SRv6 view.

segment-routing ipv6

3. Enter SRv6 TE view.

traffic-engineering

4. Enable SRv6 TE policy logging.

srv6-policy log enable

By default, SRv6 TE policy logging is disabled.

Enabling SNMP notifications for SRv6 TE policies

About this task

This feature enables the device to send SNMP notifications about state changes and resource usage anomalies of SRv6 TE policies. For SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

Procedure

1. Enter system view.

system-view

2. Enable SNMP notifications for SRv6 TE policies.

snmp-agent trap enable srv6-policy

By default, SNMP notifications for SRv6 TE policies are disabled.

Display and maintenance commands for SRv6 TE policies

Execute display commands in any view.

Task	Command
Display BGP peer or peer group information.	display bgp [ instance instance-name ] peer ipv6 [ sr-policy ] [ ipv6-address prefix-length \| { ipv6-address \| group-name group-name } log-info \| [ ipv6-address ] verbose ]
Display BGP IPv6 SR policy routing information.	display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ sr-policy-prefix [ advertise-info ] \| peer ipv6-address { advertised-routes \| received-routes } [ statistics ] \| statistics ]
Display BGP peer group information.	display bgp [ instance instance-name ] group ipv6 sr-policy [ group-name group-name ]
Display BGP update group information.	display bgp [ instance instance-name ] update-group ipv6 sr-policy [ ipv6-address ]
Display BFD information for SRv6 TE policies.	display segment-routing ipv6 te bfd [ down \| policy { { color color-value \| end-point ipv6 ipv6-address } * \| name policy-name } \| up ]
Display SRv6 TE policy database information.	display segment-routing ipv6 te database [ link \| node \| prefix \| srv6-sid ]
Display SRv6 TE forwarding information.	display segment-routing ipv6 te forwarding [ policy { name policy-name \| { color color-value \| end-point ipv6 ipv6-address } * } ] [ verbose ]
Display SRv6 TE policy information.	display segment-routing ipv6 te policy [ name policy-name \| down \| up \| { color color-value \| end-point ipv6 ip-address } * ]
Display information about the most recent down event for SRv6 TE policies.	display segment-routing ipv6 te policy last-down-reason [ binding-sid bsid \| color color-value endpoint ipv6 ipv6-address \| policy-name policy-name ]
Display SRv6 TE policy statistics.	display segment-routing ipv6 te policy statistics
Display status information about SRv6 TE policies.	display segment-routing ipv6 te policy status [ policy-name policy-name ]
Display SBFD information for SRv6 TE policies.	display segment-routing ipv6 te sbfd [ down \| policy { { color color-value \| end-point ipv6 ipv6-address } * \| name policy-name } \| up ]
Display SRv6 TE SID list information.	display segment-routing ipv6 te segment-list [ name seglist-name \| id id-value ]
Display information about SRv6 SIDs collected from the LS database.	display segment-routing ipv6 te source-sid [ end \| end-x \| sid ]

‌

SRv6 TE policy configuration examples

Example: Configuring SRv6 TE policy-based forwarding

Network configuration

As shown in Figure 8, perform the following tasks on the devices to implement SRv6 TE policy-based forwarding over a specific path:

· Configure Device A through Device D to run IS-IS to implement Layer 3 connectivity.

· Configure basic SRv6 on Device A through Device D.

· Configure an SRv6 TE policy on Device A to forward user packets along path Device A > Device B > Device C > Device D.

Figure 8 Network diagram

‌

Device	Interface	IP address	Device	Interface	IP address
Device A	Loop1	1::1/128	Device B	Loop1	2::2/128
	XGE2/0/0	1000::1/64		XGE2/0/0	1000::2/64
	XGE2/0/1	4000::1/64		XGE2/0/1	2000::2/64
Device C	Loop1	3::3/128	Device D	Loop1	4::4/128
	XGE2/0/0	3000::3/64		XGE2/0/0	3000::4/64
	XGE2/0/1	2000::3/64		XGE2/0/1	4000::4/64

Procedure

1. Configure IP addresses and masks for interfaces. (Details not shown.)

2. Configure Device A:

# Configure an SRv6 SID list.

[DeviceA] segment-routing ipv6

[DeviceA-segment-routing-ipv6] encapsulation source-address 1::1

[DeviceA-segment-routing-ipv6] locator a ipv6-prefix 5000:: 64 static 32

[DeviceA-segment-routing-ipv6-locator-a] opcode 1 end

[DeviceA-segment-routing-ipv6-locator-a] quit

[DeviceA-segment-routing-ipv6] traffic-engineering

[DeviceA-srv6-te] srv6-policy locator a

[DeviceA-srv6-te] segment-list s1

[DeviceA-srv6-te-sl-s1] index 10 ipv6 6000::1

[DeviceA-srv6-te-sl-s1] index 20 ipv6 7000::1

[DeviceA-srv6-te-sl-s1] index 30 ipv6 8000::1

[DeviceA-srv6-te-sl-s1] quit

# Create an SRv6 TE policy and set the attributes.

[DeviceA-srv6-te] policy p1

[DeviceA-srv6-te-policy-p1] binding-sid ipv6 5000::2

[DeviceA-srv6-te-policy-p1] color 10 end-point ipv6 4::4

[DeviceA-srv6-te-policy-p1] candidate-paths

[DeviceA-srv6-te-policy-p1-path] preference 10

[DeviceA-srv6-te-policy-p1-path-pref-10] explicit segment-list s1

[DeviceA-srv6-te-policy-p1-path-pref-10] quit

[DeviceA-srv6-te-policy-p1-path] quit

[DeviceA-srv6-te-policy-p1] quit

[DeviceA-srv6-te] quit

[DeviceA-segment-routing-ipv6] quit

# Configure IS-IS and set the IS-IS cost style to wide.

<DeviceA> system-view

[DeviceA] isis 1

[DeviceA-isis-1] network-entity 00.0000.0000.0001.00

[DeviceA-isis-1] cost-style wide

[DeviceA-isis-1] address-family ipv6 unicast

[DeviceA-isis-1-ipv6] segment-routing ipv6 locator a

[DeviceA-isis-1-ipv6] quit

[DeviceA-isis-1] quit

[DeviceA] interface ten-gigabitethernet 2/0/0

[DeviceA-Ten-GigabitEthernet2/0/0] isis ipv6 enable 1

[DeviceA-Ten-GigabitEthernet2/0/0] quit

[DeviceA] interface ten-gigabitethernet 2/0/1

[DeviceA-Ten-GigabitEthernet2/0/1] isis ipv6 enable 1

[DeviceA-Ten-GigabitEthernet2/0/1] quit

[DeviceA] interface loopback 1

[DeviceA-LoopBack1] isis ipv6 enable 1

[DeviceA-LoopBack1] quit

3. Configure Device B:

# Configure the SRv6 End.SID.

[DeviceB] segment-routing ipv6

[DeviceB-segment-routing-ipv6] locator b ipv6-prefix 6000:: 64 static 32

[DeviceB-segment-routing-ipv6-locator-b] opcode 1 end

[DeviceB-segment-routing-ipv6-locator-b] quit

[DeviceB-segment-routing-ipv6] quit

# Configure IS-IS and set the IS-IS cost style to wide.

<DeviceB> system-view

[DeviceB] isis 1

[DeviceB-isis-1] network-entity 00.0000.0000.0002.00

[DeviceB-isis-1] cost-style wide

[DeviceB-isis-1] address-family ipv6 unicast

[DeviceB-isis-1-ipv6] segment-routing ipv6 locator b

[DeviceB-isis-1-ipv6] quit

[DeviceB-isis-1] quit

[DeviceB] interface ten-gigabitethernet 2/0/0

[DeviceB-Ten-GigabitEthernet2/0/0] isis ipv6 enable 1

[DeviceB-Ten-GigabitEthernet2/0/0] quit

[DeviceB] interface ten-gigabitethernet 2/0/1

[DeviceB-Ten-GigabitEthernet2/0/1] isis ipv6 enable 1

[DeviceB-Ten-GigabitEthernet2/0/1] quit

[DeviceB] interface loopback 1

[DeviceB-LoopBack1] isis ipv6 enable 1

[DeviceB-LoopBack1] quit

4. Configure Device C:

# Configure the SRv6 End.SID.

[DeviceC] segment-routing ipv6

[DeviceC-segment-routing-ipv6] locator c ipv6-prefix 7000:: 64 static 32

[DeviceC-segment-routing-ipv6-locator-c] opcode 1 end

[DeviceC-segment-routing-ipv6-locator-c] quit

[DeviceC-segment-routing-ipv6] quit

# Configure IS-IS and set the IS-IS cost style to wide.

<DeviceC> system-view

[DeviceC] isis 1

[DeviceC-isis-1] network-entity 00.0000.0000.0003.00

[DeviceC-isis-1] cost-style wide

[DeviceC-isis-1] address-family ipv6 unicast

[DeviceC-isis-1-ipv6] segment-routing ipv6 locator c

[DeviceC-isis-1-ipv6] quit

[DeviceC-isis-1] quit

[DeviceC] interface ten-gigabitethernet 2/0/0

[DeviceC-Ten-GigabitEthernet2/0/0] isis ipv6 enable 1

[DeviceC-Ten-GigabitEthernet2/0/0] quit

[DeviceC] interface ten-gigabitethernet 2/0/1

[DeviceC-Ten-GigabitEthernet2/0/1] isis ipv6 enable 1

[DeviceC-Ten-GigabitEthernet2/0/1] quit

[DeviceC] interface loopback 1

[DeviceC-LoopBack1] isis ipv6 enable 1

[DeviceC-LoopBack1] quit

5. Configure Device D:

# Configure the SRv6 End.SID.

[DeviceD] segment-routing ipv6

[DeviceD-segment-routing-ipv6] locator d ipv6-prefix 8000:: 64 static 32

[DeviceD-segment-routing-ipv6-locator-d] opcode 1 end

[DeviceD-segment-routing-ipv6-locator-d] quit

[DeviceD-segment-routing-ipv6] quit

# Configure IS-IS and set the IS-IS cost style to wide.

<DeviceD> system-view

[DeviceD] isis 1

[DeviceD-isis-1] network-entity 00.0000.0000.0004.00

[DeviceD-isis-1] cost-style wide

[DeviceD-isis-1] address-family ipv6 unicast

[DeviceD-isis-1-ipv6] segment-routing ipv6 locator d

[DeviceD-isis-1-ipv6] quit

[DeviceD-isis-1] quit

[DeviceD] interface ten-gigabitethernet 2/0/0

[DeviceD-Ten-GigabitEthernet2/0/0] isis ipv6 enable 1

[DeviceD-Ten-GigabitEthernet2/0/0] quit

[DeviceD] interface ten-gigabitethernet 2/0/1

[DeviceD-Ten-GigabitEthernet2/0/1] isis ipv6 enable 1

[DeviceD-Ten-GigabitEthernet2/0/1] quit

[DeviceD] interface loopback 1

[DeviceD-LoopBack1] isis ipv6 enable 1

[DeviceD-LoopBack1] quit

Verifying the configuration

# Display SRv6 TE policy information on Device A.

[DeviceA] display segment-routing ipv6 te policy

Name/ID: p1/0

Color: 10

Endpoint: 4::4

Name from BGP:

BSID:

Mode: Explicit Type: Type_2 Request state: Succeeded

Current BSID: 5000::2 Explicit BSID: 5000::1 Dynamic BSID: -

Reference counts: 4

Flags: A/BS/NC

Status: Up

AdminStatus: Up

Up time: 2020-04-02 16:08:03

Down time: 2020-04-02 16:03:48

Hot backup: Disabled

Statistics: Disabled

Statistics by service class: Disabled

Drop-upon-invalid: Disabled

BFD trigger path-down: Disabled

SBFD: Disabled

BFD Echo: Disabled

Forwarding index: 2150629377

Association ID: 1

Service-class: -

PCE delegation: Not configured

PCE delegate report-only: Not configured

Encapsulation mode: -

Candidate paths state: Configured

Candidate paths statistics:

CLI paths: 1 BGP paths: 0 PCEP paths: 0

Candidate paths:

Preference : 10

CPathName:

Instance ID: 0 ASN: 0 Node address: 0.0.0.0

Peer address: ::

Optimal: Y Flags: V/A

Explicit SID list:

ID: 1 Name: s1

Weight: 1 Forwarding index: 2149580801

State: Up State(-): -

Verification State: -

Source IPv6 address: -

Active path MTU: 1500 bytes

The output shows that the SRv6 TE policy is in up state. The device can use the SRv6 TE policy to forward packets.

# Display SRv6 TE forwarding information on Device A.

[DeviceA] display segment-routing ipv6 te forwarding verbose

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 5000::2

Policy forwarding index: 2150629377

Main path:

Seglist ID: 1

Seglist forwarding index: 2149580801

Weight: 1

Outgoing forwarding index: 2148532225

Interface: XGE2/0/0

Nexthop: FE80::54CB:70FF:FE86:316

Path ID: 0

SID list: {6000::1, 7000::1, 8000::1}

# Display SRv6 forwarding information on Device A.

[DeviceA] display segment-routing ipv6 forwarding

Total SRv6 forwarding entries: 3

Flags: T - Forwarded through a tunnel

N - Forwarded through the outgoing interface to the nexthop IP address

A - Active forwarding information

B - Backup forwarding information

ID FWD-Type Flags Forwarding info

Attri-Val Attri-Val

--------------------------------------------------------------------------------

2148532225 SRv6PSIDList NA XGE2/0/0

FE80::54CB:70FF:FE86:316

{6000::1, 7000::1, 8000::1}

2149580801 SRv6PCPath TA 2148532225

2150629377 SRv6Policy TA 2149580801

07-Segment Routing Configuration Guide

Configuring SRv6 TE policies

About SRv6 TE policies

SRv6 TE policy identification

SRv6 TE policy creation

SRv6 TE policy validity

Traffic steering to an SRv6 TE policy

SRv6 TE policy path selection

SRv6 TE policy forwarding procedure

SRv6 TE policy tasks at a glance

About this task

Restrictions and guidelines

Procedure

Configuring a candidate path to use manually configured SID lists

About this task

Procedure

About this task

Prerequisites

Procedure

About this task

Procedure

Configuring BGP to redistribute BGP IPv6 SR policy routes

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Maintaining BGP sessions

Prerequisites

Procedure

About this task

Restrictions and guidelines

Procedure

Configuring a default color value for VPN routes

Configuring a default color value for public network routes

Configuring a tunnel policy

Specifying the tunnel policy for a VPN instance

Specifying the tunnel policy for a PW

Specifying the tunnel policy for an EVPN instance

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Configuring SRv6 TE policy resource usage alarm thresholds

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

SRv6 TE policy configuration examples

Network configuration

Procedure

Verifying the configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us