- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2020 01:15 PM
I am trying to modify the value of the MID Server parameter mid.snmp.request.timeout. After I modify the value, save the changes, and restart the MID Server the value reverts back to the original value.
The current value is 6000 and I would like to change the value to 2000. The steps I am taking are below.
- Navigate to MID Servers > MID Servers
- Click on the name of the target MID Server
- Click on the Configuration Parameters tab
- Find the Parameter name of mid.snmp.request.timeout
- Double-click on the value column and modify from 6000 to 2000
- Click Save
- Verify the value is now showing as 2000
- Click Restart MID Server
After the MID Server service is restarted the value of mid.snmp.request.timeout shows the original value of 6000. I can successfully modify the value of other Configuration Parameters, such as mid.log.level or mid.snmp.session.timeout. This happens in our test and production instances.
The MID Server parameters document notes "You can override this parameter with the timeout SNMP probe parameter." I checked SNMP - Classify and SNMP - Identify probes and neither had this paramater.
Is there another setting somewhere for mid.snmp.session.timeout that may be overwriting my changes at the MID Server level?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2020 11:26 AM
I opened a HI Case and they found the cause immediately.
We have been setting parameters on each individual MID Server. I didn't realize there was a way to set a parameter across all MID Servers.
If you go to MID Server > Properties, anything listed there will be applied to ALL servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2020 01:44 PM
Edit: sorry just realized you checked. that's the only other spot that I know of, but what you could do is just set at the probe parameter to what you want.
There's a probe parameter for SNMP timeout that might be overriding it
https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_SNMPProbeParameters.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2020 07:13 AM
Yes I checked that one well, thank you for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2020 11:26 AM
I opened a HI Case and they found the cause immediately.
We have been setting parameters on each individual MID Server. I didn't realize there was a way to set a parameter across all MID Servers.
If you go to MID Server > Properties, anything listed there will be applied to ALL servers.