Troubleshooting the sensor
This topic describes common problems that occur with the SNMP MIB2 sensor and presents solutions for those problems.
The SNMP MIB2 sensor is not started, when the session sensor times out
- Problem
- When the session sensor fails because of a timeout, the SNMP MIB2 sensor is not started.
- Solution
- If the session sensor times out, the SNMP MIB2 sensor is not started by default. If you want to
change this behavior, set the
com.collation.discover.agent.sys.SessionSensor.timeout.snmpproperty to true in the collation.properties file. For details, see Configuring the collation.properties file entries.
The sensor incorrectly identifies L3 switches as routers
- Problem
- For SNMP devices that Agile Service Manager does not already know about, Agile Service Manager occasionally misidentifies L3 switches as routers.
- Solution
- Use the SNMP templates to provide Agile Service Manager with hints to correctly identify the switches and routers.
The sensor fails doing an OS discovery
- Problem
- The sensor fails doing an OS discovery.
- Solution
- Verify the credentials provided in the access list and check to ensure that SNMP is running on the Agile Service Manager client.
DataPower device discovered with SnmpMib2Sensor does not merge with data discovered by other sensors
- Problem
- DataPower device that is discovered with SnmpMib2Sensor does not merge with the data that is discovered by other sensors.
- Solution
- When DataPower device is configured to use the SNMP protocol, it can be discovered by using SnmpMib2Sensor. However, DataPower uses a custom set of SNMP OIDs that SnmpMib2Sensor does not query. These OIDs are read only by the CustomMib2ComputerSystem sensor with the use of Jython extension script.