Using the neighbor next-hop-self command on the route reflector will modify next hop attributes only for routes that are learned from eBGP peers and not the intended routes that are. BGP has a number of custom roles that routers can fill. Do not use the neighbor next-hop-self command to modify the next hop attribute for a route reflector when this feature is enabled for a route reflector client. Role of routers in BGP networksĭynamic routing has a number of different roles that routers can fill. For more information about IPv6 BGP keywords, see the FortiSwitchOS CLI Reference. The main CLI keywords have IPv6 equivalents that are identified by the “6” on the end of the keyword, such as config network6 or set allowas-in6.

BGP and IPv6įortiSwitch units support IPv6 over BGP using the same config router bgp CLI command as IPv4 but different subcommands. When determining your network topology, note that the number of available or supported routes is not set by the configuration but depends on the available memory on the FortiSwitch units. Some parts of BGP are not explained here because they are common to other dynamic routing protocols. In a BGP network, there are some terms that need to be explained before going ahead. BGP enabled more networks to take part in the Internet backbone to effectively decentralize it and make the Internet more robust, and less dependent on a single ISP or backbone network. It was designed to replace the old Exterior Gateway Protocol (EGP) which had been around since 1982, and was very limited. It was introduced in RFC 2858 and RFC 2545.īGP is the routing protocol used on the Internet. Other routing protocols use UDP.īGP makes routing decisions based on path, network policies, and rulesets instead of the hop-count metric as RIP does, or cost-factor metrics as OSPF does.īGP-4+ supports IPv6. BGP is the only routing protocol to use TCP for a transport protocol. The main benefits of BGP-4 are classless inter-domain routing and aggregate routes.

That RFC has since been replaced by RFC 4271. The current version, BGP-4, was released in 1995 and is defined in RFC 1771. FortiSwitch units support iBGP, and eBGP only for communities.īGP was first used in 1989. eBGP is used to connect many different networks together and is the main routing protocol for the Internet backbone. iBGP is intended for use within your own networks. NOTE: You must have an advanced features license to use BGP routing.īorder Gateway Protocol (BGP) contains two distinct subsets: internal BGP (iBGP) and external BGP (eBGP). BGP routing | FortiSwitch 6.4.3 | Fortinet Document Library

Route reflector client