Traverse provides a mechanism for refreshing maximum values or SNMP object identifiers (SNMP OID) when an SNMP test has changed. For example, when memory or disk capacity has changed, tests that return percentage-based values would be incorrect unless the max value (for determining 100%) is refreshed. Additionally, in some cases even replacing a device with similar hardware can cause the SNMP OIDs to change, thus creating a mismatch between the current SNMP OIDs and the ones which Traverse discovered during initial provisioning.
If one of the previous situations occurs, the user need only repeat the test provisioning process for a changed device. Traverse will discover whether any material changes on the device have occurred and highlight those changes on the Update Tests page, giving the user the option to also change thresholds and actions that apply to the test. Traverse can also automatically check for these changes automatically. See Test Parameter Rediscovery for more information.
If you see a non-OK test, you can click on the non-OK icon itself (at the test level, not device level) to see the returned error message. However, if the OID is marked as "invalid" and the tests do not exist (e.g. a port module or disk partition no longer exists), then these tests should be deleted manually since Traverse will not automatically delete these tests.