Configure HP Blade ,C7000 and HP Virtual Connect Manager (VCM) for XenServer infrastructure.

HP C7000 chassis can hold different blade model and for that refer to HP site . Here I am going to explain how HP Blade Center can be designed for XenServer . XenServer require 1 management NIC . This NIC can not be tagged at XenCenter level . Hence at the switch side this needs to be defined as trunk with access for management VLAN (Incase there is a dedicated VLAN ). Its a good practice to dedicate a VLAN for XenServer host.

Now out of 8 nic (by default Blade BL 460 G6 sever can give 8 NIC with nic partitioning . These 8 nic can be divided to be used as FcOE or ethernet . In below example I am using two NIC for management interface , two NIC for VM traffic and other two for FcOE. Here you can see there is last leg where FcOE is installed.

To start we need to ensure all the MAC as well as WWN is set to .

This is for Fibre network or FcOE.

Other setting is on advanced settings : Here we should use "Map VLAN Tags". Also we set the speed at server profile rather than global level.

Next is to create a uplink for ether network . This is called shared uplink set. There will be two shared uplink set as there are two switch . Each shared uplink set can have ports from respective switch and can not span across other switch. In other word we can have ports from single VCM. This will create one bundle provided on core switch there is a ether channel or LACP is done on the core switch.

After all the ports are mapped this will be look like this . Here four 1 Gb ports has been mapped to one share uplink . Hence uplink bandwidth from one VCM is 4Gb. 

For creating VLAN's we need to create on each of the SUS (Shared uplink Set) . Right click as shown below and select add. This will prompt for network details We need to be careful with tagging VLAN. Again set the network speed at NIC level.

Now define shared uplink for SAN. Assigned the port based connectivity.

Once SUS is defined for SAN this is how it looks like . Here each 2Gb port will be bundled to create 4Gb uplink to storage.

Now once these two SUS is created each for Ethernet as well SAN this should be mapped to the profile. "Multiple Networks " will allow you to create multiple VLAN on single bond or link . These VLAN can be selected as shown below after creating on each of the SUS. You can also see LOM in each BAY1 and BAY 2. Hence each blade will have 4 NIC on BAY 1 and 4 NIC on BAY2.

This is how the Ethernet Networks looks like when it is mapped . Here you can see each network is mapped to each of the server profile.

On XenServer , this is how looks like. Here you can see management NIC is set to 1GB where as other NIC is set to 2GB. 

We have created a Bond 2+3 for VM network and this is how VLAN is mapped .

That is all for now, hope you enjoyed

How to Change XenServer (6.0.2) pool IP address.

Prior to XenServer 6.0 if you have to change the pool IP address there were few steps need to be followed from CLI but with 6.0 and above it has been made simpler . How check this out:

1. I got two XS pool where I need to move both host from IP address to other IP address. Get the console access and then select the following from xsconsole

This will bring warning window

Select the interface and hit OK

Choose the static mode to re-ip the host

For the slave you will get following option

Finally it will prompt you reboot , make sure you reboot the pool master first and then all the slave. This needs to be done simultaneously .

Verint Screen recording integration with XenApp

In this blog I will explain the way to integrate Verint Screen recording solution with XenApp. Solution from Verint is used widely by call center where agent desktop and voice is recorded simultaneously . While these solution is meant for physical desktop but Verint does support this on XenApp. Citrix does have its own screen recording solution but it does not record the voice like Verint does. Not have a good knowledge but looks like it has integration with extension as well as desktop that way anyone can make out what agent is doing while talking over the phone.

Solution from Verint is called as  "Impact 360 Version 10 QM & Analytics " . As per support following XenApp version is supported :

First agent is install the agent on XenApp box and before the that there is pre-requisite is following

Now run the U100_8447.msi to install the agent

Choose the require module to install

From XenApp prospective "Thin Client Environment " should be checked

Provide the require setting, from XA prospective does not make difference .

Provide the require setting for ILA.

Go with default unless required changes.

This will start the installation of Verint impact agent .

Once the agent installation is completed make sure XenApp box is rebooted

Now after the installation is completed make sure few testing is performed. Login with the XenApp box and execute ILAQueryApp.exe. Type the any user agent login ID with domainname\username along with PBX ID. This query should throw result

Run the IntelliLink Analyzer and make sure it should show success for the same extension. It will also show Screen IP.

At the same time if task manager is launched on XenApp box , RFBAgent.exe/ILALoginApp.exe should be running under every user ID. This will ensure that recording will happen.

If the XenApp is published as Hosted Shared Desktop then nothing is required because each login will execute above two executable for each user. Now if recording as to be done for published application , it can be done in two way :

Option  1 – Automatic in Seamless Mode

If we have to execute this two executable for each application launch , following needs to be done

1   From the Impact 360 Version 10 Installation CD, from the Tools\Citrix folder, open the Citrix.zip and copy IlaApp.cmd to  the %WINDIR%\system32 folder.
2 Via Notepad, open UltraApp.cmd and verify that the directory path points to the ILA installation path. If not, modify the path accordingly.
3 Configure Anti-Virus not to remove IlaApp.cmd.
4 Run IlaApp.cmd and verify that the ILALoginApp, RFBAgent.exe and HostedApp processes appear in the Windows Task Manager; then end the processes.
5 From the Impact 360 Version 10 Installation CD, from the Tools\Citrix folder, open the Citrix.zip and run InstallILAforsharedapp.vbs to update the following registry keys:
HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\AppSetup
HKLM\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\LogoffCheckSysModules
These updates add RFBAgent.exe and Ilaloginapp.exe to the list of executables that seamlessly start upon a user's login and terminate upon logoff, thus ensuring the proper functioning of the CTI Agent.
6 Export the following registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\ILA (for rollback purposes).
7 Delete the following registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\ILA.
8 Verify the updates as follows:
a. On a Citrix client with no open session, run one of the published applications.
b. On the Citrix server, check the session information and verify that the RFBAgent.exe and ILALoginApp, processes appear in the Windows Task Manager.
c. From the same Citrix client session, run a second published application.
d. On the Citrix server, look at the session information and verify that the RFBAgent.exe, and ILALoginApp processes do not appear twice in the Windows Task Manager.
e. On the client side, close the second application.
f. On the Citrix server, verify that the session does not end on the Citrix server side and that ILA and RFB continue running.
g. On the client side, close the first application and verify that the session ends on the Citrix side and ILA and RFB stop running.

Apart of from above step even putting a login script for each user to run RFBAgent.exe, and ILALoginApp.exe. Also all the three executable Apps + (RFBAgent.exe, and ILALoginApp ) in a batch file and publishing the batch file will allow the seamless automatic launch of the agent + application

Option 2- Manually trigger the applications after login into thin client.

When the shared session mode cannot be used for all applications that need to be recorded (for example, a Citrix Farm where each server runs specific applications), you can provide a folder with application shortcuts. The user will then be able to activate Impact 360 V10 QM & Analytics applications by using the shortcuts residing in that folder. Note that this method enforces the manual activation of applications that are normally activated automatically upon login.

In below example before launching notepad , Verint ILA/Verint SAA should be executed

That's it for today and reference are :

A)  Impact 360 V10 Desktop Installations User Guide Ver M

