2009-04-11 10:25 PM
Probably, the vFilers might have been discovered a long time ago. By
default, the vFiler monitor runs on hourly basis for each Storage
system. As you are managing the storage system successfully for more
than a year, the vFilers of this storage system might have been
discovered already if they were exist.
So, the corresponding event "vFiler Discovered" should have gone to
"History" and further it might have been purged from your DB if the
"Events Purge Interval" is set to default (25.71 weeks).
If you want to see this event now, probably you can perform one of the
following tasks :
=> Create a new vFiler @ your storage system. Wait for an hour and look
at "vFiler Discovered" event in DFM.
=> Delete the existing vFiler from DFM DB and wait for an hour. DFM will
discover this when its next vFilerMon runs.
Note : The later one is not suggested if it is a production environment.
You can push the discovery on-demand using "dfm host discover
<storage_system>" if you dont want to wait for the periodic vFilerMon
2009-04-12 02:51 AM
>> I've run dfm host discover for both the hosting filer as well as the vfiler and no event of this type has been logged. Does host discovery also need to be enabled?
- Are there any vFilers on the hosting filer that are not yet discovered by OpsManager in your environment.? If so, please give more details.
- By host discovery, I assume you mean the option "discoverEnabled". This need not be enabled for vFilers to be discovered on an already discovered
However, there is a separate option named "discoverVfilers" that needs to be enabled for vFiler discovery.
Please check whether it is enabled in "dfm option list".
>> Yes, the hosting filer has been in the environment and managed/monitored by DFM for well over a year.
This event is generated on the vFiler that is discovered as an Informational event.
Have you checked the following::
"dfm report view events-history <vfiler-id> | grep -i discover" for a discovered vFiler, to see if the event is present.