Brocade Trunking

[Amy Bach_1]

Hi all,

We currently have two fabrics with (1) HP Storage Works 4/256 Brocade switch per fabric. We just received two additional HP 4/256 switches which are located in a separate building. The building distance exceeds the shortwave SFP distance limitation so we have purchased long wave SFPs to ISL between the two buildings. We have confirmed that the distance between the two buildings does not exceed the long wave SFP dinstance limitation. Since we purchased the powerpak license for each switch, we not only get the extended fabric capability, but also the ISL trunking capability. We are looking to create a (4) port ISL trunk between the new and existing switches. I have read the trunking documentation and it seems pretty straight forward. Simply, make ISL connections and then enable ISL trunking, that the process is done automatically using the existing ISLs which meet the trunking requirements (i.e., that the ISLs to be trunked exist in the same quad). Is this correct? Are there any gotchas in connecting the new switches to the existing ones (aside from checking PIDs and Domain IDs?). Anything I should look out for?

Thanks for your advice.

-Amy

[SAKET_5]

Amy,

I would be surprised if ISL trunking isnt enabled by default on 4/256 as well (it certainly is on 4/32) - so my understanding is as you suspect - you just establish the ISL connections (MUST come from the same quad )and you should then have a trunk configured for you automagically - confirm it with "switchshow", "islshow" and "trunkshow" (output from these commands should make it obvious your trunk configuration with "MASTER" ISLs and the slaves).

Domain ID, PID - yep right on the money - I would also just do a "configshow" to ensure any other fabric wide parameters are consistent as well - "buffer credit", etc.

Also, check the firmware versions and if they are not up to date then possibly a good opportunity to bring them all up-to-date.

[The Spartan]

Well, last word -

If you find that ISL is not flowing ie any issue with the fabric,
try fabstatsshow command - it would indicate towards the parameter causing the concern.