Implement Isilon probe and schema update using RESTMON and MCS
Article ID: 270726
Updated On:
Products
Issue/Introduction
We need assistance on implementing Isilon monitoring using RESTMON and MCS.
Environment
- DX UIM 20.4.* / 23.4.*
Cause
- Guidance
Resolution
EMC Isilon monitoring seems to be loosely (but not officially supported by a probe), through the use of snmpcollector or restmon
Dell EMC Isilon storage devices monitoring (broadcom.com)
We have a rest schema for Isilon. We officially use the restmon probe to support this.
Steps:
- Make sure the latest restmon probe is downloaded and present in the local archive on the Primary hub.
- You can deploy the restmon probe to a hub or robot - but as with most monitoring probes try to keep it off of the Primary hub.
- Restmon is essentially a remote probe because you'll provide the credentials to access the remote rest API.
- Extract the isilon_schema.json file as you'll need to upload the .json not the zip.
- The schema json file must be named with _schema.json so that it's recognized when uploading it through the Operator Console. Examples: isilon_schema.json, elasticsearch_schema.json, etc.
- Login to the Operator Console and go to Settings->Restmon
When uploading the schema through the Operator Console, the friendly name you give it will be what you see in MCS when you start to create a profile. If you just name it as Isilon, you'll see the template in MCS as "Setup Isilon." One thing of note here...once you make changes to the schema file, you have to use the same friendly name so it overwrites it. If you give it a different name it'll be a new template. This is especially important if you create your own at some point.- Use Notepad++ to edit the file for greatest readability and flexibility.
- Once uploaded it will be available in MCS for use.
- Once you create the profile, the restmon probe will be distributed to the robot.
You can also deploy the restmon probe to the robot through IM and then when you create the profile in MCS, it will recognize that restmon has already been deployed.
It make take some time for deployment.
NOTE: The restmon probe uses port 3033 by default for communication to Isilon devices. Be sure that firewalls, ACLs, etc allow communication from the robot where the restmon probe is deployed to the Isilon device on port 3033. If this communication is not allowed, the probe logs will report that the connection is refused.
Additional Information
The latest Isilon schema can be downloaded from support.nimsoft.com.(from restmon_schema-Samples. https://support.nimsoft.com/unsecure/archive.aspx?id=476)
[this latest version includes the feature F138395 Isilon Probe: Auto-discovery and monitoring of multi-node clusters]
restmon-sample-schemas
Make sure the restmon probe is in the local archive. Extract the isilon_schema.json file as you'll need to upload the .json rather than the zip. The schema json file must be named with _schema.json so that it's recognized when uploading it through the operator console. Examples: isilon_schema.json, elasticsearch_schema.json, etc.
Feedback
