OS Startup Issues (with I/O Virtualization)

This section explains how to troubleshoot startup issues on managed servers.

When using HBA address rename

When using HBA address rename, the WWN that was set for the server's HBA is set from the manager when the power to the server is turned on again.

When errors occur within the admin server, the HBA address rename setup service sets the WWN for the server's HBA.

Use the following procedure to confirm and correct the problem.
1. If the server was replaced immediately beforehand, confirm that hardware information was successfully reconfigured following server replacement.
  For details, refer to "6.2.2 Reconfiguration of Hardware Properties" or "6.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide VE".
2. Check the storage environment.
  Check that the WWN set for the server's HBA have access to the appropriate storage device and logical volume. Set a proper access path if none was configured yet.
  
  For details, refer to "8.2 Configuring the Storage Environment" in the "Design Guide VE".
3. Check the manager's startup status.
  For details on how to check the startup status of the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
4. Perform either one of the following based on the manager's startup status.
  - If the manager is not running
    
    Start the manager.
    
    If the manager cannot start because of a server fault, for example, recover the server after completing step 5.
  - If the manager is already running
    
    Occasionally the timing of the manager startup can prevent it from controlling a managed server. If this is the case, restart the managed server.
    
    Even if the manager is running, if communication problems happen on the admin LAN (due to issues with network interfaces, cabling, or LAN switches), the managed server will not start. After performing step 5, the LAN configuration must be repaired.
5. Check the running state of the HBA address rename setup service.
  Check the running state of this service in the HBA address rename server.
  
  Start the server where this service has been set up if it is not running yet, then start the managed server.
  
  The WWN for the managed server's HBA will then be set using the most recent state synchronized with the admin server.
6. Check the managed server console.
  Check the managed server console to confirm that it has successfully started up.
  
  If an error message is output, take action according to the corresponding message ID in "Messages".
7. For managed servers other than PRIMERGY BX servers, check that the MAC address entered at registration is correct. If it is incorrect, reconfigure the server's hardware properties.
  The registered MAC address can be confirmed in the [Resource Details] tab for the corresponding physical server.
  
  Refer to "A.6 [Resource Details] tab" in the "User's Guide VE" for details.
8. Check the following network environment.
  - Whether communication between the admin server and the managed server is possible
  - Whether there are any DHCP or PXE servers running on the subnet used by managed servers
  - When the admin server and the managed server belong to different subnets, whether the DHCP relay agent of the router is correctly configured
When using VIOM or ISM
1. Check settings for the WWN of server HBA, the MAC addresses of NIC, booting, and networking which are managed by VIOM or ISM.
  Check whether the admin LAN server profile is correct or not by opening the VIOM or ISM client.
2. Check the storage environment.
  Check whether the settings for the WWN of the server's HBA, the MAC addresses of NIC, and booting can access correct storage units and volume. If the setting was not completed, set the proper access path.
  
  For details, refer to "8.2 Configuring the Storage Environment" in the "Design Guide VE".

2.1 OS Startup Issues (with I/O Virtualization)