Welcome to the BIG-IP LTM VE forums

Thanks Treepose,

 

 

The netstat command revealed that the 172.16.X.X

 

management network was in the routing table, but only specified as a broadcast address 172.16.232.255 or a subnet; 172.16.232 /24

 

 

I'm obviously a networking newbie and don't know the correct interpretations for a lot of this information. Plus the VMware adds another layer of abstraction to straighten out. For example, the 172.16.232.128 (my management IP) should only exist with the virtual emulation, but my router has to know it's there in order for my browser to communicate with it. Is there a way to do that? For now, all I can do is access the GUI through the internal self IP (which I know is not recommended) .

 

 

What's setting me back even worse is that "b reset" - to wipe out all my settings and start from scratch - is registering as an invalid command. But again, maybe this is an artifact of working with a simulation and not the real thing. Nonetheless - it's nice to have an BIG IP to poke around on !

 

 

I'm suspecting the problem might have something to do with the way I set up my host (Using a real qualified domain from dynDNS the first time. Now I'm using a dummy domain, but maybe it doesn't matter). My original BIG IP VE setup had a management IP that was actually accessible..... BUT - none of the pool members were reachable !

 

 

Living and learning.