Fujitsu Technology Solutions GmbH

ServerView Virtual-IO Manager for PRIMERGY
Version 3.1 (3.1.04)
February 2013

Release Notes

© Fujitsu Technology Solutions 2013
All rights reserved

Designations used in this document may be trademarks, the use of which by third parties for their own purposes could violate the rights of the trademark owners.

Contents:

1 General

This Release Note is a summary of the major extensions, dependencies and operating information with respect to ServerView Virtual-IO Manager under the approved Windows operating systems.

1.1 Ordering

ServerView Virtual-IO Manager can be ordered from your local distributors.
ServerView Virtual-IO Manager is subject to the general terms and conditions of the Fujitsu Technology Solutions GmbH software product use and service agreement.

1.2 Delivery

The product ServerView Virtual-IO Manager is supplied on the ServerView Software CD which can be ordered with the order number U15000-C289.
The installation of ServerView Virtual-IO Manager requires the input of a license string which must be ordered separately together with a service contract.
Updates, patches and fixes can be obtained at the downloaded area of http://support.ts.fujitsu.com.

1.3 Documentation

The following documentation is available for ServerView Virtual-IO Manager:

• ServerView Virtual-IO Manager V3.1 User Guide, October 2012
• ServerView Virtual-IO Manager Command Line Interface V3.1, October 2012

For an understanding of the operations and a secure usage the following documentation of the ServerView Suite is also recommended:

• Basic Concepts, July 2009
• Documentation Overview
• Secure PRIMERGY Server Management - Enterprise Security, May 2009
• ServerView Installation Manager, January 2011
• ServerView Operations Manager 5.50 – Installation under Windows, November 2011
• ServerView Operations Manager 5.50 – Installation under Linux, November 2011
• ServerView Operations Manager 5.50 – Server Management, November 2011
• BIOS Integrated iSCSI Boot for PRIMERGY Server Installation and Configuration, November 2008

These documentations are available at the ServerView Suite DVD 2 or online at http://manuals.ts.fujitsu.com at the link "Industry standard servers". They may be supplemented with Chapter 6 of these release notes which contains changes and extensions to the manual of the product concerned.
A German version of the manual is available at the ServerView Suite DVD 2.

1.4 License Terms and Conditions

This software is subject to the software product use and service agreement: "General Software Terms and Conditions of the Fujitsu Technology Solutions GmbH".
The respective document "eula_en_V2.pdf" can be found on the ServerView Software CD.

2 System Requirements

2.1 Delivery Units

ServerView Virtual-IO Manager is delivered as part of the PRIMERGY ServerView Suite DVD 1. The installation package SV_VIOM.exe is used for 32 bit Windows X86 systems and for 64 bit Windows X64 systems.

2.2 Required Hardware

For the installation of ServerView Virtual IO Manager the following minimal hardware is required:

These values represent a minimum requirement that may increase depending on the amount of data used.

The MAC and WWN Virtualization feature strongly depends on corresponding features in MMB, server blades and daughter cards.
The following blade server components are supported:

BX600 Blade Server with the following configuration:

BX900 Blade Server with the following configuration:

BX400 Blade Server with the following configuration:

PRIMERGY Rack Server configuration:

Supported PCI Controller:

A BX400, BX600 or BX900 system fulfilling the above requirements can be managed by ServerView Virtual-IO Manager, if the network settings of the MMB and all LAN connection blades are correctly setup, so that these blades can be reached from the management station by telnet or SSH and SNMP.
The BX400, BX600 or BX900 blade system must also be a member in the ServerView server list.
For BX600 IBP connection blade in addition the network that connects the management station with the IBP connection blades must be connected to the first uplink port of the IBP connection blades. This is port 0/11 for IBP 10/6 and port 0/31 for IBP 30/12.
The BX400 and BX900 connection blades must have an IP address configuration for the Out-of-Band (oob) management of these connection blades and must be reachable from the management station by this management port by telnet or SSH (telnet or SSH must be enabled). The usage of the in-band management protocol for BX400 or BX900 connection blades in IBP mode is not supported.
In order to use SSH connection to IBP connection blades the "Administrative Mode" for SSH connection must be enabled, by default it is disabled and at least one of SSH version 1 or 2 must be enabled.

2.3 Required Software

The ServerView Virtual-IO Manager can be installed under:
WINDOWS:

