{"id":272,"date":"2014-11-06T12:39:17","date_gmt":"2014-11-06T17:39:17","guid":{"rendered":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/?p=272"},"modified":"2014-11-06T13:57:26","modified_gmt":"2014-11-06T18:57:26","slug":"updating-vmware-server-via-esxi-shell","status":"publish","type":"post","link":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/?p=272","title":{"rendered":"Updating Vmware Server via esxi shell"},"content":{"rendered":"<p>Here are the steps you need to follow to do an update to a ESXi5.5 server from the command line:<\/p>\n<p>Taken from the following guide:<\/p>\n<p>https:\/\/pubs.vmware.com\/vsphere-51\/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-E51C5DB6-F28E-42E8-ACA4-0EBDD11DF55D.html<\/p>\n<p>Note: \u00a0You must run the following to enable https access for esxcli:<\/p>\n<pre>esxcli network firewall ruleset set -e true -r httpClient<\/pre>\n<p>1. Find an update profile to use:<\/p>\n<pre>esxcli software sources profile list \\ \r\n--depot=https:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml | grep 201410<\/pre>\n<p>The | is optional but you can grep for later versions.<\/p>\n<p>2. Check with dryrun<\/p>\n<pre>esxcli software profile update --dry-run -d \\\r\nhttps:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml \\\r\n -p ESXi-5.5.0-201410001001s-standard\r\n\r\nEnter Maintenance mode:\r\n\r\n<\/pre>\n<p class=\"P_ProcedureHead\"><a name=\"992378\" shape=\"rect\"><\/a>To enter maintenance mode<\/p>\n<table border=\"0\" summary=\"\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\"><\/td>\n<td colspan=\"1\" rowspan=\"1\" width=\"100%\">\n<pre class=\"L1F_List1First_inner\"><a name=\"992379\" shape=\"rect\"><\/a>\u00a0<span class=\"C_Command\">esxcli &lt;conn_options&gt; system maintenanceMode set --enable true<\/span> \r\nto enter maintenance mode.<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p class=\"B1_BodyIndent\"><a name=\"992380\" shape=\"rect\"><\/a>After all virtual machines on the host have been suspended or migrated, the host enters maintenance mode. You cannot deploy or power on a virtual machine on hosts in maintenance mode.<\/p>\n<div class=\"L1_List1_outer\">\n<table border=\"0\" summary=\"\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td colspan=\"1\" rowspan=\"1\"><\/td>\n<td colspan=\"1\" rowspan=\"1\" width=\"100%\">\n<pre class=\"L1_List1_inner\"><a name=\"992381\" shape=\"rect\"><\/a>\u00a0<span class=\"C_Command\">esxcli &lt;conn_options&gt; system maintenanceMode set --enable false<\/span> to have a host exit maintenance mode.<\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>3. Use that profile to update:<\/p>\n<pre>esxcli software profile update -d \/\r\nhttps:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml \\\r\n-p ESXi-5.5.0-201410001001s-standard<\/pre>\n<p>4. Review Event log &#8211; you should see an installation message like the following:<\/p>\n<pre>Successfully installed 17 VIB(s), removed 16 VIB(s). Please use 'esxcli software profile get' or see\r\n log for more detail about the transaction.<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Here are the steps you need to follow to do an update to a ESXi5.5 server from the command line: Taken from the following guide: https:\/\/pubs.vmware.com\/vsphere-51\/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-E51C5DB6-F28E-42E8-ACA4-0EBDD11DF55D.html Note: \u00a0You must run the following to enable https access for esxcli: esxcli network firewall ruleset set -e true -r httpClient 1. Find an update profile to use: esxcli [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/posts\/272"}],"collection":[{"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=272"}],"version-history":[{"count":14,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/posts\/272\/revisions"}],"predecessor-version":[{"id":286,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=\/wp\/v2\/posts\/272\/revisions\/286"}],"wp:attachment":[{"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=272"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.cs.toronto.edu\/~jhancock\/wlog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}