Feed Detail

7 years ago

Hi Kishan, Yes, this is new to 5.17. And I asked Snow for some explanation since for some, the user-defined name was shown while for others the Vcenter host name was? This is what I got back: In SIM 5.14, 5.15 and 5.16, as part of adding support for Oracle licensing and to correctly report and display datacenter/cluster hierarchy, the option of user-defined datacenter names are removed. Additionally a Snowpack file is generated for each Vcenter host that reports basic information as shown in the below example: <Client Architecture ="64-bit" HostName ="DNS name of Vcenter" BiosSerialNumber ="vmware-10 11 12 13 " ConfigName ="VMware vSphere_1" ClientType ="SIEDP" Site ="Snow" ClientVersion ="5.17" Manufacturer ="VMware, Inc." Model ="VMware Virtual Platform" HypervisorName ="VMware Virtual Platform" IsVirtual ="1" IsVDI ="1" /> <OperatingSystem Version ="6.7.0" Name ="VMware vCenter Server" BuildNumber ="123456789" Manufacturer ="VMware, Inc." /> When processed by Snow Inventory, the Vcenter server will be reported as a device in Snow Inventory and SLM. This is what we see in the screenshot shared by you. So the issue in your case is with two Vcenters ‘VCenter X’ and ‘Vcenter Y’. These two Vcenters for some reasons (probably incorrect configuration in Domain or something), fail to expose their configured DNS names (highlighted in yellow in above example) in VSphere API endpoints from which the VSphere connector reads their information. So when the connectors don’t find the DNS names for a Vcenter, it retrieves its configured name in VSphere connector GUI as fallback and report it in generated Snowpack file. Since in your case the user-defined names show up, you might have an issue with a DNS configuration too? success, Gert-Jan.

Expand Post

Gert-Jan Kosterman
7 years ago
Hi Kishan, Yes, this is new to 5.17. And I asked Snow for some explanation since for some, the user-defined name was shown while for others the Vcenter host name was? This is what I got back: In SIM 5.14, 5.15 and 5.16, as part of adding support for Oracle licensing and to correctly report and display datacenter/cluster hierarchy, the option of user-defined datacenter names are removed. Additionally a Snowpack file is generated for each Vcenter host that reports basic information as shown in the below example: <Client Architecture ="64-bit" HostName ="DNS name of Vcenter" BiosSerialNumber ="vmware-10 11 12 13 " ConfigName ="VMware vSphere_1" ClientType ="SIEDP" Site ="Snow" ClientVersion ="5.17" Manufacturer ="VMware, Inc." Model ="VMware Virtual Platform" HypervisorName ="VMware Virtual Platform" IsVirtual ="1" IsVDI ="1" /> <OperatingSystem Version ="6.7.0" Name ="VMware vCenter Server" BuildNumber ="123456789" Manufacturer ="VMware, Inc." /> When processed by Snow Inventory, the Vcenter server will be reported as a device in Snow Inventory and SLM. This is what we see in the screenshot shared by you. So the issue in your case is with two Vcenters ‘VCenter X’ and ‘Vcenter Y’. These two Vcenters for some reasons (probably incorrect configuration in Domain or something), fail to expose their configured DNS names (highlighted in yellow in above example) in VSphere API endpoints from which the VSphere connector reads their information. So when the connectors don’t find the DNS names for a Vcenter, it retrieves its configured name in VSphere connector GUI as fallback and report it in generated Snowpack file. Since in your case the user-defined names show up, you might have an issue with a DNS configuration too? success, Gert-Jan.
Expand Post
- Portal User
  7 years ago
  Thanks Gert-Jan for your response. I will get validate DNS configuration information.
  Expand Post