Ports Stuck in intializing

Unanswered Question
Feb 27th, 2007

On Friday we rebooted a server and it did not get it's drives back. The port shows up as red in DM. The only way to get the prot active was to reboot the SAN switch, then it worked fine. Today a different sever was rebooted and the same symptom happened. There are no errors or core dumps and no errors on the port. Any ideas on what the problem is or how ti find what is causing the failure. Other than that failed port all other servers are working fine. The switch is a 9120 running ver.m9100-s1ek9-mz.2.0.1b.bin. The only error I see is

2007 Feb 27 19:54:17 ACFCSW1 %KERN-2-SYSTEM_MSG: Virtual device eth2 as ks to queue packet! Any helpd would be great.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
colin.mcnamara Tue, 02/27/2007 - 19:39

My guess is there is an sfp problem. Or communication between the backplane and the SFP.

The virtual device asking to queue packet is a linux kernel message. It has to do with the kernel thinking an interface is up, while it is physically in a down state.

My recommendation is to try swapping the sfp out. This should cause the backplane to notice a new SFP and re-initialize itself.

To confirm this you should get more information about the port. You can follow the steps below to accomplish this.

If you mouse over the port in device manager it should tell you why the port is down.

you can also execute

sho port internal event-history interface fc 1/1

substitute 1/1 for your port number. And post the results here .

That will help a bit in troubleshooting the problem.

If this is helpful please remember to give this a score.

tcherry Wed, 02/28/2007 - 06:48

Here are the messages from the sh port internal command:

>>>>FSM: has 115 logged transitions<<<<<

1) FSM: Transition at 699767 usecs after Mon Feb 26 15:41:26 2007

Previous state: [PI_FSM_ST_IF_NOT_INIT]

Triggered event: [PI_FSM_EV_MODULE_INIT_DONE]

Next state: [PI_FSM_ST_IF_INIT_EVAL]

2) FSM: Transition at 699824 usecs after Mon Feb 26 15:41:26 2007

Previous state: [PI_FSM_ST_IF_INIT_EVAL]

Triggered event: [PI_FSM_EV_IE_ERR_DISABLED_CAP_MISMATCH]

Next state: [PI_FSM_ST_IF_DOWN_STATE]

3) FSM: Transition at 8675 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_IF_DOWN_STATE]

Triggered event: [PI_FSM_EV_FCOT_INSERTED]

Next state: [PI_FSM_ST_IF_INIT_EVAL]

4) FSM: Transition at 8859 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_IF_INIT_EVAL]

Triggered event: [PI_FSM_EV_IE_PORT_INIT]

Next state: [PI_FSM_ST_PORT_INIT]

5) FSM: Transition at 8911 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_PORT_INIT_CHECK_OUTSTANDING_RESPONSES]

Next state: [PI_FSM_ST_PORT_INIT]

6) FSM: Transition at 11835 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_PORT_PRE_INIT_CONFIG_DONE]

Next state: [PI_FSM_ST_PORT_INIT]

7) FSM: Transition at 11945 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_PORT_INIT_CHECK_OUTSTANDING_RESPONSES]

Next state: [PI_FSM_ST_PORT_INIT]

8) FSM: Transition at 19658 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_ACL_MODE_PROG_DONE]

Next state: [PI_FSM_ST_PORT_INIT]

9) FSM: Transition at 19718 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_PORT_INIT_ALL_RESP_RCVD]

Next state: [PI_FSM_ST_PORT_INIT]

10) FSM: Transition at 19805 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_PORT_INIT]

Triggered event: [PI_FSM_EV_UNLOCK_RESOURCE]

Next state: [PI_FSM_ST_LINK_INIT]

11) FSM: Transition at 20471 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_LINK_INIT]

Triggered event: [PI_FSM_EV_PACER_BRINGUP_ALLOWED]

Next state: [FSM_ST_NO_CHANGE]

12) FSM: Transition at 21508 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_LINK_INIT]

Triggered event: [PI_FSM_EV_LCP_SET_PORT_CFG_RESP_RCVD]

Next state: [FSM_ST_NO_CHANGE]

13) FSM: Transition at 357022 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_LINK_INIT]

Triggered event: [PI_FSM_EV_LCP_LINK_STATUS_RCVD]

Next state: [FSM_ST_NO_CHANGE]

14) FSM: Transition at 357035 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_LINK_INIT]

Triggered event: [PI_FSM_EV_LCP_INIT_STATUS_SUCCESS]

Next state: [FSM_ST_NO_CHANGE]

15) FSM: Transition at 357116 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_LINK_INIT]

Triggered event: [PI_FSM_EV_LCP_INIT_STATUS_7]

Next state: [PI_FSM_ST_F_PORT_INIT_1]

16) FSM: Transition at 537059 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_F_PORT_INIT_1]

Triggered event: [PI_FSM_EV_FLOGI_RCVD_AND_ALLOWED]

Next state: [PI_FSM_ST_F_PORT_INIT]

17) FSM: Transition at 553787 usecs after Mon Feb 26 15:41:28 2007

Previous state: [PI_FSM_ST_F_PORT_INIT]

Triggered event: [PI_FSM_EV_FLOGI_ACC_SENT]

Next state: [PI_FSM_ST_F_PORT_UP]

18) FSM: Transition at 754476 usecs after Mon Feb 26 22:24:07 2007

Previous state: [PI_FSM_ST_F_PORT_UP]

Triggered event: [PI_FSM_EV_LCP_LINK_STATUS_RCVD]

tblancha Wed, 02/28/2007 - 10:39

It is more than likely a RMA situation. Call OSM or Cisco TAC and get RMA.

tcherry Thu, 03/01/2007 - 08:05

We RMA'd the switch last night and all is well. Thanks for all your help. This forum was more helpful than EMC support was in resolution to our problem.

Actions

This Discussion

 

 

Trending Topics: Storage Networking