Enterprise Technology By Phil Edholm

Cisco VSS….too little, too late?

As I discussed in a previous set of blog postings, delivering redundancy is a critical path to assuring overall system availability. For a number of years, Nortel has deployed a patented implementation called Split Multi Link Trunking (SMLT) that uses the IEEE 802 standard in a configuration that is active-active with incredibly low switchover time. When compared with traditional techniques, such as spanning tree or routing, this technique has been judged vastly superior by both our customers and by independent testing organizations such as the Tolly Group. Nortel has deployed this technology for over six years to deliver effective Switch Clustering in a number of Ethernet Switching platforms. This is important, as the Nortel Switch Clustering means small and medium enterprise customers don't have to compromise on resiliency as Nortel offers a range of products that meet their architecture needs.

The recent Cisco announcement of their long awaited Virtual Switching System for the Catalyst 6500 LAN Switch is a dramatic endorsement that delivering redundancy is a very real networking challenge. Without a form of technology guaranteeing active-active redundancy, networks are mired in the 90s. Cisco’s VSS announcement clearly confirms there are significant deficiencies in their current offers based on various combinations of spanning tree and routing. However, the announcement also seems to expose serious flaws in Cisco’s latest attempt to tackle active-active redundancy. I thought it would be interesting to contrast the new Cisco VSS with the proven Nortel SMLT solution and see what the critical differences are. It is important to note that all of my comments are based on publicly available data, and any erroneous interpretations are not intentional, but may be a result of the limited information Cisco has chosen to release about it's VSS system.

From the announcements, it would appear that Virtual Switching System (VSS) is only available on the top-of-the-range, fully-loaded Catalyst 6500 Switch. Fitted with the Supervisor 720-10GE module; the Virtual Switch Link (VSL) must be made with 10G Ethernet connections, using either the 10G ports on the Sup720 or those on the X6708-10GE with DFC3/CXL Interface module. Further, in order for the system to work, it appears all interfaces in the chassis must have the latest DFC functionality installed, potentially causing an expensive upgrade for any older modules. SMLT, on the other hand, works across all the modules in a Nortel 8600 and does not require card level upgrades or specialized interfaces.

The Cisco VSS seems to essentially turn two switches into a single chassis by connecting the control processors together across the VSL. While in some cases this may have limited advantages in configuration and management, it would appear to have serious implementation drawbacks. Between two switches operating as a VSS pair, there can only be 2 Sup720 modules. This means that when there is a failure or other reason to take one of the chassis down (for re-configuration for example), the remaining chassis will only have a single processor, exposing it to failure issues. In the Nortel implementation, each chassis can have both a primary and secondary processor, essentially doubling the overall redundancy at minimal cost. This leads to two other questions that can only be answered with testing; does having a single Sup720 supporting 2 chassis over a VSL result in reduced operating capacity or other performance issues and does the encapsulation techniques used on the VSL result in performance issues in latency or scale during large scale failures? The Nortel Switch Clustering using SMLT has proven that it excels in both scaling and transitions as it enables dual active processors in each chassis and does not use proprietary encapsulation on the inter-switch links.

Finally, it is not clear if or how the VSS can interoperate with open MLT access devices such as wiring closet switches and server NICs. A critical strength of the SMLT solution is seamless integration with standards based MLT devices. The SMLT solutions do not require special software and have proven interoperability with a number of other vendors wiring closet switches, including Cisco as well as a wide variety of NICs in servers. In fact, Nortel SMLT has been identified by VMWare as the optimal solution for multi-connections in a VMWare virtualization environment. While it appears that the VSS uses software in the access devices for some levels of functionality, it is not clear whether or how it performs in an open multi-vendor environment and how this limits functionality when the devices are not Cisco..

All of this means that network architects now have to decide which Cisco design methodology to use – VSS, L3 or traditional Spanning Tree– and very serious budget considerations must come into play. The promotion of yet another non Standard-based approach means further concern about customer choice.

I think it is time for a reality-check. Do we really need more Cisco proprietary technology to make our networks and businesses more complex? Clearly the answer is ‘no’, and Cisco’s move is in direct conflict with recent discussions within the Analyst, Media, and User communities: Cisco’s solutions are increasingly recognised as being expensive and not worth the price delta. I believe users should actively avoid the use of proprietary solutions that lead to single vendor lock-in.

Nortel has established a proven track record with our SMLT and Switch Clustering architecture for more than six years now, delivering deterministic application reliability and availability, all with a fully open and tested interoperable model. The real beauty of Nortel’s solution is that the principle business benefits are consistently delivered across the portfolio (both in multiple product and platforms as well as a variety of interface speeds), and appropriately scaled and priced for deployment from corporate headquarters to regional offices. This enables businesses to enjoy consistent service delivery and applications reliability, further enhancing application usage, performance, and value.

However, I would like to thank Cisco for endorsing the need for the technology leadership that Nortel has demonstrated and for recognizing some of the issues with their previously proposed implementations.

Trackbacks/Pings

  1. […] as well as a penchant for trying to present attempts at catch-up as innovation - see my post on VSS. In the VSS case, the Cisco technology is proprietary and appears to be a pathetic effort to […]

