Home

Fujitsu V3.1 User's Manual

Contents

1. 2 329 12 3 10 The FunctionC onfiguration element 22 2 329 13 VIOM scenarios 0000 00000 c cece cece ccc eee e cece eeeee 331 13 1 Shifting tasks from one server blade to another 331 13 2 Moving tasks using the server profile failover 332 13 3 Disaster RECOVETY 2 cece eee cece cece ccccccececeeeees 333 14 VIOM database 00000000 a ccc eee e ee eeee 337 14 1 VIOM Backup Service 22 222222 eceeeeeeeeeeee 338 14 1 1 Configuring the job schedule on Windows 339 14 1 1 1 Syntax of Quartz cron expressions 340 14 1 2 Configuring the job schedule on Linux 342 14 1 3 Configuring the output directories 0 22 22 343 14 1 4 Starting the Backup Service on Windows 344 14 1 5 Starting the VIOM Backup Service on Linux 344 14 1 6 Logging the Backup Service 220 2220000 345 14 2 Restoring the VIOM database on Windows 345 14 2 1 Restoration via SQL Server Management Studio 345 14 2 2 Restoration via Enterprise Manager 349 14 2 3 Checking the database backup 22220 22 349 14 3 Restoring the VIOM database on Linux 350 15 Appendix 22 2 0 222 c cence cece ccc ccceeeeeeeees 353 15 1 Repla
2. You configure the network parameters of an I O connection blade as follows e 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 e Click Apply to activate the settings 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 124 ServerView Virtual lO Manager 4 3 Configurations on the managed BX900 Blade Server DHCP Client Name Bx9 081Paae95 CBL Subnet Mask Gateway IP Mode Setting Value DHCP Client Name Setting Value IP Address Setting Value 1 gt Subnet Mask Setting Value Enter selection or type to quit You configure the network parameters of an I O connection blade as follows In the Remote Manager choose 1 Management Agent 6 Con nection Blade Select an I O connection blade Choose 2 Management Port Information Make the relevant entries for the following parameters o IP Mode Setting Value o IP Address Setting Value o Subnet Mask Setting Value o Gateway Setting Value Activate the settings by clicking Apply Management port Network Set ting D For Fibre Channel switch modules select FC Switch Blade a you must also specify access data for the parameters Set Login Username
3. wow Ces e Coots eet Cimot 4 Lokales Intranet Figure 31 Server Profiles view If in the Server Profiles view in the area on the left a folder is selected all server profiles in this folder are shown in the table otherwise the selected pro file is shown In the table there is one row per server profile showing the rel evant information the profile The name os the server profile The identifier of a port there is one row per port that is defined in the profile ServerView Virtual lO Manager 159 5 Virtual lO Manager user interface The name of the network defining the dedicated LAN con nection 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 If more than one server profile is selected or the selected server profile is assigned this button is disabled Delete The selected profiles will be deleted A message appears asking if you wish to delete the corresponding server profiles If you confirm this the server profiles will be deleted You can only delete server profiles that are not assigned If any selected server profile is assigned this button is disabled Details The Serverprofile lt profile name gt dialog box is opened providing infor m
4. Select the configuration to restore In the Configuration column you select the configuration s to restore Configuration Selection box and configurations that could be restored Targe For blade servers only The target to which the configuration will be restored is specified Options button It opens the Restore Options dialog box You can select following configurations to restore Profiles Restore the server profiles ServerView Virtual lO Manager 229 5 Virtual lO 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 lt server gt Restore the configuration saved for the selected server For blade servers the Restore Options dialog box opens auto matically in which you specify additional parameters see section Restore Options dialog box Servers on page 241 In addition you can click the Options button in the last column to open the Restore Options dialog box see Restore Options dialog box servers on page 241 for each configuration For PRIMERGY rack servers the three options in the Restore Options dialog box are disabled In addition Reassign Pro files is selected 5 4 5 7 Select Data step Delete Backup Files wizard Select Data is the third step in the Delete Backup Files Configuration wiz ard Delete Backup Files Action y f These f
5. 1 Before VIOM can work with a blade server chassis or PRIMERGY rack server it must be managed by VIOM 2 For blade servers with IBP you can define external network con nections 3 You then define the corresponding profiles for all applications images and save them in the server profile repository on the central management station ServerView Virtual lO Manager 29 2 4 2 Virtual lIO 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 Defining networks LAN for blade servers only In order for VIOM to be able to switch the network paths correctly when assigning profiles first VIOM has to know which networks are present on the respective chassis on which uplink ports This also makes it possible to separate individual server blades or groups of server blades from a network perspective so that two server blade groups do not have any connection to each other in terms of network Defining network paths on an IBP module includes the following steps e Defining an uplink set An uplink set comprises one or several uplink ports An uplink port is an extern
6. Virtual lO Manager 58 ServerView Virtual lO Manager 3 2 1 3 2 Installing the Virtual lO Manager on a Windows based CMS Installing the Virtual lO Manager using a graphical inter face Installation process 1 oa fF WOW DN 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 Select the option ServerView Software Products Click Start Inthe next window select the required language Select ServerView Virtual lO Manager Double click the SV_VIOM exe The installation wizard is launched After determining a number of parameters of the existing operating sys tem base the following window is displayed ie Fujitsu Server iew Yirtual IO Manager Setup FUJITSU Welcome to the Fujitsu ServerView Virtual lO Manager Installation Wizard tis strongly recommended that you exit all Windows programs before running this setup program Click Cancel to quit the setup program then close any programs you have running Click Next to continue the install WARNING This program is protected by copyright law and international treaties Unauthorized reproduction or distribution of this program or any portion of it may result in severe civil and criminal penalties and will be prosecuted to the maximum extent possible under law Cancel ServerView Virtual lO Manager 59 60
7. Activate Port Backup Switch to a backup port if an error occurs in the active port The port backup function is only available if at least one backup port is con figured By default Activate Port Backup is selected Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail The linkdown event triggers a failover process on the server blade if con figured accordingly ServerView Virtual lO Manager 169 5 Virtual lO 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 link down 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 con nection to remain intact In order for the failover process in the server blade to work from LAN port 1 to LAN port 2 aLAN team must have been configured on the server blade and the network on the second IBP module must have been con figured accordingly By default Linkdown propagation is selected Enable LACP You activate the LACP protocol via Enable LACP Isolate mode You activate the isolate mode via Isolate mode With isolate mode acti vated server blades in the same chassis that use the same network can not commun
8. Create a Hyper V virtual network Create clusters Prepare virtual machines o oN Oa F ODN gt Register virtual machines in clusters z Install and configure storage management software as Install and configure VM management software Q ServerView Virtual lIO Manager 2 7 High Availability HA support 12 Install and configure ServerView Operations Manager and ServerView Virtual IO Manager On the secondary node Connect with shared storage Configure BIOS Install Hyper V roles Install and configure EMC Solutions Enabler if used Add a failover clustering function Create a Hyper V virtual network Install Hyper V roles Add a failover clustering function oO oN oa F ODN ZR Create a Hyper V virtual network Create clusters Prepare virtual machines N Register virtual machines in clusters 13 Operate the management station in a cluster For details of items 7 to 13 refer to the Hyper V manual If an error occurs on a VM guest the operation will continue if the VM guest is switched over High availability of VMware HA To make use of the high availability functionality of VMware HA you must use the operating system VMware Infrastructure 3 with the two concepts Cluster and Resource Pool ServerView Virtual lO Manager 51 2 Virtual lIO Manager Introduction Virtual Infrastructure Client Figure 12 Architecture and typical configu
9. To define modify or delete uplink sets and networks in a stack select one stack member and start the desired operation Details can be found in Defin ing network paths LAN on page 277 Using stacked SB11 Connection Blades in IBP Mode VIOM also supports stacked SB11 connection blades in IBP mode but the configured stack must not span over several chassis Stacked SB11 con nection blades in switch mode are also supported since VIOM handles them transparently In this case the stack can span over several chassis For correct handling by VIOM the SNMP agent on the stacked SB11 con nection blades must be running and the SNMP community for the SNMP agent on the stack must be configured to be identical to the SNMP com munity of the blade server management blade If this is not done ServerView Operations Manager cannot retrieve the necessary information for VIOM in order to detect the stack correctly and the stack members might be handled as single connection blades which will result in errors It is important to configure the SB11 IBP stack before managing the chassis by VIOM Also the topology of the stack which connection blades belong to the stack should not be changed while the chassis is managed If the stack gets broken while the chassis is managed by VIOM this is handled as a stacking error by VIOM In this case the stack needs to be repaired 128 ServerView Virtual lO Manager 4 4 4 4 Configurations on the managed PRI
10. e For Windows Virtual lO Manager events are recorded in the ServerView VIOM event log of the Windows Event Viewer with source ServerView Virtual IO Manager ServerView Virtual lO Manager SOAP API ServerView Virtual lO Backup Service and ServerView Virtual lO License Man ager ServerView Virtual lO Manager 359 15 Appendix e ForLinux Virtual IO Manager events are output to the system log with source VIOM MAN VIOM LICENSE MANAGER and VIOM BACKUP SERVICE The event logs for errors are self explanatory and not listed here Infor mational events that describe changes to the configuration are shown in the following table The log entries contain more information e g names of involved uplink sets or nodes than listed in the Meaning column If you are running Windows this list of event IDs should enable you to filter the events for relevant entries 360 ServerView Virtual lO Manager 15 4 Event logging 51217 Node has been restored to ServerView Virtual lO Manager data base configuration sa There are no event IDs available in Linux ServerView Virtual lO Manager 361 362 ServerView Virtual lO Manager
11. 5 4 Wizards 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 Save local Saves the configuration in a file on the computer on which the GUI runs File Name for the backup file It is strongly recommended to specify a complete path on Windows including drive letter because other wise the file location depends on the used browser and operating system Browse Opens the file selection dialog box in which you can navigate to the desired folder and then select an existing backup file or specify the name of the backup file If the file already exists it will be overwritten 5 4 5 3 Select File step Restore Configuration wizard Select File is the second step in the Restore Configuration wizard In this step you select the the backup file from which you want to restore the con figuration ServerView Virtual lO Manager 225 5 Virtual lO Manager user interface Restore Configuration Select Action Restore file From Management Station Name Date AllConfig xml 2011 04 18 08 41 39 BX900 2 wo Prof
12. Name Name of the backup file Date Date and time when the backup file is created Select All Selects all the backup files ServerView Virtual lO Manager 227 5 Virtual lO 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 Save Configuration tion t File Select servers to save Belect Data Chassis V Bx900 2 FJ 111 22 11 111 E 111 22 12 11 Save profiles 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 Save Profiles Specify whether server profiles are to be saved too It is essential that you save the profiles along with the configuration if the assigned profiles are to be reas signed once the configuration has been restored 228 ServerView Virtual IO Manager 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 Restore Configuration Select configuration to restore Configuration Target C Profiles C Bx900 2 Figure 63 Select Data step Restore Configuration wizard
13. Note The dis play 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 lt remote_connector_dir gt ViomAPI xml Please modify the lines lt viom debugging level gt 0 lt viom debugging level gt lt viom tracing level gt 0 lt viom tracing level gt by setting debugging level and tracing level to 127 You will then need to restart the SCS service On a Windows operating system the default for the Remote Connector instal lation directory lt remote_connector_dir gt is C Program Files Fujitsu ServerView Suite Remote Connector On a Linux operating system the Remote Connector is installed in the direc tory opt fujitsu ServerViewSuite SCS There you will also find the VIOM configuration file ViomAPI xml containing among other things the name and location of the VIOM trace file lt viom logging file gt var log fujitsu ServerViewSuite viom viom provider log lt viom logging file gt If you modify the VIOM configuration file you must restart the a 1 Remote Connector for it to become effective On a Windows operating system the action Collect Log Files in the Start menu Start All Programs Fujitsu ServerView Suite Virtual lO Man ager Collect Log Files creates a ZIP archive This ZIP archive contains all log files from Virtual lO Man
14. Position First LSN jt i Database Full TORONTO2ZO08 SQLSERVERVIEW ViomDB 1 26000000017400037 2 Server local SQLSERVERVIEW Connection TORONTO2008 Administrator 5 View connection properties Ready 2 Onthe General page enter the name ViomDB or master in the To data base field or select the name from the list Select the option From device 4 Click the button Add the database backup ViomDB Data bak from the appropriate stor age 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 col umn 7 Switch to the Options page 8 Select the options Overwrite the existing database 9 If no transaction log backup ViomDBLog bak is available click OK Otherwise select the option Overwrite the existing database and Leave database nonoperational and do not roll back uncommitted transactions Additional transaction logs can be restored ServerView Virtual lO Manager 347 14 VIOM database 10 Click OK and then OK again Restoration of the database begins In the ObjectExplorer you will see the message ViomDB Restoring Restore the transaction logs if available 1 Click Databases and then select Restore Databases from the con text menu The Restore Database window opens 2 Onthe General page in the To Database field select the name ViomDB from the list Select the option From Device 4 Click the butto
15. When un assigning a VIOM server profile the following actions are per formed 1 2 3 268 VIOM checks that the server is powered off by reading the power state reported by the iRMC VIOM clears the VIOM specific virtualization data stored in the iIRMC Internally the VIOM server profile is no longer assigned to this PRIM ERGY rack server VIOM performs the special init boot see also actions when assigning a profile This is done in order to remove any virtual addresses from the I O devices so that the original manufacturer addresses MAC ServerView Virtual lO Manager 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 col umn state In some situations you may need to manually update this information in order to get the current state To do this click the Update States button Behavior after AC failure The VIOM specific virtualization data and inventory data are stored in the iRMC This data only remains valid as long as the iRMC is powered on Dur ing a power loss disconnection of all power cables or power loss in the data center the iIRMC will forget the VIOM vi
16. You can configure the network parameters of an I O connection blade using the easy to use Web interface or you can use the Remote Manager of the management blade Configuration using the Web interface Itis important that the I O connection blades of the BX900 can be accessed from the management station via their management port You can configure the network parameters of the management port of an I O connection blade using the Web interface of the management blade ServerView Virtual lO Manager 123 4 Configuration f BX900S1 Front View af RI Refresh Controller Time 04 01 2009 14 18 02 Locate System Unit Details E Uptime 1 day s 21 20 48 Power Consumption Mode disable Input Power Consumption Actual Max Vj css Scheduled z 1121 12800 Error Power Consumption Mode off Remaining Output Power 8917 Locate eL e k C E contguration User Assigned Name User Assigned Name Ta JBxgoosiPoo0gs cB1 P00095 CB1 Apply Management Port Settings BX900S1 Rear View Setting Value Current Value Enable DHCP 7 DHCP IP Address 0 at f E 111 22 220 122 Subnet Mask 0 J0 J 0 255 255 224 0 Gateway Address 0 10 0 0 111 22 220 1 The settings will be effective after 3 minutes Apply Reload Settings Polling Settings Enable Period Polling J Enable Polling Password System Unit Management Blades 4 O Server Blades O Storage Blades 5 Connection Blades
17. tiate is selected If auto negotiation is not selected on the external switch you configure the value using the drop down menu according to the settings on the external switch The following values are available auto negotiate Default The transmission speed is negotiated with the external switch 1Gbit s 1 Gbit s full duplex 2 Gbit s 2 Gbit s full duplex 4 Gbit s 4 Gbit s full duplex 8 Gbit s 8 Gbit s full duplex ServerView Virtual lO Manager 217 5 Virtual lO 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 D This step is only shown if at least one FCoE function for a CNA mez zanine card is specified in the second step of the Edit Server Pro file wizard 218 ServerView Virtual IO Manager 5 4 Wizards 4 Edit Server Profile profile2 Ea Name CNA parameter settings Mezz 1 Port 1 Function 1 LAN Bandwidth 50 VLAN ID Mezz 1 Port 1 Function 2 FCoE Bandwidth 50 4 7 Enable DCB settings Priority Level fMezz 1 Port 2 Function 1 LAN Bandwidth 50 VLAN ID
18. CMS under Windows or Linux see section Installing the Virtual lO Man ager on a Windows based CMS on page 58 and Installing the Virtual lO Manager on a Linux based CMS on page 73 Please check first the requirements for installing the Virtual lIO Manager on CMS see section Prerequisites for the VIOM installation on page 57 If a previous version is already installed on the management station an update installation runs automatically when you install the new version All previous VIOM configurations and definitions remain the same see section Updating the Virtual lIO Manager on a Windows based CMS on page 72 and Updating the Virtual lO Manager on a Linux based CMS on page 89 If you want to use the command line interface of the Virtual lO Manager VIOM CLI you must install the VIOM CLI software package You will find details on how to install and use VIOM CLI in the Virtual lO Manager Com mand Line Interface manual Prerequisites for the VIOM installation The requirements for installing the Virtual lO Manager on a central man agement station are as follows e Operating system for the central management station o Microsoft Windows Server 2003 all editions o Microsoft Windows Server 2003 R2 all editions o Microsoft Windows Server 2008 all editions o Microsoft Windows Server 2008 R2 all editions o Linux Novell SLES10 SP2 and SP3 o Novell SLES 11 SP1 and SP2 o RedHat RHEL 5 6 5 7 5 8 o RedHat
19. MV css 508 3570 Eror Scheduled Consumption Mode off Remaining Output Power 1974 W System Asset Tag N A Locate RAIA LEG BX400S1 Rear View EMMEMIEMEP connouration E User Assigned Name User Assigned Name BX400 VIOM2 CB1 e Refresh Apply Blade Asset Tag System System Unit Front Side YO Module Management Blades S Server Blades S Storage Blades Blade Asset Tag WA Apply 8Gb FC Connection Blade 2 Management Port Settings SAS Connection Blade 3 Setting Value Current Value he bias ee pares Enable DHCP 7 DHCP Rear Fan Units n Power Supplies IP Address 1 o a 111 22 22 111 Subnet Mask 7 o o 255 255 248 0 Gateway Address 7 o i 111 22121 Enable VLAN mM NO VLAN i You configure the network parameters of an I O connection blade as follows e 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 e Click Apply to activate the settings 4 2 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 e Normal Layer 2 switch mode e IBP mode For
20. Port 2 Function 1 LAN Bandwidth 50 VLAN ID Mezz 1 Port 2 Function 2 iSCSI Bandwidth 50 gt VLAN ID 7 Enable DCB settings Priority Level Previous F Next Finish a iu Cancel J fj Help 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 O channel is not 100 the values are internally adjusted accordingly D This is the bandwidth reserved for the FCoE function E The FCoE function might share the complete bandwidth of 10 Gb with other functions A value of 60 for exam ple means that a bandwidth of at least 6 Gb sec is reserved for the FCoE packages Vlan ID optional The Vlan ID that is used by this function This field is not available for FCoE functions ServerView Virtual lO Manager 201 5 Virtual lO 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 ina 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 If the port of the server blade where the profile will be used is connected to a LAN pass
21. The procedure varies according to the column e Inthe VLAN column By double clicking an entry in the table a dialog box opens in which you can make your changes e Inthe Uplink Ports and Backup Ports columns both only available on the Details tab When changing the ports enter the ports separated by a comma You can define related areas using the minus sign e g 11 13 is the same as 11 12 13 When changing the ports in a switch stack take care to change the value in the appropriate row e Inthe Linkdown Prop Port Backup LACP and IGMP columns on the Details tab Click the check box to change the existing con figuration e Inthe port view of the Graphic tab Select the changes in the context menu of the corresponding port Deleting networks If several networks are assigned to a shared uplink set you have the option of deleting networks You can delete networks using either the Graphic or Details tab 1 Select the corresponding networks in the table on the Graphic or Details tab 2 Click the Delete button or select Delete in the context menu 286 ServerView Virtual lO Manager 8 4 8 4 Copying an IBP configuration A message appears asking whether you wish to delete the cor responding network 3 If you confirm this the networks will be deleted G Ifyou delete all networks or the last network of an uplink set the related uplink set is also deleted Copying an IBP configuration You have
22. To restore address ranges will be necessary if address ranges have been changed since the backup configuration was saved or if they have been created on another management station This option cannot be selected together with Keep existing profiles 7 Click OK to apply your selection or Cancel to close the dialog box with out applying your selection 11 2 2 Restoring blade server configurations 1 To restore blade server configurations select the corresponding blade server in the Select Data step The Restore Options dialog box opens in which you specify additional parameters You can also open this step 306 ServerView Virtual lO Manager 11 2 Restoring the configuration by clicking the Options button in the table row 2 Select Restore Spare Information to restore the information on the spare slots 3 Select Reassign Profiles if you want to reassign the profiles which were assigned when the backup was performed This option is only avail able if the backup contains profiles If the option to restore profiles is not selected this is performed automatically when you select the Restore only reassigned profiles option 4 Select Restore On Different Chassis to restore the backup on another blade server If you select this option you have to select the destination blade server in another dialog box 5 Click OK to apply your selection and Cancel to close the dialog box with out applying your selection 11 2 3 Restoring
23. blade server only IBP selected If you select an I O connection blade and this module does not have the wrong model or stacking error state in State Causes you can use the ServerView Virtual lO Manager 147 5 3 3 5 3 3 1 5 Virtual lO 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 inthe VIOM database Video Redirection PRIMERGY rack server and server blades Opens a new window where the console output of the server is shown Ext LAN Connections tab On the Ext LAN Connections tab you configure the LAN modules with the external devices Two tabs are available for doing this It is only enabled if a single blade server is selected in the server list e Graphic tab This tab schematically displays the connection blades IBPs and ports Using this tab you can create new network definitions modify or delete definitions as well as copy definitions from one connection blade to another one e Details tab This tab contains a table with the present definitions Using this tab you can create new network definitions or modify and delete existing ones Also on this
24. e Validity period only relevant for demo licenses e Max number of assignments that are allowed with the licenses e Number of currently assigned server profiles e Number of server profiles that can still be assigned with the licenses For more information see section Displaying license information on page 275 3 7 Updating ServerView Operations Manager ServerView Operations Manager may be updated at any time while the Vir tual lO Manager is idle Thus you should stop the Virtual lO Manager Service before starting the update Updating ServerView Operations Manager consists of three steps e Perform an update installation of ServerView Operations Manager e Check that the updated version works okay e Start the Virtual lO Manager Service D After performing a modify installation of ServerView Operations Man ager you need to start the Virtual lIO Manager Service 94 ServerView Virtual lO Manager 3 8 3 8 Upgrading or moving the SQL Server database D When you need to uninstall existing ServerView Operations Man ager and install the new one you should uninstall existing Virtual IO Manager e Save your configuration by using the Configuration Backup Restore button on the Virtual lO Manager tab e Uninstall Virtual lO Manager e Uninstall ServerView Operations Manager e Install ServerView Operations Manager e Install Virtual lO Manager e Restore your configuration by using the Configuration Backup I Restore button on
25. may end up with two different blades containing identical virtual addresses Therefore you should only assign and boot the profile on the other site if you are sure that the failed site is not longer active on the networks The easiest way to ensure this is to completely power off the failed site before restarting the profiles on the other site To avoid having two blades powered on with the same server profile you must prepare the power on behavior of the chassis During site preparation the server blades BehaviorAfterAC Fail flag need to be set to Always power off You can do this in either of the following ways Via MMB preferred because more convenient The MMB Power Restore Policy function on the Power Management tab controls the Behavior After AC Fail Set it as indicated to Always power off for every server blade in the chassis ServerView Virtual lO Manager 335 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 Procedure for restoring the failed site After powering on the failed chassis the blades will automatically execute a so called
26. ported Please note that the ports on the external switch which are connected to the IBP ports that form a LAG have to form a static LAG if the LAG on the IBP forms a static LAG You can optionally enable the LACP mode when creating a network If the LAG on the IBP is configured to use LACP the LAG on the external switch must also be configured to use LACP Note The Link Aggregation Control Protocol LACP is defined in IEEE 802 3ad which allows dynamic trunking of two or more net work connections between two switches For a single network no VLAN IDs are taken into account i e all packages are allowed through irrespective of the VLAN ID To define an single network follow the steps below 1 Click on the Ext LAN Connections tab in in the work area on the left 2 Start the Create network wizard by e clicking New on the Graphic or Details tabs e selecting New Uplink Set in the context menu of an uplink set The Create network wizard is launched 280 ServerView Virtual lO Manager 8 1 Defining an uplink set 3 Inthe 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
27. server blades that support the I O virtualization 100 ServerView Virtual lO Manager 4 1 Configurations on the managed BX600 Blade Server To check the parameter setting in the Remote Manager of the man agement blade choose 1 Management Agent 3 System Infor mation 11 Automatic Inventory Retrieval e Toensure 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 3 Configuring the I O connection blades The IBP modules in fabric 1 and the optional connection blades IBP or Bro cade Fibre Channel switch blades in fabric 2 must be configured and con nected to the local network so that they can be accessed from the central management station on which the ServerView Operations Manager and VIOM are installed You can configure the network parameters of an I O connection blade using the easy to use Web interface or you can use the Remote Manager of the management blade ServerView Virtual lO Manager 101 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 Health Status Health Status 2 BladeServer 8X60083 2 Component GbE IBP Blade 1 System Power Uptime 63 day s 10 16 35 Configuration Current Value DHCP Enable 1 NO DH
28. the management blade To do this choose 1 Management Agent 2 Management Blade The Management Blade Firmware Version parameter displays the installed firmware version You can also check ServerView Virtual lO Manager 121 4 Configuration the version via the Web interface If your firmware version is lower than the version required you must update it to the required firmware version before you activate VIOM man agement for the blade server You can run an update via the Remote Manager of the management blade 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 Then specify path and name of the file with the new firmware version by selecting option 2 Management Blade Image File Name After this select option 3 Management Blade Update Enable e You must configure the management blade and connect it to the local net work so that the management LAN port of the management blade can be accessed from the central management station on which the ServerView Operations Manager and VIOM is installed e Access to the management blade via Telnet or SSH is essential for VIOM You must configure the management blade via its Web interface To do this choose Settings System Unit Network Interface Management LAN On the Ethernet tab check the telnet and SSH set tings in the Text based Access section e Ensure that the Automatic Inventory Retrieval
29. 19 99 3E F1 E0 wwn range 50 01 99 93 ED 2A 10 00 50 01 99 93 EF 1E 0D FE license key AAA BBBB CCCC DDDD EEEE FFFF GGGG Important directories of Virtual lO Manager opt fujitsu ServerViewSuite plugins viom In all Linux distributions this is the installation directory where the binaries and libraries are stored var fujitsu ServerViewSuite viom Directory in which variable information of VIOM is usually stored 88 ServerView Virtual lO Manager 3 4 4 3 5 3 5 Updating the Virtual lO Manager on a Linux based CMS var log fujitsu ServerViewSuite viom Directory in which the VIOM log files are stored Collecting diagnostic information Sometimes it might be necessary to gather diagnostics information in order to send it to your Fujitsu support service In the Manager subdirectory of the VIOM installation directory you will find a dump sh script that you may launch using the following command cd opt fujitsu ServerViewSuite plugins viom Manager sh dump sh The dump sh script collects and generates a set of diagnostics files zips them and stores the result in the directory var fujitsu ServerViewSuite viom dumps Updating the Virtual lO Manager on a Linux based CMS If you have already installed a previous version you can run an update instal lation In this case you must specify the upgrade option when invoking the installation script sh install viom sh u
30. 338 ServerView Virtual lO Manager 14 1 VIOM Backup Service The following parameters need to be configured for the backup jobs e 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 e The parameter for the directory where the output files are stored see sec tion Configuring the output directories on page 343 D Dependencies on the database On Windows Both the VIOM Manager and the Backup Service use Windows Authentication to access SQL Server This means at the very least that both services must run under the same Windows account as the SQL Server On Linux The Virtual IO Manager is installed under the root user and with root privileges The database is accessed via the database user svuser which has already been created by ServerView prior to the Virtual lO Manager installation Warning On Windows It is a known behaviour of SQL Server that the trans action log grows unless it is periodically backed up We therefore strongly recommend that you configure and start the Backup Serv ice in order to backup at least the transaction log 14 1 1 Configuring the job schedule on Windows The jobs and their triggers are defined in the quartz_jobs xml file in the lt installation_path gt VIOM Manager directory Cron triggers may be mod ified by the user by editing this XML file T
31. 4 Wizards Create Server Profile Overview of Server Profile Properties Serverprofile BX62054_Virt Inot assigned Type of the profile blade 6 onboard ports LAN Mezzanine card board 1 Port Network Virtual Address Onboard 1 INET_1 to be assigned Onboard 2 INET_1 to be assigned Onboard 3 DB_1 lto be assigned Onboard 4 DBA to be assigned Onboard 5 WEB_1 lto be assigned Onboard 6 WEB_1 lto be assigned Mezzanine 1 Port 1 to be assigned Mezzanine 1 Port 2 lto be assigned Boot menu usage is not disabled Boot priority 1 Mezzanine 1 Port 1 PXE boot Boot priority 2 Mezzanine 1 Port 2 PXE boot No comment Previous Finish Cancel Help Figure 49 Confirm step 5 4 4 Edit Server Profile wizard You use this wizard to modify a server profile The Edit Server Profile wizard comprises several dialog boxes to guide you through the individual steps All required steps are displayed in the tree struc ture on the left 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 1 Name step Edit Server Profile wizard Name is the first step in the Edit Server Profile wizard In the first step you can modify the name its intended target and the description of the server pro file ServerView Virtual lO Manager 205 5 Virtual lO Manager user interface Edit Server Profile profile
32. Chap Secret The mutual CHAP password This password must be identical to the password configured on the iSCSI target It must contain 12 to 16 char acters 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 Boot Parameters for SAN boot in the case of Fibre Channel ports or functions Edit Server Profile profile2 Nam Please fill in the boot parameters Use arrow buttons to change boot priority Onboard 1 1 Mezzanine 2 Port 1 1st Target Port Name WWPN 77 88 99 aa bb cc dd ee 2 and Target Port Name WWPN Speed auto negotiate Topology auto Point to Point first 3 Previous Next Finish Cancel Help Figure 54 Boot Parameter step SAN boot 1st Target In 1st Target you configure the boot device Port Name WWPN worldwide port name of the port for the boot device 216 ServerView Virtual lO Manager 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 nego
33. IBP 1Gb 18 6 PY CB Eth Switch IBP 1Gb 18 6 in IBP in IBP mode mode optional PY CB Eth Switch IBP 10 Gb PY CB Eth Switch IBP 10 Gb 18 8 in 18 8 in IBP mode IBP mode optional 1 Even though this constellation is possible it does not make sense because only the first port can be used from the IBP module in bay 3 Operation in Open Fabric mode Open Fabric mode refers to the use of non VIOM capable LAN modules together with the Virtual lO Manager In this case you can only work with vir tual I O parameters and not with dedicated network connections ServerView Virtual lO Manager 111 4 2 1 2 4 Configuration Therefore if you do not want to use any routing all combinations are possible even with non VIOM capable I O connection blades You must take the fol lowing into account e You cannot mix LAN and IBP modules within fabric 3 e Youcan only assign profiles if no networks are defined for their ports D You can force the assignment of a profile with network def i initions by selecting the Ignore ext LAN connections option in the profile selection dialog box or by answering the sub sequent query accordingly In doing so however the network definitions are ignored e You can operate LAN models of different sizes within fabric 3 although you cannot use all download links from the larger model Fibre Channel hardware configuration You can install the Fibre Channel switch blades in fabric 2 or fabric 3 They can be
34. Installing the Virtual lO 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 D The validity of the MAC address input is not checked Please confirm that your input address is valid before you click Next D If you have several installations of the Virtual lO Manager in your LAN network then you must ensure that the address ranges used do not overlap Otherwise addresses may be assigned several times D To change the range of the address after installation is finished you must uninstall the Virtual IO Manager and install it again Therefore if it is possible that addresses may have to be added after the Virtual lIO Manager is set up we recommend that you install it without selecting the address range You should input a virtual address when creating the server profile 9 Click Next E Fujitsu ServerView Virtual IO Manager Setup Installation Configuration foe Please select one of the listed address ranges for virtual WWNN FU SU and WWPN addresses or define your own custom address range WWN Address Range Property Description WWN Address Range 1 WWN Address Range 2 50 01 99 93 ED 24 10 00 50 01 99 93 EF 1E 0D FF WWN Address Range 3 WWN Address Range 4 WWN Address Range 5 WWN Address Range 6 WWN Address Range 7 Maahi A cdedemee Danan 2 Custom WWN Address Range Parameters Start Address 50 01 99 93 E
35. Mezz 1 Port 2 Function 2 iSCSI Bandwidth 50 gt VLAN ID 7 Enable DCB settings Priority Level Previous l Finish Cancel J m Help J 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 If the port of the server blade where the profile will be used is connected to a LAN pass thru module or a PY CB Eth Switch IBP 10 Gb 18 8 SBAX2 connection blade in switch mode the option Enable DCB set tings should not be set Priority Level The priority level Possible values are 0 to 7 for FCoE this is by default the value 3 for iSCSI the default value is 4 ServerView Virtual lO Manager 219 5 Virtual lO 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 O channel is not 100 the values are internally adjusted accordingly D 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 e
36. 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 The values must be in hexadecimal format for example 11 22 33 44 55 66 WWN_RANGE Possible values are NONE No predefined WWN address range default value WWN1 Range 50 01 99 93 ED 2A 10 00 50 01 99 93 EF 1E 0D FF WWN2 Range 50 01 99 93 EF 1E 0E 00 50 01 99 93 F 1 12 0B FF 70 ServerView Virtual lO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS WWN3 Range 50 01 99 93 F 1 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 WWN_START WWN_END These parameters must be set if WWN_Custom is specified The values must be in hexadecimal format for example 11 22 33 44 55 66 77 88 DEBUG MODE Possible values are true Enable debug mode default value false D
37. ServerView database is described in the manual ServerView Operations Manager Installations under Windows The restoration of the VIOM database is similar 14 2 3 Checking the database backup From time to time you can check the backups with the SQL Server Man agement Studio or the Enterprise Manager E For how to check database backups with the Enterprise Manager see the relevant sections in the manual ServerView Operations Manager Installations under Windows For the SQL Server Management Studio follow the instructions in thesection Restoration via SQL Server Management Studio on page 345 but with the following changes 1 On the General tab enter any name in the Restore as database field e g RECOVERYTEST 2 Onthe Options tab change the path names in the Move to physical file name column as follows e ViomDB mdf to RecoveryViomDB mdf e ViomDB_log LDF to RecoveryViom_log LDF ServerView Virtual lO Manager 349 14 3 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 Restoring the VIOM database
38. Serverprofile profile2 not assigned Type of the profile blade 2 onboard ports FC Mezzanine card board 1 Port Network Virtual Address Onboard 1 NET_1 100 19 99 3e d2 a1 Onboard 2 NET_1 00 1 9 3e d2 az wil be assigned WWPN to be assigned WIWNN to be assigned WiWPN to be assigned Mezzanine 1 Port 1 Mezzanine 1 Port 2 Boot menu usage is not disabled Boot priority 1 Onboard 1 PXE boot Boot priority 2 Onboard 2 PXE boot No comment Previous Finish Cancel Help Figure 57 Confirm step 222 ServerView Virtual lO Manager 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 lIO Manager tab 5 4 5 1 Select Action step Configuration Backup Restore wizard You save and restore backup files as well as delete them on the man agement station using a wizard You launch the wizard using the Con figuration Backup Restore button on the Virtual lO Manager tab Select Action is the first step in the Configuration Backup Restore wizard In this step you select the action that you want to carry out Save Conf
39. VLAN networks 000200222 e eee 282 8 1 4 Defining a dedicated service network 2 285 ServerView Virtual lO Manager 7 Contents 8 2 Modifying an uplink set 000000000 0020 285 8 3 Deleting networks 22 22 2222 e cece cece eee cece ees 286 8 4 Copying an IBP configuration 2 2 00 e eee eee 287 8 5 Copying configuration 00000 0000 c cece eee cece 288 9 Defining and assigning server profiles 0 0 289 9 1 Defining server profiles 20 2 e cece eee eeeeeeeeeees 290 9 2 Viewing server profiles 00 c cc eeeec eee cece ee ceeeeeeeeees 294 9 3 Modifying server profiles 0c cece cece cece eeeeeeeeees 294 9 4 Copying server profiles 2 eee eee eee eeeeeeeeeeeeees 295 9 5 Deleting server profiles 20 oo e cece eee eeeeeeeeeeeees 296 9 6 Assigning server profiles 0c cece cece cece eeeeeeeeeees 296 9 7 Deleting profile assignments 2 0 2 2 cece cece cece cece cece ee eee 298 10 Viewing the blade server configuration 301 11 Saving and restoring 002 00222 e ee eee ee 303 11 1 Saving your configuration and server profiles 303 11 2 Restoring the configuration 000 220 000 222 cece eee 304 11 2 1 Restoring server profiles 000 00 0000 0000202222 305 11 2 2 Restoring blade server configurations 306 11 2 3
40. a DHCP server in the network static 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 196 ServerView Virtual lO Manager 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 You can enter a LUN ID in this field if Address Origin static is selected Authentication Authentication Method None No authentication is used CHAP CHAP authentication is activated for this port CHAP allows the target to authenticate the initiator After activating CHAP you must enter a user name and password for the target Mutual CHAP Mutual CHAP authentication is activated for this port Mutual CHAP allows the initiator to authenticate the target After activating mutual CHAP authentication you must enter a user name a password for the target and a mutual CHAP password Chap Username CHAP user name The name must be identical to the name configured on the iSCSI target ServerView Virtual lO Manager 197 5 Virtual lO Manager user interface Chap Secret CHAP password T
41. a standard configuration Protocol Select the protocol to be used for communication with the management blade or the I O connection blades Port If Use default port is not checked you have the option of specifying other port numbers for the modules in this field Use default port Uses the default port The default port is dependent on the protocol and the relevant module For a management blade Port 3172 for Telnet and Port 22 for SSH For an I O connection blade Port 23 for Telnet and Port 22 for SSH The Port input field is inactive if this option is checked ServerView Virtual lO Manager 233 5 5 2 5 Virtual lO Manager user interface For a standard configuration these values should not be changed 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 Authentication Enter authentication data for these modules i Configure protocols 111 22 11 111 User name admin Password eeecccee Trap Destination it 122 22 1 11 Figure 66 VIOM Manager authentication PRIMERGY rack server For each PRIMERGY rack server you must to specify the user name and password for the
42. an external network ServerView Virtual lO Manager 163 5 Virtual lO 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 2 Edit Properties step Create Network wizard internal network Edit Properties is the second step in the Create Network wizard The selection you made at the first step of the Create Network wizard deter mines which fields are displayed in the second step Edit Properties step for internal networks xl 4 Name of network Internal_3 Previous Next Finish Figure 33 Create Network wizard second step Cancel Help 164 ServerView Virtual IO Manager 5 4 Wizards Name of network Name for the internal network 5 4 1 3 Edit Properties step Create Network wizard single VLAN network Edit Properties is the second step in the Create Network wizard The selection you made at the first step of the Create Network wizard deter mines which fields are displayed in the second step Edit Properties step for single networks VLAN networks Name of uplink set NET_1 M Activate Port Backup Link Speed Auto negotiation Linkdown propagation C Enable
43. are supported by VIOM To manage a blade server with VIOM you must carry out the following pre paratory steps e Configure the management blade or management blades see section Configuring the BX600 management blade on page 99 e Configure the I O connection blades see section Configuring the I O connection blades on page 101 e Define the connection of the IBP modules with the network see section Connecting IBP modules on page 104 e Add the blade server to the server list of the ServerView Operations Man ager see section Adding a server to the ServerView server list on page 135 Supported hardware configurations for the connection blades To define dedicated network connections for server blades with networks IBP modules are required e Atleast one IBP module must be installed in fabric 1 or in fabric 2 of the blade server chassis e To support a Fibre Channel mezzanine card you must install a 4 GB Bro cade switch blade SW4016 D4 Fibre Channel switch blade for BX600 ServerView Virtual lO Manager 97 4 Configuration in fabric 2 FC switch blades do not support any dedicated network con nections but just the virtualization of the I O parameters instead e If you only intend to work with virtual I O parameters Open Fabric mode and not with dedicated network connections you can also install non VIOM capable LAN modules in fabric 1 or fabric 2 Furthermore you can operate non VIOM capable LAN modules in
44. can find out what combinations of I O connection blades are supported by VIOM To manage a blade server with VIOM you must carry out the following pre paratory steps e Configure the management blade or management blades see section Configuring the BX900 management blade on page 121 e Configure the I O connection blades see section Configuring the I O connection blades on page 123 e Define the connection of the IBP modules with the network see section Connecting IBP modules on page 126 e Add the blade server to the server list of the ServerView Operations Man ager see section Adding a server to the ServerView server list on page 135 118 ServerView Virtual lO Manager 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 e 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 LAN connection blades can be inserted in connection bays 1 and 2 of fabric 1 in order to connect the onboard LAN ports and in connection bays 3 and 4 of fabric 2 in order to connect the LAN ports of the first mezzanine card Irre spective of the defined SMUX setting the connection blades can be inserted in connection bays 5 and 6 of fabric 3 or in connection bays 7 and 8 of fabric 4 in order to conn
45. channels as boot devices in the 1 O Channels step If you configured at least two channels as boot devices in the previous step use the arrow up and arrow down buttons to change the boot order The selection you made at the 1O C hannels step iSCSI boot or SAN boot determines which fields are displayed in this dialog box 194 ServerView Virtual lO Manager 5 4 Wizards Boot Parameters for an iSCSI boot LAN ports or iSCSI function on CNA mezzanine card Create Server Profile Please fill in the boot parameters Onboard 1 Initiator Parameters Address Origin Initiator Name IPv4 Address Gateway Address Target Parameters Address Origin Target Name IPv4 Address Authentication Authentication Method Chap Username Chap Secret Mutual Chap Secret DHCP static ign Initiator BX900Blade 1 111 11 111 162 Wi 1 DHCP static ign NetApp com 111 11 111 163 Port 3260 opt O None abcdefghijklmnopqrstu cHaP Mutual CHAP VLAN Id Subnet Mask 255 255 255 0 12 16 characters 12 16 characters Previous next Finish cancel Help 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 specifi
46. checkbox in the corresponding row under Native VLAN in the table to define a network as a native VLAN 186 ServerView Virtual lO Manager 5 4 3 5 4 3 1 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 The column Isolate mode is not shown if the connection blade does not support isolate mode Delete button Deletes a selected VLAN networks from the list Create Server Profile wizard You use this wizard to define a new server profile The Create 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 You define a server profile in the Server Profile view in the area on the right of the ServerView Virtual lO Manager window To open the Create Server Profile wizard click the New button in the area on the right or select New Profile from the Profiles group context menu Another way to define server profiles is to switch to the view of the servers managed by VIOM in the area on the left using the Server List button Then switch to the Server Config
47. database 11 4 3 Restoring the configuration of a server blade slot In a few rare cases e g when the network connection to the management blade is interrupted an error may occur during the assignment of a server pro file to a server blade slot In this case the following errors may occur e The configuration of one or several IBP modules is not correct In this case proceed as described in section Restoring an IBP module configuration see Restoring VIOM specific configurations on page 308 e The virtualization data virtual I O addresses and possibly also boot parameters of the profile have not been written correctly In this case the corresponding slot on the Setup tab indicates the status Fault Here you can use the Restore Slot button on the Setup tab to rewrite the virtualization data D If a server blade is in the slot the server blade must be disabled _ for a Restore Slot Replacing the front control blade If the front control blade of a blade server needs to be replaced the con figuration has to be restored for each slot This means you have to carry out Restore Slot for each server blade slot Inthis case VIOM also provides an option that allows you to restore the entire chassis see section Restoring the blade server chassis con figuration on page 311 D e The Virtual lO Manager does not automatically recognize that ig the front control board has been replaced and hence all the relat ed virtual
48. eee 3 Productive LAN Switch E Management Port Management LAN Productive LAN MMB Management Blade CB Connection Blade Figure 17 BX900 Network Overview The I O connection blades must be connected to the central management sta tion via their management port 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 ServerView Virtual lO Manager 127 4 Configuration The stacking software configures each device tables and registers to support all switching functions for example switching link aggregation port mon itoring spanning tree protocol VLAN etc The entire stack will appear as a single IBP You find a detailed description about switch stacking in the PRIMERGY BX900 Blade Server Systems Ethernet Connection Blade Module IBP ver sion User s Guide chapter 6 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 Then all members of this stack are highlighted the stack master is yellow shaded all other members are green shaded Beside this Stack Master or Stack Member is shown in the details area
49. follows 1 Carry out the base configuration configure the IP parameters system name of the IBP of the connection blade In addition the IP con figuration of the connection blade must have been read from the Server View Operations Manager This is done as part of a regular scan of the blade server chassis D You may have to start the blade server chassis scan explicitly by selecting Explore in the context menu of the relevant blade server chassis in the server list of the ServerView Operations Manager 2 Click Restore IBP on the Setup tab to write the configuration saved internally to the new connection blade 11 4 2 Deleting the configuration of an uninstalled IBP module If an IBP module for which a configuration still exists has been removed from a chassis the configuration remains in the internal database of the Virtual lO Manager This incorrect state is displayed on the Setup tab for the respective chassis with a corresponding state icon on the graphical display of the empty slot on the rear of the chassis slot is empty is indicated as the state in State Cause for this slot You can delete the configuration you no longer need You do this as follows 1 Click the relevant slot in the graphical display on the rear of the chassis 2 Then click the Delete Configuration button ServerView Virtual lO Manager 309 11 Saving and restoring Delete Configuration deletes the configuration saved internally in the VIOM
50. from a file 304 ServerView Virtual lO Manager 11 2 Restoring the configuration Click Next to go to the Select File step Select the backup file from which you want to restore the configuration e Select Restore file from Management Station to select a backup file from the management station e Select Restore local file to select a file on the computer on which the GUI runs When you click Restore file from Management Station you select a backup file from the list on the management station When you click Restore local file you select a backup file on the local computer on which the GUI runs By clicking Browse the file selection dialog box opens which allows you to select the relevant backup file You can also enter the backup file name directly in the input field Once you have selected a backup file click Next to go to the Select Data step to define the data you wish to restore Select the configuration you wish to restore under Select configuration to restore e Select Profiles to restore the server profiles e Select aserver to restore the configuration saved for a blade server 11 2 1 Restoring server profiles 1 Select Profiles in the Select Data step to restore server profiles The Restore Options dialog box opens in which you specify additional parameters You can also open this dialog box by clicking the Options button in the Profiles row Select the server profiles which will be restored If you sel
51. group as an active port or as a backup port An uplink set must contain at least one active port All active uplink ports and all backup ports each form a LAG If anetwork needs to be configured so that the IBP module switches to another port if any problems arise then besides configuring the active ports you also have to configure one or several ports as backup ports If there is no longer a connection for any of the active ports of an uplink set the backup ports are activated and the ports that were active until this point are deactivated Assign the required ports of the IBP to the uplink set by opening the con text menu of each relevant port D For a LAG configuration you have to configure at least two gt active ports With PY CB Eth Switch IBP 1Gb 36 8 2 connection blades 1GB uplinks and 10 Gb uplinks must not be mixed If you try this the Finish button will not be enabled a Wb 6 Select additional options such as Activate Port Backup Switch to a backup port if an error occurs in the active port 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 ServerView Virtual lO Manager 281 8 Defining network paths LAN 7 Ifthe uplink set is created on a PY CB Eth Switch IBP 10 Gb 18 8 click Next to confirm your entries The next step of the Create network wiz ard opens In th
52. hardware configuration 4 3 2 You can install the Fibre Channel switch blades in fabric 2 or fabric 3 They can be operated in two different modes e in normal switch mode e 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 The following table shows you which configurations are sup ported in fabric 2 and fabric 3 Bay 3 Bay 5 Bay 4 Bay 6 Access Gateway mode Access Gateway mode optional Standard switch mode Standard switch mode optional1 1Even though this constellation is possible it does not make sense because only the first port can be used from the Fibre Channel switch blade in bay 3 or 5 Configuring the BX900 management blade The blade server must be fitted with at least one S1 management blade The management blade has two user friendly user interfaces a Web inter face and a Remote Manager interface per Telnet or SSH protocol a con nection to the management blade is established per Telnet or SSH You can find a detailed description on the interfaces in the ServerView Management Blade manual for BX900 Check the following settings in the management blade e The management blade must be installed with a specific firmware ver sion To find out which firmware version you need see the release notes included You can check the firmware version in the Remote Manager of
53. iRMC with which VIOM can access this server If more than one PRIMERGY rack server is selected in the table there is a check box called Use for all components which when checked sets the values for all PRIMERGY rack servers to the ones specified for the first PRIM ERGY rack server So if the user name and password are the same for all PRIMERGY rack servers you only need to specify them once For security reasons you should change the default user name and password combination You can have the same user name and password for all com 234 ServerView Virtual lO Manager 5 5 Dialog boxes ponents or different ones for each You must specify this accordingly in this dialog box With the Configure protocols button you can expand the dialog box so that you can also specifiy the port to be used by VIOM to access the com ponents This value should not be changed in a standard configuration User name A valid user name with access rights to the iIRMC Password Password of the user ID Trap Destination IP address IPv4 or IPv6 of the VIOM management station to which traps are sent in the case of connecting the PRIMERGY rack server to power This field is preset with one IP address of the VIOM management station It should only be changed if the management station is reach able by different IP addresses and another one should be used Use for all components Sets the values for all PRIMERGY rack servers to the ones specified for first
54. in one uplink set ServerView Virtual lO Manager 31 2 Virtual IO Manager Introduction D 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 inde pendent network paths e g for different applications e g database server communication server or individual areas e g development accounting or personnel administration D To find out what happens when you activate the management of a iiz blade server using the Virtual IO Manager with the standard IBP con figuration see section VIOM internal operations on blade servers on page 261 The following figure provides an overview of typical uplink sets that you can configure using VIOM 32 ServerView Virtual lO Manager 2 4 Defining networks LAN for blade servers only Server Blade 1 Server Blade 2 Server Blade 3 Server Blade 4 Server Blade 5 Server Blade 6 Server Blade 7 Server Blade 8 Server Blade 9 Server Blade 10 Blade chassis Figure 4 Typical uplink sets The uplink ports can be assigned to an uplink set as active ports or as back up ports
55. information on how to perform the switch refer to the Switch Blade user manual ServerView Virtual lO Manager 115 4 Configuration Please note that before you activate blade server management sev eral uplink ports of aLAN connection blade in IBP mode form a stat ic link aggregation group LAG If you activate blade server management using VIOM all uplink ports of IBP modules will be deactivated and will only be reactivated when networks are defined in the IBP module 4 2 4 1 Network Overview All components such as the management blades and I O connection blades the central management station and the management console must be inter connected via LAN It is recommended that you set up a management LAN that is separate from the productive LAN as illustrated in the following figure D If there are not enough physical ports available a VLAN based man z agement LAN can also be implemented 116 ServerView Virtual IO Manager 4 2 5 4 2 Configurations on the managed BX400 Blade Server Management A i Station se gr te Management LAN Switch errs Productive LAN Switch E Management Port Management LAN Productive LAN MMB Management Blade CB Connection Blade Figure 16 BX400 Network Overview The I O connection blades must be connected to the central management sta tion via their management port Switch stacking support A stacking function is a group set of I
56. item PRIMERGY ServerView Links This opens the start page of the ServerView link collection 3 Viathe ServerView Suite DVD 1 e Inthe start window of the ServerView Suite DVD 1 select the option Select ServerView Software Products e Click Start This takes you to the page with the software products of the ServerView Suite e Onthe menu bar select Links This opens the start page of the ServerView link collection Documentation for the ServerView Suite The documentation for the ServerView Suite can be found on the ServerView Suite DVD 2 supplied with each server system The documentation can also be downloaded free of charge from the Internet You will find the online documentation at http manuals ts fujitsu com under the link Industry standard servers For an overview of the documentation to be found under ServerView Suite as well as the filing structure see the ServerView Suite sitemap Server View Suite Site Overview ServerView Virtual lO Manager 23 1 Introduction Typographic conventions The following typographic conventions are used Indicates various types of risk namely health risks risk of data loss and risk of damage to devices D Indicates additional relevant information and tips Indicates references to names of interface elements Indicates system output and system elements e g file names and paths monospace ndicates statements that are to be entered using the keyboard semibold blue
57. of the listed address ranges for virtual MAC FU I SU addresses or define your own custom address range MAC Address Range Property Description MAC Address Range 1 MAC Address Range 2 00 19 99 3E D2 A1 00 19 99 3E F1 E0 MAC Address Range 3 MAC Address Range 4 MAC Address Range 5 MAC Address Range 6 MAC Address Range 7 MAAC idoroco Danan 2 v Custom MAC Address Range Parameters Start Address 00 19 99 3E D2 A1 End Address 00 19 99 3E F1 E0 lt Back Next gt Cancel In this window specify which address range the Virtual IO Manager should use for virtual MAC addresses The virtual MAC addresses are assigned automatically in a profile for the LAN ports during the server pro file definition 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 If sucha range is insufficient you can also select a range double the size using MAC Address Range 1 and 2to MAC Address Range 7 and 8 Each of these areas contains 16000 MAC addresses If you have an address range of your own that you wish to use for virtual MAC addresses then select it in the Custom MAC Address Range drop down menu In this case the fields in Custom MAC Address Range Parameters in which you can enter the start and end MAC address of the address range become active ServerView Virtual lO Manager 3 4
58. of the server is not off you can switch it off by clicking Shut down or by selecting Shutdown in the context menu 1 Click Shutdown in the context menu or click the Shutdown button 2 Inthe next dialog box select the type of shutdown Graceful Shut down or Forced Power Off 3 If you confirm your selection the server is switched off D You can update the display in the State column by clicking D Update States button or with Update State in the context menu Click Assign Profile or select Assign Profile in the context menu of the required slot The Select Profile dialog box opens In this dialog box select the required server profile in the tree structure The area on the right displays information on the selected profile 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 e Ignore ext LAN connections e Ignore Spare e Skip downlink checks ServerView Virtual lO Manager 297 9 7 9 Defining and assigning server profiles 8 Confirm your selection with OK The selected server profile is assigned to the slot D 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 D If the server profile is already assigned to another slot or PRIMERG
59. on page 296 e The spare blade only assumes the role of the failed server blade if the VIOM server profile also contains the boot settings e g FC boot settings and if the spare blade is suitable for boot ing the same operating system as booted by the original blade The Virtual lO Manager does not make any changes to the oper ating system 13 3 Disaster Recovery Ina disaster recovery scenario meaning you have two generally identical sites and if one fails you restart all or at least the most important applications on the other site the server profile assignment feature may be used to move the application from one site to the other as illustrated in the following dia grams ServerView Virtual lO Manager 333 13 VIOM scenarios Chassis ASlot 1 profileA Chassis ASlot 2 ProfileB Chassis ASlot 3 VIOM DB Primary site ProfileC Secondary site Chassis A exe Slot 1 profileA Slot 2 ProfileB Siot s ProfileC Chassis B MMB Primary site Chassis B Slot 1 profileA Chassis B Slot 2 ProfileB Chassis B Slot 3 ProfileC Secondary site Chassis B A P Profiles soe agnc Slot 1 profileA r Slot 2 profileB Slot 3 profileC This means you shut down the blade on the failed site unassign the profile and assign it again on the other site But this on
60. parameter is set to automatic so that the management blade automatically generates the inventory information required by VIOM when the server blade is insert ed VIOM needs this inventory information specifically for the server blades that support the I O virtualization To check the parameter setting in the Remote Manager of the man agement blade choose 1 Management Agent 3 System Infor mation 10 Automatic Inventory Retrieval To check the parameter setting in the Web interface open the Com ponents section and select System System Unit The System Infor mation section on the right contains the option Automatic Inventory Retrieval If the value of this is not set to automatic please set it to 122 ServerView Virtual lO Manager 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 e Toensure 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 3 Configuring the I O connection blades The connection blades in fabric 1 and the optional connection blades in fabric 2 3 and 4 must be configured and connected to the local network so that they can be accessed from the central management station on which the ServerView Operations Manager and VIOM are installed
61. 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 Other wise the procedure is the same as above see Refuse existingAddressAction optional Specifies the response if a virtual address is already in use If this attrib ute is specified it overwrites the value from the ServerProfiles element 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 profile It contains the following elements ServerView Virtual lO Manager 317 12 Importing and exporting server profiles ServerProfileName Name of the server profile lOVirtualizationUsage Yes The profile uses virtual addresses You must specify the Address Virtualization element in all OChannel elements of this profile No The profile does not use any virtual addresses You must not spec ify the AddressVirtualization element in any OChannel element of this profile BootMenuUsage Yes The VIOM boot settings can be overwritten on your local computer No The VIOM boot settings are prevented from being overwritten on your l
62. shown with a red background ServerView Virtual lO Manager 91 3 Installation and uninstallation 2 Click Register new license Register new license J xj Please enter license string canca Enter a valid license here You can also enter several licenses by click ing Register new license again Each license contains a number of assigns This license permits you to assign this number of server pro files Licenses purchased with Virtual IO Manager versions prior to V2 4 are also still valid These licenses v1 contain a chassis count which is mul tiplied by 18 to get the assign count used in licenses v2 purchased with Virtual lO Manager V2 4 or later 3 Click Exit in the VIOM License Manager dialog box to exit the License Manager D On Linux you can also add a licence without graphical user inter face cd opt fujitsu ServerViewSuite plugins viom Manager sh license sh license key lt key gt no gui You can also delete licenses provided that the total number of assignments of the remaining licenses is not smaller than the number of server profiles assigned To do this launch the License Manager from the Windows Start Menu or with the license sh script 1 On Windows Choose Start All Programs Fujitsu ServerView Suite Virtual lO Manager License Management On Linux Execute the command sh license sh 92 ServerView Virtual lO Manager 3 6 License management EA 10M Licen
63. the HBA to send its requests It should be specified only for CNA iSCSl 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 SubnetMask Only when DHCPUsage is No The IP subnet mask This should be the IP subnet mask of the net work used to connect this port in the case of an iSCSI boot Gateway IPv4Address Only when DHCPUsage is No The IP address of the network gateway This is necessary if the iSCSI target is in a subnetwork other than the subnetwork of the selected iSCSI boot port If no gateway is used 0 0 0 0 can be spec ified as IP address of gateway ISCSITarget Specifies the values of the iSCSI target This element contains the fol lowing elements ServerView Virtual lO Manager 325 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 stat ic SCSI LUN ID Name Only when DHCPUsage is No The IQN name of the iSCSI target IPv4Address Only when DHCPUsage is No The IP address of the iSCSI target PortNumber Optional only if DHCPUsage is No TCP port number
64. the scroll bar to reach the uplink ports of another stack member The context menu can contain the following menu items Add Only activated if the port is not yet assigned to the uplink set Assigns the port to the uplink set If the port is already assigned to another uplink set this assignment is deleted Add as Backup Only activated if the port is not yet assigned to the uplink set 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 ServerView Virtual lO Manager 171 5 Virtual lO 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 col ors in the display light red light green or dark red dark green The name of the uplink set is assigned to configured ports which you can rec ognize by this D With PY CB Eth Switch IBP 1Gb 36 8 2 connection blades 1GB uplinks and 10 Gb uplinks must not be mixed If you try this the Next and Finish buttons will not be enabled D The Next and Finish buttons are disabled
65. 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 In the Authentication dialog box you enter the data for authentication e g user names passwords ports which VIOM can use to access the selected 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 Restore Use the Restore button to write the configuration and virtualization data virtual I O addresses and possibly also boot parameters saved inter nally in VIOM database to all IBP modules and slots of the selected blade server For the selected PRIMERGY rack servers the vir tualization data are rewritten Restore Slot blade server only front side slot selected If you select a slot you can use the Restore Slot button to rewrite the virtualization data virtual I O addresses and possibly also boot param eters of the assigned profile if a problem occurs Restore IBP
66. will then create a trace file for each connection blade configuration command These files are written to the directory lt ServerView Suite gt plugins viom Manager logs The ServerView Virtual lO 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 auto matically deleted 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 lt ServerView Suite gt plugins viom Manager In some cases it might be necessary to increase the number of log files in order to keep trace information for a longer period of time If so please modify the line log4j appender DebugAppender MaxBackupI ndex 25 and set the property MaxBackupIndex to an appropriate value Depending on the amount of requests sent to the Virtual lO Manager service it might be nec essary to set this value to 50 or even higher if you want to keep log infor mation for about one week The property MaxFileSize should not be increased because it might make it difficult to load files into an editor ServerView Virtual lO Manager 357 15 Appendix After modifying the StartOptions property in the Viom Config properties file or the MaxBackupIndex property in the man log4j properties file the service Server ViewVirtuallOManagerService must be restarted
67. 0 If the first uplink port 0 11 belongs to the uplink set 1_NET but no port group 108 ServerView Virtual lIO Manager 4 2 4 2 Configurations on the managed BX400 Blade Server is assigned to this uplink set because for example 1_NET is to be deleted then you can restore the LAN connection to the IBP by adding the port to the standard uplink set Enter the following commands Vty 0 configure Vty 0 Config interface 0 11 Vty 0 Interface 0 11 uplink set default Vty 0 Interface 0 11 exit Vty 0 Config exit Vty 0 In these cases however the configuration used from VIOM no longer matches the actual configuration In this case you should use the VIOM user interface for the affected IBP module to restore the configuration e Todo this go to the Setup tab and click the affected IBP module in the rear view of the blade server chassis The details for the IBP module and the Restore IBP button are then dis played at the bottom on the right e Click the Restore IBP button The IBP module is then programmed according to the configuration saved in VIOM Configurations on the managed BX400 Blade Server In section Supported hardware configurations for the connection blades on page 110 you can find out what combinations of I O connection blades are supported by VIOM To manage a blade server with VIOM you must carry out the following pre paratory steps e Configure the management blade or ma
68. 0 12 Ext 2 0 5 Server Blade 5 0 13 Ext 3 0 6 Server Blade 6 0 14 Ext 4 0 7 Server Blade 7 0 15 Ext 5 0 8 Server Blade 8 0 16 Ext 6 0 9 Server Blade 9 0 10 Server Blade 10 Uplink set default Ports 0 11 0 12 0 16 Port group default Ports 0 1 0 2 0 3 0 10 Figure 75 Standard configuration of the IBP 10 6 before activation In this configuration all server blades are linked with the standard uplink set The six uplink ports together form a LAG ServerView Virtual lO Manager 263 7 Managing servers with VIOM Initial configuration after activating VIOM management 0 1 Server Blade 1 0 2 Server Blade 2 0 3 Server Blade 3 0 11 Ext 4 0 4 Server Blade 4 0 12 Ext 2 0 5 Server Blade 5 0 13 Ext 3 0 6 Server Blade 6 0 14 Ext 4 0 7 Server Blade 7 0 15 Ext 5 0 8 Server Blade8 0 16 Ext 6 0 9 Server Blade9 0 10 Server Blade 10 _ Uplink set default Ports 0 11 Port group default Ports none 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 cen tral management station is connected must be connected to this first uplink port In the case of the LAN connection blades of the BX400
69. 1 22 11 222 S VIOM Managed MMB firmware 4 893 inza no spares _unmanage Restore _ Authentication E Lokales Intranet Figure 26 Setup tab The Setup tab contains information on the servers selected in Server List The table contains one entry for each of the blade or PRIMERGY rack servers selected in the server list For selected server blades the cor 144 ServerView Virtual IO Manager 5 3 Tabs responding blade server is shown The table provides the following infor mation Admin IP IP address to administrate the server Causes Causes For the possible values and its meaning see the table below If asingle server is selected in the table above the table there are more details about this server available e The front and rear rear only for blade server according to the actual con figuration e Information on the model e The IP address and firmware version of the management blade or PRIM ERGY rack server e The number of spare slots defined for blade servers only e State causes for PRIMERGY rack servers only If a single blade server is selected in the table slots can be selected in the graphic to get more information about the slot the server blade or switch blade which is plugged into this slot e Number of slot or connection bay e Stacking info if available e Product name if selected slot is not empty e P address if available e BIOS version for server blad
70. 2 222 2222 21 1 5 ServerView Suite link collection 020 00222 2222 21 1 6 Documentation for the ServerView Suite 20 2 23 1 7 Typographic conventions 2 20200 e ee eeeee eee eeeeeee 24 2 Virtual lO Manager Introduction 222 2222200 25 2 1 Virtual addresses 2 2 2 00 e cece 25 2 2 Special connection blade for blade server 22 2222222222 25 2 3 Management with VIOM Procedure 2 22 2222 28 2 4 Defining networks LAN for blade servers only 30 2 5 Server profiles 2 2 2 0 ccc c eee e cece ccceeeeccececeees 43 2 5 1 Defining server profiles 00 002 20000 cee eee eeee ee eee 44 2 5 2 Assigning server profiles 0 0 2 20000 e cece eee 44 2 5 3 Dedicated LAN connections only for blade servers 45 2 5 4 Virtualizing I O parameters 222000 eee cece eee cece 45 2 6 Server profile failover for blade servers only 47 2 7 High Availability HA Support 222 00000 c cece eee eee eee 48 3 Installation and uninstallation 2 22222222222 57 3 1 Prerequisites for the VIOM installation 202222222222222 57 3 2 Installing the Virtual lO Manager on a Windows based CMS 58 3 2 1 Installing the Virtual IO Manager using a graphical interface 59 3 2 2 Installing the Virtual IO Manager using
71. 2 Name of the profile profile2 Select type of profile Virtual Addresses Server Blade Contr Server Blade double height Other PRIMERGY Server Preset values to use for server type Comment Finish Cancel Help 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 Other PRIMERGY Server The profile can be assigned to a PRIMERGY rack server Preset values to use for server type Server model optional 206 ServerView Virtual lO Manager 5 4 Wizards The number and type of LAN ports under Onboard IO channels are adjusted automatically according to the server model you select The number of LAN ports and mezzanine PCI cards cannot exceed the max imum possible value for the selected server model Comment Comments on a more detailed description of the profile optional 5 4 4 2 Configure Cards step Edit Server Profile wizard Configure Cards is the next step in the Edit Server Profile wizard Inthis step you specify the number and type of mezzanine cards as well as the number of I O channels for each ca
72. 3 1 This element can also have the following optional attribute errorAction Specifies whether the import will continue if an error occurs The value can be overwritten in lower level elements Possible values are Abort Default The first error aborts the entire import Continue Errors are converted into wamings The import then continues with the next object 314 ServerView Virtual lO Manager 12 3 Format of export files The Objects element contains the following elements e UserlInfo optional e ServerProfiles Describes the profiles to be imported see below 12 3 2 The ServerProfiles element The ServerProfiles element can have the following optional attributes errorAction Specifies whether the import will continue if an error occurs If this attrib ute is specified it overwrites the value from the Objects element For individual server profiles the value in the corresponding ServerProfile element can be overwritten Possible values are Abort The first error aborts the entire import Continue Errors are converted into wamings and the import then continues with the next object existingProfileAction Specifies the response if a server profile to be imported already exists For individual server profiles the value in the corresponding Server Profile element can be overwritten Possible values are Refuse Default Handled in accordance with the current error behavior See errorAction Replace An exis
73. 3 3 Configuring the I O connection blades 2 2222 123 4 ServerView Virtual lO Manager Contents 4 3 4 Connecting IBP modules 0 0 2 eee eee 126 4 3 4 1 Network Overview 22222 220 2222 eee eee ee eee 126 4 3 5 Switch stacking support 0 00000000 0c 127 4 4 Configurations on the managed PRIMERGY rack server 129 4 5 VIOM server profile mapping 0 02 2222 ee eee 132 4 6 PCI slot location in PRIMERGY rack servers 133 4 7 Adding a server to the ServerView server list 135 5 Virtual lO Manager user interface 22 137 5 1 Virtual lO Manager main window eeeeeeeeeeeees 137 S2 Tree VICW scr eo th aae rs ds de yon us e aee anea 139 5 2 1 Tree structure Server List 00 0000cc0 cece eee eee eee 140 5 2 2 Tree structure Profiles 0 0 00c cece eee ee eee e eee ee 141 5S ADS heats Condit eee ao ae de tele ee E Eo cee 142 5 3 1 Virtual lO Manager tab 2 20 22 occ e eee eee eee 142 5 3 2 Setup tab oo say cere dee T soe eddies 144 5 3 3 Ext LAN Connections tab 22 22 cece cece eee eeee 148 5 3 3 1 Graphic tab on Ext LAN Connections tab 148 5 3 3 2 Details tab on Ext LAN Connections tab 150 5 3 4 Server Configuration tab 0 0 0 0 e eee cece eee eee 151 5 3 5 Chassis Configurat
74. 3 Installation and uninstallation 7 Click Next ie Fujitsu Server iew irtual IO Manager Setup oix License Agreement You must agree with the license agreement below to proceed FUJITSU Fujitsu Technology Solutions Software License Agreement for End Users 1 Subject of this Agreement 1 1 Forthe purposes of this agreement Software shall mean the software with the object code the version and the specification indicated in the software product data sheet of Fujitsu Technology Solutions The Software consists of machine readable instructions and or printed documentation and related licensed materials A w ae ooa E accept the license agreement Ido not accept the license agreement Aise Installation Vizard R Reset lt Back Cancel Accept the license agreement by selecting the corresponding option ServerView Virtual IO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS 8 Click Next ie Fujitsu Server iew irtual IO Manager Setup User Information TS Enter the following information to personalize your installation FU I U Full Name user Organization Fujitsu Technology Solutions The settings for this application can be installed for the current user or for all users that share this computer You must have administrator rights to install the settings for all users Install this application for Anyone who uses this computer Only for me Aise I
75. 6 12 in IBP 36 12 in IBP mode mode optional PY CB Eth Switch IBP 1Gb 18 6 PY CB Eth Switch IBP 1Gb 18 6 in IBP in IBP mode mode optional PY CB Eth Switch IBP 10 PY CB Eth Switch IBP 10 Gb 18 8 in Gb18 8 in IBP mode IBP mode optional 1 Even though this constellation is possible it does not make sense because only the first port can be used from the IBP module in bay 1 3 5 or 7 Operation in Open Fabric mode Open Fabric mode refers to the use of non VIOM capable LAN modules together with the Virtual lO Manager In this case you can only work with vir tual I O parameters and not with dedicated network connections Therefore if you do not want to use any routing all combinations are possible even with non VIOM capable I O connection blades You must take the fol lowing into account e You cannot mix LAN and IBP modules within a fabric e Youcan only assign profiles if no networks are defined for their ports D You can force the assignment of a profile with network def z initions by selecting the Ignore ext LAN connections option in the profile selection dialog box or by answering the sub sequent query accordingly In doing so however the network definitions are ignored e You can operate LAN models of different sizes within a fabric although you cannot use all download links from the larger model 120 ServerView Virtual IO Manager 4 3 Configurations on the managed BX900 Blade Server 4 3 1 2 Fibre Channel
76. As a result there are different ways of configuring an uplink set e 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 In this case the active port switches to the backup port if an error occurs linkdown event for all active ports In the figure shown this could be the uplink sets 1 and 2 if for each of these one port of the uplink set is configured as an active port and one port as a backup port e Link aggregation group By grouping several active uplink ports in one uplink set a link ServerView Virtual lO Manager 33 2 Virtual IO Manager Introduction aggregation group LAG is formed By providing several parallel con nections you achieve higher level of availability and a greater con nection capacity In the figure above this could be the uplink sets 1 and 2 if both uplink ports of these uplink sets are configured as active ports If an uplink set has several backup ports these backup ports also form a link aggregation group automatically in the case of a failover It is essen tial that the ports of an external LAN switch which are linked to a LAG form a static LAG Using VIOM it is possible to define a number of networks e Internal networks Internal network e Single networks Single network e Virtual networks with VLAN IDs VLAN networks e Virtual networks with
77. BP 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 The stacking software configures each device tables and registers to support all switching functions for example switching link aggregation port ServerView Virtual lO Manager 117 4 3 4 Configuration monitoring spanning tree protocol VLAN etc The entire stack will appear as asingle IBP You find a detailed description about Switch Stacking in the manual PRIM ERGY BX900 Blade Server Systems Ethernet Connection Blade Module IBP version User s Guide chapter 6 VIOM supports uplink sets and networks on switch stacks 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 Then all members of this stack are highlighted the stack master is yellow shaded all other members are green shaded Beside this Stack Master or Stack Member is shown in the details area To define modify or delete uplink sets and networks in a stack select one stack member and start the desired operation Details can be found in Defin ing network paths LAN on page 277 Configurations on the managed BX900 Blade Server In section Supported hardware configurations for the connection blades on page 119 you
78. BX900 which support an IBP mode currently 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 none of the uplink ports has a con nection after VIOM management is activated These modules must be 264 ServerView Virtual lO Manager 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 Inthe 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 lO Manager for a blade server chassis the following actions are executed internally 1 The initial state see figure Standard configuration of the IBP 10 6 before activation on page 263 is restored for the IBP modules In detail this means e First all defined networks and uplink sets apart from the standard uplink set are deleted e The downlink ports are connected to the standard uplink set e All uplink ports are added to the standard uplink set as active ports In doing this you have to note that the uplink ports form a LAG Before you deactivate management with the Virtual IO Manager it is essential that you therefore first remove all the LAN cables except for the one connected to the first uplink port 2 Inthe management blade any existing virtual
79. CP DHCP Client Name SNAS NIA IP Address l 411 22 221 122 Subnet Mask 255 255 254 0 Gateway Address l 111 22 220 1 apy The settings will be effective after 3 minutes Login Settings Status Overview Asset Overview Logging Components Chassis Management Blades Period Polling Server Blades 7 Gitconneciion Bases Login User Name GhE IBP Blade 1 GbE IBP Blacle 2 FC Switch Blade 3 FC Switch Blade 4 Power Supplies Dicital KVM Blade Login Password Polling Password You configure the network parameters of an I O connection blade as follows e InDHCP 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 e Click Apply to activate the settings 102 ServerView Virtual lO Manager 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 X Telnet 111 22 222 121 http 111 22 221 122 7 Status ok Manufacture FSC Manufacture Date gt 68 31 7200 05 01 08 Serial Number Q735LU66006 Product Name BK66 GbE Intelligent Blade Panel 30 12 Model Name A3C4069 6649 Hardware Version 1 6 Firmware Version 2 08 MAC Address 66 1B 24 78 54 B IP Mode NO DHCP DHCP Client Name N A IP Ad
80. Configuration tab in the area on the right 4 Select the server blade in the table that is to assume the tasks of the faul ty server blade ServerView Virtual lO Manager 331 13 VIOM scenarios 5 You can only assign a server profile to a server blade if the server blade is shut down Therefore shut the server blade down if applicable by clicking Shut down or by selecting Shutdown in the context menu You can see the state of a server blade in the State column To see the current power state you may need to update the display using the Update States but ton or with Update State in the context menu 6 Click Assign Profile or select Assign Profile in the context menu of the required server blade The Select Profile dialog box opens see Select Profile dialog box on page 245 7 Select the server profile of the faulty server blade in the tree structure The area on the right displays information on the selected profile Con firm your selection with OK A message appears asking if you wish to delete the assignment If you confirm this then the previous assignment is deleted and the profile is assigned to the new server blade The display on the Server Configuration tab is updated accordingly 8 Then switch the server blade back on using the Boot button The new server blade can then assume the tasks of the previous one without any restrictions 13 2 Moving tasks using the server profile failover Tasks can also be moved fr
81. D 2A 10 00 End Address 50 01 99 93 EF 1E 0D FF lt Back Next gt Cancel ServerView Virtual lO Manager 81 3 Installation and uninstallation In this window specify which address range the Virtual lIO 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 anda WWNN World Wide Node Name Eight predefined WWN address ranges are available for selection which do not overlap WWN Address Range 1 to WWN Address Range 8 Each individual address range contains 32 767 487 WWN addresses If you have an address range of your own that you wish to use for virtual WWN addresses then select it in the Custom WWN Range drop down menu In this case the fields in Custom WWN Address Range Param eters in which you can enter the start and end WWN address become active D The validity of the WWN address input is not checked Please confirm that your input address is valid before you click Next D If you have several installations of the Virtual lO Manager in S9 your Storage network then you must ensure that the address ranges used do not overlap Otherwise addresses may be assigned several times q Tochange the range of the address after installation is finished 7 you must uninstall the Virtual lO Man
82. FC Target 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 You can specify the following values 0 auto negotiate The transmission speed is negotiated with the external switch 1 1 Gbit s full duplex 2 2 Gbit s full duplex 4 4 Gbit s full duplex 8 8 Gbit s full duplex FC Topology Specifies the type of port connection with the external SAN network You can specify the following values 0 auto loop first 328 ServerView Virtual lO Manager 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 10The FunctionConfiguration element The FunctionC onfiguration element specifies function specific attributes FunctionBandwidth The share of the bandwidth in percent that is reserved for this function If the sum of all bandwidths of one O channel is not 100 the values are internally adjusted accordingly F
83. GUI runs These backup files contain the configurations networks uplink sets assigned profiles spare slot definitions of one or several chassis and or pro files You save and restore backup files as well as delete them on the man agement station using a wizard You launch the wizard using the Con figuration Backup Restore button on the Virtual lO Manager tab Saving your configuration and server profiles The starting point for backing up your configuration and server profiles is the Virtual lO Manager tab 1 Launch the wizard using the Configuration Backup Restore button 2 Select Save Configuration in the first step of the wizard to save the con figuration in a file Click Next to go to the Select File step 4 Select the computer on which you want to save the configuration e Select Save on Management Station to save the configuration to the management station e Select Save local to save the configuration in a file on the computer on which the GUI runs 5 When you select Save on Management Station you save the con figuration to the central management system There are two ways of specifying the backup file ServerView Virtual lO Manager 303 11 2 11 Saving and restoring e Select an existing file from the list that will then be overwritten e 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
84. I O connection blade e g 1 Console Redirect GbE IBP Blade 1 You are now connected to the selected I O connection blade To access the connection blade from the central management station the first uplink port must belong to an uplink set to which a port group is also assigned You can find out what the current settings are by entering the commands show uplink set and show port group ServerView Virtual lO Manager 107 4 Configuration Example Vty 0 show uplink set External backup ports Link state Port IGMP Backup snoop LACP Uplink External External Set Name ports active ports default 1_NET 0 11 0 11 1_NW1 0 12 0 13 0 14 0 13 0 14 1_NW2 0 15 0 16 0 15 Vty 0 Vty 0 show port group Port Group Name Internal Ports default 1_INTERN 1 1_INTERN 2 1_NET 0 1 0 2 1_NW1 1_NW2 0 12 0 16 yes yes yes yes Uplink Set Name default 1_NET 1_NW1 1_NW2 no yes no yes yes no yes yes no yes yes no External Ports 0711 0 12 0 13 0 14 0 15 0 16 In the above example the first uplink port 0 11 belongs to the uplink set 1_ NET and the port group 1_NET is assigned to this uplink set If port 0 11 does not belong to any uplink set but should belong to uplink set 1_NET then enter the following commands Vty 0 configure Vty 0 Config interface 0 11 Vty 0 Interface 0 11 uplink set 1 NET Vty 0 Interface 0 11 exit Vty 0 Config exit Vty
85. 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 Select Save local to save the configuration in a file on the computer on which the GUI runs There are two ways of specifying the backup file e Enter the name for the backup file directly in the input field On Win dows if you do not specify a complete path including drive letter the file will be saved on the desktop e Click Browse to open the file selection dialog box in which you can navigate to the desired folder and select an existing backup file or specify the name of the backup file If the file exists it will be over written 7 Once you have specified a backup file click Next to go to the Select Data step of the wizard 8 In Select servers to save select the servers whose configuration you wish to save Do not select any servers if you only wish to save profiles 9 Select Save Profiles to specify whether server profiles are to be saved too D It is essential that you save the profiles along with the configuration p if the assigned profiles are to be reassigned once the configuration has been restored Restoring the configuration The starting point for restoring a configuration is the Virtual IO Manager tab 1 Launch the relevant wizard using the Configuration Backup Restore button 2 Select Restore Configuration to restore a configuration
86. Isolate mode You activate the isolate mode via Isolate mode With isolate mode acti vated server blades in the same chassis that use the same network can not communicate with each other but only with an external device though the uplinks This checkbox is not shown if the connection blade does not support iso late mode Add button Adds the virtual LAN network to the table below Table You can also define a network as a native VLAN or service VLAN and set the isolate mode in the table retrospectively Native VLAN Select the checkbox in the corresponding row under Native VLAN in the table to define a network as a native VLAN 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 ServerView Virtual lO Manager 175 5 4 2 5 4 2 1 5 Virtual lO 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 Edit Uplink Set wizard You use the Edit Uplink Set wizard to modify an defined uplink set The Edit Uplink Set wizard comprises several dialog boxe
87. LACP IGMP Snooping CO Isolate mode Ports for this uplink set change with right click Bx900 1 Connection Bay 3 BX900 1 S03 Dz EJ 2c Uplink set contains 2 ports 0 backup Previous Next Finish Cancel Help Figure 34 Create Network wizard second step Name of uplink set Name of uplink set In the case of a single network the network auto matically has the same name Activate Port Backup Switch to a backup port if an error occurs in the active port The port backup function is only available if at least one backup port is ServerView Virtual lO Manager 165 5 Virtual lO Manager user interface configured By default Activate Port Backup is selected Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail The linkdown event triggers a failover process on the server blade if con figured accordingly 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 link down 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 con nection to remain intact In order for the failover process in the server blade to work from LAN port 1 to LAN port 2 aLAN te
88. M enabled flag in the iRMC is reset indicating that the server is no longer VIOM managed This action invalidates the VIOM inventory data in the iIRMC 5 IfaVIOM server profile was assigned to this server an init boot is ini tiated With this action the virtualization of I O addresses is deactivated so the original manufacturer addresses are activated again Also the boot priorities set in the server profile are no longer valid 274 ServerView Virtual lIO Manager 7 6 7 6 Displaying license information Displaying license information You use the Show Licenses button on the Virtual lIO Manager tab to request information on the licenses assigned 1 Todo this click the Show Licenses button on the Virtual lO Manager tab The Licenses Information dialog box opens 2 Click OK to close the Licenses Information dialog box The information displayed includes the following e The total number of server profiles that can be assigned using VIOM with the license entered e The number of server profiles already assigned with the license e The number of server profiles that may still be assigned with the license If the permitted total number of licenses has been reached you cannot assign any more server profiles Further assignment Assign Profile is denied and a corresponding error message is displayed The only two pos sibilities for still assigning another server profile are e tounassign another server profile or e tospecify ano
89. MC firmware version see the release notes supplied D The Virtual lO Manager can only manage BX600 chassis with S3 E management blades MMB S3 that are assembled with the fol lowing e Infabric 1 IBP or LAN modules e In fabric 2 IBP modules LAN modules or FC switch blades of the type SW4016 You must not mix the modules within a fabric Fabric 2 can also be empty Only one of the permitted connection blades can be inserted in fabric 1 and 2 at each time 14 ServerView Virtual IO Manager 1 3 Supported Hardware D In Japan BX600 blade servers are not supported Managed BX400 blade servers Supported systems BX400 with MMB S1 For information on the required firmware version see the release notes supplied The following table shows which server blades are supported with which range of functions Server Scope of functions BX920 S2 Server profiles with I O virtualization and network connection BX920 S3 definition BX922 S2 Server profiles with I O virtualization and network connection definition BX924 S2 Server profiles with I O virtualization and network connection BX924 S3 definition Table 2 Supported server blades For information on the BIOS and iRMC firmware version see the release notes supplied ServerView Virtual lO Manager 15 1 Introduction D The Virtual IO Manager can only manage BX400 chassis with S1 gt management blades MMB 1 that are assembled with the fol lowing e Infabri
90. MERGY rack server It is also important that the members of a stack have a unique user assigned name in the MMB and that the stack member IDs of the par ticipating connection blades are set to 1 before building the stack The typical procedure for correct handling by VIOM is e 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 e Check that the blade server management blade correctly shows the stat us of the stack For this it is important that all members of the stack show the same IP address which must be the IP address of the stack master The stacking status in MMB must be Master for exactly one member of the stack and must be Member for all other members of the stack As long as these two conditions are not fulfilled VIOM will not be able to handle the stack correctly e Update the information for this blade server chassis in ServerView Oper ations Manager by performing the explore action for the blade server chassis e Perform the Refresh action in VIOM user interface so that also VIOM has the updated information about the changed configuration The last two actions will also be done automatically when waiting about two or three minutes this also depends on the refresh interval configured in ServerView Operations Manager It is not supported to change the stack configuration while the
91. OM package create one e g root VIOM_3 1 0 and copy the zip file e g VIOM_ 3 1 0 2012 08 15 zip from the installation medium to that directory and unzip it mkdir root VIOM 3 1 0 cp VIOM_3 1 0 2012 08 15 zip root VIOM 3 1 0 cd root VIOM_ 3 1 0 unzip VIOM 3 1 0 2012 08 15 zip ServerView Virtual lO Manager 3 4 Installing the Virtual lO 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 8 Fujitsu ServerView Virtual IO Manager Setup Welcome to the Fujitsu ServerView Virtual l1O Manager Installation Wizard Click Next to continue the installation WARNING This program is protected by copyright law and international treaties Unauthorized reproduction or distribution of this program or any portion of it may result in severe civil and criminal penalties and will be prosecuted to the maximum extent possible under law PRIMECENTER ServerView Virtual lO Manager 75 3 Installation and uninstallation 4 Click Next 8 Fujitsu ServerView Virtual IO Manager Setup License agreement c You must agree with the license agreement belowto proceed FUJI l SU Fujitsu Technology Solutions Software License Agreement for End Users 1 Subject of this Agreement 1 1 Forthe purposes of this agreement OSoftwareO shall mean the software with the object code the version and the specification indicated in th
92. PRIMERGY rack server Configure protocols Expands the dialog box so that you can also specifiy the protocol and the port to be used by VIOM to access the PRIMERGY rack server s These values should not be changed in a standard configuration Protocol Select the protocol to be used for communication with the PRIMERGY rack servers Port If Use default port is not checked you have the option of specifying other port numbers for the PRIMERGY rack servers in this field ServerView Virtual lO Manager 235 5 Virtual lO Manager user interface Use default port Uses the default port The default port is dependent on the protocol and the relevant module Fora 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 This dialog box varies depending on what you have selected in the table on the Setup tab If you select several servers with at least one blade server in this table you only specify one user name and password These will be used for all MMBs and IBPs of all selected blade servers and for all selected PRIMERGY rack servers For protocol port and trap destination the default values are used If this situation is not suitable for you pleas
93. PRIMERGY rack server configurations 1 To restore PRIMERGY rack server configurations select the cor responding PRIMERGY rack server in the Select Data step The Reassign Profiles option is automatically selected and cannot be deselected This means that the profiles which were assigned when the backup was performed are reassigned You cannot specify more options for restoring a PRIMERGY rack server If Profiles is not selected in the Select Data step of the Restore Configuration wizard it is selected automatically when you select a PRIMERGY rack server In this case the Restore only reassigned profiles option will be selected for pro files see section Restore Options dialog box server profiles on page 243 ServerView Virtual lO Manager 307 11 3 11 4 11 4 1 11 Saving and restoring Deleting backup files on the management station The starting point for deleting backup files on the management station is the Virtual lO 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 To do this select the corresponding files in the list Using the Select All and Clear Selection buttons you can select or deselect all the files 4 Click Next to revie
94. RHEL 6 6 1 6 2 ServerView Virtual lO Manager 57 3 2 3 Installation and uninstallation D In Japan Novell SLES is not supported ServerView Virtual lO Manager can also be installed in Virtual Machine VM under Windows Hyper V or VMware ESX server The operating system running on the VM must be one of the above listed operating sys tems and must be supported by the used hypervisor e Installed software packages o ServerView Operations Manager as of Version 5 50 13 o Java Runtime Environment JRE version 6 0 update 31 or higher D Together with ServerView Operations Manager 6 10 it is B also possible to use JRE version 7 0 update 7 or higher e Fire wall settings o Port 3172 must be opened for TCP IP connection to Remote Con nector Service o Port 162 must be opened to receive SNMP traps from iRMC when managing PRIMERGY rack servers You can also obtain the current requirements from the release notes You find the release notes e g on a Windows based management station under Start All Programs Fujitsu ServerView Suite Virtual lO Manager Release Notes Installing the Virtual lO Manager on a Windows based CMS The corresponding software is supplied with the PRIMERGY ServerView Suite DVD1 You can find the entire software for the PRIMERGY Server View Suite under ServerView Software Product Selection To find the Vir tual lO Manager software package SV_VIOM exe in this product selection choose ServerView
95. Range 8 0 01 99 93 F 4 D6 02 00 50 01 99 93 FC C4 00 00 WAN Address Range 5 WAN Address Range 6 WAN Address Range 7 WAN Address Range 8 ees J OOO End Address LI O C L LJ L Wise Installation Wizard Back Cancel 64 ServerView Virtual IO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS In this window specify which address range the Virtual lIO 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 anda WWNN World Wide Node Name Eight predefined WWN address ranges are available for selection which do not overlap WWN Address Range 1 to WWN Address Range 8 Each individual address range contains 32 767 487 WWN addresses If you have an address range of your own that you wish to use for virtual WWN addresses then select it in the Custom WWN Range drop down menu In this case the fields in Custom WWN Address Range Param eters in which you can enter the start and end WWN address become active D The validity of the WWN address input is not checked Please confirm that your input address is valid before you click Next D If you have several installations of the Virtual lO Manager in S9 your Storage network then you must ensure that the addre
96. Restoring PRIMERGY rack server configurations 307 11 3 Deleting backup files on the management station 308 11 4 Restoring VIOM specific configurations 308 11 4 1 Restoring an IBP module configuration 308 11 4 2 Deleting the configuration of an uninstalled IBP module 309 11 4 3 Restoring the configuration of a server blade slot 310 11 4 4 Restoring the blade server chassis configuration 311 12 Importing and exporting server profiles 0 000000000000 313 12 1 Exporting server profiles 000000 0000022222 cece cece eee ee ee 313 12 2 Importing server profiles 22 22 0022 e eee eee ee ee 313 12 3 Format of export files 22 0 000222222 c cece ee eee cece eee 314 12 3 1 The Objects element 0000 00000002222 c cece cece 314 12 3 2 The ServerProfiles element 222222 315 12 3 3 The ServerProfile element 002 2022222ee eee 316 12 3 4 The l OChannel element 2222222 222222 319 12 3 5 The Address element 22222222 20022 cece eee 323 12 3 6 The BootEnvironment element 2 2 323 12 3 7 The SCSIBootConfiguration element 324 8 ServerView Virtual lO Manager Contents 12 3 8 The FCBootConfiguration element 327 12 3 9 The DCBConfiguration element
97. T_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 con nected are displayed as squares and contain the port number These are ports 37 38 39 The uplink set to which the port belongs is also listed This means for example that ports 41 and 42 belong to the uplink set NET_ 1 The blue lines from an uplink port to a network indicate which network is assigned to an uplink set In the example above network NET_1 is therefore assigned to the uplink set NET_1 with ports 41 and 42 The VLAN networks V_NET_1 V_NET_5 belong to the uplink set V_NET ServerView Virtual lO Manager 157 5 3 6 5 Virtual lO 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 BX920 S1 or lt empty gt if the slot is empty is displayed below the slots The lines from a slot to a network indicate the network to which a server blade is connected Tagged VLAN networks are marked as green lines with square endpoi
98. User Guide English FUJITSU ServerView Suite ServerView Virtual lIO Manager V3 1 User Guide Edition October 2012 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual Your feedback helps us optimize our documentation to suit your individual needs Feel free to send us your comments by e mail to manuals ts fujitsu com Certified documentation according to DIN EN ISO 9001 2008 To ensure a consistently high quality standard and user friendliness this documentation was created to meet the regulations of a quality man agement system which complies with the requirements of the standard DIN EN ISO 9001 2008 cognitas Gesellschaft fur Technik Dokumentation mbH www cognitas de Copyright and trademarks Copyright 1998 2012 Fujitsu Technology Solutions GmbH All rights reserved Delivery subject to availability right of technical modifications reserved All hardware and software names used are trademarks of their respective manufacturers Contents Contents 22 000 e cece ee eee e eee ceeeeeeeeeeanes 3 1 Introduction 2 2 2 22 c ccc anana eee 11 1 1 Target groups and objective of this manual 12 1 2 System requirements 02 20000 c cece cece ee ceeeeceeeeeeee 12 1 3 Supported Hardware 22 2 2 cece eee ccc ccceeeeecececccees 14 1 4 Changes since the previous edition
99. VIOM managed status in the IRMC user interface click the Disable VIOM button in the IRMC view System Overview To deactivate the servers VIOM managed status via the system BIOS open the Advanced menu ServerView Virtual lO Manager 271 7 Managing servers with VIOM Kj admin 11 1 12 11 22 Full Control RMC 52 53 Advanced Video Redirection d E 5 xj Extras Remote Storage Power Control Languages Preferences Help f 7 Mouse Sync Gtr AR vun Axor Context rocs cirar pei Local Montor always on ptio Setup Utility Copyright C 2011 American Megatrends Inc 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 admin 111 12 11 22 Full Control iRMC 52 53 Advanced Video Redirection 5 xj Extras Remote Storage Power Control Languages Preferences Help cin AB yn Axcr Cortera rocs VIOM f lag Enabled Regardless of whether you deactivate the VIOM managed status via the iRMC interface or via the BIOS interface the VIOM enabled flag is reset and the information that identifies the VIOM management station the VIOM vir tualization data and the inventory data are cleared But please note that the iRMC configuration of the VIOM management station as an SNMP trap des tination is not removed by this process You will need to manually check
100. VLAN IDs native VLAN ID VLAN networks e Service LAN Dedicated service network e Service VLAN Service VLAN networks The network types in bold indicate their corresponding names in the VIOM GUI Internal networks An internal network refers to a network connection within the IBP in which server blades are only linked to each other However no uplink ports are assigned to this network connection In this case it is an internal connection via the IBP module It makes sense to have an internal network if the server blades only need to communicate amongst each other and for security reasons there must be no connection to an extemal network In the figure 3 represents an internal network Single networks VIOM interprets a single network as an uplink set that is only used for access in one network 34 ServerView Virtual lO Manager 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 In the figure 1 and 2 illustrate single networks Virtual networks with VLAN IDs D
101. Y rack server a corresponding message appears in another dialog box asking whether you wish to continue with the operation If you confirm this the previous assignment is deleted and the profile is assigned to the new slot or PRIMERGY rack server If you try to assign a PRIMERGY rack server profile with PCI cards to a blade server slot or a blade server profile toa PRIMERGY rack server a warnig is shown If you confirm that you really want to assign the profile only the mezzanine PCI cards in slot 1 and 2 are regard ed see VIOM server profile mapping on page 132 Deleting profile assignments You use the Server Configuration tab to delete the assignment of a server profile from an individual slot or PRIMERGY rack server 1 Click Server List if applicable to switch to the server list view in the area on the left 2 Inthe tree structure on the left select the corresponding server from the VIOM Managed group Switch to the Server Configuration tab in the area on the right 4 Select the corresponding slot of the blade server or the PRIMERGY rack server in the table 298 ServerView Virtual lO Manager 9 7 Deleting profile assignments 5 You can only deactivate a server profile if the corresponding server is switched off power off You can see whether the server is switched off in the State column If the state of the server is not off you can switch it off by clicking Shut down or by selecting Shutdown in the contex
102. ability HA support Operating system Admin server if HA oe ae Windows Server 2008 R2 Foundation y Hyper V B l Hyper V only x64 Windows Server 2008 Enterprise x86 x64 v Hyper V only x64 Figure 10 Supported Hyper V high availability configurations v Windows Server 2008 Standard x86 x64 v v The Windows Server Core Installation option is not supported for admin server and guest OS on VM To set up the Windows 2008 Hyper V cluster and the virtual machine that will be controlled from it click here for the Microsoft instructions http technet microsoft com en us library cc732181 28v ws 10 29 aspx If there is a fault in the Hyper V cluster node the Microsoft cluster will per form a failover action of the Hyper V environment to the other cluster node and restart the virtual machine that is acting as the ServerView Suite man agement station ServerView Virtual lO Manager 49 2 Virtual lIO Manager Introduction CMS ie ts Windows 2008 R2 Cluster Figure 11 Failover action of the Hyper V environment to the other cluster node S 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 Connect with shared storage Configure BIOS Install Hyper V roles Install and configure EMC Solutions Enabler if used Add a failover clustering function
103. addresses assigned by the manufacturer will be used auto matically The same applies if the virtualization of the I O addresses for a slot is switched off e g if the corresponding server profile is moved If the central management server is switched off or the connection between the management station and the management blade is interrupted all the blade servers use the configuration last defined Once the connection to the external networks is configured and the server profiles assigned with virtualization parameters by the ServerView Virtual lO Manager the management station does not necessarily have to run with the Virtual lO Manager software To operate the virtualized blade server chas sis the software is not required PRIMERGY rack servers The virtualization I O parameters of a PRIMERGY rack server are stored ina specific table in the baseboard management controller IRMC of the server When a PRIMERGY rack server is powered on checks are running in the boot phase to determine whether virtualization parameters are defined in the iRMC table These parameters are transferred to the I O adapters so that vir tualized addresses are used in the same way as the physical addresses assigned by the manufacturer 46 ServerView Virtual lO Manager 2 6 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 th
104. ager VIOM database information and log files from the ServerView ServerList service 358 ServerView Virtual lO Manager 15 4 15 4 Event logging For how to collect diagnostic data on a Linux operating system see the chap ter Collecting diagnostic information on page 89 To activate the trace functionality of the ServerView Virtual lIO Manager user interface proceed as follows 1 2 On the Virtual lIO Manager tab click the Preferences button 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 file size if necessary The trace will be written to this file 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 Reproduce the error Save the trace file s for later diagnosis Click the Preferences button again see step 4 and deselect the option Write trace messages to file If you do not do this the trace will con tinue to be written even after the user interface is restarted Event logging The ServerView Virtual lO Manager writes event logs if an error occurs event type Error or if the configuration is modified event type Information Where the events are logged depends on the system on which the Server View Virtual lO Manager is installed
105. ager and install it again Therefore if it is possible that addresses may have to be added after the Virtual lIO Manager is set up we recommend that you install it without selecting the address range You should input a virtual address when creating the server profile 82 ServerView Virtual lO Manager 10 11 3 4 Installing the Virtual lO Manager on a Linux based CMS Click Next to launch the License Manager E VIOM License Manager Register new license Total assign limit Assigned profiles Assign credits Exit Click Register new license 8 Register new license Please enter license string Cancel Enter at least one valid license here so that you can use the Virtual lO Manager functions You can enter several licenses here For more infor mation on the License Manager see section License management on page 90 Then click OK D e The licenses are not version bound e Licenses purchased with Virtual lO Manager versions prior to V2 4 are also still valid These licenses v1 contain a chassis count which is multiplied by 18 to get the assign count used in licenses v2 purchased with Virtual lIO Man ager V2 4 or later 12 Click Exit in the VIOM License Manager dialog box to exit the License Manager The dialog box closes ServerView Virtual lO Manager 83 3 4 2 3 Installation and uninstallation 13 Inthe final screen you may view the release notes or the installation log 8 Fujitsu Serve
106. al port that connects the chassis with your LAN infrastructure If an uplink set is used by several virtual network connections VLANs the uplink set is referred to as a shared uplink set e Defining one or several networks that are assigned to the uplink set The definition of a network in the context of VIOM refers to i the allocation of a meaningful name for network access from outside the network 30 ServerView Virtual IO Manager 2 4 Defining networks LAN for blade servers only D If a blade server chassis is managed by VIOM manual con figurations not done by VIOM of an IBP connection blade are not supported Manual configuration of IBP connection blades might result in incorrect behavior of VIOM or get lost during configuration by VIOM Before managing a chassis by VIOM IBP connection blades should be set to factory default setting except IP address con figuration of the administrative interface user assigned name and access protocol SSH or telnet By default the IBP module IBP 10 6 is supplied with the following con figuration Server Blade 1 Server Blade 2 Server Blade 3 Server Blade 4 Server Blade 5 Server Blade 6 Server Blade 7 Server Blade 8 Server Blade 9 Server Blade 10 Blade chassis Figure 3 Standard configuration of the IBP module 10 6 All uplink ports of the IBP module IBP 10 6 are combined
107. alized from the rack servers you should unassign the profile S Copying server profiles You can create several similar server profiles by creating copies of an exist ing server profile 1 Todo this switch to the Server Profiles view in the area on the left of the ServerView Virtual lO Manager window Click Profiles if appli cable 2 Select the required profile 3 Select Copy Profile from the context menu of the selected server pro file A copy of the relevant server profile is created The copy of a server profile is saved in the server profile repository under the same name with the suffix _1 If you make several copies the suffix is incre mented The copy gets a new name and new virtual addresses are assigned All other properties e g boot parameter are equal in the original and the copy ServerView Virtual lO Manager 295 9 5 9 6 9 Defining and assigning server profiles D You can only copy server profiles if you specified address ranges for gt the virtual addressed when you installed VIOM Deleting server profiles You can delete server profiles you no longer need 1 Todo this switch to the Server Profiles view in the area on the left of the ServerView Virtual lO Manager window Click Profiles if appli cable 2 Select the required profiles in the area on the right 3 Click Delete or select Delete Profile in the context menu of the selected server profile 4 Amessage appears asking if yo
108. am must have been configured on the server blade and the network on the second IBP module must have been con figured accordingly By default Linkdown propagation is selected Enable LACP You activate the LACP protocol via Enable LACP Isolate mode You activate the isolate mode via Isolate mode With isolate mode acti vated server blades in the same chassis that use the same network can not communicate with each other but only with an external device though the uplinks This checkbox is not shown if the connection blade does not support iso late mode or if VLAN networks are created Link Speed By selecting a Link Speed you can select the transmission speed If auto negotiation is not selected on the extemal switch configure this value if a problem occurs using the drop down menu according to the set tings on the external switch The following values are available 166 ServerView Virtual lO Manager 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 If necessary the corresponding downlink ports may be added to the forwarding table of this
109. an be specified than are supported by the selected model a Wp If you have configured the number and type of ports and cards click Next to go to the l1O Channels step Select Use virtual addresses to use virtual MAC addresses and WWN addresses with this profile You can enter these addresses in Virtual Addresses step within this wizard or VIOM can assign these addresses automatically Select Disable Boot Menu Usage F12 to prevent your VIOM boot set tings from being overwritten on your local computer For CNA lO channels select the number of physical functions using the and B buttons and select the type of each physical function using the dropdown list SMUX setting is only enabled on blade server profiles if a second mez zanine card is defined as aLAN mezzanine card Here you can define the fabric to which the card is routed The upper table displays the onboard LAN ports up to 6 Another table is displayed for each configured mezzanine or PCI card 1 You can specify a network for each LAN or CNA port in a blade server profile under the Network column ServerView Virtual lO Manager 291 9 Defining and assigning server profiles If you want to use the profile on blade servers with IBP modules you can specify a network for each LAN port If you work with blade servers that have non VIOM capable LAN modules Open Fabric mode do not specify a network as it is not possible to define net works on these modules To
110. and Set Login Password beforehand for the corresponding I O connection blade in the management blade ServerView Virtual lO Manager 125 4 3 4 4 3 4 1 4 Configuration 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 e Normal Layer 2 switch mode e IBP mode For information on how to perform the switch refer to the Switch Blade user manual D Please note that before you activate blade server management sev eral uplink ports of aLAN connection blade in IBP mode form a stat ic link aggregation group LAG If you activate blade server management using VIOM all uplink ports of IBP modules will be deactivated and will only be reactivated when networks are defined in the IBP module Network Overview All components such as the management blades and I O connection blades the central management station and the management console must be inter connected via LAN It is recommended that you set up a management LAN that is separate from the productive LAN as illustrated in the following figure D If there are not enough physical ports available a VLAN based man AS Ft agement LAN can also be implemented 126 ServerView Virtual lO Manager 4 3 5 4 3 Configurations on the managed BX900 Blade Server Management Station a J par e re e eee Management LAN Switch
111. ange the instance name to the new value e g SqlServerInstance local SQLSERVERVIEW2 Uninstalling the Virtual lO Manager Before you uninstall VIOM you should unmanage all servers After unin stalling all information will be lost Therefore save your server profiles if you want to use them later Uninstalling the Virtual lO Manager on a Windows based CMS You uninstall the Virtual lO Manager via the Windows start menu e OnWindows Server 2003 Select Start Settings Control Panel Add Remove Programs e OnWindows Server 2008 Select Start Control Panel Programs and Features To display the product versions select Choose Details from the View menu Select the Version option and click OK Under Fujitsu ServerView Virtual lIO Manager select the entry Remove This uninstalls the complete package Uninstalling the Virtual lO Manager on a Linux based CMS In order to uninstall VIOM use the unstall_viom sh script which is found in the installation directory of VIOM cd opt fujitsu ServerViewSuite plugins viom Manager sh uninstall viom sh 96 ServerView Virtual lO Manager 4 1 Configuration In the following sections you find information on the required configurations on the managed server Configurations on the managed BX600 Blade Server In section Supported hardware configurations for the connection blades on page 97 you can find out what combinations of I O connection blades
112. are removed from uplink sets 8 5 Copying configuration You have the option of copying all defined uplink sets and networks of a chas sis to another chassis The following describes how to create a copy of all networks of a chassis on another chassis 1 Activate the Ext LAN Connections tab 2 Click Copy Configurations In the Select Target Chassis dialog box select the chassis to which the configuration should be copied and click OK After affirmation to overwrite the existing configuration copying starts The source and the target chassis both should have the same IBP types in the same slots Otherwise the copy will probably fail 288 ServerView Virtual lO Manager Defining and assigning server profiles To use address virtualization or to enable a server blade to use a defined net work you must 1 Define a server profile 2 Assign the profile to a slot ora PRIMERGY rack server A server profile contains a set of parameters which contains the VIOM spe cific input output parameters and the input output connections You can define a server profile in two different ways e Using the Server Profiles view e Using the Server Configuration tab The server profile is then stored in the server profile repository You activate a server profile by assigning it to a slot in the blade server or toa PRIMERGY rack server The following functions are available in the profile view e You define server profiles by clicking N
113. arget You can enter a name in this field if Address Origin static is selected 214 ServerView Virtual lO Manager 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 CHAP CHAP authentication is activated for this port CHAP allows the target to authenticate the initiator After activating CHAP you must enter a user name and password for the target Mutual CHAP Mutual CHAP authentication is activated for this port Mutual CHAP allows the initiator to authenticate the target After activating mutual CHAP authentication you must enter a user name a password for the target and a mutual CHAP password Chap Username CHAP user name The name must be identical to the name configured on the iSCSI target Chap Secret CHAP password This password must be identical to the password con figured on the iSCSI target It must contain 12 to 16 characters ServerView Virtual lO Manager 215 5 Virtual lO Manager user interface This password must differ from the password in the Mutual Chap Secret field Mutual
114. ated network ServerView Virtual lO Manager 41 2 Virtual lIO Manager Introduction Service VLAN networks untagged Server Blade 1 tagged 4094 tagged 10 tagged 20 untagged tagged 4094 Server Blade 2 Service VLAN tagged 4094 untagged Server Blade 3 tagged 20 tagged 30 untagged Server Blade 4 Blade chassis Figure 9 Service VLAN networks The Service VLAN networks are designed to separate LAN packages of mul tiple virtual NICs defined in the operating system running on the server blade and route them to specific uplink external ports To do this the different vir tual NICs in the operating system must be configured to send their packages with a VLAN tag that is identical to the Service VLAN ID of the Service VLAN network The behavior of a Service VLAN network is such that it receives tagged pack ets with the Service VLAN ID from the server blade and forwards them to uplink ports as tagged packets The LAN packages leave the IBP tagged at the uplink ports Incoming tagged packets with the Service VLAN ID at the uplink port are sent to the corresponding downlink internal ports blade servers as tagged packets 42 ServerView Virtual lO Manager 2 5 2 5 Server profiles Note that Service VLAN networks may overlap on the downlink ports with single networks VLAN networks dedicated service networks and other Serv ice VLAN networks The untagged packets re
115. ation on the selected server profile Export The selected server profiles are exported A file selection box opens in which you select the name of the file to which you want to save the exported profiles Import Server profiles are imported In the file selection box that opens select the file that you want to import 160 ServerView Virtual lO Manager 5 4 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 Show Profile Details The Serverprofile lt profile name gt dialog box is opened providing infor mation on the selected server profile If more than one server profile is selected this menu item is disabled Delete Profile The selected profiles will be deleted A message appears asking if you wish to delete the corresponding server profiles If you confirm this the server profiles will be deleted You can only delete server profiles that are not assigned If any selected server profile is assigned this menu item is disabled Wizards A wizard is an assistant that guides you step by step through a task A wizard usually consists of several steps that you work through in sequence T
116. ber of the database server dbuser ServerView Operations Manager username in the database by default svuser dbpasswd Password in the database by default the ServerView Operations Man ager database has no password mac range MAC address range Custom range must be set with the MAC start address and the MAC end address The values must be in hexadecimal format for example 4 1 22 33 44 55 66 Predefined MAC address ranges must be separated by a comma Pos sible values for predefined MAC address ranges are MAC1 Range 00 19 99 3E D2 A1 00 19 99 3E F1 E0 MAC2 Range 00 19 99 3E F1 E1 00 19 99 3F 11 20 MAC3 Range 00 19 99 3F 11 21 00 19 99 3F 30 60 ServerView Virtual lO Manager 85 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 86 WWN address range The values fora custom address range must be in hexadecimal format for example 11 22 33 44 55 66 77 88 Predefined WWN address ranges must be separated by a comma Pos sible values for
117. blade In this way server profiles allow the available blade hardware to be used flexibly In this context VIOM provides the option to define a slot as a spare slot If a problem occurs or maintenance work needs to be carried out you can trigger ServerView Virtual lO Manager 43 2 5 1 2 5 2 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 lIO Manager 1 Define a server profile 2 Assign the profile to a slot ora PRIMERGY rack server Defining server profiles A server profile is made up of a set of parameters that contain the related VIOM parameters These include e Virtual MAC addresses and WWN addresses e Boot parameters e For blade servers only LAN connections for the I O channels of a server blade The server profiles are stored centrally and independently of hardware under a user defined name in a server profile repository on the central management station Assigning server profiles The server profiles that are stored in the central server profile repository can be assigned to the slots of a blade server or to a PRIMERGY rack server using VIOM In order to do this the blade server or PRIMERGY rack server must be managed by VIOM In addition you must switch off the server blade in the corresponding slot or the PRIMERGY rack ser
118. blade server chassis is managed by VIOM If it is needed to change the stack con figuration the chassis is to be unmanaged in VIOM before changing the con figuration Configurations on the managed PRIMERGY rack server A PRIMERGY rack server must fulfill the following requirements in order to be manageable by VIOM ServerView Virtual lO Manager 129 4 Configuration e The PRIMERGY rack server must be in the list of supported server types e The system BIOS and the iRMC firmware must fulfill VIOM require ments Details concerning the required BIOS version and iRMC firm ware version might be found in the release notes e 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 iIRMC of the PRIMERGY rack server If any routers or firewalls are involved this protocol must be allowed between the VIOM central man agement station and the managed PRIMERGY rack server By default the iIRMC is configured to receive an IP address via DHCP If no DHCP server is running you must configure a static IP address net mask and default gateway manually for the IRMC of every PRIMERGY rack server that is to be managed by VIOM e The PRIMERGY rack server and especially the iIRMC must be added to the server list of ServerView Operations Manager ServerView Oper ations Manager must be configured in such a way that it
119. c 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 e Infabric 2 o LAN connection blades PY CB Eth Switch IBP 1 Gb 36 8 2 PY CB Eth Switch IBP 1 Gb 36 12 PY CB Eth Switch IBP 1 Gb 18 6 or PY CB Eth Switch IBP 10 Gb 18 8 in switch mode or IBP mode o LAN pass thru connection blades PY CB Eth Pass Thru 10 Gb 18 18 o FC switch blades of the type Brocade 5450 or o FC pass thru connection blades PY CB FC Pass Thru 8 Gb 18 18 e Infabric 3 same as fabric 2 The LAN connection blades in fabric 3 must run in the same mode However only one connection blade can be inserted in fabric 3 You must not switch the mode of a LAN connection blade if you are using the Virtual lO Manager to manage the BX400 chassis 16 ServerView Virtual lO Manager 1 3 Supported Hardware Managed BX900 blade servers Supported systems BX900 with MMB S1 For information on the required firmware version see the release notes supplied The following table shows which server blades are supported with which range of functions Server Scope of functions blade Server profiles with I O virtualization and network connection definition BX922 S2 Server profiles with I O virtualization and network connec
120. can be added to this port with the button Functions can be removed with the button 192 ServerView Virtual lO Manager 5 4 Wizards 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 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 In it you can select a managed blade server chassis from the selection list The networks defined for this chassis that are suitable for the selected port are then displayed To select a network double click the name or select the name and click the Add button Make sure that the networks entered here are will be configured before the profile is activated on the corresponding blade server Cs W As long as a network does not yet exist the server profile can be created with this network but cannot yet be assigned to a slot If you wish to exit the network selection without selecting a network click the Close button or another input field Names of tagged VLAN networks You can specify tagged VLAN networks for each LAN or CNA port but not for
121. can com municate with the IRMC This means that ServerView Operations Man ager must know a valid user account and password that allow RMCP communication with the iIRMC of that server ServerView Operations Manager must show the PRIMERGY rack server as manageable by VIOM A VIOM icon indicates whether this PRIMERGY rack server is man ageable by VIOM or not a This PRIMERGY rack server is managed by VIOM This PRIMERGY rack server is manageable by VIOM but man agement is inactive No This PRIMERGY rack server could not be managed by VIOM or icon its state could not be provided 130 ServerView Virtual lO Manager 4 4 Configurations on the managed PRIMERGY rack server For further information on the server list see the ServerView Operations Manager user guide e Forcorrect 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 If any routers or firewalls are involved these must be configured in such a way that SNMP traps can be delivered to the ServerView management If a PRIMERGY rack server is managed by VIOM as well as the user account used for contacting the IRMC you must specify the IP address or host name of the ServerView management station The supplied address is registered on the iRMC as a trap destination In addition on each iRMC t
122. can easily move an operating system image or an application from one server blade or PRIMERGY rack server to another The following basic I O parameters belong to the virtualization parameters e Virtual MAC address LAN e Virtual WWN addresses Fibre Channel You can also define the iSCSI boot parameters for LAN ports which are defined as iSCSI boot devices For each Fibre Channel HBA port the fol lowing SAN boot configuration parameters can be virtualized e Boot e 1st target port name WWPN of the target device e ist target LUN e 2nd target port name WWPN of the target device e 2nd target LUN ServerView Virtual lO Manager 45 2 Virtual lIO 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 These parameters are transferred to the I O adapters so that the virtualized addresses are used in the same way as the physical addresses assigned by the manufacturer This ensures that no changes need to be made if a server blade is exchanged or a server profile moved If a server blade or a mezzanine card is removed from a blade server and inserted in the slot of another blade server that is not managed by VIOM then the physical I O
123. ceived from the server blade or uplink port should obey the rule of the overlapping single network or VLAN network D The VLAN tags of the overlapping VLAN networks dedicated serv ice networks and Service VLAN networks must be different Different Service VLAN networks may share the same uplink ports If the port that is member of the Service VLAN network receives tagged packets with the Service VLAN ID SVID of a specific Service VLAN network these received tagged packets will be forwarded based on the definition of this Serv ice VLAN network The Service VLAN networks with disjoint uplink sets may have identical SVIDs Service VLAN networks may also share the same uplink ports with VLAN networks The VLAN tag of Service VLAN networks and VLAN networks sharing the same uplink ports must be different Server profiles A server profile contains the following VIOM specific parameters 1 Defining the connection in external networks see section Defining net work paths LAN on page 277 only for blade servers 2 Defining the physical identity in the form of I O addresses MAC WWN 3 Defining the boot devices with parameters To activate a server profile of this type it must be assigned to a server blade slot ora PRIMERGY rack server For a blade server it can be moved to another slot if required e g in the event of server blade failure The server blade in another slot thereby assumes the identity of the previous server
124. checkbox is not shown if the connection blade does not support iso late mode Link Speed By selecting a Link Speed you can select the transmission speed If auto negotiation is not selected on the extemal switch configure this ServerView Virtual lO Manager 181 5 Virtual lO Manager user interface value if a problem occurs using the drop down menu according to the set tings on the external switch The following values are available Auto negotiation The transmission speed is negotiated with the external switch You can achieve a transmission speed of 1 Gbit s with this value 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 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 If an uplink set for a switch stack is defined the uplink ports of all IBPs belonging to the stack are shown one below the other Use the scroll bar to reach the uplink ports of another stack member The context menu can contain the following menu items Add Only activated if the por
125. cified Initiator Name Name of the iSCSI initiator to be used in the case of an iSCSI boot for the connection to the iSCSI target ServerView Virtual lO Manager 213 5 Virtual lO 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 sub net mask in this field if Address Origin static is selected Gateway Address IP address of the network gateway You can enter the gateway address in this field if Address Origin static is selected This is necessary if the iSCSI target is in a subnetwork other than the subnetwork of the selected iSCSI boot port If iSCSI initiator and target are in the same network segment no gate way is needed The gateway address should be set to the value 0 0 0 0 Target Parameters Address Origin DHCP The system tries in the case of an iSCSI boot 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 static 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 Target Name IQN name of the iSCSI t
126. cing IBP modules 00 0e eee eee eee 353 15 2 VIOM address ranges 00020 c cece e cece e cece eee eee 354 15 3 Creating diagnostic data 000000 0000 c cece 356 15 4 Event logging 202 e eee eeeeeeeeeees 359 ServerView Virtual lO Manager 9 10 ServerView Virtual lO Manager 1 Introduction You use the ServerView Virtual IO Manager Virtual lIO Manager or VIOM for short software to manage the input output parameters I O parameters of fol lowing servers e PRIMERGY blade server BX600 BX400 BX900 D In Japan BX600 blade servers are not supported e PRIMERGY rack server RX200 S7 RX300 S7 RX350 S7 e PRIMERGY tower server TX300 S7 D When PRIMERGY rack servers are mentioned below both the PRIMERGY rack servers and the PRIMERGY tower servers are meant Additionally the LAN connection blade the Intelligent Blade Panel IBP in PRIMERGY blade servers can be managed via VIOM As an extension to the ServerView Operations Manager it is possible to man age a large number of PRIMERGY blade servers and PRIMERGY rack servers centrally by the central management station using VIOM This includes virtualizing and for blade servers saving the server blade specific I O parameters MAC addresses WWN addresses I O connections includ ing the boot parameters and configuring and managing a blade server s Intel ligent Blade Panel in a hardware independent server profi
127. cked ig before a chassis is added in the VIOM management If VIOM can recognize from this that a chassis is already managed by another Virtual lO Manager you receive a corresponding warn ing If however you are sure that a chassis is no longer man aged by another VIOM installation you can still add the chassis to the management despite the warning 2 All IBP modules in this chassis are set to an initial state that has the fol lowing properties e The downlink ports of an IBP module no longer have a connection This means that the server blades are not connected to each other or to an external network e Except for the first uplink port no uplink port in other words none of the other external ports has an external connection In the case of the LAN connection blades of the BX400 BX900 cur rently 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 which support an IBP mode no external port not even the first uplink port has an external connection The figures below show the standard configuration of the IBP mod ule before activating and the initial configuration after activating VIOM management Manage button 262 ServerView Virtual IO Manager 7 4 VIOM internal operations on blade servers Standard configuration before activating VIOM management 0 1 Server Blade 1 0 2 Server Blade 2 0 3 Server Blade 3 0 11 Ext 1 0 4 Server Blade 4
128. col ors in the display light red light green or dark red dark green The name of the uplink set is assigned to configured ports which you can rec ognize by this With PY CB Eth Switch IBP 1Gb 36 8 2 connection blades 1GB uplinks and 10 Gb uplinks must not be mixed If you try this the Next and Finish buttons will not be enabled P So D The Next and Finish buttons are disabled while not at least one a ros active port is included in the uplink set 5 4 1 4 Edit Properties step Create Network wizard dedicated service net work Edit Properties is the second step in the Create Network wizard The selection you made at the first step of the Create Network wizard deter mines which fields are displayed in the second step 168 ServerView Virtual IO Manager 5 4 Wizards Edit Properties step for dedicated service networks E Create Network for IBP BX900 1 S03 Name of uplink set SNET M Activate Port Backup Link Speed Auto negotiation M Linkdown propagation Service VLAN ID 1234 C Enable LACP V IGMP Snooping Isolate mode Ports For this uplink set change with right click Bx900 1 Connection Bay 3 BX900 1 S503 E is K 2 EJ 20 E zz Uplink set contains 1 ports 0 backup Finish Cancel Help Figure 35 Create Network wizard second step Name of uplink set Name of uplink set In the case of a single network the network auto matically has the same name
129. con __ Indicates a link to a related topic tinuous text ink con jIndicates a link to a location you have already visited tinuous text Indicates variables which must be replaced with real values Indicates options that can be specified syntax Indicates a key on your keyboard If you need to enter text in uppercase the Shift key is specified for example SHIFT A for A If you need to press two keys at the same time this is indicated by a plus sign between the two key symbols Screenshots Some of the screenshots are system dependent so some of the details shown may differ from your system There may also be system specific dif ferences in menu options and commands 24 ServerView Virtual lO Manager 2 1 2 2 Virtual lO Manager Introduction This chapter provides a general introduction to the concept of the Virtual lO Manager VIOM Virtual addresses Physical MAC addresses and WWN addresses are stored on the network card or in the host bus adapter HBA of a server blade or PRIMERGY rack server If a server blade or PRIMERGY rack server has to be exchanged or the operating system and or the application has to be started on another server usually the LAN or SAN network has to be reconfigured This means that whilst the MAC address and the WWN addresses identify a physical server blade several administrators have to be involved To separate the administration areas from each other it is necessary to keep th
130. corresponding row under Native VLAN in the table You can also change the VLAN ID of a network in the table ret rospectively To do this click in the corresponding row under VLAN Id in the table and edit the VLAN ID You can also define a network as a service VLAN in the table ret rospectively To do this select the checkbox in the corresponding row under Service VLAN in the table You can also delete VLAN networks from the list To do this select one of the VLAN networks in the table and click Delete When you have defined all the networks you need click Finish to con firm your entries The networks added to the table are created with the configured uplink set The new defined VLAN networks are added to the tables on the Graphic and Details tabs 284 ServerView Virtual lO Manager 8 2 8 2 Modifying an uplink set For further information on defining networks see section Defining networks LAN for blade servers only on page 30 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 The Create network wizard is launched 2 Inthe first step of the Create network wizard select Dedicated service network and confirm your entry by clicking Ne
131. cted server profile The Server profiles lt profile name gt dialog box opens to provide infor mation on the selected server profile For server profiles that are assigned you can also open the information win dow on the Server Configuration tab To do this select a slot or PRIM ERGY rack server that has a server profile assigned to it and then select Show Profile Details in the context menu Modifying server profiles You can modify server profiles retrospectively 1 294 To do this switch to the Server Profiles view in the area on the left of the ServerView Virtual lO Manager window Click Profiles if appli cable ServerView Virtual lO Manager 9 4 9 4 Copying server profiles 2 Select the required profile in the area on the right of the ServerView Vir tual lO 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 D You can only modify server profiles that are not assigned If this is am not the case the Edit button or Edit Profile menu item is inactive D Before inserting a server blade with new optional hardware you should unassign the profile and modify it Before detaching the PCI card virtu
132. d R Cancel Once the update installation is complete the final window of the installation wizard confirms that the update installation has been successful just like in the full installation Exit the installation wizard by clicking Finish Installing the Virtual IO Manager on a Linux based CMS The corresponding software is supplied with the PRIMERGY ServerView Suite DVD1 You can find the entire software for the PRIMERGY Server View Suite under ServerView Software Product Selection To find the Vir tual IO Manager software package like 3 1 0_2012 08 15 zip in this product selection choose ServerView Virtual lO Manager Please check the requirements for installing the Virtual lIO Manager to see whether the Linux distribution you use is supported by the Virtual lO Manager see section Prerequisites for the VIOM installation on page 57 ServerView Virtual lO Manager 73 3 4 1 3 Installation and uninstallation Installing the Virtual lO Manager using a graphical inter face If you want to use the graphical installation an X Windows server should be installed on your desktop computer Check the prerequisites for the VIOM installation see section Prerequisites for the VIOM installation on page 57 Installation process 1 74 Set the DISPLAY environment variable export DISPLAY lt IP address host name gt 0 0 Example export DISPLAY 111 22 33 115 0 0 If you prefer to have a dedicated directory for each VI
133. d 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 in a backup port D A network must be selected in the table in order to make the context E menu available for an uplink port Context menus in the Server Profiles view Depending on what you select in the Server Profiles view of the Server View Virtual lO Manager window context menus with different menu items are displayed The context menu of the Profiles group in the left area of the window con tains the following menu item 248 ServerView Virtual IO Manager 5 6 3 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 Context menu on the Server Configuration tab The context menu of the Server Configuration tab contains the following menu items Assign Profile Assign server profile to a slot or PRIMERGY rack server Unassign Profile Remove assignment of a server profile from a slot or PRIMERGY rack server Create profile Create a server profile Show Profile Details View definition of the assigned server profil
134. d uplink set Although both uplink sets have virtual networks with the VLAN ID 20 these are two different virtual networks Server blade 2 can not communicate with server blade 3 Packets that come from outside the network which have a VLAN tag that corresponds to the VLAN ID of a virtual network are transferred in precisely this VLAN network Before the packet exits the module on the server blade side the VLAN tag of a virtual network is removed in the same way as a port based VLAN Packets that come from outside the network which have a VLAN tag that does not match any VLAN ID of a virtual network are not transferred They are dropped 36 ServerView Virtual lO Manager 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 con nected In the process VLAN tags with the VLAN ID of the virtual network are added to these packets These packets exit the IBP module at the uplink ports of the related uplink set with this VLAN tag Packets that come from a server blade which have a VLAN tag are not transferred to a VLAN network They are either dropped or transferred else w
135. d 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 Virtual networks with VLAN ID used in tagged mode While normally the VLAN IDs of packets that leave the IBP on the server blade side are removed it is possible to use a VLAN network in tagged mode This means that all packets retain their VLAN tag when they are trans mitted to the server blade Packets that arrive on the server blade side of the IBP must have a VLAN tag with the corresponding VLAN ID if they are to transferred to this VLAN network in tagged mode Packets without a VLAN tag are dropped unless there is a VLAN network in untagged mode associated with the same downlink 38 ServerView Virtual IO Manager 2 4 Defining networks LAN for blade servers only untagged Server Blade 1 a VLAN10 native tagged 30 tagged 20 untagged tagged 20 tagged 30 Server Blade 2 untagged Server Blade 3 eg untagged Server Blade 4 Blade chassis Figure 7 Virtual networks with VLAN ID used in tagged mode Several VLAN networks in tagged mode can be used on the same IBP down link port They can also be combined with service networks The mode in which a VLAN network is used is controlled by network def initions in a
136. de If you only intend to work with virtual I O parameters Open Fabric mode of the Virtual IO Manager and not with dedicated network connections you can also use the connection blades in switch mode or you can use LAN connection blades that do not support IBP mode This applies sep arately to the connection blades in each fabric In other words you can operate one connection blade in IBP mode in fabric 1 and one connection blade in switch mode in fabric 2 e You must install an 8 GB Brocade switch blade in fabric 2 and or 3 in order to support a Fibre Channel mezzanine card 110 ServerView Virtual lO Manager 4 2 Configurations on the managed BX400 Blade Server 4 2 1 1 LAN hardware configuration Using IBP Modules The following LAN connection blades in IBP mode can be used in fabric 1 connection bay 1 and fabric 2 connection bay 2 for the first mezzanine card Bay 1 Bay2 PY CB Eth Switch IBP 1Gb 36 8 2 in IBP mode PY CB Eth Switch IBP 1Gb 36 12 in IBP mode PY CB Eth Switch IBP 1Gb 18 6 in IBP mode PY CB Eth Switch IBP 10 Gb 18 8 in IBP mode Fabric 3 has configuration restrictions in relation to the IBP modules The fol lowing table shows you which configurations are supported in fabric 3 Bay 4 PY CB Eth Switch IBP 1Gb PY CB Eth Switch IBP 1Gb 36 8 2 in 36 8 2 in IBP mode IBP mode optional PY CB Eth Switch IBP 1Gb PY CB Eth Switch IBP 1Gb 36 12 in IBP 36 12 in IBP mode mode optional PY CB Eth Switch
137. default 3260 for iSCSI BootLUN Only when DHCPUsage is No The LUN ID of the boot disk on the SCSI target AuthenticationMethod None No authentication is used 326 ServerView Virtual lO Manager 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 con figured on the iSCSI target ChapSecret Not when AuthenticationMethod is None The CHAP password This password must be identical to the pass word configured on the iSCSI target and it must contain 12 to 16 characters This password must differ from the password in the MutualChapSecret element MutualChapSecret Only when AuthenticationMethod is MutualCHAP The Mutual CHAP password This password must be identical to the password configured on the iSCSI target and it must contain 12 to 16 characters This password must differ from the password in the ChapSecret element 12 3 8 The FCBootConfiguration element The FC BootC onfiguration element contains the following elements FC Target Once or twice ServerView Virtual lO Manager 327 12 Importing and exporting server profiles The first or only FC Target configures the boot device while the second
138. der ServerView Virtual lO Manager The 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 true false MAC__ RANGE lt mac_range gt MAC_START lt mac_address_start gt MAC_END lt mac_address_end gt WWN_RANGE lt wwn_range gt WWN__ START lt wwn_address_start gt WWN_END lt wwn_address _ 68 ServerView Virtual lIO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS end gt DEBUG MODE true false VIOM LICENSE KEY lt key_ value gt Command line parameters for installation DO_ADDRESS_RANGE_SELECTION Possible values are true You want to set MAC_RANGE and WWN_RANGE default value false You do not want to set MAC_RANGE and WWN_RANGE MAC_RANGE Possible values are NONE No predefined MAC address range default value MAC1 Range 00 19 99 3E D2 A1 00 19 99 3E F1 E0 MAC2 Range 00 19 99 3E F1 E1 00 19 99 3F 11 20 MAC3 Range 00 19 99 3F 11 21 00 19 99 3F 30 60 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 ServerView Virtual lO Manager 69 3 Installation and uninstallation MAC8 Range 00 19 99 3F AD 61 00 19 99 3F CC A1 MAC12
139. dress Ss eee eek eee Subnet Mask z 255 255 254 0 Gateway a k e err IP Mode Setting Value DHCP Client Name Setting Value IP Addre Setting Value Subnet Mask Setting Value Gateway Setting Value Apply Network Setting LED Control Power Control Period Polling Set Login U Set Login P Set Enable P rd Enter selection or pe gt to quit You configure the network parameters of an I O connection blade as follows e Inthe Remote Manager choose 1 Management Agent 6 Con nection Blade e Select an I O connection blade e Make the relevant entries for the following parameters o IP Mode Setting Value o IP Address Setting Value o Subnet Mask Setting Value o Gateway Setting Value e Activate the settings by clicking Apply Network Setting ServerView Virtual lO Manager 103 4 Configuration D For Fibre Channel switch modules select FC Switch Blade you must also specify access data for the parameters Set Login User name and Set Login Password beforehand for the corresponding I O connection blade in the management blade 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 Here the management LAN is the network to which the central management station is connected and via which you can access the management blades and all I O connection blades The first uplink port is always the external uplink port of an IBP module on the
140. e Update State Update the power state display the boot mode and the virtualization stat us of a server ServerView Virtual lO Manager 249 5 Virtual lO Manager user interface Inventory Boot Re create the inventory table of the server During inventory boot the system BIOS assembles the inventory infor mation of the server blade or PRIMERGY rack server hardware as need ed by the Virtual lO Manager and sends it to the management blade or to iIRMC where it is stored In some cases a manual execution of the inventory boot is necessary in order to support the new functionality e For support of new functionality a new version of the inventory table might be needed Example Converged network adapter card CNA e In some cases the new version of the inventory table might not be created automatically for the server Example The new version of the inventory table is only supported by a new version of the system BIOS You must execute the inventory boot manually after applying a new g version of the system BIOS and iRMC firmware or a new version of the firmware of the optional hardware Boot Start the server s Shutdown Switch off the server Failover Assign the server profile of a slot to a suitable spare slot in the event of a failure Video Redirection Open a new window where the console output of the server is shown 250 ServerView Virtual IO Manager 5 7 5 7 1 5 7 2 5 7 3 5 7 General buttons Gene
141. e Channel hardware configuration 99 4 1 2 Configuring the BX600 management blade 99 4 1 3 Configuring the I O connection blades 2 2222 2 101 4 1 4 Connecting IBP modules 020022 222 eee 104 4 1 4 1 Network Overview 0 000 22 e cece eee 105 4 1 4 2 Notes and recommendations 106 4 2 Configurations on the managed BX400 Blade Server 109 4 2 1 Supported hardware configurations for the connection DIAS EER 2 set eh Uhh oa Aloe TOL ie eek eel T 110 4 2 1 1 LAN hardware configuration 002000020222222 02 111 4 2 1 2 Fibre Channel hardware configuration 112 4 2 2 Configuring the BX400 management blade 113 4 2 3 Configuring the I O connection blades 2 22222 114 4 2 4 Connecting IBP modules 00 22 eee eee 115 4 2 4 1 Network Overview 00 00 22 eee cece cece eee ee 116 4 2 5 Switch stacking support 00 0000000 0 eee 117 4 3 Configurations on the managed BX900 Blade Server 118 4 3 1 Supported hardware configurations for the connection bladess i hearths SE raters ee eines eet tes 8 119 4 3 1 1 LAN hardware configuration 222 22 119 4 3 1 2 Fibre Channel hardware configuration 121 4 3 2 Configuring the BX900 management blade 121 4
142. e I O parameters MAC and WWN outwardly constant Using virtual addresses instead of the MAC addresses or WWN addresses stored on the NIC network interface card or in the HBA the addressing remains constant even when a server blade is exchanged at the slot ora PRIMERGY rack server is replaced by another one Special connection blade for blade server Up to now blade servers have been used essentially to connect the LAN Local Area Network and Fibre Channel ports FC ports of individual server blades to the LAN and SAN networks SAN Storage Area Network using switch blades or pass thru blades which are inserted in the blade chassis It is the responsibility of the LAN or SAN administrators to manage these switches This leads to an overlap of the different administration areas ServerView Virtual lO Manager 25 2 Virtual lIO Manager Introduction Figure 1 Overlapping areas of responsibility As the areas of responsibility overlap this means that up to three admin istrators may be involved if a server blade s configuration changes e g because a server blade has to be replaced due to hardware problems and as a result the switches have to be reconfigured The onboard LAN and FC controllers in the server blade are connected to the installed LAN or FC switches via a midplane and are in turn connected to the LAN and SAN network via their uplink ports Providers use specific pro tocols or protocol extensions for switches fr
143. e Management Depending on which menu you select the individual menu items for this menu are displayed in the row below the menu bar For more information on the menus of the menu bar see the ServerView Operations Manager user manual Depending on what you select on the left in the work area the following is dis played in a tree structure e server list e server profiles You switch between the two views by clicking the Server List and Profiles buttons The area on the right displays the following depending on what is selected in the area on the left 138 ServerView Virtual lO Manager 5 2 5 2 Tree view Selection Display on the right on the left Server Five tabs are displayed in the area on the right see List Tabs on page 142 All Server Only the Virtual lO 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 Man aged server group Object s in Only the Virtual lO Manager and Setup tabs are acti the VIOM vated in the area on the right You can activate VIOM Manageable management of objects on the Setup tab server group Object s in The Virtual lO Manager Setup and Server Con the VIOM figuration tabs are activated in the area on the right Managed The Ext LAN Connections and Chassis Con server group figuration tabs are only enabled if a single blade server is selected An overvi
144. e 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 select ed the trace output is written to the Java Console only File name Enter here the file name for the trace output You can use the Browse button to select the file Max file size Specifies the maximal size of a trace file 240 ServerView Virtual lO Manager 5 5 Dialog boxes If the maximum file size is reached the trace file will be renamed and a new one will be used The renamed trace files will have a number append ed up to a maximum of ten possible back up trace files Therefore the trace files can use up to ten times the specified value of disk space 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 info Also some information about minor errors is traced fine Information necessary for error diagnosis is traced call trace More detailed information as fine finer Even more information than in call trace data Most detailed trace currently not used 5 5 6 Restore Options dialog box Servers The Restore Options dialog box opens when you select a blade server in the Se
145. e double the size using MAC Address Range 1 and 2 to MAC Address Range 7 and 8 Each of these areas contains 16 000 MAC addresses 354 ServerView Virtual lO Manager 15 2 VIOM address ranges These address ranges are defined as follows ace macs C 00 19 99 3F 8E 21 00 19 99 3F CC A0 For virtualization of the WWN addresses of Fibre Channel I O devices you can choose from eight predefined WWN address ranges which do not over lap WWN Address Range 1 to WWN Address Range 8 Each individual address range contains 32 767 487 WWN addresses ServerView Virtual lO Manager 355 15 3 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 F 3 06 09 FF WWN4 50 01 99 93 F3 06 0A 00 50 01 99 93 F4 FA 07 FF IWWN5 _ 50 01 99 93 F4 FA 08 00 50 01 99 93 F6 EE 05 FF IWWN6 50 01 99 93 F6 EE 06 00 50 01 99 93 F8 E2 03 FF 50 01 99 93 F8 E2 04 00 50 01 99 93 FA D6 02 FF 50 01 99 93 FA D6 03 00 50 01 99 93 FC C9 FF FF If you have an address range of your own that you wish to use for virtual MAC or virtual WWN addresses then select it in the Custom MAC Range or Custom WWN Range You can also assign individual virtual addresses when defining a VIOM server profile D Virtual addresses should always be taken from a reser
146. e 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 In this step you specify the number of mezzanine PCI cards as well as the number and type of I O channels for each card and for onboard Create Server Profile Name y z Onboard Card Type OLan Ocna 10 Channels 2 Mezzanine card slot 1 Card Type un Orc Oca 10 Channels 2 Mezzanine card slot 2 Previous Next Finish Cancel Help Figure 43 Configure Card step In the Onboard box you can specify the type and number of onboard ports to be supported with this server profile If you selected a server blade model under Preset values to use for server type in the Name step the number and type of ports is initialized according to the model You can adjust the number for the server profile However you cannot exceed the maximum pos sible value for the selected server model ServerView Virtual lO Manager 189 5 4 3 3 5 Virtual lO 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 F
147. e if you are using the Virtual lIO Manager to manage the BX900 chassis 18 ServerView Virtual lO Manager 1 3 Supported Hardware Managed PRIMERGY rack servers und PRIMERGY tower servers The following PRIMERGY rack and tower server models are supported PRIMERGY Scope of functions model RX200S7 Assign VIOM server profiles with I O address virtualization RX300 S7 and boot configuration for the onboard LAN ports and the sup ported PCI controller PANS Network connection definition is not supported For information on the BIOS and iRMC firmware version see the release notes supplied The following PCI controllers are supported for all the above PRIMERGY rack server systems e Emulex 10GbE OCe10102 CNA e Emulex 8Gb FC HBALPe 12002 e Emulex 8Gb FC HBA LPe 1250 1 channel e INTEL 2 port 10GbE D2755 Niantec e INTEL 4 port D2745 Barton Hills e INTEL 2 port D2735 Kawela 82576NS e INTEL Eth Ctrl 4x1Gb Cu PCle x4 D3045 e INTEL Eth Ctrl 2x1Gb Cu PCle x4 D3035 e INTEL 10GbE 10GBase T RJ45 PCle LAN ServerView Virtual lO Manager 19 1 Introduction PCI controller Scope of functions Emulex 10GbE OCe10102 Define physical functions and type LAN FCoE iSCSI of physical functions Assign virtual addresses to physical function and optionally define boot parameter This CNA supports two physical functions for each of both physical ports The first physical function must be of type LAN The phys
148. e if you specified address g ranges when you installed VIOM Next to each virtual address you see the status of the address The status can have the following values Sans sigim OOOO Allocate OK The address is automatically assigned Not changed The address is not changed OK OK OK The address is valid and has not been assigned yet Not checked The address entered has not been checked yet warning No value error Either an address was not specified or Allocate virtual address was not selected Not unique The same address is in use for several ports error ServerView Virtual lO Manager 221 5 Virtual lO Manager user interface saus siten OOO i Out of range The address is outside the specified address range error Syntax error The address is syntactically incorrect error Already used The address is already in use error Check Addresses A check is performed to determine whether the addresses are currently in use in other profiles and whether they are within the range specified This button is only active if for at least one address Allocate virtual address has not been selected and all virtual addresses have been entered correctly 5 4 4 7 Confirm step Edit Server Profile wizard Confirm is the next step in the Edit Server Profile wizard In this step you can check the entries you have made once again Edit Server Profile profile2 Overview of Server Profile Properties
149. e it to the required firmware version before you activate VIOM man agement for the blade server You can run an update via the Web inter face of the management blade Open the Information Operation section on the left side and select Firmware Update within Operation e You must configure the management blade and connect it to the local net work so that the management LAN port of the management blade can be accessed from the central management station on which the ServerView Operations Manager and VIOM is installed e Access to the management blade via Telnet or SSH is essential for VIOM You must configure the management blade via its Web interface To do this choose Settings System Unit Network Interface Management LAN On the Ethernet tab check the telnet and SSH set tings in the Text based Access section e Ensure that the Automatic Inventory Retrieval parameter is set to automatic so that the management blade automatically generates the inventory information required by VIOM when the server blade is insert ed G VIOM needs this inventory information specifically for the server blades that support the I O virtualization ServerView Virtual lO Manager 113 4 Configuration To check the parameter setting in the Web interface open the Com ponents section and select System System Unit The System Infor mation section on the right contains the option Automatic Inventory Retrieval If the value of it is not set
150. e modules Virtual lO Manager will undo the changes already made the next time the service starts This means that when the serv 54 ServerView Virtual lO Manager 2 7 High Availability HA support ice has restarted the configuration should be the same as it was just before the interrupted request D Some configuration actions of the Virtual IO Manager user E interface consist of several independent internal con figuration requests The Virtual lIO Manager can only undo the last internal configuration request If Virtual lO Manager successfully executes all necessary changes for a request but is just interrupted while sending the response to the Virtual IO Manager client the changes will not be undone e The transaction concept of the Virtual lO Manager should allow you to restart the service and execute the described undo actions if the data base is not corrupted by the SQL database service used What Virtual lO Manager does not do Virtual lO Manager does not control the availability of the ServerView Virtual IO Manager service It also does not check the availability of the virtual machine that is used as the ServerView Suite management station The letter should be done by the Microsoft Hyper V cluster if it is correctly con figured ServerView Virtual lO Manager 55 56 ServerView Virtual lO Manager 3 1 Installation and uninstallation You can install the Virtual lO Manager on a central management station
151. e or PRIMERGY rack server hardware as need ed by the Virtual lO Manager and sends it to the management blade or to iIRMC where it is stored In some cases a manual execution of the inventory boot is necessary in order to support the new functionality e For support of new functionality a new version of the inventory table might be needed Example Converged network adapter card CNA e In some cases the new version of the inventory table might not be created automatically for the server Example The new version of the inventory table is only supported by a new version of the system BIOS D You must execute the inventory boot manually after applying a new bz version of the system BIOS and iRMC firmware or a new version of the firmware of the optional hardware Boot Click Boot to start the selected server blade s and PRIMERGY rack servers Shutdown Click Shutdown to switch the selected server blades and PRIMERGY rack servers off You can only assign a server profile to a server blade or PRIMERGY rack server if it is switched off power off In the next dialog box you can select Graceful Shutdown or Forced Power Off Graceful Shutdown Shuts down the server properly and then switches it off 154 ServerView Virtual IO Manager 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 a
152. e outputDirLinux entity defines the directory for full backup files example var fujitsu ServerViewS uite viom postgres backups on Linux D 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 Server View Virtual IO DB Backup Service 1 Select Start Settings Control Panel Administrative Tools Services 2 Select the ServerView Virtual IO DB Backup Service and then select Start from the context menu To have the Backup Service start automatically from now on you will need to configure it as follows 1 Select Start Settings Control Panel Administrative Tools Services 2 Select the ServerView Virtual IO DB Backup Service and then select Properties from the context menu On the General tab set the start type to Automatic 4 Click OK 14 1 5 Starting the VIOM Backup Service on Linux When you have configured the Backup Service you must start the Backup Service 1 service viom_ backup start 2 chkconfig viom backup on The second command is necessary for the Backup Service to restart after a reboot of the management station 344 ServerView Virtual lO Manager 14 2 Restoring the VIOM database on Windows 14 1 6 Logging the Backup Service 14 2 14 2 1 The Backup Service lo
153. e 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 Vir tual IO Manager before the server is powered on again This restoration proc ess is done automatically But this requires that the management station has to be kept running as long as PRIMERGY rack servers are managed For fur ther information see VIOM internal operations on a PRIMERGY rack server on page 266 Server profile failover for blade servers only If a problem occurs or maintenance work needs to be carried out VIOM pro vides the option to move the server profiles from the affected server blade to a suitable server blade within the same blade server In order to do this you must define spare slots that assume the tasks of the other server blade in such acase It is advisable to install server blades at the spare slots so that they are available if a problem occurs or maintenance work needs to be carried out A failover of this type can only take place if the server blade on which the failover is to take place is switched off If a server blade fails for example you launch the failover function via the context menu of the corresponding server blade VIOM then searches for a spare slot that has a server blade to which the server profile can be assigned Once such a sl
154. e previous step use the arrow up and arrow down buttons to change the boot order The selection you made at the second step iSCSI boot or SAN boot deter mines which fields are displayed in this dialog box 212 ServerView Virtual lO Manager 5 4 Wizards Boot Parameters for an iSCSI boot LAN ports or iSCSI function on CNA mezzanine card Edit Server Profile profile2 Name v Please fill in the boot parameters Onboard 1 Initiator Parameters Address Origin Initiator Name IPv4 Address Gateway Address Target Parameters Address Origin Target Name IPv4 Address Authentication Authentication Method Chap Username Chap Secret Mutual Chap Secret DHCP static ign Initiator BX900Blade 1 111 11 111 162 Wi 1 DHCP static ign NetApp com 111 11 111 163 Port 3260 opt O None abcdefghijklmnopqrstu cHaP Mutual CHAP VLAN Id Subnet Mask 255 255 255 0 12 16 characters 12 16 characters Previous next Finish cancel Help 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 spe
155. e select fewer servers in the table before you click the Manage or Authentication button Authentication Enter authentication data For these modules All Selected Servers User name Password Figure 67 VIOM Manager authentication PRIMERGY rack server and blade server 236 ServerView Virtual IO Manager 5 5 4 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 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 Vir tual lIO Manager tab Licenses Information License Version Bound Assign Count Duration Days 4T3P MHQG A4GY 5NBP FNC3 OX5Y JUAY all 18 14 Assign Limit 18 Used Assigns O Assign Credit 18 Figure 68 Licenses Information In the table there is one row per license Column _ Significance License License code Version VIOM version if the license is version bound currently not yet Bound supported i Number of server profiles that this license permits you to assign Count using the Virtual lIO Manager Duration Validity period only applies to demo licenses Days ServerView Virtual lO Manager 237 5 5 5 5 Virtual lO Manager user interface Assign Limit Maximum number of server profiles that can be assigned with the licenses Used A
156. e software product data sheet of Fujitsu Technology Solutions he Software consists of machine readable instruc tions and or printed documentation and related li censed materials 1 2 Please read this agreement carefully before you use the Software If you do not accept the license agreement do not accept the license agreement Accept the license agreement by selecting the corresponding option 76 ServerView Virtual lO Manager 3 4 Installing the Virtual lO Manager on a Linux based CMS 5 Click Next 8 Fujitsu ServerView Virtual lIO Manager Setup User Information Enter the following information to porsonalize your installation FUJI I SU Full Name user Organization Fujitsu Technology Solutions lt Back Next gt Enter your name and the name of your company organization ServerView Virtual lO Manager 77 3 Installation and uninstallation 6 Click Next is Fujitsu ServerView Virtual IO Manager Setup Database Server Connection Please select the host and user account for the Database Service Database Host 127 0 0 1 Database Port 9212 Database User Name svuser Enter the data on the ServerView database The database user svuser has been created during ServerView installation and is used by VIOM as well 78 ServerView Virtual lO Manager 3 4 Installing the Virtual lO Mana
157. e view Virtual IO Manager provides the following tabs e Virtual lO Manager tab e Setup tab e Ext LAN Connections tab with o Graphic tab o Details tab e Server Configuration tab e Chassis Configuration tab Initially the Virtual O Manager tab is activated 5 3 1 Virtual lO Manager tab The Virtual lO Manager tab contains general information on VIOM It is the only tab that is always enabled if Server List is selected in the tree view 142 ServerView Virtual lO Manager 5 3 Tabs https tx200s3 sw5 servware abg fsc net 3170 Lang en Virtual I0 Manager tx200s3 sw5 Windows Internet Explorer DER S ServerView User administrator Logout MEE raministration Ass ServerBrowser Home gt gt Virtual IO Manager eol VIOM Manageable Virtual TO Manager setup Ext LAN Connections Server Configuration Chassis Configuration w Bx400 VIOML 9 Bx600 3 ServerView Virtual IO Manager P Bx900 1 Bx900 5 P Bx900_4 P Rx20057 v1oM4 VIOM server https tx200s3 sw5 servware abg fsc net px30057 VIOMs GUI version 3 1 0 buld 2012 08 08 07 11 55 1x30057 V10M3 API version 3 1 0 buld 2012 08 06 13 07 06 5 VION Managed VIOM manager 3 1 0 buld 2012 08 06 13 07 11 javam 6 0_99 609 gi Bx900 2 Configuration Backup Restore Currently one server is managed by VIOM To manage a server by VIOM select it in the left tree and choose manage To configure a managed server select it in the
158. eated inven tory boot the VIOM virtualization data is rewritten by VIOM to the IRMC also evaluating the new inventory data and the virtualization data is made active via an init boot As long as the virtualization data is not available to the server this server will not be able to boot A This illustrates that when managing PRIMERGY rack servers with VIOM it is very important that the VIOM management sta tion is always running It is advisable to make regular backups of the ServerView Oper ations Manager database and the VIOM database including trans action logs These database backups and transaction logs should be stored on high availability storage media Regular backups of the OS image of the ServerView management station should also be created so that the VIOM management station can always be rec reated in the event of a server crash If the server needs to boot after AC failure even though the VIOM man agement station is not currently available the VIOM managed status of this server must be deactivated see also below But if this is done the I O address virtualization of the server gets lost The Virtual lO Manager later detects that this server is no longer VIOM managed by the VIOM enabled flag in the IRMC Because of this the VIOM managed status in the Virtual lO Manager is changed to unmanaged in this case and if a profile was assigned to this server it is internally unassigned If aVIOM managed PRIMERGY rack server i
159. ect the Restore only reassigned profiles only the profiles that are reassigned to the selected servers will be restored see section Restoring blade server configurations on page 306 If you do not select the Restore only reassigned profiles option all the profiles saved in the backup file will be restored ServerView Virtual lO Manager 305 11 Saving and restoring 3 Select the Keep existing profiles option to keep the existing profiles This option is selected automatically if you select the Restore only reas signed profiles option If you do not select this option all existing pro files are deleted before the configuration is restored 4 Ifyou select the Keep existing profiles option select what is to happen with the existing profiles of the same name in On Existing Profiles e The restore operation is canceled and an error message displayed Abort Restore e The existing profiles are renamed by adding the backup date and possibly also a number to the file names Rename Restored Pro files e The existing profiles are replaced by the profiles contained in the backup Replace Existing Profiles e The profiles are not restored and the existing profiles continue to be used instead Use Existing Profiles 5 If you want to assign new virtual addresses select Assign new virtual addresses The restored profiles are assigned new virtual addresses 6 If you want to restore address ranges select Restore Address Ranges
160. ect the second mezzanine card To define dedicated network connections for server blades with net works you require LAN connection blades in IBP mode The 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 con nection blades support a normal Layer 2 switch mode and IBP mode If you only intend to work with virtual I O parameters Open Fabric mode of the Virtual IO Manager and not with dedicated network connections you can also use the connection blades in switch mode or you can use LAN connection blades that do not support IBP mode This applies sep arately to the connection blades in each fabric In other words you can operate connection blades in IBP mode in fabric 1 and connection blades in switch mode in fabric 2 e You must install an 8 GB Brocade switch blade in fabric 2 and or 3 in order to support a Fibre Channel mezzanine card 4 3 1 1 LAN hardware configuration Using IBP modules All fabrics have identical configuration restrictions in relation to the IBP mod ules The following table shows you which configurations are supported in ServerView Virtual lO Manager 119 4 Configuration fabric 1 fabric 2 fabric 3 and fabric 4 Bay 1 Bay 3 Bay 5 Bay 7 Bay 2 Bay 4 Bay 6 Bay 8 PY CB Eth Switch IBP 1Gb PY CB Eth Switch IBP 1Gb 36 8 2 in 36 8 2 in IBP mode IBP mode optional PY CB Eth Switch IBP 1Gb PY CB Eth Switch IBP 1Gb 3
161. ection blade is accepting IBP commands please perform the action Explore in ServerView Oper ations Manager menu item of the context menu in the ServerList win dow for the related blade server chassis and wait until this action is complete 6 Now start the user interface of Virtual lIO Manager and select the cor responding blade server chassis in the server tree sub tree VIOM Man aged On the Setup tab select the new connection blade VIOM should report the error status Hardware does not match database for this mod ule and should show the action Restore IBP Please perform this action for the new connection blade 7 Once Restore IBP is successfully completed plug in the LAN cables Please make sure you connect them as they were connected to the old connection blade For uplink sets with active ports and backup ports you should first connect the active ports and then the backup ports When you have completed these actions the new IBP module should work correctly VIOM address ranges During installation of ServerView Virtual lIO Manager you can select address ranges used for automatic assignment of virtual MAC and WWN addresses For virtualization of the MAC addresses of LAN I O devices you can choose from eight predefined MAC address ranges which do not overlap MAC Address Range 1 to MAC Address Range 8 Each of these address ranges contains 8 000 MAC addresses If such a range is insufficient you can also select a rang
162. ection to Remote Con nector Service o Port 162 must be opened to receive SNMP traps from iRMC when managing PRIMERGY rack servers You can also obtain the current requirements from the release notes You find the release notes e g on a Windows based management station under Start All Programs Fujitsu ServerView Suite Virtual lO Manager Release Notes License You must purchase licenses to use the Virtual lIO Manager At least one license is required Each license contains a count which determines the allowed number of server profile assigns If more than one license is reg istered the counts are added together ServerView Virtual lO Manager 13 1 3 1 Introduction Supported Hardware Managed BX600 blade servers Supported systems BX600 S3 with MMB S3 For information on the required firmware version see the release notes included The following table shows which server blades are supported with which range of functions Server blade Scope of functions BX620 S2 BX620 S3 Server profiles without I O virtualization but with net work connection definition BX620 S4 BX620 S5 Server profiles with I O virtualization and network BX620 S6 connection definition BX630 Server profiles without I O virtualization but with net work connection definition BX630 S2 Server profiles with I O virtualization and network connection definition Table 1 Supported server blades For information on the BIOS and iR
163. ed here static A static client IP address subnet mask and gateway IP address must be specified Initiator Name Name of the iSCSI initiator to be used in the case of an iSCSI boot for the connection to the iSCSI target ServerView Virtual lO Manager 195 5 Virtual lO Manager user interface VLAN Id VLAN ID that is used by the HBA to send its requests optional Should be used only for CNA iSCSl 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 You can enter the sub net mask in this field if Address Origin static is selected Gateway Address IP address of the network gateway You can enter the gateway address in this field if Address Origin static is selected This is necessary if the iSCSI target is in a subnetwork other than the subnetwork of the selected iSCSI boot port If iSCSI initiator and target are in the same network segment no gate way is needed The gateway address should be set to the value 0 0 0 0 Target Parameters Address Origin DHCP The system tries in the case of an iSCSI boot 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
164. ed with the element you have selected are then highlighted 156 ServerView Virtual lO Manager 5 3 Tabs Virtual I0 Manager tx200s3 sw5 Windows Internet Explorer He S ServerView administrator Logout Fuffrsu SererBrowser Server Configuration Virtual10 Manager Users Passwords National Settings Base Configuration Wizard Home gt gt Virtual IO Manager BO Al Server VIOM Manageable Virtual 10 Manager Sae Chassis Configuration Bx600 3 This is a schematic view of the chassis Bx600 5 You get more information on a link by moving the mouse over it Bxeo0s3 2 ee Bx900 1 Network Types 1 Internal Network 5 Single Network Y x VLAN Network oO Bx900 6 D5 x Dedicated Service Network S x Service VLAN Network x VLAN ID w Bx900_4 E E VIOM Managed t a 11 22 1111 sl g oo Ko ad Connection Bay 1 NET_A 5 NET_2 5 NET 3 5 NET 4 5 CT fT profile Pwr ON Slot 1 Slot 2 Slot 3 Slot 4 Slot 6 Slot 14 Slot 7 Slot 8 Bxe20Si BX920S1 empty empty Bx960 St 5X960 Update States E Lokales intranet 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 NE
165. ee Authentication dialog box single blade server on page 231 Authen tication dialog box PRIMERGY rack server on page 234 and Authen tication dialog box PRIMERGY rack server and blade server on page 236 In this dialog box you enter the user names passwords for the man agement blade for the IBP modules or for the PRIMERGY rack servers which VIOM can use to access these components By default the user name admin and password admin are set up for all components In this case you must only enter the user name and 258 ServerView Virtual lO Manager 7 2 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 accord ingly in this dialog box 4 Click the Configure protocols button if you do not use the default pro tocols or ports The Authentication dialog box expands so that you can also configure the protocol and ports used by VIOM to access the com ponents 1 Select the protocol to be used for communication with the man agement blade the I O connection blades or PRIMERGY rack servers Protocol 2 Specifying the port numbers for the compo
166. eld is 0 Speed Transmission speed used by the selected port By default auto nego tiate is selected If auto negotiation is not selected on the external switch you configure the value using the drop down menu according to the settings on the external switch The following values are available auto negotiate Default The transmission speed is negotiated with the external switch 1Gbit s 1 Gbit s full duplex 2 Gbit s 2 Gbit s full duplex 4 Gbit s 4 Gbit s full duplex ServerView Virtual lO Manager 199 5 Virtual lO 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 D This step is only shown if CNA onboard ports are selected or at nS ipi z least one CNA mezzanine card is specified in the second step of the Create Server Profile wizard 200 ServerView Virtual IO Manager 5 4 Wizards 4 Create Server Profile CNA parameter settings Mezz 1 Port 1 Function 1 LAN Bandwidth 504 VLAN ID Mezz 1 Port 1 Function 2 FCoE Bandwidth 50 gt 7 Enable DCB settings Priority Level Mezz 1
167. els 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 Disable Boot Menu Usage F12 Prevents the VIOM boot settings from being overwritten on your local computer SMUX setting This is only visible if a second mezzanine card of a blade server profile is defined as a LAN mezzanine card Defines the fabric to which the second mezzanine card is routed ServerView Virtual lO Manager 191 5 Virtual lO Manager user interface Fabric 3 All paths are routed to fabric 3 Fabric 4 All paths are routed to fabric 4 Fabric 3 amp 4 LAN1 is routed to fabric 3 and LAN2 to fabric 4 For more information on SMUX settings see the documentation PRIM ERGY BX900 Blade Server Systems ServerView Management Blade 1 The upper table displays the onboard ports up to 6 Another table is dis played for each available mezzanine PClI card configured in the previous step The tables have the following columns first col Port number of the onboard or the mezzanine PCI card port On umn CNA cards the type of the function LAN FCoE iSCSI can be selected from the drop down list Another function
168. enter a network name click the table cell to switch to edit mode You can also open a network selection dialog box via the but ton In this dialog box you can select a managed blade server chas sis from the selection list The networks defined for this chassis are then displayed To select a network double click the name or select the name and click the Add button D Make sure that the networks entered here are will be con i figured before the profile is activated on the corresponding blade server As long as a network does not yet exist the server profile can be created with this network but cannot yet be assigned to a slot If you wish to exit the network selection without selecting a network click another input field 2 You can specify tagged VLAN networks for each LAN or CNA port in a blade server profile If you specify more than one tagged VLAN 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 added to the Tagged VLAN column if you use the Add tagged but ton 3 You can specify service networks for each LAN or CNA port in a blade server profile If you specify more than one service network for a port the names must be separated by commas If you use the net work 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 14 To configure the
169. epending on the IBP module you have 6 to 12 uplink ports available You can define as many different networks as there are uplink ports If networks are to be created with backup ports or with a link aggregation group then the number of possible networks on an IBP module is automatically reduced You can get around this restriction regarding the uplinks that are physically available by defining virtual networks Virtual Local Area Network VLAN By setting up virtual networks which can be identified by unique numbers known as VLAN IDs you can set up several logical networks that are com pletely separate from each other from a technical and network perspective These networks share an uplink set shared uplink set without the server blades of one virtual network being able to communicate with server blades of the other virtual networks ServerView Virtual lO Manager 35 2 Virtual lIO Manager Introduction untagged Server Blade 1 tagged 10 tagged 20 untagged Server Blade 2 untagged Server Blade 3 tagged 20 tagged 30 untagged Server Blade 4 Blade chassis 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 share
170. erface Edit Uplink Set Edit Properties Add Networks Enable DCB Purpose FCoE W Priority Level 3 Bandwidth sols Hints DCB Data Center Bridging is mandatory to use FCoE Previous Finish Cancel 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 Possible values are 0 to 7 for FCoE this is by default the value 3 for iSCSI the default value is 4 Bandwidth The share of the bandwidth in percent that is assigned to this function If the sum of all bandwidths of one O channel is not 100 the values are 184 ServerView Virtual lO Manager 5 4 Wizards internally adjusted accordingly D This is the bandwidth reserved for the FCoE function The FCoE function might share the complete bandwidth of 10 Gb with other functions A value of 60 for exam ple means that a bandwidth of at least 6 Gb sec is reserved for the FCoE packages 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 Define networks which use this uplink set Add another n
171. erverView Virtual lO Manager 345 14 VIOM database Stop the services ServerView Virtual IO Manager Services and Server View Virtual IO DB Backup Services 1 Select Start Settings Control Panel Administrative Tools Services 2 Select the appropriate service and then select Stop from the context menu Restrict the access to the VIOM database 1 Start SQL Server Management Studio 2 Connect with the SQL Server instance and select Databases ViomDB Select Properties from the context menu 4 Select the Options page and under Restrict Access select the entry RESTRICTED_USER Click OK followed by YES Restore from the database backup 1 Click Databases and then select Restore Databases from the con text menu The Restore Databases window opens 346 ServerView Virtual lO Manager 14 2 Restoring the VIOM database on Windows Restore Database ViomDB jor x Select apa LS Script Help 1 General a a Options Destination for restore Select or type the name of a new or existing database for your restore operation To database ViomDB X To a point in time Most recent possible im Source for restore Specify the source and location of backup sets to restore From database F From device C Program Files x86 Fujitsu ServerView Suite VIOM Manager backups ViomDbD ata bal fel Select the backup sets to restore Restore Name Component Type Server Database
172. es of a virtual NIC defined in the operating system running on the server blade to specific uplink ports In order to do this the virtual NIC in the operating system must be configured to send all packets with a VLAN tag 40 ServerView Virtual lO Manager 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 Incoming tagged packets at uplink ports are dropped Note that dedicated service networks may overlap on the downlink ports with single networks VLAN networks other dedicated service networks and Service VLAN networks explained below The untagged packets received from the server blade or uplink port should obey the rule of the single network or VLAN network that overlaps with the dedicated service network D The VLAN tags of the overlapping VLAN networks dedicated serv i ice networks and Service VLAN networks must be different Dedicated service networks cannot overlap with any other network at the uplink ports This means the uplink ports of a dedicated service network can only be assigned to this dedic
173. es or Firmware version for switches e Manage State ServerView Virtual lO Manager 145 5 Virtual lO Manager user interface e Fault State e 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 data base doesn t match Configuration of switch server does not match hardware with database not supported Switch server model is not supported model does not match The model is supported but some other require slot configuration ments are not met no configuration No configuration of switch server is stored inside the database no ServerView entry No entry of blade server inside of ServerView Operations Manager different switches in fab The switch is incompatible with another switch ric in the same fabric inapplicable profile The assigned server profile is incompatible with i the plugged blade server stacking error The switch configuration is not compatible with the stacking groups profile assigned Switch server is used by an assigned server pro file slot is empty No hardware plugged although a configuration exists Depending on what you select the following buttons are available that allow you to carry out various actions Manage Activates the management of the selected servers The Authentication dialog box opens In this dialog box you enter the user names and 146 ServerView Virtual IO Manager 5 3 Tabs passwords
174. etwork Network Name Y _NET_6 VLAN ID eo Native VLAN C Service VLAN Isolate mode Network VLAN ID Native VLAN Service VLAN Isolate mode 10 20 30 40 50 Previous Finish Cancel Figure 41 Edit Uplink Set wizard second step Inthis step you assign meaningful names for the networks defined via VLAN IDs which are to be assigned to the uplink set defined in the previous step ServerView Virtual lO Manager 185 5 Virtual lO 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 With isolate mode acti vated server blades in the same chassis that use the same network can not communicate with each other but only with an external device though the uplinks This checkbox is not shown if the connection blade does not support iso late mode Add button Adds the virtual LAN network to the table below Table You can also define a network as a native VLAN or service VLAN and set the isolate mode in the table retrospectively Native VLAN Select the
175. ew see section Defining server profiles on page 290 e You modify server profiles by clicking Edit see section Modifying server profiles on page 294 e You delete server profiles by clicking Delete see section Deleting server profiles on page 296 You can also access these functions using various context menus These will be pointed out to you at the relevant places You can also copy a server profile using the context menu of a profile see section Copying server pro files on page 295 You assign a server profile to a slot or toa PRIMERGY rack server on the Server Configuration tab using the Assign profile button or Assign Pro file in the context menu of the required slot or PRIMERGY rack server see section Assigning server profiles on page 296 ServerView Virtual lO Manager 289 9 1 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 lO 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 Defining server profiles To define a server profile the Create Server Profile wizard is used This wiz ard can be opened from two views Profiles view 1 Switch to the Profiles view in the area on the left of the ServerView Vir tual lO Manager window Click Profiles if applicable If no profiles have been created yet the Profiles
176. ew Virtual lO Manager 323 12 Importing and exporting server profiles e FCBootConfiguration BootPriority Specifies the boot order Possible values are 1 to 4 However each value can only appear once within a profile PXEBootC onfiguration 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 FCBootC onfiguration Specifies that the port is a SAN boot device You can only specify this element for FC ports The elements contained in this element are described below 12 3 7 The ISCSIBootConfiguration element The ISCSIBootConfiguration element contains the following elements ISCSlInitiator Specifies the values of the iSCSI initiator This element contains the fol lowing elements DHCPUsage Yes In the case of an iSCSI boot the system tries to obtain the client IP address subnet mask and gateway IP address from a DHCP server Only the initiator name must be specified here 324 ServerView Virtual lO Manager 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
177. ew of the previously defined profiles group Only the corresponding profile D It is not possible to select unmanaged and managed servers in the ig server list at the same time Tree view The tree view is on the left of the work area in the Virtual IO Manager and pro vides various views ServerView Virtual lO Manager 139 5 2 1 5 Virtual lO Manager user interface e Server list default e Profiles You switch between the two views by clicking the Server List and Profiles buttons The Server List button is always above the tree structure The Pro files button is e Below the tree structure if the server list is displayed in this area e 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 The icons in front of the objects in the tree structure match the icons in the ServerView server list You can find a table describing the icons and their meaning in the ServerView Operations Manager user manual Tree structure Server List Servertist i H All Server 5 IOM Manageable I Bx600 3 T Bx600 5 T Bx60053 2 T Bx900 1 T Bx900 6 E E I Bx900_4 5 IOM Managed P 111 22 11 111 P 111 22 12 11 Bx900 2 E E H E Figure 23 Server List tree structure 140 ServerView Virtual IO Manager 5 2 Tree view When you select Server List standard on the left of the work a
178. ezzanine card 1 I O port 4 Mezzanine card 2 I O port 1 Mezzanine card 2 I O port 2 Mezzanine card 2 I O port 3 Figure 18 Mapping of lO channels 132 ServerView Virtual lO Manager 4 6 PCI slot location in PRIMERGY rack servers D e Profiles with onboard CNA configuration cannot be assigned to servers which do not have an onboard CNA controller e 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 4 6 PCI slot location in PRIMERGY rack servers The PCI slots of the supported PRIMERGY rack servers are located as fol lows RX200 S7 Figure 19 RX200 S7 connection panel on the rear 1 PCI slot 3 12 PCI slot 2 13 PCI slot 1 Management LAN connector IRMC Standard LAN connector LAN 2 6 Shared LAN connector LAN 1 ServerView Virtual lO Manager 133 4 Configuration RX300 S7 Cerra 7 6 YY n ARERR itt Figure 20 RX300 S7 connection panel on the rear 6 Standard LAN connector LAN 2 Management LAN connector IRMC 18 PCI slot 5 9 PCI slot 6 134 ServerView Virtual lO 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 z poise ew AeA Adding a server to the ServerView server list In order to manage a server with VIOM
179. f an uplink set The Create network wizard is launched 282 ServerView Virtual lO Manager 8 1 Defining an uplink set 3 Inthe 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 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 An uplink set must contain at least one active port All active uplink ports and all backup ports each form a LAG If anetwork needs to be configured so that the IBP module switches to another port if any problems arise then besides configuring the active ports you also have to configure one or several ports as backup ports If there is no longer a connection for any of the active ports of an uplink set the backup ports are activated and the ports that were active until this point are deactivated Assign the required ports of the IBP to the uplink set by opening the con text menu of each relevant port D For a LAG configuration you have to configure at least two ig active ports With PY CB Eth Switch IBP 1Gb 36 8 2 connection blades 1GB uplinks and 10 Gb uplinks must not be mixed If you try this the Next and Finish buttons will not be enabled P I 6 Select additional options
180. f 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 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 In it you can select a managed blade server chassis from the selection list The networks defined for this chassis that are suitable for the selected port are then displayed To select a network double click the name or select the name and click the Add button Make sure that the networks entered here are will be configured before the profile is activated on the corresponding blade server Cs W As long as a network does not yet exist the server profile can be created with this network but cannot yet be assigned to a slot If you wish to exit the network selection without selecting a network click the Close button or another input field Names of tagged VLAN networks You can specify tagged VLAN networks for each LAN or CNA port but not for profiles of type Rack Server If you specify more than one tagged VLAN for a port the names must be separated by commas If you use the network selection box
181. fabric 1 with FC modules in fabric 2 4 1 1 1 LAN hardware configuration Using IBP modules Fabric 1 and fabric 2 have identical configuration restrictions in relation to the IBP modules The following table shows you which configurations are sup ported in Fabric 1 and 2 Bay 1 Bay 3 Bay 2 Bay 4 IBP 10 6 IBP 10 6 optional IBP 30 12 IBP 30 12 optional 1 Even though this constellation is possible it does not make sense because only the first port can be used from the IBP 30 12 in bay 1 or bay 3 D You can also use different IBP modules within one fabric In this con stellation however not all downlinks can be used by the larger model Operation in Open Fabric mode Open Fabric mode refers to the use of non VIOM capable LAN modules together with the Virtual lO Manager In this case you can only work with vir tual I O parameters and not with dedicated network connections Therefore if you do not want to use any routing all combinations are possible even with non VIOM capable I O connection blades You must take the fol lowing into account 98 ServerView Virtual lO Manager 4 1 Configurations on the managed BX600 Blade Server e You cannot mix LAN and IBP modules within a fabric e You can only assign profiles if no networks are defined for their ports D You can force the assignment of a profile with network def initions by answering the subsequent query accordingly In doing so however the networ
182. fective IBP D 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 The labeling should also contain information about active ports and backup ports Before removing the LAN cables please make sure you have all the information you need to reconnect them to the same ports on the new connection blade 2 Now remove the defective connection blade and replace it with a new one of the same type D Important Do not connect the LAN cables at this stage 3 After booting the new connection blade check its mode If it is not run ning in IBP mode please change the mode to IBP mode and reboot the connection blade You can change the mode via the web based user interface of the management blade see Configuration tab for the select ed connection blade Check and change the Firmware Mode Setting in the MMB web based user interface 4 Make sure that the IP configuration of the new connection blades is cor rect and also that the new connection blade has the correct authen tication data Same user name and password as the old one If you are ServerView Virtual lO Manager 353 15 2 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 conn
183. for which there are no hardware ports will make it impossible to successfully assign the profile ServerView Virtual lO Manager 131 4 5 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 VIOM server profile mapping Although server profiles for PRIMERGY rack server models and blade servers differ with regard to I O channel types profiles for PRIMERGY rack servers can be assigned to blade servers and profiles for blade servers can be assigned to PRIMERGY rack servers if the target server provides the same O controllers and meets certain requirements To determine if such an assign is possible it is important to know how I O channels of blade server mezzanine cards are mapped to I O channels of PCI add on cards and vice versa Onboard I O channels are taken as they are Of course the device type of the destination ports have to be compatible to the source ports The used I O channel mapping is shown in the following table Mezzanine card in blade PCI controller in PRIMERGY rack server server Mezzanine card 1 I O port 1 PCI controller 1 I O port 1 Mezzanine card 1 I O port 2 PCI controller 1 I O port 2 Mezzanine card 1 I O port 3 PCI controller 1 I O port 3 M
184. g tasks using the server profile failover on page 332 Port If a profile is assigned to the slot or PRIMERGY rack server the column contains an entry for each port with the port number If a profile is assigned to the slot or PRIMERGY rack server this Address column contains an entry with the virtual MAC address or the vir tual WWN address for each port Network If a profile is assigned to the slot or PRIMERGY rack server the column contains an entry for each port with the names of the net works that use this port If this port is also used by service net works those names are enclosed in S and Tagged VLAN network names are enclosed in T and Example net work S service T tagged Buttons Assign Profile Click Assign Profile to assign a server profile to the selected PRIM ERGY rack server or to the selected slot of a blade server The Select Profile dialog box opens Unassign Profile Click Unassign Profile to delete server profile assignments The assign ment is deleted and no server profile is assigned to the corresponding slot or PRIMERGY rack server The display on the Server Con figuration tab is updated accordingly ServerView Virtual lO Manager 153 5 Virtual lO Manager user interface Inventory Boot Click Inventory Boot to re create the inventory table of the selected server blade or PRIMERGY rack server During inventory boot the system BIOS assembles the inventory infor mation of the server blad
185. geable SEEDS ES Ext LAN Connections Eyer na einen w exeo0 3 t Bx600 5 Details Soon Chassis IBP T UpinkSet Y Network YY VLAN Uplink Ports Backup Ports Bx900 1 Bx900 2 Bay 1 NET 41 42 Bx900 6 Gay ner a I ex900_4 Bxsoo2 av NeT 2 43 44 S VIOM Managed Bx900 2 Bayt NET3 ir 45 46 AO 111 22 11 111 pxooo 2 Bay1 NET_4 47 48 i Saux a Bx900 2 Bay1 VNET F 39 40 Bx900 2 Bay 1 E 39 40 DOPE Eee Bx900 2 Bay 1 E E 39 40 Bxo00 2 Bay 1 E INET 39 40 Bx900 2 Bay 1 E F 39 40 Bx900 2 Bay 2 3 44 Bx900 2 Bay 5 Bx900 2 Bay 7 z oomsassmmaee fioo in oao oonekarekann Copy Configurations E Lokales Intranet Rioo 150 ServerView Virtual lIO Manager 5 3 4 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 Server Configuration tab On the Server Configuration tab you can do the following e Assign server profiles to the slots of a blade server or to a PRIMERGY rack se
186. ger on a Linux based CMS 7 Click Next 8 Fujitsu ServerView Virtual IO Manager Setup Installation Configuration The following configuration is used by Fujitsu ServerView FU l SU Virtual lO Manager Please check the option Select address ranges for IO Visualization if you want to select one of the predefined MAC and WWN address ranges or if you to specify your own address range for I0 visualization If this option is not selected Fujitsu ServerView Virtual lO Manager will use no address range for virtual addresses This means that for server profiles with IO visualization for every I0 channels an address must be specified manually v Select address ranges for I0 Visualization If you select Select address ranges for IO Virtualization you can specify address ranges for virtual addressing If you want to use the automatic assignment of virtual address es in server profiles you must have already defined address ranges here 8 Click Next If you did not select Select address ranges for IO Virtualization in the previous window clicking Next brings you to the Ready to Install the Application window in which you start the installation ServerView Virtual lO Manager 79 3 Installation and uninstallation 80 If you selected Select address ranges for IO Virtualization the fol lowing window opens 8 Fujitsu ServerView Virtual IO Manager Setup Installation Configuration 92 Please select one
187. ger user interface D This is the bandwidth reserved for the FCoE function The FCoE function might share the complete bandwidth of 10 Gb with other functions A value of 60 for exam ple means that a bandwidth of at least 6 Gb sec is reserved for the FCoE packages 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 net work is created Create Network for IBP BX900 1 S03 Define networks which use this uplink set Add another network Network Name v_NET_6 VLAN ID feol Native VLAN C Service VLAN Isolate mode Network VLAN ID Native VLAN Service VLAN Isolate mode 10 F O 20 30 40 50 Finish Cancel Help Figure 37 Create Network wizard third step In this step you assign meaningful names for the networks defined via VLAN IDs which are to be assigned to the uplink set defined in the previous step Add another network Network Name meaningful name of the network 174 ServerView Virtual lO Manager 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
188. group is empty 2 Click the New button in the area on the right or select New Profile from the Profiles group context menu to launch the wizard for defining a server profile ServerList view 1 Switch to the view of the servers managed by VIOM in the area on the left using the Server List button 2 Switch to the Server Configuration tab on the right 3 Select Create Profile from the context menu of a table entry When the Create Server Profile wizard is launched proceed as follows 1 Enter the name of the profile in the first step of the wizard Name step If a profile already exists with this name or the name is invalid the name is marked in red 2 Select the type of the profile 3 Optional Select a server model under Preset values to use for server type 4 Optional Provide a comment for the profile 290 ServerView Virtual lO Manager 10 11 12 13 9 1 Defining server profiles Once you have entered all the required data click Next to go to the Con figure Cards step of the wizard Select the type and number of onboard IO channel in the Configure Cards step 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 The number of onboard ports cannot exceed the maximum pos sible value for the selected server model Furthermore no more mezzanine PCI cards c
189. gs important events in the Windows Event Logging or syslog on Linux So you can search the Windows Event Logging respectively syslog for infor mation on the Backup Services or for troubleshooting them Restoring the VIOM database on Windows Inthe event of an error you can restore the VIOM database from the back ups You must not delete the current VIOM database or the errored VIOM database If you find any errors during restoration you must restart the res toration from the beginning For the restoration you must first read in the database backup and then if available one or more transaction log backups Backups of transaction logs are available if the corresponding backup jobs are configured in the Backup Service D Before you restore the VIOM database the ServerView database E may also have to be restored For more on restoring the ServerView database please see the manual Installing ServerView Operations Manager Software under Windows Installation Guide D When the VIOM Backup Service is started the master database is backed up once Follow the same steps as described below to restore the master database as well but note that ServerView Oper ations Manager also backs up the master database It is up to the user to choose the most recent backup for that database and restore it Restoration via SQL Server Management Studio To restore the VIOM database and if available the transaction logs proceed as follows S
190. he SNMP community for SNMP traps must match the con figuration of ServerView Operations Manager It has to be ensured that SNMP traps sent by the iRMC are allowed to pass all routers and fire walls to reach the local LAN port to which the specified IP address is associated e If an operating system is installed and running ServerView Operations Manager should have SNMP access to the server It is preferable to install ServerView agents on the operating system When managing multiple PRIMERGY rack servers via VIOM the vir tualization of the I O ports together with the definition of the boot device con figuration Fibre Channel boot iSCSI boot PXE boot by VIOM allows easy shifting of an application OS boot image from one server to another To make this possible the servers that should be able to run the same image should have identical or nearly identical hardware configuration regarding I O controllers Fibre Channel controllers additional LAN controllers Converged Network Controllers If for example your VIOM server profile uses two onboard LAN ports and two Fibre Channel ports on PCI card 2 all PRIMERGY rack servers that should be able to take these server profiles must have at least two onboard LAN ports and a Fibre Channel controller in the PCI slot 2 Additional controllers in other PCI slots do not cause prob lems when assigning a VIOM server profile Missing I O ports I O ports that are configured in the VIOM server profile
191. he database configuration is taken from the ViomConfig properties file ServerView Virtual lO Manager 339 14 VIOM database Trigger description relating to the full backup job in the quartz_ jobs xml file lt trigger gt lt cron gt lt name gt cronFullBackupJobTrigger lt name gt lt group gt MSSQL cron lt group gt lt description gt lt job name gt FullBackupJob lt job name gt lt jop group gt MSSOL lt jop group gt lt cron expression gt 0 0 19 FRI lt cron expression gt lt cron gt lt trigger gt The trigger description above only belongs to the job called FullBackupJob of SQL Server There are also trigger descriptions for the Incre mentalBackupJob and BackupLogJob jobs To change the execution time for a backup job you must open the quartz_ jobs xml file and update the Quartz cron expression in the trigger description relating to the relevant backup job For a description of Quartz cron expres sions see section Syntax of Quartz cron expressions on page 340 14 1 1 1 Syntax of Quartz cron expressions This section provides a brief explanation of the Quartz cron expression syn tax In the context of the VIOM Backup Service a cron expression describes when one of the database backup jobs defined for your database will execute A Quartz cron expression is a sequence of six to seven fields separated by a blank The following fields are allowed Field Mandatory Special characters 340 ServerView Virt
192. he number of steps used and their sequence are shown in a tree structure on the left Steps that you have already completed are indicated in the tree The buttons in the bottom right of each step allow you to progress through the wizard workflow Previous Opens the previous step in the wizard ServerView Virtual lO Manager 161 5 4 1 5 Virtual lO 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 lIO Manager provides the following wizards e Create Network for IBP wizard e Edit Uplink Set wizard e Create Server Profile wizard e Edit Server Profile wizard e Configuration Backup Restore wizard Create Network for IBP wizard only for blade servers You use the Create Network for IBP wizard to define a network In the Vir tual lO 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 fol lowing steps e Defining an uplink set An uplink set contains a number of uplink ports You can combine multiple uplink ports in one uplink set You can con figure the ports as active ports or as backup ports e Possibly also defining one or several meaningful network names which are as
193. here e g to service networks But VLAN networks can also be used with tagged packets when the network is used in tagged mode see Virtual net works with VLAN ID used in tagged mode on page 38 Virtual network with a VLAN ID as native VLAN You can select a virtual network of a shared up link set as the default or native VLAN All packages that do not contain a VLAN ID will be allowed through this connection Packets that come from outside the network which do not have a VLAN tag are routed in the network with the native VLAN ID and assigned a cor responding VLAN tag in the process Packets that come from outside the network which have a VLAN tag that corresponds to the native VLAN ID are not transferred in any of the networks belonging to the uplink set They are dropped Packets that come from a server blade to the native VLAN network exit an IBP module without a VLAN tag The VLAN tag is therefore removed from the network packet before it exits the IBP module at the uplink port ServerView Virtual lO Manager 37 2 Virtual lIO Manager Introduction untagged z Server Blade 1 VLAN10 native untagged tagged 20 untagged Server Blade 2 untagged Server Blade 3 tagged 20 tagged 30 untagged Server Blade 4 Blade chassis 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 share
194. his password must be identical to the password con figured on the iSCSI target It must contain 12 to 16 characters This password must differ from the password in the Mutual Chap Secret field Mutual Chap Secret The mutual CHAP password This password must be identical to the password configured on the iSCSI target It must contain 12 to 16 char acters 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 Boot Parameters for SAN boot in the case of Fibre Channel ports or functions Create Server Profile Please fill in the boot parameters Mezzanine 1 Port 1 Ist Target Port Name W WPN 77 88 99 aa bb cc dd ee 1 2nd Target Port Name WWPN Previous Next Finish Cancel _ Help Figure 46 Boot Parameter step SAN boot 1st Target In 14st Target you configure the boot device 198 ServerView Virtual IO Manager 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 fi
195. ical functions for the two physical ports must be defined similarly This means that the storage function for both physical ports must be of the same type When using iSCSI with iSCSI boot the iSCSI initiator must be identical Excep tion physical port is completely disabled Emulex 8Gb FC HBA Assign virtual WWPN and WWNN LPE 12004 Optionally define the first and second boot tar Emulex 8Gb FC HBA LPe get and LUN 1250 1 channel Disable I O ports INTEL 2 port 10GbE Assign virtual MAC D2755 Niantec INTEL 4 port D2745 Bar ton Hills INTEL 2 port D2735 D There is no explicit disable Kawela 82576NS j functionality for I O ports in VIOM I O ports that are not INTEL Eth Ctrl 4x1Gb Cu defined in a VIOM profile will PCle x4 D3045 be implicitly disabled if the INTEL Eth Ctrl 2x1Gb Cu device supports this func PCle x4 D3035 tionality INTEL 10GbE 10GBase T RJ45 PCle LAN Optionally define PXE boot per port Disable I O ports 20 ServerView Virtual lO Manager 1 4 1 5 1 4 Changes since the previous edition For information on the required firmware version see the release notes sup plied Changes since the previous edition The current edition is valid for ServerView Virtual lO Manager V3 1 and replaces the online manual PRIMERGY ServerView Suite ServerView Vir tual lO Manager V3 0 Edition March 2012 ServerView Virtual lO Manager V3 1 includes the following new features e Suppo
196. ically assigns a virtual address after you exit the wizard Q Automatic assignment is only possible if you specified address ranges when you installed VIOM ServerView Virtual lO Manager 203 5 Virtual lO Manager user interface Next to each virtual address you see the status of the address The status can have the following values Sans 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 Not unique error The same address is in use for sev eral ports Out of range The address is outside the spec error ified address range Syntax error The address is syntactically incor error rect Already used The address is already in use error Check Addresses A check is performed to determine whether the addresses are currently in use in other profiles and whether they are within the range specified This button is only active if for at least one address Allocate virtual address has not been selected and all virtual addresses have been entered correctly 5 4 3 7 Confirm step Create Server Profile wizard Confirm is the last step in the Create Server Profile wizard In this step you can check the entries you have made once again 204 ServerView Virtual lO Manager 5
197. icate with each other but only with an external device though the uplinks This checkbox is not shown if the connection blade does not support iso late mode Link Speed By selecting a Link Speed you can select the transmission speed If auto negotiation is not selected on the extemal switch configure this value if a problem occurs using the drop down menu according to the set tings on the external switch The following values are available Auto negotiation The transmission speed is negotiated with the external switch You can achieve a transmission speed of 1 Gbit s with this value 10 Mbit s 10 Mbit s full duplex 170 ServerView Virtual lO Manager 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 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 If an uplink set for a switch stack is defined the uplink ports of all IBPs belonging to the stack are shown one below the other Use
198. iewSuite plugins viom Manager quartz_jobs xml 342 ServerView Virtual lO Manager 14 1 VIOM Backup Service For PostgreSQL If the schedule does not suit your needs you should edit the Quartz cron expression z lt cron gt lt name gt PostgresJobTrigger lt name gt lt group gt Postgres cron lt group gt lt description gt lt description gt lt job name gt PostgresJob lt job name gt lt job group gt Postgres lt job group gt lt cron expression gt 0 0 19 FRI lt cron expres sion gt lt cron gt 14 1 3 Configuring the output directories To configure the output directories for the backup jobs you must open quartz_job xml e g on Windows in the lt installation_path gt VIOM Man ager directory Example lt xml version 1 0 encoding utf 8 gt lt DOCTYPE quartz lt ENTITY outputDirLinux var f ujitsu ServerViewSuite viom postgres backups gt lt ENTITY outputDirWindows c Backups gt lt ENTITY outputLogDirWindows c Backups Log gt gt You must modify the XML entity definitions at the beginning of the file so that they suit to your requirements e The outputDirWindows entity defines the directory for full and incre mental backup files example c Backups on Windows e The outputLogDirWindows entity defines the directory for the backup files of the transaction logs example c Backups Log on Windows ServerView Virtual lO Manager 343 14 VIOM database e Th
199. igned power on pending Power off BX900 1 F05 BX900 1 Bx960 St Boot normal unassigned power on pending Power off BX900 1 F06 BX900 1 Bx960 SI Boot normal O unassigned power on pending Power off BX900 1 F07 8x900 1 Bx960 52 Boot init unassigned power on pending Bx900 1 F08 BX900 1 empty O unassigned Power off BX900 1 F09 Bx900 1 Bx92052 3060 Boot normal unassigned CiitentoryBoot_ Boot 1 Cmte states vdeo Redirection J Local intranet 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 The table provides the following information Name Name of the server blade or PRIMERGY rack server Location For server blades the name of the chassis containing the server blade otherwise empty Slot Slot number blank for PRIMERGY rack servers Type Type of the server blade or PRIMERGY rack server or blank if the slot is empty Bios BIOS version of the server blade or PRIMERGY rack server 152 ServerView Virtual IO Manager 5 3 Tabs 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 Movin
200. iguration Select an action Save chassis configuration s and or server profiles Restore Configuration Restore chassis configuration s and or server profiles Delete Configuration Delete backup file s on Management Station Figure 58 Select Action step Save Configuration Select Save Configuration to save a configuration in a file ServerView Virtual lO Manager 223 5 Virtual lO 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 D 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 In this step you select the computer on which you want to save the configuration Save Configuration Save on Management Station Name Date AllConfig xml 2011 04 18 08 41 39 BX900 2 wo Profiles xml 2011 04 18 08 40 47 Bx900 2 xml 2011 04 18 08 38 33 File O Save local File Previous Cancel Figure 59 Select File step Save Configuration wizard Save on Management Station Saves the configuration on the management station Name of existing backup files that will be overwritten 224 ServerView Virtual lO Manager
201. ile If you do not use an already configured mezzanine card you can remove it with the Delete button With the arrow buttons on the right you can change the position of a mez zanine PCI card To do this you must select a mezzanine PCl card by click ing in its box a blue border indicates that it is selected You can use the up and down arrows to move the selected card by one position If there is alrea dy acard in the target position the cards swap their places Any con figuration for the mezzanine PCI cards e g boot configuration or virtual addresses is retained 10 Channels step Edit Server Profile wizard 10 Channels is the next step in the Edit Server Profile wizard 208 ServerView Virtual lO Manager 5 4 Wizards V Use virtual addresses Disable Boot Menu Usage F12 Local boot settings used Onboard Card Network Tagged VLAN Service Boot 1 05 ian disabled Suan disabled Mezzanine Card 1 Type CNA Network Tagged VLAN Service Boot Bia _ disabled B root Bi disabled Ba ji disabled FCoE 8 disabled Mezzanine Card 2 Type FC Network Tagged VLAN Service Boot Tei disabled Ory disabled Previous Finish Cancel Help Figure 52 O 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 de
202. iles xml 2011 04 18 08 40 47 Bx900 2 xml 2011 04 18 08 38 33 File Restore local file File Previous Cancel Figure 60 Select File step Restore Configuration wizard Restore file from Management Station Backup file from the management station 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 Restore local file A backup file on the local computer on which the GUI runs File Name for the backup file 226 ServerView Virtual lO Manager 5 4 Wizards Browse Opens the file selection dialog box in which you can select the rel evant backup file 5 4 5 4 Select File step Delete Backup Files wizard Select File is the second step in the Delete Backup Files wizard In this step you select the backup files you want to delete on the management sta tion Delete Backup Files Select Files to delete Name Date AllConfig xml 2012 08 16 08 45 45 Bx900 2 wo Profiles xml 2012 08 09 08 25 52 Bx900 2 xml 2012 08 16 08 45 45 Select All Clear Selection Figure 61 Select File step Delete Backup Files wizard The table displays the backup files You can sort the list of backup files according to file name or date by clicking the table headline accordingly ha Selection box
203. iles will be deleted if you press Finish Bx900 2 wo Profiles xml Bx900 2 xml Figure 64 Select Data step Delete Backup Files wizard 230 ServerView Virtual IO Manager 5 5 5 5 1 5 5 Dialog boxes Inthis step you will see the names of the files you wish to delete The files are deleted after you have clicked Finish Dialog boxes Virtual lIO Manager provides the following dialog boxes e Authentication dialog box e Licenses Information dialog box e Restore Options dialog box e Select Profile dialog box Authentication dialog box single blade 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 a single blade server in this table the following Authentication dialog box is shown ServerView Virtual lO Manager 231 5 Virtual lO Manager user interface Authentication Enter authentication data for these modules MMB User name admin Protocol Telnet v Password eeeee Port Use for all components Use default port Bx900 21 501 User name admin Protocol Password sssss Port Bx900 24502 User name admin Protocol Password sssss Port Bx900 2 503 User name admin Protocol Password eeeee Port Figure 65 VIOM Manager authentication single blade server In thi
204. ilover process on the server blade if con figured accordingly 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 ServerView Virtual lO Manager 177 5 Virtual lO 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 aLAN team must have been configured on the server blade and the network on the second IBP module must have been con figured accordingly Enable LACP You activate the LACP protocol via Enable LACP Isolate mode You activate the isolate mode via Isolate mode With isolate mode acti vated server blades in the same chassis that use the same network can not communicate with each other but only with an external device though the uplinks This checkbox is not shown if the connection blade does not support iso late mode or if VLAN networks are edited Link Speed By selecting a Link Speed you can select the transmission speed If auto negotiation is not selected on the external switch configure this value if a problem occurs using the drop down menu accord
205. ing to the set tings on the external switch The following values are available Auto negotiation The transmission speed is negotiated with the external switch You can achieve a transmission speed of 1 Gbit s with this value 10 Mbit s 10 Mbit s full duplex 100 Mbit s 100 Mbit s full duplex 178 ServerView Virtual lO Manager 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 If an uplink set for a switch stack is defined the uplink ports of all IBPs belonging to the stack are shown one below the other Use the scroll bar to reach the uplink ports of another stack member The context menu can contain the following menu items Add Only activated if the port is not yet assigned to the uplink set Assigns the port to the uplink set If the port is already assigned to another uplink set this assignment is deleted Add as Backup Only activated if the port is not yet assigned to the uplink set Assigns the port as a backup port to the uplink set If the port is already assigned to another uplink set this assignment is dele
206. ining D The downloads include the following o Current software statuses for the ServerView Suite as well as addi tional Readme files o Information files and update sets for system software components BIOS firmware drivers ServerView agents and ServerView update agents for updating the PRIMERGY servers via Server View Update Manager or for locally updating individual servers via ServerView Update Manager Express o The current versions of all documentation on the ServerView Suite You can retrieve the downloads free of charge from the Fujitsu Tech nology Solutions Web server For PRIMERGY servers links are offered on the following topics e Service Desk e Manuals e Product information e Spare parts catalogue Access to the link collection You can reach the link collection of the ServerView Suite in various ways 1 Via ServerView Operations Manager 22 ServerView Virtual lO Manager 1 6 1 6 Documentation for the ServerView Suite e Select Help Links on the start page or on the menu bar This opens the start page of the ServerView link collection 2 Viathe ServerView Suite DVD 2 or via the start page of the online doc umentation for the ServerView Suite on the Fujitsu Technology Solutions manual server You access the start page of the online documentation via the fol lowing link http manuals ts fujitsu com e Inthe selection list on the left select Industry standard servers e Click the menu
207. inventory boot and will be switched off again automatically As described above the VIOM database contains the current profile assign ments but the failed MMB still contains the status prior to the disaster Syn chronizing the hardware with the VIOM database may be achieved by either restoring the whole chassis which is preferable because it is simple and secure By choosing Restore on the Setup tab you are ensuring that all chassis com ponents MMB connection blades server blades and IBP are correctly set but this only works if all the server blades are switched off Alternatively individual server blades slots may be restored by applying the Restore Slot function but keep in mind that this only configures the selected slot and does not restore the entire IBP As an advantage this function works in case if certain server blades need to be kept running After applying the restore function the VIOM database and the chassis hard ware of the restored site are in sync again and you may move applications back to the recovered site using the server profile assignment function 336 ServerView Virtual lO Manager 14 VIOM database This chapter describes the VIOM database on a Windows or Linux based CMS The Virtual lO Manager requires two databases e The ServerView database which is installed with ServerView Oper ations Manager and e The VIOM database which is installed with VIOM Both databases should be regula
208. ion 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 accord ingly in this dialog box 4 Click the Configure protocols button if you do not use the default pro tocols or ports The Authentication dialog box expands so that you can also configure the protocol and ports used by VIOM to access the com ponents 1 Select the protocol to be used for communication with the man agement blade or the I O connection blades Protocol 2 Specifying the port numbers for the modules if Use default port is not checked D For a standard configuration these values should not be E changed 5 When you click OK the configuration is applied and the Authentication dialog box closes 6 When you click Cancel the Authentication dialog box closes without applying your changes 260 ServerView Virtual lO Manager 7 3 Deactivating management with VIOM 7 3 Deactivating management with VIOM 7 4 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 If you are unmanaging a blade server you will receive a wa
209. ion tab 00 cccccece cece eeeees 156 5 3 6 Server Profiles View cccccecececcccceceeecccceeees 158 BA WIZ ALS oo 2 epee eles a act chk ale ate Sint Ba Mant ae Oh a 161 5 4 1 Create Network for IBP wizard only for blade servers 162 5 4 1 1 Select Type step Create Network wizard 163 5 4 1 2 Edit Properties step Create Network wizard internal network o fe hee les Peal Ne ae 164 5 4 1 3 Edit Properties step Create Network wizard single IMLAN network 0 00 eee cece e cece cece ee eee ee 165 5 4 1 4 Edit Properties step Create Network wizard ded icated service network 2 2 22 e eee 168 5 4 1 5 DCB Properties step Create Network wizard sin gle VLAN network 2 22000000 e cece ee 172 5 4 1 6 Add Networks step Create Network wizard VLAN NEWA cbs Mets ta rn otek tease coca wetaer E neonate Dien nat 174 5 4 2 Edit Uplink Set wizard 2 22222222 22022 2 2 176 5 4 2 1 Edit Properties step Edit Uplink Set wizard sin gle VLAN network 0000 e eee eeeeee 176 ServerView Virtual lO Manager 5 Contents 5 4 2 2 Edit Properties step Edit Uplink Set wizard dedicated service network 00 00 cee cece cece cece eee eeeeeeeeeee 180 5 4 2 3 DCB Properties Edit Uplink Set wizard single VLAN Network lt c ces te le Lee es et EA 183 5 4 2 4 Add Networks step Edit Uplink Set wizard VLAN ne
210. irtual IO i Disk Management information 27 05 2010 16 30 19 ServerView Virtual IO E fe Services and Applications information 27 05 2010 16 30 18 ServerView Virtual IO Information 27 05 2010 16 30 18 ServerView Virtual IO G Information 27 05 2010 16 30 17 ServerView Virtual IO information 27 05 2010 16 28 34 ServerView Virtual IO e 4 Success Audit 27 05 2010 16 28 33 ServerView Virtual IO bila Bosses 9999Nn FT99 0R 909000 Event 27 05 2010 Source ServerView VirtuallO Ma t Time 16 33 33 Category 0 Type Information EventID 50421 User N A Computer MURNAU Description Uplinkset CB1_NET1 id 7 created on LAN switch BX900_44S01 id 231 of blade server BX900_4 Data Bytes Words Figure 74 VIOM specific log file ServerView Virtual lO Manager 255 6 Using the Virtual IO Manager 6 3 2 Logging the actions on Linux On Linux the actions of VIOM are logged using the Syslog mechanism All informational messages are logged using the Syslog facility user For exam ple on SLES 11 you will find the VIOM messages in the file var log user_ messages 256 ServerView Virtual lO Manager 7 1 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 t
211. is step you can specify the CNA parameters 8 Click Finish to confirm your entries A network is created with the con figured uplink set The new network is added to the tables on the Graphic and Details tabs For further information on defining networks see section Defining networks LAN for blade servers only on page 30 Defining VLAN networks When you define VLAN networks you define an uplink set referred to as shared uplink set in the following which the various VLAN networks with different VLAN IDs share As each network within a shared uplink set is given a unique VLAN ID these networks are completely separate from one another 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 Since it is possible to use several connections simultaneously ina LAG you can achieve a higher transmission speed and greater level of reliability in the net work D In this case a static LAG is formed i e the LACP protocol is not ia supported Please note that even the ports on the external switch which are connected with the IBP ports that form a LAG also have to form a static LAG To define an VLAN networks follow the steps below 1 Click on the Ext LAN Connections tab in in the work area on the left 2 Start the Create network wizard by e clicking New on the Graphic or Details tabs e selecting New Uplink Set in the context menu o
212. isable debug mode VIOM_LICENSE_KEY The license key ServerView Virtual lO Manager 71 3 3 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 ae ECTION false 3 SV_VIOM exe q DO ADDRESS RANGE SE VIOM LICENSE KEY abcdef Updating the Virtual lO Manager on a Windows based CMS If you have already installed a previous version an update installation runs automatically when you install the Virtual IO Manager In this case all user specific configurations and definitions remain the same An update installation starts in the same way as a full installation see sec tion Installing the Virtual IO Manager on a Windows based CMS on page 58 But the update installation takes place once you have confirmed the license agreement and exited the readme window by clicking Next 72 ServerView Virtual lO Manager 3 4 3 4 Installing the Virtual lO Manager on a Linux based CMS Updating System The features you selected are currently being installed FU ITSU Installing ServerView Virtual IO Manager as service Time remaining 0 seconds Aise Installation Wizar
213. ization data server profile data is deleted for each server blade slot 3 The blade server chassis is indicated as unmanaged This happens on the one hand in the VIOM database In addition in the management blade of the blade server chassis the information that this blade server chassis is managed by this installation of the Virtual IO Manager is delet ed ServerView Virtual lO Manager 265 7 5 7 Managing servers with VIOM VIOM internal operations on a PRIMERGY rack server This section explains the internal operations perfomed when you activate or deactivate management with VIOM for a PRIMERGY rack server VIOM internal operations during activation When you activate management with the Virtual lO Manager for a PRIM ERGY rack server the following actions occur internally 1 The PRIMERGY rack server is indicated as managed by this VIOM installation This is done by assigning a corresponding status to this server node in the VIOM database and also by storing information about the VIOM installation ina VIOM specific property in the iRMC This infor mation uniquely identifies the current VIOM installation Note This infor mation is not changed during an update installation of VIOM but it does change when uninstalling and during a new installation D This information in the iRMC is always checked before a server z is managed If VIOM can recognize from this that a PRIM ERGY rack server is already managed by ano
214. ization data has been lost e Before you restore the configuration of the slots or the entire con figuration of the blade server chassis after replacing the front control board you first have to carry out the base configuration of the management blade 310 ServerView Virtual IO Manager 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 lO Manager is rewritten for a blade server chassis managed by the Virtual lO Manager e The configurations saved in the Virtual lO Manager are performed again accordingly for all the IBP modules in the chassis e The virtualization data of the assigned profiles is saved again in the chas sis using the existing configuration data in the Virtual lO Manager for each server blade slot Any installed server blades must be disabled for this AY ServerView Virtual lO Manager 311 312 ServerView Virtual lO Manager 12 12 1 Importing and exporting server pro files You have the option of exporting and importing server profiles The exported data is available as XML files that can be modified or enhanced You can use this procedure for example if you want to create a number of profiles without using the wizard The format of the exported files or the files to be imported is described in section Format of export files on page 314 Exporting server p
215. k definitions are ignored e 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 2 Fibre Channel hardware configuration You can only install the Fibre Channel switch blades in fabric 2 They can be operated in two different modes e in normal switch mode e in Access Gateway mode As a result different combination options are possible The following table shows you which configurations are possible and which are supported in fab ric 2 Bay 4 Access Gateway mode Access Gateway mode Standard switch mode Standard switch mode Access Gateway mode Access Gateway mode Standard switch mode fF ae Standard switch mode Configuring the BX600 management blade The blade server must be fitted with one or two S3 management blades The management blade has two user friendly user interfaces a Web inter face and a Remote Manager interface per Telnet or SSH protocol a con nection to the management blade is established per Telnet or SSH You can ServerView Virtual lO Manager 99 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 e The management blade must be installed with a specific firmware ver sion To find out which firmware version you need see the release notes included You can check the firmware version in the Remo
216. l lIO Manager 3 6 License management e If you do not have a valid license you cannot log in to the VIOM Man ager e Ifthe 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 Delet ing profile assignments on page 298 or Unmanage see section Deac tivating management with VIOM on page 261 A license check is performed automatically when you install VIOM see sec tion Installing the Virtual IO Manager on a Windows based CMS on page 58 and periodically during the running time of the VIOM service On Windows you can also launch the License Manager the tool for man aging licenses separately from the Windows Start Menu e g to specify new or additional licenses On Linux you can also launch the License Manager by starting the license sh script which you find in the installation directory of VIOM 1 On Windows Choose Start All Programs Fujitsu ServerView Suite Virtual lO Manager License Management On Linux Execute the command sh license sh FAVIOM License Manager ol xj n License string Version bound Duration days Assign count Register new license 4T3P MHQG A4GY 5SNBP FNC3 OX5Y JUAY v2 14 18 Total assign limit 18 Assigned profiles 0 Assign credits 18 Exit Invalid licenses e g expired or banned licenses are
217. l lO Manager performs a special so called inventory boot which creates an inventory table for this server in the iIRMC This inven tory table is used to check the availability of the required I O devices when assigning a VIOM server profile to this PRIMERGY rack server Therefore you will see that a PRIMERGY rack server is powered on when a server is managed by VIOM This inventory boot does not boot an operating system it powers down the server when the inventory table is created and stored in the iIRMC After these actions the PRIMERGY rack server is integrated into the VIOM management and is ready to be assigned a VIOM server profile When assigning a VIOM server profile the following actions are performed 1 VIOM checks that the server is powered off by reading the power state reported by the iRMC VIOM reads the inventory data stored in the IRMC and checks whether the server supplies the I O devices configured in the VIOM server profile that is to be assigned to this server VIOM writes virtualization data to the iRMC This data contains the vir tual addresses for all the configured I O devices in the VIOM server pro file and also the boot information The virtualization data also contains the port disable configuration for any I O device found in the inventory data of this server for which the server profile does not contain a con figuration VIOM cannot guarantee that all I O devices that are not con figured in the pr
218. le This server profile can be assigned toa PRIMERGY rack server or server blade e For PRIMERGY rack servers A server profile can be assigned to a PRIMERGY rack server and can also be moved from one PRIMERGY rack server to another e For blade servers The server profile can be assigned to a server blade using VIOM and can also be moved between different server blades of the same or of another blade server By assigning the server profiles to a server you can start the required appli cation without having to reconfigure the SAN and LAN network ServerView Virtual lO Manager 11 1 1 1 2 1 Introduction VIOM provides an easy to use Web based graphical user interface which you can launch using the ServerView Operations Manager Using this inter face you can carry out all the necessary tasks for managing the I O param eters of a PRIMERGY blade server or PRIMERGY rack server and for the LAN connection blade the IBP module in PRIMERGY blade server VIOM also provides a comprehensive command line interface which you can use to perform administrative VIOM tasks in a script based environment The VIOM CLI command line interface provides an easy to use interface for creating scripts and automating administrative tasks The command line interface is available both on Windows and Linux plat forms and you install it using separate installation packages For more infor mation on VIOM CLI see the documentation entitled ServerVie
219. lect Data step of the Restore Configuration wizard It also opens when you click the Options button in the table row In this dialog box you can specify additional parameters to restore blade server configurations ServerView Virtual lO Manager 241 5 Virtual lO Manager user interface D 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 Soin this case you cannot change any of the options Restore Options Restore BX900 2 C Restore Spare Information C Reassign Profiles C Restore On Different Chassis Figure 71 Restore Options dialog box blade server Restore Spare Information Specifies whether the information on the spare slots is restored Reassign Profiles Specifies whether the profiles which were assigned when the backup was performed are reassigned This option is only enabled if the backup contains profiles If Profiles is not selected in the Select Data step of the Restore Con figuration wizard it is selected automatically when you close this dialog box with OK In this case the Restore only reassigned profiles option see Restore Options dialog box server profiles on page 243 will be selected for profiles Restore On Different Chassis Specifies that the backup is restored on another blade server If you select this option a B
220. left tree M Trusted sites Figure 25 Virtual lIO Manager tab Show Licenses Displaying information on the licenses assigned see section Dis playing license information on page 275 Preferences Showing and modifying user preferences see section Preferences dialog box on page 238 Configuration Backup Restore Saving and restoring the blade server configuration and the server pro files see chapter Saving and restoring on page 303 ServerView Virtual lO Manager 143 5 Virtual lO Manager user interface 5 3 2 Setup tab Using this tab you specify whether an object is to be managed with VIOM or not e Fora 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 e Fora blade server or PRIMERGY rack server in the VIOM Managed server group you can deactivate management with VIOM by adding this server to the VIOM Manageable server group Virtual IO Manager tx200s3 sw5 Windows Internet Explorer ek S ServerView User administrator Logout Fujitsu Home gt gt Virtual 10 Manager 4 Al Server VIOM Manageable Wirtual TO Manager su Ext LAN Connections Server Configuration Chassis Configuration w Bx600 3 VIOM Status Managed by VIOM Ok Click on blade slot or switch to get information Housing Name BX900 2 Model Type Bx900 04 IP address of MMB 11
221. ls you must use the command line interface of the service manager The command sc qfailure Server ViewVirtualIOManagerService displays the current con figuration where ServerViewVirtuallOManagerService is the name of the service e The ServerView Virtual lO Manager Backup service is also configured for automatic restart in the event of failure during installation D By default the Virtual lO Manager Backup service is not con ig figured to start automatically as it requires configuration By default the following restart behavior is configured o The first restart of the service is tried 5 seconds after unexpected ter mination of the service o The second restart is tried 30 seconds after termination of the serv ice o Subsequent restarts are tried 120 seconds after termination of the service fe The restart counter is reset after 600 seconds The details of this configuration cannot be seen via the nor mal graphical user interface of the service manager To see the details you must use the command line interface of the service manager The command sc qfailure Server ViewVirtuallOBackupService displays the current con figuration where ServerViewVirtuallOManagerService is the name of the service e f the Virtual lO Manager is interrupted during a configuration request for example creation of networks in an IBP connection blade or assignment of a VIOM server profile while executing configuration commands on hardwar
222. ly works if the chassis MMB connection blades and server blades are accessible to the VIOM man agement station which is typically not the case in such a disaster scenario 334 ServerView Virtual lO Manager 13 3 Disaster Recovery To allow the switchover in this case VIOM provides a forced unassign option allowing you to unassign a profile even if the corresponding MMB con taining this profile is not available But applying this function means that there will be two chassis with at least partially identical profiles potentially resulting in for example duplicate vir tual addresses as soon as the failed site goes online again This chapter describes the settings and procedures for avoiding duplicate addresses and how to handle a site failover with VIOM As already mentioned there are two major issues unassign the profiles at a failed no longer reachable site and handle the power on procedure of the failed site to avoid duplicate MAC and WWN addresses The first issue is solved by the forced unassign function which is available as amenu item in the VIOM Web GUI as a CLI command D But beware This function should only be used if there is no other z way to get the profile unassigned A forced unassign will only remove the profile to server blade assignment in the VIOM data base but not in the corresponding hardware MMB IBP server blade If you later assign this profile to a different server blade you
223. mplemented ServerView Virtual lO Manager 105 4 Configuration Management a console tocco SS Central Management gt Management LAN Switch Station Productive LAN Switch IBP 2 optional Management LAN Productive LAN Figure 15 BX600 Network Overview Port 0 11 for an IBP 10 6 or port 0 31 for an IBP 30 12 must be connected to the central management station 4 1 4 2 Notes and recommendations We recommend that you do not use the first uplink port in the network def initions If you cannot avoid doing so then you must note the following e The speed definition used must remain set to auto negotiate e The network that uses this uplink port must not be deleted 106 ServerView Virtual lO Manager 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 Establish a Telnet or SSH connection to the management blade of the affected blade server chassis Example Telnet 10 10 10 50 3172 Enter the authentication data for the management blade In the Remote Manager choose 3 Console Redirection 2 Con sole Redirect Connection Blade Select the affected
224. multicast group or removed again The IGMP Snooping option is selected by default 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 If an uplink set for a switch stack is defined the uplink ports of all IBPs belonging to the stack are shown one below the other Use the scroll bar to reach the uplink ports of another stack member The context menu can contain the following menu items Add Only activated if the port is not yet assigned to the uplink set Assigns the port to the uplink set If the port is already assigned to another uplink set this assignment is deleted Add as Backup Only activated if the port is not yet assigned to the uplink set ServerView Virtual lO Manager 167 5 Virtual lO 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 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
225. n 5 Add the transaction log file ViomDBLog bak from the appropriate stor age 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 col umn Switch to the Options page 8 Select the option Overwrite the existing database If you want to restore further transaction logs select the option Leave the database non operational and do not roll back uncommitted transactions Additional transaction logs can be restored If you want to restore the last transaction log select the option Leave the database ready to use Additional transaction logs cannot be restored 9 Click OK and then OK again Once the last transaction log has been restored the database status must be normal again The add on Restoring is no longer displayed in the Object Explorer The services ServerView Virtual IO Manager Services and ServerView Virtual IO DB Backup Services must be restarted 348 ServerView Virtual lO Manager 14 2 Restoring the VIOM database on Windows 1 Select Start Settings Control Panel Administrative Tools Services 2 Select the appropriate service and then select Restart from the context menu It is now possible to access the VIOM database via Virtual lO Manager again 14 2 2 Restoration via Enterprise Manager Enterprise Manager may be used for SQL Server 2000 to restore the VIOM database How this is done for the
226. nagement blades see section Configuring the BX400 management blade on page 113 e Configure the I O connection blades see section Configuring the I O connection blades on page 114 ServerView Virtual lO Manager 109 4 Configuration e Define the connection of the IBP modules with the network see section Connecting IBP modules on page 115 e Add the blade server to the server list of the ServerView Operations Man ager see section Adding a server to the ServerView server list on page 135 4 2 1 Supported hardware configurations for the connection blades The following connection blades are supported in a BX400 e 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 LAN connection blades can be inserted in connection bay 1 of fabric 1 in order to connect the onboard LAN ports in connection bay 2 of fabric 2 in order to connect the onboard LAN ports of the first mezzanine card or in connection bays 3 and 4 of fabric 3 in order to connect the LAN ports of the second mez zanine card To define dedicated network connections for server blades with net works you require LAN connection blades in IBP mode The 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 con nection blades support a normal Layer 2 switch mode and IBP mo
227. nction properly p Back Next gt Cancel 14 Click Next to launch the License Manager vI0M License Manager 0 x E License string I Version bound Duration days I Assign count Register new license Deregister licenses Total assign limit 0 Assigned profiles 0 Assign credits 0 Exit ServerView Virtual lO Manager 67 3 2 2 3 Installation and uninstallation 15 Click Register new license Register new license xj Please enter license string Cancel Enter at least one valid license here so that you can use the Virtual lO Manager functions You can enter several licenses here For more infor mation on the License Manager see section License management on page 90 D e The licenses are not version bound I e Licenses purchased with Virtual IO Manager versions prior to V2 4 are also still valid These licenses v1 contain a chassis count which is multiplied by 18 to get the assign count used in licenses v2 purchased with Virtual IO Man ager V2 4 or later 16 Click Exit in the VIOM License Manager dialog box to exit the License Manager The dialog box closes 17 Click Finish to end the installation Installing the Virtual lO Manager using the command line interface The Virtual lO Manager can be installed using the command line interface You start the installation via the installation package SV_VIOM exe which you will find on the ServerView Suite DVD 1 un
228. nd PRIMERGY rack servers Video Redirection Click Video Redirection A new window opens where the console out put of the server is shown Context menu Inthe table or the graphic several actions can be choosen from the context menu of the selected server click right mouse button Assign Profile Assign a server profile to a slot or PRIMERGY rack server Unassign Profile Remove the assignment of a server profile from a slot or PRIMERGY rack server Create Profile Create a server profile Show Profile Details View definition of the assigned server profile Update State Update the power state display the boot mode and the virtualization stat us of a server Inventory Boot Re create the inventory table of the server blade s and PRIMERGY rack server s ServerView Virtual lO Manager 155 5 3 5 5 Virtual lO 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 pro files on page 289 Chassis Configuration tab The Chassis Configuration tab provides an overview of the blade server configuration e The IBP configuration e The server profile assignment You can select an uplink port a network or a bay by clicking it The elements associat
229. nents if Use default port is not checked D For a standard configuration these values should not be changed 5 When you click OK the configuration is applied and the Authentication dialog box closes The tabs in the area on the right are then activated 6 When you click Cancel you close the Authentication dialog box with out applying your changes and end the activation process Changing access rights and ports You can also change the access rights and ports for the components MMB IBP or PRIMERGY rack servers retrospectively 1 Select the required server To do this click the required server on the left of the VIOM window in the VIOM Managed server group ServerView Virtual lO Manager 259 7 Managing servers with VIOM 2 Click Authentication on the Setup tab The Authentication dialog box opens See Authentication dialog box single blade server on page 231 Authentication dialog box PRIMERGY rack server on page 234 3 Enter the user names and passwords for the individual components for the management blade and for all I O connection blades or for the PRIM ERGY rack servers which VIOM can use to access these com ponents By default the user name admin and password admin are set up for all components In this case you must only enter the user name and pass word 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 connect
230. nfiguration is restored If you select the Keep existing profiles option select what is to happen with the existing profiles of the same name in On Existing Profiles Abort Restore The restore operation is canceled and an error message displayed Rename Restored Profiles The existing profiles are renamed by adding the backup date and possibly also a number to the file names Replace Existing Profiles The existing profiles are replaced by the profiles contained in the backup Use Existing Profiles The profiles are not restored and the existing profiles continue to be used instead Assign new virtual addresses The restored profiles are assigned new virtual addresses Restore Address Ranges Specifies that the origin address ranges will be restored 244 ServerView Virtual lO Manager 5 5 Dialog boxes This will be necessary if address ranges have been changed since the backup configuration has been saved or if it is created on another man agement station This option cannot be selected together with Keep existing profiles 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 Inthe Select Profile dialog box you can select the required server profile in the tree structure The area on the right displays information on the selected profile To open this dialog box click Assign Profile or select Assign Profile in the context me
231. ng of the various icons 5 1 Virtual lO Manager main window Once you have launched the Virtual IO Manager the following main window is displayed ittps tx200s3 sw5 seryware abg fsc net 3170 Lang en Virtual IO Manager tx200s3 sw5 Windows Internet Explorer DER S ServerView User administrator Logout Vertual 10 Manager Setup Ext LAN Connections Server Configuration Chassis Configuration ServerView Virtual IO Manager P Rx20057 v10M4 VIOM server https tx200s3 sw5 servware abg fsc net RX30057 VIOM4 GUI version 3 1 0 buld 2012 08 08 07 11 55 H Txao0s7 v1om3 API version 3 1 0 buld 2012 08 06 13 07 06 20 A e VIOM manager 3 1 0 buld 2012 06 06 13 07 11 java 1 6 0_33 b03 Configuration Backup Restore Currently one server is managed by VIOM To manage a server by VIOM select it in the left tree and choose manage To configure a managed server select it in the left tree oJ Trusted sites Figure 22 VIOM main window ServerView Virtual lO Manager 137 5 Virtual lO Manager user interface The window is divided into three areas e The ServerView Suite header e The menu bar e 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 e ServerList e Administration e Asset Management e Event Management e Monitoring e Updat
232. nstallation Vizard R Back Cancel Enter your name and the name of your company organization You must also specify whether the settings should only apply for the current user or for any user working on this system Select the corresponding option ServerView Virtual lO Manager 61 3 Installation and uninstallation 10 62 Click Next iz Fujitsu Server iew irtual IO Manager Setup a x Installation Configuration The following configuration is used by Fujitsu ServerView FU l I SU Virtual lO Manager Please check the option Select address ranges for IO Virtualization if you want to select one of the predefined MAC and VWVYN address ranges or if you want to specify your own address range for IO virtualization If this option is not selected Fujitsu ServerView Virtual lO Manager will use no address range for virtual addresses This means that for server profiles with IO virtualization for every IO channel an address must be specified manually MV Select address ranges for IO Virtualization Aise Installation Vyizard If you select Select address ranges for IO Virtualization you can specify address ranges for virtual addressing D If you want to use the automatic assignment of virtual address es in server profiles you must have already defined address ranges here Click Next If you did not select Select address ranges for IO Virtualization in the previous window clicking Next brings you
233. nts all other networks as blue lines with round endpoints The slots are displayed for each connection bay In the figure above only the connections for Connection Bay 1 are displayed The other connection bays are displayed below this one The server blade in Slot 1 is connected to the network NET_1 via the server profile profile2 This applies to LAN ports 1 and 3 of this blade onboard LAN port 1 and 3 are assigned to Connection Bay 1 Update States Updates the display of the on off status of the server blades in the rec tangle of the slots Server Profiles view The Server Profiles view shows the defined server profiles To open the Server Profiles view in the area on the right of the ServerView Virtual lO Manager window click Profiles in the area on the left of the ServerView Virtual lO Manager window 158 ServerView Virtual lO Manager 5 3 Tabs Virtual I0 Manager tx200s3 sw5 Windows Internet Explorer ta S ServerView User administrator Logout Fujitsu SenverList SET al Asset Management Deployment EyentManagement Monitoring Update Management Security ServerBrowser Server Configuration VirtualiO Manager Users Passwords National Settings Base Configuration Wizard Home gt gt Virtual IO Manager Server Profiles profilet profile2 profile unassigned Mezzanine 1 Port 1 Mezzanine 1 Port 2 Onboard 1 Onboard 2 profile2 unassigned Comment for double
234. nu of the required slot or PRIMERGY rack server on the Server Configuration tab ServerView Virtual lO Manager 245 5 Virtual lO Manager user interface Select Profile Select the profile to be assigned Profiles double profilet profile2 No profile selected C Ignore ext LAN connections C Ignore Spare C Skip downlink checks 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 waming 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 net works of the server profile Then no paths are configured and only the vir tual addresses are used 246 ServerView Virtual lO Manager 5 6 5 6 1 5 6 Context menus Ignore Spare No warning during assignment to a spare slot Skip downlink checks OK No warning even though ports are configured in the server profile for which there are no downlinks in the IBP If anetwork 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 The selected server profile is assigned to the slot D m If you have not selected Ignore ext LAN connec
235. nux Instal lation Guide VIOM Backup Service The Backup Service of the Virtual lO Manager is a service used to peri odically back up the VIOM database D Note that its sole purpose is currently to back up the VIOM data base whereas the backup of ServerView database is done by ServerView itself But a backup of the VIOM database will be of little use if the ServerView database is lost So in general you should back up both databases periodically at roughly the same times Under Windows the Backup Service is designed as a Windows service using the Open Source Quartz framework The service schedules backup jobs for the databases currently used by VIOM namely SQL Server on Windows respectively PostgreSQL on Linux The Backup Service allows three types of backup for which there is one backup job each e A full backup of the database full backup job on Windows and Linux e Anincremental backup of the database incremental backup job on Windows only e The backup of the transaction logs transaction backup job on Win dows only Note that under Linux and PostgreSQL no transaction logs are saved only full backups You may modify the schedule of these backup jobs in a syntax similar to UNIX cron format The Backup Service is integrated in the install packages of VIOM Manager The Backup Service does not start directly after installation as it must be configured first After this you must start it manually
236. o 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 The following sections describe how to activate or deactivate VIOM man agement of a server and how to set or change the access rights and ports Please note A server may always only be managed by one man agement station with the Virtual lIO Manager If nevertheless you try to manage a server from a different management station you receive the message that this server is already being managed by a management station P Wp You can ignore this warning if you want to manage the VIOM from another management station In this case however you need to ensure that the other installation of the Virtual lIO Manager no longer exists Otherwise you will have undefined statuses in the managed server After the Virtual lO Manager is reconstructed on the CMS due toa hardware failure uninstalling and reinstalling etc you will need to power off all target servers that are managed by the Virtual lO Man ager because the networks have to be reconfigured and the server profiles are reassigned ime Activating management with VIOM To manage a server with VIOM you have to select the server from the VIOM Manageable server group and add it to the VIOM Managed server group You do this using the Manage button on the Setup tab ServerVie
237. ocal computer Comment optional Comment on a more detailed description of the profile SmuxSettingMezzanine2 optional If a second mezzanine card is defined as a LAN card this element is used to specify the fabric to which the card is routed Possible values are Fabric3 All paths are routed to fabric 3 318 ServerView Virtual lO Manager 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 lOChannels Defines the ports This element contains an OChannel element for each port of the profile see below 12 3 4 The lOChannel element An lOChannel element contains the following elements lOChannelSpec Specifies the port and contains the following elements lOChannelType Specifies the port type LAN LAN port FC FC port ISCSI For future use LANFunction Physical LAN function of a CNA port FCFunction Physical FCoE function of a CNA port ServerView Virtual lO Manager 319 12 Importing and exporting server profiles ISCSIFunction Physical iSCSI function of a CNA port 10Slotindex 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 lOBoardType Type of board to which the port belongs OnBoard OnBoard DaughterC ard Mezzanine card AddonCard PCI card lOBoardNumber Number of the board to which the port belongs always 1 fo
238. ofile are disabled This only works on devices that ServerView Virtual lO Manager 267 7 Managing servers with VIOM support this functionality VIOM performs a special so called init boot that initializes all the I O devices with the virtualization configuration This init boot can be avoid ed and a normal boot performed instead This option is available in the VIOM user interface when assigning a profile option Power On after Assign All the VIOM specific initialization is also performed during a normal boot The special init boot does not try to boot an operating sys tem it always powers off a server after the initialization is done When the init boot is successfully completed the server reports the stat us VIOM_SETTING_OK This status information is available in the VIOM user interface on the Server Configuration tab in the table col umn state In some situations you may need to manually update this information in order to get the current state To do this click the Update States button The status VIOM_SETTING_FAILED indicates a failure In this case the server will not be able to boot and a request to power on will result in a power off status when the VIOM initialization fails The system event log accessible via the iRMC interface will contain further information about this event The status POWER_ON_PENDING indicates that an initial or normal boot is still outstanding and the virtualization configuration is not in effect
239. ogs all actions in the Windows Event Log including logins to the Virtual lIO Manager and all changes to the specific blade server configuration on the Virtual lO 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 254 ServerView Virtual lO Manager 6 3 Logging the actions using VIOM Computer Management Sy File Action View Window Help mF A ee m Computer Management Local a EA System Tools G Information 31 05 2010 09 37 54 ServerView Virtual IO B E Event viewer information 31 05 2010 09 37 52 ServerView Virtual IO 8 Application information 31 05 2010 09 37 52 ServerView Virtual IO of Security information 31 05 2010 09 34 59 ServerView Virtual IO f Serverview vrom Success Audit 31 05 2010 09 34 53 ServerView Virtual IO rae powershel mformatin 27 05 2010 16 33 43 ServerView Vrtual I0 Shared Folders Information 27 05 2010 16 33 37 ServerView Virtual IO Local Users and Groups Information 27 05 2010 16 33 33 Serverview Virtual IO Performance Logs and Alert information 27 05 2010 16 32 06 ServerView Virtual IO f Device Manager Qeror 27 05 2010 16 30 36 ServerView Virtual IO 8 amp Storage Information 27 05 2010 16 30 21 ServerView Virtual IO Removable Storage information 27 05 2010 16 30 20 ServerView Virtual IO Disk Defragmenter information 27 05 2010 16 30 19 ServerView V
240. om different manufacturers which can lead to interoperability problems between the internal and external switches of different providers 26 ServerView Virtual lO Manager 2 2 Special connection blade for blade server To resolve these problems the switch blades installed in the blade server can be replaced by special connection blades The following connection blade are available for this e ForSAN BX600 BX600 4 4Gb FC Switch 12port SW4016 SW4016 D4 in the Access Gateway mode FC AG BX400 BX900 Brocade 5450 8 Gb Fibre Channel Switch in the Access Gateway mode FC AG e ForLAN BX600 BX600 GbE Intelligent Blade Panel 30 12 or 10 6 IBP GbE BX400 BX900 Connection Blade PY CB Eth Switch IBP 1Gb 36 8 2 PY CB Eth Switch IBP 1Gb 36 12 PY CB Eth Switch IBP 1Gb 18 6 or PY CB Eth Switch IBP 10 Gb 18 8 in the IBP mode The connection blades can run in switch mode in IBP mode or in End Host Mode EHM These connection blades offer the advantage of a switch cable con solidation without the above mentioned disadvantages ServerView Virtual lO Manager 27 2 3 2 Virtual IO Manager Introduction Server Administration Figure 2 Separate areas of responsibility Management with VIOM Procedure You use the ServerView Virtual lO Manager VIOM to manage the con nection blades of a blade server and to maintain the relevant I O parameters constant at the chassis slot of a blade server or at the PRIMERGY rack ser
241. om one server blade to another To do this you define spare slots It is advisable to install server blades in the spare slots that you do not use for regular operations 2 You can also use a spare slot as a completely normal slot even though it has been configured as a spare slot 1 Click Server List if applicable to switch to the server list view in the area on the left 2 Inthe tree structure on the left select the corresponding blade server from the VIOM Managed group 3 Switch to the Server Configuration tab in the area on the right 332 ServerView Virtual lO Manager 13 3 Disaster Recovery 4 Define the slots that are to be available as spare slots for a server profile failover To do this enable the check box in the Spare column in the table for the relevant slots If an error occurs or maintenance work needs to be carried out select the Fail over function in the context menu of the affected server blade on the Server Configuration tab In this case VIOM searches for the slot configured as a spare slot When it has found a suitable slot it deletes the previous profile assignment and assigns the profile to the spare slot The server blade installed in the spare slot therefore assumes the role of the failed server blade including the network addresses D e The profile can only be assigned to the spare slot if the server gt blade in this slot is switched off power off see also section Assigning server profiles
242. on Linux Inthe event of an error you can restore the VIOM database from the back ups You must not delete the current VIOM database or the errored VIOM database If you find any errors during restoration you must restart the res toration from the beginning D Before you restore the VIOM database the ServerView database may also have to be restored For more on restoring the ServerView database please see Installing ServerView Operations Manager Software under Linux Installation Guide Here are the additional steps for restoring the VIOM database 1 Stop the VIOM Backup Service etc init d viom_backup stop 2 Stop the VIOM Manager Service etc init d viom_man stop 3 Import the VIOM database bzip2 cd var fujitsu ServerViewSuite viom postgres backups ViomDB dump bz2 opt fujitsu ServerViewSuite Postgresql pgsql bin psql p 9212 d ViomDB U svuser 4 Start the VIOM Manager Service etc init d viom_man start 350 ServerView Virtual lO Manager 14 3 Restoring the VIOM database on Linux 5 Start the VIOM Backup Service etc init d viom_backup start ServerView Virtual lO Manager 351 352 ServerView Virtual lO Manager 15 15 1 Appendix Replacing IBP modules If an IBP connection blade in a chassis managed by Virtual lIO 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 de
243. operated in two different modes e in normal switch mode e 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 The following table shows you which configurations are sup ported in fabric 3 Bay 3 Bay 4 Access Gateway mode Access Gateway mode optional Standard switch mode Standard switch mode optional 1Even though this constellation is possible it does not make sense because only the first port can be used from the Fibre Channel switch blade in bay 3 112 ServerView Virtual lO Manager 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 e The management blade must be installed with a specific firmware ver sion To find out which firmware version you need see the release notes included You can check the firmware version in the Web interface by selecting a management blade component on the left and then checking the value of Firmware Version on the Information tab If your firmware version is lower than the version required you must updat
244. or 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 This card can have up to two ports With lO Channels you specify the number of ports for the card to be sup ported with this server profile If you do not use an already configured mezzanine card you can remove it with the Delete button With the arrow buttons on the right you can change the position of a mez zanine PCI card To do this you must select a mezzanine PCl card by click ing in its box a blue border indicates that it is selected You can use the up and down arrows to move the selected card by one position If there is alrea dy a card in the target position the cards swap their places Any con figuration for the mezzanine PCI cards e g boot configuration or virtual addresses is retained 10 Channels step Create Server Profile wizard 10 Channels is the next step in the Create Server Profile wizard 190 ServerView Virtual lO Manager 5 4 Wizards J Use virtual addresses Disable Boot Menu Usage F12 Local boot settings used Onboard Card Network Tagged VLAN Service Boot E e disabled van el disabled Mezzanine Card 1 Type LAN Network Tagged VLAN Service Boot e i disabled 2 Biman f disabled Previous Next Finish Cancel j Help Figure 44 O Chann
245. ot has been found the profile assignment on the affected server blade is deleted and the server profile is assigned to the new server blade The new server blade thus assumes the role of the failed server blade including the network addresses D The Virtual IO Manager does not make any changes to the boot image in a SAN and does not clone any disk images to the local hard disk of the replacement server blade ServerView Virtual lO Manager 47 2 Virtual lIO Manager Introduction High Availability HA support VIOM supports the following high availability environment e Windows 2008 R2 Hyper V cluster with ServerView Operations Man ager and ServerView Virtual IO Manager installed on a virtual machine with Windows Server operating system e VMware HA with ServerView Operations Manager and ServerView Vir tual lO Manager installed on a virtual machine with Windows Server oper ating system This means that the ServerView management station is a virtual machine run ning on a Windows 2008 Hyper V cluster or ina VMware HA environment High availability of Hyper V cluster The following Hyper V high availability configurations will be supported Operating system Admin server if H Windows Server 2003 R2 Enterprise x86 x64 SP2 or higher Windows Server 2003 R2 Standard x86 x64 SP2 v or higher Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise 48 ServerView Virtual IO Manager 2 7 High Avail
246. ow the steps below 1 Click on the Ext LAN Connections tab in in the work area on the left 2 Start the Create network wizard by e clicking Newon the Graphic or Details tabs e selecting New Uplink Set in the context menu of an uplink set The Create network wizard is launched 3 Inthe first step of the Create network wizard select Internal network and confirm your entry by clicking Next The second step of the Create network wizard opens 4 Enter the required name for the internal network in Name of network Confirm this by clicking Finish The internal network is configured with the specified name You cannot edit an internal network To find out how to delete an internal net work see Deleting networks on page 286 ServerView Virtual lO Manager 279 8 1 2 8 Defining network paths LAN Defining a single network In VIOM a single network refers to a network in which a server blade can communicate extemally 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 Since it is possible to use several connections simultaneously ina LAG you can achieve a higher transmission speed and greater level of reliability in the net work D A static LAG is formed by default i e the LACP protocol is not sup
247. pecified for functions and must not be specified for other IOC hannelType 12 3 5 The Address element An Address element that specifies the E MAC address of a CNA FCoE func tion must have the attribute purpose fcoe Each other Address element must have the attribute purpose normal If it does not contain any elements the VIOM Manager automatically assigns the virtual addresses according to the port type during the import ALAN port CNA LAN function or CNA iSCSI function may contain the VirtualMAC element whose value is the virtual MAC address An FC port may contain the VirtualWWNN and or VirtualWWPN elements whose values are the corresponding virtual addresses If only one of these two elements is specified the VIOM Manager automatically assigns the other virtual address during the import A CNA FCoE function may contain the VirtualMAC element additional to the elements of a FC port If it is not specified the VIOM Manager assigns the E MAC address during import The ignoreRange attribute of the VirtualMAC VirtualWWNN and VirtualWWPN elements specifies whether the given virtual address is in the range that was specified when you installed VIOM Possible values for this attribute are Yes ignore the range and No check the range 12 3 6 The BootEnvironment element The BootEnvironment element contains the BootPriority element and one of the following elements e PXEBootConfiguration e ISCSIBootConfiguration ServerVi
248. pgrade When running an update installation all user specific configurations and def initions remain the same An update installation starts in the same way as a full installation see sec tion Installing the Virtual IO Manager on a Linux based CMS on page 73 But the update installation takes place once you have confirmed the license agreement and exited the readme window by clicking Next ServerView Virtual lO Manager 89 3 Installation and uninstallation EX Fujitsu ServerView Virtual IO Manager Setup Updating System The features you selected are currently being installed FUJI SU Installing Cancel 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 D e The licenses are not version bound e Registered licenses for an installed Virtual lO Manager version prior to V2 4 are multiplied internally by 18 This means that the chassis count of these licenses v1 is converted x18 into the assign count used in licenses v2 used as of Virtual lIO Man ager V2 4 The specified licenses are verified when you launch VIOM 90 ServerView Virtua
249. port as the boot device select PXE boot iSCSI boot or SAN boot from the selection list under Boot If you configure an 292 ServerView Virtual IO Manager 15 16 17 18 9 1 Defining server profiles iSCSI boot device or SAN boot device you must specify additional boot settings in the next step Click Next to access another step in this wizard The next steps depend on what you configured in the O Channels step 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 You specify the boot order by using the arrow buttons on the right to move the boot devices up or down The boot parameters for each port are specified in the corresponding field You have to specify additional parameters for an iSCSI boot in the case of LAN ports and SAN boot in the case of Fibre Channel ports You do not have to specify any additional parameters for a PXE boot in the case of LAN ports If you configured at least one CNA 1O channel another step in this wiz ard is the CNA Parameter step In this step you specify the CNA parameter for all physical functions If you selected Use virtual addresses in the lO Channels step of this wizard another step in this wizard is the Virtual Addresses step You specify the virtual addresses in this step For each address you can enter a
250. predefined WWN address ranges are WWN1 Range 50 01 99 93 ED 2A 10 00 50 01 99 93 EF 1E 0D FF ServerView Virtual lO Manager 3 4 Installing the Virtual lO Manager on a Linux based CMS WWN2 Range 50 01 99 93 EF 1E 0E 00 50 01 99 93 F 1 12 0B FF WWN3 Range 50 01 99 93 F 1 12 0C 00 50 01 99 93 F3 06 09 FF WWN4 Range 50 01 99 93 F3 06 0A 00 50 01 99 93 F4 FA 07 FF WWN5 Range 50 01 99 93 F4 FA 08 00 50 01 99 93 F6 EE 05 FF WWN6 Range 50 01 99 93 F6 EE 06 00 50 01 99 93 F8 E2 03 FF WWN7 Range 50 01 99 93 F8 E2 04 00 50 01 99 93 FA D6 02 FF WWN8 Range 50 01 99 93 FA D6 02 00 50 01 99 93 FC CA 00 00 no gui Run installation in console mode non gui installation license key The license key for the Virtual IO Manager check prerequisites Only check prerequisites and exit Jang VIOM installation language Possible values en English ServerView Virtual lO Manager 87 3 4 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 1 dbport 9212 mac range 00 19 99 3E D2 A1 00
251. profiles of type Rack Server If you specify more than one tagged VLAN for a port the names must be separated by commas If you use the network selection box the name of the chosen net work is added to the Tagged VLAN column if you use the Add tagged button ServerView Virtual lO Manager 193 5 Virtual lO Manager user interface Names of the service networks You can specify service net works for each LAN or CNA port but not for profiles of type Rack Server If you specify more than one service network for a port the names must be separated by commas If you use the network selection box the name of the chosen net work is replaced in the Network column or added to the Service column depending on the type of the selected network To configure the port as the boot device select PXE boot iSCSI boot or SAN boot from the selection list If you select disabled this port is not a boot device You can define up to four boot devices in a profile The values available in the selection list depends on type of port or function If you configure an iSCSI boot device or SAN boot device you must specify additional boot settings in the Boot Parameter step 5 4 3 4 Boot Parameter step Create Server Profile wizard Boot Parameter is the next step in the Create Server Profile wizard In this step you specify the boot device and boot parameter order This step is only shown if you configured a iSCSI boot or SAN boot or at least two
252. r OnBoard 1 or 2 for mezzanine cards and 1 to 14 for PCI cards lOPortN umber Number of the port counts upwards from 1 lOFunctionNumber Number of the physical function of a CNA port If this IOC hannel element do not specify a physical function the value must be 1 lOChannelUsage Indicates whether the port can be used Yes The IO channel is enabled No The IO channel is disabled 320 ServerView Virtual IO Manager 12 3 Format of export files Networks Defines the networks used by this IO channel This element contains an optional NetworkName element optionally followed by one or more ServiceName elements and then optionally by one or more Tag gedName elements NetworkName Optional must not be specified for FC ports or for PRIMERGY rack server profiles Network name If you want to use the profile on blade servers with IBP modules you can specify a network If you work with blade servers that have non VIOM capable LAN modules Open Fabric mode do not specify a network as it is not possible to define net works on these modules ServiceName Optional must not be specified for FC ports or for PRIMERGY rack server profiles Service network name TaggedName Optional must not be specified for FC ports or for PRIMERGY rack server profiles Tagged VLAN network name D The NetworkName ServiceName and TaggedName ele ia ments must be the same for all physical functions of a CNA port AddressVirtualiza
253. rView Virtual IO Manager Setup fo Fujitsu ServerView FUJITSU Virtual 1O Manager has been successfully installed Click Finish button to exit this installation C See installation log See release notes g w z w O a Finish 14 Click Finish to end the installation Installing the Virtual lO 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 lO Manager using a graphical interface on page 74 Simply use the no gui switch and enter suitable parameters The following syntax is supported sh install viom sh dbhost lt ip address hostname gt dbport lt port number gt dbuser lt username gt dbpasswd lt password gt mac range lt first mac addr gt lt last mac addr gt MAC lt x gt MAC lt xy gt wwn range lt first wwn addr gt lt last wwn addr gt WWN lt x gt no gui license key lt key string gt 84 ServerView Virtual lO Manager 3 4 Installing the Virtual lO Manager on a Linux based CMS check prerequisites lang en ja u upgrade q quiet f force i installdir v verbose h help Command line parameters for installation dbhost IP address or hostname of the database server dbport Port num
254. ral buttons This section describes the general buttons that you will come across in the Virtual lIO Manager Buttons in the area on the left Server List button Click Server List in the left area of the Virtual lO 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 lO Manager to switch to the profile view of the defined server profiles Button in the area on the right ot Click this button to refresh the display on the tab General buttons in other dialog boxes Back button Click Back to return to the previous step of the relevant wizard Cancel button Click Cancel to close a wizard dialog box without saving your changes Finish button Click Finish to confirm your entries and exit the relevant wizard This button is only active if all the required entries have been made ServerView Virtual lO Manager 251 5 8 5 Virtual lO Manager user interface Help button Click Help to launch the context sensitive online help Next button Click Next to go to the next step of the relevant wizard OK button Click OK to confirm your entries The dialog box closes Icons This section contains a list of the VIOM specific icons and their meaning These icons are displayed on the Setup tab when you click a module in the display con Significance i The module cannot be managed ry The module has minor configuration p
255. ration of VMware Infrastructure 3 52 ServerView Virtual lO 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 HA functionality supported by Virtual lIO Manager HA functionality is supported by Virtual IO Manager by the following meas ures e The central ServerView Virtual IO Manager service is configured to be restarted automatically in the event of failure This automatic restart of the service is configured during installation of Virtual lO manager By default the following restart behavior is configured o The first restart of the service is tried 5 seconds after unexpected ter mination of the service o The second restart is tried 30 seconds after termination of the serv ice o Subsequent restarts are tried 60 seconds after termination of the service o The restart counter is reset after 600 seconds ServerView Virtual lO Manager 53 2 Virtual lIO Manager Introduction D The details of this configuration cannot be seen via the nor i mal graphical user interface of the service manager To see the detai
256. rd and for onboard Edit Server Profile profile2 Name y j Onboard Card Type OLan Ocna 10 Channels 2 Mezzanine card slot 1 Card Type OLN OFC cna 10 Channels 2 lezzanine card slot 2 Card Type Oun FE Ocna 10 Channels 2 Previous Next _ Finish Cancel Help Figure 51 Configure Card step In the Onboard box you can specify the type and number of onboard ports to be supported with this server profile If you selected a server blade model under Preset values to use for server type in the Name step the number and type of ports is initialized according to the model You can adjust the number for the server profile However you cannot exceed the maximum pos sible value for the selected server model ServerView Virtual lO Manager 207 5 4 4 3 5 Virtual lO 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 This card can have up to two ports With lO Channels you specify the number of ports for the card to be sup ported with this server prof
257. rea 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 Includes the servers that are managed using VIOM This server group contains the servers that were selected in the VIOM Manageable group for which the Manage action was successfully carried out The servers managed by VIOM are then no longer listed in the VIOM Manageable group 5 2 2 Tree structure Profiles eroties SSS DO Sis double profilei profile2 Figure 24 Profiles tree structure When you select Profiles on the left of the work area the defined server pro files are displayed The folder is empty as long as a server profile has not yet been created ServerView Virtual lO Manager 141 5 Virtual lO Manager user interface e Select a folder to show all contained profiles in the profiles table in the Server Profiles view in the area on the right of the ServerView Virtual IO Manager window By using the context menu in the area on the left you can create a new profile e 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 3 Tabs If Server List is activated in the tre
258. rent uan NET 3 transparent NET 4 transparent V NETL VNET_2 Firmware Vers 6 12 Manage State managed Fault State ok State Cause profile assigned V_NET_3 Restore IBP x VINET 4 V_NET_S 3x900 2 Connection Bay 1 BX900 2 501 ms mis Copy Configurations Lokales Intranet 100 gt Figure 27 Graphic tab on the Ext LAN Connections tab New Click New to define a new uplink set The Create network wizard is launched ServerView Virtual lO Manager 149 5 Virtual lO 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 lt name of uplink set gt window opens For more information on this see chapter Defining network paths LAN on page 277 5 3 3 2 Details tab on Ext LAN Connections tab The Details tab contains a table with the existing definitions Using this tab you can also define new network definitions or modify and delete existing ones Virtual IO Manager tx200s3 sw5 Windows Internet Explorer S ServerView User administrator SererBrowser Serer Configuration VirtualO Manager Users Passwords National Settings Base Confiquration Wizard Home gt gt Virtual IO Manager BX900 2 9 Al Server VIOM Mana
259. resses If you have an address range of your own that you wish to use for virtual MAC addresses then select it in the Custom MAC Address Range drop down menu In this case the fields in Custom MAC Address Range Parameters in which you can enter the start and end MAC address of the address range become active ServerView Virtual lO Manager 63 3 Installation and uninstallation D The validity of the MAC address input is not checked Please confirm that your input address is valid before you click Next D If you have several installations of the Virtual lO Manager in your LAN network then you must ensure that the address ranges used do not overlap Otherwise addresses may be assigned several times D To change the range of the address after installation is finished you must uninstall the Virtual IO Manager and install it again Therefore if it is possible that addresses may have to be added after the Virtual lO Manager is set up we recommend that you install it without selecting the address range You should input a virtual address when creating the server profile 11 Click Next ie Fujitsu Server iew irtual IO Manager Setup Installation Configuration Please select one of the listed address ranges for virtual WANN and FU l I SU VWYPN addresses or define your own custom address range WWH Address Range Property Description WAN Address Range 1 WAN Address Range 2 WAN Address Range 3 WAN Address Range 4 WAN Address
260. rly backed up The ServerView database is backed up independently of the VIOM database e For backing up the VIOM database you can use the VIOM Backup Serv ice which is described in this chapter see section VIOM Backup Serv ice on page 338 e For the ServerView database there is a separate backup concept which is described in Installing ServerView Operations Manager Software under Windows Installation Guide and Installing ServerView Oper ations Manager Software under Linux Installation Guide On Windows In addition to the database backups transaction logs are creat ed for both the ServerView database and the VIOM database In the event of a problem the database can be restored using the most recent backups of the ServerView and VIOM databases and their respective transaction logs D Note that under Linux and PostgreSQL no transaction logs are 7 saved only full backups e For how to restore the VIOM database on Windows using the backups and transaction logs see section Restoring the VIOM database on Win dows on page 345 e For how to restore the VIOM database on Linux using the backups see section Restoring the VIOM database on Windows on page 345 e For how to restore the ServerView database see Installing ServerView Operations Manager Software under Windows Installation Guide and ServerView Virtual lO Manager 337 14 1 14 VIOM database Installing ServerView Operations Manager Software under Li
261. rning that the previous configuration will be deleted if you move the server The warn ing also informs you that before deactivating management with VIOM you should remove all the LAN cables except the one connected to the first uplink port If you click Yes the previous configuration with VIOM is deleted and the blade server is added to the VIOM Manageable server group If you click No you close the window without moving the server D For PRIMERGY rack servers If you are only unmanaging i PRIMERGY rack servers a simple confirmation message is shown For more information on the internal operations for deactivating management with VIOM see section VIOM internal operations on blade servers on page 261 VIOM internal operations on blade servers This section contains a list of internal operations that are executed when you activate or deactivate management with VIOM for a blade server VIOM internal operations during activation When you activate management with the Virtual lO Manager for a blade server chassis the following actions are executed internally ServerView Virtual lO Manager 261 7 Managing servers with VIOM 1 The chassis is indicated as managed This happens on the one hand in the VIOM database However information is also defined in the man agement blade of the chassis that this chassis is managed by this instal lation of the Virtual lO Manager D This information in the management blade is always che
262. roblems amp The module has major configuration problems Table 4 Icons on the Setup tab 252 ServerView Virtual IO Manager 6 1 6 2 Using the Virtual lIO Manager Starting the Virtual lO Manager You can start the Virtual lIO Manager from the main window of the Server View 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 lO Manager on the start page of the Operations Manager by choosing Administration Virtual lO Manager On Windows you can also launch VIOM from the Windows Start Menu 1 Choose Start ALL Programs Fujitsu ServerView Suite Vir tual IO Manager Virtual lO Manager In both cases the login page of the Fujitsu ServerView Suite Central Authen tication Service is displayed Here you enter a valid user name and pass word of a user with AccessVIOM privilege By default this is a user with Administrator role The start page of the Virtual lIO Manager is then displayed Closing Virtual lO Manager You can close the Virtual lIO Manager by closing the main window 1 To close the Virtual lIO Manager main window click on the Close icon in the browser window ServerView Virtual lO Manager 253 6 Using the Virtual IO Manager 6 3 Logging the actions using VIOM 6 3 1 Logging the actions on Windows The Virtual lO Manager l
263. rofiles To export server profiles proceed as follows 1 Inthe left section of the ServerView Virtual lO Manager window switch to the Server Profiles view If applicable click Profiles 2 Select the required profiles 3 Then click the Export button A file selection box opens in which you select the name of the file to which you want to save the exported profiles 12 2 Importing server profiles To import server profiles proceed as follows 1 Inthe left section of the ServerView Virtual lO Manager window switch to the Server Profiles view If applicable click Profiles 2 Then click the Import button A file selection box opens 3 Inthe file selection box select the file that you want to import ServerView Virtual lO Manager 313 12 3 12 3 1 12 Importing and exporting server profiles 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 lt xml version 1 0 encoding UTF 8 gt lt Objects xmlns http schemas fujitsu com serverview viom objects xmlns xsi http www w3 org 2001 XMLSchema instance schemaVersion V3 1 gt lt Objects gt The Objects element The Objects element is the root element of the XML file and must have the following attributes xmins http schemas fujitsu com serverview viom objects e xmins xsi http Awww w3 org 2001 XMLSchema instance schemaVersion V
264. rowse button appears Click this button to opena 242 ServerView Virtual lIO Manager 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 In this dialog box you can specify addi tional parameters to restore server profiles Restore Options Restore profiles C Keep existing profiles On Existing Profiles C Assign new virtual addresses C Restore Address Ranges Figure 72 Restore Options dialog box server profiles ServerView Virtual lO Manager 243 5 Virtual lO Manager user interface Restore only reassigned profiles Specifies that only the profiles that are reassigned to the selected blade servers will be restored see section Restoring blade server con figurations on page 306 If you do not select this option all the profiles saved in the backup file will be restored Keep existing profiles Specifies that the existing profiles remain the same This option is select ed automatically if you select the Restore only reassigned profiles option If you do not select this option all existing profiles are deleted before the co
265. rt for INTEL Eth Ctrl 4x1Gb Cu PCle x4 D3045 INTEL Eth Ctrl 2x1Gb Cu PCle x4 D3035 and INTEL 10GbE 10GBase T RJ45 PCle LAN in PRIMERGY rack servers e Support of VLAN groups in tagged mode in VIOM server profile see Defining networks LAN for blade servers only on page 30 O Chan nels step Create Server Profile wizard on page 190 and O Channels step Edit Server Profile wizard on page 208 e DCB settings also possible for iSCSI see CNA Parameter step Create Server Profile wizard on page 200 and CNA Parameter step Edit Server Profile wizard on page 218 e Video Redirection for server blades and rack servers see Server Con figuration tab on page 151 e User specific display properties are stored session independent see Preferences dialog box on page 238 e Support of JAVA Runtime Environment 7 only with ServerView Oper ation Manager 6 10 e The section High Availability HA has been updated and now includes VMware HA see High Availability HA support on page 48 ServerView Suite link collection Via the link collection Fujitsu Technology Solutions provides you with numer ous downloads and further information on the ServerView Suite and PRIM ERGY servers ServerView Virtual lO Manager 21 1 Introduction For ServerView Suite links are offered on the following topics e Forum e Service Desk e Manuals e Product information e Security information e Software downloads e Tra
266. rtualization data as well as the VIOM specific inventory data When AC power returns and the iIRMC has booted again it still has the following information 1 This PRIMERGY rack server is managed by VIOM 2 The VIOM enabled flag is set 3 The unique identification of the VIOM installation 4 The SNMP trap destination as specified by VIOM when managing the server 5 Whether VIOM virtualization data was stored in the iRMC before power loss or not If VIOM virtualization data was stored in the IRMC before power loss and because the iIRMC knows that the server was managed by VIOM and that vir tualization data was assigned a special communication process with the VIOM management station will start when the iRMC is booted again after power has returned This communication is based on sending SNMP traps to the VIOM management station and setting specific status information in the iRMC For this process to work the VIOM management station must be run ning and must be accessible to the IRMC As long as the iRMC did not receive virtualization data from the VIOM man agement station it will periodically send SNMP traps to the management ServerView Virtual lO Manager 269 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 iIRMC user interface or BIOS interface At the end of this process the VIOM inventory data is freshly recr
267. rver e Delete server profile assignments e Define anew server profile directly from here e Define spare slots on blade servers e Move a server profile from one slot to a suitable spare slot start a server profile failover only for blade server e Switch server blades or PRIMERGY rack servers on and off For more information on this see chapter Defining and assigning server pro files on page 289 ServerView Virtual lO Manager 151 5 Virtual lO Manager user interface Virtual lO Manager t lt 200s3 sw5 Windows Internet Explorer DER S ServerView User administrator Logoi Fujitsu ServerList E Asset Management Deployment Event Management Monitoring Update Management Security ServerBrowser Server Configuration Virtual IO Manager Users Passwords National Settings Base Configuration Wizard Home gt gt Virtual 10 Manager BX900 1 E Al Server VIOM Manageable SNe eel ee reed Server Configuration PETE a Bx400 vIoML VIOM Status Managed by VIOM OK e Bx600 3 DA ooz Housing Name Bx900 1 Sj ex900 5 Model Type Bx90051 Bx900_4 IP Address of MMB 172 17 51 231 P Rx30057 VIOM4 MMB Firmware 5 02 amp Tx30057 V1OM3 VIOM Managed Bap ex200 1 RX20057 VIOM4 no spares Name Y Location Y Slot BX900 1 F02 BX900 1 empty unassigned Power off BX900 1 F03 Bx900 1 Bx92051 Boot normal unassigned VIOM setting OK Power off BX900 1 F04 Bx900 1 Bx920 S1 Boot normal unass
268. s 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 To make it easier for you in the MMB area there is a checkbox called Use for all components which when checked sets the values for all IBPs to the ones specified for the MMB So if the user name and password are the same for all components this should be the standard you only need to specify them once 232 ServerView Virtual lO Manager 5 5 Dialog boxes For security reasons you should change the default user name and password combination You can have the same user name and password for all com ponents or different ones for each You must specify this accordingly in this dialog box 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 con figuration User name A valid user name with access rights to the MMB or IBP Password Password of the user ID Use for all components Sets the values for all IBPs to the ones specified for the MMB Configure protocols Expands the dialog box so that you can also specifiy the protocol and the port to be used by VIOM to access the components These values should not be changed in
269. s moved to a different location that is not controlled by the VIOM management station that originally con trolled it this PRIMERGY rack server cannot boot because it waits end lessly for the virtualization data It is best to unmanage the PRIMERGY rack server in VIOM before moving it to the new location If this is no longer possible the VIOM managed status can be deactivated in the iIRMC user interface and the system BIOS 270 ServerView Virtual lO Manager 7 5 VIOM internal operations on a PRIMERGY rack server S ServerView System Overview E System Information i Bios E iRMc 53 Power LED Power On E Power Management Error LED ot E Power Consumption css Len or E Sensors it or u E Event Log asda id isa Server Management E Network Settings E Alerting E User Management Virtual IO Manager Identification 971 af8b0 4051 4bde bb 5 101827256e04 111 22 11 14 E Console Redirection Video Redirection JWS Disable VIOM Remote Storage Text Console SOL iRMC S3 SSH Access iRMC 3 Telnet Access System Asset Tag Apply Refresh System Type PRIMERGY RX300 S7 Chassis Type RX300S7R1 Serial YLAR000028 BIOS Version V4 6 5 1 R1 0 8 for D2939 A1x System GUID 03000200 0400 0500 0008 000700080009 System Name RX300S7 VIOMS 2009 2012 Fujitsu Technology Solutions All rights reserved 18 Feb 2012 16 08 55 ol a redctes Protected nodes of tome gt To deactivate the server s
270. s to guide you through the individual steps All required steps are displayed in the tree struc ture on the left You modify an defined uplink using the Ext LAN Connections tab This tab contains two other tabs Graphic and Details To open the Edit Uplink Set wizard click Edit on the Graphic or Details tab Edit Properties step Edit Uplink Set wizard single VLAN network Edit Properties is the first step in the Edit Uplink Set wizard The type of the network determines which fields are displayed in this step 176 ServerView Virtual lO Manager 5 4 Wizards Edit Properties step for single networks VLAN networks Edit Uplink Set NET_1 DCB Properties Name of uplink set INET 1 Add Networks Activate Port Backup Link Speed Auto negotiation Linkdown propagation C Enable LACP IGMP Snooping O Isolate mode Ports For this uplink set change with right click BX900 1 Connection Bay 3 BX900 1 503 io Be Gy 2 E 20 KI 22 Uplink set contains 2 ports 0 backup f Finish Cancel Help Figure 38 Edit Uplink Set wizard first step You can modify following parameters in the first step of the wizard Activate Port Backup Switch to a backup port if an error occurs in the active port The port backup function is only available if at least one backup port is con figured Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail The linkdown event triggers a fa
271. se Manager ol License string __ Version bound Duration days 14 Assign count Register new license 4T3P MHQG A4GY 5NBP FNC3 OXSY JUAY v2 all 1 Total assign limit 18 Assigned profiles 0 Assign credits 18 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 D On Linux you can also add a licence without graphical user inter face cd opt fujitsu ServerViewSuite plugins viom Manager java jar VIOM LICENSE MANAGER jar remove lt key gt In addition to using the License Manager to manage licenses you can dis play the licenses assigned in the Virtual lO Manager interface To do this you must click the Show Licenses button on the Virtual lO Manager tab You use the Show Licenses button on the Virtual lO Manager tab to request information on the licenses assigned 1 Todo this click the Show Licenses button on the Virtual l O Manager tab 2 The Licenses Information dialog box opens Licenses Information License Version Bound Assign Count T Duration Days 4T3P MHQG A4GY SNBP FNC3 OxSY JUAY all 18 14 Assign Limit 18 Used Assigns 0 Assign Credit 18 ServerView Virtual lO Manager 93 3 Installation and uninstallation 3 The information displayed includes the following e License code
272. server profile It cannot be specified within the network settings The advantage of the tagged mode is that the same VLAN networks can be used either untagged for separate server blades on different downlinks or tagged for one server blade with separate virtual machines on one downlink ServerView Virtual lO Manager 39 2 Virtual lIO Manager Introduction Dedicated service networks untagged Server Blade 1 tagged 4094 tagged 10 tagged 20 untagged Server Blade 2 tagged 4094 untagged Dedicated Service LAN untagged Server Blade 3 tagged 20 tagged 30 untagged Server Blade 4 Blade chassis Figure 8 Dedicated service networks The dedicated service network is designed to separate LAN traffic of an iRMC from the operating system LAN traffic if the IRMC is not using a sep arate management LAN but is configured to share its LAN traffic with an onboard LAN port of the server blade In order to separate the LAN traffic of iIRMC and operating system in this case the IRMC must also be configured to use a VLAN tag for its LAN packets A dedicated service network defined with the same VLAN ID as used by the iRMC allows the tagged iIRMC LAN packets to be routed to specific uplink port s external port s whereas the other LAN packets from the operating system are routed to a separate uplink port In addition the dedicated service network can also be used to route the LAN packag
273. signed to the uplink set 162 ServerView Virtual lO Manager 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 In the first step you specify what type of uplink set or what network you wish to create Create Network for IBP BX900 2 SO02 Select the type of the shared uplink set network to create Creates a network without uplink ports Single network Creates an uplink set with a single network The uplink set and the network will get the same name The network forwards all tagged and untagged traffic YLAN Service VLAN networks Creates an shared uplink set with a number of VLAN and or Service VLAN networks The VLAN tags are removed at the downlink ports Dedicated service network Creates a dedicated service network Figure 32 Create Network wizard first step Internal network Creates an internal network without a connection to an uplink port This establishes a connection between the server blades internal IBP con nections without there being a connection to
274. ss ranges used do not overlap Otherwise addresses may be assigned several times q Tochange the range of the address after installation is finished 7 you must uninstall the Virtual lO Manager and install it again Therefore if it is possible that addresses may have to be added after the Virtual lIO Manager is set up we recommend that you install it without selecting the address range You should input a virtual address when creating the server profile ServerView Virtual lO Manager 65 3 Installation and uninstallation 12 Click Next E Fujitsu Server iew irtual IO Manager Setup Ready to Install the Application Click Next to begin installation 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 66 ServerView Virtual lO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS 13 Click Next The installation of the Virtual lO Manager is started The fol lowing window is then displayed ie Fujitsu Server iew Yirtual IO Manager Setup fet Ea Fujitsu ServerView Virtual lO FUJITSU Manager has been successfully installed Please click the Next button to start the License Manager before finishing the installation After entering a valid license and closing the License Manager window the installation finishes Without entering a valid license ServerView Virtual lO Manager will not fu
275. ssigns 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 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 Virtual IO Manager tab Inthe Preferences dialog box are two tabs to set user preferences e Display tab e Trace tab 238 ServerView Virtual lO Manager 5 5 Dialog boxes Display tab Preferences iz Some settings of display properties are stored user specific on the computer where the VIOM user interface is executed You can reset these settings to factory defaults by selecting the checkbox below C Reset display settings 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 ServerView Virtual lO Manager 239 5 Virtual lO Manager user interface Trace tab Preferences Display Write trace messages to file File name ew Suite plugins viom Manager logs quitrace txt Max file size T MB Trace level fine Figure 70 Trace tab Preferences dialog box On the Trace tab parameters for tracing th
276. such as Activate Port Backup Switch to a backup port if an error occurs in the active port 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 7 Click Next to confirm your entries The last step of the Create network wizard opens In this step you assign meaningful names for the net ServerView Virtual lO Manager 283 8 Defining network paths LAN 10 11 12 13 14 15 16 works defined via VLAN IDs which are to be assigned to the uplink set defined in the previous step 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 con trast however two networks on two different uplink sets can use the same VLAN ID These networks are still completely separate from one another Optional e Specificy a native VLAN network All packages that do not contain a VLAN ID will be allowed through this connection e Select a network as service VLAN Click Add the virtual LAN network is added to the table below Define any other required networks that are to use the port group and confirm each of these with Add You can also define a network as a native VLAN in the table ret rospectively To do this select the checkbox in the
277. t WOK oath Ueto wae D aae Er A RM eh Eh ih SAE hue ae ONO CR 185 5 4 3 Create Server Profile wizard 2 2 2222222 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 1O Channels step Create Server Profile wizard 190 5 4 3 4 Boot Parameter step Create Server Profile wizard 194 5 4 3 5 CNA Parameter step Create Server Profile wizard 200 5 4 3 6 Virtual Addresses step Create Server Profile wizard 202 5 4 3 7 Confirm step Create Server Profile wizard 204 5 4 4 Edit Server Profile wizard 222220 22222222 205 5 4 4 1 Name step Edit Server Profile wizard 205 5 4 4 2 Configure Cards step Edit Server Profile wizard 207 5 4 4 3 1 O Channels step Edit Server Profile wizard 208 5 4 4 4 Boot Parameter step Edit Server Profile wizard 212 5 4 4 5 CNA Parameter step Edit Server Profile wizard 218 5 4 4 6 Virtual Addresses step Edit Server Profile wizard 220 5 4 4 7 Confirm step Edit Server Profile wizard 222 5 4 5 Save Configuration wizard 22 eee eee 223 5 4 5 1 Select Action step Configuration Backup Restore wiz ONG oct ee ee Se a here MS ae eet cd 223 5 4 5 2 Select File step Save Configuration Wizard 224 5 4 5 3 Select File step Restore Configura
278. t is not yet assigned to the uplink set Assigns the port to the uplink set If the port is already assigned to another uplink set this assignment is deleted Add as Backup Only activated if the port is not yet assigned to the uplink set 182 ServerView Virtual lO Manager 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 The corresponding port is configured as a backup port and no longer as active port Ports configured as active or backup ports are indicated by different col ors in the display light red light green or dark red dark green The name of the uplink set is assigned to configured ports which you can rec ognize by this 5 4 2 3 DCB Properties Edit Uplink Set wizard single VLAN network DCB Properties is the second step in the Edit Uplink Set wizard if a single network or a VLAN network is edited D It is only displayed if the connection blade supports DCB Data Center Bridging i e for PY CB Eth Switch IBP 10 Gb 18 8 con nection blades ServerView Virtual lO Manager 183 5 Virtual lO Manager user int
279. t menu D You can update the display in the State column by clicking z Update States button or with Update State in the context menu 6 Click Unassign Profile or select Unassign Profile in the context menu of the required slot The assignment is deleted and no server profile is assigned to the cor responding slot or PRIMERGY rack server The display on the Server Con figuration tab is updated accordingly ServerView Virtual lO Manager 299 300 ServerView Virtual lO Manager 10 Viewing the blade server con figuration You view the blade server configuration via the Chassis configuration tab 1 Click the Chassis configuration tab The Chassis configuration tab contains a schematic display of the existing configuration of the blade server 2 Click the Update States button to update the display of the on off status of the server blades in the rectangle of the slots 3 Click an uplink port a network or a bay to select it The elements asso ciated with the element you have selected are then highlighted ServerView Virtual lO Manager 301 302 ServerView Virtual lO Manager 11 11 1 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
280. tab you find the Copy Configuration button for copying all net works of achassis For more information see section Copying con figuration on page 288 Graphic tab on Ext LAN Connections tab The Graphic tab contains a schematic display of the I O connection blades and ports Using this tab you can create new network definitions edit or 148 ServerView Virtual lO Manager 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 sche matic view of the uplink ports of the selected IBP If the selected IBP belongs to a switch stack all members of this stack are highlighted by coloring them yellow for the stack master green for other stack members In the port area the uplink ports of all stack members are displayed Virtual I0 Manager tx200s3 sw5 Windows Internet Explorer DOR S ServerView User administrator Logout Fujitsu Home gt gt Virtual 10 Manager EEN ES Ext LAN Connections Graphic ETE Connection Bay 1 BX900 21S01 Y Network TVND Product Name PY CB Eth Switch IBP 1Gb ram treneperent 900 36 12 Mode 1BP a m VIOM Managed ip ackress etre NET_2 transpa
281. te Manager of the man agement blade To do this choose 1 Management Agent 2 Man agement Blade The Management Blade Firmware Version parameter displays the installed firmware version You can also check the version via the Web interface If your firmware version is lower than the version required you must update it to the required firmware version before you activate VIOM man agement for the blade server You can run an update via the Remote Manager of the management blade Fora MMB S3 choose 4 TFTP update 6 Management Blade Update Enable After selecting 5 TFTP Update in 4 Management Blade Image File Name you first specify the name of the firmware file with the new firm ware version e You must configure the management blade and connect it to the local net work so that it can be accessed from the central management station on which the ServerView Operations Manager and VIOM are installed e Access to the management blade via Telnet or SSH is essential for VIOM You must configure the management blade via its Web interface To do this choose Chassis Settings Network Interface Telnet or Chassis Settings Network Interface SSH e Ensure that the Automatic Inventory Retrieval parameter is set to automatic Then the management blade automatically generates the inventory information required by VIOM when the server blade is insert ed VlOM needs this inventory information specifically for the
282. ted 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 ServerView Virtual lO Manager 179 5 Virtual lO Manager user interface The corresponding port is configured as a backup port and no longer as active port Ports configured as active or backup ports are indicated by different col ors in the display light red light green or dark red dark green The name of the uplink set is assigned to configured ports which you can rec ognize by this 5 4 2 2 Edit Properties step Edit Uplink Set wizard dedicated service net work Edit Properties is the first step in the Edit Uplink Set wizard The type of the network determines which fields are displayed in this step Edit Properties step for dedicated service networks Edit Uplink Set SNET DCB Properties Name of uplink set Add Networks Activate Port Backup Link Speed Auto negotiation Linkdown propagation Service VLAN ID 1234 L C Enable Lace IGMP Snooping C Isolate mode Ports For this uplink set change with right click Bx900 1 Connection Bay 3 BX900 14503 E 0 2 EJ 20 K 22 Uplink set contains 1 ports 0 backup Figure 39 Edit Uplink Set wizard first step You can modify following parame
283. ters in the first step of the wizard 180 ServerView Virtual IO Manager 5 4 Wizards Activate Port Backup Switch to a backup port if an error occurs in the active port The port backup function is only available if at least one backup port is con figured Linkdown propagation Send a linkdown event if both the active ports and the backup ports fail The linkdown event triggers a failover process on the server blade if con figured accordingly 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 link down 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 con nection to remain intact In order for the failover process in the server blade to work from LAN port 1 to LAN port 2 aLAN team must have been configured on the server blade and the network on the second IBP module must have been con figured accordingly Enable LACP You activate the LACP protocol via Enable LACP Isolate mode You activate the isolate mode via Isolate mode With isolate mode acti vated server blades in the same chassis that use the same network can not communicate with each other but only with an external device though the uplinks This
284. tes an uplink set with a network The uplink set and the network have the same name To find out what other entries you need to make during the further course of the wizard see section Defining a single network on page 280 VLAN Service VLAN networks Creates an uplink set to which one network or even multiple net works with a VLAN ID can be assigned To find out what other entries you need to make during the further course of the wizard see section Defining VLAN networks on page 282 Dedicated Service network Creates an uplink set with one dedicated service network To find ServerView Virtual lO Manager 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 Defining an internal network If server blades only need to communicate with each other and for security reasons there must be no connection to an external network then you con figure an internal network without a connection to an uplink In this case we are dealing with internal IBP connections When defining the server profiles and assigning these profiles to the server blade slots you specify which server blades are to be connected via which LAN ports via an internal network see chapter Defining and assigning server profiles on page 289 To define an internal network foll
285. the list of SNMP trap destinations and delete all unrequired entries To do this open the view Alerting SNMP Traps in the iRMC user interface ServerView Virtual lO Manager 273 7 Managing servers with VIOM S ServerView E seer a Server View Remote Management iRMC 3 Web Server M Deutsch Ha SNMP Trap Alerting SNMP Trap Destination SNMP Community fpublio Apply Trap Destination IP Address or DNS Name Server Management E Network Settings SNMP Server 1 111 22 11 11 Apply Test E Alerting Ti SNMP Traps SNMP Server 2 0 0 0 0 Apply i Brall SNMP Server 3 0 0 0 0 Apply Test E User Management i Console Redirection SNMP Server 4 0 0 0 0 Apply Test Wideo Redirection JWS Remote Storage SNMP Server 5 0 0 0 0 Apply Test Text Console SOL iRMC 3 SSH Access SNMP Server 6 0 0 0 0 Apply Test iRMC S3 Telnet Access SNMP Server 7 0 0 0 0 Apply Test Refresh Apply All VIOM internal operations during deactivation When you deactivate management with the Virtual lO Manager for a PRIM ERGY rack server the following actions occur internally 1 VIOM checks that the server is powered off by reading the power state reported by the iIRMC 2 IfaVIOM server profile is assigned to this server the server profile is internally unassigned and the VIOM virtualization data is deleted in the iIRMC 3 The iRMC property that holds the information about the VIOM man agement station is cleared 4 The VIO
286. the Virtual lO Manager tab Upgrading or moving the SQL Server database The ServerView Operations Manager manual Installation under Windows explains what you must be aware of when updating your SQL Server data base on the central management station CMS or on a remote node The following is based on that information In chapter Upgrade installations of SQL Server two major cases are distinguished e Upgrading an SQL Server instance while keeping the instance name e Moving an SQL Server instance to an instance with a different name In the former case there there is one thing to add if the Virtual IO Manager is running on the central management station Just make sure that both the Vir tual IO Manager and the Backup Service are stopped before you start upgrad ing the SQL Server In the latter case you must perform two additional steps while the VIOM serv ices are stopped e When you have created the ServerViewDB database in the new instance execute a similar command sequence for ViomDB CREATE DATABASE ViomDB ON PRIMARY FILENAME lt data_path gt ViomDB mdf ServerView Virtual lO Manager 95 3 9 3 9 1 3 9 2 3 Installation and uninstallation LOG ON FILENAME lt data_path gt ViomDB_log LDF FOR ATTACH DBCC UPDATEUSAGE ViomDB e Inthe installation directory of the Virtual lIO Manager you will find a Java properties file called ViomConfig properties Ch
287. the command line OELE O e E E ee tte wig Oh ok is Sete Jes ee A 68 3 3 Updating the Virtual lIO Manager on a Windows based CMS 72 3 4 Installing the Virtual lO Manager on a Linux based CMS 73 3 4 1 Installing the Virtual IO Manager using a graphical interface 74 3 4 2 Installing the Virtual IO Manager using the command line 84 3 4 3 Important directories of Virtual lO Manager 88 3 4 4 Collecting diagnostic information 2 222eeeeee 89 ServerView Virtual lO Manager 3 Contents 3 5 Updating the Virtual lIO Manager on a Linux based CMS 89 3 6 License management 0 2 e cece ee eeeeeeeee 90 3 7 Updating ServerView Operations Manager 94 3 8 Upgrading or moving the SQL Server database 95 3 9 Uninstalling the Virtual lO Manager 2220000 220 0 96 3 9 1 Uninstalling the Virtual lO Manager on a Windows based CMS 52 oe atone scenes sata eh tena ok tc sa a es ace batss 96 3 9 2 Uninstalling the Virtual lO Manager on a Linux based CMS 96 4 Configuration 2 2 2 2 eee cece e cece cece cece cece ee eees 97 4 1 Configurations on the managed BX600 Blade Server 97 4 1 1 Supported hardware configurations for the connection Blades sie saiae Wet one Bait sion eo oen dome Sins cade ae y Mahon 97 4 1 1 1 LAN hardware configuration 22222 2200 98 4 1 1 2 Fibr
288. the left 222222 2222222 251 5 7 2 Button in the area on the right 00 0000000022002 251 5 7 3 General buttons in other dialog boxes 2 22 251 5 8 ICONS cs 252 6 Using the Virtual lO Manager 2222222 253 6 1 Starting the Virtual lO Manager 0 eee cece cece eens 253 6 2 Closing Virtual lO Manager ccee cece ee eeeeeeeeeees 253 6 3 Logging the actions using VIOM 2 22 2 e cess eee 204 6 3 1 Logging the actions on Windows 22 eeeeeeeee 204 6 3 2 Logging the actions on Linux 2 22 eee eee ee ee ee 256 7 Managing servers with VIOM 0 0 2 0 22222 257 7 1 Activating management with VIOM 2222222 257 7 2 Changing access rights and ports 0 0 2222002 259 7 3 Deactivating management with VIOM 222222 261 7 4 VIOM internal operations on blade servers 261 7 5 VIOM internal operations on a PRIMERGY rack server 266 7 6 Displaying license information 00000000 22 cece ee eee eee eee 275 8 Defining network paths LAN 0 0 0 0 00 2222 277 8 1 Defining an uplink Set 2 222222 eee eee cece cece e eee 278 8 1 1 Defining an internal network 00 0 22220 279 8 1 2 Defining a single network 2 00000000002 2ee eee eee 280 8 1 3 Defining
289. the name of the chosen net work is added to the Tagged VLAN column if you use the Add tagged button ServerView Virtual lO Manager 211 5 Virtual lO Manager user interface Names of the service networks You can specify service net works for each LAN or CNA port but not for profiles of type Rack Server If you specify more than one service network for a port the names must be separated by commas If you use the network selection box the name of the chosen net work is replaced in the Network column or added to the Service column depending on the type of the selected network To configure the port as the boot device select PXE boot iSCSI boot or SAN boot from the selection list If you select disabled this port is not a boot device You can define up to four boot devices in a profile The values available in the selection list depends on type of port or function If you configure an iSCSI boot device or SAN boot device you must specify additional boot settings in the Boot Parameter step 5 4 4 4 Boot Parameter step Edit Server Profile wizard Boot Parameter is the next step in the Edit Server Profile wizard In this step you can modify the boot device configuration and the boot parameter order This step is only shown if you configured a iSCSI boot or SAN boot or at least two channels as boot devices in the previous step of the Edit Server Profile wizard If you configured at least two channels as boot devices in th
290. the option of copying the defined uplink sets and networks to a sec ond IBP module This can be useful if you use a teaming configuration for fail ure safety on the server blades If the ports of a server blade that are con nected to the first IBP each form a LAN team with the corresponding ports connected to the second IBP and these ports are connected to the same net works then in the case that the teaming software triggers a failover the LAN connection remains in the same networks If you wish to use the failure safety then the following requirements must be met 1 The uplink sets must be defined with the Linkdown propagation function 2 ALAN team must be configured on the server blade 3 The network on the second IBP module must be configured accordingly The following describes how to create a corresponding IBP configuration by making a copy 1 Activate the Graphic tab on the Ext LAN Connections tab 2 Select the IBP whose configuration should be copied and click Copy 3 Then select the IBP to which to copy and press the Paste button 4 If you confirm the query all definitions of the one IBP module are copied to the other IBP module ServerView Virtual lO Manager 287 8 Defining network paths LAN D e VIOM always copies the entire configuration irrespective of gt what is selected in the tables e lf the target IBP has fewer uplink ports than the source IBP all uplink ports which does not exist on the target
291. ther Virtual lO Manager you receive a corresponding warning If however you are sure that a server is no longer managed by another VIOM installation you can still add the server to the man agement despite the warning VIOM also changes a special VIOM enabled flag in the iIRMC from not enabled to enabled and a trap destination is stored in the iIRMC The trap destination is one of the required details that VIOM needs to manage a PRIMERGY rack server The trap destination must be the IP address or server name of the ServerView management station where this Vir tual lIO Manager and ServerView Operations Manager are installed When you specify a server name the iIRMC must be able to resolve this server name into a valid IP address via DNS so that SNMP traps sent by iIRMC to the IP address reach the VIOM management station 266 ServerView Virtual lO Manager 7 5 VIOM internal operations on a PRIMERGY rack server The iRMC has limited storage to store multiple trap des tinations This configuration can be modified by other programs or by using the iRMC user interface When removing the trap destination of the VIOM management station from the iRMC configuration this might result in incorrect behavior of the server in the case of a power loss event for this server z VIOM also needs a username and password in order to authen ticate on the IRMC when communicating with the iRMC via RMC protocol IPMI over LAN 2 The Virtua
292. ther license see section License management on page 90 ServerView Virtual lO Manager 275 276 ServerView Virtual lO Manager Defining network paths LAN This chapter describes how to define network paths on an IBP module LAN connection blade using VIOM In the Virtual lO 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 fol lowing steps e Defining an uplink set An uplink set contains a number of uplink ports You can combine multiple uplink ports in one uplink set You can con figure the ports as active ports or as backup ports e Possibly also defining one or several meaningful network names which are assigned to the uplink set You can configure the IBP modules individually or for a failover configuration you can generate an identical configuration by copying the definitions of one IBP module to a second module You define network paths using the Ext LAN Connections tab This tab contains two other tabs Graphic and Details On both tabs the New Edit and Delete buttons are available e Click New to define a new uplink set see section Defining an uplink set on page 278 e Click Edit to edit an existing uplink set see section Modifying an uplink set on page 285 e Click Delete to delete networks or uplink sets see section Dele
293. thru module or a PY CB Eth Switch IBP 10 Gb 18 8 SBAX2 connection blade in switch mode the option Enable DCB set tings should not be set Priority Level The priority level Possible values are 0 to 7 for FCoE this is by default the value 3 for iSCSI the default value is 4 5 4 3 6 Virtual Addresses step Create Server Profile wizard Virtual Addresses is the next step in the Create Server Profile wizard In this step you specify the virtual addresses for each port It is only shown if Use virtual addresses is activated in the 1O Channels step of the Create Server Profile wizard 202 ServerView Virtual lO Manager 5 4 Wizards Create Server Profile Onboard 1 irtual MAC assigned GaAlocate Allocate virtual address Onboard 2 irtual MAC No value Ignore range C Allocate virtual address Figure 48 Virtual Addresses step Virtual MAC Virtual WWNN Virtual WWPN Virtual E MAC The virtual address Virtual MAC and E MAC Enode MAC addresses must have the structure XX XX XX XX XX XX while virtual WWN address es must have the structure XX XX XX XX XX XX XX XX Each x represents a hexadecimal character 0 9 a f A F D The Enode MAC address is the MAC address of an FCoE func tion Ignore range If this option is selected it is not checked whether the given virtual address is in the range that was specified when you installed VIOM Allocate virtual address VIOM automat
294. ting net works on page 286 On the Details tab you can edit existing configurations directly using the table see section Modifying an uplink set on page 285 Context menus are also available on the tabs for defining network paths These will be indicated to you at the relevant places ServerView Virtual lO Manager 277 8 1 8 Defining network paths LAN The Chassis Configuration tab provides an overview of the configuration IBP configuration and server profile assignment of a blade server see chap ter Viewing the blade server configuration on page 301 Defining an uplink set To define an uplink set follow the steps below 1 2 278 You can start the Create network wizard by e clicking New on the Graphic or Details tabs on the Ext LAN Con nections tab e selecting New Uplink Set in the context menu of an uplink set The Create network wizard is launched In the first step of the wizard you specify what type of uplink set or what network you wish to create You can choose between e Internal network Creates an internal network without a connection to an uplink port This establishes a connection between the server blades internal IBP connections without there being a connection to an external net work To find out what other entries you need to make during the fur ther course of the wizard see section Defining an internal network on page 279 Single network selected by default Crea
295. ting server profile is replaced if it is not assigned to a slot Otherwise the procedure is the same as above see Refuse ServerView Virtual lO Manager 315 12 Importing and exporting server profiles existingAddressAction Specifies the response if a virtual address is already in use For individ ual server profiles the value in the corresponding ServerProfile element can be overwritten Possible values are Refuse Handled in accordance with the current error behavior See errorAction New A new address is allocated for each affected IO channel NewForAll New addresses are assigned for all IO channels of the profiles It contains a ServerProfile element for each server profile to be imported see below 12 3 3 The ServerProfile element Each ServerProfile element contains the following attributes id Is the server profile ID This value must be unique within the import file It is not written to the VIOM database but it is specified in error mes sages errorAction optional Specifies whether the import will continue if an error occurs If this attrib ute is specified it overwrites the value from the ServerProfiles or Objects element Possible values are Abort The first error aborts the entire import 316 ServerView Virtual lO Manager 12 3 Format of export files Continue Errors are converted into wamings and the import then continues with the next object existingProfileAction optional Specifies the
296. tion Must not exist if the profile does not use any virtual addresses must exist if the profile uses virtual addresses Contains an Address element for each virtual address see The Address element on page 323 ServerView Virtual lO Manager 321 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 ele ment must be specified if BootDeviceUsage has the value Yes see above DCBUsage Indicates whether DCB Data Center Bridging should be used for this port or function It should only be enabled for FCoE functions Yes DCB will be used and the DCBConfiguration element see below must be specified No DCB will not be used and the DCBConfiguration element see below must not be specified DCBConfiguration optional Specifies the DCB configuration for this function This element must be specified if DCBUsage has the value Yes See above 322 ServerView Virtual lO Manager 12 3 Format of export files FunctionConfiguration optional Specifies the configuration for a function see The Func tionConfiguration element on page 329 This element must be s
297. tion definition BX924 S2 Server profiles with I O virtualization and network connection BX924 S3 definition BX960 S1 Server profiles with I O virtualization and network connection definition Table 3 Supported server blades For information on the BIOS and iRMC firmware version see the release notes supplied ServerView Virtual lO Manager 17 1 Introduction D The Virtual IO Manager can only manage BX900 chassis with S1 gt management blades MMB 1 that are assembled with the fol lowing e Infabric 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 e Infabric 2 o LAN connection blades PY CB Eth Switch IBP 1Gb 36 8 2 PY CB Eth Switch IBP 1Gb 36 12 PY CB Eth Switch IBP 1Gb 18 6 or PY CB Eth Switch IBP 10 Gb 18 8 in switch mode or IBP mode or o LAN pass thru connection blades PY CB Eth Pass Thru 10 Gb 18 18 o FC switch blades of the type Brocade 5450 o FC pass thru connection blades PY CB FC Pass Thru 8 Gb 18 18 e Infabric 3 same as fabric 2 e Infabric 4 same as fabric 1 The LAN connection blades in a fabric must run in the same mode However only one connection blade can be inserted in a fabric You must not switch the mode of a LAN connection blad
298. tion wizard 225 5 4 5 4 Select File step Delete Backup Files wizard 227 5 4 5 5 Select Data step Save Configuration wizard 228 5 4 5 6 Select Data step Restore Configuration wizard 229 5 4 5 7 Select Data step Delete Backup Files wizard 230 5 5 Dial0g bOXES s 2 22 25 5 cesc sob Pisin oon nethaadenast pak stone Bahasa 231 5 5 1 Authentication dialog box single blade server 231 5 5 2 Authentication dialog box PRIMERGY rack server 234 5 5 3 Authentication dialog box PRIMERGY rack server and lade Server ic cats te he dct de 2 boned dade ee E EEEa EE 236 5 5 4 Licenses Information dialog box 2222222 237 ServerView Virtual lO Manager Contents 5 5 5 Preferences dialog box 0 cece eee eee eee 238 5 5 6 Restore Options dialog box Servers 241 5 5 7 Restore Options dialog box server profiles 243 5 5 8 Select Profile dialog box 2 222 222 cece cece eee cece ee eee 245 5 6 Context menus 22 22 occ e eee cc cec eee e cece cccceeeeeees 247 5 6 1 Context menus on the Ext LAN Connections tab 247 5 6 2 Context menus in the Server Profiles view 248 5 6 3 Context menu on the Server Configuration tab 249 5 7 General buttons 22 22 2222 2 2 cece ec cece ee ececccceees 251 5 7 1 Buttons in the area on
299. tions Ignore Spare or Skip downlink checks a corresponding warning is issued in another window In this case you must confirm that you still want to assign the server profile to this slot If the server profile is already assigned to another slot a cor responding message appears in another window asking whether you wish to continue with the operation If you confirm this the previous assignment is deleted and the profile is assigned to the new slot If you try to assign a PRIMERGY rack server profile with PCI cards to a blade server slot or a blade server profile to a PRIMERGY rack server a warning is shown If you confirm that you really want to assign the profile only the mezzanine PCI cards in slot 1 and 2 are regarded see VIOM server profile mapping on page 132 Context menus This section contains a list of the various context menus as well as a brief description of the individual menu items Context menus on the Ext LAN Connections tab The Ext LAN Connections tab provides a number of context menus The context menu of an uplink set contains the following menu items ServerView Virtual lO Manager 247 5 6 2 5 Virtual lO 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 Ad
300. to automatic please set it to auto matic and remove and insert all blades or perform a power off and power on of the blade server chassis e Toensure 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 2 3 Configuring the I O connection blades The connection blades in fabric 1 and the optional connection blades in fabric 2 and 3 must be configured and connected to the local network so that they can be accessed from the central management station on which the Server View Operations Manager and VIOM are installed You can configure the network parameters of an I O connection blade using the easy to use Web interface of the management blade Configuration using the Web interface D It is important that the I O connection blades of the BX400 can be is accessed from the management station via their management port You can configure the network parameters of the management port of an I O connection blade using the Web interface of the management blade 114 ServerView Virtual lO Manager 4 2 Configurations on the managed BX400 Blade Server B 400 Remote Management Bx400 10M2 controlled by VOM E BxX400S1 Front View od Controller Time 02 16 2012 15 59 29 amp System Unit Details Uptime 155 day s 02 24 5 Power Consumption Mode Minimum Input Power Consumption Actual f Max
301. to the Ready to Install the Application window in which you start the installation If you selected Select address ranges for IO Virtualization the fol lowing window opens ServerView Virtual lO Manager 3 2 Installing the Virtual lO Manager on a Windows based CMS ie Fujitsu Server iew irtual IO Manager Setup Installation Configuration Please select one of the listed address ranges for virtual MAC FUJITSU addresses or define your own custom address range MAC Address Range Property Description MAC Address Range 6 MAC Address Range 7 MAC Address Range 3 MAC Address Range 1 and 2 MAC Address Range 1 and 2 00 19 99 3E D2 41 00 19 99 3F 11 20 MAC Address Range 3 and 4 MAC Address Range 5 and 6 MAC Address Range 7 and 3 Custom MAC Address Range nl el eo AE Vise Installation Vvizard Back Cancel In this window specify which address range the Virtual IO Manager should use for virtual MAC addresses The virtual MAC addresses are assigned automatically in a profile for the LAN ports during the server pro file definition 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 If such a range is insufficient you can also select a range double the size using MAC Address Range 1 and 2 to MAC Address Range 7 and 8 Each of these areas contains 16000 MAC add
302. u wish to delete the corresponding server profiles 5 If you confirm this the server profiles will be deleted q You can only delete server profiles that are not assigned If this is not the case the Delete button or Delete Profile menu item is inac tive Assigning server profiles You use the Server Configuration tab to assign server profiles to individual slots or PRIMERGY rack servers D The number of possible assigns depends on the registered licenses T Each license contains a count which allows a certain number of assigns If the assign counts of all licenses are used up no further assign is possible Only one assign count is allocated per profile assign even for multislot profiles 1 Click Server List if applicable to switch to the server list view in the area on the left 296 ServerView Virtual IO Manager 9 6 Assigning server profiles In the tree structure on the left select the corresponding blade server or PRIMERGY rack server from the VIOM Managed group Switch to the Server Configuration tab in the area on the right Select the required slot of the blade server or the required PRIMERGY rack server in the table D For blade servers you can also assign the server profile to an F empty slot You can only assign a server profile to a server blade or PRIMERGY rack server if the server is switched off power off You can see whether the state of the server is correct in the State column If the state
303. ual lO Manager 14 1 VIOM Backup Service Field Mandatory Special characters Year 1970 2099 ty Table 5 Fields of a Quartz cron expression Example A simple example would be O 0 19 24 DEC 2010 This cron expression would trigger a backup job at 7 00 p m on 24 12 2010 The following table shows the use of special characters in a cron expression Special Description Meaning of characters the example Describes a list of 2 or 92 SAT SUN At9am more values Describes a sequence starting with x and incre mented by y ServerView Virtual lO Manager 341 14 VIOM database Special Description Meaning of characters the example Day of month and day of MON 2010 Every second week must not be givena value at the same time so use the question mark for the unspecified field of the two Last day of month 008L Nearest weekday to x 009 15W where x ranges from 1 to 31 The y th weekday xofa 009 2 month where y ranges from 1 to 5 and x from 1 to 7 __ _ neaning SUN SAT Jo o monty SUN SAT Table 6 Use of special characters Last weekday x of every 0012 7 6 At 12 noon on month where x ranges the last Friday from 1 7 meaning SUN SAT 14 1 2 Configuring the job schedule on Linux The Backup Service uses the open source Quartz framework to periodically run jobs that perform various backups of the database Quartz is configured by editing the file lopt fujitsu ServerV
304. unctionVLANId optional The Vlan ID that is used by this function This value must not be spec ified for FCoE functions ServerView Virtual lO Manager 329 330 ServerView Virtual lO Manager 13 13 1 VIOM scenarios This chapter describes examples of when VIOM can be used 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 By virtualizing the I O addressing tasks can be shifted without the network administrators having to be involved In order to shift server profile tasks from the central management station with out involving a network administrator you must use virtual addresses To do this you have to select virtual addressing when you define the server profile 1 When defining a server profile check the Use virtual addresses option in the second step of the Create Server Profile wizard You move a server profile from one server blade to another on the Server Configuration tab You do this as follows 1 Click Server List if applicable to switch to the server list view in the area on the left 2 Inthe tree structure on the left select the corresponding blade server from the VIOM Managed group Switch to the Server
305. uration tab on the right and select Create Pro file from the context menu of a table entry Name step Create Server Profile wizard Name is the first step in the Create Server Profile wizard In the first step you specify the name of the server profile its intended target and optionally a comment ServerView Virtual lO Manager 187 5 Virtual lO Manager user interface Create Server Profile Name of the profile Select type of profile Virtual Addresses Server Blade Contr Server Blade double height Other PRIMERGY Server Preset values to use for server type Comment 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 Other PRIMERGY Server The profile can be assigned to a PRIMERGY rack server Preset values to use for server type Server model optional 188 ServerView Virtual lO Manager 5 4 Wizards The number and type of LAN ports under Onboard IO channels are adjusted automatically according to the server model you select The number of LAN ports and mezzanine PCI cards cannot exceed the max imum possible valu
306. ved address iz range otherwise you might find that you are using addresses from a vendor address range and this could result in duplicated addresses The original addresses of a controller should never be used as virtual addresses in a VIOM server profile If you have several installations of the Virtual lO Manager in your network you must ensure that the address ranges used by two installations do not overlap Otherwise addresses may be assigned several times to different systems which results in duplicated addresses Creating diagnostic data To activate the trace functionality of the ServerView Virtual lIO Manager serv ice please edit the file ViomConfig properties in the directory lt Server View Suite gt plugins viom Manager 356 ServerView Virtual lO Manager 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 lIO Manager service is lt ServerView Suite gt plugins viom Manager logs viom manager log To also get full trace information from the module that configures connection blades such as IBP 10 6 IBP 30 12 SB11A or SB11 add the debug option trace driverdbg to this line StartOptions debug trace driverdbg The ServerView Virtual lO Manager service
307. ver VIOM is installed on the central management station and integrated in the ServerView Operations Manager 28 ServerView Virtual lO Manager 2 3 Management with VIOM Procedure For blade servers management with VIOM essentially includes the following functions e Defining the network paths on the Intelligent Blade Panel IBP module e Defining the I O parameters including virtual addresses of a server blade e Saving the I O parameters in combination with the required network paths in server profiles e Assigning the server profiles to the server blades or to empty slots as well as moving a server profile between any number of server blades You can assign the server profiles to any number of different server blades of a blade server or even to another blade server provided that the required net work connections are available on the respective chassis For PRIMERGY rack servers management with VIOM essentially includes the following functions e Defining the I O parameters including virtual addresses of a PRIM ERGY rack server e Saving the I O parameters in server profiles e Assigning the server profiles toa PRIMERGY rack server Before you can execute the functions above a blade server chassis or PRIM ERGY rack server must be managed by VIOM You also do this using the GUI of the Virtual lIO Manager see chapter Managing servers with VIOM on page 257 Management using VIOM is divided into the following key steps
308. ver in order to assign a server profile to this slot or PRIMERGY rack server For blade servers a server profile can also be assigned to an empty slot A slot can thus be prepared for use at a later date Using virtual addressing you can e g quickly replace a faulty server blade by preconfiguring another server blade without changing the configuration 44 ServerView Virtual lIO Manager 2 5 3 2 5 4 2 5 Server profiles 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 The networks explicitly named in the server profile must be configured before hand in the affected IBP modules If non VIOM capable LAN modules are installed Open Fabric mode you cannot set any dedicated LAN connections paths In this case you must work with profiles whose I O ports do not contain any network assignment Virtualizing I O parameters Virtualizing the physical server identity in the form of physical MAC address es WWN addresses and boot parameters is a key function of the Server View Virtual lO Manager software By defining virtual I O addresses and boot parameters as part of a server pro file you
309. very right of the upper row as seen from behind first uplink port Figure 14 First uplink port of an IBP module For an IBP 10 6 the first uplink port is port 0 11 and for an IBP 30 12 it is port 0 31 IBP administration must be granted access to this port 104 ServerView Virtual lO Manager 4 1 4 1 4 1 Configurations on the managed BX600 Blade Server For the external switch to which an IBP module is connected for admin istration you have to ensure that the Spanning Tree Protocol STP is switched off for the port which is connected to the first uplink port of the IBP module Before you activate management of a blade server with VIOM only this port is allowed to have a connection to external LAN switches Other LAN cables for the connection with other networks to external switches may only be con nected once the management of the blade server with VIOM has been acti vated This is because the first six or first eight uplink ports form a static link aggregation group LAG in the IBP standard configuration Network Overview All components such as the management blades and I O connection blades the central management station and the management console must be inter connected via LAN It is recommended that you set up a management LAN that is separate from the productive LAN as illustrated in the following figure D If there are not enough physical ports available a VLAN based man Aa 3 agement LAN can also be i
310. vice 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 Disable Boot Menu Usage F12 Prevents the VIOM boot settings from being overwritten on your local computer SMUX setting This is only visible if a second mezzanine card of a blade server profile is defined as a LAN mezzanine card Defines the fabric to which the second mezzanine card is routed ServerView Virtual lO Manager 209 5 Virtual lO Manager user interface Fabric 3 All paths are routed to fabric 3 Fabric 4 All paths are routed to fabric 4 Fabric 3 amp 4 LAN1 is routed to fabric 3 and LAN2 to fabric 4 For more information on SMUX settings see the documentation PRIM ERGY BX900 Blade Server Systems ServerView Management Blade 1 The upper table displays the onboard ports up to 6 Another table is dis played for each available mezzanine PClI card configured in the previous step The tables have the following columns first col Port number of the onboard or the mezzanine PCI card port On umn CNA cards the type of the function LAN FCoE iSCSI can be selected from the drop down list Another function can be added to this port with the button Functions can be removed with the button 210 ServerView Virtual IO Manager 5 4 Wizards Network Name o
311. virtual address or select Allocate virtual address In the latter case VIOM automatically assigns a virtual address after you exit the wizard D Automatic assignment is only possible if you specified address 5 ranges when you installed VIOM see Installing the Virtual lO Manager on a Windows based CMS on page 58 Next to each virtual address you see the status of the address If you specify an address you can select Ignore range to disable the check whether the address is in the range that you specified during the installation of VIOM ServerView Virtual lO Manager 293 9 2 9 3 9 Defining and assigning server profiles 19 20 21 Once you have entered all the required data click Next to go to the Con firm step of the wizard Use this step to check the entries you have made once again 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 Viewing server profiles You can view a server profile definition You do this as follows 1 Switch to the Server Profiles view in the area on the left of the Server View Virtual lO Manager window Click Profiles if applicable Select the required profile in the area on the right of the ServerView Vir tual lO Manager window Then click Details or select Show Details in the context menu of the sele
312. w Virtual lO Manager Command Line Interface Target groups and objective of this manual This manual is aimed at system administrators network administrators and service professionals who have a sound knowledge of hardware and soft ware The manual describes the functionality and user interface of theVirtual 1O Manager System requirements Central management station e Operating system for the central management station o Microsoft Windows Server 2003 all editions o Microsoft Windows Server 2003 R2 all editions o Microsoft Windows Server 2008 all editions o Microsoft Windows Server 2008 R2 all editions o Linux Novell SLES10 SP2 and SP3 o Novell SLES 11 SP1 and SP2 12 ServerView Virtual lO Manager 1 2 System requirements o RedHat RHEL 5 6 5 7 5 8 o RedHat RHEL 6 6 1 6 2 D In Japan Novell SLES is not supported ServerView Virtual lO Manager can also be installed in Virtual Machine VM under Windows Hyper V or VMware ESX server The operating system running on the VM must be one of the above listed operating sys tems and must be supported by the used hypervisor e Installed software packages o ServerView Operations Manager as of Version 5 50 13 o Java Runtime Environment JRE version 6 0 update 31 or higher D Together with ServerView Operations Manager 6 10 it is g also possible to use JRE version 7 0 update 7 or higher e Fire wall settings o Port 3172 must be opened for TCP IP conn
313. w Virtual lO Manager 257 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 iIRMC of this server To access the iIRMC you must specify user name and password 1 Select the required server To do this click the required server in the VIOM Manageable server group on the left of the VIOM window The server is displayed on the Setup tab The tab view corresponds to the model and configuration of the selected server D As long as the server does not belong to the VIOM Managed E server group only the Setup and Virtual lO Manager tabs are activated 2 Click the Manage button If you are going to manage a blade server you receive a warning that the previous configuration will be deleted This means that the default set tings following the initial operation of the blade server or even the user defined settings in the IBP modules will be deleted For more information on this see section VIOM internal operations on blade servers on page 261 3 If youclick Yes the Authentication dialog box opens This dialog box varies depending on the selection in the table on the Setup tab S
314. w the files to be deleted and delete them by clicking the Finish button Restoring VIOM specific configurations Restoring an IBP module configuration If an error occurs during the configuration of an IBP module then the con figuration of the IBP module no longer matches the one saved internally in the database in the Virtual lO Manager This incorrect status is displayed on the Setup tab for the respective chassis with a corresponding status icon on the graphical display of the IBP module on the rear side of the chassis Inthis situation you can only continue configuring the respective IBP module once you have restored the configuration You do this as follows 1 Click the respective IBP module in the graphical display on the rear of the chassis 2 Thenclick the Restore IBP button 308 ServerView Virtual lO Manager 11 4 Restoring VIOM specific configurations The Restore IBP function rewrites the configuration saved internally in the VIOM database to the IBP module D In doing so all the connections are interrupted momentarily as all E the network connections are reprogrammed in the IBP module The same applies if a defective IBP module is replaced In this case the Vir tual IO Manager recognizes that a new connection blade has been inserted in the managed blade server chassis The corresponding module is indicated on the Setup tab with a note regarding the inconsistent configuration You restore the configuration as
315. while not at least one AS r eee r active port is included in the uplink set 5 4 1 5 DCB Properties step Create Network wizard single VLAN network DCB Properties is the third step in the Create Network wizard if a single network or a VLAN network is created This step is only displayed if the connection blade supports DCB Data Center Bridging i e for PY CB Eth Switch IBP 10 Gb 18 8 connection blades 172 ServerView Virtual lO Manager 5 4 Wizards Create Network for IBP Purpose FCoE x Priority Level 3 Bandwidth 50 Hints DCB Data Center Bridging is mandatory to use FCoE Finish Cancel Help 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 Possible values are 0 to 7 for FCoE this is by default the value 3 for iSCSI the default value is 4 Bandwidth The share of the bandwidth in percent that is assigned to this function If the sum of all bandwidths of one O channel is not 100 the values are internally adjusted accordingly ServerView Virtual lO Manager 173 5 Virtual lO Mana
316. xam ple means that a bandwidth of at least 6 Gb sec is reserved for the FCoE packages 5 4 4 6 Virtual Addresses step Edit Server Profile wizard Virtual Addresses is the next step in the Edit Server Profile wizard In this step you specify the virtual addresses for each port It is only shown if Use virtual addresses is activated in the second step of the Edit Server Profile wizard Edit Server Profile profile2 Onboard 1 irtual MAC 00 19 99 3e d2 a1 Not changed Ignore range Allocate virtual address Onboard 2 irtual MAC Eo be assigne O Allocate fllocate virtual address Check Addresses Previous Next _ Finish Cancel Help Figure 56 Virtual Addresses step 220 ServerView Virtual lO Manager 5 4 Wizards Virtual MAC Virtual WWNN Virtual WWPN Virtual E MAC The virtual address Virtual MAC and E MAC Enode MAC addresses must have the structure XX XX XX XX XX XX while virtual WWN address es must have the structure XX XX XX XX XX XX XX XX Each x represents a hexadecimal character 0 9 a f A F D The Enode MAC address is the MAC address of an FCoE func tion Ignore range If this option is selected it is not checked whether the given virtual address is in the range that was specified when you installed VIOM Allocate virtual address VIOM automatically assigns a virtual address after you exit the wizard D Automatic assignment is only possibl
317. xt The second step of the Create network wizard opens 3 The following steps are the same steps as the steps for defining single networks 4 In addition to the steps for defining a single network a Service VLAN ID must be specified Enter the required Service VLAN ID 5 Once you have made all your entries confirm these with Finish When you click Finish a dedicated service network is created with the con figured uplink set The new network is added to the tables on the Graphic and Details tabs A dedicated service network contains always the value service vlan id in the VLAN id column Modifying an uplink set You can modify a defined uplink set via the Graphic and Details tabs on the Ext LAN Connections tab 1 Select the corresponding uplink set in the table on the Graphic or Details tab 2 Click Edit The Edit Uplink Set wizard is launched in which you can change the configuration ServerView Virtual lO Manager 285 8 3 8 Defining network paths LAN D The name of the uplink set cannot be changed the field is inac j tive The type of the uplink set cannot be changed either The Edit Uplink Set wizard is the same as the Create network wizard see section Defining an uplink set 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
318. you have to add it to the server list of the ServerView Operations Manager after you have configured it 1 2 a g a z ServerView Virtual lO Manager 135 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 D In this window you have to specify the IP address and the system T name of the management blade You can find a detailed description on the server browser in the ServerView Operations Manager user manual If the server is added to the ServerView server list then this server is also automatically added to the VIOM specific server group VIOM Manageable In order to manage a server it is essential to move it from the VIOM Man ageable server group to the second VIOM specific server group VIOM Man aged In the context of VIOM we refer to this as VIOM management acti vation More information on activating and deactivating VIOM management for a server is described in chapter Managing servers with VIOM on page 257 136 ServerView Virtual IO Manager 5 Virtual lO Manager user interface This chapter contains a general introduction to the Virtual lIO Manager VIOM describing e The structure of the Virtual lIO Manager start page e The tabs wizards dialog boxes buttons and context menus that are available when working with VIOM e The meani

Download Pdf Manuals

Related Search

Related Contents

Descargar manual  FreeRDP User Manual - FOSS  Jet Tools Table Saw User's Manual  Palax KS35 Ergo/S Manuel    GP50 Gradient Pump Operator`s Manual  Technaxx Protection Case TE01  Avira User Manual  Xyron 850 / 1200 user manual  MANUAL DEL OPERADOR  

Copyright © All rights reserved. Failed to retrieve file