Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Connecting switches with same sysnames in Network Atlas causes confusion

Connecting switches with same sysnames in Network Atlas causes confusion

Created by Con Finucane, last modified by MindTouch on Jun 23, 2016

Views: 7 Votes: 0 Revisions: 3

Overview

This article describes what happens when you have multiple switches with the same sysname and if there is a way to ignore the duplicates.

Environment

All versions of  NPM

Cause 

This is due to customer environment.

Resolution

If the sysnames have the same name, add them to the Orion database with the same name. Network Atlas will show the connections it finds and is not designed to ignore any connections. The confusion happens when you use the same sysname that's being used by multiple devices. NPM works as expected, however, there is no way to ignore duplicate sysnames that were detected.

 

 

Last modified
21:57, 22 Jun 2016

Tags

Classifications

Public