BIG-IP® 3.x and 4.x
These metrics should work for both 3.x and 4.x, and have not
been depreciated with the upgrade to 4.x. Some versions of 2.x probably work
as well, although I do not have the ability to test this.
These metrics are non-global, which means they are metrics that only
account for a component of the BIG-IP® and it's configuration, such as
connections per second for a particular VIP rather than the entire unit.
|
Metrics for a given VIP
|
There are two ways that BIG-IP's® MIBS will let you can get
the metrics for a particular VIP. You can get it via the Layer 3 address (IP
address) or with the Layer 3 address and Layer 4 port.
With the Layer 3 address, whatever ports you have configured for an IP (such
as port 80 and 443) will be included in the metrics.
With the Layer 3 and Layer 4 OID, every single port you have
configured will have a different pair of OIDs (octets in versus octets out).
Remember, these are all octets, same thing as bytes. If you want bits
per second, remember to include the bits option in
your MRTG config (this simply multiplies the figure by 8).
Layer 3 OIDs
Metric: Octets In
OID: 1.3.6.1.4.1.3375.1.1.2.2.1.8.X.X.X.X (where
x.x.x.x is the IP address)
Name: enterprises.f5.f5systems.loadbal.virtualAddress.
virtualAddressTable.virtualAddressEntry.virtualAddressOctetsIn
Type: Counter
Metric: Octets Out
OID: 1.3.6.1.4.1.3375.1.1.2.2.1.9.X.X.X.X (where
x.x.x.x is the IP address)
Name: enterprises.f5.f5systems.loadbal.virtualAddress.
virtualAddressTable.virtualAddressEntry.virtualAddressOctetsIn
Type: Counter
Metric: Connection Rate
OID: 1.3.6.1.4.1.3375.1.1.2.2.1.14.X.X.X.X
Name: enterprises.f5.f5systems.loadbal.virtualAddress.
virtualAddressTable.virtualAddressEntry.virtualAddressTotalConn
Type: Counter
Metric: Current Connections
OID: 1.3.6.1.4.1.3375.1.1.2.2.1.12.X.X.X.X
Name: enterprises.f5.f5systems.loadbal.virtualAddress.
virtualAddressTable.virtualAddressEntry.virtualAddressCurrentConn
Type: Gauge
Layer 3/Layer 4 OIDs
Metric: Octets In
OID: 1.3.6.1.4.1.3375.1.1.3.2.1.13.X.X.X.X.Y (where
x.x.x.x is the IP address and Y is the TCP port)
Name: enterprises.f5.f5systems.loadbal.virtualServer.
virtualServerTable.virtualServerEntry.virtualServerOctetsIn
Type: Counter
Metric: Octets Out
OID: 1.3.6.1.4.1.3375.1.1.3.2.1.14.X.X.X.X.Y (where
x.x.x.x is the IP address and Y is the TCP port)
Name: enterprises.f5.f5systems.loadbal.virtualServer.
virtualServerTable.virtualServerEntry.virtualServerOctetsOut
Type: Counter
Metric: Connection Rate
OID: 1.3.6.1.4.1.3375.1.1.3.2.1.19.X.X.X.X.Y
Name: enterprises.f5.f5systems.loadbal.virtualServer.
virtualServerTable.virtualServerEntry.virtualServerTotalConn
Type: Counter
Metric: Current Connections
OID: 1.3.6.1.4.1.3375.1.1.3.2.1.17.X.X.X.X.Y
Name: enterprises.f5.f5systems.loadbal.virtualServer.
virtualServerTable.virtualServerEntry.virtualServerCurrentConn
Type: Gauge
Sample Config
If I did a sample configuration for each one of these
metrics, it would take several pages. Instead, I'll just give an example of
out to measure any of the octets in versus octet out OIDs, as those I would
imagine would cause the most confusion for those just begging their journey
with MRTG.
The following MRTG config will give you in versus out (just like in a
regular MRTG interface config) for a VIP with an IP address of 192.168.0.200
on a machine named bigip1.
Target[bigip1_VIP1]:
1.3.6.1.4.1.3375.1.1.2.2.1.8.192.168.0.200&
1.3.6.1.4.1.3375.1.1.2.2.1.9.192.168.0.200:public@bigip1
MaxBytes[bigip1_VIP1]: 100000000
AbsMax[bigip1_VIP1]: 100000000
Options[bigip1_VIP1]: growright,bits
Title[bigip1_VIP1]: bits per second for VIP1 (192.168.0.200)
PageTop[bigip1_VIP1]: <H1>Bits Per Second for VIP1 (192.168.0.200)
</H1>
<TABLE>
<TR><TD>System:</TD><TD>bigip1</TD></TR>
<TR><TD>Maintainer:</td><td>tony</TD></TR>
<TR><TD>Object:</TD><TD>Bandwidth -
1.3.6.1.4.1.3375.1.1.2.2.1.8.192.168.0.200 versus
1.3.6.1.4.1.3375.1.1.2.2.1.9.192.168.0.200</TD></TR>
</TABLE>
YLegend[bigip1_VIP1]: bits/s
ShortLegend[bigip1_VIP1]: bits/s
Legend1[bigip1_VIP1]: Bits In
Legend2[bigip1_VIP1]: Bits Out
LegendI[bigip1_VIP1]:
LegendO[bigip1_VIP1]:
|
|
|
