This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Monitoring Big F5 Resources - List of Virtual Servers Resource - List of Pools Resource - List of Nodes Resource- Connections

This article will help you to understand the F5  Big f5 polling and OID's in details as  following resources will be monitored default in Orion and will be presented in Graphs as below.

Firstly

Please Note:  You must enable Provisioning for LTM and GTM in the device if this feature is disabled on the device configuration the below information will not be collected from the device therefor make sure the LTM & GTM are enabled .

For more information please see the below vendor page.

AskF5 | Manual Chapter: Integrating BIG-IP LTM with BIG-IP GTM Systems

Capture.PNG

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

NameF5-BIGIP-LOCAL-MIBltmVirtualServTable:ltmVirtualServName1.3.6.1.4.1.3375.2.2.10.1.2.1.1
Address TypeF5-BIGIP-LOCAL-MIBltmVirtualServTable:ltmVirtualServAddrType1.3.6.1.4.1.3375.2.2.10.1.2.1.2
IP AddrF5-BIGIP-LOCAL-MIBltmVirtualServTable:ltmVirtualServAddr1.3.6.1.4.1.3375.2.2.10.1.2.1.3
PortF5-BIGIP-LOCAL-MIBltmVirtualServTable:ltmVirtualServPort1.3.6.1.4.1.3375.2.2.10.1.2.1.6
Enabled StateF5-BIGIP-LOCAL-MIBltmVsStatusTable:ltmVsStatusEnabledState1.3.6.1.4.1.3375.2.2.10.13.2.1.3
Availability StateF5-BIGIP-LOCAL-MIBltmVsStatusTable:ltmVsStatusAvailState1.3.6.1.4.1.3375.2.2.10.13.2.1.2

List of Pools Resource

MIB

Object Name

OID

NameF5-BIGIP-LOCAL-MIBltmPoolTable:ltmPoolName1.3.6.1.4.1.3375.2.2.5.1.2.1.1
ModeF5-BIGIP-LOCAL-MIBltmPoolLbMode1.3.6.1.4.1.3375.2.2.5.1.2.1.2
Enabled StateF5-BIGIP-LOCAL-MIBltmPoolStatusTable:ltmPoolStatusEnabledState1.3.6.1.4.1.3375.2.2.5.5.2.1.3
Availability StateF5-BIGIP-LOCAL-MIBltmPoolStatusTable:ltmPoolStatusAvailState1.3.6.1.4.1.3375.2.2.5.5.2.1.2

List of Nodes Resource

MIB

Object Name

OID

NameF5-BIGIP-LOCAL-MIBltmNodeAddrTable:ltmNodeAddrName (for BIG-IP SW Ver 11.2+)1.3.6.1.4.1.3375.2.2.4.1.2.1.17
Address TypeF5-BIGIP-LOCAL-MIBltmNodeAddrTable:ltmNodeAddrAddrType1.3.6.1.4.1.3375.2.2.4.1.2.1.1
IPF5-BIGIP-LOCAL-MIBltmNodeAddrTable:ltmNodeAddrAddr1.3.6.1.4.1.3375.2.2.4.1.2.1.2
Enabled StateF5-BIGIP-LOCAL-MIBltmNodeAddrStatusTable:ltmNodeAddrStatusEnabledState1.3.6.1.4.1.3375.2.2.4.3.2.1.4
Availability StateF5-BIGIP-LOCAL-MIBltmNodeAddrStatusTable:ltmNodeAddrStatusAvailState1.3.6.1.4.1.3375.2.2.4.3.2.1.3

Connections

MIB

Object Name

OID

Connections TotalF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatClientTotConns1.3.6.1.4.1.3375.2.1.1.2.1.7
Connections CurrentF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatClientCurConns1.3.6.1.4.1.3375.2.1.1.2.1.8
Connections SSLF5-BIGIP-SYSTEM-MIBsysGlobalClientSslStat:sysClientsslStatCurNativeConns1.3.6.1.4.1.3375.2.1.1.2.9.4
Connections SSL CurrentF5-BIGIP-SYSTEM-MIBsysGlobalClientSslStat:sysClientsslStatCurCompatConns1.3.6.1.4.1.3375.2.1.1.2.9.7

Throughputs

MIB

Object Name

OID

Client Bytes InF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatClientBytesIn1.3.6.1.4.1.3375.2.1.1.2.1.3
Client Bytes OutF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatClientBytesOut1.3.6.1.4.1.3375.2.1.1.2.1.5
Server Bytes InF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatServerBytesIn1.3.6.1.4.1.3375.2.1.1.2.1.10
Server Bytes OutF5-BIGIP-SYSTEM-MIBsysGlobalStat:sysStatServerBytesOut1.3.6.1.4.1.3375.2.1.1.2.1.12

How can i confirm the above  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 -