PVS targets not booting after moving targets to a seperate network.

PVS targets not booting after moving targets to a seperate network.

book

Article ID: CTX694777

calendar_today

Updated On:

Description


The PVS environments network was reconfigured

  • Originally before reconfiguration, target devices were on the same vlan as the PVS server streaming adapters, and booted successfully.
  • Network reconfiguration had PVS targets moved into their own separate vlan, separate from PVS server streaming network adapters
    • Routing was configured between the vlans, and firewall rules configured to only allow PVS related traffic, TFTP and PVS streaming.

After the change PVS targets failed to boot in this separate vlan.

  • Targets showed station IP address, server IP address, correct NBP filename pvsnbpx64.efi, but showing NBP file size of 0 Bytes and then an error PXE-E18 Server response time out.
    • This infomration indicated that PVS targets were getting correct DHCP IP addresses and scope options, but failing to download the boot file over tftp.

Network traces were captured on the PVS servers

  • The target device was rebooted, repeating the same screen showing error PXE-E18, and the network trace showed packets coming from the PVS target to the TFTP port 69, but no response packets.
  • Using windows inbuilt tftp client on another windows machine in the same vlan as PVS target devices, TFTP download of pvsnbpx64.efi was attempted and failed, showing the same network trace, packets coming into port 69, but no response packets.
  • Using a third party tftp server on the PVS server, with Citrix TFTP service stopped and disabled, also showed no change.
  • BDM boot was configured on the target, to eliminate TFTP requirement, and network traces showed PVS login packets arriving to port 6910, but no response packets.

Cause

The original streaming network was configured as an isolated non route-able network, and so PVS servers streaming adapters were never configured with a default gateway or any routing.
This works well when all target devices are in the same broadcast subnet, but fails when network traffic needs to route to other networks, like when the PVS targets were moved to a separate network and vlan.

Resolution

The PVS servers streaming adapters were configured with a default gateway and a route added to the PVS target devices network vlan.

Issue/Introduction

After moving target devices to a new network, they booted to a black screen, showing station IP address, server IP address, correct NBP filename pvsnbpx64.efi, but showing NBP file size of 0 Bytes and then an error PXE-E18 Server response time out.