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

What about a modification of Tip #3 from this page? https://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2015/03/12/cutting-down-on-alerting-noise… It seems like a complex alert with 2 parts, one for each unit might do the job. Just modify it do work with your 2 custom pollers.

Thankfully, I did all of my CompTia certs back before they started requiring re-certification. My SolarWinds cert is old now and maybe should be refreshed. I should re-aquire my Cisco certs sometime. I should be able to pass several Cisco certs given I have had CCNA and CCNP in the past and specialized training in Cisco…

We saw this issue one time when there was a corrupt alert in the database. SolarWinds support had to assist in finding directly in the database tables and getting it deleted.

I have been trying to get !Cisco WLC clients count per SSID by Ovad‌ working, but I have not had much luck yet.

I had something like this happening in July. I couldn't list resources on either new or current nodes. I applied Orion Platform v2015.1.2 – HotFix2 and the problem went away for me.

I have seen that error for two or three conditions. * The device is off. I have that happening with some backup/shelfware switches. * Credentials or protocol used for backup failed. * Is there an ACL/firewall blocking the connection? So the questions are: Which protocol are you using and does it work with a client…

The SUP6L part is talking about the supervisor card in the chassis, the brains of the chassis which contains operating code. We traded in our old Sup6 card for a Sup7 card a couple of years ago in order to support a newer multi-port fiber card like you are mentioning. It may be that the 24 port fiber card isn't supported…

Mine is located in C:\Program Files (x86)\SolarWinds\Orion\NPM

We are in process of setting up an F5 with additional web servers. We had one AWE, and SolarWinds support looked at the active connections and recommended we needed 3 more AWEs. All 4 will be placed behind the F5 once that configuration is complete. We have installed and tested the new web servers already, we are just…

I don't have a good answer for you, but I have a Cisco ASR 1002-X node showing 19 VRFs. We have a single management IP on a loopback that we monitor that node with. We don't look at separate contexts. I am sure we have more nodes like this, but that is the quick one I knew about.

Are you seeing the same or similar thing as in this thread? SolarWinds.InformationService.ServiceV3.exe - Railing a single processor?

I think I know which template you may be using and that does seem a bit limited. It could be modified if we learned the language it uses. Or it might be easier to push a script under Configuration Management. Of course by that time, you could have configured those two descriptions from the CLI. I really liked being able to…

I think we did find an SNMP OID that matched our intentionally idle states. I was able to make a UNDP for this OID, but I can't figure out how to use the alert GUI with the built in alert to use it as a filter. This is from Cisco's SNMP Object Navigator. SNMP walk against a couple of routes on one of our routers looks like…

Bump

I have been trying to figure this out as well, not only for BGP, but also for OSPF and EIGRP. Basically I get from our WAN team that they know there will always be idle BGP links, waiting to be used in a backup scenario. I think what they really want is an alert for when a BGP link drops from Established. Not any that are…

The built in EnergyWise reports may also have some of this information as long as you are collecting the data.

I have the 'chassis' and blades added. Our blades added just fine and I think they are reporting the right data. But by chassis, I mean the management IP of the primary Fiber Interconnect, or more accurately the UCS Manager web GUI IP, which is on the primary Fiber Interconnect. When I add the individual IPs for the Fiber…

I have had to turn off the auto-import due to this issue. It kept importing unwanted/undesired interfaces when it broke my interface selection settings. We have not fully automated server imports, so that was unaffected for us, but I can see where that would be an issue as well. I will be looking forward to this getting…

You won't see the node name in the summary as shown, but you can include it in the alert action itself. I use UNDPs to alert on APC UPS SmartTrim status and this statement in the alert works. Just use the insert variable tool to get the right variable for your instance. Set up the text around it as you want. ALERT: Node…

That can be confusing because they didn't put the SAM credential library in the same place. Go to Settings > All Settings > Sam Settings and look under Global Sam Settings for the Credential Library.

I still see a 26 point difference between the leader board and next to my login at the top of the page. That is an odd number, no idea why that difference.

I have not seen it trigger while changing alerts for some time, and I have made changes. One new alert I was working on I changed yesterday and found I needed to disable/enable to trigger it again to see if it was working as expected.

Part of this may depend on company policy, other parts on efficiency. In my previous job, we were required to use AD authentication for all apps, including SolarWinds so that password policy was maintained, and additional username/passwords were not required. Where I am now, AD groups are far more efficient. We are a very…

I believe there are a couple of threads on this. Alert - Responding to SNMP? Can we alert for SNMP not responding nodes?

bump

bump

I have a similar problem, but it is a little different. The maps update fine on the main engine, but do not update on the additional web server. I have not looked to see if the above solutions will fix this yet.

bump aLTeReGo​cobrien​

I have not had discoveries fail the discover part unless there was a problem with the credentials, firewalls/acls, or poller issues. I have had occasional problems with imports, where the discover worked fine, selected what the import including interfaces, and the import claimed to be successful but the nodes were not…

For me, that came down to the device type falling to just Cisco, not a specifically identified model. I had to look at the admin views by device type settings and make sure that was not on "(default)" but set to "Node Details - Summary". That fixed the problem for me.