(Optional) Configuring Inter-AS Static Traversal
When a BIERv6 network is deployed across ASs, static BFR-neighbors need to be configured so that static BIERv6 BIFT entries are generated. These entries enable traversal to be implemented if BIERv6-incapable nodes exist on an inter-AS path, as long as these nodes support IPv6 unicast forwarding.
Context
Figure 1 shows the networking of inter-AS static traversal. In the networking, a BIERv6 next-hop neighbor needs to be manually set for the upstream node of each BIERv6-incapable node. This allows this upstream node to generate a BIERv6 BIFT entry. Currently, the End.BIER SID of a BIERv6-capable next hop can be set based on a specific range of BFR-IDs corresponding to the destination nodes of multicast packets. For example, on PE1, ASBR2's End.BIER SID is manually set as the next hop for the multicast packets destined for PE2 (with BFR-ID 2) and PE3 (with BFR-ID 3).
Procedure
- Run system-view
The system view is displayed.
- Run bier
BIER is enabled, and the BIER view is displayed.
- Run sub-domain sub-domain-val ipv6
The sub-domain view is displayed.
- Run protocol static-bift
Static BIFT-based forwarding is enabled.
- Run bfr-neighbor end-bier ipv6-address bfr-id bfrid-start [ to bfrid-end ]
The End.BIER SID of a BIERv6-capable next hop is set based on a specific range of BFR-IDs corresponding to the destination nodes of multicast packets.
If the BFR-IDs of the destination nodes are in multiple ranges, repeat this command until all the BFR-IDs are specified.
- Run quit
Exit the sub-domain view.
- Run quit
Exit the BIER view.
- Run commit
The configuration is committed.
- (Optional) Repeat 1 to 8 if a BIERv6-incapable node to be traversed has multiple nodes upstream.