Chapter 4 Modifying IPM Components

Setting SNMP Timeout and Retry Environment Variables

Setting SNMP Timeout and Retry Environment Variables

An IPM server and source router need not be physically near each other. In fact, they can be thousands of miles apart. However, as the distance increases, so does the time it takes the source router to respond to SNMP requests. If the response time exceeds a predefined timeout value, IPM interprets the delay as an SNMP timeout, which could impact the operation of your collectors.

For example, if you have an IPM server in New York and a source router in Tokyo, SNMP timeouts might prevent you from configuring collectors on the source router. Or you might be able to configure the collectors, but timeouts might result in periods when no statistical data can be collected from the source router.

If you experience this problem, the best solution is to define an additional IPM server that is physically nearer the source router. However, if that is not an option, you can set new values for the SNMP timeout and retry environment variables.

Note SNMP environment variables are engineered for all but the most extreme operating conditions. Modifying these variables can adversely affect IPM’s performance, resulting in unacceptably long delays in responding to user requests. Unless you are certain that you must, you should not modify these variables.

 

 

User Guide for Internetwork Performance Monitor

 

 

 

 

 

 

OL-11291-01

 

 

4-29

 

 

 

 

 

Page 123
Image 123
Cisco Systems OL-11291-01 manual Setting Snmp Timeout and Retry Environment Variables