Interface count mismatch between primary and secondary devices in Portal
search cancel

Interface count mismatch between primary and secondary devices in Portal

book

Article ID: 437653

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

The interface count shown in the NetOps Portal dashboard does not match between a primary and secondary device in a High Availability (HA) pair. One device shows the expected number of interfaces, while the other shows fewer.

Environment

All supported NetOps Performance Management releases

Cause

The mismatched count is often caused by a difference in the administrative state of the interfaces on the physical devices. NetOps Performance Management typically filters out interfaces that are administratively "Down" from the active inventory or specific dashboard views.

For Example:

  • Primary Device: ifAdminStatus OID (1.3.6.1.2.1.2.2.1.7) reports a value of 1 (Up).
  • Secondary Device: ifAdminStatus OID (1.3.6.1.2.1.2.2.1.7) reports a value of 2 (Down).

Resolution

Portal is wokring as epxected here. To resolve the mismatch, synchronize the administrative state of the interfaces on the device level:

  1. Identify the Mismatched Interface: Compare the interface lists for both devices in the Portal to identify which specific interface is missing.
  2. Verify SNMP Status: Use an SNMP walk tool to check the ifAdminStatus (1.3.6.1.2.1.2.2.1.7.[Index]) for the missing interface on both devices.