Motorola Sl4000 Manual

  



  1. Motorola Sl4000 Manual Software
  2. Motorola Sl4000 Manual Model

Oracle's SL4000 library is the successor to the SL3000 library. It is physically similar to the SL3000 and retains many of the same features. The SL4000 offers the following benefits:

MOTOTRBO™ SL4000 Series UHF digital hand portable two way radio with built-in Bluetooth and integrated Option Board. Motorola have cancelled this model. It has been replaced by the SL4010e. Please enquire for further information regarding other MOTOTRBO alternatives. View and Download Motorola SL4010 user manual online. Professional digital two-way radio. SL4010 radio pdf manual download. Also for: Sl4000. Motorola computer programs contained in the Motorola products described in this manual may not be copied, reproduced, modified, reverse-engineered, or distributed in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication.

Full product guide for the Motorola SL4000 Keywords: Motorola SL4000 Manual Created Date: 4340Z. Copyrighted Motorola Solutions computer programs contained in the Motorola Solutions products described in this manual may not be copied, reproduced, modified, reverse-engineered, or distributed in any manner without the express written permission of Motorola Solutions. Furthermore, the purchase of Motorola Solutions products.

  • Higher storage capacity (from 200 to 9,017 storage cells)

  • Drive capacity from 1 to 120 tape drives (up to three DEMs)

  • Secure, authenticated library communications using HTTPS protocol

  • Support for dual AEMs to support bulk loading and redundant robotics

  • Support for a variety of mixed media and tape drives

  • Ability to partition an SL4000 at the storage cell and drive level

Caution:

You must audit an SL4000 after it is configured or reconfigured to ACSLS. You must also audit an SL4000 after increasing or changing the activated capacity of the library.

The library reports the potential cell locations that are not accessible to ACSLS when ACSLS audits it. Inaccessible cell locations include: locations where CAPs, drives, and operator panels are installed; cell locations that the robots cannot access; cell locations that are not activated; and locations that are not in this partition.

ACSLS Support

ACSLS provides support for the following SL4000 features:

  • ACSLS supports the new LSM type SL4000 which is visible in queries and displays. The SL4000 library is managed and operated as a single-LSM ACS.

  • ACSLS uses the same generic panel maps for both SL3000 and SL4000 libraries.

  • ACSLS can manage up to 16 partitions of a single SL4000 library.

  • The maximum number of CAPs in one LSM is increased to 15.

    • With AEMs, a maximum of 15 CAPs

    • With parking modules, a maximum of 14 CAPs

  • Ability to dedicate a CAP to a partition within the SL4000.

    Use the SL4000 GUI to dedicate CAPs to an SL4000 partition. The library reports both dedicated and shared CAPs to ACSLS. Only CAPs that are dedicated to a partition managed by ACSLS can be set to automatic mode.

  • The SL4000 does not currently provide a CAP Aliasing feature.

Before Configuring ACSLS for the SL4000

Before you configure ACSLS for the SL4000:

  • Verify that all SL4000 components are operational.

    ACSLS builds its library configuration from the information reported by the library. If SL4000 components are not operational, the library information may not be reported to ACSLS, and the ACSLS configuration of the SL4000 could be incomplete.

  • Verify that required library configuration is complete.

    ACSLS will require a known user name and password that have been defined on the SL4000 library. Any partitioning should also be performed, and if ACSLS will be managing a partition then it must not be a SCSI partition. The partition number will be required during library configuration.

To verify that all of the components of the SL4000 are operational, or to complete any required library set-up, log in to the SL4000 Web-based GUI. Refer to the SL4000 User's Guide for procedures.

Configuring the SL4000 to ACSLS

Once the SL4000 components are operational, use one of the following ACSLS utilities to configure the SL4000 to ACSLS:

  • acsss_config utility (see 'Using acsss_config to Configure Your Library Hardware')

  • Dynamic Configuration (config) utility (see 'Using the Dynamic Configuration (config) utility')

