BROCADE IP PRIMER

Console49F Link 50F1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 47Power1F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 48Console49F Link 50F1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 47Power1F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 48424C424C424C424C424C424C424C424C424C424C424C424CPwrPwrActiveActiveConsoleConsole10/100/1000Ethernet10/100/1000EthernetFastIron SX800FastIron SX800LinkActLinkAct1 Link1 LinkActAct22424C424C424C424C424C424C424C424C424C424C424C424CPwrPwrActiveActiveConsoleConsole10/100/1000Ethernet10/100/1000EthernetLinkActLinkAct1 Link1 LinkActAct2249FLinkPower49FLinkPower50FConsole1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 471F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 4850FConsole1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 471F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 48424C424C424C424C424C424C424C424C424C424C424C424CPwrPwrActiveActiveConsoleConsole10/100/1000Ethernet10/100/1000EthernetFastIron SX800FastIron SX800LinkActLinkAct1 Link1 LinkActAct49FLinkPower49FLinkPower50F2Console424C424C424C424C424C424C1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 471F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 4850F2Console424C424C424C424C424C424C1 3 5 7 9 1113 15 17 19 21 2325 27 29 31 33 3537 39 41 43 45 471F 2F 3F 4F2 4 6 8 10 1214 16 18 20 22 2426 28 30 32 34 3638 40 42 44 46 48PwrPwrActiveActiveConsoleConsole10/100/1000Ethernet10/100/1000EthernetLinkActLinkAct1 Link1 LinkActAct22Chapter 9: Spanning Tree ProtocolWe would configure Core Switch A and Core Switch B with VSRP. They wouldhold an election to see which of them should be considered Master. Let's saythat the election results in Core Switch A becoming the Master. Core Switch Bwould now be the Backup. Traffic will not be forwarded on Core Switch B'slinks. Core Switch B would only listen for Hello packets from Core Switch A (theMaster).Core ACore BMasterBackupThe three lower switches, in this scenario, do not have to be VSRP-aware. Infact, they don't even have to be Brocade switches. VSRP-aware switches willfailover faster. This is something to consider when designing an infrastructurelike this.The Master switch (Core Switch A) is now forwarding traffic and is also sendingHello packets to the Backup (Core Switch B). Hello packets are sent out all ofthe VSRP ports on the Master switch (it's a good idea to have more than one).When the Backup stops receiving Hello packets after a defined period of time,it presumes that the Master is dead, and it assumes the role of Master. CoreSwitch B's links are now active, and Core Switch A's links are not.Core ACore BMasterThe failover time for VSRP is similar to RSTP. It's sub-second (for VSRP-awareswitches). In this example, we've used one Master and one Backup. Dependingon configuration, an election can result in one Master and up to fourBackup switches.To configure VSRP, let's presume that all the links in our diagram are in thesame VLAN (VLAN 10). Within VLAN 10's config, we need to define a VirtualRouter ID (VRID).212 Brocade IP Primer