From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Tue Jan 17 2006 - 17:55:19 GMT-3
Thanks, Chris. I always like to know why something works the way it does,
rather than just knowing what buttons to push. I appreciate the review.
Dave
-----Original Message-----
From: Chris Lewis
To: Schulz, Dave
Cc: ccielab@groupstudy.com
Sent: 1/17/2006 1:37 PM
Subject: Re: PPP frame config
Just the way the code is written. It is always safest to build something
(like a virtual template) before it is referenced by a configuration
command. Otherwise you are entering a configuration command that cannot
work, then going back and trying to fix it by creating the referenced
entity. Not all software copes with that sort of thing equally well.
Chris
On 1/16/06, Schulz, Dave <DSchulz@dpsciences.com
<mailto:DSchulz@dpsciences.com> > wrote:
Wow! I didn't realize that....that is EXACTLY what it was, and
everything is working. Thanks, Chris! Any thoughts on WHY the order is
important here?
Dave
-----Original Message-----
From: Chris Lewis
To: Schulz, Dave
Cc: ccielab@groupstudy.com <mailto:ccielab@groupstudy.com>
Sent: 1/16/2006 8:27 PM
Subject: Re: PPP frame config
Did yo ucreate the cirtual-template first? If not teh order of
operations can mess things up. A reload may fix it.
Chris
On 1/16/06, Schulz, Dave < <mailto:DSchulz@dpsciences.com>
DSchulz@dpsciences.com
<mailto:DSchulz@dpsciences.com <mailto:DSchulz@dpsciences.com> > >
wrote:
Here is a little different issue that I am having on a configuration on
a multipoint frame with PPP and OSPF. R1 is the hub with the spokes
being R2 and R3. The strange thing about this one is that the network
advertised on R2 is seen on R3, but not on R1. I can't seem to find any
reason why this is occurring in the config, and the OSPF relationships
appear to be forming correctly (see below). Thoughts?
Here are the configs:
R1:
!
interface Serial0/0
no ip address
encapsulation frame-relay
frame-relay lmi-type ansi
!
interface Serial0/0.1 multipoint
frame-relay interface-dlci 102 ppp Virtual-Template1
frame-relay interface-dlci 103 ppp Virtual-Template1
no frame-relay inverse-arp
!
interface Virtual-Template1
ip address <http://172.16.123.1 <http://172.16.123.1/> > 172.16.123.1
<http://172.16.123.1/> <http://255.255.255.0/> 255.255.255.0
<http://255.255.255.0 <http://255.255.255.0/> >
!
router ospf 1
network <http://172.16.123.0/> 172.16.123.0 <http://172.16.123.0
<http://172.16.123.0/> > <http://0.0.0.255/> 0.0.0.255
<http://0.0.0.255 <http://0.0.0.255/> >
area 0
R2:
interface Loopback0
ip address 22.2.2.2 <http://22.2.2.2/> <http://22.2.2.2
<http://22.2.2.2/> > 255.255.255.0 <http://255.255.255.0/>
< <http://255.255.255.0/> http://255.255.255.0>
!
interface Virtual-Template1
ip address 172.16.123.2 <http://172.16.123.2/> < <http://172.16.123.2/>
http://172.16.123.2> <http://255.255.255.0 <http://255.255.255.0/> >
<http://255.255.255.0/> 255.255.255.0
!
interface Serial0
no ip address
encapsulation frame-relay
frame-relay interface-dlci 201 ppp Virtual-Template1
no frame-relay inverse-arp
frame-relay lmi-type ansi
!
router ospf 1
log-adjacency-changes
redistribute connected metric 3 metric-type 1 subnets route-map LOOP
network 172.16.123.0 <http://172.16.123.0/> <http://172.16.123.0
<http://172.16.123.0/> > <http://0.0.0.255/> 0.0.0.255
<http://0.0.0.255 <http://0.0.0.255/> >
area 0
!
route-map LOOP permit 10
match interface Loopback0
!
route-map LOOP permit 20
!
R3:
!
interface Virtual-Template1
ip address 172.16.123.3 <http://172.16.123.3/> <http://172.16.123.3
<http://172.16.123.3/> > <http://255.255.255.0/> 255.255.255.0
<http://255.255.255.0 <http://255.255.255.0/> >
!
interface Serial0
no ip address
encapsulation frame-relay
frame-relay interface-dlci 301 ppp Virtual-Template1
no frame-relay inverse-arp
frame-relay lmi-type ansi
!
interface Serial1
no ip address
shutdown
!
router ospf 1
log-adjacency-changes
network 172.16.123.0 <http://172.16.123.0/> < <http://172.16.123.0/>
http://172.16.123.0> 0.0.0.255 <http://0.0.0.255/> <
<http://0.0.0.255/> http://0.0.0.255>
area 0
R1.....
R1#sh ip ospf nei
Neighbor ID Pri State Dead Time Address
Interface
<http://172.16.123.3/> 172.16.123.3 <http://172.16.123.3
<http://172.16.123.3/> > 0 FULL/ - 00:00:38
<http://172.16.123.3/> 172.16.123.3 <http://172.16.123.3
<http://172.16.123.3/> >
Virtual-Access3
<http://172.16.123.2/> 172.16.123.2 <http://172.16.123.2
<http://172.16.123.2/> > 0 FULL/ - 00:00:39
<http://172.16.123.2/> 172.16.123.2 <http://172.16.123.2
<http://172.16.123.2/> >
Virtual-Access1
Dave Schulz,
Email: <mailto:dschulz@dpsciences.com> dschulz@dpsciences.com
<mailto:dschulz@dpsciences.com <mailto:dschulz@dpsciences.com> >
< <mailto:dschulz@dpsciences.com+%3Cmailto:dschulz@dpsciences.com>
mailto:dschulz@dpsciences.com > >
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3