Enable the SP/BMC automatic network configuration
Enabling the SP to use automatic network configuration is preferred over manually configuring the SP network. Because the SP automatic network configuration is cluster wide, you do not need to manually manage the SP network for individual nodes.
This task applies to both the SP and the BMC.
The subnet you want to use for the SP automatic network configuration must already be defined in the cluster and must have no resource conflicts with the SP network interface.
network subnet showcommand displays subnet information for the cluster.
The parameter that forces subnet association (the
-force-update-lif-associationsparameter of the
network subnetcommands) is supported only on network LIFs and not on the SP network interface.
If you want to use IPv6 connections for the SP, IPv6 must already be configured and enabled for ONTAP.
network options ipv6 showcommand displays the current state of IPv6 settings for ONTAP.
Specify the IPv4 or IPv6 address family and name for the subnet that you want the SP to use by using the
system service-processor network auto-configuration enablecommand.
Display the SP automatic network configuration by using the
system service-processor network auto-configuration showcommand.
If you subsequently want to disable or reenable the SP IPv4 or IPv6 network interface for all nodes that are in quorum, use the
system service-processor network modifycommand with the
When the SP automatic network configuration is enabled, you cannot modify the SP IP address for a node that is in quorum. You can only enable or disable the SP IPv4 or IPv6 network interface.
If a node is out of quorum, you can modify the node’s SP network configuration, including the SP IP address, by running
system service-processor network modifyfrom the node and confirming that you want to override the SP automatic network configuration for the node. However, when the node joins the quorum, the SP automatic reconfiguration takes place for the node based on the specified subnet.