Subscribe

SMVI used wrong account

Hi,

 

we are running VSC6.2.1 with VSphere 5.5.

 

Authentication on cDot 9.1 is changed to AD and it work fine.

In SMVI, the authentication for the filers is set to a AD account. 

 

It works for 95% of the backup jobs.

 

The remaining 5% are still using the old local user "esxbackup" as it was configured before.

 

Sun Apr 02 2017 20:22:46 +02:00 [kern_audit:info:1732] cluster50:ontapi ::  cluster50_svm7:esxbackup :: <netapp xmlns="http://www.netapp.com/filer/admin" [...]
Sun Apr 02 2017 20:22:55 +02:00 [kern_audit:info:1732] cluster50:ontapi ::  cluster50_svm7:esxbackup :: snapshot-create :: Success

I recreated the backupjobs to make sure that it not does contain old info.

 

No change of behaviour.

 

I found the following in the smvi\wrapper.log

 

INFO   | jvm 1    | 2017/03/30 15:22:57 | com.netapp.autozapi.client.ApiAuthenticationException: Authentication to Storage System cluster50_node1 as user esxbackup failed.  Response code: 401
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.autozapi.client.ZapiInvocation.processResponse(ZapiInvocation.java:248)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.autozapi.client.ZapiInvocation.invoke(ZapiInvocation.java:116)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.autozapi.client.XmlZapiInvocation.invoke(XmlZapiInvocation.java:40)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.autozapi.client.ZapiRunner.run(ZapiRunner.java:151)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.autozapi.client.ZapiRunner.run(ZapiRunner.java:121)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.common.zapi.SmviZapiRunner.run(SmviZapiRunner.java:67)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.smvi.zapi.CServerTarget.populateNodeVServers(CServerTarget.java:155)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.smvi.zapi.CServerTarget.refresh(CServerTarget.java:70)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.smvi.zapi.ZAPIExecutorFactory$RefreshThread.doRefresh(ZAPIExecutorFactory.java:617)
INFO   | jvm 1    | 2017/03/30 15:22:57 | 	at com.netapp.smvi.zapi.ZAPIExecutorFactory$RefreshThread.run(ZAPIExecutorFactory.java:576)

INFO   | jvm 1    | 2017/03/30 15:22:43 | com.netapp.autozapi.client.ApiAuthenticationException: Authentication to Storage System cluster50 as user esxbackup failed.  Response code: 401
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.autozapi.client.ZapiInvocation.processResponse(ZapiInvocation.java:248)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.autozapi.client.ZapiInvocation.invoke(ZapiInvocation.java:116)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.autozapi.client.XmlZapiInvocation.invoke(XmlZapiInvocation.java:40)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.autozapi.client.ZapiRunner.run(ZapiRunner.java:151)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.autozapi.client.ZapiRunner.run(ZapiRunner.java:121)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.common.zapi.SmviZapiRunner.run(SmviZapiRunner.java:67)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.smvi.zapi.CServerTarget.populateNodeVServers(CServerTarget.java:155)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.smvi.zapi.CServerTarget.refresh(CServerTarget.java:70)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.smvi.zapi.ZAPIExecutorFactory$RefreshThread.doRefresh(ZAPIExecutorFactory.java:617)
INFO   | jvm 1    | 2017/03/30 15:22:43 | 	at com.netapp.smvi.zapi.ZAPIExecutorFactory$RefreshThread.run(ZAPIExecutorFactory.java:576)

Then I added the local "esxbackup" account to the cluster50:

 

INFO   | jvm 1    | 2017/03/30 19:35:39 | DEBUG: setDebug: JavaMail version 1.4.1
INFO   | jvm 1    | 2017/03/30 20:50:57 | DEBUG: setDebug: JavaMail version 1.4.1
INFO   | jvm 1    | 2017/03/30 21:18:32 | DEBUG: setDebug: JavaMail version 1.4.1
INFO   | jvm 1    | 2017/03/30 22:30:31 | DEBUG: setDebug: JavaMail version 1.4.1
INFO   | jvm 1    | 2017/03/30 22:55:40 | DEBUG: setDebug: JavaMail version 1.4.1
INFO   | jvm 1    | 2017/03/30 23:10:45 | DEBUG: setDebug: JavaMail version 1.4.1

The errors are gone!

 

How can I remove the remaining local accounts? Where are they hidden?

 

Marcus

Re: SMVI used wrong account

The weird thing with those authentication errors, is that they are (as the name seems to indicate) for either cluster or node connections, not SVM's are seen earlier.

How did you configure your storage systems in VSC configuration, for SVM or cluster?

 

Besides that the only place I know VSC/SMVI has some bespoke configuration, would be in the override.smvi file (hidden) in the smvi subdirectory of VSC.

 

/Xander