From: Héctor Fernández (gnakh@telefonica.net)
Date: Mon Aug 22 2005 - 19:23:56 GMT-3
Hi Dave,
Who is 90.90.100.1? It's the router that's advertising that route, not you
(2.2.2.2). Or may be, it was your R3 router before you statically changed
the router-id and that route comes from a neighbor. I could not say.
Clear ip ospf process in all routers...
I hope this helps
Best regards
Hictor
----- Original Message -----
From: "Schulz, Dave" <DSchulz@dpsciences.com>
To: <ccielab@groupstudy.com>
Sent: Monday, August 22, 2005 8:37 PM
Subject: OSPF Redistribution with route-map
> Greetings, group -
>
> I am trying to redistribute loopback interfaces (specific ones) with a
> route-map, and having a strange occurrence.
>
> Here is the configuration:
>
> R3#sh run
> !
> interface Loopback0
> ip address 90.90.90.1 255.255.255.0
> !
> interface Loopback1
> ip address 90.90.91.1 255.255.255.0
> !
> interface Loopback2
> ip address 90.90.92.1 255.255.255.0
> !
> interface Loopback3
> ip address 90.90.93.1 255.255.255.0
> !
> interface Loopback4
> ip address 90.90.94.1 255.255.255.0
> !
> interface Loopback5
> ip address 90.90.95.1 255.255.255.0
> !
> interface Loopback6
> ip address 90.90.96.1 255.255.255.0
> !
> interface Loopback7
> ip address 90.90.97.1 255.255.255.0
> !
> interface Loopback8
> ip address 90.90.98.1 255.255.255.0
> !
> interface Loopback9
> ip address 90.90.99.1 255.255.255.0
> !
> interface Loopback10
> ip address 90.90.100.1 255.255.255.0
> !
> interface Serial0
> ip address 192.168.1.3 255.255.255.0
> encapsulation frame-relay
> ip ospf message-digest-key 1 md5 ipexpert
> ip ospf priority 0
> no arp frame-relay
> frame-relay map ip 192.168.1.2 302 broadcast
> frame-relay map ip 192.168.1.4 302 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type ansi
> !
> router ospf 1
> router-id 2.2.2.2
> log-adjacency-changes
> no auto-cost
> area 0 authentication message-digest
> redistribute connected subnets route-map LOOP
> network 192.168.1.0 0.0.0.255 area 0
> !
> access-list 1 permit 90.90.96.0 0.0.3.255 log
> route-map LOOP permit 10
> match ip address 1
> set metric 10
> !
>
> Here is the sh ip ospf database:
>
> R3# sh ip ospf data
>
> OSPF Router with ID (2.2.2.2) (Process ID 1)
>
>
> Router Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum Link
> count
> 1.1.1.1 1.1.1.1 700 0x80000024 0xD3EF 1
> 2.2.2.2 2.2.2.2 167 0x80000002 0xDFFA 1
> 192.168.1.4 192.168.1.4 480 0x80000020 0x2DEF 1
>
> Net Link States (Area 0)
>
> Link ID ADV Router Age Seq# Checksum
> 192.168.1.2 1.1.1.1 55 0x80000020 0x30FB
>
> Type-5 AS External Link States
>
> Link ID ADV Router Age Seq# Checksum Tag
> 90.90.96.0 2.2.2.2 18 0x80000001 0x503D 0
> 90.90.97.0 2.2.2.2 18 0x80000001 0x4547 0
> 90.90.98.0 2.2.2.2 18 0x80000001 0x3A51 0
> 90.90.99.0 2.2.2.2 18 0x80000001 0x2F5B 0
> 90.90.100.0 90.90.100.1 232 0x80000001 0xFF6D 0
> R3#
>
>
> Looks good, except for one item....the access list was intended to allow
> only subnets 96 through 99 (which it does)....but I am also getting the
> 100 subnet!? I can't figure out why this is not being denied.
> And....why is it showing up from the router-id 90.90.100.1, when I have
> specifically set the router-id to 2.2.2.2. Very strange, eh?
>
> Dave
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3