• Microsoft Windows Server 2003
• Microsoft Windows Server 2003 SP1
• Microsoft Windows Server 2003 SP1 X64
• Microsoft Windows Server 2003 SP2
• Microsoft Windows Server 2003 SP2 X64
• Microsoft Windows Server 2003 R2 (including SP1 and SP2)
• Microsoft Windows Server 2003 R2 X64 (including SP1 and SP2)
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 (X64)
• Microsoft Windows Server 2008 R2 (X64)
• Microsoft Windows Server 2008 R2 SP1
• Microsoft Windows Server 2012

LINUX:

• Novell (SLES10), SP2, SP3, SP4 (32bit and 64 bit)
• Novell (SLES 11), SP1 and SP2 (32 bit and 64 bit)
• Red Hat RHEL 5.6, 5.7, 5.8, 5.9 (32 bit and 64 bit)
• Red Hat RHEL 6, 6.1, 6.2, 6.3 (32 bit and 64 bit)

The following software packages must be available on the central management station:

• A standard Windows Server or LINUX platform (see list above)
• ServerView 5.50.13 or higher
• Java Runtime Environment 6.0 (update 26 or higher; Note: update 29 is not supported) or Java Runtime Environment 7.
  Java Runtime Environment 7 requires ServerView Operations Manager 6.10 or higher.

2.4 Configuration Requirements

Firewall Settings on the Central Management Station
Port 3172 must be opened for TCP/IP connection to the ServerView Remote Connector Service.

TCP/IP Connection to SQL Server
The SQL Server instance used for the ServerView database must allow TCP/IP connections.

Automatic Inventory Retrieval
The management blade must be configured for automatic inventory boot. If this is not configured it must be configured before managing a blade server system with VIOM and all blades must be removed and reinserted after this. You check the parameter setting in the Remote Manager of the management blade by choosing
(1) Management Agent – (3) System Information – (11) Automatic Inventory Retrieval.

Stacking for "PY CB Eth Switch/IBP 1Gb 36/8+2" connection blades
Virtual-IO manager supports stacked "PY CB Eth Switch/IBP 1Gb 36/8+2" connection blades in IBP mode only in a single chassis. A stack must not use "PY CB Eth Switch/IBP 1Gb 36/8+2" connection blades connection in multiple chassis.

3 Changes

Changes with version 1.1

• Version 1.1 of Virtual-IO Manager supports the so called "open fabric" mode. This means that Virtual-IO Manager V1.1 allows managing BX600 chassis that do not have IBP connection blades. In this case only the virtualization of MAC and WWN addresses and the setting of boot options for server blades are supported.
• The configuration of connection blades other than IBP connection blades is not supported.

Changes with version 2.0

• Version 2.0 of Virtual-IO Manager supports the BX900 blade server system.
• It allows defining 2 mezzanine cards to a server profile. Mezzanine cards can be of type LAN or Fibre Channel.
• Note: Since virtualization of the MAC addresses of a LAN daughter card in a BX600 blade is not supported, server profiles with IO virtualization and a LAN mezzanine card cannot be used on a BX600 system.

Changes with version 2.0.05

• ServerView Operation Manager 4.90 or higher is required.
• The installation of the ServerView agents on the management station is no longer required.
• There is only one installation package SV_VIOM.exe used for 32 bit Windows operating system and 64 bit X64 Windows operating system. The separate X64 installation package SV_VIOM_X64.msi is no longer supported.
• The default installation directory is changed to the directory "C:\Program Files\Fujitsu\ServerView Suite\VIOM Manager".
• The display string of the ServerView Virtual-IO Manager service is changed to "ServerView Virtual IO Manager Service"

The following two bugs have been fixed:

• when a storage blade was re-plugged into another slot it appeared twice in the node list
• when a CPU blade was re-plugged into a different blade server, the VIOM manager threw an exception

Changes with version 2.1
The following additional hardware is supported:

• BX922 S2 server blade
• SB11 connection blade in switch or IBP mode; but only not stacked. Multiple connection blades in one stack are not supported by Virtual-IO Manager.
• Fibre Channel Pass Through connection blades

The following new functionality is supported:

• iSCSI boot configuration in VIOM profile (supported by BX920 S1, BX922 S2 and BX620 S5 with BIOS and iRMC firmware update)
  Note: iSCSI boot must not be configured for LAN ports of mezzanine cards.
• Definition of MUX setting for the second LAN mezzanine card
• Manual definition of virtualized addresses in VIOM profile wizard
• Export and import of VIOM server profiles. Exported VIOM server profiles are described in XML. The corresponding XML schema is described in the file ViomObjects-V2.1.xsd which is part of the installation and can be found in the directory <INSTALL_DIR>/soap.
• The action "Collect Log Files" in the "Start" menu (Start -> All Programs -> Fujitsu ServerView Suite -> Virtual-IO Manager -> Collect Log Files) creates a ZIP archive with log files from Virtual-IO Manager, VIOM database information and log files from ServerView Server - List service.

