Lots of user still looking for the Universal Device Poller as a solution on thwack therefor adding the post below.
In order to monitor Big F5 Resources you no longer relay on Universal Device Pollers as following resources will be monitored default in Orion and will be presented in Graphs as below.
List of Virtual Servers Resource
List of Pools Resource
List of Nodes Resource
Connections
Requirements are Following OID's should be present within the device MIBWALK in order to assign the default poller.
List of Virtual Servers Resource
| MIB | Object Name | OID |
|---|---|---|---|
| Name | F5-BIGIP-LOCAL-MIB | ltmVirtualServTable:ltmVirtualServName | 1.3.6.1.4.1.3375.2.2.10.1.2.1.1 |
| Address Type | F5-BIGIP-LOCAL-MIB | ltmVirtualServTable:ltmVirtualServAddrType | 1.3.6.1.4.1.3375.2.2.10.1.2.1.2 |
| IP Addr | F5-BIGIP-LOCAL-MIB | ltmVirtualServTable:ltmVirtualServAddr | 1.3.6.1.4.1.3375.2.2.10.1.2.1.3 |
| Port | F5-BIGIP-LOCAL-MIB | ltmVirtualServTable:ltmVirtualServPort | 1.3.6.1.4.1.3375.2.2.10.1.2.1.6 |
| Enabled State | F5-BIGIP-LOCAL-MIB | ltmVsStatusTable:ltmVsStatusEnabledState | 1.3.6.1.4.1.3375.2.2.10.13.2.1.3 |
| Availability State | F5-BIGIP-LOCAL-MIB | ltmVsStatusTable:ltmVsStatusAvailState | 1.3.6.1.4.1.3375.2.2.10.13.2.1.2 |
List of Pools Resource
| MIB | Object Name | OID |
|---|---|---|---|
| Name | F5-BIGIP-LOCAL-MIB | ltmPoolTable:ltmPoolName | 1.3.6.1.4.1.3375.2.2.5.1.2.1.1 |
| Mode | F5-BIGIP-LOCAL-MIB | ltmPoolLbMode | 1.3.6.1.4.1.3375.2.2.5.1.2.1.2 |
| Enabled State | F5-BIGIP-LOCAL-MIB | ltmPoolStatusTable:ltmPoolStatusEnabledState | 1.3.6.1.4.1.3375.2.2.5.5.2.1.3 |
| Availability State | F5-BIGIP-LOCAL-MIB | ltmPoolStatusTable:ltmPoolStatusAvailState | 1.3.6.1.4.1.3375.2.2.5.5.2.1.2 |
List of Nodes Resource
| MIB | Object Name | OID |
|---|---|---|---|
| Name | F5-BIGIP-LOCAL-MIB | ltmNodeAddrTable:ltmNodeAddrName (for BIG-IP SW Ver 11.2+) | 1.3.6.1.4.1.3375.2.2.4.1.2.1.17 |
| Address Type | F5-BIGIP-LOCAL-MIB | ltmNodeAddrTable:ltmNodeAddrAddrType | 1.3.6.1.4.1.3375.2.2.4.1.2.1.1 |
| IP | F5-BIGIP-LOCAL-MIB | ltmNodeAddrTable:ltmNodeAddrAddr | 1.3.6.1.4.1.3375.2.2.4.1.2.1.2 |
| Enabled State | F5-BIGIP-LOCAL-MIB | ltmNodeAddrStatusTable:ltmNodeAddrStatusEnabledState | 1.3.6.1.4.1.3375.2.2.4.3.2.1.4 |
| Availability State | F5-BIGIP-LOCAL-MIB | ltmNodeAddrStatusTable:ltmNodeAddrStatusAvailState | 1.3.6.1.4.1.3375.2.2.4.3.2.1.3 |
Connections
| MIB | Object Name | OID |
|---|---|---|---|
| Connections Total | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatClientTotConns | 1.3.6.1.4.1.3375.2.1.1.2.1.7 |
| Connections Current | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatClientCurConns | 1.3.6.1.4.1.3375.2.1.1.2.1.8 |
| Connections SSL | F5-BIGIP-SYSTEM-MIB | sysGlobalClientSslStat:sysClientsslStatCurNativeConns | 1.3.6.1.4.1.3375.2.1.1.2.9.4 |
| Connections SSL Current | F5-BIGIP-SYSTEM-MIB | sysGlobalClientSslStat:sysClientsslStatCurCompatConns | 1.3.6.1.4.1.3375.2.1.1.2.9.7 |
Throughputs
| MIB | Object Name | OID |
|---|---|---|---|
| Client Bytes In | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatClientBytesIn | 1.3.6.1.4.1.3375.2.1.1.2.1.3 |
| Client Bytes Out | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatClientBytesOut | 1.3.6.1.4.1.3375.2.1.1.2.1.5 |
| Server Bytes In | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatServerBytesIn | 1.3.6.1.4.1.3375.2.1.1.2.1.10 |
| Server Bytes Out | F5-BIGIP-SYSTEM-MIB | sysGlobalStat:sysStatServerBytesOut | 1.3.6.1.4.1.3375.2.1.1.2.1.12 |
How can i confirm the below OID's are available under the device.
Please run the below MIB Walk tool and search through the MIBWalk out put.
Download Zip File from below link on Orion Server desktop
http://downloads.solarwinds.com/solarwinds/Release/PreRelease/SolarWindsSnmpWalk.zip
Run SNMPWalk.exe
Enter ip address of the Node under "Agent Address or DNS name >
Select Version " 2c / or 3 " Depending on the Node configured .
Enter the " community String" configured for the device .
Click on " Scan "
Wait for the finish and save the .Txt file open and search if you are able to locate the above OID's within the device MIB.
- If you still have the issue please open support ticket -