RE: Encapsulation Failed [7:31916]

2002-01-16 Thread Fraasch James
I will post an answer as soon I can come up with one. We will just have to see how good the Cisco TAC is! Thanks again for all the information. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=32176&t=31916 -- FAQ, list archives, a

RE: Encapsulation Failed [7:31916]

2002-01-15 Thread [EMAIL PROTECTED]
(MTU 1500) to an HSSI (default MTU 4470 I think - not 1500, anyway). JMcL - Forwarded by Jenny Mcleod/NSO/CSDA on 16/01/2002 08:34 am - Jenny Mcleod 15/01/2002 03:30 pm To: [EMAIL PROTECTED] cc: Subject: RE: Encapsulation Failed [7:31916] Actually,

RE: Encapsulation Failed [7:31916]

2002-01-15 Thread Lupi, Guy
Oppenheimer [mailto:[EMAIL PROTECTED]] ~Sent: Tuesday, January 15, 2002 2:01 PM ~To: [EMAIL PROTECTED] ~Subject: Re: Encapsulation Failed [7:31916] ~ ~ ~At 11:35 AM 1/15/02, Fraasch James wrote: ~>First, thanks for all the information. I forgot to mention ~that when I did ~>a Show ip int b

RE: Encapsulation Failed [7:31916]

2002-01-15 Thread Lupi, Guy
I have had strange problems like this before, but nothing exactly like this. The hellos should be sent by each router as a keepalive method on point to point lines, as well as to verify area id, subnet mask on the interface, authentication, hello interval and so on, and you should see the state tr

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread Priscilla Oppenheimer
At 11:35 AM 1/15/02, Fraasch James wrote: >First, thanks for all the information. I forgot to mention that when I did >a Show ip int brief I saw up and up. Next, here is some pertinent >configuration information: > >Interface Serial 2/5 >mtu 2044 That's kind of a strange MTU. What is the oth

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread s vermill
Fraasch James wrote: > > First, thanks for all the information. I forgot to mention > that when I did a Show ip int brief I saw up and up. Next, here > is some pertinent configuration information: > > Interface Serial 2/5 >mtu 2044 >ip address 172.25.x.x 255.255.255.252 >encapsulati

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread s vermill
Paul Borghese wrote: > > You should be able to use the QUOTE button on the website to to > quote the > message. Please tell me if this is broken as I have been > upgrading the > internals of the website and may have missed a bug. > > Thanks! > > Paul Paul, You just can't teach us newbies an

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread Fraasch James
First, thanks for all the information. I forgot to mention that when I did a Show ip int brief I saw up and up. Next, here is some pertinent configuration information: Interface Serial 2/5 mtu 2044 ip address 172.25.x.x 255.255.255.252 encapsulation ppp ipx network B051 ipx update

RE: Encapsulation Failed [7:31916]

2002-01-15 Thread s vermill
>Unfortunately I can't find a debug to tell that my Hellos are >multicast >rather than unicast. I guess I'll have to wait until Priscilla >ponies up the >$ for a WAN sniffer. :) Chris, Since you are in a lab environment, you can turn on 'debug ip packet' and see the destination address of 224.

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread Paul Borghese
y 15, 2002 10:41 AM Subject: Re: Encapsulation Failed [7:31916] > >Well, that does make sense, now that you mention it. (OSPF sending > >multicast Hellos on a serial interface). OSPF uses Hellos as a >keepalive, > >not just for establishing adjacencies. > > >Notic

RE: Encapsulation Failed [7:31916]

2002-01-15 Thread Kane, Christopher A.
wait until Priscilla ponies up the $ for a WAN sniffer. :) Chris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 10:44 PM To: [EMAIL PROTECTED] Subject: RE: Encapsulation Failed [7:31916] At 10:04 PM 1/14/02, Kane, Christopher A. wro

Re: Encapsulation Failed [7:31916]

2002-01-15 Thread s vermill
>Well, that does make sense, now that you mention it. (OSPF sending >multicast Hellos on a serial interface). OSPF uses Hellos as a >keepalive, >not just for establishing adjacencies. >Notice, that your reply is still hard to read because we can't tell >what >you wrote and what I wrote. But i

RE: Encapsulation Failed [7:31916]

2002-01-14 Thread [EMAIL PROTECTED]
ed lines. JMcL "Kane, Christopher A." Sent by: [EMAIL PROTECTED] 15/01/2002 02:04 pm Please respond to "Kane, Christopher A." To: [EMAIL PROTECTED] cc: Subject:RE: Encapsulation Failed [7:31916] Yes, OSPF sends hellos on Serial interface

RE: Encapsulation Failed [7:31916]

2002-01-14 Thread Priscilla Oppenheimer
hat lately. > >Chris > >-Original Message- >From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 14, 2002 8:40 PM >To: [EMAIL PROTECTED] >Subject: Re: Encapsulation Failed [7:31916] > > >At 07:57 PM 1/14/02, s vermill wrote: > >Priscill

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread Priscilla Oppenheimer
Well, that does make sense, now that you mention it. (OSPF sending multicast Hellos on a serial interface). OSPF uses Hellos as a keepalive, not just for establishing adjacencies. Notice, that your reply is still hard to read because we can't tell what you wrote and what I wrote. But if you're

RE: Encapsulation Failed [7:31916]

2002-01-14 Thread Kane, Christopher A.
"Full" as on a broadcast medium. I'd need someone else to chime in on point-to-multipoint as I haven't configured that lately. Chris -Original Message- From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] Sent: Monday, January 14, 2002 8:40 PM To: [EMAIL PROTECTE

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread s vermill
>Good question. The IBM 6611 does bridging for one thing. The other >hint was >that it was attempting to send an OSPF Hello on a serial interface. >Does >OSPF do that? How does it establish adjacency to a neighbor router >on a >WAN? On a point-to-point network, I figured it just knew who its >ne

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread s vermill
Good question. The IBM 6611 does bridging for one thing. The other hint was that it was attempting to send an OSPF Hello on a serial interface. Does OSPF do that? How does it establish adjacency to a neighbor router on a WAN? On a point-to-point network, I figured it just knew who its neighbor

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread Priscilla Oppenheimer
At 07:57 PM 1/14/02, s vermill wrote: >Priscilla, > >May I ask what led you to believe that bridging was involved as opposed to >just assuming that the source address was the Cisco router itself? Good question. The IBM 6611 does bridging for one thing. The other hint was that it was attempting t

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread s vermill
Priscilla, May I ask what led you to believe that bridging was involved as opposed to just assuming that the source address was the Cisco router itself? Just as an opportunity to learn something. Regards, Scott Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=31924&t=31916 --

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread Priscilla Oppenheimer
At 05:45 PM 1/14/02, Fraasch James wrote: >I ran into a problem this weekend. I have a 7204 on one end and an IBM 6611 >on the other of a point to point T-1. IBM requires PPP encapsulation. I >debugged and got the following: > >*Jan 12 02:57:19.231: IP: s=172.25.137.201 (local), d=224.0.0.5 (Ser

Re: Encapsulation Failed [7:31916]

2002-01-14 Thread John Neiberger
Can we see the relevant portions of the config plus output from 'show int'? Thanks, John >>> "Fraasch James" 1/14/02 3:45:41 PM >>> I ran into a problem this weekend. I have a 7204 on one end and an IBM 6611 on the other of a point to point T-1. IBM requires PPP encapsulation. I debugged and