How Not to Assign KVM IP Addresses Via Cisco UCS Manager

Boxing-gloveAfter a few hours poking around a newly deployed UCS cluster trying to get some basic profiles created and assigned. I realized that I had actually no idea how the KVM is actually supposed to work inside the UCS cluster. Which is funny as this was a subject that we touched on during my DCUDC class. Apparently we did not touch on it enough.

Anyway, before I get ahead of myself, lets review the gear in this cluster.

2 5108 chassis
7 B200 M2 blades with 2104 IOMs
2 6248s Fabric Interconnects

Now in my network all lights out management ips (ilos, ipmi, etc) are all on one particular vlan, which for the purpose of this post we will call VLAN 100. Non application related infrastructure equipment (servers, virtual hosts) are on another vlan, which we will call VLAN 200. So when the Fabric Interconnets were deployed, I gave them each an ip address on VLAN 200. And once UCS Manager was up and running, I created a KVM ip address pool of unused ip addresses on VLAN 100. Well guess what, this is wrong.

Routing for the KVM addresses is done through the management interfaces on the Fabric Interconects, so unless you are using vlan tagging, your KVM pool must be on the same vlan as the ip addresses assigned to your Fabric Interconnects.

But wait, why is this?

I thought that I could even assign private 192.168.x.x ip addreses to the KVMs as they were only supposed to be managed via the UCS Manager, but this also incorrect.

Navigate to one of your working KVM ip addresses in a web browser and you can access the KVM of the blade outside of UCS Manager. Nice, which is how I actually expected this to work. 

Logo

Note that I find it rather dumb to have my KVM management ips and Fabric Interconnects on the same vlan as a rule, however since this is how its supposed to work I am going to have to let that one go.

Now, the fact that you can navigate to a specific KVM IP address via a web browser also makes the idea of using a pool of ip addresses silly. Would you not want to hard code the KVM ip address in the service profile so that you always know which server's console you are logging into? Dunno, I am still working on figuring that one out.

 

Advertisements

Reset HP ILO Via the Command Line

Gary_the_snail Its not unheard of that an HP ILO (Integrated Lights Out) can become sick and slow down to a crawl. When this occurs, a restart of the ILO is in order, which is easily accomplished via the ILO cli interface. Note that you need to make sure that that you have enabled ssh access in ilo.

The steps to reset an ilo via ssh are below.

</>hpiLO-> cd /map1
status=0
status_tag=COMMAND COMPLETED

</map1>hpiLO-> reset
status=0
status_tag=COMMAND COMPLETED
Resetting iLO.

CLI session stopped

Additional Resources:

http://fatmin.com/2011/06/13/redirect-linux-console-to-hp-ilo-via-ssh/

http://www.thevirtualway.it/en/?p=985

http://setaoffice.com/2010/07/17/connecting-to-hp-ilo-using-the-command-line/

ProLiant System Management Homepage

Prod-shot-170x190 The HP Systems management homepage is a web based utility for managing and monitoring Proliant Servers. It can be installed via the ProLiant Support Pack DVD (on linux its just an rpm). Once installed you can modify the default settings via the perl script, hpSMHSetup.pl located in /usr/local/hp.

To access your server's homepage navigate to https://<yourhostname>:2381 in your browser. You must include the https:// part of the url. Use your root user and password to access.

From the homepage you can monitor system, subsystems and status views of your server. Any critical, major, minor, or warning alerts will appear in the Overall Status Summary.

 

Sun 5220 Console and ILOM How To

solaris_logo

As far as I know this documentation is specific to Sun T5150s and Sun T5250s. However some of the information below may also pertain to other Sun systems running ILOM.

ILOM Commands

To power on the host, type:

start /SYS

To power off the host, type:

stop /SYS

To reset the host, type:

reset /SYS

How to set the system not to auto boot the OS

Example:

-> set /HOST/bootmode script=”setenv auto-boot? false”

Press Enter and then type:

-> reset /SYS

Accessing the Console from ILOM

start /SP/console

Configuring a Static IP Address Using CLI and Ethernet

Log in to the ILOM using Secure Shell (SSH) over the network, or
by connecting a terminal to the serial port. To establish a Secure Shell (SSH)
connection to the CLI, type the appropriate connection command in the
SSH application. For example, to connect to the ILOM with an IP address
of 129.144.82.20, type the following command:

# ssh -l root 129.144.82.20

Type the following command to set the working directory.

cd /SP/network

Type the following commands to specify a static Ethernet
configuration.

Note – The following values are samples only. You must specify the IP
address, netmask, and gateway appropriate for your ILOM and network
configuration.

set pendingipaddress=129.144.82.26
set pendingipnetmask=255.255.255.0
set pendingipgateway=129.144.82.254
set pendingipdiscovery=static
set commitpending=true