Configuration 703
at least this time. Note that if your sample period did not include any samples when the connectivity was particularly slow then it may be advisable to add a small additional time on top of your measured longest response time (for example, another 500 ms) to allow for additional delays.
It is recommended that you do not enter a number of retries or a timeout period for any request type that is less than the default value. The defaults are reproduced below:
Table 108 Retry and Timeout Defaults
| Default Number of |
|
Request Type | Retries | Default Timeout Period |
|
|
|
DNS server | 1 | 3000 ms |
IP Ping | 2 | 2000 ms |
SNMP | 2 | 3000 ms |
HTTP/Telnet | 1 | 30000 ms |
End station | 2 | 6000 ms |
|
|
|
Note that the default timeout period for HTTP/telnet is high relative to the defaults for the other request types in order to allow the successful retrieval of NBX telephone information from NBX call processors during Network Discovery.
If you do not have an NBX call processor on a particular subnet then you may wish to specify a timeout period for HTTP/telnet requests on that subnet that is lower than 30000 ms. In such situations it is recommended that you do not specify a timeout period less than 6000 ms.
3Com Network Director can generate historical reports on devices in your network. These reports will include IP Ping response times and, for DNS servers, DNS response times. While these provide no details of retries, the response times shown in these reports can be used to help determine appropriate timeout periods for the devices in your network.
To generate a historical report for a device, select the device in the map or tree and then select Monitoring > Historical Report. See “Performance Reporting” on page 385 for more information on historical reports.