Solved: VSC login frequency

FULLSTEAM · ‎2013-01-23

The VSC user configured in Backup & Recovery / Setup, is logging into vCenter every 10 seconds.

Is this to be expected? Can it be tuned down so it's not so spamtastic?

Thanks!

(ESXi 5.0 and VSC 4.0)

schrie · ‎2013-01-29

It sounds like the registration process failed during your upgrade - the authentication from VSC is checked each 10seconds, and if it fails or something has changed, it tries to re-register with the vCenter server, which is what is happening in your case - this is by design in that it should be checking, but not by design as in you shouldn't have so many sessions.

I'd recommend completing the registration again - try this:

Log into the VSC server over RDP using an administrator account
Open a web browser and go to https://localhost:8143/Register.html
For troubleshooting purposes, re-register using an administrator account (local)
Make sure you're entering the IP addresses of the vCenter and VSC servers for the registration
Click the register button
Montor the sessions to see if there are still logins each 10seconds (after initial logins are completed)

View solution in original post

schrie · ‎2013-01-29

It sounds like the registration process failed during your upgrade - the authentication from VSC is checked each 10seconds, and if it fails or something has changed, it tries to re-register with the vCenter server, which is what is happening in your case - this is by design in that it should be checking, but not by design as in you shouldn't have so many sessions.

I'd recommend completing the registration again - try this:

Log into the VSC server over RDP using an administrator account
Open a web browser and go to https://localhost:8143/Register.html
For troubleshooting purposes, re-register using an administrator account (local)
Make sure you're entering the IP addresses of the vCenter and VSC servers for the registration
Click the register button
Montor the sessions to see if there are still logins each 10seconds (after initial logins are completed)

FULLSTEAM · ‎2013-02-06

So, while not absolutely the answer, it was enough to put me in the right direction, so, full marks.

The VSC server was properly registered, but someone else had gone through behind the scenes on the AD server and pulled the VSC service account out of the VMware admin group. So, effectively, it wasn't an admin anymore, and here we were.

I really wish there were better privilege definitions for VSC. Like, being able to give an account just enough privs to do its job. The Backup/Recovery defaults to using the admin user to do backups, but, with some research you can find that SMVI only needs a subset of privs, and you can define a role just for it. But then you have to set that user on every backup job. That's probably another bug.

Anyway! Thanks for the pointer.

kboyle · ‎2013-02-06

"I really wish there were better privilege definitions for VSC."

Stay Tuned! VSC 4.2 is coming and has Role Based Access Control!

FULLSTEAM · ‎2013-02-06

Awesome. I'll take four copies, some new docs, and glazed doughnut. To go.

kboyle · ‎2013-02-07

Would you like fries with that? <wink>

FURMANITEWW · ‎2013-09-04

Schrie,

We are currently running VSC 4.2 with ONTAP 8.2P2 on cCenter 5.1 and we are running into the same issue. I have done your recommendation and still no luck.

Any other suggestions?

Thanks,

IT

schrie · ‎2013-09-05

Lets go ahead and start a new thread for you IT, it sounds like you might be having a different problem. If we can't figure it out over the new thread, we'll just get you to open a new support case and work through reviewing the logs in more depth to find the RCA