Updating (preserving existing settings) – Dell Emulex Family of Adapters User Manual

Page 302

Advertising
background image

OneCommand Manager Command Line Interface Version 10.2 User Manual

P010067-01A Rev. A

2. Installing and Uninstalling the CLI

Linux

302

6. When prompted, choose whether or not to enable Secure Management for

OneCommand:

Do you want to enable Secure Management feature for OneCommand?

(s/u)

Enter 's' to select secure management. (LDAP/NIS OCM group

configuration required)

Enter 'u' to run without secure management (default).

Enter the letter 's' or 'u'.

Installing in Linux With an Existing OneCommand CLI Kit

Before installing the OneCommand Manager CLI, download the appropriate driver

from the Emulex website and install the driver. For example:

On OneConnect FCoE adapters:

For RHEL 5.5and later and SLES10 SP3 and later operating systems, use

Linux driver version 8.2.0.x.

For RHEL6 and later and SL11 SP1 and later operating systems, use Linux

driver version 8.3.5.x.

On OneConnect iSCSI adapters, use the iSCSI driver.

On OneConnect NIC adapters (including iSCSI-NIC and FCoE-NIC adapters),

use the Ethernet driver.

Note: The OneCommand Manager core kit cannot be installed if a previous version of

the HBAnyware utility is installed.

You have two options when installing the OneCommand Manager CLI on a Linux

system with an existing OneCommand CLI kit:

Updating an existing installation – preserve existing settings

Performing a clean install – overwrite existing settings

Updating (Preserving Existing Settings)

To update the OneCommand Manager CLI and preserve settings, you must install the

current core kit as detailed in “Installing in Linux Without an Existing OneCommand

CLI Kit” on page 300. The “.rpm” file handles the configuration file update. The install

script executes an rpm update (rpm -U *.rpm) to update the installed version of the core

kit to the current version.

Note: There is no update path from an HBAnyware 4.x or 3.x core kit to a

OneCommand Manager 5.1 or later core kit. You must un-install previous

versions of the HBAnyware utility before installing a OneCommand Manager

core kit. For information on uninstalling older versions of HBAnyware, see

“Uninstalling Older HBAnyware Kits in Linux” on page 303.

Advertising