Intergrating a DCX-4S into a McData Fabric

I have just setup a DCX-4S and want to add it to one of our existing fabrics. The DCX is configured with an IP and I am able to access it via the web tools and the CLI. I have also changed the interopmode to (2) McData Fabric to match the existing fabric and verified that safe and default zoning are disabled. The existing fabric consists of two McData 6064, three McData 4500 and one McData 4700 all running firmware version 09.09.07. the DCX is at firmware version 6.0.0e.

One of the 6064 has the switch priority set to principal and the rest are set to default, the DCX is also set to principal. How do I change the DCX to subordanate? I am unable to find the command and it doesn't look like it can be done through the GUI. I would actually like to make the DCX principal but I'm not sure how to do it without wiping out the configuration of the existing switches. I read the solution guide for integrating a DCX at the core of a McData fabric but it requires a EFCM license which I don't have, I'm running the basic edition of connectrix manager. Does anyone have a different method?

Re: Intergrating a DCX-4S into a McData Fabric

Which is ur Core SW in the Fabric?If it is DCX-4S, you can make it to to principal. in the Fabricshow the principal SW will be seen with a > mark.In switchshow ISLs from subordinate SWs will be upstream towards Principal SW and from Principal SW ISL will be downstream.

It is not essential to make the DCX-4S principal. As in the fabric , when it will be merged, the lowest WWN sw will automatically be the principal.

look at the fabricprincipal cmnd:

user> help fabricprincipal

User Commands fabricPrincipal(1)

NAME fabricPrincipal - Sets the principal switch selection mode.

SYNOPSIS fabricprincipal

DESCRIPTION Use this command to set principal switch selection mode for the switch.

The implementation of the fabricPrincipal command is based solely on mechanisms specified in the Fibre Channel standards. The mechanisms specified provide a preference for a switch requesting to be the principal switch in a fabric, but they do not provide an absolute guarentee that a switch requesting to be the principal switch will actually achieve this status.

When dealing with larger fabrics, the selection of the principal switch is less deterministic. In these cases, to help ensure that the desired switch is selected as the principal switch, a small selection of switches should be connected together first, followed by the addition of the rest of the fabric.

OPERANDS This command has the following operands:

-f Specify the -f option to force a fabric rebuild. This option is required when enabling principal switch mode. This option is not valid with the disabling principal switch mode.

-h Specify the -h option to display the command usage summary.

-q Specify the -q option to display the current mode state.

mode Specify 1 enable, or 0 to disable principal switch mode (the mode activates when the fabric rebuilds). This operand is optional.

Re: Intergrating a DCX-4S into a McData Fabric

--->>> The existing fabric consists of two McData 6064, three McData 4500 and one McData 4700 all running firmware version 09.09.07. the DCX is at firmware version 6.0.0e.

Are you sure the DCX is running with FOS 6.0.0e ?

EOS 9.9.7 is incompatible with FOS 6.0.x, and 6.1.x,

--->>> One of the 6064 has the switch priority set to principal and the rest are set to default, ....

Note, when you set the Brocade as Principal, you need to set the McDATA as "neverprincipal"

--->>> I read the solution guide for integrating a DCX at the core of a McData fabric but it requires a EFCM license which I don't have, I'm running the basic edition of connectrix manager. Does anyone have a different method?

With DCFM Professional, is for Free. Ask you Reseller / Supplyer or OEM to obtain the Software.

Join the Community

Please note: Certain product lines referenced on this website have been acquired by third party buyers and may no longer be supported, offered or sold by Brocade, A Broadcom Limited Company. These product lines include, but are not limited to, the Virtual Router (vRouter), Virtual Application Delivery Controller (vADC), the Virtual Evolved Packet Core (vEPC) and the Software Defined Networking (SDN) Controller. Any mention of these product lines, including associated services and support on this site, as it relates to Brocade should now be considered historical reference only. Ongoing use of such products may be subject to terms and conditions of the buyer.

Some, but not all the content on this site is provided, reviewed, approved or endorsed by Brocade but in any case, is provided solely as a convenience of our customers. All postings and use of the content on this site are subject to the BROCADE WEBSITE USE TERMS AND CONDITIONS. BROCADE ASSUMES NO LIABILITY WHATSOEVER, MAKES NO REPRESENTATION AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO THE CONTENT PROVIDED HEREIN, INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, CORRECTNESS, APPROPRIATENESS OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED. THIRD PARTIES USE THIS CONTENT AT THEIR OWN RISK. Content on this site may contain or be subject to specific guidelines or limitation on use. Third parties using this content agree to abide by any limitation or guidelines and to comply with the BROCADE WEBSITE USE TERMS AND CONDITIONS. Brocade may make changes to this content, to specifications, or product design or descriptions at any time, or may remove content at its sole discretion without notice.