![]() So Frame Relay and SDLC which are multi-point do have layer 2 addresses to specify which peer you are sending to. Layer 2 resolution is important if the connection is multi-point and you may have more than one peer on the serial connection. If you think about it this makes good sense. With PPP or HDLC when the router prepares to send a frame out the interface it just sends it without trying to specify a layer 2 address. But the serial protocols that we use most often, PPP and HDLC do not have layer 2 resolution. The answer to your question about layer 2 resolution is that some serial protocols do have layer 2 resolution, such as Frame Relay that uses the DLCI for layer 2 resolution or SDLC which had a station polling address for layer 2 resolution. It goes 1 to 2 and then 2 to 1 then 1 to 2 then 2 to 1 then 1 to 2 where it times out so 2 generates the response that shows up in the output. It goes 1 to 2 and then 2 to 1 then 1 to 2 then 2 to 1 where it times out so 1 generates the response that shows up in the output. It goes 1 to 2 and then 2 to 1 then 1 to 2 where it times out so 2 generates the response that shows up in the output. It goes 1 to 2 and then 2 to 1 where it times out so 1 generates the response that shows up in the output. It goes 1 to 2 where it times out so 2 generates the response that shows up in the output. Basically this is what is happening"įirst traceroute probe has TTL = 1. You say it should create a loop, and the output does demonstrate looping behavior. I am not clear whether you are asking a question about the traceroute output. My last query, what serial link use for resolution at layer2, if no layer2 info used then packet should have drop. VRF info: (vrf in name/id, vrf out name/id) Now lets say If i configured R1: 10.10.10.1/24 R2 10.10.10.2/24( though in real scenario we use /30 on serial) and try to ping 10.10.10.4 from R1 which do not exist. Here when I ping R1 ip then req goes to R2 and R2 check if the intended req ip belong to its own subnet if it then it will send its to R1. I know Ethernet communication mechanism but bit confused on serial link.Īwaiting for enlightenment on this query.įrom your input I understand, in serial if we ping IP then its first redirect towards peer end and then peer redirect it towards the originator. Then I tried to ping my own IP 10.10.10.1, ping failed !!,why I am not able to ping my own IP, whereas in ethernet it works fine.Īssuming serial don't used L2 address and its fail during L2 lookup, then how router serial port communicate. Packet sent with a source address of 10.10.10.1 ![]() Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: Now I pinged 1.1.1.1 from R1 having source 10.10.10.1, which won't ping( it is obvious) Now I changed R2 s1/1 ip address to 1.1.1.1/30 whereas R1 s1/1 IP is same. Success rate is 100 percent (5/5), round-trip min/avg/max = 12/25/68 ms Sending 5, 100-byte ICMP Echos to 10.10.10.2, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 40/52/100 ms Sending 5, 100-byte ICMP Echos to 10.10.10.1, timeout is 2 seconds: ![]() Recently I face one issue when serial port/line protocol up and I was not able to ping my own my. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |