Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Stacked switches not showing individual switch data

Stacked switches not showing individual switch data

Table of contents

Overview

This article explains why the individual switch data cannot be viewed when monitoring a stack of switches.

Environment

  • NPM 10.5 to NPM 11.5.3
  • All stacked switches

Detail

When switches are stacked, the other member switches of the stack act as ports for the management switch. When the stack is polled, a communication with the management switch occurs. If it does not give data on the other members of the stack, then these will not show up in the report. The other members of the stack cannot be polled individually unless they have IP addresses that are in NPM.

There are several possible workarounds to that can be implemented however to infer the status of the stack switches.

Universal Device Pollers can be used to monitor switch interfaces for instances to infer the availability of the switch.

Although not full proof, it will trigger an alert when the stack switch goes down. More options can be found under the thwack post provided below:

https://thwack.solarwinds.com/ideas/1720#start=25

Support for monitoring of Cisco switches only is available under NPM version 12 and newer, if you are looking to upgrade please see this article.  

 

Last modified

Tags

Classifications

Public