8 Configuring Host Applications

See Also

Changing the Host Interface Type of a Non-Partitioned Library

Note:

For a partitioned library, see "Changing the Partition Interface Type".
  1. Select Tools > Select Active Cells.

  2. Click the Select Active Cells tab.

  3. Select the interface type.

  4. Click Apply, and then Yes to update the library controller database.

    The new interface type is active immediately. You do not need to start the library.

Updating Hosts After Modifying Capacity

Updating ACSLS and ELS After Modifying Capacity

Initiate an audit through ACSLS and ELS to update the host database (see the host software documentation).

Effect on HLI Hosts After Modifying Capacity

After modifying the capacity configuration, the library controller sends an asynchronous message to all hosts notifying them that the library configuration has changed.

After adding active storage slots, the library stays online. Host jobs and connectivity are not affected.

After deactivating a storage slot or removing an empty drive slot, the library goes offline temporarily. The library comes back online after updating the library controller database.

Updating SCSI Hosts After Modifying Capacity

Issue commands to update the host configuration information (see the host software documentation).

Effect on FC-SCSI Hosts After Modifying Capacity

After activating or deactivating resources or modifying a host LUN connection, the library goes offline temporarily with a "Unit Attention" condition.

After activating or deactivating drives, the library updates the SCSI element numbering (see "Default SCSI Storage Element (Cartridges) Numbering Scheme").

Updating Hosts After Modifying Partitioning

Updating ACSLS or ELS After Modifying Partitioning

  • After creating an HLI partition, configure the host connection through ACSLS or ELS (see the host software documentation). An HLI partition can have up to 16 assigned hosts.

  • After modifying the partitioning configuration, initiate an audit through ACSLS and ELS to update the host database.

Effect on Hosts of Modifying an HLI Partition

For HLI hosts, the partition remains online when you allocate resources to the partition. However, the partition will go offline temporarily when you remove resources from the partition. The affected partition automatically comes back online and the library notifies all hosts connected to the partition of the configuration change. Neighboring partitions are not disturbed.

After allocating or removing resources, hosts experience a brief interruption as library configuration information is updated. The host automatically continues to process jobs.

Updating SCSI Hosts After Modifying Partitioning

  • After creating an FC-SCSI partition, configure the host-partition connection in SLC (see "Changing FC-SCSI Host Connection Information").

    An FC-SCSI partition can have more than one host-partition connection. The connection information consists of the world wide port name of the FC-SCSI host bus adapter and the logical unit number (LUN) of the host.

  • After modifying the partitioning configuration, issue commands to update the host configuration information (see the host software documentation).

Effect on Hosts of Modifying an FC-SCSI Partition

After adding or deleting a host-partition connection or changing the LUN, the affected partition goes offline with a "LUNS Data Has Changed Unit Attention" condition. If a host has unique ITL nexus connection mappings for each partition connection, then only the partition experiencing the connection change is affected.

After allocating or removing a resource, the affected partition goes offline with a condition of "Mode Parameters Have Changed Unit Attention". Neighboring partitions are not disturbed.

Updating Hosts After Modifying the MV Pool

Updating ACSLS and ELS After Modifying the MV Pool

  • For ACSLS, you must initiate reconfiguration after modifying the MV pool. Use the config drives <panel_id> utility. For more information, see the ACSLS Administrator's Guide.

  • For ELS, no action is required after modifying the MV pool. ELS hosts automatically reconfigure. However, the reconfiguration can cause a disruption in mount/dismount requests when trying to set a lock on control data sets (see the host management documentation).

Effect on HLI Hosts of Modifying the MV Pool

After adding drives to the MV pool, the library (or affected partition) will go offline. The affected hosts receive "Configuration Changed", "LSM Ready", and then "Not Ready" messages from the library. ELS automatically removes drives moved to the MV pool from its configuration. ACSLS automatically updates drives moved to the MV pool to an offline state, but ACSLS requires you to initiate reconfiguration.

After removing drives from the MV pool, the library and partitions remain online. For a non-partitioned library, the drive slots are available to hosts immediately. ELS hosts begin reconfiguration, but ACSLS hosts require you to initiate reconfiguration. For a partitioned library, you must allocate the drive slot removed from the MV pool to a partition (see "Partitioning the Library").

Updating SCSI Hosts After Modifying the MV Pool

Initiate a reconfiguration to update the host configuration information (see the host software documentation).

Effect on SCSI Hosts of Modifying the MV Pool

After adding drives to the MV pool, the library (or affected partition) will go offline.The library renumbers element IDs and sends two Unit Attentions: "Not Ready to Ready Transition" and "Mode Parameters Changed". You should initiate a reconfiguration of the host.

When removing drives from the MV pool, the library and partitions remain online. The library logically assigns the drive the last element ID regardless of the drive's physical location. When the library comes back online, SCSI hosts receive two Unit Attentions: "Not Ready to Ready Transition" and "Mode Parameters Changed". You should initiate a reconfiguration. For a partitioned library, you must allocate the drive slot removed from the MV pool to a partition (see "Partitioning the Library").

Effect on SCSI Element IDs of Modifying the MV Pool

Modifying the MV pool can renumber the SCSI element IDs. If renumbering occurs, you may need to reconfigure the host.

When you add a drive to the MV pool, the library automatically re-assigns element IDs to all drives. The drive slot of the MV drive is treated as "empty" and the library does not assign it an element ID (see "Default SCSI Storage Element (Cartridges) Numbering Scheme").

When you remove a drive from the MV pool, the library logically assigns it the last element ID regardless of the drive's physical location.

To avoid renumbering, select the drive that is both physically and logically the last element ID (verify the drive is a T10000C or D).

