1. Manuals
  2. Brands
  3. Fujitsu Manuals
  4. Software
  5. ServerView Virtual-IO Manager V3.1
  6. User manual

Fujitsu ServerView Virtual-IO Manager V3.1 User Manual

Serverview suite
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
User Guide - English
ServerView Suite
ServerView Virtual-IO Manager V3.1
User Guide
Edition October 2012

Advertisement

Table of Contents
loading

Related Manuals for Fujitsu ServerView Virtual-IO Manager V3.1

Summary of Contents for Fujitsu ServerView Virtual-IO Manager V3.1

  • Page 1 User Guide - English ServerView Suite ServerView Virtual-IO Manager V3.1 User Guide Edition October 2012...

  • Page 2: Copyright And Trademarks

    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...

  • Page 3: Table Of Contents

    Contents Contents 1 Introduction 1.1 Target groups and objective of this manual 1.2 System requirements 1.3 Supported Hardware 1.4 Changes since the previous edition 1.5 ServerView Suite link collection 1.6 Documentation for the ServerView Suite 1.7 Typographic conventions 2 Virtual-IO Manager - Introduction 2.1 Virtual addresses 2.2 Special connection blade for blade server 2.3 Management with VIOM - Procedure...
  • Page 4 Contents 3.5 Updating the Virtual-IO Manager on a Linux-based CMS 3.6 License management 3.7 Updating ServerView Operations Manager 3.8 Upgrading or moving the SQL Server database 3.9 Uninstalling the Virtual-IO Manager 3.9.1 Uninstalling the Virtual-IO Manager on a Windows-based 3.9.2 Uninstalling the Virtual-IO Manager on a Linux-based CMS 4 Configuration 4.1 Configurations on the managed BX600 Blade Server 4.1.1 Supported hardware configurations for the connection...

  • Page 5: Edit Properties Step

    Contents 4.3.4 Connecting IBP modules 4.3.4.1 Network - Overview 4.3.5 Switch stacking support 4.4 Configurations on the managed PRIMERGY rack server 4.5 VIOM server profile mapping 4.6 PCI slot location in PRIMERGY rack servers 4.7 Adding a server to the ServerView server list 5 Virtual-IO Manager user interface 5.1 Virtual-IO Manager main window 5.2 Tree view...
  • Page 6 Contents 5.4.2.2 Edit Properties step (Edit Uplink Set wizard - dedicated service network) 5.4.2.3 DCB Properties (Edit Uplink Set wizard - single/VLAN network) 5.4.2.4 Add Networks step (Edit Uplink Set wizard - VLAN net- work) 5.4.3 Create Server Profile wizard 5.4.3.1 Name step (Create Server Profile wizard) 5.4.3.2 Configure Cards step (Create Server Profile wizard) 5.4.3.3 IO-Channels step (Create Server Profile wizard)
  • Page 7 Contents 5.5.5 Preferences dialog box 5.5.6 Restore Options dialog box (servers) 5.5.7 Restore Options dialog box (server profiles) 5.5.8 Select Profile dialog box 5.6 Context menus 5.6.1 Context menus on the Ext. LAN Connections tab 5.6.2 Context menus in the Server Profiles view 5.6.3 Context menu on the Server Configuration tab 5.7 General buttons 5.7.1 Buttons in the area on the left...
  • Page 8 Contents 8.2 Modifying an uplink set 8.3 Deleting networks 8.4 Copying an IBP configuration 8.5 Copying configuration 9 Defining and assigning server profiles 9.1 Defining server profiles 9.2 Viewing server profiles 9.3 Modifying server profiles 9.4 Copying server profiles 9.5 Deleting server profiles 9.6 Assigning server profiles 9.7 Deleting profile assignments 10 Viewing the blade server configuration...
  • Page 9 Contents 12.3.8 The FCBootConfiguration element 12.3.9 The DCBConfiguration element 12.3.10 The FunctionConfiguration element 13 VIOM scenarios 13.1 Shifting tasks from one server blade to another 13.2 Moving tasks using the server profile failover 13.3 Disaster Recovery 14 VIOM database 14.1 VIOM Backup Service 14.1.1 Configuring the job schedule on Windows 14.1.1.1 Syntax of Quartz cron expressions 14.1.2 Configuring the job schedule on Linux...
  • Page 10 ServerView Virtual-IO Manager...

  • Page 11: Introduction

    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: PRIMERGY blade server (BX600, BX400, BX900) In Japan, BX600 blade servers are not supported. PRIMERGY rack server (RX200 S7, RX300 S7, RX350 S7) PRIMERGY tower server (TX300 S7) When PRIMERGY rack servers are mentioned below, both, the PRIMERGY rack servers and the PRIMERGY tower servers, are...

  • Page 12: Target Groups And Objective Of This Manual

    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.
  • Page 13 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.

  • Page 14: Supported Hardware

    1 Introduction 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-...
  • Page 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.
  • Page 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: In fabric 1: 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...
  • Page 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,...
  • Page 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: In fabric 1: 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...
  • Page 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.
  • Page 20 1 Introduction PCI controller Scope of functions Emulex 10GbE OCe10102 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.

  • Page 21: Changes Since The Previous Edition

    VMware HA (see "High-Availability (HA) support" on page 48). ServerView Suite link collection Via the link collection, Fujitsu Technology Solutions provides you with numer- ous downloads and further information on the ServerView Suite and PRIM- ERGY servers. ServerView Virtual-IO Manager...
  • Page 22 ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge from the Fujitsu Tech- nology Solutions Web server. For PRIMERGY servers, links are offered on the following topics:...

  • Page 23: Documentation For The Serverview Suite

    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 doc- umentation for the ServerView Suite on the Fujitsu Technology Solutions manual server. You access the start page of the online documentation via the fol- lowing link: http://manuals.ts.fujitsu.com...

  • Page 24: Typographic Conventions

    1 Introduction 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 Indicates system output and system elements, e.g., file names and paths.

  • Page 25: Virtual-Io Manager - Introduction

    Virtual-IO Manager - Introduction This chapter provides a general introduction to the concept of the Virtual-IO Manager (VIOM). 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.
  • Page 26 2 Virtual-IO Manager - Introduction Figure 1: Overlapping areas of responsibility As the areas of responsibility overlap, this means that up to three admin- istrators 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.
  • Page 27 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: 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)

  • Page 28: Management With Viom - Procedure

    2 Virtual-IO Manager - Introduction Figure 2: Separate areas of responsibility Management with VIOM - Procedure You use the ServerView Virtual-IO Manager (VIOM) to manage the con- nection 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.
  • Page 29 2.3 Management with VIOM - Procedure For blade servers, management with VIOM essentially includes the following functions: Defining the network paths on the Intelligent Blade Panel (IBP module) Defining the I/O parameters (including virtual addresses) of a server blade Saving the I/O parameters in combination with the required network paths in server profiles 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...

  • Page 30: Defining Networks (Lan) (For Blade Servers Only)

    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.
  • Page 31 2.4 Defining networks (LAN) (for blade servers only) If a blade server chassis is managed by VIOM, manual con- figurations (not done by VIOM) of an IBP connection blade are not supported. Manual configuration of IBP connection blades might result in incorrect behavior of VIOM or get lost during configuration by VIOM.
  • Page 32 2 Virtual-IO Manager - Introduction In the case of IBP 30/12, the first 8 uplink ports are combined in one uplink set by default, and all 30 downlinks are connected with this standard uplink set. Using VIOM, you can change the standard configuration of an IBP module. You can combine several uplink ports into one uplink set as well as define several uplink sets for a LAN connection blade.
  • Page 33 2.4 Defining networks (LAN) (for blade servers only) Figure 4: Typical uplink sets The uplink ports can be assigned to an uplink set as active ports or as back- up ports. As a result, there are different ways of configuring an uplink set: "Port backup"...
  • Page 34 2 Virtual-IO Manager - Introduction aggregation group (LAG) is formed. By providing several parallel con- nections, you achieve higher level of availability and a greater con- nection capacity. In the figure above, this could be the uplink sets (1) and (2) if both uplink ports of these uplink sets are configured as active ports.
  • Page 35 2.4 Defining networks (LAN) (for blade servers only) A key attribute of a "single" network is that it is VLAN transparent. You can therefore channel several external networks with different VLAN tags (or also without VLAN tags) through a "single" network. Packets with or even without a VLAN tag, which arrive at the uplink ports from outside the network, are channeled to the related server blades with the corresponding network.
  • Page 36 2 Virtual-IO Manager - Introduction Figure 5: Networks with VLAN ID In the figure above, two shared uplink sets are configured on the IBP module. Two virtual networks VLAN10 and VLAN20 with the VLAN IDs 10 and 20 are assigned to the upper shared uplink set, and two virtual networks VLAN21 and VLAN30 with the VLAN IDs 20 and 30 are assigned to the lower shared uplink set.
  • Page 37 2.4 Defining networks (LAN) (for blade servers only) Packets that come from outside the network with no VLAN tag are also dropped. This behavior can be changed by configuring a virtual network as native VLAN (see "Virtual network with a VLAN ID as native VLAN" on page 37).
  • Page 38 2 Virtual-IO Manager - Introduction Figure 6: Networks with a VLAN ID and a native VLAN ID In the figure above, the VLAN ID 10 is defined as the native VLAN ID in the upper shared uplink set. As a result, the data packets of server blade 1 with the VLAN ID 10 (red) exit the uplink without a VLAN ID tag.
  • Page 39 2.4 Defining networks (LAN) (for blade servers only) Figure 7: Virtual networks with VLAN ID used in tagged mode Several VLAN networks in tagged mode can be used on the same IBP down- link port. They can also be combined with service networks. The mode in which a VLAN network is used is controlled by network def- initions in a server profile.
  • Page 40 2 Virtual-IO Manager - Introduction Dedicated service networks Figure 8: Dedicated service networks The dedicated service network is designed to separate LAN traffic of an iRMC from the operating system LAN traffic if the iRMC is not using a sep- arate management LAN but is configured to share its LAN traffic with an onboard LAN port of the server blade.
  • Page 41 2.4 Defining networks (LAN) (for blade servers only) The same VLAN tag must be specified when defining the dedicated service network that is to transport these packages. The behavior of a dedicated service network is such that it receives tagged packets from the server blade, but the tags are stripped when they leave the uplink port.
  • Page 42 2 Virtual-IO Manager - Introduction Service VLAN networks Figure 9: Service VLAN networks The Service VLAN networks are designed to separate LAN packages of mul- tiple virtual NICs defined in the operating system running on the server blade and route them to specific uplink (external) ports. To do this, the different vir- tual NICs in the operating system must be configured to send their packages with a VLAN tag that is identical to the Service VLAN ID of the Service VLAN network.

  • Page 43: Server Profiles

    2.5 Server profiles Note that Service VLAN networks may overlap on the downlink ports (with single networks, VLAN networks, dedicated service networks and other Serv- ice VLAN networks). The untagged packets received from the server blade or uplink port should obey the rule of the overlapping single network or VLAN network.

  • Page 44: Defining Server Profiles

    2 Virtual-IO Manager - Introduction a server profile failover, which searches for a suitable spare server blade that will assume the tasks of the failed server blade. To use server profiles, you must do the following in the Virtual-IO Manager: 1.

  • Page 45: Dedicated Lan Connections (Only For Blade Servers)

    2.5 Server profiles 2.5.3 Dedicated LAN connections (only for blade servers) You can assign each I/O port of a server blade to an explicit network in the server profile. As a server profile is not connected to any hardware, only the network name is recorded in it.
  • Page 46 2 Virtual-IO Manager - Introduction Blade Servers The virtualization I/O parameters of all the server blades of a chassis are stored in a specific table in the management blade (MMB) of this blade server. When a server blade powered on, checks are run in the boot phase to determine whether virtualization parameters are defined in the MMB table for this server blade slot.

  • Page 47: Server Profile Failover (For Blade Servers Only)

    2.6 Server profile failover (for blade servers only) If the virtualization of the I/O addresses for a slot is switched off, e. g. if the corresponding server profile is unassigned, the physical I/O addresses assigned by the manufacturer will automatically be reactivated in the next boot phase.

  • Page 48: High-Availability (Ha) Support

    2 Virtual-IO Manager - Introduction High-Availability (HA) support VIOM supports the following high-availability environment: Windows 2008 R2 Hyper-V cluster with ServerView Operations Man- ager and ServerView Virtual-IO Manager installed on a virtual machine with Windows Server operating system. VMware HA with ServerView Operations Manager and ServerView Vir- tual-IO Manager installed on a virtual machine with Windows Server oper- ating system.
  • Page 49 2.7 High-Availability (HA) support Operating system Admin server if HA Guest Hypervisor Windows Server 2008 R2 Foundation [*] [Hyper-V] Windows Server 2008 Standard (x86, x64) [*] [Hyper-V] (only x64) Windows Server 2008 Enterprise (x86, x64) [*] [Hyper-V] (only x64) Figure 10: Supported Hyper-V high-availability configurations [*] The Windows Server Core Installation option is not supported for admin server and guest OS on VM.
  • Page 50 2 Virtual-IO Manager - Introduction Figure 11: Failover action of the Hyper-V environment to the other cluster node In the failover clustering of the Hyper-V environment, ServerView supports the cold migration of virtual machines. To setup the Hyper-V cluster, proceed as follows: On the primary node: 1.
  • Page 51 2.7 High-Availability (HA) support 12. Install and configure ServerView Operations Manager and ServerView Virtual-IO Manager. On the secondary node: 1. Connect with shared storage. 2. Configure BIOS. 3. Install Hyper-V roles. 4. Install and configure EMC Solutions Enabler (if used). 5.
  • Page 52 2 Virtual-IO Manager - Introduction Figure 12: Architecture and typical configuration of VMware Infrastructure 3 ServerView Virtual-IO Manager...
  • Page 53 2.7 High-Availability (HA) support Figure 13: Host failover with VMware HA VMware HA links up multiple ESX/ESXi servers to form a cluster with shared resources. If one host fails, VMware HA reacts immediately by restarting any affected virtual machine on a different host. The cluster is created and managed via VirtualCenter.
  • Page 54 2 Virtual-IO Manager - Introduction The details of this configuration cannot be seen via the nor- mal graphical user interface of the service manager. To see the details, you must use the command line interface of the service manager. The command sc qfailure Server- displays the current con- ViewVirtualIOManagerService...
  • Page 55 2.7 High-Availability (HA) support ice has restarted, the configuration should be the same as it was just before the interrupted request. Some configuration actions of the Virtual-IO Manager user interface consist of several “independent” internal con- figuration requests. The Virtual-IO Manager can only undo the last internal configuration request.
  • Page 56 ServerView Virtual-IO Manager...

  • Page 57: Installation And Uninstallation

    Installation and uninstallation You can install the Virtual-IO Manager on a central management station (CMS) under Windows or Linux (see section "Installing the Virtual-IO Man- ager on a Windows-based CMS" on page 58 "Installing the Virtual-IO Manager on a Linux-based CMS" on page 73).

  • Page 58: Installing The Virtual-Io Manager On A Windows-Based Cms

    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. Installing the Virtual-IO Manager on a Windows-...

  • Page 59: Installing The Virtual-Io Manager Using A Graphical Interface

    3.2 Installing the Virtual-IO Manager on a Windows-based CMS 3.2.1 Installing the Virtual-IO Manager using a graphical inter- face Installation process 1. Insert the PRIMERGY ServerView Suite DVD 1 in the DVD-ROM drive. If the DVD does not start automatically, click the setup.exe file in the root directory of the DVD-ROM.
  • Page 60 3 Installation and uninstallation 7. Click Next. Accept the license agreement by selecting the corresponding option. ServerView Virtual-IO Manager...
  • Page 61 3.2 Installing the Virtual-IO Manager on a Windows-based CMS 8. Click Next. Enter your name and the name of your company/organization. You must also specify whether the settings should only apply for the current user or for any user working on this system. Select the corresponding option. ServerView Virtual-IO Manager...
  • Page 62 3 Installation and uninstallation 9. Click Next. If you select Select address ranges for IO Virtualization, you can specify address ranges for virtual addressing. If you want to use the automatic assignment of virtual address- es in server profiles, you must have already defined address ranges here.
  • Page 63 3.2 Installing the Virtual-IO Manager on a Windows-based CMS In this window, specify which address range the Virtual-IO Manager should use for virtual MAC addresses. The virtual MAC addresses are assigned automatically in a profile for the LAN ports during the server pro- file definition.
  • Page 64 3 Installation and uninstallation The validity of the MAC address input is not checked. Please confirm that your input address is valid before you click Next. If you have several installations of the Virtual-IO Manager in your LAN network, then you must ensure that the address ranges used do not overlap.
  • Page 65 3.2 Installing the Virtual-IO Manager on a Windows-based CMS In this window, specify which address range the Virtual-IO Manager should use for virtual WWN addresses. The virtual WWN addresses are assigned automatically for the Fibre Channel ports of an optional Fibre Channel mezzanine card during the server profile definition, whereby each port has two addresses (a WWPN - World Wide Port Name and a WWNN - World Wide Node Name).
  • Page 66 3 Installation and uninstallation 12. Click Next. Once you have made all your entries, click Next to start the installation. If you want to make further changes, click Back to return to the previous window. ServerView Virtual-IO Manager...
  • Page 67 3.2 Installing the Virtual-IO Manager on a Windows-based CMS 13. Click Next. The installation of the Virtual-IO Manager is started. The fol- lowing window is then displayed: 14. Click Next to launch the License Manager. ServerView Virtual-IO Manager...

  • Page 68: Installing The Virtual-Io Manager Using The Command Line Interface

    3 Installation and uninstallation 15. Click Register new license. Enter at least one valid license here so that you can use the Virtual-IO Manager functions. You can enter several licenses here. For more infor- mation on the License Manager, see section "License management"...
  • Page 69 3.2 Installing the Virtual-IO Manager on a Windows-based CMS end>"][DEBUG_MODE=true|false][VIOM_LICENSE_KEY = "<key_ value>"] Command line parameters for installation: DO_ADDRESS_RANGE_SELECTION Possible values are: true You want to set MAC_RANGE and WWN_RANGE (default value). false You do not want to set MAC_RANGE and WWN_RANGE. MAC_RANGE Possible values are: NONE...
  • Page 70 3 Installation and uninstallation MAC8 Range 00:19:99:3F:AD:61 - 00:19:99:3F:CC:A1 MAC12 Range 00:19:99:3E:D2:A1 - 00:19:99:3F:11:20 MAC34 Range 00:19:99:3F:11:21 - 00:19:99:3F:4F:A0 MAC56 Range 00:19:99:3F:4F:A1 - 00:19:99:3F:8E:20 MAC78 Range 00:19:99:3F:8E:21 - 00:19:99:3F:CC:A1 MAC_CUSTOM Custom range must be set with the MAC_START and MAC_END parameters.
  • Page 71 3.2 Installing the Virtual-IO Manager on a Windows-based CMS WWN3 Range 50:01:99:93:F1:12:0C:00 - 50:01:99:93:F3:06:09:FF WWN4 Range 50:01:99:93:F3:06:0A:00 - 50:01:99:93:F4:FA:07:FF WWN5 Range 50:01:99:93:F4:FA:08:00 - 50:01:99:93:F6:EE:05:FF WWN6 Range 50:01:99:93:F6:EE:06:00 - 50:01:99:93:F8:E2:03:FF WWN7 Range 50:01:99:93:F8:E2:04:00 - 50:01:99:93:FA:D6:02:FF WWN8 Range 50:01:99:93:FA:D6:02:00 - 50:01:99:93:FC:CA:00:00 WWN_CUSTOM Custom range must be set with the WWN_START and WWN_ END parameters.

  • Page 72: Updating The Virtual-Io Manager On A Windows-Based Cms

    3 Installation and uninstallation Example 1. SV_VIOM.exe /q MAC_RANGE=MAC_CUSTOM MAC_ START="11:22:33:44:55:66" MAC_ END="22:33:44:55:66:77" WWN_RANGE=WWN_CUSTOM WWN_ START="33:44:55:66:77:88:99:AA" WWN_ END="44:55:66:77:88:99:AA:BB" VIOM_LICENSE_KEY =abcdef 2. SV_VIOM.exe /q MAC_RANGE=MAC78 WWN_RANGE=WWN8 VIOM_ LICENSE_KEY=abcdef 3. SV_VIOM.exe /q DO_ADDRESS_RANGE_SELECTION=false VIOM_LICENSE_KEY=abcdef Updating the Virtual-IO Manager on a Windows- based CMS If you have already installed a previous version, an update installation runs automatically when you install the Virtual-IO Manager.

  • Page 73: Installing The Virtual-Io Manager On A Linux-Based Cms

    3.4 Installing the Virtual-IO Manager on a Linux-based CMS Once the update installation is complete, the final window of the installation wizard confirms that the update installation has been successful, just like in the full installation. Exit the installation wizard by clicking Finish. Installing the Virtual-IO Manager on a Linux-based The corresponding software is supplied with the PRIMERGY ServerView Suite DVD1.

  • Page 74: Installing The Virtual-Io Manager Using A Graphical Interface

    3 Installation and uninstallation 3.4.1 Installing the Virtual-IO Manager using a graphical inter- face If you want to use the graphical installation, an X Windows server should be installed on your desktop computer. Check the prerequisites for the VIOM installation (see section "Prerequisites for the VIOM installation"...
  • Page 75 3.4 Installing the Virtual-IO Manager on a Linux-based CMS 3. After these preparations, start the installation by launching the GUI: sh install_viom.sh The welcome window opens. ServerView Virtual-IO Manager...
  • Page 76 3 Installation and uninstallation 4. Click Next. Accept the license agreement by selecting the corresponding option. ServerView Virtual-IO Manager...
  • Page 77 3.4 Installing the Virtual-IO Manager on a Linux-based CMS 5. Click Next. Enter your name and the name of your company/organization. ServerView Virtual-IO Manager...
  • Page 78 3 Installation and uninstallation 6. Click Next. Enter the data on the ServerView database. The database user svuser has been created during ServerView installation and is used by VIOM as well. ServerView Virtual-IO Manager...
  • Page 79 3.4 Installing the Virtual-IO Manager on a Linux-based CMS 7. Click Next. If you select Select address ranges for IO Virtualization, you can specify address ranges for virtual addressing. If you want to use the automatic assignment of virtual address- es in server profiles, you must have already defined address ranges here.
  • Page 80 3 Installation and uninstallation If you selected Select address ranges for IO Virtualization, the fol- lowing window opens: In this window, specify which address range the Virtual-IO Manager should use for virtual MAC addresses. The virtual MAC addresses are assigned automatically in a profile for the LAN ports during the server pro- file definition.
  • Page 81 3.4 Installing the Virtual-IO Manager on a Linux-based CMS Validity of MAC address input is not checked. Please advance to the next screen after confirming your input address is valid. The validity of the MAC address input is not checked. Please confirm that your input address is valid before you click Next.
  • Page 82 3 Installation and uninstallation In this window, specify which address range the Virtual-IO Manager should use for virtual WWN addresses. The virtual WWN addresses are assigned automatically for the Fibre Channel ports of an optional Fibre Channel mezzanine card during the server profile definition, whereby each port has two addresses (a WWPN - World Wide Port Name and a WWNN - World Wide Node Name).
  • Page 83 3.4 Installing the Virtual-IO Manager on a Linux-based CMS 10. Click Next to launch the License Manager. 11. Click Register new license. Enter at least one valid license here so that you can use the Virtual-IO Manager functions. You can enter several licenses here. For more infor- mation on the License Manager, see section "License management"...

  • Page 84: Installing The Virtual-Io Manager Using The Command Line

    3 Installation and uninstallation 13. In the final screen you may view the release notes or the installation log. 14. Click Finish to end the installation. 3.4.2 Installing the Virtual-IO Manager using the command line The installation script install_viom.sh may also be used in a non-graphical installation, as explained here.
  • Page 85 3.4 Installing the Virtual-IO Manager on a Linux-based CMS [ --check-prerequisites][ --lang[ en|ja]][ -u|--upgrade] [ -q|--quiet][ -f|--force][ -i|--installdir][ -v|--verbose] [ -h|--help] Command line parameters for installation: --dbhost IP-address or hostname of the database server --dbport Port number of the database server --dbuser ServerView Operations Manager username in the database, by default svuser...
  • Page 86 3 Installation and uninstallation MAC4 Range 00:19:99:3F:30:61 - 00:19:99:3F:4F:A0 MAC5 Range 00:19:99:3F:4F:A1 - 00:19:99:3F:6E:E0 MAC6 Range 00:19:99:3F:6E:E1 - 00:19:99:3F:8E:20 MAC7 Range 00:19:99:3F:8E:21 - 00:19:99:3F:AD:60 MAC8 Range 00:19:99:3F:AD:61 - 00:19:99:3F:CC:A1 MAC12 Range 00:19:99:3E:D2:A1 - 00:19:99:3F:11:20 MAC34 Range 00:19:99:3F:11:21 - 00:19:99:3F:4F:A0 MAC56 Range 00:19:99:3F:4F:A1 - 00:19:99:3F:8E:20 MAC78 Range 00:19:99:3F:8E:21 - 00:19:99:3F:CC:A1...
  • Page 87 3.4 Installing the Virtual-IO Manager on a Linux-based CMS WWN2 Range 50:01:99:93:EF:1E:0E:00 - 50:01:99:93:F1:12:0B:FF WWN3 Range 50:01:99:93:F1:12:0C:00 - 50:01:99:93:F3:06:09:FF WWN4 Range 50:01:99:93:F3:06:0A:00 - 50:01:99:93:F4:FA:07:FF WWN5 Range 50:01:99:93:F4:FA:08:00 - 50:01:99:93:F6:EE:05:FF WWN6 Range 50:01:99:93:F6:EE:06:00 - 50:01:99:93:F8:E2:03:FF WWN7 Range 50:01:99:93:F8:E2:04:00 - 50:01:99:93:FA:D6:02:FF WWN8 Range 50:01:99:93:FA:D6:02:00 - 50:01:99:93:FC:CA:00:00 --no-gui Run installation in console mode, non-gui installation...

  • Page 88: Important Directories Of Virtual-Io Manager

    -–dbhost=127.0.0.1 -–dbport=9212 --mac-range=00:19:99:3E:D2:A1,00:19:99:3E:F1:E0 --wwn-range=50:01:99:93:ED:2A:10:00,50:01:99:93:EF:1E:0D:FF --license-key=AAA-BBBB-CCCC-DDDD-EEEE-FFFF-GGGG 3.4.3 Important directories of Virtual-IO Manager /opt/fujitsu/ServerViewSuite/plugins/viom In all Linux distributions, this is the installation directory where the binaries and libraries are stored. /var/fujitsu/ServerViewSuite/viom Directory in which variable information of VIOM is usually stored. ServerView Virtual-IO Manager...

  • Page 89: Collecting Diagnostic Information

    3.4.4 Collecting diagnostic information Sometimes it might be necessary to gather diagnostics information in order to send it to your Fujitsu support service. In the Manager subdirectory of the VIOM installation directory, you will find a dump.sh script that you may launch using the following command: cd /opt/fujitsu/ServerViewSuite/plugins/viom/Manager sh dump.sh...

  • Page 90: License Management

    3 Installation and uninstallation Once the update installation is complete, the final window of the installation wizard confirms that the update installation has been successful, just like in the full installation. Exit the installation wizard by clicking Finish. License management You need at least one license in order to use VIOM.
  • Page 91 On Linux, you can also launch the License Manager by starting the license.sh script which you find in the installation directory of VIOM. 1. On Windows: Choose Start – [All] Programs – Fujitsu – ServerView Suite – Virtual-IO Manager – License Management.
  • Page 92 To do this, launch the License Manager from the Windows Start Menu or with the license.sh script. 1. On Windows: Choose Start – [All] Programs – Fujitsu – ServerView Suite – Virtual-IO Manager – License Management. On Linux: Execute the command sh license.sh.
  • Page 93 On Linux you can also add a licence without graphical user inter- face: cd /opt/fujitsu/ServerViewSuite/plugins/viom/Manager java -jar ./VIOM-LICENSE-MANAGER.jar -remove <key> In addition to using the License Manager to manage licenses, you can dis- play the licenses assigned in the Virtual-IO Manager interface. To do this, you must click the Show Licenses button on the Virtual-IO Manager tab.

  • Page 94: Updating Serverview Operations Manager

    3 Installation and uninstallation 3. The information displayed includes the following: License code Validity period (only relevant for demo licenses) Max. number of assignments that are allowed with the licenses Number of currently assigned server profiles Number of server profiles that can still be assigned with the licenses For more information, see section "Displaying license information"...

  • Page 95: Upgrading Or Moving The Sql Server Database

    3.8 Upgrading or moving the SQL Server database When you need to uninstall existing ServerView Operations Man- ager and install the new one, you should uninstall existing Virtual-IO Manager: Save your configuration by using the Configuration Backup / Restore button on the Virtual-IO Manager tab Uninstall Virtual-IO Manager Uninstall ServerView Operations Manager Install ServerView Operations Manager...

  • Page 96: Uninstalling The Virtual-Io Manager

    Select Start – Control Panel – Programs and Features. To display the product versions, select Choose Details from the View menu. Select the Version option and click OK Under Fujitsu ServerView Virtual-IO Manager select the entry Remove. This uninstalls the complete package. 3.9.2 Uninstalling the Virtual-IO Manager on a Linux-based In order to uninstall VIOM use the unstall_viom.sh script which is found in...

  • Page 97: Configuration

    Configuration In the following sections, you find information on the required configurations on the managed server. Configurations on the managed BX600 Blade Server In section "Supported hardware configurations for the connection blades" on page 97, you can find out what combinations of I/O connection blades are supported by VIOM.

  • Page 98: Lan Hardware Configuration

    4 Configuration in fabric 2. FC switch blades do not support any dedicated network con- nections, but just the virtualization of the I/O parameters instead. If you only intend to work with virtual I/O parameters (Open Fabric mode) and not with dedicated network connections, you can also install non- VIOM-capable LAN modules in fabric 1 or fabric 2.

  • Page 99: Fibre Channel Hardware Configuration

    4.1 Configurations on the managed BX600 Blade Server You cannot mix LAN and IBP modules within a fabric. You can only assign profiles if no networks are defined for their ports. You can force the assignment of a profile with network def- initions by answering the subsequent query accordingly.
  • Page 100 4 Configuration find a detailed description on the interfaces in the ServerView Management Blade manual for BX600. Check the following settings in the management blade: The management blade must be installed with a specific firmware ver- sion. To find out which firmware version you need, see the release notes included.

  • Page 101: Configuring The I/O Connection Blades

    4.1 Configurations on the managed BX600 Blade Server To check the parameter setting in the Remote Manager of the man- agement blade, choose (1) Management Agent – (3) System Infor- mation – (11) Automatic Inventory Retrieval. To ensure that the blade server names in the ServerView server list are unique, you must assign a system name to the blade server chassis.
  • Page 102 4 Configuration Configuration using the Web interface You can configure the network parameters of an I/O connection blade using the Web interface of the management blade. You configure the network parameters of an I/O connection blade as follows: In DHCP Enable, select whether the connection blade should be given its IP address from an DHCP server or not.
  • Page 103 4.1 Configurations on the managed BX600 Blade Server Configuration using the Remote Manager You can also configure the network parameters of the I/O connection blades using the Remote Manager of the management blade. You configure the network parameters of an I/O connection blade as follows: In the Remote Manager, choose (1) Management Agent –...

  • Page 104: Connecting Ibp Modules

    4 Configuration For Fibre Channel switch modules (select FC Switch Blade), you must also specify access data for the parameters Set Login User- name and Set Login Password beforehand for the corresponding I/O connection blade in the management blade. 4.1.4 Connecting IBP modules The IBP modules must be connected to the management LAN via the first uplink port, in other words, the first external LAN port.

  • Page 105: Network - Overview

    4.1 Configurations on the managed BX600 Blade Server For the external switch to which an IBP module is connected for admin- istration, you have to ensure that the Spanning Tree Protocol (STP) is switched off for the port, which is connected to the first uplink port of the IBP module.

  • Page 106: Notes And Recommendations

    4 Configuration Figure 15: BX600: Network - Overview Port 0/11 for an IBP 10/6 or port 0/31 for an IBP 30/12 must be connected to the central management station. 4.1.4.2 Notes and recommendations We recommend that you do not use the first uplink port in the network def- initions.
  • Page 107 4.1 Configurations on the managed BX600 Blade Server Otherwise, you may have a situation whereby the corresponding IBP module can no longer be accessed from the central management station. If this happens, you must use the console redirection function of the management blade to configure the IBP module so that it can be accessed again via the management LAN of the management station.
  • Page 108 4 Configuration Example (Vty-0) #show uplink-set Uplink External External External Link Port IGMP Set Name ports active ports backup ports state Backup snoop LACP -------- -------------- ------------ ------------ ----- ------ ----- ---- default  - -           yes   no  yes  no 1_NET    0/11  0/11   yes   yes  yes...

  • Page 109: Configurations On The Managed Bx400 Blade Server

    4.2 Configurations on the managed BX400 Blade Server is assigned to this uplink set (because, for example, 1_NET is to be deleted), then you can restore the LAN connection to the IBP by adding the port to the standard uplink set. Enter the following commands: (Vty-0) #configure (Vty-0) (Config)#interface 0/11 (Vty-0) (Interface 0/11)#uplink-set default...

  • Page 110: Supported Hardware Configurations For The Connection Blades

    4 Configuration Define the connection of the IBP modules with the network, see section "Connecting IBP modules" on page 115 Add the blade server to the server list of the ServerView Operations Man- ager, see section "Adding a server to the ServerView server list" on page 4.2.1 Supported hardware configurations for the connection blades The following connection blades are supported in a BX400:...

  • Page 111: Lan Hardware Configuration

    4.2 Configurations on the managed BX400 Blade Server 4.2.1.1 LAN hardware configuration Using IBP Modules The following LAN connection blades in IBP mode can be used in fabric 1 (connection bay 1) and fabric 2 (connection bay 2) for the first mezzanine card: Bay 1 (Bay2) PY CB Eth Switch/IBP 1Gb 36/8+2 in IBP mode...

  • Page 112: Fibre Channel Hardware Configuration

    4 Configuration Therefore, if you do not want to use any routing, all combinations are possible even with non-VIOM-capable I/O connection blades. You must take the fol- lowing into account: You cannot mix LAN and IBP modules within fabric 3. You can only assign profiles if no networks are defined for their ports.

  • Page 113: Configuring The Bx400 Management Blade

    4.2 Configurations on the managed BX400 Blade Server 4.2.2 Configuring the BX400 management blade The blade server must be fitted with at least one S1 management blade. The BX400 management blade has a user friendly Web interface. You can find a detailed description on the interfaces in the ServerView Management Blade manual for BX400.

  • Page 114: Configuring The I/O Connection Blades

    4 Configuration To check the parameter setting in the Web interface open the Com- ponents section and select System – System Unit. The System Infor- mation section on the right contains the option Automatic Inventory Retrieval. If the value of it is not set to automatic, please set it to auto- matic and remove and insert all blades or perform a power-off and power-on of the blade server chassis.

  • Page 115: Connecting Ibp Modules

    4.2 Configurations on the managed BX400 Blade Server You configure the network parameters of an I/O connection blade as follows: Activate the Enable DHCP option under Management Port Settings if the connection blade is to receive its IP address from a DHCP server. If this option is not activated, you must specify the IP address, subnet mask, and the gateway address.

  • Page 116: Network - Overview

    4 Configuration Please note that before you activate blade server management, sev- eral uplink ports of a LAN connection blade in IBP mode form a stat- ic link aggregation group (LAG). If you activate blade server management using VIOM, all uplink ports of IBP modules will be deactivated and will only be reactivated when networks are defined in the IBP module.

  • Page 117: Switch Stacking Support

    4.2 Configurations on the managed BX400 Blade Server Figure 16: BX400: Network - Overview The I/O connection blades must be connected to the central management sta- tion via their management port. 4.2.5 Switch stacking support A stacking function is a group set of IBP(s) connected through Infiniband CX4 interface of the HiGig/HiGig+ ports.

  • Page 118: Configurations On The Managed Bx900 Blade Server

    4 Configuration monitoring, spanning tree protocol, VLAN, etc. The entire stack will appear as a single IBP. You find a detailed description about Switch Stacking in the manual "PRIM- ERGY BX900 Blade Server Systems- Ethernet Connection Blade Module- IBP version (User`s Guide)", chapter 6. VIOM supports uplink sets and networks on switch stacks.

  • Page 119: Supported Hardware Configurations For The Connection Blades

    4.3 Configurations on the managed BX900 Blade Server 4.3.1 Supported hardware configurations for the connection blades The following connection blades are supported in a BX900: The 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, and PY CB Eth Switch/IBP 10 Gb 18/8 as LAN connection blades.
  • Page 120 4 Configuration fabric 1, fabric 2, fabric 3, and fabric 4. Bay 1 (Bay 3) (Bay 5) (Bay 7) Bay 2 (Bay 4) (Bay 6) (Bay 8) PY CB Eth Switch/IBP 1Gb PY CB Eth Switch/IBP 1Gb 36/8+2 in 36/8+2 in IBP mode IBP mode (optional PY CB Eth Switch/IBP 1Gb PY CB Eth Switch/IBP 1Gb 36/12 in IBP...

  • Page 121: Fibre Channel Hardware Configuration

    4.3 Configurations on the managed BX900 Blade Server 4.3.1.2 Fibre Channel hardware configuration You can install the Fibre Channel switch blades in fabric 2 or fabric 3. They can be operated in two different modes: in normal switch mode in Access Gateway mode As a result, different combination options are possible.
  • Page 122 4 Configuration the version via the Web interface. If your firmware version is lower than the version required, you must update it to the required firmware version before you activate VIOM man- agement for the blade server. You can run an update via the Remote Manager of the management blade.

  • Page 123: Configuring The I/O Connection Blades

    4.3 Configurations on the managed BX900 Blade Server automatic and remove and insert all blades or perform a power-off and power-on of the blade server chassis. To ensure that the blade server names in the ServerView server list are unique, you must assign a system name to the blade server chassis. System names are assigned when the management blade is configured.
  • Page 124 4 Configuration You configure the network parameters of an I/O connection blade as follows: Activate the Enable DHCP option under Management Port Settings if the connection blade is to receive its IP address from a DHCP server. If this option is not activated, you must specify the IP address, subnet mask, and the gateway address.
  • Page 125 4.3 Configurations on the managed BX900 Blade Server You configure the network parameters of an I/O connection blade as follows: In the Remote Manager, choose (1) Management Agent – (6) Con- nection Blade. Select an I/O connection blade. Choose (2) Management Port Information. Make the relevant entries for the following parameters IP Mode Setting Value IP Address Setting Value...

  • Page 126: Connecting Ibp Modules

    4 Configuration 4.3.4 Connecting IBP modules The PY CB Eth Switch/IBP 1Gb 36/8+2, PY CB Eth Switch/IBP 1Gb 36/12 LAN, PY CB Eth Switch/IBP 1Gb 18/6, and PY CB Eth Switch/IBP 10 Gb 18/8 connection blades support two modes: "Normal" Layer 2 switch mode IBP mode For information on how to perform the switch, refer to the Switch Blade user manual.

  • Page 127: Switch Stacking Support

    4.3 Configurations on the managed BX900 Blade Server Figure 17: BX900: Network - Overview The I/O connection blades must be connected to the central management sta- tion via their management port. 4.3.5 Switch stacking support A stacking function is a group set of IBP(s) connected through Infiniband CX4 interface of the HiGig/HiGig+ ports.
  • Page 128 4 Configuration The stacking software configures each device tables and registers to support all switching functions, for example, switching, link aggregation, port mon- itoring, spanning tree protocol, VLAN, etc. The entire stack will appear as a single IBP. You find a detailed description about switch stacking in the "PRIMERGY BX900 Blade Server Systems- Ethernet Connection Blade Module- IBP ver- sion (User`s Guide)", chapter 6.

  • Page 129: Configurations On The Managed Primergy Rack Server

    4.4 Configurations on the managed PRIMERGY rack server It is also important that the members of a stack have a unique "user assigned" name in the MMB and that the stack member IDs of the par- ticipating connection blades are set to 1 before building the stack. The typical procedure for correct handling by VIOM is: Configure the stack by enabling the blade server internal stacking links and by connecting SB11 connection blades in different fabrics of the...
  • Page 130 4 Configuration The PRIMERGY rack server must be in the list of supported server types. The system BIOS and the iRMC firmware must fulfill VIOM require- ments. Details concerning the required BIOS version and iRMC firm- ware version might be found in the release notes. The iRMC of the PRIMERGY rack server must be reachable by LAN from the central management station where VIOM is installed.
  • Page 131 4.4 Configurations on the managed PRIMERGY rack server For further information on the server list, see the "ServerView Operations Manager" user guide. For correct operation in case of power loss (AC failure) for PRIMERGY rack servers, the iRMC of these servers must be able to send SNMP traps to the central ServerView management station with ServerView Operations Manager and VIOM running on it.

  • Page 132: Viom Server Profile Mapping

    4 Configuration Although VIOM does not guarantee that boot images created for one server type also work with another server type, VIOM also supports the assignment of server profiles for blades on PRIMERGY rack servers and vice versa. For further information, see the section "VIOM server profile mapping"...

  • Page 133: Pci Slot Location In Primergy Rack Servers

    4.6 PCI slot location in PRIMERGY rack servers Profiles with onboard CNA configuration cannot be assigned to servers which do not have an onboard CNA controller. Only I/O channels on master slots are mapped. So if a server profile for a BX960 S1 contains I/O channels for the slave slot they are ignored when the profile is assigned to a PRIMERGY rack server.
  • Page 134 4 Configuration RX300 S7 Figure 20: RX300 S7 connection panel on the rear 1 PCI slot 1 2 PCI slot 2 3 PCI slot 3 4 PCI slot 4 5 Shared LAN connector (LAN 1) 6 Standard LAN connector (LAN 2) 7 Management LAN connector (iRMC) 8 PCI slot 5 9 PCI slot 6...

  • Page 135: Adding A Server To The Serverview Server List

    4.7 Adding a server to the ServerView server list TX300 S7 and RX350 S7 Figure 21: TX300 S7 connection panel on the rear 1 PCI slot 9 2 PCI slot 8 3 PCI slot 7 4 PCI slot 6 5 PCI slot 5 6 PCI slot 4 7 PCI slot 3 8 PCI slot 2...
  • Page 136 4 Configuration You add the server to the ServerView server list using the server browser of the ServerView Operations Manager. To do this, choose Administration – ServerBrowser to open the Server Browser properties window. In this window, you have to specify the IP address and the system name of the management blade.

  • Page 137: Virtual-Io Manager User Interface

    Virtual-IO Manager user interface This chapter contains a general introduction to the Virtual-IO Manager (VIOM) describing: The structure of the Virtual-IO Manager start page The tabs, wizards, dialog boxes, buttons, and context menus that are available when working with VIOM The meaning of the various icons Virtual-IO Manager main window Once you have launched the Virtual-IO Manager, the following main window...
  • Page 138 5 Virtual-IO Manager user interface The window is divided into three areas: The ServerView Suite header The menu bar The work area with the tree structure on the left and tabs and views on the right The menu bar below the headline allows you to navigate between the various functions of the ServerView Operations Manager: ServerList Administration...

  • Page 139: Tree View

    5.2 Tree view Button Selection Display on the right on the left Server Five tabs are displayed in the area on the right (see List "Tabs" on page 142). All Server Only the Virtual-IO Manager tab is activated, which server group contains general information on VIOM.

  • Page 140: Tree Structure (Server List)

    5 Virtual-IO Manager user interface Server list (default) Profiles You switch between the two views by clicking the Server List and Profiles buttons. The Server List button is always above the tree structure. The Pro- files button is: Below the tree structure if the server list is displayed in this area Directly above the tree structure if the profiles are displayed in this area.

  • Page 141: Tree Structure (Profiles)

    5.2 Tree view When you select Server List (standard) on the left of the work area, the All Server server group is displayed according to the ServerView server list as well as the two VIOM-specific server groups VIOM Manageable and VIOM Managed.

  • Page 142: Tabs

    5 Virtual-IO Manager user interface Select a folder to show all contained profiles in the profiles table in the Server Profiles view in the area on the right of the ServerView Virtual- IO Manager window. By using the context menu in the area on the left, you can create a new profile.
  • Page 143 5.3 Tabs Figure 25: Virtual-IO Manager tab Show Licenses Displaying information on the licenses assigned (see section "Dis- playing license information" on page 275) Preferences Showing and modifying user preferences (see section "Preferences dialog box" on page 238) Configuration Backup / Restore Saving and restoring the blade server configuration and the server pro- files (see chapter "Saving and restoring"...

  • Page 144: Setup Tab

    5 Virtual-IO Manager user interface 5.3.2 Setup tab Using this tab, you specify whether an object is to be managed with VIOM or not. For a blade server or PRIMERGY rack server in the VIOM Manageable server group, you can activate the administration of VIOM using the Setup tab by adding this server to the VIOM Managed server group.
  • Page 145 5.3 Tabs responding blade server is shown. The table provides the following infor- mation: Column Significance Name Name of the server Status Manage status of the server Type Product name Firmware Firmware version Admin-IP IP address to administrate the server Causes Causes.
  • Page 146 5 Virtual-IO Manager user interface Fault State State Causes The (Causes or State Causes) state cause is not at all a fault. It is simply a state marker. The following values are defined: Cause Significance data base doesn't match Configuration of switch/server does not match hardware with database.
  • Page 147 5.3 Tabs passwords, which VIOM can use to access these servers. For details "Authentication dialog box (single blade server)" on page 231, "Authentication dialog box (PRIMERGY rack server)" on page 234, and "Authentication dialog box (PRIMERGY rack server and blade server)" on page 236.

  • Page 148: Ext. Lan Connections Tab

    5 Virtual-IO Manager user interface Restore IBP button to write the configuration saved internally in the VIOM database to the IBP module. Delete Configuration blade server only (switch or switch slot selected) If you select a slot for an I/O connection blade and the slot has the empty slot, wrong model, or stacking error state, you can use the Delete Configuration button to delete the configuration saved internally in the VIOM database.
  • Page 149 5.3 Tabs delete existing ones, as well as copy definitions from one connection blade to another. In the upper left part of the Graphic tab there is the rear view of the selected chassis. If an IBP is selected in this graphic, its uplink sets and networks are shown in the table on the right.

  • Page 150: Details Tab On Ext. Lan Connections Tab

    5 Virtual-IO Manager user interface Edit Click Edit to edit an existing uplink set. The Edit Uplink Set wizard is launched in which you can change the configuration. Delete Click Delete to delete networks or uplink sets. Details Click Details to get more information on the selected uplink set. The Uplink Set <name of uplink set>...

  • Page 151: Server Configuration Tab

    5.3 Tabs Figure 28: Details tab on the Ext. LAN Connections tab You can sort the table by the columns IBP, Uplink Set, and Network. Click New to define a new uplink set. The Create network wizard is launched. Edit Click Edit to edit an existing uplink set.
  • Page 152 5 Virtual-IO Manager user interface Figure 29: Server Configuration tab The table contains one entry for each slot of the blade servers selected in the server list and one entry for each PRIMERGY rack server selected in the server list. If only slots of one blade server or only one PRIMERGY rack server is selected in the table, more information about this server is shown above the table.
  • Page 153 5.3 Tabs Column Significance State Power state Spare Indicates whether or not the slot is a spare slot. You change the definition of a slot as a spare slot directly in the table (see section "Moving tasks using the server profile failover" on page 332).
  • Page 154 5 Virtual-IO Manager user interface Inventory Boot Click Inventory Boot to re-create the inventory table of the selected server blade or PRIMERGY rack server. During inventory boot the system BIOS assembles the inventory infor- mation of the server blade or PRIMERGY rack server hardware as need- ed by the Virtual-IO Manager and sends it to the management blade or to iRMC, where it is stored.
  • Page 155 5.3 Tabs Forced Power Off Switches off the server irrespective of the status of the operating system. Update States Click Update States to update the display in the State column for all server blades and PRIMERGY rack servers. Video Redirection Click Video Redirection.

  • Page 156: Chassis Configuration Tab

    5 Virtual-IO Manager user interface Boot Start the server blade(s) and PRIMERGY rack server(s). Shutdown Switch off the server blade(s) and PRIMERGY rack server(s). Failover Assign the server profile of a slot to a suitable spare slot in the event of a failure.
  • Page 157 5.3 Tabs Figure 30: Chassis Configuration tab The defined networks are listed in a rectangular box for each connection bay with an IBP connection blade. In the example above, connection bay 1 has the networks NET_1, NET_2, NET_3, NET_4, V_NET_1, …. Each network has a continuous gray row.

  • Page 158: Server Profiles View

    5 Virtual-IO Manager user interface The slots are displayed as smaller rectangles (Slot 1, Slot 2, Slot 3, …) below the rectangle that contains the list of networks. The name of an assigned server profile is entered in these rectangles. In the example above, profile2 is entered for Slot 1.
  • Page 159 5.3 Tabs Figure 31: Server Profiles view If in the Server Profiles view in the area on the left a folder is selected, all server profiles in this folder are shown in the table, otherwise the selected pro- file is shown. In the table there is one row per server profile showing the rel- evant information the profile: Column Significance...
  • Page 160 5 Virtual-IO Manager user interface Column Significance Network The name of the network defining the dedicated LAN con- nection Comment for A more detailed description of the profile (optional). Buttons The Create Server Profile wizard is started to define a new profile. Edit The Edit Server Profile wizard is started to modify the selected profile.

  • Page 161: Wizards

    5.4 Wizards Context menu Several actions for a server profile can be choosen from the context menu (click right mouse button): Edit Profile The Edit Server Profile wizard is started to modify the selected profile. You can only modify server profiles that are not assigned. If more than one server profile is selected or the selected server profile is assigned, this menu item is disabled.

  • Page 162: Create Network For Ibp Wizard (Only For Blade Servers)

    5 Virtual-IO Manager user interface Next Opens the next step in the wizard. Finish Executes the wizard with your settings. Cancel Cancels the wizard workflow without saving your changes. Help Launchs the context-sensitive online help. Virtual-IO Manager provides the following wizards: Create Network for IBP wizard Edit Uplink Set wizard Create Server Profile wizard...

  • Page 163: Select Type Step (Create Network Wizard)

    5.4 Wizards The Create Network for IBP wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left. You define network paths using the Ext. LAN Connections tab. This tab contains two other tabs (Graphic and Details).
  • Page 164 5 Virtual-IO Manager user interface Single network (selected by default) Creates an uplink set with a network. The uplink set and the network have the same name. VLAN / Service VLAN networks Creates an uplink set to which one network or even multiple networks with a VLAN ID can be assigned.
  • Page 165 5.4 Wizards Name of network Name for the internal network. 5.4.1.3 Edit Properties step (Create Network wizard - single /VLAN network) Edit Properties is the second step in the Create Network wizard. The selection you made at the first step of the Create Network wizard deter- mines which fields are displayed in the second step.
  • Page 166 5 Virtual-IO Manager user interface configured. By default, Activate Port Backup is selected. Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail. The linkdown event triggers a failover process on the server blade if con- figured accordingly.
  • Page 167 5.4 Wizards Auto negotiation The transmission speed is negotiated with the external switch. You can achieve a transmission speed of 1 Gbit/s with this value. 10 Mbit/s 10 Mbit/s full-duplex. 100 Mbit/s 100 Mbit/s full-duplex. By default, Auto negotiation is selected. IGMP Snooping If IGMP Snooping is activated, the connection blade controls whether requests to join a multicast group occur at the downlink ports of an uplink...
  • Page 168 5 Virtual-IO Manager user interface Assigns the port as a backup port to the uplink set. If the port is already assigned to another uplink set, this assignment is deleted. Remove Only available if the port is already assigned to the uplink. Removes the port assignment from the uplink set.
  • Page 169 5.4 Wizards Edit Properties step for dedicated service networks Figure 35: Create Network wizard (second step) Name of uplink set Name of uplink set. In the case of a single network, the network auto- matically has the same name. Activate Port Backup Switch to a backup port if an error occurs in the active port.
  • Page 170 5 Virtual-IO Manager user interface If you select Linkdown propagation, the ports of the related server blades receive a linkdown event if a problem occurs. If the LAN drivers in the operating system of the server blade are configured accordingly, this linkdown event then triggers a failover on the second LAN port.
  • Page 171 5.4 Wizards 100 Mbit/s 100 Mbit/s full-duplex. By default, Auto negotiation is selected. Service VLAN id A Service VLAN ID must be specified. IGMP Snooping If IGMP Snooping is activated, the connection blade controls whether requests to join a multicast group occur at the downlink ports of an uplink set.
  • Page 172 5 Virtual-IO Manager user interface Active Only available if the port is configured as Backup. The corresponding port is configured as active and no longer as backup. Backup Only available if the port is configured as Active. The corresponding port is configured as a backup port and no longer as active port.
  • Page 173 5.4 Wizards Figure 36: Create Network wizard (DCB Properties) Enable DCB Enables the DCB feature of the connection blade. The DCB (Data Center Bridging) settings here are specific configuration settings in a DCB-enabled switching device. This option should be enabled if this uplink set should be used for FCoE (Fibre Channel over Ethernet).
  • Page 174 5 Virtual-IO Manager user interface This is the bandwidth reserved for the FCoE function. The FCoE function might share the complete bandwidth of 10 Gb with other functions. A value of 60, for exam- ple, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages.
  • Page 175 5.4 Wizards VLAN-Id The unique VLAN number of the network specified above. The VLAN ID must be assigned uniquely within a shared uplink set. Native VLAN Defines a network as native VLAN. All packages that do not contain a VLAN ID will be allowed through this connection. Service VLAN Defines a network as service VLAN.

  • Page 176: Edit Uplink Set Wizard

    5 Virtual-IO Manager user interface in the same chassis that use the same network cannot communicate with each other, but only with an external device though the uplinks. The column Isolate mode is not shown if the connection blade does not support isolate mode.
  • Page 177 5.4 Wizards Edit Properties step for single networks/VLAN networks Figure 38: Edit Uplink Set wizard (first step) You can modify following parameters in the first step of the wizard: Activate Port Backup Switch to a backup port if an error occurs in the active port. The port backup function is only available if at least one backup port is con- figured.
  • Page 178 5 Virtual-IO Manager user interface linkdown event is then triggered if all ports configured as active and all ports configured as backup ports of an uplink set fail. This allows the LAN connection to remain intact. In order for the failover process in the server blade to work from LAN port 1 to LAN port 2, a LAN team must have been configured on the server blade and the network on the second IBP module must have been con- figured accordingly.
  • Page 179 5.4 Wizards IGMP Snooping If IGMP Snooping is activated, the connection blade controls whether requests to join a multicast group occur at the downlink ports of an uplink set. If necessary, the corresponding downlink ports may be added to the forwarding table of this multicast group or removed again.
  • Page 180 5 Virtual-IO Manager user interface The corresponding port is configured as a backup port and no longer as active port. Ports configured as active or backup ports are indicated by different col- ors in the display (light red/light green or dark red/dark green). The name of the uplink set is assigned to configured ports, which you can rec- ognize by this.
  • Page 181 5.4 Wizards Activate Port Backup Switch to a backup port if an error occurs in the active port. The port backup function is only available if at least one backup port is con- figured. Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail. The linkdown event triggers a failover process on the server blade if con- figured accordingly.
  • Page 182 5 Virtual-IO Manager user interface value if a problem occurs using the drop-down menu according to the set- tings on the external switch. The following values are available: Auto negotiation The transmission speed is negotiated with the external switch. You can achieve a transmission speed of 1 Gbit/s with this value.

  • Page 183: Dcb Properties (Edit Uplink Set Wizard - Single/Vlan Network)

    5.4 Wizards Assigns the port as a backup port to the uplink set. If the port is already assigned to another uplink set, this assignment is deleted. Remove Only available if the port is already assigned to the uplink. Removes the port assignment from the uplink set. Active Only available if the port is configured as Backup.
  • Page 184 5 Virtual-IO Manager user interface Figure 40: DCB Properties Enable DCB Enables the DCB feature of the connection blade. The DCB (Data Center Bridging) settings here are specific configuration settings in a DCB-enabled switching device. This option should be enabled if this uplink set should be used for FCoE (Fibre Channel over Ethernet).
  • Page 185 5.4 Wizards internally adjusted accordingly. This is the bandwidth reserved for the FCoE function. The FCoE function might share the complete bandwidth of 10 Gb with other functions. A value of 60, for exam- ple, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages.
  • Page 186 5 Virtual-IO Manager user interface Add another network Network Name meaningful name of the network. VLAN Id The unique VLAN number of the network specified above. The VLAN ID must be assigned uniquely within a shared uplink set. Native VLAN Defines a network as native VLAN.

  • Page 187: Name Step (Create Server Profile Wizard)

    5.4 Wizards Service VLAN Select the checkbox in the corresponding row under Service VLAN in the table to define a network as a service VLAN. Isolate mode Select the checkbox in the corresponding row under Isolate mode to set the isolate mode for this network. With isolate mode activated, servers in the same chassis that use the same network cannot communicate with each other, but only with an external device though the uplinks.
  • Page 188 5 Virtual-IO Manager user interface Figure 42: Name step Name of the profile Name of the server profile. If a profile already exists with this name or the name is invalid, the name is marked in red. Select type of profile The target type to which this profile should be assignable: Server Blade This profile can be assigned to slots of a blade server.

  • Page 189: Configure Cards Step (Create Server Profile Wizard)

    5.4 Wizards The number and type of LAN ports under Onboard IO channels are adjusted automatically according to the server model you select. The number of LAN ports and mezzanine/PCI cards cannot exceed the max- imum possible value for the selected server model. Comment Comments on a more detailed description of the profile (optional) 5.4.3.2 Configure Cards step (Create Server Profile wizard)

  • Page 190: Io-Channels Step (Create Server Profile Wizard)

    5 Virtual-IO Manager user interface Depending on the selected profile and server type, there are a number of boxes, each representing a slot for a mezzanine or PCI card. If you want to configure a mezzanine or PCI card with this server profile, you must click the Add button in the corresponding slot to add a card.
  • Page 191 5.4 Wizards Figure 44: IO-Channels step Local boot settings used This message shows that the local boot settings are being used in the server profile. This message is not displayed if a boot device is used in the server profile. Use virtual addresses Uses virtual MAC addresses and WWN addresses with this profile.
  • Page 192 5 Virtual-IO Manager user interface Fabric 3 All paths are routed to fabric 3. Fabric 4 All paths are routed to fabric 4. Fabric 3 & 4 LAN1 is routed to fabric 3 and LAN2 to fabric 4. For more information on SMUX settings, see the documentation "PRIM- ERGY BX900 Blade Server Systems - ServerView Management Blade S1".
  • Page 193 5.4 Wizards Column Significance Network Name of the network. You can specify a network for each LAN or CNA port, but not for profiles of type Rack Server. If you want to use the profile on blade servers with IBP modules, you can specify a network for each LAN or CNA port.

  • Page 194: Boot Parameter Step (Create Server Profile Wizard)

    5 Virtual-IO Manager user interface Column Significance Service Names of the service networks. You can specify service net- works for each LAN or CNA port, but not for profiles of type Rack Server. If you specify more than one service network for a port, the names must be separated by commas.
  • Page 195 5.4 Wizards Boot Parameters for an iSCSI boot (LAN ports or iSCSI function on CNA mezzanine card) Figure 45: Boot Parameter step (iSCSI boot) Initiator Parameters Address Origin DHCP The system tries (in the case of an iSCSI boot) to obtain the client IP address, subnet mask, and gateway IP address from a DHCP server.
  • Page 196 5 Virtual-IO Manager user interface VLAN Id VLAN ID that is used by the HBA to send its requests.(optional) Should be used only for CNA-iSCSI-functions. IPv4 address Static client IP address to be used for this port. The port will use this IP address for the entire iSCSI session.
  • Page 197 5.4 Wizards Target Name IQN name of the iSCSI target. You can enter a name in this field if Address Origin: static is selected. IPv4 address IP address of the iSCSI target. You can enter an IP address in this field if Address Origin: static is selected.
  • Page 198 5 Virtual-IO Manager user interface Chap Secret CHAP password. This password must be identical to the password con- figured on the iSCSI target. It must contain 12 to 16 characters. This password must differ from the password in the Mutual Chap Secret field.
  • Page 199 5.4 Wizards Port Name WWPN (worldwide port name) of the port for the boot device. LUN (logical unit number) address of the boot device. The default value for the field is 0. 2nd Target In 2nd Target, you configure the backup boot device (optional). Port Name WWPN (worldwide port name) of the port for the backup boot device.

  • Page 200: Cna Parameter Step (Create Server Profile Wizard)

    5 Virtual-IO Manager user interface 8 Gbit/s 8 Gbit/s full-duplex Topology Type of port connection with the external SAN network. Possible values: auto (loop first) auto (Point-to-Point first) Point-to-Point Arbitrated loop By default, auto (Point-to-Point first) is set. 5.4.3.5 CNA Parameter step (Create Server Profile wizard) CNA Parameter is the next step in the Create Server Profile wizard.
  • Page 201 5.4 Wizards Figure 47: CNA Parameter step Bandwidth The share of the bandwidth in percent that is assigned to this function. If the sum of all bandwidths of one IO-channel is not 100, the values are internally adjusted accordingly. This is the bandwidth reserved for the FCoE function. The FCoE function might share the complete bandwidth of 10 Gb with other functions.

  • Page 202: 5.4.3.6 Virtual Addresses Step (Create Server Profile Wizard

    5 Virtual-IO Manager user interface Enable DCB Settings This option is available only for FCoE and iSCSI functions. It enables the DCB (Data Center Bridging) feature of the connection blade. The DCB settings here are specific configuration settings in a DCB-enabled switching device.
  • Page 203 5.4 Wizards Figure 48: Virtual Addresses step Virtual MAC, Virtual WWNN, Virtual WWPN, Virtual E-MAC The virtual address. Virtual MAC and E-MAC (Enode MAC) addresses must have the structure xx:xx:xx:xx:xx:xx while virtual WWN address- es must have the structure xx:xx:xx:xx:xx:xx:xx:xx. Each x represents a hexadecimal character (0-9, a-f, A-F).

  • Page 204: Confirm Step (Create Server Profile Wizard)

    5 Virtual-IO Manager user interface Next to each virtual address, you see the status of the address. The status can have the following values: Status Significance Allocate (OK) The address is automatically assigned. OK (OK) The address is valid and has not been assigned yet.

  • Page 205: Edit Server Profile Wizard

    5.4 Wizards Figure 49: Confirm step 5.4.4 Edit Server Profile wizard You use this wizard to modify a server profile. The Edit Server Profile wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree struc- ture on the left.
  • Page 206 5 Virtual-IO Manager user interface Figure 50: Name step Name of the profile Name of the server profile. If a profile already exists with this name or the name is invalid, the name is marked in red. Select type of profile The target type to which this profile should be assignable: Server Blade This profile can be assigned to slots of a blade server.

  • Page 207: Configure Cards Step (Edit Server Profile Wizard)

    5.4 Wizards The number and type of LAN ports under Onboard IO channels are adjusted automatically according to the server model you select. The number of LAN ports and mezzanine/PCI cards cannot exceed the max- imum possible value for the selected server model. Comment Comments on a more detailed description of the profile (optional) 5.4.4.2 Configure Cards step (Edit Server Profile wizard)

  • Page 208: Io-Channels Step (Edit Server Profile Wizard)

    5 Virtual-IO Manager user interface Depending on the selected profile and server type, there are a number of boxes, each representing a slot for a mezzanine or PCI card. If you want to configure a mezzanine or PCI card with this server profile, you must click the Add button in the corresponding slot to add a card.
  • Page 209 5.4 Wizards Figure 52: IO-Channels step Local boot settings used This message shows that the local boot settings are being used in the server profile. This message is not displayed if a boot device is used in the server profile. Use virtual addresses Uses virtual MAC addresses and WWN addresses with this profile.
  • Page 210 5 Virtual-IO Manager user interface Fabric 3 All paths are routed to fabric 3. Fabric 4 All paths are routed to fabric 4. Fabric 3 & 4 LAN1 is routed to fabric 3 and LAN2 to fabric 4. For more information on SMUX settings, see the documentation "PRIM- ERGY BX900 Blade Server Systems - ServerView Management Blade S1".
  • Page 211 5.4 Wizards Column Significance Network Name of the network. You can specify a network for each LAN or CNA port, but not for profiles of type Rack Server. If you want to use the profile on blade servers with IBP modules, you can specify a network for each LAN or CNA port.

  • Page 212: Boot Parameter Step (Edit Server Profile Wizard)

    5 Virtual-IO Manager user interface Column Significance Service Names of the service networks. You can specify service net- works for each LAN or CNA port, but not for profiles of type Rack Server. If you specify more than one service network for a port, the names must be separated by commas.
  • Page 213 5.4 Wizards Boot Parameters for an iSCSI boot (LAN ports) or iSCSI function on CNA mezzanine card Figure 53: Boot Parameter step (iSCSI boot) Initiator Parameters Address Origin DHCP The system tries (in the case of an iSCSI boot) to obtain the client IP address, subnet mask, and gateway IP address from a DHCP server.
  • Page 214 5 Virtual-IO Manager user interface IPv4 address Static client IP address to be used for this port. The port will use this IP address for the entire iSCSI session. You can enter an IP address in this field if Address Origin: static is selected. Subnet Mask IP subnet mask.
  • Page 215 5.4 Wizards IPv4 address IP address of the iSCSI target. You can enter an IP address in this field if Address Origin: static is selected. Port TCP port number (default: 3260 for iSCSI). You can enter a port number in this field if Address Origin: static is selected. (optional) LUN ID of the boot disk on the SCSI target.
  • Page 216 5 Virtual-IO Manager user interface This password must differ from the password in the Mutual Chap Secret field. Mutual Chap Secret The mutual CHAP password. This password must be identical to the password configured on the iSCSI target. It must contain 12 to 16 char- acters.
  • Page 217 5.4 Wizards LUN (logical unit number) address of the boot device. The default value for the field is 0. 2nd Target In 2nd Target, you configure the backup boot device. Port Name WWPN (worldwide port name) of the port for the backup boot device. LUN (logical unit number) address of the backup boot device.

  • Page 218: Cna Parameter Step (Edit Server Profile Wizard)

    5 Virtual-IO Manager user interface Topology Type of port connection with the external SAN network. Possible values: auto (loop first) auto (Point-to-Point first) Point-to-Point Arbitrated loop By default, auto (Point-to-Point first) is set. 5.4.4.5 CNA Parameter step (Edit Server Profile wizard) CNA Parameter is the next step in the Edit Server Profile wizard.
  • Page 219 5.4 Wizards Figure 55: CNA Parameter step Enable DCB Settings This option is available only for FCoE and iSCSI functions. It enables the DCB (Data Center Bridging) feature of the connection blade. The DCB settings here are specific configuration settings in a DCB-enabled switching device.

  • Page 220: Virtual Addresses Step (Edit Server Profile Wizard)

    5 Virtual-IO Manager user interface Bandwidth The share of the bandwidth in percent that is assigned to this function. If the sum of all bandwidths of one IO-channel is not 100, the values are internally adjusted accordingly. This is the bandwidth reserved for the FCoE function. The FCoE function might share the complete bandwidth of 10 Gb with other functions.
  • Page 221 5.4 Wizards Virtual MAC, Virtual WWNN, Virtual WWPN, Virtual E-MAC The virtual address. Virtual MAC and E-MAC (Enode MAC) addresses must have the structure xx:xx:xx:xx:xx:xx while virtual WWN address- es must have the structure xx:xx:xx:xx:xx:xx:xx:xx. Each x represents a hexadecimal character (0-9, a-f, A-F). The Enode MAC address is the MAC address of an FCoE func- tion.

  • Page 222: Confirm Step (Edit Server Profile Wizard)

    5 Virtual-IO Manager user interface Status Significance Out of range The address is outside the specified address range. (error) Syntax error The address is syntactically incorrect. (error) Already used The address is already in use (error) Check Addresses A check is performed to determine whether the addresses are currently in use in other profiles and whether they are within the range specified.

  • Page 223: Select Action Step (Configuration Backup/Restore Wiz- Ard)

    5.4 Wizards 5.4.5 Save Configuration wizard You use the Save Configuration wizard to save and to restore backup files as well as to delete them on the management station. The Save Configuration wizard comprises several dialog boxes to guide you through the individual steps. All required steps are displayed in the tree structure on the left.

  • Page 224: Select File Step (Save Configuration Wizard)

    5 Virtual-IO Manager user interface Restore Configuration Select Restore Configuration to restore a configuration from a file. Delete Configuration Select Delete Configuration to delete backup files you no longer need on the central management station. You delete backup files saved locally using the means available on the operating system of the local computer 5.4.5.2 Select File step (Save Configuration Wizard) Select File is the second step in the Save Configuration wizard.

  • Page 225: Select File Step (Restore Configuration Wizard)

    5.4 Wizards Column Significance Date Date and time when the backup file is created. You can sort the list of existing backup files according to file name or date by clicking the table headline accordingly. File Name for the backup file. You can also create a file in subdirectories by specifying the entire path name (e.g.
  • Page 226 5 Virtual-IO Manager user interface Figure 60: Select File step (Restore Configuration wizard) Restore file from Management Station Backup file from the management station. Column Significance Name Name of an existing backup file. Date Date and time when the backup file is created. You can sort the list of existing backup files according to file name or date by clicking the table headline accordingly.

  • Page 227: Select File Step (Delete Backup Files Wizard)

    5.4 Wizards Browse Opens the file selection dialog box in which you can select the rel- evant backup file. 5.4.5.4 Select File step (Delete Backup Files wizard) Select File is the second step in the Delete Backup Files wizard. In this step you select the backup files you want to delete on the management sta- tion.

  • Page 228: Select Data Step (Save Configuration Wizard)

    5 Virtual-IO Manager user interface Clear Selection Deselects all the backup files. 5.4.5.5 Select Data step (Save Configuration wizard) Select Data is the third step in the Save Configuration wizard. In this step you select the servers whose configuration you wish to save. Figure 62: Select Data step (Save Configuration wizard) Select servers to save Servers whose configuration you wish to save.

  • Page 229: Select Data Step (Restore Configuration Wizard)

    5.4 Wizards 5.4.5.6 Select Data step (Restore Configuration wizard) Select Data is the third step in the Restore Configuration wizard. In this step you define the data you wish to restore. Figure 63: Select Data step (Restore Configuration wizard) Select the configuration to restore In the Configuration column you select the configuration(s) to restore.

  • Page 230: Select Data Step (Delete Backup Files Wizard)

    5 Virtual-IO Manager user interface The Restore Options dialog box opens automatically in which you specify additional parameters (see section "Restore Options dialog box (server profiles)" on page 243 <server> Restore the configuration saved for the selected server. For blade servers, the Restore Options dialog box opens auto- matically in which you specify additional parameters (see section "Restore Options dialog box (servers)"...

  • Page 231: Dialog Boxes

    5.5 Dialog boxes In this step you will see the names of the files you wish to delete. The files are deleted after you have clicked Finish. Dialog boxes Virtual-IO Manager provides the following dialog boxes: Authentication dialog box Licenses Information dialog box Restore Options dialog box Select Profile dialog box 5.5.1 Authentication dialog box (single blade server)
  • Page 232 5 Virtual-IO Manager user interface Figure 65: VIOM Manager authentication (single blade server) In this dialog box, you enter the user names/passwords for the management blade and for the IBP modules, which VIOM can then use to access these modules. For the MMB and each IBP, you must specify the user name and password with which VIOM can access the component.
  • Page 233 5.5 Dialog boxes For security reasons you should change the default user name and password combination. You can have the same user name and password for all com- ponents or different ones for each. You must specify this accordingly in this dialog box.

  • Page 234: Authentication Dialog Box (Primergy Rack Server)

    5 Virtual-IO Manager user interface For a standard configuration, these values should not be changed. 5.5.2 Authentication dialog box (PRIMERGY rack server) The Authentication dialog box is displayed when you click the Manage or Authentication button on the Setup tab. This dialog box varies depending on what you have selected in the table on the Setup tab.
  • Page 235 5.5 Dialog boxes ponents or different ones for each. You must specify this accordingly in this dialog box. With the Configure protocols button you can expand the dialog box, so that you can also specifiy the port to be used by VIOM to access the com- ponents.

  • Page 236: Authentication Dialog Box (Primergy Rack Server And Blade Server)

    5 Virtual-IO Manager user interface Use default port Uses the default port. The default port is dependent on the protocol and the relevant module. For a PRIMERGY rack server: Port 623 The Port input field is inactive if this option is checked. For a standard configuration, these values should not be changed.

  • Page 237: Licenses Information Dialog Box

    5.5 Dialog boxes User name A valid user name with access rights to the MMBs, IBPs, and iRMCs Password Password of the user ID 5.5.4 Licenses Information dialog box The Licenses Information dialog box displayes a table showing the relevant information of the license.

  • Page 238: Preferences Dialog Box

    5 Virtual-IO Manager user interface Assign Limit Maximum number of server profiles that can be assigned with the licenses Used Assigns Number of server profiles currently being assigned Assign Credit Number of server profiles that can still be assigned with the licenses Closes the Licenses Information dialog box.
  • Page 239 5.5 Dialog boxes Display tab Figure 69: Display tab (Preferences dialog box) The Display tab allows you to reset the display settings. If you change some display properties (e.g. the width of columns in a table), these are stored user-specific. These settings can be reset to factory defaults by selecting the Reset display settings check box.
  • Page 240 5 Virtual-IO Manager user interface Trace tab Figure 70: Trace tab (Preferences dialog box) On the Trace tab, parameters for tracing the VIOM-GUI can be set. This is useful to create diagnostic data (see section "Creating diagnostic data" on page 356).

  • Page 241: Restore Options Dialog Box (Servers)

    5.5 Dialog boxes If the maximum file size is reached, the trace file will be renamed and a new one will be used. The renamed trace files will have a number append- ed, up to a maximum of ten possible back-up trace files. Therefore the trace files can use up to ten times the specified value of disk space.
  • Page 242 5 Virtual-IO Manager user interface For PRIMERGY rack servers, the Restore Options dialog box can also be opened by clicking the Options... button. But the three options in the Restore Options dialog box are disabled. In addition, Reassign Profiles is selected. So in this case, you cannot change any of the options.

  • Page 243: Restore Options Dialog Box (Server Profiles)

    5.5 Dialog boxes dialog box where you can select the destination blade server. Applies your selection and closes the dialog box. Cancel Closes the dialog box without applying your selection. 5.5.7 Restore Options dialog box (server profiles) The Restore Options dialog box opens when you select Profiles in the third step of the Restore Configuration wizard.
  • Page 244 5 Virtual-IO Manager user interface Restore only reassigned profiles Specifies that only the profiles that are reassigned to the selected blade servers will be restored (see section "Restoring blade server con- figurations" on page 306). If you do not select this option, all the profiles saved in the backup file will be restored.

  • Page 245: Select Profile Dialog Box

    5.5 Dialog boxes This will be necessary if address ranges have been changed since the backup configuration has been saved or if it is created on another man- agement station. This option cannot be selected together with Keep existing profiles. Applies your selection and closes the dialog box.
  • Page 246 5 Virtual-IO Manager user interface Figure 73: Select Profile dialog box Power On after Assign The server is started once the server profile has been assigned. To prevent further questions when warnings occur, you can state here that you want to assign the server profile even if a warning is issued: Ignore ext.

  • Page 247: Context Menus

    5.6 Context menus Ignore Spare No warning during assignment to a spare slot Skip downlink checks No warning, even though ports are configured in the server profile for which there are no downlinks in the IBP. If a network is defined for such a LAN port, the server profile cannot be assigned in any case.

  • Page 248: Context Menus In The Server Profiles View

    5 Virtual-IO Manager user interface New Uplink Set Define a new uplink set Edit Uplink Set Edit an uplink set Delete Delete network(s) or uplink set(s) The context menu of an uplink port can contain the following menu items depending on how it is configured: Assign port to an uplink set Add as Backup Assign port to an uplink set as a backup port...

  • Page 249: Context Menu On The Server Configuration Tab

    5.6 Context menus New Profile Create a server profile The context menu of a profile contains the following menu items: Edit Profile Edit selected server profile Show Profile Details View definition of a selected server profile Delete Profile Delete selected server profile Copy Profile Create a copy of the selected server profile 5.6.3 Context menu on the Server Configuration tab...
  • Page 250 5 Virtual-IO Manager user interface Inventory Boot Re-create the inventory table of the server. During inventory boot the system BIOS assembles the inventory infor- mation of the server blade or PRIMERGY rack server hardware as need- ed by the Virtual-IO Manager and sends it to the management blade or to iRMC, where it is stored.

  • Page 251: General Buttons

    5.7 General buttons General buttons This section describes the general buttons that you will come across in the Virtual-IO Manager. 5.7.1 Buttons in the area on the left Server List button Click Server List in the left area of the Virtual-IO Manager to switch to the file tree view according to the ServerView server list.

  • Page 252: Icons

    5 Virtual-IO Manager user interface Help button Click Help to launch the context-sensitive online help. Next button Click Next to go to the next step of the relevant wizard. OK button Click OK to confirm your entries. The dialog box closes. Icons This section contains a list of the VIOM-specific icons and their meaning.

  • Page 253: Using The Virtual-Io Manager

    Administration – Virtual-IO Manager. On Windows, you can also launch VIOM from the Windows Start Menu. 1. Choose Start – [ALL] Programs – Fujitsu – ServerView Suite – Vir- tual-IO Manager – Virtual-IO Manager. In both cases, the login page of the Fujitsu ServerView Suite Central Authen- tication Service is displayed.

  • Page 254: Logging The Actions Using Viom

    6 Using the Virtual-IO Manager Logging the actions using VIOM 6.3.1 Logging the actions on Windows The Virtual-IO Manager logs all actions in the Windows Event Log, including logins to the Virtual-IO Manager and all changes to the specific blade server configuration on the Virtual-IO Manager.
  • Page 255 6.3 Logging the actions using VIOM Figure 74: VIOM-specific log file ServerView Virtual-IO Manager...

  • Page 256: Logging The Actions On Linux

    6 Using the Virtual-IO Manager 6.3.2 Logging the actions on Linux On Linux the actions of VIOM are logged using the Syslog mechanism. All informational messages are logged using the Syslog facility user. For exam- ple on SLES 11 you will find the VIOM messages in the file /var/log/user_ messages.

  • Page 257: Managing Servers With Viom

    Managing servers with VIOM When you install a new server that can be managed using VIOM and add it to the ServerView server list, then this server is automatically added to the VIOM-specific server group VIOM Manageable. In order to manage the server with VIOM, you first have to add it to the group of servers managed with VIOM (VIOM Managed).
  • Page 258 7 Managing servers with VIOM To manage a blade server, you have to access the management blade of the BX600/BX400/BX900 chassis and the IBP modules in the chassis. To access the management module (MMB) and the IBP modules with VIOM, you have to specify data for authentication during activation, e.

  • Page 259: Changing Access Rights And Ports

    7.2 Changing access rights and ports password for the management blade or the first PRIMERGY rack server and click Use for all components. These settings are then applied to all I/O connection blades or all PRIMERGY rack servers. You should change the default user name and password combination for security reasons.
  • Page 260 7 Managing servers with VIOM 2. Click Authentication on the Setup tab. The Authentication dialog box opens. See "Authentication dialog box (single blade server)" on page 231, "Authentication dialog box (PRIMERGY rack server)" on page 234. 3. Enter the user names and passwords for the individual components (for the management blade and for all I/O connection blades or for the PRIM- ERGY rack servers), which VIOM can use to access these com- ponents.

  • Page 261: Deactivating Management With Viom

    7.3 Deactivating management with VIOM Deactivating management with VIOM You deactivate the management of servers by moving the servers from the VIOM Managed server group to the VIOM Manageable server group. 1. Select the required servers. To do this, click the required server on the left of the VIOM window in the VIOM Managed server group.
  • Page 262 7 Managing servers with VIOM 1. The chassis is indicated as "managed". This happens, on the one hand, in the VIOM database. However, information is also defined in the man- agement blade of the chassis that this chassis is managed by this instal- lation of the Virtual-IO Manager.
  • Page 263 7.4 VIOM internal operations on blade servers Standard configuration before activating VIOM management Figure 75: Standard configuration of the IBP 10/6 before activation In this configuration, all server blades are linked with the standard uplink set. The six uplink ports together form a LAG. ServerView Virtual-IO Manager...
  • Page 264 7 Managing servers with VIOM Initial configuration after activating VIOM management Figure 76: Initial configuration of the IBP 10/6 after activation After activating the VIOM management (Manage button), the server blades are not connected to each other and are not connected to any external networks.
  • Page 265 7.4 VIOM internal operations on blade servers configured so that they can be accessed from the central management station via their management port. 3. In the management blade, any existing virtualization data (server profile data) is deleted for each server blade slot. VIOM internal operations during deactivation When you deactivate management with the Virtual-IO Manager for a blade server chassis, the following actions are executed internally:...

  • Page 266: Viom-Internal Operations On A Primergy Rack Server

    7 Managing servers with VIOM VIOM-internal operations on a PRIMERGY rack server This section explains the internal operations perfomed when you activate or deactivate management with VIOM for a PRIMERGY rack server. VIOM-internal operations during activation When you activate management with the Virtual-IO Manager for a PRIM- ERGY rack server, the following actions occur internally: 1.
  • Page 267 7.5 VIOM-internal operations on a PRIMERGY rack server The iRMC has limited storage to store multiple trap des- tinations. This configuration can be modified by other programs or by using the iRMC user interface. When removing the trap destination of the VIOM management station from the iRMC configuration, this might result in incorrect behavior of the server, in the case of a power loss event for this server.
  • Page 268 7 Managing servers with VIOM support this functionality. 4. VIOM performs a special so-called init boot that initializes all the I/O devices with the virtualization configuration. This init boot can be avoid- ed and a normal boot performed instead. This option is available in the VIOM user interface when assigning a profile: option Power On after Assign.
  • Page 269 7.5 VIOM-internal operations on a PRIMERGY rack server addresses or WWN addresses) are used from now on. Also the boot device priority setting as defined in the VIOM server profile is no longer valid. The performed init boot results in a power-off state and the server reports the status “Boot without VIOM”...
  • Page 270 7 Managing servers with VIOM station indicating that it is still waiting for these data. This process can be interrupted by disabling the VIOM managed status in iRMC user interface or BIOS interface. At the end of this process the VIOM inventory data is freshly recreated (inven- tory boot), the VIOM virtualization data is rewritten by VIOM to the iRMC (also evaluating the new inventory data) and the virtualization data is made active via an init boot.
  • Page 271 7.5 VIOM-internal operations on a PRIMERGY rack server To deactivate the server’s VIOM-managed status in the iRMC user interface, click the Disable VIOM button in the iRMC view System Overview. To deactivate the server’s VIOM-managed status via the system BIOS, open the Advanced menu: ServerView Virtual-IO Manager...
  • Page 272 7 Managing servers with VIOM Select VIOM in the Advanced menu and set the VIOM-flag from Enabled to Disabled: ServerView Virtual-IO Manager...
  • Page 273 7.5 VIOM-internal operations on a PRIMERGY rack server Regardless of whether you deactivate the VIOM-managed status via the iRMC interface or via the BIOS interface, the VIOM-enabled flag is reset, and the information that identifies the VIOM management station, the VIOM vir- tualization data, and the inventory data are cleared.
  • Page 274 7 Managing servers with VIOM VIOM-internal operations during deactivation When you deactivate management with the Virtual-IO Manager for a PRIM- ERGY rack server, the following actions occur internally: 1. VIOM checks that the server is powered off by reading the power state reported by the iRMC.

  • Page 275: Displaying License Information

    7.6 Displaying license information Displaying license information You use the Show Licenses button on the Virtual-IO Manager tab to request information on the licenses assigned. 1. To do this, click the Show Licenses button on the Virtual-IO Manager tab. The Licenses Information dialog box opens. 2.
  • Page 276 ServerView Virtual-IO Manager...

  • Page 277: Defining Network Paths (Lan)

    Defining network paths (LAN) This chapter describes how to define network paths on an IBP module (LAN connection blade) using VIOM. In the Virtual-IO Manager, defining a network path refers to specifying which external ports are used to connect the relevant blade server chassis to which external networks.

  • Page 278: Defining An Uplink Set

    8 Defining network paths (LAN) The Chassis Configuration tab provides an overview of the configuration (IBP configuration and server profile assignment) of a blade server (see chap- "Viewing the blade server configuration" on page 301). Defining an uplink set To define an uplink set, follow the steps below: 1.

  • Page 279: Defining An Internal Network

    8.1 Defining an uplink set out what other entries you need to make during the further course of the wizard, see section "Defining a dedicated service network" on page 285. You can view the configurations made on the Graphic and Details tabs. 8.1.1 Defining an internal network If server blades only need to communicate with each other and, for security reasons, there must be no connection to an external network, then you con-...

  • Page 280: Defining A Single Network

    8 Defining network paths (LAN) 8.1.2 Defining a single network In VIOM, a single network refers to a network in which a server blade can communicate externally via one or several uplink ports. The uplink ports are grouped in an uplink set. The network is given the same name as the uplink set.
  • Page 281 8.1 Defining an uplink set 3. In the first step of the Create network wizard, select Single network and confirm your entry by clicking Next. The second step of the Create network wizard opens. 4. Enter the required name for the uplink set in Name of uplink set. The network automatically has the same name.

  • Page 282: Defining Vlan Networks

    8 Defining network paths (LAN) 7. If the uplink set is created on a PY CB Eth Switch/IBP 10 Gb 18/8, click Next to confirm your entries. The next step of the Create network wiz- ard opens. In this step, you can specify the CNA parameters. 8.
  • Page 283 8.1 Defining an uplink set 3. In the first step of the Create network wizard, select VLAN / Service VLAN networks and confirm your entry by clicking Next. The second step of the Create network wizard opens. 4. Enter the required name for the uplink set in Name of uplink set. 5.
  • Page 284 8 Defining network paths (LAN) works defined via VLAN IDs, which are to be assigned to the uplink set defined in the previous step. 8. Enter the meaningful name of the network to be used by the uplink set as well as the unique VLAN ID of the network within the shared uplink set.

  • Page 285: Defining A Dedicated Service Network

    8.2 Modifying an uplink set For further information on defining networks, see section "Defining networks (LAN) (for blade servers only)" on page 8.1.4 Defining a dedicated service network Defining a dedicated service network is mostly the same as defining a single network.

  • Page 286: Deleting Networks

    8 Defining network paths (LAN) The name of the uplink set cannot be changed; the field is inac- tive. The type of the uplink set cannot be changed either. The Edit Uplink Set wizard is the same as the Create network wizard (see section "Defining an uplink set"...

  • Page 287: Copying An Ibp Configuration

    8.4 Copying an IBP configuration A message appears asking whether you wish to delete the cor- responding network. 3. If you confirm this, the networks will be deleted. If you delete all networks or the last network of an uplink set, the related uplink set is also deleted.

  • Page 288: Copying Configuration

    8 Defining network paths (LAN) VIOM always copies the entire configuration irrespective of what is selected in the tables. If the target IBP has fewer uplink ports than the source IBP, all uplink ports which does not exist on the target are removed from uplink sets.

  • Page 289: Defining And Assigning Server Profiles

    Defining and assigning server profiles To use address virtualization or to enable a server blade to use a defined net- work, you must: 1. Define a server profile 2. Assign the profile to a slot or a PRIMERGY rack server A server profile contains a set of parameters, which contains the VIOM-spe- cific input/output parameters and the input/output connections.

  • Page 290: Defining Server Profiles

    9 Defining and assigning server profiles An overview of the defined server profiles is displayed via the profile view on the left of the ServerView Virtual-IO Manager window. In this case, a table containing an overview of the profiles defined up to now is displayed on the right of the window.
  • Page 291 9.1 Defining server profiles 5. Once you have entered all the required data, click Next to go to the Con- figure Cards step of the wizard. 6. Select the type and number of onboard IO channel in the Configure Cards step. 7.
  • Page 292 9 Defining and assigning server profiles If you want to use the profile on blade servers with IBP modules, you can specify a network for each LAN port. If you work with blade servers that have non-VIOM-capable LAN modules (Open Fabric mode), do not specify a network as it is not possible to define net- works on these modules.
  • Page 293 9.1 Defining server profiles iSCSI boot device or SAN boot device, you must specify additional boot settings in the next step. 15. Click Next to access another step in this wizard. The next steps depend on what you configured in the IO-Channels step. 16.

  • Page 294: Viewing Server Profiles

    9 Defining and assigning server profiles 19. Once you have entered all the required data, click Next to go to the Con- firm step of the wizard. 20. Use this step to check the entries you have made once again. 21.

  • Page 295: Copying Server Profiles

    9.4 Copying server profiles 2. Select the required profile in the area on the right of the ServerView Vir- tual-IO Manager window. Then click Edit or select Edit Profile from context menu. 3. The Edit Server Profile wizard is launched in which you can change the existing server profile definition.

  • Page 296: Deleting Server Profiles

    9 Defining and assigning server profiles You can only copy server profiles if you specified address ranges for the virtual addressed when you installed VIOM. Deleting server profiles You can delete server profiles you no longer need. 1. To do this, switch to the Server Profiles view in the area on the left of the ServerView Virtual-IO Manager window.
  • Page 297 9.6 Assigning server profiles 2. In the tree structure on the left, select the corresponding blade server or PRIMERGY rack server from the VIOM Managed group. 3. Switch to the Server Configuration tab in the area on the right. 4. Select the required slot of the blade server or the required PRIMERGY rack server in the table.

  • Page 298: Deleting Profile Assignments

    9 Defining and assigning server profiles 8. Confirm your selection with OK. The selected server profile is assigned to the slot. If you have not selected Ignore ext. LAN connections, Ignore Spare or Skip downlink checks, a corresponding warning can be issued in another dialog box.
  • Page 299 9.7 Deleting profile assignments 5. You can only deactivate a server profile if the corresponding server is switched off (power off). You can see whether the server is switched off in the State column. If the state of the server is not off, you can switch it off by clicking Shut- down or by selecting Shutdown in the context menu.
  • Page 300 ServerView Virtual-IO Manager...

  • Page 301: Viewing The Blade Server Configuration

    10 Viewing the blade server con- figuration You view the blade server configuration via the Chassis configuration tab. 1. Click the Chassis configuration tab.The Chassis configuration tab contains a schematic display of the existing configuration of the blade server. 2. Click the Update States button to update the display of the on/off status of the server blades in the rectangle of the slots.
  • Page 302 ServerView Virtual-IO Manager...

  • Page 303: Saving And Restoring

    11 Saving and restoring You can save your blade server configuration and server profiles in files and restore them later. Backups like these are useful, for example, if you want to use previous configurations after a new installation. You can store these backup files both on the management station and locally on the computer on which the Web GUI runs.

  • Page 304: Restoring The Configuration

    11 Saving and restoring Select an existing file from the list that will then be overwritten. Enter the name for the backup file directly in the input field.You can also write in subdirectories by specifying the entire path name (e. g. directory/file).

  • Page 305: Restoring Server Profiles

    11.2 Restoring the configuration 3. Click Next to go to the Select File step. 4. Select the backup file from which you want to restore the configuration: Select Restore file from Management Station to select a backup file from the management station. Select Restore local file to select a file on the computer on which the GUI runs 5.

  • Page 306: Restoring Blade Server Configurations

    11 Saving and restoring 3. Select the Keep existing profiles option, to keep the existing profiles. This option is selected automatically if you select the Restore only reas- signed profiles option. If you do not select this option, all existing pro- files are deleted before the configuration is restored.

  • Page 307: Restoring Primergy Rack Server Configurations

    11.2 Restoring the configuration by clicking the Options... button in the table row. 2. Select Restore Spare Information to restore the information on the spare slots. 3. Select Reassign Profiles if you want to reassign the profiles which were assigned when the backup was performed. This option is only avail- able if the backup contains profiles.

  • Page 308: Deleting Backup Files On The Management Station

    11 Saving and restoring 11.3 Deleting backup files on the management station The starting point for deleting backup files on the management station is the Virtual-IO Manager tab. 1. Launch the relevant wizard using the Configuration Backup / Restore button. 2.

  • Page 309: Deleting The Configuration Of An Uninstalled Ibp Module

    11.4 Restoring VIOM-specific configurations The Restore IBP function rewrites the configuration saved internally in the VIOM database to the IBP module. In doing so, all the connections are interrupted momentarily, as all the network connections are reprogrammed in the IBP module. The same applies if a defective IBP module is replaced.

  • Page 310: Restoring The Configuration Of A Server Blade Slot

    11 Saving and restoring Delete Configuration deletes the configuration saved internally in the VIOM database. 11.4.3 Restoring the configuration of a server blade slot In a few rare cases (e. g. when the network connection to the management blade is interrupted), an error may occur during the assignment of a server pro- file to a server blade slot.

  • Page 311: Restoring The Blade Server Chassis Configuration

    11.4 Restoring VIOM-specific configurations 11.4.4 Restoring the blade server chassis configuration By clicking Restore on the Setup tab, the entire virtualization information of the Virtual-IO Manager is rewritten for a blade server chassis managed by the Virtual-IO Manager: The configurations saved in the Virtual-IO Manager are performed again accordingly for all the IBP modules in the chassis.
  • Page 312 ServerView Virtual-IO Manager...

  • Page 313: Importing And Exporting Server Profiles

    12 Importing and exporting server pro- files You have the option of exporting and importing server profiles. The exported data is available as XML files that can be modified or enhanced. You can use this procedure, for example, if you want to create a number of profiles without using the wizard.

  • Page 314: Format Of Export Files

    12 Importing and exporting server profiles 12.3 Format of export files The file specified during an import must be an XML file whose root element is Objects (see below). This file has the following structure: <?xml version="1.0" encoding="UTF-8"?> <Objects xmlns="http://schemas.fujitsu.com/serverview/viom/objects" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance schemaVersion="V3.1"> … </Objects>...

  • Page 315: The Serverprofiles Element

    12.3 Format of export files The Objects element contains the following elements: UserInfo (optional) ServerProfiles Describes the profiles to be imported (see below) 12.3.2 The ServerProfiles element The ServerProfiles element can have the following optional attributes: errorAction Specifies whether the import will continue if an error occurs. If this attrib- ute is specified, it overwrites the value from the Objects element.

  • Page 316: The Serverprofile Element

    12 Importing and exporting server profiles existingAddressAction Specifies the response if a virtual address is already in use. For individ- ual server profiles, the value in the corresponding ServerProfile element can be overwritten. Possible values are: Refuse Handled in accordance with the current error behavior (see errorAction).
  • Page 317 12.3 Format of export files Continue Errors are converted into warnings and the import then continues with the next object. existingProfileAction optional Specifies the response if a server profile to be imported already exists. If this attribute is specified, it overwrites the value from the ServerProfiles element.
  • Page 318 12 Importing and exporting server profiles ServerProfileName Name of the server profile. IOVirtualizationUsage The profile uses virtual addresses. You must specify the Address- Virtualization element in all IOChannel elements of this profile. The profile does not use any virtual addresses. You must not spec- ify the AddressVirtualization element in any IOChannel element of this profile.

  • Page 319: The Iochannel Element

    12.3 Format of export files Fabric4 Default All paths are routed to fabric 4. Fabric3+4 LAN1 is routed to fabric 3 and LAN2 to fabric 4. IOChannels Defines the ports. This element contains an IOChannel element for each port of the profile (see below). 12.3.4 The IOChannel element An IOChannel element contains the following elements: IOChannelSpec...
  • Page 320 12 Importing and exporting server profiles ISCSIFunction Physical iSCSI function of a CNA port IOSlotIndex For I/O Channels in a profile that uses only one slot:always 0. For multi-slot profiles: 0 for the main slot and 2 for the lower slot. IOBoardType Type of board to which the port belongs: OnBoard...
  • Page 321 12.3 Format of export files Networks Defines the networks used by this IO channel. This element contains an optional NetworkName element optionally followed by one or more ServiceName elements and then optionally by one or more Tag- gedName elements: NetworkName Optional, must not be specified for FC ports or for PRIMERGY rack server profiles.
  • Page 322 12 Importing and exporting server profiles BootDeviceUsage Indicates whether the port is used as a boot device. The port is a boot device and the BootEnvironment element (see below) must be specified. The port is not a boot device and the BootEnvironment element (see below) must not be specified.

  • Page 323: The Address Element

    12.3 Format of export files FunctionConfiguration optional Specifies the configuration for a function (see " The Func- tionConfiguration element" on page 329). This element must be specified for functions and must not be specified for other IOChannelType. 12.3.5 The Address element An Address element that specifies the E-MAC address of a CNA FCoE-func- tion must have the attribute purpose="fcoe".

  • Page 324: The Iscsibootconfiguration Element

    12 Importing and exporting server profiles FCBootConfiguration BootPriority Specifies the boot order. Possible values are 1 to 4. However, each value can only appear once within a profile. PXEBootConfiguration Specifies that the port is a PXE boot device. This element is empty. You can only specify this element for LAN ports.
  • Page 325 12.3 Format of export files A static client IP address, subnet mask, and gateway IP address must be specified. Name Name of the iSCSI initiator to be used (in the case of an iSCSI boot) for the connection to the iSCSI target. VLANId optional VLAN ID that is used by the HBA to send its requests.
  • Page 326 12 Importing and exporting server profiles DHCPUsage In the case of an iSCSI boot, the system tries to obtain the name of the iSCSI target, the IP address of the iSCSI target, the IP port number, and the SCSI LUN ID from a DHCP server in the network.

  • Page 327: The Fcbootconfiguration Element

    12.3 Format of export files CHAP CHAP authentication is activated for this port. CHAP allows the target to authenticate the initiator. MutualCHAP Mutual CHAP authentication is activated for the port. Mutual CHAP allows the initiator to authenticate the target. ChapUserName Not when AuthenticationMethod is None The CHAP user name.
  • Page 328 12 Importing and exporting server profiles The first or only FCTarget configures the boot device while the second FCTarget configures the backup boot device. It contains the following elements: TargetWWPN The WWPN (worldwide port name) of the port for the boot device. TargetLUN The LUN (logical unit number) address of the boot device.

  • Page 329: The Dcbconfiguration Element

    12.3 Format of export files Point-to-Point auto (Point-to-Point first) Arbitrated loop 12.3.9 The DCBConfiguration element The DCBConfiguration element specifies one priority group and contains the following elements: PriorityPurpose The purpose of this priority group. Possible values are Other, FCoE, and iSCSI. PriorityLevel Priority level;...
  • Page 330 ServerView Virtual-IO Manager...

  • Page 331: Viom Scenarios

    13 VIOM scenarios This chapter describes examples of when VIOM can be used. 13.1 Shifting tasks from one server blade to another If an operating system or an application needs to run on another server blade of a blade server or if a server blade fails and another server blade has to assume these tasks, then VIOM allows server profiles to be moved from one slot of the blade server to another from the central management station.

  • Page 332: Moving Tasks Using The Server Profile Failover

    13 VIOM scenarios 5. You can only assign a server profile to a server blade if the server blade is shut down. Therefore shut the server blade down, if applicable, by clicking Shut- down or by selecting Shutdown in the context menu. You can see the state of a server blade in the State column.

  • Page 333: Disaster Recovery

    13.3 Disaster Recovery 4. Define the slots that are to be available as spare slots for a server profile failover. To do this, enable the check box in the Spare column in the table for the relevant slots. If an error occurs or maintenance work needs to be carried out, select the Fail- over function in the context menu of the affected server blade on the Server Configuration tab.
  • Page 334 13 VIOM scenarios This means you shut down the blade on the failed site, unassign the profile, and assign it again on the other site. But this only works if the chassis (MMB, connection blades, and server blades) are accessible to the VIOM man- agement station, which is typically not the case in such a disaster scenario.
  • Page 335 13.3 Disaster Recovery To allow the switchover in this case, VIOM provides a “forced unassign” option, allowing you to unassign a profile even if the corresponding MMB (con- taining this profile) is not available. But applying this function means that there will be two chassis with at least partially identical profiles, potentially resulting in, for example, duplicate vir- tual addresses as soon as the failed site goes online again.
  • Page 336 13 VIOM scenarios Via iRMC on each server blade: As an alternative you may log on to each iRMC and set the “Power Restore Policy” to “Always power off” for each iRMC separately, at least for all server blades potentially running virtual addresses. We strongly recommend that you set it for all.

  • Page 337: Viom Database

    14 VIOM database This chapter describes the VIOM database on a Windows- or Linux-based CMS. The Virtual-IO Manager requires two databases: The ServerView database, which is installed with ServerView Oper- ations Manager, and The VIOM database, which is installed with VIOM. Both databases should be regularly backed up.

  • Page 338: Viom Backup Service

    14 VIOM database "Installing ServerView Operations Manager Software under Linux - Instal- lation Guide". 14.1 VIOM Backup Service The Backup Service of the Virtual-IO Manager is a service used to peri- odically back up the VIOM database. Note that its sole purpose is currently to back up the VIOM data- base, whereas the backup of ServerView database is done by ServerView itself.

  • Page 339: Configuring The Job Schedule On Windows

    14.1 VIOM Backup Service The following parameters need to be configured for the backup jobs: The Quartz cron expressions which determine when the backup jobs are scheduled (see section "Configuring the job schedule on Windows" on page 339) and "Configuring the job schedule on Linux" on page 342.

  • Page 340: Syntax Of Quartz Cron Expressions

    14 VIOM database Trigger description relating to the full backup job in the quartz_ jobs.xml file <trigger>  <cron>   <name>cronFullBackupJobTrigger</name>   <group>MSSQL-cron</group>   <description />   <job-name>FullBackupJob</job-name>   <jop-group>MSSQL</jop-group>   <cron-expression>0 0 19 ? * FRI</cron-expression>  </cron> </trigger> The trigger description above only belongs to the job called FullBackupJob of SQL Server.
  • Page 341 14.1 VIOM Backup Service Field Mandatory Values Special characters Month 1 - 12 or JAN - DEC , - * / Day of Week yes 1 - 7 or SUN - SAT , - * / ? L # Year 1970 - 2099 , - * / Table 5: Fields of a Quartz cron expression...

  • Page 342: Configuring The Job Schedule On Linux

    Table 6: Use of special characters 14.1.2 Configuring the job schedule on Linux The Backup Service uses the open source Quartz framework to periodically run jobs that perform various backups of the database. Quartz is configured by editing the file: /opt/fujitsu/ServerViewSuite/plugins/viom/Manager/quartz_jobs.xml ServerView Virtual-IO Manager...

  • Page 343: Configuring The Output Directories

    14.1 VIOM Backup Service For PostgreSQL: If the schedule does not suit your needs, you should edit the Quartz cron expression: <cron> <name>PostgresJobTrigger</name> <group>Postgres-cron</group> <description>…</description> <job-name>PostgresJob</job-name> <job-group>Postgres</job-group> <cron-expression>0 0 19 ? * FRI</cron-expres- sion> </cron> 14.1.3 Configuring the output directories To configure the output directories for the backup jobs, you must open quartz_job.xml (e.g.

  • Page 344: Starting The Backup Service On Windows

    14 VIOM database The outputDirLinux entity defines the directory for full backup files (example: /var/fujitsu/ServerViewSuite/viom/postgres/backups) on Linux. The output directories for the backup files should be on a different hard disk than the VIOM database. This could also be an external hard disk.

  • Page 345: Logging The Backup Service

    14.2 Restoring the VIOM database on Windows 14.1.6 Logging the Backup Service The Backup Service logs important events in the Windows Event Logging or syslog on Linux. So you can search the Windows Event Logging respectively syslog for infor- mation on the Backup Services or for troubleshooting them. 14.2 Restoring the VIOM database on Windows In the event of an error, you can restore the VIOM database from the back- ups.
  • Page 346 14 VIOM database Stop the services ServerView Virtual IO Manager Services and Server- View Virtual IO DB Backup Services: 1. Select Start – [Settings] – Control Panel – Administrative Tools – Services. 2. Select the appropriate service and then select Stop from the context menu.
  • Page 347 14.2 Restoring the VIOM database on Windows 2. On the General page, enter the name ViomDB or master in the To data- base field or select the name from the list. 3. Select the option From device. 4. Click the ... button. 5.
  • Page 348 14 VIOM database 10. Click OK and then OK again. Restoration of the database begins. In the ObjectExplorer you will see the message ViomDB (Restoring…). Restore the transaction logs if available: 1. Click Databases and then select Restore Databases … from the con- text menu.

  • Page 349: Restoration Via Enterprise Manager

    14.2 Restoring the VIOM database on Windows 1. Select Start – [Settings] – Control Panel – Administrative Tools – Services. 2. Select the appropriate service and then select Restart from the context menu. It is now possible to access the VIOM database via Virtual-IO Manager again.

  • Page 350: Restoring The Viom Database On Linux

    1. Stop the VIOM Backup Service: /etc/init.d/viom_backup stop 2. Stop the VIOM Manager Service: /etc/init.d/viom_man stop 3. Import the VIOM database: bzip2 –cd /var/fujitsu/ServerViewSuite/viom/postgres/ backups/ViomDB.dump.bz2 |/opt/fujitsu/ServerViewSuite/ Postgresql/pgsql/bin/psql –p 9212 –d ViomDB –U svuser 4. Start the VIOM Manager Service: /etc/init.d/viom_man start...
  • Page 351 14.3 Restoring the VIOM database on Linux 5. Start the VIOM Backup Service: /etc/init.d/viom_backup start ServerView Virtual-IO Manager...
  • Page 352 ServerView Virtual-IO Manager...

  • Page 353: Appendix

    15 Appendix 15.1 Replacing IBP modules If an IBP connection blade in a chassis managed by Virtual-IO Manager fails, please perform the following actions when replacing this connection blade with a connection blade of the same type: 1. Unplug all LAN cables connected to the defective IBP. Important All cables should have a label that uniquely identifies them and allows you to reconnect them to the same...

  • Page 354: Viom Address Ranges

    15 Appendix using telnet as the communication protocol, please check whether telnet is enabled on the new connection blade. 5. When the new connection blade has the correct setup and is running in IBP mode (final boot has finished and connection blade is accepting IBP commands), please perform the action Explore in ServerView Oper- ations Manager (menu item of the context menu in the ServerList win- dow) for the related blade server chassis and wait until this action is...
  • Page 355 15.2 VIOM address ranges These address ranges are defined as follows: Address range Start address End address MAC1 00:19:99:3E:D2:A1 00:19:99:3E:F1:E0 MAC2 00:19:99:3E:F1:E1 00:19:99:3F:11:20 MAC3 00:19:99:3F:11:21 00:19:99:3F:30:60 MAC4 00:19:99:3F:30:61 00:19:99:3F:4F:A0 MAC5 00:19:99:3F:4F:A1 00:19:99:3F:6E:E0 MAC6 00:19:99:3F:6E:E1 00:19:99:3F:8E:20 MAC7 00:19:99:3F:8E:21 00:19:99:3F:AD:60 MAC8 00:19:99:3F:AD:61 00:19:99:3F:CC:A0 MAC12 00:19:99:3E:D2:A1 00:19:99:3F:11:20 MAC34...

  • Page 356: Creating Diagnostic Data

    15 Appendix These address ranges are defined as follows: Address range Start address End address WWN1 50:01:99:93:ED:2A:10:00 50:01:99:93:EF:1E:0D:FF WWN2 50:01:99:93:EF:1E:0E:00 50:01:99:93:F1:12:0B:FF WWN3 50:01:99:93:F1:12:0C:00 50:01:99:93:F3:06:09:FF WWN4 50:01:99:93:F3:06:0A:00 50:01:99:93:F4:FA:07:FF WWN5 50:01:99:93:F4:FA:08:00 50:01:99:93:F6:EE:05:FF WWN6 50:01:99:93:F6:EE:06:00 50:01:99:93:F8:E2:03:FF WWN7 50:01:99:93:F8:E2:04:00 50:01:99:93:FA:D6:02:FF WWN8 50:01:99:93:FA:D6:03:00 50:01:99:93:FC:C9:FF:FF If you have an address range of your own that you wish to use for virtual MAC or virtual WWN addresses, then select it in the Custom MAC Range or Custom WWN Range.
  • Page 357 15.3 Creating diagnostic data On a Windows operating system this is typically the directory C:\Program Files\Fujitsu\ServerView Suite\plugins\viom\Manager. Please modify the line StartOptions= by adding the option --debug trace (two minus signs!): StartOptions=--debug trace The trace file of the ServerView Virtual-IO Manager service is: <ServerView Suite>\plugins\viom\Manager\logs\viom-manager.log...
  • Page 358 Remote Connector for it to become effective. On a Windows operating system the action Collect Log Files in the Start menu (Start - All Programs - Fujitsu - ServerView Suite - Virtual-IO Man- ager - Collect Log Files) creates a ZIP archive. This ZIP archive contains all log files from Virtual-IO Manager, VIOM database information, and log files from the ServerView ServerList service.

  • Page 359: Event Logging

    15.4 Event logging For how to collect diagnostic data on a Linux operating system, see the chap- "Collecting diagnostic information" on page To activate the trace functionality of the ServerView Virtual-IO Manager user interface, proceed as follows: 1. On the Virtual-IO Manager tab click the Preferences button. 2.
  • Page 360 15 Appendix For Linux Virtual-IO Manager events are output to the system log with source VIOM-MAN, VIOM-LICENSE-MANAGER, and VIOM-BACKUP- SERVICE. The event logs for errors are self-explanatory and not listed here. Infor- mational events that describe changes to the configuration are shown in the following table.
  • Page 361 15.4 Event logging Event Meaning 50722 Profile modified. 50723 Profile deleted. 50735 Profile assigned. 50736 Profile unassigned. 50821 IO-channel added to profile. 50822 IO-channel of profile modified. 50823 IO-channel removed from profile. 50921 Address range set. 50923 Address range unset. 51000 Power mode for node set.
  • Page 362 ServerView Virtual-IO Manager...

Table of Contents