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. If this situation occurs in your configuration, you must remove the old target or source from the database, as well as any IP Path Echo collectors that use the old ta
