Forum Discussion

Colin_Walker_12's avatar
Colin_Walker_12
Historic F5 Account
Feb 15, 2010

Welcome to the BIG-IP LTM VE forums

Thanks for checking out the forums for the BIG-IP LTM VE. This is where you can come to discuss your experiences with LTM VE, ask questions of others that are using it, share suggestions, and look fo...
ve
virtualization
net_enthused_25's avatar
net_enthused_25
Icon for Nimbostratus rankNimbostratus
Mar 09, 2010
Thanks qe,

 

 

I can get into the BIGIP GUI at 192.168.1.245 as you suggested. But this amounts to logging into the internal self-IP ( at .245) and using it as a management port.

 

 

And now I can even get my pool members up and running. You would think that it would be better to stay out of the 192.168 network to avoid conflicts. However, I can't seem to get into the BIGIP GUI when I use an automatically designated mgmt IP, such as 172.16.X.X.

 

 

Moreover, the only time I can get *any* communication with the BIG IP (pool members, mgmt, VIPs, you name it ) is if I stay on my own actual subnet of 192.168.1.X.

 

 

I get the feeling that this is not as it should be.

 

 

A router issue ? Or perhaps is the VMware (Fusion) complicating things?