NetWorker: NMC progress bar stuck at 5% after launching NetWorker Administration window
Summary: This KB documents a scenario that can cause the NMC GUI progress bar to get stuck at 5% progress.
Symptoms
The NetWorker server has one or more VMware vCenter's registered on it.
The NMC server's gstd.raw reports an authentication error for the vCenter:
Windows: C:\Program Files\EMC NetWorker\Management\GST\logs\gstd.raw
gstd NSR notice ERROR generated: "Unable to fetch data from vCenter: Cannot complete login due to an incorrect user name or password." in file "/disks/nasbld/nas83/nw/#.#/nsrwebui/modules/nsm/gstnsm.c" line #4750
Windows: C:\Program Files \EMC NetWorker\nsr\vproxy\logs\nsrvisd/nsrvisd-daemon.log
YYYY-MM-DDTHH:mm:SS-TZ ERROR: [##] 952aa502-3e5a-442b-99bf-80f4372bc4e0-vCenter_Name: Unable to log in to vCenter 'vCenter_Name': ServerFaultCode: Cannot complete login due to an incorrect user name or password.
YYYY-MM-DDTHH:mm:SS-TZ ERROR: [##] 952aa502-3e5a-442b-99bf-80f4372bc4e0-vCenter_Name: Failed to load inventory from 'vCenter_Name'.Cause
Resolution
1. On the NetWorker server, open an Administrator command prompt or root SSH session.
For each of the vCenters reporting a log in failure in the nsrvisd-daemon.log, perform the following.
2. Using the nsrports command, verify that the NetWorker server can resolve the vCenter and connect to port 443.
nsrports -t vCenter_Name -p 443
Example:
[root@nsr ~]# nsrports -t vcsa.amer.lan -p 443
Forward lookup for vcsa.amer.lan
Query time: 0.001 sec
Canonical name (CNAME): vcsa.amer.lan
Address (A): 192.168.9.111
Connect to port 443: Succeeded (0.001 sec)
Reverse lookup for 192.168.9.111
Query time: 0.000 sec
Name: vcsa.amer.lan
3. Use the nsradmin command-line utility to confirm which user account is used for the vCenter reporting login failures in the nsrvisd-daemon.log.
[root@nsr ~]# nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> p type: nsr hypervisor; name: vcsa.amer.lan
type: NSR hypervisor;
name: vcsa.amer.lan;
version: 8.0.2;
comment: ;
service: VMware VirtualCenter;
endpoint: "https://vcsa.amer.lan/sdk";
username: networker_user@vsphere.local;
password: *******;
command: nsrvim;
proxy: nsr.amer.lan;
console events: Yes;
cloud: No;
console cancel: Yes;
Snapshot FreeSpace Warning Threshold: 0;
Snapshot FreeSpace Failure Threshold: 0;
restricted data zone: ;
nsradmin>
4. From a web browser, access the vSphere web client for the vCenter server.
5. Log in to vSphere using the account used to add the vCenter to NetWorker (see step 3).
6. On the NetWorker server, update the password for the vCenter user account. This can be done using nsradmin, or the NetWorker Web User Interface.
nsradmin method:
A. On the NetWorker server, open and Administrator command prompt, or root shell.B. Run:
nsradmin
C. From the
nsradmin command prompt, set the type to the vCenter resource:
. type: nsr hypervisor; name: vCenter_Name
print type: nsr hypervisor
update password: Correct_PasswordExample:
[root@nsr ~]# nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> . type: nsr hypervisor; name: vcsa.amer.lan
Current query set
nsradmin> update password: !Password1
password: *******;
Update? y
updated resource id 198.0.90.20.0.0.0.0.196.80.99.102.192.168.9.150(3983)
nsradmin>
NWUI method:
A. Log in to the NetWorker Web User Interface (NWUI) for the NetWorker server: https://NetWorker_Address:9090/nwuiB. Go to Protection->VMware vCenters.
C. Select the vCenter reporting authentication errors.
E. Update the Password and click Save.
7. Once credentials have been corrected for each vCenter previously reporting login failures, launch the NMC and attempt to connect to the NetWorker server.