Frame Relay Problem

2000-11-26 Thread James Wilson

Hi All,

I hope someone can shed some light on the problem I have come across in the 
following scenario :

Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a 
router in the middle doing frame relay switching. The frame switch is _not_ 
fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1. 
Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There is 
_no_ PVC between R2 and R3.

The particular lab exercise here specifies that each router much be able to 
ping every other router in the frame cloud. BUT the use of the 'frame-relay 
map' command is forbidden, and only R1 can be configured using a subinterface.

As I have it configured R1 can ping both R2 and R3 as expected. However, 
both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The 
question stipulates you should use routing and not Layer2 to Layer3 
mapping. A debug on the ping from R2 to R3 shows that there is no map entry 
for R3 hence encapsulation failed. A look at 'sh frame map' shows there is 
only 1 entry and it is for R1. This sh frame map is identical on R2 and R3.

So the question is, how can I get R2 and R3 to be able to ping each other 
using routing and not the frame relay map command.

It's got two of us here studying for our CCIE stumped, so im hoping someone 
out there has an idea as to how this can be accomplished.

Also, as this is for the CCIE, static routes are not an option.

Cheers.

Jim.

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame Relay problem

2000-11-30 Thread Jim Healis

Your telco provisioned the PVC on the same circuit as DLCI 17, this is
evident by the show frame-relay pvc command.  You have it configured on
Serial 0, which is why it shows up, down.  But it is actually on Serial 1.

Try configuring the sub-interface on Serial 1, and I bet it comes up and
starts running.

-j

Subject:
 Frame Relay - Real Life Problem
Date:
 30 Nov 2000 00:16:34 -0500
   From:
 [EMAIL PROTECTED] (Adele Galus)
 Organization:
 GroupStudy.com Discussion Groups
 Newsgroups:
 groupstudy.cisco




This is a configuration problem.

Situation:  I have two ISP's involved.  The router is a 2500 series.
Internal CSU/DSU.
On DLCI 17 ISP traffic routes.  The other DLCI 16 doesn't.  Information
is correct -
I must be missing something.




Cormick#show frame-relay map
Serial0.16 (down): point-to-point dlci, dlci 16(0x10,0x400), broadcast
  status deleted
Serial1.1 (up): point-to-point dlci, dlci 17(0x11,0x410), broadcast,
IETF
  status defined, active




Cormick#show frame-relay pvc

PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE =
Serial0.16

  input pkts 0 output pkts 4in bytes 0
  out bytes 1794   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 4  out bcast bytes 1794
  pvc create time 9w3d, last time pvc status changed 7w4d

PVC Statistics for interface Serial1 (Frame Relay DTE)

DLCI = 16, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE =
Serial1

  input pkts 0 output pkts 0in bytes 0
  out bytes 0  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 0Num Pkts
Switched 0
  pvc create time 9w3d, last time pvc status changed 7w4d

DLCI = 17, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial1.1

  input pkts 73176244  output pkts 63755322 in bytes 2986909822
  out bytes 4214766293 dropped pkts 239 in FECN pkts 273970
  in BECN pkts 254655  out FECN pkts 0  out BECN pkts 0
  in DE pkts 940978out DE pkts 0
  out bcast pkts 96267  out bcast bytes 27724896
  pvc create time 9w3d, last time pvc status changed 7w4d




Cormick#show interfaces
Ethernet0 is up, line protocol is up
  Hardware is Lance, address is 0010.7b3a.3a4e (bia 0010.7b3a.3a4e)
  Internet address is 63.200.119.158/28
  MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, rely 255/255, load 2/255

  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 3/75, 210 drops
  5 minute input rate 18000 bits/sec, 24 packets/sec
  5 minute output rate 113000 bits/sec, 24 packets/sec
 64042206 packets input, 881888058 bytes, 16 no buffer
 Received 365077 broadcasts, 0 runts, 0 giants, 210 throttles
 13798 input errors, 0 CRC, 0 frame, 0 overrun, 13798 ignored, 0
abort
 0 input packets with dribble condition detected
 73886303 packets output, 3838898715 bytes, 0 underruns
 0 output errors, 46341 collisions, 430 interface resets
 0 babbles, 0 late collision, 105851 deferred
 0 lost carrier, 0 no carrier
 0 output buffer failures, 0 output buffers swapped out
Serial0 is up, line protocol is down
  Hardware is HD64570 with FT1 CSU/DSU
  MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 255/255, load 1/255

  Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10
sec)
  LMI enq sent  578802, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  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 4/0, interface
broadcasts 2
  Last input never, output 00:00:04, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 5210 input errors, 52 CRC, 2 frame, 3 overrun, 320 ignored, 11
abort
 578805 packets output, 8105008 bytes, 0 underruns
 0 output errors, 0 collisions, 192612 interface resets
  

Frame Relay problem

2000-10-10 Thread Hans Stout

Hi colleagues,

I have a problem with my frame relay connection; the serial interface is 
up/down, and when I debug the serial interface, I can see that the interface 
is constantly trying to restart:23w5d:

Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down

What could be the reason for this ? I'll add the output for the sh int:


Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u

Thanks for your help in advance.

Georg

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame relay problem

2000-11-07 Thread David Welch

Hi, Could anyone help with the following : Part of our network consists of 
Cisco 4500 routers connected via BT frame relay links.
The problem I am seeing on all 10 routers is links going down then up, often 
for exactly one minute : eg

.Oct 24 16:25:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592 state 
cha
nged to INACTIVE
.Oct 24 16:25:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Serial2/0.
4, changed state to down
.Oct 24 16:26:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592 state 
cha
nged to ACTIVE
.Oct 24 16:26:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Serial2/0.
4, changed state to up

The PTT have tested all lines and insist they are clean
This is happening about 5 - 10 times a day. The IOS was upgraded not too 
long ago I think. It is now 12.0(4)
This doesn't seem to have much impact but my customer just wants to know 
why!
Any ideas/suggestions very welcome

TIA

Dave Welch
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



FRAME RELAY PROBLEM

2000-08-23 Thread Peter Gray

I have got a problem with FR Config Running OSPF. Router A & B are connected 
to C & D over FR PVC but they don't have to talk to each ther. It means A 
connected to C & D and B is also connected to C & D. I am using FR 
Subinterfaces with pt-to-pt. What is happening that sometime I am able to 
ping to  router C & router D subinterfaces from router A but sometimes i 
don't get any response. I am even unable to ping sub-intf of Routers from 
within the routers.
See sample config of one of the routers that i have:
interface Serial0
no ip address
ip directed-broadcast
encapsulation frame-relay
ip ospf network broadcast
no ip mroute-cache
!
interface Serial0.1 point-to-point
ip address 131.18.19.185 255.255.255.252
ip directed-broadcast
ip ospf network broadcast
frame-relay interface-dlci 310
!
interface Serial0.2 point-to-point
ip address 131.18.19.189 255.255.255.252
ip directed-broadcast
ip ospf network broadcast
frame-relay interface-dlci 210

This is config of router B connected to C & D and subintf of C &D are on 
same subnet as subintf 0.1 and 0.2 on this router.
Is pt-to-pt with sub-intf OK for this scenario?

Any suggestions... What is the possible cause of problem?? Why I am even 
unable to ping local subintface from within the router??

Thanks..
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

___
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame Relay Problem

2000-05-17 Thread Nathan Cruz




I've set up a frame relay switch at home trying to 
complete one of the "CCIE Lab all in one" Labs. For my question, what could 
cause a PVC to be inactive? Things I've checked. 
 
Serial is up line protocol is up on both sides. 

LMI type is the same
Clocking is set on DCE side. 
Encapsulation is Frame relay
 
What else is there to check? All suggestions 
appreciated.


Re: Frame Relay Problem

2000-11-26 Thread Rodgers Moore

If you could post the configs it would help, but here's some ideas to try.

Are you sure have inverse ARP working?
Have you tried a static route to R3 (from R2) gatewayed to R1's IP and the
same on R3 to R2 via R1's IP?
Look into Proxy ARP.
Just a thought, I've never tried this but, is there a way to make a static
ARP entry?

Rodgers Moore

"James Wilson" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi All,
>
> I hope someone can shed some light on the problem I have come across in
the
> following scenario :
>
> Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> router in the middle doing frame relay switching. The frame switch is
_not_
> fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
is
> _no_ PVC between R2 and R3.
>
> The particular lab exercise here specifies that each router much be able
to
> ping every other router in the frame cloud. BUT the use of the
'frame-relay
> map' command is forbidden, and only R1 can be configured using a
subinterface.
>
> As I have it configured R1 can ping both R2 and R3 as expected. However,
> both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> question stipulates you should use routing and not Layer2 to Layer3
> mapping. A debug on the ping from R2 to R3 shows that there is no map
entry
> for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> only 1 entry and it is for R1. This sh frame map is identical on R2 and
R3.
>
> So the question is, how can I get R2 and R3 to be able to ping each other
> using routing and not the frame relay map command.
>
> It's got two of us here studying for our CCIE stumped, so im hoping
someone
> out there has an idea as to how this can be accomplished.
>
> Also, as this is for the CCIE, static routes are not an option.
>
> Cheers.
>
> Jim.
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>


_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-26 Thread Frank B.

Unless I'm mis-reading you here this is the correct behavior for a
partial mesh.  Unless you provide a full mesh you won't get dynamic
mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
subnet and the PVC from R1 to R3 is another subnet--Frame relay and
Inverse ARP alone can't route between them.

So if you can't get a PVC between R2 and R3...then run any routing
protocol on all 3 routers and you should be able to ping from R2 to R3
and vice-versa (RIP will work fine to prove this point.)  Hope this
helps...and as always, comments are welcome ( and in fact expected
;-)Frank

James Wilson wrote:
> 
> Hi All,
> 
> I hope someone can shed some light on the problem I have come across in the
> following scenario :
> 
> Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> router in the middle doing frame relay switching. The frame switch is _not_
> fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There is
> _no_ PVC between R2 and R3.
> 
> The particular lab exercise here specifies that each router much be able to
> ping every other router in the frame cloud. BUT the use of the 'frame-relay
> map' command is forbidden, and only R1 can be configured using a subinterface.
> 
> As I have it configured R1 can ping both R2 and R3 as expected. However,
> both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> question stipulates you should use routing and not Layer2 to Layer3
> mapping. A debug on the ping from R2 to R3 shows that there is no map entry
> for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> only 1 entry and it is for R1. This sh frame map is identical on R2 and R3.
> 
> So the question is, how can I get R2 and R3 to be able to ping each other
> using routing and not the frame relay map command.
> 
> It's got two of us here studying for our CCIE stumped, so im hoping someone
> out there has an idea as to how this can be accomplished.
> 
> Also, as this is for the CCIE, static routes are not an option.
> 
> Cheers.
> 
> Jim.
> 
> _
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-26 Thread whatshakin

Sounds like all you need to get your branch traffic to the next hop (hub
router) where the hub router will route it for you because it knows of the
routes to all destinations.  You could use static routes or route maps with
the next-hop parameter to do this.

- Original Message -
From: James Wilson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, November 26, 2000 5:50 PM
Subject: Frame Relay Problem


> Hi All,
>
> I hope someone can shed some light on the problem I have come across in
the
> following scenario :
>
> Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> router in the middle doing frame relay switching. The frame switch is
_not_
> fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
is
> _no_ PVC between R2 and R3.
>
> The particular lab exercise here specifies that each router much be able
to
> ping every other router in the frame cloud. BUT the use of the
'frame-relay
> map' command is forbidden, and only R1 can be configured using a
subinterface.
>
> As I have it configured R1 can ping both R2 and R3 as expected. However,
> both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> question stipulates you should use routing and not Layer2 to Layer3
> mapping. A debug on the ping from R2 to R3 shows that there is no map
entry
> for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> only 1 entry and it is for R1. This sh frame map is identical on R2 and
R3.
>
> So the question is, how can I get R2 and R3 to be able to ping each other
> using routing and not the frame relay map command.
>
> It's got two of us here studying for our CCIE stumped, so im hoping
someone
> out there has an idea as to how this can be accomplished.
>
> Also, as this is for the CCIE, static routes are not an option.
>
> Cheers.
>
> Jim.
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-26 Thread James Wilson

Nope, all one subnet. i.e all interfaces are on the 10.1.X.X/16 subnet

Hence the problem.

Im well aware this is the normal partial mesh behavior and that its quiet 
easily rectified using map statements... but for this particular setup it 
requests the use of routing and not frame relay map statements.

At 06:26 PM 26/11/2000 -1000, Frank B. wrote:
>Unless I'm mis-reading you here this is the correct behavior for a
>partial mesh.  Unless you provide a full mesh you won't get dynamic
>mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
>subnet and the PVC from R1 to R3 is another subnet--Frame relay and
>Inverse ARP alone can't route between them.
>
>So if you can't get a PVC between R2 and R3...then run any routing
>protocol on all 3 routers and you should be able to ping from R2 to R3
>and vice-versa (RIP will work fine to prove this point.)  Hope this
>helps...and as always, comments are welcome ( and in fact expected
>;-)Frank
>
>James Wilson wrote:
> >
> > Hi All,
> >
> > I hope someone can shed some light on the problem I have come across in the
> > following scenario :
> >
> > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> > router in the middle doing frame relay switching. The frame switch is _not_
> > fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There is
> > _no_ PVC between R2 and R3.
> >
> > The particular lab exercise here specifies that each router much be able to
> > ping every other router in the frame cloud. BUT the use of the 'frame-relay
> > map' command is forbidden, and only R1 can be configured using a 
> subinterface.
> >
> > As I have it configured R1 can ping both R2 and R3 as expected. However,
> > both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> > question stipulates you should use routing and not Layer2 to Layer3
> > mapping. A debug on the ping from R2 to R3 shows that there is no map entry
> > for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> > only 1 entry and it is for R1. This sh frame map is identical on R2 and R3.
> >
> > So the question is, how can I get R2 and R3 to be able to ping each other
> > using routing and not the frame relay map command.
> >
> > It's got two of us here studying for our CCIE stumped, so im hoping someone
> > out there has an idea as to how this can be accomplished.
> >
> > Also, as this is for the CCIE, static routes are not an option.
> >
> > Cheers.
> >
> > Jim.
> >
> > _
> > FAQ, list archives, and subscription info: 
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-26 Thread James Wilson

