Add new san switch to Fabric Brocade

[IT_CNB]

Hi,

my san server farm is composed of n.02 Fabric 6510 (A-B) Principal Role and n. 08 switch 300 as subordinate role.

n.04 brocade 300 on 6510_A and n.04 brocade 300 on 6510_B whit ISL port (n. 02 ports per switch).

I need to add another n. 02 brocade 300 switches as subordinate on Fabric, n.01 switch on 6510_A and n.02 switch on 6510_B whit ISL.

How can I proceed?

Proceed with the basic configuration, switchname, ipaddrset, dnsconfig, tsclockserver, same domain_id, connect to 6510.

For the configuration as subordinate?

Is the procedure correct?

Thanks for the support.

[Antonio Bongiorno T…]

@IT_CNB

--->>>Proceed with the basic configuration, switchname, ipaddrset, dnsconfig, tsclockserver, same domain_id, connect to 6510.

be aware, each switch in the "same" Fabric must have a unique DID, and not the same.

->For the configuration as subordinate?

from command line issue the command

"fabricprincipal 0"

for more details refer the Command Reference Guide.

...I'm not a friend of "fabricprincipal" command

[IT_CNB]

Hi Antonio,

thanks for the support.

By the same "domain id" i meant to assign a new "domain_id" to the new switches 300 different from others switch and fabric, also for ISL configuration to 6510.

Once configured as subordinate, does the configuration take it automatically from 6510? Alias, Zoning, etc...

Let me know
Thanks

[Antonio Bongiorno T…]

"same and new" is not the same.

->Once configured as subordinate, does the configuration take it automatically from 6510? Alias, Zoning, etc...

yes, as soon the switch ISL - join the fabric the config is replicated in the new switch itself, an dyou should see the switch in the Fabric when isssue "fabricshow" command.

[IT_CNB]

Hi Antonio,

ok.

No specific commands are required for ISL configuration on 6510.
With the same "domain_id" on new 300 the switch 6510 configures isl automatically, is it correct?

Thanks

[Thomas.Letsche · Accepted solution]

Hi,

the Principal switch is able to change a DID when a duplicate is detected however this is influenced by some factors if it is changed or the ISL is segmented. Insistent DID, etc..

Best Practice is to manually assign different DID in the fabric.

[IT_CNB]

Thanks for the support