06-16-2010 05:33 AM
It seems equal to me , here is the outputs.
Do you see something wrong here?
fabric.ops.mode.isolate:0, command not found
fabric.ops.mode.noClassF:0ack.passes:1000: command not found
fabric.ops.mode.tachyonCompat:0ses:180: command not found
fabric.ops.mode.useCsCtl:0passes:120: command not found
fabric.ops.vc.class.3:3AUTO: command not found
fabric.ops.vc.linkCtrl:0es:5000d not found
06-16-2010 10:00 AM
It is correct, but you have written that you made some zoning in the new sw. while you are merging these, do a cfg clear also in the new sw. have you done this.does it show why it is segmented, i mean any clue like DID is same, some parameters are same liek this. what it shows in the errdump?
06-16-2010 10:08 AM
Yes, I cleared the configuration from the new switch before the connection
I don't have a clue why, Domain ID is different, what else can't collide?
I don't have errordump for now (maybe later)
Any idea for now ??
06-16-2010 10:31 AM
What is the interopmode set to on the existing Brocade(s)? Since you seem to be attaching to QLogic switches, I am wondering if the interopmode had been set to something other than 0 (native) at some time in the past.
I can see from the switchshow of the new Brocade that it is set to mode 0 still. Those modes will need to match for the merge to take place. You can check the mode by viewing switchshow, interopmode, or configshow commands.
06-16-2010 11:57 AM
I've checked it and the interopmode on the two current brocades is set to 1.
It might be our issue, isn't it ?
Tomorrow I will try to change it and see what's going on
As far as I understood this is the right action plan:
ON NEW BROCADE
1. set the interopmode to 1
2. clear config
4. connect between the brocades
am I rigth?
06-16-2010 04:35 PM
So the mismatched interopmode settings is most definitely the problem here. But I'm afraid the solution isn't going to be as simple as setting the new switch to "1."
Starting with FOS 6.0, the interopmode setting of 1 was obsoleted and replaced by modes 2 & 3. So the only choices you have for interop on the 300 are 0, 2 or 3. The only option I see here would be to upgrade the older Brocades to 6.x and then try setting them to mode 3 along with the new Brocade. I can only guess that that might work and allow you to continue to remain connected to the QLogic switches.
As I think someone else already mentioned, Brocade does not really support connectivity to QLogic switches. The interopmodes that are supported only include support for connecting to other Brocades and to legacy McData switches.
06-17-2010 03:38 AM
I've try to set the new brocade to interopmode 3, and connect it to brocade 1.
The status was:
On old brocade: E-Port segmented,(Eport Isolated)
On new brocade: E-Port segmented,(Op Mode incompat)
Will it help if i will set it to interopmode 2? I have some possibiliteis there - default zoning and secure zoning
I attached a visio of my configuration
06-18-2010 08:28 AM
Post "switchshow" output from all brocade in this Fabric, and upload the Visio Draft now, without space, like "Fabric_Topology_vsd.zip"
the community not allow file upload with space, and cannot be Downloaded.
06-18-2010 10:43 AM
No, I do not believe it will help to set it to mode 2 either. As I said, the modes are going to have to match for the merge to take place.