{"id":978,"date":"2016-04-08T06:20:43","date_gmt":"2016-04-08T06:20:43","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2016\/04\/08\/stretched-l2-domains-vmotion\/"},"modified":"2021-07-27T19:59:57","modified_gmt":"2021-07-27T19:59:57","slug":"stretched-l2-domains-vmotion","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Networking\/Terms-and-Concepts\/stretched-l2-domains-vmotion.html","title":{"rendered":"Stretched L2 Domains + VMotion"},"content":{"rendered":"
https:\/\/packetpushers.net\/podcast\/podcasts\/datanauts-029-evil-behind-long-distance-vmotion-stretched-l2\/<\/a><\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Issues with Layer2 across DCs Ideally, data centers do not share fate. But extending L2 creates a common broadcast domain in 2 data center. Now, we are sharing fate Traffic patterns become sub-optimal Where does the default-gateway live? In the local DC? Or remote? Traffic to load balancer to pool member, but pool member lives … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"yoast_head":"\n