Support for BGP-4++

Gaia Embedded implements BGP-4++ to support multiprotocol extensions.

You must use an IPv4 address for the router ID (BGP identifier). After the BGP session is completed, you can advertise and withdraw prefixes by sending normal "UPDATE" messages that include one or both of the new multiprotocol attributes "MP_REACH_NLRI" (advertises reachability of routes) and "MP_UNREACH_NLRI" (withdraws routes).

The new attributes are backward compatible. If two routers have a BGP session and only one supports the multiprotocol attributes, they can still exchange unicast IPv4 routes.

On each peer you configure the type of routes (capability) that should be exchanged between peers. Choose this selection:

• IPv4 unicast (the default)

To establish peering, the routers must share a capability.

Note - Do not use the route redistribution and inbound filter pages of the Portal to configure routing policies for BGP-4++. Use the route map commands in the CLI.