New Gaia Dynamic Routing features by release

R81

• OSPFv3 AH authentication - support authentication for OSPFv3 protocol security
• IPv6 route aggregation - support aggregating routes in order to reduce the number of prefixes advertised to neighbor routers thus improving performance and scaling
• IPv4 NAT-pool routes - support NAT with routing by configuring and redistributing NAT-pool routes to routing protocols
• RIP route sync - re-implement RIP route sync in the standard way like the other routing protocols
• PIM restart - adds PIM to protocols which have user restarts
• BGP Support for VxLAN interfaces
• Dynamic Routing support for GRE interfaces

R80.40

• 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

R80.30

• 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.

R80.20

• AllowAS-in-count
• 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.

R80.10

• 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

 

R77.30

• 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).

 

R77.20

• 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)

 

R77.10

• 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

 

R77

• SNMP OIDs for VRRPv2
• Routing configuration support in Gaia Cloning Groups (cadmin)

 

Feature Support as of R80.20 Release

Routing:

Routing Protocols
Gateway Mode	VSX Mode
OSPF OSPF IPv6 clusterXL and VRRPv3 OSPF IPv4: OSPFv2 (RFC 2328), VRRPv2 and ClusterXL Intermonitoring with ClusterXL added in R77.30 OSPFv2/v3 with Multiple Instances BFD support (OSPFv2/v3)	OSPF OSPFv2 (IPv4) and OSPFv3 (IPv6)  ClusterXL only (VRRP is not supported) Numbered warp interfaces are not supported. Intermonitoring with ClusterXL added in R77.30 OSPFv2/v3 with Multiple Instances BFD Support (OSPFv2/v3)
BGP BGP IPv4: (RFC 1771) VRRPv2 and ClusterXL BGP IPv6: Multiprotocol Extension Capability, VRRPv3 only (ClusterXL is not supported) BGP IPv6 MD5 authentication supports 4-byte AS Number, local-AS and AS-override, AllowAS-in-count, BFD support (IPv4, IPv6)	BGP BGP IPv4 and IPv6 ClusterXL only (VRRP is not supported) BGP IPv6 MD5 authentication supports 4-byte AS Number, local-AS and AS-override, AllowAS-in-count. BFD support (IPv4, IPv6)
PIM (RFC 4601 and RFC 3973) PIM IPv4: Sparse Mode, Dense Mode, Source Specific Multicast, IGMPv2, IGMPv3, VRRPv2 and ClusterXL PIM IPv6: Not supported	PIM (RFC 4601 and RFC 3973) PIM IPv4: Sparse Mode, Dense Mode, Source Specific Multicast, IGMPv2, IGMPv3, ClusterXL only (VRRP is not supported) Numbered warp interfaces are not supported. PIM IPv6: Not supported
RIP RIP IPv4: VRRPv2 and ClusterXL RIPng for IPv6: supported as of R80.10	RIP RIP IPv4: ClusterXL only (VRRP is not supported) Numbered warp interfaces are not supported. RIPng for IPv6: not supported
Policy-Based Routing (PBR) PBR IPv4: Based on Source IP, Destination IP and Interface. ECMP is supported. VRRPv2 and ClusterXL are supported. Destination Port and Protocol are supported as of R77.30 PBR IPv6: Not supported Note – PBR does not work with ISP redundancy	Policy-Based Routing (PBR) PBR IPv4: Based on Source IP, Destination IP and Interface. ECMP is supported. ClusterXL only is supported (VRRP is not supported). PBR IPv6: Not supported PBR with Destination Port and Protocol are not supported in VSX mode due to configuration limitation
Routing Applications (supported on all protocols, exceptions are noted)
Gateway Mode	VSX Mode
IP Broadcast Helper (IPv4 only)	IP Broadcast Helper (IPv4 only)
DHCP Relay (IPv4 and IPv6)	DHCP Relay (IPv4 and IPv6)
Router Discovery (IPv4 and IPv6) Note: IPv6 Router discovery works on Single gateway and in CLusterXL.   IPv4 Router discovery Not supported in ClusterXL; supported only on single Security Gateway, or in VRRP cluster.	Router Discovery (IPv4 and IPv6) IPv6 Router Discovery is supported in ClusterXL and with VSX.   Note: IPv4 Router Discovery Not supported in ClusterXL (supported only on single VSX Gateway)
Inbound Route Filtering IPv4: All protocols IPv6: All protocols	Inbound Route Filtering IPv4: All protocols IPv6: All protocols
Route Redistribution (IPv4 and IPv6)	Route Redistribution (IPv4 and IPv6)
Route Aggregation (IPv4 only)	Route Aggregation (IPv4 only)
ICMP (IPv4 and IPv6)	ICMP (IPv4 and IPv6)
ECMP (IPv4 only) OSPF BGP (eBGP as of R77.10, iBGP as of R80.10)	ECMP (IPv4 only) OSPF BGP (eBGP as of R77.10, iBGP as of R80.10)
Graceful Restart Helper (IPv4 and IPv6)  BGP IPv4/IPv6 and OSPFv2/v3 supported Graceful Restart Restarter (IPv4 and IPv6) BGP IPv4/IPv6 and OSPFv2/v3 are not supported on GW mode	Graceful Restart Helper (IPv4 and IPv6) BGP IPv4/IPv6 and OSPFv2/v3 supported Graceful Restart Restarter (IPv4 and IPv6) BGP IPv4/IPv6 and OSPFv3 supported OSPFv2 is not supported on VSX mode only on VRRP
Static Multicast Routes as of R77.30 (IPv4, VRRP and Cluster XL supported)	Static Multicast Routes as of R77.30 (IPv4, Cluster XL supported)

 

