Fibre Channel (SAN)

Reply
New Contributor
Posts: 4
Registered: ‎05-17-2013

DCX-4S-B merge via ICL


Hi Experts,

We have the  existing DCX-4S-B in our environment

Site 1

Virtual Fabric info in the DCX

Base Fabric on the Core Blades

Virtual Fabric 1 for user connectivity

Virtual Fabric 2 for connectivity to Site 2

Site 2

Virtual Fabric info in the DCX

Base Fabric on the Core Blades

Virtual Fabric 1 for user connectivity

Virtual Fabric 2 for connectivity to Site 1

We need to expand the Fabric at Site 1 and Site 2 . Hence we are adding 1 DCX at each site.

I understand expanding the DCX via ICL needs the ISL precautions : unique domain id / cfg / switch mode

ARE THERE ANY OTHER PARAMETERS I NEED TO BE AWARE OF ?

DO THE VIRTUAL FABRIC INFO GETS PROPOGATED AUTOMATICALLY WHEN WE DO THE MERGE ? HOW DOES IT WORK ? WHAT EXTRA I HAVE TO DO ?

WOULD BE REALLY HELPFUL IF SOMEBODY CAN GUIDE ME FOR ANY DOCUMENT (BROCADE) FOR THIS ACTIVITY

Thanks in advance.

Frequent Contributor
Posts: 90
Registered: ‎12-26-2010

Re: DCX-4S-B merge via ICL

New Contributor
Posts: 4
Registered: ‎05-17-2013

Re: DCX-4S-B merge via ICL

Hi SKT

Many thanks for your reply.

But this document cites creating a basic ISL between switches.

What we are doing here is ICL between two DCX  switches and it has virtual fabrics. XISL is not supported on ICL. However does this mean we cannot merge the virtual fabrics on the DCX.

Do you have any document which cites extending the DCX via ICL and how the merge of the virtual fabric configuration takes place ?

Valued Contributor
Posts: 549
Registered: ‎03-20-2011

Re: DCX-4S-B merge via ICL

you still have to chop your new physical switches into LSes.

in a way, this also depends on where you will place ICL ports - into the base switch or into the logical switches. please read the admin guide - it denotes all the limitations.

External Moderator
Posts: 4,973
Registered: ‎02-23-2004

Re: DCX-4S-B merge via ICL

sant,

I've at several time configured ICL with DCX, this is very simple, however:

from your principal question, please correct me if I'm wrong or miss understood you question, BOTH DCX are at the moment productive and both have active config.

now you want to ICL = Inter Chassis Link both DCX

Is correct ?

TechHelp24
New Contributor
Posts: 4
Registered: ‎05-17-2013

Re: DCX-4S-B merge via ICL

Hi Techhelp,

Thanks for responding.

No , I have the following config currently.

Site 1

It has 2 DCX which are in separate fabrics : lets name them DCX1 and DCX2

Each DCX has three logical switches : base switch , repl, user config switch

Site 2

It has 2 DCX which are in separate fabrics lets name them DCX 3 and DCX 4

Each DCX has three logical switches : base switch , repl, user config switch

DCX1 repl logical switch and DCX3 repl logical switch are part of the same fabric

DCX2 repl logical switch and DCX4 repl logical switch are part of the same fabric

Now we are adding 2 DCX to each Site.

So at site 1 >

DCX1 extended with a new DCX

DCX2 extended with a new DCX

Similarly at site 2

DCX3 extended with a new DCX

DCX4 extended with a new DCX

Now as per my understanding : what I should be doing is

Check all ISL parameters are in place : domain id / cfg /

Enable VF on the new switch : reboot

Create the same logical switches on the new dcx

Apply the ICL license on all the dcx`s

Make sure ICL ports are in base switch.

Turn on XISL

Enable the ICL  ports.

NOT SURE WHETHER THIS ACTIVITY WILL CAUSE ANY DISRUPTION TO THE EXISTING PRODUCTION DCX.

Hope I am clear

Contributor
Posts: 57
Registered: ‎08-12-2009

Re: DCX-4S-B merge via ICL

Sant

Your steps are correct. When you configure the same VF configuration on the new DCX and interconnect with ICL each logical switch will form to connect a Virtual Fabric between the chassis via the ICL interconnections. Zoning for each logical switch will also be copied to each logical switch on the new chassis.

New Contributor
Posts: 4
Registered: ‎05-17-2013

Re: DCX-4S-B merge via ICL

Hi jdaignea,

Many thanks for your reply. Apologize for late reply. It has been a pretty hectic schedule for last 2 weeks.

Enabling the XISL on the existing production DCX : will it cause any disruption or outage.

Regards,

SK

External Moderator
Posts: 4,973
Registered: ‎02-23-2004

Re: DCX-4S-B merge via ICL

if you refer to enable ( fosconfig command ) Virtual Fabric = XISL, see output below as example

TH24_B_51_EDGE_FAB4:admin> fosconfig --enable vf

WARNING:  This is a disruptive operation that requires a reboot to take effect.

All EX ports will be disabled upon reboot.

Would you like to continue :

TechHelp24

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.