Network Down Boot (P1 Critical Alert)- Troubleshooting Guide

KB 905774 - Network Down Boot (P1 Critical Alert)- Troubleshooting Guide

Purpose

This document provides a standardized approach for handling and troubleshooting the Network Down - Boot alert, ensuring quick response to critical incidents and maintaining cluster control and system accessibility.

Alert Name

Network Down - Boot

Alert Description

This alert is triggered when the boot network interface on a node is down or unavailable.

This interface is critical for:

  1. Management communication
  2. Cluster control connectivity
  3. External access to the system

Loss of this interface can isolate nodes from cluster control and prevent user/system access.

Severity

P1 - Critical Impact

Possible Causes

  1. Network cable disconnected or faulty
  2. SFP/transceiver failure
  3. Switch port down or misconfigured
  4. Gateway unreachable
  5. NIC hardware issue

L1 Engineer Actions

Step 1 – Log the Alert

  1. Log the alert in the monitoring system
  2. Capture:
    1. Alert name
    2. Node/interface details
    3. Timestamp
    4. Current status

Step 2 – Create Ticket

  1. Monitor the alert for 15 minutes
  2. If the alert persists:
    1. Create an internal ticket
    2. Include all captured details

Step 3 – Escalation (If required)

  1. Inform L2 engineer immediately (P1 priority)
  2. Share complete alert information

Step 4 – Documentation

  1. After confirmation with L2:
    1. Update Issue Master Sheet/ Issue Tracker Sheet

L2 Engineer Actions

Step 1 – Network Reachability

  1. Ping the default gateway from the affected node
  2. Check for packet loss or connectivity failure

Step 2 – Interface & Link Check

  1. Verify NIC/interface status (UP/DOWN)
  2. Check for:
    1. Errors
    2. Packet drops

Step 3 – Switch Validation

  1. Verify switch port status
  2. Review switch logs for:
    1. Link flaps
    2. Port errors
    3. Shutdown events

Step 4 – Physical Verification

  1. Check cable connectivity or replace if required
  2. Verify SFP/transceiver status
  3. Replace faulty components if required

Step 5 – Isolation Testing

  1. Test with:
    1. Alternate switch port
    2. Known working cable/SFP

Step 6 – OEM Escalation (If required)

  1. If unresolved:
    1. Raise a case with OEM/vendor
    2. Share logs and troubleshooting details

Resolution

The issue is considered resolved when:
  1. Network interface is UP
  2. Node is reachable (ping/SSH)
  3. No packet loss observed
  4. Alert is cleared from monitoring

Escalation

  1. L1 → L2: Immediate escalation for P1 alerts
  2. L2 → OEM/Vendor: If issue persists after troubleshooting

    • Related Articles

    • KB 905833 - Network Down Extern (P1 Critical Alert) - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Network Down - Extern alert, including L1 and L2 actions, escalation procedures, and resolution criteria for critical incidents. Alert Name Network Down - ...

    • KB 905711 - Network Degraded (Boot) Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Network Degraded - Boot alert, enabling L1 and L2 engineers to ensure timely detection, prevent full network outage, and maintain service availability. Alert ...

    • KB 021137 - Network Down IB Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Network Down – IB alert, including L1 and L2 actions, escalation process, and resolution criteria. Alert Name Network Down – IB Alert Description This alert ...

    • KB 715377 - ZFS Pool Capacity Critical Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the ZFS Pool Capacity Critical alert, enabling rapid response to prevent storage exhaustion, performance degradation, and potential service outages. Alert Name ...

    • KB 717596 - PSU Error Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the PSU Error alert, ensuring quick identification of power supply issues and maintaining system power redundancy. Alert Name PSU Error Alert Description This ...

    • Recent Articles

    • KB 148090 - Install an OS remotely via ASUS IPMI's KVM

      Here's how to install an OS remotely via ASUS IPMI's KVM (Java or HTML5-based remote console): 1. Access the BMC web interface. Connect to the ASUS IPMI/ASMB management LAN port (separate from the server's normal NICs). Browse to ...

    • KB 114035 - Zotac RMA Process

      ZOTAC RMA PROCESS Overview This plan outlines the overall operational support process for ZOTAC hardware supported by Mbuzz, covering warranty validation, technical diagnosis, RMA coordination, replacement and return handling, SLA management, ...

    • Download Log from ASUSTOR NAS

      How to download Log from NAS Purpose: This article will helps support team to guide customer to download Log to share the evidence for component failure. Problem: Customer reports for Storage device not detected. Storage failure. / Storage not ...

    • TeamGroup Memory Warranty & RMA Process

      Purpose To provide a clear and simple process for handling Team Group Memory warranty and RMA claims. Warranty Verification Product model and serial number. Purchase invoice or proof of purchase. Warranty eligibility. Product condition and any signs ...

    • Common Reasons for RMA Rejection

      Purpose This article outlines the most common reasons why RMA requests are rejected. Understanding these reasons helps Technical Support teams reduce claim delays and improve first-time approval rates. Physical Damage RMA requests are rejected when ...

    • Popular Articles

    • CP Plus Camera and NVR Configuration

      NVR Configuration The CP Plus Pro Series of NVRs have been meticulously designed for providing you with upgraded performance and higher recording quality in your IP video surveillance solution. The robust processor that has been inculcated in this ...

    • KB 775235 - Kerberos Authentication – Overview

      What is Kerberos? Kerberos is a secure authentication method used in our Active Directory (AD) environment (mbuzztech.com). It allows users to: Access multiple systems without re-entering passwords (Single Sign-On – SSO) Log in once Where We Use It ...

    • KB 935001 - AMD Ryzen AM4 Motherboard CPU Compatibility

      For the AM4 Platform, AMD has been very generous when it comes to motherboard compatibility. A CPU launched in 2022, like the Ryzen 7 5800X3D, will work with an almost 6-year-old motherboard, like the ASRock X370 Pro, which was launched in early ...

    • KB 532001 - Ubuntu Server 22.04 Installation Hangs on ASUS WRX80e-SAGE Series

      During the installation of Ubuntu Server 22.04 on ASUS WRX80E-SAGE series motherboards, the installation process hangs during the boot phase. The issue is associated with USB disk recognition errors, particularly with devices managed by the XHCI ...

    • KB 686001 - ASUS Server Stress Testing Guide for INTEL and AMD Platforms

      Creating a Bootable USB with Asus Test Tool Step 1: Download Required Files Download Asus Linux Image: Save the Linux image file provided by Asus. Download Memtest Tool: Open a browser, search for "Memtest," and download the free version from the ...