Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Orion Platform > SAM objects in Orion Maps are unknown or grayed out

SAM objects in Orion Maps are unknown or grayed out

Updated May 30, 2018

Overview

In some cases, Orion Maps show SAM Orion.APM.GenericApplication objects with a status of Unknown. The object is grayed out or there is an unexpected error. This occurs only with SAM components. When you hover over the object you see the message object status is unknown

 

maps 1.PNG

Maps 2.PNG

Environment

  • NPM 12.2
  • SAM 6.5 or SAM 6.6, SAM 6.7

Cause 

Orion Maps was a new feature released with Core 2017.3 and EOC 2.0.

It's possible that this happened because some computers had an older version of Network Atlas in use. 

The SAM plugin has a mechanism to translate IDs to new format (with siteID |0 ).

Resolution

To fix this issue, you can do either of the following:

  • Recreate the map with objects using an up-to-date Network Atlas tool.
  • Manually fix the maps by changing the IDs of the affected objects, as described below.

 

To change the obect ID:

  1. Go to the Network Atlas cache folder. By default, it is:
    c:\Users\USERNAME\AppData\Roaming\SolarWinds\NetworkAtlas\Maps\Orion\localhost\
  2. Open the files in a text editor such as Notepad, and add |0 to any IDs. For example:
    • OriginalOrion.APM.GenericApplication: 1xxx#
    • UpdatedOrion.APM.GenericApplication: 1xxx|0#
  3. Save the files.
  4. In Network Atlas, make some small change so the maps appear edited and will be saved to the database. 


Incorrect example:

comment: "NetObjects=: 0#,Orion.Nodes: 16|0#,Orion.APM.GenericApplication: 0#"
SWNetObjectNID: "Orion.APM.GenericApplication: 2|0#"
 
Correct example:
comment: "NetObjects=: 0#,Orion.Nodes: 16|0#,Orion.APM.GenericApplication: 0#"
SWNetObjectNID: "Orion.APM.GenericApplication: 2|0#"
 
 
***********************************************************************************************************************
 
Resolution 2
 
Replace the broken component with a working component that is green:
 
The grey component highlighted below is not mapped to a component so has become orphaned somehow. 
You can still see the component is green in the objects list so replace the grey component with the working component
 
clipboard_e10d66fece760761681b87da6c7c5f0df.png
 
 
Right-click a grayed out component shows no mappings so is unknown
 
clipboard_ecebcdc024647436bd4a3701faf806edf.png
 
 
Right-click the green component above shows the mappings to a certain component.
 
clipboard_ea9555179200577e07860650b59363d8d.png
 
 

 

Last modified

Tags

Classifications

Public