DISTRO_B_COMMS_MISSING
Viewing this guide for
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
did-distro-b-comms-missing-fail{"<small><b>Step 1</b></small><br/>Question: Did DISTRO_B_COMMS_MISSING check fa..."}
escalate-to-p2-firmware-platform{{"<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-distro-b-comms-missing-fail -->|Yes| escalate-to-p2-firmware-platform
did-distro-b-comms-missing-fail -->|No| re-check-failed-validator-check
style did-distro-b-comms-missing-fail fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-firmware-platform 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.
1 question
Did
DISTRO_B_COMMS_MISSING check fail in mx_ethernet_node validator? 2 escalation
Escalate to P2 Firmware Platform On Call.
3 action
You might have matched the wrong failing check, please navigate to the original guide here: Ethernet Link Fault Guide.
Make sure you match the correct failing validator check from the table.
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.