StoreEver Tape Storage
1748169 Members
3870 Online
108758 Solutions
New Discussion юеВ

Re: FC connection drop to MSL 6030

 
IBaltay
Honored Contributor

Re: FC connection drop to MSL 6030

Hi, the most important is to repeat/compare the error counter values on the impacted ports
the pain is one part of the reality
Havard_3
Occasional Advisor

Re: FC connection drop to MSL 6030

Ok, here's the process done following your input.

Ran a short backup just to produce the error and start with a clean sheet.
Rebooted backup server only, e1200 & library didn't show up and link to first brocade down.
Rebooted library and server, e1200 & library shows up and link to first brocade down

Then started portErrShow, noted values.
Initated ntbackup job, ran for 56 minutes and 42 seconds then failed.
During backup job portErrShow was re-run about every 5 to 10 minutes, but values didn't change.
Once the error appeared I again ran portErrShow, and the only value that had changed was under disc c3, which went up from 298 to 340 for fc connection to the controller card as seen below.

0 = e1200
19 = controller card in server


frames enc crc too too bad enc disc link loss loss frjt fbsy
tx rx in err shrt long eof out c3 fail sync sig
=====================================================================
0: 3.7g 2.6g 0 0 0 0 0 454k 0 22k 3.8k 7.6k 0 0
19: 2.8g 4.0g 0 0 0 0 0 172k 298 182 867 459 0 0


frames enc crc too too bad enc disc link loss loss frjt fbsy
tx rx in err shrt long eof out c3 fail sync sig
=====================================================================
0: 3.7g 2.6g 0 0 0 0 0 454k 0 22k 3.8k 7.6k 0 0
19: 2.8g 4.0g 0 0 0 0 0 172k 340 182 867 459 0 0


I then checked HBanywhere on the backup server;
Link to second brocade up and HSV 200's visible, but drives & e1200 not listed.
Link to first brocade down, still.

Verified this in turn by going into the web mgmt interface for the second brocade, and here the port connection to the controller card was still alive (19) - but the link to the e1200 was down (0).
As mentioned above, the only place where a value changed was the port connecting the controller card on the backup server - not the one to the e1200. Yet that is the one that drops.
IBaltay
Honored Contributor

Re: FC connection drop to MSL 6030

Hi,
can you connect he library to the second ("good") fabric to see if the problem there persists or not to isolate the problem?
the pain is one part of the reality
Havard_3
Occasional Advisor

Re: FC connection drop to MSL 6030

-Removed the zoning configuration that was related to the backup server and MSL on both switches.
-Moved the MSL onto the other SAN switch, along with the backup server (using the "good" port on the controller card).
-Verified that they appeared on the switch, and recreated aliases and a zone for them.
-Ran the backup job again.

Same error after a while. MSL/e1200 drops out of the SAN switch, but the backup server remains.
Same results as before on portErrShow.

I've placed an order for a new fibre cable just to see if I can get the controller card to connect to both SAN switches and rule out a cable error, but it does look like the error is related to the library since it gets disconnected from them both?
Havard_3
Occasional Advisor

Re: FC connection drop to MSL 6030

Replaced the fibre cable going from the second port on the controller card on the server and to the switch, no change.

Put the same new fibre cable between the e1200 and the switch, and backups have now been running for over two hours. So if all goes well I'll let a job run over night and see what happens.


Rhoderick B. Boral
New Member

Re: FC connection drop to MSL 6030


Hi,

Do you have the solution already?
This is the same case for us right now.
MSL 8096, Brocade switch, Windows clients, HBA (EMulex).

Thanks for your reply!
Havard_3
Occasional Advisor

Re: FC connection drop to MSL 6030

Hi,

Yes, more or less. The last fibre cable that we replaced has fixed the backups. Still only have one connection up from the emulex board, but we're replacing the server soon so once the backups got running fine we just left it as is.