{"id":178,"date":"2018-11-17T23:12:52","date_gmt":"2018-11-17T21:12:52","guid":{"rendered":"https:\/\/vmoller.dk\/?p=178"},"modified":"2018-11-17T23:19:06","modified_gmt":"2018-11-17T21:19:06","slug":"lom-warning-in-vmware-on-hpe-gen10-servers","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2018\/11\/17\/lom-warning-in-vmware-on-hpe-gen10-servers\/","title":{"rendered":"VMware &#8220;LOM link&#8221; warning in &#8220;Hardware Health&#8221;"},"content":{"rendered":"<div class=\"mceTemp\">\n<div><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-181\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/1G-LOM-error.jpg\" alt=\"\" width=\"1606\" height=\"545\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/1G-LOM-error.jpg 1606w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/1G-LOM-error-300x102.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/1G-LOM-error-768x261.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2018\/11\/1G-LOM-error-1024x347.jpg 1024w\" sizes=\"auto, (max-width: 1606px) 100vw, 1606px\" \/><\/div>\n<\/div>\n<p>For quite some time I have observed a LOM warning in VMware health status tab on an HPE Proliant ML350 Gen10 server. It seems like it reports the warning on two NIC that are down, even though there are unused by ESXi.<\/p>\n<p><!--more-->Warning<br \/>\n[Device] I\/O Module 3 LOM_Link_P3<br \/>\n[Device] I\/O Module 4 LOM_Link_P4<\/p>\n<p>The new ILO5 version 1.37 seems to have fixed the issue \u2013 if the warning persists after updating, then try to clear the IML log on the ILO.<br \/>\nHappy updating!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For quite some time I have observed a LOM warning in VMware health status tab on an HPE Proliant ML350 Gen10 server. It seems like it reports the warning on two NIC that are down, even though there are unused by ESXi.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[20,31,6,7],"tags":[23,30,29,17,24,4],"class_list":["post-178","post","type-post","status-publish","format-standard","hentry","category-esxi","category-hpe","category-vmware","category-vsphere","tag-esxi","tag-gen10","tag-hpe-server","tag-patching","tag-vcenter","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=178"}],"version-history":[{"count":5,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/178\/revisions"}],"predecessor-version":[{"id":186,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/178\/revisions\/186"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}