From: Scott Morris (smorris@xxxxxxxx)
Date: Sun Apr 09 2000 - 11:44:08 GMT-3
With RIP broadcasting every 30 seconds, and his dialer timeout time of 300
seconds, even if it misses the first RIP packet, I wouldn't see any problem
in timing...
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
LASSERRE Grégory
Sent: Sunday, April 09, 2000 7:23 AM
To: 'Derek Small (Fuse)'; ccielab@groupstudy.com
Subject: RE: Problem with snapshot routing.
Hi Derek,
i've not looked up your config files on the web (no access actually)
however if i understand well your problem, here is what i think :
between the time the call is solicited by the rip packets and the time
the ISDN line goes up, the RIP packet is lost.
To solve this problem :
dialer hold-queue 50 (per. example)
to configure on BRI interface (or dialer interface if you have one).
Best regards.
Greg.
> -----Message d'origine-----
> De: Derek Small (Fuse) [SMTP:dwsmall@fatkid.com]
> Date: dimanche 9 avril 2000 00:36
> À: ccielab@groupstudy.com
> Objet: Problem with snapshot routing.
>
> Ok I have a challenge for everyone. The first person to solve this one
> gets
> a free time slot on Fatkid.com.
>
> The solution for the SnapShot routing scenario is broken. The server
> router, R2, is not sending or receiving RIP updates when snapshot brings
> the
> BRI up. What is wrong?
>
> Hint, I have removed the dialer option from the "snapshot server 5"
> command
> under the BRI, that didn't do it.
>
> The first person to post the correct config for R2 and R3 wins!
>
>
> Derek Small
> dwsmall@fatkid.com
>
>
> ----- Original Message -----
> From: Richard Wagner <rfwagner@hotmail.com>
> To: <obuba@bellatlantic.net>; <ccielab@groupstudy.com>
> Sent: Thursday, April 06, 2000 9:52 PM
> Subject: Re: trace message
>
>
> > That is a host unreachable.
> >
> > Check this link!
> >
> http://cco.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/fun
> _r
> /frprt3/frtroubl.htm#16344
> >
> > Here's a section of:
> >
> http://www.cisco.com/cpress/cc/td/cpress/fund/ith2nd/it2430.htm#xtocid1376
> 71
> 3
> >
> > Destination-unreachable messages include four basic types: network
> > unreachable, host unreachable, protocol unreachable, and port
> unreachable.
> >
> > Network-unreachable messages usually mean that a failure has occurred in
> the
> > routing or addressing of a packet.
> >
> > Host-unreachable messages usually indicates delivery failure, such as a
> > wrong subnet mask.
> >
> > Protocol-unreachable messages generally mean that the destination does
> not
> > support the upper-layer protocol specified in the packet.
> >
> > Port-unreachable messages imply that the TCP socket or port is not
> > available.
> >
> > An ICMP echo-request message, which is generated by the ping command, is
> > sent by any host to test node reachability across an internetwork. The
> ICMP
> > echo-reply message indicates that the node can be successfully reached.
> >
> >
> >
> >
> > >From: "Nnanna Obuba" <obuba@bellatlantic.net>
> > >Reply-To: "Nnanna Obuba" <obuba@bellatlantic.net>
> > >To: <ccielab@groupstudy.com>
> > >Subject: trace message
> > >Date: Thu, 6 Apr 2000 21:21:03 -0400
> > >
> > >Hi all,
> > >
> > >Can anyone please tell me what the H means when you are trying to trace
> a
> > >route
> > >ie
> > >
> > >Type escape sequence to abort.
> > >Tracing the route to 20.1.1.1
> > >
> > > 1 10.10.1.1 28 msec 28 msec 28 msec
> > > 2 10.10.1.1 !H * !H
> > >
> > >
> > >TIA
> > >
> > >Nnanna
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:13 GMT-3