Basic IPv6 BGP example | Administration Guide (2024)

In this example, Enterprise Core FortiGate peers with the ISP BGP Router over eBGP to receive a default route.

Topology

The following topology is used for this example:

Basic IPv6 BGP example | Administration Guide (1)

Basic IPv6 BGP example | Administration Guide (2)

Please note that the IPv6 addresses used in this example are for illustrative purposes only and should not be used in your environment.

The 2001:db8::/32 prefix is a special IPv6 prefix designated for use in documentation examples. See RFC 3849 for more information.

Basic IPv6 BGP example | Administration Guide (3)

Please note that the Autonomous System Numbers (ASN) used in this example are reserved for documentation use only and should not be used in your environment. See RFC 5398 for more information.

To configure BGP on the Enterprise Core FortiGate in the GUI:
  1. Go to Network > BGP.

  2. Set Local AS to 64511.

  3. Set Router ID to 13.13.13.13.

  4. In the Neighbors table, click Create New and set the following:

    IP 2001:db8:d0c:6::2
    Remote AS 64510
  5. Click OK.

  6. Under IPv6 Networks, set IP/Netmask to 2001:db8:d0c:6::/64.

  7. Click Apply.

To configure BGP on the Enterprise Core FortiGate in the CLI:
config router bgp set as 64511 set router-id 13.13.13.13 config neighbor edit "2001:db8:d0c:6::2" set remote-as 64510 next end config network6 edit 1 set prefix6 2001:db8:d0c:6::/64 next endend

Testing the configuration

To verify the status of the neighbors:
# get router info6 bgp neighborsVRF 0 neighbor table:BGP neighbor is 2001:db8:d0c:6::2, remote AS 64510, local AS 64511, external link BGP version 4, remote router ID 1.1.1.2 BGP state = Established, up for 02:43:35 Last read 00:00:14, hold time is 180, keepalive interval is 60 seconds Configured hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: Route refresh: advertised and received (old and new) Address family IPv4 Unicast: advertised and received Address family VPNv4 Unicast: advertised and received Address family IPv6 Unicast: advertised and received Address family L2VPN EVPN: advertised and received Received 263 messages, 0 notifications, 0 in queue Sent 260 messages, 1 notifications, 0 in queue Route refresh request: received 0, sent 0 NLRI treated as withdraw: 0 Minimum time between advertisem*nt runs is 30 seconds For address family: IPv4 Unicast BGP table version 1, neighbor version 0 Index 1, Offset 0, Mask 0x2 Community attribute sent to this neighbor (both) 0 accepted prefixes, 0 prefixes in rib 0 announced prefixes For address family: VPNv4 Unicast BGP table version 1, neighbor version 0 Index 1, Offset 0, Mask 0x2 Community attribute sent to this neighbor (both) 0 accepted prefixes, 0 prefixes in rib 0 announced prefixes For address family: IPv6 Unicast BGP table version 3, neighbor version 2 Index 1, Offset 0, Mask 0x2 Community attribute sent to this neighbor (both) 3 accepted prefixes, 3 prefixes in rib 1 announced prefixes For address family: L2VPN EVPN BGP table version 1, neighbor version 1 Index 1, Offset 0, Mask 0x2 Community attribute sent to this neighbor (both) 0 accepted prefixes, 0 prefixes in rib 0 announced prefixes Connections established 2; dropped 1Local host: 2001:db8:d0c:6::1, Local port: 179Foreign host: 2001:db8:d0c:6::2, Foreign port: 16500Egress interface: 9Nexthop: 13.13.13.13Nexthop interface: port3Nexthop global: 2001:db8:d0c:6::1Nexthop local: fe80::20c:29ff:fefc:1868BGP connection: shared networkLast Reset: 02:43:42, due to BGP Notification sentNotification Error Message: (CeaseUnspecified Error Subcode)
To verify the networks learned from neighbors or a specific network:
# get router info6 bgp networkVRF 0 BGP table version is 3, local router ID is 13.13.13.13Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S StaleOrigin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight RouteTag Path*> ::/0 2001:db8:d0c:6::2(fe80::20c:29ff:febc:eec2) 0 0 0 64510 ? <-/1>*> 64:ff9b::/96 2001:db8:d0c:6::2(fe80::20c:29ff:febc:eec2) 0 0 0 64510 ? <-/1>* 2001:db8:d0c:6::/64 2001:db8:d0c:6::2(fe80::20c:29ff:febc:eec2) 0 0 0 64510 i <-/->*> 100 32768 0 i <-/1>Total number of prefixes 3
To verify the routing table:
# get router info6 routing-tableIPv6 Routing TableCodes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, B - BGP, V - BGP VPNv6 * - candidate defaultTimers: UptimeRouting table for VRF=0B* ::/0 [20/0] via fe80::20c:29ff:febc:eec2, port3, 02:45:56, [1024/0]C ::1/128 via ::, root, 03:45:04B 64:ff9b::/96 [20/0] via fe80::20c:29ff:febc:eec2, port3, 02:45:56, [1024/0]C 2001:db8:d0c:1::/64 via ::, port1, 00:33:21O 2001:db8:d0c:2::/64 [110/2] via fe80::20c:29ff:fe4d:f81f, port1, 00:33:04, [1024/0] [110/2] via fe80::20c:29ff:fe6b:b2c9, port2, 00:33:04, [1024/0]C 2001:db8:d0c:3::/64 via ::, port2, 03:45:04O 2001:db8:d0c:4::/64 [110/2] via fe80::20c:29ff:fe4d:f81f, port1, 00:33:04, [1024/0]O 2001:db8:d0c:5::/64 [110/2] via fe80::20c:29ff:fe6b:b2c9, port2, 02:51:32, [1024/0]C 2001:db8:d0c:6::/64 via ::, port3, 03:45:04
Basic IPv6 BGP example | Administration Guide (2024)
Top Articles
Latest Posts
Article information

Author: Allyn Kozey

Last Updated:

Views: 5856

Rating: 4.2 / 5 (43 voted)

Reviews: 82% of readers found this page helpful

Author information

Name: Allyn Kozey

Birthday: 1993-12-21

Address: Suite 454 40343 Larson Union, Port Melia, TX 16164

Phone: +2456904400762

Job: Investor Administrator

Hobby: Sketching, Puzzles, Pet, Mountaineering, Skydiving, Dowsing, Sports

Introduction: My name is Allyn Kozey, I am a outstanding, colorful, adventurous, encouraging, zealous, tender, helpful person who loves writing and wants to share my knowledge and understanding with you.