Feedback requested for Virtual Storage Console 2.0 Users

[robertim]

We're looking for feedback from  customers that have downloaded Virtual Storage Console and are using it. Any and all comments and feedback welcome.

[amritad]

You can try installing it on another VM and check while registering give your vCenter details.

. I’m wondering if it’s because the vCenter server is loaded.

Regards

Amrita

[stefan_pietsch]

Hmm, I just checked the event logs on the server.

Since the installation we're getting these warnings and errors from SMVI every 30 minutes (event ID 4096).

I'm not sure if this is the reason why the vSphere clients hang, but I'll uninstall it and install it somewhere else again...

Kind regards,

Stefan

#######################################################################################

111760769 [btpool0-1] WARN com.netapp.common.credentials.FileCredentialPersistenceManager - CPM-00305: Persistence file C:\Program Files\NetApp\Virtual Storage Console\smvi\server\etc\cred does not exist.

113560778 [btpool0-1] ERROR 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.<init>(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)

[raimiansch]

Hi Together!

Every night I create backups with the CLI "smvi.bat backup create -id NSC-OA-01 -id NSC-OA-02 -backup-name DMS_daily". The backup works fine but in the event log some times i received a similar message like stefan.

Thanks for your helps.

Rainer

985801399 [btpool0-178] ERROR 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.<init>(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)

[amritad]

Hi

Do you see this error with just the cli or wven when you use the UI?

REgards

Amrita

[raimiansch]

Hi Amrita!

Thanks for your fast response.

Yes, it seems, that this error messages only occure with CLI.

Regards

Rainer

[amritad]

Hi

Wondering why that is happening. Does the backup go through fine? And can you restore from the backup?

Regards

Amrita

[raimiansch]

That strange ...

Also between 0 and 1 am in the morning i make in summary 10 Backups with smvi.bat (CLI). And within this time, there are some messages in the event log.

Now I restored one VM from one of this backups and it works fine.

But today at 11:30 I have also this error message in the event log but nobody did anything at this time. We had an backup with the CLI but it was ready at 11:27. And my restore was on 11:52.

[amritad]

Wonder why this behavior is happening. We need to check if everyone is running into this issue.

Regards

Amrita

[raimiansch]

I could be that this error messages (com.netapp.smvi.security.authentication.vsphere.VSphereAuthenticator - Failed to authenticate vSphere sessionId) has nothing todo with the backup jobs. Because now I have filterd out this messages and this messages happens every 30 minutes excatly each hour and half an hour. And this every time also at a time where no actions occurs with the smvi.

[jimrmclean]

We see these errors in the event logs as well.  Does not appear to affect backup/restore functionality; haven't tried provisioning yet.  Just annoying and filling up the event logs...

[amritad]

Could one of you log a support case for this? Just to get to the root cause of this issue.

Regards

Amrita

[raimiansch]

I have opened a case for this. I will post the result here.

[martialalmac1]

Hi, I'm experiencing the exact same error message in the event logs every 30 minutes. Has anyone else got to the bottom of this error?

Thanks.

[jangelmo_fujitsu]

Do we have any update on this? I have a user with the same problem.

[jmalghem2009]

I have exactly the same problem with version 2.0.1 and vSphere ESX 4.0 and 4.1 with vCenter 4.1 on a customer installation.

Any update will be greatly appreciated.

Thanks,

Julien

[skuebart]

Hi all,

I am working together with the customer to implement VSC 2.0.1P1 on his vCenter-Server but VSC is not running well. After the installation we were able to scan his environment and to set up the FAS controllers in the RCU-section "provisioning and cloning". But when we try to add the storage controllers in SMVI, we receive the error "Could not log onto the storage system <storagename> with the provided credentials". We are yousing the exact same logon credentials like within the general VSC and the specific RCU-setup.