Changes with version 2.2
The following additional hardware is supported:

• BX920 S2 server blade
• BX924 S2 server blade
• PY CB Eth Switch/IBP 10Gb (SBAX2)
• Support for 10 GB mezzanine card ("PY Eth Mezz Card 10Gb 2 Port Niantic") with MAC address virtualization and iSCSI boot configuration.
• BX620 S5 server blade
• BX620 S6 server blade

The following new functionality is supported:

• Configuration of "Dedicated Service Networks" and "Service VLAN Networks". Details about the behavior of "Dedicated Service Networks" and "Service VLAN Networks" are described in the ServerView Virtual-IO Manager User Guide. The VIOM server profile wizard allows to specify these network types in addition to the network types "Single Network" and "VLAN Network".
• Backup service for the database of the Virtual-IO Manager. With Virtual-IO Manager V2.2 a separate service is installed that is responsible for periodic backups of the Virtual-IO Manager database. The service is not started automatically. Before starting the service it needs to be configured to fit the requirements of the administrator. After this the start mode of the service should be changed from "manual" to "automatic" and the service should be started. More details about the backup service, it’s configuration and how to restore the VIOM database from a backup are described in the ServerView Virtual-IO Manager User Guide.

Changes with version 2.3

• Supports and requires ServerView Operations Manager 5.0.
• The installation location changes to <ServerView Suite>\plugins\viom where <ServerView Suite> is the "ServerView Suite" directory from the installation of ServerView Operations Manager.

The following new functionality is supported:

• Stacked SB11 connection blades in IBP mode.
• Support definition of server profiles for double height server blades (like BX960)
• Copy network configuration to another chassis
• Japanese language support. (Language depends on language of ServerView Operations Manager)
• The name of the service is renamed to "ServerViewVirtualIOManagerService".

Changes with version 2.4
The following new functionality is supported:

• Support of BX400 blade server chassis
• Support of "PY CB Eth Switch/IBP 1Gb 18/6" (SB6) connection blades
• New license model. Starting with VIOM 2.4 each assigned server profile occupies a VIOM license. Old license strings are still supported; the number of manageable chassis in an old license string is multiplied by 18 in order to define the number of assignable VIOM server profiles.

Changes with version 2.4.05
The following bugs are fixed:

• Avoid 1 second delay when sending a VIOM request from web service to Virtual-IO Manager service.
• The VIOM GUI of version 2.4.04 displayed a connection blade in bay 1 as connection blade 2 and a connection blade in bay 2 as connection blade 1. The connection blades 3 and 4 were not handled correctly similarly. When selecting the connection blade in bay 1 (shown as connection blade in bay 2) the connection blade 2 was configured in reality. This incorrect display is corrected with version 2.4.05
• When selecting BX960 as blade type a profile with 8 onboard LAN ports is created by default (4 onboard LAN ports on the main slot and 4 onboard LAN ports on the lower slot). This is incorrect. With version 2.4.05 only 4 onboard LAN ports will be created by default.
• When an IBP connection blade is removed and inserted again while the Virtual-IO Manager GUI was running, Virtual-IO Manager reported the error status wrong model for this connection blade and only deletion of the network configuration was possible. This is not correct. Virtual-IO Manager should report a possible configuration mismatch and restoring the configuration should be possible. This is solved with version 2.4.05
• When two or more SB11 IBPs are configured to form a stack group, the VIOM manager sporadically might hang up and cause a database lock.

Changes with version 2.6
The following new functionality/hardware is supported:

