FCIP interface stuck at initializing on 9216i v2.1a (vsan segmented)

Answered Question
Sep 13th, 2005
User Badges:

Following the instructions in both the config guide and troubleshooting guide to configure the FCIP profile and interface, my fcip2 interface status is stuck at initializing. Looking in FM events tab, I can see that the 9216i's are cycling between these states: vsan merged; N_Port unmanageble; vsan segmented and N_Port Up. show fcdom domainlist on the higher priority switch shows it flip-flopping between [local] and principal] [local] states. Using show zoneset active, I can see the zoneset being transfered over to the 2nd switch. Despite all this, the fcip interface does not stay up. Thanks for helping.

Correct Answer by tblancha about 11 years 11 months ago

I would go ahead and open TAC case and attach show tech detail from both switches.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
tblancha Wed, 09/14/2005 - 07:43
User Badges:
  • Cisco Employee,

Just going from your info, it sounds like the interface comes up for a little bit of time. More than likely then, the issue is MTU. You have an MTU configured larger than somewhere in the network can handle it. If you get the show log output and it shows alot of TCP retransmissions, this is the problem.

tom.duong Wed, 09/14/2005 - 08:40
User Badges:

Tx! Show log didn't reveal any TCP retransmissions. I changed mtu from 3000 to 8000 on both 9216i and verified that 6509 ports are also at 9000; couldn't set to 9000 in cli, DM or FM. Don't know why you can't set 9000, but still no cigar.

Correct Answer
tblancha Wed, 09/14/2005 - 09:08
User Badges:
  • Cisco Employee,

I would go ahead and open TAC case and attach show tech detail from both switches.

tom.duong Wed, 09/14/2005 - 13:42
User Badges:

Tx! You were on the right track. The problem was indeed an mtu problem after working with TAC, which reset it to 1500.


This Discussion



Trending Topics: Storage Networking