Troubleshooting server profiles

Server profile is not created or updated correctly

When a server profile is not created or updated correctly, a notification appears at the top of the screen stating the profile operation was not successful; click the notification area to show more details. Also, the status icon next to the server profile name indicates it is in an Error condition (). The profile remains on the appliance, but you must edit the profile to correct it. When you correct the server profile, the profile status changes to OK ().

Symptom Possible cause and recommendation

Server profile is not created or updated correctly

Verify the following conditions:

  1. Verify that the prerequisites listed in Create and apply a server profile have been met.

  2. Verify that the following conditions are TRUE:

  3. When issues have been addressed, either edit the profile or delete the profile and create another profile.

Server profile has duplicate networks on the same physical port

  • Change the connection to a different port

  • Change the connection to use a different VLAN

Cannot find a network when adding a connection

Verify that the following condition is true:

  • The logical interconnect group is set up with the networks configured into uplink sets

Cannot add a connection from the profile

Verify that the following conditions are true:

  • The interconnects in the logical interconnect group are in the Configured state and have the correct firmware

  • The servers are in the No Profile Applied state, have the correct firmware, and the ports are mapped to the correct interconnect

A profile operation timeout when applying BIOS settings

The server hardware or its iLO are powered-off or reset

  • In most cases, retrying the operation resolves the problem

The appliance cannot collect progress information from the iLO

  • In most cases, retrying the operation resolves the problem

Auto-assignment for FlexNIC fails while assigning/deploying connections

Invalid configuration

  • Auto-assignment for FlexNIC connections does not validate the following:

    • Bandwidth oversubscription on the physical port

    • Maximum networks (VLANs) on the physical port

    • Duplicate networks (VLANs) on the physical port

  • Manual assignment is required

Cannot apply the server profile

Symptom Possible cause and recommendation

Cannot apply the server profile

If you received an error that Intelligent Provisioning failed to boot in the required period of time, perform these steps:

  1. Attempt to boot into Intelligent Provisioning manually on the affected system by pressing F10 during POST.

  2. If manually booting to Intelligent Provisioning works, then retry the operation from HPE OneView.

    If manual booting still fails, reboot the iLO and then retry step 1.

  3. If the previous steps fail and the server is a BL465c with an active Smart Array Controller, disable the IOMMU on the server temporarily using RBSU.

    1. During system boot, press F9 to enter the RBSU.

    2. Select System Options.

    3. Select Processor Options.

    4. Select AMD-Vi (IOMMU).

    5. Select Disabled.

    6. Save and exit RBSU.

  4. If booting still fails, install the latest version of Intelligent Provisioning found at http://hpe.com/info/intelligentprovisioning..

Cannot verify the status of the server hardware

Verify the operational status of the server hardware

  1. Click Cancel to exit from the Create Server Profile screen.

  2. From the main menu, navigate to the Server Hardware screen.

  3. Find, and then select the server hardware.

Profile operations are not successful

Symptom Possible cause and recommendation

Message indicates that the server is managed by another management system

The enclosure is no longer managed by HPE OneView

To prevent losing all allocated virtual IDs, perform the following steps before forcibly deleting the server profile.

  1. Use REST APIs or Powershell to get the server profile.

    GET /rest/server-profiles

  2. Force delete the profile using the UI or REST APIs.

  3. Recreate the IDs using the User Specified option in the UI, or use REST APIs to create the server profile:

    1. Get the server profile.

      GET /rest/server-profiles

    2. Edit the server profile.

      1. Remove uri, serverHardwareTypeUri, enclosureGroupUri, enclosureUri, and enclosureBay.

      2. Change the serverHardwareUri value to the server the profile is going to be associated to.

      3. Change serialNumberType from Virtual to UserDefined.

      4. In the connections property, change macType from Virtual to UserDefined.

      5. In the connections property, change wwpnType from Virtual to UserDefined.

      6. In the connections property, if applicable change networkUri with the correct networks.

    3. Create the server profile.

      POST /rest/server-profiles

Cannot update or delete profile

Symptom Possible cause and recommendation

Unable to update profile: MyProfile

A firmware update is in progress 

When a firmware update is in progress, you cannot make additional firmware changes.

Wait until the firmware install is complete.

Unable to delete profile: MyProfile

A firmware update is in progress 

When a firmware update is in progress, you cannot make additional firmware changes.

Do one of the following:

  • Wait until the firmware installation is complete. It is highly recommended that you do not abort before the installation is completed.

  • Select the Force delete option.

Server is not powered off 

To delete a profile, the server must be powered off.


[NOTE: ]

NOTE: Momentary press is allowed at all times but Press and Hold is restricted as it might send the server to an inconsistent state.


Unable to power off server profile

Press and hold operation is denied 

The Press and hold power operation is not allowed while HPE Smart Update Tools is updating firmware or drivers.

Do one of the following:

  • Momentarily press the power button and HPE SUT will ensure none of the hardware goes to an inconsistent state.

  • Try the Press and hold power operation after HPE SUT has moved to a terminal state.


[NOTE: ]

NOTE: It is highly recommended that you wait until the firmware installation is complete and that you do not abort the process.


Cannot complete firmware installation

The firmware on {server} does not match the firmware baseline 

If you selected to update firmware using HPE SUT, you need to install HPE SUT to complete the firmware and driver update.

Inconsistent firmware

Symptom Possible cause and recommendation

Firmware installation not complete or does not match baseline

Firmware does not match firmware baseline 

Do one of the following:

  • Install and run HPE Smart Update Tools.

  • Edit the server profile to use the “Firmware only” option for firmware baseline installation.

Unable to update firmware

Baseline not supported with HPE Smart Update Tools 

Do one of the following:

  • Select a baseline that has HP SUM 7.4 or above and iLO firmware version 2.30 or above. For information about HP SUM, see the HP SUM Best Practices Implementation Guide at: www.hpe.com/info/hpsum/documentation.

  • Edit the affected server profiles to use Firmware only.

Server does not have required license for virtual media 

Apply an iLO Advanced license on the server or apply an iLO hotfix for 2.30.

Servers powered on, but not configured for HPE SUT

Servers are powered on but their server profiles are not configured to use HPE Smart Update Tools 

Edit the affected server profiles and select a firmware update option that uses HPE Smart Update Tools.


[NOTE: ]

NOTE: This symptom can also appear when attempting Logical Enclosure shared infrastructure and server profile firmware update.


Any failure to update firmware and OS drivers

Some components did not deploy 

If a few components fail to deploy, login to the target server OS and run gatherlogs bat/sh (use either bat or sh based on whether the OS is Windows or Linux, respectively). gatherlogs is located in the target server staging directory. To identify the staging directory, use the hpesut—status command from the staging directory and send the report to HPE for troubleshooting. See the HPE Smart Update Tools User Guide at: http://www.hpe.com/info/hpsut/docs.