Network Speed IB Alert - Troubleshooting Guide

KB 021273 - Network Speed IB Alert - Troubleshooting Guide

Purpose

This document provides a standardized approach for handling and troubleshooting the Network Speed – IB alert, including L1 and L2 actions, escalation process, and resolution guidelines.

Alert Name

Network Speed IB

Alert Description

This alert is triggered when the InfiniBand (IB) link operates below the expected bandwidth. It indicates a mismatch or degradation in IB link speed on the head node, which can impact high-performance computing (HPC) environments.

Severity

P2 – High Impact

Possible Causes

  1. InfiniBand link speed mismatch
  2. Faulty or incompatible IB cables
  3. Defective SFP/transceiver modules
  4. Switch port configuration issues
  5. Hardware limitations or degradation
  6. Issues in IB fabric health

L1 Engineer Actions

Step 1 – Log the Alert

  1. Log in to the affected node
  2. Review alert summary and details

Step 2 – Create Ticket

  1. Monitor the alert for 20 minutes for auto-resolution
  2. If issue persists:
    1. Create an internal ticket
    2. Include observations and alert details

Step 3 – Escalation (If required)

  1. Inform L2 team after 20 minutes if unresolved
  2. Share all relevant findings

Step 4 – Documentation

After confirmation with L2, update Issue Master Sheet/ Issue Tracker Sheet.

L2 Engineer Actions

Step 1 – Verify InfiniBand Link Speed

ibstat

  1. Check current IB link speed
  2. Compare with expected bandwidth

Step 2 – Check IB Fabric Health

  1. Validate overall InfiniBand fabric status
  2. Identify any inconsistencies or degraded links

Step 3 – Inspect Transceivers (SFPs)

  1. Check on both- Server side and Switch side
  2. Ensure proper seating and compatibility

Step 4 – Switch Side Validation (If Applicable)

  1. Perform port flapping- Shutdown/ No Shutdown
  2. Validate switch configuration for IB ports

Step 5 – Hardware Validation

  1. Reseat or replace faulty components:
    1. IB Cable
    2. SFP/ Transceiver

Step 6 – OEM Escalation (If Required)

  1. If issue persists after troubleshooting:
    1. Raise a ticket with OEM/vendor
    2. Share observations and test results

Resolution

The issue is considered resolved when:
  1. IB link speed matches expected hardware specifications
  2. No degradation observed in IB performance
  3. Cluster communication latency is normal
  4. Alert is cleared

Escalation

  • L1 → L2: If not resolved within 20 minutes
  • L2 → OEM/Vendor: If hardware or configuration 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, ...