• Installation of ServerView Virtual-IO Manager on a management station under LINUX operating system
• The 10 GB Ethernet LAN Pass Thru module is supported
• Support for Converged Network Adapter (CNA) mezzanine card PY CNA Mezz. Card 10Gb 2 Port (MC-CNA102E). With version 2.6 it is possible to select the mezzanine type CNA in the profile wizard. In case of a CNA mezzanine card it is possible to configure 2 physical functions per physical port of the adapter, 1 LAN function and 1 storage function. The storage function can be of type FCOE or of type iSCSI.
• Support of a new version server inventory information. New system BIOS versions are able to support a new version of the inventory information. The MMB property systeminfo/ViomPreferredInventoryVersion contains the information which version of this inventory information is preferred by the Virtual-IO Manager that manages this blade server chassis. By default the value is "2.0". For ServerView Virtual-IO manager 2.6 the preferred version for the inventory information is "2.5". When performing an update installation, Virtual-IO manager changes the value of systeminfo/ViomPreferredInventoryVersion to the value "2.5" and performs a so called "Inventory Boot" for all blades, that are currently powered off. Also Virtual-IO manager checks the value of systeminfo/ViomPreferredInventoryVersion when managing a chassis and sets the value to "2.5" if necessary. If this happens also this "Inventory Boot" is executed for all server blades. Whether a blade supports the new inventory version depends on the BIOS version. This means that the "Inventory Boot" is also necessary when updating the BIOS version to a version that supports newer version of the inventory and if new functionality should be used. The new inventory version 2.5 used by Virtual-IO manager 2.6 is necessary in order to support CNA controllers. The Virtual-IO manager user interface allows to perform an Inventory Boot for selected blades manually.
  Note: Virtual-IO manager 2.6 also supports older inventory version, but with the older inventory version no CNA support is possible.
  When downgrading the Virtual-IO manager installation to a lower version (ex. 2.4) the MMB property systeminfo/ViomPreferredInventoryVersion od all chassis that were managed by a Virtual-IO manager version 2.6 needs to be checked and set to version "2.0" manually. Also an Inventory Boot for all blades should be performed manually.
• Support for ETS/PFC settings in "PY CB Eth Switch/IBP 10Gb 18/8" connection blades in IBP mode.
  ETS: Enhanced Transmission Selection (IEEE 802.1Qaz)
  PFC: Priority-base Flow Control (IEEE 802.1Qbb)
• Support "isolation" of downlink ports. This feature can only be configured for networks defined in a "PY CB Eth Switch/IBP 10Gb 18/8" connection blade in IBP mode. If this feature is enabled for a network server blades using the same network cannot communicate between each others, although they are using the same network. They are "isolated" from each other for this network.
• Automatic restart of ServerView Virtual IO manager service and backup service in case of failure. Details about the restart behavior are described in the manual chapter "High Availability Support".
• Support for a high available management station based on a Windows 2008 R2 Hyper-V cluster and VIOM installed together with ServerView Operations Manager on a virtual machine with Windows OS running on this Hyper-V cluster. Details about the supported configurations are described in the manual chapter "High Availability Support".
• With version 2.6 it is possible to configure a virtual MAC address or a virtual FC address outside of the configured address ranges for virtual addresses.
• Support of the single sign on environment in ServerView Suite. With version 2.6 an additional logon with a user account defined in the operating system of the central management station is no longer necessary. In order to work with Virtual-IO Manager the credentials of a user account with the privilege "AccessVIOM" (by default assigned to the security role "Administrator") as defined in the ServerView Suite central authentication service must be used. Only a user with the "AccessVIOM" privilege can connect to the Virtual-IO Manager service.

Changes with version 3.0
The following new functionality/hardware is supported:

• Manage PRIMERGY rack servers. RX200-S7, RX300-S7 and TX300-S7 are supported
• Support BX920-S3 and BX924-S3
• Support "PY CNA Mezzanine Card 10 Gb 2 Port (MC-CNA112E)" in BX920-S3 and BX924-S3
• Support BX900S2 chassis

Changes with version 3.1.03
The following new functionality/hardware is supported:

• Support the configuration of multiple VLAN groups in tagged mode in VIOM server profile.
• Optionally allow DCB settings for iSCSI function in VIOM server profile.
• Support JAVA 7 runtime environment (requires ServerView Operations Manager 6.10 or higher)
• Support PCI LAN controller D3035 for Rack Server (2 x 1 GbE)
• Support PCI LAN controller D3045 for Rack Server (4 x 1 GbE)
• Support 2 x 10 GbE 10BaseT PCI LAN controller for Rack Server
• Start Video Redirection to selected Rack Server or selected server blade from VIOM user interface (setup tab or server configuration tab)
• The connection Blade "PY CB 10Gb FEX Nexus B22 (Cisco)" is recognized as supported component. This connection blade is handled in transparent mode by VIOM.

Changes with version 3.1.04
The following problems are solved with VIOM 3.1.04:

• When restoring the configuration of a SBAX2 connection blade (IBP mode) with networks where DCB usage is enabled, for uplink ports of
• Optionally allow DCB settings for iSCSI function in VIOM server profile.
• Support JAVA 7 runtime environment (requires ServerView Operations Manager 6.10 or higher)
• Support PCI LAN controller D3035 for Rack Server (2 x 1 GbE)
• Support PCI LAN controller D3045 for Rack Server (4 x 1 GbE)
• Support 2 x 10 GbE 10BaseT PCI LAN controller for Rack Server
• Start Video Redirection to selected Rack Server or selected server blade from VIOM user interface (setup tab or server configuration tab)
• The connection Blade "PY CB 10Gb FEX Nexus B22 (Cisco)" is recognized as supported component. This connection blade is handled in transparent mode by VIOM.