Updating HLI Host Management Software for RE

For more information about RE, see "Redundant Electronics Overview".

ACSLS

ACSLS 7.3 or higher is required for RE and you may need to add port connections to the libraries. There are two methods:

  • Stop ACSLS. Run acsss_config, specifying the existing ACSs and port connections (with the ACSs in the same sequence) and add the new port connections. Start ACSLS.

  • Run the config ports utility while ACSLS is running, specifying the existing ports in the same sequence and adding new ports at the end. You cannot change or delete port connections with config ports.

ELS

Oracle highly recommends PTFs L1H15S0(VM)/L1H15S1(MVS) for 6.2 and L1H15S2 for 7.0.

Table 8-1 HSC/ELS PTF HLI Compatibility Level Support for FRS_4.00 and above

HSC/ELS Level Level 20 or Below Level 21 Level 22 Level 23 Minimum RE SupportFoot 1  Level 23 Enhanced RE SupportFoot 2  Level 23 Multi-RE SupportFoot 3 

6.1

Level 21 PTF

L1H14UU (VM)

L1H14UV (MVS)

Unsupported

Unsupported

Unsupported

Unsupported

6.2

Level 21 PTF

L1HA4UW (VM)

L1H14UX (MVS)

L1H15DH (VM)

L1H15DI (MVS)

L1H15H9 (VM)

L1H15HA (MVS)

L1H15MF (VM)

L1H15ME (MVS)

L1H168F (VM)

L1H168G (MVS)

7.0 (MVS)

Level 21 PTF

L1H14UY

L1H15DJ

L1H15HB

L1H15MH

L1H168H

7.1 (MVS)

Included

Included

Included

Included

Included

L1H168I


Footnote 1 Can connect to one SL3000 RE library in an ACS string. Only the connected library can be switched through HSC switch command.

Footnote 2 Can connect to one SL3000 RE library in an ACS string. All RE libraries can be switched through the HSC switch command. Supports 32 TCP/IP connections. Includes dual TCP/IP support, display of acs-id, auto CAP recovery, and support for 64 read in-transit cartridges during cartridge recovery.

Footnote 3 Can connect to multiple SL3000 RE libraries in an ACS string. Includes same functionality as the enhanced RE support.

Configuring Dual TCP/IP

Note:

Before configuring dual TCP/IP, gather information regarding the network, routing, and IP addresses from the administrator or use the appropriate network ip command.

Configuring the Library for Dual TCP/IP

Use the route command to manage the routing tables. Define routes for the 2A and 2B ports to the hosts.

  1. Using the CLI, take both ports offline:

    SL3000> network ip link set dev 2A down
    SL3000> network ip link set dev 2B down
    
  2. Add the new IP addresses and subnet masks for both ports:

    SL3000> network ip address add IP_address/netmask dev 2A
    SL3000> network ip address add IP_address/netmask dev 2B
    
  3. To make the change active, bring both ports online:

    SL3000> network ip link set dev 2A up
    SL3000> network ip link set dev 2B up
    
  4. Enter the network routing configuration for each port:

    • For multiple hosts, add the IP address and netmask for each host:

      SL3000> network ip route add IP_address/netmask dev 2A
      SL3000> network ip route add IP_address/netmask dev 2B
      
    • For a single host, no netmask value is required:

      SL3000> network ip policy route add host_IP_address dev 2A
      SL3000> network ip policy route add host_IP_address via gateway_IP_address dev 2A
      SL3000> network ip policy enable 2A |2B
      SL3000> network ip policy status
      
  5. Verify the configuration.

    SL3000> network ip address show
    SL3000> network ip route show
    SL3000> network ip policy route show dev 2A |2B
    
  6. Check the date and time for accuracy.

    SL3000> time
    time print
    time HH: MM
    time HH:MM:SS
    
  7. Test the configuration to ensure you can access the library through both ports.

Configuring an ACSLS Host for Dual TCP/IP

For the ACSLS server, you should use the acsss_config command or the Dynamic Configuration config utility to configure two network interfaces on two separate subnets. Use the route command to define the two routes on the ACSLS server. A second physical connection improves reliability.

  1. Update the routing tables of the ACSLS server by following the ACSLS documentation. If there is a single network interface on the ACSLS server, no special routing is required on the host.

  2. Using the UNIX command prompt at the ACSLS server, use the Dynamic Config command to add a port connection to the SL3000.

    1. Ensure the ACS is in online or diagnostic mode to ACSLS.

    2. Use config port acs_id to add a port.

    3. If not already online, bring the ACS online to ACSLS.

  3. To remove or replace an existing IP address with a different port:

    1. Shut down ACSLS by issuing kill.acsss (for 7.3 and below) or acsss disable (for 8.0 and above).

    2. Configure the new ports by issuing acsss_config.

    3. Bring ACSLS back online by issuing rc.acsss (for 7.3 and below) or acsss enable (for 8.0 and above)

For more information, see the ACSLS Administrator's Guide.

Configure an ELS Host for Dual TCP/IP

  1. Update the routing tables of the IBM mainframe by following the ELS documentation. If there is a single network interface on the IBM mainframe, no special routing is required on the host.

  2. At the IBM mainframe console or PARMLIB, use the LMUPATH control statement to define network LMU attachments.

  3. Specify a second LMUADDR parameter to define the dual TCP/IPs. ELS automatically determines whether the connection is dual TCP/IP or dual LMU.

  4. Take the ACS offline, issue the LMUPDEF command, and bring the ACS back online to pick up the revised LMUPATH statement that includes the second connection.

For more information, see the ELS documentation.