2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
m
→Procedures: Imported stuff from old Wiki
m (→Procedures: Added "Netflow") |
m (→Procedures: Imported stuff from old Wiki) |
||
| Line 109: | Line 109: | ||
|<code> vmware -v </code> || ESX software version and build | |<code> vmware -v </code> || ESX software version and build | ||
|} | |} | ||
=== ESX Shutdown === | |||
* Shutdown a host ready for power off | |||
** <code> shutdown -h now </code> | |||
* Restart a host | |||
** <code> shutdown -r now </code> | |||
=== High Availability Stop/Start === | |||
* Stop HA... | |||
** <code> /etc/init.d/VMWAREAAM51_vmware stop </code> | |||
* Start HA... | |||
** <code> /etc/init.d/VMWAREAAM51_vmware start </code> | |||
== VMWare Managment Agent Restart == | |||
<pre> | |||
service mgmt-vmware restart | |||
Stopping VMware ESX Server Management services: | |||
VMware ESX Server Host Agent Services [ OK ] | |||
VMware ESX Server Host Agent Watchdog [ OK ] | |||
VMware ESX Server Host Agent [ OK ] | |||
Starting VMware ESX Server Management services: | |||
VMware ESX Server Host Agent (background) [ OK ] | |||
Availability report startup (background) [ OK ] | |||
</pre> | |||
If this fails to stop the service, you can try to manually kill the processes. '''Untested - don't do during day, if you use this and it works, delete this warning note.''' | |||
# Determine the PID's of the processes | |||
#* <code> ps -auxwww | grep vmware-hostd </code> | |||
#* which should give you something like, in which case the PID's are 2807 and 2825... | |||
#* <code> root 2807 0.0 0.3 4244 884 ? S Mar10 0:00 /bin/sh /usr/bin/vmware-watchdog -s hostd -u 60 -q 5 -c /usr/sbin/vmware-hostd-support /usr/sbin/vmware-hostd -u </code> | |||
#* <code> root 2825 0.1 12.0 72304 32328 ? S Mar10 1:14 /usr/lib/vmware/hostd/vmware-hostd /etc/vmware/hostd/config.xml -u </code> | |||
#* <code> root 13848 0.0 0.2 3696 556 pts/0 R 08:43 0:00 grep vmware-hostd </code> | |||
# Kill the PID's using <code> kill -p pid </code> | |||
#* So, for example, <code> kill -9 2807 </code> and <code> kill -9 2825 </code> | |||
# Then reattempt the service restart | |||
== Maintenance Mode == | |||
To put the ESX into maintenance mode with no access from the Infrastructure Client (VCP) use the following commands - use with caution | |||
Put esx into maintenance mode: | |||
<pre> | |||
vimsh -n -e /hostsvc/maintenance_mode_enter | |||
</pre> | |||
check the esx is in maintenance mode | |||
<pre> | |||
vimsh -n -e /hostsvc/runtimeinfo | grep inMaintenanceMode | awk ‘{print $3}’ | |||
</pre> | |||
exit maintenance mode | |||
<pre> | |||
vimsh -n -e /hostsvc/maintenance_mode_exit | |||
</pre> | |||
== Virtual Machine Shutdown == | |||
* To determine state of an Virtual Machine running from the local ESX | |||
** <code> vmware-cmd /vmfs/volumes/DEV-LON-SAN/ArbuthTG/ArbuthTG.vmx getstate </code> | |||
** <code> getstate() = on </code> | |||
* Shutdown a Virtual Machine running from the local ESX forcefully | |||
** <code> vmware-cmd /vmfs/volumes/DEV-LON-SAN/ArbuthTG/ArbuthTG.vmx stop hard </code> | |||
** <code> stop(hard) = 1 </code> | |||
== TCPDump Network Sniffer == | |||
Basic network sniffer available in Service Console | |||
[http://www.tcpdump.org/tcpdump_man.html TCPDump instruction manual] | |||
EG To sniff all traffic on the Service Console interface, vswif0, going to/from 159.104.227.40 | |||
<code> tcpdump -i vswif0 host 159.104.224.70 </code> | |||
== Security == | == Security == | ||