4 Product Installation, Configuration and Start-up

The installation package SV_VIOM.exe is used for 32 bit Windows X86 systems and for 64 bit Windows X64 systems. (Note: IA64 architecture is not supported).
The LINUX installation packages can be found in the ZIP archive VIOM_3.01.04_<build_date>.zip (<build_date> is the date when the package was created). For hints how to install ServerView Virtual-IO Manager on LINUX operating system please look and the ServerView Virtual-IO Manager User Guide chapter "Installing the Virtual-IO Manager on a Linux-based CMS".

Before installing ServerView Virtual-IO Manager the following software must be installed:

• Java Runtime Environment 6.0 (update 25 or higher with exception of update 29) or Java Runtime Environment 7.0
• ServerView 5.50.13 or higher

ServerView Virtual-IO Manager requires a license, which contains the numbers of server profiles that can be assigned to server slots. During installation the license manager is called where one or more licenses can be registered. If you want to add/remove licenses later you can call the license manager at any time out of the start menu. A wrong license string is detected when the service "ServerViewVirtualIOManagerService" with display string "ServerView Virtual IO Manager Service" is started. The service "ServerViewVirtualIOManagerService" does not accept commands when a wrong license is specified. In order to solve this, a correct license must be specified via the license manager of ServerView Virtual-IO Manager.

Important note: If you have already used a ServerView Virtual-IO Manager GUI other then version 3.1.0x please clear the cache of the JAVA virtual machine. If this is not done it might happen that an older version of the GUI is loaded in the browser. In that case the displayed version for the VIOM GUI will not be same as the actual version 3.1.0x of ServerView Virtual-IO Manager.

Java security warning dialog
When the Virtual-IO Manager user interface is opened, the following Java security warning dialog might be displayed:
=======================================================
Warning - Security

Java has discovered application components that could
indicate a security concern.

Name: ViomApplet

Block potentially unsafe components from being run? (recommended)
More Information...
[Yes] [No]
------------------------------------------------------
The application contains both signed and unsigned code.
Contact the application vendor to ensure that it has
not been tampered with.
=======================================================
This warning dialog must be answered with "No".
To prevent the warning message dialog, the option "Enable - hide warning and run with protections" has to be set in Java Control Panel as described in http://download.oracle.com/javase/6/docs/technotes/guides/jweb/mixed_code.html#jcp.

Growing Transaction Log File
It is a known behaviour of Microsoft SQL Server that the transaction log grows unless it is periodically saved away. We thus strongly recommend configuring and starting the Backup Service in order to backup at least the transaction log. Also the start behaviour of the Backup Service should be changed to start automatically.

Update installation When updating ServerView Operation Manager from version 4.92 to version 5.00 or higher, an installation of previous Virtual-IO Manager versions will no longer work. Directly after update of ServerView Operation Manager the Virtual-IO Manager must be updated to version 2.6. The update is only possible from version 2.2.
Important note: Before updating ServerView Operations Manager to version 5.00 or higher, VIOM must be updated to version 2.2.
Before updating ServerView Virtual-IO Manager it is recommended to save the current VIOM configuration and also to create a backup of the VIOM database (see description of VIOM backup service in the VIOM manual).

Command line options for Windows installation
Since VIOM 2.4 command line installation is supported and installation parameters like address ranges and VIOM license can be specified by command line.
The following syntax is supported:

SV_VIOM.exe /q [DO_ADDRESS_RANGE_SELECTION=%Value1%] [MAC_RANGE=%Value2%] [MAC_START="%CustomValue%"] [MAC_END="%CustomValue%"] [WWN_RANGE=%Value3%] [WWN_START="%CustomValue%"] [WWN_END="%CustomValue%"] [DEBUG_MODE=%Value4%] [VIOM_LICENSE_KEY = "key value"]


DO_ADDRESS_RANGE_SELECTIONvalue should be:

MAC_RANGEvalue should be:

MAC_START and MAC_END values must be in hex. Format "11:22:33:44:55:66".

WWN_RANGEvalue should be:

WWN_START and WWN_END values must be in hex. Format "11:22:33:44:55:66:77:88".

DEBUG_MODEvalue should be:

