tcs@ccci.UUCP (Terry Slattery) (01/03/91)
Has anyone developed tools for diagnosing routing loops? I'm thinking of something that gets routing tables and configurations from multiple routers in a 'snapshot' fashion while the routing loop exists. Using SNMP would be nice, but the MIB doesn't contain an entry identifying the source of the routes (i.e. static, RIP derived, etc), making it more difficult to determine the source of the problem. [Should MIB-II incorporate such a variable?] I'm planning on building something to telnet to each router and grab a copy of the routing table, perhaps using 'expect', but wanted to check for existing tools first. Tools for analyzing the routing tables would be nice, but not critical. Thanks, -tcs
kasten@EUROPA.INTERLAN.COM (Frank Kastenholz) (01/03/91)
> From tcp-ip-RELAY@NIC.DDN.MIL Wed Jan 2 14:08:22 1991 > From: ccci!tcs@uunet.UU.NET (Terry Slattery) > To: tcp-ip@nic.ddn.mil > Cc: cisco@spot.colorado.edu > Subject: Routing loop tools > > Has anyone developed tools for diagnosing routing loops? I'm thinking of > something that gets routing tables and configurations from multiple routers > in a 'snapshot' fashion while the routing loop exists. Using SNMP would be > nice, but the MIB doesn't contain an entry identifying the source of the > routes (i.e. static, RIP derived, etc), making it more difficult to Yes it does ... look at ipRouteProto Frank Kastenholz Racal Interlan