Unsolved
This post is more than 5 years old
2 Posts
0
1477
October 9th, 2013 05:00
What does Symmetrix device event symbolic code "SEVT_ACCESS_TO_NR_DEVICE" represents?
Hi,
I am using EMC symmetrix API "SymEventGet" to get Symmetrix events.
I am getting many events from Symmetrix DMX and VMAX arrays with symbolic code of the event as "SEVT_ACCESS_TO_NR_DEVICE" string. Also the numeric code for these events shows "0X003f" and the director identifier refers to a port such as "FA-10D".
I am getting nearly 1000 events with different directory identifier but with same symbolic code "SEVT_ACCESS_TO_NR_DEVICE".
I am concerned about what these events are and do I need to take any action on this storage device?
Regards,
Shivaraj
0 events found
No Events found!


bmshivaraj
2 Posts
0
October 9th, 2013 06:00
I could see there are lot of such symbolicCodes from SYMAPI.h file. If you can share me any document which clearly explains what each of these symbolic Codes represents that will be great.
Regards,
Shivaraj
LBM99
1 Rookie
•
119 Posts
0
October 9th, 2013 09:00
I couldn't find any official docs to provide but did find this description in an old internal problem tracking ticket:
"Access was attempted to a Not Ready device"
In that ticket there were also xx33 errors logging in the Symmetrix. Your array may have some too. You can ask your local EMC Support to connect and see what devices any x33 errors are logging on, and what the state of those volumes are.
We typically see those error codes in situations where an application is trying to access or check status of a volume that is unavailable for reasons like being a target of a TimeFinder session and the volume is NR due to the TFsession state, or an unbound Thin volume, or a NR RDF volume, etc. The array usually has no problems in these situations and the errors are usually not even a cause to a call home. If there was a serious problem, then you would most likely be seeing other obvious issues, and more serious error codes would have logged that would generate a dial home. Of course there are exceptions to every rule, so probably worth having someone take a look, even if just for the benefit of your own knowledge.
Also note that the old problem ticket was not for the logging of the event itself. It was for a very old problem where the event code was being logged to the incorrect volume number and is almost guaranteed to be not related to what you are seeing, except for the meaning of the event code itself.
Hope that helps a little. Let us know what you find.
Mike