Config :

R1

!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R1-Ob
!
!
!
!
hub ether 0 1
  link-test
  auto-polarity
!
hub ether 0 2
  link-test
  auto-polarity
!
hub ether 0 3
  link-test
  auto-polarity
!hub ether 0 4
  link-test
  auto-polarity
!
hub ether 0 5
  link-test
  auto-polarity
!
hub ether 0 6
  link-test
  auto-polarity
!
hub ether 0 7
  link-test
  auto-polarity
!
hub ether 0 8
  link-test
  auto-polarity
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  no ip address
  encapsulation frame-relay
  no ip mroute-cache
  clockrate 64000
!
interface Serial0.1 multipoint
  ip address 10.1.1.1 255.255.0.0
  frame-relay interface-dlci 101
  frame-relay interface-dlci 102
!
interface Serial1
  no ip address
  shutdown
!
router ospf 1
  network 10.1.0.0 0.0.255.255 area 0
  neighbor 10.1.1.3
  neighbor 10.1.1.2
  default-information originate always metric-type 1
!
ip classless
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R2

!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname R2-Sambuca
!
!
ip subnet-zero
!
hub ether 0 1
  link-test
  auto-polarity
!
hub ether 0 2
  link-test
  auto-polarity
!
hub ether 0 3
  link-test
  auto-polarity
!
hub ether 0 4
  link-test
  auto-polarity
!
hub ether 0 5
  link-test
  auto-polarity
!
hub ether 0 6
  link-test
  auto-polarity
!
hub ether 0 7
  link-test
  auto-polarity
!
hub ether 0 8
  link-test
  auto-polarity
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  ip address 10.1.1.2 255.255.0.0
  encapsulation frame-relay
  ip ospf priority 0
  no fair-queue
  frame-relay interface-dlci 100
!
interface Serial1
  no ip address
  shutdown
!
router ospf 1
  network 10.1.0.0 0.0.255.255 area 0
!
no ip classless
!
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R3

!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R3-Budvar
!
!
ip subnet-zero
ip cef
!
!
!
interface ATM1/0
  no ip address
  no ip directed-broadcast
  shutdown
  no atm ilmi-keepalive
!
interface ATM4/0
no ip address
  no ip directed-broadcast
  shutdown
  no atm ilmi-keepalive
!
interface Serial5/0
  ip address 10.1.1.3 255.255.0.0
  no ip directed-broadcast
  encapsulation frame-relay
  ip ospf interface-retry 0
  ip ospf priority 0
  no ip mroute-cache
  no fair-queue
  frame-relay interface-dlci 100
!
interface Serial5/1
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/2
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/3
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/4
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/5
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/6
  no ip address
  no ip directed-broadcast
  shutdown
!
interface Serial5/7
  no ip address
  no ip directed-broadcast
  shutdown
!
interface TokenRing6/0/0
  no ip address
  no ip directed-broadcast
  no ip route-cache distributed
  shutdown
!
interface TokenRing6/0/1
  no ip address
  no ip directed-broadcast
  no ip route-cache distributed
  shutdown
!
interface TokenRing6/0/2
  no ip address
  no ip directed-broadcast
  no ip route-cache distributed
  shutdown
!
interface TokenRing6/0/3
  no ip address
  no ip directed-broadcast
  no ip route-cache distributed
  shutdown
!
router ospf 1
  network 10.1.0.0 0.0.255.255 area 0
  distance 1
!
ip classless
!
!
!
line con 0
  transport input none
line aux 0
line vty 0 4
!
end



At 10:00 PM 26/11/2000 -0500, you wrote:
>If you could post the configs it would help, but here's some ideas to try.
>
>Are you sure have inverse ARP working?
>Have you tried a static route to R3 (from R2) gatewayed to R1's IP and the
>same on R3 to R2 via R1's IP?
>Look into Proxy ARP.
>Just a thought, I've never tried this but, is there a way to make a static
>ARP entry?
>
>Rodgers Moore
>
>"James Wilson" <[EMAIL PROTECTED]> wrote in message
>[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi All,
> >
> > I hope someone can shed some light on the problem I have come across in
>the
> > following scenario :
> >
> > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> > router in the middle doing frame relay switching. The frame switch is
>_not_
> > fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
>is
> > _no_ PVC between R2 and R3.
> >
> > The particular lab exercise here specifies that each router much be able
>to
> > ping every other router in the frame cloud. BUT the use of the
>'frame-relay
> > map' command is forbidden, and only R1 can be configured using a
>subinterface.
> >
> > As I have it configured R1 can ping both R2 and R3 as expected. However,
> > both R2 and R3 can only ping R1 (the hub) yet cannot 

RE: Frame Relay Problem

2000-11-26 Thread Aaron K. Dixon

You will need to either generate default routes for the spokes or use policy
routing to set the default next hop.

Regards,
Aaron K. Dixon

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Frank B.
Sent: Sunday, November 26, 2000 10:27 PM
To: James Wilson
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Frame Relay Problem


Unless I'm mis-reading you here this is the correct behavior for a
partial mesh.  Unless you provide a full mesh you won't get dynamic
mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
subnet and the PVC from R1 to R3 is another subnet--Frame relay and
Inverse ARP alone can't route between them.

So if you can't get a PVC between R2 and R3...then run any routing
protocol on all 3 routers and you should be able to ping from R2 to R3
and vice-versa (RIP will work fine to prove this point.)  Hope this
helps...and as always, comments are welcome ( and in fact expected
;-)Frank

James Wilson wrote:
>
> Hi All,
>
> I hope someone can shed some light on the problem I have come across in
the
> following scenario :
>
> Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> router in the middle doing frame relay switching. The frame switch is
_not_
> fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
is
> _no_ PVC between R2 and R3.
>
> The particular lab exercise here specifies that each router much be able
to
> ping every other router in the frame cloud. BUT the use of the
'frame-relay
> map' command is forbidden, and only R1 can be configured using a
subinterface.
>
> As I have it configured R1 can ping both R2 and R3 as expected. However,
> both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> question stipulates you should use routing and not Layer2 to Layer3
> mapping. A debug on the ping from R2 to R3 shows that there is no map
entry
> for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> only 1 entry and it is for R1. This sh frame map is identical on R2 and
R3.
>
> So the question is, how can I get R2 and R3 to be able to ping each other
> using routing and not the frame relay map command.
>
> It's got two of us here studying for our CCIE stumped, so im hoping
someone
> out there has an idea as to how this can be accomplished.
>
> Also, as this is for the CCIE, static routes are not an option.
>
> Cheers.
>
> Jim.
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay Problem

2000-11-26 Thread James Wilson

All interfaces on the frame relay network are in the same 10.1.x.x/16 
subnet. Hence there is a connected route comming from the frame relay 
interface which will be preferred over any default route or any other route.

At 10:43 AM 26/11/2000 -0600, Aaron K. Dixon wrote:
>You will need to either generate default routes for the spokes or use policy
>routing to set the default next hop.
>
>Regards,
>Aaron K. Dixon
>
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
>Frank B.
>Sent: Sunday, November 26, 2000 10:27 PM
>To: James Wilson
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: Frame Relay Problem
>
>
>Unless I'm mis-reading you here this is the correct behavior for a
>partial mesh.  Unless you provide a full mesh you won't get dynamic
>mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
>subnet and the PVC from R1 to R3 is another subnet--Frame relay and
>Inverse ARP alone can't route between them.
>
>So if you can't get a PVC between R2 and R3...then run any routing
>protocol on all 3 routers and you should be able to ping from R2 to R3
>and vice-versa (RIP will work fine to prove this point.)  Hope this
>helps...and as always, comments are welcome ( and in fact expected
>;-)Frank
>
>James Wilson wrote:
> >
> > Hi All,
> >
> > I hope someone can shed some light on the problem I have come across in
>the
> > following scenario :
> >
> > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> > router in the middle doing frame relay switching. The frame switch is
>_not_
> > fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
>is
> > _no_ PVC between R2 and R3.
> >
> > The particular lab exercise here specifies that each router much be able
>to
> > ping every other router in the frame cloud. BUT the use of the
>'frame-relay
> > map' command is forbidden, and only R1 can be configured using a
>subinterface.
> >
> > As I have it configured R1 can ping both R2 and R3 as expected. However,
> > both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> > question stipulates you should use routing and not Layer2 to Layer3
> > mapping. A debug on the ping from R2 to R3 shows that there is no map
>entry
> > for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> > only 1 entry and it is for R1. This sh frame map is identical on R2 and
>R3.
> >
> > So the question is, how can I get R2 and R3 to be able to ping each other
> > using routing and not the frame relay map command.
> >
> > It's got two of us here studying for our CCIE stumped, so im hoping
>someone
> > out there has an idea as to how this can be accomplished.
> >
> > Also, as this is for the CCIE, static routes are not an option.
> >
> > Cheers.
> >
> > Jim.
> >
> > _
> > FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>_
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay Problem

2000-11-27 Thread Aaron K. Dixon

Then try using policy routing to set the next-hop for all packets to go to
the hub which has a route to the other spoke.  Then the other spoke should
have the same type of route-map.  Using this method you won't need to change
the routing table, but change the packets themselves.  Don't forget that if
you are doing this from a local ping on the router you will need to enable
the route-map with the local policy command.

Regards,
Aaron K. Dixon


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
James Wilson
Sent: Sunday, November 26, 2000 10:48 PM
To: Aaron K. Dixon
Cc: Frank B.; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Frame Relay Problem


All interfaces on the frame relay network are in the same 10.1.x.x/16
subnet. Hence there is a connected route comming from the frame relay
interface which will be preferred over any default route or any other route.

At 10:43 AM 26/11/2000 -0600, Aaron K. Dixon wrote:
>You will need to either generate default routes for the spokes or use
policy
>routing to set the default next hop.
>
>Regards,
>Aaron K. Dixon
>
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
>Frank B.
>Sent: Sunday, November 26, 2000 10:27 PM
>To: James Wilson
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: Frame Relay Problem
>
>
>Unless I'm mis-reading you here this is the correct behavior for a
>partial mesh.  Unless you provide a full mesh you won't get dynamic
>mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
>subnet and the PVC from R1 to R3 is another subnet--Frame relay and
>Inverse ARP alone can't route between them.
>
>So if you can't get a PVC between R2 and R3...then run any routing
>protocol on all 3 routers and you should be able to ping from R2 to R3
>and vice-versa (RIP will work fine to prove this point.)  Hope this
>helps...and as always, comments are welcome ( and in fact expected
>;-)Frank
>
>James Wilson wrote:
> >
> > Hi All,
> >
> > I hope someone can shed some light on the problem I have come across in
>the
> > following scenario :
> >
> > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> > router in the middle doing frame relay switching. The frame switch is
>_not_
> > fully meshed. R1 is acting as the hub with R2 and R3 being spokes off
R1.
> > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There
>is
> > _no_ PVC between R2 and R3.
> >
> > The particular lab exercise here specifies that each router much be able
>to
> > ping every other router in the frame cloud. BUT the use of the
>'frame-relay
> > map' command is forbidden, and only R1 can be configured using a
>subinterface.
> >
> > As I have it configured R1 can ping both R2 and R3 as expected. However,
> > both R2 and R3 can only ping R1 (the hub) yet cannot ping each other.
The
> > question stipulates you should use routing and not Layer2 to Layer3
> > mapping. A debug on the ping from R2 to R3 shows that there is no map
>entry
> > for R3 hence encapsulation failed. A look at 'sh frame map' shows there
is
> > only 1 entry and it is for R1. This sh frame map is identical on R2 and
>R3.
> >
> > So the question is, how can I get R2 and R3 to be able to ping each
other
> > using routing and not the frame relay map command.
> >
> > It's got two of us here studying for our CCIE stumped, so im hoping
>someone
> > out there has an idea as to how this can be accomplished.
> >
> > Also, as this is for the CCIE, static routes are not an option.
> >
> > Cheers.
> >
> > Jim.
> >
> > _
> > FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>_
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-27 Thread Frank B.

Ah...now I need more info.  Below you stated "only R1 can be configured
using a subinterface"--so that's my first question:

Is it configured with sub-int's, one for ea PVC?  If yes, and they are
configured as point-to-point then I believe that each separate PVC is
required to be on a separate subnet since the router treats each as a
separate interface.  In this scenario my original response will work.
 
If no, then are you using one multipoint subint on R1 the Hub router? 
If so, one subnet works for all three interfaces but I believe you'll
need map statements at the spokes.  I understand this isn't an option. 
So please provide more details...

If your lab exercise doesn't explicitly disallow point-to-point
subinterfaces at the hub router, R1, then I'd configure it that way,
with 2 differnet subnets and run RIP on all 3 routers...it will work. 
If I missed another restriction you're facing please advise
soonest...I'm now very interested in this one.  Thanks, Frank

James Wilson wrote:
> 
> Nope, all one subnet. i.e all interfaces are on the 10.1.X.X/16 subnet
> 
> Hence the problem.
> 
> Im well aware this is the normal partial mesh behavior and that its quiet
> easily rectified using map statements... but for this particular setup it
> requests the use of routing and not frame relay map statements.
> 
> At 06:26 PM 26/11/2000 -1000, Frank B. wrote:
> >Unless I'm mis-reading you here this is the correct behavior for a
> >partial mesh.  Unless you provide a full mesh you won't get dynamic
> >mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
> >subnet and the PVC from R1 to R3 is another subnet--Frame relay and
> >Inverse ARP alone can't route between them.
> >
> >So if you can't get a PVC between R2 and R3...then run any routing
> >protocol on all 3 routers and you should be able to ping from R2 to R3
> >and vice-versa (RIP will work fine to prove this point.)  Hope this
> >helps...and as always, comments are welcome ( and in fact expected
> >;-)Frank
> >
> >James Wilson wrote:
> > >
> > > Hi All,
> > >
> > > I hope someone can shed some light on the problem I have come across in the
> > > following scenario :
> > >
> > > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a
> > > router in the middle doing frame relay switching. The frame switch is _not_
> > > fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1.
> > > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There is
> > > _no_ PVC between R2 and R3.
> > >
> > > The particular lab exercise here specifies that each router much be able to
> > > ping every other router in the frame cloud. BUT the use of the 'frame-relay
> > > map' command is forbidden, and only R1 can be configured using a
> > subinterface.
> > >
> > > As I have it configured R1 can ping both R2 and R3 as expected. However,
> > > both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The
> > > question stipulates you should use routing and not Layer2 to Layer3
> > > mapping. A debug on the ping from R2 to R3 shows that there is no map entry
> > > for R3 hence encapsulation failed. A look at 'sh frame map' shows there is
> > > only 1 entry and it is for R1. This sh frame map is identical on R2 and R3.
> > >
> > > So the question is, how can I get R2 and R3 to be able to ping each other
> > > using routing and not the frame relay map command.
> > >
> > > It's got two of us here studying for our CCIE stumped, so im hoping someone
> > > out there has an idea as to how this can be accomplished.
> > >
> > > Also, as this is for the CCIE, static routes are not an option.
> > >
> > > Cheers.
> > >
> > > Jim.
> > >
> > > _
> > > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-11-27 Thread NeoLink2000
In a message dated 11/27/00 12:46:17 AM Eastern Standard Time, [EMAIL PROTECTED] writes:


Solve the problem with routing, not 
layer 3 to layer 2 mapping".

Hence ruling out any static frame mapping or arp type solutions as these 
are all layer 2 to layer 3 mapping techniques.


Couldn't you use, on the edges (r2/r3), a gateway of last resort like (ip route 0.0.0.0 0.0.0.0 s0) so when you couldn't find a route it would send it out s0 to the frame switch and then r1 would be able to pass it to the other end...?

Another thought. The lab says that it doesn't want you to use layer 3 to layer 2 mapping. Why can't you use static if it's, as you said, layer 2 to layer 3?

These are just some thoughts, hope I spark something...

Mark Zabludovsky ~ CCNA, CCDA, 1/2-NP
[EMAIL PROTECTED]

 "Even if I knew I had only 1 more week to live, I would still schedule my CCIE lab. I would just have to work a little harder I guess. After all, without any goals in life, I'm dead already."
   ~Mark Zabludovsky~


RE: Frame Relay Problem

2000-11-27 Thread Taylor, Don
Title: RE: Frame Relay Problem





Maybe I'm missing something, but in looking at your config and cross-referencing the rules of the lab, I can't understand why you didn't just create two subinterfaces on R1.

-Original Message-
From: James Wilson [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000 5:50 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Frame Relay Problem



Hi All,


I hope someone can shed some light on the problem I have come across in the 
following scenario :


Three routers, R1,R2 and R3 all connected via a Frame Relay cloud with a 
router in the middle doing frame relay switching. The frame switch is _not_ 
fully meshed. R1 is acting as the hub with R2 and R3 being spokes off R1. 
Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. There is 
_no_ PVC between R2 and R3.


The particular lab exercise here specifies that each router much be able to 
ping every other router in the frame cloud. BUT the use of the 'frame-relay 
map' command is forbidden, and only R1 can be configured using a subinterface.


As I have it configured R1 can ping both R2 and R3 as expected. However, 
both R2 and R3 can only ping R1 (the hub) yet cannot ping each other. The 
question stipulates you should use routing and not Layer2 to Layer3 
mapping. A debug on the ping from R2 to R3 shows that there is no map entry 
for R3 hence encapsulation failed. A look at 'sh frame map' shows there is 
only 1 entry and it is for R1. This sh frame map is identical on R2 and R3.


So the question is, how can I get R2 and R3 to be able to ping each other 
using routing and not the frame relay map command.


It's got two of us here studying for our CCIE stumped, so im hoping someone 
out there has an idea as to how this can be accomplished.


Also, as this is for the CCIE, static routes are not an option.


Cheers.


Jim.


_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]





Re: Frame Relay Problem

2000-11-27 Thread James Wilson

Your suggestions are good, unfortunately i have already tried most of them 
and other break the rules of the lab

Here's a run down :

- R1 is currently configured with 1 multipoint subinterface with multiple 
frame-relay interface-dlci commands.
- The rules state only 1 subinterface can be used, and also state only the 
one 10.1.0.0/16 subnet can be used so that rules out the multiple subnets.
- The lab stipulates the ip addresses for R1, R2 and R2 be 10.1.1.1/16, 
10.1.1.2/16, 10.1.1.3/16 respectively.

So there goes the multiple point to point interfaces / multiple subnets 
idea. bummer.

As you said, Map statements are not to be used. The direct quote from the 
lab is "Also, one of the problems in this lab [i.e r2 not being able to 
ping r3] can be solved with multiple frame map ip statements, but this is 
not the solution i want you to use. Solve the problem with routing, not 
layer 3 to layer 2 mapping".

