> For the complete documentation index, see [llms.txt](https://chameleoncloud.gitbook.io/chi-in-a-box/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chameleoncloud.gitbook.io/chi-in-a-box/operations/runbooks/nodenetworkbridgedown.md).

# Node Network Bridge Down

**Summary**: A Linux bridge is no longer reporting traffic.

**Consequences**: If the bridge is being used by processes to send/receive traffic, those processes are effectively cut off from the network. This ranges from fine to very bad, depending on the process/service.

#### Possible causes

**A Docker network was deleted**: if a Docker network was deleted or recreated recently, this alert can fire, because Linux typically creates a bridge for each Docker network. The bridge name will include part of the Docker network ID if this is the case. Typically this is benign if this is the cause.

**Network is misconfigured**: it is likely that, if this is a major/primary network bridge, then all connectivity is down (though a [`NodeExporterDown`](https://github.com/ChameleonCloud/chi-in-a-box/blob/stable/xena/docs/runbooks/\[Runbook]-NodeExporterDown/README.md) alert would be expected in that case, as the monitoring infrastructure likely wouldn't be able to get this information from the problem host at all!).

**OVS bridges were deleted**: this *can* happen during an upgrade, but shouldn't persist for very long. It may be necessary to repair OVS state. Try running `./cc-ansible reconfigure --tags openvswitch` to fix.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://chameleoncloud.gitbook.io/chi-in-a-box/operations/runbooks/nodenetworkbridgedown.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.