Comments

  1. Cisco is deploying another piece of propritary hardware?Say it ain’t so.

    This sounds ike nothing more than a 10GigE “bus” between two Catalyst switches. It does bring the question up in my mind, is VSS incompatible with other redundancy arrangements such as HSRP/VRRP/GLBP and spanning tree? (Could you mix implementations on the same network or subnet)? If not, transitions could be painful. I also wonder if there are other configuration/implementation issues such as hidden subnets and L3 addressing restrictions?

    It appears as if this can only be set up as 1+1 sparing, I would have expected that N+1 or better yet, N+N sparing would be available.

    I still say Nortel needs to make SMLT easier for others to incorporate. Pick a partner and implement SMLT with their kit, I bet you both sell more boxes.

  2. So with VSS you no longer need HSRP/VRRP/GLBP/STP to answer the previous comment. Most of the drawbacks that have been illustrated above are limitations of the initial release of the feature set and I’m sure will be addressed. I would love to see a side by side comparison for SMLT and VSS, given that this blog entry only is intended to touch on the limitations of the Cisco VSS feature.

  3. Another point of contention is that VSS allows multiple (currently 2) switches to appear as one logical entity. So from a management and troubleshooting perspective as en engineer this is a very appealing feature. SMLT at least from what I’ve seen is nothing more than an advanced link aggregation protocol. It would appear to me that we are compaing apples to oranges.

  4. Doesn’t Nortel SMLT still require you to disable STP? Maintain two configurations? Limit of vlans (1980)?

  5. Nortel SMLT is very simple to implement. Basically, you configure the MLT (Multilink Trunk) and specify an SMLT ID on both Nortel switches. It’s the SMLT ID that allows the pair of switches to act as one and associate MAC addresses of connected devices to the same entity. Downstream devices simply configure themselves with whatever 802.3ad compliant link aggregations (including EtherChannel) and are unaware that there is a pair of Nortel switches. All links active (unlike STG), rapid failover (link state change detection time ~ 500ms) and vastly simplified operations (no spanning or multiple spanning tree groups, hitless software upgrades, etc.).

    Many server vendor have incorporated Nortel SMLT into their spec books. Check the IBM Redbook for Blade Server as an example.

  6. VSS /SMLT came from Inkra Networks about two years ago.

  7. the unspoken competion between nortel and cisco i am sure will lead us to a more dynamic ip world.

  8. WOW!!! - I thought this post would generate lots of comments….I guess that, like the VSS announcement it is generating Very Small Stimulation in the market……

    Many, I agree that we should look into how to extend SMLT beyond the open wiring closet interface.

  9. Amazing that this critique of VSS came up at such a high level when I did a search for Cisco VSS on Google. I wander what Nortel paid for that!
    I suppose your critisism of Cisco is based on the overall market penetration of Nortel. After all, I have noticed Nortel taking vast chunks of the networking market from Cisco recently, so they must have a better product, right? Oh, they aren’t? I’m sorry, the impression that I got from this blog entry was that Nortel was so superior to Cisco and has such better technology that Cisco might as well lock their doors! Hmm… better take a closer look, fellas, and stop letting that paycheck blind you from reality…

  10. It’s interesting that you say ” Do we really need more Cisco proprietary technology to make our networks and businesses more complex”

    Is Nortel SMLT “open source”????????????

    give me a break

  11. SMLT uses standard MLT in the wiring closet nodes. It does not require any proprietary software in the majority of devices, only using special software int he core switches.

  12. VSS is very new - so a comparison at this stage of its release is a little unfair - I’m sure that Nortel’s solution underwent some maturing.
    VSS is very simple - the Sup720-10GE allows two 6500 switches to be virtualised and managed as one single switch. This removes the need for HRSP/STP and similar redundancy protocols. Although the Sup itself has only two 10GE ports each, further 10GE ports on other line cards can be included to increase bandwidth. There very little encapsulation bandwidth and on a 10GE+ link is nothing.

    This is a recent article that might interest readers:
    http://www.networkworld.com/reviews/2008/010308-cisco-virtual-switching-test.html?page=1

  13. Jim, I wanted to respond to your “pay to play” comment. As the author of the blog, I did not, and am not aware of any activity that paid for any placement. There have been a number of references to this blog as well as minimal other commentary.
    I stand by the value of our products in both simplicity and performance.

  14. I missed Mark’s comment about SMLT longevity. Actually SMLT has been available in products for over 6 years and is well proven in thousands of installations.

  15. Phils said :”It [SMLT] does not require any proprietary software in the majority of devices, only using special software int he core switches.”

    This is no different than a VSS. A VSS will allow any device that supports 802.3ad to form a Multi-chassis EtherChannel with the two switches that make up the VSS. This is not a requirement, though, since they also support Cisco’s PAgP as well as straight EtherChannel with no protocol.

  16. There are several things that are wrong in Phil’s original post :

    1. All linecards do not require a DFC in the chassis that make up the VSS.

    2. The comment about having single chassis exposure ignores the fact that a large number of customers deploy single Supervisor chassis in pairs using HSRP / VRRP / GLBP today. These deployments are just as vulnerable to single chassis exposure, so there is no increase in risk.

    3. The Networkworld test verfied that over 700Mpps could be passed through the VSS, so the performance concern is a non-issue. As for latency, VSS with MEC actually reduces latency as there will be fewer hops taken by packets.

    4. As has been previously mentioned, VSS operates with 802.3ad-compliant devices as well as devices that support PAgP and EtherChannel with no protocol. VSS does not use software in the access device.

    Please feel free to ask any further VSS questions.

  17. Hi,

    I want a layer 2 redundacny between Nortel 8600-2 and Cisco 6500-2 switches.
    We know VSS works with Cisco and smlt with Nortel
    But my question here is how do we integrate them in terms of configuration and physcial connectivity.
    Also do let me know the network design considerations if any available.

    Thanks in Advance

Leave a Reply