Hence ruling out any static frame mapping or arp type solutions as these 
are all layer 2 to layer 3 mapping techniques.

The use of OSPF is permitted and required throughout the lab, with alll 
frame relay interfaces being in Area 0.

At 06:58 PM 26/11/2000 -1000, Frank B. wrote:
>Ah...now I need more info.  Below you stated "only R1 can be configured
>using a subinterface"--so that's my first question:
>
>Is it configured with sub-int's, one for ea PVC?  If yes, and they are
>configured as point-to-point then I believe that each separate PVC is
>required to be on a separate subnet since the router treats each as a
>separate interface.  In this scenario my original response will work.
>
>If no, then are you using one multipoint subint on R1 the Hub router?
>If so, one subnet works for all three interfaces but I believe you'll
>need map statements at the spokes.  I understand this isn't an option.
>So please provide more details...
>
>If your lab exercise doesn't explicitly disallow point-to-point
>subinterfaces at the hub router, R1, then I'd configure it that way,
>with 2 differnet subnets and run RIP on all 3 routers...it will work.
>If I missed another restriction you're facing please advise
>soonest...I'm now very interested in this one.  Thanks, Frank
>
>James Wilson wrote:
> >
> > Nope, all one subnet. i.e all interfaces are on the 10.1.X.X/16 subnet
> >
> > Hence the problem.
> >
> > Im well aware this is the normal partial mesh behavior and that its quiet
> > easily rectified using map statements... but for this particular setup it
> > requests the use of routing and not frame relay map statements.
> >
> > At 06:26 PM 26/11/2000 -1000, Frank B. wrote:
> > >Unless I'm mis-reading you here this is the correct behavior for a
> > >partial mesh.  Unless you provide a full mesh you won't get dynamic
> > >mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
> > >subnet and the PVC from R1 to R3 is another subnet--Frame relay and
> > >Inverse ARP alone can't route between them.
> > >
> > >So if you can't get a PVC between R2 and R3...then run any routing
> > >protocol on all 3 routers and you should be able to ping from R2 to R3
> > >and vice-versa (RIP will work fine to prove this point.)  Hope this
> > >helps...and as always, comments are welcome ( and in fact expected
> > >;-)Frank
> > >
> > >James Wilson wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I hope someone can shed some light on the problem I have come 
> across in the
> > > > following scenario :
> > > >
> > > > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud 
> with a
> > > > router in the middle doing frame relay switching. The frame switch 
> is _not_
> > > > fully meshed. R1 is acting as the hub with R2 and R3 being spokes 
> off R1.
> > > > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3. 
> There is
> > > > _no_ PVC between R2 and R3.
> > > >
> > > > The particular lab exercise here specifies that each router much be 
> able to
> > > > ping every other router in the frame cloud. BUT the use of the 
> 'frame-relay
> > > > map' command is forbidden, and only R1 can be configured using a
> > > subinterface.
> > > >
> > > > As I have it configured R1 can ping both R2 and R3 as expected. 
> However,
> > > > both R2 and R3 can only ping R1 (the hub) yet cannot ping each 
> other. The
> > > > question stipulates you should use routing and not Layer2 to Layer3
> > > > mapping. A debug on the ping from R2 to R3 shows that there is no 
> map entry
> > > > for R3 hence encapsulation failed. A look at 'sh frame map' shows 
> there is
> > > > only 1 entry and it is for R1. This sh frame map is identical on R2 
> and R3.
> > > >
> > > > So the question is, how can I get R2 and R3 to be able to ping each 
> other
> > > > using routing and not the frame relay map command.
> > > >
> > > > It's got two of us here studying for our CCIE stumped, so im hoping 
> someone
> > > > out there has an idea as to how this can be accomplished.
> > > >
> > > > Also, as this is for the CCIE, static rou

RE: Frame Relay Problem

2000-11-27 Thread Aaron K. Dixon

With that in mind you come back to the solution of using route-maps to set
your default next-hop.  This is a layer 3 resolution for your problem and
should solve all of your issues.

Regards,
Aaron K. Dixon

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
James Wilson
Sent: Sunday, November 26, 2000 10:58 PM
To: Frank B.
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Frame Relay Problem


Your suggestions are good, unfortunately i have already tried most of them
and other break the rules of the lab

Here's a run down :

- R1 is currently configured with 1 multipoint subinterface with multiple
frame-relay interface-dlci commands.
- The rules state only 1 subinterface can be used, and also state only the
one 10.1.0.0/16 subnet can be used so that rules out the multiple subnets.
- The lab stipulates the ip addresses for R1, R2 and R2 be 10.1.1.1/16,
10.1.1.2/16, 10.1.1.3/16 respectively.

So there goes the multiple point to point interfaces / multiple subnets
idea. bummer.

As you said, Map statements are not to be used. The direct quote from the
lab is "Also, one of the problems in this lab [i.e r2 not being able to
ping r3] can be solved with multiple frame map ip statements, but this is
not the solution i want you to use. Solve the problem with routing, not
layer 3 to layer 2 mapping".

Hence ruling out any static frame mapping or arp type solutions as these
are all layer 2 to layer 3 mapping techniques.

The use of OSPF is permitted and required throughout the lab, with alll
frame relay interfaces being in Area 0.

At 06:58 PM 26/11/2000 -1000, Frank B. wrote:
>Ah...now I need more info.  Below you stated "only R1 can be configured
>using a subinterface"--so that's my first question:
>
>Is it configured with sub-int's, one for ea PVC?  If yes, and they are
>configured as point-to-point then I believe that each separate PVC is
>required to be on a separate subnet since the router treats each as a
>separate interface.  In this scenario my original response will work.
>
>If no, then are you using one multipoint subint on R1 the Hub router?
>If so, one subnet works for all three interfaces but I believe you'll
>need map statements at the spokes.  I understand this isn't an option.
>So please provide more details...
>
>If your lab exercise doesn't explicitly disallow point-to-point
>subinterfaces at the hub router, R1, then I'd configure it that way,
>with 2 differnet subnets and run RIP on all 3 routers...it will work.
>If I missed another restriction you're facing please advise
>soonest...I'm now very interested in this one.  Thanks, Frank
>
>James Wilson wrote:
> >
> > Nope, all one subnet. i.e all interfaces are on the 10.1.X.X/16 subnet
> >
> > Hence the problem.
> >
> > Im well aware this is the normal partial mesh behavior and that its
quiet
> > easily rectified using map statements... but for this particular setup
it
> > requests the use of routing and not frame relay map statements.
> >
> > At 06:26 PM 26/11/2000 -1000, Frank B. wrote:
> > >Unless I'm mis-reading you here this is the correct behavior for a
> > >partial mesh.  Unless you provide a full mesh you won't get dynamic
> > >mappings for both spokes.  Also, I assume the PVC from R1 to R2 is one
> > >subnet and the PVC from R1 to R3 is another subnet--Frame relay and
> > >Inverse ARP alone can't route between them.
> > >
> > >So if you can't get a PVC between R2 and R3...then run any routing
> > >protocol on all 3 routers and you should be able to ping from R2 to R3
> > >and vice-versa (RIP will work fine to prove this point.)  Hope this
> > >helps...and as always, comments are welcome ( and in fact expected
> > >;-)Frank
> > >
> > >James Wilson wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I hope someone can shed some light on the problem I have come
> across in the
> > > > following scenario :
> > > >
> > > > Three routers, R1,R2 and R3 all connected via a Frame Relay cloud
> with a
> > > > router in the middle doing frame relay switching. The frame switch
> is _not_
> > > > fully meshed. R1 is acting as the hub with R2 and R3 being spokes
> off R1.
> > > > Hence there is a PVC betweenR1 and R2 and a PVC between R1 and R3.
> There is
> > > > _no_ PVC between R2 and R3.
> > > >
> > > > The particular lab exercise here specifies that each router much be
> able to
> > > > ping every other router in the frame cloud. BUT the use of the
> 'frame-relay
> > > > map' comman

