Commands: Manual Page Reference - Fujitsu€¦ · cluster show.....70 cluster contact-info...

FUJITSU Storage ETERNUS AX series All-Flash Arrays, ETERNUS HX series Hybrid Arrays ONTAP 9.8 Commands: Manual Page ReferenceFUJITSU Storage ETERNUS AX series All-Flash Arrays, ETERNUS HX series Hybrid Arrays
P3AG-5962-01ENZ0
autobalance aggregate show-aggregate-state................................................................................................51
autobalance aggregate show-unbalanced-volume-state.................................................................................53
cluster add-node-status............................................................................................................ 59
cluster create............................................................................................................................ 60
cluster show ............................................................................................................................. 70
cluster log-forwarding show ..........................................................................................................................101
event catalog show........................................................................................................................................145
event filter create ..........................................................................................................................................158
event filter delete ..........................................................................................................................................159
job show-completed............................................................................................................... 203
lun delete............................................................................................................................... 230
lun copy cancel ..............................................................................................................................................245
lun copy modify .............................................................................................................................................245
Manage Lun Move Operations................................................................................................ 271
lun move cancel.............................................................................................................................................271
lun move modify............................................................................................................................................272
metrocluster heal ................................................................................................................... 290
metrocluster modify ............................................................................................................... 290
metrocluster remove-dr-group ............................................................................................... 291
metrocluster check config-replication commands..........................................................................................308
network test-path................................................................................................................... 374
network traceroute................................................................................................................. 375
network traceroute6............................................................................................................... 376
network interface check commands...............................................................................................................425
network interface dns-lb-stats commands.....................................................................................................427
network interface failover-groups commands................................................................................................428
network interface lif-weights commands.......................................................................................................432
network qos-marking modify.........................................................................................................................483
18. qos commands................................................................................................. 506 qos adaptive-policy-group commands.................................................................................... 506
qos adaptive-policy-group create...................................................................................................................506
security audit commands ....................................................................................................... 551
security certificate create ...............................................................................................................................554
security key-manager show-key-store ...........................................................................................................616
security key-manager update-passphrase .....................................................................................................616
security key-manager backup commands......................................................................................................617
security key-manager config commands........................................................................................................619
security saml-sp create ..................................................................................................................................682
security saml-sp delete ..................................................................................................................................683
security saml-sp modify .................................................................................................................................684
Security Session Commands ................................................................................................... 686
snaplock log create........................................................................................................................................742
snaplock log delete........................................................................................................................................742
snaplock log modify.......................................................................................................................................743
snapmirror break.................................................................................................................... 750
snapmirror mediator show.............................................................................................................................846
statistics-v1 nfs show-mount .........................................................................................................................865
statistics-v1 nfs show-nlm .............................................................................................................................867
statistics catalog directory ...................................................................................................... 909
statistics catalog counter commands .............................................................................................................909
statistics settings commands.................................................................................................. 960
storage aggregate show-resync-status ........................................................................................................1005
storage disk replace.....................................................................................................................................1079
storage disk set-foreign-lun.........................................................................................................................1081
storage iscsi-initiator disconnect .................................................................................................................1166
storage shelf port commands ......................................................................................................................1238
system controller show ................................................................................................................................1301
system health commands .................................................................................................... 1375
system license add.......................................................................................................................................1388
system license clean-up...............................................................................................................................1388
system license delete...................................................................................................................................1390
system node upgrade-revert commands......................................................................................................1485
system snmp location ..................................................................................................................................1572
system snmp prepare-to-downgrade ...........................................................................................................1572
system snmp show ......................................................................................................................................1573
system snmp community commands...........................................................................................................1573
volume online ...................................................................................................................... 1651
volume prepare-for-revert .................................................................................................... 1652
volume rehost ...................................................................................................................... 1652
volume rename .................................................................................................................... 1653
volume restrict ..................................................................................................................... 1653
volume show ........................................................................................................................ 1654
volume show-footprint ......................................................................................................... 1673
volume efficiency undo................................................................................................................................1718
volume move abort......................................................................................................................................1770
volume reallocation start.............................................................................................................................1830
vserver remove-protocols ..................................................................................................... 1871
vserver cifs prepare-to-downgrade ..............................................................................................................1910
vserver cifs remove-netbios-aliases .............................................................................................................1911
vserver export-policy netgroup commands ..................................................................................................2060
vserver export-policy rule commands ..........................................................................................................2064
vserver fcp commands .......................................................................................................... 2081
vserver iscsi delete.......................................................................................................................................2142
vserver iscsi modify......................................................................................................................................2142
vserver iscsi show.........................................................................................................................................2144
vserver iscsi start..........................................................................................................................................2146
vserver nfs connected-clients commands.....................................................................................................2215
vserver peer transition commands...............................................................................................................2287
Preface
First Edition April 2021
Warning Signs
Warning signs are shown throughout this manual in order to prevent injury to the user and/or material damage. These signs are composed of a symbol and a message describing the recommended level of caution. The following explains the symbol, its level of caution, and its meaning as used in this manual.
This symbol indicates the possibility of serious or fatal injury if the is not used properly.
This symbol indicates the possibility of minor or moderate personal injury, as well as damage to the and/or to other users and their property, if the is not used properly.
Notice Symbols
The following notice symbols are used in this manual:
Indicates information that you need to observe when using the ETERNUS storage system. Make sure to read the information.
Indicates information and suggestions that supplement the descriptions included in this manual.
39 Commands: Manual Page Reference
1. exit
Quit the CLI session
Availability: This command is available to cluster and Vserver administrators at the admin privilege level.
Description
Examples
cluster1::> exit Goodbye
2. history
Show the history of commands for this CLI session
Description
The history command displays the command history of the current CLI session. A numeric ID precedes each command. Use this number with the redo command to re-execute that history item.
Examples
The following example displays the command history of the current CLI session:
cluster1::> history 1 vserver show 2 man volume show 3 volume delete -vserver vs0 -volume temporary2 4 volume modify { -volume temp* } -state offline
cluster1::> redo 3
3. man
Display the online manual pages
Description
The man command displays the manual page of the command you specify. If you do not specify a command, command displays the man page index.
Parameters
[<text>] - Valid CLI command The command for which you'd like to see the manual page. The syntax of the command is the same as the command itself. The man command supports abbreviations and tab completion of the command name.
Examples
The following example displays the manual page for the storage aggregate create command.
cluster1::> man sto aggr cre
That example could also have been fully specified as:
cluster1::> man storage aggregate create
4. redo
Execute a previous command
Description
The redo command re-executes a command that has been executed previously in the current CLI session. Specify a previously run command using:
• A string that matches part of a previous command. For example, if the only volume command you have run is volume show, enter redo vol to re-execute the command.
• The numeric ID of a previous command, as listed by the history command. For example, enter redo 4 to re-execute the fourth command in the history list.
• A negative offset from the end of the history list. For example, enter redo -2 to re-execute the command that you ran two commands ago.
Parameters
[<text>] - String, Event Number, or Negative Offset Use this parameter to specify a string, a numeric ID from the command history, or a negative number that identifies the command to be re-executed.
Examples
The following example re-executes command number 10 in the command history:
cluster1::> redo 10
5. rows
Show/Set the rows for the CLI session
Description
The rows command displays the number of rows that can be displayed in the current CLI session before the interface pauses output. If you do not set this value, it adjusts automatically based on the actual height of your terminal. If the actual height is undefined, the default number of rows is 24. Specify a number to set the number of rows that can be displayed. Setting this value manually disables auto-adjustment. Specify zero (0) to disable pausing.
You can also set this value using the set -rows command.
Parameters
[<integer>] - Number of Rows the Screen Can Display Use this parameter to specify the number of rows your terminal can display.
Examples
The following example displays the current number of rows, then resets the number of rows to 48:
cluster1::> rows 36
cluster1::> rows 48
6. set
Display/Set CLI session settings
Description
Parameters
[-privilege <PrivilegeLevel>] - Privilege Level Use this parameter to specify the privilege level of the command session. Possible values are
• admin - Used for routine system management commands
• advanced - Used for infrequent, dangerous, or complicated commands
• diagnostic - Used for detailed diagnostic commands that are used only by support personnel
[-confirmations {on|off}] - Confirmation Messages Use this parameter with the value on to specify that the interface prompt for confirmation before executing potentially dangerous commands. Use this parameter with the value off to specify that the interface not prompt for confirmation, even before potentially dangerous commands execute. The default setting is on.
[-showallfields {true|false}] - Show All Fields Use this parameter with the value true to specify that the interface display all field columns when displaying tabular output. Use this parameter with the value false to specify that the interface display only selected columns. The default setting is false.
[-showseparator <text>] - Show Separator Use this parameter to specify the characters to use as the field separator. The field separator is used between field columns when -showallfields is set to "true". The separator can be from one to three characters in length. When specifying the separator, enclose it in quotation marks ("). Set the separator to one or more spaces to disable this feature.
[-active-help {true|false}] - Active Help Use this parameter with the value true to specify that pressing the question mark (?) key is sufficient to execute a help request. Use this parameter with the value false to specify that you must press the Return key after the question mark key to execute a help request. The default setting is true.
[-units {auto|raw|B|KB|MB|GB|TB|PB}] - Data Units Use this parameter to specify the default units used when reporting data sizes. Possible values are:
• auto - Auto-scale data size for human-readable output
• raw - Bytes without unit designation
• B - Bytes
• MB - Megabytes (KB x 1024, aka mebibytes)
• GB - Gigabytes (MB x 1024, aka gibibytes)
• TB - Terabytes (GB x 1024, aka tebibytes)
• PB - Petabytes (TB x 1024, aka pebibytes) The default setting is auto.
[-rows <integer>] - Pagination Rows ('0' disables) Use this parameter to specify the number of rows that can be displayed in the current CLI session before the interface pauses output. If you do not set this value, it adjusts automatically based on the actual height of your terminal. If the actual height is undefined, the default number of rows is 24.
Setting this value manually disables auto-adjustment. Specify zero (0) to disable pausing.
You can also set this value using the rows command.
[-vserver <text>] - Default Vserver Use this parameter to specify the name of the Vserver to use as the default value for the -vserver parameter of commands. WARNING: Vserverized commands that only have a single required parameter, which is the <userinput>- vserver<userinput>, allow the Vserver to be specified positionally, without <userinput>- vserver<userinput> preceding it. Due to this, care must be taken when using CLI commands that do not require the <userinput>-vserver<userinput> parameter. For example, using the "vserver nfs delete *" command will ignore the "set -vserver" value as the parser considers the "*" to be the Vserver.
[-node <text>] - Default Node Use this parameter to specify the name of the node to use as the default value for the -node parameter of commands.
[-stop-on-error {true|false}] - Stop On Error Use this parameter with the value true to specify that continuing commands should stop if they encounter an error. Use this parameter with the value false to specify that continuing commands should continue if they encounter an error.
[-prompt-timestamp {above|inline|none}] - Display Prompt Timestamp Print the current date and time as a part of the prompt. The possible values are
• above - print the timestamp using the system timestamp format on the line above the remainder of the prompt.
• inline - print the timestamp using the system timestamp format at the beginning of the line with the remainder of the prompt.
• none - do not print the timestamp. The default value is none.
Examples
cluster1::> set -privilege advanced
Warning: These advanced commands are potentially dangerous; use them only when directed to do so by Fujitsu personnel. Do you wish to continue? (y or n): y
cluster1::*>
The following examples cause all columns to be shown in output rows, with a comma used as the field separator.
cluster1::> set -showallfields true
node1,e0a,cluster,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:90:20:e9,true,physical,-,-, -,-,-,-,-, node1,e0b,cluster,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:90:20:f3,true,physical,-,-, -,-,-,-,-, node1,e0c,data,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:90:20:fd,true,physical,-,-,-,-, -,-,-, node1,e0d,data,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:90:20:07,true,physical,-,-,-,-, -,-,-, node2,e0a,cluster,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:2e:b6:62,true,physical,-,-, -,-,-,-,-, node2,e0b,cluster,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:2e:b6:6c,true,physical,-,-, -,-,-,-,-, node2,e0c,data,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:2e:b6:76,true,physical,-,-,-,-, -,-,-, node2,e0d,data,up,1500,true,true,full,full,auto,1000,full,none,00:0c:29:2e:b6:80,true,physical,-,-,-,-, -,-,-,
The following example shows how to create a prompt with a timestamp.
cluster1::> set -prompt-timestamp above
7. top
Go to the top-level directory
Description
The top command changes the current working directory of the command prompt to the top-level command directory.
Examples
The following example returns the command prompt from the storage aggregate directory to the top- level directory:
cluster1::storage aggregate> top
8. up
Go up one directory
Description
The up command, which can also be specified as two dots (..), changes the current working directory of the command prompt to the directory that is up one level in the command hierarchy.
Examples
The following example takes the command prompt up one level from the storage aggregate directory:
cluster1::storage aggregate> up
9. application commands
application provisioning config modify
Availability: This command is available to cluster administrators at the advanced privilege level.
Description
Parameters
[-is-mixed-storage-services-allowed {true|false}] - Is Mixed Storage Services Allowed Specifies whether mixed cost storage services are allowed for provisioning placement. If the value of this parameter is false, only the aggregates closest to the performance requirements of the storage service are used. If the value of this parameter is true, all aggregates with sufficient performance are considered. The initial value for option is false.
Examples
application provisioning config show
Description
Examples
10. autobalance commands
The autobalance directory
autobalance aggregate commands
Auto Balance Aggregate
autobalance aggregate show-aggregate-state
Description
The autobalance aggregate show-aggregate-state command displays information about an aggregate state that is considered by the Auto Balance Aggregate feature.
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 If this parameter is specified, the display will be limited to only those aggregates with a node that matches the specified value.
[-aggregate <aggregate name>] - Name of the Aggregate If this parameter is specified, the display will be limited to only that aggregate with a name that matches the specified value.
[-total-size {<integer>[KB|MB|GB|TB|PB]}] - Total Size of the Aggregate If this parameter is specified, the display will be limited to only those aggregates with a total-size that matches the specified value.
[-used-size {<integer>[KB|MB|GB|TB|PB]}] - Used Size of the Aggregate If this parameter is specified, the display will be limited to only those aggregates with a used-size that matches the specified value.
[-aggregate-unbalanced-threshold {<integer>[KB|MB|GB|TB|PB]}] - Threshold When Aggregate Is Considered Unbalanced
If this parameter is specified, the display will be limited to only those aggregates with a threshold that matches the specified value.
[-outgoing-size {<integer>[KB|MB|GB|TB|PB]}] - Size of Outgoing Volumes in the Aggregate If this parameter is specified, the display will be limited to only those aggregates with an outgoing-size that matches the specified value. Outgoing size will be equal to the total size of the volumes that move away from each one of those aggregate.
[-incoming-size {<integer>[KB|MB|GB|TB|PB]}] - Size of Incoming Volumes in the Aggregate If this parameter is specified, the display will be limited to only those aggregates with an incoming-size that matches the specified value. Incoming size will be equal to the total size of the volumes that move towards to each one of those aggregates.
[-raidtype {raid_tec|raid_dp|raid4}] - RAID Type
If this parameter is specified, the display will be limited to only those aggregates with a raidtype that matches the specified value.
[-home-cluster <UUID>] - Home Cluster ID If this parameter is specified, the display will be limited to only those aggregates with a home-cluster ID that matches the specified value.
[-is-hybrid {true|false}] - Aggregate Is a Hybrid If this parameter is specified as true, the display will be limited to only hybrid aggregates. If the parameter is specified as false, the display will be limited to only non-hybrid aggregates.
[-is-incoming-volume-thin {true|false}] - An Incoming Volume Is Thin When you use thin provisioning for a volume, it can run out of space even if it has not yet consumed its nominal size and you should carefully monitor space utilization to avoid unexpected errors due to the volume running out of space. If this parameter is specified as true, the display will be limited to only those aggregates which are the target of a move of thin volume. If the parameter is specified as false, the display will be limited to only those aggregates which are not the target of a move of thin volume.
[-is-balanceable {true|false}] - Is Balanceable If this parameter is specified as true, the display will be limited to only balanceable aggregates. If the parameter is specified as false, the display will be limited to only non-balanceable aggregates.
[-is-move-target {true|false}] - Aggregate Is a Volume Move Target If this parameter is specified as true, the display will be limited to only those aggregates which are target of a volume move. If the parameter is specified as false, the display will be limited to only those aggregates which are not the target of a volume move.
[-attributes <text>, ...] - Aggregate Attributes If this parameter is specified, the display will be limited to only those aggregates with attributes that matches the specified values.
[-aggregate-available-threshold {<integer>[KB|MB|GB|TB|PB]}] - Threshold When Aggregate Is Considered Balanced
If this parameter is specified, the display will be limited to only those aggregates which meet the specified threshold to be considered as balanced.
Examples
The following example displays information about the state for all aggregates in the cluster.
cluster1::*> autobalance aggregate show-aggregate-state Aggregate: aggr0 Total Size: 4.78GB Used Size: 4.56GB Outgoing Size: 0B Incoming Size: 0B Aggregate Used Space Threshold: 3.34GB Aggregate Available Space Threshold: 1.91GB RAID Type: raid_dp Home Cluster ID: edf0379b-16da-11e6-aa3c-0050568558c2 Attributes: CFO Excluded Mroot
Aggregate: aggr_1 Total Size: 12.61GB Used Size: 111.6MB Outgoing Size: 0B Incoming Size: 0B Aggregate Used Space Threshold: 8.83GB
10. autobalance commands autobalance aggregate commands
Aggregate Available Space Threshold: 5.04GB RAID Type: raid4 Home Cluster ID: edf0379b-16da-11e6-aa3c-0050568558c2 Attributes: Excluded
The following example displays information about all entries of the aggregate state, for all aggregates in the cluster.
cluster1::*> autobalance aggregate show-aggregate-state -instance Node Name: cluster-1-01 Name of the Aggregate: aggr0 Total Size of the Aggregate: 4.78GB Used Size of the Aggregate: 4.56GB Threshold When Aggregate Is Considered Unbalanced: 3.34GB Size of Outgoing Volumes in the Aggregate: 0B Size of Incoming Volumes in the Aggregate: 0B RAID Type: raid_dp Home Cluster ID: edf0379b-16da-11e6-aa3c-0050568558c2 Aggregate Is a Hybrid: false An Incoming Volume Is Thin: false Is Balanceable: false Aggregate Is a Volume Move Target: false Aggregate Attributes: CFO Excluded Mroot Threshold When Aggregate Is Considered Balanced: 1.91GB
Node Name: cluster-1-01 Name of the Aggregate: aggr_1 Total Size of the Aggregate: 12.61GB Used Size of the Aggregate: 111.6MB Threshold When Aggregate Is Considered Unbalanced: 8.83GB Size of Outgoing Volumes in the Aggregate: 0B Size of Incoming Volumes in the Aggregate: 0B RAID Type: raid4 Home Cluster ID: edf0379b-16da-11e6-aa3c-0050568558c2 Aggregate Is a Hybrid: false An Incoming Volume Is Thin: false Is Balanceable: false Aggregate Is a Volume Move Target: false Aggregate Attributes: Excluded Threshold When Aggregate Is Considered Balanced: 5.04GB
autobalance aggregate show-unbalanced-volume-state
Description
Parameters
[-node {<nodename>|local}] - Node Name If this parameter is specified, the display will be limited to only those volumes with a node that matches the specified value.
[-DSID <integer>] - DSID of the Last Volume Queried If this parameter is specified, the display will be limited to only those volumes with a DSID that matches the specified value.
[-aggregate <aggregate name>] - Aggregate If this parameter is specified, the display will be limited to only those volumes with an aggregate name that matches the specified value.
[-volume-name <text>] - Name of the Volume If this parameter is specified, the display will be limited to only that volume with a name that matches the specified value.
[-last-threshold-crossed-time <MM/DD/YYYY HH:MM:SS>] - Last Time Threshold Crossed If this parameter is specified, the display will be limited to only those volumes with a threshold crossing time that matches the specified value.
[-last-placed-time <MM/DD/YYYY HH:MM:SS>] - Last Time Volume Was Moved If this parameter is specified, the display will be limited to only those volumes with a last time they have been moved that matches the specified value.
[-is-moving {true|false}] - Is Volume Currently Moving If this parameter is specified as true, the display will be limited to only the moving volumes. If the parameter is specified as false, the display will be limited to only the non-moving volumes.
[-is-quiesced {true|false}] - Is Volume Quiesced If this parameter is specified as true, the display will be limited to only the quiesced volumes. If the parameter is specified as false, the display will be limited to only the non-quiesced volumes.
[-total-footprint {<integer>[KB|MB|GB|TB|PB]}] - Total Size of the Volume If this parameter is specified, the display will be limited to only those volumes with a total footprint that matches the specified value.
[-attributes <text>, ...] - Volume's Attributes If this parameter is specified, the display will be limited to only those volumes with attributes that matches the specified value.
[-last-checked <MM/DD/YYYY HH:MM:SS>] - Last Time Volume State Was Checked If this parameter is specified, the display will be limited to only those volumes with a last time their state was checked that matches the specified value.
Examples
The following example display information about all of the unbalanced volumes that the Auto Balance Aggregate feature is aware of.
cluster1::*> autobalance aggregate show-unbalanced-volume-state Last Checked On: 3/13/2014 14:32:01
Volume: ro10 Footprint: 20.20MB
Last Time Over IOPS Threshold: 3/12/2014 16:20:18 Last Placed: 3/11/2014 10:16:04 Attributes: Over IOPS Threshold Stabilizing
Volume: test Footprint: 20.20MB Last Time Over IOPS Threshold: 3/12/2014 16:20:18 Last Placed: 3/11/2014 10:16:42 Attributes: Over IOPS Threshold In Mirror Stabilizing
The following example displays all of the information that the Auto Balance Aggregate feature has collected for all of the unbalanced volumes it is aware of.
cluster1::*> autobalance aggregate show-unbalanced-volume-state -instance Node Name: cluster-1-01 DSID of the Last Volume Queried: 1025 Aggregate: aggr_1 Name of the Volume: ro10 Last Time Threshold Crossed: 3/12/2014 16:20:18 Last Time Volume Was Moved: 3/11/2014 10:16:04 Is Volume Currently Moving: false Is Volume Quiesced: false Total Size of the Volume: 20.20MB Volume's Attributes: Over IOPS Threshold Stabilizing Last Time Volume State Was Checked: 3/13/2014 08:20:18
Node Name: cluster-1-01 DSID of the Last Volume Queried: 1026 Aggregate: aggr_1 Name of the Volume: test Last Time Threshold Crossed: 3/12/2014 16:20:18 Last Time Volume Was Moved: 3/11/2014 10:16:42 Is Volume Currently Moving: false Is Volume Quiesced: false Total Size of the Volume: 20.20MB Volume's Attributes: Over IOPS Threshold In Mirror Stabilizing Last Time Volume State Was Checked: 3/13/2014 08:20:18
autobalance aggregate config commands
Auto Balance Aggregate configuration
autobalance aggregate config modify
Description
The autobalance aggregate config modify command allows the user to customize the parameters that determine when volumes should be considered for automatic move or recommendation by the Auto Balance Aggregate feature.
Parameters
[-is-enabled {true|false}] - Is the Auto Balance Aggregate Feature Enabled This specifies whether the Auto Balance Aggregate feature is enabled and running.
[-aggregate-unbalanced-threshold-percent <integer>] - Threshold When Aggregate Is Considered Unbalanced (%)
This specifies the space used threshold percentage that will cause the Auto Balance Aggregate feature to consider an aggregate as unbalanced.
[-aggregate-available-threshold-percent <integer>] - Threshold When Aggregate Is Considered Balanced (%)
This specifies the threshold percentage which will determine if an aggregate is a target destination for a move. The Auto Balance Aggregate feature will attempt to move volumes from an unbalanced aggregate until it is under this percentage.
Examples
The following example displays a modification for the default configuration of the Auto Balance Aggregate feature
cluster1::*> autobalance aggregate config show Is the Auto Balance Aggregate Feature Enabled: false Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40
cluster1::*> autobalance aggregate config modify -is-enabled true
cluster1::*> autobalance aggregate config show Is the Auto Balance Aggregate Feature Enabled: true Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40
At the diagnostic level, there are additional modifiable parameters.
cluster1::*> autobalance aggregate config show Is the Auto Balance Aggregate Feature Enabled: false Mode of the Auto Balance Aggregate Feature: recommend Polling Interval: 3600 Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40 Volume Operations Threshold (IOPS): 100 Volume Operations Threshold Not Exceeded for Duration: 24 Volume Not Moved Again for Duration: 48
cluster1::*> autobalance aggregate config modify -mode auto -polling-interval 4000
cluster1::*> autobalance aggregate config show Is the Auto Balance Aggregate Feature Enabled: false Mode of the Auto Balance Aggregate Feature: auto Polling Interval: 4000
Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40 Volume Operations Threshold (IOPS): 100 Volume Operations Threshold Not Exceeded for Duration: 24 Volume Not Moved Again for Duration: 48
autobalance aggregate config show
Description
The autobalance aggregate config show command displays information about parameters that determine when volumes should be considered for automatic move or recommendation by the Auto Balance Aggregate feature.
Examples
The following example displays the default configuration for the Auto Balance Aggregate feature
cluster1::*> autobalance aggregate config show Is the Auto Balance Aggregate Feature Enabled: false Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40
At the diagnostic level, the output displays the information below.
Is the Auto Balance Aggregate Feature Enabled: false Mode of the Auto Balance Aggregate Feature: recommend Polling Interval: 3600 Threshold When Aggregate Is Considered Unbalanced (%): 70 Threshold When Aggregate Is Considered Balanced (%): 40 Volume Operations Threshold (IOPS): 100 Volume Operations Threshold Not Exceeded for Duration: 24 Volume Not Moved Again for Duration: 48
11. Cluster Commands
Manage clusters
The cluster commands enable you to create and manage Data ONTAP 8 clusters.
cluster add-node
Expand the cluster by discovering and adding new nodes
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The cluster add-node command discovers and adds new nodes to the cluster. When the -node-count parameter is specified, the command attempts to add that many nodes to the cluster. The -node-ip parameter can be specified to directly add a node. The -cluster-ips parameter can be specified to directly add one or more nodes in parallel. Only one of the -node-count, -node-ip and -cluster-ips parameters can be provided. The system node show-discovered command displays all the nodes discovered on the local network.
Note The node-count parameter is deprecated and may be removed in a future release of Data ONTAP. Use the -cluster-ips parameter instead.
Note The node-ip parameter is deprecated and may be removed in a future release of Data ONTAP. Use the -cluster-ips parameter instead.
Parameters
{ -cluster-ips <IP Address>, ... - List of Cluster Interface IP Addresses of the Nodes Being Added This parameter contains a comma separated list of cluster interface IP addresses of the nodes in the cluster you are creating. All the nodes specified in the list will be added to the cluster.
| -retry [true] - Retry a failed cluster add-node operation Use this parameter to retry the most recently failed cluster add-node command with the originally specified parameters. Retry is not supported if the cluster add-node command was originally run with either the -node-count or -node-ip parameters.
| -node-count <integer> - (DEPRECATED)-Number of Nodes Being Added Number of nodes to be added to the cluster. If fewer nodes are discovered, all the discovered nodes are added to the cluster and the command will fail since there are fewer nodes than specified. If more nodes are found than the number specified, the command will fail because there is no way to determine which nodes you intend to add to the cluster.
Note The -node-count parameter is supported on non-shared architecture platforms only.
| -node-ip <IP Address>} - (DEPRECATED)-Cluster IP Address of Node Cluster IP address of the node to add. When this parameter is provided, the command directly adds the node.
[-node-names <text>, ...] - List of Node Names
This parameter contains a comma separated list of node names of all the nodes in the cluster you are creating. The node names must have an one to one correspondence with -cluster-ips parameter. The names provided will be used to rename the nodes once they are added to the cluster.
[-foreground {true|false}] - Foreground Process When set to false the command runs in the background as a job. The default is true, which causes the command to return after the operation completes.
[-allow-mixed-version-join [true]] - Allow a Node At a Different Version to Join Cluster This parameter allows nodes with different, but compatible versions of Data ONTAP to be added to the cluster. A Data ONTAP best practice is to add nodes to the cluster that are of the same Data ONTAP version as the nodes in the cluster, but that may not always be possible.
Examples
cluster1::> cluster add-node -cluster-ips 1.1.1.1, 2.2.2.2 Use the 'cluster add-node-status' command to see the progress of the add-node operation.
The following example adds 3 nodes using -node-count.
cluster1::> cluster add-node -node-count 3 [Job 22] Job succeeded.
Related reference
cluster create (page 60)
Show cluster expansion progress
Description
The cluster add-node-status command displays the progress of the node joining a cluster initiated by using the cluster create command or the cluster add-node command
Parameters
[-node-uuid <UUID>] - Node UUID Select the node that match the specified node UUID.
[-node-name <text>] - Node Name Select the nodes that match the specified node name.
[-cluster-ip <IP Address>] - IP Address of a Cluster Interface of Node
11. Cluster Commands cluster add-node-status
Select the nodes that match the specified cluster IP.
[-status <Cluster Operation Status>] - The Status of Current Task Being Performed Select the nodes that match the specified status. This status shows whether the operation is ongoing or complete with success or failure. The various phases that a node goes through are node-initialization, joining-cluster, service-startup, post-cluster-setup and success or failure.
[-failure-msg <text>] - Error Reason Select the nodes that match the specified error string.
[-last-updated <MM/DD/YYYY HH:MM:SS>] - Last Updated The date/time stamp of the last update to the status.
Examples
The following example shows the progress of a node add operation:
clus1::> cluster add-node-status Node Name Node IP Status Error Reason --------------- ----------------- -------------- ---------------------- node1 1.1.1.1 success -
Related reference
Create a cluster
Description
The cluster create command creates a cluster with one or more nodes. When the -node-count parameter is specified, the command attempts to add that many nodes to the cluster. The -cluster-ips parameter can be specified to add one or more nodes in parallel. Only one of the -node-count and - cluster-ips parameters can be provided.
Note that single-node clusters do not require configuring the cluster network. A cluster network interface must be configured before other nodes can join the cluster.
Note The node-count parameter is deprecated and may be removed in a future release of Data ONTAP. Use the -cluster-ips parameter instead.
Parameters
[-license <License Code V2>] - (DEPRECATED)-Base License
Note This parameter is deprecated and may be removed in a future release of Data ONTAP.
Use this optional parameter to specify the base license for the cluster. Obtain this value from your sales or support representative.
11. Cluster Commands cluster create
-clustername <text> - Cluster Name Use this parameter to specify the name of the cluster you are creating.
• The name must contain only the following characters: A-Z, a-z, 0-9, "-" or "_".
• The first character must be one of the following characters: A-Z or a-z.
• The last character must be one of the following characters: A-Z, a-z or 0-9.
• The maximum supported length is 44 characters.
• The system reserves the following names: "all", "cluster", "local" and "localhost".
| [-cluster-ips <IP Address>, ...] - List of Cluster Interface IP Addresses of the Nodes Being Added This parameter contains a comma separated list of cluster interface IP addresses of the nodes in the cluster you are creating. All the nodes specified in the list will be added to the cluster.
| [-node-count <integer>] - (DEPRECATED)-Node Count Use this parameter to specify the number of nodes in the cluster you are creating.
• -node-count parameter is supported on non-shared architecture platforms only.
[-node-names <text>, ...] - List of Node Names This parameter contains a comma separated list of node names of all the nodes in the cluster you are creating. The node names must have an one to one correspondence with -cluster-ips parameter. The names provided will be used to rename the nodes once they are added to the cluster.
| -retry [true]} - Retry a failed cluster create operation Use this parameter to retry the most recently failed cluster create command with the originally specified parameters. Retry is not supported if the cluster create command was originally run with either the -node-count or -node-ip parameters.
Examples
cluster1::> cluster create -clustername cluster1
The following example creates a cluster named cluster1 with node-count 4 on a non-shared architecture platform.
cluster1::> cluster create -clustername cluster1 -node-count 4
cluster join
(DEPRECATED)-Join an existing cluster using the specified member's IP address or by cluster name
Description
Note This command is deprecated and may be removed in a future release of Data ONTAP. Use cluster add-node from a node in the cluster instead.
The cluster join command adds a node to an existing cluster. Use the cluster create command to create a cluster if one does not already exist.
11. Cluster Commands cluster join
Note that a cluster network interface must be configured for the cluster before other nodes can join the cluster.
Parameters
{ -clusteripaddr <IP Address> - IP Address of a Cluster Interface from a Node in the Cluster Use this parameter to specify the IP address of a cluster interface. This must be the IP address of a cluster interface of a node that is already in the cluster. This parameter is mutually exclusive with the - cluster-name parameter.
| -cluster-name <text>} - (DEPRECATED)-Cluster Name of the Cluster to Join Deprecated. Use this parameter to specify the name of an existing cluster to join.
[-allow-mixed-version-join [true]] - Allow a Node at a Different Version to Join Cluster This parameter allows nodes with different, but compatible versions of Data ONTAP to join the cluster. A Data ONTAP best practice is to join nodes to the cluster that are of the same Data ONTAP version as the nodes in the cluster, but that may not always be possible.
[-node-name <text>] - Name to Use for the Node in the Cluster This parameter specifies the name that the node will have when we join it to the cluster.
Examples
The following example joins the local node to a cluster. The IP address 192.0.2.66 is the address of a cluster interface of a node that already belongs to the cluster.
node::> cluster join -clusteripaddr 192.0.2.66
Related reference
Description
The cluster modify command modifies the cluster attributes of a node, including its eligibility to participate in the cluster. At the advanced privilege level, you can use the command to specify whether a node holds epsilon. Epsilon is an extra fractional vote that enables quorum to form using slightly weaker requirements. For example, two out of four eligible nodes are sufficient to form quorum if one of those two nodes holds epsilon.
Parameters
-node {<nodename>|local} - Node Use this parameter to specify the name of the node to modify. If you do not specify a node, the command runs on the local node.
[-epsilon {true|false}] - Epsilon Use this parameter with the value true to specify that the node holds Epsilon in the cluster. Use this parameter with the value false to specify that the node does not hold Epsilon in the cluster. In a cluster, only one node can be designated as Epsilon at any given time. You can designate a node as Epsilon to add weight to its voting in a cluster with an even number of nodes.
[-eligibility {true|false}] - Eligibility
11. Cluster Commands cluster modify
Use this parameter with the value true to specify that the node is eligible to participate in the cluster. Use this parameter with the value false to specify that the node is not eligible to participate in the cluster. If you modify a node as ineligible to participate in the cluster, the command prompts you for confirmation before it runs.
[-skip-quorum-check-before-eligible [true]] - Skip Quorum Check Before Setting Node Eligible If this parameter is specified, quorum checks will be skipped prior to setting a node eligible. When setting a node to eligible, the operation will continue even if there is a possible data outage due to a quorum issue.
[-skip-quorum-check-before-ineligible [true]] - Skip Quorum Check Before Setting Node Ineligible
If this parameter is specified, quorum checks will be skipped prior to setting a node ineligible. When setting a node to ineligible, the operation will continue even if there is a possible data outage due to a quorum issue.
Examples
This example modifies a node to make it eligible to participate in the cluster.
cluster1::*> cluster modify -node node3 -eligibility true
The following example removes epsilon from the node named node0 and adds it to the node named node1:
cluster1::*> cluster modify -node node0 -epsilon false cluster1::*> cluster modify -node node1 -epsilon true
cluster ping-cluster
Description
The cluster ping-cluster command probes network connectivity to remote cluster interfaces, and performs an RPC server check.
Parameters
-node <nodename> - Node Use this parameter to send the ping from the node you specify.
[-use-sitelist {true|false}] - Use Sitelist for Cluster Interfaces Use this parameter with the value true to specify that the command use the sitelist to determine any incomplete cluster IP information. Use this parameter with the value false to specify that the command not use the sitelist.
[-skip-rpccheck {true|false}] - Skip RPC Server Check Use this parameter with the value true to specify that the command not perform the rpcinfo check of remote hosts. Use this parameter with the value false to specify that the command perform the rpcinfo check. The rpcinfo check checks the status of the RPC servers on the remote hosts. By default, the rpcinfo check runs on the program number of the portmapper. Use the -rpc-prognum parameter to override this default.
[-rpc-prognum <integer>] - RPC Server to Check Use this parameter to override default behavior and run the rpcinfo check on the program number you specify. By default, the rpcinfo check runs on the program number of the portmapper.
11. Cluster Commands cluster ping-cluster
Examples
The following example shows typical output for this command.
cluster1::*> cluster ping-cluster -node node1 Host is node1 Getting addresses from network interface table... Local = 10.254.231.102 10.254.91.42 Remote = 10.254.42.25 10.254.16.228 Ping status: .... Basic connectivity succeeds on 4 path(s) Basic connectivity fails on 0 path(s) ................ Detected 1500 byte MTU on 4 path(s): Local 10.254.231.102 to Remote 10.254.16.228 Local 10.254.231.102 to Remote 10.254.42.25 Local 10.254.91.42 to Remote 10.254.16.228 Local 10.254.91.42 to Remote 10.254.42.25 Larger than PMTU communication succeeds on 4 path(s) RPC status: 2 paths up, 0 paths down (tcp check) 2 paths up, 0 paths down (udp check)
cluster remove-node
Description
The cluster remove-node command removes a node from a cluster.
Before you can remove a node from a cluster, you must shut down all of the node's shared resources, such as virtual interfaces to clients. If any of a node's shared resources are still active, the command fails. The failure message will display which active resources must be shut down before the node can be removed from the cluster.
Parameters
{ -node <nodename> - Node to Unjoin Use this parameter to specify the name of the node to remove from the cluster.
| -cluster-ip <IP Address>} - IP Address of a Cluster Interface of Node to Unjoin Use this parameter to specify the cluster IP of the node to remove from the cluster.
[-skip-quorum-check-before-unjoin [true]] - Skip Quorum Check before Unjoin If this parameter is specified, quorum checks will be skipped prior to the remove-node command. The operation will continue even if there is a possible data outage due to a quorum issue.
[-skip-last-low-version-node-check [true]] - Skip the Check That Prevents Unjoining the Last Low Versioned Node
This parameter allows the node with lowest version of Data ONTAP to be removed from the cluster.
11. Cluster Commands cluster remove-node
Examples
The following example shows how to remove the node named node4 from the cluster.
cluster1::*> cluster remove-node -node node4
The following example forcibly removes the node from the cluster:
cluster1::*> cluster remove-node -node node4 -force
cluster setup
Setup wizard
Description
Note Use of this command to join a node to an existing cluster is deprecated and might be removed in a future release of Data ONTAP. From a node in the cluster use the system node show-discovered command and then use the cluster add-node command.
The cluster setup command runs the cluster setup wizard, which can be used to either create a cluster or join a node to an existing cluster. When you run the cluster setup wizard, enter the appropriate information at the prompts. You will be asked to provide the following information to create a cluster:
• Node management interface port, IP address, netmask, default gateway
• Cluster name
• Cluster base license key
Note This parameter has been deprecated. It may be removed from a future release of Data ONTAP.
• Feature license keys
• Cluster administrator's password
• DNS domain names
• Name server IP addresses
• Location You will be asked to provide the following information to join a cluster:
• Node management interface port, IP address, netmask, default gateway
• Cluster IP address The cluster management interface is used for managing the cluster. It provides one IP address to manage the cluster and will fail over to another node, if necessary. This is the preferred IP address for managing the cluster, but you can also manage the cluster by logging in to the node management IP address of a node in the cluster. Since the cluster management interface must be able to fail over, the port role for the interface must be "data" and typically the best choice for an IP address is one on the data network. The node management interface will not fail over, so an IP address on the management network and a port with the role "node management" is the best choice. Alternatively, you can assign an IP address on the data network to the cluster management interface - if that is better in your network topology - but the port must be a data port. The two examples below illustrate the cluster create and cluster join operations, respectively.
11. Cluster Commands cluster setup
Examples
The following example shows the create option of cluster setup.
node::> cluster setup
Welcome to the cluster setup wizard.
You can enter the following commands at any time: "help" or "?" - if you want to have a question clarified, "back" - if you want to change previously answered questions, and "exit" or "quit" - if you want to quit the cluster setup wizard. Any changes you made before quitting will be saved.
You can return to cluster setup at any time by typing "cluster setup". To accept a default or omit a question, do not enter a value.
This system will send event messages and periodic reports to Fujitsu Technical Support. To disable this feature, enter autosupport modify -support disable within 24 hours.
Enabling AutoSupport can significantly speed problem determination and resolution should a problem occur on your system. For further information on AutoSupport, see: http://support.netapp.com/autosupport/
Type yes to confirm and continue {yes}: yes
Enter the node management interface port [e0c]: Enter the node management interface IP address: 192.0.2.66 Enter the node management interface netmask: 255.255.255.192 Enter the node management interface default gateway: 192.0.2.1 The node management interface has been modified to use port e0c with IP address 192.0.2.66. Use your web browser to complete cluster setup by accessing https://192.0.2.66
Otherwise, press Enter to complete cluster setup using the command line interface:
Do you want to create a new cluster or join an existing cluster? {create, join}: create
Do you intend for this node to be used as a single node cluster? {yes, no} [no]:
Existing cluster interface configuration found:
Port MTU IP Netmask e0a 9000 169.254.21.189 255.255.0.0 e0b 9000 169.254.29.73 255.255.0.0
Do you want to use this configuration? {yes, no} [yes]:
Enter the cluster administrator's (username "admin") password:
Retype the password:
Step 1 of 5: Create a Cluster You can type "back", "exit", or "help" at any question.
Enter the cluster name: cluster1
Creating cluster cluster1
Cluster cluster1 has been created.
Step 2 of 5: Add Feature License Keys You can type "back", "exit", or "help" at any question.
Enter an additional license key []:
Step 3 of 5: Set Up a Vserver for Cluster Administration You can type "back", "exit", or "help" at any question.
Enter the cluster management interface port [e0d]: Enter the cluster management interface IP address: 192.0.2.60 Enter the cluster management interface netmask: 255.255.255.192 Enter the cluster management interface default gateway [192.0.2.1]:
A cluster management interface on port e0d with IP address 192.0.2.60 has been created. You can use th is address to connect to and manage the cluster.
Enter the DNS domain names: data.example.com Enter the name server IP addresses: 192.0.2.147 DNS lookup for the admin Vserver will use the data.example.com domain.
Step 4 of 5: Configure Storage Failover (SFO) You can type "back", "exit", or "help" at any question.
SFO is licensed. SFO will be enabled when the partner joins the cluster.
Step 5 of 5: Set Up the Node You can type "back", "exit", or "help" at any question.
Where is the controller located []: Sunnyvale
Cluster "cluster1" has been created.
To complete cluster setup, you must join each additional node to the cluster by running "system node show-discovered" and "cluster add-node" from a node in the cluster.
To complete system configuration, you can use either OnCommand System Manager or the Data ONTAP command-line interface.
To access OnCommand System Manager, point your web browser to the cluster management IP address (https://192.0.2.60).
To access the command-line interface, connect to the cluster management IP address (for example, ssh [email protected]).
cluster1::>
An example of using cluster setup to join a cluster is shown below.
node::> cluster setup
Welcome to the cluster setup wizard.
You can enter the following commands at any time: "help" or "?" - if you want to have a question clarified, "back" - if you want to change previously answered questions, and "exit" or "quit" - if you want to quit the cluster setup wizard. Any changes you made before quitting will be saved.
You can return to cluster setup at any time by typing "cluster setup". To accept a default or omit a question, do not enter a value.
This system will send event messages and periodic reports to Fujitsu Technical Support. To disable this feature, enter autosupport modify -support disable within 24 hours.
Enabling AutoSupport can significantly speed problem determination and resolution should a problem occur on your system. For further information on AutoSupport, see: http://support.netapp.com/autosupport/
Type yes to confirm and continue {yes}: yes
Enter the node management interface port [e0c]: Enter the node management interface IP address: 192.0.2.67 Enter the node management interface netmask: 255.255.255.192 Enter the node management interface default gateway: 192.0.2.1 A node management interface on port e0c with IP address 192.0.2.67 has been created.
Use your web browser to complete cluster setup by accessing https://192.0.2.67
Otherwise, press Enter to complete cluster setup using the command line interface:
Do you want to create a new cluster or join an existing cluster? {create, join}: join
Existing cluster interface configuration found:
Port MTU IP Netmask e0a 9000 169.254.31.170 255.255.0.0 e0b 9000 169.254.115.61 255.255.0.0
Do you want to use this configuration? {yes, no} [yes]:
Step 1 of 3: Join an Existing Cluster You can type "back", "exit", or "help" at any question.
Enter the IP address of an interface on the private cluster network from the cluster you want to join: 169.254.115.8
Joining cluster at address 169.254.115.8
This node has joined the cluster cluster1.
Step 2 of 3: Configure Storage Failover (SFO) You can type "back", "exit", or "help" at any question.
SFO is licensed. SFO will be enabled when the partner joins the cluster.
Step 3 of 3: Set Up the Node You can type "back", "exit", or "help" at any question.
This node has been joined to cluster "cluster1".
To complete cluster setup, you must join each additional node to the cluster by running "system node show-discovered" and "cluster add-node" from a node in the cluster.
To complete system configuration, you can use either OnCommand System Manager or the Data ONTAP command-line interface.
To access OnCommand System Manager, point your web browser to the cluster management IP address (https://192.0.2.60).
To access the command-line interface, connect to the cluster management IP address (for example, ssh [email protected]).
cluster1::>
cluster add-node (page 58)
cluster create (page 60)
cluster join (page 61)
Display cluster node members
Description
The cluster show command displays information about the nodes in a cluster.
Parameters
[-node {<nodename>|local}] - Node Selects the nodes that match this parameter value.
[-node-uuid <UUID>] - UUID (privilege: advanced) Selects the nodes that match this parameter value.
[-epsilon {true|false}] - Epsilon (privilege: advanced) Selects the nodes that match this parameter value. In a cluster, only one node can be designated as Epsilon at any given time. You can designate a node as Epsilon to add weight to its voting in a cluster with an even number of nodes.
[-eligibility {true|false}] - Eligibility Selects the nodes that match this parameter value (true means eligible to participate in the cluster).
[-health {true|false}] - Health Selects the nodes that match this parameter value (true means online).
Examples
The following example displays information about all nodes in the cluster:
cluster1::> cluster show Node Health Eligibility --------------------- ------- ------------
11. Cluster Commands cluster show
node0 true true node1 true true node2 true true node3 true true
The following example displays information about the node named node1:
cluster1::> cluster show -node node1
Node: node1 Eligibility: true Health: true
cluster contact-info commands
cluster contact-info modify
Modify contact information for the cluster
Description
The cluster contact-info modify command modifies contact information for the cluster administrators. If any values contain spaces, you must enclose those values in quotes. Use the cluster contact-info show command to display contact information for the cluster administrators.
Parameters
[-primary-name <text>] - Name of Primary Contact Use this parameter to specify the name of the primary contact.
[-primary-phone <text>] - Phone Number of Primary Contact Use this parameter to specify the phone number of the primary contact.
[-primary-alt-phone <text>] - Alternate Phone Number of Primary Contact Use this parameter to specify the alternate phone number of the primary contact.
[-primary-email <text>] - Email Address or User ID of Primary Contact Use this parameter to specify the email address of the primary contact.
[-secondary-name <text>] - Name of Secondary Contact Use this parameter to specify the name of the secondary contact.
[-secondary-phone <text>] - Phone Number of Secondary Contact Use this parameter to specify the phone number of the secondary contact.
[-secondary-alt-phone <text>] - Alternate Phone Number of Secondary Contact Use this parameter to specify the alternate phone number of the secondary contact.
[-secondary-email <text>] - Email Address or User ID of Secondary Contact Use this parameter to specify the email address of the secondary contact.
[-business-name <text>] - Business Name Use this parameter to specify the name of the business responsible for this cluster.
[-address <text>] - Business Address
Use this parameter to specify the street address of the business responsible for this cluster.
[-city <text>] - City Where Business Resides Use this parameter to specify the name of the city in which the business is located.
[-state <text>] - State Where Business Resides Use this parameter to specify the name of the state or province in which the business is located.
[-country <Country Code>] - 2-Character Country Code Use this parameter to specify the 2-character country code of the country in which the business is located.
[-zip-code <text>] - Postal Code Where Business Resides Use this parameter to specify the postal or ZIP code area in which the business is located.
Examples
The following example changes the name and phone numbers of the secondary contact person for the cluster.
cluster1::> cluster contact-info modify -secondary-name "John Doe" -secondary-phone 123.555.0156 -secon dary-alt-phone 123.555.0178
The following example changes the mailing address of the business responsible for the cluster.
cluster1::> cluster contact-info modify -address "123 Example Avenue" -city Exampleville -state "New Ex ample" -zip-code 99999 -country US
Related reference
cluster contact-info show
Display contact information for the cluster
Description
The cluster contact-info show command displays contact information for the cluster administrators.
Examples
cluster1::> cluster contact-info show
Name of Primary Contact : Richard Roe Phone Number of Primary Contact : 123.555.0123
Alternate Phone Number of Primary Contact : 123.555.0145 Email Address or User Id of Primary Contact : [email protected]
Name of Secondary Contact : John Doe Phone Number of Secondary Contact : 123.555.0167
Alternate Phone Number of Secondary Contact : 123.555.0189 Email Address or User Id of Secondary Contact : [email protected]
Business Name : Example Dot Com Business Address : 123 Example Avenue
City Where Business Resides : Exampleville State Where Business Resides : New Example
11. Cluster Commands cluster contact-info commands
2-Character Country Code : US Postal Code Where Business Resides : 99999
cluster controller-replacement commands
Delete network interfaces displaced away from this node by controller-replacement
Description
Delete references to logical interfaces that were displaced to another node due to a controller-replacement. A LIF that has been displaced to another node has had its home-node modified to another node because no network ports were available in the same broadcast domain on the original home-node. Deleting this entry does not delete the LIF, it only deletes the entry from the displaced-lifs table indicating that the LIF's current home-node is considered restored.
Parameters
-node <nodename> - Node Selects the node from which the LIF was displaced.
-vserver <vserver> - Vserver Selects the vserver on which the LIF resides.
-lif-name <text> - Lif Name Selects the name of the LIF for which to display displaced information.
Examples
cluster1::> cluster controller-replacement network displaced-interface delete -vserver vs0 -lif lif1
cluster controller-replacement network displaced-interface restore-home-node
Restore home node for networked interfaces displaced by controller-replacement
Description
Restore the original home node of logical interfaces that were displaced to another node due to a controller- replacement. A LIF that has been displaced to another node has had its home-node modified to another node because no network ports were available in the same broadcast domain on the original home-node. Restoring the home-node attempts to find a home-port on the original home node if a suitable port exists.
Parameters
-node <nodename> - Node Selects the node from which the LIF was displaced.
11. Cluster Commands cluster controller-replacement commands
-vserver <vserver> - Vserver Selects the vserver on which the LIF resides.
-lif-name <text> - Lif Name Selects the name of the displaced LIF to be restored.
Examples
The following example restores the home-node of a displaced LIF.
cluster1::> cluster controller-replacement network displaced-interface restore-home-node -vserver vs0 -lif lif1
cluster controller-replacement network displaced-interface show
Display network interfaces displaced away from this node by controller-replacement
Description
Display logical interfaces that were displaced to another node due to a controller-replacement. A LIF that has been displaced to another node has had its home-node modified to another node because no network ports were available in the same broadcast domain on the original home-node.
Parameters
[-node <nodename>] - Node Selects the node from which the LIF was displaced.
[-vserver <vserver>] - Vserver Selects the vserver on which the LIF resides.
[-lif-name <text>] - Lif Name Selects the name of the LIF for which to display displaced information.
[-original-home-node <nodename>] - Original Home Node The original home-node that was assigned to the LIF prior to controller-replacement.
[-current-home-node <nodename>] - Current Home Node The current home-node assigned to the LIF after controller-replacement.
Examples
cluster1::> cluster controller-replacement network displaced-interface show (cluster controller-replacement network displaced-interface show) Original Current Vserver LIF Name Home Node Home Node ---------------- ----------------------- ------------------ ------------------ vs0 lif1 node1 node2 1 entry was displayed.
cluster controller-replacement network displaced-vlans commands
cluster controller-replacement network displaced-vlans delete
Remove VLANs displaces by controller-replacement
Description
Delete VLAN tags that were displaced due to a controller-replacement. A VLAN tag that has been displaced is a tag that was based on a network port that either no longer exists, or was moved to a new broadcast domain. Restoring the vlan-tags re-creates them on the specified network port.
Parameters
-node <nodename> - Node Selects the node on which the displaced vlans reside.
-port <netport> - Original Base Port The original base port where the vlans existed prior to controller-replacement.
Examples
cluster1::> cluster controller-replacement network displaced-vlans delete -node local -port e0c
cluster controller-replacement network displaced-vlans restore
Delete VLANs displaced by controller-replacement
Description
Restore VLAN tags that were displaced due to a controller-replacement. A VLAN tag that has been displaced is a tag that was based on a network port that either no longer exists, or was moved to a new broadcast domain. Restoring the vlan-tags re-creates them on the specified network port.
Parameters
-node <nodename> - Node Selects the node on which the displaced vlans reside.
-port <netport> - Original Base Port The original base port where the vlans existed prior to controller-replacement.
-destination-port <netport> - Destination Port The destination port where the vlan-tags will be restored.
Examples
The following example restores vlan-tags displaced from port e0c onto port e0d.
cluster1::> cluster controller-replacement network displaced-vlans restore -node node1 -port e0c -dest ination-port e0d
cluster controller-replacement network displaced-vlans show
Display VLANs displaced by controller-replacement
Description
Display VLAN tags that were displaced due to a controller-replacement. A VLAN tag that has been displaced is a tag that was based on a network port that either no longer exists, or was moved to a new broadcast domain. Restoring the vlan-tags re-creates them on the specified network port.
Parameters
[-node <nodename>] - Node Selects the node on which the displaced vlans reside.
[-port <netport>] - Original Base Port The original base port where the vlans existed prior to controller-replacement.
[-vlan-tags <integer>, ...] - Displaced VLANs The vlan-tags that were assigned to the network port prior to controller-replacement.
Examples
cluster1::> cluster controller-replacement network displaced-vlans show (cluster controller-replacement network displaced-vlans show) Original Node Base Port VLANs --------- --------- --------------------------------------------------------- node1 e0c 100,110,120,300,310,320 1 entry was displayed.
cluster date commands
cluster date modify
Modify the current date and time for the nodes in the cluster
Description
The cluster date modify command sets the time zone, date, and time on every node in the cluster.
Parameters
[-timezone <Area/Location Timezone>] - Time Zone This parameter sets the timezone, specified in the Olson format.
{ [-date {MM/DD/YYYY HH:MM:SS [{+|-}hh:mm]}] - Date and Time This parameter sets the date and time, in the format MM/DD/YYYY HH:MM:SS.
| [-dateandtime <[[[[[cc]yy]mm]dd]hhmm[.ss]]>] - Date and Time
11. Cluster Commands cluster date commands
This parameter sets the date and time information, in the format [[[[[cc]yy]mm]dd]hhmm[.ss]]. The argument for setting the date and time is interpreted as follows:
• cc First 2 digits of the year (e.g., 20 for 2011).
• yy Last 2 digits of year (e.g., 10 for 2010).
• mm Numeric month, a number from 01 to 12.
• dd Day, a number from 01 to 31.
• hh Hour, a number from 00 to 23.
• mm Minute, a number from 00 to 59.
• ss Second, a number from 00 to 59. If the first two digits of the year are omitted, and the last two digits are greater than 68, a date in the 1900s is used. Otherwise, a date in the 2000s is used. If all four digits of the year are omitted, the default is the current year. If the month or day is omitted, the default is the current month or day, respectively. If the seconds are omitted, the default is set to 00. The system automatically handles the time changes for Daylight Saving and Standard time, and for leap seconds and years.
| [-utcdateandtime | -u <[[[[[cc]yy]mm]dd]hhmm[.ss]]>]} - UTC Date and Time This parameter sets the date and time information in Coordinated Universal Time (UTC), in the format [[[[[cc]yy]mm]dd]hhmm[.ss]]. -u is an alias for -utcdateandtime. The argument for setting the date and time is interpreted as follows:
• cc First 2 digits of the year (e.g., 20 for 2011).
• yy Last 2 digits of year (e.g., 10 for 2010).
• mm Numeric month, a number from 01 to 12.
• dd Day, a number from 01 to 31.
• hh Hour, a number from 00 to 23.
• mm Minute, a number from 00 to 59.
• ss Second, a number from 00 to 59. If the first two digits of the year are omitted, and the last two digits are greater than 68, a date in the 1900s is used. Otherwise, a date in the 2000s is used. If all four digits of the year are omitted, the default is the current year. If the month or day is omitted, the default is the current month or day, respectively. If the seconds are omitted, the default is set to 00. Time changes for Daylight Saving and Standard time, and for leap seconds and years, are handled automatically.
Examples
The following example sets the date and time to January 1 2011, at 1:00 a.m.:
cluster1::> cluster date modify -date "01/01/2011 01:00:00"
The following example sets the date and time in the UTC format to May 22, 2011, at 09:25:00 a.m.:
cluster1::> cluster date modify -u 201105220925.00.
cluster date show
Display the current date and time for the nodes in the cluster
Description
The cluster date show command displays the time zone, date, and time settings for one or more nodes in the cluster. By default, the command displays date and time settings for all nodes in the cluster.
11. Cluster Commands cluster date commands
Parameters
| [-utc ] Displays date and time information in Coordinated Universal Time (UTC).
| [-utcdate ] Displays date and time information in UTC.
[-node {<nodename>|local}] - Node S

Commands: Manual Page Reference - Fujitsu€¦ · cluster show.....70 cluster contact-info...

Documents

Transcript of Commands: Manual Page Reference - Fujitsu€¦ · cluster show.....70 cluster contact-info...