From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Sun Nov 27 2005 - 00:34:37 GMT-3
You should remove any and all excess configuration and then test for
reachability. Remember that in the real lab you shouldn't have the
extra configuration applied without first having reachability.
Take off the redistribution, RIP triggered, authentication,
passive-interface default, etc and then test reachability.
HTH,
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
22Cent@gmail.com
Sent: Friday, November 25, 2005 12:59 PM
To: Group Study
Subject: I am missing something? - VIrtual Template
I can't seem to locate the issue here.
[the rest of the
networt]-------R2--FR/Virtual-template-------------------R4
R4 can't reach anything past R2. I've posted my configs below. Any help
would be great. Thanks Ray
R2
interface Serial0/1
no ip address
encapsulation frame-relay
frame-relay interface-dlci 214 ppp Virtual-Template1
no frame-relay inverse-arp
!
interface Virtual-Template1
ip address 12.12.24.2 255.255.255.0
ip rip triggered
ip rip authentication mode md5
ip rip authentication key-chain cisco
router rip
version 2
timers basic 30 180 0 240
redistribute ospf 1
passive-interface default
no passive-interface Virtual-Template1
network 12.0.0.0
default-metric 2
no auto-summary
R4 ( Notice the routing table)
interface Serial0/0
no ip address
encapsulation frame-relay
frame-relay interface-dlci 412 ppp Virtual-Template1
no frame-relay inverse-arp
interface Virtual-Template1
ip address 12.12.24.4 255.255.255.0
ip rip authentication mode md5
ip rip authentication key-chain cisco
router rip
version 2
passive-interface default
no passive-interface Virtual-Template1
network 12.0.0.0
no auto-summary
R4's routing table
R 199.172.11.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
R 199.172.10.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
R 199.172.9.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
R 199.172.8.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
4.0.0.0/30 is subnetted, 1 subnets
R 4.1.1.0 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
R 198.198.3.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
R 198.198.1.0/24 [120/2] via 12.12.24.2, 00:00:00, Virtual-Access1
12.0.0.0/8 is variably subnetted, 13 subnets, 3 masks
R 12.12.7.7/32 [120/2] via 12.12.24.2, 00:00:01, Virtual-Access1
R 12.12.5.5/32 [120/2] via 12.12.24.2, 00:00:01, Virtual-Access1
R 12.12.3.3/32 [120/2] via 12.12.24.2, 00:00:01, Virtual-Access1
R 12.12.1.1/32 [120/2] via 12.12.24.2, 00:00:01, Virtual-Access1
R 12.12.2.0/24 [120/1] via 12.12.24.2, 00:00:02, Virtual-Access1
C 12.12.4.0/24 is directly connected, Loopback0
R 12.12.12.0/22 [120/2] via 12.12.24.2, 00:00:02, Virtual-Access1
C 12.12.24.0/24 is directly connected, Virtual-Access1
C 12.12.24.2/32 is directly connected, Virtual-Access1
R 12.12.28.0/24 [120/1] via 12.12.24.2, 00:00:02, Virtual-Access1
R 12.12.56.0/24 [120/2] via 12.12.24.2, 00:00:02, Virtual-Access1
R 12.12.65.0/24 [120/2] via 12.12.24.2, 00:00:02, Virtual-Access1
R 12.12.125.0/24 [120/1] via 12.12.24.2, 00:00:02, Virtual-Access1
R 192.3.1.0/24 [120/2] via 12.12.24.2, 00:00:02, Virtual-Access1
150.100.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 150.100.2.0/24 is directly connected, FastEthernet0/0
R 150.100.0.0/16 [120/2] via 12.12.24.2, 00:00:02, Virtual-Access1
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:08 GMT-3