Mechanical support for the proof of theoretical properties of a process algebra. ... a given process algebra can be rewritten into a basic term, which is a term consisting of only ... As an alternative, we investigate how the rewriting mechanisms of
Table of Contents. Monitoring Citrix Provisioning Servers . .... Table of Figures. F
igure 1: The layer model of the Citrix Provisioning server .
Booting the PC is the process of loading the operating system from disk into ...
first portion of the boot sequence (steps 1-6) is controlled by programs stored in ...
a how to start script automatically a how to ... >/dev/msglog 2/dev/msglog
CSS runs power-on self tests on the hardware and checks the boot configuration.
During any of these phases, the CSS reports problems through error ...
May 5, 2014 - This paper illustrates using an intelligent application-aware storage ... Do: When running Login VSI tests
The mechanism of choice for explicit QoS support is Differentiated Services ... multiple service classes help to save costly WAN link capacity on integrated ...
The process begins when a user contacts the Citrix Web Interface (WI) server ... found under Advanced Host Detailsâare
delivering cloud services. Accelerate your implementation ... Overtureʼs Citrix Consulting services can assist in the d
The server module delivers the XenDesktop servers and virtual desktops. We use XenServer 5.6 as ... our XenDesktop-hoste
You can shift expensive, labor-intensive desk-side tasks to an automated process that saves money and ... access to Leno
An application to VPN provisioning ... A customer requests a service to the ... Considering the complexity of required services, according to the customer SLA ...
Conference on Local Computer Networks Workshops (LCN '12 Workshops), ... under the Ontario Research Fund-Research Excellence (ORF-RE) program, and ...
tive analysis, we use the ArcGIS software. ..... ios occur due to varying LUC rates. As energy ..... ios by revealing the complexity of cause-and-effect relationships.
provisioning ubiquitous, sensing-based information services. As parts of the ... Conference on Local Computer Networks Workshops (LCN '12 Workshops),.
As we can see, all the native IMS element groups need to be combined for advanced conferencing services provisioning. The involved nodes are: Serving Call ...
This paper presents the distributed service development and provisioning framework, which is designed .... ding on the specific service provider's profile and.
Provisioning Resilient, Adaptive Web Services-based Workflow: A Semantic. Modeling Approach ..... the time taken to repair a service where TTR represents ...
Apr 5, 2012 - Organic and 15 Conventional agricultural fields with varying species ...... Pimentel D, Harvey C, Resosudarmo P, Sinclair K, Kurz D, McNair M,.
we characterize the paradigmatic case of Facebook, considering not only the traffic flows but also the main organizations and. CDNs providing them. Our study ...
May 11, 2011 - Create the Provisioning Services Target Devices . ..... is best to configure a default template for the c
BDM uses a two-‐stage boot process where the PVS loca1on is hardcoded into
the bootstrap ... Windows Opera1ng Systems starts loading drivers and.
BNISTACK is ... Star1ng with PVS 7.x a BDM hard disk par11on can be assigned
to virtual.
Citrix Provisioning Services (PVS) Boot Process 1
2
IP Acquisi9on
The PVS target device acquires an IP address using the DORA process. The following configura@ons are supported:
DHCP
Single Read Mode Acer a target device has logged into PVS and has been directed to a PVS Server for streaming, the bootstrap file (ARDBP32.bin, TSBBDM.bin or TSBOROM.bin) will then intercept any requests (i.e. hard disk requests) made to Interrupt 13.
DHCP
An IP Address is obtained using the following Discover, Offer, Request and Acknowledge (DORA) process.
5
BNISTACK / MIO
During the final phase, the BNISTACK Driver is loaded and mul@ple I/O (MIO) begins
BNISTACK
The TFTP Server Name is obtained from DHCP op@on 66 and the filename is obtained from DHCP op@on 67.
1. The Target Device broadcasts DHCP Discover packets.
ARDBP32.bin
DHCP Discover Broadcast Target Device
4
Bootstrap Download The bootstrap file is downloaded from the TFTP Server to the Target Device using the TFTP Server from DHCP op@on 66 and filename (ARDBP32.bin) from DHCP op@on 67. TSBBDM.bin is downloaded if Boot Device Manager (BDM) is used and TSBOROM.bin is used if the target devices use op@on ROM (OROM).
v1.4
2. The DHCP Server sends a DHCP Offer packet to the Target Device with the IP address, Subnet Mask, lease @me. DHCP Default Gateway and DNS Server Domain Name informa@on Server to the Target Device.
Simple Requests & Replies PVS Server
Target Device
Target Device
Target Device
The Target Device and the PVS Server will con@nue to communicate exchanging vDisk data un@l the Microsoc PVS Windows Opera@ng Systems starts loading drivers and Server BNISTACK is successfully loaded.
DHCP Offer Packet 3. The Target Device sends a unicast message to the DHCP Server reques@ng the offered IP address. A Transac@on ID is used to track the accepted offer. The Target Device will send a broadcast message no@fying other DHCP Servers that the offer from another DHCP Server was accepted. DHCP Request
Boot Device Manager (BDM)
BDM uses a two-‐stage boot process where the PVS loca@on is hardcoded into the bootstrap generated by BDM. The rest of the required boot informa@on like the low level PVS device drivers is downloaded from the PVS Server using a proprietary download protocol based on TFTP that uses UDP port 6969.
4. The DHCP Server sends a DHCPACK packet to the Target Device.
Network Boo9ng – w/DHCP Op9ons (no PXE Service) In this configura@on, the DORA process explained above is used in addi@on to the following:
Target Device
The TFTP Server Name and BooWile Name (ardbp32.bin) is provided using op@ons 66 & 67
During the MIO stage, the Target Device is opera@on and read /write requests occur as follows:
Typical Read Requests
Single Read Request Packet Mul9ple Read Reply Packets
TSBBDM.bin
DHCP Offer Packet
Target Device PVS Server
Target Device
Op9on ROM (OROM)
Target Device
On Target Devices that use op@on ROM, the bootstrap file name is configured on the network interface card (NIC) . TSBOROM.bin
In this scenario, the Target Device is configured for network boot. 1. The firmware of the Target Device adds op@on 60 to the DHCP Discover packet being broadcast. DHCP Discover Broadcast Target Device
Target Device
This op@on is used with devices from Dell and others that use the Intel Desktop Board. Further informa@on can be found at h[p://download.intel.com/products/motherboard/ DQ45CB/323251.pdf
Star@ng with PVS 7.x a BDM hard disk par@@on can be assigned to virtual machines during ini@al VM deployment via the XenDesktop Setup Wizard. This scenario does not use the two-‐stage boot because the newly created BDM is monolithic and already contains the low level PVS drivers. The TFTP-‐ based download protocol is no longer needed.
DHCP Acknowledgement
The Target Device ini@ates a handshake with the PVS Server sta@ng the BNISTACK driver is up. BNISTACK is loaded into memory and takes over for the bootstrap managing the MIO communica@on. At this point , the following informa@on is exchanged: • vDisk name • Image Mode • Ac@ve Directory Password Management Op@on • Write Cache Type and Size • Client Name • Licensing
Single Write Reply Confirma9on Packet
PVS Server
*MIO writes occur when the vDisk is in private mode or the write cache is configured for server side cache. PVS Server
2. DHCP Server responds with IP Address, Gateway and Subnet informa@on. DHCP Server Reply 3. The PXE Server replies with the TFTP Server address and bootstrap file name.
PXE & DHCP Servers
PXE Server Reply 4. The Target Device sends a request to the TFTP Server for the bootstrap file.
3
PVS Logon Process
Summary Load Balancing Algorithm
Acer the Target Device gets an IP address and downloads the bootstrap file it proceeds to login to a PVS Server to start streaming the vDisk image. This steps are as follows:
Bootstrap File Request 5. The TFTP Server replies with the bootstrap file name. Bootstrap File Reply
When using a Citrix Boot ISO to download the bootstrap the Target Device gets the IP address informa@on directly from the boot ISO and downloads the bootstrap manager. As configured in the Boot Device Management (BDM) configura@on.
Citrix Boot ISO – DHCP In this scenario, BDM is configured for the Target Device to use the DORA process to get the IP address informa@on. Then the two stage bootstrap download will start.
Get IO Port
Get Login Port
TFTP Server
Citrix Boot ISO – Sta9c IP
Target Device
• The Target Device contacts the PVS Server specified in the bootstrap file using the default UDP port 6910. • The server responds with the IP address and port to Con@nue the login process.
PVS Server
Login Start • The Target Device iden@fies itself by its MAC address and specifies the type of login being requested. Transferred to IO • The PVS Server moves the Target Device from the login thread to the I/O thread. The PVS Server replies with all disk, client and policy informa@on needed and sent to the Target Device.
The Target Device requests the IP address and port used for the single read mode. Target Device
Get IO Service
PVS Server
The Target Device requests the PVS Server start the I/O thread and requests informa@on on which vDisk to use. Login Complete • The PVS Server grants access for the I/O opera@on to the Target Device. • Addi@onal configura@on is sent specifying the boot device. Get vDisk Informa9on • The Target Device requests which vDisk will be streamed. • The PVS Server replies with the vDisk informa@on including write cache loca@on if the Target is in standard mode.
All PVS servers are capable of ac@ng as both a login server and an I/O server. A PVS login server normally aeempts to load balance devices between all servers that have access to a given vDisk when the device ini@ally logs in. The login server only bypasses load balancing if the server override property is set for the vDisk locator. The load balancing algorithm provides simple connec@on count balancing. (i.e. the login server aeempts to place the same number of devices on each server that has access to a given vDisk.)
The following summarizes the PVS Boot Process detailed on the diagram: 1. IP Acquisi@on – The Target Device acquires an IP address. 2. Bootstrap Download – The bootstrap file is downloaded. 3. PVS Logon Process – The Target Device logs on to PVS. 4. Single Read Mode – Single read mode communica@on is established between the Target Device and the PVS Server. 5. BNISTACK / MIO – The BNISTACK driver on the Target Device takes over communica@ons with the PVS Server and Mul@ple I/O occurs.
Authors: Citrix Technical Support/Provisioning Services Escala@on Team Please submit feedback to hep://support.citrix.com/ar@cle/CTX136378
