Virtual Server Cmds

virtual server has to be enabled on vlan which traffic is coming.

 

 

by default when creating, virtual server will be enabled on all vlan.

1)........"by default when creating, virtual server will be enabled on all vlan"

 

 

So if a specific vlan alone is enabled on a Virtual server, does the default configuration of allowing ALL VLANS gets disabled?

 

 

2)......"virtual server has to be enabled on vlan which traffic is coming"

 

 

So...in the virtual server configuration, traffic is coming on the vlan, c_200.36.134.128_26, as the VIP is sitting on this Vlan, so if this Vlan is not enabled on the virtual server,

 

 

the VIP WILL NOT ping. is that right?

So if a specific vlan alone is enabled on a Virtual server, does the default configuration of allowing ALL VLANS gets disabled? yes

 

 

So...in the virtual server configuration, traffic is coming on the vlan, c_200.36.134.128_26, as the VIP is sitting on this Vlan, so if this Vlan is not enabled on the virtual server, the VIP WILL NOT ping. is that right?no. the virtual server is listening on port 443. it does nothing about icmp. the one who responds icmp is virtual address. if you look at virtual address (e.g. 200.36.134.131), you will see ARP is enabled. if you disable ARP and clear ARP cache, the virtual address will not be pingable.

1)........." no. the virtual server is listening on port 443. it does nothing about icmp. the one who responds icmp is virtual address."

 

 

So, if i change the virtual server configuration to as below (removed the vlan, _200.36.134.128_26 ), you mean to say, one can still ping the VIP, 200.36.134.131?

 

 

virtual apps_critical_BTK

 

{

 

pool bzt_pool destination 200.36.134.131:https

 

ip protocol tcp

 

persist persist_default

 

profiles tcp_default {}

 

vlans {

 

c_10.201.20.25_27

 

c_16.25.42.36_26

 

} enable

 

yes.

e.g.

[root@ve1023:Active] config  b virtual bar list
virtual bar {
   pool foo
   destination 172.28.19.79:80
   ip protocol 6
   rules myrule
   profiles {
      http {}
      tcp {}
   }
   vlans none enable
}

 arp
Address                  HWtype  HWaddress           Flags Mask            Iface
172.28.19.254            ether   00:01:E8:D5:D4:47   C                     eth0

 ping 172.28.19.79
PING 172.28.19.79 (172.28.19.79) 56(84) bytes of data.
64 bytes from 172.28.19.79: icmp_seq=1 ttl=255 time=2.97 ms
64 bytes from 172.28.19.79: icmp_seq=2 ttl=255 time=1.18 ms

--- 172.28.19.79 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 1.180/2.075/2.971/0.896 ms

But in my case, the VIP, 200.36.134.131, was not pinging from within the F5 prompt itself.

 

 

Nor was it pinging from its upstream router, there was no arp for the VIP as well, even though, arp was enabled on the virtual server.

 

 

till.................

 

 

BUT WHEN i added/enabled the vlan, c _200.36.134.128_26, on the virtual server, as below:

 

 

virtual apps_critical_BTK

 

{

 

pool bzt_pool destination 200.36.134.131:https

 

ip protocol tcp

 

persist persist_default

 

profiles tcp_default {}

 

vlans {

 

c_10.201.20.25_27

 

c_200.36.134.128_26

 

c_16.25.42.36_26

 

} enable

 

 

I was IMMEDIATELY, able to VIP from within and upstream router as well. Can you explain this?

 

would you mind trying this?

 

 

1. remove c_200.36.134.128_26 vlan from the virtual server

 

 

2. disable and then enable arp on 200.36.134.131

 

b virtual address 200.36.134.131 arp disable

 

b virtual address 200.36.134.131 arp enable

 

 

3. ping 200.36.134.131 witin bigip prompt

Arp was enabled already. Just to make sure that i did disable the virtual server and reenabled it back.

 

 

But there was no change.

nitass,

 

 

can you please reply?

i have not had any other idea. if no one else has, i suggest opening a support case to see if they can help.