ETERNUS CS Highend - Fujitsu manual server

Transcription

Integration Guide - English
ETERNUS CS Highend
Integration Guide
Integration of the ETERNUS CS HE into the Storage Infrastructure
Edition 2011-05-02
Comments… Suggestions… Corrections…
The User Documentation Department would like to know your
opinion on this manual. Your feedback helps us to optimize our
documentation to suit your individual needs.
Feel free to send us your comments by e-mail to:
manuals@ts.fujitsu.com
Certified documentation
according to DIN EN ISO 9001:2008
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:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © Fujitsu Technology Solutions GmbH 2011.
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
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5
Preparatory considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2
Summary of permitted configurations . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1
ETERNUS CS HE configurations with BS2000 . . . . . . . . . . . . . . . . . . . . 23
2.2
ETERNUS CS HE configurations with z/OS
2.3
Configurations with ETERNUS CS HE in the SAN environment
2.4
Restrictions from the application program side . . . . . . . . . . . . . . . . . . . 23
2.5
Restrictions for server farms using Open Systems . . . . . . . . . . . . . . . . . 24
2.6
General information on Open Systems . . . . . . . . . . . . . . . . . . . . . . . . 24
3
ETERNUS CS HE in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
Miscellaneous . . . . . . . . . . . . . .
Asynchronous tape processing with SYNC
Configuration of logical drives in BS2000 .
Activities in UGEN . . . . . . . . . . . . .
Activities in MAREN . . . . . . . . . . . .
Further preparatory activities in MAREN .
Activities in NDM . . . . . . . . . . . . . .
Activities in ROBAR-CL and ROBAR-SV .
Integration Guide ETERNUS CS HE 2011-05-02
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . 23
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . 23
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
25
26
26
28
31
34
35
3
Contents
3.1.8
3.1.8.1
3.1.8.2
3.1.9
3.1.10
Activities in BS2000-CSC . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . .
Activities in ETERNUS CS HE: EMTAPE, VAMU/VACS
Multiple ETERNUS CS HE systems . . . . . . . . . . . .
DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
37
37
39
40
40
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 ETERNUS CS HE . . . . . .
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
41
41
41
41
43
43
43
44
54
56
56
3.3
3.3.1
3.3.2
3.3.3
ETERNUS CS HE on S servers
Firmware/software statuses . . .
Connection and configuration . .
Restrictions . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
57
57
58
59
3.4
3.4.1
3.4.2
3.4.3
ETERNUS CS HE on an SQ server . . . . . . . . . .
Configuration in ETERNUS CS HE . . . . . . . . . . .
Connection between ETERNUS CS HE and SQ servers
About the software configuration on the SQ server . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
60
60
60
61
4
ETERNUS CS HE 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 Configuration . . . . . . . . . . . . . .
Virtual Drive Sharing . . . . . . . . . . . . . . . . . .
Representation of Virtual Drives in ETERNUS CS HE
Logical Volume Definition . . . . . . . . . . . . . . .
VACS Interface . . . . . . . . . . . . . . . . . . . . .
4
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
64
65
65
66
67
68
69
70
Contents
4.4
4.4.1
4.4.2
Host Software Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Allocation Influencing and Scratch Subpooling . . . . . . . . . . . . . . . . . . . . . 72
Message Processing and Automation . . . . . . . . . . . . . . . . . . . . . . . . . . 73
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
NCS/CSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Installation and Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Virtual Drives Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Scratch Subpooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Scratch Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
ETERNUS CS HE NCS/CSC network attachment via firewall in a z/OS environment
93
CSC Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
CSMVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Sample configuration for ETERNUS CS HE, LMS/CSMVS with FS5193 gateway . 97
LOAD balancing with LMS/CSMVS . . . . . . . . . . . . . . . . . . . . . . . . 101
Scratch alignment between RMM/CA-1 and ETERNUS CS HE for LMS/CSMVS 102
Setting manual scratch for ETERNUS CS HE from the host . . . . . . . . . . . 102
HACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Installation and Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
HACPARM1 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
HACC ARCHIVE initialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
HACC Scratch Synchronisation Process . . . . . . . . . . . . . . . . . . . . . 126
HACC Volume Initialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
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 . . . .
4.7
Host Software Component - HSC . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.8
Library Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
4.9
User Exits and Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
127
127
127
127
140
141
141
142
142
143
143
144
147
5
Contents
5
ETERNUS CS HE on UNIX-type systems . . . . . . . . . . . . . . . . . . . . . . 153
5.1
5.1.1
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
Linux . . . . . . . . . . . . . .
EMULEX controller . . . . . . .
Qlogic QLA2200F Controller . . .
RedHat LINUX . . . . . . . .
SuSE Linux 8.0 Professional
SuSE SLES 9.0 . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
153
153
153
153
153
156
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
5.2.10
5.2.11
5.2.12
5.2.13
5.2.14
5.2.15
5.2.15.1
5.2.15.2
5.2.15.3
5.2.15.4
5.2.16
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . .
Useful commands and URLs . . . . . . . . . . . . . . .
Important settings and information . . . . . . . . . . . .
Driver for EMULEX . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . .
HBAnyware . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
156
156
157
157
159
160
161
163
165
166
167
167
173
177
177
177
177
180
190
195
195
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
HP-UX . . . . . .
General . . . . .
Restrictions . . .
Useful commands:
Links . . . . . . .
Device nodes . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
196
196
196
196
196
197
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.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 . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
198
198
198
199
200
202
203
204
6
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
6
ETERNUS CS HE in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.1
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.2
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . 206
7
ETERNUS CS HE on NAS systems . . . . . . . . . . . . . . . . . . . . . . . . . 207
7.1
General information on saving using NDMP . . . . . . . . . . . . . . . . . . . . 207
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
NetApp . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . .
Configuration in ETERNUS CS HE . . .
Useful commands . . . . . . . . . . . .
Update Installation in ETERNUS CS HE
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
207
207
207
208
208
208
7.3
7.3.1
7.3.2
7.3.3
7.3.3.1
7.3.3.2
7.3.4
Celerra . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . .
Configuration in ETERNUS CS HE . . . . . . . .
Configuration of Celerra . . . . . . . . . . . . . .
Useful commands, to be executed on the control node
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
209
209
209
209
209
210
212
8
Tape management systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
8.2
8.2.1
8.2.2
NetWorker (EMC and Fujitsu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
8.3
8.3.1
8.3.2
8.3.3
8.3.3.1
8.3.3.2
8.3.3.3
8.3.3.4
8.3.4
8.3.4.1
8.3.4.2
NetBackup (Symantec) . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . .
LMF configuration . . . . . . . . . . . . . . . . . . .
Connection of the robot controller (VACS) via a firewall
Template for supporting SCRATCH mount . . . . . .
Sample screens . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . .
Windows 2003 . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
218
218
218
219
221
222
223
224
238
238
239
7
Contents
8.3.4.3
8.3.4.4
8.3.4.5
8.3.4.6
8.3.4.7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
239
239
240
242
242
8.4
8.4.1
8.4.2
8.4.3
8.4.4
8.4.4.1
8.4.4.2
8.4.4.3
8.4.4.4
8.4.4.5
8.4.4.6
8.4.4.7
8.4.4.8
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.5.7
8.4.6
8.4.6.1
8.4.6.2
8.4.6.3
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
Data Protector . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . .
Licenses . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . . .
Installation in UNIX systems . . . . . . . . . . . . . . .
Installation of Data Protector . . . . . . . . . . . .
Configuration of ETERNUS CS HE 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 . . . . . . . . . . . . . . . . . .
VJUK configuration . . . . . . . . . . . . . . . . . . .
Supported slots . . . . . . . . . . . . . . . . . . .
Autoconfiguration . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . .
DAS interface . . . . . . . . . . . . . . . . . . . .
ACS interface . . . . . . . . . . . . . . . . . . . .
Autolabeling . . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . .
Windows . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
243
243
243
243
244
244
244
245
246
246
253
259
265
270
270
270
270
270
271
271
272
279
279
279
279
280
280
281
281
282
283
283
8.5
8.5.1
8.5.2
8.5.2.1
8.5.2.2
8.5.2.3
Tivoli / TSM . . . . . . . . .
Documentation . . . . . . . .
Installation and configuration
TSM installation . . . . .
TSM configuration . . . .
Special parameters . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
284
284
284
284
285
288
8
Reliant UNIX
Solaris . . .
HP-UX . . .
IBM-AIX . .
Linux . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
8.5.2.4
8.5.3
8.5.3.1
8.5.3.2
8.5.3.3
8.5.3.4
8.5.4
8.5.4.1
8.5.4.2
8.5.4.3
8.5.5
8.5.5.1
8.5.5.2
8.5.5.3
8.5.5.4
8.5.5.5
8.5.5.6
8.5.6
8.5.7
8.5.7.1
8.5.7.2
8.5.7.3
8.5.7.4
8.5.7.5
8.5.7.6
Examples . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration with Gresham EDT . . . .
Gresham 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 2000 . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
288
289
290
290
294
295
297
297
298
301
302
302
302
303
306
307
307
307
308
308
308
308
309
309
309
8.6
8.6.1
8.6.2
8.6.3
8.6.4
8.6.4.1
8.6.4.2
8.6.5
CA ARCserve Backup . . . . . . . . . .
ARCserve . . . . . . . . . . . . . . . . .
ETERNUS CS HE . . . . . . . . . . . . .
Backup server . . . . . . . . . . . . . . .
Startup and configuration of virtual libraries
Configuring a SCSI library (VJUK) . .
Using an ACSLS library . . . . . . . .
Import or export under ARCserve . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
310
310
310
311
311
311
312
312
8.7
8.7.1
8.7.2
Time Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
8.8
VJUK emulation
8.9
NAS filer - NetApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
8.10
8.10.1
8.10.1.1
DiskXtender for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Configuration in ETERNUS CS HE . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Virtual Library Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
9
Contents
8.10.1.2
8.10.1.3
8.10.1.4
8.10.1.5
8.10.2
8.10.3
8.10.3.1
8.10.3.2
8.10.4
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 . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
324
325
325
326
326
327
327
328
329
8.11
8.11.1
8.11.2
8.11.3
8.11.4
8.11.5
CommVault Simpana (Galaxy) . . . . .
General . . . . . . . . . . . . . . . . .
ACSLS library in Simpana with VACS . .
SCSI library with VJUK . . . . . . . . .
ADIC DAS Library in Simpana with VDAS
Further information . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
330
330
331
343
351
361
8.12
8.12.1
8.12.2
VTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Incompatibility problem in ETERNUS CS HE V4.0A and higher . . . . . . . . . . . 368
Use of the vtcp-config tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
8.13
8.13.1
8.13.1.1
8.13.1.2
8.13.1.3
8.13.2
8.13.2.1
8.13.2.2
8.13.2.3
Backup Exec 2010 . . . . . .
Configuring ETERNUS CS HE
Virtual Library Services . .
Logical Drives . . . . . . .
LV Size . . . . . . . . . . .
Adjusting Backup EXEC . . . .
Barcode rules . . . . . . .
Device drivers . . . . . . .
Licenses . . . . . . . . . .
8.14
BakBone NetVault®:Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
9
ETERNUS CS HE NAS functionality . . . . . . . . . . . . . . . . . . . . . . . . . 385
9.1
9.1.1
9.1.1.1
9.1.1.2
9.1.1.3
9.1.1.4
9.1.2
9.1.3
9.1.3.1
9.1.3.2
Network connection of the ETERNUS CS HE NAS frontend
Use of IP pools . . . . . . . . . . . . . . . . . . . . . . . . .
Load distribution in IP pools . . . . . . . . . . . . . . . . .
High availability of the data inputs . . . . . . . . . . . . . .
Load balancing via DNS server configuration . . . . . . . .
Restrictions for clients which are reached only via routers .
Detailed settings for network interfaces . . . . . . . . . . . . .
Releasing filesystems and file groups . . . . . . . . . . . . . .
NFS releases . . . . . . . . . . . . . . . . . . . . . . . .
CIFS releases . . . . . . . . . . . . . . . . . . . . . . . .
10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
370
370
370
371
371
371
372
373
377
385
385
386
386
387
389
389
389
390
391
Contents
9.1.4
9.1.5
User configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Protection period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
9.2
Separating physical devices of the VTL and of the NAS backend by FC zoning
9.3
Joint use of logical devices and libraries by the VTL and the NAS backend
10
Useful commands and information . . . . . . . . . . . . . . . . . . . . . . . . . 395
10.1
Logging, configuration tools, traces in UNIX systems
10.2
Display of ETERNUS CS HE configuration data for the service engineer . . . . 395
10.3
10.3.1
10.3.2
10.3.3
10.3.4
10.3.5
10.3.6
ETERNUS CS HE 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 . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
396
396
396
397
397
397
397
10.4
10.4.1
10.4.2
10.4.3
Control of ADIC / ABBA / AML libraries .
DASADMIN . . . . . . . . . . . . . . . .
Communication between client and server
Possible problems and solutions . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
398
398
400
401
10.5
10.5.1
10.5.2
10.5.3
10.5.4
10.5.5
10.5.6
10.5.7
10.5.8
Control of the StorageTek libraries . . . . .
Cleaning management in StorageTek libraries
Adding tapes in L180 . . . . . . . . . . . . .
Partitioning a library . . . . . . . . . . . . . .
Starting the ssi daemon . . . . . . . . . . . .
Stopping the ssi daemon . . . . . . . . . . .
cmd_proc . . . . . . . . . . . . . . . . . . .
Communication between client and server . .
Possible problems and troubleshooting advice
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
402
402
402
402
403
403
403
403
405
10.6
Information on the Cashion connection . . . . . . . . . . . . . . . . . . . . . . 405
10.7
Information on Fujitsu libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
10.8
Information on LTO drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
10.9
Information on cascading with CentricStor V3.x systems . . . . . . . . . . . . . 406
10.10
10.10.1
10.10.2
10.10.2.1
Fibre channel switches in the SAN environment
Features of the FC connection . . . . . . . . . . .
Zoning . . . . . . . . . . . . . . . . . . . . . . .
Rules . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
393
. . 393
. . . . . . . . . . . . . . 395
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
408
408
409
409
11
Contents
10.10.2.2
10.10.2.3
10.10.2.4
10.10.2.5
Zoning example (6 hosts on 3 ICPs) . . . . . . . . . .
Configuration example . . . . . . . . . . . . . . . . . .
Configuration of the brocade switch via Internet Explorer
Diagnostics in the event of performance problems . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
410
411
413
418
10.11
Host bus adapters (HBA)
10.12
10.12.1
10.12.2
10.12.3
10.12.4
Example of a filter bridge for separating ETERNUS CS HE
General . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start/stop script bridge . . . . . . . . . . . . . . . . . . . . .
Configuration file: csbridge . . . . . . . . . . . . . . . . . .
Ports used by ETERNUS CS HE . . . . . . . . . . . . . . .
.
.
.
.
.
420
420
421
426
428
10.13
10.13.1
429
10.13.1.1
10.13.1.2
10.13.2
10.13.2.1
10.13.2.2
10.13.2.3
10.13.3
Long distance over an FCIP connection with Cisco Switch . . . . . . . . . . . .
Long distance over an FCIP connection between the internal Brocade Switches of
ETERNUS CS HE with CMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Cisco Switch via the graphical user interface (Fabric Manager) .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.14
10.14.1
10.14.2
10.14.3
10.14.3.1
10.14.3.2
10.14.3.3
10.14.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
448
448
449
450
451
451
452
454
11
Installation of the GUI software GXCC/XTCC . . . . . . . . . . . . . . . . . . . . 455
11.1
Information about the installation CD . . . . . . . . . . . . . . . . . . . . . . . . 455
11.2
11.2.1
11.2.1.1
11.2.1.2
11.2.1.3
11.2.1.4
11.2.1.5
11.2.1.6
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 ETERNUS CS HE
Deinstallation of the Software . . . . . . . . . . . . . . . .
Configuration Data . . . . . . . . . . . . . . . . . . . . . .
12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
429
430
435
444
444
444
445
447
455
456
456
457
458
459
459
459
Contents
11.2.2
11.2.2.1
11.2.2.2
11.2.2.3
11.2.3
11.2.3.1
11.2.3.2
11.2.3.3
Installation on a LINUX Platform . .
How to proceed . . . . . . . .
Starting the GUI Software . . .
Deinstalling the GUI Software .
Installation on a SOLARIS Platform
How to proceed . . . . . . . .
Starting the GUI Software . . .
Deinstalling the Software . . .
11.3
11.3.1
11.3.2
Online Documentation of the GUI Software . . . . . . . . . . . . . . . . . . . . 464
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Displaying the Documentation via the Help Function of the GUI . . . . . . . . . . . 464
11.4
11.4.1
11.4.2
11.4.2.1
11.4.2.2
11.4.2.3
Font Files . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . .
Installation of the font files . . . . . . . .
Installation on MS-Windows Platform
Installation on a LINUX Platform . . .
Installation on a SOLARIS Platform .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
465
465
465
465
465
465
11.5
11.5.1
11.5.1.1
11.5.1.2
11.5.1.3
11.5.2
11.5.2.1
11.5.2.2
Offline Mode . . . . . . . .
Integrating the Snapshot Files
MS-Windows Platform . .
LINUX Platform . . . . .
SOLARIS Platform . . . .
Functionality in Offline Mode
Static Display . . . . . .
Dynamic Display . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
466
466
467
467
468
469
469
469
11.6
11.6.1
11.6.2
11.6.3
11.6.4
11.6.5
11.6.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 . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
470
470
471
472
472
473
473
12
Web GUI for ETERNUS CS HE administration . . . . . . . . . . . . . . . . . . . 475
12.1
Starting the Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.2
Logging in
12.3
Protection by certificates and firewalls . . . . . . . . . . . . . . . . . . . . . . . 477
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
460
460
461
461
461
462
463
463
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
13
Contents
13
Application recommendation for ETERNUS CS HE Update Installation . . . . . 479
13.1
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
13.2
13.2.1
13.2.2
13.2.3
13.2.4
Update procedure
Online update . . .
Rolling update . . .
Split cluster update
Cluster update . . .
13.3
Update situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
13.4
13.4.1
13.4.2
13.4.3
13.4.3.1
13.4.4
13.4.4.1
Update assessment criteria . . . . . . . . . . . . . . . . . .
Planning and administration expenditure . . . . . . . . . . . .
Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Total duration and downtime . . . . . . . . . . . . . . . . . . .
Time required for the rolling update . . . . . . . . . . . . .
Time required for split cluster update . . . . . . . . . . . . . .
Time required for cluster update installation (with downtime)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
482
482
485
486
486
488
489
13.5
13.5.1
13.5.2
13.5.3
Update handling instructions . . . . . . . . . . . . . . . . . . . .
Rolling Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Split cluster update . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of the transfer of front-end activities on the BS2000 S-server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
491
491
492
493
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
480
480
480
480
481
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Environmental Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Index
14
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
1 Introduction
ETERNUS CS HE 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 ETERNUS CS HE.
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
ETERNUS CS HE:
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 ETERNUS CS HE.
●
It provides information for host system administrators about the settings needed to
connect their systems (BS2000, MVS/ESA, Linux UNIX, Windows...) to ETERNUS CS
HE.
●
There is advice for setting up libraries which can work both as a back end with
ETERNUS CS HE or directly with the host.
●
It shows the zoning of an FC switch which can be switched between the host und
ETERNUS CS HE.
●
It shows ETERNUS CS HE service personnel how ETERNUS CS HE should be
configured for connection to each of the host systems indicated.
Only the maintenance technicians who have the ETERNUS CS HE root and service
passwords can access and edit ETERNUS CS HE configurations. The ETERNUS CS HE
configuration is described in the maintenance manual [2]. The configuration set up in
ETERNUS CS HE 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 ETERNUS CS HE to host systems, divided by system (BS2000, MVS/ESA,
UNIX-type 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 ETERNUS CS HE configuration data
– Using libraries
– Setting FC switches
– Host Bus Adapter
– Configuration example for ETERNUS CS HE (adding an ICP)
17
Notes
Introduction
1.4 Notes
General
ETERNUS CS is subject to constant development. The information contained in this
manual is subject to change without notice.
Changed company name
On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
Changed product name
With the release of Version 4.1A, the product name has been changed from CentricStor to
ETERNUS CS.
Changed model names
In addition to the product being renamed, all the model names for V4.1A have also been
changed. The old names and the corresponding new names are shown in the table below:
CentricStor model in V4.0A
ETERNUS CS model in V4.1A
VTC and SBU
ETERNUS CS50
VTA 500
ETERNUS CS500
VTA 1000
ETERNUS CS1000
VTA 1500
ETERNUS CS1500
VTA 2000
ETERNUS CS2000
VTA 3000
ETERNUS CS3000
VTA 4000
ETERNUS CS4000
VTA 5000
ETERNUS CS5000
Figures and program outputs in this edition of the manual
Unfortunately it was not possible to create new hardware pictures,
screenshots and program outputs for all the examples, which means that
occasionally the former company logo, the former company name, the former product name
and the former model names appear. Please forgive us for this shortcoming.
18
Introduction
Preparatory considerations
1.5 Preparatory considerations
The ETERNUS CS HE 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 ETERNUS CS HE (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
ETERNUS CS HE.
The logical volumes of ETERNUS CS HE 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 ETERNUS CS HE; 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 ETERNUS CS HE.
In many cases, ETERNUS CS HE 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 ETERNUS CS HE.
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
The figure below shows which host components handle the various items of configuration
data in the ETERNUS CS HE.
The procedure to be followed depends on the system. Lines written in bold apply to Open
Systems and BS2000 on FC (SX and S Server), lines written in italics apply to MVS/ESA
and BS2000/OSD.
19
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 213)
Host adapter
Which FC-HBAs are used on your host for CS (page 419)?
Check the version of the firmware and the BIOS settings 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
Check the version of the driver for the FC adapter.
Set your system so that the necessary device nodes are
created. (from page 153).
Add the CS drives to the BS2000 or MVS configuration files.
Real libraries
Switch/Director
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 409)
Set FICON director (BS2000 and z/OS, page 25 ff, page 63)
ETERNUS CS HE
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
20
Start ETERNUS CS HE as a client in a real library.
Set up cleaning management in a library. Where necessary,
partition real libraries (examples from page 398).
Introduction
The following tests and settings should be made before the starting configuration work.
●
ETERNUS CS HE 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. Fujitsu 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 ETERNUS CS HE accordingly. In
order to ensure trouble-free operation, the configuration in ETERNUS CS HE must
match the host configuration exactly.
●
Cases where several hosts are to be connected to ETERNUS CS HE. 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.
i
Take note of the maximum throughput of the available FC connections. If this
limit is exceeded, the performance of the fibre channel may fall dramatically.
If real libraries of ETERNUS CS HE 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 ETERNUS CS HE must
be completed before ETERNUS CS HE is configured.
●
Establish how the cleaning of the drives is carried out. ETERNUS CS HE 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.
●
You should check, which host adapter types are in use with your system on ETERNUS
CS HE. Make sure that up-to-date FW drivers are installed. You should check
compliance with these requirements and implement them where necessary, before
starting any integration work.
i
The chapter “Useful commands and information” on page 395 shows how you can
find the current configuration data of the ETERNUS CS HE on the graphical user
interface.
21
22
Introduction
2 Summary of permitted configurations
2.1 ETERNUS CS HE 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 ETERNUS CS HE configurations with z/OS
Host connection
Device emulation
Library connection
FICON(ESCON) host adapter
IBM3490
HACC, ACSLS, CSMVS
2.3 Configurations with ETERNUS CS HE in the SAN
environment
i
The current support matrix is for the service available at the internet address:
https://partners.ts.fujitsu.com/teams/cpc/Support%20Matrix/ETERNUS_CS_Support_Matrix.xlsx
2.4 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.
23
Restrictions for server farms using Open Systems
Summary of permitted configurations
2.5 Restrictions for server farms using Open Systems
In principle all Open System hosts should be able work with an ETERNUS CS HE 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 167.
2.6 General information on Open Systems
As of version CS 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 “Configurations with ETERNUS CS HE in the SAN environment”
on page 23.
24
i
The variable or fixed block length mode is not configured on the ETERNUS CS HE
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 ETERNUS CS HE in BS2000/OSD
3.1 Miscellaneous
When ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE naturally also ensure that a consistent saved status has
been achieved.
25
Miscellaneous
ETERNUS CS HE in BS2000/OSD
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 ETERNUS CS HE 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 [8] 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
26
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
*
27
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
ETERNUS CS HE 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
ETERNUS CS HE system in MAREN.
4. Next, restart MARENCP.
28
●
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 ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE 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
29
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 ETERNUS CS HE 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:
30
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 ETERNUS
CS HE tapes, MAREN supplies all three locations (HOME-LOC, FREE-LOC and
TEMP-LOC) with the same value specified in FREE-LOCATION when //ADD-FREEVOL 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)
31
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 ETERNUS CS HE 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.
32
Miscellaneous
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.
33
Miscellaneous
3.1.6 Activities in NDM
For a full description, see the BS2000 manual on system support [3].
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 ETERNUS CS HE 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 ETERNUS CS HE 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.
34
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 ETERNUS CS HE is made by an emulation of an ADIC library
(VAMU), the following settings for ETERNUS CS HE 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 ETERNUS CS HE is connected to BS2000/OSD via ROBAR, the following preliminary
work is necessary:
●
ROBAR-SV must be reinstalled for ETERNUS CS HE operation. In this case the
ETERNUS-CS-HE-specific 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
●
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 ETERNUS CS HE 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.
35
Miscellaneous
ROBAR must be installed with the corresponding storage location name (here CEST1).
ETERNUS CS HE 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 ETERNUS CS
HE 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 ETERNUS CS HE in BS2000 and in
ROBAR, see the manuals MAREN [4] Chapter 8.3 and ROBAR [6].
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.
36
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 HE cannot be set up.
Message CSCX050 is then issued.
!
The virtual connection to ETERNUS CS HE 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 [10]) 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 ETERNUS CS HE 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 ETERNUS CS HE 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.
37
Miscellaneous
Archive addresses, which cannot occur in physical archives are also accepted (and
correctly operated by ETERNUS CS HE):
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 ETERNUS CS HE 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.
38
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 ETERNUS CS HE: EMTAPE, VAMU/VACS
The logical devices are installed in the initial or update configuration using the GXCC
interface in the service mode.
ETERNUS CS HE 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 37).
39
Miscellaneous
3.1.9 Multiple ETERNUS CS HE systems
●
When multiple ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE
are made by the service provider.
40
SX servers
3.2 SX servers
As of K818 EKS 9, CS V2.1supports 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/OSD-BC V5.0C). SX100D 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 CS V3.0 and higher.
3.2.1 Connection via FC switch
ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE. Loop mode must be set permanently as the FC topology at the HBA
of the SX server and Eternus CS HE.
The direct connection has been tested with CS 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. A further test with CS V4.0A on the VTA 1500 model in which
the FC controller LP9402DC was used on ICP1, and on SX160, where Solaris 10, the
Leadville driver and X2000 V4.0A were used, plus FC controller LP11002, was also
successful. Loop mode was set permanently as the FC topology in accordance with the
SX160 Service Manual (4 = attempt loop mode only).
3.2.3 Configuring the tape units in ETERNUS CS HE
The virtual tape devices for the SX servers must be configured in ETERNUS CS HE 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.
41
SX servers
Example of ETERNUS CS HE connected to SX140:
vtls.conf in ETERNUS CS HE:
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
...
42
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 ETERNUS CS HE
viewpoint, like an Open System installation. For BS2000/OSD and the emulation layers
below it, the drives generated in ETERNUS CS HE appear to be native SCSI tape devices.
3.2.4.2
Configuration steps
The ETERNUS CS HE 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 ETERNUS CS HE devices (BS2 tapes) can subsequently be set up via WSA
(WebSysAdmin).
43
SX servers
3.2.4.3
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.
44
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 ETERNUS CS HE 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",
"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";
45
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;
...
46
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 ETERNUS CS HE devices (see example on page 42):
...
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 ->
47
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)
48
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
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 ETERNUS CS HE.
It makes sense (for example because of selective SM2) to select a free channel
from 00 through 0F for ETERNUS CS HE.
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
49
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 ETERNUS CS
HE 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.
50
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
-
SCD PORT SIDE DEV-ADDR PATH
0B00
AVAIL
0B0C
AVAIL
51
SX servers
Example: SX140 Leibniz with 48 ETERNUS CS HE devices
In the example the 2 EMKTAPE processes are running for device 40:
leibniz # ps -ef | grep -i EMKTAPE_40
root
root
52
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
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
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
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
53
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 an ETERNUS CS HE ICP. To save on Solaris
resources, it is however recommendable only to activate the ETERNUS CS HE devices
which are actually needed in X2000 (WSA).
●
Dynamic addition of devices
The I/O handler permits a maximum of 4096 bus devices. ETERNUS CS HE 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.
54
●
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 ETERNUS CS HE with the configuration setting Compression ON or OFF.
Thus X2000 ensures that data compression is always active in ETERNUS CS HE for a
tape device on the SX server unless configuration is configured with OFF in ETERNUS
CS HE for this tape device.
●
Device sharing, switch, path
SX servers do not support SCSI Reserve/Release.
Using the ETERNUS CS HE devices via a joint WSA Management Server as shared
devices, i.e. exclusively on several SX servers alternately, has not been tested with
ETERNUS CS HE.
The so-called 1:1 configuration has been quality-assured and generally released:
The FC port of an ETERNUS CS HE 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 an
ETERNUS CS HE ICP.
This excludes joint use of an ICP port and logical devices in ETERNUS CS HE by
multiple SX servers, by SX and S servers (business servers of the S series, see section
“ETERNUS CS HE on S servers” on page 57) or with Open Systems.
The devices are connected by a single path.
55
SX servers
3.2.6 Restrictions
●
Use of ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE 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
56
3.3 ETERNUS CS HE on S servers
As of CS V2.1 and BS2000/OSD-BC Version 5.0C support not only the connection of
ETERNUS CS HE 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
ETERNUS CS HE:
●
FC Switch
–
–
–
●
Brocade 2800 FW V2.60D
Brocade 12000 FW V4.0.0b
Connectrix McData FW 05.02.0013 ; EC 1030218
HCP-Level S server:
–
–
–
–
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-02N+023
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
57
3.3.2 Connection and configuration
The virtual devices for S servers must be configured as follows in ETERNUS CS HE:
Connection type: FC-SCSI
Emulation:
IBM 3590E
For S servers, a maximum of 64 devices per ICP can be configured in ETERNUS CS HE.
Virtual robot control of ETERNUS CS HE can be implemented both via the VAMU interface
(with ROBAR-CL/ROBAR-SV on the host side) and via the VACS interface (with CSC on
the host side).
Connection of ETERNUS CS HE 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
58
%
NKR0111 'DEVICE
=50' ASSIGNED ELSEWHERE
%
NKR0044 'DEVICE
=50': ATTACHMENT REJECTED
The ETERNUS CS HE 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: ETERNUS CS HE 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 ETERNUS CS HE 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.
ETERNUS CS HE 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)
59
ETERNUS CS HE on an SQ server
3.4 ETERNUS CS HE on an SQ server
3.4.1 Configuration in ETERNUS CS HE
CS V3.1D SP04 and higher and ETERNUS CS HE 4.1A-SP00 and higher supported the
connection of SQ servers (SQ100).
The connection to SQ servers is not released for CS 4.0A owing to an lpfc problem.
In ETERNUS CS HE the virtual tape devices for SQ servers must be configured with connection type FC-SCSI and emulation 3590E.
Example from vtls.conf in ETERNUS CS HE
…
36:ICP2:10:00:00:00:c9:51:c3:68:T0:AUTO >>> mit externen FC-Switch s.u. <<<
37:ICP2:10:00:00:00:c9:51:c3:69:T1:LOOP >>> ohne externen FC-Switch s.u. <<<
…
V300:ICP2:8888:SQSYSSW:FC-SCSI:VAMU:80:HOST:1:0:0x00:IBM:IBM
03590E1A:00C6E97D0300:0:ENABLED
03590E1A:00C6E97D0301:0:ENABLED
03590E1A:00C6E97D0302:0:ENABLED
03590E1A:00C6E97D0303:0:ENABLED
03590E1A:00C6E97D0304:0:ENABLED
03590E1A:00C6E97D0305:0:ENABLED
03590E1A:00C6E97D0306:0:ENABLED
03590E1A:00C6E97D0307:0:ENABLED
3.4.2 Connection between ETERNUS CS HE and SQ servers
The SQ servers are connected to ETERNUS CS HE via Fibre Channel with an external FC
switch (target mode AUTO in ETERNUS CS HE, see vtls.conf above) or directly - in the sense of without an external FC switch (target mode LOOP in ETERNUS CS HE, see vtls.conf
above). An FC switch enables multiple HBA ports or targets of ETERNUS CS HE to be assigned to the same HBA port in the SQ server. However, alternating use of the same virtual
ETERNUS CS HE tape devices in the SAN by multiple SQ servers or other server types
(SX or S servers or OpenSystems) is not released owing to the missing reserve/release on
60
the SQ server side. In other words an HBA port in ETERNUS CS HE should only be assigned to one HBA port of an SQ server, or it must be configured in the ETERNUS CS HE
LUN Mapping (note: LUN mapping is supported in ETERNUS CS HE V4 and higher).
The devices are connected via 1 path.
3.4.3 About the software configuration on the SQ server
The SQ100 is released with at least the following software statuses:
X2000 V5.1A (basic LINUX SLES 10 SP2)
Operating system package OSD/XC 4.0A (basic BS2000/OSD-BC V8.0)
For X2000 the tape devices can be configured with the Web GUI of the server unit’s SQ
Manager. The BS2000 mn of the virtual tape device is defined here.
Tape drives in the SQ Manager X2000 V5.2
61
●
The unit ID in X2000 may not be identical to the BS2000 mn.
Example
mn=87 with Unit-ID=00 in BS2000 /sh-dev-conf (80,81,82,83,84,85,86,87),p
%
%
%
%
%
%
%
%
%
●
DVC
80
81
82
83
84
85
86
87
DEV-TYPE
3590E
3590E
3590E
3590E
3590E
3590E
3590E
3590E
CONF-STATE
ATTACHED
ATTACHED
ATTACHED
ATTACHED
ATTACHED
ATTACHED
ATTACHED
ATTACHED
PID CTL CHPID IOS
00
77
00
77
00
77
00
77
00
77
00
77
00
77
00
77
-
SCD PORT SIDE DEV-ADDR
7780
7781
7782
7783
7784
7785
7786
7700
PATH
AVAIL
AVAIL
AVAIL
AVAIL
AVAIL
AVAIL
AVAIL
AVAIL
Under some circumstances LUN 0 may not recognized as a tape device on the SQ server, for example after an SQ server reboot while tape emulation vtd is stopped in ETERNUS CD, e.g. because of DNA:
service@sqsys200(X): scanPciSlot -v -scan port=64:00.1 lun=0-7
OLD: Host: scsi12 Channel: 00 Id: 00 Lun: 00
Vendor: STGT-FC Model: ICP2
Rev: 1.37
Type:
Processor
ANSI SCSI revision:
Vendor: IBM
Model: 03590E1A
Rev: E32E
Type:
Sequential-Access
ANSI SCSI revision:
Vendor: IBM
Model: 03590E1A
Rev: E32E
Type:
Sequential-Access
ANSI SCSI revision:
…
Vendor: IBM
Model: 03590E1A
Rev: E32E
Type:
Sequential-Access
ANSI SCSI revision:
Vendor: IBM
Model: 03590E1A
Rev: E32E
Type:
Sequential-Access
ANSI SCSI revision:
●
04
03
03
03
03
Remedy to ensure that the SQ server recognizes LUN 0 as a tape device again:
FC LINK DOWN / UP after the tape emulations have been restarted in ETERNUS CS
HE, or ICP/VTC reboot.
62
●
If compression with HOST (see vtls.conf above) is set in ETERNUS CS HE for the virtual
tape device, ETERNUS CS HE performs compression when the volume type in BS2000
is Tape-C4 and does not perform compression when the volume type in BS2000 is TapeC3.
●
For further information, please refer to the following manuals: SQ100: Operation and Administration, SQ100: Operating Manual, SQ100 Business Server: Maintenance Manual
4 ETERNUS CS HE on z/OS
4.1 Introduction
An ETERNUS CS HE virtual tape server behaves towards z/OS or OS/390 systems like a
physical IBM 3490E 36-track tape system and is able to communicate with more than one
LPAR in parallel.
The virtual tape drives (devices) offered by ETERNUS CS HE 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 ETERNUS CS HE and the IBM host is implemented both
via ESCON or ESCON Director channels and via FICON or 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 Fujitsu Technologie Solutions and
CSMVS from Fujitsu Technology Solutions. Dependent on which host software was chosen,
the corresponding Virtual Library Service (library emulation) is set in ETERNUS CS HE.
The type of physical library attached to ETERNUS CS HE (back end) is not visible to the
host.
ETERNUS CS HE 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 ETERNUS CS HE data sheet or the menu of the
ETERNUS CS HE 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 Fujitsu Technology Solutions); further information is also provided in the
ETERNUS CS HE manuals. For information on tape management systems please refer to
the manuals which the vendors provide.
63
Subjects Covered
ETERNUS CS HE on z/OS
4.2 Subjects Covered
The individual subject areas are:
–
–
–
–
–
–
Definition of ETERNUS CS HE logical drives in z/OS using HCD
Logical volume definition
VACS Interface
Host software functions: NCS/CSC, CSMVS, HACC
Examination of the tape management interfaces 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, ETERNUS CS HE supports 640 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. 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 (CUs) 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/cascaded configuration via an
ESCON or FICON director (switch) are possible.
64
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 to upgrade each of the ISPs later to a configuration with 64 virtual drives. In case of ESCON attachment, TYPE=FC is replaced by
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
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 Configuration
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 Port1 function is mandantory for
the switch/director. This also applies if Cascaded FICON is configured. Refer to the manual
of the switch/director for further details.
For further information on HCD details, see IBM Hardware Configuration Definition User's
Guide.
1
CUP
66
CHPID
CHPID
CHPID
CHPID
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
Sharing of virtual drives can be implemented in SYSPLEX or using tape sharing software
such as CA-MIM. Device sharing between BS2000 and SYSPLEX is not 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. A timeout value of 10 minutes is recommended for ETERNUS CS HE virtual
drives.
The following MIH entry in SYS1.PARMLIB (IECIOSxx) represents this recommendation:
Example
MIH DEV=(1E00-1E0F), TIME=10:00
/*T3490*/
67
4.3.3 Representation of Virtual Drives in ETERNUS CS HE
The virtual drives of ETERNUS CS HE are defined in accordance with the host software.
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.
The LibDevName consists of the virtual quadruple (ACS, LSM, panel, row). For mount
balancing purposes, special logic is applied to the numbering of the virtual drives. Details
of the schema used for numbering the drives are provided in the section on setting up
NCS/CSC (see section “NCS/CSC” on page 74).
68
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. In versions 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. Refer to the corresponding chapter of the tape
management software that is used in conjunction with ETERNUS CS HE.
The following figure shows the Logical Volume Groups window in which the LVG is created:
69
4.3.5 VACS Interface
The Virtual ACSLS interface enables ETERNUS CS HE to look like a SUN/STK ACSLS
server. Scratch subpools must be defined here, to map logical volume groups to a scratch
subpool.
i
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.
1. Log in to ETERNUS CS HE via a TELNET session (CS 3.x) or ssh session (CS 4.0 and
higher) and start the operation with:
cmd_proc
2. First define the pool ID that will be used. The available pool IDs lie between 1 and 254
and are defined using the following syntax (use of the default pool 0 is not recommended):
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
70
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
Note, that the volser is case sensitive. For mainframe volumes use capitals!
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 mount has taken place for a virtual volume, for security reasons the virtual
volume loses its scratch status. Although it is still a scratch volume from the
viewpoint of the tape management, ETERNUS CS HE regards the volume as a data
volume. After the next scratch synchronization, the status of the volume is reset to
scratch in VACS. The query pool and the query scratch commands only show
counts or volumes, that have the scratch status in VACS.
71
Host Software Functions
4.4 Host Software Functions
The different host software solutions, that are available for an ETERNUS CS HE 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:
●
Allocation Influencing
●
Message processing and automation
●
Scratch synchronisation between ETERNUS CS HE and tape management
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 requesting an existing
file via the OS catalog. In contrast to the JCL VOL=SER parameter together with the
UNIT=esoteric parameter, the other two allocation requests end up in a generic device
allocation, which in case of ETERNUS CS HE virtual drives is 3490.
In a mixed configuration (i.e. ETERNUS CS HE and other non-ETERNUS CS HE 3490-type
drives), such a request may end up in an allocation, where an ETERNUS CS HE logical
volume should be mounted on a manual drive or a physical volume should be mounted on
an ETERNUS CS HE virtual drive. To avoid this situation, the control program influences
the allocation 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 ETERNUS CS HE. This
is also called scratch subpooling.
i
72
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.
Host Software Functions
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 control program can execute allocation to the corresponding esoteric name in accordance
with the file or job name. 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 .
4.4.2 Message Processing and Automation
The host software analyzes messages for the tape volumes and communicates with
ETERNUS CS HE in order to control the mounting and dismounting of volumes. Tape
volume 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. Refer to the discussion of supported tape management software for more information.
Messages for mounting/dismounting volumes are always analyzed in order to obtain the
function which is to be performed, the device address and the volume number.
Furthermore, a scratch subpool can be selected on the basis of various criteria (e.g. file
name or job name). Scratch subpooling may also be implemented via the tape
management system. Please refer to the section, which explains the different tape
management software.
73
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.2.0 and also applies for ELS 7.0. When applicable, any special features of ELS 7.0
are also pointed out.
4.5.1.1
Overview
The Nearline Control System (NCS) is a software package to drive SUN/STK libraries in a
z/OS or OS/390 environment. It provides the basic function SMS and optional subfunctions.
The subfunction Client System Component for MVS (CSC/MVS) is used to attach the
ETERNUS CS HE 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 ETERNUS CS 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
74
TMC
SYSB
ETERNUS CS
VLP
SVLP
VACS
VACS
4.5.1.2
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.2 software are contained:
FMID
Function
Needed for ETERNUS CS HE
SOS6200
contains SMC load modules, macros and
samples
Yes
SMZ6200
contains the SMC JES3 support
Yes, if JES3 installation
SOS6200
contains HSC load modules, macros and
samples
No, but is recommended if
RMM, CA1 or TLMS tape
management is used
SSKY500
contains the HTTP server load modules,
macros and samples
NO
SOC6200
contains the LibraryStation load modules and NO
samples
SCS6200
contains the MVS/CSC load modules,
macros and samples
YES
ASAR700
contains SAS/C 7.0 selected components
required for the StorageTek HTTP server
NO
SSCR70C
required for LibraryStation and MVS/CSC
YES
SSCR70D
required for LibraryStation and MVS/CSC
and the StorageTek HTTP server
YES
i
The function SOS6200 for HSC contains load modules for scratch synchronisation,
that are also used by CSC. If you do not install SOS6200, 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 SOS6200, the ready to go
load modules are contained in library SLULINK. Please refer also to the CSC
System Programmer's Guide.
75
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
76
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)
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
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
*
77
ALOCTIME(180)
MSGCASE(MIXED)
TRACE(NO)
TRACD(FILE)
LOG(RESET)
<<<<<<<<<<
COMPRFX('!')
<<<<<<<<<<
LKEYDEF('YOUR.CSC.PARMS(CSCKEY)')
* TIME OUT SECONDS
* OUTPUT CASE
* LOGGING OPTION
* COMMAND PREFIX
<<<<<<<<<<<<<<
The SERVER parameter is set to ACSLS because ETERNUS CS HE emulates this type of
attachment.
Add the IP address of ETERNUS CS HE and the name of your TCP/IP started task to
INTERNET and TCPN.
For LIBDEV specify the esoteric name of your logical ETERNUS CS HE drives. By default
ETERNUS CS HE 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 ETERNUS CS HE, specify the esoteric name
of these non library drives.
The LIBUNIT statement must contain all ETERNUS CS HE 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 ETERNUS CS HE 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 80).
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.
78
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 activated. For more information, please refer also to the chapter Firewall:
section “ETERNUS CS HE NCS/CSC network attachment via firewall in a z/OS
environment” on page 93.
●
One started task of CSC manages one and only one ETERNUS CS HE. If you are using
multiple ETERNUS CS HE systems or a SUN/STK library via CSC, 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. We recommend, to use
TAPEREQ VOLT(N) ESOT(CS_Esoteric) MED(STD) REC(36TRACK)
as the very last statement.
●
With NCS 6.2 the processing of TAPEREQ statements has been switched to POLICY.
The TAPEREQ statement is still supported for reasons of compatibility. A REXX is available in the SMC.Samplib for migrating from TAPEREQ to POLICY.
●
With CSC and SERVER type ACSLS, which is used for ETERNUS CS HE, 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.
79
4.5.1.3
Virtual Drives Coordinates
Virtual drive coordinates are defined during setup of 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 ETERNUS CS HE 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'.
The PANEL ID begins with '01' and represents the drive wall or panel. A drive wall can
accommodate up to 20 drives. For the sake of clarity, only IDs 01 through 16 should be
used. Consequently, if your configuration contains more than 256 virtual drive addresses,
PANEL ID '02' is available. The drive location within a panel starts with 0.
The diagram shows examples of some allocations 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'
80
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.
In the example a maximum of 4 drive positions per panel are occupied in order to demonstrate the distribution to another panel:
ICP 0
z/OS
CSC
DEV CU
ADDR ADD ITMAP
VACS
ICP 2
CSC
z/OS
DEV CU
ADDR ADD
LibDevName
VACS
UNITMAP
LibDevName
1C00
1C01
1C02
1C03
1C04
1C05
1C06
1C07
1C08
1C09
1C0A
1C0B
1C0C
1C0D
1C0E
1C0F
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
0EC0
0EC1
0EC2
0EC3
0EC4
0EC5
0EC6
0EC7
0EC8
0EC9
0ECA
0ECB
0ECC
0ECD
0ECE
0ECF
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
1C10
1C11
1C12
1C13
1C14
1C15
1C16
1C17
1C18
1C19
1C1A
1C1B
1C1C
1C1D
1C1E
1C1F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
0ED0
0ED1
0ED2
0ED3
0ED4
0ED5
0ED6
0ED7
0ED8
0ED9
0EDA
0EDB
0EDC
0EDD
0EDE
0EDF
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
81
ICP 1
CSC
z/OS
DEV CU
ADDR ADD
82
VACS
UNITMAP
ICP 3
CSC
z/OS
DEV CU
ADDR ADD
LibDevName
VACS
UNITMAP
LibDevName
1D00
1D01
1D02
1D03
1D04
1D05
1D06
1D07
1D08
1D09
1D0A
1D0B
1D0C
1D0D
1D0E
1D0F
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
0FC0
0FC1
0FC2
0FC3
0FC4
0FC5
0FC6
0FC7
0FC8
0FC9
0FCA
0FCB
0FCC
0FCD
0FCE
0FCF
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
03
03
03
03
03
03
03
03
03
03
03
03
03
03
03
03
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
1D10
1D11
1D12
1D13
1D14
1D15
1D16
1D17
1D18
1D19
1D1A
1D1B
1D1C
1D1D
1D1E
1D1F
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
0FD0
0FD1
0FD2
0FD3
0FD4
0FD5
0FD6
0FD7
0FD8
0FD9
0FDA
0FDB
0FDC
0FDD
0FDE
0FDF
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
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 walls. Within a drive wall 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.
83
ICP 0
CSC
z/OS
DEV CU
ADDR ADD
84
VACS
UNITMAP
ICP 1
CSC
z/OS
DEV CU
ADDR ADD
LibDevName
VACS
UNITMAP
LibDevName
1C00
1C01
1C02
1C03
1C04
1C05
1C06
1C07
1C08
1C09
1C0A
1C0B
1C0C
1C0D
1C0E
1C0F
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
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
1D00
1D01
1D02
1D03
1D04
1D05
1D06
1D07
1D08
1D09
1D0A
1D0B
1D0C
1D0D
1D0E
1D0F
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
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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
1C10
1C11
1C12
1C13
1C14
1C15
1C16
1C17
1C18
1C19
1C1A
1C1B
1C1C
1C1D
1C1E
1C1F
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
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
1D10
1D11
1D12
1D13
1D14
1D15
1D16
1D17
1D18
1D19
1D1A
1D1B
1D1C
1D1D
1D1E
1D1F
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
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
4.5.1.4
1C20
1C21
1C22
1C23
1C24
1C25
1C26
1C27
1C28
1C29
1C2A
1C2B
1C2C
1C2D
1C2E
1C2F
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1D20
1D21
1D22
1D23
1D24
1D25
1D26
1D27
1D28
1D29
1D2A
1D2B
1D2C
1D2D
1D2E
1D2F
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1C30
1C31
1C32
1C33
1C34
1C35
1C36
1C37
1C38
1C39
1C3A
1C3B
1C3C
1C3D
1C3E
1C3F
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
08
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
1D30
1D31
1D32
1D33
1D34
1D35
1D36
1D37
1D38
1D39
1D3A
1D3B
1D3C
1D3D
1D3E
1D3F
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
02
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
09
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
Scratch Subpooling
When NCS/CSC is used to control ETERNUS CS HE, the scratch subpooling function 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,
SMC user Exit 01 are provided depending on the software used: RMM, CA-1, TLMS and
Control-T. The exits themselves comprise static source code which is compiled together
with the table configured by the user. 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,
85
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 automatically included in 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 version of NCS, all delivered source code is HSC
format.
Example for CA-1, TLMS and Control-T Member SPTABCTS
********************************** ************************************
*
*
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)
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
*######################################################################
***********************************************************************
86
TABSPEND EQU
*
DEFINE END OF TAB
Tailor the table 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 ETERNUS CS HE 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 ##############
*
*######################################################################
*#
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'
87
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
***********************************************************************
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 pools and non-SMS pools.
Once you have completed the table SPTABCT or SPTABRMM, compile and linkedit the exit
to the NCS/SMC load library (SMCLINK) as follows.
//ASMUX01
88
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.NCS620.SMC6200.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.
For mount balancing to function, the following must be entered in the ALLOCDEF statement
of the SMC:
Ê
ZEROSCR(OFF)
The parameter can also be set dynamically using a command:
Ê
F SMC,ALLOCDEF ZEROSCR(OFF)
89
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. The
library server for ETERNUS CS HE is VACS. VACS keeps track of 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 active.
i
SCSCONDB supports RMM, CA-1 and TLMS. To synchronise Control-T with
VACS, a REXX script is offered 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
system will reject the usage of the affected volume and request a remount. VACS automatically selects another volume and processing continues.
i
Due to the asynchronous process, ETERNUS CS HE 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 can 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. The subsystem parameter
must be added. For this purpose a REXX procedure is provided 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.
90
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.
91
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 scratch list produced as a result of this procedure 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. Please refer to the section
“User Exits and Scripts” on page 152 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),
//
//*
92
//IKJSPF
//
//SYSTSPRT
//SYSPROC
//SYSTSIN
//SCRIN
//SCROUT
//
//
//
//*
//SETSCR1
//STEPLIB
//SCSIN
//SYSPRINT
//SCSPRINT
//*
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
ETERNUS CS HE NCS/CSC network attachment via firewall in a z/OS environment
In a z/OS system environment, that attaches ETERNUS CS HE via a firewall and CSC, the
following considerations must be taken:
ETERNUS CS HE incoming ports can be fixed, using the VACS configuration. Please refer
to the ETERNUS CS HE 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:
93
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 ETERNUS CS HE to mainframe:
CS1 and CS2 must be granted to use both ports 50099 and 50199 for entering MF, instead
of assigning one exclusivly each ETERNUS CS HE.
After the change has been activated, a TCP/IP trace should be taken for verification.
94
4.5.1.7
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 ETERNUS CS HE 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 addresses 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 ETERNUS CS HE logical drives matches the configuration.
95
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 70)
●
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 ETERNUS
CS HE 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 ETERNUS CS HE 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, CA1 and TMLS as tape management software. For
integration of scratch subpooling, refer to the corresponding chapter in this document:
–
–
section “DFSMSrmm considerations” on page 127 for RMM and
section “CA1 and TLMS considerations” on page 141 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 ETERNUS CS HE. 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.
96
The following table of the CSMVS Installation & Administration Guide should be observed.
Recommended installation procedures are 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 ETERNUS CS HE, LMS/CSMVS with FS5193 gateway
ESCON/FICON connections to the drives
z/OS
ETERNUS CS HE
LMS/CSMVS
TCP/IP
FS5193
Gateway
VACS
97
–
–
–
98
ETERNUS CS1000 with IUP0 and IUP1, each with 32 logical drives
Tape drives in the z/OS generated on 8000-803F
Logical drives in ETERNUS CS HE (LibDevName)
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
99
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
100
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
# 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
CSECT
MTCSICP ICP=0,LOW=8000,NUM=32,DSN=NO,TYPE=INITIAL
MTCSICP ICP=1,LOW=8020,NUM=32
MTCSDSN
END
101
4.5.2.3
Scratch alignment between RMM/CA-1 and ETERNUS CS HE 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. If the
implementation via the exit is not wanted, scratch alignment can also take place using the
batch program described in section “Setting manual scratch for ETERNUS CS HE from the
host”. The list of tapes from the tape management housekeeping job is used as the input
here.
4.5.2.4
Setting manual scratch for ETERNUS CS HE from the host
It is recommended that the tapes should be set to scratch for ETERNUS CS HE from the
host instead of doing this in ETERNUS CS HE 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
//
102
4.5.3 HACC
4.5.3.1
Overview
The HACC is a software package which was originally created to drive Quantum/ADIC
libraries in a z/OS or OS/390 environment. It also can be used to control an ETERNUS CS
HE. If multiple ETERNUS CS HE systems are used, a separate instance of the HACC must
be started. The HACC communicates with ETERNUS CS HE via the VAMU feature, which
emulates the Grau AMU of a physical library. ETERNUS CS HE 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 ETERNUS CS HE drives must be coded. For volumes that are
103
mounted based on a catalog search, a catalog user exit is used to modify the allocation of
the drive. 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 uses a file called HACC
ARCHIVE. In case of ETERNUS CS HE, 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.
Note, that in contrast 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 the exchange log 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 106. Short
explainations of ETERNUS CS HE most important parameters are given also.
104
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 117.
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 126
105
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
*
106
*---------------------------------------------------------------------*
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
*
107
*---------------------------------------------------------------------*
*
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)
*
108
*
!--------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
*
109
*---------------------------------------------------------------------*
*
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
*-------------->
110
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 ----------------------------------------*
111
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
112
*
*---------------------------------------------------------------------*
*
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
113
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 --------------------------------------------------*
114
1
SYSDEF1: specify VTLS for ETERNUS CS HE
2
Use STIMER=01 so that the exchange log dataset is checked every second for
outstanding mounts. As ETERNUS CS HE 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 ETERNUS CS HE. 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 ETERNUS CS HE, 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
115
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.
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.
116
4.5.3.4
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.
117
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
118
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
119
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
120
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.
121
=== 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.
122
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.
123
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
124
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 tape management database and the ARCHIVE file
to reflect the current scratch status.
125
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 ETERNUS CS HE. So from
the viewpoint of ETERNUS CS HE, each mount in conjuction with HACC is specific. HACC
merely executes a STUB for the virtual scratch volume, which means that it is not reloaded
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 issuing FREEVOL. In addition, RESET may be used if you prefer to have
the lower number ranges reused. High volsers will then initially 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.
126
Tape Management Software
4.6 Tape Management Software
This chapter explains the setup for different tape management systems.
In case, your ETERNUS CS HE is attached via the VACS emulation, the LVGs of ETERNUS
CS HE have to be mapped to a pool-ID in VACS. This is done, using the cmd_proc application in a command box of the ETERNUS CS HE VLP. The procedure was explained
earlier in this document (see section “Logical Volume Definition” on page 69).
4.6.1 DFSMSrmm considerations
Functions of DFSMSrmm, that interface with ETERNUS CS HE are scratch processing and
scratch volume subpooling. As ETERNUS CS HE 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
127
subpools. The library type used for ETERNUS CS HE 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 define 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))
When multiple LPARs access a TCDB, an IDCAMS IMPORT is required for the master catalogs of the additional systems:
IMPORT OBJECTS((SYS1.VOLCAT.VGENERAL) VOLUME(MYVOL1)
DEVICETYPE(3390))) CONNECT VOLCAT
i
-
On no account may you forget the VOLCAT parameter here, otherwise the tape allocation for specific requirements will no longer function.
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
128
There is no need to start the OAM started task, if you are not using an IBM library.
In case of a mixed environment (IBM library and ETERNUS CS HE), please ignore
OAM messages CBR3006I and CBR3002E that occur for the library entry that was
defined for ETERNUS CS HE.
The description below shows a sample procedure for the SMS definitions required. The panel structure can differ according to the z/OS release.
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
Optical Library
Optical Drive
Tape Library
- Optical Library Configuration
- Optical Drive Configuration
- Tape Library Configuration
129
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.
130
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
.
.
.
.
0
0
0
0
(0
(0
(0
(0
to
to
to
to
999999)
999999)
999999)
999999)
View next Panel;
Exit; CANCEL to Exit.
131
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).
132
-----------------------------------------------------------------------------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 the storage group that represents a scratch subpool. This scratch subpool is mapped
to an ETERNUS CS HE logical volume group (LVG). The storage group type is: TAPE.
Select option 2 to enter the TAPE STORAGE GROUP DEFINE screen:
133
-----------------------------------------------------------------------------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
ETERNUS CS HE, 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.
134
-----------------------------------------------------------------------------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 groups. 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 files.
135
-----------------------------------------------------------------------------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.
136
-----------------------------------------------------------------------------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 the storage class 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 filter lists for file names in order to assign different management classes.
137
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)
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
138
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')
.......
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)
EXPDTCHECK(N)
MEDIANAME(3490)
VLPOOL PREFIX(B*) TYPE(S) DESCRIPTION('LVG02')
NAME(SGLVG02)
EXPDTCHECK(N)
MEDIANAME(3490)
VLPOOL PREFIX(C*) TYPE(S) DESCRIPTION('LVG03')
NAME(SGLVG03)
EXPDTCHECK(N)
MEDIANAME(3490)
-
The EXPDTCHECK parameter is necessary to permit volumes to be written to which are
Sratch but have an expiry date in the volume header or for processing with DISP=MOD.
Now convert the 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 ETERNUS CS HE, 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.
139
Checklist to implement RMM scratch subpooling
1. Define the VOLCAT (not nessary if already using SMS tape)
2. Define the OAM subsystem 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 also others if these are
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)
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 ETERNUS CS HE, 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.
140
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
ETERNUS CS HE:
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
4.6.2 CA1 and TLMS considerations
Functions of CA1 and TLMS, that interface with ETERNUS CS HE are Scratch processing
and scratch volume subpooling. As ETERNUS CS HE 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
The method, on how scratch volumes are synchronised is dependent on the host software
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).
1
If Auto Labelling is disabled
2
If NCS/CSC or CSMVS is used
141
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 parameter file. 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
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 ETERNUS CS HE, use the appropriate procedures to expand
the TMC and the VMF, respectively and to add the new volsers to the tape management
system.
142
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
ETERNUS CS HE:
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
4.6.3 Control-T considerations
Functions of Control-T, that interface with ETERNUS CS HE are Scratch processing and
scratch volume subpooling. As ETERNUS CS HE 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
The method used to synchronize scratch volumes is dependent on the host software
product that is used. It is implemented in the Control-T management run which is executed
regularly and is performed asynchronously via an additional jobstep (NCS/CSC and
HACC). Control-T is currently not supported by CSMVS.
1
2
143
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 both supported host software solutions
(NCS/CSC and HACC).
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
144
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
145
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.
146
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 ETERNUS CS HE, you can start the initialisation process (only
if Auto Labelling is disabled).
147
//CTTTPI
JOB ........
//*
//CTTTPI
EXEC PGM=CTTTPI,REGION=8M
//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 ETERNUS CS HE logical volumes.
maximum count is 9999
i
ETERNUS CS HE:
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
148
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 an ETERNUS CS HE 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 ETERNUS CS HE 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.
149
Library Station
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 an ETERNUS CS HE backend
configuration via LibStation/HSC.
ETERNUS CS 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
ETERNUS CS
VLP
Library Control
!
IDP
PLS
VACS
IMPORTANT!
Note that the ETERNUS CS HE frontend and backend connection work totally
independent from each other.
There are three typs of communucation:
150
●
CSC talks to VACS to perform ETERNUS CS HE virtual mount.
●
Physical Library Services talks to LibStation to perform physical mounts.
●
Physical mounts, either ETERNUS CS HE backend or z/OS native, are issued by HSC
to Library Control communication.
Library Station
If you want to use the Library Station software to control your ETERNUS CS HE backend
drives, make sure that the required FMIDs are installed. Please refer to section “Installation
and Customisation” on page 75 for more details.
After the software is SMP/E installed, set up the HSC environment to map the new configuration. ETERNUS CS HE 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 ETERNUS CS HE.
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 ETERNUS CS HE 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.
151
User Exits and Scripts
4.9 User Exits and Scripts
The following user exits and scripts referenced in previous chapters may be downloaded
from
Service partner portal ➟ Storage ➟ ETERNUS CS / CentricStor ➟ Documents ➟ downloads ➟
add-on ➟ Integration_with_IBM_Mainframes
https://partners.ts.fujitsu.com/com/service/ps/Storage/CentricStor/Pages/defa
ult.aspx?CurrentFolder=2fc4ba9d-97be-412f-a09a-3be145877853
152
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 ETERNUS CS HE on UNIX-type systems
5.1 Linux
5.1.1 EMULEX controller
The current EMULEX driver for SUSE Linux is 8.2.0 or higher. The driver is supplied
together with the Linux system.
5.1.2 Qlogic QLA2200F Controller
5.1.2.1
RedHat LINUX
Use of ETERNUS CS HE is supported as of RedHat Linux RHEL 4.
i
5.1.2.2
Neither a drive of the type Mammoth2 nor a VJUK library controller should be defined
on LUN0, otherwise only 1 LUN will be recognized in the RHEL 4/lpfc.
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). Particularly
intensive tests were conducted with the verrsions specified.
●
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).
153
Linux
ETERNUS CS HE on UNIX-type systems
●
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 ETERNUS CS HE 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, an emulation running in ETERNUS CS HE is once again
automatically recognized with 32 LUNs.
Overview of driver versions
Controller
Linux
version
QLA2200
1
154
Driver
Version
Source
SuSe 8.0 qla2x00
4.46.5
supplied in kernel
SuSe 8.0 qla2x00
4.47.11
FSC
SuSe 8.1 qla2200 6.1b2
supplied in kernel
SuSe 8.1 qla2x00
FSC
4.47.11
Notes
only sees 8 LUNs 1
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
Data compression
On the host side, the compression in ETERNUS CS HE 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 ETERNUS CS HE.
–
–
–
–
–
For the drive emulation FSC/CentricStor, compression at the host is turned off by
default.
For the drive 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.
155
Solaris
5.1.2.3
SuSE SLES 9.0
●
Neither a virtual drive of type Mammoth2 nor a VJUK robot controller should be defined
on LUN0, otherwise only 8 LUNs will be recognized by SLES 9/lpfc. 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
Rebooting a server or reloading the FC driver (Qlogic or Emulex) on a server connected
to ETERNUS CS HE and running SLES 9 SP3 will cause the drive to be rewound. This
interrupts I/O operations running on other servers which are connected to the same
drives.
We recommend the installation of SuSE update
udev-021-36.63.i586.rpm/udev-021-36.63.x86_64.rpm
in order to prevent this problem.
5.2 Solaris
5.2.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.
●
156
The EMULEX LP9802DC FC controller may not be used.
Solaris
5.2.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:
https://partners.ts.fujitsu.com/com/service/Pages/default.aspx
5.2.3 Important settings and information
●
You must be operating with the tape driver st.
●
Solaris does not permit two FC controllers to bind to the same WWPN. This is also not
permitted in ETERNUS CS HE because it would otherwise bind two different device
nodes to the same logical device. This is not supported by the backup tools.
●
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 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
Ê
Then call /usr/sbin/FJSVmadm/swhardmon update so that the modifications
become effective.
157
Solaris
●
On Solaris systems (test system Solaris 9 with LP10K) with the EMULEX lpfc driver
6.30g the device nodes are not recognized as tape volumes, though LUN recognition
is correct (see /var/log/messages). This applies to all ETERNUS CS HE emulation
types.
Example with type "CentricStor":
# mt -f /dev/rmt/49cbn status
/dev/rmt/49cbn: No such device or address
#ls -l /dev/*cbn
…
lrwxrwxrwx
1 root
root
55 Apr 20 16:44 /dev/rmt/49cbn ../../devices/pci@85,2000/fibre-channel@1,1/st@38,0:cbn
…
Output from /var/log/messages:
…
/pci@85,2000/fibre-channel@1,1/st@38,0 (st76):
Apr 21 09:52:43 mars
<CentricStor>
Apr 21 09:52:43 mars scsi: [ID 193665 kern.info] st76 at lpfc2: target
Apr 21 09:52:43 mars genunix: [ID 936769 kern.info] st76 is
/pci@85,2000/fibre-channel@1,1/st@38,0
…
38 lun 0
Measure:
After Solaris reboot perform HBA reset on Solaris, e.g.
# /opt/HBAnyware/hbacmd reset 10:00:00:00:c9:45:70:b7
With the latest EMULEX lpfc driver 6.11.cx2 released by FSC/FTS the problem "No
such device" after Solaris reboot does not occur any more. This also applies to the legacy versions 6.01f.
158
Solaris
5.2.4 Driver for EMULEX
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 165 and the example of the file
lpfc.conf.
159
Solaris
5.2.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
160
Solaris
5.2.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 virtual tape 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 ETERNUS CS HE drives are then recognized and the corresponding device nodes created.
161
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 160).
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 173 shows an example.
After a reboot, the ETERNUS CS HE 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).
162
Solaris
5.2.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 ->
...
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
163
Solaris
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 ETERNUS CS HE)
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
/dev/vt/STAR-ICP1/V110bn
/dev/vt/STAR-ICP1/V110cbn
...
/dev/vt/STAR-ICP1/V11Fbn
/dev/vt/STAR-ICP1/V11Fcbn
/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.
i
164
The LUNs set in ETERNUS CS HE can be shown via:
Global Status function bar ➟ Tools ➟ Show Balloon Help Summary
Solaris
5.2.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 ETERNUS CS HE
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 ETERNUS CS HE.
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
●
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 ETERNUS
CS HE 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).
165
Solaris
5.2.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]
..............
166
FUJITSU MAJ3182MC
FUJITSU MAJ3182MC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
Solaris
5.2.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 173).
5.2.11 Contents of the file lpfc.conf for Solaris
An example of a file modified for ETERNUS CS HE is shown below. The entries relating to
ETERNUS CS HE 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;
167
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
168
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;
#
#
#
#
#
#
#
#
#
#
#
#
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
169
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
170
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;
171
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.
172
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.2.12 Contents of the file st.conf for Solaris
An example of a file modified for ETERNUS CS HE is shown below. The entries relating to
ETERNUS CS HE 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 281) 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",
"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",
173
Solaris
"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",
"IBM
ULTRIUM-TD2",
"IBM Ultrium-2",
"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
###PROPERTY SECTION
XVXA-1
=
XEXB-8505
=
XEXB-8900
=
XMammoth2
=
XVXA-2
=
Xtor
=
XC1537A
=
XC1557A
=
XC5683A
=
XC5713A
=
XC7438A
=
XUltrium
=
XHP-ULT-2
=
X03570C
=
X03590B
=
X03590E
=
CLASS_LTO2
=
X123107
=
XDLT7000
=
XDLT8000
=
XDLT4000
=
XDAT
=
XSDAT
=
XULTRIUM
=
XSDX-500C
=
X9490
=
X9840
=
XSUNDLT7K
=
174
"XC5683A",
"XC5713A",
"XC7438A",
"XUltrium",
"XHP-ULT-2",
"X03570C",
"X03590B",
"X03590E",
"CLASS_LTO2",
"X123107",
"XDLT7000",
"XDLT8000",
"XDLT4000",
"XDAT",
"XSDAT",
"XULTRIUM",
"XSDX-500C",
"X9490",
"X9840",
"XSUNDLT7K",
"XS400";
1,0x36,0,0xde39,1,0x80,0;
1,0x35,0,0x8e39,2,0x15,0x8c,1;
1,0x29,0,0x19e39,1,0x7f,0;
1,0x35,0,0x19e39,1,0x28,0;
1,0x36,0,0x19e39,2,0x80,0x81,1;
1,0x36,0,0x18619,1,0x00,0;
1,0x34,1024,0x9639,4,0x00,0x13,0x24,0x3,3;
1,0x34,1024,0x9639,4,0x00,0x13,0x24,0x3,3;
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
1,0x34,1024,0x19639,4,0x00,0x13,0x24,0x3,3;
1,0x36,0,0x19639,4,0x00,0x00,0x00,0x40,3;
1,0x36,0,0x29639,4,0x00,0x00,000,0x42,3;
1,0x24,0,0x618639,1,0x00,0;
1,0x24,0,0x618639,1,0x00,0;
1,0x24,0,0x618639,1,0x00,0;
1,0x3b,0,0x45863d,2,0x40,0x42,1;
1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
1,0x38,0,0x9639,4,0x82,0x83,0x84,0x85,2;
1,0x38,0,0x9639,4,0x84,0x85,0x88,0x89,2;
1,0x38,0,0x9639,4,0x80,0x81,0x82,0x83,2;
1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,3;
1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,3;
1,0x36,0,0x19639,4,0x00,0x00,0x00,0x00,3;
1,0x36,0,0x9639,4,0x30,0x8c,0x8c,0x8c,1;
1,0x24,0,0x1867d,1,0x00,0;
1,0x36,0,0x19679,1,0x00,0;
1,0x36,0,0x19639,4,0x82,0x83,0x84,0x85,2;
Solaris
XS400
=
1,0x3b,0,0x45863d,3,0x00,0x40,0x42,2;
###END OF PROPERTY SECTION
###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;
175
Solaris
# target=13 lun=0;
# 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
176
Solaris
5.2.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.2.14 Extensions for NetBackup
For NetBackup the sg driver must be installed in accordance with the NetBackup Media
Manager Device Configuration Guide from Veritas.
5.2.15 Sun StorEdge SAN Foundation Software (SFS/Leadville)
5.2.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.
!
1
CAUTION!
SFS/lpfc mixed operation has not been released.
https://sdlc1a.sun.com
177
Solaris
The following HBAs with the SFS software package can be used in the Primepower systems of Fujitsu:
●
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.0B301 can be obtained from the websites for service
partners (Home ➟ Partner Portal ➟ Service partner portal ➟ PRIMEPOWER ➟ Software ➟
Documents ➟ control DVD Products ➟ Solaris Platform ➟ FSC Basic Extensions ➟ Updates).
Installing this packages results in the /kernel/drv/st.conf file for the released tape
drives and for the drive emulations of ETERNUS CS HE being modified.
1
https://partners.ts.fujitsu.com/com/service/primepower/software/Documents/control%20DVD%20Products/Solaris%20Platform/
FSC%20Basic%20Extensions/Updates/Readme.htm
178
Solaris
The following configuration files must be adjusted for SFS/Leadville operation using
ETERNUS CS HE:
●
/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
ETERNUS CS HE 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 ETERNUS CS HE 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 an ETERNUS CS HE 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 parameter is set for an emulation running
in ETERNUS CS HE:
Xtor=1,0x36,0,0x18619,1,0x00,0;
179
Solaris
5.2.15.2
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 ETERNUS CS HE 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
:
:
180
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.
181
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.
-------------------------------------------------------------------------------------
182
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`/.
183
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)
184
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.
185
Solaris
In this case the WWPN 10000000c9553c6e represents the WWPN of the ETERNUS
CS HE ICP ports. 16 Tape Devices (LUNs 0-15) and one Changer Device are configured
on this ETERNUS CS HE port.
At this time the ETERNUS CS HE 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
186
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):
187
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):
188
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 emulation of the type FSC/CentricStor
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.
189
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.2.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
190
<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.
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
Solaris
[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
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
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
191
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).
192
Solaris
# cfgadm -al
Ap_Id
Type
Receptacle
Occupant
Condition
disk
disk
fc-fabric
tape
tape
tape
tape
tape
tape
tape
tape
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
configured
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
…
c5::50060e80102547d5
c5::50060e80102557b1
c6
c6::10000000c98fb824
c6::10000000c98fc0f0
c6::10000000c98fc26a
c6::10000000c98fc4cc
c6::10000000c98fc4f8
c6::10000000c98fc648
c6::10000000c98fc656
c6::10000000c98fca2e
Displays a list of all WWNs which the host sees at the local HBA port c6.
# cfgadm -al -o show_SCSI_LUN
c2
c2::10000000c955abfb,0
c2::10000000c955abfb,1
c2::10000000c955abfb,2
c2::10000000c955abfb,3
c2::10000000c955abfb,4
c2::10000000c955abfb,5
c2::10000000c955abfb,6
c2::10000000c955abfb,7
fc-fabric
tape
tape
tape
tape
tape
tape
tape
tape
connected
connected
connected
connected
connected
connected
connected
connected
connected
configured
configured
configured
configured
configured
configured
configured
configured
configured
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
unknown
Lists which LUNs the host sees at the local HBA port c2 for WWN 10000000c955abfb.
# fcinfo hba-port -l
HBA Port WWN: 2100001b3286446b
OS Device Name: /dev/cfg/c8
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.2.2
FCode/BIOS Version: BIOS: 1.24; fcode: 1.26; EFI: 1.8;
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 2000001b3286446b
193
Solaris
Link Error Statistics:
Link Failure Count: 0
Loss of Sync Count: 0
Loss of Signal Count: 0
Primitive Seq Protocol Error Count: 0
Invalid Tx Word Count: 0
Invalid CRC Count: 0
HBA Port WWN: 2101001b32a6446b
OS Device Name: /dev/cfg/c9
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.2.2
FCode/BIOS Version: BIOS: 1.24; fcode: 1.26; EFI: 1.8;
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 2001001b32a6446b
Lists which WWNs and attributes the local HBA ports have.
# fcinfo remote-port -ls -p
10000000c941e28d
Remote Port WWN: 10000000c955abfb
Active FC4 Types: SCSI
SCSI Target: yes
Node WWN: 20000000c955abfb
LUN: 0
Vendor: IBM
Product: ULTRIUM-TD2
OS Device Name: /dev/rmt/47n
194
Solaris
LUN: 1
Vendor: IBM
LUN: 2
Vendor: IBM
LUN: 3
Vendor: IBM
Queries which remote WWNs and which associated LUNs the host sees via its own HBA
port with WWN 10000000c941e28d.
5.2.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.2.16 HBAnyware
With ETERNUS CS HE Version 5.0 the HBAnyware Command Line Interface can be used
to maintain the internal FC infrastructure.
For additional information please refer to following URL:
http://www-dl.emulex.com/support/utilities/hbanyware/41/hbanyware.pdf
!
CAUTION!
Please contact our Second/Third Level Support before you modify anything with our
FC HBAs!
195
HP-UX
5.3 HP-UX
5.3.1 General
●
HP-UX B11.00 is required for connection to ETERNUS CS HE.
(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
ETERNUS CS HE. 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.3.2 Restrictions
The system only supports 8 LUNs per partner WWN.
The system must not be connected to an FC switch with the 8 domains.
i
5.3.3 Useful commands:
–
–
–
–
–
–
–
sam (configuration network, setting up device nodes etc.)
swinstall, swverify (software installation)
fcmsutil /dev/td0
ioscan (scanning the I/O ports – shows ETERNUS CS HE)
lsdev
xstm
see the chapter “Useful commands and information” on page 395
5.3.4 Links
HP: Migration to Fabric
196
HP-UX
5.3.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 ETERNUS CS HE 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).
197
IBM-AIX
5.4 IBM-AIX
5.4.1 Restrictions
The standard driver OST (Other SCSI Tape) generates device nodes, which cannot
compress.
In CS V2.1 or higher, compression can be turned on explicitly for an LD.
i
5.4.2 Important settings and information
●
●
3590 Emulation on the ETERNUS CS HE 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
198
●
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.4.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 395
199
IBM-AIX
5.4.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 ETERNUS CS HE.
Ê
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.
200
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.
201
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.4.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.
202
IBM-AIX
5.4.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 CS 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:
203
IBM-AIX
5.4.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
204
6 ETERNUS CS HE in Windows
The following restriction applies for the Windows operating system: A maximum of 32 LUNS
can be released for Windows in ETERNUS CS HE. If more LUNS are configured for
Windows in ETERNUS CS HE, 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.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.
205
Important settings and information
ETERNUS CS HE in Windows
6.2 Important settings and information
●
Windows can only see drives of one type on ETERNUS CS HE.
●
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 ETERNUS CS HE for 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 ETERNUS CS HE backups, for example, can no longer be used
with the Microsoft MM2 driver 5.2.3790.0 (01.10.2002)!
●
206
For the emulations IBM 3590 or LTO-2, the corresponding drivers must be installed.
These can be downloaded from http://www.ibm.com/support/us/en/.
7 ETERNUS CS HE on NAS systems
7.1 General information on saving using NDMP
ETERNUS CS HE 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.
207
NetApp
ETERNUS CS HE on NAS systems
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.4 Useful commands
sysconfig -av
sysconfig -t
reboot
show hardware configuration
show tapes
reboot NetApp system
7.2.5 Update Installation in ETERNUS CS HE
NetApp filers crash during update installation of ETERNUS CS HE
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.
208
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
7.3.3 Configuration
7.3.3.1
Configuration in ETERNUS CS HE
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.
209
Celerra
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 ETERNUS CS HE.
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
Data-Mover 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
nRestore
PAX
16
16
writeToArch
PAX
1
1
writeToTape
PAX
1
1
nThread
PAX
64
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'
210
current
0
4
1
''
'8859-1'
configured
v4OldTapeCompatible
bufsz
Celerra
NDMP
NDMP
1
128
1
256
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
convDialect
NDMP
'8859-1'
scsiReserve
NDMP
1
dialect
NDMP
''
includeCkptFs
NDMP
1
md5
NDMP
0
forceRecursiveForNonDAR
NDMP
0
snapTimeout
NDMP
5
bufsz
NDMP
128
snapsure
NDMP
0
v4OldTapeCompatible
NDMP
1
current
4
'8859-1'
1
''
1
0
0
5
128
0
1
configured
256
211
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
212
8 Tape management systems
8.1 General
General information is provided below concerning the use of ETERNUS CS HE together
with tape management systems, e.g. NetWorker, NetBackup.
The tape management systems currently supported can be found in the support matrix for
ETERNUS CS HE:
https://partners.ts.fujitsu.com/teams/cpc/Support%20Matrix/ETERNUS_CS_
Support_Matrix.xlsx
The following robotic emulation types (virtual library services) are available with
ETERNUS CS HE:
●
VDAS: emulation of DAS/ACI Server
●
VACS: emulation of ACSLS Server
●
VJUK: emulation of SCSI jukebox
The following tape drive emulation types (logical drives) are available with ETERNUS CS
HE:
●
IBM/IBM 3590E1A
●
STK/T9840B
●
IBM/LTO Ultrium 2/4
●
EXABYTE/Mammoth2
●
FSC/CentricStor
The tape drive types and robotic types which are supported by the tape management
systems are listed in the support or compatibility information for the products.
Since ETERNUS CS HE emulates real hardware tape drives, SCSI jukeboxes and tape
libraries, most of the configuration steps needed are identical to the ones needed for real
hardware. Differences are described in the sections below.
213
General
Tape management systems
Consult the tape management systems documentation for a description of how to configure
and use the tape drives and robotics. Most of the systems provide command line or
graphical interfaces for this purpose.
Before configuration of the tape management system can be performed, all tape devices
and robotics must be accessible on the host systems. Check this with the commands and
interfaces provided in the operating system, see chapter “ETERNUS CS HE on UNIX-type
systems” on page 153 for more information.
If the VDAS or VACS emulation is used, a network connection between ETERNUS CS HE
and the host system must be established. This can be checked with the ping command.
Furthermore the name of the host system must be resolvable on the VLP/IUP/VTC of the
ETERNUS CS HE, and the name of the VLP/IUP/VTC must be resolvable on the host
system. Check this using the nslookup command if DNS is used, or search for the host name
in the hosts file.
The maximum IO block size supported by ETERNUS CS HE is 256 KB. Check the
operating system and tape management system documentation for which IO block sizes
are supported. Changes in the default configuration of the management systems might be
needed.
i
The operations import and export of volumes are not supported by ETERNUS CS
HE.
ETERNUS CS HE provides various sizes for logical volumes. The standard value is 900
MB, but other values between 2 GB and 200 GB are selectable. If compression is performed
by ETERNUS CS HE, the amount of data which will fit on a logical volume increases
accordingly (the standard compression ratio for tapes is 1:2; compression with ETERNUS
CS HE is at least as good.). Given the total capacity, there is a simple relationship between
the size and the number of logical volumes: The larger the volumes are, the less volumes
are required, and the smaller the volumes are, the more volumes are required.
The larger the logical volumes are, the more the following negative effects increase:
●
Logical volumes may match physical volumes less well, and appending volumes may
increase the amount of wasted space on physical tape.
●
The utilization of the Tape Volume Cache (TVC) may decrease.
●
The restoration of even a small amount of data may require a large amount of data to
be read back into the TVC.
The number of virtual volumes should be calculated carefully since maintaining very large
numbers of volumes might be a very expensive process which consumes a great deal of
resources on the host systems.
214
NetWorker (EMC and Fujitsu)
8.2 NetWorker (EMC and Fujitsu)
8.2.1 Documentation
Information about NetWorker can be found in the following documentation:
●
Fujitsu NetWorker on the Internet:
https://ts.fujitsu.com/products/software/management/storage/networker/index.html
●
Fujitsu NetWorker Manuals:
http://manuals.ts.fujitsu.com
●
Fujitsu Networker Compatibility Guides:
https://partners.ts.fujitsu.com/com/products/storage/software/emc_sw/networker/back
up_basics/Pages/default.aspx
●
EMC Networker in EMC POWERLINK (personal account required):
https://powerlink.emc.com
8.2.2 Configuration
As a preparation step to configure ETERNUS CS HE, the NetWorker command inquire
should be invoked. The inquire command provides a list of all attached devices with their
device node, inquiry string, serial number, and other information. This list is very useful in
order to find out what ETERNUS CS HE devices are mapped to what device nodes.
Like a real SCSI jukebox or tape library, ETERNUS CS HE is configured in NetWorker using
the jbconfig command. jbconfig creates a jukebox resource along with device resources for
the virtual drives to store all configuration and status data related to the respective
ETERNUS CS HE system. If the VJUK emulation is used, proceed in the same way as for
real SCSI jukeboxes (see the NetWorker Administrator's Guide).
When a VDAS or VACS jukebox is configured, jbconfig asks for the following information:
●
Configure Mode: enter the choice for configuring an STL silo
●
Silo type: depending on the ETERNUS CS HE robotic emulation chosen:
– VDAS: enter the choice for DAS/ACI
– VACS: enter the choice for ACSLS
●
Jukebox Name: enter a name of your choice. Only restriction: there is not already another
jukebox with this name.
●
Silo Server: IP node name of the VLP/IUP/VTC in the external LAN.
215
●
STLI interface library:
– Fujitsu NetWorker:
– VDAS: enter libstlaci_cs.so, except in firewall environments where libstlaci_fw_cs.so
is used
– VACS: enter libstlstk_cs.so
– EMC NetWorker: confirm the prompted default value
●
The other information requested by jbconfig must be answered in the same way as for
real tape libraries.
Some values of the NetWorker Device Resource must be adapted to ETERNUS CS HE configurations:
●
Device block size
The maximum IO block size supported by ETERNUS CS HE is 256 KB. The default
block size used by NetWorker for the tape drive type 3590 Magstar is higher than this
value. All NetWorker hosts in a data zone (i.e. the NetWorker server and the server's
storage nodes) must use the same block size. For every virtual drive the block size
attribute of all device resources must be changed to the same value.
●
CDI
Set CDI to Not used in the device resources of all ETERNUS CS HE logical drives.
This is because virtual tape drives in ETERNUS CS HE do not require cleanings or
tape-drive-specific error recovery. On the other hand, CDI enabled can cause
NetWorker to malfunction because the SCSI interface of virtual tape drives in
ETERNUS CS HE does not completely comply with the SCSI interfaces of real tape
drives.
NetWorker supports two functions which allow more powerful use of ETERNUS CS HE:
●
Prefetching
Prefetching is a feature which is important for recover commands. It accelerates
NetWorker recover commands from multiple volumes if not all volumes are in the TVC
of ETERNUS CS HE and have to be read from physical tape. The prefetch feature is
implemented as a script which is invoked by the NetWorker notification mechanism and
which tells ETERNUS CS HE to read the required logical volumes from physical tape
into the TVC in advance so that they are already back in the TVC when NetWorker
issues the mount command. It must be observed that the prefetch feature accelerates
mounts from the 3rd volume on; it has no effect on the mount times for the 1st and 2nd
volumes.
Templates for the prefetch scripts (for EMC NetWorker as well as for Fujitsu NetWorker)
and a readme about how to install and configure the script are available at ftp:ftp.fujitsusiemens.com/pub/nsr/add-on.
216
●
Fast Mount
If NetWorker mounts a logical volume for relabeling and the logical volume is not in the
TVC, ETERNUS CS HE reads the logical tape back from physical tape into the TVC,
which is useless since NetWorker will immediately invalidate all this data by relabeling
the tape. In detail, things are more complicated: NetWorker actually reads some tape
data even in the case of (re-)labeling. What NetWorker reads are the first 2 blocks on
the tape which hold the volume label. NetWorker reads the label blocks in order to avoid
overwriting valid backup data by mistake. These two label blocks fit into a portion of data
at the beginning of a logical volume which is TVC-resident, i.e. which is never purged
from the TVC. So access to the NetWorker label never requires restoration of a logical
volume from physical tape.
FastMount is an additional function in the silo interface between NetWorker and
ETERNUS CS HE. In ETERNUS CS HE, FastMount is implemented in such a way that
volumes are mounted without recovering any data from physical tape. If FastMount is
available, NetWorker mounts a volume to be (re-)labeled by means of FastMount rather
than using the ordinary mount function.
The FastMount feature is available for the VDAS and VACS emulations together with
Fujitsu NetWorker. EMC NetWorker supports this feature with the VACS emulation only.
Further information about NetWorker can be found in the following documentation:
●
Fujitsu NetWorker on the Internet:
https://ts.fujitsu.com/products/software/management/storage/networker/index.html
●
Fujitsu NetWorker Manuals:
http://manuals.ts.fujitsu.com
●
Fujitsu Networker Compatibility Guides:
https://partners.ts.fujitsu.com/com/products/storage/software/emc_sw/networker/back
up_basics/Pages/default.aspx
●
EMC Networker in EMC POWERLINK (personal account required):
https://powerlink.emc.com
217
NetBackup (Symantec)
8.3 NetBackup (Symantec)
Currently only the NetBackup Data Center product supports the connecting of robots via
LAN.
8.3.1 Documentation
●
Release Notes Symantec NetBackup
●
Release Notes Symantec NetBackup
●
Installation Guide Symantec NetBackup BusinesServer
●
System Admistrator’s Guide Symantec NetBackup DataCenter for UNIX
●
User’s Guide Symantec NetBackup for UNIX
●
Installation Guide Symantec NetBackup DataCenter for UNIX
●
Media Manager System Admistrator’s Guide Symantec NetBackup DataCenter for
UNIX
●
Media Manager Device Configuration Guide Symantec NetBackup for UNIX
●
User’s Guide Symantec NetBackup for Microsoft Windows 95/98/NT/2000
●
Troubleshooting Guide Symantec NetBackup for UNIX
●
Installation Guide Symantec NetBackup BusinesServer for PC Clients
The manuals are available on CDs or on the Internet at: http://www.symantec.com.
8.3.2 Installation
Perform a standard NetBackup installation as referenced in the NetBackup Installation
Guide for the NetBackup version you use.
Example from Solaris
218
–
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’.
8.3.3 Configuration
●
Recommended configuration tools: bpadm, jnbSA and jbpSA.
●
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.
●
To define devices under NetBackup follow the instructions of the Device Config Guide
for NetBackup version and Operating System.
Notes / Features
●
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.
●
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.
●
The Leadville driver from SUN StorEdge SAN Foundation Software (SFS) can also be used
on Solaris systems (see section “Sun StorEdge SAN Foundation Software
(SFS/Leadville)” on page 177).
●
/kernel/drv/st.conf on Solaris (see section “Contents of the file st.conf for Solaris”
on page 173) must be adapted appropriately for ETERNUS CS HE. After Version
2.0B20 of the SMAWdevsp package has been installed, no further settings are required.
It is important that the following parameter is set for an emulation running in ETERNUS
CS HE:
Xtor=1,0x36,0,0x18619,1,0x00,0;
●
On Solaris, the sg driver from Symantec must also be installed. See: Media Manager
Device Configuration Guide from Symantec.
●
/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. All media servers connected to VACS also need
an ssi client, i.e. for Windows media servers connected to ETERNUS CS HE, Libattch
software needs to be installed.
219
●
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 ETERNUS CS HE. 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
ETERNUS CS HE.
●
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 238).
●
It is recommended that you do not configure the same device (virt. device in ETERNUS
CS HE) 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 401 (VDAS) or page 405 (VACS).
●
The ACS numbers configured in ETERNUS CS HE must be strictly ascending.
NetBackup(W2K3) would not be executable if, for example, ACS=0 is used for BS2000
and ACS=2 for NetBackup. Instead, use ACS=0 for BS2000 and ACS=1 for NetBackup.
●
A scratch pool must be configured in cmd_proc for NetBackup and the virutal volumes
must be accommodated there:
> define pool 0 5000 1
# define poolid 1 for max. 5000 volumes
einrichten
ACSSA> set scratch 1 NBU000-NBU999 # Add volumes to pool
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
ETERNUS CS HE.
220
●
The Virtual Tape Devices on the ETERNUS do not allow buffering higher than 256KB
Do not use tape buffers size more than 256KB (262144) in:
8.3.3.1
–
%install_path%/netbackup/db/config/SIZE_DATA_BUFFER
for Unix and Linux
–
%install_path%\netbackup\db\config\SIZE_DATA_BUFFER
for Windows
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
i
Only the name of ETERNUS CS HE 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
221
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.
The following processes must run on the LMF client (the programs vmps and bpps
belong to NetBackup):
bash-2.03# vmps
root 5329
1 0 14:37:55 ?
0:00 vmd
root 5323
1 0 14:37:55 ?
0:00 /usr/openv/volmgr/bin/ltid
root 5373 5323 0 14:37:59 ?
0:00 avrd
root 5376
1 0 14:37:59 ?
0:00 lmfcd
root 5372 5323 0 14:37:57 ?
0:00 lmfd
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.3.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.symantec.com) were used under Solaris for quality assurance.
222
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 ETERNUS CS HE the fixed port is defined as follows:
GXCC -> Configuration -> VirtualLibraryService ->
VACS : RPC-Port Selection UserDefined
RPC-Port:
!
8.3.3.3
2001
Caution!
Communication is still handled via RPC!
Port 111/UDP may not be locked.
Template for supporting SCRATCH mount
When using an LV just for writing (FAST-MOUNT) NetBackup does not communicate this to
ETERNUS CS HE 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
223
ssh $HOST 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
ssh -n $HOST1 vlmif conf -r -n -v $VSN1
done
8.3.3.4
Sample screens
Activity Monitor Daemons:
224
225
Activity Monitor Processes:
226
Policies Overview:
Add a New Policy:
227
Change Policy - Attributes:
228
Change policy - Add Client:
Add Schedule - Attributes:
229
Add Schedule - Start Window:
230
Add a New Drive:
231
Add a New Robot:
232
New Storage Unit:
233
Select Inventory Robot:
234
Robot Inventory:
235
Robot Inventory Done:
236
Inventory vm.conf:
237
8.3.4 System specific
8.3.4.1
Windows 2000
●
NetBackup Datacenter from Version 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.
●
By default a Windows machine does not have ACS Deamon (ACSD) build in the
Operating System. Because of that a Windows Host is unable to communicate with an
ACS Robotic through the LAN. ETERNUS CS HE just emulates an ACS Robot.
Therefore it is necessary to install & configure SUN LibAttach sofware on the Windows
NetBackup Server.
SymantecConfiguration settings NetBackup/Windows:
238
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\host
the name of the VLP)
s
drive Emulation
EXABYTE/Mammoth2
Treiber: Mammoth2 V2.10.0.0
von EXABYTE
alternative emulation
IBM/IBM 03590E1A
Driver: halfinch.sys from
Symantec
file version 5.0.1.1
Driver version: 4.0.1381.1
Caution: The Halfinch Driver
can only be installed after
installing NetBackup.
8.3.4.2
Windows 2003
●
By default a Windows machine does not have ACS Deamon (ACSD) build in the
Operating System. Because of that a Windows Host is unable to communicate with an
ACS Robotic through the LAN. ETERNUS CS HE just emulates an ACS Robot.
Therefore it is necessary to install and configure SUN LibAttach sofware on the
Windows NetBackup Server.
●
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.
●
Symantec requests
–
–
–
–
8.3.4.3
NetBackup version:
Library in ETERNUS CS HE:
Media type:
Emulation in ETERNUS CS HE:
V6.0 MP4
VACS (libattach 1.4.1 required)
HCART
IBM Magstar 3590E1A
Reliant UNIX
NetBackup does not support Reliant UNIX from FSC. Only Reliant from Pyramid is
supported, but no quality assurance is provided by ETERNUS CS HE.
8.3.4.4
Solaris
●
NetBackup Datacenter from Version 3.4.1
●
The NetBackup Datacenter Patch NB_34_2 must be used.
Configuration settings of NetBackup/Solaris:
Drive type
media type
HCART
Device node (no rewind device) /dev/rmt/*cbn
with ACSLS robot control:
robot type
ACS Automated Cartridge System
with DAS robot control
robot type
TLM Tape Library Multimedia
drive emulation
FSC/CentricStor
c = optional
compression
239
●
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.
●
The sg driver must also be installed. See: Media Manager Device Configuration Guide
Symantec NetBackup for UNIX, Linux, and Windows.
●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 Symantec NetBackup, T.Daude 28.02.02 Symantec 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 Symantec NetBackup, damit Sockets bereits nach
# 30 sek. vom System zu Wiederverwendung freigegeben werden
# (Default: 4 min)
# T. Daude, Symantec Software GmbH
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 30000
8.3.4.5
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
240
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
Type of emulation in ETERNUS CS HE
FSC/CentricStor
241
8.3.4.6
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.3.4.7
/dev/rmt*.1
with ACSLS robot control: robot type
with DAS robot control: robot type
FSC/CentricStor
Linux
●
242
Device node (no rewind device)
ETERNUS CS HE is supported on Linux Redhat in NetBackup V6.0 MP5 and higher.
Data Protector
8.4 Data Protector
8.4.1 Documentation
The documentation for Data Protector is shipped on CD together with the product.
8.4.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 ETERNUS CS HE)
Unlimited Slot Libraries Extension for STK ACSLS or EMASS/GRAU DAS
8.4.3 Miscellaneous
Up to Version 4.1 the software was marketed under the name Omniback.
As ETERNUS CS HE 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.
243
Data Protector
8.4.4 Installation in UNIX systems
8.4.4.1
8.4.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 ETERNUS CS HE in Data Protector
Note 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.
244
8.4.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 ETERNUS CS HE 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
ssh CentricStor-VLP 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.
This script can lead to corrupted data because if between the creation list of media by DP
and the truncate of the volumes by CS, DP could write to one volume of the list and then
CS truncate the volume. When the list is created, the volumes should be freezed.
!
CAUTION!
When using the script it may happen that data is written to volumes and truncated
to the stub shortly after that, leading to corrupted data. Therefore only use this script
when a time interval without backups is guaranteed. If this is not possible, use the
script shift-lager-free.x to move volumes to the FREE pool temporarily (see
“Scripts for pool maintenance” on page 247).
245
Data Protector
8.4.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
ssh 130.11.10.81 vlmif prefetch -v $VSN >>$PREMOUNT_LOG 2>&1
done
date >>$PREMOUNT_LOG
echo "-----------------------E-N-D-----------------------"
>>$PREMOUNT_LOG
echo "---------------------------------------" >>$PREMOUNT_LOG
8.4.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.
246
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
247
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
248
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
ssh $VLP 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 "
Holger.Mustermann@firma.de < /tmp/sc.$$
rm /tmp/sc.$$
# Delete PIDFILE
rm $PIDFILE
249
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
250
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
251
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
252
8.4.4.6
Data Protector
Configuration as StorageTek ACS library
1. Define library name (device name) and select robot as StorageTek ACS library.
253
Data Protector
2. Specify ACSLM host name.
The ACSLM host name is the name of the ETERNUS CS HE machine on which VACS
is running (normally the VLP).
Select Abort for Busy drive handling and Use volser as medium label on initialization.
254
Data Protector
3. Specify CAP.
CAP is 0 for ETERNUS.
4. Specify media type.
T3840/T4890/T9490 for FSC-CentricStor emulation.
255
Data Protector
5. Configuration of library completed.
Click yes to start drive configuration.
6. Specify device name for first drive.
256
Data Protector
7. Select data drive for first drive.
Use serial number to identify LUN and drive index.
8. Enter drive index (ACSID).
257
Data Protector
9. Select Advanced Options to change block size to 256 kB.
10. Configure next drive if required.
258
8.4.4.7
Data Protector
Configuration as a GRAU-DAS library
1. Select robot as GRAU-DAS library.
2. Configure GRAU-DAS library.
259
Data Protector
The DAS Server is the name of the ETERNUS CS HE machine on which the VDAS process
is running.
260
Data Protector
3. Specify CAP.
CAP is 0 for ETERNUS.
4. Specify media type.
The IBM 3590-E1A emulation is used in this example.
261
Data Protector
5. Configuration of library completed.
Click Yes to start drive definition.
6. Enter the required drive name.
262
Data Protector
7. Select the required drive from the drop down box.
Identify the LUN by drive serial number.
8. Enter the DAS library device name of the drive.
263
Data Protector
9. Change block size in Advanced Options for performance.
264
8.4.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 ETERNUS CS HE.
1. Select Add Volsers.
265
Data Protector
2. Specify volume prefix and interval.
It is only possible to specify an interval beginning with 1 (e.g. APP001). If a start with 0 is
required (APP000) this can only be done using the CLI.
266
Data Protector
3. View of specified volumes.
4. Right click one or more volumes and select Format.
267
Data Protector
5. Select the media pool.
6. Skip this step.
268
Data Protector
7. Check Force operation and specify medium size, in this case 900MB, then click Finish.
269
Data Protector
8.4.5
8.4.5.1
VJUK configuration
Supported slots
Only 1500 slots are supported per VJUK emulation of DataProtector.
8.4.5.2
Autoconfiguration
An autoconfiguration menu is available for VJUK. With Devices ➟ Autoconfigure Devices... you
can call a self-explanatory autoconfiguration procedure.
8.4.5.3
Configuration of the robots under AIX
With DataProtector, AIX can only be used as a client.
8.4.5.4
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.
270
8.4.5.5
Data Protector
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
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.4.5.6
Configuration of the robot devices under Windows
After ETERNUS CS HE 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.
271
Data Protector
8.4.5.7
Configuration of a library under Solaris
Library - General:
272
Data Protector
Library - Control:
273
Data Protector
Library - Repository:
274
Data Protector
Library - Settings:
275
Data Protector
Drive - General:
276
Data Protector
Drive - Drive:
277
Data Protector
Drive - Settings:
278
Data Protector
8.4.6 Miscellaneous
8.4.6.1
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 Quantum (robot manufacturers). Also see: http://www.quantum.com.
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.4.6.2
Details about the possible causes of connection problems with VDAS and other troubleshooting advice is given in section “Possible problems and solutions” on page 401.
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 405.
8.4.6.3
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.
279
Data Protector
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.4.7.1
Windows
●
When using the ACSLS interface, the software product LibAttach from StorageTek must
be used.
●
When using the DAS interface, copy:
a) Copy aci.dll, winrpc.dll or winrpc32.dll to \winnt\system32 and
<OMINBACK_HOME>\bin.
a) Run Portinst to install Portmapper.
a) Restart.
a) Under SERVICES, see if Portmapper and RPC services are running.
●
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)
with ACSLS robot control model
StorageTek ACS Library
with DAS robot control model
GRAU DAS Library
drive emulation
FSC/CentricStor
Device nodes: SCSI<Adapter>:<Bus>:<ID>:<LUN>[C|N]
C=compressed, N=nonrewinding
●
280
From Version 6.1 on Server 2008 only 64 bit versions are supported as Cell Manager.
8.4.7.2
Data Protector
Reliant UNIX
●
Not currently released.
●
ETERNUS CS HE is only supported as a media agent without robot control.
●
Data Protector/RelUNIX settings:
media type
Device Nodes
drive emulation
8.4.7.3
FSC/CentricStor
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 or VJUK
281
Data Protector
8.4.7.4
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.
You can check if the lib is correct using these commands:
cd /opt/omni/lbin
./bma –version
You can check the contents the libaci.sl using the following command:
# file libaci.sl
Output:
libaci.sl: ELF-32 shared object file - IA64
●
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/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
282
Depending on the software: There is application software which works with non-rewind nodes. Other software requires rewind nodes.
8.4.7.5
8.4.7.6
Data Protector
IBM-AIX
●
ETERNUS CS HE 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
Support for ETERNUS CS HE:
●
under VJUK
●
no ADS or DAS
●
as server with Linux x86_64
●
as Client with Linux IA64
283
Tivoli / TSM
8.5 Tivoli / TSM
8.5.1 Documentation
The documentation is shipped on CD together with the product. It includes the following
manuals:
●
Tivoli Storage Manager for Windows - Quick Start
●
Tivoli Storage Manager for Windows - Administrator's Guide
●
Tivoli Storage Manager for Windows - Administrator's Reference
●
Tivoli Storage Manager - Messages
You can obtain this documentation from the following Internet links:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
TSM 5.5:
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.help.doc/w
elcome.htm
8.5.2 Installation and configuration
8.5.2.1
TSM installation
At least version 4.2.1.7 is required.
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
284
8.5.2.2
Tivoli / TSM
TSM configuration
The complete configuration was set with the help of command line tools. .
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 NOHUP ./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
IBM Tape Device Driver
In ETERNUS CS HE you are recommended to configure "IBM 3590E1A" or "LTO Ultrium
2" as the emulation for the Virtual Drives (VTDs).
With the exception of AIX, the appropriate IBM Tape Device Driver should be installed on
the UNIX and Windows platforms.
The IBM Tape Device Drivers can be downloaded from the following FTP site:
ftp://ftp.software.ibm.com/storage/devdrvr
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 in TSM V4.x:
DEFINE DRIVE <name of library> <name of drive> DEVICE=<device file>
ACSDRVID=<ACS drive ID>
In Version 4.x a tape must be mounted in the drive in the drive definition.
In Version 5 and higher no tape needs to be mounted in the drive definition. The statements for defining a drive are as follows:
DEFINE DRIVE <name of library> <name of drive> ACSDRVID=<ACS drive ID>
DEFINE PATH <server name> <name of drive> SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=<name of library> DEVICE=<device file>
285
Tivoli / TSM
The device files of the drives can be determined using the tapelist tool of the IBM Tape
Device Driver.
Example (LTO Ultrium 2 emulation)
/opt/IBMtape/tapelist
Instance
Special File
Device
Serial Number
TGT/LUN
Ucode
World Wide NN
World Wide PN
Dev Phy Path
Path Type
: 93
: /dev/rmt/63st
: ULTRIUM-TD2
: C56AAD0100
: 525824/0
: 4770
: 10000000C9470544
: N/A
:/devices/pci@82,2000/lpfc@1/fp@0,0/st@w10000000c9470544,0
: N/A
Define device class:
QUERY DRIVE enables the defined drives to be viewed and the device type which is
available to be determined.
Depending on the type of VTD tape emulation in CentricStor, the following device types
are recognized:
VTD Emulation
IBM 3590E1A
LTO Ultrium 2
i
DEVTYPE
3590
LTO
If the IBM Tape Devie Driver is not installed under Solaris, the VTD emulation
IBM 3590E1A of the DEVTYPE GENERICTAPE must be used in order to use the
operating system’s tape driver.
The device classes are then created as follows:
●
286
For VTD-Emulation LTO Ultrium 2:
DEFINE DEVCLASS <Name der Device Klasse>
LIBRARY=<Name der Library>
DEVTYPE=LTO
FORMAT=ULTRIUM2
ESTCAPACITY=2000M
MOUNTRETENTION=60
MOUNTWAIT=60
MOUNTLIMIT=DRIVES
Tivoli / TSM
●
For VTD-Emulation IBM 3590E1A:
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
●
Add to storage pool
DEFINE VOLUME <name of pool> <name of volume>
287
Tivoli / TSM
●
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.5.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.5.2.4
Examples
Configuration
DEFINE LIBRARY CentricStor LIBTYPE=ACSLS ACSID=1
In TSM V4.x:
DEFINE DRIVE CentricStor V20C DEVICE=/dev/rmt/1st ACSDRVID=1,0,0,12
In TSM V5.x:
DEFINE DRIVE CentricStor V20C ACSDRVID=1,0,0,12
DEFINE PATH TSMSERVER1 V20C SRCTYPE=SERVER DESTTYPE=DRIVE
DEVICE=/dev/rmt/1st LIBRARY=CentricStor
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=LTO FORMAT=ULTRIUM2
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
288
Tivoli / TSM
Handling the volume
LABEL LIBVOLUME CentricStor SEARCH=yes VOLRANGE=TIV01,
TIV20 CHECKIN=private, OVERWRITE=yes
DEFINE VOLUME CentricPool TIV01
... to
DEFINE VOLUME CentricPool TIV20
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.5.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™
289
Tivoli / TSM
8.5.3.1
Gresham installation
Version 6.2.1.0 was tested under HP-UX, and Version 8.0.0.0 under Solaris/SPARC.
The following package is played in:
edt.6210.hpux.tar.gz Gresham DistribuTape or
edt-acsls.8000.sol-sparc.tar.gz
EDT 6.2.1.0 under HP-UX:
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
EDT 8.0.0.0 under Solaris:
The package was unpacked using gunzip and then extracted using
tar -xvf edt-acsls.8000.sol-sparc.tar. It was installed using the setup script.
The directory in which the software is installed by default is /opt/GESedt-acsls
8.5.3.2
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 396 and section “Virtual libraries” on page 397).
Then start the script with the parameter both. This starts the SSI process, and simultaneously initializes DistribuTape.
290
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 0 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 .
Sample configuration of EDT V6.2.1.0 and EDT V8.0.0.0, 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
291
Tivoli / TSM
Sample configuration EDT 8.0.0.0:
LICENSE PERM <LicenseKey>
LIBRARY <LibraryName>
LIBTYPE ACSLS
POOL <PoolID>
CLIENTID <ClientName>
DRIVE <DeviceFile> ACS_<ACSDriveID>
END
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.
292
ACSLS
ACSLS must be specified as LibType. This specification must be entered
directly after LibraryName.
Pool ID
Must agree with the Pool ID set by cmd_proc.
ClientName
By default the system’s host name is specified here.
Device file
Full path for the device file of the drive. The following devices are used in
HP: /dev/rmt/*m. Provided the IBMtape driver is installed, the following
devices are used under Solaris: /dev/rmt/*st
ACS drive ID
Drive ID with which the drive is recognized in the library, e.g. 0,0,0,0.
Tivoli / TSM
A graphical administration console, Gresham Control Center, is supplied with Gresham
DistribuTape Version 8.0.0.0. This is started using the script
/opt/GESedtcc/admin/EDTCC.ksh
The library can be configured using the Control Center.
Example
293
Tivoli / TSM
8.5.3.3
TSM configuration
In the description below a distinction is made between TSM 4.2 with Gresham 6.2.1.0 and
TSM 5.5 with Gresham 8.0.0.0 when the configuration settings differ.
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
–
in TSM 4.2:
DEFINE LIBRARY <name of library> LIBTYPE=external
EXTERNALManager=/<Gresham installation path>/bin/elm
–
in TSM 5.5:
DEFINE LIBRARY <name of library> LIBTYPE=external lanfree=yes obeymountretention=yes
DEFINE PATH <name of TSMserver> <name of library> srctype=server desttype=library EXTERNALManager='/<Gresham installation
path>/bin/elmdt'
Defining a device class
–
in TSM 4.2 with IBM 3590E1A tape emulation in ETERNUS CS HE
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>
–
in TSM 5.5 with LTO Ultrium 2 tape emulation in ETERNUS CS HE
DEFINE DEVCLASS <name of device class> LIBRARY=<name of library>
DEVT=LTO FORMAT=ULTRIUM2 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>
294
Tivoli / TSM
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>
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.5.3.4
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
Gresham EDT Version 6.2.1.0:
Contents of /opt/OMIdtelm/bin/elm.conf:
LICENSE PERM 1444291050
LIBRARY CENTRICSTOR
POOL 100
MSG MDRVSTAT MDRVERR MPOOLSTAT /opt/OMIdtelm/bin/msg.out
295
Tivoli / TSM
DIAG ESUB EDRV ECNV EELM /opt/OMIdtelm/bin/dbg.out
DRIVE /dev/rmt/36m ACS_2,0,0,4
END
Gresham EDT Version 8.0.0.0:
Contents of /opt/GESedt-acsls/bin/elm.conf
LICENSE PERM 1444291050
LIBRARY CENTRICSTOR
LIBTYPE ACSLS
POOL 100
CLIENTID mch004tx
DRIVE /dev/rmt/36st ACS_2,0,0,4
END
Configuration check
elm_testlibdesc -l CENTRICSTOR
Configuration for TSM 4.2 (IBM 3590E1A emulation in ETERNUS CS HE)
DEFINE LIBRARY CentricStor LIBTYPE=external
EXTERNALManager=/opt/OMIdtelm/bin/elm
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=3590 FORMAT=DRIVE
ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=4
UPDATE COPYGROUP standard standard standard DESTINATION=CentricPool
296
Tivoli / TSM
Configuration for TSM 5.5 (LTO Ultrium 2 emulation in CentricStor)
DEFINE LIBRARY CentricStor LIBTYPE=external LANFREE=yes
OBEYMOUNTRETENTION=yes
DEFINE PATH MCH004TX CentricStor SRCTYPE=server DESTTYPE=library
EXTERNALManager='/opt/GESedt-acsls/bin/elmdt'
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=LTO FORMAT=ULTRIUM2
ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=4
UPDATE COPYGROUP standard standard standard DESTINATION=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.5.4 Configuring a SCSI library on AIX via VJUK
8.5.4.1
General
The VJUK emulation is supported as of version CS 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 ETERNUS CS HE.
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.
297
Tivoli / TSM
8.5.4.2
Configuration steps
1. ETERNUS CS HE 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
ETERNUS CS HE:
# 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
298
i
Tivoli / TSM
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
299
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
300
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
ETERNUS CS HE 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.
!
8.5.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.
301
Tivoli / TSM
8.5.5 LANfree configuration without Gresham
8.5.5.1
Prerequisites
Software
TSM Server + Agents + Client
Version: 5.3.2.0
Emulation in ETERNUS CS HE
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.5.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.
302
8.5.5.3
Tivoli / TSM
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
303
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
Ê
304
dsmsta
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 ...
Ê
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
305
Tivoli / TSM
8.5.5.4
Ê
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
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
306
Tivoli / TSM
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.
8.5.5.5
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.5.5.6
If an agent crashes during reservation it is not always recovered automatically upon
booting. In ETERNUS CS HE 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.5.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 *
307
Tivoli / TSM
8.5.7.1
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.5.7.2
LIBTYPE
ACSLS
EXABYTE/Mammoth2
Reliant UNIX
TSM does not support Reliant UNIX.
8.5.7.3
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:
308
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/*cn
drive emulation
FSC/CentricStor
8.5.7.4
Tivoli / TSM
HP-UX
The ACSLS controller can only be addressed via Gresham EDT.
Configuration:
8.5.7.5
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/cXtXdXBEST
drive emulation
FSC/CentricStor
IBM-AIX
Configuration:
8.5.7.6
DEVTYPE
3590
LIBTYPE
ACSLS
Device nodes
/dev/rmt*
drive emulation
3590E1A
Linux
TSM does not support Linux.
309
CA ARCserve Backup
8.6 CA ARCserve Backup
8.6.1 ARCserve
The initial release for operation with ETERNUS CS HE has taken place for:
●
BrightStor ARCserve r11.1 for Windows
●
BrightStor ARCserve r11 for Windows
●
BrightStor ARCserve r11.1 for Linux
The following ARCserve versions can also be operated with ETERNUS CS HE:
●
BrightStor ARCserve Backup r11.5
●
CA ARCserve Backup r12.5 SP1
8.6.2 ETERNUS CS HE
A prerequisite for operation with ARCserve is as least Version 3.0 as of K834.1. Only
CS 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 (ETERNUS CS HE native)
The Logical Drives can be assigned the following device names in the GXCC ➟ Configuration
➟ Logical Drives menu under Emu/Inquiry Data:
310
●
EXABYTE/Mammoth2
●
FSC/CentricStor (ETERNUS CS HE native)
●
IBM/IBM03590E1A
●
IBM/LTO Ultrium 2
●
IBM/LTO Ultrium 4
●
STK/T9840B
●
STK/T9840D
CA ARCserve Backup
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:
●
ARCserve r12.XX:
25 LVs
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 volume
of a backup job here.
8.6.3 Backup server
The backup server on which ARCserve runs is connected to ETERNUS CS HE via FC. A
controller which has been released for the Primergy and the ETERNUS CS HE 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.
8.6.4 Startup and configuration of virtual libraries
8.6.4.1
Configuring a SCSI library (VJUK)
1. Configure the virtual library on ETERNUS CS HE 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 a VJUK is configured in ETERNUS CS HE (GXCC ➟ Configuration ➟ Logical
Drives menu), the first LUN is automatically reserved for the controller and thus displayed as disabled. Any number of tape drives can then be assigned to this controller.
Their LUNs are assigned automatically.
When an Emulex controller is used the elxcfg or HBAnyware program can be employed
to configure the Emulex controller or to check whether the controller has recognized all
the ETERNUS CS HE LUNs.
311
CA ARCserve Backup
2. The operating system performs a device recognition. 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.
3. Start the ARCserve device configuration.
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.
4. Start the ARCserve manager.
5. 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.
8.6.4.2
Using an ACSLS library
The Sun Microsystems program LibAttach must ne used for library control for ACSLS
library support on Windows systems.
In addition, the ARCserve Enterprise option must be installed. Configuration is performed
by means of enterprise module configuration. The assignment of tape drives to libraries
and the assignment of tape volumes is performed using the coordinates predefined by
ETERNUS CS HE.
8.6.5 Import or export under ARCserve
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
ETERNUS CS HE; 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.
312
Time Navigator
8.7 Time Navigator
8.7.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.7.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.
313
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:
314
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 .
315
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.
316
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:
317
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 ETERNUS CS HE.
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).
318
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 ETERNUS CS HE 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.
319
VJUK emulation
8.8 VJUK emulation
●
Connection of the virtual robotics VJnn and of its virtual tape devices is implemented
via an FC switch.
●
Up to 48 virtual jukeboxes VJnn are supported per ETERNUS CS HE.
●
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 ETERNUS CS HE.
●
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.
320
●
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 ETERNUS CS HE and zoning on
the FC switch have been configured, the LUNS/Tapes 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.
●
No robotics driver must be installed specially for the FSC/CS-TL 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 21th of
June 2006 on Windows 2008).
VJUK emulation
●
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.
Alternatively, in CS V4 and higher logical volumes can be configured on a TVC-resident
basis (LVG attribute Cache Policy with the value NO_BACKUP_TO_TAPE or
TVC_RESIDENCE) or a Disk Library Edition (models ETERNUS CS500DL and
ETERNUS CS1000DL) can be used.
321
NAS filer - NetApp
8.9 NAS filer - NetApp
Miscellaneous
The distinctive feature of the configuration is that the version of NDMP used (version 3)
does not support tape cloning.
ETERNUS CS HE 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
●
ETERNUS CS HE 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 “NetWorker
(EMC and Fujitsu)” on page 215).
Configuration of NetApp devices e.g. nrst31a (cmp, norewind) as NDMP devices.
Useful commands
322
sysconfig -av
show adapter
sysconfig –t
show tapes
reboot
reboot filer
DiskXtender for Windows
8.10 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.
The expansion for DiskXtender for Windows in ETERNUS CS HE is available as of Release
3.1D SP01.
ETERNUS CS HE should first be configured and connected with the system on which
DiskXtender for Windows is running so that the ETERNUS CS HE 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 ETERNUS CS HE system should be connected to the DiskXtender
for Windows system at fibre channel level (if necessary select zoning on the FC switch).
8.10.1.1
Virtual Library Services
ACSLS is used for communicating with DiskXtender for Windows, i.e. VACS on the
ETERNUS CS HE 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
323
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.10.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:
324
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 ETERNUS CS HE 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.10.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 /etc/opt/fsc/CentricStor/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.10.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.
325
8.10.1.5
Mixed Media Info
The /etc/opt/fsc/CentricStor/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 /opt/fsc/CentricStor/mixed_media.default file is available as a template for
manual creation of the /etc/opt/fsc/CentricStor/mixed_media.conf file.
The /etc/opt/fsc/CentricStor/mixed_media.conf file is (re)activated by VACSreinit.
8.10.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 327) but is not required for
operation. MediaStor should only be installed for this purpose, not configured.
326
8.10.3 DiskXtender for Windows configuration
i
8.10.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 ➟ Programs ➟ 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
ETERNUS CS HE 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 324) - are stored in the
/etc/opt/fsc/CentricStorf/vtls.conf file.
327
8.10.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 324)
<LibDevName 2nd character> 1 (see section “Logical Drives” on
page 324)
<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.
328
8.10.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 324).
●
An alternative to Media Copy is provided by the Multi-Target Feature of DiskXtender for
Windows.
●
When any change is made to the ETERNUS CS HE configuration for any logical drive
(vtd on ICP), all tape device emulations are stopped and restarted in ETERNUS CS HE
V3.1D throughout the ICPs when Distribute and Activate takes place. When Distribute and
Activate takes place in ETERNUS CS HE 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 of logical drives in ETERNUS CS HE
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.
329
CommVault Simpana (Galaxy)
8.11 CommVault Simpana (Galaxy)
8.11.1 General
●
CommVault Simpana has been released since 6.1.0 Service Pack 4 on Windows.
For the use with ETERNUS CS HE the following CommVault Simpana 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))
If the Media Agent to ETERNUS CS HE is connected via the library interface ACSLS
(VACS), LibAttach is required on Windows.
Via the ETERNUS CS HE function VACS ACCESS Control ON the logical volumes have
to be specified, which CommVault Simpana is allowed to use.
i
●
CommVault Simpana accesses all volumes, which it sees in the library.
It is recommended to set the timeout value for mount to 90 minutes.
By the following request, which appears by VACS and VJUK Library, click on Yes.
330
8.11.2 ACSLS library in Simpana with VACS
In the library configuration for CommVault Simpana the Work Pool Number 0 and the Volume
Range NoScratch have to be specified. This leads CommVault Simpana to scratch a released
volume before reusing it. Different to a manual Erase/Scratch in CommVault Simpana migrated logical volumes are not recalled from physical drives when an automatic Scratch Mount
of a recycleable data medium is performed in a ACSLS-Library with VACS.
A prerecycle script is not necessary.
Configuring the ACSLS library
331
332
333
334
Configuring drives
335
336
337
338
339
Assigning the VACS coordinates for the drives via Drive ID
340
341
Configuring the mount timeout
342
8.11.3 SCSI library with VJUK
●
In ETERNUS CS HE a higher LUN can be specified for VJUK than the LUNs of the virtual tape drives (in the example tape drives LUN 0 through 31 and VJUK for ADIC Scalar 10K on LUN 32).
●
The service Removable Storage (RSM Removable Storage Management) must be stopped and disabled in Windows (Administrative Tools).
●
The original driver from Microsoft (see section “VJUK emulation” on page 320; 8th item)
is enabled automatically in Windows for the virtual robotics VJUK in ETERNUS CS HE
In the device manager is the Library as „Unbekannter Medienwechsler/Unknown Medium Changer” displayed.
Configuring the SCSI library and tape drives
343
The Select Drives list shows the virtual tape drives which are physically recognized in Windows. The checkmark may not be used as a selection character for those tape drives which
are not under corresponding VJUK control in ETERNUS CS HE or which are not to be employed with VJUK in the Simpana application (in the example only the 16 tape drives from
LUN 0 through LUN 15 are relevant for VJUK and are to be configured in Simpana).
344
When automatic detection takes place by means of Exhaustive Detection of the SCSI library
and of the tape drives, at least one virtual volume from the volume range of the associated
VJUK must exist in ETERNUS CS HE beforehand as Exhaustive Detection mounts/unmounts
a volume on each device:
In the example precisely one volume is mounted/unmounted on all 16 selected tape drives
(see above) one after the other via VJUK in the case of Exhaustive Detection. In this case no
data is written (in contrast to Validate drive for configured tape drives (see section “Further
information” on page 361).
345
Configuring the SCSI library and all tape drives in the
Simpana context menu Configure
346
The Drive ID is assigned automatically by Simpana when the tape drives are configured:
347
348
Configuring the mount timeout
349
Displaying the number of devices, slots and media in the library
350
8.11.4 ADIC DAS Library in Simpana with VDAS
i
The configuration of an ADIC DAS library in CommVault Simpana with VDAS requires
at least ETERNUS CS HE V5.0A SP01!
Configuring the ADIC DAS library
Prior to configuring, make sure that the "NobleNet Portmapper for TCP", installed with the
QUANTUM DAS-Client(ACI) software, is started:
i
Potential services for ACSLS/VACS (StorageTek LibAttach, SUN RPC Portmapper)
are from experience incompatibel with the NobleNet Portmapper and therfore must
be deactivated.
The following configuration steps are illustrated using the example of an ADIC DAS Library
in Simpana 8.0 SP05 on Windows 2003 (in the example mch003sx) with ETERNUS CS HE
(in the example VDAS on VLP eule).
351
352
Ê
Set Windows environment variables DAS_SERVER and DAS_CLIENT:
Ê
Perform detection of virtual ETERNUS CS HE tape devices (e.g. IBM LTO Ultrium 4
emulations) via FC-SW at mch003sx:
353
Ê
Adding LAN library in dialog window Add IP Library with the following entries:
Library Type:
ADIC DAS (position (1) in the screenshot below)
Library Host Name:
Name of the MediaAgent of the Simpana servers where the
drives are configured (position (2) in the screenshot below)
Drive Count:
Number of drives to be configured in Simpana in the ADIC DAS
library (postion (3) in the screenshot below)
i
Also less drives, than target (VDAS) devices are configured in ETERNUS CS
HE at the FC controller target, can be specified.
1
2
3
354
Ê
Configuring library controller in dialog window Library and Drive Configuration:
355
Ê
356
Assigning detected tape devices to empty library device slots ("Move to …"):
357
Ê
358
Opening dialog window Drive Properties and entering its VDAS-LibDev name (as
specified in ETERNUS CS HE) in the Drive ID field for each tape drive:
i
The ETERNUS CS HE VDAS-LibDev names that are automatically
detected by Simpana are offered in the Drive ID list.
Compare these with the "serial number" as shown in ETERNUS CS HE
(XTCC on ICP, vtls.conf).
!
In the Drive ID field the LibDev name must be entered that exacty
corresponds to the LUN or the device node.
Ê
Configuring each tape drive:
359
Ê
After completely configuring the library and its drives in Simpana, it is useful to verify
them by means of Simpana with the so called "drive validation". In doing so, media must
be available in the ADIC DAS library in Simpana, in order to tentatively perform a
Write/Read.
i
360
In ETERNUS CS HE it can be configued via "Virtual Library Services VDAS"
which media, i.e. logical volumes of the ETERNUS CS HE, are detected by
Simpana in its ADIC DAS library or can be accessed.
8.11.5 Further information
●
It is recommendable to check the configuration of the tape drives by means of Simpana
drive validation (Validate drive context menu writes and reads) before performing a backup.
●
Number of data transfer operations for a media agent:
When messages containing Total number of data transfer operations on the
MediaAgent exceeds the maximum allowed value appear, it may be necessary to increase
the parameter Maximum number of parallel data transfer operations in MediaAgent Properties
➟ Tab General.
The default value is generally 25 (see CommVault Simpana 7.0 Manual Features - Media Management, page 338 and 342).
361
i
●
When checking the configuration, ensure that the maximum number of parallel
data transfer operations (see above) is limited to the default value of 25 in the
case of jobs for drive validation.
If a very large number of logical volumes results in the CommCell Console GUI slowing
down or hanging - e.g. when the slots are displayed - the size of the Java memory for
the GUI call of the CommCell Console can be increased. For this purpose the -Xms512m
and -Xmx1024m parameters are added below the icon CommCell Console GUI ➟
Properties ➟ Shortcut tab in the Target field in the example (screenshot CommVault in
Windows):
"C:\Program Files\Java\jre1.6.0_06\bin\javaw.exe" -Duser.language=en Duser.country=EN -Xms512m -Xmx1024m -jar cv.jar mch005nx 8401 -oemid=1
362
●
ETERNUS CS HE V4.1A and higher supports SCSI-3 Persistent Reserve IN/OUT for
physical drives of type IBM LTO Ultrium 2, IBM LTO Ultrium 4, STK T9840Ba, and
STK T9840D at the ETERNUS CS HE frontend.
If Simpana shall use SCSI-3 Persistent Reserve IN/OUT (to reserve or release drives
across different paths or different hosts), this can be activated for LAN and SCSI
libraries in window Library Properties ➟ tab Drive in the entry area SCSI Reservation for
physical tape volumes of the above mentioned type (position number (1) in the screenshot below).
1
2
363
●
Being a system for storage virtualization ETERNUS CS HE does not support cleaning
at the frontend. Therefore in window Library Properties ➟ Tab Drive the options in the
entry area Enable Auto-Cleaning (position number (2) in the above screenshot) must remain deactivated.
Cleaning should also be deactivated in the menu item Tools ➟ Control Panel ➟ Media Management. In window Media Management Configuration the value for Ignore media and drive
use count thresholds for Virtual Tape Libraries (position nummer (1) in the screenshot below) can be changed from 0 (no) to 1 (yes).
1
364
Additionally the parameter Low Watermark for media in the library must be set to 0 for
Cleaning Media (position number (1) in the screenshot below). This suppresses the error
messages which appear in the EventViewer. The number of data media in the cleaning
pool [cleaning media] within the library [STK ACSLS 1] lies below the required minimum
number of [1].
1
365
366
●
To minimize the logical volumes on physical tapes at the ETERNUS CS HE backend, in
the Simpana dialog window Spare Group Properties the spare media selection criteria
can be set to Use recycled media first instead of keeping the default value Use new media
first.
●
The Block Size must not be higher than 256KB. For more information have a look at
CommVault Manual section „Performance Tunables for Media Management“.
367
VTCP
8.12 VTCP
VTCP (Virtual Tape Control Program) is a backup application which runs on Fujitsu
mainframe servers. It was developed specially for using an ETERNUS-VT600 system,
which is equivalent to CS V3.1.
A Fujitsu document describes how the service engineer must adjust ETERNUS VT600 (CS
V3.1D) after it has been installed in a Fujitsu mainframe environment to permit it to work
with VTCP.
8.12.1 Incompatibility problem in ETERNUS CS HE V4.0A and higher
The introduction of the FHS (Filesystem Hierarchy Standard) and the standard security features in CS V4.0A and higher not only removed the basis for the configuration adjustments
described in the document mentioned above, but also required changes to the VTCP software.
To solve this problem, in CS V4.0A and higher the vtcp-config tool was provided which permits exceptions to FHS compliance (reintroduction of the /usr/apc/... paths) and cancels some of the security features (enabling of rexec and setting up a vtcp user account
which has no password). Use of the tool as described in the section below enables the current VTCP software to work directly with ETERNUS CS HE.
8.12.2 Use of the vtcp-config tool
The two operations in the original Fujitsu document
adduser vtcp
passwd vtcp ...
must be replaced by
/opt/fsc/CentricStor/etc/vtcp-config -configure
This implements the required measures on both VLPs. In addition, it must be ensured that
IP reverse lookup on the VLPs of ETERNUS CS HE functions for the host systems which intend to use this interface.
The following command can be used to delete the vtcp user account and to disable rexec on
both VLPs:
/opt/fsc/CentricStor/etc/vtcp-config -deconfigure
368
VTCP
The current status of the VTCP configuration on the ISP concerned can be queried with the
command
/opt/fsc/CentricStor/etc/vtcp-config -status
The following files and directories are affected when the tool is used:
/etc/xinetd.d/rexec
/etc/hosts.allow
/etc/passwd
/etc/shadow
/home/vtcp
369
Backup Exec 2010
8.13 Backup Exec 2010
Backup Exec 2010 is a backup application for Windows environments.
The current hardware compatibility list can be found at:
http://www.symantec.com/docs/TECH137050
The current software compatibility list can be found at:
http://www.symantec.com/docs/TECH137682
Backup Exec (abbreviated to BE below) can also be administered on a distributed basis, i.e.
used on various servers and administered via a console. This makes BE highly scalable.
8.13.1 Configuring ETERNUS CS HE
The following parameters should be configured in ETERNUS CS HE:
8.13.1.1
●
●
Logical Drives
●
LV Size
Only SCSI libraries are supported by BE. FSC/CS-TL should be used as the VJUK inquiry
string to ensure that ETERNUS CS HE is recognized correctly in BE as a virtual library. A
maximum of 20,000 slots should be used, otherwise the backup server is severely slowed
down.
Virtual Library Services - Configuration with various volume ranges
370
8.13.1.2
Backup Exec 2010
Logical Drives
BE supports up to 79 drives per virtual library when the corresponding licenses are installed. No additional drives are assigned to the library.
The emulations supported are shown in the support matrix.
i
8.13.1.3
The current support matrix for the service can be found on the internet at:
https://partners.ts.fujitsu.com/teams/cpc/Support%20Matrix/ETERNUS_CS_Support_Matrix.xlsx
LV Size
The maximum LV size should remain restricted to 2 GB to prevent a mount timeout. If the
LV is not in the cache after 450 seconds, the library is reset by BE and flagged as offline.
When major restore activities take place, prefetch scripts should be used up front so that
the corresponding LVs are available in the cache.
8.13.2 Adjusting Backup EXEC
The following properties should be adjusted in Backup EXEC:
●
Barcode rules
●
Device drivers
●
Licenses
371
Backup Exec 2010
8.13.2.1
Barcode rules
ETERNUS CS does not support the use of "barcode rules". This must be disabled in the
library properties.
Library properties
372
8.13.2.2
Backup Exec 2010
Device drivers
The current Symantec device drivers should be installed. This can be done using the "Tape
Device Configuration Wizard". You should make sure beforehand that all tape devices can
be seen in the Windows device manager (Start-> Run-> devmgmt.msc). The BE "Tape Device Configuration Wizard" can then be started via "Tools-> Configure Devices-> Configure
Tape Devices".
1. Select "Install tape device drivers".
373
Backup Exec 2010
2. The wizard is started. Click "Next" and click "Next" again in the subsequent window.
374
Backup Exec 2010
3. Select the options as described below:
375
Backup Exec 2010
4. Hardware scan
Here the hardware is searched for which can be (re)installed. Click "Details" to display a list
containing the envisaged actions:
Confirming by clicking "Next" in the preceding window causes the actions to be executed
and the wizard to be terminated.
376
8.13.2.3
Backup Exec 2010
Licenses
To guarantee the full support of BE for ETERNUS CS HE, the "Virtual Tape Library Unlimited Drive Option" license should be installed. This enables 79 drives to be used in a virtual library.
After the license has been installed, the ETERNUS CS HE devices should look like this:
377
BakBone NetVault®:Backup
8.14 BakBone NetVault®:Backup
Documentation
Documentation can be found on BakBone Website.
http://www.bakbone.com/product_documentation.php
Preconditions for VACS
To use VACS with NVBU install these components:
●
BakBone VaultShare Plugin Module for ACSLS
●
LibAttach 1.4.3 (for Windows Server 2008) x86 32bit
REHL x86_64
To start the NVBU-GUI install following additional packages:
378
●
glibc*.i686.rpm
●
nss-softokn-freebl*.i686.rpm
●
libICE*.i686.rpm
●
libXp*.i686.rpm
●
libuuid*.i686.rpm
●
libXmu*.i686.rpm
●
libSM*.i686.rpm
●
libxcb*.i686.rpm
●
libXt*.i686.rpm
●
libXau*.i686.rpm
●
libX11*.i686.rpm
●
libXext*.i686.rpm
●
openmotif22*.i686.rpm
ACSLS coordinates and LibDevName
In ETERNUS CS HE logical volumes are based for ACSLS in a home-location. To identify
the home-location of your LVs log on to CLI and start cmd_proc. Enter query volume all
or for a specific volume query volume AK0000.
Example output
ACSSA> query volume AK0000
2011-01-19 13:30:38
Volume Status
Identifier Status
Current Location
AK0000 home
1, 1, 1, 1, 1
Type
3490E
At first you need to identify the first two numbers (acs and lsm). Afterwards you can
configure your Logical Drives with the same ACS and LSM. It is important to configure the
right LibDevName. Otherwise NVBU will not be able to handle drives and media.
i
If there are ACS and LSM differently configured in ETERNUS CS HE, the homelocation of LVs will be set automatically to 1,1,1,1,1.
For additional information see also „LibDevName in the Service Manual“ (GXCC
Main Menu ➟ Configuration ➟ Logical Drives ➟ LibDevName).
The name comprises four decimal digits, the so-called coordinates, separated by ','.
The following rules apply here:
1. coordinate (ACS): 0 - 255, 1 is recommended as the default
2. coordinate (LSM): 0 - 23
3. coordinate (PANEL): 1 - 10, 12 -15
4. coordinate (DRIVE): 0 – 19
i
This means NVBU supports a maximum of 280 drives with VACS (14 panels * 20
drives).
379
Library Configuration
NVBU displays all ACS Numbers (see section above). Choose the correct one defined by
the home-location of your LVs.
To add a drive choose an empty Bay (1) and select your drive (2).
1
2
After the drives were added, they need to be mapped.
380
1
2
3
4
1. enter the LSM
2. enter the Panel
3. enter the drive number
4. the name is optional, e.g. the name of the emulation for better troubleshooting
381
Drive Configuration
Your drives can be configured as follows:
1
3
2
1. Disable “Cleaning Tapes Supported”
2. Set the “Media block size (Kb)” to 256, which is the maximum for ETERNUS CS HE, to
increase performance.
3. Decreasing this value will result in disabled tape drives to become up faster again.
382
4
4. Disable “Issue a load command to start cleaning cycle”
383
NVBU Configuration
In NVBU Configurator (Start ➟ BakBone Software ➟ NetVault Backup ➟ NVBU Configurator)
select “Media Manager” Tab.
Enable „Use barcodes as labels“.
Set “Unavailable device retry interval (mins)” to 1. This reduces the drive’s offline time.
Media request timeout
Here you can define how long NVBU has to wait for media. It is defined by each backup job
but can be saved in a policy. This is a possibility to avoid timeouts while restoring migrated
LVs which want to be reused.
384
9 ETERNUS CS HE NAS functionality
9.1 Network connection of the ETERNUS CS HE NAS frontend
9.1.1 Use of IP pools
ICPs of an ETERNUS CS HE cluster on which the NAS services NFS and/or CIFS are configured are also referred to as NAS ICPs.
Clients which use the NAS services of an ETERNUS CS HE must have an IP connection
to at least one NAS ICP in order to be able to mount the NAS filesystems or file groups exported from ETERNUS CS HE.
To achieve load distribution and high availability of the data paths between NAS clients and
NAS ICPs, the IP addresses of the NAS ICPs which can be reached from NAS clients must
be configured in IP pools. Each IP pool contains a group of IP addresses and assigned network interfaces. ETERNUS CS HE guarantees the availability of all IP addresses of an IP
pool for NAS clients as long as at least one network interface which is assigned to the pool
is operable.
Interfaces of the type ACCESS can also be configured on a NAS ICP. However, these interfaces are not used for connecting NAS clients and are not described below.
The following rules apply for creating IP pools:
●
An IP pool must contain at least one IP address.
●
An IP pool may only contain IP addresses in the same IP subnetwork.
●
If an IP pool contains fewer IP addresses than network interfaces which are assigned
to it, interfaces can remain unused.
●
If an IP pool contains more IP addresses than network interfaces which are assigned to
it, there will be interfaces to which more than one IP address is assigned.
●
A network interface can be assigned to only one IP pool.
●
Different IP pools must contain addresses in different IP subnetworks.
385
ETERNUS CS HE NAS functionality
When multiple IP pools are used, a corresponding number of subnetworks must exist in the
customer network. It is, however, not necessary to define more than one IP pool just to be
able to use all the network interfaces which are available on the NAS ICPs. The rules for
configuring IP pools enable multiple network interfaces of a NAS ICP to be assigned to the
same IP pool and consequently to the same IP subnetwork.
9.1.1.1
Load distribution in IP pools
The data traffic on the incoming side is distributed over the available interfaces of a NAS
ICP by the NAS clients making equal use of the IP addresses of the IP pools with their assigned interfaces. Routing settings on the NAS ICP are responsible for the distribution of
the outgoing data to the interfaces of a NAS ICP. When effective load distribution is achieved on the incoming side, this is also the case on the outgoing side.
NAS
Client 1
192.168.17.20
ICP1
192.168.17.100
192.168.17.101
NAS
Client 2
192.168.17.21
IP Pool
NAS
Client 3
192.168.17.22
NAS
Client 4
192.168.17.23
192.168.17.102
192.168.17.103
ICP2
The figure shows a configuration comprising four NAS clients, each of which uses a particular IP address to communicate with a total of two NAS ICPs of the ETERNUS CS HE.
Two addresses of an IP pool are configured on each NAS ICP. The NAS ICPs transfer packets to clients via the same interfaces that were used to receive the clients’ jobs.
9.1.1.2
High availability of the data inputs
When a network interface fails, ETERNUS CS HE initially attempts (if possible and if so configured) to switch the IP address of the failed interface to an alternative local interface on
the node (local failover) which belongs to the same IP pool as the failed interface. In this
case the active data stream is retained.
386
If no such interface exists, ETERNUS CS HE switches the IP address to an interface of the
same IP pool on another node (global failover). In this case the active data stream is interrupted.
In both cases it is ensured that the IP addresses assigned to the services are always available.
9.1.1.3
Load balancing via DNS server configuration
This section describes how DNS load balancing can be used to enable a Network Attached
Storage which is implemented in the network by multiple servers to look like a service with
a single point of access.
Method of operation
DNS permits multiple IP addresses to be assigned to one name. If such a name is queried
by a resolver, the DNS server always returns all known IP addresses, but in a changing order. The resolver then has the responsibility of deciding which IP address is actually used.
The strategy according to which a DNS server specifies the order can be configured in the
case of bind-compatible name servers. Three variants are possible in the case of BIND: cyclical, random and permanent. With the permanent variant the IP addresses are returned
in the order in which they are contained on the name server.
The DNS query by the client is only issued the first time a connection is set up. If the client
knows the IP address, it always communicates with the server of this IP address when
further queries are issued. Access to another server is excluded. The problem of session
binding, in other words when a particular client always has to communicate with the same
server, as is the case for CIFS and NFS, does not occur with DNS.
Configuring ETERNUS CS HE NAS with DNS load balancing
ETERNUS CS HE NAS with DNS load balancing requires a DNS server in the environment.
The IP address of each NAS data input must be entered in this with the same name.
387
client1
.....
clientN
DNS
LAN
ICP1
.....
ICPn
VLP
ETERNUS CS HE
The procedure for doing this is presented taking a DNS on Microsoft Windows Server 2003
as an example:
1. Start -> Administrative Tools -> DNS
2. In the console tree, right-click the applicable forward lookup zone and click New Host.
3. In the Name text box, type the DNS computer name for the new host.
4. In the IP address text box, type the IP address for the new host.
5. Select the Create associated pointer (PTR) record check box to create an additional
pointer record in a reverse zone for this host, based on the information you entered in
Name and IP address.
6. Click Add Host to add the new host record to the zone.
i
388
To avoid the need to enter the NAS clients in the ICP’s host file, it makes sense to
configure the DNS server for the ISPs as well. This can also be done from the VLP.
9.1.1.4
Restrictions for clients which are reached only via routers
All IP packets to systems outside the subnetworks to which a NAS ICP has direct access
are sent to the default router.
i
If the default router is part of the subnetwork of an IP pool, appropriate routing settings on the NAS ICP guarantee that the corresponding IP addresses (with the assigned interfaces on the NAS-ICP) including NAS clients, which are outside the
subnetworks to which a NAS ICP has direct access, can be used as target addresses without restriction.
!
CAUTION!
Currently only one default router can be configured per NAS-ICP.
9.1.2 Detailed settings for network interfaces
ETERNUS CS HE V5 enables connection parameters of the Link Layer of a network interface to be set explicitly. By default these settings are specified between the network interface and the switch by means of autonegotiation. In certain cases, however, it can be necessary to set the parameters manually, e.g. when autonegotiation is not possible or fails.
In the configuration window Network Interfaces the autonegotiation specification must then
be set to NO for the interface concerned. Furthermore, the connection speed and duplex
mode must be specified explicitly.
i
These setting options exist for all network interfaces, not just for those in an IP pool.
9.1.3 Releasing filesystems and file groups
NAS filesystems or NAS file groups are released on the NAS ICPs. If a NAS filesystem in
the ETERNUS CS HE configuration has not been assigned to an HSM service, it is released
completely. If, on the other hand, it is managed by an HSM service, separate releases are
performed for all file groups of the filesystem.
ETERNUS CS HE generates the release with permanently predefined attributes.
389
9.1.3.1
NFS releases
NFS releases are listed in the /etc/exports file on every NAS ICP. ETERNUS CS HE generates entries there with the following attributes:
<fsname>
*(rw,fsid=<id>,secure,no_subtree_check,sync,root_squash)
<fsname> is the name of the filesystem or file group. This name may not be changed. Nor
may the administrator add or remove releases.
<id> stands for a particular numeric filesystem ID determined by ETERNUS CS HE. Each
entry in /etc/exports contains its own <id> which the administrator may not change.
The remaining release attributes, on the other hand, may be changed. Following this action
the NFSD component must be stopped and then restarted on all NAS ICPs. The XTCC interfaces must be used to stop and start the NFSD component.
The release of the filesystem or file group is not restricted to particular users or client hosts
and should be adapted to the requirements of the customer network.
The other entries have the following meaning:
rw
The filesystem or file group is exported for the purpose of reading and writing. It
makes no sense to change this attribute, assuming that the filesystem/file group is
used as a storage location for backup and archive applications.
secure
The NFS server checks whether all client jobs are sent from privileged ports.
For security reasons you are recommended not to change this attribute.
no_subtree_check
The NFS server does not perform the check to see whether a client’s job concerns
a file which resides in an exported subtree of the filesystem. Provided applications
do not configure any hard links between filesystems of different file groups of the
same filesystem, the setting should not be changed.
sync
The NFS server executes all write jobs of NFS V2 and all commit jobs of NFS V3
synchronously, i.e. the client receives an acknowledgment only when the data has
been persistently stored on the server. The opposite setting async does achieve
higher performance of the NFS server. However, in this case the client receives an
acknowledgment for the storage of data which is not yet persistent on the server and
would be lost if the server were to crash. Whether such situations are tolerable depends on the client’s restart behavior. You are recommended to retain the sync setting.
390
no_root_squash
When the client issues a job with the privileged user ID 0, the server also executes
the job with this ID. For security reasons it may be necessary to change this setting
on root_squash. The server will then map all client accesses with user ID 0 to accesses with a nonprivileged user ID (by default the ID of the user nobody). In this
case the administrator must ensure that the applications on the NFS clients also
have access rights with nonprivileged user IDs to all the required data of exported
NFS filesystems and file groups.
9.1.3.2
CIFS releases
CIFS releases are managed in a database which is synchronized throughout the cluster.
They can be displayed using the net conf list command.
Contents of the [global] section may not be changed.
Only settings of sections which describe the releases of the various CIFS shares may be
changed (but releases may not be added or removed). As with the NFS releases you are
recommended to supplement the attributes by access lists for authorized users and/or
hosts.
CIFS shares are released by ETERNUS CS HE with the following attributes:
path = <fs_fg_path>
Path of the released filesystem or file group. This setting may not be changed.
comment = <text>
Comment text (may be changed)
read only = no
The filesystem or file group is released for reading and writing. It makes no sense
to change this attribute, assuming that the filesystem/file group is used as a storage
location for backup and archive applications.
391
9.1.4 User configuration
The users and groups whose identities are used by the NAS clients to access the released
filesystems and file groups must be configured on the NAS ICPs.
The user IDs/group IDs must be generated on all NAS ICPs, and the user IDs/group IDs
must be the same on each node.
With NFS, numeric user IDs and group IDs are used to validate the client’s accesses. These
IDs are transferred 1:1 between the client and the server. If the client uses an ID which is
not known on the server, the server maps this ID to an "anonymous", nonprivileged ID. It
does the same when access takes place with the super user ID 0, different to the default
NFS release generated by CS (see attribute “no_root_squash” on page 391).
With CIFS, the client logs in as soon as a CIFS share has been mounted. In this case an
ID must be used which is known on the server. This ID must exist on all NAS ICPs as a
Linux ID, and it must be known to the Samba server on a NAS ICP which is used as a CIFS
server before the first login of a NAS client can take place. This is done using the following
command:
smbpasswd -a <username>
When a CIFS client logs in, the user name and password are queried.
9.1.5 Protection period
In released NAS filesystems with the attribute PROTECTABLE=Yes, applications can establish a protection period by setting the file access stamp to a future point in time. However,
file protection becomes effective only when no write permission is set for the file.
i
A protected file cannot be changed or deleted before the protection period has
elapsed.
File protection can be removed before the protection period has elapsed, but only by calling
the administration command ecs-del-protection on an ETERNUS CS HE node.
392
Separating physical devices of the VTL and of the NAS
9.2 Separating physical devices of the VTL and of the NAS
backend by FC zoning
In ETERNUS CS HE systems which are used simultaneously as virtual tape libraries and
as NAS/HSM servers, the same SCSI tape drives and SCSI libraries may not be visible simultaneously for VTL IDPs and for NAS IDPs.
This assignment of the devices to FC zones and appropriate configuration of the FC switches ensure that the devices provided for VTL or NAS purposes can be accessed only by
the relevant IDP nodes.
9.3 Joint use of logical devices and libraries by the VTL and the
NAS backend
It is possible to use the logical drives and virtual libraries provided by the ETERNUS CS HE
as backend devices for the NAS/HSM services. This can be done by either cascading two
separate ETERNUS CS HE systems or by creating a 'loopback' configuration in which the
FC-ports of the NASIDP are directly cabled to FC-ports on one or more ICPs. A connection
for the library access must also be provided (either FC or LAN). The following points must
be considered when building up such a configuration.
●
The VTL resources that are to be used by the NASIDP must be completely configured
and activated before they can be configured for use in the NASIDP.
●
The library access can be implemented via FC (vjuk) or via LAN (vacs).
– The FC connection is restricted to no more than 64K LVs per vjuk however multiple
vjuk libraries can be configured.
– The LAN connection between NASIDP and the VLP must be provided externally to
the ETERNUS CS HE to enable the Auto VLP failover function.
●
The selection of the size of the LVs used has a very large effect on the access times of
files that have been migrated and must be retrieved from tape. As does the number of
LDs
●
The FC connections from the NASIDP to the ICPs should be distributed to different ICP
to ensure availability of the LDs if an ICP fails or is taken out of service.
●
The two data replication options must be considered, either TVPG with primary and
copy TVPs or the more flexible dual/triple save LVGs. The data replication factor and
data transfer requirement during the entire process being the decisive factor.
●
The additional load on the VTL cache / ICP and IDP's must be considered.
393
Joint use of logical devices and libraries by the VTL and the NAS backendETERNUS CS HE NAS
394
10 Useful commands and information
10.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.
10.2 Display of ETERNUS CS HE 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 [2].
The following instructions are addressed to host system administrators who have no
maintenance authorization for ETERNUS CS HE and need information for setting up a host
or real robot system.
395
Useful commands and information
10.3 ETERNUS CS HE 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.
10.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.
10.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.
396
10.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.
10.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.
10.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.
10.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.
397
Control of ADIC / ABBA / AML libraries
10.4 Control of ADIC / ABBA / AML libraries
10.4.1 DASADMIN
In the host
●
The host is the DAS client of VDAS in ETERNUS CS HE.
The following variables must be set and exported:
DAS_SERVER=<name or IP address of the VDAS servers (see page 397)>
e.g. DAS_SERVER=172.25.95.172
DAS_CLIENT=<name of client (=own name) in configuration>
e.g. DAS_CLIENT=suse7
In ETERNUS CS HE
●
ETERNUS CS HE (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.
●
ETERNUS CS HE (PLS) is the DAS client for DAS in AMU-PC.
In this context, DASADMIN can also be started on the PLS host of the ETERNUS CS
HE (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 ETERNUS CS HE takes over the
cleaning management for the drives.
398
In the Aan ETERMU PC
ETERNUS CS HE (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 ETERNUS CS HE drives.
After activating the configuration, there should be a function check of mount and
dismount via dasadmin. For real devices this is done from ETERNUS CS HE (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 ETERNUS CS HE (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, ETERNUS CS HE 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 397).
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
399
10.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.
400
10.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.
401
Control of the StorageTek libraries
10.5 Control of the StorageTek libraries
This describes how the physical libraries are operated.
10.5.1 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 ETERNUS CS HE 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 ETERNUS CS HE configuration.
If CLN volume groups are also shown in Global Status next to the physical volume groups
in the library, ETERNUS CS HE will administer the cleaning of the drives in the corresponding library.
10.5.2 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.
10.5.3 Partitioning a library
The SL500, SL3000 and SL8500 robots can be split into a number of partitions. The relevant chargeable license from SUN must be read in to do this. Robot control must take place
by means of an FC switch and the corresponding zoning. The partitions are configured
using the control program SL-Console with the firmware status FRS_4.40 or higher.
i
402
A firmware status of 1300 or higher is required for SL500.
10.5.4 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
10.5.5 Stopping the ssi daemon
1. Request the PID with ps –ef | grep ssi.
2. kill –15 <pid>
10.5.6 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
10.5.7 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.
403
RPC communication for ACSLS control
ACSLS client-server communication:
ACSLS
server
Request via Port
50004 →
(50000–50099
possible)
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
ACSLS client
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.
404
Information on the Cashion connection
10.5.8 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 403) blocked by a firewall ?
●
Under Windows 2000 and WIN-NT the Storagetek Libattach and PowerRPC Portmapper
services must be active.
10.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
405
Information on Fujitsu libraries
10.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
10.8 Information on LTO drives
Carrying on recording physical tapes shall only be done on physical drives of one manufacturer and only for the last and identical LTO generation. This needs to be considered for
tape drives assigned to a tape library in ETERNUS CS HE.
This means for example:
–
In the tape library TL0, to which also physical volumes of a physical volume group PVGx
are assigned, HP LTO-4 und IBM LTO-4 shall not be activated simultaneously when performing a save, because updates on devices of different manufacturers is not guaranteed.
–
In a tape library, physical drives of type IBM LTO-4 and IBM LTO-2 shall not be activated
simultaneously when performing a save.
10.9 Information on cascading with CentricStor V3.x systems
The following must be borne in mind when an CentricStor V3.x system is used as a cascading destination:
If an FC controller of an IDP of the cascading source (V5.0 system) is connected directly
(not via an FC switch) to an FC controller of an ICP of the cascading destination (V3. system), LOOP mode must be configured for every such FC controller in the V3.x system.
This change is necessary irrespective of whether this connection is used by PLS or PDS.
406
Information on cascading with CentricStor V3.x systems
The setting is made using the GXCC menu Configuration ➟ FC Boards. The FC controller’s
Mode parameter must be switched from AUTO to LOOP. Distribute and Activate must then be
executed.
407
10.10 Fibre channel switches in the SAN environment
10.10.1 Features of the FC connection
408
●
Provided that no direct point-to-point connections between host and ETERNUS CS
HE/ICP are used, all components of the SAN can be connected via a fibre channel
switch to the ETERNUS CS HE ICPs. The (brocade) switch works here with zoning
which can be configured via Telnet or Internet Explorer. For more information, see
section “Zoning” on page 409.
●
Startup sequence: The FC switch must always be switched on first and then the
ETERNUS CS HE 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.
●
Regardless of the switch type used, it is advisable to set the transmission speed
explicitly for the port employed with the portcfgspeed command.
●
If an FC switch Brocade 4100 is used internally or externally in an ETERNUS CS HE
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.
10.10.2 Zoning
10.10.2.1
Rules
–
–
The SAN switch must be independent and must not be linked to the internal switch from
ETERNUS CS HE.
There are 2 different ways to configure zoning:
1. Port zoning (recommended for ETERNUS CS HE)
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.
–
–
–
–
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.
409
10.10.2.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
Windows
NT
9
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
410
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.
10.10.2.3
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
Machine
Zone
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
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
411
Machine
Zone
active
ICP
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)
412
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
10.10.2.4
Configuration of the brocade switch via Internet Explorer
Call Administration tool:
413
Then select Zone Administration, enter login admin and password.
414
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
415
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
416
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
417
10.10.2.5
Diagnostics in the event of performance problems
When performance problems occur it may be necessary to look at the data throughput in a
ETERNUS CS HE 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.
418
Host bus adapters (HBA)
10.11 Host bus adapters (HBA)
All HBAs which are commonly used in the SAN environment and the corresponding management software are supported.
The table below provides an overview:
Manufac- Management SW
turer
URL for download information
Emulex
HBAnyware
http://www.emulex.com/downloads/emulex/cnas-and-hbas/drivers/vmware.html
Qlogic
SANsurfer FC HBA Manager
http://driverdownloads.qlogic.com
Agilent
HP
IBM
419
10.12 Example of a filter bridge for separating ETERNUS CS HE
10.12.1 General
The problem that customers want to be certain that ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE 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:
420
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 ETERNUS CS HE are described after the scripts.
10.12.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:
# 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'
421
}
get_bridges () {
ls -1 /sys/class/net | egrep '^br[0-9]'
}
reset_ebtables () {
$EBTABLES -F
$EBTABLES -t broute -F
$EBTABLES -X
$EBTABLES -t broute -X
$EBTABLES -P INPUT ACCEPT
$EBTABLES -P 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
422
}
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
}'
}
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" ] && {
423
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
[ "$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
}
424
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)
$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
425
10.12.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:
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: ""
#
426
## 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
}
# 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
427
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 ;
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;
"
10.12.4 Ports used by ETERNUS CS HE
The TCP and UDP ports used by ETERNUS CS HE are described in section 4.2.1 Network
services of the User Guide [1].
428
Long distance over an FCIP connection with Cisco Switch
10.13 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.
10.13.1 Long distance over an FCIP connection between the internal Brocade
Switches of ETERNUS CS HE with CMF
To permit a catastrophe-resident solution, two VSANs are required which should also have
two redundant connections in the WAN to ensure redundancy.
The VSANs are created via the CISCO LAN/WAN. In the example below, FCS0 has a connection to FCS1 via VSAN10, and FCS2 has a connection to FCS3 via VSAN11.
429
10.13.1.1
Configuration settings
i
Important for the CISO-FCIP configuration: the IOs within ETERNUS CS HE may
not be interrupted in order to prevent the ETERNUS CS HE mirror from being split.
If only one connection between the sides exists, the ETERNUS CS HE 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.
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 to E (E_port)
Example
CISCO configuration via CLI for ports 1 and 2, and on Cisco Switch1:
config t
interface fc 1/1 -2
portmode E
switchport trunk mode off
switchport speed 4000
switchport rate-mode dedicated
no shutdown
exit
config t
vsan database
vsan 10 interop 3
vsan 11 interop 3
no shutdown
exit
430
Brocade settings
In the default configuration, ports 2 and 3 on the FC switches are provided as an ISL connection.
When additional bandwidth is required for the ISL connections, additional ports can be
used. The settings used in the example must be specified here.
The following settings must be made and if necessary checked in the internal FC switches
FCS0,1,2 and 3:
–
Interoperability Modes remains in Native Mode
–
PID format must be 1. This can be checked with:
configshow: fabric.ops.mode.pidFormat
–
Longdistance is enabled via the switch configuration:
FCS0:admin> switchdisable
FCS0:admin> configure
Fabric parameters (yes, y, no, n): [no] y
…
…
Long Distance Fabric: (0..1) [0] 1
●
For Brocade FabOS < 6.3
Set ISL Mode for ports 2 and 3:
portcfgislmode 2 1
portcfgislmode 3 1
Define Speed as max. 4G:
portcfgspeed 2,4
portcfgspeed 3,4
Disable Trunking:
portcfgtrunkport 2,0
portcfgtrunkport 3,0
Enable Long Distance (e.g. 20 km):
●
portcfgloongdistance 2,LS,0,20
portcfglongdistance 3,LS,0,20
For Brocade FabOS 6.3 and higher
Disable Quality of Service:
portcfgqos
portcfgqos
Disable Credit Recovery:
portcfgcreditrecovery - - disable 2
portcfgcreditrecovery - - disable 3
- - disable 2
- - disable 3
431
Checking the settings with portcfgshow
●
FabricOS 5.3.x
FCS2:admin> portcfgshow:
Ports of Slot 0
0 1 2 3
4 5 6 7
8 9 10 11
12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
Trunk Port
ON ON .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Long Distance
.. .. LS LS
.. .. .. ..
.. .. .. ..
.. .. .. ..
VC Link Init
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked L_Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked G_Port
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
Disabled E_Port
.. .. .. ..
ON ON ON ON
ON ON ON ON
ON ON ON ON
ISL R_RDY Mode
.. .. ON ON
.. .. .. ..
.. .. .. ..
.. .. .. ..
RSCN Suppressed
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Persistent DisableON ON .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
NPIV capability
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
Mirror Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Ports of Slot 0
16 17 18 19
20 21 22 23
24 25 26 27
28 29 30 31
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
Trunk Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Long Distance
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
VC Link Init
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked L_Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked G_Port
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
Disabled E_Port
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
ISL R_RDY Mode
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
RSCN Suppressed
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Persistent Disable.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
NPIV capability
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
Mirror Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
432
●
FabricOS 6.3.x
/fabos/cliexec/portcfgshow:
Ports of Slot 0
0 1 2 3
4 5 6 7
8 9 10 11
12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
4G 4G 4G 4G
Fill Word
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
AL_PA Offset 13
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Trunk Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Long Distance
.. .. LS LS
.. .. .. ..
.. .. .. ..
.. .. .. ..
VC Link Init
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked L_Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Locked G_Port
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
Disabled E_Port
.. .. .. ..
ON ON ON ON
ON ON ON ON
ON ON ON ON
ISL R_RDY Mode
.. .. ON ON
.. .. .. ..
.. .. .. ..
.. .. .. ..
RSCN Suppressed
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Persistent DisableON ON .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
NPIV capability
ON ON ON ON
ON ON ON ON
ON ON ON ON
ON ON ON ON
QOS E_Port
AE AE .. ..
AE AE AE AE
AE AE AE AE
AE AE AE AE
EX Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Mirror Port
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Rate Limit
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Credit Recovery
ON ON .. ..
ON ON ON ON
ON ON ON ON
ON ON ON ON
Fport Buffers
.. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Port Auto Disable .. .. .. ..
.. .. .. ..
.. .. .. ..
.. .. .. ..
Checking the settings with switchshow
/fabos/bin/switchshow:
switchName:
switchType:
switchState:
switchMode:
switchRole:
switchDomain:
switchId:
switchWwn:
zoning:
switchBeacon:
FC Router:
Allow XISL Use:
LS Attributes:
FCS0
66.1
Online
Native
Subordinate
1
fffc01
10:00:00:05:1e:c5:e8:3c
OFF
OFF
OFF
OFF
[FID: 128, Base Switch: No, Default Switch: Yes,
Address Mode 0]
433
Index Port Address Media Speed State
Proto
==============================================
0
0
010000
-4G
No_Module
FC Disabled (Persistent)
1
1
010100
-4G
No_Module
FC Disabled (Persistent)
2
2
010200
id
4G
Online
FC LS E-Port 20:e3:00:0d:ec:b6:dd:c1 "MDSM1C01" (upstream)
3
3
010300
id
4G
Online
FC LS E-Port 20:e3:00:0d:ec:b6:dd:c1 "MDSM1C01"
4
4
010400
id
4G
Online
FC F-Port 10:00:00:00:c9:95:9c:1a
5
5
010500
id
4G
Online
FC F-Port 10:00:00:00:c9:95:98:06
6
6
010600
id
4G
Online
FC F-Port 10:00:00:00:c9:95:8f:e4
7
7
010700
id
4G
Online
FC F-Port 10:00:00:00:c9:95:9b:28
8
8
010800
id
4G
Online
FC F-Port 10:00:00:00:c9:95:9c:e2
9
9
010900
id
4G
Online
FC F-Port 10:00:00:00:c9:95:90:40
10 10
010a00
-4G
No_Module
FC
11 11
010b00
-4G
No_Module
FC
12 12
010c00
-4G
No_Module
FC
13 13
010d00
id
4G
Online
FC F-Port 20:40:00:0b:5d:6a:0f:2c
14 14
010e00
id
4G
Online
FC F-Port 20:40:00:0b:5d:6a:0f:2b
15 15
010f00
id
4G
Online
FC F-Port 20:40:00:0b:5d:6a:0f:29
16 16
011000
-4G
No_Module
FC
17 17
011100
-4G
No_Module
FC
18 18
011200
-4G
No_Module
FC
19 19
011300
-4G
No_Module
FC
20 20
011400
-4G
No_Module
FC
21 21
011500
-4G
No_Module
FC
22 22
011600
-4G
No_Module
FC
23 23
011700
-4G
No_Module
FC
24 24
011800
-4G
No_Module
FC (No POD License) Disabled
25 25
011900
-4G
No_Module
26 26
011a00
-4G
No_Module
27 27
011b00
-4G
No_Module
28 28
011c00
-4G
No_Module
29 29
011d00
-4G
No_Module
30 30
011e00
-4G
No_Module
31 31
011f00
-4G
No_Module
32 32
012000
-4G
No_Module
33 33
012100
-4G
No_Module
34 34
012200
-4G
No_Module
35 35
012300
-4G
No_Module
36 36
012400
-4G
No_Module
37 37
012500
-4G
No_Module
38 38
012600
-4G
No_Module
39 39
012700
-4G
No_Module
434
Checking the settings with fabricshow
Ê
Use fabricshow to check whether FCS0 and FCS1 and also the Cisco Switches are
visible.
fabricshow:
CURRENT CONTEXT -- 0 , 128
/fabos/cliexec/fabricshow:
Switch ID
Worldwide Name
Enet IP Addr
FC IP Addr
Name
------------------------------------------------------------------------1: fffc01 10:00:00:05:1e:c5:e8:3c 192.168.101.220 0.0.0.0
"FCS0"
3: fffc03 10:00:00:05:1e:c5:e4:12 192.168.101.221 0.0.0.0
"FCS1"
7: fffc07 20:e3:00:0d:ec:af:b6:41 126.40.108.41
0.0.0.0
>"MDSM1B01"
9: fffc09 20:e3:00:0d:ec:3b:fc:c1 126.196.112.10 0.0.0.0
"MDSC1A01"
113: fffc71 20:e3:00:0d:ec:3c:12:01 126.196.112.36 0.0.0.0
"MDSC2A01"
177: fffcb1 20:e3:00:0d:ec:b6:dd:c1 126.40.108.43
0.0.0.0
"MDSM1C01"
Ê
Then use the same command to check the connection between FCS2 and FCS3.
If all the settings are correct, you can begin Initial Configuration of ETERNUS CS HE.
10.13.1.2
Configuring the Cisco Switch via the graphical user interface (Fabric Manager)
Setting the license
Setting Interop Mode on Cisco
435
FCIP wizard for setting up the FCIP connection between the two switches
Tools ➟ Others ➟ FCIP Tunnel
436
437
438
439
440
Device Manager
The ISL connection must be defined as E (E_Port) in the Device Manager:
441
Tunnels Advanced for setting Write Accelerator
Gigabit Ethernet
Overall view of fabric with FCIP and the two ETERNUS CS HE sides
442
Ping for determining the runtime to terminals
443
10.13.2 Long distance over an FCIP connection between IDP and real tape
10.13.2.1
Configuration overview
10.13.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.
444
●
Sets Write and Tape Acceleration for FCIP
●
Sets Port in the device manager to Fx_Port
10.13.2.3
Configuring the Cisco Switches via the graphical user interface (Fabric Manager)
Defining zones for the visibility of the real tape drives
445
Defining Write and Tape Acceleration
446
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 ETERNUS CS HE so that a corresponding target for the drive can be generated on the IDP.
Device Manager: FC ➟ Domain Manager ➟ Persisiten FcIDs
10.13.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
447
VACS security by means of ownership
10.14 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.
10.14.1 VACS configuration parameters in GXCC
The screenshot below shows the VACS configuration parameters in the GXCC menu Configuration ➟ Virtual Library Services:
448
10.14.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.
449
10.14.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
450
POOL
0
LOCK OWNER
0
unowned
10.14.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:
10.14.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
451
10.14.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.
452
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 an ETERNUS CS HE.
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
453
10.14.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 ETERNUS CS HE.
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 an ETERNUS CS HE.
454
11 Installation of the GUI software GXCC/XTCC
11.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.
11.2 Installation descriptions
This CD-ROM can be used to install the GUI software required for the monitoring of an
ETERNUS CS HE system. The GUI software was tested on the operating systems MSWindows 95/98/NT/2000/XP/VISTA, LINUX and SOLARIS. 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.
455
Installation descriptions
Installation of the GUI software GXCC/XTCC
11.2.1 Installation on MS-Windows Platform
The operating systems supported are MS-Windows 95/98/NT/2000/XP and VISTA. 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.
On a multi-user system (such as MS-Windows NT/2000/XP/VISTA), 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 administrative functions, however, do require an administrator account.
i
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 470.
11.2.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 gui87en.exe using the left
mouse key.
i
On MS-Windows VISTA this step must be explicitely allowed if the User Account
Control is active.
The installation of the software starts.
A complete installation encompasses the following components:
456
GUI software GXCC and XTCC
●
Graphical User Interface:
●
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 Integr. Tools:
Extensions in the CA Unicenter software for
ETERNUS CS HE
Using a selection window, it is possible to exclude specific components from the installation
process.
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.
i
By selection of the component GXCC Demo (FALKE) the snapshot files required for
the offline mode (refer to section “Offline Mode” on page 466) 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. In the concluding window Setup has finished
installing... the user can decide to Import V6 User Data (if available) and to Uninstall V6 Control
Center (if present). The installation will be terminated by clicking the Finish button.
11.2.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 ETERNUS CS HE 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 an ETERNUS CS HE system
(offline-mode). Depending on actual availability it consists of the complete ETERNUS CS
HE service and/or user manual or it consists of selected chapters, 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 456):
!
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 doc87en.exe using the left
mouse key.
i
Control is active.
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.
i
On MS-Windows VISTA the final message 'This program might not have installed correctly' can be ignored.
457
11.2.1.3
Starting the GUI Software
Via Start ➟ Program Files ➟ Fujitsu ➟ ETERNUS CS Control Center V7 a menu structure with
the following functions will be shown:
GXCC
●
–
–
–
XTCC
●
–
–
–
XTCC Observe Mode
XTCC Service Mode
XTCC User Mode
Setup
●
–
–
–
–
–
–
Add ETERNUS CS to CA Unicenter
Delete ETERNUS CS from CA Unicenter
SNMP Integration Liesmich
SNMP Integration Readme
Try to repair inoperable GXCC or XTCC 1
Uninstall ETERNUS CS Control Center
Tools
●
–
–
–
i
1
GXCC Observe Mode
GXCC Service Mode
GXCC User Mode
Global Status (large)
Global Status (small)
Recorder
In case of an active firewall the blockades of the components tclsh and Tclkit must
be suspended ('Unblock').
Because of special protective mechanisms on MS-Windows VISTA this function must be invoked in the context 'Run as Administrator'.
458
11.2.1.4
Creating the CA-Unicenter Extensions for ETERNUS CS HE
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/VISTA), 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 ➟ Program Files ➟ Fujitsu ➟
ETERNUS CS Control Center V7 ➟ Setup ➟ SNMP Integration Readme.
For the installation of the extensions the tool Start ➟ Program Files ➟ Fujitsu ➟ ETERNUS CS
Control Center V7 ➟ Setup ➟ Add ETERNUS CS 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 ➟ Program Files ➟ Fujitsu ➟ ETERNUS CS Control Center V7 ➟ Delete
ETERNUS CS from CA-Unicenter the extensions can be deleted.
11.2.1.5
Deinstallation of the Software
After invocation of Start ➟ Program Files ➟ Fujitsu ➟ ETERNUS CS Control Center V7 ➟ Setup
➟ Uninstall ETERNUS CS Control Center a window with the title 'Fujitsu ETERNUS CS
Control Center V7 Uninstall' will be displayed asking 'Are you sure that you want to
completely remove Fujitsu ETERNUS CS Control Center V7 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 470.
11.2.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>.
459
11.2.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.
The package names for the GUI software of ETERNUS CS HE V4 and higher have
changed. Before installing this GUI-Software the GUI packages of any older version
must be deinstalled.
i
11.2.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:
fsc-BrkXtcc-<version>-<date><time>.i686.rpm
fsc-GlbXtcc-<version>-<date><time>.i686.rpm
fsc-GlbDoc-<version>-<date><time>.i686.rpm
5. Install these three packets in the following sequence:
a) rpm -i fsc-BrkXtcc*.rpm --nodeps
b) rpm -i fsc-GlbXtcc*.rpm --nodeps
c) rpm -i fsc-GlbDoc*.rpm --nodeps
460
11.2.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 gxcc, and for XTCC the program xtcc
should be invoked. Start in service mode, observe mode, or user mode is accomplished via
options -service, -observe, or -user. Without any option specified the program is
started in user mode.
Syntax of command line input:
gxcc [-service | -observe] [&]
xtcc [-service | -observe] [&]
i
11.2.2.3
If the Linux server is accessed via a VNC client and if IPv6 is activated on the Linux
server, the environment variable DISPLAY contains IPv6 format of the server IP
address (e.g. ::1:1.0, ::ffff:127.0.0.1:1.0). In this case the variable DISPLAY
must be provided with IPv4 format of the IP address (e.g. 127.0.0.1:1.0) or with
the hostname (e.g. localhost:1.0) to ensure starting the GUI software.
Deinstalling the GUI Software
The deinstallation has to be performed under the user account root in the following
sequence:
1. rpm -e fsc-GlbDoc
2. rpm -e fsc-GlbXtcc
3. rpm -e fsc-BrkXtcc
11.2.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.
461
11.2.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.
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 Locale 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
462
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.
i
11.2.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.
GXCC and XTCC are started via command line input. The user can specify the operation
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.
Syntax of command line input:
gxcc [-service | -observe] [&]
xtcc [-service | -observe] [&]
11.2.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
463
Online Documentation of the GUI Software
11.3 Online Documentation of the GUI Software
11.3.1 General
The GUI software includes the capability to automatically access, provide and update the
online documentation for the ETERNUS CS HE 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 an ETERNUS CS HE system (offline-mode). Depending on actual availability it consists
of the complete ETERNUS CS HE service and/or user manual or it consists of selected
chapters, concerning the graphical user interface.
11.3.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 CS <version> Service manual (complete) will be displayed,
if the complete service manual exists, or an entry CS <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 CS <version>User manual (complete) will
be displayed, if the complete user manual exists, or an entry CS <version>User manual (GUIPart) 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
!
464
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.
Font Files
11.4 Font Files
11.4.1 General
When the GUI software uses a fixed font (monospaced font) to display window elements,
the preferred font (as from ETERNUS CS HE V4.0) is the TrueType font Bitstream Sans Vera
Mono, if this font is installed in the X Window system. Otherwise the font Courier, which
exists on all platforms, is used, as it has been in the past. Among other things, this new font
has the characteristic that the number 0 differs clearly from the character O.
During the installation of ETERNUS CS HE the font will be installed by default, and
therefore will automatically be used when the GUI software is started on the ETERNUS CS
HE console. If the GUI software is installed using the GUI CD on computers outside of
ETERNUS CS HE and the GUI should use the new font, the font must be installed on the
computer where the GUI software runs.
On the GUI computer the font may be installed at a later time. For this purpose the GUI CD
provides the related font files in the directory fonts. This directory is located in the root
directory of the CD-ROM.
11.4.2 Installation of the font files
The installation of the font files depends on the platform and must be executed manually in
the majority of cases.
11.4.2.1
Installation on MS-Windows Platform
The installation of the font files occurs automatically during the installation of the GUI
software.
11.4.2.2
Installation on a LINUX Platform
The installation of the font files has to be performed manually by the user. The procedure
depends on the Linux distribution used. The X Server has to be restarted in all cases at the
end of the font installation, so that the new font files may be used.
11.4.2.3
Installation on a SOLARIS Platform
The installation of the font files has to be performed manually by the user. The procedure
depends on the Solaris system used. The X Server has to be restarted in all cases at the
end of the font installation, so that the new font files may be used.
465
Offline Mode
11.5 Offline Mode
Usually the display generated by the GUI software is based on data, which are periodically
received from an active ETERNUS CS HE 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 ETERNUS CS HE 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 ETERNUS CS HE
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.
11.5.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.
466
11.5.1.1
Offline Mode
MS-Windows Platform
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.
i
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 gui87en.exe.
i
Control is active.
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.
11.5.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
467
Offline Mode
11.5.1.3
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.
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.
468
Offline Mode
11.5.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 an ETERNUS CS HE 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.
11.5.2.1
Static Display
Starting GXCC in offline mode will always display a static picture of an ETERNUS CS HE
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.
11.5.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 Status Monitor
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.
469
Installation of the GUI software
11.6 Unattended Installation / Deinstallation under MS-Windows
ATTENTION!
To perform this function on MS-Windows VISTA the User Account Control (UAC) must
be inactive. Otherwise the process will be blocked by an unacknowledged UAC
dialog.
!
11.6.1 Setup Command Line Parameters
The Setup programs gui87en.exe / doc87en.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. 1
/COMPONENTS=comma_separated_list_of component_names *)
Overrides the default components settings. Using this command line parameter causes
Setup to automatically select Custom type.
i
This parameter is only valid for gui87en.exe. The component gui must always
be included in the comma separated list.
Component names used for the ETERNUS CS HE GUI:
gui
ico
dem
uni
1
Graphical User Interface
GXCC Observe Mode Shortcut
GXCC Demo (FALKE)
CA Unicenter Integration Tools
optional
470
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:\Program Files\Fujitsu 2
Group=ETERNUS CS Control Center V7
NoIcons=0
Components=gui,ico,dem,uni
The Dir entry can be used to locate
C:\Program Files\Fujitsu\ETERNUS CS Control Center V7\unins000.exe2
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.
11.6.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.
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
471
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.
11.6.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.
11.6.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).
472
Unattended Installation / Deinstallation under MS-
11.6.5 Setup Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Uninstall\
Fujitsu ETERNUS CS Control Center V7_is1
...
UninstallString REG_SZ C:\Programme\Fujitsu\ETERNUS CS Control Center V7\
unins000.exe 1
11.6.6 GUI Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Uninstall\
Fujitsu ETERNUS CS Control Center V7
ADMIN_USER REG_SZ ?
GXTCC_HOME REG_SZ C:\Programme\Fujitsu\ETERNUS CS Control Center V7\gxtcc 1
XTCC_HOME REG_SZ C:\Programme\Fujitsu\ETERNUS CS Control Center V7\xtcc 1
TCLSH REG_SZ C:\Programme\Fujitsu\ETERNUS CS Control Center V7\tclsh.exe 1
WISH REG_SZ C:\Programme\Fujitsu\ETERNUS CS Control Center V7\wish.exe 1
1
pathname of the default directory
473
474
12 Web GUI for ETERNUS CS HE administration
As of ETERNUS CS HE V5.0A a web based graphical user interface is supplied for administration of ETERNUS CS HE.
This GUI offers all functions necessary for media management (i.e. LV, LVG, PV, PVG).
The Web GUI does not need any further software to be installed and can be used on common operating systems with Firefox (version 2 and 3) or Internet Explorer(IE7 and IE8), also
on the ETERNUS CS HE console.
For detailed informationen about operating and monitoring via the Web GUI please refer to
the User Guide or the Online help (after having started the Web GUI and successful login
to a ETERNUS CS HE system).
12.1 Starting the Web GUI
To permit communication between the client (browser) and the CS-WEB application in the
ETERNUS CS HE cluster (Web server), the Web server supports both the customary HTTP
connection, in which all data is transferred between the client and the server in unencrypted
form, and an encrypted HTTPS (SSL) connection.
Proceed as follows to start the Web GUI in the mode you require:
1. Call the Web browser.
2. Enter the address in the Web browser:
–
http://<host>/eternus-cs for unencrypted transmission
–
https://<host>/eternus-cs for encrypted transmission
Enter the host name or the IP address of the VLP in place of <host>.
3. Click on [Enter].
Once you have started the Web GUI successfully, the login window is displayed (see section “Logging in” on page 476).
475
Logging in
Web GUI for ETERNUS CS HE administration
12.2 Logging in
You can log into an ETERNUS CS HE system via a dialog window. The login window will
appear automatically when you
–
enter the address of the server manually in the address bar of your browser,
–
call the address of the server from the favorites,
–
call the address of the server from another page.
The Fujitsu ’infinite’ icon (
browser tab.
i
) is displayed both to the left of the URL and in the
Proceed as follows to log into an ETERNUS CS HE system:
1. Enter your user name in the User Name field.
i
The user "xtccuser" is already preconfigured on the system and can be used
immediately.
2. Enter your password in the Password field.
3. Click on Login.
The ETERNUS CS HE Control Center will attempt to obtain authentication via the selected
server.
476
Protection by certificates and firewalls
If the login is successful, the user name is displayed at the top right of the login window. The
overview page for the server on which you have logged in will also open.
If the login is not successful, the message Login failed will be displayed in the login window
without any further information.
If a connection error has occurred, the error message Connection failed and a technical
message will be displayed in the login window.
12.3 Protection by certificates and firewalls
When using the https protocol, the certificate offered by ETERNUS CS HE may need to be
accepted in the Web browser (after consultation with the system administrator).
For detailed information refer to the Web GUI User Guide, section „Certificate management“.
If the ETERNUS CS HE system is protected by a firewall, the ETERNUS CS HE administrator must give access to the ports for the Web GUI (http and/or https).
477
Protection by certificates and firewalls
478
13 Application recommendation for ETERNUS CS
HE Update Installation
This chapter provides the service engineer and the administrator of the front-end application with the necessary decision information what update procedure shall be chosen and
also acts as an example and guideline for the rolling update of an ETERNUS CS HE cluster.
13.1 General information
The rolling software update is a flexible basic procedure via which the software update for
ETERNUS CS HE systems can be executed interrupt-free for the front-end application.
One or a number of CS nodes are installed while the remaining nodes maintain operations.
The non-interruption for an active front-end application presumes that this application is
available on at least 2 ICPs or 2 IUPs, that it is SWAP master resistant in its LAN robot
connection, that it can also execute an interrupt-free switchover between these connections
and that administrative interfaces permit the implementation of such switchovers.
If this is not fulfilled, running jobs are aborted. As ETERNUS CS HE operations are not
interrupted during the rolling update, non-plannable recovery runs are possible at any time.
Plannable backup jobs should be terminated before starting the rolling update.
As an alternative to the interrupt-free rolling software update, ETERNUS CS HE always
offers the option of a so-called cluster update where the CS nodes are basically updated
simultaneously. This procedure requires much less time for the update but also a (short)
downtime of the entire system. Values for the time required for the software update via the
various procedures are compared in the section Update assessment criteria.
In specific situations, the decision for a particular update procedure should be based on
weighing up the customer's priorities and the features of the backup applications used.
479
Update procedure
Application recommendation for ETERNUS CS HE Update Installation
13.2 Update procedure
The decision about the update procedure used is supported by the software update
program (updmc). It determines the possible update options based on the software version
already installed on the system and the new updates to be installed. The service engineer
makes the final decision about the recommended procedure to be used based on customer
requirements.
13.2.1 Online update
The online update installation is a fully automatic, interrupt-free update procedure where an
ETERNUS CS HE service is not interrupted. ETERNUS CS HE system redundancy and
failsafe is not restricted at any time. This method assumes that the components of the
operating system kernel, the CAFS and the central ETERNUS CS HE components are not
affected by the update installation.
13.2.2 Rolling update
The rolling software update is a flexible basic procedure via which the software update for
ETERNUS CS HE systems can be executed interrupt-free for the front-end application.
One or a number of CS nodes are installed while the remaining nodes maintain operations.
The non-interruption for an active front-end application presumes that this application is
available on at least 2 ICPs or 2 IUPs, that it is SWAP master resistant in its LAN robot
connection, that it can also execute an interrupt-free switchover between these connections
and that administrative interfaces permit the implementation of such switchovers.
13.2.3 Split cluster update
In typical 2-site ETERNUS CS HE configurations the CS system is symmetrically
distributed over two locations and the applications connected redundantly. In this case, the
so-called split cluster update is also an interrupt-free rolling update configuration
optimized for front-end applications via which all ISPs of a location are simultaneously
installed. The other location runs the ETERNUS CS HE and backup activities of the frontend applications for this period.
480
Update situations
13.2.4 Cluster update
As an alternative to the interrupt-free rolling software update, ETERNUS CS HE always
offers the option of a so-called cluster update where the CS nodes are basically updated
simultaneously. This procedure requires much less time for the update but also a (short)
downtime of the entire system, i.e. all applications must be ended before starting the
cluster update. Values for the time required for the software update via the various procedures are compared in the section Update assessment criteria .
13.3 Update situations
Depending on the existing update conditions, the service engineer must decide for one of
the software update procedures recommended by the update tool updmc:
●
●
●
Online update
Condition:
The update medium (hotfix/patch CD) fulfills all the criteria for the online
update.
Execution:
fully automatic via the update program updmc, a decision by the service
engineer is not required.
Rolling update
Conditions:
The rolling update must be performed interrupt-free on oneor a number
of CS nodes (see section “Rolling update” on page 480).
The update program updmc has recommended rolling update as a
possible update procedure.
Execution:
The service engineer performs the rolling update according to the
Update handling instructions section “Rolling Update” on page 491.
The service engineer can decide to use the cluster update (with
downtime).
Split cluster update
Conditions:
The update program updmc recommends the rolling update as a
possible update procedure and the CS system is symmetrically
distributed at two locations and the applications are connected symmetrically and redundantly.
Execution:
The service engineer executes the software update according to the
Update handling instructions - “Split cluster update” on page 492.
Alternatively, the service engineer can decide to use the cluster update
(with downtime).
481
Update assessment criteria
●
Cluster update
Conditions:
A maintenance slot with CS downtime is available to the service
engineer
Execution:
The service engineer continues the software update program updmc
with c (continue). The update is executed automatically.
The post update actions are executed by the service engineer according
to the instructions in the update program updmc, .
13.4 Update assessment criteria
13.4.1 Planning and administration expenditure
In order to estimate the planning and administration expenditure involved in implementing
the rolling update, the type and configuration of the front-end applications to be operated
are of decisive importance. In order to perform the SW update for the front-end applications
interrupt-free, it must be ensured when configuring the front-end application that the tape
devices are distributed at various ICPs.
It should also be noted that the front-end applications can be be re-connected differently
regarding the LAN robot connection. (see table “Front-end applications in an ETERNUS CS
HE environment” on page 483, Column: SWAP Master Resistant).
An overview of the currently most common front-end applications is in table “Front-end
applications in an ETERNUS CS HE environment” on page 483. Should an application be
used which is not listed here, Fujitsu Technology Solutions Product Planning must be
contacted beforehand.
The first two columns show the front-end application and the operating system used. The
column ’Pending’ Device Deactivation shows whether the deactivation of the drives belonging
to the ICP/IUP can be requested in backup/restore mode.
The column SWAP Master Resistant shows whether the reconnection of the LAN library
(VDAS, VACS, VAMU) after swap master on VLP or IUP, can take place in the application
without any problems, e.g. in the mount requests hanging in the application.
The column Handling instructions describes the activities for the service engineer and the
administrator for the respective front-end application.
482
Front-end
application
Operating
System
’Pending’ Device
deactivation
Y / N / open
SWAP master
Resistant:
Y / N / open
Handling instructions for service
engineer (SE) or administrator (AD)
FSC
NetWorker
Solaris
Linux SuSe
Y
Only free drives can
be disabled.
Y VDAS
N VACS
AD: Sets device resources to
enabled=Service/No
SE: Executes update and post-update
actions on ICP/IUP
enabled=Yes
EMC
NetWorker
AIX
Y
Y VDAS
HP-UX
Only free drives N VACS
can be detached.
enabled=Service/No
actions on ICP/IUP
enabled=Yes
Solaris
Win2k3 (2)
Linux
(SuSe)
Tru64 (12)
Symantec /
Veritas
NetBackup
AIX
HP-UX
Solaris
Win2k3 (2)
Linux
(SuSe)
IBM TSM
AIX
HP-UX
Solaris
Win2k3 (2)
Linux
(SuSE)
Linux
(RedHat)
Y
Only free drives
can be detached.
If a reboot of the
ICP/IUP occurs,
problems will
occur under
Solaris!
Y
Free drives can
be detached/
attached.
Assigned drives
can also be
detached, but is
not recommended by the
TSM manual
Y VDAS
Y VACS
AD: Waits until all jobs are ended and
then enables the devices
AD: Sets free devices to status down
actions on ICP/IUP
AD: Sets devices to status up
Y VACS with
AD: Sets devices to ONLINE=NOSE:
spor. hang-up 1) Executes update and post-install
actions on the ICP/IUP
AD: Sets devices to ONLINE=YES
Table 1: Front-end applications in an ETERNUS CS HE environment
483
Front-end
application
Operating
System
deactivation
Y / N / open
SWAP master
Resistant:
Y / N / open
HP
DataProtector
AIX
Y
Y VDAS
N VACS 1)
N VACS
AD: disabled devices of the application for this ICP/IUP
Y VDAS
N VACS 1)
not released
HP-UX
Solaris
Linux
(RedHat)
SE: executes update and post-update
action
AD: enabled devices of the application for
this ICP/IUP
Win2k3 (2) |
A64
CA
ARCserve
r11.5 SP3
Win2k3 (2)
Y
Linux
(SuSE)
CA
ARCserve r12
Win2k3 (2)
not released
EMC
DiskXtender
for Unix/Linux
Solaris
open if necessary open if
not released
POC as DUXL is
necessary POC
not in customer use as DUXL is not in
customer use
EMC
DiskXtender
for Windows
Win2k3 (2)
N
NetApp Filer
ONTAP 7.0
Linux
(SuSe)
N
update only possible after the application
has been ended!i.e. No rolling update
possible!
not released
ONTAP7.2
CommVault
Win2k3
Y with spor.
hangers
not released
NetVault
Win2k3
Y mit spor.
Hängern
not released
Celerra
DART
OS 5.5
not released
484
Front-end
application
Operating
System
deactivation
Y / N / open
SWAP master
Resistant:
Y / N / open
BS2000
SX-Server
Y
Add-on for FC
connection:
After detach-device
in the BS2000 Stop
tape emulation in
X2000; Start tape
emulation in X2000
before attach-device
in BS2000
Y VACS/CSC
Y VAMU/RobarSV with restart
option
AD: detached devices in BS2000
AD: Waits for end of detach pending
AD: stops tape emulation in X2000 (only
with FC)
ST: Executes update and post-install
action on the ICP/IUP
AD: starts tape emulation in X2000 (with
FC only)
AD: attached devices in the BS2000
BS2000
S-Server
Y
Y VACS/CSC
Y VAMU/RobarSV with restart
option
AD: detached devices in the BS2000
AD:Waits for end of detach pending
ST: Executes update and post-install
actions on the ICP/IUP
AD:attached devices in the BS2000
1
If error occur in the appliction due to swap master VLP/SVLP switchover, a reboot of the VLP is then necessary!
13.4.2 Complexity
As can be seen in the table above, the complexity of the operation from an application pointof-view is defined by the number and type of applications and the size of the backup configurations on the front-end.
The rolling update must be viewed as a basic mechanism which is the prerequisite for
interrupt-free application operation subject to the conditions described above. The
additional support required by the data center administration regarding the coordination of
the individual instances affected by the update must be clarified beforehand. Decisive is
●
whether the ICP/IUP to be installed can be simply switched off as the affected applications must "survive" this downtime via redundancy and the corresponding symmetrical
configuration of the devices without any interruption to the backup operation.
●
whether the devices for the applications involved are easy to disable/detach and subsequently enable/attach so as to to automatically restart backup operations,
●
manual interventions in the application by the system administrator are required, in
agreement with the service engineer, to place the device affected by the ICP/IUP
update to the status that permits a detach/attach,
●
whether a mixture of all previously named options exists and the coordinated decommissioning is therefore linked to a high amount of work for the administrator or
485
whether, in the worst-case, deactiving individual ICP/IUPs is not even possible due to
the existing configuration which thus leads to unforeseeable system statuses in the
application.
●
The conditions listed show that detailed planning is essential before implementing the
rolling update in order to guarantee no interruptions during the update.
13.4.3 Total duration and downtime
This section compares the time required for the update versions rolling update, split cluster
update and cluster update (with downtime).
The service engineer must decide whether he wants to or must execute an interrupt-free
update for the application via rolling update / split cluster update for a longer time slot or
whether he wants to execute the automatic update with a restricted downtime in a slot that
is as short as possible.
13.4.3.1
Time required for the rolling update
A backup of the current system partition of the ISP must be made before the update.
The time required for the rolling update of a CS cluster is as follows.
●
The first update step is that the installation program itself is updated on all ISPs and the
installation servers and SW repository are loaded with the new software from the DVD.
●
The second update step is to consecutively update the software on all ISPs.
!
CAUTION!
The time required for the transferring or switching over the applications as described
above is not taken into account in the following table.
ETERNUS
CS
versions
Site
ISP
backup1 update
without
reboot
update
with
reboot
Comment:
CS500
CS1000
A
iup0
5-15
14
20
including SI2upd and
repository update
B
iup1
5-15
4
10
5-15
18
30
Net without application switchover
times!
Table 2: Time required for rolling update installation
486
ETERNUS
CS
versions
Site
CS1500 A,B,C
CS2000
Single site
CS3000
A,B,C
Single site
CS4000
A,B,C
Single site
ISP
backup1 update
without
reboot
update
with
reboot
Comment:
vlp1
5-15
14
20
repository update
vlp0
5-15
4
10
tbp0
5
4
10
Icp0..1
5-10
8
20
Idp0..1
5-10
8
20
5-15
38
80
times!
vlp1
5-15
14
20
repository update
vlp0
5-15
4
10
tbp0
5
4
10
Icp0..2
5-10
12
30
Idp0..2
5-10
12
30
5-15
46
100
times!
vlp1
5-15
14
20
repository update
vlp0
5-15
4
10
tbp0
5
4
10
Icp0..3
5-10
16
40
Idp0..3
5-10
16
40
5-15
54
120
times!
487
ETERNUS
CS
versions
Site
CS5000
A,B,C
Single site
ISP
backup1 update
without
reboot
update
with
reboot
Comment:
vlp1
5-15
14
20
repository update
vlp0
5-15
4
10
tbp0
5
4
10
Icp0..5
5-10
24
60
Idp0..5
5-10
24
60
5-15
70
160
times!
1
Backups are started across all ISPs in parallel; the runtime is defined by the system size and the system load.
13.4.4 Time required for split cluster update
The time required for the split cluster update installation of a CS cluster is as follows.
–
A backup of the current system partition of all ISPs of the site affected by the update
must be made before the update.
The installation program itself is then updated online on all ISPs and the installation
servers and the SW repository are loaded with the new software from the DVD.
All ISPs at site A are subsequently updated.
When site A is fully operational again and the applications have been switched, site B is
updated.
Once site B is fully operational again, site C is updated.
–
–
–
–
!
CAUTION!
The time required for the startup/shutdown and switchover of the applications
(as described above) is not taken into account in the following table.
ETERNUS
CS HE
versions
CS500
CS1000
Site
A,B
ISP
backup1 update
without
reboot
iup0
5-15
14
iup1
5-15
4
5-15
18
update
with
reboot
Comment:
20 including SI2upd and repository
update
10
30 Net without application times
Table 3: Time required for split cluster update
488
ETERNUS
CS HE
versions
CS2000 CS5000
Multisite
Site
A
B
C
ISP
backup1 update
without
reboot
update
with
reboot
Comment:
vlp0
5-15
14
icp..,idp.
5-10
6
5-15
20
vlp1
5-15
6
12 vlp1
icp..,idp.
5-10
6
12 icp1/3/5, idp1/3/5 ..run parallel
to vlp1
5-15
6
12 Total: site B
5
4
10
5
4
10 Total: site C
5-15
30
tbp0
20 including SI2upd and repository
update
12 icp0/2/4, idp0/2/4
32 Total: site A
54 Net without application times
Table 3: Time required for split cluster update
1
13.4.4.1
Backups are started across all ISPs in parallel; the runtime is defined by the system size and the system load..
Time required for cluster update installation (with downtime)
●
Before updating the ISPs, a backup of the current system partition must be made.
●
The installation program itself is then updated and the installation servers and the SW
repository are loaded with the new software from the DVD.
●
The software is then updated on all ISPs.
●
Finally, depending on the post-install-action displayed, the service engineer must restart
the CS system or reboot the ISPs.
The times listed below (in minutes) only act as a guideline for the update installation time
for the TX300-S3 hardware. The time required for the update is determined mainly by the
type of update, the number of SW packets, the number of ISPs and by the broker activities
during stop/start/reboot of the ISP/cluster. The typical times for updating a TX300-S3 cluster
are shown in the following table.
489
CAUTION!
The time required for startup/shutdown of the applications is not taken into account
in the following table..
!
CS
versions
CS50
CS500
CS1000
CS1500 CS4000
Single site
CS2000 CS5000
Multisite
Site
ISPs
backup1 update
without
reboot
updatew Comment: ISPs involved
ith
reboot
A
VTC
5-15
12
18 CS50 in total
A,B
IUP0
5-15
14
20 including SI2upd and repository update
IUP1
5-15
4
5-15
18
30 Total of CS500/CS1000
VLP0
5-15
14
20 including SI2upd and repository update
VLP1,
TBP..
5-15
6
5-15
20
40 Total of CS1500 - CS4000
VLP0
5-15
14
20 including SI2upd and
repository update
ICP, IDP..
5-10
6
A,B,C
A
10
20 VLP1, TBP0, {ICP + IDP}
reboot partially parallel
12 ICP0,2,4, IDP0,2,4 ..reboot
parallel
B
5-10
20
32 Total: site A
VLP1
5-15
14
20 incl. Repository update
ICP, IDP..
5-10
6
12 ICP1,3,5, IDP1,3,5 ..reboot
parallel
5-10
C
TBP0
20
32 Total site B
5
4
10
5
4
10 Total site C
5-15
25
37 Total of CS2000 - CS5000 2
Table 4: Time required for cluster update installation (with downtime)
490
1
Backups are started across all ISPs in parallel; the runtime is defined by the system size and the system load..
2
for parallel update of site A-C, plus additional 5 minutes. Three DVDs are required!
Application recommendation for ETERNUS CS HE Update Installation Update handling instructions
13.5 Update handling instructions
13.5.1 Rolling Update
The procedure for the rolling update is described in the service manual, section:
Implementing the installation - rolling update for models CS1500 and higher.
i
This section only explains the rolling update for CS1500 and the ICP CS nodes and the
connected front-end applications.
!
Step
CAUTION!
All ISPs of the type ICP must be updated individually and consecutively and the
steps described in the following table must be followed each time:
Service engineer input
Action
5.1
Transfer front-end activities
See section “Example of the transfer of
front-end activities on the BS2000 Sserver” on page 493
5.2
updmc -u <version> ICP<n>c <CR> Start update of the ICP<n> (continue)
The displayed pre-update action is
automatically executed.
5.3
For example:ssh ICP<n> reboot
The service engineer executes the
displayed post update action for the ICP.
If a reboot is requested as post update
action, it must be initiated using the
reboot-command on the ICP (not via vtcon
on the VLP master).
Table 5: Excerpt from the table rolling update as of CS1500
491
Update handling instructions Application recommendation for ETERNUS CS HE Update Installation
13.5.2 Split cluster update
i
492
The procedure for the split cluster update is described in the service manual,
section: Implementing the installation - split cluster update for models CS1500 and higher.
●
Assuming a symmetrical front-end connection, the front-end activities are transfered
simultaneously as described in the handling instructions “Example of the transfer of
front-end activities on the BS2000 S-server” on page 493 to all ICPs of a location, while
the other location maintains the current backup operation of the front-end applications.
●
The software is then jointly updated on all ICPs of this location; the front-end activities
of the other location are transferred and the update is run at the other location.
●
The symmetrical distribution of the front-end activities at the two locations is the
conclusion. The cluster status existing before the update is thus re-established.
13.5.3 Example of the transfer of front-end activities on the BS2000 S-server
A rolling update of the ETERNUS CS HE can be performed interrupt-free for the BS2000
application on the S server, if tape devices of at least two ICPs are available in the BS2000.
All front-end activities of this ICP must be transferred to another ICP before the rolling
update for an ICP can be started.
This is as follows based on the example BS2000 on an S-server, which executes its Archive
tape activities via the ETERNUS CS HE ISPs (ICP1 and ICP5):
●
The service engineer checks the front-end activities on ICP1 via the menu Global Status
Monitor in the GXCC. On the ETERNUS CS HE side, 16 emulations each are
configured on both the ICP1 and ICP5 (virtual components Emu ICP1 LibDevice:
50...5F , ICP5 LibDevice: 10...1F).
Read/write activities on
devices on ICP1
493
494
●
On the application side on the front-end on the BS2000 S Server, the administrator
can use the command show-device-depot' to check the logical devices in the depot (in this
example 50 -5F and 10…1F).
●
The administrator checks the existence of the logical devices (50 ..5F and 10...1F) in the
Robar SV configuration.
●
The administrator detaches the logical devices of the front-end application (belonging to
the ICP1) using the command det-dev *d(50,5F ). The currently used devices
change initially to the status detach-pending.
●
The service engineer checks whether the front-end activities automatically transfer to
ICP5 after detaching the devices on the ICP1. If this is the case, no further action is
required by the administrator. If this is not the case (possibly unanswered messages to
the BS2000 console), then the administrator must intervene and ensure that all frontend activities that previously ran on the ICP1 are now started on another ISP (here
ICP5).
The first device is
already mounted
on ICP5.
495
496
●
The administrator and the service engineer wait until all application backups/restores
have been transferred from ICP1 to ICP5 and devices are no longer attached with ICP1
(virtual components emu instead of previous turquoise running+attached is now green =
running)
●
As soon as all front-end activities have been ended on ICP1 (see above), the Service
Engineer starts the rolling update on ICP1 (Step 5.2 in table 5 on page 491)
●
The service engineer executes the post-update action for ICP1 (Step 5.3 in table 5 on
page 491)
Figure 1: Figure 7: CentriStor Status - reboot ICP1
●
The service engineer waits until the "post-update-activities" have ended on the ICP1 and
the ICP1 is actively functioning again in the ETERNUS CS HE cluster.
●
The administrator now attaches in the BS2000 all logical devices of the ICP1 via the
BS2000 command att-dev *d(50.5f) and checks via the show-device command
whether all of the devices are attached and assigned.
497
498
●
The service engineer waits until the front-end application integrates the devices on
ICP1 and mounts on its devices.
●
The rolling update on the first ICP (in this case ICP1) is thus completed.
●
The procedure must then be applied to all other cluster ICPs accordingly.
table 5 on page 491
Glossary
3490 Emulation ➟ LD
A
ACI
ACS
ACSLS
AL
AML
AMU
Interface to the ABBA Robot via DAS
StorageTek Library
Controls the StorageTek libraries
Fibre Channel (➟ FC) operating mode, also abbreviated to FCAL
ADIC name for libraries
PC to monitor the AML Robot including the library
AutoVLP Failover Function
As the VLP Master plays a central role in the ETERNUS CS HE system, failure of the
VLP Master also causes the entire system to fail. To prevent this, a standby Standby
VLP (SVLP) can be integrated into the system as a backup computer. This SVLP is
inactive except for the monitoring function.
The AutoVLP failover function checks the functional integrity of the VLP Master at regular
intervals and, when it detects a malfunction, automatically takes the requisite steps: the
current VLP Master is split from the system and the SVLP is integrated into the system
as the current VLP Master. The system is then once more fully operational.
499
Glossary
B
Battery Backup Unit ➟ BBU
BBU
Emergency power supply which, in the event of a power outage, retains the data which
has not been saved in the memory for an unspecified time.
BSM Component
BSM Component (BSMC) stands for Backend Storage Manager and is the BSM Server.
Bugfix
A bugfix is a software modification to solve a problem which was reported via the PULS1
procedure. Such a problem report is identified by a PULS number with the format
A0nnnnnn (n=decimal digit).
1
PULS is the acronym for the German term for process and control system
500
Glossary
C
Cache
In the manual the term cache is sometimes used not only in its general sense but as a
synonym for Tape Volume Cache (TVC) or Tape Filesystem (TFS).
Cache Filesystem ➟ TFS
Cache Mirroring Feature ➟ CMF
Cache Policy
The Cache Policy is a feature of an LVG. It determines the behavior with regard to backup
in the TVC and to tape for the associated LVs. It can only be defined when a new LVG
is created. The following values are possible:
STANDARD:
TVC_RESIDENCE:
NO_BACKUP_TO_TAPE:
The logical volumes are displaced from the TVC according to an LRU algorithm if the memory space is required
for other purposes and after they have been
backed up to physical volumes.
The logical volumes are never displaced from the TVC,
even after they have been backed up to physical volumes.
The logical volumes are not backed up to physical volumes and can therefore never be displaced from the
TVC.
The default setting is STANDARD.
CAFS
The ETERNUS CS HE Appliance Filesystem (CAFS) is a cluster filesystem which, since CS
V4.0, has been used for the tape files systems of the TVC and also for the /DB and
/install2000 filesystems instead of DTVFS which was previously used under SINIXZ.
CAFS satisfies the ETERNUS CS HE requirements to a large degree, both in terms of
powerful processing of very large volumes of data and also in terms of data integrity and
availability even when hardware components are affected by a fault or fail completely.
CAFS enables ETERNUS CS HE operation to be maintained (apart from possible
reductions in performance) when the appropriate redundant configuration is provided,
even when disk faults occur, the RAID system crashes, one or more nodes in the cluster
crash, and faults occur in SAN and LAN communication, including complete failure of
the SAN.
501
Glossary
CAFS Cluster
A CAFS Cluster consists of CAFS Nodes, NSDs and a LAN which interconnects the
CAFS Nodes. An ETERNUS CS HE system forms a single CAFS Cluster.
When the CAFS Cluster is configured, a primary and a secondary Cluster Configuration
Server must be defined. The Cluster Configuration Server manages the information on
the CAFS Cluster Configuration and makes it available to all CAFS Nodes. When the
CAFS Daemon of a CAFS Node is started, it contacts the primary Cluster Configuration
Server (or the secondary Cluster Configuration Server if the primary does not respond)
to obtain the current data on the CAFS Cluster Configuration. Without this data it cannot
join the CAFS Cluster.
In order to prevent a split-brain situation in the CAFS Cluster when the SAN and LAN
are split into two or more parts, CAFS provides so-called Quorum Nodes and
Tiebreaker Disks. Provided more than half the Quorum Nodes are operating and can
be reached via the LAN, the CAFS Cluster is operational. In the models ETERNUS
CS500 and CS1000 both ISPs (IUP0 and IUP1) are configured as Quorum Nodes; in
the models ETERNUS CS1500 or higher both VLP ISPs (VLP0 and VLP1) and the
Tiebreaker Processor (TBP0) are configured as Quorum Nodes. When exactly half of
an even number of Quorum Nodes is accessible via the LAN, the Tiebreaker Disks
decide the issue. If the majority of the Tiebreaker Disks are available in this case, the
CAFS Cluster remains operational. Precisely one Tiebreaker Disk is configured for the
models ETERNUS CS500 and CS1000.
CAFS Cluster Configuration Manager
There is precisely one Cluster Configuration Manager in the CAFS Cluster. In the
models ETERNUS CS1500 or higher it executes on the VLP master.
When a CAFS Node crashes, the Configuration Manager decides whether a quorum
still exists and whether or not CAFS Cluster operation should continue.
CAFS Filesystem
A CAFS Filesystem is a filesystem of the type gpfs which is managed and maintained
by the CAFS. ETERNUS CS HE V4.0 or higher has not only the Tape Filesystems
(TFSs), but also /DB and /install2000 CAFS Filesystems.
CAFS Filesystem Manager
There is precisely one Filesystem Manager for each CAFS filesystem. In the models
ETERNUS CS1500 or higher it executes on the VLP master.
The Filesystem Manager implements status and configuration changes to the
filesystem, deals with mount and unmount requests and checks the efficiency of disk
utilization.
CAFS Node
A CAFS Node is an operating system map on a computer within a CAFS Cluster. In
ETERNUS CS HE each ISP is a CAFS Node, and vice versa.
502
Glossary
cascading
With the cascading feature ETERNUS CS HE offers the option of using another
ETERNUS CS HE system which is connected via FC as the backend system. The
ETERNUS CS HE system used as the backend is called the cascading destination. The
ETERNUS CS HE system which uses the cascading destination is referred to as the
cascading source.
The main feature of the cascading source is that it uses PVs in native tape format
(➟ native tape format). This format corresponds to the original format of the LV when it
is transferred from the host applications to ETERNUS CS HE; it consequently contains
no metainformation.
ETERNUS CS HE 1
(Cascading Source)
FCIP
FCIP
IDP
FC
Storage
Router 1
WAN
Storage
Router 2
FC
ICP
ETERNUS CS HE 2
(Cascading Destination)
The tunneling protocol FCIP (FibreChannel over TCP/IP) can be considered as the connection technology for long distances here, but it must be implemented outside
ETERNUS CS HE, for example in storage routers:
CIFS ➟ NAS
Cluster Configuration Server ➟ CAFS Cluster
503
Glossary
CMF
The Cache Mirroring Feature (CMF) is used to ensure data security and to provide
greater protection against data loss as the result of disasters. The data stored on the
internal hard disk system is mirrored synchronously to a second cluster location. This
is done over Fibre Channel connections, also when large distances are involved. Even
if a location is completely destroyed, all the data which was saved on such an
ETERNUS CS HE configuration will consequently be available.
CNC
ESCON channel operating mode
Configuration Manager ➟ CAFS Cluster Configuration Manager
CSC
CTL
StorageTek Library Interface
Complete SCSI address
CU serial number
The 5-character CU serial number is used to identify an ISP. The abbreviation CU
stands for Control Unit and is equivalent to ISP. The CU serial number is generated automatically and is unique within an ETERNUS-CS system. It can also be visible to the
outside, for example for backup applications when identifying the logical drives of an ICP.
In this case it may be necessary to adjust its value. Such a configuration change is performed by the maintenance staff.
The CU serial number can be displayed in XTCC.
The CU serial number is not to be confused with the 10-character Primergy product serial number which begins with Y.
504
Glossary
D
DAS
Interface for monitoring the AML robot (open systems)
Data Management API
A Data Management API (DMAPI) is a set of interfaces which permits applications to intercept filesystem calls in the GPFS as DMAPI events and to handle these in a manner
which is transparent for the caller. This functionality is required above all for the recall
function.
Distribute and Activate ➟ DNA
DNA
The Distribute and Activate (DNA) function must be invoked in GXCC every time a
change is made to the configuration of the ETERNUS CS HE system. This ensures that
the new configuration is distributed to and activated on all the ISPs.
E
Emulation
An emulation is a functional simulation of one system by another. The emulated system
receives the same data, executes the same programs and achieves the same results
as the original system.
Example: A logical drive (LD) emulates a physical drive (PD).
ETERNUS CS HE System Messages ➟ System Messages
Extented Tape Control Center ➟ XTCC
505
Glossary
F
Failover ➟ AutoVLP Failover Function
FC
Fibre Channel (FC) is a standard which was designed for serial and continuous highspeed transfer of large volumes of data. It is also used in the Storage Area Network (SAN)
within ETERNUS CS HE and in some cases for the connections between the ICPs and
the hosts and between the IDPs and the back-end devices. The FC controllers used in
ETERNUS CS HE support bandwidths of between 1 Gbit/s (Gigabit per second) and
4 Gbit/s.
In the case of a Fibre Channel, each device has a WWNN (World Wide Node Name)
and each port of a device a WWPN (World Wide Port Name) as a unique worldwide
identifier. Each of these is a 64-bit address which is generally presented in hexadecimal
format as 8 bytes separated by colons.
A distinction is made between three types of Fibre Channel topologies :
–
–
–
Switched Fabric (FC-SW)
In the case of the Fibre Channel Switched Fabric, point-to-point connections are
switched between the channel via one or more FC switches.
Arbitrated Loop ( FC-AL)
In the case of the Fibre Channel Arbitrated Loop a logical bus is involved on which all
terminals share the same bandwidth. In ETERNUS CS HE, FC-AL can only be used
to connect back-end devices.
Point-to-Point (FC-P2P)
This refers to a direct connection between two terminals.
The FC Layer Model has 5 layers which have the following names:
–
–
–
–
–
FC-0 (Physical Layer)
FC-1 (Data Link Layer, coding/decoding the signals to be transferred)
FC-2 (Network Layer, flow control, service classes)
FC-3 (Common Services Layer, e.g. multicast, striping)
FC-4 (Protocol Mapping Layer, e.g. FCP, FICON)
FC Layer Model ➟ FC
FCIP
Internet-protocol-based storage networking technology (RFC 3821) which enables FC
data to be tunneled over IP networks.
FCP
FCP, like FICON, is a protocol of the uppermost layer FC-4 (Protocol Mapping Layer) in
the FC Layer Model. It defines how the SCSI protocol of the Application Layer above,
which is exchanged between the application and the terminal, is mapped onto the
services of the lower FC layers.
506
Glossary
FC Switch
An FC switch is the central component of an FC-based Storage Area Network (SAN). It is
capable of connecting each of the terminals which are connected in a star-shaped
configuration with any of the others and of guaranteeing a defined bandwidth for each
connection. The FC switches used for the internal SAN in the models ETERNUS CS500
and highter have 16, 24 or 32 ports.
Fibre Connectivity ➟ FICON
Fibre Channel ➟ FC
Fibre Channel Protocol ➟ FCP
Fibre Channel Switch ➟ FC Switch
FICON
FICON, like FCP, is a protocol of the uppermost layer FC-4 (Protocol Mapping Layer)
in the FC Layer Model. It defines how the ESCON protocol of the Application Layer
above is mapped onto the services of the FC layers below.
Filegroup
Filegroup (FG) is an abstract configuration object - comparable with a Logical Volume
Group (LVG) in ETERNUS CS HE. A Filegroup represents a set of files in the filesystem
- more precisely: a subtree - and is a carrier of common attributes of these files. Among
other things, a Filegroup forms the basis of Shares which refer to the entire subtree represented by the Filegroup or parts thereof. Filegroups are disjunctive. In particular, Filegroups cannot be nested.
Filesystem Descriptor
The Filesystem Descriptor is a data structure with important descriptive data of a CAFS
Filesystem, such as the assigned NSDs, the current status and the references to the
logging files.
At least one Filesystem Descriptor exists for each CAFS filesystem. Depending on the
ETERNUS CS HE model, up to 3 replications are maintained, distributed over the various locations.
In the model ETERNUS CS50 only one Filesystem Descriptor exists for each CAFS filesystem.
In the models ETERNUS CS500 or higher a quorum is defined for each CAFS filesystem for the Filesystem Descriptor replications. If this quorum is fallen below, CAFS unmounts the filesystem concerned on all ISPs.
Filesystem Manager ➟ CAFS Filesystem Manager
507
Glossary
G
Global Extended Control Center ➟ GXCC
Globat Status
Global Status outputs all important operating data in graphical format, and allows you
to display important system data over configurable periods. For CAFS filesystems
displayed by Global Status also some maintenance functions are offered depending on
the respective state of these filesystems.
Graphical User Interface ➟ GUI
GUI
Graphical user interface for maintaining and operating the ETERNUS CS HE.
➟ Tcl/Tk GUI
➟ Web GUI
GXCC
GXCC is the user interface for operation, maintenance and monitoring of ETERNUS CS
HE.
It is a program with X user interface which supplies a complete graphical image of an
ETERNUS CS HE systems which includes all the connected devices and ISPs, such as
ICP, IDP and VLP. GXCC handles all ISPs and other components of an ETERNUS CS
HE network as a unit.
H
HA
HCC
Fibre channel or ESCON adapter in ETERNUS CS HE
Software running on MVS for AML access
Header
At the start of each physical tape written by ETERNUS CS HE there is an 80-byte header
followed by a Tapemark.
Hierarchical Storage Management
Hierarchical Storage Management (HSM) stands for the overall solution for virtualizing
the filesystems by increasing the RAID system capacity by means of tape storage.
508
Glossary
Hotfix
A hotfix is a software correction which is created to correct a high-priority customer
problem and is read in on the customer system concerned specifically to correct this
customer problem.
A prerequisite for providing a hotfix is a message in the PULS procedure.
Every hotfix software correction is always integrated into the next service pack. If this is
not possible because of a lack of time, a new hotfix must, if necessary, be created on
the basis of the new service pack.
HSM Component
HSM Component (HSMC) is the short name for Hierarchical Storage Management.
HSM Copy
An HSM Copy is a copy of a file on a tape medium which is generated by the HSM Component.
HSM Service
HSM Service (HSMS) is the name of the entire stack for HSM on an IDP (including the
subcomponents for ILM Component, HSM Component, and BSM Component).
HSMS_MGR ➟ HSMS Manager
HSMS Manager
HSMS Manager is the Broker Manager for the HSMS-Broker objects. The HSMS Manager contains the management functions for the subcomponents ILMC, HSMC, and
BSMC and the HSMS central management of cross-component objects for cross-component coordination.
HSMS Physical Device Services
HSMS Physical Device Services (HPDS) serve the HSMS Physical Devices in accordance with the PDSs in ETERNUS CS HE.
HSMS Physical Devices
HSMS Physical Devices (HPD) are the tape drives used by HSMS in the HSMS Tape Libraries.
HSMS Physical Library Service
HSMS Physical Library Service (HPLS) refers to the control of an HSMS Tape Library and
is comparable with the PLS.
HSMS Tape Library
The HSMS Tape Library (HTL) is a library which is used by HSMS.
509
Glossary
I
ICP
In the ETERNUS CS HE system the ICP is the interface to the host systems connected.
These are connected using ESCON, FICON or FCP.
The ICP’s principal task is to emulate the physical drives for the host systems
connected.
The predefined host names for this ISP type are ICP0, ICP1, etc.
ICP_IDP
An ICP_IDP combines the attributes of an ICP and those of an IDP: this computer has
interfaces to the hosts and to the tape drives.
Hosts
Interfaces
to the host
ETERNUS CS HE
Robots
external LAN
ICP_IDP
internal LAN
Interfaces to
tape drives
FC
The ICP_IDP is the only ISP type used in the models ETERNUS CS500 and CS1000
and consequently has the attributes of a VLP.
IUP (Integrated Universal Processor) is a synonym for ICP_IDP.
The predefined host names for this ISP type are IUP0 and IUP1.
510
Glossary
IDP
The IDP is the interface to the tape drives connected. Either a SCSI or FC connection
is used.
The IDP is responsible for communication with the real tape drives.
The predefined host names for this ISP type are IDP0, IDP1, etc.
ILM Component
ILM Component (ILMC) implements the ILM Service part in the HSM Service.
ILM Policy
This term refers to a set of Policy Rules for controlling Migration and Recall.
ILM Policy Engine
This is a mechanism contained in the GPFS for processing an ILM Policy. It executes
the rules defined in the policy.
ILM Policy Job
This term refers to the application of a policy for a filesystem at a specified time or when
space is required.
ILM Policy Rule
This refers to a single rule for selecting files and applying a defined operation to these
files.
Information Lifecycle Management
Information Lifecycle Management (ILM) is a GPFS enhancement which supports the Premigration and the Migration of files on the basis of policies.
Integrated Channel Processor ➟ ICP
Integrated Device Processor ➟ IDP
Integrated Standard Processor ➟ ISP
Integrated Universal Processor ➟ ICP_IDP
511
Glossary
ISP
ISP (Integrated Standard Processor) is the general term for a processor which is used
in an ETERNUS CS HE system. Depending on the peripherals and the software configuration, a distinction is made between the following types of ISP:
ICP
NAS ICP
IDP
NAS IDP
ICP_IDP
TBP
VLP
VTC
ISP with host connection using ESCON, FICON and/or FCP.
ISP with LAN ports and two internal FC ports.
ISP without host adapter but with tape drives.
ISP with SAN interface and/or LAN interface for NAS filesystems.
This ISP type combines the attributes of ICP, IDP and VLP in one ISP. An
ICP_IDP has both a host adapter and a SCSI or FC controller to operate
real tape drives and robots. IUP (Integrated Universal Processor) is a
synonym for ICP_IDP
This ISP type is provided in the models ETERNUS CS1500 or higher. The
TBP (Tiebreaker Processor) is one of the three Quorum Nodes in the CAFS
Cluster. Its function is to prevent a split-brain situation.
Processors of this type always occur in pairs in the models ETERNUS
CS1500 or higher. Central management processes, in particular VLM and
PLM, run on one of the two, the VLP Master. The other, the Standby VLP
(SVLP), monitors the operating status of the VLP Master and is kept ready
to take over the VLP Master’s tasks.
In the smallest model ETERNUS CS50 this is the only ISP and combines
the attributes of the ICP, IDP and VLP. For the TVC the local disks are
configured to form a RAID10 instead of an external RAID system.
ETERNUS CS HE
Master
Host
ports
Console port
SVLP
IDP
ICP
FC Switches
ICP
IDP
Robot
ports
VLP
RAID
Systems
TBP
Figure 2: ETERNUS CS HE configuration with 5 ISPs (2 ICPs, 2 IDPs and one VLP)
IUP ➟ ICP_IDP
512
Glossary
L
LD
A logical drive is a virtual, non-physical drive which presents the host applications the
interface of a real drive which is emulated by a program. Two types of emulation programs are distinguished in ETERNUS CS HE; these are referred to as VTD (Virtual
Tape Device) and 3490 Emu (or Emu for short).
VTD emulations are used when the hosts are connected via FC SCSI. The emulated
device types are EXABYTE/Mammoth2, FSC/CentricStor, IBM/IBM 3590E1A, BM/LTO
Ultrium 2 and STK/9840B.
3490 emulations are used when the hosts are connected via ESCON or FICON. The
emulated device types are IBM 3490-E and Fujitsu F6473K.
Depending on the authorization information (license keys) installed, a total of up to 128
LDs can be operated per ICP. However, more than 64 LDs per ICP are only permitted
for ICPs whose host channel connections are all of the type FC SCSI.
Local Unit ➟ LUN
Location
A location is a combination of ETERNUS CS HE components which are physically close
to each other. In other words these components are either accommodated in the same
rack or in multiple racks which are set up immediately next to each other.
The models ETERNUS CS50, CS500 and CS1000 form a single location (SingleLocation System).
In ETERNUS CS1500 or higher up to 3 locations are possible. These are assigned the
standard names A, B, and C (Multi-Location System).
If the locations are at geographically separate sites, this is called a Multi-Site System.
Otherwise the term Single-Site System is used.
Logical Drive ➟ LD
Logical Unit Number ➟ LUN
Logical Volume ➟ LV
Logical Volume Group ➟ LVG
513
Glossary
LUN
A Logical Unit Number (LUN) was originally, and still is, used to address subunits of a
SCSI target, for example individual drives of a tape library, in the event of I/O requests.
LUN masking refers to the masking of LUNs of a SCSI target in such a way that particular
users can only access particular devices. In ETERNUS CS HE this functionality is
implemented by means of LUN mapping, in which the original LUN range specified by a
particular host is mapped onto an equally large map LUN range on the available devices
(logical devices) in such a way that the devices represented by the mapped LUNs are
available exclusively to this host.
In the storage world the term LUN is used to refer to the subdivision of a RAID system
into logical disks and has been extended to include logical unit, as a result of which LUN
refers to a virtual disk as seen from outside of the RAID system.
LUN Masking ➟ LUN
LUN Mapping ➟ LUN
LV
A logical volume (LV) is a file which is stored temporarily in a tape filesystem of the Tape
Volume Cache (TVC) and stored permanently in a physical volume (PV). The standard
size in an LVG is 900 MB, but this can be selected in discrete steps: 2, 5, 10, 20, 50,
100 oder 200 GB.
Depending on the model, up to 1.5 million LVs can be defined in an ETERNUS CS HE
system, the name of each (VSN) being unique in the system.
LVG
Group of logical volumes for which the same rules apply.
LV stub
The part of a logical volume which (regardless of the Cache Policy) remains resident in
the TVC is identified with LV stub or, in an unambiguous context, with stub. It is 128 KB
in size and contains all the metainformation and the first data blocks of the logical
volume.
514
Glossary
M
Manager Node
When the CAFS Cluster is configured, the CAFS Nodes which can be considered as
Manager Nodes for the roles of Configuration Manager and Filesystem Manager are
specified. The Manager which is then active during CAFS Cluster operation is then
determined automatically.
In then models ETERNUS CS500 and CS1000 both ISPs (IUP0 and IUP1), and in the
models ETERNUS CS1500 or higher both VLP ISPs (VLP0 and VLP1) are configured
as Manager Nodes. In the model ETERNUS CS50 the single ISP is naturally also a
Manager Node.
Message Manager ➟ MSGMGR
Migration
Files which have not yet been premigrated are saved on tape. Their file contest on disk
is released except for a stub. Files which have been premigrated are released except
for a stub.
MSGMGR
Exists once in ETERNUS CS HE. Filters and saves the ISPs’ system messages and
implements predefined measures (e.g. service call, sends SMS, etc.). The MSGMGR
is also responsible for forwarding the system messages to the user interface.
Multi-Site System ➟ Location
515
Glossary
N
NAS
Network Attached Storage (NAS) is storage which is made available by an autonomous
computer, also referred to as a filer, in a LAN via the NFS (Network File System) or
SMBP (Server Message Block Protocol). The latter is also referred to as CIFS (Common
Internet File System), LAN Manager Protocol or NetBIOS Protocol and is implemented
in Linux by means of the free software Samba.
In ETERNUS CS HE the role of a filer is performed by the ICP, ICP_IDP (IUP) or VTC.
NAS ICP
Der NAS ICP bildet innerhalb des ETERNUS-CS-HE-Clusters die Schnittstelle zum
Kunden-LAN für Zugriffe auf Netzwerkdateisysteme, die via NFS und/oder CIFS freigegeben wurden. Im Gegensatz zu den ICPs der VTL benötigt ein NAS-ICP mindestens
ein externes Netzwerkinterface.
Ein NAS-ICP ist mit 4 LAN-Ports ausgerüstet. Für den Anschluss an den NAS-Cache
besitzt der NAS ICP zwei interne FC-Ports. Die zentrale Aufgabe des NAS-ICP ist die
Bereitstellung von Filesystemen für Applikationen, die auf den Hosts des Kunden-LAN
laufen. Die Filesysteme können in ein hierarchisches Speichermanagement integriert
sein.
NAS IDP
Auf dem NAS-IDP laufen die Dienste des hierarchischen Speichermanagements. Diese
benötigen den direkten Zugriff auf die Ressourcen des Hintergrundspeichers.
Der NAS IDP ist zuständig für die Kommunikation mit den Tape Libraries und Bandlaufwerken, um Kopien von Dateien aus NAS-Filesystemen auf Bandvolumes zu speichern
bzw. von dort abzurufen. Er ist mit den dafür erforderlichen SAN- und/oder LAN-Schnitstellen ausgestattet. Die Kommunikation mit den anderen Rechnern des ETERNUSCS-HE-Clusters erfolgt über eine redundante LAN-Verbindung.
NAS Filesystem
A NAS Filesystem (NASFS) is a filesystem in the CAFS, in which ETERNUS CS HE provides shares for storing data via NAS interfaces (NFS, CIFS).
native tape format
The native tape format of a PV corresponds to the original format of the LV as transferred
from the host applications to ETERNUS CS HE; it consequently contains no metainformation. The assignment between LV and PV is 1:1. The VSNs of the LV and assigned
PV are identical.
Native tape format is mandatory for a PV which is to be saved at a cascading destination. But native tape format is also permitted for backup to physical backend devices.
Native tape format is configured by assigning the PVG attribute Type the value NATIVE.
NDMP
Standardized interfaces at application level (Layer 7 of the OSI Reference Model) for
data transfer and backup control in the NAS environment
516
Glossary
Network Shared Disk ➟ NSD
NFS ➟ NAS
NSD
The term Network Shared Disk (NSD) refers to a disk which has been assigned a name
that is unique within the CAFS Cluster. The disk can be: a physical disk, a partition of a
physical disk, a logical disk (LUN) or a partition of a logical disk. Normally all ISPs are
connected to an NSD via the SAN. When this direct access to an NSD is interrupted,
access must take place over the LAN via the primary or secondary NSD server which
is assigned to this NSD.
The NSD name begins with rd if the NSD is contained in an external RAID system,
otherwise it begins with the name of the ISP on whose local disks it resides. The
following naming schema is used:
<NSD-name>
rd<xx>L<yyyy>[p<z>] or <ISP-name>L<yyyy>[p<z>]
<xx>
RAID number, 2-digit, decimal
<ISP-name>
ISP name
<yyyy>
LUN, 4-digit, hexadecimal
<z>
Partition number, 1- or 2-digit, decimal
An NSD which is assigned for use by a CAFS Filesystem has the NSD Usage attribute,
which has one of the following values:
dataAndMetadata
The NSD contains both metadata and user data.
dataOnly
The NSD contains only user data and no metadata.
metadataOnly
The NSD contains only metadata and no user data.
descOnly
The NSD contains no user data and no metadata, but a socalled Filesystem Descriptor.
The NSD is automatically assigned the appropriate value for the ETERNUS CS HE
model and for the location concerned during the GUI configuration of the CAFS
Filesystems. This value can only be set explicitly in Expert mode.
The value of the NSD Failure Group attribute is also set automatically and can only be
modified when the GUI is in Expert mode. NSDs which can all fail simultaneously as the
result of a particular error event, for example all NSDs at one location, are assigned to
the same NSD Failure Group. If, for example, the replication factor 2 is set for the user
data and/or metadata of a filesystem, CAFS attempts to store the two copies in NDSs
in different NSD Failure Groups so that the user data and/or metadata remains available
when only one NSD Failure Group crashes.
NSD Failure Group ➟ NSD
517
Glossary
NSD Name ➟ NSD
NSD Server
An NSD Server is a CAFS Node which must be connected directly to the NSD which it
accesses on behalf of other CAFS Nodes. A primary and a secondary NSD Server can
be configured for each NSD. A CAFS Node can perform the role of the NSD Server for
multiple NSDs. It can simultaneously be the primary NSD Server for some NSDs and
the secondary NSD Server for others. If a CAFS Node has either no or only restricted
access to an NSD (e.g. failure of either both or one of the redundant SAN connections),
it communicates with the associated primary NSD Server, and if this does not respond,
with the secondary NSD Server.
As in ETERNUS CS HE all ISPs (with the exception of the TBP) are connected to all
NSDs via the internal SAN and via the internal LAN, and with each other also via the
internal LAN, each one of them satisfies the requirements to be the NSD Server for
each NSD. For the models ETERNUS CS500 and CS1000, IUP0 is configured as the
primary NSD Server and IUP1 as the secondary NSD Server for all NSDs. In the model
ETERNUS CS1500 or higher VLP0, which belongs to Location A, is the primary NSD
Server for all NSDs of Location A and the secondary NSD Server for all NSDs of
Location B, while VLP1, which belongs to Location B, performs the complementary
NSD Server roles.
NSD Usage ➟ NSD
O
OCI
Operator Command Interface (OCI) is a generic term for the commands of the PLM
(plmcmd, plmif), the VLM (vlmcmd, vlmif) and the VLMF (vlmfif). All these
command names are linked to the oci program, which implements the user interface
and functionality - in particular with regard to logging and tracing - which are common
to all commands.
Operator Command Interface ➟ OCI
Owner Node of a Filesystem
This is a node on which an HSM Component deals with the DMAPI events for a filesystem.
518
Glossary
P
Patch
A patch is a software correction which corrects a problem discovered during quality
assurance or on the customer’s systems and is provided globally. All patches in a
service pack are contained on the patch CD.
To guarantee the software integrity of the customer systems, all the patches contained on
the patch CD must always be installed.PERFLOG
Exists once in each ETERNUS CS HE. Obtains and stores the performance data.
Global Status supplies the performance data.
Performance Logger ➟ To guarantee the software integrity of the customer systems, all
the patches contained on the patch CD must always be installed.PERFLOG
PD
A Physical Drive is a phsysical tape cartridge drive which is connected to the IDP.
PDS
Software for controlling tape cartridge drives.
Physical Device Server ➟ PDS
Physical Drive ➟ PD
Physical Library
A Physical Library (PL) is a physical robot control or a physical partition of a tape robot.
Physical Library Manager ➟ PLM
Physical Library Services ➟ PLS
Physical Volume ➟ PV
Physical Volume Group ➟ PVG
PLM
The PLM coordinates all requests for the peripherals connected (robot systems, tape
drives). The data management of the PLM contains information about where and on
which physical volume (PV) each logical volume (LV) is stored.
PLS
The PLS is the link between ETERNUS CS HE and the robot archive. Requests to the
robots, e.g. to move a tape cartridge in the robot archive, are issued on behalf of the
PLM.
Preferred Node of a Filesystem
This is a node on which an HSM Component initiates HSM management of a filesystem.
Premigration
A tape copy of a file is created. The file content is retained on disk.
519
Glossary
PV
A physical volume (PV) is a data storage which is managed by the PLM (Physical Library Manager). The following cases must be distinguished here:
1. The PV is a real magnetic tape cartridge on which generally multiple logical volumes (LVs) are stored together with additional metainformation in a CS-internal tape
format.
2. The PV is a real magnetic tape cartridge on which precisely one logical volume is
stored in native tape format (➟ native tape format). This format corresponds to the
original format of the LV when it is transferred from the host applications to
ETERNUS CS HE; it consequently contains no metainformation. PVs of this type
occur particularly when the ETERNUS CS HE system is functioning as a cascading
source, but they can also occur independently of the existence of cascaded
ETERNUS CS HE systems.
3. The PV is a virtual magnetic tape cartridge on which precisely one logical volume
is stored in native tape format. In this case the ETERNUS CS HE system functions
as a cascading source.
The VSN of a PV is defined when the PV is added to a PVG. The other configurable
attributes of a PV correspond to the attributes of the assigned PVG. The Type attribute
has the value NATIVE for PVs in native tape format, and in all other cases the value
STACKED.
PVG
Group of physical volumes for which the same rules apply.
Q
Quorum Node ➟ CAFS Cluster
520
Glossary
R
Reconciliation
This term refers to an action of the HSM Component for comparing the contents of a
filesystem with the managed metadata. For example, as a result of the reconciliation the
metadata for deleted files is invalidated on the BSM.
RAID (Redundant Array of Independent Disks)
A RAID System consists of at least a RAID controller and a disk array. A RAID controller
organizes the data on the disk array in such a manner that a disk error will not result in
any data being lost and that higher read and write speeds can be achieved than with a
single disk. Loss of data is prevented by redundant storage of the data on different
disks, i.e. by mirroring. Higher read and write speeds are achieved by striping, i.e. by
splitting the data into stripes which can be accessed in parallel. Precisely how these two
basic functions work on their own and in combination is specified by the RAID Level.
In ETERNUS CS HE the two mirrored system disks of an ISP form a RAID system of
RAID Level 1 (simple mirroring). The 6 internal disks which are used in the model
ETERNUS CS50 for the TVC, on the other hand, are configured as a real RAID system
of RAID Level 10. Here striping takes place using disks which are mirrored in pairs
(RAID 0 via multiple RAID 1).
In the models ETERNUS CS500 or higher external RAID systems which are connected
to the ISPs via the internal SAN and the internal LAN are used for the TVC. A RAID
system of this type consists of so-called shelves. A shelf contains up to 15 disks and is
equipped with redundant power supply modules and fans. The shelf which is also
equipped with 2 RAID controllers is called a RAID basic unit. A shelf without RAID
controllers is called a RAID extension. An external RAID system which is used in the
models ETERNUS CS500 or higher consists of one RAID basic unit and up to 7 RAID
extensions, and RAID Level 5 is configured for each of these RAID systems.
RAID System
A RAID (Redundant Array of Independent Disks) system consists of one or two RAID
controllers and multiple physical hard disks. These are organized as a logical disk drive
which permits a greater storage capacity, greater data security and/or greater
throughput than a single physical disk drive.
The TVC of an ETERNUS CS HE system uses one to up to eight RAID systems.
Recall
The file content on disk is recovered from the tape copy.
Redundant Array of Independent Disks ➟ RAID System
521
Glossary
Reorganisation
Depending on the configuration paramters, the logical volumes (LVs) saved on the
physical volumes (PVs) are automatically copied onto other physical volumes (PVs) of
the same physical volume group (PVG). This is done for the following reasons:
–
–
–
Effective use of the physical volumes (PVs) available
Prevention of physical and chemical aging processes
Faulty or inaacessible physical volumes (PVs)
This procedure is called Reorganisation. Reorganisation of an individual physical disk
(PVs) can also be initiated by the administration.
Replication Factor
The Replication Factor specifies the number of copies which the CAFS makes of the
user data, metadata and the Filesystem Descriptor of a CAFS Filesystem in order to
enhance availability in the event of a malfunction. Replication Factor 1 means no
replication; the data is only backed up once. With Replication Factor 2 the data is replicated and stored on NSDs in different NSD Failure Groups. A separate Replication Factor
can be assigned to the user data, the metadata and the Filesystem Descriptor.
During the GUI configuration of the CAFS Filesystems the Replication Factor is
assigned automatically in accordance with the ETERNUS CS HE model and the configuration of the locations. The Replication Factor for user data, metadata and the
Filesystem Descriptor of a CAFS Filesystem can only be set in the Expert mode of the
graphical user interface (GUI).
S
SAN
The entire data flow between all ETERNUS CS HE components (ISPs and external
RAID Systems) is handled via an internal Starage Area Network (SAN) which must be
configured redundantly for the models ETERNUS CS1500 or higher. It is implemented
by one FC switch with high-performance capability, or, when redundancy is provided in
single-site systems, by two of these, or by at least four of these in multi-site systems.
Two FC technologies are available: Multi Mode and Single Mode. In Multi Mode the
devices which are connected via 4 Gbit Fibre Channel can be located up to 150 m from
each other; in Single Mode the distance can be as much as 30 km.
Scope
A scope is understood as the scope of variables, namely program or file sections in
which the variables are usable and visible.
Example: The ETERNUS CS HE configuration file vtls_add.conf contains scopes for
special configuration settings which cannot be made via the graphical user interface.
522
Glossary
Server Management
The functions for monitoring the physical statuses of the hardware components of an
ETERNUS CS HE ISP, e.g. temperature, power, are referred to collectively by the term
Server Management. Since ETERNUS CS HE V4.0A these functions have been implemented using the corresponding software modules of PRIMERGY ServerView Suite.
One major task of Server Management is to analyze the System Event Log (SEL), an
NVRAM (non volatile random access memory) in which the BMC (Baseboard
Management Controller) and BIOS log hardware incidents in accordance with the
industry standard IPMI (Intelligent Platform Management Interface).
ServerView ➟ Server Management
Service Pack
A service pack consists of all the ETERNUS CS HE software which implements the
functions and patches released in an ETERNUS CS HE version at a particular time.
This includes the following data carriers:
–
–
a service pack DVD
a patch CD if patches have been released.
The data carriers can be used both for initial installation and for update installation.
A service pack is identified unambiguously by the combination of the number of the
service pack DVD and the number of the patch CD. When a new service pack DVD is
produced, i.e. its number is incremented by 1, the software stored on it incorporates all
the corrections of the patches in the last service pack.
Share
A Share is a directory node in a NASFS which is exported for NFS or CIFS accesses.
Single-Site System ➟ Location
Standby VLP ➟ SVLP
Storage Area Network ➟ SAN
523
Glossary
Storagepool
This is a logical group of storage devices as viewed in terms of, for example, performance, installation location or failure probability. ILM Policy Rules permit files to be moved between storagepools. A distinction is made in particular between internal and external storagepools. The background storage for HSM purposes in ETERNUS CS HE
is represented solely by external pools. From the ILM viewpoint, access to external
pools is only possible by means of interface commands.
Stub ➟ LV stub
SVLP
The SVLP (Standby VLP) is an ISP of the type VLP. It monitors the operational status
of the VLP Master and is kept ready to take over the VLP Master’s tasks if it crashes
(AutoVLP Failover Function).
System Messages
The messages generated by the software components of an ISP and collected locally
by syslog-ng in /var/log/messages are selected by the ETERNUS CS HE Message
Management in accordance with specific filter rules, stored centrally on the VLP master
under /msg/MESSAGE_HISTORY, and processed further on a specific basis according to
configurable settings. The messages selected are called ETERNUS CS HE system
messages, or system messages for short. The last 600 system messages can be displayed
by means of the GXCC function Show System Messages.
524
Glossary
T
Tape Filesystem ➟ TFS
Tape Filesystem Group ➟ TFG
Tapemark
A tapemark identifies the end of a header or logical volume (LV) on a physical tape.
Tape Volume Cache ➟ TVC
Tape Volume Group
Tape Volume Group (TVG) is a logical group of tape volumes on the NAS Backend as
seen from the viewpoint of the ETERNUS CS HE Administrator.
Tape Volume Pool Group
The Tape Volume Pool Group (TVPG) is the set of the one, two or three Tape Volume Pools
which are bundled to generate single, double or treble Tape Copies of the data.
Tape Volume Pool
The Tape Volume Pool is the set of volumes within a Tape library.
Tape Volumes
Tape Volumes (TVs) is the term used in ETERNUS CS HE to refer to the tapes and the
corresponding PVs.
TBP
All models ETERNUS CS1500 or higher contain precisely one Tiebreaker Processor
(TBP). This processor is one of the three Quorum Nodes in the CAFS Cluster and
prevents a split-brain situation when the LAN and SAN connections between Locations
A and B fail. For this reason a separate Location C is defined for the TBP. The TBP is
connected to all the other ISPs via the internal LAN. However, it has no connection to
the internal SAN.
The host name of the TBP is TBP0.
Tcl/Tk GUI
The Tcl/Tk GUI includes the components GXCC, Globat Status, XTCC
525
Glossary
TFG
A Tape Filesystem Group (TFG) can consist of one or more tape filesystems. The ETERNUS-CS administrator generates a TFG by selecting the tape filesystems which are to
belong to this TFG and by assigning the TFG a name. Assignment of a TFS to the
specified TFG does not take effect immediately after this selection has been made, but
only after further configuration steps (see below).
Each tape filesystem belongs to precisely one TFG. If a tape filesystem is not explicitly
assigned to a named TFG, it automatically belongs to TFG FLOATING, which exists implicitly and cannot be generated or deleted.
The assignment of an LVG to a named TFG or to TFG FLOATING defines that the LVs
of the LVG are distributed evenly over the various tape filesystems of just this TFG. The
corresponding definition of a TFG thus enables the tape filesystems of this TFG to be
used exclusively by the LVs of the assigned LVGs. As long as no LVG is assigned to a
specified TFG or as soon as no LVG is assigned to a specified TFG, the tape filesystems which are explicitly assigned to this TFG do not belong to the specified TFG but
to the FLOATING TFG.
If a TFS is removed from a TFG, the LVs stored in the TFS are moved to the remaining
tape filesystems of the TFG.
TFS
Since ETERNUS CS HE V4.0A a Tape Filesystem (TFS) is a filesystem of the type gpfs
(CAFS) in which the logical volumes (LVs) are stored temporarily. The tape filesystems
as a whole constitute the Tape Volume Cache (TVC). In ETERNUS CS HE the tape
filesystems are tied to a permanent naming schema: /cache/nnn, where nn stands for
a number between 100 and 899. When the Cache Mirroring Feature (CMF) is used, each
tape filesystem is mirrored. The tape filesystems are configured within the ETERNUS
CS HE configuration by means of GXCC. The storage space available for a TFS is
provided by NSDs being assigned exclusively to this TFS.
Tiebreaker Disk ➟ CAFS Cluster
Tiebreaker Processor ➟ TBP
TVC
The TVC (Tape Volume Cache) is the core of the entire virtual archiving system. It
represents the tape filesystems as a whole in which the logical volumes are stored
temporarily. One or more RAID Systems (up to 8) are used for this purpose.
526
Glossary
V
VACS
Emulation of an ACS in ETERNUS CS HE
VAMU
AMU Emulation in ETERNUS CS HE
VDAS
Emulation of a DAS in ETERNUS CS HE
Virtual Library Manager ➟ VLM
Virtual Library Processor ➟ VLP
Virtual Library Services ➟ VLS
Virtual Tape Controller ➟ VTC
Virtuelles Archivsystem ➟ TVC
VLM
Each robot request of the requesting host system is registered in the VLM. The requisite
emulations (VLMF, VAMU, VACS, VDAS, VJUK) are used in ETERNUS CS HE to
support the libraries.
The TVC is always accessed via the VLM.
VLP
The models ETERNUS CS1500 or higher contain two ISPs of the type VLP. One of
these assumes the role of the VLP Master, the other that of the Standby VLP (SVLP).
The central management processes, in particular the VLM and PLM, run on the VLP
Master. The Standby VLP monitors the operational status of the VLP Master and is kept
ready to take over the VLP Master’s tasks if it crashes (AutoVLP Failover Function).
The predefined host names for this ISP type are VLP0 and VLP1.
VLP Master
The VLP Master is an ISP of the type VLP. The central management processes, such
as VLM and PLM, run on it. VLP is sometimes used as a synonym for VLP Master.
527
Glossary
VLS
The tape archives emulated in ETERNUS CS HE are referred to as Virtual Library
Services (VLS).
Depending on the type and number of host systems connected, the VLS occurs in
various instances:
Host port
Instance
Library
BS2000/OSD, z/OS and OS/390
VAMU
ADIC
Open Systems Server (UNIX, Windows)
VDAS
CSC Clients of BS2000/OSD
VACS
StorageTek
LIB/SP Clients from Fujitsu
VLMF
Fujitsu
Open Systems Clients, UNIX and Windows
VJUK
SCSI
Open Systems Server (UNIX, Windows) with ACSLS
Volume Header
Each logical volume (LV) which is written to a physical tape is preceded by a 32,768byte Volume Header.
Volume Serial Number ➟ VSN
VSN
Name of the logical volume (LV) or of the physical volume (PV). Any combination of up
to 6 characters. The following are permitted:
–
–
–
Alphabetic characters in upper case
The special characters #, $, @, _, %, +, - (plus and minus characters may not
occupy the first position)
Digits
The Volume Serial Number must be unique in the name space of the LVs and in the name
space of the PVs in the entire ETERNUS-CS network.
VTC
VTC is an ISP type and was previously also the name of the smallest ETERNUS-CS
model which consisted of precisely one ISP of this type.
Like an ICP_IDP it combines the attributes of an ICP, IDP and VLP. In contrast to the
ICP_IDP it is equipped with additional boards. These boards and an internal RAID
controller are used to configure an internal RAID system which is used for the TVC.
The predefined host name for this ISP type is VTC.
VTD ➟ LD
528
Glossary
W
Web GUI
Web based, graphical user interface for administrators and operators.
WORM
WORM is the abbreviation for Write Once and Read Multiple (times). In other words: data
which is written to a WORM tape cannot be overwritten or modified and can be deleted
only by means of demagnetization. This permits, for example, audit-standard storage of
data during its entire archiving period.
WWNN
WWPN
Number of an FC node
Number of an FC port (for FC nodes with several ports)
X
XTCC
The graphical user interface XTCC permits displays and operations within an ISP.
529
Glossary
530
Abbreviations
A
ACF
ACI
ACS
ACSLS
ADIC
AL
AML
AMU
ASR&R
Automatic Cartridge Facility
AML Client Interface
Automatic Cartridge System
ACS Library Software
Advanced Digital Information Corporation
Arbitrated Loop
Automatic Media Library
AML Management Unit
Automatic Server Reconfiguration and Restart
B
BBU
BMC
BSM
BSMC
Battery Backup Unit
Baseboard Management Controller
Backend Storage Management
BSM Component
C
CAFS
CDB
CIFS
CMF
CSC
CSI
CSV
CSW
CTDB
CTL
CU
ETERNUS CS HE Appliance File System
Command Descriptor Block
Common Internet File System
Cache Mirroring Feature
Client System Component
Client System Interface
Comma Separated Values
Console Switch
Samba Cluster TDB Service
Controller Target LUN
Control Unit
531
Abbreviations
D
DA
DAS
DASD
DDM
DFHSM
DLDSW0
DMAPI
DNA
DPO
DTVFS
Device Adapter
Distributed AML Server
Direct Access Storage Device
Disk Drive Module
Data Facility Hierarchical Storage Manager
dual-labeled, dual-sided, write once
Data Management API
Distribute and Activate
Data Path Optimizer
Distributed Tape Volume File System
E
EBNF
EMU
EQDM
ERP
ESCD
ESCM
ESCON
ESS
Erweiterte Backus-Naur-Form
Virtual EMUlation of 3490E
Electronic Quality Data Management
Error and Recovery Procedure
ESCON Director
ESCON Manager
Enterprise System Connection
Enterprise Storage Server
F
FC
FCAL
FCH
FCIP
FCP
FCS
FG
FGM
FICON
FID
FRU
FSC
FTP
FUD
FW
532
Fibre Channel
Fibre Channel Arbitrated Loop
Fibre Channel Hub
Fibre Channel over IP
Fibre Channel Protocol
Fibre Channel Switch
Filegroup
Freigabemitteilung
Fiber Connection
FRU-Identifier
Field Replaceable Unit
Fault Symptom Code
File Transfer Protocol
Faulty-, Used- oder Dirty-Tapes
Firmware
Abbreviations
G
GB
GUI
GXCC
GXTCC
Gigabyte
Grafic User Interface
Global Extended Control Center
Global Extended Tape Control Center
H
HA
HACC
HBA
HCC
HCD
HDD
HPD
HPDS
HPLS
HSC
HSI
HSM
HSMC
HSMS
HSMS_MGR
HSP
HTL
Host Adapter
Host Access
Host Bus Adapter
Host Control Component
Harware Configuration Definition
Hard Disk Drive
HSMS Physical Device
HSMS Physical Device Service
HSMS Physical Library Service
Host Software Component
Hardware Software Interface
Hierarchical Storage Management
HSM Component
HSM Service
HSM Manager
Hauptspeicher
HSMS Tape Library
I
ICP
IDP
ILM
ILMC
IML
IODF
IOS
IPL
IPMI
ISL
ISP
ITC
IUP
Integrated Channel Processor
Integrated Device Processor
Information LIfecycle Management
ILM Component
Initial Microcode Load
I/O Definition File
Input Output Supervisor
Initial Program Load
Intelligent Platform Management Interface
Inter-Switch-Link
Integrated Standard/Service Processor
Intelligent Tape Controller
Integrated Universal Processor
J
JCL
Job Control Language
533
Abbreviations
K
KB
KVM
Kilobyte
Keyboard Video Mouse
L
LAN
LCU
LD
LED
LM
LMF
LMU
LP
LPAR
LRU
LSM
LSS
LUN
LV
LVD
LVG
LZ
Local Area Network
Logical Control Unit
Logical Drive
Light-Emitting Diode
Library Manager
Library Management Facility
Library Management Unit
Logical Path
Logical Partition
Least Recently Used
Logical Storage Module
Logical SubSystem
Logical Unit Number
Logical Volume
Low Voltage Differential
Logical volume group
Lieferzentrum
M
MCP
MD
MIB
MIM
MBK
MM
MSGMGR
MMS
MTU
Master Control Process
Mount Daemon
Management Information Base
Media Information Message
Magnetbandkassette
Multi Mode
Message Manager
Migration Supervisor Server
Maximum Transmit Unit
N
NAS
NASFS
NDM
NDMP
NFS
NFSD
534
Network Attached Storage
NAS Filesystem
Nucleus Device Management
Network Data Management Protocol
Network File System
NFS Service
Abbreviations
O
OCI
Operator Command Interface
P
PCI
PD
PDS
PERFLOG
PID
PL
PLM
PLS
PS
PSU
PTF
PV
PVG
Peripheral Component Interconnect
Physical Drive
Physical Device Server
Performance Logger
Process ID
Physical Library
Physical Library Manager
Physical Library Services
Power Supply
Power Supply Unit
Program Temporary Fix
Physical Volume
Physical Volume Group
R
RAID
RMT
ROBAR
RPLM
RSCN
Redundant Array of Independent (Inexpensive) Disks
Remote Monitoring and Administration
Robot Archive
Recovery-PLM
Registered State Change Notification
S
SAE
SAN
SAS
SCP
SCSI
SDD
SEL
SFP
SIM
SM
SMBD
SMBP
SNMP
SP
SPARC
System Administrator Edition
Storage Area Network
Serial Attached SCSI
Service Access System
Slave Control Process
Small Computer System Interface
Subsystem Device Driver
System-Event-Log
Small Form-factor Pluggable
Service Information Message
Single Mode
Samba Services
Server-Message-Block-Protokoll
Simple Network Management Protocol
SCSI Parallel Service Pack
Scalable Processor Architecture
535
Abbreviations
SPCC
SPS
SS
SSI
SSID
ssh
SVLP
Standard Peripheral Channel Connector
Standby Power Supply
SubSystem
Storage Server Interface
SubSystem IDentification
Secure Shell
Standby-VLP
T
TBP
TFS
TV
TVC
TVG
TVP
TVPG
Tie Breaker Processor
Tape File System
Tape Volume
Tape Volume Cache
Tape Volume Group
Tape Volume Pool
Tape Volume Pool Group
U
UCB
UFS
UPS
Unit Control Block
Unix File System
Uninterruptable Power Supply
V
VACS
VAMU
VD
VDAS
VDRV
VJUK
VLM
VLP
VLS
VMD
VPD
VOLSER
VSN
VT_LS
VTA
VTC
VTD
VTOC
536
Virtual ACSLS
Virtual AML Management Unit
Virtual Drive
Virtual DAS
Virtual Disk Driver
Virtual Jukebox
Virtual Library Manager
Virtual Library Processor
Virtual Mount Daemon
Vital Product Data
Volume Serial Number
Volume Serial Number
Virtual Tape und Library System
Virtual Tape Appliance
Virtual Tape Controller
Virtual Tape Device
Volume Table of Contents
Abbreviations
W
WLM
WORM
WWNN
WWPN
Workload Manager
Write Once and Read Multiple (times)
World Wide Node Number
World Wide Port Number
X
XRC
XTCC
Extended Remote Copy
Extented Tape Control Center
537
Abbreviations
538
Related publications
Ordering manuals
The manuals are available as online manuals, see http://manuals.ts.fujitsu.com, or in
printed form which must be payed and ordered separately at
http://manualshop.ts.fujitsu.com.
[1]
ETERNUS CS HE V.4.1A/V5.0A User Guide
[2]
ETERNUS CS HE V.4.1A/V5.0A Maintenance Manual (only available as an online manual
on the websites for service partners under
Home ➟ Partner Portal ➟ Support Portal ➟ Product Support ➟ Storage ➟
ETERNUS CS / CentricStor ➟ documentation:
https://partners.ts.fujitsu.com/com/service/ps/Storage/CentricStor/Pages/
default.aspx?CurrentFolder=551ac9b0-7ef7-4a3d-8f19-2bfcd002bde2).
[3]
BS2000/OSD-BC V#.## Introduction to System Support *)
[4]
MAREN V#.## (BS2000/OSD) MAREN for Administrators *)
[5]
MAREN V#.## (BS2000/OSD) MAREN for Users *)
[6]
ROBAR V#.## (BS2000/OSD, Reliant UNIX, Solaris) Tape Cartridge Archiving System *)
[7]
IBM Magstar Virtual Tape Server: Planning, Implementing, and Monitoring
(SG24-2229-05) **)
[8]
BS2000/OSD-BC V#.## System Installation *)
[9]
BS2000/OSD-BC V#.## Commands (several volumes) *)
[10]
StorageTek User Guide BS2000 CSC Version 6.2
[11]
ADIC Manual for HCC
[12]
StorageTek Manual, Client System Component for MVS, Systems Programmer Guide,
Release 4.0, 31343480
539
Literatur
[13]
User Guide SX Series Business Servers - Operation and Administration
Order Number: U41272-J-Z385-2-76
The manuals marked with *) are available under BS2000/OSD mainframes. “#.##” shows the
version number available on your host.
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 (“-”).
540
Environmental Protection
Returns, Recycling and Disposal
Details on the return and recycling of devices and disposables can be obtained from the
website:
http://ts.fujitsu.com/aboutus/company_information/business_excellence/
environmental_care/recycling.html
Further information on environmental protection
You will find further information on environmental protection on the website:
http://ts.fujitsu.com/abotus/company_information/business_excellence/
environmental_care/index.html
541
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
Index
/390 firmware
43
A
ACS
NetBackup 220
ACSLS 323
communication 404
ADIC library 35
AIX
device nodes 202
limitations 198
settings and info 198
useful commands 199
AMU PC 398
applications
limitations 23
B
backup times 246
block size 54
Brocade Silkworm 41
BS2 tapes 48
BS2000 partition 43
BS2000/OSD 43
bugfix 500
C
CA1 141
cascading
with ETERNUS CS HE V3.x systems
Cashion connection 405
cbn nodes 219
Celerra 209
changer 323
406
Cisco Switch 429
cleaning management
StorageTek libraries 402
cloning 207
cmd_proc
STK libraries 403
CommVault Simpana (Galaxy) 330
compression 55
Linux 8.0 155
NetApp 322
NetBackup 239
configuration
LANfree 302
Linux client 304
Linux Storage Agent 304
logical drives in z/OS 64
SAN environment 305
TSM server 305
configuration data
ETERNUS CS HE 395, 396
configuration tools
UNIX systems 395
Connectrix McData 41
control unit
BS2000 26
controller
EMULEX 153
coordinates
virtual drives 80
CSC 74
StorageTek 37
to BS2000 37
CSMVS 96
543
Index
D
DAS
NetBackup 220
DAS client 398
DAS server 398
DASADMIN
in ETERNUS CS HE 398
in host 398
Data Protector 177, 243
Datamover 209
LP10000 178
device depot 34
device name 39
device nodes
AIX 202
rewind 202
Solaris 163
device sharing 55
DFSMSrmm 127
diagnostic documentation 56
diagnostics
performance problems 418
DiskXtender for Windows 323
configuration 327
configuration in ETERNUS CS HE
Installation 326
driver
AIX 3590 198
AIX OST 198
Solaris EMULEX 162
Solaris NetBackup 177
dsmadmc 305
E
EMLXemlxu 178
EMTAPE 39
EMULEX
Solaris 159
EMULEX controller 153
Emulex Fibre Channel driver 177
Emulex HBAs 178
ETERNUS CS HE configurations 23
extended drive 323
544
F
FC connections
special features 408
FC switch
IP addresses 396
FCIP connection 429
Fibre channel
SAN Environment 408
fixed block length mode 24
Fujitsu libraries 406
G
GENTAB 39
Gresham 302
H
HACC 103
HAL 43
HBA 419
HCD 63
hotfix 509
HSC 149
HSI 54
323
I
IBMTape driver 303
ICP sharing 409
installation
GUI software 455
IOGEN 43
IP addresses
display 396
FC switch 396
ISP 396
libraries 396
ISP
IP addresses 396
L
L180
import tapes 402
LANfree configuration 302
LANfree data transfers
verification 306
Index
Leadville driver 177, 219
Legato (EMC) 323
LibAttach
Windows 280
libraries
IP addresses 396
library device name
ETERNUS CS HE 39
limitations
AIX 198
through application 23
Linux client
configuration 304
Linux Storage Agent
configuration 304
lmadmin 406
LMF 221
logging
UNIX systems 395
logical drives
configuration in z/OS 64
long distance 429
LP11000 178
LP9002L 178
LP9802 178
lpfc 177
lpfc.conf
Solaris 167
lpfc/qla driver 177
M
MAREN
BS2000 28
MDS-9000 family 429
MediaStor 326
more than 8 LUN
Windows 2000 205
MPxIO 177
N
NAS systems 207
NCS 74
NDM
BS2000 34
NDMP 207
NetApp 207
NetApp-Filer 208
NetBackup
Solaris extensions 177
non-rewind 238, 239, 241, 242, 280, 322
number of devices 54
O
ommVault
330
P
patch 519
PDS
display 397
performance problems
diagnostics 418
persistent binding
Solaris 165
physical volumes
sharing 19
PLP 406
PLS
display 397
port zoning 409
PSR 56
Q
qla 177
Qlogic Fibre Channel driver
Qlogic QLA2200F
Linux RedHat 153
Linux Suse 8.0 153
177
R
real drive
sharing 19
real robot
sharing 19
reconfiguration boot 43
RedHat LINUX 153
rewind
device nodes 202
RFC 3821 429
545
Index
RMM 127
ROBAR 35
rpm packages
302
S
S servers 57
SAN environment
configuration 305
service pack 523
settings and info
AIX 198
Solaris 157
Windows 2000 206
SFS 177, 219
SFS software package 178
SFS/Leadville driver 177
sharing
physical volumes 19
real drives 19
real Robot 19
SMAWdevsp 178
SMIT 302
Solaris
requirements 156
st.conf 173
SPARC64 mode 43
SQ server 60
ssi daemon 403
st.conf
Solaris 173
startup sequence
fibre channel 408
storage location 26
storage networking technology 429
StorageTek libraries 37, 402
SUN StorEdge SAN Foundation Software 177,
219
Sun/QLogic HBAs 178
SuSE SLES 9.0 156
SX servers 41
System Management Interface Tool 302
546
T
Tape 213
tape driver ST
Solaris 161
tapeutil 203
telnet 418
TIVsm-API 302
TIVsm-BA 302
TIVsm-stagent 302
TIVsm-tsmscsi 302
TLMS 141
traces
UNIX systems 395
TSM documentation 307
TSM server
configuration 305
U
UGEN
BS2000
26, 39
V
VACS 39, 323
ETERNUS CS HE 39
NetBackup 219
VAMU 39
ETERNUS CS HE 39
verification
LANfree data transfer 306
virtual drives
coordinates 80
virtual libraries
display 397
VJUK
configuration 270
configuring a SCSI library on AIX
emulation 320
vjukadmin 297, 301, 320
VTCP 368
VTD emulation 24
297
W
Windows 2000
Index
WSA 43, 49
WWNN
display 397
zoning 409
WWPN
display 397
X
X2000 43
X6767A 178
X6768A 178
Z
z/OS 63
zoning
configuration examples
ICP sharing 409
rules 409
411
547

ETERNUS CS Highend - Fujitsu manual server

Transcription

Similar documents

Korg Poly61

REWINDING HIPHOP`S MIXTAPE HISTORY

Music_Emp_audio_1980

Mackie Designs LM3204 Contractor`s Specs

DC DC - technicalaudio.com

The Broselow® system

Polaroid Pinhole Photo Kit User`s Guide

splinting avian fractures

Jacksonville Jaguars Select Cloud-Based Data Protection