Fujitsu ServerView Virtual-IO Manager User Manual
User Guide - English
ServerView Suite
ServerView Virtual-IO Manager V3.1
User Guide
Edition October 2012
Comments… Suggestions… Corrections…
The User Documentation Department would like to know your opinion of
this manual. Your feedback helps us 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 © 1998 - 2012 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.
Contents
Contents 3
1 Introduction 11
1.1 Target groups and objective of this manual 12
1.2 System requirements 12
1.3 Supported Hardware 14
1.4 Changes since the previous edition 21
1.5 ServerView Suite link collection 21
1.6 Documentation for the ServerView Suite 23
1.7 Typographic conventions 24
2 Virtual-IO Manager - Introduction 25
2.1 Virtual addresses 25
2.2 Special connection blade for blade server 25
2.3 Management with VIOM - Procedure 28
2.4 Defining networks (LAN) (for blade servers only) 30
2.5 Server profiles 43
2.5.1 Defining server profiles 44
2.5.2 Assigning server profiles 44
2.5.3 Dedicated LAN connections (only for blade servers) 45
2.5.4 Virtualizing I/O parameters 45
2.6 Server profile failover (for blade servers only) 47
2.7 High-Availability (HA) support 48
3 Installation and uninstallation 57
3.1 Prerequisites for the VIOM installation 57
3.2 Installing the Virtual-IO Manager on a Windows-based CMS 58
3.2.1 Installing the Virtual-IO Manager using a graphical interface
3.2.2 Installing the Virtual-IO Manager using the command line
interface 68
3.3 Updating the Virtual-IO Manager on a Windows-based CMS 72
3.4 Installing the Virtual-IO Manager on a Linux-based CMS 73
3.4.1 Installing the Virtual-IO Manager using a graphical interface
3.4.2 Installing the Virtual-IO Manager using the command line 84
3.4.3 Important directories of Virtual-IO Manager 88
3.4.4 Collecting diagnostic information 89
59
74
ServerView Virtual-IO Manager 3
Contents
3.5 Updating the Virtual-IO Manager on a Linux-based CMS 89
3.6 License management 90
3.7 Updating ServerView Operations Manager 94
3.8 Upgrading or moving the SQL Server database 95
3.9 Uninstalling the Virtual-IO Manager 96
3.9.1 Uninstalling the Virtual-IO Manager on a Windows-based
CMS 96
3.9.2 Uninstalling the Virtual-IO Manager on a Linux-based CMS
4 Configuration 97
4.1 Configurations on the managed BX600 Blade Server 97
4.1.1 Supported hardware configurations for the connection
blades 97
4.1.1.1 LAN hardware configuration 98
4.1.1.2 Fibre Channel hardware configuration 99
4.1.2 Configuring the BX600 management blade 99
4.1.3 Configuring the I/O connection blades 101
4.1.4 Connecting IBP modules 104
4.1.4.1 Network - Overview 105
4.1.4.2 Notes and recommendations 106
4.2 Configurations on the managed BX400 Blade Server 109
4.2.1 Supported hardware configurations for the connection
blades 110
4.2.1.1 LAN hardware configuration 111
4.2.1.2 Fibre Channel hardware configuration 112
4.2.2 Configuring the BX400 management blade 113
4.2.3 Configuring the I/O connection blades 114
4.2.4 Connecting IBP modules 115
4.2.4.1 Network - Overview 116
4.2.5 Switch stacking support 117
4.3 Configurations on the managed BX900 Blade Server 118
4.3.1 Supported hardware configurations for the connection
blades 119
4.3.1.1 LAN hardware configuration 119
4.3.1.2 Fibre Channel hardware configuration 121
4.3.2 Configuring the BX900 management blade 121
4.3.3 Configuring the I/O connection blades 123
96
4 ServerView Virtual-IO Manager
Contents
4.3.4 Connecting IBP modules 126
4.3.4.1 Network - Overview 126
4.3.5 Switch stacking support 127
4.4 Configurations on the managed PRIMERGY rack server 129
4.5 VIOM server profile mapping 132
4.6 PCI slot location in PRIMERGY rack servers 133
4.7 Adding a server to the ServerView server list 135
5 Virtual-IO Manager user interface 137
5.1 Virtual-IO Manager main window 137
5.2 Tree view 139
5.2.1 Tree structure (Server List) 140
5.2.2 Tree structure (Profiles) 141
5.3 Tabs 142
5.3.1 Virtual-IO Manager tab 142
5.3.2 Setup tab 144
5.3.3 Ext. LAN Connections tab 148
5.3.3.1 Graphic tab on Ext. LAN Connections tab 148
5.3.3.2 Details tab on Ext. LAN Connections tab 150
5.3.4 Server Configuration tab 151
5.3.5 Chassis Configuration tab 156
5.3.6 Server Profiles view 158
5.4 Wizards 161
5.4.1 Create Network for IBP wizard (only for blade servers) 162
5.4.1.1 Select Type step (Create Network wizard) 163
5.4.1.2 Edit Properties step (Create Network wizard - internal
network) 164
5.4.1.3 Edit Properties step (Create Network wizard - single
/VLAN network) 165
5.4.1.4 Edit Properties step (Create Network wizard - dedicated service network) 168
5.4.1.5 DCB Properties step (Create Network wizard - single/VLAN network) 172
5.4.1.6 Add Networks step (Create Network wizard - VLAN
network) 174
5.4.2 Edit Uplink Set wizard 176
5.4.2.1 Edit Properties step (Edit Uplink Set wizard - single/VLAN network) 176
ServerView Virtual-IO Manager 5
Contents
5.4.2.2 Edit Properties step (Edit Uplink Set wizard - dedicated
service network) 180
5.4.2.3 DCB Properties (Edit Uplink Set wizard - single/VLAN
network) 183
5.4.2.4 Add Networks step (Edit Uplink Set wizard - VLAN network) 185
5.4.3 Create Server Profile wizard 187
5.4.3.1 Name step (Create Server Profile wizard) 187
5.4.3.2 Configure Cards step (Create Server Profile wizard) 189
5.4.3.3 IO-Channels step (Create Server Profile wizard) 190
5.4.3.4 Boot Parameter step (Create Server Profile wizard) 194
5.4.3.5 CNA Parameter step (Create Server Profile wizard) 200
5.4.3.6 Virtual Addresses step (Create Server Profile wizard)
5.4.3.7 Confirm step (Create Server Profile wizard) 204
5.4.4 Edit Server Profile wizard 205
5.4.4.1 Name step (Edit Server Profile wizard) 205
5.4.4.2 Configure Cards step (Edit Server Profile wizard) 207
5.4.4.3 IO-Channels step (Edit Server Profile wizard) 208
5.4.4.4 Boot Parameter step (Edit Server Profile wizard) 212
5.4.4.5 CNA Parameter step (Edit Server Profile wizard) 218
5.4.4.6 Virtual Addresses step (Edit Server Profile wizard) 220
5.4.4.7 Confirm step (Edit Server Profile wizard) 222
5.4.5 Save Configuration wizard 223
5.4.5.1 Select Action step (Configuration Backup/Restore wizard) 223
5.4.5.2 Select File step (Save Configuration Wizard) 224
5.4.5.3 Select File step (Restore Configuration wizard) 225
5.4.5.4 Select File step (Delete Backup Files wizard) 227
5.4.5.5 Select Data step (Save Configuration wizard) 228
5.4.5.6 Select Data step (Restore Configuration wizard) 229
5.4.5.7 Select Data step (Delete Backup Files wizard) 230
5.5 Dialog boxes 231
5.5.1 Authentication dialog box (single blade server) 231
5.5.2 Authentication dialog box (PRIMERGY rack server) 234
5.5.3 Authentication dialog box (PRIMERGY rack server and
blade server) 236
5.5.4 Licenses Information dialog box 237
202
6 ServerView Virtual-IO Manager
Contents
5.5.5 Preferences dialog box 238
5.5.6 Restore Options dialog box (servers) 241
5.5.7 Restore Options dialog box (server profiles) 243
5.5.8 Select Profile dialog box 245
5.6 Context menus 247
5.6.1 Context menus on the Ext. LAN Connections tab 247
5.6.2 Context menus in the Server Profiles view 248
5.6.3 Context menu on the Server Configuration tab 249
5.7 General buttons 251
5.7.1 Buttons in the area on the left 251
5.7.2 Button in the area on the right 251
5.7.3 General buttons in other dialog boxes 251
5.8 Icons 252
6 Using the Virtual-IO Manager 253
6.1 Starting the Virtual-IO Manager 253
6.2 Closing Virtual-IO Manager 253
6.3 Logging the actions using VIOM 254
6.3.1 Logging the actions on Windows 254
6.3.2 Logging the actions on Linux 256
7 Managing servers with VIOM 257
7.1 Activating management with VIOM 257
7.2 Changing access rights and ports 259
7.3 Deactivating management with VIOM 261
7.4 VIOM internal operations on blade servers 261
7.5 VIOM-internal operations on a PRIMERGYrack server 266
7.6 Displaying license information 275
8 Defining network paths (LAN) 277
8.1 Defining an uplink set 278
8.1.1 Defining an internal network 279
8.1.2 Defining a single network 280
8.1.3 Defining VLAN networks 282
8.1.4 Defining a dedicated service network 285
ServerView Virtual-IO Manager 7
Contents
8.2 Modifying an uplink set 285
8.3 Deleting networks 286
8.4 Copying an IBP configuration 287
8.5 Copying configuration 288
9 Defining and assigning server profiles 289
9.1 Defining server profiles 290
9.2 Viewing server profiles 294
9.3 Modifying server profiles 294
9.4 Copying server profiles 295
9.5 Deleting server profiles 296
9.6 Assigning server profiles 296
9.7 Deleting profile assignments 298
10 Viewing the blade server configuration 301
11 Saving and restoring 303
11.1 Saving your configuration and server profiles 303
11.2 Restoring the configuration 304
11.2.1 Restoring server profiles 305
11.2.2 Restoring blade server configurations 306
11.2.3 Restoring PRIMERGYrack server configurations 307
11.3 Deleting backup files on the management station 308
11.4 Restoring VIOM-specific configurations 308
11.4.1 Restoring an IBP module configuration 308
11.4.2 Deleting the configuration of an uninstalled IBP module 309
11.4.3 Restoring the configuration of a server blade slot 310
11.4.4 Restoring the blade server chassis configuration 311
12 Importing and exporting server profiles 313
12.1 Exporting server profiles 313
12.2 Importing server profiles 313
12.3 Format of export files 314
12.3.1 The Objects element 314
12.3.2 The ServerProfiles element 315
12.3.3 The ServerProfile element 316
12.3.4 The IOChannel element 319
12.3.5 The Address element 323
12.3.6 The BootEnvironment element 323
12.3.7 The ISCSIBootConfiguration element 324
8 ServerView Virtual-IO Manager
Contents
12.3.8 The FCBootConfiguration element 327
12.3.9 The DCBConfiguration element 329
12.3.10 The FunctionConfiguration element 329
13 VIOM scenarios 331
13.1 Shifting tasks from one server blade to another 331
13.2 Moving tasks using the server profile failover 332
13.3 Disaster Recovery 333
14 VIOM database 337
14.1 VIOM Backup Service 338
14.1.1 Configuring the job schedule on Windows 339
14.1.1.1 Syntax of Quartz cron expressions 340
14.1.2 Configuring the job schedule on Linux 342
14.1.3 Configuring the output directories 343
14.1.4 Starting the Backup Service on Windows 344
14.1.5 Starting the VIOM Backup Service on Linux 344
14.1.6 Logging the Backup Service 345
14.2 Restoring the VIOM database on Windows 345
14.2.1 Restoration via SQL Server Management Studio 345
14.2.2 Restoration via Enterprise Manager 349
14.2.3 Checking the database backup 349
14.3 Restoring the VIOM database on Linux 350
15 Appendix 353
15.1 Replacing IBP modules 353
15.2 VIOM address ranges 354
15.3 Creating diagnostic data 356
15.4 Event logging 359
ServerView Virtual-IO Manager 9
10 ServerView Virtual-IO Manager
1 Introduction
You use the ServerView Virtual-IO Manager (Virtual-IO Manager or VIOM for
short) software to manage the input/output parameters (I/O parameters) of following servers:
l PRIMERGYblade server (BX600, BX400, BX900)
In Japan, BX600 blade servers are not supported.
l PRIMERGY rack server (RX200 S7, RX300 S7, RX350 S7)
l PRIMERGY tower server (TX300 S7)
When PRIMERGY rack servers are mentioned below, both, the
PRIMERGY rack servers and the PRIMERGY tower servers, are
meant.
Additionally the LAN connection blade, the Intelligent Blade Panel (IBP) in
PRIMERGY blade servers, can be managed via VIOM.
As an extension to the ServerView Operations Manager, it is possible to manage a large number of PRIMERGY blade servers and PRIMERGY rack
servers centrally by the central management station using VIOM. This
includes virtualizing and, for blade servers, saving the server blade-specific
I/O parameters (MAC addresses, WWN addresses, I/O connections including the boot parameters) and configuring and managing a blade server's Intelligent Blade Panelin a hardware-independent server profile.
This server profile can be assigned to a PRIMERGY rack server or server
blade:
l For PRIMERGY rack servers: A server profile can be assigned to a
PRIMERGY rack server and can also be moved from one PRIMERGY
rack server to another.
l For blade servers: The server profile can be assigned to a server blade
using VIOM and can also be moved between different server blades of
the same or of another blade server.
By assigning the server profiles to a server, you can start the required application without having to reconfigure the SAN and LAN network.
ServerView Virtual-IO Manager 11
1 Introduction
VIOM provides an easy-to-use Web-based graphical user interface, which
you can launch using the ServerView Operations Manager. Using this interface, you can carry out all the necessary tasks for managing the I/O parameters of a PRIMERGY blade server or PRIMERGY rack server and for the
LAN connection blade, the IBP module in PRIMERGY blade server.
VIOM also provides a comprehensive command line interface, which you
can use to perform administrative VIOM tasks in a script-based environment.
The VIOM CLI (command line interface) provides an easy-to-use interface for
creating scripts and automating administrative tasks.
The command line interface is available both on Windows and Linux platforms, and you install it using separate installation packages. For more information on VIOM CLI, see the documentation entitled "ServerView Virtual-IO
Manager Command Line Interface".
1.1 Target groups and objective of this manual
This manual is aimed at system administrators, network administrators and
service professionals, who have a sound knowledge of hardware and software. The manual describes the functionality and user interface of theVirtualIO Manager.
1.2 System requirements
Central management station
l Operating system for the central management station
o
Microsoft Windows® ServerTM2003 all editions
o
Microsoft Windows® ServerTM2003 R2 all editions
o
Microsoft Windows® ServerTM2008 all editions
o
Microsoft Windows® ServerTM2008 R2 all editions
o
Linux Novell (SLES10): SP2 and SP3
o
Novell (SLES 11): SP1 and SP2
12 ServerView Virtual-IO Manager
1.2 System requirements
o
Red Hat RHEL5.6/5.7/5.8
o
Red Hat RHEL 6, 6.1/6.2
In Japan: Novell SLES is not supported.
ServerView Virtual-IO Manager can also be installed in Virtual Machine
(VM) under Windows Hyper-V or VMware ESX server. The operating
system running on the VM must be one of the above listed operating systems and must be supported by the used hypervisor.
l Installed software packages
o
ServerView Operations Manager as of Version 5.50.13
o
Java Runtime Environment (JRE) version 6.0, update 31 or higher
Together with ServerView Operations Manager 6.10, it is
also possible to use JRE version 7.0, update 7 or higher.
l Fire wall settings
o
Port 3172 must be opened for TCP/IP connection to Remote Connector Service.
o
Port 162 must be opened to receive SNMP traps from iRMC when
managing PRIMERGY rack servers.
You can also obtain the current requirements from the release notes. You find
the release notes e.g. on a Windows-based management station under Start
- [All] Programs - Fujitsu - ServerView Suite - Virtual-IO Manager Release Notes.
License
You must purchase licenses to use the Virtual-IO Manager. At least one
license is required. Each license contains a count which determines the
allowed number of server profile assigns. If more than one license is registered, the counts are added together.
ServerView Virtual-IO Manager 13
1 Introduction
1.3 Supported Hardware
Managed BX600 blade servers
Supported systems: BX600 S3 with MMB S3. For information on the required
firmware version, see the release notes included.
The following table shows which server blades are supported with which
range of functions.
Server blade Scope of functions
BX620 S2, BX620 S3 Server profiles without I/O virtualization but with net-
work connection definition
BX620 S4, BX620 S5,
BX620 S6
Server profiles with I/O virtualization and network
connection definition
BX630 Server profiles without I/O virtualization but with net-
work connection definition
BX630 S2 Server profiles with I/O virtualization and network
connection definition
Table 1: Supported server blades
For information on the BIOS and iRMC firmware version, see the release
notes supplied.
The Virtual-IO Manager can only manage BX600 chassis with S3
management blades (MMB S3) that are assembled with the following:
l In fabric 1: IBP or LAN modules
l In fabric 2: IBP modules, LAN modules or FC switch blades of
the type SW4016
You must not mix the modules within a fabric.
Fabric 2 can also be empty. Only one of the permitted connection
blades can be inserted in fabric 1 and 2 at each time.
14 ServerView Virtual-IO Manager
1.3 Supported Hardware
In Japan, BX600 blade servers are not supported.
Managed BX400 blade servers
Supported systems: BX400 with MMB S1. For information on the required
firmware version, see the release notes supplied.
The following table shows which server blades are supported with which
range of functions.
Server
blade
BX920 S2,
BX920 S3
BX922 S2 Server profiles with I/O virtualization and network connection
BX924 S2,
BX924 S3
Table 2: Supported server blades
For information on the BIOS and iRMC firmware version, see the release
notes supplied.
Scope of functions
Server profiles with I/O virtualization and network connection
definition
definition
Server profiles with I/O virtualization and network connection
definition
ServerView Virtual-IO Manager 15
1 Introduction
The Virtual-IO Manager can only manage BX400 chassis with S1
management blades (MMB S1) that are assembled with the following:
l In fabric 1:
l In fabric 2:
o
LAN connection blades (PY CB Eth Switch/IBP 1 Gb
36/8+2 (SB11), PY CB Eth Switch/IBP 1 Gb 36/12
(SB11A), PY CB Eth Switch/IBP 1 Gb 18/6 (SB6), or PY
CB Eth Switch/IBP 10 Gb 18/8 (SBAX2)) in switch mode or
IBP mode, or
o
LAN pass thru connection blades (PY CB Eth Pass Thru 10
Gb 18/18)
o
LAN connection blades (PY CB Eth Switch/IBP 1 Gb
36/8+2, PY CB Eth Switch/IBP 1 Gb 36/12, PY CB Eth
Switch/IBP 1 Gb 18/6, or PY CB Eth Switch/IBP 10 Gb
18/8) in switch mode or IBP mode,
o
LAN pass thru connection blades (PY CB Eth Pass Thru 10
Gb 18/18),
o
FC switch blades of the type Brocade 5450, or
o
FC pass thru connection blades (PY CB FC Pass Thru 8
Gb 18/18)
l In fabric 3: same as fabric 2
The LAN connection blades in fabric 3 must run in the same mode.
However, only one connection blade can be inserted in fabric 3.
You must not switch the mode of a LAN connection blade if you are
using the Virtual-IO Manager to manage the BX400 chassis.
16 ServerView Virtual-IO Manager
1.3 Supported Hardware
Managed BX900 blade servers
Supported systems: BX900 with MMB S1. For information on the required
firmware version, see the release notes supplied.
The following table shows which server blades are supported with which
range of functions.
Server
blade
BX920 S1,
BX920 S2,
BX920 S3
BX922 S2 Server profiles with I/O virtualization and network connection
BX924 S2,
BX924 S3
BX960 S1 Server profiles with I/O virtualization and network connection
Table 3: Supported server blades
For information on the BIOS and iRMC firmware version, see the release
notes supplied.
Scope of functions
Server profiles with I/O virtualization and network connection
definition
definition
Server profiles with I/O virtualization and network connection
definition
definition
ServerView Virtual-IO Manager 17
1 Introduction
The Virtual-IO Manager can only manage BX900 chassis with S1
management blades (MMB S1) that are assembled with the following:
l In fabric 1:
l In fabric 2:
o
LAN connection blades (PY CB Eth Switch/IBP 1 Gb
36/8+2 (SB11), PY CB Eth Switch/IBP 1 Gb 36/12
(SB11A), PY CB Eth Switch/IBP 1 Gb 18/6 (SB6), or PY
CB Eth Switch/IBP 10 Gb 18/8 (SBAX2)) in switch mode or
IBP mode, or
o
LAN pass thru connection blades (PY CB Eth Pass Thru 10
Gb 18/18)
o
LAN connection blades (PY CB Eth Switch/IBP 1Gb
36/8+2, PY CB Eth Switch/IBP 1Gb 36/12, PY CB Eth
Switch/IBP 1Gb 18/6, or PY CB Eth Switch/IBP 10 Gb
18/8) in switch mode or IBP mode, or
o
LAN pass thru connection blades (PY CB Eth Pass Thru 10
Gb 18/18),
o
FC switch blades of the type Brocade 5450
o
FC pass thru connection blades (PY CB FC Pass Thru 8
Gb 18/18)
l In fabric 3: same as fabric 2
l In fabric 4: same as fabric 1
The LAN connection blades in a fabric must run in the same mode.
However, only one connection blade can be inserted in a fabric.
You must not switch the mode of a LAN connection blade if you are
using the Virtual-IO Manager to manage the BX900 chassis.
18 ServerView Virtual-IO Manager
1.3 Supported Hardware
Managed PRIMERGY rack servers und PRIMERGY tower servers
The following PRIMERGY rack and tower server models are supported:
PRIMERGY
Scope of functions
model
RX200 S7 Assign VIOM server profiles with I/O address virtualization
RX300 S7
RX350 S7
and boot configuration for the onboard LAN ports and the supported PCI controller.
Network connection definition is not supported.
TX300 S7
For information on the BIOS and iRMC firmware version, see the release
notes supplied.
The following PCI controllers are supported for all the above PRIMERGY
rack server systems:
l Emulex 10GbE OCe10102 CNA
l Emulex 8Gb FC HBA LPe 12002
l Emulex 8Gb FC HBA LPe 1250 (1 channel)
l INTEL 2-port 10GbE (D2755 – Niantec)
l INTEL 4-port (D2745 - Barton Hills)
l INTEL 2-port (D2735 - Kawela 82576NS)
l INTEL Eth Ctrl 4x1Gb Cu PCIe x4 (D3045)
l INTEL Eth Ctrl 2x1Gb Cu PCIe x4 (D3035)
l INTEL 10GbE 10GBase-T(RJ45) PCIe LAN
ServerView Virtual-IO Manager 19
1 Introduction
PCI controller Scope of functions
Emulex 10GbE OCe10102
CNA
Emulex 8Gb FC HBA
LPe 12002
Emulex 8Gb FC HBA LPe
1250 (1 channel)
INTEL 2-port 10GbE
(D2755 – Niantec)
INTEL 4-port (D2745 - Barton Hills)
INTEL 2-port (D2735 Kawela 82576NS)
INTEL Eth Ctrl 4x1Gb Cu
PCIe x4 (D3045)
INTEL Eth Ctrl 2x1Gb Cu
PCIe x4 (D3035)
Define physical functions and type (LAN,
FCoE, iSCSI) of physical functions.
Assign virtual addresses to physical function
and optionally define boot parameter.
This CNA supports two physical functions for
each of both physical ports. The first physical
function must be of type LAN. The physical
functions for the two physical ports must be
defined similarly. This means that the storage
function for both physical ports must be of the
same type. When using iSCSI with iSCSI boot
the iSCSI initiator must be identical. Exception: physical port is completely disabled.
Assign virtual WWPN and WWNN.
Optionally define the first and second boot target and LUN.
Disable I/O ports.
Assign virtual MAC.
Optionally define PXE boot per port.
Disable I/O ports.
There is no explicit disable
functionality for I/O ports in
VIOM. I/O ports that are not
defined in a VIOM profile will
be implicitly disabled if the
device supports this functionality.
INTEL 10GbE 10GBaseT(RJ45) PCIe LAN
20 ServerView Virtual-IO Manager
1.4 Changes since the previous edition
For information on the required firmware version, see the release notes supplied.
1.4 Changes since the previous edition
The current edition is valid for ServerView Virtual-IO Manager V3.1 and
replaces the online manual "PRIMERGY ServerView Suite, ServerView Virtual-IO Manager V3.0", Edition March 2012.
ServerView Virtual-IO Manager V3.1 includes the following new features:
l Support for INTEL Eth Ctrl 4x1Gb Cu PCIe x4 (D3045), INTEL Eth Ctrl
2x1Gb Cu PCIe x4 (D3035), and INTEL 10GbE 10GBase-T(RJ45) PCIe
LAN in PRIMERGY rack servers.
l Support of VLAN groups in tagged mode in VIOM server profile (see
"Defining networks (LAN) (for blade servers only)" on page 30, "IO-Channels step (Create Server Profile wizard)" on page 190, and "IO-Channels
step (Edit Server Profile wizard)" on page 208).
l DCB settings also possible for iSCSI (see " CNA Parameter step
(Create Server Profile wizard)" on page 200 and "CNA Parameter step
(Edit Server Profile wizard)" on page 218).
l Video Redirection for server blades and rack servers (see "Server Con-
figuration tab" on page 151).
l User-specific display properties are stored session independent (see
"Preferences dialog box" on page 238).
l Support of JAVA Runtime Environment 7 (only with ServerView Oper-
ation Manager 6.10)
l The section "High Availability - HA" has been updated and now includes
VMware HA (see "High-Availability (HA) support" on page 48).
1.5 ServerView Suite link collection
Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.
ServerView Virtual-IO Manager 21
1 Introduction
For ServerView Suite, links are offered on the following topics:
l Forum
l Service Desk
l Manuals
l Product information
l Security information
l Software downloads
l Training
The downloads include the following:
o
Current software statuses for the ServerView Suite as well as additional Readme files.
o
Information files and update sets for system software components
(BIOS, firmware, drivers, ServerView agents and ServerView
update agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via
ServerView Update Manager Express.
o
The current versions of all documentation on the ServerView
Suite.
You can retrieve the downloads free of charge from the Fujitsu Technology Solutions Web server.
For PRIMERGY servers, links are offered on the following topics:
l Service Desk
l Manuals
l Product information
l Spare parts catalogue
Access to the link collection
You can reach the link collection of the ServerView Suite in various ways:
1. Via ServerView Operations Manager.
22 ServerView Virtual-IO Manager
1.6 Documentation for the ServerView Suite
l Select Help – Links on the start page or on the menu bar.
This opens the start page of the ServerView link collection.
2. Via the ServerView Suite DVD 2 or via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions
manual server.
You access the start page of the online documentation via the following link:
http://manuals.ts.fujitsu.com
l In the selection list on the left, select Industry standard servers.
l Click the menu item PRIMERGY ServerView Links.
This opens the start page of the ServerView link collection.
3. Via the ServerView Suite DVD 1.
l In the start window of the ServerView Suite DVD 1, select the
option Select ServerView Software Products.
l Click Start. This takes you to the page with the software products of
the ServerView Suite.
l On the menu bar select Links.
This opens the start page of the ServerView link collection.
1.6 Documentation for the ServerView Suite
The documentation for the ServerView Suite can be found on the ServerView
Suite DVD 2 supplied with each server system.
The documentation can also be downloaded free of charge from the Internet.
You will find the online documentation at http://manuals.ts.fujitsu.com under
the link Industry standard servers.
For an overview of the documentation to be found under ServerView Suite
as well as the filing structure, see the ServerView Suite sitemap (Server-
View Suite – Site Overview).
ServerView Virtual-IO Manager 23
1 Introduction
1.7 Typographic conventions
The following typographic conventions are used:
Convention Explanation
Indicates various types of risk, namely health risks, risk of data
loss and risk of damage to devices.
Indicates additional relevant information and tips.
bold Indicates references to names of interface elements.
monospace
monospace
semibold
Indicates system output and system elements, e.g., file names
and paths.
Indicates statements that are to be entered using the keyboard.
blue continuous text
pink continuous text
<abc> Indicates variables which must be replaced with real values.
[abc] Indicates options that can be specified (syntax).
[key]
Indicates a link to a related topic.
Indicates a link to a location you have already visited.
Indicates a key on your keyboard. If you need to enter text in
uppercase, the Shift key is specified, for example, [SHIFT] +
[A] for A. If you need to press two keys at the same time, this is
indicated by a plus sign between the two key symbols.
Screenshots
Some of the screenshots are system-dependent, so some of the details
shown may differ from your system. There may also be system-specific differences in menu options and commands.
24 ServerView Virtual-IO Manager
2 Virtual-IO Manager - Introduction
This chapter provides a general introduction to the concept of the Virtual-IO
Manager (VIOM).
2.1 Virtual addresses
Physical MAC addresses and WWN addresses are stored on the network
card or in the host bus adapter (HBA) of a server blade or PRIMERGY rack
server. If a server blade or PRIMERGY rack server has to be exchanged or
the operating system and/or the application has to be started on another
server, usually the LAN or SAN network has to be reconfigured. This means
that whilst the MAC address and the WWN addresses identify a physical
server blade, several administrators have to be involved.
To separate the administration areas from each other, it is necessary to keep
the I/O parameters (MAC and WWN) outwardly constant.
Using virtual addresses instead of the MAC addresses or WWN addresses
stored on the NIC (network interface card) or in the HBA, the addressing
remains constant even when a server blade is exchanged at the slot or a
PRIMERGY rack server is replaced by another one.
2.2 Special connection blade for blade server
Up to now, blade servers have been used essentially to connect the LAN
(Local Area Network) and Fibre Channel ports (FC ports) of individual server
blades to the LAN and SAN networks (SAN - Storage Area Network) using
switch blades or pass-thru blades, which are inserted in the blade chassis. It
is the responsibility of the LAN or SAN administrators to manage these
switches. This leads to an overlap of the different administration areas.
ServerView Virtual-IO Manager 25
2 Virtual-IO Manager - Introduction
Figure 1: Overlapping areas of responsibility
As the areas of responsibility overlap, this means that up to three administrators may be involved if a server blade's configuration changes, e. g.
because a server blade has to be replaced due to hardware problems and, as
a result, the switches have to be reconfigured.
The onboard LAN and FC controllers in the server blade are connected to the
installed LAN or FC switches via a midplane and are, in turn, connected to
the LAN and SAN network via their uplink ports. Providers use specific protocols or protocol extensions for switches from different manufacturers,
which can lead to interoperability problems between the internal and external
switches of different providers.
26 ServerView Virtual-IO Manager
2.2 Special connection blade for blade server
To resolve these problems, the switch blades installed in the blade server
can be replaced by special connection blades. The following connection
blade are available for this:
l For SAN:
BX600: BX600 4/4Gb FC Switch 12port (SW4016, SW4016-D4) in the
Access Gateway mode (FC AG)
BX400/BX900: Brocade 5450 8 Gb Fibre Channel Switch in the Access
Gateway mode (FC AG)
l For LAN:
BX600: BX600 GbE Intelligent Blade Panel 30/12 or 10/6 (IBP GbE)
BX400/BX900: Connection Blade PY CB Eth Switch/IBP 1Gb 36/8+2,
PY CB Eth Switch/IBP 1Gb 36/12, PY CB Eth Switch/IBP 1Gb 18/6, or
PY CB Eth Switch/IBP 10 Gb 18/8 in the IBP mode. (The connection
blades can run in switch mode, in IBP mode, or in End Host Mode
(EHM).)
These connection blades offer the advantage of a switch (cable consolidation) without the above-mentioned disadvantages.
ServerView Virtual-IO Manager 27
2 Virtual-IO Manager - Introduction
Figure 2: Separate areas of responsibility
2.3 Management with VIOM - Procedure
You use the ServerView Virtual-IO Manager (VIOM) to manage the connection blades of a blade server and to maintain the relevant I/O parameters
constant at the chassis slot of a blade server or at the PRIMERGY rack
server. VIOM is installed on the central management station and integrated in
the ServerView Operations Manager.
28 ServerView Virtual-IO Manager
2.3 Management with VIOM - Procedure
For blade servers, management with VIOM essentially includes the following
functions:
l Defining the network paths on the Intelligent Blade Panel (IBP module)
l Defining the I/O parameters (including virtual addresses) of a server
blade
l Saving the I/O parameters in combination with the required network
paths in server profiles
l Assigning the server profiles to the server blades or to empty slots as
well as moving a server profile between any number of server blades
You can assign the server profiles to any number of different server blades of
a blade server or even to another blade server, provided that the required network connections are available on the respective chassis.
For PRIMERGY rack servers, management with VIOM essentially includes
the following functions:
l Defining the I/O parameters (including virtual addresses) of a PRIM-
ERGY rack server
l Saving the I/O parameters in server profiles
l Assigning the server profiles to a PRIMERGY rack server
Before you can execute the functions above, a blade server chassis or PRIMERGY rack server must be managed by VIOM. You also do this using the
GUI of the Virtual-IO Manager (see chapter "Managing servers with VIOM"
on page 257).
Management using VIOM is divided into the following key steps:
1. Before VIOM can work with a blade server chassis or PRIMERGY rack
server it must be managed by VIOM.
2. For blade servers with IBP, you can define external network connections.
3. You then define the corresponding profiles for all applications/images
and save them in the server profile repository on the central management
station.
ServerView Virtual-IO Manager 29
2 Virtual-IO Manager - Introduction
4. You can then assign these server profiles to any of the individual slots of
a blade server or to a PRIMERGY rack server.
5. If required, you can remove the assignment of the server profile.
For blade server, you can move the profiles from one blade server slot to
another, or move them to another blade server. For PRIMERGY rack
servers, you can move the profiles from one server to another server.
2.4 Defining networks (LAN) (for blade servers only)
In order for VIOM to be able to switch the network paths correctly when
assigning profiles, first VIOM has to know which networks are present on the
respective chassis on which uplink ports.
This also makes it possible to separate individual server blades or groups of
server blades from a network perspective so that two server blade groups do
not have any connection to each other in terms of network.
Defining network paths on an IBP module includes the following steps:
l Defining an uplink set.
An uplink set comprises one or several uplink ports. An uplink port is an
external port that connects the chassis with your LAN infrastructure. If
an uplink set is used by several virtual network connections (VLANs),
the uplink set is referred to as a shared uplink set.
l Defining one or several networks that are assigned to the uplink set.
The definition of a network in the context of VIOM, refers to
the allocation of a meaningful name for network access from
outside the network
30 ServerView Virtual-IO Manager
Loading...