Filter
Top Products
A-16
User Guide for Internetwork Performance Monitor
OL-11291-01
Appendix A IPM FAQs and Troubleshooting Tips
Troubleshooting IPM
Q.
How do I access the database directly?
A.
Follow these steps on your machine:
On Windows machine:
cd install dir/Server/bin
setIPMEnv
isql –UDBA –P
dbpassword
On Solaris machine:
csh
cd
install dir/CSCOipm/bin
Source setIPMEnv
isql –UDBA –P
dbpassword
Where install dir is the IPM installed directory.
Q.
I am not getting any response from SA Agent Responder, how do I resolve this problem?
A.
If Enhanced UDP jitter collectors get no response from the SA Agent Responder on a target router,
the Responder might have become disabled, or it might show control message errors.
To determine whether the Responder is disabled, enter the following command on the target router:
sh rtr resp
If you see this message, the Responder is disabled:
RTR Responder is: Disabled.
If you see these messages, the Responder is enabled, but control message errors have occurred:
Number of Errors:
Recent Error Sources:
To correct either of these problems disable and enable the Responder.
Q.
What should I do when all DHCP IP Address Leases are Exhausted?
A.
When you use DHCP operations with certain DHCP servers, all DHCP IP address leases on the
servers can be exhausted. To reduce the likelihood of this problem occurring:
• Reduce IP address lease times on your DHCP servers. Long lease times increase the likelihood
of this problem occurring.
• Change the frequency of the DHCP operations from the default of 60 seconds to 5 minutes.
• Do not configure a large number of DHCP operations on the same subnet (using the same DHCP
server).
Q.
What should I do when IP Path Echo Discovery Prevents IP Address Change?
A.
In general, you should not allow an IP Path Echo collector to use another collector’s source or target
as an intermediate hop. However, if you do allow this configuration, the Change IP Address utility
fails as a result of this sequence of events:
1. An IP Path Echo collector uses another collector’s source or target as an intermediate hop.
2. The IP address of the source or target changes.
3. The IP Path Echo operation automatically discovers the change and adds the new address to its data
structures in the IPM database.
4. You run the Change IP Address utility.
5. IPM detects that the new address already exists in the IP Path Echo data structures. Since you cannot
change an IP address to an address that already exists in the database, IPM does not allow you to
make the change, and the Change IP Address utility fails.