From: surenv (surenv@hpssk211.sgp.hp.com)
Date: Tue Jan 07 2003 - 23:04:19 GMT-3
Hi Grp,
I am having so problems understanding VLSM-FLSM redistribution. This
is my network.
-------(e1/0)R4(s0/0)---------------(FR)-----------------(s1/0)(R3)
R4(e1/0) ------- 133.10.24.4/25
R4(s0/0) ------- 133.10.34.4/24
R3(s1/0) -------- 133.10.34.3/24
I want the 133.10.24.0/25 subnet to appear in the routing table of R3.
However, I do not want to summarize. Therfore, I used secondary address
of the same subnet. do not worry about the 192.168.0.0 routes appearing
in the routing table. I am only interested in few things.
(1) Why doesn't 133.10.24.0./25 route appear on R3?
(2) Why does all routes appear with the secondary subnet mask/25 rather
than the primary subnet mask/24?
Please help.
R4-Config
interface Serial0/0
ip address 133.10.134.4 255.255.255.128 secondary
ip address 133.10.34.4 255.255.255.0
encapsulation frame-relay
ip split-horizon
serial restart-delay 0
no arp frame-relay
frame-relay map ip 133.10.134.3 403 broadcast
frame-relay map ip 133.10.34.3 403 broadcast
no frame-relay inverse-arp
frame-relay lmi-type ansi
end
interface Ethernet1/0
ip address 133.10.24.4 255.255.255.128
end
router eigrp 1
redistribute rip metric 64 100 255 1 1500
network 133.10.4.0 0.0.0.255
network 133.10.24.0 0.0.0.255
no auto-summary
no eigrp log-neighbor-changes
!
router rip
redistribute eigrp 1 metric 1
passive-interface default
no passive-interface Serial0/0
network 133.10.0.0
no auto-summary
R3 - Config
interface Serial1/0
ip address 133.10.134.3 255.255.255.128 secondary
ip address 133.10.34.3 255.255.255.0
encapsulation frame-relay
ip split-horizon
serial restart-delay 0
no arp frame-relay
frame-relay map ip 133.10.134.4 304 broadcast
frame-relay map ip 133.10.34.4 304 broadcast
no frame-relay inverse-arp
router rip
network 133.10.0.0
network 192.168.1.0
network 192.168.2.0
network 192.168.3.0
network 192.168.4.0
network 192.168.5.0
network 192.168.6.0
no auto-summary
Routing table R4
R 192.168.5.0/24 [120/1] via 133.10.34.3, 00:00:01, Serial0/0
133.10.0.0/16 is variably subnetted, 17 subnets, 2 masks
C 133.10.134.0/25 is directly connected, Serial0/0
D EX 133.10.156.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
D EX 133.10.14.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
D EX 133.10.8.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
D EX 133.10.6.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
D EX 133.10.5.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
C 133.10.4.0/24 is directly connected, Loopback0
R 133.10.3.0/25 [120/1] via 133.10.34.3, 00:00:01, Serial0/0
D 133.10.2.0/24 [90/409600] via 133.10.24.2, 00:31:32, Ethernet1/0
D EX 133.10.1.0/24 [170/40563200] via 133.10.24.2, 00:31:32,
Ethernet1/0
D 133.10.25.0/24 [90/2195456] via 133.10.24.2, 00:31:32,
Ethernet1/0
C 133.10.24.0/25 is directly connected, Ethernet1/0
D EX 133.10.23.0/24 [170/40563200] via 133.10.24.2, 00:31:34,
Ethernet1/0
C 133.10.34.0/24 is directly connected, Serial0/0
D EX 133.10.68.0/24 [170/40563200] via 133.10.24.2, 00:31:34,
Ethernet1/0
D EX 133.10.81.0/24 [170/40563200] via 133.10.24.2, 00:31:34,
Ethernet1/0
D EX 133.10.110.0/24 [170/40563200] via 133.10.24.2, 00:31:34,
Ethernet1/0
R 192.168.1.0/24 [120/1] via 133.10.34.3, 00:00:03, Serial0/0
R 192.168.3.0/24 [120/1] via 133.10.34.3, 00:00:03, Serial0/0
Routing table R3
R3#sh ip route
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, ia - IS-IS
inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.4.0/24 is directly connected, Loopback4
C 192.168.5.0/24 is directly connected, Loopback5
C 192.168.6.0/24 is directly connected, Loopback6
133.10.0.0/16 is variably subnetted, 16 subnets, 2 masks
C 133.10.134.0/25 is directly connected, Serial1/0
R 133.10.156.0/25 [120/1] via 133.10.34.4, 00:00:14, Serial1/0
R 133.10.14.0/25 [120/1] via 133.10.34.4, 00:00:14, Serial1/0
R 133.10.8.0/25 [120/1] via 133.10.34.4, 00:00:14, Serial1/0
R 133.10.6.0/25 [120/1] via 133.10.34.4, 00:00:15, Serial1/0
R 133.10.5.0/25 [120/1] via 133.10.34.4, 00:00:15, Serial1/0
R 133.10.4.0/25 [120/1] via 133.10.34.4, 00:00:15, Serial1/0
C 133.10.3.0/24 is directly connected, Loopback0
R 133.10.2.0/25 [120/1] via 133.10.34.4, 00:00:15, Serial1/0
R 133.10.1.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
R 133.10.25.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
R 133.10.23.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
C 133.10.34.0/24 is directly connected, Serial1/0
R 133.10.68.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
R 133.10.81.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
R 133.10.110.0/25 [120/1] via 133.10.34.4, 00:00:16, Serial1/0
C 192.168.1.0/24 is directly connected, Loopback1
C 192.168.2.0/24 is directly connected, Loopback2
C 192.168.3.0/24 is directly connected, Loopback3
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:45 GMT-3