For more details, please see ourCookie Policy.

Fibre Channel (SAN)

New Contributor
Posts: 2
Registered: ‎05-31-2012

Moving Trunks between switches and back again

We're having some building work done and have managed to pinch a 48K from a sister site to accomodate moving our own.

I don't work with Brocades that often apart from an odd bit of zoning now and again and need some help. Would appreciate a list of commands, pointers etc. needed to do this. The fabric currently has three 48Ks and a two 5100s that I'm not drawing. Two 48ks are ours (SW01 and SW02) and one isn't (SW03). SW03 is only temporary for a month or so and we've setup a short wave based trunk between SW02 and SW03 to accomodate moving all of the servers (OpenVMS, Tru64, HP-UX & RHEL) from SW02 to SW03 and all we need to move next are is the long wave trunk.

Current setup:


First question: we have some spare long wave sfps that can go into SW03 - so what do we need to do to move the trunk from SW01-SW02 to SW01-SW03 so that it looks like:


Then for about a month it'll sit like:


When SW02 is then back in place and powered up we need to move back the short wave ISLs, all servers and again move the long wave based trunk back from SW01-SW03 to SW01-SW02 so that we end up with:


Any pointers, commands etc. much apprecaited as I'm going to be digging into the manuals this weekend!



Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: Moving Trunks between switches and back again

You can run the portcfgperssitentdisable command to disable the ISLs. This ensures that the links are disabled on your switch sw02 after a reboot! Otherwise you will have an uncontrolled fabric build.

To create a trunk all ports of the trunk have to run on the same speed (portcfgspeed) All ports must stay on the same port group on both switches.

Trunking license have to be installed on both switches before a trunk can be enabled.

If you use long wave SFPs (LWL) you have have to make sure that you use single /mono mode cables (yellow cables). Before connecting these cables into the SFPs please clean the cables with the correct tools.

Afteer you have cabled the new trunk clear with the command stats clear all error counter on the switches sw01 and sw03. After some time run the command porterrshow to check if you have errors on the new links. If so check which errors you have and do some corrective work and run the commands a second time. portperfshow is also a good command to check how much traffic is going over the lines.

errdump will show you if you have general errors on the SAN switch.

When you plan to enable you switch sw02 make sure that you have removed the zoning db from that switch. Otherwise the switch can not join the fabric if you have done zoning changes on switch sw01 and sw03.



New Contributor
Posts: 2
Registered: ‎05-31-2012

Re: Moving Trunks between switches and back again

Thanks so if I'm right in following this the procedure should be (bearing in mind ports 127 and 255 in all three directors have the long wave SFPs and the trunk between SW01 and SW02 currently sits on these ports):

  • Permanently disable 127 and 255 on SW02
  • Disable 127 and 255 on SW01
  • clear stats and err on 127 and 255 on SW01 and SW03
  • set port speed on SW03-127 and SW03-255
  • configure trunk ports on SW03-127 and SW03-255
  • plug in single mode from SW01-127 to SW03-127
  • plug in single mode from SW01-255 to SW03-255
  • enable ports SW03-127 and SW03-255
  • sysShutDown on SW02
  • clearconfig on SW02


As all three of these directors are currently in the same fabric (no virtual fabrics in place) can we just remove the ISL trunk from between SW01-SW02 and effectively plug the cables from SW01 into SW03 on the same ports and it should recognise without further configuration needed?



Join the Broadcom Community

Get quick and easy access to valuable resources across the Broadcom Community Network.