UNSOLVED

postcat

updated

7 years ago

P

postcat

1 Message

0

2885

December 4th, 2019 02:00

VxRail E560F validate Error

Each node is connected via Cisco 3850

Disk Information Not Available
Failed to get disk information on host DE700193900056-01-01.
ESXi host (DE700193900055-01-01)
An error occurred when attempting to connect to host at null.
ESXi host (DE700193900056-01-01)
An error occurred when attempting to connect to host at null.
ESXi host (DE700193900057-01-01)
An error occurred when attempting to connect to host at null.
Management password
An error occurred while validating the provided ESXi password. Consider using a new password, or attempt to re-validate.
Management username
An error occurred while validating the provided ESXi user name. Consider using a new user name, or attempt to re-validate.
Root password
An error occurred while validating the provided ESXi password. Consider using a new password, or attempt to re-validate.
config.validation.host.0.communication.error
Communication Error (DE700193900057-01-01)
config.validation.host.1.communication.error
Communication Error (DE700193900055-01-01)
config.validation.host.2.communication.error
Communication Error (DE700193900056-01-01)
hosts.DE700193900055-01-01.systemInfo.vendor
Failed to find hardware manufacturer model from node MarvinId {id=DE700193900055, totalSupportedNodes=1, position=1}.
hosts.DE700193900056-01-01.systemInfo.vendor
Failed to find hardware manufacturer model from node MarvinId {id=DE700193900056, totalSupportedNodes=1, position=1}.
hosts.DE700193900057-01-01.systemInfo.vendor
Failed to find hardware manufacturer model from node MarvinId {id=DE700193900057, totalSupportedNodes=1, position=1}.
misc
An internal server error occurred during environment preparation for WitnessHostValidator.

 

How do I fix it?

  • Richard Giv

    1 Message

    2528

    0

    Posted December 19th, 2019 06:00

    I have exactly the same error on new deployment running 4.7.110-12663825

     

    Disk Information Not Available
    Failed to get disk information on host DE600192402558-01-01.
    ESXi host (DE600192402556-01-01)
    An error occurred when attempting to connect to host at null.
    ESXi host (DE600192402557-01-01)
    An error occurred when attempting to connect to host at null.
    ESXi host (DE600192402558-01-01)
    An error occurred when attempting to connect to host at null.
    Management password
    An error occurred while validating the provided ESXi password. Consider using a new password, or attempt to re-validate.
    Management username
    An error occurred while validating the provided ESXi user name. Consider using a new user name, or attempt to re-validate.
    Root password
    An error occurred while validating the provided ESXi password. Consider using a new password, or attempt to re-validate.
    config.validation.host.0.communication.error
    Communication Error (DE600192402557-01-01)
    config.validation.host.1.communication.error
    Communication Error (DE600192402556-01-01)
    config.validation.host.2.communication.error
    Communication Error (DE600192402558-01-01)
    hosts.DE600192402556-01-01.systemInfo.vendor
    Failed to find hardware manufacturer model from node MarvinId {id=DE600192402556, totalSupportedNodes=1, position=1}.
    hosts.DE600192402557-01-01.systemInfo.vendor
    Failed to find hardware manufacturer model from node MarvinId {id=DE600192402557, totalSupportedNodes=1, position=1}.
    hosts.DE600192402558-01-01.systemInfo.vendor
    Failed to find hardware manufacturer model from node MarvinId {id=DE600192402558, totalSupportedNodes=1, position=1}.
    misc
    An internal server error occurred during environment preparation for WitnessHostValidator.
     
    Did you manage to resolve the issue ?
  • Osama2020

    1 Message

    2121

    0

    Posted July 12th, 2020 03:00

    I have the Same error on vxrail E560 with 4.5 firmware.

    any one did fix it?

  • 2087

    0

    Posted July 14th, 2020 19:00

    Hi

    I have the same error.you already found some solution?

  • novahertz

    1 Rookie

    •

    24 Posts

    1531

    0

    Posted March 19th, 2021 08:00

    its seems stupid but check time synchronization for every single ESXi host. as well DNS resolution, this can fix a lot of weird validation errors.