Forum Discussion

vipin_96627's avatar
vipin_96627
Icon for Nimbostratus rankNimbostratus
May 14, 2012

GlobalLB::set_fallback_ip with ipv6 address throws error in f5 (BIG-IP 10.2.3)

Hello,

 

 

GlobalLB::set_fallback_ip with input ipv6 address throws error as below,

 

 

No handlers could be found for logger "suds.client"

 

Traceback (most recent call last):

 

File "main.py", line 23, in

 

b.GlobalLB.Pool.set_fallback_ip(['POOL1'], ["2001:0db8:85a3:0000:0000:8a2e:0370:7334"])

 

File "build/bdist.linux-x86_64/egg/suds/client.py", line 542, in __call__

 

File "build/bdist.linux-x86_64/egg/suds/client.py", line 602, in invoke

 

File "build/bdist.linux-x86_64/egg/suds/client.py", line 649, in send

 

File "build/bdist.linux-x86_64/egg/suds/client.py", line 702, in failed

 

File "build/bdist.linux-x86_64/egg/suds/bindings/binding.py", line 265, in get_fault

 

suds.WebFault: Server raised fault: 'Exception caught in GlobalLB::urn:iControl:GlobalLB/Pool::set_fallback_ip()

 

Exception: Common::OperationFailed

 

primary_error_code : 17236379 (0x0107019B)

 

secondary_error_code : 0

 

error_string : 0107019b:3: Fallback IP address in pool (POOL1) was either empty or an invalid address'

 

 

can somebody let me know what is the issue is. I have provided valid ipv6 address & valid pool name. so wondering why this error?

 

 

I am using BIG-IP 10.2.3 version.

 

 

Thanks,

 

Vipin

 

4 Replies

  • I'm wondering if the set_fallback_ip method doesn't support IPv6 addresses. Will it take an IPv4 address?
  • yes it is accepting ipv4 address. but when i give ipv6 it throws above error
  • I don't understand if API cannot accept ipv6, how the f5 GUI can accept ipv6 address
  • I am a bit more careful assuming this iControl method won't accept an IPv6 address - hopefully someone with a bit more knowledge can confirm. But if that is indeed the case, it wouldn't surprise me all that much. There's no method to set the IPv6 NoError Response property with iControl either - at least in v10. I guess I think if iControl in a maturing phase - it wasn't added right out of the gate. You can imagine how difficult it must be to expose each new software feature in an API - it's got to be an almost impossible task.