Examples:
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
SV_VIOM.exe /q MAC_RANGE=MAC78 WWN_RANGE=WWN8 VIOM_LICENSE_KEY =abcdef
SV_VIOM.exe /q DO_ADDRESS_RANGE_SELECTION=false VIOM_LICENSE_KEY =abcdef


5 Product Specific Issues

5.1 General Issues

Before updating or un-installing ServerView Operations Manager the service "ServerViewVirtualIOManagerService" with display string "ServerView Virtual IO Manager Service" should be stopped and restarted after update of ServerView Operations Manager finished.

When a blade server chassis containing IBP connection blades is managed by VIOM, the configuration of these IBP connection blades must not be changed by direct access (CLI or Web interface) for these connection blades. This restriction avoids inconsistencies in the server management software stack.

When assigning a server profile with virtual I/O addresses to a BX600 server blade (this note is not relevant for BX900) the virtual MAC addresses of the onboard LAN ports are stored in the NVRAM of the LAN chips. When removing these blades and inserting the blades to a different BX600 chassis or a different slot it might happen that the management blade of the chassis where the blade is inserted, still shows the "old" virtual MAC addresses that were assigned to the blade when the blade was in the previous chassis/slot. This happens when there is no ServerView Virtual-IO Manager server profile assigned to the slot, into the blade is inserted or when the blade is inserted into a chassis with older management blade hardware or older MMB S3 firmware. But when the blade is powered on the next time, the BIOS of the blade will restore the original "manufacturer" MAC addresses to the LAN ports during POST. This means the blade will never make network access with the "old" virtual addresses after being moved to the new chassis or slot. In order to work around the problem that the MMB shows MAC addresses that are not used by this blade, it is recommended to power-on the blade and let run BIOS POST until OS boot. The previously used virtual MAC of this moved blade might cause problems for example when using ServerView Deployment Manager, which is using the MAC address information from the management blade.

5.2 Restrictions

Since virtualization of the MAC addresses of a LAN daughter card in a BX600 blade is not supported, server profiles with IO virtualization and a LAN mezzanine card cannot be used on a BX600 system.

iSCSI Boot via normal LAN port
iSCSI boot configuration must not be configured for LAN ports on mezzanine cards. This also means that a XML profile import file must not contain profiles with iSCSI boot configurations for LAN ports on a mezzanine card. The same is true for profiles created by the Virtual-IO manager command line interface.

Due to restriction in the iSCSI boot functionality of the supported LAN controllers the number LAN ports with iSCSI boot configuration is limited to 2 ports. In addition the iSCSI initiator name for the 2 ports must be identical. It is not possible to define different initiator names for the 2 iSCSI boot ports. When importing a profile description via Virtual-IO Manager import interface, the XML import file must not contain profiles where the iSCSI initiator names of 2 ports in one profile are not identical.

The chap user name, chap secret or mutual chap secret in the iSCSI boot configuration must not contain any UTF8 characters. Only 7 bit ASCII characters are processed correctly.

With the BX920 S1 BIOS version 3B38 server profiles that are using more than one LAN port for iSCSI boot are not working. In addition a VIOM server profile will not be working correctly when for the iSCSI boot options the target parameter "Address Origin" is set to "DHCP". With BIOS 3B38 only static configuration of the target parameters are working. All these restrictions are solved with the BX920 S1 BIOS version 3B39 (or higher).

10 GB Ethernet mezzanine and SMUX Setting
The 10 GB Ethernet mezzanine card does not support SMUX setting. Its ports are always connected to connection blade 5 and 6 in a BX900 chassis. Therefore a VIOM profile with LAN path configuration (IBP networks) for the second mezzanine card will work correctly on a blade with 10 GB Ethernet mezzanine card as second mezzanine card only when the SMUX selection is set to fabric 3 and when the configured networks also exist in the IBP connection blades 5 and 6.

BX920-S3/BX924-S3 onboard CNA controller and the MC-CNA112E mezzanine card
When configuring a profile with an I/O card of type CNA, the storage function (FCOE or iSCSI) of both physical ports must be of the same type FCOE or iSCSI.

For the BX920-S3/BX924-S3 onboard CNA controller and the MC-CNA112E mezzanine card the following configurations are possible:
(Concerning the BX920-S3/BX924-S3 onboard CNA controller it is assumed that it is not running in the mode 4 x 1 GbE due to the type of used connection blades.)

