Forum Discussion
Nimbostratuswhy big ip needs to access hosts of vlan for which it ask a self ip.
i know that management ip is different from self ip. management ip is required to connect the appliance through internet and performing updates and changes to the appliance.and self ip is required to access the host in a particular vlan.so my question is that why it needs to access the host of the vlans? correct me if i am wrong. when the request arrives at big ip , according to the algorithm it distributes the load backend servers so where does the vlan and self ip concept arrives
- MvdG
Cirrus
Hi,
The BIG-IP act as a full proxy. So there are two TCP connections. One at the client side and one at the (backend) server side.
So the TCP connection at the server side comes from the self-IP of the server VLAN. In a cluster setup, this TCP connections comes from the float-IP.
To monitor backend servers, you can add a monitor to a pool and nodes. This monitor traffic comes from the self-ip address of the BIP-IP.
Hopes this helps.
Martijn
mukulthanks a lot for your time. i've got it a little bit but could be more elaborating.?plz
as per my understanding i've drawn this diagram and i think to access those each servers in different vlans it needs a self ip. but cannot it communicate with those servers with its own management ip.
Martijn_144688Cirrostratus
Hi,
The BIG-IP act as a full proxy. So there are two TCP connections. One at the client side and one at the (backend) server side.
So the TCP connection at the server side comes from the self-IP of the server VLAN. In a cluster setup, this TCP connections comes from the float-IP.
To monitor backend servers, you can add a monitor to a pool and nodes. This monitor traffic comes from the self-ip address of the BIP-IP.
Hopes this helps.
Martijn
- mukul
thanks a lot for your time. i've got it a little bit but could be more elaborating.?plz
as per my understanding i've drawn this diagram and i think to access those each servers in different vlans it needs a self ip. but cannot it communicate with those servers with its own management ip.
Kalo_52732Altocumulus
maybe you're confusing data-plane and control-plane. self-ips and vlans resides on the data-plane, it handled by tmmd(bigip traffic management daemon, in short). tmm caliculates nat, snat and floating objects etc... and the management-ip resides on the control-plane, it handled by linux ( generic ethernet0). Load balancing algorithms will run at data-plane only, not the manamement segment(control-plane). so, looking at your diag, you have to create one more vlan and self-ip, then deploy a client on that segment.
- mukul
thanks kalo for sharing your knowledge with me.
