User guide

ManualsBrandsFUJITSU ManualsComputer AccessoriesCentricStor V3.1D

Edition July 2007

CentricStor V3.1D

User Guide

Summary of content (640 pages)

PAGE 1
CentricStor V3.
PAGE 2
Comments… Suggestions… Corrections… The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs. Feel free to send us your comments by e-mail to: manuals@fujitsu-siemens.
PAGE 3
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1 Objective and target group for the manual . . . . . . . . . . . . . . . . . . . . . . 20 1.2 Concept of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.3 Notational conventions 1.4 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2 CentricStor - Virtual Tape Library . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
Contents 2.6 2.6.1 2.6.2 2.6.3 Procedures . . . . . . . . . . . . . . . . Creating the CentricStor data maintenance Issuing a mount job from the host . . . . . Scratch mount . . . . . . . . . . . . . . . 2.7 New system functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 2.8 2.8.1 2.8.2 2.8.3 2.8.4 2.8.4.1 2.8.4.2 Standard system functions . . . . . . Partitioning by volume groups . . . . . . “Call Home” in the event of an error . . . SNMP support . . . . . . . . . . . . . .
PAGE 5
Contents 4.1.3 4.1.3.1 4.1.3.2 4.1.3.3 4.1.3.4 4.1.3.5 4.1.3.6 4.1.3.7 4.1.3.8 4.1.3.9 4.1.3.10 4.1.3.11 System administrator activities . . . . . . . . . . . . . . . . Adding a logical volume group . . . . . . . . . . . . . . . Adding a physical volume group . . . . . . . . . . . . . . Adding logical volumes to a logical volume group . . . . . Adding physical volumes to a physical volume group . . . Assigning an LVG to a PVG . . . . . . . . . . . . . . . .
PAGE 6
Contents 5.2.3 5.2.4 5.2.5 5.2.5.1 5.2.5.2 GXCC in other systems . . . . . . . . . . . . . Screen display requirements . . . . . . . . . . Managing CentricStor via SNMP . . . . . . . . Connection to SNMP management systems SNMP and GXCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 5.3.1 5.3.2 5.3.2.
PAGE 7
Contents 6.1.6 6.1.6.1 6.1.6.2 6.1.7 6.1.8 6.1.9 6.1.9.1 6.1.10 6.1.11 6.1.12 6.1.12.1 6.1.13 6.1.14 6.1.14.1 6.1.14.2 6.1.15 6.1.16 6.1.17 6.1.18 6.1.19 Block diagram . . . . . . . . . . . . . . . . . . . . Status information . . . . . . . . . . . . . . . . Object information and object-related functions . ICP object information . . . . . . . . . . . . . . . . IDP object information . . . . . . . . . . . . . . . . Functions of an ISP . . . . . . . . . . . . . . . . . Show Details (XTCC) . . . . . . . . .
PAGE 8
Contents 6.2.7 6.2.7.1 6.2.7.2 6.2.7.3 6.2.7.4 6.2.8 6.2.8.1 6.2.9 6.2.9.1 6.2.9.2 6.2.9.3 6.2.9.4 6.2.9.5 6.2.9.6 6.2.9.7 6.2.9.8 6.2.9.9 6.2.9.10 6.2.9.11 6.2.9.12 6.2.9.13 6.2.9.14 6.2.9.15 6.2.9.16 6.2.9.17 6.2.10 6.2.10.1 6.2.10.2 6.2.10.3 6.2.10.4 6.2.10.5 6.2.10.6 6.2.10.7 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RAID Filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Volume Groups . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
Contents 7.3.1.2 7.3.2 7.3.3 7.3.3.1 7.3.3.2 7.3.4 7.3.5 Exit . . . . . . . . . . . . . . . . Config . . . . . . . . . . . . . . . . Tools . . . . . . . . . . . . . . . . . Global eXtended Control Center . Show Balloon Help Summary . . Statistics . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . 7.4 Global Status button bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 7.5 7.5.1 7.5.2 7.5.3 Display of the Global Status Monitor Performance . . . . . . . . . . . .
PAGE 10
Contents 7.7.1.5 7.7.1.6 7.7.1.7 7.7.1.8 7.7.2 7.7.3 7.7.4 7.7.5 7.7.5.1 7.7.5.2 7.7.6 7.7.6.1 7.7.6.2 7.7.7 7.7.8 Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status bar . . . . . . . . . . . . . . . . .
PAGE 11
Contents 8.3.4.4 8.3.4.5 8.3.5 8.3.5.1 8.3.5.2 8.3.5.3 8.3.5.4 8.3.5.5 8.3.6 8.3.6.1 8.3.7 8.3.7.1 8.3.7.2 8.3.7.3 8.3.7.4 8.3.7.5 8.3.7.6 Scan Now . . . . . . . . . . . . . . Interaction Timeout . . . . . . . . . Tools . . . . . . . . . . . . . . . . . . . XTCC Communications . . . . . . . Get Remote/Expand Local File . . . Show Remote File . . . . . . . . . . Compare Local Files . . . . . . . . . XTCC Update/Revert . . . . . . . . Profile . . . . . . . . . . . . . . . . . . Select . . . . . . . . . . .
PAGE 12
Contents 8.5.8.3 8.5.8.4 8.5.8.5 8.5.9 Abort . . . . . . . . . . . . Enlarge Font / Reduce Font Tab Stop Interval . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 365 366 366 8.6 8.6.1 8.6.2 8.6.2.1 8.6.2.2 8.6.2.3 8.6.2.4 8.6.2.5 8.6.2.6 8.6.2.7 8.6.2.
PAGE 13
Contents 8.10 8.10.1 8.10.1.1 8.10.1.2 8.10.1.3 8.10.2 8.10.2.1 8.10.2.2 8.10.2.3 8.10.2.4 Virtual 3490 drives . . . . . . . . . . . . . . . . . . . . . . Object information and error messages for virtual 3490 drives Error conditions indicated on the display . . . . . . . . . Object information . . . . . . . . . . . . . . . . . . . . . SIM/MIM error messages on virtual devices . . . . . . . . Virtual drive functions . . . . . . . . . . . . . . . . . . . . . Show SCSI Sense . . . . . . . . . . . . . . . .
PAGE 14
Contents 8.17 8.17.1 8.17.2 8.17.2.1 8.17.2.2 8.17.2.3 8.17.2.4 8.17.2.5 RAID systems . . . . . . . . . . . . . . . . . . . . Object information on RAID systems . . . . . . . . Functions of RAID systems . . . . . . . . . . . . . Show Complete RAID Status (all types) . . . . . Show Mode Pages (CX500/CX3-20 and FCS80) Show Mode Page Details . . . . . . . . . . . . Show Log Pages . . . . . . . . . . . . . . . . . Show Log Page Details . . . . . . . . . . . . . 8.18 8.18.1 8.18.
PAGE 15
Contents 8.23.3 8.23.3.1 Global functions for tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Remove Symbols of all Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 8.24 8.24.1 8.24.2 8.24.2.1 8.24.2.2 MSGMGR (Message Manager) . . . . . . . . . . . . . . Object information on the Message Manager (MSGMGR) MSGMGR functions . . . . . . . . . . . . . . . . . . . . Show Trace . . . . . . . . . . . . . . . . . . . . . . Show Trap Trace . . . . . . . . . . . . . . . . .
PAGE 16
Contents 9.2.12 9.2.13 9.2.14 9.2.15 9.2.15.1 9.2.15.2 9.2.15.3 9.2.15.4 9.2.16 9.2.17 9.2.18 9.2.19 9.2.20 9.2.21 9.2.22 9.2.23 9.2.24 9.2.25 9.2.26 9.2.27 9.2.28 9.2.29 SXMM... (Message Manager) . . . . . . . . . . . . . . . . . SXPL... (PLM: Physical Library Manager) . . . . . . . . . . . SXPS... (PLS: Physical Library Server) . . . . . . . . . . . . SXRD... (FibreCAT: RAID) . . . . . . . . . . . . . . . . . . . Messages of the monitoring daemon for the internal RAID FibreCAT S80 messages . . . . . . .
PAGE 17
Contents 12.1.2.2 12.1.2.3 12.1.3 12.1.3.1 12.1.3.2 12.1.3.3 12.1.3.4 12.1.3.5 12.1.3.6 12.1.4 12.1.4.1 12.1.4.2 12.1.4.3 12.1.5 12.1.5.1 12.1.5.2 12.1.5.3 12.1.5.4 12.1.5.5 12.1.6 12.1.7 Activating the configuration . . . . . . . . . . . . . . . . Changes in central files . . . . . . . . . . . . . . . . . . Monitoring CentricStor . . . . . . . . . . . . . . . . . . . . . GXCC as a monitoring tool without SNMP . . . . . . . . Monitoring using any SNMP Management Station . . . .
PAGE 18
Contents 12.4 12.4.1 12.4.1.1 12.4.1.2 12.4.1.3 12.4.2 12.4.3 12.4.4 12.4.4.1 12.4.4.2 12.4.5 12.4.6 12.4.7 12.4.8 12.4.9 12.4.10 12.4.11 Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xpdf, gzip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . GNU GENERAL PUBLIC LICENSE . . . . . . . . . . . . . . Appendix: How to Apply These Terms to Your New Programs Firebird . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 19
1 Introduction With CentricStor, a virtual tape robot system is placed in front of the real tape robot system (with the real drives and cartridges). In this way the host and the real archive are fully decoupled. The virtual tape robot system knows what are referred to as virtual (logical) drives and virtual (logical) volumes.
PAGE 20
Objective and target group for the manual Introduction The host is connected using the following connection technologies: ● ESCON channels ● FibreChannel ● FICON Communication between the individual control units takes place via the LAN in CentricStor, the transport of the user data to and from the RAID system via the FibreChannel. The physical drives can be connected to the backend via both FibreChannel and SCSI technology. 1.
PAGE 21
Introduction Notational conventions Global Status The Global Status Monitor provides a graphical display of all important operating data in a window. XTCC The program XTCC is used mainly to monitor the individual CentricStor computers (ISPs) including the peripheral devices connected to the computers. Explanation of console messages This chapter describes the most important of the console messages. And as far as possible suggests a way of solving the problem.
PAGE 22
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 23
2 CentricStor - Virtual Tape Library 2.1 The CentricStor principle Drive Drive Drive Drive Host Robots Data cartridges Conventional host robot system Figure 1: Conventional host robot system In a conventional real host robot system, the host system requests certain data cartridges to be mounted in a defined real tape drive. As soon as the storage peripherals (robots, drives) report that this has been completed successfully, data transfer can begin.
PAGE 24
The CentricStor principle CentricStor - Virtual Tape Library Robots Data cartridges CentricStor Drive Drive Drive Drive Physical volumes Host Disk cache Logicaldrive drive Logical Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive Logical drive logical volume
PAGE 25
CentricStor - Virtual Tape Library The CentricStor principle As soon as a mount job is issued, the Library Manager checks whether the requested volume is already in the disk cache. If so, the volume is immediately released for processing by the application. If not, CentricStor requests the corresponding cartridge to be mounted onto a physical drive, and reads the logical volume into the disk cache.
PAGE 26
Hardware architecture CentricStor - Virtual Tape Library 2.
PAGE 27
CentricStor - Virtual Tape Library Hardware architecture 2.2.1 ISP (Integrated Service Processor) CentricStor is a group of several processors, each running special software (UNIX derivative) as the operating system. These processors are referred to collectively as the ISP (Integrated Service Processor).
PAGE 28
Hardware architecture 2.2.1.2 CentricStor - Virtual Tape Library ICP (Integrated Channel Processor) The ICP is the interface to the host systems connected in the overall system.
PAGE 29
CentricStor - Virtual Tape Library 2.2.1.3 Hardware architecture IDP (Integrated Device Processor) The IDP is the interface to the connected tape drives. CentricStor FC FC IDP Robots SCSI or FC SCSI or FC Figure 6: Internal and external IDP connections The IDP is responsible for communication with real tape drives. To optimize performance, only two real tape drives should be configured per IDP. Because of the relatively short length of a SCSI cable (approx.
PAGE 30
Hardware architecture CentricStor - Virtual Tape Library 2.2.2 RAID systems for the Tape Volume Cache A TVC (Tape Volume Cache) is the heart of the entire virtual archive system. It represents all of the Tape File Systems in which the logical volumes can be stored temporarily. One or more RAID systems (up to 8) are used for this. Each RAID system contains at least the basic configuration, which consists of FC disks and 2 RAID controllers.
PAGE 31
CentricStor - Virtual Tape Library Hardware architecture The metadata of the logical volumes to be written or read is stored on the 1st RAID system, as a result of which the usable capacity of this RAID system is reduced by 16 GB. A CentricStor can contain up to 8 RAID. The number of cache file systems determines the number of logical volumes available (up to 500,000). At least one cache file system is required for each 100,000 logical volumes.
PAGE 32
Software architecture CentricStor - Virtual Tape Library This SAN-based design means that each CentricStor component is in a position to access the TVC. 2.2.
PAGE 33
CentricStor - Virtual Tape Library MSP/XSP LIB/SP z/OS OS/390 Software architecture CentricStor VLS VLP VLMF PLS ADIC AMU/SDLC DAS HACC CSC StorageTek VAMU PLS ACSLS BS2000 ROBAR VACS Jukebox CSC PLS Accessor VDAS Open Systems ACSLS PLP VJUK1 PLS LMF LITE DAS-ACI SCSI VLM PLM Backup software TVC CentricStor console Figure 8: Central role of the VLP in a CentricStor configuration1 VLP (Virtual Library Processor) The VLP is responsible for the coordination of the entire CentricStor
PAGE 34
Software architecture CentricStor - Virtual Tape Library VLM (Virtual Library Manager) Each robot job from the requesting host system is registered in the VLM. To support the libraries, corresponding emulations (VLMF, VAMU, VACS, VDAS, VJUK) are used in CentricStor. The TVC is administered exclusively by the VLM. The VLM data maintenance contains the names of the logical volumes with which the TVC is to work.
PAGE 35
CentricStor - Virtual Tape Library Operation 2.4 Operation CentricStor is operated via the graphical user interfaces GXCC (Global Extended Control Center) and XTCC (Extended Tape Control Center). These are used to perform all administration and configuration tasks. Using this control center, it is possible to display the current operating statuses of all CentricStor components, together with a large amount of performance and utilization data.
PAGE 36
Administering the tape cartridges CentricStor - Virtual Tape Library 2.5.2 Repeated writing of a logical volume onto tape Tape header Tape header If a logical volume which has already been saved onto tape is written to tape a second time following an update, the first backup will be declared invalid. The current volume is appended after the last volume of this tape or another tape with sufficient storage space.
PAGE 37
CentricStor - Virtual Tape Library Administering the tape cartridges 2.5.4 Reorganization of the tape cartridges LV0000 LV0003 LV0004 LV0005 PV0000 LV0006 LV0007 LV0008 LV0010 LV0009 CentricStor LV0002 LV0001 LV0011 PV0002 : : : : LV0037 VLM PV0001 Read tapes When a logical volume is released by the host’s volume management facility (e.g. MAREN in BS2000/OSD), it is flagged accordingly in the CentricStor data maintenance facility which contains the metadata for each volume.
PAGE 38
Procedures CentricStor - Virtual Tape Library 2.6 Procedures 2.6.1 Creating the CentricStor data maintenance Initial situation: CentricStor is installed and configured. As yet, there is no data on the RAID system. The tape cartridges of the robots are blank.
PAGE 39
CentricStor - Virtual Tape Library Procedures 2.6.2 Issuing a mount job from the host Initial situation: The logical volume LV0005 is already located on the physical volume PV0002.
PAGE 40
Procedures CentricStor - Virtual Tape Library Depending on whether the logical volume is still in the RAID system or is only on a physical volume, the following two situations arise: Case 1: The volume is migrated to tape and is no longer located in the RAID system. a) The VLM issues a request to the PLM to read the logical volume LV0005 into the RAID system. b) The PLM checks its data maintenance to determine the physical volume on which the requested logical volume LV0005 is located: PV0002.
PAGE 41
CentricStor - Virtual Tape Library Case 2: Procedures The logical volume has been modified. a) The VLM informs the PLM that the logical volume is to be copied onto tape. b) The PLM selects a suitable tape cartridge: a completely new tape, a scratch tape, or a tape onto which writing has not yet resulted in an overflow. If this cartridge is not yet mounted, the PLM checks whether a real drive is available in the robot archive at this point.
PAGE 42
Procedures CentricStor - Virtual Tape Library 2.6.3 Scratch mount To prevent reading in from the physical medium in cases where a logical volume is to be rewritten anyway, under certain circumstances CentricStor performs a “scratch mount”. The special features of the scratch mount in CentricStor are as follows: – If the logical volume is migrated, i.e. it is no longer in the TVC, only a “stub” is made available for the application. This stub contains only the tape headers.
PAGE 43
CentricStor - Virtual Tape Library New system functions 2.7 New system functions CentricStor Version 3.1C for the first time provides the option of creating logical volumes (LVs) more than 2 GB in size as a standard feature. The LV size can be selected in discrete steps for each logical volume group (LVG): STANDARD: EXTENDED: ● ● 900 MB 2 GB 5 GB 10 GB 20 GB 50 GB 100 GB 200 GB The DTV file system must be migrated for CentricStor systems configured with Version 3.0 or earlier.
PAGE 44
Standard system functions CentricStor - Virtual Tape Library 2.8 Standard system functions The following functions are standard in every CentricStor system: ● ● ● ● Partitioning by volume groups “Call Home” in the event of an error SNMP support Exporting and importing tape cartridges 2.8.1 Partitioning by volume groups CentricStor supports a volume group concept.
PAGE 45
CentricStor - Virtual Tape Library Standard system functions 2.8.3 SNMP support It is possible to integrate CentricStor into remote monitoring by an SNMP Management Station such as “CA Unicenter” or “Tivoli”. In the event of system errors (error weighting EMERGENCY, ALERT, ERROR, CRITICAL), CentricStor sends a trap to the SNMP Management Station, which causes the CentricStor icon to change color (insofar as this is supported by the SNMP Management Station).
PAGE 46
Standard system functions 2.8.4.1 CentricStor - Virtual Tape Library Vault attribute and vault status The vault attribute is assigned to a physical volume group (PVG) by means of the GXCC function Configuration ➟ Physical Volume Groups in the Type entry field (see page 187).
PAGE 47
CentricStor - Virtual Tape Library Optional system functions 2.9 Optional system functions CentricStor is available in a variety of configuration levels, in each of which further customer-specific extensions (e.g. larger disk cache) are possible.
PAGE 48
Optional system functions CentricStor - Virtual Tape Library 2.9.1 Compression The figure below illustrates the principle of software compression of logical volumes: Data from host ICP Logical volumes TVC EMTAPE VTD Figure 15: Principle of compressing logical volumes Just as a physical drive can perform data compression, so also can the tape drive emulations (EMTAPE1 or VTD2) once they have been released3 on the ICP. In this way, the logical volumes can be stored in compressed form in the TVC.
PAGE 49
CentricStor - Virtual Tape Library Optional system functions In BS2000/OSD (“HOST” attribute), compression is controlled on the basis of the tape type: – – TAPE-C3: TAPE-C4: compression off compression on In UNIX, the compression setting can be selected by the device nodes. The compression setting can be passed in ESCON or SCSI command to the tape emulation, and the compressed data is stored block-by-block on the logical volume (the VLM and PLM do not have any information about this).
PAGE 50
Optional system functions CentricStor - Virtual Tape Library All supported robot archive types are permitted: – – – – – ADIC AML systems (with DAS) ADIC scalar systems (with DAS or SCSI) StorageTek systems (with ACSLS or SCSI) IBM Cashion Fujitsu robot (with LMF) Please refer to the current product information for the library and drive type configurations currently available. It is possible to have different drive types within the same archive.
PAGE 51
CentricStor - Virtual Tape Library Host2 LVG2 Host1 LVG1 LVG 1 LV0001 CentricStor LV0002 LV0003 ........... LV3000 PVG 1 PV0001 PV0002 PV0003 ........... PV0300 Optional system functions PVG 2 PV0301 PV0302 PV0303 ........... PV0600 LVG 2 LV3001 LV3002 LV3003 ........... LV6000 PVG 3 PV0701 PV0702 PV0703 ........... PV0800 Archive1 PVG 4 PV0801 PV0802 PV0803 ...........
PAGE 52
Optional system functions CentricStor - Virtual Tape Library 2.9.4 Extending virtual drives This option allows you to increase the number of logical drives from the standard 32 per ICP to up to 64 per ICP. This makes it possible to operate up to 256 logical drives in a single CentricStor system. 2.9.5 System administrator’s edition The “System Administrator Edition” (SAE) option provides a graphical user interface for administering the CentricStor system from a remote PC workstation.
PAGE 53
CentricStor - Virtual Tape Library Optional system functions If the “automatic VLP failover” function has been activated, the following actions are no longer permitted in the system: i – – – changing the LAN configuration rebooting or shutting down of the VLP (init 0 or init 6: these commands cause a failover!) disconnecting a LAN or FC cable If the VLP fails, the scenario is as follows: 1.
PAGE 54
Optional system functions CentricStor - Virtual Tape Library 3. After the defective processor has been repaired, it is integrated once again into the overall system and takes over the role of the SVLP: ISP SVLP VLP ISP Activation FC fabric Figure 20: Activation of the defective processor for the SVLP The status, i.e.
PAGE 55
CentricStor - Virtual Tape Library Optional system functions 2.9.8 Cache Mirroring Feature 2.9.8.1 General CentricStor V3.1 provides users with enhanced data security and greater protection against data loss through disasters, promptly for all nearline data. Data stored on the internal hard disk system is mirrored synchronously to a second cluster location. This is done via 2-Gbit FibreChannel connections, also over long distances.
PAGE 56
Optional system functions 2.9.8.3 CentricStor - Virtual Tape Library Software requirements The “vtlsmirr” key must have been read in and enabled for the mirror function. This is done by customer support. Assuming that the hardware requirements are satisfied (see the section above) and the RAID systems have been defined by the corresponding LUN assignment (see the section “Mirrored RAID systems” on page 57), the overall system is configured as a mirror system solely through the existence of the key.
PAGE 57
CentricStor - Virtual Tape Library 2.9.8.4 Optional system functions Mirrored RAID systems A mirrored CentricStor system has 1 to a maximum of 4 RAID mirror pairs.
PAGE 58
Optional system functions 2.9.8.5 CentricStor - Virtual Tape Library Presentation of the mirror function in GXCC In GXCC the mirror functions of a double RAID system are indicated by two arrows.
PAGE 59
CentricStor - Virtual Tape Library Optional system functions 2.9.9 Accounting On the one hand this function permits the accounting data of logical volume groups to be displayed in GXCC (see the section “Statistics » Usage (Accounting)” on page 293). Example On the other hand this function enables the current accounting data to be sent by e-mail at defined times (see the section “Setup for accounting mails” on page 229).
PAGE 60
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 61
3 Switching CentricStor on/off IMPORTANT! The vendor recommends that CentricStor should not be switched off. This should only be done in exceptional circumstances. ! 3.1 Switching CentricStor on Before switching CentricStor on, you must ensure that the units with which CentricStor is to communicate, i.e. host computers, ROBAR-SV systems (in the case of host connection via ROBAR), the robot control processor, and the tape robots are already up and running.
PAGE 62
Switching CentricStor off Switching CentricStor on/off Using GXCC or XTCC check that all the necessary CentricStor processes are running (all processor boxes must be green). 5. BS2000/OSD: Case 1: Host connection via ROBAR Ê Start ROBAR-SV (with the menu program robar or robar_start; see ROBAR manual [3]). Case 2: Host connection via CSC Ê Start CSC (see CSC manual [4]). 3.
PAGE 63
4 Selected system administrator activities 4.1 Partitioning on the basis of volume groups 4.1.1 General By partitioning on the basis of volume groups, it is possible to combine certain logical volumes to form a logical volume group (LVG) and certain physical volumes to form a physical volume group (PVG).
PAGE 64
Partitioning on the basis of volume groups UNIX system BS2000 host LVG1 LV0001 LV0002 LV0003 ........... LV3000 PVG1 PV0001 PV0002 PV0003 ........... PV0300 CentricStor Archive BS2000 UNIX data Data LVG2 LV3001 LV3002 LV3003 ........... LV6000 PVG2 PV0501 PV0502 PV0503 ........... PV0600 Selected system administrator activities You have two different systems (a BS2000 host and a UNIX system) using CentricStor in conjunction with an archive system.
PAGE 65
Selected system administrator activities Partitioning on the basis of volume groups Physical volume groups: – It is possible to configure up to 100 physical volume groups1. i By default, CentricStor always has at least two physical volume groups (“BASE” and “TR-LVG”). These exist in addition to the freely configurable volume groups. – All physical volumes of a physical volume group belong to the same physical library.
PAGE 66
Partitioning on the basis of volume groups 4.1.3.1 Selected system administrator activities Adding a logical volume group ● The form and detailed information are provided in the section “Logical Volume Groups” on page 173 1. Click on the “NEW” button. 2. The following must be entered: Name Type Location Comment Name of the new logical volume group Extended (2 GB, ... , 200 GB) or standard (900 MB) Cache area (floating or defined explicitly) Comment 3. Click on the “OK” button.
PAGE 67
Selected system administrator activities 4.1.3.4 Partitioning on the basis of volume groups Adding physical volumes to a physical volume group Only physical volumes contained in the physical library may be specified. i The form and detailed information are provided in the section “Physical Volume Operations » Add Physical Volumes” on page 223.
PAGE 68
Partitioning on the basis of volume groups 4.1.3.7 Selected system administrator activities Changing logical volumes to another group The form and detailed information are provided in the section “Logical Volume Operations » Change Volume Group” on page 209. ● The following information must be specified: – Specification whether all volumes (“all”) or just a certain number (“range”) of volumes of the original logical volume group are to be moved to the new group.
PAGE 69
Selected system administrator activities 4.1.3.10 Partitioning on the basis of volume groups Removing physical volumes from a physical volume group Only scratch tapes which do not contain any valid logical volumes can be removed, unless the physical volumes have been reorganized prior to doing this (flag is set). i ● The form and detailed information are provided in the section “Physical Volume Operations » Erase Physical Volumes” on page 226.
PAGE 70
Cache management Selected system administrator activities 4.2 Cache management This functionality enables individual cache file systems to be reserved for exclusive use by particular LV groups. LV groups which are not assigned to a cache file system are distributed to the remaining caches (“FLOATING” setting). Cache file system LVG1 LV0001 LV0002 LV0003 ........... LV3000 FLOATING /cache/101 LVG4 LVG3 LV3001 LVG2 LV3001 LV3002 LV3001 LV3002 LV3003 LV3002 LV3003 ........... LV3003 ........... LV6000 ...
PAGE 71
Selected system administrator activities Dual Save The specification of whether a logical volume group is defined as “FLOATING” or with cache residence in a particular cache is made in the “Location” field when the logical volume group is defined (see section “Logical Volume Groups” on page 173). The settings for the cache file system can be altered later at any time. 4.3 Dual Save 4.3.
PAGE 72
Dual Save Selected system administrator activities 4.3.2 System administrator activities 4.3.2.1 Assigning a logical volume group to two physical volume groups The form and detailed information are provided in the section “Physical Volume Operations » Link/Unlink Volume Groups” on page 221.
PAGE 73
Selected system administrator activities Reorganization 4.4 Reorganization A brief overview of the reorganization of tape cartridges can be found on page 37. i 4.4.1 Why do we need reorganization? Reorganizations are performed for the following four reasons: 1.
PAGE 74
Reorganization Selected system administrator activities 4. Physical volume inaccessible status The PLM can no longer access the physical volume. This can be due to the following reasons: – – The robot cannot access the physical volume. The tape header cannot be read. The logical volumes affected may need to be read in again from a backup copy (dual save) and backed up again. 4.4.
PAGE 75
Selected system administrator activities Reorganization 4.4.3 When is a reorganization performed? Depending on the type of event or status which triggers reorganization, the PLM performs reorganization either immediately after the event occurs or within a configurable time of day interval.
PAGE 76
Reorganization Selected system administrator activities Once the number of scratch tapes reaches the hard limit again, the “all clear” is given (see page 76): SXPL011 ... PLM(#11): NOTICE: number of free PVs of PV-group over absolute minimum () again For the following statuses, reorganization is only initiated within the configured time of day interval.
PAGE 77
Selected system administrator activities Reorganization Only physical volumes in read status on which the relative proportion of valid data is less than the percentage value configured in the Fill Grade parameter are taken into account. If a physical volume is in write status and the percentage value for its valid data drops below the Fill Grade value, it is placed in read status and is therefore a candidate for reorganization.
PAGE 78
Reorganization Selected system administrator activities 4.4.5 Own physical volumes for reorganization backup The PLM distinguishes between backup requests from the host and backup requests which are caused by a reorganization. As long as the number of scratch tapes is above the hard minimum, the PLM attempts to use a physical volume exclusively for the request type involved.
PAGE 79
Selected system administrator activities Reorganization 4.4.7 Configuration parameters All configuration parameters can be set specifically for each physical volume group. It must be ensured that a dependency on the number of available drives exists and that not too many reorganizations take place in parallel, otherwise these will be delayed unnecessarily on account of the lack of drives. Each reorganization requires two drives: one for reading in and one for writing.
PAGE 80
Reorganization Selected system administrator activities When the percentage of valid data on a physical volume which is in write status and is not currently mounted in a Physical Device Service is below this limit value and at the same time a reorganization is in progress because a scratch tape limit value has been fallen below, this physical volume is placed in read status, and it is therefore a candidate for reorganization.
PAGE 81
Selected system administrator activities Cleaning physical drives PLM Refresh Interval Number of days after which the physical volumes in this group are to be recopied. The count starts with the day on which the physical volume switched from scratch status to write status. This value must be defined in accordance with the recommendations of the tape manufacturer. Default: 365 4.
PAGE 82
Synchronization of the system time using NTP Selected system administrator activities 4.6 Synchronization of the system time using NTP In CentricStor the configuration with regard to NTP is carried out automatically, which means that the file /etc/ntp.conf is created with the appropriate entries for each computer. It is no longer necessary for the system administrator to modify the files.
PAGE 83
5 Operating and monitoring CentricStor 5.1 Technical design 5.1.1 General CentricStor monitoring and operation is carried out on two levels by GXCC and XTCC. .
PAGE 84
Technical design Operating and monitoring CentricStor GXCC (Global Extended Control Center) is a program with an X user interface that provides a complete graphical representation of a CentricStor system, and covers all connected devices and ISPs (Integrated Service Processors) such as ICPs (Integrated Channel Processors), IDPs (Integrated Device Processors), and VLPs (Virtual Library Processors). GXCC processes all ISPs and other components of a CentricStor cluster as if they were a single unit.
PAGE 85
Operating and monitoring CentricStor Technical design The figure below shows the components and the connections used for control and monitoring (the Fibre Channel networking and the paths to the hosts are not shown): CentricStor Remote computer VLP GXCC ouput data GXCC InfoBroker IDP InfoBroker FC fabric X11 server GXCC ICP InfoBroker SCSI components SNMP components SCSI or FC interface LAN or TCP/IP connection within processor LAN Figure 30: GXCC components with X11 server as remote computer
PAGE 86
Technical design Operating and monitoring CentricStor In this configuration GXCC runs on the remote computer (e.g. Windows PC) and uses the interfaces of its user interface directly. At short intervals GXCC inquires of the CentricStor VLP whether there is new data. Here only 20 bytes are transferred. If new data is available, the VLP sends the GXCC user data to the remote computer, which edits the data and forwards it to the output screen.
PAGE 87
Operating and monitoring CentricStor Technical design 5.1.3 Monitoring structure within a CentricStor ISP The figure on page 89 contains a more detailed representation of how GXCC monitors the individual CentricStor control components. This figure should also be regarded as one example of the many configurations possible. The figure shows the logical or physical connections used by GXCC for monitoring and control purposes.
PAGE 88
Technical design Operating and monitoring CentricStor The table below lists the control components: Name Function Comment LD Logical Device: emulation of a drive. Must run on the ISP in which the associated host interface (ESCON/ FICON/FC) is installed (ICP). MSGMGR Message Manager: filters and stores Only one instance throughout system messages. Triggers actions in CentricStor. response to certain situations (e.g. SNMP traps). PDS Physical Device Service: drives one physical tape drive.
PAGE 89
Operating and monitoring CentricStor Technical design ISP of the CentricStor network Remote computer Keyboard Screen VLM PLM Mouse VLS PLS GXCC MSGMGR PERF InfoBroker RequestBroker ICP of the CentricStor network VMD Mainframe hosts LD Open Systems hosts VLS ESCON, FICON or FC host connection InfoBroker RequestBroker IDP of the CentricStor network PDS SCSI drives SCSI libraries PLS SCSI or FC connections to drives and libraries InfoBroker RequestBroker TCP/IP LAN TCP/IP LAN or TCP/IP
PAGE 90
Technical design Operating and monitoring CentricStor 5.1.4 Operating modes GXCC recognizes the following three user privilege levels: Service mode Access to all CentricStor functions available via GXCC. Users must use the “diag” password to identify themselves to the CentricStor ISP with which they are connected. User mode Access to the functions required for normal operation.
PAGE 91
Operating and monitoring CentricStor Operator configuration 5.2 Operator configuration 5.2.
PAGE 92
Operator configuration Operating and monitoring CentricStor 5.2.3 GXCC in other systems GXCC can also be installed and is executable in Windows 98/NT/2000/XP, LINUX and SOLARIS systems. An installation CD is supplied with each CentricStor. This contains the tools and information files required for installation on the relevant systems. You will find more information on this in the installation manual. GXCC V6.0, GXCC V3.0 and GXTCC V2.x can be installed in the same system at the same time.
PAGE 93
Operating and monitoring CentricStor 5.2.5.2 Operator configuration SNMP and GXCC Monitoring and operation of CentricStor by GXCC runs independently of SNMP. In addition, however, CentricStor also offers the basic functions required for management via an SNMP station. Thanks to the great flexibility of GXCC as regards configuration, when GXCC is used together with SNMP the monitoring and operation of CentricStor can be adapted to suit the IT infrastructure and the requirements of the user.
PAGE 94
Operator configuration Operating and monitoring CentricStor The figure below shows some of the possible configurations for an SNMP manager for connecting GXTXCC to the triggering CentricStor on the basis of a trap: SNMP management station Application launching SNMP manager X11 server GXCC Workstation GXCC SNMP agent Info Broker GXCC CentricStor SNMP agent GXCC Info Broker GXCC Optional if there is no RMT license GXCC CentricStor X11 connection to GXCC, higher bit rate required Traps from
PAGE 95
Operating and monitoring CentricStor – Starting GXCC The GUI software must be installed explicitly on the workstation for operation of GXCC outside CentricStor. A CD with GXCC (GUI CD) is provided free with each CentricStor. GXCC can be installed an unlimited number of times to run CentricStor. It will run on Windows 98/NT/2000/XP, LINUX, SOLARIS and SINIX-Z systems. 5.3 Starting GXCC 5.3.1 Differences to earlier CentricStor versions i In CentricStor V3.
PAGE 96
Starting GXCC Operating and monitoring CentricStor The table below lists the possible start parameters: Parameter Meaning Comment 1 -aspect Size and position of the main win- has the format dow on the screen [=][WxH]+|-X+|-Y WxH: Width x height (pixels) X,Y: Coordinates (pixels) [*] * is optional +|+ or - 96 -autoscan1 Cycle duration for updating the main window Reduction of the data when operating via Teleservice -display Host name/IP address of the X terminal at which the windo
PAGE 97
Operating and monitoring CentricStor Parameter Meaning Comment -user Starts the application in User mode If not specified: User mode 1 The command line arguments -aspect, -autoscan, -lang, -size have priority over values already stored in a profile file. To start in User mode, use: To start in Observe mode, use: 5.3.2.
PAGE 98
Starting GXCC Operating and monitoring CentricStor 5.3.3 Environment variable XTCC_CLASS GXCC supports an environment variable with this names as follows: If this environment variable is not defined when GXCC is started, it is set to the value “Xtcc”. Otherwise the specified value is taken. The relevant value is is inherited by all applications called by the current GXCC instance.
PAGE 99
Operating and monitoring CentricStor 5.3.4.1 Starting GXCC Optional access control for Observe mode When a CentricStor V3.1 system is installed, the “xtccobsv” ID is set up by default and the line “+ xtccobsv” entered in the home/xtccobsv/.rhosts file. As a result this optional access control is initially inactive and no password is required for Observe mode. This procedure is the same as in earlier CentricStor versions.
PAGE 100
Starting GXCC 5.3.4.3 Operating and monitoring CentricStor Suppressing the password query Releasing individual users The password query can be suppressed if an entry in the .rhosts file permits access to CentricStor. To do this, the monitoring system is entered in the following .rhosts file on the monitored system: Service mode: User mode: Observe mode: /usr/apc/diag/.rhosts home/xtccuser/.rhosts home/xtccobsv/.rhosts The following options are available for an entry in the .
PAGE 101
Operating and monitoring CentricStor 5.3.4.4 Starting GXCC Additional password query If GXCC or XTCC requires a password to transfer an update (see the section “Software updates” on page 118) or manual (see the section “Online Manual” on page 235), the following window appears: This password query is made only when the user can access the system without a primary password query.
PAGE 102
Starting GXCC Operating and monitoring CentricStor 5.3.5 Starting the CentricStor console ● Position the mouse pointer to a neutral screen area. ● Press the right mouse button. ● The Root Menu appears, including the function “Global eXtended Control Center”. If you select this item, you are offered the three modes of GXCC: – – – Observe Mode User Mode Service Mode When you have selected the required start mode GXCC is started. 5.3.6 Starting from an X11 server i 5.3.6.
PAGE 103
Operating and monitoring CentricStor – Starting GXCC and the RequestBroker of the connected ISP, which gathers information from all components and forwards commands from the man/machine interface to the respective recipients (XTCC, which only ever handles a single ISP, connects itself directly to the InfoBroker of this ISP). X11 server (e.g. VLP, workstation or PC, Mac, Linux etc.) Includes the mouse, keyboard, screen. Can be a SINIX or Windows system or another system with appropriate software.
PAGE 104
Starting GXCC 5.3.6.2 Operating and monitoring CentricStor Using the direct XDMCP interface The full range of XDMCP (X Display Manager Control Protocol) functions cannot be used in CentricStor 2.1. You are strongly recommended to use the X11 servers in Passive mode. 5.3.6.3 Starting from a UNIX system 1. Make sure that the ISP to be addressed is listed in the XHOST list of the calling system.
PAGE 105
Operating and monitoring CentricStor 5.3.6.4 Starting GXCC Starting from a Windows system via Exceed With appropriate preparation, GXCC can be started by clicking an icon on the desktop. More details can be found in the Exceed help information. This section only describes the GXCC-specific settings of Exceed. Exceed preparations Ê Open the following window by choosing “Programs” ➟ “Exceed” ➟ “Xconfig”: Ê Click “Communication” in the Xconfig window.
PAGE 106
Starting GXCC Operating and monitoring CentricStor Starting GXCC via Exceed Ê Start Exceed (preferably via the Windows autostart function). Ê Choose “Xstart”. Ê Activate the Start menu as shown in the following example: The user ID is tele, and the password entered must be the appropriate tele password. The GXCC password is requested later in accordance with the desired operating mode. Host contains the IP address of the ISP to be addressed (generally the VLP).
PAGE 107
Operating and monitoring CentricStor Starting GXCC Choose the Windows Start menu “Programs” ➟ “Hummingbird Connectivity” ➟ “Exceed” and ➟ “Xsession” to display a selection of start files: When you have selected the start file and chosen “Run!”, GXCC will be started on the selected unit. i U41117-J-Z125-7-76 However, you can also drag the start file to the desktop as a shortcut or save it on the desktop. Then, the program is started as usual by double-clicking the icon.
PAGE 108
Starting GXCC 5.3.6.5 Operating and monitoring CentricStor Starting from a Windows/NT system via XVision i When installing XVision, the UNIX environment must also have been installed. XVision setting An example is shown in the following diagram: It is important that the display mode “Multiple windows” is set.
PAGE 109
Operating and monitoring CentricStor Starting GXCC The diagram below shows an example of the fonts setting: Ê The “Allow font substitution” option must be disabled. Ê When specifying the font path items, the UNIX fonts must be listed before other fonts. If different settings are defined, the layout of GXCC windows and dialog boxes may be corrupted.
PAGE 110
Starting GXCC Operating and monitoring CentricStor All options must be disabled in the “Security” tab. The “XDMCP” box may not be checked, to ensure that Passive mode is secure: Settings for the client The X11 server must be included in the host list of the computer on which the GXCC is running. This can be done using the XVision Services “Host Finder” or “Host Explorer”. You must use the user ID “tele”. To automate the login process, the ID and password should be stored in the host characteristics.
PAGE 111
Operating and monitoring CentricStor Starting GXCC Starting GXCC with the “Remote Program Starter” Ideally, GXCC should be activated via the “Remote Program Starter”. This allows the process to be automated such that GXCC can be started by clicking an icon. When GXCC is started in Observe mode, no further dialog is then required. Preparing the Program Starter: An appropriate file (*.rps file) must be created.
PAGE 112
Starting GXCC Operating and monitoring CentricStor Example The settings under “Options” and “View Response” should correspond to those shown in the example. The full contents of the command line are shown in the “Display” tab: The input field “Title” has no effect and should not be used. If you need the “-title” function (label on the window title bar only, not on the icon), specify “-title” instead of “-name” in the command line.
PAGE 113
Operating and monitoring CentricStor Starting GXCC The settings can be saved in a file with an .rps extension. When you double-click the file, the Remote Program Starter is started and executes this file. If you create a link to this file on the desktop, you can therefore start GXCC by double-clicking the corresponding icon. Only the password for User or Service mode need then be entered manually.
PAGE 114
Starting GXCC Operating and monitoring CentricStor i This allows you to control whether everyone with access to your host can also start GXCC. You can save the settings. After the terminal emulation has started, you can activate the saved settings and establish the connection. 5.3.
PAGE 115
Operating and monitoring CentricStor Starting GXCC If the local system is not part of a CentricStor network and no unit name is specified in the start parameters, a message box will be output leading you to the “Unit Select” menu (see the sections “Selecting the CentricStor system” on page 116 and “Unit” on page 147): File Clicking “File” starts GXCC in Test and Demo mode. In this mode, information is obtained from files taken from GXCC systems beforehand. Unit Opens the Unit Select menu.
PAGE 116
Starting GXCC Operating and monitoring CentricStor 5.3.8 Selecting the CentricStor system If the local system is not part of CentricStor, the Unit Select menu is displayed when GXCC is started. Example The operation and functions of Unit Select are described in the section “Select” on page 147. Errors that occur when a connection is established after clicking on “OK” are handled differently because no connection yet exists to CentricStor. 5.3.
PAGE 117
Operating and monitoring CentricStor Starting GXCC 5.3.10 Authentication As soon as a connection has been established, client authentication takes place. Passwordbased authentication is performed every time the program is started. When operating in User mode, you will be requested by the addressed system to enter the password of the user ID “xtccuser”. Passwords are normally not required (see the section “Operating modes” on page 90 and the section “Passwords” on page 98) when operating in Observe mode.
PAGE 118
Starting GXCC Operating and monitoring CentricStor If the password is entered incorrectly three times, GXCC will be started in Observe mode (but only if no password protection has been set for Observe mode). 5.3.11 Software updates If you have contacted a “remote” CentricStor system, the InfoBroker checks whether its system contains more recent versions of GXCC and XTCC. If required you will then be informed via a window that the InfoBroker has more recent versions.
PAGE 119
6 GXCC 6.1 Main window 6.1.1 Standard The GXCC main window shows a circuit diagram of CentricStor. If pictures of real products (robots, drives, RAID systems) are used, these are only symbols which bear no relation to the actual appearance of the product.
PAGE 120
Main window GXCC ● Left half of screen – Circuit diagram of CentricStor ● Right half of screen – System information – Information field ● Line with the last console alarm message and acknowledgment button ● Footer 6.1.2 Loss of a connection If the connection to the InfoBroker is lost, the data displayed will no longer be current. An attempt is made to establish a new connection approximately every 20 seconds.
PAGE 121
GXCC Main window 6.1.3 Elements of the GXCC main window 6.1.3.1 Title bar The title bar is laid out as follows: : CentricStor() : System name entered during configuration. No display if no system name has been entered. IP address and unit name of the ISP to which GXCC is connected. If GXCC is running on the VLP, this is set to “local”. In Simulation mode the title bar contains only the display “Simulation”. 6.1.3.
PAGE 122
Main window GXCC i An error flag (yellow or pink) can be displayed only if the Infobroker has been started and is operational. Consequently in certain situations, especially during the boot phase of individual ISPs, it can occur that an overall status of turquoise (OK) is displayed even though the status of individual ISPs is shown as not operational in the GXCC main window. i Further information is provided in section “GXCC as a monitoring tool without SNMP” on page 549.
PAGE 123
GXCC 6.1.3.3 Main window – Scan rate Interval between scans in seconds. – Bit rate The floating point number shows the bit rate for communication with the InfoBroker. The rate is calculated using the length of time taken to transfer a status information package. This indicator is of particular interest in the case of a modem connection. – Operating system of the host to be monitored – GXCC version The GXCC version is shown in the last field.
PAGE 124
Main window 6.1.3.5 GXCC Console messages Console messages are displayed above the footer. These can be: – – – system messages messages relating to the system configuration messages relating to the connection between GXCC and the system The last messsage is always displayed. You obtain the complete message log by clicking on the relevant function button (see the section “Function buttons and displays in the button bar” on page 123).
PAGE 125
GXCC Main window 6.1.4 Message window Many GXCC messages must be taken notice of and acknowledged by the user. This prevents the same function or contradictory functions being started on one device. Message windows with an “OK” button are closed after you click on this button. Message windows without an “OK” button with texts such as “... Timeout is nn sec. Please wait ...” are displayed if Broker data is waited for at the same time as a device function is performed.
PAGE 126
Main window GXCC 6.1.6 Block diagram The main window displays a circuit diagram of the CentricStor system with the ISPs, RAID systems and the connecting Fibre Channel system. Processors CentricStor is a group of processors, each running the SINIX-Z operating system. These processors are referred to collectively as the ISP (Integrated Service Processor).
PAGE 127
GXCC Main window The triangle at the top left indicates that GXCC is connected to this ISP. The boxes at the upper edge contain the numbers of the controllers. Triangle on the right-hand side: Mirror status The status of the hardware components and drivers is displayed in the right-hand margin (see page 133). The line in upper case specifies the ISP type.
PAGE 128
Main window GXCC Special aspects when performing Distribute and Activate The following special aspects must be borne in mind when performing Distribute and Activate: ● Some GXCC menu items are hidden. ● The current progress is displayed in blue script in the system message line. Messages are displayed here concerning the stage which the procedure has reached. ● The status (only in the event of an error) of each ISP is displayed.
PAGE 129
GXCC Main window Fibre channel elements The internal FC connections are represented in the form of an FC fabric in the center of the figure with connections to both the ISPs and the RAID system(s). FibreChannel connections to the FC switch which are faulty are drawn with dashed lines until the SNMP trap has been processed by the FC switch. These lines are then removed. i The VLP and the SVLP must be entered in the FC switch as the trap receiver, otherwise the lines cannot be removed.
PAGE 130
Main window GXCC A check is made to see whether, in the case of redundant Fibre Channel systems, the connections go from every ISP to various switches and whether the FC adapter with the lowest number goes to the switch with the lowest number (throughput optimization).
PAGE 131
GXCC Main window The colors have the following meaning: Green Operational Pink i Not operational, no cache file system affected As in the case of the FibreCAT CX500/CX3-20 or Eternus 3000/4000 it is not possible to read the status via an FC port, the “operational” status (green) is displayed for these RAID systems.
PAGE 132
Main window GXCC Left-clicking on the RAID symbol causes further information to be output in the righthand part of the GXCC info window: RAID information in the info window RAID symbol This example shows a CentricStor with two RAID systems (IDs: 1 and 2). Information on both RAID systems is output in the info window: The primary caches 100, 101, 102, 103 und DB are located on the RAID system with the ID 1. The associated secondary cache is located on the RAID system with the ID 2.
PAGE 133
GXCC 6.1.6.1 Main window Status information The current operating status of CentricStor elements is indicated by the background color of the associated symbols. The bar on the right which is divided into several compartments shows the status of hardware components and drivers. i Green: Yellow: Pink: Red: Blue: You can obtain detailed information in the right-hand part of the window by clicking on the object with the left mouse button. All subcomponents are online and ready to operate. Undefined.
PAGE 134
Main window GXCC 6.1.7 ICP object information In order to be able to connect to various host types, ISPs can contain ESCON/FICON channel adapters, FC adapters or both types of connection. The object information will vary accordingly. Object information of an ICP which contains only FibreChannel ports. The following information is displayed: – name and release version of the ICP. – the operating status of the channel adapter(s) and the FibreChannel adapter for the host connection (= upper box).
PAGE 135
GXCC Main window 6.1.8 IDP object information The following information is displayed: – name and release version of the IDP – if present: IP address of the external LAN port(in the example the external port is faulty) – the status of the FC controller for the connection to the cache (= top box) – the operating status of the physical device servers (= middle box) – the operating status of the SCSI controllers for the tape drives (= bottom box) 6.1.
PAGE 136
Main window GXCC 6.1.11 Information about the RAID systems This information box shows the following information for every RAID system (by a box symbol to the right of the RAID symbol): – – – the type and target number of the RAID controller(s) the status of the RAID controller(s) any additional information available If CentricStor has several RAID systems, the box to the right of the symbol is divided into the corresponding number of fields.
PAGE 137
GXCC Main window 6.1.12 RAID system functions The following window appears when you right-click on the RAID symbol: 6.1.12.1 Show complete RAID status Selecting this option displays all the data of the RAID systems: i As in the case of the FibreCAT CX500/CX3-20 and Eternus 3000/4000 it is not possible to read the status via an FC port, “no information available” is always output for these RAID systems.
PAGE 138
Main window GXCC 6.1.13 Information on Fibre Channel fabric Information on FC switches can be obtained via SNMP (Simple Network Management Protocol). The mnemonic name, operating status, and contents of the last unprocessed trap are output. If the message “No data received” is displayed instead of this information, this indicates that there are no unprocessed traps present.
PAGE 139
GXCC 6.1.14.1 Main window Controller Color Scheme You can select whether you wish to display the FC connections in such a way that all connections to a single ISP are displayed in the same color (Controller Color Scheme) or so that all connections to a domain (a switch) are displayed in the same color (Domain Color Scheme). The mode that is not currently set will be offered. This setting is only relevant for the representation. If incorrect cabling exists, the color setting will have no effect.
PAGE 140
Main window GXCC 6.1.15 Information about the FC connections If you hover the mouse pointer over an icon belonging to an FC connection, information about this line will be displayed. The following information is output: – – the name of the switch, as assigned during configuration, and the port that the line goes to. The controller in the ISP can be read directly from the overview image (13 in the example shown above). 6.1.
PAGE 141
GXCC Main window 6.1.17 ISP system messages If an important console message is entered in the log file (/usr/apc/vtls/ VTLS_MESSAGES) of one of the CentricStor ISPs, this is displayed in the lower part of the GXCC window. Messages with the statuses “ERROR”, “CRITICAL” (red) and “ALERT”, “EMERGENCY” (red: flashing red) are considered critical. By clicking on the button to the left of the message line you confirm you have read the message in your GXCC. You can thus recognize when a new message has arrived.
PAGE 142
Main window GXCC 6.1.19 Configuration Changed If a configuration change is currently being processed in CentricStor, a floppy disk symbol with a yellow background will appear in the button bar. This occurs if a menu item of the configuration complex is confirmed with “OK” after activation of the last configuration change. 142 i When the InfoBroker is restarted, the latent configuration changes are deleted.
PAGE 143
GXCC Function bar 6.2 Function bar dd The individual functions can be selected either by clicking on them with your mouse or by pressing the ALT key together with the accelerator key (underlined letter). i How exactly such shortcuts are handled depends on the operating system or the Window Manager, e.g. on whether the keys are pressed simultaneously or first ALT and then the key for the undescored character is pressed. 6.2.
PAGE 144
Function bar 144 GXCC ● Configuration (page 166) – RAID Filesystems (page 171) – Logical Volume Groups (page 173) – Physical Volume Groups (page 181) – Distribute and Activate (page 188) ● Profile (page 191) – Add/Select Profile(page 191) ● Administration (page 193) – Show WWN’s (page 195) – Show Optional Functions (page 196) – Show CS Configuration (page 197) – Diagnostic Snapshots (page 197) – Logical Volume Operations (page 202) – Physical Volume Operations (page 215) – Setup for accounting mails
PAGE 145
GXCC Function bar 6.2.2 File Es stehen folgende Funktionen zur Verfügung: – – – – – 6.2.2.1 Save Open Show Print Exit Save Saves the current InfoBroker data. You can thus use this to recover the system display subsequently. By default, configurations are saved as .gxd files. i With this function you save precisely the data which currently leads to the picture displayed. As a result you can practically retain a snapshot in the form of source files. This data can later be read into a GXCC.
PAGE 146
Function bar 6.2.2.2 GXCC Open Opens a file selector window with which you can open a configuration that was generated with “Save” (see above). The window contains the field for entering the file name plus the following function keys: OK Checks whether the specified file is a valid GXCC configuration file and, if so, outputs its contents in graphical format and is displayed in Simulation mode. If not, an error message is output.
PAGE 147
GXCC 6.2.2.5 Function bar Exit Shuts down GXCC. It is recommended that you use this function in preference to the button in the top left-hand corner of the window. When GXCC is shut down, any global status processes started from GXCC will remain active. 6.2.3 Unit In this manual the ISPs of a CentricStor are referred to as “units”. This is to prevent confusion with the BS2000, z/OS, OS/390 or Open Systems computers, the hosts, which are connected to CentricStor.
PAGE 148
Function bar GXCC The indirect connection is used to monitor systems which cannot be reached directly (Example: Modem connection to the “socket_host” with “target_host” connected to a LAN). In this case first a socket connection is set up to the “socket_host”, and this is then continued step-by-step via the “proxy_host” on to the “target_host”. A prerequisite for this is that the InfoBroker is available on every system of the connection chain.
PAGE 149
GXCC Function bar Buttons at the bottom of the screen OK Establishes a connection to the ISP selected in the lise. If the unit address was only entered in the entry field, it will not be incorporated in the list. Add Adds the entered unit data to the list. Remove Removes the selected entry from the list. Replace Replaces the selected entry in the list. Help Opens a text window which contains Help information.
PAGE 150
Function bar GXCC 6.2.4 Options Allows you to set the window size and the page ratio. When defining the graphic display settings, it is recommended that you stop the Autoscan process (see the section “Start Autoscan/Stop Autoscan” on page 152), since otherwise the display will always return to the original settings. If GXCC is running under the control of a profile file that has been explicitly specified, all changes made using the “Options” and “Autoscan” functions will be saved to this profile file. 6.
PAGE 151
GXCC Function bar Customer Name This field contains a customer name that is a maximum of 60 characters long and which can be edited in User or Service mode. Special characters " \ $ [ ] ' will be replaced by underscores “_”. Each time a change is made to the string and the OK button is clicked, the information is saved on the monitored system. If this field is deleted GXCC uses a default name which depends on the system type.
PAGE 152
Function bar GXCC 6.2.5 Autoscan 6.2.5.1 Start Autoscan/Stop Autoscan An Autoscan is a process by means of which information is transferred periodically from the InfoBrokers to GXCC, and the graphical display is subsequently updated accordingly. It is either active (started) or inactive (stopped), its status indicated by the color of the text in the bottom right-hand corner of your screen. Green means that the Autoscan process is active, in which case the function bar offers the “Stop Autoscan” function.
PAGE 153
GXCC 6.2.5.2 Function bar Settings The slider controls the Autoscan interval for exchanging information with the InfoBroker. An Autoscan cycle consists of data transfer, display generation and autoscan delay. The default setting is “Self Adjusting”. In this mode, the interval is automatically adapted to the number of objects to be displayed, and varies between 4 and 20 seconds. By selecting “Manual Adjusting” and moving the slider, you can also set the Autoscan interval manually.
PAGE 154
Function bar GXCC 6.2.6 Tools The following functions are offered: – – – – – 6.2.6.1 Global Status Get Remote/Expand Local File Show Remote File Show System Messages GXCC Update/Revert Tool (only offered to authorized users) Global Status This function is used to call the Global Status Monitor (for a description see the chapter “Global Status” on page 237) on the connected CentricStor. 6.2.6.
PAGE 155
GXCC Function bar The window contains the following fields: Remote Host / IP-Address [Description]: Name or IP address of the remote system together with an optional comment. Remote User: Remote system user ID under which file transfer is performed. Remote Password: Password (not visible) for the remote system ID under which file transfer is performed. Remote File: Path and name of the remote file. Local File: Path and name of the local file (created from the remote file).
PAGE 156
Function bar GXCC Browse Local Opens a dialog box in which you can select and open a local file for the “Expand Local” function. Help Opens a window with help information. Cancel Closes the menu. 6.2.6.3 Show Remote File Opens a menu consisting of several entry fields, a message window, a list box and various buttons: In this window you can transfer a file from a remote system to the local system and view it using a file viewer.
PAGE 157
GXCC Function bar Remote Password Password (not visible) for the remote system ID under which data transfer is performed. Messages Field used to output messages from the components involved in file transfer. The following text colors are used: black and green for the process sequence, red for errors, and (in the event of errors) blue for associated messages resulting from platformspecific system calls or from the file transfer protocol.
PAGE 158
Function bar 6.2.6.4 GXCC Show System Messages Opens a text window to display the ISP system messages. The window is automatically positioned on the last outputs. The console messages of all CentricStor systems are listed by priority and in the order in which they occurred. You can also display the system messages by clicking the symbols in the title bar.
PAGE 159
GXCC Function bar DateTime Date and time in the form YYYY-MM-DD HH:MM:SS. ISP-Name Name of the ISP from which the message originates. Separator One or two characters (for their meaning see page 441) Message text In addition to the functions available in all text windows, the function bar of the system message window also contains “AutoUpdate” and “AutoPopup”. These functions of the text viewer are described on page 362. i 6.2.6.
PAGE 160
Function bar GXCC i If the online manuals have to be updated as well, the manuals are transferred in the background after the program files. If the transfer is completed successfully, the new manual is activated automatically and the older edition deleted. Thus, if you do not activate a new software version immediately, it can happen that the online manual is more up to date than the user interface software.
PAGE 161
GXCC Function bar Carrying out a software update When you choose the menu command, the following window appears: A list of the GXCC versions in existence is displayed in the upper part of the window, starting with the most recent version. The version of GXCC (or XTCC) that they are currently using is displayed in the first line of the “Dialog” box. “Revert” reverts to the status brought about by the initial installation.
PAGE 162
Function bar GXCC A monitor program keeps track of all the GXCCs and their ramifications. It initiates the termination of subapplications and brings it to your attention if other users are also using GXCC. The lower half of the screen contains the output area “Dialog”, which displays the update status and context-sensitive instructions, and an input area for messages to other GXCC users.
PAGE 163
GXCC Function bar Help Opens a text window containing help information. This is also an active GXCC/XTCC application, and it is thus closed when the update operation is executed. You thus cannot keep the window open during the update. This should not be a problem because there are context-sensitive explanations and instructions given, where necessary, in the dialog box. Cancel Terminates the update tool.
PAGE 164
Function bar GXCC ● You restart again. This time the process ends with the green message “Update done”. ● It now makes sense to terminate the update tool by means of the “Cancel” button. The service that monitors all the applications of the GXCC/XTCC family is thus restarted with the updated version the first time one of these applications is started.
PAGE 165
GXCC Function bar Procedure If you were able to start the tool, first a window will open which explains the further procedure. This procedure consists of the following steps: 1. Select the component to be repaired: GXCC or XTCC 2. Select the remote system from which the compressed archive of the selected component is to be fetched. 3. Execute the “Get Remote / Expand Local File” tool: Here only the “Remote Password” need be entered; all other parameters are already specified and may NOT be changed.
PAGE 166
Function bar GXCC 6.2.7 Configuration PVGs and LVGs can be configured, i.e. created, modified and deleted, in User mode. Changed parameters are stored in the file /usr/apc/broker/vtls_vg.conf.new. The floppy disk symbol appears in the CentricStor main window. The changed data is activated using the “Distribute and Activate” function. i Changes to the LVGs affect VLM and PLM, changes to the PVGs affect only thePLM. These components are stopped and restarted during “Distribute and Activate”.
PAGE 167
GXCC Function bar ➟ Configuration menu on the function bar Clicking the “Configuration” button in the toolbar opens a drop-down menu with the following items: – RAID Filesystems – Logical Volume Groups – Physical Volume Groups – Distribute and Activate Selecting the required function provides access to a series of dialog boxes for displaying and setting the configuration parameters.
PAGE 168
Function bar GXCC Elements of the configuration dialog boxes Command buttons along the lower border: All dialog boxes used to change the configuration have the same set of buttons: OK Temporarily saves your changes to /usr/apc/broker/vtls.conf.new or /usr/apc/broker/vtls_vg.conf.new and ensures that they are taken into consideration in the other dialog boxes of the configuration group. If the …conf.
PAGE 169
GXCC Function bar List editor The following example displays a configuration dialog box containing two lists: Several objects of the same type often have to be defined at configuration (e.g. Virtual Library Servers, PVGs, LVGs). The list editor in the configuration dialog boxes is used for this. An editor area consists of a list of the objects already defined and a number of elements such as display windows, text entry fields, command buttons and radio buttons.
PAGE 170
Function bar GXCC Adding a new object: Click the “NEW” button. An empty entry field appears in which you can enter a name. Depending on the type of the object, further entry fields will also be displayed. These are filled with defaults wherever this is possible or useful. If you enter a formally correct text in the name field and then display it by pressing the Return key or by clicking another field or button, the new object is defined.
PAGE 171
GXCC 6.2.7.1 Function bar RAID Filesystems After you have selected this function a form for configuring the RAID system is displayed: In Observe and User mode the OK button is not present and all the checkboxes are disabled. Buttons Disable caches Some tests on empty file systems and consistent LVG assignments are skipped (no) or executed (yes). FC redundancy (appears only if the function is installed in CentricStor) Here you can enable or disable the FC redundancy function in CentricStor.
PAGE 172
Function bar GXCC Information Mirroring Whether the mirror function is enabled or disabled in CentricStor is specified here. i The attributes of a RAID system with the mirror function enabled, whether and how it is mirrored, are defined by the assignment of the LUNs during RAID configuration. Configuration window In the table the columns represent the RAIDs and the rows represent the LUNs (the rows can also contain disk numbers in the case of internal RAIDs).
PAGE 173
GXCC Function bar Key Status The meaning of the various colors and checkbox conditions is explained. The cells also contain a summary (e.g. “mounted 85”). Command buttons along the lower border Cancel Closes the window. Reset The setting is reset to the value when the window was opened. The window remains open. Help Shows a help file. 6.2.7.2 Logical Volume Groups In this step at most 512 LVGs can be incorporated in CentricStor.
PAGE 174
Function bar GXCC Buttons and entry fields i In the case of LVGs already distributed with “Distribute and Activate”, the “To Be Deleted” button is offered (as in the form above), in the case of newly entered LVGs the “DELETE” button. The “BASE” LVG is always present and cannot be deleted. The transfer LVG with the name TR-LVG is also always present, but not shown in this menu. “NEW” button: Adds a new LVG. When you click on “NEW” the entry field for the name is opened.
PAGE 175
GXCC Function bar “DELETE” button: Appears only if a line is selected and the selected LVG has not yet been made known to the system. This is typically the case if you have just created an LVG and have not yet selected “Distribute and Activate”. Not to be confused with the “Delete LVGs” function (for details see “Input areas” ➟ “To Be Deleted”). Deletes the selected LVG. An LVG entry can only be removed with “Delete” if the configuration has not yet been activated with “Distribute and Activate”.
PAGE 176
Function bar GXCC take no action. Once the request to delete an LVG has been successfully issued and activated in the system, the action is an asynchronous action and cannot be influenced by the user. Name Name of the LVG. The data of the LVG is kept under this name in CentricStor. The LVG is defined by entering a name. The name contains a maximum of 6 characters (only letters, numbers and “_”). This field can only be modified until the LVG has been activated using “Distribute and Activate”.
PAGE 177
GXCC Function bar Further information Reducing the LV size of an existing LVG: It is not possible to reduce the LV size of an existing LVG in CentricStor. If you want a smaller LV size, you must create a new LVG with the required LV size. The data which was written to the large LVs must then be written to the new, smaller LVs using the customer’s (or customer system’s) backup tools (host resources).
PAGE 178
Function bar GXCC Erase Scratch LVs This specifies how the data of scratch volumes is to be handled: ENABLED Only the stub data (volume header) is to be retained. CAUTION! With this setting it must be assumed at all times that the data on scratch volumes - and also on the physical volumes - will automatically be deleted and consequently be irretrievably lost. This behavior was implemented as the default in early CentricStor versions without the option of changing it by means of configuration.
PAGE 179
GXCC Function bar Command buttons along the lower border OK Accepts the entry. It becomes effective with “Distribute and Activate”. The “Configuration Changed” symbol (floppy disk symbol) appears in the GXCC main window. The changed configuration data is stored, even after GXCC has terminated. If the InfoBroker is restarted or the VLP is shut down without a preceding “Distribute and Activate”, the data which was changed is lost. Cancel Closes the window without accepting the entries.
PAGE 180
Function bar GXCC The settings for the cache file system can be modified later at any time. After a modification a “Distribute and Activate” operation is required in which, however, only the VLM and the PLM must be restarted if this was the only change. If assignments between cache file systems and LV groups are modified, this can result in certain logical volumes having to be moved from one cache file system to another because the old assignment no longer applies.
PAGE 181
GXCC 6.2.7.3 Function bar Physical Volume Groups In this window volume groups of the physical volumes can be created, deleted or modified. When the window is called the existing physical volume groups are initially displayed: i In the case of PVGs already distributed with “Distribute and Activate”, the “To Be Deleted” button is offered (as in the form above), in the case of newly entered PVGs the “DELETE” button. The “BASE” PVG is always present and cannot be deleted.
PAGE 182
Function bar GXCC List area At the top of the form there is a list area with data regarding PVGs that have already been integrated. The following is displayed: Name Type Tape Library Comment To Be Deleted Name of the PVG Type of the PVG Tape library assigned Comment Marking for deleting the volume group You mark a line by clicking on it. The data of the selected PVG is presented in the entry fields and buttons below. When you change the group selection the contents of the entry fields are buffered.
PAGE 183
GXCC Function bar “DELETE” button: Appears only if a line is selected and the selected PVG has not yet been made known to the system. This is typically the case if you have just created a PVG and have not yet selected “Distribute and Activate”. Not to be confused with the “Delete PVGs” function (see below: “Entry area” ➟ “To Be Deleted”). Deletes the selected PVG. A PVG entry can only be removed with “DELETE” if the configuration has not yet been activated with “Distribute and Activate”.
PAGE 184
Function bar GXCC Tape Library The volumes of the group are stored in this physical archive. The archives defined in the configuration are offered. This field can be changed only until the PVG has been activated using “Distribute and Activate”. Type Type of the PVG. A PVG can be of the type “STACKED” or “VAULT”. STACKED means that no external influence on the PVs is possible. VAULT means that logical deletion or reentry of PVs in CentricStor is possible. The default settting is “STACKED”.
PAGE 185
GXCC Function bar Reorganisation Parameters PLM Refresh Interval (Days) Number of days after which this group’s volumes are to be refreshed. This value must be defined in accordance with the tape manufacturer’s recommendations. Value range: min: 90, max: 999, default: 365 Absolute Minimum (Volumes) Absolute minimum number of free volumes. When this minimum is reached all resources are used with priority for reorganization. The following hierarchy applies: Soft Minimum > Hard Minimum > Absolute Minimum.
PAGE 186
Function bar GXCC Write Throughput (MB/sec) Write Overhead (sec) The PLM uses the Write Throughput and Write Overhead parameters to select the physical volume which it can release in the shortest time in the event of a reorganization. Write Throughput specifies the estimated write performance of the write drive in MB/sec, Write Overhead the estimated overhead in seconds per volume to be written.The values proposed should be changed only by an expert who is fully aware of the effects of the settings.
PAGE 187
GXCC Function bar Creating a new physical volume group A new PVG is created by clicking on the NEW button. In the PVG list an empty line is opened and highlighted. All editing fields except for “Name” and “Comment” are filled with default values. The physical volume group is set up by entering a name in the text field provided. In addition, the location must be selected from the “Tape Library” drop-down menu. In each CentricStor the PVG “BASE” is permanently specified.
PAGE 188
Function bar 6.2.7.4 GXCC Distribute and Activate Then Distribute and Activate function is normally called after a change has been made to the configuration. The changed configuration files are distributed to all the CentricStor processors. The software licenses in the VLP are distributed as required. Options for “Mode” Activate_pending_config This setting is always selected by default. It causes the current configuration changes to be distributed and activated.
PAGE 189
GXCC Function bar Buttons OK If the configuration data is correct, a security query is displayed. When you acknowledge this, “Distribute and Activate” is executed. The new configuration data is distributed to all ISPs. Depending on the type of change CentricStor processes are stopped and restarted. The connection to the InfoBroker is retained. If the configuration of the FC boards of an ISP has been changed, this ISP is rebooted. Cancel Closes the message window. “Distribute and Activate” is not executed.
PAGE 190
Function bar GXCC Notes on naming the configuration files The active configuration files /usr/apc/conf/vtls.conf and /usr/apc/conf/vtls_vg.conf are renamed in all ISPs of the CentricStor to /usr/apc/conf/vtls.conf.yyyymmddhhiiss and /usr/apc/conf/vtls_vg.conf.yyyymmddhhiiss ( yyyymmdd = YearMonthDay, hhiiss = HourMinuteSecond). The working files /usr/apc/broker/vtls.conf.new and /usr/apc/broker/vtls_vg.conf.new are transferred to the active configuration files /usr/apc/conf/vtls.
PAGE 191
GXCC Function bar 6.2.8 Profile The term “profile” encompasses the following: – – – the settings chosen under “Options” the settings chosen under “Autoscan” the window size and position as set using the graphical user interface The screen size can be predefined as a start parameter (-size). All other options are set to their default values by GXCC on startup. 6.2.8.
PAGE 192
Function bar GXCC Buttons at the bottom of the screen section OK Applies the selected profile file. The display is immediately adapted to the new profile settings. The newly selected file is shown at the bottom of the GXCC screen. All changes to the profile data for the current session are recorded in this file. Add The file name specified in the editing field is added to the list and is also displayed at the bottom of the GXCC screen. From now on, profile data is saved to this file.
PAGE 193
GXCC Function bar 6.2.9 Administration The following functions are offered: – – – – – – – Show WWN’s Show Optional Functions Show CS Configuration Diagnostic Snapshots Logical Volume Operations 1 Physical Volume Operations 2 Setup for accounting mails 1 If the VLM is not running, this menu item is displayed against a gray background and cannot be selected. 2 If the PLM is not running, this menu item is displayed against a gray background and cannot be selected.
PAGE 194
Function bar GXCC Depending on authorization and/or the version of the connected CentricStor system, individual menu items are not available.
PAGE 195
GXCC 6.2.9.1 Function bar Show WWN’s The following information is listed for all ISPs: the IP addresses, the World Wide Node Names, the World Wide Port Names and the connection number of the FC connections to the FC switches of all FC controllers.
PAGE 196
Function bar 6.2.9.2 GXCC Show Optional Functions The optional functions (licenses which must be released using a key) are listed in a text window with a note indicating whether or not they are licensed and installed in this system. Example i 196 Subsequent installation of individual keys is performed under SINIX-2000-Z using SYSADM.
PAGE 197
GXCC 6.2.9.3 Function bar Show CS Configuration This function outputs the contents of the configuration files /usr/apc/conf/vtls.conf, /usr/apc/conf/vtls_vg.conf and, if present, /usr/apc/conf/vtls_add.conf. Example 6.2.9.4 Diagnostic Snapshots This function is not offered in Observe mode. This function performs a similar task to the vtrc script, but in contrast to vtrc permits selection of the ISPs on which the function is to be performed.
PAGE 198
Function bar GXCC Create snapshot(s) When you select this function, the “Diagnostic Snapshots” window is output which contains an overview of all ISPs in the system and the Diagnostic Snapshots there: The columns contain the following information: 198 ISP Name Names of the ISPs # of existing snapshots Number of snapshots which already exist on this ISP total size of snapshots (MB) Total memory space in MB occupied by the snapshots saved on the ISP date and time of last snapshot Date and time of
PAGE 199
GXCC Function bar “Create Snapshot(s)” button: If you have switched the “new snapshot to be created” option to “yes” (default: “no”) on the ISPs concerned and then press the “Create Snapshot(s)” button, the snapshots are generated and saved on the selected ISPs. The system acknowledges the user input with an information window containing a list of the selected ISPs and the name of the directory in which the snapshot files are saved.
PAGE 200
Function bar GXCC Show survey / Delete snapshots This function outputs the “Show List of Snapshots” window: The window contains a list of all snapshots in the system. The most recent snapshot is contained at the top of the list, the oldest at the bottom.
PAGE 201
GXCC Function bar “Delete Snapshot(s)” button: Clicking on this button causes all snapshots which are marked with “yes” to be deleted. The system acknowledges the user input with an information window containing the information ”snapshot(s) will be deleted”. If you press “Delete Snapshot(s)” without marking one or more ISPs beforehand, the message “no snapshots selected for deletion or deletion failed” is issued.
PAGE 202
Function bar GXCC – A routine which runs periodically checks whether the free memory in the file systems in which the snapshots are saved has fallen below the specified value. If this is the case, the oldest snapshots are deleted: either until enough free memory is available again in the file system or until only the number of snapshots defined in the field “Minimum number of snapshots, which shall be kept” (see below) are present. A “Free space threshold” value of 0 is ignored.
PAGE 203
GXCC 6.2.9.6 Function bar Logical Volume Operations » Show Logical Volumes As a CentricStor can contain up to 500 000 logical volumes selection tools are offered. A menu containing a large number of filter functions for selecting logical volumes is opened: If you use the settings in the screenshot above and click on OK, a list of all logical volumes is output which match the selected filters.
PAGE 204
Function bar GXCC Logical Volume Group You can select either a logical volume group or “all”. Volume Status With the checkboxes you can specify that only volumes with the selected status are to be displayed. If no checkbox is selected all the selected volumes of the specified volume group(s) are displayed. A message box is used to indicate whether a volume set selected in this way is empty. After you have acknowledged with “OK” you can start a new selection.
PAGE 205
GXCC Function bar The following data is output: VSN GRP C-ID SIZE ACCESS TIME STATE Volume serial number, name of the logical volume. Logical volume group. A cartridge migrated from CentricStor Version 1 belongs to the BASE group. Cache ID (this column appears only when “CacheID” has been enabled) Amount of user data on the volume (decimal, in bytes). Date and time of the last access, empty if uninitialized. State of the logical volume: Faulty Home Mounted Mount Pending Mnt.
PAGE 206
Function bar GXCC Example 2 Output window when range is set (Volume serial number: STW075; Number of volumes: 6): The meaning of the columns is explained in example 1.
PAGE 207
GXCC 6.2.9.7 Function bar Logical Volume Operations » Show Logical Volumes (physical view) You use this call to display the logical volumes which are known to the PLM together with their statuses. i You obtain statistcs on the logical volumes by calling the function of the same name for “logical view”. In contrast to the VLM call the PLM call does not permit the use of wildcards, allowing instead filtering according to PVG, LVG and tape library.
PAGE 208
Function bar GXCC The logical volumes are displayed in the following window: PLM-specific data of the LVs is output: LV LVG size save request at PV 1 PVG 1 TL 1 bl_nr 1 PV 2 PVG 2 TL 2 bl_nr 2 208 Name of the LV Name of the LV group Size of the LV Save date and time: The save request for the LV was accepted by the PLM at this time. PV on which the current map of the LV is stored. This PV is located in the PVG which is specified in the PVG 1 column. PVG to which the LV is connected.
PAGE 209
GXCC 6.2.9.8 Function bar Logical Volume Operations » Change Volume Group This function is not available in Observe mode. Changes the assignment of logical volumes to a logical volume group. i The data maintenance system of the VLM keeps a record for each logical volume, showing where it is currently stored and on which physical volume group(s) it is to be backed up, if necessary.
PAGE 210
Function bar GXCC VABC08,...,VABC031. If any volumes do not exist in the name range defined by the start name and number specifications, then this is indicated in a ready message and the operation is continued. Thus, in this example, the volumes VABC032 ff. would not be moved. This acknowledgement only indicates that the data maintenance system in VLM has been modified accordingly. The storage location of each of the volumes is only changed the next time that a save is actually performed.
PAGE 211
GXCC 6.2.9.9 Function bar Logical Volume Operations » Add Logical Volumes This function is not available in Observe mode. Input parameters Enter the following information in the dialog window: Volume Serial Number Name of the logical volume (VSN or VOLSER). Any combination consisting of a maximum of 6 characters. The following are permitted: – – Alphabetic characters in upper case. The special characters #, $, @, _, %, +, - (the plus and minus characters may not be the first).
PAGE 212
Function bar GXCC Example VXYZ21 results in an error message if Number of Volumes > 78. If an existing logical volume is to be replaced by an empty volume of the same name, it must first be deleted (see next section) and then added again. i The assignment of logical volume group to one or two physical volume group(s) is described in the section “Physical Volume Operations » Link/Unlink Volume Groups” on page 221. Buttons along the bottom border OK The add operation is started.
PAGE 213
GXCC Function bar After the function has been completed, a message box with an OK button appears: 2230 logical volume(s) added When you click “OK”, the entry form and the message box disappear. 6.2.9.10 Logical Volume Operations » Erase Logical Volumes This function is not available in Observe mode. This function enables logical volumes to be removed from the library and their contents to be deleted. Make sure that the volumes to be erased have been released from the pool managed by the host(s).
PAGE 214
Function bar GXCC Actions linked with “OK” The designated logical volumes are removed from the VLM data maintenance system. Images of the LVs on physical volumes are not deleted but merely marked as invalid. If some volumes are not contained in the specified name range, the delete operation is continued. The number of volumes actually deleted is specified in the completion message.
PAGE 215
GXCC 6.2.9.11 Function bar Physical Volume Operations This submenu offers the following functions: – – – – – Show Physical Volumes Link/Unlink Volume Groups Add Physical Volumes Erase Physical Volumes Reorganize Physical Volumes i 6.2.9.12 These menu items are offered only if the PLM is running. Physical Volume Operations » Show Physical Volumes An identical function is offered in the Global Status under “Statistics” (see page 257).
PAGE 216
Function bar GXCC Therefore, you can choose to display: – – – – – A specific physical volume (specify only the volume ID) All the volumes in a physical group (specify only the physical volume group) All the volumes in a library (specify only the library) All physical volumes (specify “all-data”) All cleaning volumes (specify “all-cleaning”) You can also set certain criteria for the display: new/forcednew Volumes that have not yet been initialized.
PAGE 217
GXCC Function bar If the query relates to multiple volumes, the following overview is displayed: Meaning of the information pos Line number PV Number of the physical volume When the number is prefixed with a plus or minus sign: + = LVs written but not yet securely on the PV - = LVs invalidated but new version not yet securely on the PV TL Tape Library: Name of the archive PVG Name of the physical volume group state Status; possible values: e___ E___ f___ f_d_ i___ n___ N___ o___ U41117-J-Z125-7
PAGE 218
Function bar GXCC _r__ _rd_ s___ _v__ _w__ _wd_ ____ Read volume on which no space is available for further data The cartridge is full but an attempt is still made to write the directory onto the tape The PV must be scanned (used for transfer).
PAGE 219
GXCC Function bar Meaning of the information: pos PV TL PVG state Line number Number of the physical volume Name of the archive Name of the physical volume group, usually starts at “CLNP”. status The following values are possible for cleaning cartridges: o___ (“scratch”) when the volume has only just been added, _r__ Read volume, has no more space for additional data. This is the normal state of a cleaning cartridge. f___ (“faulty”) when all the cleaning cycles have been used up. max.
PAGE 220
Function bar GXCC This is followed by a list of the (valid) logical volumes stored on the PV: pos LV file-Id LVG bl_nr size/MB save request at Line number Name of the logical volume Hexadecimal: internal version number in the TVC Name of the group to which the logical volume belongs Number of the first block of the logical volume on the PV Size Time at which the PLM received the save job.
PAGE 221
GXCC 6.2.9.13 Function bar Physical Volume Operations » Link/Unlink Volume Groups This function is not available in Observe mode. The assignments of LVG to one or two (with Dual Save) PVGs are established, resolved, or changed. The list in the upper screen section contains the logical volume groups. LVG PVG (Original) PVG (Copy) Name of the LVG, as defined in the configuration. Name of the originally assigned PVG, or “-unlinked-”. “-unlinked-” means that no PVG has been assigned yet.
PAGE 222
Function bar GXCC Buttons along the bottom border OK Link/Unlink is started. Cancel The window is closed without any further activity. Actions linked with “OK” 1. Before the PVG is linked, the logical volume size is checked: If the LV size is > 2 GB, the capacity of the PVs already assigned must be twice as large as the LV size, otherwise the assignment is rejected with the following message: Attempting to link PVGs (,>PVG2>) to LVG (): The capacity of the PVs of PVG is too small 2.
PAGE 223
GXCC Function bar Note for linking If practically the same number of drives is configured for the robots in dual save, restores can be optimized through the following distribution and crossed-over PVG sequence: Example of linking LVG1 PVG1 PVG2 LVG2 PVG2 PVG1 Distribution to two LVGs with a crossed-over PVG sequence ensures that all drives are available for restores. The restore times can thus be considerably reduced (but not in all cases; e.g. multiple restores of one PV). 6.2.9.
PAGE 224
Function bar GXCC Window for entering physical volumes: The form shows whether levels have dropped below the defined minimum numbers for a Volume Group. In the same way, a warning is output for cleaning cartridges when the number of cleaning cycles left drops below the defined minimum. In order to add one or more new volumes, you must make the following specifications. Volume Serial Number (First) number of the volume(s) Physical Volume Group PVG to which the volume is to be assigned.
PAGE 225
GXCC Function bar Number of Cleaning Cycles Only applies to cleaning cartridges: the number of cleaning cycles still possible for the inserted cartridge (decimal value). Flag “Omit Header Check” Only applies to data cartridges: The header of an added volume is always overwritten with a CentricStor header without exception.
PAGE 226
Function bar GXCC The PLM normally uses the cartridge with the fewest available cycles for cleaning to avoid shelves being occupied unnecessarily by partially used cartridges. An exception to this strategy is made only if multiple cleaning requests are handled simultaneously. It can take some time to complete this job. Processing takes place asynchronously. After a while it is thus, for example, advisable to check in the “Global Status” to see whether the volumes have actually been included.
PAGE 227
GXCC Function bar Option is not set: If a volume contains valid data, an error message is output and the volume is not deleted. Option is set: A “Move” is carried out automatically for volumes containing valid data. The volume is then removed from the data maintenance system. Buttons along the bottom border OK The specified volumes are removed from the PLM data maintenance system. Cancel The window is closed without any further activity.
PAGE 228
Function bar 6.2.9.16 GXCC Physical Volume Operations » Reorganize Physical Volumes This function is not available in Observe mode. It allows you to manually copy the contents of a physical volume to one or more volumes in the same physical group or to interrupt such a reorganization. After reorganization, the physical volume is empty. It is then usually available for subsequent writing by the PLM.
PAGE 229
GXCC 6.2.9.17 Function bar Setup for accounting mails i This function is displayed only if an accounting license is installed. This menu permits orders to be configured which automatically send accounting data by e-mail. ! CAUTION! sendmail must have been configured for this function to be effective) ( see section “Sendmail configuration” on page 558). Displaying input options in the list area List of Mail Orders: All orders that have already been defined are displayed.
PAGE 230
Function bar GXCC Mail Address(es): In this field the user can enter one or more e-mail addresses (separated by blanks and/ or commas) to which the accounting data is to be sent. LVGs (Logical Volume Groups): A number of radio buttons is displayed here which enable the user to define the LVGs for which accounting data is to be requested. The first button is labeled “(ALL)”. If this button is enabled, accounting data is requested for all LVGs known in the system.
PAGE 231
GXCC Function bar Send mail at : This field is used to define the time (in hours and minutes) at which the accounting data is to be sent by mail. Default: 00:00 on |: Here the user can define the day on which the accounting data is to be sent by mail. Format and default value: See above. Mail subject: Here you can enter the subject which is to be used when the mail lis sent. The system may supplement the subject specified here by the suffix “(part of )” (see “Max.
PAGE 232
Function bar GXCC 6.2.10 Help The following entries can be selected in the “Help” menu: – – – – – – – 6.2.10.1 Readme / LIESMICH Direct Help / Direkthilfe System Messages About GXCC... Revision Summary Hardware Summary Online Manual CentricStor User Guide (in Observe or User mode) or Service Manual (in Service mode). This item appears only if a suitable manual is available in the language set. Readme / LIESMICH A text window containing the CentricStor Operating Manual (README) is opened.
PAGE 233
GXCC 6.2.10.
PAGE 234
Function bar 6.2.10.
PAGE 235
GXCC 6.2.10.7 Function bar Online Manual This function starts a PDF reader and the most up-to-date version of the manual which is available is displayed in the language set. If no manual is available in the language set this menu item is omitted. When GXCC connects with a CentricStor, any more up-to-date version of the manual which is present there is automatically transferred and enabled. One of the menu items – – CentricStor Vm.n User Guide (complete) CentricStor Vm.
PAGE 236
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 237
7 Global Status 7.1 General The Global Status Monitor outputs all important operating data in graphical format, and allows you to display important system data over configurable periods.
PAGE 238
General Global Status When “Global Status” is started, a window like the one shown below will be opened: The figure above is just an example, it can be arranged as you wish. Footer The components are, from left to right: Profile Language CS Version Operating mode Size Scan Time Platform Version 238 Name of the profile file. A profile file can be selected with the -profile parameter at startup time or at any time via the function bar.
PAGE 239
Global Status Operation of the Global Status Monitor 7.2 Operation of the Global Status Monitor CentricStor comes with a performance monitor, which constantly records and saves component operating data at intervals of a few seconds. Your service staff can specify in which file system and for which time period the data is to be stored. The Global Status Monitor analyzes the performance data and displays individual readings, either as they stand at present or their course over time. 7.
PAGE 240
Function bar of the Global Status Monitor Global Status Setting options Print to – Printer Output is to a PostScript printer. After you click on the “Setup” button a window is displayed for entering the printer setup: In this form you can make the printer default settings. After you click on the “Save” button the settings are transferred to the previous window. – File Output is to a file in PostScript format.
PAGE 241
Global Status Function bar of the Global Status Monitor 7.3.2 Config “Config” allows you to control the appearance of the display. When you click on “Save” in the “Config” menu the position of the GLOBSTAT window on the screen and the position of the subwindow in this window are stored and reused each time the “Global Status” is opened again. A separate data record is created for each monitored CentricStor. “Reset” resets the screen settings to the values when the software was supplied.
PAGE 242
Function bar of the Global Status Monitor – Global Status The screen division can be set in the usual manner. Permanent recording of operating data is not affected. i Some objects are symbolized using relatively small fields, which makes it more difficult to position the mouse. The mode described here is designed to be used to record certain operating statuses and to describe these using the Balloon Help fields for the purposes of training and documentation.
PAGE 243
Global Status Function bar of the Global Status Monitor The following data is listed: Emulations Arranged according to ICP: emu/vid name lib. device virtual device mounted volume special state (emu/device) Number of the emulation (390 emulation) / LUN (FC SCSI device). Archive name/address of the device. System name of the virtual tape device. VSN of a mounted volume; empty if no volume is mounted. Status of the emulation/device; in the example, two of the emulations are running with activated trace.
PAGE 244
Function bar of the Global Status Monitor Global Status Physical Devices Arranged according to IDP: pds name scsi device manufacturer device type and model prod. rev. special state (pds/dev) Name of the PDS. CTL (controller, target, LUN) of the device. Self-explanatory Self-explanatory Firmware status Status information of PDS/device. Physical Library Processes plm process pls processes host type 244 ISP running the PLM. Name of the PLS.
PAGE 245
Global Status Function bar of the Global Status Monitor Cache Data The cache utilization data is displayed. 7.3.4 Statistics The following menu options are available: – – – – History of (page 264) Logical Components (page 267) Physical Components (page 276) Usage (Accounting)1 (page 293) Both records of operating data (history) and the current operating mode (statistics) can be displayed and sorted according to various criteria.
PAGE 246
Global Status button bar Global Status 7.4 Global Status button bar Frequently used functions can be accessed immediately after you have clicked on the relevant button: Shows all three subwindows Shows only right subwindow (physical) Shows only central subwindow (logical) Shows only left subwin.
PAGE 247
Global Status Display of the Global Status Monitor 7.
PAGE 248
Display of the Global Status Monitor Global Status You can set the visible section of the subwindow by dragging the handles on the separating lines. The visible part of the subwindow can be moved in the horizontal direction for each subwindow separately by means of the scroll bar. The boundaries between the subwindows can be fixed by clicking on the upper control points. Fixed boundaries are displayed with red control points.
PAGE 249
Global Status Display of the Global Status Monitor 7.5.1 Performance The left-hand part of the window displays the current data throughput at the external interfaces. i.e. the ESCON/FICON channels and/or FC interfaces to the hosts and the SCSI or FC controllers forthe tape drives. The display area becomes visible when the mouse pointer is positioned near the maximum display bar. The maximum bar outline is then temporarily displayed.
PAGE 250
Display of the Global Status Monitor Global Status The smaller diagrams on the right indicate the data rates via the ESCON/FICON host connections (= 390-CH) or FC host connections (=FIBRE-CH) to the virtual drives (top diagrams) and the data rates via the SCSI or FC controllers to the physical drives (bottom diagram) for each controller and transfer direction. The ICPs/IDPs are identified by their names.
PAGE 251
Global Status Display of the Global Status Monitor 7.5.2 Virtual Components The middle window section displays the current statuses of the tape emulations, the virtual devices and the occupancy of the tape volume cache(s): Emulations and virtual drives Emulations and virtual drives are displayed in the left-hand part of the picture and are arranged by ICP. Each emulation and each virtual device is represented by a box.
PAGE 252
Display of the Global Status Monitor Global Status Virtual library servers The middle column indicates the operating statuses of the VLM and virtual library servers (VLSs). If you click the left mouse button on on an object, an info box is output containing further details. In the case of control components, for example, this would indicate the host on which the component runs.
PAGE 253
Global Status Display of the Global Status Monitor Additional displays for mirrored systems ● Red bar on a cache column: The cache is no longer mirrored (“out of sync”). Left: Right: ● Primary cache Secondary cache Yellow bar on a cache column: The cache concerned is being resynchronized and is still in the “out of sync” status.
PAGE 254
Display of the Global Status Monitor Global Status 7.5.3 Physical Components This screen displays the operating status of CentricStor’s physical resources. These consist of the cartridge drives, the physical robot controllers and the physical volumes. This part of the display is not available in the evaluation model. The second example shows how the screen layout changes when there are a large number of PVGs. The display shows (from left to right) the PDS and the associated cartridge drives (pDev).
PAGE 255
Global Status Display of the Global Status Monitor drives, the PDS, the PLS, and the PLM are color-coded in accordance with the key displayed at the right-hand edge of the screen section. Left-clicking on an object causes information to be displayed. The address (host name or SCSI Controller:Target:LUN) of the access system is specified at the top of the box.
PAGE 256
Display of the Global Status Monitor i Global Status Newly added volumes are not available until they have been initialized by the PLM. The height of the bar represents the number of volumes. If less volumes are available than the minimum values usually displayed for “Hard Minimum” and “Soft Minimum”, then the minimum values cannot be displayed using this form of representation and thus do not appear on the diagram. This situation occurs regularly when the PVG is being filled.
PAGE 257
Global Status History data 7.6 History data History data is system data which has been collected over a lengthy period. For this purpose a Performance Monitor constantly runs in CentricStor. The Performance Monitor collects and stores the operating data of the components, e.g. performance, mount, availability of the devices and the device assignment, at intervals of a few seconds. The customer service can determine the files system and period in which measured data is to be saved.
PAGE 258
History data Global Status 7.6.1 General 7.6.1.1 Recording analog operating data If you move the mouse to a Global Status display and click on the right button, “Show Statistics” is offered. When you select this function a window opens for presenting the chronological progress. A description of how to operate this is provided on page 262.
PAGE 259
Global Status Measured value History data Type Call Description Scratch Volumes of H a PVG Object: PVG column in right-hand part of screen page 313 Cache Usage H Object: Cache column in central part of screen page 265 Usage of Overall Cache H Statistics » History of » Cache Usage or page 265 Object: Column for overall cache in central part of screen Throughput of a PDS or Host Adapter H Object: Column for PDS or host adapter of page 304 an ICP in left-hand part of screen Overall Throughpu
PAGE 260
History data 260 Global Status Measured value Type Call Description Physical Volume Groups Tape Statistics H Object: PVG column in right-hand part of screen page 313 Physical Volumes Occupancy T Statistics » Physical Components » Physical Volumes page 279 Reorganization Status T Statistics » Physical Components »Reorga- page 291 nization Status Usage (Accounting) T Statistics » Usage (Accounting) page 293 U41117-J-Z125-7-76
PAGE 261
Global Status History data By System By PVG By cache By IDP By ICP By Device Channel Min/Max/Aver.
PAGE 262
History data 7.6.1.3 Global Status Selecting the time period The recording period or analysis period must be selected for displays of the type H. When you have selected one of these displays a window with an empty page appears. The function bar contains tools for defining the time period (day, time, range). The period selected (day, time, range) is displayed in a small field below the button bar. The default value is “the last 24 hours” or “the current hour”.
PAGE 263
Global Status History data The button bar below these options allows you to select the functions “Exit” and “Redraw”: Redraw: Draws the diagram with the current settings Exit i If you have selected a long recording period (e.g. months) a very large volume of data must be analyzed and transferred. In the wait time you are offered an info box containing the “CANCEL” button. You should click on this button if you have accidentally selected this long recording period.
PAGE 264
History data Global Status 7.6.2 Data which can be called via the function bar The following menus and submenus can be called under “Statistics”: 7.6.2.1 ● History of – Cache Usage (page 265) – Channel/Device Performance (page 266) ● Logical Components – Logical Drives (page 268) – Logical Volumes (physical view) (page 271) – Logical Volumes (logical view) (page 272) – Logical Volume Groups (page 273) – Jobs of Logical Vol.
PAGE 265
Global Status 7.6.2.2 History data Statistics » History of » Cache Usage The history of cache usage is output in accordance with the cache total values of the virtual components subwindow.
PAGE 266
History data 7.6.2.3 Global Status Statistics » History of » Channel/Device Performance Statistics on the overall throughput as they are presented continuously in the left-hand bar of the Performance subwindow are output. You can use the four checkboxes at the lower edge of the screen to determine what data is presented. The following options are offered: Channel Read/Write (also for FC host adapters): Front-end throughput. Device Read/Write: Back-end throughput.
PAGE 267
Global Status 7.6.2.4 History data Statistics » Logical Components The following submenus are available: – – – – – Logical Drives (page 268) Logical Volumes (physical view) (page 271) Logical Volumes (logical view) (page 272) Logical Volume Groups (page 273) Jobs of Logical Vol. Groups (page 275) i Notes on the refresh function: All statistics functions support the refresh function: After the function has been executed, i.e.
PAGE 268
History data 7.6.2.5 Global Status Statistics » Logical Components » Logical Drives i You obtain statistics on the utilization of the logical drives by selecting an ICP in the central section of the Global Status display and calling the object-related statistics function. Displays the occupied status of the logical drives. You can select drives in particular statuses using a selection window: i This statistics function supports the refresh function.
PAGE 269
Global Status History data The list of logical drives is output in a text window after you click on the “OK” or “Refresh” button: The following information is output: VSN VSN of the volume mounted in a drive or “Empty” GRP LVG of a mounted volume or C-ID Number of the cache (=Cache-ID) to which the mounted volume is assigned or SIZE Size of the data contained in the volume or ACCESS TIME Timestamp of the last access or STATE Faulty Home Mounted Mount Pending Mnt.
PAGE 270
History data Global Status Rest. Canc. Unld. Pend. The reading in of the logical volume by the physical volume was canceled (occurs with a scratch mount). The logical volume has just been ejected from a logical drive (emergency unload). There is still no confirmation for this. FLG Flags: D “dirty”: M “migrated”: The volume is located in the cache but has not been saved since the last change.
PAGE 271
Global Status 7.6.2.6 History data Statistics » Logical Components »Logical Volumes (physical view) You use this call to display the logical volumes which are known to the PLM together with their statuses. The right-hand part of the window displays all the output data in tabular form.
PAGE 272
History data Global Status The columns of the distribution table contain the associated values of the distribution parameters. The columns containing the number of LVs to which the various distribution parameter values relate and their percentage share in the total quantity are also visible. The pie chart is a graphical presentation of the distribution table. Clicking on a pie segment or a line in the distribution table highlights the related entries in the overall data table. 7.6.2.
PAGE 273
Global Status 7.6.2.8 History data Statistics » Logical Components » Logical Volume Groups If multiple logical volume groups exist an intermediate menu is then displayed for selecting the volume group: i This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on page 267. You can select either all groups or a specific group.
PAGE 274
History data Global Status After you click on “OK” or “Refresh” the following window appears: The following data is displayed: pos LVG PVG1 PVG2 LVs pending jobs recover jobs lv-size 274 Line number Name of the logical volume group Name of the first or only assigned physical volume group, or -===== if empty Name of the second assigned PVG (if assigned - Dual Save), or -===== if empty Number of logical volumes in this group Number of jobs which the PLM has accepted for this LVG.
PAGE 275
Global Status 7.6.2.9 History data Statistics » Logical Components » Jobs of Logical Volume Groups If CentricStor contains more than one logical volume group (LVG) the required group is entered using an intermediate menu: i This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on page 267. If only one group is defined this intermediate step is skipped.
PAGE 276
History data Global Status Meaning of the columns: The job data (result for ... :) is output separately for each LVG. pos 7.6.2.10 Serial number LVG Name of the logical volume group PVG 1 Name of the first assigned physical volume group If '======' is specified as the name, no PVG is assigned to the LVG. PVG 2 Name of the second assigned physical volume group If '======' is specified as the name, only a single save is performed for the LVG (no Dual Copy).
PAGE 277
Global Status 7.6.2.11 History data Statistics » Physical Components » Physical Drives First of all the library involved is queried: If only one tape library exists, the name of this tape library appears here. i This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on page 276. The library required is selected via the drop-down menu.
PAGE 278
History data state Global Status Current status of the drive. Possible values: unused occupied disabled unreachable dis./unreach. Free, no PVG assigned Occupied; where relevant, the next columns show the name of the mounted volume, the PVG, and the job status. Not used, possibly faulty The PDS cannot be reached. The PDS is disabled and cannot be reached. PV VSN of the physical volume PVG Physical volume group job state Status of the ongoing operation.
PAGE 279
Global Status History data timestamp Time at which the current status was entered. i 7.6.2.12 If you right-click on a library in the right-hand part of the Global Status screen and select “Show Statistics” you are shown an overview of the drive utilization in graphical and table form. Statistics » Physical Components » Physical Volumes Depending on the setting of the volume selection an overview of one or more physical volumes and a statistical analysis are displayed.
PAGE 280
History data Global Status An overview in table form is then shown Meaning of the columns: 280 pos Line number PV Number of the physical volume TL Tape Library: Name of the archive PVG Name of the physical volume group state Status; possible values: e___ Volume ready for invalidation. E___ The PV is reorganized and then invalidated. f___ An error occurred while working with this tape. It is not reused and automatically reorganized.
PAGE 281
Global Status History data s___ _v__ _w__ _wd_ ____ The PV must be scanned (used for transfer). The PV is in “vault” state. Write volume that can still be used for save operations. The cartridge is not yet full; currently there is no directory on the tape. The state is unknown (used for Transfer-In). next-bl Block number of the free range. This indicates the physical utilization level.
PAGE 282
History data Global Status Meaning of the columns: pos PV TL PVG state Line number Number of the physical volume Tape Library: Name of the archive Name of the physical volume group, usually starts at “CLNP”. status The following values are possible for cleaning cartridges: o___ (“scratch”) when the volume has just been added. _r__ Read volume, has no more space for additional data. This is the normal state of a cleaning cartridge. f___ (“faulty”) when all the cleaning cycles have been used up. max.
PAGE 283
Global Status History data Meaning of the columns: pos LV file-Id LVG bl_nr size/MB save request at Line number Name of the logical volume Hexadecimal: a type of version number in the TVC Name of the group to which the logical volume belongs Number of the first block of the logical volume on the PV Size Time at which the PLM received the save job. This timestamp allows the Disaster Recovery mechanism to identify which of the various different copies of a logical volume is the most recent.
PAGE 284
History data Global Status When you select all data PVGs the following overview is displayed: Meaning of the columns: pos PVG Type PVs scratch LVs TL jobs (wait-work) Reorg.
PAGE 285
Global Status History data available/used cycles Number of available cleaning cycles for the physical volumes / number of cleaning cycles which are executed. TL The tape library. jobs (wait-work) Number of waiting jobs / number of working jobs.
PAGE 286
History data Global Status PVG statistics are displayed in the first line. Name Meaning Example PVG Name AMLG1 Type Type of the PVG stacked PVs Number of physical volumes 30 scratch Number empty 19 LVs Number of logical volumes 2066 TL Tape Library: Name of the archive AML jobs (wait-work) Number of jobs in queue or being processed Reorg.
PAGE 287
Global Status History data number of parallel requests to VLM (REORG) Number of “Move Requests” to be processed simultaneously which the PLM sends to the VLM for the purpose of reorganizing PVs. The higher this value, the more resources are reserved by the reorganization. cancel time for REORG If a move request issued by the PLM to the VLM remains in an unchanged status beyond this time it is canceled by the PLM. This does not apply for a PV reorganization started by an operator command.
PAGE 288
History data Global Status time slice for PDS-scheduler Time in seconds for which a PDS remains assigned to a PV group. After this time has elapsed an active job is terminated and the drive may be unloaded. Depending on the load situation it is then assigned to another PVG. The value must be greater than or equal to 600 seconds. Assignment of the physical drives to the PVGs can be controlled by different sized time slices. The larger the time slice of a PVG, the greater its share in the use of the drives.
PAGE 289
Global Status 7.6.2.14 History data Statistics » Physical Components » Jobs of Physical Vol. Groups A window for selecting one or all PVGs is opened: i This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on page 276. The job data for the selected group(s) is displayed: The top part of the text field shows the jobs that are being processed, the lower part the queue.
PAGE 290
History data Global Status type Type of job ERASE INIT INITNEW RDIR REST SAVE UNLOAD WDIR Invalidate PV header Load and initialize PV Add new PV, write header Reads the directory. Restore an LV from the physical tape to the “Tape Volume Cache” Save an LV from the “Tape Volume Cache” to a physical type Unload PV from PDS Writes the directory. PDS The name of the PDS which processes the job. As long as a job is in the queue and no PDs is yet assigned to it, this column contains ’======’.
PAGE 291
Global Status 7.6.2.15 History data Statistics » Physical Components » Reorganization Status A window for selecting one or all PVGs is opened (naturally the clean PVGs are not offered): i This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on page 276. If only one group is defined this intermediate step is skipped.
PAGE 292
History data Global Status Otherwise the status of the reorganization of the physical volume group(s) is displayed: Meaning of the entries: no.
PAGE 293
Global Status History data The frequent occurrence of retries can also indicate that the reorganization times coincide with peak loads. In this case the reorganization times should be moved (“Scratch Time Frame” field, see the section “Physical Volume Groups” on page 181). More detailed information on the retry causes is provided in the system messages (see the section “Show System Messages” on page 158). 7.6.2.
PAGE 294
History data Global Status Selection fields Accounting data requested for Here you can choose between the following options: all_LVGs The accounting data for all LVGs in the system is output. selected_LVGs Initially all the LVGs known in the system are displayed as check buttons. Example You can then select those LVGs whose accounting data you are interested in.
PAGE 295
Global Status History data Accounting Data When you click on the “OK” button the account information is displayed in a text field (here with the option “Data fields to be separated by white space”): The data is output in the following form for each CentricStor computer: ● Title “Accounting Data for CentricStor ” ● Subtitle Date and time and format of the output U41117-J-Z125-7-76 295
PAGE 296
History data ● Global Status Table One or more tables with the accounting data depending on whether the data for all, for one or for multiple logical volume groups (LVGs) was requested. Each table consists of the following: – Title all LVGS LVG – Display of all LVGs Display of the selected LVG Columns The individual columns are separated by white space or commas (no white space) .
PAGE 297
Global Status History data 7.6.3 Data which can be called via objects of the Global Status The chronological progress and statistical data can be displayed via some Global Status objects. To do this position the mouse cursor over the object. If data is present for the object, this is indicated by a blue border or the device designation is colored blue. If you press the right mouse button a context menu with the menu item “Show Statistics” is opened.
PAGE 298
History diagrams Global Status 7.7 History diagrams After a statistic has been selected, first of all a window with an empty page appears. The window is structured as follows: Menu bar Toolbar Title bar Page Legend bar Status line 7.7.1 Function/menu bar 7.7.1.
PAGE 299
Global Status History diagrams Export This function causes the history data to be read in as specified by the current settings. The data is then written to a file. Details on this are provided in the section “Exporting history data” on page 314. Print Prints the chart or saves the print image to a file. If Global Status is running under Windows it is advisable to use the print function button (page 246). This opens the usual Windows print menu.
PAGE 300
History diagrams Global Status Orientation You use “Orientation” to select “Portrait” format, “Landscape” format or “Auto” (automatic adjustment). Paper Here you can select “A4” or “letter”. Mode Setting options: “color” or “grayscale” Buttons along the lower border Print Printout takes place with the values set. Help A help text is output. Default Saves all current settings. Cancel The window is closed without the changes being accepted. Exit This closes the window. 7.7.1.
PAGE 301
Global Status 7.7.1.3 History diagrams Time A pull-down menu with the values 0 - 23 is opened in which you can define the start time for a display area. After you have clicked on the required time, the window is closed and the value selected is taken over. 7.7.1.4 Range A pull-down menu is opened in which you can define the the display period: The duration of the display period is defined with the values at the bottom.
PAGE 302
History diagrams 7.7.1.7 Global Status Profile Profile enables the current settings, e.g. for the analysis period, to be stored and reused the next time the program is called. Specifically this means: – – – Managing profiles (submenu: Add/Select Profile) Importing options from a profile file (submenu: Add/Select Profile) Storing options in a profile (submenu: Save) Automatic storing/import: When the Viewer has been terminated, the current settings are saved in the current profile.
PAGE 303
Global Status History diagrams 7.7.
PAGE 304
History diagrams Global Status Host adapters For each host adapter a column showing the current throughput for read and write operations of the host - arranged according to ICP - is displayed in the upper half of the left-hand subwindow. As described above, you can have the chronological progress of these values displayed for each host adapter. Mode selection (max, min/max or average, see section “Selecting the presentation mode” on page 263) is supported.
PAGE 305
Global Status History diagrams 7.7.5 Diagrams for virtual components (central part of the screen) 7.7.5.1 ICP emulations A distinction must be made here between whether the readlog or getlog protocol is being used on the connected CentricStor. This depends on the CentricStor version currently installed: = V3.1D: < V3.
PAGE 306
History diagrams Global Status Outputs for CentricStor V3.1D or higher (get_log protocol) The following diagrams are offered depending on the mode selected (see the section “Mode” on page 301): ● Mount state diagram The mounted state is displayed for each emulation/PDSs in the selected period.
PAGE 307
Global Status ● History diagrams Mount summary diagram The number of emulations/PDSs in the mounted state at any given time is shown here.
PAGE 308
History diagrams Global Status Outputs for CentricStor < V3.1D (read_log protocol) Slider i If more than 16 emulations are defined, a slider is displayed in the button bar. You can use this to select which group of 16 emulations is to be displayed. The presentation period is set permanently to one hour. The key at the bottom of the window describes the meaning of the colors of the lines in the picture, i.e. statuses. The percentage share of each status in the period shown is also displayed.
PAGE 309
Global Status 7.7.5.2 History diagrams Cache Usage The progress of the cache usage can be displayed for each individual cache file system or for all caches together. To do this, right-click on the relevant cache column in the central section and select “Show Statistics” in the context menu. After you have specified the required time period you are shown a presentation of the cache usage: The color presentation of the cache statuses in your system may differ from this example.
PAGE 310
History diagrams Global Status Meaning of the statuses free Not used. This area can be used immediately for saving volume images. clean Contains valid volume images. The volumes are unchanged compared to their images saved on tape (either not yet written or already saved). If another mount takes place for a volume from this area, this can be performed without a delay. If the storage space is required for other volumes, it can be used without delay. used In use.
PAGE 311
Global Status History diagrams Example for V3.
PAGE 312
History diagrams Global Status Example for < V3.1D The presentation period is set permanently to one hour. Each line pair shows the status of the PDS (upper line) and that of the relevant physical drive (lower line).
PAGE 313
Global Status 7.7.6.2 History diagrams Tape pool values When you click on a column in the right-hand part of the screen with the right mouse button and select “Show Statistics” a window containing the tape pool values appears. Example The presentation shows the progress for the physical volumes used. Start date, start time and range can be selected for this display.
PAGE 314
History diagrams Global Status 7.7.7 Exporting history data This function causes the history data to be read in as specified by the current settings. The data is then written to a file. This can involve considerably more data than would be needed to draw the diagram currently selected (see the example below).
PAGE 315
Global Status History diagrams Example Scope of output: It is possible that more data fields are written to the file than would be shown on the screen, namely all data fields which were read in for the presentation selected (i.e. the raw data supplied at the interface). Example: U41117-J-Z125-7-76 If the presentation mode average is selected, the min/max data fields are nevertheless imported and exported in addition to the average data fields.
PAGE 316
History diagrams Global Status 7.7.8 Command line tool for generating the history data The shell script get_hist.sh was created to permit the history data of a CentricStor system to be made available in a text format (e.g. for the spreadsheet program Excel). This script is contained in the /usr/apc/bin directory. It can be used to analyze the current history data of the system on which it is called (Case a), or the imported data of a foreign system (Case b).
PAGE 317
Global Status History diagrams All values which can be selected in the graphical call of the history function can also be specified as additional parameters. The -hd parameter, which is described further below, is also accepted. Which parameters can or must be specified differs according to the history type. The correlation is shown by a matrix which the script outputs when the help function (-h or -? parameter) is called: get_hist.sh -? call: get_hist.
PAGE 318
History diagrams Global Status or wild card term> | | | | | | -da | | | | | | -dv | | | | | | -hd (*3) | | | | | | -ho =0 and <24)> | | | | | | -in
PAGE 319
Global Status History diagrams Presentation of the data in Excel In order to permit the history data to be presented on a graphical interface of a type similar to CentricStor, an Excel macro has been created which is supplied with the GXCC product. This macro is only intended as an example and in no way provides a 1:1 map of the GXCC graphical interface. The macro is contained in the following directory: /osd/Windows/Excel_Performance_Makro.
PAGE 320
History diagrams Global Status Example 1. Create a file get_hist.sh total -da 2006-03-29 -ho 0 -pt 6h >YIN.total2.txt 2. Transfer file 3.
PAGE 321
Global Status History diagrams 4.
PAGE 322
History diagrams Global Status 5.
PAGE 323
Global Status History diagrams Here, by way of comparison, is the GXCC presentation: Note the output mode (min,max,average) selected in GXCC and the spreadsheet of the same name selected in EXCEL.
PAGE 324
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 325
8 XTCC 8.1 General While GXCC regards a CentricStor system as a whole, XTCC is limited to one ISP together with the connected peripherals. You start XTCC for an ISP by positioning the mouse pointer in GXCC over the symbol of the ISP and right-clicking to select the “Show Details (XTCC)” option from the function menu. For each ISP, XTCC can be started as often as you wish. When GXCC is terminated, all XTCC instances that were started from GXCC are also terminated.
PAGE 326
General XTCC CentricStor recognizes various ISP types. ICP Integrated Channel Processor An ICP has a permanent connection to one or more BS2000/OSD, z/OS or OS/390 hosts via ESCON/FICON adapters or to an open systems host via an FC controller operating as a host connection. Host adapters and virtual devices are available only on ICPs. IDP Integrated Device Processor An IDP always has at least one tape drive connected via SCSI or FC and an associated PDS. Physical devices are available only on IDPs.
PAGE 327
XTCC General In the case of an ICP_IDP combination, the display is somewhat different: PDSs and emulations/virtual devices are located on the same level in the diagram. The PDSs are connected to the associated device controller, and the emulations are connected to the associated host adapter(s).
PAGE 328
Margins of the main XTCC window XTCC 8.2 Margins of the main XTCC window 8.2.1 Title bar Local()-Config if XTCC is running on the ISP under consideration. Remote()-config “” if XTCC is running on another ISP in the CentricStor system. i GXCC always starts XTCC on the system on which GXCC is also running. Remote(
PAGE 329
XTCC Margins of the main XTCC window SERV XTCC mode (OBSV=Observe, SERV=Service, USER=User, SIMU=Simulation). 80% Current window size setting (in the example, 80%). Autoscan Green = started Yellow = active Red flashing = stopped / temporarily disabled White =blocked (SIMU mode) S 5s Autoscan operating mode and interval (S = self-adjusting, M = manually adjusted). n.me+op Read rate for InfoBroker data [n.m*10op bytes/second]. The rate is calculated using the transfer time of an InfoBroker record.
PAGE 330
Function bar XTCC 8.
PAGE 331
XTCC Function bar 8.3.1 File 8.3.1.1 Select Selects a configuration file saved previously with “Save” (see below): The window contains the field for entering the file name plus the following function keys: OK Checks whether the specified file is a valid XTCC configuration file and, if so, its contents are output in graphical format and in Simulation mode. If not, an error message is output. Browse Opens a standard dialog box for searching for and selecting a file. The file type is preset to *.
PAGE 332
Function bar 8.3.1.4 XTCC Print Unix Platform Saves or prints the configuration currently displayed in PostScript format: This opens a window containing the following fields and buttons: Print to Specifies the target for the printout. Command List box used to specify the printer. In the case of UNIX systems, this field must be set to the name of the print program or script. 332 File Target for the PostScript file to be created. The presetting is determined by the color mode set.
PAGE 333
XTCC Function bar File Selection with input field. List box used to specify the name under which the PostScript file is to be saved. Depending on the color selection made under “Mode”, this field is preset with the file name /outcolor.ps or /outgray.ps, where is set to the XTCC tmp directory. To print out the configuration, these files can then be sent to the PostScript printer that supports the corresponding mode.
PAGE 334
Function bar 8.3.1.5 XTCC Exit Shuts down XTCC, saving the current settings to the profile file in the process. The settings are not saved if XTCC is exited using the following functions: – System function Click on the CentricStor icon at the top left and in the pull-down menu select the “Close” function or the function at the bottom (the menu language depends on the system language selected). – 334 Window Manager function At the top right click on the box containing the X.
PAGE 335
XTCC Function bar 8.3.2 Unit 8.3.2.1 Select This function is disabled if XTCC is started from GXCC. Otherwise, if XTCC was started directly, the “XTCC Unit Select” window is opened. Example The operation and functions of Unit Select are described in the section “Select” on page 147. Errors during connection setup with “OK” are handled differently, however, because in this case no connection exists as yet to a CentricStor.
PAGE 336
Function bar XTCC 8.3.3 Options 8.3.3.1 Settings Opens a submenu containing the following functions: Allows you to set the following options: Size [%] You can vary the scale of the graphic display from 20% to 120% in 5% steps. If you set a value less than 80%, all the object functions will be deactivated and the images for the drive types will no longer be displayed. By left- or right-clicking anywhere in the XTCC window, you can reset the configuration display to 100% with the optimum aspect.
PAGE 337
XTCC Function bar For Infobox: Move Pointer The infos are displayed by positioning the mouse cursor. Click Button The infos are displayed by clicking on the left mouse button. The descriptions in the manual generally relate to this mode. Help in: English Help texts in English. German Help texts in German. i The language of the help texts also controls which version of the online manual is offered in the Help menu.
PAGE 338
Function bar XTCC 8.3.4 Autoscan Each Autoscan cycle consists of a data transfer phase, a display phase, and the Autoscan delay. The Autoscan delay is the interval between the end of the display phase and the beginning of the subsequent data transfer phase. The color of the “Autoscan” text in the status bar in the bottom right-hand corner of the XTCC window shows the current status of this periodic transfer of information.
PAGE 339
XTCC 8.3.4.3 Function bar Settings Opens a submenu containing the following setting options and buttons: Autoscan Delay [s] This scale allows you to determine the interval currently set. If “Manual Adjusting” is selected, this value can be changed. Mode Self Adjusting (S) The Autoscan delay is determined automatically and displayed in the status bar in the format Ss.
PAGE 340
Function bar XTCC OK Confirms the settings and closes the menu. Help Opens a window containing the XTCC help file. Cancel Cancels the settings and closes the menu. 8.3.4.4 Scan Now Triggers an additional, immediate scan cycle in the event of an Autoscan process being stopped manually or a lengthy Autoscan delay. This function can also be initiated by pressing CTRL + spacebar simultaneously. 8.3.4.
PAGE 341
XTCC Function bar 8.3.5 Tools The following functions are available: – – – – – 8.3.5.1 XTCC Communications Get Remote/Expand Local File Show Remote File Compare Local Files XTCC Update/Revert XTCC Communications Opens a window containing a list box and an input field: The list box contains the IDs of the XTCC connections to the selected ISPs together with short messages (Message) which are used for communication between the XTCC users.
PAGE 342
Function bar XTCC If messages are present, then the number of messages is displayed by means of the yellow indicator Msg: in the XTCC status bar. Yellow letter symbols are also visible in the configuration display. Meaning of the buttons Send Sends a message entered in the “Broadcast Message” window to the InfoBroker. You can also use the Return key instead of this button. Clear Deletes the input field and message in the InfoBroker. Help Displays the XTCC help file.
PAGE 343
XTCC 8.3.5.4 Function bar Compare Local Files Starts a graphical tool which enables two local text files to be compared. The two files are displayed in synchronized text windows. Differences are marked in color, and the number of differences is entered in the status line at the bottom right. By selecting “View / Show Line Comparison Window” in the diff tool menu, differences within individual lines can be made visible. Notes – – – 8.3.5.
PAGE 344
Function bar XTCC 8.3.6 Profile The term “profile” encompasses all user-specific settings chosen under “Options” and “Autoscan”. These settings are stored in a user-specific subdirectory.
PAGE 345
XTCC Function bar If you require individual profile settings, you should define separate profile settings. The profile data is saved in a matrix format: A directory is set up for each profile name, including “default”. Directory: default.prf Name1.prf Name2.prf Name3.prf CentricStor A CentricStor_A.opt CentricStor_A.opt CentricStor_A.opt CentricStor_A.opt CentricStor B CentricStor_B.opt CentricStor_B.opt CentricStor_B.opt CentricStor_B.opt CentricStor C CentricStor_C.opt CentricStor_C.
PAGE 346
Function bar 8.3.6.1 XTCC Select Allows you to create and select user-specific subdirectories in the temporary XTCC directory. All option settings are then stored in unit-specific files in these subdirectories. The name of the subdirectory is formed from the profile name and the extension .prf. The “Profile Select” function opens a window consisting of a list box, an input field, and various buttons. The list box contains the profile names already defined.
PAGE 347
XTCC Function bar Notes on operating – – – – You use the two scroll bars for positioning in the list box. Double-clicking on an entry with the left mouse button transfers this to the entry field. Simultaneously pressing the Ctrl+o keys enables the content of the list box to be sorted in ascending or descending order. Search function: After you have entered a search string in the entry field, pressing the return key displays the next hit.
PAGE 348
Function bar XTCC 8.3.7 Help The appearance of the submenu depends on the language selected in “Settings” (see page 336): 8.3.7.1 German: English: Help Help LIESMICH Direkthilfe Maus-Funktionen About XTCC... Benutzerhandbuch Readme Direct Help Mouse Functions About XTCC... User Guide README / LIESMICH This function is used to open the file viewer with the help file in accordance with the language setting, thus here to “Help”: Information on using the file viewer can be found starting on page 360.
PAGE 349
XTCC 8.3.7.4 Function bar About XTCC... The version of XTCC can also be seen at the bottom right of the configuration overview window. Meaning of the buttons OK The window is closed. File info Opens a text window in which information on the XTCC files that exist is output: The version numbers are displayed in the left-hand column provided these are contained in the file concerned.
PAGE 350
Function bar 8.3.7.5 XTCC CentricStor User Guide One of the menu functions – – CentricStor User Guide (complete) CentricStor User Guide (GUI Part) is offered if – – – XTCC is operated in User or Observe mode, the monitored system is of the type “CentricStor” and a PDF documentation file suitable for the CentricStor Version m.n and the current language setting is available.
PAGE 351
XTCC 8.3.7.6 Function bar CentricStor Service Manual One of the menu functions – – CentricStor Service Manual (complete) CentricStor Service Manual (GUI Part) is offered if – – – XTCC is operated in Service or Simu mode, the monitored system is of the type “CentricStor” and a PDF documentation file suitable for the CentricStor Version m.n and the current language setting is available.
PAGE 352
Elements of the XTCC window XTCC 8.4 Elements of the XTCC window 8.4.1 Display Each XTCC window displays an ISP of the CentricStor system, together with the connected peripherals. The ISP is represented by a beige field at the center of the window: The small colored boxes around the edge represent the peripheral controllers (ESCON, FICON, FC, SCSI, FC-SCSI). The small boxes in the middle represent software processes.
PAGE 353
XTCC Elements of the XTCC window The operating status of an element is indicated by the color of the associated box, where the following color key applies: Green: Pink: Yellow: Red: Normal Malfunctioning, offline or not ready Status unclear, some subcomponents are malfunctioning Configuration error; the component is contained in the configuration description, but the InfoBroker has not yet established contact with it If the ISP contains numerous XTCC objects, its contents are displayed over several tab
PAGE 354
Elements of the XTCC window XTCC 8.4.2 Unexpected errors In the event of internal errors such as those that occur owing to missing (mandatory) variables of the InfoBroker, XTCC opens (if possible) a window with the title: “XTCC Problem Info”. This window contains the error message and buttons for further activities: Exit Terminates XTCC. Stack Trace Opens a window with further information on the error. If you click on the “Cancel” button in this window, the window is closed and “Continue” is attempted.
PAGE 355
XTCC Elements of the XTCC window The Autoscan process is stopped for the duration of this wait time. Such a window can - if absolutely necessary - be closed by clicking on the relevant Window-Manager-specific button at the top right or left of the window title bar. The wait time for restarting the Autoscan is not reduced by this, however: The Autoscan process remains stopped until it is possible to terminate the associated function or the maximum wait time has elapsed (timeout nn sec.). 8.4.
PAGE 356
Elements of the XTCC window XTCC 8.4.5 Group display When CentricStor components are displayed, there may be more configuration elements (e.g. virtual drives) than can be displayed in a single window. At the same time, you may often want to monitor operations at multiple CentricStor ISPs simultaneously. Without the appropriate tools, this can make your screen difficult to interpret. In XTCC, both problems are solved by the use of an overview window display.
PAGE 357
XTCC Elements of the XTCC window The status line is contained at the bottom edge of the Groups window: Autoscan S 5s green = released yellow = active flashing red= stopped / temporarily discontinued white = locked (Simu mode) Autoscan operating mode(S = Automatic setting, M = Manual setting) Autoscan interval If the group display is minimized, you can reopen it simply by clicking the appropriate tab. Click the tab to open the group display for the entire ISP.
PAGE 358
Elements of the XTCC window XTCC Color codes in the group display The object colors used in the group display are very similar to those in the configuration display: SYS Turquoise OK HA Ct Emu/ Manager/ Server Target/ V-Drive RAID ACTIVE OK Running and attached Read/write, read only, busy OK Green Running and not attached Pink ACTIVATING Hanging CHAN_DISAB 11) CONFIGURED FAILED INACTIVE INITIAL STOPPED Stopped Online, offline Error Yellow12) Unknown Unknown Unknown Warning White Re
PAGE 359
XTCC Elements of the XTCC window Explanation 1 File system full: red flashing tool symbol in the configuration overview. Flashing symbol for system messages in the GXCC window. 2 File system 95% full: black flashing tool symbol in the configuration overview. 3 SNMP: SNMP manager has received an SNMP trap. Flashing SNMP symbol in the configuration overview. 4 Drive needs cleaning. Yellow flashing symbol in the configuration overview. 5 Busy for some time.
PAGE 360
File viewer XTCC 8.5 File viewer XTCC provides a file viewer, complete with scroll bars and search functions, for displaying help texts and the data returned by various “Show” functions. This file viewer supports both text and binary files. Text files or hexadecimal dumps up to 100 Mbytes in size can be read. 8.5.1 Opening the file viewer ● The file viewer can be opened manually by selecting “File” ➟ “Show” in GXCC or XTCC. An intermediate form will be output allowing you to select a file for display.
PAGE 361
XTCC File viewer 8.5.3 File 8.5.3.1 Open (Text)/Open (Hex) This function is only available in User and Service mode. Opens a file selection box. Once you have made your selection, the file viewer is then opened in pure text mode (Open (Text)) or in combined hexadecimal/text mode (Open (Hex)). The display mode can be changed later on if desired. When loading large files, the display window is opened as soon as the first few lines have been read in.
PAGE 362
File viewer XTCC 8.5.4 AutoUpdate This function is offered only when called by specific GXCC/XTCC functions. The file displayed is reread cyclically. If entries have been added, these are shown at the end of the text window and highlighted by a lighter background. 8.5.4.1 Start Only when AutoUpdate is stopped: AutoUpdate is activated. 8.5.4.2 Stop Only when AutoUpdate is active: AutoUpdate is stopped. 8.5.5 AutoPopup This menu item is only offered if the AutoUpdate is active.
PAGE 363
XTCC File viewer 8.5.6 Highlight Selecting “Down” or “Up” with the left mouse button or pressing the associated keyboard shortcut enables you to highlight all occurrences of the string specified in “Search String” in color. The number of occurrences is output in “Highlighted”, and the cursor is positioned on the first occurrence starting from the beginning or end of the text. If the string cannot be found in the text, the message “No match found” is output.
PAGE 364
File viewer XTCC Highlighted Depending on the search procedure, this field outputs the number of color-highlighted hits for the string being searched for. This counter also takes multiple hits into account (depending on the search method and string). The search is ended when the color of the text for this field changes from red to green. Read [%] Shows the percentage of the file already read in.
PAGE 365
XTCC File viewer 8.5.8 Mode 8.5.8.1 1st Line -> Ruler/Selection -> Ruler Displays the first line or the selected line in the non-scrolling area of the window. This function can be used when viewing long tables in order to keep the title bar visible at all times. Some applications predefine the title bars. 8.5.8.2 Text/Hex These functions are not offered by all applications. The selected file is displayed either in text mode or as a hexadecimal ASCII dump.
PAGE 366
File viewer 8.5.8.5 XTCC Tab Stop Interval In text files with tabulators the tab stop interval can change. The “default” generates an interval of 8 characters with behavior typical for a text editor. For the other values intervals from 1 .... 20 can be selected with behavior typical for a text editor. 8.5.9 Help Opens a text window containing operating instructions.
PAGE 367
XTCC ISP 8.6 ISP 8.6.1 Object information on the ISP The object representing the entire ISP is hidden behind the text “CentricStor” in the center of the XTCC window. Object representing the entire ISP If required two additional symbols are displayed: – A yellow flashing SNMP symbol indicates that SNMP data is present. – A yellow or red flashing tool symbol indicates that the file system is overfull (yellow >95%, red = 100%).
PAGE 368
ISP XTCC Hardware Type Prod. Serial No. Graphics Board Firmware Autoload Primergy PC model. Serial number of the Primergy Type of graphics board Indication of whether or not the firmware autoload function is activated. InfoBroker Level Revision level of the InfoBroker. RAM Memory configuration. The usual prefixes apply; 1 MB = 220, 1 GB = 230, 1 TB = 240 bytes. File system occupancy level (if more than 95%) Over time, the ongoing logging process can cause the file system to fill up.
PAGE 369
XTCC 8.6.2.
PAGE 370
ISP 8.6.2.2 XTCC Version Consistency Check This function is offered only if the consistency check mechanism is available on the monitored system and inconsistencies have been detected in the currently installed software version. This case can, for example, occur in the event of subsequent integration of developer corrections. A window opens in which the result of the check is displayed: This example shows that Version 1.7 of header file headers/apc/pds_plm.
PAGE 371
XTCC 8.6.2.3 ISP Show Diff. Curr./Prev. Version This function is offered only if the consistency check mechanism is available on the system being observed. It is used to show the difference between the current and the previous versions using the graphical Diff tool. The two versions are displayed in synchronized text windows. The differences are marked with colors and the number is shown at the bottom right in the status line.
PAGE 372
ISP 8.6.2.4 XTCC Show Node Element Descriptors This function is available only for ICPs with an ESCON channel adapter. It displays the node element descriptors of the ESCON channel adapters and the underlying virtual devices: i 372 Show/View functions open windows that are equipped with scroll bars and search functions. For information on the tools that can be used to navigate through these windows when large data volumes are involved, see the section “File viewer” on page 360.
PAGE 373
XTCC 8.6.2.5 ISP Show Configuration Data Outputs a configuration display in table form: i For space reasons the example has been shortened. The configuration data shows: – – – – information about the ISP a list of emulations with emulation name, HSI and device name (for ICPs) or a list of PDSs for an IDP.
PAGE 374
ISP XTCC The SCSI devices are represented in the normal way as c (=controller) t(=target)l(=Lun), where cc, tt, ll are shown as decimal numbers. cc tt ll specifies the controller number in the ISP. target number in the form of a decimal number. With components connected via Fibre Channel, the path is coded in this number. This is described in more detail in the next section. Logical Unit Number of the component.
PAGE 375
XTCC 8.6.2.6 ISP Show System Log Displays system messages from the file klog.msg: 8.6.2.7 Show SNMP Data This function is only available if a flashing yellow “SNMP” symbol indicates that one or more SNMP data blocks are available. It opens a submenu in which you can select a block for display. This is then removed from the submenu. 8.6.2.8 Clean File System This function is not available in Observe mode.
PAGE 376
Internal objects of the ISP XTCC 8.7 Internal objects of the ISP 8.7.1 Representation of internal objects Internal objects are those that do not communicate directly with the external data path and are arranged physically within the system. If the block for the internal objects is not in the foreground, the visible border of the dark gray block changes its color to blue when the mouse pointer is positioned on it, indicating that it is selected.
PAGE 377
XTCC 8.7.1.2 Internal objects of the ISP CD-ROM The status of a CD-ROM drive is indicated by the following colors: Turquoise: Pink: Yellow: Read/write, read, busy Online, offline Status unknown If the mouse pointer is positioned over such an object, its color changes to blue, indicating that it is selected.
PAGE 378
Internal objects of the ISP 8.7.1.4 XTCC SCSI controller This is represented exactly as described in the section “Object information on SCSI controllers” on page 421. 8.7.1.5 RAID controller A RAID controller is represented by a block in which the device number (RAID #0, RAID #1 etc.), controller number and interface type SP (SCSI parallel) are displayed.
PAGE 379
XTCC ESCON/FICON host adapter 8.8 ESCON/FICON host adapter 8.8.1 Object information for the ESCON/FICON host adapter Each host adapter is represented by a block at the top of the ICP. Within the block, the host adapter number (HA #0, HA #1, etc.) and type (ESCON, FICON, FC) are displayed. The status of the host adapter is indicated by the colors pink (not active), green (active) and yellow (unknown).
PAGE 380
ESCON/FICON host adapter Channel Nodes XTCC List of host channels used to establish a logical path. Each line corresponds to one ESCON channel. The list shows the node ID of the ESCON port in the host. The hexadecimal number separated by a blank represents the port number of the host channel on the ESCON Director (= link address). The colon is followed by “chi” (= Channel Image) with a list of the virtual channels of the host connected via this physical path.
PAGE 381
XTCC ESCON/FICON host adapter 8.8.2 ESCON/FICON host adapter functions The following functions are available: – – – 8.8.2.1 Show Node ID Details Show Node Element Descriptors Show Dump (prkdump) Show Node ID Details Display of the node element descriptors of an ESCON/FICON host adapter, of the ESCON/ FICON Director, and of the host channels connected to the host adapter: The node ID is formatted. An explanation of the abbreviations can be found under the list.
PAGE 382
ESCON/FICON host adapter 8.8.2.2 XTCC Show Node Element Descriptors Display of the node element descriptors of an ESCON/FICON host adapter and the underlying virtual devices. i 382 Show/View functions open windows that are equipped with scroll bars and search functions. For information on the tools that can be used to navigate through these windows when large data volumes are involved, see the section “File viewer” on page 360.
PAGE 383
XTCC 8.8.2.3 ESCON/FICON host adapter Show Dump (prkdump) Display of the host adapter driver dump: i U41117-J-Z125-7-76 To analyze this dump, you will need detailed knowledge of the system.
PAGE 384
Emulations of drives connected to OS/390 host adapters XTCC 8.9 Emulations of drives connected to OS/390 host adapters 8.9.1 Information on emulations The ESCON channel adapter only has emulations of drives of the types IBM-3490E and Fujitsu F6473K. In the Fujitsu-Siemens Computers product lists, 3490-E devices are listed under the number 3590 and must not be confused with 3590 tape drives from IBM. Each emulation is assigned to a virtual tape drive.
PAGE 385
XTCC Emulations of drives connected to OS/390 host adapters The information box contains the following information: Emulation Name of the emulation. Virtual Drive Internal CentricStor name for the logical drive. Mnemonic Name of the logical drive in the host (if defined). CIuster, Unit ESCON address of the logical drive (chennel and unit number). Revision Software revision level.
PAGE 386
Emulations of drives connected to OS/390 host adapters 8.9.2.
PAGE 387
XTCC 8.9.2.2 Emulations of drives connected to OS/390 host adapters Show Short Trace Displays general information at the beginning of the start trace file: This is followed by the trace on all commands sent by the host together with their termination.
PAGE 388
Emulations of drives connected to OS/390 host adapters 8.9.2.
PAGE 389
XTCC 8.9.2.4 Emulations of drives connected to OS/390 host adapters Show Error Log Displays a text window containing the error log of the virtual device or emulation.
PAGE 390
Emulations of drives connected to OS/390 host adapters 8.9.2.5 XTCC Show Memory Log Displays the process log for the emulation which is present in memory: This function makes it possible to display a continuous memory trace for the emulation (logging). This logging is independent of the trace set manually. Example Memory log, range 100 8.9.3 Functions for all 3490 emulations In Observe and User mode no functions are available which affect all emulations.
PAGE 391
XTCC Virtual 3490 drives 8.10 Virtual 3490 drives 8.10.1 Object information and error messages for virtual 3490 drives Each emulation is assigned its own virtual drive. In this object, the error messages and behavior of a real drive are simulated as required. Even the display units on real 3490 drives are reproduced faithfully and have the same displays as the real object of the emulation.
PAGE 392
Virtual 3490 drives XTCC The display can contain one of the following messages: Display 0 Display 1 Description CU READY -- CU ready but path not yet connected. CU ONL -- CU ready, path connected. EMU STOP NORMAL Emulation stopped: normal end. When a logical volume is loaded, the third line specifies which cache contains the associated data. 8.10.1.
PAGE 393
XTCC 8.10.1.2 Virtual 3490 drives Object information The extended information contains the following data: Drive Status (Empty, write-protected); Specifies whether a cartridge is inserted and whether data can be written to this cartridge. Check Condition Date and description of the last Check Condition that occurred. Medium Type (Only for mounted volume); Currently always “Virtual-Tape”. Password Password assigned to the drive by the host software.
PAGE 394
Virtual 3490 drives XTCC The following table lists the SIMs/MIMs used by the emulation and gives the probable cause. MIM fault symptom code FSC(0-3) X’hhhh’ MIM text Possible cause 0C01 Unsupported format 0C02 Hard write error TFS hard write error. Hard errors which recur repeatedly cause CentricStor to crash. 0C03 Hard read error TFS hard read error. Hard errors which recur repeatedly cause CentricStor to crash.
PAGE 395
XTCC 8.10.2.1 Virtual 3490 drives Show SCSI Sense i The device emulation of CentricStor works internally as a protocol converter from the channel to the SCSI protocol and vice versa. In a CentricStor ICP the SCSI interface is only emulated. In the real system the device emulation works with the interfaces of the file system to the RAID cache. However, because internal processing takes place as SCSI, the error display is accordingly in SCSI notation because this is standardized.
PAGE 396
Virtual 3490 drives 8.10.2.2 XTCC Show Medium Info (MIM) An info box appears if no MIM log exists: Displays the latest Media Information Messages in a text window.
PAGE 397
XTCC 8.10.2.3 Virtual 3490 drives Show Service Info (SIM) Displays the latest Service Information Messages in a text window. The MIM and SIM codes of the virtual devices are described in the section “Object information” on page 393. 8.10.2.4 Unload and Unmount This function is used to unload and unmount the virtual volume.
PAGE 398
FC-SCSI host adapter XTCC 8.11 FC-SCSI host adapter 8.11.1 Object information on FC-SCSI host adapters Each host adapter is represented by a block at the top of the ICP. Within the block, the host adapter number (HA #0, HA #1, etc.) and type (ESCON, FICON, FC) are displayed. The status of the host adapter is indicated by the colors pink (not active), green (active) and yellow (unknown).
PAGE 399
XTCC Emulations of SCSI drives (VTD) A dashed line indicates that the host adapter and/or emulation are not ready. If no line is displayed, no LUN was found. 8.11.2 FC-SCSI host adapter functions 8.11.2.1 Perform Link Down/Up Sequence For approx. 30 seconds the status “Link Down” is generated, thus activating a flashing display on the module. This enables the module to be located in the hardware. i The function can be called only if the host adapter is in “ACTIVE” mode. 8.
PAGE 400
Emulations of SCSI drives (VTD) XTCC The figure below shows the characteristics of an emulation as displayed in XTCC. The information box displays: Virtual Tape Device Internal SINIX name for the device. Logical Unit Number LUN on the FC-SCSI interface. Controller Serial number on the FC-SCSI controller. Revision Revision level of the emulation. Process ID Process ID of the emulation. Active, Own and Default Trace Configuration Trace settings (dependent on the VTD version).
PAGE 401
XTCC Emulations of SCSI drives (VTD) 8.12.2 Functions for individual VTD emulations The following function is available: – 8.12.2.1 Show Trace Show Trace Displays the emulation trace in a text window. The example above shows the trace entries created when the VTD is started. During operation, the trace primarily records the SCSI commands processed. 8.12.3 Functions for all VTD emulations “All” means all emulations on this ISP. In Observe and User mode no functions are available.
PAGE 402
Virtual SCSI drives XTCC 8.13 Virtual SCSI drives 8.13.1 Object information on virtual tape drives Drives of this type are designated as VDrives. In contrast to real drives, an associated SCSI controller exists only when the logical volume is located on the local disk. This is the case with a VTC, for example. In the case of CentricStor systems with an external RAID, a logical volume is addressed via a mount point (e.g. 'raid102').
PAGE 403
XTCC Virtual SCSI drives The following is displayed: Inquiry data Drive Status Check Condition: Reservation Medium Type: VSN Location Base Directory Vendor ID, product ID, product revision level, drive serial number. Vendor ID and product ID can be selected during configuration. Online, Offline, Read/Write Date and designation of the error condition that occurred last. The last 4 bytes of the WWPN of the host which reserves the drive are displayed.
PAGE 404
Virtual SCSI drives XTCC 8.13.2 Virtual generic drive functions Depending on the emulation, the following functions are available: /390 VDRV 8.13.2.1 OS VDRV Show SCSI Sense Shows the accumulated SCSI sense bytes of the virtual drive. 8.13.2.2 Show Medium Info (MIM) Shows the “Media Information Messages”. 8.13.2.3 Show Service Info (SIM) Shows the “Service Information Messages”. 8.13.2.4 Unload and Unmount Unloads and unmounts the virtual volume.
PAGE 405
XTCC VLS (Virtual Library Service) 8.14 VLS (Virtual Library Service) 8.14.1 Object information on VLSs A VLS (Virtual Library Server) is the emulation of an archive system for magnetic tapes. CentricStor can emulate various types of archive systems. VLSs of the type VACS, VLMF or VDAS serve a number of clients. These VLSs can only run once in CentricStor. A VLS of the type VAMU or VJUK is only able to serve a single client.
PAGE 406
VLS (Virtual Library Service) ● XTCC The following information is also output for VLSs of the type VJUK: Example: VJUK Vendor ID Product ID Serial No Slots Controller Lun Mode Vendor identifier Product identifier Serial number Number of slots Number of the controller used SCSI Lun of the jukebox Operating status 8.14.2 Functions for individual VLSs The functions available for a VLS depend on its type. VDAS has the “Show Trace” function which opens a text window containing trace information. 8.14.2.
PAGE 407
XTCC VMD (Virtual Mount Daemon) 8.15 VMD (Virtual Mount Daemon) 8.15.1 Object information on the Virtual Mount Daemon (VMD) The VMD, also known as the mount server, controls the mounting and unmounting of virtual volumes in the virtual drive(s) on behalf of the VLM. Each ICP has its own VMD. The VMD and the drives it serves must be located on the same ISP. The status of the VMD is indicated by the colors pink (stopped), green (running), and green/ brown (running with the trace switched on).
PAGE 408
VLM (Virtual Library Manager) XTCC 8.16 VLM (Virtual Library Manager) 8.16.1 Object information for the VLM Virtual libraries are emulated and mapped to physical libraries in a process pair consisting of a VLM (Virtual Library Manager) and a PLM (Physical Library Manager). In XTCC, the VLM and PLM are represented by small boxes in the VLP. The status of the VLM is indicated by the colors pink (stopped), green (running), green/brown (running with the trace switched on), and green/red (in HALT mode).
PAGE 409
XTCC VLM (Virtual Library Manager) ● Whether the cache file system is used for “floating” volumes or whether volume groups are permanently assigned to it (“exclusive”). ● The number of “misplaced” volumes which may be present. These are logical volumes which are currently not located in the cache file system for which they were configured. The cache status provides an overview of the CentricStor load status.
PAGE 410
VLM (Virtual Library Manager) 8.16.2.2 XTCC Set HALT Mode/Set RUN Mode This function is not available in Observe mode. In HALT mode, the VLM accepts no mount jobs for logical volumes. All other CentricStor activities continue to run. The hosts can continue to access logical volumes that are already mounted. Mount jobs are rejected with the error message “N005 - Robot not ready”. ! WARNING! In some host systems, even a brief HALT period can result in considerable disturbance to magnetic tape processing.
PAGE 411
XTCC RAID systems 8.17 RAID systems 8.17.1 Object information on RAID systems CentricStor can be supplied with the RAID systems S80, CX500, CX3-20 and Eternus 3000/4000. In XTCC, the RAID systems are represented as peripherals connected to the ISP via a Fibre Channel controller. In some CentricStor configurations, internal RAID controllers are used. These have a direct connection to the host and do not require a Fibre Channel connection. They are thus not visible in the overview of the ISP.
PAGE 412
RAID systems XTCC The controller types differ slightly in their presentation of the functions available: Eternus 3000/4000 CX500/CX3-20 S80 (=FC2502) Internal RAID system 412 U41117-J-Z125-7-76
PAGE 413
XTCC RAID systems In the case of external RAID systems, the information window contains the following information: – – – – – vendor ID, product ID type and serial number of the RAID system firmware release (insofar as this can be queried) operating status and any error messages (info) internal SINIX name, SCSI topology (CTL) and the connection to the FC fabric In Fabric Mode, the information “Local Domain x, Port y“ is displayed for the target numbers 128…2047. The local domain is in the value range 1..
PAGE 414
RAID systems XTCC 8.17.2 Functions of RAID systems The following functions are available: – – – – – Show Complete RAID Status (all types) Show Mode Pages (CX500/CX3-20 and FCS80) Show Mode Page Details Show Log Pages Show Log Page Details The availability of the functions de-pends on the particular RAID system. The menus are available in all operating modes. 8.17.2.
PAGE 415
XTCC RAID systems This very extensive information indicates the status of the controllers and the disks. The displays are self-explanatory. For a more precise interpretation, in particular in the case of partial failures, please refer to the RAID system manual. The content and presentation depend on the type of RAID controller. 8.17.2.2 Show Mode Pages (CX500/CX3-20 and FCS80) Displays the SCSI mode pages in a text window.
PAGE 416
PLM (Physical Library Manager) XTCC 8.18 PLM (Physical Library Manager) 8.18.1 Object information on the PLM The status of the Physical Library Manager (PLM) is represented by the colors pink (stopped), green (running), green / brown (running with trace switched on) and green / red (in recovery mode). In the extended status the PID and the autostart setting are also displayed. 8.18.2 PLM functions In User and Observe modes no PLM functions are available.
PAGE 417
XTCC PLS (Physical Library Service) 8.19 PLS (Physical Library Service) 8.19.1 Object information on the PLS Each physical library is assigned at least one PLS (Physical Library Server). The PLS of a SCSI-controlled archive must run on the ISP that contains the associated SCSI controller. The easiest way of identifying the location of a PLS is to use the Global Status Monitor.
PAGE 418
SCSI archive systems XTCC 8.20 SCSI archive systems 8.20.1 Object information on archive systems Archives with a SCSI-controlled access system can be operated in the ISP via the XTCC instance containing the associated PLS. A lighter-colored image of the archive system is shown behind the drive(s) belonging to the archive. All associated drives are also enclosed in a light gray shadow frame, which is intended to represent the archive system.
PAGE 419
XTCC SCSI archive systems 8.20.2 SCSI Archive system functions This function is offered after you right-click on the archive system icon (behind the drive icon). i 8.20.2.1 The Show Mode Pages, Show Mode Page Details, Show Log Pages and Show Log Page Details functions are not offered for all libraries. Show Mode Pages The SCSI mode pages are displayed. This function is not offered for all systems and all libraries. 8.20.2.
PAGE 420
PDS (Physical Device Service) XTCC 8.21 PDS (Physical Device Service) 8.21.1 Object information on PDS A PDS (Physical Device Server) controls precisely one physical device. The object information displays the controller and target of the associated SCSI device. This information is also indicated by the color of the connecting lines to the SCSI controllers and drives. A PDS consists of two processes, one for communicating with the RAID system and the other for communicating with the device.
PAGE 421
XTCC SCSI controllers 8.22 SCSI controllers 8.22.1 Object information on SCSI controllers Each SCSI controller is represented by a block at the bottom of the inner window. Within the block, the device number (SCSI #1, SCSI#2, etc.), controller number, and interface type (SP = SCSI parallel / FC = Fibre Channel) are displayed.
PAGE 422
SCSI controllers XTCC Max. Targets Name Interface Target Location Mode WW Node Number WW Port Number the maximum number of targets supported by the controller the system name of the controller the interface variant (e.g. SCSI Parallel or Fibre Channel) an indication of whether or not the targets are inside or outside the cabinet. mode, if available (FC): LOOP (L) or POINT TO POINT (P) World Wide Node Number (FC) World Wide Port Number (FC) 8.22.
PAGE 423
XTCC Cartridge drives (real) 8.23 Cartridge drives (real) 8.23.1 Object information on tape drives The XTCC user interface is designed for a wide range of tape drives. Please refer to the data sheet for your product variant to determine which drives are or can be connected. Depending on the drive type, some of the functions described here may not be available and some of the information given here may not apply.
PAGE 424
Cartridge drives (real) XTCC If Service Information Messages (SIM) or Medium Information Messages (MIM) are present in the drive, these are indicated by means of a yellow or red flashing SIM/MIM symbol, depending on their severity (severity 0/1/2/3 = Service/Moderate/Serious/Acute). If the device hangs, the entire block is marked with a large red “X”. Devices which are recognized by XTCC as SCSI targets on the SCSI bus but which cannot be identified further are assigned the type designation “xxxx”.
PAGE 425
XTCC Cartridge drives (real) 8.23.2 Tape drive functions Which functions are actually offered depends on the drive type. The menus are only examples. The following functions are available: – – – – – – – – Show SCSI Sense Show Log Pages Show Log Page Details Show Mode Pages Show Mode Page Details Show Vital Product Data Show Medium Info (MIM) Show Service Info (SIM) The device type and the SCSI address (controller, target) are displayed in the title bar.
PAGE 426
Cartridge drives (real) 8.23.2.1 XTCC Show SCSI Sense Displays the SCSI sense data: SCSI logging starts with the earliest entries, (see timestamp). It consists of four reference sections which are described in the hardware reference manual of the corresponding device. For MBK6 (3490-HSI): – – – – – 8.23.2.2 CDB, i.e. the SCSI command with associated parameters.
PAGE 427
XTCC 8.23.2.3 Cartridge drives (real) Show Log Page Details A submenu is opened in which you specify which log pages are to be itemized and displayed. 8.23.2.4 Show Mode Pages Displays the SCSI mode pages: This displays the current device setting (to perform a detailed analysis it is essential to refer to the device-specific SCSI reference manual, Mode Pages chapter).
PAGE 428
Cartridge drives (real) 8.23.2.5 XTCC Show Mode Page Details A submenu shows which mode pages the device supplies. If you select a page here that is also described in the SCSI standard, this will be displayed and interpreted in detail as in the example below. i 428 The SCSI topology (CTL) as well as the Inquiry String of the drive are shown in the “control lines” of the text window.
PAGE 429
XTCC 8.23.2.6 Cartridge drives (real) Show Vital Product Data Displays certain elements of the vital product data: You can use this function to display a subsection of the configuration data stored in the tape device. The device settings made in the Service and Operator menus can be found again here. These include, for example, the display language. Here you will also find the device’s FID log which provides important assistance to service engineers (FID: FRU identifier, FRU: field replaceable unit).
PAGE 430
Cartridge drives (real) XTCC Extract from the FID log: In this way you can extract an event or error history. FID code and FSC1 and FSC2 (Fault Symptom Code) must be reported to the manufacturer if errors which cannot be resolved occur on the device.
PAGE 431
XTCC 8.23.2.7 Cartridge drives (real) Show Medium Info (MIM) If there is no MIM entry, you will be notified in an info box: If Medium Information Messages have been recorded, a text window appears with the messages: The MIMs of the drives are recorded. The MIMs and the various responses are described in the maintenance documentation of the devices.
PAGE 432
Cartridge drives (real) 8.23.2.8 XTCC Show Service Info (SIM) Displays the Service Information Messages: If problems relating to the channel adapter (CONTROL UNIT) or tape devices (TAPE) occur, this information permits a better assessment of the severity of the recorded error. The problem is described in more detail in this window. In some cases, there is already a suggested solution for the service engineer. If required, the PDS creates two separate SIMs.
PAGE 433
XTCC 8.23.3.1 MSGMGR (Message Manager) Remove Symbols of all Drives Removes all warning signals on drives (MIM and SIM symbols) without having to retrieve the underlying error message. Warning signals can also be removed in Observe mode, but only by retrieving the underlying error message. 8.24 MSGMGR (Message Manager) 8.24.1 Object information on the Message Manager (MSGMGR) The Message Manager monitors and saves the system outputs of the various processors of the CentricStor system.
PAGE 434
MSGMGR (Message Manager) 8.24.2.1 XTCC Show Trace Displays the trace data: 8.24.2.2 Show Trap Trace Displays the trap trace data: The trap trace records all SNMP traps sent by the Message Manager to the SNMP management station(s).
PAGE 435
XTCC PERFLOG 8.25 PERFLOG 8.25.1 Object information of PERFLOG PERFLOG regularly collects performance-related system data and stores it in log files. The logging period and the directory in which log files are stored can be defined by service personnel during configuration. The log files can be displayed in graphical format using the tools described starting in section “History data” on page 257.
PAGE 436
PERFLOG XTCC 8.25.2 PERFLOG functions 8.25.2.1 Show Trace & Logging Displays the trace and log data: This example shows an extract from a trace depicting the events recorded during startup.
PAGE 437
XTCC ACCOUNTD (Account Daemon) 8.26 ACCOUNTD (Account Daemon) 8.26.1 Object information of ACCOUNTD The Account Daemon records the accounting data in a database. i This object is displayed as of CentricStor V3.1C2000 provided the Accounting License is installed. The status of the Account Daemon (ACCOUNTD) is shown by the colors pink (stopped) and green (running). Name PID Autostart Name as displayed in the symbol Process ID enabled / disabled 8.26.
PAGE 438
MIRRORD (mirror daemon) XTCC 8.27 MIRRORD (mirror daemon) 8.27.1 Object information of MIRRORD The mirror daemon monitors the status of the cache mirror. i The presentation of this object requires CentricStorV3.1C and the Cache Mirroring Feature License (CMF). MIRRORD consists of two processes: the parent and child processes. The upper half of the block is used to present the parent process, the lower half the child process.
PAGE 439
XTCC S80D (S80 daemon) 8.28 S80D (S80 daemon) 8.28.1 Object information of S80D Daemon S80D is a monitoring process for RAID systems of the type FC2502. Name PID Autostart Name as shown in the symbol Process ID enabled / disabled The status of the daemon is indicated by the following colors: pink green yellow Stopped Running Status unknown 8.28.2 Functions of S80D S80D has no functions which can be addressed via XTCC in User or Observe mode.
PAGE 440
VLPWATCH (VLPwatch daemon) XTCC 8.29 VLPWATCH (VLPwatch daemon) 8.29.1 Object information of VLPWATCH When the AutoVLP failover function is enabled, one VLPwatch daemon runs on the VLP and one on the SVLP. These daemons monitor the operational integrity of the VLP and, in the event of a failure, trigger automatic VLP switchover. PID Autostart Process ID enabled / disabled The status of the daemon is indicated by the following colors: pink green Stopped Running 8.29.
PAGE 441
9 Explanation of console messages 9.1 General When unusual events occur, the various CentricStor software components output messages at the console. The message texts are stored in the file /var/adm/klog.msg on the host in question and can be viewed centrally via the GXCC menu item “Show System Messages” (see section “Show System Messages” on page 158).
PAGE 442
General Explanation of console messages The color and text of the message provide you with important information concerning an event: ● Message color The color informs you of the “urgency” of a message: Urgency Description Color None --- Black INFO General information Black DEBUG Debug information Black NOTICE Information about a normal state change Black WARNING Warning message Blue ERROR Error message Red CRITICAL Information about a critical state Red ALERT Alarm message: the
PAGE 443
Explanation of console messages General Alongside the message number, the weight and the message text itself, the message provides the following additional information. ● Example SXSM018 2005-08-06 10:51:45 ICP0 : Aug 6 10:51:45 sma003: Fan 2: Fan is not manageable Message text Separator Name of the ISP Time Date Message number In the sections below, only the message line components printed in bold here, i.e. the message number and message text, are presented.
PAGE 444
General Explanation of console messages The message numbers in the following section are arranged alphabetically Message 444 Page SXCF... (CMF: Cache Mirroring Feature) 445 SXCH... (Channel: pcib/pcea) 447 SXCM... (CHIM) 449 SXDN... (DNA: Distribute and Activate) 450 SXDT... (DTV File System) 450 SXFC... (FibreChannel Driver) 452 SXFP... (FibreChannel Driver) 454 SXFW... (Firmware) 455 SXIB... (Info Broker) 456 SXLA... (LANWATCH) 458 SXLV... (Log Volume) 458 SXMM...
PAGE 445
Explanation of console messages Message lines 9.2 Message lines 9.2.1 SXCF... (CMF: Cache Mirroring Feature) SXCF012 CMF(#12): ALERT: failed to become PRIMARY, time exhausted: seconds Meaning During the switchover to multi-user mode (RunLevel 2) in the VLP’s boot phase the rc2 script /etc/rc2.d/S70mirrorstart determined that the data of the cache mirror when obsolete when it checked it. The switchover to multi-user mode is stopped until the data resources have been validated manually.
PAGE 446
Message lines Explanation of console messages Case 3: If the value 0 seconds is specified as the period, no usable data is contained in /etc/mirrord/ms.db. Notify 3rd-Level Support! SXCF014 CMF(#14): ALERT: failed to become PRIMARY, stale data Meaning When switching from SVLP to VLP a mirror backup server switches to become the mirror server (from the viewpoint of the CMF). During the change to multi-user mode in the VLP’s boot phase, the /etc/rc2.
PAGE 447
Explanation of console messages Message lines 4. Check whether the mirror server’s processes are running: myps mirror.s Sample output ? 922 ? 5179 ? 5177 1 5177 1 ? ? ? ? /etc/mirrord/mirror.client ? ? ? ? /etc/mirrord/mirror.server ? ? ? ? /etc/mirrord/mirror.server In the mirror server’s event log (/etc/mirrord/ms.event file) there is an entry with the message “ASSUMING role PRIMARY”. Example: s.event: 1110 152018.18 MS: ASSUMING role PRIMARY (1, 1) 1110 152018.22 MS: 5.
PAGE 448
Message lines SXCH004 NOTICE Explanation of console messages ESCON-ad pcea (bus dev ) started Meaning The ESCON port has been activated. This happens regularly at system startup. A port can also be reactivated after being reset or deactivated. SXCH005 ALERT ESCON-ad pcea (bus dev ) Memory error Meaning A memory error has occurred on the ESCON board. The driver was requested to perform a board reset and to recalibrate the memory.
PAGE 449
Explanation of console messages SXCH009 ALERT Message lines ESCON-adaptor (ser_no Meaning A test of the internal data paths on the ESCON board (PCEAS/PCEAT) which runs during the startup phase and idle times returned an error. Response Replace the ESCON board. SXCH010 ALERT ESCON-adaptor CRC READ Error in Channel Meaning During a read access the data was corrupted when it was transferred from the SINIX memory to the ESCON channel.
PAGE 450
Message lines Explanation of console messages 9.2.4 SXDN... (DNA: Distribute and Activate) SXDN100 (DNA#100): ALERT: switch SVLP_to_VLP successfully completed! (needed time: : (mm:ss)) Meaning The VLP switchover was successful. The time required for it is specified in parentheses. SXDN101 (DNA#101): ALERT: switch SVLP_to_VLP completed with errors! (needed time: : (mm:ss)) Meaning The VLP switchover has been completed. The previous SVLP is now the current VLP.
PAGE 451
Explanation of console messages SXDT003 Message lines DTV(# 3): ALERT: dev=: disk filesystem state is corrupted! Meaning Due to I/O errors when writing metadata, the DTV file system on the corresponding hard disk has become inconsistent. If this I/O problem is temporary, the metadata operation is rolled back and the file system is automatically restored to a consistent state (see message SXDT004 ...). Response Notify maintenance staff.
PAGE 452
Message lines Explanation of console messages 9.2.6 SXFC... (FibreChannel Driver) SXFC026 ALERT SXFC005 None PVA1ICP0 : FC2: IOCB_E_LOCAL_REJECT PVA1ICP0 : FC2: loop_id 0, IOCB error sequence timeout Meaning These two messages only occur together. The 'sequence timeout' indicates a problem which was detected/caused by the Emulex firmware. A typical example is a data transfer while writing or reading which is not terminated within the permissible maximum time.
PAGE 453
Explanation of console messages SXFC030 NOTICE Message lines FC5: RSCN for port 00637713 received RSCN means “Registered State Change Notification”. This is a “service” of the FC switch which every FC port can request from the switch. As the “central unit” the switch at all times has a general overview of all active FC ports in the fabric. The FC port which utilizes the RSCN service is now notified of each change in the fabric (e.g. addition or removal of an FC port) in the form of an “RSCN”.
PAGE 454
Message lines Explanation of console messages The message is only significant for external FC controllers. The abortion may have been initiated either by the SAN host or CentricStor. contains the 4 most significant bytes of the host WWN. A data transfer (read/write) is generally aborted, and the user receives an error message. Response The message can be ignored for the internal FC controllers because the SCSI target interface is not used here for data transfers.
PAGE 455
Explanation of console messages Message lines Temporary unavailability of the FC The following message complex, with LOOP-DOWN, rescheduling and LINK-UP messages, is output: SXFP041 None SXFP041 None SXFP041 None fcpal (sadm): rescheduling after temporarily unavailable resource fcpal (sadm): rescheduling on intr : unavailable resource fcpal (sadm): skipping timer processing Meaning The FC configuration is being changed.
PAGE 456
Message lines Explanation of console messages 9.2.9 SXIB... (Info Broker) System messages from the InfoBroker SXIB001 IB 001 EMERGENCY "*** %s File System full. ***" Meaning %s = name of the affected file system. The file system is 100% full. SXIB002 IB 002 ALERT "*** %s File System %d Percent filled . ***" Meaning %s = name of the affected file system. The file system is %d percent full (output once the occupancy level reaches 93%). SXIB100 IB 100 NOTICE "%s automatically restarted.
PAGE 457
Explanation of console messages SXIB200 Message lines IB 200 NOTICE "Please archive the performance history log files." Response If performance analyses are required for periods which precede the recording period, the history log files from the [fsys]/apc/diag/emtape/hist_log directory must be archived. Obsolete performance history log files are automatically deleted after the recording period has elapsed . SXIB201 IB 201 WARNING "Performance history recording discontinued.
PAGE 458
Message lines Explanation of console messages Response Wait to see whether the error message appears repeatedly (multiple messages) because with “bge” and the “cisco catalyth switches” there is the problem that the LAN is only available with a delay. If the error recurs repeatedly, . Notify the maintenance staff. 9.2.10 SXLA... (LANWATCH) SXLA001 LANWATCH(#1): CRITICAL: : LINK DOWN Meaning The LAN interface (e.g.
PAGE 459
Explanation of console messages Message lines 9.2.12 SXMM... (Message Manager) SXMM007 KLOG[]: INFO: Message Manager unavailable! Meaning Information that the Message Manager is not available. Response Notify maintenance staff. SXMM005 KLOG[]: WARNING: vlsTrace() error Meaning Error while creating a new trace file or error while activating/deactivating the trace. Response Notify maintenance staff.
PAGE 460
Message lines SXMM005 Explanation of console messages KLOG[]: WARNING: fopen(/dev/osm) error errno= Meaning Error while opening /dev/osm. Response Notify maintenance staff. SXMM005 KLOG[]: WARNING: fstat(/dev/osm) error errno= Meaning Error while accessing /dev/osm. Response Notify maintenance staff. SXMM005 KLOG[]: WARNING: stdout error errno= Meaning Error while accessing stdout.
PAGE 461
Explanation of console messages SXMM007 Message lines KLOG[]: INFO: setsid() errno= Meaning Internal process error SXMM012 VLSM[]: WARNING: too many client entries pid= sd= Meaning Owing to lack of space the Message Manager could not accept any new connection request. SXMM012 VLSM[]: WARNING: Send SNMP Trap() error Meaning Error while calling the SendTrap process for sending a message to the SNMP master station.
PAGE 462
Message lines SXMM012 Explanation of console messages VLSM[]: WARNING: Check Path /usr/apc/tmp/msgadm error Meaning The directory /usr/apc/tmp/msgadm cannot be created. Response Notify maintenance staff. SXMM012 VLSM[]: WARNING: chdir(/usr/apc/tmp/msgadm) error errno= Meaning Error while changing the working directory to /usr/apc/tmp/msgadm. Response Notify maintenance staff.
PAGE 463
Explanation of console messages Message lines Response Notify maintenance staff. SXMM013 VLSM[]: NOTICE: File removed Meaning Information indicating that the oldest history file has been removed. SXMM014 VLSM[]: INFO: No space left in /msg (kbytes= used= avail= capacity=) Meaning Directory /msg (history files) could no longer be written to owing to lack of space. The odest history file has been removed.
PAGE 464
Message lines Explanation of console messages Response Notify maintenance staff. SXMM019 EMSG[]: WARNING: ReadNextEvtMsgLine() error Meaning Error while reading the event message file. Response Notify maintenance staff. SXMM019 EMSG[]: WARNING: fork() error errno= Meaning Internal process error Response Notify maintenance staff. SXMM019 EMSG[]: WARNING: vlsTrace() error Meaning Error while creating a new trace file.
PAGE 465
Explanation of console messages SXMM019 Message lines EMSG[]: INFO: Message Manager unavailable! Meaning Information that the Message Manager is not available. Response Notify maintenance staff. SXMM021 EMSG[]: INFO: ******* START EmsgTrap (EventMessageTrap) daemon Meaning Information on the start of the process EmsgTrap. SXMM021 EMSG[]: INFO: reopen(stdin)->/dev/null error Meaning Error while redirecting stdin to /dev/null.
PAGE 466
Message lines SXPL003 Explanation of console messages PLM(#3): ALERT: on not reachable Meaning It was not possible to send a message to the PDS on the host . Response Check whether the PDS and/or host are running and whether the TCP/IP connection is okay. If the corresponding IDP is running but the connection is not working, check the cables and the hubs. Notify maintenance staff if necessary.
PAGE 467
Explanation of console messages Message lines Check the following values: – – – – – soft minimum number of empty PV hard minimum number of empty PV absolute minimum number of empty PV amount of valid data for REORG timeframe for REORG The margin between “soft” and “hard” should be large enough, and the REORG interval should be suitably big. Normally, the value specified for the degree to which the cartridge for reorganization is filled should be large.
PAGE 468
Message lines SXPL011 Explanation of console messages PLM(#11):NOTICE: number of free PVs of PV-group over absolute minimum () again Meaning The number of free tapes is again greater than the absolute minimum. SXPL012 PLM(#12): ERROR: doesn't eject a volume, probably hardware error Meaning The PDS has not ejected a physical volume in such a way that the robot can grab it.
PAGE 469
Explanation of console messages Message lines List of the error strings reported with PLM/RPLM(#16) ERR_PDS_03_INIT: Meaning Error while initializing/opening the device node. Illegal device node (path). Illegal directory in the cartridge’s memory chip1 (tape directory corrupted). Response Evaluate physical error code. This error can occur if the SCSI devices/controllers cannot be accessed when CentricStor is started up.
PAGE 470
Message lines Explanation of console messages ERR_PDS_03_DRV_NOTREADY Meaning MTC drive/tape cartridge is not ready. Timeout expired. Error on TestUnitReady. Response Evaluate physical error code and sense bytes! Normal behavior on unload if error information ASC/ASCQ 3A/00 or 04/03 present. In this case, the message was caused by a preventive unload to an empty or already unloaded drive.
PAGE 471
Explanation of console messages Message lines ERR_PDS_03_POS_NOT_AFTER_TAPEMARK Meaning Positioning error: There is no tape marke immediately in front of the read/write position that is to be adopted. The block position transferred is presumably not correct. Response Evaluate the physical error code and sense bytes. It may be that the PLM has transferred an incorrect block number. If you think this is the case, save the diagnostic documentation.
PAGE 472
Message lines Explanation of console messages Response Notify maintenance staff. ERR_PDS_02_WRITE Meaning Error while writing to the cache file Response Notify maintenance staff. ERR_PDS_02_SEEK Meaning Error while positioning in the cache file Response Notify maintenance staff. SXPL018 PLM(#18): ERROR: reports error = on PV Meaning The PDS has reported a class-1 (general) error (ERR_PDS_01...).
PAGE 473
Explanation of console messages Message lines ERR_PDS_01_INVALID_HEADER_SIGN Meaning Tape header has no valid identifier (POS1) at position 0. Response Notify maintenance staff. ERR_PDS_01_TAPE_NON_VTLS Meaning Tape header does not have a valid CentricStor identifier. Response The volume was probably not imported correctly. Repeat the import procedure. If necessary, delete header (“Erase physical Volume”) and write a new CentricStorcompatible header to the tape (“Add physical Volume”).
PAGE 474
Message lines Explanation of console messages ERR_PDS_01_VSN_NOT_VALID Meaning VSN in the tape header and the transferred VSN are not identical. The operation can therefore not be performed. Response This is probably due to manual intervention. If you are sure that there is no user data on the cartridge, write the correct header. ERR_PDS_01_GROUP_NOT_VALID Meaning PV group in the tape header and the transferred PV group are not identical. The operation can therefore not be performed.
PAGE 475
Explanation of console messages SXPL021 Message lines LM(#21): NOTICE: Reorganisation failed for LV on PV , continue Meaning A reorganization operation initiated by the user encountered an error. The logical volume could not be read from the physical volume . An attempt will be made to move any other logical volumes from this physical volume. Response If this message occurs repeatedly, check whether the physical volume is accessible. There may be a media error.
PAGE 476
Message lines SXPL025 Explanation of console messages PLM(#25): WARNING : single saved LVs in dual save LV-group found Meaning Following a disaster recovery it is possible that logical volumes were first saved in a group or, if a dual save group has been created from a single save group, old logical volumes which have only been saved only once were found. The PLM automatically attempts to save these logical volumes a second time.
PAGE 477
Explanation of console messages Message lines Response Install the appropriate license key. SXPL030 PLM(#30):CRITICAL: missing licence for optional function "Multiple Library Support", exiting ! Meaning Several physical library servers are configured, but the required license key is missing. Response Install the appropriate license key.
PAGE 478
Message lines SXPL041 Explanation of console messages PLM(#41): NOTICE: Cleaning-group of Tape-library has no cartridge, tape-library is responsible for cleaning ! Meaning No cleaning cartridge is present. Response It is only necessary to enter cleaning cartridges if CentricStor is to clean the physical drives. SXPL042 PLM(#42): NOTICE: Cleaning-cartridge of Tape-library is unusable ! Meaning A cleaning cartridge is unusable.
PAGE 479
Explanation of console messages SXPL048 Message lines PLM(#48): NOTICE: cleancycles for tape-library available again Meaning PLM(#45) has been correctly responded to? SXPL049 PLM(#49): WARNING: ejected PV of tapelibrary is needed for restore ! Meaning The PV of a vault group has been removed from the robot, but is now required for a restore job. Response The PV must be imported.
PAGE 480
Message lines Explanation of console messages Response Only use cartridges with enough capacity. SXPL056 PLM(#56): NOTICE: all PVGs of TL deactivated Meaning This message is output after the plmcmd conf -e -T command has been issued: All physical volume groups of the specified robot have been deactivated.
PAGE 481
Explanation of console messages SXPL062 Message lines PLM(#62): ERROR: LV can not be reorganized, reason: . It was set to inaccessible at the PLM. Meaning The PLM attempts to reorganize an LV. This LV is unknown to the VLM or in the “faulty” status and can therefore not be read in. To prevent reorganization from being obstructed, the PLM sets this LV to “inaccessible”.
PAGE 482
Message lines Explanation of console messages 9.2.14 SXPS... (PLS: Physical Library Server) For the messages SXPS000 to SXPS008 of the robot software, only error numbers #4000 - #4008 are described because these error messages are dependent on the robot. The various error messages for robot types supported by at the current time are no longer individually listed. SXPS000 PLS(#4000) ERROR: 'vsn': i This message may also be issued if 'vsn' is jammed in a drive.
PAGE 483
Explanation of console messages SXPS006 Message lines PLS(#4006) ERROR: Meaning A general robot error which is not necessarily traceable to a device or a cassette. The meaning of the error message can be found in the relevant robot documentation. Response The robot error messages are mostly self-explanatory.
PAGE 484
Message lines SXPS996 Explanation of console messages PLS 996 NOTICE "Stop %s for Maintenance." Meaning %s stands for: PLS name (e.g. PLS1, ...). The PLS process %s was stopped via a menu in the graphical user interface. PLS 997 NOTICE "%s automatically restarted %s after %d tries." Meaning %s stands for: PLS name (e.g. PLS1, ...). The PLS process %s was automatically restarted after %d attempts. PLS 998 NOTICE "%s automatically restarted." Meaning %s stands for: PLS name (e.g. PLS1, ...).
PAGE 485
Explanation of console messages Message lines 9.2.15 SXRD... (FibreCAT: RAID) The table below shows the message numbers with the RAID systems which issue the messages: 9.2.15.
PAGE 486
Message lines SXRD001 Explanation of console messages NOTICE: raidd: 0:0:1 - disk state changed (Dead -> Write-Only) Meaning A rebuild is active for the physical disk of controller 0, channel 0, target ID 1. SXRD001 NOTICE: raidd: 0:0:1 - disk state changed (Dead -> Online) Meaning A rebuild was successful for the physical disk of controller 0, channel 0, target ID 1. All the associated logical disks are fully operational (redundant) again.
PAGE 487
Explanation of console messages SXRD001 Message lines ALERT: raidd: c50d0 - state is Critical Meaning This message is only generated when the raidd is started at system boot. The logical disk 0 on controller 0 no longer provides any redundancy. This indicates a hardware problem with a physical disk belonging to the addressed logical disk. Response Notify maintenance staff. SXRD001 ALERT: raidd: c50d0 - state is Offline Meaning This message is only generated when the raidd is started at system boot.
PAGE 488
Message lines SXRD104 Explanation of console messages WARNING: raid 0:1:0 - Disk: Write-Only, 17300 MB Meaning A rebuild is active for the physical disk of controller 0, channel 1, target ID 0. 9.2.15.2 SXRD00 FibreCAT S80 messages s80d: RAID: : Raid enclosure Meaning If there is a status change in a S80 component, a message will be output on the console.
PAGE 489
Explanation of console messages Message lines Response In the event of a message with the error weight ALERT: Notify maintenance staff. Example SXRD003 s80d: RAID: ALERT: #212215 Enclosure 3, Power Supply 2 Critical Connection between status and error weighting: OK Warning Not Available Unknown Critical Not Installed NOTICE WARNING ERROR ERROR ALERT ALERT Messages with the error weighting ALERT trigger a teleservice call.
PAGE 490
Message lines 9.2.15.4 SXRD501 Explanation of console messages FibreCAT CX500 and CX3-20 messages RAID: NOTICE Hard SCSI Error recovered (<#501>) ctl Where: ctl ID of the FibreCAT (target # of the two RAID controllers) Path via which the message was transferred (ctrl = controller#, tgt = target#, lun = logical device) Meaning Access via the specified path is possible again (positive message, cf. SXRD901).
PAGE 491
Explanation of console messages Message lines 9.2.16 SXRP... (RPLM: Recovery Physical Library Manager) SXRP003 RPLM(#3): ALERT: on not reachable Meaning It was not possible to send a message to the PDS on the host . Response Check whether the PDS and/or host are running and whether the TCP/IP connection is okay. If the corresponding IDP is running but the connection is not working, check the cables and the hubs. Notify maintenance staff if necessary.
PAGE 492
Message lines SXRP015 Explanation of console messages RPLM(#15): ERROR: reports sense = on PV Meaning The PDS has reported an error code for the physical volume . Response Notify maintenance staff. SXRP016 RLM(#16): ERROR: reports error = on PV Meaning The PDS has reported a class-3 error (ERR_PDS_03...).
PAGE 493
Explanation of console messages SXRP019 Message lines RPLM(#19): NOTICE: job canceled on PDS , PV , state Meaning The PLS or the PDS could not execute a job because of a timeout. Describes the command in which the timeout occurred. For the PLS: PLS_INSPECT MOUNT UMOUNT For the PDS: PDS_INSPECT RDIR INIT UNLOA The command is extended by the suffix _SENT_TIMECHECK.
PAGE 494
Message lines SXRP051 Explanation of console messages RPLM(#51): ERROR: reports errno = ( ) on PV Meaning The PDS has detected an error. Response Notify maintenance staff if necessary. SXRP052 RPLM(#52): NOTICE: PLS reports VOLUME ERROR for PV , PV-file will be removed Meaning The physical library does not know this PV. Response Check the VSN of the PV, correct it, and notify the robot of the new VSN. 9.2.17 SXSB...
PAGE 495
Explanation of console messages SXSB007 ALERT Message lines : fcpal (sadm): timeout on target lun CDB i For more information, see the section “Timeout on the RAID disk array” on page 538 and section “Timeout on the MTC drives” on page 539. Meaning An I/O operation has taken too long (minutes!), and as a result has been stopped and started again. Response Notify maintenance staff. 9.2.18 SXSC...
PAGE 496
Message lines SXSD017 ALERT shdt: Explanation of console messages cmd "Read" @ blk key "Medium Error" (0x03) asc .... Meaning Irrecoverable read errors occur sporadically on the FibreCAT RAID disk array despite mirroring. Response Notify maintenance staff. SXSD018 shdt: Target vanished See the section “Failover at the RAID system” on page 541 9.2.20 SXSE...
PAGE 497
Explanation of console messages Message lines 9.2.21 SXSM... (Server Management) The term “sma#” used in this description is a collective term for the process names “sma”, “sma02”, “sma03”, “sma04”, “sma05” and “sma06” which are specified in the error messages in accordance with the hardware type of the SINIX server. With the fan messages, the fan IDs have the following meaning: SysFanx Cpux Fan PSx Fan System fan number x (e.g. SysFan3) CPU fan number x (e.g. Cpu0 Fan) Power supply fan number x (e.
PAGE 498
Message lines Explanation of console messages Depending on the Primergy type the server will be reactivated after the wait time specified in the BIOS setup and the system started up. This mechanism is governed by the “ASR&R Boot Delay” and “Boot Retry Counter” entries in the BIOS setup. Response Notify maintenance staff.
PAGE 499
Explanation of console messages SXSM010 ALERT SXSM010 ALERT Message lines sma#: Memory Module disabled sma#: Memory Module disabled; Module# = Meaning Memory module is in the “disabled” state. This can be caused by the following: a) The memory module was disabled in the BIOS setup. b) The memory module was enabled in the BIOS setup, but has been disabled because of too many memory errors. Response Notify maintenance staff.
PAGE 500
Message lines SXSM018 ALERT Explanation of console messages sma#: Fan : Fan is not manageable Meaning Fan has failed and must be replaced. If the fan is inoperable for more than 3 minutes, the SINIX system is shut down and the server deactivated to prevent the server from overheating. Response Notify maintenance staff. SXSM019 ALERT sma#: Fan : Removable fan is not installed Meaning Fan is not installed or has failed.
PAGE 501
Explanation of console messages SXSM026 ALERT Message lines sma#: Voltage is too low Meaning The voltage with ID is too low. This message can also be triggered by faulty regulators, sensors, batteries or power supplies. Response Notify maintenance staff. SXSM027 ALERT sma#: Voltage is too high Meaning The voltage with ID is too high. This message can also be triggered by faulty regulators, sensors, batteries or power supplies. Response Notify maintenance staff.
PAGE 502
Message lines Explanation of console messages If the fan is inoperable for more than 3 minutes, the SINIX system is shut down and the server deactivated to prevent the server from overheating. Response Notify maintenance staff. SXSM033 ALERT sma#: Fan : Fan was removed Meaning Fan has been removed or has failed. If the fan is inoperable for more than 3 minutes, the SINIX system is shut down and the server deactivated to prevent the server from overheating. Response Notify maintenance staff.
PAGE 503
Explanation of console messages SXSM036 ALERT Message lines sma#: CPU internal error occurred Meaning An internal error was detected in CPU . Response Notify maintenance staff. SXSM037 ALERT sma#: Fan connection to fanboard defective Meaning The cable connection from the motherboard to the fan board does not exist or is defective. Response Notify maintenance staff.
PAGE 504
Message lines SXSM042 ALERT Explanation of console messages sma#: Memory Error Logging limit reached Meaning The limit for the Memory Error Log was reached because of too many correctable memory errors. No further correctable memory errors are recorded. Response Notify maintenance staff. SXSM043 ALERT sma#: Memory Module configuration error; [Module# = ] Meaning The memory configuration is errored. Response Notify maintenance staff.
PAGE 505
Explanation of console messages Message lines Response Notify maintenance staff. SXSM046 ALERT sma#: PCI system error; bus# ; device# ; function# Meaning A PCI system error is indicated by an onboard device. The onboard device is indicated by the bus/device/function parameters. Response Notify maintenance staff. SXSM047 ALERT sma#: PCI Bus correctable error at slot Meaning A correctable PCI bus error has occurred at slot number . Response Notify maintenance staff.
PAGE 506
Message lines SXSM049 ALERT Explanation of console messages sma#: Primergy Product Serial Number not available Meaning The product serial number of the Primergy is not available. This can be caused by the following: a) The product serial number is not entered in the Primergy IdProm (e.g. after the ID chip has been replaced). b) The ID chip is defective. c) The connection (cable/connector) to the IdProm is defective. Response Notify maintenance staff.
PAGE 507
Explanation of console messages Message lines Response Notify maintenance staff. SXSM054 ALERT sma#: CPU automatically throttled Meaning The CPU performance has been reduced because the CPU temperature was high. This is designed to prevent the CPU from becoming any hotter and entering the critical temperature range. The increase in the CPU temperature can, for example, be caused by a fan which is no longer fully operational (e.g. if a fan prefailure has occurred). Response Notify maintenance staff.
PAGE 508
Message lines Explanation of console messages Response Check the ambient temperature and the fan situation. Notify maintenance staff iff no connection to increased ambient temperatures or fan faults could be determined and this message continues to appear.
PAGE 509
Explanation of console messages SXSM501 ALERT Message lines sma#: BIOS Boot Retry Counter countdown occurred - maybe watchdog timeout Meaning The Boot Retry Counter1 (BIOS setup, menu item Server) has timed out. Response Notify maintenance staff. SXSM502 ALERT sma#: Internal error at communication with autoss Meaning Internal communication to the autoss process (for shutting down the system) is down. One reason for this could be that autoss has been terminated. Response Notify maintenance staff.
PAGE 510
Message lines Explanation of console messages 9.2.22 SXSW... (Software Mirror) SXSW010 SWM(#10): ALERT: mirror degrade: failed Meaning Part of the mirror (, primary or secondary) has failed. As the device is designed with redundancy, operations can continue. However, the remaining part is no longer failsafe. To restore failsafe performance, the failed part should be repaired. Response Notify maintenance staff.
PAGE 511
Explanation of console messages SXTF003 Message lines ERROR: dtv_ipalloc: dtv_ipsize too big, set to Meaning The value of the Inode pool size that can be configured using space.c is invalid and is replaced by the maximum permitted value. The result is that the maximum permitted value is used. Response Notify maintenance staff.
PAGE 512
Message lines SXTF004 Explanation of console messages WARNING: dtv_mount: setopt(CLUSTER_READS) failed! Meaning The disk controller intended as the volume cache cannot perform cluster read operations. This error should only occur during test operation if no RAID controller is available. Performance may be reduced. Response Notify maintenance staff if message occurs during normal operation. SXTF004 WARNING: dtv_balloc(buf): i/o cache full! Meaning Warning; performance may be impaired.
PAGE 513
Explanation of console messages SXTF005 SXTF005 Message lines NOTICE: dtv_iread: root directory stale! NOTICE: dtv_rdlookup: root directory stale: , ino= Meaning These error messages indicate that, due to manual intervention, the image of the root directory stored in the working memory is no longer up to date. This does not impair operation but, if it occurs frequently, there will be a loss of performance because the root directory has to be read in again.
PAGE 514
Message lines SXTF005 SXTF005 Explanation of console messages NOTICE: dtv_iread(: ino=): root directory stale! NOTICE: dtv_rdlookup(: ino=): root directory stale! Meaning When reading in a file or searching the root directory on a DTV client system (e.g. ICP), it was determined that the specified file has been deleted or renamed at some point. As a result, the root directory is reloaded.
PAGE 515
Explanation of console messages SXTF006 Message lines PANIC: dtv_iactive(: inode(s) in use Meaning The file system has been unmounted even though it was currently in use. This results in a system crash. Response Notify maintenance staff if necessary. SXTF007 ERROR: :\ illegal value for variable , use default Meaning The value of a variable configurable using space.c is invalid. As a result, the variable is set to the default value.
PAGE 516
Message lines SXTF011 Explanation of console messages DTV_FSCK(dev=): ... Meaning Normal output of the implicit file system check carried out when mounting a DTV file system. 9.2.24 SXVD... (Distributed Tape Volume Driver) SXVD001 ERROR vdrv (FAILOVER): switch ... See the section “Failure of RAID systems” on page 540 and the section “Failover at the RAID system” on page 541.
PAGE 517
Explanation of console messages Message lines 9.2.25 SXVL... (VLM: Virtual Library Manager) SXVL001 VLM(# 1): ALERT: ???: cannot register as supervisor - not mounted ? Meaning The VLM cannot log on as supervisor for a specific cache filesystem. The reason for this is usually that the filesystem specified in the error message is not mounted. You can use the mount command to determine whether the filesystem is mounted. The named filesystem must be present in the output list.
PAGE 518
Message lines SXVL006 Explanation of console messages VLM(# 6): ERROR: volume ??? set to 'Faulty' (???) Meaning This error can have a number of different causes. It is usually caused by problems accessing the DTV filesystem. Further details can be found in the logging information. Response The logical volume can be reset using the XTCC function “Reset Logical Volume”. However, you should first check the cause as it may then be necessary to check the data on the volume.
PAGE 519
Explanation of console messages SXVL013 Message lines VLM(#13):ALERT: FATAL: database inconsistencies ! Meaning Inconsistencies have occurred in the VLM data maintenance system. Response Notify maintenance staff! SXVL014 VLM(#14): FATAL: more files in cache X than allowed: NNN (max.
PAGE 520
Message lines SXVL020 Explanation of console messages VLM(#20): ALERT: vtls.conf: SCRATCH_LABEL_: wrong format Meaning When the VLM was started errors were found in configuration file vtls.conf. The VLM is terminated. Response Notify maintenance staff. SXVL021 VLM(#21): ALERT: vtls.conf: SCRATCH_BLOCK: wrong format Meaning When the VLM was started errors were found in configuration file vtls.conf. The VLM is terminated. Response Notify maintenance staff.
PAGE 521
Explanation of console messages SXVL997 Message lines VLM 997 NOTICE "Automatically restarted after %d tries." Meaning The VLM was automatically restarted after %d attempts. SXVL998 VLM 998 NOTICE "Automatically restarted." Meaning The VLM was automatically restarted. SXVL999 VLM 999 ALERT "Auto restart %d times failed. Intervention required." Meaning The VLM could not be restarted even after %d attempts. Manual intervention is required. 9.2.26 SXVLS...
PAGE 522
Message lines Explanation of console messages 9.2.27 SXVS... (VLS: Virtual Library Server) SXVS995 VLS(#995): NOTICE "%s started." Meaning %s stands for: VLS name (e.g. VA02, VC03, etc.). The VLS process %s was started via a menu in the graphical interface. SXVS996 VLS(#996): NOTICE "Stop %s for Maintenance." Meaning %s stands for: VLS name (e.g. VA02, VC03, ...). The VLS process %s was stopped via a menu in the graphical user interface.
PAGE 523
Explanation of console messages Message lines 9.2.28 SXVW... (VLPWATCH) VLP failover messages SXVW001 VLPWATCH: ALERT: AutoVLP-Failover: switch SVLP_to_VLP successfully completed! Meaning The switchover from the SVLP to the VLP has been successfully completed. SXVW002 VLPWATCH: ALERT: AutoVLP-Failover: SVLP is not alive! Meaning The AutoVLP function is active on the VLP. The VLP has detected that there is no sign of life from the required SVLP.
PAGE 524
Message lines SXVW007 SXVW007 SXVW007 Explanation of console messages VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: Raid1 (cache 100 | 101) not mounted! VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: connection to LAN and start of vtls prevented! VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: please correct the Raid1-connection and reboot the system! Meaning No connection to RAID1 could be set up. Mounting of the tape file system is forbidden.
PAGE 525
Explanation of console messages Message lines Response Rectify the LAN connection problems and reboot the ISP. SXVW012 VLPWATCH: ALERT: VW(#012) AutoVLP-Failover: FC connection to RAID is DOWN; shutdown! Meaning There is no connection to the 1st RAID system. A shutdown with Power OFF was performed for the ISP. Response Rectify the RAID problems and reboot the ISP.
PAGE 526
Message lines Explanation of console messages Response The function should already have been stopped on the VLP; if it has not been, it must be stopped on the VLP. The additional messages must be taken into account; detailed information is stored in the log_VLPwatch and log_vlpwatch files in the logging directory /etc/vtls/log. The function can then be restarted via the interface.
PAGE 527
Explanation of console messages SXVW020 Message lines VLPWATCH: ALERT: VW(#020) AutoVLP-Failover: VLPwatch is started first on SVLP Meaning The VLPwatch monitoring wizard was started on the SVLP first. This is not permissible. (Can only be done in the case of manual activation.) Response Restart the AutoVLP failover function via the interface. SXVW021 VLPWATCH: ALERT: VW(#021) AutoVLP-Failover: check of /etc/vfstab failed Meaning Incorrect configuration of the caches and DB.
PAGE 528
Message lines Explanation of console messages Response If the VLP and SVLP are running correctly automatic switchover should be initiated manually. SXVW026 VLPWATCH: ALERT: VW(#026) switch VLP/SVLP to SVLP/VLP timed out - reboot! Meaning The switchover from the VLP to the SVLP or from the SVLP to the VLP cannot be completed. The ISP is rebooted. Response A reboot is the automatic response.
PAGE 529
Explanation of console messages SXVW031 SXVW031 Message lines VLPWATCH: ALERT: VW(#031) AutoVLP-failover: internal or external LAN connection is not configured; terminated! VLPWATCH: ALERT: VW(#031) AutoVLP-failover: please correct the LAN-connection and reboot the system! Meaning Less than 2 LAN interfaces are configured, and this means that the internal or external LAN is not configured. Response Check the LAN configuration and configure the missing interface.
PAGE 530
Message lines SXVW038 Explanation of console messages VLPWATCH: NOTICE: VW(#038) AutoVLP-Failover: VLP is alive: wait max. 180 seconds before a failover, if VLP is not alive Meaning The VLP has already provided a sign of life in the extended monitoring time of 7 or 5 minutes in the boot or start phase; the monitoring time is now reduced to 3 minutes (default). This message can only occur on the current SVLP.
PAGE 531
Explanation of console messages SXVW046 Message lines VLPWATCH: NOTICE: VW(#046) AutoVLP-failover: SVLP is alive! Meaning The VLP logs that the SVLP is available. SXVW047 VLPWATCH: ALERT: VW(#047) AutoVLP-failover: SVLP is not alive! Meaning The VLP logs that the SVLP is not available. Response The SVLP and its connections to the VLP must be checked.
PAGE 532
Message lines SXVW053 Explanation of console messages VLPWATCH: NOTICE: VW(#053) AutoVLP-Failover: system error of getx2kvp()! Meaning An error occurred while checking the license. Response Check the license. SXVW054 VLPWATCH: NOTICE: VW(#054) AutoVLP-Failover: error of %d=getx2kvp()! Meaning An error occurred while checking the license. Response Check the license.
PAGE 533
Explanation of console messages SXVW058 Message lines VLPWATCH: ALERT: VW(#058) AutoVLP-Failover: LAN_1 connection is DOWN on SVLP; Failover not functional! Meaning The SVLP has no connection to the external LAN. The AutoVLP failover function is not working. Response Investigate and correct the LAN connection problem.
PAGE 534
Message lines SXVW064 Explanation of console messages VLPWATCH: NOTICE: VW(#064) AutoVLP-Failover: only one mirror-side is accessible wait maximum %d minutes to see an update of the timestamp of SVLP Meaning In the boot phase it is detected that only one mirror side is available. The situation and the time stamp of the SVLP are monitored. If the timeout of up to 5 minutes has elapsed, a required action is initiated and logged accordingly.
PAGE 535
Explanation of console messages SXVW068 Message lines VLPWATCH: ALERT: VW(#068) AutoVLP-Failover: internal or external LAN connection is not configured! Meaning The internal or external LAN connection is broken. The function cannot work properly. Response Check the LAN connection and make sure it works correctly. SXVW069 VLPWATCH: ALERT: VW(#069) -Failover: shutdown, because an error occurred! Meaning As a consequence of previous messages the is system shut down (power off). Response Reboot the ISP.
PAGE 536
Message lines SXVW073 Explanation of console messages VLPWATCH: ALERT: VW(#073) AutoVLP-Failover: VLPwatch on is running, communication to is defective (internal LAN or Broker on down)! Meaning VLPwatch on the SVLP is running, but communication to the SVLP via the Broker has been interrupted. The Broker on the SVLP is not running or the internal LAN on the SVLP is interrupted. Response Determine the Broker status and the internal LAN status on the SVLP.
PAGE 537
Explanation of console messages Message lines 9.2.29 SXVX... (Veritas File System) SXVX001 WARNING: vxfs: vx_idelxwri_done - inode 487921 on /usr had a write error at offset 147456 Meaning When trying to write FS meta information (i.e. inodes) to disk, an IO error happened. The file denoted by the inode number will not be updated properly and information is lost. Response You may use find /usr -inum 487921 -print to find out which file was damaged. The ls -i command will report inode numbers also.
PAGE 538
Message complexes Explanation of console messages 9.3 Message complexes 9.3.1 Timeout on the RAID disk array SXSB007 ALERT fcpal0 (sadm12): timeout on target lun CDB ....F C0 00 01 80 00 0007b790: fc_send_fcp: FCP_ABORT...
PAGE 539
Explanation of console messages Message complexes 9.3.2 Timeout on the MTC drives SXSB007 ALERT adsl1 (sadm): timeout on target lun CDB .... or SXSB007 ALERT adsl2 (sadm): timeout on target lun CDB ....
PAGE 540
Message complexes Explanation of console messages 9.3.3 Failure of RAID systems SXVD001 SXVD001 SXVD002 vdrv (FAILOVER): switch 0:40->1:41 vdrv (FAILOVER): switch 1:41->0:40 vdrv (FAILOVER): Error exit 0130002A E54EC000 Meaning Both RAID controllers have failed. A failover (1st line) and switchback (2nd line) have been performed but both without success; the RAID disk array with the next highest minor number can no longer be accessed.
PAGE 541
Explanation of console messages Message complexes 9.3.4 Failover at the RAID system SXSD018 shdt: Target vanished or SXSD015 shdt: cmd "Write or Read" @ blk key "Not Ready" (0x02) asc "Drive Not Ready" (0x04) ascq 0x02 WARNING followed by SXVD004 SXVD001 vdrv (FAILOVER): int switching vdrv (FAILOVER): switch 0:4->1:5 but not followed directly by another “switch” message. Meaning Normal failover.
PAGE 542
Message complexes Explanation of console messages 9.3.5 Bus Reset for SCSI Controller SXCM001 None SXSB001 None SXSB005 None chim1 (sadm9): SCSI-Bus reset chim1 (sadm9): SCSI-Bus reset chim1 (sadm9): RESETTING CONTROLLER Meaning A bus reset was triggered for SCSI controller 9 (in this example, chim/Adaptec controller 1).
PAGE 543
10 Waste disposal and recycling CentricStor is a product with a long life. The decisive factors here are not just the expansion options but also the quality. However development is ongoing. Amounts of data which can hardly be foreseen today will have to be processed in the future. The demands on storage space, speed and design of computers are increasing.
PAGE 544
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 545
11 Contacting the Help Desk The telephone numbers for the Fujitsu Siemens Computers Help Desk can be found at the following URL: http://www.fujitsu-siemens.com/helpdesk When you call, please have the serial number of your device available.
PAGE 546
Eine Dokuschablone von Frank Flachenecker by f.f.
PAGE 547
12 Appendix 12.1 Integration of CentricStor V3.1 in SNMP This document describes how CentricStor can be monitored using SNMP. What does the system administrator need to configure on the CentricStor side for this purpose, and what can be monitored? An installation package is available from FSC specifically for the SNMP Management Station CA Unicenter. The customer is provided with comprehensive support for installation on CA Unicenter (NMS Version 3.0) under Microsoft Windows through installation scripts.
PAGE 548
Integration of CentricStor V3.1 in SNMP Appendix 12.1.2 Activating SNMP on CentricStor 12.1.2.1 Configuring SNMP under CentricStor The CentricStor system’s VLP establishes the connection to the outside world. Consequently SNMP only needs to be configured on this processor. If a standby VLP exists (VLP1), SNMP configuration must also be performed on this processor. To configure SNMP the system administrator logs on to the VLP under “root” and calls sysadm.
PAGE 549
Appendix Integration of CentricStor V3.1 in SNMP 12.1.3 Monitoring CentricStor 12.1.3.1 GXCC as a monitoring tool without SNMP i This item is totally independent of SNMP and indicates that GXCC is fundamentally an effective monitoring tool. GXCC and XTCC together with Tcl/Tk must be installed from the GUI CD supplied with CentricStor. If Tcl/Tk is already installed and is not to be overwritten, Tcl/Tk is installed in an arbitrary directory. On Windows systems, Tcl/Tk is a part of GXCC.
PAGE 550
Integration of CentricStor V3.1 in SNMP Appendix With it a simple statement can be provided on the operating condition of CentricStor: turquoise: CentricStor is working (OK) yellow: CentricStor is working with restrictions (degraded, attention) pink: CentricStor is in fail state The “Global System State” is shown by a colored square in the bottom line of the GXCC. If the mouse is positioned on this square, more details of the current state are shown in the form of a Balloon Help. 12.1.3.
PAGE 551
Appendix 12.1.3.3 Integration of CentricStor V3.1 in SNMP CentricStor Global System State Every 300 seconds the Global System State (see the section “GXCC as a monitoring tool without SNMP” on page 549) of CentricStor is sent via a trap. It is not meaningful to write this trap onto the SNMP Management Station. This trap is designed to control the color of the ICON. The format of this trap is identical to the CentricStor Trap. The various bindings are set as follows: ObjectID: Specific Trap #: Var.
PAGE 552
Integration of CentricStor V3.1 in SNMP 12.1.3.6 Appendix Monitoring of CentricStor V2/V3.0 and V3.1 If an SNMP Management Station is required to monitor a CentricStor V3.1 and a CentricStor V2/V3.0 simultaneously, the following applies: On the Management Station the GUI CD of CentricStor V3.1 is read in as described here. The V3.1 systems can be monitored as described. As the V2/V3.
PAGE 553
Appendix 12.1.4.2 Integration of CentricStor V3.1 in SNMP Installation of the CA Unicenter extensions for CentricStor Tools for adding and deleting CA Unicenter extensions were stored under Start -> Programs -> Fujitsu Siemens Computers -> Tape Control Center -> Setup through the installation of the GUI CD 2. The tool Add CentricStor to CA Unicenter must be called to install the extensions. This tool stores all associated files which are needed for CA Unicenter operation in the associated directories.
PAGE 554
Integration of CentricStor V3.1 in SNMP Appendix 12.1.5 Working with CA Unicenter and CentricStor 12.1.5.1 CentricStor icon under CA Unicenter The following icon was selected for CentricStor in 3-D format: It contains the texts Fujitsu Siemens and CentricStor.
PAGE 555
Appendix Integration of CentricStor V3.1 in SNMP In 2D format CentricStor is represented as follows: The Global System State trap is automatically set to green, yellow or red. 12.1.5.2 Identifying a CentricStor and assigning the icon After the add-ons have been activated with Add CentricStor to CA Unicenter, a CentricStor System is automatically recognized in the Unicenter-Discovery and is assigned to the fscCentricStor class with the appropriate icon.
PAGE 556
Integration of CentricStor V3.1 in SNMP 12.1.5.3 Appendix Receipt and preparation of a CentricStor trap On receipt of CentricStor traps, messages are output on the Event Console. The standard traps (e.g. coldStart) are issued without special preparation and appear on the Event Console with the lead text %CATD_I_060, SNMPTRAP:.
PAGE 557
Appendix 12.1.5.4 Integration of CentricStor V3.1 in SNMP Monitoring CentricStor using ping and MIB-II All objects entered in CA Unicenter are automatically moitored by means of ping and MIB-II. This requires that the agent “Mib2” works with the right community. The administrator must make any necessary adjustments in the Pollset Browser of CA Unicenter. 12.1.5.
PAGE 558
E-mail support in CentricStor Appendix 12.2 E-mail support in CentricStor 12.2.1 Sendmail configuration sendmail is started only if the configuration file /etc/mail/sendmail.cf exists. This file is not generated, but under certain conditions it is modified to correct errors. During installation a sample file is created under /etc/mail/sendmail.cf.sample which can be used as /etc/mail/sendmail.cf. This file may need to be adapted.
PAGE 559
Appendix E-mail support in CentricStor – In the file /etc/netconfig, the entries which have “inet” in the 4th column must be complemented by the entry “,/usr/lib/resolv.so” in the last (7th) column. Example Thus (the separator is the tabulator!) tcp tpi_cots_ord v inet tcp /dev/tcp /usr/lib/tcpip.so udp tpi_clts vb inet udp /dev/udp /usr/lib/tcpip.so rawip tpi_raw - inet - /dev/rawip /usr/lib/tcpip.so icmp tpi_raw - inet icmp /dev/icmp /usr/lib/tcpip.
PAGE 560
E-mail support in CentricStor Appendix 12.2.3 Configuring the e-mail template The configurable data of the e-mail can be set in e-mail-format-specific configuration files. The configuration file must be created by copying a sample file and then be adapted to the conditions. If a customer-specific configuration file exists for an e-mail format, an e-mail is created and sent in accordance with the configuration file.
PAGE 561
Appendix E-mail support in CentricStor The normal procedure is for an e-mail to be sent starting with the error weight ERROR. In the case of the error weights NOTICE and WARNING, only very few, specially selected messages are offered for e-mail dispatch, for example SXPL027 (page 476), SXPL049 (page 479) and SXPL050 (page 479). 12.2.4 Description of the e-mail formats The sample file has the name: /usr/apc/bin/msg_mail.config.
PAGE 562
Transferring volumes Appendix 12.3 Transferring volumes 12.3.1 Introduction A transfer enables LVs to be exported from a CentricStor system and imported into another CentricStor. For the export these LVs are temporarily copied into the special LV group TR-LVG using “plmcmd trans …” commands and saved on PVs of the special PV group TR-PVG. These PVs can then be removed and transported to another CentricStor.
PAGE 563
Appendix Transferring volumes 12.3.2 Export procedure 1. Copying LVs TR-LVG LVG1 LVG2 A00001 Z10000 A00001 Z10000 plmif trans -o -v A00001,Z10000 TR-PVG A00001 Z10000 Figure 36: Copying an LV to TR-PVG With the aid of the transfer-out command (see the section “Transfer-out” on page 566), the PLM creates an additional copy of the LVs selected for export in a special transfer LVG, theTR-LVG.
PAGE 564
Transferring volumes Appendix The transfer volume groups TR-LVG and TR-PVG are now ready for another transfer. 3. Removing PVs from a library The PVs determined above can now be physically removed from the library using a DAS or ACSLS command (see the section “Library commands” on page 571). The existing copies of these LVs on other PVs when Mono Save or Dual Save is used remain unaffected by the transfer: These copies are retained in the physical library unchanged.
PAGE 565
Appendix Transferring volumes 12.3.4 Special features of the PVG TR-PVG ● PVs in the unknown status cannot be deleted using plmif conf -e ... . ● No reorganization takes place, neither can it be initiated using a command. ● Limits: PV_SCRATCH_SOFT_MIN: not observed PV_SCRATCH_HARD_MIN: 2 PV_SCRATCH_MIN: -1 ● Similarly to cleaning groups, no configuration parameters are output in response to plmif query -c. ● No values for this group are forwarded to the InfoBroker.
PAGE 566
Transferring volumes Appendix 12.3.5 Additional command line interface (CLI) 12.3.5.1 Transfer-out plmif trans -o ( -t HH:MM [-g ] | -v [,]* | -f : ) A transfer-out is initiated using this command. – The PLM causes LVs which are located in normal LVGs to be copied to the special LVG TR-LVG. The LVs are not moved, which means that the originals are still present after the transfer-out. – The LVs are copied from the TVC to the PVs.
PAGE 567
Appendix Transferring volumes Example of an output when no transfer-out is active AZUR-VLP0# plmif query -g pos LV-Group PVGroup1 1 A P16 2 BASE BASE 3 C P19 4 D ====== 5 TR-LVG TR-PVG 6 ksp ====== PVGroup2 ====== ====== ====== ====== ====== ====== LVs 10010 0 10000 0 0 0 pending jobs 0 0 0 0 0 0 recover jobs 0 0 0 0 0 0 Example of the start of a transfer-out AZUR-VLP0# plmif trans -o -v EXIM00,EXIM01,EXIM02 LV EXIM00 scheduled for transfer. LV EXIM01 scheduled for transfer.
PAGE 568
Transferring volumes Appendix Example of an output after termination of the transfer-out AZUR-VLP0# plmif query pos LV-Group PVGroup1 1 A P16 2 BASE BASE 3 C P19 4 D ====== 5 TR-LVG TR-PVG 6 ksp ====== 12.3.5.
PAGE 569
Appendix Transferring volumes If the VLM does not know the LV, no restore command is issued to the PLM for the purpose of actually reading in the LV. The PLM therefore waits for an unlimited time, and no progress can be recognized when you query the jobs (plmif query -j -G TR-PVG). You can then either create this LV in the LVG, or skip this LV using the transfer-in cancel command (see the section “Skipping an LV / removing a PV” on page 570).
PAGE 570
Transferring volumes 12.3.5.4 Appendix Removing an LV from a transfer list plmif trans -o -c [ -v ] This command enables an LV to be removed from the list of LVs to be transferred. If it has already been transferred, the command is rejected. If no LV is specified, the entire transfer-out is aborted. Existing save requests are still processed. Example AZUR-VLP0# plmif trans -o -c transfer-out cancelled. 12.3.5.
PAGE 571
Appendix Transferring volumes 12.3.7 Library commands 12.3.7.1 ADIC library with DAS server ejects cartridges from the AML [via the eject area] dasadmin eject2 [-c] [-t media-type] volserrange area inserts [normal data] cartridges [via the insert area] in the AML dasadmin insert2 -n area Further information is provided in the DAS manual. 12.3.7.2 StorageTek Library with ACSLS server Eject volumes [of a cartridge pool] eject cap_id vol_id | volrange ...
PAGE 572
Licenses Appendix 12.4 Licenses All licenses dealed with the Open Source Software in CentricStor are listed below. 12.4.1 Xpdf, gzip GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 12.4.1.
PAGE 573
Appendix Licenses Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents.
PAGE 574
Licenses Appendix b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
PAGE 575
Appendix Licenses The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
PAGE 576
Licenses Appendix It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices.
PAGE 577
Appendix Licenses PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12.
PAGE 578
Licenses Appendix If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License.
PAGE 579
Appendix Licenses 12.4.2 Firebird INTERBASE PUBLIC LICENSE Version 1.0 1. Definitions. 1.0.1. “Commercial Use” means distribution or otherwise making the Covered Code available to a third party. 1.1. “Contributor” means each entity that creates or contributes to the creation of Modifications. 1.2. “Contributor Version” means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.3.
PAGE 580
Licenses Appendix 1.10.1. “Patent Claims” means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. 1.11.
PAGE 581
Appendix Licenses 2.2. Contributor Grant.
PAGE 582
Licenses Appendix via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. 3.3. Description of Modifications.
PAGE 583
Appendix Licenses 3.5. Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A.
PAGE 584
Licenses Appendix 4. Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.
PAGE 585
Appendix Licenses 6.4 Origin of the Interbase Public License. The Interbase public license is based on the Mozilla Public License V 1.1 with the following changes: 1. The license is published by Borland Software Corporation. Only Borland Software Corporation can modify the terms applicable to Covered Code. 2. The license can be modified used for code which is not already governed by this license.
PAGE 586
Licenses Appendix 8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as “Participant”) alleging that: (a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.
PAGE 587
Appendix Licenses TING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a “commercial item,” as that term is defined in 48 C.F.R. 2.101 (Oct.
PAGE 588
Licenses Appendix EXHIBIT A - InterBase Public License. ``The contents of this file are subject to the Interbase Public License Version 1.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.Interbase.com/IPL.html Software distributed under the License is distributed on an “AS IS” basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
PAGE 589
Appendix Licenses 12.4.3 Sendmail SENDMAIL LICENSE The following license terms and conditions apply, unless a different license is obtained from Sendmail, Inc., 6425 Christie Ave, Fourth Floor, Emeryville, CA 94608, USA, or by electronic mail at license@sendmail.com. License Terms: Use, Modification and Redistribution (including distribution of any modified or derived work) in source and binary forms is permitted only if each of the following conditions is met: 1.
PAGE 590
Licenses Appendix (b) Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: (i) Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. (ii) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
PAGE 591
Appendix Licenses IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of Daniel Veillard shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from him. 12.4.4.
PAGE 592
Licenses Appendix THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
PAGE 593
Appendix Licenses The following individuals contributed in part to the Network Time Protocol Distribution Version 4 and are acknowledged as authors of this work. 1. [1]Mark Andrews Leitch atomic clock controller 2. [2]Bernd Altmeier hopf Elektronik serial line and PCI-bus devices 3. [3]Viraj Bais and [4]Clayton Kirkwood port to WindowsNT 3.5 4. [5]Michael Barone GPSVME fixes 5.
PAGE 594
Licenses Appendix 29. [32]Louis A. Mamakos MD5-based authentication 30. [33]Lars H. Mathiesen adaptation of foundation code for Version 3 as specified in RFC-1305 31. [34]Danny Mayer Network I/O, Windows Port, Code Maintenance 32. [35]David L. Mills
PAGE 595
Appendix Licenses 9. mailto:%20Marc.Brett@westgeo.com 10. mailto:%20Piete.Brooks@cl.cam.ac.uk 11. mailto:%20reg@dwf.com 12. mailto:%20clift@ml.csiro.au 13. mailto:casey@csc.co.za 14. mailto:%20Sven_Dietrich@trimble.COM 15. mailto:%20dundas@salt.jpl.nasa.gov 16. mailto:%20duwe@immd4.informatik.uni-erlangen.de 17. mailto:%20dennis@mrbill.canet.ca 18. mailto:%20jhay@icomtek.csir.co.za 19. mailto:%20glenn@herald.usask.ca 20. mailto:%20iglesias@uci.edu 21. mailto:%20jagubox.gsfc.nasa.gov 22.
PAGE 596
Licenses Appendix 53. mailto:%20tsuruoka@nc.fukuoka-u.ac.jp 54. mailto:%20vixie@vix.com 55. mailto:%20Ulrich.Windl@rz.uni-regensburg.de 12.4.6 tcpd /************************************************************************ * Copyright 1995 by Wietse Venema. All rights reserved. Some individual * files may be covered by other copyrights.
PAGE 597
Appendix Licenses 12.4.8 openssh This file is part of the OpenSSH software. The licences which components of this software fall under are as follows. First, we will summarize and say that all components are under a BSD licence, or a licence more free than that. OpenSSH contains no GPL code. 1. * Copyright (c) 1995 Tatu Ylonen , Espoo, Finland * All rights reserved * * As far as I am concerned, the code I have written for this software * can be used freely for any purpose.
PAGE 598
Licenses Appendix The legal status of this program is some combination of all these permissions and restrictions. Use only at your own responsibility. You will be responsible for any legal consequences yourself; I am not making any claims whether possessing or using this is legal or not in your country, and I am not taking any responsibility on your behalf. NO WARRANTY BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
PAGE 599
Appendix Licenses * Ariel Futoransky * 3. ssh-keyscan was contributed by David Mazieres under a BSD-style license. * * * * * Copyright 1995, 1996 by David Mazieres . Modification and redistribution in source and binary forms is permitted provided that due credit is given to the author and the OpenBSD project by leaving this copyright notice intact. 4.
PAGE 600
Licenses Appendix * * * * * * * * * * * * * * * 3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED.
PAGE 601
Appendix Licenses Networks Associates Technology, Inc. Solar Designer Todd C. Miller Wayne Schroeder William Jones Darren Tucker Sun Microsystems The SCO Group * * * * * * * * * * * * * * * * * * * * Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2.
PAGE 602
Licenses Appendix c) Compatibility code (openbsd-compat) Apart from the previously mentioned licenses, various pieces of code in the openbsd-compat/ subdirectory are licensed as follows: Some code is licensed under a 3-term BSD license, to the following copyright holders: Todd C. Miller Theo de Raadt Damien Miller Eric P. Allman The Regents of the University of California Constantin S.
PAGE 603
Appendix Licenses * * * * * * * * * * * * * Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C.
PAGE 604
Licenses Appendix 12.4.9 openssl LICENSE ISSUES The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
PAGE 605
Appendix Licenses * * * * * * * * * * * * * * * * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
PAGE 606
Licenses Appendix * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * "This product includes cryptographic software written by * Eric Young (eay@cryptsoft.
PAGE 607
Appendix Licenses 12.4.10 tcl Copyright: This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
PAGE 608
Licenses Appendix 12.4.11 tk Copyright: This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
PAGE 609
Glossary AutoVLP failover function As the VLP Master plays a central role in the CentricStor system, failure of the VLP Master also causes the entire system to fail. To prevent this, a standby Standby VLP (SVLP) can be integrated into the system as a backup computer. This SVLP is inactive except for the monitoring function.
PAGE 610
Glossary Distribute and Activate ➟ DNA Distributed Tape Volume File System ➟ DTVFS DNA The Distribute and Activate (DNA) function must be invoked in GXCC every time a change is made to the configuration of the CentricStor system. This ensures that the new configuration is distributed to and activated on all the ISPs.
PAGE 611
Glossary The FC Layer Model has 5 layers which have the following names: – – – – – FC-0 (Physical Layer) FC-1 (Data Link Layer, coding/decoding the signals to be transferred) FC-2 (Network Layer, flow control, service classes) FC-3 (Common Services Layer, e.g. multicast, striping) FC-4 (Protocol Mapping Layer, e.g. FCP, FICON) FC Layer Model ➟ FC FCP FCP, like FICON, is a protocol of the uppermost layer FC-4 (Protocol Mapping Layer) in the FC Layer Model.
PAGE 612
Glossary Header At the start of each physical tape written by CentricStor there is an 80-byte header followed by a Tapemark. ICP In the CentricStor system the ICP is the interface to the host systems connected. These are connected using ESCON, FICON or FCP. The ICP’s principal task is to emulate the physical drives for the host systems connected. The predefined host names for this ISP type are ICP0, ICP1, etc.
PAGE 613
Glossary VLP VTC ISP which has neither a host nor a device port. Some central management processes, in particular VLM und PLM, run on this ISP. A CentricStor system can contain two VLP-ISPs. The central management processes then only run on one of these, the VLP Master. The other, the Standby VLP (SVLP), is inactive except for monitoring the VLP Master. In the small CentricStor models VTC and SBU this is the only ISP and combines the attributes of the ICP, IDP and VLP.
PAGE 614
Glossary Message Manager ➟ MSGMGR MSGMGR Exists once in CentricStor. Filters and saves the ISPs’ system messages and implements predefined measures (e.g. service call, sends SMS, etc.). The MSGMGR is also responsible for forwarding the system messages to the user interface. PERFLOG Exists once in each CentricStor. Obtains and stores the performance data. Global Status supplies the performance data.
PAGE 615
Glossary Redundant Array of Independent Disks ➟ RAID system Reorganisation Depending on the configuration paramters, the logical volumes (LVs) saved on the physical volumes (PVs) are automatically copied onto other physical volumes (PVs) of the same physical volume group (PVG).
PAGE 616
Glossary System Administrator Edition ➟ SAE Tape File System ➟ TFS Tapemark A tapemark identifies the end of a header or logical volume (LV) on a physical tape. Tape Volume Cache ➟ TVC TFS In CentricStor V3.1D a Tape File System (TFS) is a file system of the type dtvfs (DTVFS) in which the logical volumes (LVs) are stored temporarily. The Tape File Systems as a whole constitute the Tape Volume Cache (TVC).
PAGE 617
Glossary VLP Master The VLP Master is an ISP of the type VLP in which the central management processes, such as VLM and PLM, are active. VLP is sometimes used as a synonym for VLP Master. VLS The tape archives emulated in CentricStor are referred to as Virtual Library Services (VLS).
PAGE 618
Glossary VTC VTC is both an ISP type and the name of the smallest CentricStor model, which consists of precisely one ISP of this type. Like an ICP_IDP it combines the attributes of an ICP, IDP and VLP. In contrast to the ICP_IDP it is equipped with additional boards. These boards and an internal RAID controller are used to configure an internal RAID system which is used for the TVC. The predefined host name for this ISP type is VTC.
PAGE 619
Figures Figure 1: Conventional host robot system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 2: Host robot system with CentricStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 3: Example of a CentricStor configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Figure 4: Internal VLP connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 5: External and internal ICP connections .
PAGE 620
Figures Figure 23: Example of a CentricStor mirror system with 3 RAID mirror pairs . . . . . . . . 57 Figure 24: Primary and secondary caches in a RAID mirror pair . . . . . . . . . . . . . . . . . 57 Figure 25: Presentation of the mirror function in GXCC . . . . . . . . . . . . . . . . . . . . . . . . 58 Figure 26: POWER ON/OFF button on the ISP (example TX300) . . . . . . . . . . . . . . . . 61 Figure 27: Example of partitioning on the basis of volume groups . . . . . . . . . . . . . . . .
PAGE 621
Abbreviations Abbreviation Long form 3490E 36-Track Drive from IBM 3490F 36-Track Drive from IBM 3590 128-Track Drive from IBM = Magstar, = SNI 3591 3590E 256-Track Drive from IBM = successor of Magstar 3592 512-Track Drive (=Jaguar) from IBM Successor to the 3590 drive family 9490 36-Track Drive from STK = Timberline 9840 Tape Drive from STK = Eagle 9940 Tape Drive from STK ABBA/x --- ACF Automatic Cartridge Facility ACI AML Client Interface ACS Automatic Cartridge System ACSLS
PAGE 622
Abbreviations 622 Abbreviation Long form Explanation CSV Comma Separated Values CSW Console Switch CTL Control, Target, LUN CU Control Unit DAS Distributed AML Server Interface to control AML Robots (Open Systems) DASD Direct Access Storage Device In CS system usually the TVC DLDSW0 Dual-Labeled, DualSided, Write Once DNA Distribute and Activate GXCC function DTVFS Distributed Tape Volume File System Filesystem on RAID Systems which contains the LVs in form of files.
PAGE 623
Abbreviations Abbreviation Long form FW Firmware GXCC Global Extended Control Center User interface for CentricStor including administration, service and monitoring in CentricStor V3.x GXTCC Global Extended Tape Control Center User interface for CentricStor including administration, service and monitoring in CentricStor V2.
PAGE 624
Abbreviations 624 Abbreviation Long form Explanation MCP Master Control Process MD Mount Daemon MIB Management Information Base MIM Media Information Message Message for a defective cartridge, only 3590x/3592 MBK Magnetbandkassette (German) Magnetic tape cartridge MM Multi Mode MSGMGR Message Manager OCI Operator Command Interface PCI Peripheral Component In- Bus standard for connecting peripherals with terconnect the chip set of a processor PD Physical Drive Physical drive hooked
PAGE 625
Abbreviations Abbreviation Long form Explanation RAID Redundant Array of Independent (Inexpensive) Disks RMT Remote Monitoring and Administration CentricStor expansion for which a license is required ROBAR Robot Archive ROBAR-SW allows BS2000 to talk to an AML/x tape roboter RPLM Recovery PLM SAE System Administrator Edition SAN Storage Area Network SAS Serial Attached SCSI SAE enables CentricStor to be operated from a remote PC (SAE computer) via the graphical user interface.
PAGE 626
Abbreviations 626 Abbreviation Long form Explanation TVC Tape Volume Cache File system on RAID system(s) which contain(s) the LVs in the form of files. The ISPs access different LVs at the same time. UFS Unix File System UPS Uninterruptable Power Supply VACS Virtual ACSLS Emulates an ACSLS to the host. VAMU Virtual AML Management Unit Emulates an AMU to the host. VD Virtual Drive VDAS Virtual DAS Emulates an AMU to the host.
PAGE 627
Related publications The manuals are available as online manuals, see http://manuals.fujitsu-siemens.com, or in printed form which must be paid and ordered separately at http://FSC-manualshop.com. [1] SINIX-2000 V8.0/V8.1/V8.
PAGE 628
Related publications [3] ROBAR 3.0B (BS2000/OSD, SINIX) Tape Cartridge Archiving System User Guide Target group Computer centers working with the ABBA robot system (CC staff, in particular system administrators and archivers), ROBAR users Contents The manual describes the ROBAR software product that, in conjunction with the ABBA system, controls automatic operation within a tape cartridge archiving system.
PAGE 629
Index 3490 emulation function menu 385 global functions 390 object information 384 Show Error Log 389 Show Error/Transfer Statistics Show Path Trace 388 Show Short Trace 387 3595-RMT 91 A Absolute Min.
PAGE 630
Index B Balloon Help 242 Balloon Help Summary Emulations 243 Physical Devices 244 Physical Library Processes 244 Virtual Library Processes 243 BASE logical volume group 174 physical volume group 181 basic hardware 234 block diagram GXCC 126 XTCC 352 block size 28 button bar 123 C CA Unicenter 552 cache file system 70, 179 cache management 70 Cache Mirroring Feature 31, 55 cache residence 179 Call Home 44 Cancel Time PVG 287 cartridge drives Global Status 254 Show Mode Page Details 428 CD-ROM status informa
PAGE 631
Index D DAS 50 DAS server 571 data PVG show 285 show all 284 Delete snapshots 200 diagnostic data 197 directory 36 Dirty Limit 178 disaster 476 recovery 283 Down/Up Sequence 399 drives block sizes 28 cleaning 81 Dual Save 50, 71 Dual Save Dirty Limit 178 E e-mail support 558 EMTAPE 48 emulations Global Status 251 English Help GXCC 150 XTCC 337 Erase Logical Volumes 213 Physical Volume(s) 226 error messages starting GXCC 104 virtual drives 391 ESCON boards 234 ESCON channel adapter function menu 381 object
PAGE 632
Index flashing display activation on the module 399 free pool 63 fscCentricStor 555 Fujitsu Library 571 Fujitsu robot 50 function bar file viewer 360 Global Status 239 GXCC 143 XTCC 330 functions ACCOUNTD 437 archive systems (SCSI) 419 ISP 135 G German 150 German Help Options XTCC 337 Get Remote / Expand Local File GXCC 154 XTCC 342 get_log protocol 305, 310 Global History Viewer 257 Global Status 237 Balloon Help Summary 242 button bar 246 cartridge drives 254 Config 241 Display 247 emulations 251 File 23
PAGE 633
Index H hard disk status information 376 Hard Min.
PAGE 634
Index tcpd 596 tk 608 XML 590 Xpdf 572 Link Down/Up Sequence 399 Link/Unlink Volume Groups 221 LMF 50 LMF server (PLP) 571 Logical Drives control component 88 see also Virtual Drives Show 268 Logical Volume Group(s) configuration 173 Show 273 Logical Volume(s) Add 211 Erase 213 Show (PLM View) 271 Show (VLM View) 272 loss of connection recovery 120 LRU procedure 39 LVG 63 M Management Station 45 Manual Online 235 manual update 160 Meaning 219 message color 442 message lines 445 Message Manager see MSGMGR m
PAGE 635
Index VLP 126 VLS 405 VMD 407 VTD VTD emulation 399 object-specific functions XTCC 355 Observe mode 90 Open (Text)/Open (Hex) file viewer 361 openssh 597 openssl 604 operating data 257 optional functions 196 Options 336 GXCC 150 XTCC 336 Options Settings GXCC 150 XTCC 336 P partitioning 44 partitioning on the basis of volume groups password query additional 101 passwords GXCC 98 PDS 420 control component 88 function menu 420 information 420 PERFLOG control component 88 function menu 436 information 435 Sho
PAGE 636
Index R RAID controller functions 137 GXCC information 136 RAID controller (internal) status information 378 RAID controllers internal 234 RAID Filesystems configuration 171 RAID system monitoring process 439 RAID systems 234 depiction 130 function menu 414 information 411 Show Mode Page Details 415 read tape 37 read_log protocol 305, 310 Readme GXCC 232 XTCC 348 record analog operating data 258 recovery 476 recycling 543 remote monitoring 45 Remote Program Starter 111 Remove Symbols tape drive 433 Reorgan
PAGE 637
Index Show Balloon Help Summary 242 Cache Status 408 Complete RAID Status 414 Configuration Data 373 CS Configuration 197 Current Aspect GXCC 151 Details (ISP) 135 Dump (prkdump) 383 Error Log 3490 emulation 389 Error/Transfer Statistics 3490 emulation 386 Jobs of Logical Volume Groups 275 Logical Drives 268 Logical Volume Group(s) 273 Logical Volumes 203, 271 Logical Volumes (physical view) 207 Logical Volumes (PLM View) 271 Logical Volumes (VLM View) 272 Medium Info (MIM) 431 Memory Log 390 Memory Log 34
PAGE 638
Index GXCC via XVision 108 Observe mode 97 problems 115 User mode 97 XTCC 135 start parameters 96 starting GXCC console 102 starting from X server GXCC 102 status information GXCC 133 Stop Autoscan GXCC 152 Autoscan XTCC 338 StorageTek Library 571 StorageTek systems 50 streamer status information 377 subsequent installation individual keys 196 SVLP 27, 126 switch on CentricStor 61 synchronization 82 SysObjID 550, 555 system administrator’s edition 52 system data 257 system messages collective display in GX
PAGE 639
Index virtual drive error conditions indicated on display 392 function menu 394 information 393 information and error messages 391 representation in Global Status Monitor 251 SCSI sense 395 Show Medium Info (MIM) 396 Show Service Info (SIM) 397 SIM/MIM error messages 393 virtual drives display 392 object information/error messages 391 virtual SCSI drive see VTD VJUK 88 VLM 34 control component 88 Global Status 252 information 408 Set HALT Mode / Set RUN Mode 410 VLMF 88 VLP 27, 33 definition 126 VLP failov
PAGE 640
Index Options 336 Options Settings 336 Print 332 profile 344 Readme 348 Show Remote File 342 start 135 status bar 328 title bar 328 Toggle Aspect 337 Toggle Size 337 Tools 341 Unit 335 XUS Message Update/Revert Tool 159 XVision setting 108 640 U41117-J-Z125-7-76