When I was listening to the Intelligent Redundant Framework (IRF) presentation from HP during the Tech Field Day 2010 and read the HP/H3C IRF 2.0 whitepaper afterwards, IRF looked like a technology sent straight from Data Center heavens: you could build a single unified fabric with optimal L2 and L3 forwarding that spans the whole data center (I was somewhat skeptical about their multi-DC vision) and behaves like a single managed entity.
No wonder I started drawing the following highly optimistic diagram when I was updating my Data Center 3.0 webinar, which now includes information on Multi-Chassis Link Aggregation (MLAG) technologies from numerous vendors (as always, attendees of past webinars get free access to updated materials and recordings).
However, the worm of doubt was continuously nagging somewhere deep in my subconsciousness, so I decided to check the configuration guides of various HP switches (kudos to HP for the free and unrestricted access to their very good documentation). I selected a core switch (S12508) and an access-layer switch (S5820X-28S) from the HP IRF technology page, downloaded their configuration guides and studied the IRF chapters. What a disappointment:
- Only devices of the same series can form an IRF. How is that different from any other stackable switch vendor?
- Only two core switches can form an IRF. How is that different from Cisco’s VSS or Juniper’s XRE200?
- One device in the IRF is the master, others are slaves. Same as Cisco’s VSS.
- Numerous stackable switches can form an IRF. Everyone else is calling that a stack.
- IRF partition is detected through proprietarily modified LACP or BFD. Same as Cisco’s VSS.
- After IRF partition, the loser devices block their ports. The white paper is curiously mum about the consequences of IRF partition. No wonder, IRF does the same thing as any other vendor – the losing part of the cluster blocks its ports following a partition.
There might be something novel in the IRF technology that I’ve missed and that truly sets it apart from other vendors' solutions. If that’s the case, please chime in with your comments. For the moment, IRF looks like stacking-as-usual to me.