Introduced : BIG-IP_v11.0.0
The RouteDomainterface enables you to work with the definitions and
attributes contained in a device&aposs route domains. Route domains
allow you to specify overlapping IP addresses for different objects in
the system. This allows a service provider, for example, to have two
different pool members at 10.10.10.1 that represent completely
different real servers. The addresses for the two pool members might
be 10.10.10.1%1 and 10.10.10.1%2 where the numbers after the percent
signs are numeric ids of route domains. Note that the source and
destination addresses in the firewall methods (get_fw_rule and so on)
are type Common::NetAddress, a type which allows one to specify a
prefix length after the address, e.g., “10.1.1.0/24” or
||An enumeration of routing protocols which are supported for dynamic routing. On a system which is licensed to support dynamic routing, each routing protocol can be individually enabled or disabled on a per route domain basis. This is achieved by adding or removing routing protocols to/from the route domain question.
||A sequence of routing protocol types.
||RoutingProtocol  
||Alias for sequence of routing protocol sequences.
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor
or control community code contributions. We make no guarantees or warranties regarding the available code,
and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any
code available in the BIG-IP API reference guides is solely at your own risk.