Network Degraded (Boot) Alert - Troubleshooting Guide

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 Name

Network Degraded - Boot

Alert Description

This alert is triggered when one slave interface in a bonded network configuration goes down.

It indicates that the bonded interface has lost redundancy, leaving the system with a single active network path

Severity

P2 – High Impact

Possible Causes

  1. Network cable disconnection or fault
  2. Faulty NIC/interface
  3. Switch port issues or shutdown
  4. Link flapping or instability
  5. Configuration mismatch in bonding
  6. Hardware or transceiver issues

L1 Engineer Actions

Step 1 – Log the Alert

  1. Log in to the monitoring system
  2. Review:
    1. Alert summary
    2. Affected host
    3. Interface details

Step 2 – Create Ticket

  1. Monitor the alert for 15 minutes to check if transient
  2. If issue persists:
    1. Create an internal ticket
    2. Include:
    3. Hostname
    4. Interface details
    5. Timestamp
    6. Observations

Step 3 – Escalation (If required)

  1. Inform L2 team if alert persists beyond 20 minutes
  2. Share all relevant details

Step 4 – Documentation

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

L2 Engineer Actions

Step 1 – Check Bond Status

cat /proc/net/bonding/*
  1. Identify:
    1. Active and failed slave interfaces
    2. Link status (UP/DOWN)
    3. MII status

Step 2 – Verify Network Interface

ip link show
  1. Check interface state
  2. Look for down or unstable interfaces

Step 3 – Switch Port Validation

  1. Verify corresponding switch port:
    1. Link status (UP/DOWN)
    2. Errors or flapping
    3. Coordinate with network team if required

Step 4 – Physical Inspection

  1. Check and reseat network cable and trans receiver.
  2. Replace cable if faulty

Step 5 – OEM Escalation (If required)

  1. If issue persists:
    1. Raise ticket with OEM
    2. Share logs and observations

Resolution

The issue is considered resolved when:

  • All bond slave interfaces are UP
  • Bonded interface regains redundancy
  • No link instability or flapping observed
  • Alert is cleared

Escalation

  1. L1 → L2: If not resolved within 20 minutes
  2. L2 → OEM/Vendor: If hardware/network issue persists

    • Recent Articles

    • KB-630208 | How to use Find and Locate to search for files in Linux

      Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...

    • KB-630164 | How to use rsync to Synchronize Files

      Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...

    • KB-630107 | How to create a Linux swap file

      Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...

    • MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims

      MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...

    • KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error

      Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...

    • 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 ...

    • How to Remove and Reinstall NVIDIA Drivers on Ubuntu

      This article provides step by step guide to completely remove existing NVIDIA drivers and reinstall specific version of the NVIDIA driver on the Ubuntu system Prerequisites Administrative (sudo) access to the Ubuntu system. Internet access to ...

    • KB 692001 - Personal Computers and Servers - Classification and Point of Contact

      We can classify the computers that MBUZZ handles based on their form-factor as below: Tower Workstations, Desktops, Gaming PCs and SFF (Small form factor) PCs fall under this category. These are computers people would use on a desk and rarely move. ...

    • KB 298031 - M.2 SSD Tier List

      The sequential read and write speeds, which are usually the most advertised number, are not a proper benchmark of real-world performance or the quality of an SSD. This article categorizes and tiers SSDs based on factors like the type of NAND flash, ...