• 1 physical function: only 1 LAN function; the type of the single physical function must not be FCOE or iSCSI
• 2 physical functions: 1 LAN function together with 1 storage function (which can be iSCSI or FCOE) or 2 LAN functions
• 4 physical functions: 3 LAN functions together with 1 storage function (which can be iSCSI or FCOE) or 4 LAN functions
  In this case a VLAN ID should be configured for all physical functions of type LAN and iSCSI in the VIOM profile. Without configuration of a VLAN ID a connection might not be established. Of cause the configuration of VLAN IDs for the physical functions also requires configuration of corresponding VLAN IDs in the connected connection blade or external switch.
  (Note: The VIOM "single networks" in an IBP connection blade are VLAN transparent. Corresponding VLANs must be configured in the external switch, to which the uplink-set in the IBP is connected.)

PXE boot is only possible via the first LAN function; any additional LAN functions do not support PXE boot.

When configuring a CNA I/O card in a VIOM profile with iSCSI functions with iSCSI boot configuration for both physical ports of the CNA, the boot priority of the 2 functions at the 2 physical ports is not evaluated. The boot configuration of the iSCSI function which target can be reached first will be booted.

CNA mezzanine MC-CNA102E card
For a CNA mezzanine MC-CNA102E card the server profile wizard must always have a LAN function as first physical function and a storage function (FCOE or iSCSI) as second function. Internally the Virtual-IO manager does not have this restriction. The other interfaces of the Virtual-IO manager (for example VIOM command line interface and the profile import interface) allow the definition of profiles where physical functions are missing. Assigning such profiles to a server blade might lead to unexpected behaviour. The status of the server blade might change to VIOM_SETTING_FAILED instead of VIOM_SETTING_OK or the MMB might report "unknown type mezzanine card" as mezzanine card information. Therefore the current version of ServerView Virtual-IO manager requires that each physical port of the CNA controller must have a LAN function as first function and a storage function as second function when defining VIOM profiles by VIOM CLI or profile import interface which include a CNA mezzanine card. This requirement must be fulfilled by the user of the CLI or profile import interface.

Virtual-IO Manger allows the selection of PXE boot for the LAN function of a physical CNA port. PXE boot is currently not supported by the firmware of the "PY CNA Mezz. Card 10Gb 2 Port (MC-CNA102E)" mezzanine card. Therefore users must not define VIOM profiles, where a LAN function of CNA port is selected as PXE boot device.

When assigning a VIOM profile without CNA configuration to a server blade with a CNA mezzanine card, the 2 physical ports of the CNA are disabled. In this situation the MMB might report "unknown type mezzanine card" as mezzanine card information for the corresponding blade. In order to solve this problem the profile must be un-assigned. After this the blade must be removed and re-inserted again.

General CNA configuration:
The bandwidth parameter for an I/O channel function (CNA) must not be set to the value 0.
In addition the bandwidth parameter of a FCOE function with DCB enabled must not be set to the value 100.

iRMC Configuration of Rack Server
It is suggested to use the separate "Management LAN" configuration for the iRMC LAN connection instead of the "Shared LAN" configuration. When using the shared LAN configuration it happens that iRMC is not reachable during power on of a server for some seconds. This can influence the VIOM behavior and might cause additional error reports.

F12 Boot Menu
When a server profile is assigned to a server blade that contains configuration of a fibre channel mezzanine card and also defines a fibre channel boot configuration for this FC mezzanine card, the fibre channel option ROM might not be visible in the F12 boot menu. In addition the fibre channel option ROM might not be activated for the boot that was initiated by the F12 boot menu. This might disable installation of an operating system on the fibre channel device by using the F12 boot menu. In order to work around the problem, the fibre channel option ROM must be activated in system BIOS before assigning the VIOM server profile and the FC boot configuration of the VIOM profile must also be configured in the FC controller BIOS before assigning the profile.

Java security warning messages
When Virtual-IO Manager user interface is opened, a Java security warning messages might be displayed. For details on this issue please have a look at the "important notes" in chapter 4 of these release notes.

5.3 Important Notes

Incorrect handling of "LACP", "IGMP snooping" and "Linkdown Propagation"
With ServerView Virtual-IO Manager V2.1.04 the network properties "LACP", "IGMP snooping", "Linkdown Propagation" where not set for the corresponding uplink-sets in the IBP connection blades as defined for the network (uplink-set). This problem is solved with ServerView Virtual-IO Manager V2.3. But in order to get the correct setting in the IBP modules after an update installation of VIOM from version 2.1.04 to 2.3 (or following version) the IBP configuration must be restored ("Restore Switch" for every IBP connection blade or "Restore" for the complete chassis. Please be aware that during the restore action the network connectivity gets lost.)

