VSC 2.1.1 - Failed to authenticate vSphere sessionId

[fletch2007]

Our vCenter (v5)  on ONTAP 7.3.5.1P2 is logging these every 30 minutes and its blowing up our daily vCheck report - its puzzling since the plugin seems to have working authentication (we see vFiler datastores and hosts etc) - so what is it complaining about?  I see many folks with this error going back 10 months - As mentioned in this thread before it got locked:

http://communities.netapp.com/thread/10472?start=105&tstart=0

Our errors:

com.netapp.smvi.security.authentication.vsphere.VSphereAuthenticator - Failed to authenticate vSphere sessionId %s com.vmware.vim.InvalidLoginFaultMsg    at com.netapp.smvi.VimClient.createUserSession(VimClient.java:195)    at com.netapp.smvi.VimClient.validateLogin(VimClient.java:131)    at com.netapp.smvi.VimClient.(VimClient.java:74)    at com.netapp.smvi.VimClientFactory.getVimClient(VimClientFactory.java:105)    at com.netapp.smvi.security.authentication.vsphere.VSphereAuthenticator.isValidSession(VSphereAuthenticator.java:44) at com.netapp.smvi.security.authentication.handler.VSphereAuthenticationHandler.authenticate(VSphereAuthenticationHandler.java:27) at com.netapp.smvi.security.authentication.AuthenticationChainManager.authenticate(AuthenticationChainManager.java:39) at com.netapp.smvi.security.PasswordHandler.handle(PasswordHandler.java:75)    at org.apache.ws.security.processor.UsernameTokenProcessor.handleUsernameToken(UsernameTokenProcessor.java:160) at org.apache.ws.security.processor.UsernameTokenProcessor.handleToken(UsernameTokenProcessor.java:56) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:326) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:243) at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:179) at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:66) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:104) at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)    at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:350) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:182)    at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:163)    at org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServlet.java:141)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)    at org.mortbay.jetty.Server.handle(Server.java:324)    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)    at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)    at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)    at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:620) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)

I'd like to keep using the plugin if we can resolve this

thanks

http://vmadmin.info

[johncartier]

I just upgraded to vSphere 5, and see the same errors - every 30 minutes.  The scheduled backups seem to work, and I can see the controllers w/in the NetApp plugin on the vSphere client. We're using NFS for our datastores, and are running ONTAP 7.3.4

[arash]

Hello Guys ;

This is a known issue after upgrading the VSC :

Symptoms

After configuring, upgrading, or sustained use of Backup and Recovery (also known as SMVI) through Virtual Storage Console (VSC), the logs report the following error message every 30 minutes:
Failed to authenticate vSphere sessionId %s

Cause

This is due to missing, invalid, or inaccurate vCenter credentials stored within the backup jobs configured within Backup and Recovery, or the global credentials being used for backups.

Solution

To prevent this error message from appearing, verify the following:

• Global vCenter credentials match RBAC requirements from VSC 2.1 or VSC 2.1.1 (or refer to the document for the appropriate VSC version)
• Each backup job configured within VSC has been set to use 'Default vCenter Credentials'
• The user configured is a local administrator on the local server
• The user configured does not have restrictive permissions within any component of vCenter (vCenter, Datacenter, ESX Cluster, ESX host, Datastores, and so on)
• The user configured does not have a disabled account on the local server or the Active Directory