| Oracle Virtual Operator Panel User's Guide Release 2.1 E48640-01 |
|
 Previous |
 Next |
This chapter describes VOP pre-installation requirements.
VOP is available in two versions, designed for the following customer roles:
System Administrator
This version of VOP is designed for the system administrator who configures and controls the VOP configuration.
Operator
This version of VOP is designed for the operator who monitors the configuration. In this version, the operator can only manipulate a single tape drive at one time.
Each of these versions can be run in either standalone or client/server mode.
This section describes MD-VOP system requirements.
The VOP client requires the following:
VOP is supported on the following operating systems:
Linux Kernel (2.6.18 or later), Redhat 9.0, ES
Solaris 10/Solaris 11 (Sparc and x86)
Microsoft Windows XP (with Service Pack 3), Windows 7, or Windows 8
The VOP package includes separate installers for each of these operating systems.
The following are required:
2 GHz processor
Disk Space: Approximately 40 GB
Memory: 4 GB
Monitor screen resolution 1024x768 (minimum)
Available Ethernet port for static IP addressing
RJ45-RJ45 Ethernet cross-over cables (direct connection to a tape drive or drive tray)
RJ45-RJ45 Ethernet cables (connection through an Ethernet switch)
This section describes MD-VOP library and drive support.
MD-VOP supports multiple tape drives at the library level.
The following table lists libraries supported by MD-VOP, along with required minimum firmware levels:
The following table lists tape drives supported by MD-VOP, along with required minimum firmware levels:
Table 3-2 MD-VOP Tape Drive Support
| Tape Drive | Minimum Firmware Requirement |
|---|---|
|
T10000A |
1.44.111 |
|
T10000B |
1.44.211 |
|
T10000C |
1.51.316 |
|
T10000D |
TBD |
|
T9840D |
1.45.703 |
|
HP LTO4* |
H58S (Fibre Channel)B57S (SCSI) |
|
IBM LTO4* |
94D7 |
|
HP LTO 5* |
I5BS |
|
IBM LTO 5* |
BBNH/2.36.23 |
|
HP LTO 6* |
TBD |
|
IBM LTO 6* |
TBD |
|
VSM 4/5 |
TBD |
* LTO encryption-capable tape drives only
You can manually add tape drives to the MD-VOP configuration in order to provide placeholders as an indication that there is a tape drive in a particular slot.
The following table lists supported placeholder tape drives, along with required minimum firmware levels:
|
Note: 9XXX drives are non-reactive. You can obtain logs for these drives, however, they do not show loaded/unloaded state. |
MD-VOP allows the user to create a service request in My Oracle Support (MOS) and automatically transmit logs for Oracle Support review. The following devices are supported:
Oracle StorageTek SL8500, SL3000, SL500, and SL150 libraries
Oracle StorageTek T9x40 and T10000 series tape drives
VSM 4/5
This feature requires a valid service contract. Also, devices must be activated in MOS for processing. See "ASR" for more information about this feature.
The following table lists tape drives supported by T10000 9840D VOP, along with required minimum firmware levels:
The following table lists tape drives supported by LTO VOP, along with required minimum firmware levels:
Review the following additional considerations:
To use VOP with a drive, you must have an Ethernet connection from your computer to the Ethernet port on the tape drive or drive tray rear panel.
For a direct connection to the drive, you must use a single crossover Ethernet cable.
For an indirect connection (through an Ethernet switch), you must use a straight Ethernet cable to connect your computer to the switch. The switch-to-drive cable should already be connected.
VOP is designed to operate on the service network configured as a private LAN. It uses the service network Ethernet port for communications. This port can also be used by other applications, such as:
Oracle Key Manager (OKM), formerly Key Management System (KMS), used for secure encryption of tape drives.
Oracle Service Delivery platform (SDP), used for delivery of fast and accurate service.
The private LAN recommendation ensures security from unauthorized access. Refer to the Oracle Key Manager Systems Assurance Guide for more information about the service network.
The following are additional considerations:
When configuring the tape drive network, adhere to the guidelines included in your tape drive publications. A qualified service representative should implement the tape drive network.
If MD-VOP is the only program installed, the following are recommended:
Connect the tape drive Ethernet port on a private network.
Use static IP addresses, not dynamic addresses.
Use Level 2 switches to isolate each library (highly recommended)
Ensure that the latest firmware is loaded on all tape drives.
The IP address for a new tape drive defaults to 10.0.0.1. When you configure the network and tape drives, be sure to configure one tape drive at a time as you add them to the network.
MD-VOP configuration requires a unique IP address to be assigned for each tape drive.
If the configuration environment includes SDP, contact your SDP service representative to assist in assigning IP addresses.
Though VOP and VOP server can coexist, it is recommended that you do not mix these modes in most situations. A limited number of connections to the tape drives is permitted.
When the VOP server is used, a VLAN is required between the tape drives, libraries, and the VSM. The VLAN must reside on a separate IP to the server. This should be a private service network to the devices with private ports to the devices.
The VOP server requires static IP addresses.
|
 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|