MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

3800 and 2800 (ISL)

 
Shawn_53
Occasional Visitor

3800 and 2800 (ISL)

I am implementing a core-edge topology. I am using a SAN 16 (3800) as a core switch, and a SAN 16 (2800) as an edge switch. Zoning is enabled on the 2800. There are no zones setup on the 3800. I would like to know if there are any "special" configurations that has to be made on either to ISL the 2800 to the 3800. I am in a switched fabric environment. The domain id of the 2800 is 2; the domain id of the 3800 is 100. I was informed that since the 2800 has a lower domain id, that the configuration from the 2800 would be 'pushed' to the 3800. Once I connected the two switches, the connection shows up as an E-Port (incompatible). Any suggestions? Thanks in advance.
8 REPLIES 8
Eugeny Brychkov
Honored Contributor

Re: 3800 and 2800 (ISL)

Shawn,
where did you get word 'incompatible'? E-port is a designator for ISL. So as soon as you connect two switches you'll see that ports you connected together become E-ports.
If 2800 has zoning enables, but 3800 does not then zoning info will be copied from 2800 to 3800 switch. But to avoid problems I would edit configuration on 2800 switch, take config file from there, download it to 3800 and then connect them with ISL
Eugeny
Shawn_53
Occasional Visitor

Re: 3800 and 2800 (ISL)

After connecting the two switches and issuing the switchshow command, it displayed as an E-Port, but where you would normally see WWIDs from connected servers or storage controllers, it displayed "incompatible"

And if your right about an E-Port being a designator for an ISL connection, I have big problems with that. Support told me that it should display as an F-Port.
Eugeny Brychkov
Honored Contributor

Re: 3800 and 2800 (ISL)

Did you check all ISL connected ports are autonegotiate or 1GB fixed speed? You know if you'll set 3800 port to 2G then ISL will not work because 2800 can work only at 1G! Please zip supportshow from both switches and attach to your next reply
Eugeny
Shawn_53
Occasional Visitor

Re: 3800 and 2800 (ISL)

Yes the ports on the 3800 are set to auto. The connections are no longer there because I am under the assumption that it did not work because of the "imcompatible" on the switchshow. With the ISL connection removed, I'm not sure if you will be able to see what I'm referring to. But the supportshow outputs are attached.

Thanks
Eugeny Brychkov
Honored Contributor

Re: 3800 and 2800 (ISL)

3800 shows overheating: 46/42/40C. It's too high. Max operating temperature is 40C.
Error message is "WARNING FABRIC-SEGMENTED, 3, port 4, incompatible flow control parameters" and "ELP rejected".
Value of 'fabric.ops.mode.pidFormat' on two switches should match. You can try setting 2800 value to 1, but I think as soon as 2800 works maybe it's better to change 3800 value to 0 and try merging fabrics again and look if it will succeed
Eugeny
Shawn_53
Occasional Visitor

Re: 3800 and 2800 (ISL)

Thanks, I'll give it a try.
BR686637
Occasional Visitor

Re: 3800 and 2800 (ISL)

Check also the firmwares on the 2800 and 3800 switches (2.6.0c or higher for 2800 and 3.0.2f or higher for 3800).
When connecting our 2800 switches (with initial firmware 2.0.4a) to 3800 switches (with firmware 3.0.2f), we encountered spontaneous reboots and hangs on the 2800 switches.
Reason: heavy ethernet traffic (due to monitoring) could lock the switch.
So we had to upgrade the 2800 firmware to 2.6.0c.

Also instead of using autonegation for the port speed, fix the speed to 1GB on the 3800 ports you want to use for the 2800 ISL. You avoid a lot of possible errors caused by port speed negotation

greetings,

Jan
Yuri Jossa
Occasional Visitor

Re: 3800 and 2800 (ISL)

Eugeny
I work with Shawn.
Setting the PID on the 2800 switches worked.
Thanks for fixing our problem.