> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/generic/solution/host-interfaces-using-enic-drivers-become-disabled-and-lose-con.md).

# Host Interfaces Using 'enic' Drivers Become Disabled and Lose Connectivity

## Problem

* A Platform9 Managed host shows as offline from Clarity UI.
* Connectivity errors are observed as shown below.

{% tabs %}
{% tab title="/var/log/pf9/hostagent.log" %}

```none
pf9_app.py INFO - Setting the desired service state
pf9_app.py INFO - Setting service state pf9-comms.3.9.0-663.baf294f. Command: sudo systemctl start pf9-comms
session.py INFO - Converge succeeded
amqp.py WARNING - Connection closed due to Not specified, retrying in 10 seconds
session.py ERROR - Connection closed unexpectedly.
slave.py ERROR - Connection error. Retrying in 10 seconds.
Traceback (most recent call last):
  File "/opt/pf9/hostagent/lib/python2.7/site-packages/bbslave/slave.py", line 83, in reconnect_loop
    channel_retry_period=retry_period)
  File "/opt/pf9/hostagent/lib/python2.7/site-packages/bbslave/session.py", line 716, in start
    raise AMQPConnectionError
```

{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="/var/log/pf9/muster.log" %}

```none
AMQPConnectionError upstream: failed to connect to RabbitMQ: Exception (501) Reason: "read tcp 127.0.0.1:41514->127.0.0.1:5672: i/o timeout"
```

{% endtab %}
{% endtabs %}

* The **enic devcmd** timed out messages are reported in */var/log/messages* on the host.

{% tabs %}
{% tab title="/var/log/messages" %}

```none
kernel: [21479642.626977] enic 0000:06:00.0 enp6s0: devcmd 4 timed out
kernel: [21479642.727633] enic 0000:07:00.0 enp7s0: devcmd 4 timed out
...
kernel: [21479650.951488] enic 0000:07:00.0 enp7s0: devcmd2 4: wq is full. fetch index: 17, posted index:16
kernel: [21479650.952179] enic 0000:0c:00.0 enp12s0: devcmd2 4: wq is full. fetch index: 8, posted index: 7
...
kernel: [21489854.868177] enic 0000:0c:00.0 enp12s0: devcmd2 4: wq is full. fetch index: 8, posted index: 7
kernel: [21489854.869338] enic 0000:07:00.0 enp7s0: devcmd2 4: wq is full. fetch index: 17, posted index:16
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Platform9 Managed Kubernetes - All Versions
* CentOS Linux 7.4
* enic driver - v2.3.0.31

## Cause

The **enic** module sends a command to the NIC firmware and does not receive a timely response. NIC firmware hangs or in a bad state.

## Resolution

Work with the hardware vendor to investigate this issue further and upgrade firmware to the latest version recommended by the hardware vendor.

## Additional Information

RedHat: [Why did interfaces using 'enic' drivers get disabled with errors and lose connectivity?](https://access.redhat.com/solutions/2390931)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/generic/solution/host-interfaces-using-enic-drivers-become-disabled-and-lose-con.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.