03-14-2012 11:58 AM
That's my understanding as well, especially after gauravgupta posted a plan for how they were planning to connect the switches
The plan looks good to me (as do the output of the commands) as for connecting the switches.
Maybe you want to take care of the rest of the non-fc related settings too before joining it to the fabric? Like SNMP, ipfilter, aptpolicy, etc?
gauravgupta: after you connect the switches and against some odds they aren't in the same fabric, you can see in switchshow/errshow the first reason why the merge didn't happen.
03-14-2012 12:05 PM
Looks fine, but some notes:
As I saw- there are no D_ID conflicts.
Both switches are in native mode.
Default zone setting is the same.
So far looks good.
After you merge the fabric, you can see if everything is well by fabricshow command (before issue the fabricprincipal command).
You can verify the status of the ISL by islshow command.
If this situation is good- continue with the fabricprincipal command.
Everything is OK.
Have a good luck!
03-14-2012 01:00 PM
one more question,
Is it required to run fabric principal command immediately or we can do that later when we plan to move fiber cables from old to new switch?
Can we run at the time we plan to do decommission the old switch?
Also when we plan to connect ISL ports , is it required to shutdown the new switch and bring it up once the ISL fiber ports are connected?
Thanks in advance