cancel
Showing results for 
Search instead for 
Did you mean: 

Need Help on Configuring Virtual Server

ShankarA_326137
Nimbostratus
Nimbostratus

Hi,

 

I have downloaded virtual appliance (BIG IP VE) from F5 Big IP site and installed on my Vmware fusion. I was able to access the console (mgmt 10.0.3.82) and created internal(10.0.4.100) and external (10.0.5.100) network. Also, crated nodes and pool. So far so good.

 

Now, when I am configuring virtual server - I am little bit confused or don't know what value should I be using for destination address?. For source address I have (0.0.0.0/0) this so pretty much I accept everything here.

 

I have gone through many videos on the Internet and no one clearly explains the Virtual Server IP address and from where did they get this IP. Since I am using a virtualised environment (VMWARE fusion), what could be the external network here? I am trying to have a LB forward port 80 requests to my backend web servers running on port 80.

 

Can someone please shed some light?

 

Thanks Shankar

 

7 REPLIES 7

habib_Khan
Nimbostratus
Nimbostratus

Destination IP address is nothing but that virtual IP you use to access the application. As its Virtual Edition , if its LAB make sure you have reach ability to network segment/subnet you define for LB VIP and selfip's should have reach ability to Pool members/Nodes.

 

ShankarA_326137
Nimbostratus
Nimbostratus

Hi Habib,

 

yes, this is kind of LAB setup. The IP which I've used in pool (pool member 10.0.3.84 on port 80) was accessible fine (ex: http://10.0.3.84). I got stuck up at virtual server end. I tried using the virtual server IP as 10.0.5.101 and the virtual server status shows green. But when I tried to access http://10.0.5.101 that did not work. I should get a apache web page but instead I got page not found error. What am I doing wrong?

 

ifconfig on F5 device;

 

eth0 Link encap:Ethernet HWaddr 00:0C:29:78:7B:BF inet addr:10.0.3.82 Bcast:10.0.3.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe78:7bbf/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:67156 errors:0 dropped:0 overruns:0 frame:0 TX packets:16380 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15557179 (14.8 MiB) TX bytes:2772795 (2.6 MiB) eth2 Link encap:Ethernet HWaddr 00:0C:29:78:7B:D3 inet6 addr: fe80::20c:29ff:fe78:7bd3/64 Scope:Link UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:261714 errors:0 dropped:0 overruns:0 frame:0 TX packets:707 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:39288375 (37.4 MiB) TX bytes:55022 (53.7 KiB) eth3 Link encap:Ethernet HWaddr 00:0C:29:78:7B:DD inet6 addr: fe80::20c:29ff:fe78:7bdd/64 Scope:Link UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:262340 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:39342025 (37.5 MiB) TX bytes:4950 (4.8 KiB) external Link encap:Ethernet HWaddr 00:0C:29:78:7B:D3 inet addr:10.0.5.100 Bcast:10.0.5.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe78:7bd3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:36730 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3031044 (2.8 MiB) TX bytes:180 (180.0 b) internal Link encap:Ethernet HWaddr 00:0C:29:78:7B:DD inet addr:10.0.4.100 Bcast:10.0.4.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe78:7bdd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:36723 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3030624 (2.8 MiB) TX bytes:180 (180.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.255.255.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:72113 errors:0 dropped:0 overruns:0 frame:0 TX packets:72113 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14595136 (13.9 MiB) TX bytes:14595136 (13.9 MiB) lo:1 Link encap:Local Loopback inet addr:127.2.0.2 Mask:255.255.255.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 tmm Link encap:Ethernet HWaddr 00:98:76:54:32:10 inet addr:127.1.1.254 Bcast:127.1.1.255 Mask:255.255.255.0 inet6 addr: fe80::298:76ff:fe54:3210/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9282 Metric:1 RX packets:18467 errors:0 dropped:0 overruns:0 frame:0 TX packets:18521 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1020329 (996.4 KiB) TX bytes:8296771 (7.9 MiB) tmm_bp Link encap:Ethernet HWaddr 02:01:23:45:00:FE inet addr:127.20.0.254 Bcast:127.20.255.255 Mask:255.255.0.0 inet6 addr: fe80::1:23ff:fe45:fe/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Any ideas? thanks

habib_Khan
Nimbostratus
Nimbostratus

Hi Shankar,

 

1) Check if you are able to ping the VIP from where your trying to access this page.(If you are unable to ping, you need to first fix the reachability) 2) Check the status of Pool (is it green or red in status). If pool is not showing green (check the monitor you set) and also login to ltm using cli and do ping and telnet to pool member. 3) if step 1 and 2 are fine good. Then you can check in cli (tmos) show sys connection | grep 10.0.5.101. If your seeing your connection hit in connection table, for further troubleshooting run tcpdump . 4)tcpdump -vni 0.0:nnn -s 0 "( host 10.0.5.101 and 10.0.3.84 ) or ( host "ip from where your connecting" )"

 

You should be able to do the basic troubleshooting with above steps. Let me know if any confusion or more information needed.

 

ShankarA_326137
Nimbostratus
Nimbostratus

Hi Habib,

 

I think I can't ping the VIP from my mac. I will need to work on it. Any idea on how to fix it? Should I go to network preference and add another network with IP in same range (10.0.5.150 and 255.255.255.0) and gw as 10.0.3.1 ? correct?

 

thanks

 

Stanislas_Piro2
Cumulonimbus
Cumulonimbus

Hi,

 

When configuring "External" interface, choose IP addresses according the VMNET IP network on your Mac. it help to access VS ip address 🙂

 

then, configure automap source address translation in the virtual server if F5 is not the Apache default gateway.

 

ShankarA_326137
Nimbostratus
Nimbostratus

Thanks Stanislas. Will give it a try.

 

ShankarA_326137
Nimbostratus
Nimbostratus

voila !!! That did work Stanislas. Thanks so much both of you (Habib too). Everything appears to be working correctly. You saved tons of my time.