Tonight I need to configure the Multipath Policy from “Most Recently Used” to “Round Robin (VMware) on our vSphere 4.1 and HP EVA6400 environment. After reading “Configuration best practices for HP StorageWorks Enterprise Virtual Array (EVA) family and VMware vSphere 4” I decided to change the path status

To check the status of the Multipath Policy you can run the following PowerCLI script:

Per host:

Get-VMhost ESXHOST | Get-ScsiLun -LunType disk

Per Cluster:

Get-Cluster CLUSTERNAME| Get-VMHost | Get-ScsiLun -LunType disk

To change the Multipath Policy you can run the following command:

Per Host:

Get-VMHost ESXHOST | Get-ScsiLun -CanonicalName "naa.6005*" | Set-ScsiLun -MultipathPolicy "roundrobin"

Result in vCenter:

Last week I had some trouble by a customer, 4 of my 8 datastores aren’t visible/accessible on the 6 ESX 3.5u2 hosts connected to a (FC) HP MSA1500.  Some datastores become unavailable and some were not affected. Numerous VMs were down, some of those with warning messages like Orphaned and Inaccessible.

Oke.. let’s troubleshoot:

Checking for active paths: esxcfg-mpath -l | grep -i active

FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:2 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:6 On active preferred
Local 70:0.0 vmhba2:0:0 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:1 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:5 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:3 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:7 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:0 On active preferred
FC 6:2.1 210100e08bb27a58<->500508b30091aac9 vmhba1:0:4 On active preferred

All online!

Checking for death paths: esxcfg-mpath -l | grep -i death

[root@esxmeri01 /]#

None death paths!

Checking my HBA’s connected to the SAN: cd /vmfs/devices/disks and list:  ls vmh*

vmhba1:0:1:0  vmhba1:0:2:1  vmhba1:0:4:0  vmhba1:0:5:1  vmhba1:0:7:0  vmhba2:0:0:1   vmhba2:0:0:3  vmhba2:0:0:6  vmhba2:0:0:9
vmhba1:0:1:1  vmhba1:0:3:0  vmhba1:0:4:1  vmhba1:0:6:0  vmhba1:0:7:1  vmhba2:0:0:10  vmhba2:0:0:4  vmhba2:0:0:7
vmhba1:0:2:0  vmhba1:0:3:1  vmhba1:0:5:0  vmhba1:0:6:1  vmhba2:0:0:0  vmhba2:0:0:2   vmhba2:0:0:5  vmhba2:0:0:8

All online!

Represent LUN’s from HP ACU to ESX hosts:

I unpresent and represented the LUN’s in the HP ACU to the hosts, did a rescan but no still no success

Read more…

Guillermo Musumeci has written a good tool for removing HP Proliant Support Pack, also a good tip @ Twitter: “Nice tool before p2v action” indeed, you must remove all driver software before you start p2v .

Download: Here

Description:

When a remote connection is established with Integrated Lights-Out/Integrated Lights-Out 2 (iLO/iLO2) using Internet Explorer 8, the browser may stop responding due to Internet Explorer 8 security features. The issue occurs while connecting to the iLO webpage and starting IRC or another iLO/iLO2 remote console client.

Scope:

Any ProLiant server using Integrated Lights-Out/Integrated Lights-Out 2 (iLO/iLO2) and connecting to a Remote Client using Microsoft Internet Explorer 8.

Resolution:

As a workaround, the iLO/iLO2 IP address or DNS name can be added to the Intranet Explorer 8 "Local Intranet" zone that lists Intranet websites.

Perform the following steps to add the DNS website name or IP address:

1. In Internet Explorer 8 click on "Tools->Internet Options" and the Internet Options pop-up will be displayed.
2. Click on the "Security" Tab.
3. Select the "Local Intranet" icon and click on the "Sites" button to the right and the "Local Intranet" pop-up will be displayed.
4. Click on "Advanced" and add the iLO/iLO2 IP address or DNS name into the blank text box and add the website to the local Intranet zone.
5. After adding the website, click on "Close" to save the website in the zone.

After adding the iLO/iLO2 IP address or DNS name in the Internet Explorer 8 local Intranet zone, all iLO/iLO2 clients will connect as expected.

Source: HP and for the tip Eric Gray

Het is daarstraks niet gelukt om te upgraden van HP Management Agent versie 8.1 naar versie 8.2, had voorheen ook mijn oude installatie bestanden verwijdert.

