NetApp HCI, Manual

Page: 128 / 363

curl -u $mnode_user_name:$mnode_password --insecure -X POST \
https://$mnode_IP:442/json-rpc/10.0 \
-H 'Content-Type: application/json' \
-H 'cache-control: no-cache' \
-d ' {
"params": {
"network": {
"$eth1": {
"#default" : false,
"address" : "$storage_IP",
"auto" : true,
"family" : "inet",
"method" : "static",
"mtu" : "9000",
"netmask" : "$subnet_mask",
"status" : "Up",
"virtualNetworkTag" : "$vlan_id"
}
},
"cluster": {
"name": "$mnode_host_name",
"cipi": "$eth1.$vlan_id",
"sipi": "$eth1.$vlan_id"
}
},
"method": "SetConfig"
}
'
Find more Information
• Add an asset to the management node
• NetApp Element Plug-in for vCenter Server
• NetApp HCI Resources Page
Recover a management node
You can manually recover and redeploy the management node for your cluster running
NetApp Element software if your previous management node used persistent volumes.
You can deploy a new OVA and run a redeploy script to pull configuration data from a previously installed
management node running version 11.3 and later.
What you’ll need
• Your previous management node was running NetApp Element software version 11.3 or later with
persistent volumes functionality engaged.