Logging in to SnapCenter

SnapCenter supports role-based access control (RBAC). SnapCenter admin assigns roles and resources through SnapCenter RBAC to either a user in workgroup or active directory, or to groups in active directory. The RBAC user can now log in to SnapCenter with the assigned roles.

Before you begin

You should enable Windows Process Activation Service (WAS) in Windows Server Manager.
If you want to use Internet Explorer as the browser to log in to the SnapCenter Server, you should ensure that the Protected Mode in Internet Explorer is disabled.

About this task

During installation, the SnapCenter Server Install wizard creates a shortcut and places it on the desktop and in the Start menu of the host where SnapCenter is installed. Additionally, at the end of the installation, the Install wizard displays the SnapCenter URL based on the information that you provided during installation, which you can copy if you want to log in from a remote system.

Attention: If you have multiple tabs open in your web browser, closing just the SnapCenter browser tab does not log you out of SnapCenter. To end your connection with SnapCenter, you must log out of SnapCenter either by clicking the Sign out button, or by closing the entire web browser.

Best Practice: For security reasons, it is recommended that you do not enable your browser to save your SnapCenter password.

The default GUI URL is a secure connection to the default port 8146 on the server where the SnapCenter Server is installed (https://server:8146). If you provided a different server port during the SnapCenter installation, that port is used instead.

For Network Load Balance (NLB) deployment, you must access SnapCenter using the NLB cluster IP (https://NLB_Cluster_IP:8146). If you do not see the SnapCenter UI when you navigate to https://NLB_Cluster_IP:8146 in Internet Explorer (IE), you must add the NLB IP address as a trusted site in IE on each plug-in host, or you must disable IE Enhanced Security on each plug-in host.

SnapCenter in an HA configuration with Application Request Routing (ARR) enabled exhibits backup jobs in a perpetually 'running' state.

In addition to using the SnapCenter GUI, you can use PowerShell cmdlets to create scripts to perform configuration, backup, and restore operations. Some cmdlets might have changed with each SnapCenter release. The SnapCenter cmdlet or SnapCenter CLI documentation has the details.

Note: If you are logging in to SnapCenter for the first time, you must log in using the credentials that you provided during the install process.

Procedure

Launch SnapCenter from the shortcut located on your local host desktop, or from the URL provided at the end of the installation, or from the URL provided by your SnapCenter administrator.

Enter user credentials.

To specify the following...	Use one of these formats...
Domain administrator	`NetBIOS\UserName` `UserName@UPN suffix` For example, username@netapp.com `Domain FQDN\UserName`
Local administrator	`UserName`

To specify the following...

Use one of these formats...

Domain administrator

NetBIOS\UserName

UserName@UPN suffix For example, username@netapp.com

Domain FQDN\UserName

Local administrator

UserName

If you are assigned more than one role, from the Role box, select the role that you want to use for this login session.
Your current user and associated role are shown in the upper right of SnapCenter after you are logged in.

Result

If you are using SnapCenter for the first time, the Storage Systems page is displayed, and the Get Started pane is expanded.

If the logging fails with the error that site cannot be reached, you should map the SSL certificate to SnapCenter.

Site cannot be reached

After logging to SnapCenter Server for the first time, the SnapCenter Server Configuration Checker schedule is created. The default values are Weekly and Every Sunday at 11:59 pm. To modify the schedule or run the SnapCenter Server schedule, click Settings > Scheduled Configuration Checker.

After you finish

If you have untrusted Active Directory domains that you want SnapCenter to support, you must register those domains with SnapCenter before configuring the roles for the users on untrusted domains. The administration documentation has more details.

Performing administrative tasks