Netgear FSM726v3 7200 managed switch v8.x CLI reference manual - Page 395

Managed Switch CLI Manual, Release 8.0 debug rip packet This command turns on tracing of RIP requests and responses. This command takes no options. The output is directed to the log file. Default Format Mode disabled debug rip packet Privileged EXEC A sample output of the trace message is shown below. JAN 01 00:35:15 192.168.17.29-1 RIP[181783160]: rip_map_debug.c(96) 775 % Pkt RX on Intf: 1/0/1(1), Src_IP:43.1.1.1 Dest_IP:43.1.1.2 Rip_Version: RIPv2 Packet_Type:RIP_RESPONSE ROUTE 1): Network: 10.1.1.0 Mask: 255.255.255.0 Metric: 1 ROUTE 2): Network: 40.1.0.0 Mask: 255.255.0.0 Metric: 1 ROUTE 3): Network: 10.50.50.0 Mask: 255.255.255.0 Metric: 1 ROUTE 4): Network: 41.1.0.0 Mask: 255.255.0.0 Metric: 1 ROUTE 5): Network:42.0.0.0 Mask:255.0.0.0 Metric:1 Another 6 routes present in packet not displayed. The following parameters are displayed in the trace message: Parameter TX/RX Intf Src_IP Dest_IP Rip_Version Packet_Type Routes Number of routes not printed Definition TX refers to a packet transmitted by the device. RX refers to packets received by the device. The interface that the packet came in or went out on. Format used is unit/slot/port (internal interface number). Unit is always shown as 1 for interfaces on a non-stacking device. The source IP address in the IP header of the packet. The destination IP address in the IP header of the packet. RIP version used . Type of RIP packet. . Up to 5 routes in the packet are displayed in the following format: Network: Mask Next_Hop Metric The next hop is only displayed if it is different from 0.0.0.0. For RIPv1 packets, Mask is always 0.0.0.0. Only the first five routes present in the packet are included in the trace. There is another notification of the number of additional routes present in the packet that were not included in the trace. Utility Commands v1.0, July 2009 6-78