11 Ebgp Peerings for Ipv6

Understanding Multiprotocol BGP (MP-BGP)

RFC 4760: Defines Multiprotocol Extensions for BGP-4.
- Previous RFCs: RFC 2283 (Feb 1998 - Original), RFC 2858 (Jun 2000).
- Current Standard: RFC 4760 (Jan 2007).
IPv6 Support: RFC 2545 introduces the use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing.
- RFC 2545: Published in Mar 1999 and remains current.
New Attributes: MP-BGP introduces two new attributes, MP_REACH_NLRI and MP_UNREACH_NLRI, to support multiprotocol routing.

Directly Connected Neighbors: The same considerations as in IPv4 apply to MP-BGP.
Non-Directly Connected Neighbors: Similar considerations to IPv4 apply.
- Configuration Options: To establish connections with non-directly connected neighbors, options like ebgp-multihop or disable-connected-check (a Cisco best practice) are required.
- Update Source Matching: The update source must match the neighbor statement.

fe80::/10 Address Space: MP-BGP uses the fe80::/10 address space for IPv6 link-local addressing.
- Defined in RFC 4291.
Not Routable on the Internet: These addresses are not publicly routable on the global Internet.
Security Consideration: Proper security measures are essential when using IPv6 link-local addressing in MP-BGP.

Validation Commands: eBGP validation and verification in the context of MP-BGP can be achieved using commands such as:
- show bgp ipv6 unicast summary: Provides a summary of BGP information for IPv6 unicast routes.
- show bgp ipv6 unicast neighbor [neighbor IP]: Displays details of a specific BGP neighbor for IPv6 unicast routes.

Understanding Multiprotocol BGP (MP-BGP) and its application in both IPv4 and IPv6 is crucial for enabling multiprotocol routing in your network.