HP iLO 3 Scripting and Command Line Guide

EJECT_VIRTUAL_MEDIA runtime errors

Possible EJECT_VIRTUAL_MEDIA errors are:

• RIB information is open for read-only access. Write access is

required for this operation.

• User does not have correct privilege for action. VIRTUAL_MEDIA_PRIV

required.

• No image present in the Virtual Media drive.

• An invalid Virtual Media option has been given.

GET_VM_STATUS

GET_VM_STATUS returns the Virtual Media drive status. This command must display within a

RIB_INFO element.

For example:

<RIB_INFO MODE="read">

<GET_VM_STATUS DEVICE="FLOPPY"/>

</RIB_INFO>

</LOGIN>

</RIBCL>

GET_VM_STATUS parameters

DEVICE specifies the Virtual Media device target. The possible values are FLOPPY or CDROM. If

the DEVICE is not specified, FLOPPY is assumed. These values are not case-sensitive.

GET_VM_STATUS runtime errors

The possible GET_VM_STATUS error is:

An invalid Virtual Media option has been given.

GET_VM_STATUS return messages

The return message displays the current state of the Virtual Media. The VM_APPLET parameter

shows if a virtual media device is already connected through the Integrated Remote Console, Java

Integrated Remote Console, or the iLO 3 graphical interface. If the VM_APPLET = CONNECTED,

then the (non-URL based) Virtual Media is already in use and cannot be connected through scriptable

Virtual Media or Virtual Media XML commands.

NOTE: Only URL-based Virtual Media can be connected through scriptable Virtual Media or

Virtual Media XML. However, URL-based Virtual Media will display as DISCONNECTED through

VM_APPLET even if an URL-based VM is configured via the iLO, Integrated Remote Console, Java

Integrated Remote Console, CLI, or RIBCL.

The DEVICE parameter tells which device this return message is for. The BOOT_OPTION shows

the current setting; BOOT_ALWAYS means that the server always use the Virtual Media device for

booting, BOOT_ONCE means that the server boots to the Virtual Device once and then disconnects

the Virtual Media on the subsequent server reboot, and NO_BOOT means that the Virtual Media

does not connect during a server reboot. The WRITE_PROTECT_FLAG parameter shows if the

Virtual Media image can be written to. The IMAGE_INSERTED parameter tells if the Virtual Media

device is connected via the scriptable Virtual Media or the Virtual Media XML command.

A possible GET_VM_STATUS return message is:

94 RIBCL XML Scripting Language