that command isn't necessary with back-to-back cabling. the interface's controller can determine the cablings orientation and set the interface to the correct type automatically.
what I don't see is the dce providing a clocking rate. scott ""John Neiberger"" wrote in message news:[EMAIL PROTECTED] > In addition, one side needs to act as the frame relay DCE. Use the > 'frame-relay intf-type dce' command to accomplish this. > > John > > >>> Larry Letterman 3/14/03 11:38:56 AM >>> > somewhere in the routers config there will need to be a frame > switch command and a frame route command, which is how the Frame > Switch that Scott mentions works... > > Larry Letterman > Network Engineer > Cisco Systems > > > ----- Original Message ----- > From: s vermill > To: [EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 12:10 PM > Subject: RE: Back-to-back FR P2P circuits with Different Dlci's [7:65355] > > > Cisco Nuts wrote: > > > > Hello, > > Does any one know why if 2 routers configured back-to-back for > > frame relay > > point-to-point intf. using different dlci's does NOT work? > > Well, it's been a while since I worked with FR. But if you think about a > "true" FR circuit, DLCIs are locally significant but both the customer prem > equipment and the FR switch have to have matching DLCIs. It's essentially > a > logical circuit ID that needs to be agreed to by both end points in order > for communication to take place. If you have three routers, you can > configure one to act as a FR switch. Then two spur routers can talk, via > the "switch," on different DLCIs. > > > Unless, they are defined the same on both routers, does it > > work!! > > Here is my config: > > R5#ri s1.1 > > Building configuration... > > > > Current configuration : 147 bytes > > ! > > interface Serial1.1 point-to-point > > ip address 1.1.1.1 255.255.255.0 > > ip router isis > > frame-relay interface-dlci 102 > > clns router isis > > end > > > > R5# > > > > > > R6#ri s0.1 > > Building configuration... > > > > Current configuration : 200 bytes > > ! > > interface Serial0.1 point-to-point > > ip address 1.1.1.2 255.255.255.0 > > ip router isis > > ip pim sparse-dense-mode > > frame-relay interface-dlci 102 > > clns router isis > > isis circuit-type level-1 > > end > > > > R6#ping 1.1.1.1 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: > > !!!!! > > Success rate is 100 percent (5/5), round-trip min/avg/max = > > 32/32/36 ms > > R6# > > > > > > Now change the dlci # on R6: > > > > R6#ri s0.1 > > Building configuration... > > > > Current configuration : 200 bytes > > ! > > interface Serial0.1 point-to-point > > ip address 1.1.1.2 255.255.255.0 > > ip router isis > > ip pim sparse-dense-mode > > frame-relay interface-dlci 201 > > clns router isis > > isis circuit-type level-1 > > end > > > > R6#ping 1.1.1.1 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: > > ..... > > Success rate is 0 percent (0/5) > > R6# > > > > > > Can any one explain?? > > Thank you. > > Sincerely, > > CN > > > > > > > > > > > > > > _________________________________________________________________ > > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > > http://join.msn.com/?page=features/junkmail Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65595&t=65595 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
