Skip to main content
A newer release of this product is available.

security config status show

Contributors
Suggest changes

(DEPRECATED)-Display Security Configuration Status

Availability: This command is available to cluster administrators at the advanced privilege level.

Description

Note This command has been deprecated as of 9.9 and may be removed in a future release of Data ONTAP. Reboot is no longer required to apply the security configuration, so it now always displays false.
The `security config status show` command displays the required reboot status of the nodes in the cluster after security configuration settings have been modified using the link:security-config-modify.html[security config modify] command. Use this command to monitor the status of the required reboot process. When all nodes have rebooted, the cluster is ready to use the new security configuration settings.

Parameters

{ [-fields <fieldname>,…​]

If you specify the -fields <fieldname>, …​ parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-instance ] }

If you specify the -instance parameter, the command displays detailed information about all fields.

[-node {<nodename>|local}] - Node Name (privilege: advanced)

Select the node whose reboot-status you want to display.

[-reboot-needed {true|false}] - Reboot Needed (privilege: advanced)

reboot-needed status of the node that tells if the node requires a reboot for security configuration to take effect.

Examples

The following example displays the status of a configuration change in a four-node cluster.

cluster1::> security config status show
Nodes in Cluster      Reboot Needed
--------------------- -------------------
node1                 true
node2                 true
node3                 false
node4                 false
4 entries were displayed.

The following example shows the output of the command after the cluster reboot process is complete.

cluster1::> security config status show
Nodes in Cluster      Reboot Needed
--------------------- -------------------
node1                 false
node2                 false
node3                 false
node4                 false
4 entries were displayed.