VRRP

Refer to sk105170 - Configuration requirements / considerations and limitations for VRRP cluster on Gaia OS

Gateway Mode	VSX Mode
IPv4: VRRPv2 - Supports Monitored Circuits, Non-preempt, Auto-deactivation, Simplified VRRP Configurations (MCVR) RIP OSPF OSPFv2 Graceful restart BGP PIM IPv6: VRRPv3 - Supports Monitored Circuits, Non-preempt. OSPFv3 BGP with multiprotocol support RIPng (R80.10) VRRPv3: PIM, Simplified VRRP Configuration and Auto-deactivation are not yet supported.	VRRP is not suppoted in VSX Mode. VSX uses ClusterXL only.

 

Routing How-To Documents:

OSPF

• sk98968 - OSPF on Gaia
• sk100502 - How to configure Equal Cost Multipath (ECMP) over OSPF on Gaia OS

BGP

• sk95967 - BGP on Gaia OS
• sk100499 - BGP on Gaia OS - configuring Graceful Restart
• sk100504 - How to configure Equal Cost Multipath (ECMP) over eBGP on Gaia

PIM

• sk100239 - How to configure PIM on Gaia OS

DHCP / DHCP Relay:

• sk98839 - Configuration of IPv4 BOOTP/DHCP Relay using legacy services
• sk104114 - Configuration of IPv4 BOOTP/DHCP Relay using new services

IP Broadcast Helper

• sk98810 - How to configure IP Broadcast Helper on Gaia OS

Routing Policy Configuration

• sk98936 - How to configure route redistribution and inbound route filters in Gaia Portal
• sk100501 - How to configure Routemaps in Gaia Clish

Policy Based Routing

• sk167135 - Policy-Based Routing and Application-Based Routing in Gaia

General Limitations and Notes regarding Dynamic Routing and VRRP (for per-release limitations, see the release notes for your chosen release)

• Use of Advanced VRRP Configuration in cases of multiple VRRP interfaces: Use of Advanced VRRP configuration is recommended when there are many VRRP interfaces (> 10). Use of VRRP (a.k.a. "mcvr") may result in very slow response in configuring due to the large number of VRRP configuration bindings.
  
  

• Route Redistribution and Inbound Router Filters vs. Routemaps:

  There are two ways to configure routing policy
  • Route Redistribution and Inbound Router Filters (WebUI-only prior to R80.10; CLI available from R80.10)
  • Routemaps (CLI only)

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.

For example:

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).