This is the most important step in troubleshooting SIA situations. Identify the neighbor 10.10.1.2 to be responsible for the route being in SIA state. The steps to isolating the SIA mode problem are: Listing 8.31 shows that the neighbor 10.10.1.2 is not replying consistently, resulting in the route 192.168.15.0/24 being in the SIA state. Listing 8.31 Output of the show ip eigrp topology active Command in A1Ĭodes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - Reply status A 192.168.15.0/24, 0 successors, FD is 512640000, Q 1 replies, active 00:00:01, query-origin: Local origin via 10.10.2.2 (Infinity/Infinity), Serial1 Remaining replies: via 10.1.1.2, r, Serial0
This is evident in the show ip eigrp topology active command in A1, as shown in Listing 8.31. In Figure 8.7, one of the routes is always seen in SIA mode. Router A4 is a neighbor of A2.įigure 8.7: An EIGRP network showing the SIA state. Figure 8.7 shows an EIGRP network in which routers A2 and A3 are neighbors of router A1. The neighbor that fails to reply is removed from the neighbor table.Ĭonsider the example depicted in Figure 8.7 to understand issues pertaining to SIA routes. Such a route is said to be in Stuck-In-Active (SIA) state. In some cases, replies of queries may not be received from all routers to which they were sent. If there are no feasible successors available in the topology table, the particular route is marked as active, and queries are sent out to all the neighbors regarding that route. In case of any topology change in EIGRP, the successors are searched from within the topology table.
0 kommentar(er)
