SanSwitch 16 PLOGI's

[BR824100]

Hi,

I am currently experiencing a problem with SANSwitch16 (Brocade 2800). I attempted to tidy up our server room at the weekend and move this switch from one cab to another. Previously it was working fine, but now I am recieving errors as shown below. Port 3 is one of the connections to an HSG80 controller and port 15 is a connection to the SMA.

Could I have damaged the cables in the move or could this be a config setting that wasn't saved and was lost when the switch was shut down?

Both systems seem to be up and I have no errors in the event logs.


SANSwitch1:admin> Mar 7 13:13:44.883 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc
cos=0xc df_size=2048
Mar 7 13:13:59.749 port 3: PLOGI s_id=0x11300 d_id=0xfffffc cos=0x8 df_size=20
48
Mar 7 13:14:09.866 port 3: PLOGI s_id=0x11300 d_id=0xfffffc cos=0x8 df_size=20
48
Mar 7 13:14:19.949 port 3: PLOGI s_id=0x11300 d_id=0xfffffc cos=0x8 df_size=20
48
Mar 7 13:14:30.049 port 3: PLOGI s_id=0x11300 d_id=0xfffffc cos=0x8 df_size=20
48
Mar 7 13:14:40.149 port 3: PLOGI s_id=0x11300 d_id=0xfffffc cos=0x8 df_size=20
48
Mar 7 13:17:44.916 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc cos=0xc df_size=2
048

SANSwitch1:admin> Mar 7 13:19:44.966 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc
cos=0xc df_size=2048
Mar 7 13:21:45.249 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc cos=0xc df_size=2
048
Mar 7 13:27:45.283 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc cos=0xc df_size=2
048
Mar 7 13:29:45.333 port 15: PLOGI s_id=0x11f00 d_id=0xfffffc cos=0xc df_size=2
048

[CA1004210]

That message in general does not indicate any errors - all it says is that a device on port 3 & port 15 have succesfully completed Fabric Login (FLOGI) and subsequently now doing a Port Login (PLOGI) to poll for devices that they have access to. Is it likely that your SMA is polling the HSG80 - are you running HSG Element Manager?

Have you not seen this message before?

[BR824100]

The SMA is running Element Manager and I have seen it report multiple PLOGI entries but not continuously like it is now and have not had this on the HSG conrollers continuously before. The only thing I can think of is that these connections are now running over OM3 cabling. Could this cause and issue? I have other servers with the same cards in however (and the other HSG ports) and these are not shown the same issues.