superfly · Senior Network Engineer · ✭✭✭✭✭

Is there any update on the issue? Are all the switches that hang the same type and same IOS?

You can create a rule on the syslog servers that "Log the Message to a file" or "Forwards the Syslog Message". Either one of these 2 options should help you in your goal.

If you are talking about just a page view in Solarwinds, you can do the following. First add a common unique word to all the interface descriptions you are interested in seeing on the view Then create a Summary view page. Add in 'Percent Utilization of All Interfaces" into your view. Open up the Page and click the Edit…

What does it display in the Current Percent Utilization of Each Interface window?

I don't think the alerts will be on the exact same time when you include the seconds field. So first alert is 10:52:05 and the next is 10:52:15 etc. An interface goes into warning when a ping doesn't get through. Is this interface particularly busy? Or does Solarwinds go through a "slow" path to get to this interface?

Are all your services up and running? Have you tried rebooting your Solarwinds server?

Try just downloading the installer for VNQM 4.4.1 and run that. If still no luck, then remove VNQM 4.4 and run the installer again. I had a similar problem with the new installer and VMan version 7. I had to remove VMan first and then the new installer would run ok.

Why do you just create an alert for this? That way they get an email alerting them to the issue rather than having to look at a screen. And if you have netflow, you can include a link in the email straight to the interface in netflow so that you can see who's causing all the traffic.

The discovery process will list out all the devices it has found and whether or not they are "new" or "changed" nodes. Changed nodes are ones that already exist in Solarwinds. But nothing changes to the nodes until you import them into Solarwinds after the discovery process has completed. When you import them, you can…

There are a number of stack related alerts included as out-of-the-box alerts. The custom alerts I use for switches is based on syslog messages. So things like power failure, temperature, eigrp changes etc, I alert on that.

I don't use ConnectNow as I find that it doesn't always get the links right but there are 2 notes for ConnectNow to work. They are * The ConnectNow tool cannot create indirect connections. For example, if the map objects A and C are connected indirectly through device B, you must manually add device B to the map to create…

It is uploaded to the running config. Tick the box "Write to NVRAM" if you want to save it to the startup config as well.

If you don't want to monitor the workstations, the easiest thing to do is to just delete them out of NPM. That way you'll receive no information from them anymore.

If you manage all your nodes using a Global Connection Profile, then you'd only need to change the password in one place e.g. Manage Windows Credentials. But if you are putting in a username and password on each device when you manage it, you will need to change the password on each device.

If you change the name in Manage Nodes, then the name will stay that way forever (unless of course you change it again).

Yup as mentioned above, that will be fine.

I would try adding the group by using an user name that has administrative access to the AD. That should work.

What I used to do was, was to send the alert to an opsgenie email address, which in turn would SMS or email it to the oncall person. The oncall person was determined in the opsgenie roster.

It seems that the colours are buildtin. You should log a case for it, maybe there's a way to change it in the database itself. But the colours are different as Red means Down and Orange means Critical.

You need to monitor something that goes down when the link goes down. Then the link will go red. I have all my links coloured as green to symbalise that they are up. But they go red when the link goes down. Just right click on the link in Atlas and in the Status setup just add the node or interface that goes down when the…

Go to Device Tracker and select Ad-hoc Reporting. Just will in the wild card in the top right hand corner and press enter. It then gives you all the info you need, plus there's an export to Excel option.

Hahahahaha, you have too much time on your hands! Thanks for the smiles

Go into syslog viewer Select Syslog, My Custom Rules Create New Rule Configure up the rule and this includes creating an alert for the rule. Once finished, open up the alert and in the trigger email, use the following in the email body. ${N=OLM.AlertingMacros;M=OLMAlertMessage.EventMessage} That sends the whole syslog…

I'm running NCM 7.3.2 with no issues. My path is C:\Program Files (x86)\SolarWinds\Orion\SolarWinds.NCM.RTNForwarder.exe ${IP_Address},RealtimeNotification,${DateTime},${Message} Make sure the exe exists in the folder. Also double check your settings in Admin, Settings, NCM Settings and then select Real-Time Change…

You can't have a common view for each customer that then shows different information. You would need to create a view per customer that would only have access to "their" devices. You can certainly duplicate the 'original' view and then modify the restrictions as applicable for that customer.

We back up our F5 UCS files via NCM but we can't do version control. This is a copy of our script (I've removed the IP address of our SCP server, replaced with x.x.x.x). We run SFTP/SCP process on our Solarwinds server and it's setup to allow any user access (no password required). The script also removes all previous ucs…

Pictures are better than words This should be enabled This should be disabled

Have you checked those devices with the Orio at the start what the actual system name is? Remember system name and display name are not necessarily the same.

Are you talking about these? Just add them into the Interface view. If you like on the edit button, you can change the look of these dials.

Use %user kelly%