Need assistance on implementing Isilon probe and schema update
Article ID: 270726
Updated On:
Products
Issue/Introduction
We need assistance on implementing the isilon probe and using RESTMON and MCS.
Environment
- Release: 20.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
https://knowledge.broadcom.com/external/article/135336/
We have a rest schema for Isilon. WE officially use restmon probe to support this.
Steps:
1. Make sure the restmon probe is downloaded and present the local archive on the Primary hub.
Restmon v3.37
- You can deploy the restmon probe to a hub or robot - but as with most monitoring probes try to keep it off the Primary hub.
- Restmon is essentially a remote probe because you'll provide the credentials to access the remote rest api.
2. Extract the isilon_schema.json file as you'll need to upload the .json not the zip.
3. 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.
4. 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 go 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 chnages 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.
5. 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.
Additional Information
The latest Isilon schema is attached to this article.
Make sure the restmon probe is in the locall 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.
Monitor Technologies using Restmon
When uploading through the Operator Console, the friendly name you give it will be what you see in MCS when you go to create a profile. If you just name it as Isilon, you'll see the template in MCS as "Setup Isilon". Remember, if you need to make any 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 schema at some point.. Once uploaded it will be available in MCS for use.
You can deploy the restmon probe to a hub or robot - but as with most monitoring probes try to keep it off the Primary hub. Restmon is essentially a remote probe because you'll provide the credentials to access the remote REST API.
Once you create the MCS 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 but note that it takes a bit more time to let MCS deploy it.
Attachments
Feedback
