Question about Interop between MDS9509 and Brocade 3800

[huangdc]

I meet a very strange problem when I tried to connect MDS9509 to Brocade 3800.

The firmware of 9509 is 2.1(2d) and the firmware of 3800 is v3.2.1.

The topology is as below.

server1--3800A---3800B-----9509-----disk

|

|

server2

Server1 is attached to 3800A, server2 to 3800B, disk to 9509

The PID of each 3800 is 1. In MDS9509, I use VSAN 7 to connect to 3800B. I set VSAN 7 to interop mode 3. And I change the flow control mode of attching port of 3800B to R-ready.

The strange problem is when I use show fcns data vsan 7 on 9509, I can see server1,server2 and disk. But when I use nsallshow on 3800A, I can only see server1. And on 3800B, I can only see server2.

I disable the port of 9509 which connecting 3800B and reboot 3800A and 3800B. This time on 3800A, I can see both server1 and server2. On 3800B, the result is the same.

The I enable the port of 9509 which connecting 3800B and reboot 3800A and 3800B. The problem occur again. I can only see the local device when I run nsallshow on 3800A and 3800B.

Does anyone have experience on this?

Just now I did another test the topology is as below,

server1--3800A---9509-----disk

In interop mode 3, same problem occur. Then I change 3800A to interop and 9509 to interop mode 1. Then no problem now, both switch can see both server and storage.

Can anyone give some advice?

[tblancha]

Have not had exactly that symptom but something close if you are using IVR. IE, that the ISl to the 3800b is in one vsan and the disk is in another? If so, then add this command to the 9509 and shut/no shut the E port.

ivr virtual-fcdomain-add vsan ,

If there is not IVR, then get the 9509 to SANOS 2.1.2b and greater and then run fcanalzer and write the output to volatile when doing a shut/no shut to see the nameserver interaction. Then you can tftp it

a PC and view it will ethereal.

[huangdc]

Actually,I put the disk attaching to 9509 to VSAN 7 which is the same VSAN as 3800 in. The code of 9509 is 2.1(2d) which is the latest code published on Cisco Web site.

I will try fcanalyzer local to test.

[huangdc]

Just now I did a test.

I debug fcns all vsan 7

Then I shutdown the interface connect to 3800B and then I no shut that interface. The debug info is in the attachment.

From we debug we can see 9509(domain ID 93) recieved some entry from 3800A(domain ID 111),3800B(domain ID 112),

VSAN 7:

--------------------------------------------------------------------------

FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE

--------------------------------------------------------------------------

0x5d0002 N 50:05:07:63:03:0b:c3:5a (IBM) scsi-fcp:target fc..

0x6f0000 N 50:05:07:68:01:40:01:b3 (IBM) scsi-fcp:target

0x700000 N 50:05:07:68:01:20:03:ac (IBM) scsi-fcp:target

But from 3800A and 3800B, we still can only see the devices attached local.

[tblancha]

Sorry, nothing is attached. Also might want to open a TAC case on this to read debugs. Also note that 3.2.1 is not on the Cisco matrix for interop 3.

In interop1, the domain of 93 would be invalid as the valid domain ids are 97-127.

[huangdc]

Thanks for your answer.

You are right. When I test interop mode 1, I changed the domain ID to 97.

Can you help to provide the supporting matrix of each interop mode? Thanks a lot!

I always meet error when I tried to attach the debug output. But when I analyzed the output file, I found that in interop 3, 9509 did not recieved NS query from 3800. And in interop 1, 9509 recieved NS query and give reply. I think this is the root cause. But I don't know why 3800 did not send out NS query in interop mode 3.

[tblancha]

It's quite possible that there is something in the 3.2.1 dealing with the NS query and that's why it's not a certified interop release. That matrix can be found at http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/interop/matrix.pdf