# Vthunder ethernet port down

**URL:** <https://community.a10networks.com/t/vthunder-ethernet-port-down/514>\
**Category:** ADC - Application Delivery\
**Created:** [July 18, 2018, 9:35pm UTC](https://community.a10networks.com/t/vthunder-ethernet-port-down/514 "2018-07-18T21:35:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pcarrillo](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@pcarrillo](https://community.a10networks.com/u/pcarrillo)\
**Post date:** [July 18, 2018, 9:35pm UTC](https://community.a10networks.com/t/vthunder-ethernet-port-down/514/1 "2018-07-18T21:35:18Z")

</div>

Hi,

I hope you can help me with this issuse.

I am configuring a vthunder 4.1.1 on VMware 5.5. The OVF deploy was successfull but the ethernet ports are in a down state (only the eth ports, the mgmt port works whitout problems). At the VMware layer, the network adapters are “connected at power on”, its driver is VMXNET3 for the eth1 / eth2 ports and E1000 for the mgmt port. In the VMware host there are many servers working at the same virtual networks than the vthunder.

The interface config output are:

interface management

```auto
  ip address 30.10.10.19 255.255.255.0
  ip default-gateway 30.10.10.1

```

!  
interface ethernet 1  
&nbsp;&nbsp;enable  
!  
interface ethernet 2  
&nbsp;&nbsp;enable

The sh int brief output are:

```auto
mgmt Up Full 1000 N/A N/A 0050.56a5.6454 30.10.10.19/24 1
1 Down None None None 111 0050.56a5.518b 0.0.0.0/0 0
2 Down None None None Tag 0050.56a5.5beb 0.0.0.0/0 0

```

Did somebody had the same problem?

Regards  
Pablo Carrillo

---

<div class="post-metadata">

**Author:** ![ericn](https://avatars.discourse-cdn.com/v4/letter/e/f4b2a3/32.png) [@ericn](https://community.a10networks.com/u/ericn)\
**Post date:** [July 27, 2018, 4:59pm UTC](https://community.a10networks.com/t/vthunder-ethernet-port-down/514/2 "2018-07-27T16:59:22Z")

</div>

I am using vSphere/ESXi v5.5, data interfaces of type VMXNET3 just fine. I would suggest opening a ticket with TAC. Assuming licensing is in order and the interfaces are actually Device Status \> Connected after boot of the vm, it “should” work.
