Too bad nobody else is participating in this interesting thread. I changed the title. Mabye that will help! ;-)
Your question boils down to: "Does it matter that RTS is down on a serial interface acting as DCE on a router acting as a Frame Relay switch? The interface is connected to the DCE side of a cross-over cable." Your testing reveals that it doesn't matter. The interface is up/up and passing traffic. So you're wondering if RTS really matters. There's a good chance it doesn't matter in this situation. Consider what it stands for: Request to Send. On a full-duplex point-to-point serial interface, the DTE shouldn't have to send RTS before the DCE side asserts Clear to Send (CTS) and accepts incoming data. That stuff was used on old RS-232 multidrop lines, as far as I know. On a multidrop line, it's important that only one station send at a time. So that station has to assert RTS. The DCE side then asserts CTS. When the DTE sees Clear To Send (CTS) it knows it can send. See here for more info on RS-232 and V.35 specifications: http://www.sangoma.com/signal.htm Just out of curiousity, does it work even if that router with the problem is the DTE side? Turn the cross-over cable the other way so that DTE is on the Frame Relay switch side. (That will still work by the way. The side that is doing FR DCE doesn't have to be the 'physical-layer' DCE.) On the new DCE router, specify the clocking. Does the interface still come up/up? If not, then you would have a problem in the "real world." In the lab, though, there's no problem. You can just make sure that you connect the DCE side to the interface that seems to have a problem with this signal. Priscilla He Shuchen wrote: > > Thank you again. Here is the detail information about RTS=down > > I have 5 routers, and configured the 2520 as Frame Relay > Switch. Four 2501 routers connected to it. All other three > serial interfaces's singal of 2520 are DCD=up DSR=up DTR=up > RTS=up CTS=up, only serial 1's interface status is DCD=up > DSR=up DTR=up RTS=down CTS=up. and I have changed cable and > routers to the s1, The RTS still down. But it did and do work > well. So I want to know "Is RTS meaningless"? > > The configuration and show output of 2520's serial 1 > > R7#sh ru in s1 > Building configuration... > > Current configuration: > ! > interface Serial1 > no ip address > no ip directed-broadcast > encapsulation frame-relay > clockrate 125000 > frame-relay lmi-type ansi > frame-relay intf-type dce > frame-relay route 501 interface Serial0 105 > end > > R7# > Serial1 is up, line protocol is up > Hardware is HD64570 > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, > load 1/255 > Encapsulation FRAME-RELAY, loopback not set, keepalive set > (10 sec) > LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0 > LMI enq recvd 105, LMI stat sent 105, LMI upd sent 0, DCE > LMI up > LMI DLCI 0 LMI type is ANSI Annex D frame relay DCE > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface > broadcasts 0 > Last input 00:00:01, output 00:00:01, output hang never > Last clearing of "show interface" counters 00:17:24 > Input queue: 0/75/0 (size/max/drops); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/1/256 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 148 packets input, 4350 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 > abort > 168 packets output, 5832 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > DCD=up DSR=up DTR=up RTS=down CTS=up > R7# > > R7# sh fr pvc > > PVC Statistics for interface Serial0 (Frame Relay DCE) > > DLCI = 102, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial0 > > input pkts 41 output pkts 211 in bytes > 2624 > out bytes 79455 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 41 > > pvc create time 00:51:45, last time pvc status changed > 00:51:35 > > DLCI = 103, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial0 > > input pkts 133 output pkts 102 in bytes > 10216 > out bytes 7776 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 133 > > pvc create time 00:51:48, last time pvc status changed > 00:38:08 > > DLCI = 105, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial0 > > input pkts 135 output pkts 321 in bytes > 9172 > out bytes 31736 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 135 > > pvc create time 00:51:49, last time pvc status changed > 00:51:40 > > PVC Statistics for interface Serial1 (Frame Relay DCE) > > DLCI = 501, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial1 > > input pkts 322 output pkts 135 in bytes > 31848 > out bytes 9172 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 322 > pvc create time 00:51:50, last time pvc status changed > 00:51:40 > ====>you can see that serial 1 is working, because it switched > 322 packets > PVC Statistics for interface Serial2 (Frame Relay DCE) > > DLCI = 201, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial2 > > input pkts 212 output pkts 42 in bytes > 79519 > out bytes 2688 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 212 > > pvc create time 00:51:55, last time pvc status changed > 00:51:46 > > PVC Statistics for interface Serial3 (Frame Relay DCE) > > DLCI = 301, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, > INTERFACE = Serial3 > > input pkts 103 output pkts 134 in bytes > 7848 > out bytes 10280 dropped pkts 0 in FECN > pkts 0 > in BECN pkts 0 out FECN pkts 0 out BECN > pkts 0 > in DE pkts 0 out DE pkts 0 > out bcast pkts 0 out bcast bytes 0 Num > Pkts Switched 103 > > pvc create time 00:51:59, last time pvc status changed > 00:38:25 > R7# > > The configuration and show results of 2501's s0: > R5#sh ru > Building configuration... > > Current configuration: > ! > version 12.0 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > service udp-small-servers > service tcp-small-servers > ! > hostname R5 > ! > > ! > ip subnet-zero > no ip domain-lookup > ! > ! > ! > interface Ethernet0 > ip address 11.1.1.1 255.255.0.0 > no ip directed-broadcast > no ip route-cache > no ip mroute-cache > ! > interface Serial0 > ip address 10.10.1.5 255.255.0.0 > no ip directed-broadcast > encapsulation frame-relay > no ip route-cache > ip ospf network point-to-multipoint > no ip mroute-cache > frame-relay lmi-type ansi > ! > interface Serial1 > no ip address > no ip directed-broadcast > no ip route-cache > no ip mroute-cache > shutdown > clockrate 64000 > ! > router ospf 1 > network 10.10.1.5 0.0.0.0 area 0 > network 11.1.1.1 0.0.0.0 area 0 > ! > router bgp 2 > no synchronization > neighbor 10.10.1.1 remote-as 2 > ! > ip classless > ! > alias exec i sh ip route > ! > line con 0 > transport input none > line aux 0 > transport input all > line vty 0 4 > no login > ! > end > > R5# > > R5#sh in s 0 > Serial0 is up, line protocol is up > Hardware is HD64570 > Internet address is 10.10.1.5/16 > MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, > load 1/255 > Encapsulation FRAME-RELAY, loopback not set, keepalive set > (10 sec) > LMI enq sent 332, LMI stat recvd 329, LMI upd recvd 0, DTE > LMI up > LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0 > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > Broadcast queue 0/64, broadcasts sent/dropped 111/0, > interface broadcasts 110 > Last input 00:00:00, output 00:00:00, output hang never > Last clearing of "show interface" counters never > Input queue: 0/75/0 (size/max/drops); Total output drops: 0 > Queueing strategy: weighted fair > Output queue: 0/1000/64/0 (size/max total/threshold/drops) > Conversations 0/1/256 (active/max active/max total) > Reserved Conversations 0/0 (allocated/max allocated) > 5 minute input rate 1000 bits/sec, 1 packets/sec > 5 minute output rate 1000 bits/sec, 1 packets/sec > 569 packets input, 20613 bytes, 0 no buffer > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 > abort > 795 packets output, 48006 bytes, 0 underruns > 0 output errors, 0 collisions, 2 interface resets > 0 output buffer failures, 0 output buffers swapped out > 6 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > ===============> all signals are up (strange) > R5#sh fr map > Serial0 (up): ip 10.10.1.1 dlci 501(0x1F5,0x7C50), dynamic, > broadcast,, status defined, active > R5#sh ip os ne > > Neighbor ID Pri State Dead Time > Address Interface > 10.20.1.1 1 FULL/ - 00:01:37 > 10.10.1.1 Serial0 > =======>> OSPF is working > R5# > > > > ----- Original Message ----- > From: "Priscilla Oppenheimer" > To: > Sent: Saturday, August 10, 2002 3:20 AM > Subject: Re: Stange thing [7:50911] > > > > He Shuchen wrote: > > > > > > Thank you Priscilla Oppenheimer and other people here. and > I am > > > sorry because English is not my native language. > > > > No problem. I think it's admirable that you can speak English > at all. > > > > At the bottom of the box where you type messages, if you are > using the Web > > interface, is a button that says Quote. If you click on that > button, then > > your message will include the message to which you are > responding. > > > > Most of us read these messages in a connectionless, stateless > fashion. We > > can't understand messages that don't have any history with > them. It's too > > much work to go back and look at previous messages. > > > > > It's a little > > > difficult to read a lot of information in the group. I will > > > notice previous messages before I ask question. > > > > Noticing isn't the problem. Use the Quote button please. > That's the point. > > Or if you do GroupStudy via e-mail, then configure your > e-mail application > > to include the message to which you are responding. Thanks. > > > > > I configured the 2520 router as Frame Relay switch and > > > connected it to a 2501 with a DTE to DCE v.35 Cross-over > cable. > > > It's my lab environment. The 2520 is DCE and 2501 is DTE. > The > > > 2520's RTS=down, but 2501's DCD=up DSR=up DTR=up RTS=up > > > CTS=up. It have up for several days. I think it's a hardware > > > problem with the 2520's serial problem. Other interfaces in > > > 2520 are ok. and I'm sure it's not a cable problem because I > > > have used another cable. > > > The IOS is c2500-i-l.121-7.bin. > > > > I think it may be a hardware problem too. It may be a problem > with the 2501, > > however. It should assert RTS since it's the DTE side. By > doing more > > testing, you can determine if the problem resides with the > DTE side not > > asserting RTS or the DCE side not recognizing that RTS has > been asserted. > > > > But for now it works, so that's good! Please keep us informed > if it > > continues to work. It's an interesting question. Thanks for > bringing it to > > our attention. > > > > I'm sorry if my English is too complicated or for any errors. > I don't spell > > check anymore now that I use the Web interface. :-) > > > > Priscilla > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=51273&t=50911 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
