Skip to main content

Accessing the SP/BMC

A cluster user account that is configured with the service-processor application type can access the SP from an administration host (using an SSH connection) or the serial console. ONTAP enables you to restrict SSH access of the SP to only the administration hosts with specific IP addresses.

Note
This topic applies to both the SP and the BMC.

The system timeout commands manage the settings for the automatic timeout period of CLI sessions, including console and SSH connections to the SP.

  • Accounts that can access the SP
    When you try to access the SP, you are prompted for credential. Cluster user accounts that are created with the service-processor application type have access to the SP CLI on any node of the cluster. SP user accounts are managed from ONTAP and authenticated by password.
  • Accessing the SP/BMC from an administration host
    You can log in to the SP of a node from an administration host to perform node management tasks remotely.
  • Accessing the SP/BMC from the system console
    You can access the SP from the system console (also called serial console) to perform monitoring or troubleshooting tasks.
  • Relationship among the SP CLI, SP console, and system console sessions
    You can open an SP CLI session to manage a node remotely and open a separate SP console session to access the console of the node. The SP console session mirrors output displayed in a concurrent system console session. The SP and the system console have independent shell environments with independent login authentication.
  • Managing the IP addresses that can access the SP
    By default, the SP accepts SSH connection requests from administration hosts of any IP addresses. You can configure the SP to accept SSH connection requests from only the administration hosts that have the IP addresses you specify. The changes you make apply to SSH access to the SP of any nodes in the cluster.