| StorageTek Tape Analytics Installation and Configuration Guide Release 2.0.1 E41585-03 |
|
 Previous |
 Next |
| StorageTek Tape Analytics Installation and Configuration Guide Release 2.0.1 E41585-03 |
|
Previous |
Next |
This chapter describes the concepts behind configuring libraries to send proper data to STA. Read this chapter before initiating the related configuration tasks in Chapter 4.
The SL500, SL3000, and SL8500 libraries have a command line interface (CLI) and a graphical user interface, StorageTek Library Console (SL Console, standalone or web-based). The SL150 library exclusively uses a browser-based user interface.
For most CLI commands, the syntax is the same across the SL500, SL3000, and SL8500 library models. For the few commands where the syntax varies by library model, examples are provided. Most CLI examples use an SL500 library. If you are configuring an SL3000 or SL8500 library, the details returned by each command may vary slightly from what is shown.
CLI Usage Tips
Use a terminal emulator, such as PuTTY, to establish an SSH (secure shell) connection to the library CLI.
Enable logging so you can review your activity should you need to troubleshoot errors.
SL500 library commands are case-sensitive.
With some firmware versions, the CLI times out after six hours.
To display help for any CLI command, type help plus the command name (for example, help snmp).
Communication between the STA server and libraries is through the SNMP interface. The libraries send data to STA through SNMP traps, and STA retrieves library configuration data through SNMP "get" functions.
To establish communication between the STA server and the libraries, you perform configuration procedures on the libraries (as described in Chapter 4) and STA server (as described in Chapter 5).
For additional information about SNMP implementation on the libraries, see the StorageTek Modular Libraries SNMP Reference Guide.
|
Note: On a periodic basis, the MySQL Event Scheduler will purge processed SNMP records from the database to minimize database growth. |
SNMP v3 is the recommended protocol for SNMP communications between STA and the libraries, and is also required for configuring media validationFoot 1 within STA. Depending on your site requirements, however, you may choose to use v2c. Chapter 4 describes the recommended v3 configuration. See Appendix B, "Configuring SNMP v2c Mode," for information on configuring the v2c protocol.
|
Note: While STA uses the recommended SNMP v3 protocol to communicate with the library, the initial handshake between the library and STA server is through the v2c protocol. |
The authentication, encryption, and message integrity features in SNMP v3 provide a secure mechanism for sending library data. To set up SNMP v3 communication on each library, you define the library as a v3 user and the STA server as a v3 trap recipient. In addition, you must specify authorization and privacy mechanisms and passwords. For STA, the authorization method is always SHA (Secure Hash Algorithm), and the privacy method is always DES (Data Encryption Standard).
STA supports only one SNMP v3 user. The same v3 user must be defined on all libraries monitored by a single STA server. Your libraries may already have one or more v3 users, and you can use one of these for STA communication. However, it is highly recommended that you set up a new, unique v3 user for this purpose.
The SNMP v3 protocol requires each SNMP device to have a globally unique engine ID. Therefore, the STA server and the libraries each have their own unique engine IDs. In the case of SL8500 library complexes, each library in the complex also has its own SNMP agent, and therefore its own unique engine ID. The engine ID contains a maximum of 31 hexadecimal characters.
Traps use the sender's engine ID; therefore, you must specify the library engine ID when you define STA as the SNMP v3 trap recipient.
In the STA data store, media history is retained by volume serial number (volser). Because all history for a particular piece of media is tied to its volser, Oracle recommends that you avoid duplicate volsers. Volsers should be unique across all monitored libraries. Duplicate volsers will result in co-mingling of data for different pieces of media.
For more information on duplicate volsers, see the StorageTek Tape Analytics Data Reference Guide.
An SL3000 or SL8500 library can have one, two, or four IP addresses, depending on which features are activated. However, STA is capable of maintaining uninterrupted connections with up to two library IP addresses at a time. Therefore, on a given library, you can configure STA to support either Dual TCP/IP or Redundant Electronics (but not both). You must always specify a primary library IP address, but you can optionally specify a secondary IP address.
If STA is configured to support Dual TCP/IP, it will maintain a connection with the library in the event of a port failover. If STA is configured to support Redundant Electronics, it will maintain a connection with the library in the event of a controller card switch. After a Redundant Electronics switch completes, you must perform a connection test and data collection to verify the library connection and retrieve current library configuration data (see ”SNMP Management Tasks” in the STA Administration Guide). See the library User's Guide for more information about these features.
|
Note: For libraries with both features, Oracle recommends that you configure STA to support Redundant Electronics, as this feature is more critical to maintaining continuous library operations. |
Table 3-1 summarizes the recommended library IP addresses to use when configuring the STA connection to the library.
Table 3-1 Recommended Library IP Addresses for STA Connection
| Activated Features | Primary Library IP | Secondary Library IP |
|---|---|---|
|
Neither |
2B port |
NA |
|
Dual TCP/IP only |
2B port |
2A port, active card |
|
Redundant Electronics only |
active card 2B port |
standby card 2B port |
|
Both |
active card 2B port |
standby card 2B port |
Additional Configuration Considerations
To configure STA to support Dual TCP/IP on an SL3000 or SL8500 library, you may need to use policy routing. For more information, consult the SL3000 or SL8500 Host Connectivity Guide. If you need assistance with Dual TCP/IP configuration, contact Oracle Support.
If a library has both Redundant Electronics and Dual TCP/IP, the STA server's subnet must be different from the subnet of the library port not configured for STA (STA GUI, ”Define Library Connection Details” screen). Otherwise, the library may try to send information through those ports (unknown to STA) and it will be rejected by STA.
Make sure your default gateway is the 2B interface.
LTO drives that support the Automation/Drive Interface (ADI) allow STA to provide high quality data (for example, drive performance and utilization), depending on configuration and firmware level. Drives that do not support ADI only provide basic data. ADI must be enabled on both the library and LTO drives. See the STA Requirements Guide for more information.
Footnote Legend
Footnote 1: Supported libraries only. See STA Requirements Guide.
|
 Copyright © 2012, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|