Características de los fertilizantes a utilizar

This section provides instructions for configuring Sun Solaris in an Enterprise Backup Solution (EBS) environment. The configuration process involves:

• Upgrading essential EBS hardware components to meet the minimum firmware and device driver requirements

• Installing the minimum patch/service pack level support for: • Sun Solaris

• backup software

Refer to the following web sites to obtain the necessary patches:

• For HP: http://www.hp.com/support

• For Sun: http://www.sun.com

NOTE: Refer to the EBS Compatibility Matrix for all current and required hardware, software, firmware, and device driver versions at:http://www.hp.com/go/ebs.

See ”Installation checklist” on page 103 to ensure that the hardware and software in the SAN is correctly installed and configured.

Configuring the SAN

This procedural overview provides the necessary steps to configure a Sun Solaris host into an EBS. Refer to the documentation provided with each Storage Area Network (SAN) component for additional component setup and configuration information.

Currently supported adapters for Sun Solaris include:

• SWSA4-SB uses the package CPQfca and configuration file fca.conf

• SWSA4-SC uses CPQfcaw and configuration file fcaw.conf

• SWSA4-PC uses CPQfcaPCI and configuration file fca-pci.conf

• FCA2257P uses the package QLA2300 and the configuration file qla2300.conf

• JNI FCE6460, FCX-6562 and FCX2-6562 use the package JNIC146x and the configuration file jnic146x.conf

• Sun SG-XPCI1FC-QF2 (X6767A) and SG-XPCI2FC-QF2 (X6768A) use the Sun SAN Foundation software packages and the cfgadm configuration utility

• Sun SG-XPCI1FC-JF2 and SG-XPCI2FC-JF2 use the package SUNWjfca and SUNWjfcax and the configuration file jfca.conf

• Emulex LP9002L/LP10000/LP10000DC use the package lpfc and the configuration file lpfc.conf

SWSA4 adapter configuration

IMPORTANT: This guide uses SWSA4-SC as the example for all SWSA4 adapters. Substitute your device name, driver package, and configuration file appropriately.

1. Prepare the required rack mounted hardware and cabling in accordance with the specifications listed in backup software user guide as well as the installation and support documentation for each

component in the SAN.

NOTE: To complete this installation, log in as root.

2. After installing the HBA, install the device driver. The driver comes with the HBA or can be obtained from http://www.hp.com/support.

3. To ensure that no previous device driver was installed, at the prompt, type: #pkginfo | grep CPQfcaw

If no driver is loaded, a prompt is returned. If there is a driver installed, verify that it is the correct revision. If not, enter the following to remove the driver:

#pkgrm <package name>

4. Install the new driver. Navigate to the directory where the driver package is located and at the prompt, type:

#pkgadd -d ./CPQfcaw

5. Make sure that the driver is installed. At the prompt, type: #pkginfo -l CPQfcaw

6. Look at the device configuration file to make sure the configuration is appropriate. There are two lines needed for this configuration. Check these lines with the following:

#egrep “fca_nport =|def_wwpn_binding “ /kernel/drv/fcaw.conf The output should be:

fca_nport = 1;

def_wwpn_binding = “$0000000000000000”

NOTE: The numbers that def_wwpn_binding = are not important. As long as there is a '$' followed by any 16 digits the device is configured properly. If these are not set properly, edit them as needed.

FCA2257P adapter configuration

Substitute for your device name appropriately.

1. Prepare the required rack mounted hardware and cabling in accordance with the specifications listed in backup software user guide as well as the installation and support documentation for each

component in the SAN.

2. After installing the HBA, verify proper hardware installation. At the OpenBoot PROM ok prompt, type: show-devs

If the HBA is installed correctly, an entry similar to the following is displayed (the path will very slightly depending on your configuration):

/pci@1f,4000/QLGC,qla@5

Verify the HBA hardware installation in Solaris at the shell prompt by typing: prtconf -v | grep QLGC

If the HBA is installed correctly and the driver has not yet been installed you will see a device similar to the following:

QLGC,qla (driver not attached)

NOTE: To complete this installation, log in as root.

3. After installing the HBA, install the device driver. The driver comes with the HBA or can be obtained from http://www.qlogic.com/support/drivers_software.asp. Refer to the section, “OEM and ISV

approved/recommended drivers and firmware.”

