Comments
-
For anything redundant, I monitor both nodes individually. But this will only work if both nodes have their own IP address. As for best practice, I don't know.
-
Add a widget like Top XX Interfaces by Percent Utilization and then use a filter to just populated it with the interfaces you're interested in.
-
That view is showing the link in utilization, not whether the link is up or down. It is telling you that it's unable to show the link utilization.
-
All the posts should have this button on them Click on it on the post that contains the Correct Answer.
-
Solarwinds will pick up the new device details, no problems there. Only issue will be if the interfaces you monitor change names. You may need to delete the now 'unknown' interfaces and add in the new ones. I've done this heaps when I upgrade old devices to new ones.
-
I haven't upgraded mine as yet but FWIW every other upgrade I've done has always gone faultless.
-
It's in the manual under Status Indicators. Here's the list from the manual
-
Welcome to all the newbies!
-
NPM shows how much utilization you have and NTA shows you who is using that bandwidth.
-
How are you creating this image? It looks to me that the layout is depended on the length of the first columns entry.
-
How about creating 2 separate reports and adding in a time frame to something similar as listed in this image.
-
Can't say I've ever experienced that. What version of NPM do you use?
-
I've not done this but this may help you. http://thwack.solarwinds.com/thread/29526
-
How many ports are you licensed for? Is it a case of trying to monitor more ports than your license allows?
-
One time I couldn't log a ticket on the Solarwinds website so I emailed customersales@solarwinds.com & maintenance@solarwinds.com. I got a reply from maintenance that logged a ticket for me. I've not rung them as they're not in Australia. This bit is in their email footer. Maybe email them as well. " If you have any…
-
I ended up changing the hop count to 0 so that the scan wouldn't take as long. So now I just have the 1 scan and it completes in the allowed timeframe.
-
Vous devez vérifier votre état paramètre Mode Rollup . Et le changer pour " spectacles d'état mixtes d'avertissement" . J'ai utilisé google traducteur pour écrire ce post , je l'espère , il est logique .
-
You can download it from Microsoft. Just search in google for Microsoft mdac. 2.8 seems to be the current version.
-
Best way to scan is to have a separate network range for your network devices, that way it will only discover devices you're interested in. If your network devices are just mixed in the ranges with computers etc, then you'll have to scan the whole range. But once you've done a scan, tick all the all the devices you're not…
-
The default community string is public. But it's normally the device that has the community string configured on it, not the wireless lan card.
-
What have you configured in each of the tabs of your discovery profile? Obviously discoveries can take a long time depending on what you have configured. Also adding to the Hop Count will cause it to take a long time. If you say set 1 IP range x.x.x.x/24 and with a Hop Count of 0, then the discovery shouldn't take too long.
-
I use the following syntax to just show me certain interfaces on certain devices. sysname like 'SWITCH1%' and interfacealias like '%Core%' or sysname like 'SWITCH1%' and interfacealias like '%Dist%' So in this case if will show interfaces on SWITCH1 that have either Core or Dist in the interface description. The % sign is…
-
The interface name should update automatically on the next poll. If that's not happening, then maybe the interface name has been set manually within "Edit Interface" in Solarwinds. In that case if you do a List Resources on the node within Node Management, it will grab the actual description on the interface. Submit that,…
-
Have you seen this? Success Center 1) See above link 2) Not sure 3) In a non-changing network, I don't see a real issue with setting the polling time higher than the default. I've always just left it as default. 4) In think it was an issue with older versions of NPM. These days it all works as intended. I also found this…
-
It's using a flux capacitor
-
You can do this with UDT (if you have it). Or you can do this with NPM provided you are monitoring all the ports in the switch. You then create a report that shows all unplugged or down interfaces and specifies how may hours they've each been down for.
-
Easiest solution would be to email from Solarwinds to Jira and have Jira create a ticket from the email. Creating issues and comments from email - Atlassian Documentation
-
I do this as part of my config download jobs. Once a week I download the startup configs, then 1 hour later I download the running configs and as part of that job I compare it to the last downloaded config which in this case is the startup config. It then emails me all the difference details of those configs that don't…
-
I think these 2 links will answer your questions. How Does Orion Mark a Node as Down? Calculate node availability
-
I don't believe emails are queued up. So if the event has passed and all is green, then no emails should be sent.