Om de HP Management Agents te deinstalleren opnieuw de oude “hpmgmt-8.1.0-vmware3x.tgz” gedownload en uitgepakt met tar -zxvf hpmgmt-8.2.0-vmware3x.tgz

Uit de map: /var/tmp/update/hpmgmt/810/ het volgende commando uitgevoerd:

./installvm810.sh –uninstall

De agents worden nu juist gedeinsatlleerd:

De nieuwe installatie kan worden uitgevoerd.

Download: hpmgmt-8.2.0-vmware3x.tgz

Download URL: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-f7e5291b6fe84bdd95f996a7b1

Release notes:

Important:

• The HP Insight Manager Agents version 8.2.0 supports VMware ESX 3.0.2 and higher versions only.
• The upgrade of HP Insight Manager Agents is not supported. Please uninstall the older version before installing the HP Insight Manager Agents version 8.2.0.
• The Emulex and Qlogic libraries will need to be downloaded from Qlogic and Emulex websites directly. For detailed download and installation instructions for these libraries, please refer to the “README” file, which is included in the downloadable HP Insight Manager package.

• For the HP Insight Manager Agents to function properly with ESX 3.x, the firewall ports for the ‘hpim’ service (2381) and the ‘snmpd’ service need to be enabled. Please see the README file for additional details regarding how to enable these firewall ports during the Insight Manager Agents installation.
• Configuring multiple trap destinations during silent installation of this package is currently not supported. If you want to configure multiple trap destinations, edit the “snmpd.conf” file to add the trap destinations and restart both the ‘snmpd’ and ‘hpasm’ services.
• If the internal health LED on a server is amber, the server might shutdown or reboot as soon as the HP Insight Manager Agents are installed. This feature is called Automatic Server Recovery, and is enabled to ensure that the server can be recovered even though there is a major hardware problem. Please get the hardware error fixed if the color of the internal health LED on your server is amber.
• The hp-OpenIPMI package is installed on ESX 3.0 and above. This package is for servers with iLO 2 and an IPMI Base Management Controller.
• During the installation and configuration of HP Insight Manager Agents, the install script may prompt whether to keep the existing snmpd.conf file. The default to this prompt is ‘n’, which will then continue to gather the required SNMP configurations. Answer ‘y’ to this question only if you have a snmpd.conf file already configured with read/write strings and dlmod support.

./installvm820.sh –silent –inputfile hpmgmt.conf

Today I started a new project where I had to configure 2 HP StorageWorks 4/16 SAN Switches. The firmware 5.3.0 was installed. The switches are configured with a static ip address 10.77.77.77/24 you can change your laptops ip address to an ip in the specified range and login to the java applet. Another option is to connect the console cable to the switch and configure it by console. I encountered some problems trying to upgrade the firmware by using the java applet.

After changing the ip address and starting the java applet the java applet would not start. I tried different java versions but still the problem remains. The java applet starts loading until “initializing switch details” where it will freeze to load the java applet.

Instead of trying to install all know java versions to start the java applet I had to upgrade the firmware to the latest version by using the console.

I connected the console cable to the switch and powered it up and started HyperTerminal.

1. Type in “admin” to login on to the console

2. Type in “password” to login on to the console

3. Press “Ctrl-c” at this moment we don’t want to change the password

4. Type in “ipaddrshow” to show the default ip address

5. Type in “ipaddrset” to change the ip configuration

6. Press the “enter-key” until you see the DHCP[Off] prompt

7. Type in “on” to turn on the dhcp option

8. To check the version type in “version” to upgrade to the latest version we need first to upgrade to 6.0.0b.

9. Download the firmware extract the files and place the files on an FTP server.

10. Type in “firmwaredownload” to start the firmware upgrade

11. Type in the FTP-Server ip address

12. Type in the location of the firmware files located on the ftp server. Don’t forget to add “release.plist” at the end

13. Type in “y” to upgrade the firmware. You can get a cup of coffee this will take a few minutes.

14. The upgrade completed successfully

15. Start IE7 to load the applet to see if the upgrade had any effect. Browse to the ip address that was assigned by the dhcp server.

16. The login screen will popup

17. Type in the “User Name” and “Password” to load the applet

The swd77 Web Tools popup so the upgrade was successfully and works with my current java version. Now I can use the GUI to upgrade the firmware to the latest version and configure zoning.