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

JaapL_306396's avatar
JaapL_306396
Icon for Altocumulus rankAltocumulus
Jan 20, 2017

Trouble matching interfaces Big IP VE LTM trial and ESXi / vSphere 6.0.0

textHi all,

 

I 've seen quite a few question on installing LTM VE on vSphere. It didn't help me so far.

 

What I 've got: 1. vSphere host running version 6.0.0, 4 NICs Intel Pro 2. VM LTM VE 11.3.0.39.0 3. Cisco switch SG300-28

 

vSphere config: 1. Networking: vSwithch0 with 1 NIC, Management network, Portgroup VLAN 172, Portgroup VLAN 192 2. VM LTM VE with 4 NICs VMXNET3: 1x VM Network No VLAN, 1x VM Network VLAN 1 (0:c:29:ec:c1:83), 1x VM Network VLAN 172 (0:c:29:ec:c1:6f), 1x VM Network VLAN 192 (0:c:29:ec:c1:79)

 

Switch config: 1. VLAN 1, 172, 192 have an ip-address configured so it can 'route' between VLANs 2. VLAN 1 untagged, VLAN 172 tagged, VLAN 192 tagged on ports where vSphere 4 NICs are connected

 

VM LTM VE config Got three (instead of 4) interfaces: 1.1 (0:c:29:ec:c1:6f), 1.2 (0:c:29:ec:c1:79), 1.3 (0:c:29:ec:c1:83) 1. Management port (temporary) on VLAN/Subnet External being VLAN 1 2. VLANs 1 untagged on 1.3, 172 tagged on 1.1, 192 tagged on 1.3 3. Self IP Internal VLAN/Subnet 172, VLAN/Tunnel: Internal VLAN-172, Port lockdown: allow default

 

After a 'show arp' on the switch I can see the Self-IP IP-address of VLAN 172 with mac-address 0:c:29:ec:c1:6f However the 'show arp' does not give the port the mac-address is seen !!!

 

Problem:

 

Although I 've matched the interfaces of LTM VE to the network adapters of the vSphere host, I can stil not ping the Self-IP of e.g VLAN 172.

 

Question:

 

HELP !

 

Thanx Jaap

 

No RepliesBe the first to reply