Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Problem Adding F5 Big IP System

I am having problems when trying to add an F5 Big IP system into Orion NPM. NPM is not able to determine the name of the device, what type of device it is, nor is it able to determine that the vendor is F5. Those fields are all blank.

From what I've read it looks like F5 does not put all of this standard information into the MIB-II but instead puts it into their enterprise MIBs but I still don't have a real good understanding of MIBs and SNMP from that perspective so I may not be understanding their documents correctly.

In any case, has anyone had any experience in trying to add a Big IP system from F5 into Orion NPM and been able to successfully pull this information?

If I can get NPM to recognize the vendor, then I can build a custom view for these devices which will allow me customize the information presented since I can't get an interface list or monitor CPU utilization through the standard MIBs but again must rely on their enterprise MIBs.

Find more posts tagged with

snmp_mib_f5_big_ip

Accepted answers

RodNC

Ok...I have the answer. It turns out I interpreted the F5 documentation a bit too literally when doing the initial configuration and I set it up on the Big-IPs so that NPM could only poll the F5 enterprise MIB.

Once I relaxed my config a bit and specified an OID of just ".1", everything took like a charm, although I had to delete the current devices and re-add them.

I guess that's what you get when you hand a newbie the books and tell him to add a new device to NPM!!

All comments

SamuelB

My F5 Big IPs are detected without a problem.

What version/SP of Orion NPM are you running?

What is your Big IP model and software version?

Have you downloaded the latest copy of the MIBs (available in your customer portal)?

brian_duvall

If you are running old 4.5 code on F5..the vendor will not detect as F5. I believe mine detected as a Linux box.

If you are running v9 code, you should be ok and you may want to check your Orion install.

RodNC

We are running Orion NPM version 9.0 SP2.

The F5 is a Big-IP 8400 running version "BIG-IP 9.4.4 Build 73.1 Hotfix HF1".

When I poll it with NPM I get a response but the "Machine Type" is "Unknow", it does not recognize the vendor, and other SNMP standard information such as "System Name" and "Location" is not populated.

Also, I am not getting a reading on the CPU utilization on the Node Details view.

If I could get NPM to recognize the vendor in this case, I could change the default view for the device and customize it with the different pollers, which would fix a lot of my problems.

brian_duvall

That is odd. I don't personally have 8400's so possibly the System OID is not mapping correctly. I am running Orion 9.5 and have 3600's running version 9 code and it detects without issue.

jlintner

I have some Big IP 6400's and they were identified properly. They are running version 9.3.1, and we are using SNMPv3.

RodNC

Once I relaxed my config a bit and specified an OID of just ".1", everything took like a charm, although I had to delete the current devices and re-add them.

I guess that's what you get when you hand a newbie the books and tell him to add a new device to NPM!!

DirtySouth

For those of you monitoring F5's right now with NPM, what type of information are you able to poll? CPU, memory, interface utilization? Any custom pollers? I'm curious because we have several F5's that were not currently monitoring via SNMP.

Thanks

drew999999

I have a few custom pollers setup which gather virtual, pool, and member status. I'm also gathering some historical traffic stats on the virtuals.

I don't really care for the way that F5 has their mibs laid out as it's not easy to link the members back to the pools, or the pools to the virtuals.