For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Brian_Miller_01's avatar
Brian_Miller_01
Icon for Nimbostratus rankNimbostratus
Apr 07, 2014

Virtual Server Type inaccurate when using Native SOAP call to LocalLB:VirtualServer:create

I'm using native SOAP call, LocalLB:VirtualServer:create, to create Virtual Servers. Setting the VirtualServerType to RESOURCE_TYPE_POOL results in a server that's of server type Performance(L4) in the GUI.

 

Please see the comment for the XML codeblocks, as the codeblock fence doesn't seem to work correctly in the question.

 

application delivery
devops
iControl
LTM
soap

3 Replies

  • Brian_Miller_01's avatar
    Brian_Miller_01
    Icon for Nimbostratus rankNimbostratus
    Apr 07, 2014
    I'm using native SOAP call, LocalLB:VirtualServer:create, to create Virtual Servers. Setting the VirtualServerType to RESOURCE_TYPE_POOL results in a server that's of server type Performance(L4) in the GUI. Here's the request that I'm using. Notice that the server types are different: one is RESOURCE_TYPE_POOL, and the other is RESOURCE_TYPE_FAST_L4: ~~~~~ myTestVirtualServer10 192.168.10.20 8080 IP myTestVirtualServer11 192.168.10.21 8080 IP 255.255.255.255 255.255.255.255 RESOURCE_TYPE_POOL myTestPool2 RESOURCE_TYPE_FAST_L4 myTestPool2 PROFILE_CONTEXT_TYPE_ALL tcp PROFILE_CONTEXT_TYPE_ALL tcp ~~~~~ When I query the server type, LocalLB:VirtualServer:get_type, with the following: ~~~~~ myTestVirtualServer10 myTestVirtualServer11 ~~~~~ IControl returns the following - Notice that they are the same server type and it's RESOURCE_TYPE_POOL: ~~~~~ RESOURCE_TYPE_POOL RESOURCE_TYPE_POOL ~~~~~ In the Management GUI, both servers show a server type of Performance(L4). Anyone have an idea of what's going on here? Software is F5 LTM software appliance 11.5.
    • Brian_Miller_01's avatar
      Brian_Miller_01
      Icon for Nimbostratus rankNimbostratus
      Apr 08, 2014
      It seems to be related to an error in my code. The corrected create request follows. Notice that the protocol value has been corrected, as well as the VirtualServerProfile sequence: ~~~ myTestVirtualServer2 192.168.10.2 8080 PROTOCOL_TCP myTestVirtualServer3 192.168.10.3 8080 PROTOCOL_TCP 255.255.255.255 255.255.255.255 RESOURCE_TYPE_POOL myTestPool2 RESOURCE_TYPE_POOL myTestPool2 PROFILE_CONTEXT_TYPE_ALL /Common/http PROFILE_CONTEXT_TYPE_CLIENT /Common/tcp PROFILE_CONTEXT_TYPE_ALL /Common/http PROFILE_CONTEXT_TYPE_CLIENT /Common/tcp ~~~