Forum Discussion

9 Replies

    • I'm familiar with admin sections for Device Management > Devices , Device Groups .. but I'm not seeing how to configure FIP ... perhaps it's there but I'm not seeing it
    • nitass_89166's avatar
      nitass_89166
      Icon for Noctilucent rankNoctilucent
      you just assign non-local traffic group (e.g. traffic-group-1) to floating object (e.g. selfip, virtual server ip).
    • sorry to be dense but i don't see a virtual-server with ip corresponding to the fip for our traffic-group ... our traffic-group has two devices with ips 192.168.220.220,221 ... by inspection, fip 192.168.220.222 directs traffic to active device .. but there is no virtual-server with ip 192.168.220.222 ... i'm just not seeing where fip is configured
  • isn't it normal ha configuration e.g. device-group, traffic-group, etc?

     

    • I'm familiar with admin sections for Device Management > Devices , Device Groups .. but I'm not seeing how to configure FIP ... perhaps it's there but I'm not seeing it
    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      you just assign non-local traffic group (e.g. traffic-group-1) to floating object (e.g. selfip, virtual server ip).
    • sorry to be dense but i don't see a virtual-server with ip corresponding to the fip for our traffic-group ... our traffic-group has two devices with ips 192.168.220.220,221 ... by inspection, fip 192.168.220.222 directs traffic to active device .. but there is no virtual-server with ip 192.168.220.222 ... i'm just not seeing where fip is configured
  • Hi Baltostar,

    on CLI you can check for floating self IPs with the following command (single-line output, filters "floating enabled" and prints strings 3 [name] and 6 [address/mask]):

    tmsh list net self one-line | awk '/floating.enabled/ {print $3, $6}'
    

    In WebUI the floating self IPs should be listed in Failover Objects of your traffic-group-1 or other traffic-groups you have added. Of course they will show up as well in the list of self IPs not belonging to "traffic-group-local-only" as in nitass screenshot.

    To create a floating self IP requires to already have a non-floating self IP in the related VLAN.

    tmsh create net self self_float_175 address 10.131.131.176/24 vlan vlan_prod_131 allow-service none traffic-group traffic-group-1
    

    The example above creates a new floating self IP in traffic-group-1. If you don´t set the traffic-group parameter it will be a non-floating self IP and assigned to the traffic-group-local-only.

    Thanks, Stephan