4. To ensure that no previous device driver was installed, at the prompt, type: #pkginfo | grep QLA2300

This will list the specific driver package installed, such as QLA2300-3, if any. If no driver is installed, a prompt is returned. If there is a driver installed, verify that it is the correct revision by entering:

#pkginfo -l QLA2300-3

If you need to remove the driver, enter: #pkgrm <package name>

5. Install the new driver. Navigate to the directory where the driver package is located and at the prompt, type:

6. Make sure that the driver is installed. At the prompt, type: #pkginfo -l QLA2300-3

7. Look at the device configuration file to make sure the configuration is appropriate. Fibre Channel tape support should be enabled. An example follows:

hba0-fc-tape=1;

Persistent binding can be configured by binding SCSI target IDs to the Fibre Channel world wide port name of the router. To setup persistent binding the persistent binding only option should be enabled. An example follows.

hba0-persistent-binding-configuration=1;

After enabling persistent binding only, router world wide port names (wwpn) should be bound to SCSI target IDs. For example, if a router has a wwpn of 1111222233334444 and is visible to hba0, bind it to SCSI target ID 64 as follows:

hba0-SCSI-target-id-64-fibre-channel-port-name = “1111222233334444”;

NOTE: Persistent binding for the FCA2257P HBA used to be defined in the st.conf configuration file. It is now defined in the qla2300.conf configuration file as shown above.

JNI FCE6460, FCX-6562 and FCX2-6562 adapter configuration

Substitute for your device name appropriately.

1. Prepare the required rack mounted hardware and cabling in accordance with the specifications listed in backup software user guide as well as the installation and support documentation for each

component in the SAN.

NOTE: To complete this installation, you must log in as root.

2. After installing the HBA, verify proper hardware installation. At the OpenBoot PROM ok prompt, type: show-devs

If the HBA is installed correctly you will see a device similar to the following (the path will vary slightly depending on your configuration):

/pci@18,700000/JNI,FCR@1

Verify the HBA hardware installation in Solaris at the shell prompt by typing: prtconf -v | grep JNI

If the HBA is installed correctly and the driver has not yet been installed you will see a device similar to the following:

JNI, FCR (driver not attached)

3. Install the HBA device driver. The driver for the HBA can be obtained from http://www.jni.com/OEM. Be sure to download the Solaris driver for HP.

4. To ensure that no previous device driver was installed, at the prompt, type: #pkginfo -l JNIC146x

If no driver is loaded, a prompt is returned. If there is a driver installed, verify that it is the correct revision. If you need to remove the driver, enter:

#pkgrm <package name>

5. Install the new driver. Navigate to the directory where the driver package is located and at the prompt, type:

#pkgadd -d ./JNIC146x.pkg Select the JNIC146x package.

6. Make sure that the driver is installed. At the prompt, type: #pkginfo -l JNIC146x

7. Verify the HBA driver attached by typing: prtconf -v | grep JNI

If the driver is attached you will see a device similar to the following: JNI, FCR, instance #0

NOTE: In the following examples, the information is provided for HBA instance 1. Your HBA may be of a different instance.

8. Look at the device configuration file to make sure the configuration is appropriate. To set the HBA in fabric mode make sure the following entries are in the file:

jnic146x1-FcLoopEnabled = 0; jnic146x1-FcFabricEnabled = 1;

9. Static (persistent) binding can be configured in the device configuration file by binding SCSI target IDs and LUNs to the Fibre Channel world wide port name (wwpn) of the router. An example follows:

jnic146x1-automap = 0;

NOTE: “automap = 0" means no target/LUN instance will be initialized by any jnic146x instance unless the targetX_hba or targetX_lunY_hba binding parameters are explicitly defined.

You also need to add the following in the “Configuration parameters for target to FC device mapping section”: jnic146x1-target64_lun0_hba=”jnic146x1”; jnic146x1-target64_lun1_hba=”jnic146x1”; jnic146x1-target64_lun2_hba=”jnic146x1”; jnic146x1-target64_lun3_hba=”jnic146x1”; jnic146x1-target64_wwpn=”100000e0022286bf”;

where “100000e0022286bf” is the wwpn of the router Fibre Channel port. In addition, JNI recommends the following settings:

NOTE: In the following examples, the information is provided for HBA instance 1. Your HBA may be of a different instance.

Some parameters may not currently exist in the jnic146x.conf configuration file and may need to be added.