SnapCenter is unable to discover resources when using disjoint namespace
Applies to
SnapCenter 4.9
Issue
- SnapCenter is unable to discover resources when using disjoint namespace
- The following is seen in the
SnapManagerWeb_<JobID<.logfor the resource discovery job:
- The following is seen in the
INFO SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] Start - GetHostNameINFO SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] Account details: bypassdomain TrueDEBUG SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] Resolving host name =<ServerName.DomainName>INFO SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] Validate DNS hostEntry for any Malicious script or contentINFO SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] End - GetHostNameDEBUG SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] DiscoverResources URL: https://<ServerName.DomainName>:8145/SMCoreHostManagementService/DiscoverResources.......................ERROR SnapManagerWeb_<JobID> PID=[xxxx] TID=[217] ErrorCode (121), ErrorMessage (Host '<ServerName>' is not registered with SnapCenter Server.)......................INFO SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] StorageFileSystem count: 0DEBUG SnapManagerWeb_<JobID> PID=[xxxx] TID=[xxxx] Could not find resource's StorageFileSystem.
- When adding a host or cluster, SCW discovery does not work and the file system is not discovered
Standalone hostResponse error: Host 'hostname' is not registered with SnapCenter Server
- Cluster
Failed to find host (hostname). Verify the host is up and running and check the DNS and firewall settings. No such host is known
Note: If these errors are seen when using disjoint namespaces, follow the Solution section
