Sign in today to find solutions:

Don't have an account? Sign up

 
CentricStor V3.1D
User Guide
Edition July 2007
Next page ->

Summary of Contents

  • Page 1

    CentricStor V3.1D User Guide Edition July 2007...

  • 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.com Certified documentation according to DIN EN ISO 9001:2000 To ensure a consistently high quality standard and...

  • Page 3: Table Of Contents

    Contents Introduction ........19 Objective and target group for the manual .

  • Page 4: Table Of Contents

    Contents Procedures ........38 2.6.1 Creating the CentricStor data maintenance .

  • Page 5: Table Of Contents

    4.1.3 System administrator activities 4.1.3.1 Adding a logical volume group ......66 4.1.3.2 Adding a physical volume group .

  • Page 6: Table Of Contents

    Contents 5.2.3 GXCC in other systems ....... . . 92 5.2.4 Screen display requirements 5.2.5...

  • Page 7: Table Of Contents

    6.1.6 Block diagram ........126 6.1.6.1 Status information .

  • Page 8: Table Of Contents

    Contents 6.2.7 Configuration ........166 6.2.7.1 RAID Filesystems .

  • Page 9: Table Of Contents

    7.3.1.2 Exit ......... 240 7.3.2 Config .

  • Page 10: Table Of Contents

    Contents 7.7.1.5 Run ........301 7.7.1.6 Mode .

  • Page 11: Table Of Contents

    8.3.4.4 Scan Now ........340 8.3.4.5 Interaction Timeout .

  • Page 12: Table Of Contents

    Contents 8.5.8.3 Abort ........365 8.5.8.4 Enlarge Font / Reduce Font .

  • Page 13: Table Of Contents

    8.10 Virtual 3490 drives ........391 8.10.1 Object information and error messages for virtual 3490 drives .

  • Page 14: Table Of Contents

    Contents 8.17 RAID systems ........411 8.17.1 Object information on RAID systems .

  • Page 15: Table Of Contents

    8.23.3 Global functions for tape drives ......432 8.23.3.1 Remove Symbols of all Drives ......433 8.24 MSGMGR (Message Manager) .

  • Page 16: Table Of Contents

    Contents 9.2.12 SXMM... (Message Manager) ......459 9.2.13 SXPL... (PLM: Physical Library Manager) ..... . . 465 9.2.14 SXPS...

  • Page 17: Table Of Contents

    12.1.2.2 Activating the configuration ......548 12.1.2.3 Changes in central files ......548 12.1.3 Monitoring CentricStor .

  • Page 18: Table Of Contents

    Contents 12.4 Licenses ........572 12.4.1 Xpdf, gzip .

  • Page 19: Introduction

    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, Concept Of The Manual

    Objective and target group for the manual 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.

  • Page 21: Notational Conventions, Note

    Introduction 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.

  • Page 22

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • Page 23: Centricstor - Virtual Tape Library, The Centricstor Principle

    2 CentricStor - Virtual Tape Library 2.1 The CentricStor principle Conventional host robot system Host 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 Host robot system with CentricStor Host Figure 2: Host robot system with CentricStor With CentricStor, a virtual archive system is installed upstream of the real archive system with the physical drives and data cartridges. This enables the host to be completely isolated from the real archive.

  • Page 25

    CentricStor - Virtual Tape Library 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

    Hardware architecture 2.2 Hardware architecture Mainframe ESCON Director Switch UNIX/Windows FICON Switch Mainframe Figure 3: Example of a CentricStor configuration In this example, CentricStor comprises the following hardware components: a VLP (Virtual Library Processor), which monitors and controls the CentricStor ●...

  • Page 27: Isp (integrated Service Processor), Vlp (virtual Library Processor)

    CentricStor - Virtual Tape Library 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). Depending on the peripheral connection, the hardware configuration, the software configuration, and the task in the CentricStor system, a distinction is made between the following processor types: –...

  • Page 28: Icp (integrated Channel Processor)

    Hardware architecture 2.2.1.2 ICP (Integrated Channel Processor) The ICP is the interface to the host systems connected in the overall system. Hosts BS2000/OSD, z/OS and OS/390 z/OS and OS/390 BS2000/OSD, Open Systems Figure 5: External and internal ICP connections Depending on the type of host system used, it is possible to equip an ICP with a maximum of 4 ESCON boards on the host side (connection with BS2000/OSD, z/OS or OS/390), with one or two FICON ports (connection with z/OS or OS/390), or with one or two FC boards (BS2000/OSD or open systems).

  • Page 29: Idp (integrated Device Processor), Icp_idp Or Iup (integrated Universal Processor)

    CentricStor - Virtual Tape Library 2.2.1.3 IDP (Integrated Device Processor) The IDP is the interface to the connected tape drives. CentricStor 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.

  • Page 30: Raid Systems For The Tape Volume Cache

    Hardware architecture 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.

  • Page 31: Fibrechannel (fc), Fc Switch (fibre Channel Switch)

    CentricStor - Virtual Tape Library 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.

  • Page 32: Host Connection, Software Architecture

    Software architecture This SAN-based design means that each CentricStor component is in a position to access the TVC. 2.2.5 Host connection The host connection on the ICP is implemented using the following connection technologies: Host system Mainframe Open Systems FibreChannel with ESCON or FICON connections can be operated in mixed mode on an ICP.

  • Page 33

    CentricStor - Virtual Tape Library MSP/XSP LIB/SP z/OS OS/390 HACC BS2000 ROBAR Open Systems ACSLS DAS-ACI SCSI Backup software Figure 8: Central role of the VLP in a CentricStor configuration VLP (Virtual Library Processor) The VLP is responsible for the coordination of the entire CentricStor system. Although the software can be activated on any of the ICP or IDP systems, it is recommended for perfor- mance reasons that you either provide a separate VLP, or activate the components of the VLP on one of the IDPs, since the CPU utilization is at its lowest here.

  • Page 34

    Software architecture 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: Operation, Writing The Tape Cartridges According To The Stacked Volume Principle

    CentricStor - Virtual Tape Library 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: Repeated Writing Of A Logical Volume Onto Tape, Creating A Directory

    Administering the tape cartridges 2.5.2 Repeated writing of a logical volume onto tape 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: Reorganization Of The Tape Cartridges

    CentricStor - Virtual Tape Library 2.5.4 Reorganization of the tape cartridges 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. This process, combined with updates (see the section section “Creating a directory”...

  • Page 38: Procedures, Creating The Centricstor Data Maintenance

    Procedures 2.6 Procedures 2.6.1 Creating the CentricStor data maintenance Initial situation: To start CentricStor, the PLM and VLM data maintenance facility must be created: Host BS2000 ROBAR MAREN LV0000 LV0001 LV0002 LV0003 Figure 13: CentricStor after the VLM and PLM data maintenance have been created 1.

  • Page 39: Issuing A Mount Job From The Host

    CentricStor - Virtual Tape Library 2.6.2 Issuing a mount job from the host Initial situation: Host LV0005 Data Figure 14: Procedure for a mount job A mount job is executed as follows: 1. The host issues a mount job for logical volume LV0005, which is then accepted by the VLM.

  • Page 40

    Procedures 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: Case 2: 3. The host performs read and write accesses on the logical volume. 4.

  • Page 41

    CentricStor - Virtual Tape Library Case 2: The data of the logical volume is retained on the RAID system until deleted by the VLM in accordance with the LRU procedure. U41117-J-Z125-7-76 The logical volume has been modified. a) The VLM informs the PLM that the logical volume is to be copied onto tape.

  • Page 42: Scratch Mount

    Procedures 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: –...

  • Page 43: New System Functions

    CentricStor - Virtual Tape Library 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: ●...

  • Page 44: Standard System Functions, Partitioning By Volume Groups

    Standard system functions 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: Snmp Support, Exporting And Importing Tape Cartridges

    CentricStor - Virtual Tape Library 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: Vault Attribute And Vault Status, Transfer Pvg

    Standard system functions 2.8.4.1 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 associated tape cartridges (PVs) can be placed in vault status using the following com- mand: plmcmd conf -E They are then locked for all read and write operations until vault status is cancelled again...

  • Page 47: Optional System Functions

    CentricStor - Virtual Tape Library 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. In addition to the basic configuration, optional functions are available which allow you to customize the CentricStor functionality to suit your needs: Compression ●...

  • Page 48: Compression

    Optional system functions 2.9.1 Compression The figure below illustrates the principle of software compression of logical volumes: Data from host Figure 15: Principle of compressing logical volumes Just as a physical drive can perform data compression, so also can the tape drive emula- tions (EMTAPE volumes can be stored in compressed form in the TVC.

  • Page 49: Multiple Library Support

    CentricStor - Virtual Tape Library In BS2000/OSD (“HOST” attribute), compression is controlled on the basis of the tape type: – TAPE-C3: – TAPE-C4: 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: Dual Save

    Optional system functions 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.

  • Page 51

    CentricStor - Virtual Tape Library Host1 LVG1 LVG 1 LV0001 LV0002 LV0003 LV3000 PVG 1 PV0001 PV0002 PV0003 PV0300 Figure 17: Example of Dual Save functionality In accordance with the assignment rules for the volume group functionality (see the logical volumes from LVG 1 (LV0001-LV3000) are mirrored on the physical volumes of PVG 1 (PV0001-PV0300) and PVG 2 (PV0301-PV0600) in the robot Archive1.

  • Page 52: Extending Virtual Drives, System Administrator's Edition, Fibre Channel Connection For Load Balancing And Redundancy

    Optional system functions 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.

  • Page 53

    CentricStor - Virtual Tape Library If the “automatic VLP failover” function has been activated, the following actions are no longer permitted in the system: – changing the LAN configuration – rebooting or shutting down of the VLP (init 0 or init 6: these commands cause a failover!) –...

  • Page 54

    Optional system functions 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: Figure 20: Activation of the defective processor for the SVLP The status, i.e. AutoVLP failover active or inactive, is clearly visible on the GUI: Figure 21: Display of the AutoVLP failover status on the GUI The left-hand triangle is only displayed if an SVLP is configured.

  • Page 55: Cache Mirroring Feature, General, Hardware Requirements

    CentricStor - Virtual Tape Library 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: Software Requirements

    Optional system functions 2.9.8.3 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 “Mirrored RAID systems”...

  • Page 57: Mirrored Raid Systems

    CentricStor - Virtual Tape Library 2.9.8.4 Mirrored RAID systems A mirrored CentricStor system has 1 to a maximum of 4 RAID mirror pairs. RAID mirror pair 1 1stRAID 2ndRAID ID 1 Figure 23: Example of a CentricStor mirror system with 3 RAID mirror pairs In a RAID mirror pair, one RAID system contains only primary caches, the other only secondary caches (mirror caches): RAID mirror pair...

  • Page 58

    Optional system functions 2.9.8.5 Presentation of the mirror function in GXCC In GXCC the mirror functions of a double RAID system are indicated by two arrows. Example Figure 25: Presentation of the mirror function in GXCC Genuine RAID pairs are indicated with a white dot, potential pairs by a thicker black line between the boxes on the right-hand side The display can contain an odd number of RAID systems if, for example, a defective RAID system has been separated from the CentricStor system.

  • Page 59

    CentricStor - Virtual Tape Library 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 Example On the other hand this function enables the current accounting data to be sent by e-mail at defined times (see the U41117-J-Z125-7-76 section “Statistics »...

  • Page 60

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • 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 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 Ê...

  • Page 63: Selected System Administrator Activities, Partitioning On The Basis Of Volume Groups, General

    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: Rules

    Partitioning on the basis of volume groups BS2000 host LVG1 LV0001 LV0002 LV0003 LV3000 PVG1 PV0001 PV0002 PV0003 PV0300 Figure 27: Example of partitioning on the basis of volume groups 4.1.2 Rules Logical volume groups: – It is possible to configure up to 512 logical volume groups. By default, CentricStor always has at least two logical volume groups (“BASE”...

  • Page 65

    Selected system administrator activities Physical volume groups: – It is possible to configure up to 100 physical volume groups 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. –...

  • Page 66: Adding A Logical Volume Group, Adding A Physical Volume Group

    Partitioning on the basis of volume groups 4.1.3.1 Adding a logical volume group The form and detailed information are provided in the ● on page 173 1. Click on the “NEW” button. 2. The following must be entered: Name Type Location Comment Comment 3.

  • Page 67: Adding Physical Volumes To A Physical Volume Group, Assigning An Lvg To A Pvg

    Selected system administrator activities 4.1.3.4 Adding physical volumes to a physical volume group Only physical volumes contained in the physical library may be specified. The form and detailed information are provided in the ● tions » Add Physical Volumes” on page The following information must be specified: –...

  • Page 68: Changing Logical Volumes To Another Group, Removing Logical Volumes, Removing Logical Volume Groups

    Partitioning on the basis of volume groups 4.1.3.7 Changing logical volumes to another group The form and detailed information are provided in the ● tions » Change Volume Group” on page 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: Removing Physical Volumes From A Physical Volume Group, 4.1.3.11 Removing Physical Volume Groups

    Selected system administrator activities 4.1.3.10 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). The form and detailed information are provided in the ●...

  • Page 70: Cache Management

    Cache management 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). LVG1 LV0001 LV0002...

  • Page 71: General, Dual Save

    Selected system administrator activities 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 The settings for the cache file system can be altered later at any time. 4.3 Dual Save 4.3.1 General Dual Save (see...

  • Page 72: System Administrator Activities 4.3.2.1 Assigning A Logical Volume Group To Two Physical Volume Groups

    Dual Save 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 ● tions » Link/Unlink Volume Groups” on page The following information must be selected: –...

  • Page 73: Reorganization, Why Do We Need Reorganization

    Selected system administrator activities 4.4 Reorganization A brief overview of the reorganization of tape cartridges can be found on 4.4.1 Why do we need reorganization? Reorganizations are performed for the following four reasons: 1. Effective use of the physical volumes’ capacity There are two situations in which logical volumes may be rendered invalid on a physical volume: –...

  • Page 74: How Is A Physical Volume Reorganized

    Reorganization 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.

  • Page 75: When Is A Reorganization Performed

    Selected system administrator activities 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. The following three events cause reorganization to be triggered immediately regardless of the time of day: Explicitly by means of a user command ●...

  • Page 76: Which Physical Volume Is Selected For Reorganization

    Reorganization 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 <PVG> over absolute minimum (<num>) again For the following statuses, reorganization is only initiated within the configured time of day interval.

  • Page 77

    Selected system administrator activities 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: Own Physical Volumes For Reorganization Backup, Starting The Reorganization Of A Physical Volume

    Reorganization 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 invol- ved.

  • Page 79: Configuration Parameters

    Selected system administrator activities 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 unneces- sarily on account of the lack of drives.

  • Page 80

    Reorganization 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: Cleaning Physical Drives

    Selected system administrator activities 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.

  • Page 82: Synchronization Of The System Time Using Ntp

    Synchronization of the system time using NTP 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.

  • Page 83: Operating And Monitoring Centricstor, Technical Design, General

    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. ESCON ESCON GXCC XTCC FICON GXCC FICON XTCC Figure 29: GXCC/XTCC on the CentricStor ISPs (example VTA 2000-5000) U41117-J-Z125-7-76 CentricStor GXCC...

  • Page 84: Principles Of Operation Of Gxcc

    Technical design 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).

  • Page 85

    Operating and monitoring CentricStor 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 InfoBroker SCSI components Figure 30: GXCC components with X11 server as remote computer In this example GXCC runs on a CentricStor computer.

  • Page 86

    Technical design 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: Monitoring Structure Within A Centricstor Isp

    Operating and monitoring CentricStor 5.1.3 Monitoring structure within a CentricStor ISP The figure on page 89 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 The table below lists the control components: Name Function Logical Device: emulation of a drive. MSGMGR Message Manager: filters and stores system messages. Triggers actions in response to certain situations (e.g. SNMP traps). Physical Device Service: drives one physical tape drive.

  • Page 89

    Operating and monitoring CentricStor Remote computer Keyboard TCP/IP LAN TCP/IP LAN or TCP/IP connection within processor Figure 32: Monitoring structure in CentricStor (example VTA 2000-5000) U41117-J-Z125-7-76 Mouse Screen GXCC Mainframe hosts ESCON, FICON or FC Open host connection Systems hosts SCSI drives SCSI or FC connections to...

  • Page 90: 5.1.4 Operating Modes

    Technical design 5.1.4 Operating modes GXCC recognizes the following three user privilege levels: Service mode User mode Observe mode The operating mode is set as a start parameter when GXCC is called. The password will be queried once the connection has been established. If the wrong password is entered, an error message is output and the query is repeated.

  • Page 91: Operator Configuration, Basic Configuration, Expansion

    Operating and monitoring CentricStor 5.2 Operator configuration 5.2.1 Basic configuration Without requiring additional hardware or further software licences, CentricStor offers the following configuration for operation and monitoring: GXCC X11 server Figure 33: CentricStor basic configuration Within a CentricStor cluster, the InfoBroker will accept two connections to GXCC if this has been started on an ISP of CentricStor.

  • Page 92: Connection To Snmp Management Systems

    Operator configuration 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.

  • Page 93: Snmp And Gxcc

    Operating and monitoring CentricStor 5.2.5.2 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 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 agent CentricStor Figure 34: Configuration options at an SNMP management station –...

  • Page 95

    Operating and monitoring CentricStor – 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.

  • Page 96

    Starting GXCC The table below lists the possible start parameters: Parameter -aspect <param> Size and position of the main win- -autoscan -display -globstat -lang -multiport -nointro -observe -profile <file> -service -simu <file> -singleport -size -unit Meaning dow on the screen Cycle duration for updating the main window Host name/IP address of the...

  • Page 97: Explanation Of The Start Parameter -aspect

    Operating and monitoring CentricStor Parameter -user 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.1 Explanation of the start parameter -aspect The argument of this parameter has the format {[=][WxH]+|-X+|-Y} Where: The window is displayed on the screen with a width of W pixels and a height of H pi-...

  • Page 98: Environment Variable Xtcc_class, Passwords

    Starting GXCC 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: Optional Access Control For Observe Mode, Authentication

    Operating and monitoring CentricStor 5.3.4.1 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.

  • Page 100: Suppressing The Password Query

    Starting GXCC 5.3.4.3 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:...

  • Page 101: Additional Password Query

    Operating and monitoring CentricStor 5.3.4.4 Additional password query If GXCC or XTCC requires a password to transfer an update (see the dates” on page ing window appears: This password query is made only when the user can access the system without a primary password query.

  • Page 102: Starting The Centricstor Console, Starting From An X11 Server

    Starting GXCC 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: –...

  • Page 103

    Operating and monitoring CentricStor – and the RequestBroker of the connected ISP, which gathers information from all compo- nents 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).

  • Page 104: Using The Direct Xdmcp Interface, Starting From A Unix System

    Starting GXCC 5.3.6.2 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.

  • Page 105: Starting From A Windows System Via Exceed

    Operating and monitoring CentricStor 5.3.6.4 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.

  • Page 106

    Starting GXCC 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.

  • Page 107

    Operating and monitoring CentricStor 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.

  • Page 108: Starting From A Windows/nt System Via Xvision

    Starting GXCC 5.3.6.5 Starting from a Windows/NT system via XVision 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. Operating and monitoring CentricStor U41117-J-Z125-7-76...

  • Page 109

    Operating and monitoring CentricStor 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 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.

  • Page 111

    Operating and monitoring CentricStor 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.

  • Page 112

    Starting GXCC 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”...

  • Page 113

    Operating and monitoring CentricStor 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: Gxcc Welcome Screen

    Starting GXCC 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.7 GXCC welcome screen When a connection is setup up successfully to the X11 server a welcome screen appears (but not if the -nointro parameter was specified at GXCC startup): When you see this screen, the connection between GXCC and the X11 server has been...

  • Page 115

    Operating and monitoring CentricStor 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”...

  • Page 116: Selecting The Centricstor System, Establishing A Connection After Clicking On Ok

    Starting GXCC 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 page 147. Errors that occur when a connection is established after clicking on “OK” are handled differently because no connection yet exists to CentricStor.

  • Page 117: Authentication

    Operating and monitoring CentricStor 5.3.10 Authentication As soon as a connection has been established, client authentication takes place. Password- based 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”.

  • Page 118: Software Updates

    Starting GXCC 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.

  • Page 119: Gxcc, Main Window, Standard

    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. Function bar (page 143)

  • Page 120: Loss Of A Connection

    Main window 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.

  • Page 121: Elements Of The Gxcc Main Window, Title Bar, Footer

    GXCC 6.1.3 Elements of the GXCC main window 6.1.3.1 Title bar The title bar is laid out as follows: <systemname>: CentricStor(<IP-address><unit-name>) <systemname>: System name entered during configuration. No display if no system name has been entered. <IP-address><unit-name> 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”.

  • Page 122

    Main window 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 op- erational in the GXCC main window.

  • Page 123: Function Buttons And Displays In The Button Bar, System Information

    GXCC – 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.

  • Page 124: Console Messages, Function Bar

    Main window 6.1.3.5 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 bar”...

  • Page 125

    GXCC 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”...

  • Page 126: Block Diagram

    Main window 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 The triangle at the top left indicates that GXCC is connected to this ISP. On the VLP and SVLP a triangle is displayed if the AutoVLP failover has been configured: If this triangle is red, AutoVLP failover is not activated. Green indicates that it is activated.

  • Page 128

    Main window Special aspects when performing Distribute and Activate The following special aspects must be borne in mind when performing Distribute and Activa- Some GXCC menu items are hidden. ● The current progress is displayed in blue script in the system message line. ●...

  • Page 129

    GXCC 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 connec- tions to the FC switch which are faulty are drawn with dashed lines until the SNMP trap has been processed by the FC switch.

  • Page 130

    Main window 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). Host connections In the overview screen, the connections to the hosts (ESCON/FICON or Fibre Channel) are depicted as short lines emerging from the inner frame:...

  • Page 131

    GXCC The colors have the following meaning: Green Operational Pink 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 Left-clicking on the RAID symbol causes further information to be output in the right- hand part of the GXCC 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.

  • Page 133: Status Information, Object Information And Object-related Functions

    GXCC 6.1.6.1 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. You can obtain detailed information in the right-hand part of the window by clicking on the object with the left mouse button.

  • Page 134: Icp Object Information

    Main window 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: –...

  • Page 135: Idp Object Information, Functions Of An Isp, Show Details (xtcc)

    GXCC 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) –...

  • Page 136: Information About The Raid Systems

    Main window 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) –...

  • Page 137: Raid System Functions, Show Complete Raid Status

    GXCC 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: 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”...

  • Page 138: Information On Fibre Channel Fabric, Functions Of The Fibre Channel Fabric

    Main window 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 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).

  • Page 140: Information About The Fc Connections, Information On The Archive Systems

    Main window 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 –...

  • Page 141: Isp System Messages, Snmp Messages

    GXCC 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”...

  • Page 142: Configuration Changed

    Main window 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.

  • Page 143: Function Bar, Overview Of Gxcc Functions

    GXCC 6.2 Function bar 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). How exactly such shortcuts are handled depends on the operating system or the Window Manager, e.g.

  • Page 144

    Function bar Configuration (page ● – RAID Filesystems (page – Logical Volume Groups (page – Physical Volume Groups (page – Distribute and Activate (page Profile (page ● – Add/Select Profile(page Administration (page ● – Show WWN’s (page – Show Optional Functions (page –...

  • Page 145: File, Save

    GXCC 6.2.2 File Es stehen folgende Funktionen zur Verfügung: – Save – Open – Show – Print – Exit 6.2.2.1 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. With this function you save precisely the data which currently leads to the picture displayed.

  • Page 146: Open, Show, Print

    Function bar 6.2.2.2 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: 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.

  • Page 147: Exit, Unit, Select

    GXCC 6.2.2.5 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.

  • Page 148

    Function bar 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”...

  • Page 149

    GXCC Buttons at the bottom of the screen 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. Adds the entered unit data to the list. Remove Removes the selected entry from the list.

  • Page 150: Options, Settings

    Function bar 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 Autoscan/Stop Autoscan” on page original settings. If GXCC is running under the control of a profile file that has been explicitly specified, all changes made using the “Options”...

  • Page 151: Show Current Aspect

    GXCC 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.

  • Page 152: Autoscan, Start Autoscan/stop Autoscan

    Function bar 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.

  • Page 153: Settings

    GXCC 6.2.5.2 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.

  • Page 154: Tools, Global Status, Get Remote/expand Local File

    Function bar 6.2.6 Tools The following functions are offered: – Global Status – Get Remote/Expand Local File – Show Remote File – Show System Messages – GXCC Update/Revert Tool 6.2.6.1 Global Status This function is used to call the Global Status Monitor (for a description see the “Global Status”...

  • Page 155

    GXCC 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.

  • Page 156: Show Remote File

    Function bar 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 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 platform- specific system calls or from the file transfer protocol.

  • Page 158

    Function bar 6.2.6.4 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.

  • Page 159

    GXCC DateTime ISP-Name Separator 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 Certain alerting actions are predefined for the messages in accordance with their priorities.

  • Page 160

    Function bar 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 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”...

  • Page 162

    Function bar A monitor program keeps track of all the GXCCs and their ramifications. It initiates the termi- nation 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 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.

  • Page 164

    Function bar 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 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.

  • Page 166: Configuration

    Function bar 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. Changes to the LVGs affect VLM and PLM, changes to the PVGs affect only thePLM.

  • Page 167

    GXCC ➟ 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 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: 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.

  • Page 169

    GXCC 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.

  • Page 170

    Function bar 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: Raid Filesystems

    GXCC 6.2.7.1 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).

  • Page 172

    Function bar Information Mirroring Whether the mirror function is enabled or disabled in CentricStor is specified here. 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.

  • Page 173: Logical Volume Groups

    GXCC 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.

  • Page 174

    Function bar Buttons and entry fields 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.

  • Page 175

    GXCC “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”...

  • Page 176

    Function bar 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.

  • Page 177

    GXCC 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 Erase Scratch LVs This specifies how the data of scratch volumes is to be handled: ENABLED DISABLED Dual Save Dirty Limit (%) Determines the maximum share which logical volumes of this LVG which are “dirty” may be assigned in the cache file system. When this value is exceeded and the selected LVG is connected to 2 PVGs, CentricStor will switch from dual save to single save in the event of problems on the backend, e.g.

  • Page 179

    GXCC Command buttons along the lower border Accepts the entry. It becomes effective with “Distribute and Activate”. The “Configu- ration 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.

  • Page 180

    Function bar 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: Physical Volume Groups

    GXCC 6.2.7.3 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: In the case of PVGs already distributed with “Distribute and Activate”, the “To Be Deleted”...

  • Page 182

    Function bar 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 Marking for deleting the volume group You mark a line by clicking on it.

  • Page 183

    GXCC “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”...

  • Page 184

    Function bar 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.

  • Page 185

    GXCC 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.

  • Page 186

    Function bar 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 reorgani- zation. 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 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.

  • Page 188: Distribute And Activate

    Function bar 6.2.7.4 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”...

  • Page 189

    GXCC Buttons 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.

  • Page 190

    Function bar 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.conf and /usr/apc/conf/vtls_vg.conf and distributed to all ISPs of CentricStor.

  • Page 191: Profile, Add/select Profile

    GXCC 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.

  • Page 192

    Function bar Buttons at the bottom of the screen section 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. The file name specified in the editing field is added to the list and is also displayed at the bottom of the GXCC screen.

  • Page 193: Administration

    GXCC 6.2.9 Administration The following functions are offered: – Show WWN’s – Show Optional Functions – Show CS Configuration – Diagnostic Snapshots – Logical Volume Operations – Physical Volume Operations – Setup for accounting mails If the VLM is not running, this menu item is displayed against a gray background and cannot be selected. If the PLM is not running, this menu item is displayed against a gray background and cannot be selected.

  • Page 194

    Function bar Depending on authorization and/or the version of the connected CentricStor system, indi- vidual menu items are not available. The table below shows which menu items are available in which mode: Shutdown CS System Destroy RAID Filesystems Start/Stop CS Processes Commit SYS_MSG Show WWN's Show Optional Functions...

  • Page 195: Show Wwn's

    GXCC 6.2.9.1 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. Example U41117-J-Z125-7-76 Function bar...

  • Page 196: Show Optional Functions

    Function bar 6.2.9.2 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 Subsequent installation of individual keys is performed under SINIX-2000-Z using SYSADM.

  • Page 197: Show Cs Configuration, Diagnostic Snapshots

    GXCC 6.2.9.3 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 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: ISP Name # of existing snapshots total size of snapshots (MB) date and time of last snapshot new snapshot to be created...

  • Page 199

    GXCC “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 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. The columns contain the following information: ISP Name date and time of snapshot...

  • Page 201

    GXCC “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”...

  • Page 202: Logical Volume Operations

    Function bar – 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”...

  • Page 203

    GXCC 6.2.9.6 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 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.

  • Page 205

    GXCC The following data is output: C-ID SIZE ACCESS TIME STATE STALE FLAGS U41117-J-Z125-7-76 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).

  • Page 206

    Function bar 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. GXCC U41117-J-Z125-7-76...

  • Page 207

    GXCC 6.2.9.7 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. You obtain statistcs on the logical volumes by calling the function of the same name for “logical view”.

  • Page 208

    Function bar The logical volumes are displayed in the following window: PLM-specific data of the LVs is output: size save request at PV 1 PVG 1 TL 1 bl_nr 1 PV 2 PVG 2 TL 2 bl_nr 2 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...

  • Page 209

    GXCC 6.2.9.8 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. 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 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.

  • Page 211

    GXCC 6.2.9.9 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.

  • Page 212

    Function bar 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. The assignment of logical volume group to one or two physical volume group(s) is described in the Groups”...

  • Page 213

    GXCC 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.

  • Page 214

    Function bar 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.

  • Page 215: Physical Volume Operations

    GXCC 6.2.9.11 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 These menu items are offered only if the PLM is running. 6.2.9.12 Physical Volume Operations »...

  • Page 216

    Function bar 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) –...

  • Page 217

    GXCC If the query relates to multiple volumes, the following overview is displayed: Meaning of the information Line number 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 Tape Library: Name of the archive Name of the physical volume group...

  • Page 218

    Function bar _r__ _rd_ s___ _v__ _w__ Write volume that can still be used for save operations _wd_ The cartridge is not yet full; currently there is no directory on the tape ____ next-bl Block number of the free range. This indicates the physical utilization level. Number of saved logical volumes Number of valid saved logical volumes;...

  • Page 219

    GXCC Meaning of the information: Line number Number of the physical volume Name of the archive Name of the physical volume group, usually starts at “CLNP”. state status The following values are possible for cleaning cartridges: o___ _r__ f___ max. count Initial number of cleaning cycles used_count Number of cleaning cycles used...

  • Page 220

    Function bar This is followed by a list of the (valid) logical volumes stored on the PV: file-Id bl_nr size/MB save request at The information for a cleaning cartridge contains a list showing all the cleaning runs carried out using this cartridge along with the time and PDS of each run: Line number Name of the logical volume Hexadecimal: internal version number in the TVC...

  • Page 221

    GXCC 6.2.9.13 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. PVG (Original) PVG (Copy) Click a line to select the desired PVG.

  • Page 222

    Function bar Buttons along the bottom border 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 (<PVG1>,>PVG2>) to LVG (<LVG>): The capacity of...

  • Page 223

    GXCC 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.

  • Page 224

    Function bar 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.

  • Page 225

    GXCC 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 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.

  • Page 227

    GXCC 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 The specified volumes are removed from the PLM data maintenance system.

  • Page 228

    Function bar 6.2.9.16 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.

  • Page 229: Setup For Accounting Mails

    GXCC 6.2.9.17 Setup for accounting mails 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 “Sendmail configuration”...

  • Page 230

    Function bar 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.

  • Page 231

    GXCC Send mail at <hh:mm>: 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 <MM-DD>|<week day>: Here the user can define the day on which the accounting data is to be sent by mail. Format and default value: See above.

  • Page 232: Help, Readme / Liesmich, Direct Help / Direkthilfe, System Messages, About Gxcc

    Function bar 6.2.10 Help The following entries can be selected in the “Help” menu: – 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).

  • Page 233: Revision Summary

    GXCC 6.2.10.5 Revision Summary A text window with information on the installed software of all CentricStor ISPs is displayed: System Name IP Number Revision Production Date U41117-J-Z125-7-76 name of the ISP IP address revision level of the software production date of the software Function bar...

  • Page 234: Hardware Summary

    Function bar 6.2.10.6 Hardware Summary A window with information on the hardware components installed in the system is opened: Information on the following hardware components is output: ISPs ● – Basic hardware – Graphic adapters – Internal RAID controllers – ESCON boards –...

  • Page 235: Online Manual

    GXCC 6.2.10.7 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.

  • Page 236

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • Page 237: Global Status, General

    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. There are several options for starting “Global Status”: – using the optional start parameter -globstat parallel to GXCC –...

  • Page 238

    General 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...

  • Page 239: Operation Of The Global Status Monitor, Function Bar Of The Global Status Monitor, File

    Global Status 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.

  • Page 240

    Function bar of the Global Status Monitor 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.

  • Page 241: Config

    Global Status 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”...

  • Page 242: Global Extended Control Center, Tools, Show Balloon Help Summary

    Function bar of the Global Status Monitor – The screen division can be set in the usual manner. Permanent recording of operating data is not affected. 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 The following data is listed: Emulations Arranged according to ICP: emu/vid name lib. device virtual device mounted volume special state (emu/device) virtual library processes vlm process vls processes U41117-J-Z125-7-76 Function bar of the Global Status Monitor Number of the emulation (390 emulation) / LUN (FC SCSI device). Archive name/address of the device.

  • Page 244

    Function bar of the Global Status Monitor Physical Devices Arranged according to IDP: pds name scsi device manufacturer device type and model prod. rev. special state (pds/dev) Physical Library Processes plm process pls processes host type Name of the PDS. CTL (controller, target, LUN) of the device.

  • Page 245: Statistics, Help

    Global Status 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) 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 button bar 7.4 Global Status button bar Frequently used functions can be accessed immediately after you have clicked on the relevant button: Hardcopy (only if Global Sta- tus is running on Windows) Terminates Global Status Shows all three subwindows Shows only right subwindow (physical) Shows only central subwindow (logical) Shows only left subwin.

  • Page 247: Display Of The Global Status Monitor

    Global Status 7.5 Display of the Global Status Monitor The Global Status Monitor window consists of three vertically aligned subwindows separated from one another by gray lines: Subwindow scroll bars The subwindows show (from left to right): – the throughput through the host interfaces and the device SCSI or FC controllers –...

  • Page 248

    Display of the Global Status Monitor 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.

  • Page 249: Performance

    Global Status 7.5.1 Performance The left-hand part of the window displays the current data throughput at the external inter- faces. 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.

  • Page 250

    Display of the Global Status Monitor 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.

  • Page 251: Virtual Components

    Global Status 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.

  • Page 252

    Display of the Global Status Monitor 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.

  • Page 253

    Global Status Additional displays for mirrored systems Red bar on a cache column: The cache is no longer mirrored (“out of sync”). ● Left: Right: Yellow bar on a cache column: The cache concerned is being resynchronized and is still ●...

  • Page 254: Physical Components

    Display of the Global Status Monitor 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.

  • Page 255

    Global Status 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 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.

  • Page 257: History Data

    Global Status 7.6 History data History data is system data which has been collected over a lengthy period. For this purpo- se 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.

  • Page 258: Recording Analog Operating Data, General, Overview Of The Displays

    History data 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.

  • Page 259

    Global Status Measured value Scratch Volumes of a PVG Cache Usage Usage of Overall Cache Throughput of a PDS or Host Adapter Overall Throughput H Jobs of Logical Volume Groups Jobs of Physical Volume Groups Logical Drives Logical Drives Utili- zation Logical Volume Groups...

  • Page 260

    History data Measured value Physical Volume Groups Tape Statistics Physical Volumes Occupancy Reorganization Status Usage (Accounting) Type Call Object: PVG column in right-hand part of screen Statistics » Physical Components » Physical Volumes Statistics » Physical Components »Reorga- nization Status Statistics »...

  • Page 261

    Global Status The table below shows the selection and control options for the history data: CentricStor virtual Components CentricStor Virtual Mounts number of Mounts cumulated MountTime CentricStor Total Mount Time (% of Range) virtual drives CentricStor Concurrent VTDs usage (Histogram) % of virtual drives CentricStor Cache % free...

  • Page 262: Selecting The Time Period

    History data 7.6.1.3 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.

  • Page 263: Selecting The Presentation Mode

    Global Status The button bar below these options allows you to select the functions “Exit” and “Redraw”: 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”...

  • Page 264: Data Which Can Be Called Via The Function Bar

    History data 7.6.2 Data which can be called via the function bar The following menus and submenus can be called under “Statistics”: History of ● – Cache Usage – Channel/Device Performance Logical Components ● – Logical Drives – Logical Volumes (physical view) –...

  • Page 265

    Global Status 7.6.2.2 Statistics » History of » Cache Usage The history of cache usage is output in accordance with the cache total values of the virtual components subwindow. U41117-J-Z125-7-76 History data...

  • Page 266

    History data 7.6.2.3 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.

  • Page 267

    Global Status 7.6.2.4 Statistics » Logical Components The following submenus are available: – Logical Drives – Logical Volumes (physical view) – Logical Volumes (logical view) – Logical Volume Groups – Jobs of Logical Vol. Groups 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 Statistics » Logical Components » Logical Drives 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: This statistics function supports the refresh function.

  • Page 269

    Global Status 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 of the volume mounted in a drive or “Empty” LVG of a mounted volume or - C-ID Number of the cache (=Cache-ID) to which the mounted volume is assigned or - SIZE...

  • Page 270

    History data Rest. Canc. Unld. Pend. Flags: D “dirty”: M “migrated”: When the r flag is specified (i.e. -fr: displays volumes which are currently being reorganized) an additional column with the following flags is output: P “pending”: Q “queued”: R “restore”: C “cancelled”: S “save”: When the s flag is specified (i.e.

  • Page 271

    Global Status 7.6.2.6 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. LV1st VSN of the first logical volume of a name group (see below) LVend...

  • Page 272

    History data The columns of the distribution table contain the associated values of the distribution para- meters. The columns containing the number of LVs to which the various distribution para- meter values relate and their percentage share in the total quantity are also visible. The pie chart is a graphical presentation of the distribution table.

  • Page 273

    Global Status 7.6.2.8 Statistics » Logical Components » Logical Volume Groups If multiple logical volume groups exist an intermediate menu is then displayed for selecting the volume group: This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on You can select either all groups or a specific group.

  • Page 274

    History data After you click on “OK” or “Refresh” the following window appears: The following data is displayed: PVG1 PVG2 pending jobs recover jobs lv-size 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...

  • Page 275

    Global Status 7.6.2.9 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: This statistics function supports the refresh function. Information on this function and the “OK”...

  • Page 276

    History data Meaning of the columns: The job data (result for ... :) is output separately for each LVG. Serial number PVG 1 PVG 2 pending jobs lv-size 7.6.2.10 Statistics » Physical Components The following submenus are available: – Physical Drives (see below) –...

  • Page 277

    Global Status 7.6.2.11 Statistics » Physical Components » Physical Drives First of all the library involved is queried: This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on The library required is selected via the drop-down menu. A list of the device statuses is displayed: The output field contains a line with the name of the archive system.

  • Page 278

    History data state Current status of the drive. Possible values: unused occupied disabled unreachable dis./unreach. VSN of the physical volume Physical volume group job state Status of the ongoing operation. Possible values: ===== DONE PLS_INSPECT_SENT PDS_INSPECT_SENT MOUNT_SENT UMOUNT_SENT INIT_SENT INIT_NEW_SENT ERASE_SENT READ_SENT WRITE_SENT...

  • Page 279

    Global Status timestamp Time at which the current status was entered. 7.6.2.12 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. The physical volume(s) can be identified in an intermediate menu: This statistics function supports the refresh function.

  • Page 280

    History data An overview in table form is then shown Meaning of the columns: Line number Number of the physical volume Tape Library: Name of the archive Name of the physical volume group state Status; possible values: e___ E___ f___ f_d_ i___ n___...

  • Page 281

    Global Status s___ _v__ _w__ Write volume that can still be used for save operations. _wd_ The cartridge is not yet full; currently there is no directory on the tape. ____ next-bl Block number of the free range. This indicates the physical utilization level. Number of saved logical volumes Number of valid saved logical volumes;...

  • Page 282

    History data Meaning of the columns: Line number Number of the physical volume Tape Library: Name of the archive Name of the physical volume group, usually starts at “CLNP”. state status The following values are possible for cleaning cartridges: o___ _r__ f___ max.

  • Page 283

    Global Status Meaning of the columns: file-Id bl_nr size/MB save request at The information for a cleaning cartridge contains a list showing all the cleaning runs carried out using this cartridge with the time and PDS of each run: 7.6.2.13 Statistics »...

  • Page 284

    History data When you select all data PVGs the following overview is displayed: Meaning of the columns: Type scratch jobs (wait-work) Reorg. (PV) When you select all cleaning PVGs the following overview is displayed: Meaning of the columns: Type Line number Name of the physical volume group Type of PV group (stacked, transfer, vault or cleaning) Total number of physical volumes in the group...

  • Page 285

    Global Status available/used cycles jobs (wait-work) When you select only one data PVG the settings for the PVG and a list of the PVs stored on it are displayed: U41117-J-Z125-7-76 Number of available cleaning cycles for the physical volumes / number of cleaning cycles which are executed.

  • Page 286

    History data PVG statistics are displayed in the first line. Name Type scratch jobs (wait-work) Number of jobs in queue or being Reorg. (PV) The next block contains the parameters for controlling reorganization. soft minimum number of empty PVs: If the number of free volumes specified here is not reached, reorganization will take place in the reorganization time shown further below.

  • Page 287

    Global Status 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.

  • Page 288

    History data 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.

  • Page 289

    Global Status 7.6.2.14 Statistics » Physical Components » Jobs of Physical Vol. Groups A window for selecting one or all PVGs is opened: This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on 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 type Type of job ERASE INIT INITNEW RDIR REST SAVE UNLOAD WDIR 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 Statistics » Physical Components » Reorganization Status A window for selecting one or all PVGs is opened (naturally the clean PVGs are not offered): This statistics function supports the refresh function. Information on this function and the “OK” and “Cancel” buttons is provided on If only one group is defined this intermediate step is skipped.

  • Page 292

    History data Otherwise the status of the reorganization of the physical volume group(s) is displayed: Meaning of the entries: state retry timestamp The number specified in the retry column also relates to command retries at the PLM-VLM interface. If the high load on the VLM means that a PLM request could not be satisfied within this time limit, the job is issued again.

  • Page 293

    Global Status 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 More detailed information on the retry causes is provided in the system messages (see the section “Show System Messages”...

  • Page 294

    History data Selection fields Accounting data requested for Here you can choose between the following options: all_LVGs selected_LVGs Data fields to be separated by Here you are given the opportunity of outputting the accounting table(s) in a format in which the individual fields are separated either by white space or by a comma. The accounting data for all LVGs in the system is output.

  • Page 295

    Global Status 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 ●...

  • Page 296

    History data 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 <LVG-name>...

  • Page 297: 7.6.3 Data Which Can Be Called Via Objects Of The Global Status

    Global Status 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.

  • Page 298: History Diagrams, Function/menu Bar, File

    History diagrams 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: 7.7.1 Function/menu bar 7.7.1.1 File The following functions are available: – Export – Print –...

  • Page 299

    Global Status 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 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...

  • Page 300: Date

    History diagrams 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 Help Default Cancel Exit This closes the window.

  • Page 301: Time, Range, Mode

    Global Status 7.7.1.3 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.

  • Page 302: Toolbar, Profile, Help

    History diagrams 7.7.1.7 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) –...

  • Page 303: Status Bar, Diagrams For The Throughput (left-hand Part Of The Screen)

    Global Status 7.7.3 Status bar The status bar at the bottom of the screen displays (from left to right) the following informa- tion: remote_time protocol Protocol version Profile last history call Language Platform Version 7.7.4 Diagrams for the throughput (left-hand part of the screen) Overall throughput This function can also be reached via the function bar (see the of »...

  • Page 304

    History diagrams Host adapters For each host adapter a column showing the current throughput for read and write opera- tions 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.

  • Page 305: Diagrams For Virtual Components (central Part Of The Screen)

    Global Status 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 in- stalled: = V3.1D: get_log protocol...

  • Page 306

    History diagrams Outputs for CentricStor V3.1D or higher (get_log protocol) The following diagrams are offered depending on the mode selected (see the de” on page 301): Mount state diagram ● The mounted state is displayed for each emulation/PDSs in the selected period. This shows the time when a cartridge was mounted: Global Status section “Mo-...

  • Page 307

    Global Status Mount summary diagram ● The number of emulations/PDSs in the mounted state at any given time is shown here. This shows how many tapes were unmounted at a particular time: U41117-J-Z125-7-76 History diagrams...

  • Page 308

    History diagrams Outputs for CentricStor < V3.1D (read_log protocol) 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.

  • Page 309

    Global Status 7.7.5.2 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 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.

  • Page 311

    Global Status History diagrams Example for V3.1D U41117-J-Z125-7-76...

  • Page 312

    History diagrams 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). Global Status U41117-J-Z125-7-76...

  • Page 313: Tape Pool Values

    Global Status 7.7.6.2 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: Exporting History Data

    History diagrams 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 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 sup- plied at the interface).

  • Page 316: Command Line Tool For Generating The History Data

    History diagrams 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.

  • Page 317

    Global Status All values which can be selected in the graphical call of the history function can also be spe- cified 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.

  • Page 318

    History diagrams or wild card term> -da <start date (YYYY-MM-DD)> -dv <device name as found| in globstat(*2) or wild card term> -hd <history directory, e.g. /usr/tmp/\ hist_log> (*3) -ho <start hour (>=0 and <24)> -in <ISP name, e.g. ICP0 | or wild card term>...

  • Page 319

    Global Status 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.

  • Page 320

    History diagrams Example 1. Create a file get_hist.sh total -da 2006-03-29 -ho 0 -pt 6h >YIN.total2.txt 2. Transfer file 3. Open Excel macro: Global Status U41117-J-Z125-7-76...

  • Page 321

    Global Status History diagrams 4. Open history file: U41117-J-Z125-7-76...

  • Page 322

    History diagrams Global Status 5. Confirm you wish to open it: U41117-J-Z125-7-76...

  • Page 323

    Global Status 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. U41117-J-Z125-7-76 History diagrams...

  • Page 324

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • Page 325: Xtcc, General

    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)”...

  • Page 326

    General CentricStor recognizes various ISP types. 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.

  • Page 327

    XTCC 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, Title Bar, Status Bar

    Margins of the main XTCC window 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(<IP addr. of ISP><host name of ISP>)-config “<comment from unit list>” if XTCC is running on another ISP in the CentricStor system. GXCC always starts XTCC on the system on which GXCC is also running.

  • Page 329

    XTCC SERV XTCC mode (OBSV=Observe, SERV=Service, USER=User, SIMU=Simulation). 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).

  • Page 330

    Function bar 8.3 Function bar Subfunctions: File ● – Select (page – Save (page – Show (page – Print (page – Exit (page Unit ● – Select (page Options ● – Settings (page – Toggle Size (page – Toggle Aspect (page –...

  • Page 331: Select, File, Save, Show

    XTCC 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: 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.

  • Page 332: Print

    Function bar 8.3.1.4 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.

  • Page 333

    XTCC 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 <path>/outcolor.ps or <path>/outgray.ps, where <path>...

  • Page 334

    Function bar 8.3.1.5 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 – Window Manager function At the top right click on the box containing the X. Click on the CentricStor icon at the top left and in the pull-down menu select the “Close”...

  • Page 335: Unit, Select

    XTCC 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 page 147.

  • Page 336

    Function bar 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.

  • Page 337

    XTCC For Infobox: Move Pointer The infos are displayed by positioning the mouse cursor. Click Button Help in: English German The language of the help texts also controls which version of the online manual is offered in the Help menu. If there is no manual available in that language, no manual is offered in the Help menu.

  • Page 338: Start, Autoscan, Stop

    Function bar 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”...

  • Page 339

    XTCC 8.3.4.3 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 Manual Adjusting (M) Scale Range If “Manual Adjusting”...

  • Page 340: Scan Now, Interaction Timeout

    Function bar 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.

  • Page 341: Xtcc Communications, Tools

    XTCC 8.3.5 Tools The following functions are available: – XTCC Communications – Get Remote/Expand Local File – Show Remote File – Compare Local Files – XTCC Update/Revert 8.3.5.1 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: Get Remote/expand Local File, Show Remote File

    Function bar If messages are present, then the number of messages is displayed by means of the yellow indicator Msg:<n> 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”...

  • Page 343: Compare Local Files, Xtcc Update/revert

    XTCC 8.3.5.4 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”...

  • Page 344

    Function bar 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. When the main menu functions Unit ➟ Select – File ➟ Select – File ➟ Exit –...

  • Page 345

    XTCC 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: CentricStor A CentricStor B CentricStor C CentricStor D Profile data is stored in this directory for each unit under the name <system_name>.opt.

  • Page 346

    Function bar 8.3.6.1 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”...

  • Page 347

    XTCC 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.

  • Page 348: Readme / Liesmich, Help, Direct Help / Direkthilfe, Mouse Functions / Maus-funktionen

    Function bar 8.3.7 Help The appearance of the submenu depends on the language selected in “Settings” (see page 336): German: Help LIESMICH Direkthilfe Maus-Funktionen About XTCC... Benutzerhandbuch 8.3.7.1 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 8.3.7.2...

  • Page 349: About Xtcc

    XTCC 8.3.7.4 About XTCC... The version of XTCC can also be seen at the bottom right of the configuration overview window. Meaning of the buttons 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: Centricstor User Guide

    Function bar 8.3.7.5 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 –...

  • Page 351: Centricstor Service Manual

    XTCC 8.3.7.6 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 –...

  • Page 352: Elements Of The Xtcc Window, Display

    Elements of the XTCC window 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).

  • Page 353

    XTCC The operating status of an element is indicated by the color of the associated box, where the following color key applies: Green: Normal Pink: Malfunctioning, offline or not ready Yellow: Status unclear, some subcomponents are malfunctioning Red: 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 sheets.

  • Page 354: Unexpected Errors

    Elements of the XTCC window 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.

  • Page 355

    XTCC 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.).

  • Page 356: Group Display

    Elements of the XTCC window 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.

  • Page 357

    XTCC The status line is contained at the bottom edge of the Groups window: Autoscan If the group display is minimized, you can reopen it simply by clicking the appropriate tab. When you select a group, its color changes to blue. If you then click your left mouse button, the group is transferred to the configuration display and its number appears in the “Group m of n”...

  • Page 358

    Elements of the XTCC window Color codes in the group display The object colors used in the group display are very similar to those in the configuration display: Turquoise OK Green Pink Yellow White File system Black File system SNMP Brown ACTIVE ACTIVATING...

  • Page 359

    XTCC Explanation File system full: red flashing tool symbol in the configuration overview. Flashing symbol for system messages in the GXCC window. File system 95% full: black flashing tool symbol in the configuration overview. SNMP: SNMP manager has received an SNMP trap. Flashing SNMP symbol in the configuration overview.

  • Page 360: File Viewer

    File viewer 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”...

  • Page 361: Open (text)/open (hex), File, Save As, Re-read, Print, Exit

    XTCC 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)).

  • Page 362: Autoupdate, Start, Stop, Autopopup, Enable, Disable

    File viewer 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.

  • Page 363: Highlight

    XTCC 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.

  • Page 364: Search Down/up

    File viewer 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.

  • Page 365: Mode, Text/hex, Enlarge Font / Reduce Font

    XTCC 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.

  • Page 366: Tab Stop Interval, Help

    File viewer 8.5.8.5 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: Object Information On The Isp

    XTCC 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. If required two additional symbols are displayed: – A yellow flashing SNMP symbol indicates that SNMP data is present. –...

  • Page 368: Isp Functions

    Hardware Type Prod. Serial No. Graphics Board Firmware Autoload InfoBroker Level File system occupancy level (if more than 95%) 8.6.2 ISP functions Function Show Revision History Version Consistency Check Show Diff. Curr./Prev. Version Show Node Element Descriptors Show Configuration Data Show System Log Clean File System Primergy PC model.

  • Page 369: Show Revision History

    XTCC 8.6.2.1 Show Revision History This function is used to display a log showing all the software updates of the ISP: U41117-J-Z125-7-76...

  • Page 370: Version Consistency Check

    8.6.2.2 Version Consistency Check This function is offered only if the consistency check mechanism is available on the moni- tored 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 devel- oper corrections.

  • Page 371: Show Diff. Curr./prev. Version

    XTCC 8.6.2.3 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 differ- ences are marked with colors and the number is shown at the bottom right in the status line.

  • Page 372: Show Node Element Descriptors

    8.6.2.4 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 under- lying virtual devices: Show/View functions open windows that are equipped with scroll bars and search functions.

  • Page 373: Show Configuration Data

    XTCC 8.6.2.5 Show Configuration Data Outputs a configuration display in table form: 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

    The SCSI devices are represented in the normal way as c (=controller) <cc>t(=target)<tt>l(=Lun)<ll>, where cc, tt, ll are shown as decimal numbers. 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.

  • Page 375: Show System Log, Show Snmp Data, Clean File System

    XTCC 8.6.2.6 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.

  • Page 376: Internal Objects Of The Isp, Representation Of Internal Objects, Hard Disk Drives

    Internal objects of the ISP 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: Cd-rom, Streamer

    XTCC 8.7.1.2 CD-ROM The status of a CD-ROM drive is indicated by the following colors: Turquoise: Pink: Yellow: If the mouse pointer is positioned over such an object, its color changes to blue, indicating that it is selected. If you press the left mouse button, a window containing the following information appears: –...

  • Page 378: Scsi Controller, Hard Disk, Cd-rom, Streamer, All Internal Objects, 8.7.2.3 Raid Controller

    Internal objects of the ISP 8.7.1.4 SCSI controller This is represented exactly as described in the controllers” on page 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. The status of the controller is indicated by the following colors: Pink: Hang condition “true”...

  • Page 379: Escon/ficon Host Adapter, Object Information For The Escon/ficon Host Adapter

    XTCC 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 Example for a FICON host adapter ● The following information is also displayed in the information box: Adapter Status Board Number Board Type Bus Type Bus Number Device Number WW Node Number WW Port Number Node ID Channel Nodes Connecting lines to the hosts...

  • Page 381: Escon/ficon Host Adapter Functions, Show Node Id Details

    XTCC 8.8.2 ESCON/FICON host adapter functions The following functions are available: – Show Node ID Details – Show Node Element Descriptors – Show Dump (prkdump) 8.8.2.1 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.

  • Page 382

    ESCON/FICON host adapter 8.8.2.2 Show Node Element Descriptors Display of the node element descriptors of an ESCON/FICON host adapter and the under- lying virtual devices. 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 page 360.

  • Page 383: Show Dump (prkdump)

    XTCC 8.8.2.3 Show Dump (prkdump) Display of the host adapter driver dump: To analyze this dump, you will need detailed knowledge of the system. U41117-J-Z125-7-76 ESCON/FICON host adapter...

  • Page 384: Information On Emulations

    Emulations of drives connected to OS/390 host adapters 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.

  • Page 385: Functions For Individual 3490 Emulations

    XTCC The information box contains the following information: Emulation Virtual Drive Mnemonic CIuster, Unit Revision Attached Path (CUI, CHI): n,t,cc,llll,a,uu (uu, cc) Describes the paths to the hosts: Host adapter number Host adapter type Channel image if defined llll: Link address (connection number of the host on the ESCON director) Connection status (a=attached) Control Unit Image (CUI) Channel Process/Device Process/Last Error...

  • Page 386: Show Error/transfer Statistics

    Emulations of drives connected to OS/390 host adapters 8.9.2.1 Show Error/Transfer Statistics Display of the error and statistical data transferred to the host: XTCC U41117-J-Z125-7-76...

  • Page 387: Show Short Trace

    XTCC 8.9.2.2 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 termi- nation. U41117-J-Z125-7-76 Emulations of drives connected to OS/390 host adapters...

  • Page 388: Show Path Trace

    Emulations of drives connected to OS/390 host adapters 8.9.2.3 Show Path Trace Displays the path sequence of I/Os: XTCC U41117-J-Z125-7-76...

  • Page 389: Show Error Log

    XTCC 8.9.2.4 Show Error Log Displays a text window containing the error log of the virtual device or emulation. Logical device error messages may be issued as a result of: – operating errors (read command for empty drive, write command for write-protected volume) –...

  • Page 390: Show Memory Log, Functions For All 3490 Emulations

    Emulations of drives connected to OS/390 host adapters 8.9.2.5 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...

  • Page 391: Virtual 3490 Drives, Object Information And Error Messages For Virtual 3490 Drives

    XTCC 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: Error Conditions Indicated On The Display

    Virtual 3490 drives The display can contain one of the following messages: Display 0 CU READY CU ONL EMU STOP When a logical volume is loaded, the third line specifies which cache contains the associated data. 8.10.1.1 Error conditions indicated on the display Display 1 Display 2 EMU STOP ERR #001...

  • Page 393: Object Information, Sim/mim Error Messages On Virtual Devices

    XTCC 8.10.1.2 Object information The extended information contains the following data: Drive Status Check Condition Medium Type Password Compression VSN-Location Cache-Directory The graphical display also indicates error messages that have not yet been acknowledged. A flashing icon indicates whether Service Information Messages (SIM) or Media Infor- mation Messages (MIM) exist.

  • Page 394: Virtual Drive Functions

    Virtual 3490 drives 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’ 0C01 0C02 0C03 0C04 0C05 0C06 B111 0815 0816 0817 8.10.2 Virtual drive functions The following functions are available: –...

  • Page 395: Show Scsi Sense

    XTCC 8.10.2.1 Show SCSI Sense 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.

  • Page 396: Show Medium Info (mim)

    Virtual 3490 drives 8.10.2.2 Show Medium Info (MIM) An info box appears if no MIM log exists: Displays the latest Media Information Messages in a text window. XTCC U41117-J-Z125-7-76...

  • Page 397: Show Service Info (sim), Unload And Unmount

    XTCC 8.10.2.3 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 mation” on page 8.10.2.4 Unload and Unmount This function is used to unload and unmount the virtual volume. U41117-J-Z125-7-76 393.

  • Page 398: Fc-scsi Host Adapter, Object Information On Fc-scsi Host Adapters

    FC-SCSI host adapter 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: Fc-scsi Host Adapter Functions, Perform Link Down/up Sequence, Emulations Of Scsi Drives (vtd)

    XTCC 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 dis- play on the module.

  • Page 400

    Emulations of SCSI drives (VTD) The figure below shows the characteristics of an emulation as displayed in XTCC. The information box displays: Virtual Tape Device Logical Unit Number Controller Revision Process ID Active, Own and Default Trace Configuration Internal SINIX name for the device. LUN on the FC-SCSI interface.

  • Page 401: Functions For Individual Vtd Emulations, Show Trace, Functions For All Vtd Emulations

    XTCC 8.12.2 Functions for individual VTD emulations The following function is available: – Show Trace 8.12.2.1 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.

  • Page 402: Virtual Scsi Drives

    Virtual SCSI drives 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 Cen- tricStor systems with an external RAID, a logical volume is addressed via a mount point (e.g.

  • Page 403

    XTCC The following is displayed: Inquiry data Drive Status Check Condition: Reservation Medium Type: VSN Location Base Directory Depending on the operating status, some of the information listed above may not be displayed. U41117-J-Z125-7-76 Vendor ID, product ID, product revision level, drive serial number. Vendor ID and product ID can be selected during configuration.

  • Page 404: Unload And Unmount, Show Medium Info (mim), Show Service Info (sim)

    Virtual SCSI drives 8.13.2 Virtual generic drive functions Depending on the emulation, the following functions are available: /390 VDRV 8.13.2.1 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”.

  • Page 405: Vls (virtual Library Service), Object Information On Vlss

    XTCC 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.

  • Page 406: Functions For Individual Vlss, Show Trace, Global Functions For All Vlss Of An Isp

    VLS (Virtual Library Service) The following information is also output for VLSs of the type VJUK: ● Vendor ID Product ID Serial No Slots Controller Mode 8.14.2 Functions for individual VLSs The functions available for a VLS depend on its type. VDAS has the “Show Trace”...

  • Page 407: Vmd (virtual Mount Daemon), Object Information On The Virtual Mount Daemon (vmd), Vmd Functions

    XTCC 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.

  • Page 408: Vlm (virtual Library Manager), Object Information For The Vlm, Vlm Functions, Show Cache Status

    VLM (Virtual Library Manager) 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.

  • Page 409

    XTCC 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: Set Halt Mode/set Run Mode

    VLM (Virtual Library Manager) 8.16.2.2 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.

  • Page 411: Raid Systems, Object Information On Raid Systems

    XTCC 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.

  • Page 412

    RAID systems The controller types differ slightly in their presentation of the functions available: XTCC Eternus 3000/4000 CX500/CX3-20 S80 (=FC2502) Internal RAID system U41117-J-Z125-7-76...

  • Page 413

    XTCC In the case of external RAID systems, the information window contains the following infor- mation: – 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) –...

  • Page 414: Functions Of Raid Systems, Show Complete Raid Status (all Types)

    RAID systems 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.

  • Page 415: Show Mode Pages (cx500/cx3-20 And Fcs80), Show Mode Page Details, Show Log Pages

    XTCC 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.

  • Page 416

    PLM (Physical Library Manager) 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).

  • Page 417: Pls (physical Library Service), Object Information On The Pls, Functions For Individual Plss

    XTCC 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, Object Information On Archive Systems

    SCSI archive systems 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.

  • Page 419: Scsi Archive System Functions, Show Mode Pages, Show Mode Page Details, Show Log Pages

    XTCC 8.20.2 SCSI Archive system functions This function is offered after you right-click on the archive system icon (behind the drive icon). The Show Mode Pages, Show Mode Page Details, Show Log Pages and Show Log Page Details functions are not offered for all libraries. 8.20.2.1 Show Mode Pages The SCSI mode pages are displayed.

  • Page 420

    PDS (Physical Device Service) 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 infor- mation 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.

  • Page 421: Scsi Controllers, Object Information On Scsi Controllers

    XTCC 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 Max. Targets Name Interface Target Location Mode WW Node Number WW Port Number 8.22.2 SCSI controller functions No menu is provided in Observe mode. The title bar displays the serial number of the SCSI interface and the controller number. The functions are used to diagnose problems and eliminate hang conditions.

  • Page 423: Cartridge Drives (real), Object Information On Tape Drives

    XTCC 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) 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”.

  • Page 425: Tape Drive Functions

    XTCC 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 –...

  • Page 426: Show Log Pages, Show Scsi Sense

    Cartridge drives (real) 8.23.2.1 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): –...

  • Page 427: Show Log Page Details, Show Mode Pages

    XTCC 8.23.2.3 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: Show Mode Page Details

    Cartridge drives (real) 8.23.2.5 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. The SCSI topology (CTL) as well as the Inquiry String of the drive are shown in the “control lines”...

  • Page 429: Show Vital Product Data

    XTCC 8.23.2.6 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.

  • Page 430

    Cartridge drives (real) 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 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: Global Functions For Tape Drives, Show Service Info (sim)

    Cartridge drives (real) 8.23.2.8 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.

  • Page 433: Remove Symbols Of All Drives, Msgmgr (message Manager), Object Information On The Message Manager (msgmgr)

    XTCC 8.23.3.1 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...

  • Page 434: Show Trace, Show Trap Trace

    MSGMGR (Message Manager) 8.24.2.1 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). XTCC U41117-J-Z125-7-76...

  • Page 435: Perflog, Object Information Of Perflog

    XTCC 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”...

  • Page 436: Perflog Functions

    PERFLOG 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. XTCC U41117-J-Z125-7-76...

  • Page 437: Accountd (account Daemon)

    XTCC 8.26 ACCOUNTD (Account Daemon) 8.26.1 Object information of ACCOUNTD The Account Daemon records the accounting data in a database. 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).

  • Page 438: Mirrord (mirror Daemon), Object Information Of Mirrord, Functions Of Mirrord

    MIRRORD (mirror daemon) 8.27 MIRRORD (mirror daemon) 8.27.1 Object information of MIRRORD The mirror daemon monitors the status of the cache mirror. 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: Object Information Of S80d, Functions Of S80d

    XTCC 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 Process ID Autostart enabled / disabled The status of the daemon is indicated by the following colors: pink Stopped green...

  • Page 440: Vlpwatch (vlpwatch Daemon), Object Information Of Vlpwatch, Functions Of Vlpwatch

    VLPWATCH (VLPwatch daemon) 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.

  • Page 441: Explanation Of Console Messages, General

    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”...

  • Page 442

    General 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 None INFO DEBUG NOTICE WARNING ERROR CRITICAL ALERT EMERGENCY Alarm message: the system is in an unstable state The weight is normally a component part of the message text.

  • Page 443

    Explanation of console messages 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 In the sections below, only the message line components printed in bold here, i.e.

  • Page 444

    General The message numbers in the following section are arranged alphabetically SXCF... (CMF: Cache Mirroring Feature) SXCH... (Channel: pcib/pcea) SXCM... (CHIM) SXDN... (DNA: Distribute and Activate) SXDT... (DTV File System) SXFC... (FibreChannel Driver) SXFP... (FibreChannel Driver) SXFW... (Firmware) SXIB... (Info Broker) SXLA...

  • Page 445: Message Lines, Sxcf... (cmf: Cache Mirroring Feature)

    Explanation of console messages 9.2 Message lines 9.2.1 SXCF... (CMF: Cache Mirroring Feature) SXCF012 CMF(#12): ALERT: failed to become PRIMARY, time exhausted: 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.

  • Page 446

    Message lines 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).

  • Page 447: Sxch... (channel: Pcib/pcea)

    Explanation of console messages 4. Check whether the mirror server’s processes are running: myps mirror.s Sample output ? 922 ? 5179 ? 5177 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 ESCON-ad pcea<port> (bus <pci-bus> dev <pci-device>) started NOTICE Meaning The ESCON port <port> has been activated. This happens regularly at system startup. A port can also be reactivated after being reset or deactivated. SXCH005 ESCON-ad pcea<port> (bus <pci-bus> dev <pci-device>) Memory error ALERT Meaning A memory error has occurred on the ESCON board.

  • Page 449: Sxcm... (chim)

    Explanation of console messages SXCH009 ESCON-adaptor <board> (ser_no <serial-nr) Compare Error in Channel <chn> ALERT 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.

  • Page 450: Sxdn... (dna: Distribute And Activate)

    Message lines 9.2.4 SXDN... (DNA: Distribute and Activate) SXDN100 (DNA#100): ALERT: switch SVLP_to_VLP successfully completed! (needed time: <mm>:<ss> (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>...

  • Page 451

    Explanation of console messages SXDT003 DTV(# 3): ALERT: dev=<maj,min>: 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 ...).

  • Page 452

    Message lines 9.2.6 SXFC... (FibreChannel Driver) SXFC026 PVA1ICP0 : FC2: IOCB_E_LOCAL_REJECT ALERT SXFC005 PVA1ICP0 : FC2: loop_id 0, IOCB error sequence timeout None 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 FC5: RSCN for port 00637713 received NOTICE 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.

  • Page 454: Sxfp... (fibrechannel Driver)

    Message lines The message is only significant for external FC controllers. The abortion may have been initiated either by the SAN host or CentricStor. <host> 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.

  • Page 455: Sxfw... (firmware)

    Explanation of console messages Temporary unavailability of the FC The following message complex, with LOOP-DOWN, rescheduling and LINK-UP messages, is output: SXFP041 fcpal<n> (sadm<k>): rescheduling after temporarily unavailable resource None SXFP041 fcpal<n> (sadm<k>): rescheduling on intr : unavailable resource None SXFP041 fcpal<n>...

  • Page 456: Sxib... (info Broker)

    Message lines 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.

  • Page 457

    Explanation of console messages SXIB200 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 archi- ved. Obsolete performance history log files are automatically deleted after the recording pe- riod has elapsed .

  • Page 458: Sxla... (lanwatch), Sxlv... (log Volume)

    Message lines 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...

  • Page 459: Sxmm... (message Manager)

    Explanation of console messages 9.2.12 SXMM... (Message Manager) SXMM007 KLOG[<pid>]: INFO: Message Manager unavailable! Meaning Information that the Message Manager is not available. Response Notify maintenance staff. SXMM005 KLOG[<pid>]: WARNING: vlsTrace(<trace signal>) 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 KLOG[<pid>]: WARNING: fopen(/dev/osm) error errno=<error number> <error description> Meaning Error while opening /dev/osm. Response Notify maintenance staff. SXMM005 KLOG[<pid>]: WARNING: fstat(/dev/osm) error errno=<error number> <error description> Meaning Error while accessing /dev/osm. Response Notify maintenance staff. SXMM005 KLOG[<pid>]: WARNING: stdout error errno=<error number> <error description>...

  • Page 461

    Explanation of console messages SXMM007 KLOG[<pid>]: INFO: setsid() errno=<error number> <error description> Meaning Internal process error SXMM012 VLSM[<pid>]: WARNING: too many client entries pid=<process id> sd=<socket descriptor> Meaning Owing to lack of space the Message Manager could not accept any new connection request.

  • Page 462

    Message lines SXMM012 VLSM[<pid>]: WARNING: Check Path /usr/apc/tmp/msgadm error Meaning The directory /usr/apc/tmp/msgadm cannot be created. Response Notify maintenance staff. SXMM012 VLSM[<pid>]: WARNING: chdir(/usr/apc/tmp/msgadm) error errno=<error number> <error description> Meaning Error while changing the working directory to /usr/apc/tmp/msgadm. Response Notify maintenance staff. SXMM012 VLSM[<pid>]: WARNING: VTLS configuration file read error Meaning...

  • Page 463

    Explanation of console messages Response Notify maintenance staff. SXMM013 VLSM[<pid>]: NOTICE: File <filename> removed Meaning Information indicating that the oldest history file has been removed. SXMM014 VLSM[<pid>]: INFO: No space left in /msg (kbytes=<n> used=<n> avail=<n> capacity=<n>) 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 Response Notify maintenance staff. SXMM019 EMSG[<pid>]: WARNING: ReadNextEvtMsgLine() error Meaning Error while reading the event message file. Response Notify maintenance staff. SXMM019 EMSG[<pid>]: WARNING: fork() error errno=<error number> <error description> Meaning Internal process error Response Notify maintenance staff. SXMM019 EMSG[<pid>]: WARNING: vlsTrace(<trace filename>) error Meaning...

  • Page 465: Sxpl... (plm: Physical Library Manager)

    Explanation of console messages SXMM019 EMSG[<pid>]: INFO: Message Manager unavailable! Meaning Information that the Message Manager is not available. Response Notify maintenance staff. SXMM021 EMSG[<pid>]: INFO: ******* START EmsgTrap (EventMessageTrap) daemon Meaning Information on the start of the process EmsgTrap. SXMM021 EMSG[<pid>]: INFO: reopen(stdin)->/dev/null error Meaning...

  • Page 466

    Message lines SXPL003 PLM(#3): ALERT: <PDS-name> on <hostname> not reachable Meaning It was not possible to send a message to the PDS <PDS-name> on the host <hostname>. Response Check whether the PDS and/or host are running and whether the TCP/IP connection is okay.

  • Page 467

    Explanation of console messages 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”...

  • Page 468

    Message lines SXPL011 PLM(#11):NOTICE: number of free PVs of PV-group <PVG> over absolute minimum (< >) again Meaning The number of free tapes is again greater than the absolute minimum. SXPL012 PLM(#12): ERROR: <PDS-name> doesn't eject a volume, probably hardware error Meaning The PDS <PDS-name>...

  • Page 469

    Explanation of console messages 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 chip 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 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 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.

  • Page 472

    Message lines 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: <PDS-name> reports error = <PDS-error-string> on PV <PV-name> Meaning The PDS <PDS-name>...

  • Page 473

    Explanation of console messages 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 CentricStor- compatible header to the tape (“Add physical Volume”).

  • Page 474

    Message lines 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.

  • Page 475

    Explanation of console messages SXPL021 LM(#21): NOTICE: Reorganisation failed for LV <LV-name> on PV <PV-name>, continue Meaning A reorganization operation initiated by the user encountered an error. The logical volume <LV-name> could not be read from the physical volume <PV-name>. An attempt will be made to move any other logical volumes from this physical volume.

  • Page 476

    Message lines SXPL025 PLM(#25): WARNING : <num> single saved LVs in dual save LV-group <name> 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.

  • Page 477

    Explanation of console messages 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. SXPL031 PLM(#31):WARNING: Initialization failed for PV <name>, PV-group <name>;...

  • Page 478

    Message lines SXPL041 PLM(#41): NOTICE: Cleaning-group of Tape-library <name> 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 <name>...

  • Page 479

    Explanation of console messages SXPL048 PLM(#48): NOTICE: <num> cleancycles for tape-library <name> available again Meaning PLM(#45) has been correctly responded to? SXPL049 PLM(#49): WARNING: ejected PV <name> of tapelibrary <name> 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.

  • Page 480

    Message lines Response Only use cartridges with enough capacity. SXPL056 PLM(#56): NOTICE: all PVGs of TL <name> deactivated Meaning This message is output after the plmcmd conf -e -T <TL> command has been issued: All physical volume groups of the specified robot have been deactivated. SXPL057 PLM(#57): NOTICE: all PVGs of TL <name>...

  • Page 481

    Explanation of console messages SXPL062 PLM(#62): ERROR: LV <name> can not be reorganized, reason: <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” sta- tus and can therefore not be read in.

  • Page 482: Sxps... (pls: Physical Library Server)

    Message lines 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.

  • Page 483

    Explanation of console messages SXPS006 PLS(#4006) ERROR: <robot error message> 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 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.

  • Page 485: Sxrd... (fibrecat: Raid), Messages Of The Monitoring Daemon For The Internal Raid

    Explanation of console messages 9.2.15 SXRD... (FibreCAT: RAID) The table below shows the message numbers with the RAID systems which issue the messages: Message number SXRD001 SXRD100 - SXRD104 SXRD002 - SXRD009 SXRD010 SXRD501, SXRD901 9.2.15.1 Messages of the monitoring daemon for the internal RAID Messages during ongoing operation SXRD001 NOTICE: raidd: 0:BBU - charging [xx] completed...

  • Page 486

    Message lines SXRD001 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.

  • Page 487

    Explanation of console messages SXRD001 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.

  • Page 488: Fibrecat S80 Messages

    Message lines SXRD104 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 FibreCAT S80 messages SXRD00<n> s80d: RAID: <weight>: <raid-id> Raid<raid#> enclosure <shelf#> <component> <status>...

  • Page 489: Fibrecat Cx500 And Cx3-20 Messages

    Explanation of console messages 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: Warning Not Available Unknown Critical Not Installed...

  • Page 490

    Message lines 9.2.15.4 FibreCAT CX500 and CX3-20 messages SXRD501 RAID: NOTICE <raid-id> Hard SCSI Error recovered (<#501>) c<ctrl>t<tgt>l<lun> Where: <raid-id> c<ctrl>t<tgt>l<lun> Meaning Access via the specified path is possible again (positive message, cf. SXRD901). SXRD901 RAID: ALERT <raid-id> Hard SCSI Error (<#901>) c<ctrl>t<tgt>l<lun> Where: <raid-id>...

  • Page 491: Sxrp... (rplm: Recovery Physical Library Manager)

    Explanation of console messages 9.2.16 SXRP... (RPLM: Recovery Physical Library Manager) SXRP003 RPLM(#3): ALERT: <PDS-name> on <hostname> not reachable Meaning It was not possible to send a message to the PDS <PDS-name> on the host <hostname>. Response Check whether the PDS and/or host are running and whether the TCP/IP connection is okay.

  • Page 492

    Message lines SXRP015 RPLM(#15): ERROR: <PDS-name> reports sense = <Sense-Byte-Value> on PV <PV-name> Meaning The PDS <PDS-name> has reported an error code for the physical volume <PV-name>. Response Notify maintenance staff. SXRP016 RLM(#16): ERROR: <PDS-name> reports error = <PDS-error-string> on PV <PV-name> Meaning The PDS <PDS-name>...

  • Page 493

    Explanation of console messages SXRP019 RPLM(#19): NOTICE: job canceled on PDS <pds>, PV <pv>, state <state> Meaning The PLS or the PDS could not execute a job because of a timeout. Describes the command in which the timeout occurred. <state> For the PLS: For the PDS: The command is extended by the suffix _SENT_TIMECHECK.

  • Page 494: Sxsb... (sadm Driver: Scsi Bus Error)

    Message lines SXRP051 RPLM(#51): ERROR: <pds> reports errno = <num> ( <string> ) on PV <name> Meaning The PDS has detected an error. Response Notify maintenance staff if necessary. SXRP052 RPLM(#52): NOTICE: PLS reports VOLUME ERROR for PV <pv>, PV-file will be removed Meaning The physical library does not know this PV.

  • Page 495: Sxsc... (savecore: Organize Coredump), Sxsd... (scsi Disks: Driver Shd)

    Explanation of console messages SXSB007 <PC> : fcpal<n> (sadm<m>): timeout on target <t> lun <l> CDB <some bytes> ALERT For more information, see the page 538 Meaning An I/O operation has taken too long (minutes!), and as a result has been stopped and started again.

  • Page 496: Sxse... (exabyte Tapes)

    Message lines SXSD017 shd<k>t<ctl>: ALERT Meaning Irrecoverable read errors occur sporadically on the FibreCAT RAID disk array despite mirroring. Response Notify maintenance staff. SXSD018 shd<k>t<ctl>: Target vanished See the section “Failover at the RAID system” on page 541 9.2.20 SXSE... (EXABYTE Tapes) SXSE005 WARNING: exa: out of spt, deconfiguring exa Meaning...

  • Page 497: Sxsm... (server Management)

    Explanation of console messages 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 <Id>...

  • Page 498

    Message lines 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 sma#: Memory Module <Id> disabled ALERT SXSM010 sma#: Memory Module disabled; Module# = <Id> ALERT Meaning Memory module <Id> 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.

  • Page 500

    Message lines SXSM018 sma#: Fan <Id>: Fan is not manageable ALERT Meaning Fan <Id> 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.

  • Page 501

    Explanation of console messages SXSM026 sma#: <Id> Voltage is too low ALERT Meaning The voltage with ID <Id> is too low. This message can also be triggered by faulty regulators, sensors, batteries or power supplies. Response Notify maintenance staff. SXSM027 sma#: <Id>...

  • Page 502

    Message lines 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 sma#: Fan <Id>: Fan was removed ALERT Meaning Fan <Id>...

  • Page 503

    Explanation of console messages SXSM036 sma#: CPU <ID> internal error occurred ALERT Meaning An internal error was detected in CPU <Id>. Response Notify maintenance staff. SXSM037 sma#: Fan <Id> connection to fanboard defective ALERT 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 sma#: Memory Error Logging limit reached ALERT 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 sma#: Memory Module configuration error; [Module# = <Id>] ALERT Meaning The memory configuration is errored.

  • Page 505

    Explanation of console messages Response Notify maintenance staff. SXSM046 sma#: PCI system error; bus# <a>; device# <b>; function# <c> ALERT Meaning A PCI system error is indicated by an onboard device. The onboard device is indicated by the bus/device/function <a, b, c> parameters. Response Notify maintenance staff.

  • Page 506

    Message lines SXSM049 sma#: Primergy Product Serial Number not available ALERT 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).

  • Page 507

    Explanation of console messages Response Notify maintenance staff. SXSM054 sma#: CPU <Id> automatically throttled ALERT 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 tempera- ture range.

  • Page 508

    Message lines Response Check the ambient temperature and the fan situation. Notify maintenance staff iff no con- nection to increased ambient temperatures or fan faults could be determined and this mes- sage continues to appear. SXSM058 sma#: Fatal general memory error; Module# = <Id> ALERT SXSM059 sma#: Recoverable general memory error;...

  • Page 509

    Explanation of console messages SXSM501 sma#: BIOS Boot Retry Counter countdown occurred - maybe watchdog timeout ALERT Meaning The Boot Retry Counter Response Notify maintenance staff. SXSM502 sma#: Internal error at communication with autoss ALERT 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.

  • Page 510: Sxsw... (software Mirror)

    Message lines 9.2.22 SXSW... (Software Mirror) SXSW010 SWM(#10): ALERT: <dev> mirror degrade: <part> failed Meaning Part of the mirror (<part>, primary or secondary) has failed. As the device <dev> is designed with redundancy, operations can continue. However, the remaining part is no longer failsafe.

  • Page 511

    Explanation of console messages SXTF003 ERROR: dtv_ipalloc: dtv_ipsize too big, set to <val> 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.

  • Page 512

    Message lines SXTF004 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. Perfor- mance may be reduced. Response Notify maintenance staff if message occurs during normal operation.

  • Page 513

    Explanation of console messages SXTF005 NOTICE: dtv_iread: root directory stale! SXTF005 NOTICE: dtv_rdlookup: root directory stale: <name>, ino=<num> 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 NOTICE: dtv_iread(<maj,min>: ino=<ino>): root directory stale! SXTF005 NOTICE: dtv_rdlookup(<maj,min>: ino=<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 PANIC: dtv_iactive(<maj,min>: <cnt> 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: <func>:\ illegal value <val> for variable <var>, use default <val> Meaning The value of a variable configurable using space.c is invalid.

  • Page 516

    Message lines SXTF011 DTV_FSCK(dev=<maj,min>): <message> ...<message> 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 vdrv<n> (FAILOVER): switch ... ERROR See the section “Failure of RAID systems” on page 540 RAID system”...

  • Page 517: Sxvl... (vlm: Virtual Library Manager)

    Explanation of console messages 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.

  • Page 518

    Message lines SXVL006 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”.

  • Page 519

    Explanation of console messages SXVL013 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 Meaning This message occurs only if the VLM is configured for cache only mode, for example if the system was previously not configured for cache only mode and now the number of logical volumes exceeds the limit which depends on the cache size.

  • Page 520

    Message lines SXVL020 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.

  • Page 521: Sxvls... (vt_ls: Virtual Tape And Library System)

    Explanation of console messages SXVL997 VLM 997 NOTICE "Automatically restarted 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.

  • Page 522: Sxvs... (vls: Virtual Library Server)

    Message lines 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.

  • Page 523: Sxvw... (vlpwatch)

    Explanation of console messages 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 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 VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: Raid1 (cache 100 | 101) not mounted! SXVW007 VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: connection to LAN and start of vtls prevented! SXVW007 VLPWATCH: ALERT: VW(#007) AutoVLP-Failover: please correct the Raid1-connection and reboot the system! Meaning No connection to RAID1 could be set up.

  • Page 525

    Explanation of console messages 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.

  • Page 526

    Message lines 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 infor- mation is stored in the log_VLPwatch and log_vlpwatch files in the logging directory /etc/vtls/log.

  • Page 527

    Explanation of console messages SXVW020 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.

  • Page 528

    Message lines 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.

  • Page 529

    Explanation of console messages SXVW031 VLPWATCH: ALERT: VW(#031) AutoVLP-failover: internal or external LAN connection is not configured; terminated! SXVW031 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.

  • Page 530

    Message lines SXVW038 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;...

  • Page 531

    Explanation of console messages SXVW046 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 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 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 wor- king. Response Investigate and correct the LAN connection problem. SXVW059 VLPWATCH: ALERT: VW(#059) AutoVLP-Failover: FC connection to RA ID is DOWN on SVLP;...

  • Page 534

    Message lines SXVW064 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.

  • Page 535

    Explanation of console messages SXVW068 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...

  • Page 536

    Message lines SXVW073 VLPWATCH: ALERT: VW(#073) AutoVLP-Failover: VLPwatch on <isp_name> is running, communication to <isp_name> is defective (internal LAN or Broker on <isp_name> down)! Meaning VLPwatch on the SVLP is running, but communication to the SVLP via the Broker has been interrupted.

  • Page 537: Sxvx... (veritas File System)

    Explanation of console messages 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.

  • Page 538: Message Complexes, Timeout On The Raid Disk Array

    Message complexes 9.3 Message complexes 9.3.1 Timeout on the RAID disk array SXSB007 fcpal0 (sadm12): timeout on target <t> lun <l> CDB ...F C0 00 01 80 00 ALERT 0007b790: fc_send_fcp: FCP_ABORT... 0007b790: response: error = 0x03, vendor = 0x16, expl = 0x00, reason = 0x00, action 0x00 0007b790: freeing FC_E_ABORT_REQUESTED SXSD013...

  • Page 539: Timeout On The Mtc Drives

    Explanation of console messages 9.3.2 Timeout on the MTC drives SXSB007 adsl1 (sadm<n>): timeout on target <t> lun <l> CDB ... ALERT SXSB007 adsl2 (sadm<n+1>): timeout on target <t> lun <l> CDB ... ALERT followed by WARNING: (adsl,3rd) Adaptec AIC-7870 PCI SCSI HBA: CH0 TARGET<t> LUN<l> is being reset Ph_NonInit: calling Ph_AbortDev Ph_AbortDev: scanning for target <t>...

  • Page 540: Failure Of Raid Systems

    Message complexes 9.3.3 Failure of RAID systems SXVD001 vdrv<n> (FAILOVER): switch 0:40->1:41 SXVD001 vdrv<n> (FAILOVER): switch 1:41->0:40 SXVD002 vdrv<n> (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;...

  • Page 541: Failover At The Raid System

    Explanation of console messages 9.3.4 Failover at the RAID system SXSD018 shd<k>t<ctl>: Target vanished SXSD015 shd<k>t<ctl>: "Drive Not Ready" (0x04) ascq 0x02 WARNING followed by SXVD004 vdrv<n> (FAILOVER): int switching SXVD001 vdrv<n> (FAILOVER): switch 0:4->1:5 but not followed directly by another “switch” message. Meaning Normal failover.

  • Page 542: Bus Reset For Scsi Controller

    Message complexes 9.3.5 Bus Reset for SCSI Controller SXCM001 chim1 (sadm9): SCSI-Bus reset None SXSB001 chim1 (sadm9): SCSI-Bus reset None SXSB005 chim1 (sadm9): RESETTING CONTROLLER None Meaning A bus reset was triggered for SCSI controller 9 (in this example, chim/Adaptec controller 1). Explanation of console messages U41117-J-Z125-7-76...

  • Page 543: Waste Disposal And Recycling

    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.

  • Page 544

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • Page 545: Contacting The Help Desk

    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. U41117-J-Z125-7-76...

  • Page 546

    Eine Dokuschablone von Frank Flachenecker by f.f. 1992...

  • Page 547: Appendix, Integration Of Centricstor V3.1 In Snmp, Structure

    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.

  • Page 548: Activating Snmp On Centricstor, Configuring Snmp Under Centricstor, Activating The Configuration, Changes In Central Files

    Integration of CentricStor V3.1 in SNMP 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. Conse- quently SNMP only needs to be configured on this processor. If a standby VLP exists (VLP1), SNMP configuration must also be performed on this processor.

  • Page 549: Monitoring Centricstor, Gxcc As A Monitoring Tool Without Snmp

    Appendix 12.1.3 Monitoring CentricStor 12.1.3.1 GXCC as a monitoring tool without SNMP 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.

  • Page 550: Monitoring Using Any Snmp Management Station

    Integration of CentricStor V3.1 in SNMP 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.

  • Page 551: Centricstor Global System State, Gxcc On The Snmp Management Station

    Appendix 12.1.3.3 CentricStor Global System State Every 300 seconds the Global System State (see the without SNMP” on page 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 #:...

  • Page 552: Reading In The Gui Cd

    Integration of CentricStor V3.1 in SNMP 12.1.3.6 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.

  • Page 553: Installation Of The Ca Unicenter Extensions For Centricstor, Identification And Editing Of The Centricstor Traps

    Appendix 12.1.4.2 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 exten- sions.

  • Page 554: Working With Ca Unicenter And Centricstor, Centricstor Icon Under Ca Unicenter

    Integration of CentricStor V3.1 in SNMP 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. In the WorldView tree you see the CentricStor systems Cest and STAR-VLP0 in the figure below: Appendix U41117-J-Z125-7-76...

  • Page 555: Identifying A Centricstor And Assigning The Icon

    Appendix 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: Receipt And Preparation Of A Centricstor Trap

    Integration of CentricStor V3.1 in SNMP 12.1.5.3 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: Monitoring Centricstor Using Ping And Mib-ii

    Appendix 12.1.5.4 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.

  • Page 558

    E-mail support in CentricStor 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.

  • Page 559

    Appendix – 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.so...

  • Page 560: Configuring The E-mail Template

    E-mail support in CentricStor 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: Description Of The E-mail Formats

    Appendix 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 479) and SXPL050 12.2.4 Description of the e-mail formats...

  • Page 562: Transferring Volumes, Introduction

    Transferring volumes 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: Export Procedure

    Appendix 12.3.2 Export procedure 1. Copying LVs TR-LVG A00001 Z10000 TR-PVG A00001 Z10000 Figure 36: Copying an LV to TR-PVG With the aid of the transfer-out command (see the the PLM creates an additional copy of the LVs selected for export in a special transfer LVG, theTR-LVG.

  • Page 564

    Transferring volumes 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 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 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: Similarly to cleaning groups, no configuration parameters are output in response to...

  • Page 566: Additional Command Line Interface (cli), Transfer-out

    Transferring volumes 12.3.5 Additional command line interface (CLI) 12.3.5.1 Transfer-out plmif trans -o ( -t HH:MM [-g <LVG>] | -v <LV>[,<LV>]* | -f <HOST>:<file> ) 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.

  • Page 567

    Appendix Example of an output when no transfer-out is active AZUR-VLP0# plmif query -g pos LV-Group PVGroup1 BASE TR-LVG 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. LV EXIM02 scheduled for transfer.

  • Page 568: Removing Pvs And Lvs, Adding A Pv To The Transfer-in

    Transferring volumes Example of an output after termination of the transfer-out AZUR-VLP0# plmif query -g pos LV-Group PVGroup1 2 BASE 5 TR-LVG 6 ksp 12.3.5.2 Removing PVs and LVs plmif trans -o -G This command is used to remove all PVs of the group TR-PVG which have the status 'read' from the PLM-DB, and also all LVs which have been transferred to these PVs.

  • Page 569

    Appendix 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 Options...

  • Page 570: Removing An Lv From A Transfer List, Skipping An Lv / Removing A Pv

    Transferring volumes 12.3.5.4 Removing an LV from a transfer list plmif trans -o -c [ -v <LV> ] 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.

  • Page 571: Library Commands, Adic Library With Das Server, Storagetek Library With Acsls Server

    Appendix 12.3.7 Library commands 12.3.7.1 ADIC library with DAS server ejects cartridges from the AML [via the eject area] inserts [normal data] cartridges [via the insert area] in the AML Further information is provided in the DAS manual. 12.3.7.2 StorageTek Library with ACSLS server Eject volumes [of a cartridge pool] from the library Make manual mode CAP ready to...

  • Page 572: Licenses, Xpdf, Gzip

    Licenses 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.

  • Page 573

    Appendix Also, for each author's protection and ours, we want to make certain that everyone under- stands 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' reputati- ons.

  • Page 574

    Licenses b) You must cause any work that you distribute or publish, that in whole or in part con- tains 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. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a...

  • Page 575

    Appendix The source code for a work means the preferred form of the work for making modifica- tions 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 It is not the purpose of this section to induce you to infringe any patents or other pro- perty right claims or to contest validity of any such claims; this section has the sole pur- pose of protecting the integrity of the free software distribution system, which is imple- mented by public license practices.

  • Page 577: Appendix: How To Apply These Terms To Your New Programs

    Appendix PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRI- TING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MO- DIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIAB- LE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO...

  • Page 578

    Licenses If the program is interactive, make it output a short notice like this when it starts in an inter- active 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;...

  • Page 579: Firebird

    Appendix 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 avai- lable to a third party. 1.1. “Contributor” means each entity that creates or contributes to the creation of Mo- difications.

  • Page 580

    Licenses 1.10.1. “Patent Claims” means any patent claim(s), now owned or hereafter acquired, in- cluding without limitation, method, process, and apparatus claims, in any patent Li- censable by grantor. 1.11. “Source Code” means the preferred form of the Covered Code for making modifi- cations to it, including all modules it contains, plus any associated interface defini- tion files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another...

  • Page 581

    Appendix 2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, nonexclusive license under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an un- modified basis, with other Modifications, as Covered Code and/or as part of a Lar- ger Work;...

  • Page 582

    Licenses 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.

  • Page 583

    Appendix 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.

  • Page 584

    Licenses 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;...

  • Page 585

    Appendix 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 Soft- ware Corporation can modify the terms applicable to Covered Code. 2.

  • Page 586

    Licenses 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: 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.2 of this License shall, upon 60 days notice from Participant terminate prospectively,...

  • Page 587

    Appendix 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 DAMA- GES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. U.S. GOVERNMENT END USERS. The Covered Code is a “commercial item,”...

  • Page 588

    Licenses EXHIBIT A - InterBase Public License. ``The contents of this file are subject to the Interbase Public License Version 1.0 (the “Li- cense”); 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”...

  • Page 589: Sendmail

    Appendix 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 electro- nic 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: Licence For Libxslt Except Libexslt

    Licenses (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: Licence For Libexslt

    Appendix IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWI- SE, 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 adverti- sing or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from him.

  • Page 592

    Licenses THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EX- PRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MER- CHANTABILITY, 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 OTHERWI- SE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

  • Page 593

    Appendix The following individuals contributed in part to the Network Time Protocol Distribution Ver- sion 4 and are acknowledged as authors of this work. 1. [1]Mark Andrews <mark_andrews@isc.org> Leitch atomic clock controller 2. [2]Bernd Altmeier <altmeier@atlsoft.de> hopf Elektronik serial line and PCI-bus de- vices 3.

  • Page 594

    Licenses 29. [32]Louis A. Mamakos <louie@ni.umd.edu> MD5-based authentication 30. [33]Lars H. Mathiesen <thorinn@diku.dk> adaptation of foundation code for Version 3 as specified in RFC-1305 31. [34]Danny Mayer <mayer@ntp.org>Network I/O, Windows Port, Code Maintenance 32. [35]David L. Mills <mills@udel.edu> Version 4 foundation: clock discipline, authentica- tion, precision kernel;...

  • Page 595

    Appendix 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. mailto:%20jbj@chatham.usdesign.com 23. mailto:Hans.Lambermont@nl.origin-it.com 24. mailto:H.Lambermont@chello.nl 25. mailto:%20phk@FreeBSD.ORG 26. http://www4.informatik.uni-erlangen.de/%7ekardel 27. mailto:%20kardel(at)ntp(dot)org 28. mailto:%20jones@hermes.chpc.utexas.edu 29.

  • Page 596: Tcpd, Prngd

    Licenses 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. * This material was originally written and compiled by Wietse Venema at * Eindhoven University of Technology, The Netherlands, in 1990, 1991, * 1992, 1993, 1994 and 1995.

  • Page 597: Openssh

    Appendix 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 sum- marize and say that all components are under a BSD licence, or a licence more free than that.

  • Page 598

    Licenses The legal status of this program is some combination of all these permissions and rest- rictions. Use only at your own responsibility. You will be responsible for any legal con- sequences yourself; I am not making any claims whether possessing or using this is le- gal or not in your country, and I am not taking any responsibility on your behalf.

  • Page 599

    Appendix * Ariel Futoransky <futo@core-sdi.com> * <http://www.core-sdi.com> 3. ssh-keyscan was contributed by David Mazieres under a BSD-style license. * Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>. * 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.

  • Page 600

    Licenses * 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 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.

  • Page 602

    Licenses c) Compatibility code (openbsd-compat) Apart from the previously mentioned licenses, various pieces of code in the open- bsd-compat/ subdirectory are licensed as follows: Some code is licensed under a 3-term BSD license, to the following copyright hol- ders: Todd C. Miller Theo de Raadt Damien Miller Eric P.

  • Page 603

    Appendix * 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.

  • Page 604: Openssl

    Licenses 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 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;...

  • Page 606

    Licenses * 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.com)"...

  • Page 607

    Appendix 12.4.10 tcl Copyright: This software is copyrighted by the Regents of the University of California, Sun Microsys- tems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files as- sociated with the software unless explicitly disclaimed in individual files. The authors hereby grant permission to use, copy, modify, distribute, and license this soft- ware and its documentation for any purpose, provided that existing copyright notices are re- tained in all copies and that this notice is included verbatim in any distributions.

  • Page 608: U41117-j-z125-7-76

    Licenses 12.4.11 tk Copyright: This software is copyrighted by the Regents of the University of California, Sun Microsys- tems, Inc., and other parties. The following terms apply to all files associated with the soft- ware unless explicitly disclaimed in individual files. The authors hereby grant permission to use, copy, modify, distribute, and license this soft- ware and its documentation for any purpose, provided that existing copyright notices are re- tained in all copies and that this notice is included verbatim in any distributions.

  • Page 609: Glossary

    Glossary AutoVLP failover function As the VLP Master 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 except for the monitoring function. The AutoVLP failover function checks the functional integrity of the intervals and, when it detects a malfunction, automatically takes the requisite steps: the current...

  • Page 610

    Glossary Distribute and Activate ➟ Distributed Tape Volume File System ➟ The Distribute and Activate (DNA) function must be invoked in 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

    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) –...

  • Page 612

    Glossary Header At the start of each physical tape written by CentricStor there is an 80-byte header followed by a Tapemark. 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.

  • Page 613

    Figure 39: CentricStor configuration with 5 ISPs (2 ICPs, 2 IDPs and one VLP IUP ➟ ICP_IDP A logical drive is a virtual, non-physical drive. In CentricStor up to 64 logical drives can be operated per ICP. Logical Drive ➟ Logical Volume ➟...

  • Page 614

    Glossary Message Manager ➟ MSGMGR Exists once in CentricStor. Filters and saves the ISPs’ system messages and imple- ments 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.

  • Page 615

    Redundant Array of Independent Disks ➟ 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). This is done for the following reasons: –...

  • Page 616

    Glossary System Administrator Edition ➟ Tape File System ➟ Tapemark A tapemark identifies the end of a header or logical volume (LV) on a physical tape. Tape Volume Cache ➟ 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.

  • Page 617

    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. The tape archives emulated in CentricStor are referred to as Virtual Library Services (VLS).

  • Page 618

    Glossary VTC is both an consists of precisely one Like an ICP_IDP 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

    Figures Figure 1: Conventional host robot system ........23 Figure 2: Host robot system with CentricStor .

  • 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 .

  • Page 621

    Abbreviations Abbreviation 3490E 3490F 3590 3590E 3592 9490 9840 9940 ABBA/x ACSLS AML/x ASR&R U41117-J-Z125-7-76 Long form Explanation 36-Track Drive from IBM 36-Track Drive from IBM = Berino, successor of 3490E 128-Track Drive from IBM = Magstar, = SNI 3591 256-Track Drive from IBM = successor of Magstar 512-Track Drive (=Jagu- Successor to the 3590 drive family...

  • Page 622

    Abbreviations Abbreviation DASD DLDSW0 DTVFS ESCD ESCON FCAL FICON Long form Explanation Comma Separated Values Console Switch Control, Target, LUN Relates to SCSI device Control Unit Distributed AML Server Interface to control AML Robots (Open Systems) Direct Access Storage In CS system usually the TVC Device Dual-Labeled, Dual- Sided, Write Once...

  • Page 623

    Abbreviation GXCC GXTCC HACC U41117-J-Z125-7-76 Long form Explanation Firmware Global Extended User interface for CentricStor including admi- Control Center nistration, service and monitoring in CentricStor V3.x Global Extended Tape User interface for CentricStor including admi- Control Center nistration, service and monitoring in Cen- tricStor V2.x Host Access Hard Disk Drive...

  • Page 624

    Abbreviations Abbreviation MSGMGR PERFLOG Long form Explanation Master Control Process Mount Daemon Management Information Base Media Information Message for a defective cartridge, only 3590- Message x/3592 Magnetbandkassette Magnetic tape cartridge (German) Multi Mode Message Manager One instance in CentricStor. Filters and stores the system messages of the ISPs and beforehand takes defined measures (e.g.

  • Page 625

    Abbreviation RAID ROBAR RPLM SCSI SNMP SPCC SVLP U41117-J-Z125-7-76 Long form Explanation Redundant Array of Independent (Inexpensive) Disks Remote Monitoring and CentricStor expansion for which a license is Administration required Robot Archive ROBAR-SW allows BS2000 to talk to an AML/x tape roboter Recovery PLM System Administrator SAE enables CentricStor to be operated from...

  • Page 626

    Abbreviations Abbreviation VACS VAMU VDAS VDRV VJUK VOLSER VT_LS XTCC Long form Explanation Tape Volume Cache File system on RAID system(s) which con- tain(s) the LVs in the form of files. The ISPs access different LVs at the same time. Unix File System Uninterruptable Power Supply...

  • Page 627: Related Publications

    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. SINIX-2000 V8.0/V8.1/V8.5 Installation, Operation and Administration User Guide Target group The manual is intended for privileged users (operators, system administrators) of the service/console processor 3970-2x, the channel adapters 3970 and 3971, the business server SR2000-C, and the enterprise data server DS2000.

  • Page 628

    Related publications 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

    Index 3490 emulation function menu global functions object information Show Error Log Show Error/Transfer Statistics Show Path Trace Show Short Trace 3595-RMT Absolute Min. Account Daemon ACCOUNTD functions object information accounting Accounting Data accounting license 229, accounting mails setup ACSLS ACSLS server Logical Volumes Physical Volume(s)

  • Page 630

    Index Balloon Help Balloon Help Summary Emulations Physical Devices Physical Library Processes Virtual Library Processes BASE logical volume group physical volume group basic hardware block diagram GXCC XTCC block size button bar CA Unicenter cache file system 70, cache management Cache Mirroring Feature 31, cache residence Call Home...

  • Page 631

    DAS server data PVG show show all Delete snapshots diagnostic data directory Dirty Limit disaster recovery Down/Up Sequence drives block sizes cleaning Dual Save 50, Dual Save Dirty Limit e-mail support EMTAPE emulations Global Status English Help GXCC XTCC Erase Logical Volumes Physical Volume(s) error messages...

  • Page 632

    Index flashing display activation on the module free pool fscCentricStor Fujitsu Library Fujitsu robot function bar file viewer Global Status GXCC XTCC functions ACCOUNTD archive systems (SCSI) German German Help Options XTCC Get Remote / Expand Local File GXCC XTCC get_log protocol 305, Global History Viewer Global Status...

  • Page 633

    hard disk status information Hard Min. hardware architecture hardware components 26, Hardware Summary Help file viewer GXCC XTCC Help Desk Highlight file viewer Highlight Down / Up file viewer history Print history data host connections depiction Host-Select menu HP-UX IBM-Cashion icon definition information...

  • Page 634

    Index tcpd Xpdf Link Down/Up Sequence Link/Unlink Volume Groups LMF server (PLP) Logical Drives control component see also Virtual Drives Show Logical Volume Group(s) configuration Show Logical Volume(s) Erase Show (PLM View) Show (VLM View) loss of connection recovery LRU procedure Management Station Manual Online...

  • Page 635

    VTD emulation object-specific functions XTCC Observe mode Open (Text)/Open (Hex) file viewer openssh openssl operating data optional functions Options GXCC XTCC Options Settings GXCC XTCC partitioning partitioning on the basis of volume groups password query additional passwords GXCC control component function menu information PERFLOG...

  • Page 636

    Index RAID controller functions GXCC information RAID controller (internal) status information RAID controllers internal RAID Filesystems configuration RAID system monitoring process RAID systems depiction function menu information Show Mode Page Details read tape read_log protocol 305, Readme GXCC XTCC record analog operating data recovery recycling...

  • Page 637

    Show Balloon Help Summary Cache Status Complete RAID Status Configuration Data CS Configuration Current Aspect GXCC Details (ISP) Dump (prkdump) Error Log 3490 emulation Error/Transfer Statistics 3490 emulation Jobs of Logical Volume Groups Logical Drives Logical Volume Group(s) Logical Volumes 203, Logical Volumes (physical view) Logical Volumes (PLM View) Logical Volumes (VLM View)

  • Page 638

    Index GXCC via XVision Observe mode problems User mode XTCC start parameters starting GXCC console starting from X server GXCC status information GXCC Stop Autoscan GXCC Autoscan XTCC StorageTek Library StorageTek systems streamer status information subsequent installation individual keys SVLP 27, switch on CentricStor synchronization SysObjID 550,...

  • Page 639

    virtual drive error conditions indicated on display function menu information information and error messages representation in Global Status Monitor SCSI sense Show Medium Info (MIM) Show Service Info (SIM) SIM/MIM error messages virtual drives display object information/error messages virtual SCSI drive see VTD VJUK control component...

  • Page 640

    Index Options Options Settings Print profile Readme Show Remote File start status bar title bar Toggle Aspect Toggle Size Tools Unit XUS Message Update/Revert Tool XVision setting U41117-J-Z125-7-76...

Comments to this Manuals

Symbols: 0

Latest comments:

×

Select the desired size and copy embed code

Copy your embed code and put on your site: