Getting the following error when running the code line by line - something to do with “GET not implemented”? Is there something I need to enable on the F5?
I’ve been testing with the free ABC MP, however we went back to the HYCU F5 Big-IP MP for SCOM.
This because we also want to monitor Certificates,…
When we tried to add more oid to monitor, we had troubles finding the correct mib/oid. Next
to that we also use SNMP v3 and base SCOM network monitoring.
The problem is that we do not allow ICMP Ping to our F5 devices therefore when these two scripts run they check to see if the hosts specified in the F5-BigIP-Hosts.csv are up via Test-Connection (PING)
F5-Discovery-rest.ps1
F5-Discovery-snmp.ps1
I have amended the code on both scripts for where the scripts do a PING check:-
Hi Ruben, The issue with the Appliance name was an error on my part – I didn’t extract the MIBs into the correct folder…
I wonder if you could shed some light on this issue?
We have 2 F5’s in site PW and 2 F5’s in site PB. I started setting up Site PW with WatcherPW (Server running script) – see below Fig 1 showing a health state for both PW1 and PW2 but nothing for BP1 and PB 2 as I have turned off the schedule on WatcherPB (Server running script)
After PW1 and PW2 were completely discovered and health state up-to-date I enabled the Schedule for Site PB to discover PB1 and PB2. See Fig 2 below – Now the health state for PW1 and PW2 have been discarded and PB1 and PB2’s health state is being represented. This has been like this for a few days and both site schedules are running perfectly.
It would seem that this applies to all the group health statuses – Node Addr Group, PoolsTatus Group and TrafficGroupItem Group
It seems the MP can’t represent both sites group statuses at the same time?
not sure if I understand you correct. Please confirm
You firstly exported the information for the first set of F5 waited until they have been discovered. Then you changed the scripts to discover the second set of F5 is that right?
If so I know the reason for the problem. You need to keep all F5 appliance been discoverable. - Configuration files and CSV need to keep. If you don’t SCOM will purge them from the database.
I have tried the hostname. What protocol and port does the script use to talk to the F5 device? I know port 161 and 162 need to be open for SNMP and port 443 but what else do I need?
Is it that you couldn’t find the actual MIB OID? If so you could use a utility called a MIB Browser from Manage Engine to do an SNMP Walk. Then you’ll be able to see what OID you need.
Had to allow ping from Monitor & SCOM Server to F5 and vice versa. The MP now seems to be working - For some reason the SystemNodeName isn’t being populated
Hi Ruben,
I have attached a Diagram to explain our environment.
Basically, we have two sites. One SCOM environment 2 SCOM servers per site and one SCOM Watcher server per site. Each Watcher server in turn run their own discovery against the F5’s and the agent feed the information back into the SCOM environment. - Hope that makes sense?
I use these Watcher servers for Skype For Business as well to run synthetic transaction etc