B)  Impact 360 V10 Desktop Installations User Guide Ver V

C)  Impact 360 V10 Desktop Installations User Guide Ver K

How to test ISCSI speed and capture trace for ISCSI nic on XenServer

In this blog I am going to talk about test throughput of ISCSI lun and then capture the packet on storage interface. Later on these packets can be open via wireshark.

In the above example first do find out lun which is currently mapped by running ll /dev/mapper. In my case it is the first one .

Now use the command to read the file size of 10MB *100 time which is like 1GB of date read from the lun . At the same time run tcpdump command on the same XenServer (Basically two ssh session ) on nic which is connected to the storage sub system . In my case it is xenbr8 . This can also be determined by running "route " command.

Do the same to determine  write speed . There would be two .pcap file under root which you can import using winscp and latter can be open via wireshark . When it open via wireshark it shows complete path for packet transfer

How to create LUN on EMC VNX 5500 and assign it to XenServer host.

In my last post I explained how to map iSCSI interface from XenServer to VNX 5500 box. In this post I will explain how to create lun and map it to the XenServer Cluster.

Launch Unisphere console and select the box. Choose storage and from drop down select "LUNs". This will bring to the page where all the created lun will be listed. Hit "Create"

 

This will pop one box asking for information like

Storage Pool Type : It is better to choose pool

Raid type : This is defined while creating pool and I am not going to explain those details in my post as this post is

                       meant  creation and attaching lun to XenServer.

Storage Pool for new LUN: Again this is created when commissioning of storage.

Capacity will show space for each of the pool separately, not over all storage.

Rest is self explanatory. Under "Advance" tab make sure you choose "Auto" and this way you don't have to bother about owner of the LUN. As you know VNX 5500 is active passive storage.  

Tiering should be set to "Auto" as it will automate fail over process.

Once LUN is created you need to assign to the storage group. Assuming that respective Storage group is already created.

Once LUN is assigned to the storage  group . Then we have to assign host to the storage group . It  same place from where you can create Storage group. Select the respective Storage Group and click properties . Choose the hosts tab , from here move the available host to the connected host list . This will assign LUN tot he respective XenServer.

LUN tab will which SP is the owner of the LUN. There is also a state during the SP fail over which SP will own the  LUN .

How to update HOSTNAME on Dell IDRAC for PowerEdge M710HD server

Sometimes it is quite tough to find simple stuff on quite popular sites. May be I am stupid or may be its poor documentation. I was trying to update hostname as shown below because by default the hostname would be localhost.

In order to update this , boot the Dell server and press Ctrl+ E when you get below boot menu

This will bring iDRAC configuration utility . I was thinking this somewhere you can do from desktop. Yeah stupid of me. So choose "LAN Parameters" and then "Host Name String". It will popup box for hostname. Provide correct host name and exit with saving changes.

How to map iSCSI interface of XenServer 6.0.2 to EMC VNX 5500

I am starting series of blog with hastag "DellEMCXEN "which will talks about integrating XenServer with EMC VNX 5500. XenServer is installed on Dell Power Edgem710 HD with Chassis M1000e connected via Nexus 5500 and Dell switch M8024.

First define storage interface on XenServer and for that choose configure under "Management Interface " and then select "New Interface" . Now specify the name and then choose the NIC which will be configure for storage traffic. Supply IP address. This needs to be repeated for all the interface which is connected to the storage.

Once this is done then perform discovery of the nic for the logging into EMC. This can be perform via CLI as well as via XenCenter. To perform via XenCenter select new storage and choose "Software iSCSI". Choose "Name" and then under location provide information as follows :

Target host: This will be IP address of target Storage Processor or controller . Specify all the IP address with ,

Target IQN: Here you will find IQN of the target storage processor . If it has 4 ports then you will see 4 IQN. We need to choose the one which is highlighted (*)

This will log all the targets on the EMC VNX box to mapped .

From the command line following  needs to be run from the host in order to login.

Once all the message says successfully login , open EMC Unixshpere and select "Connectivity status "  on left hand side under "Hosts ". This will popup Host initiators window. You will find one name with just IQN as shown below. This is the new targets which has logged in . Select "Edit " from bottom and then provide information about "host name" "IP address" . IP address is of  XenServer  management IP . Make sure you choose initiator type as "clarion open " and Fail Over mode as "ALUA 4". ALUA is the latest fail over mode as per EMC and other storage vendors.

With this host will be connected to to EMC storage. In the next series , I will explain process of creating lun and attaching it to the storage group.

Forcibly take control of Dell -IDRAC console access

Some people have a bad habit of taking control of DRAC access and locking their workstation . If someone want to have access they have to wait till gentleman comes back and provide him so. One way its good but other way its frustrate other.

We can forcibly take control of session by resetting the console access . You can do this at your own risk :) . Launch the weblogin and press the tab "Reset iDRAC6"

Install XenServer 6.0.2 on Dell PowerEdge M710HD using Integrated Remote Access Controller

Installing XenServer is quite simple but option on Dell remote control access controller is little tricky. First we should insure that virtual media is attached by default it will be Detach as shown below.

Launch the Dell virtual console in order to map the ISO .

Attach the media virtual media using "Virtual media wizard" as shown below

Browse and assign the media using ISO image

Change the boot order to boot from the "Virtual CD"

This will bring the boot menu which will guide step by step to install XenServer 6.0.2

Select the Keymap which is mostly US

This will bring welcome screen

Accept the license agreement .

It depends what you want to . We are performing clean installation

This will detect the local hard drive where you want to install the XenServer . Choose thin provisioning if you want to enable intellicache for XenDesktop.

Installation media will be local media.

Supplement packs are required if you are planning to host linux as a guest VM's or else choose NO.

If you doubts the install media choose to verify or else skip it.

Type the password as Test123  :)

Here you are going to choose management interface. This can be bonded once it is added to the pool using XenCenter.

Choose the timezone which server belongs to not YOU :)

Select the correct country which server is located not YOU :)

Define the NTP server which you have or else choose the manual time entry

Specify the NTP server name or IP address.

Specify the host name and DNS server and continue with XenServer install .

You are all set.