Forum Discussion

CadenL's avatar
CadenL
Level 6
9 years ago

NetBackup Appliance CallHome fails after upgrade to 2.6.1.2

Having just completed a NetBackup Upgrade on 2 x 5230 Appliance (Previous version is 2.6.0.3 and target version is 2.6.1.2) we've noticed the call home feature no longer works - it was working ok prior to the upgrade.

We receive an error when trying to enable the Proxy server saying

'Not able to upload call home data error while CONNECT thru proxy: 407 Proxy Authentication Required at /opt/NBUAppliance/scripts/LWP/Protocal/connect/Socket/Base.pm line 41'

We have applied EEB from https://www.veritas.com/support/en_US/article.TECH228989.html with no benefit and are confident we have the correct username and password.

If we run the "export HTTP_PROXY=http://proxy.domain.com:8000/" command followed by the "w3m https://www.symappmon.com" we seem to be able to connect and get prompted for credentials. Veritas have sent us the new urls for this but we get the same error and feel this isn't simply a case of changing the URLs.

Any one had similar issues following an upgrade?

many thanks 

  • I am not sure but this may be down to the new authentication standards required by 2.6.1.2 as it also causes other issues.

    Unfortunately it doesn't ask you to change the password for the appliance at any point, even though it needs it to be more complex than it was before.

    You may want to change the admin password to a complex one and then try again .. a similar thing happens with logs shares etc stopping working

  • Thanks for the thoughts

    I don't know if the admin password is associated with this issue - but then I'm not sure where the issue is anway. The call home works fine if I configure the Appliance with direct Internet access and only errors when I try to configure it through our proxy server. I've tried different proxy passwords (all with complex passwords) but still nothing and the proxy account it was using before the upgrade also had a complex password - it only stopped working after the upgade as I specifically tested it moments before the commencing the upgrade and then again immediately afterwards.

    I'm pretty sure it's not using the admin password when trying to connect to the Proxy server so (theoretically) setting this to a complex password may not make any difference.

    Anyway I've logged a support call and Veritas are working on it.

    thanks again

  • No more update for this yet. I've an open call with support who have been working on it for a couple of weeks now. I'll post the resolution once veritas have made some progress. Thanks