Wireless Access

Did you follow the instructions in the Virtual Appliance Installation Guide?

Assume you didn't enable both interfaces at the same time, as it would create a L2 loop?

Also not sure where the misspelled switchport turnk comes from? Did you copy this from the CLI output? I would expect switchport trunk.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

Assume you didn't enable both interfaces at the same time, as it would create a L2 loop?

Also not sure where the misspelled switchport turnk comes from? Did you copy this from the CLI output? I would expect switchport trunk.

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

Assume you didn't enable both interfaces at the same time, as it would create a L2 loop?

Also not sure where the misspelled switchport turnk comes from? Did you copy this from the CLI output? I would expect switchport trunk.

I recently helped a customer deploy a very similar environment (VDS), I still don't see the relevance of running multiple ethernet interfaces, you can use adapter 1 for management and then adapter 2 for you networking. Just deploy a second virtual controller on a different host if you want resilience. 

We did run into an issue with NIC teaming, it is described in the link below.  Check the third reply in the link below, to see if that get's you any further. 

https://airheads.hpe.com/community-home/digestviewer/viewthread?MID=25240

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

I recently helped a customer deploy a very similar environment (VDS), I still don't see the relevance of running multiple ethernet interfaces, you can use adapter 1 for management and then adapter 2 for you networking. Just deploy a second virtual controller on a different host if you want resilience. 

We did run into an issue with NIC teaming, it is described in the link below.  Check the third reply in the link below, to see if that get's you any further. 

https://airheads.hpe.com/community-home/digestviewer/viewthread?MID=25240

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

Assume you didn't enable both interfaces at the same time, as it would create a L2 loop?

Also not sure where the misspelled switchport turnk comes from? Did you copy this from the CLI output? I would expect switchport trunk.

Is the network assigned to the VM configured to support trunk?

The vSwitch and port group (assuming using VMware) configuration is important and pretty much non-negotiable.

I recently helped a customer deploy a very similar environment (VDS), I still don't see the relevance of running multiple ethernet interfaces, you can use adapter 1 for management and then adapter 2 for you networking. Just deploy a second virtual controller on a different host if you want resilience. 

We did run into an issue with NIC teaming, it is described in the link below.  Check the third reply in the link below, to see if that get's you any further. 

https://airheads.hpe.com/community-home/digestviewer/viewthread?MID=25240

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

Is the network assigned to the VM configured to support trunk?

The vSwitch and port group (assuming using VMware) configuration is important and pretty much non-negotiable.

I recently helped a customer deploy a very similar environment (VDS), I still don't see the relevance of running multiple ethernet interfaces, you can use adapter 1 for management and then adapter 2 for you networking. Just deploy a second virtual controller on a different host if you want resilience. 

We did run into an issue with NIC teaming, it is described in the link below.  Check the third reply in the link below, to see if that get's you any further. 

https://airheads.hpe.com/community-home/digestviewer/viewthread?MID=25240

In that case, it doesn't make sense that two interfaces that are configured identical, connected (only one at the time) to a virtual ethernet in ESXi connected to the same vlan, that it doesn't work.

I can only think of a different configuration in the ESXi or the uplink switch where the vnics are connected to. As you mention that it's another VM adapter, is that different physical NIC and vSwitch on the ESXi? Please double-check the MTU/MAC-Change/Promiscuous settings on the NIC/vSwitch (check installation guides) and the settings on the upstream switch.

Can't imagine that this is a VMC problem.

Correct.  I had only one interface active at a time.  The typo was from me typing in my config.  The system I'm using for remote access doesn't make it easy for me to copy paste the config so I typed it and had a typo apparently.

Assume you didn't enable both interfaces at the same time, as it would create a L2 loop?

Also not sure where the misspelled switchport turnk comes from? Did you copy this from the CLI output? I would expect switchport trunk.