From: FATHALLAH (sfathallah@mail.cbi.net.ma)
Date: Thu Apr 10 2003 - 07:30:31 GMT-3
the most way is redistribute connected with route map that match the frame
interface.
refards
-----Message d'origine-----
De : Gibbs, John [mailto:John.Gibbs@AccentureWarwick.com]
Envoyi : jeudi 10 avril 2003 10:35
@ : 'FATHALLAH'; Jennifer Bellucci
Cc : Ccielab
Objet : RE: ISIS & OSPF Red issues
Hi Jennifer
you need to do a redistribute connected subnets in ospf on R5, with a route
map. Then create an access list that refers to 135.25.45.0. This will then
advertise out your 135.25.45.0 network.
Regards
John Gibbs CCNP CNE ACA
Senior Network Consultant
-----Original Message-----
From: FATHALLAH [mailto:sfathallah@mail.cbi.net.ma]
Sent: 10 April 2003 10:00
To: Jennifer Bellucci
Cc: Ccielab
Subject: RE: ISIS & OSPF Red issues
it's not a problem in your config. the isis router redistribute just the
network known throuth his neigbors it never redistribute the derictely
connected network !!!! BIZAR!!! but correct.
regards
-----Message d'origine-----
De : nobody@groupstudy.com [mailto:nobody@groupstudy.com]De la part de
Jennifer Bellucci
Envoyi : mercredi 9 avril 2003 09:15
@ : ccielab@groupstudy.com
Objet : ISIS & OSPF Red issues
Hello People
I have a problem with ISIS and OSPF redistribution. R5 and R4 attach over
a Frame-relay cloud. R5 has R3 amongst others in its OSPF network. R4 is
able
to ping all of R5's interfaces and R5 can do
the same for R4's interfaces, R4 cannot ping any further than R5. R5 and R4
are receiving all the routes via the protocols. R3 on the OSPF network is
also
receiving
all the routes advertised by the ISIS network. R3 can ping R4 loopback and
Ethernet 1 interfaces only.
R3 and the rest of the OSPF network are not getting route 135.25.45.0, which
is the ISIS Frame-relay network.
After having removed all the filters and stuff, its still the same thing. I
added a static route on R3 for network 135.25.45.0 and everything works
perfectly,
so the problem lies in this route not getting advertised.
Can you please take a look and see what I am doing wrong? Is it error in the
config or is it a command I am missing?
any pointers would be welcomed. IOS version is 12.2.2d and routers are
c2500.
Configs are below.
Thanks
R5 - config
logging rate-limit console 10 except errors
enable password ccie
username r3 password 0 ccie
ip subnet-zero
no ip finger
no ip domain-lookup
ip multicast-routing
no ip dhcp-client network-discovery
frame-relay switching
clns routing
isdn switch-type basic-net3
interface Loopback0
ip address 133.25.5.5 255.255.255.255
!
interface Ethernet0
ip address 135.25.55.5 255.255.255.0
ip router isis
ip pim dense-mode
ip igmp join-group 224.2.2.2
!
interface Serial0
no ip address
encapsulation frame-relay
no fair-queue
no frame-relay inverse-arp
frame-relay lmi-type cisco
!
interface Serial0.1 point-to-point
ip address 135.25.45.5 255.255.255.0
ip router isis
frame-relay interface-dlci 504
clns router isis
!
interface Serial0.2 multipoint
ip address 135.25.235.5 255.255.255.240
ip pim dense-mode
ip ospf authentication
ip ospf message-digest-key 1 md5 cisco
ip ospf network point-to-multipoint
ip ospf priority 100
frame-relay map ip 135.25.235.2 502 broadcast
frame-relay map ip 135.25.235.3 503 broadcast
frame-relay map ip 135.25.235.5 502 broadcast
frame-relay interface-dlci 502
frame-relay interface-dlci 503
!
interface Serial9
ip address 135.25.56.5 255.255.255.0
encapsulation frame-relay
ip split-horizon
ip ospf authentication
ip ospf authentication-key cisco
ip ospf network point-to-point
ip ospf priority 100
frame-relay map ip 135.25.56.5 516 broadcast
frame-relay map ip 135.25.56.6 516 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
!
interface BRI0
ip address 135.25.35.5 255.255.255.252
encapsulation ppp
ip ospf cost 2000
ip ospf priority 100
dialer idle-timeout 40
dialer map ip 135.25.35.6 name r3 broadcast
dialer load-threshold 64 either
dialer-group 1
isdn switch-type basic-net3
cdapi buffers regular 0
cdapi buffers raw 0
cdapi buffers large 0
no peer neighbor-route
no cdp enable
ppp multilink
!
router ospf 1
router-id 133.25.5.5
log-adjacency-changes
area 0 authentication message-digest
area 5 authentication
area 5 virtual-link 133.25.6.6 message-digest-key 1 md5 cisco
redistribute isis subnets
network 133.25.5.0 0.0.0.255 area 0
network 135.25.35.5 0.0.0.0 area 0
network 135.25.56.0 0.0.0.255 area 5
network 135.25.235.5 0.0.0.0 area 0
neighbor 135.25.235.3 cost 64
neighbor 135.25.235.2 cost 64
!
router isis
redistribute ospf 1 metric 10 metric-type external level-1-2
net 47.0001.5555.5555.5554.00
is-type level-2-only
!
ip kerberos source-interface any
ip classless
ip http server
!
dialer-list 1 protocol ip permit
route-map ii2o deny 10
match tag 114
!
route-map ii2o permit 20
set tag 411
!
route-map o2ii permit 10
set tag 114
sh ip route - output for router R5
O E2 192.168.13.0/24 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
O E2 192.168.9.0/24 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
O E2 192.168.11.0/24 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
O E2 192.168.5.0/24 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
O E2 192.168.7.0/24 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
133.25.0.0/32 is subnetted, 9 subnets
O IA 133.25.8.8 [110/880] via 135.25.56.6, 00:26:23, Serial9
O E2 133.25.10.10 [110/20] via 135.25.235.2, 00:26:23, Serial0.2
O E2 133.25.7.7 [110/20] via 135.25.56.6, 00:26:24, Serial9
O E2 133.25.1.1 [110/20] via 135.25.235.2, 00:26:24, Serial0.2
O 133.25.6.6 [110/870] via 135.25.56.6, 00:26:34, Serial9
O 133.25.3.3 [110/65] via 135.25.235.3, 00:26:34, Serial0.2
O 133.25.2.2 [110/65] via 135.25.235.2, 00:26:34, Serial0.2
i L2 133.25.4.4 [115/20] via 135.25.45.4, Serial0.1
C 133.25.5.5 is directly connected, Loopback0
O E2 192.168.1.0/24 [110/20] via 135.25.235.2, 00:26:24, Serial0.2
151.100.0.0/21 is subnetted, 1 subnets
O E2 151.100.32.0 [110/100] via 135.25.235.2, 00:26:24, Serial0.2
150.100.0.0/24 is subnetted, 1 subnets
O E2 150.100.1.0 [110/20] via 135.25.235.2, 00:26:24, Serial0.2
135.25.0.0/16 is variably subnetted, 12 subnets, 6 masks
C 135.25.235.0/28 is directly connected, Serial0.2
O 135.25.235.3/32 [110/64] via 135.25.235.3, 00:26:34, Serial0.2
O 135.25.235.2/32 [110/64] via 135.25.235.2, 00:26:34, Serial0.2
O IA 135.25.23.0/25 [110/74] via 135.25.235.2, 00:26:24, Serial0.2
[110/74] via 135.25.235.3, 00:26:24, Serial0.2
O E2 135.25.12.0/24 [110/20] via 135.25.235.2, 00:26:25, Serial0.2
O IA 135.25.66.64/29 [110/879] via 135.25.56.6, 00:26:25, Serial9
i L2 135.25.11.11/32 [115/30] via 135.25.45.4, Serial0.1
C 135.25.56.0/24 is directly connected, Serial9
C 135.25.55.0/24 is directly connected, Ethernet0
C 135.25.45.0/24 is directly connected, Serial0.1
C 135.25.35.4/30 is directly connected, BRI0
i L2 135.25.114.0/24 [115/20] via 135.25.45.4, Serial0.1
O E2 192.168.3.0/24 [110/20] via 135.25.235.2, 00:26:25, Serial0.2
R4 - config
hostname r4
logging rate-limit console 10 except errors
enable password ccie
ip subnet-zero
no ip finger
no ip domain-lookup
no ip dhcp-client network-discovery
clns routing
interface Loopback0
ip address 133.25.4.4 255.255.255.255
ip router isis
!
interface Ethernet0
ip address 150.100.2.5 255.255.255.0
!
interface Ethernet1
ip address 135.25.114.4 255.255.255.0
ip router isis
clns router isis
!
interface Serial0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
frame-relay lmi-type cisco
!
interface Serial0.1 point-to-point
ip address 135.25.45.4 255.255.255.0
ip router isis
frame-relay interface-dlci 405
clns router isis
!
interface Serial1
no ip address
shutdown
!
router isis
redistribute rip metric 0 route-map ii2r metric-type external
net 47.0001.5555.5555.5555.00
!
router rip
version 2
redistribute isis level-2 route-map rr2ii
network 150.100.0.0
no auto-summary
!
ip kerberos source-interface any
ip classless
ip http server
!
route-map rr2ii permit 10
set tag 666
!
route-map ii2r deny 10
match tag 666
!
route-map ii2r permit 20
set tag 999
!
sh ip route - output for R4
i L2 192.168.13.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 192.168.9.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 192.168.11.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 192.168.5.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 192.168.7.0/24 [115/84] via 135.25.45.5, Serial0.1
133.25.0.0/32 is subnetted, 10 subnets
i L2 133.25.8.8 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.2.2 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.3.3 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.6.6 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.1.1 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.7.7 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.10.10 [115/84] via 135.25.45.5, Serial0.1
i L2 133.25.5.5 [115/84] via 135.25.45.5, Serial0.1
R 133.25.20.20 [120/1] via 150.100.2.2, 00:00:18, Ethernet0
C 133.25.4.4 is directly connected, Loopback0
i L2 192.168.1.0/24 [115/84] via 135.25.45.5, Serial0.1
151.100.0.0/21 is subnetted, 1 subnets
i L2 151.100.32.0 [115/84] via 135.25.45.5, Serial0.1
150.100.0.0/24 is subnetted, 2 subnets
C 150.100.2.0 is directly connected, Ethernet0
i L2 150.100.1.0 [115/84] via 135.25.45.5, Serial0.1
135.25.0.0/16 is variably subnetted, 12 subnets, 6 masks
i L2 135.25.235.0/28 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.235.3/32 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.235.2/32 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.23.0/25 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.12.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.66.64/29 [115/84] via 135.25.45.5, Serial0.1
i L1 135.25.11.11/32 [115/20] via 135.25.114.11, Ethernet1
i L2 135.25.56.0/24 [115/84] via 135.25.45.5, Serial0.1
i L2 135.25.55.0/24 [115/20] via 135.25.45.5, Serial0.1
C 135.25.45.0/24 is directly connected, Serial0.1
i L2 135.25.35.4/30 [115/84] via 135.25.45.5, Serial0.1
C 135.25.114.0/24 is directly connected, Ethernet1
i L2 192.168.3.0/24 [115/84] via 135.25.45.5, Serial0.1
sh ip route - output for R3
O E2 192.168.13.0/24 [110/20] via 135.25.23.2, 00:29:05, Ethernet0
O E2 192.168.9.0/24 [110/20] via 135.25.23.2, 00:29:05, Ethernet0
O E2 192.168.11.0/24 [110/20] via 135.25.23.2, 00:29:05, Ethernet0
O E2 192.168.5.0/24 [110/20] via 135.25.23.2, 00:29:05, Ethernet0
O E2 192.168.7.0/24 [110/20] via 135.25.23.2, 00:29:06, Ethernet0
133.25.0.0/32 is subnetted, 9 subnets
O E2 133.25.4.4 [110/20] via 135.25.235.5, 00:29:06, Serial0
O IA 133.25.8.8 [110/944] via 135.25.235.5, 00:29:06, Serial0
O IA 133.25.6.6 [110/934] via 135.25.235.5, 00:29:07, Serial0
O 133.25.5.5 [110/65] via 135.25.235.5, 00:29:17, Serial0
O 133.25.2.2 [110/129] via 135.25.235.5, 00:29:17, Serial0
O E2 133.25.10.10 [110/20] via 135.25.23.2, 00:29:07, Ethernet0
O E2 133.25.7.7 [110/20] via 135.25.23.23, 00:29:07, Ethernet0
O E2 133.25.1.1 [110/20] via 135.25.23.2, 00:29:08, Ethernet0
C 133.25.3.3 is directly connected, Loopback0
O E2 192.168.1.0/24 [110/20] via 135.25.23.2, 00:29:08, Ethernet0
151.100.0.0/21 is subnetted, 1 subnets
O E2 151.100.32.0 [110/100] via 135.25.23.2, 00:29:08, Ethernet0
150.100.0.0/24 is subnetted, 1 subnets
O E2 150.100.1.0 [110/20] via 135.25.23.2, 00:29:08, Ethernet0
135.25.0.0/16 is variably subnetted, 10 subnets, 6 masks
O 135.25.235.5/32 [110/64] via 135.25.235.5, 00:29:18, Serial0
C 135.25.235.0/28 is directly connected, Serial0
O 135.25.235.2/32 [110/128] via 135.25.235.5, 00:29:18, Serial0
C 135.25.23.0/25 is directly connected, Ethernet0
O E2 135.25.12.0/24 [110/20] via 135.25.23.2, 00:29:08, Ethernet0
O IA 135.25.66.64/29 [110/943] via 135.25.235.5, 00:29:08, Serial0
O E2 135.25.11.11/32 [110/20] via 135.25.235.5, 00:29:08, Serial0
O IA 135.25.56.0/24 [110/933] via 135.25.235.5, 00:29:08, Serial0
C 135.25.35.4/30 is directly connected, BRI0
O E2 135.25.114.0/24 [110/20] via 135.25.235.5, 00:29:09, Serial0
O E2 192.168.3.0/24 [110/20] via 135.25.23.2, 00:29:09, Ethernet0
Jennifer_bellucci@hotmail.com
****************************************************
Before being delivered to the Accenture Warwick
Microsoft Exchange system, this email (including any
attachments) was scanned by Mailsweeper for viruses
and inappropriate content, according to Accenture's
standard email policy.
Accenture reserves the right to monitor email from
external and internal sources for the purpose of
ensuring correct and appropriate use of Accenture
communication equipment.
****************************************************
*********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you are not the intended recipient, you must not
copy, distribute or take any action in reliance on it.
Opinions expressed are those of the individual sender and not of
Accenture.
If you have received this email in error please notify the sender by
return email.
This footnote confirms that this email message has been checked for
viruses and inappropriate content.
Accenture reserves the right to monitor email communications from
external and internal sources for the purpose of ensuring correct and
appropriate use of Accenture communication equipment.
*********************************************************************
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:50 GMT-3