Building Network Automation Solutions
6 week online course starting in September 2017

STP in Brocade VCS Fabric – an Interesting Solution after a Long Wait

A few years ago I lambasted the lack of STP support in Brocade’s VCS fabric. It took Brocade over two years to solve the problem, but they finally came up with an interesting end-to-end solution.

Here are a few highlights; for more details read the Configuring STP-type Protocols section in Network OS Administrator Guide.

Supported protocols. Network OS 4.0 and above supports standard STP, RSTP and MSTP, as well as Cisco’s PVST and PVRST in both standalone and fabric mode.

Single STP instance. A fabric of VDX switches behaves as a single STP instance, representing the fabric as a single humongous switch to its STP peers. As far as I know, this is the only fabric solution where numerous switches with independent control and management planes act as a single STP instance (Cisco’s vPC is also a single STP instance, but limited to two switches).

No root bridge enforcement. I’ve seen solutions that require the fabric (or MLAG pair) becoming a root bridge. Other solutions split a bridging domain into small STP domains around a fabric core. VCS fabric has no such limitation – the fabric participates in the regular operation of xSTP and blocks its edge ports as needed.

Internal state synchronization. RBridges (VDX switches) exchange STP information, probably using proprietary extensions to FSPF protocol that VCS fabric uses instead of IS-IS.

Distributed STP calculation. Each RBridge uses information supplied by its FSPF peers (think OSPF or IS-IS topology database), and information received through the fabric edge ports in xSTP BPDUs, to calculate the xSTP state and change the port state of its edge ports. Fabric ports are not affected by xSTP; they use TRILL-based forwarding controlled by FSPF routing protocol.

Summary. Brocade definitely took an interesting approach to STP integration and (within the scope of that approach) executed flawlessly. The solution is obviously totally proprietary, but then we probably gave up the idea of having multi-vendor fabrics years ago.

However, looking at the bigger picture, one has to wonder whether a tight integration with STP is better than fabric-at-core-STP-at-edges approach. If the VCS fabric is not the root bridge, then it propagates topology change events across all STP islands connected to its edge ports. That might be what the customers want, but it might not be the most stable solution.

More information?

I’m running a Data Center Fabrics update session in May 2014 – it will cover new features of Brocade’s Network OS as well as new switches from Cisco, Juniper, Arista and a few other vendors, and the software improvements these vendors made in the last year.

If you’re reading this blog post after May 2014, don’t despair – you can always buy a recording of the webinar, a bundle of all data center webinars, or a subscription that gives you access to all webinars I ever did.

1 comment:

  1. Cisco's FabricPath presents itself to the STP domain as a single switch as well. In contrast to the Brocade solution, the FabricPath domain must be the root bridge for the network and will err-disable CE VLANs which receive superior BPDUs.

    ReplyDelete

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.