ACSLS uses the SCI interface (HTTPS communications, including authentication) to communicate with, and operate the SL4000 library.

Refer to the acsss_config and config utilities for details on how to specify connection parameters for various library types, including the SL4000.

Note:

  • Two or more ACSLS servers cannot be connected to an SL4000 library.

    Though ACSLS does not enforce any limits, connecting two or more servers to an SL4000 will result in database performance and cartridge management issues.

  • For proper functionality, ensure that the ACSLS server clock is in sync with the SL4000 internal clock, within a few minutes.

Changing the SL4000 User Name and Password

If the SL4000 user name or password changes or expires, you must use the acs_rewallet.sh utility to update ACSLS authentication. See 'acs_rewallet.sh' for more information.

SL4000 Modules

There are five types of modules in an SL4000 library, with a total of 15 modules allowed in a single library.

Note:

Refer to your SL4000 library publications for the latest updates to configuration and feature availability, as needed.
  • Base module, one, required

    This module consists of a single frame, which centralizes the infrastructure for all other modules in the library. One Base Module, and only one, is required for every library installation.

    On the front of this module is:

    • A single, 26 cartridge-dual magazine-cartridge access port (CAP).

    • A service door for library access.

    • A front panel with three LEDs: Library Active, Service Required, and Wait.

    • An optional feature for a touch screen operator panel or window.

  • Drive Expansion Module (DEM), maximum of three

    This module allows further expansion of tape drives and provides additional data cartridge capacity. A maximum of three Drive Expansion Modules can be added to the required Base Module, on any side of the base module.

  • Cartridge Expansion Module (CEM), maximum of twelve

    This module provides additional cartridge cell capacity and growth. It does not include tape drives. A maximum of twelve Cartridge Expansion Modules can be added, though the maximum number is dependent on the number of other module types present.

  • Parking Expansion Module (PEM), leftmost and the rightmost side modules

    These are the left-most and the right-most side modules. They are the same as the cartridge expansion module, with six columns of arrays (three on the front wall and three on the rear wall) that are inaccessible to allow the library to park a defective robot. In the left PEM, it is the three leftmost columns (front and back). In the right PEM, it is the three rightmost columns.

  • Access Expansion Module (AEM)

    See 'Using the AEM' for more information.

Note:

ManualAn SL4000 with dual robots has either AEMs or PEMs.

SL4000 Panel Types

ACSLS uses the same panel types for both SL3000 and SL4000 libraries. Instead of having specific panel definitions that define each possible cell location, the SL4000 uses generic panel definitions.

The three generic panel types map to a variety of specific panel maps. They are:

  • Single SL4000 cell panel type

    To determine which cells are present in this library and which cells are part of the activated capacity and are assigned to this partition, you must audit the library.

  • Drive panel type

    When you configure the library, ACSLS determines which drives are present. Before you configure the library, make sure all drives are powered on and ready.

  • Not installed

    This is a placeholder for the front and rear panels on modules that are not yet installed.

Understanding SL4000 Addressing

SL4000 library modules consist of walls, columns, and rows that house cartridges, tape drives, cartridge access ports, and robotic units.

Like the SL3000, the SL4000 uses internal addresses that are somewhat different than the traditional PRC (panel, row, column) addresses used in ACSLS to map physical locations in a library.

  • SL3000 and SL4000 addresses are one-based (not 0) and also use negative numbers.

  • Library addresses use five parameters: library, rail, column, side, and row.

As with other libraries (SL8500, SL150), ACSLS provides a mapping of physical locations into PRC addresses (acs, lsm, panel, row, column) for administrative and client usage. See 'SL4000 Addressing' for more information about the panel numbering used for an SL4000 library.

Refer to your SL4000 library publications for detailed information about physical configuration and addressing, and for any other procedures related to library operations.

SL4000 Addressing

An SL4000 can be expanded without changing any of the ACSLS addresses for drives and storage cells. Since ACSLS addresses map the largest possible SL4000 library, you can add modules without changing the addresses of existing cells, drives, and CAPs.

