Skip to main content

Managing nodes

A node is a controller in a cluster. You can display information about a node, set node attributes, rename a node, add or remove a node, or start or stop a node. You can also manage a node remotely by using the Service Processor (SP).

A node is connected to other nodes in the cluster over a cluster network. It is also connected to the disk shelves that provide physical storage for the ONTAP system to use. Services and components that are controlled by the node, not by the cluster, can be managed by using the system node commands.

A node SVM represents a node in the cluster. If you run the vserver show command, the output includes node SVMs in the list.

  • Displaying node attributes
    You can display the attributes of one or more nodes in the cluster, for example, the name, owner, location, model number, serial number, how long the node has been running, health state, and eligibility to participate in a cluster.
  • Modifying node attributes
    You can modify the attributes of a node as required. The attributes that you can modify include the node's owner information, location information, asset tag, and eligibility to participate in the cluster.
  • Renaming a node
    You can change a node's name as required.
  • Adding nodes to the cluster
    After a cluster is created, you can expand it by adding nodes to it. You add only one node at a time.
  • Removing nodes from the cluster
    You can remove unwanted nodes from a cluster, one node at a time. After you remove a node, you must also remove its failover partner. If you are removing a node, then its data becomes inaccessible or erased.
  • Accessing a node's log, core dump, and MIB files by using a web browser
    The Service Processor Infrastructure ( spi ) web service is enabled by default to enable a web browser to access the log, core dump, and MIB files of a node in the cluster. The files remain accessible even when the node is down, provided that the node is taken over by its partner.
  • Accessing the system console of a node
    If a node is hanging at the boot menu or the boot environment prompt, you can access it only through the system console (also called the serial console). You can access the system console of a node from an SSH connection to the node's SP or to the cluster.
  • Rules governing node root volumes and root aggregates
    A node's root volume contains special directories and files for that node. The root aggregate contains the root volume. A few rules govern a node's root volume and root aggregate.
  • Starting or stopping a node
    You might need to start or stop a node for maintenance or troubleshooting reasons. You can do so from the ONTAP CLI, the boot environment prompt, or the SP CLI.
  • Managing a node by using the boot menu
    You can use the boot menu to correct configuration problems on a node, reset the admin password, initialize disks, reset the node configuration, and restore the node configuration information back to the boot device.
  • Managing a node remotely using the SP/BMC
    You can manage a node remotely using an onboard controller, called a Service Processor (SP) or Baseboard Management Controller (BMC). This remote management controller is included in all current platform models. The controller stays operational regardless of the operating state of the node.