File based backup fails on VC - PNID is not resolvable to any IP on the existing system
search cancel

File based backup fails on VC - PNID is not resolvable to any IP on the existing system

book

Article ID: 395698

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

Symptoms
yyyy-mm-ddThh:mm:ss [20220216-230008-18778458] [MainProcess:PID-27365] [Net::GetPNIDAddrInfo:Net.py:639] INFO: PNID 'example.local' is resolved with addresses: ['10.#.#.#']
yyyy-mm-ddThh:mm:ss [20220216-230008-18778458] [MainProcess:PID-27365] [BackupManager::GenerateBackupMetadata:BackupManager.py:202] ERROR: PNID is not resolvable to any IP on the existing system

 

Environment

VMware vCenter Server 8.0.x
VMware vCenter Server 7.0.x

Cause

DNS servers of the VCs PNID have incorrect A records and not resolving to the IP of the VC

Resolution

Verify nslookup outputs to ensure the DNS server resolved to the correct IP ,and update A records as needed . After ensuring A records are valid and correct, the backup job will work again. 

  • Find the DNS servers configured on SDDC
    1. Login to SDDC using vcf and su to root
    2. Run the command 
      cat /etc/resolv.conf

Example output

# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 192.X.X.X

nameserver 194.X.X.X
search example.local 

  • nslookup the VC FQDN to IP using both Name servers.
    nslookup example.local 192.#.#.#

    The output  should return the actual IP of VC 

Server:         192.X.X.X
Address:        192.X.X.X#53

Name:   example.local
Address: 192.X.X.X

  • nslookup example.local 192.#.#.#
    The output  should return the actual IP of VC 

Server:         194.X.X.X
Address:        194.X.X.X#53

Name:  example.local
Address: 192.X.X.X

If the outputs differ from the actual IP address of the VC, then A records to be updates on the DNS servers configured to reflect the actual IP of VC.