Résumé du contenu de la page N° 1
User Guide - English
ServerView Suite
ServerView Virtual-IO Manager V3.1
User Guide
Edition October 2012
Résumé du contenu de la page N° 2
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 man- agement system which complie
Résumé du contenu de la page N° 3
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
Résumé du contenu de la page N° 4
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 96 4 Configuration 97 4.1 Configurations on the managed BX600 Blade Server 97 4.1.1 Supported hardware configurations for the connecti
Résumé du contenu de la page N° 5
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 Vi
Résumé du contenu de la page N° 6
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 net- work) 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
Résumé du contenu de la page N° 7
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 ot
Résumé du contenu de la page N° 8
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
Résumé du contenu de la page N° 9
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.
Résumé du contenu de la page N° 10
10 ServerView Virtual-IO Manager
Résumé du contenu de la page N° 11
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 fol- lowing servers: l PRIMERGY blade 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. Additiona
Résumé du contenu de la page N° 12
1 Introduction VIOM provides an easy-to-use Web-based graphical user interface, which you can launch using the ServerView Operations Manager. Using this inter- face, you can carry out all the necessary tasks for managing the I/O param- eters 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
Résumé du contenu de la page N° 13
1.2 System requirements o Red Hat RHEL 5.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 sys- tems 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
Résumé du contenu de la page N° 14
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, Server profiles with I/O virtualization and network BX620 S6 conn
Résumé du contenu de la page N° 15
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 Scope of functions blade BX920 S2, Server profiles with I/O virtualization and network connection BX920 S3 definition BX922 S2 Server profiles with I/O virtualization and network con
Résumé du contenu de la page N° 16
1 Introduction The Virtual-IO Manager can only manage BX400 chassis with S1 management blades (MMB S1) that are assembled with the fol- lowing: l In fabric 1: 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) l In fabric 2: o LAN connection blades (PY CB Eth Swi
Résumé du contenu de la page N° 17
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 Scope of functions blade BX920 S1, Server profiles with I/O virtualization and network connection BX920 S2, definition BX920 S3 BX922 S2 Server profiles with I/O virtualization and network connection definition BX924 S2, Server pro
Résumé du contenu de la page N° 18
1 Introduction The Virtual-IO Manager can only manage BX900 chassis with S1 management blades (MMB S1) that are assembled with the fol- lowing: l In fabric 1: 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) l In fabric 2: o LAN connection blades (PY CB Eth Swi
Résumé du contenu de la page N° 19
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 and boot configuration for the onboard LAN ports and the sup- RX300 S7 ported PCI controller. RX350 S7 Network connection definition is not supported. TX300 S7 For information on the BIOS and iRMC firmware version, see the release notes supplied. The
Résumé du contenu de la page N° 20
1 Introduction PCI controller Scope of functions Emulex 10GbE OCe10102 Define physical functions and type (LAN, CNA 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 mus
