User Guide - English ServerView Suite ServerView Virtual-IO Manager V3.
Comments… Suggestions… Corrections… The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by e-mail to manuals@ts.fujitsu.com.
Contents Contents 3 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 11 12 12 14 21 21 23 24 2 Virtual-IO Manager - Introduction 2.1 Virtual addresses 2.2 Special connection blade for blade server 2.3 Management with VIOM - Procedure 2.4 Defining networks (LAN) (for blade servers only) 2.
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 CMS 3.9.2 Uninstalling the Virtual-IO Manager on a Linux-based CMS 89 90 94 95 96 96 96 4 Configuration 4.1 Configurations on the managed BX600 Blade Server 4.1.1 Supported hardware configurations for the connection blades 4.1.
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 5.2.1 Tree structure (Server List) 5.2.2 Tree structure (Profiles) 5.3 Tabs 5.3.1 Virtual-IO Manager tab 5.3.2 Setup tab 5.3.3 Ext.
Contents 5.4.2.2 Edit Properties step (Edit Uplink Set wizard - dedicated service network) 180 5.4.2.3 DCB Properties (Edit Uplink Set wizard - single/VLAN network) 183 5.4.2.4 Add Networks step (Edit Uplink Set wizard - VLAN network) 185 5.4.3 Create Server Profile wizard 187 5.4.3.1 Name step (Create Server Profile wizard) 187 5.4.3.2 Configure Cards step (Create Server Profile wizard) 189 5.4.3.3 IO-Channels step (Create Server Profile wizard) 190 5.4.3.
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 5.7.2 Button in the area on the right 5.7.3 General buttons in other dialog boxes 5.
Contents 8.2 Modifying an uplink set 8.3 Deleting networks 8.4 Copying an IBP configuration 8.5 Copying configuration 8 285 286 287 288 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 289 290 294 294 295 296 296 298 10 Viewing the blade server configuration 301 11 Saving and restoring 11.
Contents 12.3.8 The FCBootConfiguration element 12.3.9 The DCBConfiguration element 12.3.10 The FunctionConfiguration element 327 329 329 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 331 331 332 333 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 14.1.
ServerView Virtual-IO Manager
1 Introduction You use the ServerView Virtual-IO Manager (Virtual-IO Manager or VIOM for short) software to manage the input/output parameters (I/O parameters) of following servers: l PRIMERGY blade server (BX600, BX400, BX900) In Japan, BX600 blade servers are not supported. l PRIMERGY rack server (RX200 S7, RX300 S7, RX350 S7) l PRIMERGY tower server (TX300 S7) When PRIMERGY rack servers are mentioned below, both, the PRIMERGY rack servers and the PRIMERGY tower servers, are meant.
1 Introduction VIOM provides an easy-to-use Web-based graphical user interface, which you can launch using the ServerView Operations Manager. Using this interface, you can carry out all the necessary tasks for managing the I/O parameters of a PRIMERGY blade server or PRIMERGY rack server and for the LAN connection blade, the IBP module in PRIMERGY blade server. VIOM also provides a comprehensive command line interface, which you can use to perform administrative VIOM tasks in a script-based environment.
1.2 System requirements o Red Hat RHEL 5.6/5.7/5.8 o Red Hat RHEL 6, 6.1/6.2 In Japan: Novell SLES is not supported. ServerView Virtual-IO Manager can also be installed in Virtual Machine (VM) under Windows Hyper-V or VMware ESX server. The operating system running on the VM must be one of the above listed operating systems and must be supported by the used hypervisor. l Installed software packages o ServerView Operations Manager as of Version 5.50.13 o Java Runtime Environment (JRE) version 6.
1 Introduction 1.3 Supported Hardware Managed BX600 blade servers Supported systems: BX600 S3 with MMB S3. For information on the required firmware version, see the release notes included. The following table shows which server blades are supported with which range of functions.
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.
1 Introduction The Virtual-IO Manager can only manage BX400 chassis with S1 management blades (MMB S1) that are assembled with the following: l l l In fabric 1: o LAN connection blades (PY CB Eth Switch/IBP 1 Gb 36/8+2 (SB11), PY CB Eth Switch/IBP 1 Gb 36/12 (SB11A), PY CB Eth Switch/IBP 1 Gb 18/6 (SB6), or PY CB Eth Switch/IBP 10 Gb 18/8 (SBAX2)) in switch mode or IBP mode, or o LAN pass thru connection blades (PY CB Eth Pass Thru 10 Gb 18/18) In fabric 2: o LAN connection blades (PY CB Eth Switch
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.
1 Introduction The Virtual-IO Manager can only manage BX900 chassis with S1 management blades (MMB S1) that are assembled with the following: l l In fabric 1: o LAN connection blades (PY CB Eth Switch/IBP 1 Gb 36/8+2 (SB11), PY CB Eth Switch/IBP 1 Gb 36/12 (SB11A), PY CB Eth Switch/IBP 1 Gb 18/6 (SB6), or PY CB Eth Switch/IBP 10 Gb 18/8 (SBAX2)) in switch mode or IBP mode, or o LAN pass thru connection blades (PY CB Eth Pass Thru 10 Gb 18/18) In fabric 2: o LAN connection blades (PY CB Eth Switch/IB
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 RX300 S7 RX350 S7 Assign VIOM server profiles with I/O address virtualization and boot configuration for the onboard LAN ports and the supported PCI controller. Network connection definition is not supported. TX300 S7 For information on the BIOS and iRMC firmware version, see the release notes supplied.
1 Introduction PCI controller Scope of functions Emulex 10GbE OCe10102 Define physical functions and type (LAN, CNA FCoE, iSCSI) of physical functions. Assign virtual addresses to physical function and optionally define boot parameter. This CNA supports two physical functions for each of both physical ports. The first physical function must be of type LAN. The physical functions for the two physical ports must be defined similarly.
1.4 Changes since the previous edition For information on the required firmware version, see the release notes supplied. 1.4 Changes since the previous edition The current edition is valid for ServerView Virtual-IO Manager V3.1 and replaces the online manual "PRIMERGY ServerView Suite, ServerView Virtual-IO Manager V3.0", Edition March 2012. ServerView Virtual-IO Manager V3.1 includes the following new features: 1.
1 Introduction For ServerView Suite, links are offered on the following topics: l Forum l Service Desk l Manuals l Product information l Security information l Software downloads l Training The downloads include the following: o Current software statuses for the ServerView Suite as well as additional Readme files.
1.6 Documentation for the ServerView Suite l Select Help – Links on the start page or on the menu bar. This opens the start page of the ServerView link collection. 2. Via the ServerView Suite DVD 2 or via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server. You access the start page of the online documentation via the following link: http://manuals.ts.fujitsu.com l In the selection list on the left, select Industry standard servers.
1 Introduction 1.7 Typographic conventions The following typographic conventions are used: Convention Explanation Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. bold Indicates references to names of interface elements. monospace Indicates system output and system elements, e.g., file names and paths. monospace semibold Indicates statements that are to be entered using the keyboard.
2 Virtual-IO Manager - Introduction This chapter provides a general introduction to the concept of the Virtual-IO Manager (VIOM). 2.1 Virtual addresses Physical MAC addresses and WWN addresses are stored on the network card or in the host bus adapter (HBA) of a server blade or PRIMERGY rack server. If a server blade or PRIMERGY rack server has to be exchanged or the operating system and/or the application has to be started on another server, usually the LAN or SAN network has to be reconfigured.
2 Virtual-IO Manager - Introduction Figure 1: Overlapping areas of responsibility As the areas of responsibility overlap, this means that up to three administrators may be involved if a server blade's configuration changes, e. g. because a server blade has to be replaced due to hardware problems and, as a result, the switches have to be reconfigured.
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.
2 Virtual-IO Manager - Introduction Figure 2: Separate areas of responsibility 2.3 Management with VIOM - Procedure You use the ServerView Virtual-IO Manager (VIOM) to manage the connection blades of a blade server and to maintain the relevant I/O parameters constant at the chassis slot of a blade server or at the PRIMERGY rack server. VIOM is installed on the central management station and integrated in the ServerView Operations Manager.
2.
2 Virtual-IO Manager - Introduction 4. You can then assign these server profiles to any of the individual slots of a blade server or to a PRIMERGY rack server. 5. If required, you can remove the assignment of the server profile. For blade server, you can move the profiles from one blade server slot to another, or move them to another blade server. For PRIMERGY rack servers, you can move the profiles from one server to another server. 2.
2.4 Defining networks (LAN) (for blade servers only) If a blade server chassis is managed by VIOM, manual configurations (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.
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. This gives you several independent network paths e. g. for different applications (e. g.
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 backup ports. As a result, there are different ways of configuring an uplink set: l "Port backup" configuration When you configure a "port backup", you define an uplink set with at least two uplink ports, and configure one of these as an active port and the other as a backup port.
2 Virtual-IO Manager - Introduction aggregation group (LAG) is formed. By providing several parallel connections, you achieve higher level of availability and a greater connection 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. If an uplink set has several backup ports, these backup ports also form a link aggregation group automatically in the case of a failover.
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. The same applies to the network packets that come from the server blades.
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. Although both uplink sets have virtual networks with the VLAN ID 20, these are two different virtual networks.
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). Packets that come from a server blade, which do not have a VLAN tag, are routed in the VLAN network to which the LAN port of the server blade is connected.
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. Incoming data packets without a VLAN ID tag are assigned the VLAN ID 10 internally. These data packets are only transferred to server blade 1.
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 downlink port. They can also be combined with service networks. The mode in which a VLAN network is used is controlled by network definitions in a server profile. It cannot be specified within the network settings.
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 separate management LAN but is configured to share its LAN traffic with an onboard LAN port of the server blade. In order to separate the LAN traffic of iRMC and operating system in this case, the iRMC must also be configured to use a VLAN tag for its LAN packets.
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. Incoming untagged packets at the uplink port are tagged and sent to the corresponding downlink ports (internal ports)/blade server as tagged packets.
2 Virtual-IO Manager - Introduction Service VLAN networks Figure 9: Service VLAN networks The Service VLAN networks are designed to separate LAN packages of multiple 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 virtual 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.
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 Service 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. The VLAN tags of the overlapping VLAN networks, dedicated service networks and Service VLAN networks must be different. Different Service VLAN networks may share the same uplink ports.
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. Define a server profile 2. Assign the profile to a slot or a PRIMERGY rack server 2.5.1 Defining server profiles A server profile is made up of a set of parameters that contain the related VIOM parameters.
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. If a server profile is assigned to a slot, the downlinks connected to the I/O channels of the slot are added to the IBP modules in the specified network.
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.
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. The iRMC of a PRIMERGY rack server loses virtualization I/O parameter table during power failures. So the table has to be rewritten by ServerView Virtual-IO Manager before the server is powered on again.
2 Virtual-IO Manager - Introduction 2.7 High-Availability (HA) support VIOM supports the following high-availability environment: l Windows 2008 R2 Hyper-V cluster with ServerView Operations Manager and ServerView Virtual-IO Manager installed on a virtual machine with Windows Server operating system. l VMware HA with ServerView Operations Manager and ServerView Virtual-IO Manager installed on a virtual machine with Windows Server operating system.
2.7 High-Availability (HA) support Operating system Admin server if HA Guest OS Windows Server 2008 R2 Foundation [*] P Hypervisor P [Hyper-V] Windows Server 2008 Standard (x86, x64) [*] P P [Hyper-V] (only x64) Windows Server 2008 Enterprise (x86, x64) [*] P P [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.
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. Connect with shared storage. 2. Configure BIOS. 3. Install Hyper-V roles. 4. Install and configure EMC Solutions Enabler (if used). 5. Add a failover clustering function. 6.
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. Add a failover clustering function. 6. Create a Hyper-V virtual network. 7. Install Hyper-V roles. 8. Add a failover clustering function. 9. Create a Hyper-V virtual network. 10. Create clusters. 11.
2 Virtual-IO Manager - Introduction Figure 12: Architecture and typical configuration of VMware Infrastructure 3 52 ServerView Virtual-IO Manager
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. For a detailed description of the high-availability functionality with VMware HA, visit http://www.vmware.com/pdf/vmware_ha_wp.pdf.
2 Virtual-IO Manager - Introduction The details of this configuration cannot be seen via the normal 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 ServerViewVirtualIOManagerService displays the current configuration, where ServerViewVirtualIOManagerService is the name of the service.
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 configuration requests. The Virtual-IO Manager can only undo the last internal configuration request.
ServerView Virtual-IO Manager
3 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 Manager on a Windows-based CMS" on page 58 and "Installing the Virtual-IO Manager on a Linux-based CMS" on page 73). Please check first the requirements for installing the Virtual-IO Manager on CMS (see section "Prerequisites for the VIOM installation" on page 57).
3 Installation and uninstallation In Japan: Novell SLES is not supported. ServerView Virtual-IO Manager can also be installed in Virtual Machine (VM) under Windows Hyper-V or VMware ESX server. The operating system running on the VM must be one of the above listed operating systems and must be supported by the used hypervisor. l Installed software packages o ServerView Operations Manager as of Version 5.50.13 o Java Runtime Environment (JRE) version 6.
3.2 Installing the Virtual-IO Manager on a Windows-based CMS 3.2.1 Installing the Virtual-IO Manager using a graphical interface 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. 2. Select the option ServerView Software Products. 3. Click Start. 4. In the next window, select the required language. 5. Select ServerView – Virtual-IO Manager. 6.
3 Installation and uninstallation 7. Click Next. Accept the license agreement by selecting the corresponding option.
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.
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 addresses in server profiles, you must have already defined address ranges here. 10. Click Next.
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 profile definition. Eight predefined MAC address ranges are available for selection, which do not overlap (MAC Address Range 1 to MAC Address Range 8). Each of these address ranges contains 8000 MAC addresses.
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. Otherwise addresses may be assigned several times. To change the range of the address after installation is finished, you must uninstall the Virtual-IO Manager and install it again.
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).
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.
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 following window is then displayed: 14. Click Next to launch the License Manager.
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 information on the License Manager, see section "License management" on page 90 l The licenses are not version bound. l Licenses purchased with Virtual-IO Manager versions prior to V2.4 are also still valid.
3.2 Installing the Virtual-IO Manager on a Windows-based CMS end>"][DEBUG_MODE=true|false][VIOM_LICENSE_KEY = ""] 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.
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. MAC_START, MAC_END These parameters must be set if MAC_Custom is specified.
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.
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 3.
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. 3.4 Installing the Virtual-IO Manager on a Linux-based CMS The corresponding software is supplied with the PRIMERGY ServerView Suite DVD1.
3 Installation and uninstallation 3.4.1 Installing the Virtual-IO Manager using a graphical interface 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" on page 57). Installation process 1. Set the DISPLAY environment variable: export DISPLAY=:0.0 Example export DISPLAY=111.22.33.115:0.0 2.
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.
3 Installation and uninstallation 4. Click Next. Accept the license agreement by selecting the corresponding option.
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.
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.
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 addresses in server profiles, you must have already defined address ranges here. 8. Click Next.
3 Installation and uninstallation If you selected Select address ranges for IO Virtualization, the following 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 profile definition. Eight predefined MAC address ranges are available for selection, which do not overlap (MAC Address Range 1 to MAC Address Range 8).
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. 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. Otherwise addresses may be assigned several times.
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).
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 information on the License Manager, see section "License management" on page 90. Then click OK l The licenses are not version bound. l Licenses purchased with Virtual-IO Manager versions prior to V2.4 are also still valid.
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. You find the script in the directory where you unzipped the VIOM software package (see "Installing the Virtual-IO Manager using a graphical interface" on page 74).
3.
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 --wwn-range WWN address range.
3.
3 Installation and uninstallation ja Japanese --upgrade|-u Run installation in upgrade mode if you upgrade from one VIOM version to another --quiet|-q Silent installation --force|-f Force installation without rpm and error checks --installdir|-i Path to the installation directory tree up to and including subdirectory RPMS (default:current directory) --verbose|-v More logging details in the log files Example sh install_viom.sh -–no-gui -–dbhost=127.0.0.
3.5 Updating the Virtual-IO Manager on a Linux-based CMS /var/log/fujitsu/ServerViewSuite/viom Directory in which the VIOM log files are stored. 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.
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. 3.6 License management You need at least one license in order to use VIOM. You purchase licenses for a certain number of server profiles that can be assigned to server blades using VIOM. l The licenses are not version bound.
3.6 License management l If you do not have a valid license, you cannot log in to the VIOM Manager. l If the number of currently assigned server profiles exceeds the number of server profiles you are allowed to assign, you cannot make any further configuration changes except for Unassign Profile (see section "Deleting profile assignments" on page 298 ) or Unmanage(see section "Deactivating management with VIOM" on page 261).
3 Installation and uninstallation 2. Click Register new license. Enter a valid license here. You can also enter several licenses by clicking Register new license again. Each license contains a number of assigns. This license permits you to assign this number of server profiles. Licenses purchased with Virtual-IO Manager versions prior to V2.4 are also still valid.
3.6 License management 2. Select the relevant license and click Deregister licenses. The selected license is deleted. If the number of allowed assignments is smaller than the number of assigned server profiles, an error message is displayed and the deletion process canceled. On Linux you can also add a licence without graphical user interface: cd /opt/fujitsu/ServerViewSuite/plugins/viom/Manager java -jar ./VIOM-LICENSE-MANAGER.
3 Installation and uninstallation 3. The information displayed includes the following: l License code l Validity period (only relevant for demo licenses) l Max. number of assignments that are allowed with the licenses l Number of currently assigned server profiles l Number of server profiles that can still be assigned with the licenses For more information, see section "Displaying license information" on page 275. 3.
3.8 Upgrading or moving the SQL Server database When you need to uninstall existing ServerView Operations Manager and install the new one, you should uninstall existing Virtual-IO Manager: 3.
3 Installation and uninstallation LOG ON (FILENAME='\ViomDB_log.LDF') FOR ATTACH DBCC UPDATEUSAGE('ViomDB') l In the installation directory of the Virtual-IO Manager you will find a Java properties file called ViomConfig.properties. Change the instance name to the new value, e.g.: SqlServerInstance=(local)\\SQLSERVERVIEW2 3.9 Uninstalling the Virtual-IO Manager Before you uninstall VIOM, you should unmanage all servers. After uninstalling, all information will be lost.
4 Configuration In the following sections, you find information on the required configurations on the managed server. 4.1 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.
4 Configuration in fabric 2. FC switch blades do not support any dedicated network connections, but just the virtualization of the I/O parameters instead. l If you only intend to work with virtual I/O parameters (Open Fabric mode) and not with dedicated network connections, you can also install nonVIOM-capable LAN modules in fabric 1 or fabric 2. Furthermore, you can operate non-VIOM-capable LAN modules in fabric 1 with FC modules in fabric 2. 4.1.1.
4.1 Configurations on the managed BX600 Blade Server l You cannot mix LAN and IBP modules within a fabric. l You can only assign profiles if no networks are defined for their ports. You can force the assignment of a profile with network definitions by answering the subsequent query accordingly. In doing so, however, the network definitions are ignored. l You can operate LAN models of different sizes within a fabric, although you cannot use all download links from the larger model. 4.1.1.
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: l The management blade must be installed with a specific firmware version. To find out which firmware version you need, see the release notes included. You can check the firmware version in the Remote Manager of the management blade. To do this, choose (1) Management Agent – (2) Management Blade.
4.1 Configurations on the managed BX600 Blade Server To check the parameter setting in the Remote Manager of the management blade, choose (1) Management Agent – (3) System Information – (11) Automatic Inventory Retrieval. l 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. 4.1.
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: l In DHCP Enable, select whether the connection blade should be given its IP address from an DHCP server or not. If you select NO DHCP, you must enter the IP address, subnet mask and the gateway address. l Click Apply to activate the settings.
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: l In the Remote Manager, choose (1) Management Agent – (6) Connection Blade. l Select an I/O connection blade.
4 Configuration For Fibre Channel switch modules (select FC Switch Blade), you must also specify access data for the parameters Set Login Username 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.
4.1 Configurations on the managed BX600 Blade Server For the external switch to which an IBP module is connected for administration, 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. Before you activate management of a blade server with VIOM, only this port is allowed to have a connection to external LAN switches.
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 definitions. If you cannot avoid doing so, then you must note the following: l The speed definition used must remain set to auto negotiate. l The network that uses this uplink port must not be deleted.
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. You do this as follows: l Establish a Telnet or SSH connection to the management blade of the affected blade server chassis.
4 Configuration Example (Vty-0) #show uplink-set Uplink External Set Name ports External active ports External Link Port IGMP backup ports state Backup snoop LACP -------- -------------- ------------ ------------ ----- ------ ----- ---default - - - yes no yes no 1_NET 0/11 0/11 - yes yes yes no 1_NW1 0/12,0/13,0/14 0/13,0/14 0/12 yes yes yes no 1_NW2 0/15,0/16 0/16 yes yes yes no 0/15 (Vty-0 (Vty-0) #show port-group Port Group Name Internal Ports Uplink Set Name External
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.
4 Configuration l Define the connection of the IBP modules with the network, see section "Connecting IBP modules" on page 115 l Add the blade server to the server list of the ServerView Operations Manager, see section "Adding a server to the ServerView server list" on page 135 4.2.
4.2 Configurations on the managed BX400 Blade Server 4.2.1.
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 following into account: l You cannot mix LAN and IBP modules within fabric 3. l You can only assign profiles if no networks are defined for their ports. You can force the assignment of a profile with network definitions by selecting the Ignore ext.
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. Check the following settings in the management blade: l The management blade must be installed with a specific firmware version.
4 Configuration To check the parameter setting in the Web interface open the Components section and select System – System Unit. The System Information section on the right contains the option Automatic Inventory Retrieval. If the value of it is not set to automatic, please set it to automatic and remove and insert all blades or perform a power-off and power-on of the blade server chassis.
4.2 Configurations on the managed BX400 Blade Server You configure the network parameters of an I/O connection blade as follows: l 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. l Click Apply to activate the settings. 4.2.
4 Configuration Please note that before you activate blade server management, several uplink ports of a LAN connection blade in IBP mode form a static 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. 4.2.4.
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 station 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. One of the IBP(s) controlled the operation of the stack modules is called the stack master. Other IBP(s) are belonging to the stack members of the stack group system.
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 "PRIMERGY BX900 Blade Server Systems- Ethernet Connection Blade ModuleIBP version (User`s Guide)", chapter 6. VIOM supports uplink sets and networks on switch stacks. An uplink set can contain uplink ports from different IBPs in a stack. You can see stacks in the VIOM GUI on the Setup tab if you click on a stack member.
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: l 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.
4 Configuration fabric 1, fabric 2, fabric 3, and fabric 4.
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: l in normal switch mode l in Access Gateway mode As a result, different combination options are possible. Fabric 2 and fabric 3 have identical configuration restrictions in relation to the Fibre Channel switch blades.
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 management for the blade server. You can run an update via the Remote Manager of the management blade. For a MMB S1, choose (4) TFTP update. First specify the IP address of the TFTP server by selecting option (1) TFTP Server IP Adress.
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. l 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. 4.3.
4 Configuration You configure the network parameters of an I/O connection blade as follows: l 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. l Click Apply to activate the settings.
4.3 Configurations on the managed BX900 Blade Server You configure the network parameters of an I/O connection blade as follows: l In the Remote Manager, choose (1) Management Agent – (6) Connection Blade. l Select an I/O connection blade. l Choose (2) Management Port Information.
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: l "Normal" Layer 2 switch mode l IBP mode For information on how to perform the switch, refer to the Switch Blade user manual.
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 station 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. One of the IBP(s) controlled the operation of the stack modules is called the stack master. Other IBP(s) are belonging to the stack members of the stack group system.
4 Configuration The stacking software configures each device tables and registers to support all switching functions, for example, switching, link aggregation, port 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 "PRIMERGY BX900 Blade Server Systems- Ethernet Connection Blade Module- IBP version (User`s Guide)", chapter 6. VIOM supports uplink sets and networks on switch stacks.
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 participating connection blades are set to 1 before building the stack. The typical procedure for correct handling by VIOM is: l Configure the stack by enabling the blade server internal stacking links and by connecting SB11 connection blades in different fabrics of the same chassis by special stacking cables.
4 Configuration l The PRIMERGY rack server must be in the list of supported server types. l The system BIOS and the iRMC firmware must fulfill VIOM requirements. Details concerning the required BIOS version and iRMC firmware version might be found in the release notes. l The iRMC of the PRIMERGY rack server must be reachable by LAN from the central management station where VIOM is installed. VIOM uses the RMCP protocol (IPMI over LAN) to communicate with the iRMC of the PRIMERGY rack server.
4.4 Configurations on the managed PRIMERGY rack server For further information on the server list, see the "ServerView Operations Manager" user guide. l 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.
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" on page 132. 4.
4.6 PCI slot location in PRIMERGY rack servers 4.6 l Profiles with onboard CNA configuration cannot be assigned to servers which do not have an onboard CNA controller. l 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. PCI slot location in PRIMERGY rack servers The PCI slots of the supported PRIMERGY rack servers are located as follows.
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 134 ServerView Virtual-IO Manager
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 9 PCI slot 1 10 Shared LAN connector (LAN 1) 11 Standard LAN connector (LAN 2) 12 Management LAN connector (iRMC) 4.
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. You can find a detailed description on the server browser in the ServerView Operations Manager user manual.
5 Virtual-IO Manager user interface This chapter contains a general introduction to the Virtual-IO Manager (VIOM) describing: 5.
5 Virtual-IO Manager user interface The window is divided into three areas: l The ServerView Suite header l The menu bar l 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: l ServerList l Administration l Asset Management l Event Management l Monitoring l Update Management Depending on which menu you select, the individual menu items for
5.2 Tree view Button Selection on the left Display on the right Server List Five tabs are displayed in the area on the right (see "Tabs" on page 142). All Server Only the Virtual-IO Manager tab is activated, which server group contains general information on VIOM. VIOM Man- Same as if all servers of the group were selected. ageable or VIOM Managed server group Object(s) in Only the Virtual-IO Manager and Setup tabs are actithe VIOM vated in the area on the right.
5 Virtual-IO Manager user interface l Server list (default) l 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 Profiles button is: l Below the tree structure if the server list is displayed in this area l Directly above the tree structure if the profiles are displayed in this area. The display in the area on the right changes according to what you select in this area.
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. All Server Includes the servers according to the ServerView server list VIOM Man- Includes the servers that can be managed using VIOM, but ageable are currently not managed VIOM Man- Includes the servers that are managed using VIOM.
5 Virtual-IO Manager user interface 5.3 l 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 VirtualIO Manager window. By using the context menu in the area on the left, you can create a new profile. l Select a profile to show it in the profiles table. By using the context menu, you can edit and delete this profile or make a copy of it.
5.
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. l 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.
5.3 Tabs responding blade server is shown. The table provides the following information: 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.
5 Virtual-IO Manager user interface l Fault State l 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 hardware Configuration of switch/server does not match with database. not supported Switch/server model is not supported. model does not match slot configuration The model is supported, but some other requirements are not met.
5.3 Tabs passwords, which VIOM can use to access these servers. For details see "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. The servers are added to the VIOM Managed server group. Unmanage Deactivate management with VIOM by adding the selected servers to the VIOM Manageable server group. Authentication Opens the Authentication dialog box.
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.
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. Additional information about the selected IBP is shown on the left of the graphic. At the bottom of the tab there is a schematic view of the uplink ports of the selected IBP.
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 window opens. For more information on this, see chapter "Defining network paths (LAN)" on page 277. 5.3.3.2 Details tab on Ext.
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. New Click New to define a new uplink set. The Create network wizard is launched. 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. For more information on this, see chapter "Defining network paths (LAN)" on page 277. 5.3.
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.
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).
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 information of the server blade or PRIMERGY rack server hardware as needed by the Virtual-IO Manager and sends it to the management blade or to iRMC, where it is stored.
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. A new window opens where the console output of the server is shown.
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. For more information on this, see chapter "Defining and assigning server profiles" on page 289". 5.3.
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. At the top edge of the rectangle, the uplink ports of the connection blade connected are displayed as squares and contain the port number. These are ports 37, 38, 39, ….
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. Also in this rectangle, switched-on server blades are indicated with Pwr ON. You can update this display of the on/off status of the server blades with the Update States button. The type of server blade connected (e.g.
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 profile is shown.
5 Virtual-IO Manager user interface Column Significance Network The name of the network defining the dedicated LAN connection Comment for A more detailed description of the profile (optional). Buttons New 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. You can only modify server profiles that are not assigned.
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.
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: l Create Network for IBP wizard l Edit Uplink Set wizard l Create Server Profile wizard l Edit Server Profile wizard l Configuration Backup/Restore wizard 5.4.
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). To open the Create Network for IBP wizard, click New on the Graphic or Details tab. 5.4.1.1 Select Type step (Create Network wizard) Select Type is the first step in the Create Network wizard.
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. Dedicated Service network Creates an uplink set with one dedicated service network. 5.4.1.
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 determines which fields are displayed in the second step. Edit Properties step for single networks/VLAN networks Figure 34: Create Network wizard (second step) Name of uplink set Name of uplink set.
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 configured accordingly. If you select Linkdown propagation, the ports of the related server blades receive a linkdown event if a problem occurs.
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 set.
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. 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.
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 automatically has the same name. 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 configured. By default, Activate Port Backup is selected.
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. A 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.
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. If necessary, the corresponding downlink ports may be added to the forwarding table of this multicast group or removed again. The IGMP Snooping option is selected by default.
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. Ports configured as active or backup ports are indicated by different colors in the display (light red/light green or dark red/dark green).
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). Purpose The purpose of the DCB setting. Possible values are FCoE and iSCSI. Priority Level The priority level.
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 example, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages. 5.4.1.6 Add Networks step (Create Network wizard - VLAN network) Add Networks is the third step in the Create Network wizard if a VLAN network is created.
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. Isolate mode You activate the isolate mode via Isolate mode.
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. Delete Deletes a selected VLAN networks from the list. 5.4.2 Edit Uplink Set wizard You use the Edit Uplink Set wizard to modify an defined uplink set.
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 configured. Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail.
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 configured accordingly. Enable LACP You activate the LACP protocol via Enable LACP.
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. Ports for the uplink set (change with right click) Assign the required ports of the IBP to the uplink set. To do this, open the context menu of each relevant port.
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 colors 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 recognize by this. 5.4.2.2 Edit Properties step (Edit Uplink Set wizard - dedicated service network) Edit Properties is the first step in the Edit Uplink Set wizard.
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 configured. 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 configured accordingly. If you select Linkdown propagation, the ports of the related server blades receive a linkdown event if a problem occurs.
5 Virtual-IO Manager user interface value if a problem occurs using the drop-down menu according to the settings 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. 10 Mbit/s 10 Mbit/s full-duplex. 100 Mbit/s 100 Mbit/s full-duplex. Service VLAN id A Service VLAN ID must be specified.
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. The corresponding port is configured as active and no longer as backup. Backup Only available if the port is configured as Active.
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). Purpose The purpose of the DCB setting. Possible values are FCoE and iSCSI. Priority Level The priority level.
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 example, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages. 5.4.2.4 Add Networks step (Edit Uplink Set wizard - VLAN network) Add Networks is the second step in the Edit Uplink Set wizard if a VLAN network is edited.
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. All packages that do not contain a VLAN ID will be allowed through this connection. Service VLAN Defines a network as service VLAN. Isolate mode You activate the isolate mode via Isolate mode.
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.
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. Server Blade (double height) This profile can be assigned to two slots of a BX900 which are one over the other.
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 maximum 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) Configure Cards is the next step in the 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. For each card you must specify its type: LAN LAN card. This card can have up to four ports. FC Fibre Channel card. This card can have up to two ports. CNA CNA card.
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. You can enter this information in another step within the wizard or VIOM can assign this information automatically.
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 "PRIMERGY BX900 Blade Server Systems - ServerView Management Blade S1". The upper table displays the onboard ports (up to 6). Another table is displayed for each available mezzanine/PCI card configured in the previous step.
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. 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 networks on these modules.
5 Virtual-IO Manager user interface Column Significance Service Names of the service networks. You can specify service networks 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. If you use the network selection box, the name of the chosen network is replaced in the Network column or added to the Service column depending on the type of the selected network.
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. Only the initiator name and (optional) the VLAN ID must be specified here. static A static client IP address, subnet mask, and gateway IP address must be specified.
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. You can enter an IP address in this field if Address Origin: static is selected. Subnet Mask IP subnet mask. This should be the IP subnet mask of the network used to connect this port (in the case of an iSCSI boot).
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. 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 LUN ID of the boot disk on the SCSI target.
5 Virtual-IO Manager user interface Chap Secret CHAP password. This password must be identical to the password configured on the iSCSI target. It must contain 12 to 16 characters. 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 characters. This password must differ from the password in the Chap Secret field.
5.4 Wizards Port Name WWPN (worldwide port name) of the port for the boot device. LUN 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. LUN LUN (logical unit number) address of the backup boot device. The default value for the field is 0. Speed Transmission speed used by the selected port.
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. In this step, you specify the parameter for CNA functions.
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. A value of 60, for example, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages.
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. This option should be enabled if the profile will be used in a blade server chassis where the corresponding physical CNA port will be connected to a PY CB Eth Switch/IBP 10 Gb 18/8 (SBAX2) connection blade in IBP mode.
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 addresses 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 function.
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. Not checked (warn- The address entered has not been ing) checked yet. No value (error) Either an address was not specified or Allocate virtual address was not selected.
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 structure on the left. To open the Edit Server Profile wizard, click the Edit button in the area on the right or select Edit in the context menu of the selected server profile. 5.4.4.
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. Server Blade (double height) This profile can be assigned to two slots of a BX900 which are one over the other.
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 maximum 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) Configure Cards is the next step in the 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. For each card you must specify its type: LAN LAN card. This card can have up to four ports. FC Fibre Channel card. This card can have up to two ports. CNA CNA card.
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. You can enter this information in another step within the wizard or VIOM can assign this information automatically.
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 "PRIMERGY BX900 Blade Server Systems - ServerView Management Blade S1". The upper table displays the onboard ports (up to 6). Another table is displayed for each available mezzanine/PCI card configured in the previous step.
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. 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 networks on these modules.
5 Virtual-IO Manager user interface Column Significance Service Names of the service networks. You can specify service networks 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. If you use the network selection box, the name of the chosen network is replaced in the Network column or added to the Service column depending on the type of the selected network.
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. Only the initiator name and (optional) the VLAN ID must be specified here. static A static client IP address, subnet mask, and gateway IP address must be specified.
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. This should be the IP subnet mask of the network used to connect this port (in the case of an iSCSI boot). You can enter a subnet mask in this field if Address Origin: static is selected. Gateway Address IP address of the network gateway.
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 LUN ID of the boot disk on the SCSI target. You can enter a LUN ID in this field if Address Origin: static is selected. Authentication Authentication Method None No authentication is used.
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 characters. This password must differ from the password in the Chap Secret field. For more information, see the documentation " iSCSI Boot for PRIMERGY Server with Intel Network Controllers".
5.4 Wizards LUN 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 LUN (logical unit number) address of the backup boot device. The default value for the field is 0. Speed Transmission speed used by the selected port. By default, auto negotiate is selected.
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. In this step, you specify the parameter for CNA functions.
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. This option should be enabled if the profile will be used in a blade server chassis where the corresponding physical CNA port will be connected to a PY CB Eth Switch/IBP 10 Gb 18/8 (SBAX2) connection blade in IBP mode.
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. A value of 60, for example, means that a bandwidth of at least 6 Gb/sec is reserved for the FCoE packages. 5.4.4.
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 addresses 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 function.
5 Virtual-IO Manager user interface Status Significance Out of range (error) The address is outside the specified address range. Syntax error (error) The address is syntactically incorrect. Already used (error) The address is already in use 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.
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. You launch the wizard using the Configuration Backup / Restore button on the Virtual-IO Manager tab. 5.4.5.
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.
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. directory/file). If the required directories do not yet exist, they are created automatically. The backup files are assigned the .xml suffix automatically if you have not specified one.
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. File Name for the backup file.
5.4 Wizards Browse Opens the file selection dialog box in which you can select the relevant 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 station. Figure 61: Select File step (Delete Backup Files wizard) The table displays the backup files.
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. Do not select any servers if you only wish to save profiles.
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. Column Significance Configuration Selection box and configurations that could be restored.
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 ). Restore the configuration saved for the selected server. For blade servers, the Restore Options dialog box opens automatically in which you specify additional parameters (see section "Restore Options dialog box (servers)" on page 241 ) . In addition, you can click the Options...
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. 5.5 Dialog boxes Virtual-IO Manager provides the following dialog boxes: l Authentication dialog box l Licenses Information dialog box l Restore Options dialog box l Select Profile dialog box 5.5.1 Authentication dialog box (single blade server) The Authentication dialog box is displayed when you click the Manage or Authentication button on the Setup tab.
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.
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 components 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 protocol and port to be used by VIOM to access the components. These values should not be changed in a standard configuration.
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. If you select one or more PRIMERGY rack server(s) in this table on the Setup tab, the following Authentication dialog box is shown.
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 components. This value should not be changed in a standard configuration.
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. 5.5.3 Authentication dialog box (PRIMERGY rack server and blade server) The Authentication dialog box is displayed when you click the Manage or Authentication button on the Setup tab.
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. This dialog box opens when you click the Show Licenses button on the Virtual-IO Manager tab.
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 OK Closes the Licenses Information dialog box. 5.5.5 Preferences dialog box The Preferences dialog box allows you to set user preferences. This dialog box opens when you click the Preferences button on the VirtualIO Manager tab.
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.
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). On this tab you find the following options and input fields: Write trace messages to file Select this option to write trace output to file(s). If this option is not selected, the trace output is written to the Java Console only.
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 appended, 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. Trace level Specifies the amount of trace information. To create diagnostic data, fine is an appropriate value. no tracing Tracing is switched off. severe Only the most important information is traced.
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. Figure 71: Restore Options dialog box (blade server) Restore Spare Information Specifies whether the information on the spare slots is restored.
5.5 Dialog boxes dialog box where you can select the destination blade server. OK 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. It also opens when you click the Options... button in the Profiles row.
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 configurations" on page 306). If you do not select this option, all the profiles saved in the backup file will be restored. Keep existing profiles Specifies that the existing profiles remain the same. This option is selected automatically if you select the Restore only reassigned profiles option.
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 management station. This option cannot be selected together with Keep existing profiles. OK Applies your selection and closes the dialog box. Cancel Closes the dialog box without applying your selection. 5.5.8 Select Profile dialog box In the Select Profile dialog box, you can select the required server profile in the tree structure.
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. LAN connections If you try to assign a server profile with configured networks to a normal LAN switch, you will get an error. With this option you ignore all networks of the server profile.
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. With this option you can assign a server profile even though no switch is set OK The selected server profile is assigned to the slot. If you have not selected Ignore ext.
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: Add Assign port to an uplink set Add as Backup Assign port to an uplink set as a backup port Remove Remove port assignment from an uplink set Active Change configuration of a backup port in an active port Backup Change configuration of an active port i
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.
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 information of the server blade or PRIMERGY rack server hardware as needed by the Virtual-IO Manager and sends it to the management blade or to iRMC, where it is stored.
5.7 General buttons 5.7 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. Profiles button Click Profiles in the left area of the Virtual-IO Manager to switch to the profile view of the defined server profiles. 5.7.
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. 5.8 Icons This section contains a list of the VIOM-specific icons and their meaning. These icons are displayed on the Setup tab when you click a module in the display. Icon Significance The module cannot be managed. The module has minor configuration problems.
6 Using the Virtual-IO Manager 6.1 Starting the Virtual-IO Manager You can start the Virtual-IO Manager from the main window of the ServerView Operations Manager: 1. Start the ServerView Operations Manager. For information on starting the ServerView Operations Manager, see the ServerView Operations Manager user guide. 2. Start the Virtual-IO Manager on the start page of the Operations Manager by choosing Administration – Virtual-IO Manager.
6 Using the Virtual-IO Manager 6.3 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. To do this, the Virtual-IO Manager creates a separate Event Log ServerView VIOM, in which it saves its events (see "Event logging" on page 359).
6.
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 example on SLES 11 you will find the VIOM messages in the file /var/log/user_ messages.
7 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). When moving a server from one group to another, you have to define the access rights as well as the protocols and ports used for the individual modules.
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. g. passwords and possibly also protocols and port numbers. To manage a PRIMERGY rack server, you have to access the iRMC of this server. To access the iRMC you must specify user name and password. 1.
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. You can have the same user name and password for all components or different ones for each. You must specify this accordingly in this dialog box. 4.
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 PRIMERGY rack servers), which VIOM can use to access these components.
7.3 Deactivating management with VIOM 7.3 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. 2. Click Unmanage on the Setup tab. 3.
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 management blade of the chassis that this chassis is managed by this installation of the Virtual-IO Manager. This information in the management blade is always checked before a chassis is added in the VIOM management.
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.
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. Only the first uplink port has an external connection. To enable you to configure the IBP module, the network to which the central management station is connected must be connected to this first uplink port.
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: 1.
7 Managing servers with VIOM 7.5 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 PRIMERGY rack server, the following actions occur internally: 1. The PRIMERGY rack server is indicated as “managed” by this VIOM installation.
7.5 VIOM-internal operations on a PRIMERGY rack server The iRMC has limited storage to store multiple trap destinations. 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.
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 avoided and a normal boot performed instead. This option is available in the VIOM user interface when assigning a profile: option Power On after Assign. All the VIOM-specific initialization is also performed during a normal boot.
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” which is also displayed in the VIOM user interface on the Server Configuration tab in the table column state.
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 (inventory 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.
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.
7 Managing servers with VIOM Select VIOM in the Advanced menu and set the VIOM-flag from Enabled to Disabled: 272 ServerView Virtual-IO Manager
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 virtualization data, and the inventory data are cleared. But please note that the iRMC configuration of the VIOM management station as an SNMP trap destination is not removed by this process.
7 Managing servers with VIOM VIOM-internal operations during deactivation When you deactivate management with the Virtual-IO Manager for a PRIMERGY 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. 2. If a VIOM server profile is assigned to this server, the server profile is internally unassigned and the VIOM virtualization data is deleted in the iRMC. 3.
7.6 Displaying license information 7.6 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. Click OK to close the Licenses Information dialog box.
ServerView Virtual-IO Manager
8 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. Defining these types of network paths on an IBP module includes the following steps: l Defining an uplink set. An uplink set contains a number of uplink ports.
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 chapter "Viewing the blade server configuration" on page 301). 8.1 Defining an uplink set To define an uplink set, follow the steps below: 1. You can start the Create network wizard by: l clicking New on the Graphic or Details tabs on the Ext. LAN Connections tab l selecting New Uplink Set in the context menu of an uplink set.
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 configure an internal network without a connection to an uplink.
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. By grouping several active uplink ports in an uplink set and assigning an uplink set to a network, a link aggregation group (LAG) can be formed.
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. 5. Under Ports for the uplink set, select the uplink ports that should belong to this uplink set. An uplink port can be included in the port group as an active port or as a backup port.
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 wizard opens. In this step, you can specify the CNA parameters. 8. Click Finish to confirm your entries. A network is created with the configured uplink set. The new network is added to the tables on the Graphic and Details tabs.
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. Under Ports for the uplink set, select the uplink ports that should belong to this uplink set. An uplink port can be included in the port group as an active port or as a backup port.
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. The networks on an uplink set must have different VLAN IDs. In contrast, however, two networks on two different uplink sets can use the same VLAN ID. These networks are still completely separate from one another. 9.
8.2 Modifying an uplink set For further information on defining networks, see section "Defining networks (LAN) (for blade servers only)" on page 30. 8.1.4 Defining a dedicated service network Defining a dedicated service network is mostly the same as defining a single network. For further information, see section "Defining a single network" on page 280 1. Click New on the Graphic or Details tabs or select New Uplink Set in the context menu to define a new dedicated service network.
8 Defining network paths (LAN) The name of the uplink set cannot be changed; the field is inactive. 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" on page 278). Modifying an uplink set directly in the table On the Graphic and Details tabs, you can modify the existing configurations directly via the table (with the exception of the Chassis and IBP columns on the Details tab).
8.4 Copying an IBP configuration A message appears asking whether you wish to delete the corresponding 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. 8.4 Copying an IBP configuration You have the option of copying the defined uplink sets and networks to a second IBP module. This can be useful if you use a teaming configuration for failure safety on the server blades.
8 Defining network paths (LAN) 8.5 l VIOM always copies the entire configuration irrespective of what is selected in the tables. l 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. Copying configuration You have the option of copying all defined uplink sets and networks of a chassis to another chassis. The following describes how to create a copy of all networks of a chassis on another chassis: 1.
9 Defining and assigning server profiles To use address virtualization or to enable a server blade to use a defined network, 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-specific input/output parameters and the input/output connections.
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. 9.1 Defining server profiles To define a server profile the Create Server Profile wizard is used. This wizard can be opened from two views: Profiles view 1.
9.1 Defining server profiles 5. Once you have entered all the required data, click Next to go to the Configure Cards step of the wizard. 6. Select the type and number of onboard IO channel in the Configure Cards step. 7. Optional: Add mezzanine/PCI cards to the appropriate slots and select the type and number of IO channels for each card. You can move a card to another slot by using the arrow buttons on the right.
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 networks on these modules. To enter a network name, click the table cell to switch to edit mode. You can also open a network selection dialog box via the "..." button.
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. If you configured several boot devices or one boot device that requires additional parameters, the next step is the Boot Parameter step. In this step, you specify the boot order and boot parameters for each port.
9 Defining and assigning server profiles 19. Once you have entered all the required data, click Next to go to the Confirm step of the wizard. 20. Use this step to check the entries you have made once again. 21. If the server profile definition is okay, click Finish to exit the wizard. In this case, the server profile is created and saved in the server profile repository. The new server profile is now shown in the Server Profiles view. 9.2 Viewing server profiles You can view a server profile definition.
9.4 Copying server profiles 2. Select the required profile in the area on the right of the ServerView Virtual-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. The Edit Server Profile wizard is the same as the Create Server Profile wizard. For a more detailed description of the wizard, see section "Defining server profiles" on page 290.
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. 9.5 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. Click Profiles, if applicable. 2. Select the required profiles in the area on the right. 3.
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. For blade servers, you can also assign the server profile to an empty slot. 5.
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. In this case you must confirm that you still want to assign the server profile to this slot.
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 Shutdown or by selecting Shutdown in the context menu. You can update the display in the State column by clicking Update States button or with Update State in the context menu. 6.
ServerView Virtual-IO Manager
10 Viewing the blade server configuration 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. 3. Click an uplink port, a network or a bay to select it.
ServerView Virtual-IO Manager
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. These backup files contain the configurations (networks, uplink sets, assigned profiles, spare slot definitions) of one or several chassis and/or profiles.
11 Saving and restoring l Select an existing file from the list that will then be overwritten. l 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). If the required directories do not yet exist, they are created automatically. The backup files are assigned the .xml suffix automatically if you have not specified one. 6.
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: l Select Restore file from Management Station to select a backup file from the management station. l Select Restore local file to select a file on the computer on which the GUI runs 5. When you click Restore file from Management Station, you select a backup file from the list on the management station. 6.
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 reassigned profiles option. If you do not select this option, all existing profiles are deleted before the configuration is restored. 4.
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 available if the backup contains profiles. If the option to restore profiles is not selected, this is performed automatically when you select the Restore only reassigned profiles option. 4.
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. Select Delete Configuration to delete backup files you no longer need on the central management station. The second step Select File in the Delete Backup Files wizards opens. 3. Select the files you want to delete on the management station.
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. In this case, the Virtual-IO Manager recognizes that a new connection blade has been inserted in the managed blade server chassis.
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 profile to a server blade slot. In this case, the following errors may occur: l The configuration of one or several IBP modules is not correct.
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: l The configurations saved in the Virtual-IO Manager are performed again accordingly for all the IBP modules in the chassis.
ServerView Virtual-IO Manager
12 Importing and exporting server profiles 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. The format of the exported files or the files to be imported is described in section "Format of export files" on page 314. 12.1 Exporting server profiles To export server profiles, proceed as follows: 1.
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: … 12.3.
12.3 Format of export files The Objects element contains the following elements: l UserInfo (optional) l 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 attribute is specified, it overwrites the value from the Objects element.
12 Importing and exporting server profiles existingAddressAction Specifies the response if a virtual address is already in use. For individual 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). New A new address is allocated for each affected IO channel. NewForAll New addresses are assigned for all IO channels of the profiles.
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. Possible values are: Refuse Handled in accordance with the current error behavior (see errorAction). Replace The existing server profile is replaced if it is not assigned.
12 Importing and exporting server profiles ServerProfileName Name of the server profile. IOVirtualizationUsage Yes The profile uses virtual addresses. You must specify the AddressVirtualization element in all IOChannel elements of this profile. No The profile does not use any virtual addresses. You must not specify the AddressVirtualization element in any IOChannel element of this profile. BootMenuUsage Yes The VIOM boot settings can be overwritten on your local computer.
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.
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 OnBoard DaughterCard Mezzanine card AddonCard PCI card IOBoardNumber Number of the board to which the port belongs: always 1 for OnBoard, 1 or 2 for mezzanine cards, and 1 to 14 for PCI cards.
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 TaggedName elements: NetworkName Optional, must not be specified for FC ports or for PRIMERGY rack server profiles. Network name. If you want to use the profile on blade servers with IBP modules, you can specify a network.
12 Importing and exporting server profiles BootDeviceUsage Indicates whether the port is used as a boot device. Yes The port is a boot device and the BootEnvironment element (see below) must be specified. No The port is not a boot device and the BootEnvironment element (see below) must not be specified. BootEnvironment optional Specifies the boot settings for this port; it is described below. This element must be specified if BootDeviceUsage has the value Yes (see above).
12.3 Format of export files FunctionConfiguration optional Specifies the configuration for a function (see " The FunctionConfiguration 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-function must have the attribute purpose="fcoe". Each other Address element must have the attribute purpose="normal".
12 Importing and exporting server profiles l 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. ISCSIBootConfiguration Specifies that the port is an iSCSI boot device. You can only specify this element for LAN ports. The elements contained in this element are described below.
12.3 Format of export files No 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. It should be specified only for CNA-iSCSI-functions. IPv4Address Only when DHCPUsage is No The static client IP address to be used for this port. The port will use this IP address for the entire iSCSI session.
12 Importing and exporting server profiles DHCPUsage Yes 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. No You must specify a static name for the iSCSI target, a static IP address for the iSCSI target, a static IP port number, and a static SCSI LUN ID. Name Only when DHCPUsage is No The IQN name of the iSCSI target.
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. The name must be identical to the name configured on the iSCSI target. ChapSecret Not when AuthenticationMethod is None The CHAP password.
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. FCLinkSpeed Specifies the transmission speed used by this port.
12.3 Format of export files 4 Point-to-Point 8 auto (Point-to-Point first) 12 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; default for FCoE is 3, default for iSCSI is 4. Possible values are 0 to 7. 12.3.
ServerView Virtual-IO Manager
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.
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 Shutdown or by selecting Shutdown in the context menu. You can see the state of a server blade in the State column. To see the current power state, you may need to update the display using the Update States button or with Update State in the context menu. 6.
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 Failover function in the context menu of the affected server blade on the Server Configuration tab. In this case, VIOM searches for the slot configured as a spare slot.
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 management station, which is typically not the case in such a disaster scenario.
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 (containing 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 virtual addresses as soon as the failed site goes online again.
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. This setting prevents a failed site from automatically booting the server blade after AC power becomes available again.
14 VIOM database This chapter describes the VIOM database on a Windows- or Linux-based CMS. The Virtual-IO Manager requires two databases: l The ServerView database, which is installed with ServerView Operations Manager, and l The VIOM database, which is installed with VIOM. Both databases should be regularly backed up. The ServerView database is backed up independently of the VIOM database.
14 VIOM database "Installing ServerView Operations Manager Software under Linux - Installation Guide". 14.1 VIOM Backup Service The Backup Service of the Virtual-IO Manager is a service used to periodically back up the VIOM database. Note that its sole purpose is currently to back up the VIOM database, whereas the backup of ServerView database is done by ServerView itself. But a backup of the VIOM database will be of little use if the ServerView database is lost.
14.1 VIOM Backup Service The following parameters need to be configured for the backup jobs: l 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.
14 VIOM database Trigger description relating to the full backup job in the quartz_ jobs.xml file cronFullBackupJobTrigger MSSQL-cron FullBackupJob MSSQL 0 0 19 ? * FRI The trigger description above only belongs to the job called FullBackupJob of SQL Server. There are also trigger descriptions for the IncrementalBackupJob and BackupLogJob jobs.
14.1 VIOM Backup Service Field Mandatory Values Month yes Special characters 1 - 12 or JAN - DEC , - * / Day of Week yes 1 - 7 or SUN - SAT , - * / ? L # Year 1970 - 2099 no ,-*/ Table 5: Fields of a Quartz cron expression Example A simple example would be: 0 0 19 24 DEC ? 2010 This cron expression would trigger a backup job at 7.00 p.m. on 24.12.2010.
14 VIOM database Special Description characters Example Meaning of the example ? Day of month and day of * * * ? * MON 2010 week must not be given a value at the same time, so use the question mark for the unspecified field of the two Every second on all Mondays in 2010 L Last day of month 008L*? At 8.00 a.m.
14.1 VIOM Backup Service For PostgreSQL: If the schedule does not suit your needs, you should edit the Quartz cron expression: PostgresJobTrigger Postgres-cron … PostgresJob Postgres 0 0 19 ? * FRI 14.1.3 Configuring the output directories To configure the output directories for the backup jobs, you must open quartz_job.xml (e.g.
14 VIOM database l 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. 14.1.4 Starting the Backup Service on Windows When you have configured the Backup Service you must start the ServerView Virtual IO DB Backup Service. 1.
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 information 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 backups. You must not delete the current VIOM database or the errored VIOM database.
14 VIOM database Stop the services ServerView Virtual IO Manager Services and ServerView 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. Restrict the access to the VIOM database: 1. Start SQL Server Management Studio. 2. Connect with the SQL Server instance and select Databases – ViomDB. 3. Select Properties from the context menu. 4.
14.2 Restoring the VIOM database on Windows 2. On the General page, enter the name ViomDB or master in the To database field or select the name from the list. 3. Select the option From device. 4. Click the ... button. 5. Add the database backup ViomDBData.bak from the appropriate storage location and then click OK. 6. Select the database backup to be restored: In Select the backup sets to restore, click the box in the Restore column. 7. Switch to the Options page. 8.
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 context menu. The Restore Database window opens. 2. On the General page, in the To Database field select the name ViomDB from the list. 3. Select the option From Device. 4. Click the ... button. 5. Add the transaction log file ViomDBLog.
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. 14.2.2 Restoration via Enterprise Manager Enterprise Manager may be used for SQL Server 2000 to restore the VIOM database.
14 VIOM database Make all other entries as described in the relevant sections. Afterwards, the database should have been restored under the name RECOVERYTEST. You can check this as follows: 1. Click the SQL Server instance and select Databases. 2. Select Refresh from the context menu. The database RECOVERYTEST must be displayed in the list. You can then delete the database RECOVERYTEST as follows: 1. Select the database and then select Drop from the context menu. 14.
14.3 Restoring the VIOM database on Linux 5. Start the VIOM Backup Service: /etc/init.
ServerView Virtual-IO Manager
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 ports in the new IBP module at the end of the procedure.
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 Operations Manager (menu item of the context menu in the ServerList window) for the related blade server chassis and wait until this action is complete. 6.
15.
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:0
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: \plugins\viom\Manager\logs\viom-manager.
15 Appendix After modifying the StartOptions property in the ViomConfig.properties file or the MaxBackupIndex property in the man-log4j.properties file , the service ServerViewVirtualIOManagerService must be restarted. (Note: The display string of this service is: ServerView Virtual IO Manager Service.) You can also activate the trace functionality for the VIOM provider of the ServerView Connector Service (SCS). To do so you must modify the file \ViomAPI.xml.
15.4 Event logging For how to collect diagnostic data on a Linux operating system, see the chapter "Collecting diagnostic information" on page 89. 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. In the Preferences dialog box, select the Trace tab. There select the option Write trace messages to file and enter a file name in the File name input field and change the Max.
15 Appendix l For Linux Virtual-IO Manager events are output to the system log with source VIOM-MAN, VIOM-LICENSE-MANAGER, and VIOM-BACKUPSERVICE. The event logs for errors are self-explanatory and not listed here. Informational events that describe changes to the configuration are shown in the following table. The log entries contain more information (e.g. names of involved uplink sets or nodes) than listed in the Meaning column.
15.4 Event logging Event Meaning ID 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. 51100 Virtual-IO Manager launched successfully. 51217 Node has been restored to ServerView Virtual-IO Manager database configuration.
ServerView Virtual-IO Manager
