Unsolved
This post is more than 5 years old
2 Intern
•
155 Posts
0
1692
October 15th, 2012 14:00
DMX-4 issue
Hi All,
Every 2 hours we have this message on the SMC,
Critical error 2 Fibre Channel Front End has failed or inoperable.
And in DMX-4 command line symevent
A Fibre Channel optical module has experienced a problem'
And all our SRDF/S devices give a message that SRDF/S not in synchronised state.
No Events found!
PedalHarder
3 Apprentice
•
465 Posts
0
October 15th, 2012 15:00
I suggest you open a service request and have a PSE take a look at your array.
PedalHarder
3 Apprentice
•
465 Posts
1
October 15th, 2012 15:00
So no CRC or other errors accumulating on the switch port?
Does the error message indicate which front-end port is failing?
Perhaps move the FA to a different switch port.
If the switch port is the only part of the storage infrastructure used by the problem FA you may want to look at replacing the cable between array and switch port.
KD8EWE
2 Intern
•
155 Posts
0
October 15th, 2012 15:00
Fibre Channel front-end has failed or is inoperable. there is no specific FA in the error message. Any inputs
KD8EWE
2 Intern
•
155 Posts
0
October 15th, 2012 15:00
PSE logged in and checked the DMX, there is no issue on DMX side. he suspect external network.
we checked our SAN side mostly CISCO but nothing could be seen.
if anyone else faced this kind of issue and if it is external network what it could be??
PedalHarder
3 Apprentice
•
465 Posts
1
October 15th, 2012 16:00
You should see the issuing director in the symevent output. Take a look at the second column of the symevent output with heading "Dir".
RobertDudley
2 Intern
•
448 Posts
1
October 17th, 2012 07:00
If you think you ahve a bad director issue this command:
symcfg -sid xxxx list -dir all (will list all directors)
symcfg -sid xxxx list -FA all (will only list FA's)
Look for any director port that has Dead listed in it.
KD8EWE
2 Intern
•
155 Posts
0
October 17th, 2012 13:00
Hello Friends,
All the FAs and RF went offline at least for 30 seconds. I have never seen this in my career.. it happened two times within the time span of 2 hours. EMC's explanation was Low Cache on the R2 Frame of SRDF.. it reached bottle neck and was sending back the request because of heavy application server started recently. Now resolved by increasing the cache by EMC Customer engineer.
Thanks for all your help. It was almost a Disaster situation.