Access the Administrator Console

1. Update the host file on the machine used to access the Administrator console.

   Update the /etc/hosts file to map the controller Administrator console IP address to the following FQDNs. Each entry must be on a single line — place all FQDNs for the same IP on one line separated by spaces:

   <Controller IP Address> api.local.<tenant-domain> iapi.local.<tenant-domain> login.local.<tenant-domain> portal.local.<tenant-domain> toolkitsessions.local.cgnx.net controller.local.<tenant-domain> ops-ui.prisma-sd-wan.com

   In /etc/hosts, each line must begin with an IP address. All hostnames for a given IP address must appear on a single line, separated by spaces. Placing FQDNs on continuation lines causes DNS resolution failures for those hostnames. Replace <tenant-domain> with your actual tenant domain.
2. Accept the certificate presented by the Administrator console and Operator console.

   If you are not using a CA-signed certificate for the Administrator console, accept (trust) the certificate presented by the Administrator console:

   • Access the URL https://api.local.<tenant-domain>/v2.0/api/login and trust the certificate.
   • Then access the URL https://login.local.<tenant-domain>/sign-in.html.
3. Access the controller Administrator console URL to connect.

   To access the Operator console, open a browser and navigate to:

   https://ops-ui.prisma-sd-wan.com:9443

   The Operator console displays information on host system utilization such as CPU, memory, and storage. You can view the current controller version, the tenant ID, and the backup configuration on the dashboard.

   If you have a multiple node HA deployment, the Operator console displays information on all the 9 nodes.