Blob Agent/Dock Network Connection Issues
Viewing this guide for
Applicable alarms (2)
NO_INTERNET_VIA_ETHERNETUNSTABLE_INTERNET_VIA_ETHERNET
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for NO_INTERNET_VIA_ETHERNET) as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
ssh-into-the-dock["<small><b>Step 1</b></small><br/>Action: SSH into the Dock"]
run-the-following-command-to-view-the-st["<small><b>Step 2</b></small><br/>Action: Run the following command to view the..."]
look-for-zipwan-end0-in-the-output-is-t{"<small><b>Step 3</b></small><br/>Question: Look for zipwan@end0 in the output...."}
run-the-following-command-to-restart-the["<small><b>Step 4</b></small><br/>Action: Run the following command to restart ..."]
run-the-same-command-you-ran-earlier-to["<small><b>Step 5</b></small><br/>Action: Run the same command you ran earlier ..."]
is-zipwan-end0-marked-as-up{"<small><b>Step 6</b></small><br/>Question: Is zipwan@end0 marked as UP?"}
ssh-into-the-aircraft-run-the-following["<small><b>Step 7</b></small><br/>Action: SSH into the Aircraft. Run the follow..."]
run-the-following-command-to-get-zipwan["<small><b>Step 8</b></small><br/>Action: Run the following command to get zip..."]
continue-to-next-step["<small><b>Step 9</b></small><br/>Action: Continue to next step."]
take-a-look-at-the-baraza-logs-using-th{"<small><b>Step 10</b></small><br/>Question: Take a look at the Baraza logs using ..."}
this-is-a-site-network-problem-if-this["<small><b>Step 11</b></small><br/>Action: This is a site network problem. If th..."]
proceed-to-the-next-step["<small><b>Step 12</b></small><br/>Action: Proceed to the next step."]
review-the-site-network-traffic-from-th{"<small><b>Step 13</b></small><br/>Question: Review the site network traffic from ..."}
does-this-correspond-with-low-site-traf{"<small><b>Step 14</b></small><br/>Question: Does this correspond with low site tr..."}
site-network-problem-follow-site-networ["<small><b>Step 15</b></small><br/>Action: This is a site network problem. If th..."]
escalate-to-p2-dock-embedded-on-call{{"<small><b>Step 16</b></small><br/>Escalation: Escalate to P2 Dock Embedded On Call"}}
proceed-to-the-next-step-2["<small><b>Step 17</b></small><br/>Action: Proceed to the next step."]
in-the-journalctl-log-for-the-blob-agen{"<small><b>Step 18</b></small><br/>Question: In the journalctl_log for the blob_..."}
the-blob-agent-is-successfully-download{"<small><b>Step 19</b></small><br/>Question: The blob_agent is successfully downlo..."}
site-network-problem-follow-site-networ-2["<small><b>Step 20</b></small><br/>Action: This is a site network problem. If th..."]
escalate-to-p2-dock-embedded-on-call-2{{"<small><b>Step 21</b></small><br/>Escalation: Escalate to P2 Dock Embedded On Call"}}
escalate-to-p2-dock-embedded-on-call-3{{"<small><b>Step 22</b></small><br/>Escalation: Escalate to P2 Dock Embedded On Call"}}
ssh-into-the-dock --> run-the-following-command-to-view-the-st
run-the-following-command-to-view-the-st --> look-for-zipwan-end0-in-the-output-is-t
look-for-zipwan-end0-in-the-output-is-t -->|Yes| run-the-following-command-to-restart-the
look-for-zipwan-end0-in-the-output-is-t -->|No| continue-to-next-step
run-the-following-command-to-restart-the --> run-the-same-command-you-ran-earlier-to
run-the-same-command-you-ran-earlier-to --> is-zipwan-end0-marked-as-up
is-zipwan-end0-marked-as-up -->|Yes| ssh-into-the-aircraft-run-the-following
is-zipwan-end0-marked-as-up -->|No| run-the-following-command-to-get-zipwan
ssh-into-the-aircraft-run-the-following --> take-a-look-at-the-baraza-logs-using-th
run-the-following-command-to-get-zipwan --> take-a-look-at-the-baraza-logs-using-th
continue-to-next-step --> take-a-look-at-the-baraza-logs-using-th
take-a-look-at-the-baraza-logs-using-th -->|Yes| this-is-a-site-network-problem-if-this
take-a-look-at-the-baraza-logs-using-th -->|No| proceed-to-the-next-step
proceed-to-the-next-step --> review-the-site-network-traffic-from-th
review-the-site-network-traffic-from-th -->|Yes| does-this-correspond-with-low-site-traf
review-the-site-network-traffic-from-th -->|No| proceed-to-the-next-step-2
does-this-correspond-with-low-site-traf -->|Yes| site-network-problem-follow-site-networ
does-this-correspond-with-low-site-traf -->|No| escalate-to-p2-dock-embedded-on-call
proceed-to-the-next-step-2 --> in-the-journalctl-log-for-the-blob-agen
in-the-journalctl-log-for-the-blob-agen -->|Yes| the-blob-agent-is-successfully-download
in-the-journalctl-log-for-the-blob-agen -->|No| escalate-to-p2-dock-embedded-on-call-2
the-blob-agent-is-successfully-download -->|Yes| site-network-problem-follow-site-networ-2
the-blob-agent-is-successfully-download -->|No| escalate-to-p2-dock-embedded-on-call-3
style ssh-into-the-dock fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-the-following-command-to-view-the-st fill:#dcfce7,stroke:#22c55e,color:#14532d
style look-for-zipwan-end0-in-the-output-is-t fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style run-the-following-command-to-restart-the fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-the-same-command-you-ran-earlier-to fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-zipwan-end0-marked-as-up fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style ssh-into-the-aircraft-run-the-following fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-the-following-command-to-get-zipwan fill:#dcfce7,stroke:#22c55e,color:#14532d
style continue-to-next-step fill:#dcfce7,stroke:#22c55e,color:#14532d
style take-a-look-at-the-baraza-logs-using-th fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style this-is-a-site-network-problem-if-this fill:#dcfce7,stroke:#22c55e,color:#14532d
style proceed-to-the-next-step fill:#dcfce7,stroke:#22c55e,color:#14532d
style review-the-site-network-traffic-from-th fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style does-this-correspond-with-low-site-traf fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style site-network-problem-follow-site-networ fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-dock-embedded-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style proceed-to-the-next-step-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style in-the-journalctl-log-for-the-blob-agen fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-blob-agent-is-successfully-download fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style site-network-problem-follow-site-networ-2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-p2-dock-embedded-on-call-2 fill:#fef3c7,stroke:#f59e0b,color:#78350f
style escalate-to-p2-dock-embedded-on-call-3 fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
SSH into the Dock
2 action
Run the following command to view the state of all network interfaces:
ip a. 3 question
Look for
zipwan@end0 in the output. Is the interface marked as DOWN (see screenshot)? 4 action
Run the following command to restart the Dock’s Network Config Service:
sudo systemctl restart network_config. 5 action
Run the same command you ran earlier to view all network interfaces:
ip a. 6 question
Is
zipwan@end0 marked as UP? 7 action
SSH into the Aircraft. Run the following command to restart the Blob Agent:
To see if logs offload, check the
sudo systemctl restart blob_agent. Logs should start offloading/the problem should be resolved. If it is not resolved within 1 hour, proceed to step 4.To see if logs offload, check the
blob_agent or log_offloader journalctl logs. 8 action
Run the following command to get
If it does not resolve after 1 hour, check
zipwan@end0 back up: sudo ip link set zipwan up. Check if it succeeded with running ip a again, and if so, logs should start offloading/the problem should be resolved.If it does not resolve after 1 hour, check
zipwan@end0 another time. Is it down again? This indicates flakey network connection. Proceed to step 4. 9 action
Continue to next step.
10 question
Take a look at the Baraza logs using the Site Network template. Have there been any
NO_INTERNET_VIA_ETHERNET or UNSTABLE_INTERNET_VIA_ETHERNET alarms on the dock within the last two hours? 11 action
This is a site network problem. If this is the first time this has happened in the past 24h, wait 1 hour to see if the issue resolves itself.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error.
12 action
Proceed to the next step.
13 question
Review the site network traffic from the dock using the Site Network Health template and find which port (1 or 2) has traffic. In addition, find the zip’s
In the blob_agent
1.
2.
3.
journalctl_log for the blob_agent.In the blob_agent
journalctl, are there any of the following errors?1.
send failed because receiver is gone2.
1: connection closed before message completed3.
did not hear back from the cloud 14 question
Does this correspond with low site traffic (
<200kB/s)? 15 action
This is a site network problem. If this is the first time this has happened in the past 24h, wait 1 hour to see if the issue resolves itself.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error steps.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error steps.
16 escalation
Escalate to P2 Dock Embedded On Call
17 action
Proceed to the next step.
18 question
In the
journalctl_log for the blob_agent, is either a download or upload speed logged? 19 question
The blob_agent is successfully downloading/uploading. Are there low download/upload speeds from the blob_agent (
<200,000 bps) and low site traffic (<200kB/s)? 20 action
This is a site network problem. If this is the first time this has happened in the past 24h, wait 1 hour to see if the issue resolves itself.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error steps.
If this is the second time, follow the Site Network Outage troubleshooting guide and skip the Asset Offline Due To Comms/Provisioning Agent Error steps.
21 escalation
Escalate to P2 Dock Embedded On Call
22 escalation
Escalate to P2 Dock Embedded On Call
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.