What is the login behavior after a DR upgrade reboot? (4039001)

1. Before Upgrade (3.2.1)

   - login user for local console was "administrator"

   - remaining users to web logged in with active directory credentials in form of domain\username or username@domain

2. During Upgrade

   - Logged into DR6000 with credentials (domain\username)

   - Uploaded DR6000 firmware 4.0 into upgrade page in DR6000 web interface

   - Rebooted when prompted

   - After reboot, attempted to login with domain\username, received message along the lines of "not in logon group"

   - Tried logging in with user "administrator" with password that worked for admin before, refused.

   - Tried logging in with user "administrator" with default password as specified in release notes, refused.

   - During this time NetVault was reporting its VTL in a CIFS share on DR6000 (accessed via AD credentials) and RDA container were both down.

   - Tried logging in to local console with administrator and the password we had, that worked.

   - Tried logging in with user@domain, it let me in and went through the setup wizard, stating it migrated local user credentials (the RDA backup_user, etc.)

   - Was then able to reset "administrator" to previous password, successfully tested login.

   - Then tested domain\username login and that is suddenly working as well

R&D attempted to reproduce the reported problem and was unsuccessful, the system credential access responded as expected during the upgrading staging updates.

When the DR is rebooted (say after an upgrade) it normally takes about 4 to 5 minutes for all services to be up. When the web server starts running we can see the DR GUI login page. At this time the local “administrator” user is allowed to login with the existing password. If default password is changed the changed password has to be used. The user credentials are validated immediately (meaning it is not dependent on access to domain or domain authentication services to be up.) If we login within a minute or two after the reboot using the local administrator user, upon successful login the page shows “Initializing…” until all services are up.

If we try to login using domain user (like <domain name>\<username>) before the domain authentication client services are up, we see the message – “Login Group not defined or Active Directory Client not yet up.”

Their observations support the assessment the system was probably still in the process of syncing the updates and the credentials unexpected took more time to reestablish access to the Web GUI.  

If this behavior because repetitive or no login is granted, please open a SR.