ServerView Virtual-IO Manager does no longer work due to database problems when SQL Express 2008 is installed
The above problem appears in the following situation:

1. install ServerView Operations Manager with MSDE 2000 SP4.
2. install ServerView Virtual-IO Manager
3. install SQL Server 2008 Express downloaded from Microsoft download site
4. stop and start ServerView Virtual IO Manager Service. The service stops after a while.

This is a SQL Server problem. It is proposed to apply the workaround described in: http://support.microsoft.com/kb/905618/en-us
Root cause is a permission problem in the Windows Registry. The SQL Express 2008 installer does not change the permissions of the MSDE entries.

Usage of CNA mezzanine card "PY CNA Mezz. Card 10Gb 2 Port (MC-CNA102E)"
In order to use the FCOE function, the personality of the CNA must be set to FCOE.
In order to use iSCSI function the personality of the CNA must be set to iSCSI.
Important Note: The personality of the CNA can be set with the EMULEX One Command Manager. After changing the personality an inventory boot for the related blade must be executed, this can be done by the VIOM user interface.

6 Corrigenda of Product Documentation

7 Hints

7.1 Un-installation Issues

7.2 Creating Diagnostic Data

ServerView Virtual-IO Manager service log
In order to activate trace functionality of the ServerView Virtual-IO Manager service, please edit the file ViomConfig.properties in the directory <ServerView Suite>\plugins\viom\Manager. On a Windows operating system this is typically the directory C:\Program Files\Fujitsu\ServerView Suite\plugins\viom\Manager

Please modify the line "StartOptions=" and add the option "--debug trace" (2 minus signs).

The trace file of the ServerView Virtual-IO Manager service is <ServerView Suite>\plugins\viom\Manager\logs\viom-manager.log

ServerView Virtual-IO Manager driver log
In order to get full trace information also from the module that configures connection blades like IBP 10/6, IBP 30/12, SB11A or SB11 add the debug option "trace,driverdbg" to file ViomConfig.properties (StartOptions=--debug trace,driverdbg). In that case the ServerView Virtual-IO Manager service will create a trace file for each connection blades configuration command. These files are written to the directory "<ServerView Suite>\plugins\viom\Manager\logs".

Maximal size of diagnostic data
The ServerView Virtual-IO Manager service creates a pre-defined maximum number of log files. Each log file can have a pre-defined maximum size. When the maximum number of log files is reached the oldest log file is automatically deleted and new log information is written to a new log file. The maximum number of log files can be changed by editing the file man-log4j.properties in the directory <ServerView Suite>\plugins\viom\Manager.

In some cases it might be necessary increase the number of log files in order to keep trace information for a longer time period. In such a case please modify the line log4j.appender.DebugAppender.MaxBackupIndex=25 and set the property MaxBackupIndex to an appropriate value. Depending on the amount of requests send to the Virtual-IO Manager service it might be necessary to set this property to the value 50 or maybe even higher, if you want to keep log information for about 1 week. The property MaxFileSize should not be increased, because it might make it difficult to load files into an editor.

Important note: After modifying the property "StartOptions" in the ViomConfig.properties or the property MaxBackupIndex in the file man-log4j.properties, the service "ServerViewVirtualIOManagerService" must be re-started.
(Note: The display string of this service is: "ServerView Virtual IO Manager Service")

VIOM Provider log
Additionally it is possible to activate the trace functionality for the VIOM provider of the ServerView Connector Service (SCS). In order to do so the file <REMOTE_CONNECTOR_DIR>\ViomAPI.xml must be modified.
Please modify the lines

and set "debugging-level" and "tracing-level" to 127. A restart of the SCS service is necessary.

On a Windows operating system the default for the Remote Connector installation directory <REMOTE_CONNECTOR_DIR> is: C:\Program Files\Fujitsu\ServerView Suite\Remote Connector.
On a Linux OS the Remote Connector is installed into the directory: /opt/fujitsu/ServerViewSuite/SCS.

There you will also find the configuration file ViomAPI.xml containing among other things name and location of the VIOM trace file:

If you modify VIOM configuration file you need to restart the Remote Connector in order for it to become effective.

Collecting diagnostic data
On a Windows operating system the action "Collect Log Files" in the "Start" menu (Start -> All Programs -> Fujitsu -> ServerView Suite -> Virtual-IO Manager -> Collect Log Files) creates a ZIP archive with log files from Virtual-IO Manager, VIOM database information and log files from ServerView Server - List service.

For details how to collect diagnostic data on a Linux operating system please have a look at the chapter "Collecting diagnostic information" in the manual.