Default Offset Filters will impact new created Masks under Generic-SNMP
Hi Expert,
We found that our new created Masks collecting will be impacted by default Offset Filters, like "calculate-size.xml" under "APG\Collecting\Value-Offset-Filter\Generic-SNMP\conf". For example, when we name a new metric name as "Capacity", we will get warning "property 'StUnitSz_test' not found" which is defined in "calculate-size.xml", this will cause the "Capacity" cannot be collected into database.
May we know how to make our masks ignored by these default Offset Filters, and how to create new default Offset Filters that only impact our masks?
Or may be we should create a new SNMP poller out of Generic-SNMP, may we know how to create a new one safely?
We found that we can create a new poller which totally same as Generic-SNMP in centralized-management, it have all the folder and configuration files same as Generic-SNMP, but while import our masks, the our customize configurations will only be generated into Generic-SNMP, not our XXX-SNMP poller.
May we know how to import our mask into our own XXXX- SNMP poller?
In order to import your custom mask in the new collector you installed, you need to register the new collector either in snmp device discovery or in the SNMP Collector UI (depending on which one you are using).
Important point to keep in mind the SNMP poller uses a telnet control interface that uses port 2008 by default...if you did not choose another port when you installed it, you will need to edit slave-snmp-poller.xml and snmp-polling-distribution.xml (/opt/APG/Collecting/SNMP-Collector/ /conf) and select another port like 2018 and make sure the firewall is opened.
We hope our new created collector can be configured from IE, for example add mask and new device from IE. But as test, new mask and device was added to Generic-SNMP by default.
Could you please let us know a brief steps for Device-Discovery? Some of our customer don't have support entitle, but they still want to monitor 3rd party device via SRM.
The easiest way would be to create the new mask in the Mib Browser
and export it from the SNMP Collector UI.
You can then copy the snmp-mask block from the exported xml and paste it in the snmp-mask.xml (APG/Collecting/SNMP-Collector//conf)
You should backup all files before modifying them.
You will then need to create a capability discovery script, you can look at the existing capability discovery script (APG/Custom/WebApps-Resources/Default/device-discovery/snmp-capability-discovery-actions) as a reference and import it in SNMP device discovery.
You should then be able to add new devices and discover the custom capabilities.
Please note that custom mask and discovery scripts are not supported by DellEMC.
We still face same problem that by this way the configured masks and devices can only be deployed to "Generic-SNMP",not our new created one "NewTest-SNMP".We hope to import and configure from IE, but deploy it to our own "NewTest-SNMP".
warmghost
19 Posts
2333
0
Posted November 2nd, 2017 00:00
We found that we can create a new poller which totally same as Generic-SNMP in centralized-management, it have all the folder and configuration files same as Generic-SNMP, but while import our masks, the our customize configurations will only be generated into Generic-SNMP, not our XXX-SNMP poller.
May we know how to import our mask into our own XXXX- SNMP poller?