PNID change issue on 6.7 Update 3

-

As we know PNID change is supported on 6.7 U3 onwards, however while changing the hostname from VAMI, you may encounter errors “Failed to create replication placeholder” and “Network update failed” :


To fix the issue, we need to replace the pnid_utils.py file which is at /usr/lib/applmgmt/networking/py/vmware/appliance/networking/pnid/ location with attached one, restart Appliance mgmt. service and try changing PNID again.

Comments

Post a Comment

Popular posts from this blog

Replacing vROPS Certificates

-
Image
Issue:  When using default certificates in vROPS  Due to security requirements it was necessary to replace the default self-signed certificates with a trusted certificate signed by an internal CA. Unlike vCenter, vROPS uses a common name vc-ops-slice-1 followed by slice-2 for data and other node, where vCenter has SAN names in the default certificate so when you add the root of the local machine trusted store then the vCenter url shows secured. In order to make the secure SSL we have to generate the CSR and get it signed by any third party SSL vendors or our own Microsoft CA.  I will be generating a CSR and getting signed by internal Microsoft CA .We can refer this below article from VMware as reference.  https://kb.vmware.com/s/article/2046591?lang=en_us Steps:  1.The first step is to create a new private key from taking a SSH session to master node vROPS. openssl genrsa -out vrops.key 2048 2. Using the configuration file below make sure to provide de...
Read more

Manually Replacing the solution user certificate on VCSA/PSC 6.x

-
Manually Replacing the solution user certificate on VCSA/PSC 6.x Note : -- Take a snapshot of the VC or PSC before proceeding. --  PSC has two solution users : machine and vsphere-webclient. -- VC has four solution users : machine, vpxd, vpxd-extension and vsphere-webclient. -- VC with embedded PSC has four solution users : machine, vpxd, vpxd-extension and vsphere-webclient. -- SSO admin username and password would vary depending on the configuration. -- Windows Install directory may vary depending on your installation.  -- Run the below command to get the machine ID of the node : Appliance :   /usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost Windows : "%VMWARE_CIS_HOME%"\vmafdd\vmafd-cli get-machine-id --server-name localhost 0. Take a backup of the old solution user certificates and its private keys. Appliance : /usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store machine --alias machine...
Read more

VAPI Endpoint service failure

-
VAPI Endpoint service failure  ERROR | state-manager1            | StsBuilder                     | Failed to acquire token for the solution user 2018-11-15T21:50:42.647Z | ERROR | state-manager1            | DefaultStateManager            | Could not initialize endpoint runtime state. com.vmware.vapi.endpoint.config.ConfigurationException: com.vmware.vim.sso.client.exception.AuthenticationFailedException: Provided credentials are not valid.         at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:182)         at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)      ...
Read more