«

Hi Everyone,

I'm sure someone can shed some light on the this, it's doing my head
in! I've been at it for 7 hours and I'm sure there must be some decent
explaination.

I'm setting up Frame Relay Home Lab as per Chris Bryant, here is the
switch config:

http://www.thebryantadvantage.com/Fr...y%20Switch.htm

All is well apart from R2, where I have configured a multipoint
sub-interface 1.123

Sometimes I see (looped) when doing a show int and on the 2610 that
I've configured as a Frame Relay switch, I see this, it's continously
up and down.


FRAME_SWITCH# sh i
08:27:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/2,
changed sta te to down FRAME_SWITCH# sh i
08:27:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/2,
changed sta te to up FRAME_SWITCH# sh i
08:27:56: %FR-5-DLCICHANGE: Interface Serial1/2 - DLCI 221 state
changed to ACTI VE FRAME_SWITCH# sh i
08:28:06: %FR-5-DLCICHANGE: Interface Serial1/2 - DLCI 221 state
changed to INAC TIVE FRAME_SWITCH# sh i
08:28:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/2,
changed sta te to down FRAME_SWITCH# sh i
08:28:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/2,
changed sta te to up


I have switched cables, also gone from S0 to S1 but no joy.

Would really appreciate any input to help.

Thanks a million.









Show run: R2

interface Serial1.123 multipoint
no ip route-cache
frame-relay map ip 192.168.1.100 221 broadcast
frame-relay map ip 192.168.3.100 221 broadcast


Show int: R2

Serial1 is up, line protocol is down (size/max), txload 1/255, rxload
1/
Hardware is HD64570t rate 0 bits/sec, 0
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,anged stat
5 minute output rate 0 bits/sec, 0
reliability 255/255, txload 1/255, rxload 1/255OS acce
Last clearing of "show interface" counters 00:48:11
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)
Available Bandwidth 1158 kilobits/sec
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
498 packets input, 6570 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
10 input errors, 10 CRC, 1 frame, 0 overrun, 0 ignored, 0 abort
351 packets output, 4608 bytes, 0 underruns
0 output errors, 0 collisions, 87 interface resets
0 output buffer failures, 0 output buffers swapped out
78 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Serial1.123 is down, line protocol is down
Hardware is HD64570
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY

and yes, I know I made a typo!

> Show run: R2
>
> interface Serial1.123 multipoint
> no ip route-cache
> frame-relay map ip 192.168.1.100 221 broadcast
> frame-relay map ip 192.168.3.100 221 broadcast

Try

interface Serial1.123 multipoint
no ip route-cache
frame-relay map ip 192.168.1.100 221 broadcast
frame-relay map ip 192.168.3.100 321 broadcast

Note that the secind map statement maps DLCI 321 to 192.168.3.100 321.

Cisco da Gama
http://ciscostudy.blogspot.com

Chris Bryanat who wrote the papers says this:

"notice that even that I'm going to 2 different IP addresses I use the
same DLCI, that's because, for data to get to router 3 (3.100) it has
to go through router 1 (2.100) in the first place, it's a spoke to
spoke communication"

The topology is HUB/SPOKE - 1.100 & 2.100/3.100







On 7 Apr 2006 12:41:29 -0700, ""
<> wrote:

>> Show run: R2
>>
>> interface Serial1.123 multipoint
>> no ip route-cache
>> frame-relay map ip 192.168.1.100 221 broadcast
>> frame-relay map ip 192.168.3.100 221 broadcast
>
>Try
>
> interface Serial1.123 multipoint
> no ip route-cache
> frame-relay map ip 192.168.1.100 221 broadcast
> frame-relay map ip 192.168.3.100 321 broadcast
>
>Note that the secind map statement maps DLCI 321 to 192.168.3.100 321.
>
>Cisco da Gama
>http://ciscostudy.blogspot.com

wrote:
> Chris Bryanat who wrote the papers says this:
>
> "notice that even that I'm going to 2 different IP addresses I use the
> same DLCI, that's because, for data to get to router 3 (3.100) it has
> to go through router 1 (2.100) in the first place, it's a spoke to
> spoke communication"
>
> The topology is HUB/SPOKE - 1.100 & 2.100/3.100

In the link that you provided in your first post, the FR switch
configuration does not seem to support this spoke to spoke
communication that you are referring to. The part you quote probably
refers to a different set-up where the FR switch is also configured to
allow the spoke to spoke communication.

I would suggest that you first get the simple huband spoke
configuration working and then work with variations of that config to
get the spoke to spoke working.

Cisco da Gama
http://ciscostudy.blogspot.com

Thanks Cisco da Gama,

One error I had was:

LMI DLCI 1023 LMI type is CISCO frame relay DTE

instead of:

frame intf-type dce

So now that's sorted but still having some issues, trying to get my
'mentor' to telnet in and see what the deal is.

Thanks for your help,

Melon