For more details, please see ourCookie Policy.

Fibre Channel (SAN)

Occasional Contributor
Posts: 10
Registered: ‎05-05-2015
Accepted Solution

Principal vs Subordinate switch

Our core switch (brocade dcx-4s-b) changed the role to Subordinate from Principlal during the Upgrade. Does it make any differences in the fabric configuration? Is changing the switch role a must? This is production environment, I think changing role is a disruptive process. Please advise me. 

Broadcom Moderator
Posts: 120
Registered: ‎04-27-2009

Re: Principal vs Subordinate switch



technically it makes no real difference. The principal manages the time and the domain ID assignments in the fabric. If it changed (not normal at all in my eyes) to a pizzabox switch I would change it back to the director, higher CPU..etc..


You can force the principal switch non-disruptively with the fabricprincipal -f CLI. See the Help pages. It just forces a Built Fabric.

You can also assign priorities for each switch to prevent things like that.



If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider.
Occasional Contributor
Posts: 10
Registered: ‎05-05-2015

Re: Principal vs Subordinate switch

Thank you Thomas. Just wanted to confirm that  changing fabric role is a non-disruptive activity becuase I had seen the confusing statements in this forums whether fabric build is disruptive or not.

Join the Broadcom Support Community

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