Ok. So I’m back at it now.
The first step of this mulligan was to remove the activated license from the corrupted windows box that caused me all the trouble in the first place.
While I deploy a brand new Windows 2012 image, I headed over to the solarwinds website and read through this document. As detailed in the doc, I installed the licensing application. Deactivated the NPM license and everything went as great.
Good news so far. I’m really looking forward to start digging into how NPM manages HP Networking gear.
So after the fiasco of the last attempted install. I learned a couple of things.
- The Solarwinds NPM install package from the customer portal does NOT include the embedded Microsoft SQL server. If you want to run this with SQL express, then you need to install the eval version. Good thing to know if you are trying to install NPM in a smaller environment. Keep in mind though, it is STRONGLY recommended – I read it multiple times in the docs – to use an external SQL server when using NPM in production. This makes sense for a “real” network, but for my purposes, I have a small lab so there’s really no need.
- My Windows image was hosed. screwed. burned out. totally useless. When I did the install on a brand new Windows 2012 server, it went totally smooth. I pre-installed the IIS server, as mentioned in the docs, and everything else went off without a hitch, so much so that the only reason I’m mentioning it is the fact that I had so much trouble the first time. The blame for that one goes on a bad windows build.
It’s been a couple of years since I was at the helm of an NPM box, but to be honest, it feels pretty comfortable. Having a lot of sticktime on some other products, I had a bit of trouble with getting the desired results from the discovery process ( IP ranges vs. Subnets didn’t do exactly what I wanted – I kept getting more ranges that I wanted to. ) but after a few tries, I managed to get the initial discovery up and running without any trouble.
In general. The discovery process went smooth. Interestingly, NPM asked me for windows, vmware, telnet/ssh, and SNMP credentials. The nice thing, which kind of surprised me, was that NPM was now able to discover my VMware ESXi and vCenter servers. This is a good thing as I’m a big fan of providing a consolidated view of the entire network, whether that’s physical or virtual, wired or wireless. I’ll check later into what Virtualization support is actually offered in NPM, but for now, I’m happy to see that I can at least identify the resources on my network.
The not so good:
There were a couple of mis–labeled devices. Specifically, the HP 5500EI and the HP 5120EI which are a couple of boxes that have been in the market now for a few years. As you can see from the images below, both of these devices are HP devices. The description ( which is pulled directly from the device through the sysdesc OID ( .126.96.36.199.188.8.131.52.0 for anyone who’s counting ) does show that this is an HP device.
On the bright side, the error has been submitted to the NPM unknown device thread here so hopefully this will be addressed in a future update.
In previous versions of Solarwinds, one of the things that did bother me was having to jump back and forth between the web interface and the windows console depending on the task that I needed to accomplish. I know Solarwinds has done a lot of work to move all the administrative functions into the web interface, but it doesn’t look like Network Atlas has made the cut yet.
This is first glance, so it’s possible I just haven’t clicked on the right button yet. One of the most powerful pieces of a good NMS is an accurate topology map. Now that I’ve got the network discovered and up and running, creating some network maps are going to be my next task.
In general, Solarwinds feels familiar. It’s not too far removed from the versions I was more familiar with so I’m hoping that digging in is going to go more smoothly. I’m also VERY happy that I’m over my initial install issues. That was a painful experience and it’s nice to be able to say I just had a corrupted windows build. The new install went perfectly. I’ve been spending some time upgrading my lab to ESX 5.5 this week, as well as playing with the HP SDN Controller as well, so I might take a break from Solarwinds for a bit, but expect more info in the future as I start to spend some more time with NPM.