Forum Discussion
shaggy_121467
Jun 13, 2014Cumulonimbus
I am seeing the same behavior between a standard and Perf L4 VS in v11.5.0 (albeit using python/bigsuds):
ltm virtual test_asm_vs {
destination 1.1.1.1:http
ip-protocol tcp
mask 255.255.255.255
pool test_asm_pl
profiles {
http { }
tcp { }
}
source 0.0.0.0/0
vs-index 2
}
ltm virtual test_asm_fastl4_vs {
destination 1.1.1.6:80
ip-protocol tcp
mask 255.255.255.255
profiles {
fastL4 { }
}
source 0.0.0.0/0
vs-index 6
}
Python:
>>> b.LocalLB.VirtualServer.get_type(['test_asm_vs'])
['RESOURCE_TYPE_POOL']
>>> b.LocalLB.VirtualServer.get_type(['test_asm_fastl4_vs'])
['RESOURCE_TYPE_POOL']
Since VS-type as is not necessarily a configuration item within the VS config, you may need to identify a VS by examining the profiles in combination with VirtualServer.get_type(). Seems a little weird, but its an option:
>>> b.LocalLB.VirtualServer.get_profile(['test_asm_fastl4_vs'])
[[{'profile_name': '/Common/fastL4', 'profile_context': 'PROFILE_CONTEXT_TYPE_ALL','profile_type': 'PROFILE_TYPE_FAST_L4'}]]
- Lee_Payne_53457Jun 13, 2014CirrostratusIf we cant figure out why its reporting the wrong thing then I may have to look at using the profiles to determine the VS type.
- shaggy_121467Jun 13, 2014CumulonimbusIt's not necessarily the "wrong" thing, as it is a pool-based VS; however, the get_type wiki (https://clouddocs.f5.com/api/icontrol-soap/LocalLB__VirtualServer__VirtualServerType.html) does say that VirtualServerType contains member "RESOURCE_TYPE_FAST_L4". I'm curious to see what combination of VS options trigger that get_type response
- Lee_Payne_53457Jun 13, 2014CirrostratusAfter some quick testing it appears that most work, I can get reject, L"_Forwarding, IP_Forwarding just not L4 forwarding, I'm wondering if something changed in v10/11 (as it was introduced in v9) which means it will always report as pool based.