From: Nigel.Johnson@barclayscapital.com
Date: Wed Jun 23 2004 - 12:52:06 GMT-3
Thanks for that Brian. I was getting my PPP confused with Point-to-Point and
Point-to-Multipoint OSPF stuff - there's just too may P's!!!
I was looking at OSPF demand circuits at the time and how the 32-bit host
route you get on a ISDN circuit running PPP can cause the ISDN to flap if
you're redistributing between OSPF and RIP on the same router under certain
conditions, and how 'no peer neighbor-route' can cure this.
That's my excuse anyway and I'm sticking to it! ;)
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: 23 June 2004 16:32
To: Nigel.Johnson@barclayscapital.com; chenleish@online.sh.cn;
ccielab@groupstudy.com
Subject: RE: questions
Nigel,
The /32 route generated from the "peer neighbor-route" command and
the /32 generated from the OSPF point-to-multipoint network type have
nothing to do with each other.
Here is part of an earlier e-mail I sent about the peer neighbor-route
command:
<quote>
The "peer neighbor-route" command is normally used for unnumbered IP links.
If a link is unnumbered, a route will be needed in order to reach the remote
side's IP address. This "peer neighbor-route" command is how a route to the
remote end is created. If you disable the "peer neighbor-route" command on
an unnumbered link, a static route will normally be needed to reach the
remote end.
For someone to get an understanding of the "peer neighbor-route" command and
how it's used in a real network, try enabling PPP on a serial link between
two routers. Use IP unnumbered for the serial addressing based off of each
respective router's loopback interface. Then ping the remote end's
loopback. Now do the "no peer neighbor-route" command on each side of the
link and 'bounce' (shut/no shut) the interface. Try to ping the remote
end's loopback to see the benefit of having the "peer neighbor-route"
command enabled. </quote>
As far as the /32 from OSPF when using the point-to-multipoint network type,
here is the section of the RFC that explains it:
<rfc2328>
12.4.1.4. Describing Point-to-MultiPoint interfaces
For operational Point-to-MultiPoint interfaces, one or
more link descriptions are added to the router-LSA as
follows:
o A single Type 3 link (stub network) is added with
Link ID set to the router's own IP interface
address, Link Data set to the mask 0xffffffff
(indicating a host route), and cost set to 0.
</rfc2328>
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com Internetwork Expert, Inc.
http://www.InternetworkExpert.com Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Nigel.Johnson@barclayscapital.com
Sent: Wednesday, June 23, 2004 3:48 AM
To: chenleish@online.sh.cn; ccielab@groupstudy.com
Subject: RE: questions
A1. I've not tried it but ip think 'no peer neighbor-route' may remove it.
A2. I don't believe it is -
http://www.cisco.com/warp/public/625/ccie/rs/lab_exam_blueprint.html
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of cl
Sent: 23 June 2004 07:01
To: ccielab@groupstudy.com
Subject: questions
1!" when i enable ospf on the frame-relay interface,and the interface use
"ip ospf network p2mp" ,it will generate the interface address as a /32
route in routing table , how to get rid of it?
2!"is IPSEC include in the R&S lab ?
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:49 GMT-3