PVS 2507 on XenServer - Target devices on same VLAN as PVS server are working fine. However, target devices on different VLAN are slow to boot and stuck at this screen forever. WC is set to Cache on RAM with overflow to disk. DHCP options 11, 66 and 67 are set on the non-PVS VLAN.

Routing / FW issue ? Best practice is to keep them in the same VLAN. You get 2 PVS per site/data center

I would group the potential causes into three main categories: 1. Traffic filtering or inspection – for example, firewalls, ACLs, or network devices inspecting or restricting traffic (especially UDP), which can impact PVS streaming. See Network requirements for PVS streaming https://docs.citrix.com/en-us/provisioning/2503-1/system-requirements.html 2. Network performance constraints – latency, bandwidth limitations, or physical separation (e.g. different racks, network paths, or datacentres). Could yuo ping, traceroute, pathping, smokeping, use some other tool between these 2 VLANs where PVS server and target resides to see what’s happening therein ters of latency. 3. Other anomalies – including configuration issues, platform-specific behaviour, or unexpected environmental factors. In this scenario, the assumption is that all systems are located within the same datacentre, and VLANs are primarily used to segment the network and reduce broadcast domain size rather than to separate geographically distant resources. You coudl try generating BDM iso and boot from it to keep the DHCP option out of the picture.

Different VLAN? Bottleneck is the router or firewall. Had that at a client where someone decided to turn on packet inspection between the pvs targets and servers. The router turned in it's resignation papers and took down ALL traffic.

Sure, will review with network/firewall teams. How about have two NICs -one in each VLAN supporting target devices local to that VLAN? https://support.citrix.com/external/article/CTX692234/provisioning-services-with-multiple-non.html

Yes we do that, no need to set a GW for the PVS VLAN

Ok. Whether target devices cross boot from other NIC or they stay within the VLAN specific network?

They stay in my case, they should for you too, I use BDM iso boot. If you boot PXE you set the PVS one first and configure your PVS for this DHCP scope /VLAN only

i dont see a lot of folks separating stream onto sep NICs these days.

Did you format the overflow disk on the master?

Yes. I use same vDisk to boot targets with different VLANs. Devices within the same VLAN works fine. Not a write cache disk format/initialize issue. Even the devices that are not part of PVS VLAN, 6 out of 10 booted fine after multiple restarts.

It's firewall issue you need to add the pvs ports in application filtering in firewall...we had the same issue..we had Palo alto firewall