we have 2 F5's in Production - when the LB admin did an upgrade this past Monday - while on his end both f5's were up and running as expected but in Orion the Primary F5 basically become a brick .. status Unknown and status reason LTM is in an unknown state and of course was not reporting on any virtual servers or Pools and Pool Members. How could I alert on this same type of scenario again? I did look to set up a new alert for an F5 devices but didn't see any drop down choice to key off of.
You may need to play around with an f5 to see which particular status is the one you need to trigger on, but I *think* the Orion Status would be your best bet for the LTM Server.
Screenshot from NPM 12.1
zackm so this was the strange part - the node itself was up and responding to SNMP but the F5 stuff wasn't sending any info back - i had the F5 eng start with restarting the snmp service to see if that would resolve it and it did. This all happened after he upgraded the version on the f5
If you run this against your database, you can see the various sources of data for the LTM Server object:
SELECT * FROM F5_LTM_Server_V
The reason I think you need to use the "Orion Status" object, instead of "F5 Status" is precisely what you mentioned re: SNMP failing. Almost exclusively, the 'Unknown' status for all objects in Orion is reserved for one of 2 scenarios:
What I think happened to you was that after the F5 came back online, the SNMP service was in a faulted state. The next time Orion tried to poll that device, SNMP failed, which resulted in an Unknown status.
If that assumption is accurate, then creating an alert like I mentioned before, using the "Orion Status = Unknown" as a trigger, should alert you to a similar problem in the future.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.