I have two MDS9220I switches and recently added a third MDS9220I at another site. While trying to configure a pair of new FCIP links to the new MDS9220I I am running into a strange situation.
When I create an initially bring the fcip interfaces up with just VSAN 1 trunking, the links come up fine, device-aliases distribute okay. As soon as I add the replication VSAN (we'll call it 100) to the trunk list, the links on the new MDS switch side begin killing the link complaining:
%PORT-5-IF_TRUNK_UP: %$VSAN 1%$ Interface fcip1, vsan 1 is up
%PORT-5-IF_TRUNK_UP: %$VSAN 199%$ Interface fcip1, vsan 100 is up
%PORT-5-IF_TRUNK_DOWN: %$VSAN 1%$ Interface fcip1, vsan 1 is down (TCP max retransmission reached)
%PORT-5-IF_TRUNK_DOWN: %$VSAN 100%$ Interface fcip1, vsan 100 is down (TCP max retransmission reached)
%PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: %$VSAN 1%$ Interface fcip1 is down(TCP conn. closed - retransmit failure)
%PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: %$VSAN 1%$ Interface fcip1 is down(TCP conn. closed - retransmit failure)
Remote side is similar except with the message (TCP conn. closed by peer).
The only thing different than my other FCIP links is that I unfortunately need to route traffic for the switch1 IPStorage1/1 and switch2 IPStorage1/1 interfaces. To do so, I've setup static routes for the interfaces:
EG:
switch1 default gateway 10.0.0.1(/24), ipstorage1/1 on 192.168.100.10/24
ip route 192.168.200.0 255.255.255.255 192.168.100.1 interface IPStorage1/1
switch2 default gateway 10.1.0.1(/24), ipstorage1/1 on 192.168.200.10/24
ip route 192.168.100.0 255.255.255.255 192.168.200.1 interface IPStorage1/1
I'm trying to look for any other basic troubleshooting suggestions before I go to support. To the best of my knowledge the networks are up and fully funtional (Networking team assures me the networks are up and not firewalled, without issue) so I'm assuming I've got some part of the fcip config that I'm missing.
