fredag 19. november 2010

HP SIM Agent Configure on ESXi 4.1

http://communities.vmware.com/message/1590665


There is no HP Agent for ESXi. What you probably installed (at least I hope...) is the CIM offline bundle for HP.

Once you have those installed, you have to configure HP SIM to use WBEM (NOT SNMP) to communicate with the ESXi server. I actually had to do this very recently and documented it. See below:

1) Make sure the HP CIM bundle is installled. To do this, either install ESXi with the HP version of ESXi, or install the offline bundle downloaded from HPs site. To install the offline bundle:

1) Log onto VMWare VC Server
2) Go to Start Menu and Launch the VMWare CLI
3) Cd to the bin directory: c:\program files (x86)\Vmware\VmWAre vSphere CLI\bin

To Verify what patches in the bundle apply to your host:

Vihostupdate.pl --server servername --scan --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --scan --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

Make

To install:

Vihostupdate.pl --server servername --install --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --install --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

2) Go to HP SIM, and go to Options -> Discovery.

3) On the discovery screen, create a new discovery task. Add your ESXi hosts to the "Ping inclusion ranges/host names" text box.

4) CLick the blue Credentials button on the bottom (this is important).

5) CLick Show advanced protocol credentials.

6) Click the WBEM/WMI tab.

7) Enter in a valid username and password for your ESXi Host (I use root and the root password).

8) Click OK.

9) Now save the task by clicking Save.

10) Run the task by selecting it's radio button and clicking Run Now.

This should cause it to appear in HP SIM. Now, you need to setup WBEM indications (they replace SNMP traps).

To do this:

1) Log into Insight Manager on AH-Monitor1

2) Go to Options -> Events -> Subscribe to WBEM Events

3) Verify your server is in the Targets list (Click Add Target if necessary).

4) Click Next and finish the wizard to activate these events.

5) Reboot the ESXi Server to have this take effect.

tirsdag 7. september 2010

Hvordan sjekke når en VMware ESX host sist har bootet + grep-kommando

For å sjekke når en VMware ESX-host sist har bootet fra kommando-linje, kan man bruke kommando'en
"last"
Denne vil vise siste aktivitet og boot.

For å sjekke logger, bruk kommandoen:   grep "" vmkernel*

onsdag 28. juli 2010

How to configure iLO on ESX-servers

Physical access it not necessary to configure ilo, I do it all the time with the hponcfg utility.... which in some ways is very scary that you can get physical access to the host from inside the host, but since the capability is there you might as well take advantage of it.

First you need to download and install the hponcfg utiltity from HP:
hponcfg 1.6.0-1 (linux)


Then you need to install it via rpm
#>rpm -ivh hponcfg-1.6.0-1.linux.rpm

Next, you will need to craft a .xml file to change your ip information and possibly your passwords. Note that you don't have to know the admin password to change the admin password and/or network settings. I'll post a sample one here which covers most of the basics. If you want to auth ilo against AD you'll have to do some more work. Download the attachment that I added, change to match your variables. Then you just need to apply the .xml

#>hponcfg -f configure_ilo.xml

Attachments:
configure_ilo.xml (994 bytes)

mandag 19. juli 2010

List of Control Panel apps (*.cpl) you can launch from command line.

Accessibility Options
access.cpl


Add/Remove Programs
appwiz.cpl

Add Hardware Wizard
hdwwiz.cpl

Automatic Updates
wuaucpl.cpl

Bluetooth Properties
bthprops.cpl


Display Properties
desk.cpl


Firewall Properties
firewall.cpl


Game Controllers
joy.cpl


Internet Options
inetcpl.cpl


iSCSI Initiator
iscsicpl.cpl


Java Control Panel
jpicpl32.cpl


Licensing Mode
liccpa.cpl


Mouse Properties
main.cpl


Network Connections
ncpa.cpl


Network Setup Wizard
netsetup.cpl


ODBC Properties
odbccp32.cpl


Power Options
powercfg.cpl


Regional and Language Options
intl.cpl


Sound and Audio Devices
mmsys.cpl


Stored Passwords
keymgr.cpl


System Properties
sysdm.cpl


Telephone and Modem Properties
telephon.cpl


Time and Date Settings
timedate.cpl


User Accounts
nusrmgr.cpl

Windows Security Center
wscui.cpl


Wireless Link
irprops.cpl


tirsdag 1. juni 2010

UNetbootin create bootable Live USB drives for Ubuntu, Fedora, and other Linux distributions

Introduction


UNetbootin allows you to create bootable Live USB drives for Ubuntu, Fedora, and other Linux distributions without burning a CD. It runs on both Windows and Linux. You can either let UNetbootin download one of the many distributions supported out-of-the-box for you, or supply your own Linux .iso file if you've already downloaded one or your preferred distribution isn't on the list.

http://unetbootin.sourceforge.net/

torsdag 15. april 2010

Extend'ing disks in WMware

http://www.penguinpunk.net/blog/?p=12

If you’re working in a VMware ESX environment, you should normally be able to use SAN-based disk expansion technologies, combined with diskpart in Windows, or vmkfstools in VMware ESX, to achieve the desired result.

In Windows, run the following commands to extend a basic volume:

diskpart

list volume

select volume x (where x is the number of the volume you wish to extend)

extend

exit

In VMware ESX, run the following command to extend a vmdk disk file:

vmkfstools -X 50G disk.vmdk

Note that the 50G value is the new size of the disk, not the extra space you require.

If you find yourself needing to extend a boot volume in Windows Server 2003, diskpart won’t be any help. Before you reach for the gparted ISO file, think about combining vmkfstools with another (test) Virtual Machine. Here are the required steps:

1. Backup your VM (VM1).
2. Shutdown VM1 and run vmkfstools against VM1’s disk file.
3. Attach the disk to a second guest (VM2).
4. Run diskpart on the volume (in this case it will probably be D: or something similar).
5. Once the volume is extended, shutdown VM2 and remove (but don’t delete) the disk from VM2’s config.
6. Attach the newly expanded volume to VM1.
7. Boot VM1.
8. Profit.

I hope that’s provided a starting point for further investigation into basic and dynamic disks. Remember, before converting every volume in sight to Dynamic, think very carefully about the ramifications of doing this.

onsdag 17. mars 2010