Re: Can't Ping Local Serial Interface of 2610
Dear Ken and John I really appreciate your discussion. I really understood the concept of mapping between subinterface and DLCI number. I surly understood that in ptp connection, all the router need to know is which DLCI number is associated with given subinterface address. However, what is still not clear to me is multipoint connection. In multipoint connection, there could several DLCI number. Therefore, a specific DLCI number should be associated with interface ip address. Now, my question is which interface ip address should be associated with local DLCI number between ip address of subinterface in your site or ip address of subinterface on remote site. In ptp connection above, DLCI number was associated with ip address of subinterface in your site (not remote site). According to the ciscopress book that I have, in multipoint connection, a specific DLCI number was associated with the ip address of interface on remote site. I am not sure if I asked clear question to be understood. If you need more explanation regarding my question, I am willing to send you back immediately. Thanks in adv. jeongwoo --- John Dill [EMAIL PROTECTED] wrote: Dear Ken, Thanks for the followup. The reason for the change in the frame (dlci) map command is related to the fact that it is a point-to-point interface. Consider further: The purpose of the frame map statement is to explicitly map the L3 address to a L2 dlci number. On a multipoint interface, there may be several dlci numbers in play, so the particular dlci must be explicitly paired with a L3 address. However, on a point-to-point sub-interface there is only one dlci number. Once the dlci is known, the router can make the connection by considering the sub-interface's ip address and mask. If a packet is to be forwarded to the subnet defined by the IP address on a given ptp sub-interface, then it is mapped to the single dlci associated with this ptp link. All the router needs to know is what dlci is associated with this ptp sub-interface. It then has the info it needs to map L3 addresses to that dlci. HTH, John "Claussen, Ken" [EMAIL PROTECTED] 10/18/00 08:42AM After adding the Frame-relay Map statement, as suggested by several people, I was able to ping the local serial Interface. I then created the interface as a Sub-interface and attempted to use the Frame-relay map command and received the "You should use the Frame-Relay Interface-dlci" command from the router. When the Tnterface-dlci command was applied to the sub-interface (s0/0.1) IP traffic began passing back and forth on the serial link. I also had to add the appropriate static route to the default gateway, as suggested, so other clients on the development network (192.168.1.0) would know where to send traffic destined for the test network (192.168.3.0) or the Intermediate network (192.168.4.0). Routes had already been setup on the routers, but the default gateway did not know about the 192.168.4.0 network until I added the static route. After adding the route all traffic successfully was passed from all clients to the Test network via the intermediate successfully. I understand now why I had to assign the Map statement to the global interface, so that layer Layer 3 knows which layer 2 interface to use, what I am still a little confused about is why the command changes when applied to a sub-interface to Frame-relay interface-dlci instead of Frame Relay Map IP. I appreciate all responses they all helped me to troubleshoot and understand the Frame Relay technology successfully, thank you. Ken Claussen MCSE CCA CCNA [EMAIL PROTECTED] "The mind is a terrible thing to waste!" _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Can't Ping Local Serial Interface of 2610
Dear Ken and John I really appreciate your discussion. I really understood the concept of mapping between subinterface and DLCI number. I surly understood that in ptp connection, all the router need to know is which DLCI number is associated with given subinterface address. However, what is still not clear to me is multipoint connection. In multipoint connection, there could several DLCI number. Therefore, a specific DLCI number should be associated with interface ip address. Now, my question is which interface ip address should be associated with local DLCI number between ip address of subinterface in your site or ip address of subinterface on remote site. In ptp connection above, DLCI number was associated with ip address of subinterface in your site (not remote site). According to the ciscopress book that I have, in multipoint connection, a specific DLCI number was associated with the ip address of interface on remote site. I am not sure if I asked clear question to be understood. If you need more explanation regarding my question, I am willing to send you back immediately. Thanks in adv. jeongwoo --- John Dill [EMAIL PROTECTED] wrote: Dear Ken, Thanks for the followup. The reason for the change in the frame (dlci) map command is related to the fact that it is a point-to-point interface. Consider further: The purpose of the frame map statement is to explicitly map the L3 address to a L2 dlci number. On a multipoint interface, there may be several dlci numbers in play, so the particular dlci must be explicitly paired with a L3 address. However, on a point-to-point sub-interface there is only one dlci number. Once the dlci is known, the router can make the connection by considering the sub-interface's ip address and mask. If a packet is to be forwarded to the subnet defined by the IP address on a given ptp sub-interface, then it is mapped to the single dlci associated with this ptp link. All the router needs to know is what dlci is associated with this ptp sub-interface. It then has the info it needs to map L3 addresses to that dlci. HTH, John "Claussen, Ken" [EMAIL PROTECTED] 10/18/00 08:42AM After adding the Frame-relay Map statement, as suggested by several people, I was able to ping the local serial Interface. I then created the interface as a Sub-interface and attempted to use the Frame-relay map command and received the "You should use the Frame-Relay Interface-dlci" command from the router. When the Tnterface-dlci command was applied to the sub-interface (s0/0.1) IP traffic began passing back and forth on the serial link. I also had to add the appropriate static route to the default gateway, as suggested, so other clients on the development network (192.168.1.0) would know where to send traffic destined for the test network (192.168.3.0) or the Intermediate network (192.168.4.0). Routes had already been setup on the routers, but the default gateway did not know about the 192.168.4.0 network until I added the static route. After adding the route all traffic successfully was passed from all clients to the Test network via the intermediate successfully. I understand now why I had to assign the Map statement to the global interface, so that layer Layer 3 knows which layer 2 interface to use, what I am still a little confused about is why the command changes when applied to a sub-interface to Frame-relay interface-dlci instead of Frame Relay Map IP. I appreciate all responses they all helped me to troubleshoot and understand the Frame Relay technology successfully, thank you. Ken Claussen MCSE CCA CCNA [EMAIL PROTECTED] "The mind is a terrible thing to waste!" _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Can't Ping Local Serial Interface of 2610
Dear Ken and John I really appreciate your discussion. I really understood the concept of mapping between subinterface and DLCI number. I surly understood that in ptp connection, all the router need to know is which DLCI number is associated with given subinterface address. However, what is still not clear to me is multipoint connection. In multipoint connection, there could several DLCI number. Therefore, a specific DLCI number should be associated with interface ip address. Now, my question is which interface ip address should be associated with local DLCI number between ip address of subinterface in your site or ip address of subinterface on remote site. In ptp connection above, DLCI number was associated with ip address of subinterface in your site (not remote site). According to the ciscopress book that I have, in multipoint connection, a specific DLCI number was associated with the ip address of interface on remote site. I am not sure if I asked clear question to be understood. If you need more explanation regarding my question, I am willing to send you back immediately. Thanks in adv. jeongwoo --- John Dill [EMAIL PROTECTED] wrote: Dear Ken, Thanks for the followup. The reason for the change in the frame (dlci) map command is related to the fact that it is a point-to-point interface. Consider further: The purpose of the frame map statement is to explicitly map the L3 address to a L2 dlci number. On a multipoint interface, there may be several dlci numbers in play, so the particular dlci must be explicitly paired with a L3 address. However, on a point-to-point sub-interface there is only one dlci number. Once the dlci is known, the router can make the connection by considering the sub-interface's ip address and mask. If a packet is to be forwarded to the subnet defined by the IP address on a given ptp sub-interface, then it is mapped to the single dlci associated with this ptp link. All the router needs to know is what dlci is associated with this ptp sub-interface. It then has the info it needs to map L3 addresses to that dlci. HTH, John "Claussen, Ken" [EMAIL PROTECTED] 10/18/00 08:42AM After adding the Frame-relay Map statement, as suggested by several people, I was able to ping the local serial Interface. I then created the interface as a Sub-interface and attempted to use the Frame-relay map command and received the "You should use the Frame-Relay Interface-dlci" command from the router. When the Tnterface-dlci command was applied to the sub-interface (s0/0.1) IP traffic began passing back and forth on the serial link. I also had to add the appropriate static route to the default gateway, as suggested, so other clients on the development network (192.168.1.0) would know where to send traffic destined for the test network (192.168.3.0) or the Intermediate network (192.168.4.0). Routes had already been setup on the routers, but the default gateway did not know about the 192.168.4.0 network until I added the static route. After adding the route all traffic successfully was passed from all clients to the Test network via the intermediate successfully. I understand now why I had to assign the Map statement to the global interface, so that layer Layer 3 knows which layer 2 interface to use, what I am still a little confused about is why the command changes when applied to a sub-interface to Frame-relay interface-dlci instead of Frame Relay Map IP. I appreciate all responses they all helped me to troubleshoot and understand the Frame Relay technology successfully, thank you. Ken Claussen MCSE CCA CCNA [EMAIL PROTECTED] "The mind is a terrible thing to waste!" _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Can't Ping Local Serial Interface of 2610
Trying do a frame-relay map statement that maps dlci no to the ip address of the interface you are trying to ping suaveguru --- "Claussen, Ken" [EMAIL PROTECTED] wrote: I am trying to setup a Frame Relay link in a lab situation. We have Layer 2 speaking LMI back and forth and the line Protocol is reported as Up on the serial interface. We assigned it a Private address and created a static route pointing at the serial interface of the other router. When you do a Show ip route it reports that all the routes exist as I believe they should (See config to follow) The Problem is we can't ping the IP address of the local serial interface 192.168.4.1, and I can't seem to figure out why. I beleive if I could ping the local serial interface then traffic would pass from our development network to our test network on 192.168.3.1. Please review my config on the 2610 and help me figure out why I can't ping the local interface before I use this router as a frisbee (which would be a shame considering it is a 2610) Begin Config Current configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname cisco2600 ! enable password cisco ! ip subnet-zero ! ! ! ! ! interface Ethernet0/0 ip address 192.168.1.3 255.255.255.0 no ip directed-broadcast ! interface Serial0/0 ip address 192.168.4.1 255.255.255.0 no ip directed-broadcast encapsulation frame-relay IETF no ip mroute-cache frame-relay interface-dlci 101 ! ip classless ip route 0.0.0.0 0.0.0.0 192.168.1.1 ip route 192.168.3.0 255.255.255.0 192.168.4.2 no ip http server ! dialer-list 1 protocol ip permit dialer-list 1 protocol ipx permit snmp-server engineID local 0009023094104240 snmp-server community public RO ! line con 0 exec-timeout 0 0 password cisco transport input none line aux 0 line vty 0 4 password cisco login ! no scheduler allocate end cisco2600# End Config Please help to save my sanity! all responses are greatly appreciated! Ken Claussen MCSE CCNA CCA _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Can't Ping Local Serial Interface of 2610
Title: Re: Can't Ping Local Serial Interface of 2610 After adding the Frame-relay Map statement, as suggested by several people, I was able to ping the local serial Interface. I then created the interface as a Sub-interface and attempted to use the Frame-relay map command and received the You should use the Frame-Relay Interface-dlci command from the router. When the Tnterface-dlci command was applied to the sub-interface (s0/0.1) IP traffic began passing back and forth on the serial link. I also had to add the appropriate static route to the default gateway, as suggested, so other clients on the development network (192.168.1.0) would know where to send traffic destined for the test network (192.168.3.0) or the Intermediate network (192.168.4.0). Routes had already been setup on the routers, but the default gateway did not know about the 192.168.4.0 network until I added the static route. After adding the route all traffic successfully was passed from all clients to the Test network via the intermediate successfully. I understand now why I had to assign the Map statement to the global interface, so that layer Layer 3 knows which layer 2 interface to use, what I am still a little confused about is why the command changes when applied to a sub-interface to Frame-relay interface-dlci instead of Frame Relay Map IP. I appreciate all responses they all helped me to troubleshoot and understand the Frame Relay technology successfully, thank you. Ken Claussen MCSE CCA CCNA [EMAIL PROTECTED] The mind is a terrible thing to waste!
