HOVER_SF_COMMS_MISSING
Background
Section titled “Background”A mission may fail this validator check if Hover-Stbd-Fwd is not detected on the network or if it disappears from the network mid-flight. There may be multiple underlying causes of this issue:
- The respective load switch faulted (overcurrent)
- The node’s busbars got disconnected (open circuit)
- Physical damage to the board/flex mating connector causing no link on either side.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-hover-sf-comms-missing-fail{"<small><b>Step 1</b></small><br/>Question: Did HOVER_SF_COMMS_MISSING check fa..."}
escalate-hover-sf-comms-missing{{"<small><b>Step 2</b></small><br/>Escalation: Escalate to P2 Firmware Platform On C..."}}
re-check-failed-validator-check["<small><b>Step 3</b></small><br/>Action: You might have matched the wrong fail..."]
did-hover-sf-comms-missing-fail -->|Yes| escalate-hover-sf-comms-missing
did-hover-sf-comms-missing-fail -->|No| re-check-failed-validator-check
style did-hover-sf-comms-missing-fail fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-hover-sf-comms-missing fill:#fef3c7,stroke:#f59e0b,color:#78350f
style re-check-failed-validator-check fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
HOVER_SF_COMMS_MISSING check fail in mx_ethernet_node validator?Make sure you match the correct failing validator check from the table.
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.