donpepe

Theres a few ways you could tackle this. I would look at DHCP client name, MAC address, or make your own custom property. I normally have a custom property and do all my alerting out of NPM for up/down. Much more elegant. But if you must distinguish between the two if you use a certain naming convension the DHCP client…

Im being silly. The VNQM 4.2 upgrade states in the release note that they add support for Version 10.

Ive had this happen a few times before. Its a corrupted service. The fix involves going into add and remove programs. Uninstall the information services program. Then reinstalling it from the individual installers thats hidden in the file system. I dont remember where it is, but if you open a ticket they can show you where…

Then again, this guy tested it and he says it works just fine.

I asked that question recently. The short answer is we have some waiting to do.

I don't believe so? I guess it depends. The Solar Winds server will log everything in its local time. CST as you stated. It will not use the routers or switches local time. Are you trying to achieve relevance in time for the local support team or the remote team in this scenario? 

Been using third party ones. Saved a ton of money and yet to have a failed one. Its been a little over a year since i switched.

Network atlas can. Make sure that you import the nodes using discovery then use the ConnectNow feature in atlas. Here is a short guide on doing that the rest of the process. http://www.solarwinds.com/netperfmon/solarwinds/wwhelp/wwhimpl/common/html/wwhelp.htm?context=SolarWinds&lang=en&file=Or… As for your second question…

One update. Passthrough authentication is working now magically. So im only stuck on issue two.

I would personally like to see better native support for PTP wireless radios.

That's a tough one. The way we do it is we use custom properties for alerting and groups for reporting. The reason for this is the alerting is much better tied into the nodes than groups. If i want to group together several nodes ill use a custom property for this same reason. Sorry I'm pretty sure this isn't exactly what…

I have the same issue...

When my server ran slow we were able to speed things up by doing two things. Making sure we had the latest and greatest version of all the modules (helped alot!) and we identified issues with the communication between the web front end and the database in the front ends event log. It showed plenty of time outs waiting for…

Simply no. Your network confiugration should be very intentional. Having it change automatically is asking for trouble.

If you go into the advanced alert you can insert variables into the text which change dynamically depending on the alert. To get the URL of the node all you would have to type is "${Node.NodesDetailsURL}" For example if i wanted to make a link to hop from the email straight to the node which went down i would add: <a…

What i do is i have a visio that shows all the racks. I take a screen shot and make it my background. Then I paste in the servers over the the rack to show what is actually there. Then I use a node LED to show the status of that device next to it.