Tuesday, April 29, 2008

MDS Fc port stuck in initializing

Reasons:
- flogi server not responding correctly
show flogi internal event interface fc x/y

- persistent fcid limit exceeded ( 255 entries with all area unique fcid because
of qlogic hbas)

MDS9513-83-SJ# show run | include "vsan Z" | include fcid | count
where Z is vsan #.
- conflict in persistent fcids ( MDS can't assign the fcid allocated
to WWN)

- # of devices more than 255 if qlogic or devices that need area unique fcid
is allocated

- supervisor failure or module issue, flogi command not reaching the supervisor
or flogi process.

show fc2 internal even errors

these are few causes.

4 comments:

Unixsa06 said...
This comment has been removed by the author.
Jerome Joseph said...

Also a port can get stuck in Initializing in case of OSM/Host
optimized line cards, you need to force set E port and make it dedicated port mode.

Mohit said...

I am running
Hardware
cisco MDS 9124 ("1/2/4 Gbps FC/Supervisor-2")
Software
BIOS: version 1.0.6
kickstart: version 3.2(1a)
system: version 3.2(1a)
I am facing NPIV login problem
current conifg

CISCO215# show fcdomain fcid persistent
Total entries 14.

Persistent FCIDs table contents:
VSAN WWN FCID Mask Used Assignment if(for info)
---- ---------------------- -------- ----------- ---- ---------- ----
2 20:01:00:05:33:09:88:c2 0x550300 SINGLE FCID YES DYNAMIC fc1/2
2 20:00:00:05:33:09:88:c2 0x550500 SINGLE FCID YES DYNAMIC fc1/1
2 20:18:00:05:33:09:88:c2 0x550501 SINGLE FCID YES DYNAMIC fc1/1
2 20:00:00:11:0d:5a:10:00 0x550502 SINGLE FCID YES DYNAMIC fc1/1
2 20:02:00:0d:ec:96:fe:41 0x550600 SINGLE FCID YES DYNAMIC fc1/3


Now if fc1/1 interface is shutdown and device 20:18:00:05:33:09:88:c2 tries to login behind fc1/3 it is getting fcid allocation fail

why is this happening?
I am getting following error
005330988c2) refcnt:1 reqcnt:1
2011 Dec 1 03:42:52.168716 flogi: fs_mts_hdlr_dm_get_fcids: Cannot allocate fcid for pWWN: 20:18:00:05:33:09:88:c2, dst ifindex: 16781312 Err: 1075511296
2011 Dec 1 03:42:52.168785 flogi: fs_add_event_pair_for_flogi: FLOGI HOLD(0x1010be4c) refcnt:2
2011 Dec 1 03:42:52.168854 flogi: fs_inc_num_internal_exceptions(4359):ifindex 0x1001000 resetting tot_internal_exceptions; was 1
2011 Dec 1 03:42:52.168932 flogi: fu_fsm_execute_all: match_msg_id(0), log_already_open(0)
2011 Dec 1 03:42:52.169004 flogi: fu_fsm_execute: ([2]20:18:00:05:33:09:88:c2)
2011 Dec 1 03:42:52.169064 flogi: current state [FLOGI_ST_GET_FCID]
2011 Dec 1 03:42:52.169120 flogi: current event [FLOGI_EV_CANNOT_ALLOCATE_FCID]
2011 Dec 1 03:42:52.169176 flogi: next state [FLOGI_ST_DESTROY_FSM]
2011 Dec 1 03:42:52.169245 flogi: fs_timer_stop: rid(0x40000000), ev(82), t_id(2)
2011 Dec 1 03:42:52.169308 flogi: fs_fc2_send_ack1: ack1 not reqd s_idx[1001000] flags[0] vsan[0x2]
2011 Dec 1 03:42:52.169384 flogi: Sending fc2 flogi reject reason 7 for port 20:18:00:05:33:09:88:c2 vsan 2 ifindex 0x1001000 for exchange 0x32c0402 fcid 0x000000.
2011 Dec 1 03:42:52.169445 flogi: FLOGI reject generated.

Unknown said...

You can have this problem when you try to associate a Device Alias to a VSAN that doesn't exis (Through DPVM database ).

show flogi internal info interface fcX/Y