Troubleshooting
These pages help you diagnose and recover from common CID boot, network, and registration failures. Match what you observed to the right starting page; each page's Confirm this is the right document section will route you elsewhere if the symptom turns out to belong to a different failure mode.
The diagnostic procedures linked from this page are intended for IT administrators familiar with Linux commands. Incorrect use of the underlying tools can misconfigure the CID and render it inoperable. Proceed only if you are comfortable working in a Linux environment.
Where to start
| What you observed | Start with |
|---|---|
| The CID is emitting 1-, 2-, 3-, or 4 beeps on startup | Beep codes on startup |
| The CID appears offline in CID Hub but is not beeping | Verify CID internet connectivity |
| Activation of a brand-new CID is stalling or failing with no specific error | Verify CID internet connectivity |
| Activation, monitoring, or software updates broke after a network change | Verify CID internet connectivity |
| You see a specific TCP, TLS, certificate, NTP, or DNS error in logs or the UI | The matching page in All pages |
| The CID appears associated with the wrong device, or the Corporate NIC was replaced | Contact Agilent Support to correct the device registration. |
| You need to register a brand-new CID for the first time | Activate a CID (a how-to, not a troubleshooting flow) |
All pages
Pages are listed in the order they tend to apply when reading top-down: boot-time symptoms first, then a triage tool, then specific failure modes from the most foundational network layer to the application layer.
- Beep codes on startup. Use this when the CID is audibly beeping during or after boot.
- Verify CID internet connectivity. Start here when you suspect a network problem but no specific error has surfaced yet.
- DNS resolution failure. Names cannot be resolved to IP addresses.
- TCP port 443 blocked. Outbound HTTPS connections cannot be established.
- NTP time synchronization failure. The CID clock has drifted; TLS validation may be a downstream effect.
- TLS handshake failure. The TCP connection succeeds but the TLS session is terminated.
- Certificate validation errors. A certificate-related error remains after the basic network checks pass.
- OpenLab Server unreachable. The CID cannot reach, validate, or register with the OpenLab CDS Server.
Related procedures
- Activate a CID
- Factory reset a CID
- Internet requirements in System requirements
Last updated: