Install Dell OpenManage 7.4 on XenServer 6.5

Download PDF

1.

Login to your console through SSH like ssh root@YOUR-XEN-SERVER-IP

2.

Add the Dell repository

To do this run this command:
wget -q -O – http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

3.

Install lockfile
OpenManage needs a binary called ‘lockfile’ which can be found in the ‘procmail’ package and seems to be working. Execute these commands to install the binary:
yum –enablerepo=base –disablerepo=citrix install procmail
cp /usr/bin/lockfile /tmp/
yum remove procmail
mv /tmp/lockfile /usr/bin/lockfile

4.

Install srvadmin-all
To install the OpenManage software run this command:
yum –enablerepo=base –disablerepo=citrix install srvadmin-all

5.

Add a firewall rule
Before we can access the web-interface we need to add a rule to the firewall and restart iptables:
vi /etc/sysconfig/iptables
Add this line before the REJECT line at the bottom:
-A RH-Firewall-1-INPUT -m state –state NEW -m tcp -p tcp –dport 1311 -j ACCEPT
Restart iptables:
service iptables restart
Start the services

6.

To start the services run this command:
/opt/dell/srvadmin/sbin/srvadmin-services.sh start

7.

Access the web-interface
To access the web-interface open your browser (IE, Firefox or Safari, chrome doesn’t work) and go to:
https://YOUR-XEN-SERVER-IP:1311/
You can now login with your XenServer root login and password.

iSCSI Naming and Addressing

Download PDF

In an iSCSI network, each iSCSI element that uses the network has a unique and permanent iSCSI name and is assigned an address for access.
iSCSI Name
Identifies a particular iSCSI element, regardless of its physical location. The iSCSI name can use IQN or EUI format.

IQN (iSCSI qualified name)

. Can be up to 255 characters long and has the following format:
iqn.yyyy-mm.naming-authority:unique name

yyyy-mm
The year and month when the naming authority was established.

naming-authority
Usually reverse syntax of the Internet domain name of the naming authority. For example, the iscsi.vmware.com naming authority could have the iSCSI qualified name form of iqn.1998-01.com.vmware.iscsi. The name indicates that the vmware.com domain name was registered in January of 1998, and iscsi is a subdomain, maintained by vmware.com.

unique name
Any name you want to use, for example, the name of your host. The naming authority must make sure that any names assigned following the colon are unique. For example, iqn.1998-01.com.vmware.iscsi:name1.

EUI (extended unique identifier)

. Includes the eui. prefix, followed by the 16-character name. The name includes 24 bits for the company name assigned by the IEEE and 40 bits for a unique ID, such as a serial number.
For example,
eui.0123456789ABCDEF

iSCSI Alias
A more manageable, easy-to-remember name to use instead of the iSCSI name. iSCSI aliases are not unique, and are intended to be just a friendly name to associate with the node.

IP Address
An address associated with each iSCSI element so that routing and switching equipment on the network can establish the connection between different elements, such as the host and storage. This is just like the IP address you assign to a computer to get access to your company’s network or the Internet.

Install XenApp – Failed to configure component ‘Citrix licensing’

Download PDF

xenapp

Installing Citrix XenApp 6 Fundamentals on Server 2008R2

 

Citrix XenApp 6 installation instructions say all necessary prerequisites will be automatically installed by it’s installer. Maybe in Citrix world, but not in reality. Installation fails after 10 seconds and logs usually shows a message like “Failed to configure component ‘Citrix licensing’ “ or “Failed to configure component ‘Citrix Delivery Services Console’ “.

To get it going, you will have to start with a clean system.. No updates installed, nothing! I made a mistake here by updating my Server 2008 R2 OS with latest patches. It seems that some of them are causing install to crash even with all prerequisites installed. So first thing to do is NOT TO UPDATE YOUR OS. After XenApp install is complete, you can make an image of your system and install updates one by one and test which one fails. But in this post we won’t talk about that.

1. Install clean Server 2008 R2 – NO WINDOWS UPDATES (you can play with that later)

2. Join the domain (setup it’s IP, name etc first)

3. Add the following ROLES

– .net 3.5 (Application Server Role – not under Features)

– IIS 7 (Web Server Role – I added IIS 6 compatibility service as well)

– Remote Session Host and Licensing server

4. Reboot the server

5. Run the installer

 

It should work fine now.

Thanks Citrix for making it easy 🙂