Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Archive > 2018Jan2 - Deletes > 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 Gerald.Prado on Jan 02, 2018

Views: 973 Votes: 0 Revisions: 4

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

Tags

Classifications

Public