Too many counts of er_bad_os indicate that packets were dropped from the SAN, causing latency or link failure. Too many "enc out" counts without "crc err" counts, implies primarily a cable problem, and if Lr_in and Ols_out are quite equal then problem is most likely not caused by the switch.Ī high er_bad_os count might point to an incorrect fillword setting.
#Brocade sfps Offline
Ols_out -> offline reset out (primitive sequence), does not apply to FL_Portīack to the switch log. Ols_in -> Offline reset in (primitive sequence), does not apply to FL_Port Lr_out -> Link reset Out (primitive sequence), does not apply to FL_Port L r_in -> Link reset In (primitive sequence), does not apply to FL_Port Note: If the “Ols_in” value is higher than the “Lr_out” value, then the problem source is, in most cases, more related to the attached device (sending those offline sequences) and the switch responds to them with a link reset.Įnc out -> Encoding error outside of frames Index Port Address Media Speed State ProtoĠ 0 020000 id 4G Online FC F-Port 10:00:00:00:c9:5d:b3:ca "out") or are caused by the switch ("out" > "in"). The switch command consoles show two dedicated FC ports split to the dedicated FC switches. This issue is caused by a connectivity problem in the SAN fabric, and can be confirmed by reviewing the SAN switch log. Backup jobs for clients to an 5220 Appliance using Fiber Transport (FT) always fail with status 83.
0 kommentar(er)
