VMware Cloud Community
davercyclone
Contributor
Contributor
‎05-01-2012 06:29 PM
Jump to solution

ESX4.0 U4 Upgrade Manager Error to ESXi5

Hi All,

When scanning my two hosts for compatibility with the 5.0 baseline, I recieve an error only only one of the hosts:

"VMkernel and Service Console network interfaces are sharing the same subnet 192.168.1.0. This configuration is not supported after upgrade. Only one interface should connect to subnet 192.168.1.0"

Comparing both hosts:

Host1: vSwitch0 - VM Network / Service Console / VMkernel

Host2: vSwitch0 - VM Network / Service Console

Am I right in removing the VMkernel Port from that host as it is not doing anything (vMotion is performed on a dedicated network). I suspect it is a legacy from something that was in place before my arrival.

Thanks,

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
Virtualinfra
Commander
Commander
‎05-02-2012 12:58 AM
Jump to solution

This is a known issue, After the upgrade there is no more services console it will migrated to management port.

  • By using the Remediate wizard, you can ignore some upgrade scan warnings and force a remediation even if the upgrade warnings are not related to third-party software
    On the ESXi 5.x Upgrade page of the Remediate wizard, you can select Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation to remove third-party software installed on the host and to ensure a successful remediation. Selecting the option also forces Update Manager to ignore three potential issues that are not related to third-party software. The following warning messages are associated with the potential issues.
  • The root password is encrypted with DES encryption, causing it to be authenticated up to only 8 characters. For instructions on how to correct this, see VMware KB 1024500 at http://kb.vmware.com/kb/1024500.
  • VMkernel and Service Console network interfaces are sharing the same subnet <subnet_name>. This configuration is not supported after upgrade. Only one interface should connect to subnet <subnet_name>.
  • Unsupported devices <device_name> found on the host.
Workaround: Before a remediation, perform an upgrade scan and review the messages in the Upgrade Details window of Update Manager. Take the necessary actions recommended by the messages to ensure that the remediation succeeds.

    Solution
    1. This is a known behaviour.

    2. By using the Remediate wizard, user can ignore some upgrade scan warnings and force a remediation even if the upgrade warnings are not related to third-party software.

    3. On the ESXi 5.x Upgrade page of the Remediate wizard, user can select Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation to remove third-party software installed on the host and to ensure a successful remediation.

    4. Selecting the option also forces Update Manager to ignore three potential issues that are not related to third-party softwar

    Refer release notes:

    http://www.vmware.com/support/vsphere5/doc/vsphere-update-manager-50-release-notes.html

    Thanks & Regards Dharshan S VCP 4.0,VTSP 5.0, VCP 5.0

    View solution in original post

    0 Kudos
    2 Replies
    Virtualinfra
    Commander
    Commander
    ‎05-02-2012 12:58 AM
    Jump to solution

    This is a known issue, After the upgrade there is no more services console it will migrated to management port.

    • By using the Remediate wizard, you can ignore some upgrade scan warnings and force a remediation even if the upgrade warnings are not related to third-party software
      On the ESXi 5.x Upgrade page of the Remediate wizard, you can select Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation to remove third-party software installed on the host and to ensure a successful remediation. Selecting the option also forces Update Manager to ignore three potential issues that are not related to third-party software. The following warning messages are associated with the potential issues.
    • The root password is encrypted with DES encryption, causing it to be authenticated up to only 8 characters. For instructions on how to correct this, see VMware KB 1024500 at http://kb.vmware.com/kb/1024500.
    • VMkernel and Service Console network interfaces are sharing the same subnet <subnet_name>. This configuration is not supported after upgrade. Only one interface should connect to subnet <subnet_name>.
    • Unsupported devices <device_name> found on the host.
    Workaround: Before a remediation, perform an upgrade scan and review the messages in the Upgrade Details window of Update Manager. Take the necessary actions recommended by the messages to ensure that the remediation succeeds.

      Solution
      1. This is a known behaviour.

      2. By using the Remediate wizard, user can ignore some upgrade scan warnings and force a remediation even if the upgrade warnings are not related to third-party software.

      3. On the ESXi 5.x Upgrade page of the Remediate wizard, user can select Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation to remove third-party software installed on the host and to ensure a successful remediation.

      4. Selecting the option also forces Update Manager to ignore three potential issues that are not related to third-party softwar

      Refer release notes:

      http://www.vmware.com/support/vsphere5/doc/vsphere-update-manager-50-release-notes.html

      Thanks & Regards Dharshan S VCP 4.0,VTSP 5.0, VCP 5.0
      0 Kudos
      davercyclone
      Contributor
      Contributor
      ‎05-02-2012 01:50 AM
      Jump to solution

      Yeah I thought I had read something along those lines, thanks.

      0 Kudos