For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

a_basharat_2591's avatar
a_basharat_2591
Icon for Nimbostratus rankNimbostratus
Jun 23, 2017

Renaming VLANs stopped communication

Hi,   On a Virtual Edition F5:   I have renamed the external and internal VLAN names to something like VLAN_XX and VLAN_YY. All the parameters have been left the same as before: untagged, 4093 ...
application delivery
BIG-IP
devops
LTM
eben's avatar
eben
Icon for Nimbostratus rankNimbostratus
Jun 23, 2017

Renaming a vlan should not affect traffic flow as the name does not go in the wire, the tag does. that said, Please check 1. Interfaces are mapped to the correct VLANs. 2. VMNet is mapped appropriately.

 

If you can also share what your network is like, I could be of more help.

 

HTH eben.

 

a_basharat's avatar
a_basharat
Icon for Nimbostratus rankNimbostratus
Jun 23, 2017

From a server I can ping to the internal interface of the VE F5, but from the F5 [on CLI] I can not ping, it says unreachable:

 

[root@EN:Active:Standalone] config tracepath 172.16.0.140 1?: [LOCALHOST] pmtu 1500 1: 172.16.0.4 (172.16.0.4) 443.348ms !H 1: 172.16.0.4 (172.16.0.4) 1993.922ms !H Resume: pmtu 1500