netapp_management

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
netapp_management [2021/01/07 11:17] andonovjnetapp_management [2021/01/19 13:15] (current) – [System] andonovj
Line 3: Line 3:
  
  
-=====Disk Management=====+=====Disk Management (Simulator)=====
 Now, in order to make some use of our Virtualised storage, we need to add some disks. Now, in order to make some use of our Virtualised storage, we need to add some disks.
  
Line 28: Line 28:
 After that, we can safetly reboot the machine. Once the machines boots, we have to fix a common problem with the simulator. After that, we can safetly reboot the machine. Once the machines boots, we have to fix a common problem with the simulator.
 The simulator often crashes because of the insufficient space in the root aggregate. So, we have to assign all disks this node and remove & disable the snapshots The simulator often crashes because of the insufficient space in the root aggregate. So, we have to assign all disks this node and remove & disable the snapshots
 +
 +=====General Management=====
 +In this section we will review general disk management for both: simulator and real environment:
  
 ====Assign Disks & Remove / Disable snapshot==== ====Assign Disks & Remove / Disable snapshot====
Line 48: Line 51:
  
 {{:netappincreasevolspace.jpg?500|}} {{:netappincreasevolspace.jpg?500|}}
 +
 +====Create Aggregate====
 +
 +
 +====Create Volume====
 +=====Privilege Levels=====
 +On NetApp, we have several privilege levels:
 +
 +  * Admin - Most commands and parameters are available at this level. They are used for common or routine tasks.
 +  * Advanced - Commands and parameters at this level are used infrequently, require advanced knowledge, and can cause problems if used inappropriately. You use advanced commands or parameters only with the advice of support personnel.
 +  * Diagnostic (locked by default) - Diagnostic commands and parameters are potentially disruptive. They are used only by support personnel to diagnose and fix problems.
 +
 +
 +Let's see how to enter and use each of them:
 +
 +====Admin====
 +The admin privilege is default privilege level which you have when you enter with the management IP and username & password which you specify when you create the cluster.
 +
 +
 +<Code:bash|Code>
 +login as: admin
 +Keyboard-interactive authentication prompts from server:
 +| Password:
 +End of keyboard-interactive prompts from server
 +
 +This is your first recorded login.
 +Unsuccessful login attempts since last login: 1
 +cluster1::>
 +</Code>
 +
 +As explained above, most of the commands are available in that mode.
 +
 +====Advanced====
 +In advanced privileged level we have additional commands and options. Please be careful, as advanced should be used only with the instructions of NetApp support:
 +
 +To elevate your privileges to Advanced level, use the following syntax:
 +
 +<Code:Bash|Elevate to Advanced>
 +cluster1::> set -privilege advanced
 +
 +Warning: These advanced commands are potentially dangerous; use them only when
 +         directed to do so by NetApp personnel.
 +Do you want to continue? {y|n}: y
 +
 +cluster1::*>
 +</Code>
 +
 +We can check all the commands available in Advanced level:
 +
 +<Code:bash|Advanced Commands>
 +cluster1::*> ?
 +  application>                *Display and manage applications
 +  autobalance>                *The autobalance directory
 +  cluster>                    Manage clusters
 +  event>                      Manage system events
 +  exit                        Quit the CLI session
 +  history                     Show the history of commands for this CLI session
 +  job>                        Manage jobs and job schedules
 +  lun>                        Manage LUNs
 +  man                         Display the on-line manual pages
 +  metrocluster>               Manage MetroCluster
 +  network>                    Manage physical and virtual network connections
 +  protection-type>            *Manage Protection Types and RPOs
 +  qos>                        QoS settings
 +  redo                        Execute a previous command
 +  rows                        Show/Set the rows for this CLI session
 +  run                         Run interactive or non-interactive commands in the nodeshell
 +  security>                   The security directory
 +  set                         Display/Set CLI session settings
 +  snaplock>                   Manages SnapLock attributes in the system
 +  snapmirror>                 Manage SnapMirror
 +  statistics>                 Display operational statistics
 +  statistics-v1>              The statistics-v1 directory
 +  storage>                    Manage physical storage, including disks, aggregates, and failover
 +  storage-service>            *Manage Storage Services
 +  system>                     The system directory
 +  top                         Go to the top-level directory
 +  up                          Go up one directory
 +  volume>                     Manage virtual storage, including volumes, snapshots, and mirrors
 +  vserver>                    Manage Vservers
 +</Code>
 +
 +The commands, ending with "*" are available ONLY in advanced privileged level.
 +
 +====Diagnostic====
 +Diagnostic is to be used by NetApp personal only or by their supervsion and instructions. It can cause permanent failure if used wrongly.
 +
 +To enter into a diagnostic privileged level, use the following command (again only under Netapp personal supervision and guidance)
 +
 +<Code:bash|Elevate to Diagnostic>
 +cluster1::*> set -privilege diagnostic
 +
 +Warning: These diagnostic commands are for use by NetApp personnel only.
 +Do you want to continue? {y|n}: y
 +
 +cluster1::*>
 +</Code>
 +
 +====Legacy====
 +Legacy mode is the old ONTAP7- level of syntax. Unlike the other privileges, the legacy mode operate on the node, rather than the entire cluster level.
 +
 +To enter into legacy mode, use the following command:
 +
 +<Code:bash|Elevate to Legacy>
 +cluster1::*> system node run cluster1-01
 +Type 'exit' or 'Ctrl-D' to return to the CLI
 +cluster1-01>
 +</Code>
 +
 +Where cluster1-01 is the cluster node which you want to manage.
 +
 +====System====
 +System level is very low level management and it is usually done via the Netapp personal instructions.
 +First we have to set the diagnostic level privilege, as before and then we can enable also system level.
 +
 +<Code:bash|Elevate to System level>
 +cluster1::> set -privilege diagnostic
 +
 +Warning: These diagnostic commands are for use by NetApp personnel only.
 +Do you want to continue? {y|n}: y
 +
 +cluster1::*> systemshell local
 +  (system node systemshell)
 +[email protected]'s password:
 +
 +Warning:  The system shell provides access to low-level
 +diagnostic tools that can cause irreparable damage to
 +the system if not used properly.  Use this environment
 +only when directed to do so by support personnel.
 +
 +cluster1-01%
 +</Code>
 +
 +
  • netapp_management.1610018220.txt.gz
  • Last modified: 2021/01/07 11:17
  • by andonovj