From: G. R. Correia (razzolini80@hotmail.com)
Date: Fri Mar 28 2003 - 12:03:48 GMT-3
I believe this is a problem; your provider most likely is not using one
frame-relay switch only, then it is ok to have the same dlci; but not the
same dlci # on one FR switch...
HTH
>From: "Justin M. Ramsey" >Reply-To: "Justin M. Ramsey" >To: "Larry
Letterman" , >Subject: RE: Frame-relay / IP assistance >Date: Fri, 28 Mar
2003 07:30:45 -0600 > >Yeah, I knew that would be confusing. The reason
it is set up this way >is because I'm mimicking the real world
environment at work. On it, the >provider has given each remote router
the dlci 16, because it goes >through many service area's. The DLCI's
shouldn't be a problem to my >knowledge just a bit confusing, but here is
the show frame-relay map the >2 routers: > >R1: > >sh frame-relay map
>Serial0.18 (up): point-to-point dlci, dlci 18(0x12,0x420), broadcast >
status defined, active >Serial0.17 (up): point-to-point dlci, dlci
17(0x11,0x410), broadcast > status defined, active >Serial0.16 (up):
point-to-point dlci, dlci 16(0x10,0x400), broadcast > status defined,
active > >R2: >Serial0.17 (up): point-to-point dlci, dlci 16(0x10,0x400),
broadcast > status defined, active > > >When debugging ip packets, it
show's encapsulation failed, but from what >I see there is no
encapsulation mismatch in my configs. > > > > -----Original Message-----
>From: Larry Letterman [mailto:lletterm@cisco.com] >Sent: Friday, March
28, 2003 2:50 AM >To: Justin M. Ramsey; ccielab@groupstudy.com >Subject:
Re: Frame-relay / IP assistance > >your frame switching is kind of
confusing..your using the same dlci >number for >two routers...I suppose
it may work, but I used >different dlci's for my routers in the frame
switch... > >do a 'sh frame-relay map' and see what is mapped to the
dlci's.. > >Larry Letterman >Network Engineer >Cisco Systems > > > -----
Original Message ----- > From: Justin M. Ramsey > To:
ccielab@groupstudy.com > Sent: Thursday, March 27, 2003 7:06 PM >
Subject: Frame-relay / IP assistance > > > I am having a problem with my
Frame-relay set up and I think Ibm just > missing some little thing that
I continually overlook, hope you guys >can > help me. I have a lab set up
with a frame-relay switch going to 4 > routers, I will only deal with 2
to keep this as short as possible. I > can not ping any interfaces in
this lab, but I can show cdp neighbors > and see all the neighbors, show
cdp neighbors detail and see their IP > addresses and my show frame-relay
pvc looks good toob&here is the >output > of R1bs show frame-relay PVC:
> > PVC Statistics for interface Serial0 (Frame Relay DTE) > > Active
Inactive Deleted Static > Local 3 0 0 0 > Switched 0 0 0 0 > Unused 0 0 0
0 > > DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = >
Serial0.16 > > input pkts 370 output pkts 9501 in bytes > 88438 > out
bytes 585778 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
9501 out bcast bytes 585778 > pvc create time 05:15:11, last time pvc
status changed > 04:53:45 > > DLCI = 17, DLCI USAGE = LOCAL, PVC STATUS =
ACTIVE, INTERFACE = > Serial0.17 > > input pkts 309 output pkts 9199 in
bytes > 87078 > out bytes 491882 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 9199 out bcast bytes 491882 > pvc create time
05:13:36, last time pvc status changed > 04:54:33 > > DLCI = 18, DLCI
USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = > Serial0.18 > > input
pkts 292 output pkts 9237 in bytes > 80306 > out bytes 566181 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 9237 out bcast bytes
566181 > pvc create time 05:13:55, last time pvc status changed >
04:47:57 > > Here is the show cdp neighbors detail command on that same >
router for the R3 router: > > Device ID: R3 > Entry address(es): > IP
address: 10.10.16.2 > Platform: cisco 2500, Capabilities: Router >
Interface: Serial0.16, Port ID (outgoing port): Serial0.16 > Holdtime :
146 sec > > Version : > Cisco Internetwork Operating System Software >
IOS (tm) 2500 Software (C2500-INS-L), Version 12.0(22), RELEASE >
SOFTWARE (fc1) > Copyright (c) 1986-2002 by cisco Systems, Inc. >
Compiled Tue 02-Apr-02 00:40 by srani > > advertisement version: 1 > >
This is the debug ip packet output when pinging from R1: > > Type escape
sequence to abort. > Sending 5, 100-byte ICMP Echos to 10.10.16.2,
timeout is 2 > seconds: > > 1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2
(Serial0.16), len > 100, sending. > 1w2d: IP: s=10.10.16.1 (local),
d=10.10.16.2 (Serial0.16), len > 100, encapsulatio > n failed > 1w2d: IP:
s=10.10.16.1 (local), d=10.10.16.2 (Serial0.16), len > 100, sending. >
1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2 (Serial0.16), len > 100,
encapsulatio > n failed > 1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2
(Serial0.16), len > 100, sending. > 1w2d: IP: s=10.10.16.1 (local),
d=10.10.16.2 (Serial0.16), len > 100, encapsulatio > n failed > 1w2d: IP:
s=10.10.16.1 (local), d=10.10.16.2 (Serial0.16), len > 100, sending. >
1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2 (Serial0.16), len > 100,
encapsulatio > n failed > 1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2
(Serial0.16), len > 100, sending. > Success rate is 0 percent (0/5) > R1#
> 1w2d: IP: s=10.10.16.1 (local), d=10.10.16.2 (Serial0.16), len > 100,
encapsulatio > n failed > > This is the debug frame-relay packet output
when pinging from > R1: > > gramsize 45 > 1w2d: Serial0(i): dlci
17(0x411), pkt encaps 0x0300 0x8000 > 0x0000 0x2000(CDP), d > atagramsize
292 > 1w2d: Serial0.16: broadcast search > 1w2d: Serial0.16(o): dlci
16(0x401), pkt type 0x300, > datagramsize 44 > 1w2d: bridged dest
ffff.ffff.ffff, src 0000.0c3f.2be8, > type 806 > 1w2d: Serial0.16:
broadcast search > 1w2d: Serial0.16(o): dlci 16(0x401), pkt type 0x300, >
datagramsize 52 > 1w2d: bridged dest ffff.ffff.ffff, src 0000.0c3f.2be8,
> type 806 > 1w2d: Serial0.17: broadcast search > 1w2d: Serial0.17(o):
dlci 17(0x411), pkt type 0x300, > datagramsize 44 > 1w2d: bridged dest
ffff.ffff.ffff, src 0000.0c3f.2be8, > type 806 > 1w2d: Serial0.17:
broadcast search > 1w2d: Serial0.17(o): dlci 17(0x411), pkt type 0x300, >
datagramsize 52 > 1w2d: bridged dest ffff.ffff.ffff, src 0000.0c3f.2be8,
> type 806 > 1w2d: Serial0.18: broadcast search > 1w2d: Serial0.18(o):
dlci 18(0x421), pkt type 0x300, > datagramsize 44 > 1w2d: bridged dest
ffff.ffff.ffff, src 0000.0c3f.2be8, > type 806 > 1w2d: Serial0.18:
broadcast search > 1w2d: Serial0.18(o): dlci 18(0x421), pkt type 0x300, >
datagramsize 52 > 1w2d: bridged dest ffff.ffff.ffff, src 0000.0c3f.2be8,
> type 806 > w2d: Serial0.18: broadcast search > 1w2d: Serial0.18(o):
dlci 18(0x421), pkt encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING),
datagramsize 45 > 1w2d: broadcast dequeue > 1w2d: Serial0.16(o):Pkt sent
on dlci 16(0x401), pkt encaps 0x300 > 0x8000 0x80C2 > 0xE
(IEEE_SPANNING), datagramsize 45 > 1w2d: broadcast dequeue > 1w2d:
Serial0.17(o):Pkt sent on dlci 17(0x411), pkt encaps 0x300 > 0x8000
0x80C2 > 0xE (IEEE_SPANNING), datagramsize 45 > 1w2d: broadcast dequeue >
1w2d: Serial0.18(o):Pkt sent on dlci 18(0x421), pkt encaps 0x300 > 0x8000
0x80C2 > 0xE (IEEE_SPANNING), datagramsize 45 > 1w2d: Serial0.17:
Broadcast on DLCI 17 link 65(CDP) > 1w2d: Serial0.17(o): dlci 17(0x411),
pkt encaps 0x0300 0x8000 > 0x0000 0x2000(CDP) > , datagramsize 306 >
1w2d: broadcast dequeue > 1w2d: Serial0.17(o):Pkt sent on dlci 17(0x411),
pkt encaps 0x300 > 0x8000 0x0 > 0x2000(CDP), datagramsize 306 > 1w2d:
Serial0.16: broadcast search > 1w2d: Serial0.16(o): dlci 16(0x401), pkt
encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45 >
1w2d: Serial0.17: broadcast search > 1w2d: Serial0.17(o): dlci 17(0x411),
pkt encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45
> 1w2d: Serial0.18: broadcast search > 1w2d: Serial0.18(o): dlci
18(0x421), pkt encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING),
datagramsize 45 > 1w2d: broadcast dequeue > 1w2d: Serial0.16(o):Pkt sent
on dlci 16(0x401), pkt encaps 0x300 > 0x8000 0x80C2 > 0xE
(IEEE_SPANNING), datagramsize 45 > 1w2d: broadcast dequeue > 1w2d:
Serial0.17(o):Pkt sent on dlci 17(0x411), pkt encaps 0x300 > 0x8000
0x80C2 > 0xE (IEEE_SPANNING), datagramsize 45 > 1w2d: broadcast dequeue >
1w2d: Serial0.18(o):Pkt sent on dlci 18(0x421), pkt encaps 0x300 > 0x8000
0x80C2 > 0xE (IEEE_SPANNING), datagramsize 45 > 1w2d: Serial0.16:
broadcast search > 1w2d: Serial0.16(o): dlci 16(0x401), pkt encaps 0x0300
0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45 > 1w2d:
Serial0.17: broadcast search > 1w2d: Serial0.17(o): dlci 17(0x411), pkt
encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45 >
1w2d: Serial0.18: broadcast search > 1w2d: Serial0.18(o): dlci 18(0x421),
pkt encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45
> 1w2d: broadcast dequeue > 1w2d: Serial0.16(o):Pkt sent on dlci
16(0x401), pkt encaps 0x300 > 0x8000 0x80C2 > 0xE (IEEE_SPANNING),
datagramsize 45 > 1w2d: broadcast dequeue > 1w2d: Serial0.17(o):Pkt sent
on dlci 17(0x411), pkt encaps 0x300 > 0x8000 0x80C2 > 0xE
(IEEE_SPANNING), datagramsize 45 > 1w2d: broadcast dequeue > 1w2d:
Serial0.18(o):Pkt sent on dlci 18(0x421), pkt encaps 0x300 > 0x8000
0x80C2 > 0xE (IEEE_SPANNING), datagramsize 45 > 1w2d: Serial0.16:
broadcast search > 1w2d: Serial0.16(o): dlci 16(0x401), pkt encaps 0x0300
0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45 > 1w2d:
Serial0.17: broadcast search > 1w2d: Serial0.17(o): dlci 17(0x411), pkt
encaps 0x0300 0x8000 > 0x80C2 0xE (IEEE > _SPANNING), datagramsize 45 >
1w2d: Serial0.18: broadcast search > 1w2d: Serial0.18(o): dlci 18(0x421),
pkt encaps 0x0300 0x > > And here are the configs for R1, R3, and
R7(Frame-relay switch) > > R1: > interface Serial0 > no ip address >
encapsulation frame-relay IETF > no frame-relay inverse-arp > frame-relay
lmi-type ansi > ! > interface Serial0.16 point-to-point > ip address
10.10.16.1 255.255.255.0 > frame-relay interface-dlci 16 > bridge-group 1
> > > R3: > interface Serial0 > bandwidth 64 > no ip address > ip
directed-broadcast > encapsulation frame-relay IETF > logging event
subif-link-status > logging event dlci-status-change > no frame-relay
inverse-arp > frame-relay lmi-type ansi > ! > interface Serial0.16
point-to-point > bandwidth 56 > ip address 10.10.16.2 255.255.255.0 > no
ip directed-broadcast > frame-relay interface-dlci 16 > > R7: > interface
Serial0 > (This goes to R1) > no ip address > no ip directed-broadcast >
encapsulation frame-relay IETF > no ip route-cache > no ip mroute-cache >
logging event subif-link-status > logging event dlci-status-change >
clockrate 64000 > frame-relay lmi-type ansi > frame-relay intf-type dce >
frame-relay route 16 interface Serial2 16 > frame-relay route 17
interface Serial1 16 > frame-relay route 18 interface Serial3 16 >
interface Serial2 > (This goes to R3) > no ip address > no ip
directed-broadcast > encapsulation frame-relay IETF > logging event
subif-link-status > logging event dlci-status-change > clockrate 64000 >
frame-relay lmi-type ansi > frame-relay intf-type dce > frame-relay route
16 interface Serial0 16 > > Any help would be appreciated. > > Thanks, >
> Justin Ramsey
------------------------------------------------------------------------
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:46 GMT-3