If modules are not installed, their panels are simply mapped as 'not installed'. If panels are installed, the addresses on these panels become available. In this way, when you install a new module, addresses of the panels on existing modules do not change.

Motorola

The following figure shows SL4000 potential module and panel numbers:

Figure F-1 SL4000 Addressing


Description of 'Figure F-1 SL4000 Addressing'

The smallest SL4000 configuration is a single Base Drive Module (BDM). In a single BDM configuration, panels 30 and 31 are installed, and all other potential panel locations are not installed. When you add a Drive Expansion Module (DEM) on the left, panels 28 and 29 are also installed. If you add a Cartridge Expansion Module (CEM) to the right of the BDM, panels 32 and 33 are now installed.

The addresses of the cells and drives on the BDM never change. This ensures that as you increase your SL4000 capacity, existing ACSLS addresses for drives and storage cells do not change. The library can expand to both the right and left of the BDM, with a maximum of 15 modules.

CAP Numbering

The SL4000 supports up to 15 Cartridge Access Ports (CAPs). There can be a CAP on each SL4000 panel. CAPs are numbered, as follows:

  • CAPs 1-14 - in the CEMs or DEMs to the left of the base module

  • CAP 15 - in the base module (the only required CAP)

  • CAPs 16-29 - in the CEMs or DEMs to the right of the base module

Just as panel numbers are added counting either down or up from the base module, CAP numbers are added counting either up or down from CAP 15 in the base module. When a CAP is installed in a module, the CAP number will match the module number, remembering that the base module (BDM) is always module 15.

Caution:

Each ACS must have at least one CAP. This can be either dedicated or shared. Because all of the CAPs in an SL4000 can be dedicated to other partitions, this is a critical restriction when configuring SL4000 partitions.

Varying the SL4000 Offline

Vary SL4000 components offline to ACSLS before they are powered off, if they are inoperative, and before you open an SL4000 access door. This notifies ACSLS that they are unavailable. Once they are available, vary them back online.

Use ACSLS to Vary SL4000 Components Offline, not SL4000 GUI

Be sure to vary SL4000 components (ACSs, LSMs, and CAPs) offline to ACSLS, not the SL4000 GUI. ACSLS allows outstanding requests to complete before taking components offline, unless it is a vary offline force.

The SL4000 GUI has no knowledge of outstanding requests to ACSLS. Varying components offline using the SL4000 GUI may cause requests in progress to fail.

When to Vary SL4000 Components Offline to ACSLS

This section describes when to vary components offline to ACSLS.

Before Opening the Access Door

Before opening the SL4000 access door, issue the following command to vary the ACS offline:

Note:

If any CAPs in the SL4000 are in automatic mode, you must:
  1. Set the CAPs to manual mode before opening the access door.

  2. Set the CAPs back to automatic mode after you close the access door and the SL4000 comes back online.

If a CAP is Inoperative

If a CAP is inoperative, issue the following command to vary it offline:

Using the Dynamic Configuration (config) utility

The dynamic configuration (config) utility allows you to implement configuration changes to ACSLS libraries (and components) while ACSLS remains online and running. These configuration changes are recorded in the acsss_config.log file.

The following dynamic configuration utilities are supported:

  • config acs

  • config drives

  • config lsm

  • config ports

Using the config utility provides the following benefits:

  • ACSLS can continue running, allowing you to perform mount requests to unaffected library components.

  • Allows you to reconfigure specified library components while all other configuration information remains unchanged. For example:

    • When you specify an ACS, the configurations of other ACSs are not affected.

    • When you specify an LSM, the configurations of other LSMs are not affected.

    • When you specify a drive panel (the drives on a panel), mounts and dismounts to all existing drives are not affected.

Note:

Dynamic configuration can be used to configure a new ACS, or re-configure an existing ACS. You cannot use dynamic configuration to delete an SL4000 ACS.

Moving Cartridges Before Removing Cells from a Partition

The SL4000 can partition down to the drive and cell level. If cells are reassigned from one partition to a different partition, cartridges in those cells will be orphaned, and they will no longer be accessible by the partition that they were in before.

