PVS target devices will not HA failover to another PVS server.
book
Article ID: CTX580751
calendar_today
Updated On:
Description
PVS target devices will not HA failover to another PVS server.
Targets devices will freeze until the original server they were streaming from is available again.
HA related configurations can be checked:
- The vdisk should be configured to use cache in ram with overflow to local device hard disk, and this configuration should be checked to be effective on the booted target in the vdisk status.
- Boot configuration should show multiple PVS servers are configured as PVS login servers.
Network traces of the target while it is frozen will show:
- The target device attempting communication against the original streaming server ip and and original streaming port.
- There will be no attempt by the target device to use a PVS login port or use a different PVS server ip address.
Resolution
- Confirm Target Devices are correctly licensed
- This can be checked via PVS console, check PVS target properties, status tab. If the target is unlicensed, it will show n/a against licensing
- To reconfigure licensing via the PVS console, open the PVS farm properties, go to licensing tab, and update options appropriately there for your license type.
Problem Cause
If PVS targets are unlicensed and also outside of grace period, PVS targets will not HA failover.
Was this article helpful?
thumb_up
Yes
thumb_down
No