F5 BigIP v9 v10 v11 Templates (Global and LTM)
Moderators: Developers, Moderators
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
I created a brand new instance of cacti, same 0.8.7i version, and the f5 templates work perfectly. Really strange.
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Hi there,
I'm using this template : "cacti_host_template_f5_bigip_v9.xml" to poll some F5 Big IP LTM (version 11.5.1 HFA7).
So as many people I've got many issues with the "too long" OID : I solved those issues by modification in mysql cacti DB (many hours of debugging... thanks to "http://forums.cacti.net") :
Action Done :
alter table poller_reindex modify arg1 varchar(512);
alter table poller_reindex modify assert_value varchar(512);
alter table host_snmp_cache modify field_value varchar(512);
alter table host_snmp_cache modify snmp_index varchar(512);
alter table data_local modify snmp_index varchar(512);
Now all the graphs I need are OK regardless the OID length.
Now, I'm asking help because I'm stuck with issues with the graphs titles.
Unfortunately, I have a lot of VS and pool to graph : editing the graph title manually is not possible...
I modify in "Settings" / "Visual" the fields :
Graph Management: Maximum Title Length to 150,
Data Queries: Maximum Field Length to 150,
Data Sources: Maximum Title Length to 150.
Then all Data Sources name are OK. But for some graphs the graphs title are still NOK, for exemple:
DS name : F5 LTM int - XXXXXXXXXX - Pool Statistics - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc_wildcard_pool7
Values from template : |host_description| - Pool Statistics - |query_ltmPoolStatName|
Graph title : F5 LTM int - XXXXXXXXXX - Pool - Server Traffic - |query_ltmPoolStatName|
Values from template : |host_description| - Pool - Server Traffic - |query_ltmPoolStatName|
=> the same variable is OK in DS name not in graph title !
other example which work (from which I think this is not issue with length...) :
DS name : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
Graph title : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
------------------------------------------------------------------------------
General Information
Date Wed, 04 Feb 2015 12:46:51 +0100
Cacti Version 0.8.8a
Cacti OS unix
SNMP Version NET-SNMP version: 5.4.2.1
RRDTool Version RRDTool 1.3.x
Poller Information
Interval 60
Type cmd.php
PHP Information
PHP Version 5.2.14
PHP OS Linux
PHP SNMP Installed
max_execution_time 30
memory_limit 1024M
I'm using this template : "cacti_host_template_f5_bigip_v9.xml" to poll some F5 Big IP LTM (version 11.5.1 HFA7).
So as many people I've got many issues with the "too long" OID : I solved those issues by modification in mysql cacti DB (many hours of debugging... thanks to "http://forums.cacti.net") :
Action Done :
alter table poller_reindex modify arg1 varchar(512);
alter table poller_reindex modify assert_value varchar(512);
alter table host_snmp_cache modify field_value varchar(512);
alter table host_snmp_cache modify snmp_index varchar(512);
alter table data_local modify snmp_index varchar(512);
Now all the graphs I need are OK regardless the OID length.
Now, I'm asking help because I'm stuck with issues with the graphs titles.
Unfortunately, I have a lot of VS and pool to graph : editing the graph title manually is not possible...
I modify in "Settings" / "Visual" the fields :
Graph Management: Maximum Title Length to 150,
Data Queries: Maximum Field Length to 150,
Data Sources: Maximum Title Length to 150.
Then all Data Sources name are OK. But for some graphs the graphs title are still NOK, for exemple:
DS name : F5 LTM int - XXXXXXXXXX - Pool Statistics - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc_wildcard_pool7
Values from template : |host_description| - Pool Statistics - |query_ltmPoolStatName|
Graph title : F5 LTM int - XXXXXXXXXX - Pool - Server Traffic - |query_ltmPoolStatName|
Values from template : |host_description| - Pool - Server Traffic - |query_ltmPoolStatName|
=> the same variable is OK in DS name not in graph title !
other example which work (from which I think this is not issue with length...) :
DS name : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
Graph title : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
------------------------------------------------------------------------------
General Information
Date Wed, 04 Feb 2015 12:46:51 +0100
Cacti Version 0.8.8a
Cacti OS unix
SNMP Version NET-SNMP version: 5.4.2.1
RRDTool Version RRDTool 1.3.x
Poller Information
Interval 60
Type cmd.php
PHP Information
PHP Version 5.2.14
PHP OS Linux
PHP SNMP Installed
max_execution_time 30
memory_limit 1024M
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
algamb wrote:Hi,
i'm currently graphing data on a Viprion F5 vCMP 11.2 HF2 Box.
Cacti installation is based on Version 0.8.8a.
All the graphs are running smoothly but pool member host statistics.
When i query the data tree that should include pool member IP Host, the HEX string value is reported as empty:
Here below a brief excerpt:
snmpwalk -v 2c -c community f5boxname .1.3.6.1.4.1.3375.2.2.5.4.3.1.3
SNMPv2-SMI::enterprises.3375.2.2.5.4.3.1.3.24.47.67.111.109.109.111.110.47.114.109.115.45.119.119.119.95.52.52.51.95.112.111.111.108.20.47.67.111.109.109.111.110.47.49.
48.46.49.50.56.46.55.48.46.49.49.443 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SNMPv2-SMI::enterprises.3375.2.2.5.4.3.1.3.24.47.67.111.109.109.111.110.47.114.109.115.45.119.119.119.95.52.52.51.95.112.111.111.108.21.47.67.111.109.109.111.110.47.49.
48.46.49.50.56.46.49.54.53.46.49.48.443 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SNMPv2-SMI::enterprises.3375.2.2.5.4.3.1.3.25.47.67.111.109.109.111.110.47.98.105.99.114.45.119.119.119.95.52.52.51.95.112.111.111.108.18.47.67.111.109.109.111.110.47.4
9.48.46.57.54.46.51.46.56.52.443 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SNMPv2-SMI::enterprises.3375.2.2.5.4.3.1.3.25.47.67.111.109.109.111.110.47.98.105.99.114.45.119.119.119.95.52.52.51.95.112.111.111.108.19.47.67.111.109.109.111.110.47.4
9.48.46.57.54.46.51.46.49.51.48.443 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SNMPv2-SMI::enterprises.3375.2.2.5.4.3.1.3.25.47.67.111.109.109.111.110.47.115.101.100.105.97.45.119.119.119.95.56.48.95.112.111.111.108.19.47.67.111.109.109.111.110.47
.49.48.46.57.54.46.51.46.49.56.53.80 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<Cut>
Given what above i'm not able to retrieve IP address value and, just in case, convert it to Decimal dotted notation and include this information on the graphs.
Graphs regarding member statistics are quite useless because i'm not able to recognize which is the subject host for the metrics.
Not sure if i'm missing something or if the box is not reporting proper value.
Thanks in advance for any help on the topic.
Kind regards
-- AG
Hi again,
I have also the same issue. someone found a solution please ?
or any workaround ?
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Hi there,
finally I opened a case with our technical support for F5 regarding issue with the OID .1.3.6.1.4.1.3375.2.2.5.4.3.1.3 which return Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 => I suspect a bug.
But still found nothing regarding the graph title issue (previous post...) : please any suggestion will be appreciate a lot...
NB: sorry for my english I did not write english for a while and it is not my mother language...
finally I opened a case with our technical support for F5 regarding issue with the OID .1.3.6.1.4.1.3375.2.2.5.4.3.1.3 which return Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 => I suspect a bug.
But still found nothing regarding the graph title issue (previous post...) : please any suggestion will be appreciate a lot...
NB: sorry for my english I did not write english for a while and it is not my mother language...
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Could you please give me some advices on this ?
galerien wrote:Hi there,
I'm using this template : "cacti_host_template_f5_bigip_v9.xml" to poll some F5 Big IP LTM (version 11.5.1 HFA7).
So as many people I've got many issues with the "too long" OID : I solved those issues by modification in mysql cacti DB (many hours of debugging... thanks to "http://forums.cacti.net") :
Action Done :
alter table poller_reindex modify arg1 varchar(512);
alter table poller_reindex modify assert_value varchar(512);
alter table host_snmp_cache modify field_value varchar(512);
alter table host_snmp_cache modify snmp_index varchar(512);
alter table data_local modify snmp_index varchar(512);
Now all the graphs I need are OK regardless the OID length.
Now, I'm asking help because I'm stuck with issues with the graphs titles.
Unfortunately, I have a lot of VS and pool to graph : editing the graph title manually is not possible...
I modify in "Settings" / "Visual" the fields :
Graph Management: Maximum Title Length to 150,
Data Queries: Maximum Field Length to 150,
Data Sources: Maximum Title Length to 150.
Then all Data Sources name are OK. But for some graphs the graphs title are still NOK, for exemple:
DS name : F5 LTM int - XXXXXXXXXX - Pool Statistics - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc_wildcard_pool7
Values from template : |host_description| - Pool Statistics - |query_ltmPoolStatName|
Graph title : F5 LTM int - XXXXXXXXXX - Pool - Server Traffic - |query_ltmPoolStatName|
Values from template : |host_description| - Pool - Server Traffic - |query_ltmPoolStatName|
=> the same variable is OK in DS name not in graph title !
other example which work (from which I think this is not issue with length...) :
DS name : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
Graph title : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
------------------------------------------------------------------------------
General Information
Date Wed, 04 Feb 2015 12:46:51 +0100
Cacti Version 0.8.8a
Cacti OS unix
SNMP Version NET-SNMP version: 5.4.2.1
RRDTool Version RRDTool 1.3.x
Poller Information
Interval 60
Type cmd.php
PHP Information
PHP Version 5.2.14
PHP OS Linux
PHP SNMP Installed
max_execution_time 30
memory_limit 1024M
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Trying to get any template running with my 11.x F5 balancers with a fresh install of cacti 8.8b.
Unfortunately it looks like that the data query regex is not working correctly as a wrong index is created. Therefore i'm not able to create graphs for the interfaces, pools etc.
SNMP + F5 Mibs has been installed
I've added an screenshot to make clear what i'm talking about.
Unfortunately it looks like that the data query regex is not working correctly as a wrong index is created. Therefore i'm not able to create graphs for the interfaces, pools etc.
SNMP + F5 Mibs has been installed
I've added an screenshot to make clear what i'm talking about.
- Attachments
-
- SnipImage.JPG (59.06 KiB) Viewed 5425 times
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
My F5 v11 graphs are not continuous. Anything I missed while adding the host ? Also the device status goes UP / DOWN frequently. That may be the reason why the graphs are not continuous but I am not sure why this happens.
Any thoughts ?
Cacti version 0.8.8c
Any thoughts ?
Cacti version 0.8.8c
- Attachments
-
- f5 v11.jpg (56.06 KiB) Viewed 5273 times
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Hi,
I have the same problem. Anybody came up with a working solution for this ?
I would really appreciate it.
Regards
I have the same problem. Anybody came up with a working solution for this ?
I would really appreciate it.
Regards
galerien wrote:Hi there,
I'm using this template : "cacti_host_template_f5_bigip_v9.xml" to poll some F5 Big IP LTM (version 11.5.1 HFA7).
So as many people I've got many issues with the "too long" OID : I solved those issues by modification in mysql cacti DB (many hours of debugging... thanks to "http://forums.cacti.net") :
Action Done :
alter table poller_reindex modify arg1 varchar(512);
alter table poller_reindex modify assert_value varchar(512);
alter table host_snmp_cache modify field_value varchar(512);
alter table host_snmp_cache modify snmp_index varchar(512);
alter table data_local modify snmp_index varchar(512);
Now all the graphs I need are OK regardless the OID length.
Now, I'm asking help because I'm stuck with issues with the graphs titles.
Unfortunately, I have a lot of VS and pool to graph : editing the graph title manually is not possible...
I modify in "Settings" / "Visual" the fields :
Graph Management: Maximum Title Length to 150,
Data Queries: Maximum Field Length to 150,
Data Sources: Maximum Title Length to 150.
Then all Data Sources name are OK. But for some graphs the graphs title are still NOK, for exemple:
DS name : F5 LTM int - XXXXXXXXXX - Pool Statistics - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc_wildcard_pool7
Values from template : |host_description| - Pool Statistics - |query_ltmPoolStatName|
Graph title : F5 LTM int - XXXXXXXXXX - Pool - Server Traffic - |query_ltmPoolStatName|
Values from template : |host_description| - Pool - Server Traffic - |query_ltmPoolStatName|
=> the same variable is OK in DS name not in graph title !
other example which work (from which I think this is not issue with length...) :
DS name : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
Graph title : F5 LTM int - XXXXXXXXXX - VS - Client Connections - /Common/PROD_EXCHANGE-OWA_iApp-042014.app/PROD_EXCHANGE-OWA_iApp-042014_rpc
Values from template : |host_description| - VS - Client Connections - |query_vsName|
------------------------------------------------------------------------------
General Information
Date Wed, 04 Feb 2015 12:46:51 +0100
Cacti Version 0.8.8a
Cacti OS unix
SNMP Version NET-SNMP version: 5.4.2.1
RRDTool Version RRDTool 1.3.x
Poller Information
Interval 60
Type cmd.php
PHP Information
PHP Version 5.2.14
PHP OS Linux
PHP SNMP Installed
max_execution_time 30
memory_limit 1024M
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
I am not at all claiming to be an expert and have not really double check to make sure this is still an issue. But to fix the VS and Pool graphs with Ver 11.x I had to build new XML Data Query Files. Looks like everyone is trying to resolve the HEX issue but to me it appears they just moved the OIDs to a new design.
Below are some of the info on it.
This is for VS XML data.. I took out a lot of stuff I don't need.
<interface>
<name>F5 BigIP LTM Virtual Server Statistics</name>
<description>From F5 MIBS bigipLocalTM->ltmVirtualServers</description>
<oid_index>.1.3.6.1.4.1.3375.2.2.5.2.3.1.1</oid_index>
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)</oid_index_parse>
<index_order>ltmVSIndex</index_order>
<index_order_type>alphabetic</index_order_type>
<fields>
<ltmVSIndex>
<name>Index</name>
<source>index</source>
<direction>input</direction>
</ltmVSIndex>
<ltmVSName>
<name>Name</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.1</oid>
</ltmVSName>
<ltmVSPktsIn>
<name>Other Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.2</oid>
</ltmVSPktsIn>
<ltmVSPktsOut>
<name>Other Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.4</oid>
</ltmVSPktsOut>
<ltmVSBytesIn>
<name>Other Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.3</oid>
</ltmVSBytesIn>
<ltmVSBytesOut>
<name>Other Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.5</oid>
</ltmVSBytesOut>
<ltmVSConnsTotal>
<name>Total Other Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.7</oid>
</ltmVSConnsTotal>
</fields>
Here is the XML for the Pool.
$ more f5_bigip_ltm_member_V11.xml
<interface>
<name>F5 BigIP LTM Pool Member Statistics</name>
<description>From F5 MIBS bigipLocalTM->ltmPoolMemberStat</description>
<oid_index>.1.3.6.1.4.1.3375.2.2.5.4.3.1.1</oid_index>
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)</oid_index_parse>
<index_order>ltmPoolMemberIndex</index_order>
<index_order_type>alphabetic</index_order_type>
<fields>
<ltmPoolMemberIndex>
<name>Index</name>
<source>index</source>
<direction>input</direction>
</ltmPoolMemberIndex>
<ltmPoolName>
<name>Name</name>
<method>walk</method>
<source>VALUE/REGEXP:\/Common\/</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.1</oid>
</ltmPoolName>
<ltmPoolMemberPort>
<name>Port</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.4</oid>
</ltmPoolMemberPort>
<ltmPoolMemberPktsIn>
<name>Server Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.5</oid>
</ltmPoolMemberPktsIn>
<ltmPoolMemberPktsOut>
<name>Server Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.7</oid>
</ltmPoolMemberPktsOut>
<ltmPoolMemberBytesIn>
<name>Server Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.6</oid>
</ltmPoolMemberBytesIn>
<ltmPoolMemberBytesOut>
<name>Server Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.8</oid>
</ltmPoolMemberBytesOut>
<ltmPoolMemberConnsTotal>
<name>Total Server Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.10</oid>
</ltmPoolMemberConnsTotal>
<ltmPoolMemberConnsCurr>
<name>Current Server Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.11</oid>
</ltmPoolMemberConnsCurr>
<ltmPoolMemberPvaPktsIn>
<name>PVA Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.12</oid>
</ltmPoolMemberPvaPktsIn>
<ltmPoolMemberPvaPktsOut>
<name>PVA Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.14</oid>
</ltmPoolMemberPvaPktsOut>
<ltmPoolMemberPvaBytesIn>
<name>PVA Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.13</oid>
</ltmPoolMemberPvaBytesIn>
<ltmPoolMemberPvaBytesOut>
<name>PVA Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.15</oid>
</ltmPoolMemberPvaBytesOut>
<ltmPoolMemberPvaConnsTotal>
<name>Total PVA Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.17</oid>
</ltmPoolMemberPvaConnsTotal>
<ltmPoolMemberPvaConnsCurr>
<name>Current PVA Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.18</oid>
</ltmPoolMemberPvaConnsCurr>
<ltmPoolMemberPvaAssistConnsTotal>
<name>Total PVA Assisted Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.20</oid>
</ltmPoolMemberPvaAssistConnsTotal>
<ltmPoolMemberPvaAssistConnsCurr>
<name>Current PVA Assisted Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.21</oid>
</ltmPoolMemberPvaAssistConnsCurr>
<ltmPoolMemberAddressV11>
<name>Address</name>
<method>walk</method>
<source>VALUE/REGEXP:\/Common\/</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.28</oid>
</ltmPoolMemberAddressV11>
</fields>
</interface>
Below are some of the info on it.
This is for VS XML data.. I took out a lot of stuff I don't need.
<interface>
<name>F5 BigIP LTM Virtual Server Statistics</name>
<description>From F5 MIBS bigipLocalTM->ltmVirtualServers</description>
<oid_index>.1.3.6.1.4.1.3375.2.2.5.2.3.1.1</oid_index>
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)</oid_index_parse>
<index_order>ltmVSIndex</index_order>
<index_order_type>alphabetic</index_order_type>
<fields>
<ltmVSIndex>
<name>Index</name>
<source>index</source>
<direction>input</direction>
</ltmVSIndex>
<ltmVSName>
<name>Name</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.1</oid>
</ltmVSName>
<ltmVSPktsIn>
<name>Other Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.2</oid>
</ltmVSPktsIn>
<ltmVSPktsOut>
<name>Other Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.4</oid>
</ltmVSPktsOut>
<ltmVSBytesIn>
<name>Other Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.3</oid>
</ltmVSBytesIn>
<ltmVSBytesOut>
<name>Other Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.5</oid>
</ltmVSBytesOut>
<ltmVSConnsTotal>
<name>Total Other Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.2.3.1.7</oid>
</ltmVSConnsTotal>
</fields>
Here is the XML for the Pool.
$ more f5_bigip_ltm_member_V11.xml
<interface>
<name>F5 BigIP LTM Pool Member Statistics</name>
<description>From F5 MIBS bigipLocalTM->ltmPoolMemberStat</description>
<oid_index>.1.3.6.1.4.1.3375.2.2.5.4.3.1.1</oid_index>
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)</oid_index_parse>
<index_order>ltmPoolMemberIndex</index_order>
<index_order_type>alphabetic</index_order_type>
<fields>
<ltmPoolMemberIndex>
<name>Index</name>
<source>index</source>
<direction>input</direction>
</ltmPoolMemberIndex>
<ltmPoolName>
<name>Name</name>
<method>walk</method>
<source>VALUE/REGEXP:\/Common\/</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.1</oid>
</ltmPoolName>
<ltmPoolMemberPort>
<name>Port</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.4</oid>
</ltmPoolMemberPort>
<ltmPoolMemberPktsIn>
<name>Server Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.5</oid>
</ltmPoolMemberPktsIn>
<ltmPoolMemberPktsOut>
<name>Server Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.7</oid>
</ltmPoolMemberPktsOut>
<ltmPoolMemberBytesIn>
<name>Server Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.6</oid>
</ltmPoolMemberBytesIn>
<ltmPoolMemberBytesOut>
<name>Server Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.8</oid>
</ltmPoolMemberBytesOut>
<ltmPoolMemberConnsTotal>
<name>Total Server Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.10</oid>
</ltmPoolMemberConnsTotal>
<ltmPoolMemberConnsCurr>
<name>Current Server Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.11</oid>
</ltmPoolMemberConnsCurr>
<ltmPoolMemberPvaPktsIn>
<name>PVA Packets In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.12</oid>
</ltmPoolMemberPvaPktsIn>
<ltmPoolMemberPvaPktsOut>
<name>PVA Packets Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.14</oid>
</ltmPoolMemberPvaPktsOut>
<ltmPoolMemberPvaBytesIn>
<name>PVA Bytes In</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.13</oid>
</ltmPoolMemberPvaBytesIn>
<ltmPoolMemberPvaBytesOut>
<name>PVA Bytes Out</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.15</oid>
</ltmPoolMemberPvaBytesOut>
<ltmPoolMemberPvaConnsTotal>
<name>Total PVA Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.17</oid>
</ltmPoolMemberPvaConnsTotal>
<ltmPoolMemberPvaConnsCurr>
<name>Current PVA Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.18</oid>
</ltmPoolMemberPvaConnsCurr>
<ltmPoolMemberPvaAssistConnsTotal>
<name>Total PVA Assisted Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.20</oid>
</ltmPoolMemberPvaAssistConnsTotal>
<ltmPoolMemberPvaAssistConnsCurr>
<name>Current PVA Assisted Conns</name>
<method>walk</method>
<source>value</source>
<direction>output</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.21</oid>
</ltmPoolMemberPvaAssistConnsCurr>
<ltmPoolMemberAddressV11>
<name>Address</name>
<method>walk</method>
<source>VALUE/REGEXP:\/Common\/</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.3375.2.2.5.4.3.1.28</oid>
</ltmPoolMemberAddressV11>
</fields>
</interface>
-
- Posts: 1
- Joined: Fri Apr 28, 2017 6:21 am
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Hi,
We had same problems that bapho1337. The solution is changing:
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)[/color]</oid_index_parse>
To return the snmpwalk of oid_index that not match with oid_index.
Example:
snmpwalk of F5-BIGIP-LOCAL-MIB.ltmPoolName return:
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som1" = /Common/Som1
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som2" = /Common/Som2
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som3" = /Common/Som3
oid_index_parse return:
"/Common/Som1"
"/Common/Som2"
"/Common/Som3"
snmpwalk of F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns return:
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som1" = x
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som2" = x
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som3" = x
oid_index_parse return:
"/Common/Som1"
"/Common/Som2"
"/Common/Som3"
Regards
We had same problems that bapho1337. The solution is changing:
<oid_index_parse>OID/REGEXP:^.{31,32}\.(.*)[/color]</oid_index_parse>
To return the snmpwalk of oid_index that not match with oid_index.
Example:
snmpwalk of F5-BIGIP-LOCAL-MIB.ltmPoolName return:
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som1" = /Common/Som1
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som2" = /Common/Som2
F5-BIGIP-LOCAL-MIB.ltmPoolName."/Common/Som3" = /Common/Som3
oid_index_parse return:
"/Common/Som1"
"/Common/Som2"
"/Common/Som3"
snmpwalk of F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns return:
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som1" = x
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som2" = x
F5-BIGIP-LOCAL-MIB.ltmPoolStatServerTotConns."/Common/Som3" = x
oid_index_parse return:
"/Common/Som1"
"/Common/Som2"
"/Common/Som3"
Regards
Re: F5 BigIP v9 v10 v11 Templates (Global and LTM)
Anyone facing problems monitoring interface traffic?
All the graphs are empty
All the graphs are empty
cacti rulez!
Who is online
Users browsing this forum: No registered users and 1 guest