Administrating the Controller Remotely

Manage and monitor the controller from remote locations using secure access methods. This includes performing configuration changes, troubleshooting, and routine maintenance without requiring physical access to the system.
  1. Using controller (SmartZone) management IP address, user can SSH and login to CLI console.
    For example, ssh admin@<SZ management IP>

    SSH User Authentication

    Logging into CLI

    The following algorithms are supported for SSHv2 by SZ controller:

    1. Encryption Algorithms (client): aes128-ctr, aes256-ctr, aes256-gcm@openssh.com
    2. Encryption Algorithms (server): aes128-ctr, aes256-ctr, aes256-gcm@openssh.com
    3. Host Key Algorithms (client): rsa-sha2-256, rsa-sha2-512, ecdsa-sha2-nistp384
    4. Host Key Algorithms (server): rsa-sha2-512, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384
    5. Public Key Algorithms (client): rsa-sha2-512
    6. Public Key Algorithms (server): ssh-rsa, rsa-sha2-256, rsa-sha2-512, ecdsa-sha2-nistp384
    7. Data Integrity/MAC algorithms (client): hmac-sha2-256, hmac-sha2-512
    8. Data Integrity / MAC algorithms (server): hmac-sha2-256, hmac-sha2-512
    9. Key Exchange Methods (client): ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521
    10. Key Exchange Algorithms (server): ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521
    Note: Per the Protection Profile (PP), 'implicit' is included for aes256-gcm@openssh.com as the encryption algorithm. When aes256-gcm@openssh.com is negotiated, the MAC algorithm field is ignored, and GCM is implicitly used as the MAC. "implicit" is not an SSH algorithm identifier and is not transmitted on the wire; however, the negotiated MAC might be decoded as "implicit".

    Note: If the SSH connection is broken then it can be manually re-established.
  2. Enter the IP address https://MGMT-INTERFACE-IP:8443 in the browser to access the controller Web UI.

    Log In Using Web User Interface

    Specific configuration is not required to access the SSH and Web UI session, its enabled by default. The controller provides remote administration of the system through secure communication channel (Web UI via HTTPS and CLI via SSH) . Accordingly, TLS version 1.2 is supported and the following cipher suites are supported for TLS/HTTPS:
    1. ECDHE-RSA-AES128-GCM-SHA256
    2. ECDHE-RSA-AES256-GCM-SHA384
    3. ECDHE-ECDSA-AES128-GCM-SHA256
    4. ECDHE-ECDSA-AES256-GCM-SHA384
    Note: If the HTTPS/ Web UI connection is broken due to any issues then it can be manually re-established.
    Note: Wireless clients connecting to a managed AP are communicating on the TOE's data channel and not via the management interface and therefore, cannot perform remote administration of the SZ.

    TLS/HTTPS supports the ECDHE - secp384r1 key exchange.