Problem: We have recently added two VMs to VMAN and the VMs are showing with 'Up' for Node Details, however, Virtual Center Details shows 'Unknown' for the VCenter status on one of them, while the other shows information correctly. The Clusters\Hosts\Guests 'with problems' sections are all showing 'Parent vCenter/ESX has problem(Node status is unknown)' -- We are running version 2020.2.6 for Orion and all of our modules, with VMAN HF5. This is the first time we have tried using VMAN, it's never been in use prior to now; so we have no answer for the 'has it ever worked before?' question. The VMware vCenter Server shows Version 6.7.0. -- Credentials have been verified and seem to be authenticating properly. Polling method is set to 'VMAN Orion' for both devices and the 'Polling Status' is green for both devices. On the 'Node Properties', the 'Poll for VMware' box is ticked and the proper credentials are populated and test successfully. -- We have tried removing both vCenters and re-adding them with either the same results, or the problem flips to the other machine and vice-versa. It's almost as if for some reason VMAN can only pull from one or the other, but not both for some reason. -- We have tried adjusting the polling interval to longer periods, from 120 seconds all the way up to 300 seconds. We tested increasing the interval in 60 second increases, to no avail. Problem: We have recently added two VMs to VMAN and the VMs are showing with 'Up' for Node Details, however, Virtual Center Details shows 'Unknown' for the VCenter status on one of them, while the other shows information correctly. The Clusters\Hosts\Guests 'with problems' sections are all showing 'Parent vCenter/ESX has problem(Node status is unknown)' -- We are running version 2020.2.6 for Orion and all of our modules, with VMAN HF5. This is the first time we have tried using VMAN, it's never been in use prior to now; so we have no answer for the 'has it ever worked before?' question. The VMware vCenter Server shows Version 6.7.0. -- Credentials have been verified and seem to be authenticating properly. Polling method is set to 'VMAN Orion' for both devices and the 'Polling Status' is green for both devices. On the 'Node Properties', the 'Poll for VMware' box is ticked and the proper credentials are populated and test successfully. -- We have tried removing both vCenters and re-adding them with either the same results, or the problem flips to the other machine and vice-versa. It's almost as if for some reason VMAN can only pull from one or the other, but not both for some reason. -- We have tried adjusting the polling interval to longer periods, from 120 seconds all the way up to 300 seconds. We tested increasing the interval in 60 second increases, to no avail.

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

VMAN only accurately polling one of two vCenters

tvminser over 2 years ago

Problem: We have recently added two VMs to VMAN and the VMs are showing with 'Up' for Node Details, however, Virtual Center Details shows 'Unknown' for the VCenter status on one of them, while the other shows information correctly. The Clusters\Hosts\Guests 'with problems' sections are all showing 'Parent vCenter/ESX has problem(Node status is unknown)'

-- We are running version 2020.2.6 for Orion and all of our modules, with VMAN HF5. This is the first time we have tried using VMAN, it's never been in use prior to now; so we have no answer for the 'has it ever worked before?' question. The VMware vCenter Server shows Version 6.7.0.
-- Credentials have been verified and seem to be authenticating properly. Polling method is set to 'VMAN Orion' for both devices and the 'Polling Status' is green for both devices. On the 'Node Properties', the 'Poll for VMware' box is ticked and the proper credentials are populated and test successfully.
-- We have tried removing both vCenters and re-adding them with either the same results, or the problem flips to the other machine and vice-versa. It's almost as if for some reason VMAN can only pull from one or the other, but not both for some reason.
-- We have tried adjusting the polling interval to longer periods, from 120 seconds all the way up to 300 seconds. We tested increasing the interval in 60 second increases, to no avail.