To avoid this, before re-partitioning an SL4000, move cartridges to cells that will remain in your partition.

Finding Missing SL4000 Cartridges

If a cartridge is out of place or unaccounted for by ACSLS:

  1. Perform a physical audit of the SL4000 using the SL4000 GUI.

    The physical audit of the SL4000 is performed as a background task in between handling mount and other library operation requests.

    Caution:

    If the SL4000 contents are out of sync with ACSLS due to manual operations such as loading cartridges directly, it is not advisable to attempt continued operations.
  2. Run an ACSLS audit to update the ACSLS database to match the actual inventory of library cartridges.

Auditing New Cartridge Addresses

After an expansion has occurred, complete the following procedure:

  1. Vary the ACS and ports offline.

  2. Do one of the following:

    • Add or remove a module(s).

    • Change capacity.

    • Re-partition the library.

  3. Vary the ACS and ports online.

  4. Update the configuration in the ACSLS database using one of the following procedures:

    • Dynamic:

      • config acsacs_id or config lsm lsm_id

      • Audit the library.

    • Static:

      • Bring down ACSLS: acsss disable

      • Update the ACSLS configuration: acsss_config

      • Bring up ACSLS: acsss enable

      • Audit the library.

Unknown Cell Information Reported When Auditing the SL4000 Library

In some scenarios, while the SL4000 is auditing, cell information may be reported to ACSLS as UNKNOWN. This can cause issues when ACSLS is mounting, dismounting or auditing an SL4000 library.

One known scenario is after a SL4000 library door has been opened and closed. The SL4000 will become operational, as well as the ACSLS LSM for that ACS connected to the SL4000 library. However, the library itself may still be auditing after becoming operational and will report cell information to ACSLS as UNKNOWN. This may cause mount and dismount requests to fail. If this occurs, wait for the SL4000 to stop auditing and then re-attempt the operation again.

Service

Bulk Operations with the AEM

This section describes bulk operations with the Access Expansion Module (AEM).

The AEM is essentially a very large CAP that has all of the characteristics of a CAP, such as online/offline states and the ability to be shared by partitions.

Sl4000

The AEM allows you to perform bulk loads or unloads of up to 234 cartridges at a time, to or from the library. It also allows for the non-disruptive maintenance of a library TallBot.

For more information about the AEM, see 'Using the AEM'.

Bulk Enters

Bulk enters on an AEM enable to you to enter up to 234 cartridges at a single time. You must start a normal enter specifying the AEM cap_id. This can either be a manual enter or you can set the AEM to automatic enter mode.

In a partitioned library, you can only set a CAP to automatic enter mode if the CAP is dedicated to your partition. Dedicating an AEM to only your partition makes it unavailable to other partitions. Consider other SL4000 users before doing this.

Bulk Ejects

When ejecting more than 42 volumes to the AEM, the preferred tool for larger ejects is lib_cmd or ejecting.sh. Any other user interface, including cmd_proc, xeject, or an ACSAPI eject will limit the eject load to 42 cartridges at a time.

See 'Using lib_cmd' and 'ejecting.sh'.

Caution:

When performing a bulk eject using the AEM, ensure all CAP magazines are present. The eject fails if there are missing CAP magazines at locations where ACSLS is attempting to eject cartridges.

The AEM should not to be used for entering or ejecting small numbers of cartridges. It should only be used for bulk enters and ejects.

Using the AEM for small enters and ejects is much slower since the service safety door must be lowered when the AEM is accessed to enter or remove volumes, and raised when access to the AEM is completed. For smaller numbers of cartridges, use rotational CAPs.

Motorola Sl4000 Manual Software

Since the AEM should not be used for small enters and ejects, the maximum CAP priority is 1. This aids in preventing the AEM from being selected when the CAP ID is wild-carded with an asterisk on an audit, enter, or eject.

Aliasing SL4000 CAP IDs

The SL4000 does not currently provide a CAP Aliasing feature.

