Forum Discussion
Well no... the "physical" interfaces are assigned at the hypervisor, and Big-IP sees them as eth0, eth1, etc. This part is standard Linux stuff. It looks like TMM creates other interfaces to ride on top of those.
For example, I created a Big-IP VE in my lab and gave it three interfaces, and I can see them as eth0, eth1, and eth2. Then I see additional interfaces that TMM must be managing: tunl0, mgmt_bp, tmm0, internal, external, socks-tunnel, and http-tunnnel (whew).
Problem is, Navisite only gives me one interface (eth0). I have to assign that to Management so I can get in. So I was hoping to fake a new interface by piggybacking on the one I have.
BigIP supports VLAN tagging, but Navisite doesn't support that either. So I was hoping to fake an eth1 interface by using an alias on eth0. I created an alias (eth0:0) but TMM doesn't see it.
So I was wondering how TMM knows interfaces are there. Is there is a file I can create to fake a new eth1 and point it to eth0:0? Or maybe there some magic I can add to bigip_base.conf to do the same thing?
If I can't make this work, they will probably make me use Netscaler... and no one wants that. :P