tag:blogger.com,1999:blog-22921684.post116423508647989206..comments2023-05-12T08:13:38.639+01:00Comments on The Storage Architect: Brocade on the upChris M Evanshttp://www.blogger.com/profile/05633427140097100466noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-22921684.post-1167536292050436822006-12-31T03:38:00.000+00:002006-12-31T03:38:00.000+00:00I get disappointed at Cisco bagging when it seems ...I get disappointed at Cisco bagging when it seems obvious that people don't know the power of the MDS switches. IMHO, Brocade has lots to catch up on. One thing in particular about VSANs is that each one runs its own services which protects other VSANs from interference. Eg, each VSAN runs its own FCNS. Now if your Brocade fabric took a dive and the FCNS got totally screwed up, there goes the fabrics method of knowing where to send its data. Each VSAN also has QOS, in order delivery and FSPF load balancing. Upcoming enhancements to the MDS mean that you can directly plug DWDM SFP's (4 and 10Gbps) into the switch. Currently, you have CWDM at 2 Gpbs. I can create trunking port channels per individual or multiple VSAN's over those new SFP's and give me huge native fibre channel extensions. The list goes on when it comes to VSAN's<BR/><BR/>Now, what can I do with a Brocade switch? Hope that nothing goes wrong with it.<BR/><BR/>My advise is to do Cisco MDS training and then reconsider why you would use VSANS.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-22921684.post-1164894304580419362006-11-30T13:45:00.000+00:002006-11-30T13:45:00.000+00:00A few thoughts on VSANs --Just because you put a p...A few thoughts on VSANs --<BR/><BR/>Just because you put a particular storage port on a VSAN doesn't mean that it can't talk to initiators on other VSANs. Inter -VSAN Routing allows you to create zones the span VSANs, so you can have an initiator in one VSAN zoned to a target in another VSAN.<BR/><BR/>VSANs are also great for cases where you want to ISL two separate fabrics, but don't want to deal with merging zones. You can route between the VSANs across ISLs without merging the zonesets.<BR/><BR/>Also, if you're extending your fabric across a WAN link (say with FCIP), you can create a separate VSAN on each side of the WAN and route between them with IVR.. instead of having a single fabric spanning the WAN. That way your fabric doesn't segment when the WAN goes down, and you're not broadcasting RSCNs across the WAN when you make fabric changes.Anonymousnoreply@blogger.com