GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: Please confirm (conf#191c2d33bfbe1144e09f5b06a1286340) posted 10/23/2002
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


----- Original Message -----
From: <ccielab@xxxxxxxxxxxxxx>
To: <bbonham@xxxxxxxxx>
Sent: Wednesday, October 23, 2002 1:23 PM
Subject: Please confirm (conf#191c2d33bfbe1144e09f5b06a1286340)


> Hi,
>
> You have tried to post to GroupStudy.com's CCIELab mailing list. Because
the
> server does not recognize you as a confirmed poster, you will be required
to
> authenticate that you are using a valid e-mail address and are not a
> spammer.
>
> PLEASE DO NOT SEND YOUR ORIGINAL MESSAGE AGAIN!  BY CONFIRMING THIS EMAIL
> YOUR ORIGINAL MESSAGE (WHICH IS NOW QUEUED IN THE SERVER) WILL BE POSTED.
>
> By confirming this e-mail you certify that you understand the following:
>
> 1. The message does NOT break Cisco's Non-Disclosure requirements.
>
> 2. The message is NOT designed to advertise a commercial product.
>
> 3. All postings become property of GroupStudy.com
>
> 4. You have searched the archives prior to posting.
>
> 5. The message is NOT inflammatory.
>
> 6. The message is NOT a test message.
>
> To confirm, simply reply to this message.  No editing is necessary.  Once
> confirmed, you will be able to post without additional confirmations.
>
>
> Welcome to GroupStudy.com!
>
>
> ------ORIGINAL MESSAGE---------
>
> >From bbonham@xxxxxxxxx  Wed Oct 23 19:23:54 2002
> Received: from malone.cisco.com (malone.cisco.com [171.70.157.157])
> by groupstudy.com (8.9.3/8.9.3) with ESMTP id TAA07106
> GroupStudy Mailer; Wed, 23 Oct 2002 19:23:53 GMT
> Received: from MURCIS3696 (conv-ut-tac-106-245.cisco.com [172.30.106.245])
by malone.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id
MAA16475; Wed, 23 Oct 2002 12:23:14 -0700 (PDT)
> Message-ID: <002001c27ac9$a2090330$f56a1eac@xxxxxxxxxxxxxxxxxxxxx>
> From: "Brad Bonham" <bbonham@xxxxxxxxx>
> To: "Larson, Chris" <CLarson@xxxxxxxxx>,
>         "'Paglia, John \(USPC.PCT.Hopewell\)'" <JPaglia@xxxxxxxxxxxxx>,
>         "'enginedrive2002'" <enginedrive2002@xxxxxxxx>,
>         <ccielab@xxxxxxxxxxxxxx>
> References: <2FE42126333DD411BC8200508BDF58F807052298@xxxxxxxxxxxxxxxxxx
v>
> Subject: Re: DDR question.
> Date: Wed, 23 Oct 2002 13:23:12 -0600
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook Express 5.50.4807.1700
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
>
> A good link on demand circuit
> http://www.cisco.com/warp/public/104/dcprob.html
>
> ----- Original Message -----
> From: "Larson, Chris" <CLarson@xxxxxxxxx>
> To: "'Paglia, John (USPC.PCT.Hopewell)'" <JPaglia@xxxxxxxxxxxxx>;
> "'enginedrive2002'" <enginedrive2002@xxxxxxxx>; <ccielab@xxxxxxxxxxxxxx>
> Sent: Wednesday, October 23, 2002 1:00 PM
> Subject: RE: DDR question.
>
>
> > If periodic hello's and lsa's are suppressed so they do not flood the
> demand
> > circuit.  AND
> >
> > "only periodic hellos and refreshes of LSA's once the call is made"
> >
> > Then why is the 101 list needed? It says that hello's and lsa's will not
> be
> > sent until after the call is made? Why do you need to supress them
twice?
> >
> >
> >
> > > -----Original Message-----
> > > From: Paglia, John (USPC.PCT.Hopewell) [SMTP:JPaglia@xxxxxxxxxxxxx]
> > > Sent: Wednesday, October 23, 2002 2:08 PM
> > > To: 'enginedrive2002'; ccielab@xxxxxxxxxxxxxx
> > > Subject: RE: DDR question.
> > >
> > > The definition of 'demand-circuit' as per the 12.1 cmd. ref.:
> > > Periodic hellos are suppressed and periodic refreshes of LSAs do not
> flood
> > > the demand circuit. It allows the underlying datalink layer to be
closed
> > > when the topology is stable.
> > > ...only periodic hellos and refreshes of LSA's once the call is made.
> > > Thus,
> > > you put the 'deny ospf any any' cmd. in to keep hello's from acting as
> the
> > > 'interesting traffic' that can initialize a link. Once non-ospf
traffic
> > > brings up the link, demand-circuit kicks in.
> > >
> > > Here's the link:
> > >
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip
> > > _r
> > > /iprprt2/1rdospf.htm#xtocid19
> > > Watch the wrap!!!
> > >
> > > John
> > >
> > > > -----Original Message-----
> > > > From: enginedrive2002 [SMTP:enginedrive2002@xxxxxxxx]
> > > > Sent: Wednesday, October 23, 2002 12:51 PM
> > > > To: ccielab@xxxxxxxxxxxxxx
> > > > Subject: DDR question.
> > > >
> > > > Would someone read the doc link below, and answer a few questions:
> > > > http://www.cisco.com/warp/public/129/config-bri-map.html
> > > >
> > > > 1. On router maui-soho-01, "ip ospf demand-circuit" is configured
> under
> > > > BRI
> > > > interface, why in the example, access-list 101 still need to have
> "deny
> > > > ospf
> > > > any any"? I have never test OSPF demand-circuit at before, but I
> "guess"
> > > > with
> > > > the "ip ospf demand-circuit" command, it will already suppress the
> hello
> > > > packets. Would someone confirm this?
> > > >
> > > > 2. On router maui-nas-05, under BRI interface, the example doesn't
> > > > configure
> > > > any number to dial, which mean it could only answer the call. But
why
> in
> > > > the
> > > > example, it has "dialer-group", "dialer-list" command to define
> > > > interesting
> > > > traffic? Just to reset the idle-timer while the BRI link is up? Any
> > > other
> > > > purpose here?
> > > >
> > > > Thank you!
> > > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > > E.D.