RE: Frame Relay Problem

2000-11-27 Thread Mohamed Heeba



hi  ;
do u need the 
3 routers to be in the same subnet ?? if so ...gateway of last resort will not 
work since there is a more specific route directly connected  , i guess u 
have to check then something like policy routing .
 
as u didnt 
mention that it is a must to put the routers in the same subnet , then creating 
two different subnets ( one between r1 subif1  and r2  and the second 
between r1subif2 and r3 )  will  simply solve your problem 

 
 
Mohamed 
A.HeebaCCNP ,CCDA 

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]Sent: Sunday, November 26, 2000 10:56 
  PMTo: [EMAIL PROTECTED]; [EMAIL PROTECTED]Subject: 
  Re: Frame Relay ProblemIn a message dated 11/27/00 12:46:17 AM Eastern Standard Time, 
  [EMAIL PROTECTED] writes: 
  Solve the problem with routing, not layer 3 to layer 2 
mapping". Hence ruling out any static frame mapping or arp type 
solutions as these are all layer 2 to layer 3 mapping techniques. 
  Couldn't you use, on the edges (r2/r3), a gateway of last 
  resort like (ip route 0.0.0.0 0.0.0.0 s0) so when you couldn't find a 
  route it would send it out s0 to the frame switch and then r1 would be 
  able to pass it to the other end...? Another thought. The lab says 
  that it doesn't want you to use layer 3 to layer 2 mapping. Why can't you 
  use static if it's, as you said, layer 2 to layer 3? These are 
  just some thoughts, hope I spark something... Mark Zabludovsky ~ 
  CCNA, CCDA, 1/2-NP [EMAIL PROTECTED] 
  "Even if I knew I had only 1 more week to 
  live, I would still schedule my CCIE lab. I would just have to work a 
  little harder I guess. After all, without any goals in life, I'm dead 
  already." 
    ~Mark 
  Zabludovsky~ 


RE: Frame Relay problem

2000-10-10 Thread Stull, Cory

timing or incorrect lmi type..  If its a newer ios with autosensing lmi then
it is probably a timing or circuit issue...  Is it a T1 and did you set your
timeslots?

-Original Message-
From: Hans Stout [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 1:25 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay problem


Hi colleagues,

I have a problem with my frame relay connection; the serial interface is 
up/down, and when I debug the serial interface, I can see that the interface

is constantly trying to restart:23w5d:

Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down

What could be the reason for this ? I'll add the output for the sh int:


Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u

Thanks for your help in advance.

Georg

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay problem

2000-10-10 Thread Chris Lemagie

I'm not seeing any LMI responses from the frame-relay switch in the
interface statistics.

You will most likely have to change your LMI type from CISCO (default) to
ANSI.

Chris Lemagie
Systems Engineer
Cisco Systems
Seattle Commercial Region
(425) 468-0959
[EMAIL PROTECTED]
http://www.cisco.com/

 -Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]  On Behalf Of
Stull, Cory
Sent:   Tuesday, October 10, 2000 10:13 AM
To: 'Hans Stout'
Cc: 'ciscostudygroup'
Subject:    RE: Frame Relay problem

timing or incorrect lmi type..  If its a newer ios with autosensing lmi then
it is probably a timing or circuit issue...  Is it a T1 and did you set your
timeslots?

