jhandberg · Enterprise Event Monitoring Engineer · ✭✭✭✭✭

That was a little over 3 years ago now, and I am at a different job. The 3-PAR admins were mostly concerned about up/down notifications. I don't recall what else we got on them back then. You could try doing an SNMP walk or look through 3-PAR documents for SNMP OIDs to built up some UNDP polling.

I would like to get there for SolarWinds. But I am just as interested in getting the larger Enterprise SQL set up better. SharePoint's database and several other databases would benefit. It's all well and good to use RAID 5 for other things like backups, but SQL could benefit from different storage management.

I will look forward to your bigger writeup on this. I have tried time and again to convince our storage admins that we need to have some RAID 10 for our SolarWinds and Enterprise databases, but he won't budge even when I send links outlining the benefits. He just refuses to believe there could be a bottleneck there. He has…

I am sure the answer is yes, and that I had done that at my last job, setting them all to a specific date. I don't have access to NCM on this new job so I can't go through the steps.

That is nice, but our text file of baseline switch config wouldn't necessarily include all the access port VLAN settings. It would just include all the basic configuration bits like a standard ACL, NTP Settings, SNMP Config and such. Not the port level settings, which would vary depending on where the switch was deployed.…

I went through them one by one. They are all 3560 v2 switches. Another interesting note, when I have NPM group the nodes by Machine Type, it puts these 3560 v2 switches and our C1250 N autonomous APs in a generic "Cisco" Machine type, like it doesn't really know what to do with them. All the other different types of Cisco…

The components are usually targeting something else like an application component on a server node. So a server could be up, but there could be something still wrong with it. Another possibility is a hardware component, say a power supply sensor on a network node. This is more like what we are using here.

Not really, at least not in all cases. I have this situation going on right now due to a cut fiber somewhere. The BGP down alerts that have fired originate from a different router, but cross a couple of routers to get to the end point. The physical link is broken somewhere between, not at the point the BGP failed. It also…

My node down does have one of the Status parts in it, but I guess I didn't realize parentheses were allowed. They are not in the examples. That may help some of my more complex filters.

This is exactly what I have had to do in the last month for some special views for both nodes and interfaces when one group or Agency wanted more limited information for just their devices vs all enterprise devices.

This sounds similar to my troublesome connections. In this case, I am looking at remote sites that have single DSL connections to the internet. There are VPN tunnels back to 2 upstream aggregation routers, and multiple routes through each VPN tunnel going to the upstream routers. I believe the multiple routes to each…

This is the set of Pollers I have been using.

I was able to limit the scope to nodes with a specific Custom Property setting. I have not figured out the filter per vendor yet, but it may be similar. Near the beginning of the query i added my custom property resource: select distinct n.caption as [Server Name] -- Added custom property to include from original code…

Restricting users to specific views with specific subnets in them is what is currently requested. Or possibly restricting the ability to change subnets a group of users are not responsible for would work for our organization. I suspect though that some of the agencies will only want to see what is theirs in views.

We are still seeing some high CPU on our SQL server due to a built in query. I have a couple of other open issues, but these may not be related to the upgrade.

I suppose I should add we are not monitoring this interface, and it is currently in an Admin down state. We are monitoring Gi 1/0/12 and that port isn't having any problems. I think there are other interfaces we are monitoring that have the bias sensor issues though.

I have an awful lot of those sensors to turn off if I get buy in from the networking group. I almost wish that these apparently unreliable ones were off by default.

I also have a couple of power supplies (or fan power) doing something like this where the fan section show a bad power supply in them one minute, then no supply the next. The networking team here swears there is nothing wrong when they run the Cisco CLI to check it. I have screen shots of it there one time and not another.…

It turns out, the Orion Platform Hotfix2 actually fixed my issue. Good insight humejo‌. Now the NPM is working again, I need to upgrade NCM and SAM.

I don't see that resource as an option on the summary views.

Yes, there is a way to classify an AP detected as a rogue. As an example, our college campus has a Cisco course that uses an AP in the coursework. I can go in and classify it. First find it in the list of rogues. Then click the drop down like I have below. You can select how to classify the rogue. In the case of the…

In order to really become the de-facto industry standard for that arena of 'monitor engineer', the certification would pretty much need to be vendor agnostic. Specific solutions in SolarWinds may also exist in other product, but may be named differently, or have a completely different configuration. If your company was on…

I have received a very small handful of queries about SolarWinds due to having listed SolarWinds and my old SCP on my LinkedIn profile. Only like 4-5. It was about 50/50 on advice or asking if I was interested in a job which would require me to relocate.

It looks like were are on the same page on this one.

I have a partial answer to the Cisco OID piece. 1.3.6.1.4.1.9.9.23.1.2.1.1.6 - This lists neighbor devices by hostname. 1.3.6.1.4.1.9.9.23.1.2.1.1.7 - This lists interfaces the neighbors are on. Now the tricky bit.... .1.3.6.1.4.1.9.9.23.1.2.1.1.6.10101.44 = STRING: "hostname" <- This is a neighbor switch…

We had a script that deleted anything older than 2-3 years. We figured the hardware replacement cycle on the network made anything older less useful.

+1 for that suggestion. That is what I did on my last job. I actually configured the archive location to a network storage location and made sure that is in the server admins backup process. This meant that even if my SolarWinds instance was totally destroyed for any reason, I still had daily configs to refer to if…

The difference is all the false alerts we were getting. Example: You have an SFP based fiber port and unplug the patch cable, you get current and voltage alerts because the SFP is still there. It still draws a tiny bit of current, but the sensor goes critical for under current conditions to support the laser for the fiber.…

I eventually corrected my problem by changing the default view type for the 'generic' Cisco device types in the admin settings. The devices in this default Cisco object type are still not fully or correctly identified by device type, but at least I am back to the Node Details Summary page I really need for these devices.

I shared a resource I have built to look at our current users across 4 web servers behind an F5 in our environment. This does involve applying AppInsight for IIS against the additional web servers.