opcode { opcode | hex hex-opcode } end-dt46
Configure an End.DX4 SID. opcode { opcode | hex hex-opcode } end-dx4 interface interface-type
interface-number nexthop nexthop-ipv4-address
An End.DX4 SID cannot be configured with different output interfaces or next hops.
Configure an End.DX6 SID. opcode { opcode | hex hex-opcode } end-dx6 interface interface-type
interface-number nexthop nexthop-ipv6-address
An End.DX6 SID cannot be configured with different output interfaces or next hops.
Applying a locator to a BGP instance
About this task
In the IP public network over SRv6 scenario, use this feature in BGP IPv4 or IPv6 unicast address family view to apply for SRv6 SIDs for IPv4 or IPv6 routes.
Use this feature if the device will use End.DT4, End.DT6, End.DT46, End.DX4, or End.DX6 SIDs to deliver public network traffic across sites.
Prerequisites
Before you perform this task, you must create the specified locator.
Procedure
1. Enter system view. system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Enter BGP IPv4 or IPv6 unicast address family view.
Enter BGP IPv4 unicast address family view. address-family ipv4 [ unicast ]
Enter BGP IPv6 unicast address family view. address-family ipv6 [ unicast ]
4. Apply a locator to the BGP instance. segment-routing ipv6 locator locator-name [ auto-sid-disable ]
By default, no locator is applied to a BGP instance.
Configuring PEs to exchange BGP IPv4 or IPv6 unicast routes
Restrictions and guidelines
For more information about the commands in this task, see BGP in Layer 3—IP Routing Command
Reference .
To ensure optimal route selection and SRv6 tunnel traffic forwarding, make sure a pair of PEs are not both IPv4 and IPv6 peers to each other.
Procedure
1. Enter system view.
326
