Most of the fields in the SubVS properties screen are the same as the ones used for a normal Virtual Service.

For a description of the other fields and options, refer to the Web User Interface (WUI) Configuration Guide.

See below for descriptions of the SubVS specific fields.

Duplicate SubVS

You can click Duplicate SubVS to create a duplicate SubVS within the same Virtual Service. All SubVS configuration settings are copied to the duplicate SubVS.

When you click Duplicate SubVS, a pop-up message appears like "SubVS duplicated, SubVS Id:4, RS Id: 3". Click OK to close the pop-up. A SubVS has both a Virtual Service ID (SubVS Id) and a Real Server ID (RS Id).

The SubVS Id in the message refers to the Virtual Service ID. You can see this ID in the heading at the top of the SubVS modify screen for the relevant SubVS.

The RS Id refers to the Real Server Id - but for SubVSs this Real Server Id is used to identify the SubVS in the SubVSs section of the Virtual Service modify screen.

Note: In some scenarios, when using the Application Programming Interface (API), you need to use the Virtual Service Index of the SubVS but in other scenarios you need to use the Real Server Id of a SubVS. For further details, refer to the RESTful API documentation, PowerShell Interface Description, or PowerShell command help text.

SubVS Name: An identifiable name for the SubVS. This field is optional but we recommend that SubVSs are named as it may get confusing if several SubVSs exist.

Note: In addition to the usual alphanumeric characters, the following ‘special’ characters can be used as part of the Service Name: . @ - _ However, there must be at least one alphanumeric character before the special characters.

SubVS Type: Setting this controls the options displayed for the SubVS. It’s important to make sure the SubVS Type is set according to the type of application is being load balanced.

SubVS Weight: This will be used when determining the priority of the SubVS.

SubVS Limit: This is the maximum number of connections that can be forwarded to this SubVS before it is taken out of rotation from the main Virtual Service. The maximum limit is 100,000.

SubVS Rate Limit: This is the maximum number of connections per second that can be forwarded to this SubVS before it is taken out of rotation from the main Virtual Service. The maximum limit is 100,000.

Reencryption SNI Hostname: In LoadMaster firmware version 7.2.52 and above, it is possible to set a Reencryption SNI Hostname at the SubVS level. If this is set in a SubVS, this overrides the parent Virtual Service value and/or the received SNI value.

Note: This field is only visible when SSL re-encryption is enabled.