How to understand & Configure Sub Virtual Services (SubVS)
From within a Virtual Service you can create one or more ‘Sub-Virtual Services’ (SubVSs). A SubVS is linked to, and uses the IP address of, the ‘parent’ Virtual Service. The SubVSs may have different settings (such as health check methods, content rules etc.) to the parent Virtual Service and to other SubVSs. This allows the grouping of related Virtual Services, all using the same IP address. This could be useful when there are complex configurations such as Exchange or Lync which typically are comprised of a number of Virtual Services.
There are many advantages to using SubVSs, such as:
- SubVSs are linked to, and use the IP address of, the ‘parent’ Virtual Service
- Using SubVSs reduces the number of IP addresses required by applications such as Lync or Exchange
- SubVSs do not require non-transparency
- SubVSs may have different settings (such as content rules) to the parent Virtual Service and to each other
- Using a SubVS provides the ability to have content switching and persistency on the same Virtual Service
- Using a SubVS gives the ability to perform multiple health checks on the same Virtual Service
- SubVSs work well with ESP, but ESP is not required
Was this article helpful?
0 out of 0 found this helpful
Nazeerullah s
The issue we are facing that services are hanging on the server and the load distribution on the load balancer as per our DB is not proper as