"lsdoctor" tool reporting "Duplicates by Node ID" for "NO_NODE_ID"
search cancel

"lsdoctor" tool reporting "Duplicates by Node ID" for "NO_NODE_ID"

book

Article ID: 412605

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When performing the pro-active steps mentioned in KB:387138 - Using the tool "lsdoctor" the following error is displayed:
    },
        "default-site": {
            "##NO_HOSTNAME##": {
                "2nd Party Products": "None",
                "Problems Detected": {
                    "Duplicates Found": {
                        "Description": "Duplicate Endpoints Detected",
                        "Duplicates by Node ID": {
                            "NO_NODE_ID": {
                                "dpxa": [
                                    "########-####-####-####-########2bd3",
                                    "########-####-####-####-########87b1"
                                ]
                            }
                        },
                        "Link": "https://kb.vmware.com/s/article/80469",
                        "Recommended Action": "Ignore if this is the PSC HA VIP.  Otherwise, you must unregister the extra endpoints.",
                        "Severity": "High"
                    }

Environment

vCenter 8.x

SRM Version 9.0.x

Cause

  • The "NO_HOSTNAME" entry can be caused by second party and/or third party plugins registering with vCenter. 
  • The following Endpoint(s) are also detected/provided by lsdoctor points to a known SRM URL:
    {
                            "Endpoints (1)": {
                                "URL(1)": "<SRM_FQDN>"
                            },
                            "Node ID": "",
                            "Owner ID": "########-####-####-####-########[email protected]",
                            "Problems Detected": "No problems found.",
                            "Service ID": "########-####-####-####-########87b1",
                            "Version": "9.0.2.24170200"
                        }
  •  

Resolution

  • If SRM is still in use then take no-action using lsdoctor tool.