Forum Discussion

jkrumenacher_13's avatar
jkrumenacher_13
Icon for Nimbostratus rankNimbostratus
May 13, 2014

Self IP not functioning

I have a 3 node Viprion cluster. Node 2 does not talk out its interface. I failed over the traffic group that uses this vlan to node 1 and now the health checks work, pings to the server, default gateway, etc. I have created many vlans, so I have those to compare to, but I must just be overlooking something. On the host the vlan is created and assigned to an interface. The guest list has the newly created vlan selected. The guests have the vlan created, and the self IP and Float created on each. Node 1 (10.10.10.1 vlan11) can ping the float, node 3 (10.10.10.3), a VS on that vlan and the router (10.10.10.10) on that vlan. (node 3 as well). The L2 connected router has arp entries for node 1, 3, a VS and a SNAT.

 

Node3 can only ping itself. ifconfig shows that vlan interface

 

I forced the traffic group over so I could delete the vlan self IPs and recreate them with no better results.

 

Any other thoughts to help break this down would be great.

 

Thanks jkrum

 

2 Replies

  • I would need to see your selfip, vlan, interface, VS configuration to be able to offer up better assistance. But in general, you want to make sure your vlans, vlan tags and associated interfaces are the same on all 3 devices. then, make sure each device has it's own self ip in the appropriate subnet. Then, make sure there's a floating self IP for each traffic group.

     

    Validate under Device Management, then traffic groups in the GUI, that the associated IP addresses for these floating IP's show up in the correct traffic group.

     

  • James, Thanks for the reply. I did open a case with F5 and they believe that I need to restart mcpd. I have that scheduled for tonight. I installed a 45day compression eval license on each host and with that I have experienced sync issues, and this interface issue, along with an solarwinds alert falsely stating a guest going active / standby. I will close this after my restart.

     

    Thanks, jkrum