Port Following with Generic Virtual Services

This article relates to LoadMaster firmware version 7.2.51.

As of LoadMaster firmware version 7.2.51, you can configure port following on Virtual Services with the Service Type set to Generic. This was not possible on versions prior to 7.2.51. Port following keeps stickiness to the same Real Server across different Virtual Services.

Port following has the following requirements:

  • The Virtual Services must have the same set of Real Servers
  • The Virtual Service must be using the same persistence options

After meeting these conditions, in the Virtual Service modify screen there will be an option under Advanced Properties for Port Following. Ensure to set this on both Virtual Services to ensure that port following is done bi-directionally.

For further details on port following in general, refer to the Long Term Support (LTS) Port Following Feature Description document.

Application Programming Interface (API) Details

No API updates were made relating to this change. To configure port following when the requirements outlined above have been met, run the modvs RESTful API command and set the followvsid parameter, for example:

/access/modvs?vs=<VirtualServiceIPAddress>&port=<VirtualServicePort>&prot=<VirtualServiceProtocol>&followvsid=<IDOfVirtualServiceToFollow>

For further details on the RESTful API in general, refer to the Long Term Support (LTS) RESTful API Interface Description.

For PowerShell help, run the Get-Help command for the relevant commands.

Was this article helpful?

0 out of 0 found this helpful

Comments