From: sanjay (ccienxtyear@xxxxxxxxxxx)
Date: Sat May 26 2001 - 21:16:57 GMT-3
Thanks for the Tip Walter, You were right. I needed to enable authentication
on the Virtual link.
-sanjay
----- Original Message -----
From: "Walter Chen" <wchen@iloka.com>
To: "'sanjay'" <ccienxtyear@hotmail.com>; <ccielab@groupstudy.com>
Sent: Friday, May 25, 2001 1:10 PM
Subject: RE: PPP Encapsulation and OSPF
> The /32 routes should go away after you put "no peer nei" command. Do a
> "clear ip rout *" and see what happens.
>
> Area 2 virtual link has to be authenticated since you enabled
authentication
> for area 0. That's why you do not see .59.116/30 on R4. Remember the
> virtual link belongs to area 0 since you use it to link area 3 to area 0.
> Do not get confused by the command "area 2 vir" which just means the
virtual
> link goes across area 2.
>
> Walter
>
> -----Original Message-----
> From: sanjay [mailto:ccienxtyear@hotmail.com]
> Sent: Friday, May 25, 2001 3:46 PM
> To: Walter Chen; 'Pickell, Aaryn'; ccielab@groupstudy.com
> Subject: Re: PPP Encapsulation and OSPF
>
>
> Sorry to say this, but the 'no peer neighbor-route' command didn't work. I
> have the configs of both routers below and also the routing table of both
> routers. Also R4 doesn't have the route to 172.17.59.117 network thats
> configured on a Token Ring interface on R2, and R2 is not learning any
> routes to other routers except the Token Ring network thats on R4. Any
ideas
> what could be going on. It's got me running in cricles. Both routers are
> connected back to back via serial and R4 is connected to the Frame cloud.
R2
> Token Ring is in Area 3, and the S0 interface in Area 2. R4 Token Ring and
> S0 interface is in Area 2. The Frame Relay interface is in Area 0. Any
> feedback is appreciated. Could be something very simple that I have
> overlooked.
>
>
> r4#sh run
> Building configuration...
>
> Current configuration:
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname r4
> !
> enable password cisco
> !
> ip subnet-zero
> no ip domain-lookup
> !
> !
> !
> !
> interface Ethernet0
> ip address 172.17.59.73 255.255.255.252
> no ip directed-broadcast
> shutdown
> media-type 10BaseT
> !
> interface E
> no ip address
> no ip directed-broadcast
> shutdown
> media-type 10BaseT
> !
> interface Serial0
> ip address 172.17.59.166 255.255.255.248
> no ip directed-broadcast
> encapsulation ppp
> no ip mroute-cache
> no peer neighbor-route
> no fair-queue
> !
> interface Serial1
> no ip address
> no ip directed-broadcast
> encapsulation frame-relay IETF
> !
> interface Serial1.100 point-to-point
> ip address 172.17.59.2 255.255.255.240
> no ip directed-broadcast
> ip ospf message-digest-key 10 md5 cisco
> ip ospf network broadcast
> no arp frame-relay
> frame-relay interface-dlci 100
> !
> interface TokenRing0
> ip address 172.17.59.90 255.255.255.248
> no ip directed-broadcast
> ring-speed 4
> !
> interface TokenRing1
> no ip address
> no ip directed-broadcast
> shutdown
> !
> router ospf 100
> network 172.17.59.0 0.0.0.15 area 0
> network 172.17.59.88 0.0.0.7 area 2
> network 172.17.59.160 0.0.0.7 area 2
> area 0 authentication message-digest
> area 2 virtual-link 172.17.59.165
> !
> ip classless
> !
> !
> !
> line con 0
> exec-timeout 60 0
> transport input none
> line aux 0
> line vty 0 4
> login
> !
> end
>
> r4#sh ip rou
> Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
> default
> U - per-user static route, o - ODR
> T - traffic engineered route
>
> Gateway of last resort is not set
>
> 172.17.0.0/16 is variably subnetted, 5 subnets, 4 masks
> C 172.17.59.165/32 is directly connected, Serial0
> C 172.17.59.160/29 is directly connected, Serial0
> C 172.17.59.0/28 is directly connected, Serial1.100
> C 172.17.59.88/29 is directly connected, TokenRing0
> O IA 172.17.59.100/30 [110/74] via 172.17.59.1, 00:09:16, Serial1.100
>
>
>
> r2#sh run
> Building configuration...
>
> Current configuration:
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname r2
> !
> enable password cisco
> !
> ip subnet-zero
> no ip domain-lookup
> !
> !
> !
> !
> interface Ethernet0
> no ip address
> no ip directed-broadcast
> shutdown
> media-type 10BaseT
> !
> interface Ethernet1
> no ip address
> no ip directed-broadcast
> shutdown
> media-type 10BaseT
> !
> interface Serial0
> ip address 172.17.59.165 255.255.255.248
> no ip directed-broadcast
> encapsulation ppp
> no ip mroute-cache
> no peer neighbor-route
> clockrate 64000
> !
> interface Serial1
> no ip address
> no ip directed-broadcast
> shutdown
> !
> interface Serial2
> no ip address
> no ip directed-broadcast
> shutdown
> !
> interface Serial3
> no ip address
> no ip directed-broadcast
> shutdown
> !
> interface TokenRing0
> ip address 172.17.59.117 255.255.255.252
> no ip directed-broadcast
> ring-speed 4
> !
> interface TokenRing1
> no ip address
> no ip directed-broadcast
> shutdown
> !
> router ospf 100
> network 172.17.59.116 0.0.0.3 area 3
> network 172.17.59.160 0.0.0.7 area 2
> area 2 virtual-link 172.17.59.166
> !
> ip classless
> !
> !
> !
> line con 0
> exec-timeout 60 0
> transport input none
> line aux 0
> line vty 0 4
> login
> !
> end
>
> r2#
> r2#sh ip rou
> Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
> default
> U - per-user static route, o - ODR
> T - traffic engineered route
>
> Gateway of last resort is not set
>
> 172.17.0.0/16 is variably subnetted, 4 subnets, 3 masks
> C 172.17.59.166/32 is directly connected, Serial0
> C 172.17.59.160/29 is directly connected, Serial0
> O 172.17.59.88/29 [110/89] via 172.17.59.166, 00:06:09, Serial0
> C 172.17.59.116/30 is directly connected, TokenRing0
> r2#
>
>
>
>
>
> ----- Original Message -----
> From: "Walter Chen" <wchen@iloka.com>
> To: "'Pickell, Aaryn'" <Aaryn.Pickell@getronics.com>; "'sanjay'"
> <ccienxtyear@hotmail.com>; <ccielab@groupstudy.com>
> Sent: Friday, May 25, 2001 11:54 AM
> Subject: RE: PPP Encapsulation and OSPF
>
>
> > Aaryn was right that PPP will always install a host route of the other
> side
> > of the serial (or ISDN) link and "no peer nei" command can remove this
> > route. This is because PPP is, after all, a point-to-point protocol.
The
> > host route guarantees connectivity between the end points of the link,
no
> > matter what address you put there. One side can be 10.1.1.1/24 and the
> other
> > side can be 200.2.2.2/28 and you can still ping each other. Of course,
no
> > dynamic routing protocol will work across this link.
> >
> > Walter
> >
> > -----Original Message-----
> > From: Pickell, Aaryn [mailto:Aaryn.Pickell@getronics.com]
> > Sent: Friday, May 25, 2001 2:40 PM
> > To: 'sanjay'; ccielab@groupstudy.com
> > Subject: RE: PPP Encapsulation and OSPF
> >
> >
> > This isn't to do with OSPF. PPP will automatically install a host route
> for
> > the IP address of the other side of the link. Switching to HDLC doesn't
> do
> > this.
> >
> > You can use "no peer neighbor-route" to disable this. I think.
> >
> > Aaryn Pickell - CCNP ATM, CCDP, MCSE
> > Senior Engineer - Routing Protocols
> > Getronics Inc.
> > Direct: 713-394-1609
> > Email:aaryn.pickell@getronics.com
> >
> > This e-mail message and any attachments are confidential and may be
> > privileged. If you are not the intended recipient, please notify me
> > immediately by replying to this message and please destroy all copies of
> > this message and attachments. Thank you.
> >
> >
> > > -----Original Message-----
> > > From: sanjay [mailto:ccienxtyear@hotmail.com]
> > > Sent: Friday, May 25, 2001 1:16 PM
> > > To: ccielab@groupstudy.com
> > > Subject: PPP Encapsulation and OSPF
> > >
> > >
> > > Hi,
> > >
> > > I have 2 routers back to back via serial connection. The
> > > encapsulation on the
> > > serial interface is PPP and the ip address is
> > > 172.17.59.166/29. When I do a
> > > show IP route, the route table shows 2 networks. One of them is
> > > 172.17.59.166/32 and the second 172.17.59.160/29 (this is the
> > > subnet between
> > > the 2 routers). My question is why this behaviour when
> > > running OSPF over PPP
> > > on serial links. As soon as I changed the encapsualtion to HDLC, the
> > > 172.17.59.166/32 is gone. Any ideas?
> > >
> > > thanks,
> > > Sanjay
> > > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:54 GMT-3