- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Allowing multiple SNMPv1-v2 community strings query access to grid members
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-17-2018 08:33 AM - edited 05-17-2018 01:00 PM
We are runing 8.2.4 and currently allow SNMP community string1 from our own monitoring system to query any grid member. We have a new discovery tool being managed by another team that needs to be able to use SNMP community string2 to query our grid members. I do not see anything in the admin guide abotu how to allow multiple v1-v2 community strings.
Re: Allowing multiple SNMPv1-v2 community strings query access to grid members
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-24-2018 09:14 AM
The SNMP configuration in NIOS for v1/v2 allows you to set only one community string, while SNMPv3 allows for multiple strings.
Regards,
Tony
Re: Allowing multiple SNMPv1-v2 community strings query access to grid members
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-12-2018 07:06 AM
Hello,
we need different communities as well.
We haven't got only our own monitoring systems but also customer/vendor managed monitoring as well. Actually we can only tell our customer, the tool is not able to handle this which is frequently disappointing.
snmpd.conf is capable in having multiple read communities, why can't you add this as flexible option to the UI or anywhere else in API...
Re: Allowing multiple SNMPv1-v2 community strings query access to grid members
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-25-2020 10:19 PM - edited 03-25-2020 10:21 PM
Hi,
we need various networks also.
We haven't got just our own checking frameworks yet, in addition, client/merchant oversaw observing also. As a matter of fact, we can just tell our client, the apparatus can't deal with this which is every now and again baffling.
snmpd.conf is fit in having different understood networks, for what reason wouldn't you be able to add this as an adaptable alternative to the UI or anyplace else in API...