New Gaia Dynamic Routing features by release
- Protocol Restart for BGP and OSPF
- Protocols can be restarted via WebUI or clish
- PBR in VSX
- Enables users to configure PBR rules and tables in a VS Context
- BGP Enhanced Route Refresh
- Enables support for Enhanced Route Refresh as per RFC 7313
- Gets enabled automatically when route-refresh is enabled
- IP Reachability MultiHop detection with ICMP and BFD:
- Multihop Ping and Multiple ISPs in Policy-Based Routing.
- Multihop Ping in Static Routes.
- BFD in Static Routes.
- VSX VSID in Netflow.
- OSPF v2/v3 Multiple Instances
- BGP IPv6 MD5
- OSPFv3 support in ClusterXL including Link-Local VIP
- BFD support for BGP and OSPF (IPv4 and IPv6)
R80.10 Advanced Routing and Clustering Enhancement Hotfix (which installs over R80.10) includes these same R80.20 Dynamic Routing features (along with R80.20 ClusterXL features). For more information about this hotfix, see sk122654.
- BGP 4-Byte AS Number
- Local AS Number
- AS Override
- IPv6 DHCP Relay
- IPv6 RIPng with VRRPv3
- Route Redistribution and inbound Route Filtering CLI
- OSPF Forced Hello
- ECMP for iBGP
- SNMP for RIP, OSPF, BGP, PIM, VRRPv2 (IPv4 only)
- Show Config for BGP and Route Redistribution
- BGP route filtering and AS range
- BGP communities regexp
- OSPF Graceful Restart (supported for IPv4 with VRRP-only). In R80.20 IPv6, VSX and ClusterXL have been added.
- OSPFv2 and ClusterXL inter-monitoring (supported for IPv4, single Security Gateway, VSX and ClusterXL. In R80.20 IPv6, VSX and ClusterXL have been added.
- Static Multicast Routes (supported for IPv4, single Security Gateway, VSX, VRRP cluster, and ClusterXL. (IPv6 is not supported).
- Routing configuration support in Gaia Cloning Groups (cadmin).
- PBR with Destination Port and Service - see sk100500 (supported for IPv4, single Security Gateway, ClusterXL and VRRP. (IPv6 and VSX are not supported).
New and improved handling of DHCP.
See sk98839 for more information on procedures for setting up DHCP on Security Gateway, including:
- DHCP Relay
- DHCP Server
- DHCP Relay + DHCP Server
Legacy DHCP configuration (as supported in versions R77.10 and lower) can also be used on R77.20, if needed.
- BGP Graceful Restart (IPv4 and IPv6, Security Gateway mode and VSX mode)
- BGP ECMP (IPv4 and EBGP only, Security Gateway mode and VSX mode)
- BGP Nexthop (Peer) monitoring (IPv4 and IPv6, Security Gateway mode and VSX mode)
- Netflow support for VSX
- ping6 for IPv6 Static Routes
- Configuration of VRRP SNMP traps
- Stability and Usability fixes
- OSPF Tag Matching
- Support for DNS option in IPv6 Router Advertisements
- SNMP OIDs for VRRPv2
- Routing configuration support in Gaia Cloning Groups (cadmin)
Feature Support as of R80.20 Release
Refer to sk105170 - Configuration requirements / considerations and limitations for VRRP cluster on Gaia OS
Routing How-To Documents:
DHCP / DHCP Relay:
IP Broadcast Helper
Routing Policy Configuration
Policy Based Routing
General Limitations and Notes regarding Dynamic Routing and VRRP (for per-release limitations, see the release notes for your chosen release)
The two methods have different capabilities and different levels of integration with protocol-specific features. Routemaps are generally more capable but require all granularity to be configured within them. Also, if a Routemap is associated with a protocol (RIP/OSPF/BGP), it will take precedence over any Route Redistribution/Inbound Route Filters/protocol-specific features.
Route Redistribution can used to advertise certain routes with a specific MED to all BGP peers belonging to the same AS. Peer-specific configuration (med-out) can be used to advertise a different MED to one or more peers within the same AS. For those peers, med-out replaces the MED configured via Route Redistribution.
If a Routemap is also configured to advertise routes to BGP peers within the same AS, all Route Redistribution and peer-specific configuration is ignored.The Routemap must be configured completely to ensure that the required routes are advertised to all the peers with the MED desired.A peer-specific Routemap would need to be configured to advertise a different MED to a specific peer (see sk110477).