{"id":797,"date":"2010-10-26T12:22:32","date_gmt":"2010-10-26T11:22:32","guid":{"rendered":"http:\/\/vmdamentals.com\/?p=797"},"modified":"2011-12-29T11:41:06","modified_gmt":"2011-12-29T10:41:06","slug":"esxi-and-emc-clariion-registration-issue","status":"publish","type":"post","link":"https:\/\/www.vmdamentals.com\/?p=797","title":{"rendered":"ESXi and EMC CLARiiON registration issue"},"content":{"rendered":"

A collegue of mine, John Grinwis, pointed out a bug within a combination of ESXi, host profiles and an EMC CLARiiON: At some point the ESXi nodes swap their VMkernel ports and the CLARiiON then proceeds to register the wrong network as the management network<\/p><\/blockquote>\n

UPDATE: There now is a workaround available. Please visit Workaround: ESXi and EMC CLARiiON registration issue<\/a><\/strong>
\n

\n
\nThere appears to be a bug somewhere in vSphere 4.1 host profiles (I’ve been told by Duco Jaspars vSphere 4.0 is ok): The hosts in this situation have two VMkernel ports: management and VMotion. A pretty ordinary setup I’d say. But at some point the host profiles managed to mix up the VMKernel port numbers:<\/p>\n

correct one:
\n
\nC:Program FilesVMwareVMware vSphere CLIbin>vicfg-vmknic.pl --server x.y.z.45 -list<\/code><\/p>\n\n\n\n\n\n
Interface<\/td>\nPort Group\/DVPort<\/td>\nIP Family<\/td>\nIP Address<\/td>\n<\/tr>\n
vmk0<\/td>\nManagement Network<\/td>\nIPv4<\/td>\nx.y.z.45<\/td>\n<\/tr>\n
vmk1<\/td>\nVMotion<\/td>\nIPv4<\/td>\nm.n.p.24<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

incorrect one:
\n
\nC:Program FilesVMwareVMware vSphere CLIbin>vicfg-vmknic.pl --server x.y.z.44 -list<\/code><\/p>\n\n\n\n\n\n
Interface<\/td>\nPort Group\/DVPort<\/td>\nIP Family<\/td>\nIP Address<\/td>\n<\/tr>\n
vmk0<\/td>\nVMotion<\/td>\nIPv4<\/td>\nm.n.p.23<\/td>\n<\/tr>\n
vmk1<\/td>\nManagement Network<\/td>\nIPv4<\/td>\nx.y.z.44<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You can clearly see, that the incorrect node has its Management and VMotion VMKx numbers reversed. This causes a connected CLARiiON to negotiate the wrong management IP address:
\n\"CLARiiON<\/p>\n

This raises another issue though. Because one can discuss about where this error comes from exactly.<\/p>\n

    \n
  • You could blame the host profiles, but then again, why should VMK0 always be the management interface?<\/li>\n
  • You could blame the CLARiiON, because it just uses VMK0 instead of the real management interface. But then again, what to do if you configure two VMkernels for management?<\/li>\n
  • You could blame the VMware-CLARiiON interfacing logic. I guess that would be the right one, somewhere you simply NEED to configure which VMkernel interface should be used by the Clariion…<\/li>\n<\/ul>\n

    I hope VMware\/EMC fixes this issue soon; host profiles are simply toooo easy \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

    A collegue of mine, John Grinwis, pointed out a bug within a combination of ESXi, host profiles and an EMC CLARiiON: At some point the ESXi nodes swap their VMkernel ports and the CLARiiON then proceeds to register the wrong network as the management network UPDATE: There now is a workaround available. Please visit Workaround: […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77,5],"tags":[127,126,125,124,632,128,129],"class_list":["post-797","post","type-post","status-publish","format-standard","hentry","category-storage","category-vmware","tag-clariion","tag-emc","tag-esxi","tag-vmkernel","tag-vmware","tag-wrong-vmk","tag-wrong-vmkernel"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/797","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=797"}],"version-history":[{"count":28,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/797\/revisions"}],"predecessor-version":[{"id":3551,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=\/wp\/v2\/posts\/797\/revisions\/3551"}],"wp:attachment":[{"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=797"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=797"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vmdamentals.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=797"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}