Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How to use NPM to determine vSphere or Network Problem ?

Hi,

We have been using NPM for a while.

When we get alert from NPM - Servers / VMs are down, is there any way for our Helpdesk staff to determine whether it is a Network or vSphere issue so that they can escalate to the correct person ?

What should be set up in NPM so that it can help them for first line troubleshooting ? The main problem is they ask "How can we find out which switch the ESXi Hosts are connected to ?". Should we assign different naming convention for those switches are used for ESXi Hosts ?

Thanks

Find more posts tagged with

troubleshooting

Accepted answers

All comments

m_roberts

There are a number of things to consider and implement:

You can utilise the Group feature in Orion to put all related objects together to create a 'service' group where Interfaces that connect the hosts to the network, the hosts and other KPI metrics etc.
Create a map within a filtered Summary view page to display KPI metrics that relate to each other. This is similar to the use of groups with the same objective - create presentation of monitoring data for objects that relate and depend on each other
Your question on what is connected to each other the two features above could be implemented or you may wish to utilise the Orion UDT module as this has the track and trace functionality to help identify what is connected to which port in the network

Mark Roberts

Prosperon - UK SolarWinds Partners

Installation | Consultancy | Training | Licenses

tonyjk

Hi,

Many thanks for your valuable advice.

If there is a network problem, that SP IP may not be pingable (if it is connected to that switch) or pingable (if it is not connected to that switch).

Would it be also a good idea to include the IP addresses of those Storage Processor in the Group ? OR it may make them confusing ?

Thanks again.