-Original Message-
From: Hans Stout [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 1:25 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay problem


Hi colleagues,

I have a problem with my frame relay connection; the serial interface is
up/down, and when I debug the serial interface, I can see that the interface

is constantly trying to restart:23w5d:

Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down

What could be the reason for this ? I'll add the output for the sh int:


Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u

Thanks for your help in advance.

Georg

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at
http://profiles.msn.com.

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay problem

2000-10-10 Thread Winchester, Derek S.

Looks like you are not receiving any LMI. The problem is either with your CO
or your CSU. Check you physical connections and then call the CO to see if
they can tell you if they are having any problems

Derek S. Winchester
Sr. WAN Engineer(CCNP)
Data Communications
[EMAIL PROTECTED]
Phone: 410-953-4887
Cell: 443-562-3456


-Original Message-
From: Hans Stout [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 2:25 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay problem


Hi colleagues,

I have a problem with my frame relay connection; the serial interface is 
up/down, and when I debug the serial interface, I can see that the interface

is constantly trying to restart:23w5d:

Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down

What could be the reason for this ? I'll add the output for the sh int:


Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u

Thanks for your help in advance.

Georg

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay problem

2000-10-10 Thread Guyler, Rik [EESUS]
Title: RE: Frame Relay problem





Hmm...well, you don't give us a config or show version so we don't know for sure what the LMI settings are or what the IOS version is.  However, by the show interface you provided, it looks as if LMI is to blame.

Newer IOS autosenses the LMI type, but still, I don't trust it.  If you have an older IOS or you have a newer IOS that is "autosensing", I would hard code the LMI type.  Also, since IOS sets the LMI type to Cisco by default, when/if you hard code it, you might try setting to use ANSI LMI.

Good luck!


Rik Guyler


-Original Message-
From: Hans Stout [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 2:25 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay problem



Hi colleagues,


I have a problem with my frame relay connection; the serial interface is 
up/down, and when I debug the serial interface, I can see that the interface 
is constantly trying to restart:23w5d:


Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down


What could be the reason for this ? I'll add the output for the sh int:



Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u


Thanks for your help in advance.


Georg


_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


Share information about yourself, create your own public profile at 
http://profiles.msn.com.


**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]





RE: Frame Relay problem

2000-10-10 Thread Winchester, Derek S.

Well it's not mentioned if this is a current connection or a new install. If
this is a current connections and looking at the counters it looks like you
cleared it you might not want to change the lmi type. If this is a new
connection then I would try the auto detect feature or find out the correct
lmi

Derek S. Winchester
Sr. WAN Engineer(CCNP)
Data Communications
[EMAIL PROTECTED]
Phone: 410-953-4887
Cell: 443-562-3456


-Original Message-
From: Chris Lemagie [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 2:06 PM
To: Stull, Cory; 'Hans Stout'
Cc: 'ciscostudygroup'
Subject: RE: Frame Relay problem


I'm not seeing any LMI responses from the frame-relay switch in the
interface statistics.

You will most likely have to change your LMI type from CISCO (default) to
ANSI.

Chris Lemagie
Systems Engineer
Cisco Systems
Seattle Commercial Region
(425) 468-0959
[EMAIL PROTECTED]
http://www.cisco.com/

 -Original Message-
From:   [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]  On Behalf Of
Stull, Cory
Sent:   Tuesday, October 10, 2000 10:13 AM
To: 'Hans Stout'
Cc:     'ciscostudygroup'
Subject:RE: Frame Relay problem

timing or incorrect lmi type..  If its a newer ios with autosensing lmi then
it is probably a timing or circuit issue...  Is it a T1 and did you set your
timeslots?

-Original Message-
From: Hans Stout [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 1:25 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay problem


Hi colleagues,

I have a problem with my frame relay connection; the serial interface is
up/down, and when I debug the serial interface, I can see that the interface

is constantly trying to restart:23w5d:

Serial5/0: attempting to restart:
--More--
23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
--More--
23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down

What could be the reason for this ? I'll add the output for the sh int:


Serial5/0 is up, line protocol is down
  Hardware is M4T
  MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
 reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation FRAME-RELAY, crc 16, loopback not set
  Keepalive set (10 sec)
  LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
  LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
  LMI DLCI 1023  LMI type is CISCO  frame relay DTE
  FR SVC disabled, LAPF state down
  Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0
  Last input 05:47:09, output 00:00:02, output hang never
  Last clearing of "show interface" counters 00:39:54
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  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
 354 packets output, 4649 bytes, 0 underruns
 0 output errors, 0 collisions, 80 interface resets
 0 output buffer failures, 0 output buffers swapped out
 80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u

Thanks for your help in advance.

Georg

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at
http://profiles.msn.com.

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay problem

2000-10-10 Thread jason yee

You might want to check the LMI type follow by the
encapsulation type to see if it is ok 


also set keepalive to zero to see if the interface
comes up if not you got a back interface


suaveguru24
--- Hans Stout <[EMAIL PROTECTED]> wrote:
> Hi colleagues,
> 
> I have a problem with my frame relay connection; the
> serial interface is 
> up/down, and when I debug the serial interface, I
> can see that the interface 
> is constantly trying to restart:23w5d:
> 
> Serial5/0: attempting to restart:
> --More--
> 23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0,
> DTE down
> --More--
> 23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0,
> DTE down
> 
> What could be the reason for this ? I'll add the
> output for the sh int:
> 
> 
> Serial5/0 is up, line protocol is down
>   Hardware is M4T
>   MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
>  reliability 255/255, txload 1/255, rxload 1/255
>   Encapsulation FRAME-RELAY, crc 16, loopback not
> set
>   Keepalive set (10 sec)
>   LMI enq sent  240, LMI stat recvd 0, LMI upd recvd
> 0, DTE LMI down
>   LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
>   LMI DLCI 1023  LMI type is CISCO  frame relay DTE
>   FR SVC disabled, LAPF state down
>   Broadcast queue 0/64, broadcasts sent/dropped 0/0,
> interface broadcasts 0
>   Last input 05:47:09, output 00:00:02, output hang
> never
>   Last clearing of "show interface" counters
> 00:39:54
>   Queueing strategy: fifo
>   Output queue 0/40, 0 drops; input queue 0/75, 0
> drops
>   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
>  354 packets output, 4649 bytes, 0 underruns
>  0 output errors, 0 collisions, 80 interface
> resets
>  0 output buffer failures, 0 output buffers
> swapped out
>  80 carrier transitions DCD=up  DSR=up 
> DTR=up  RTS=up  CTS=u
> 
> Thanks for your help in advance.
> 
> Georg
> 
>
_
> Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com.
> 
> Share information about yourself, create your own
> public profile at 
> http://profiles.msn.com.
> 
> **NOTE: New CCNA/CCDA List has been formed. For more
> information go to
> http://www.groupstudy.com/list/Associates.html
> _
> UPDATED Posting Guidelines:
> http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


__
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay problem

2000-10-10 Thread Charles Ryan

Try setting encapsulation to "frame-relay ietf" and LMI type to "ansi" or
"ansi annex d"

-Chuck

- Original Message -
From: "Hans Stout" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 10, 2000 2:24 PM
Subject: Frame Relay problem


> Hi colleagues,
>
> I have a problem with my frame relay connection; the serial interface is
> up/down, and when I debug the serial interface, I can see that the
interface
> is constantly trying to restart:23w5d:
>
> Serial5/0: attempting to restart:
> --More--
> 23w5d: Serial5/0(out): StEnq, myseq 4, yourseen 0, DTE down
> --More--
> 23w5d: Serial5/0(out): StEnq, myseq 5, yourseen 0, DTE down
>
> What could be the reason for this ? I'll add the output for the sh int:
>
>
> Serial5/0 is up, line protocol is down
>   Hardware is M4T
>   MTU 1500 bytes, BW 2048 Kbit, DLY 2 usec,
>  reliability 255/255, txload 1/255, rxload 1/255
>   Encapsulation FRAME-RELAY, crc 16, loopback not set
>   Keepalive set (10 sec)
>   LMI enq sent  240, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
>   LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
>   LMI DLCI 1023  LMI type is CISCO  frame relay DTE
>   FR SVC disabled, LAPF state down
>   Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts
0
>   Last input 05:47:09, output 00:00:02, output hang never
>   Last clearing of "show interface" counters 00:39:54
>   Queueing strategy: fifo
>   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
>   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
>  354 packets output, 4649 bytes, 0 underruns
>  0 output errors, 0 collisions, 80 interface resets
>  0 output buffer failures, 0 output buffers swapped out
>  80 carrier transitions DCD=up  DSR=up  DTR=up  RTS=up  CTS=u
>
> Thanks for your help in advance.
>
> Georg
>
> _
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> **NOTE: New CCNA/CCDA List has been formed. For more information go to
> http://www.groupstudy.com/list/Associates.html
> _
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame relay problem

2000-11-07 Thread Quadri, Habeeb

FR ckts. can drop generally either due to provider switch problem or due to
line problem.
If you got a CSU/FRAD, check the line performance parameters. First look for
stats. to see
any errors, specially SES/BES or UAS. Some CSU/DSU provides also status on
the errors like
Yellow/Red alarm etc. Also check Frame relay parameters like Frame
reliability errors and lmi 
disconnects to isolate whether this is a frame relay issue. From a practical
point of view, run a continious
ping with 1500 bytes to see whether packets drops but your problem more seem
to be a LEC issue or FR
switch. Once a ckt. drops it takes exactly 1 minute for FR ckt. to come back
up.

Hope this helps.

Habeeb.

> -Original Message-
> From: David Welch [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, November 07, 2000 5:58 AM
> To:   [EMAIL PROTECTED]
> Subject:      Frame relay problem
> 
> Hi, Could anyone help with the following : Part of our network consists of
> 
> Cisco 4500 routers connected via BT frame relay links.
> The problem I am seeing on all 10 routers is links going down then up,
> often 
> for exactly one minute : eg
> 
> .Oct 24 16:25:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
> state 
> cha
> nged to INACTIVE
> .Oct 24 16:25:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
> Serial2/0.
> 4, changed state to down
> .Oct 24 16:26:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
> state 
> cha
> nged to ACTIVE
> .Oct 24 16:26:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
> Serial2/0.
> 4, changed state to up
> 
> The PTT have tested all lines and insist they are clean
> This is happening about 5 - 10 times a day. The IOS was upgraded not too 
> long ago I think. It is now 12.0(4)
> This doesn't seem to have much impact but my customer just wants to know 
> why!
> Any ideas/suggestions very welcome
> 
> TIA
> 
> Dave Welch
> _
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> 
> Share information about yourself, create your own public profile at 
> http://profiles.msn.com.
> 
> _
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame relay problem

2000-11-07 Thread Brian Molinari

This sounds like  your router misses LMI status messages every once and a
while. This could mean a timer problem or the serial interface
could be too busy to process them correctly. My guess is the timer problem,
check with the carrier (or use a WAN sniffer) to see how often LMI status
messages are being sent from the frame switch to your router, then make sure
the defaults or the config on your router matches.

Brian

"David Welch" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi, Could anyone help with the following : Part of our network consists of
> Cisco 4500 routers connected via BT frame relay links.
> The problem I am seeing on all 10 routers is links going down then up,
often
> for exactly one minute : eg
>
> .Oct 24 16:25:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
state
> cha
> nged to INACTIVE
> .Oct 24 16:25:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial2/0.
> 4, changed state to down
> .Oct 24 16:26:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
state
> cha
> nged to ACTIVE
> .Oct 24 16:26:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial2/0.
> 4, changed state to up
>
> The PTT have tested all lines and insist they are clean
> This is happening about 5 - 10 times a day. The IOS was upgraded not too
> long ago I think. It is now 12.0(4)
> This doesn't seem to have much impact but my customer just wants to know
> why!
> Any ideas/suggestions very welcome
>
> TIA
>
> Dave Welch
> _
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>


_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame relay problem

2000-11-07 Thread jenny . mcleod



You can do 'show frame lmi' on your router and compare 'Num Status Enq. Sent'
with 'Num Status Enq. Rcvd'.  They should be the same.  If they don't match,
clear your counters and check again, and check after your problem occurs.
Another useful command to check lmi is 'debug frame lmi'.  This is a fairly safe
debug, unless you have squillions of PVCs.  Having said that, don't blame me if
turning it on makes your network fall over :-)  You can check how often you
receive lmi from the switch (make sure it matches your keepalive, which is 10
seconds by default), and every minute (this might vary depending on switch type,
dunno) you should see a list of PVCs known by the switch and their status (0x0
is inactive, 0x2 is active if I recall correctly).

Having said that, I suspect it's not an LMI problem.  If the LMI wasn't received
at all, I *think* you would see the PVC showing up as deleted (the switch
doesn't know about it), not inactive (the switch knows about it and knows it's
down).

Do PVCs on all ten routers go down at the same time?  If so, I'd seriously yell
at your telco.

JMcL
-- Forwarded by Jenny Mcleod/NSO/CSDA on 08/11/2000 10:17 am
---


"Brian Molinari" <[EMAIL PROTECTED]> on 08/11/2000 08:07:59 am

Please respond to "Brian Molinari" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:(bcc: JENNY MCLEOD/NSO/CSDA)


Subject:  Re: Frame relay problem



This sounds like  your router misses LMI status messages every once and a
while. This could mean a timer problem or the serial interface
could be too busy to process them correctly. My guess is the timer problem,
check with the carrier (or use a WAN sniffer) to see how often LMI status
messages are being sent from the frame switch to your router, then make sure
the defaults or the config on your router matches.

Brian

"David Welch" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi, Could anyone help with the following : Part of our network consists of
> Cisco 4500 routers connected via BT frame relay links.
> The problem I am seeing on all 10 routers is links going down then up,
often
> for exactly one minute : eg
>
> .Oct 24 16:25:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
state
> cha
> nged to INACTIVE
> .Oct 24 16:25:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial2/0.
> 4, changed state to down
> .Oct 24 16:26:32 UTC: %FR-5-DLCICHANGE: Interface Serial2/0 - DLCI 592
state
> cha
> nged to ACTIVE
> .Oct 24 16:26:32 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial2/0.
> 4, changed state to up
>
> The PTT have tested all lines and insist they are clean
> This is happening about 5 - 10 times a day. The IOS was upgraded not too
> long ago I think. It is now 12.0(4)
> This doesn't seem to have much impact but my customer just wants to know
> why!
> Any ideas/suggestions very welcome
>
> TIA
>
> Dave Welch
> _
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>


_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: FRAME RELAY PROBLEM

2000-08-24 Thread William Swedberg

It is my understanding that on point-to-point
interfaces they need to be on seperate subnets.  If
you have multiple routers coming into one interface,
declare the interface a point-to-multipoint interface.
 Do this when you create the subinterface or use the
"ip ospf network X" interface command.  

See this URL for Design suggestions.

http://www.cisco.com/warp/public/104/3.html


William Swedberg CCNP CCDP


--- Peter Gray <[EMAIL PROTECTED]> wrote:
> I have got a problem with FR Config Running OSPF.
> Router A & B are connected 
> to C & D over FR PVC but they don't have to talk to
> each ther. It means A 
> connected to C & D and B is also connected to C & D.
> I am using FR 
> Subinterfaces with pt-to-pt. What is happening that
> sometime I am able to 
> ping to  router C & router D subinterfaces from
> router A but sometimes i 
> don't get any response. I am even unable to ping
> sub-intf of Routers from 
> within the routers.
> See sample config of one of the routers that i have:
> interface Serial0
> no ip address
> ip directed-broadcast
> encapsulation frame-relay
> ip ospf network broadcast
> no ip mroute-cache
> !
> interface Serial0.1 point-to-point
> ip address 131.18.19.185 255.255.255.252
> ip directed-broadcast
> ip ospf network broadcast
> frame-relay interface-dlci 310
> !
> interface Serial0.2 point-to-point
> ip address 131.18.19.189 255.255.255.252
> ip directed-broadcast
> ip ospf network broadcast
> frame-relay interface-dlci 210
> 
> This is config of router B connected to C & D and
> subintf of C &D are on 
> same subnet as subintf 0.1 and 0.2 on this router.
> Is pt-to-pt with sub-intf OK for this scenario?
> 
> Any suggestions... What is the possible cause of
> problem?? Why I am even 
> unable to ping local subintface from within the
> router??
> 
> Thanks..
>
_
> Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com.
> 
> Share information about yourself, create your own
> public profile at 
> http://profiles.msn.com.
> 
> ___
> UPDATED Posting Guidelines:
> http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to
> [EMAIL PROTECTED]
> 
> 
> 


__
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

___
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay Problem

2000-05-17 Thread Benjamin Walling

This post may show my ignorance, but I'll try.  When I set up frame relay in
my lab, I used three routers.  One was configured as a frame relay switch.
I connected the other two to it and set up a frame relay connection between
them.  I was unaware that two adjacent routers could run frame relay to each
other.

Ben

-Original Message-
From: Nathan Cruz [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 17, 2000 8:04 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay Problem




I've set up a frame relay switch at home trying to complete one of the
"CCIE Lab all in one" Labs. For my question, what could cause a PVC to be
inactive? Things I've checked.

Serial is up line protocol is up on both sides.
LMI type is the same
Clocking is set on DCE side.
Encapsulation is Frame relay

What else is there to check? All suggestions appreciated.
 - att1.htm

___
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem

2000-05-18 Thread steven



Have you configure the frame-relay route ??? and "frame-relay 
intf-type dce" on the frame-relay switch ???
 
lee

  ""Nathan Cruz"" <[EMAIL PROTECTED]> wrote in message 
  005c01bfc015$55999d00$[EMAIL PROTECTED]">news:005c01bfc015$55999d00$[EMAIL PROTECTED]...
  
  I've set up a frame relay switch at home trying 
  to complete one of the "CCIE Lab all in one" Labs. For my question, what could 
  cause a PVC to be inactive? Things I've checked. 
   
  Serial is up line protocol is up on both sides. 
  
  LMI type is the same
  Clocking is set on DCE side. 
  Encapsulation is Frame relay
   
  What else is there to check? All suggestions 
  appreciated.


Re: Frame Relay Problem

2000-05-19 Thread Miguel Harris

First what routing protocol are you using and email me for Dynamic Routing on IP, 
OSPF, Static, IPX (Dynamic or Static), Dynamic Over Multi.

Miguel Harris
Network Engineer 
CCNA
email: [EMAIL PROTECTED]

another thing check your DLCI information each router requires a DLCI for every frame 
relay virtual Circuit


Date: Wed, 17 May 2000 22:03:56 -0400
From: "Benjamin Walling" <[EMAIL PROTECTED]>
Subject: RE: Frame Relay Problem

This post may show my ignorance, but I'll try.  When I set up frame relay in
my lab, I used three routers.  One was configured as a frame relay switch.
I connected the other two to it and set up a frame relay connection between
them.  I was unaware that two adjacent routers could run frame relay to each
other.

Ben

- -Original Message-
From: Nathan Cruz [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 17, 2000 8:04 PM
To: [EMAIL PROTECTED]
Subject: Frame Relay Problem




I've set up a frame relay switch at home trying to complete one of the
"CCIE Lab all in one" Labs. For my question, what could cause a PVC to be
inactive? Things I've checked.

Serial is up line protocol is up on both sides.
LMI type is the same
Clocking is set on DCE side.
Encapsulation is Frame relay

What else is there to check? All suggestions appreciated.
- att1.htm

___
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

--


___
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame Relay Problem -- SOLUTION CONFIGs

2000-11-27 Thread James Wilson

All,

Thanks for the help, especially Aaron Dixon... Below are the working 
configs, solved through using Policy Routing which i hadnt thought of.

R1

!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R1-Ob
!
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  no ip address
  encapsulation frame-relay
  no ip mroute-cache
  clockrate 64000
!
interface Serial0.1 multipoint
  ip address 10.1.1.1 255.255.0.0
  no ip split-horizon
  frame-relay interface-dlci 101
  frame-relay interface-dlci 102
!
interface Serial1
  no ip address
  shutdown
!
ip classless
!
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R2

!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname R2-Sambuca
!
!
ip subnet-zero
!
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  ip address 10.1.1.2 255.255.0.0
  encapsulation frame-relay
  ip ospf priority 0
  ip policy route-map POLICY
  no fair-queue
  frame-relay interface-dlci 100
!
interface Serial1
  no ip address
  shutdown
!
ip local policy route-map POLICY
no ip classless
access-list 1 permit 10.1.0.0 0.0.255.255
route-map POLICY permit 10
  match ip address 1
  set ip next-hop 10.1.1.1
!
!!
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R3

!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R3-Budvar
!
!
ip subnet-zero
ip cef
!
!
interface Serial5/0
  ip address 10.1.1.3 255.255.0.0
  no ip directed-broadcast
  encapsulation frame-relay
  ip ospf interface-retry 0
  ip ospf priority 0
  no ip mroute-cache
  ip policy route-map POLICY
  no fair-queue
  frame-relay interface-dlci 100
!
ip local policy route-map POLICY
ip classless
!
access-list 1 permit 10.1.0.0 0.0.255.255
route-map POLICY permit 10
  match ip address 1
  set ip next-hop 10.1.1.1
!
!
!
line con 0
  transport input none
line aux 0
line vty 0 4
!
end

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame-relay problem [7:1986]

2001-04-25 Thread Justin M. Clark

my layout looks kinda like this:

(Computer1)--e0(router1)s0--z---s0(router2)e0--(Computer2)

router1/s0 is the DCE  so i do:
config t
frame-relay switching

then on both i do

encapsulation frame-relay
frame-realy interface-dlci 17
frame-relay intf-type dXe

i then do debug frame-relay lmi and it shows that dce and dte are up but now
i can no longer ping from computer1 to computer2.

but as soon as i switch back to HDLC it all works fine.

the wierd thing is, when i have frame-relay turned on, i cant even ping
router1/s0's ip address from router1.

any ideas?

--
Justin M. Clark
MCSE 4.0, MCSE 2000
CCNA, CCDA
[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=1986&t=1986
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame Relay Problem [7:4435]

2001-05-14 Thread robert alldread

Hey,

I have read through the archives and found information close to what I am
needing, but not exactly.

Here is the question...

I have (3) 3600 series routers connected by Frame-relay links.  router#1 is
the main, router#2 and router#3 hang off of the main in a hub and spoke
config.  I have a DHCP server behind router#1 that all subnets use for
address's.  I am running EIGRP.

Router#2 and router#3 have "ip helper-address" statements for the DHCP
server.  Router#2 can ping the DHCP server and its own serial interface and
get DHCP addresses, but router#3 can't ping the DHCP server or its own
serial interface, or get DHCP address's.  Traffic passes fine, LMI is
correct, and PVC's are setup correctly.  Both Router#2 and Router#3 have the
exact same config(beside network numbers, ip address's, and DLCI's).

What would cause a router not to be able to ping it own serial interface??? 
"show ip int s0" says (up,up) and LMI are increasing every 10 seconds..

Please helpcisco TAC can't even solve this one...

I am not a member of groupstudy (yet), so please respond to
"[EMAIL PROTECTED]"

Thank you guys!!




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4435&t=4435
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame-Relay Problem [7:41250]

2002-04-11 Thread PING

If I have this simple net:

3660(FR Switch)---3640

I am using NM-4T on both routers.
Default (HDLC) encapsulation causes both router serial interfaces to
come up. I am trying inverse ARP from Caslow book but as
soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE

and supplying clock.
I am not sure if someone has tried NM-4T with FR?

/N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41250&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



frame-relay problem [7:60522]

2003-01-07 Thread Stull, Cory
I've got 2 frame-relay PVC's to 2 different remote locations...  Both
identical locations with same amount of PC's running same applications...
Greenbay and Madison and the central location is Milwaukee.   When doing a
normal ping test to Greenbay and Madison the Greenbay locations response
times are almost 3 times faster.   When doing a large 4048byte ping test the
Madison locations response times are a little bit faster..
 
The routers are 2500's and the speed of both circuits is 128k port 64k CIR
frame-relay.   Weighted fair queueing as is the default.
 
Why would my ping times be 3 times faster to Greenbay with normal ping and a
little faster to Madison with a large ping?
 
Of course SBC hasn't found anything wrong.
 
 
Any advice would be helpful, this one is stumping me.
 
Thanks
Cory




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=60522&t=60522
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame Relay Problem -- SOLUTION CONFIGs

2000-11-27 Thread Aaron K. Dixon

I'm glad that you resolved the problem.  Policy routing can be a very
powerful tool and it overrides limitations of not being able to use static
routes.  You should take the time to review all of the possibilities
availble with policy routing.  Of course, don't forget that if you want to
policy route locally generated traffic use the ip local policy command.
That will get you everytime otherwise.

Regards,
Aaron K. Dixon
CCIE #6460

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
James Wilson
Sent: Monday, November 27, 2000 1:25 AM
To: [EMAIL PROTECTED]
Subject: Frame Relay Problem -- SOLUTION CONFIGs


All,

Thanks for the help, especially Aaron Dixon... Below are the working
configs, solved through using Policy Routing which i hadnt thought of.

R1

!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R1-Ob
!
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  no ip address
  encapsulation frame-relay
  no ip mroute-cache
  clockrate 64000
!
interface Serial0.1 multipoint
  ip address 10.1.1.1 255.255.0.0
  no ip split-horizon
  frame-relay interface-dlci 101
  frame-relay interface-dlci 102
!
interface Serial1
  no ip address
  shutdown
!
ip classless
!
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R2

!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname R2-Sambuca
!
!
ip subnet-zero
!
!
interface Ethernet0
  no ip address
  shutdown
!
interface Serial0
  ip address 10.1.1.2 255.255.0.0
  encapsulation frame-relay
  ip ospf priority 0
  ip policy route-map POLICY
  no fair-queue
  frame-relay interface-dlci 100
!
interface Serial1
  no ip address
  shutdown
!
ip local policy route-map POLICY
no ip classless
access-list 1 permit 10.1.0.0 0.0.255.255
route-map POLICY permit 10
  match ip address 1
  set ip next-hop 10.1.1.1
!
!!
!
line con 0
line aux 0
line vty 0 4
  login
!
end

R3

!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R3-Budvar
!
!
ip subnet-zero
ip cef
!
!
interface Serial5/0
  ip address 10.1.1.3 255.255.0.0
  no ip directed-broadcast
  encapsulation frame-relay
  ip ospf interface-retry 0
  ip ospf priority 0
  no ip mroute-cache
  ip policy route-map POLICY
  no fair-queue
  frame-relay interface-dlci 100
!
ip local policy route-map POLICY
ip classless
!
access-list 1 permit 10.1.0.0 0.0.255.255
route-map POLICY permit 10
  match ip address 1
  set ip next-hop 10.1.1.1
!
!
!
line con 0
  transport input none
line aux 0
line vty 0 4
!
end

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem -- SOLUTION CONFIGs

2000-11-27 Thread Nigel Taylor

James,
Well it's good to see you got this problem solved and as
always the list was invaluable(Big up! Aaron).  Thanks for sharing this one
with us.  I'm going to throw this one up on the routers and what the
magic...

"I love this business" and "I love this list"

Nigel.

- Original Message -
From: James Wilson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 27, 2000 7:25 AM
Subject: Frame Relay Problem -- SOLUTION CONFIGs


> All,
>
> Thanks for the help, especially Aaron Dixon... Below are the working
> configs, solved through using Policy Routing which i hadnt thought of.
>
> R1
>
> !
> version 11.3
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname R1-Ob
> !
> !
> interface Ethernet0
>   no ip address
>   shutdown
> !
> interface Serial0
>   no ip address
>   encapsulation frame-relay
>   no ip mroute-cache
>   clockrate 64000
> !
> interface Serial0.1 multipoint
>   ip address 10.1.1.1 255.255.0.0
>   no ip split-horizon
>   frame-relay interface-dlci 101
>   frame-relay interface-dlci 102
> !
> interface Serial1
>   no ip address
>   shutdown
> !
> ip classless
> !
> !
> line con 0
> line aux 0
> line vty 0 4
>   login
> !
> end
>
> R2
>
> !
> version 11.2
> no service password-encryption
> no service udp-small-servers
> no service tcp-small-servers
> !
> hostname R2-Sambuca
> !
> !
> ip subnet-zero
> !
> !
> interface Ethernet0
>   no ip address
>   shutdown
> !
> interface Serial0
>   ip address 10.1.1.2 255.255.0.0
>   encapsulation frame-relay
>   ip ospf priority 0
>   ip policy route-map POLICY
>   no fair-queue
>   frame-relay interface-dlci 100
> !
> interface Serial1
>   no ip address
>   shutdown
> !
> ip local policy route-map POLICY
> no ip classless
> access-list 1 permit 10.1.0.0 0.0.255.255
> route-map POLICY permit 10
>   match ip address 1
>   set ip next-hop 10.1.1.1
> !
> !!
> !
> line con 0
> line aux 0
> line vty 0 4
>   login
> !
> end
>
> R3
>
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname R3-Budvar
> !
> !
> ip subnet-zero
> ip cef
> !
> !
> interface Serial5/0
>   ip address 10.1.1.3 255.255.0.0
>   no ip directed-broadcast
>   encapsulation frame-relay
>   ip ospf interface-retry 0
>   ip ospf priority 0
>   no ip mroute-cache
>   ip policy route-map POLICY
>   no fair-queue
>   frame-relay interface-dlci 100
> !
> ip local policy route-map POLICY
> ip classless
> !
> access-list 1 permit 10.1.0.0 0.0.255.255
> route-map POLICY permit 10
>   match ip address 1
>   set ip next-hop 10.1.1.1
> !
> !
> !
> line con 0
>   transport input none
> line aux 0
> line vty 0 4
> !
> end
>
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-relay problem [7:1986]

2001-04-25 Thread Circusnuts

I'm not sure, but is this a typo, but are you running some sort of inverted
clocking > ???  Do you have a frame type or
LMI configured ???  It usually makes more sense when you setup your lab with
one central clocking router as the Frame cloud.  The information you need
from the Frame Switch, started in version 10.0 (most any router would work
here).

Phil
- Original Message -
From: Justin M. Clark 
To: 
Sent: Wednesday, April 25, 2001 7:11 PM
Subject: Frame-relay problem [7:1986]


> my layout looks kinda like this:
>
> (Computer1)--e0(router1)s0--z---s0(router2)e0--(Computer2)
>
> router1/s0 is the DCE  so i do:
> config t
> frame-relay switching
>
> then on both i do
>
> encapsulation frame-relay
> frame-realy interface-dlci 17
> frame-relay intf-type dXe
>
> i then do debug frame-relay lmi and it shows that dce and dte are up but
now
> i can no longer ping from computer1 to computer2.
>
> but as soon as i switch back to HDLC it all works fine.
>
> the wierd thing is, when i have frame-relay turned on, i cant even ping
> router1/s0's ip address from router1.
>
> any ideas?
>
> --
> Justin M. Clark
> MCSE 4.0, MCSE 2000
> CCNA, CCDA
> [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=1989&t=1986
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame-relay problem [7:1986]

2001-04-26 Thread Parrish, Ben

I used the sample configs off of the Cisco TAC website.
http://www.cisco.com/warp/customer/125/fr_switching.html  
requires CCO login)

http://www.cisco.com/warp/public/125/index.shtml
(does Not require CCO login)

The first link is for frame-relay switching.  (i.e. one router acting as a 
frame switch.  Great if you have a 2522 to act as a switch.  This one is a 
little confusing due to the local signifigance of DLCI's but the switch
works great.
The second is a general link to sample configs dealing with frame-relay.
Good Luck,
Benjamin Parrish
CCNP,CCDP (CCIE written in 29 hours and counting)

-Original Message-
From: Justin M. Clark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 6:12 PM
To: [EMAIL PROTECTED]
Subject: Frame-relay problem [7:1986]


my layout looks kinda like this:

(Computer1)--e0(router1)s0--z---s0(router2)e0--(Computer2)

router1/s0 is the DCE  so i do:
config t
frame-relay switching

then on both i do

encapsulation frame-relay
frame-realy interface-dlci 17
frame-relay intf-type dXe

i then do debug frame-relay lmi and it shows that dce and dte are up but now
i can no longer ping from computer1 to computer2.

but as soon as i switch back to HDLC it all works fine.

the wierd thing is, when i have frame-relay turned on, i cant even ping
router1/s0's ip address from router1.

any ideas?

--
Justin M. Clark
MCSE 4.0, MCSE 2000
CCNA, CCDA
[EMAIL PROTECTED]
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=2097&t=1986
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem [7:4435]

2001-05-14 Thread Ken Vandenbark

R,

Are you using inverse arp or maps statements for your dlci to ip mappings?
If you are using mappings you will need to configure a map statement as the
one to the hub but map it to the local ip of the router. Use caution if on
production network.
For the problem with DHCP try traceroute and see where it dies.
hth
kv

- Original Message -
From: "robert alldread" <>
To: 
Sent: Monday, May 14, 2001 11:00 AM
Subject: Frame Relay Problem [7:4435]


> Hey,
>
> I have read through the archives and found information close to what I am
> needing, but not exactly.
>
> Here is the question...
>
> I have (3) 3600 series routers connected by Frame-relay links.  router#1
is
> the main, router#2 and router#3 hang off of the main in a hub and spoke
> config.  I have a DHCP server behind router#1 that all subnets use for
> address's.  I am running EIGRP.
>
> Router#2 and router#3 have "ip helper-address" statements for the DHCP
> server.  Router#2 can ping the DHCP server and its own serial interface
and
> get DHCP addresses, but router#3 can't ping the DHCP server or its own
> serial interface, or get DHCP address's.  Traffic passes fine, LMI is
> correct, and PVC's are setup correctly.  Both Router#2 and Router#3 have
the
> exact same config(beside network numbers, ip address's, and DLCI's).
>
> What would cause a router not to be able to ping it own serial
interface???
> "show ip int s0" says (up,up) and LMI are increasing every 10 seconds..
>
> Please helpcisco TAC can't even solve this one...
>
> I am not a member of groupstudy (yet), so please respond to
> "[EMAIL PROTECTED]"
>
> Thank you guys!!
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=&t=4435
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame Relay Problem [7:4435]

2001-05-14 Thread Jason Roysdon

Make sure you have 'ip bootp server' configured (default), and not 'no ip
bootp server'.  It will stop the ip helper-address from forwarding DHCP
requests if you have it disabled.

Use extended ping to ping from the LAN side of the router that is at the
site with DHCP problems.

'term mon' and 'debug ip dhcp server events' and 'debug ip dhcp server
events' (I think those are the right debugs, I can't seem to find any for ip
helper-address or bootp debug commands so I'm guessing that is it.  Actually
I think the 'debug ip dhcp server *' stuff is for the local dhcp server that
could be configured on the router.  You'll want 'debug ip udp' but be aware
that this will potentially generate a ton of debugs depending on normal
traffic.  I just did it on my local VoIP network: Bad idea, hehee.

What's the fastest command to kill all debug on a router?  I'm pretty sure
it's 'u all'

--
Jason Roysdon, CCNP+Security/CCDP, MCSE, CNA, Network+, A+
List email: [EMAIL PROTECTED]
Homepage: http://jason.artoo.net/



""robert alldread""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hey,
>
> I have read through the archives and found information close to what I am
> needing, but not exactly.
>
> Here is the question...
>
> I have (3) 3600 series routers connected by Frame-relay links.  router#1
is
> the main, router#2 and router#3 hang off of the main in a hub and spoke
> config.  I have a DHCP server behind router#1 that all subnets use for
> address's.  I am running EIGRP.
>
> Router#2 and router#3 have "ip helper-address" statements for the DHCP
> server.  Router#2 can ping the DHCP server and its own serial interface
and
> get DHCP addresses, but router#3 can't ping the DHCP server or its own
> serial interface, or get DHCP address's.  Traffic passes fine, LMI is
> correct, and PVC's are setup correctly.  Both Router#2 and Router#3 have
the
> exact same config(beside network numbers, ip address's, and DLCI's).
>
> What would cause a router not to be able to ping it own serial
interface???
> "show ip int s0" says (up,up) and LMI are increasing every 10 seconds..
>
> Please helpcisco TAC can't even solve this one...
>
> I am not a member of groupstudy (yet), so please respond to
> "[EMAIL PROTECTED]"
>
> Thank you guys!!
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4454&t=4435
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-11 Thread Chris Camplejohn

Did you put frame-relay intf-type on the frame-interface?

Chris

""PING""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> If I have this simple net:
>
> 3660(FR Switch)---3640
>
> I am using NM-4T on both routers.
> Default (HDLC) encapsulation causes both router serial interfaces to
> come up. I am trying inverse ARP from Caslow book but as
> soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE
>
> and supplying clock.
> I am not sure if someone has tried NM-4T with FR?
>
> /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41254&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame-Relay Problem [7:41250]

2002-04-11 Thread Lupi, Guy

Do you have another router to connect to the 3660?  This would give you a
better idea of how it really works.  It looks like right now you are trying
to do frame relay back to back, which also works, but it depends on how you
have your settings.  If you want to do frame relay encapsulation back to
back, take a look at this link:

http://www.cisco.com/warp/public/125/frbacktoback_hybrid.html

Guy

-Original Message-
From: PING
To: [EMAIL PROTECTED]
Sent: 4/11/2002 9:49 PM
Subject: Frame-Relay Problem [7:41250]

If I have this simple net:

3660(FR Switch)---3640

I am using NM-4T on both routers.
Default (HDLC) encapsulation causes both router serial interfaces to
come up. I am trying inverse ARP from Caslow book but as
soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE

and supplying clock.
I am not sure if someone has tried NM-4T with FR?

/N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41255&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-11 Thread Engelhard M. Labiro

Ping,

Have you configure the following comands on FR switch ?
1. Global config mode : "frame-relay switching"
2. Interface config mode: "frame-relay intf-type dce"



- Original Message - 
From: "PING" 
To: 
Sent: Friday, April 12, 2002 10:49 AM
Subject: Frame-Relay Problem [7:41250]


> If I have this simple net:
> 
> 3660(FR Switch)---3640
> 
> I am using NM-4T on both routers.
> Default (HDLC) encapsulation causes both router serial interfaces to
> come up. I am trying inverse ARP from Caslow book but as
> soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE
> 
> and supplying clock.
> I am not sure if someone has tried NM-4T with FR?
> 
> /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41258&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-11 Thread PING

Yes. It works from 3660 to 3800. Doesn't work from
NM-4T to NM-4T.

/N

Chris Camplejohn wrote:

> Did you put frame-relay intf-type on the frame-interface?
>
> Chris
>
> ""PING""  wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > If I have this simple net:
> >
> > 3660(FR Switch)---3640
> >
> > I am using NM-4T on both routers.
> > Default (HDLC) encapsulation causes both router serial interfaces to
> > come up. I am trying inverse ARP from Caslow book but as
> > soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE
> >
> > and supplying clock.
> > I am not sure if someone has tried NM-4T with FR?
> >
> > /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41259&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-11 Thread PING

The question is that Caslow says on page-110 that if FR switching is
on, just enabling the encapsulation will bring up the PVC by using
inverse arp. I don't see that happening.

/N

"Engelhard M. Labiro" wrote:

> Ping,
>
> Have you configure the following comands on FR switch ?
> 1. Global config mode : "frame-relay switching"
> 2. Interface config mode: "frame-relay intf-type dce"
>
> - Original Message -
> From: "PING"
> To:
> Sent: Friday, April 12, 2002 10:49 AM
> Subject: Frame-Relay Problem [7:41250]
>
> > If I have this simple net:
> >
> > 3660(FR Switch)---3640
> >
> > I am using NM-4T on both routers.
> > Default (HDLC) encapsulation causes both router serial interfaces to
> > come up. I am trying inverse ARP from Caslow book but as
> > soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE
> >
> > and supplying clock.
> > I am not sure if someone has tried NM-4T with FR?
> >
> > /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41260&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame-Relay Problem [7:41250]

2002-04-11 Thread Sean Knox

Check the clock rate and cabling on both ends. If the clock rate specified
is different than what the module supports, then I believe the line will
come up and go back down. (For example, the WIC-2A/S cards only support a
maximum clock rate of 128K).

* Check cabling (are the DCE and DTE ends correct?)
* Make sure frame-relay intf-type is set correctly on both ends (and cabling
is OK)
* Check clock rate (set on the interface)
* Issue a "no shut" on all frame-relay interfaces on both ends of the PVC.

hth,
Sean

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
PING
Sent: Thursday, April 11, 2002 7:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Frame-Relay Problem [7:41250]


The question is that Caslow says on page-110 that if FR switching is
on, just enabling the encapsulation will bring up the PVC by using
inverse arp. I don't see that happening.

/N

"Engelhard M. Labiro" wrote:

> Ping,
>
> Have you configure the following comands on FR switch ?
> 1. Global config mode : "frame-relay switching"
> 2. Interface config mode: "frame-relay intf-type dce"
>
> - Original Message -
> From: "PING"
> To:
> Sent: Friday, April 12, 2002 10:49 AM
> Subject: Frame-Relay Problem [7:41250]
>
> > If I have this simple net:
> >
> > 3660(FR Switch)---3640
> >
> > I am using NM-4T on both routers.
> > Default (HDLC) encapsulation causes both router serial interfaces to
> > come up. I am trying inverse ARP from Caslow book but as
> > soon as I enable FR (or even PPP) encap, line goes down. 3660 is the DCE
> >
> > and supplying clock.
> > I am not sure if someone has tried NM-4T with FR?
> >
> > /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41264&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-12 Thread PING

I have already done all steps except the first one. Its a good point and
I'll check that. It is possible that module doesn't support 64K clock(?)

/N

Sean Knox wrote:

> Check the clock rate and cabling on both ends. If the clock rate specified
> is different than what the module supports, then I believe the line will
> come up and go back down. (For example, the WIC-2A/S cards only support a
> maximum clock rate of 128K).
>
> * Check cabling (are the DCE and DTE ends correct?)
> * Make sure frame-relay intf-type is set correctly on both ends (and
cabling
> is OK)
> * Check clock rate (set on the interface)
> * Issue a "no shut" on all frame-relay interfaces on both ends of the PVC.
>
> hth,
> Sean
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> PING
> Sent: Thursday, April 11, 2002 7:43 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Frame-Relay Problem [7:41250]
>
> The question is that Caslow says on page-110 that if FR switching is
> on, just enabling the encapsulation will bring up the PVC by using
> inverse arp. I don't see that happening.
>
> /N
>
> "Engelhard M. Labiro" wrote:
>
> > Ping,
> >
> > Have you configure the following comands on FR switch ?
> > 1. Global config mode : "frame-relay switching"
> > 2. Interface config mode: "frame-relay intf-type dce"
> >
> > - Original Message -
> > From: "PING"
> > To:
> > Sent: Friday, April 12, 2002 10:49 AM
> > Subject: Frame-Relay Problem [7:41250]
> >
> > > If I have this simple net:
> > >
> > > 3660(FR Switch)---3640
> > >
> > > I am using NM-4T on both routers.
> > > Default (HDLC) encapsulation causes both router serial interfaces to
> > > come up. I am trying inverse ARP from Caslow book but as
> > > soon as I enable FR (or even PPP) encap, line goes down. 3660 is the
DCE
> > >
> > > and supplying clock.
> > > I am not sure if someone has tried NM-4T with FR?
> > >
> > > /N




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41294&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay Problem [7:41250]

2002-04-13 Thread Michael Williams

Sean brings up a good point to check the maximum clock rate of your module. 
I've seen more than 1 person try to use the A/S module for 1.544Mbps
However, the A/S module that he refers to supports a max of 115.2Kbps in
async mode and when put into sync mode supports a max of 128Kbps.  This
module you speak of (NM-4T) should support up to 8Mbps on a single interface
or up to 2Mbps on all 4 interfaces at the same time.  (just to be sure I
checked Cisco's site on that module and here's what I found:

"The 4-port synchronous (sync) serial network module (NM-4T) has four DB-60
ports and provides a data rate of 8 Mbps on port 0, 4 Mbps each on port 0
and port 2, or 2 Mbps on all four ports simultaneously. The NM-4T network
module supports only sync mode. "

http://www.cisco.com/warp/public/107/hw_4t.html

So you clockrate shouldn't be a problem at 64Kbps.  It seems that most
of any suggestions I could make have been covered here (framing, frame-relay
switching, etc).  I guess I would just start at layer 1 and work up from
there.  i.e. make sure all cables, connectors and even serial interfaces on
the routers are good, then proceed up to layer 2 with debugs, etc

HTH,
Mike W.


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=41368&t=41250
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: frame-relay problem [7:60522]

2003-01-07 Thread Captain Lance
Have you factored in the amount of load on the PVC between Milwaukee and
Madison?



""Stull, Cory""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I've got 2 frame-relay PVC's to 2 different remote locations...  Both
> identical locations with same amount of PC's running same applications...
> Greenbay and Madison and the central location is Milwaukee.   When doing a
> normal ping test to Greenbay and Madison the Greenbay locations response
> times are almost 3 times faster.   When doing a large 4048byte ping test
the
> Madison locations response times are a little bit faster..
>
> The routers are 2500's and the speed of both circuits is 128k port 64k CIR
> frame-relay.   Weighted fair queueing as is the default.
>
> Why would my ping times be 3 times faster to Greenbay with normal ping and
a
> little faster to Madison with a large ping?
>
> Of course SBC hasn't found anything wrong.
>
>
> Any advice would be helpful, this one is stumping me.
>
> Thanks
> Cory




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=60539&t=60522
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Bob Timmons

We're switching our routers from 3Com to Cisco and we're having
trouble at one of our sites.  We've got a hub-and-spoke configuration
from our central site to 4 other sites.  3 of the sites come up when
we switch the hardware to Cisco (simply moving the CSU from the 3Com
router to the Cisco router), the 4th does not.  I'm including the
Central Site config and 2 of the remotes (Site 1 comes up, Site 2 does
not).

We've changed out the router (including the serial ports), csu, serial
cable, rj45's, everything.  It's not a hardware problem.  We changed
the CSU on the central site, just to see if it would help.  No go.

Please let me know if you see something weird.

I've replaced the DLCI #'s with letters, but they match up (i.e. if
it's ABC in site 1, it matches to ABC in central site).  I didn't
include configs for sites 3 & 4, but they're identical with the
exception of the DLCI's and IP's.  (and they work as well).

Something I had thought about... this site is in Canada and we're in
the US as well as the other 3 sites.  Would there be any caveats
regarding international connections?  Again, everything works when
connected to the 3Com equipment, it's only when we connect up the
Cisco's that site 1 fails.

Thanks for any input.

Bob

--
Site 1 (This site works fine)

Current configuration:
!
version 12.0

ip subnet-zero

interface Serial0/0
 ip address x.x.53.26 255.255.255.252
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-point
 ip ospf dead-interval 60
 no ip mroute-cache
 no fair-queue
 frame-relay interface-dlci ABC
--
Site 2 (This site does not come up)

Current configuration:
!
version 12.0

ip subnet-zero

interface Serial0/0
 ip address x.x.53.2 255.255.255.252
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-point
 ip ospf dead-interval 60
 no ip mroute-cache
 no fair-queue
 frame-relay interface-dlci XYZ
--
Central Site

Current configuration:
version 12.0

ip subnet-zero

interface Serial5/1
 no ip address
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf dead-interval 60
!
interface Serial5/1.1 point-to-point
 ip address x.x.53.17 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 ipx network 92
 frame-relay interface-dlci GHI
!
interface Serial5/1.2 point-to-point
 ip address x.x.53.21 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 ipx network 54B
 frame-relay interface-dlci DEF
!
interface Serial5/1.3 point-to-point
 bandwidth 64000
 ip address x.x.53.1 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 frame-relay interface-dlci XYZ
!
interface Serial5/1.4 point-to-point
 bandwidth 64000
 ip address x.x.53.25 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 frame-relay interface-dlci ABC
--




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32307&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread John Neiberger

What do you mean, specifically?  Does the line protocol never come up? 
Does the line protocol come up yet OSPF adjacencies do not form?  Does
the physical interface even come up?

Thanks,
John

>>> "Bob Timmons"  1/17/02 9:22:54 AM >>>
We're switching our routers from 3Com to Cisco and we're having
trouble at one of our sites.  We've got a hub-and-spoke configuration
from our central site to 4 other sites.  3 of the sites come up when
we switch the hardware to Cisco (simply moving the CSU from the 3Com
router to the Cisco router), the 4th does not.  I'm including the
Central Site config and 2 of the remotes (Site 1 comes up, Site 2 does
not).

We've changed out the router (including the serial ports), csu, serial
cable, rj45's, everything.  It's not a hardware problem.  We changed
the CSU on the central site, just to see if it would help.  No go.

Please let me know if you see something weird.

I've replaced the DLCI #'s with letters, but they match up (i.e. if
it's ABC in site 1, it matches to ABC in central site).  I didn't
include configs for sites 3 & 4, but they're identical with the
exception of the DLCI's and IP's.  (and they work as well).

Something I had thought about... this site is in Canada and we're in
the US as well as the other 3 sites.  Would there be any caveats
regarding international connections?  Again, everything works when
connected to the 3Com equipment, it's only when we connect up the
Cisco's that site 1 fails.

Thanks for any input.

Bob

--
Site 1 (This site works fine)

Current configuration:
!
version 12.0

ip subnet-zero

interface Serial0/0
 ip address x.x.53.26 255.255.255.252
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-point
 ip ospf dead-interval 60
 no ip mroute-cache
 no fair-queue
 frame-relay interface-dlci ABC
--
Site 2 (This site does not come up)

Current configuration:
!
version 12.0

ip subnet-zero

interface Serial0/0
 ip address x.x.53.2 255.255.255.252
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-point
 ip ospf dead-interval 60
 no ip mroute-cache
 no fair-queue
 frame-relay interface-dlci XYZ
--
Central Site

Current configuration:
version 12.0

ip subnet-zero

interface Serial5/1
 no ip address
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf dead-interval 60
!
interface Serial5/1.1 point-to-point
 ip address x.x.53.17 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 ipx network 92
 frame-relay interface-dlci GHI
!
interface Serial5/1.2 point-to-point
 ip address x.x.53.21 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 ipx network 54B
 frame-relay interface-dlci DEF
!
interface Serial5/1.3 point-to-point
 bandwidth 64000
 ip address x.x.53.1 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 frame-relay interface-dlci XYZ
!
interface Serial5/1.4 point-to-point
 bandwidth 64000
 ip address x.x.53.25 255.255.255.252
 no ip directed-broadcast
 ip ospf network point-to-point
 ip ospf dead-interval 60
 frame-relay interface-dlci ABC
--




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32313&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Bob Timmons

On S5/1 I get UP/UP.

On S5/1.4, I get UP/UP on our side and UP/UP on the remote side.
On S5/1.3 I get Down/Down on our side and Up/Down on their side.

> What do you mean, specifically?  Does the line protocol never come up?
> Does the line protocol come up yet OSPF adjacencies do not form?  Does
> the physical interface even come up?
>
> Thanks,
> John
>
> >>> "Bob Timmons"  1/17/02 9:22:54 AM >>>
> We're switching our routers from 3Com to Cisco and we're having
> trouble at one of our sites.  We've got a hub-and-spoke configuration
> from our central site to 4 other sites.  3 of the sites come up when
> we switch the hardware to Cisco (simply moving the CSU from the 3Com
> router to the Cisco router), the 4th does not.  I'm including the
> Central Site config and 2 of the remotes (Site 1 comes up, Site 2 does
> not).
>
> We've changed out the router (including the serial ports), csu, serial
> cable, rj45's, everything.  It's not a hardware problem.  We changed
> the CSU on the central site, just to see if it would help.  No go.
>
> Please let me know if you see something weird.
>
> I've replaced the DLCI #'s with letters, but they match up (i.e. if
> it's ABC in site 1, it matches to ABC in central site).  I didn't
> include configs for sites 3 & 4, but they're identical with the
> exception of the DLCI's and IP's.  (and they work as well).
>
> Something I had thought about... this site is in Canada and we're in
> the US as well as the other 3 sites.  Would there be any caveats
> regarding international connections?  Again, everything works when
> connected to the 3Com equipment, it's only when we connect up the
> Cisco's that site 1 fails.
>
> Thanks for any input.
>
> Bob
>
> --
> Site 1 (This site works fine)
>
> Current configuration:
> !
> version 12.0
>
> ip subnet-zero
>
> interface Serial0/0
>  ip address x.x.53.26 255.255.255.252
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  no ip mroute-cache
>  no fair-queue
>  frame-relay interface-dlci ABC
> --
> Site 2 (This site does not come up)
>
> Current configuration:
> !
> version 12.0
>
> ip subnet-zero
>
> interface Serial0/0
>  ip address x.x.53.2 255.255.255.252
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  no ip mroute-cache
>  no fair-queue
>  frame-relay interface-dlci XYZ
> --
> Central Site
>
> Current configuration:
> version 12.0
>
> ip subnet-zero
>
> interface Serial5/1
>  no ip address
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf dead-interval 60
> !
> interface Serial5/1.1 point-to-point
>  ip address x.x.53.17 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  ipx network 92
>  frame-relay interface-dlci GHI
> !
> interface Serial5/1.2 point-to-point
>  ip address x.x.53.21 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  ipx network 54B
>  frame-relay interface-dlci DEF
> !
> interface Serial5/1.3 point-to-point
>  bandwidth 64000
>  ip address x.x.53.1 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  frame-relay interface-dlci XYZ
> !
> interface Serial5/1.4 point-to-point
>  bandwidth 64000
>  ip address x.x.53.25 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  frame-relay interface-dlci ABC
> --




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32319&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Vincent Miller

Is the last site by any chance through an NNI link ?
Have your tried frame-relay lmi-type ansi at both ends ?


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32326&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread John Neiberger

Are you positive you have the DLCI assignments the same as in the 3COM
router you replaced?

What do 'show frame map' and 'show frame pvc' look like?  Do you have
any PVCs that are UNUSED/INACTIVE?  

On the remote side that is UP/DOWN, do you see any incoming packets at
all or does it think the interface is up simply because DTR is high? 
What does show interface show on the remote side?  Equal numbers of LMI
enquiries sent compared to stats received?

Thanks,
John

>>> "Bob Timmons"  1/17/02 10:35:42 AM >>>
On S5/1 I get UP/UP.

On S5/1.4, I get UP/UP on our side and UP/UP on the remote side.
On S5/1.3 I get Down/Down on our side and Up/Down on their side.

> What do you mean, specifically?  Does the line protocol never come
up?
> Does the line protocol come up yet OSPF adjacencies do not form? 
Does
> the physical interface even come up?
>
> Thanks,
> John
>
> >>> "Bob Timmons"  1/17/02 9:22:54 AM >>>
> We're switching our routers from 3Com to Cisco and we're having
> trouble at one of our sites.  We've got a hub-and-spoke
configuration
> from our central site to 4 other sites.  3 of the sites come up when
> we switch the hardware to Cisco (simply moving the CSU from the 3Com
> router to the Cisco router), the 4th does not.  I'm including the
> Central Site config and 2 of the remotes (Site 1 comes up, Site 2
does
> not).
>
> We've changed out the router (including the serial ports), csu,
serial
> cable, rj45's, everything.  It's not a hardware problem.  We changed
> the CSU on the central site, just to see if it would help.  No go.
>
> Please let me know if you see something weird.
>
> I've replaced the DLCI #'s with letters, but they match up (i.e. if
> it's ABC in site 1, it matches to ABC in central site).  I didn't
> include configs for sites 3 & 4, but they're identical with the
> exception of the DLCI's and IP's.  (and they work as well).
>
> Something I had thought about... this site is in Canada and we're in
> the US as well as the other 3 sites.  Would there be any caveats
> regarding international connections?  Again, everything works when
> connected to the 3Com equipment, it's only when we connect up the
> Cisco's that site 1 fails.
>
> Thanks for any input.
>
> Bob
>
> --
> Site 1 (This site works fine)
>
> Current configuration:
> !
> version 12.0
>
> ip subnet-zero
>
> interface Serial0/0
>  ip address x.x.53.26 255.255.255.252
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  no ip mroute-cache
>  no fair-queue
>  frame-relay interface-dlci ABC
> --
> Site 2 (This site does not come up)
>
> Current configuration:
> !
> version 12.0
>
> ip subnet-zero
>
> interface Serial0/0
>  ip address x.x.53.2 255.255.255.252
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  no ip mroute-cache
>  no fair-queue
>  frame-relay interface-dlci XYZ
> --
> Central Site
>
> Current configuration:
> version 12.0
>
> ip subnet-zero
>
> interface Serial5/1
>  no ip address
>  no ip directed-broadcast
>  encapsulation frame-relay
>  ip ospf dead-interval 60
> !
> interface Serial5/1.1 point-to-point
>  ip address x.x.53.17 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  ipx network 92
>  frame-relay interface-dlci GHI
> !
> interface Serial5/1.2 point-to-point
>  ip address x.x.53.21 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  ipx network 54B
>  frame-relay interface-dlci DEF
> !
> interface Serial5/1.3 point-to-point
>  bandwidth 64000
>  ip address x.x.53.1 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  frame-relay interface-dlci XYZ
> !
> interface Serial5/1.4 point-to-point
>  bandwidth 64000
>  ip address x.x.53.25 255.255.255.252
>  no ip directed-broadcast
>  ip ospf network point-to-point
>  ip ospf dead-interval 60
>  frame-relay interface-dlci ABC
> --




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32328&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Terry Vore

Bob,,


You need to verify the LMI on the Canadian end...Cisco uses Strata 
(surprise) and Bell Canada uses Ansi or Annex A or Ddepends on where 
you are...I use to manage a network with several sites in the northland and 
we ran into this consistently. You can have different types of LMI in your 
network and it runs fine.

Terry Vore























At 11:22 AM 1/17/2002 -0500, you wrote:
>[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32337&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Bob Timmons

Thanks everyone for all the input... We're doing another test today at 4pm
(EST) so I'll get more info and I'll try using different lmi-types.  I seem
to remember trying ansi, but I'll give it another go and I'll document all
of the show frame map/pvc/etc in case it doesn't work again.  Am I correct
in assuming that the LMI is set only at the interface level and the
subinterfaces will get it from the interface?

> Bob,,
>
>
> You need to verify the LMI on the Canadian end...Cisco uses Strata
> (surprise) and Bell Canada uses Ansi or Annex A or Ddepends on where
> you are...I use to manage a network with several sites in the northland
and
> we ran into this consistently. You can have different types of LMI in your
> network and it runs fine.
>
> Terry Vore
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 11:22 AM 1/17/2002 -0500, you wrote:
> >[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32344&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread John Neiberger

Yes, the LMI is set at the interface level.  However, since you're using
12.0 the router should auto-detect the LMI type. 

John

>>> "Bob Timmons"  1/17/02 12:59:25 PM >>>
Thanks everyone for all the input... We're doing another test today at
4pm
(EST) so I'll get more info and I'll try using different lmi-types.  I
seem
to remember trying ansi, but I'll give it another go and I'll document
all
of the show frame map/pvc/etc in case it doesn't work again.  Am I
correct
in assuming that the LMI is set only at the interface level and the
subinterfaces will get it from the interface?

> Bob,,
>
>
> You need to verify the LMI on the Canadian end...Cisco uses Strata
> (surprise) and Bell Canada uses Ansi or Annex A or Ddepends on
where
> you are...I use to manage a network with several sites in the
northland
and
> we ran into this consistently. You can have different types of LMI in
your
> network and it runs fine.
>
> Terry Vore
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 11:22 AM 1/17/2002 -0500, you wrote:
> >[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32349&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Terry Vore

Well, the sub-interfaces do not need the LMI, it is only used to report the 
information about the dlci's to the interfaceactually I have turned off 
the keepalives in a lab environment and still pass traffic to a frame 
switch.keepalives =LMI for CiscoThe other thing is to be sure of the 
type of FrameRelay encapsulationCisco or RFC1490Cisco routers 
default to CiscoThis is set at the dlci level


Terry Vore



At 02:59 PM 1/17/2002 -0500, you wrote:
>Thanks everyone for all the input... We're doing another test today at 4pm
>(EST) so I'll get more info and I'll try using different lmi-types.  I seem
>to remember trying ansi, but I'll give it another go and I'll document all
>of the show frame map/pvc/etc in case it doesn't work again.  Am I correct
>in assuming that the LMI is set only at the interface level and the
>subinterfaces will get it from the interface?
>
> > Bob,,
> >
> >
> > You need to verify the LMI on the Canadian end...Cisco uses Strata
> > (surprise) and Bell Canada uses Ansi or Annex A or Ddepends on where
> > you are...I use to manage a network with several sites in the northland
>and
> > we ran into this consistently. You can have different types of LMI in
your
> > network and it runs fine.
> >
> > Terry Vore
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > At 11:22 AM 1/17/2002 -0500, you wrote:
> > >[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32356&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread [EMAIL PROTECTED]

You are correct, the LMI is set at the interface level.
One command that I don't think has been mentioned is 'debug frame-relay 
lmi'.  It's pretty safe for a debug command - it shows you what is 
happening between your router and the frame switch.  You should see status 
enquiries and status messages every 10 seconds, and every 60 seconds a 
list of PVCs known by the switch, and their status.  The 10 sec/60sec 
might vary depending on switch type - I'm not sure.

JMcL 

- Forwarded by Jenny Mcleod/NSO/CSDA on 18/01/2002 08:48 am -


"Bob Timmons" 
Sent by: [EMAIL PROTECTED]
18/01/2002 06:59 am
Please respond to "Bob Timmons"

 
To: [EMAIL PROTECTED]
    cc: 
    Subject:Re: Frame-Relay problem - 3Com to Cisco (long)
[7:32307]


Thanks everyone for all the input... We're doing another test today at 4pm
(EST) so I'll get more info and I'll try using different lmi-types.  I 
seem
to remember trying ansi, but I'll give it another go and I'll document all
of the show frame map/pvc/etc in case it doesn't work again.  Am I correct
in assuming that the LMI is set only at the interface level and the
subinterfaces will get it from the interface?

> Bob,,
>
>
> You need to verify the LMI on the Canadian end...Cisco uses Strata
> (surprise) and Bell Canada uses Ansi or Annex A or Ddepends on where
> you are...I use to manage a network with several sites in the northland
and
> we ran into this consistently. You can have different types of LMI in 
your
> network and it runs fine.
>
> Terry Vore
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 11:22 AM 1/17/2002 -0500, you wrote:
> >[EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32366&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Frame-Relay problem - 3Com to Cisco (long) [7:32307]

2002-01-17 Thread Bob Timmons

Ok, success!  Well, it turns out, we had a bad CSU.  Strange thing, though.
It worked ok on the 3Com equipment and last time we did testing, we put the
CSU on the Cisco and it didn't work.  We put it back on the 3Com and it
worked fine.  This time, we couldn't get it to work on the Cisco, tried
putting it back and it died.  We configured (yet) another CSU and up it
came.  I guess you can never try enough hardware sometimes.  Thanks for all
the input.  It's much appreciated.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=32402&t=32307
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]