RAF@CU.NIH.GOV (Roger Fajman) (10/01/90)
Here's a few suggestions for enhancements that I think would help in figuring out routing problems: DEBUG IP-ROUTING net-number Only routing changes for the specified network number would be displayed. For subnetted networks it would be helpful to be able to specify either a single subnet or the entire network. DEBUG IP-ROUTING DEFAULT Same as above, but for the default route. DEBUG routing-process [net-number] [INTERFACE interface-name] [IN|OUT] If a network number is used, only incoming and outgoing routing information for the specified network or subnet would be displayed. If IN or OUT is specified, only incoming or outgoing routing information would be displayed. If an interface is specified, the information display would be limited to that interface only. DEBUG routing-process DEFAULT [IN|OUT] [INTERFACE interface-name] Same as above, but for the default route. With 1500-1600 routes coming in from SURAnet, DEBUG RIP just floods the console without accomplishing much that's useful. DEBUG IP-ROUTING doesn't tell me what's going on unless the routes are changing and even then it shows me a lot of changes that I'm not interested in. We had a problem with the default route recently (including a bug in the cisco software) and it would have helped a lot if SHOW IP ROUTES gave the same information about the source of the default route that it does for other routes. Has anyone else noticed that in 8.1(19) DEBUG IP-ROUTING displays XNS RIP changes too? Seems like a bug. Thanks to cisco, by the way, for implementing the TRACE command in 8.1. It's very nice.