Quantcast
Channel: IEOC - INE's Online Community
Viewing all articles
Browse latest Browse all 10744

How does ping work with "no ip routing"

$
0
0

Hi everyone,

If I have a switch where "ip routing" has not been enabled, how does the ping get through?

 

For example, I have an interface on this switch with ip address 155.1.37.7 and I am directly connected to a router with IP address 155.1.37.3. The pings are successful; however, because IP routing is turned off when I issue "sh ip route" from the switch I don't see any connections. Below is the output from "debug ip packet" for this ping. If possible, could you explain what this debug is showing?

 

SW1#ping 155.1.37.3 repeat 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 155.1.37.3, timeout is 2 seconds:
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 9/9/9 ms
SW1#
*Mar  1 02:05:25.478: IP: s=0.0.0.0 (local), d=155.1.37.3, len 100, local feature, RCLI(7), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Mar  1 02:05:25.478: IP: s=0.0.0.0 (local), d=155.1.37.3, len 100, local feature, Local Clustering(8), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Mar  1 02:05:25.478: IP: tableid=0, s=0.0.0.0 (local), d=155.1.37.3 (FastEthernet0/3), routed via RIB
*Mar  1 02:05:25.478: IP: s=155.1.37.7 (local), d=155.1.37.3 (FastEthernet0/3), len 100,
SW1#sending
*Mar  1 02:05:25.478: IP: s=155.1.37.7 (local), d=155.1.37.3 (FastEthernet0/3), len 100, output feature, Check hwidb(72), rtype 1, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Mar  1 02:05:25.478: IP: s=155.1.37.7 (local), d=155.1.37.3 (FastEthernet0/3), len 100, sending full packet
*Mar  1 02:05:25.487: IP: s=155.1.37.3 (FastEthernet0/3), d=155.1.37.7, len 100, input feature, MCI Check(63), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
*Mar  1 02:05:25.487: IP: s=155.1.37.3
SW1#(FastEthernet0/3), d=155.1.37.7, len 100, rcvd 1

 

Thanks for your help!


Viewing all articles
Browse latest Browse all 10744

Trending Articles