Forum Discussion

3 Replies

  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus

    Reasonably easy, but it has some weird effects for the admin.

     

    First, choose an ID. (integer). And a name... And create a RouteDomain (Under Networks in the GUI).

     

    Then assign VLANs to it... Then configure all the normal stuff... e.g. Virtual Servers etc... You assign IP's (And therefore VS's, nodes etc) by appending the route domain ID to the IP address. e.g. for RD 41 and the IP 192.168.1.1, you'd create it as 192.168.1.1%41

     

    That's pretty much all there is to it. The subtleties are in getting your SNATs, NAT's, VS etc in the correct RD first up. Because as with a lot of things, it's a right pain to change it afterwards (e.g. Moving stuff between RD's if you create it wrong. So many things WON'T sync between cluster members if you do a lot of config and then expect to be able to sync afterwards).

     

    H

     

  • For version 11.4.x, here is a link to the implementation guide: http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-implementations-11-4-0/13.htmlconceptid

     

  • Thanks for the information, it is really helpful. Is there special consideration for HA cluster failover with routed domain?