After installing Super Tuesday updates on my servers, my VBA backups are all failing with "Unable to connect to VBA emc-ba.it.endgames.local, error Cannot establish session to VBA." And that's literally it. I go to the logs for that job and that's also all it says. All backups were working so, there's really not much else it could be. There is not firewall between networker and the VBA or the ESXi server. When I snoop the connection through WireShark, I see traffic between the two on port 8543, so I'm rather mystified here. I'm in the process of reviewing all the updates to see what might be likely, but I'm hoping someone may have already seen and resolved this, even though I didn't see anything in the forum.
This is Networker 8.1.3 on Windows 2012 with VBA version1.0.3.6.
Really, really surprised this isn't a bigger thing on this community, but in the event someone else comes across it, here's the answer. You can either unininstall KB3061518 or apply the below registry hack.
Modify the windows registry to enable the proper protocols by default. A KB for this procedure is being written by Mahesh.
NOTE: It is highly recommended to backup registry before following this process
Everytime I try to open that link, either by clicking on your link or searching through the portal, I get a salesforce.com error. I get this a lot through the EMC portal.
Login Error Your login attempt using single sign-on with an identity provider certificate has failed. Please contact your salesforce.com administrator for more information.
Well, I'd love to do that, except the cert on this appliance is STILL insecure and now after the hotfixes, even IE won't connect to it. I've tried FF, Chrome, safari, and IE and none of them will connect to the appliance due to an insecure cert.
The NetWorker VMware Protection integration is configured in the environment and scheduled backups were working successfully. The policies started encountering a failed state and the policy message shows:
Unable to connect to VBA [EBR_APPLIANCE], error Cannot establish session to VBA.
When you log into the EMC Backup & Recovery (EBR) Virtual Backup Appliance the "dpnctl status" command indicates that the mcs service is down. The EBR web configuration screen only shows that the backup scheduler service is down. Attempting to start the mcs service with "dpnctl start mcs" fails to properly start the mcs service.
The dpnctl.log, under the /usr/local/avamar/var/log/ directory, shows:
YYYY/MM/DD-HH:MM:SS Starting Administrator Server... YYYY/MM/DD-HH:MM:SS Started YYYY/MM/DD-HH:MM:SS Caught Fault - YYYY/MM/DD-HH:MM:SS Type : com.vmware.vim25.InvalidLogin YYYY/MM/DD-HH:MM:SS Actor : null YYYY/MM/DD-HH:MM:SS Code : null YYYY/MM/DD-HH:MM:SS Reason : Cannot complete login due to an incorrect user name or password. YYYY/MM/DD-HH:MM:SS Fault String : Cannot complete login due to an incorrect user name or password. YYYY/MM/DD-HH:MM:SS Exception running : VMWare YYYY/MM/DD-HH:MM:SS - - - - - - - - - - - - - - - END YYYY/MM/DD-HH:MM:SS dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" -exit status 1
Resolution
Update the vCenter registration information under the EBR configuration screen. If the vCenter server registration fails to save with the SSO username and password, ensure the password has not expired. If expired, update the SSO password via the vSphere Web client interface. Once the vCenter registration information is updated, the EBR appliance needs to be restarted.
Alright, I found a desktop with an unpatched IE and got into the admin interface. But this did not fix the issue. I updated both the VMWare and NetWorker configs.
patrickt333
34 Posts
2561
1
Posted May 15th, 2015 12:00
Really, really surprised this isn't a bigger thing on this community, but in the event someone else comes across it, here's the answer. You can either unininstall KB3061518 or apply the below registry hack.
Modify the windows registry to enable the proper protocols by default. A KB for this procedure is being written by Mahesh.
NOTE: It is highly recommended to backup registry before following this process
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
"DisabledByDefault"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
NOTE: The ‘SSL 2.0’ is set to default of disabled by above and all other Keys under ‘Protocols’ will be overwritten