Fujitsu SE700, BS2000, SE500, SE300 User Manual
English
FUJITSU Server BS2000
SE700 / SE500 / SE300
Administration and Operation
User Guide
Valid for:
M2000 V6.2A SP1 (V6.2A05 and higher)
X2000 V6.0A SP1 (V6.2A05 and higher)
HNC V6.2A SP1 (V6.2A05 and higher)
Edition March 2018
Comments… Suggestions… Corrections…
The User Documentation Department would like to know your
opinion on this manual. Your feedback helps us to optimize our
documentation to suit your individual needs.
Feel free to send us your comments by e-mail to:
manuals@ts.fujitsu.com
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system which
complies with the requirements of the standard
DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © 2018 Fujitsu Technology Solutions GmbH.
All rights reserved. Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
The Xen® mark is a trademark of Citrix Systems, Inc., which manages the mark on behalf of the Xen open source
community. The Xen® mark is registered with the U.S. Patent and Trademark Office, and may also be registered in
other countries.
Novell and SUSE are registered trademarks of Novell, Inc. in the USA and other countries.
Linux is a registered trademark of Linus Torvalds.
Windows® is a registered trademark of Microsoft Corporation.
The Linux-based basic software M2000, X2000, and HNC which is installed on the Management Unit, Server Unit
x86, and HNC contains Open Source Software. The licenses for this can be found in the LICENSES directory on the
relevant installation DVD.
This manual is printed
on paper treated with
chlorine-free bleach.
Content
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Documentation for the SE servers . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Objective and target groups of this manual . . . . . . . . . . . . . . . . . . . . . 14
1.3 Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4 Changes since the last edition of the manual . . . . . . . . . . . . . . . . . . . . 16
1.5 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6 Names and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.7 Open Source Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 Architecture and strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Software of the SE server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.1 Structure of the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.2 Software status, system version and update status . . . . . . . . . . . . . . . . . . 25
2.2.3 Updates to the basic software and add-on packs . . . . . . . . . . . . . . . . . . . 26
2.2.3.1 Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.3.2 Security fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.3.3 Hot fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.3.4 Add-on pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.4 Management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.1.1 IPv6 autoconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.1.2 Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.3.1.3 Managing the "senet" domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.3.1.4 ACL functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.3.1.5 NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
U41855-J-Z125-3-76
Content
2.3.2 Integration of BS2000 into the SE Manager . . . . . . . . . . . . . . . . . . . . . . 36
2.3.3 Integration of BS2000 into the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.3.4 Integration of the XenVM guest systems into the LAN (only SU x86) . . . . . . . . . 39
2.3.5 Overview of the possible LAN connections of the VMs . . . . . . . . . . . . . . . . . 40
2.3.6 Important information about IP configuration . . . . . . . . . . . . . . . . . . . . . . 41
2.4 External configuration disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.5 Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.1 Management Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.2 SU Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.6 Management Unit and SE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.1 Role and user strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.2 IP-based access to the Management Unit . . . . . . . . . . . . . . . . . . . . . . . 51
2.6.3 Redundant Management Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.6.4 Central logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.7 Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.7.1 Implementing VM2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.7.2 Virtualization on Server Unit x86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.7.2.1 CPU pool management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.7.2.2 Main memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.2.3 BS2000 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.7.2.4 XenVM devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.8 Time synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.9 Customer Support and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.9.1 Tasks of Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.9.2 Tasks of the customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.9.3 Maintenance and remote service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.9.4 Handling updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.9.4.1 Providing updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.9.4.2 Tasks and responsibilities when installing updates . . . . . . . . . . . . . . . . . 72
3 Operating the SE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.1 Calling the SE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.1.1 Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.1.2 Logging out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.2 Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.2.1 Session timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.2.2 Automatic update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.2.3 Restricted operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
U41855-J-Z125-3-76
Content
3.3 SE Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.3.1 Window types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.3.2 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.3.3 Terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
3.3.4 The dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.3.5 The wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.3.6 Web UIs of Application Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.4 Working with the SE Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.4.1 Calling an object or function in the SE Manager . . . . . . . . . . . . . . . . . . . . 88
3.4.2 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3.4.3 Filtering and sorting a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
3.4.4 Executing an action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.4.5 Calling the online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.4.6 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5 Operating and managing systems on Server Units . . . . . . . . . . . . . . . . 105
5.1 Setting BS2000 operation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.1.1 Server Unit /390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
5.1.2 Server Unit x86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
5.2 Opening the BS2000 console and dialog window . . . . . . . . . . . . . . . . . 112
Messages on the BS2000 console . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.3 SVP console on Server Unit /390 . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.4 Working in Native BS2000 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.4.1 Starting (IPL) and shutting down a BS2000 system, executing an IPL dump and
migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
5.4.2 Setting the options (only SU x86) . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.4.3 Evaluating KVP logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.5 Working in VM2000 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.5.1 VM administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.5.2 Managing VM resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.5.3 Setting VM options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5.5.4 Operating a VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
5.5.4.1 Start and shut down a BS2000 guest system, create a dump / enable and
disable (and delete) a BS2000 VM, migrate . . . . . . . . . . . . . . . . . . . . 123
5.5.4.2 Managing devices of the VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
U41855-J-Z125-3-76
Content
5.6 Working in XenVM mode (on Server Unit x86) . . . . . . . . . . . . . . . . . . . 130
5.6.1 VM administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.6.2 Managing VM resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.6.3 Tracking VM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.6.4 Setting VM options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.6.4.1 Defining the remaining runtime for shutdown . . . . . . . . . . . . . . . . . . . 136
5.6.4.2 Setting VM-specific options (auto start and delay) . . . . . . . . . . . . . . . . 137
5.6.5 Operating a VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.6.5.1 Displaying VM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.6.5.2 Opening the console of the XenVM . . . . . . . . . . . . . . . . . . . . . . . . 138
5.6.5.3 Starting and shutting down the XenVM . . . . . . . . . . . . . . . . . . . . . . 139
5.6.5.4 Changing the configuration of the XenVM . . . . . . . . . . . . . . . . . . . . 140
5.6.5.5 Managing devices of the XenVM . . . . . . . . . . . . . . . . . . . . . . . . . 141
6 Operating and managing systems on Application Units . . . . . . . . . . . . . 147
6.1 Operating a Native system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
6.2 Operating virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6.3 Installing an operating system on an Application Unit . . . . . . . . . . . . . . 151
7 Managing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
7.1 SE management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7.1.1 BS2000 Backup Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7.1.2 openUTM WebAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
7.1.3 ROBAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
7.2 Managing user-defined management applications . . . . . . . . . . . . . . . . 161
7.3 Administering user-defined links . . . . . . . . . . . . . . . . . . . . . . . . . . 162
8 Monitoring performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
U41855-J-Z125-3-76
Content
9 Managing devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.1 Managing BS2000 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.1.1 Device addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.1.2 Device management on Server Unit /390 . . . . . . . . . . . . . . . . . . . . . . . 168
9.1.2.1 Predefined BS2000 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
9.1.2.2 Device connection via Management Unit and HNC . . . . . . . . . . . . . . . . 169
9.1.2.3 Configuration in IORSF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
9.1.3 Device management on Server Unit x86 . . . . . . . . . . . . . . . . . . . . . . . . 171
9.1.3.1 Predefined BS2000 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
9.1.3.2 Connection of peripheral devices . . . . . . . . . . . . . . . . . . . . . . . . . 171
9.1.4 Managing disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
9.1.4.1 Displaying generated disks on Server Unit /390 . . . . . . . . . . . . . . . . . . 173
9.1.4.2 Managing disks on Server Unit x86 . . . . . . . . . . . . . . . . . . . . . . . . 174
9.1.5 Managing KVP devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
9.1.6 Managing LAN devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
9.1.7 Managing tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
9.1.7.1 Emulated tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
9.1.7.2 Emulated tape devices from the BS2000 viewpoint . . . . . . . . . . . . . . . . 185
9.2 Managing XenVM devices on Server Unit x86 . . . . . . . . . . . . . . . . . . . 188
9.2.1 Managing disk pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
9.2.2 Managing virtual disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
9.2.3 Managing virtual switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
9.2.4 Managing installation sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
10 Managing hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
10.1 Managing units of the SE server . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.1 Powering a unit on or off, rebooting a unit . . . . . . . . . . . . . . . . . . . . . . . 198
10.1.2 Managing the SE servers of the Management Cluster . . . . . . . . . . . . . . . . . 200
10.1.3 Managing the Server Unit /390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10.1.3.1 Displaying system information and interfaces of the SU /390 . . . . . . . . . . . 201
10.1.3.2 Displaying the IP configuration of the SU /390 . . . . . . . . . . . . . . . . . . . 203
10.1.4 Managing the Management Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
10.1.4.1 Displaying system information and interfaces of a Management Unit . . . . . . . 204
10.1.4.2 Managing the IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
10.1.4.3 Managing routing of the Management Unit . . . . . . . . . . . . . . . . . . . . 210
10.1.4.4 Managing the DNS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 211
10.1.4.5 Managing SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
10.1.4.6 Setting the system time (time synchronization or local) . . . . . . . . . . . . . . 214
10.1.4.7 Entering CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
10.1.4.8 Managing updates of the Management Unit . . . . . . . . . . . . . . . . . . . . 217
U41855-J-Z125-3-76
Content
10.1.4.9 Managing configuration data (CSR) of the MU . . . . . . . . . . . . . . . . . . 220
10.1.4.10 Generating diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
10.1.4.11 Managing service access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
10.1.5 Managing the HNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
10.1.5.1 Displaying system information and interfaces of the HNC . . . . . . . . . . . . 227
10.1.5.2 Managing the IP configuration of the HNC . . . . . . . . . . . . . . . . . . . . 230
10.1.5.3 Managing routing of the HNC . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
10.1.5.4 Displaying the DNS configuration of the HNC . . . . . . . . . . . . . . . . . . 232
10.1.5.5 Configuring Net-Storage on the HNC . . . . . . . . . . . . . . . . . . . . . . . 232
10.1.5.6 Managing updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.1.5.7 Managing configuration data (CSR) of the HNC . . . . . . . . . . . . . . . . . 235
10.1.5.8 Generating diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
10.1.6 Managing Server Unit x86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
10.1.6.1 Displaying system information and interfaces of the unit . . . . . . . . . . . . . 237
10.1.6.2 Managing the IP configuration of the SU x86 . . . . . . . . . . . . . . . . . . . 240
10.1.6.3 Managing routing of the SU x86 . . . . . . . . . . . . . . . . . . . . . . . . . 240
10.1.6.4 Displaying the DNS configuration of the SU x86 . . . . . . . . . . . . . . . . . 241
10.1.6.5 Configuring Net-Storage on the SU x86 . . . . . . . . . . . . . . . . . . . . . 241
10.1.6.6 Managing updates of the SU x86 . . . . . . . . . . . . . . . . . . . . . . . . . 244
10.1.6.7 Managing configuration data (CSR) of the SU x86 . . . . . . . . . . . . . . . . 244
10.1.6.8 Generating diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
10.1.7 Managing Application Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
10.1.7.1 Configuring an Application Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 246
10.1.7.2 Displaying hardware information of the Application Unit . . . . . . . . . . . . . 248
10.1.7.3 Managing the IP configuration of the Application Unit . . . . . . . . . . . . . . 250
10.2 Managing IP networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10.2.1 Displaying information on networks and switches . . . . . . . . . . . . . . . . . . 252
10.2.1.1 Overview of IP networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
10.2.1.2 Configuring SENET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
10.2.1.3 Information on switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
10.2.1.4 Graphical display of the internal IP network topology . . . . . . . . . . . . . . . 257
10.2.1.5 Overview of the performance and utilization of the Net Unit ports . . . . . . . . 258
10.2.2 Managing a Data Network Public . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
10.2.2.1 Configuring the ACL settings of the DANPU network . . . . . . . . . . . . . . . 261
10.2.2.2 Information on the performance and utilization of the DANPU ports . . . . . . . 263
10.2.3 Managing a Data Network Private . . . . . . . . . . . . . . . . . . . . . . . . . . 265
10.2.3.1 Add network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
10.2.3.2 Activate RADVD / DNS / NTP server . . . . . . . . . . . . . . . . . . . . . . . 267
10.2.3.3 Managing members of a DANPR network . . . . . . . . . . . . . . . . . . . . 268
10.2.3.4 Configuring the ACL settings of the DANPR network . . . . . . . . . . . . . . . 268
10.2.3.5 Information on the performance and utilization of the DANPR ports . . . . . . . 268
U41855-J-Z125-3-76
Content
10.2.4 Managing a Management Network Public . . . . . . . . . . . . . . . . . . . . . . . 269
10.2.4.1 Configuring the ACL settings of the MANPU network . . . . . . . . . . . . . . . 271
10.2.4.2 Information on the performance and utilization of the MANPU ports . . . . . . . . 271
10.2.5 Managing a Management Network Private . . . . . . . . . . . . . . . . . . . . . . . 272
10.2.5.1 Overview over the status of all private management networks . . . . . . . . . . 272
10.2.5.2 Information on the performance and utilization of the ports of the private
management networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
10.2.5.3 Managing members of optional MONPR networks . . . . . . . . . . . . . . . . 275
10.2.5.4 Configuring ACL settings of optional MONPR networks . . . . . . . . . . . . . . 276
10.3 Managing FC networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
10.3.1 Overview of FC networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
10.3.2 Configuring settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
10.3.3 Displaying messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
10.3.4 Displaying connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
10.4 Managing storage systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
10.4.1 Overview of the storage systems of the SE server configuration . . . . . . . . . . . 281
10.4.2 Overview over the storage systems of an MU . . . . . . . . . . . . . . . . . . . . . 283
10.4.3 Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
10.5 HW inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
10.5.1 Rack view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
10.5.2 Displaying units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
10.5.3 Displaying components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
10.5.4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
10.6 Managing energy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
10.6.1 Monitoring energy consumption of the units of the SE server . . . . . . . . . . . . . 290
10.6.2 Simulating energy saving scenarios for the SE server . . . . . . . . . . . . . . . . . 292
10.6.3 Scheduled power on/off of units of the SE server . . . . . . . . . . . . . . . . . . . 293
11 Managing a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
11.2 Status of the Management Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 296
11.3 Managing an SU Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
U41855-J-Z125-3-76
Content
12 Managing authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
12.1 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
12.1.1 Managing accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
12.1.2 Managing passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
12.1.3 Managing individual rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
12.1.4 Displaying sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
12.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
12.2.1 Access to an LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
12.2.2 IP-based access restriction to the MUs . . . . . . . . . . . . . . . . . . . . . . . . 311
12.3 Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
12.3.1 SSL certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
12.3.1.1 Confirming/importing a certificate in the web browser . . . . . . . . . . . . . . 314
12.3.2 Managing certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
12.3.2.1 Using the standard certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
12.3.2.2 Creating and enabling a new self-signed SSL certificate . . . . . . . . . . . . . 319
12.3.2.3 Requesting an SSL certificate . . . . . . . . . . . . . . . . . . . . . . . . . . 319
12.3.2.4 Uploading and activating a customer-specific certificate . . . . . . . . . . . . . 321
13 Managing logging functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
13.1 Displaying audit logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
13.2 Displaying event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
13.3 Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
14 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
14.1 Operating BS2000 with PuTTY . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
14.1.1 BS2000 console on MU or SU /390 . . . . . . . . . . . . . . . . . . . . . . . . . . 332
14.1.2 BS2000 dialog on MU or SU /390 . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
14.1.3 SVP console on MU or SU /390 . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
14.1.4 BS2000 console on SU x86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
14.1.5 BS2000 dialog on SU x86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
14.1.6 Information on the user strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
14.2 Working with EMDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
14.2.1 Using shortcuts for special characters . . . . . . . . . . . . . . . . . . . . . . . . 352
14.2.2 Using programmable keys (pfkeys) . . . . . . . . . . . . . . . . . . . . . . . . . . 352
U41855-J-Z125-3-76
Content
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365
U41855-J-Z125-3-76
Content
U41855-J-Z125-3-76
1 Introduction
With the completely newly developed FUJITSU Server BS2000 SE Series, FUJITSU now
offers a server infrastructure which consists of three server lines. Under the umbrella of this
SE infrastructure, multiple application scenarios are possible in various combinations for
both mainframe applications and applications of the open world. This new platform stands
out on account of the unrivaled performance scalability (scale-up and scale-out), and
ensures that users can manage their application workloads securely, quickly and efficiently
across technological boundaries with maximum availability.
One major aim in developing the SE series was to provide a uniform management strategy
which offers customers significant added value through maximum integration, and
guarantees extremely cost-effective operation of their IT.
The new SE server line succeeds the tried and tested S and SQ server lines, integrating
the advantages of both lines in an optimal manner. The heart of the SE series is formed by
the /390-based Server Units, the x86-based Server Units, the Net Unit (NU) and the
Management Unit (MU). All components are integrated into a standard 19" rack and are
supplied to customers ready to use. With its newly developed processors and appreciably
higher system performance, the new generation of the SE series offers enhanced
configuration options, maximum availability and, not least of all, significantly reduced power
consumption.
Depending on requirements, the SE server contains all the system components needed for
operation as an overall application:
– Server Unit /390 for BS2000 guest systems
– Server Unit x86 with BS2000, Linux or Windows guest systems
– Application Units x86 for operating Native or hypervisor systems (e.g. Linux, Windows,
VMware, OVM, etc.)
– Shareable tape and disk periphery
– A high-speed, server-internal infrastructure to connect the components with each other
and with the customer's IP and FC networks.
U41855-J-Z125-3-76 11
Introduction
The SE server offers the following advantages:
– Cross-system administration with state-of-the-art, browser-based GUI (SE Manager) as
a single point of operation
– Centralized system monitoring of all components
– End-to-end redundancy concept
– Joint service process
– All options for consolidation through virtualization
– SE components and infrastructure are preconfigured and supplied to customers ready
to use
SE servers consequently enable flexible and application-specific implementation which
fulfills high SLAs through the use of high-end components and an end-to-end redundancy
concept, and nevertheless permits cost-effective operation of the overall system with few
resources thanks to its uniformity.
Intel x86-based server systems with their VMware, Linux or Windows system platforms also
profit from the concepts for stable system operation tested on the mainframe:
– Selection of high-quality server components
– Redundant hardware components
– Prepared operating concepts which also include high availability
– Comprehensive tests before release
– Comprehensive service concept.
The management interface which is uniform for all SE servers, the SE Manager, permits a
view of all the system components involved and, from this higher-level perspective, enables
the resources to be optimized through efficient distribution of the application to the systems
which are currently utilized least.
It is possible to combine two SE servers in a management cluster to a management entity
and therefore utilize the advantages of the SE Manager for two SE servers at the same
time. Every Management Unit can be used to control all components of the cluster, thus
enhancing protection against failure. Within an SU Cluster, a live migration can be
performed to migrate BS2000 systems without interruption.
SE servers consequently permit particularly stable system operation which includes not
only the mainframe platforms which have to date been known to be particularly failsafe, but
also other Server Units and the infrastructure and peripherals employed by the SE server.
This can be achieved with fewer resources for administration and system operation than for
separate operation of different IT systems.
12 U41855-J-Z125-3-76
Introduction Documentation for the SE servers
1.1 Documentation for the SE servers
A wide range of documentation is available for the SE servers. As the BS2000 OSD/XC
software package comprises the BS2000 OSD/BC operating system and additional
system-related software products, the documentation for BS2000 OSD/XC consists of the
following:
● The manuals on BS2000 OSD/BC, which provide the basic literature on BS2000
OSD/XC.
● The manuals for the system-related software products which belong to the BS2000
OSD/XC software package also apply.
Any additions to the manuals are described in the Readme files for the various product
versions. These Readme files are available at http://manuals.ts.fujitsu.com under the various
products.
Current information, version and hardware dependencies and instructions for installing and
using a product version are contained in the associated Release Notice. Release Notices,
in particular those relating to BS2000, M2000, X2000, and HNC, are available at
http://manuals.ts.fujitsu.com.
The documentation for the SE servers consists of the following parts:
● Operating Manual SE700 / SE500 / SE300 (consisting of a number of modules):
– Basic Operating Manual SE700 / SE500 / SE300 [1]
– Server Unit /390 (SE700 / SE500) [2]
– Server Unit x86 (SE700 / SE500 / SE300) [3]
– Additive Components (SE700 / SE500 / SE300) [4]
● Operation and Administration [5]
● Quick Guide [6]
● Security Manual [7]
● Cluster Solutions for SE Servers (Whitepaper) [8]
U41855-J-Z125-3-76 13
Objective and target groups of this manual Introduction
1.2 Objective and target groups of this manual
This manual is intended for people who operate an SE server:
● As administrator you manage the entire SE server with all its components and the
operating systems which run on it. You need a good knowledge of the BS2000, Linux
and Windows operating systems and of the network and peripherals.
As administrator you can also manage the integration of the optional Application Units
on which an open operating system (by default Linux) runs in Native mode or in a
virtualized manner (e.g. under VMware® vSphere 5).
● For other users, roles are provided with a customized selection of functions (e.g.
operator, XenVM administrator, etc.) to permit the assigned tasks to be performed.
14 U41855-J-Z125-3-76
Introduction Summary of contents
1.3 Summary of contents
Chapter 2 contains fundamental information which is relevant for all readers (e.g.
architecture, fundamental operating functions).
Chapter 3 contains fundamental information on the SE Manager, the central user interface
of the SE server.
The subsequent chapters describe the tasks on the SE server and the user interface of the
SE Manager. They are based on the tree structure of the SE Manager.
Detailed information on the data displayed, the dialog boxes, and operation of the SE
Manager is provided in the online help of the SE Manager.
README file
For information on any functional changes or extensions to this manual, please refer to the
product-specific Readme file.
In addition to the product manuals, Readme files for each product are available to you
online at http://manuals.ts.fujitsu.com. You will also find the Readme files on the Softbook
DVD.
Information under BS2000
When a Readme file exists for a product version, you will find the following file on the
BS2000 system:
SYSRME.<product>.<version>.<lang>
This file contains brief information on the Readme file in English or German (<lang>=E/D).
You can view this information on screen using the
The
/SHOW-INSTALLATION-PATH INSTALLATION-UNIT=<product> command shows the user
/SHOW-FILE command or an editor.
ID under which the product‘s files are stored.
Additional product information
Current information, version and hardware dependencies and instructions for installing and
using a product version are contained in the associated Release Notice. These Release
Notices are available online at http://manuals.ts.fujitsu.com.
U41855-J-Z125-3-76 15
Changes since the last edition of the manual Introduction
1.4 Changes since the last edition of the manual
This manual describes the functionality of the SE Manager with the use of the basic
software M2000/X2000/HNC V6.2A.
Information on the hardware lifecycle of the FUJITSU Server BS2000 SE Series
With the hardware lifecycle of the SE series, the hardware basis for the Server Unit x86, the
Management Unit and the HNC has been renewed. These new generation versions are
called SU300 M2, MU M2 and HNC M2. They are supported from basic software V6.2A
onwards.
The FUJITSU BS2000 servers of the SE series that are equipped with this hardware
generation are called SE300B, SE500B and SE700B.
Functional extensions
The basic software M2000/X2000/HNC V6.2A provides the following functional extensions:
● MU redundancy
An SE server may contain two MUs, which are equally ranking in management and
operation:
Actions can be executed from each MU.
The add-ons on both MUs are integrated into the SE Manager as links and can
therefore be called from each MU.
If the SE Manager is called via DNS, the session is global for all MUs. You can switch
from one MU to another without having to log in again. An add-on can be called without
having to log in again even if it is installed on the other MU.
● Support of clusters
If an SE server configuration consists of two SE servers, the SE servers are managed
together in a shared Management Cluster.
Two SUs of the same type (SU /390 or SU x86) can be combined into one SU cluster.
SU clusters enable the Live Migration (LM) function for migrating BS2000 systems from
one SU to another.
● Support of LDAP accounts
LDAP accounts can be used for all user roles. The SE Manager enables the LDAP
configuration, which is the prerequisite to use LDAP accounts.
● Audit logging
The administrator is able to track changes to objects or to the configuration of the SE
server, including the user, time and action involved. The system logs all actions
performed in the SE Manager or via the CLI.
16 U41855-J-Z125-3-76
Introduction Changes since the last edition of the manual
● Event logging
Events in the SE server configuration are logged with a weighting. The logging includes
events triggered by the StorMan add-on.
● Alarm management
The administrator can configure the automatic messaging (via SNMP trap or E-Mail)
that is triggered for events from a certain weighting.
● For BS2000 devices, the number of free licenses is displayed.
● For SU /390, an emergency system is provided. For this purpose, two emulated disks
are provided on the MU.
● For AU PQ with Oracle VM Server, the SE Manager enables direct access to the Oracle
VM console.
As of Service Pack 1 of the basic software M2000 / X2000 / HNC V6.2A, the following
changes result:
● Additional AU models are supported:
– the PRIMERGY-based AU25 M4
– the PRIMEQUEST-based AUQ38E and DBU38E
● With regard to the hardware basis, AUs are generally distinguished by AU PY
(PRIMERGY-based) and AU PQ (PRIMEQUEST-based).
● For SU / 390 the dialog box Initiate IMPL / Change BS2000 operation mode is now available
in the BS2000 operating mode tab in the Actions group. The dialog permits you to initiate
the IMPL and optionally to change the operation mode. After the execution of the IMPL,
a BS2000 IPL is always initiated.
● For SU / 390, the BS2000 operation mode tab and the VM menus Disks, KVP, LAN and
Tape devices now also provide links for managing the IORSF files in the Devices menu.
● For Audit Logging and Event Logging in the main menu Logging, a new calendar function
facilitates the entry of date and time, if the time period for the displayed entries should
be changed.
U41855-J-Z125-3-76 17
Notational conventions Introduction
1.5 Notational conventions
The following notational conventions are used in this manual:
I
V
Ê
italics
monospace
monospaced
semibold
<abc>
[Key symbols]
[ ] The titles of related publications in the text are abbreviated. The complete title of
each publication which is referred to by a number is listed in the Related
Publications chapter after the associated number.
This symbol indicates important information and tips which you should bear
in mind.
This symbol and the word CAUTION! precede warning information. In the
interests of system and operating security you should always observe this
information.
The action which you must perform is indicated by this symbol.
Texts from the SE Manager (e.g. menu name, tab)
System inputs and outputs
Statements which are entered via the keyboard are displayed in this font.
Variables which are replaced by values.
Keys are displayed as they appear on the keyboard. When uppercase letters
need to be entered, the Shift key is specified, e.g. [SHIFT] - [A] for A. If two
keys need to be pressed at the same time, this is indicated by a hyphen
between the key symbols.
18 U41855-J-Z125-3-76
Introduction Names and abbreviations
1.6 Names and abbreviations
Because the names are used frequently, for the sake of simplicity and clarity the following
abbreviations are employed:
● SE server for the FUJITSU Server BS2000 SE Series (Server Units /390 and x86) with
the following models:
● SE700 for FUJITSU Server BS2000 SE700 / SE700B
(with SU700, more than one SU300 and AU optional)
● SE500 for FUJITSU Server BS2000 SE500 / SE500B
(with SU500, more than one SU300 and AU optional)
● SE300 for FUJITSU Server BS2000 SE300 / SE300B
(with SU300, more than one SU300 and AU optional)
● SU for the Server Unit irrespective of the unit type
A distinction is made between SUs depending on the unit type:
● SU /390 for Server Unit /390 (type of Server Unit with one or more /390 processors)
● SU x86 for Server Unit x86 (type of Server Unit with one or more x86 processors)
Based on the different models, a distinction is made between the following SUs:
● SU700 for the Server Unit of the unit type SU /390 in SE700 and SE700B
● SU500 for the Server Unit of the unit type SU /390 in SE500 and SE500B
● SU300 for the Server Unit of the unit type SU x86 in SE300, optionally in SE500 /
SE700 or SE500B / SE700B
● MU for the Management Unit. The MU enables centralized, user-friendly and cross-
system management on the SE server.
● AU for the Application Unit (with x86-based hardware)
A distinction is made between AUs depending on the hardware base:
● Application Unit PY for a PRIMERGY-based AU (e.g. hardware model AU25 or
AU47).
● Application Unit PQ for a PRIMEQUEST-based AU (e.g. hardware model AU87 or
DBU87).
● HNC (High Speed Network Connect) connects the SU /390 with the LAN and as a net
client also permits access to the Net-Storage. HNC designates both Linux-based basic
software and the hardware unit itself on which this basic software executes.
U41855-J-Z125-3-76 19
Open Source Software Introduction
● BS2000 server as the generic term for all SE servers and the existing S and SQ
servers. BS2000 servers are operated with the relevant BS2000 operating system.
● BS2000 for the BS2000 OSD/BC operating system in compound nouns, e.g. BS2000
system.
1.7 Open Source Software
The Linux-based basic software M2000, X2000, and HNC which is installed on the
Management Unit, Server Unit x86, and HNC contains Open Source Software. The
licenses for this can be found in the LICENSES directory on the relevant installation DVD.
20 U41855-J-Z125-3-76
2 Architecture and strategies
2.1 Architecture
In the maximum configuration, a FUJITSU Server BS2000 of the SE Series (SE server for
short) consists of the following components:
● Management Unit (MU) with SE Manager
The operation of the SE server with a single Management Unit is called a "single-MU
configuration". The Management Unit can be redundant in design. An SE server
configuration with more than one Management Unit (MU redundancy on the SE server
or Management Cluster with two SE servers) is called "multi-MU configuration".
MU redundancy ensures that the components of the SE server can still be operated if
one MU fails. In particular this means that the SKP functionality is then still available for
operating an SU /390.
● Server Unit (SU)
– An SU /390 enables operation of BS2000 (Native BS2000 or VM2000).
– An SU x86 enables operation of BS2000 (Native BS2000 or VM2000). XenVM
operation with Linux or Windows guest systems is also possible as an option.
Depending on the model family, the following combinations are possible:
– SE700 with an SU /390 and optionally up to two further SU x86
– SE500 with an SU /390 and optionally up to two further SU x86
– SE300 with an SU x86 and optionally up to two further SU x86
● Application Unit (AU)
Multiple AUs can be operated on the SE server. An AU enables operation of
applications under Linux, Windows or hypervisor-based systems.
A distinction is made between AUs depending on the hardware base:
● Application Unit PY refers to all PRIMERGY-based AUs (e.g. hardware model AU25
or AU47).
● Application Unit PQ refers to all PRIMEQUEST-based AU (e.g. hardware model
AU87 or DBU87).
U41855-J-Z125-3-76 21
Architecture Architecture and strategies
● Net Unit (NU)
The Net Unit offers maximum performance and security for internal communication in
an SE server and for a connection to customer networks (IP networks). For an SU /390,
HNC is an additional component of the Net Unit.
In the case of SE500 and SE700 the Net Unit is always redundant in design. In the case
of SE300 redundancy of the Net Unit is optional.
The Net Unit is supplied preconfigured, is autonomous with respect to SE server
management, and can easily be connected to the customer network.
● Rack console and KVM switch
● Peripherals (storage)
● Optional hardware components:
Disk storage systems (for SU x86, AU), tape library systems (for SU x86), FC switches
22 U41855-J-Z125-3-76
Architecture and strategies Architecture
Redundant Management Unit (MU) with SE Manager
Customer network
Net Unit
SE Server
(IP networks)
Management Unit (MU) with SE Manager
Redundant Net Unit
BS2000
Linux
Windows
Disk
Tape
Disk
VMware, Citrix,
Hyper-V, OVM ...
Further optional
peripherals
VM2000
Xen
VM2000
Windows
Linux
BS2000
BS2000
Peripherals
Application
Server Unit x86Server Unit /390
Unit (AU)
(SU /390) (SU x86)
All components of the SE server are integrated into a joint rack or multiple racks.
Information on the current hardware configuration of your SE server is displayed by the
SE Manager in the Hardware → HW Inventory menu (see section “HW inventory” on
page 285).
Figure 1: Architecture of SE servers
The SE Manager enables you to operate and manage all components of the SE server
centrally from the Management Unit. The SE Manager offers a user-friendly, web-based
user interface for this purpose.
U41855-J-Z125-3-76 23
Software of the SE server Architecture and strategies
2.2 Software of the SE server
2.2.1 Structure of the software
M2000
M2000 is the basic software of the Management Unit. It provides, among other things, the
following main functions for accessing SE servers:
● SE Manager as Single Point of Administration (central operation and administration of
the SE servers)
– Operation and administration of the BS2000 systems on SU /390 and SU x86
(BS2000 console, BS2000 dialog, SVP console on SU /390)
– Operation and administration of the XenVMs on SU x86
– Operation and administration of VMs on AUs
– Realizes the data collection and storage necessary for managing and operating the
SE server.
Receives events from all instances of the SE server for displaying, editing and
forwarding.
In the case of a multi-MU configuration, these internal functions are coordinated
between the MUs.
● Role and user strategy
● Net Unit functions for integration of the SE server into the network world
● SE Desktop for operation on the local console of the Management Unit
● Integration into the Remote Service
X2000
X2000 is the basic software of the SU x86. It provides, among other things, the following
functions:
● Execution system for BS2000 systems and XenVMs (including I/O system)
● Management functions for administering the BS2000 VMs and the XenVMs in the SE
Manager
● Management functions for administering the BS2000 devices and the XenVM devices
in the SE Manager
● Configuration of the Net-Storage for the BS2000 systems of the SU x86
24 U41855-J-Z125-3-76
Architecture and strategies Software of the SE server
HNC
HNC is the basic software of the HNC. It provides, among other things, the following
functions:
● Network connection for the BS2000 systems of the SU /390
● Configuration of the Net-Storage for the BS2000 systems of the SU /390
Add-on packs
In addition to the standard software M2000, X2000, and HNC, the SE server offers
enhancements by means of add-on packs.
The possible installation of add-on packs on the MU enables costs and maintenance to be
avoided on the SE server for additional servers, e.g. for ROBAR or openSM2. See also
section “Add-on pack” on page 27.
2.2.2 Software status, system version and update status
In addition to the system version, the software status also includes the updates which are
installed on the unit. Software updates can only be installed if they are available on the local
system.
Under SW version in the system information the SE Manager displays on the MU, SU x86,
and HNC the version of the basic software M2000, X2000 or HNC, including the update
status.
On the SU /390 the SE Manager displays the HCP (Hardware Control Program) software
(e.g. in the SU /390 information on page 201), but in this case does not support update
management.
The software status consequently has the following components:
Component Example Description
Version 6.2A
Revision REV=0100 Update status
Security fix 6.2A, No.001 – Security fixes are assigned to a version and update
status.
– Security fixes have a sequence number for each
version status and each update status (001 in the
example)
Hot fix 6.2A, REV=0100,
A0603507-H03
U41855-J-Z125-3-76 25
– Hot fixes are assigned to a version and update status
– In their name hot fixes contain a problem message
number (A0603507 in the example) and a sequence
number (H03 in the example)
Software of the SE server Architecture and strategies
In contrast to the other update types, add-on packs are autonomous software products
which FUJITSU makes available for installation on the Management Units. An add-on pack
is either a software product which is installed by default (e.g. StorMan on the Management
Unit) or one which is optional.
Add-on packs are managed like updates to the basic software, but the software status
displayed consists of the product name and a product-specific version designation.
2.2.3 Updates to the basic software and add-on packs
You can transfer the following types of updates to the Management Unit, the SU x86 and
the HNC and manage them there:
– Security fix
– Hot fix
– Add-on pack
2.2.3.1 Naming conventions
Updates are supplied as files of the following types:
● iso.gz for files which can be downloaded from the download server
● iso for files which are supplied on CD/DVD
The following naming conventions apply for the files containing the updates:
Security fix e.g. MV6.2A.SF.001.iso[.gz]
The security fix with the number 001 is assigned to the version and update status
6.2A.
Hot fix e.g. MV6.2A0100.A0603507-H03.iso[.gz]
The hot fix with the name A0603507-H03 is assigned to the version and update
status 6.2A REV=0100.
Add-on pack e.g. MV.STORMAN-7.0.0-12.4.iso
This add-on pack contains StorMan V7.0
The first letter in the file name indicates the basic software of the associated unit:
– X for X2000 on the Server Unit
– M for M2000 on the Management Unit
– H for HNC on the HNC
26 U41855-J-Z125-3-76
Architecture and strategies Software of the SE server
2.2.3.2 Security fix
A security fix contains all the security-relevant updates for the Linux-based basic software.
Security fixes protect the system against, for example, unauthorized intrusion and attacks
from the outside. Whether you install current security fixes depends on your security
requirements and whether the SE server can be accessed only via the protected
administration LAN or also from the outside. The functional use of the SE server is also
guaranteed without the current security fixes.
A security fix may also be installed by the customer. Installation takes place in the SE
Manager under an administrator account.
2.2.3.3 Hot fix
A hot fix contains a patch with which an urgent problem in your system can be rectified as
quickly as possible.
A hot fix can only be installed by Customer Support. Installation can only be performed
using a CLI command under the Customer Support account.
2.2.3.4 Add-on pack
Add-on packs are software components on a unit which have their own web interfaces that
are integrated into the SE Manager. The type and location of the integration into the SE
Manager depends on the category to which the add-on pack is to be assigned, e.g.
Application, Monitoring, Hardware Management.
Add-on packs have their own version schema and can be replaced independently of the
basic software.
An add-on package contains software which FUJITSU provides for use on the units.
Currently add-on packs are only provided for the Management Unit. By default a distinction
is made between installed and optional add-on packs:
– In the case of an add-on pack which is installed by default, the customer must, if
necessary, install newer versions.
– In the case of an optional add-on pack, the customer must also perform installation or
uninstallation. Customer Support can also do this when requested.
Add-on packs are also distinguished by whether they are chargeable or included in the price
and preinstalled.
U41855-J-Z125-3-76 27
Software of the SE server Architecture and strategies
The fact that the web interfaces of the add-on packs are integrated into the SE Manager
means the following:
– The add-on packs are visible as links in the SE Manager's menu.
– When such a link is clicked, the add-on pack's web interface is opened in the same
browser window.
– You log into the add-on pack's web interface implicitly using the account with which you
are working in the SE Manager and in the same session. The same setting therefore
applies for the session timeout in the event of inactivity. Logging off in the add-on also
leads to logging off in the SE Manager and thus to the login window of the SE Manager.
– From the add-on pack's web interface there is a link back to the last valid main window
in the SE Manager.
Add-on packs have their own online help systems and, when necessary, are described in
separate product manuals. These online helps are integrated into that of the SE Manager,
but can also be called separately.
Overview of the current add-on packs in the SE Manager on the MU:
Add-on
(product name)
OPENSM2
(openSM2 Performance Monitor)
OPENUTM
(openUTM Server Administration)
ROBAR
(ROBAR-SV Server)
STORMAN
(Storage Manager)
Table 1: Add-on packs in the SE Manager on the MU
ChargeablePreinstalled
Yes Optional Category: Monitoring
Yes No Category: Application
Yes Optional Category: Application
No Yes Category: Hardware
ex works
Integration into the
SE Manager
→ Performance
→ Applications → SE management
application
→ Applications → SE management
application
Management
→ Hardware → Storage
28 U41855-J-Z125-3-76
Loading...