Parameter Description instances created in cross-connect group view:
•
VPN instances.
•
The public instance.
•
EVPN instances created in VSI view, VPN instance view, and public instance view.
6. (Optional.) Apply a tunnel policy to the EVPN instance. tunnel-policy tunnel-policy-name
By default, no tunnel policy is applied to an EVPN instance.
For more information about this command, see EVPN Command Reference .
Configuring SRv6 SIDs
Restrictions and guidelines
For more information about the commands in this task, see SRv6 commands in Segment Routing
Command Reference .
Procedure
1. Enter system view. system-view
2. Enable SRv6 and enter SRv6 view. segment-routing ipv6
3. Configure a locator and enter SRv6 locator view.
locator locator-name [ ipv6-prefix ipv6-address prefix-length [ args args-length | static static-length ] * ]
4. Configure the opcode portion.
Configure End.DT4 SIDs.
opcode opcode end-dt4 [ vpn-instance vpn-instance-name [ evpn ] ]
The specified VPN instance must exist. You cannot configure the same End.DT4 SID for different VPN instances.
Configure End.DT46 SIDs.
opcode opcode end-dt46 [ vpn-instance vpn-instance-name [ evpn ] ]
The specified VPN instance must exist. You cannot configure the same End.DT46 SID for different VPN instances.
Configuring a VSI interface as a distributed SRv6 gateway
About this task
To save Layer 3 interface resources on a distributed SRv6 gateway, multiple EVPN VPLS networks can share one VSI interface. You can assign multiple IPv4 addresses to the VSI interface for the
EVPN VPLS networks to use as gateway addresses.
When multiple EVPN VPLS networks share a VSI interface, you must specify the subnet of each VSI for the VSI interface to identify the VSI of a packet. The subnets must be unique.
310