After a reboot of the vCenter-Server the customer receives following error logs (please apologize that it's German :)):

Protokollname: Application

Quelle:        SMVI

Datum:         22.02.2011 17:32:31

Ereignis-ID:   4096

Aufgabenkategorie:(4)

Ebene:         Warnung

Schlüsselwörter:Klassisch

Benutzer:      Nicht zutreffend

Computer:      V6300ARV.de.arag.net

Beschreibung:

2652503 [btpool0-2] WARN com.netapp.common.credentials.FileCredentialPersistenceManager - CPM-00305: Persistence file C:\Program Files\NetApp\Virtual Storage Console\smvi\server\etc\cred does not exist.

Ereignis-XML:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="SMVI" />

    <EventID Qualifiers="0">4096</EventID>

    <Level>3</Level>

    <Task>4</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2011-02-22T16:32:31.000000000Z" />

    <EventRecordID>2248</EventRecordID>

    <Channel>Application</Channel>

    <Computer>V6300ARV.de.arag.net</Computer>

    <Security />

  </System>

  <EventData>

    <Data>2652503 [btpool0-2] WARN com.netapp.common.credentials.FileCredentialPersistenceManager - CPM-00305: Persistence file C:\Program Files\NetApp\Virtual Storage Console\smvi\server\etc\cred does not exist.

</Data>

  </EventData>

</Event>

Protokollname: Application

Quelle:        SMVI

Datum:         22.02.2011 17:32:56

Ereignis-ID:   4096

Aufgabenkategorie:(5)

Ebene:         Fehler

Schlüsselwörter:Klassisch

Benutzer:      Nicht zutreffend

Computer:      V6300ARV.de.arag.net

Beschreibung:

2678268 [admin0 7d85f20f210609b79f17b76e82e6339b] ERROR com.netapp.smvi.task.credential.CredStorageSystemAddAction - Could not log onto the storage system so020arv.de.arag.net with the provided credentials.

Ereignis-XML:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="SMVI" />

    <EventID Qualifiers="0">4096</EventID>

    <Level>2</Level>

    <Task>5</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2011-02-22T16:32:56.000000000Z" />

    <EventRecordID>2253</EventRecordID>

    <Channel>Application</Channel>

    <Computer>V6300ARV.de.arag.net</Computer>

    <Security />

  </System>

  <EventData>

    <Data>2678268 [admin0 7d85f20f210609b79f17b76e82e6339b] ERROR com.netapp.smvi.task.credential.CredStorageSystemAddAction - Could not log onto the storage system so020arv.de.arag.net with the provided credentials.

</Data>

  </EventData>

</Event>

Any ideas for solving the problem are more than welcome!

Thank you in advance and many regards,

Sascha

[imarcroft]

I know there has been some mention of this in posts above.

I have had the problem where VSC 2.0.1P1 when it detects the controllers of the 3140 is picks up the E0m port, even amending xml files doesn't seem to change this behaviour

the only way I could fix it was to remove VSC disable E0m ports and reinstall and perform a rediscover

[imarcroft]

Also as an addition to this, everytime you perform an update to rediscover new ESX hosts you need to disable the E0M port or it will rediscover it.

[raimiansch]

I have a question about backup of VMs with iSCSI luns.

I have a windows 2003 VM with 3 vmdk disk and 10 iSCSI disk mapped over snapdrive for windows. All related volumes - datastore, volume for iSCSI luns - are placed in a vfiler.

When I now make a backup with the svc the tool make an snapshot of all volumes containing iSCSI luns and present this luns to the server.

But for what?

The svc says, that the backup was successfully created, but the svc has mapped all 10 luns to the server but only unmapped 4 luns. That means currently I have mapped 6 luns of the created snapshot to the server.

After all when I delete the backup on the svc it will only delete the snapshot of the datastore volume and from the svc database. But the snapshots of the iscsi volumes and the volume clones will reside on the filer an. And also the mapping to the server.

Have anybode else this phenomenon?

Thanks for your response.

Rainer

[ryan_benigno]

As was already mentioned, SM-VI really needs the ability to disable VM snapshots for individual VM's on a data store.  With VIBE I was able to do this, but when we moved to SM-VI it was necessary to create a separate set of data stores for VM's that don't work with VM consistent snapshots, and a 2nd set of backup jobs.  It was frustrating to adjust operational policies and system design because a seemingly basic feature is missing.

+1 on discovery issues in VSC - it simply doesn't work very well.  I have a site with NFS data stores (no block), and had to create a dummy iSCSI data store on each controller and present those to the ESX cluster for VSC discovery to work.

[HendersonD]

I agree with Ryan. In our case I did not create a separate data store I just created two jobs, one where vmware snapshots are taken and one where they are not. The problem is we are taking a filer snapshot on the same datastore twice. We have an NFS datastore and discovery with vsc 2.0.1 worked fine