Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to update content libraries after changing vCenter Server PNID (76482)

Last Updated: 4/17/2023Categories: How toTotal Views: 4903Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

You see the error Unable to reach the remote library host (no route to host). performing one of these options:

Creation of a new subscription for an existing published library

Sync of an existing subscribed library

Force sync of an existing subscribed library item

Cause

Content libraries are not updated with the new PNID when a vCenter Server's PNID is updated.

Resolution

Running the attached script will update:

Subscription url of all published libraries in the specified VC with new PNID

Subscription url of all subscribed libraries (subscribed with subscriptions) in the specified VC and linked VCs with the new PNID

Subscription url of all subscribed libraries (subscribed without subscriptions) in the specified VC with the new PNID. This script should be executed individually for each VC where such subscribed libraries exist.

Subscription information of all subscribed libraries (subscribed with subscriptions) in the specified VC with the new PNID. Subscription information is stored with its publisher in the specified VC or linked VC.

Prerequisites

Python 3.0 or greater

Running the script

Copy the script to any win/lin machine.

Run the script using command python3 update_pnid_in_content_library.py --help. This should display options for running the script with examples.

To update subscription url of all published libraries in the specified VC (and subscribed libraries with subscriptions in the specified or linked VC) with the new PNID:

python3 update_pnid_in_content_library.py --publishers -vcsa-pnid new_pnid -vcsa-username SSO_username -vcsa-password SSO_password

To update subscription url of all impacted subscribed libraries without subscriptions in the specified VC with the new PNID. Only those subscribed libraries will be updated whose corresponding publisher VC pnid has changed. This script should be executed individually for each VC where such subscribed libraries exist:

python3 update_pnid_in_content_library.py --subscribers -vcsa-pnid subscriber_vcsa_pnid -vcsa-username subscriber_vcsa_SSO_username -vcsa-password subscriber_vcsa_SSO_password -publisher-old-pnid old_pnid -publisher-new-pnid new_pnid

To update subscription information of all subscribed libraries with subscriptions in the specified VC. The subscription information is stored with its publisher in the same VC or a linked VC:

python3 update_pnid_in_content_library.py --subscriptions -vcsa-pnid new_pnid -vcsa-username SSO_username -vcsa-password SSO_password

Note:

It is recommended to run the script such that subscription urls of published libraries are updated first and subscription urls of subscribed libraries are updated next and then the associated subscriptions are updated.

Script will not update the subscription urls of password protected published libraries. This can be manually updated by unpublishing and publishing the library. If the library has subscriptions then delete the subscriptions, unpublish and publish the library (which will update the publish url) and then recreate the subscriptions.

For VCs in linked mode which need to be updated, it is expected that the credentials specified for logging into the specified VCSA has content library privileges on all linked VCs.

Please take a backup of the VC before running the script so that the VC can be restored from the backup if the script fails and leaves the db in an inconsistent state.

Script has not been tested on VCSA deployed with custom ports and might not work as expected.

If the PNID of multiple linked VCs should be updated, it is recommended to run this script after every PNID update. For ex: When PNID of two linked VCs, VC1 and VC2 are updated without running this script, information about subscriptions from VC1 to VC2 might have the wrong PNID for VC2. In this case script might not work as expected. Hence it is recommended to run the script after updating VC1's PNID, update VC2's PNID and run the script again.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

76482_update_pnid_in_content_library.py

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant