From: Qingli Gao (qgao@frycomm.com)
Date: Thu Nov 03 2005 - 14:41:37 GMT-3
Yes, I did.
I tried S1, same thing happened.
What I am wondering is without keepalive,
Is this considered a good connection since the protocol is up now?
Here is the show int s0 on that 2501 after disable keepalive
Serial0 is up, line protocol is up
Hardware is HD64570
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, loopback not set
Keepalive not set
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
Last input never, output 01:45:28, output hang never
Last clearing of "show interface" counters 02:09:33
Input queue: 0/75/0/0 (size/max/drops/flushes); 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
0 packets input, 0 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
218 packets output, 2859 bytes, 0 underruns
0 output errors, 0 collisions, 47 interface resets
0 output buffer failures, 0 output buffers swapped out
80 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
----- Original Message -----
From: "Cisco CCIE" <onlyccie@gmail.com>
To: "Qingli Gao" <qgao@frycomm.com>
Cc: "Adel Abouchaev" <adel@netmasterclass.net>; <ccielab@groupstudy.com>
Sent: Thursday, November 03, 2005 12:25 PM
Subject: Re: weird Frame-relay switch problem
> Hi,
>
> As you have menctioned that you are using a 2501, why dont you change the
> interface from s0 to s1 and check if the line protocol is up with the same
> configuration ?
>
> This will eliminate problems associated with 2501's serial 0 interface
> (hardware failure).
>
> ~Only CCIE.
>
> On 11/3/05, Qingli Gao <qgao@frycomm.com> wrote:
>>
>> LMI type: Cisco
>> keepalive 10s on both side before I disable it
>>
>> this is exactly the same as other 7 serial.
>> but only this 2501 need turn of keep alive.
>>
>> ----- Original Message -----
>> From: "Adel Abouchaev" <adel@netmasterclass.net>
>> To: "Kim Gao" <gaoqingli@gmail.com>; <ccielab@groupstudy.com>
>> Sent: Thursday, November 03, 2005 11:52 AM
>> Subject: Re: weird Frame-relay switch problem
>>
>>
>> > What is LMI on both ends?
>> >
>> > Adel.
>> >
>> > ----- Original Message -----
>> > From: "Kim Gao" <gaoqingli@gmail.com>
>> > To: <ccielab@groupstudy.com>
>> > Sent: Thursday, November 03, 2005 8:25 AM
>> > Subject: weird Frame-relay switch problem
>> >
>> >
>> >>I setup a lab at home using a bunch of routers
>> >>
>> >> 4500 8S as a frame-relay switch
>> >> s0---s7 connect to different routers's S0 using cross DTE/DCE cable
>> >>
>> >> On all the serial of 4500, it looks like this:
>> >> interface Serial1
>> >> no ip address
>> >> no ip directed-broadcast
>> >> encapsulation frame-relay
>> >> clockrate 64000
>> >> frame-relay intf-type dce
>> >> frame-relay route 102 interface Serial2 201
>> >> frame-relay route 103 interface Serial3 301
>> >> frame-relay route 104 interface Serial4 401
>> >> frame-relay route 105 interface Serial5 501
>> >> frame-relay route 106 interface Serial6 601
>> >> frame-relay route 107 interface Serial7 701
>> >> frame-relay route 108 interface Serial0 801
>> >>
>> >> On all the DTE routers's s0:
>> >>
>> >> interface Serial0
>> >> no ip address
>> >> encapsulation frame-relay
>> >> no ip mroute-cache
>> >> no frame-relay inverse-arp
>> >>
>> >> All the connection are up except one 2501, the
>> >> protocol is down.
>> >> I tried to add no keepalive on that 2501 's S0 and the
>> >> corresponding Serial on 4500,
>> >> then protocol turns up.
>> >>
>> >> BUT I do not need to do that on any other serials.
>> >> Can anyone guess a reason?
>> >>
>> >> Thanks a lot!
>> >>
>> >> _______________________________________________________________________
>> >> Subscription information may be found at:
>> >> http://www.groupstudy.com/list/CCIELab.html
>> >
>> > _______________________________________________________________________
>> > Subscription information may be found at:
>> > http://www.groupstudy.com/list/CCIELab.html
>> >
>>
>> This email message and any files transmitted with it contain information
>> which is confidential and intended only for the addressee(s). If you are
>> not the intended recipient(s), any usage, dissemination, disclosure, or
>> action taken in reliance on it is prohibited. The reliability of this
>> method of communication cannot be guaranteed. Email can be intercepted,
>> corrupted, delayed, incompletely transmitted, virus-laden, or otherwise
>> affected during transmission. Reasonable steps have been taken to reduce
>> the risk of viruses, but we cannot accept liability for damage sustained
>> as a result of this message. If you have received this message in error,
>> please immediately delete it and all copies of it and notify the sender.
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This email message and any files transmitted with it contain information
which is confidential and intended only for the addressee(s). If you are
not the intended recipient(s), any usage, dissemination, disclosure, or
action taken in reliance on it is prohibited. The reliability of this
method of communication cannot be guaranteed. Email can be intercepted,
corrupted, delayed, incompletely transmitted, virus-laden, or otherwise
affected during transmission. Reasonable steps have been taken to reduce
the risk of viruses, but we cannot accept liability for damage sustained
as a result of this message. If you have received this message in error,
please immediately delete it and all copies of it and notify the sender.
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:05 GMT-3