1331 - IP Route Table Entry Conflict

A conflict exists between user configured static IP routes and dynamically added routes. (The Integrate Message Feeder application monitoring dynamically creates host specific IP routes to an IMF VIP address.) There are two scenarios in which such a conflict can result:

1. If an Integrated Message Feeder application receives a service accept message and attempts to add a host specific IP route for the IP address received in the service accept message and there is an user configured static IP route (entered by ent-ip-rteEAGLE 5 ISS command) whose destination is the same IP address, then the route is not added and the UIM is sent indicating the route and result.

2. If a user enters a host specific IP route using the ent-ip-rte command and there currently exists a dynamically added route with the same destination IP address, then the dynamic route is deleted, the static route is added, and this UIM indicating the result is generated.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0003.1331 CARD 1213 INFO IP Route Table Entry Conflict
Dynamic IP Route Add Fail
Destination = 172.130.155.110
Gateway = 172.120.154.111
Mask = 255.255.255.255
Report “Date:02-02-21 Time:02:07:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Resolve the IP Address conflict.

One must either change the Integrated Message Feeder application VIP address or delete the static IP address using the following command:

dlt-ip-rte