Integration Guide CentricStor VT V3.1D

Transcription

CentricStor VT V3.1D
Integration Guide
Integration of the CentricStor into the Storage Infrastructure
Edition 2009-02-27
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:
[email protected]
Certified documentation
according to DIN EN ISO 9001:2000
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system which
complies with the requirements of the standard
DIN EN ISO 9001:2000.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © Fujitsu Siemens Computers GmbH 2009.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
This manual is printed
on paper treated with
chlorine-free bleach.
Contents
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1
Notational conventions
1.2
Content and target group of this manual . . . . . . . . . . . . . . . . . . . . . . . 17
1.3
Concept of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4
Preparatory considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5
Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2
Summary of permitted configurations . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1
CentricStor configurations with BS2000 . . . . . . . . . . . . . . . . . . . . . . . 23
2.2
CentricStor configurations with MVS/ESA . . . . . . . . . . . . . . . . . . . . . . 23
2.3
CentricStor configurations in the SAN environment . . . . . . . . . . . . . . . . . 24
2.4
Maximum block lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.5
Restrictions on the host system side . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.6
Restrictions from the application program side . . . . . . . . . . . . . . . . . . . 27
2.7
Restrictions for server farms using Open Systems . . . . . . . . . . . . . . . . . 27
2.8
General information on the open world . . . . . . . . . . . . . . . . . . . . . . . . 28
3
CentricStor in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
Miscellaneous . . . . . . . . . . . . . .
Asynchronous tape processing with SYNC
Configuration of logical drives in BS2000 .
Activities in UGEN . . . . . . . . . . . . .
Activities in MAREN . . . . . . . . . . . .
Further preparatory activities in MAREN .
CentricStor VT V3.1D 2009-02-27
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
29
29
30
30
32
35
Contents
3.1.6
3.1.7
3.1.8
3.1.8.1
3.1.8.2
3.1.9
3.1.10
Activities in NDM . . . . . . . . . . . . . . . . . . .
Activities in ROBAR-CL and ROBAR-SV . . . . . .
Activities in BS2000-CSC . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . .
Activities in CentricStor: EMTAPE, VAMU/VACS
Multiple CentricStor systems . . . . . . . . . . . .
DAS . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
37
38
40
40
42
43
43
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.4.1
3.2.4.2
3.2.4.3
3.2.5
3.2.6
3.2.7
SX servers . . . . . . . . . . . . . . . . . . . . . . . .
Connection via FC switch . . . . . . . . . . . . . . . . .
Connection without an FC switch . . . . . . . . . . . . .
Configuring the tape units in CentricStor . . . . . . . . .
Configuring the tape devices on the SX server . . . . . .
Introductory note on X2000 . . . . . . . . . . . . . .
Configuration steps . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic documentation for the tape emulation in X2000
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
44
44
44
44
46
46
46
47
57
59
59
3.3
3.3.1
3.3.2
3.3.3
CentricStor on S servers . .
Firmware/software statuses .
Connection and configuration
Restrictions . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
60
60
61
62
4
CentricStor on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2
Subjects Covered
4.3
4.3.1
4.3.1.1
4.3.1.2
4.3.2
4.3.3
4.3.4
4.3.5
Configuration of Logical Drives in z/OS . .
Example Configuration . . . . . . . . . . . .
Direct Connection . . . . . . . . . . . . .
Switched Connection . . . . . . . . . . .
Virtual Drive Sharing . . . . . . . . . . . . . .
Representation of Virtual Drives in CentricStor
Logical Volume Definition . . . . . . . . . . .
VACS Interface . . . . . . . . . . . . . . . . .
4.4
4.4.1
4.4.2
Host Software Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Allocation Influencing and Scratch Subpooling . . . . . . . . . . . . . . . . . . . . . 71
Message Processing and Automation . . . . . . . . . . . . . . . . . . . . . . . . . . 72
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
64
65
65
66
67
67
68
69
Contents
4.5
4.5.1
4.5.1.1
4.5.1.2
4.5.1.3
4.5.1.4
4.5.1.5
4.5.1.6
4.5.1.7
4.5.2
4.5.2.1
4.5.2.2
4.5.2.3
4.5.2.4
4.5.3
4.5.3.1
4.5.3.2
4.5.3.3
4.5.3.4
4.5.3.5
4.5.3.6
Host Software Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NCS/CSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and Customisation . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Drives Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scratch Subpooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scratch Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CentricStor NCS/CSC network attachment via firewall in a z/OS environment
CSC Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSMVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample configuration for CentricStor, LMS/CSMVS with FS5193 gateway . .
LOAD balancing with LMS/CSMVS . . . . . . . . . . . . . . . . . . . . . .
Scratch alignment between RMM/CA-1 and CentricStor for LMS/CSMVS . .
Setting manual scratch for CentricStor from the host . . . . . . . . . . . . .
HACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and Customisation . . . . . . . . . . . . . . . . . . . . . . . . .
HACPARM1 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HACC ARCHIVE initialisation . . . . . . . . . . . . . . . . . . . . . . . . .
HACC Scratch Synchronisation Process . . . . . . . . . . . . . . . . . . .
HACC Volume Initialisation . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
. 73
. 73
. 74
. 79
. 85
. 89
. 92
. 94
. 95
. 96
100
101
101
102
102
103
105
116
125
125
4.6
4.6.1
4.6.1.1
4.6.1.2
4.6.1.3
4.6.2
4.6.2.1
4.6.2.2
4.6.2.3
4.6.3
4.6.3.1
4.6.3.2
4.6.3.3
Tape Management Software . . . . . . . . . . . . . . . .
DFSMSrmm considerations . . . . . . . . . . . . . . . . .
Scratch Synchronisation for RMM . . . . . . . . . . . .
Scratch Subpooling with RMM . . . . . . . . . . . . . .
Volume Definition and Initialisation with RMM . . . . . .
CA1 and TLMS considerations . . . . . . . . . . . . . . .
Scratch Synchronisation for CA1 and TLMS . . . . . .
Scratch Subpooling with CA1 and TLMS . . . . . . . .
Volume Definition and Initialisation with CA1 and TLMS
Control-T considerations . . . . . . . . . . . . . . . . . . .
Scratch Synchronisation for Control-T . . . . . . . . . .
Scratch Subpooling with Control-T . . . . . . . . . . .
Volume Definition and Initialisation with Control-T . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
126
126
126
126
139
140
140
140
141
142
142
142
145
4.7
Host Software Component - HSC . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4.8
Library Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4.9
User Exits and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
5
CentricStor on UNIX-type systems . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.1
5.1.1
5.1.1.1
5.1.1.2
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
5.1.3
5.1.4
5.1.5
Linux . . . . . . . . . . . . . . . . . . . . . .
EMULEX LP8000 controller . . . . . . . . . . .
Linux RedHat (not officially released) . . . .
SuSE Linux . . . . . . . . . . . . . . . . .
Qlogic QLA2200F Controller . . . . . . . . . . .
Linux RedHat 6.2 . . . . . . . . . . . . . .
SuSE Linux 7.1 · . . . . . . . . . . . . . . .
SuSE Linux 8.0 Professional . . . . . . . .
ST Linux SCSI tape driver . . . . . . . . . . . .
Uniquely assigned device node to LUN in Linux .
Building the kernel . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
151
151
151
152
152
152
152
153
157
158
160
5.2
5.2.1
5.2.1.1
5.2.1.2
5.2.2
5.2.2.1
5.2.2.2
Reliant UNIX . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . .
Versions of Reliant UNIX . . . . . . . .
FCdriver for EMULEX LP8000 . . . . . .
Device configuration . . . . . . . . . . . . .
Compressed WWNs in the device nodes
Logical drives in the autoconf -l . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
161
161
161
161
162
162
163
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
5.3.11
5.3.12
5.3.13
5.3.14
5.3.15
5.3.15.1
5.3.15.2
5.3.15.3
5.3.15.4
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . .
Useful commands and URLs . . . . . . . . . . . . . . .
Important settings and information . . . . . . . . . . . .
Driver for EMULEX LP8000 . . . . . . . . . . . . . . . .
Installation and configuration of QLA2310F SUN . . . . .
Tape driver st . . . . . . . . . . . . . . . . . . . . . . .
Device nodes . . . . . . . . . . . . . . . . . . . . . . .
Persistent Binding . . . . . . . . . . . . . . . . . . . . .
Checking the configuration . . . . . . . . . . . . . . . .
Solaris systems in server farms . . . . . . . . . . . . . .
Contents of the file lpfc.conf for Solaris . . . . . . . . . .
Contents of the file st.conf for Solaris . . . . . . . . . . .
Extensions for Data Protector and SolarisTivoli . . . . . .
Extensions for NetBackup . . . . . . . . . . . . . . . . .
Sun StorEdge SAN Foundation Software (SFS/Leadville)
General . . . . . . . . . . . . . . . . . . . . . . . .
Example of migration from lpfc to SFS/Leadville . . .
Useful commands . . . . . . . . . . . . . . . . . . .
Familiar problems . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
165
165
165
166
167
168
169
170
172
173
174
174
180
184
184
185
185
187
197
200
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
HP-UX . . . . . .
General . . . . .
Restrictions . . .
Useful commands:
Links . . . . . . .
Device nodes . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
200
200
200
200
201
201
5.5
5.5.1
5.5.2
5.5.3
5.5.4
5.5.5
5.5.6
5.5.7
IBM-AIX . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . .
Important settings and information
Useful commands . . . . . . . . .
Configuration of the drives . . . . .
Device nodes . . . . . . . . . . .
Testing the tape drives with tapeutil
Problems with AIX . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
202
202
202
203
204
206
207
208
6
CentricStor in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
6.1
6.1.1
6.1.2
NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6.2
6.2.1
6.2.2
Windows 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . 212
7
CentricStor on NAS systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
7.1
General information on saving using NDMP . . . . . . . . . . . . . . . . . . . . 213
7.2
7.2.1
7.2.2
7.2.3
7.2.3.1
7.2.3.2
7.2.4
NetApp . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . .
Configuration in CentricStor . . . . . . . . . . . . .
Configuration of the backup application (NetWorker)
Useful commands . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
213
213
213
214
214
214
214
Contents
7.3
7.3.1
7.3.2
7.3.3
7.3.3.1
7.3.3.2
7.3.3.3
7.3.4
Celerra . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . .
Configuration in CentricStor . . . . . . . . . . . . .
Configuration of Celerra . . . . . . . . . . . . . . .
Useful commands, to be executed on the control node .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8
Tape management systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.1.4.1
8.1.4.2
8.1.4.3
8.1.4.4
8.1.5
8.1.6
8.1.7
8.1.8
8.1.8.1
8.1.8.2
8.1.8.3
8.1.8.4
8.1.8.5
8.1.8.6
8.1.8.7
NetWorker (Legato/EMC and FSC) . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . .
NetWorker versions . . . . . . . . . . . . . . . . . . . . . .
Configuration of the “CentricStor” library . . . . . . . . . . .
Configuration of virtual devices (NetWorker resource devices)
ACSLS interface . . . . . . . . . . . . . . . . . . . . . .
DAS interface . . . . . . . . . . . . . . . . . . . . . . .
Fast mount support . . . . . . . . . . . . . . . . . . . .
Changing from NetWorker 5.5 to 6.1... . . . . . . . . . .
Configuring a jukebox in NetWorker on Solaris . . . . . . . .
Prefetch with FSC NetWorker . . . . . . . . . . . . . . . . .
Tips and tricks . . . . . . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
221
221
221
222
230
231
232
232
233
234
236
237
237
237
238
239
240
241
241
243
8.2
8.2.1
8.2.2
8.2.3
8.2.3.1
8.2.3.2
8.2.3.3
8.2.3.4
NetBackup (Veritas) . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . .
LMF configuration . . . . . . . . . . . . . . . . . . .
Connection of the robot controller (VACS) via a firewall
Template for supporting SCRATCH mount . . . . . .
Sample screens . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
244
244
244
245
246
248
249
250
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
215
215
215
216
216
216
218
219
Contents
8.2.4
8.2.4.1
8.2.4.2
8.2.4.3
8.2.4.4
8.2.4.5
8.2.4.6
8.2.4.7
8.2.4.8
System specific . .
Windows NT 4.0
Windows 2000 .
Windows 2003 .
Reliant UNIX . .
Solaris . . . . .
HP-UX . . . . .
IBM-AIX . . . .
Linux . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
257
257
258
259
259
260
261
262
262
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.3.4.1
8.3.4.2
8.3.4.3
8.3.4.4
8.3.4.5
8.3.4.6
8.3.4.7
8.3.4.8
8.3.5
8.3.6
8.3.6.1
8.3.6.2
8.3.6.3
8.3.6.4
8.3.6.5
8.3.6.6
8.3.7
8.3.7.1
8.3.7.2
8.3.7.3
8.3.7.4
8.3.8
8.3.8.1
8.3.8.2
8.3.8.3
8.3.8.4
8.3.8.5
8.3.8.6
8.3.8.7
Data Protector . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . .
Licenses . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . .
Installation in UNIX systems . . . . . . . . . . . . . .
Installation of Data Protector . . . . . . . . . . .
Configuration of CentricStor in Data Protector . .
Template for SCRATCH mount support . . . . . .
Template for PREFETCH support . . . . . . . . .
Bypassing lengthy backup times in Data Protector
Configuration as StorageTek ACS library . . . . .
Configuration as a GRAU-DAS library . . . . . . .
Setup of volumes . . . . . . . . . . . . . . . . .
Installation example for Windows NT . . . . . . . . .
VJUK configuration . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . .
Configuration of the robots under AIX . . . . . . .
Configuration of the robots under HP-UX . . . . .
Configuration of the robots under Solaris . . . . .
Configuration of the robot devices under Windows
Configuration of a library under Solaris . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . .
Virtual drives . . . . . . . . . . . . . . . . . . . .
DAS interface . . . . . . . . . . . . . . . . . . .
ACS interface . . . . . . . . . . . . . . . . . . .
Autolabeling . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
263
263
263
263
264
264
264
265
266
266
273
276
279
282
288
288
288
288
288
289
289
296
296
297
298
298
298
298
299
300
301
301
302
302
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
8.4
8.4.1
8.4.2
8.4.2.1
8.4.2.2
8.4.2.3
8.4.2.4
8.4.3
8.4.3.1
8.4.3.2
8.4.3.3
8.4.3.4
8.4.3.5
8.4.4
8.4.4.1
8.4.4.2
8.4.4.3
8.4.5
8.4.5.1
8.4.5.2
8.4.5.3
8.4.5.4
8.4.5.5
8.4.5.6
8.4.6
8.4.7
8.4.7.1
8.4.7.2
8.4.7.3
8.4.7.4
8.4.7.5
8.4.7.6
8.4.7.7
Tivoli / TSM . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration . . . . . . . . . . . . . .
TSM installation . . . . . . . . . . . . . . . . . . .
TSM configuration . . . . . . . . . . . . . . . . . .
Special parameters . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration with Gresham EDT . . . .
Gresham installation . . . . . . . . . . . . . . . . .
TSM installation . . . . . . . . . . . . . . . . . . .
Gresham configuration . . . . . . . . . . . . . . .
TSM configuration . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . .
Configuring a SCSI library on AIX via VJUK . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . .
Configuration steps . . . . . . . . . . . . . . . . .
Modifying the VJUK configuration and notifying TSM
LANfree configuration without Gresham . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . .
Verification of LANfree data transfer . . . . . . . . .
General information . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . .
Miscellaneous and restrictions . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
303
303
303
303
304
306
306
307
307
308
308
310
311
312
312
313
316
317
317
317
318
322
323
323
323
324
324
324
324
324
325
325
325
8.5
8.5.1
8.5.2
8.5.3
8.5.4
BrightStor ARCserve Backup
ARCserve . . . . . . . . . . .
CentricStor . . . . . . . . . . .
Backup server . . . . . . . . .
Further information . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
326
326
326
328
330
8.6
8.6.1
8.6.2
Time Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
8.7
8.7.1
VJUK emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
8.8
NAS filer - NetApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
8.9
8.9.1
8.9.1.1
8.9.1.2
8.9.1.3
8.9.1.4
8.9.1.5
8.9.2
8.9.3
8.9.3.1
8.9.3.2
8.9.4
DiskXtender for Windows . . . . . .
Configuration in CentricStor . . . . . .
Virtual Library Services . . . . . .
Logical Drives . . . . . . . . . . .
Logical Volume Groups . . . . . .
Add Logical Volumes . . . . . . .
Mixed Media Info . . . . . . . . .
Installing DiskXtender for Windows . .
DiskXtender for Windows configuration
Ascertaining the name of the tapes
Configuring media services . . . .
Further information . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
341
341
341
342
343
343
343
344
344
344
345
346
8.10
8.10.1
8.10.2
8.10.3
8.10.3.1
8.10.3.2
8.10.3.3
CommVault Galaxy . . . . . . . . . .
Documentation . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . .
Configuration of the ACSLS library
Configuration of the drives . . . . .
Configuration of the mount timeout
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
347
347
347
348
348
352
359
9
Useful commands and information . . . . . . . . . . . . . . . . . . . . . . . . . 361
9.1
Logging, configuration tools, traces in UNIX systems
9.2
Display of CentricStor configuration data for the service engineer
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.3.6
CentricStor configuration data displays for the user
IP addresses and host names . . . . . . . . . . . . . .
Emulations . . . . . . . . . . . . . . . . . . . . . . . .
Virtual libraries . . . . . . . . . . . . . . . . . . . . . .
Real devices (PDS) . . . . . . . . . . . . . . . . . . .
Real libraries (PLS) . . . . . . . . . . . . . . . . . . .
WWNN and WWPN of the FC connections . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
362
362
362
363
363
363
363
9.4
9.4.1
9.4.2
9.4.3
Control of ADIC / ABBA / AML libraries .
DASADMIN . . . . . . . . . . . . . . . .
Communication between client and server
Possible problems and solutions . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
364
364
366
367
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . 361
. . . . . . . 361
Contents
9.5
9.5.1
9.5.2
9.5.3
9.5.4
9.5.5
9.5.6
9.5.7
9.5.8
9.5.9
Control of the StorageTek libraries . . . . .
Powderhorn to extend drives . . . . . . . . .
Cleaning management in StorageTek libraries
Adding tapes in Powderhorn . . . . . . . . . .
Adding tapes in L180 . . . . . . . . . . . . .
Starting the ssi daemon . . . . . . . . . . . .
Stopping the ssi daemon . . . . . . . . . . .
cmd_proc . . . . . . . . . . . . . . . . . . .
Communication between client and server . .
Possible problems and troubleshooting advice
9.6
Information on the Cashion connection . . . . . . . . . . . . . . . . . . . . . . 372
9.7
Information on Fujitsu libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
9.8
9.8.1
9.8.2
9.8.3
9.8.3.1
9.8.3.2
9.8.3.3
9.8.3.4
9.8.3.5
Qualified fibre channel switches in the SAN environment
Features of the FC connection . . . . . . . . . . . . . . . . .
Permitted FC switches . . . . . . . . . . . . . . . . . . . . .
Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zoning example (6 hosts on 3 ICPs) . . . . . . . . . . .
Configuration example . . . . . . . . . . . . . . . . . . .
Configuration of the brocade switch via Internet Explorer .
Diagnostics in the event of performance problems . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
373
373
374
374
374
375
376
378
383
9.9
9.9.1
9.9.2
9.9.2.1
9.9.2.2
9.9.3
9.9.3.1
9.9.3.2
Host bus adapters (HBA) . . . .
Overview of the host bus adapters
Firmware download . . . . . . . .
LP8000 . . . . . . . . . . . .
QLA2200F . . . . . . . . . . .
BIOS settings . . . . . . . . . . .
LP8000 . . . . . . . . . . . .
QLA2200F . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
384
384
385
385
385
385
385
385
9.10
9.10.1
9.10.2
9.10.3
9.10.4
Example of a filter bridge for separating CentricStor™
General . . . . . . . . . . . . . . . . . . . . . . . . . .
Start/stop script bridge . . . . . . . . . . . . . . . . . . .
Configuration file: csbridge . . . . . . . . . . . . . . . .
Ports used by CentricStor . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
387
387
387
392
396
9.11
9.11.1
Long distance over an FCIP connection with Cisco Switch . . . . . . . . . . .
Long distance over an FCIP connection between the internal Brocade Switches of
CentricStor with CMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Cisco Switch via the graphical user interface (Fabric Manager)
9.11.1.1
9.11.1.2
9.11.1.3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
368
368
369
369
369
369
369
370
370
372
. 397
.
.
.
.
397
397
397
398
Contents
9.11.2
9.11.2.1
9.11.2.2
9.11.2.3
9.11.3
Long distance over an FCIP connection between IDP and real tape . . . . . . . . .
Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Cisco Switches via the graphical user interface (Fabric Manager)
Test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
406
406
407
407
409
9.12
9.12.1
9.12.2
9.12.3
9.12.3.1
9.12.3.2
9.12.3.3
9.12.3.4
VACS security by means of ownership . . . . . . . . .
VACS configuration parameters in GXCC . . . . . . . . .
Application example of ownership transfer for a volume . .
Ownership of a volume . . . . . . . . . . . . . . . . . .
Definition and meaning of the Userid in the ACSLS . .
Authorized Userid . . . . . . . . . . . . . . . . . . .
Special features when using the VACS security rules .
Use of the Authorized Userid by customer applications
410
410
411
412
413
413
414
416
10
Installation of the GUI software GXCC/XTCC . . . . . . . . . . . . . . . . . . . . 417
10.0.1
10.0.2
Information about the installation CD . . . . . . . . . . . . . . . . . . . . . . . . . 417
Information about restrictions and known bugs . . . . . . . . . . . . . . . . . . . . 417
10.1
10.1.1
10.1.1.1
10.1.1.2
10.1.1.3
10.1.1.4
10.1.1.5
10.1.1.6
10.1.2
10.1.2.1
10.1.2.2
10.1.2.3
10.1.3
10.1.3.1
10.1.3.2
10.1.3.3
10.1.4
10.1.4.1
10.1.4.2
10.1.4.3
Installation descriptions . . . . . . . . . . . . . . . . .
Installation on MS-Windows Platform . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . .
Installation of the GUI documentation (optional) . . .
Starting the GUI Software . . . . . . . . . . . . . . .
Creating the CA-Unicenter Extensions for CentricStor
Deinstallation of the Software . . . . . . . . . . . . .
Configuration Data . . . . . . . . . . . . . . . . . . .
Installation on a LINUX Platform . . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . .
Deinstalling the GUI Software . . . . . . . . . . . . .
Installation on a SOLARIS Platform . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . .
Deinstalling the Software . . . . . . . . . . . . . . .
Installation on a SINIX-Z Platform . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . .
Deinstalling the Software . . . . . . . . . . . . . . .
10.2
10.2.1
10.2.2
Online Documentation of the GUI Software . . . . . . . . . . . . . . . . . . . . 428
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Displaying the Documentation via the Help Function of the GUI . . . . . . . . . . . 428
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
417
418
418
419
420
421
421
421
422
422
423
423
423
423
425
425
426
426
427
427
Contents
10.3
10.3.1
10.3.1.1
10.3.1.2
10.3.1.3
10.3.1.4
10.3.2
10.3.2.1
10.3.2.2
Offline Mode . . . . . . . .
Integrating the Snapshot Files
MS-Windows Platform . .
LINUX Platform . . . . .
SOLARIS Platform . . . .
SINIX-Z Platform . . . . .
Functionality in Offline Mode
Static Display . . . . . .
Dynamic Display . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
429
430
430
430
431
432
433
433
433
10.4
10.4.1
10.4.2
10.4.3
10.4.4
10.4.5
10.4.6
Unattended Installation / Deinstallation under MS-Windows
Setup Command Line Parameters . . . . . . . . . . . . . . . .
Setup Exit Codes . . . . . . . . . . . . . . . . . . . . . . . .
Uninstaller Command Line Parameters . . . . . . . . . . . . .
Uninstaller Exit Code . . . . . . . . . . . . . . . . . . . . . .
Setup Registry Settings . . . . . . . . . . . . . . . . . . . . .
GUI Registry Settings . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
434
434
435
436
436
437
437
10.5
Restrictions and known bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
11
Important information regarding the CentricStor environment . . . . . . . . . . 439
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Environmental Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
1 Introduction
CentricStor VT can be operated on BS2000 and MVX/ESA systems via an ESCON host
adapter, and on several variants of UNIX, Linux, Windows hosts and on BS2000 (SX and S
Server) via Fibre Channel Fabric.
This introduction describes the settings for this on the hosts, on the fibre channel
connection system and on CentricStor VT.
In the following chapters of this manual CentricStor always stands for CentricStor VT.
15
Notational conventions
Introduction
1.1 Notational conventions
This manual uses the symbols and other notational conventions to draw your attention to
certain items of text. The following symbols are used:
This symbol indicates actions to be performed by the user (e.g.
keyboard input).
Ê
WARNING
!
i
The warning symbol denotes important instructions and items of information such as warnings.
This indicates information which is particularly important for the
functionality of the product.
[ ... ]
Square brackets are used to enclose cross-references to related publications, and to indicate optional parameters in command descriptions.
For names, commands and messages this typewriter font is used (e.g. the SETLOGON-PARAMETERS command).
The following examples show how to give commands on the graphical user interface of
CentricStor:
Example 1:
[GXCC - Function bar: Tools ➟ Global Status]; Global status function bar ➟ Tools ➟ Show
Balloon Help Summary
Ê
On the function bar in GXCC, open the drop-down menu Tools and choose the
function Global Status. This part is enclosed in square brackets [..] to indicate that
the Global Status Window can also be permanently open.
Ê
If the global status window is open, open the drop-down menu Tools from the
function bar, and select the Function Show Balloon Help Summary.
Example 2:
[GXCC object function ➟ VLP ➟ Show Details or Maintenance]; XTCC object function ➟
VLM ➟ Show logical Drives
16
Ê
In GXCC, select the VLP icon, choose the function Show Details (User/Observe
Mode) or Maintenance (Service Mode). This part is enclosed in square brackets
[..] to indicate that the XTCC Window for the VLP can also be permanently open.
Ê
If the XTCC window for the VLP is opened, open the drop-down menu of the VLP
icon and choose the function Show logical Drives.
Introduction
Content and target group of this manual
1.2 Content and target group of this manual
This manual contains information on the host connection (BS2000, MVS/ESA, Linux, UNIX,
Windows...) of CentricStor.
●
It provides information for host system administrators about the settings needed to
connect their systems (BS2000, MVS/ESA, Linux UNIX, Windows...) to CentricStor.
●
There is advice for setting up libraries which can work both as a back end with
CentricStor or directly with the host.
●
It shows the zoning of an FC switch which can be switched between the host und
CentricStor.
●
It shows CentricStor service personnel how CentricStor should be configured for
connection to each of the host systems indicated.
Only the maintenance technicians who have the CentricStor root and service passwords
can access and edit CentricStor configurations. The CentricStor configuration is described
in the maintenance manual [1]. The configuration set up in CentricStor is displayed on the
graphical interface. It can also be output from the graphical interface in various ways and
displayed as a list. The relevant details can be found in the graphical interface manuals.
1.3 Concept of the manual
This manual is a supplement to the user and maintenance manual. The installation instructions are divided as follows:
1. General operating procedures and summary tables (system independent).
2. Connecting CentricStor to host systems, divided by system (BS2000, MVS/ESA, UNIXtype systems, and Windows).
3. Tape management systems (NetWorker,..Tivoli), divided by management system. Each
section contains an appendix detailing the operating-system specific features.
4. Practical instructions such as:
– Useful commands for UNIX systems.
– Instructions on accessing CentricStor configuration data
– Using libraries
– Setting FC switches
– Host Bus Adapter
– Configuration example for CentricStor (adding an ICP)
17
Preparatory considerations
Introduction
1.4 Preparatory considerations
The figure below shows which host components handle the various items of configuration
data in the CentricStor (CS).
The procedure to be followed depends on the system. Lines written in red apply to Open
Systems and BS2000 on FC (SX and S Server), lines written in blue apply to MVS/ESA and
BS2000/OSD.
18
Introduction
Host system
e.g. Solaris, AIX
Management system
e.g. NetWorker, Tivoli
Settings in the management system
selection of an appropriate emulation in CS (from page 221)
Host adapter
Is the FC-HBA permitted on your host for CS (page 384)? Check
the version of the firmware and the BIOS settings (page 385) and
correct where necessary.
Library client
What are the data (IP address, port number) for the library client?
To which virtual drives and virtual volumes should it have access?
Enter values in the CS configuration.
Virtual driver/
Device nodes
Real libraries
Switch/Director
Check the version of the driver for the FC adapter.
Set your system so that the necessary device nodes are created.
(from page 151).
Add the CS drives to the BS2000 or MVS configuration files.
Should real libraries present in CS also be used as native?
Do you want the real drives to be cleaned by CS?
Set fibre channel zoning (page 374)
Set ESCON director (BS2000 and z/OS, page 29 ff, page 63)
CentricStor
Virtual devices
Set device emulations (device type, library address, library type,
corresponding configuration desired for the host)
Virtual libraries
Set up library emulation, set client access rights.
Real devices
Link real devices with library, set up cleaning management
Library
Library
Real devices
Start CentricStor as a client in a real library.
Set up cleaning management in a library. Where necessary,
partition real libraries (examples from page 364).
19
Introduction
The following tests and settings should be made before the starting configuration work.
●
CentricStor can emulate various tape cartridge drives. This manual indicates which
drive types can be used with your system, and provides instructions on how to create
device nodes with the necessary properties.
We recommend that you use the emulations given in these instructions. FujitsuSiemens has carried out extensive testing precisely for this configuration.
●
Individual management systems (e.g. NetWorker, Tivoli,...) only support particular
types of library and drive. Before you start, you should note which library your tape
management system can operate and then configure CentricStor accordingly. In order
to ensure trouble-free operation, the configuration in CentricStor must match the host
configuration exactly.
●
Cases where several hosts are to be connected to CentricStor. In these cases you
should first establish if and how virtual volumes and drives will be separated from each
other in the emulated libraries, and then set the emulations accordingly.
●
Set the number and allocation of the virtual drives.
You should take steps to ensure that any virtual drive in an open system is connected
precisely to one FC adapter only.
!
●
If real libraries of CentricStor and the hosts are to be used jointly, set how the drives and
storage areas are divided.
This division and the cabling of the library and the drives with CentricStor must be
completed before CentricStor is configured.
●
Establish how the cleaning of the drives is carried out. CentricStor can take over the
cleaning of the drives assigned to it, including the administration of the cleaning
cartridges. Not all libraries, however, allow the drive specific administration of cleaning.
●
This manual describes the host adapter type which has been tested with your system
on CentricStor, the firmware revisions, the drives and the BIOS settings (if any)
required. You should check compliance with these requirements and implement them
where necessary, before starting any integration work.
i
20
CAUTION:
Distribute the drives among the hosts so that no more than 2*4 drives (2 hosts
with 4 drives each) are operated simultaneously via one FC connection. If this
limit is exceeded, the performance of the fibre channel may fall dramatically.
The chapter “Useful commands and information” on page 361 shows how you can
find the current configuration data of the CentricStor on the graphical user interface.
Introduction
Note
1.5 Note
The CentricStor front end, depending on the configuration setup, can emulate several robot
systems (connected via TCP/IP LAN) and tape drives (connected via ESCON or fibre
channel). This is independent of which real robot systems and which drives are actually
connected to CentricStor (back end). Details on the emulations which can be set, and the
real devices which can be connected can be found in the data sheet of your CentricStor.
The logical volumes of CentricStor can be easily distinguished from real volumes. They do
not belong to a logical library and are not therefore assigned to any drive type. Thus they
can be mounted in practically all drive emulations configured in CentricStor; the only limitations here are those deriving from the type of backup tool (e.g. NetWorker) used. The name
of a volume must, therefore, be unique for the whole CentricStor.
In many cases, CentricStor is integrated into an existing host system with backup and tape
management system. Tape libraries may already be present, which can be linked directly
with the host, or as a back end with
CentricStor.
The following rules apply here:
Real drives
cannot be used jointly
Physical tape cartridge drives cannot be used jointly
Robots
can be used jointly if the robot controller supports this
21
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
2 Summary of permitted configurations
2.1 CentricStor configurations with BS2000
Host connection
Device emulation
Library connection
ESCON host adapter, FC (SX and S Server)
FSC3590 Emulation / IBM3490
ROBAR/AMU or CSC/ACS
2.2 CentricStor configurations with MVS/ESA
Host connection
Device emulation
Library connection
ESCON host adapter
FSC3590 emulation / IBM3490
HACC
23
CentricStor configurations in the SAN environment
Summary of permitted configurations
2.3 CentricStor configurations in the SAN environment
i
The current support matrix is for FSC Service and service partners available at the
internet address:
https://partners.fujitsu-siemens.com/teams/cpc/Support%20Matrix/CentricStor_Support_Matrix.xls
ACS robot control
NetWorker
FSC
NetWorker
Legato
NetBackup
VERITAS
TSM
IBM
Data
Protector
HP
BEX
Syncsort
Time
Navigator
ATEMPO
AIX
---
Mammoth2
3590E1A1
3590E1A
---
---
---
HP-UX
---
Mammoth2
gen. SCSI-2
gen. SCSI-2 2 gen. SCSI-2
---
---
3590E1A1
---
---
---
---
---
---
---
---
---
gen. SCSI-2
gen. SCSI-2
gen. SCSI-2 ---
Mammoth23
Mammoth2
gen. SCSI-2
---
3590E1A1
3590E1A
1
3590E1A
3590E1A
Linux
gen. SCSI-2 ---
1
Mammoth2
Reliant
gen. SCSI-2 --Mammoth2
Solaris
gen. SCSI-2 Mammoth2
Mammoth2
WIN 2K
---
WIN 2K3 ---
gen. SCSI-2
3590E1A
Mammoth2
---
3590E1A
1
Mammoth2
3590E1A
---
---
Mammoth2
3590E1A
WIN NT
---
Mammoth2
Mammoth2
3
under test
gen. SCSI-2
---
---
3590E1A1
24
1
Certified by Veritas: RedHat LINUX was used.
2
The product DistribuTape from Greham is required.
3
This has not been officially released by Veritas for NetBackup.
DAS robot control
NetWorker FSC
NetWorker
Legato
NetBackup
VERITAS
TSM
IBM
Data Protector
HP
AIX
---
---
under test
---
3590E1A
HP-UX
---
Mammoth2
generic SCSI-2
---
generic SCSI-2
Mammoth2
Linux
generic SCSI-2
Mammoth2
---
---
---
---
Reliant
generic SCSI-2
Mammoth2
---
---
---
---
Solaris
generic SCSI-2
Mammoth2
Mammoth2
generic SCSI-2
---
---
WIN 2K
---
Mammoth2
---
---
generic SCSI-2
WIN NT
---
Mammoth2
---
---
generic SCSI-2
25
SCSI jukebox robot controller (VJUK)
Application
Platform in test
Jukebox
emulation
BrightStor
ARCserve R11.1
SUSE Linux
ADIC Scalar 1000 Mammoth22
R11.11 SP1
Tape device
emulation
Maximum
volume No.
Restictions
At least 1182
Restore Multiplex
SLES8 SP3
Abortion
SLES9
Being examined
at CA
Mammoth22
Windows 2003
3590E1A
Legato Disk
Xtender UNIX
(DXUL) 2.63
Solaris 9
FSC Networker 7.1 Solaris 9
EKS 1-3
ADIC Scalar 10K
3590E1A
At least
10000
---
FSC CS-TL
gen. SCSI-2
30000
---
Legato Networker
7.1.2
Windows 2000 SP4 FSC CS-TL
Mammoth2
20014
---
Veritas NetBackup
5.0 MP 1
Windows 2003
FSC CS-TL
Mammoth2
16000
---
HP
Data Protector 4.1
Windows 2000
FSC CS-TL
gen. SCSI-2
At least 1000
---
DataProtector 5.1
Windows 2003
1500
HP-UX
TSM
AIX 4.3.3
ADIC Scalar 10K
3590E1A
16000
---5
AIX 5.2
26
1
In the test on Windows, CentricStor also showed that it can function with the predecessor version (ARCserve
R11 with device patch 5 and patch QO53978) for Windows.
2
ARCServe on Windows works in fixed block length mode.
3
DiskXtender 2000 5.60.025 was tested on Windows 2003 with tape device type IBM 3590E1A but could not be
operated because of incompatibility of the end-of-tape identification/volume capacity.
4
If there are more than approx. 2001 slots for volums+drives Networker (jbconfig) aborts with error 0x29
unknown error. An increase in the slot limit is being investigated on the Networker side.
5
In the event of hardware scanning with cfgmgr and VJUK, AIX reports cfgmgr: 0514-621 WARNING: The
following device packages are required for device support but are not currently
installed. device.fcp.changer. No functional restriction was observed.
Maximum block lengths
2.4 Maximum block lengths
Emulation
Maximum block length
FSC/generic SCSI-2
256 KB
EXABYTE/Mammoth2
240 KB
IBM/3590E1A
256 KB
The maximum block length is defined by the SCSI command read max blocksize.
2.5 Restrictions on the host system side
Windows:
Reliant:
Solaris:
HP-UX:
Can only see drives of the same type on CentricStor (page 210 and 212).
Support from V5.45B0030 or higher (page 161).
– An older LP8000 driver must be used.
– Connection of two FC controllers to the same WWPN is not permitted.
The system only supports 8 LUN for each partner WWPN.
2.6 Restrictions from the application program side
NetBackup:
Versions before V4.5 only support the first 15 DAS drives with the DAS robot
control.
TSM:
Does not currently support DAS robot interfaces.
2.7 Restrictions for server farms using Open Systems
In principle all Open System hosts should be able work with a CentricStor via a fabric.
However, given the wide variety of FC controller hardware and the large number of
operating systems involved, problems can occur. This section provides a quick guide to the
problems which may arise and suggests some solutions.
The following problems are known:
●
Solaris scans all LUNs and as a consequence sporadically disturbs the data transfers
of other systems.
Troubleshooting: see section “Solaris systems in server farms” on page 174.
27
General information on the open world
2.8 General information on the open world
As of CentricStor™ V3.0 fixed block length mode is supported in VTD emulation.
This applies for all 3 emulation types:
–
–
–
FSC generic
EXABYTE Mammoth2
IBM 3590E
As a result, BrightStor ARCserve backup can, for example, be supported on Windows. For
releases see the section “CentricStor configurations in the SAN environment” on page 24.
28
i
The variable or fixed block length mode is not configured on the CentricStor user
interface, but is defined internally by the application on the host.
!
CAUTION!
The pro-FC port resources currently suffice for 64 x 256-MB I/Os in parallel (256 MB
is the maximum variable block length). If fixed block length is used the size of
maximum block length may be increased, however only at the cost of the number of
emulations, i.e. if 2-MB fixed block I/Os are used the maximum number of emulations that can be used in parallel is 8 ( i.e. 64 * 256/2048 ).
3 CentricStor in BS2000/OSD
3.1 Miscellaneous
When CentricStor is operated in BS2000/OSD the large number of virtual drives means that
the number of mount messages can increase. To prevent message queues at the console
in unattended mode when NBLOGENF=Y is set to specify audit-standard console logging,
the system administrator must ensure that enough space is always available on the home
pubset for the CONSLOG files.
In addition, the time for buffering messages with BCAM should not be restricted with
/BCTIMES LETT=... .
Because there is no option for controlling the library in offline mode (without ROBAR/CSC),
no SLED is possible for CentricStor either on the ESCON or on the FC channel. Nor is initial
installation by FIRST or SIROS or physical backup with offline FDDRL supported.
3.1.1 Asynchronous tape processing with SYNC
In the case of asynchronous tape processing, e.g. by means of BTAM (cf. BS2000/OSD-BC
User Guide, DVS Assembler interface), the data is initially buffered in a device-specific
buffer and written to tape only when a specific buffer utilization level is reached. As a result,
in some circumstances not all data will really have been written to tape when hardware or
software faults occur. Only when the CLOSE command has been positively acknowledged
is it guaranteed that all data has been stored consistently on the volume.
As the buffer utilization level is device-specific, it cannot be assumed that the buffer content
is transferred to the tape during processing after a particular amount of data has been
exceeded. However, calling the SYNC command enables a consistent status to be ensured
section by section while asynchronous tape processing is in progress.
Basically the use of CentricStor in no way alters this fact. However, as the buffers are very
large here, it can occur that when an error occurs considerably more data has not yet been
written to tape than in real mode. Only afer CLOSE or SYNC has been acknowledged
positively does CentricStor naturally also ensure that a consistent saved status has been
achieved.
29
Miscellaneous
CentricStor in BS2000/OSD
Fujitsu Siemens Computers products such as HSMS or ARCHIVE secure asynchronous
tape processing by calling the SYNC command. This is also required in customers’ own
applications and programs.
3.1.2 Configuration of logical drives in BS2000
The configuration of virtual CentricStor drives is practically identical to the configuration of
36-track drives in ABBA or STK robots.
For the instances given below of MAREN, NDM and ROBAR or CSC you must define an
identical, freely selectable storage location with a maximum of 5 characters (e.g. CEST1).
The steps necessary for the different instances are shown in the following example:
3.1.3 Activities in UGEN
i
Each ICP is an independent control unit in BS2000 on the ESCON channel and can
thus be configured using 2 or 4 paths in the direct connection. The address area
always begins with null.
1. Create an input file for UGEN (for details, see the system installation manual [7] of the
BS2000 version you are using):
Example:
Task:
Generation with two ICPs, each with 2 ESCON controllers, where all
virtual drives are connected via ESCON using two paths. These two
paths correspond to the two ESCON channels on each ICP.
i
30
BS2000 supports configurations using a maximum of 8
paths. However, only 4 ESCON channels can be connected
to one ICP.
Miscellaneous
***********************************************************************
*
MBK
FSC 3590E / IBM 3490E
ICP0/ICP1
***********************************************************************
*
* Controller for ICP0 drives
CTL 80,BLM,A,(7A,0,I),*
CTL 81,BLM,A,(79,0,I),*
*
|
|
*
|
+-----> Channel
*
+--> Controller
*
* Controller for ICP1 drives
CTL 82,BLM,A,(3C,0,I),*
CTL 83,BLM,A,(3B,0,I),*
*
*
Definition of 16 Logical Devices on ICP0
*
*
+-----> Logical Device (mnemonic in BS2000 and ROBAR or CSC)
*
| +--> TAPE-C4 (36-track device, IBM3490 FSC 3590 )
*
| |
+-------------> Address area (begins with null)
*
| |
|
+---------> 1. Controller
*
| |
|
|
+--> 2. Controller
*
| |
|
|
|
DVC B0,C4,D,00,(80,I),(81,I),AT=CTL
DVC B3,C4,D,01,(80,I),(81,I),AT=CTL
DVC B4,C4,D,02,(80,I),(81,I),AT=CTL
DVC B5,C4,D,03,(80,I),(81,I),AT=CTL
DVC B6,C4,D,04,(80,I),(81,I),AT=CTL
DVC B7,C4,D,05,(80,I),(81,I),AT=CTL
DVC B8,C4,D,06,(80,I),(81,I),AT=CTL
DVC B9,C4,D,07,(80,I),(81,I),AT=CTL
DVC BA,C4,D,08,(80,I),(81,I),AT=CTL
DVC BB,C4,D,09,(80,I),(81,I),AT=CTL
DVC BC,C4,D,0A,(80,I),(81,I),AT=CTL
DVC BD,C4,D,0B,(80,I),(81,I),AT=CTL
DVC BE,C4,D,0C,(80,I),(81,I),AT=CTL
DVC BF,C4,D,0D,(80,I),(81,I),AT=CTL
DVC BG,C4,D,0E,(80,I),(81,I),AT=CTL
DVC BH,C4,D,0F,(80,I),(81,I),AT=CTL
*
31
Miscellaneous
*
*
Definition of 16 Logical Devices on ICP1
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
BI,C4,D,00,(82,I),(83,I),AT=CTL
BJ,C4,D,01,(82,I),(83,I),AT=CTL
BK,C4,D,02,(82,I),(83,I),AT=CTL
BL,C4,D,03,(82,I),(83,I),AT=CTL
BM,C4,D,04,(82,I),(83,I),AT=CTL
BN,C4,D,05,(82,I),(83,I),AT=CTL
BO,C4,D,06,(82,I),(83,I),AT=CTL
BP,C4,D,07,(82,I),(83,I),AT=CTL
BQ,C4,D,08,(82,I),(83,I),AT=CTL
BR,C4,D,09,(82,I),(83,I),AT=CTL
BS,C4,D,0A,(82,I),(83,I),AT=CTL
BV,C4,D,0B,(82,I),(83,I),AT=CTL
BW,C4,D,0C,(82,I),(83,I),AT=CTL
BX,C4,D,0D,(82,I),(83,I),AT=CTL
BY,C4,D,0E,(82,I),(83,I),AT=CTL
BZ,C4,D,0F,(82,I),(83,I),AT=CTL
2. Call UGEN:
UGEN INPUT=<INPUT-FILE>
3.1.4 Activities in MAREN
●
Version < V10
1. Use the following MARENADM instruction to define the storage location for the
CentricStor logical volumes:
//MODIFY-MAREN-PARAMETER LOCATION = *PAR(LOC-NAME = CEST1,
ACTION = *ADD)
2. Terminate MARENCP (MARENADM instruction):
//STOP-CONTROL-PROG MARENCP
3. Enter the following line in the MARENCP-ENTER file:
LOCATION CEST1,LOCAL,ROBAR-2
i
The new ROBAR-2 operand is required to indicate the operating mode for the
CentricStor system in MAREN.
4. Next, restart MARENCP.
32
●
Miscellaneous
Version >= V10
Parameters which are local on a computer or global which were previously defined
when the MARENCP procedure was started have no effect in MAREN V10.0A and
higher. They are grouped together as computer-specific functions.
Only after the MARENCP task has been started for the first time during the BS2000 sysstem run can the MAREN subsystem become active. Before this point, tape processing
is rejected in the case of dialog tasks; in the case of batch tasks an operator input is
requested. Consequently, when a system is started up using suitable startup procedures, it must be ensured that the control program and the MAREN subsystem are already
loaded when a session is opened.
The storage location for the logical volumes of CentricStor is defined with the following
MARENADM statement:
//MODIFY-MAREN-PARAMETER LOCATION-ENTRIES = *PAR(LOC-NAME = CEST1,
ACTION = *ADD(OPERATING-MODE=*ROBAR2))
The original file $SYSMAREN.SYSENT.MAREN.100.SPD.MARENCP can be used for
startup.
When you connect CentricStor to an STK robot system and some of the STK drives
continue to be used as native TAPE-C4 devices, you should note the following:
The storage location of the volumes used as real native (not to be confused with the tape
volumes used by CentricStor for making physical backups) is not defined in MAREN as a
robot storage location (operating mode for the real STK robots in MAREN is EXTERNAL and
not ROBAR-1). Because MAREN tries to handle free tape requests using volumes from a
robot storage location, when CentricStor is implemented the virtual volumes will be
assigned as free tapes by default.
To prevent this, you will need to use a MARENLM reservation file or make use of MAREN
exits.
Here is an example:
The real volumes in the STK robot system are still to be used with the MAREN storage
location STK1 for the free tape requests. Only jobs that have the job name CESTTEST are to
be assigned free tapes by MARENUCP from the virtual volumes entered in the MAREN
storage location CEST1.
MARENLM is used to take the following records from the MAREN reservation file (only
relevant fields are mentioned):
Location
Volume type
Job name
CEST1
TAPE-C4
CESTTEST
STK1
TAPE-C4
33
Miscellaneous
In order to make the same selection using MAREN exits, the following commands are
required:
In MARENEX6 (Device Depot Exit)
MARENEX6
TAPEC4
REALVOL
RETURN
CSECT
...
CLC
BE
...
CLC
BNE
MVC
B
MVC
...
DS
XR
LM
BR
DEVTYPE,=CL8'TAPE-C4'
TAPEC4
CRJOB,=CL8'CESTTEST'
REALVOL
USERFELD+9(8),=CL8'CEST1'
RETURN
USERFELD+9(8),=CL8'STK1'
SELECT VIRTUAL VOLUME
SELECT REAL VOLUME
0H
15,15
14,12,12(13)
14
In MARENEX1 (Reserve Request Exit)
MARENEX1
CHECKDEV
TAPEC4
REALVOL
RETURN
CSECT
...
CLC
BE
...
CLC
BE
...
CLC
BNE
MVC
B
MVC
...
DS
XR
LM
BR
LAFUNKNM,=CL8'MARENUCP'
CHECKDEV
CALLER = MARENUCP?
DEVICE,=CL2'BC'
TAPEC4
DEVICE TYPE = TAPE-C4?
CRJOB,=CL8'CESTTEST'
REALVOL
HOMELOC,=CL8'CEST1'
RETURN
HOMELOC,=CL8'STK1'
SELECT VIRTUAL VOLUME
SELECT REAL VOLUME
0H
15,15
14,12,12(13)
14
If subsequently (after completion of the migration phase) free tape requests are to be
handled from CentricStor and the free TAPE-C4 cartridges as defined for the user ID
USEREXCH are to be removed from the pool of real STK volumes, then the entries described
above must be replaced in the MARENLM file by the following entry:
34
Location
Volume type
User ID
STK1
TAPE-C4
USEREXCH
Miscellaneous
3.1.5 Further preparatory activities in MAREN
1. Including logical volumes in the MAREN catalog:
Case 1:
Logical volumes are added to the MAREN catalog using the following MARENADM
statement:
//ADD-FREE-VOLUMES VOL=..., FREE-LOCATION=CEST1, DEVICE-TYPE=TAPE-C4
Separate modification of TEMP-LOC is not necessary here. In the case of CentricStor
tapes, MAREN supplies all three locations (HOME-LOC, FREE-LOC and TEMP-LOC)
with the same value specified in FREE-LOCATION when //ADD-FREE-VOL is executed
(in contrast to TLS locations, for exmple).
Case 2:
If a logical volume is to be reserved for a particular user ID as soon as it is included in
the MAREN catalog, the following statement is used:
//ADD-RESERVED-VOLUME VOLUME=..., LOCATION=*PAR(HOME-LOC=CEST1,
FREE-LOC=CEST1, TEMP-LOC=CEST1), DEVICE-TYPE=TAPE-C4, USER-ID=...
2. Initializing the logical volumes:
The logical volumes can be initialized only when the corresponding preparations have
been completed in NDM and ROBAR (in the event of a host connection via ROBAR).
Before they are used for the first time all virtual volumes must be initialized. The
following MARENADM statement is used for this purpose:
//INIT-VOLUMES VOL=..., NEW-VOLUMES=*YES
Alternately the virtual volumes can be initialized with the BS2000 utility routine INIT. The
statement used for this is:
INIT TAPE-C4,VSN=...,NEW
The simplest way to include and initialize a number range of free volumes is to use the
following sequence of MARENADM statements:
//ADD-FREE-VOL VOL=*INT(FROM=<vsn1>,TO=<vsn2>),FREE-LOC=CEST1,
DEV-TYPE=TAPE-C4,INIT=*YES
//FREE-VOL VOL=*INT(FROM=<vsn1>,TO=<vsn2>),INIT-FILE=MARENADM.INITFILE(INIT- LOC=CEST1)
//INIT-VOL INIT-LOC=CEST1, ... ,NEW-VOL=*YES
The following message is output on the console for each released virtual volume:
MARM1S1 SET VIRTUAL VOLUME '<vsn>' OF SYSTEM '<location>' AS FAST MOUNT.
REPLY (0=OK; 1=NOK)
35
Miscellaneous
This message is answered by ROBAR or CSC.
When the virtual volumes are released the data on them is deleted irrevocably. Only the
tape labels are retained.
The location name for the virtual volumes must be specified in the INIT-VOL statement.
The following message is output by MAREN during the initialization run for virtual
volumes:
MARM1IB MOUNT VOLUME ''<vsn>' ON DEVICE '<device>' FROM ROBOT
'<location>''?
Further special aspects for logical volumes in MAREN:
–
Exporting by means of //EXPORT-VOLUME not allowed.
–
No relocation possible using //RETURN-VOLUMES.
–
Modification of HOME-, FREE- or TEMP-LOCATION via //MOD-VOL-ATTR is
rejected.
–
Deletion not possible using //REMOVE-USER-VOLUMES.
Virtual volumes must be released for deletion using //FREE-VOLUMES and then be
deleted using //REM-FREE-VOLUMES. Only the MAREN catalog entry is removed.
The logical volumes must then be deleted in CentricStor using the GXCC function.
Release run
In the MAREN release run all the released logical volumes are set to "migrated" provided
they are still in the cache. In a subsequent MAREN initialization run, however, logical
volumes are not restored, but the stub of a volume which still exists in the cache is initialized. However, if these volumes are initialized via the BS2000 user program INIT or in the
context of a MAREN free tape request, a restore takes place, as a result of which these
tapes are mounted with a slight delay. You are therefore recommended to reinitialize
released volumes via MAREN.
If you want to prevent the logical volumes being set to "migrated" when the MAREN release
run takes place, the optional REP correction A0447567-012 must be used. This correction
suppresses the output of the message MARM1S1 'SET VIRTUAL VOLUME '(&00)' OF
SYSTEM '(&01)' AS FAST MOUNT. REPLY (0=OK; 1=NOK)' when the MAREN release run
takes place and thus also implicitly suppresses migration of these volumes.
You are advised to perform initialization of logical volumes using the MARENADM
statement INIT-VOL.
Reinitialization of virtual volumes using the MARENADM statement INIT-VOL VOL=<oldvsn>,NEW-VOL=<new- vsn> is not permitted. This corresponds to the procedure in the real
robot in which the barcode label does not change and the old real tape is therefore still
loaded into the drive.
36
Miscellaneous
3.1.6 Activities in NDM
For a full description, see the BS2000 manual on system support [2].
The virtual tape devices must be assigned to a device depot in NDM, where the name of
this device depot must be identical to the MAREN storage location1:
/ADD-DEVICE-DEPOT UNIT=(mn1,mn2 ... mnx), LOCATION=CEST1
In BS2000/OSD V4.0A it is possible to assign more than 128 tape drives to a device depot
when the optional REP correction A0460384-330 is used.
To guarantee smooth and high-performance tape operation, the following values should be
set using the BS2000/OSD command /MODIFY-MOUNT-PARAMETER:
/MOD-MOUNT-PAR PREMOUNT-MSG=*IGNORE-USER-REQUEST
This parameter causes the output of the PREMOUNT messages (NKVT012 PREMOUNT
TAPE '(&00)' ON DEVICE '(&01)') to be suppressed. This message is of no significance in
robot operation in that it is only answered with "tsn." by ROBAR but no reactions occur. If
tapes frequently need to be mounted manually on real drives outside the robot, it may be
advisable to retain the default value PREMOUNT-MSG=*ACCORDING-TO-USERREQUEST.
!
CAUTION: The procedure here is the same as that for a real robot. Virtual tape
operation with CentricStor must be set with unconditional unloading of the virtual
volume. To do this, use the following command:
/MOD-MOUNT-PAR UNLOAD-REL-TAPE=
*REGARDLESS-OF-USER-REQUEST(TAPE-FAM=*MBK)
If long tapes are also to be dismounted after they have been used, the TAPE=*ALL
operand must be specified instead of TAPE=*MBK.
Restriction:
However, if operations take place on tape in a session with SPOOLOUT, this
parameter means that the SPOOLOUT tape must be dismounted and then
remounted after every SPOOLOUT of a file.
If several virtual drives are attached to a single BS2000, and these drives are located on
several CentricStor ICPs, then in order to ensure that the load is spread equally across the
various ICPs it is necessary to set the following mount parameter.
/MOD-MOUNT-PAR NEXT-TAPE-MOUNT = *LEAST-RECENTLY-USED-DEVICE
1
If the list of devices contains more than 10 entries, you must use several commands.
37
Miscellaneous
3.1.7 Activities in ROBAR-CL and ROBAR-SV
These are necessary if an ADIC library is connected.
If the virtual connection to CentricStor is made by an emulation of an ADIC library (VAMU),
the following settings for CentricStor are necessary for the host connection via ROBAR to
the VAMU. ROBAR must be Version 3_0B or higher.
ROBAR-CL
The following settings are recommended for monitoring times (entered in the file
SYSPAR.ROBAR-CL.040.PROZPARAM):
VerbMonitoring=300
VerbMonitoringTime=180
From ROBAR 4.0 these are the standard specifications.
ROBAR-SV
If CentricStor is connected to BS2000/OSD via ROBAR, the following preliminary work is
necessary:
●
ROBAR-SV must be reinstalled for CentricStor operation. In this case the CentricStorspecific ROBAR Rule Files are read in.
●
If the ROBAR environment variable ROBAR-ARCHIV is set (see ROBAR menu item
DEFINES -> PROFILE), the VSNs of the logical volumes must be included in this.
Example
ROBAR_ARCHIV=LV0000-LV9999
export ROBAR_ARCHIV
38
●
The addressing mode robot_devid=EXPLICIT must be set for the virtual devices. This
ensures that the mnemonic form of addressing is used.
●
Operation of the software ROBAR-SV V3.0D in conjunction with CentricStor has only
been released for RISC systems. Operation of the software ROBAR-SV V4.0A has
been released without restriction for RISC and Primepower systems.
●
After every restart of a VLS component the associated ROBAR-SV must also be
restarted.
Miscellaneous
ROBAR must be installed with the corresponding storage location name (here CEST1).
CentricStor is set as the AMU version at installation.
1. Make the following entries in the ROBAR configuration file:
a) Storage location name:
Location=CEST1
b) Number of robots:
robots_count=1
i
The virtual archive system is only supported as a single robot system.
c) VLP address and VAMU port:
robot_address1=TCP/IP(<VLP-adr>,<VAMU-port>)
i
The virtual archive system is accessed exclusively via a TCP/IP connection
(to the VAMU).
d) Virtual devices (are defined as TAPE-C4 devices):
gen_devices
mn1 robot=1 type=TAPE-C4
:
mnx robot=1 type=TAPE-C4
end_devices
The input and output areas of the robot system are irrelevant as far as CentricStor is
concerned.
2. The following parameters must be set so that the device mnemonic of the ROBAR-SV
configuration is used:
robot_devid=EXPLICIT
i
For further information on the configuration of CentricStor in BS2000 and in
ROBAR, see the manuals “MAREN” [3] Chapter 8.3 and “ROBAR” [5].
If a real archive system and a virtual archive system are to be operated together, a
separate ROBAR installation will be required for each of the two robot systems. The
storage location name for virtual volumes must be different from that used for real
volumes.
If several virtual archive systems are to be operated together, a separate ROBAR
installation will be required for each robot system. The volumes of each robot
system must be assigned their own separate storage location.
39
Miscellaneous
3.1.8 Activities in BS2000-CSC
These are necessary if a StorageTek library is connected.
3.1.8.1
General information
CSC Version 6.2 or higher must be used.
If an earlier version is used, the connect to ETERNUS CS cannot be set up. Message CSCX050 is then issued.
!
The virtual connection to CentricStor is implemented by emulating a StorageTek library
(VACS). The following preparations are therefore required in order to implement the host
connection to VACS via the StorageTek library interface:
●
After the CSC-Software has been installed (see CSC manual [9]) you will need to define
a virtual server with the following attributes in the CSC Gentab:
SERVER NAME=CEST1,PRONAM1=<vlp>,PRONAM2=,
VIRTUAL=Y,MOUNT=P,AUTOROUT=N,CAPSIZE=0, ,MGMTCLASS=BS2000
The server name (CEST1 in the example) can be freely selected, but may only be a
maximum of 5 Bytes in size and must be identical to the device depot name for the
virtual drives in BS2000 and to the storage location name for the virtual volumes in
MAREN.
Enter the VLP of the CentricStor configuration as the PRONAM.
The Parameter MOUNT=P[ROPOSE] must be set. CSC will then mount the virtual
volumes on the devices suggested by BS2000.
This means that dummy devices cannot be used as a virtual server because these are
not known to CentricStor and it is not possible to mount volumes on devices of this type.
This also means that CSC does not switch virtual drives back and forth between the
individual computers.
●
The virtual drives must be assigned to this server in the CSC Gentab.
Example:
DE HOSTNAME=HOST1,BS2DEV=B0,UNIXDEV=090,SERVER=CEST1,... DE
HOSTNAME=HOST1,BS2DEV=B1,UNIXDEV=091,SERVER=CEST1,...
etc.
Virtual drives are not switched by CSC and an entry in the PRIO parameter does not
therefore have any meaning.
The value to be specified for BS2DEV is the device mnemonic in BS2000.
The BS2000 devices are numbered sequentially in decimal notation in UNIXDEV, where
the last (lowest) position can take the values 0...9,A...J.
40
Miscellaneous
Archive addresses, which cannot occur in physical archives are also accepted (and
correctly operated by CentricStor):
LSM-ID:
Panel:
Slot:
0-F
0-F
0-9,A,B,C,D,E,F,G,H,I,J
The UNIXDEV names in the CSC Gentab must match the VACS libdev name specified
in the GXCC configuration in the Virtual Drives menu.
Example:
A UNIXDEV = 010 in the CSC-GENTAB must be entered in GXCC with the VACS
LibDevName = 0-0-1-0, a UNIXDEV = 122 must be entered in GXCC with the VACS
LibDevName = 0-1-2-2. You must only use decimal numbers (009 is followed by 010
and not by 00A).
For a virtual drive, you can use the same co-ordinates as for a real robot drive. This type
of overlap does not cause problems because the server name (e.g. CEST1) is also
flagged in the drive definition in the CSC Gentab, next to the UNIXDEV, which in this
case is the same.
If you have 2 ICPs with 32 drives each, we recommend that you assign the UNIXDEVs
from 000 to 031 to the ICP0 devices (in the GXCC configuration menu for Virtual Drives;
this corresponds to the VACS LibDevNames from 0-0-0-0 to 0-0-3-1). The devices on
ICP1 can then be assigned the UNIXDEVs 032 through 063. Alternatively, you could
assign the devices on ICP1 the UNIXDEVs 100 through 131.
As a general rule, you can number the devices under UNIXDEV as you wish. There will
be no problems as long as the VACS LibDevName in GXCC is selected appropriately.
But this does, in some cases, make debugging harder and can lead to oversights when
modifying the configuration (e.g. when installing a new ICP).
●
For the real Volumes (used outside CentricStor as native), you must also define a server
(if the STK robot system was already being used as
native before the introduction of CenricStor, then this entry is contained in the CSC
Gentab):
SERVER NAME=SILO1,PRONAM1=<stksun>,PRONAM2=,VIRTUAL=N,MOUNT=A,DEFAULT=Y
The server name can be freely selected, but may only be a maximum of 5 Bytes, and
must be identical to the Device Depot Name for the real drives in BS2000 and the
storage location name for the real volumes in MAREN.
The name of the ACSLS computer must be entered as the PRONAM.
41
Miscellaneous
The attributes VIRTUAL=N and MOUNT=A must be set. MOUNT=A[NY] means that CSC
can also mount drives other than those specified by BS2000 in the mount message. The
DEFAULT=Y parameter means that tape requests occurring as a result of MAREN
messages which do not specify a tape device (e.g. MARM1I2, MARUP45 etc.), are also
directed to this server.
i
3.1.8.2
The Gentab parameter SILONAME is only relevant if in the MARENUCP start
procedure, the parameter PROPOSE has not been set. If this MARENUCP
parameter is missing, then in the event of a free tape request, CSC will locate
and mount a real volume, using the MARENADM statement
//SECURE-FREE-VOLUMES.
●
Alongside the definitions of the individual servers, their respective drives and the
connected BS2000 host, the MAREN parameter is also to be set to Y in the CSC Gentab.
●
The created Gentab is implemented using the CSC Procedure PRC.CSCUTGEN. The
created output file must be specified in the CSC enter file ENT.CSCMAIN.
Activities in CentricStor: EMTAPE, VAMU/VACS
The logical devices are installed in the initial or update configuration using the GXCC
interface in the service mode.
CentricStor names of the LDs
The internal Centric Stor names of LDs are preassigned and are as follows for emulation
type OS-390:
L<Nnn>
where N = 0 .. 7 (as a rule) is the number of the ICP, on which the emulation is running, and
nn = 00 .. 1F (3F) is the number of the emulation with 32 or 64 LDs per ICP.
Device name and library device name
In the case of VLS-Type VAMU, the device name and library device name are always the
same, and must match the mnemonic of the LDs generated in UGEN.
Similarly with VLS-Type VACS, the device name must the mnemonic of the LDs generated
in UGEN.
The library device name must, however, match the virtual co-ordinates (e.g. 0-1-2-5) of the
StorageTek library, as they were generated in the GENTAB of BS2000-CSC (see section
“Activities in BS2000-CSC” on page 40).
42
Miscellaneous
3.1.9 Multiple CentricStor systems
●
When multiple CentricStor systems are used it must be ensured that the computer
names are unique in the LAN.
●
In order to avoid LAN performance/LAN load problems in the event of a kernel update
by means of "prepupdate" (cpio: broke pipe) when CentricStor is spread over several
locations, the service staff should perform the upgrade separately at each location.
●
After configuration changes in dynamic ESCON Director operation, e.g. port changes
because of modified cabling, the ICPs must be restarted.
3.1.10 DAS
The settings for the real drives’ cleaning mechanism, for robot sharing mode, and the
entries for the real drives’ configuration which are required to operate CentricStor are made
by the service provider.
43
SX servers
3.2 SX servers
As of K818 EKS 9, CentricStor V2.1 K818 EKS 9 supports connection via fibre channel to
the business servers of the SX series SX100-A, SX100-B, SX100-C, SX130, SX140 and
SX150 with OSD/XC Version 1.1 or newer (software package on the basis of BS2000/OSDBC V5.0C). SX100-D and SX160 with X2000 V4.0A or higher and OSD/XC Version 3.0 or
higher (software package based on BS2000/OSD-BC V7.0A) are supported by CentricStor
V3.0 and higher.
3.2.1 Connection via FC switch
CentricStor on SX servers can be connected to the Emulex FC controller on an SX server
(LP9002 as of FW Rev. 3.90A7 or LP9802 as of FW Rev. 1.01A2 ) via an FC switch
(Brocade; Connectrix McData).
The following FC switches were used in the CentricStor test with SX servers:
–
–
–
Brocade Silkworm 3800 Version V3.0.2c
Brocade Silkworm 12000 FW V4.0.0b
Connectrix McData FW 05.02.0013; EC 1030218
3.2.2 Connection without an FC switch
An FC connection of the SX server is also possible directly (meaning without an FC switch)
to CentricStor. The "direct connection" has been tested with CentricStor V3.0 on an Intelligent Tape Controller (ITC). X2000 V3 and OSD/XC 2.0 (software package based on
OSD-BC V6.0) ran on the SX server - SX140 in the test.
3.2.3 Configuring the tape units in CentricStor
The virtual tape devices for the SX servers must be configured in CentricStor with
connection type FC-SCSI and IBM 3590E emulation.
In contrast to the original IBM drive which is operated as TAPE-C6 under BS2000, the
TAPE-C4 interface is used for the virtual 3590-E1A.
44
SX servers
Example of CentricStor connected to SX140 (Leibniz):
vtls.conf in CentricStor:
V000:SPATZ-ISP0:8016:V000:FC-SCSI:VAMU:40:ON:1:15:0x00:IBM:IBM
03590E1A:0000000D0000:0
V001:SPATZ-ISP0:8017:V001:FC-SCSI:VAMU:41:ON:1:15:0x01:IBM:IBM
03590E1A:0000000D0001:0
...
45
SX servers
3.2.4 Configuring the tape devices on the SX server
3.2.4.1
Introductory note on X2000
The BS2000/OSD operating system with the X2000 carrier system is installed on the
BS2000 partition. X2000 is based on Solaris and principally provides the runtime
environment for BS2000/OSD.
The available CPUs of a BS2000 partition are logically divided into CPUs for BS2000/OSD
and into I/O processors which X2000 makes available for BS2000/OSD. The available main
memory is also divided between BS2000/OSD and X2000.
The functions offered by X2000 include:
●
HAL (Hardware Abstraction Layer)
HAL maps the hardware-software interfaces of /390 mode onto equivalent interfaces of
SPARC64 mode.
●
/390 firmware
The /390 firmware component supplements SPARC64 mode and enables existing /390
code to run object-compatibly (im /390 mode; synonym: compatibility mode) on
SPARC64 hardware.
●
Implementation of I/Os and data communication
The fibre channel peripherals are operated under BS2000/OSD by emulating the devices
in X2000 as so-called bus peripherals.
In the event of connection via FC, the BS2000 host behaves, from the CentricStor
viewpoint, like an Open System installation. For BS2000/OSD and the emulation layers
below it, the drives generated in CentricStor appear to be native SCSI tape devices.
3.2.4.2
Configuration steps
The CentricStor devices are made known to the BS2000 operating system through configuration in X2000 as of Version 2.5A (based on Solaris 8). Generation using IOGEN in
BS2000/OSD is not required.
The following files must be adjusted on the SX server for device configuration:
●
/kernel/drv/lpfc.conf (WWPN binding)
●
/usr/kernel/drv/SMAWLsti.conf (extension Targets/LUNS)
A reconfiguration boot of Solaris must then be performed.
The CentricStor devices (BS2 tapes) can subsequently be set up via WSA
(WebSysAdmin).
46
3.2.4.3
SX servers
Examples
Extract /kernel/drv/lpfc.conf
...
# 0x1
ELS events
# 0x2
Device Discovery events
# 0x4
Mailbox Command events
# 0x8
Miscellaneous events
# 0x10
Link Attention events
# 0x20
IP events
# 0x40
FCP events
# 0x80
Node table events
# 0x1000 FCP Check Condition events
log-verbose=0x10;
...
fcp-bind-WWPN= "10000000c937fa43:lpfc0t53"; # CentricStor Spatz ISP0 ctrl 15
...
# If automap is set, SCSI IDs for all FCP nodes without
# persistent bindings will be automatically generated.
# If new FCP devices are added to the network when the system is down,
# there is no guarantee that these SCSI IDs will remain the same
# when the system is booted again.
# If one of the above fcp binding methods is specified, then automap
# devices will use the same mapping method to preserve
# SCSI IDs between link down and link up.
# If no bindings are specified above, a value of 1 will force WWNN
# binding, 2 for WWPN binding, and 3 for DID binding.
# If automap is 0, only devices with persistent bindings will be
# recognized by the system.
automap=0;
...
# Some disk devices have a "select ID" or "select Target" capability.
# From a protocol standpoint "select ID" usually means select the
# Fibre channel "ALPA". In the FC-AL Profile there is an "informative
# annex" which contains a table that maps a "select ID" (a number
# between 0 and 7F) to an ALPA. If scan-down is set to a value of 0,
# the lpfc driver assigns target ids by scanning its ALPA map
# from low ALPA to high ALPA.
#
# Turning on the scan-down variable (on = 1,2, off = 0) will
# cause the lpfc driver to use an inverted ALPA map, effectively
# scanning ALPAs from high to low as specified in the FC-AL annex.
# A value of 2, will also cause target assignment in a private loop
# environment to be based on the ALPA (hard addressed).
#
# Note: This "select ID" functionality is a PRIVATE LOOP ONLY
# characteristic and will not work across a fabric.
47
SX servers
scan-down=0;
...
# topology: link topology for initializing the Fibre Channel connection.
#
0 = attempt loop mode, if it fails attempt point-to-point mode
#
2 = attempt point-to-point mode only
#
4 = attempt loop mode only
#
6 = attempt point-to-point mode, if it fails attempt loop mode
# Set point-to-point mode if you want to run as an N_Port.
# Set loop mode if you want to run as an NL_Port.
topology=0;
...
Notes:
–
The WWPN associated with the drive can be determined via the graphical user
interface (GXCC) of the CentricStor system.
–
The expression lpfc0t53 defines the Emulex Controller used (lpfc0..,lpfc1..,..) and the
freely selectable but unique target ID (....t0,....t1,..).
Extract /usr/kernel/drv/SMAWLsti.conf
...
###DRIVE CONFIG SECTION
tape-config-list=
"EXABYTE EXB-8505",
"EXB-8505",
"EXABYTE EXB-8900",
"EXB-8900",
"EXABYTE Mammoth2",
"EXABYTE MAMMOTH 2",
"FSC
",
"CentricStor",
"HP
C1537A",
"HP DDS3 4mm DAT",
"HP
C1557A",
"HP DDS3 4mm DATloader",
"HP
C5683A",
"HP DDS4 4mm DAT",
"HP
C5713A",
"HP
Ultrium",
"HP Ultrium",
"M4 DATA OPEN REEL TAPE ", "3505",
"IBM
03570C",
"3570",
"IBM
03590B",
"PXT1",
"IBM
03590E",
"T3591-E1",
"IBM
03490C",
"3588",
"IBM
ULT3580",
"3580",
"IBM
ULTRIUM-TD1",
"3580",
"IBM
ULTRIUM-TD2",
"3580-2",
"M4 DATA 123107 SCSI",
"3588",
"QUANTUM DLT8000",
"DLT8000",
"Quantum DLT4000",
"DLT 4000",
"Quantum DLT7000",
"DLT7000",
"STK
9490",
"STK 9490",
"STK
T9840",
"STK 9840",
"STK
T9940",
"STK 9940",
48
"XEXB-8505",
"XEXB-8900",
"XMammoth2",
"Xtor",
"XC1537A",
"XC1557A",
"XC5683A",
"XC5713A",
"XUltrium",
"X3505",
"X03570C",
"X03590B",
"X03590E",
"X03490C",
"X03580",
"X03580",
"X03580",
"X123107",
"XDLT8000",
"XDLT4000",
"XDLT7000",
"X9490",
"X9840",
"X9840";
SX servers
###END OF DRIVE CONFIG SECTION
###PROPERTY SECTION
XEXB-8505
=
1,0x35,0,0x4ce39,2,0x15,0x8c,1;
XEXB-8900
=
1,0x29,0,0x4ce39,4,0x7f,0x7f,0x7f,0x7f,0;
XMammoth2
=
1,0x35,0,0x1de39,1,0x28,0;
Xtor
=
1,0x36,0,0x18619,1,0x00,0;
XC1537A
=
1,0x34,1024,0xd639,4,0x00,0x13,0x24,0x3,3;
XC1557A
=
1,0x34,1024,0xd639,4,0x00,0x13,0x24,0x3,3;
XC5683A
=
1,0x34,1024,0xd639,4,0x00,0x13,0x24,0x3,3;
XC5713A
=
1,0x34,1024,0xd639,4,0x00,0x13,0x24,0x3,3;
XUltrium
=
1,0x36,0,0xd639,4,0x00,0x00,0x00,0x40,3;
X3505
=
1,0x33,0,0x41d,4,0x01,0x02,0x06,0x03,3;
X03570C
=
1,0x24,0,0x65c439,1,0x00,0;
X03490C
=
1,0x24,0,0x65c439,1,0x00,0;
X03590B
=
1,0x24,0,0x65c439,1,0x00,0;
X03590E
=
1,0x24,0,0x65c439,1,0x00,0;
X123107
=
1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
XDLT8000
=
1,0x38,0,0xD639,4,0x84,0x85,0x88,0x89,2;
XDLT4000
=
1,0x38,0,0xD639,4,0x80,0x81,0x82,0x83,2;
XDLT7000
=
1,0x38,0,0xD639,4,0x82,0x83,0x84,0x85,2;
X9490
=
1,0x24,0,0x1c43d,1,0x00,0;
X9840
=
1,0x24,0,0x45c439,1,0x00,0;
X03580
=
1,0x36,0,0x45c439,1,0x40,0;
###END OF PROPERTY SECTION
# Specifiy devices in CentricStor here, e.g. 64
name="SMAWLsti" class="scsi" target=53 lun=0;
...
49
SX servers
Device nodes
After a reconfiguration boot reboot -- -r the device nodes generated can be found under
/dev/rmt.
Example: SX140 Leibniz with 48 CentricStor devices (see example on page 45):
...
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/3cn ->
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,0:cn
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/4cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/6cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/7cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/8cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/9cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/10cn ->
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/11cn ->
...
lrwxrwxrwx
1 root
root
59 Nov 4 15:23 /dev/rmt/19cn ->
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,f:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/20cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/21cn ->
...
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/29cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/30cn ->
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,1a:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/31cn ->
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,1b:cn
...
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/39cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/40cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/41cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/42cn ->
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/43cn ->
50
SX servers
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/44cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/45cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/46cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2a:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/47cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2b:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/49cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2d:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/48cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2c:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/50cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2e:cn
lrwxrwxrwx
1 root
root
60 Nov 4 15:23 /dev/rmt/52cn
../../devices/pci@80,4000/fibre-channel@2/SMAWLsti@35,2f:cn
...
->
->
->
->
->
->
->
->
Setting up BS2 tapes in the WSA
●
Select host connector in BS2000
The host connector (HC) for setting up the BS2 tapes must be specified in the WSA (see
the next section). The HC is defined in BS2000/OSD as a channel from the range 00
through 0F. The channel type IE1(XS) is definitive in BS2000/OSD for the emulated
devices.
Example: BS2000/OSD of SX130 Perseus
/sh-dev-conf *chn(0*)
% MNEM UN-CLASS UN-TYPE
% 00
CHN
IE1(XS)
% 01
CHN
IE1(XS)
% 02
CHN
IE1(XS)
% 03
CHN
IE1(XS)
% 05
CHN
IE1(XS)
% 06
CHN
IE1(XS)
% 07
CHN
IE1(XS)
% 08
CHN
IE1(XS)
% 09
CHN
IE1(XS)
% 0A
CHN
IE1(XS)
% 0C
CHN
IE1(XS)
% 0D
CHN
IE1(XS)
% 0E
CHN
IE1(XS)
CONF-STATE
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
ATTACH /ON
POOL/SIDE
51
SX servers
Notes:
–
–
Channels not equal to 0* are not virtual channels. These are assigned by the
hardware. They are thus not available for selection for CentricStor.
It makes sense (for example because of selective SM2) to select a free channel
from 00 through 0F for CentricStor.
In the example, 0B can be selected as HC for WSA.
By configuring the HC with WSA, the HC is automatically added as a channel in
BS2000/OSD by the system (see next section).
●
Entries in WSA
1. Call WSA:
# DISPLAY=nnn.nn.nn.nnn:0.0;export DISPLAY
# WSA
2. Click on the X2000 Bs2Devices icon
3. Click on the BS2 Tapes button
4. BS2 tape menu: Select Create (wait for output)
5. Enter HC, for example B (selected as channel in BS2000; see above)
6. Select /dev/rmt/?cn device node
7. MN is the device mn in BS2000/OSD associated with the device node or LUN (see
vtls.conf above)
8. Unit is automatically updated with the HC setting
9. Click on Ok and wait until channel and device are assigned on VM2000
52
SX servers
For each device mn, 2 EMKTAPE_mn processes run in X2000, provided active=yes is
set for the device in WSA/BS2 Devices.
Example: SX130 Perseus
●
Timeout
In the case of large configurations or if there is a high system load on the SX server,
you are recommended to extend timeout monitoring when configuring CentricStor
devices (setting up BS2 tapes with WSA).
The timeout value can be increased in the file /etc/opt/SMAWwsaS/WSA:
# Default timeout for wdmexec commands (in seconds) ...
WSA_TIMEOUT : 255
The WSA_TIMEOUT variable defines the timeout in seconds. The value of WSA_TIMEOUT
can be changed from 45 to a maximum of 255.
53
SX servers
Example SX130 Perseus continued:
The channel and tape devices are automatically assigned:
...
%VM2G-000.150210
%IOR1-000.150211
%VM2G-000.150617
%IOR1-000.150617
%VM2G-000.151206
%IOR1-000.151208
...
%
%
%
%
%
%
VMS4065 DEVICE '0E' ADDED TO VM2000 CONFIGURATION
NKR0164 DEVICE 0E OF TYPE C400 ADDED
VMS4065 DEVICE '0F' ADDED TO VM2000 CONFIGURATION
NKR0164 DEVICE 0F OF TYPE C400 ADDED
VMS4065 DEVICE '30' ADDED TO VM2000 CONFIGURATION
NKR0164 DEVICE 30 OF TYPE C400 ADDED
/sh-dev-c 00,p
% DVC DEV-TYPE CONF-STATE PID CTL CHPID IOS
% 00
3590E
ATTACHED
00 0B
/sh-dev -conf *chn(0b),all
% MNEM UN-CLASS UN-TYPE CONF-STATE
% 0B
CHN
IE1(XS) ATTACH /ON
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
...
OUTER-CONNECTION
DVC
:00 ,INCLUDED
DVC
:01 ,INCLUDED
DVC
:02 ,INCLUDED
DVC
:03 ,INCLUDED
DVC
:04 ,INCLUDED
DVC
:05 ,INCLUDED
DVC
:06 ,INCLUDED
DVC
:07 ,INCLUDED
DVC
:08 ,INCLUDED
DVC
:09 ,INCLUDED
DVC
:0A ,INCLUDED
DVC
:0B ,INCLUDED
DVC
:0C ,INCLUDED
DVC
:0D ,INCLUDED
DVC
:0E ,INCLUDED
DVC
:0F ,INCLUDED
DVC
:30 ,INCLUDED
/sh-dev-conf 0C,p
% DVC DEV-TYPE CONF-STATE PID CTL CHPID IOS
% 0C
3590E
ATTACHED
00 0B
-
54
SCD PORT SIDE DEV-ADDR PATH
0B00
AVAIL
0B0C
AVAIL
SX servers
Example: SX140 Leibniz with 48 CentricStor devices
In the example the 2 EMKTAPE processes are running for device 40:
leibniz # ps -ef | grep -i EMKTAPE_40
root
root
9229
9213
9213
1
0 Feb 17 ? 0:05 EMKTAPE_40 /dev/SMAW/X2000/B/00 /dev/rmt/3cn
0 Feb 17 ? 0:00 EMKTAPE_40 /dev/SMAW/X2000/B/00 /dev/rmt/3cn
55
SX servers
Example SX140 Leibniz continued:
/sh-dev-conf *chn(0b)
% MNEM UN-CLASS UN-TYPE
% 0B
CHN
CONF-STATE
IE1(XS)
/sh-dev-conf *chn(0b) ,all
% MNEM UN-CLASS UN-TYPE CONF-STATE
% 0B
CHN
IE1(XS) ATTACH /ON
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
56
POOL/SIDE
ATTACH /ON
OUTER-CONNECTION
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
:40
:41
:42
:43
:44
:45
:46
:47
:48
:49
:4A
:4B
:4C
:4D
:4E
:4F
:50
:51
:52
:53
:54
:55
:56
:57
:58
:59
:5A
:5B
:5C
:5D
:5E
:5F
:60
:61
:62
:63
:64
:65
:66
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
SX servers
%
%
%
%
%
%
%
%
%
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
:67
:68
:69
:6A
:6B
:6C
:6D
:6E
:6F
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
3.2.5 Notes
●
Number of devices
An SX server recognizes all 64 devices in a CentricStor ICP. To save on Solaris
resources, it is however recommendable only to activate the CentricStor devices which
are actually needed in X2000 (WSA).
●
Dynamic addition of devices
The I/O handler permits a maximum of 4096 bus devices. CentricStor devices on the
FC also belong to the bus devices. The IOH enables dynamic addition of bus devices
(for example WSA -> BS2 Tapes -> Create), covering at least 64 devices and up to 10%
of the bus devices already defined. Sufficient memory for dynamic addition of devices
is kept free internally by the system. For further devices, an IPL may be required for
BS2000/OSD after the devices have been entered in /etc/opt/SMAW/X2000/bs2tab
with WSA.
Thus the earlier limit of 32 tape devices in BS2000/OSD 5.0C no longer applies.
●
HSI in BS2000
The virtual 3590-E1A devices are operated by BS2000 via the MBK6-HSI.
Device type:
Volume type:
●
printable:
TSOS type:
printable:
TSOS type:
3590E
C4
TAPE-C4
BC
Block size
In contrast to Open Systems Solaris … BS2000/OSD 5.0C currently supports a
maximum I/O block size of 32 Kbyte.
57
SX servers
●
Compression
OSD/XC does not support the compression selection HOST.
The BS2000 devices (mn) are permanently linked to the Solaris device nodes via
X2000 with descriptor c (/dev/rmt/*cn) and cannot control compression by means
of volume type TAPE-C3 or TAPE-C4.
Control can only be implemented for a device via CentricStor with the configuration
setting Compression ON or OFF.
Thus X2000 ensures that data compression is always active in CentricStor for a tape
device on the SX server unless configuration is configured with OFF in CentricStor for
this tape device.
●
Device sharing, switch, path
SX servers do not support SCSI Reserve/Release.
Using the CentricStor devices via a joint WSA Management Server as shared devices,
i.e. exclusively on several SX servers alternately, has not been tested with
CentricStor.
The so-called 1:1 configuration has been quality-assured and generally released:
The FC port of a CentricStor ICP must be assigned to precisely one FC port of an
SX server and the FC port of an SX server to precisely one FC port of a CentricStor
ICP.
This excludes joint use of an ICP port and logical devices in CentricStor by multiple
SX servers, by SX and S servers (business servers of the S series, see section
“CentricStor on S servers” on page 60) or with Open Systems.
The devices are connected by a single path.
58
SX servers
3.2.6 Restrictions
●
Use of CentricStor by the X2000 tool PSR (physical saving and restoring of disks or
individual slices) is not provided for.
●
Before maintenance work that results in the emulations (vtd) in CentricStor being terminated takes place, the tape emulations in X2000 should be disabled. If this is not done,
experience shows that with X2000 V4.0A on Solaris 10 a Solaris reboot will generally
be required to permit the CentricStor tape devices to be assigned to BS2000 again
(A0562700 emu.core in X2000 V4.0A).
The tape emulations in X2000 are generally disabled/enabled via WSA. The process of
disabling/enabling a large number of tape emulations on the SX server can be
expedited under X2000 V2.5 using the following commands in Solaris:
/opt/SMAW/X2000/bin/acfconf stop -i MKTAPE
/opt/SMAW/X2000/bin/acfconf load -i MKTAPE
3.2.7 Diagnostic documentation for the tape emulation in X2000
The diagnostic documentation for the tape emulation in X2000 can be found on the
SX server in directory /var/opt/SMAW/X2000/diag/emtape
59
CentricStor on S servers
3.3 CentricStor on S servers
As of CentricStor V2.1 and BS2000/OSD-BC Version 5.0C support not only the connection
of CentricStor via ESCON, but also connection via Fibre Channel - always with FC switch on the Business Servers of the S series (S120, S140, S145, S155, S165, S170, S180,
S190, S200).
3.3.1 Firmware/software statuses
At least the following firmware/software statuses are required to operate S servers with
CentricStor:
●
FC Switch
–
–
–
●
HCP-Level S server:
–
–
–
–
60
Brocade 2800 FW V2.60D
Brocade 12000 FW V4.0.0b
Connectrix McData FW 05.02.0013 ; EC 1030218
S120
at least E45L01G-01P+034 or current E45L01G-01R+008
S140/S170
at least E40L01G-02N+062 or current E40L01G-02Q+016
S145/S155/S180/S190
at least E60L02G-02D+047 or current E60L02G-02E+120
S165, S200
at least E70L01G-01U+039
●
In BS2000/OSD-BC as of V05.0C the corrections package P1/05 or higher or for S165
and S200 the corrections package P2/07 or higher
●
MAREN 9.0B corresponding to correction package 2/2003 of 09.12.2003 with the
optional patch REP: A0504294. The optional patch REP is not required with MAREN
10.0A.
●
ROBAR-SV 5.0A00 (this enables ROBAR-CL 4.0A00 still to be used in BS2000/OSD
5.0C). Migration from ROBAR SV 4.0A00 to ROBAR SV 5.0A00 with the rule file EKS
"RO150A002" for Reliant UNIX (Mips) or "RO550A002" for Solaris is urgently recommended.
●
CSC 6.2
3.3.2 Connection and configuration
The virtual devices for S servers must be configured as follows in CentricStor:
Connection type: FC-SCSI
Emulation:
IBM 3590E
For S servers, a maximum of 64 devices per ICP can be configured in CentricStor. Virtual
robot control of CentricStor can be implemented both via the VAMU interface (with ROBARCL/ROBAR-SV on the host side) and via the VACS interface (with CSC on the host side).
Connection of CentricStor to S servers is always implemented via an FC switch (Brocade
or Connectrix McData) to Fujitsu’s proprietary channel module FC-SCSI on the S server.
The so-called inverted Y configuration and the Y configuration have been released, and
also their combination as a so-called X configuration: Multiple ICP ports can be assigned
jointly to a port (FC channel) of an S server, and multiple S servers may make joint use of
the same ICP port. The individual LUNs/tape devices are assigned exclusively to 1 S server
with /attach-device mn in BS2000.
Example:
S190 /sh-dev-conf (50,70,10,4g),p
%
DVC
DEV-TYPE CONF-STATE PID CTL CHPID IOS
%
50
3590E
ATTACHED
-
8O
F0
-
-
-
-
F0000000 AVAIL
%
70
3590E
ATTACHED
-
8P
F0
-
-
-
-
F0000000 AVAIL
%
10
3590E
ATTACHED
-
88
F0
-
-
-
-
F0000000 AVAIL
%
4G
3590E
ATTACHED
-
89
F0
-
-
-
-
F0000000 AVAIL
S170 /sh-dev-conf (50,70,10,4g),p
%
DVC
DEV-TYPE CONF-STATE PID CTL CHPID IOS
%
50
3590E
DET(EX)
-
8O
98
-
-
-
-
98000000 AVAIL
%
70
3590E
DET(EX)
-
8P
98
-
-
-
-
98000000 AVAIL
%
10
3590E
DET(EX)
-
88
98
-
-
-
-
98000000 AVAIL
%
4G
3590E
DET(EX)
-
89
98
-
-
-
-
98000000 AVAIL
/attach-device 50
%
NKR0111 'DEVICE
=50' ASSIGNED ELSEWHERE
%
NKR0044 'DEVICE
=50': ATTACHMENT REJECTED
61
The CentricStor devices must be generated by means of IOGEN in BS2000. The README
file for BS2000 should also be referred to (SYSRME.BS2CP.140.E):
**********************************************************************
*
CHN
FIBRECHANNEL / FICON
*
**********************************************************************
CHN 98,IBF,MODE=FCP
**********************************************************************
*
MBK
3590E/3591
*
**********************************************************************
CTL 8M,BLM,(98,0,10000000C932A5E4)
*ICP-WWPN
*
*
+- ➟ Address range per controller (must start at zero)
*
|
DVC L0,C4,D,0000,(8M),AT=CTL
BS2000/OSD-BC supports the compression selection HOST: CentricStor then writes in
uncompressed format for volume type TAPE-C3 and in compressed format for volume type
TAPE-C4.
The following error message indicates incorrect generation of the controller on the ICP
(here ICP3):
(C0) +XAA5-000.203902 % NDW0104 Device D0: SenseID
STGT-FC RZWUICP3 incompatible with Device Type C4
3.3.3 Restrictions
The so-called "1:1" configuration has been released:
It is inadmissible for S servers and SX servers (business servers of the SX series SX100,
SX130, SX140, SX150) or S servers and Open System servers to make joint use of an ICP
port and thus of all logical devices in CentricStor on this ICP port. A risk is to be expected
because, for example, SX servers do not support the device reservation (reserve/release).
On the FC switch, no other zone with the ICP port - even if it is not used - may be entered
by another host which does not belong to the S series.
CentricStor tape devices and FC disks may not be configured in the same zone on the FC
switch and not on the same channel of the S server.
Address range per controller (must start at zero)
62
4 CentricStor on z/OS
4.1 Introduction
A CentricStor virtual tape server behaves towards z/OS or OS/390 systems like a physical
IBM-3490E 36 track tape technology and is in a position to communicate with more than
one LPAR in parallel.
The virtual tape drives (devices) offered by CentricStor are configured in the HCD (Harware
Configuration Definition) like real connected devices. Dependencies of the operating
system which is in use (SMPE status) are not known.
The physical connection between CentricStor and the IBM host is implemented via ESCON
or the ESCON director channels and also via FICON or the FICON director channels. The
technical software connection takes place via a host software for an ATL (Automatic Tape
Library) which runs as a subsystem in z/OS or OS/390. Host software solutions that are
available are: NCS/CSC from SUN/STK, HACC from Quantum/ADIC and CSMVS from
FSC. Dependent on which host software was chosen, the corresponding Virtual Library
Service (library emulation) is set in CentricStor. However, the type of physical library
attached to CentricStor (back end) is not visible to the host.
CentricStor can make several different virtual drives available depending on configuration
level and ESCON/FICON ports contained. Those with the highest configuration level can
be taken from the relevant CentricStor data sheet or the menu of the CentricStor configuration program GXCC.
The information in this manual is expanded on by the installation manual for the host
software solutions NCS/CSC (from SUN/StorageTek), HACC (from Quantum(ADIC)) and
CSMVS (from FSC); further information is also provided in the CentricStor manuals. For
information on tape management systems please refer to the manuals which the vendors
provide.
63
Subjects Covered
CentricStor on z/OS
4.2 Subjects Covered
The individual subject areas are:
–
–
–
–
–
–
Definition of CentricStor logical drives in z/OS using HCD
Logical volume definition
VACS Interface
Host software functions: NCS/CSC, CSMVS, HACC
Tape management considerations for DFSMSrmm, CA1, TLMS and Control-T
Scratch subpooling
4.3 Configuration of Logical Drives in z/OS
From the point of view of the host, each virtual tape drive is connected like a physical tape
drive.
With the highest configuration level, CentricStor supports 512 3490E tape drives (devices)
simultaneously. The following configuration examples describes a configuration level for 64
tape drives.
An ICP (Integrated Channel Processor) controls up to 64 virtual tape drives. To achieve an
acceptable throughput, a setup for 32 virtual drives per ICP is recommended.
For z/OS, an ICP represents up to 4 3490E Control Units (CU). A single 3490E controller
supports 16 devices. On ESCON or FICON channels four logical control units are defined
to represent all 64 drive addresses. The IOCP subparameter CUADD within the UNITADD
statement is used to define the logical control units (0-3). In a recommended configuration
of 32 logical drives per ICP, only CUADD=0 and CUADD=1 are needed.
Every ICP is equipped with at least two ESCON or FICON ports, which should be used for
redundancy. Both, a direct connection and a switched configuration via an ESCON or
FICON director (switch) are possible.
64
CentricStor on z/OS
Configuration of Logical Drives in z/OS
4.3.1 Example Configuration
4.3.1.1
Direct Connection
ESCON or
FICON Host
Channel
ICP0
CU 0 1E00
CUADD 0
UNITADDR 00..15
CU 1 1E10
CUADD 1
UNITADDR 00..15
B0
B1
B2
B3
B4
ICP1
B5
B6
CU 0 1E40
CUADD 0
UNITADDR 00..15
CU 1 1E50
CUADD 1
UNITADDR 00..15
B7
Generating 2 ICPs with 32 virtual drives each:
The example uses addresses 1E00-1E1F for ICP0 and 1E40-1E5F for ICP1, so that the
gaps (1E20-1E3F and 1E60-1E7F) can be used in case the ICPs are upgraded to a 64
virtual drive configuration. In case of ESCON attachment TYPE=FC should read
TYPE=CNC.
CHPID
CHPID
CHPID
CHPID
PATH=(B0),SHARED,TYPE=FC
CNTLUNIT CUNUMBR=1E00,PATH=(B0,B1),
UNITADD=((00,016)),CUADD=0,UNIT=3490
65
CentricStor on z/OS
IODEVICE ADDRESS=(1E00,016),UNITADD=00,CUNUMBR=(1E00),
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
4.3.1.2
Switched Connection
Switch 65
ICP0
ESCON or
FICON
Host
4A
Channel
4B
B0
CU 0 1E00
CUADD 0
UNITADDR
00..15
CU 1 1E10
CUADD 1
UNITADDR
00..15
B1
B2
B3
ICP1
B4
B5
4A
B6
CU 0 1E40
CUADD 0
UNITADDR
00..15
CU 1 1E50
CUADD 1
UNITADDR
00..15
B7
4B
Switch 67
The example shows a FICON switched configuration. For ESCON replace TYPE=FC by
TYPE=CNC.
The example also shows a configuration, that did not define the switch/director itself. If the
switch/director is defined within the HCD, the Control Unit Port (CUP) feature is mandantory
for the switch/director. This also applies, if cascading FICON is configured. Please refer to
the manual of the switch/director about further details.
For further information on HCD details, see IBM Hardware Configuration Definition User's
Guide.
CHPID
CHPID
CHPID
CHPID
66
CentricStor on z/OS
CNTLUNIT CUNUMBR=1E00,PATH=(B0,B1,B6,B7),
UNITADD=((00,016)),CUADD=0,UNIT=3490,Link=(4A,4A,4A,4A)
UNITADD=((00,016)),CUADD=1,UNIT=3490,Link=(4A,4A,4A,4A)
UNITADD=((00,016)),CUADD=0,UNIT=3490,Link=(4B,4B,4B,4B)
UNITADD=((00,016)),CUADD=1,UNIT=3490,Link=(4B,4B,4B,4B)
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
STADET=Y,UNIT=3490
4.3.2 Virtual Drive Sharing
Device sharing is not recommended outside a SYSPLEX or without equivalent host tape
drive sharing software. Device sharing between BS2000 and SYSPLEX is not also recommended. ESCON and FICON adapters, CUs and ICPs can be used jointly between z/OS
and BS2000 systems.
i
z/OS uses the missing interupt handler (MIH) to control outstanding channel operations. Fujitsu Siemens Computers recommends to use a timeout value of 10
minutes for CentricStor virtual drives.
The following MIH entry in SYS1.PARMLIB (IECIOSxx) represents this recommendation:
Example
MIH DEV=(1E00-1E0F), TIME=10:00,HALT=06:00
/*T3490*/
4.3.3 Representation of Virtual Drives in CentricStor
The virtual drives of CentricStor are defined dependent on the host software solution.
NCS/CSC and CSMVS both use the VACS interface, whereas HACC uses the VAMU
interface. Mapping of the virtual drives is done by the LibDevName within the parameter file
of the corresponding software.
The LibDevName for HACC is a two digit decimal or hexadecimal number.
i
If your HACC configuration uses more than 100 virtual drives, make sure, that the
hexadecimal representation is used during the initial setup of the VAMU drives.
67
CentricStor on z/OS
The LibDevName consists of the virtual quadruple (ACS, LSM, panel, row). Due to
restrictions of the NCS/CSC, the maximum number of drives per panel is 4. Therefore and
for mount balancing purposes, special logic is applied to the numbering of the virtual drives.
The scheme for the numbering will be discussed under the chapter of NCS/CSC setup.
4.3.4 Logical Volume Definition
Before logical (virtual) volumes (LV) can be defined using the GUI, the logical volume group
(LVG) has to be defined first. With CentricStor version 4.0A und V3.1D SP04 and higher,
the LVG supports a new attribute: Auto Labelling (default disabled!)
Using Auto Labelling makes the process of volume initialisation obsolete. It generates a
VOL1 and HDR1 record for each logical volume. If you do not enable the Auto Labelling
option, you have to initialise each volume. Please refer to the corresponding chapter of the
tape management software that is used in conjunction with CentricStor.
The following graphic shows the Auto Labelling option in the LVG define panel:
68
CentricStor on z/OS
4.3.5 VACS Interface
The Virtual ACSLS interface enables CentricStor to look like a SUN/STK ACSLS server.
Scratch subpools must be defined here, to map logical volume groups to a scratch subpool.
Before you use the following procedure, refer to the explainations that correspond
to your tape management software. The sequence is also dependent on the initialisation process of the logical volumes.
i
1. Login to CentricStor via a TELNET session and start the operation with: cmd_proc
2. Define pool ID and assign scratch status to LVs
At first define the pool-ID, that will be used. The available range of pool-IDs is 1 to 254.
The syntax to define a pool is as follows:
define pool &low_water_mark &high_water_mark &pool_ID
It may be a good idea, to specify a high_water_mark to a value, that covers one week
of scratch usage. Then you get an information, in case you have defined too many
scratch volumes, which may occupy backend space. For low_water_mark specify a
value that fits your requirements.
Example:
define pool 600 3000 1
Pool-ID 1 is now defined and you can query it or all pools with:
query pool 1 or q pool all
Reply may be as follows:
ACSSA> q pool all
2007-01-02 15:28:16
Identifier Volume Count
0
0
1
0
2
1134
8
999
10
265
50
58
Pool Status
Low Water Mark
High Water Mark
02147483647
600
3000
0
99999
0
99999
0
1000
0
100
Attributes
3. Now assign the volumes that belong to LVG01 to the scratch pool:
set scratch &pool_ID &volrange
set scratch 1 A00000-A00999
i
Please note, that the volser is case sensitive. For mainframe volumes use
capitals!
69
Host Software Functions
CentricStor on z/OS
After the volumes are assigned to pool ID 01, the output of the query pool 1 looks
like this:
ACSSA> q pool 1
2007-01-02 15:37:16
Identifier Volume Count
1
1000
Pool Status
Low Water Mark
High Water Mark
600
3000
Attributes
Further information can be obtained using the query scratch command:
ACSSA> q scratch 1
1
A00001
1
A00001
1
A00002
......
1
A00988
1
A00989
1
A00990
1
A00991
i
1, 1, 1, 1,1
1, 1, 1, 1,1
1, 1, 1, 1,1
home
home
home
3490E
3490E
3490E
1,
1,
1,
1,
home
home
home
home
3490E
3490E
3490E
3490E
1,
1,
1,
1,
1,
1,
1,
1,
1,1
1,1
1,1
1,1
After a volume has been mounted, it looses its scratch status. This is done for
security reasons. Although it is scratch from the point of view of the tape
management, it is a data volume in CentricStor. With the next scratch synchronisation run, it will be scratch again in VACS. The query pool and the query
scratch commands only show counts or volumes, that have the scratch status in
VACS.
4.4 Host Software Functions
The different host software solutions, that are available for a CentricStor attachment to
z/OS, optimize the functionality of the system and should be chosen by the installations
needs Three major functions are represented by the host software and will be discussed
here. These functions are:
70
●
Allocation Influencing
●
Message processing and automation
●
Scratch synchronisation between CentricStor and tape management
CentricStor on z/OS
4.4.1 Allocation Influencing and Scratch Subpooling
In a z/OS environment, tape processing is done by the application in two ways. Tape
volumes are allocated either specific or nonspecific.
A specific tape request is either issued by coding the VOL=SER parameter in JCL, by the
application itself during dynamic allocation (e.g. DFHSM recall) or by allocating an existing
dataset via the OS-catalog. In opposite to the JCL VOL=SER parameter together with the
UNIT=esoteric parameter, the other two allocation requests end up in a generic device
request, which in case of CentricStor virtual drives is 3490.
In a mixed configuration (i.e. CentricStor and other 3490-type drives), such a request may
end up in an allocation, where a CentricStor logical volume should be mounted on a manual
drive or a physical volume should be mounted on a CentricStor virtual drive. To avoid this
situation, the allocation influencing function of the host software interfaces the allocation
request via the subsystem interface by modifying the eligible device list (EDL).
A nonspecific allocation requests any available tape, that can be used for output. These
volume are referred as scratch volumes. Scratch volume ranges may be grouped by function
or size and are represented by a logical volume group (LVG) within CentricStor. This is also
called scratch subpooling.
i
The expression scratch subpool is understood differently in many views. Some
functions refer to a scratch subpool as a volume range or even multiple ranges
independently from the status, whereas from an ACSLS/VACS point of view, only
the volumes that have a scratch status belong to the pool.
Normally the esoteric name of the tape subsystem is specified for example in the JCL and
in this case no allocation influencing is necessary. For ease of use, installation may want to
specify a higher level of esoteric or a generic name for the allocation request. In this case,
the allocation influencing function of the host software may direct the allocation to the
appropriate esoteric based on dataset name and/or jobname. This kind of function varies
with the supported software packages and will be discussed in the corresponding chapter,
that explains the differences between NCS/CSC, HACC and CSMVS .
71
CentricStor on z/OS
4.4.2 Message Processing and Automation
The host software packages analyse tape related messages and communicate with
CentricStor to indicate mounts and dismounts. Tape related messages may be issued either
by the operating system itself or by the tape management system. The tape management
system may also change or suppress OS messages. Please refer to the discussion of
supported tape management software for more information.
Basically mount/dismount messages are analysed to extract function, device address and
volume serial. Further analysis may be used to select a scratch subpool based on different
criteria. Scratch subpooling may also be implemented via the tape management system.
Please refer to the section, which explains the different tape management systems.
72
CentricStor on z/OS
Host Software Solutions
4.5 Host Software Solutions
4.5.1 NCS/CSC
This chapter gives important information on the installation and customisation of CSC/MVS.
It does not replace the SUN/STK documentation. The information that is given, is based on
NCS 6.1.0.
4.5.1.1
Overview
The Nearline Control System is a software package to drive SUN/STK libraries in a z/OS or
OS/390 environment. It consists of basic functions and option subfuctions. The subfunction
Client System Component for MVS (CSC/MVS) is used to attach the CentricStor VACS
emulation. The CSC covers the functions Message Processing and Automation and Scratch
Synchronisation. It communicates with VACS via TCP/IP. Allocation Influencing is covered by
the Storage Management Component (SMC), which is the base function of NCS.
Control Path of a CentricStor Configuration with CSC
SYSA
Tapemanagement
CSC
SYST
Tapemanagement
Tapemanagement
CSC
TMC
CSC
SMC
SMC
SMC
TCP/IP
TCP/IP
TCP/IP
Comments:
SYSA and SYSB
share a Tape
Management
Database or Control
Dataset (TMC)
SYST has a seperate
TMC
All systems connect
to the same VACS
ports of the VLP
TMC
SYSB
CentricStor
VLP
SVLP
VACS
VACS
73
4.5.1.2
CentricStor on z/OS
Installation and Customisation
NCS is installed via the SMP/E program. The base function (SMC) and the subfunctions are
represented by FMIDs. The following FMIDs of the NCS 6.1 software are contained:
FMID
Function
Needed for CentricStor
SMC6100
contains the SMC load modules and samples
Yes
SMZ6100
contains the SMC JES3 support
Yes, if JES3 installation
SMX6100
provides SMC-specific functions for the
StorageTek HTTPserver.
NO
SSKY5000 Contains the HTTP server load modules,
distributed macros and samples
ASAR700
contains SAS/C 7.0 selected components required NO
for the StorageTek HTTP server
SOS6100
contains the HSC load modules, distributed
macros, and samples
NO, but recommended
if tape management is
RMM, CA1 or TLMS
SCS6100
contains the MVS/CSC load modules, distributed
macros and samples
YES
SOC6100
contains the LibraryStation load modules and
samples
NO
SSCR70C
contains SAS/C 7.0 selected components required YES
for LibraryStation and MVS/CSC
SSCR70D
contains SAS/C 7.0 selected components required YES
for LibraryStation, MVS/CSC, and the StorageTek
HTTP server
i
74
NO
The function SOS6100 for HSC contains load modules for scratch synchronisation,
that are also used by CSC. If you do not install SOS6100, you have to manually
maintain the module that corresponds to your tape management software.
Assemble and linkedit it to the CSC load library. A sample source code for
SLUDRCA1, SLUDRTLM and SLUDRRMM is provided in the software package of
NCS for HSC in library SLSSAMP. If you decide to install SOS6100, the ready to go
load modules are contained in library SLULINK. Please refer also to the CSC
System Programmer's Guide.
CentricStor on z/OS
Additional information on CSC customisation
After the SMP/E installation is complete, you can begin with the customisation process of
the CSC. Please follow the instructions of the CSC Configuration Guide.
Please refer to the following example to setup the CSC startup parameters:
*********************************************************************
*
* SAMPLE STARTUP PARAMETERS FOR MVS/CSC
*
*********************************************************************
*
SERVER(ACSLS)
<<<<<<<<<<
* SERVER TYPE
COMM(TCPIP)
* TCP/IP COMMUNICATIONS
TCPN(TCPIPSTC)
<<<<<<<<<<
* TCP/IP NAME
* INTERNET ADDRESS OF VACS
INTERNET(192.168.82.113)
<<<<<<<<<<
* CENTRICSTOR IP ADDR
*
LIBDEV(,CSTOR)
<<<<<<<<<<
* LIBRARY ESOTERICS
NONLIB(CART)
<<<<<<<<<<
* NONLIBRARY ESOTERICS
*
LIBUNIT(1E00,1E01,1E02,1E03,1E04,1E05,1E06,1E07, * ICP 0
1E08,1E09,1E0A,1E0B,1E0C,1E0D,1E0E,1E0F, 1E10,1E11,1E12,1E13,1E14,1E15,1E16,1E17, 1E18,1E19,1E1A,1E1B,1E1C,1E1D,1E1E,1E1F, 1E40,1E41,1E42,1E43,1E44,1E45,1E46,1E47, * ICP 1
1E48,1E49,1E4A,1E4B,1E4C,1E4D,1E4E,1E4F, 1E50,1E51,1E52,1E53,1E50,1E55,1E56,1E57, 1E58,1E59,1E5A,1E5B,1E5C,1E5D,1E5E,1E5F)
*
UNITMAP(1E00,01:01:01:0,* ICP 0 CU 0
1E01,01:02:01:0,* DRIVE 0
1E02,01:03:01:0,* PANEL 2
1E03,01:04:01:0,* LSM 1 - 16
1E04,01:05:01:0,*
1E05,01:06:01:0,*
1E06,01:07:01:0,*
1E07,01:08:01:0,*
1E08,01:09:01:0,*
1E09,01:0A:01:0,*
1E0A,01:0B:01:0,*
1E0B,01:0C:01:0,*
1E0C,01:0D:01:0,*
1E0D,01:0E:01:0,*
1E0E,01:0F:01:0,*
1E0F,01:10:01:0,*
1E40,01:01:01:1,* ICP 1 CU 0
75
1E41,01:02:01:1,1E42,01:03:01:1,1E43,01:04:01:1,1E44,01:05:01:1,1E45,01:06:01:1,1E46,01:07:01:1,1E47,01:08:01:1,1E48,01:09:01:1,1E49,01:0A:01:1,1E4A,01:0B:01:1,1E4B,01:0C:01:1,1E4C,01:0D:01:1,1E4D,01:0E:01:1,1E4E,01:0F:01:1,1E4F,01:10:01:1,1E10,01:01:01:2,1E11,01:02:01:2,1E12,01:03:01:2,1E13,01:04:01:2,1E14,01:05:01:2,1E15,01:06:01:2,1E16,01:07:01:2,1E17,01:08:01:2,1E18,01:09:01:2,1E19,01:0A:01:2,1E1A,01:0B:01:2,1E1B,01:0C:01:2,1E1C,01:0D:01:2,1E1D,01:0E:01:2,1E1E,01:0F:01:2,1E1F,01:10:01:2,1E50,01:01:01:3,1E51,01:02:01:3,1E52,01:03:01:3,1E53,01:04:01:3,1E54,01:05:01:3,1E55,01:06:01:3,1E56,01:07:01:3,1E57,01:08:01:3,1E58,01:09:01:3,1E59,01:0A:01:3,1E5A,01:0B:01:3,1E5B,01:0C:01:3,1E5C,01:0D:01:3,1E5D,01:0E:01:3,1E5E,01:0F:01:3,1E5F,01:10:01:3)
CentricStor on z/OS
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
DRIVE 1
PANEL 2
LSM 1 - 16
ICP 0
DRIVE
PANEL
LSM 1
CU 1
2
2
- 16
ICP 1
DRIVE
PANEL
LSM 1
CU 1
3
2
- 16
*
76
CentricStor on z/OS
ALOCTIME(180)
WTODESC(NO)
MSGCASE(MIXED)
DELDISP(NOSCRTCH)
TRACE(NO)
TRACD(FILE)
LOG(RESET)
<<<<<<<<<<
COMPRFX('!')
<<<<<<<<<<
LKEYDEF('YOUR.CSC.PARMS(CSCKEY)')
*
*
*
*
TIME OUT SECONDS
NO MESSAGE HIGHLIGHTING
OUTPUT CASE
DELETE DISPOSITION
* LOGGING OPTION
* COMMAND PREFIX
<<<<<<<<<<<<<<
The SERVER parameter is set to ACSLS because CentricStor emulates this type of
attachment.
Add the IP address of CentricStor and the name of your TCP/IP started task to INTERNET
and TCPN.
For LIBDEV specify the esoteric name of your logical CentricStor drives. By default
CentricStor is represented as ACS1. Therefore you have to specify ,cs_esoteric. If you
need any other numbering of the ACS ID, please check the first digit of the virtual drive
coordinate during the VACS setup and also specify the correct number of commas
preceding the esoteric name. The count of commas represents the ACS number.
In case you also use other tape drives than CentricStor, specify the esoteric name of these
non library drives.
The LIBUNIT statement must contain all CentricStor logical drives. It must match all drives,
that are contained in the esoteric that is given under LIBDEV.
UNITMAP contains the virtual drives location of CentricStor logical drives. Please make
sure, that it matches the definitions of the VACS setup. The example defines 64 logical
drives that are represented by two ICPs. The distribution of the logical drives across LSMs
should allow mount balancing across the ICPs. Please refer to the chapter, which explains
virtual drives coordinates (see section “Virtual Drives Coordinates” on page 79).
Make sure that you have a file or member that contains a valid license key for NCS/CSC
under LKEYDEF.
The parameter PORT does not take effect under SERVER(ACSLS). It cannot be used to
restrict communication ports to enable a firewall management.
77
CentricStor on z/OS
In addition, please observe the following hints during the setup:
●
CSC runs as an OMVS user. When you add a userID for the started task, make sure,
that an OMVS segment is defined for it. Also make sure, that the directory for this OMVS
user is read/write enabled. If both actions are not accomplished, unpredictable results
may occur. CSC only will only give an error message, that it cannot connect to the
library server, in this case VACS. You may check with your security administrator for
assistance.
●
CSC uses TCP/IP services. The function PORTMAP is used. Please check, that the
PORTMAP started task is automatically started by TCP/IP and port 111 for TCP and
UDP is enabled. For more information, please refer also to the chapter Firewall:
section “CentricStor NCS/CSC network attachment via firewall in a z/OS environment”
on page 92.
●
One started task of CSC manages one and only one CentricStor. If you are using
multiple CentricStor systems or a remote SUN/STK library, define the appropriate
number of CSC subsystems. Remember to adjust the LIBUNIT statement accordingly.
●
CSC and HSC both use the functionality of the Storage Management Component
(SMC). There is only one SMC started task per z/OS image, independent from the
number of CSCs.
●
If you are running JES3, please specify ALLOCDEF DEFER(ON)in your SMC startup
commands to enable message processing for scratch subpooling.
●
Whereas the SMC subsystem name and the started task name have no dependency
on each other, please note, that the first four digits of the started task name of the CSC
must match the CSC subsystem name.
●
With NCS 6.1 the processing of TAPEREQ statements was moved from CSC and HSC
to SMC. In a mixed environment the correct tailoring of the TAPEREQ statements is
essential. FSC recommends, to use
TAPEREQ VOLT(N) ESOT(CS_Esoteric) MED(STD) REC(36TRACK)
as the very last statement.
●
78
With CSC and attachment type ACSLS, which is used for CentricStor, also the
parameter SUBPOOL for scratch subpooling is not supported with TAPEREQ. Instead,
the SMC user exit 01 has to be used. Please refer the the chapter “Scratch Subpooling”
on page 85.
CentricStor on z/OS
4.5.1.3
Virtual Drives Coordinates
Virtual drive coordinates are defined during setup of CentricStor Virtual Library Services.
These coordinates must be mapped in the UNITMAP statement of the CSC parameters.
The coordinates represent a SUN/STK ACS and contain: ACS-ID, LSM-ID, PANEL-ID and
DRIVE-SLOT. As all CentricStor virtual volumes own the same virtual slot, which is
01:01:01:01, a scheme can be set up to avoid virtual pass-thrus and to perform drive
allocation across ICPs.
All virtual drives of a logical control unit are spread across all LSMs, i.e. drive with
subschannel address 00 is mapped to LSM x'01', 01 to LSM x'02' and so on until 0F is
mapped to LSM x'10'.
PANEL-ID starts with '01' and represents a drive wall. One drive panel can contain up to
4 drives. So if your configuration contains more than 64 virtual drives addresses, PANELID '02' will represent drives x'40' to x'7F' or a new range from x'00' to x'3F'. The
drive location within a panel starts with 0. In case of 192 logical drives a third panel is
needed. 256 logical drives occupy four panels.
The diagramm shows examples of some mappings to demonstrate the logic. The drive
location within a drive panel is not shown. Drives of ICP0 are are mapped to position 0, ICP1
to position 1, IPC2 to position 2 and ICP3 to position 3.
Logical Drive Mapping Scheme– 4 ICP / 32 LD each ICP
ICP2
ICP0
1C00
1C01
1C02
~
1C0F
1D00 1D01
~
1C1F
1D10 1D11
1D02
1D12
ICP3
ICP1
~
1D0F
1E00
1E01
1E02
~
~
1D1F
1E10
1E11
1E12
~
1E0F
1F00
1F01
1F02
~
1F0F
1E1F
1F10
1F11
1F12
~
1F1F
1C01
1C10
1C11
01
1C12
02
LSM01
X'01'
01
02
LSM02
X'02'
01
02
LSM03
X'03'
Drive Panel
01
02
LSM16
X'10'
The following two tables show the sample configuration from above with 4 ICPs and 32
logical drives each. It is assumed that it is a split configuration with ICP0 and ICP2 on one
site and ICP1 and ICP3 on the second site. This config distributes the mounts to both sites.
The tables also show the CUADD value of each address range that is used for the HCD
process.
79
80
CentricStor on z/OS
CentricStor on z/OS
81
CentricStor on z/OS
The next example shows 2 ICPs with 64 logical drives each. In this case the logical drives
of a single ICP are distributed to two virtual drive panels. Within a drive panel the positions
of logical drives of ICP0 and ICP1 are interleaved. Position 0 and 2 are mapped to ICP0 and
position 1 and 3 to ICP1:
Logical Drive Mapping Scheme – 2 ICP / 64LD each ICP
ICP0
1C00
1C01
1C02
ICP1
~
1C0F
1C10 1C11
1C12
~
1C1F
1D00
1D01
1D02
~
1D0F
1D10
1D11
1D12
~
1D1F
~
1C2F
1C30 1C31
1C32
~
1C3F
1D20
1D21
1D22
~
1D2F
1D30 1D31
1D32
~
1D3F
1C01
1C20
1C21
01
1C22
02
LSM01
X'01'
01
02
LSM02
X'02'
01
02
LSM03
X'03'
Drive Panel
01
02
LSM16
X'10'
The following two tables show the sample configuration from above with 2 ICPs and 64
logical drives each.
82
CentricStor on z/OS
83
84
CentricStor on z/OS
CentricStor on z/OS
4.5.1.4
Scratch Subpooling
With NCS/CSC, the scratch subpooling feature of the tape management software is used.
Please refer also to the section, that corresponds to your tape management software.
To process the changed or additional mount messages of the tape management software,
FSC delivers SMC user exits dependent on the software used: RMM, CA-1, TLMS and
Control-T. The exits themselve are static source code, that has to be compiled and
linkedited together with a user maintained table. This table is common for CA-1, TLMS and
Control-T. A separate version is available for RMM. The reason is the length of the scratch
pool name, which is 13 digits for CA-1, TLMS and Control-T. For RMM it is eight digits and
the exit also allows to define a default pool ID. The table itself is included into the source
code by using the assembler copy statement. As SUN/STK has announced that CSC format
exit will not longer be supported in a future release of NCS, all delivered source code is HSC
format.
Example for CA-1, TLMS and Control-T - Member SPTABCT
********************************** ************************************
*
*
THIS TABLE IS USED TO MAP TAPE MANAGEMENT SCRATCH SUBPOOL
*
NAMES TO A CSC POOLID. POOLIDS 1-254 ARE AVAILABLE EXCEPT
*
POOLID 238 WHICH IS X'EE'. X'EE' IS USED FOR ERROR INDICATION.
*
IN CASE YOU NEED POOLID 238, CHANGE THE SOURCE CODE OF THE
*
EXIT TO REFLECT YOUR ERROR POOLID.
*
*
THIS TABLE IS VALID FOR CA-1, TLMS AND CONTROL-T
*
*
FOR RMM USE TABLE SPTABRMM
*
*
*
ESOTERIC NAME FOR CENTRICSTOR
*
CSESO
DC
CL8'CSTOR'
<<<--- SPECIFY CENTRICSTOR ESOTERIC
*
*######################################################################
*#
TABLE TO MATCH SUBPOOL NAMES TO SCRATCH SUBPOOL NUMBER
*#
STRUCTURE: 13 BYTES SP NAME (CT DEFINITION)
*#
1 BYTE SCRATCH SUBPOOL NUMBER (DECIMAL)
*######################################################################
***********************************************************************
TABSP
DS
0H
TABSPE
DC
CL13'DUMMY.POOL
'
TABSPP
DC
X'FF'
TABSPEL EQU
*-TABSP
DEFINE TABLE ENTRY LENGTH
DC
CL13'ABCDPOOL123 ',AL1(01)
DC
CL13'SCRATCH.PROD ',AL1(02)
85
CentricStor on z/OS
DC
CL13'PROD.POOL
',AL1(03)
DC
CL13'A000.POOL
',AL1(04)
DC
CL13'ANOTHER.PROD ',AL1(05)
DC
CL13'B111.POOL
',AL1(06)
DC
CL13'C222.POOL
',AL1(08)
***********************************************************************
*######################################################################
*#
ADDITIONAL POOL-IDS ARE TO BE DEFINED BEFORE THIS STMNT
*######################################################################
***********************************************************************
TABSPEND EQU
*
DEFINE END OF TAB
Tailor the table member SPTABCT or SPTABRMM according to your needs. If you plan to
use this exit, note that scratch subpool 238 (hex 'EE') is used as an error indication in case
a subpool name could not be matched. If you want to use it for other purposes, please
change the source of the exit 01 accordingly.
The pool IDs are coded in decimal. For CSESO specify the esoteric name, that you also
used in the CSCPARMs under the LIBDEV statement. The esoteric name is used by
EDTINFO macro services within the exit to mapped all CentricStor devices. This mecanism
secures, that configuration changes concerning the logical drive range are applied automatically.
i
For CA1 and TLMS please make sure, that the additional mount messages TMSxxx
and CTSxxx are not suppressed by MPF.
This is the table member SPTABRMM for the RMM version of the user exit:
********************************** ************************************
*
THESE TABLES ARE USED TO MAP TAPE MANAGEMENT SCRATCH SUBPOOL
*
NAMES TO A CSC POOLID. POOLIDS 1-254 ARE AVAILABLE EXCEPT
*
POOLID 238 WHICH IS X'EE'. X'EE' IS USED FOR ERROR INDICATION.
*
IN CASE YOU NEED POOLID 238, CHANGE THE SOURCE CODE OF THE
*
EXIT TO REFLECT YOUR ERROR POOLID.
*
*
THE FIRST TABLE DEFINES DEFAULT POOLS BASED ON LPAR NAME
*
IF YOU DO NOT WANT DEFAULTS, SPECIFY AN INVALID LPAR NAME
*
WITH THE ERROR POOL INDICATION OF X'EE' OR DECIMAL 238
*
*
THE SECOND TABLE REFERENCES THE STORAGE GROUP AND THE
*
CORRESPONDING POOLID.
*
*
THIS MEMBER IS VALID FOR RMM
*
*
FOR CA-1, TLMS AND CONTROL-T USE TABLE SPTABCT
*
*
ESOTERIC NAME FOR CENTRICSTOR
*
CSTORUNT DC
CL8'CSTOR'
<<<< CENTRICSTOR ESOTERIC ##############
86
CentricStor on z/OS
*
*######################################################################
*#
TABLE TO MATCH LPAR NAMES TO SCRATCH SUBPOOL NUMBER
*#
STRUCTURE: 4 BYTES LPAR NAME
*#
*######################################################################
***********************************************************************
SYSSP
DS
0H
SYSSPE
DC
XL4'FFFFFFFF'
SYSSPP
DC
X'FF'
SYSSPEL EQU
*-SYSSP
DC
CL4'SYS1',AL1(01)
DC
CL4'MVSA',AL1(02)
DC
CL4'OTTO',AL1(03)
DC
CL4'STAN',AL1(32)
***********************************************************************
*######################################################################
*#
ADDITIONAL SMFIDS ARE TO BE DEFINED BEFORE THIS STMNT
*######################################################################
***********************************************************************
SYSSPEND EQU
*
DEFINE END OF TAB
***********************************************************************
*######################################################################
*#
TABLE TO MATCH SUBPOOL NAMES TO SCRATCH SUBPOOL NUMBER
*#
STRUCTURE: 8 BYTES SP NAME (RMM DEFINITION)
*#
*######################################################################
***********************************************************************
TABSP
DS
0H
TABSPE
DC
CL8'DUMMY '
TABSPP
DC
X'FF'
TABSPEL EQU
*-TABSP
DC
CL08'PRODPOOL',AL1(11)
DC
CL08'TESTPOOL',AL1(12)
DC
CL08'NEWPOOL ',AL1(13)
DC
CL08'SCRATCH1',AL1(14)
DC
CL08'SGTAPE ',AL1(15)
DC
CL08'DAVID
',AL1(16)
DC
CL08'PETER
',AL1(17)
DC
CL08'FRANK
',AL1(18)
DC
CL08'SUNNY
',AL1(19)
***********************************************************************
*######################################################################
*#
ADDITIONAL POOLNAMES ARE TO BE DEFINED BEFORE THIS STMNT
*######################################################################
***********************************************************************
TABSPEND EQU
*
DEFINE END OF TAB
***********************************************************************
87
CentricStor on z/OS
The RMM version enables you to define default pool IDs by LPAR name. You may use the
same pool ID for multiple LPARs that share a RMM CDS. Using the default table allows you
to use the same storage group for different sysplexes. However, you cannot mix pool
assignment using SMS and Non-SMS.
Once you have completed the table SPTABCT or SPTABRMM, compile and linkedit the exit
to the NCS/SMC load library (SMCLINK) as follows.
//ASMUX01 JOB (ACCT#),'CSC EXIT',CLASS=A,MSGCLASS=X,
//
NOTIFY=&SYSUID
//ASM
EXEC PGM=ASMA90,PARM=OBJ
//SYSPRINT DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSLIB
DD DISP=SHR,DSN=SYS1.MACLIB
//
DD DISP=SHR,DSN=SYS1.MODGEN
//
DD DISP=SHR,DSN=SMP.NCS610.SMC6100.SMCMAC <<<<< Check
//
DD DISP=SHR,DSN=your.exit.sourcelib
<<<<< Change
//SYSUT1
DD UNIT=SYSDA,SPACE=(CYL,(3,1))
//SYSPUNCH DD DUMMY
//SYSLIN
DD DISP=(,PASS),DSN=&&OBJ,UNIT=3390,SPACE=(CYL,(1,1))
//SYSIN
DD DISP=SHR,DSN= your.exit.sourcelib(yourexit) <<<<<<<
//*
//LKED
EXEC PGM=IEWL,PARM='LIST,XREF,RENT,REUS,REFR',COND=(0,NE)
//SYSLMOD DD DISP=SHR,DSN=smc.smclink(SLSUX01)
<<<<< Change
//SYSUT1
DD UNIT=SYSDA,SPACE=(CYL,(3,1))
//SYSLIN
DD DISP=(OLD,DELETE),DSN=&&OBJ
For yourexit specify the name of the exit, that applies to your tape management software.
Tape Management Exit Name
DFSMSrmm
UX01RMM
CA-1 and TLMS
UX01CA1
Control-T
UX01CTLT
When you setup the SMC startup commands, please include the following command:
Ê
UEXIT 01 NAME(SLSUX01) FORMAT(HSC) LOAD
If you need to change the exit table, you can enable the new version via command. On the
MVS console enter:
Ê
F SMC,UEXIT 01 NAME(SLSUX01) FORMAT(HSC) LOAD
The command assumes, that the started task name is SMC.
88
CentricStor on z/OS
4.5.1.5
Scratch Synchronisation
Scratch mounting in a NCS/CSC environment is performed under the control of the library
server. The library server selects a volume to be mounted on a nonspecific request. In case
of CentricStor, the library server is VACS. VACS keeps track about the status of the volumes
and groups these in subpools (see section “Scratch Subpooling” on page 85). The scratch
status of volumes in VACS has to be kept in sync with the tape management system.
The synchronisation normally takes places once a day during the daily maintenance job of
the tape management system. In case of NCS/CSC it is an asysnchronous process. The
CSC utility program SCUCONDB reads the contents of the tape management database
and creates scratch commands that are sent via the network to VACS. You can do an incremental or a full synchronisation. The started task for CSC must be up and running.
i
SCSCONDB supports RMM, CA-1 and TLMS. To synchronise Control-T with
VACS, FSC supplies a REXX procedure, that creates scratch commands out of a
scratch report. Please refer to the corresponding documentation within this chapter.
As an effect of the asynchronous process, it may happen that a volume is mounted by VACS
that is not scratch in the tape management database. In this case, the tape management
will reject the usage of the affected volume and request a remount. VACS will automate the
remount and processing continues.
i
Due to the asynchronous process, CentricStor option Erase Scratch Volume in the
LVG options may be an issue. Make sure, that you only run incremental scratch
update or stop tape processing during full synchronisation.
The CSC utility will check the complete tape management database and create scratch
commands for every scratch volume in case of a full synchronisation. When you use the
EXEC parm TODAY, it will perform an incremental synchronisation and create scratch
statement for all volumes that became scratch today. The scratch command file will
therefore contain volumes that are not known by VACS. The resulting warning messages
may be ignored.
If your installation uses multiple CSC started tasks, the output of SCSCONDB cannot be
used as it is. The produced scratch commands do not contain the parameter SUBSYS. By
default the commands are then sent to the first CSC subsystem. Therefore the subsystem
parameter must be added. FSC supplies a REXX procedure, that adds the SUBSYS
parameter and also selects only volumes out of a predefined volume range. Using this
procedure also avoids unnecessary network traffic during the synchronisation. The REXX
procedure SCRCSC uses positional parameters from the EXEC-PARM-statement. These
are:
1. Name of the procedure itself
2. Name of the CSC subsystem that should be synchronised
3. Volser range to select valid LVs
For each volser range use a separate step.
89
CentricStor on z/OS
The following example shows the complete scratch synchronisation process.
//*
//*CONDB
//*CONDB
//STEPLIB
//
//SCSTMS
//SLSTMS
//SCSPRINT
//SCSSOUT
//
//*
//SELECT1
//
//SYSTSPRT
//SYSPROC
//SYSTSIN
//SCRIN
//SCROUT
//
//*
//SETSCR1
//STEPLIB
//SCSIN
//SYSPRINT
//SCSPRINT
//*
//
EXEC PGM=SCUCONDB,PARM='TMS,SCRPOOL(SL),TODAY' << Incremental
EXEC PGM=SCUCONDB,PARM='TMS,SCRPOOL(SL),00001' << Full Sync
DD DISP=SHR,DSN=your.SCSLINK
DD DISP=SHR,DSN=your.SLULINK
DD DISP=SHR,DSN=your.TMC
DD DUMMY
DD SYSOUT=*
DD DISP=(,PASS),DSN=&&TEMPIN,SPACE=(TRK,(15,15),RLSE),
LRECL=72,BLKSIZE=0,RECFM=FB,DSORG=PS
EXEC PGM=IKJEFT1B,DYNAMNBR=90,
PARM='SCRCSC CSC1 A00000-A99999'
DD SYSOUT=*
DD DSN=your.REXX.library,DISP=SHR
DD DUMMY
DD DSN=&&TEMPIN,DISP=(OLD,DELETE)
DD DSN=&&TEMPOUT,DISP=(,PASS,DELETE),SPACE=(TRK,(5,5),RLSE),
EXEC PGM=SCUADMIN
DD DISP=(OLD,DELETE),DSN=&&TEMPOUT
DD SYSOUT=*
DD SYSOUT=*
The EXEC parm TMS represents CA-1 as the installed tape management software. For
TLMS specify TLMS; for RMM specify RMM. Please select the appropriate synchronisation
method (incremental or full). You may use incremental sync on a daily basis and run full
sync monthly.
90
CentricStor on z/OS
Scratch synchronisation with Control-T
The SCUCONDB utility does not support Control-T. Scratch synchronisation is accomplished using a scratch list of Control-T, that can be created using CTTRPT/CTTRFSCR.
The produced report will look like this:
BMC SOFTWARE, INC.
CONTROL-M/Tape REPORT (REL 6.1.14)
DATE 20/06/2007 TIME 15.36
FULL LIST OF VOLUMES IN A SCRATCH STATUS
----------------------------------------
VOLSER
MEDIA TYPE
POOL NAME
DATASET NAME
-----D00000
D00001
D00002
D00003
D00004
D00005
D00006
D00007
D00008
D00009
D00010
D00011
D00012
D00013
D00014
D00015
D00016
D00017
D00018
D00019
D00020
WD0002
WD0003
WD0005
WD0007
.........
---------CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CS2GB
CART
CART
CART
CART
--------------LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
LDDEF
C9840
C9840
C9840
C9840
-------------------------------------------**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
**.SCRATCHED.VOLUME
HSM.BCDS.BACKUP.V0001157
SYSTXRH.HSMDUMP.#020301
SMGP.GROUP.T18.CART
HSM.BACKTAPE.DATASET
VOLUME
EXPIRATION
DATE
-----------
09 Mar 2001
26 Jun 2001
01 Jan 1989
PAGE
1
LAST ACCESS
DATE
LOCATION
----------20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
20 Jun 2007
26 Apr 2007
02 Mar 2001
19 Jun 2001
16 Mar 2001
-------MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
MAINLIB
The scratch report is input to the REXX procedure SCRCNTLT that is provided by FSC.
Please refer to the section “User Exits and Scripts” on page 150 for details. The provided
REXX script selects all scratch volumes from the report, which is then a full synchronisation.
If you want to run an incremental synchronisation, restrict the scratch report to volumes that
became scratch today. Please consult the Control-T manuals for more information.
The complete scratch synchronisation process for a Control-T environment is shown below:
//jobcard JOB (ACCT#),'SCRSELECT',CLASS=c,MSGCLASS=x,
//
NOTIFY=&SYSUID
//*
//
JCLLIB ORDER=your.BMC.IOA.PROCLIB
//
INCLUDE MEMBER=IOASET
//*
//* PRODUCE A FULL SCRATCH REPORT
//*
//FSCRREP EXEC CTTRPT
//SYSIN
DD DISP=SHR,DSN=your.BMC.IOA.SAMPLE(CTTRFSCR)
//REPOUT
DD DSN=&&REPORT,
//
DISP=(,PASS),DSN=&&TEMPIN,SPACE=(TRK,(15,15),RLSE),
//
//*
91
//IKJSPF
//
//SYSTSPRT
//SYSPROC
//SYSTSIN
//SCRIN
//SCROUT
//
//
//
//*
//SETSCR1
//STEPLIB
//SCSIN
//SYSPRINT
//SCSPRINT
//*
CentricStor on z/OS
EXEC PGM=IKJEFT1B,DYNAMNBR=90,
PARM='SCRCNTLT &cscname &medianame &startvol-&endvol'
DD SYSOUT=*
DD DSN=your.exec.lib,DISP=SHR
DD DUMMY
DD DSN=&&REPORT,DISP=(OLD,DELETE)
DD DSN=&&SCRCMD,DISP=(,PASS,DELETE),
RECFM=FB,LRECL=72,BLKSIZE=0,
SPACE=(TRK,(5,1),RLSE),
UNIT=SYSDA
EXEC PGM=SCUADMIN
DD DISP=(OLD,DELETE),DSN=&&SCRCMD
DD SYSOUT=*
DD SYSOUT=*
The REXX procedure SCRCNTLT uses positional parameters from the EXEC-PARMstatement. These are:
1.
2.
3.
4.
Name of the procedure itself
Name of the CSC subsystem that should be synchronised
Media name that was used during initialisation.
Volser range to select valid LVs
For each media name and volser range use a separate step.
4.5.1.6
CentricStor NCS/CSC network attachment via firewall in a z/OS environment
In a z/OS system environment, that attaches CentricStor via a firewall and CSC, the
following considerations must be taken:
CentricStor incoming ports can be fixed, using the VACS configuration. Please refer to the
CentricStor documentation Service Manual GUI Module and the StorageTek ACSLS
documentation chapter G.
Mainframe incoming ports cannot be fixed within CSC. Therefore TCP/IP parameters can
be used, in case, no other application uses dynamic UDP high ports. If this is the case,
all UDP high ports should be reserved and the incoming port(s) for CSC should be
assigned. One port is needed for each CSC started task. Assume, that port 50099 and
50199 are used as incoming ports for two CSCs:
92
CentricStor on z/OS
The TCP/IP parameters should include:
PORT 50099 UDP CSC1
PORT 50199 UDP CSC2
PORTRANGE 1024 49075 UDP RESERVED
i
The syntax is misleading, as PORTRANGE uses a starting port number and a
count of ports. So you have to do some calculations, instead of just specifying
the range.
Example
PORTRANGE 1024 49075 reserves 1024 to 50098. As 49075 is a count, and port 1024
is included, 1 has to be subtracted from the calculation: 1024 + 49095 - 1 = 50098.
Also make sure, that the highest port 65535 is reserved: 50200 + 15336 - 1 = 65535.
The parameters can edited into a member of the TCP/IP parmlib and then be activated
dynamically using the OBEY command:
VARY TCPIP,,O,TCPIP.TCPPARMS(&member)
If using the dynamic activation, make sure, that the original TCP/IP parms are updated and
reflect the change.
The portrange statements result, that only MF incoming ports 50099 and 50199 remain
open. However there is no guarantee, that CSC1 will use 50099 and CSC2 will use 50199.
It may be dependant on the startup sequence. Also after stopping and starting CSC the
usage may be exchanged.
So additional firewall setup is needed for direction CentricStor to mainframe:
CS1 and CS2 must be granted to use both ports 50099 and 50199 for entering MF, instead
of assigning one exclusivly each CS.
After the change has been applied, a TCP/IP trace should be taken for verification.
93
4.5.1.7
CentricStor on z/OS
CSC Troubleshooting
This section should give help with common problems that may occurs during setup of the
CSC configuration
CSC does not start
1. When starting the CSC started task, make sure, that the messages
SCS3247I Network interface state active
SCS0880I Recovery request successful; the LCS is reconciled to the
current MVS/CSC state
SCS0517I MVS/CSC subsystem CSC1 initialization complete
show up. Instead you may see:
SCS3246I Network interface failure, attempting recovery
There are several reasons why the network interface does not get active:
●
TCPIP portmap service is needed to run CSC. Is the PORTMAP started task
active?
●
Are there multiple TCPIP started task on the system and does the CSC parameter
set reference the correct STC?
●
Is the correct IP address specified in the CSC parameters?
●
Is an OMVS segment defined for the userID of the CSC task?
●
Is the OMVS user directory of CSC write enabled?
●
Is there a firewall between z/OS and CentricStor and are ports blocked?
2. When starting the CSC started task the following the messages appear:
SCS0661E No cartridge-type UCB for specified LIBUNIT 6410
SCS0665I SCSPARM UNITMAP entry for device 6410 ignored
The messages may report multiple virtual drive addresses. Make sure, that the CSC
parameters are coded correctly. Check LIBUNIT and UNITMAP statements. If the
messages appear for drives with subchannel ID 10-16, make sure, that the coordinates
in UNITMAP are coded in hex notation.
3. When starting the CSC started task the following the messages appear:
SCS0726E ACS esoteric CSTEST supplied on SCSPARM LIBDEV parameter for
ACS 01 contains devices in ACS 09 of UNITMAP mappings
The LIBUNIT parameter is not coded correctly. Check that the comma count is correct
and the esoteric name for CentricStor logical drives matches the configuration.
94
CentricStor on z/OS
Scratch volumes are not mounted
CSC shows the following message:
*02 #SCS0918D Mount of SCRTCH on drive 6301 failed, reason code: 0105 NO
SCRATCH TAPES; reply "C"ancel or "R"etry
Reasons:
●
The required user exit 01 is not active.
Check with F SMC,UEXIT LIST command.
●
The requested subpool does not contain any scratch volumes.
Check with VACS command q pool all (refer section “VACS Interface” on page 69)
●
Subpool not assigned by exit.
Enable CSC log and check log messages for the pool ID that was assigned. If subpool
0 was used, check user exit table for errors; else check esoteric name for CentricStor
logical drives that is also defined within this table (see section “Scratch Subpooling” on
page 85; label CSESO for CA1 version and CSTORUNT for RMM version).
4.5.2 CSMVS
The CSMVS software was especially developped fo CentricStor and is documented under:
CSMVS Installation & Administrator Guide.
This chapter only gives additional information on the software environment to avoid redundancies to the original document.
CSMVS supports DFSMSrmm and CA1 as tapemanagement software. For integration of
scratch subpooling, refer to the corresponding chapter in this document:
–
–
section “DFSMSrmm considerations” on page 126 for RMM and
section “CA1 and TLMS considerations” on page 140 for CA1.
This is the prefered method to implenet scratch subpooling.
In both cases (RMM and CA1), the VPOOLxx statement in CSMVS parmlib member
CSPARMST is used, to map the pool name to the VACS pool ID.
The documentation also mentions differences for installations with unique and not-unique
esoterics with CentricStor. Keep in mind, that normally read mounts are allocated via the
OS catalog, which is related to a device generic. In this case the not-unique esoterics installation procedure applies.
95
CentricStor on z/OS
The following table of the CSMVS Installation & Administration Guide should be observed. The
common installation procedure is marked in green.
4.5.2.1
JES Type ESOTERIC
TMS
Required
Modules
Sub-System
Init
MPF
JES2
UNIQUE
RMM WITH VLPOOL
CSMVS
MTCSRMTL
NO
JES2
UNIQUE
RMM NO VLPOOL
CSMVS
CSMSGXIT
YES
JES2
UNIQUE
CA1
CSMVS
CSTMSXIT
YES
JES2
NOTUNIQUE
RMM WITH VLPOOL
CSMVS
MTCSRMMI
NO
JES2
NOTUNIQUE
RMM NO VLPOOL
CSMVS
CSMSGXIT
MTCSINIT
YES
JES2
NOTUNIQUE
CA1
CSMVS
CSTMSXIT
MTCSINIT
YES
JES3
SPECIAL
RMM WITH VLPOOL
CSMVS
MTCSRMJ3
NO
JES3
SPECIAL
RMM NO VLPOOL
CSMVS
CSMSGXIT
YES
JES3
SPECIAL
CA1
CSMVS
CSTMSXIT
YES
Sample configuration for CentricStor, LMS/CSMVS with FS5193 gateway
ESCON/FICON connections to the drives
z/OS
CentricStor
LMS/CSMVS
96
TCP/IP
FS5193
Gateway
VACS
CentricStor on z/OS
–
–
–
VTA1000 with ICP0 and ICP1, each with 32 logical drives
Tape drives in the z/OS generated on 8000-803F
Logical drives in CentricStor (LibDevName)
97
CentricStor on z/OS
Example Definition file CSPARM in the z/OS for LMS/CSMVS
MODE=TCPIP
MTU=8000
NUMMTUS=64
ATLNAME=SERV1
DEFPOOL=02
VPOOL00=SQ0
VPOOL01=SQ1
VPOOL02=SQ
TCPIPADR=172.25.25.233
TCPPORT=1301
ALTCDEV=172.25.25.234
98
CentricStor on z/OS
Definition of the tape drives in the FS5193 gateway in /etc/5193gw.cfg
#----------------------------------------------------------------------# FS5193 Gateway Manager VACS Drives Parameter
# This parameter specify the conversion table between LMS/Client known
# drives and VACS Server drives.
#----------------------------------------------------------------------# FS5193 Gateway Drives (max 2048 Drives)
!% 5193gw_drives
# DRIVE NAME: 4 hexadecimal chars (for VM/VSE, should be device number)
# ACS, LSM, PANEL, TRANSPORT: in decimal
# DRIVE NAME ACS LSM PANEL TRANSPORT VACS
8000
8001
8002
8003
8004
8005
8006
8007
8008
8009
800A
800B
800C
800D
800E
800F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
801A
801B
801C
801D
801E
801F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
99
CentricStor on z/OS
# ICP1
4.5.2.2
8020
8021
8022
8023
8024
8025
8026
8027
8028
8029
802A
802B
802C
802D
802E
802F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
803A
803B
803C
803D
803E
803F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
LOAD balancing with LMS/CSMVS
To achieve LOAD balancing via the ICPs, the LMS/CSMVS must be notified of which tape
devices (device number) are located on which ICPs.
Example MTCSICP macro in MTCSACT module
MTCSACT
100
CSECT
MTCSICP ICP=0,LOW=8000,NUM=32,DSN=NO,TYPE=INITIAL
MTCSICP ICP=1,LOW=8020,NUM=32
MTCSDSN
END
CentricStor on z/OS
4.5.2.3
Scratch alignment between RMM/CA-1 and CentricStor for LMS/CSMVS
Scratch alignment is implemented for LMS/CSMVS with RMM and CA-1 via an exit. For
each tape which returns to the scratch pool, the pool is modified in such a way that a console message in the following format is generated:
CSC001A <volser>
With this implementation scratch alignment takes place synchronously to RMM/CA-1.
4.5.2.4
Setting manual scratch for CentricStor from the host
It is recommended that the tapes should be set to scratch for CentricStor from the host instead of doing this in CentricStor using the cmd_proc program. For this purpose, the first
time scratch tapes are labeled with the tape label program of TMS (RMM or CA-1), the
CSMSCRT program is used in a second step.
JCL example
//********************************************************************
//*
JOB FOR MANUALLY SET VOLUMES TO SCRATCH IN CS
//********************************************************************
//COPY
EXEC PGM=CSMSCRT
//SYSIN
DD *
SQ1810
SQ1814
SQ1815
//
101
CentricStor on z/OS
4.5.3 HACC
4.5.3.1
Overview
The HACC is a software package to drive Quantum/ADIC libraries in a z/OS or OS/390
environment. It also can be used to control a CentricStor. If multiple CentricStors are used,
a separate instance of the HACC must be started. The HACC communicates with
CentricStor via the VAMU feature, which emulates the Grau AMU of a physical library.
CentricStor can run multiple VAMU instances which use a dedicated pair of TCP/IP ports.
Each LPAR running a primary HACC must use a separate VAMU to ensure propper
functioning. Special attention must be made, if multiple LPARs share a tape management
database. In this case, one LPAR will be used to run a primary HACC, whereas the other
LPARs run secondary HACCs. Up to 7 secondary HACCs can be set up. Please refer to the
configuration section for more details.
Control Path of a CentricStor Configuration with HACC
SYSA
HACC primary
TCP/IP
HACC
Archive
SYSB
SYST
Tapemanagement
Tapemanagement
HACC secondary
HACC primary
TMC
Tapemanagement
TMC
TCP/IP
Exchange
Log
Unit Log
HACC
Archive
Unit Log
Comments:
SYSA and SYSB
share a Tape
Management
Database or Control
Dataset (TMC)
SYST has a seperate
TMC
SYSA connects to
VAMU1 and SYST
connects to VAMU2
of the VLP
CentricStor
VLP
SVLP
VAMU1
VAMU1
VAMU2
VAMU2
The primary HACC performs mount automation by analysing mount related messages and
sends commands via the VAMU interface.
Allocation influencing is not performed by the HACC directly. For scratch mounts and
specific mounts, that are not result of a catalog search (e.g. VOL=SER=anyvol in JCL), the
correct esoteric name for the CentricStor drives must be coded. For volumes that are
102
CentricStor on z/OS
mounted based on a catalog search, a catalog user exit is used to modify the unit allocation.
Please refer to the corresponding section in the HACC documentation that explains the
installation of LKSVC26.
Scratch mounting is controlled by the HACC itself. The HACC maintains a file called HACC
ARCHIVE. In case of CentricStor, the only purpose of the ARCHIVE is, to register to scratch
or private status of a virtual volume. The HACC selects a scratch volume from the ARCHIVE
and issues then a specific mount via VAMU. The size of the ARCHIVE is dependend on the
number of virtual volumes that are defined.
Please note, that CSC and CSMVS direct VACS to mount any scratch volume out of a
scratch pool. This is one of the main differences between CSC/CSMVS and HACC
functionality.
4.5.3.2
Installation and Customisation
HACC is installed via the SMP/E program. The installation procedure is explained in the
HACC Installation and Customization Guide.
The following table is an extract of the HACC Installation and Customization Guide. Additional
information is provided if necessary.
1. Satisfy installation preconditions
2. Define ALIASes
3. PARMLIB definitions
4. Install MVS allocation influencing (when necessary)
This step is important to enable allocation influencing for cataloged datasets.
5. Load the installation tape (SMP/E, NON-SMP/E)
6. Create HCC work files
If you share a tape management database among multiple LPARs, you must define an
exchange log file for every secondary HACC (client). The primary HACC checks this file
for outstanding mounts. Additionally a unit log file is used to trap the status of the virtual
drives.
7. Modify the search algorithm for HACPARM (optional)
8. Create a user interface under ISPF
The user interface under ISPF is important, because it is used to initialise the HACC
ARCHIVE. Please refer to the HACC ISPF User Guide.
9. Definitions in HACPARM1 member
See the parameter example in section “HACPARM1 example” on page 105. Short
explainations of CentricStor most important parameters are given also.
103
CentricStor on z/OS
10. Generate the HCC archive (HAA)
The ARCHIVE is a VSAM cluster to track the scratch status of the virtual volumes.
Please refer also to the definitions of the virtual robot (racks) that must match the count
of the virtual volume. For every virtual volume you need a virtual slot. The creation of
the ARCHIVE initialisation is shown in section “HACC ARCHIVE initialisation” on
page 116.
11. Create the HCC start procedure
The start procedure of a primary HACC looks like this:
//HACC
//
//
//
//
//
//
//
//
//
//HACCPROC
//
//
//
//
//
//
//
//
//
//
//
//
//
//STEPLIB
//HACCPARM
PROC SYS=PRI,
FMTU=N,
FEX=,
HOT=Y,
TEST=N,
SSI=N,
SIM=N,
SUP=N,
HID=H1,
A1ID=A1
EXEC PGM=ZHC00100,
TIME=1440,
DPRTY=(14,7),
<--- HIGHER AS BATCH
REGION=4M,
PARM=('SYS=&SYS',
'FMTU=&FMTU',
'FEX=(&FEX)',
<--- ACTIVATE IF NEEDED
'HOT=&HOT',
'TEST=&TEST',
'SSI=&SSI',
'SIM=&SIM',
'SUP=&SUP',
'HID=&HID',
'A1ID=&A1ID')
DD DSN=HACC.ZHC300.LOAD,DISP=SHR
DD DSN=SYS1.PARMLIB(HACPARM1),DISP=SHR
For the first start after an IPL of the system that hosts the primary HACC, you should
specify FMTU=Y and FEX=Y during startup of the HACC. Unit log file and Exchange
log files are formatted. For a secondary HACC specify SYS=SECx. The x represents
the suffix of the exchange log that this system should use.
For more information, refer to the HACC documentation.
12. Adapt scratch tape processing
See section “HACC Scratch Synchronisation Process” on page 125
104
CentricStor on z/OS
13. Check / adapt the communication interface
14. Enable the RACF authorization call (optional)
15. Adapt user exits (optional)
16. Function tests (recommended)
4.5.3.3
HACPARM1 example
PCOMPLX=PROD
SSINAME=HAC1
IN SYS1.PARMLIB(IEFSSN00)
STATISTICS=YES
SYSDEF1=1,VTLS
(1)
SYSTEM 1 WITH ROB 1
*
JES=JES2
JOB ENTRY SUBSYSTEM
ROUTCD=1,3,5,11
ROUTING CODES FOR HACC MESSAGES
LANG=E
MESSAGES IN ENGLISH LANGUAGE
STIMER=01
(2)
CPU EXCHANGE LOG INTERVALL TIMER
*---------------------------------------------------------------------*
*
HACNET HID=HX,LU=XXXXXXXX,LM=YYYYYYYY,LU2=ZZZZZZZZ
*
*
!
!
!
!
*
*
!
!
!
'-2.LUNAME IF XXXXXXXX *
*
!
!
!
IF NOT PARALLEL SESS.*
*
!
!
'-------- MODE NAME FOR SESS. *
*
!
!
WITH HID
*
*
!
'----------------------- 1. LUNAME (ONLY IF
*
*
!
PARALLEL SESSIONS
*
*
'------------------------------ HACC IDENTIFIER
*
*---------------------------------------------------------------------*
HACNET HID=V1,
(3)
NAME OF AMU SYS1
IP=130.10.0.47,
IP-ADDRESS OF PRIMARY
LPORT=9100,
INTERNAL PORT NUMBER FOR HAC
PORT=9055,
PORT NUMBER OF CORRESPONDING AMU
TYPE=PRI
INDICATE: THIS IS PRIMARY AMU
*
*---------------------------------------------------------------------*
*
STANDARD TMS EXIT
*
*---------------------------------------------------------------------*
*
!TLMS!
*
*
!UCC1!
*
*
TMS=!UCV5!,FROMVOL,TOVOL(,NNNNN)
*
*
!SEQF!
!
!
!
*
*
!
!
--- NO.OF SCRATCH TO BE SELECTED *
*
!
---------- HIGHEST VOLSER IN RANGE
*
*
----------------- LOWEST VOLSER IN RANGE
*
*---------------------------------------------------------------------*
*
TMS & TMSEXIT ARE MUTUALLY EXCLUSIVE
*
105
CentricStor on z/OS
*---------------------------------------------------------------------*
TMS=SEQF,A00000,E99999,99999
(4)
*
*---------------------------------------------------------------------*
*
AUTOFREEVOL=YES/NO
*
*---------------------------------------------------------------------*
AUTOFREEVOL=NO
*
*---------------------------------------------------------------------*
*
SCRATCHTAPE ACCESS BY SCRATCHGROUP-ID'S
*
*---------------------------------------------------------------------*
*
VOLGR=FROMVOL,TOVOL,NNN(,S=N),GROUP
*
*
!
!
!
!
!
*
*
!
!
!
!
- SCRATCH-GROUP-ID
*
*
!
!
!
----- ABBA SYSTEM
*
*
!
!
----------- SCR-WARNING-LEVEL (001-999) *
*
!
---------------- HIGHEST VOLSER IN RANGE
*
*
------------------------ LOWEST VOLSER IN RANGE
*
*---------------------------------------------------------------------*
VOLGR=A00000,A09999,00500,S=1,POOLHB
(5)
VOLGR=B00000,B19999,00500,S=1,POOLHH
VOLGR=C00000,C29999,00500,S=1,POOLAB
VOLGR=D00000,D09999,00500,S=1,SCRTCH
VOLGR=D00000,D09999,00500,S=1,PRIVAT
VOLGR=E00000,E00999,00500,S=1,POOLNC
*---------------------------------------------------------------------*
*
SCRATCHTAPE ACCESS BY GENERIC DSNAME
*
*---------------------------------------------------------------------*
*
DSNGR=FROMVOL,TOVOL,NNNNN,DSNAME
*
*
!
!
!
!
*
*
!
!
!
------ GENERIC DSNAME (1-44)
*
*
!
!
----------- SCR-WARNING-LEVEL (001-999) *
*
!
---------------- HIGHEST VOLSER IN RANGE
*
*
------------------------ LOWEST VOLSER IN RANGE
*
*---------------------------------------------------------------------*
*
*---------------------------------------------------------------------*
*
EJECT SELECTION BY GENERIC DSNAME
*
*---------------------------------------------------------------------*
*
EJDSN=NN,S,DSNAME
*
*
! !
!
*
*
! !
--------- GENERIC DSNAME (1-44)
*
*
! ------------- ABBA-SYSTEM (1-2)
*
*
---------------- EJECT-DEVICE (01-NN)
*
*---------------------------------------------------------------------*
*
*---------------------------------------------------------------------*
*
EJECT SELECTION BY VOLSER-RANGE
*
106
CentricStor on z/OS
*---------------------------------------------------------------------*
*
EJVOL=NN,S,FROMVOL,TOVOL
*
*
! !
!
!
*
*
! !
!
--- HIGHEST VOLSER
*
*
! !
---------- LOWEST VOLSER
*
*
! --------------- ABBA-SYSTEM (1-2)
*
*
------------------ EJECT-DEVICE (01-NN)
*
*---------------------------------------------------------------------*
*
*---------------------------------------------------------------------*
*
TAPE CLEANING ACTIONS
*
*---------------------------------------------------------------------*
*
CLEAN=NN,MMM,TIME
*
*
!
!
!
*
*
!
!
-------- UNIT-CLEANING-TIME + ADDITIONAL
*
*
!
------------ MAX.CLEANING OPERATIONS FOR CL-TAPE
*
*
---------------- CLEANING PERIOD PER UNIT
*
*---------------------------------------------------------------------*
CLEAN=AMU
*
*---------------------------------------------------------------------*
*
VI-EXIT MODULNAME
*
*---------------------------------------------------------------------*
*VIEXIT=HAC23037
*
*---------------------------------------------------------------------*
*
EJ-EXIT MODULNAME
*
*---------------------------------------------------------------------*
*EJEXIT=HAC23038
*
*---------------------------------------------------------------------*
*
MO-EXIT MODULNAME
*
*---------------------------------------------------------------------*
*MOEXIT=HAC23036
*
*---------------------------------------------------------------------*
*
MAX.NO.OF SWAPS OF ALL UNITS (0-2)
*
*---------------------------------------------------------------------*
SWAPLIM=1
1 SWAP ALLOWED
*
*---------------------------------------------------------------------*
*
MSG AUTOREPLY
*
*---------------------------------------------------------------------*
*MSG=XXXXXXD,XXXXXXXXXXX
*
*
!
!
*
*
----------------------- MSG ID
*
*
!
ARC*
*
*
!--------NOAUTOREPLY (AB HSM 2.5.0)
*
107
CentricStor on z/OS
*
!--------AUTOREPLY
*
*
!
IEF238D
*
*
!--------NOAUTOREPLY
*
*
!--------AUTOREPLY
*
*
!
IEF433D
*
*
*
*
!--------REPLY=HOLD
*
*
!--------REPLY=NOHOLD
*
*
!
IEC507D
*
*
*
*
!--------REPLY=U (=USE)
*
*
!--------REPLY=M (=UNLOAD)
*
*
!
IEC510D FILE PROTECT RING
*
*
*
*
!--------REPLY=U (=UNLOAD)
*
*
!--------REPLY=F (=REWIND,SWITCH OFF,REMOUNT)
*
*
!
SCRATCH: KEEP,EJECT,MOUNT SCRATCH
*
*
!
IEC534D CHANGE LABEL
*
*
*
*
!--------REPLY=U (=USE) ONLY FOREIGN MOUNTS
*
*
!--------REPLY=M (=UNLOAD)
*
*
!
IEC701D IEHINIT TAPE TO BE LABELED
*
*
*
*
!--------AUTOREPLY (REPLY=M)
*
*
!--------REPLY=M
*
*---------------------------------------------------------------------*
MSG=ARC*,AUTOREPLY
*
* MSG=IEF238D,AUTOREPLY
MSG=IEF238D,NOAUTOREPLY
*
MSG=IEF433D,REPLY=NOHOLD
*
MSG=IEC507D,REPLY=M
*
MSG=IEC510D,REPLY=F
*
MSG=IEC534D,REPLY=M
*
MSG=IEC701D,REPLY=M
*
108
CentricStor on z/OS
*---------------------------------------------------------------------*
*
3480/3490-ABBA-UNITS
*
*---------------------------------------------------------------------*
* UNIT=CUU,NN,S,R,ALTCUU=CUU(,FPMALOC=DDSSRRPP,DDSSRRPP)
*
*
!
! ! !
!
!
*
*
!
! ! !
!
------- FPMA COORD.RANGE
*
*
!
! ! !
------------------------ ALTERNATE ADDRESS
*
*
!
! ! --------------------------------- ROBOT NO FOR ACCESS *
*
!
! ----------------------------------- ABBA SYSTEM NO
*
*
!
------------------------------------- ABBA-UNIT-ID (01-99)*
*
------------------------------------------ MVS DEVICE ADDRESS *
*----------------------------------------------------------- SYS 1 ---*
UNITNUM=HEX
(6)
*--------------> ESOTERIC-UNIT-NAME: CSTOR
UNIT=0200,01,1,1
(7)
UNIT=0201,02,1,1
UNIT=0202,03,1,1
UNIT=0203,04,1,1
UNIT=0204,05,1,1
UNIT=0205,06,1,1
UNIT=0206,07,1,1
UNIT=0207,08,1,1
UNIT=0208,09,1,1
UNIT=0209,0A,1,1
UNIT=020A,0B,1,1
UNIT=020B,0C,1,1
UNIT=020C,0D,1,1
UNIT=020D,0E,1,1
UNIT=020E,0F,1,1
UNIT=020F,10,1,1
*-------------->
UNIT=0220,11,1,1
UNIT=0221,12,1,1
UNIT=0222,13,1,1
UNIT=0223,14,1,1
UNIT=0224,15,1,1
UNIT=0225,16,1,1
UNIT=0226,17,1,1
UNIT=0227,18,1,1
UNIT=0228,19,1,1
UNIT=0229,1A,1,1
UNIT=022A,1B,1,1
UNIT=022B,1C,1,1
UNIT=022C,1D,1,1
UNIT=022D,1E,1,1
UNIT=022E,1F,1,1
UNIT=022F,20,1,1
*-------------->
109
CentricStor on z/OS
UNIT=0240,41,1,1
UNIT=0241,42,1,1
UNIT=0242,43,1,1
UNIT=0243,44,1,1
UNIT=0244,45,1,1
UNIT=0245,46,1,1
UNIT=0246,47,1,1
UNIT=0247,48,1,1
UNIT=0248,49,1,1
UNIT=0249,4A,1,1
UNIT=024A,4B,1,1
UNIT=024B,4C,1,1
UNIT=024C,4D,1,1
UNIT=024D,4E,1,1
UNIT=024E,4F,1,1
UNIT=024F,50,1,1
*---------------------------------------------------------------------*
*
PHYSICAL LIBRARY DEFINITION
*
*---------------------------------------------------------------------*
*LDEV=DXX,XX,XX,XX,XX,XX,XX,XX,NN,S=N,R=N,M,FMPA/MPMA/HWS/DYN
*
*
! ! ! ! ! ! ! ! ! !
!
! !
*
*
! ! ! ! ! ! ! ! ! !
!
! !
*
*
! ! ! ! ! ! ! ! ! !
!
! ---- ROBOT NO. 2 (OPTIONAL) *
*
! ! ! ! ! ! ! ! ! !
!
! (WHEN SPEC.S= MUST BE SPEC.)*
*
! ! ! ! ! ! ! ! ! !
!
--- ROB NO.1 (OPTIONAL, DEF.1)*
*
! ! ! ! ! ! ! ! ! !
!
(WHEN SPEC.S= MUST BE SPEC.)*
*
! ! ! ! ! ! ! ! ! !
---- ABBA SYSTEM (1-2) (OPT,DEF.1)*
*
! ! ! ! ! ! ! ! ! -------- NO.OF SLOTS PER ROW
*
*
! ! ! ! ! ! ! ! ----------- LAST POSITION IN LAST ROW
*
*
! ! ! ! ! ! ! -------------- FIRST POSITION IN FIRST ROW *
*
! ! ! ! ! ! ----------------- LAST ROW IN SEGMENT
*
*
! ! ! ! ! -------------------- FIRST ROW IN SEGMENT
*
*
! ! ! ! ----------------------- LAST SEGMENT
*
*
! ! ! -------------------------- FIRST SEGMENT
*
*
! ! ----------------------------- DEVICE TYPE (COORDINATE)
*
*
! !
(MUST BE UNIQUE WHEN TW/RCK) *
*
! -------------------------------- DEVICE NO.
*
*
---------------------------------- DEVICE TYPE
*
*
T=TOWER
*
*
R=RACK
*
*
F=FOREIGN MOUNT
*
*
E=EJECT
*
*
I=INSERT
*
*
W=WASTE BOX
*
*---------------------------------------------------------------------*
*
CENTRIC
*
*---------------------------------------------------------------------*
*----- 20 SEG IN 50 ROWS * 50 ----------------------------------------*
110
CentricStor on z/OS
LDEV=R01,01,01,20,01,50,01,50,50,S=1,R=1
(8)
50000 SLOTS
LDEV=R02,02,01,20,01,50,01,50,50,S=1,R=1
50000 SLOTS
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
*
ABBA/E SYSTEM 1 ROBA
I/O-AREAS
*
*---------------------------------------------------------------------*
LDEV=I01,00,01,01,01,01,01,01,10,S=1,R=1
VI 1 SLOT
LDEV=E01,00,02,02,01,01,01,10,10,S=1,R=1
EJ 10 SLOTS
LDEV=W01,00,00,00,00,00,01,01,99,S=1,R=1
WASTE BOX
*---------------------------------------------------------------------*
*---------------------------------------------------------------------*
*
HACC DSNAMES
*
*---------------------------------------------------------------------*
*
*
* XDSNULOG = DSN /UNIT LOG (BDAM)
*
* XDSNSTMS = DSN /SCRATCH VOLSERS
*
* XDSNARCH = DSN /ARCHIVES (VSAM - KSDS)
*
* XDSNMLOG = DSN /MESSAGE LOG (QSAM)
*
* XDSNEXC1 = DSN,RECNO=ZZZZ /DATA TRANSFER LOG - SECSYS 1 (BDAM)
*
* XDNSEXC2 = DSN,RECNO=ZZZZ /DATA TRANSFER LOG - SECSYS 2 (BDAM)
*
*
*
* !
!
*
* !
----- COUNT OF RECORDS
*
* -------------------------- P = PRODUCTION / T = TEST DSNAMES
*
*
*
*---------------------------------------------------------------------*
*
*
PDSNULOG=HACC.HCCV.HACCULOG
(10.1)
PDSNARCH=HACC.PROD.PDSNARCH
(10.2)
PDSNMLG1=HACC.HCCV.HACCMLG1
(10.3)
PDSNEXC1=HACC.HCCV.EXC1
(10.4)
*
*---------------------------------------------------------------------*
*
EXTERNAL SECURITY DEFINITION
*
*---------------------------------------------------------------------*
* EXTSEC=RACF,CLASS=$HACC,RESPREF=$HACC.CMD
*
*---------------------------------------------------------------------*
*
AUTOREPEAT=YES/NO
*
*---------------------------------------------------------------------*
AUTOREPEAT=YES
*AUTOREPEAT=NO
111
CentricStor on z/OS
*
*---------------------------------------------------------------------*
*
AUTO-COMMANDS
*
*---------------------------------------------------------------------*
*
AUTOCMD=' HACC COMMAND
' (,INTV=MMM)
M=MIN
*
*---------------------------------------------------------------------*
AUTOCMD=LOGSTART
AUTOCMD='SYSLOG OFF'
AUTOCMD='ACOM 1',INTV=15
AUTOCMD='ROSA 1,1'
AUTOCMD='RELEASE 1,1'
*
*---------------------------------------------------------------------*
*
ABSWAIT=YES/NO
DEFAULT=NO
*
*---------------------------------------------------------------------*
ABSWAIT=NO
*
*---------------------------------------------------------------------*
*
UCBATI=NN
NN=ATTENTION INDEX, DEFAULT=08
(32) *
*---------------------------------------------------------------------*
UCBATI=08
*---------------------------------------------------------------------*
*
BUFNO ARC=NNNN
NO. OF BUFFERS ARCHIV , DEFAULT=200
*
*
BUFNO CUU=NNNN
NO. OF BUFFERS CUU-LOG, DEFAULT=150
*
*
BUFNO EXC=NNNN
NO. OF BUFFERS EXC-LOG, DEFAULT=200
*
*
BUFNO MSG=NNNN
NO. OF BUFFERS MSG-LOG, DEFAULT=150
*
*
BUFNO SSI=NNNN
NO. OF BUFFERS SSI,
DEFAULT=200
*
*---------------------------------------------------------------------*
BUFNO ARC=0800
BUFNO CUU=0150
BUFNO EXC=0200
BUFNO MSG=0250
BUFNO SSI=0250
*---------------------------------------------------------------------*
*
PRTY EJ=NN
BASE PRIOR. EJECT CMD'S
*
*
PRTY KE=NN
BASE PRIOR. KEEP CMD'S
*
*
PRTY MO=NN
BASE PRIOR. MOUNT CMD'S
*
*
PRTY MV=NN
BASE PRIOR. MOVE CMD'S
*
*
PRTY VI=NN
BASE PRIOR. VOL. INSERT CMD'S
*
*
PRTY SCH=NN
BASE PRIOR. SEARCH INSERT DEVICE CMD'S
*
*
PRTY JOB=JOBNAME,INCR=+/-NN MOUNT/KEEP PRTY FOR JOBS
*
*---------------------------------------------------------------------*
PRTY EJ=25
PRTY KE=30
PRTY MO=35
PRTY MV=20
PRTY VI=26
PRTY SCH=30
112
CentricStor on z/OS
PRTY JOB=HSM,INCR=+7,G
*---------------------------------------------------------------------*
*
TSO SECURITY (IF NO RACF AUTHORISATION CALL)
*
*---------------------------------------------------------------------*
*TSOSEC=USERID,HAA=U/R/N,ABS=Y/N(,HAAIND1=LEVEL)
*
*
!
! ! !
! !
!
*
*
!
! ! !
! !
-- 1.LEVEL INDEX FOR HAA *
*
!
! ! !
! !
DATASETS (1-8 CHAR)
*
*
!
! ! !
! !
*
*
!
! ! !
! ----- ABS NO ACCESS
*
*
!
! ! !
------- ABS FULL ACCESS (YES)
*
*
!
! ! ------------- HAA NO ACCESS
*
*
!
! --------------- HAA READ ACCESS
*
*
!
----------------- HAA UPDATE ACCESS
*
*
-------------------------- TSO USERID (1-7)
*
*
*
*---------------------------------------------------------------------*
MAXTSO USERS=16,BUFFN=600,LOC=ABOVE
SECURITY TYPE=HAA,USERID=UJ,ACCESS=UPD
(11)
SECURITY TYPE=ABS,USERID=UJ,ACCESS=ALL
SECURITY TYPE=ISP,USERID=UJ,ACCESS=ALL
*---------------------------------------------------------------------*
*
MAXCOOR=200000
(9)
MAXVOL=150000
*
*
PASSWORD FOR TAPE LABEL INITIALIZATION
*
*---------------------------------------------------------------------*
*TLIPW=PASSWORD
PASSWORD TO ALLOW TLI
*
*
NOPW
NO PASSWORD REQUIRED
*
*
U
DEFAULT PASSWORD
*
*---------------------------------------------------------------------*
TLIPW=NOPW
*
*---------------------------------------------------------------------*
*
WAITTIME FOR ISSUEING KEEP-MESSAGE, DEFAULT=00
*
*---------------------------------------------------------------------*
*KEEPWT=SS(,RR,DDD)
*
*
!
!
!
*
*
!
!
------------ DELAY-TIME FOR AUTOREP N206 (030-999 S) *
*
!
---------------- NO.OF N206 AUTOREP (00-99)
*
*
-------------------- WAITTIME FOR ISSUEING KEEP (00-99)
*
*---------------------------------------------------------------------*
KEEPWT=01,10,030
*
*-------------- END --------------------------------------------------*
113
114
CentricStor on z/OS
1
SYSDEF1: specify VTLS for CentricStor
2
Use STIMER=01 so that the exchange log dataset is checked every second for
outstanding mounts. As CentricStor is a virtual tape system this makes sure, that mount
times a minimised.
3
Under HACNET specifiy the VAMU network environment. The subparameter type is
used for the AMU and not for the type of the HACC (primary or secondary). The ports
are defined during VAMU setup.
4
TMS=SEQF in the example is used for a flat file, that contains the scratch volume list.
It can be used also for any tape management system. You may need a script to format
your scratch list to match the SEQF file (volume serial on position 1). For CA1, TLMS
you may also use the appropriate keyword for TMS. For RMM use the DFSMSRMM
sample job of the HACC.SAMP file to create the sequential file during RMM housekeeping.
5
The VOLGR statement defines scratch volume pools. Make sure, that the definitions
map the LVGs defined in CentricStor. Volume subpooling features of the tape
management system may be used. Please refer to the corresponding chapter of the
tape management system, that you have installed. In this case, the 5th subparameter
refers to the poolname, that is shown in the modified mount message. If you prefer not
to use the subpooling feature of the tape management system, you may direct
subpooling based on JOB or DSN. In this case you have to add the subparameter
PREFER=DSN|JOB to the VOLGR statement. You also have to add DSNGR and/or
JOBGR statements to your HACC parms. For additional information, look up the HACC
documentation.
6
For UNITNUM specify HEX so that you can use up to 256 virtual drives. Te default is
decimal and in this case only 99 drives are available. This parameter must match the
VAMU settings.
7
Every virtual drive is defined by a UNIT statement. The first subparameter specifies the
MVS address. The second parameter is the virtual drive position defined by the
VAMU and must start with 01. If you plan for upgrades of the number of virtual drives,
make sure that you keep the gap large enough. In the example the second list of
devices starts at 41, so that 21-40 leaves a 32 virtual drive range for enhancements.
For CentricStor, the third and forth subparameter of the UNIT statement is always 1.
8
The statement: LDEV=R01,01,01,20,01,50,01,50,50,S=1,R=1 defines the virtual
robot rack. In this case it defines 20 segment with 50 rows and 50 columns. This makes
up to a total of 50,000 virtual volumes. If you need a larger number of virtual volumes
you may add additional rack statements:
LDEV=Rnn,nn,01,20,01,50,01,50,50,S=1,R=1 this adds 50,000 volumes. Please
copy the other LDEV statements from the example to your production parm set. Instead
you may use: LDEV=R01,01,01,40,01,50,01,50,50,S=1,R=1 to specify 100,000
virtual slots.
CentricStor on z/OS
9
The MAXCOOR and MAXVOL statement should exceed the number of slots defined in
the LDEV=Rxx statement, as for the management of the virtual robot additional coordinates are created. The count you specify is used when you define the ARCHIVE control
file.
10 HACC system control files (refer job ASPALLOC out of HACC.SAMP file):
10.1
As explained earlier, the UNITLOG is used to track the status of the drives in
case of a restart of the HACC. Under PDSNULOG you specify its name.
10.2
The Name of the ARCHIVE file is registered under PDSNARCH. The creation
of the ARCHIVE is documented in the HACC documentation. Please refer also
to the next paragraph.
10.3
Message logs are used to document, which messages were analysed. A set of
logs are defined under PDSNMLGx, where x represent a number from 1 to 4.
You may want to archive the message log when a switch to the next available
log occurs.
10.4
The EXCHANGE logs, that are used for every secondary HACC are defined via
PDSNMLGx, where x represents a number from 1-7.
11 SECURITY: Defines user security for different HACC functions. For detailed information, refer the HACC manuals. Please note, that for TYPE=HAA, ACCESS=ALL is
not valid.
115
4.5.3.4
CentricStor on z/OS
HACC ARCHIVE initialisation
Once the ARCHIVE file is allocated, you run the initialisation process via the ISPF interface.
In case you have not created the HACC parms via an editor, you have to load the ISPF table
for the HACC parms first. Then you run the HACC Archive Administration HAA via option
2. Before you press enter check, that you have specified the correct name of the
HACCPARM.
------------------------------------------------------------------------------ZHCM000P
GRAU Software GmbH
08/04/18
HACC/ABBA Define HACPARM1 Function Selection
17:00
-----------------------------------------------------------------------------Option/Selection: 2
1
2
3
-
Create HACPARM1
HACC Archive Administration HAA
HACC Operator Command Interface
Name Hacparm (Default HACPARM1) :
HACPARM1
------------------------------------------------------------------------------ENTER to process. Enter END command or END key to terminate.
116
CentricStor on z/OS
The HACC Archive Administration panel shows up:
HAA 01/1
HACC ARCHIVE ADMINISTRATION (HAA 3.0.0/M00)
UJ
==============================================================================
PFK
--1
2
3
4
5
6
7
8
9
10
11
12
FUNCTION
--------------------CARTRIDGE LIBRARY
OPTICAL LIBRARY
SAVE/RESTORE/COPY/EXPORT/IMPORT
STATISTICS
DISPLAY ALL DEVICES
GENERATE ARCHIVE FROM HACCPARM
EXIT
NO.COORDS=000000,NO.VOLUMES=000000 - VOLSER=PROD01,DSN=HACC.PROD.PDSNARCH
ARCHIVE CLUSTER IS EMPTY, APPLY "GENERATE ARCHIVE FROM HACCPARM"
==============================================================================
ENTER: 9
<-- SELECT BY NUMBER OR PFK
To generate the ARCHIVE, enter 9 and press the enter key. The following messages show
that the archive was generated:
GENERATION OF ARCHIVE COORDINATES IN PROGRESS
ARCHIVE SAVED, RECORDS=0000001,SAVEDSN=UJ.HACCARCH.SAVE.P.D08113.T133947
ARCHIVE RECORDS CREATED, NO.OF RECORDS=0100313,DSN=UJ.HACCARCH.COORD
SYSOUT FREED FOR DYNAMIC ALLOCATION
SORT COMPLETED. SORTOUT-DSN=UJ.HACCARCH.COORD
FILES ARE MERGED. RECORD STATISTICS:
CREATED RECORDS FROM HACPARM1: 0100313
DUPLICATE ENTRIES (RECTYP 02): 0000000
ARCHIVE RECORDS OLD .........: 0000001
ARCHIVE RECORDS DELETED .....: 0000000
USED EXISTENT RECORDS .......: 0000001
INSERTED NEW HACPARM1 RECORDS: 0100312
TOTAL NO.OF MERGED RECORDS ..: 0100313
MERGE OF HACPARM1 AND ARCHIVES IS COMPLETED.
ARCHIVE LOADED,NO.OF RECORDS=0100314,DSN=UJ.HACCARCH.MERGE
CREATE/MODIFY COMPLETED
<-- ANY CHAR TO CONFIRM
g
117
CentricStor on z/OS
Enter any character to return to the HAA main panel, which now shows the result of the
generation process. The virtual coordinates were created. But the ARCHIVE contains no
volumes.
HAA 01/1
UJ
==============================================================================
PFK
--1
2
3
4
5
6
7
8
9
10
11
12
FUNCTION
OPTICAL LIBRARY
STATISTICS
DISPLAY ALL DEVICES
EXIT
NO.COORDS=100092,NO.VOLUMES=000000
-
VOLSER=PROD01,DSN=HACC.PROD.PDSNARCH
==============================================================================
ENTER: 1
118
CentricStor on z/OS
To create the logical volumes and to assign them to their virtual coordinates, enter 1.
HAA 02/1
CARTRIDGE LIBRARY
UJ
==============================================================================
PFK
--1
2
3
4
5
6
7
8
9
10
11
12
FUNCTION
------------------------------DISPLAY COMPLETE VOLSER ENTRIES
DISPLAY/MODIFY VOLSER ENTRIES
DEFINE VOLSERS TO ABBA LIBRARY
ASSIGN VOLSERS TO HOME-COORDINATES
UNASSIGN VOLSERS FROM HOME-COORDINATES (IMMEDIATE)
UNASSIGN AND ASSIGN TO "VIRTUAL" (AFTER CARTRIDGE IS EJECTED)
ASSIGN VOLSERS TO "VIRTUAL"
DISPLAY CARTRIDGE LIBRARY DEVICES
DELETE VOLSERS
PRINT VOLSER-COORDINATE ASSIGNMENTS
RETURN TO MAIN MENUE
NO VOLSERS FOUND. APPLY "DEFINE VOLSERS"
==============================================================================
ENTER: 3
119
CentricStor on z/OS
As you can see from the message, no volumes are yet defined. Select option 3 to start the
definition process.
HAA 02/3
DEFINE VOLSERS TO ABBA-SYSTEMS
UJ
==============================================================================
VOLSER START- END- PREFIX
NO PREFIX NUMBER NUMBER LENGTH
1 A
00000
09999
1
2 B
00000
19999
1
3 C
00000
29999
1
4 D
00000
09999
1
5 E
00000
00999
1
6
7
8
9
10
-----------------------------------------------------------------------------VOLSER-PREFIX: 0-6 bytes, aphanumeric, JCL restrictions
START/END NO.: 0-6 digits,0-999999
With this function all VOLSERs are defined that should be handled by ABBA.
Assignments to HOME-COORDs: see PFK4, assignments to DYNAMIC AREA: see PFK7
Without assignment the defined volsers remain "INITIAL".
==============================================================================
ENTER: y <-- "Y" TO CONFIRM INPUT OR ANY CHAR TO RESPECIFY
You may now enter multiple volume ranges and a volser prefix. The prefix length is calculated automatically when you hit enter. You may change your input or confirm the changes
by entering Y. The volser definition panel is refreshed and the last line reads:
ENTER: g
<-- "C"=CONTINUE SELECTION, "G"=GENERATE OR "I"=IGNORE REQUEST
If your definitions are o.k. start the volser generation by entering G. The result is shown on
the next screen, where you confirm to load the generated data to the ARCHIVE file. Enter
yes with no abbreviation.
120
CentricStor on z/OS
=== CREATION OF VOLSER-RECORDS IN PROGRESS ===
ARCHIVE SAVED, RECORDS=0100314,SAVEDSN=UJ.HACCARCH.SAVE.P.D08113.T134513
NO.OF RECORDS COPIED=100314,OUPUT-DSN=UJ.HACCARCH.SAVE.P.VOLSER
A00000-A09999 10000
B00000-B19999 20000
C00000-C29999 30000
D00000-D09999 10000
E00000-E00999 01000
TOTAL RECORDS=171314,OUPUT-DSN=UJ.HACCARCH.SAVE.P.VOLSER
SYSOUT FREED FOR DYNAMIC ALLOCATION
SORT COMPLETED. SORTOUT-DSN=UJ.HACCARCH.SAVE.P.VOLSER
<== DECIDE RELOAD ARCHIVE WITH NEW DATA:
<== ENTER "YES" TO PROCEED OR ANY CHAR TO IGNORE RELOAD
yes
ARCHIVE LOADED,NO.OF RECORDS=0171314,DSN=UJ.HACCARCH.SAVE.P.VOLSER
SELECTED VOLSER-RECORDS ARE CREATED
<-- ANY CHAR TO CONFIRM
g
When the volser records were created return to the Cartridge Library screen where you
enter 4 to assign the volumes to their virtual coordinates.
HAA 02/1
CARTRIDGE LIBRARY
UJ
==============================================================================
PFK
--1
2
3
4
5
6
7
8
9
10
11
12
FUNCTION
------------------------------DISPLAY COMPLETE VOLSER ENTRIES
DISPLAY/MODIFY VOLSER ENTRIES
DEFINE VOLSERS TO ABBA LIBRARY
ASSIGN VOLSERS TO HOME-COORDINATES
UNASSIGN VOLSERS FROM HOME-COORDINATES (IMMEDIATE)
UNASSIGN AND ASSIGN TO "VIRTUAL" (AFTER CARTRIDGE IS EJECTED)
ASSIGN VOLSERS TO "VIRTUAL"
DISPLAY CARTRIDGE LIBRARY DEVICES
DELETE VOLSERS
PRINT VOLSER-COORDINATE ASSIGNMENTS
RETURN TO MAIN MENUE
==============================================================================
ENTER: 4
In the next screen you have to select a virtual rack device to which you assign the volumes.
In case your HACCPARMx contains multiple LDEV=Rxx commands, a line is shown for
each command. The ASSIGNED column shows that no volumes are assigned.
121
CentricStor on z/OS
HAA 02/5
CARTLIB DEVICE SELECTION FOR VOLSER ASSIGNMENT
UJ
==============================================================================
NO. DEV S ROB T/R SEG
ROW
POS
CAPACITY ASSIGNED
FIRST LAST SPLIT
01 R01 1 1
01 01-20 01-50 01-50
50000
0
--0
02 R02 1 1
02 01-20 01-50 01-50
50000
0
--0
==============================================================================
ENTER: 01 <-- NO.FOR DEVICE OR ANY CHAR TO RETURN
Select the number of the device you want to work with and press enter.
HAA 02/6
ASSIGN VOLSERS TO HOME COORDINATES (Hierarchical Org.)
UJ
==============================================================================
LIBRARY DEVICE ......: R01
ABBA SYSTEM NO. .....: 1
NO.OF SEGMENTS ......: 20
ACCESS BY ROBOT .....: 1
NO.OF ROWS ..........: 50
CAPACITY OF.DEVICE...: 50000
NO.OF POSITIONS .....: 50
NO.OF ASSIGNED SLOTS :
0
-----------------------------------------------------------------------------COORDINATE RANGE
FROM-TO:
- TOWER/RACK ........: 01
- SEGMENTS ..........: 01 20
If all FROM-TO ranges are identical
- ROWS ..............: 01 50
only 1 record will be created.
- POSITIONS .........: 01 50
VOLSER ASSIGNMENT:
- START VOLSER ......: A00000
CALCULATED END-VOLSER: C19999 after enter
- ASSIGNMENT (H or V): V
H=horizontal,V=vertical
- DEFAULT STATUS ....: MB
STATUS: see GENERAL INFORMATIONS
- MAPS-MANPOOL.......: N
N=No (Default) / Y=Yes
-----------------------------------------------------------------------------The specified START-VOLSER is assigned to the first coordinate, the next
VOLSER-numbers are created in ascending order and are assigned to the next
coordinates. the coordinates run in the sequence: HORIZONTAL or VERTICAL
==============================================================================
ENTER: s <-- "S" FOR ASSIGN-SELECTION OR CHAR TO RESPECIFY
Enter the start volser into the corresponding field. For Assignment choose V and for Default
Status choose MB (M=Cartrigde Type Volume; B=Volume in Library). Pressing enter will
refresh the screen and show the Calculated End-Volser. You now select S to proceed with
the assignment process.
122
CentricStor on z/OS
HAA 02/5
UJ
==============================================================================
ROW
POS
CAPACITY ASSIGNED
FIRST LAST SPLIT
01 R01 1 1
01 01-20 01-50 01-50
50000
50000
A00000 C19999
0
02 R02 1 1
02 01-20 01-50 01-50
50000
0
--0
==============================================================================
ENTER: 02 <-- NO.FOR DEVICE OR ANY CHAR TO RETURN
Now you see that volumes are assigned to the virtual rack. You also see the starting volser.
You now proceed with next device 02. Note that the last assigned volser is C19999.
HAA 02/6
ASSIGN VOLSERS TO HOME COORDINATES (Hierarchical Org.)
UJ
==============================================================================
LIBRARY DEVICE ......: R02
ABBA SYSTEM NO. .....: 1
NO.OF SEGMENTS ......: 20
ACCESS BY ROBOT .....: 1
NO.OF ROWS ..........: 50
CAPACITY OF.DEVICE...: 50000
NO.OF POSITIONS .....: 50
NO.OF ASSIGNED SLOTS :
0
-----------------------------------------------------------------------------COORDINATE RANGE
FROM-TO:
- TOWER/RACK ........: 02
- SEGMENTS ..........: 01 20
If all FROM-TO ranges are identical
- ROWS ..............: 01 50
only 1 record will be created.
- POSITIONS .........: 01 50
VOLSER ASSIGNMENT:
- START VOLSER ......: C20000
CALCULATED END-VOLSER: E00999
- ASSIGNMENT (H or V): V
H=horizontal,V=vertical
- DEFAULT STATUS ....: MB
STATUS: see GENERAL INFORMATIONS
- MAPS-MANPOOL.......: N
N=No (Default) / Y=Yes
-----------------------------------------------------------------------------The specified START-VOLSER is assigned to the first coordinate, the next
VOLSER-numbers are created in ascending order and are assigned to the next
coordinates. the coordinates run in the sequence: HORIZONTAL or VERTICAL
==============================================================================
ENTER: s <-- "S" FOR ASSIGN-SELECTION OR CHAR TO RESPECIFY
For the start volser enter the first unassigned volume number: C20000.
HAA 02/5
UJ
==============================================================================
ROW
POS
CAPACITY ASSIGNED
FIRST LAST SPLIT
01 R01 1 1
01 01-20 01-50 01-50
50000
50000
A00000 C19999
0
02 R02 1 1
02 01-20 01-50 01-50
50000
0
--0
==============================================================================
ENTER:
<-- NO.FOR DEVICE OR ANY CHAR TO RETURN
<<<<--- NO CHAR to Return
123
CentricStor on z/OS
If you are ready with your assignments leave the NO.FOR DEVICE field emtpy end press
enter. The instruction to enter any character is misleading.
The HAA main panel shows up again and reports the number of coordinates and volumes.
Also the name of the ARCHIVE and the volser location appears.
HAA 01/1
UJ
==============================================================================
PFK
--1
2
3
4
5
6
7
8
9
10
11
12
FUNCTION
OPTICAL LIBRARY
STATISTICS
DISPLAY ALL DEVICES
EXIT
NO.COORDS=100092,NO.VOLUMES=071000
-
VOLSER=PROD01,DSN=HACC.PROD.PDSNARCH
==============================================================================
ENTER:
Leave the dialog pressing PF12.
If you need to define new volser ranges or want to change these, you have to update the
ARCHIVE file. The easiest way is to create a new ARCHIVE with the updated specifications. Before it can be used, resync your tapemanagent database and the ARCHIVE file to
reflect the current scratch status.
124
CentricStor on z/OS
4.5.3.5
HACC Scratch Synchronisation Process
Scratch mounting is performed under control of HACC. HACC selects a scratch volume
from the ARCHIVE file and directs a mount for this volume to CentricStor. So from the
viewpoint of CentricStor, each mount in conjuction with HACC is specific. HACC only stubs
the scratch virtual volume so that it is not restored into the tape volume cache.
The TMS statement of the HACPARMx member informs HACC about the tape
management environment. Please refer to the HACC manuals for further details. In any
case, you can create a sequential file that contains the volsers of the scratch volumes.
TMS=SEQF enables this file to be used during a FREEVOL command. Please note that the
FREEVOL command may use different subparameters. Dependend on the method you
create the scratch file you may have to use another format: If you create an incremental
scratch file (it only contains volsers, that became scratch during the last housekeeping), use
subparameter ADD together with the FREEVOL command. If you create a complete scratch
file, use REP when issueing FREEVOL. In addition RESET may be used in case you prefer
to use only low volser numbers. High volsers will normally remain unused. This way you can
control whether you have defined too many logical volumes (check the count of unused
volumes).
For RMM a sample procedure to create the scratch flat file and to issue the FREEVOL
command is included in HACC.SAMP.
For the very first FREEVOL command use the REP,RESET subparameters.
4.5.3.6
HACC Volume Initialisation
HACC includes a function to initialise volumes automatically. This process is performed
outside the tape management. If you prefer to use this method, please make sure that use
define the volumes into your tape management accordingly (e.g. ADDVOL command with
INIT(N) for RMM). For more information about the automated initialisation process refer to
the description of the TLI command of HACC.
125
Tape Management Software
CentricStor on z/OS
4.6 Tape Management Software
This chapter explains the setup for different tape management systems.
In case, your CentricStor is attached via the VACS emulation, the LVGs of CentricStor have
to be mapped to a pool-ID in VACS. This is done, using the cmd_proc application in a
command box of the CentricStor VLP. The procedure was explained earlier in this document
(see section “Logical Volume Definition” on page 68).
4.6.1 DFSMSrmm considerations
Functions of DFSMSrmm, that interface with CentricStor are scratch processing and
scratch volume subpooling. As CentricStor also maintains the list of scratch volumes, a
sychronisation process with RMM must be in place.
4.6.1.1
Scratch Synchronisation for RMM
The method, on how scratch volumes are synchronised is dependent on the host software
product, that is used. It is implemented into the RMM housekeeping and may be done
synchronously (CSMVS) using RMM user exit EDGUX200 or asynchronously via an
additional jobstep (NCS/CSC and HACC). Please refer the the corresponding chapter of the
host software.
4.6.1.2
Scratch Subpooling with RMM
Scratch subpooling of DFSMS is implemented either by using DFSMS/ACS routines or by
using user exit EDGUX100. The more flexible way is the use of the DFSMS/ACS routines.
This method is described here to enable users to do it more easily. It applies to all host
software solutions.
i
Before you choose to use this method, please review your current RMM
setup. In case you use a modified exit EDGUX100, check the functions, that are in
use. If this exit already assigns a management criteria, you have to implement this
function into your ACS routines. The default exit checks EXPDT=99000 for catalog
control and assigns a management criteria of D99000, which is mapped to a VRS
with the WHILECATALOG option. The ACS management class routine then should
assign a management class of D99000 when run under the environment of
RMMVRS. This management class of D99000 has to be defined as a dummy class.
The function foreign tape with EXPDT=98000 is not affected using the proposed solution.
The SMS based subpooling relies on a tape library. This can be SMS- or NonSMSmanaged and is configured via the ISMF/ISPF interface. Multiple storage groups can be
defined for a single tape library. These storage groups represent the different scratch
126
CentricStor on z/OS
subpools. The library type used for CentricStor is Non-SMS. It must not be defined using
the HCD/IOCDS process. Before you start the ISMF dialog, make sure that the Tape
Control Database (TCDB) is defined in your system. The TCDB is also called VOLCAT. The
following JCL example can be used to allocate it. In case you already use an IBM tape
library or IBM virtual tape library, this step is obsolete, because the VOLCAT was already
defined earlier.
JCL to define the TCDB
//DEFTCDB JOB
//*
//STEP1
EXEC PGM=IDCAMS
//SYSPRINT DD
SYSOUT=A
//SYSIN
DD
*
DEFINE USERCATALOG (NAME(SYS1.VOLCAT.VGENERAL) VOLCATALOG VOLUME(MYVOL1) CYLINDERS(1 1))
In case you have no IBM tape library installed, there is no need, to specify more than one
cylinder of disk space, as no volumes are recorded within the TCDB. Only the library entry
is kept. If your system currently does not make use of OAM, you must enable the subsystem
for OAM before you proceed using the Library Management dialog. This can be done using
the MVS system command:
SETSSI ADD,SUBNAME=OAM1,INITRTN=CBRINIT
Or insert the following statement to your system PARMLIB (member IEFSSNxx) before
scheduling an IPL:
SUBSYS SUBNAME(OAM1) INITRTN(CBRINIT)
i
There is no need to start an OAM address space, if you are not using an IBM library.
In case of a mixed environment (IBM library and CentricStor), please ignore OAM
messages CBR3006I and CBR3002E that occur for the library entry that was
defined for CentricStor.
127
CentricStor on z/OS
After the VOLCAT has been successfully defined, enter the Library Management dialog in
ISMF:
Panel Help
-----------------------------------------------------------------------------ISMF PRIMARY OPTION MENU - z/OS DFSMS V1 R6
Enter Selection or Command ===> 10
Select one of the following options and press Enter:
0 ISMF Profile
- Specify ISMF User Profile
1 Data Set
- Perform Functions Against Data Sets
2 Volume
- Perform Functions Against Volumes
3 Management Class
- Specify Data Set Backup and Migration Criteria
4 Data Class
- Specify Data Set Allocation Parameters
5 Storage Class
- Specify Data Set Performance and Availability
6 Storage Group
- Specify Volume Names and Free Space Thresholds
7 Automatic Class Selection - Specify ACS Routines and Test Criteria
8 Control Data Set
- Specify System Names and Default Criteria
9 Aggregate Group
- Specify Data Set Recovery Parameters
10 Library Management
- Specify Library and Drive Configurations
11 Enhanced ACS Management
- Perform Enhanced Test/Configuration Management
C Data Collection
- Process Data Collection Function
L List
- Perform Functions Against Saved ISMF Lists
P Copy Pool
- Specify Pool Storage Groups for Copies
R Removable Media Manager
- Perform Functions Against Removable Media
X Exit
- Terminate ISMF
Use HELP Command for Help; Use END Command or X to Exit.
Then select option 3: TAPE LIBRARY
Panel Help
-----------------------------------------------------------LIBRARY MANAGEMENT SELECTION MENU
Enter Selection or Command ===> 3
1
2
3
128
Optical Library
Optical Drive
Tape Library
- Optical Library Configuration
- Optical Drive Configuration
- Tape Library Configuration
CentricStor on z/OS
The TAPE LIBRARY APPLICATION SELECTION menu shows up. Make sure you have
specified your current SCDS. Enter the library name you have choosen into the corresponding field and select option 3 (Define).
Panel Utilities Help
-----------------------------------------------------------------------------TAPE LIBRARY APPLICATION SELECTION
Command ===>
To Perform Library operations, Specify:
CDS Name
. . . . . . . 'PROD.SMS.SCDS'
(1 to 44 Character Data Set Name or 'Active')
Library Name . . . . . CENTLIB1
(For Tape Library list, fully or
Partially Specified or * for all)
Select one of the
3 1. List
2. Display 3. Define 4. Alter
-
following options :
Generate a list of Libraries
Display a Library
Define a Library
Alter a Library
If List option is chosen,
Enter "/" to select option
Respecify View Criteria
Respecify Sort Criteria
Use ENTER to Perform Selection;
Use HELP Command for Help; Use END Command to Exit.
129
CentricStor on z/OS
On the next screen, enter a description for the library and a Library-ID. Choose any ID, that
fits your installation. Also specify P for the Entry Default Use Attribute and K for Eject
Default.
Panel Utilities Scroll Help
-----------------------------------------------------------------------------TAPE LIBRARY DEFINE
Page 1 of 2
Command ===>
SCDS Name . : PROD.SMS.SCDS
Library Name : CENTLIB1
To Define Library, Specify:
Description ==> Dummy Library for CentricStor RMM Subpooling
==>
Library ID . . . . . . . . . . . 12345
(00001 to FFFFF)
Console Name . . . . . . . . . .
Entry Default Data Class . . . .
Entry Default Use Attribute . . P
(P=PRIVATE or S=SCRATCH)
Eject Default . . . . . . . . . K
(P=PURGE or K=KEEP)
Media Type: Scratch Threshold
Media1 . . .
Media2 . . . 0
Media3 . . .
Media4 . . . 0
Media5 . . .
Media6 . . . 0
Media7 . . .
Media8 . . . 0
Use ENTER to Perform Verification; Use DOWN Command to
Use HELP Command for Help; Use END Command to Save and
130
.
.
.
.
0
0
0
0
(0
(0
(0
(0
to
to
to
to
999999)
999999)
999999)
999999)
View next Panel;
Exit; CANCEL to Exit.
CentricStor on z/OS
As this is a dummy library, specify NO for the initial status in the next screen.
-----------------------------------------------------------------------------TAPE LIBRARY DEFINE
Page 2 of 2
Command ===>
SCDS Name . : PROD.SMS.SCDS
Library Name : CENTLIB1
Initial Online Status (Yes, No, or Blank):
MVSA
===> NO *MVSPL
===>
.
.
.
Warning:
When you connect a tape library to a system group rather than a system,
you lose the ability to vary that library online or offline to the
individual systems in the system group. It is strongly recommended that
the tape library be connected to individual systems only.
Use ENTER to Perform Verification; Use UP Command to View previous Panel;
Use HELP Command for Help; Use END Command to Save and Exit; CANCEL to Exit.
Now that the tape library is defined, you must define storage groups, that represent the
scratch subpools. Use the ISMF dialog again to start the definitions (Option 6).
131
CentricStor on z/OS
-----------------------------------------------------------------------------STORAGE GROUP APPLICATION SELECTION
Command ===>
To perform Storage Group Operations, Specify:
CDS Name . . . . . . 'PROD.SMS.SCDS'
(1 to 44 character data set name or 'Active' )
Storage Group Name
SGLVG01
(For Storage Group List, fully or
partially specified or * for all)
Storage Group Type
TAPE
(VIO, POOL, DUMMY, COPY POOL BACKUP,
OBJECT, OBJECT BACKUP, or TAPE)
Select one of the
2 1. List
2. Define 3. Alter
4. Volume -
following options :
Generate a list of Storage Groups
Define a Storage Group
Alter a Storage Group
Display, Define, Alter or Delete Volume Information
If List Option is chosen,
Use ENTER to Perform Selection;
Enter a storage group name, that represents a scratch subpool. This scratch subpool is
mapped to a CentricStor logical volume group (LVG). The storage group type is: TAPE.
Select option 2 to enter the TAPE STORAGE GROUP DEFINE screen:
132
CentricStor on z/OS
-----------------------------------------------------------------------------TAPE STORAGE GROUP DEFINE
Command ===>
SCDS Name . . . . . : PROD.SMS.SCDS
Storage Group Name : SGLVG01
To DEFINE Storage Group, Specify:
Description ==> CentricStor Logical Volume Group 01
==>
Library Names (1 to 8 characters each):
===> CENTLIB1 ===>
===>
===>
===>
===>
DEFINE
SMS Storage Group Status . . Y
===>
===>
(Y or N)
Use ENTER to Perform Verification and Selection;
You may now enter a description for the storage group. You must enter the library name for
CentricStor, that you have defined previously during the tape library definition process.
Make sure, that the storage group is enabled by entering Y into the DEFINE SMS Storage
Group Status field and press ENTER.
133
CentricStor on z/OS
-----------------------------------------------------------------------------SMS STORAGE GROUP STATUS DEFINE
Page 1 of 2
Command ===>
SCDS Name . . . . : PROD.SMS.SCDS
Storage Group Name : SGLVG01
Storage Group Type : TAPE
To DEFINE Storage Group System/
Sys Group Status, Specify:
( Possible SMS SG Status
for each:
- Pool SG Type
System/Sys
SMS SG
System/Sys
SMS SG
NOTCON, ENABLE, DISALL
Group Name
Status
Group Name
Status
DISNEW, QUIALL, QUINEW
----------------------------- Tape SG Type
MVSA
===> ENABLE
*MVSPL
===> NOTCON
NOTCON, ENABLE,
MVSB
===> ENABLE
===>
DISALL, DISNEW
MVSC
===> ENABLE
===>
- Copy Pool Backup SG Type
===>
===>
NOTCON, ENABLE )
===>
===>
* SYS GROUP = sysplex
===>
===>
minus Systems in the
===>
===>
Sysplex explicitly
===>
===>
defined in the SCDS
Use ENTER to Perform Verification; Use DOWN Command to View next Panel;
Enable the systems to access the storage group. For the system group name specify
NOTCON. Save your changes and restart the process, until all LVGs are mapped to a
storage group.
To progress the SMS setup, you now define management classes according to your needs.
You may use one management class per LVG. In addition, you may also define special
classes for the WHILECATALOG attribute or Cycle control, e.g. EXPDT=99005. Make sure,
that the management classes used for tape are not used for DASD data sets.
134
CentricStor on z/OS
-----------------------------------------------------------------------------MANAGEMENT CLASS APPLICATION SELECTION
Page 1 of 2
Command ===>
To perform Management Class Operations, Specify:
CDS Name . . . . . . . . . 'PROD.SMS.SCDS'
(1 to 44 character data set name or 'Active' )
Management Class Name . . . MCLVG01
(For Management Class List, fully or
partially specified or * for all)
Select one of the
3 1. List
2. Display 3. Define 4. Alter
-
following options :
Generate a list of Management Classes
Display a Management Class
Define a Management Class
Alter a Management Class
If List Option is chosen,
Use ENTER to Perform Selection; Use DOWN Command to View next Selection Panel;
Select option 3 to define the management class.
135
CentricStor on z/OS
-----------------------------------------------------------------------------MANAGEMENT CLASS DEFINE
Page 1 of 5
Command ===>
SCDS Name . . . . . . : PROD.SMS.SCDS
Management Class Name : MCLVG01
To DEFINE Management Class, Specify:
Description ==> Management for CentricStor Logical Volume Group 01
==>
Expiration Attributes
Expire after Days Non-usage . . NOLIMIT
Expire after Date/Days . . . . . NOLIMIT
Retention Limit
. . . . . . . . . NOLIMIT
(1 to 9999 or NOLIMIT)
(0 to 9999, yyyy/mm/dd or
NOLIMIT)
(0 to 9999 or NOLIMIT)
Use ENTER to Perform Verification; Use DOWN Command to View next Panel;
As RMM only run the management class and storage group routines for Non-SMS libraries,
the data class and storage class routines need not to be updated. Please note, that RMM
will assign a storage class of USERMM.
Once you have gone through the process, that was previously discussed, you now can tailor
your ACS routines.
The management class routine is called by RMM under the environment of RMMVRS and
RMMPOOL. Only when run under RMMVRS, the assigned management class is registered
in the RMM dataset record, which then can be used for definition of VRS's. You may use
different logics for the two environments. Please apply the logic that applies to your system
needs. E.g. use data set name filter lists to assign different management classes.
PROC MGMTCLAS
FILTLIST HSM_ML2
INCLUDE('DFHSM.HMIGTAPE.DATASET')
FILTLIST HSM_BACKUP
INCLUDE('DFHSM.BACKTAPE.DATASET')
FILTLIST ........etc etc.........................
.......
SELECT
WHEN (&ACSENVIR = 'RMMPOOL')
SELECT
WHEN (&DSN = &HSM_ML2)
SET &MGMTCLAS = 'MCLVG01'
WHEN (&DSN = &HSM_BACKUP)
136
CentricStor on z/OS
OTHERWISE
END
WHEN (&ACSENVIR = 'RMMVRS')
SELECT
WHEN (&EXPDT = '1999000')
SET &MGMTCLAS = 'D99000'
OTHERWISE
SET &MGMTCLAS = ''
END
OTHERWISE
DO
SELECT
WHEN (&MGMTCLAS = '')
SET &MGMTCLAS='DEFAULT'
OTHERWISE
........
END
END
END
END
Now an example for the storage group routine follows:
PROC STORGRP
/***************************************************************/
FILTLIST ............
/***************************************************************/
SELECT
WHEN (&ACSENVIR = 'RMMPOOL')
SELECT
WHEN (&MGMTCLAS = 'MCLVG01')
SET &STORGRP = 'SGLVG01'
END
OTHERWISE
SELECT
WHEN (&STORCLAS = 'LOGGER')
SET &STORGRP = 'LOGGER'
WHEN (&STORCLAS = 'SMSWRK')
.......
137
CentricStor on z/OS
The newly defined storage groups have to be mapped to a VLPOOL statement of the RMM
startup parameters. Please stop your tape processing during the activations of the new
parameters and the activation of the changed SMS environment. For the Option statement,
specify SMSACS(YES), to enable RMM to use the ACS routines.
Also add VLPOOL statements; the NAME parameter must match the storage group name:
VLPOOL PREFIX(A*) TYPE(S) DESCRIPTION('LVG01')
NAME(SGLVG01)
MEDIANAME(3490)
VLPOOL PREFIX(B*) TYPE(S) DESCRIPTION('LVG02')
NAME(SGLVG02)
MEDIANAME(3490)
VLPOOL PREFIX(C*) TYPE(S) DESCRIPTION('LVG03')
NAME(SGLVG03)
MEDIANAME(3490)
-
Now translate your changed ACS routines, activate the new configuration and restart RMM.
With the changed configuration, RMM will now change scratch mount messages IEC501A
and IEF233A by adding - POOL=storgrp at the end of the message. This change will be
used by the supported host software solutions of CentricStor, to assign a scratch volume
out of the corresponding LVG. Please note, that only the system log shows the change of
the mount message. The change does not appear in the joblog.
Checklist to implement RMM scratch subpooling
1. Define the VOLCAT (not nessary if already using SMS tape)
2. Define the OAM subsystem interface entry (not nessary if already using SMS tape)
3. Define the tape library using ISMF
4. Define one storage group per logical volume group
5. Define one or more management classes for tape
6. Define a management class for catalog control (D99000) and if needed for cycle control
(for example D99005) (if EDGUX100 function used and VRS for D99000 previously
defined)
7. Tailor your management class routine to query the RMMVRS environment
8. Tailor your storage group routine to query the RMMPOOL environment
9. Translate the changed ACS routines
10. Add SMSACS(YES) to your RMM option statement
11. Update your VLPOOL statements
12. Stop tape processing (RMM)
138
CentricStor on z/OS
13. Activate the new SMS environment
14. Restart RMM
4.6.1.3
Volume Definition and Initialisation with RMM
In case you did not you the Auto Labelling option of the LVG, all logical volumes of that LVG
have to be initialised using EDGINERS.
It is very important to use the correct sequence of actions for the process of volume
definition and initialisation. Please refer to the checklist at the end of the chapter for the
recommended sequence.
After the LVs are defined in CentricStor, use the TSO ADDVOL command or the dialog
ADDSCRATCH of RMM to register these to the RMM CDS. If you did not enable the Auto
Labelling option, make sure that you set the INIT(Y) parameter of the ADDVOL command.
If Auto Labelling is disabled, start EDGINERS to initialize the volumes now:
//INITCS JOB
//EDGINIT EXEC PGM=EDGINERS,
//
PARM=('INITIALIZE,COUNT(50),NOVERIFY,POOL(A*)',
//
'BATCH(0),STATUS(NOTMASTER)')
//TAPE
DD UNIT=(CSTOR,,DEFER)
//
Use Batch(0), to ensure, that all scratch volumes are initialised. The COUNT value just
groups volumes together for initialisation. The maximum number is 99. For POOL specify
the prefix value of the VLPOOL statement that corresponds to the pool. You cannot use the
NAME contents.
For VACS attachments under NCS/CSC and CSMVS now run the SET SCR command under
cmd_proc of the VACS emulation. The procedure is explained earlier in this section (4.3.5).
i
Please observe the following sequence when defining logical volumes to
CentricStor:
1.
2.
3.
4.
5.
6.
7.
Define the logical volume group (Recommendation: Auto Labelling enabled)
Add logical volumes to a group
Add the volumes to RMM
Initialise the LVs with EDGINERS 1
Define the pool-ID in VACS 2
Assign the LVs to the pool-ID using set scratch 2
In case of HACC run the scratch synchronisation process
1
If Auto Labelling is disabled
2
If NCS/CSC or CSMVS is used
139
CentricStor on z/OS
4.6.2 CA1 and TLMS considerations
Functions of CA1 and TLMS, that interface with CentricStor are Scratch processing and
scratch volume subpooling. As CentricStor also maintains the list of scratch volumes, a
sychronisation process with CA1 and TLMS must be in place.
4.6.2.1
Scratch Synchronisation for CA1 and TLMS
product, that is used. It is implemented into the CA1 or TLMS TMSCLEAN/TLMSTRS job
and may be done synchronously (CSMVS) using CA1 user exit TMSXCLN1, asynchronously via an additional jobstep (NCS/CSC) or by the FREEVOL command (HACC).
CSMVS is currently not supported with TLMS.
4.6.2.2
Scratch Subpooling with CA1 and TLMS
Scratch subpooling of CA1 and TLMS is implemented using SCR and NSM statements in
the PPOPTION data set. For CA1, the members are TMOSCRxx and TMONSMxx. The
corresponding members for TLMS are CTOSCRxx and CTONSMxx.
The implementation for subpooling applies to all host software solutions.
The SCR parameters define the scratch subpool, whereas the NSM parameter define
which dataset pattern are assigned to which pool.
********** TMOSCR00 **********
SCRPOOL=SP.LVG01,RANGE=100000-109999,
RANGE=200000-209999
SCRPOOL=SP.LVG02,RANGE=300000-319999
SCRPOOL=SP.LVG03,RANGE=320000-359999
********** TMONSM00 **********
DSN=DFHSM.HMIGTAPE.-,POOL=SP.LVG01
DSN=DFHSM.BACKTAPE.-,POOL=SP.LVG02
DSN=-,POOL=SP.LVG03
After you have defined your pools and pool matching table, activate the new configuration.
The result of this implementation is, that CA1 and TLMS will issue additional mount
messages and keep the original messages IEC501A and IEF233A unchanged. The
additional messages are copies of the originals, where the string PRIVAT or SCRTCH is
replaced by the corresponding poolname. The message is prefixed with a CA1/TLMS
identifier.
Example:
IEC501A M 5540,PRIVAT,SL,COMP,BACKFULL,STEP1,DUMP.BACKUP05.CSL
TMS002 IEC501A M 5540,SP.LVG03,SL,COMP,BACKFULL,STEP1,DUMP.BACKUP05.CSL
140
CentricStor on z/OS
4.6.2.3
Volume Definition and Initialisation with CA1 and TLMS
have to be initialised using TMSTPNIT for CA1 or TLMSNITT for TLMS.
After the LVs are defined in CentricStor, use the appropriate procedures to expand the TMC
and the VMF, respectively and to add the new volsers to the tape management system.
If Auto Labelling is disabled, start TMSTPNIT or TLMSINTT to initialize the volumes now:
//stepname EXEC PGM=TMSTPNIT or TLMSNITT
// ,PARM='ROBOT'
//STEPLIB DD DSN=your.steplib,DISP=SHR
//TAPEDB DD DSN=your.TMC.or.VMF
//SYSPRINT DD SYSOUT=A
//LABELDD DD UNIT=(tape,,DEFER)
//SYSIN DD *
NEWTAPE NUMBTAPE=count,SER=volser
/*
For automation purposes use the EXEC parm ROBOT. The count for the NUMBTAPE
parameter ranges from 1 to 999 in case of CA1 5.11. For other releases and for TLMS,
please check the manuals. Restrictions may also apply for alphanumeric volser ranges.
i
CentricStor:
1.
2.
3.
4.
5.
6.
7.
Expand you TMC or VMF and add the volumes
Initialise the LVs with TMSTPNIT or TLMSNITT 1
In case of HACC now the scratch synchronisation process
1
2
141
CentricStor on z/OS
4.6.3 Control-T considerations
Functions of Control-T, that interface with CentricStor are Scratch processing and scratch
volume subpooling. As CentricStor also maintains the list of scratch volumes, a sychronisation process with Control-T must be in place.
4.6.3.1
Scratch Synchronisation for Control-T
product, that is used. It is implemented into the Control-T xxxxxxxx job and is be done
asynchronously via an additional jobstep (NCS/CSC and HACC). CSMVS is currently not
supported with Control-T.
4.6.3.2
Scratch Subpooling with Control-T
Scratch subpooling of Control is implemented using the IOA dialog to update the Control-T
parameter statements.
The implementation for subpooling applies to all host software solutions.
The following description gives you an overview of the pool and rules definition facilities of
Control-T. If you need detailed information, please refer to the CONTROL-M/Tape User
Guide.
To start the pool definition, enter the IOA dialog under TSO/ISPF and select option TP.
--------------------- IOA PRIMARY OPTION MENU -----------------(1)
OPTION ===>
USER TADMIN
DATE 27.01.08
4
5
6
7
8
IV
TR
TP
TV
TI
TC
COND-RES IOA Conditions/Resources Display
LOG IOA Log Display
TSO Enter TSO Command
MANUAL COND IOA Manual Conditions Display
CALENDAR DEF IOA Calendar Definition
VARIABLE DATABASE IOA Variable Database Definition Facility
RULE DEFINITION CTT Rule Definition
POOL DEFINITION CTT Pool Definition
VAULT DEFINITION CTT Vault Definition
INQ/UPD MEDIA DB CTT Media Database Inquire/Update
CHECK IN EXT VOL CTT External Volume Check-In
COMMANDS: X - EXIT, HELP, INFO OR CHOOSE A MENU OPTION 18.05.34
142
CentricStor on z/OS
The POOL DEFINITION ENTRY PANEL will show up:
-------------- CONTROL-M/Tape POOL DEFINITION ENTRY PANEL --------(TP)
COMMAND ===>
SPECIFY LIBRARY, TABLE NAME, POOL NAME
LIBRARY ===> CTTP.PROD.PARM
TABLE
===>
POOL
===>
(Blank for table selection list)
(Blank for pool selection list)
USE THE COMMAND "SHPF" TO SEE PFK ASSIGNMENT 14.34.11
Press enter to see which pool tables are defined.
TABLES OF LIBRARY CTT.PROD.PARM
-------------(TP)
COMMAND ===>
SCROLL===> CRSR
OPT NAME --------- VV.MM CREATED
CHANGED
SIZE INIT MOD
ID
S
$$POOL
01.01 07/08/03 07/09/11 09:33
41
41
0 TADMIN
$$VAULT
01.01 07/08/03 07/10/13 12:09
70
70
0 TADMIN
===== >>>>>>>>>>>> NO MORE TABLES IN THIS LIBRARY <<<<<<<<<<<<<< =====
$$POOL is a default pool that should exist in your installation. Select this pool and you will
see the defined pools of your Control-T.
POOLS OF LIBRARY: CTT.PROD.PARM
TABLE: $$POOL
COMMAND ===>
SCROLL===> CRSR
OPT POOL ----------------- DESCRIPTION ------------------------------ACSTAPE
VOLUMES OF AUTOMATIC TAPE LIBRARY
I
MANUAL
DAILY BACKUP TAPE
===== >>>>>>>>>>>>>>> NO MORE POOLS IN THIS TABLE <<<<<<<<<<<<<<< ====
OPTIONS: S SELECT D DELETE I INSERT
13.58.23
Select I to insert a new pool. The panel will be refreshed with an insert line, where you enter
the new pool name and the description. Press enter again and you can now define details
of the pool. Make sure, that you are in EDIT mode.
-------------- POOL CSLVG01
TABLE $$POOL -------(TP.S)
COMMAND ===>
SCROLL===> CRSR
+--------------------------------------------------------------------+
POOL NAME
CSLVG01
OWNER DP1
DESCRIPTION CENTRICSTOR LOGICAL VOLUME POOL 01
DESCRIPTION
======================================================================
VOLUMES FROM A00000 TO A09999
===== >>>>>>>>>>> END OF POOL DEFINITION PARAMETERS <<<<<<<<<<<< =====
FILL IN POOL DEFINITION. CMDS: EDIT, SHPF
13.58.59
143
CentricStor on z/OS
You may enter multiple ranges for a given pool. Save your ranges and select TR in the IOA
Primary Option Menu.
-------------- CONTROL-M/Tape RULE DEFINITION ENTRY PANEL --------(TR)
COMMAND ===>
SPECIFY LIBRARY, TABLE NAME, RULE NAME
LIBRARY ===> CTTP.PROD.RULES
TABLE
===>
RULE
===>
AUTOMATIC RULE SORTING
SHOW SCHEDULING CRITERIA
SHOW RULE DOCUMENTATION
AUTO-SAVE DOCUMENTATION
===>
===>
===>
===>
(Blank for table selection list)
(Blank for rule selection list)
Y
Y
N
N
(Y/N)
(Y/N)
(Y/N)
(Y/N)
USE THE COMMAND "SHPF" TO SEE PFK ASSIGNMENT
09.10.15
When you press Enter, the Rule Definition Facility Table List Screen appears and you can
select the rules table, where you want to add your pooling rules.
TABLES OF LIBRARY CTT.PROD.RULES
--------(TR)
COMMAND ===>
SCROLL===> CRSR
OPT NAME -------- VV.MM CREATED
CHANGED
SIZE INIT MOD ID
S RULTAB01
01.01 00/08/08 00/08/08 08:05
70
70
0 TADMIN
===== >>>>>>>>>>>>> NO MORE TABLES IN THIS LIBRARY <<<<<<<<<<<<<< ====
OPTIONS: S SELECT B BROWSE D DELETE
14.35.05
RULES OF LIBRARY: CTT.PROD.RULES
TABLE: ADM0002
COMMAND ===>
SCROLL===> CRSR
OPT RULE --------------- DESCRIPTION --------------------------------I
CATALOG KEEP WHILECATALOGUED
===== >>>>>>>>>>>>>> NO MORE RULES IN THIS TABLE <<<<<<<<<<<<<<<<< ===
OPTIONS: S SELECT D DELETE I INSERT C COPY
09.33.22
Select I to insert a new rule. The panel will be refreshed with an insert line, where you enter
the new rule name and the description. Press enter again and you can now define details of
the rule. Make sure, that you are in EDIT mode.
144
CentricStor on z/OS
RULE: HSMML2 LIB CTT.PROD.RULES
TABLE:RULTAB01
COMMAND ===>
SCROLL===> CRSR
+--------------------------------------------------------------------RULE NAME
HSMML2
GROUP PRODUCTION
MODE PROD (Prod/Test)
OWNER
TADMIN
SEQUENCE PRIORITY 01
CONTINUE SEARCH N (Y/N)
DESCRIPTION HSM MIGRATION LEVEL 2 VOLUMES IN CENTRICSTOR
DOCMEM
JOBDOCS
DOCLIB CTT.PROD.DOC
======================================================================
ON DATASET = DFHSM.HMIGTAPE.*
And/Or/Not
======================================================================
DO POOL _ CSLVG01
DO
======================================================================
===== >>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<< ====
FILL IN RULE DEFINITION. CMDS: EDIT, SHPF, DOC, SCHED, DOOPT, ONOPT
Save your modifications and activate the configuration using CTTINIT.
i
This example represents only a simple rule by data set name. If you have more
complex rules or nested rules, please refer to the CONTROL-M/Tape User Guide.
The result of this implementation is, that Control-T will issue its own mount messages and
suppress the original messages IEC501A and IEF233A. The Control-T messages are
copies of the originals, where the string PRIVAT or SCRTCH is replaced by the corresponding poolname and the message prefix is replaced by a Control-T identifier.
Example
IEC501A M 5540,PRIVAT,SL,COMP,DFHSM,STEP1,DFHSM.HMIGTAPE.DATASET
CTT101A M 5540,CSLVG01,SL,COMP,DFHSM,STEP1,DFHSM.HMIGTAPE.DATASET
4.6.3.3
Volume Definition and Initialisation with Control-T
have to be initialised using CTTTPI.
Please refer to the checklist at the end of the chapter for the recommended sequence.
After the LVs are defined in CentricStor, you can start the initialisation process (only if Auto
Labelling is disabled).
//CTTTPI
//*
//CTTTPI
JOB ........
EXEC PGM=CTTTPI,REGION=8M
145
CentricStor on z/OS
//STEPLIB DD DISP=SHR,DSN=BMC.IOA.V610.LOAD
//
DD DISP=SHR,DSN=BMC.IOA.V610I.CTRANS
//DAPARM
DD DISP=SHR,DSN=BMC.IOA.V610I.PARM
//
DD DISP=SHR,DSN=BMC.IOA.V610I.IOAENV
//SYSABEND DD SYSOUT=*
//DAMDB
DD DISP=SHR,DSN=MVSA.BMC.CTT610.MDBD.E000
//DAMDI
DD DISP=SHR,DSN=MVSA.BMC.CTT610.MDBI.E000
//DATRC
DD DISP=SHR,DSN=MVSA.BMC.CTT610.TRC
//CTTTPICT DD UNIT=SYSDA,SPACE=(TRK,1)
//CTTTPITP DD UNIT=(CSTOR,,DEFER),DISP=(NEW,KEEP,KEEP)
//SYSIN DD *
TYPERUN MDBUPDAT=Y,ADD=Y,PROTECT=NOREAD
INITT SER=A00000,NUMBTAPE=1000,MEDIA=CS2GB
/*
The parameters used are:
MDBUPDAT=Y
ADD=Y
PROTECT=NOREAD
MEDIA=mediatype
NUMBTAPE=count
a volume entry, that is initialised, is rebuild in the media database
no need to define the LVs in the media database. They are registered by the init process.
avoid read errors of uninitialized volumes.
may be used to assign a name for references, e.g. is used in scratch
sync script. For ease of use, a single medianame should be
assigned to all CentricStor logical volumes.
maximum count is 9999
i
CentricStor:
1.
2.
3.
4.
5.
6.
7.
1
Initialise the LVs with CTTTPI 1
Define volumes to the Media Database 2
In case of HACC now run the scratch synchronisation process
2
If Auto Labelling is enabled
3
146
CentricStor on z/OS
Host Software Component - HSC
4.7 Host Software Component - HSC
Part of the SUN/STK software suite NCS is the Host Software Component - HSC. The HSC
is used to control a SUN/STK physical library and in addtion with the Virtual Tape Control
System (VTCS) feature used to control a Virtual Storage Manager (VSM). It also is base to
perform an ACSLS type server communication which may be used to control a backend
library of a CentricStor configuration. HSC may also be installed, if native tape drives on a
SUN/STK library are used by z/OS. Another option is to use an additional CSC instance for
the native tape drives and to control the library via an ACSLS server. HSC has only an
indirect relationship to CentricStor as it may be the vehicle to perform backend mounts via
Library Station. For further details on HSC, please consult the corresponding SUN/STK
documentation.
147
Library Station
CentricStor on z/OS
4.8 Library Station
Another part of the SUN/STK software suite NCS is the feature Library Station. This is the
communication interface for the ACSLS server type setup. Library Station runs within the
address space of the HSC. This chapter assumes that an active HSC environment is
already in place.
The following diagramm shows a z/OS system, that supports a CentricStor backend configuration via LibStation/HSC.
CentricStor with SUN/STK Library – Backend Control via LibStation/HSC
z/OS
ICP – Integrated Channel
Processor
HSC
IDP – Integrated Data
Processor
VLP – Virtual Library
Processor
PLS – Physical Library
Services
LibStation
SMC
TCP/IP
CSC
VACS – Virtual ACSLS
FICON
Fiber Channel
LAN
ICP
SUN/STK Library
CentricStor
VLP
Library Control
!
IDP
PLS
VACS
CAUTION!
Note that the CentricStor frontend and backend connection work totally
independent from each other.
There are three typs of communucation:
148
●
CSC talks to VACS to perform CentricStor virtual mount.
●
CentricStor Physical Library Services talks to LibStation to perform physical mounts.
●
Physical mounts, either CS backend or z/OS native, are issued by HSC to Library
Control communication.
CentricStor on z/OS
Library Station
If you want to use the Library Station software to control your CentricStor backend drives,
make sure that the required FMIDs are installed. Please refer to section “Installation and
Customisation” on page 74 for more details.
After the software is SMP/E installed, set up the HSC environment to map the new configuration. CentricStor drives have to be dedicated. Run the LIBGEN process to include the
new drives and/or library and add a HOSTID for drives, that are controlles by LibStation.
Refer to the HSC Configuration Guide for details on the LIBGEN process and also the
LibraryStation Configuration Guide.
The following description should only give you an idea what tasks are necessary to
complete the LibStation setup.
1. Update the HSC parameters by adding the LibStation definitions:
a) Include the location for the software license key:
LKEYDEF DSN('your.SLSPARM(LKEYINF1)')
b) Include the LSINIT statement:
LSINIT NETHOST(CLI1) COMMONSP(SPCSTOR)
COMMTYPE(TCPIP) TCPNAME(TCPIP) CREQLOG(YES)
HOSTID(SYSA) LSDEF('your.SLSPARM(LSDEFRO2)')
PDF('your.PDFRO2') PDFX('your.PDFRO2.PATH')
-
NETHOST states the HOSTID for LibStation that was defined during LIBGEN.
COMMONSP defines the default scratch pool name.
COMMTYPE(TCPIP) is used to connect CentricStor.
HOSTID defines which LPAR is running the Library Station in a multi HSC
environment.
LDDEF is the location of your Library Station definitions, where you define pools
based on IP-addresses.
PDF and PDFX define the Persistent Data File (VSAM).
2. Create the member that represents the LSDEF statements:
SPNUM NUM(31) SPNAME(SPPVG01) IPADDR(192.50.35.133)
SPNUM NUM(32) SPNAME(SPPVG02) IPADDR(192.50.35.133)
i
Please note, that the subpool numbers which are defined here are HSC pool
IDs. They are not CentricStor pool IDs.
3. Update the parameter member, that defines the scatch pools to reflect the entries in the
LSDEF definitions:
SCRPO NAME(SPPVG01),RANGE(P10000-P10499),LABEL(SL)
SCRPO NAME(SPPVG02),RANGE(P20000-P20299),LABEL(SL)
i
There may be other tasks necessary to complete the LibStation setup. For example
you may also include RACF security mechanisms.
149
User Exits and Scripts
CentricStor on z/OS
4.9 User Exits and Scripts
The following user exits and scripts referenced in previous chapters may be downloaded
from
Service partner portal ➟ Storage ➟ CentricStor ➟ Documentation ➟ add-on
➟ Integration_with_IBM_Mainframes
https://partners.fujitsusiemens.com/com/service/storage/CentricStor/Pages/default.aspx?CurrentFolder=2fc4ba9d-97be-412f-a09a-3be145877853
150
Name
Description
UX01RMM
RMM Scratch Subpooling User Exit for CSC Attachment
UX01CA1
CA1 and TLMS Scratch Subpooling User Exit for CSC Attachment
UX01CTLT
Control-T Scratch Subpooling User Exit for CSC Attachment
SCRCSC
REXX Procedure to map SCUCONDB output to required format
SCRCNTLT
REXX Procedure to Extract Control-T Scratch Volumes
5 CentricStor on UNIX-type systems
5.1 Linux
5.1.1 EMULEX LP8000 controller
!
5.1.1.1
The LP8000 controller has still not been released on Linux. The settings described
below are advance information.
Linux RedHat (not officially released)
●
EMULEX driver for Linux version 4.02f.
●
The driver module provided by EMULEX only runs under RedHat 6.2.
●
The open source cannot be translated.
●
The Topology setting must be changed in the file lpfc.conf.c for a switch connection
(parameter == 2).
●
The shell procedure MAKEDEV must be adapted accordingly.
●
/etc//lilo.con must be extended by the following entry, in order to see more than
8 LUNs:
append="max_scsi_luns=128" (also see description by EMULEX).
●
Activation of the modprobe lpfcdd or insmod lpfcdd drivers.
●
Error messages etc. are in the file: /var/log/messages
●
Problems and troubleshooting:
Kernel Panic:
●
Set the interrupt of LP8000 to 11.
If further problems arise: remove LP8000 and reboot. Load Lpfcdd. Then reinstall the
board.
151
Linux
5.1.1.2
CentricStor on UNIX-type systems
SuSE Linux
EMULEX Driver for Linux version 4.02f
●
As finished object modules are only delivered for RedHat 6.2, the open source must be
translated. For this, the kernel sources, which are not installed as standard, must be
present on the machine.
●
The shell script issmp must be adapted as appropriate for a multi-processor system.
Using grab, search for SMP instead of smp. In a multi-processor system, the version with
the extension -SMT must be entered in the file /usr/include/linux/version.h .
●
The Topology setting must be changed in the file lpfc.conf.c for a switch connection
(parameter == 2).
●
/etc/lilo.conf need not be adapted.
●
Activation of the driver with modprobe lpfcdd or insmod lpfcdd.
Overview of driver versions
Controller
LINUX version Driver
Version
Source
LP9002
SuSe 8.1
lpfcdd
4.20p
FSC
LP9802
SuSe 8.1
lpfcdd
4.20p
FSC
5.1.2 Qlogic QLA2200F Controller
5.1.2.1
5.1.2.2
152
Linux RedHat 6.2
●
Linux driver for RedHat 6.2. Version: V2.23/1.19.10 from Qlogic
●
BIOS version of card: 1.61
SuSE Linux 7.1 ·
●
Linux driver for RedHat 6.2. Version: V2.23/1.18.10 from Qlogic
●
BIOS version of card: 1.61
●
Linux kernel version: 2.2.18
●
The open source code must be translated. For this the kernel sources must be read in.
●
Then the kernel must be recreated, as the kernel delivered by SuSE does not exactly
fit the sources which have been loaded (see Building the Kernel).
5.1.2.3
Linux
SuSE Linux 8.0 Professional
●
With the driver qla2x00, delivered with kernel 2.4.18, version 5,.38b16 is used.
Note:
The message in /var/log/boot.msg gives an incorrect driver version:
<6>scsi0 : QLogic QLA2200 PCI to Fibre Channel Host Adapter: bus 0 device 13 irq 9
<4>
Firmware version: 2.01.37, Driver version 4.46.5
●
BIOS version of the card: 1.54 or 1.61 or 1.72 or 1.77 (recommended). Fujitsu-Siemens
has extensively tested the named versions.
●
Linux kernel version: 2.4.18.
The Open Source code must be translated. For this the kernel sources must be read in.
The variable OSVER must have exactly the same name in the make file as in the
directory where the Linux source is located (e.g. linux).
●
The driver contained in the SuSE distribution has a error which prevents the tape from
being ejected from the drive. The LUN_NOT_READY from the drive is wrongly seen as
an error, and because of this the command is not executed. You can get round this
function call by commenting out qla2x00_check_sense in line 9964.
●
As the emulations from CentricStor register themselves as SCSI-II drives, only the first
8 LUNs are scanned in the kernel 2.4.18 (except for the IBM-3590 emulation). Further
drives must be added with the following command after every reboot:
echo "scsi add-single-device a b c d" > /proc/scsi/scsi
Where:
a
b
c
d
= Host adapter ID
= SCSI channel on the host adapter (for multi-channel HA)
= SCSI ID
= SCSI LUN
The following is a small Perl script which adds all LUNs from 8 to 32.
------------------------------------------------------------------------
#!/usr/bin/perl
$ILoop = 0;
for ( $ILoop = 8; $ILoop < 32; $ILoop++) {
system("echo \"scsi add-single-device 1 0 0 $ILoop\" >
/proc/scsi/scsi");
}
------------------------------------------------------------------------
From kernel version 2.4.19, the CentricStor emulation is recognized automatically with
32 LUNs.
153
Linux
Notes on Linux on Primergy B210
The ServerWorks chip set used with B210 still does not appear to run sufficiently stably with
the standard kernel. During test applications running for several hours, complete crashes
continued to occur frequently. The system only ran stably when a single processor kernel
with the following kernel boot parameter was created:
noapic
nmi_watchdog=0
There has been lot of information about this in the newsgroups, it is most likely that this error
will be solved in the next kernel version.
Overview of driver versions
Controller
Linux
version
QLA2200
1
154
Driver
Version
Source
Notes
SuSe 8.0 qla2x00
4.46.5
supplied in kernel
SuSe 8.0 qla2x00
4.47.11
FSC
only sees 8 LUNs 1
SuSe 8.1 qla2200 6.1b2
supplied in kernel
SuSe 8.1 qla2x00
FSC
4.47.11
only sees8 LUNs 1
According to the SCSI2 protocol, only 3 bits (0-7) should be used for LUNs. In the old QLOGIC driver version
this rule was not applied so strictly. In FSC version 4.47.11 this is handled more strictly. If more than 8 devices
are required, you should return to using the old drivers.
Linux
Notes on missing device nodes
If a tape emulation (e.g. V104) is not available on the ICP, then at boot the Linux host
automatically only sees the device area, i.e.in this example it only sees from V100 to V103.
This situation can arise if during the Linux boot, vtd emulations were stopped directly in an
ICP.
If vtd V104 is stopped on the ICP, you will find the following messages on a Linux host in
/var/log/messages:
...
Sep 30 14:09:19 mhpabhsc kernel: st: Version 20020205, bufsize 32768,
wrt 30720, max init. bufs 4, s/g segs 16
Sep 30 14:09:19 mhpabhsc kernel: Attached scsi tape st0 at scsi0, channel
Sep 30 14:09:21 mhpabhsc kernel: isapnp: Scanning for PnP cards
...
0,
0,
0,
0,
id
id
id
id
0,
0,
0,
0,
lun
lun
lun
lun
0
1
2
3
The higher LUNs can be added with add-single-device, if necessary, by using the modified
Pearl script from page 153.
#!/usr/bin/perl
# LUNs einrichten: siehe /proc/scsi/scsi
for ( $iLoop = 4; $iLoop < 8; $iLoop++) {
system("echo \"scsi add-single-device 0 0 0 $iLoop\" > /proc/scsi/scsi");
}
This makes 3 further LUNs (device nodes) visible to the host.
/var/log/messages:
...
Sep 30 14:27:13 mhpabhsc kernel: Attached scsi tape st4 at scsi0, channel 0, id 0, lun 5
...
!
CAUTION!
This action may cause the previous assignment of Linux - device nodes to
CentricStor - LUN / or to CentricStor - LibDevName (i.e. VDAS name/VACS
co-ordinates).
155
Linux
Data compression
On the host side, the compression in CentricStor is activated for a (logical) device with the
mt command. For this to occur, the virtual drive must be configured with
Compression = Host.
Example:
# mt -f /dev/nst0 datcompression 2
compression ***
Compression on.
*** Activate
compression ***
Compression off.
*** Deactivate
***
Compression off.
*** Status display
The setting is only effective if the (logical) volume is unloaded before the mt. With an mt on
a loaded volume, the change in compression modes is not effective. This behavior depends
on CentricStor.
–
–
–
–
–
For the CentricStor emulation FSC/CentricStor, compression at the host is turned off by
default.
For the CentricStor emulation EXABYTE/Mammoth2, compression at the host is
switched on as default.
The last activation or deactivation on the Linux host is still valid after the Linux reboot.
After the restart of the tape emulation (vtd), the default (see above) is again valid.
The compression at the host of the device node can also be configured in Linux with the
program stinit. In this case multiple or all drives can be configured at once without a tape
being mounted. A definition file must be created. This file has the following format:
manufacturer=FSC model = "CentricStor" {
mode1 blocksize=0 compression=0 # 0=not 1=compressed
}
The function call is then, for example:
stinit -f <DefFileName> /dev/st13 /dev/st14 /dev/st15 ...
Generally:
stinit [-f conf-file] [-h] [-p] [-r] [-v] [devices...]
The other Linux tape modes (/dev/st*, /dev/st*l, /dev/st*m, /dev/st*a) can
also be configured in this way.
156
Linux
5.1.3 ST Linux SCSI tape driver
The ST driver with the old Linux kernel (< 2.6) only supports a maximum of 32 drives as
standard. As of Linux kernel 2.6 more than 64 ST devices can be generated. Information
on generating drive nodes:
Rewind drive nodes:
Drive
Major
Minor
0
9
0
1
9
1
2
9
2
NoRewind drive nodes:
Drive
Major
Minor
0
9
128
1
9
129
2
9
130
There are various other drive nodes and these all use a different ModePage. However,
these are not relevant to for the CentricStor connection.
The nodes are created with the command: mknod st0 c 9 0.
There are two methods for creating the device nodes:
1. Adapting the MAKEDEV file in the /dev directory
st[0-9]|st[123][0-9])
major=`Major st 9`
unit=`suffix $arg st`
makedev st${unit} c $major $unit $tape
makedev nst${unit} c $major `math 128 + $unit` $tape
makedev st${unit}l c $major `math 32 + $unit` $tape
makedev nst${unit}l c $major `math 160 + $unit` $tape
makedev st${unit}m c $major `math 64 + $unit` $tape
makedev nst${unit}m c $major `math 192 + $unit` $tape
makedev st${unit}a c $major `math 96 + $unit` $tape
makedev nst${unit}a c $major `math 224 + $unit` $tape
;;
Creating device nodes with cd /dev; ./dev/MAKEDEV st10.
157
Linux
2. A small Perl script:
#!/usr/bin/perl
$iLoop = 0;
$NonRewindDevice = 0;
system("mknod st$iLoop c 9 $iLoop");
$NonRewindDevice = 128 + $iLoop;
system("mknod nst$iLoop c 9 $NonRewindDevice");
}
!
CAUTION!
When using configuration or application programs such as Spheras or GamSam, it
may be necessary to generate additional SG device nodes. Consequently a brief
example script for the nodes from 16 through 64 is provided below:
#!/usr/bin/perl
$iLoop = 0;
system("mknod /dev/sg$iLoop c 21 $iLoop");
}
5.1.4 Uniquely assigned device node to LUN in Linux
Scsidev is a tool used to obtain unique names for SCSI devices in Linux.
The names usually given by Linux do not reflect physical relationships in any way.
To get round this problem, you can use the program ScsiDev to be found under
http://www.garloff.de/kurt/linux/scsidev/.
Installation: after unpacking the package, the following is sufficient:
configure
make
make install
to install the program.
There is also a patch file in the package which extends the local boot file, so that at each
system start the SCSIDev device files are created. The following commands are sufficient
for patching:
cd /etc/init.d
patch -p0 -i <SCSIDev-Directory>/boot.diff
158
Linux
Depending on the system, you must do some manual follow-up work. With a SuSE 8.0
installation, for example, both lines
test -z "$DO_FREE_RAM4"
unset DO_FREE_RAM4
|| freeramdisk /dev/ram4
must be added by hand in line 82.
If any SCSI driver is loaded as a module, in /etc/modules.conf the alias
scsi_hostadapter
should be set to the corresponding SCSI adapter, or in line 41
modprobe scsi_hostadapter
should be set to the corresponding module name.
At every restart, the SCSI-Dev device names are immediately present under /dev/scsi.
The names (for tape drives) are made up as follows:
nsth1-0c0i0l0
nsth1-0c0i0l1
sth1-0c0i0l0
sth1-0c0i0l1
The n before the name indicates a non-rewinding device.
The st indicates the type of device files and corresponds exactly to the name which is
normally found in the /dev/ directory.
h1-0 is an attempt to make a unique name for the host adapter.
c0 is an indicator for the channel
i0 is an indicator for the SCSI ID
l0 is an indicator for the SCSI LUN
i.e.
[n][type of device][SCSI adapter]c[Channel]i[SCSI ID]l[LUN]
159
Linux
5.1.5 Building the kernel
With an SMP kernel:
1. On UTS_RELEASE in /usr/include/linux/version.h, check and adapt as appropriate.
2. On EXTRAVERSION in /usr/src/linux/Makefile, check and adapt as appropriate.
cd /usr/src/linux
make xconfig
Configuring via graphical interface.
With Primergy B210 where the boot disk is connected via Adaptec, ensure that the Adaptec
driver is active. The Symbios driver must be deactivated.
make dep
make clean
make bzImage
cp arch/i386/boot/bzImage /boot/vmlinuz.js (e.g.)
Next, adapt /etc/lilo.conf as appropriate or add a new module.
mk_initrd –k vmlinuz.js –i initrd.js
lilo
make modules_install
Then you can boot with the new system.
160
Reliant UNIX
5.2 Reliant UNIX
5.2.1 Requirements
5.2.1.1
Versions of Reliant UNIX
CentricStor functions fully, i.e. with compression and 64 logical drives, with the following
versions:
–
–
–
5.2.1.2
5.45 B00 + EKS SIY5B063
5.45 B10 + EKS SIY5B124
5.45 B20 (and later versions)
FCdriver for EMULEX LP8000
i
Reliant UNIX is connected to CentricStor via the FC controller EMULEX LP8000.
With the RM6001 there is a line for each FC controller (in this case 4 controllers) in the file
/etc/controller . The line is as follows:
.
#ctlr_type:
cab_id:
bus_id:
chan:
mbp:
fc :
log_no:
0 :
bus_type:
pci :
16 :
206 :
slot_id:
4 :
7 :
:
fc :
1 :
pci :
16 :
238 :
4 :
7 :
fc :
2 :
pci :
16 :
238 :
5 :
6 :
fc :
8 :
pci :
16 :
206 :
5 :
6 :
:
option
1
:
1
:
If an FC switch is connected and the switch protocol is used, a 1 must be entered in the
option column.
If a hub is connected, or if there is a direct link to another participant, the field must be left
free (AL protocol).
1
For the RM400, see the man pages on the command upd_channel_id
161
Reliant UNIX
5.2.2 Device configuration
5.2.2.1
Compressed WWNs in the device nodes
To avoid excessively long names in the device nodes, the WWNs in Reliant UNIX have been
compressed from 16 to 5 characters. To find the assignment of WWNs to the compressed
WWNs, use the command autoconf -F:
# autoconf -F
Fibre Channel Configuration:
fc/fc0 FC LP6502-OS [FW
iof0/stape.09.912a1
iof0/stape.09.d9277
iof0/stape.09.c9fcc
2.12 00], Top.: FC_AL, state: DOWN
3.02 00], Top.: PT-PT FABRIC, state: READY
10000000c924f6c1 D_ID 01.12.00 L_ID 126
10000000c92610c3 D_ID 01.11.00 L_ID 126
10000000c924f66f D_ID 01.10.00 L_ID 126
2.12 00], Top.: FC_AL, state: DOWN
3.02 00], Top.: PT-PT, state: DOWN
Here you can see that three host bus adapters for the LP8000 are recognized on the other
side of the switch (PT-PT FABRIC) via the FC controller 09.
If a zoning was configured on the switch, as in the zoning example on page 375, the host
bus adapter of ICP2 (see the section with the grey background on the table below) would
not have been recognized. This means that the device nodes of ICP2 could not initially be
created and access to the LDs would not at first be possible.
In order to find out the ICP assignments, make a comparison with the WWNs of the FC
controller:
compressed WWN
WWPN
Open Systems ICP
912a1
10:00:00:00:c9:24:f6:c1
ICP2
d9277
10:00:00:00:c9:26:10:c3
ICP1
c9fcc
10:00:00:00:c9:24:f6:6f
ICP0
i
162
If several FC controllers are connected to the same fabric (without zoning) on
CentricStor, the other controllers can also see all the ICPs; this means that all the
logical devices (see following section) can also be seen from various locations.
However, they can only be accessed via different paths. A dedicated assignment
should be made here via the zoning in the switch. This is so that the HW configuration can be automatically switched over to a different path.
5.2.2.2
Reliant UNIX
Logical drives in the autoconf -l
i
Requirement: installation of the package SI_draid.
# autoconf -l
fc/fc2 FC LP8000-OS [FW 3.02 00], Top.: PT-PT FABRIC, state:
READY
iof0/sport.09 FCP
iof0/stape.09.912a1 Centric Stor
iof0/stape.09.912a1.1 Centric Stor
...
iof0/stape.09.d9277 Centric Stor
iof0/stape.09.d9277.1 Centric Stor
...
iof0/stape.09.c9fcc Centric Stor
iof0/stape.09.c9fcc.0 Centric Stor
...
The device nodes under /dev/iof0/ in Reliant UNIX
raw tape device
FC controller
compressed WWNN (ICP)
LUN (logic device number)
n = no rewind, c=compression
/dev/iof0/rstape.09.921a1.63n
Only the following two types of device node may be used in NetWorker with the CentricStor
logical device:
/dev/iof0/rstape.09.921a1.63n
/dev/iof0/rstape.09.921a1.63cn
no rewind
compression & no rewind
163
Reliant UNIX
If no zoning is used, all the ICPs will be visible and, as a consequence, so will the logical
devices on the ICPs. As a rule, each host is only assigned its own LDs, while the other LDs
remain with other hosts.
!
CAUTION: At this point a clean configuration is needed in order to avoid unwanted
access to external LDs. We therefore recommend that you use symbolic links with
more meaningful names (with ICP and LD name in CentricStor) only for those LDs
which are to be accessed by this host. (An example of a more meaningful name
would be vt for virtual tape):
Link
UNIX device nodes
/dev/vt/STAR-ICP0/V000n
/dev/vt/STAR-ICP0/V000cn
...
/dev/vt/STAR-ICP0/V01Fn
/dev/vt/STAR-ICP0/V01Fcn
/dev/iof0/rstape.09.c9fcc.0n
/dev/iof0/rstape.09.c9fcc.0cn
...
/dev/iof0/rstape.09.c9fcc.31n
/dev/iof0/rstape.09.c9fcc.31cn
...
/dev/iof0/rstape.09.d9277.00c
/dev/iof0/rstape.09.d9277.00cn
...
/dev/iof0/rstape.09.d9277.15c
/dev/iof0/rstape.09.d9277.15cn
Example of a shell script for creating links:
# create-vt-links
cd /dev
mkdir vt
# 1st 32 LDs on ICP0 :
ln -s /dev/iof0/rstape.09.c9ffc.0n
..
ln -s /dev/iof0/rstape.09.c9ffc.31cn /dev/vt/STAR-ICP0/V01Fcn
# 1st 16 LDs on ICP1 :
ln -s /dev/iof0/rstape.09.d9277.0n
..
ln -s /dev/iof0/rstape.09.d9277.15cn /dev/vt/STAR-ICP1/V10Fcn
Wherever possible you should use the same nomenclature on the other hosts. Only these
links should be entered in the NetWorker configurations subsequently.
There is a further advantage if the FC controller is reconfigured on a host. In this case all
device nodes (controller numbers) are changed on the right-hand side, and the symbolic
links on the left-hand side point to invalid destinations. In other words, although all the links
must be recreated, the entries in the host applications (e.g. NetWorker) remain unchanged.
164
Solaris
5.3 Solaris
5.3.1 Requirements
●
Versions 7, 8, 9 and 10 are supported (2.6 on request).
●
To operate tape drives in Solaris V8, at least the following patches must be present on
the system:
108725-09, 108528-15, 108987-09, 111111-03 and 112396-02.
Without these patches there will delays in defining drives, especially under Tivoli.
●
The EMULEX LP9802DC FC controller may not be used.
5.3.2 Useful commands and URLs
●
The current patch level of the system can be found with the command: uname –a.
The result is, for example:
SunOS HAI 5.8 Generic_108528-09 sun4u sparc FJSV,GPUU
In the example, patch level 108528 is installed.
●
For information about more recent patches, visit the SUN internet site at
http://www.sun.com ➟ Support ➟ Patches ➟ Recommended & Security Patches.
You can get information here on which cluster patches are current for the systems.
●
Homepage of IP SQ SF (Solutions & Field Support) on the intranet:
http://utensil.pdb.fsc.net
●
Service Partner Portal on the extranet:
http://extranet.fujitsu-siemens.com/servicepartners/service_partner_portal.html
165
Solaris
5.3.3 Important settings and information
●
You must be operating with the tape driver st.
●
The requirements for CentricStor are:
–
–
FC driver lpfc version V5.01A.
FW version 3.90A7 with FC controller LP8000 from EMULEX.
Solaris does not permit two FC controllers to bind to the same WWPN. This is also not
permitted in CentricStor because it would otherwise bind two different device nodes to
the same logical device. This is not supported by the backup tools.
!
●
CAUTION: If lpfc V4.21e and LP8000-FW 3.82a1 are used, a connection via
the FC switch from an FC controller in the host can only be made to an FC
controller in the ICPs. For each FC controller in the ICPs, there must be a
dedicated FC controller in the host.
If a new zone is defined and activated in a fabric, all Solaris systems connected to this
fabric will report an error. The file /var/adm/messages gives this message, for
example:
WARNING: lpfc0:120:Device disappeared, nodev timeout: …
●
On FSC/Fujitsu Solaris systems reservation problems can occur with the emulations.
These are caused by the chktapecln daemon, which runs every 6 hours.
You must proceed as follows to disable this daemon:
Ê
cp /etc/opt/FJSVmadm/hardmontab /etc/opt/FJSVmadm/hardmontab.org
Ê
Delete the following line from the /etc/opt/FJSVmadm/hardmontab file:
2160 /usr/sbin/FJSVmadm/chktapecln
Ê
166
Then call /usr/sbin/FJSVmadm/swhardmon update so that the modifications
become effective.
Solaris
5.3.4 Driver for EMULEX LP8000
The driver lpfc must be installed. It normally consists of the files
/kernel/drv/lpfc and
/kernel/drv/lpfc.conf.
The driver is also on the supplement CD.
The firmware is copied to the directory /opt/SMAW/SMAWfirm. The firmware is loaded with
the flup tool. In Solaris 5.6, the directory is called /opt/SMAW/SMAWfirm6.
Supplement CD 2.0A00-05:
Version
Firmware
4.10e
3.20x4
After booting, you can obtain the driver version and firmware from the file
/var/adm/messages:
Feb 26 07:14:46 lieser lpfc: [ID 253773 kern.notice] NOTICE:
Feb 26 07:14:46 lieser Emulex LightPulse FC SCSI/IP 4.10e
Feb 26 07:14:46 lieser scsi: [ID 107833 kern.notice] /pci@15,4000/fibre-channel@2 (lpfc0):
Feb 26 07:14:46 lieser Binding WWPN 10:00:00:00:c9:23:0a:d7 to FCP/SCSI Target53
Feb 26 07:14:46 lieser scsi: [ID 107833 kern.notice] /pci@15,4000/fibre-channel@2 (lpfc0):
Feb 26 07:14:46 lieser Binding WWPN 10:00:00:00:c9:27:a1:55 to FCP/SCSI Target54
Feb 26 07:14:50 lieser lpfc: [ID 129691 kern.notice] NOTICE: lpfc0: Firmware Rev3.20 (D2D3.20X4)
Feb 26 07:14:50 lieser lpfc: [ID 664688 kern.notice] NOTICE: lpfc0: WWPN:10:00:00:00:c9:23:04:92
WWNN:20:00:00:00:c9:23:04:92 DID 0xb1700
i
The accompanying file lpfc.conf must be adapted as appropriate. For more
information see section “Persistent Binding” on page 172 and the example of the file
lpfc.conf.
167
Solaris
5.3.5 Installation and configuration of QLA2310F SUN
First of all the required updates and patches for Solaris must be installed. To do this you
load the SAN_X.X.X_install_it.tar.Z package from http://www.sun.com/storage/san.
This package contains all the updates and patches and a script for automatic intallation and
for automatic loading of new updates/patches. It also installs the qlc driver.
The qlc driver recognizes the installed QLA2300F SUN HBA and writes some information
to the Systemlog, but it does not recognize any drives. The QLA2300 driver from Sun is
needed. You will find this on the QLogic web site. This package enables you to install the
qla2300 driver with the /kernel/drv/qla2300.conf configuration file. This driver
writes some entries to the /etc/driver_aliases file. These must be removed and the
line qla2300 "pci1077,2300" entered.
The qlc driver must now be removed: rem_drv qlc. The qla2300 driver is then added:
add_drv -c scsi -i "pci1077,2300" -n qla2300. A reconfiguration reboot is then
required: reboot ---r.
To ensure that the same device nodes are always used, persistent binding must be configured. To do this you load the SANblade CLI for Solaris SPARC package from the web site
containing the driver package. Following installation you can configure the driver using the
scli program. This program finds the installed HBA. It can display various attributes and,
among other things, configure persistent binding. You must insert the target ID which is
entered in the st.conf in the appropriate place. The program writes the corresponding
information to the /kernel/drv/qla2300.conf file. After another reconfiguration reboot
the recognized drives should be contained in the Systemlog with the correct target ID.
i
A LUN can also be locked by means of an entry in the driver configuration file
qla23000.conf, for example:
ba0-SCSI-target-id-0-lun-0-disable
168
Solaris
5.3.6 Tape driver st
i
The more recent controller CDs install this tape type already in the st.conf.
To ensure that tape devices can be operated with a LUN <> 0, the file
/kernel/drv/st.conf must be extended as follows:
1. Then the entry for the new device type of the logical drive CentricStor of FSC must be
made in the tape-config-list (the entry for a Magstar drive is shown below):
tape-config-list=
"FSC
",
"IBM
03590B",
centrs
X03590B
=
=
"CentricStor",
"PXT1",
"centrs",
"X03590B";
1,0x36,0,0x18619,1,0x00,0;
1,0x24,0,0x61c439,1,0x00,0;
2. Next, the LUNs to be used from this host must be specified for the connected targets
(ICPs):
#
#
#
#
name="st"
name="st"
...
name="st"
#
#
#
name="st"
name="st"
...
name="st"
#
#
#
#
#
name="st"
name="st"
...
name="st"
STAR-ICP0:
2nd 32 LDs
ctrl-14 :
3rd 16 LDs
class="scsi" target=53 lun=32;
ctrl-15 :
4th 16 LDs
STAR-ICP1:
2nd 16 LDs
ctrl-14 :
2nd 16 LDs
Following a reboot, the CentricStor drives are then recognized and the corresponding
device nodes created.
169
Solaris
i
The target and LUN are specified in hexadecimal form for the device nodes, i.e.:
– 53 becomes 0x35
– 63 becomes 0x3f
In the case of Qlogic HBAs, the st.conf file alone is not decisive for creating the
device node, i.e. the system also creates device nodes when there is no LUN
entry specifying this in st.conf. This means that no LUNs can be masked out in
this way, either. Instead, this must be done using the qla2300.conf file (see section “Installation and configuration of QLA2310F SUN” on page 168).
3. It is advisable to save the modified st.conf file as st.conf.save, for example,
because certain tools will overwrite the file automatically.
The section “Contents of the file st.conf for Solaris” on page 180 shows an example.
After a reboot, the CentricStor drives are recognized.
If there are further targets in the FC loop (e.g. other ICPs, disks or tape devices) further
target numbers appear. The file st.conf must then be appropriately extended. EMULEX
drivers are configured via the file /kernel/drv/lpfc.conf in the same way as the target
numbers of the FC targets are shown in st.conf (previously SCSI IDs).
5.3.7 Device nodes
Solaris creates symbolic links for recognized tape units in /dev/rmt which point to the
device nodes in the /devices/ directory:
lrwxrwxrwx 1 root root 52 Apr 16 14:09 0bn
->
../../devices/pci@1d,2000/fibre-channel@1/st@35,0:bn
lrwxrwxrwx 1 root root 53 Apr 16 14:09 0cbn ->
../../devices/pci@1d,2000/fibre-channel@1/st@35,0:cbn
...
../../devices/pci@1d,2000/fibre-channel@1/st@35,1f:cbn
lrwxrwxrwx 1 root root 53 Apr 16 14:09 32bn ->
...
../../devices/pci@1d,2000/fibre-channel@1/st@36,1f:bn
...
../../devices/pci@1d,2000/fibre-channel@1/st@0,0:cbn
lrwxrwxrwx 1 root root 51 Apr 16 14:09 49bn ->
...
170
Solaris
On the extreme right, in st@35,1f:cbn
– 35 is the target number 53 in hex format,
– 1f is LUN=31 in hex format,
– c: compression mode,
– b: Berkley mode,
– n: no rewind
together these items describe the logical device V01F on ICP0 (see vtls.conf [ ld ]),
The numbers in /dev/rmt (here 0 - 49) are selected by Solaris depending on the configuration.
– 0-31 are the second 32 LDs on ICP0
– 32-47 are the second 16 LDs on ICP1
– 48-49 are the two native Magstar drives via the targets 0 und 1
i
If the two Magstar drives appear at the start, all the link numbers are shifted. In this
case:
– 0-1 would be the two native Magstar drives via targets 0 und 1
– 2-33 would be the second 32 LDs on ICP0
– 34-49 would be the second 16 LDs on ICP1
To avoid unwanted accesses to external LDs, it is thus necessary at this point to create
symbolic links with more meaningful names (with ICP and LD name in CentricStor) for those
LDs that are to be accessed by this host. (An example of a more meaningful name would
be vt for virtual tape):
Link
Solaris device nodes
/dev/vt/STAR-ICP0/V020bn
/dev/vt/STAR-ICP0/V020cbn
…
/dev/vt/STAR-ICP0/V03Fbn
/dev/vt/STAR-ICP0/V03Fcbn
/devices/pci@1d,2000/fibre-channel@1/st@35,20:bn
/devices/pci@1d,2000/fibre-channel@1/st@35,20:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@35,3f:bn
/devices/pci@1d,2000/fibre-channel@1/st@35,3f:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@36,10:bn
/devices/pci@1d,2000/fibre-channel@1/st@36,10:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@36,1f:bn
/devices/pci@1d,2000/fibre-channel@1/st@36,1f:cbn
Wherever possible you should use the same nomenclature on the other hosts. Only these
links should be entered in the NetWorker configurations subsequently.
There is a further advantage if the FC controller is reconfigured on a host. In this case all
device nodes (controller numbers) are changed on the right-hand side, and the symbolic
links on the left-hand side point to invalid destinations. In other words, although all the links
must be recreated, the entries in the host applications (e.g. NetWorker) remain unchanged.
171
Solaris
The LUNs set in CentricStor can be shown via:
i
[GXCC - function bar: Tools ➔ Global Status] ;
Global Status function bar ➔ Tools ➔ Show Balloon Help Summary
5.3.8 Persistent Binding
If a device with SCSI is to be operated in Solaris via FC, a unique ID (SCSI ID) must be
assigned to each target (i.e. the external FC controllers of the ICPs in this case). There are
a number of ways for making this assignment. However, the only secure method is to use
persistent binding, because with the automatic procedure the assignment might go wrong in
a reboot or a reconfiguration. A line is entered in lpfc.conf for each CentricStor controller
to be operated from Solaris:
fcp-bind-WWPN="10000000c922e06b:lpfc0t53";
The 16-position number is the WWPN, the 'World Wide Port Name' encoded in the FC card
in CentricStor.
If the host does not use an ICP logical device, no persistent binding should be entered for
its FC adapter.
An overview of the WWNs for all adapters of the ICP can be shown with:
GXCC - Function bar: Administration ➟ Show WWN’s
i
To show the WWNN and WWPN for an individual host adapter use:
[GXCC object function ➟ ICP… ➟ Show Details]; Host adapter object information
Alternatively, you can find out the number from Solaris in /var/adm/messages after
booting, or in Sinix-Z through /etc/fc/fclog | grep "own port_name", likewise after
booting.
Rules
172
●
The 0 in lpfc0t53 must address the appropriate FC controller.
●
The 53 here is the assigned SCSI-ID, which must be cross-matched with st.conf
(target=53).
●
It is advisable to select a target number outside of the usual range of 0-16 in order to
avoid conflicts with normal tape devices. For example, this avoids a situation where a
normal tape unit on a different (SCSI) controller is checked on the numerous
CentricStor LUNs.
●
If several target systems are linked, the target ID must increase over several FC
controllers. (e.g. lpfc0t53, lpfc0t54, lpfc1t55 - but not lpfc0t53, lpfc1t54,
lpfc0t55).
Solaris
5.3.9 Checking the configuration
Its own FC controller must be logged in on the switch as the F-port. You can check this on
the switch by logging yourself in on the switch through telnet.
SAN_SW10:admin> switchshow
switchName: SAN_SW10
switchType:
2.4
switchState:
Online
switchRole:
Principal
switchDomain:
10
switchId:
fffc0a
switchWwn:
10:00:00:60:69:12:53:3e
switchBeacon:
OFF
port 0: id Online
F-Port
10:00:00:00:c9:21:6b:db
port 1: id Online
F-Port
21:00:00:e0:8b:02:cb:36
port 2: sw Online
L-Port
1 public
port 3: sw No_Light
port 4: id Online
F-Port
10:00:00:00:c9:21:8a:a8
port 5: id Online
F-Port
10:00:00:00:c9:24:f6:2e
port 6: id Online
F-Port
10:00:00:00:c9:22:a6:29
port 7: -- No_Module
port 8: id Online
F-Port
10:00:00:00:c9:21:f6:0c
port 9: id Online
F-Port
10:00:00:00:c9:26:19:fc
Connections from the switch to ICPs and to hosts must be of the F-Port type.
After installing the BASIC Extension from the supplement CD, you can check the accessibility
of the LUNs on the ICP with the following command:
/opt/SMAW/sbin/prtcfg | more
............
sd, instance #0 [c1t0d0]
sd, instance #1 [c1t1d0]
scsi, instance #1
fibre-channel, instance #0
st, instance #21 [rmt/0]
..............
FUJITSU MAJ3182MC
FUJITSU MAJ3182MC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
173
Solaris
5.3.10 Solaris systems in server farms
During a reboot, Solaris scans all LUNs with reserve/release. On server farms this feature can
occasionally cause problems with other host systems. A solution to this problem is to mask
the LUNs in the st.conf file given that Solaris will only scanned the LUNs defined as such
(see section “Contents of the file st.conf for Solaris” on page 180).
5.3.11 Contents of the file lpfc.conf for Solaris
An example of a file modified for CentricStor is shown below. The entries relating to
CentricStor are highlighted in red.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
COPYRIGHT 1997, 1998, 1999, 2000, EMULEX CORPORATION
3535 Harbor Boulevard, Costa Mesa, CA 92626
All rights reserved. This computer program and related documentation
is protected by copyright and distributed under licenses restricting
its use, copying, distribution and decompilation. This computer
program and its documentation are CONFIDENTIAL and a TRADE SECRET
of EMULEX CORPORATION. The receipt or possession of this program
or its documentation does not convey rights to reproduce or disclose
its contents, or to manufacture, use, or sell anything that it may
describe, in whole or in part, without the specific written consent
of EMULEX CORPORATION. Any reproduction of this program without
the express written consent of EMULEX CORPORATION is a violation
of the copyright laws and may subject you to criminal prosecution.
$Id: lpfc.conf 1.7 2000/06/23 23:42:13 mks Exp $
Solaris LightPulse lpfc (SCSI) / lpfn (IP) driver: global initialized data.
# Verbosity: only turn this flag on if you are willing to risk being
# deluged with LOTS of information.
# You can set a bit mask to record specific types of verbose messages:
#
# 0x1
ELS events
# 0x2
Device Discovery events
# 0x4
Mailbox Command events
# 0x8
Miscellaneous events
# 0x10
Link Attention events
# 0x20
IP events
# 0x40
FCP events
# 0x80
Node table events
# 0x1000
FCP Check Condition events
log-verbose=0;
174
Solaris
# Setting log-only to 0 causes log messages to be printed on the
# console and to be logged to syslog (which may send them to the
# console again if it's configured to do so).
# Setting log-only to 1 causes log messages to go to syslog only.
log-only=1;
#
# +++ Variables relating to FCP (SCSI) support. +++
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
Setup FCP persistent bindings,
fcp-bind-WWPN binds a specific WorldWide PortName to a target id,
fcp-bind-WWNN binds a specific WorldWide NodeName to a target id,
fcp-bind-DID binds a specific DID to a target id.
Only one binding method can be used.
WWNN, WWPN and DID are hexadecimal values.
WWNN must be 16 digits with leading 0s.
WWPN must be 16 digits with leading 0s.
DID must be 6 digits with leading 0s.
The SCSI ID to bind to consists of two parts, the lpfc interface
to bind to, and the target number for that interface.
Thus lpfc0t2 specifies target 2 on interface lpfc0.
NOTE: Target ids, with all luns supported, must also be in sd.conf.
scan-down must be set to 0 or 1, not 2 which is the default!!
Here are some examples:
WWNN
SCSI ID
fcp-bind-WWNN=
"2000123456789abc:lpfc1t0",
"20000020370c27f7:lpfc0t2";
fcp-bind-WWPN=
WWPN
SCSI ID
"2100123456789abc:lpfc0t0",
"21000020370c2855:lpfc0t1",
"2100122222222222:lpfc2t2";
DID
SCSI ID
fcp-bind-DID=
"0000ef:lpfc0t3";
BEGIN: LPUTIL-managed Persistent Bindings
fcp-bind-WWPN="10000000c922e06b:lpfc0t53";
#
# If automap is set, SCSI IDs for all FCP nodes without
# persistent bindings will be automatically generated.
# If new FCP devices are added to the network when the system is down,
# there is no guarantee that these SCSI IDs will remain the same
# when the system is booted again.
# If one of the above fcp binding methods is specified, then automap
# devices will use the same mapping method to preserve
# SCSI IDs between link down and link up.
# If no bindings are specified above, a value of 1 will force WWNN
# binding, 2 for WWPN binding, and 3 for DID binding.
# If automap is 0, only devices with persistent bindings will be
175
Solaris
# recognized by the system.
automap=0
# fcp-on:
true (1) if FCP access is enabled, false (0) if not.
fcp-on=1;
# lun-queue-depth:
the default value lpfc will use to limit
# the number of outstanding commands per FCP LUN. This value is
# global, affecting each LUN recognized by the driver, but may be
# overridden on a per-LUN basis (see below). RAID arrays may want
# to be configured using the per-LUN tunable throttles.
lun-queue-depth=30;
# tgt-queue-depth:
the default value lpfc will use to limit
# the number of outstanding commands per FCP target. This value is
# global, affecting each target recognized by the driver, but may be
# overridden on a per-target basis (see below). RAID arrays may want
# to be configured using the per-target tunable throttles. A value
# of 0 means don't throttle the target.
tgt-queue-depth=0;
# lpfcNtM-lun-throttle: the maximum number of outstanding commands to
# permit for each LUN of an FCP target that supports multiple LUNs.
# The default throttle for the number of commands outstanding to a single
# LUN of a multiple-LUN target is lun-queue-depth. For a target that
# can support multiple LUNs, it may be useful to specify a LUN throttle
# that differs from the default.
# Example: lpfc0t17-lun-throttle=48;
# says that each LUN on target 17, interface lpfc0 should be allowed
# up to 48 simultaneously outstanding commands.
# lpfc1t39-lun-throttle=10;
# lpfc0t40-lun-throttle=30;
# lpfcNtM-tgt-throttle: the maximum number of outstanding commands to
# permit for a FCP target.
# By default, target throttle is diabled.
# Example: lpfc0t17-tgt-throttle=48;
# says that target 17, interface lpfc0 should be allowed
# up to 48 simultaneously outstanding commands.
#lpfc1t39-tgt-throttle=10;
#lpfc0t40-tgt-throttle=30;
#
#
#
#
#
#
#
#
#
#
#
#
176
no-device-delay [0 to 30] - determines the length of
the interval between deciding to fail back an I/O because there is no way
to communicate with its particular device (e.g., due to device failure) and
the actual fail back. A value of zero implies no delay whatsoever.
Cautions: (1) This value is in seconds.
(2) Setting a long delay value may permit I/O to build up,
each with a pending timeout, which could result in the exhaustion of
critical Solaris kernel resources. In this case, you may see a fatal
message such as
PANIC: Timeout table overflow
Note that this value can have an impact on the speed with which a
Solaris
# system can shut down with I/Os pending and with the HBA not able to
# communicate with the loop or fabric, e.g., with a cable pulled.
no-device-delay=1;
#
# +++ Variables relating to IP networking support. +++
#
# network-on:
true (1) if networking is enabled, false (0) if not
# This variable will be set during the installation of the driver
# via pkgadd.
network-on=0;
# xmt-que-size: size of the transmit queue for mbufs (128 - 10240)
xmt-que-size=256;
#
# +++ Variables common to both SCSI (FCP) and IP networking support. +++
#
# Some disk devices have a "select ID" or "select Target" capability.
# From a protocol standpoint "select ID" usually means select the
# Fibre channel "ALPA". In the FC-AL Profile there is an "informative
# annex" which contains a table that maps a "select ID" (a number
# between 0 and 7F) to an ALPA. If scan-down is set to a value of 0,
# the lpfc driver assigns target ids by scanning its ALPA map
# from low ALPA to high ALPA.
#
# Turning on the scan-down variable (on = 1,2, off = 0) will
# cause the lpfc driver to use an inverted ALPA map, effectively
# scanning ALPAs from high to low as specified in the FC-AL annex.
# A value of 2, will also cause target assignment in a private loop
# environment to be based on the ALPA (hard addressed).
#
# Note: This "select ID" functionality is a PRIVATE LOOP ONLY
# characteristic and will not work across a fabric.
scan-down=1;
# Determine how long the driver will wait to begin linkdown processing
# when a cable has been pulled or the link has otherwise become
# inaccessible, 1 - 255 secs. Linkdown processing includes failing back
# cmds to the target driver that have been waiting around for the link
# to come back up. There's a tradeoff here: small values of the timer
# cause the link to appear to "bounce", while large values of the
# timer can delay failover in a fault tolerant environment. Units are in
# seconds. A value of 0 means never failback cmds until the link comes up.
linkdown-tmo=30;
# If set, nodev-holdio will hold all I/O errors on devices that disappear
# until they come back. Default is 0, return errors with no-device-delay.
nodev-holdio=0;
# If set, nodev-tmo will hold all I/O errors on devices that disappear
177
Solaris
# until the timer expires. Default is 0, return errors with no-device-delay.
nodev-tmo=0;
# Use no-device-delay to delay FCP RSP errors and certain check conditions.
delay-rsp-err=0;
# Treat certain check conditions as an FCP error.
check-cond-err=0;
# num-iocbs: number of iocb buffers to allocate (128 to 10240)
num-iocbs=512;
# num-bufs: number of ELS buffers to allocate (128 to 4096)
# ELS buffers are needed to support Fibre channel Extended Link Services.
# Also used for SLI-2 FCP buffers, one per FCP command, and Mailbox commands.
num-bufs=512;
# topology:
link topology for initializing the Fibre Channel connection.
#
0 = attempt loop mode, if it fails attempt point-to-point mode
#
2 = attempt point-to-point mode only
#
4 = attempt loop mode only
#
6 = attempt point-to-point mode, if it fails attempt loop mode
# Set point-to-point mode if you want to run as an N_Port.
# Set loop mode if you want to run as an NL_Port.
# topology on all CentricStor controllers is 2.
# Default for other FC connections is topology=4;may require further adjustment.
lpfc0-topology=2;
topology=4;
# Set a preferred ALPA for the adapter, only valid if topology is loop.
# lpfc0-assign-alpa=2; Request ALPA 2 for lpfc0
# ip-class: FC class (2 or 3) to use for the IP protocol.
ip-class=3;
# fcp-class: FC class (2 or 3) to use for the FCP protocol.
fcp-class=3;
# Use ADISC for FCP rediscovery instead of PLOGI.
use-adisc=0;
# Extra FCP timeout for fabrics (in seconds).
fcpfabric-tmo=0;
# Number of 4k STREAMS buffers to post to IP ring.
post-ip-buf=128;
# Set to 1 to decrement lun throttle on a queue full condition.
dqfull-throttle=1;
178
Solaris
# Setting zone-rscn to 1 causes the driver to check with the
# NameServer to see if an N_Port ID received from an RSCN applies.
# If "Soft Zoning" is used, with Brocade Fabrics, this
# should be set to 1.
zone-rscn=0;
# Use ACK0, instead of ACK1 for class 2 acknowledgement.
ack0=0;
# Workaround for PCI nexus driver bug, Solaris 2.5.1 SPARC & x86,
# Solaris 2.6 beta SPARC (and probably x86). The PCI nexus driver
# doesn't recognize PCI_CLASS_SERIALBUS and other relatively recent
# PCI 2.1 specifications. Fibre Channel belongs to PCI_CLASS_SERIALBUS.
# Because the nexus driver doesn't recognize SERIALBUS, it assigns a
# default hardware interrupt priority to the adapter that is LOWER than
# the software interrupt priority, with poor results. By resetting the
# class-code, we pretend that the LightPulse belongs to PCI_CLASS_NET,
# which gets us a decent hardware interrupt priority level. DO NOT CHANGE
# OR COMMENT OUT THIS WORKAROUND UNLESS YOU KNOW THAT THE NEXUS DRIVER
# IS FIXED. [97/07/16]
class-code=0x00020000;
# Used only by i386 FCP (SCSI)
flow_control="duplx" queue="qfifo" disk="scdk";
# Solaris/x86 only: select allocation of memory for DMA. THIS VARIABLE
# CAN AFFECT WHETHER LPFC RUNS CORRECTLY ON AN X86 PLATFORM. The Solaris
# DDI specification mandates the use of ddi_dma_mem_alloc when allocating
# memory suitable for DMA. This memory comes from a pool reserved at
# boot-time and sized by a variable called "lomempages"; this variable
# may be set in /etc/system. The variable defaults to a small value, e.g.,
# 36 pages, which isn't nearly enough for LPFC when running IP. Typically,
# we've cranked the value up to 1100 pages or so. But this pool represents
# precious "low memory" on a PC -- memory below the 16M address boundary.
# This memory is also needed by the OS and other drivers.
#
# On some machines, we can get away with using kmem_zalloc instead of
# ddi_dma_mem_alloc, thus avoiding the requirement to use lomempages.
# However, this trick is NOT portable! Some x86 systems absolutely need
# to use lomempages for their DMA.
#
# So... if you think your x86 system is one of those that requires the
# use of lomempages, set this variable to one. Be sure to pick a suitable
# value for lomempages in /etc/system; the value depends on how many of
# the various kinds of buffers you allocate for IP and SCSI. Otherwise,
# set this variable to zero and relax, as then lpfc can allocate the
# memory it needs without further input from you.
use-lomempages=0;
# Old Open Boot Prom (SPARC): if your SPARC doesn't have a sufficiently
# recent version of OBP, it may be unable to probe and identify a
# LightPulse adapter. You will need to use the following workaround.
179
Solaris
# Important note: you can't just use the following three lines "as is"!
# Refer to the Solaris LightPulse Device Driver documentation for details.
#reg =
0x00801000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, # PCI
#
0x02801010, 0x00000000, 0x00000000, 0x00000000, 0x00001000, # SLIM
#
0x02801018, 0x00000000, 0x00000000, 0x00000000, 0x00000100; # CSRs
# link-speed: link speed selection for initializing the Fibre Channel connection.
#
0 =
auto select (default)
#
1 =
1 Gigabaud
#
2 =
2 Gigabaud
link-speed=0;
5.3.12 Contents of the file st.conf for Solaris
An example of a file modified for CentricStor is shown below. The entries relating to
CentricStor are highlighted in red. The bit setting in the Property Section of the example is
recommended only if the backup application (e.g. DataProtector on Solaris see section
“Solaris” on page 301) or any other feature specifies nothing else.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
This file contains officially supported devices of Fujitsu Siemens Computers
Please don't delete the ### comments.
To support additional drives, please refer to the st man page for details.
When adding new entries into the tape-config-list, or uncommenting
existing entries, be careful. Lines in the middle of the list must
end with comma, and the last line in the list MUST end with semicolon.
Each record (line) in the tape-config-list below has the form;
SCSI-Inquiry-String, Text for /var/adm/messages, Jump-Label,
Jump-Label points to an entry in the configuration strings section.
The flag ST_BUFFERED_WRITE (0x4000) is obsolete in Solaris 9 or
Solaris 8 and patch 108725-14. Therefore ST_BUFFERED_WRITE is reset
in the tapeoptions of all configuration strings. If this st.conf is
used on older Solaris version (2.6, 2.7...) ST_BUFFERD_WRITE has to
be set by editing this file.
###DRIVE CONFIG SECTION
tape-config-list=
"ECRIX
VXA-1",
"EXABYTE EXB-8505",
"EXABYTE EXB-8900",
"EXABYTE Mammoth2",
"EXABYTE VXA-2",
"FSC
",
"HP
C1537A",
"HP
C1557A",
180
"Ecrix VXA-1",
"EXABYTE EXB8505",
"EXABYTE VXA-2",
"CentricStor",
"HP DDS3 4mm DAT",
"XVXA-1",
"XEXB-8505",
"XEXB-8900",
"XMammoth2",
"XVXA-2",
"Xtor",
"XC1537A",
"XC1557A",
"HP
C5683A",
"HP DDS4 4mm DAT",
"HP
C5713A",
"HP
C7438A",
"HP DDS5 4mm DAT",
"HP
Ultrium 1",
"HP Ultrium",
"HP
Ultrium 2",
"HP Ultrium",
"IBM
03570C",
"3570",
"IBM
03590B",
"PXT1",
"IBM
03590E",
"3591-Ex",
"M4 DATA 123107 SCSI",
"3588",
"QUANTUM DLT7000",
"DLT7000",
"QUANTUM DLT8000",
"DLT8000",
"Quantum DLT4000",
"DLT 4000",
"SEAGATE DAT
9SP40-000", "Seagate DDS4 4mm DAT",
"SEAGATE DAT
DAT72-000", "SEAGATE_DAT_72",
"SEAGATE ULTRIUM",
"Seagate Ultrium Tape",
"SONY
SDX-500C",
"SONY AIT-2 tape drive",
"STK
9490",
"STK 9490",
"STK
9840",
"STK 9840",
"SUN
DLT7000",
"Sun DLT7000",
"TANDBERGTS400",
"Tandberg 420LTO LTO",
###END OF DRIVE CONFIG SECTION
Solaris
"XC5683A",
"XC5713A",
"XC7438A",
"XUltrium",
"XHP-ULT-2",
"X03570C",
"X03590B",
"X03590E",
"X123107",
"XDLT7000",
"XDLT8000",
"XDLT4000",
"XDAT",
"XSDAT",
"XULTRIUM",
"XSDX-500C",
"X9490",
"X9840",
"XSUNDLT7K",
"XS400";
###PROPERTY SECTION
XVXA-1
=
1,0x36,0,0xde39,1,0x80,0;
XEXB-8505
=
1,0x35,0,0x8e39,2,0x15,0x8c,1;
XEXB-8900
=
1,0x29,0,0x19e39,1,0x7f,0;
XMammoth2
=
1,0x35,0,0x19e39,1,0x28,0;
XVXA-2
=
1,0x36,0,0x19e39,2,0x80,0x81,1;
Xtor
=
1,0x36,0,0x18619,1,0x00,0;
XC1537A
=
1,0x34,1024,0x9639,4,0x00,0x13,0x24,0x3,3;
XC1557A
=
1,0x34,1024,0x9639,4,0x00,0x13,0x24,0x3,3;
XC5683A
=
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
XC5713A
=
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
XC7438A
=
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
XUltrium
=
1,0x36,0,0x19639,4,0x00,0x00,0x00,0x40,3;
XHP-ULT-2
=
1,0x36,0,0x29639,4,0x00,0x00,000,0x42,3;
X03570C
=
1,0x24,0,0x618639,1,0x00,0;
X03590B
=
1,0x24,0,0x618639,1,0x00,0;
X03590E
=
1,0x24,0,0x618639,1,0x00,0;
X123107
=
1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
XDLT7000
=
1,0x38,0,0x9639,4,0x82,0x83,0x84,0x85,2;
XDLT8000
=
1,0x38,0,0x9639,4,0x84,0x85,0x88,0x89,2;
XDLT4000
=
1,0x38,0,0x9639,4,0x80,0x81,0x82,0x83,2;
XDAT
=
1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,3;
XSDAT
=
1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,3;
XULTRIUM
=
1,0x36,0,0x19639,4,0x00,0x00,0x00,0x00,3;
XSDX-500C
=
1,0x36,0,0x9639,4,0x30,0x8c,0x8c,0x8c,1;
X9490
=
1,0x24,0,0x1867d,1,0x00,0;
X9840
=
1,0x36,0,0x19679,1,0x00,0;
XSUNDLT7K
=
1,0x36,0,0x19639,4,0x82,0x83,0x84,0x85,2;
XS400
=
1,0x3b,0,0x45863d,3,0x00,0x40,0x42,2;
###END OF PROPERTY SECTION
181
Solaris
###TARGET
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
CONFIG SECTION
class="scsi" target=0
lun=0;
lun=1;
lun=2;
lun=3;
lun=4;
lun=5;
lun=6;
lun=7;
lun=8;
lun=9;
lun=10;
lun=11;
lun=12;
lun=13;
lun=14;
lun=15;
name="st" class="scsi"
target=1 lun=0;
target=2 lun=0;
target=3 lun=0;
target=4 lun=0;
target=5 lun=0;
target=6 lun=0;
#
# In case there are wide tape drives, one can use these targets
#
#name="st" class="scsi"
# target=8 lun=0;
# target=9 lun=0;
# target=10 lun=0;
# target=11 lun=0;
# target=12 lun=0;
# target=13 lun=0;
182
Solaris
# target=14 lun=0;
# target=15 lun=0;
#
# for CentricStor we use more luns
#
# Support LPx
name="st" class="scsi" target=53 lun=0;
# The following 4 LUNs are used by other systems in the server farm.
# name="st" class="scsi" target=53 lun=17;
##### end of target config section
183
Solaris
5.3.13 Extensions for Data Protector and SolarisTivoli
For Data Protector the size of the shared memory must be extended.
Ê
In the file /etc/system the entry:
set shmsys:shminfo_shmmax=0x7FFFFFFF
This change has no negative effect on the system.
Ê
Then the system must be rebooted.
5.3.14 Extensions for NetBackup
For NetBackup the sg driver must be installed in accordance with the NetBackup Media
Manager Device Configuration Guide from Veritas.
184
Solaris
5.3.15 Sun StorEdge SAN Foundation Software (SFS/Leadville)
5.3.15.1
General
The Leadville driver from SUN StorEdge SAN Foundation Software (SFS) can also be used on
Solaris systems as an alternative to the Emulex FibreChannel driver lpfc and the Qlogic FibreChannel driver qla. For this purpose, the SAN Foundation Software from Sun must be
downloaded1 for Solaris 8/9. You must register to do this. In Solaris 10 (1/06) and higher,
the software is already part of the operating system.
The benefits of the SFS/Leadville driver lie in the flexible administration of SAN devices in
general, and in the integrated multipath and load balancing softrware MPxIO for RAID systems. A permanent binding of the targets and LUNs as with the lpfc/qla driver is no longer
required.
CAUTION!
SFS/lpfc mixed operation has not been released.
i
The following HBAs with the SFS software package can be used in the Primepower systems of Fujitsu Siemens:
●
Emulex HBAs
–
–
–
–
●
LP9002L (2Gb/s)
LP9802 (2Gb/s)
LP10000[-DC] (2Gb/s)
LP11000 (4 GB/s)
Sun/QLogic HBAs (only with special release)
–
–
X6767A
X6768A
In addition to the SFS software, the Emulex FibreChannel Device Management Utility
EMLXemlxu must also be installed. This utility permits both administration (firmware/Fcode
update) and diagnostics. The current version of the utility can be obtained free of charge
from the Emulex websites.
The SMAWdevsp software package must also be installed. This package is contained on the
Control DVD. The current version 2.0B202 can be obtained from the Fujitsu Siemens service sites. Installing this packages results in the /kernel/drv/st.conf file for the tapes
released by FSC and the CentricStor tape emulations being modified.
1
https://sdlc1a.sun.com
2
http://extranet.fujitsu-siemens.com/service/primepower/software/Control-DVDProducts/Solaris/FSCBasicExtensions/Updates/Readme.htm
185
Solaris
The following configuration files must be adjusted for SFS/Leadville operation using
CentricStor:
●
/kernel/drv/emlxs.conf
link-speed=1/2/4
It is advisable to set a fixed speed for the FibreChannel connection.
topology=2
The connection of the Open System Server to the ICP of
CentricStor is always implemented via FibreChannel switches. Point
to Point topology must therefore be set permanently.
The default value should be retained for all other parameters. If HBA-specific settings
need to be made - e.g. when RAID systems are connected directly - the HBA instance
must be set before the parameter.
Example: emlxs0-topology=4;
●
/kernel/drv/fp.conf
Settings are required in this file only if CentricStor tape LUNs are to be masked. This feature is only available in Solaris 10 (Patch 119130-22) and higher.
Example
4 virtual tapes (LUNs 0-3) are configured on one port of a CentricStor ICP. 2 servers
are now connected to this port via a FibreChannel switch. Server 1 should see all 4 tape
LUNs, but server 2 only tape LUNs 2 and 3. From the viewpoint of server 2, tape LUNs
0 and 1 must therefore be entered in a blacklist.
pwwn-lun-blacklist=
"510000f010fd92a1,0,1",
"510000e012079df1,1,2";
This entry means that LUNs 0 and 1 on the target 510000f010fd92a1 and LUNs 1 and
2 on target 510000e012079df1 cannot be accessed after a reboot.
●
/kernel/drv/st.conf
After Version 2.0B20 of the SMAWdevsp package has been installed, no further settings
are required. It is important that the following parameters are set for FSC CentricStor
emulation:
Xtor=1,0x36,0,0x18619,1,0x00,0;
186
5.3.15.2
Solaris
Example of migration from lpfc to SFS/Leadville
The example below illustrates migration from lpfc to SFS/Leadville on a Primepower 450
with Solaris 9. The virtual tapes rmt/0-3 belong to a VJUK emulation, the virtual tapes
rmt/4-7 to a VDAS emulation.
1. Overview of the configuration with lpfc driver
# /opt/SMAW/sbin/prtcfg
:
fibre-channel, instance #0
sgen, instance #36
:
FSC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
8 LUNs of the FSC CentricStor tape emulation and one sgen instance of the VJUK emulation are visible on the FibreChannel HBA with the instance number 0. The following
phyiscal path belongs to sgen instance 36:
# grep sgen /etc/path_to_inst
"/pci@82,2000/fibre-channel@1/sgen@3,10" 36 "sgen"
A node name for this sgen instance in contained under /dev/scsi/changer:
# ls -al /dev/scsi/changer
total 6
drwxr-xr-x
2 root
root
512 Oct 4 16:15 .
drwxr-xr-x
3 root
root
512 Jul 10 2006 ..
lrwxrwxrwx
1 root
other
62 Oct 4 16:15 c3t3d16 ->
../../../devices/pci@82,2000/fibre-channel@1/sgen@3,10:changer
# mtx -f /dev/scsi/changer/c3t3d16 status
Storage Changer /dev/scsi/changer/c3t3d16:4 Drives, 222 Slots ( 12 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full :VolumeTag=LV1000
:
:
187
Solaris
2. Installation of the SFS package
# uncompress SAN_4[1].4.12_install_it.tar.Z
# tar xvf SAN_4[1].4.12_install_it.tar
# cd SAN_4.4.12_install_it
# install_it
Logfile /var/tmp/install_it_Sun_StorEdge_SAN.log : restarted on Wed Mar 7 16:46:32
MET 2007
This routine installs the packages and patches that
make up Sun StorEdge SAN.
Would you like to continue with the installation?
[y,n,?] y
Verifying system...
Checking for incompatible patches
: Done
Begin installation of SAN software
Installing StorEdge SAN packages Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
Package
SUNWsan
SUNWcfpl
SUNWcfplx
SUNWcfclr
SUNWcfcl
SUNWcfclx
SUNWfchbr
SUNWfchba
SUNWfchbx
SUNWfcsm
SUNWfcsmx
SUNWmdiu
SUNWqlc
SUNWqlcx
SUNWjfca
SUNWjfcax
SUNWjfcau
SUNWjfcaux
SUNWemlxs
SUNWemlxsx
SUNWemlxu
SUNWemlxux
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
StorEdge SAN packages installation completed.
188
Solaris
Installing StorEdge SAN patches and required patches Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
Patch
111847-08
113046-01
113049-01
113039-19
113040-22
113041-14
113042-17
113043-14
113044-07
114476-09
114477-04
114478-08
114878-10
119914-11
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Installed
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Successfully.
Patch installation completed.
Installation of Sun StorEdge SAN completed Successfully
------------------------------------------------------------------------------------Please reboot your system.
-------------------------------------------------------------------------------------
189
Solaris
3. Installation of the Emulex FibreChannel Device Managment Utility
#
tar xvf emlxu_kit-1.00n-sparc.tar
#
emlxu_install
<Removing old EMLXemlxu package>
pkgrm: ERROR: no package associated with <EMLXemlxu>
<Expanding emlxu_kit-1.00n-sparc.tar>
<Adding new package>
Processing package instance <EMLXemlxu> from </export/home/mon/Emulex>
Emulex LightPulse Fibre Channel Adapter Utilities (usr)
(sparc) 1.00n,REV=2006.04.19.16.36
COPYRIGHT
2004-2006 Emulex. All rights reserved.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <EMLXemlxu> [y,n,?] y
Installing Emulex LightPulse Fibre Channel Adapter Utilities (usr) as <EMLXemlxu>
## Installing part 1 of 1.
[ verifying class <none> ]
Installation of <EMLXemlxu> was successful.
<Cleaning directory>
<emlxu_install complete>
<Execute "emlxu_remove" when ready to uninstall>
In Solaris 10, the package should only be installed in the global zone using
pkgadd -G -d `pwd`/.
190
Solaris
4. Changing the HBA/driver asignment
# /opt/EMLXemlxu/bin/emlxdrv
Driver Alias Present Boot Sun Models
-------------------------------------------------------------------------lpfc
lpfs no
no
no LP8000S and LP9002S (SBUS)
lpfc
f800 no
no
no LP8000 and LP8000DC
lpfc
f900 no
no
no LP9002, LP9002C, LP9002DC, and LP9402DC
lpfc
f980 yes
no
lpfc
fa00 no
no
no LP10000, LP10000DC and LP10000ExDC
lpfc
fd00 no
no
no LP11000 and LP11002
f0a5 no
no
no 2G Blade Adapter (emlxs only)
emlxs fc00 no
no
yes LP10000-S and LP10000DC-S (emlxs only)
emlxs fc10 no
no
yes LP11000-S and LP11002-S (emlxs only)
Available commands:
--------------------------------------------------------------------------set_emlxs <Alias> - Sets emlxs driver to bind to the specified device(s)
set_emlxs_sun
- Sets emlxs driver to bind to all Sun devices
set_emlxs_all
- Sets emlxs driver to bind to all devices
set_lpfc <Alias>
- Sets lpfc driver to bind to the specified device(s)
set_lpfc_nonsun
- Sets lpfc driver to bind to all non-Sun devices
clear_dev <Alias> - Clears driver binding to the specified device(s)
clear_lpfc
- Clears all lpfc driver bindings
clear_emlxs
- Clears all emlxs driver bindings
clear_sun
- Clears driver bindings to all Sun devices
clear_nonsun
- Clears driver bindings to all non-Sun devices
clear_all
- Clears driver bindings to all devices
q
- Exits this program.
The emlxdrv command enables a driver to be assigned to the various Emulex HBAs.
In the example above, the Ipfc driver is currently assigned to the HBAs which are released in the Primepower. The emlxs driver is assigned to all HBAs using the
set_emlxs_all command.
emlxdrv> set_emlxs_all
Driver Alias Present Boot Sun Models
-------------------------------------------------------------------------emlxs lpfs no
no
no LP8000S and LP9002S (SBUS)
emlxs f800 no
no
emlxs f900 no
no
no LP9002, LP9002C, LP9002DC, and LP9402DC
emlxs f980 yes
no
emlxs fa00 no
no
no LP10000, LP10000DC and LP10000ExDC
emlxs fd00 no
no
no LP11000 and LP11002
emlxs f0a5 no
no
no 2G Blade Adapter (emlxs only)
emlxs fc00 no
no
yes LP10000-S and LP10000DC-S (emlxs only)
emlxs fc10 no
no
yes LP11000-S and LP11002-S (emlxs only)
191
Solaris
5. Rebooting the system
# reboot --
-rv
Messages of the new SFS/Emulex driver emlxs appear on the console:
[B.1273]emlxs0: NOTICE: 100: Driver attach.
(2006.12.12.00.10))
[B.128C]emlxs0: NOTICE: 100: Driver attach.
WWNN:20000000C930AED8)
[B.129B]emlxs0: NOTICE: 100: Driver attach.
PCI-device: fibre-channel@1, emlxs0
emlxs0 is /pci@82,2000/fibre-channel@1
[5.04B5]emlxs0: NOTICE: 720: Link up. (2Gb,
(Emulex-S s9-64 sparc v1.12b
(LP9802 Dev_id:f980 Sub_id:f980 Id:12)
(Firmware:1.91a5 Boot:none Fcode:none)
(WWPN:10000000C930AED8
(FW Library: LP10000-S: v1.91x15)
(FW Library: LP11000-S: v2.70a5)
(FW Library: LP11002-S: v2.70a5)
fabric *)
6. Checking the system configuration under SFS/Leadville
#
cfgadm -al -o show_FCP_dev
Ap_Id
c4
c4::10000000c9553c6e,0
c4::10000000c9553c6e,1
c4::10000000c9553c6e,2
c4::10000000c9553c6e,3
c4::10000000c9553c6e,4
c4::10000000c9553c6e,5
c4::10000000c9553c6e,6
c4::10000000c9553c6e,7
c4::10000000c9553c6e,8
c4::10000000c9553c6e,9
c4::10000000c9553c6e,10
c4::10000000c9553c6e,11
c4::10000000c9553c6e,12
c4::10000000c9553c6e,13
c4::10000000c9553c6e,14
c4::10000000c9553c6e,15
c4::10000000c9553c6e,16
Type
fc-fabric
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
med-changer
Receptacle
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
Occupant
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
Condition
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
This output shows that an HBA c4 is connected to a FibreChannel switch (fc-fabric
in the Type column). In the case of a directly connected storage device, fc-privat
would be contained in the Type column. The reference of HBA c4 to the physical node
is contained in the /dev/cfg directory.
# ls -al /dev/cfg/c4
lrwxrwxrwx
1 root
root
51 Mar 7 17:26 /dev/cfg/c4 ->
../../devices/pci@82,2000/fibre-channel@1/fp@0,0:fc
HBA c4 sees a target with the WWPN 10000000c9553c6e of the type tape.
192
Solaris
In this case the WWPN 10000000c9553c6e represents the WWPN of the CentricStor
ICP ports. 16 Tape Devices (LUNs 0-15) and one Changer Device are configured on this
CentricStor port.
At this time the CentricStor configuration is consequently visible to Solaris, but not yet
activated (Occupant unconfigured).
The following command is issued to activate this configuration on the target
10000000c9553c6e on HBA c4:
# cfgadm -c configure c4::10000000c9553c6e
# cfgadm -al -o show_FCP_dev
Ap_Id
c4
c4::10000000c9553c6e,0
c4::10000000c9553c6e,1
c4::10000000c9553c6e,2
c4::10000000c9553c6e,3
c4::10000000c9553c6e,4
c4::10000000c9553c6e,5
c4::10000000c9553c6e,6
c4::10000000c9553c6e,7
c4::10000000c9553c6e,8
c4::10000000c9553c6e,9
c4::10000000c9553c6e,10
c4::10000000c9553c6e,11
c4::10000000c9553c6e,12
c4::10000000c9553c6e,13
c4::10000000c9553c6e,14
c4::10000000c9553c6e,15
c4::10000000c9553c6e,16
Type
fc-fabric
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
tape
med-changer
Receptacle
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
Occupant
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
Condition
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
You can now view information on the LUNs using the
luxadm display <Target WWPN> command:
# luxadm display 10000000c9553c6e
DEVICE PROPERTIES for tape: 10000000c9553c6e
Vendor:
IBM
Product ID:
03590E1A
Revision:
E32E
Serial Num:
0000000D010F
Device Type:
Tape device
Path(s):
LUN number
/dev/rmt/8n
/devices/pci@82,2000/fibre-channel@1/fp@0,0/st@w10000000c9553c6e,f:n
LUN path port WWN:
10000000c9553c6e
Host controller port WWN:
10000000c930aed8
Path status:
Not Ready
193
Solaris
Vendor:
IBM
Product ID:
03590E1A
Revision:
E32E
Serial Num:
0000000D010E
Device Type:
Tape device
Path(s):
/dev/rmt/9n
/devices/pci@82,2000/fibre-channel@1/fp@0,0/st@w10000000c9553c6e,e:n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
:
:
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0107
Device Type:
Tape device
Path(s):
Tape device node
/dev/rmt/16n
/devices/pci@82,2000/fibre-channel@1/fp@0,0/st@w10000000c9553c6e,7:n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0106
Device Type:
Tape device
Path(s):
/dev/rmt/17n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0105
Device Type:
Tape device
Path(s):
194
Solaris
/dev/rmt/18n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0104
Device Type:
Tape device
Path(s):
/dev/rmt/19n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0103
Device Type:
Tape device
Path(s):
/dev/rmt/20n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0102
Device Type:
Tape device
Path(s):
/dev/rmt/21n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0101
Device Type:
Tape device
Path(s):
195
Solaris
/dev/rmt/22n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
Vendor:
FSC
Product ID:
CentricStor
Revision:
8.8
Serial Num:
0000000D0100
Device Type:
Tape device
Path(s):
/dev/rmt/23n
LUN path port WWN:
10000000c9553c6e
10000000c930aed8
Path status:
Not Ready
The 8 tape LUNs (/dev/rmt/16 - 23) of the FSC CentricStor emulation which were
previously visible using the lpfc driver as /dev/rmt/0 - 7 can now be recognized
again.
The changer device is not displayed when luxadm display <WWPN> is used.
Here the relevant device node is contained in the /dev/scsi/changer directory.
#
ls -al /dev/scsi/changer
Node name with lpfc
total 8
Node name with
drwxr-xr-x
2 root
root
512 Mar 8 11:49 .
Leadville
drwxr-xr-x
3 root
root
512 Jul 10 2006 ..
lrwxrwxrwx
1 root
other
62 Oct 4 16:15 c3t3d16 ->
../../../devices/pci@82,2000/fibre-channel@1/sgen@3,10:changer
lrwxrwxrwx
1 root
root
85 Mar 8 11:49 c4t10000000C9553C6Ed16 ->
../../../devices/pci@82,2000/fibrechannel@1/fp@0,0/sgen@w10000000c9553c6e,10:changer
Before the SFS/Leadville conversion, 8 tape LUNs were visible (see the prtcfg command above). The 8 tape LUNs were released in /kernel/drv/st.conf.
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
name="st"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
target=3
target=3
target=3
target=3
target=3
target=3
target=3
target=3
lun=0;
lun=1;
lun=2;
lun=3;
lun=4;
lun=5;
lun=6;
lun=7;
With SFS/Leadville, these definitions are no longer needed in st.conf.
196
Solaris
The disadvantage is that all LANs on this target are now visible. With Solaris 10, these
LUNs which are not required can be masked by means of the blacklist (see above). This
is not possible with Solaris 8/9. As an alternative, these LUNs can be set offline using
the following command.
Example: # luxadm -e offline /dev/rmt/8n
5.3.15.3
Useful commands
A few commands which are not described in detail but which are very helpful in analyzing
problems are listed below.
# /opt/EMLXemlxu/bin/emlxadm
The get_host_attrs call under emlxadm enables you to obtain all the necessary information on the selected HBAs.
# emlxadm
EMLXADM Device Management Utility, Version 1.00r
COPYRIGHT
2004-2006 Emulex. All rights reserved.
Available HBA's:
1.
2.
/devices/pci@82,2000/fibre-channel@1/fp@0,0:devctl (CONNECTED)
/devices/pci@80,2000/fibre-channel@1/fp@0,0:devctl (NOT CONNECTED)
Enter an HBA number or zero to exit: 1
HBA: /devices/pci@82,2000/fibre-channel@1/fp@0,0:devctl
Available commands:
get_num_devs
get_dev_list
get_logi_params <wwpn>
get_host_params
get_sym_pname
set_sym_pname
get_sym_nname
set_sym_nname
dev_login
dev_logout
get_state
dev_remove
link_status
get_fcode_rev
download_fcode
get_fw_rev
download_fw
get_boot_rev
<string>
<string>
<wwpn>
<wwpn>
<wwpn>
<wwpn>
<d_id>
[filename]
[filename]
[rev2]
- Returns the number of FC devices seen by this HBA.
- Returns a list of FC devices seen by this HBA.
- Returns the login paramters for a specified FC
device.
- Return the host parameters.
- Returns the symbolic port name of a device.
- Sets the symbolic port name for a device.
- Returns the symbolic node name of a device.
- Sets the symbolic node name for a device.
- Performs an FC login to a device.
- Performs an FC logout to a device.
- Returns current Leadville state of a specified
device.
- Remove the FC device from Leadville management.
- Request link error status from a specified D_ID.
- Returns the current Fcode revison of the HBA.
- Download the HBA fcode.
- Returns the current firmware revison of the HBA.
- Download the HBA firmware.
* Returns the current boot revison of the HBA.
197
Solaris
download_boot
get_dump_size
force_dump
get_dump
get_topology
reset_link
reset_hard
reset_hard_core
diag
ns
parm_get_num
parm_get_list
parm_get
parm_set
msgbuf
get_host_attrs
get_port_attrs
get_path
get_vpd
q
h
hba
p
[filename]
*
<-t,-b> <file> <wwpn,0>
<test>
*
*
<label>
*
Download the HBA boot image.
Returns the HBA's firmware core dump size.
Force a firmware core dump on this HBA.
Saves firmware core dump to a file.
Returns the current FC network topology.
Resets the link of a specified FC device.
Reset the HBA.
Reset the HBA firmware core.
Perform a diagnostic test on the HBA.
Performs a complete query of the fabric name server.
Returns the total number of configurable parameters.
Returns a list of configurable parameters.
Gets the value of a specified parameter in the
driver.
<label> <val> * Sets the value of a specified parameter in the
driver.
all or <number> [-i interval] * Returns the driver's internal message
log.
- Returns the host adapter and port attributes.
<index>, <wwn> or all - Returns the port attributes.
<index>
- Returns the adapter path.
* Returns the adapter's Vital Product Data (VPD).
- Exits this program.
- Returns this help screen.
- Select another hba.
- Repeat previous command.
*Emulex adapters only
emlxadm> get_host_attrs
Host Attributes:
Manufacturer
Serial Number
Model
Model Description
Node WWN
Node Symbolic Name
Hardware Version
Driver Version
Optional ROM Version
Firmware Version
Vendor Specific ID
Number of HBA ports
Driver Name
Last Change
fp Instance
Node WWN
Port WWN
Port Fc Id
Port Type
Port State
Port Supported COS
198
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
Emulex
0000C930AED8
LP9802
Emulex LP9802 2Gb 1-port PCI-X FC HBA
20000000C930AED8
none
2003806d
1.12b (2006.12.12.00.10)
none
1.91a5
f98010df
1
Emulex-S s9-64 sparc v1.12b
1
0
20000000C930AED8
10000000C930AED8
050a00
Nport
Online
Class3
Solaris
Port Supported FC4 Types
= 00000000, 00000000,
00000000, 00000000,
Port Active FC4 Types
= 00000120, 00000000,
00000000, 00000000,
Port Symbolic Name
= none
Port Supported Speed
= 1Gb, 2Gb
Port Speed
= 2Gb
Port Max Frame Size
= 0x800 bytes
Fabric Name
= 0000000000000000
Number of Discovered Ports = 1
00000000,
00000000,
00000000,
00000000,
00000000,
00000000,
00000000,
00000000,
# luxadm -e port
/devices/pci@3,700000/SUNW,qlc@0/fp@0,0:devctl
/devices/pci@6,600000/SUNW,qlc@0/fp@0,0:devctl
/devices/pci@6,600000/SUNW,qlc@0,1/fp@0,0:devctl
/devices/pci@7,700000/SUNW,emlxs@0/fp@0,0:devctl
/devices/pci@7,700000/SUNW,emlxs@0,1/fp@0,0:devctl
CONNECTED
CONNECTED
CONNECTED
CONNECTED
CONNECTED
# luxadm -e forcelip /dev/cfg/c4
The FibreChannel loop is reinitialized.
!
CAUTION!
The FibreChannel connection is briefly interrupted here.
# cfgadm -c [un]configure c4::10000000c9553c6e
Places the target 10000000c9553c6e in the unconfigured status and should therefore not
be used. The unconfigured status can be canceled again using the configure option.
#
Pos
0
1
2
3
luxadm -e dump_map /dev/cfg/c2
Port_ID
a1100
a1b00
b1b00
b1c00
Hard_Addr
0
0
0
0
Port WWN
10000000c9553b3e
5006016939a008de
5006016339a008de
10000000c957ecf2
Node WWN
20000000c9553b3e
50060160b9a008de
50060160b9a008de
20000000c957ecf2
Type
0x1
0x0
0x0
0x1f
(Tape device)
(Disk device)
(Disk device)
(Unknown Type,Host Bus
Adapter)
# luxadm display /dev/rmt/15n
Displays information of the relevant devices (see above).
199
HP-UX
5.3.15.4
Familiar problems
●
In the case of a multipath connection to a tape LUN, the reservation is not canceled by
the mt -f /dev/rmt/x forcereserve command.
●
When a luxadm display /dev/rmt/16 is executed for a tape which is currently
being used, the following error message is issued:
Error: SCSI failure. - /dev/rmt/16
5.4 HP-UX
5.4.1 General
●
HP-UX B11.00 is required for connection to CentricStor.
(there are two older FC cards, A6684A with HSC-EISA and A6685A with HP-HSC
Interface, which are already supported by HP-UX B10.20. These have not yet been
tested. Both cards support Fabric Login.)
●
The patch PHKL_23939 from http://www.hp.com is required for connection to
CentricStor. If the patch is not in use, the machine logs itself on and off with every
open/close on the FC switch. Then the klog.msg of the ICP constantly shows
messages.
●
Device nodes can only be generated if they can be accessed from LUN 0 without interruption.
5.4.2 Restrictions
i
The system only supports 8 LUNs per partner WWN.
The system must not be connected to an FC switch with the 8 domains.
5.4.3 Useful commands:
–
–
–
–
–
–
–
200
sam (configuration network, setting up device nodes etc.)
swinstall, swverify (software installation)
fcmsutil /dev/td0
ioscan (scanning the I/O ports – shows CentricStor)
lsdev
xstm
see the chapter “Useful commands and information” on page 361
HP-UX
5.4.4 Links
HP: Migration to Fabric
5.4.5 Device nodes
By default, device nodes are created as compressed. However, Mammoth2 and generic
SCSI emulations create nodes which are not compressed. In these cases compression
should be switched on in the CentricStor configuration.
/dev/rmt/c6t0d0BESTb
...
!
CAUTION!
If the port on the switch or the switch itself changes then the devices must be regenerated with sam. In the process the controller number is raised
(/dev/rmt/c6t0d0BESTb -> /dev/rmt/c7t0d0BESTb).
201
IBM-AIX
5.5 IBM-AIX
5.5.1 Restrictions
The standard driver OST (Other SCSI Tape) generates device nodes, which cannot
compress.
In CentricStor V2.1 or higher, compression can be turned on explicitly for an LD.
i
●
●
3590 Emulation on the CentricStor side:
–
LAN libraries:
LUN 0 must always be defined with FSC CentricStor, the other LUNs with
IBM 03590.
–
SCSI libraries:
Define robotics on LUN 0, all emulations with IBM 03590
–
Drives with the emulation FSC CentricStor are entered in AIX as other scsis tape.
–
Drives with the emulation IBM 03590 are entered as IBM 3590 Tape Drive and
Medium Changer.
The Atape must be used in AIX.
The driver for the drive 3590 (Atape.7.0.3.0.bin or newer version) can be loaded from
ftp://ftp.software.ibm.com/storage/devdrvr/AIX/
The installation of Atape.driver can be checked with:
# lslpp -L Atape.driver
Fileset
Level State Description
---------------------------------------------------------------------------Atape.driver
8.4.9.0 C
IBM AIX Enhanced Tape and Medium Changer Device Driver
202
●
When the Mammoth2 emulation is used configuration can take place from LUN 0.
●
Device nodes can only be generated if they can be accessed from LUN 0 without interruption.
●
In AIX there is no persistent binding as AIX addresses the devices directly via the
WWN.
●
IBM-AIX
When hardware scanning takes place with cfgmgr and VJUK the following message is
issued:
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed. devices.fcp.changer
No functional restriction has been observed.
5.5.3 Useful commands
–
–
–
–
–
–
–
–
smit (System Management Interface Tool)
smit (Alpha-Menu)
smit chgenet (FastPath to Ethernet adapter configuration; en0: Standard Ethernet;
et0: Ethernet 802.3)
smit tcpip (FastPath to TCP/IP configuration; Caution: IP addresses are sometimes
interpreted as octal numbers)
smit user (FastPath to user/group management)
lscfg –v (show hardware configuration)
lsdev –C –c tape (show tapes)
also see chapter “Useful commands and information” on page 361
203
IBM-AIX
5.5.4 Configuration of the drives
Ê
First, delete any drives present drives with smit -> Devices -> Tape Drive ->
Remove a Tape Drive.
Ê
Connect the drives or link them with CentricStor.
Ê
Reboot the system with reboot -- -r. If the system cannot be rebooted, you can, for
example, delete the tapes with the following script:
#!/usr/bin/ksh
lsdev -Cc tape | awk '{ print $1 }' | while read RMT; do
rmdev -l $RMT -d
done
After this, recreate the configuration automatically with cfgmgr.
Checking the tape drives in AIX:
# lsdev -Cc tape
rmt0 Available 10-78-01 IBM 3590 Tape Drive and Medium Changer (FCP)
Checking the characteristics of a tape drive:
# lsattr -El rmt1
mode
yes
block_size
0
compress
yes
autoload
no
logging
no
max_log_size
500
space_mode
SCSI
rew_immediate no
trailer_labels no
retain_reserve no
emulate_auto
no
limit_readerp no
fail_degraded no
devtype
03590E1A
mtdevice
scsi_id
0x31a00
lun_id
0x2000000000000
location
ww_name
0x10000000c937fa42
drive_port
0
new_name
dev_status
node_name
alt_pathing
no
primary_device rmt1
Use Buffered Writes
Block Size (0=Variable Length)
Use Hardware Compression on Tape
Use Autoloading Feature at End-ofActivate volume information logging
Maximum size of log file (in # of entries)
Backward Space/Forward Space Record Mode
Use Immediate Bit in Rewind Commands
Trailer Label Processing
Retain Reservation
Use Random Mode to Emulate Autoloader Tape Drive
Limit Read Error Recovery Time to 5 Seconds
Fail Tape Operation if Degraded Media is Detected
Device Type
Library Device Number
SCSI Target ID
Logical Unit Number
Location
World Wide Port Name
Drive Port Number
New Logical Name
N/A
World Wide Node Name
Enable Alternate Pathing Support
Primary Logical Device
True
True
True
True
True
True
True
True
True
False
True
True
True
False
True
True
True
True
False
False
True
False
False
True
False
The WWN and LU, among other things, are output. Scsi_id is the port ID on the SAN switch.
204
IBM-AIX
Inquiring the manufacturer data of a drive:
# lscfg -vl rmt2
DEVICE
rmt2
LOCATION
10-78-01
DESCRIPTION
IBM 3590 Tape Drive and Medium
Changer (FCP)
Manufacturer................IBM
Machine Type and Model......03590E1A
Serial Number...............0000000D0003
Device Specific.(FW)........E32E
Loadable Microcode Level....A0B00E26
Outputting information on the HBA of AIX:
The adapters have the designations fcsn, with n = adapter number
Inquiring the existing HBAs:
# lsdev -Cc adapter | grep fcs
fcs0
Available 10-78
FC Adapter
Inquiring a particular HBA:
# lscfg -vl fcs0
DEVICE
fcs0
LOCATION
10-78
DESCRIPTION
FC Adapter
Part Number.................03N4167
EC Level....................D
Serial Number...............KT02900429
Manufacturer................0010
FRU Number..................03N4167
Network Address.............10000000C9232A4A
ROS Level and ID............02903331
Device Specific.(Z0)........4002206D
Device Specific.(Z1)........10020193
Device Specific.(Z2)........3001506D
Device Specific.(Z4)........FF101493
Device Specific.(Z8)........10000000C9232A4A
Device Specific.(Z9)........SS3.30X1
Device Specific.(ZA)........S1F3.30X1
Device Specific.(ZB)........S2F3.30X1
Device Specific.(YL)........P1-I5/Q1
The network address is the adapter WWN.
205
IBM-AIX
Modifying the device characteristics (only required for other scsi tape devices!):
Reserve support and variable block length can be set for these drives via smit.
The device nodes IBM 3590 Tape do not need to be modified.
Ê
smit ➟ Devices ➟ Tape Drive ➟ Change / Show Characteristics of a Tape Drive
Reserve/Release set support to yes
set lock size from 512 to 0 ( == variable)
or with SHELL:
chdev -l 'rmt0' -a res_support='yes'
chdev -l 'rmt0' -a block_size='0'
5.5.5 Device nodes
Device nodes in AIX:
Special File
Rewind on Close
Retension on Open
Density Setting
/dev/rmt*
Yes
No
#1
/dev/rmt*.1
No
No
#1
/dev/rmt*.2
Yes
Yes
#1
/dev/rmt*.3
No
Yes
#1
/dev/rmt*.4
Yes
No
#2
/dev/rmt*.5
No
No
#2
/dev/rmt*.6
Yes
Yes
#2
/dev/rmt*.7
No
Yes
#2
Density #1 = highest possible, #2 = next highest.
206
IBM-AIX
5.5.6 Testing the tape drives with tapeutil
Tapeutil permits simple tests of the tape functions. Fixed block mode is used, so tapeutil can
be employed in CentricStor V3.0 or higher.
Menu:
# tapeutil
General Commands:
1. Open a Device
2. Close a Device
3. Device Info
4. Tape Drive Service Aids
5.
6.
7.
8.
Inquiry
Test Unit Ready
Reserve Device
Request Sense
9.
10.
11.
Q.
Log Sense Page
Mode Sense Page
Release Device
Quit Program
Medium Changer Commands:
12. Element Information
13. Position To Element
14. Element Inventory
15. Exchange Medium
16.
17.
18.
19.
Move Medium
Load/Unload Medium
Initialize Element Status
Prevent/Allow Medium Removal
Tape Commands:
20. Query/Set Parameters
21. Prevent/Allow Medium Removal
22. Rewind
23. Erase Gap
24. Forward Space Filemarks
25. Forward Space Records
26. Space to End of Data
27. Log Sense
28. Display Message
29. Synchronize Buffers
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
Read and Write Tests
Unload Tape
Erase
Write Filemarks
Backward Space Filemarks
Backward Space Records
Query/Set Tape Position
Read or Write Files
Query/Create/Change Partition
Report Density Support
Enter Selection:
207
IBM-AIX
5.5.7 Problems with AIX
The machine freezes on booting with error 0518.
The system cannot complete a mount.
1.
2.
3.
4.
Insert the first installation CD.
Switch on the machine.
When there is a white screen after the fourth ICON, press the F1 key.
Then change the boot sequence in the maintenance menu and then boot first from the
CD.
5. The system then automatically starts up from the CD.
6. F1 ↵
7. 1 ↵ (English)
8. 3 ↵ (Start Maintenance Mode for System Recovery)
9. 1 ↵ (Access a Root Volume Group)
10. 0 ↵ (Continue)
11. Then select the boot disk
12. 1 ↵ (Access this volume and start a shell)
13. The system then carries out a mount on all important file systems.
14. If there are problems, the fsck must be carried out manually.
15. Then reconstruct the boot sequence with the commands:
bootlist –m normal –o
to show the current status
bootlist –m normal hdisk0 to specify the disk as the first
bootlist –m normal –o
to show current status
208
6 CentricStor in Windows
6.1 NT 4.0
6.1.1 Installation
●
Primergy 070 with LAN and SCSI card (FC card is removed)
●
Format SCSI disk via Adaptec BIOS. If you do not do this, problems may occur
if Linux etc. was previously installed on the machine.
●
Install the NT 4.0 basic system if it is not already present.
●
Install Service Pack 6a if it is not already present. LP8000 requires Service Pack 3 or
higher. We strongly recommend the use of SP 6a.
●
Insert the Qlogic card QLA2200F with BIOS 1.61 and install the driver for NT 4.0
(Version. 7.02.05.02) from the floppy disk delivered with the card
or
Insert LP8000 card and then, for example, install the driver for NT 4.0
(Version. 4-4.53a5), which can be downloaded from http://www.emulex.com.
●
Then reboot the system.
●
After this, Qlogic or LP8000 must be visible as SCSI devices (system control ➟ SCSI).
●
Attach the fibre channel and create a link to ICP (zoning on the switch etc.).
●
Via system control ➟ search for tape device drives.
●
Driver is requested. Then, for example, install M2 TapeDrive Device Driver V2.10
(m2_v210_winnt.exe) from EXABYTE. The driver can be downloaded from
http://www.exabyte.com. This process must be repeated for all drives. Which driver is
to be installed depends on the applications you intend to use (see chapter “Tape
management systems” from page 221).
●
This completes the installation.
209
NT 4.0
CentricStor in Windows
●
The following restriction applies for the Windows operating system: no more than 32
LUNs can be released for Windows in CentricStor. If more LUNs are configured for Windows in CentricStor, it can happen that Windows will see all the devices but will not load
any tape device drivers.
●
The session rest time must be set using a command to 0 minutes. If you do not do this,
NT will ask all visible devices if they are still there and will disturb any running I/Os.
net config server /autodisconnect:0
●
If an LUN (vtd) is being used over other hosts and is thus blocked, NT will abort at this
device during the reboot and device scan and will not be able to find the successive
devices with higher LUNs.
●
NT4.0 can only see drives of one type on CentricStor.
●
When booting with QL2200 the following error messages are written regularly in the
system event log:
"The driver has found a controller error on \Device\SCSI\ql2200 or
ql22001" with the event data: "80110000, f0130000, f0210000,
f0140000, f0170000".
This is normal behavior and occurs, for example, when there are changes in the FC
topology.
●
In order to ensure that the specified block size of 192 KB is maintained in Windows NT
and Windows 2000 with the Qlogic FCC Miniport Driver for the QLA2200 adapter for
Exabyte Mammoth-2, you must ensure that the registry
HKEY_LOCAL_MACHINE ➔ SYSTEM ➔ CurrentControlSet ➔ Services ➔ Ql2200
➔ Parameters ➔ Device
has a high enough setting for the value MaximumSGList:REG_DWORD .
The default of 0x21(33) in some newer driver versions (e.g. 8.1.5.10 NT4 IP or W2K
IP, FW Version 2.02.01 TP/IP) gives an unsuitable block size of only 128 KB; this
rules out volume-sharing with other systems such as Linux.
If MaximumSGList:REG_DWORD is set to 0x41(65), the maximum block size is set
to 256 KB. Windows must be rebooted after the change. If the NetWorker volume is
labeled under MaximumSGList:REG_DWORD 0x41(65), it is then described with the
specified block size of 192 KB for Exabyte Mammoth-2.
210
Windows 2000/2003
6.2 Windows 2000/2003
The following restriction applies for the Windows operating system: A maximum of 32 LUNS
can be released for Windows in CentricStor. If more LUNS are configured for Windows in
CentricStor, it can happen that Windows sees all the devices but does not load any tape
device drivers.
In Windows 2003 logical devices are supported with the FC port driver 5-2.22a8 64.
6.2.1 Configuration
Recognizing more than 8 LUNs
●
Change to
HKEY_LOCAL_MACHINE➔ SYSTEM ➔ CurrentControlSet ➔ Control ➔
ScsiPort ➔ SpecialTargetList with REGEDIT.
●
Define a new key which corresponds to the emulation inquiry. Setup:
Vendor 8 characters
Device 16 characters
Version 1 character
Blanks are shown as _ .
Example
EXABYTE_Mammoth2________v
FSC_____CentricStor_____8
●
Define field. LargeLUNs: REG_DWORD: 0x1
●
For IBM 3590E emulation, an entry is not necessary because the emulation has set the
HiSupport Bit.
●
See also the Knowledge Base Article 243869 or 310072 in Microsoft Windows NT.
211
Windows 2000/2003
●
Windows can only see drives of one type on CentricStor.
●
When booting with QL2200, the following error messages are written regularly in the
system event log:
"The driver has found a controller error on \Device\SCSI\ql2200 or
ql22001" with the event data: "80110000, f0130000, f0210000,
f0140000, f0170000"
This is normal behavior and occurs, for example, when there are changes in the FC
topology.
●
In order to ensure that the specified block size of 192 KB is maintained in Windows NT
and Windows 2000 with the Qlogic FCC Miniport Driver for QLA2200 adapter for
Exabyte Mammoth-2, you must ensure that the registry.
HKEY_LOCAL_MACHINE ➟ SYSTEM ➟ CurrentControlSet ➟ Services ➟ Ql2200
➟ Parameters ➟ Device
has a high enough setting for the value MaximumSGList:REG_DWORD.
The default of 0x21(33) in some newer driver versions (e.g. 8.1.5.10 NT4 IP or W2K
IP, FW Version 2.02.01 TP/IP) gives an unsuitable block size of only 128 KB; this
rules out volume-sharing with other systems such as Linux.
If MaximumSGList:REG_DWORD is set to 0x41(65), the maximum block size is set
to 256 KB. Windows must be rebooted after the change. If the NetWorker volume is
labeled under MaximumSGList:REG_DWORD 0x41(65), it is then described with the
specified block size of 192 KB for Exabyte Mammoth-2.
●
Before the operating system is updated the device drivers on the host for the HBAs,
tape devices and robotics (jukebox/media changer) on the fibre channel must be
backed up with CentricStorfor safety’s sake, and after the operating system has been
updated any automatic driver update that takes place must be verified.
Reason: In Windows 2003 it has been observed that after an update the EXABYTE
Mammoth2 tape device driver installed previously has been replaced by a MICROSOFT
Mammoth2 tape device driver which was not compatible with the volumes written previously. Consequently CentricStor backups, for example, can no longer be used with the
Microsoft MM2 driver 5.2.3790.0 (01.10.2002)!
212
7 CentricStor on NAS systems
7.1 General information on saving using NDMP
CentricStor offers implicit cloning of tapes, which means that a copy of NDMP backups can
be created without placing an additional load on the NAS system .
7.2 NetApp
7.2.1 Prerequisites
Tests were performed in the following system environment:
●
NetApp FAS3020 with operating system version ONTAP 7.2.4 and FC controller
Qlogic 2312
●
Connection of NetApp via FC switch
7.2.2 Restrictions
NetApp filers support up to 64 tape devices. Consequently zoning and other suitable
measures must be used to ensure that the NetApp filer as far as possible only sees the tape
devices intended for it, but in no case more than a total of 64 tape devices.
Because of a restriction in the ONTAP operating system of the NetApp filers, it must also
be ensured that LUN 0 on all the ICP controllers which are visible for NetApp filers is set to
an emulation other than Mammoth2.
213
NetApp
CentricStor on NAS systems
7.2.3 Configuration
7.2.3.1
Configuration in CentricStor
IBM 3590E, Mammoth 2 and 9840B are tape emulations which have been tested successfully.
For performance reasons you are recommended to select the HOST setting (compression
by the host) for the GXCC configuration function Logical Drives in the Compression form; the
ON or OFF setting can also be used.
7.2.3.2
On the NetWorker server the CentricStor devices on NetApp filers are configured as NDMP
devices. The name of the devices is
rd=<data_mover>:<tape device>,
where <data mover> is the host name of the NetApp filer concerned and <tape device> is
the name of the tape device ascertained using the sysconfig -t command.
Example of a NetApp tape device name: nrst31a (cmp, norewind).
The device block size used by NetWorker for the CentricStor devices must be selected so
that the maximum possible block size for the systems involved is not exceeded and that a
uniform device block size is set for all CentricStor devices which are configured on the NetWorker server and on the storage nodes and NDMP devices controlled by this server. The
maximum block size supported by NetApp filers and CentricStor is 256k. In particular with
the device type 3590 the default value must therefore be reduced from 384k to 256k.
In newer NetWorker versions the device block size is set using the hidden attribute device
block size of the device resource. Another method which also works for older NetWorker versions is to set this value using the environment variable NSR_DEV_BLOCK_SIZE_<media
type>=<n> with <media type> as the device type, as specified in the device resource, and
<n> as the block size in kB.
Example: NSR_DEV_BLOCK_SIZE_3590=256
The jukebox resource’s load sleep, unload sleep and eject sleep timers are set as recommended for NetWorker (see section “Configuration of the “CentricStor” library” on page 222).
7.2.4 Useful commands
sysconfig -av
sysconfig -t
reboot
214
show hardware configuration
show tapes
reboot NetApp system
Celerra
7.3 Celerra
7.3.1 Prerequisites
Tests were performed in the following system environment:
●
Celerra Datamover NS700G with operating system version DART 5.5.24.204 (or
NS20G with DART 5.5.32.4)
●
Connection of Celerra via FC switch
7.3.2 Restrictions
Celerra only permits the addr- designation to identify NDMP tape devices, not the name designation. This is a general restriction of the DART operating system.
Example
The server_devconfig server_2 -list -scsi -nondisks command on the
Celerra Control Node supplies the following output (abbreviated here):
server_2 :
name
tape14
Scsi Device Table
addr
type
c64t0l13
tape
info
IBM 03590E1A E32E130000000D011D
On the Celerra Control Node the NDMP bufsz specified in
/nas/server/slot_<x>/param for the Datamovers connected to CentricStor may not be
set to more than 256.
In migrating from ONTAP 5.1 to ONTAP 5.2 the channel ID changed in the addr designation
of the tape device node (example: device c80t0l13 became c64t0l13). Corresponding
changes had to be made in NetWorker.
215
Celerra
7.3.3 Configuration
7.3.3.1
Configuration in CentricStor
IBM 3590E, Mammoth 2 and 9840B are tape emulations which have been tested successfully.
For performance reasons you are recommended to select the HOST setting (compression
by the host) for the GXCC configuration function Logical Drives in the Compression form; the
ON or OFF setting can also be used.
7.3.3.2
Configuration of Celerra
It is generally recommended that the block size for NDMP backups should be increased
from the default value of 128k to 256k, the maximum value possible in CentricStor. Under
certain circumstances the value to be set depends on the block size used by the backup
application, see below. The block size is set by issuing the command below for each DataMover on the Celerra ControlNode
server_param <data_mover_n> -facility NDMP -modify bufsz -value 256
and rebooting the Data-Mover.
The default values can be used for the other settings for the Data-Mover.
Example 1
Valid settings of a Data-Mover server_2 under DART OS 5.5.24.204:
$ server_version server_2
server_2 : Product: EMC Celerra File Server Version: T5.5.24.204
$ server_param server_2 -facility PAX -list
server_2 :
param_name
facility default
current
configured
paxWriteBuff
PAX
64
64
dump
PAX
0
0
allowVLCRestoreToUFS
PAX
0
0
checkUtf8Filenames
PAX
1
1
paxStatBuff
PAX
128
128
readWriteBlockSizeInKB
PAX
64
64
filter.numFileFilter
PAX
5
5
paxReadBuff
PAX
64
64
filter.numDirFilter
PAX
5
5
noFileStreams
PAX
0
0
nFTSThreads
PAX
8
8
scanOnRestore
PAX
1
1
filter.caseSensitive
PAX
1
1
nPrefetch
PAX
8
8
216
nRestore
writeToArch
writeToTape
nThread
Celerra
PAX
PAX
PAX
PAX
16
1
1
64
16
1
1
64
$ server_param server_2 -facility NDMP -list
server_2 :
param_name
facility default
md5
NDMP
0
maxProtocolVersion
NDMP
4
scsiReserve
NDMP
1
dialect
NDMP
''
convDialect
NDMP
'8859-1'
v4OldTapeCompatible
NDMP
1
bufsz
NDMP
128
current
0
4
1
''
'8859-1'
1
256
configured
256
Example 2
Valid settings of a Data-Mover server_2 under DART OS 5.5.32.4:
$ server_version server_2
server_2 : Product: EMC Celerra File Server Version: T5.5.32.4
$ server_param server_2 -facility PAX -list
server_2 :
param_name
facility default
current
configured
paxWriteBuff
PAX
64
64
dump
PAX
0
0
allowVLCRestoreToUFS
PAX
0
0
checkUtf8Filenames
PAX
1
1
paxStatBuff
PAX
128
128
readWriteBlockSizeInKB
PAX
64
64
filter.numFileFilter
PAX
5
5
writeToTape
PAX
1
1
paxReadBuff
PAX
64
64
filter.numDirFilter
PAX
5
5
noFileStreams
PAX
0
0
nFTSThreads
PAX
8
8
scanOnRestore
PAX
1
1
filter.caseSensitive
PAX
1
1
nPrefetch
PAX
8
8
nRestore
PAX
8
8
writeToArch
PAX
1
1
filter.dialect
PAX
''
''
nThread
PAX
64
64
$ server_param server_2 -facility NDMP -list
server_2 :
param_name
facility default
maxProtocolVersion
NDMP
4
current
4
configured
217
Celerra
convDialect
scsiReserve
dialect
includeCkptFs
md5
forceRecursiveForNonDAR
snapTimeout
bufsz
snapsure
v4OldTapeCompatible
7.3.3.3
NDMP
NDMP
NDMP
NDMP
NDMP
NDMP
NDMP
NDMP
NDMP
NDMP
'8859-1'
1
''
1
0
0
5
128
0
1
'8859-1'
1
''
1
0
0
5
128
0
1
256
On the NetWorker server the CentricStor devices on the Celerra are configured as NDMP
devices. The name of the devices is
rd=<data_mover>:<tape device>,
where <data mover> is the host name of the Data-Mover concerned and <tape device> is
the address of the tape device ascertained using the server_devconfig command (see
section “Restrictions” on page 215). Example of a Celerra tape device address: c64t0l13
(cmp, norewind).
The device block size set in NetWorker must be the same as the blksz value set in Celerra.
In addition, as with NetApp filers the device block size used by NetWorker for the
Centric-Stor devices must be selected so that the maximum possible block size for the systems involved is not exceeded and that a uniform device block size is set for all CentricStor
devices which are configured on the NetWorker server and on the storage nodes and
NDMP devices controlled by this server. The maximum block size supported by CentricStor
is 256k. In particular with the device type 3590 the default value must therefore be reduced
from 384k to 256k. If the device type Mammoth-2 is to be operated using the default block
size of 192k preset in NetWorker, the value of blksz on the Celerra must also be set to192k.
In newer NetWorker versions the device block size is set using the hidden attribute device
block size of the device resource. Another method which also works for older NetWorker versions is to set this value using the environment variable
NSR_DEV_BLOCK_SIZE_<media type>=<n> with <media type> as the device type, as specified in the device resource, and <n> as the block size in kB.
Example: NSR_DEV_BLOCK_SIZE_3590=256
The jukebox resource’s load sleep, unload sleep and eject sleep timers are set as recommended for NetWorker (see section “Configuration of the “CentricStor” library” on page 222).
218
Celerra
7.3.4 Useful commands, to be executed on the control node
Display tape devices:
server_devconfig server_<x> -list -scsi -nondisks
Create tape device node:
server_devconfig server_<x> -create -scsi -nondisks
Scan tape devices:
server_devconfig server_<x> -probe -scsi -nondisks
Reboot server_<x>
server_cpu server_<x> -reboot -monitor now
219
by f.f. 1992
8 Tape management systems
8.1 NetWorker (Legato/EMC and FSC)
8.1.1 Documentation
The CD from Legato/EMC contains help files and man files for all supported operating
systems. You are also referred to the EMC internet site.
8.1.2 NetWorker versions
CentricStor was tested with the following versions of FSC NetWorker:
Version
EKS
Host
5.5A30
1-4
Reliant UNIX
1, 3, 4
Solaris
5.5A40
-
Reliant UNIX
6.0A00
1
The definitive version of the STLI library (Silo Tape Library Interface) for ACI functions (AML
Client Interface) is libstlaci_310.so (see below: resource jukebox, Attribute STL
interface lib). This is supplied from NetWorker 5.5A30 EKS 4 onwards and is installed as
default under /opt/nsr/lib.
The DAS administration program Version 3.10 dasadmin_310 can be used to communicate with VDAS in CentricStor.
In this case export DAS_SERVER=<VLP-name> must be set.
dasadmin_310 is supplied from NetWorker 5.5A30 EKS 4 onwards and is installed as
default under /opt/nsr.
As of NetWorker 6.0A00 EKS 1, libstlaci_310.so and dasadmin_310 are also
supplied by FSC EP ST SMS 4 (Storage Management Software NetWorker).
221
NetWorker (Legato/EMC and FSC)
Tape management systems
8.1.3 Configuration of the “CentricStor” library
–
Model: other STL or DAS Silo or ACSLS Silo. System dependent restrictions are
explained in section “System specific” on page 257.
–
Control Port: VLP host name type=3590 [client=<hostname>]
The IP address for the VLP host must be entered in the /etc/hosts. The client
parameter for high availability configurations can be used with IP aliasing.
–
Devices:
This correspond to the attribute name (see above), as in real operation in the resource
devices.
–
Eject sleep: 1 (guide value)
The default NetWorker value of 5 is unnecessarily high for operation with CentricStor
and can be reduced.
–
Unload sleep: 2 (guide value)
and can be reduced.
–
Load sleep: 1 (guide value)
and can be reduced.
–
Idle_device_timeout: 1
–
STL device names:
STL device names refer to the ID used to address the logical device via the library path
(i.e. the LibDevName from column 7 Section [ ld ] in the configuration file
/usr/apc/conf/vtls.conf on the VLP host). This data is shown in the graphical
user interface in table form under:
[GXCC Function bar tools ➔ Global Status ;] Function bar tools ➔
Show Balloon Help Summary or in Global Status with balloon help for individual
virtual devices.
Example: VDAS device names D104
Example: VACS device names 2,0,0,6 (corresponding to LibDevName 2-0-0-6 (see
below) coordinates for VACS devices).
As with real operation, the STL device names must be entered exactly in the sequence
of device attribute assignment (see above).
–
222
STL interface lib:
/opt/nsr/lib/libstlaci_310.so (see NetWorker version above) for virtual ADIC
robot (VDAS).
/opt/nsr/lib/libstlstk.so for virtual STK robot (VACS).
If the NetWorker programs are not installed as standard, i.e. under /opt/nsr, the lib
path name must be adapted accordingly.
Miscellaneous
–
VDAS_TIMEOUT_MOVE
A mount request in CentricStor (vlm) is timed out by VDAS using the
VDAS_TIMEOUT_MOVE timer (default 100 minutes; this can be set in the CentricStor
configuration file section [ vls ] ). A timer set with the DAS environment variable
ACI_TIMEOUT_MOVE (default 1800 seconds) also runs on the client side
(dasadmin_301). This timer should always be set to a higher value than
VDAS_TIMEOUT_MOVE !
The inactivity timeout must also be set as appropriate in the NetWorker resource groups
(default 30 minutes).
The high default value of 100 minutes for VDAS_TIMEOUT_MOVE takes account of the
maximum restore times for physical cartridges.
–
ACSLS_SERVER for VACS
The following must be set in /etc/default/nsr or - from NetWorker V6 - in
/etc/res/defaults:
ACSLS_SERVER=<VLP host name>.
The IP address of the VLP host must be entered in /etc/hosts.
–
Coordinates for VACS devices
In the /usr/apc/conf/vtls.conf configuration file on the VLP host, the virtual
drives allocated to the VACS have a LibDevName in the form w-x-y-z, where w, x, y and
z are decimal numbers between 0 and 255 (see STL device names above).
–
Administration program cmd_proc for STK robot systems
As with the ACS library software (ACSLS) with the ACS system administrator (ACSSA)
of a real STK robot archive system, the virtual ACS (VACS) of CentricStor has an
administration interface or a user interface. See README file of the administration tool
/usr/apc/doc/LIESMICH.cmd_proc on the VPL host.
–
Large number of devices
If there is a large number of devices configured in NetWorker, devices must be disabled
if such a number is not actually needed (fewer running nsrmmd daemons for device
support).
In order to save internal NetWorker resources with a large number of devices (remote
nsrmmds) the Nrsrmmd polling interval in the resource server can be increased (default
10 seconds, give value 20).
223
–
Following ICP reboot
Volumes mounted in logical devices are discarded following an ICP reboot, so that
NetWorker outputs a warning with the next device access, e.g. a dismount (nsrd:
media warning: /dev/... opening: I/O error ; nsrjb: read open error,
I/O error).
–
Cleaning: does not occur
The logical devices do not support cleaning cartridges.
–
Options element status:
In order to use the function nsrjb -E (element status), the Element Status field in the
jukebox resource should be set using the Jukebox Options. However, this is NOT set by
default after configuration of the library with jbconfig.
–
Control port configuration for VDAS taking AutoVLP failover into account:
CentricStor V3.1D and higher can be configured in such a manner that
a) the IP addresses are linked to the VLP master and SVLP roles, i.e. when AutoVLP
failover occurs, the new VLP master takes over the IP address of the original VLP
master (GXCC menu Configuration ➟ NetWork Interfaces: VLP0 MASTER / VLP1
BACKUP). This is only possible when the VLP master and SVLP are located in the
same subnetwork.
b) the IP addresses are linked to the ISP hardware, i.e. when AutoVLP failover occurs,
the new VLP master must be addressed using the IP address of the original SVLP
(GXCC menu Configuration ➟ NetWork Interfaces: VLP0 ACCESS / VLP1 ACCESS).
This configuration must be defined if the VLP master and SVLP are not located in
the same subnetwork.
In case b) two das servers - the VLP master and SVLP - must be specified for the Control
Port of the NSR jukebox resource in FSC NetWorker (at least in 7.3 and higher). See NetWorker Manpage emass_silo:
"NETWORKER CONFIGURATION
The silo configuration is created with jbconfig. Among others, the following information has
to be entered:
Type of Installation:
Install an STL Silo
Kind of Silo:
DAS Silo (ADIC/EMASS/Grau)
Name of the host running the DAS software:
<das server1> [<das server2>] [type=<medium type>] [client=<client name>]
[port=<port number>] [timeout=<sec>]
with
<das server 1>: Host name of the DAS server
224
<das server 2>: The format with two DAS server names is used if the DAS server runs
on a high availability cluster of two hosts with names <das server 1> and <das server 2>.
Available only with DAS 3.01 and later…"
Example
CentricStor vtls.conf
…
[ lan ]
NAMES:IF00:IF01
IF00:VLP0:172.25.75.8:255.255.255.0:172.25.75.1:ACCESS
IF01:VLP1:172.25.75.10:255.255.255.0:172.25.75.1:ACCESS
…
Solaris /etc/hosts
172.25.75.8
172.25.75.10
eule1 Eule1 EULE1
eule2 Eule2 EULE2
On Solaris FSC NetWorker 7.4 jukebox resource
type: NSR jukebox;
application key: ;
application name: ;
auto clean: No;
auto media management: No;
autodetect id: ;
available slots: 1-1000;
bar code reader: Yes;
cleaning delay: 60;
cleaning slots: ;
comment: ;
control port: eule1 eule2 debug=3 client=172.25.82.218
timeout=7200;
current capacity: 48 TB, "Archive Clone: 0 KB", "PC Archive: 0
KB", "Indexed Archive: 0 KB", "Archive: 0 KB", "Indexed Archive Clone: 0
KB", "Full: 0 KB", "Default Clone: 0 KB", "PC Archive Clone: 0 KB","po3: 0
KB", "Default: 0 KB", "NonFull: 0 KB", "po2: 0 KB", "Offsite: 0 KB", "po1:
48 TB";
debug trace level: 0;
default cleanings: ;
deposit timeout: 15;
i
The following restriction applies on the NetWorker side: the High Availability
Feature, i.e. the specification of 2 VDAS servers, is not implemented in the firewall variant (libstlaci_fw_310.so, libstlaci_fw_cs.so,
dasadmin_fw_310).
225
i
In versions of NetWorker before V6, we recommended that you set the following
variables, as otherwise the drives are often set to disabled:
NSR_STL_PARALLEL_OPTIONS=NO
(no parallel mount)
i
When tapes are closed the following message may be issued:
nsrd: media notice: Volume ... on device ....: Block size 32768 bytes
not 196608 bytes. Verify the device configuration. Tape positioning by
record is disabelt
Correct tape processing is not impaired by this. The problem has been fixed in FSCNetWorker V7.1.
Restrictions
The import/export of logical volumes is not supported.
Jukebox configuration settings:
226
type:
NSR jukebox;
name:
stk_pow;
description:
;
model:
EXB-10i EXB-10e/EXB-10h EXB-120 EXB-210 EXB-400 Series
EXB-X80 EXB-X200 HP-C1553A HP optical LMS Magstar
Magstar-MP DLT-4700 STK-9710 ACL Overland-LXB Emass
AML/S
Faststor Scalar 100 Standard SCSI Jukebox 3494 Cashion ABBA
ABBA 3490 ABBA 8mm ABBA optical [STK Silo] other STL
SmartMedia ;
enabled:
[Yes] No ;
control port:
HASE-VLP;
devices:
/dev/iof0/rstape.14.933ba.1chn, /dev/iof0/rstape.14.933bachn,
/dev/iof0/rstape.14.933ba.2chn, /dev/iof0/rstape.14.933ba.3chn,
"rd=lieser:/dev/rmt/57cbn", "rd=lieser:/dev/rmt/58cbn",
"rd=lieser:/dev/rmt/63cbn", "rd=lieser:/dev/rmt/64cbn";
bar code reader:
[Yes] No ;
match bar code
labels:
Yes [No];
available slots:
1-200;
STL device names:
"1,0,0,1", "1,0,0,0", "1,0,0,2", "1,0,0,3", "1,0,0,4", "1,0,0,5",
"1,0,0,6", "1,0,0,7", "1,0,0,8", "1,0,0,9", "1,0,0,10", "1,0,0,11",
"1,0,0,12", "1,0,0,13", "1,0,0,14", "1,0,0,15";
STL device sharing:
;
STL interface lib:
/opt/nsr/lib/libstlstk.so;
SRS server:
;
auto clean:
Yes [No];
cleaning slots:
;
default cleanings:
5;
auto media
management:
[Yes] No ;
application name:
;
application key:
;
read hostname:
colorado;
NDMP jukebox:
Yes [No];
NDMP Type:
Standard NDMP NetApp ;
NDMP hostname:
;
remote user:
;
password:
;
NDMP jukebox
handle:
;
NDMP bus number:
;
NetWorker is configured using an alphanumeric or graphical interface. The examples in the
following figures show both variants.
227
The following figure shows the default settings (the alterations for CentricStor are marked
in red):
228
The following figure shows the settings of the jukebox properties made via the graphical
interface.
If the data, which is to be backed up, is already highly compressed, you can improve performance by using a non-compressing device node in NetWorker. In Windows there are
special settings (see section “System specific” on page 237).
i
After setting up or modifying a silo - especially after removing devices - it is best to
ensure that the hidden attributes in the resource silo, device number and drive number
are identical.
(Note: There is likely to be an improvement in FSC-NetWorker from version 6.1A10
onwards).
229
8.1.4 Configuration of virtual devices (NetWorker resource devices)
Further system-specific settings are given in page 237.
–
Name:
NetWorker does not, of course, recognize the physical devices in the real robot on
CentricStor. The pathnames of the device nodes in the resource devices (and resource
jukebox; see below) relate to the logical devices in CentricStor.
In UNIX, Linux, AIX, and Reliant-UNIX systems we strongly recommend that you do not
use the original device nodes in applications such as Networker and do not use the links
created by the system itself. Instead, use the links with uniform CentricStor names
which refer to the original device nodes.
Example:
NetWorker backup node 1 on RM600
NetWorker backup node 2 on Primepower
Link to Reliant UNIX device nodes
Link to Solaris device nodes
...
-
-
...
...
-
-
...
The no rewind function characteristic (descriptor n) is mandatory for NetWorker, as in real
operation.
230
The BSD option (explicit descriptor b for Solaris) is mandatory for NetWorker, as in real
operation.
Data compression by CentricStor can be activated (descriptor c) provided appropriate
data compression exists.
Other device characteristics, such as high data density (descriptor h), are not
supported.
–
Media family: tape
–
Media type: generic256
In NetWorker V6.0A00 and later, the attribute assignment generic256 is only made
visible with NSR_SHOW_GENERIC=1 in /nsr/res/defaults. In the case of an update
installation, the automatic conversion of generic256 to 8mm 5GB must be avoided by
setting export NSR_SHOW_GENERIC=1 before the installation or by making the entry
in /nsr/res/defaults before the first NetWorker start.
–
Volume default capacity: 895 MB
The default NetWorker value of 2 GB for generic 256 must be reduced to 895 MB for a
suitable capacity display of logical volumes. The value must be set before tape installation in order to be effective.
–
Further recommendations:
If the data which is to be backed up is already highly compressed, you can improve
performance by using a non-compressing device node in NetWorker. In Windows there
are special settings (see section “System specific” on page 237).
8.1.4.1
ACSLS interface
NetWorker currently only supports one ACSLS server. Thus a NetWorker server cannot
control a real robot and CentricStor simultaneously. From version V6.1 onwards the FSC
NetWorker can address several ACSLS servers.
Details about the possible causes of connection problems with VACS and troubleshooting
advice is given in section “Possible problems and troubleshooting advice” on page 372.
231
8.1.4.2
DAS interface
Before you can work with this interface, you must authorize access to the drive via DAS with
the command:
dasadmin alloc <virt. drive> UP <Client>
Details about the possible causes of connection problems with VDAS and other troubleshooting advice is given in section “Possible problems and solutions” on page 367.
Access to the virtual drive and to the planned volume number area must be permitted for
the client in CentricStor. These assignments are made within the framework of the
CentricStor configuration by the service engineer.
8.1.4.3
Fast mount support
As older NetWorker versions does not communicate this to CentricStor via supported
standard interfaces when using an LV only to write (fast mount1):
VDAS/DAS aci_scratch_set
VACS/ACSLS csc_set_scratch
a template can be used on UNIX machines, the so-called prerecycle script. This is made
available by the FSC NetWorker development department:
http://extranet.fujitsu-siemens.com/service/storage/centricstor/download/add-on
It is called nsr_CS_prerecycle.sh. From V7.1, it is supplied together with FSC NetWorker.
In FSC NetWorker the scratch functions for VACS and VDAS are new in Version 7.2. FSC
NetWorker 7.2 performs the fast mount only when a tape is recycled (i.e. only in the event
of an nsrjb -R or an automatic recycle).
In CentricStor the scratch function for VACS is already available in V2.1 and the scratch
function for VDAS is new in Version 3.1B.
To permit use of the fast mount with FSC NetWorker 7.2, the user must enter the corresponding library for the jukebox resource (query when setting up the silo of jbconfig):
VACS: /opt/nsr/lib/libstlstk_cs.so
VDAS: /opt/nsr/lib/libstlaci_cs.so
(Default: /opt/nsr/lib/libstlstk.so)
(Default: /opt/nsr/lib/libstlaci_310.so)
From EMC NetWorker 7.3.2 with Patch lgtpa86655 and from FSC NetWorker 7.3A00, the
prerecycle script for implementing fast mount can be completely dispensed with.
i
1
NetWorker cannot use the feature Post Disaster Recovery Scratch Volume Processing
(for the first time in K835.7 the physical tape acess is avoided after disaster recovery
in the case of a fast mount through a configurable, predefined label which the VLM
In the CentricStor environment, the term scratch mount is customarily used to describe mounting only for writing. NetWorker uses
the term fast mount for this.
232
writes): A NetWorker label contains not only the barcode but also a volume ID. This
ID is assigned by the NetWorker server. This ID is generated from several parameters, e.g. from the server’s IP address and the timestamp. The volume ID is
checked when relabeling takes place. If it does not match the value in the media DB
the volume is not relabeled.
8.1.4.4
Changing from NetWorker 5.5 to 6.1...
Changing from NetWorker 5.5 to NetWorker 6.1... makes no difference to CentricStor itself.
Within NetWorker the following points must be noted.
1. The index is converted and it is therefore no longer possible to return from NetWorker
6 to 5.
2. In 5.5 CentricStor devices of type generic256 were in use.
Caution: in an update installation to 6.0A00 it is converted by default to 8mm GB!
The conversion to type 8mm GB can be avoided, if
export NSR_SHOW_GENERIC=1
is set before the installation, or an entry is made in /nsr/res/defaults before the
first NetWorker start.
3. It is advisable to change the device type from generic256 to CentricStor. (The old
generic256 type volumes are compatible with the new CentricStor type, i.e.they can be
read, written and recycled).
4. NetWorker does not allow a subsequent device type change.
There is no automatic conversion of device types. To avoid the expense of deleting
devices in resource jukeboxes and resource devices and then re-entering them, use the
following tip:
–
–
–
–
Close NetWorker
Make a backup copy of nsr.res
Edit nsr.res: change media type from generic256 to CentricStor
Start NetWorker again.
If you have any problems, you can get help from NetWorker support.
5. Another tip: Jukeboxes/Silos can no longer be defined in the GUI in V6...., but only with
CLI jbconfig (as in Legato NetWorker).
Instead of Model other STL, Model DAS_SILO or ACSLS_Silo is now entered.
233
8.1.5 Configuring a jukebox in NetWorker on Solaris
The device nodes in Solaris must have the same numbers in the NetWorker jukebox as the
virtual drives in the associated VJUK emulation of CentricStor.
Sample configuration
ICP0 : 32 virtual drives V000 through V01F
ICP2 : 1 jukebox controller VJ01 and 32 virtual drives V200 through V21F
The target controllers in the ICPs have the following target IDs on the Solaris host via
persistent binding:
ICP2 : Target ID 53 (hex 35)
ICP0: Target ID 54 (hex 36)
Configuration steps:
1. Creation of an assignment list for virtual drives and slot numbers in
CentricStor (vjukadmin <JUKBOX-NAME> inventory drives)
2. Listing all Solaris device nodes which are to be configured in the jukebox
(Networker command inquire on the host)
3. Configuration of a jukebox using the NetWorker command jbconfig
!
CAUTION
The slot numbers in CentricStor are displayed by vjukadmin in hexadecimal
format. jbconfig of NetWorker displays these in decimal format (decimal 256
= hexadecimal 100).
1. Configuration step
Information as per vjukadmin in CentricStor:
VLP0 (VLP0_KAUZ)# vjukadmin VJ01 set offline
Jukebox VJ01 set to offline
VLP0 (VLP0_KAUZ)# vjukadmin VJ01 inventory drives
INQUIRY-DATA:
SLOT
DRIVE
VSN
0100
V000
0101
V001
...
011E
V01E
011F
V01F
0120
V200
0121
V201
...
013E
V21E
013F
V21F
-
234
Information as per NetWorker command inquire on the Solaris host:
bash-2.05# inquire
[email protected]:FSC
CS-TL
CentricStor
CentricStor
...
CentricStor
CentricStor
CentricStor
CentricStor
...
S/N: 0000000D001E
S/N: 0000000D001F
83.7|Autochanger (Jukebox)
S/N: 0C00000D0200
83.6|Tape, /dev/rmt/1cbn
S/N: 0000000D0201
S/N: 0000000D0202
S/N: 0000000D021F
S/N: 0000000D0220
S/N: 0000000D0000
S/N: 0000000D0001
CentricStor
CentricStor
The Solaris device node which corresponds to the virtual drive V000 in CentricStor is:
CentricStor
S/N: 0000000D0000
NetWorker command jbconfig on the Solaris host:
bash-2.05# jbconfig
1) Configure an AlphaStor/SmartMedia Jukebox.
2) Configure an Autodetected SCSI Jukebox.
3) Configure an Autodetected NDMP SCSI Jukebox.
4) Configure an SJI Jukebox.
5) Configure an STL Silo.
What kind of Jukebox are you configuring? [1] 2
Installing 'Standard SCSI Jukebox' jukebox - [email protected].
What name do you want to assign to this jukebox device? MYJUK
Should the jukebox use SRS managed devices? (yes/no) no
Turn NetWorker auto-cleaning on (yes / no) [yes]? no
The drives in this jukebox cannot be auto-configured with the available
information. You will need to provide the path for the drives.
Is (any path of) any drive intended for NDMP use? (yes / no) [no]
235
Please enter the device path information in one of the following formats:
/dev/rmt/1cbn --for local path or
host:device-path --for remote node or
host:drive-letter:directory path --for Windows disk file
Drive 1, element 256
Drive path ?
/dev/rmt/33cbn
Drive 2, element 257
Drive path ?
/dev/rmt/34cbn
.
Further information on NetWorker
●
The default setting in lus.conf must be checked and increased if you wish to
configure more LUNS in NetWorker.
Example
For Emulex LP9 (default 32 LUNS pci10df,f900:126-32C), increase to 64 LUNS
pci10df,f900:126-128C (A0517437).
●
For CentricStor the CDI option should be set to not used in accordance with the recommendation of FSC NetWorker QA. The default setting CDI SCSI commands has to date
resulted in the following being reported in the NetWorker daemon log:
nsrd: media notice: Volume "Sxxxxx" on device "/dev/rmt/1bn":
Block size is 32768 bytes not 262144 bytes. Verify the device
configuration. Tape positioning by record is disabled.
●
In the load test with NetWorker and VJUK, the following message often occurred in the
NetWorker daemon log:
nsrd: Jukebox
'VJnn' failed: get_elements_st: acquisition of locks failed
The message can be ignored:
Here the element status in the SCSI jukebox is not fetched. In other words there is no
CentricStor VJUK-specific error message, but it is information resulting from internal
NetWorker processes with a high level of parallelism.
8.1.6 Prefetch with FSC NetWorker
FSC NetWorker supports the prefetch topic in CentricStor Version V2.1 from Version
6.1A10 onwards.
Restriction: The NetWorker solution does not support several CentricStor silos.
236
8.1.7 Tips and tricks
1. Error message: ALL of the devices are in busy by nsrmmd
After setting up or modifying a silo - especially after removing devices - it is best to
ensure that the hidden attributes in the resource silo, device number and drive number are
identical. (Note: It is likely that an improvement to FSC-NetWorker will be introduced
from version 6.1A10).
2. FSC NetWorker 7.3A00 or higher no longer offers the media/device type CentricStor
explicitly. It can be made visible using the FSC NetWorker environment variable
NSR_SHOW_FSC_DEVICES=yes which must be entered in /nsr/res/defaults before
NetWorker is started.
3. CentricStor supports a maximum block size of 256 KB. In the case of CentricStor tape
emulations IBM 3590E1A the NetWorker default block size for 3590 must therefore be
reduced from 384 KB to 256 KB in FSC/EMC NetWorker. This must be done before labeling using NetWorker takes place. How the block size is configured is described in the
NetWorker Administration Guide.
8.1.8 System specific
8.1.8.1
Windows NT 4.0
●
When using the ACSLS interface, the software product LibAttach from StorageTek must
be used.
●
If the data which is to be backed up is already highly compressed, you can set the
variable NOR_NO_HW_COMPRESS=yes to switch off compression in the device emulations in CentricStor and thus achieve higher performance.
●
With Legato NetWorker and EXBYTE Mammoth2 devices, the following messages may
come through NetWorker:
nsrd: media…notice: Volume … on device …: Block size 32768 bytes not
196608 bytes. Verify the device configuration. Tape positioning by
record is disabled.
However, this does not disturb correct tape processing. The problem is eliminated in
FSC NetWorker.
237
●
8.1.8.2
238
NetWorker settings for Windows NT 4.0:
media type
8mm Mammoth-2
Device Nodes
\\.\Tape* (* = 0, 1, ... 10, 11, 12)
with ACSLS robot control model
ACSLS SILO
STL interface lib
libstlstk.dll
with DAS robot control model
DAS Silo
STL interface lib
libstlemass.dll
drive emulation
EXABYTE/Mammoth2
Windows 2000
●
be used. The product for Windows NT 4.0 can be used.
●
When using the DAS interface, the variables DAS_SERVER and DAS_CLIENT must be
defined as system variables under: Start ➟ Settings ➟ Control Panel. In the control panel
select the entry System (System Properties). In System Properties, click the Advanced
tab. In the center you will find a button called Environment Variables.
●
If the data which is to be backed up is already highly compressed, you can set the
variable NSR_NO_HW_COMPRESS=yes, to switch off compression in the device emulations in CentricStor and thus achieve higher performance.
●
With Legato NetWorker and EXBYTE Mammoth2 devices, the following messages may
come through NetWorker:
nsrd: media…notice: Volume … on device …: Block size 32768 bytes not
196608 bytes. Verify the device configuration. Tape positioning by
record is disabled.
However, this does not disturb correct tape processing. The problem is fixed in FSC
NetWorker.
●
When using Legato NetWorker on Windows 2000, the following message is sometimes
given by nsrmmd without any function problems: tape_bsf failed: Device must
be cleaned. This behavior is specific to CentricStor. The message section Device
must be cleaned is a reaction to the Windows operating system.
●
NetWorker settings for Windows 2000:
media type
8mm Mammoth-2
Device Nodes
\\.\Tape*
STK Silo
STL interface lib
libstlstk.dll
STL interface lib
drive emulation
●
8.1.8.3
EXABYTE/Mammoth2
VJUK settings
Application
Legato NetWorker 7.1.2
Platform
Windows 2000 SP4 5.00.2195
Jukebox type in CS
FSC CS-TL
Tape device type in CS
EXABYTE: Mammoth2
Jukebox type in application
Autodetected SCSI jukebox or standard SCSI
jukebox (jbconfig entry)
Media type in application
Mammoth2
Max. volume number per
jukebox in application
2.001 (with more than approx. 2001 slots+drives
jbconfig aborts with Failure 0x29 unknown
error)
Reliant UNIX
●
When using the ACSLS interface, the file: /etc/default/nsr from theVACS server
should be entered. As of V6, the file: /etc/res/defaults is used. Example:
ACSLS_SERVER=HASE-IDP1
●
NetWorker settings for Reliant UNIX:
media type
generic256
Device Nodes
/dev/iof0/rstape.*cn
c = optional compression
with ACSLS robot control model STK Silo
STL interface lib
libstlstk.so
other STL or DAS Silo
STL interface lib
libstlaci_310.so
drive emulation
FSC/CentricStor
239
8.1.8.4
Solaris
●
For NetWorker, the nodes with the modifier b (e.g. /dev/rmt/8bn) must always be
used. The b selects the so-called BSD behavior (no implicit space operation on close,
(see man st; man mtio), to which NetWorker is set. If you take a node without b,
NetWorker will have to keep dealing with positioning problems (visible in daemon.log).
When the Mammoth2 emulation is used the following settings should be made in the
st.conf file:
"EXABYTE Mammoth2",
....
EXB-M2
= 1, 0x35,
"Exabyte Mammoth2 8mm Helical Scan","EXB-M2";
0, 0x3de39, 1, 0x28, 0;
If SRS is used, the SCSI reserve/release (0x20000, ST_NO_RESERVE_RELEASE) is
disabled in the option field.
The following values apply without SRS:
"EXABYTE Mammoth2",
....
EXB-M2
= 1, 0x35,
●
"Exabyte Mammoth2 8mm Helical Scan","EXB-M2";
0, 0x1de39, 1, 0x28, 0;
When using the ACSLS interface, the file: /etc/default/nsr from the VACS server
should be entered. From V6 onwards, the file: /etc/res/defaults is used.
Example: ACSLS_SERVER=HASE-IDP1
●
240
NetWorker settings for Solaris:
media type
generic256
Device Nodes
/dev/rmt/*cbn
STK Silo
STL interface lib
/opt/nsr/libstlstk.so
other STL or DAS Silo
STL interface lib
/opt/nsr/libstlaci_310.so
drive emulation
FSC/CentricStor
c = optional
compression
●
8.1.8.5
VJUK settings
Application
FSC NetWorker 7.1 EKS 1-3
Platform
Solaris 9
Jukebox type in CS
FSC CS-TL
Tape device type in CS
FSC: CentricStor
Jukebox type in application
Autodetected SCSI jukebox or standard
SCSI jukebox (jbconfig entry)
Media type in application
CentricStor
Max. number of volumes per jukebox in
application
60,000
HP-UX
●
8.1.8.6
NetWorker settings for HP-UX:
media type
8mm Mammoth-2
Device Nodes
/dev/rmt/c*t0d*BESTnb
STK Silo
STL interface lib
/usr/lib/libstlstk.sl
DAS Silo
STL interface lib
/usr/lib/libstlemass.sl
drive emulation
EXABYTE/Mammoth2
IBM-AIX
●
Does not support DAS robot control.
●
NetWorker settings for IBM-AIX:
media type
8mm Mammoth-2
Device Nodes
/dev/rmt*.1
ACSLS_SILO
STL interface lib
/usr/lib/libstlstk.so.a
drive emulation
EXABYTE/Mammoth2
241
Example:
Extension of the rc.nsr start file:
# Start of lines added by NetWorker - DO NOT DELETE OR CHANGE THIS LINE
# installed by nsr_ize on Mo 17 Dez 16:14:53 2001
#
# Default locale
#
LANG=C
export LANG
# Override to a different locale if /usr/lib/nsr/LANG exist
[ -r /usr/lib/nsr/LANG ] && . /usr/lib/nsr/LANG
# make tape devices available - begin
for rmt in rmt12 rmt13 rmt14 rmt15 ; do
mkdev -l $rmt > /dev/console 2>&1
done
# make tape devices available - end
# StorageTek silo interface - begin
CSI_HOSTNAME=HASE-IDP1
export CSI_HOSTNAME
(/usr/bin/mini_el) > /dev/console 2>&1 &
(/usr/bin/ssi) > /dev/console 2>&1 &
# StorageTek silo interface - end
(
echo 'starting NetWorker daemons:') > /dev/console
if [ -f /bin/nsrexecd ]; then
(/bin/nsrexecd) > /dev/console 2>&1
(echo ' nsrexecd') > /dev/console
fi
if [ -f /bin/lgtolmd ]; then
(/bin/lgtolmd -p /nsr/lic -n 1) > /dev/console 2>&1
(echo ' lgtolmd') > /dev/console
fi
if [ -f /bin/nsrd -a ! -f /bin/NetWorker.clustersvr ]; then
(/bin/nsrd) > /dev/console 2>&1
(echo ' nsrd') > /dev/console
fi
# End of lines added by NetWorker - DO NOT DELETE OR CHANGE THIS LINE
242
8.1.8.7
Linux
●
When using the CentricStor emulation EXABYTE/Mammoth2:
FSC NetWorker from 6.1A00 EKS1-6 or from V6.1A10 with media type 8mm
Mammoth2 is to be operated on the Linux host, where the volume default capacity in the
NetWorker resource devices is to be set to 895 MB.
●
When using the CentricStor emulation FSC/CentricStor:
FSC NetWorker from 6.1A00 EKS1-6 with media type CentricStor is to be operated on
the Linux host, where the volume default capacity in the NetWorker resource devices is
already 895 MB by default.
NetWorker settings for Linux:
media type
CentricStor
Device Nodes
/dev/nst0...1
ACSLS_Silo
STL interface lib
/opt/nsr/lib/libstlstk.so
model DAS_Silo
STL interface lib
/opt/nsr/lib/libstlaci_310.so
drive emulation
FSC/CentricStor
1
NetWorker only supports non-rewind devices.
243
NetBackup (Veritas)
8.2 NetBackup (Veritas)
Currently only the NetBackup Data Center product supports the connecting of robots via
LAN.
8.2.1 Documentation
NetBackup documentation
Version
Release Notes Veritas NetBackup
3.4
Release Notes Veritas NetBackup
3.4.1
Installation Guide Veritas NetBackup BusinesServer
3.4.1
System Admistrator’s Guide Veritas NetBackup DataCenter for UNIX
3.4
User’s Guide Veritas NetBackup for UNIX
3.4
Installation Guide Veritas NetBackup DataCenter for UNIX
3.4
Media Manager System Admistrator’s Guide Veritas NetBackup
DataCenter for UNIX
3.4
Media Manager Device Configuration Guide Veritas NetBackup for UNIX 3.4
User’s Guide Veritas NetBackup for Microsoft Windows 95/98/NT/2000
3.4
Troubleshooting Guide Veritas NetBackup for UNIX
3.4
Installation Guide Veritas NetBackup BusinesServer for PC Clients
3.4
As of Version 4.5 there are no further printed editions. The manuals are available on CDs
or on the Internet at: http://www.veritas.com.
8.2.2 Installation
Example from Solaris
244
–
To install NetBackup, call install on the CD.
–
All queries to the installer are self-explanatory.
–
Approx. 200MB of disk space is required.
–
Default installation path is: /opt/openv/….
–
NetBackup is started by a S77…-script or with ‘initbprd’.
–
NetBackup is stopped with a K77….-script or with ‘bp.kill_all’.
NetBackup (Veritas)
8.2.3 Configuration
●
Configuration tool ( X): xbpadm.
●
Storage Units must be configured first, then the devices.
●
The device nodes must be cbn nodes:
c = optional compression.
b = BSD option which is needed explicitly for Solaris.
●
Classes must be defined for the backup jobs.
Notes / Features
●
NetBackup works with standard UNIX tape access: mt / tar.
●
From Version 4.5 the term Class is no longer used and is now interpreted as Policy.
●
st.conf on Solaris must be adapted appropriately for CentricStor (see above).
●
On Solaris, the sg driver from Veritas must also be installed. See: Media Manager Device
Configuration Guide from Veritas.
●
There are problems with the Java user interface. xbpadm (X-Tool) is recommended as
a replacement.
●
/opt/openv/volmgr/bin/robtest for diagnosing devices and acs interface
(see System Administrator’s Guide, Appendix B, Robotic Test Utilities)
●
In the NetBackup ‘inventory’, VACS only returns tapes which are already known to
VACS or have already been accessed.
●
In supporting ACS robot interfaces, ensure that only up to 20 spaces for drives are
supported per panel. This restriction must be observed in the configuration of a virtual
drive in CS. The drive coordinates are stated in the form:
ACS(0-126)-LSM(0-23)-Panel(0-19)-Drive(0-19). The numbers in brackets state the
permitted values where only the values 0-11 can be used for NetBackup in drives. This
must be followed in the definition of virtual drives in CentricStor.
●
When using the DAS Robot interface, you must ensure that in NetBackup V3.4 only the
first 15 DAS drives are supported. As of NetBackup Version V4.5, up to 250 drives are
supported.
●
No additional modules are needed to support robot interfaces ACS and DAS. Windows
is an exception (see section “System specific” on page 257).
245
NetBackup (Veritas)
●
It is recommended that you do not configure the same device (virt. device in
CentricStor) in several NetBackup systems. If the same device is under robot control in
parallel NetBackup servers, it can be disturbed by SCSI commands. Where necessary,
set the device to the NetBackup device status DOWN in the parallel system.
●
Before you can work with the DAS interface, you must authorize access to the drive via
DAS with: dasadmin alloc <virt. drive> UP <client>
DASADMIN is not shipped with NetBackup and must be purchased separately.
●
Details about the possible causes of connection problems with VDAS or VACS and
other troubleshooting advice is given in sections “Possible problems and solutions” on
page 367 (VDAS) or page 372 (VACS).
●
The ACS numbers configured in CentricStor must be strictly ascending.
NetBackup(W2K3) is not executable if, for example, ACS=0 is used for BS2000 and
ACS=2 for NetBackup (ACS=0 for BS2000 and ACS=1 for NetBackup would be OK).
●
A scratch pool must be configured in cmd_prog muss for NetBackup and the virutal
volumes must be accommodated there:
> define pool 0 5000 1
# poolid 1 für max. 5000 Volumes einrichten
ACSSA> set scratch 1 NBU000-NBU999 # Volumes in den Pool aufnehmen
ACSSA> logoff
●
The following filters must be entered in the configuration file
<netbackup_path>\volmgr\vm.conf:
INVENTORY_FILTER = ACS <netbackup_roboter_nummer> BY_ACS_POOL 1
<netbackup_roboter_nummer> is generally not equal to the ACSid configured in
CentricStor.
8.2.3.1
LMF configuration
Client configuration under Solaris 8
●
Only the client package may be installed: FJSVlmfc
●
The lmadmin tool is used for configuration:
lmadmin -c
Modifying the LMF client environment file
1.modify the system parameters
2.get library parameters from server
3.modify library parameters
4.modify drive parameters
5.display all parameters
e.end
Please select a function. (1-5,e)>1
246
i
NetBackup (Veritas)
Only the name of CentricStor has been specified: yin. For everything else the
default has been accepted.
Modifying the system parameters
network service name(or port number)[lmf](the name is defined in "/etc/services",q)>
the name of the server host(host name,q)[server01]>
the node name of the server host(the name is defined in "/etc/hosts",q)[yin]>yin
yin will be set
another node name(or IP address) of the server host(the name is defined in "/etc/hosts"(set
space for delete),q)>
security management of volume load authority[disable](1.disable,2.enable,q)>
1.modify the system parameters
2.get library parameters from server
3.modify library parameters
4.modify drive parameters
5.display all parameters
e.end
Please select a function. (1-5,e)>2
Set library parameters by the LMF environment file of the server
Get library parameters from server
Following library or drive parameters will be added
library ID
= 0000
library name[LibCS](alphanumeric less than 8 characters,q)>
drive type(V000)[128track](1.128track,2.36track,3.18track,q)>1
special file of drive(V000)(128track)[no special file](0-99,n.no special file,q)>
.....
i
The drive types are inquired for each library (for each ICP). Here you must note
which ICP the displayed drives belong to.
NetBackup configuration is implemented as for Windows 2000. The administration
console is started with xvmadm. From here you go via the file menu to the Device
Management. Robots and drives are configured there.
As of Version 4.5 the Motif interfaces xbpadm, xbpmon, xvmadm and xdevadm are no
longer supported. The Java interfaces jnbSA and jbpSA are recommended, and also
the command line and the menu-based program bpadm.
The following processes must run on the LMF client (the programs vmps and bpps
belong to NetBackup):
bash-2.03# vmps
root 5329
1
root 5323
1
root 5373 5323
root 5376
1
root 5372 5323
0
0
0
0
0
14:37:55
14:37:55
14:37:59
14:37:59
14:37:57
?
?
?
?
?
0:00
0:00
0:00
0:00
0:00
vmd
/usr/openv/volmgr/bin/ltid
avrd
lmfcd
lmfd
247
NetBackup (Veritas)
bash-2.03# bpps
root 5410
1 0 14:38:01 ?
0:00 /bin/sh
/usr/openv/netbackup/bin/admincmd/nbdbdmon --user=root
root 5422 5410 0 14:38:01 ?
0:00 /usr/openv/db/bin/nbdbd -basedir=/usr/openv/db --datadir=/usr/openv/db/var --u
root 5331
1 0 14:37:55 ?
0:00
/usr/openv/netbackup/bin/bprd
root 5339
1 0 14:37:55 ?
0:01
/usr/openv/netbackup/bin/bpdbm
root 5471 4923 0 14:38:23 pts/8
0:00 bpadm
root 5343 5339 0 14:37:55 ?
0:00
/usr/openv/netbackup/bin/bpjobd
bash-2.03#
8.2.3.2
Connection of the robot controller (VACS) via a firewall
From the current version of NetBackup on, connection of the ACSLS robot controller is
supported via a firewall.
NetBackup V5.0 and service release 3 (available on the Internet at:
http://support.veritas.com) were used under Solaris for quality assurance.
The robot name configured in NetBackup must be determined before configuration takes
place:
/opt/openv/volmgr/bin/tpconfig
-> 2) Robot Configuration
-> 4) List Configuration
Currently defined robotics are:
ACS(0) ACSLS server = 172.25.95.166
The following variables must then be set on the NetBackup server in the file
/opt/openv/volmgr/vm.conf.
Syntax: ( variable = robot name port)
ACS_TCP_RPCSERVICE
ACS_CSI_HOSTPORT = 172.25.95.166 2001
ACS_SSI_INET_PORT = 172.25.95.166 2001
In CentricStor the fixed port is defined as follows:
GXCC -> Configuration -> VirtualLibraryService ->
VACS : RPC-Port Selection UserDefined
RPC-Port:
!
248
2001
Caution!
Communication is still handled via RPC!
Port 111/UDP may not be locked.
8.2.3.3
NetBackup (Veritas)
Template for supporting SCRATCH mount
When using an LV just for writing (FAST-MOUNT) NetBackup does not communicate this to
CentricStor over the supported standard interfaces:
VDAS/DAS
VACS/ACSLS
aci_scratch_set
csc_set_scratch
Instead of this, the following template can be used on UNIX systems.
#!/bin/sh
#----------------------------------------------------------------------#
Example of fast access to (=recycle) volumes
#----------------------------------------------------------------------HOST=yin
VSNList=`/usr/openv/netbackup/bin/admincmd/bpmedialist -l | \
/usr/bin/awk '{print $11, $1}' | \
/usr/bin/egrep '^0' | \
/usr/bin/awk '{print $2}'`
for VSN in $VSNList
do
rsh $HOST /usr/apc/bin/vlmif conf -r -n -v $VSN
done
This script truncates the LV to the part which is always contained in the cache, so no restore
is required in the event of the next mount.
In newer versions of NetBackup the following template can be used:
set +vx
TZ=GMT-26
# set time + 24 h
HOST1=CS1
HOST2=CS2
DATE=`date +%m/%d/%Y`
# will be the next day in the script shell
TZ=Europe/Berlin
# Find tape (LV) which expire today in the media DBD's
/usr/openv/netbackup/bin/admincmd/bpmedialist -summary | /usr/bin/grep $DATE
| awk '{print $1}' | sort -u >/tmp/list # list of LVs which expire tomorrow
# Reset der VSN's
/usr/bin/cat /tmp/liste | while read VSN1
do
rsh -n $HOST1 /usr/apc/bin/vlmif conf -r -n -v $VSN1
done
249
NetBackup (Veritas)
8.2.3.4
Sample screens
Overview:
250
NetBackup (Veritas)
Main screen:
251
NetBackup (Veritas)
Define Storage Unit:
252
NetBackup (Veritas)
Add New Unit:
253
NetBackup (Veritas)
Configure Devices:
254
NetBackup (Veritas)
Configured Classes:
255
NetBackup (Veritas)
Monitoring:
256
NetBackup (Veritas)
8.2.4.1
Windows NT 4.0
●
NetBackup Datacenter from Version 3.4.1.
●
The NetBackup Datacenter Patch NB_341_2 must be used.
●
Only supports ACSLS robot control.
●
be used.
●
VERITAS recommends the 3590E emulation.
●
NetBackup Datacenter 3.4.1
Sometimes the event log records event 4118: "Cannot read Volume header on
drive x (device y, \\.\Tape z); retrying ... ". The label is written with
block length HEX 400, but is read with HEX 8000. Thus there is no functional restriction
on the Backup/Restore.
NetBackup/NT configuration setting:
Drive type
½“ cartridge (hcart)
media type
HCART
Device node (no
rewind device)
Tape0, Tape1, ...
with ACSLS robot
control, robot type
ACS automated cartridge
system
ACSLS host
Name of the host where IP address: in
VACS is running (normally Winnt\system32\drivers\etc\hosts
the name of the VLP)
drive emulation
EXABYTE/Mammoth2
or
alternative emulation
IBM/IBM 03590E1A
Driver: Mammoth2 V2.10 from
EXABYTE
Driver: halfinch.sys from VERITAS
file version 5.00
Caution: the halfinch driver can
only be installed after installing
NetBackup.
257
NetBackup (Veritas)
●
Additional parameter settings (for example values, adapt as necessary)
NetBackup admin ➔ configure NetBackup:
8.2.4.2
●
Master Server, right click ➔ Properties ➔
Universal settings: logging enabled; logging level=10
Global NetBackup attributes: maximum jobs per client=20
●
Media Server, right click ➔ Properties ➔
●
Clients, right click ➔ Properties ➔
●
Storage unit management ➔ Storage Unit Properties:
maximum concurr. Drives for backup=8
maxim. Multiplexing per drive=2 (1 to 32; default 1)
●
Backup policy management ➔ class double-click:
limit jobs per class= 99 explicit (=default?)
Schedules ➔ Schedule double click ➔ media multiplexing=2
(1 to 32; default 1)
Caution: Multiplexing increases restore time.
Windows 2000
●
●
●
Only supports ACSLS robot control.
●
●
VERITAS recommends the 3590E emulation.
●
NetBackup Datacenter 3.4.1
Sometimes the event log records event 4118: Cannot read Volume header on
drive x (device y, \\.\Tape z); retrying ... . The label is written with block
length HEX 400, but is read with HEX 8000. Thus there is no functional restriction on
the Backup/Restore.
258
NetBackup (Veritas)
Configuration settings NetBackup/Windows:
8.2.4.3
Drive type
media type
HCART
Device node (no
rewind device)
Tape0, Tape1, ...
with ACSLS robot
control: robot type
ACS automated cartridge
system
ACSLS host
Name of the host where IP address: in
VACS is running (normally Winnt\system32\drivers\etc\host
the name of the VLP)
s
drive emulation
EXABYTE/Mammoth2
Driver: Mammoth2 V2.10.0.0
from EXABYTE
alternative emulation
IBM/IBM 03590E1A
Driver: halfinch.sys from
VERITAS
file version 5.0.1.1
Driver version: 4.0.1381.1
Caution: The Halfinch Driver
can only be installed after
installing NetBackup.
Windows 2003
●
The logical volumes can be added in NetBackup with ”New Volumes”.
●
The avr daemon of NetBackup on Windows often reports the following:
Event 4111 "GetTapeParameters () failed Device must be cleaned".
This does not result in any functional restriction.
●
Veritas requests
–
–
–
–
8.2.4.4
NetBackup version: V6.0 MP4
Library in CentricStor: VACS (libattach 1.4.1 required)
Media type: HCART
Emulation in CentricStor: IBM Magstar 3590E1A
Reliant UNIX
TSM does not support Reliant UNIX from FSC. Only Reliant from Pyramid is supported, but
no quality assurance is provided by CentricStor.
259
NetBackup (Veritas)
8.2.4.5
Solaris
●
●
Configuration settings of NetBackup/Solaris:
Drive type
media type
HCART
Device node (no rewind device) /dev/rmt/*cbn
●
c = optional
compression
with ACSLS robot control:
robot type
ACS Automated Cartridge System
with DAS robot control
robot type
TLM Tape Library Multimedia
drive emulation
FSC/CentricStor
NetBackup configuration is implemented as for Windows 2000. The administration
console is started with xvmadm (another option is xnb). From here you go via the file
menu to the Device Management. Robots and drives are configured there.
As of Version 4.5 the Motif interfaces xbpadm, xbpmon, xvmadm and xdevadm are no
longer supported. The Java interfaces jnbSA and jbpSA are recommended, and also
the command line and the menu-based program bpadm.
●
260
The sg driver must also be installed. See: Media Manager Device Configuration Guide from
Veritas.
●
NetBackup (Veritas)
To avoid hold-ups due to long waiting times for messages, it is strongly recommended
that you lengthen the system message queue.
To do this, you must extend the file /etc/system with the following entry:
..
# Settings for VERITAS NetBackup, T.Daude 28.02.02 VERITAS Software GmbH
set msgsys:msginfo_msgmap=4096
set msgsys:msginfo_msgmax=4096
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgmni=16
set msgsys:msginfo_msgssz=64
set msgsys:msginfo_msgtql=4096
set msgsys:msginfo_msgseg=4096
●
You should detach the sockets first. Set the file
/etc/rcS.d/S55network4NBU with the following content:
#!/sbin/sh
# Einstellung fuer VERITAS NetBackup, damit Sockets bereits nach
# 30 sek. vom System zu Wiederverwendung freigegeben werden
# (Default: 4 min)
# T. Daude, VERITAS Software GmbH
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 30000
8.2.4.6
HP-UX
Settings for improved performance:
●
Extend block number and block size to 256KB:
#echo "262144" >/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
#echo "16" >/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
●
For TCP/IP network connections, extend the buffer size.
#echo "65536" >/usr/openv/netbackup/NET_BUFFER_SZ
●
NetBackup/HP-UX configuration settings:
Drive type
media type
HCART
Device node (no rewind device)
/dev/rmt/c*t0d*BESTnb
with ACSLS robot control: robot type
with DAS robot control: robot type
CentricStor emulation
FSC/CentricStor
261
NetBackup (Veritas)
8.2.4.7
IBM-AIX
●
The device node must be set to extended filemarks. This setting is preset for AIX 4.3.
chdev –l 'rmt0' –a extfm='yes'
●
NetBackup/AIX configuration settings:
Drive type
media type
8.2.4.8
/dev/rmt*.1
with ACSLS robot control: robot type
with DAS robot control: robot type
FSC/CentricStor
Linux
●
262
Device node (no rewind device)
In NetBackup V6.0 MP5 and higher on Linux Redhat via SAN connection
Data Protector
8.3 Data Protector
8.3.1 Documentation
The documentation for Data Protector is shipped on CD together with the product.
8.3.2 Licenses
The following licenses may also be needed for Data Protector:
–
–
–
Cell Manager Multi-Drive
Multi-Drive Server (if other servers are linked to CentricStor)
Unlimited Slot Libraries Extension for STK ACSLS or EMASS/GRAU DAS
8.3.3 Miscellaneous
Up to Version 4.1 the software was marketed under the name Omniback.
As CentricStor mounts virtual volumes extremely quickly, you must ensure that the
hardware configuration of the Data Protector environment is appropriately defined. To avoid
bottlenecks this may call for relocation of the mount server to its own system.
Data Protector currently only releases the media for a save job once the entire job has run.
As the media table is contained in shared memory, parallel long save runs can lead to a
bottleneck in media management. A remedy can be found in optimum distribution of the
long and short jobs. It is planned to change this behavior of the media management in
Data Protector V5.5.
263
Data Protector
8.3.4 Installation in UNIX systems
8.3.4.1
8.3.4.2
Installation of Data Protector
●
Call /usr/sbin/swinstall
●
In the Specify Source window, choose the menu item Select Network Directory/CDROM and
specify the mount point of the CD-ROM. Then click OK to open the SD Install - Software
Selection window. The Data Protector product appears in the list of available products.
●
Select it for installation with Mark for Install under the Actions menu item.
●
Under the Actions menu item, select Install analysis and then click OK to start the installation.
●
After the installation you can start Data Protector with:
/sbin/init.d/omni start
and stop it with
/sbin/init.d/omni stop
●
Starting <DATA_PROTECTOR_HOME>/bin/xomni starts the graphical configuration
menu.
Configuration of CentricStor in Data Protector
Make sure that the virtual drives register as FSC-CentricStor, so that Data Protector is
unknown. For this reason, when you click on the Data Exchange Device menu, you only get
the error message that no devices are present. In this case you must just specify the device
nodes manually e.g. /dev/rmt/c0t0d0BEST.
Up to version 3.5, you must also activate the menu item Use direct library access under
Advanced options in the drive configuration. From version 4.1 onwards, there is no need to
activate this item.
Under VDAS the option of using Exabyte Mammoth2 as a tape emulation is also available.
Here the media type T3480/T... is selected for FSC-CentricStor for library and drives, and
the media type Exabyte for Exabyte Mammoth2.
Under VACS it is not possible to use Exabyte Mammoth2 as the media type Exabyte
cannot be selected.
264
8.3.4.3
Data Protector
Template for SCRATCH mount support
When using an LV just for writing (FAST-MOUNT) Data Protector does not communicate
this to CentricStor over the supported standard interfaces:
VDAS/DAS
VACS/ACSLS
aci_scratch_set
csc_set_scratch
Instead of this, on UNIX machines you can set the following template:
#!/bin/sh
#--------------------------------------------------------------------# Example of fast access to (=recycle) volumes
#
# Limiting conditions:
#
- Omniback must work with compressing device nodes
#
- Compression must be active in CentricStor
#--------------------------------------------------------------------VSNList=`/opt/omni/bin/omnimm -list_scratch_media "Default
T3480/T4890/T9490" | \
/usr/bin/grep "\[" | \
/usr/bin/awk -F[ '{print $2}' | \
/usr/bin/awk -F] '{print $1}'`
for VSN in $VSNList
do
remsh CentricStor-VLP /usr/apc/bin/vlmif conf -r -n -v $VSN
done
This script truncates the LV to the part which is always contained in the cache, so no restore
is required in the event of the next mount.
265
Data Protector
8.3.4.4
Template for PREFETCH support
#!/bin/sh
#--------------------------------------------------------------------# PREMOUNT for fast access to volumes on restore
#
#--------------------------------------------------------------------PREMOUNT_LOG=/var/opt/omni/log/premount.log
echo "====================B=E=G=I=N=N===================="
>>$PREMOUNT_LOG
date >>$PREMOUNT_LOG
VSNList=`cat /tmp/premount.txt`
for VSN in $VSNList
do
echo $VSN >>$PREMOUNT_LOG
remsh 130.11.10.81 /usr/apc/bin/vlmif prefetch -v $VSN >>$PREMOUNT_LOG
2>&1
done
date >>$PREMOUNT_LOG
echo "-----------------------E-N-D-----------------------"
>>$PREMOUNT_LOG
echo "---------------------------------------" >>$PREMOUNT_LOG
8.3.4.5
Bypassing lengthy backup times in Data Protector
Under Data Protector the problem can occur that backup times are prolonged by a restore
on the back end. This is caused because sorting of the free (virtual) cartridges is a
permanent process, i.e. the FREE ALLOCATION TABLE is constantly being updated, with
the result that scratched and newly released cartridges get mixed. Load times range from
under one second up to several minutes.
This behavior for handling free (virtual) cartridges within Data Protector is bypassed by
removing the virtual volumes whose retention period is due to elapse on the next day from
the media pool and assigning them to a storage pool. The volumes can remain in the latter
pool until the retention period has elapsed. They are then scratched and moved into the free
pool from which Data Protector takes the tapes for backups.
266
Data Protector
Media pool maintenance for bypassing
lengthy load times for virtual libraries
4. Tapes with
backup data
1. Determine the
tapes whose retention
period is due to
elapse on next day
and move to
STORAGE
2. Scratch expired
tapes and move to
FREE
Backup
Media pool DEFAULT
Media pool STORAGE
3. Remove scratched
tapes for backup
Media pool FREE
A prerequisite for the procedure described is that the media pools have been set up:
–
–
–
Scratch all virtual volumes in the FREE pool.
Move the virtual volumes whose retention period elapses in the next 2 days into the
STORAGE pool.
Set up a recurring job which handles pool maintenance.
Scripts for pool maintenance
The procedure for pool maintenance is implemented for Data Protector using the following
scripts:
●
prefree_morgen.x
Determine the virtual cartridges which expire on the
following day
●
obii_lager-scratch.x
Scratch expired cartridges in STORAGE pool
●
shift-lager-free.x
Move to the FREE pool
●
datum+1.x
Help script for current date + 1
267
Data Protector
Script: prefree_morgen.x
# Set Working Directory
export WORKDIR=/rzf/db/omniback/etc/hsc/TAPES/prefree
# Determine current date + 1
export DATUM=`$WORKDIR/datum+1.x`
# List Omniback DEFAULT pool for CentricStor
/opt/omni/bin/omnimm -list_pool "Default T3480/T4890/T9490" >
$WORKDIR/ausgabe
#Determine locations in CentricStor.
#The result is a list of the following type:
#R00234
#R12345
#R22334
#...etc.
grep $DATUM $WORKDIR/ausgabe > $WORKDIR/aus2
cat $WORKDIR/aus2 | awk '{ print $2 }' | sed -e 's/\[//' -e 's/\]//' >
$WORKDIR/aus3
#Process the list in a loop
for kassette in `cat $WORKDIR/aus3`
do
/opt/omni/bin/omnimm -move_medium $kassette "Lager Pre_Free"
done
Script: obii_lager-scratch.x
#!/bin/sh
#----------------------------------------------------------------------#
SCRATCH for fast access to (=recycle) volumes
#
#
Marginal condition:
#
- Omniback must work with compressing device nodes
#
- Compression must be active in CentricStor
#----------------------------------------------------------------------# Define log file
SCRATCH_LOG=/var/opt/omni/log/lager-scratch.log
VLP=172.25.95.165
# Check whether Sratch script is already running...
export PIDFILE=/opt/omni/lager-scratch-pidfile
export PID=$$
if [ -f $PIDFILE ]
then
kill -0 `cat $PIDFILE` 2>/dev/null
268
Data Protector
ret=$?
if [ $ret = 0 ] ; then
echo Zweiter Start von $0 verhindert! >> $SCRATCH_LOG
echo ABBRUCH von zweitem $0 am `date`>> $SCRATCH_LOG
exit
else
# Could have crashed...or been killed...
rm $PIDFILE
fi
fi
# Create PIDFILE...
echo $PID > $PIDFILE
# Start logging
echo "====================B=E=G=I=N=N====================" >>$SCRATCH_LOG
date >> $SCRATCH_LOG
# List of locations in CenctricStor
VSNList=`/opt/omni/bin/omnimm -list_scratch_media "Lager Pre_Free" | \
/usr/bin/grep "\[" | \
/usr/bin/awk -F[ '{print $2}' | \
/usr/bin/awk -F] '{print $1}'`
# Process the list in a loop
for VSN in $VSNList
do
echo $VSN >>$SCRATCH_LOG
remsh $VLP /usr/apc/bin/vlmif conf -r -n -v $VSN >>$SCRATCH_LOG 2>&1
done
date >> $SCRATCH_LOG
echo "----------------------E-N-D-E----------------------" >>$SCRATCH_LOG
echo "---------------------------------------" >>$SCRATCH_LOG
# Send mail...
echo " Protokoll liegt unter /var/opt/omni/log/lager-scratch.log auf H01102!" > /tmp/sc.$$
mailx -s "LAGER-Scratchlauf fuer CentricStore am `date` beendet "
[email protected] < /tmp/sc.$$
rm /tmp/sc.$$
# Delete PIDFILE
rm $PIDFILE
269
Data Protector
Script: shift-lager-free.x
# Define Working Directory
export WORKDIR=/rzf/db/omniback/etc/hsc/TAPES/prefree
# Determine cartridges without retention period
= None
/opt/omni/bin/omnimm -list_pool "Lager Pre_Free" >
$WORKDIR/shiftlager.ausgabe
grep None $WORKDIR/shiftlager.ausgabe | awk '{ print $2 }' | sed -e
's/\[//' -e 's/\]//' > $WORKDIR/shiftlager.aus
# Process in a loop
for kassette in `cat $WORKDIR/shiftlager.aus`
do
/opt/omni/bin/omnimm -move_medium $kassette "Free T3480/T4890/T9490"
done
Help script: datum+1.x.
#!/bin/sh
# tdate: A Bourne shell script that
# prints tomorrow's date
# Output Form: Month Day Year
# From Focus on Unix: http://unix.about.com
# Adjusted for template
# Set the current month day and year.
month=`date +%m`
day=`date +%d`
year=`date +%Y`
# Add 0 to month. This is a
# trick to make month an unpadded integer.
month=èxpr $month + 0`
# Add one to the current day.
day=èxpr $day + 1`
#Determine if it is the first day of
# the next month.
nextmonth=1;
case $month in
270
Data Protector
1|3|5|7|8|10|12)
if [ $day -eq 32 ]; then
nextmonth=0;
fi
;;
4|6|9|11)
nextmonth=0;
fi
;;
2)
#Determine if it is a leap year.
leapyear=1;
if [ èxpr $year % 4` -eq 0 ]; then
if [ èxpr $year % 400` -eq 0 ]; then
leapyear=0;
elif [ èxpr $year % 100` -eq 0 ]; then
leapyear=1;
else
leapyear=0;
fi
fi
if [ $leapyear -eq 0 ]; then
nextmonth=0;
fi
else
nextmonth=0;
fi
fi
;;
esac
# If it is next month then day is 1 and
# month is incremented by 1.
if [ $nextmonth -eq 0 ]; then
day=1
month=èxpr $month + 1`
#If month is 13 then it is Jan 1 of next year.
if [ $month -eq 13 ]; then
month=1
year=èxpr $year + 1`
fi
fi
271
Data Protector
# Leading zero in month
case $month in
1|2|3|4|5|6|7|8|9)
export month=0$month
;;
esac
# Leading zero in day
case $day in
1|2|3|4|5|6|7|8|9)
export day=0$day
;;
esac
# Ich nehme an in 16 Jahren ist das egal... :-)
export year=ècho $year|sed -e 's/20//'`
# Print the month day and year.
echo $month/$day/$year
exit 0
272
8.3.4.6
Data Protector
Configuration as StorageTek ACS library
Selection of robot as StorageTek ACS library
273
Data Protector
T3480 is selected as the tape type in the library configuration. The ACSLM host name is
the name of the machine in CentricStor on which VACS is running (normally the VLP).
The cap 0,0,0 is simply a default cap which is needed by Data Protector and accepted by
CentricStor.
Busy drive handling must be Abort.
The data device must be entered manually.
274
Data Protector
Logical device - Advanced options
275
Data Protector
8.3.4.7
276
Configuration as a GRAU-DAS library
Data Protector
T3480 is selected as the tape type in the library configuration. The DAS Server is the name
of the machine in CentricStor, the VDAS process is running. The E01 and I01 caps are
simply default caps which are needed by Data Protector and accepted by CentricStor.
Busy drive handling must be Abort.
The data device must be entered manually.
277
Data Protector
Logical device - Advanced
278
8.3.4.8
Data Protector
Setup of volumes
The simplest way to check that the configuration has been successful is to first format some
tapes which have been previously generated in CentricStor. Simply right click on the previously configured library and select the menu item Manage.
279
Data Protector
In the Library Management window under Edit, select the option Add Volsers and specify the
prefix and indices. These slots are then assigned to the library.
280
Data Protector
Library Management - CentricStor
After selecting a slot, under Edit, select the menu item Init and use this to format the tape.
281
Data Protector
Library Management - Initialize Medium
In the Init menu, you must only specify the media pool used by the library for the tape. If the
tape is already described with other programs, you must also select force initialization.
8.3.5 Installation example for Windows NT
The example shows an installation of Data Protector 4.1 with ACSLS in Windows NT.
Unpack ns4453a5.zip
Install device driver
282
Data Protector
Check if the driver has
been started
For operations over
ACSLS, LibAttach
must be installed
283
Data Protector
Check, to see if
LibAttach runs with
SSI
Definition of library
284
Data Protector
Specify the IP
address of the
VLP
Define CAP
285
Data Protector
Define Drive
Selection from the
list of recognized
SCSI drives
286
Data Protector
Enter the virtual
drive position
corresponding to
the CentricStor
configuration
Set drive type
287
Data Protector
8.3.6
8.3.6.1
VJUK configuration
General
Only 1500 slots are supported per VJUK emulation of DataProtector.
8.3.6.2
Configuration of the robots under AIX
With DataProtector, AIX can only be used as a client.
8.3.6.3
Configuration of the robots under HP-UX
After the devices under /dev/rmt have been deleted, the insf -e command is executed.
This program creates all device files anew. The device for the robot can be found under
/dev/rac.
8.3.6.4
Configuration of the robots under Solaris
A prerequisite is that the following configuration files are correctly set up:
/kernel/drv/st.conf
/kernel/drv/lpfc.conf
The sst driver is required for the robot. This is supplied by HP and is located under
/opt/omni/spt. It is copied to /usr/kernel/drv using its configuration file sst.conf as
follows (take care!):
●
Solaris 32-bit:
$cp /opt/omni/spt/sst /usr/kernel/drv/sst
$cp /opt/omni/spt/sst.conf /usr/kernel/drv/sst.conf
●
Solaris 64-bit:
$cp /opt/omni/spt/sst.64bit /usr/kernel/drv/sparcv9/sst
$cp /opt/omni/spt/sst.conf /usr/kernel/drv/sst.conf
The robot’s target and Lun are copied into file sst.conf.
Subsequently the line below is entered in the /etc/devlink.tab file:
type=ddi_pseudo;name=sst;minor=character rsst\A1
i
Blanks may not be used for whitespace, but only TABs.
The driver is then installed:
add_drv sst
288
Data Protector
After the reconfiguration boot (reboot -- -r) you can search for the device file for the
robot under the /devices directory. A link to this must be created from the /dev directory
if the system has not done this automatically, for example:
ln -s /devices/pci@1f,4000/scsi@3,1/sst@4,1:character /dev/rsst4
You see the name of the rsst* device in the boot log (dmesg) or system log
(/var/adm/messages).
8.3.6.5
Configuration of the robot devices under Windows
After CentricStor has been connected, the Windows system automatically recognizes the
robot and the drives. You can see the robot under the autochanger in the device manager.
Tape and robot devices are displayed using the DataProtector devbra -dev command.
8.3.6.6
Configuration of a library under Solaris
Library - General:
289
Data Protector
Library - Control:
290
Data Protector
Library - Repository:
291
Data Protector
Library - Settings:
292
Data Protector
Drive - General:
293
Data Protector
Drive - Drive:
294
Data Protector
Drive - Settings:
295
Data Protector
8.3.7 Miscellaneous
8.3.7.1
Virtual drives
As Data Protector does not recognize the drive FSC-CentricStor, this error message will
appear every time the drive is accessed:
Unknown Device, please check device support matrix
as shown in the figure below. However, the error message has no effect on operations.
To suppress this warning, create the following file:
HP-UX:
Other UNIX systems:
Windows systems:
296
/opt/omni/.devtab
/usr/omni/.devtab
<Data_Protector_Home>\devtab
Data Protector
This file contains the line
CentricStor
CentricStor
5
5
Product ID which you obtain as follows:
HP-UX:
Load tape and enter the command
diskinfo -v /dev/rmt/<device name>.
Windows:
Look in the SCSI registry which you can find under
HARDWARE\DEVICEMAP\Scsi.
Media type which can be found in Table A-1 in the appendix of the
hp OpenView Data Protector Administrator's Guide.
If there are two devices in the system with the same product ID but with different
vendor IDs, the line must look as follows:
<product_ID>
<vendor_ID>
<media_type_number>
The vendor ID is also displayed in response to the aforementioned diskinfo command.
For further details, see Configuring Unsupported Devices in the hp OpenView Data Protector
Administrator's Guide.
8.3.7.2
DAS interface
From Data Protector A.03.10 onwards, more than 15 drives will be recognized as long as
the following two conditions are fulfilled:
1. The following patches are used:
Data Protector version
Patch
A.03.10
PHSS_21642
A.04.10
PHSS_26358
2. The following variable has been set in the.omnirc file:
OB2DASDRIVESTATUS2=1
●
In order to enable DAS control, the DAS media agent must first be installed on the client.
This software must be purchased and can be obtained from ADIC (robot manufacturers). Also see: http://www.adic.com.
297
Data Protector
HP-UNIX:
●
The shared library libaci.sl from the ADIC DAS package must be copied to
<Data_Protector_Home>/lib.
●
The file .omnirc.TMPL in <Data_Protector_Home> must be copied to .omnirc in the
same directory and must be extended with the following entry:
DAS_SERVER=<name or IP address of the VDAS server in CentricStor >
DAS_CLIENT=<name of the client in the configuration>
●
8.3.7.3
Details about the possible causes of connection problems with VDAS and other troubleshooting advice is given in section “Possible problems and solutions” on page 367.
ACS interface
In order to enable ACS control, the ACS media agent must first be installed on the client.
Details about the possible causes of connection problems with VACS and troubleshooting
advice is given in section “Possible problems and troubleshooting advice” on page 372.
8.3.7.4
Autolabeling
When Autolabeling is enabled for an LVG, the following error message is entered in the Data
Protector file debug.log:
ValidateOBMediumHeader: -ERROR (Tape7:0:1:7C): header is not an OmniBack
header.
This problem is avoided if Autolabeling is disabled for the LVG. To do this, the Auto Labelling
attribute in the GXCC configuration function Logical Volume Groups must be set to the default
value DISABLED.
8.3.8.1
Windows NT 4.0
●
be used.
●
When using the DAS interface:
a) Copy aci.dll, winrpc.dll or winrpc32.dll and ezrpcw32.dll to
\winnt\system32 and <OMINBACK_HOME>\bin.
b) Run Portinst to install Portmapper.
c) Restart.
298
Data Protector
d) Under SERVICES, see if Portmapper and RPC services are running.
●
The system drivers are not used. The drivers must be deactivated as follows:
Under Start ➟ Properties ➟ System Control select the Tape Drives option. The individual
drives can be deactivated here by right clicking.
●
The values for adapters, bus, ID etc.can be found at
Start ➟ Properties ➟ System control ➟ SCSI adapter ➟ <FC adapter> ➟ BUSx
➟ <device emulation> under Properties/Settings.
●
If you are using Data Protector 3.5, use the patch win_0017 (from the Data Protector
CD).
●
Data Protector/NT settings:
media type
T3480
Device Nodes
SCSI*:*:*:*C
Tape*:*:*:*C (from version 4.1)
StorageTek ACS Library
GRAU DAS Library
drive emulation
FSC/CentricStor
Device nodes: SCSI<Adapter>:<Bus>:<ID>:<LUN>[C|N]
C=compressed, N=nonrewinding
8.3.8.2
Windows 2000
●
●
When using the DAS interface, copy:
aci.dll, winrpc.dll or winrpc32.dll to \winnt\system32 and
<OMINBACK_HOME>\bin.
●
Run Portinst to install Portmapper.
●
Restart.
●
Under SERVICES, see if Portmapper and RPC services are running.
●
The system drivers are not used and they must be deactivated.
Under Start ➟ System control, select the System option. In the menu which appears, select
the Hardware tab. Then open the device manager. Next, deactivate the relevant drives
by right clicking in the device manager under the tape drive option.
299
Data Protector
●
You will need to transmit the values for Adapter, Bus, ID etc. To obtain this information
for the SCSI adapter, use
Workstation <right mouse button> Manager ➟ Device Manager SCSI + RAID controller ➟
<FC Adapter> (double click). For the BUS, ID and LUN, use Tape Drive ➟ LW
(double click).
●
If you are using Data Protector 3.5, use the patch win_0017 (from the Data Protector
CD).
●
Data Protector/Windows settings:
media type
T3480
Device nodes
SCSI*:*:*:*C
Tape*:*:*:*C (from version 4.1)
GRAU DAS Library
drive emulation
FSC/CentricStor
Device nodes: SCSI<Adapter>:<Bus>:<ID>:<LUN>[C|N]
C=compressed, N=nonrewinding
8.3.8.3
Reliant UNIX
●
Not currently released.
●
CentricStor is only supported as a media agent without robot control.
●
Data Protector/RelUNIX settings:
media type
Device Nodes
drive emulation
300
FSC/CentricStor
8.3.8.4
8.3.8.5
Data Protector
Solaris
●
The system is supported as a media agent and server (3.51) with ACSLS robot control.
●
The patches PHSS_24428 and PHSS_24430 from Data Protector were used.
The patch can be downloaded from http://www.openview.hp.com.
●
The variable shminfo_shmax must be increased (see description from Solaris)
●
In the file /kernel/drv/st.conf the variable must be changed as follows:
centrs = 1,0x21,0,0x18a19,1,0x00,0;
●
When using the ACS interface, the ssi daemon must be started from
<Data_Protector_Home>/acs/ssi as follows:
./ssi.sh start <Name or IP address of the VACS server>
●
Data Protector/Solaris settings:
media type
T3480
Device nodes
/dev/rmt/*cb
drive emulation
FSC/CentricStor
HP-UX
●
Patch PHSS_24659 from Data Protector is required. The patch can be downloaded
from http://www.openview.hp.com.
●
When using the DAS interface the shared library libaci.sl from the ADIC DAS
package must be copied to <Data_Protector_Home>/lib. On a 64-bit machine,
there can be problems with a 64-bit lib from ADIC.
You can check if the lib is correct using these commands:
cd /opt/omni/lbin
./bma –version
If there is an error message, the 32-bit lib should be used.
●
When using the ACS interface, the ssi daemon must be started from
<Data_Protector_Home>/acs/ssi as follows:
./ssi.sh start <Name or IP address of the VACS server>
301
Data Protector
●
Data Protector/HP-UX settings:
media type
T3480
Device nodes
/dev/rmt/c*t*d*BEST
or1
/dev/rmt/c*t*d*BESTn (n for non rewind)
GRAU DAS Library
STL interface lib
libaci.sl
drive emulation
FSC/CentricStor or Mammoth2
1
8.3.8.6
8.3.8.7
Depending on the software: There is application software which works with non-rewind nodes. Other software requires rewind nodes.
IBM-AIX
●
CentricStor is only supported as a media agent.
●
The only node which is compressed is 3590-E. However, this drive is only supported by
the DAS robot controller. Thus there is no edition with ACS robot control.
●
Data Protector/AIX settings:
media type
3590
Device nodes
/dev/rmt*
GRAU DAS Library
STL interface lib
libaci.a
drive emulation
3590E1A
Linux
The system is only supported as a client.
302
Tivoli / TSM
8.4 Tivoli / TSM
8.4.1 Documentation
The documentation is shipped on CD together with the product. It includes the following
manuals:
Manual
Version / Release
Tivoli Storage Manager for Windows
Quick Start
as of Version 4/Release 2,
June 2001
Administrator's Guide
June 2001
Administrator's Reference
June 2001
Tivoli Storage Manager
Messages
June 2001
You can obtain this documentation from the following Internet links:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
TSM 5.3:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp?topic=/com.ibm.itsmaixn.doc/an
rai53.htm
8.4.2 Installation and configuration
8.4.2.1
TSM installation
At least version 4.2.1.7 is required. With version 4.2.0, errors occur when defining drives.
The following packages are to be read in (example for Solaris, other platforms are similar):
TSM4217S_Sun.tar.Z TSM server
IP22372.tar.Z TSM client
All packages are unpacked with uncompress and then extracted with
tar -xvf <name of file>. Then the packages are all installed with
pkgadd -d /<full path>/<name of the package> .
The software is installed by default in the directory: /opt/tivoli/tsm
303
Tivoli / TSM
8.4.2.2
TSM configuration
The complete configuration was set with the help of command line tools. This is because it
is not possible to configure an individual drive on the graphical interface since you cannot
specify the device file of the drive there.
Complete configuration via the Web interface is possible in Version 5 and higher.
All pathnames are relative to the TSM main path.
●
Start from rc.acs_ssi from the <TSM>/devices/bin directory
●
Start of the server with ./dsmserv quiet & from the directory
<TSM>/server/bin
●
Start the administrative console with ./dsmadmc from the directory
<TSM>/client/admin/bin
The user and password in the default installation are:
Login:
User:
admin
admin
All of the following commands are given on the administrative console.
Define the Library
DEFINE LIBRARY <name of library> LIBTYPE=ACSLS ACSID=1
Define a drive
DEFINE DRIVE <name of library> <name of drive> DEVICE=<device file>
ACSDRVID=<ACS drive ID>
A tape must be inserted in the drive.
The following definition has been added from Version V5:
DEFINE PATH <server name> <drive name> SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=<name of library> DEVICE=<device file>
Define device class:
You can look at the defined drive with QUERY DRIVE and find out which device class is
to be created.
304
Tivoli / TSM
In Solaris, this is the GENERICTAPE class in AIX 3590. The device classes are then
created as follows:
●
For GENERICTAPE:
DEFINE DEVCLASS <name of device class>
LIBRARY=<name of library>
DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M
MOUNTRETENTION=60
MOUNTWAIT=60
MOUNTLIMIT=DRIVES
●
For 3590:
DEFINE DEVCLASS <name of device class>
LIBRARY=<name of library>
DEVTYPE=3590
FORMAT=DRIVE
ESTCAPACITY=900M
PREFIX=<prefix of volume in use>
MOUNTRETENTION=60
MOUNTWAIT=60
MOUNTLIMIT=DRIVES
●
Define a storage pool:
DEFINE STGPOOL <name of pool> <name of device class>
MAXSCRATCH=<number of scratch tapes in pool>
●
Change for backup
UPDATE COPYGROUP standard standard standard TYPE=archive DESTINATION=<name of pool>
●
Change for archive
UPDATE COPYGROUP standard standard standard TYPE=backup DESTINATION=<name of pool>
●
Change the management class
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=<name
of pool>
●
Subsequent activation
ACTIVATE POLICYSET standard standard
●
Label and check in volumes
LABEL LIBVOLUME <name of library> SEARCH=yes
VOLRANGE=<first volume> ,<last volume>
CHECKIN=private OVERWRITE=yes
305
Tivoli / TSM
●
Add to storage pool
DEFINE VOLUME <name of pool> <name of volume>
●
Activate web console
To activate the web console, you must modify the file dsmserv.opt from the
<TSM>/server/bin directory before starting the server. If this file is not present, it
can be created by copying the standard file dsmserv.opt.smp from the same
directory.
The following entries must be activated in this file:
COMMmethod HTTP
HTTPport 1580
Then you can reach the console from any web browser at the following address:
http://<IP address of the TSM server>:1580
8.4.2.3
Special parameters
In the file dsmserv.opt the parameter ACSTIMEOUTX should be set to 5 (i.e. a maximum
wait time of 50 minutes for ACS library access).
8.4.2.4
Examples
Configuration
DEFINE LIBRARY CentricStor LIBTYPE=ACSLS ACSID=1
DEFINE DRIVE CentricStor V20C DEVICE=/dev/rmt1cn ACSDRVID=1,0,0,12
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M MOUNTRETENTION=60 MOUNTWAIT=60 MOUNTLIMIT=DRIVES
DEFINE STGPOOL CentricPool CentricTape MAXSCRATCH=0
UPDATE COPYGROUP standard standard standard TYPE=archive
DESTINATION=CentricPool
UPDATE COPYGROUP standard standard standard TYPE=backup
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=CentricPool
Handling the volume
LABEL LIBVOLUME CentricStor SEARCH=yes VOLRANGE=TIV01,
TIV20 CHECKIN=private, OVERWRITE=yes
DEFINE VOLUME CentricPool TIV01
... to
DEFINE VOLUME CentricPool TIV20
306
Tivoli / TSM
Backup of a directory
Starting from dsmc:
ARCHIVE /home/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
Restore of a directory
Starting from dsmc:
RETRIEVE /home/ /tmp/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
8.4.3 Installation and configuration with Gresham EDT
This software package makes it possible to control ACSLS controlled robots via Gresham
EDT with the External Library Manager Function. This function must be used in configuration
with HP-UX, as TSM does not support any ACSLS libraries in HP-UX.
For further information on the software see:
http://www.gresham-software.com
See product: EDT-DistribuTAPE™
8.4.3.1
Gresham installation
Version 6.2.1.0 has been tested by FSC.
The following package is played in:
edt.6210.hpux.tar.gz Gresham DistribuTape
The package was unpacked with gunzip and then extracted with
tar -xvf edt.6210.hpux.tar. Then the unpacked
OMIdtelm.6210.depot was installed with
swinstall -s /<full path>/OMIdtelm.6210.depot.
The software is installed by default in the directory: /opt/OMIdtelm
307
Tivoli / TSM
8.4.3.2
TSM installation
Version 4.2.1.7 has been tested by FSC.
The following packages are read in:
TSM4217SRV_HPUX.tar TSM server
IP22368.tar TSM client
All packages are unpacked with gunzip and then extracted with tar -xvf <name of
file>. Then the server is installed with
swinstall -s /<full path>/<name of package>
and the client with
swinstall -x mount_all_filesystems=false -v -s `pwd`/TIVsmC TIVsm
The software is installed by default in the directory:
/opt/tivoli/tsm
8.4.3.3
Gresham configuration
Start the SSI agent
First the rc.edt script from the <installations path>/bin
directory must be edited; you can create it by copying from rc.edt.smp.
In this file the variable MEDIA_MNGR_HOST must also be changed.
You should enter the IP address or (with working name resolution) the machine name of the
VLP, on which the ACSLS emulation is running (see section “IP addresses and host names”
on page 362 and section “Virtual libraries” on page 363).
Then start the script with the parameter both. This starts the SSI process, and simultaneously initializes DistribuTape.
308
Tivoli / TSM
Set up a storage pool and add tapes on the VLP.
You log in to the VLP and start the program cmd_proc which can be used to configure the
emulation of the ACSLS connection.
You then create a pool using:
define pool <Low Water Mark> <High Water Mark> <Pool ID>
Watermarks and pool IDs:
Low Water Mark
Lowest number of available volumes which must be in the pool;
should be set to 0.
High Water Mark
Maximum number of available volumes in the pool; can be as
high as you wish, e.g. 10000.
Pool ID
A number given by you, from 1 to 65534.
All further commands can then be carried out again on the computer on which Gresham
DistribuTape was installed. However, it is also possible to continue working on the VLP with
cmd_proc.
You can now add volumes to the pool with the command set_scratch:
set_scratch -p <pool ID> -a <first volume> -b <last volume>
or
set scratch <PoolID> <first volume>-<last volume>
You can then see if everything is correctly configured using the query
q_pool -p <pool ID>.
Configuration of a library in Gresham DistribuTape
The complete configuration of a library is carried out using the configuration file elm.conf,
which is found under <installation path>/bin.
If it does not exist, you can copy the example file elm.conf.smp to elm.conf .
Example configuration, including explanation of the most important elements:
LICENSE PERM <license key>
LIBRARY <library name>
POOL <pool ID>
DRIVE <device file> ACS_<ACS drive ID>
END
309
Tivoli / TSM
Configuration with Gresham DistribuTape:
License key
License key, shipped by Gresham together with the product at purchase.
Library name A name you choose which must agree with the library defined later in TSM.
In order to be recognized by TSM, this must be written in block capitals.
8.4.3.4
Pool ID
Must agree with the Pool ID set by cmd_proc.
Device file
Full path for the device file of the drive. The following devices are used in
HP: /dev/rmt/*m.
ACS drive ID
Drive ID with which the drive is recognized in the library, e.g. 0,0,0,0.
TSM configuration
The complete configuration was made using the command line tools. All pathnames are
relative to the TSM main path.
●
Start the server with ./dsmserv & from the directory <TSM>/server/bin
●
Start the administrative console with ./dsmadmc from the directory
<TSM>/client/admin/bin
The user and password in the default installation are
Login:
User:
admin
admin
All of the following commands are given on the administrative console.
Defining the Library
DEFINE LIBRARY <name of library> LIBTYPE=external
EXTERNALManager=/<Gresham installation path>/bin/elm
Defining a device class
DEFINE DEVCLASS <name of device class> LIBRARY=<name of library>
DEVTYPE=GENERICTAPE ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60
MOUNTLIMIT=<number of drives defined in DistribuTape>
Defining a storage pool
DEFINE STGPOOL <name of pool> <name of device class>
MAXSCRATCH=<number of scratch tapes in pool>
Changing and activating policy
UPDATE COPYGROUP standard standard standard DESTINATION=<name of
pool>
Change for backup
UPDATE COPYGROUP standard standard standard TYPE=archive DESTINATION=<name of pool>
310
Tivoli / TSM
Change for archive
UPDATE COPYGROUP standard standard standard TYPE=backup DESTINATION=<name of pool>
Changing the management class
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=<name of
pool>
Subsequent activation
Activate web console
To activate the web console, you must modify the file dsmserv.opt from the
<TSM>/server/bin directory before starting the server. If this file is not present, it can
be created by copying the standard file dsmserv.opt.smp from the same directory.
The following entries must be activated in this file:
COMMmethod HTTP
HTTPport 1580
You can then reach the console from any web browser at the following address:
http://<IP address of the TSM server>:1580
8.4.3.5
Examples
Configuration for Gresham DistribuTape
Making the scratch pool
Log in on the VLP, start from cmd_proc
Enter: define pool 0 10000 100
Add tapes to scratch pool set_scratch -p 100 -a TSMG00 -b TSMG09
Contents of /opt/OMIdtelm/bin/elm.conf:
LICENSE PERM 1444291050
LIBRARY CENTRICSTOR
POOL 100
MSG MDRVSTAT MDRVERR MPOOLSTAT /opt/OMIdtelm/bin/msg.out
DIAG ESUB EDRV ECNV EELM /opt/OMIdtelm/bin/dbg.out
DRIVE /dev/rmt/36m ACS_2,0,0,4
END
Configuration check
elm_testlibdesc -l CENTRICSTOR
311
Tivoli / TSM
Configuration for TSM
DEFINE LIBRARY CentricStor LIBTYPE=external
EXTERNALManager=/opt/OMIdtelm/bin/elm
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=4
DEFINE STGPOOL CentricPool CentricTape MAXSCRATCH=10
UPDATE COPYGROUP standard standard standard DESTINATION=CentricPool
UPDATE COPYGROUP standard standard standard TYPE=archive
UPDATE COPYGROUP standard standard standard TYPE=backup
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=CentricPool
Backup of a directory
Starting from dsmc:
ARCHIVE /home/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
Restore a directory
Starting from dsmc:
RETRIEVE /home/ /tmp/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
8.4.4 Configuring a SCSI library on AIX via VJUK
8.4.4.1
General
The VJUK emulation is supported as of CentricStor Version V3.0.
The term element number in the SCSI library corresponds to the term slot number in VJUK.
The device nodes in AIX must have the same slot or element numbers in the TIVOLI-SCSI
library as the virtual drives in the associated VJUK emulation of CentricStor.
The VJUK administration tool vjukadmin can be used, among other things, to create an
inventory of the slots or drives, to unload volumes from the drives, and to transfer them
again to the slots.
Access to VJUK with vjukadmin is only possible in the offline status. vjukadmin permits
switching between offline and online. A host can only access the VJUK in online status.
312
8.4.4.2
Tivoli / TSM
Configuration steps
1. CentricStor configuration
Library type / max. number of slots: ADIC/Scalar-10K 16000
Use of LUN 0 as robotics, emulation IBM 03590E1A for virtual drives
Creating the assignment list of the virtual drives and associated slot numbers in
CentricStor:
# vjukadmin VJ00 inventory drives
vjukadmin VJ00 inventory drives
INQUIRY-DATA:
SLOT
DRIVE
VSN
0100
V001
0101
V002
0102
V003
0103
V004
0104
V005
0105
V006
0106
V007
-
i
The slot number is output in hexadecimal format. The element address must be
specified in decimal format for the TSM.
2. Creating the device nodes via smit in AIX
smit -> Devices -> Tivoli Storage Manager Devices
-> Fibre Channel SAN Attached Devices
-> Discover Devices Supported by TSM
-> Parent FC Adapter.
The robotics are assigned the device names lb0, lb1, etc., the devices the names mt0,
mt1, etc.
Device node names for robotics: /dev/lb0, …
Checking the WWN of the robotics:
# lsattr -El lb0
FCPORT_ID 0x31a00
LUNMAP_ID 0x0
WW_NAME
0x10000000c937fa42
PRODUCT_ID Scalar 10K
FC Port ID
Mapped LUN ID of the device
WW Name of the Port
Product ID of the device
True
True
False
False
Generating the device node names via the Atape driver:
cfgmgr
313
Tivoli / TSM
i
The following cfgmgr message can be ignored:
" cfgmgr: 0514-621 WARNING: The following device packages are
required for device support but are not currently installed.
devices.fcp.changer "
No functional restriction has been observed.
The device nodes /dev/mt0, … created by TSM are not to be used for the tape drives
but those created by cfgmgr via the Atape driver: /dev/rmt0, …
Checking the attributes of a device node in AIX:
# lsattr -El rmt1
mode
yes
Use Buffered Write
True
block_size
0
Block Size (0=Variable Length
True
compress
yes
Use Hardware Compression on Tape
True
autoload
no
Use Autoloading Feature at End-of-Tape
True
logging
no
Activate volume information loggingTrue
True
max_log_size
500
Maximum size of log file (in # of
entries)
True
space_mode
SCSI
Backward Space/Forward Space Record Mode
True
rew_immediate no
Use Immediate Bit in Rewind Commands
True
trailer_labels no
Trailer Label Processing
True
retain_reserve no
Retain Reservation
False
emulate_auto
no
Use Random Mode to Emulate Autoloader
Tape Drive True
limit_readerp no
Limit Read Error Recovery Time to 5
Seconds
True
fail_degraded no
Fail Tape Operation if Degraded Media is
Detected True
devtype
03590E1A
Device Type
False
mtdevice
Library Device Number
True
scsi_id
0x31a00
SCSI Target ID
True
lun_id
0x2000000000000
Logical Unit Number
True
314
Tivoli / TSM
location
Location
True
ww_name
0x10000000c937fa42 World Wide Port Name
False
drive_port
0
Drive Port Number
False
new_name
New Logical Name
True
dev_status
N/A
False
node_name
World Wide Node Name
False
alt_pathing
no
Enable Alternate Pathing Support
True
primary_device rmt1
Primary Logical Device
False
In addition to the WWN and LUN, the drive’s port ID is also specified under scsi_id.
3. Configuration of a non-shared library in the Tivoli Storage Manager V5.1.5
Example
define library aix-vj00 libtype=scsi
define path aix AIX-VJ00 srctype=server desttype=library device=/dev/lb0
define drive aix-vj00 rmt0 element=256
…
define path aix rmt0
device=/dev/rmt0.1
device=/dev/rmt1.1
device=/dev/rmt2.1
…
srctype=server desttype=drive library=aix-vj00
Special features for the Tivoli Storage Manager
Checking volumes with labels into a library:
label libvolume aix-vj00 search=yes volrange=X00000,X00999
labelsource=barcode checkin=scratch overwrite=yes
Checking a volume with an existing label into the library:
checkin libvolume aix-vj00 X00000 status=scratch checklabel=barcode
checkout libvolume aix-vj00 X00000 remove=no checklabel=no
315
Tivoli / TSM
The checkout is to take place with remove=no. If remove=yes the TSM would
attempt to transfer the volume into the VJUK’s I/O slot.
To harmonize the directories between the TSM administration and VJUK:
audit library aix-vj00 checklabel=barcode
or
audit library aix-vj00 checklabel=yes
If checklabel=yes each volume is mounted and the label read by TSM. With
CentricStor this means that a volume which was migrated to a real tape must be read
into the cache again!
When checklabel=barcode the data inventory of VJUK and TSM is harmonized.
This operation lasts only a few minutes, even with 16,000 slots, for example.
audit library checklabel=barcode is recommended if TSM finds volumes
mounted in the last TSM run when it starts and cannot reset these, or if an audit library
is recommended by TSM.
If the TSM drives are not emptied by audit volume either, this must be performed using
vjukadmin unload and vjukadmin unmount.
i
8.4.4.3
CAUTION!
audit library with checklabel=yes causes problems with drives which still
contain volumes from the last TSM. TSM wants to load another volume in what
it regards as an empty drive and then aborts the audit function.
Modifying the VJUK configuration and notifying TSM
●
Modifying the VJUK’s robotics connection (TSM must be terminated to permit this):
The device node, e.g. /dev/lb0, must be removed in AIX and created again:
–
–
●
Remove with smit or with rmdev -l lb0 -d
Create again with smit
Modifying the number of slots:
It is sufficient to restart TSM.
316
Tivoli / TSM
8.4.5 LANfree configuration without Gresham
8.4.5.1
Prerequisites
Software
TSM Server + Agents + Client
Version: 5.3.2.0
Emulation in CentricStor
IBM 3590
Library Emulation
VACS or VJUK (not as powerful)
Driver on the host systems
IBMtape driver
TSM server
AIX 5.2, IBMtape, Atape driver Version 9.2.6.0
Drivers
TSM server
AIX 5.2
IBMtape, Atape driver Version 9.2.6.0
Storage agents
8.4.5.2
SOLARIS V8
IBM Tape & Medium Changer Device Driver
4.1.2.6
HP-UX 11i V1 (64-Bit)
atdd 3.5.0.29
W2K3 SP1
IBMtape 6.0.8.2
LINUX SLES 9 SP2
IBMtape-2.1.1-2.6.5-7.191.i386.rpm.bin
Installation
The TSM server and client are installed on the AIX server using the System Management
Interface Tool (SMIT).
The rpm packages TIVsm-stagent, TIVsm-tsmscsi, TIVsm-BA and TIVsm-API are installed
on the Linux system.
317
Tivoli / TSM
8.4.5.3
Configuration
Generating the device files
The /dev/rmt devices are generated on the AIX server using cfgmgr. The device file for
the robot is generated with SMIT. To do this, select the following in SMIT:
Devices
->Tivoli Storage Manager Devices
-> FibreChannel SAN Attached Devices
-> Discover Devices Supported by TSM
-> ...
The device file generated is called /dev/lbX, für X = 0..n.
On the Linux client the device files are generated automatically by the IBMtaped daemon in
the case of the IBMtape installation as of Version 1.3.. They are called /dev/IBMtapeX and
/dev/IBMtapeXn ( X = 0..n ), only the first one being used for configuration here.
Device node with IBMTape driver under Solaris:
/dev/rmt/130stcbn
../../devices/pci@17,2000/fibre-channel@1/IBMtape@3a,21:stcbn
HPUX
crw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rw-
1
1
1
1
bin
bin
bin
bin
bin
bin
bin
bin
205
205
205
205
0x1b0000
0x1b0080
0x1b0040
0x1b00c0
Jan
Jan
Jan
Jan
12
12
12
12
17:27
17:27
17:27
17:27
/dev/rmt/c27t0d0BEST
/dev/rmt/c27t0d0BESTn
/dev/rmt/c27t0d0BESTnb
ioscan -fnkC tape bringt:
# ioscan -fnkC tape
Class
I H/W Path
Driver S/W State
H/W Type
Description
========================================================================
tape
0 0/0/1/0.3.0
stape CLAIMED
DEVICE
HP
C1537A
/dev/rmt/0m
/dev/rmt/c0t3d0BESTn
/dev/rmt/0mb
/dev/rmt/c0t3d0BESTnb
/dev/rmt/0mn
/dev/rmt/c0t3d0DDS
/dev/rmt/0mnb
/dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST
/dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0DDSnb
tape
133 0/4/0/0.2.6.255.0.0.0
stape CLAIMED
DEVICE
STK
T9840B
318
Tivoli / TSM
Configuration of the Linux client
The default directory of the Linux client is /opt/tivoli/tsm/client/ba/bin.
1. The freely selectable name of the server is entered in the dsm.opt file:
servername tsm
2. The following entries are made in the dsm.sys file:
SErvername tsm
COMMMethod
TCPPort
TCPServeraddress
enablelanfree
LANFREECommmethod
LANFREETCPPort
TCPip
1502
<IP address/Name>
yes
TCPIP
1500
1502 is specified as TCPPort here. The default TCPPort is 1500. The value may
possibly have to be modified in the dsmserv.opt server file. The values are basically
freely selectable (1024 through 32767).
Configuration of the Linux Storage Agent
The default directory of the Storage Agent is /opt/tivoli/tsm/StorageAgent/bin.
First the configuration file of the Storage Agent, dsmsta.opt, is edited and the following
entry is made:
DEVCONFIG devconfig.txt
The Storage Agent writes device configuration data into the file specified here. This is
generated with the following command (in one line):
Ê
dsmsta setstorageserver myname=csagnt mypassword=xxxxx \
myhladdress=<IPAdresse des StAgent> \
servername=tsm serverpassword=yyyyy \
hladdress=<IPAdresse des TSM Servers> lladdress=1502
The TCP server address specified under hladdress must be the same as that specified in
the dsm.sys file (see above). This command also writes the following line into the
dsmsta.opt file:
SERVERNAME tsm
The Storage Agent can be started either in the background using the script
Ê
dsmsta.rc [ start | stop | restart | status ]
or in the foreground with the command
Ê
dsmsta
319
Tivoli / TSM
Configuration of the TSM server
First the following commands are issued on the server administration console dsmadmc:
Ê
set servername tsm
Ê
set serverpassword xxxxxx
Ê
set serverhladdress <IP address/Name of the TSM server>
Ê
set serverlladdress 1502
Ê
set crossdefine on
For each client for which data transfer via the SAN is envisaged the Storage Agent is
defined as if it were a server (one line!):
Ê
define server csagnt serverpassword=xxxxx hladdress=<IP addr./Name of
Storage Agent> lladdress=1500 [validateprotocol=all]
Here the name and password must be the same as those which were used in defining the
Storage Agent on the client. lladdress designates the LANfree data port.
Configuration of the SAN environment
i
In the documentation the configuration is described slightly differently.
The administration console can also be used to define the library, the drives, the device
class and the storage pool, e.g.:
Ê
define library centricstor libtype=acsls shared=yes
(or for VJUK: define library centricstor libtype=scsi shared=yes)
Ê
define path tsm centricstor srctype=server desttype=library device=/dev/lb0
Ê
define drive centricstor drive0 element=256
Ê
define path tsm drive0 srctype=server desttype=drive library=centricstor \
device=/dev/rmt0
Ê
define path csagnt drive0 srctype=server desttype=drive \
library=centricstor device=/dev/IBMtape0
... further drives and paths ...
320
Ê
define devclass centrictape library=centricstor devtype=3590 format=drive \
estcapacity=900M mountretention=0 mountwait=1 mountlimit=drives
Ê
define stgpool centricpool centrictape maxscratch=100
Ê
define domain cs_domain
Tivoli / TSM
Ê
define policyset cs_domain cs_policy
Ê
define mgmtclass cs_domain cs_policy cs_defmgt
Ê
assign defmgmtclass cs_domain cs_policy cs_defmgt
Ê
define copygroup cs_domain cs_policy cs_defmgt type=backup \
destination=centricpool
Ê
define copygroup cs_domain cs_policy cs_defmgt type=archive \
destination=centricpool
Ê
activate policyset
Ê
[register|update] node <NodeName> <Password> domain=cs_domain
cs_domain cs_policy
321
Tivoli / TSM
8.4.5.4
Verification of LANfree data transfer
For this purpose the Storage Agent is started in the foreground as described above. The
administration console dsmadmc is used on the server. A backup is now made on the client.
On both consoles - Storage Agent and server - the data transfer can be observed by issuing
the following command several times:
Ê
query session
In this case the number of bytes received (Bytes Recvd) on the Storage Agent should be
incremented up to the full size of the backup, while on the server it should only be possible
to see the considerably smaller number of bytes for metadata.
If the backup is excuted with the command line program dsmc, e.g.:
Ê
dsmc archive /ein/directory/*
a summary of the backup is displayed on the console after it has been completed. Information on the LANfree data should be visible there, for example:
Total number of objects inspected:
374
Total number of objects archived:
374
Total number of objects updated:
0
Total number of objects rebound:
0
Total number of objects deleted:
0
Total number of objects expired:
0
Total number of objects failed:
0
Total number of bytes transferred:
22.84 MB
LanFree data bytes:
22.83 MB
<<<<<<<<<<<====================
Data transfer time:
12.82 sec
Network data transfer rate:
1,824.59 KB/sec
Aggregate data transfer rate:
348.14 KB/sec
Objects compressed by:
0%
Elapsed processing time:
00:01:07
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.0
Client date/time: 04/26/05
19:12:25
(c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights
Reserved.
322
8.4.5.5
Tivoli / TSM
General information
●
HP-UX + LINUX can only use ACSLS from TSM 5.3.2.0.
●
TSM uses the record length of 256 KB for all the platforms mentioned.
●
A drive is reserved alternately by the server and the agent in SCSI style for tape I/O.
Here it must be ensured that SHARED=YES and RESETDrives=YES are set.
●
8.4.5.6
If an agent crashes during reservation it is not always recovered automatically upon
booting. In CentricStor the reservation of a drive for a host can be canceled by
stopping/starting the emulation.
References
All processes described here were taken from the TSM documentation. This is available in
HTML or PDF format at the following URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp
8.4.6 Miscellaneous and restrictions
●
The volumes must be alphanumeric.
●
Tivoli/TSM does not currently support any DAS robot interfaces. Version 5 may provide
this support.
●
TSM or TSM Label only includes restricted support for drive positioning:
acs(1), lsm(0-23), panel(0-19), drive(0-19)
●
TSM Server Trace for drive problems with tape robots
trace dis *
trace enable pvr mms systime
trace begin /tmp/trace.out
> Aktion …..
trace flush
trace end
trace dis *
323
Tivoli / TSM
8.4.7.1
Windows NT 4.0
not yet released
8.4.7.2
Windows 2000
If you are using the ACSLS interface, you must use the LibAttach2 software by
StorageTek. You can use the product for Windows NT 4.0.
Configuration:
media type
Mammoth2
Device nodes
8.4.7.3
LIBTYPE
ACSLS
EXABYTE/Mammoth2
Reliant UNIX
TSM does not support Reliant UNIX.
8.4.7.4
Solaris
Only ACSID=1 is supported.
i
For the audit library, in dsmserv.opt change the parameter ACSTIMEOUTX
from
the default setting 1 (=10 minutes) to the setting 4 (=40 minutes).
Some drives will only be ready for use again after UPDATE DRIVE ONLINE=NO/YES.
DEFINE DRIVE last approximately 1 minute.
Configuration:
324
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/*cn
drive emulation
FSC/CentricStor
8.4.7.5
Tivoli / TSM
HP-UX
The ACSLS controller can only be addressed via Gresham EDT.
Configuration:
8.4.7.6
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/cXtXdXBEST
drive emulation
FSC/CentricStor
IBM-AIX
Configuration:
8.4.7.7
DEVTYPE
3590
LIBTYPE
ACSLS
Device nodes
/dev/rmt*
drive emulation
3590E1A
Linux
TSM does not support Linux.
325
8.5 BrightStor ARCserve Backup
8.5.1 ARCserve
The initial release for operation with CentricStor has taken place for:
●
ARCserve r11.1 for Windows
●
ARCserve r11 for Windows
●
ARCserve r11.1 for Linux
The following ARCserve versions can also be operated with CentricStor:
●
CA ARCserve Backup r11.5
●
CA ARCserve Backup r12
8.5.2 CentricStor
A prerequisite for operation with ARCserve is at least Version 3.0 as of K834.1. Only
CentricStor V3.0 offers the VJUK interface and fixed block mode, both of which are used by
ARCserve.
Every device type which can be selected in the GXCC ➟ Configuration ➟ Virtual Library
Services menu under VJUK using the Inquiry button can be used as a virtual library:
●
ADIC/Scalar-1000
●
ADIC/Scalar-10K
●
FSC/CS-TL (CentricStor native)
The Logical Drives can be assigned the following device names in the GXCC ➟ Configuration
➟ Logical Drives menu under Emu/Inquiry Data:
326
●
EXABYTE/Mammoth2
●
FSC/CentricStor (CentricStor native)
●
IBM/IBM3590E1A
●
IBM/LTO3
The restriction on the number of continuation tapes which can be processed by ARCserve
must be taken into account when configuring the Logical Volume Size in the GXCC ➟
Configuration ➟ Logical Volume Groups menu (LV size button):
●
ARCserve r11.5:
25 LVs
●
ARCserve r12:
101 LVs
With ARCserve r11.5 an LV size of, for example, 2 GB would enable only 50 GB to be saved
per backup job. Consequently it may be necessary to adjust the LV size to the data volumeof
a backup job here.
327
8.5.3 Backup server
The backup server on which ARCserve runs is connected to CentricStor via FC. A controller
which has been released for the Primergy and the CentricStor connection and has the
appropriate driver must be used for this purpose. When the Storport Miniport Driver is used
with any Emulex HBA the default settings are suitable, which means that configuration is
not required. Otherwise the controller and driver parameters must be set appropriately for
the connection of a tape library.
In tests good results were achieved under Windows 2003 with an LP9002 with 3.90a7
firmware and 2.21.a7 driver and the following parameter settings:
328
329
8.5.4 Further information
After the hardware and software have been installed, the following steps are recommended
for startup and configuration:
Configure the virtual library on CentricStor and check the LUNs assigned with the aid of
GXCC. The tape drives are assigned their LUNs automatically, starting with 0. The VJUK
LUN must be configured in the GXCC under Virtual Library Services, and it makes sense to
use the next free LUN after the tape drives. Windows and ARCserve have no problems if
there are gaps in the LUNs, however.
●
When an Emulex controller is used the aforementioned parameters are set with
”elxcfg”, and HBAnywhere is used to check whether the controller has recognized all the
CentricStor LUNs.
●
In the next step the operating system must recognize all the devices. Under Windows
this is done in the Device Manager. No Windows drivers are required for the jukebox or
tape drives; ARCserve handles hardware control itself.
●
Only when these hurdles have been taken can ARCserve device configuration be
started. Here the tape drives are assigned to their jukebox.
It is advisable to use the Eject Media after Backup option in ARCserve (Device Configuration ➟ Library Properties or Global Job Options ➟ Operations). This ensures that an
Unmount/Eject is automatically performed at the end of a backup job, thus ejecting the
cartridge used from the virtual drive. Without this option ARCserve leaves the cartridge
in the drive in order to have it available more quickly for reuse.
●
Starting the ARCserve manager and calling the Device Window. The virtual jukebox
with its drives and slots now appears here. After an initial inventory the backup server
is ready to operate.
Information on import / export
With real hardware the Import or Export function under ARCserve is used to address the
mailslot of a jukebox in order to import or export cartridges without opening the jukebox and
thus forcing a complete, time-consuming inventory. This function is also supported in
CentricStor; the Scalar 1000 contains 12 virtual Mailslots.
These mailsolts can be addressed from ARCserve, i.e. cartridges can be exported there
from the magazine and also be reimported into the magazine. However, since these virtual
mailslots with their virtual cartridges do not really exist, this function can only be used to
resort cartridges in the jukebox.
330
Time Navigator
8.6 Time Navigator
8.6.1 General
The Time Navigator is only released for Windows 2000 in the context of a customer project.
It was tested using Time Navigator V3.7. A mixed configuration with Mammoth2 and 3590
has been tested successfully. TINA is able to manage various pools with different drives.
8.6.2 Configuration
Configuring Magstar 3590E in Windows:
Definition of the drives in TINA:
Further settings must then be made in TINA for the virtual drives.
Select the drive type and edit it.
331
Time Navigator
Main screen for editing the drive type:
The Cartridge Life Cycle must be set to Maximum. 5,000,000 is a virtually unachievable value.
Information tab:
332
Time Navigator
"Cleaning management by TINA" must be disabled.
Note: No volume size need be set.
The scratch pool for VACS is defined on the VLP:
IUP0# cmd_proc
ACSSA> define pool 0 7000 3
Define: Define completed, Success.
Define: Pool 3 created.
ACSSA> set scratch 3 A00000-A05999
Set: volume A00000 in tape pool 3 is
…
i
a
a
a
a
a
scratch
scratch
scratch
scratch
scratch
volume.
volume.
volume.
volume.
volume.
TINA does not accept pool number 0.
On Windows 2000 the Libattach program must be installed.
Sample configuration:
iup0 is the ISP on which the VLP functionality runs and must be defined in the Hosts file on
the backup server .
333
Time Navigator
The Virtual Library must be selected in TINA:
Virtual Library is the correct type for ACSLS-Silos:
Enter the library name and select STK ACSLS as Library Management Software.
334
Time Navigator
After you have confirmed the configuration the following screen appears:
After you have confirmed with OK a few variables need to be set:
The coordinates of the virtual drives are set with Edit:
335
Time Navigator
You can define values manually or press "…" to have preferred items displayed. These must
be the same as the drive items defined in CentricStor .
After you have entered all the parameters the following screen is displayed:
The pool number should be the one defined in the VACS (3 here).
336
Time Navigator
After you have made these entries have the content of the library displayed and perform
reinitialization:
All the volumes (LVs) in the sepecified range are then accessible for the library.
TINA supports scatch pools. If an LV is recycled or migrated CentricStor receives the
command to truncate the LV and to perform no further restore from the volume (PV).
For this purpose the line:
TRUNCATE_CARTRIDGE="yes"
must be inserted in the file:
%TINA_HOME%/Vtl/catalog_library/vtl_config.txt
!
CAUTION:
Atempo recommends that you should only use one drive when labeling as familiar
problems will otherwise occur.
337
VJUK emulation
8.7 VJUK emulation
8.7.1 General
●
Connection of the virtual robotics VJnn and of its virtual tape devices is implemented
via an FC switch.
●
Up to 20 virtual jukeboxes VJnn are supported per CS.
●
In the GXCC configuration virtual drives the vtd line on whose LUN VJnn is configured
is displayed but is not available for tape emulation (so-called shadow device with the
disabled identifier in the configuration file). You are therefore recommended if possible
to use a LUN for the robotics which is higher than the number of virtual drives (LUNs).
Note: The FC controller always permits LUNs up to 255. Sample tests with FSC
Networker on Solaris and VJNN on LUN 220 worked.
i
AIX needs the robotics on LUN 0.
●
Windows with VJUK recognizes more than 8 LUNS if a virtual drive and not the virtual
robotics is configured on LUN 0 in CentricStor.
●
Maximum number of volume slots in VJUK:
Emulation
Maximum slots
OEM limit
FSC/CS-TL
61440
ADIC/Scalar-1000
61440
1182
ADIC/Scalar-10K
61440
22938
The slot limit of 61440 can be lower owing to the host platform/backup application.
338
●
The administration tool vjukadmin is supplied for VJUK. The slot sequence of the drives
and media which may need to be taken into consideration for configuring the backup
application is displayed using the inventory command.
●
On Windows 2003, after VJNN, the virtual drives in CentricStor and zoning on the FC
switch have been configured, the LUNS/Tapex are reentered in the registry without any
further action, i.e. also without rebooting Windows 2003, and unknown autochanger and
the tape devices (EXABYTE driver for Mammoth2 V2.10 was already present) are
recognized and made operational.
VJUK emulation
●
No robotics driver must be installed specially for the CentricStor virtual jukebox in
Windows; the original Microsoft driver is activated automatically (unknown autochanger
from the manufacturer GenChanger with driver version 5.2.3790.0, driver date 1
October 2002 on Windows 2003).
●
VDAS and VACS can mount volumes from VJUK. A collision/operating errors can be
avoided by means of correct configuration or setting up the name ranges on the backup
server.
●
As in the real world, by default VJUK offers the backup application 1 transport unit for
mounting/unmounting logical volumes in virtual drives. In the event of a mount request
(SCSI move request) for restoring the relevant virtual volume from the real tape, VJUK
must consequently wait for the restore from the real tape to be completed and is blocked
for further mount/unmount requests during this period.
●
In the real world, library control via SCSI is not designed for long delays in the case of
SCSI requests. Consequently timeout values in the single-digit minute range are
customary in drivers and application programs. In the case of a mount request which
requests the virtual volume concerned to be restored from the real tape, SCSI aborts
can be caused by both the operating system and the backup application. In order to
prevent this, prefetch scripts should be used as far as possible so that virtual volumes
are read into a cache in advance.
339
NAS filer - NetApp
8.8 NAS filer - NetApp
Miscellaneous
The distinctive feature of the configuration is that the version of NDMP used (version 3)
does not support tape cloning.
CentricStor offers an implicit cloning of tapes, so that now a copy of NDMP backups can be
made without extra burden on NetApp.
Requirements
–
–
NetApp F760 with operating system version ONTAP6.2R2 and FC controller
FC-BA X2045A (QLA2200).
NetApp connection via FC switch
Restrictions
Only the first 16 virtual drives of NetApp are recognized.
Configuration
●
CentricStor ICP
Emulation IBM 3590E
Compression by HOST
●
NetWorker 6.1A10 with EKS 1-5 for Solaris
In /nsr/res/defaults make the following entry:
NSR_DEV_BLOCK_SIZE_3590=256
The NetWorker block size for 3590 must be adapted from default 384k to 256k. This is
because the DUMP command which is implicitly called on NetApp sets 256k as the
maximum block size.
The settings for the timer are as recommended for NetWorker (section “Configuration
of the “CentricStor” library” on page 222).
Configuration of NetApp devices e.g. nrst31a (cmp, norewind) as NDMP devices.
Useful commands
340
sysconfig -av
show adapter
sysconfig –t
show tapes
reboot
reboot filer
DiskXtender for Windows
8.9 DiskXtender for Windows
DiskXtender for Windows is a software package from Legato (EMC) that saves data written
to a Windows drive which has been declared as an extended drive in a library on a changer
in accordance with specific rules.
Information on trademarks
●
DiskXtender for Windows, MediaStor and Legato are trademarks of the EMC Corporation.
●
SUN is a registered trademark of the Sun Microsystems, Inc.
●
EMULEX is a registered trademark of the EMULEX Corporation.
●
CentricStor is a trademark of Fujitsu-Siemens Computers GmbH.
8.9.1 Configuration in CentricStor
The expansion for DiskXtender for Windows in CentricStor is available as of Release 3.1D
SP01.
CentricStor should first be configured and connected with the system on which DiskXtender
for Windows is running so that the CentricStor tapes are already known there when DiskXtender for Windows is installed.
To avoid complications, only the drives required for DiskXtender for Windows should be
generated, and only this CentricStor system should be connected to the DiskXtender for
Windows system at fibre channel level (if necessary select zoning on the FC switch).
8.9.1.1
Virtual Library Services
ACSLS is used for communicating with DiskXtender for Windows, i.e. VACS on the
CentricStor side. The following settings via GXCC ➟ Configuration ➟ Virtual Library Services
must be made to permit this:
Mode:
Enabled
RPC-Port Selection: Default
Access Control:
ON
341
A client entry must be generated for each extended drive on the DiskXtender for Windows
side:
Name:
UserId:
<Name of the DiskXtender for Windows system in capital letters>
By default the user ID has the following format:
DX_<Name of the DiskXtender for Windows system in upper case>_
<Extended Drive letter>
Volumes:
<All volumes which may be used for this extended drive>
The specified volumes are assigned to the extended drive of the DiskXtender system
specified in the relevant user ID.
Creation or deletion of a volume during ongoing operation - after VACS-reinit - is recognized on the fly on the DiskXtender for Windows side.
Example
DiskXtender system WILLI with extended drives D and E is assigned the logical
volumes DXD000 through DXD099 and DXE000 through DXE0999 respecively in
accordance with VACS:
8.9.1.2
Name:
UserId:
VOLUMES:
WILLI
DX_WILLI_D
DXD000 - DXD099
Name:
UserId:
VOLUMES:
WILLI
DX_WILLI_E
DXE000 - DXE099
Logical Drives
The following settings via GXCC ➟ Configuration ➟ Logical Drives must be made to permit
this:
Drive Definition:
Compression:
VLS:
Emu/Inquiry Data:
Comment:
LibDevName:
342
For example 8 as FC-SCSI device number
practical:
ON
DiskXtender cannot copy compressed media to logical drives for
which no compression is set or vice versa. Compression should
therefore be set uniformly in CentricStor for all logical devices which
DiskXtender for Windows can use.
required:
VACS
required:
STK/T9840B
e.g.:
DRIVE00 - DRIVE07
The LibDEvNames (device coordinates) offered by GXCC may
need to be modified to ACS=1 and LSM =1 in the interests of consistency with the home location 1,1,1,1,1 (default) of the media.
You should note down the LibDevName as it is required for DiskXtender for Windows configuration.
i
8.9.1.3
GXCC ➟ Tools ➟ Global Status ➟ Tools ➟ Show Balloon Help Summary can be used
to output a list which, among other things, displays the assignment of the virtual
tape devices to LUN and LibDevName.
Logical Volume Groups
A group with a size of 20 GB must be created since the emulated drives are designed for
this tape size. This size must be used when creating volumes.
Example
Name:
LV Size:
Location:
Comment:
LGPE20
20 GB
FLOATING
DiskXtender Group
This results in the following entry in /usr/apc/conf/vtls_vg.conf for the logical volume
group, e.g. LGPE20:
...
502:LGPE20:DiskXtender Group
LGPE20_ERASE_SCRATCH=0
LGPE20_PARTIAL_SAVE_LIMIT=0
LGPE20_LVSIZE:19070
LGPE20_LOCATION:floating …
8.9.1.4
Add Logical Volumes
When creating volumes for DiskXtender for Windows a group with a size of 20 GB must be
entered as the logical volume group here.
8.9.1.5
Mixed Media Info
The /usr/apc/conf/mixed_media.conf file with the following entries must be active for
VACS:
...
DRIVE:16:T9840B;INQUIRY:T9840B:IBM3490E;MEDIA:STK1R:STK1U
...
MEDIA:9:STK1R;GROUP:BASE:LGPE20;CLEAN:NEVER
...
The /usr/apc/mixed_media.default file is available as a template for manual creation
of the /usr/apc/conf/mixed_media.conf file.
The /usr/apc/conf/mixed_media.conf file is (re)activated by VACS-reinit.
343
8.9.2 Installing DiskXtender for Windows
The following must be installed for the DiskXtender for Windows system in accordance with
vendor specifications:
●
At least Operating System Windows 2003 SP1
●
Fibre Channel controller and driver (e.g. EMULEX LP9002 Port Driver 5.2.40.2 of
07/19/2005 FW 3.93A0; EMULEX LP11002-M4 elxsli2 Driver: SLI-2 v5-2.40a2 of
07/19/2005 FW 2.10A7, etc.)
●
At least SUN StorageTek ACSLS Manger Software Version 1.4.1
●
At least STK 9840B tape driver 6.1.0.0 of 05/12/2003
●
At least EMC DiskXtender for Windows 6.20.027
MediaStor (at least Version 6.2) from EMC is very useful for support during configuration
(see section “DiskXtender for Windows configuration” on page 344) but is not required for
operation. MediaStor should only be installed for this purpose, not configured.
8.9.3 DiskXtender for Windows configuration
i
8.9.3.1
The left mouse button or overlining of the field is meant with the "->" character.
Special activation using the right mouse button is indicated by "(RMT)>".
Ascertaining the name of the tapes
-> Start -> Progams -> EMC MediaStor -> Utilities -> SCSI Manager
Note down the names of the STK T9840B entries.
Example
SCSI.2.1.0.0
..
SCSI.2.1.0.7
The last character in the name under SCSI Manager corresponds to the LUN of the logical
CentricStor device on the HBA port which is assigned to the DiskXtender system. In the
example, these are LUN 0 and LUN 7. The assignments logical tape device, FC controller,
LUN and LibDevName - configuration takes place using GXCC ➟ Logical Drives (see
section “Logical Drives” on page 342) - are stored in the /usr/apc/conf/vtls.conf file.
344
8.9.3.2
Configuring media services
➟ Start ➟ Progams ➟ EMC DiskXtender File System Manager ➟ Administrator
➟ Service ➟ Configure Media Services
➟ Add
(X) StorageTek ACSLS
Configure ACSLS Drives
➟ Add
The entries noted under SCSI Manager and LibDevName are now required. See above for the
assignment.
Device Name:
ACS:
LSM:
Panel:
Drive:
<SCSI Manager Name>
<LibDevName 1st character> 1 (see section “Logical Drives” on
page 342)
<LibDevName 2nd character> 1 (see section “Logical Drives” on
page 342)
<LibDevName 3rd character>
<LibDevName 4th character>
Example
Device Name:
ACS:
LSM:
Panel:
Drive:
SCSI.2.1.0.0
1
1
1
0
Device Name:
ACS:
LSM:
Panel:
Drive:
SCSI.2.1.0.3
1
1
4
0
➟ Add
Enter the next drive and so on until all the drives required have been entered. A single drive
might possibly be enough.
After they have been successfully entered and, if required, Windows has been rebooted,
the services automatically assume the status ONLINE.
345
8.9.4 Further information
●
After labeling, DiskXtender for Windows displays the following sizes for the medium:
Total bytes: 19.999.948.800
Written bytes: 1.006.764.032
●
The Media Copy function is only possible within the ACSLS Media Services. It must be
ensured that the compression setting is uniform (see section “Logical Drives” on
page 342).
●
An alternative to Media Copy is provided by the Multi-Target Feature of DiskXtender for
Windows.
●
When any change is made to the CentricStor configuration for any logical drive (vtd on
ICP), all tape device emulations are stopped and restarted in CentricStor V3.1D
throughout the ICPs when Distribute and Activate takes place. When Distribute and
Activate takes place in CentricStor with the tape device emulations being
stopped/started, the ACSLS Service and the volumes in DiskXtender for Windows go
offline. Remedy: Reboot the DiskXtender for Windows server.
But such uncontrolled offline statuses for DiskXtender for Windows should be avoided
so as to prevent potential inconsistencies in the DiskXtender for Windows environment.
Consequently configuration/reconfiguration in CentricStor von logical drives should only
be performed on the ICP on which the tape device emulations for DiskXtender for
Windows run during previously announced maintenance times or be activated with
Distribute and Activate. For the purpose of this maintenance, the DiskXtender for
Windows server should first be shut down and rebooted following a successful
Distribute and Activate.
346
CommVault Galaxy
8.10 CommVault Galaxy
8.10.1 Documentation
The documentation for CommVault Galaxy is delivered with the product on CDs.
8.10.2 General
●
CommVault Galaxy has been released since 6.1.0 Service Pack 4 on Windows.
For the use with CentricStor the following CommVault Galaxy patches are necessary:
–
–
–
–
win_6.1.0B50_0906
win_6.1.0B50_0946
win_6.1.0B50_0968
win_6.1.0B50_CentricStorScratchAgedMed(1056)
or
–
–
win_6.1.0B50_0906
win_6.1.0B50_1137
(contains win_6.1.0B50_0946, win_6.1.0B50_0968,
win_6.1.0B50_CentricStorScratchAgedMed(1056))
●
Emulation type in CentricStor: IBM3590E1A.
●
Connection of the Media Agent to CentricStor via the library interface ACSLS (VACS);
LibAttach is necessary.
●
Via the CentricStor function VACS ACCESS Control ON the logical volumes have to
be specified, which CommVault Galaxy is allowed to use.
i
CommVault Galaxy accesses all volumes, which it sees in the library.
●
In the library configuration for CommVault Galaxy the Work Pool Number 0 and the
Volume Range NoScratch have to be specified.
CommVault Galaxy scratches an aged volume before reusing it.
A prerecycle script is not necessary.
●
It is recommended to set the timeout value for mount to 90 minutes.
347
CommVault Galaxy
8.10.3 Configuration
8.10.3.1
Configuration of the ACSLS library
Hint: Work Pool Number: 0 and Volume Range: NoScratch
348
CommVault Galaxy
349
CommVault Galaxy
350
CommVault Galaxy
351
CommVault Galaxy
8.10.3.2
352
Configuration of the drives
CommVault Galaxy
353
CommVault Galaxy
354
CommVault Galaxy
355
CommVault Galaxy
356
CommVault Galaxy
Assigning of the VACS coordinates for the drives via Drive ID:
357
CommVault Galaxy
358
8.10.3.3
CommVault Galaxy
Configuration of the mount timeout
359
by f.f. 1992
9 Useful commands and information
9.1 Logging, configuration tools, traces in UNIX systems
System logging
Configuration tools
Program trace
Reliant UNIX
/var/adm/log/messages
sysadm
truss
Solaris
/var/adm/messages
WSA
truss
Linux
/var/log/messages
yast
strace
HP-UX
/var/adm/syslog/syslog.log
sam
truss
smit
only from V5
onwards
AIX
1
1
/var/adm/ras/conslog
This file can only be viewed properly with the program smit.
9.2 Display of CentricStor configuration data for the service
engineer
With maintenance authorization, you can set and read the configuration data via the
graphical interface
GXCC ➔ function bar ➔ configuration. There is a full description in the maintenance
manual [1].
The following instructions are addressed to host system administrators who have no
maintenance authorization for CentricStor and need information for setting up a host or real
robot system.
361
Useful commands and information
9.3 CentricStor configuration data displays for the user
To set up the host configuration, you often need information on which ISP a device
emulation, a library emulation, a device server (PDS) or a library server (PLS) is running.
You receive a compact overview in global status, to start e.g. with:
GXCC main window; Function bar: Tools ➔ Global Status.
9.3.1 IP addresses and host names
ISP
The IP addresses of the ISP are shown at the top of the XTCC main window. The host name
is visible in the label of the ISP icon in the GXCC main window.
The IP addresses of the ISP are also contained in the list which can be viewed with:
GXCC main window; Function bar: Administration ➔ Show WWNN and WWPN
Libraries
The IP addresses of real libraries are shown in the GXCC main window in the robot icons
at the bottom of the display and in the related balloon help.
FC switch
The IP addresses or host names of the internal FC switch (or switches) are displayed in the
object information of the FC fabric.
9.3.2 Emulations
The emulations are represented as columns over the host name of their ICP in global
status. If you leave the mouse pointer over the box which represents the emulation or virtual
device, this will display the name of the emulation, the LUN (fibre channel) or the device
name (ESCON) and the number of the assigned controller and the robot address.
In the XTCC of the relevant ICP you can obtain the same information by left clicking the icon
of the emulation or the virtual device. The inquiry data which have been set are displayed
in the icon of the virtual device.
There is a printable overview at
Global Status; Function bar: Tools ➔ Show Balloon Help Summary.
362
9.3.3 Virtual libraries
The libraries are represented in Global Status by boxes next to the emulations. If you leave
the mouse pointer over the icon, the ISP and emulation type will be displayed.
For VDAS and VACS types, the entered clients are outputted in the balloon info of the icon
in the XTCC window.
The Balloon Help Summary also shows on which ISP the relevant emulation is running.
9.3.4 Real devices (PDS)
In Global Status, the physical drives are shown in a box with the libraries belonging to them.
PDS names and SCSI address CTLs are shown in Balloon Help or in the summary, in order
of ISP.
9.3.5 Real libraries (PLS)
In Global Status, PLSs are represented by a box with the PLS name, the ISP on which the
PLS is running, and the PLS type.
i
SCSI controlled robots are driven by PLS on the ISP to which the SCSI interface of
the robots leads.
The allocation of the PLS to PDS is graphically displayed in the right-hand part of Global
Status.
9.3.6 WWNN and WWPN of the FC connections
GXCC Function bar: Administration ➟ Show WWN’s
A text window with a listing is opened. The data of the host adapter, ordered by ICP, are
shown as external.
363
Control of ADIC / ABBA / AML libraries
9.4 Control of ADIC / ABBA / AML libraries
9.4.1 DASADMIN
In the host
●
The host is the DAS client of VDAS in CentricStor.
The following variables must be set and exported:
DAS_SERVER=<name or IP address of the VDAS servers (see page 363)>
e.g. DAS_SERVER=172.25.95.172
DAS_CLIENT=<name of client (=own name) in configuration>
e.g. DAS_CLIENT=suse7
In CentricStor
●
CentricStor (VLS) is the DAS server for the hosts.
The host should be added to the list of VDAS clients. Its access rights must be set. The
process is described in the maintenance manual under Configurations ➟ Virtual Library
Services.
●
CentricStor (PLS) is the DAS client for DAS in AMU-PC.
In this context, DASADMIN can also be started on the PLS host of the CentricStor (in
the general VLP).
The IP address of the AMU-PC is entered under Configurations ➟ Physical Library
Services.
Drives (PDS) and library services are brought together as libraries with Configurations
➟ Tape Libraries. Here you must also specify if CentricStor takes over the cleaning
management for the drives.
364
In the AMU PC
CentricStor (PLS) is the DAS client of the DAS server in the AMU.
●
In the DAS server, the service engineer must configure the VLP on which the PLS (or
PLSs) run, as the ACI client for the physical CentricStor drives.
After activating the configuration, there should be a function check of mount and
dismount via dasadmin. For real devices this is done from CentricStor (host of the
relevant PLS), for virtual devices it is done from the hosts.
i
If you wish to perform the physical cleaning of the tape drives for some or all drives
via CentricStor (see section on Configuration ➟ Tape Libraries in the maintenance
manual), then the automatic cleaning for these drives must be deactivated on the
AMU-PC. If CLN volume groups are also shown in Global Status next to the physical
volume groups in the library, CentricStor administers the cleaning of the drives in
the corresponding library.
In vtls.conf, the IP address of the server for the physical library is defined in the section
[pls]. The client is defined in the variable SYSNAME (also see page 363).
Activity
Command lines
Allocate
dasadmin allocd <virt.drive> UP <client>
Mount
dasadmin mo [-t <type>] <vsn> <virt.drive>
e.g. dasadmin mo –t 3590 MAG1 002034
Unmount
dasadmin unload [-t <type>] <virt.drive>
Eject -> Home
dasadmin dism [-t <type>] <vsn>
e.g. dasadmin dism –t 3590 002034
Inform
dasadmin listd
Store tape
dasadmin insert <area>
e.g. dasadmin insert I01
Eject tape
dasadmin eject [-t <type>] <volser-range> <area>
e.g. dasadmin eject –t 3590 002034 E01
or dasadmin eject –t 3590 002007-002009 E01
Status of a
tape
dasadmin view [-t typ] <vsn>
e.g. dasadmin view -t LTO A00127
Help
dasadmin -h
365
9.4.2 Communication between client and server
It is common practice these days to construct firewalls between individual security cells.
Here, we describe how communication works in these cases.
RPC communication for DAS control:
DAS client
DAS server
Enquiry for port of program number: 536875008 via
TCP/UDP Port 111
(in UNIX: rpcinfo –p <DAS server>)
Returns port <XXX>
The port is either located dynamically in the system
after server start or can be assigned in VDAS.
A request is made to the DAS server:
The client finds itself a free port and registers itself with
rpcbind with Port <YYY> and a program number. This
is a number from 40000000 and is increased with
every request. A free port is requested every time.
The rpc function communicates the client program
number, where the response is awaited.
Request to DAS server via TCP/IP Port <XXX>
Enquiry for port of program number which was given
via TCP/UDP Port 111
Returns port <YYY>
Confirmation message for the request via port <YYY>
The client logs out of rpcbind releases the port <YYY>
again.
366
9.4.3 Possible problems and solutions
Problem: No connection to VDAS from the SAN host is possible via dasadmin.
●
Call dasadmin qversion on the VLP. For this call, the host (VLP) must be defined in
vtls.conf.
●
Check with rcpinfo -p on the VLP, to see if the rpcbind process works.
●
Is the UDP protocol (see communication between client and server) blocked by a
firewall?
●
In Windows 2000 the variables DAS_SERVER and DAS_CLIENT must be defined as
system variables under: Start ➟ Settings ➟ Control Panel. In Control Panel, select the
entry System (System Properties). In System Properties, click the Advanced tab. In the
center you will find a button called Environment Variables.
●
With the variable ACI_DEBUG=1, a further trace stage can be set.
367
Control of the StorageTek libraries
9.5 Control of the StorageTek libraries
This describes how the physical libraries are operated.
9.5.1 Powderhorn to extend drives
●
Installing and cabling drives
●
Restart LMU with IPL
●
Enter the following commands on the ACSLS-Server:
#kill.acsss
#acsss_config
#rc.acsss
Menu item
7
Y
Y
1
1
/dev/ttya
Y
overwritten
y
Client:
n
Ctrl-c (abort program)
The LOG file is located in /log/acsss_config.log.
However the ACSLS server is administered via cmd_proc .
368
9.5.2 Cleaning management in StorageTek libraries
If the automatic cleaning for the drives (with STK this applies either for all drives or for none)
is to be switched off and CentricStor has to take over the cleaning, proceed as follows:
1. Call acsss_config on the ACSLS computer and select the following menu item:
3: Set general product behavior variables
2. From the parameters which are then offered, set Enable Transport Auto Clean Option to
FALSE.
Make sure that cleaning management is activated in the CentricStor configuration. If CLN
volume groups are also shown in Global Status next to the physical volume groups in the
library, CentricStor will administer the cleaning of the drives in the corresponding library.
9.5.3 Adding tapes in Powderhorn
●
The entry slot must be in AUTO Mode. If necessary, switch this on via ACSLS.
●
Then put the tapes into the entry slot and close.
9.5.4 Adding tapes in L180
●
Open the door, and sort the tapes into the slots.
●
Then close the door again. The robot then makes an inventory run of all the tapes found
in the library.
9.5.5 Starting the ssi daemon
The ssi daemon needs 3 environment variables:
–
–
–
CSI_HOSTNAME=<name of the SUN controller computer with the real robot or of the
VACS host>
CSI_CLIENTNAME=<name of client computer>
CSI_TCP_RPCSERVICE=TRUE
The ssi daemon is started with the command: ssi 0 50004 23
9.5.6 Stopping the ssi daemon
1. Request the PID with ps –ef | grep ssi.
2. kill –15 <pid>
369
9.5.7 cmd_proc
In order to be able to use the program, the ssi process must be running.
Operations with cmd_proc:
Inform
query drive all
Mount
mount <VOL> <POS>
e.g. mount TDS004 2,0,0,1
Unload
dismount <VOL> <POS> f
e.g. dismount TDS004 2,0,0,1 f
Show scratch pools
query pool all
Show contents of a scratch pool
query scratch <pool id>
e.g. query scratch 0
Leave program
logoff
9.5.8 Communication between client and server
It is common practice these days to construct firewalls between individual security cells.
Here, we describe how communication works in these cases.
370
RPC communication for ACSLS control
ACSLS client-server communication:
ACSLS client
ACSLS
server
Enquiry for port of program number: 300031
via TCP/UDP Port 111
← Response via
dynamic port
← Returns port <XXX>
(in UNIX: rpcinfo –p <ACSLS server>)
The port is either located dynamically in the
system after server start, or it can be
assigned in VACS.
A request is made to the ACSLS server:
SSI daemon
Robot controller program
Request via Port
50004 →
(50000–50099
possible)
If the SSI daemon has still not registered
with rpcbind, it finds a free port and registers
with rpcbind with port <YYY> and the
program number. This lies between
1234567886 – 1234567985 and depends
on the port number of the client.
e.g. Port 50004 == 1234567890
The rpc function communicates the SSI
program number, where the response is
awaited.
Request to ACSLS server via TCP/IP Port
<XXX> →
←Enquiry for port of program number,
which was given, via TCP/UDP Port 111
Returns port <YYY> →
← Confirmation message for the request via
port <YYY>
The SSI daemon does not log out from
rpcbind.
371
Information on the Cashion connection
9.5.9 Possible problems and troubleshooting advice
Problem: No connection to VACS possible from SAN host.
●
Call cmd_proc -p 50099 on the VLP.
●
On the VLP use rcpinfo -p to check whether the rpcbind process works.
●
Is the UDP protocol (see section “Communication between client and server” on
page 370) blocked by a firewall ?
●
Under Windows 2000 and WIN-NT the Storagetek Libattach and PowerRPC Portmapper
services must be active.
9.6 Information on the Cashion connection
For a Cashion connection over 122 m, 2 COM servers (COM <-> Ethernet) from
W&T1 - Product 586312 - were used which were configured in box-to-box mode.
The configuration is described in the manual3.
The following parameters from the standard package had to be modified here:
●
TCP/IP addresses/configuration (gateway, network masks)
Setting to box-to-box
Standard: 9600,8,N,1
Modification of hardware handshake ➟ without handshake
●
ISP-COM connection with 9P/9P twisted serial cable. Robot connection with
standard 9P/25P cable.
Connection of the COM servers takes place via a normal LAN.
1
http://www.wut.de
2
http://www.wut.de/e-58631-ww-dade-000.php3
3
http://www.wut.de/e-58w3w-10-inde-000.php3
372
Information on Fujitsu libraries
9.7 Information on Fujitsu libraries
The control computer of FUJITSU libraries is the PLP. All settings for the FUJITSU library
are made on this, such as adding or deleting clients.
This is done with the lmadmin program which is contained in the
/opt/FJSVlmf/bin directory.
Further information is provided in the following PLP manuals:
–
–
–
–
–
FUJITSU LMF SERVER/CLIENT USER'S GUIDE
ETERNUS LT270 TAPE LIBRARY UNIT INSTALLATION INSTRUCTIONS
ETERNUS LT270 Tape Library User's Guide
ETERNUS LT270 Setup Guide
ETERNUS LT270 Tape Library Maintenance Guide
9.8 Qualified fibre channel switches in the SAN environment
9.8.1 Features of the FC connection
●
Provided that no direct point-to-point connections between host and CentricStor/ICP
are used, all components of the SAN can be connected via a fibre channel switch to the
CentricStor ICPs. The (brocade) switch works here with zoning which can be
configured via Telnet or Internet Explorer. For more information, see the chapter on
zoning (see page 374).
●
Startup sequence: The FC switch must always be switched on first and then the
CentricStor ICPs. If you do not switch on in this sequence FC_AL will be activated
instead of FC point-to-point.
●
If a Linux 8.0 host shares an ICP host connection with other systems (Linux or other),
no part of the configuration may be changed while the system is running. This includes
reboot and shutdown processes of one of the hosts.
373
9.8.2 Permitted FC switches
Manufacturer Type
1
Brocade
Silkworm 2800
Ports
FW
Comments
16
V2.1
Silkworm 2800 with emc FC
firmware extension
V2.2.1.a
Silkworm 3800
Silkworm
Connectrix
DS16B
41002
16
V3.1.3
16, 24, 32 V5.1.0a
16
V2.5.0.d
1
Regardless of the switch type used, it is advisable to set the transmission speed explicitly for the port employed
with the portcfgspeed command.
2
If an FC switch Brocade 4100 is used internally or externally in a CentricStor system, problems can occur in the
automatic recognition of the FC topology (LOOP instead of fabric).
The problem can be solved by explicitly preventing the use of LOOP on the port employed: The switch command
portcfggport ensures that LOOP initialization does not take place. You can obtain information about this using
the help command.
9.8.3 Zoning
9.8.3.1
Rules
–
–
The SAN switch must be independent and must not be linked to the internal switch from
CentricStor.
There are 2 different ways to configure zoning:
1. Port zoning (recommended for CentricStor)
2. WWN zoning
Port zoning obliges the use of a strict, but advantageous cable plan. It does not require
any changes to be made to the configuration of the switch when host bus adapters are
exchanged. With WWNN-Zoning, defective GBIC ports can be changed without reconfiguring.
–
–
–
–
374
Each zone may contain only one point-to-point connection to a host, so that if there is
an error in a host bus adapter, further connections are not broken.
While a new zone configuration is being activated, there should be no data traffic in the
whole fabric.
The rule that you should not have any overlapping zones on a device (here the ICP),
must be broken. You must break the rule in order to enable ICP-Sharing by different
hosts.
Only connections that are strictly necessary should be created.
9.8.3.2
Zoning example (6 hosts on 3 ICPs)
colorado
RM 600:
Reliant UNIX
Primepower:
Solaris
6
Ports:
ente 2
ente 1
V8
Windows
NT
Windows
2000
8
7
ente 4
ente 3
9
Windows
NT
Windows
2000
11
10
Zones:
6-0, 6-1, 6-2
7-0, 7-1, 7-2
8-3, 10-4
9-3, 11-5
FC switch
(external)
Ports:
0
2
1
3
ICP2
4
5
14
15
V200 ... V21E
V21F
V220 ... V23E
14
V100
V101 ... V10F
V23F
32 LDs
32 LDs
ICP1
Mammoth2
15
Mammoth2
generic SCSI II
V110
16 LDs
14
ICP0
15
V000 ... V00F
V010 ... V01F
16 LDs
16 LDs
V111 ... V11F
16 LDs
V120 ... V12F
16 LDs
V130 ... V13F
16 LDs
generic SCSI II
V020 ... V02F
16 LDs
V030 ... V03F
16 LDs
RM600 with Reliant UNIX are assigned as follows:
–
–
–
The first 16 LDs of ICP0 via controller 14
The second 16 LDs of ICP0 via controller 15
The first 16 LDs of ICP1 via controller 14
The Primepower with Solaris are assigned as follows:
–
–
–
The third 16 LDs of ICP0 via controller 14
The fourth 16 LDs of ICP0 via controller 15
The second 16 LDs of ICP1 via controller 14
ente 1 with Windows NT are assigned as follows:
– The third 16 LDs of ICP1 via controller 15
ente 2 with Windows 2000 are assigned as follows:
– The fourth 16 LDs of ICP1 via controller 15
375
ente 3 with Windows NT are assigned as follows:
– The first 32 LDs of ICP2 via controller 14
ente 4 with Windows 2000 are assigned as follows:
– The second 32 LDs of ICP2 via Controller 15
This example continues to be widely used in the configuration of Reliant UNIX, Solaris and
NetWorker.
9.8.3.3
376
Configuration example
port 00
ICP0
port 02
ICP1
port 04
ICP2
port 06
RM600
ctrl 14
ctrl 14
ctrl 14
colorado
port 01
ICP0
port 03
ICP1
port 05
ICP2
port 07
Solaris
ctrl 15
ctrl 15
ctrl 15
V8
port 08
Windows
NT
ente 1
port 10
Windows
NT
ente 3
port 12
port 14
port 09
Windows
2000
ente 2
port 11
Windows
2000
ente 4
port 13
port 15
Machine
Zone
active
ICP
colorado (RM) VTLS0600 ( 6 - 0)
Yes
ICP0 ctrl 14
Yes
ICP0 ctrl 15
Yes
ICP1 ctrl 14
Solaris (V8)
VTLS0600 ( 7 - 0)
Yes
ICP0 ctrl 14
Solaris (V8)
VTLS0701 ( 7 - 1)
Yes
ICP0 ctrl 15
Solaris (V8)
VTLS0702 ( 7 - 2)
Yes
ICP1 ctrl 14
ente 1 (NT)
VTLS0803 ( 8 - 3)
Yes
ICP1 ctrl 15
ente 2 (2000)
VTLS0903 ( 9 - 3)
Yes
ICP1 ctrl 15
ente 3 (NT)
VTLS1004 (10 - 4)
Yes
ICP2 ctrl 14
ente 4 (2000)
VTLS1105 (11 - 5)
Yes
ICP2 ctrl 15
ente3 (NT)
VTLS0005 (0 - 5)
ente (NT)
VTLS0105 (1 – 5)
Colorado (RM) VTLS0605 (6 – 5)
ICP7 (for tests)
Yes
ICP7 (V700 – V70F)
ente2 (NT)
VTLS0805 (8 – 5)
ICP7 (V710 – V71F)
ente4 (NT)
VTLS1005 (10 – 5)
ICP7 (V710 – V71F)
hp-ux01
VTLS1105 (11 - 5)
Yes
ICP7
Solaris V8
VTLS1205 (12 - 5)
Yes
ICP7
ente3 (NT)
VTLS0015 (0 - 15)
Yes
ICP8 (for tests)
ente (NT)
VTLS0115 (1 – 15)
Yes
ICP8 (V808 – V80F)
Colorado (RM) VTLS0615 (6 – 15)
ICP8 (V800 - V807)
ente2 (NT)
VTLS0815 (8 – 15)
Yes
ICP8
ente4 (NT)
VTLS1015 (10 – 15)
Yes
ICP8
hp_ux01
VTLS1115 (11 – 15)
Solaris (V8)
VTLS1215 (12 – 15)
ICP8
Yes
ICP8
377
9.8.3.4
Configuration of the brocade switch via Internet Explorer
Call Administration tool:
378
Then select Zone Administration, enter login admin and password.
379
Define zones:
●
Enter the zones (see example above) in the configuration and activate with Apply.
Outputting zoning with telnet:
Note: When describing the zones, the domain is also specified, e.g.
zone: vtls0005 2,0; 2,5
means that the zone vtls0005 contains the ports 0 and 5 in switch 2.
HASE_SW2:admin> zoneshow
Defined configuration:
cfg: konfigCAT1
vtls0115; vtls1215; vtls1205; zone39; zone27; zone137;
zone49;
vtls0815; vtls0015; vtls1015; vtls1105; vtls0605
cfg: konfigCAT2
zone39; zone27; zone137; zone49
zone: cross01 2,14; 2,1
zone: cross02 2,14; 2,8
zone: vtls0005
2,0; 2,5
380
zone: vtls0015
2,0; 2,15
zone: vtls01 2,13; 2,15; 2,8; 2,1
zone: vtls0105
2,5; 2,1
zone: vtls0115
2,15; 2,1
zone: vtls0605
2,5; 2,6
zone: vtls0615
2,15; 2,6
zone: vtls0805
2,5; 2,8
zone: vtls0815
2,15; 2,8
zone: vtls1005
2,10; 2,5
zone: vtls1015
2,10; 2,15
zone: vtls1105
2,11; 2,5
zone: vtls1115
2,11; 2,15
zone: vtls1205
2,5; 2,12
zone: vtls1215
2,12; 2,15
zone: zone02 2,2; 2,7
zone: zone03 2,3; 2,0
zone: zone04 2,4; 2,0
zone: zone10 2,10; 2,7
zone: zone11 2,11; 2,9; 2,7
zone: zone137 2,13; 2,7
zone: zone27 2,2; 2,7
zone: zone39 2,3; 2,9
zone: zone49 2,4; 2,9
381
Effective configuration:
cfg: konfigCAT1
zone: vtls0015
2,0
2,15
zone: vtls0115
2,15
2,1
zone: vtls0605
2,5
2,6
zone: vtls0815
2,15
2,8
zone: vtls1015
2,10
2,15
zone: vtls1105
2,11
2,5
zone: vtls1205
2,5
2,12
zone: vtls1215
2,12
2,15
zone: zone137 2,13
2,7
zone: zone27 2,2
2,7
zone: zone39 2,3
2,9
zone: zone49 2,4
2,9
382
9.8.3.5
Diagnostics in the event of performance problems
When performance problems occur it may be necessary to look at the data throughput in a
CentricStor system. The easiest way to ascertain the values is on the internal FC switch.
With Brocade switches this is possible using telnet.
Use telnet to go to the switch under the admin ID. You must ask the service provider for
the password for admin. The FC switches a defined under the names FCS0 through FCS3
in the /etc/hosts file.
The following commands can be used to read out information:
fabricshow
Shows the fabric configuration
switchshow
Shows the configuration of the ports and connected WWPN. Interconnect connections and FC speeds are displayed.
zoneshow
Shows the configured and active zones (switch on the frontend or
backend)
portperfshow
Shows the performance on the various ports and Interconnect connections
The session is terminated with the logout command.
If Brocade switches are also installed on the SAN side it is also possible here to perform
objective analyses using the commands mentioned above. In this case the Interconnect
connections in particular must be looked at specifically as they occassionally present a bottleneck.
383
Host bus adapters (HBA)
9.9 Host bus adapters (HBA)
9.9.1 Overview of the host bus adapters
Tested host bus adapters:
384
Type
GB Manufac- GBIC present
turer
Comment
LP6205
1
Emulex
no
Will not be tested (RM400-CF02)
LP7000
1
Emulex
no
In RS/6000 with special FW as FC
6227
LP8000
1
Emulex
yes
(RM400-CF10,RM6T5CF10,GP7xx-CF10)
LP9002
2
Emulex
no
LP9802
2
Emulex
no
QLA2100F
1
Qlogic
no
QLA2200F
1
Qlogic
no
QLA2310F
2
Qlogic
no
QLA2340
2
Qlogic
no
QLA2342
2
Qlogic
no
HP FCA2214
2
Qlogic
no
In HP systems
QLA2310-SUN 2
Qlogic
no
In SUN systems
HP5158
1
HP
yes
In HP systems
A5158A
1
Agilent
yes
In HP systems
A6795A
2
Agilent
no
In HP systems
A6826A
2
Qlogic
no
In HP systems
HP FCA2101
2
HP
yes
HP FCA2404
2
HP
no
FC6228
2
IBM
no
00P2995/96 (FC 6228)
FC6239
2
IBM
no
In IBM systems (LP9802)
Is not used as only HUB is
supported
9.9.2 Firmware download
9.9.2.1
LP8000
In MSDOS, the current firmware version is loaded onto the LP8000 card with the program
lputil. The program and description can be downloaded from the Internet from the manufacturer's page at: (www.emulex.com).
9.9.2.2
QLA2200F
When using the QLOGIC driver, the driver firmware is loaded to the board.
9.9.3 BIOS settings
9.9.3.1
LP8000
The card works without special BIOS settings.
9.9.3.2
QLA2200F
BIOS settings QLA2200F:
Setting
Default
CentricStor
Host Adapter Settings
Host Adapter BIOS
Disabled
Frame Size
1024
Loop Reset Delay
5 seconds
Adapter Hard Loop ID
Disabled
Hard Loop ID
0
2048
Advanced Adapter Settings
Execution Throttle
16
Fast Command Posing
Enabled
>4Gbyte Addressing
Disabled
LUNs per Target
8
Enable LIP Reset
No
Enable LIP Full Login
Yes
Enable Target Reset
No
32
385
Setting
Default
Login Retry Count
8
Port Down Retry Count
8
Drivers Load RISC Code
Enabled
Enable Database Updates
No
Disable Database Load
No
IOCB Allocation
256 buffers
Extended Error Logging Disabled
Disabled
CentricStor
64
Extended Firmware Settings
386
Extended Control Block
Enabled
RIO Operation Mode
0
Connection Options
3
Class 2 Service
Disabled
ACK0
Disabled
Fibre Channel Tape Support
Disabled
Fibre Channel Confirm
Disabled
Command Reference Number
Disabled
Read Transfer Ready
Disabled
Response Timer
0
Interrupt Delay Timer
0
1
enabled
9.10 Example of a filter bridge for separating CentricStor™
9.10.1 General
The problem that customers want to be certain that CentricStor does not open a back door
into their computer centers repeatedly raises its ugly head. One approach to solve this is a
filter bridge between CentricStor and the rest of the computer center on the basis of a
LINUX PC. The following is intended as an aid to solving this problem.
●
A conventional PC with at least 2 network interfaces can be used.
●
The LINUX system used in the CentricStor development was, for example, SuSE
SLES9 Rcxx. Linux 2.6.5-7.97 is supplied as the kernel, and this is sufficient. However,
the userland commands brctl and ebtables are not available. These were
obtained from the Internet as a source and compiled and installed.
●
The system contains the start/stop script bridge which you can copy with cut&paste to
the /root ID, for example. The commands are then:
Start:
Stop:
Status:
sh /root/bridge start
sh /root/bridge stop
sh /root/bridge status
●
The bridge configuration is also available on the system and should be copied under
the ID /etc/sysconfig, otherwise the bridge script must be adjusted. Adjustments are
only required in this configuration file. You have a free hand in designing the set of rules
RULES_xx, provided you bear in mind that the set of rules is interpreted/evaluated
several times by the shell before it is executed. It is advisable to use the example below
as a guide.
●
The ports used by CentricStor are described after the scripts.
9.10.2 Start/stop script bridge
#! /bin/sh
#
# /etc/sysconfig/csbridge
#
### BEGIN INIT INFO
# Provides:
CentricStor
# Required-Start: network
# Required-Stop: network
# Default-Start: 2 3 5
# Default-Stop:
387
# Description:
Start the system filtering bridge
### END INIT INFO
LV=èxpr \ùname -r\` : '$...$.*'`
BRCTL=`which brctl`
EBTABLES=`which ebtables`
IPTABLES=`which iptables`
IFCONFIG=`which ifconfig`
. /etc/rc.status
rc_reset
[ "$BRCTL" -a "$EBTABLES" -a "$IFCONFIG" ] || {
echo -n "$0: one or more commands not found"
false; rc_status
rc_exit
}
. /etc/sysconfig/csbridge
[ "$CSBRIDGE" = yes ] || exit 0
[ "$LV" ] && expr $LV \< 2.6 >/dev/null && {
echo -n "$0: Linux Kernel has to be 2.6 or newer"
false; rc_status
rc_exit
}
get_ip () {
IF=$1
ifconfig $IF | sed -ne '/inet addr:/s/.*inet addr:$[09\.]*$.*$/\1/p'
}
get_mask () {
IF=$1
ifconfig $IF | sed -ne '/Mask:/s/.*Mask:$[0-9\.]*$.*$/\1/p'
}
get_bridges () {
ls -1 /sys/class/net | egrep '^br[0-9]'
}
reset_ebtables () {
$EBTABLES -F
$EBTABLES -t
$EBTABLES -X
$EBTABLES -t
$EBTABLES -P
$EBTABLES -P
388
broute -F
broute -X
INPUT ACCEPT
OUTPUT ACCEPT
$EBTABLES -P FORWARD ACCEPT
[ -f /tmp/ebtabsav ] && sh /tmp/ebtabsav
}
reset_iptables () {
$IPTABLES -F
$IPTABLES -t
$IPTABLES -X
$IPTABLES -t
$IPTABLES -P
$IPTABLES -P
$IPTABLES -P
}
nat -F
nat -X
INPUT ACCEPT
OUTPUT ACCEPT
FORWARD ACCEPT
get_brif () {
BR=ècho $1| sed -e 's/^br//'`
$BRCTL show |
awk '
BEGIN { run=0 }
/^br'"$BR"'/ { run=1 }
/^br[^'"$BR"']/ { run=0 }
{ if ( run == 1 ) print $NF
}'
}
portof () {
SERVICE=$1
PROTO=$2
egrep '^'$SERVICE'[ ].*/'$PROTO /etc/services | sed -e 's@/.*@@' -e
's/^.*[ ]//'
}
macof () {
cat /sys/class/net/$1/address
}
get_brif () {
BR=ècho $1| sed -e 's/^br//'`
$BRCTL show |
awk '
BEGIN { run=0 }
/^br'"$BR"'/ { run=1 }
/^br[^'"$BR"']/ { run=0 }
{ if ( run == 1 ) print $NF
}'
}
389
case "$1" in
start)
echo -n "Starting csbridge services"
$0 probe >/dev/null && {
true ; rc_status -v
rc_exit
}
[ "$CSBRIDGES" ] || {
false ; rc_status
rc_exit
}
echo; echo " saving ebtables / iptables "
echo "EBTABLES=$EBTABLES" >/tmp/ebtabsav
echo "IPTABLES=$IPTABLES" >>/tmp/ebtabsav
$EBTABLES -L | sed -e 's/,.*: / /' -ne '/Bridge chain:/s/Bridge
chain:/$EBTABLES -P /p' >> /tmp/ebtabsav
$EBTABLES -L --Lx >>/tmp/ebtabsav
$EBTABLES -t broute -L --Lx >>/tmp/ebtabsav
echo "echo \"`cat /proc/sys/net/ipv4/ip_forward`\" >
/proc/sys/net/ipv4/ip_forward" >>/tmp/ebtabsav
echo -n " creating csbridges "
for i in $CSBRIDGES ; do
echo -n "br$i "
IF_IP=""
IF_MASK=""
for j in èval echo \\\$CSPUBLIC_$i \\\$CSPRIVATE_$i` ; do
IF_IP_T=`get_ip $j`
[ "$IF_IP" -a "$IF_IP_T" ] && {
# Fehler
echo
echo "You listed more than 1 configured interface for the
bridge br$i"
false ; rc_status ; rc_exit
}
[ -z "$IF_IP" ] && {
IF_IP=$IF_IP_T
IF_MASK=`get_mask $j`
}
done
$BRCTL addbr br$i ; rc_status
for j in èval echo \\\$CSPUBLIC_$i \\\$CSPRIVATE_$i` ; do
echo ; echo -n "
setting up interface $j for bridge br$i"
$BRCTL addif br$i $j ; rc_status
$IFCONFIG $j down ; rc_status
$IFCONFIG $j 0.0.0.0 promisc up ; rc_status
done
390
[ "$IF_IP" ] && {
echo ; echo -n "
setting up interface br$i"
$IFCONFIG br$i $IF_IP netmask $IF_MASK promisc up ; rc_status
}
[ "èval echo \\\$RULES_$i`" ] && {
echo ; echo -n "
setting up ebtables for bridge br$i"
[ -f "èval echo \\\$RULES_$i`" ] && {
sh èval echo \\\$RULES_$i` ; rc_status
} || {
eval echo \"ècho \\\$RULES_$i`\" | sh ; rc_status
}
}
done
echo ; echo -n "csbridge needs about 30 seconds to initialize"
echo ; echo -n "
- please give me some time"
rc_status -v
;;
stop)
echo -n "Shutting down csbridge services"
BRIDGES=`get_bridges`
echo -n " - Bridges: "$BRIDGES
[ "$BRIDGES" ] || {
true; rc_status -v
rc_exit
}
for i in $BRIDGES ; do
BR_NR=ècho $i | sed -e 's/br//'`
BR_IF=`get_brif $i`
$IFCONFIG $i down
for j in $BR_IF ; do
[ "$j" = "no" ] || {
$IFCONFIG $j down
$BRCTL delif $i $j ; rc_status
}
done
$BRCTL delbr $i ; rc_status
done
reset_iptables ; rc_status
reset_ebtables ; rc_status
/etc/init.d/network restart
rc_status -v
;;
try-restart)
$0 stop && $0 start
rc_status
;;
restart)
391
$0 stop
$0 start
rc_status
;;
reload|force-reload)
;;
status)
echo "Checking for service csbridge:"
$BRCTL show
; rc_status
$EBTABLES -L --Ln
; rc_status
$IPTABLES -vL --line-numbers ; rc_status
rc_status -v
;;
probe)
echo -n "csbridge: "
ls /sys/class/net/br* >/dev/null 2>&1 && {
echo " configured"
exit 0
} || {
echo " unconfigured"
exit 1
}
;;
*)
echo "Usage: $0 {start|stop|status|try-restart|restart|forcereload|reload|probe}"
exit 1
;;
esac
rc_exit
9.10.3 Configuration file: csbridge
## Path:
Network/CSbridge
## Description:
## Type:
yesno
## Default:
yes
## Config:
kde,profiles
#
# Enable a filtering bridge for use in CS environment.
# This setting allows to turn the CSbridge on and off while
# preserving the particular network setup.
#
CSBRIDGE="yes"
## Type:
392
string
## Default: ""
#
# CSBRIDGES is the list of bridges to be initialized
# example: CSBRIDGES="0 1 2" enables three bridges
# with the public interfaces CSPUBLIC_0, CSPUBLIC_1 and CSPUBLIC_2
# and the private interfaces CSPRIVATE_0, CSPRIVATE_1 and CSPRIVATE_2
# and creates the virual interfaces br0, br1 and br2,
#
# active interfaces of the standard network configuration
# are mapped to the br interfaces.
# If the count of defined bridges does not match the
# count of configured interfaces, csbridge will not start
#
CSBRIDGES="0"
## Type:
string
## Default: ""
#
# CSPUBLIC/PRIVATE_xx are lists of interfaces
# to be used by bridge xx
# up to now, only 1 element per list is allowed
# Example:
# CSPUBLIC_0="eth0"
# CSPRIVATE_0="eth1"
#
CSPUBLIC_0="eth0"
CSPRIVATE_0="eth2"
## Type:
string
## Default: ""
#
## Type:
string
## Default:
""
#
# PROTECTED_HOSTS_xx are lists of IP-Addresses
# to be used by bridge xx
# Example:
# PROTECTED_HOSTS_0="172.25.95.144" # Host: columbia
#
PROTECTED_HOSTS_0="172.25.95.144 172.25.95.166"
## Type:
## Default:
string
""
macof () {
cat /sys/class/net/\$1/address
}
393
# RULES
#
RULES_0="
portof () {
SERVICE=\$1
PROTO=\$2
egrep '^'\$SERVICE'[
].*/'\$PROTO /etc/services | sed -e
's@/.*@@' -e 's/^.*[
]//'
}
echo 1 > /proc/sys/net/ipv4/ip_forward ;
$EBTABLES -P INPUT ACCEPT ;
$EBTABLES -P FORWARD ACCEPT ;
$EBTABLES -P OUTPUT ACCEPT ;
# DIRECTION : both
$IPTABLES -t filter -P FORWARD DROP;
#
PROTO=tcp ;
for ir0 in ntp sunrpc 9669 6996 domain 2000 ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
ir0=\`portof \$ir0 \$PROTO\`;
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT
done ;
# next block can be deleted if working with fixed ports in VLS
for ir0 in 1024:65535 ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT
done ;
;
;
;
;
$IPTABLES -t filter -A FORWARD -p icmp --icmp-type 8 -j ACCEPT
PROTO=udp ;
for ir0 in ntp snmp snmptrap sunrpc domain ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT ;
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT ;
done ;
#
$IPTABLES -t filter -A FORWARD -j ACCEPT -m state --state
ESTABLISHED,RELATED;
#
# PROTECTED_HOSTS_0 will be REJECTED, not DROPPED
if [ \"$PROTECTED_HOSTS_0\" ] ; then
$IPTABLES -N HOSTREJ ;
# $IPTABLES -P HOSTREJ DROP ;
394
for ir0 in $PROTECTED_HOSTS_0 ; do
$IPTABLES -t filter -A FORWARD -j HOSTREJ -s \$ir0 ;
$IPTABLES -t filter -A FORWARD -j HOSTREJ -d \$ir0 ;
done ;
$IPTABLES -t filter -A HOSTREJ -j LOG --log-level warning --logip-option --log-tcp-option --log-prefix REJ\ ;
$IPTABLES -t filter -A HOSTREJ -p tcp -j REJECT --reject-with
tcp-reset ;
$IPTABLES -t filter -A HOSTREJ
-j REJECT --reject-with
icmp-host-prohibited ;
$IPTABLES -t filter -A HOSTREJ -j DROP;
fi ;
#
# Logging
#
$IPTABLES -t filter -A FORWARD -j LOG --log-level warning --log-ip-option
--log-tcp-option --log-prefix DROP\ ;
$IPTABLES -t filter -A FORWARD -j DROP;
"
395
9.10.4 Ports used by CentricStor
Port
Service
Protocol Service
111
sunrpc
udp
RPC services
6996
tcp
GXCC (can be locked if single mode is used in GXCC)
9669
tcp
GXCC
ICMP
Ping (GXCC works with this)
Typ 8
When the DAS interface is used
xxxx
tcp
A fixed DAS port can be defined for VDAS with firewall
option. sunrpc (port 111) can then be locked.
xxxx
tcp
VDAS port for RPC can be permanently assigned.
When the ACSLS interface is used
xxxx
396
tcp
VACS port for RPC can be permanently assigned.
25
smtp
tcp
If the VLP sends mail
53
domain
tcp
If the VLP operates with DNS, e.g. sends mail
53
domain
udp
If the VLP operates with DNS, e.g. sends mail
123
ntp
tcp
If NTP is used
123
ntp
udp
If NTP is used
161
snmp
udp
If CentricStor SNMP is monitored
162
snmptrap udp
If CentricStor SNMP is monitored
xxxx
tcp
RPC port in the PLS configuration with firewall
50050+
<PLS No>
tcp
ssi port for reply from ACSLS server (e.g. 50052 for
PLS2)
Long distance over an FCIP connection with Cisco Switch
9.11 Long distance over an FCIP connection with Cisco Switch
FCIP connections can be established using Cisco Switches / Directors of the MDS-9000
family.
FCIP is a storage networking technology (RFC 3821) based on the Internet protocol which
enables FC data to be tunneled via IP networks.
9.11.1 Long distance over an FCIP connection between the internal Brocade
Switches of CentricStor with CMF
CentricStor
Seite 1
9.11.1.1
Configuration overview
9.11.1.2
Configuration settings
i
CentricStor
Seite 2
Important for the CISO-FCIP configuration: the IOs within CentricStor may not be
interrupted in order to prevent the CentricStor mirror from being split.
If only one connection between the sides exists, the CentricStor ISPs must be shut down a vtcon stop is not sufficient.
Cisco settings
●
A VSAN without zones
●
Firmware status >= 3.1.2 required
●
MTU (Maximum Transmit Unit) Frame Size:
The default size is 1500. You are recommended not to change the pathmtu enable setting; this is used to calculate the best MTU size automatically.
397
Not all network connections support an MTU size > 1500.
●
Sets Write acceleration for FCIP
●
Interoperability Mode in the Cisco Switch/Director 3
●
Sets ISL Port in the device manager to E (E_port)
Brocade settings
●
ISL: Defines the port on the Brocade Switch which is connected to Cisco using
portcfgislmode <port number>, 1
●
Interoperability Modes in the Brocade: remains in native mode
●
PID format must be set to 1.
This can be checked using configshow: fabric.ops.mode.pidFormat
9.11.1.3
Configuring the Cisco Switch via the graphical user interface (Fabric Manager)
Setting the license
Setting Interop Mode on Cisco
398
FCIP wizard for setting up the FCIP connection between the two switches
Tools ➟ Others ➟ FCIP Tunnel
399
400
401
402
403
Device Manager
The ISL connection must be defined as E (E_Port) in the Device Manager:
404
Tunnels Advanced for setting Write Accelerator
Gigabit Ethernet
Overall view of fabric with FCIP and the two CentricStor sides
405
Ping for determining the runtime to terminals
9.11.2 Long distance over an FCIP connection between IDP and real tape
9.11.2.1
406
Configuration overview
9.11.2.2
Configuration settings
Cisco settings:
●
Firmware status >= 3.1.2 required
●
MTU (Maximum Transmit Unit) Frame Size:
The default size is 1500. You are recommended not to change the pathmtu enable setting; this is used to calculate the best MTU size automatically. Not all network connections support an MTU size > 1500.
9.11.2.3
●
Sets Write and Tape Acceleration for FCIP
●
Sets Port in the device manager to Fx_Port
Configuring the Cisco Switches via the graphical user interface (Fabric Manager)
Defining zones for the visibility of the real tape drives
407
Defining Write and Tape Acceleration
408
Special feature for real drives in fabric mode
Persistent FcIDs must be defined for the drives. Only certain values are permitted from the
viewpoint of CentricStor so that a corresponding target for the drive can be generated on
the IDP.
Device Manager: FC ➟ Domain Manager ➟ Persisiten FcIDs
9.11.3 Test environment
2 * Cisco MDS 9509 Multilayer Director DS-C9509 FW Level 3.1(2b)
comprising:
Supervisor/Fabric-2
2x1GE IPS, 14x1/2Gbps FC Module
DS-X9530-SF2-K9
DS-X9302-14K9
409
VACS security by means of ownership
9.12 VACS security by means of ownership
This section provides an example of how the VACS ownership configuration parameters are
used, and the special features of their use with the various backup tools are described.
9.12.1 VACS configuration parameters in GXCC
The screenshot below shows the VACS configuration parameters in the GXCC menu Configuration ➟ Virtual Library Services:
410
9.12.2 Application example of ownership transfer for a volume
Media server
Master server
has overall control of all volumes
Normal media server
can only access its own volumes
Master
Media server 1
Media server 2
Media server 3
Rule for transferring the ownership of volumes
Parameter setting
Meaning
Mount Scratch Ownership:
Requestor
With mount scratch the requester becomes the new
owner of the volume.
Set Scratch Ownership:
Unowned
With set scratch the volume is set to unowned.
Procedure
Initial status
for volume:
➟
unowned
into scratch pool
Media server 1/2/3
➟
Master server
Activity:
mount
Activity:
set scratch
owned by M1/2/
out of scratch pool
unowned
into scratch pool
Note
The master decides centrally that volumes are to be set to scratch. As the master is the
Authorized User, it can do this without taking over ownership of the volumes.
Mutual access to the volumes by the media servers is prevented by the ownership.
When a volume is released, it can be selected by any media server.
A volume either has one owner or is unowned.
411
9.12.3 Ownership of a volume
Assigning the ownership of a volume
●
By entering the volume in a volume range for a client in the VACS configuration (initial
ownership of volumes).
!
CAUTION!
This applies only when an owner is set for the first time for a volume, otherwise
the ownership is not changed.
Check using volrpt.
●
By assigning ownership using the cmd_proc subcommand: set owner
●
Using rules for transferring ownership when the following activities are performed: mount
scratch, set scratch, set scratch reset.
When the status changes from scratch to data you can, for example, define that the
mounting user is to become the new owner.
A specific mount for a volume from a scratch pool is handled like a mount scratch.
Checking the ownership of a volume
Using the volrpt command
Example
VLP1 (KAUZ)# vlscmd VC01 volrpt -v XC0000
VSN
GRP
SIZE ACCESS TIME STATE FLG LOCATION
XC0000 KM20GB 16384 Home
1,1,1,1,1
412
POOL
0
LOCK OWNER
0
unowned
9.12.3.1
Definition and meaning of the Userid in the ACSLS
The Userid discussed here has nothing to do with a user account at operating system level.
It is defined in the backup tool for ACSLS accesses; the default is the host name or empty
(““).
Whether an ACSLS Userid can be set depends on the backup tool:
9.12.3.2
Backup tool
Option of setting the Userid explicitly from the backup tool (if this
is not possible, either the host name or empty is used)
BS2000/Archive …
-
DataProtector
YES
DiskXtenderW
YES
MVS CSC
-
MVS LMS/CSMVS
-
Netbackup
-
Networker
-
TSM w/o Gresham
-
TSM with Gresham
YES
Authorized Userid
The Authorized Userid can access volumes of the assigned Userid. It does not need to be
the owner to obtain access.
The following backup tools enable a client/master relationship to be set up for VACS access
to volumes:
●
Netbackup
●
Data Protector
413
9.12.3.3
Special features when using the VACS security rules
Definition of the Userid for the host
In VACS the Userid used by the backup tool which is employed for ACSLS requests must
be entered. All is not permitted. Most backup tools use ("") or the host name for ACSLS requests.
VACS replaces the empty entry by the first entry found. It is therefore recommendable to
enter the host name as the Userid if no explicit Userid is known.
414
Backup tool
Userid
BS2000/Archive … CSC
Host name
DataProtector
Userid is formed from the device name of the library in
DataProtector
DiskXtenderW
Userid is formed from the host name and drive
MVS/ Tools
Host name
Netbackup
Host name
Networker
Host name
TSM w/o Gresham
Host name
TSM with Gresham
Configurable in the backup tool/host name
Access to unowned volumes
Unowned volumes are accessible within the entire VACS.
Conflicts are possible when backup tools want to use all visible volumes or when more than
one instance of a backup tool accesses a CentricStor.
Backup tool
Access to volumes
BS2000/Archive …
Only the volumes defined in
MAREN are used.
DataProtector
Access to owned and unowned
volumes.
DiskXtenderW
volumes.
MVS/ CSC
Volumes are assigned explicitly.
MVS/ LMS /CSMVS
Netbackup
volumes.
Networker
TSM w/o Gresham
TSM with Gresham
Access only to volumes of a defined scratch pool.
Consequence of use when
VACS contains unowned
volumes of other backup
tools
Not possible
415
9.12.3.4
Use of the Authorized Userid by customer applications
Example with NetBackup
Each master server has overall control of the volumes of its media servers.
A media server is always assigned to one customer. In terms of volume accesses, the media servers should be separated from each other. The master server can access all volumes
of its mefia servers.
The master server returns thevolumes to the VACS scratch pool as unowned when they have
been released.
Another media server fetches an unowned volume from the scratch pool. This media server
then becomes the owner of this volume.
This mechanism is implemented using the Netbackup tool robstat.
This is only possible for one instance CentricStor möglich.
Example with NetBackup or TimeNavigator
There are multiple applications.
Each application has a primary and a secondary master server.
Each master server is responsible for a number of media servers.
The VACS scratch pools are not used.
Multiple NetBackup and TimeNavigator instances access a CentricStor.
416
10 Installation of the GUI software GXCC/XTCC
General
10.0.1 Information about the installation CD
This installation guide is stored in the root directory of the CD-ROM in the following 3 files:
README.txt
README.unix
README.pdf
!
ASCII text for the display on MS Windows systems.
ASCII text for the display on UNIX-based systems.
PDF document for platform-independent display.
CAUTION!
The installation descriptions on the CD may be more up-to-date than the descriptions in this Integration Guide.
10.0.2 Information about restrictions and known bugs
Restrictions and known bugs are described in section “Restrictions and known bugs” on
page 438.
10.1 Installation descriptions
This CD-ROM can be used to install the GUI software required for the monitoring of a
CentricStor system. The GUI software was tested on the operating systems MS-Windows
95/98/NT/2000/XP, LINUX, SOLARIS, and SINIX-Z. The software to be installed includes
the base software Tcl/Tk and the GUI software components GXCC and XTCC. In the
following the procedures for installing the software packages on the various operating
systems are described.
417
Installation descriptions
Installation of the GUI software GXCC/XTCC
10.1.1 Installation on MS-Windows Platform
The operating systems supported are MS-Windows 95/98/NT/2000 and XP. On these
platforms the base software Tcl/Tk is integrated in the GUI software packet (GXCC and
XTCC). Versions of Tcl/Tk, including all associated links, that are already installed at the
time of installation, are not affected by the installation process per se. Any available configuration data in the file hosts.txt will automatically be saved.
i
On a multi-user system (such as MS-Windows NT/2000/XP), the installation and
deinstallation must be performed under an administrator account. However, the
programs can be started from any account via the menu Start. Certain administration functions, however, do require an administrator account.
Names of files and directories can be displayed by MS-Windows in different ways
(e.g. name.ext, Name.ext, NAME.EXT). This has, however, no significance.
Names of folders, window titles, button labels and message texts depend on the
language option of MS-Windows and may deviate from this description.
Information about unattended installation can be found in section “Unattended Installation
/ Deinstallation under MS-Windows” on page 434.
10.1.1.1
How to proceed
The installation should be conducted in the following manner:
1. Insert the CD-ROM into the CD drive, if not yet done.
2. Open the CD-ROM folder Windows and double click the file gui86en.exe using the left
mouse key.
The installation of the software starts.
A complete installation encompasses the following components:
418
●
Graphical User Interface: GUI software GXCC and XTCC
●
GXCC Observe Mode Shortcut: This is a symbol on the Desktop for calling GXCC in
Observe Mode
●
GXCC Demo (FALKE): Demonstration files for GXCC
●
CA Unicenter Integration Tools: Extensions in the CA Unicenter software for CentricStor
Using a selection window, it is possible to exclude specific components from the installation
process.
i
Should the tools required for the installation and deletion of CA-Unicenter extensions on MS-Windows NT/2000 Systems be needed, then the CA Unicenter
Integration Tools components must not be deselected.
By selection of the component GXCC Demo (FALKE) the snapshot files required for
the offline mode (refer to section “Offline Mode” on page 429) will be included.
During the installation of the GUI software, the user will be guided through the process by
means of various self explanatory dialogue windows. All individual windows containing the
buttons Next or Install must be acknowledged. The concluding window Setup has finished
installing... causes the installation to terminate successfully when the button Finish is
pressed.
10.1.1.2
Installation of the GUI documentation (optional)
The GUI software includes the capability to automatically access, provide and update the
online documentation for the CentricStor system being monitored. The documentation of
the GUI programs GXCC and XTCC can optionally be installed to ensure that it is accessible even when no connection has been established to a CentricStor system (offlinemode). Depending on actual availability it consists of the complete CentricStor service
and/or user manual or it consists of selected chapters from the service and/or user manual,
concerning the graphical user interface.
!
CAUTION!
Because the documentation will be copied into the folder doc of GXCC, it is
important to perform the following steps after the installation of the GUI software
(section “How to proceed” on page 418):
1. Insert the CD-ROM into the CD drive, if not yet done.
2. Open the CD-ROM folder Windows and double click the file doc86en.exe using the left
mouse key.
The installation of the documentation starts.
During the installation some self explanatory dialogue windows containing the buttons Next
or Install must be acknowledged. The concluding window Setup has finished installing...
causes the installation to terminate successfully when the button Finish is pressed.
419
10.1.1.3
Starting the GUI Software
A menu structure with the following functions is displayed via Start ➟ Programs ➟ Fujitsu
Siemens Computers ➟ V6 Control Center:
●
GXCC
–
–
–
●
XTCC
–
–
–
●
Add CentricStor to CA Unicenter
Delete CentricStor from CA Unicenter
SNMP Integration Liesmich
SNMP Integration Readme
Try to repair inoperable GXCC or XTCC
Uninstall the FSC V6 Control Center
Tools
–
–
–
420
XTCC Observe Mode
XTCC Service Mode
XTCC User Mode
Setup
–
–
–
–
–
–
●
GXCC Observe Mode
GXCC Service Mode
GXCC User Mode
Global Status (large)
Global Status (small)
Recorder
10.1.1.4
Creating the CA-Unicenter Extensions for CentricStor
During the installation of the GUI Software, various tools for the installation and deletion of
the CA-Unicenter extensions are installed provided that the CA Unicenter Integration Tools
components has not been deselected.
On a multi user system (MS-Windows NT/2000/XP), these tools can only be installed under
the account of the user (with administration privileges) who installed the GUI Software.
Guidance for the operation will be given by invoking Start ➟ Programs ➟ Fujitsu Siemens
Computers ➟ V6 Control Center ➟ Setup ➟ SNMP Integration Readme.
For the installation of the extensions the tool Start ➟ Programs ➟ Fujitsu Siemens Computers
➟ V6 Control Center ➟ Setup ➟ Add CentricStor to CA-Unicenter should be invoked. This tool
copies all files necessary for the operation of the CA-Unicenter to the appropriate directories.
By invoking Start ➟ Programs ➟ Fujitsu Siemens Computers ➟ V6 Control Center ➟ Setup
➟ Delete CentricStor from CA-Unicenter the extensions can be deleted.
10.1.1.5
Deinstallation of the Software
After invocation of Start ➟ Programs ➟ Fujitsu Siemens Computers ➟ V6 Control Center ➟ Setup
➟ Uninstall the FSC V6 Control Center a window with title FSC V6 Control Center (v6_cc)
Uninstall will be displayed asking "Are you sure that you want to completely
remove FSC V6 Control Center (v6_cc) and all of its components ?". Pressing
"Yes" starts the deinstallation of both, the GUI software and the documentation. By pressing
"No", deinstallation can be cancelled. Any available configuration data in the file hosts.txt
will automatically be saved.
Information about unattended deinstallation can be found in section “Unattended Installation / Deinstallation under MS-Windows” on page 434.
10.1.1.6
Configuration Data
During the course of the installation, a check is made as to whether the configuration data,
contained in the file hosts.txt, already exists in the associated directory. If this is not the
case, a search is made for configuration data which were saved during a possible previous
deinstallation process. If a previous version, in violation of the recommended procedures,
was not deinstalled and thus no configuration data was saved, then the configuration data
in the file hosts.txt must be copied manually from the directory
<Installation_path_old\xtcc\tmp> to <Installation_path_new\xtcc\tmp>.
421
10.1.2 Installation on a LINUX Platform
On this platform the base software Tcl/Tk is integrated in the GUI software packet (GXCC
and XTCC). Versions of Tcl/Tk that are already installed at the time of installation are not
affected by the installation process per se.
10.1.2.1
How to proceed
1. Insert the CD-ROM into the CD drive.
2. Mount the CD-ROM on the file system:
mount <directory for the CD drive>
Example: mount /media/cdrom
3. Select the LINUX directory on the CD-ROM:
cd <directory for the CD drive>/Linux
Example: cd /media/cdrom/Linux
4. List the content:
ls
Within the displayed file names following files are required for installing the GUI
software:
xtcc-<version>.i386.rpm
gxtcc-<version>.noarch.rpm
gxtcc-doc-<version>.noarch.rpm
5. Install these three packets in the following sequence:
a) rpm -i xtcc-<version>.i386.rpm
b) rpm -i gxtcc-<version>.noarch.rpm
c) rpm -i gxtcc-doc-<version>.noarch.rpm
422
10.1.2.2
GXCC and XTCC are started via command line input. The user can specify the operation
mode as start parameter. For GXCC the program /usr/local/bin/gxcc, and for XTCC
the program /usr/local/bin/xtcc should be invoked. The path name can be omitted, if
the directory /usr/local/bin is included within the search path for programs. Startup in
service mode, observe mode, or user mode is accomplished via options -service,
-observe, or -user. If no option is specified, the program is started in user mode.
Syntax of command line input:
/usr/local/bin/gxcc [-service | -observe] [&]
/usr/local/bin/xtcc [-service | -observe] [&]
10.1.2.3
Deinstalling the GUI Software
The deinstallation has to be performed under the user account root in the following
sequence:
1. rpm -e gxtcc
2. rpm -e xtcc
3. rpm -e gxtcc-doc
10.1.3 Installation on a SOLARIS Platform
The installation has to be performed under the user account root of the SOLARIS system.
On this platform the base software Tcl/Tk is integrated in the GUI software packet (GXCC
and XTCC). Versions of Tcl/Tk that are already installed at the time of installation are not
affected by the installation process per se. The installation has been tested with SPARC
SOLARIS Version 9 (english). In other SOLARIS versions the procedure may differ.
10.1.3.1
How to proceed
In case of operating the system via the CDE user interface a window File Manager will
be displayed automatically with the directory of the CD-ROM.
2. Open the directory Solaris by double clicking the icon of this directory with the left
mouse button.
423
3. Start the installation by double clicking the icon of the file Installer with the left mouse
button.
This will start an installation wizard, which guides the user via several dialog windows
through the installation process:
a) The windows Welcome and Local Selection have to be acknowledged via the Next
button.
b) In the window titled Product Selection the option Default Install should be used instead
of the default Custom Install, when the displayed product name is (XGXTCC). This
window has to be acknowledged via the Next button.
c) In the window Ready to Install the button Install Now starts the installation process of
the software. The progress is displayed during the installation process.
d) Completion is displayed in a window titled Installation Summary. Acknowledging this
window by pressing the button Exit closes the installation wizard.
4. Release the CD-ROM by invoking the function eject in the menu File of the window File
Manager.
As an alternative to the CDE user interface, the command line interface requires the
following procedure:
1. Select the directory of the CD-ROM:
cd <directory for the CD drive>
Example: cd /cdrom/cdrom0
2.
List the contents:
ls
3. Select the directory of the Solaris Platform:
cd Solaris
4. List the contents:
ls
5. Start the installation file:
./installer &
An installation wizard will be started, which guides the user via several dialog windows
through the installation process (as when starting the installation via the File Manager).
6. Release the CD-ROM via the command eject in the root directory.
424
i
10.1.3.2
If the installation is not successful because the package SMAWLskel was already
installed on the system, select the option Custom Install for installation and deselect
the package SMAWLskel in the list of installable packages.
mode as a start parameter. For GXCC the program gxcc, and for XTCC the program xtcc
should be invoked. Startup in service mode, observe mode, or user mode is accomplished
via options -service, -observe, or -user. If no option is specified, the program is started
in user mode.
gxcc [-service | -observe] [&]
xtcc [-service | -observe] [&]
10.1.3.3
Deinstalling the Software
The deinstallation has to be performed under the user account root. It consists of the
commands listed below.
After entering of each command the message "The following package is currently
installed:" will be displayed followed by additional information about the package. The
question "Do you want to remove this package?" should be answered with "y".
Then the following message will be displayed: "This package contains scripts which
will be executed with super-user permission during the process of
removing this package. Do you want to continue with the removal of this
package [y,n,?,q]?". This question has to be answered with "y".
1. pkgrm SMAWLbrk
2. pkgrm SMAWLglb
3. pkgrm SMAWLgdc
425
10.1.4 Installation on a SINIX-Z Platform
The installation has to be performed under the user account root. It includes the base
software Tcl/Tk and the GUI software GXCC and XTCC.
!
10.1.4.1
WARNING!
The installation is only intended for pure SINIX-Z platforms. On SINIX-2000-Z
machines (in particular SAE, CentricStor) the GUI software must not be installed
from of this CD-ROM. For these machines other officially released procedures exist
for installing the GUI software.
How to proceed
1. Insert CD-ROM into the CD drive.
2. Start the installation by invoking the following command:
cdinst
3. Follow the instructions within the displayed FMLI window:
a) Window 1 Process Multi-Product CD-ROM: Respond by pressing F3 (Save).
b) Window 2 CENTRICSTOR_GUI: Respond by pressing F8 (Continue).
c) Window 3 CENTRICSTOR_GUI: Item SINIX-Z CENTRICSTOR_GUI Graphic User
Interface (GUI) for CentricStor: Mark with F2 and accept by pressing the Enter key.
Then the following actions are displayed:
info
pkginfo
README
install
d) Select install and accept by pressing F3 (Enter).
e) Window 4 Install: The default values should be accepted by pressing F3 (Save).
The installation starts.
Installation is completed when the prompt "Press ENTER to continue" is displayed. After
pressing the Enter key, Window 3 will be displayed again, and has to be closed by pressing
F6. Window 4 should be closed by pressing F8 (Exit). This completes the processing of the
command cdinst.
426
10.1.4.2
mode as start parameter. GXCC is invoked via the program gxcc, XTCC via the program
xtcc. Startup in service mode, observe mode, or user mode is accomplished via options
-service, -observe, or -user. If no option is specified, the program is started in user
mode.
/usr/local/bin/gxcc [-service | -observe] [&]
/usr/local/bin/xtcc [-service | -observe] [&]
10.1.4.3
Deinstalling the Software
The deinstallation has to be performed under the user account root by invoking the
commands below in the given sequence.
After entering each command the message "The following package is currently
installed:" will be displayed followed by additional information about the package. The
question "Do you want to remove this package?" should be answered with "y".
1. pkgrm GlbXtcc
2. pkgrm BrkXtcc
3. pkgrm tcl
4. pkgrm GlbDoc
427
Online Documentation of the GUI Software
10.2 Online Documentation of the GUI Software
10.2.1 General
The GUI software includes the capability to automatically access, provide and update the
online documentation for the CentricStor system being monitored.
During the installation of the GUI programs GXCC and XTCC their documentation will also
be installed to ensure that it is accessible even when no connection has been established
to a CentricStor system (offline-mode). Depending on actual availability it consists of the
complete CentricStor service and/or user manual or it consists of selected chapters from
the service and/or user manual, concerning the graphical user interface.
10.2.2 Displaying the Documentation via the Help Function of the GUI
The Help menu of GXCC and XTCC contains an entry for the GUI online documentation,
the text of which depends on the operation mode the GUI has been started with. After
starting in service mode, an entry CentricStor <version> Service manual (complete) will be
displayed, if the complete service manual exists, or an entry CentricStor <version> Service
manual (GUI-Part) will be displayed, if only the chapters concerning the graphical user
interface are available.
In case of user mode and observe mode an entry CentricStor <version>User manual
(complete) will be displayed, if the complete user manual exists, or an entry CentricStor
<version>User manual (GUI-Part)) will be displayed, if only the chapters concerning the
graphical user interface are available. The service mode will be handled like the user and
observe mode if no service manual is available.
Invoking this function leads to the display of the service or user manual with a PDF viewer.
For this purpose a PDF viewer must be installed on the system:
–
–
–
–
On a MS-Windows platform: Acrobat Reader
On a LINUX platform: xpdf or acroread
On a Solaris platform: acroread
On a SINIX-Z platform: xpdf
!
428
CAUTION!
If the GUI software is started on a Linux system from a MS Windows system via Xserver, then the Online documentation display can cause the X-server to crash
when Acrobat Reader 4 is installed on the Linux system. This effect has not been
observed with Acrobat Reader 5.
Offline Mode
10.3 Offline Mode
Usually the display generated by the GUI software is based on data, which are periodically
received from an active CentricStor system. The communication partner within the active
system is the InfoBroker. For demonstration purposes the GUI software can take the data
from a file, and display the information of an inactive CentricStor system, described by these
data. This way of operation will be called offline mode in the following, the file will be called
a snapshot file.
When GXCC is running on a system which does not contain the InfoBroker, a window Mode
Select will be automatically displayed to the user, containing an option button for setting the
operation mode. Via the option File the user chooses the offline mode, and in the window
File Select the user may determine the snapshot file. The user may use the default snapshot
file or select a snapshot file from an arbitrary directory via the button Browse. After determining the snapshot file the GUI software displays the name of the CentricStor system
which is described by the snapshot file.
When GXCC is running on a system which contains the InfoBroker, the system described
will be displayed automatically. In order to choose in this case the offline mode one has to
invoke the function Open from the menu File of the GXCC window. Then the window File
Select will be displayed to the user, offering the functions described above.
During the installation of GXCC the directory TEST for snapshot files will be created. The
snapshot file gxtcc.gxd will be created in this directory. It is proposed as default in the
window File Select. Additional files are provided on the CD-ROM for demonstration
purposes. They have to be copied manually into the appropriate directory in order to use
them.
429
Offline Mode
10.3.1 Integrating the Snapshot Files
In the following the procedures for copying the snapshot files onto the various operating
platforms is described under the appropriate headings.
10.3.1.1
MS-Windows Platform
i
The following steps are only required, if during installation setup of the GUI software
the component GXCC Demo (FALKE) has been deselected; otherwise the additional
files are already present.
The installation is to be done as follows:
1. Insert the CD-ROM into the CD drive if not already done.
2. Open the Windows directory on the CD and double click the left hand mouse button on
the file gui86en.exe.
3. The displayed Installation directory must be incorporated using the Next button.
4. A window appears with the title Directory Exists followed by the message "The
directory '<Installation_directory>' already exists. Would you like
to install to that directory anyway ?" This question should be replied to in
the affirmative by means of "Yes".
5. By selecting the component GXCC Demo (FALKE), the additional installation of the
necessary snapshot files is prepared.
6. All subsequent windows are to be acknowledged with the Next or Install buttons.
7. In the final window Setup has finished installing... clicking on the Finish button concludes
the installation process.
10.3.1.2
LINUX Platform
1. Mount the CD-ROM on the file system:
mount <directory for the CD drive>
Example: mount /media/cdrom
2. Select the CD-ROM directory which contains the snapshot files:
cd <directory for the CD drive>/demo/TEST
Example: cd /media/cdrom/demo/TEST
3. Copy all snapshot files (including directories) into the directory prepared by GXCC:
cp -r * /usr/apc/gxtcc/TEST
430
10.3.1.3
Offline Mode
SOLARIS Platform
In case of operating the system via the CDE user interface a window File Manager will
be displayed automatically with the directory of the CD-ROM.
2. Open the directory demo by double clicking the icon of this directory with the left mouse
button.
3. Open the directory TEST by clicking the icon of this directory with the left mouse button.
4. Select all files and folders by invoking the function Select All in the menu Select within the
window File Manager of the CD-ROM.
5. Open a new window File Manager for the target for the snapshot files via the workspace
menu of the desktop (i.e. positioning the mouse pointer on the desktop background and
pressing the right mouse button). There the function File Manager has to be invoked
within the submenu entry Files.
6. Open the target directories /opt/SMAW/SMAWLglb/gxtcc/TEST, by opening sequentially all directories of this path by double clicking the icon of each directory with the left
mouse button.
7. Copy the highlighted snapshot files via drag&drop into the target directory. All
highlighted files implicitly are also transferred.
8. Close the window File Manager for the target of the snapshot files.
9. Release the CD-ROM by invoking the function eject in the menu File in the window File
Manager.
431
Offline Mode
As an alternative to the CDE user interface, the command line interface requires the
following procedure:
1. Select the directory of the CD:
cd <directory for the CD drive>
Example: cd /cdrom/cdrom0
2. List the content:
ls
3. Select the CD-ROM directory containing the snapshot files:
cd demo/TEST
4. Copy all snapshot files (including directories) into the directory prepared by:
cp -r * /opt/SMAW/SMAWLglb/gxtcc/TEST
5. Release the CD-ROM via the command eject in the root directory.
10.3.1.4
SINIX-Z Platform
1. Determining the device node of the CD drive:
ls /dev/dsk/*cdr*
2. Mount the CD-ROM on the file system of the system:
mount -F hs -o ro,dos <Device node of CD drive> /cdrom <Device node
of CD drive>
3. Select the CD-ROM directory containing the snapshot files:
cd /cdrom/demo/test
4. Copy all snapshot files (including directories) into the directory prepared by GXCC:
cp -r * /usr/apc/gxtcc/TEST
432
Offline Mode
10.3.2 Functionality in Offline Mode
The data of a snapshot file reflect either a snapshot or a maximum 2 hour period of the
history of a CentricStor systems. The covered time period determines whether the display
in the Global-Status-Monitor is static or dynamic. In case of a static display the picture does
not change, since the data only reflect a single point in time. In case of a dynamic display
the picture is updated periodically, according to the data which correspond to the period
currently reflected.
Both kinds of snapshot files can be distinguished by the name suffix. A file with the suffix
gxd contains a single snapshot only, whereas a file with the suffix db covers a whole period.
10.3.2.1
Static Display
Starting GXCC in offline mode will always display a static picture of a CentricStor system.
For each ISP in the display there is a function menu provided containing the function Show
Details (XTCC), which opens a XTCC window in offline mode and displays a static picture
of the concerned ISP.
In the menu Tools of the GXCC menu bar the Global-Status-Monitor can be started. If there
is only one snapshot file of type gxd of the concerned system (i.e. there is no additional file
*.db), the stored operational data are only displayed in a static picture. The display of
performance data is not included, because it only reflects a snapshot.
10.3.2.2
Dynamic Display
If a snapshot file of type db exists for the system already being displayed in GXCC, then the
GXCC-Recorder tool will be activated when the Global-Status-Monitor is started in offline
mode. This tool delivers to the Global-Status-Monitor periodically the operational data
which are stored in the snapshot file for the concerned time period. The Global-StatusMonitor updates the display according to the data delivered. When operational data
changes, changes become visible in the picture displayed by the Global-Status-Monitor, but
not in GXCC.
The tool GXCC-Recorder also supports the sequential display of snapshot files of different
systems (this is called ROTATE mode). In order to do so the user has to select the corresponding snapshot files of type db within the application window of the GXCC-Recorder.
When a snapshot file changes, then the GXCC display changes also.
433
Installation of the GUI software
10.4 Unattended Installation / Deinstallation under MS-Windows
10.4.1 Setup Command Line Parameters
The Setup programs gui86en.exe / doc86en.exe accept the following command line
parameters:
/SILENT
The wizard and the background window are not displayed. The installation progress
window is displayed. Error messages during installation are displayed.
/VERYSILENT
The wizard, the background window, and the installation progress window are not
displayed. Error messages during installation are displayed.
/SUPPRESSMSGBOXES
Instructs Setup to suppress message boxes. Only has an effect when combined with
/SILENT and /VERYSILENT.
/DIR=x:\dirname 1
Overrides the default directory name normally displayed on the Select Destination
Directory wizard page. A fully qualified pathname must be specified. Don't forget to use
quotes if the dirname contains spaces.
/COMPONENTS=comma_separated_list_of_component_names 1
Overrides the default components setting Complete Installation. Using this command line
parameter causes Setup to automatically select Customized Installation type.
i
This parameter is only valid for gui86en.exe. The component gui must always
be included in the comma separated list.
Component names used for the CentricStor GUI:
gui
ico
dem
uni
1
Graphical User Interface
GXCC Observe Mode Shortcut
GXCC Demo (FALKE)
CA Unicenter Integration Tools
optional
434
Unattended Installation / Deinstallation under MS-
/SAVEINF=filename 1
Instructs Setup to save installation settings to the specified file. Don't forget to use
quotes if the filename contains spaces.
SAVEINF file example:
[Setup]
Dir=C:\Programme\FSC 2
Group=Fujitsu Siemens Computers
NoIcons=0
Components=gui,ico,dem,uni
The Dir entry can be used to locate C:\Programme\FSC\v6_cc\unins000.exe 2 in
case of unattended uninstall.
/LOADINF=filename 1
Instructs Setup to load and re-use the settings from the specified file after having
checked the command line. This file can be prepared using the /SAVEINF parameter
explained above. Don't forget to use quotes if the filename contains spaces.
10.4.2 Setup Exit Codes
0
Setup was successfully run to completion.
1
Setup failed to initialize.
2
The user clicked Cancel in the wizard before the actual installation started, or chose No
on the opening This will install... message box.
3
A fatal error occurred while preparing to move to the next installation phase (for
example, from displaying the pre-installation wizard pages to the actual installation
process). This should never happen except under the most unusual of circumstances,
such as running out of memory or Windows resources.
4
A fatal error occurred during the actual installation process.
i
Errors that cause an Abort/Retry/Ignore box to be displayed are not fatal errors.
If the user chooses Abort at such a message box, exit code 5 will be returned.
5
The user clicked Cancel during the actual installation process, or chose Abort at an
Abort/Retry/Ignore box.
6
The Setup process was forcefully terminated by the debugger (Run or Terminate used in
IDE).
1
optional
2
pathname of the default directory
435
Installation of the GUI software
Before returning an exit code of 1, 3, or 4, an error message explaining the problem will
normally be displayed. Future versions may return additional exit codes, so applications
checking the exit code should be programmed to handle unexpected exit codes gracefully.
Any non-zero exit code indicates that Setup was not run to completion.
10.4.3 Uninstaller Command Line Parameters
The uninstaller program unins000.exe accepts the following command line parameters:
/SILENT
When specified, the uninstaller will neither ask the user any questions nor display a
message stating that uninstall is complete. Shared files that are no longer in use are
deleted automatically without prompting.
Any critical error messages will still be shown on the screen. The uninstallation progress
window is displayed.
/VERYSILENT
When specified, the uninstaller will neither ask the user any questions nor display a
message stating that uninstall is complete. Shared files that are no longer in use are
deleted automatically without prompting.
Any critical error messages will still be shown on the screen. The uninstallation progress
window is not displayed.
/SUPPRESSMSGBOXES
Instructs the uninstaller to suppress message boxes. Only has an effect when combined
with /SILENT and /VERYSILENT.
10.4.4 Uninstaller Exit Code
The uninstaller will return a non-zero exit code if the user cancels or a fatal error is encountered. Programs checking the exit code to detect failure should not check for a specific nonzero value; any non-zero exit code indicates that the uninstaller was not run to completion.
Note that at the moment you get an exit code back from the uninstaller, some code related
to uninstallation might still be running. Because Windows doesn't allow programs to delete
their own EXEs, the uninstaller creates and spawns a copy of itself in the TEMP directory.
This clone performs the actual uninstallation, and at the end, terminates the original
uninstaller EXE (at which point you get an exit code back), deletes it, then displays the
uninstall complete message box (if it hasn't been suppressed with /SILENT or
/VERYSILENT).
436
Unattended Installation / Deinstallation under MS-
10.4.5 Setup Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current
Version\Uninstall\FSC V6 Control Center_is1
...
UninstallString REG_SZ
C:\Programme\FSC\v6_cc\unins000.exe 1
10.4.6 GUI Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current
Version\Uninstall\FSC V6 Control Center
ADMIN_USER REG_SZ ?
GXTCC_HOME REG_SZ C:\Programme\FSC\v6_cc\gxtcc 1
XTCC_HOME REG_SZ C:\Programme\FSC\v6_cc\xtcc
1
TCLSH REG_SZ C:\Programme\FSC\v6_cc\xtcc\osd\Windows\tclsh.exe 1
WISH REG_SZ C:\Programme\FSC\v6_cc\xtcc\osd\Windows\wish.exe 1
1
pathname of the default directory
437
Restrictions and known bugs
10.5 Restrictions and known bugs
Depending on the XTCC version used, the following error messages may occur while
executing the function XTCC Update / Revert. These messages can be ignored because the
listed files and directories are not required.
Instead of the recommended actions the function should be finished by pressing the Cancel
button.
Message while executing “XTCC Update”
Extraction failed <
tar: osd/Linux/i486: Cannot open: File exists
tar: Error exit delayed from previous errors>
Update failed
The application directory could be inconsistent
=> Try again "Update"
If the failure persists:
=> Re-Install manually using the Basic version CD
Message while executing “XTCC Revert”
Recursive copy failed <
cp: cannot overwrite directory '/usr/apc/xtcc/./osd/Linux/i486'
Revert failed
The application directory could be inconsistent
=> Try again "Revert"
If the failure persists:
=> Re-Install manually using the Basic version CD
438
with
with
with
with
with
with
non-directory
non-directory
non-directory
non-directory
non-directory
non-directory>
11 Important information regarding the
CentricStor environment
This chapter is designed to address and show how to rectify familiar problems in the
CentricStor environment. The information is intended for service personnel and
consultants.
●
NetApp filers crash during update installation of CentricStor
With the current status of the NetApp filers, deactivation commands must be entered
before you reboot the ICP so that the filer survives this reboot. Activation is required
after this reboot.
439
Abbreviations
Abbreviation Full name
Explanation
AL
Arbitrated Loop
Fibre Channel operating mode, also
abbreviated to FCAL
ACF
Automatic Cartridge Facility
ACI
AML Client Interface
Interface to the ABBA Robot via DAS
ACS
Automatic Cartridge System
StorageTek Library
ACSLS
ACS Library Server (or Software)
controls the StorageTek libraries
ADIC
Advanced Digital Information Corporation
AML
Automated Media Library
ADIC name for libraries
AMU
AML Management Unit
PC to monitor the AML Robot including
the library
CNC
ESCON channel operating mode
CS
CentricStor
CSC
StorageTek Library Component
StorageTek Library Interface
CTL
Controller Target LUN
complete SCSI address
CU
Control Unit
DA
Device Adapter
DAS
Distributed AML Server
DDM
Disk Drive Module
DFHSM
IBM: Data Facility Hierarchical Storage
Manager
DFRMM
Interface to monitor the AML robot (open
systems)
Component of DFHSM
DPO
Data Path Optimizer
DTVFS
Distributed Tape Volume File System
EMTAPE
Tape emulation in CentricStor
ERP
Error and Recovery Procedure
441
Abbreviations
Explanation
ESCD
ESCON Director
ESCM
ESCON Manager
ESCON
Enterprise System Connection
ESS
Enterprise Storage Server
FBA
Fixed Block Architecture
FC
Fibre Channel
FCAL
Fibre Channel Arbitrated Loop
FCH
Fibre Channel Hub
FCIP
Fibre Channel over IP
FCP
Fibre Channel Protocol
FCS
Fibre Channel Switch
FSC
Fujitsu Siemens Computers
GB
Gigabyte
GXCC
Global Extended Control Center
graphical user interface of CentricStor
V3.0 for servicing, maintaining and
monitoring
GXTCC
Global Extended Tape Control Center
graphical user interface of CentricStor
V2.1 for servicing, maintaining and
monitoring
GUI
Graphical User Interface
Collective description for GXTCC/XTCC/
Global Status
HA
Host Adapter
Fibre channel or ESCON adapter in
CentricStor
HACC
Host access of ABBA/x in the MVS
corresponds to ROBAR in BS2000
HBA
Host Bus Adapter
here: FC adapter on the host
HCC
Host Control Component
Software running on MVS for AML
access.
HCD
Hardware Configuration Definition
HDD
Head and Disk Drive
HSC
StorageTek: Host Software Component
442
FC link via hub or loop
Internet-protocol-based storage
networking technology (RFC 3821) which
enables FC data to be tunneled over IP
networks.
MVS (or BS2000) program to control ACS
robots, comparable to ROBAR-CL
Abbreviations
Explanation
ICP
Integrated Channel Processor
Processor in CentricStor which contains
the FC or ESCON host adapter
IDP
Integrated Device Processor
Processor in CentricStor connected to
real cartridge drives
IML
Initial Microcode Load
IODF
I/O Definition File
IOS
Input Output Supervisor
IPL
Initial Program Load
ISP
Integrated Service Processor
JCL
Job Control Language
KB
Kilobyte
LAN
Local Area Network
LCU
Logical Control Unit
LD
Logical Drive
LM
Library Manager
LP
Logical Path
LPAR
Logical Partition
LMU
StorageTek: Library Management Unit
Central control for operating up to 16 LSM
LSM
StorageTek: Library Storage Module
Silo including robot
LSS
Logical SubSystem
LUN
Logical Unit Number
Device accessible via an SCSI (or FCSCSI) target
LV
Logical Volume
Also called virtual volume. Uncompressed
capacity 895MB, corresponding to the
emulated drive 3490E.
MAREN
Magnetic tape management in BS2000
MTU
Maximum Transmit Unit
NAS
Network Attached Storage
File servers which provide storage capacity in an IP network.
The Network Data Management Protocol
(NDMP) is generally used for communication between backup software and a
file server via the TCP/IP protocol stack.
NDM
Nucleus Device Management
Device Management of BS2000
Overall term for processors in CentricStor
emulated tape drive in an ICP
443
Abbreviations
Explanation
NDMP
Network Data Management Protocol
Standardized interfaces at application level (Layer 7 of the OSI Reference Model)
for data transfer and backup control in the
NAS environment
PDS
Physical Device Server
Process in the IDP for operating a real
drive
PLS
Physical Library Server
Process for operating a real library in
CentricStor
PTF
Program Temporary Fix
RAID
Redundant Array of Independent (originally:
Inexpensive) Disks
ROBAR
Robot Archive
The ROBAR-SW makes it possible for
BS2000 to communicate with an AML/x
tape library
ROBAR-CL
ROBAR Client
ROBAR-SW in BS2000
ROBAR-SV
ROBAR Server
ROBAR software on SINIX computer
SAN
Storage Area Network
Memory network supported by FC
SCSI
Small Computer Systems Interface
SDD
SubSystem Device Driver
SNMP
Simple (or Standard) Network Management
Protocol
SPARC
Scalable Processor Architecture
SS
SubSystem
SSID
SubSystem IDentification
UCB
Unit Control Block
VACS
Virtual ACS
Emulation of an ACS in CentricStor
VAMU
Virtual AML Management Unit
AMU Emulation in CentricStor
VDAS
Virtual DAS
Emulation of a DAS in CentricStor
VLP
Virtual Library Processor
ISP in CentricStor in which VLM, PLM
and different central processes run. In
several models together with IDP
VOLSER
Volume Serial Number Name of a Volumes
VPD
Vital Product Data
444
Name of the RISC architecture used by
SUN
Abbreviations
Explanation
VSN
Volume Serial Number
VTOC
Volume Table of Contents
MM
CentricStor maintenance manual
WLM
Workload Manager
WWNN
World Wide Node Number
Number of an FC node
WWPN
World Wide Port Number
Number of an FC port (for FC nodes with
several ports)
XRC
Extended Remote Copy
XTCC
Extended Tape Control Center
User interface for ISP
445
by f.f. 1992
Related publications
Ordering manuals
The manuals are available as online manuals, see http://manuals.fujitsu-siemens.com, or
in printed form which must be payed and ordered separately at
http://FSC-manualshop.com.
[1]
CentricStor Maintenance Manual (also available as an online manual from CentricStor 2.1
onwards).
[2]
BS2000/OSD-BC V#.## Introduction to System Support *)
[3]
MAREN V#.## (BS2000/OSD) MAREN for Administrators *)
[4]
MAREN V#.## (BS2000/OSD) MAREN for Users *)
[5]
ROBAR V#.## (BS2000/OSD, Reliant UNIX, Solaris) Tape Cartridge Archiving System *)
[6]
IBM Magstar Virtual Tape Server: Planning, Implementing, and Monitoring
(SG24-2229-05) **)
[7]
BS2000/OSD-BC V#.## System Installation *)
[8]
BS2000/OSD-BC V#.## Commands (several volumes) *)
[9]
StorageTek User Guide BS2000 CSC Version 6.2
[10]
ADIC Manual for HCC
[11]
StorageTek Manual, Client System Component for MVS, Systems Programmer Guide,
Release 4.0, 31343480
[12]
User Guide SX Series Business Servers - Operation and Administration
Order Number: U41272-J-Z385-2-76
The manuals marked with *) are available on the BS2000/OSD manual server at:
http://manuals.fujitsu-siemens.com/mainframes.html. “#.##” shows the version number
available on your host.
447
Literatur
The manuals marked with **) are IBM Redbooks available from:
http://publib-b.boulder.ibm.com/Redbooks.nsf/portals/
The current version is offered here. The order number gives the version number after the
second hyphen (“-”).
448
Environmental Protection
Returns, Recycling and Disposal
Details on the return and recycling of devices and disposables in the European area can be
obtained from your Siemens dealer or from our Recycling Center in Paderborn, Germany:
Tel.
Fax.
Germany 05251 8180-10
Germany 05251 8180-15
Further information on environmental protection
The Environment Affairs Manager for Siemens AG will be happy to answer any questions
on environmental protection.
Siemens AG
Environmental Protection Office
Werner von Siemens Straße 6
86159 Augsburg, Germany
Tel.
Fax.
Germany 0821 599-2999
Germany 0821 599-3440
449
by f.f. 1992
Index
/390 firmware
46
A
ACS
NetBackup 245
permitted configurations
ACSLS 341
communication 371
Networker 231
Server Networker 223
ADIC library 38
AIX
device nodes 206
limitations 202
settings and info 202
useful commands 203
AMU PC 364
applications
limitations 27
B
backup times 266
BIOS settings 385
block length
maximum 27
block size 57
Brocade 374
Brocade Silkworm 44
BS2 tapes 51
BS2000 partition 46
BS2000/OSD 46
BSD
Solaris 240
24
C
CA1 140
Cashion connection 372
cbn nodes 245
Celerra 215
CentricStor configurations 23
changer 341
Cisco Switch 397
cleaning management
StorageTek libraries 369
cloning 213
cmd_proc
STK libraries 223, 370
CommVault Galaxy 347
compressed WWN
Reliant UNIX 162
compression 58
Linux 8.0 156
NetApp 340
NetBackup 260
Networker 239
switch off NT 237
Windows 238
configuration
LANfree 317
Linux client 319
Linux Storage Agent 319
logical drives in z/OS 64
Networker 222
SAN environment 320
TSM server 320
configuration data
CentricStor 361, 362
configuration tools
UNIX systems 361
451
Index
Connectrix McData 44
control port
Networker 222
control unit
BS2000 30
coordinates
virtual drives 79
CSC 73
StorageTek 40
to BS2000 40
CSMVS 95
D
DAS
NetBackup 245
Networker 232
permitted configurations 25
DAS client 364
DAS server 364
DASADMIN
in CentricStor 364
in host 364
Data Protector 184, 263
Datamover 215
LP10000 185
device count
Networker 223
device depot 37
device name 42
device nodes
AIX 206
missing 155
Reliant UNIX 162, 163
rewind 206
Solaris 170
device sharing 58
devices
Networker 222
DFSMSrmm 126
diagnostic documentation 59
diagnostics
performance problems 383
452
DiskXtender for Windows 341
configuration 344
configuration in CentricStor 341
Installation 344
driver
AIX 3590 202
AIX OST 202
Linux Adaptec 160
Linux EMULEX 152
Linux ST 157
Linux Symbios 160
NT 209
NT QLA2200F 209
Rel UNIX LP8000 161
Solaris EMULEX 170
Solaris NetBackup 184
dsmadmc 320
E
eject sleep
Networker 222
EMLXemlxu 185
EMTAPE 42
Emulex Fibre Channel driver
Emulex HBAs 185
EMULEX LP8000
Linux RedHat 151
Linux SuSE 152
Linux Suse 152
Reliant UNIX 161
Solaris 167
extended drive 341
185
F
fast mount 232
FC connections
special features 373
FC switch
IP addresses 362
permitted types 373
FCIP connection 397
firmware download 385
fixed block length mode 28
Fujitsu libraries 373
Index
G
GENTAB 42
Gresham 317
H
HACC 102
HAL 46
HBA 384
HCD 63
host systems
limitations
HSC 147
HSI 57
27
I
IBMTape driver 318
ICP reboot
Networker 224
ICP sharing 374
Idle_Device_Timeout
Networker 222
installation
GUI software 417
IOGEN 46
IP addresses
display 362
FC switch 362
ISP 362
libraries 362
ISP
IP addresses 362
K
kernel building
Linux 160
L
L180
import tapes 369
LANfree configuration 317
LANfree data transfers
verification 322
Leadville driver 185
Legato (EMC) 341
LibAttach
NT 4.0 237, 257, 298
Windows 238, 258, 299
libraries
IP addresses 362
library device name
CentricStor 42
limitations
AIX 202
through application 27
through host 27
links
on LD 164
shell script for creating links
Linux client
configuration 319
Linux Storage Agent
configuration 319
lmadmin 373
LMF 246
load sleep
Networker 222
logging
UNIX systems 361
logical drives
configuration in z/OS 64
long distance 397
LP11000 185
LP9002L 185
LP9802 185
lpfc 185
lpfc.conf
Solaris 174
lpfc/qla driver 185
164
M
MAREN
BS2000 32
MDS-9000 family 397
media family
Networker 231
media type
Networker 231
MediaStor 344
453
Index
model
Networker 222
more than 8 LUN
Windows 2000 211
MPxIO 185
N
NAS systems 213
NCS 73
NDM
BS2000 37
NDMP 213
NetApp 213
NetApp-Filer 439
NetBackup
Java 245
Solaris extensions 184
Networker 221
NetWorker backup node 230
no rewind 163
non-rewind 157, 159, 257, 259, 260, 261, 262,
299, 300, 340
NT 4.0 209
number of devices 57
O
ommVault 347
options element status
Networker 224
P
PDS
display 363
performance problems
diagnostics 383
permitted configurations
ACS 24
DAS 25
VJUK 26
persistent binding
Solaris 172
physical volumes
sharing 21
454
PLP 373
PLS
display 363
port zoning 374
Powderhorn
extend 368
import tapes 369
PSR 59
Q
QL2200
error messages 210
qla 185
QLA2200F
NT 209
Qlogic Fibre Channel driver
Qlogic QLA2200F
Linux RedHat 152
Linux Suse 7.1 152
Linux Suse 8.0 153
185
R
real drive
sharing 21
real robot
sharing 21
reconfiguration boot 46
Reliant UNIX 161
restrictions
Networker 226
rewind
device nodes 206
RFC 3821 397
RMM 126
ROBAR 38
rpm packages 317
S
S servers 60
SAN environment
configuration 320
scratch mount 232
session rest time
NT 210
Index
settings and info
AIX 202
NT 4.0 210
Solaris 166
Windows 2000 212
SFS 185
SFS software package 185
SFS/Leadville driver 185
sharing
physical volumes 21
real drives 21
real Robot 21
Silkworm 374
SMAWdevsp 185
SMAWLskel 425
SMIT 317
Solaris
requirements 165
st.conf 180
SPARC64 mode 46
ssi daemon 369
st.conf
Solaris 180
startup sequence
fibre channel 373
STL device names
Networker 222
STL interface lib
Networker 222
storage location 30
storage networking technology 397
StorageTek libraries 40, 368
SUN StorEdge SAN Foundation Software 185
Sun/QLogic HBAs 185
SX servers 44
System Management Interface Tool 317
T
Tape 221
tape driver ST
Linux 157
Solaris 169
tapeutil 207
telnet 383
TIVsm-API 317
TIVsm-BA 317
TIVsm-stagent 317
TIVsm-tsmscsi 317
TLMS 140
traces
UNIX systems 361
TSM documentation 323
TSM server
configuration 320
U
UGEN
BS2000 30, 42
UNIX device nodes 164
unload sleep
Networker 222
V
VACS 42, 341
CentricStor 42
coordinates of the device 223
NetBackup 245
server 239
VAMU 42
CentricStor 42
VDAS
TIMEOUT_MOVE Networker 223
verification
LANfree data transfer 322
virtual devices
Networker 230
virtual drives
coordinates 79
virtual libraries
display 363
VJUK
configuration 288
configuring a SCSI library on AIX 312
emulation 338
permitted configurations 26
vjukadmin 312, 316, 338
455
Index
volume default capacity
Networker 231
VTD emulation 28
W
Windows 2000
Windows 2000/2003 211
WSA 46, 52
WWNN
display 363
zoning 374
WWPN
display 363
X
X2000 46
X6767A 185
X6768A 185
Z
z/OS 63
zoning
configuration examples
FC switch 162
ICP sharing 374
rules 374
456
376
Information on this document
On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
This document from the document archive refers to a product version which
was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have
been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the format …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at
http://ts.fujitsu.com/...
and the user documentation at http://manuals.ts.fujitsu.com.
Copyright Fujitsu Technology Solutions, 2009
Hinweise zum vorliegenden Dokument
Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von
Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine
bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche
Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden
Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions
angeboten und haben die Form …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009

Integration Guide CentricStor VT V3.1D

Transcription

Similar documents

Basic map of China - ellenjmchenry.com

stuck on you - Mark Khaisman

Students use AutoSketch software to complete the design of a home

Build a Winning Partner Program

Correction Tape E-blast for Highland Group_July 2014

Auto Tape Dispenser EZ-9000 GR

MONO CORRECTION TAPE REFILLABLE

Table Kushion #5050... copy

TECH-MASTERS: Novatex Tape

CUBBI