Global IPv4IPv6 Routing Table


We verified that IPv4 and Ipv6 prefixes can be transported natively over an SRv6 network without VRF-based VPN services. The Egress PE advertised correctly an SRv6 service SID for IPv4/IPv6 prefixes in BGP and then the ingress PE encapsulated IPv4/IPv6 packets into IPv6 using advertised SRv6 SID as the outer IPv6 destination address.
We confirmed SRv6 endpoint processed the packets using one of the designated behaviors: End.DT4 with NEXT-CSID, End.DT6 with NEXT-CSID, or End.DT46 with NEXT-CSID.

Figure 92

Figure 92:Global Routing Table over SRv6

ABRPERoute ReflectorTraffic GeneratorTransit Node

Ericsson Router6671,
H3C CR16003E-F,
Huawei NetEngine A821,
Juniper PTX10002-36QDD,
Nokia 7750 SR-1

H3C CR16000-M1A,
H3C CR16003E-F,
Huawei ATN 910D-A,
Huawei NetEngine A821,
Juniper ACX7509,
Juniper MX204,
Juniper MX304,
Juniper PTX10002-36QDD,
Keysight IxNetwork,
Nokia 7250 IXR-e2,
Nokia 7750 SR-1

Juniper PTX10002-36QDDKeysight IxNetworkArista 7280R3

Table 44: Global IPv4/IPv6 Routing Table  - µSID

Interested in our testing services?

If you are interested and would like to receive more information, please send us an email and sign up for our newsletter to stay up-to-date.