HPE EVA Storage
1829128 Members
2263 Online
109986 Solutions
New Discussion

Adding Brocade switch to pre-existing fabric

 
Adam Garsha
Valued Contributor

Adding Brocade switch to pre-existing fabric

What I have done to a new Brocade FC switch:
-> changed password
-> changed domain ID to be unique
-> checked firmware level and verified "good"
-> set network params (p.s. extra points for how to disable ethernet autonegotiate and lock to 100/full)
-> set time and timezone
-> verified ethernet connectivity
-> changed all ports to 2G (vs. auto)
-> plugged in my SFP's

Now...

To add this switch to a pre-existing live-production fabric, do I need to disable it or anything before plugging in the FC cables that will act as ISL's to a pre-existing set of switches?

Namely, when I look at the switch admin gui, it says the lone-wolf switch thinks it is "principle" currently, is there anything that I need to do to put it in a 'accept your zoning info, etc from other switches when I plug you into the fabric mode' before I plug it in?

Thanks!
4 REPLIES 4
Adam Garsha
Valued Contributor

Re: Adding Brocade switch to pre-existing fabric

This should be an easy question. I've searched, but I am interested in specifics.

Is there anything I need to do besides the steps I've listed above before I plug my new switches into a production fabric.

I've got good firmware levels. Good Domain ID. Network is set the way I want it.

My only hessitation is that the new switch is set as "principle"... I want to ensure that it slurps the zone info, etc from the pre-existing fabric vs. nock-out-the-zones in my pre-existing fabric...

Is there a mode/config param that I should set prior to pluging in the ISL's?

If not then, not.

This is a generic case of adding a new brocade switch (just de-boxed) to an all brocade fabric (with all fairly-new FOS's).

Thanks!
Adam Garsha
Valued Contributor

Re: Adding Brocade switch to pre-existing fabric

No soup or points for you!

Just kidding. Called support.

They recommended checking PID and configshow settings to make sure they are consistent before ISL'ing.

The lowest Domain ID wins... so since my new switches have higher Domain ID's... I don't need to worry about them being "principle" right now... they will become subordinate and slurp the zoning info as I want by default.

They said mcdata/cisco may have some settings that you can force the switches to be subordinate prior to adding to the fabric.
Steven Clementi
Honored Contributor

Re: Adding Brocade switch to pre-existing fabric

Adam:

At the very minimum, you only need to change the Domain ID, assuming you have all like switches. If you have a mix of older switches in the fabric, then you also need to make sure the firmwares all can coexist with each other.

When you make th ISL connection, the "principle" status shold change to "subordinate". It is mostly all automatic. Connect the switch, it joins the fabric and the zone config uploads to it.

One thing you can do is... shut the switch down, mke the ISL connection, then power it up. Instead of booting up regular, it should boot up and join the fabric, bypassing the "principle" election.

Also, if the switch is right out of the box, then it should not have azone config on it. If it does, it would be easiest to just clear the config.


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
Steven Clementi
Honored Contributor

Re: Adding Brocade switch to pre-existing fabric

Thats what i get for watching TV in-between clicking reply and submit.


;o)
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)