Forum Discussion
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_basharatJun 23, 2017Nimbostratus
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
- eben_259100Jun 23, 2017Cirrostratus
share the output of the following commands. "tmsh show net route lookup 172.16.0.140"
what hypervisor is the VE running on? Is this a lab environment?
- a_basharatJun 23, 2017Nimbostratus
It is a bit strange, because when I force two interfaces on a single VLAN, apart from giving me back an error saying basically that NO, it puts a 0 ahead of the interface, then I take off one of the interfaces, leaving one in and it works: