<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multipathing on the bin</title><link>https://thebin.net/tags/multipathing/</link><description>Recent content in Multipathing on the bin</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 19 May 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://thebin.net/tags/multipathing/index.xml" rel="self" type="application/rss+xml"/><item><title>Solaris Networking: Datalink Multipathing Protocol</title><link>https://thebin.net/2014/05/solaris-networking-datalink-multipathing-protocol/</link><pubDate>Mon, 19 May 2014 00:00:00 +0000</pubDate><guid>https://thebin.net/2014/05/solaris-networking-datalink-multipathing-protocol/</guid><description>&lt;p&gt;In this article we are going to go over Datalink Multipathing Protocol (DLMP) available in Solaris.  DLMP is similar to IPMP, however there are some key differences, the biggest being the layer at which it operates.  DLMP operates at the datalink layer of the OSI model, while IPMP operates at the network layer.  Due to the differences in those layers DLMP opens up a lot of possibilities that were not possible with IPMP.  For example if you had a requirement for redundant networking for a service, either IPMP and DLMP would both be able to meet that requirement very well.  However if you had a requirement that the service runs inside of a zone or a logical domain then the level of work in IPMP becomes much higher.  This is because these hypervisors assign datalink devices to their guests.  Since the redundancy for IPMP is built on a level higher we need to assign multiple non-redundant interfaces to the guests and then build the interfaces and IPMP groups inside each of the guests.&lt;/p&gt;</description></item></channel></rss>