All Apps and Add-ons

Fail to set active folder as partition "/Common" for Template

Thibaut
New Member

Hi everyone,

We want to use this App with our F5 that is in version 11.5.3.
We have a problem when it tries to change the partition to /Common.
It look likes it can correctly find what partitions there is on our F5 (only Common actually) but when it tries to change to that partition, there is an error.
Here are the debug logs :

2016-03-30 11:44:19,842 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:48 | Get an f5 connection: adm.splunk@10.x.x.x
2016-03-30 11:44:19,842 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:52 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,842 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:60 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,843 DEBUG pid=126893 tid=Thread-1132 file=F5_iControl_Template.py:fetch:71 | Get Partitions for API: Networking.VLAN.get_list
2016-03-30 11:44:19,916 DEBUG pid=126893 tid=Thread-1132 file=F5_iControl_Template.py:fetch:73 | Partitions for API "Networking.VLAN.get_list" is ['/Common']
2016-03-30 11:44:19,916 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:putConn:66 | Put an f5 connection: adm.splunk@10.x.x.x
2016-03-30 11:44:19,916 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:putConn:67 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,916 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:48 | Get an f5 connection: adm.splunk@10.x.x.x
2016-03-30 11:44:19,917 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:52 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,917 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:getConn:60 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,990 ERROR pid=126893 tid=Thread-1132 file=F5_iControl_Template.py:_fetch:92 | Fail to set active folder as partition "/Common" for Template "call Networking.VLAN.get_list against Networking.VLAN.get_auto_lasthop;get_cmp_hash_algorithm;get_customer_id;get_description;get_dynamic_forwarding;get_failsafe_action;get_failsafe_state;get_failsafe_timeout;get_if_index;get_learning_mode;get_member;get_mtu;get_sflow_poll_interval;get_sflow_poll_interval_global;get_sflow_sampling_rate; get_sflow_sampling_rate_global;get_source_check_state;get_static_forwarding;get_true_mac_address;get_vlan_id" on F5 BIGIP "10.x.x.x"
2016-03-30 11:44:19,990 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:putConn:66 | Put an f5 connection: adm.splunk@10.x.x.x
2016-03-30 11:44:19,990 DEBUG pid=126893 tid=Thread-1132 file=F5_BigIP_Pool.py:putConn:67 | F5 connection count for "adm.splunk@10.x.x.x" is 1
2016-03-30 11:44:19,990 DEBUG pid=126893 tid=Thread-1132 file=f5_bigip_scheduler.py:run:167 | end fetch.

I know someone had the same problem ( https://answers.splunk.com/answers/346898/unable-to-poll-f5-servers-from-splunk-for-logs-err.html ) but we are not using fips appliances like he is so I think the problem is different.

We're using Splunk 6.3 and the last version of the App, the adm.splunk user has admin rights (Administrator role with advanced shell also and located in partition Common).

Any help will be appreciated 🙂

Thanks !

0 Karma
1 Solution

sduchene_splunk
Splunk Employee
Splunk Employee

Opening Port 443 is mandatory and fixed the issue apparently, can you please confirm ?
The doc has been updated here :
http://docs.splunk.com/Documentation/AddOns/latest/F5BIGIP/Configureinputs

View solution in original post

0 Karma

sduchene_splunk
Splunk Employee
Splunk Employee

Opening Port 443 is mandatory and fixed the issue apparently, can you please confirm ?
The doc has been updated here :
http://docs.splunk.com/Documentation/AddOns/latest/F5BIGIP/Configureinputs

0 Karma

Thibaut
New Member

Sorry for the delay.
Yes, don't forget to open the flow from the Splunk to your F5 on port 443 for icontrol.

Don't get fooled by these kind of logs where you think the splunk can communicate with the F5 :

2016-03-30 11:44:19,843 DEBUG pid=126893 tid=Thread-1132 file=F5_iControl_Template.py:fetch:71 | Get Partitions for API: Networking.VLAN.get_list
 2016-03-30 11:44:19,916 DEBUG pid=126893 tid=Thread-1132 file=F5_iControl_Template.py:fetch:73 | Partitions for API "Networking.VLAN.get_list" is ['/Common']
0 Karma

pgadhari
Builder

@Thibaut - So did you opened the port 443 on heavy forwarder, what is the process you followed on enabling that port ? Did you open the port in "Data inputs" ==> TCP ==> added a new port 443 in listen mode ? please explain ? I am also getting the same errors above, when I am configuring the F5 add-on in my setup ?

Please let me know exact procedure of opening the port 443, as I am trying to do it using data inputs but getting error ?

0 Karma

sduchene_splunk
Splunk Employee
Splunk Employee

Thibaut, can you confirm the note here : http://docs.splunk.com/Documentation/AddOns/latest/F5BIGIP/Configureinputs

Note: The username you provide needs to have been created in the Common partition
I'm no F5 expert, but it seems the account has to be "created" in the partition used. is it your case ?

0 Karma

Thibaut
New Member

Hi Simon,

Yes, the user is created in the Common partition, actually we only have one partition so everything on our F5 is in the Common partition.
I also tried to put directly "Common" in the partition section under the F5 Big-IP server of the addon (by default it is left blank to check all the partitions) but it didn't change anything to my problem.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...