{"id":2765,"date":"2015-04-24T11:00:38","date_gmt":"2015-04-24T01:00:38","guid":{"rendered":"https:\/\/www.penguinpunk.net\/blog\/?p=2765"},"modified":"2015-06-01T14:45:19","modified_gmt":"2015-06-01T04:45:19","slug":"vmware-vsphere-5-5-u2-workarounds-and-random-things-part-2","status":"publish","type":"post","link":"https:\/\/www.penguinpunk.net\/blog\/vmware-vsphere-5-5-u2-workarounds-and-random-things-part-2\/","title":{"rendered":"VMware &#8211; vSphere 5.5 U2 Workarounds and Random Things &#8211; Part 2"},"content":{"rendered":"<p>In a <a title=\"VMware \u2013 vSphere 5.5 U2 Workarounds and Random Things \u2013 Part 1\" href=\"https:\/\/www.penguinpunk.net\/blog\/vmware-vsphere-5-5-u2-workarounds-and-random-things-part-1\/\" target=\"_blank\">previous post<\/a>, I mentioned I was doing a vSphere deployment sitting on some <a title=\"HP Servers Support &amp; Certification Matrix\" href=\"http:\/\/h17007.www1.hp.com\/us\/en\/enterprise\/servers\/supportmatrix\/vmware.aspx\" target=\"_blank\">HP blades with SD cards installed<\/a>. Because of this, I had to configure a few different parts of ESXi to point to network services rather than using local, persistent storage. This isn&#8217;t a bad thing in any case, as you really want your logs and core dumps to be off-host when you&#8217;re trying to troubleshoot host issues.<\/p>\n<p>&nbsp;<\/p>\n<p><em>Network Dump Collector<\/em><\/p>\n<p>It&#8217;s a good idea to have your core dumps going to a central location. you can do this with <a title=\"Configuring an ESXi 5.x host to capture a VMkernel coredump from a purple diagnostic screen via the Network Dump Collector\" href=\"http:\/\/kb.vmware.com\/kb\/2002955?src=vmw_so_vex_dfrit_205\" target=\"_blank\">Network Dump Collector<\/a> or via <a title=\"Configuring a diagnostic coredump partition on an ESXi 5.x host (2004299)\" href=\"http:\/\/kb.vmware.com\/kb\/2004299?src=vmw_so_vex_dfrit_205\" target=\"_blank\">shared diagnostic storage<\/a>. In this instance, I&#8217;ve provided an example on how to configure the host to use the Network Dump Collector, which can be installed from the vCenter installation media.<\/p>\n<p>&nbsp;<\/p>\n<pre><strong>login as: root<\/strong>\r\n<strong> Using keyboard-interactive authentication.<\/strong>\r\n<strong> Password:<\/strong>\r\n<strong> The time and date of this login have been sent to the system logs.\r\n\r\n<\/strong><strong>VMware offers supported, powerful system administration tools.\u00a0 Please<\/strong>\r\n<strong> see www.vmware.com\/go\/sysadmintools for details.\r\n\r\n<\/strong><strong>The ESXi Shell can be disabled by an administrative user. See the<\/strong>\r\n<strong> vSphere Security documentation for more information.<\/strong>\r\n<strong> ~ # esxcli system coredump network get<\/strong>\r\n<strong> Enabled: false<\/strong>\r\n<strong> Host VNic:<\/strong>\r\n<strong> Network Server IP:<\/strong>\r\n<strong> Network Server Port: 0<\/strong>\r\n<strong> ~ # esxcli system coredump network set --interface-name vmk0 --server-ipv4\u00a0192.168.0.100 --server-port 6500<\/strong>\r\n<strong> ~ # esxcli system coredump network set --enable true<\/strong>\r\n<strong> ~ # esxcli system coredump network get<\/strong>\r\n<strong> Enabled: true<\/strong>\r\n<strong> Host VNic: vmk0<\/strong>\r\n<strong> Network Server IP:\u00a0192.168.0.100<\/strong>\r\n<strong> Network Server Port: 6500<\/strong>\r\n<strong> ~ # esxcli system coredump network check<\/strong>\r\n<strong> Verified the configured netdump server is running<\/strong>\r\n<strong> ~ # \/sbin\/auto-backup.sh<\/strong>\r\n<strong> Files \/etc\/vmware\/dvsdata.db and \/tmp\/auto-backup.1942245\/\/etc\/vmware\/dvsdata.db differ<\/strong>\r\n<strong> Saving current state in \/bootbank<\/strong>\r\n<strong> Clock updated.<\/strong>\r\n<strong> Time: 05:04:38\u00a0\u00a0 Date: 04\/21\/2015\u00a0\u00a0 UTC<\/strong>\r\n<strong> ~ #<\/strong><\/pre>\n<p>&nbsp;<\/p>\n<p>It&#8217;s important to check that the <a title=\"Determining whether the vSphere ESXi Network Dump Collector service is running (1039058)\" href=\"http:\/\/kb.vmware.com\/kb\/1039058?src=vmw_so_vex_dfrit_205\" target=\"_blank\">Network Dump Collector service is running<\/a>, too.<\/p>\n<p>&nbsp;<\/p>\n<p><em>vSphere Syslog Server<\/em><\/p>\n<p>You&#8217;ll also want to point your syslogs to a remote location. If you don&#8217;t have access to syslog in your environment, you can set it up from the vCenter installation media. Here&#8217;s <a title=\"Configuring syslog on ESXi 5.x and 6.0 (2003322)\" href=\"http:\/\/kb.vmware.com\/kb\/2003322?src=vmw_so_vex_dfrit_205\" target=\"_blank\">an article on how to do that<\/a>. Here&#8217;re the rough steps you need to take.<\/p>\n<p>Check your current configuration first.<\/p>\n<pre><strong>~ # esxcli system syslog config get<\/strong>\r\n<strong> Default Network Retry Timeout: 180<\/strong>\r\n<strong> Local Log Output: \/scratch\/log<\/strong>\r\n<strong> Local Log Output Is Configured: false<\/strong>\r\n<strong> Local Log Output Is Persistent: false<\/strong>\r\n<strong> Local Logging Default Rotation Size: 1024<\/strong>\r\n<strong> Local Logging Default Rotations: 8<\/strong>\r\n<strong> Log To Unique Subdirectory: false<\/strong>\r\n<strong> Remote Host: &lt;none&gt;<\/strong><\/pre>\n<p>Now you can set the configuration.<\/p>\n<pre><strong>~ # esxcli system syslog config set --loghost='tcp:\/\/192.168.0.100:514'<\/strong><\/pre>\n<p>Load the configuration.<\/p>\n<pre><strong>~ # esxcli system syslog reload<\/strong><\/pre>\n<p>Check that the configuration worked.<\/p>\n<pre><strong>~ # esxcli system syslog config get<\/strong><\/pre>\n<p>Backup the configuration.<\/p>\n<pre><strong>~ # \/sbin\/auto-backup.sh<\/strong><\/pre>\n<p>&nbsp;<\/p>\n<p><em>Persistent Scratch<\/em><\/p>\n<p>I recommend setting a persistent scratch location as well. You can read about that <a title=\"Creating a persistent scratch location for ESXi 4.x\/5.x\/6.0 (1033696)\" href=\"http:\/\/kb.vmware.com\/kb\/1033696?src=vmw_so_vex_dfrit_205\" target=\"_blank\">here<\/a>. In my case I used shared storage with directories for each host. I then set that as an option to configure\u00a0via Host Profiles.<\/p>\n<p>&nbsp;<\/p>\n<p>Okay, so hopefully that was useful for someone. More to follow &#8230;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In a previous post, I mentioned I was doing a vSphere deployment sitting on some HP blades with SD cards installed. Because of this, I had to configure a few different parts of ESXi to point to network services rather than using local, persistent storage. This isn&#8217;t a bad thing in any case, as you [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[54,127,4],"tags":[793,110,589,798,19,786,226,99,151,749],"class_list":["post-2765","post","type-post","status-publish","format-standard","hentry","category-esxi","category-vcenter","category-vmware","tag-esxi","tag-howto","tag-kb","tag-vcenter","tag-virtualisation","tag-vmware","tag-vmware-kb","tag-vmware-tools","tag-vsphere","tag-workarounds"],"_links":{"self":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/2765","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/comments?post=2765"}],"version-history":[{"count":16,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/2765\/revisions"}],"predecessor-version":[{"id":2912,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/posts\/2765\/revisions\/2912"}],"wp:attachment":[{"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/media?parent=2765"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/categories?post=2765"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.penguinpunk.net\/blog\/wp-json\/wp\/v2\/tags?post=2765"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}