{"id":55,"date":"2010-02-22T23:19:44","date_gmt":"2010-02-23T05:19:44","guid":{"rendered":"http:\/\/www.unifiedcomputingblog.com\/?p=55"},"modified":"2010-02-22T23:19:44","modified_gmt":"2010-02-23T05:19:44","slug":"mac-forwarding-table-aging-on-ucs-6100-fabric-interconnects","status":"publish","type":"post","link":"http:\/\/www.unifiedcomputingblog.com\/?p=55","title":{"rendered":"MAC forwarding table aging on UCS 6100 Fabric Interconnects"},"content":{"rendered":"<p>I was recently forwarded some information on the MAC table aging process in the UCS 6100 Fabric Interconnects that I thought was very valuable to share.<\/p>\n<p>Prior to this information, I was under the impression (and various documentation had confirmed) that the Fabric Interconnect never ages MAC addresses &#8211; in other words, it understands where all the MAC addresses are within the chassis\/blades, and therefore has no need to age-out addresses. \u00a0 In the preferred Ethernet Host Virtualizer mode, it also doesn&#8217;t learn any addresses from the uplinks, again, so no need to age a MAC address.<\/p>\n<p>So what about VMware and the virtual MAC addresses that live behind the physical NICs on the blades?<\/p>\n<p>Well, as it turns out, the Fabric Interconnects <strong>do<\/strong> age addresses, just not those assigned by UCS Manager to a physical NIC (or a vNIC on a Virtual Interface Card &#8211; aka Palo).<\/p>\n<p>On UCS code releases prior to 1.1, learned address age out in 7200 seconds (120 minutes) and is not configurable.<\/p>\n<p>On UCS code releases of 1.1 and later, learned addresses age out in 7200 seconds (120 minutes) by default, but can be adjusted in the LAN Uplinks Manager within UCS Manager.<\/p>\n<p>Why do we care? \u00a0 Well, it&#8217;s possible that if a VM (from which we&#8217;ve learned an address) has gone silent for whatever reason, we may end up purging it&#8217;s address from the forwarding table after 120 minutes&#8230; which will mean it&#8217;s unreachable from the outside world, since we&#8217;ll drop any frame that arrives on an uplink to an unknown unicast MAC address. \u00a0 Only if the VM generates some outbound traffic will we re-learn the address and be able to accept traffic on the uplinks for it.<\/p>\n<p>So if you have silent VMs and have trouble reaching them from the outside world, you&#8217;ll want to upgrade to the latest UCS code release and adjust the MAC aging timeout to something very high (or possibly never).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was recently forwarded some information on the MAC table aging process in the UCS 6100 Fabric Interconnects that I thought was very valuable to share. Prior to this information, I was under the impression (and various documentation had confirmed) that the Fabric Interconnect never ages MAC addresses &#8211; in other words, it understands where &hellip; <a href=\"http:\/\/www.unifiedcomputingblog.com\/?p=55\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">MAC forwarding table aging on UCS 6100 Fabric Interconnects<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[7,8],"tags":[55],"class_list":["post-55","post","type-post","status-publish","format-standard","hentry","category-ucs-hardware","category-ucs-management","tag-ucsm"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts\/55","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=55"}],"version-history":[{"count":0,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=\/wp\/v2\/posts\/55\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.unifiedcomputingblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}