Festplattenverteilung (Befehlssammlung)

Anzeige von Festplattenzugehörigkeit zu jeweiligem FC Port
            > storage show disc -p 
Anzeige von Nicht-zugeordneten Disks
            > disk show -n
Zuordnen von Disks:
            > disk assign -o owner diskname  (-s unassigne)
Anzeige von Aggregate Disks, Spare Disks & Partner Disks inkl. Status (Zeroing)
            > sysconfig -r

Root Volume umziehen

Sachverhalt:
Aufgabe ist es ein Root Volume der Netapp umzuziehen. Wir gehen von der Grundannahme aus, dass auf dem Filer Kopf eine vol0(Root Volume) existiert, welches auf dem aggr0 liegt.
(Stand OnTap 7.3.4)

allgemeines Vorgehen:
> cf disable (Cluster Failover disablen)

1. erstellen eines neuen Aggregate mit Namen: aggr1
2. erstellen eines neuen Volumes mit Namen: vol1
       größe des Volume muss mindestens dem vol0 entsprechen! je nach File Typ zwischen 20-30GB;
3. > ndmpd on (falls noch nicht geschehen
4. > ndmpcopy -f /vol/vol0 /vol/vol1 (-f kopiert Systemdateien)
5. > vol options vol1 root (setzt vol1 als neues Root volume ein)
6. reboot des Filers
7. CTRL C für Special Boot Options auswählen
8. Option 5 - in den Maintainance mode wechseln
9. aggr options aggr1 root (setzt aggr1 als neues Root Aggregate ein)
10. > halt
11. > autoboot (Filer fährt wieder hoch)

Nun kann das alte vol0 und danach aggr0 gelöscht werden. Es empfiehlt sich der Übersicht halber das neue aggr1 und vol1 wieder in die alten Namen um zu benennen. Es empfiehlt sich danach den Filer zu rebooten.

Ausschalten von VMs über Konsole

Kommando Konsolen Befehle zum starten und stoppen von VMs (source:vmware KB):

http://kb.vmware.com/kb/1004340

Powering off the virtual machine

To determine if you must use the command line, attempt to power off the virtual machine:

1. Connect VMware Infrastructure (VI) Client to the Virtual Center Server. Right-click on the virtual machine and click Power off.
2. Connect VI Client directly to the ESX host. Right-click on the virtual machine and click Power off.
   If this does not work, you must use the command line method.

Determining the virtual machine's state

1. Determine the host on which the virtual machine is running. This information is available in the virtual machine's Summary tab when viewed in the VI Client page.
2. Log in as root to the ESX host using an SSH client.
3. Run the following command to verify that the virtual machine is running on this host:
   
   # vmware-cmd -l
   The output of this command returns the full path to each virtual machine running on the ESX host. Verify that the virtual machine is listed, and record the full path for use in this process. For example:
   
   # /vmfs/volumes/<UUID>/<VMDIR>/<VMNAME>.vmx
   
4. Run the following command to determine the state in which the ESX host believes the virtual machine to be operating:
   # vmware-cmd <path.vmx> getstate
   
   If the output from this command is getstate() = on, the VirtualCenter Server may not be communicating with the host properly. This issue must be addressed in order to complete the shutdown process.
   If the output from this command is getstate() = off, the ESX host may be unaware it is still running the virtual machine. This article provides additional assistance in addressing this issue.

Powering off the virtual machine while collecting diagnostic information using the vm-support script

 

Use the following procedure when you want to investigate the cause of the issue. This command attempts to power off the virtual machine while collecting diagnostic information. Perform these steps in order, as they are listed in order of potential impact to the system if performed incorrectly.

 

Perform these steps first:

1. Determine the WorldID with the command:
   
   # vm-support -x
   
2. Kill the virtual machine by using the following command in the home directory of the virtual machine:
   
   # vm-support -X <world_ID>
   
   This can take upwards of 30 minutes to terminate the virtual machine.
   
   Note: This command uses several different methods to stop the virtual machine. When attempting each method, the command waits for a pre-determined amount of time. The timeout value can be configured to be 0 by adding -d0 to switch to the vm-support command.

If the preceding steps fail, perform the following steps for an ESX 3.x host:

1. List all running virtual machines to find the VMID of the affected virtual machine with the command:
   # cat /proc/vmware/vm/*/names
   
2. Determine the master world ID with the command:
   # less -S /proc/vmware/vm/####/cpu/status
   
3. Scroll to the right with the arrow keys until you see the group field. It appears similar to:
   Group
   vm.####
   
4. Run the following command to shut the virtual machine down with the group ID:
   
   # /usr/lib/vmware/bin/vmkload_app -k 9 ####

If the preceding steps fail, perform the following steps for an ESX 4.x host:

1. List all running virtual machines to find the vmxCartelID of the affected virtual machine with the command:
   # /usr/lib/vmware/bin/vmdumper -l
   
2. Scroll through the list until you see your virtual machine's name. The output appears similar to:
   vmid=5151       pid=-1  cfgFile="/vmfs/volumes/4a16a48a-d807aa7e-e674-001e4ffc52e9/mdineeen_test/vm_test.vmx"  uuid="56 4d a6 db 0a e2 e5 3e-a9 2b 31 4b 69 29 15 19"  displayName="vm_test"  vmxCartelID=####
   
3. Run the following command to shut the virtual machine down with the vmxCartelID:
   
   # /usr/lib/vmware/bin/vmkload_app -k 9 ####

Powering off the virtual machine using the vmware-cmd command

 

This procedure uses the ESX command line tool, and attempts to gracefully power off the virtual machine. It works if the virtual machine's process is running properly and is accessible. If unsuccessful, the virtual machine's process may not be running properly and may require further troubleshooting.

1. From the Service Console of the ESX host, run the following command:
   vmware-cmd <path.vmx> stop
   
   Note: <path.vmx> is the complete path to the configuration file, as determined in the previous section. To verify that it is stopped, run the command:
   # vmware-cmd <path.vmx> getstate
   
2. From the Service Console of the ESX host, run the command:
   # vmware-cmd <path.vmx> stop hard
   
   Note: <path.vmx> is the complete path to the configuration file, as determined in the previous section. To verify that it is stopped, run the command:
   # vmware-cmd <path.vmx> getstate
   
3. If the virtual machine is still inaccessible, proceed to the next section.

Using the ESX command line to kill the virtual machine

 

If the virtual machine does not power off using the steps in this article, it has likely lost control of its process. You need to manually kill the process at the command line.

 

Caution: This procedure is potentially hazardous to the ESX host. If you do not identify the appropriate process id (PID), and kill the wrong process, it may have unanticipated results. If you are not comfortable with the following procedure, contact VMware Technical Support and open a Service Request. Please refer to this article when you create the SR.

1. To determine if the virtual machine process is running on the ESX host, run the command:
   # ps auxwww |grep -i <VMNAME>.vmx
   
   The output of this command appears similar to the following if the .vmx process is running:
   
   root 3093 0.0 0.3 2016 860 ? S< Jul30 0:17 /usr/lib/vmware/bin/vmkload_app /usr/lib/vmware/bin/vmware-vmx -ssched.group=host/user -# name=VMware ESX Server;version=3.5.0;licensename=VMware ESX Server;licenseversion=2.0 build-158874; -@ pipe=/tmp/vmhsdaemon-0/vmx569228e44baf49d1; /vmfs/volumes/49392e30-162037d0-17c6-001f29e9abec/<VMDIR>/<VMNAME>.vmx
   The process ID (PID) for this process is in bold. In this example, the PID is 3093. Take note of this number for use in the following steps.
   
   Caution: Ensure that you identify the line specific only to the virtual machine you are attempting to repair. If you continue this process for another virtual machine the one in question, you can cause downtime for the other virtual machine.
   If the .vmx process is listed, it is possible that the virtual machine has lost control of the process and that it must be stopped manually.
   
2. To kill the process, run the command:
   
   # kill <PID>
   
3. Wait 30 seconds and check for the process again.
4. If it is not terminated, run the command:
   
   # kill -9 <PID>
   
5. Wait 30 seconds and check for the process again.
6. If it is not terminated, the ESX host may need to be rebooted to clear the process. This is a last resort option, and should only be attempted if the preceding steps in this article are unsuccessful.