SL4000 OCSI Retention Time

The OSCI retention time determines how long the SL4000 library retains events on the OSCI channel if ACSLS and the SL4000 become disconnected due to network outages or other network related issues.

The OSCI retention time is set to two hours and is configured by ACSLS when creating the OSCI destination channel on the library. This is an internally configured time and is not configured by the installer or other ACSLS UI.

If ACSLS and SL4000 connectivity is lost for longer than the two hour retention time, OSCI events may be lost. In most cases, no further action is required once connectivity is restored. However, if CAP enter or eject operations were occurring at the time of connectivity loss and the OSCI retention time has elapsed, it may be necessary to stop and restart ACSLS to re-sync ACSLS with the library.

ACSLS Support for Library Upgrade of SL3000 to SL4000

A field upgrade option is available to convert an SL3000 library into an SL4000 library. Although only ACSLS 8.5 can support the SL4000, either ACSLS 8.4 or ACSLS 8.5 may be managing the SL3000.

If ACSLS 8.4 (or a patch to 8.4) is currently managing the SL3000, use either of the following options:

  • You can perform the library upgrade during the upgrade from ACSLS 8.4.0 to 8.5.0.

  • You can perform the library upgrade after first importing the SL3000 into ACSLS 8.5.0

With either option, you remove the SL3000 library from the current configuration (by running acsss_config), and then add the SL4000 library to the ACSLS 8.5.0 configuration. After the library upgrade is complete, use either acsss_config or config acs new to add the SL4000 library. Once you run an audit against the SL4000, the library is ready for operation.

  • If you plan to bring an upgraded SL4000 directly into ACSLS 8.5, remove the SL3000 library from the ACSLS 8.4 configuration before exporting the database for the upgrade to the 8.5 release. The library upgrade can be performed at the same time as the ACSLS upgrade.

  • If ACSLS 8.5 is already managing the SL3000 prior to the library upgrade, shut down ACSLS and run acsss_config to drop the SL3000. The library upgrade can be performed at that time. No database export or import is needed.

Motorola Sl4000 Manual Model

Important Considerations

  • Drives and media supported by the SL4000 are not the same as those supported in the SL3000. Any affected drives or media should be physically removed from the SL3000 as part of the library upgrade.

  • Once the library is ready and operational, perform all required library setup to create a user and password, certificates, etc. You will need this authentication information to configure the library to ACSLS.

  • You must always run an ACSLS audit against a new library before starting client operations.

What About my Volume Information?

By default, ACSLS retains volume records for 5 days after a volume is ejected or is marked absent (no longer in the library). This allows us to preserve information such as use count, last access date, or ownership.

Be sure to retain absent/ejected volumes for some non-zero period (dv_config -p ABSENT_VOLUME_RETENTION_PERIOD). A value of zero indicates to delete those records immediately.

After the SL3000 library is removed, the volumes are considered absent. When audit is run against the SL4000, the volume records are re-activated with new home locations.

What About my Logical Libraries?

There is no provision for exporting a logical configuration, and the physical drive identifiers associated with any logical library backed by the SL3000 will change (panel numbers will be different). Therefore, the logical configuration must be re-defined after the SL4000 has been added to the ACSLS 8.5 physical configuration.

You can use the lib_cmd display command to create a record of the existing logical configuration (libraries, drives, volumes and mappings) for reference.

What About my Client Applications?

Because the drive identifiers will change between the SL3000 and SL4000, along with CAP identifiers, client applications may need to refresh their view of the library configuration and then re-inventory the library. This is especially true for ACSAPI clients, which use ACSLS drive identifiers directly. However, even FC (logical) clients must refresh their views, since the element addresses for their resources may have changed.There should be no impact to XAPI clients, as library configuration is re-discovered at startup.

Using watch_vol

You can use the watch_vol utility, along with the vol_attr.dat file, to automatically assign various attributes when a volume is entered, discovered, or re-activated. This may be helpful in automating some of the media management tasks, including assignment of volume owner, logical library, etc.