The customer reported the alarm and informed us that before the alarm occurence he just created a new NFS share . After about a minute the alarm recovered by itself . Investigation will continue .
System Name: FileEngine
Occurred At: Tue May 20 09:55:13 2014 CEST
The status of key resources (name NFS ) of moudle (name NFS ) on clustered NAS engine node (Name FileEngine_02 ) is abnormal. The moudle can not work normally.
Collected the logs from the N8000 machine , file engine 2 and analyzed them . Noticed that just before the alarm occurence the customer created a new NFS share . In the immediate moment the alarm which is configured by default to work like this , started a search process to see which , if any ,NFS resource is abnormal . The output was that the resource is abnormal cause it caught it exactly when it was reloading (the resource) .
The creation of a new NFS share caused a reload of the new created resource in group NFS . During that same time the alarm performed periodical check (once every 90 seconds) and sent the output that the resource is abnormal (resource present but not in use)
This happened due to the design of the file engine . In conclusion there is nothing wrong with the system and this is , sort of speaking , normal.