Installation Guide CentricStor V3.1

Transcription

CentricStor V3.1
Installation Guide
Edition: 13 October 2006
Copyright © Fujitsu Siemens Computers GmbH, 2006.
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 was produced by
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Edition 7
13 October 2006
Fujitsu Siemens computers GmbH
User Documentation
81730 Munich
Germany
Comments
Suggestions
Corrections
Fax: 0 700 / 372 00000
e-mail: [email protected]
http://manuals.fujitsu-siemens.com
Submitted by
Comments on CentricStor V2.1/3.0/3.1
CentricStor Installation Guide
✁
Edition 7
Contents
1
1.1
1.2
1.3
1.4
1.5
1.6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Content and target group of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What’s new in this edition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Concept of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparatory considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14
15
15
16
16
19
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
Summary of permitted configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CentricStor configurations with BS2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CentricStor configurations with MVS/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CentricStor configurations in the SAN environment . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum block lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions on the host system side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions from the application program side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions for server farms using Open Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information on the open world . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
21
22
24
24
24
25
25
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.8.1
3.1.8.2
3.1.9
3.1.10
3.2
3.2.1
3.2.2
3.2.3
CentricStor in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activities in BS2000-CSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activities in CentricStor: EMTAPE, VAMU/VACS . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple CentricStor systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SX servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection via FC switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection without an FC switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the tape units in CentricStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
27
28
28
30
33
35
36
38
38
40
41
41
41
41
42
42
Edition 7
13 October 2006
Contents
3.2.4
3.2.4.1
3.2.4.2
3.2.4.3
3.2.5
3.2.6
3.2.7
3.3
3.3.1
3.3.2
3.3.3
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 . . . . . . . . . . . . . . . . . . .
CentricStor on S servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firmware/software statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
44
44
45
55
57
57
58
58
59
60
4
4.1
4.2
4.3
4.3.1
4.3.2
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.12.1
4.12.2
4.12.3
4.12.3.1
4.12.3.2
4.12.3.3
4.12.3.4
CentricStor on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subjects covered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of virtual drives in z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example configuration without ESCON-Director . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example configuration with ESCON Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Representation of the example configuration in CentricStor . . . . . . . . . . . . . . . . . . . . .
Definitions of the I/O devices in CSC/ASC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MVS/CSC start procedure (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System task CSC/ASC Library entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DFHSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DFRMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scratch alignment between CentricStor, MVS/CSC and DFRMM . . . . . . . . . . . . . . . . .
Configuration of the system task HACC in CentricStor operation via HACC . . . . . . . . .
Mount balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS390/zOS-CSC-5.1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of the CSC device statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Schematic diagram of the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
61
62
62
63
65
67
69
70
71
72
72
72
73
74
74
74
74
74
75
77
78
5
5.1
5.1.1
5.1.1.1
5.1.1.2
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
CentricStor on UNIX-type systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMULEX LP8000 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux RedHat (not officially released) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Qlogic QLA2200F Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux RedHat 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuSE Linux 7.1 · . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuSE Linux 8.0 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
79
79
80
80
80
80
81
13 October 2006
Edition 7
Contents
5.1.3
5.1.4
5.1.5
5.2
5.2.1
5.2.1.1
5.2.1.2
5.2.2
5.2.2.1
5.2.2.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
5.3.11
5.3.12
5.3.13
5.3.14
5.3.15
5.3.16
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.5
5.5.1
5.5.2
5.5.3
5.5.4
5.5.5
5.5.6
5.5.7
Edition 7
ST Linux SCSI tape driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Uniquely assigned device node to LUN in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Building the kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Versions of Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
FCdriver for EMULEX LP8000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Compressed WWNs in the device nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Logical drives in the autoconf -l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Useful commands: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Driver for EMULEX LP8000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Driver for JNI FCE2-6412-N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Installation and configuration of QLA2310F SUN . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
The tape driver st . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Device nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Persistent Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Checking the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Solaris systems in server farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Contents of the file lpfc.conf for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Contents of the file jnic.conf for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Contents of the file st.conf for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Extensions for Data Protector and SolarisTivoli . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Extensions for NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Useful commands: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Device nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Useful commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Configuration of the drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Device nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Testing the tape drives with tapeutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Problems with AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
13 October 2006
Contents
6
6.1
6.1.1
6.1.2
6.2
6.2.1
6.2.2
CentricStor in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important settings and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
131
131
131
132
133
133
134
7
7.1
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.3
7.3.1
7.3.2
7.3.3
7.3.4
CentricStor on NAS systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information on saving using NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Useful commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Celerra . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Useful commands, to be executed on the control node . . . . . . . . . . . . . . . . . . . . .
135
135
135
135
135
136
136
137
137
137
138
139
8
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.1.4.1
8.1.4.2
8.1.4.3
8.1.4.4
8.1.5
8.1.6
8.1.7
8.1.8
8.1.8.1
8.1.8.2
8.1.8.3
8.1.8.4
8.1.8.5
8.1.8.6
8.1.8.7
Tape management systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetWorker (Legato and FSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetWorker versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the “CentricStor” library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of virtual devices (NetWorker resource devices) . . . . . . . . . . . . . . .
ACSLS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DAS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scratch mount support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing from NetWorker 5.5 to 6.1... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a jukebox in NetWorker on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prefetch with FSC NetWorker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tips and tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
141
141
141
142
149
150
151
151
152
153
155
156
156
156
157
158
159
160
160
162
13 October 2006
Edition 7
Contents
8.2
8.2.1
8.2.2
8.2.3
8.2.3.1
8.2.3.2
8.2.3.3
8.2.3.4
8.2.4
8.2.4.1
8.2.4.2
8.2.4.3
8.2.4.4
8.2.4.5
8.2.4.6
8.2.4.7
8.2.4.8
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.3.4.1
8.3.4.2
8.3.4.3
8.3.4.4
8.3.4.5
8.3.4.6
8.3.4.7
8.3.4.8
8.3.5
8.3.6
8.3.6.1
8.3.6.2
8.3.6.3
8.3.6.4
8.3.6.5
8.3.6.6
8.3.7
8.3.7.1
8.3.7.2
8.3.7.3
Edition 7
NetBackup (Veritas) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMF configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection of the robot controller (VACS) via a firewall . . . . . . . . . . . . . . . . . .
Template for supporting SCRATCH mount . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation in Unix systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation of Data Protector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of CentricStor in Data Protector . . . . . . . . . . . . . . . . . . . . . . . . .
Template for scratch mount support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Template for PREFETCH support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bypassing lengthy backup times in Data Protector . . . . . . . . . . . . . . . . . . . . . .
Configuration as StorageTek ACS library . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration as a Grau-DAS library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setup of volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation example for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VJUK configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the robots under AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the robots under HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the robots under Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the robot devices under Windows . . . . . . . . . . . . . . . . . . . . . .
Configuration of a library under Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DAS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 October 2006
163
163
163
164
165
167
168
169
176
176
177
178
179
179
180
181
181
182
182
182
182
183
183
183
184
185
185
192
195
198
201
208
208
208
208
208
209
209
216
216
217
218
Contents
8.3.8
8.3.8.1
8.3.8.2
8.3.8.3
8.3.8.4
8.3.8.5
8.3.8.6
8.3.8.7
8.4
8.4.1
8.4.2
8.4.2.1
8.4.2.2
8.4.2.3
8.4.2.4
8.4.3
8.4.3.1
8.4.3.2
8.4.3.3
8.4.3.4
8.4.3.5
8.4.4
8.4.4.1
8.4.4.2
8.4.4.3
8.4.5
8.4.5.1
8.4.5.2
8.4.5.3
8.4.5.4
8.4.5.5
8.4.5.6
8.4.6
8.4.7
8.4.7.1
8.4.7.2
8.4.7.3
8.4.7.4
8.4.7.5
8.4.7.6
8.4.7.7
8.5
8.5.1
8.5.2
System specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tivoli / TSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration with Gresham EDT . . . . . . . . . . . . . . . . . . . . . . . . . .
Gresham installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gresham configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a SCSI library on AIX via VJUK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the VJUK configuration and notifying TSM . . . . . . . . . . . . . . . . . . . .
LANfree configuration without Gresham . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verification of LANfree data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reliant UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM-AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BrightStor ARCserve Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ARCserve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CentricStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 October 2006
218
218
219
220
220
221
222
222
223
223
223
223
224
226
226
227
227
228
228
230
231
232
232
233
236
236
236
237
237
240
241
241
241
242
242
242
242
242
243
243
243
244
244
244
Edition 7
Contents
8.5.3
8.5.4
8.6
8.6.1
8.6.2
8.7
8.7.1
8.8
8.9
8.9.1
8.9.1.1
8.9.1.2
8.9.1.3
8.9.1.4
8.9.2
8.9.2.1
8.9.2.2
8.9.2.3
8.9.2.4
8.9.2.5
8.9.3
8.9.3.1
8.9.3.2
Backup server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VJUK emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NAS filer - NetApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DiskXtender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration in CentricStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Library Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Volume Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add Logical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing DiskXtender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional software required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing tape drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Library Attach (1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing DiskXtender (6.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing MediaStor (6.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DiskXtender configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ascertaining the name of the tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring media services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
245
247
248
248
248
255
255
257
258
258
258
259
259
259
260
260
260
260
261
261
262
262
263
9
9.1
9.2
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.3.6
9.4
9.4.1
9.4.2
9.4.3
9.5
9.5.1
9.5.2
9.5.3
9.5.4
9.5.5
Useful commands and information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging, configuration tools, traces in UNIX systems . . . . . . . . . . . . . . . . . . . . . . . . .
Display of CentricStor configuration data for the service engineer . . . . . . . . . . . . . . .
CentricStor configuration data displays for the user . . . . . . . . . . . . . . . . . . . . . . . . . .
IP addresses and host names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Real devices (PDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Real libraries (PLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WWNN and WWPN of the FC connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control of ADIC / ABBA / AML libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DASADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication between client and server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Possible problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control of the StorageTek libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powderhorn to extend drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning management in StorageTek libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding tapes in Powderhorn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding tapes in L180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the ssi daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265
265
265
266
266
266
267
267
267
267
268
268
270
271
272
272
273
273
273
273
Edition 7
13 October 2006
Contents
9.5.6
9.5.7
9.5.8
9.5.9
9.6
9.7
9.8
9.8.1
9.8.2
9.8.3
9.8.3.1
9.8.3.2
9.8.3.3
9.8.3.4
9.8.3.5
9.9
9.9.1
9.9.2
9.9.2.1
9.9.2.2
9.9.2.3
9.9.3
9.9.3.1
9.9.3.2
9.9.3.3
9.10
9.10.1
9.10.2
9.10.3
9.10.4
Stopping the ssi daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cmd_proc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication between client and server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Possible problems and troubleshooting advice . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information on the Cashion connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information on Fujitsu libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Qualified fibre channel switches in the SAN environment . . . . . . . . . . . . . . . . . . . . . .
Features of the FC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Permitted FC switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zoning example (6 hosts on 3 ICPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the brocade switch via Internet Explorer . . . . . . . . . . . . . . . . .
Diagnostics in the event of performance problems . . . . . . . . . . . . . . . . . . . . . .
Host bus adapters (HBA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the host bus adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firmware download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP8000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QLA2200F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCE2-6412-N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BIOS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP8000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QLA2200F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCE2-6412-N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of a filter bridge for separating CentricStor™ . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start/stop script bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration file: csbridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ports used by CentricStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
273
274
274
276
276
277
277
277
278
278
278
279
280
281
286
287
287
288
288
288
288
288
288
288
289
290
290
290
295
299
10
10.1
10.1.1
10.1.2
10.2
10.2.1
10.2.1.1
10.2.1.2
10.2.1.3
10.2.1.4
10.2.1.5
10.2.1.6
Installation of the GUI software GXCC/XTCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information about the installation CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information about restrictions and known bugs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation on MS-Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation of the GUI documentation (optional) . . . . . . . . . . . . . . . . . . . . . . . .
Starting the GUI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the CA-Unicenter Extensions for CentricStor . . . . . . . . . . . . . . . . . . .
Deinstallation of the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
301
301
301
301
302
302
303
304
305
305
305
13 October 2006
Edition 7
Contents
10.2.2
10.2.2.1
10.2.2.2
10.2.2.3
10.2.3
10.2.3.1
10.2.3.2
10.2.3.3
10.2.4
10.2.4.1
10.2.4.2
10.2.4.3
10.3
10.3.1
10.3.2
10.4
10.4.1
10.4.1.1
10.4.1.2
10.4.1.3
10.4.1.4
10.4.2
10.4.2.1
10.4.2.2
10.5
10.5.1
10.5.2
10.5.3
10.5.4
10.5.5
10.5.6
10.6
Installation on a LINUX Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deinstalling the GUI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation on a SOLARIS Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deinstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation on a SINIX-Z Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deinstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Documentation of the GUI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the Documentation via the Help Function of the GUI . . . . . . . . . . . . . .
Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integrating the Snapshot Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS-Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LINUX Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOLARIS Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SINIX-Z Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functionality in Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Static Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions and known bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
306
306
307
307
307
307
309
309
310
310
311
311
312
312
312
313
314
314
314
315
316
317
317
317
318
318
319
320
320
321
321
321
11
Important information regarding the CentricStor environment . . . . . . . . . . . . . . 323
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Environmental Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Edition 7
13 October 2006
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
1 Introduction
CentricStor can be operated on BS2000 and MVX/ESA systems via an ESCON host
adapter, and on several variants of UNIX, Linux, Windows hosts and on BS2000 (SX and S
Server) via Fibre Channel Fabric.
This introduction describes the settings for this on the hosts, on the fibre channel
connection system and on CentricStor.
Edition 7
13 October 2006
13
Notational conventions
Introduction
1.1 Notational conventions
This manual uses the symbols and other notational conventions to draw your attention to
certain items of text. The following symbols are used:
This symbol indicates actions to be performed by the user (e.g.
keyboard input).
Ê
WARNING
!
i
The warning symbol denotes important instructions and items of information such as warnings.
This indicates information which is particularly important for the
functionality of the product.
[ ... ]
Square brackets are used to enclose cross-references to related publications, and to indicate optional parameters in command descriptions.
For names, commands and messages this typewriter font is used (e.g. the SETLOGON-PARAMETERS command).
The following examples show how to give commands on the graphical user interface of
CentricStor:
Example 1:
[GXCC - Function bar: Tools ➔ Global Status]; Global status function bar ➔ Tools
➔ Show Balloon Help Summary
Ê
On the function bar in GXCC, open the drop-down menu “Tools” and choose the
function “Global Status”. This part is enclosed in square brackets [..] to indicate
that the Global Status Window can also be permanently open.
Ê
If the global status window is open, open the drop-down menu “Tools” from the
function bar, and select the Function “Show Balloon Help Summary”.
Example 2:
[GXCC object function ➔ VLP ➔ Show Details or Maintenance]; XTCC object
function ➔ VLM ➔ Show logical Drives
14
Ê
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”.
13 October 2006
Edition 7
Introduction
Content and target group of this manual
1.2 Content and target group of this manual
This manual contains information on the host connection (BS2000, MVS/ESA, Linux, UNIX,
Windows...) of CentricStor.
●
It provides information for host system administrators about the settings needed to
connect their systems (BS2000, MVS/ESA, Linux UNIX, Windows...) to CentricStor.
●
There is advice for setting up libraries which can work both as a back end with
CentricStor or directly with the host.
●
It shows the zoning of an FC switch which can be switched between the host und
CentricStor.
●
It shows CentricStor service personnel how CentricStor should be configured for
connection to each of the host systems indicated.
Only the maintenance technicians who have the CentricStor root and service passwords
can access and edit CentricStor configurations. The CentricStor configuration is described
in the maintenance manual [1]. The configuration set up in CentricStor is displayed on the
graphical interface. It can also be output from the graphical interface in various ways and
displayed as a list. The relevant details can be found in the graphical interface manuals.
1.3 What’s new in this edition?
●
New
–
–
–
●
Updates
–
–
–
–
–
–
–
–
Edition 7
The vlmcmd command has been replaced by vlmif because this is now the official
CLI interface.
section “Information about restrictions and known bugs” on page 301
section “Restrictions and known bugs” on page 321
section “Activities in MAREN” on page 30
section “Configuration of virtual drives in z/OS” on page 62
section “VJUK emulation” on page 255
section “Permitted FC switches” on page 278
section “Installation on MS-Windows Platform” on page 302
section “Starting the GUI Software” on page 307 (LINUX)
section “Starting the GUI Software” on page 309 (SOLARIS)
section “Starting the GUI Software” on page 311 (SINIX-Z)
13 October 2006
15
Concept of the manual
Introduction
1.4 Concept of the manual
This manual is a supplement to the user and maintenance manual. The installation instructions are divided as follows:
1. General operating procedures and summary tables (system independent).
2. Connecting CentricStor to host systems, divided by system (BS2000, MVS/ESA, UNIXtype systems, and Windows).
3. Tape management systems (NetWorker,..Tivoli), divided by management system. Each
section contains an appendix detailing the operating-system specific features.
4. Practical instructions such as:
– Useful commands for UNIX systems.
– Instructions on accessing CentricStor configuration data
– Using libraries
– Setting FC switches
– Host Bus Adapter
– Configuration example for CentricStor (adding an ICP)
1.5 Preparatory considerations
The figure below shows which host components handle the various items of configuration
data in the CentricStor (CS).
The procedure to be followed depends on the system. Lines written in red apply to Open
Systems and BS2000 on FC (SX and S Server), lines written in blue apply to MVS/ESA and
BS2000/OSD.
16
13 October 2006
Edition 7
Introduction
Preparatory considerations
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 141)
Host adapter
Is the FC-HBA permitted on your host for CS (page 287)? Check
the version of the firmware and the BIOS settings (page 288) and
correct where necessary.
Library client
What are the data (IP address, port number) for the library client?
To which virtual drives and virtual volumes should it have access?
Enter values in the CS configuration.
Virtual driver/
Device nodes
Real libraries
Switch/Director
Check the version of the driver for the FC adapter.
Set your system so that the necessary device nodes are created.
(from page 79).
Add the CS drives to the BS2000 or MVS configuration files.
Should real libraries present in CS also be used as native?
Do you want the real drives to be cleaned by CS?
Set fibre channel zoning (page 278)
Set ESCON director (BS2000 and z/OS, page 27 ff, page 61)
CentricStor
Virtual devices
Set device emulations (device type, library address, library type,
corresponding configuration desired for the host)
Virtual libraries
Set up library emulation, set client access rights.
Real devices
Link real devices with library, set up cleaning management
Library
Library
Real devices
Edition 7
Start CentricStor as a client in a real library.
Set up cleaning management in a library. Where necessary,
partition real libraries (examples from page 268).
13 October 2006
17
Preparatory considerations
Introduction
The following tests and settings should be made before the starting configuration work.
●
CentricStor can emulate various tape cartridge drives. This manual indicates which
drive types can be used with your system, and provides instructions on how to create
device nodes with the necessary properties.
We recommend that you use the emulations given in these instructions. FujitsuSiemens has carried out extensive testing precisely for this configuration.
●
Individual management systems (e.g. NetWorker, Tivoli,...) only support particular
types of library and drive. Before you start, you should note which library your tape
management system can operate and then configure CentricStor accordingly. In order
to ensure trouble-free operation, the configuration in CentricStor must match the host
configuration exactly.
●
Cases where several hosts are to be connected to CentricStor. In these cases you
should first establish if and how virtual volumes and drives will be separated from each
other in the emulated libraries, and then set the emulations accordingly.
●
Set the number and allocation of the virtual drives.
You should take steps to ensure that any virtual drive in an open system is connected
precisely to one FC adapter only.
!
●
If real libraries of CentricStor and the hosts are to be used jointly, set how the drives and
storage areas are divided.
This division and the cabling of the library and the drives with CentricStor must be
completed before CentricStor is configured.
●
Establish how the cleaning of the drives is carried out. CentricStor can take over the
cleaning of the drives assigned to it, including the administration of the cleaning
cartridges. Not all libraries, however, allow the drive specific administration of cleaning.
●
This manual describes the host adapter type which has been tested with your system
on CentricStor, the firmware revisions, the drives and the BIOS settings (if any)
required. You should check compliance with these requirements and implement them
where necessary, before starting any integration work.
i
18
CAUTION:
Distribute the drives among the hosts so that no more than 2*4 drives (2 hosts
with 4 drives each) are operated simultaneously via one FC connection. If this
limit is exceeded, the performance of the fibre channel may fall dramatically.
The chapter “Useful commands and information” on page 265 shows how you can
find the current configuration data of the CentricStor on the graphical user interface.
13 October 2006
Edition 7
Introduction
Note
1.6 Note
The CentricStor front end, depending on the configuration setup, can emulate several robot
systems (connected via TCP/IP LAN) and tape drives (connected via ESCON or fibre
channel). This is independent of which real robot systems and which drives are actually
connected to CentricStor (back end). Details on the emulations which can be set, and the
real devices which can be connected can be found in the data sheet of your CentricStor.
The logical volumes of CentricStor can be easily distinguished from real volumes. They do
not belong to a logical library and are not therefore assigned to any drive type. Thus they
can be mounted in practically all drive emulations configured in CentricStor; the only limitations here are those deriving from the type of backup tool (e.g. NetWorker) used. The name
of a volume must, therefore, be unique for the whole CentricStor.
In many cases, CentricStor is integrated into an existing host system with backup and tape
management system. Tape libraries may already be present, which can be linked directly
with the host, or as a back end with
CentricStor.
The following rules apply here:
Real drives
cannot be used jointly.
Physical tape cartridge drives cannot be used jointly.
Robots
can be used jointly if the robot controller supports this
Edition 7
13 October 2006
19
by f.f. 1992
2 Summary of permitted configurations
2.1 CentricStor configurations with BS2000
Host connection
Device emulation
Library connection
ESCON host adapter, FC (SX and S Server)
FSC3590 Emulation / IBM3490
ROBAR/AMU or CSC/ACS
2.2 CentricStor configurations with MVS/ESA
Host connection
Device emulation
Library connection
Edition 7
ESCON host adapter
FSC3590 emulation / IBM3490
HACC
13 October 2006
21
CentricStor configurations in the SAN environment
Summary of permitted configurations
2.3 CentricStor configurations in the SAN environment
i
The current support matrix is available at the internet address:
http://www.centricstor.de or http://www.centricstor.com
ACS robot control
AIX
HP-UX
NetWorker
FSC
NetWorker
Legato
Netbackup
VERITAS
TSM
IBM
---
Mammoth2
3590E1A1
3590E1A
---
Mammoth2
gen. SCSI-2
gen. SCSI-2
2
Data
Protector
HP
BEX
Syncsort
Time
Navigator
ATEMPO
---
---
---
gen. SCSI-2
---
---
3590E1A1
Linux
3590E1A1
---
---
---
---
---
---
---
---
---
gen. SCSI-2 Mammoth2
gen. SCSI-2
gen. SCSI-2
gen. SCSI-2
gen. SCSI-2 ---
Mammoth2
3590E1A1
Mammoth2
gen. SCSI-2
---
---
---
gen. SCSI-2
---
gen. SCSI-2 --Mammoth2
Reliant
gen. SCSI-2 --Mammoth2
Solaris
WIN 2K
---
Mammoth2
Mammoth23
3590E1A
1
3590E1A
3590E1A
WIN 2K3 ---
---
3590E1A1
WIN NT
Mammoth2
Mammoth2 3 under test
Mammoth2
3590E1A
Mammoth2
3590E1A
---
3590E1A
22
---
1
1
Certified by Veritas: RedHat LINUX was used.
2
The product DistribuTape from Greham is required.
3
This has not been officially released by Veritas for Netbackup.
13 October 2006
Edition 7
CentricStor configurations in the SAN environment
DAS robot control
NetWorker FSC
NetWorker
Legato
Netbackup
VERITAS
TSM
IBM
Data Protector
HP
AIX
---
---
under test
---
3590E1A
HP-UX
---
Mammoth2
generic SCSI-2
---
generic SCSI-2
Mammoth2
Linux
generic SCSI-2
Mammoth2
---
---
---
---
Reliant
generic SCSI-2
Mammoth2
---
---
---
---
Solaris
generic SCSI-2
Mammoth2
Mammoth2
generic SCSI-2
---
---
WIN 2K
---
Mammoth2
---
---
generic SCSI-2
WIN NT
---
Mammoth2
---
---
generic SCSI-2
SCSI jukebox robot controller (VJUK)
Application
Platform in test
Jukebox
emulation
Tape device
emulation
BrightStor
ARCserve R11.1
SUSE Linux
ADIC Scalar 1000 Mammoth22
Maximum
volume No.
Restictions
At least 1182
Restore Multiplex
SLES8 SP3
Abortion
SLES9
Being examined
at CA
R11.11 SP1
Windows 2003
Legato Disk
Xtender UNIX
(DXUL) 2.63
Solaris 9
Mammoth22
3590E1A
FSC Networker 7.1 Solaris 9
EKS 1-3
ADIC Scalar 10K
3590E1A
At least
10000
---
FSC CS-TL
gen. SCSI-2
30000
---
Legato Networker
7.1.2
Windows 2000 SP4 FSC CS-TL
Mammoth2
20014
---
Veritas NetBackup
5.0 MP 1
Windows 2003
FSC CS-TL
Mammoth2
16000
---
HP
Data Protector 4.1
Windows 2000
FSC CS-TL
gen. SCSI-2
At least 1000
---
DataProtector 5.1
Windows 2003
1500
HP-UX
TSM
AIX 4.3.3
ADIC Scalar 10K
3590E1A
16000
---5
AIX 5.2
Edition 7
13 October 2006
23
Maximum block lengths
1
In the test on Windows, CentricStor also showed that it can function with the predecessor version (ARCserve
R11 with device patch 5 and patch QO53978) for Windows.
2
ARCServe on Windows works in fixed block length mode.
3
DiskXtender 2000 5.60.025 was tested on Windows 2003 with tape device type IBM 3590E1A but could not be
operated because of incompatibility of the end-of-tape identification/volume capacity.
4
If there are more than approx. 2001 slots for volums+drives Networker (jbconfig) aborts with error 0x29
unknown error. An increase in the slot limit is being investigated on the Networker side.
5
In the event of hardware scanning with cfgmgr and VJUK, AIX reports cfgmgr: 0514-621 WARNING: The
following device packages are required for device support but are not currently
installed. device.fcp.changer. No functional restriction was observed.
2.4 Maximum block lengths
Emulation
Maximum block length
FSC/generic SCSI-2
256 KB
EXABYTE/Mammoth2
240 KB
IBM/3590E1A
256 KB
The maximum block length is defined by the SCSI command read max blocksize.
2.5 Restrictions on the host system side
Windows:
Reliant:
Solaris:
HP-UX:
Can only see drives of the same type on CentricStor (page 132 and 134).
Support from V5.45B0030 or higher (page 89).
– An older LP8000 driver must be used.
– Connection of two FC controllers to the same WWPN is not permitted.
The system only supports 8 LUN for each partner WWPN.
2.6 Restrictions from the application program side
24
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.
13 October 2006
Edition 7
Restrictions for server farms using Open Systems
2.7 Restrictions for server farms using Open Systems
In principle all Open System hosts should be able work with a CentricStor via a fabric.
However, given the wide variety of FC controller hardware and the large number of
operating systems involved, problems can occur. This section provides a quick guide to the
problems which may arise and suggests some solutions.
The following problems are known:
Solaris scans all LUNs and as a consequence sporadically disturbs the data transfers
of other systems.
●
Troubleshooting: see section “Solaris systems in server farms” on page 103.
2.8 General information on the open world
As of CentricStor™ V3.0 fixed block length mode is supported in VTD emulation.
This applies for all 3 emulation types:
–
–
–
FSC generic
EXABYTE Mammoth2
IBM 3590E
As a result, BrightStor ARCserve backup can, for example, be supported on Windows. For
releases see the section “CentricStor configurations in the SAN environment” on page 22.
i
The variable or fixed block length mode is not configured on the CentricStor user
interface, but is defined internally by the application on the host.
Caution:
The pro-FC port resources currently suffice for 64 x 256-MB I/Os in parallel (256 MB is the
maximum variable block length). If fixed block length is used the size of maximum block
length may be increased, however only at the cost of the number of emulations, i.e. if 2-MB
fixed block I/Os are used the maximum number of emulations that can be used in parallel
is 8 ( i.e. 64 * 256/2048 ).
Edition 7
13 October 2006
25
3 CentricStor in BS2000/OSD
3.1 Miscellaneous
When CentricStor is operated in BS2000/OSD the large number of virtual drives means that
the number of mount messages can increase. To prevent message queues at the console
in unattended mode when NBLOGENF=Y is set to specify audit-standard console logging,
the system administrator must ensure that enough space is always available on the home
pubset for the CONSLOG files.
In addition, the time for buffering messages with BCAM should not be restricted with
/BCTIMES LETT=... .
Because there is no option for controlling the library in offline mode (without ROBAR/CSC),
no SLED is possible for CentricStor either on the ESCON or on the FC channel. Nor is initial
installation by FIRST or SIROS or physical backup with offline FDDRL supported.
3.1.1 Asynchronous tape processing with SYNC
In the case of asynchronous tape processing, e.g. by means of BTAM (cf. BS2000/OSD-BC
User Guide, DVS Assembler interface), the data is initially buffered in a device-specific
buffer and written to tape only when a specific buffer utilization level is reached. As a result,
in some circumstances not all data will really have been written to tape when hardware or
software faults occur. Only when the CLOSE command has been positively acknowledged
is it guaranteed that all data has been stored consistently on the volume.
As the buffer utilization level is device-specific, it cannot be assumed that the buffer content
is transferred to the tape during processing after a particular amount of data has been
exceeded. However, calling the SYNC command enables a consistent status to be ensured
section by section while asynchronous tape processing is in progress.
Basically the use of CentricStor in no way alters this fact. However, as the buffers are very
large here, it can occur that when an error occurs considerably more data has not yet been
written to tape than in real mode. Only afer CLOSE or SYNC has been acknowledged
positively does CentricStor naturally also ensure that a consistent saved status has been
achieved.
Edition 7
13 October 2006
27
Miscellaneous
CentricStor in BS2000/OSD
Fujitsu Siemens Computers products such as HSMS or ARCHIVE secure asynchronous
tape processing by calling the SYNC command. This is also required in customers’ own
applications and programs.
3.1.2 Configuration of logical drives in BS2000
The configuration of virtual CentricStor drives is practically identical to the configuration of
36-track drives in ABBA or STK robots.
For the instances given below of MAREN, NDM and ROBAR or CSC you must define an
identical, freely selectable storage location with a maximum of 5 characters (e.g. “CEST1”).
The steps necessary for the different instances are shown in the following example:
3.1.3 Activities in UGEN
i
Each ICP is an independent control unit in BS2000 on the ESCON channel and can
thus be configured using 2 or 4 paths in the direct connection. The address area
always begins with null.
1. Create an input file for UGEN (for details, see the system installation manual [7] of the
BS2000 version you are using):
Example:
Task:
Generation with two ICPs, each with 2 ESCON controllers, where all
virtual drives are connected via ESCON using two paths. These two
paths correspond to the two ESCON channels on each ICP.
i
28
BS2000 supports configurations using a maximum of 8
paths. However, only 4 ESCON channels can be connected
to one ICP.
13 October 2006
Edition 7
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
*
Edition 7
13 October 2006
29
Miscellaneous
*
*
Definition of 16 Logical Devices on ICP1
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
BI,C4,D,00,(82,I),(83,I),AT=CTL
BJ,C4,D,01,(82,I),(83,I),AT=CTL
BK,C4,D,02,(82,I),(83,I),AT=CTL
BL,C4,D,03,(82,I),(83,I),AT=CTL
BM,C4,D,04,(82,I),(83,I),AT=CTL
BN,C4,D,05,(82,I),(83,I),AT=CTL
BO,C4,D,06,(82,I),(83,I),AT=CTL
BP,C4,D,07,(82,I),(83,I),AT=CTL
BQ,C4,D,08,(82,I),(83,I),AT=CTL
BR,C4,D,09,(82,I),(83,I),AT=CTL
BS,C4,D,0A,(82,I),(83,I),AT=CTL
BV,C4,D,0B,(82,I),(83,I),AT=CTL
BW,C4,D,0C,(82,I),(83,I),AT=CTL
BX,C4,D,0D,(82,I),(83,I),AT=CTL
BY,C4,D,0E,(82,I),(83,I),AT=CTL
BZ,C4,D,0F,(82,I),(83,I),AT=CTL
2. Call UGEN:
UGEN INPUT=<INPUT-FILE>
3.1.4 Activities in MAREN
●
Version < V10
1. Use the following MARENADM instruction to define the storage location for the
CentricStor logical volumes:
//MODIFY-MAREN-PARAMETER LOCATION = *PAR(LOC-NAME = CEST1,
ACTION = *ADD)
2. Terminate MARENCP (MARENADM instruction):
//STOP-CONTROL-PROG MARENCP
3. Enter the following line in the MARENCP-ENTER file:
LOCATION CEST1,LOCAL,ROBAR-2
i
The new ROBAR-2 operand is required to indicate the operating mode for the
CentricStor system in MAREN.
4. Next, restart MARENCP.
30
13 October 2006
Edition 7
●
Miscellaneous
Version >= V10
Parameters which are local on a computer or global which were previously defined
when the MARENCP procedure was started have no effect in MAREN V10.0A and
higher. They are grouped together as computer-specific functions.
Only after the MARENCP task has been started for the first time during the BS2000 sysstem run can the MAREN subsystem become active. Before this point, tape processing
is rejected in the case of dialog tasks; in the case of batch tasks an operator input is
requested. Consequently, when a system is started up using suitable startup procedures, it must be ensured that the control program and the MAREN subsystem are already
loaded when a session is opened.
The storage location for the logical volumes of CentricStor is defined with the following
MARENADM statement:
//MODIFY-MAREN-PARAMETER LOCATION-ENTRIES = *PAR(LOC-NAME = CEST1,
ACTION = *ADD(OPERATING-MODE=*ROBAR2))
The original file $SYSMAREN.SYSENT.MAREN.100.SPD.MARENCP can be used for
startup.
When you connect CentricStor to an STK robot system and some of the STK drives
continue to be used as “native” TAPE-C4 devices, you should note the following:
The storage location of the volumes used as real “native” (not to be confused with the tape
volumes used by CentricStor for making physical backups) is not defined in MAREN as a
robot storage location (operating mode for the real STK robots in MAREN is “EXTERNAL”
and not “ROBAR-1”). Because MAREN tries to handle free tape requests using volumes
from a robot storage location, when CentricStor is implemented the virtual volumes will be
assigned as free tapes by default.
To prevent this, you will need to use a MARENLM reservation file or make use of MAREN
exits.
Here is an example:
The real volumes in the STK robot system are still to be used with the MAREN storage
location “STK1” for the free tape requests. Only jobs that have the job name “CESTTEST”
are to be assigned free tapes by MARENUCP from the virtual volumes entered in the
MAREN storage location “CEST1”.
MARENLM is used to take the following records from the MAREN reservation file (only
relevant fields are mentioned):
Edition 7
Location
Volume type
Job name
CEST1
TAPE-C4
CESTTEST
STK1
TAPE-C4
13 October 2006
31
Miscellaneous
In order to make the same selection using MAREN exits, the following commands are
required:
In MARENEX6 (Device Depot Exit)
MARENEX6
TAPEC4
REALVOL
RETURN
CSECT
...
CLC
BE
...
CLC
BNE
MVC
B
MVC
...
DS
XR
LM
BR
DEVTYPE,=CL8'TAPE-C4'
TAPEC4
CRJOB,=CL8'CESTTEST'
REALVOL
USERFELD+9(8),=CL8'CEST1'
RETURN
USERFELD+9(8),=CL8'STK1'
SELECT VIRTUAL VOLUME
SELECT REAL VOLUME
0H
15,15
14,12,12(13)
14
In MARENEX1 (Reserve Request Exit)
MARENEX1
CHECKDEV
TAPEC4
REALVOL
RETURN
CSECT
...
CLC
BE
...
CLC
BE
...
CLC
BNE
MVC
B
MVC
...
DS
XR
LM
BR
LAFUNKNM,=CL8'MARENUCP'
CHECKDEV
CALLER = MARENUCP?
DEVICE,=CL2'BC'
TAPEC4
DEVICE TYPE = TAPE-C4?
CRJOB,=CL8'CESTTEST'
REALVOL
HOMELOC,=CL8'CEST1'
RETURN
HOMELOC,=CL8'STK1'
SELECT VIRTUAL VOLUME
SELECT REAL VOLUME
0H
15,15
14,12,12(13)
14
If subsequently (after completion of the migration phase) free tape requests are to be
handled from CentricStor and the free TAPE-C4 cartridges as defined for the user ID
USEREXCH are to be removed from the pool of real STK volumes, then the entries described
above must be replaced in the MARENLM file by the following entry:
32
Location
Volume type
User ID
STK1
TAPE-C4
USEREXCH
13 October 2006
Edition 7
Miscellaneous
3.1.5 Further preparatory activities in MAREN
1. Including logical volumes in the MAREN catalog:
Case 1:
Logical volumes are added to the MAREN catalog using the following MARENADM
statement:
//ADD-FREE-VOLUMES VOL=..., FREE-LOCATION=CEST1, DEVICE-TYPE=TAPE-C4
Separate modification of TEMP-LOC is not necessary here. In the case of CentricStor
tapes, MAREN supplies all three locations (HOME-LOC, FREE-LOC and TEMP-LOC)
with the same value specified in FREE-LOCATION when //ADD-FREE-VOL is executed
(in contrast to TLS locations, for exmple).
Case 2:
If a logical volume is to be reserved for a particular user ID as soon as it is included in
the MAREN catalog, the following statement is used:
//ADD-RESERVED-VOLUME VOLUME=..., LOCATION=*PAR(HOME-LOC=CEST1,
FREE-LOC=CEST1, TEMP-LOC=CEST1), DEVICE-TYPE=TAPE-C4, USER-ID=...
2. Initializing the logical volumes:
The logical volumes can be initialized only when the corresponding preparations have
been completed in NDM and ROBAR (in the event of a host connection via ROBAR).
Before they are used for the first time all virtual volumes must be initialized. The
following MARENADM statement is used for this purpose:
//INIT-VOLUMES VOL=..., NEW-VOLUMES=*YES
Alternately the virtual volumes can be initialized with the BS2000 utility routine INIT. The
statement used for this is:
INIT TAPE-C4,VSN=...,NEW
The simplest way to include and initialize a number range of free volumes is to use the
following sequence of MARENADM statements:
//ADD-FREE-VOL VOL=*INT(FROM=<vsn1>,TO=<vsn2>),FREE-LOC=CEST1,
DEV-TYPE=TAPE-C4,INIT=*YES
//FREE-VOL VOL=*INT(FROM=<vsn1>,TO=<vsn2>),INIT-FILE=MARENADM.INITFILE(INIT- LOC=CEST1)
//INIT-VOL INIT-LOC=CEST1, ... ,NEW-VOL=*YES
The following message is output on the console for each released virtual volume:
MARM1S1 SET VIRTUAL VOLUME '<vsn>' OF SYSTEM '<location>' AS FAST MOUNT.
REPLY (0=OK; 1=NOK)
Edition 7
13 October 2006
33
Miscellaneous
This message is answered by ROBAR or CSC.
When the virtual volumes are released the data on them is deleted irrevocably. Only the
tape labels are retained.
The location name for the virtual volumes must be specified in the INIT-VOL statement.
The following message is output by MAREN during the initialization run for virtual
volumes:
MARM1IB MOUNT VOLUME ''<vsn>' ON DEVICE '<device>' FROM ROBOT
'<location>''?
Further special aspects for logical volumes in MAREN:
–
Exporting by means of //EXPORT-VOLUME not allowed.
–
No relocation possible using //RETURN-VOLUMES.
–
Modification of HOME-, FREE- or TEMP-LOCATION via //MOD-VOL-ATTR is
rejected.
–
Deletion not possible using //REMOVE-USER-VOLUMES.
Virtual volumes must be released for deletion using //FREE-VOLUMES and then be
deleted using //REM-FREE-VOLUMES. Only the MAREN catalog entry is removed.
The logical volumes must then be deleted in CentricStor using the GXCC function.
Release run
In the MAREN release run all the released logical volumes are set to "migrated" provided
they are still in the cache. In a subsequent MAREN initialization run, however, logical
volumes are not restored, but the stub of a volume which still exists in the cache is initialized. However, if these volumes are initialized via the BS2000 user program INIT or in the
context of a MAREN free tape request, a restore takes place, as a result of which these
tapes are mounted with a slight delay. You are therefore recommended to reinitialize
released volumes via MAREN.
If you want to prevent the logical volumes being set to "migrated" when the MAREN release
run takes place, the optional REP correction A0447567-012 must be used. This correction
suppresses the output of the message MARM1S1 'SET VIRTUAL VOLUME '(&00)' OF
SYSTEM '(&01)' AS FAST MOUNT. REPLY (0=OK; 1=NOK)' when the MAREN release run
takes place and thus also implicitly suppresses migration of these volumes.
You are advised to perform initialization of logical volumes using the MARENADM
statement INIT-VOL.
Reinitialization of virtual volumes using the MARENADM statement INIT-VOL VOL=<oldvsn>,NEW-VOL=<new- vsn> is not permitted. This corresponds to the procedure in the real
robot in which the barcode label does not change and the old real tape is therefore still
loaded into the drive.
34
13 October 2006
Edition 7
Miscellaneous
3.1.6 Activities in NDM
For a full description, see the BS2000 manual on system support [2].
The virtual tape devices must be assigned to a device depot in NDM, where the name of
this device depot must be identical to the MAREN storage location1:
/ADD-DEVICE-DEPOT UNIT=(mn1,mn2 ... mnx), LOCATION=CEST1
In BS2000/OSD V4.0A it is possible to assign more than 128 tape drives to a device depot
when the optional REP correction A0460384-330 is used.
To guarantee smooth and high-performance tape operation, the following values should be
set using the BS2000/OSD command /MODIFY-MOUNT-PARAMETER:
/MOD-MOUNT-PAR PREMOUNT-MSG=*IGNORE-USER-REQUEST
This parameter causes the output of the PREMOUNT messages (NKVT012 PREMOUNT
TAPE '(&00)' ON DEVICE '(&01)') to be suppressed. This message is of no significance in
robot operation in that it is only answered with "tsn." by ROBAR but no reactions occur. If
tapes frequently need to be mounted manually on real drives outside the robot, it may be
advisable to retain the default value PREMOUNT-MSG=*ACCORDING-TO-USERREQUEST.
!
CAUTION: The procedure here is the same as that for a real robot. Virtual tape
operation with CentricStor must be set with unconditional unloading of the virtual
volume. To do this, use the following command:
/MOD-MOUNT-PAR UNLOAD-REL-TAPE=
*REGARDLESS-OF-USER-REQUEST(TAPE-FAM=*MBK)
If long tapes are also to be dismounted after they have been used, the TAPE=*ALL
operand must be specified instead of TAPE=*MBK.
Restriction:
However, if operations take place on tape in a session with SPOOLOUT, this
parameter means that the SPOOLOUT tape must be dismounted and then
remounted after every SPOOLOUT of a file.
If several virtual drives are attached to a single BS2000, and these drives are located on
several CentricStor ICPs, then in order to ensure that the load is spread equally across the
various ICPs it is necessary to set the following mount parameter.
/MOD-MOUNT-PAR NEXT-TAPE-MOUNT = *LEAST-RECENTLY-USED-DEVICE
1
If the list of devices contains more than 10 entries, you must use several commands.
Edition 7
13 October 2006
35
Miscellaneous
3.1.7 Activities in ROBAR-CL and ROBAR-SV
These are necessary if an ADIC library is connected.
If the virtual connection to CentricStor is made by an emulation of an ADIC library (VAMU),
the following settings for CentricStor are necessary for the host connection via ROBAR to
the VAMU. ROBAR must be Version 3_0B or higher.
Robar-CL
The following settings are recommended for monitoring times (entered in the file
SYSPAR.ROBAR-CL.040.PROZPARAM):
VerbMonitoring=300
VerbMonitoringTime=180
From ROBAR 4.0 these are the standard specifications.
ROBAR-SV
If CentricStor is connected to BS2000/OSD via ROBAR, the following preliminary work is
necessary:
●
ROBAR-SV must be reinstalled for CentricStor operation. In this case the CentricStorspecific ROBAR Rule Files are read in.
●
If the ROBAR environment variable ROBAR-ARCHIV is set (see ROBAR menu item
DEFINES -> PROFILE), the VSNs of the logical volumes must be included in this.
Example
ROBAR_ARCHIV=LV0000-LV9999
export ROBAR_ARCHIV
36
●
The addressing mode robot_devid=EXPLICIT must be set for the virtual devices. This
ensures that the mnemonic form of addressing is used.
●
Operation of the software ROBAR-SV V3.0D in conjunction with CentricStor has only
been released for RISC systems. Operation of the software ROBAR-SV V4.0A has
been released without restriction for RISC and Primepower systems.
●
After every restart of a VLS component the associated ROBAR-SV must also be
restarted.
13 October 2006
Edition 7
Miscellaneous
ROBAR must be installed with the corresponding storage location name (here CEST1).
“CentricStor” is set as the AMU version at installation.
1. Make the following entries in the ROBAR configuration file:
a) Storage location name:
Location=CEST1
b) Number of robots:
robots_count=1
i
The virtual archive system is only supported as a single robot system.
c) VLP address and VAMU port:
robot_address1=TCP/IP(<VLP-adr>,<VAMU-port>)
i
The virtual archive system is accessed exclusively via a TCP/IP connection
(to the VAMU).
d) Virtual devices (are defined as TAPE-C4 devices):
gen_devices
mn1 robot=1 type=TAPE-C4
:
mnx robot=1 type=TAPE-C4
end_devices
The input and output areas of the robot system are irrelevant as far as CentricStor is
concerned.
2. The following parameters must be set so that the device mnemonic of the ROBAR-SV
configuration is used:
robot_devid=EXPLICIT
i
For further information on the configuration of CentricStor in BS2000 and in
ROBAR, see the manuals “MAREN” [3] Chapter 8.3 and “ROBAR” [5].
If a real archive system and a virtual archive system are to be operated together, a
separate ROBAR installation will be required for each of the two robot systems. The
storage location name for virtual volumes must be different from that used for real
volumes.
If several virtual archive systems are to be operated together, a separate ROBAR
installation will be required for each robot system. The volumes of each robot
system must be assigned their own separate storage location.
Edition 7
13 October 2006
37
Miscellaneous
3.1.8 Activities in BS2000-CSC
These are necessary if a StorageTek library is connected.
3.1.8.1
General information
Wherever possible, ensure that CSCUTGEN version 61.204 or higher is used. The
storage location is only freely selectable from this version onwards.
The virtual connection to CentricStor is implemented by emulating a StorageTek library
(VACS). The following preparations are therefore required in order to implement the host
connection to VACS via the StorageTek library interface:
●
After the CSC-Software has been installed (see CSC manual [9]) you will need to define
a virtual server with the following attributes in the CSC Gentab:
SERVER NAME=CEST1,PRONAM1=<vlp>,PRONAM2=,
VIRTUAL=Y,MOUNT=P,AUTOROUT=N,CAPSIZE=0, ,MGMTCLASS=BS2000
The server name (CEST1 in the example) can be freely selected, but may only be a
maximum of 5 Bytes in size and must be identical to the device depot name for the
virtual drives in BS2000 and to the storage location name for the virtual volumes in
MAREN.
Enter the VLP of the CentricStor configuration as the PRONAM.
The Parameter MOUNT=P[ROPOSE] must be set. CSC will then mount the virtual
volumes on the devices suggested by BS2000.
This means that dummy devices cannot be used as a virtual server because these are
not known to CentricStor and it is not possible to mount volumes on devices of this type.
This also means that CSC does not switch virtual drives back and forth between the
individual computers.
●
The virtual drives must be assigned to this server in the CSC Gentab.
Example:
DE HOSTNAME=HOST1,BS2DEV=B0,UNIXDEV=090,SERVER=CEST1,... DE
HOSTNAME=HOST1,BS2DEV=B1,UNIXDEV=091,SERVER=CEST1,...
etc.
Virtual drives are not switched by CSC and an entry in the PRIO parameter does not
therefore have any meaning.
The value to be specified for BS2DEV is the device mnemonic in BS2000.
The BS2000 devices are numbered sequentially in decimal notation in UNIXDEV, where
the last (lowest) position can take the values 0...9,A...J.
38
13 October 2006
Edition 7
Miscellaneous
Archive addresses, which cannot occur in physical archives are also accepted (and
correctly operated by CentricStor):
LSM-ID:
Panel:
Slot:
0-F
0-F
0-9,A,B,C,D,E,F,G,H,I,J
The UNIXDEV names in the CSC Gentab must match the VACS libdev name specified
in the GXCC configuration in the “Virtual Drives” menu.
Example:
A UNIXDEV = 010 in the CSC-GENTAB must be entered in GXCC with the VACS
LibDevName = 0-0-1-0, a UNIXDEV = 122 must be entered in GXCC with the VACS
LibDevName = 0-1-2-2. You must only use decimal numbers (009 is followed by 010
and not by 00A).
For a virtual drive, you can use the same co-ordinates as for a real robot drive. This type
of overlap does not cause problems because the server name (e.g. CEST1) is also
flagged in the drive definition in the CSC Gentab, next to the UNIXDEV, which in this
case is the same.
If you have 2 ICPs with 32 drives each, we recommend that you assign the UNIXDEVs
from 000 to 031 to the ICP0 devices (in the GXCC configuration menu for “Virtual
Drives”; this corresponds to the VACS LibDevNames from 0-0-0-0 to 0-0-3-1). The
devices on ICP1 can then be assigned the UNIXDEVs 032 through 063. Alternatively,
you could assign the devices on ICP1 the UNIXDEVs 100 through 131.
As a general rule, you can number the devices under UNIXDEV as you wish. There will
be no problems as long as the VACS LibDevName in GXCC is selected appropriately.
But this does, in some cases, make debugging harder and can lead to oversights when
modifying the configuration (e.g. when installing a new ICP).
●
For the real Volumes (used outside CentricStor as “native”), you must also define a
server (if the STK robot system was already being used as
native before the introduction of CenricStor, then this entry is contained in the CSC
Gentab):
SERVER NAME=SILO1,PRONAM1=<stksun>,PRONAM2=,VIRTUAL=N,MOUNT=A,DEFAULT=Y
The server name can be freely selected, but may only be a maximum of 5 Bytes, and
must be identical to the Device Depot Name for the real drives in BS2000 and the
storage location name for the real volumes in MAREN.
The name of the ACSLS computer must be entered as the PRONAM.
Edition 7
13 October 2006
39
Miscellaneous
The attributes VIRTUAL=N and MOUNT=A must be set. MOUNT=A[NY] means that CSC
can also mount drives other than those specified by BS2000 in the mount message. The
DEFAULT=Y parameter means that tape requests occurring as a result of MAREN
messages which do not specify a tape device (e.g. MARM1I2, MARUP45 etc.), are also
directed to this server.
i
3.1.8.2
The Gentab parameter SILONAME is only relevant if in the MARENUCP start
procedure, the parameter PROPOSE has not been set. If this MARENUCP
parameter is missing, then in the event of a free tape request, CSC will locate
and mount a real volume, using the MARENADM statement
//SECURE-FREE-VOLUMES.
●
Alongside the definitions of the individual servers, their respective drives and the
connected BS2000 host, the MAREN parameter is also to be set to Y in the CSC Gentab.
●
The created Gentab is implemented using the CSC Procedure PRC.CSCUTGEN. The
created output file must be specified in the CSC enter file ENT.CSCMAIN.
Activities in CentricStor: EMTAPE, VAMU/VACS
The logical devices are installed in the initial or update configuration using the GXCC
interface in the service mode.
CentricStor names of the LDs
The internal Centric Stor names of LDs are preassigned and are as follows for emulation
type OS-390:
L<Nnn>
where N = 0 .. 7 (as a rule) is the number of the ICP, on which the emulation is running, and
nn = 00 .. 1F (3F) is the number of the emulation with 32 or 64 LDs per ICP.
Device name and library device name
In the case of VLS-Type VAMU, the device name and library device name are always the
same, and must match the mnemonic of the LDs generated in UGEN.
Similarly with VLS-Type VACS, the device name must the mnemonic of the LDs generated
in UGEN.
The library device name must, however, match the virtual co-ordinates (e.g. 0-1-2-5) of the
StorageTek library, as they were generated in the GENTAB of BS2000-CSC (see section
“Activities in BS2000-CSC” on page 38).
40
13 October 2006
Edition 7
SX servers
3.1.9 Multiple CentricStor systems
●
When multiple CentricStor systems are used it must be ensured that the computer
names are unique in the LAN.
●
In order to avoid LAN performance/LAN load problems in the event of a kernel update
by means of "prepupdate" (cpio: broke pipe) when CentricStor is spread over several
locations, the service staff should perform the upgrade separately at each location.
●
After configuration changes in dynamic ESCON Director operation, e.g. port changes
because of modified cabling, the ICPs must be restarted.
3.1.10 DAS
The settings for the real drives’ cleaning mechanism, for robot sharing mode, and the
entries for the real drives’ configuration which are required to operate CentricStor are made
by the service provider.
3.2 SX servers
As of K818 EKS 9, CentricStor V2.1 K818 EKS 9 supports connection via fibre channel to
the business servers of the SX series SX100, SX130 and SX140 with OSD/XC Version 1.1
or newer (software package on the basis of BS2000/OSD-BC V5.0C).
3.2.1 Connection via FC switch
CentricStor on SX servers can be connected to the Emulex FC controller on an SX server
(LP9002 as of FW Rev. 3.90A7 or LP9802 as of FW Rev. 1.01A2 ) via an FC switch
(Brocade; Connectrix McData).
The following FC switches were used in the CentricStor test with SX servers:
–
–
–
Edition 7
Brocade Silkworm 3800 Version V3.0.2c
Brocade Silkworm 12000 FW V4.0.0b
Connectrix McData FW 05.02.0013; EC 1030218
13 October 2006
41
SX servers
3.2.2 Connection without an FC switch
An FC connection of the SX server is also possible directly (meaning without an FC switch)
to CentricStor. The "direct connection" has been tested with CentricStor V3.0 on an Intelligent Tape Controller (ITC). X2000 V3 and OSD/XC 2.0 (software package based on
OSD-BC V6.0) ran on the SX server - SX140 in the test.
3.2.3 Configuring the tape units in CentricStor
The virtual tape devices for the SX servers must be configured in CentricStor with
connection type FC-SCSI and IBM 3590E emulation.
In contrast to the original IBM drive which is operated as TAPE-C6 under BS2000, the
TAPE-C4 interface is used for the virtual 3590-E1A.
42
13 October 2006
Edition 7
SX servers
Example of CentricStor connected to SX140 (Leibniz):
vtls.conf in CentricStor:
V000:SPATZ-ISP0:8016:V000:FC-SCSI:VAMU:40:ON:1:15:0x00:IBM:IBM
03590E1A:0000000D0000:0
V001:SPATZ-ISP0:8017:V001:FC-SCSI:VAMU:41:ON:1:15:0x01:IBM:IBM
03590E1A:0000000D0001:0
...
Edition 7
13 October 2006
43
SX servers
3.2.4 Configuring the tape devices on the SX server
3.2.4.1
Introductory note on X2000
The BS2000/OSD operating system with the X2000 carrier system is installed on the
BS2000 partition. X2000 is based on Solaris and principally provides the runtime
environment for BS2000/OSD.
The available CPUs of a BS2000 partition are logically divided into CPUs for BS2000/OSD
and into I/O processors which X2000 makes available for BS2000/OSD. The available main
memory is also divided between BS2000/OSD and X2000.
The functions offered by X2000 include:
●
HAL (Hardware Abstraction Layer)
HAL maps the hardware-software interfaces of /390 mode onto equivalent interfaces of
SPARC64 mode.
●
/390 firmware
The /390 firmware component supplements SPARC64 mode and enables existing /390
code to run object-compatibly (im /390 mode; synonym: compatibility mode) on
SPARC64 hardware.
●
Implementation of I/Os and data communication
The fibre channel peripherals are operated under BS2000/OSD by emulating the devices
in X2000 as so-called bus peripherals.
In the event of connection via FC, the BS2000 host behaves, from the CentricStor
viewpoint, like an Open System installation. For BS2000/OSD and the emulation layers
below it, the drives generated in CentricStor appear to be native SCSI tape devices.
3.2.4.2
Configuration steps
The CentricStor devices are made known to the BS2000 operating system through configuration in X2000 as of Version 2.5A (based on Solaris 8). Generation using IOGEN in
BS2000/OSD is not required.
The following files must be adjusted on the SX server for device configuration:
●
/kernel/drv/lpfc.conf (WWPN binding)
●
/usr/kernel/drv/SMAWLsti.conf (extension Targets/LUNS)
A reconfiguration boot of Solaris must then be performed.
The CentricStor devices (BS2 tapes) can subsequently be set up via WSA
(WebSysAdmin).
44
13 October 2006
Edition 7
3.2.4.3
SX servers
Examples
Extract /kernel/drv/lpfc.conf
...
# 0x1
ELS events
# 0x2
Device Discovery events
# 0x4
Mailbox Command events
# 0x8
Miscellaneous events
# 0x10
Link Attention events
# 0x20
IP events
# 0x40
FCP events
# 0x80
Node table events
# 0x1000 FCP Check Condition events
log-verbose=0x10;
...
fcp-bind-WWPN= "10000000c937fa43:lpfc0t53"; # CentricStor Spatz ISP0 ctrl 15
...
# If automap is set, SCSI IDs for all FCP nodes without
# persistent bindings will be automatically generated.
# If new FCP devices are added to the network when the system is down,
# there is no guarantee that these SCSI IDs will remain the same
# when the system is booted again.
# If one of the above fcp binding methods is specified, then automap
# devices will use the same mapping method to preserve
# SCSI IDs between link down and link up.
# If no bindings are specified above, a value of 1 will force WWNN
# binding, 2 for WWPN binding, and 3 for DID binding.
# If automap is 0, only devices with persistent bindings will be
# recognized by the system.
automap=0;
...
# Some disk devices have a "select ID" or "select Target" capability.
# From a protocol standpoint "select ID" usually means select the
# Fibre channel "ALPA". In the FC-AL Profile there is an "informative
# annex" which contains a table that maps a "select ID" (a number
# between 0 and 7F) to an ALPA. If scan-down is set to a value of 0,
# the lpfc driver assigns target ids by scanning its ALPA map
# from low ALPA to high ALPA.
#
# Turning on the scan-down variable (on = 1,2, off = 0) will
# cause the lpfc driver to use an inverted ALPA map, effectively
# scanning ALPAs from high to low as specified in the FC-AL annex.
# A value of 2, will also cause target assignment in a private loop
# environment to be based on the ALPA (hard addressed).
#
# Note: This "select ID" functionality is a PRIVATE LOOP ONLY
# characteristic and will not work across a fabric.
Edition 7
13 October 2006
45
SX servers
scan-down=0;
...
# topology: link topology for initializing the Fibre Channel connection.
#
0 = attempt loop mode, if it fails attempt point-to-point mode
#
2 = attempt point-to-point mode only
#
4 = attempt loop mode only
#
6 = attempt point-to-point mode, if it fails attempt loop mode
# Set point-to-point mode if you want to run as an N_Port.
# Set loop mode if you want to run as an NL_Port.
topology=0;
...
Notes:
–
The WWPN associated with the drive can be determined via the graphical user
interface (GXCC) of the CentricStor system.
–
The expression “lpfc0t53” defines the Emulex Controller used (lpfc0..,lpfc1..,..) and the
freely selectable but unique target ID (....t0,....t1,..).
Extract /usr/kernel/drv/SMAWLsti.conf
...
###DRIVE CONFIG SECTION
tape-config-list=
"EXABYTE EXB-8505",
"EXB-8505",
"EXABYTE EXB-8900",
"EXB-8900",
"EXABYTE Mammoth2",
"EXABYTE MAMMOTH 2",
"FSC
",
"CentricStor",
"HP
C1537A",
"HP DDS3 4mm DAT",
"HP
C1557A",
"HP DDS3 4mm DATloader",
"HP
C5683A",
"HP DDS4 4mm DAT",
"HP
C5713A",
"HP DDS4 4mm DATloader",
"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",
46
13 October 2006
"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";
Edition 7
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,0x18219,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;
...
Edition 7
13 October 2006
47
SX servers
Device nodes
After a reconfiguration boot reboot -- -r the device nodes generated can be found under
/dev/rmt.
Example: SX140 Leibniz with 48 CentricStor devices (see example on page 43):
...
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 ->
48
13 October 2006
Edition 7
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)
Edition 7
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
13 October 2006
POOL/SIDE
49
SX servers
Notes:
–
–
Channels not equal to 0* are not virtual channels. These are assigned by the
hardware. They are thus not available for selection for CentricStor.
It makes sense (for example because of selective SM2) to select a free channel
from 00 through 0F for CentricStor.
In the example, 0B can be selected as HC for WSA.
By configuring the HC with WSA, the HC is automatically added as a channel in
BS2000/OSD by the system (see next section).
●
Entries in WSA
1. Call WSA:
# DISPLAY=nnn.nn.nn.nnn:0.0;export DISPLAY
# WSA
2. Click on the X2000 Bs2Devices icon
3. Click on the BS2 Tapes button
4. BS2 tape menu: Select Create (wait for output)
5. Enter HC, for example B (selected as channel in BS2000; see above)
6. Select /dev/rmt/?cn device node
7. MN is the device mn in BS2000/OSD associated with the device node or LUN (see
vtls.conf above)
8. Unit is automatically updated with the HC setting
9. Click on Ok and wait until channel and device are assigned on VM2000
50
13 October 2006
Edition 7
SX servers
For each device mn, 2 EMKTAPE_mn processes run in X2000, provided active=yes is
set for the device in WSA/BS2 Devices.
Example: SX130 Perseus
●
Timeout
In the case of large configurations or if there is a high system load on the SX server,
you are recommended to extend timeout monitoring when configuring CentricStor
devices (setting up BS2 tapes with WSA).
The timeout value can be increased in the file /etc/opt/SMAWwsaS/WSA:
# Default timeout for wdmexec commands (in seconds) ...
WSA_TIMEOUT : 255
The WSA_TIMEOUT variable defines the timeout in seconds. The value of WSA_TIMEOUT
can be changed from 45 to a maximum of 255.
Edition 7
13 October 2006
51
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
-
52
13 October 2006
SCD PORT SIDE DEV-ADDR PATH
0B00
AVAIL
0B0C
AVAIL
Edition 7
SX servers
Example: SX140 Leibniz with 48 CentricStor devices
In the example the 2 EMKTAPE processes are running for device 40:
leibniz # ps -ef | grep -i EMKTAPE_40
root
root
Edition 7
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
13 October 2006
53
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
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
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
%
54
POOL/SIDE
ATTACH /ON
13 October 2006
: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
Edition 7
SX servers
%
%
%
%
%
%
%
%
%
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
DVC
:67
:68
:69
:6A
:6B
:6C
:6D
:6E
:6F
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
,INCLUDED
3.2.5 Notes
●
Number of devices
An SX server recognizes all 64 devices in a CentricStor ICP. To save on Solaris
resources, it is however recommendable only to activate the CentricStor devices which
are actually needed in X2000 (WSA).
●
Dynamic addition of devices
The I/O handler permits a maximum of 4096 bus devices. CentricStor devices on the
FC also belong to the bus devices. The IOH enables dynamic addition of bus devices
(for example WSA -> BS2 -> Tapes), 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.
Edition 7
13 October 2006
55
SX servers
●
Compression
OSD/XC does not support the compression selection “HOST”.
The BS2000 devices (mn) are permanently linked to the Solaris device nodes via
X2000 with descriptor c (/dev/rmt/*cn) and cannot control compression by means
of volume type TAPE-C3 or TAPE-C4.
Control can only be implemented for a device via CentricStor with the configuration
setting “Compression” “ON” or “OFF”.
Thus X2000 ensures that data compression is always active in CentricStor for a tape
device on the SX server unless configuration is configured with “OFF” in CentricStor for
this tape device.
●
Device sharing, switch, path
SX servers do not support SCSI Reserve/Release.
Using the CentricStor devices via a joint WSA Management Server as “shared devices”,
i.e. exclusively on several SX servers alternately, has not been tested with
CentricStor.
The so-called “1:1” configuration has been quality-assured and generally released:
The FC port of a CentricStor ICP must be assigned to precisely one FC port of an
SX server and the FC port of an SX server to precisely one FC port of a CentricStor
ICP.
This excludes joint use of an ICP port and logical devices in CentricStor by multiple
SX servers, by SX and S servers (business servers of the S series, see section
“CentricStor on S servers” on page 58) or with Open Systems.
The devices are connected by a single path.
56
13 October 2006
Edition 7
SX servers
3.2.6 Restrictions
●
Use of CentricStor by the X2000 tool PSR (physical saving and restoring of disks or
individual slices) is not provided for.
●
Before maintenance work that results in the emulations (vtd) in CentricStor being terminated takes place, the tape emulations in X2000 should be disabled.
This is currently due to X2000 V2.5A in B70 status, Edition December 2003, because
of the problems A0506063, A0506172, A0507451/A0503900.
The tape emulations in X2000 are generally disabled/enabled via WSA. As only one
device can be disabled/enabled per call via WSA under X2000 V2.5, 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 command in Solaris:
/opt/SMAW/X2000/bin/acfconf stop -i MKTAPE
/opt/SMAW/X2000/bin/acfconf load -i MKTAPE
●
If hardware (CentricStor ISP; cable to the FC switch…) is not available, not only the
message EXC0858 IVRQ Drive offline may be issued in BS2000/OSD, but also several
others (EXC0858 CUTE - VOLUME FENCED -… EXC0858 NAIN -TIME OUT AFTER
40 SEC - …).
Patch A0506063 in X2000 V2.5A, which is not yet contained in the B70 status of the
Edition December 2003, ensures that the message is always “IVRQ - DRIVE OFFLINE”
(ERROR CODE 46 an BS2000/OSD).
Example:
<T %0PVF-000.182605 % EXC0858 DER INF. (TAPE): '0B
69
DBSIHCJS L50068 -DRIVE OFFLINE- 00--0E400020A002
46000DDD200000B316280000000000008800FF0000070E1D9000009200'
IVRQ
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
Edition 7
13 October 2006
57
CentricStor on S servers
3.3 CentricStor on S servers
CentricStor V2.1 and BS2000/OSD-BC Version 5.0C support not only the connection of
CentricStor via ESCON, but also connection via Fibre Channel - immer mit FC-Switch - on
the Business Servers of the S series (S120, S140, S145, S155, S170, S180, S190).
3.3.1 Firmware/software statuses
At least the following firmware/software statuses are required to operate S servers with
CentricStor:
●
CentricStor V2.1 SINIX-2000-Z K818.15
●
FC Switch
–
–
–
●
HCP-Level S server:
–
–
–
58
Brocade 2800 FW V2.60D
Brocade 12000 FW V4.0.0b
Connectrix McData FW 05.02.0013 ; EC 1030218
S120
at least E45L01G-01P+034 or current E45L01G-01R+008
S140/S170
at least E40L01G-02N+062 or current E40L01G-02Q+016
S145/S155/S180/S190
at least E60L02G-02D+047 or current E60L02G-02E+120
●
BS2000/OSD-BC as of V05.0C with the corrections package P1/05.
●
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.1
13 October 2006
Edition 7
3.3.2 Connection and configuration
The virtual devices for S servers must be configured as follows in CentricStor:
Connection type: FC-SCSI
Emulation:
IBM 3590E
For S servers, a maximum of 64 devices per ICP can be configured in CentricStor. Virtual
robot control of CentricStor can be implemented both via the VAMU interface (with ROBARCL/ROBAR-SV on the host side) and via the VACS interface (with CSC on the host side).
Connection of CentricStor to S servers is always implemented via an FC switch (Brocade
or Connectrix McData) to Fujitsu’s proprietary channel module FC-SCSI on the S server.
The so-called inverted Y configuration and the Y configuration have been released, and
also their combination as a so-called X configuration: Multiple ICP ports can be assigned
jointly to a port (FC channel) of an S server, and multiple S servers may make joint use of
the same ICP port. The individual LUNs/tape devices are assigned exclusively to 1 S server
with /attach-device mn in BS2000.
Example:
S190 /sh-dev-conf (50,70,10,4g),p
%
DVC
DEV-TYPE CONF-STATE PID CTL CHPID IOS
%
50
3590E
ATTACHED
-
8O
F0
-
-
-
-
F0000000 AVAIL
%
70
3590E
ATTACHED
-
8P
F0
-
-
-
-
F0000000 AVAIL
%
10
3590E
ATTACHED
-
88
F0
-
-
-
-
F0000000 AVAIL
%
4G
3590E
ATTACHED
-
89
F0
-
-
-
-
F0000000 AVAIL
S170 /sh-dev-conf (50,70,10,4g),p
%
DVC
DEV-TYPE CONF-STATE PID CTL CHPID IOS
%
50
3590E
DET(EX)
-
8O
98
-
-
-
-
98000000 AVAIL
%
70
3590E
DET(EX)
-
8P
98
-
-
-
-
98000000 AVAIL
%
10
3590E
DET(EX)
-
88
98
-
-
-
-
98000000 AVAIL
%
4G
3590E
DET(EX)
-
89
98
-
-
-
-
98000000 AVAIL
/attach-device 50
Edition 7
%
NKR0111 'DEVICE
=50' ASSIGNED ELSEWHERE
%
NKR0044 'DEVICE
=50': ATTACHMENT REJECTED
13 October 2006
59
The CentricStor devices must be generated by means of IOGEN in BS2000. The README
file for BS2000 should also be referred to (SYSRME.BS2CP.140.E):
**********************************************************************
*
CHN
FIBRECHANNEL / FICON
*
**********************************************************************
CHN 98,IBF,MODE=FCP
**********************************************************************
*
MBK
3590E/3591
*
**********************************************************************
CTL 8M,BLM,(98,0,10000000C932A5E4)
*ICP-WWPN
*
DVC L0,C4,D,0000,(8M),AT=CTL
BS2000/OSD-BC supports the compression selection “HOST”: CentricStor then writes in
uncompressed format for volume type TAPE-C3 and in compressed format for volume type
TAPE-C4.
3.3.3 Restrictions
The so-called "1:1" configuration has been released:
It is inadmissible for S servers and SX servers (business servers of the SX series SX100,
SX130, SX140, SX150) or S servers and Open System servers to make joint use of an ICP
port and thus of all logical devices in CentricStor on this ICP port. A risk is to be expected
because, for example, SX servers do not support the device reservation (reserve/release).
On the FC switch, no other zone with the ICP port - even if it is not used - may be entered
by another host which does not belong to the S series.
CentricStor tape devices and FC disks may not be configured in the same zone on the FC
switch and not on the same channel of the S server.
60
13 October 2006
Edition 7
4 CentricStor on z/OS
4.1 Introduction
A CentricStor virtual tape server behaves towards z/OS or OS/390 systems like a physical
IBM-3490E 36 track tape technology and is in a position to communicate with more than
one LPAR in parallel.
The virtual tape drives (devices) offered by CentricStor are configured in the HCD like real
connected devices. Dependencies of the operating system which is in use (SMPE status)
are not known.
The physical connection between CentricStor and the IBM host is implemented via ESCON
or the ESCON director channels and also via FICON or the FICON director channels. The
technical software connection takes place via a controller program for an ATL (Automatic
Tape Library) which runs as a subsystem in z/OS or OS/390. Controller programs from both
StorageTek (CSC) and ADIC (HACC) are available. You should choose the controller
program which suits the Virtual Library Service (library emulation) set in CentricStor.
However, the type of physical library attached to CentricStor (back end) is not visible to the
host.
The example installation described here refers to CentricStor with an emulated
StorageTek library.
CentricStor can make several different virtual drives available depending on configuration
level and ESCON ports contained. Those with the highest configuration level can be taken
from the
relevant CentricStor data sheet or the menu of the CentricStor configuration routine.
The information in this manual is expanded on by the installation manual for the controller
programs CSC (from StorageTek) and HACC (from ADIC); further information is also
provided in the CentricStor manuals.
Edition 7
13 October 2006
61
Subjects covered
CentricStor on z/OS
4.2 Subjects covered
The individual subject areas are:
–
Connecting virtual drives from the point of view of the host with different configuration
alternatives.
Logical path definition with or without ESCON director (switch) (page 63 and page 65).
Control Unit Definition (page 64)
I/O Device Definition
I/O Device Definition in CentricStor
I/O Device Definition in CSC/ASC/ACSLS
Start procedure for MVS/CSC
Library information for MVS/CSC
Special settings for DFHSM and DFRMM
Scratch alignment
–
–
–
–
–
–
–
–
–
4.3 Configuration of virtual drives in z/OS
From the point of view of the host, each virtual tape drive is connected like a real one.
i
The following MIH entry is recommended in the SYS1.PARMLIB (IECIOS00) for the
virtual drives:
Example
MIH DEV=(1E00-1E0F), TIME=10:00,HALT=06:00
/*T3490*/
With the highest configuration level, CentricStor supports 512 3490E tape drives (devices)
simultaneously. This configuration example describes a configuration level for 64 tape
drives.
An ICP (Integrated Channel Processor) controls the tape drives . To achieve an acceptable
throughput, 1 ICP is needed for every 32 devices.
For z/OS, an ICP is a 3490E Control Unit (CU). With IBM, a 3490E controller supports only
16 devices. Therefore, for 64 devices, you need 2 ICPs, which are defined in the HCD as
4 3490 CUs.
To make this possible, you must specify logical addresses (CUADD).
An ICP is connected to the host physically by a ESCON channel; every ICP is equipped with
at least two ESCON inputs. Both a direct connection and a configuration via an ESCON
director (switch) are possible.
62
13 October 2006
Edition 7
CentricStor on z/OS
Configuration of virtual drives in z/OS
In CentricStor, 16 consecutive listed devices are automatically and unalterably
assigned to a CU. The number of the CU is automatically set beginning with 0 either
in every ICP or covering all ICPs. Every CU can be addressed via all ESCON
adapters or an ICP, but not through the ESCON adapters of another ICP.
i
Sharing:
Device sharing is possible in IBM-SYSPLEX. Device sharing between BS2000 and
SYSPLEX is not recommended. ESCON adapters, CUs and ICPs can be used jointly
between IBM systems and BS2000.
4.3.1 Example configuration without ESCON-Director
ICP0
CU 0 1E00
UNIT 00..15
CUADD 0
ESCON
Host
Channel:
CU1 1E10
CUADD 1 UNIT 00..15
B0
B1
B2
B3
B4
B5
B6
B7
ICP1
CU0 1F00
CUADD 0 UNIT 00..15
CU0 1F10 UNIT 00..15
CUADD 1
Generating 2 ICPs with 32 virtual drives each:
The following definitions are necessary in the HCD:
●
Assignment:
–
–
●
Edition 7
CHPID to CU(ICP)
CU to I/O Devices (tape drive)
I/O device definition
13 October 2006
63
CentricStor on z/OS
Channel Path list
In this case, the number of channels on the host is the same as the number of paths.
CHPID
Type
Mode
B0
CNC
SHR
B1
CNC
SHR
B2
CNC
SHR
B3
CNC
SHR
Port
Con.
Mngd
Description
Control Unit Definition
Example 1:
HCD generation ICP0(CU) directly connected, via two CHPIDS(B0,B1).
CNTLUNIT CUNUMBR=1E00,PATH=(B0,B1),
UNITADD=((00,016)),CUADD=0,UNIT=3490
CNTLUNIT CUNUMBR=1E10,PATH=(B0,B1),
Example 2:
HCD generation ICP1 directly connected via two CHPIDS(B2,B3).
CNTLUNIT CUNUMBR=1F00,PATH=(B2,B3),
CNTLUNIT CUNUMBR=1F10,PATH=(B2,B3),
64
13 October 2006
Edition 7
CentricStor on z/OS
4.3.2 Example configuration with ESCON Director
Switch 1
Ports
Links
ICP0
9C
9D
9E
Host
9F
Channel:
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
CU 0 1E00 UNIT 00..15
CUADD 0
CU1 1E10 UNIT 00..15
CUADD 1
Switch 2
ICP1
4C
4D
4E
4F
CU 0 1F00 UNIT 00..15
CUADD 0
CU1 1F10 UNIT 00..15
CUADD 1
Generating 2 ICPs with 32 virtual drives each:
The following definitions are necessary in the HCD:
●
Assignment:
–
–
●
Edition 7
CHPID to CU(ICP)
CU to I/O Devices (tape drive)
I/O device definition
13 October 2006
65
CentricStor on z/OS
Channel Path List
CHPID
Type
Mode
Switch
B0
CNC
SHR
01
B1
CNC
SHR
02
B8
CNC
SHR
01
B9
CNC
SHR
02
Con.
Mngd
Description
Control Unit Definition
Example 1:
HCD generation ICP0(CU) via ESCON director connected via four CHPIDS.
CNTLUNIT CUNUMBR=1E00,PATH=(B0,B1,B8,B9),
UNITADD=((00,016)),LINK=(9C,4D,9C,4D),
CUADD=0,UNIT=3490
CNTLUNIT CUNUMBR=1E10,PATH=(B0,B1,B8,B9),
UNITADD=((00,016)),LINK=(9C,4D,9C,4D),
CUADD=1,UNIT=3490
Example 2:
HCD generation ICP1(CU) via ESCON director connected via four CHPIDS.
CNTLUNIT CUNUMBR=1F00,PATH=(B0,B1,B8,B9),
UNITADD=((00,016)),LINK=(9E,4F,9E,4F),
CUADD=0,UNIT=3490
CNTLUNIT CUNUMBR=1F10,PATH=(B0,B1,B8,B9),
UNITADD=((00,016)),LINK=(9E,4F,9E,4F),
CUADD=1,UNIT=3490
66
13 October 2006
Edition 7
CentricStor on z/OS
Representation of the example configuration in CentricStor
Drive Definition
Example: HCD generation of the I/O devices (tape drives) 32 per ICP are defined
IODEVICE ADDRESS=(1E00,016),UNITADD=00,CUNUMBR=(1E00),
STADET=Y,UNIT=3490
IODEVICE ADDRESS=(1E10,016),UNITADD=00,CUNUMBR=(1E10),
STADET=Y,UNIT=3490
IODEVICE ADDRESS=(1F00,016),UNITADD=00,CUNUMBR=(1F00),
STADET=Y,UNIT=3490
IODEVICE ADDRESS=(1F10,016),UNITADD=00,CUNUMBR=(1F10),
STADET=Y,UNIT=3490
This sets the HCD definitions for CentricStor. For further information, see “IBM Hardware
Configuration Definition User’s Guide”.
4.4 Representation of the example configuration in CentricStor
The following example shows how the I/O devices (tape drives) generated in z/OS are
represented in CentricStor.
ICP0
Type
Number of log. Drives
Device Name:
Drive L000 – L00F
Drive L010 – L01F
OS-390
32
(1E00 – 1E0F)
(1E10 – 1E1F)
DevName
VLS
LibDevName
L000
1E00
VACS
0-0-1-0
L001
1E01
VACS
0-0-1-1
L002
1E02
VACS
0-0-1-2
L003
1E03
VACS
0-0-1-3
L004
1E04
VACS
0-0-1-4
L005
1E05
VACS
0-0-1-5
L006
1E06
VACS
0-0-1-6
L007
1E07
VACS
0-0-1-7
...
Edition 7
13 October 2006
67
Representation of the example configuration in CentricStor
CentricStor on z/OS
ICP1
Type
Number of log. Drives
Device Name:
Drive L100 – L10F
Drive L110 – L11F
OS-390
32
(1F00 – 1F0F)
(1F10 – 1F1F)
DevName
VLS
LibDevName
L100
1F00
VACS
0-1-1-0
L101
1F01
VACS
0-1-1-1
L102
1F02
VACS
0-1-1-2
L103
1F03
VACS
0-1-1-3
L104
1F04
VACS
0-1-1-4
L105
1F05
VACS
0-1-1-5
L106
1F06
VACS
0-1-1-6
L107
1F07
VACS
0-1-1-7
...
68
13 October 2006
Edition 7
CentricStor on z/OS
Definitions of the I/O devices in CSC/ASC
4.5 Definitions of the I/O devices in CSC/ASC
Configuration of the ACSLS
*******************************************************
SERVER(ACSLS) * SERVER TYPE
*
* (SINGLE ACS LIBRARY AND NO NON-LIBRARY DEVICES)
*
LIBDEV(STL1)
* LIBRARY ESOTERIC
LIBUNIT(1E00, * LIBRARY DEVICES
1F00, * LIBRARY DEVICES
1E01, * LIBRARY DEVICES
* LIBRARY DEVICES
DEVICES
UNITMAP(1E00,00:00:01:0,* UNIT MAPPINGS
1E01,00:00:01:1,* UNIT MAPPINGS
1F07,00:01:01:0,* UNIT MAPPINGS
Edition 7
13 October 2006
69
MVS/CSC start procedure (Example)
CentricStor on z/OS
COMM(TCPIP)
* TCP/IP COMMUNICATIONS
TCPN(TCPIP)
* TCP/IP NAME
INTERNET(172.25.91.185)
* SERVER IP ADDRESS
*
ALOCTIME(120)
* TIME OUT SECONDS
ENQNAME(LCLQNAME)
* MVS/CSC ENQ QNAME
WTODESC(NO)
* MESSAGE HIGHLIGHTING
MSGCASE(MIXED)
* OUTPUT CASE
DELDISP(NOSCRTCH)
* DELETE DISPOSITION
DEFER(NO)
* DEFERRED MOUNTS
LOG(YES)
* LOGGING OPTION
UNITAFF(SEP)
* UNIT AFFINITY SEPARATION GDGALL(NOSEP)
* GDG ALL SEPARATION
COMPRFX('*')
* COMMAND PREFIX
4.6 MVS/CSC start procedure (Example)
The name of the CSC startup procedure must be the same as the subsystem name in the
member IEFSSNyy of SYS1.PARMLIB.
//CSC0 PROC PROG=SCSBINIT,PRM=' '
//*
//CSC0 EXEC PGM=&PROG,TIME=1440,DPRTY=(7,5),
// REGION=3000K,PARM='&PRM'
//* ACCT=YOUR-ACCT-INFO,REGION=3000K,PARM='&PRM'
//*OUT OUTPUT DEFAULT=YES,DEST=YOUR-DEST-NODE
//*
//* STEPLIB MUST POINT TO MVS/CSC EXECUTABLE MODULES LIBRARIES.
//*
//STEPLIB DD DISP=SHR,DSN=your.SCS4000.SCSLINK
// DD DISP=SHR,DSN=your.SSCR65C.SACLINK
// DD DISP=SHR,DSN=your.SSCR65B.CSLLINK
//*TREQDEF('your.SCS4000.PARMLIB(TREQ)')
//* DD DISP=SHR,DSN=YOUR.TCPLINK --- NICHT FUER IBM TCP
//* TCPIP DATA
//*
//SYSTCPD DD DISP=SHR,DSN=TCPIP.TCPPARMS(TCPDATA)
//*
//* SCSPARM MUST POINT TO MVS/CSC STARTUP PARAMETERS.
//*
//SCSPARM DD DISP=SHR,DSN=your.SCS4000.PARMLIB(PARM00)
//*
//* SCSLOG IS OPTIONAL EVENT LOG AND MUST POINT TO A DSORG=PS
//* RECFM=VB LRECL=3076 BLKSIZE=10000 DATA SET OF SUFFICIENT SIZE
70
13 October 2006
Edition 7
CentricStor on z/OS
System task CSC/ASC Library entries
//* TO HOLD EVENT RECORDS FOR TIME AND ACTIVITY.
//*
//SCSLOG DD DUMMY
//*SCSLOG DD DISP=SHR,DSN=YOUR.LOG.FILE
//*
//* SCSTRACE IS OPTIONAL TRACE FILE AND MUST POINT TO A DSORG=PS
//* RECFM=VB LRECL=1004 BLKSIZE=10000 DATA SET OF SUFFICIENT SIZE
//* TO HOLD TRACE RECORDS FOR TIME AND ACTIVITY.
//*SCSTRACE DD DISP=SHR,DSN=YOUR.TRACE.FILE
//SYSABEND DD SYSOUT=*
//*
i
The started task CSC or the user ID, with which the CSC is initiated, must have an
OMVS segment (RACF).
For further details on the start procedure, see “StorageTek (CSC) Installation
Guide”.
4.7 System task CSC/ASC Library entries
PROGxx
APF ADD
DSNAME(your.SCS4000.SCSLINK) VOLUME(volser)
APF ADD
DSNAME(your.SSCR65C.SACLINK) VOLUME(volser)
APF ADD
DSNAME(your.SSCR65B.CSLLINK) VOLUME(volser)
IEFSSNxx
SUBSYS SUBNAME(CSC0) INITRTN(SCSBPREI)
SCHEDxx
PPT PGMNAME(SCSBINIT) PRIV SYST KEY(3)
Edition 7
13 October 2006
71
DFHSM
CentricStor on z/OS
4.8 DFHSM
So that the full capacity of the virtual volumes can be utilized when virtual tape drives are
used in DFHSM, the following parameters must be set in the member ARCCMDxx:
SETSYS USERUNITTABLE (STL1:STL1)
SETSYS TAPEUTULIZATION (UNITTYPE (STL1))
PERCENTFULL(9999)
The SETSYS entry TAPEUTULIZATION must be given directly after USERUNITTABLE. If
it is not entered it will have not effect because of default rules.
4.9 DFRMM
CentricStor has no direct interface with DFRMM.
For this reason the virtual volumes entered via the GXCC interface must be entered as real
volumes in DFRMM and initialized with EDGINERS.
A scratch alignment must also be run in order to synchronize the volumes.
4.10 Scratch alignment between CentricStor, MVS/CSC and
DFRMM
A scratch alignment is a procedure which ensures that the volumes in CentricStor, in
MVS/CSC and in DFRMM have the same status. StorageTek makes various procedures
available for this which must be individually adapted (see “CSC System Programmers
Guide”).
i
During a scratch alignment tape processing usually continues. This means that the
volumes written in RMM in this time are assigned the status “User” but are still
recognized as SCRATCH volumes in CentricStor.
1. If such a volume is requested as SCRATCH, RMM will reject it and request a
new SCRATCH volume.
2. If a SPECIFICmount is requested for such a volume, a SWAP is forced and a
remount initiated. The volume status is aligned implicitly between RMM and CS,
i.e. the volume has the USER status in RMM and CentricStor.
72
13 October 2006
Edition 7
CentricStor on z/OS
Configuration of the system task HACC in CentricStor operation via HACC
4.11 Configuration of the system task HACC in CentricStor
operation via HACC
For the configuration of the system task HACC, the LPORT address must be clear.
Example:
An Address space HACC with two virtual libraries.
NAME OF CENTRICSTOR ADIC
*
IP=172.025.396.18
5,
IP-ADDRESS OF PRIMARY AMU
*
LPORT=9080,
INTERNAL PORT NUMBER FOR HA
*
PORT=9055,
PORT NUMBER OF CORRESPONDING
VAMU*
*
TYPE=PRI
INDICATE: THIS IS PRIMARY AMU
*
HACNET HID=V1,
*-------------------------------------------------------------*
NAME OF CENTRICSTOR AZUR
*
IP=172.025.549.10
6,
IP-ADDRESS OF PRIMARY AMU
*
LPORT=9090,
INTERNAL PORT NUMBER FOR HA
*
PORT=9055,
PORT NUMBER OF CORRESPONDING
VAMU
*
TYPE=PRI
INDICATE: THIS IS PRIMARY PATH
HACNET HID=V2,
Edition 7
13 October 2006
73
Mount balancing
CentricStor on z/OS
4.12 Mount balancing
4.12.1 General
To distribute the mount requests evenly over the ICPs present in CentricStor, rules must be
observed in the device configuration of the host system/CSC which are illustrated in this
description. The description applies only for the use of CSC on IBM hosts.
4.12.2 Prerequisites
The prerequisites for the use of mount balancing are described below.
●
CentricStor
The tests took place in the development department on the basis of CS V2.1 / K817.
However, no dependencies on the CS version are known.
●
OS390/zOS
A prerequisite in the OS390/zOS environment is at least Version 2.10 / zOS 1.2.
●
Tape management software
A prerequisite is at least the STK software CSC 5.1.
4.12.3 Configuration description
4.12.3.1
General
To achieve even distribution of the mount requests over the CS ISPs, settings must be made
in the OS390/zOS-CSC-5.1 configuration. These settings are a logical map of the
connection to a library (ASM).
In each LSM (up to 16), up to 64 logical devices are defined. These devices correspond to
the logical drives in the ICP.
74
13 October 2006
Edition 7
CentricStor on z/OS
4.12.3.2
Mount balancing
OS390/zOS-CSC-5.1 configuration
The following example shows 3 ICPs each with 32 logical devices. The CSC-5.1 device
definitions required for this in the OS390/zOS system are as follows:
************************************************************************
SERVER(ACSLS)
* SERVER TYPE
*
* (SINGLE CENTRICSTOR LIBRARY WITH NO NON-LIBRARY DEVICES)
*
LIBDEV(,STL1)
* LIBRARY ESOTERIC
*
NOTE CENTRICSTOR IS SECOND LIBRARY
LIBUNIT(1D00,1D01,1D02,1D03,1D04,1D05,1D06,1D07, - * ICP 0
1D08,1D09,1D0A,1D0B,1D0C,1D0D,1D0E,1D0F, 1D10,1D11,1D12,1D13,1D14,1D15,1D16,1D17, 1D18,1D19,1D1A,1D1B,1D1C,1D1D,1D1E,1D1F)
1E00,1E01,1E02,1E03,1E04,1E05,1E06,1E07, - * ICP 1
1E08,1E09,1E0A,1E0B,1E0C,1E0D,1E0E,1E0F, 1E10,1E11,1E12,1E13,1E14,1E15,1E16,1E17, 1E18,1E19,1E1A,1E1B,1E1C,1E1D,1E1E,1E1F, 1F00,1F01,1F02,1F03,1F04,1F05,1F06,1F07, - * ICP 2
1F08,1F09,1F0A,1F0B,1F0C,1F0D,1F0E,1F0F, 1F10,1F11,1F12,1F13,1F14,1F15,1F16,1F17, 1F18,1F19,1F1A,1F1B,1F1C,1F1D,1F1E,1F1F)
*******************************************************
*
*
THE SMC WILL TRY TO USE DEVICES FIRST THAT ARE
*
IN THE SAME LSM AS TAPE.
*
CENTRICSTOR REPORTS ALL TAPE AS HAVING LOCATION 1,1,1,1,1
*
*
THIS MEANS IT WILL USE DRIVES FIRST IN LSM 1 THEN 2,3,....
*
*
WE NOW SPREAD THE DRIVES FOR THE ICP'S OVER 16 LSM
*
*******************************************************
*
ICP0 CU 0 DRIVE 0 PANEL 2 LSM 1 - 16
UNITMAP(1D00,01:01:02:0,* ICP 0 CU 0
1D01,01:02:02:0,* DRIVE 0
1D02,01:03:02:0,* PANEL 2
1D03,01:04:02:0,* LSM 1 - 16
.
.
.
Edition 7
13 October 2006
75
Mount balancing
CentricStor on z/OS
1D0E,01:0F:02:0,1D0F,01:10:02:0,1E00,01:01:02:1,1E01,01:02:02:1,1E02,01:03:02:1,1E03,01:04:02:1,.
.
.
1E0E,01:0F:02:1,1E0F,01:10:02:1,1F00,01:01:02:2,1F01,01:02:02:2,1F02,01:03:02:2,1F03,01:04:02:2,.
.
.
1F0E,01:0F:02:2,1F0F,01:10:02:2,1D10,01:01:02:3,1D11,01:02:02:3,1D12,01:03:02:3,1D13,01:04:02:3,.
.
.
1D1E,01:0F:02:3,1D1F,01:10:02:3,1E10,01:01:02:4,1E11,01:02:02:4,1E12,01:03:02:4,1E13,01:04:02:4,.
.
.
1E1E,01:0F:02:4,1E1F,01:10:02:4,1F10,01:01:02:5,1F11,01:02:02:5,1F12,01:03:02:5,1F13,01:04:02:5,.
.
.
1F1E,01:0F:02:5,1F1F,01:10:02:5)
*
*
*
*
*
*
ICP 1
DRIVE
PANEL
LSM 1
CU 0
1
2
- 16
*
*
*
*
*
*
ICP 2
DRIVE
PANEL
LSM 1
CU 0
2
2
- 16
*
*
*
*
*
*
ICP 0
DRIVE
PANEL
LSM 1
CU 1
3
2
- 16
*
*
*
*
*
*
ICP 1
DRIVE
PANEL
LSM 1
CU 1
4
2
- 16
*
*
*
*
*
*
ICP 1
DRIVE
PANEL
LSM 1
CU 1
5
2
- 16
*
*
*
76
13 October 2006
Edition 7
CentricStor on z/OS
Mount balancing
COMM(TCPIP)
TCPN(TCPIP)
* INTERNET ADDRESS OF VACS
INTERNET(172.25.248.146)
*
ALOCTIME(180)
ENQNAME(LCLQNAME)
WTODESC(NO)
MSGCASE(MIXED)
DELDISP(NOSCRTCH)
TRACE(NO)
TRACD(FILE)
DEFER(NO)
LOG(RESET)
UNITAFF(NOSEP)
GDGALL(SEP)
COMPRFX('*')
TREQDEF('NCS510.PARMLIB(TREQ)')
LKEYDEF('NCS510.PARMLIB(CSC)')
4.12.3.3
* TCP/IP COMMUNICATIONS
* TCP/IP NAME
* SERVER IP ADDRESS
*
*
*
*
*
TIME OUT SECONDS
MVS/CSC ENQ QNAME
MESSAGE HIGHLIGHTING
OUTPUT CASE
DELETE DISPOSITION
*
*
*
*
*
*
*
DEFERRED MOUNTS
LOGGING OPTION
UNIT AFFINITY SEPARATION
GDG ALL SEPARATION
COMMAND PREFIX
TAPE REQUEST DEFNS
LICENSE KEY LOCATION */
Description of the CSC device statement
The device statement in the OS390/zOS-CSC-5.1 system has the following format:
<devaddr>,<ACS-Server-No.>:<LSM-No.>:<Panel>:<Device-Location>
Where:
<devaddr>
Device address via which the corresponding regulation is
addressed in the assigned ICP.
<ACS-Server-No.>
ACS server number (must always be set to 01).
<LSM-No.>
LSM number
Up to 16 numbers (01 - 10) are possible.
<Panel>
Panel number
The panel number must be set to 2 or 3. Panel number 3 is
only required if you configure more than 16 devices per
LSM. This is only the case if more than 4 ICPs with 64
devices are present.
<Device-Location>
Device location in the panel. 20 devices (0 - 19) are
possible.
Example
1D00,01:01:02:0
Edition 7
13 October 2006
77
Mount balancing
4.12.3.4
CentricStor on z/OS
Schematic diagram of the configuration
CentricStor
ACS
1D00
LSM1
1D01
ICP0
1D02
1D03
LSM2
1E00
ICP1
1E01
1E02
LSM3
1E03
1F00
ICP2
1F01
LSM4
1F02
1F03
OS390/zOS – Host
CSC 5.1
78
13 October 2006
Edition 7
5 CentricStor on UNIX-type systems
5.1 Linux
5.1.1 EMULEX LP8000 Controller
!
5.1.1.1
Edition 7
The LP8000 controller has still not been released on Linux. The settings described
below are advance information.
Linux RedHat (not officially released)
●
EMULEX driver for Linux version 4.02f.
●
The driver module provided by EMULEX only runs under RedHat 6.2.
●
The open source cannot be translated.
●
The Topology setting must be changed in the file lpfc.conf.c for a switch connection
(parameter == 2).
●
The shell procedure MAKEDEV must be adapted accordingly.
●
/etc/conf.lilo must be extended by the following entry, in order to see more than
8 LUNs:
append="max_scsi_luns=128" (also see description by EMULEX).
●
Activation of the “probmod lpfcdd” or “insmod lpfcdd” drivers.
●
Error messages etc. are in the file: /var/log/messages
●
Problems and troubleshooting:
Kernel Panic:
●
Set the interrupt of LP8000 to 11.
If further problems arise: remove LP8000 and reboot. Load Lpfcdd. Then reinstall the
board.
13 October 2006
79
Linux
5.1.1.2
CentricStor on UNIX-type systems
SuSE Linux
EMULEX Driver for Linux version 4.02f
●
As finished object modules are only delivered for RedHat 6.2, the open source must be
translated. For this, the kernel sources, which are not installed as standard, must be
present on the machine.
●
The shell script issmp must be adapted as appropriate for a multi-processor system.
Using grab, search for SMP instead of smp. In a multi-processor system, the version with
the extension -SMT must be entered in the file /usr/include/linux/version.h .
●
The “Topology” setting must be changed in the file lpfc.conf.c for a switch
connection (parameter == 2).
●
/etc/lilo.conf need not be adapted.
●
Activation of the driver with modprobe lpfcdd or insmod lpfcdd.
Overview of driver versions
Controller
LINUX version Driver
Version
Source
LP9002
SuSe 8.1
lpfcdd
4.20p
FSC
LP9802
SuSe 8.1
lpfcdd
4.20p
FSC
5.1.2 Qlogic QLA2200F Controller
5.1.2.1
5.1.2.2
80
Linux RedHat 6.2
●
Linux driver for RedHat 6.2. Version: V2.23/1.19.10 from Qlogic
●
BIOS version of card: 1.61
SuSE Linux 7.1 ·
●
Linux driver for RedHat 6.2. Version: V2.23/1.18.10 from Qlogic
●
BIOS version of card: 1.61
●
Linux kernel version: 2.2.18
●
The open source code must be translated. For this the kernel sources must be read in.
●
Then the kernel must be recreated, as the kernel delivered by SuSE does not exactly
fit the sources which have been loaded (see Building the Kernel).
13 October 2006
Edition 7
5.1.2.3
Linux
SuSE Linux 8.0 Professional
●
With the driver “qla2x00”, delivered with kernel 2.4.18, version 5,.38b16 is used.
Note:
The message in /var/log/boot.msg gives an incorrect driver version:
<6>scsi0 : QLogic QLA2200 PCI to Fibre Channel Host Adapter: bus 0 device 13 irq 9
<4>
Firmware version: 2.01.37, Driver version 4.46.5
●
BIOS version of the card: 1.54 or 1.61 or 1.72 or 1.77 (recommended). Fujitsu-Siemens
has extensively tested the named versions.
●
Linux kernel version: 2.4.18.
The Open Source code must be translated. For this the kernel sources must be read in.
The variable OSVER must have exactly the same name in the make file as in the
directory where the Linux source is located (e.g. linux).
●
The driver contained in the SuSE distribution has a error which prevents the tape from
being ejected from the drive. The LUN_NOT_READY from the drive is wrongly seen as
an error, and because of this the command is not executed. You can get round this
function call by commenting out qla2x00_check_sense in line 9964.
●
As the emulations from CentricStor register themselves as SCSI-II drives, only the first
8 LUNs are scanned in the kernel 4/2/18 (except for the IBM-3590 emulation). Further
drives must be added with the following command after every reboot:
echo "scsi add-single-device a b c d" > /proc/scsi/scsi
Where:
a
b
c
d
= Host adapter ID
= SCSI channel on the host adapter (for multi-channel HA)
= SCSI ID
= SCSI LUN
The following is a small Perl script which adds all LUNs from 8 to 32.
------------------------------------------------------------------------
#!/usr/bin/perl
$ILoop = 0;
for ( $ILoop = 8; $ILoop < 32; $ILoop++) {
system("echo \"scsi add-single-device 1 0 0 $ILoop\" >
/proc/scsi/scsi");
}
------------------------------------------------------------------------
From kernel version 2.4.19, the CentricStor emulation is recognized automatically with
32 LUNs.
Edition 7
13 October 2006
81
Linux
Notes on Linux on Primergy B210
The ServerWorks chip set used with B210 still does not appear to run sufficiently stably with
the standard kernel. During test applications running for several hours, complete crashes
continued to occur frequently. The system only ran stably when a single processor kernel
with the following kernel boot parameter was created:
noapic
nmi_watchdog=0
There has been lot of information about this in the newsgroups, it is most likely that this error
will be solved in the next kernel version.
Overview of driver versions
Controller
LINUX
version
QLA2200
1
82
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.
13 October 2006
Edition 7
Linux
Notes on missing device nodes
If a tape emulation (e.g. V104) is not available on the ICP, then at boot the Linux host
automatically only sees the device area, i.e.in this example it only sees from V100 to V103.
This situation can arise if during the Linux boot, vtd emulations were stopped directly in an
ICP.
If vtd V104 is stopped on the ICP, you will find the following messages on a Linux host in
/var/log/messages:
...
Sep 30 14:09:19 mhpabhsc kernel: st: Version 20020205, bufsize 32768,
wrt 30720, max init. bufs 4, s/g segs 16
Sep 30 14:09:19 mhpabhsc kernel: Attached scsi tape st0 at scsi0, channel
Sep 30 14:09:21 mhpabhsc kernel: isapnp: Scanning for PnP cards
...
0,
0,
0,
0,
id
id
id
id
0,
0,
0,
0,
lun
lun
lun
lun
0
1
2
3
The higher LUNs can be added with add-single-device, if necessary, by using the modified
Pearl script from page 81.
#!/usr/bin/perl
# LUNs einrichten: siehe /proc/scsi/scsi
for ( $iLoop = 4; $iLoop < 8; $iLoop++) {
system("echo \"scsi add-single-device 0 0 0 $iLoop\" >
/proc/scsi/scsi");
}
This makes 3 further LUNs (device nodes) visible to the host.
/var/log/messages:
...
Sep 30 14:27:13 mhpabhsc kernel: Attached scsi tape st4 at scsi0, channel 0, id 0, lun 5
...
!
Edition 7
CAUTION: This action may cause the previous assignment of
Linux - device nodes to CentricStor - LUN / or to CentricStor - LibDevName
(i.e. VDAS name/VACS co-ordinates).
13 October 2006
83
Linux
Data compression
On the host side, the compression in CentricStor is activated for a (logical) device with the
mt command. For this to occur, the virtual drive must be configured with
Compression = Host.
Example:
# mt -f /dev/nst0 datcompression 2
compression ***
Compression on.
*** Activate
compression ***
Compression off.
*** Deactivate
***
Compression off.
*** Status display
The setting is only effective if the (logical) volume is unloaded before the “mt”. With an “mt”
on a loaded volume, the change in compression modes is not effective. This behavior
depends on CentricStor.
–
–
–
–
–
For the CentricStor emulation FSC/CentricStor, compression at the host is turned off by
default.
For the CentricStor emulation EXABYTE/Mammoth2, compression at the host is
switched on as default.
The last activation or deactivation on the Linux host is still valid after the Linux reboot.
After the restart of the tape emulation (vtd), the default (see above) is again valid.
The compression at the host of the device node can also be configured in Linux with the
program stinit. In this case multiple or all drives can be configured at once without a tape
being mounted. A definition file must be created. This file has the following format:
manufacturer=FSC model = "CentricStor" {
mode1 blocksize=0 compression=0 # 0=not 1=compressed
}
The function call is then, for example:
stinit -f <DefFileName> /dev/st13 /dev/st14 /dev/st15 ...
Generally:
stinit [-f conf-file] [-h] [-p] [-r] [-v] [devices...]
The other Linux tape modes (/dev/st*, /dev/st*l, /dev/st*m, /dev/st*a) can
also be configured in this way.
84
13 October 2006
Edition 7
Linux
5.1.3 ST Linux SCSI tape driver
The ST driver with the old Linux kernel (< 2.6) only supports a maximum of 32 drives as
standard. As of Linux kernel 2.6 more than 64 ST devices can be generated. Information
on generating drive nodes:
Rewind drive nodes:
Drive
Major
Minor
0
9
0
1
9
1
2
9
2
NoRewind drive nodes:
Drive
Major
Minor
0
9
128
1
9
129
2
9
130
There are various other drive nodes and these all use a different ModePage. However,
these are not relevant to for the CentricStor connection.
The nodes are created with the command: mknod st0 c 9 0.
There are two methods for creating the device nodes:
1. Adapting the MAKEDEV file in the /dev directory
st[0-9]|st[123][0-9])
major=`Major st 9`
unit=`suffix $arg st`
makedev st${unit} c $major $unit $tape
makedev nst${unit} c $major `math 128 + $unit` $tape
makedev st${unit}l c $major `math 32 + $unit` $tape
makedev nst${unit}l c $major `math 160 + $unit` $tape
makedev st${unit}m c $major `math 64 + $unit` $tape
makedev nst${unit}m c $major `math 192 + $unit` $tape
makedev st${unit}a c $major `math 96 + $unit` $tape
makedev nst${unit}a c $major `math 224 + $unit` $tape
;;
Creating device nodes with “cd /dev; ./dev/MAKEDEV st10”.
Edition 7
13 October 2006
85
Linux
2. A small Perl script:
#!/usr/bin/perl
$iLoop = 0;
$NonRewindDevice = 0;
system("mknod st$iLoop c 9 $iLoop");
$NonRewindDevice = 128 + $iLoop;
system("mknod nst$iLoop c 9 $NonRewindDevice");
}
!
CAUTION!
When using configuration or application programs such as Spheras or GamSam, it
may be necessary to generate additional SG device nodes. Consequently a brief
example script for the nodes from 16 through 64 is provided below:
#!/usr/bin/perl
$iLoop = 0;
system("mknod /dev/sg$iLoop c 21 $iLoop");
}
5.1.4 Uniquely assigned device node to LUN in Linux
Scsidev is a tool used to obtain unique names for SCSI devices in Linux.
The names usually given by Linux do not reflect physical relationships in any way.
To get round this problem, you can use the program “ScsiDev” to be found under
http://www.garloff.de/kurt/linux/scsidev/.
Installation: after unpacking the package, the following is sufficient:
configure
make
make install
to install the program.
There is also a patch file in the package which extends the local boot file, so that at each
system start the SCSIDev device files are created. The following commands are sufficient
for patching:
cd /etc/init.d
patch -p0 -i <SCSIDev-Directory>/boot.diff
86
13 October 2006
Edition 7
Linux
Depending on the system, you must do some manual follow-up work. With a SuSE 8.0
installation, for example, both lines
test -z "$DO_FREE_RAM4"
unset DO_FREE_RAM4
|| freeramdisk /dev/ram4
must be added by hand in line 82.
If any SCSI driver is loaded as a module, in /etc/modules.conf the alias
scsi_hostadapter
should be set to the corresponding SCSI adapter, or in line 41
modprobe scsi_hostadapter
should be set to the corresponding module name.
At every restart, the SCSI-Dev device names are immediately present under /dev/scsi.
The names (for tape drives) are made up as follows:
nsth1-0c0i0l0
nsth1-0c0i0l1
sth1-0c0i0l0
sth1-0c0i0l1
The n before the name indicates a non-rewinding device.
The “st” indicates the type of device files and corresponds exactly to the name which is
normally found in the /dev/ directory.
h1-0 is an attempt to make a unique name for the host adapter.
c0 is an indicator for the channel
i0 is an indicator for the SCSI ID
l0
i.e.
[n][type of device][SCSI adapter]c[Channel]i[SCSI ID]l[LUN]
Edition 7
13 October 2006
87
Linux
5.1.5 Building the kernel
With an SMP kernel:
1. On UTS_RELEASE in /usr/include/linux/version.h, check and adapt as appropriate.
2. On EXTRAVERSION in /usr/src/linux/Makefile, check and adapt as appropriate.
cd /usr/src/linux
make xconfig
Configuring via graphical interface.
With Primergy B210 where the boot disk is connected via Adaptec, ensure that the Adaptec
driver is active. The Symbiosdriver must be deactivated.
make dep
make clean
make bzImage
cp arch/i386/boot/bzImage /boot/vmlinuz.js (e.g.)
Next, adapt /etc/lilo.conf as appropriate or add a new module.
mk_initrd –k vmlinuz.js –i initrd.js
lilo
make modules_install
Then you can boot with the new system.
88
13 October 2006
Edition 7
Reliant UNIX
5.2 Reliant UNIX
5.2.1 Requirements
5.2.1.1
Versions of Reliant UNIX
CentricStor functions fully, i.e. with compression and 64 logical drives, with the following
versions:
–
–
–
5.2.1.2
5.45 B00 + EKS SIY5B063
5.45 B10 + EKS SIY5B124
5.45 B20 (and later versions)
FCdriver for EMULEX LP8000
i
Reliant UNIX is connected to CentricStor via the FC controller EMULEX LP8000.
With the RM6001 there is a line for each FC controller (in this case 4 controllers) in the file
/etc/controller . The line is as follows:
.
#ctlr_type:
cab_id:
bus_id:
chan:
mbp:
fc :
log_no:
0 :
bus_type:
pci :
16 :
206 :
slot_id:
4 :
7 :
:
fc :
1 :
pci :
16 :
238 :
4 :
7 :
fc :
2 :
pci :
16 :
238 :
5 :
6 :
fc :
8 :
pci :
16 :
206 :
5 :
6 :
:
option
1
:
1
:
If an FC switch is connected and the switch protocol is used, a 1 must be entered in the
“option” column.
If a hub is connected, or if there is a direct link to another participant, the field must be left
free (AL protocol).
1
For the RM400, see the man pages on the command upd_channel_id
Edition 7
13 October 2006
89
Reliant UNIX
5.2.2 Device configuration
5.2.2.1
Compressed WWNs in the device nodes
To avoid excessively long names in the device nodes, the WWNs in Reliant UNIX have been
compressed from 16 to 5 characters. To find the assignment of WWNs to the compressed
WWNs, use the command autoconf -F:
# autoconf -F
Fibre Channel Configuration:
fc/fc0 FC LP6502-OS [FW
iof0/stape.09.912a1
iof0/stape.09.d9277
iof0/stape.09.c9fcc
2.12 00], Top.: FC_AL, state: DOWN
3.02 00], Top.: PT-PT FABRIC, state: READY
10000000c924f6c1 D_ID 01.12.00 L_ID 126
10000000c92610c3 D_ID 01.11.00 L_ID 126
10000000c924f66f D_ID 01.10.00 L_ID 126
2.12 00], Top.: FC_AL, state: DOWN
3.02 00], Top.: PT-PT, state: DOWN
Here you can see that three host bus adapters for the LP8000 are recognized on the other
side of the switch (PT-PT FABRIC) via the FC controller 09.
If a zoning was configured on the switch, as in the zoning example on page 279), the host
bus adapter of ICP2 (see the section with the grey background on the table below) would
not have been recognized. This means that the device nodes of ICP2 could not initially be
created and access to the LDs would not at first be possible.
In order to find out the ICP assignments, make a comparison with the WWNs of the FC
controller:
compressed WWN
WWPN
Open Systems ICP
912a1
10:00:00:00:c9:24:f6:c1
ICP2
d9277
10:00:00:00:c9:26:10:c3
ICP1
c9fcc
10:00:00:00:c9:24:f6:6f
ICP0
i
90
If several FC controllers are connected to the same fabric (without zoning) on
CentricStor, the other controllers can also see all the ICPs; this means that all the
logical devices (see following section) can also be seen from various locations.
However, they can only be accessed via different paths. A dedicated assignment
should be made here via the zoning in the switch. This is so that the HW configuration can be automatically switched over to a different path.
13 October 2006
Edition 7
5.2.2.2
Reliant UNIX
Logical drives in the autoconf -l
i
Requirement: installation of the package SI_draid.
# autoconf -l
fc/fc2 FC LP8000-OS [FW 3.02 00], Top.: PT-PT FABRIC, state:
READY
iof0/sport.09 FCP
iof0/stape.09.912a1 Centric Stor
iof0/stape.09.912a1.1 Centric Stor
...
iof0/stape.09.d9277 Centric Stor
iof0/stape.09.d9277.1 Centric Stor
...
iof0/stape.09.c9fcc Centric Stor
iof0/stape.09.c9fcc.0 Centric Stor
...
The device nodes under /dev/iof0/ in Reliant UNIX
raw tape device
FC controller
compressed WWNN (ICP)
LUN (logic device number)
n = no rewind, c=compression
/dev/iof0/rstape.09.921a1.63n
Only the following two types of device node may be used in NetWorker with the CentricStor
logical device:
/dev/iof0/rstape.09.921a1.63n
/dev/iof0/rstape.09.921a1.63cn
Edition 7
no rewind
compression & no rewind
13 October 2006
91
Reliant UNIX
If no zoning is used, all the ICPs will be visible and, as a consequence, so will the logical
devices on the ICPs. As a rule, each host is only assigned its own LDs, while the other LDs
remain with other hosts.
!
CAUTION: At this point a clean configuration is needed in order to avoid unwanted
access to external LDs. We therefore recommend that you use symbolic links with
more meaningful names (with ICP and LD name in CentricStor) only for those LDs
which are to be accessed by this host. (An example of a more meaningful name
would be vt for virtual tape):
Link
UNIX device nodes
/dev/vt/STAR-ICP0/V000n
/dev/vt/STAR-ICP0/V000cn
...
/dev/vt/STAR-ICP0/V01Fn
/dev/vt/STAR-ICP0/V01Fcn
/dev/iof0/rstape.09.c9fcc.0n
/dev/iof0/rstape.09.c9fcc.0cn
...
/dev/iof0/rstape.09.c9fcc.31n
/dev/iof0/rstape.09.c9fcc.31cn
...
/dev/iof0/rstape.09.d9277.00c
/dev/iof0/rstape.09.d9277.00cn
...
/dev/iof0/rstape.09.d9277.15c
/dev/iof0/rstape.09.d9277.15cn
Example of a shell script for creatinglinks:
# create-vt-links
cd /dev
mkdir vt
# 1st 32 LDs on ICP0 :
ln -s /dev/iof0/rstape.09.c9ffc.0n
..
ln -s /dev/iof0/rstape.09.c9ffc.31cn /dev/vt/STAR-ICP0/V01Fcn
# 1st 16 LDs on ICP1 :
ln -s /dev/iof0/rstape.09.d9277.0n
..
ln -s /dev/iof0/rstape.09.d9277.15cn /dev/vt/STAR-ICP1/V10Fcn
Wherever possible you should use the same nomenclature on the other hosts. Only these
links should be entered in the NetWorker configurations subsequently.
There is a further advantage if the FC controller is reconfigured on a host. In this case all
device nodes (controller numbers) are changed on the right-hand side, and the symbolic
links on the left-hand side point to invalid destinations. In other words, although all the links
must be recreated, the entries in the host applications (e.g. NetWorker) remain unchanged.
92
13 October 2006
Edition 7
Solaris
5.3 Solaris
5.3.1 Requirements
●
Solaris is required for connection to CentricStor. Versions 7, 8 and 9 are supported
(2.6 on request).
●
To operate tape drives in Solaris V8, at least the following patches must be present on
the system:
108725-09, 108528-15, 108987-09, 111111-03 and 112396-02.
Without these patches there will delays in defining drives, especially under Tivoli.
●
The EMULEX LP9802DC FC controller may not be used.
5.3.2 Useful commands:
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.
For Fujitsu-Siemens customers, there are the following URLs:
http://utensil.pdb.fsc.net and
http://service.fujitsu-siemens.com/support/primepower
Edition 7
13 October 2006
93
Solaris
5.3.3 Important settings and information
●
You must be operating with the tape driver “st”.
●
The requirements for CentricStor are:
–
–
FC driver lpfc version V5.01A.
FW version 3.90A7 with FC controller LP8000 from EMULEX.
Solaris does not permit two FC controllers to bind to the same WWPN. This is also not
permitted in CentricStor because it would otherwise bind two different device nodes to
the same logical device. This is not supported by the backup tools.
!
●
CAUTION: If lpfc V4.21e and LP8000-FW 3.82a1 are used, a connection via
the FC switch from an FC controller in the host can only be made to an FC
controller in the ICPs. For each FC controller in the ICPs, there must be a
dedicated FC controller in the host.
If a new zone is defined and activated in a fabric, all Solaris systems connected to this
fabric will report an error. The file /var/adm/messages gives this message, for
example:
WARNING: lpfc0:120:Device disappeared, nodev timeout: …
●
On FSC/Fujitsu Solaris systems reservation problems can occur with the emulations.
These are caused by the “chktapecln daemon”, which runs every 6 hours.
You must proceed as follows to disable this daemon:
Ê
cp /etc/opt/FJSVmadm/hardmontab /etc/opt/FJSVmadm/hardmontab.org
Ê
Delete the following line from the /etc/opt/FJSVmadm/hardmontab file:
2160 /usr/sbin/FJSVmadm/chktapecln
Ê
94
Then call /usr/sbin/FJSVmadm/swhardmon update so that the modifications
become effective.
13 October 2006
Edition 7
Solaris
5.3.4 Driver for EMULEX LP8000
The driver lpfc must be installed. It normally consists of the files
/kernel/drv/lpfc and
/kernel/drv/lpfc.conf.
The driver is also on the supplement CD.
The firmware is copied to the directory /opt/SMAW/SMAWfirm. The firmware is loaded with
the flup tool. In Solaris 5.6, the directory is called /opt/SMAW/SMAWfirm6.
Supplement CD 2.0A00-05:
Version
Firmware
4.10e
3.20x4
After booting, you can obtain the driver version and firmware from the file
/var/adm/messages:
Feb 26 07:14:46 lieser lpfc: [ID 253773 kern.notice] NOTICE:
Feb 26 07:14:46 lieser Emulex LightPulse FC SCSI/IP 4.10e
Feb 26 07:14:46 lieser scsi: [ID 107833 kern.notice] /pci@15,4000/fibre-channel@2 (lpfc0):
Feb 26 07:14:46 lieser Binding WWPN 10:00:00:00:c9:23:0a:d7 to FCP/SCSI Target53
Feb 26 07:14:46 lieser scsi: [ID 107833 kern.notice] /pci@15,4000/fibre-channel@2 (lpfc0):
Feb 26 07:14:46 lieser Binding WWPN 10:00:00:00:c9:27:a1:55 to FCP/SCSI Target54
Feb 26 07:14:50 lieser lpfc: [ID 129691 kern.notice] NOTICE: lpfc0: Firmware Rev3.20 (D2D3.20X4)
Feb 26 07:14:50 lieser lpfc: [ID 664688 kern.notice] NOTICE: lpfc0: WWPN:10:00:00:00:c9:23:04:92
WWNN:20:00:00:00:c9:23:04:92 DID 0xb1700
i
Edition 7
The accompanying file lpfc.conf must be adapted as appropriate. For more
information see section “Persistent Binding” on page 101 and the example of the file
lpfc.conf.
13 October 2006
95
Solaris
5.3.5 Driver for JNI FCE2-6412-N
The driver jnic must be installed. This driver is on the CD delivered with the card; you can
also download it from http://www.jni.com. It should be at least Release: 4.1.
The board firmware is also delivered as part of the package JNIC.pkg on the Internet. It
should be a version from 3.8.1 or later.
The installation instructions are given in the accompanying manual and are also available
on the Internet.
i
The file /kernel/drv/jnic.conf, which is delivered with it, must be adapted as
appropriate. EZ Fibre (see below) can be used partly for this purpose.
Also see the description of the file jnic.conf.
The tape driver st is supported by the driver version mentioned above.
The controller is operated on the FC switch in the Fabric Mode. This is not set as default
and must be reconfigured.
i
It may be necessary to reboot the system a second time with “reboot -- -r”, if it
changes from Loop Mode to Fabric Mode. Also see the jnic driver messages in the
system file: /var/adm/messages.
EZ Fibre
EZ Fibre has a graphical interface. It is on the accompanying CD and is also available on
the Internet from JNI. It should be at least release version 2.2e.
The connection mode can be configured using this program. It also accurately displays the
status of the card. A configuration of the LUN binding is not possible for the jnic driver, and
must be carried out by hand.
A further problem is that the status of the target (ICP) is always shown as red (i.e. inactive).
The program changes the file jnic.conf. These changes can be seen at the end of the
example file.
96
13 October 2006
Edition 7
Solaris
5.3.6 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.
5.3.7 The tape driver st
i
The more recent controller CDs install this tape type already in the st.conf.
To ensure that tape devices can be operated with a LUN <> 0, the file
/kernel/drv/st.conf must be extended as follows:
1. Then the entry for the new device type of the logical drive “CentricStor” of “FSC” must
be made in the tape-config-list (the entry for a Magstar drive is shown below):
tape-config-list=
"FSC
",
"IBM
03590B",
centrs
X03590B
Edition 7
=
=
"CentricStor",
"PXT1",
"centrs",
"X03590B";
1,0x36,0,0x18219,1,0x00,0;
1,0x24,0,0x61c439,1,0x00,0;
13 October 2006
97
Solaris
2. Next, the LUNs to be used from this host must be specified for the connected targets
(ICPs):
#
#
#
#
name="st"
name="st"
...
name="st"
#
#
#
name="st"
name="st"
...
name="st"
#
#
#
#
#
name="st"
name="st"
...
name="st"
STAR-ICP0:
2nd 32 LDs
ctrl-14 :
3rd 16 LDs
class="scsi" target=53 lun=32;
ctrl-15 :
4th 16 LDs
STAR-ICP1:
2nd 16 LDs
ctrl-14 :
2nd 16 LDs
Following a reboot, the CentricStor drives are then recognized and the corresponding
device nodes created.
i
The target and LUN are specified in hexadecimal form for the device nodes, i.e.:
– 53 becomes 0x35
– 63 becomes 0x3f
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 116 shows an example.
After a reboot, the CentricStor drives are recognized.
If there are further targets in the FC loop (e.g. other ICPs, disks or tape devices ) further
target numbers appear. The file st.conf must then be appropriately extended. EMULEX
drivers are configured via the file /kernel/drv/lpfc.conf and JNI drivers are configured via the
file /kernel/drv/jnic.conf in the same way as the target numbers of the FC targets are shown
in st.conf (previously SCSI IDs).
98
13 October 2006
Edition 7
Solaris
5.3.8 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
Edition 7
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
13 October 2006
99
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 CentricStor) for those
LDs that are to be accessed by this host. (An example of a more meaningful name would
be vt for virtual tape):
Link
Solaris device nodes
/dev/vt/STAR-ICP0/V020bn
/dev/vt/STAR-ICP0/V020cbn
…
/dev/vt/STAR-ICP0/V03Fbn
/dev/vt/STAR-ICP0/V03Fcbn
/devices/pci@1d,2000/fibre-channel@1/st@35,20:bn
/devices/pci@1d,2000/fibre-channel@1/st@35,20:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@35,3f:bn
/devices/pci@1d,2000/fibre-channel@1/st@35,3f:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@36,10:bn
/devices/pci@1d,2000/fibre-channel@1/st@36,10:cbn
...
/devices/pci@1d,2000/fibre-channel@1/st@36,1f:bn
/devices/pci@1d,2000/fibre-channel@1/st@36,1f:cbn
Wherever possible you should use the same nomenclature on the other hosts. Only these
links should be entered in the NetWorker configurations subsequently.
There is a further advantage if the FC controller is reconfigured on a host. In this case all
device nodes (controller numbers) are changed on the right-hand side, and the symbolic
links on the left-hand side point to invalid destinations. In other words, although all the links
must be recreated, the entries in the host applications (e.g. NetWorker) remain unchanged.
i
100
The LUNs set in CentricStor can be shown via:
[GXCC - function bar: Tools ➔ Global Status] ;
Global Status function bar ➔ Tools ➔ Show Balloon Help Summary
13 October 2006
Edition 7
Solaris
5.3.9 Persistent Binding
If a device with SCSI is to be operated in Solaris via FC, a unique ID (SCSI ID) must be
assigned to each target (i.e. the external FC controllers of the ICPs in this case). There are
a number of ways for making this assignment. However, the only secure method is to use
'persistent binding', because with the automatic procedure the assignment might go wrong
in a reboot or a reconfiguration. A line is entered in lpfc.conf for each CentricStor
controller to be operated from Solaris:
fcp-bind-WWPN="10000000c922e06b:lpfc0t53";
The 16-position number is the WWPN, the 'World Wide Port Name' encoded in the FC card
in CentricStor.
If the host does not use an ICP logical device, no persistent binding should be entered for
its FC adapter.
An overview of the WWNs for all adapters of the ICP can be shown with:
GXCC - Function bar: Administration ➔ Show WWN’s
i
To show the WWNN and WWPN for an individual host adapter use:
[GXCC object function ➔ ICP… ➔ Show Details]; Host adapter object information
Alternatively, you can find out the number from Solaris in /var/adm/messages after
booting, or in Sinix-Z through /etc/fc/fclog | grep "own port_name", likewise after
booting.
Rules
Edition 7
●
The “0” in “lpfc0t53” must address the appropriate FC controller.
●
The “53” here is the assigned SCSI-ID, which must be cross-matched with st.conf
(target=53).
●
It is advisable to select a target number outside of the usual range of 0-16 in order to
avoid conflicts with “normal” tape devices. For example, this avoids a situation where a
normal tape unit on a different (SCSI) controller is checked on the numerous
CentricStor LUNs.
●
If several target systems are linked, the target ID must increase over several FC
controllers. (e.g. lpfc0t53, lpfc0t54, lpfc1t55 - but not lpfc0t53, lpfc1t54,
lpfc0t55).
●
If the JNI FC controller is used, a manual entry must be made in the file
/kernel/drv/jnic.conf. The EZ Fibre program offers no configurations. See the
example from page 97.
13 October 2006
101
Solaris
5.3.10 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]
..............
102
13 October 2006
FUJITSU MAJ3182MC
FUJITSU MAJ3182MC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
FSC
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
CentricStor
Edition 7
Solaris
5.3.11 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 116).
5.3.12 Contents of the file lpfc.conf for Solaris
An example of a file modified for CentricStor is shown below. The entries relating to
CentricStor are highlighted in red.
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
COPYRIGHT 1997, 1998, 1999, 2000, EMULEX CORPORATION
3535 Harbor Boulevard, Costa Mesa, CA 92626
All rights reserved. This computer program and related documentation
is protected by copyright and distributed under licenses restricting
its use, copying, distribution and decompilation. This computer
program and its documentation are CONFIDENTIAL and a TRADE SECRET
of EMULEX CORPORATION. The receipt or possession of this program
or its documentation does not convey rights to reproduce or disclose
its contents, or to manufacture, use, or sell anything that it may
describe, in whole or in part, without the specific written consent
of EMULEX CORPORATION. Any reproduction of this program without
the express written consent of EMULEX CORPORATION is a violation
of the copyright laws and may subject you to criminal prosecution.
$Id: lpfc.conf 1.7 2000/06/23 23:42:13 mks Exp $
Solaris LightPulse lpfc (SCSI) / lpfn (IP) driver: global initialized data.
# Verbosity: only turn this flag on if you are willing to risk being
# deluged with LOTS of information.
# You can set a bit mask to record specific types of verbose messages:
#
# 0x1
ELS events
# 0x2
Device Discovery events
# 0x4
Mailbox Command events
# 0x8
Miscellaneous events
# 0x10
Link Attention events
# 0x20
IP events
# 0x40
FCP events
# 0x80
Node table events
# 0x1000
FCP Check Condition events
log-verbose=0;
Edition 7
13 October 2006
103
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
104
13 October 2006
Edition 7
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;
#
#
#
#
#
#
#
#
#
#
#
#
Edition 7
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
13 October 2006
105
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
106
13 October 2006
Edition 7
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;
Edition 7
13 October 2006
107
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.
108
13 October 2006
Edition 7
Solaris
# Important note: you can't just use the following three lines "as is"!
# Refer to the Solaris LightPulse Device Driver documentation for details.
#reg =
0x00801000, 0x00000000, 0x00000000, 0x00000000, 0x00000000, # PCI
#
0x02801010, 0x00000000, 0x00000000, 0x00000000, 0x00001000, # SLIM
#
0x02801018, 0x00000000, 0x00000000, 0x00000000, 0x00000100; # CSRs
# link-speed: link speed selection for initializing the Fibre Channel connection.
#
0 =
auto select (default)
#
1 =
1 Gigabaud
#
2 =
2 Gigabaud
link-speed=0;
5.3.13 Contents of the file jnic.conf for Solaris
##
##
##
##
##
##
##
##
##
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
Edition 7
JNI Corporation jnic driver (Solaris SCSI) configuration file.
jnic.conf
Date last modified: January 11, 2001
For additional information and configuration examples, refer to the "readme.txt"
and "config.txt" files provided with the jnic driver installation package.
Configuration parameters: FcLoopEnabled, FcFabricEnabled, FcPortCfgEnable
Type: boolean
Default:
FcLoopEnabled =
1 (true)
FcFabricEnabled = 0 (false)
FcPortCfgEnable = 1 (true)
These parameters are used to configure HBA port topology. Since the JNI HBA
ports must be configured for operation as L_Port or N_Port, these parameters,
in conjunction with the current HBA port configuration, will determine if HBA
port reconfiguration is necessary. If HBA reconfiguration is necessary,
and the FcPortCfgEnable parameter is set, the change will take affect on the
subsequent adapter reboot. If HBA reconfiguration is necessary and the
FcPortCfgEnable parameter is not set, the driver/adapter will enter nonparticipating mode.
The HBA port will be set up or reconfigured as specified in the following
table:
13 October 2006
109
Solaris
#
Current
# Conf Param
HBA Config
# Loop Fabric (Loop or Fabric) FcPortCfgEn
Action
# ----------- ---------------- ----------- -----------------------------------# 0
0
(don't care)
X
Enter non-participating Mode
# 1
0
Loop
X
No change: L_Port Mode (private loop)
# 1
0
Fabric
1
Configure HBA port (Reboot required)
# 1
0
Fabric
0
# 0
1
Loop
1
Configure HBA port (Reboot required)
# 0
1
Loop
0
# 0
1
Fabric
X
No change: N_Port Mode (fabric)
# 1
1
Loop
X
Enter NL_Port Mode (public loop)
# 1
1
Fabric
X
N_Port Mode (fabric) Note: You cannot
# reconfigure directly from Fabric to
# Public Loop. You must first recon# figure to Private Loop, and then
# to Public Loop.
#
#FcLoopEnabled
=
1;
#FcFabricEnabled =
0;
#FcPortCfgEnable =
0;
jnic0-FcLoopEnabled=0;
jnic0-FcFabricEnabled=1;
jnic0-FcPortCfgEnable=1;
jnic1-FcLoopEnabled=1;
jnic1-FcFabricEnabled=0;
jnic1-FcPortCfgEnable=0;
#
# Configuration parameter: FcEngHeartbeatInterval
# Type: integer
# Default: 5 (sec)
#
# When the JNI adapter/driver detects that the Fibre Channel link is up (and
# there is no I/O activity), it will send a "test frame" (or heartbeat) to
# itself to verify link integrity. The test frame is sent at the interval
# specified by this parameter. If the test frame does not complete, it is
# assumed that there is a link problem. In this situation, the driver
# initiates error recovery to re-establish a good link. A value of "0"
# disables the heartbeat.
#
#FcEngHeartbeatInterval = 5;
#
#
#
#
#
#
#
#
#
#
110
Configuration parameter: FcLrrTimeout
Type: integer
Default: 100 (msec)
Restrictions: N_Port mode only
This value is valid in N_Port mode only. The Emerald Link Reset Received
(LRR) timeout value (msec) tunes link recovery behavior by synchronizing
the Emerald chip with the chip on the fabric switch. It determines how
long to send out LRs before getting back an LRR. If the timeout is reached
13 October 2006
Edition 7
Solaris
# and an LRR has not been received, the controller will start sending off-line
# sequences (OLS). The default value is adequate for most configurations.
#
#FcLrrTimeout = 100;
#
# Configuration parameter: FcLinkUpRecoveryTime
# Type: integer
# Default: 1000 (msec)
#
# Delay (msec) after the link is up before port discovery begins, allowing
# the link to stabilize and protecting against a possible I/O surge. This timer
# is reset every time the link comes up. The default value is adequate for most
# configurations.
#
#FcLinkUpRecoveryTime = 1000;
#
# Configuration parameter: BusyRetryDelay
# Type: integer
#
# Delay (msec) before retrying after receipt of an I/O with a "SCSI Busy"
# status from a target. The number of retries is based on the Solaris retry
# count associated with the I/O.
#
#BusyRetryDelay = 5000;
#
# Configuration parameter: FailoverDelay
# Type: integer
# Default: 0 (sec)
#
# Delay (seconds) before failing all I/O for an offline target. If the delay
# timer expires, all I/O for the failed target is returned to the application.
# A zero value disables failover.
#
#FailoverDelay = 0;
#
# Configuration parameter: TimeoutResetEnable
# Type: boolean
# Default: 0 (false)
#
# Boolean parameter for enabling SCSI target resets for timed out I/O. When
# the timer expires (usually 60 seconds, as specified by the upper layers),
# the driver issues a target reset to attempt to clear the device (which might
# be either too busy to respond or stuck).
#
#TimeoutResetEnable = 0;
#
Edition 7
13 October 2006
111
Solaris
# Configuration parameter: QfullRetryCount
# Type: integer
# Default: 5
#
# Number of times an I/O is retried due to receipt of a "SCSI QFULL" status
# from a target. The delay between retries is based on the QfullRetryDelay
# parameter.
#
#QfullRetryCount = 5;
#
# Configuration parameter: QfullRetryDelay
# Type: integer
#
# Delay (msec) before retrying after receipt of an I/O with a "SCSI QFULL"
# status from a target. The number of retries is based on the QfullRetryCount
# parameter.
#
#QfullRetryDelay = 5000;
#
# Configuration parameter: IoRecoveryDelay
# Type: integer
#
# Delay (msec) between target online and I/O recovery. This allows time for
# devices which must flush I/O that was in progress prior to a link going down.
#
#IoRecoveryDelay = 50;
#
# Configuration parameter: JniCreationDelay
# Type: integer
# Default: 5 (sec)
#
# Delay (seconds) after driver creation to allow the network to stabilize,
# discover ports, and build the driver's database. Increase this value
# if targets are being discovered too late in the boot process.
#
#JniCreationDelay = 5;
#
# Configuration parameter: FlogiRetryCount
# Type: integer
# Default: 3
#
# Total number of Fabric Login (FLOGI) attempts before giving up logging in to
# a switch. Failure prevents participation on a Fabric topology.
#
#FlogiRetryCount = 3;
#
112
13 October 2006
Edition 7
Solaris
# Configuration parameter: PlogiRetryCount
# Type: integer
# Default: 5
#
# Total number of Port Login (PLOGI) attempts before giving up
# logging in to a SCSI target.
#
#PlogiRetryCount = 5;
#
# Configuration parameter: FcEmldEngTcbCount
# Type: integer
# Default: 1533
#
# Total number of concurrent exchanges (also called transfer control blocks)
# allowed by the adapter. To optimize performance, set this parameter to match
# the memory capacity of the hardware.
#
#FcEmldEngTcbCount = 1533;
#
# Binding Parameters: See "config.txt" file for binding examples.
#
# Configuration parameter: def_hba_binding
# Type: string
# Default: "jnic*"
#
# "jnic*"
(means all target/LUN instances will be initialized by all
#
jnic instances)
#
# "null"
(means no target/LUN instance will be initialized by any jnic
#
instance UNLESS the targetX_hba or targetX_lunY_hba binding
#
parameters are explicitly defined)
#
# Sets the default HBA binding for every target/LUN instance which does not
# explicitly define one.
#
- A "*" following an HBA name indicates all instances of that HBA driver
#
#def_hba_binding = "jnic*";
def_hba_binding="null";
#
# Configuration parameter: def_wwnn_binding
# Type: string
# Default: "$xxxxxxxxxxxxxxxx" (means WWNN is "static don't care")
#
# Sets the 16 digit hexadecimal default WWNN binding for every target/LUN
# instance which does not explicitly define one.
#
- A "$" preceding the string indicates static binding by WWNN enabled
#
- A "x" in place of a digit indicates "don't care" for that digit
#
#
#def_wwnn_binding = "$xxxxxxxxxxxxxxxx";
#
Edition 7
13 October 2006
113
Solaris
# Configuration parameter: def_wwpn_binding
# Type: string
# Default: "$xxxxxxxxxxxxxxxx" (means WWPN is "static don't care")
#
# Sets the 16 digit hexadecimal default WWPN binding for every target/LUN
#
- A "$" preceding the string indicates static binding by WWPN enabled
#
#
#def_wwpn_binding = "$xxxxxxxxxxxxxxxx";
#
# Configuration parameter: def_port_binding
# Type: string
# Default: "xxxxxx" (means PORT is "non-static don't care")
#
# Sets the 6 digit hexadecimal default port binding for every target/LUN
#
- A "$" preceding the string indicates static binding by port ID enabled
#
#
#def_port_binding = "xxxxxx";
#
# Configuration parameters for target to FC device mapping:
#
targetX_hba,
#
targetX_lunY_hba,
#
targetX_wwnn,
#
targetX_wwpn,
#
targetX_port,
#
# Type: string
# Default:
#
# Example usage: Replace the 'x' characters with actual WWNN, WWPN, or port ID.
#
# target0_hba
= "jnic0";
# target0_lun0_hba
= "jnic0";
# target0_wwnn
= "xxxxxxxxxxxxxxxx";
# target0_wwpn
= "xxxxxxxxxxxxxxxx";
# target0_port
= "xxxxxx";
target54_wwnn="20000000C922C7AE";
target54_wwpn="10000000C922C7AE";
target54_lun0_hba="jnic0";
114
13 October 2006
Edition 7
Solaris
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
Edition 7
Configuration parameters for target and
target_throttle
<default = 256>,
lun_throttle
<default = 64>,
targetX_throttle
<default = 256>,
targetX_lun_throttle <default = 64>
targetX_lunY_throttle <default = 64>
LUN level throttling:
- Default throttle for all targets
- Default throttle for all LUNS
- Specific throttle for targetX
- Default throttle for all targetX LUNS
- Specific throttle for targetX LUN
Type: integer
Default:
Example usage:
target_throttle = 256;
lun_throttle = 64;
target0_throttle = 256;
target0_lun_throttle = 64;
target0_lun1_throttle = 64;
Configure parameter: automap
Set to 0 for persistence binding and 1 for auto mapping
Type: integer
Defalut: 0
Example usage:
automap = 0;
jnic0-automap = 0;
13 October 2006
115
Solaris
jnic0-JniCreationDelay=5;
jnic0-FlogiRetryCount=3;
jnic0-PlogiRetryCount=5;
jnic0-BusyRetryDelay=5000;
jnic0-FailoverDelay=0;
jnic0-TimeoutResetEnable=0;
jnic0-QfullRetryCount=5;
jnic0-QfullRetryDelay=5000;
jnic0-IoRecoveryDelay=50;
jnic0-automap=0;
jnic0-FcEmldEngTcbCount=1533;
jnic0-FcLrrTimeout=100;
jnic0-FcLinkUpRecoveryTime=1000;
jnic0-FcEngHeartbeatInterval=5;
jnic0-def_hba_binding="null";
5.3.14 Contents of the file st.conf for Solaris
#
# Copyright (c) 1995-2000 by Sun Microsystems, Inc.
# All rights reserved.
#
#
#pragma ident "@(#)st.conf 1.24 00/03/17 SMI"
#
# This file contains configuration entries for both officially supported
# devices of Sun Microsystems and many 3rd party devices.
#
# The officially supported devices are :
#
#
"ARCHIVE Python 28388"
#
#
#
"ARCHIVE VIPER 150"
#
"EXABYTE EXB-8200"
#
"EXABYTE EXB-8500"
#
"EXABYTE EXB-8505"
#
"EXABYTE EXB-8900"
#
"HP 88780"
#
"HP C5683A" Note 1
#
"HP C5713A" Note 1
#
"Quantum DLT4000"
#
"Quantum DLT7000"
#
"STK 9840" Note 1
#
"SUN DLT4000"
#
"SUN DLT4700"
#
"SUN DLT7000"
116
13 October 2006
Edition 7
Solaris
#
"TANDBERG SLR5"
#
"TANDBERG TDC 4200"
#
"TANDBERGMLR1"
#
"TANDBERGMLR3"
#
# Notes
# ----#
1
Drive is configured automatically - no entry is needed in st.conf.
#
# The 3rd party devices do apparently work with the configurations listed.
# All the entries have been taken from the net and probably have worked in
# the past, but have not been tested by Sun Microsystems. Use these entries
# as your starting point for generating your configuration entries.
#
#
tape-config-list=
# "Emulex MTO2",
"Emulex MT02 QIC-11/QIC-24",
"MT02",
# "ANRITSU DMT2120",
"Unisys 1/2\" Reel",
"ANRITSU",
# "ARCHIVE Python 28454",
"Archive Python 4mm Helical Scan",
"ARCH_Python",
"Archive Python 4mm DAT Stacker",
"ARCH_Python",
"Archive/Conner CTDX004 4mm DAT",
"Conner2-DAT",
# "ARCHIVE VIPER 150",
"Archive QIC-150",
"QIC150",
# "ARCHIVE VIPER 255",
"Archive QIC-525",
"QIC150",
# "DEC DLT2",
"DEC DLT",
"DLT2",
# "DEC TZ87",
"DEC DLT",
"DLT2",
# "EXABYTE EXB-2501",
"Exabyte EXB-2501 QIC",
"EXB-2501",
# "EXABYTE EXB-4200c",
"Exabyte 4mm Helical Scan",
"Exa4200c",
"Exabyte EXB-8200 8mm Helical Scan", "EXB-8200",
"Exabyte EXB-8500 8mm Helical Scan", "EXB-850X",
"Exabyte EXB-8505 8mm Helical Scan", "EXB-850X",
# "EXABYTE EXB8500C",
"Exabyte 8500C 8mm Helical Scan",
"EXB-850X",
"Mammoth EXB-8900 8mm Helical Scan", "EXB-8900",
# "FUJITSU M1016B M2483B", "Fujitsu 1/2\" Cartridge",
Fujitsu_comp",
# "FUJITSU M248",
"Fujitsu 1/2\" Cartridge",
Fujitsu_m248x",
# "HP 88780",
"HP-88780 1/2\" Reel",
"HP_half",
# "HP C1533A",
"HP DDS2 4mm DAT loader",
"HP_DAT",
# "HP C1553A ",
"HP C1553A 4mm DAT",
"HP_DAT",
# "HP C1537A",
"HP DDS-3 4mm DAT ",
"HP_DAT_3",
# "HP C1557A",
"HP DDS-3 4mm DAT loader",
"HP_DAT_3",
# "HP HP35470A",
"HP 35470A 4mm DAT",
"HP_DAT",
# "HP HP35480A",
"HP 35480A 4mm DAT",
"HP_DAT",
# "IBM 03490",
"IBM 3490E 1/2\" Cartridge",
"CLASS_3490",
# "IBM 9348",
"STK 4220 1/2\" Cartridge",
"C3490",
# "KENNEDY",
"Kennedy 1/2\" Reel",
"KENNEDY",
# "LMS",
"CDC 1/2\" Cartridge",
"LMS",
# "M4 DATA 123107 SCSI",
"M4-Data 1/2\" Reel",
"M4_DATA",
# "Metrum",
"Metrum VHS Cartridge",
"MetD",
# "QUANTUM DLT7000",
"Quantum DLT7000",
"DLT7k-data",
# "SUN DLT7000",
"Sun DLT7000",
"DLT7k-data",
# "Quantum DLT4000",
"Quantum DLT4000",
"DLT-data",
# "SUN DLT4000",
"DLT4000",
"DLT-data",
# "SUN DLT4700",
"DLT4700 Library",
"DLT-data",
Edition 7
13 October 2006
117
Solaris
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
118
"R-BYTE RB100",
"SONY SDT-5200",
"STK 9490",
"STK 4280",
"STK", "STK 1/2\
"TANDBERG 4100",
"TANDBERG 4200",
"TANDBERG TDC 4200",
"TANDBERG SLR5",
"TANDBERGMLR1",
"TANDBERGMLR3",
"TELEX",
"WANGTEK 51000 SCSI",
"WANGTEK 5150ES",
"WANGTEK 5525ES SCSI",
"WANGTEK 6130-HS",
"WangDAT Model 2600",
"WangDAT Model 3400",
"WangDAT",
"\076\000",
"FSC ",
ANRITSU
=
ARCH_Python
=
CLASS_3490
=
C3490
=
Conner2-DAT
=
DAT
=
DLT2
=
DLT-data
=
DLT7k-data
=
EXB-2501
=
EXB-8200
=
EXB-850X
=
EXB-8900
=
Exa4200c
=
Fujitsu_comp
=
Fujitsu_half
=
Fujitsu_m248x
=
HP_DAT
=
HP_DAT_3
=
HP_half
=
KENNEDY
=
LMS
=
M4_DATA
=
MT02
=
MetD
=
QIC150
=
TANDB-2_5G
=
TAND-8G-VAR
=
TANDBERG_MLR1
=
TAND-50G-VAR
=
TAND_4100_QIC
=
"R-Byte Whozits",
"DAT",
"SONY 4mm DAT",
"DAT",
"CLASS_3490",
"C3490",
" Cartridge",
"CLASS_3490",
"Tandberg 4100 QIC",
"TAND_4100_QIC",
"Tandberg 4200 QIC",
"TAND_4200_QIC",
"Tandberg QIC 2.5 Gig Tape Drive",
"TANDB-2_5G",
"Tandberg 8 Gig QIC",
"TAND-8G-VAR",
"Tandberg MLR1 QIC",
"TANDBERG_MLR1",
"Tandberg 50 Gig QIC",
"TAND-50G-VAR",
"C3490",
"Wangtek 1.2GB QIC",
"WtQIC",
"Wangtek QIC-150",
"WANGTEK_QC150",
"Wangtek 525MB QIC",
"WtQIC",
"Wangtek 4mm Helical Scan",
"WANGTEK_6130",
"WangDAT 4mm DAT",
"WangDAT",
"WangDAT 4mm DAT",
"WangDAT",
"Wang DAT 3.81 Helical Scan",
"WangDAT",
"Fujitsu 1/2\" Cartridge",
"Fujitsu_half";
"CentricSTOR",
"centrs";
1,0x25,0,0x41d,4,0x00,0x02,0x03,0x03,1;
1,0x2c,0,0xde39,4,0x00,0x8c,0x8c,0x8c,3;
1,0x24,0,0x1c43d,1,0x00,0;
1,0x24,0,0x1c43d,4,0x00,0x00,0x00,0x01,2;
1,0x2c,0,0xde39,1,0x00,0;
1,0x34,0,0x0439,1,0x00,0;
1,0x38,0,0xd639,4,0x17,0x18,0x80,0x81,2;
1,0x38,0,0xD639,4,0x80,0x81,0x82,0x83,2;
1,0x38,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
1,0x28,1024,0x442,1,0x00,0;
1,0x28,0,0x8c79,1,0x00,0;
1,0x29,0,0xce39,4,0x14,0x15,0x8c,0x8c,1;
1,0x29,0,0x19E39,4,0x27,0x27,0x27,0x27,3;
1,0x34,0,0x1639,2,0x63,0x0,1;
1,0x21,0,0x18639,4,0x00,0x00,0x00,0x09,1;
1,0x21,0,0x63b,1,0x00,0;
1,0x21,0,0xc639,1,0x00,0;
1,0x34,0,0x19679,1,0x0,0;
1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1;
1,0x23,0,0x41d,4,0x01,0x02,0x03,0xc3,1;
1,0x22,0,0x41d,4,0x01,0x02,0x03,0x03,1;
1,0x20,0,0x66b,1,0x00,0;
1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
1,0x14,512,0x202,4,0x84,0x05,0x05,0x05,1;
1,0x36,0,0x1639,1,0x00,0;
1,0x15,512,0x642,1,0x00,0;
1,0x32,0,0xD67b,1,0x0,0;
1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
1,0x32,512,0x463a,1,0x00,0;
1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
1,0x32,512,0x463a,1,0x00,0;
13 October 2006
Edition 7
#
#
#
#
#
#
#
TAND_4200_QIC
WANGTEK_6130
WANGTEK_QC150
WangDAT
WangDAT
WtQIC
Solaris
=
=
=
=
=
=
1,0x32,512,0x463a,1,0x00,0;
1,0x2a,0,0x659,1,0x00,0;
1,0x16,512,0x642,1,0x00,0;
1,0x2b,0,0x659,1,0x00,0;
1,0x34,0,0x0679,1,0x00,0;
1,0x32,512,0x467a,1,0x00,0;
centrs = 1,0x36,0,0x18219,1,0x00,0;
name="st" class="scsi"
target=0 lun=0;
target=1 lun=0;
target=2 lun=0;
target=3 lun=0;
target=4 lun=0;
target=5 lun=0;
target=6 lun=0;
#
# In case there are wide tape drives, one can use these targets
#
#name="st" class="scsi"
#
target=8 lun=0;
#
target=9 lun=0;
#
target=10 lun=0;
#
target=11 lun=0;
#
target=12 lun=0;
#
target=13 lun=0;
#
target=14 lun=0;
#
target=15 lun=0;
Edition 7
13 October 2006
119
Solaris
#
# for CentricSTOR we use more luns
#
# Support LP8000
name="st" class="scsi" target=53 lun=0;
# The following 4 LUNs will be used by the other systems in the server.
# name="st" class="scsi" target=53 lun=17;
# Support JNI FCE2-6412-N Port A
120
13 October 2006
Edition 7
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"
name="st"
name="st"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
class="scsi"
Solaris
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
target=54
lun=14;
lun=15;
lun=16;
lun=17;
lun=18;
lun=19;
lun=20;
lun=21;
lun=22;
lun=23;
lun=24;
lun=25;
lun=26;
lun=27;
lun=28;
lun=29;
lun=30;
lun=31;
##### end of target config section
5.3.15 Extensions for Data Protector and SolarisTivoli
For Data Protector the size of the shared memory must be extended.
Ê
In the file /etc/system the entry:
set shmsys:shminfo_shmmax=0x7FFFFFFF
This change has no negative effect on the system.
Ê
Then the system must be rebooted.
5.3.16 Extensions for NetBackup
For NetBackup the “sg” driver must be installed in accordance with the “NetBackup Media
Manager Device Configuration Guide” from Veritas.
Edition 7
13 October 2006
121
HP-UX
5.4 HP-UX
5.4.1 General
●
HP-UX B11.00 is required for connection to CentricStor.
(there are two older FC cards, A6684A with HSC-EISA and A6685A with HP-HSC
Interface, which are already supported by HP-UX B10.20. These have not yet been
tested. Both cards support “Fabric Login”.)
●
The patch PHKL_23939 from http://www.hp.com is required for connection to
CentricStor. If the patch is not in use, the machine logs itself on and off with every
“open/close” on the FC switch. Then the klog.msg of the ICP constantly shows
messages.
●
Device nodes can only be generated if they can be accessed from LUN 0 without interruption.
5.4.2 Restrictions
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.4.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 CentricStor)
lsdev
xstm
see the chapter “Useful commands and information” on page 265
5.4.4 Links
HP: Migration to Fabric
122
13 October 2006
Edition 7
IBM-AIX
5.4.5 Device nodes
By default, device nodes are created as compressed. However, Mammoth2 and “generic”
SCSI emulations create nodes which are not compressed. In these cases compression
should be switched on in the CentricStor configuration.
/dev/rmt/c6t0d0BESTb
...
CAUTION!
If the port on the switch or the switch itself changes then the devices must be regenerated with sam. In the process the controller number is raised
(/dev/rmt/c6t0d0BESTb -> /dev/rmt/c7t0d0BESTb).
!
5.5 IBM-AIX
5.5.1 Restrictions
The standard driver OST (Other SCSI Tape) generates device nodes, which cannot
compress.
In CentricStor V2.1 or higher, compression can be turned on explicitly for an LD.
i
●
Edition 7
3590 Emulation on the CentricStor side:
–
LAN libraries:
LUN 0 must always be defined with FSC CentricStor, the other LUNs with
IBM 03590.
–
SCSI libraries:
Define robotics on LUN 0, all emulations with IBM 03590
–
Drives with the emulation FSC CentricStor are entered in AIX as “other scsis tape”.
–
Drives with the emulation IBM 03590 are entered as “IBM 3590 Tape Drive and
Medium Changer”.
13 October 2006
123
IBM-AIX
●
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
●
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.
●
When hardware scanning takes place with cfgmgr and VJUK the following message is
issued:
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed. devices.fcp.changer
No functional restriction has been observed.
5.5.3 Useful commands
–
–
–
–
–
–
–
–
124
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 265
13 October 2006
Edition 7
IBM-AIX
5.5.4 Configuration of the drives
Ê
First, delete any drives present drives with smit -> Devices -> Tape Drive ->
Remove a Tape Drive.
Ê
Connect the drives or link them with CentricStor.
Ê
Reboot the system with reboot -- -r. If the system cannot be rebooted, you can, for
example, delete the tapes with the following script:
#!/usr/bin/ksh
lsdev -Cc tape | awk '{ print $1 }' | while read RMT; do
rmdev -l $RMT -d
done
After this, recreate the configuration automatically with cfgmgr.
Checking the tape drives in AIX:
# lsdev -Cc tape
rmt0 Available 10-78-01 IBM 3590 Tape Drive and Medium Changer (FCP)
Checking the characteristics of a tape drive:
# lsattr -El rmt1
mode
yes
block_size
0
compress
yes
autoload
no
logging
no
max_log_size
500
space_mode
SCSI
rew_immediate no
trailer_labels no
retain_reserve no
emulate_auto
no
limit_readerp no
fail_degraded no
devtype
03590E1A
mtdevice
scsi_id
0x31a00
lun_id
0x2000000000000
location
ww_name
0x10000000c937fa42
drive_port
0
new_name
dev_status
node_name
alt_pathing
no
primary_device rmt1
Use Buffered Writes
Block Size (0=Variable Length)
Use Hardware Compression on Tape
Use Autoloading Feature at End-ofActivate volume information logging
Maximum size of log file (in # of entries)
Backward Space/Forward Space Record Mode
Use Immediate Bit in Rewind Commands
Trailer Label Processing
Retain Reservation
Use Random Mode to Emulate Autoloader Tape Drive
Limit Read Error Recovery Time to 5 Seconds
Fail Tape Operation if Degraded Media is Detected
Device Type
Library Device Number
SCSI Target ID
Logical Unit Number
Location
World Wide Port Name
Drive Port Number
New Logical Name
N/A
World Wide Node Name
Enable Alternate Pathing Support
Primary Logical Device
True
True
True
True
True
True
True
True
True
False
True
True
True
False
True
True
True
True
False
False
True
False
False
True
False
The WWN and LU, among other things, are output. Scsi_id is the port ID on the SAN switch.
Edition 7
13 October 2006
125
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.
126
13 October 2006
Edition 7
IBM-AIX
Modifying the device characteristics (only required for other scsi tape devices!):
Reserve support and variable block length can be set for these drives via smit.
The device nodes “IBM 3590 Tape” do not need to be modified.
Ê
smit -> Devices -> Tape Drive -> Change / Show Characteristics of a
Tape Drive
Reserve/Release set support to yes
set lock size from 512 to 0 ( == variable)
or with SHELL:
chdev -l 'rmt0' -a res_support='yes'
chdev -l 'rmt0' -a block_size='0'
5.5.5 Device nodes
Device nodes in AIX:
Special File
Rewind on Close
Retension on Open
Density Setting
/dev/rmt*
Yes
No
#1
/dev/rmt*.1
No
No
#1
/dev/rmt*.2
Yes
Yes
#1
/dev/rmt*.3
No
Yes
#1
/dev/rmt*.4
Yes
No
#2
/dev/rmt*.5
No
No
#2
/dev/rmt*.6
Yes
Yes
#2
/dev/rmt*.7
No
Yes
#2
Density #1 = highest possible, #2 = next highest.
Edition 7
13 October 2006
127
IBM-AIX
5.5.6 Testing the tape drives with tapeutil
Tapeutil permits simple tests of the tape functions. Fixed block mode is used, so tapeutil can
be employed in CentricStor V3.0 or higher.
Menu:
# tapeutil
General Commands:
1. Open a Device
2. Close a Device
3. Device Info
4. Tape Drive Service Aids
5.
6.
7.
8.
Inquiry
Test Unit Ready
Reserve Device
Request Sense
9.
10.
11.
Q.
Log Sense Page
Mode Sense Page
Release Device
Quit Program
Medium Changer Commands:
12. Element Information
13. Position To Element
14. Element Inventory
15. Exchange Medium
16.
17.
18.
19.
Move Medium
Load/Unload Medium
Initialize Element Status
Prevent/Allow Medium Removal
Tape Commands:
20. Query/Set Parameters
21. Prevent/Allow Medium Removal
22. Rewind
23. Erase Gap
24. Forward Space Filemarks
25. Forward Space Records
26. Space to End of Data
27. Log Sense
28. Display Message
29. Synchronize Buffers
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
Read and Write Tests
Unload Tape
Erase
Write Filemarks
Backward Space Filemarks
Backward Space Records
Query/Set Tape Position
Read or Write Files
Query/Create/Change Partition
Report Density Support
Enter Selection:
128
13 October 2006
Edition 7
IBM-AIX
5.5.7 Problems with AIX
The machine freezes on booting with error 0518.
The system cannot complete a mount.
1.
2.
3.
4.
Insert the first installation CD.
Switch on the machine.
When there is a white screen after the fourth ICON, press the F1 key.
Then change the boot sequence in the maintenance menu and then boot first from the
CD.
5. The system then automatically starts up from the CD.
6. F1 ↵
7. 1 ↵ (English)
8. 3 ↵ (Start Maintenance Mode for System Recovery)
9. 1 ↵ (Access a Root Volume Group)
10. 0 ↵ (Continue)
11. Then select the boot disk
12. 1 ↵ (Access this volume and start a shell)
13. The system then carries out a mount on all important file systems.
14. If there are problems, the “fsck” must be carried out manually.
15. Then reconstruct the boot sequence with the commands:
bootlist –m normal –o
to show the current status
bootlist –m normal hdisk0 to specify the disk as the first
bootlist –m normal –o
to show current status
Edition 7
13 October 2006
129
by f.f. 1992
6 CentricStor in Windows
6.1 NT 4.0
6.1.1 Installation
●
Primergy 070 with LAN and SCSI card (FC card is removed)
●
Format SCSI disk via Adaptec BIOS. If you do not do this, problems may occur
if Linux etc. was previously installed on the machine.
●
Install the NT 4.0 basic system if it is not already present.
●
Install Service Pack 6a if it is not already present. LP8000 requires Service Pack 3 or
higher. We strongly recommend the use of SP 6a.
●
Insert the Qlogic card QLA2200F with BIOS 1.61 and install the driver for NT 4.0
(Version. 7.02.05.02) from the floppy disk delivered with the card
or
Insert LP8000 card and then, for example, install the driver for NT 4.0
(Version. 4-4.53a5), which can be downloaded from http://www.emulex.com.
Edition 7
●
Then reboot the system.
●
After this, Qlogic or LP8000 must be visible as SCSI devices (system control -> SCSI).
●
Attach the fibre channel and create a link to ICP (zoning on the switch etc.).
●
Via system control -> search for tape device drives.
●
Driver is requested. Then, for example, install “M2 TapeDrive Device Driver V2.10
(m2_v210_winnt.exe)” from EXABYTE. The driver can be downloaded from
http://www.exabyte.com. This process must be repeated for all drives. Which driver is
to be installed depends on the applications you intend to use (see chapter “Tape
management systems” from page 141).
●
This completes the installation.
13 October 2006
131
NT 4.0
CentricStor in Windows
●
The session rest time must be set using a command to 0 minutes. If you do not do this,
NT will ask all visible devices if they are still there and will disturb any running I/Os.
net config server /autodisconnect:0
●
If an LUN (vtd) is being used over other hosts and is thus blocked, NT will abort at this
device during the reboot and device scan and will not be able to find the successive
devices with higher LUNs.
●
NT4.0 can only see drives of one type on CentricStor.
●
When booting with QL2200 the following error messages are written regularly in the
system event log:
"The driver has found a controller error on \Device\SCSI\ql2200 or
ql22001" with the event data: "80110000, f0130000, f0210000,
f0140000, f0170000".
This is normal behavior and occurs, for example, when there are changes in the FC
topology.
●
In order to ensure that the specified block size of 192 KB is maintained in Windows NT
and Windows 2000 with the Qlogic FCC Miniport Driver for the QLA2200 adapter for
Exabyte Mammoth-2, you must ensure that the registry
HKEY_LOCAL_MACHINE➔SYSTEM➔CurrentControlSet➔Services➔Ql2200➔
Parameters➔Device
has a high enough setting for the value MaximumSGList:REG_DWORD .
The default of 0x21(33) in some newer driver versions (e.g. 8.1.5.10 NT4 IP or W2K
IP, FW Version 2.02.01 TP/IP) gives an unsuitable block size of only 128 KB; this
rules out volume-sharing with other systems such as Linux.
If MaximumSGList:REG_DWORD is set to 0x41(65), the maximum block size is set
to 256 KB. Windows must be rebooted after the change. If the NetWorker volume is
labeled under MaximumSGList:REG_DWORD 0x41(65), it is then described with the
specified block size of 192 KB for Exabyte Mammoth-2.
132
13 October 2006
Edition 7
Windows 2000/2003
6.2 Windows 2000/2003
The following restriction applies for the Windows operating system: A maximum of 32 LUNS
can be released for Windows in CentricStor. If more LUNS are configured for Windows in
CentricStor, it can happen that Windows sees all the devices but does not load any tape
device drivers.
In Windows 2003 logical devices are supported with the FC port driver 5-2.22a8 64.
6.2.1 Configuration
Recognizing more than 8 LUNs
Edition 7
●
Change to
HKEY_LOCAL_MACHINE➔ SYSTEM ➔ CurrentControlSet ➔ Control ➔
ScsiPort ➔ SpecialTargetList with REGEDIT.
●
Define a new key which corresponds to the emulation inquiry. Setup:
Vendor 8 characters
Device 16 characters
Version 1 character
Blanks are shown as _ . Example:
EXABYTE_Mammoth2________v
FSC_____CentricStor_____8
●
Define field. LargeLUNs: REG_DWORD: 0x1
●
For IBM 3590E emulation, an entry is not necessary because the emulation has set the
HiSupport Bit.
●
See also the Knowledge Base Article 243869 or 310072 in Microsoft Windows NT.
13 October 2006
133
Windows 2000/2003
●
Windows can only see drives of one type on CentricStor.
●
When booting with QL2200, the following error messages are written regularly in the
system event log:
"The driver has found a controller error on \Device\SCSI\ql2200 or
ql22001" with the event data: "80110000, f0130000, f0210000,
f0140000, f0170000"
This is normal behavior and occurs, for example, when there are changes in the FC
topology.
●
In order to ensure that the specified block size of 192 KB is maintained in Windows NT
and Windows 2000 with the Qlogic FCC Miniport Driver for QLA2200 adapter for
Exabyte Mammoth-2, you must ensure that the registry.
HKEY_LOCAL_MACHINE➔SYSTEM➔CurrentControlSet➔Services➔Ql2200➔Parameters->Device
has a high enough setting for the value MaximumSGList:REG_DWORD.
The default of 0x21(33) in some newer driver versions (e.g. 8.1.5.10 NT4 IP or W2K
IP, FW Version 2.02.01 TP/IP) gives an unsuitable block size of only 128 KB; this
rules out volume-sharing with other systems such as Linux.
If MaximumSGList:REG_DWORD is set to 0x41(65), the maximum block size is set
to 256 KB. Windows must be rebooted after the change. If the NetWorker volume is
labeled under MaximumSGList:REG_DWORD 0x41(65), it is then described with the
specified block size of 192 KB for Exabyte Mammoth-2.
●
Before the operating system is updated the device drivers on the host for the HBAs,
tape devices and robotics (jukebox/media changer) on the fibre channel must be
backed up with CentricStorfor safety’s sake, and after the operating system has been
updated any automatic driver update that takes place must be verified.
Reason: In Windows 2003 it has been observed that after an update the “EXABYTE”
Mammoth2 tape device driver installed previously has been replaced by a “MICROSOFT” Mammoth2 tape device driver which was not compatible with the volumes written previously. Consequently CentricStor backups, for example, can no longer be used
with the Microsoft MM2 driver 5.2.3790.0 (01.10.2002)!
134
13 October 2006
Edition 7
7 CentricStor on NAS systems
7.1 General information on saving using NDMP
The striking feature of the configuration stems from the fact that NDMP Version 3, which is
used with NetWorker 6.x, does not support cloning of tapes.
CentricStor offers implicit cloning of tapes, which means that a copy of NDMP backups can
be created without placing an additional load on the NAS system .
Even if the use of NetWorker 7.x and NDMP Version 4 makes cloning by NetWorker
possible, implicit cloning with CentricStor still offers the advantage that the NAS system is
not burdened by cloning.
7.2 NetApp
7.2.1 Prerequisites
Tests were performed in the following system environment:
–
–
NetApp F760 with operating system version ONTAP 6.2R2 and FC controller X2045A
(QLA2200)
Connection of NetApp via FC switch
7.2.2 Restrictions
Only the first 16 virtual NetApp drives are recognized. (?) - Software environment of CS:
818.204
It must be ensured here that the generic SCSI emulation “FSC CentricStor” is selected for
the relevant ICPs on LUN 0.
Edition 7
13 October 2006
135
NetApp
CentricStor on NAS systems
7.2.3 Configuration
CentricStor ICP
Emulation IBM 3590E or Mammoth 2
Recommendation: Compression by HOST; the ON or OFF setting can also be used.
At least NetWorker 6.1A10 with EKS 1-5 for Solaris
When the 3590E emulation is used, the following entry must be made on the NetWorker
server in the file /nsr/res/defaults:
NSR_DEV_BLOCK_SIZE_3590=256
(Also applies for NetWorker on Linux etc.)
The NetWorker block size for 3590 must be adjusted from the default 384k to 256k because
the DUMP command called explicitly on NetApp permits a maximum block size of 256k.
We recommend that the timer should be set as for NetWorker (see section “Configuration
of the “CentricStor” library” on page 142).
Configuration of the NetApp devices, for example “nrst31a” (cmp, norewind) as NDMP
devices.
During a backup with NetWorker, a temporary snapshot is always made implicitly and is
also saved.
7.2.4 Useful commands
sysconfig -av
sysconfig -t
reboot
136
show adapter
show tapes
reboot Filer
13 October 2006
Edition 7
Celerra
7.3 Celerra
7.3.1 Prerequisites
Tests were performed in the following system environment:
–
–
Celerra Datamover 507 with operating system versions DART 5.1.15.1 and DART
5.2.9.6
Connection of Celerra via FC switch
7.3.2 Restrictions
SW environment of CS: 818.204.
The data can only be saved via the “addr” designations of the connected devices, not via
the “name” designations. This is - regardless of CentricStor - currently a fundamental
restriction on the Celerra side. EMC is working to resolve this.
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 E32E130000000D000C 0?
On the Celerra Control Node the NDMP bufsz specified in
/nas/server/slot_<x>/param for the Datamovers connected to CentricStor may not be
set to more than 256.
In migrating from ONTAP 5.1 to ONTAP 5.2 the channel ID changed in the “addr” designation of the tape device node (example: device c80t0l13 became c64t0l13). Corresponding changes had to be made in NetWorker.
Edition 7
13 October 2006
137
Celerra
7.3.3 Configuration
CentricStor ICP
Emulation IBM 3590E or Mammoth 2
Recommendation: Compression by HOST
On the Celerra Control Node the following entries were included in
/nas/server/slot_<x>/param for DART 5.2.9.6 (support of NDMP Version 4 as default)
for the Datamovers connected to CentricStor:
param NDMP ntape=2
param NDMP bufsz=256
param PAX nbuf=8
!
IMPORTANT!
According to the Celerra manual these parameters must (!) be set. Following modification the relevant Datamover must be rebooted (e.g. with the command:
server_cpu server_<x> -reboot -monitor now).
Parameter NDMP ntape=2 allows the related Datamover to use 2 (virtual) tapes in parallel.
The default is 0 and the maximum value 8, i.e. up to 8 virtual tape devices can be used in
parallel per Datamover. The nbuf parameter must be set to four times the value of ntape, in
other words up to 32.
The bufsz value corresponds in NetWorker to the NSR_DEV_BLOCK_SIZE value for the
corresponding drive type. In NetWorker, the default block size for Mammoth 2 is 192. In
other words if you use the CentricStor Mammoth 2 emulation, bufsz must be set to 19 in the
relevant Celerra Datamover. If the 3590 emulation is used, then in contrast to the setting of
384 called for in the Celerra documentation, bufsz must be set to 256 and the entry
NSR_DEV_BLOCK_SIZE_3590=256 must be included in file /nsr/res/defaults on the
NetWorker server.
If the NDMP user is not present, a new user ndmp must be created on the Celerra Control
Node for each Datamover using:
/nas/sbin/server_user server_<x> -add -ndmp -passwd <password>
The <password> must then be used for NDMP configuration on the NetWorker server.
At least NetWorker 6.1A10 with EKS 1-5 for Solaris with DART 5.1.15.1
At least NetWorker 6.2 Build 109 on Windows with DART 5.1.15.1
At least NetWorker 7.1 with DART 5.2
138
13 October 2006
Edition 7
Celerra
We recommend that the timer should be set as for NetWorker (see section “Configuration
Configuration of the Celerra devices e.g. “c64t0l13” (cmp, norewind) as NDMP devices.
During a backup with NetWorker, no temporary snapshot is made implicitly. The current file
system status of a Datamover is saved.
Additional procedures must be added to use snapshots.
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
Edition 7
13 October 2006
139
by f.f. 1992
8 Tape management systems
8.1 NetWorker (Legato and FSC)
i
A list of the current qualified versions of ISV products is available on Internet from
the address:
http://www.CentricStor.de
8.1.1 Documentation
The CD from Legato contains help files and “man” files for all supported operating systems.
You are also referred to the Legato internet site.
8.1.2 NetWorker versions
CentricStor was tested with the following versions of FSC NetWorker:
Version
EKS
Host
5.5A30
1-4
Reliant UNIX
1, 3, 4
Solaris
5.5A40
-
Reliant UNIX
6.0A00
1
The definitive version of the STLI library (Silo Tape Library Interface) for ACI functions (AML
Client Interface) is libstlaci_310.so (see below: resource jukebox, Attribute STL
interface lib). This is supplied from NetWorker 5.5A30 EKS 4 onwards and is installed as
default under /opt/nsr/lib.
The DAS administration program Version 3.10 dasadmin_310 can be used to communicate with VDAS in CentricStor.
In this case export DAS_SERVER=<VLP-name> must be set.
Edition 7
13 October 2006
141
NetWorker (Legato and FSC)
Tape management systems
dasadmin_310 is supplied from NetWorker 5.5A30 EKS 4 onwards and is installed as
default under /opt/nsr.
As of NetWorker 6.0A00 EKS 1, libstlaci_310.so and dasadmin_310 are also
supplied by FSC EP ST SMS 4 (Storage Management Software NetWorker).
8.1.3 Configuration of the “CentricStor” library
–
Model: other STL or DAS Silo or ACSLS Silo. System dependent restrictions are
explained in section “System specific” on page 176.
–
Control Port: VLP host name type=3590 [client=<hostname>]
The IP address for the VLP host must be entered in the /etc/hosts. The client
parameter for high availability configurations can be used with IP aliasing.
–
Devices:
This correspond to the attribute name (see above), as in real operation in the resource
devices.
–
Eject sleep: 1 (guide value)
The default NetWorker value of 5 is unnecessarily high for operation with CentricStor
and can be reduced.
–
Unload sleep: 2 (guide value)
and can be reduced.
–
Load sleep: 1 (guide value)
and can be reduced.
–
Idle_device_timeout: 1
–
STL device names:
STL device names refer to the ID used to address the logical device via the library path
(i.e. the LibDevName from column 7 Section [ ld ] in the configuration file
/usr/apc/conf/vtls.conf on the VLP host). This data is shown in the graphical
user interface in table form under:
[GXCC Function bar tools ➔ Global Status ;] Function bar tools ➔
Show Balloon Help Summary ()
or in Global Status with balloon help for individual virtual devices.
Example: VDAS device names D104
142
13 October 2006
Edition 7
Example: VACS device names 2,0,0,6 (corresponding to LibDevName 2-0-0-6 (see
below) coordinates for VACS devices).
As with real operation, the STL device names must be entered exactly in the sequence
of device attribute assignment (see above).
–
STL interface lib:
/opt/nsr/lib/libstlaci_310.so (see NetWorker version above) for virtual ADIC
robot (VDAS).
/opt/nsr/lib/libstlstk.so for virtual STK robot (VACS).
If the NetWorker programs are not installed as standard, i.e. under /opt/nsr, the lib
path name must be adapted accordingly.
Miscellaneous
Edition 7
–
VDAS_TIMEOUT_MOVE
A mount request in CentricStor (vlm) is timed out by VDAS using the
VDAS_TIMEOUT_MOVE timer (default 100 minutes; this can be set in the CentricStor
configuration file section [ vls ] ). A timer set with the DAS environment variable
ACI_TIMEOUT_MOVE (default 1800 seconds) also runs on the client side
(dasadmin_301). This timer should always be set to a higher value than
VDAS_TIMEOUT_MOVE !
The inactivity timeout must also be set as appropriate in the NetWorker resource groups
(default 30 minutes).
The high default value of 100 minutes for VDAS_TIMEOUT_MOVE takes account of the
maximum restore times for physical cartridges.
–
ACSLS_SERVER for VACS
The following must be set in /etc/default/nsr or - from NetWorker V6 - in
/etc/res/defaults:
ACSLS_SERVER=<VLP host name>.
The IP address of the VLP host must be entered in /etc/hosts.
–
Coordinates for VACS devices
In the /usr/apc/conf/vtls.conf configuration file on the VLP host, the virtual
drives allocated to the VACS have a LibDevName in the form w-x-y-z, where w, x, y and
z are decimal numbers between 0 and 255 (see STL device names above).
–
Administration program cmd_proc for STK robot systems
As with the ACS library software (ACSLS) with the ACS system administrator (ACSSA)
of a real STK robot archive system, the virtual ACS (VACS) of CentricStor has an
administration interface or a user interface. See README file of the administration tool
/usr/apc/doc/LIESMICH.cmd_proc on the VPL host.
13 October 2006
143
–
Large number of devices
If there is a large number of devices configured in NetWorker, devices must be disabled
if such a number is not actually needed (fewer running nsrmmd daemons for device
support).
In order to save internal NetWorker resources with a large number of devices (remote
nsrmmds) the Nrsrmmd polling interval in the resource server can be increased (default
10 seconds, give value 20).
–
Following ICP reboot
Volumes mounted in logical devices are discarded following an ICP reboot, so that
NetWorker outputs a warning with the next device access, e.g. a dismount (nsrd:
media warning: /dev/... opening: I/O error ; nsrjb: read open error,
I/O error).
–
Cleaning: does not occur
The logical devices do not support cleaning cartridges.
–
Options element status:
In order to use the function “nsrjb -E” (element status), the “Element Status” field
in the jukebox resource should be set using the “Jukebox Options”. However, this is
NOT set by default after configuration of the library with “jbconfig”.
i
In versions of NetWorker before V6, we recommended that you set the following
variables, as otherwise the drives are often set to disabled:
NSR_STL_PARALLEL_OPTIONS=NO
(no parallel mount)
When tapes are closed the following message may be issued:
i
nsrd: media notice: Volume ... on device ....: Block size 32768 bytes
not 196608 bytes. Verify the device configuration. Tape positioning by
record is disabelt
Correct tape processing is not impaired by this. The problem has been fixed in FSCNetWorker V7.1.
144
13 October 2006
Edition 7
Restrictions
The import/export of logical volumes is not supported.
Jukebox configuration settings:
Edition 7
type:
NSR jukebox;
name:
stk_pow;
description:
;
model:
EXB-10i EXB-10e/EXB-10h EXB-120 EXB-210 EXB-400 Series
EXB-X80 EXB-X200 HP-C1553A HP optical LMS Magstar
Magstar-MP DLT-4700 STK-9710 ACL Overland-LXB Emass
AML/S
Faststor Scalar 100 Standard SCSI Jukebox 3494 Cashion ABBA
ABBA 3490 ABBA 8mm ABBA optical [STK Silo] other STL
SmartMedia ;
enabled:
[Yes] No ;
control port:
HASE-VLP;
devices:
/dev/iof0/rstape.14.933ba.1chn, /dev/iof0/rstape.14.933bachn,
/dev/iof0/rstape.14.933ba.2chn, /dev/iof0/rstape.14.933ba.3chn,
"rd=lieser:/dev/rmt/57cbn", "rd=lieser:/dev/rmt/58cbn",
"rd=lieser:/dev/rmt/63cbn", "rd=lieser:/dev/rmt/64cbn";
bar code reader:
[Yes] No ;
match bar code
labels:
Yes [No];
available slots:
1-200;
STL device names:
"1,0,0,1", "1,0,0,0", "1,0,0,2", "1,0,0,3", "1,0,0,4", "1,0,0,5",
"1,0,0,6", "1,0,0,7", "1,0,0,8", "1,0,0,9", "1,0,0,10", "1,0,0,11",
"1,0,0,12", "1,0,0,13", "1,0,0,14", "1,0,0,15";
STL device sharing:
;
STL interface lib:
/opt/nsr/lib/libstlstk.so;
SRS server:
;
auto clean:
Yes [No];
cleaning slots:
;
default cleanings:
5;
13 October 2006
145
auto media
management:
[Yes] No ;
application name:
;
application key:
;
read hostname:
colorado;
NDMP jukebox:
Yes [No];
NDMP Type:
Standard NDMP NetApp ;
NDMP hostname:
;
remote user:
;
password:
;
NDMP jukebox
handle:
;
NDMP bus number:
;
NetWorker is configured using an alphanumeric or graphical interface. The examples in the
following figures show both variants.
146
13 October 2006
Edition 7
The following figure shows the default settings (the alterations for CentricStor are marked
in red):
Edition 7
13 October 2006
147
The following figure shows the settings of the jukebox properties made via the graphical
interface.
If the data, which is to be backed up, is already highly compressed, you can improve performance by using a non-compressing device node in NetWorker. In Windows there are
special settings (see section “System specific” on page 156).
i
148
After setting up or modifying a silo - especially after removing devices - it is best to
ensure that the hidden attributes in the resource silo, “device number” and “drive
number” are identical.
(Note: There is likely to be an improvement in FSC-NetWorker from version 6.1A10
onwards).
13 October 2006
Edition 7
8.1.4 Configuration of virtual devices (NetWorker resource devices)
Further system-specific settings are given in page 156.
–
Name:
NetWorker does not, of course, recognize the physical devices in the real robot on
CentricStor. The pathnames of the device nodes in the resource devices (and resource
jukebox; see below) relate to the logical devices in CentricStor.
In UNIX, Linux, AIX, and Reliant-Unix systems we strongly recommend that you do not
use the original device nodes in applications such as Networker and do not use the links
created by the system itself. Instead, use the links with uniform CentricStor names
which refer to the original device nodes.
Example:
NetWorker backup node 1 on RM600
NetWorker backup node 2 on Primepower
Link to Reliant UNIX device nodes
Link to Solaris device nodes
...
-
-
...
...
-
-
...
The “no rewind function” characteristic (descriptor n) is mandatory for NetWorker, as in
real operation.
Edition 7
13 October 2006
149
The BSD option (explicit descriptor b for Solaris) is mandatory for NetWorker, as in real
operation.
Data compression by CentricStor can be activated (descriptor c) provided appropriate
data compression exists.
Other device characteristics, such as high data density (descriptor h), are not
supported.
–
Media family: tape
–
Media type: generic256
In NetWorker V6.0A00 and later, the attribute assignment generic256 is only made
visible with NSR_SHOW_GENERIC=1 in /nsr/res/defaults. In the case of an update
installation, the automatic conversion of generic256 to 8mm 5GB must be avoided by
setting export NSR_SHOW_GENERIC=1 before the installation or by making the entry
in /nsr/res/defaults before the first NetWorker start.
–
Volume default capacity: 895 MB
The default NetWorker value of 2 GB for generic 256 must be reduced to 895 MB for a
suitable capacity display of logical volumes. The value must be set before tape installation in order to be effective.
–
Further recommendations:
If the data which is to be backed up is already highly compressed, you can improve
performance by using a non-compressing device node in NetWorker. In Windows there
are special settings (see section “System specific” on page 156).
8.1.4.1
ACSLS interface
NetWorker currently only supports one ACSLS server. Thus a NetWorker server cannot
control a real robot and CentricStor simultaneously. From version V6.1 onwards the FSC
NetWorker can address several ACSLS servers.
Details about the possible causes of connection problems with VACS and troubleshooting
advice is given in section “Possible problems and troubleshooting advice” on page 276.
150
13 October 2006
Edition 7
8.1.4.2
DAS interface
Before you can work with this interface, you must authorize access to the drive via DAS with
the command:
dasadmin alloc <virt. drive> UP <Client>
Details about the possible causes of connection problems with VDAS and other troubleshooting advice is given in section “Possible problems and solutions” on page 271.
Access to the virtual drive and to the planned volume number area must be permitted for
the client in CentricStor. These assignments are made within the framework of the
CentricStor configuration by the service engineer.
8.1.4.3
Scratch mount support
As NetWorker does not communicate this to CentricStor via supported standard interfaces
when using an LV only to write (SCRATCH-MOUNT):
VDAS/DAS aci_scratch_set
VACS/ACSLS csc_set_scratch
a template can be used on UNIX machines, the so-called prerecycle script. This is made
available by the FSC NetWorker development department
ftp://ftp.fujitsu-siemens.com/pub/nsr/add-on (it is called nsr_CS_prerecycle.sh) or is
supplied with FSC NetWorker V 7.1 or higher.
In FSC NetWorker the scratch functions for VACS and VDAS are new in Version 7.2. FSC
NetWorker 7.2 performs the scratch mount only when a tape is recycled (i.e. only in the
event of an “nsrjb -R” or an automatic recycle).
In CentricStor the scratch function for VACS is already available in V2.1 and the scratch
function for VDAS is new in Version 3.1B.
To permit use of the scratch mount with FSC NetWorker 7.2, the user must enter the corresponding library for the “jukebox” resource (query when setting up the silo of jbconfig):
VACS: /opt/nsr/lib/libstlstk_cs.so
VDAS: /opt/nsr/lib/libstlaci_cs.so
i
Edition 7
(Default: /opt/nsr/lib/libstlstk.so)
(Default: /opt/nsr/lib/libstlaci_310.so)
NetWorker cannot use the feature “Post Disaster Recovery Scratch Volume Processing” (for the first time in K835.7: the physical tape acess is avoided after disaster
recovery in the case of a scratch mount through a configurable, predefined label
which the VLM writes): A NetWorker label contains not only the barcode but also a
volume ID. This ID is assigned by the NetWorker server. This ID is generated from
several parameters, e.g. from the server’s IP address and the timestamp. The volume ID is checked when relabeling takes place. If it does not match the value in the
media DB the volume is not relabeled.
13 October 2006
151
8.1.4.4
Changing from NetWorker 5.5 to 6.1...
Changing from NetWorker 5.5 to NetWorker 6.1... makes no difference to CentricStor itself.
Within NetWorker the following points must be noted.
1. The index is converted and it is therefore no longer possible to return from NetWorker
6 to 5.
2. In 5.5 CentricStor devices of type generic256 were in use.
Caution: in an update installation to 6.0A00 it is converted by default to 8mm GB!
The conversion to type 8mm GB can be avoided, if
export NSR_SHOW_GENERIC=1
is set before the installation, or an entry is made in /nsr/res/defaults before the
first NetWorker start.
3. It is advisable to change the device type from generic256 to CentricStor. (The “old”
generic256 type volumes are compatible with the new CentricStor type, i.e.they can be
read, written and recycled).
4. NetWorker does not allow a subsequent device type change.
There is no automatic conversion of device types. To avoid the expense of deleting
devices in resource jukeboxes and resource devices and then re-entering them, use the
following tip:
–
–
–
–
Close NetWorker
Make a backup copy of nsr.res
Edit nsr.res: change media type from “generic256” to “CentricStor”
Start NetWorker again.
If you have any problems, you can get help from NetWorker support.
5. Another tip: Jukeboxes/Silos can no longer be defined in the GUI in V6...., but only with
CLI jbconfig (as in Legato NetWorker).
Instead of Model other STL, Model DAS_SILO or ACSLS_Silo is now entered.
152
13 October 2006
Edition 7
8.1.5 Configuring a jukebox in NetWorker on Solaris
The device nodes in Solaris must have the same numbers in the NetWorker jukebox as the
virtual drives in the associated VJUK emulation of CentricStor.
Sample configuration
ICP0 : 32 virtual drives V000 through V01F
ICP2 : 1 jukebox controller VJ01 and 32 virtual drives V200 through V21F
The target controllers in the ICPs have the following target IDs on the Solaris host via
persistent binding:
ICP2 : Target ID 53 (hex 35)
ICP0: Target ID 54 (hex 36)
Configuration steps:
1. Creation of an assignment list for virtual drives and slot numbers in
CentricStor (vjukadmin <JUKBOX-NAME> inventory drives)
2. Listing all Solaris device nodes which are to be configured in the jukebox
(Networker command inquire on the host)
3. Configuration of a jukebox using the NetWorker command jbconfig
!
CAUTION
The slot numbers in CentricStor are displayed by vjukadmin in hexadecimal
format. jbconfig of NetWorker displays these in decimal format (decimal 256
= hexadecimal 100).
1. Configuration step
Information as per vjukadmin in CentricStor:
VLP0 (VLP0_KAUZ)# vjukadmin VJ01 set offline
Jukebox VJ01 set to offline
VLP0 (VLP0_KAUZ)# vjukadmin VJ01 inventory drives
INQUIRY-DATA:
SLOT
DRIVE
VSN
0100
V000
0101
V001
...
011E
V01E
011F
V01F
0120
V200
0121
V201
...
013E
V21E
013F
V21F
-
Edition 7
13 October 2006
153
Information as per NetWorker command inquire on the Solaris host:
bash-2.05# inquire
[email protected]:FSC
CS-TL
CentricStor
CentricStor
...
CentricStor
CentricStor
CentricStor
CentricStor
...
S/N: 0000000D001E
S/N: 0000000D001F
83.7|Autochanger (Jukebox)
S/N: 0C00000D0200
83.6|Tape, /dev/rmt/1cbn
S/N: 0000000D0201
S/N: 0000000D0202
S/N: 0000000D021F
S/N: 0000000D0220
S/N: 0000000D0000
S/N: 0000000D0001
CentricStor
CentricStor
Dem virtuellen Drive V000 im CentricStor entspricht der Solaris-Geräteknoten
CentricStor
S/N: 0000000D0000
NetWorker command jbconfig on the Solaris host:
bash-2.05# jbconfig
1) Configure an AlphaStor/SmartMedia Jukebox.
2) Configure an Autodetected SCSI Jukebox.
3) Configure an Autodetected NDMP SCSI Jukebox.
4) Configure an SJI Jukebox.
5) Configure an STL Silo.
What kind of Jukebox are you configuring? [1] 2
Installing 'Standard SCSI Jukebox' jukebox - [email protected].
What name do you want to assign to this jukebox device? MYJUK
Should the jukebox use SRS managed devices? (yes/no) no
Turn NetWorker auto-cleaning on (yes / no) [yes]? no
The drives in this jukebox cannot be auto-configured with the available
information. You will need to provide the path for the drives.
154
13 October 2006
Edition 7
Is (any path of) any drive intended for NDMP use? (yes / no) [no]
Please enter the device path information in one of the following formats:
/dev/rmt/1cbn --for local path or
host:device-path --for remote node or
host:drive-letter:directory path --for Windows disk file
Drive 1, element 256
Drive path ?
/dev/rmt/33cbn
Drive 2, element 257
Drive path ?
/dev/rmt/34cbn
.
Further information on NetWorker
●
The default setting in lus.conf must be checked and increased if you wish to
configure more LUNS in NetWorker.
Example
For Emulex LP9 (default 32 LUNS pci10df,f900:126-32C), increase to 64 LUNS
pci10df,f900:126-128C (A0517437).
●
For CentricStor the CDI option should be set to “not used” in accordance with the
recommendation of FSC NetWorker QA. The default setting CDI SCSI commands has
to date resulted in the following being reported in the NetWorker daemon log:
nsrd: media notice: Volume "Sxxxxx" on device "/dev/rmt/1bn":
Block size is 32768 bytes not 262144 bytes. Verify the device
configuration. Tape positioning by record is disabled.
●
In the load test with NetWorker and VJUK, the following message often occurred in the
NetWorker daemon log:
nsrd: Jukebox
'VJnn' failed: get_elements_st: acquisition of locks failed
The message can be ignored:
Here the element status in the SCSI jukebox is not fetched. In other words there is no
CentricStor VJUK-specific error message, but it is information resulting from internal
NetWorker processes with a high level of parallelism.
8.1.6 Prefetch with FSC NetWorker
FSC NetWorker supports the prefetch topic in CentricStor Version V2.1 from Version
6.1A10 onwards.
Restriction: The NetWorker solution does not support several CentricStor silos.
Edition 7
13 October 2006
155
8.1.7 Tips and tricks
Error message: “ALL of the devices are in busy by nsrmmd”
After setting up or modifying a silo - especially after removing devices - it is best to ensure
that the hidden attributes in the resource silo, “device number” and “drive number” are
identical. (Note: It is likely that an improvement to FSC-NetWorker will be introduced from
version 6.1A10).
8.1.8 System specific
8.1.8.1
156
Windows NT 4.0
●
When using the ACSLS interface, the software product “LibAttach” from StorageTek
must be used.
●
If the data which is to be backed up is already highly compressed, you can set the
variable “NOR_NO_HW_COMPRESS=yes” to switch off compression in the device
emulations in CentricStor and thus achieve higher performance.
●
With Legato NetWorker and EXBYTE Mammoth2 devices, the following messages may
come through NetWorker:
nsrd: media…notice: Volume … on device …: Block size 32768 bytes not
196608 bytes. Verify the device configuration. Tape positioning by
record is disabled.
However, this does not disturb correct tape processing. The problem is eliminated in
FSC NetWorker.
●
NetWorker settings for Windows NT 4.0:
media type
8mm Mammoth-2
Device Nodes
\\.\Tape* (* = 0, 1, ... 10, 11, 12)
with ACSLS robot control model
ACSLS SILO
STL interface lib
libstlstk.dll
with DAS robot control model
DAS Silo
STL interface lib
libstlemass.dll
drive emulation
EXABYTE/Mammoth2
13 October 2006
Edition 7
8.1.8.2
Windows 2000
●
must be used. The product for Windows NT 4.0 can be used.
●
When using the DAS interface, the variables DAS_SERVER and DAS_CLIENT must be
defined as system variables under: Start -> Settings -> Control Panel. In the control
panel select the entry System (System Properties). In System Properties, click the
“Advanced” tab. In the center you will find a button called “Environment Variables”.
●
If the data which is to be backed up is already highly compressed, you can set the
variable “NSR_NO_HW_COMPRESS=yes”, to switch off compression in the device
emulations in CentricStor and thus achieve higher performance.
●
With Legato NetWorker and EXBYTE Mammoth2 devices, the following messages may
come through NetWorker:
nsrd: media…notice: Volume … on device …: Block size 32768 bytes not
196608 bytes. Verify the device configuration. Tape positioning by
record is disabled.
However, this does not disturb correct tape processing. The problem is fixed in FSC
NetWorker.
●
When using Legato NetWorker on Windows 2000, the following message is sometimes
given by nsrmmd without any function problems: “tape_bsf failed: Device must
be cleaned”. This behavior is specific to CentricStor. The message section “Device
must be cleaned” is a reaction to the Windows operating system.
●
NetWorker settings for Windows 2000:
media type
8mm Mammoth-2
Device Nodes
\\.\Tape*
STK Silo
STL interface lib
libstlstk.dll
STL interface lib
drive emulation
Edition 7
EXABYTE/Mammoth2
13 October 2006
157
●
8.1.8.3
VJUK settings
Application
LEGATO NetWorker 7.1.2
Platform
Windows 2000 SP4 5.00.2195
Jukebox type in CS
FSC CS-TL
Tape device type in CS
EXABYTE: Mammoth2
Jukebox type in application
Autodetected SCSI jukebox or standard SCSI
jukebox (jbconfig entry)
Media type in application
Mammoth2
Max. volume number per
jukebox in application
2.001 (with more than approx. 2001 slots+drives
jbconfig aborts with Failure 0x29 unknown
error)
Reliant UNIX
●
When using the ACSLS interface, the file: /etc/default/nsr from theVACS server
should be entered. As of V6, the file: /etc/res/defaults is used. Example:
ACSLS_SERVER=HASE-IDP1
●
NetWorker settings for Reliant UNIX:
media type
generic256
Device Nodes
/dev/iof0/rstape.*cn
c = optional compression
with ACSLS robot control model STK Silo
158
STL interface lib
libstlstk.so
other STL or DAS Silo
STL interface lib
libstlaci_310.so
drive emulation
FSC/CentricStor
13 October 2006
Edition 7
8.1.8.4
Solaris
●
For NetWorker, the nodes with the modifier “b” (e.g. /dev/rmt/8bn) must always be
used. The “b” selects the so-called BSD behavior (no implicit space operation on close,
(see man st; man mtio), to which NetWorker is set. If you take a node without “b”,
NetWorker will have to keep dealing with positioning problems (visible in daemon.log).
When the “Mammoth2 emulation” is used the following settings should be made in the
st.conf file:
"EXABYTE Mammoth2",
....
EXB-M2
= 1, 0x35,
"Exabyte Mammoth2 8mm Helical Scan","EXB-M2";
0, 0x3de39, 1, 0x28, 0;
If SRS is used, the SCSI reserve/release (0x20000, ST_NO_RESERVE_RELEASE) is
disabled in the option field.
The following values apply without SRS:
"EXABYTE Mammoth2",
....
EXB-M2
= 1, 0x35,
●
"Exabyte Mammoth2 8mm Helical Scan","EXB-M2";
0, 0x1de39, 1, 0x28, 0;
When using the ACSLS interface, the file: /etc/default/nsr from the VACS server
should be entered. From V6 onwards, the file: /etc/res/defaults is used.
Example: ACSLS_SERVER=HASE-IDP1
●
Edition 7
NetWorker settings for Solaris:
media type
generic256
Device Nodes
/dev/rmt/*cbn
STK Silo
STL interface lib
/opt/nsr/libstlstk.so
other STL or DAS Silo
STL interface lib
/opt/nsr/libstlaci_310.so
drive emulation
FSC/CentricStor
13 October 2006
c = optional
compression
159
●
8.1.8.5
160
VJUK settings
Application
FSC NetWorker 7.1 EKS 1-3
Platform
Solaris 9
Jukebox type in CS
FSC CS-TL
FSC: CentricStor
Autodetected SCSI jukebox or standard
SCSI jukebox (jbconfig entry)
CentricStor
Max. number of volumes per jukebox in
application
60,000
HP-UX
●
8.1.8.6
NetWorker settings for HP-UX:
media type
8mm Mammoth-2
Device Nodes
/dev/rmt/c*t0d*BESTnb
STK Silo
STL interface lib
/usr/lib/libstlstk.sl
DAS Silo
STL interface lib
/usr/lib/libstlemass.sl
drive emulation
EXABYTE/Mammoth2
IBM-AIX
●
Does not support DAS robot control.
●
NetWorker settings for IBM-AIX:
media type
8mm Mammoth-2
Device Nodes
/dev/rmt*.1
ACSLS_SILO
STL interface lib
/usr/lib/libstlstk.so.a
drive emulation
EXABYTE/Mammoth2
13 October 2006
Edition 7
Example:
Extension of the rc.nsr start file:
# Start of lines added by NetWorker - DO NOT DELETE OR CHANGE THIS
LINE
# installed by nsr_ize on Mo 17 Dez 16:14:53 2001
#
# Default locale
#
LANG=C
export LANG
# Override to a different locale if /usr/lib/nsr/LANG exist
[ -r /usr/lib/nsr/LANG ] && . /usr/lib/nsr/LANG
# make tape devices available - begin
for rmt in rmt12 rmt13 rmt14 rmt15 ; do
mkdev -l $rmt > /dev/console 2>&1
done
# make tape devices available - end
# StorageTek silo interface - begin
CSI_HOSTNAME=HASE-IDP1
export CSI_HOSTNAME
(/usr/bin/mini_el) > /dev/console 2>&1 &
(/usr/bin/ssi) > /dev/console 2>&1 &
# StorageTek silo interface - end
(
echo 'starting NetWorker daemons:') > /dev/console
if [ -f /bin/nsrexecd ]; then
(/bin/nsrexecd) > /dev/console 2>&1
(echo ' nsrexecd') > /dev/console
fi
if [ -f /bin/lgtolmd ]; then
(/bin/lgtolmd -p /nsr/lic -n 1) > /dev/console 2>&1
(echo ' lgtolmd') > /dev/console
fi
if [ -f /bin/nsrd -a ! -f /bin/NetWorker.clustersvr ]; then
(/bin/nsrd) > /dev/console 2>&1
(echo ' nsrd') > /dev/console
fi
# End of lines added by NetWorker - DO NOT DELETE OR CHANGE THIS LINE
Edition 7
13 October 2006
161
8.1.8.7
Linux
●
When using the CentricStor emulation EXABYTE/Mammoth2:
FSC NetWorker from 6.1A00 EKS1-6 or from V6.1A10 with media type 8mm
Mammoth2 is to be operated on the Linux host, where the “volume default capacity” in
the NetWorker resource devices is to be set to 895 MB.
●
When using the CentricStor emulation FSC/CentricStor:
FSC NetWorker from 6.1A00 EKS1-6 with media type CentricStor is to be operated on
the Linux host, where the “volume default capacity” in the NetWorker resource devices
is already 895 MB by default.
NetWorker settings for Linux:
media type
CentricStor
Device Nodes
/dev/nst0...1
ACSLS_Silo
STL interface lib
/opt/nsr/lib/libstlstk.so
model DAS_Silo
STL interface lib
/opt/nsr/lib/libstlaci_310.so
drive emulation
FSC/CentricStor
1
162
NetWorker only supports non-rewind devices.
13 October 2006
Edition 7
NetBackup (Veritas)
8.2 NetBackup (Veritas)
Currently only the NetBackup Data Center product supports the connecting of robots via
LAN.
8.2.1 Documentation
NetBackup documentation
Version
Release Notes Veritas NetBackup
3.4
Release Notes Veritas NetBackup
3.4.1
Installation Guide Veritas NetBackup BusinesServer
3.4.1
System Admistrator’s Guide Veritas NetBackup DataCenter for UNIX
3.4
User’s Guide Veritas NetBackup for UNIX
3.4
Installation Guide Veritas NetBackup DataCenter for UNIX
3.4
Media Manager System Admistrator’s Guide Veritas NetBackup
DataCenter for UNIX
3.4
Media Manager Device Configuration Guide Veritas NetBackup for UNIX 3.4
User’s Guide Veritas NetBackup for Microsoft Windows 95/98/NT/2000
3.4
Troubleshooting Guide Veritas NetBackup for UNIX
3.4
Installation Guide Veritas NetBackup BusinesServer for PC Clients
3.4
As of Version 4.5 there are no further printed editions. The manuals are available on CDs
or on the Internet at:
http://www.veritas.com
8.2.2 Installation
Example from Solaris
Edition 7
–
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’.
13 October 2006
163
NetBackup (Veritas)
8.2.3 Configuration
●
Configuration tool ( X): xbpadm.
●
Storage Units must be configured first, then the devices.
●
The device nodes must be “cbn nodes”:
c = optional compression.
b = BSD option which is needed explicitly for Solaris.
●
Classes must be defined for the backup jobs.
Notes / Features
164
●
NetBackup works with standard Unix tape access: mt / tar.
●
From Version 4.5 the term “Class” is no longer used and is now interpreted as “Policy”.
●
st.conf on Solaris must be adapted appropriately for CentricStor (see above).
●
On Solaris, the “sg” driver from Veritas must also be installed. See: “Media Manager
Device Configuration Guide” from Veritas.
●
There are problems with the Java user interface. xbpadm (X-Tool) is recommended as
a replacement.
●
‘/opt/openv/volmgr/bin/robtest’ for diagnosing devices and acs interface
(see System Administrator’s Guide, Appendix B, Robotic Test Utilities)
●
In the NetBackup ‘inventory’, VACS only returns tapes which are already known to
VACS or have already been accessed.
●
In supporting ACS robot interfaces, ensure that only up to 20 spaces for drives are
supported per panel. This restriction must be observed in the configuration of a virtual
drive in CS. The drive coordinates are stated in the form:
ACS(0-126)-LSM(0-23)-Panel(0-19)-Drive(0-19). The numbers in brackets state the
permitted values where only the values 0-11 can be used for NetBackup in drives. This
must be followed in the definition of virtual drives in CentricStor.
●
When using the DAS Robot interface, you must ensure that in NetBackup V3.4 only the
first 15 DAS drives are supported. As of NetBackup Version V4.5, up to 250 drives are
supported.
●
No additional modules are needed to support robot interfaces ACS and DAS. Windows
is an exception (see section “System specific” on page 176).
13 October 2006
Edition 7
8.2.3.1
NetBackup (Veritas)
●
It is recommended that you do not configure the same device (virt. device in
CentricStor) in several NetBackup systems. If the same device is under robot control in
parallel NetBackup servers, it can be disturbed by SCSI commands. Where necessary,
set the device to the NetBackup device status “DOWN” in the parallel system.
●
Before you can work with the DAS interface, you must authorize access to the drive via
DAS with:
“dasadmin alloc <virt. drive> UP <client>” DASADMIN is not shipped with NetBackup
and must be purchased separately.
●
Details about the possible causes of connection problems with VDAS or VACS and
other troubleshooting advice is given in sections “Possible problems and solutions” on
page 271 (VDAS) or page 276 (VACS).
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 CentricStor has been specified: yin. For everything else the
default has been accepted.
Modifying the system parameters
network service name(or port number)[lmf](the name is defined in "/etc/services",q)>
the name of the server host(host name,q)[server01]>
the node name of the server host(the name is defined in "/etc/hosts",q)[yin]>yin
yin will be set
another node name(or IP address) of the server host(the name is defined in
"/etc/hosts"(set space for delete),q)>
security management of volume load authority[disable](1.disable,2.enable,q)>
1.modify the system parameters
2.get library parameters from server
3.modify library parameters
4.modify drive parameters
5.display all parameters
e.end
Please select a function. (1-5,e)>2
Edition 7
13 October 2006
165
NetBackup (Veritas)
Set library parameters by the LMF environment file of the server
Get library parameters from server
Following library or drive parameters will be added
library ID
= 0000
library name[LibCS](alphanumeric less than 8 characters,q)>
drive type(V000)[128track](1.128track,2.36track,3.18track,q)>1
special file of drive(V000)(128track)[no special file](0-99,n.no special file,q)>
.....
i
The drive types are inquired for each library (for each ICP). Here you must note
which ICP the displayed drives belong to.
Netbackup configuration is implemented as for Windows 2000. The administration
console is started with xvmadm. From here you go via the file menu to the Device
Management. Robots and drives are configured there.
As of Version 4.5 the Motif interfaces xbpadm, xbpmon, xvmadm and xdevadm are no
longer supported. The Java interfaces jnbSA and jbpSA are recommended, and also
the command line and the menu-based program bpadm.
The following processes must run on the LMF client (the programs vmps and bpps
belong to Netbackup):
bash-2.03# vmps
root 5329
1 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#
166
13 October 2006
Edition 7
8.2.3.2
NetBackup (Veritas)
Connection of the robot controller (VACS) via a firewall
From the current version of NetBackup on, connection of the ACSLS robot controller is
supported via a firewall.
NetBackup V5.0 and service release 3 (available on the Internet at:
http://support.veritas.com) were used under Solaris for quality assurance.
The robot name configured in NetBackup must be determined before configuration takes
place:
/opt/openv/volmgr/bin/tpconfig
-> 2) Robot Configuration
-> 4) List Configuration
Currently defined robotics are:
ACS(0) ACSLS server = 172.25.95.166
The following variables must then be set on the NetBackup server in the file
/opt/openv/volmgr/vm.conf.
Syntax: ( variable = robot name port)
ACS_TCP_RPCSERVICE
ACS_CSI_HOSTPORT = 172.25.95.166 2001
ACS_SSI_INET_PORT = 172.25.95.166 2001
In CentricStor the fixed port is defined as follows:
GXCC -> Configuration -> VirtualLibraryService ->
VACS : RPC-Port Selection UserDefined
RPC-Port:
!
Edition 7
2001
Caution!
Communication is still handled via RPC!
Port 111/UDP may not be locked.
13 October 2006
167
NetBackup (Veritas)
8.2.3.3
Template for supporting SCRATCH mount
When using an LV just for writing (FAST-MOUNT) Netbackup does not communicate this to
CentricStor™ over the supported standard interfaces:
VDAS/DAS
VACS/ACSLS
aci_scratch_set
csc_set_scratch
Instead of this, the following template can be used on UNIX systems.
#!/bin/sh
#----------------------------------------------------------------------#
Example of fast access to (=recycle) volumes
#----------------------------------------------------------------------HOST=yin
VSNList=`/usr/openv/netbackup/bin/admincmd/bpmedialist -l | \
/usr/bin/awk '{print $11, $1}' | \
/usr/bin/egrep '^0' | \
/usr/bin/awk '{print $2}'`
for VSN in $VSNList
do
rsh $HOST /usr/apc/bin/vlmif conf -r -n -v $VSN
done
This script truncates the LV to the part which is always contained in the cache, so no restore
is required in the event of the next mount.
In newer versions of NetBackup the following template can be used:
set +vx
TZ=GMT-26
# set time + 24 h
HOST1=CS1
HOST2=CS2
DATE=`date +%m/%d/%Y`
# will be the next day in the script shell
TZ=Europe/Berlin
# Find tape (LV) which expire today in the media DBD's
/usr/openv/netbackup/bin/admincmd/bpmedialist -summary | /usr/bin/grep $DATE
| awk '{print $1}' | sort -u >/tmp/list # list of LVs which expire tomorrow
# Reset der VSN's
/usr/bin/cat /tmp/liste | while read VSN1
do
rsh -n $HOST1 /usr/apc/bin/vlmif conf -r -n -v $VSN1
done
168
13 October 2006
Edition 7
8.2.3.4
NetBackup (Veritas)
Sample screens
Overview:
Edition 7
13 October 2006
169
NetBackup (Veritas)
Main screen:
170
13 October 2006
Edition 7
NetBackup (Veritas)
Define Storage Unit:
Edition 7
13 October 2006
171
NetBackup (Veritas)
Add New Unit:
172
13 October 2006
Edition 7
NetBackup (Veritas)
Configure Devices:
Edition 7
13 October 2006
173
NetBackup (Veritas)
Configured Classes:
174
13 October 2006
Edition 7
NetBackup (Veritas)
Monitoring:
Edition 7
13 October 2006
175
NetBackup (Veritas)
8.2.4.1
Windows NT 4.0
●
NetBackup Datacenter from Version 3.4.1.
●
The NetBackup Datacenter Patch NB_341_2 must be used.
●
Only supports ACSLS robot control.
●
must be used.
●
VERITAS recommends the 3590E emulation.
●
NetBackup Datacenter 4/3/01
Sometimes the event log records event 4118: “Cannot read Volume header on
drive x (device y, \\.\Tape z); retrying ... ”. The label is written with
block length HEX 400, but is read with HEX 8000. Thus there is no functional restriction
on the Backup/Restore.
NetBackup/NT configuration setting:
Drive type
½“ cartridge (hcart)
media type
HCART
Device node (no
rewind device)
Tape0, Tape1, ...
with ACSLS robot
control, robot type
ACS automated cartridge
system
ACSLS host
Name of the host where IP address: in
VACS is running (normally Winnt\system32\drivers\etc\hosts
the name of the VLP)
drive emulation
EXABYTE/Mammoth2
or
alternative emulation
176
IBM/IBM 03590E1A
13 October 2006
Driver: Mammoth2 V2.10 from
EXABYTE
Driver: halfinch.sys from VERITAS
file version 5.00
Caution: the halfinch driver can
only be installed after installing
NetBackup.
Edition 7
●
NetBackup (Veritas)
Additional parameter settings (for example values, adapt as necessary)
NetBackup admin ➔ configure NetBackup:
8.2.4.2
●
Master Server, right click ➔ Properties ➔
Universal settings: logging enabled; logging level=10
Global NetBackup attributes: maximum jobs per client=20
●
Media Server, right click ➔ Properties ➔
●
Clients, right click ➔ Properties ➔
●
Storage unit management ➔ Storage Unit Properties:
maximum concurr. Drives for backup=8
maxim. Multiplexing per drive=2 (1 to 32; default 1)
●
Backup policy management ➔ class double-click:
limit jobs per class= 99 explicit (=default?)
Schedules ➔ Schedule double click ➔ media multiplexing=2
(1 to 32; default 1)
Caution: Multiplexing increases restore time.
Windows 2000
●
●
●
Only supports ACSLS robot control.
●
●
VERITAS recommends the 3590E emulation.
●
NetBackup Datacenter 4/3/01
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.
Edition 7
13 October 2006
177
NetBackup (Veritas)
Configuration settings NetBackup/Windows:
8.2.4.3
Drive type
media type
HCART
Device node (no
rewind device)
Tape0, Tape1, ...
with ACSLS robot
control: robot type
ACS automated cartridge
system
ACSLS host
Name of the host where IP address: in
VACS is running (normally Winnt\system32\drivers\etc\host
the name of the VLP)
s
drive emulation
EXABYTE/Mammoth2
Driver: Mammoth2 V2.10.0.0
from EXABYTE
alternative emulation
IBM/IBM 03590E1A
Driver: halfinch.sys from
VERITAS
file version 5.0.1.1
Driver version: 4.0.1381.1
Caution: The Halfinch Driver
can only be installed after
installing NetBackup.
Windows 2003
●
The logical volumes can be added in NetBackup with ”New Volumes”.
●
The avr daemon of NetBackup on Windows often reports the following:
Event 4111 "GetTapeParameters () failed Device must be cleaned".
This does not result in any functional restriction.
●
178
VJUK settings
Application
NetBackup 5.0 MP 1
Platform
Windows 2003 5.2.3790
Jukebox type in CS
FSC CS-TL
EXABYTE: Mammoth2
TL8
8MM2
Max. number of volumes per jukebox in
application
16,000
13 October 2006
Edition 7
8.2.4.4
NetBackup (Veritas)
Reliant UNIX
TSM does not support Reliant UNIX from FSC. Only Reliant from Pyramid is supported.
8.2.4.5
Solaris
●
●
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
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.
●
Edition 7
The “sg” driver must also be installed. See: “Media Manager Device Configuration
Guide” from Veritas.
13 October 2006
179
NetBackup (Veritas)
●
To avoid hold-ups due to long waiting times for messages, it is strongly recommended
that you lengthen the system message queue.
To do this, you must extend the file “/etc/system” with the following entry:
..
# Settings for VERITAS NetBackup, T.Daude 28.02.02 VERITAS Software GmbH
set msgsys:msginfo_msgmap=4096
set msgsys:msginfo_msgmax=4096
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgmni=16
set msgsys:msginfo_msgssz=64
set msgsys:msginfo_msgtql=4096
set msgsys:msginfo_msgseg=4096
●
You should detach the sockets first. Set the file
/etc/rcS.d/S55network4NBU with the following content:
#!/sbin/sh
# Einstellung fuer VERITAS NetBackup, damit Sockets bereits nach
# 30 sek. vom System zu Wiederverwendung freigegeben werden
# (Default: 4 min)
# T. Daude, VERITAS Software GmbH
/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 30000
8.2.4.6
HP-UX
Settings for improved performance:
180
●
Extend block number and block size to 256KB:
#echo "262144" >/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
#echo "16" >/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
●
For TCP/IP network connections, extend the buffer size.
#echo "65536" >/usr/openv/netbackup/NET_BUFFER_SZ
●
NetBackup/HP-UX configuration settings:
Drive type
media type
HCART
Device node (no rewind device)
/dev/rmt/c*t0d*BESTnb
with ACSLS robot control: robot type
with DAS robot control: robot type
CentricStor emulation
FSC/CentricStor
13 October 2006
Edition 7
8.2.4.7
NetBackup (Veritas)
IBM-AIX
●
The device node must be set to extended filemarks. This setting is preset for AIX 4.3.
chdev –l 'rmt0' –a extfm='yes'
●
NetBackup/AIX configuration settings:
Drive type
media type
8.2.4.8
Device node (no rewind device)
/dev/rmt*.1
with ACSLS robot control: robot type
with DAS robot control: robot type
FSC/CentricStor
Linux
NetBackup does not support Linux.
Edition 7
13 October 2006
181
Data Protector
8.3 Data Protector
8.3.1 Documentation
The documentation for Data Protector is shipped on CD together with the product.
8.3.2 Licenses
The following licenses may also be needed for Data Protector:
–
–
–
Cell Manager Multi-Drive
Multi-Drive Server (if other servers are linked to CentricStor)
Unlimited Slot Libraries Extension for STK ACSLS or EMASS/GRAU DAS (depending
on which virtual library is used).
8.3.3 Miscellaneous
Up to Version 4.1 the software was marketed under the name Omniback.
As CentricStor mounts virtual volumes extremely quickly, you must ensure that the
hardware configuration of the Data Protector environment is appropriately defined. To avoid
bottlenecks this may call for relocation of the mount server to its own system.
Data Protector currently only releases the media for a save job once the entire job has run.
As the media table is contained in “shared memory”, parallel long save runs can lead to a
bottleneck in media management. A remedy can be found in optimum distribution of the
long and short jobs. It is planned to change this behavior of the media management in
Data Protector V5.5.
182
13 October 2006
Edition 7
Data Protector
8.3.4 Installation in Unix systems
8.3.4.1
8.3.4.2
Installation of Data Protector
●
Call /usr/sbin/swinstall
●
In the “Specify Source” window, choose the menu item “Select Network
Directory/CDROM” and specify the mount point of the CD-ROM. Then click OK to open
the “SD Install - Software Selection” window. The Data Protector product appears in the
list of available products.
●
Select it for installation with “Mark for Install” under the “Actions” menu item.
●
Under the “Actions” menu item, select “Install analysis” and then click “OK” to start the
installation.
●
After the installation you can start Data Protector with:
/sbin/init.d/omni start
and stop it with
/sbin/init.d/omni stop.
●
Starting <DATA_PROTECTOR_HOME>/bin/xomni starts the graphical configuration
menu.
Configuration of CentricStor in Data Protector
Make sure that the virtual drives register as “FSC-CentricStor”, so that Data Protector is
unknown. For this reason, when you click on the “Data Exchange Device” menu, you only
get the error message that no devices are present. In this case you must just specify the
device nodes manually e.g. /dev/rmt/c0t0d0BEST.
Up to version 3.5, you must also activate the menu item “Use direct library access” under
“Advanced options” in the drive configuration. From version 4.1 onwards, there is no need
to activate this item.
Under VDAS the option of using Exabyte Mammoth2 as a tape emulation is also available.
Here the media type “T3480/T...” is selected for FSC-CentricStor for library and drives, and
the media type “Exabyte” for Exabyte Mammoth2.
Under VACS it is not possible to use Exabyte Mammoth2 as the media type “Exabyte”
cannot be selected.
Edition 7
13 October 2006
183
Data Protector
8.3.4.3
Template for scratch mount support
When using an LV just for writing (FAST-MOUNT) Data Protector does not communicate
this to CentricStor over the supported standard interfaces:
VDAS/DAS
VACS/ACSLS
aci_scratch_set
csc_set_scratch
Instead of this, on UNIX machines you can set the following template:
#!/bin/sh
#--------------------------------------------------------------------# Example of fast access to (=recycle) volumes
#
# Limiting conditions:
#
- Omniback must work with compressing device nodes
#
- Compression must be active in CentricStor
#--------------------------------------------------------------------VSNList=`/opt/omni/bin/omnimm -list_scratch_media "Default
T3480/T4890/T9490" | \
/usr/bin/grep "\[" | \
/usr/bin/awk -F[ '{print $2}' | \
/usr/bin/awk -F] '{print $1}'`
for VSN in $VSNList
do
remsh CentricStor-VLP /usr/apc/bin/vlmif conf -r -n -v $VSN
done
This script truncates the LV to the part which is always contained in the cache, so no restore
is required in the event of the next mount.
184
13 October 2006
Edition 7
8.3.4.4
Data Protector
Template for PREFETCH support
#!/bin/sh
#--------------------------------------------------------------------# PREMOUNT for fast access to volumes on restore
#
#--------------------------------------------------------------------PREMOUNT_LOG=/var/opt/omni/log/premount.log
echo "====================B=E=G=I=N=N===================="
>>$PREMOUNT_LOG
date >>$PREMOUNT_LOG
VSNList=`cat /tmp/premount.txt`
for VSN in $VSNList
do
echo $VSN >>$PREMOUNT_LOG
remsh 130.11.10.81 /usr/apc/bin/vlmif prefetch -v $VSN >>$PREMOUNT_LOG
2>&1
done
date >>$PREMOUNT_LOG
echo "-----------------------E-N-D-----------------------"
>>$PREMOUNT_LOG
echo "---------------------------------------" >>$PREMOUNT_LOG
8.3.4.5
Bypassing lengthy backup times in Data Protector
Under Data Protector the problem can occur that backup times are prolonged by a restore
on the back end. This is caused because sorting of the free (virtual) cartridges is a
permanent process, i.e. the FREE ALLOCATION TABLE is constantly being updated, with
the result that scratched and newly released cartridges get mixed. Load times range from
under one second up to several minutes.
This behavior for handling free (virtual) cartridges within Data Protector is bypassed by
removing the virtual volumes whose retention period is due to elapse on the next day from
the media pool and assigning them to a storage pool. The volumes can remain in the latter
pool until the retention period has elapsed. They are then scratched and moved into the free
pool from which Data Protector takes the tapes for backups.
Edition 7
13 October 2006
185
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
Backup
Media pool DEFAULT
Media pool STORAGE
2. Scratch expired
tapes and move to
FREE
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:
186
●
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
13 October 2006
Edition 7
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
Edition 7
13 October 2006
187
Data Protector
ret=$?
if [ $ret = 0 ] ; then
echo Zweiter Start von $0 verhindert! >> $SCRATCH_LOG
echo ABBRUCH von zweitem $0 am `date`>> $SCRATCH_LOG
exit
else
# Could have crashed...or been killed...
rm $PIDFILE
fi
fi
# Create PIDFILE...
echo $PID > $PIDFILE
# Start logging
echo "====================B=E=G=I=N=N====================" >>$SCRATCH_LOG
date >> $SCRATCH_LOG
# List of locations in CenctricStor
VSNList=`/opt/omni/bin/omnimm -list_scratch_media "Lager Pre_Free" | \
/usr/bin/grep "\[" | \
/usr/bin/awk -F[ '{print $2}' | \
/usr/bin/awk -F] '{print $1}'`
# Process the list in a loop
for VSN in $VSNList
do
echo $VSN >>$SCRATCH_LOG
remsh $VLP /usr/apc/bin/vlmif conf -r -n -v $VSN >>$SCRATCH_LOG 2>&1
done
date >> $SCRATCH_LOG
echo "----------------------E-N-D-E----------------------" >>$SCRATCH_LOG
echo "---------------------------------------" >>$SCRATCH_LOG
# Send mail...
echo " Protokoll liegt unter /var/opt/omni/log/lager-scratch.log auf H01102!" > /tmp/sc.$$
mailx -s "LAGER-Scratchlauf fuer CentricStore am `date` beendet "
[email protected] < /tmp/sc.$$
rm /tmp/sc.$$
# Delete PIDFILE
rm $PIDFILE
188
13 October 2006
Edition 7
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
Edition 7
13 October 2006
189
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
190
13 October 2006
Edition 7
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
Edition 7
13 October 2006
191
Data Protector
8.3.4.6
Configuration as StorageTek ACS library
Selection of robot as StorageTek ACS library
192
13 October 2006
Edition 7
Data Protector
T3480 is selected as the tape type in the library configuration. The ACSLM host name is
the name of the machine in CentricStor on which VACS is running (normally the VLP).
The cap 0,0,0 is simply a default cap which is needed by Data Protector and accepted by
CentricStor.
Busy drive handling must be “Abort”.
The data device must be entered manually.
Edition 7
13 October 2006
193
Data Protector
Logical device - Advanced options
194
13 October 2006
Edition 7
8.3.4.7
Edition 7
Data Protector
Configuration as a Grau-DAS library
13 October 2006
195
Data Protector
T3480 is selected as the tape type in the library configuration. The “DAS Server” is the
name of the machine in CentricStor, the VDAS process is running. The E01 and I01 caps
are simply default caps which are needed by Data Protector and accepted by CentricStor.
Busy drive handling must be “Abort”.
The data device must be entered manually.
196
13 October 2006
Edition 7
Data Protector
Logical device - Advanced
Edition 7
13 October 2006
197
Data Protector
8.3.4.8
Setup of volumes
The simplest way to check that the configuration has been successful is to first format some
tapes which have been previously generated in CentricStor. Simply right click on the previously configured library and select the menu item “Manage”.
198
13 October 2006
Edition 7
Data Protector
In the “Library Management” window under “Edit”, select the option “Add Volsers” and
specify the prefix and indices. These slots are then assigned to the library.
Edition 7
13 October 2006
199
Data Protector
CentricStor library management
After selecting a slot, under “Edit”, select the menu item “Init” and use this to format the tape.
200
13 October 2006
Edition 7
Data Protector
Library management - initialize medium
In the Init menu, you must only specify the media pool used by the library for the tape. If the
tape is already described with other programs, you must also select “force initialization”.
8.3.5 Installation example for Windows NT
The example shows an installation of Data Protector 4.1 with ACSLS in Windows NT.
Unpack ns4453a5.zip
Edition 7
13 October 2006
201
Data Protector
Install device driver
Check if the driver has
been started
202
13 October 2006
Edition 7
Data Protector
For operations over
ACSLS, LibAttach
must be installed
Check, to see if
LibAttach runs with
SSI
Edition 7
13 October 2006
203
Data Protector
Definition of library
Specify the IP
address of the
VLP
204
13 October 2006
Edition 7
Data Protector
Define CAP
Define Drive
Edition 7
13 October 2006
205
Data Protector
Selection from the
list of recognized
SCSI drives
Enter the virtual
drive position
corresponding to
the CentricStor
configuration
206
13 October 2006
Edition 7
Data Protector
Set drive type
Edition 7
13 October 2006
207
Data Protector
8.3.6
8.3.6.1
VJUK configuration
General
Only 1500 slots are supported per VJUK emulation of DataProtector.
8.3.6.2
Configuration of the robots under AIX
With DataProtector, AIX can only be used as a client.
8.3.6.3
Configuration of the robots under HP-UX
After the devices under /dev/rmt have been deleted, the insf -e command is executed.
This program creates all device files anew. The device for the robot can be found under
/dev/rac.
8.3.6.4
Configuration of the robots under Solaris
A prerequisite is that the following configuration files are correctly set up:
/kernel/drv/st.conf
/kernel/drv/lpfc.conf
The sst driver is required for the robot. This is supplied by HP and is located under
/opt/omni/spt. It is copied to /usr/kernel/drv using its configuration file sst.conf as
follows (take care!):
●
Solaris 32-bit:
$cp /opt/omni/spt/sst /usr/kernel/drv/sst
$cp /opt/omni/spt/sst.conf /usr/kernel/drv/sst.conf
●
Solaris 64-bit:
$cp /opt/omni/spt/sst.64bit /usr/kernel/drv/sparcv9/sst
$cp /opt/omni/spt/sst.conf /usr/kernel/drv/sst.conf
The robot’s target and Lun are copied into file sst.conf.
Subsequently the line below is entered in the /etc/devlink.tab file:
type=ddi_pseudo;name=sst;minor=character rsst\A1
i
Blanks may not be used for “whitespace”, but only “TABs”.
The driver is then installed:
add_drv sst
208
13 October 2006
Edition 7
Data Protector
After the reconfiguration boot (reboot -- -r) you can search for the device file for the
robot under the /devices directory. A link to this must be created from the /dev directory
if the system has not done this automatically, for example:
ln -s /devices/pci@1f,4000/scsi@3,1/sst@4,1:character /dev/rsst4
You see the name of the rsst* device in the boot log (dmesg) or system log
(/var/adm/messages).
8.3.6.5
Configuration of the robot devices under Windows
After CentricStor has been connected, the Windows system automatically recognizes the
robot and the drives. You can see the robot under the autochanger in the device manager.
Tape and robot devices are displayed using the DataProtector devbra -dev command.
8.3.6.6
Configuration of a library under Solaris
Library - General:
Edition 7
13 October 2006
209
Data Protector
Library - Control:
210
13 October 2006
Edition 7
Data Protector
Library - Repository:
Edition 7
13 October 2006
211
Data Protector
Library - Settings:
212
13 October 2006
Edition 7
Data Protector
Drive - General:
Edition 7
13 October 2006
213
Data Protector
Drive - Drive:
214
13 October 2006
Edition 7
Data Protector
Drive - Settings:
Edition 7
13 October 2006
215
Data Protector
8.3.7 Miscellaneous
8.3.7.1
Virtual drives
As Data Protector does not recognize the drive “FSC-CentricStor”, this error message will
appear every time the drive is accessed:
“Unknown Device, please check device support matrix”
as shown in the figure below. However, the error message has no effect on operations.
To suppress this warning, create the following file:
HP-UX:
Other UNIX systems:
Windows systems:
216
/opt/omni/.devtab
/usr/omni/.devtab
<Data_Protector_Home>\devtab
13 October 2006
Edition 7
Data Protector
This file contains the line
CentricStor
CentricStor
5
5
Product ID which you obtain as follows:
HP-UX:
Load tape and enter the command
diskinfo -v /dev/rmt/<device name>.
Windows:
Look in the SCSI registry which you can find under
HARDWARE\DEVICEMAP\Scsi.
“Media type” which can be found in Table A-1 in the appendix of the
“hp OpenView Data Protector Administrator's Guide”.
If there are two devices in the system with the same product ID but with different
“vendor IDs”, the line must look as follows:
<product_ID>
<vendor_ID>
<media_type_number>
The vendor ID is also displayed in response to the aforementioned diskinfo command.
For further details, see “Configuring Unsupported Devices” in the “hp OpenView Data
Protector Administrator's Guide”.
8.3.7.2
DAS interface
From Data Protector A.03.10 onwards, more than 15 drives will be recognized as long as
the following two conditions are fulfilled:
1. The following patches are used:
Data Protector version
Patch
A.03.10
PHSS_21642
A.04.10
PHSS_26358
2. The following variable has been set in the.omnirc file:
OB2DASDRIVESTATUS2=1
●
Edition 7
In order to enable DAS control, the DAS media agent must first be installed on the client.
This software must be purchased and can be obtained from ADIC (robot manufacturers). Also see: http://www.adic.com.
13 October 2006
217
Data Protector
HP-Unix:
●
The shared library libaci.sl from the ADIC DAS package must be copied to
<Data_Protector_Home>/lib.
●
The file .omnirc.TMPL in <Data_Protector_Home> must be copied to .omnirc in the
same directory and must be extended with the following entry:
DAS_SERVER=<name or IP address of the VDAS server in CentricStor >
DAS_CLIENT=<name of the client in the configuration>
●
8.3.7.3
Details about the possible causes of connection problems with VDAS and other troubleshooting advice is given in section “Possible problems and solutions” on page 271.
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 276.
8.3.8.1
Windows NT 4.0
●
must be used.
●
When using the DAS interface:
a) Copy aci.dll, winrpc.dll or winrpc32.dll and ezrpcw32.dll to
\winnt\system32 and <OMINBACK_HOME>\bin.
b) Run Portinst to install Portmapper.
c) Restart.
d) Under SERVICES, see if Portmapper and RPC services are running.
218
●
The system drivers are not used. The drivers must be deactivated as follows:
Under Start->Properties->System Control select the “Tape Drives” option. The
individual drives can be deactivated here by right clicking.
●
The values for adapters, bus, ID etc.can be found at
Start->Properties->System control->SCSI adapter-><FC adapter>
->BUSx-><device emulation> under Properties/Settings.
●
If you are using Data Protector 3.5, use the patch win_0017 (from the Data Protector
CD).
13 October 2006
Edition 7
●
Data Protector
Data Protector/NT settings:
media type
T3480
Device Nodes
SCSI*:*:*:*C
Tape*:*:*:*C (from version 4.1)
StorageTek ACS Library
GRAU DAS Library
drive emulation
FSC/CentricStor
Device nodes: SCSI<Adapter>:<Bus>:<ID>:<LUN>[C|N]
C=compressed, N=nonrewinding
8.3.8.2
Edition 7
Windows 2000
●
●
When using the DAS interface, copy:
aci.dll, winrpc.dll bzw. winrpc32.dll nach \winnt\system32 and
<OMINBACK_HOME>\bin.
●
Run Portinst to install Portmapper.
●
Restart.
●
Under SERVICES, see if Portmapper and RPC services are running.
●
The system drivers are not used and they must be deactivated.
Under Start->System control, select the “System” option. In the menu which appears,
select the “Hardware” tab. Then open the device manager. Next, deactivate the relevant
drives by right clicking in the device manager under the “tape drive” option.
●
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).
13 October 2006
219
Data Protector
●
Data Protector/Windows settings:
media type
T3480
Device nodes
SCSI*:*:*:*C
Tape*:*:*:*C (from version 4.1)
GRAU DAS Library
drive emulation
FSC/CentricStor
Device nodes: SCSI<Adapter>:<Bus>:<ID>:<LUN>[C|N]
C=compressed, N=nonrewinding
8.3.8.3
Reliant UNIX
●
Not currently released.
●
CentricStor is only supported as a media agent without robot control.
●
Data Protector/Rel settings. UNIX:
media type
Device Nodes
drive emulation
8.3.8.4
220
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>
13 October 2006
Edition 7
●
8.3.8.5
Data Protector
Data Protector/Solaris settings:
media type
T3480
Device nodes
/dev/rmt/*cb
drive emulation
FSC/CentricStor
HP-UX
●
Patch PHSS_24659 from Data Protector is required. The patch can be downloaded
from http://www.openview.hp.com.
●
When using the DAS interface the shared library libaci.sl from the ADIC DAS
package must be copied to <Data_Protector_Home>/lib. On a 64-bit machine,
there can be problems with a 64-bit lib from ADIC.
You can check if the lib is correct using these command:
cd /opt/omni/lbin
./bma –version
If there is an error message, the 32-bit lib should be used.
Edition 7
●
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
GRAU DAS Library
STL interface lib
libaci.sl
drive emulation
FSC/CentricStor or Mammoth2
13 October 2006
221
Data Protector
8.3.8.6
8.3.8.7
IBM-AIX
●
CentricStor is only supported as a media agent.
●
The only node which is compressed is 3590-E. However, this drive is only supported by
the DAS robot controller. Thus there is no edition with ACS robot control.
●
Data Protector/AIX settings:
media type
3590
Device nodes
/dev/rmt*
GRAU DAS Library
STL interface lib
libaci.a
drive emulation
3590E1A
Linux
The system is only supported as a client.
222
13 October 2006
Edition 7
Tivoli / TSM
8.4 Tivoli / TSM
8.4.1 Documentation
The documentation for Omniback is shipped on CD together with the product. It includes
the following manuals:
Manual
Version / Release
Tivoli Storage Manager for Windows
Quick Start
as of Version 4/Release
2, June 2001
Administrator's Guide
2, June 2001
Administrator's Reference
2, June 2001
Tivoli Storage Manager
Messages
2, June 2001
You can obtain this documentation from the following Internet links:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
TSM 5.3:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp?topic=/com.ibm.itsmaixn.doc/an
rai53.htm
8.4.2 Installation and configuration
8.4.2.1
TSM installation
At least version 4.2.1.7 is required. With version 4.2.0, errors occur when defining drives.
The following packages are to be read in (example for Solaris, other platforms are similar):
TSM4217S_Sun.tar.Z TSM server
IP22372.tar.Z TSM client
All packages are unpacked with uncompress and then extracted with
tar -xvf <name of file>. Then the packages are all installed with
pkgadd -d /<full path>/<name of the package> .
The software is installed by default in the directory: /opt/tivoli/tsm
Edition 7
13 October 2006
223
Tivoli / TSM
8.4.2.2
TSM configuration
The complete configuration was set with the help of command line tools. This is because it
is not possible to configure an individual drive on the graphical interface since you cannot
specify the device file of the drive there.
All pathnames are relative to the TSM main path.
●
Start from rc.acs_ssi from the <TSM>/devices/bin directory
●
Start of the server with ./dsmserv quiet & from the directory
<TSM>/server/bin
●
Start the administrative console with ./dsmadmc from the directory
<TSM>/client/admin/bin
The user and password in the default installation are:
Login:
User:
admin
admin
All of the following commands are given on the administrative console.
Define the Library
DEFINE LIBRARY <name of library> LIBTYPE=ACSLS ACSID=1
Define a drive
DEFINE DRIVE <name of library> <name of drive> DEVICE=<device file>
ACSDRVID=<ACS drive ID>
A tape must be inserted in the drive.
The following definition has been added from Version V5:
DEFINE PATH <server name> <drive name> SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=<name of library> DEVICE=<device file>
Define device class:
You can look at the defined drive with QUERY DRIVE and find out which device class is
to be created.
224
13 October 2006
Edition 7
Tivoli / TSM
In Solaris, this is the GENERICTAPE class in AIX 3590. The device classes are then
created as follows:
Edition 7
●
For GENERICTAPE:
DEFINE DEVCLASS <name of device class>
LIBRARY=<name of library>
DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M
MOUNTRETENTION=60
MOUNTWAIT=60
MOUNTLIMIT=DRIVES
●
For 3590:
DEFINE DEVCLASS <name of device class>
LIBRARY=<name of library>
DEVTYPE=3590
FORMAT=DRIVE
ESTCAPACITY=900M
PREFIX=<prefix of volume in use>
MOUNTRETENTION=60
MOUNTWAIT=60
MOUNTLIMIT=DRIVES
●
Define a storage pool:
DEFINE STGPOOL <name of pool> <name of device class>
MAXSCRATCH=<number of scratch tapes in pool>
●
Change for backup
UPDATE COPYGROUP standard standard standard TYPE=archive DESTINATION=<name of pool>
●
Change for archive
UPDATE COPYGROUP standard standard standard TYPE=backup DESTINATION=<name of pool>
●
Change the management class
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=<name
of pool>
●
Subsequent activation
ACTIVATE POLICYSET standard standard
●
Label and check in volumes
LABEL LIBVOLUME <name of library> SEARCH=yes
VOLRANGE=<first volume> ,<last volume>
CHECKIN=private OVERWRITE=yes
13 October 2006
225
Tivoli / TSM
●
Add to storage pool
DEFINE VOLUME <name of pool> <name of volume>
●
Activate web console
To activate the web console, you must modify the file dsmserv.opt from the
<TSM>/server/bin directory before starting the server. If this file is not present, it
can be created by copying the standard file dsmserv.opt.smp from the same
directory.
The following entries must be activated in this file:
COMMmethod HTTP
HTTP port 1580
Then you can reach the console from any web browser at the following address:
http://<IP address of the TSM server>:1580
8.4.2.3
Special parameters
In the file dsmserv.opt the parameter ACSTIMEOUTX should be set to 5 (i.e. a maximum
wait time of 50 minutes for ACS library access).
8.4.2.4
Examples
Configuration
DEFINE LIBRARY CentricStor LIBTYPE=ACSLS ACSID=1
DEFINE DRIVE CentricStor V20C DEVICE=/dev/rmt1cn ACSDRVID=1,0,0,12
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M MOUNTRETENTION=60 MOUNTWAIT=60 MOUNTLIMIT=DRIVES
DEFINE STGPOOL CentricPool CentricTape MAXSCRATCH=0
UPDATE COPYGROUP standard standard standard TYPE=archive
DESTINATION=CentricPool
UPDATE COPYGROUP standard standard standard TYPE=backup
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=CentricPool
Handling the volume
LABEL LIBVOLUME CentricStor SEARCH=yes VOLRANGE=TIV01,
TIV20 CHECKIN=private, OVERWRITE=yes
DEFINE VOLUME CentricPool TIV01
... to
DEFINE VOLUME CentricPool TIV20
226
13 October 2006
Edition 7
Tivoli / TSM
Backup of a directory
Starting from dsmc:
ARCHIVE /home/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
Restore of a directory
Starting from dsmc:
RETRIEVE /home/ /tmp/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
8.4.3 Installation and configuration with Gresham EDT
This software package makes it possible to control ACSLS controlled robots via Gresham
EDT with the “External Library Manager Function”. This function must be used in configuration with HP-UX, as TSM does not support any ACSLS libraries in HP-UX.
For further information on the software see:
http://www.gresham-software.com
See product: EDT-DistribuTAPE™
8.4.3.1
Gresham installation
Version 6.2.1.0 has been tested by FSC.
The following package is played in:
edt.6210.hpux.tar.gz Gresham DistribuTape
The package was unpacked with gunzip and then extracted with
tar -xvf edt.6210.hpux.tar. Then the unpacked
OMIdtelm.6210.depot was installed with
swinstall -s /<full path>/OMIdtelm.6210.depot.
The software is installed by default in the directory: /opt/OMIdtelm
Edition 7
13 October 2006
227
Tivoli / TSM
8.4.3.2
TSM installation
Version 4.2.1.7 has been tested by FSC.
The following packages are read in:
TSM4217SRV_HPUX.tar TSM server
IP22368.tar TSM client
All packages are unpacked with gunzip and then extracted with tar -xvf <name of
file>. Then the server is installed with
swinstall -s /<full path>/<name of package>
and the client with
swinstall -x mount_all_filesystems=false -v -s `pwd`/TIVsmC TIVsm
The software is installed by default in the directory:
/opt/tivoli/tsm
8.4.3.3
Gresham configuration
Start the SSI agent
First the rc.edt script from the <installations path>/bin
directory must be edited; you can create it by copying from rc.edt.smp.
In this file the variable MEDIA_MNGR_HOST must also be changed.
You should enter the IP address or (with working name resolution) the machine name of the
VLP, on which the ACSLS emulation is running (see section “IP addresses and host names”
on page 266 and section “Virtual libraries” on page 267).
Then start the script with the parameter both. This starts the SSI process, and simultaneously initializes DistribuTape.
228
13 October 2006
Edition 7
Tivoli / TSM
Set up a storage pool and add tapes on the VLP.
You log in to the VLP and start the program cmd_proc which can be used to configure the
emulation of the ACSLS connection.
You then create a pool using:
define pool <Low Water Mark> <High Water Mark> <Pool ID>
Watermarks and pool IDs:
Low Water Mark
Lowest number of available volumes which must be in the pool;
should be set to 0.
High Water Mark
Maximum number of available volumes in the pool; can be as
high as you wish, e.g. 10000.
Pool ID
A number given by you, from 1 to 65534.
All further commands can then be carried out again on the computer on which Gresham
DistribuTape was installed. However, it is also possible to continue working on the VLP with
cmd_proc.
You can now add volumes to the pool with the command set_scratch:
set_scratch -p <pool ID> -a <first volume> -b <last volume>
or
set scratch <PoolID> <first volume>-<last volume>
You can then see if everything is correctly configured using the query q_pool -p <pool
ID>.
Configuration of a library in Gresham DistribuTape
The complete configuration of a library is carried out using the configuration file elm.conf,
which is found under <installation path>/bin.
If it does not exist, you can copy the example file elm.conf.smp to elm.conf .
Example configuration, including explanation of the most important elements:
LICENSE PERM <license key>
LIBRARY <library name>
POOL <pool ID>
DRIVE <device file> ACS_<ACS drive ID>
END
Edition 7
13 October 2006
229
Tivoli / TSM
Configuration with Gresham DistribuTape:
License key
License key, shipped by Gresham together with the product at purchase.
Library name A name you choose which must agree with the library defined later in TSM.
In order to be recognized by TSM, this must be written in block capitals.
8.4.3.4
Pool ID
Must agree with the Pool ID set by cmd_proc.
Device file
Full path for the device file of the drive. The following devices are used in
HP: /dev/rmt/*m.
ACS drive ID
Drive ID with which the drive is recognized in the library, e.g. 0,0,0,0.
TSM configuration
The complete configuration was made using the command line tools. All pathnames are
relative to the TSM main path.
●
Start the server with ./dsmserv quiet & from the directory <TSM>/server/bin
●
Start the administrative console with ./dsmadmc from the directory
<TSM>/client/admin/bin
The user and password in the default installation are
Login:
User:
admin
admin
All of the following commands are given on the administrative console.
Defining the Library
DEFINE LIBRARY <name of library> LIBTYPE=ACSLS ACSID=1
EXTERNALManager=/<Gresham installation path>/bin/elm
Defining a device class
DEFINE DEVCLASS <name of device class> LIBRARY=<name of library>
DEVTYPE=GENERICTAPE ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60
MOUNTLIMIT=<number of drives defined in DistribuTape>
Defining a storage pool
DEFINE STGPOOL <name of pool> <name of device class>
MAXSCRATCH=<number of scratch tapes in pool>
Changing and activating policy
UPDATE COPYGROUP standard standard standard DESTINATION=<name of
pool>
Change for backup
UPDATE COPYGROUP standard standard standard TYPE=archive DESTINATION=<name of pool>
230
13 October 2006
Edition 7
Tivoli / TSM
Change for archive
UPDATE COPYGROUP standard standard standard TYPE=backup DESTINATION=<name of pool>
Changing the management class
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=<name of
pool>
Subsequent activation
Activate web console
To activate the web console, you must modify the file dsmserv.opt from the
<TSM>/server/bin directory before starting the server. If this file is not present, it can
be created by copying the standard file dsmserv.opt.smp from the same directory.
The following entries must be activated in this file:
COMMmethod HTTP
HTTP port 1580
You can then reach the console from any web browser at the following address:
http://<IP address of the TSM server>:1580
8.4.3.5
Examples
Configuration for Gresham DistribuTape:
Making the scratch pool
Log in on the VLP, start from cmd_proc
Enter: define pool 0 10000 100
Add tapes to scratch pool set_scratch -p 100 -a TSMG00 -b TSMG09
Contents of /opt/OMIdtelm/bin/elm.conf:
LICENSE PERM 1444291050
LIBRARY CENTRICSTOR
POOL 100
MSG MDRVSTAT MDRVERR MPOOLSTAT /opt/OMIdtelm/bin/msg.out
DIAG ESUB EDRV ECNV EELM /opt/OMIdtelm/bin/dbg.out
DRIVE /dev/rmt/36m ACS_2,0,0,4
END
Configuration check
elm_testlibdesc -l CENTRICSTOR
Edition 7
13 October 2006
231
Tivoli / TSM
Configuration for TSM
DEFINE LIBRARY CentricStor LIBTYPE=external
EXTERNALManager=/opt/OMIdtelm/bin/elm
DEFINE DEVCLASS CentricTape LIBRARY=CentricStor DEVTYPE=GENERICTAPE
ESTCAPACITY=2000M MOUNTRETENTION=5 MOUNTWAIT=60 MOUNTLIMIT=4
DEFINE STGPOOL CentricPool CentricTape MAXSCRATCH=10
UPDATE COPYGROUP standard standard standard DESTINATION=CentricPool
UPDATE COPYGROUP standard standard standard TYPE=archive
UPDATE COPYGROUP standard standard standard TYPE=backup
UPDATE MGMTCLASS standard standard standard MIGDESTINATION=CentricPool
Backup of a directory
Starting from dsmc:
ARCHIVE /home/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
Restore a directory
Starting from dsmc:
RETRIEVE /home/ /tmp/ -SUBDIR=yes -DESCRIPTION='Hello Backup'
8.4.4 Configuring a SCSI library on AIX via VJUK
8.4.4.1
General
The VJUK emulation is supported as of CentricStor Version V3.0.
The term element number in the SCSI library corresponds to the term slot number in VJUK.
The device nodes in AIX must have the same slot or element numbers in the TIVOLI-SCSI
library as the virtual drives in the associated VJUK emulation of CentricStor.
The VJUK administration tool “vjukadmin” can be used, among other things, to create an
inventory of the slots or drives, to unload volumes from the drives, and to transfer them
again to the slots.
Access to VJUK with vjukadmin is only possible in the “offline” status. vjukadmin permits
switching between “offline” and “online”. A host can only access the VJUK in “online” status.
232
13 October 2006
Edition 7
8.4.4.2
Tivoli / TSM
Configuration steps
1. CentricStor configuration
Library type / max. number of slots: ADIC/Scalar-10K 16000
Use of LUN 0 as robotics, emulation IBM 03590E1A for virtual drives
Creating the assignment list of the virtual drives and associated slot numbers in
CentricStor:
# vjukadmin VJ00 inventory drives
vjukadmin VJ00 inventory drives
INQUIRY-DATA:
SLOT
DRIVE
VSN
0100
V001
0101
V002
0102
V003
0103
V004
0104
V005
0105
V006
0106
V007
-
i
The slot number is output in hexadecimal format. The element address must be
specified in decimal format for the TSM.
2. Creating the device nodes via smit in AIX
smit -> Devices -> Tivoli Storage Manager Devices
-> Fibre Channel SAN Attached Devices
-> Discover Devices Supported by TSM
-> Parent FC Adapter.
The robotics are assigned the device names lb0, lb1, etc., the devices the names mt0,
mt1, etc.
Device node names for robotics: /dev/lb0, …
Checking the WWN of the robotics:
# lsattr -El lb0
FCPORT_ID 0x31a00
LUNMAP_ID 0x0
WW_NAME
0x10000000c937fa42
PRODUCT_ID Scalar 10K
FC Port ID
Mapped LUN ID of the device
WW Name of the Port
Product ID of the device
True
True
False
False
Generating the device node names via the Atape driver:
cfgmgr
Edition 7
13 October 2006
233
Tivoli / TSM
i
The following cfgmgr message can be ignored:
" cfgmgr: 0514-621 WARNING: The following device packages are
required for device support but are not currently installed.
devices.fcp.changer "
No functional restriction has been observed.
The device nodes /dev/mt0, … created by TSM are not to be used for the tape drives
but those created by cfgmgr via the Atape driver: /dev/rmt0, …
Checking the attributes of a device node in AIX:
# lsattr -El rmt1
mode
yes
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 Write
Block Size (0=Variable Length
Use Hardware Compression on Tape
Use Autoloading Feature at End-of-Tape
Activate volume information loggingTrue
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
In addition to the WWN and LUN, the drive’s port ID is also specified under scsi_id.
234
13 October 2006
Edition 7
Tivoli / TSM
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
srctype=server desttype=drive library=aix-vj00 device=/dev/rmt0.1
…
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 colume with an exisitng label into the library:
checkin libvolume aix-vj00 X00000 status=scratch checklabel=barcode
checkout libvolume aix-vj00 X00000 remove=no checklabel=no
The checkout is to take place with remove=no. If remove=yes the TSM would
attempt to transfer the volume into the VJUK’s I/O slot.
To harmonize the directories between the TSM administration and VJUK:
audit library aix-vj00 checklabel=barcode
or
audit library aix-vj00 checklabel=yes
If checklabel=yes each volume is mounted and the label read by TSM. With
CentricStor this means that a volume which was migrated to a real tape must be read
into the cache again!
When checklabel=barcode the data inventory of VJUK and TSM is harmonized.
This operation lasts only a few minutes, even with 16,000 slots, for example.
audit library checklabel=barcode is recommended if TSM finds volumes
mounted in the last TSM run when it starts and cannot reset these, or if an audit library
is recommended by TSM.
If the TSM drives are not emptied by audit volume either, this must be performed using
vjukadmin unload and vjukadmin unmount.
i
Edition 7
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.
13 October 2006
235
Tivoli / TSM
8.4.4.3
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.
8.4.5 LANfree configuration without Gresham
8.4.5.1
Prerequisites
Software
TSM Server + Agents + Client
Version: 5.3.2.0
Emulation in CentricStor
IBM 3590
Library Emulation
VACS or VJUK (not as powerful)
Driver on the host systems
IBMtape driver
TSM server
AIX 5.2, IBMtape, Atape driver Version 9.2.6.0
Drivers
TSM server
AIX 5.2
IBMtape, Atape driver Version 9.2.6.0
Storage agents
236
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
13 October 2006
Edition 7
8.4.5.2
Tivoli / TSM
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.
8.4.5.3
Configuration
Generating the device files
The /dev/rmt devices are generated on the AIX server using cfgmgr. The device file for
the robot is generated with SMIT. To do this, select the following in SMIT:
Devices
->Tivoli Storage Manager Devices
-> FibreChannel SAN Attached Devices
-> Discover Devices Supported by TSM
-> ...
The device file generated is called /dev/lbX, für X = 0..n.
On the Linux client the device files are generated automatically by the IBMtaped daemon in
the case of the IBMtape installation as of Version 1.3.. They are called /dev/IBMtapeX and
/dev/IBMtapeXn ( X = 0..n ), only the first one being used for configuration here.
Device node with IBMTape driver under Solaris:
/dev/rmt/130stcbn
../../devices/pci@17,2000/fibre-channel@1/IBMtape@3a,21:stcbn
HPUX
crw-rw-rwcrw-rw-rwcrw-rw-rwcrw-rw-rw-
1
1
1
1
bin
bin
bin
bin
bin
bin
bin
bin
205
205
205
205
0x1b0000
0x1b0080
0x1b0040
0x1b00c0
Jan
Jan
Jan
Jan
12
12
12
12
17:27
17:27
17:27
17:27
/dev/rmt/c27t0d0BEST
/dev/rmt/c27t0d0BESTn
/dev/rmt/c27t0d0BESTnb
ioscan -fnkC tape bringt:
# ioscan -fnkC tape
Class
I H/W Path
Driver S/W State
H/W Type
Description
========================================================================
tape
0 0/0/1/0.3.0
stape CLAIMED
DEVICE
HP
C1537A
/dev/rmt/0m
/dev/rmt/c0t3d0BESTn
/dev/rmt/0mb
/dev/rmt/c0t3d0BESTnb
/dev/rmt/0mn
/dev/rmt/c0t3d0DDS
/dev/rmt/0mnb
/dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST
/dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0DDSnb
tape
133 0/4/0/0.2.6.255.0.0.0
stape CLAIMED
DEVICE
STK
T9840B
Edition 7
13 October 2006
237
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
Ê
238
dsmsta
13 October 2006
Edition 7
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 ...
Edition 7
Ê
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
Ê
define policyset cs_domain cs_policy
13 October 2006
239
Tivoli / TSM
8.4.5.4
Ê
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
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.0
240
13 October 2006
Edition 7
Tivoli / TSM
Client date/time: 04/26/05
19:12:25
(c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights
Reserved.
8.4.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.4.5.6
If an agent crashes during reservation it is not always recovered automatically upon
booting. In CentricStor the reservation of a drive for a host can be canceled by stopping/starting the emulation.
References
All processes described here were taken from the TSM documentation. This is available in
HTML or PDF format at the following URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp
8.4.6 Miscellaneous and restrictions
●
The volumes must be alphanumeric.
●
Tivoli/TSM does not currently support any DAS robot interfaces. Version 5 may provide
this support.
●
TSM or TSM Label only includes restricted support for drive positioning:
acs(1), lsm(0-23), panel(0-19), drive(0-19)
●
TSM Server Trace for drive problems with tape robots
trace dis *
trace enable pvr mms systime
trace begin /tmp/trace.out
> Aktion …..
trace flush
trace end
trace dis *
Edition 7
13 October 2006
241
Tivoli / TSM
8.4.7.1
Windows NT 4.0
not yet released
8.4.7.2
Windows 2000
If you are using the ACSLS interface, you must use the “LibAttach2” software by
StorageTek. You can use the product for Windows NT 4.0.
Configuration:
media type
Mammoth2
Device nodes
8.4.7.3
LIBTYPE
ACSLS
EXABYTE/Mammoth2
Reliant UNIX
TSM does not support Reliant UNIX.
8.4.7.4
Solaris
Only ACSID=1 is supported.
i
For the audit library, in dsmserv.opt change the parameter ACSTIMEOUTX from
the default setting 1 (=10 minutes) to the setting 4 (=40 minutes).
Some drives will only be ready for use again after UPDATE DRIVE ONLINE=NO/YES.
DEFINE DRIVE last approximately 1 minute.
Configuration:
242
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/*cn
drive emulation
FSC/CentricStor
13 October 2006
Edition 7
8.4.7.5
Tivoli / TSM
HP-UX
The ACSLS controller can only be addressed via Gresham EDT.
Configuration:
8.4.7.6
DEVTYPE
GENERICTAPE
LIBTYPE
ACSLS
Device nodes
/dev/rmt/cXtXdXBEST
drive emulation
FSC/CentricStor
IBM-AIX
Configuration:
8.4.7.7
DEVTYPE
3590
LIBTYPE
ACSLS
Device nodes
/dev/rmt*
drive emulation
3590E1A
Linux
TSM does not support Linux.
Edition 7
13 October 2006
243
BrightStor ARCserve Backup
8.5 BrightStor ARCserve Backup
8.5.1 ARCserve
The initial release for operation with CentricStor has taken place for:
●
ARCserve r11.1 for Windows
●
ARCserve r11 for Windows
●
ARCserve r11.1 for Linux
8.5.2 CentricStor
A prerequisite for operation with ARCserve is at least Version 3.0 as of K834.1. Only
CentricStor V3.0 offers the VJUK interface and fixed block mode, both of which are used by
ARCserve.
Only an ADIC Scalar 1000 with up to 48 drives and 1182 slots can be used as a virtual
library. Exabyte Mammoth II must be set for tape emulation. "Extended Logical Volumes"
with a capacity of 2 GB each and activated data compression permit a storage capacity of
around 4 TB per virtual Scalar 1000 when 1182 slots are used. If this is not enough, another
virtual jukebox can be configured.
244
13 October 2006
Edition 7
8.5.3 Backup server
The backup server on which ARCserve runs is connected to CentricStor via FC. A controller
which has been released for the Primergy and CentricStor connection and has the appropriate driver must be used for this purpose. The controller and driver parameters must also
be set appropriately for the connection of a tape library.
In tests good results were achieved under Windows 2003 with an LP9002 with 3.90a7
firmware and 2.21.a7 driver and the following parameter settings:
Edition 7
13 October 2006
245
246
13 October 2006
Edition 7
8.5.4 Further information
After the hardware and software have been installed, the following steps are recommended
for startup and configuration:
Configure the virtual library on CentricStor and check the LUNs assigned with the aid of
GXCC. The tape drives are assigned their LUNs automatically, starting with 0. The VJUK
LUN must be configured in the GXCC under “Virtual Library Services”, and it makes sense
to use the next free LUN after the tape drives. Windows and ARCserve have no problems
if there are gaps in the LUNs, however.
●
When an Emulex controller is used the aforementioned parameters are set with ”elxcfg”,
and “HBAnywhere” is used to check whether the controller has recognized all the
CentricStor LUNs.
●
In the next step the operating system must recognize all the devices. Under Windows
this is done in the Device Manager. No Windows drivers are required for the jukebox or
tape drives; ARCserve handles hardware control itself.
●
Only when these hurdles have been taken can ARCserve device configuration be
started. Here the tape drives are assigned to their jukebox.
It is advisable to use the “Eject Media after Backup” option in ARCserve (Device Configuration -> Library Properties oder Global Job Options -> Operations). This ensures
that an Unmount/Eject is automatically performed at the end of a backup job, thus
ejecting the cartridge used from the virtual drive. Without this option ARCserve leaves
the cartridge in the drive in order to have it available more quickly for reuse.
●
Starting the ARCserve manager and calling the Device Window. The virtual jukebox
with its drives and slots now appears here. After an initial inventory the backup server
is ready to operate.
Information on import / export
With real hardware the “Import” or “Export” function under ARCserve is used to address the
mailslot of a jukebox in order to import or export cartridges without opening the jukebox and
thus forcing a complete, time-consuming inventory. This function is also supported in
CentricStor; the Scalar 1000 contains 12 virtual Mailslots.
These mailsolts can be addressed from ARCserve, i.e. cartridges can be exported there
from the magazine and also be reimported into the magazine. However, since these virtual
mailslots with their virtual cartridges do not really exist, this function can only be used to
resort cartridges in the jukebox.
Edition 7
13 October 2006
247
Time Navigator
8.6 Time Navigator
8.6.1 General
The Time Navigator is only released for Windows 2000 in the context of a customer project.
It was tested using Time Navigator V3.7. A mixed configuration with Mammoth2 and 3590
has been tested successfully. TINA is able to manage various pools with different drives.
8.6.2 Configuration
Configuring Magstar 3590E in Windows:
Definition of the drives in TINA:
Further settings must then be made in TINA for the virtual drives.
Select the drive type and edit it.
248
13 October 2006
Edition 7
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:
Edition 7
13 October 2006
249
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 .
250
13 October 2006
Edition 7
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.
Edition 7
13 October 2006
251
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”:
252
13 October 2006
Edition 7
Time Navigator
You can define values manually or press "…" to have preferred items displayed. These must
be the same as the drive items defined in CentricStor .
After you have entered all the parameters the following screen is displayed:
The pool number should be the one defined in the VACS (3 here).
Edition 7
13 October 2006
253
Time Navigator
After you have made these entries have the content of the library displayed and perform
reinitialization:
All the volumes (LVs) in the sepecified range are then accessible for the library.
TINA supports scatch pools. If an LV is recycled or migrated CentricStor receives the
command to truncate the LV and to perform no further restore from the volume (PV).
For this purpose the line:
TRUNCATE_CARTRIDGE="yes"
must be inserted in the file:
%TINA_HOME%/Vtl/catalog_library/vtl_config.txt
!
254
CAUTION:
Atempo recommends that you should only use one drive when labeling as familiar
problems will otherwise occur.
13 October 2006
Edition 7
VJUK emulation
8.7 VJUK emulation
8.7.1 General
●
Connection of the virtual robotics VJnn and of its virtual tape devices is implemented
via an FC switch.
●
Up to 20 virtual jukeboxes VJnn are supported per CS.
●
In the GXCC configuration virtual drives the vtd line on whose LUN VJnn is configured
is displayed but is not available for tape emulation (so-called shadow device with the
“disabled” identifier in the configuration file). You are therefore recommended if possible
to use a LUN for the robotics which is higher than the number of virtual drives (LUNs).
Note: The FC controller always permits LUNs up to 255. Sample tests with FSC
Networker on Solaris and VJNN on LUN 220 worked.
i
AIX needs the robotics on LUN 0.
●
Windows with VJUK recognizes more than 8 LUNS if a virtual drive and not the virtual
robotics is configured on LUN 0 in CentricStor.
●
Maximum number of volume slots in VJUK:
Emulation
Maximum slots
OEM limit
FSC/CS-TL
61440
ADIC/Scalar-1000
61440
1182
ADIC/Scalar-10K
61440
22938
The slot limit of 61440 can be lower owing to the host platform/backup application.
Edition 7
●
The administration tool “vjukadmin” is supplied for VJUK. The slot sequence of the
drives and media which may need to be taken into consideration for configuring the
backup application is displayed using the inventory command.
●
On Windows 2003, after VJNN, the virtual drives in CentricStor and zoning on the FC
switch have been configured, the LUNS/Tapex are reentered in the registry without any
further action, i.e. also without rebooting Windows 2003, and “unknown autochanger”
and the tape devices (EXABYTE driver for Mammoth2 V2.10 was already present) are
recognized and made operational.
13 October 2006
255
VJUK emulation
256
●
No robotics driver must be installed specially for the CentricStor virtual jukebox in
Windows; the original Microsoft driver is activated automatically (unknown autochanger
from the manufacturer GenChanger with driver version 5.2.3790.0, driver date 1
October 2002 on Windows 2003).
●
VDAS and VACS can mount volumes from VJUK. A collision/operating errors can be
avoided by means of correct configuration or setting up the name ranges on the backup
server.
●
As in the real world, by default VJUK offers the backup application 1 transport unit for
mounting/unmounting logical volumes in virtual drives. In the event of a mount request
(SCSI move request) for restoring the relevant virtual volume from the real tape, VJUK
must consequently wait for the restore from the real tape to be completed and is blocked
for further mount/unmount requests during this period.
●
In the real world, library control via SCSI is not designed for long delays in the case of
SCSI requests. Consequently timeout values in the single-digit minute range are customary in drivers and application programs. In the case of a mount request which requests the virtual volume concerned to be restored from the real tape, SCSI aborts can
be caused by both the operating system and the backup application. In order to prevent
this, prefetch scripts should be used as far as possible so that virtual volumes are read
into a cache in advance.
13 October 2006
Edition 7
NAS filer - NetApp
8.8 NAS filer - NetApp
Miscellaneous
The distinctive feature of the configuration is that the version of NDMP used (version 3)
does not support tape cloning.
CentricStor offers an implicit cloning of tapes, so that now a copy of NDMP backups can be
made without extra burden on NetApp.
Requirements
–
–
NetApp F760 with operating system version ONTAP6.2R2 and FC controller
FC-BA X2045A (QLA2200).
NetApp connection via FC switch
Restrictions
Only the first 16 virtual drives of NetApp are recognized.
Configuration
●
CentricStor ICP
Emulation IBM 3590E
Compression by HOST
●
NetWorker 6.1A10 with EKS 1-5 for Solaris
In /nsr/res/defaults make the following entry:
NSR_DEV_BLOCK_SIZE_3590=256
The NetWorker block size for 3590 must be adapted from default 384k to 256k. This is
because the DUMP command which is implicitly called on NetApp sets 256k as the
maximum block size.
The settings for the timer are as recommended for NetWorker (section “Configuration
Configuration of NetApp devices e.g. “nrst31a” (cmp, norewind) as NDMP devices.
Useful commands
Edition 7
sysconfig -av
show adapter
sysconfig –t
show tapes
reboot
reboot filer
13 October 2006
257
DiskXtender
8.9 DiskXtender
DiskXtender 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, MediaStor and Legato are trademarks of the EMC Corporation.
●
StorageTek is a registered trademark of the Storage Technology Corporation.
●
CentricStor is a trademark of Fujitsu-Siemens Computers GmbH.
8.9.1 Configuration in CentricStor
The expansion for DiskXtender in CentricStor is available as of Release 3.1B4001.
CentricStor should first be configured and connected with the system on which DiskXtender
is running so that the CentricStor tapes are already known there when DiskXtender is installed.
To avoid complications, only the drives required for DiskXtender should be generated, and
only this CentricStor system should be connected to the DiskXtender system at fibre channel level (if necessary select zoning on the FC switch).
8.9.1.1
Virtual Library Services
ACSLS is used for communicating with DiskXtender, i.e. VACS on the CentricStor side. The
following settings must be made to permit this:
Mode:
Enabled
RPC-Port Selection: Default
Access Control:
ON
A client entry must be generated for each extended drive on the DiskXtender side:
Name:
UserId:
<Name or IP address of the DiskXtender system>
<User ID that can be seen in MediaStor >
By default the user ID has the following format:
DX_<Name of the DiskXtender system in upper case>_<Drive letter>
Volumes:
258
<All volumes which may be used for this extended drive>
13 October 2006
Edition 7
DiskXtender
For safety’s sake all volumes should be entered here which are to be used now or later without any already being generated yet since a subsequent modification and the activation
this entails would result in an ACSLS communication breakdown. This causes problems on
the DiskXtender side, i.e. the DiskXtender software can hang. Creation or deletion of a volume during ongoing operation is recognized on the fly on the DiskXtender side.
Example
8.9.1.2
Name:
UserId:
VOLUMES:
willi
DX_WILLI_D
DXD000 - DXD099
Name:
UserId:
VOLUMES:
willi
DX_WILLI_E
DXE000 - DXE099
Logical Drives
Drive Definition:
Compression:
VLS:
Emu/Inquiry Data:
Comment:
LibDevName:
e.g.:
8
practical:
ON
required:
VACS
required:
IBM/IBM 03590E1A
e.g.:
ACS00 - ACS07
generated automatically!
You should note down the LibDevName as it is required for DiskXtender configuration.
8.9.1.3
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:
8.9.1.4
20GB
20 GB
FLOATING
DiskXtender Group
Add Logical Volumes
When creating volumes for DiskXtender a group with a size of 20 GB must be entered as
the logical volume group here.
Edition 7
13 October 2006
259
DiskXtender
8.9.2 Installing DiskXtender
i
8.9.2.1
The character “>” indicates the left mouse button or that the field is passed over.
Special activation with the right mouse button is indicated with “(RMB)>”.
Additional software required
StorageTek Library Attach with the ACSLS protocol is used for library operation. The tape
driver required for operating CentricStor VDrives on Windows Server 2003 is ibmrmsst.sys
for IBM 03590E1A SCSI Sequential Device. Legato MediaStor from EMC is very useful for
support during configuration but is not required for operation.
8.9.2.2
Installing tape drivers
-> Start -> Settings -> Control Panel
->> System
-> Hardware -> Device Manager
(+) Tape drives (open the folder)
(RMB)> IBM 03590E1A SCSI Sequential Device
-> Update Driver ...
Hardware Update Wizard
(X) Install from a list or specific location
(X) Include this location in the search:
<Path of the tape driver package>
IBM MAGSTAR 3590 TAPE DRIVE (for Tivoli Storage Manager)
-> IBM MAGSTAR 3590 TAPE DRIVE
The tape driver must be entered for each drive that is to be used.
8.9.2.3
Installing Library Attach (1.4)
->> Setup.exe
User Name:
Organization:
CentricStor
FSC
(X) Anyone who uses this computer
Host Name:
<IP address of the CentricStor system>
(X) Launch LibAttach Configurator
(X) TCP
( ) UDP
-> Configuration -> Apply -> Yes
Close Window
260
13 October 2006
Edition 7
8.9.2.4
DiskXtender
Installing DiskXtender (6.0)
->> Setup.exe
8.9.2.5
Customer Name:
Organization:
CentricStor
FSC
Domain Name:
User Name:
Password:
Confirm Password:
Target Computers:
<Own computer name> (accept default)
Administrator (accept default)
<Administrator password>
Installing MediaStor (6.0)
->> Setup.exe
Customer Name:
Organization:
CentricStor
FSC
Domain Name:
User Name:
Password:
Confirm Password:
Target Computers:
Administrator (accept default)
Disable Removable Storage Service and continue? -> Yes
Edition 7
13 October 2006
261
DiskXtender
8.9.3 DiskXtender configuration
8.9.3.1
Ascertaining the name of the tapes
-> Start -> Progams -> EMC MediaStor -> Utilities -> SCSI Manager
Note down the names of the IBM 03590E1A entries.
Example
SCSI.2.1.0.0
..
SCSI.2.1.0.7
It is assumed that the last character in the name under “SCSI Manager” is the same as the
last character of the CentricStor VDrive number.
Example
262
SCSI Manager Name
VDrive
LibDevName
SCSI.2.1.0.0
...
SCSI.2.1.0.7
V000
1,0,7,0
V007
1,7,7,0
13 October 2006
Edition 7
8.9.3.2
DiskXtender
Configuring media services
-> Start -> Progams -> EMC DiskXtender File System Manager -> Administrator
-> Service -> Configure Media Services
-> Add
(X) EMC MediaStor
Computer Name: <Own computer name> (accept default)
-> 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>
<LibDevName 2nd character>
<LibDevName 3rd character>
<LibDevName 4th character>
Example
Device Name:
ACS:
LSM:
Panel:
Drive:
SCSI.2.1.0.0
1
0
7
0
Device Name:
ACS:
LSM:
Panel:
Drive:
SCSI.2.1.0.3
1
3
7
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 the services automatically assume the status
“ONLINE”. The Emu boxes have the appropriate color in the “Global Status Monitor” in
CentricStor.
-> Close
Edition 7
13 October 2006
263
DiskXtender
Box:
There are no Extended Drives on this computer.
Would you like to create one now?
-> Yes
Select drive: e.g.: D
-> Schedule
Should be selected as most activities are disabled in the period from
9:00 through 20:00. It is, however, possible to make a change at any
time later.
Then accept the default values until the function has been completed.
Box:
Would you like to add a media folder
to the new extended drive?
-> Yes
Enter Folder Name:
<Name of a folder> (e.g.: folder_to_acsls)
Further extended drives can be created using -> Service -> New Extended Drive ... as described above.
If order to specify a task for the DiskXtender a media group and a rule must still be created.
(RMB)> Media Groups
-> New
Name:
Media Group Type:
Media Type:
<Name of a group> (e.g.: group_to_acsls)
Media
TAPE
In order to see one activity of DiskXtender during the test you could reduce the following
values in the “Options” box:
Cached moves file watermark:
Cached moves data watermark:
10 (or even just 1)
1
In the case of a customer application the parameters must be carefully tailored to the requirements.
(RMB)> Media Rules
-> New
264
13 October 2006
Edition 7
9 Useful commands and information
9.1 Logging, configuration tools, traces in UNIX systems
System logging
Configuration tools
Program trace
Reliant UNIX
/var/adm/log/messages
sysadm
truss
Solaris
/var/adm/messages
WSA
truss
Linux
/var/log/messages
yast
strace
HP-UX
/var/adm/syslog/syslog.log
sam
truss
smit
only from V5
onwards
AIX
1
1
/var/adm/ras/conslog
This file can only be viewed properly with the program smit.
9.2 Display of CentricStor configuration data for the service
engineer
With maintenance authorization, you can set and read the configuration data via the
graphical interface
GXCC➔function bar➔ configuration. There is a full description in the maintenance
manual [1].
The following instructions are addressed to host system administrators who have no
maintenance authorization for CentricStor and need information for setting up a host or real
robot system.
Edition 7
13 October 2006
265
CentricStor configuration data displays for the user
Useful commands and information
9.3 CentricStor configuration data displays for the user
To set up the host configuration, you often need information on which ISP a device
emulation, a library emulation, a device server (PDS) or a library server (PLS) is running.
You receive a compact overview in global status, to start e.g. with:
GXCC main window; Function bar: Tools ➔Global Status.
9.3.1 IP addresses and host names
ISP
The IP addresses of the ISP are shown at the top of the XTCC main window. The host name
is visible in the label of the ISP icon in the GXCC main window.
The IP addresses of the ISP are also contained in the list which can be viewed with:
GXCC main window; Function bar: Administration ➔ Show WWNN and WWPN
Libraries
The IP addresses of real libraries are shown in the GXCC main window in the robot icons
at the bottom of the display and in the related balloon help.
FC switch
The IP addresses or host names of the internal FC switch (or switches) are displayed in the
object information of the FC fabric.
9.3.2 Emulations
The emulations are represented as columns over the host name of their ICP in global
status. If you leave the mouse pointer over the box which represents the emulation or virtual
device, this will display the name of the emulation, the LUN (fibre channel) or the device
name (ESCON) and the number of the assigned controller and the robot address.
In the XTCC of the relevant ICP you can obtain the same information by left clicking the icon
of the emulation or the virtual device. The inquiry data which have been set are displayed
in the icon of the virtual device.
There is a printable overview at
Global Status; Function bar: Tools ➔ Show Balloon Help Summary.
266
13 October 2006
Edition 7
CentricStor configuration data displays for the user
9.3.3 Virtual libraries
The libraries are represented in Global Status by boxes next to the emulations. If you leave
the mouse pointer over the icon, the ISP and emulation type will be displayed.
For VDAS and VACS types, the entered clients are outputted in the balloon info of the icon
in the XTCC window.
The Balloon Help Summary also shows on which ISP the relevant emulation is running.
9.3.4 Real devices (PDS)
In Global Status, the physical drives are shown in a box with the libraries belonging to them.
PDS names and SCSI address CTLs are shown in Balloon Help or in the summary, in order
of ISP.
9.3.5 Real libraries (PLS)
In Global Status, PLSs are represented by a box with the PLS name, the ISP on which the
PLS is running, and the PLS type.
i
SCSI controlled robots are driven by PLS on the ISP to which the SCSI interface of
the robots leads.
The allocation of the PLS to PDS is graphically displayed in the right-hand part of Global
Status.
9.3.6 WWNN and WWPN of the FC connections
GXCC Function bar: Administration ➔ Show WWN’s
A text window with a listing is opened. The data of the host adapter, ordered by ICP, are
shown as “external”.
Edition 7
13 October 2006
267
Control of ADIC / ABBA / AML libraries
9.4 Control of ADIC / ABBA / AML libraries
9.4.1 DASADMIN
In the host
●
The host is the DAS client of VDAS in CentricStor.
The following variables must be set and exported:
DAS_SERVER=<name or IP address of the VDAS servers (see page 267)>
e.g. DAS_SERVER=172.25.95.172
DAS_CLIENT=<name of client (=own name) in configuration>
e.g. DAS_CLIENT=suse7
In CentricStor
●
CentricStor (VLS) is the DAS server for the hosts.
The host should be added to the list of VDAS clients. Its access rights must be set. The
process is described in the maintenance manual under “Configurations ➔ Virtual
Library Services”.
●
CentricStor (PLS) is the DAS client for DAS in AMU-PC.
In this context, DASADMIN can also be started on the PLS host of the CentricStor (in
the general VLP).
The IP address of the AMU-PC is entered under “Configurations ➔ Physical Library
Services”.
Drives (PDS) and library services are brought together as libraries with “Configurations
➔ Tape Libraries”. Here you must also specify if CentricStor takes over the cleaning
management for the drives.
268
13 October 2006
Edition 7
In the AMU PC
CentricStor (PLS) is the DAS client of the DAS server in the AMU.
●
In the DAS server, the service engineer must configure the VLP on which the PLS (or
PLSs) run, as the ACI client for the physical CentricStor drives.
After activating the configuration, there should be a function check of mount and
dismount via dasadmin. For real devices this is done from CentricStor (host of the
relevant PLS), for virtual devices it is done from the hosts.
i
If you wish to perform the physical cleaning of the tape drives for some or all drives
via CentricStor (see section on Configuration ➔ Tape Libraries in the maintenance
manual), then the automatic cleaning for these drives must be deactivated on the
AMU-PC. If “CLN” volume groups are also shown in Global Status next to the
physical volume groups in the library, CentricStor administers the cleaning of the
drives in the corresponding library.
In vtls.conf, the IP address of the server for the physical library is defined in the section
[pls]. The client is defined in the variable “SYSNAME” (also see page 267).
Edition 7
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
13 October 2006
269
9.4.2 Communication between client and server
It is common practice these days to construct firewalls between individual security cells.
Here, we describe how communication works in these cases.
RPC communication for DAS control:
DAS client
DAS server
Enquiry for port of program number: 536875008 via
TCP/UDP Port 111
(in UNIX: rpcinfo –p <DAS server>)
Returns port <XXX>
The port is either located dynamically in the system
after server start or can be assigned in VDAS.
A request is made to the DAS server:
The client finds itself a free port and registers itself with
rpcbind with Port <YYY> and a program number. This
is a number from 40000000 and is increased with
every request. A free port is requested every time.
The rpc function communicates the client program
number, where the response is awaited.
Request to DAS server via TCP/IP Port <XXX>
Enquiry for port of program number which was given
via TCP/UDP Port 111
Returns port <YYY> à
Confirmation message for the request via port <YYY>
The client logs out of rpcbind releases the port <YYY>
again.
270
13 October 2006
Edition 7
9.4.3 Possible problems and solutions
Problem: No connection to VDAS from the SAN host is possible via “dasadmin”.
Edition 7
●
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.
13 October 2006
271
Control of the StorageTek libraries
9.5 Control of the StorageTek libraries
This describes how the physical libraries are operated.
9.5.1 Powderhorn to extend drives
●
Installing and cabling drives
●
Restart LMU with IPL
●
Enter the following commands on the ACSLS-Server:
#kill.acsss
#acsss_config
#rc.acsss
Menu item
7
Y
Y
1
1
/dev/ttya
Y
overwritten
y
Client:
n
Ctrl-c (abort program)
The LOG file is located in /log/acsss_config.log.
However the ACSLS server is administered via cmd_proc .
272
13 October 2006
Edition 7
9.5.2 Cleaning management in StorageTek libraries
If the automatic cleaning for the drives (with STK this applies either for all drives or for none)
is to be switched off and CentricStor has to take over the cleaning, proceed as follows:
1. Call “acsss_config” on the ACSLS computer and select the following menu item:
“3: Set general product behavior variables”
2. From the parameters which are then offered, set “Enable Transport Auto Clean
Option” to “FALSE”.
Make sure that cleaning management is activated in the CentricStor configuration. If “CLN”
volume groups are also shown in Global Status next to the physical volume groups in the
library, CentricStor will administer the cleaning of the drives in the corresponding library.
9.5.3 Adding tapes in Powderhorn
●
The entry slot must be in AUTO Mode. If necessary, switch this on via ACSLS.
●
Then put the tapes into the entry slot and close.
9.5.4 Adding tapes in L180
●
Open the door, and sort the tapes into the slots.
●
Then close the door again. The robot then makes an “inventory run” of all the tapes
found in the library.
9.5.5 Starting the ssi daemon
The ssi daemon needs 3 environment variables:
1. CSI_HOSTNAME=<name of the SUN controller computer with the real robot
or of the VACS host>
2. CSI_CLIENTNAME=<name of client computer>
3. CSI_TCP_RPCSERVICE=TRUE
The ssi daemon is started with the command: ssi 0 50004 23
9.5.6 Stopping the ssi daemon
1. Request the PID with ps –ef | grep ssi.
2. kill –15 <pid>
Edition 7
13 October 2006
273
9.5.7 cmd_proc
In order to be able to use the program, the ssi process must be running.
Operations with cmd_proc:
Inform
query drive all
Mount
mount <VOL> <POS>
e.g. mount TDS004 2,0,0,1
Unload
dismount <VOL> <POS> f
e.g. dismount TDS004 2,0,0,1 f
Show scratch pools
query pool all
Show contents of a scratch pool
query scratch <pool id>
e.g. query scratch 0
Leave program
log off
9.5.8 Communication between client and server
It is common practice these days to construct firewalls between individual security cells.
Here, we describe how communication works in these cases.
274
13 October 2006
Edition 7
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.
Edition 7
13 October 2006
275
Information on the Cashion connection
9.5.9 Possible problems and troubleshooting advice
Problem: No connection to VACS possible from SAN host.
●
Call cmd_proc -p 50099 on the VLP.
●
On the VLP use rcpinfo -p to check whether the rpcbind process works.
●
Is the UDP protocol (see section “Communication between client and server” on
page 274) blocked by a firewall ?
●
Under Windows 2000 and WIN-NT the “Storagetek Libattach” and “PowerRPC
Portmapper” services must be active.
9.6 Information on the Cashion connection
For a Cashion connection over 122 m, 2 COM servers (COM <-> Ethernet) from
W&T1 - Product 586312 - were used which were configured in box-to-box mode.
The configuration is described in the manual3.
The following parameters from the standard package had to be modified here:
●
TCP/IP addresses/configuration (gateway, network masks)
Setting to box-to-box
Standard: 9600,8,N,1
Modification of hardware handshake -> without handshake
●
ISP-COM connection with 9P/9P twisted serial cable. Robot connection with
standard 9P/25P cable.
Connection of the COM servers takes place via a normal LAN.
1
http://www.wut.de
2
http://www.wut.de/e-58631-ww-dade-000.php3
3
http://www.wut.de/e-58w3w-10-inde-000.php3
276
13 October 2006
Edition 7
Information on Fujitsu libraries
9.7 Information on Fujitsu libraries
The control computer of FUJITSU libraries is the PLP. All settings for the FUJITSU library
are made on this, such as adding or deleting clients.
This is done with the lmadmin program which is contained in the
/opt/FJSVlmf/bin directory.
Further information is provided in the following manuals:
–
–
–
–
–
FUJITSU LMF SERVER/CLIENT USER'S GUIDE
ETERNUS LT270 TAPE LIBRARY UNIT INSTALLATION INSTRUCTIONS
ETERNUS LT270 Tape Library User's Guide
ETERNUS LT270 Setup Guide
ETERNUS LT270 Tape Library Maintenance Guide
9.8 Qualified fibre channel switches in the SAN environment
9.8.1 Features of the FC connection
Edition 7
●
Provided that no direct point-to-point connections between host and CentricStor/ICP
are used, all components of the SAN can be connected via a fibre channel switch to the
CentricStor ICPs. The (brocade) switch works here with zoning which can be configured
via Telnet or Internet Explorer. For more information, see the chapter on zoning (see
page 278).
●
Startup sequence: The FC switch must always be switched on first and then the
CentricStor ICPs. If you do not switch on in this sequence FC_AL will be activated
instead of FC point-to-point.
●
If a Linux 8.0 host shares an ICP host connection with other systems (Linux or other),
no part of the configuration may be changed while the system is running. This includes
reboot and shutdown processes of one of the hosts.
13 October 2006
277
Qualified fibre channel switches in the SAN environment
9.8.2 Permitted FC switches
Manufacturer Type
1
Brocade
Silkworm 2800
Ports
FW
Comments
16
V2.1
Silkworm 2800 with emc FC
firmware extension
V2.2.1.a
Silkworm 3800
Silkworm
Connectrix
DS16B
41002
16
V3.1.3
16, 24, 32 V5.1.0a
16
V2.5.0.d
1
Regardless of the switch type used, it is advisable to set the transmission speed explicitly for the port employed
with the portcfgspeed command.
2
If an FC switch Brocade 4100 is used internally or externally in a CentricStor system, problems can occur in the
automatic recognition of the FC topology (LOOP instead of fabric).
The problem can be solved by explicitly preventing the use of LOOP on the port employed: The switch command
portcfggport ensures that LOOP initialization does not take place. You can obtain information about this using
the help command.
9.8.3 Zoning
9.8.3.1
Rules
–
–
The SAN switch must be independent and must not be linked to the internal switch from
CentricStor.
There are 2 different ways to configure zoning:
1. Port zoning (recommended for CentricStor)
2. WWN zoning
Port zoning obliges the use of a strict, but advantageous cable plan. It does not require
any changes to be made to the configuration of the switch when host bus adapters are
exchanged. With WWNN-Zoning, defective GBIC ports can be changed without reconfiguring.
–
–
–
–
278
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.
13 October 2006
Edition 7
9.8.3.2
Zoning example (6 hosts on 3 ICPs)
colorado
RM 600:
Reliant UNIX
Primepower:
Solaris
6
Ports:
ente 2
ente 1
V8
Windows
NT
Windows
2000
8
7
ente 4
ente 3
9
Windows
NT
Windows
2000
11
10
Zones:
6-0, 6-1, 6-2
7-0, 7-1, 7-2
8-3, 10-4
9-3, 11-5
FC switch
(external)
Ports:
0
2
1
3
ICP2
4
5
14
15
V200 ... V21E
V21F
V220 ... V23E
14
15
V100
V101 ... V10F
generic SCSI II
V110
16 LDs
14
ICP0
15
V000 ... V00F
V010 ... V01F
16 LDs
16 LDs
V23F
32 LDs
32 LDs
ICP1
Mammoth2
Mammoth2
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
Edition 7
13 October 2006
279
ente 3 with Windows NT are assigned as follows:
– The first 32 LDs of ICP2 via controller 14
ente 4 with Windows 2000 are assigned as follows:
– The second 32 LDs of ICP2 via Controller 15
This example continues to be widely used in the configuration of Reliant Unix, Solaris and
NetWorker.
9.8.3.3
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 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)
280
port 08
Windows
NT
ente 1
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
13 October 2006
ICP7
Edition 7
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)
9.8.3.4
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
Configuration of the brocade switch via Internet Explorer
Call Administration tools:
Edition 7
13 October 2006
281
Then select “Zone Administration”, enter login “admin” and password.
282
13 October 2006
Edition 7
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
Edition 7
13 October 2006
283
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
284
13 October 2006
Edition 7
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
Edition 7
13 October 2006
285
9.8.3.5
Diagnostics in the event of performance problems
When performance problems occur it may be necessary to look at the data throughput in a
CentricStor system. The easiest way to ascertain the values is on the internal FC switch.
With Brocade switches this is possible using telnet.
Use telnet to go to the switch under the admin ID. You must ask the service provider for
the password for admin. The FC switches a defined under the names FCS0 through FCS3
in the /etc/hosts file.
The following commands can be used to read out information:
fabricshow
Shows the fabric configuration
switchshow
Shows the configuration of the ports and connected WWPN. Interconnect connections and FC speeds are displayed.
zoneshow
Shows the configured and active zones (switch on the frontend or
backend)
portperfshow
Shows the performance on the various ports and Interconnect connections
The session is terminated with the logout command.
If Brocade switches are also installed on the SAN side it is also possible here to perform
objective analyses using the commands mentioned above. In this case the Interconnect
connections in particular must be looked at specifically as they occassionally present a bottleneck.
286
13 October 2006
Edition 7
Host bus adapters (HBA)
9.9 Host bus adapters (HBA)
9.9.1 Overview of the host bus adapters
Tested host bus adapters:
Edition 7
Type
GB Manufac- GBIC present
turer
Comment
LP6205
1
Emulex
no
Will not be tested (RM400-CF02)
LP7000
1
Emulex
no
In RS/6000 with special FW as FC
6227
LP8000
1
Emulex
yes
(RM400-CF10,RM6T5CF10,GP7xx-CF10)
LP9002
2
Emulex
no
LP9802
2
Emulex
no
QLA2100F
1
Qlogic
no
QLA2200F
1
Qlogic
no
QLA2310F
2
Qlogic
no
QLA2340
2
Qlogic
no
QLA2342
2
Qlogic
no
HP FCA2214
2
Qlogic
no
In HP systems
QLA2310-SUN 2
Qlogic
no
In SUN systems
HP5158
1
HP
yes
In HP systems
A5158A
1
Agilent
yes
In HP systems
A6795A
2
Agilent
no
In HP systems
A6826A
2
Qlogic
no
In HP systems
HP FCA2101
2
HP
yes
HP FCA2404
2
HP
no
FCE2-6412-N
1
JNI
no
Sometimes used in SUN
FC6228
2
IBM
no
00P2995/96 (FC 6228)
FC6239
2
IBM
no
In IBM systems (LP9802)
13 October 2006
Is not used as only HUB is
supported
287
9.9.2 Firmware download
9.9.2.1
LP8000
In MSDOS, the current firmware version is loaded onto the LP8000 card with the program
“lputil”. The program and description can be downloaded from the Internet from the
manufacturer's page at: (www.emulex.com).
9.9.2.2
QLA2200F
When using the QLOGIC driver, the driver firmware is loaded to the board.
9.9.2.3
FCE2-6412-N
The current firmware version is available from the manufacturer's Internet site at
(www.jni.com) and can be downloaded with the accompanying tools. The firmware
versions to suit the driver versions are available at the site and are also included in the
installation package.
9.9.3 BIOS settings
9.9.3.1
LP8000
The card works without special BIOS settings.
9.9.3.2
QLA2200F
BIOS settings QLA2200F:
Setting
Default
CentricStor
Host Adapter Settings
Host Adapter BIOS
Disabled
Frame Size
1024
Loop Reset Delay
5 seconds
Adapter Hard Loop ID
Disabled
Hard Loop ID
0
2048
Advanced Adapter Settings
288
Execution Throttle
16
Fast Command Posing
Enabled
13 October 2006
Edition 7
Setting
Default
>4Gbyte Addressing
Disabled
LUNs per Target
8
Enable LIP Reset
No
Enable LIP Full Login
Yes
Enable Target Reset
No
Login Retry Count
8
Port Down Retry Count
8
Drivers Load RISC Code
Enabled
Enable Database Updates
No
Disable Database Load
No
IOCB Allocation
256 buffers
Extended Error Logging Disabled
Disabled
CentricStor
32
64
Extended Firmware Settings
9.9.3.3
Extended Control Block
Enabled
RIO Operation Mode
0
Connection Options
3
Class 2 Service
Disabled
ACK0
Disabled
Fibre Channel Tape Support
Disabled
Fibre Channel Confirm
Disabled
Command Reference Number
Disabled
Read Transfer Ready
Disabled
Response Timer
0
Interrupt Delay Timer
0
1
enabled
FCE2-6412-N
In Solaris, it is not necessary to configure the card in BIOS.
Edition 7
13 October 2006
289
Example of a filter bridge for separating CentricStor™
9.10 Example of a filter bridge for separating CentricStor™
9.10.1 General
The problem that customers want to be certain that CentricStor does not open a back door
into their computer centers repeatedly raises its ugly head. One approach to solve this is a
filter bridge between CentricStor and the rest of the computer center on the basis of a
LINUX PC. The following is intended as an aid to solving this problem.
●
A conventional PC with at least 2 network interfaces can be used.
●
The LINUX system used in the CentricStor development was, for example, SuSE
SLES9 Rcxx. Linux 2.6.5-7.97 is supplied as the kernel, and this is sufficient. However,
the userland commands brctl and ebtables are not available. These were
obtained from the Internet as a source and compiled and installed.
●
The system contains the start/stop script “bridge” which you can copy with cut&paste to
the /root ID, for example. The commands are then:
Start:
Stop:
Status:
sh /root/bridge start
sh /root/bridge stop
sh /root/bridge status
●
The bridge configuration is also available on the system and should be copied under
the ID /etc/sysconfig, otherwise the “bridge” script must be adjusted. Adjustments
are only required in this configuration file. You have a free hand in designing the set of
rules RULES_xx, provided you bear in mind that the set of rules is interpreted/evaluated
several times by the shell before it is executed. It is advisable to use the example below
as a guide.
●
The ports used by CentricStor are described after the scripts.
9.10.2 Start/stop script bridge
#! /bin/sh
#
# /etc/sysconfig/csbridge
#
### BEGIN INIT INFO
# Provides:
CentricStor
# Required-Start: network
# Required-Stop: network
# Default-Start: 2 3 5
# Default-Stop:
290
13 October 2006
Edition 7
# Description:
Start the system filtering bridge
### END INIT INFO
LV=èxpr \ùname -r\` : '$...$.*'`
BRCTL=`which brctl`
EBTABLES=`which ebtables`
IPTABLES=`which iptables`
IFCONFIG=`which ifconfig`
. /etc/rc.status
rc_reset
[ "$BRCTL" -a "$EBTABLES" -a "$IFCONFIG" ] || {
echo -n "$0: one or more commands not found"
false; rc_status
rc_exit
}
. /etc/sysconfig/csbridge
[ "$CSBRIDGE" = yes ] || exit 0
[ "$LV" ] && expr $LV \< 2.6 >/dev/null && {
echo -n "$0: Linux Kernel has to be 2.6 or newer"
false; rc_status
rc_exit
}
get_ip () {
IF=$1
ifconfig $IF | sed -ne '/inet addr:/s/.*inet addr:$[09\.]*$.*$/\1/p'
}
get_mask () {
IF=$1
ifconfig $IF | sed -ne '/Mask:/s/.*Mask:$[0-9\.]*$.*$/\1/p'
}
get_bridges () {
ls -1 /sys/class/net | egrep '^br[0-9]'
}
reset_ebtables () {
$EBTABLES -F
$EBTABLES -t
$EBTABLES -X
$EBTABLES -t
$EBTABLES -P
$EBTABLES -P
Edition 7
broute -F
broute -X
INPUT ACCEPT
OUTPUT ACCEPT
13 October 2006
291
$EBTABLES -P FORWARD ACCEPT
[ -f /tmp/ebtabsav ] && sh /tmp/ebtabsav
}
reset_iptables () {
$IPTABLES -F
$IPTABLES -t
$IPTABLES -X
$IPTABLES -t
$IPTABLES -P
$IPTABLES -P
$IPTABLES -P
}
nat -F
nat -X
INPUT ACCEPT
OUTPUT ACCEPT
FORWARD ACCEPT
get_brif () {
BR=ècho $1| sed -e 's/^br//'`
$BRCTL show |
awk '
BEGIN { run=0 }
/^br'"$BR"'/ { run=1 }
/^br[^'"$BR"']/ { run=0 }
{ if ( run == 1 ) print $NF
}'
}
portof () {
SERVICE=$1
PROTO=$2
egrep '^'$SERVICE'[ ].*/'$PROTO /etc/services | sed -e 's@/.*@@' -e
's/^.*[ ]//'
}
macof () {
cat /sys/class/net/$1/address
}
get_brif () {
BR=ècho $1| sed -e 's/^br//'`
$BRCTL show |
awk '
BEGIN { run=0 }
/^br'"$BR"'/ { run=1 }
/^br[^'"$BR"']/ { run=0 }
{ if ( run == 1 ) print $NF
}'
}
292
13 October 2006
Edition 7
case "$1" in
start)
echo -n "Starting csbridge services"
$0 probe >/dev/null && {
true ; rc_status -v
rc_exit
}
[ "$CSBRIDGES" ] || {
false ; rc_status
rc_exit
}
echo; echo " saving ebtables / iptables "
echo "EBTABLES=$EBTABLES" >/tmp/ebtabsav
echo "IPTABLES=$IPTABLES" >>/tmp/ebtabsav
$EBTABLES -L | sed -e 's/,.*: / /' -ne '/Bridge chain:/s/Bridge
chain:/$EBTABLES -P /p' >> /tmp/ebtabsav
$EBTABLES -L --Lx >>/tmp/ebtabsav
$EBTABLES -t broute -L --Lx >>/tmp/ebtabsav
echo "echo \"`cat /proc/sys/net/ipv4/ip_forward`\" >
/proc/sys/net/ipv4/ip_forward" >>/tmp/ebtabsav
echo -n " creating csbridges "
for i in $CSBRIDGES ; do
echo -n "br$i "
IF_IP=""
IF_MASK=""
for j in èval echo \\\$CSPUBLIC_$i \\\$CSPRIVATE_$i` ; do
IF_IP_T=`get_ip $j`
[ "$IF_IP" -a "$IF_IP_T" ] && {
# Fehler
echo
echo "You listed more than 1 configured interface for the
bridge br$i"
false ; rc_status ; rc_exit
}
[ -z "$IF_IP" ] && {
IF_IP=$IF_IP_T
IF_MASK=`get_mask $j`
}
done
$BRCTL addbr br$i ; rc_status
for j in èval echo \\\$CSPUBLIC_$i \\\$CSPRIVATE_$i` ; do
echo ; echo -n "
setting up interface $j for bridge br$i"
$BRCTL addif br$i $j ; rc_status
$IFCONFIG $j down ; rc_status
$IFCONFIG $j 0.0.0.0 promisc up ; rc_status
done
Edition 7
13 October 2006
293
[ "$IF_IP" ] && {
echo ; echo -n "
setting up interface br$i"
$IFCONFIG br$i $IF_IP netmask $IF_MASK promisc up ; rc_status
}
[ "èval echo \\\$RULES_$i`" ] && {
echo ; echo -n "
setting up ebtables for bridge br$i"
[ -f "èval echo \\\$RULES_$i`" ] && {
sh èval echo \\\$RULES_$i` ; rc_status
} || {
eval echo \"ècho \\\$RULES_$i`\" | sh ; rc_status
}
}
done
echo ; echo -n "csbridge needs about 30 seconds to initialize"
echo ; echo -n "
- please give me some time"
rc_status -v
;;
stop)
echo -n "Shutting down csbridge services"
BRIDGES=`get_bridges`
echo -n " - Bridges: "$BRIDGES
[ "$BRIDGES" ] || {
true; rc_status -v
rc_exit
}
for i in $BRIDGES ; do
BR_NR=ècho $i | sed -e 's/br//'`
BR_IF=`get_brif $i`
$IFCONFIG $i down
for j in $BR_IF ; do
[ "$j" = "no" ] || {
$IFCONFIG $j down
$BRCTL delif $i $j ; rc_status
}
done
$BRCTL delbr $i ; rc_status
done
reset_iptables ; rc_status
reset_ebtables ; rc_status
/etc/init.d/network restart
rc_status -v
;;
try-restart)
$0 stop && $0 start
rc_status
;;
restart)
294
13 October 2006
Edition 7
$0 stop
$0 start
rc_status
;;
reload|force-reload)
;;
status)
echo "Checking for service csbridge:"
$BRCTL show
; rc_status
$EBTABLES -L --Ln
; rc_status
$IPTABLES -vL --line-numbers ; rc_status
rc_status -v
;;
probe)
echo -n "csbridge: "
ls /sys/class/net/br* >/dev/null 2>&1 && {
echo " configured"
exit 0
} || {
echo " unconfigured"
exit 1
}
;;
*)
echo "Usage: $0 {start|stop|status|try-restart|restart|forcereload|reload|probe}"
exit 1
;;
esac
rc_exit
9.10.3 Configuration file: csbridge
## Path:
Network/CSbridge
## Description:
## Type:
yesno
## Default:
yes
## Config:
kde,profiles
#
# Enable a filtering bridge for use in CS environment.
# This setting allows to turn the CSbridge on and off while
# preserving the particular network setup.
#
CSBRIDGE="yes"
## Type:
Edition 7
string
13 October 2006
295
## Default: ""
#
# CSBRIDGES is the list of bridges to be initialized
# example: CSBRIDGES="0 1 2" enables three bridges
# with the public interfaces CSPUBLIC_0, CSPUBLIC_1 and CSPUBLIC_2
# and the private interfaces CSPRIVATE_0, CSPRIVATE_1 and CSPRIVATE_2
# and creates the virual interfaces br0, br1 and br2,
#
# active interfaces of the standard network configuration
# are mapped to the br interfaces.
# If the count of defined bridges does not match the
# count of configured interfaces, csbridge will not start
#
CSBRIDGES="0"
## Type:
string
## Default: ""
#
# CSPUBLIC/PRIVATE_xx are lists of interfaces
# to be used by bridge xx
# up to now, only 1 element per list is allowed
# Example:
# CSPUBLIC_0="eth0"
# CSPRIVATE_0="eth1"
#
CSPUBLIC_0="eth0"
CSPRIVATE_0="eth2"
## Type:
string
## Default: ""
#
## Type:
string
## Default:
""
#
# PROTECTED_HOSTS_xx are lists of IP-Addresses
# to be used by bridge xx
# Example:
# PROTECTED_HOSTS_0="172.25.95.144" # Host: columbia
#
PROTECTED_HOSTS_0="172.25.95.144 172.25.95.166"
## Type:
## Default:
string
""
macof () {
cat /sys/class/net/\$1/address
}
296
13 October 2006
Edition 7
# RULES
#
RULES_0="
portof () {
SERVICE=\$1
PROTO=\$2
egrep '^'\$SERVICE'[
].*/'\$PROTO /etc/services | sed -e
's@/.*@@' -e 's/^.*[
]//'
}
echo 1 > /proc/sys/net/ipv4/ip_forward ;
$EBTABLES -P INPUT ACCEPT ;
$EBTABLES -P FORWARD ACCEPT ;
$EBTABLES -P OUTPUT ACCEPT ;
# DIRECTION : both
$IPTABLES -t filter -P FORWARD DROP;
#
PROTO=tcp ;
for ir0 in ntp sunrpc 9669 6996 domain 2000 ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
ir0=\`portof \$ir0 \$PROTO\`;
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT
done ;
# next block can be deleted if working with fixed ports in VLS
for ir0 in 1024:65535 ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT
done ;
;
;
;
;
$IPTABLES -t filter -A FORWARD -p icmp --icmp-type 8 -j ACCEPT
PROTO=udp ;
for ir0 in ntp snmp snmptrap sunrpc domain ; do
[ \"\èxpr \\\"\$ir0\\\" : '$[0-9:]*$'\`\" = \"\$ir0\" ] ||
$IPTABLES -t filter -A FORWARD -p \$PROTO --dport \$ir0 -j ACCEPT ;
$IPTABLES -t filter -A FORWARD -p \$PROTO --sport \$ir0 -j ACCEPT ;
done ;
#
$IPTABLES -t filter -A FORWARD -j ACCEPT -m state --state
ESTABLISHED,RELATED;
#
# PROTECTED_HOSTS_0 will be REJECTED, not DROPPED
if [ \"$PROTECTED_HOSTS_0\" ] ; then
$IPTABLES -N HOSTREJ ;
# $IPTABLES -P HOSTREJ DROP ;
Edition 7
13 October 2006
297
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;
"
298
13 October 2006
Edition 7
9.10.4 Ports used by CentricStor
Port
Service
Protocol
Service
111
sunrpc
udp
RPC services
6996
tcp
GXCC (can be locked if “single mode” is used in
GXCC)
9669
tcp
GXCC
ICMP
Ping (GXCC works with this)
Typ 8
When the DAS interface is used
xxxx
tcp
A fixed DAS port can be defined for VDAS with firewall
option. sunrpc (port 111) can then be locked.
xxxx
tcp
VDAS port for RPC can be permanently assigned.
When the ACSLS interface is used
xxxx
Edition 7
tcp
VACS port for RPC can be permanently assigned.
7
echo
tcp
When using CSC from BS2000
7
echo
udp
When using CSC from BS2000
25
smtp
tcp
If the VLP sends mail
53
domain
tcp
If the VLP operates with DNS, e.g. sends mail
53
domain
udp
If the VLP operates with DNS, e.g. sends mail
123
ntp
tcp
If NTP is used
123
ntp
udp
If NTP is used
161
snmp
udp
If CentricStor SNMP is monitored
162
snmptrap udp
If CentricStor SNMP is monitored
xxxx
tcp
RPC port in the PLS configuration with firewall
50050+
<PLS
No>
tcp
ssi port for reply from ACSLS server (e.g. 50052 for
PLS2)
13 October 2006
299
10 Installation of the GUI software GXCC/XTCC
10.1 General
10.1.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 Installation Guide.
10.1.2 Information about restrictions and known bugs
Restrictions and known bugs are described in section “Restrictions and known bugs” on
page 321.
10.2 Installation descriptions
This CD-ROM can be used to install the GUI software required for the monitoring of a
CentricStor system. The GUI software was tested on the operating systems MS-Windows
95/98/NT/2000/XP, LINUX, SOLARIS, and SINIX-Z. The software to be installed includes
the base software Tcl/Tk and the GUI software components GXCC and XTCC. In the
following the procedures for installing the software packages on the various operating
systems are described.
Edition 7
13 October 2006
301
Installation descriptions
Installation of the GUI software GXCC/XTCC
10.2.1 Installation on MS-Windows Platform
The operating systems supported are MS-Windows 95/98/NT/2000 and XP. On these
platforms the base software Tcl/Tk is integrated in the GUI software packet (GXCC and
XTCC). Versions of Tcl/Tk, including all associated links, that are already installed at the
time of installation, are not affected by the installation process per se. Any available configuration data in the file hosts.txt will automatically be saved.
i
On a multi-user system (such as MS-Windows NT/2000/XP), the installation and
deinstallation must be performed under an administrator account. However, the
programs can be started from any account via the menu Start. Certain administration functions, however, do require an administrator account.
Names of files and directories can be displayed by MS-Windows in different ways
(e.g. name.ext, Name.ext, NAME.EXT). This has, however, no significance.
Names of folders, window titles, button labels and message texts depend on the
language option of MS-Windows and may deviate from this description.
Information about unattended installation can be found in section “Unattended Installation
/ Deinstallation under MS-Windows” on page 318.
10.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 gui86en.exe using the left
mouse key.
The installation of the software starts.
A complete installation encompasses the following components:
302
●
Graphical User Interface: GUI software GXCC and XTCC
●
GXCC Observe Mode Shortcut: This is a symbol on the Desktop for calling GXCC in
Observe Mode
●
GXCC Demo (FALKE): Demonstration files for GXCC
●
CA Unicenter Integration Tools: Extensions in the CA Unicenter software for CentricStor
13 October 2006
Edition 7
Using a selection window, it is possible to exclude specific components from the installation
process.
i
Should the tools required for the installation and deletion of CA-Unicenter extensions on MS-Windows NT/2000 Systems be needed, then the "CA Unicenter
Integration Tools" components must not be deselected.
By selection of the component "GXCC Demo (FALKE)" the snapshot files required
for the offline mode (refer to section “Offline Mode” on page 313) will be included.
During the installation of the GUI software, the user will be guided through the process by
means of various self explanatory dialogue windows. All individual windows containing the
buttons "Next" or "Install" must be acknowledged. The concluding window Setup has finished
installing... causes the installation to terminate successfully when the button "Finish" is
pressed.
10.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 CentricStor system being monitored. The documentation of
the GUI programs GXCC and XTCC can optionally be installed to ensure that it is accessible even when no connection has been established to a CentricStor system (offlinemode). Depending on actual availability it consists of the complete CentricStor service
and/or user manual or it consists of selected chapters from the service and/or user manual,
concerning the graphical user interface.
!
CAUTION!
Because the documentation will be copied into the folder doc of GXCC, it is
important to perform the following steps after the installation of the GUI software
(section “How to proceed” on page 302):
1. Insert the CD-ROM into the CD drive, if not yet done.
2. Open the CD-ROM folder Windows and double click the file doc86en.exe using the left
mouse key.
The installation of the documentation starts.
During the installation some self explanatory dialogue windows containing the buttons
"Next" or "Install" must be acknowledged. The concluding window Setup has finished
installing... causes the installation to terminate successfully when the button "Finish" is
pressed.
Edition 7
13 October 2006
303
10.2.1.3
Starting the GUI Software
A menu structure with the following functions is displayed via Start => Programs => Fujitsu
Siemens Computers => V6 Control Center:
●
GXCC
–
–
–
●
XTCC
–
–
–
●
Add CentricStor to CA Unicenter
Delete CentricStor from CA Unicenter
SNMP Integration Liesmich
SNMP Integration Readme
Try to repair inoperable GXCC or XTCC
Uninstall the FSC V6 Control Center
Tools
–
–
–
304
XTCC Observe Mode
XTCC User Mode
XTCC Service Mode
Setup
–
–
–
–
–
–
●
GXCC Observe Mode
GXCC User Mode
GXCC Service Mode
Global Status (large)
Global Status (small)
Recorder
13 October 2006
Edition 7
10.2.1.4
Creating the CA-Unicenter Extensions for CentricStor
During the installation of the GUI Software, various tools for the installation and deletion of
the CA-Unicenter extensions are installed provided that the CA Unicenter Integration Tools
components has not been deselected.
On a multi user system (MS-Windows NT/2000/XP), these tools can only be installed under
the account of the user (with administration privileges) who installed the GUI Software.
Guidance for the operation will be given by invoking Start => Programs => Fujitsu Siemens
Computers => V6 Control Center => Setup => SNMP Integration Readme.
For the installation of the extensions the tool Start => Programs => Fujitsu Siemens Computers
=> V6 Control Center => Setup => Add CentricStor to CA-Unicenter should be invoked. This tool
copies all files necessary for the operation of the CA-Unicenter to the appropriate directories.
By invoking Start => Programs => Fujitsu Siemens Computers => V6 Control Center => Setup =>
Delete CentricStor from CA-Unicenter the extensions can be deleted.
10.2.1.5
Deinstallation of the Software
After invocation of Start => Programs => Fujitsu Siemens Computers => V6 Control Center =>
Setup => Uninstall the FSC Control Center a window with title FSC V6 Tape Control Center
(v6_cc) Uninstall will be displayed asking "Are you sure that you want to completely
remove FSC V6 Control Center (v6_cc) and all of its components ?". Pressing
"Yes" starts the deinstallation of both, the GUI software and the documentation. By pressing
"No", deinstallation can be cancelled. Any available configuration data in the file hosts.txt
will automatically be saved.
Information about unattended deinstallation can be found in section “Unattended Installation / Deinstallation under MS-Windows” on page 318.
10.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>.
Edition 7
13 October 2006
305
10.2.2 Installation on a LINUX Platform
10.2.2.1
How to proceed
The installation has to be performed under the user account root.
1. Insert the CD-ROM into the CD drive.
2. Mount the CD-ROM on the file system:
mount /cdrom
3. Select the LINUX directory on the CD-ROM:
cd /cdrom/Linux
4. List the content:
ls
Within the displayed file names following files are required for installing the GUI
software:
xtcc-<version>.i386.rpm
gxtcc-<version>.noarch.rpm
gxtcc-doc-<version>.noarch.rpm
gxtcc-docd-<version>.noarch.rpm
gxtcc-doce-<version>.noarch.rpm
5. Install these three packets in the following sequence:
a) rpm -i xtcc-<version>.i386.rpm
b) rpm -i gxtcc-<version>.noarch.rpm
c) rpm -i gxtcc-doc-<version>.noarch.rpm
d) rpm -i gxtcc-docd-<version>.noarch.rpm
e) rpm -i gxtcc-doce-<version>.noarch.rpm
306
13 October 2006
Edition 7
10.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 /usr/local/bin/gxcc, and for XTCC
the program /usr/local/bin/xtcc should be invoked. The path name can be omitted, if
the directory /usr/local/bin is included within the search path for programs. Startup in
service mode, observe mode, or user mode is accomplished via options -service,
-observe, or -user. If no option is specified, the program is started in user mode.
Syntax of command line input:
/usr/local/bin/gxcc [-service | -observe] [&]
/usr/local/bin/xtcc [-service | -observe] [&]
10.2.2.3
Deinstalling the GUI Software
The deinstallation has to be performed under the user account root in the following
sequence:
1. rpm -e gtxcc
2. rpm -e xtcc
3. rpm -e gtxcc-doc
4. rpm -e gtxcc-docd
5. rpm -e gtxcc-doce
10.2.3 Installation on a SOLARIS Platform
The installation has to be performed under the user account root of the SOLARIS system.
It includes the base software Tcl/Tk and the GUI software GXCC and XTCC. The installation has been tested with SPARC SOLARIS Version 8.
10.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.
Edition 7
13 October 2006
307
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.
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 /cdrom
2.
List the contents:
ls
3. Select the directory of the GUI-CD:
cd 'CentricStor GUI'
4. List the contents:
ls
5. Select the directory of the Solaris Platform:
cd Solaris
6. List the contents:
ls
308
13 October 2006
Edition 7
7. 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).
8. Release the CD-ROM via the command eject in the root directory.
10.2.3.2
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.
10.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 SMAWLmk4
4. pkgrm SMAWLtcl
5. pkgrm SMAWLtk
6. pkgrm SMAWLgdc
7. pkgrm SMAWLgdd
8. pkgrm SMAWLgde
Edition 7
13 October 2006
309
10.2.4 Installation on a SINIX-Z Platform
The installation has to be performed under the user account root. It includes the base
software Tcl/Tk and the GUI software GXCC and XTCC.
!
10.2.4.1
WARNING!
The installation is only intended for "pure" SINIX-Z platforms. On SINIX-2000-Z
machines (in particular SAE, CentricStor) the GUI software must not be installed
from of this CD-ROM. For these machines other officially released procedures exist
for installing the GUI software.
How to proceed
1. Insert CD-ROM into the CD drive.
2. Start the installation by invoking the following command:
cdinst
3. Follow the instructions within the displayed FMLI window:
a) Window 1 Process Multi-Product CD-ROM: Respond by pressing F3 (Save).
b) Window 2 CENTRICSTOR_GUI: Respond by pressing F8 (Continue).
c) Window 3 CENTRICSTOR_GUI: Item SINIX-Z CENTRICSTOR_GUI Graphic User
Interface(GUI) for CentricStor: Mark with F2 and accept by pressing the Enter key.
Then the following actions are displayed:
info
pkginfo
README
install
d) Select "install" and accept by pressing F3 (Enter).
e) Window 4 Install: The default values should be accepted by pressing F3 (Save).
The installation starts.
Installation is completed when the prompt "Press ENTER to continue" is displayed. After
pressing the Enter key, Window 3 will be displayed again, and has to be closed by pressing
F6. Window 4 should be closed by pressing F8 (Exit). This completes the processing of the
command "cdinst".
310
13 October 2006
Edition 7
10.2.4.2
mode as start parameter. GXCC is invoked via the program gxcc, XTCC via the program
xtcc. Startup in service mode, observe mode, or user mode is accomplished via options
-service, -observe, or -user. If no option is specified, the program is started in user
mode.
10.2.4.3
Deinstalling the Software
The deinstallation has to be performed under the user account root by invoking the
commands below in the given sequence.
After entering each command the message "The following package is currently
installed:" will be displayed followed by additional information about the package. The
question "Do you want to remove this package?" should be answered with "y".
1. pkgrm GlbXtcc
2. pkgrm BrkXtcc
3. pkgrm tcl
4. pkgrm GlbDoc
5. pkgrm GlbDocd
6. pkgrm GlbDoce
Edition 7
13 October 2006
311
Online Documentation of the GUI Software
10.3 Online Documentation of the GUI Software
10.3.1 General
The GUI software includes the capability to automatically access, provide and update the
online documentation for the CentricStor system being monitored.
During the installation of the GUI programs GXCC and XTCC their documentation will also
be installed to ensure that it is accessible even when no connection has been established
to a CentricStor system (offline-mode). Depending on actual availability it consists of the
complete CentricStor service and/or user manual or it consists of selected chapters from
the service and/or user manual, concerning the graphical user interface.
10.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 CentricStor <version> Service manual (complete) will be
displayed, if the complete service manual exists, or an entry CentricStor <version> Service
manual (GUI-Part) will be displayed, if only the chapters concerning the graphical user
interface are available.
In case of user mode and observe mode an entry CentricStor <version>User manual
(complete) will be displayed, if the complete user manual exists, or an entry CentricStor
<version>User manual (GUI-Part)) will be displayed, if only the chapters concerning the
graphical user interface are available. The service mode will be handled like the user and
observe mode if no service manual is available.
Invoking this function leads to the display of the service or user manual with a PDF viewer.
For this purpose a PDF viewer must be installed on the system:
–
–
–
–
On a MS-Windows platform: Acrobat Reader
On a LINUX platform: xpdf or acroread
On a Solaris platform: acroread
On a SINIX-Z platform: xpdf
!
312
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.
13 October 2006
Edition 7
Offline Mode
10.4 Offline Mode
Usually the display generated by the GUI software is based on data, which are periodically
received from an active CentricStor system. The communication partner within the active
system is the InfoBroker. For demonstration purposes the GUI software can take the data
from a file, and display the information of an inactive CentricStor system, described by these
data. This way of operation will be called "offline mode" in the following, the file will be called
a snapshot file.
When GXCC is running on a system which does not contain the InfoBroker, a window Mode
Select will be automatically displayed to the user, containing an option button for setting the
operation mode. Via the option File the user chooses the offline mode, and in the window
File Select the user may determine the snapshot file. The user may use the default snapshot
file or select a snapshot file from an arbitrary directory via the button "Browse". After determining the snapshot file the GUI software displays the name of the CentricStor system
which is described by the snapshot file.
When GXCC is running on a system which contains the InfoBroker, the system described
will be displayed automatically. In order to choose in this case the offline mode one has to
invoke the function Open from the menu File of the GXCC window. Then the window File
Select will be displayed to the user, offering the functions described above.
During the installation of GXCC the directory TEST for snapshot files will be created. The
snapshot file gxtcc.gxd will be created in this directory. It is proposed as default in the
window File Select. Additional files are provided on the CD-ROM for demonstration
purposes. They have to be copied manually into the appropriate directory in order to use
them.
Edition 7
13 October 2006
313
Offline Mode
10.4.1 Integrating the Snapshot Files
In the following the procedures for copying the snapshot files onto the various operating
platforms is described under the appropriate headings.
10.4.1.1
MS-Windows Platform
i
The following steps are only required, if during installation setup of the GUI software
the component GXCC Demo (FALKE) has been deselected; otherwise the additional
files are already present.
The installation is to be done as follows:
1. Insert the CD-ROM into the CD drive if not already done.
2. Open the Windows directory on the CD and double click the left hand mouse button on
the file gui86en.exe.
3. The displayed Installation directory must be incorporated using the "Next" button.
4. A window appears with the title Directory Exists followed by the message "The
directory '<Installation_directory>' already exists. Would you like
to install to that directory anyway ?" This question should be replied to in
the affirmative by means of "Yes".
5. By selecting the component GXCC Demo (FALKE), the additional installation of the
necessary snapshot files is prepared.
6. All subsequent windows are to be acknowledged with the "Next" or "Install" buttons.
7. In the final window Setup has finished installing... clicking on the "Finish" button concludes
the installation process.
10.4.1.2
LINUX Platform
1. Mount the CD-ROM on the file system:
mount /cdrom
2. Select the CD-ROM directory which contains the snapshot files:
cd /cdrom/demo/TEST
3. Copy all snapshot files (including directories) into the directory prepared by GXCC:
cp -r * /usr/apc/gxtcc/TEST
314
13 October 2006
Edition 7
10.4.1.3
Offline Mode
SOLARIS Platform
In case of operating the system via the CDE user interface a window File Manager will
be displayed automatically with the directory of the CD-ROM.
2. Open the directory demo by double clicking the icon of this directory with the left mouse
button.
3. Open the directory TEST by clicking the icon of this directory with the left mouse button.
4. Select all files and folders by invoking the function Select All in the menu Select within the
window File Manager of the CD-ROM.
5. Open a new window File Manager for the target for the snapshot files via the workspace
menu of the desktop (i.e. positioning the mouse pointer on the desktop background and
pressing the right mouse button). There the function File Manager has to be invoked
within the submenu entry Files.
6. Open the target directories /opt/SMAW/SMAWLglb/gxtcc/TEST, by opening sequentially all directories of this path by double clicking the icon of each directory with the left
mouse button.
7. Copy the highlighted snapshot files via drag&drop into the target directory. All
highlighted files implicitly are also transferred.
8. Close the window File Manager for the target of the snapshot files.
9. Release the CD-ROM by invoking the function eject in the menu File in the window File
Manager.
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 /cdrom
ls
3. Select into the directory of the GUI-CD:
cd centricstor<version>
ls
Edition 7
13 October 2006
315
Offline Mode
5. Select the CD-ROM directory containing the snapshot files:
cd demo/TEST
6. Copy all snapshot files (including directories) into the directory prepared by:
cp -r * /opt/SMAW/SMAWLglb/gxtcc/TEST
7. Release the CD-ROM via the command eject in the root directory.
10.4.1.4
SINIX-Z Platform
1. Determining the device node of the CD drive:
ls /dev/dsk/*cdr*
2. Mount the CD-ROM on the file system of the system:
mount -F hs -o ro,dos <Device node of CD drive> /cdrom <Device node
of CD drive>
3. Select the CD-ROM directory containing the snapshot files:
cd /cdrom/demo/test
4. Copy all snapshot files (including directories) into the directory prepared by GXCC:
cp -r * /usr/apc/gxtcc/TEST
316
13 October 2006
Edition 7
Offline Mode
10.4.2 Functionality in Offline Mode
The data of a snapshot file reflect either a snapshot or a maximum 2 hour period of the
history of a CentricStor systems. The covered time period determines whether the display
in the Global-Status-Monitor is static or dynamic. In case of a static display the picture does
not change, since the data only reflect a single point in time. In case of a dynamic display
the picture is updated periodically, according to the data which correspond to the period
currently reflected.
Both kinds of snapshot files can be distinguished by the name suffix. A file with the suffix
gxd contains a single snapshot only, whereas a file with the suffix db covers a whole period.
10.4.2.1
Static Display
Starting GXCC in offline mode will always display a static picture of a CentricStor system.
For each ISP in the display there is a function menu provided containing the function Show
Details (XTCC), which opens a XTCC window in offline mode and displays a static picture
of the concerned ISP.
In the menu Tools of the GXCC menu bar the Global-Status-Monitor can be started. If there
is only one snapshot file of type gxd of the concerned system (i.e. there is no additional file
*.db), the stored operational data are only displayed in a static picture. The display of
performance data is not included, because it only reflects a snapshot.
10.4.2.2
Dynamic Display
If a snapshot file of type db exists for the system already being displayed in GXCC, then the
GXCC-Recorder tool will be activated when the Global-Status-Monitor is started in offline
mode. This tool delivers to the Global-Status-Monitor periodically the operational data
which are stored in the snapshot file for the concerned time period. The Global-StatusMonitor updates the display according to the data delivered. When operational data
changes, changes become visible in the picture displayed by the Global-Status-Monitor, but
not in GXCC.
The tool GXCC-Recorder also supports the sequential display of snapshot files of different
systems (this is called ROTATE mode). In order to do so the user has to select the corresponding snapshot files of type db within the application window of the GXCC-Recorder.
When a snapshot file changes, then the GXCC display changes also.
Edition 7
13 October 2006
317
Unattended Installation / Deinstallation under MS-Windows
Installation of the GUI software
10.5 Unattended Installation / Deinstallation under MS-Windows
10.5.1 Setup Command Line Parameters
The Setup programs gui86en.exe / doc86en.exe accept the following command line
parameters:
/SPDisables the This will install... Do you wish to continue? prompt at the beginning of Setup.
/SILENT
The wizard and the background window are not displayed. The installation progress
window is displayed. Error messages during installation are displayed. The startup
prompt is displayed if you haven't disabled it with the /SP- command line option.
/VERYSILENT
The wizard, the background window, and the installation progress window are not
displayed. Error messages during installation are displayed. The startup prompt is
displayed if you haven't disabled it with the /SP- command line option.
/SUPPRESSMSGBOXES
Instructs Setup to suppress message boxes. Only has an effect when combined with
/SILENT and /VERYSILENT.
/DIR='x:\dirname' 1
Overrides the default directory name normally displayed on the Select Destination
Directory wizard page. A fully qualified pathname must be specified. Don't forget to use
quotes if the dirname contains spaces.
/COMPONENTS='comma separated list of component names' 1
This parameter is only valid for gui86en.exe: Overrides the default components
settings. Using this command line parameter causes Setup to automatically select
Custom type.
Component names used for the CentricStor GUI:
gui
ico
dem
uni
1
Graphical User Interface
GXCC Observe Mode Shortcut
GXCC Demo (FALKE)
CA Unicenter Integration Tools
optional
318
13 October 2006
Edition 7
Unattended Installation / Deinstallation under MS-
/SAVEINF='filename' 1
Instructs Setup to save installation settings to the specified file. Don't forget to use
quotes if the filename contains spaces.
SAVEINF file example:
[Setup]
Dir=C:\Programme\FSC 2
Group=Fujitsu Siemens Computers
NoIcons=0
Components=gui,ico,dem,man,uni
The Dir entry can be used to locate C:\Programme\FSC\v6_cc\unins000.exe in
case of unattended uninstall.
/LOADINF='filename' 1
Instructs Setup to load and re-use the settings from the specified file after having
checked the command line. This file can be prepared using the /SAVEINF parameter
explained above. Don't forget to use quotes if the filename contains spaces.
10.5.2 Setup Exit Codes
0
Setup was successfully run to completion.
1
Setup failed to initialize.
2
The user clicked "Cancel" in the wizard before the actual installation started, or chose
"No" on the opening This will install... message box.
3
A fatal error occurred while preparing to move to the next installation phase (for
example, from displaying the pre-installation wizard pages to the actual installation
process). This should never happen except under the most unusual of circumstances,
such as running out of memory or Windows resources.
4
A fatal error occurred during the actual installation process.
i
Errors that cause an Abort/Retry/Ignore box to be displayed are not fatal errors.
If the user chooses "Abort" at such a message box, exit code 5 will be returned.
5
The user clicked "Cancel" during the actual installation process, or chose "Abort" at an
Abort/Retry/Ignore box.
6
The Setup process was forcefully terminated by the debugger (Run or Terminate used in
IDE).
1
optional
2
pathname of the default directory
Edition 7
13 October 2006
319
Unattended Installation / Deinstallation under MS-Windows
Installation of the GUI software
Before returning an exit code of 1, 3, or 4, an error message explaining the problem will
normally be displayed. Future versions may return additional exit codes, so applications
checking the exit code should be programmed to handle unexpected exit codes gracefully.
Any non-zero exit code indicates that Setup was not run to completion.
10.5.3 Uninstaller Command Line Parameters
The uninstaller program unins000.exe accepts the following command line parameters:
/SILENT
When specified, the uninstaller will neither ask the user any questions nor display a
message stating that uninstall is complete. Shared files that are no longer in use are
deleted automatically without prompting.
Any critical error messages will still be shown on the screen. The uninstallation progress
window is displayed.
/VERYSILENT
When specified, the uninstaller will neither ask the user any questions nor display a
message stating that uninstall is complete. Shared files that are no longer in use are
deleted automatically without prompting.
Any critical error messages will still be shown on the screen. The uninstallation progress
window is not displayed.
/SUPPRESSMSGBOXES
Instructs the uninstaller to suppress message boxes. Only has an effect when combined
with /SILENT and /VERYSILENT.
10.5.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).
320
13 October 2006
Edition 7
Restrictions and known bugs
10.5.5 Setup Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current
Version\Uninstall\FSC V6 Control Center_is1
...
UninstallString REG_SZ
C:\Programme\FSC\v6_cc\unins000.exe 1
10.5.6 GUI Registry Settings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current
Version\Uninstall\FSC V6 Control Center
ADMIN_USER REG_SZ ?
GXTCC_HOME REG_SZ C:\Programme\FSC\v6_cc\gxtcc 1
XTCC_HOME REG_SZ C:\Programme\FSC\v6_cc\xtcc
1
TCLSH REG_SZ C:\Programme\FSC\v6_cc\xtcc\osd\Windows\tclsh.exe 1
WISH REG_SZ C:\Programme\FSC\v6_cc\xtcc\osd\Windows\wish.exe 1
10.6 Restrictions and known bugs
Depending on the XTCC version used, the following error messages may occur while
executing the function "XTCC Update / Revert". These messages can be ignored because
the listed files and directories are not required.
Instead of the recommended actions the function should be finished by pressing the
"Cancel" button.
Message while executing "XTCC Update"
Extraction failed <
tar: osd/Linux/i486: Cannot open: File exists
tar: Error exit delayed from previous errors>
Update failed
The application directory could be inconsistent
1
pathname of the default directory
Edition 7
13 October 2006
321
Restrictions and known bugs
=> Try again "Update"
If the failure persists:
=> Re-Install manually using the Basic version CD
Message while executing "XTCC Revert"
Recursive copy failed <
cp: cannot overwrite directory '/usr/apc/xtcc/./osd/Linux/i486'
Revert failed
The application directory could be inconsistent
=> Try again "Revert"
If the failure persists:
=> Re-Install manually using the Basic version CD
322
13 October 2006
with
with
with
with
with
with
non-directory
non-directory
non-directory
non-directory
non-directory
non-directory>
Edition 7
11 Important information regarding the
CentricStor environment
This chapter is designed to address and show how to rectify familiar problems in the CentricStor™ environment. The information is intended for service personnel and consultants.
●
Netapp filers crash during update installation of CentricStor™
With the current status of the Netapp filers, deactivation commands must be entered
before you reboot the ICP so that the filer survives this reboot. Activation is required
after this reboot.
Edition 7
13 October 2006
323
Abbreviations
Abbreviation Full name
Explanation
AL
Arbitrated Loop
Fibre Channel operating mode, also
abbreviated to FCAL
ACF
Automatic Cartridge Facility
ACI
AML Client Interface
Interface to the ABBA Robot via DAS
ACS
Automatic Cartridge System
StorageTek Library
ACSLS
ACS Library Server (or Software)
controls the StorageTek libraries
ADIC
Advanced Digital Information Corporation
AML
Automated Media Library
ADIC name for libraries
AMU
AML Management Unit
PC to monitor the AML Robot including
the library
UM
CentricStor User Manual
CNC
ESCON channel operating mode
CS
CentricStor
CSC
StorageTek Library Component
StorageTek Library Interface
CTL
Controller Target LUN
complete SCSI address
CU
Control Unit
DA
Device Adapter
DAS
Distributed AML Server
DDM
Disk Drive Module
DFHSM
IBM: Data Facility Hierarchical Storage
Manager
Interface to monitor the AML robot (open
systems)
DFRMM
Component of DFHSM
DPO
Data Path Optimizer
DTVFS
Distributed Tape Volume File System
EMTAPE
Tape emulation in CentricStor
Edition 7
13 October 2006
325
Abbreviations
Explanation
ERP
Error and Recovery Procedure
ESCD
ESCON Director
ESCM
ESCON Manager
ESCON
Enterprise System Connection
ESS
Enterprise Storage Server
FBA
Fixed Block Architecture
FC
Fibre Channel
FCAL
Fibre Channel Arbitrated Loop
FCH
Fibre Channel Hub
FCP
Fibre Channel Protocol
FCS
Fibre Channel Switch
FSC
Fujitsu Siemens Computers
GB
Gigabyte
GXCC
Global Extended Control Center
graphical user interface of CentricStor
V3.0 for servicing, maintaining and
monitoring
GXTCC
Global Extended Tape Control Center
graphical user interface of CentricStor
V2.1 for servicing, maintaining and
monitoring
GUI
Graphical User Interface
Collective description for GXTCC/XTCC/
Global Status
HA
Host Adapter
Fibre channel or ESCON adapter in
CentricStor
HACC
Host access of ABBA/x in the MVS
corresponds to ROBAR in BS2000
HBA
Host Bus Adapter
here: FC adapter on the host
HCC
Host Control Component
Software running on MVS for AML
access.
HDD
Head and Disk Drive
HSC
StorageTek: Host Software Component
MVS (or BS2000) program to control ACS
robots, comparable to ROBAR-CL
ICP
Integrated Channel Processor
Processor in CentricStor which contains
the FC or ESCON host adapter
IDP
Integrated Device Processor
Processor in CentricStor connected to
real cartridge drives
326
13 October 2006
FC link via hub or loop
Edition 7
Abbreviations
Explanation
IML
Initial Microcode Load
IODF
I/O Definition File
IOS
Input Output Supervisor
IPL
Initial Program Load
ISP
Integrated Service Processor
JCL
Job Control Language
KB
Kilobyte
LAN
Local Area Network
LCU
Logical Control Unit
LD
Logical Drive
LM
Library Manager
LP
Logical Path
LPAR
Logical Partition
LMU
StorageTek: Library Management Unit
Central control for operating up to 16 LSM
LSM
StorageTek: Library Storage Module
Silo including robot
LSS
Logical SubSystem
LUN
Logical Unit Number
Device accessible via an SCSI (or FCSCSI) target
LV
Logical Volume
Also called “virtual volume”.Uncompressed capacity 895MB, corresponding
to the emulated drive 3490E.
MAREN
Magnetic tape management in BS2000
NDM
Nucleus Device Management
Device Management of BS2000
PDS
Physical Device Server
Process in the IDP for operating a real
drive
PLS
Physical Library Server
Process for operating a real library in
CentricStor
PTF
Program Temporary Fix
RAID
Redundant Array of Independent (originally:
Inexpensive) Disks
ROBAR
Robot Archive
Edition 7
Overall term for processors in CentricStor
emulated tape drive in an ICP
The ROBAR-SW makes it possible for
BS2000 to communicate with an AML/x
tape library
13 October 2006
327
Abbreviations
Explanation
ROBAR-CL
Robar Client
ROBAR-SW in BS2000
ROBAR-SV
ROBAR Server
ROBAR software on SINIX computer
SAN
Storage Area Network
Memory network supported by FC
SCSI
Small Computer Systems Interface
SDD
SubSystem Device Driver
SNMP
Simple (or Standard) Network Management
Protocol
SPARC
Scalable Processor Architecture
SS
SubSystem
SSID
SubSystem IDentification
UCB
Unit Control Block
VACS
Virtual ACS
Emulation of an ACS in CentricStor
VAMU
Virtual AML Management Unit
AMU Emulation in CentricStor
VDAS
Virtual DAS
Emulation of a DAS in CentricStor
VLP
Virtual Library Processor
ISP in CentricStor in which VLM, PLM
and different central processes run. In
several models together with IDP
VOLSER
Volume Serial Number Name of a Volumes
VPD
Vital Product Data
VSN
Volume Serial Number
VTOC
Volume Table of Contents
MM
CentricStor maintenance manual
WLM
Workload Manager
WWNN
World Wide Node Number
Number of an FC node
WWPN
World Wide Port Number
Number of an FC port (for FC nodes with
several ports)
XRC
Extended Remote Copy
XTCC
Extended Tape Control Center
328
13 October 2006
Name of the RISC architecture used by
SUN
User interface for ISP
Edition 7
Related publications
Ordering manuals
The manuals are available as online manuals, see http://manuals.fujitsu-siemens.com, or
in printed form which must be payed and ordered separately at
http://FSC-manualshop.com.
[1]
CentricStor Maintenance Manual (also available as an online manual from CentricStor 2.1
onwards).
[2]
BS2000/OSD-BC V#.## Introduction to System Support *)
[3]
MAREN V#.## (BS2000/OSD) MAREN for Administrators *)
[4]
MAREN V#.## (BS2000/OSD) MAREN for Users *)
[5]
ROBAR V#.## (BS2000/OSD, Reliant UNIX, Solaris) Tape Cartridge Archiving System *)
[6]
IBM Magstar Virtual Tape Server: Planning, Implementing, and Monitoring
(SG24-2229-05) **)
[7]
BS2000/OSD-BC V#.## System Installation *)
[8]
BS2000/OSD-BC V#.## Commands (several volumes) *)
[9]
StorageTek User Guide BS2000 CSC Version 6.1 (under preparation)
[10]
ADIC Manual for HCC
[11]
StorageTek Manual, Client System Component for MVS, Systems Programmer Guide,
Release 4.0, 31343480
[12]
User Guide “SX Series Business Servers - Operation and Administration”
Order Number: U41272-J-Z385-2 (or U41272-J-Z385-2-76)
The manuals marked with *) are available on the BS2000/OSD manual server at:
http://manuals.fujitsu-siemens.com/mainframes.html. “#.##” shows the version number
available on your host.
Edition 7
13 October 2006
329
Literatur
The manuals marked with **) are IBM Redbooks available from:
http://publib-b.boulder.ibm.com/Redbooks.nsf/portals/
The current version is offered here. The order number gives the version number after the
second hyphen (“-”).
330
13 October 2006
Edition 7
Environmental Protection
Returns, Recycling and Disposal
Details on the return and recycling of devices and disposables in the European area can be
obtained from your Siemens dealer or from our Recycling Center in Paderborn, Germany:
Tel.
Fax.
Germany 05251 8180-10
Germany 05251 8180-15
Further information on environmental protection
The Environment Affairs Manager for Siemens AG will be happy to answer any questions
on environmental protection.
Siemens AG
Environmental Protection Office
Werner von Siemens Straße 6
86159 Augsburg, Germany
Tel.
Fax.
Edition 7
Germany 0821 599-2999
Germany 0821 599-3440
13 October 2006
331
by f.f. 1992
Index
/390 firmware
44
A
ACS
NetBackup 164
permitted configurations 22
ACSLS 258
communication 275
Networker 150
Server Networker 143
ACSLS communication brakdown
ADIC library 36
AIX
device nodes 127
limitations 123
settings and info 123
useful commands 124
AMU PC 268
applications
limitations 24
B
backup times 185
BIOS settings 289
block length
maximum 24
block size 55
Brocade 278
Brocade Silkworm 41
BS2 tapes 49
BS2000 partition 44
BS2000/OSD 44
BSD
Solaris 159
Edition 7
259
C
Cashion connection 276
cbn nodes 164
Celerra 137
CentricStor configurations 21
changer 258
channel path list
with director 66
without director 64
cleaning management
StorageTek libraries 273
cloning 135
cmd_proc
STK libraries 143, 274
compressed WWN
Reliant UNIX 90
compression 56
Linux 8.0 84
NetApp 257
Netbackup 179
Networker 158
switch off NT 156
Windows 157
configuration
LANfree 236
Linux client 238
Linux Storage Agent 238
Networker 142
SAN environment 239
TSM server 239
configuration data
CentricStor 265, 266
configuration tools
UNIX systems 265
Connectrix McData 41
13 October 2006
333
Index
control port
Networker 142
control unit
BS2000 28
definition (MVS) 64, 66
CSC
MVS 61
StorageTek 38
to BS2000 38
CSC device statement 77
CSC-5.1 device definitiions 75
D
DAS
NetBackup 164
Networker 151
DAS client 268
DAS server 268
DASADMIN
in CentricStor 268
in host 268
Data Protector 121, 182
Datamover 137
device count
Networker 144
device depot 35
device name 40
device nodes
AIX 127
missing 83
Reliant UNIX 90, 91
rewind 127
Solaris 99
device sharing 56
devices
Networker 142
DFHMS 72
DFRMM 72
diagnostic documentation 57
diagnostics
performance problems 287
334
DiskXtender 258
configuration 262
configuration in CentricStor
Installation 260
drive definition 67
driver
AIX 3590 124
AIX OST 123
Linux Adaptec 88
Linux EMULEX 80
Linux ST 85
Linux Symbios 88
NT 131
NT QLA2200F 131
Rel UNIX LP8000 89
Solaris EMULEX 98
Solaris JNI FCE2 96
Solaris Netbackup 121
dsmadmc 239
258
E
eject sleep
Networker 142
EMTAPE 40
EMULEX LP8000
Linux RedHat 79
Linux SuSE 80
Linux Suse 80
Reliant UNIX 89
Solaris 95
even distribution, mount requests 74
extended drive 258
EZ fibre
configuration program JNI 96
F
FC connections
special features 277
FC switch
IP addresses 266
permitted types 277
firmware download 289
fixed block length mode 25
Fujitsu libraries 277
13 October 2006
Edition 7
Index
G
GENTAB 40
Gresham 236
H
HACC
configuration note 73
MVS 61
HAL 44
HBA 288
host systems
limitations 24
HSI 55
I
IBM 03590E1A SCSI Sequential Device
IBM 3490E 61
ibmrmsst.sys 260
IBMTape driver 237
ICP reboot
Networker 144
ICP sharing 278
Idle_Device_Timeout
Networker 142
installation
GUI software 301
IOGEN 44
IP addresses
display 266
FC switch 266
ISP 266
libraries 266
ISP
IP addresses 266
J
JNI FCE2-6412-N
Solaris 96
jnic.conf
Solaris 109
K
kernel building
Linux 88
Edition 7
260
L
L180
import tapes 273
LANfree configuration 236
LANfree data transfers
verification 240
Legato (EMC) 258
Legato MediaStor 260
LibAttach
NT 4.0 156, 176, 218
Windows 157, 177, 219
libraries
IP addresses 266
Library Attach 260
library device name
CentricStor 40
limitations
AIX 123
through application 24
through host 24
links
on LD 92
shell script for creating links
Linux client
configuration 238
Linux Storage Agent
configuration 238
lmadmin 277
LMF 165
load sleep
Networker 142
logging
UNIX systems 265
lpfc.conf
Solaris 103
92
M
MAREN
BS2000 30
media family
Networker 150
media type
Networker 150
13 October 2006
335
Index
model
Networker 142
more than 8 LUN
Windows 2000 133
mount balancing 74
mount requests, even distribution
74
N
NAS systems 135
NDM
BS2000 35
NDMP 135
NetApp 135
Netapp-Filer 323
NetBackup
Java 164
Solaris extensions 121
Networker 141
NetWorker backup node 149
no rewind 91
non-rewind 85, 87, 176, 178, 179, 180, 181, 219,
220, 257
NT 4.0 131
number of devices 55
O
options element status
Networker 144
OS390/zOS-CSC-5.1 configuration
P
PDS
display 267
performance problems
diagnostics 287
permitted configurations
ACS 22
DAS 23
VJUK 23
persistent binding
Solaris 101
physical volumes
sharing 19
336
74
PLP 277
PLS
display 267
port zoning 278
Powderhorn
extend 272
import tapes 273
PSR 57
Q
QL2200
error messages 132
QLA2200F
NT 131
Qlogic QLA2200F
Linux RedHat 80
Linux Suse 7.1 80
Linux Suse 8.0 81
R
real drive
sharing 19
real robot
sharing 19
reconfiguration boot 44
Reliant UNIX 89
restrictions
Networker 145
rewind
device nodes 127
ROBAR 36
rpm packages 237
S
S servers 58
SAN environment
configuration 239
scratch mount
Networker 151
session rest time
NT 132
settings and info
AIX 123
NT 4.0 132
13 October 2006
Edition 7
Index
Solaris 94
Windows 2000 134
sharing
physical volumes 19
real drives 19
real Robot 19
z/OS-BS2000 63
Silkworm 278
SMIT 237
Solaris
requirements 93
st.conf 116
SPARC64 mode 44
ssi daemon 273
st.conf
Solaris 116
startup sequence
fibre channel 277
STL device names
Networker 142
STL interface lib
Networker 143
storage location 28
StorageTek libraries 38, 272
StorageTek Library Attach 260
SX servers 41
System Management Interface Tool
T
Tape 141
tape driver
DiskXtender 260
tape driver ST
Linux 85
Solaris 97
tapeutil 128
telnet 287
TIVsm-API 237
TIVsm-BA 237
TIVsm-stagent 237
TIVsm-tsmscsi 237
Edition 7
traces
UNIX systems 265
TSM documentation 241
TSM server
configuration 239
U
UGEN
BS2000 28, 40
Unix device nodes 92
unload sleep
Networker 142
237
V
VACS 40, 258
CentricStor 40
coordinates of the device 143
NetBackup 164
server 158
VAMU 40
CentricStor 40
VDAS
TIMEOUT_MOVE Networker 143
verification
LANfree data transfer 240
virtual devices
Networker 149
virtual libraries
display 267
VJUK
configuration 208
configuring a SCSI library on AIX 232
emulation 255
vjukadmin 232, 235, 255
volume default capacity
Networker 150
VTD emulation 25
W
Windows 2000
Windows 2000/2003 133
WSA 44, 50
13 October 2006
337
Index
WWNN
display 267
zoning 278
WWPN
display 267
X
X2000
44
Z
zoning
configuration examples
FC switch 90
ICP sharing 278
rules 278
338
281
13 October 2006
Edition 7
Information on this document
On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
This document from the document archive refers to a product version which
was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have
been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the format …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at
http://ts.fujitsu.com/...
and the user documentation at http://manuals.ts.fujitsu.com.
Copyright Fujitsu Technology Solutions, 2009
Hinweise zum vorliegenden Dokument
Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von
Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine
bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche
Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden
Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions
angeboten und haben die Form …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009

Installation Guide CentricStor V3.1

Transcription

Similar documents

Correction Tape E-blast for Highland Group_July 2014

MONO CORRECTION TAPE REFILLABLE

Just cut, fold and tape this stuff to create your very own Cla

Korg Poly61

PEB250 | PEB200

Next Step Hoodie Backpack Make your own table football Blue Peter

July - October 2014 - San

our Fact Sheet

VaproShield

The Frugal Ergonomic Engineer -The Sequel