From: Paul Cosgrove (paul.cosgrove@heanet.ie)
Date: Wed Apr 23 2008 - 15:54:22 ART
Sorry, strike that about redistribution. The static-to-connected routes
are redistributed.
Paul Cosgrove wrote:
> It kind of works if you use RIP and EIGRP, though clearly not with
> OSPF. I say "kind of" because if one of these protocols is
> redistributed into another routing process then the static routes (to
> connected interface) are not redistributed, so they are not treated
> like connected routes in that respect. See also that EIGRP lists the
> route as being learned via static redistribution, although no
> redistribution was configured and the route is actually internal.
>
> Router6(config)#do sh ip int br
> Interface IP-Address OK? Method
> Status Protocol
> FastEthernet0/0 172.16.23.6 YES manual
> up up FastEthernet0/1
> unassigned YES NVRAM administratively down down
> Router6(config)#ip route 5.5.5.0 255.255.255.0 fa0/0
> Router6(config)#router rip
> Router6(config-router)#network 5.0.0.0
> Router6(config-router)#do sh ip rip da
> 5.0.0.0/8 auto-summary
> 5.5.5.0/24 directly connected, FastEthernet0/0
> Router6(config-router)#router eigrp 6
> Router6(config-router)#network 5.5.5.0 0.0.0.255
> Router6(config-router)#do sh ip eigrp top
> IP-EIGRP Topology Table for AS(6)/ID(172.16.23.6)
>
> Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
> r - reply Status, s - sia Status
>
> P 5.5.5.0/24, 1 successors, FD is 2560002560
> via Rstatic (2560002560/0)
> Router6(config-router)#
>
> Paul.
>
> Botha Michael wrote:
>> Hi,
>>
>> Nope - I was wrong.
>> The network command does not do anything for this situation.
>>
>> I tried it on version 12.4.
>>
>> I think the doc-cd is wrong. I agree with Ernst - it does not work this
>> way.
>>
>> Bug ID CSCdi38232 describes the following and this contradicts what is
>> said in the doc-cd.
>>
>> redistribute connected should not redistribute static route to OSPF
>> Doing a redistribute connected will also redistribute
>> interface static route into OSPF. In other words, OSPF will generate
>> external link state advertisement for it. Doing clear ip route *
>> will delete the external link state advertisement
>>
>> The static route to the interface still has a admin distance of 1
>> whereas a connected interface has a admin distance of 0.
>>
>> This tells me that you cannot get the static to a physical interface
>> into the dynamic routing process without a redistribute static.
>>
>> Regards
>>
>> Mike B
>>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>> Murphy, William Sent: 22 April 2008 09:00 PM
>> To: Botha Michael; GS@infosecureltd.com; Mike Harrison;
>> ccielab@groupstudy.com
>> Subject: RE: Static route pointing to an interface
>>
>> Do you have 12.4 on your routers? The doc is for 12.4 so I was thinking
>> this might be new functionality/behavior...
>>
>> Bill Murphy
>> Senior Network Analyst
>> University of Texas Health Science Center - Houston
>>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>> Botha Michael
>> Sent: Tuesday, April 22, 2008 1:44 PM
>> To: GS@infosecureltd.com; Mike Harrison; ccielab@groupstudy.com
>> Subject: RE: Static route pointing to an interface
>>
>> Hi Ernst,
>>
>> Very interesting.
>> Maybe it has something to do with the fact that OSPF by default
>> advertises any loopback as a /32 host and not a network.
>>
>> Maybe you could try the ip ospf network command on your R5 loopback
>> interface to make it send the full network/mask to R1.
>>
>> Interface loopback0
>> Ip ospf network point-to-point
>>
>> This should get the full loopback network across to R1.
>>
>> Regards
>>
>> Mike B
>>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>> GS@infosecureltd.com
>> Sent: 22 April 2008 07:49 PM
>> To: 'Mike Harrison'; ccielab@groupstudy.com
>> Subject: RE: Static route pointing to an interface
>>
>> Hi Mike
>> Please see below:
>> http://www.cisco.com/en/US/docs/ios/12_4/ip_route/configuration/guide/pi
>> conf
>> ig.html#wp1000929
>>
>> The section I've highlighted is just below the Default AD table.
>>
>> Regards, Ernst
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>> Mike
>> Harrison
>> Sent: 22 April 2008 18:03
>> To: Ernst Pelser; ccielab@groupstudy.com
>> Subject: Re: Static route pointing to an interface
>>
>> Sounds like a mistake in the Doccd - Can you post the link??
>>
>>
>> Mike
>>
>> ----- Original Message -----
>> From: "Ernst Pelser" <e.pelser@infosecureltd.com>
>> To: <ccielab@groupstudy.com>
>> Sent: Tuesday, April 22, 2008 12:36 PM
>> Subject: Static route pointing to an interface
>>
>>
>>
>>> Hi All
>>> Just been reading the following relating to static routes in the
>>>
>> DocCD.
>>
>>> Static routes that point to an interface will be advertised via RIP,
>>> EIGRP,
>>> and other dynamic routing
>>> protocols, regardless of whether redistribute static router
>>>
>> configuration
>>
>>> commands were specified for
>>> those routing protocols. These static routes are advertised because
>>>
>> static
>>
>>> routes that point to an interface
>>> are considered in the routing table to be connected and hence lose
>>>
>> their
>>
>>> static nature. However, if you
>>> define a static route to an interface that is not one of the networks
>>> defined in a network command, no
>>> dynamic routing protocols will advertise the route unless a
>>>
>> redistribute
>>
>>> static command is specified for
>>> these protocols.
>>>
>>> However, when I lab this up, I don't get the results as described
>>>
>> above.
>>
>>> As a basic test I have R5 and R1 via S0/0. There are other devices in
>>>
>> the
>>
>>> network but these should not affect this test. My config are below.
>>>
>>> R5
>>> router ospf 1
>>> router-id 150.1.5.5
>>> log-adjacency-changes
>>> passive-interface Loopback0
>>> network 0.0.0.0 255.255.255.255 area 0
>>> neighbor 155.1.0.1
>>>
>>> ip route 160.1.1.0 255.255.255.0 Loopback0
>>>
>>> interface Loopback0
>>> ip address 150.1.5.5 255.255.255.0
>>> !
>>> interface Serial0/0
>>> ip address 155.1.0.5 255.255.255.0
>>> encapsulation frame-relay
>>> frame-relay map ip 155.1.0.1 501
>>> frame-relay map ip 155.1.0.4 504
>>> no frame-relay inverse-arp
>>>
>>> R1
>>> router ospf 1
>>> router-id 155.1.1.1
>>> log-adjacency-changes
>>> passive-interface Loopback0
>>> network 155.1.0.1 0.0.0.0 area 0
>>>
>>> interface Loopback0
>>> ip address 150.1.5.5 255.255.255.0
>>>
>>> !interface Serial0/0
>>> ip address 155.1.0.5 255.255.255.0
>>> encapsulation frame-relay
>>> frame-relay map ip 155.1.0.1 501
>>> frame-relay map ip 155.1.0.4 504
>>> no frame-relay inverse-arp
>>>
>>> R5 show commands
>>> Gateway of last resort is not set
>>>
>>> 155.1.0.0/24 is subnetted, 2 subnets
>>> O IA 155.1.146.0 [110/65] via 155.1.0.1, 00:35:03, Serial0/0
>>> C 155.1.0.0 is directly connected, Serial0/0
>>> 160.1.0.0/24 is subnetted, 1 subnets
>>> S 160.1.1.0 is directly connected, Loopback0
>>> 150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
>>> C 150.1.5.0/24 is directly connected, Loopback0
>>> O IA 150.1.6.6/32 [110/66] via 155.1.0.1, 00:35:03, Serial0/0
>>> O IA 150.1.4.4/32 [110/65] via 155.1.0.4, 00:35:03, Serial0/0
>>> O IA 150.1.1.1/32 [110/65] via 155.1.0.1, 00:35:04, Serial0/0
>>>
>>> R5#sh ip ospf nei
>>>
>>> Neighbor ID Pri State Dead Time Address Interface
>>> 155.1.1.1 0 FULL/DROTHER 00:01:57 155.1.0.1 Serial0/0
>>> 150.1.4.4 0 FULL/DROTHER 00:01:36 155.1.0.4 Serial0/0
>>>
>>>
>>> R1 show commands
>>> Neighbor ID Pri State Dead Time Address Interface
>>> 150.1.5.5 1 FULL/DR 00:01:51 155.1.0.5 Serial0/0
>>> 150.1.4.4 1 FULL/DR 00:00:31 155.1.146.4
>>> FastEthernet0/0
>>> 150.1.6.6 2 FULL/BDR 00:00:31 155.1.146.6
>>> FastEthernet0/0
>>>
>>> R1#sh ip route
>>> Codes: C - connected, S - static, 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
>>> i - IS-IS, su - IS-IS summary, 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
>>>
>>> 155.1.0.0/24 is subnetted, 2 subnets
>>> C 155.1.146.0 is directly connected, FastEthernet0/0
>>> C 155.1.0.0 is directly connected, Serial0/0
>>> 150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
>>> C 150.1.1.0/24 is directly connected, Loopback0
>>> O 150.1.6.6/32 [110/2] via 155.1.146.6, 00:37:19,
>>>
>> FastEthernet0/0
>>
>>> O 150.1.5.5/32 [110/65] via 155.1.0.5, 00:12:39, Serial0/0
>>> O 150.1.4.4/32 [110/2] via 155.1.146.4, 00:37:19,
>>>
>> FastEthernet0/0
>>
>>> R1#
>>> R1#sh ip ospf data
>>> R1#sh ip ospf database
>>>
>>> OSPF Router with ID (155.1.1.1) (Process ID 1)
>>>
>>> Router Link States (Area 0)
>>>
>>> Link ID ADV Router Age Seq# Checksum Link
>>>
>> count
>>
>>> 150.1.4.4 150.1.4.4 1167 0x80000003 0x003F30 1
>>> 150.1.5.5 150.1.5.5 1114 0x80000003 0x004D6B 2
>>> 155.1.1.1 155.1.1.1 242 0x80000003 0x000D67 1
>>>
>>> Net Link States (Area 0)
>>>
>>> Link ID ADV Router Age Seq# Checksum
>>> 155.1.0.5 150.1.5.5 367 0x80000003 0x00B55B
>>>
>>> Summary Net Link States (Area 0)
>>>
>>> Link ID ADV Router Age Seq# Checksum
>>> 150.1.1.1 150.1.4.4 402 0x80000002 0x00A750
>>> 150.1.1.1 155.1.1.1 242 0x80000002 0x003DC5
>>> 150.1.4.4 150.1.4.4 1167 0x80000002 0x0004F7
>>> 150.1.4.4 155.1.1.1 242 0x80000002 0x0008F3
>>> 150.1.6.6 150.1.4.4 1167 0x80000002 0x003EAF
>>> 150.1.6.6 155.1.1.1 242 0x80000002 0x00DD1A
>>> 155.1.146.0 150.1.4.4 1169 0x80000004 0x002140
>>> 155.1.146.0 155.1.1.1 244 0x80000004 0x00C0AA
>>>
>>> Router Link States (Area 1)
>>>
>>> Link ID ADV Router Age Seq# Checksum Link
>>>
>> count
>>
>>> 150.1.4.4 150.1.4.4 1168 0x80000004 0x0029A6 2
>>> 150.1.6.6 150.1.6.6 1041 0x80000003 0x003E85 2
>>> 155.1.1.1 155.1.1.1 244 0x80000004 0x008A59 2
>>>
>>> Net Link States (Area 1)
>>>
>>> Link ID ADV Router Age Seq# Checksum
>>> 155.1.146.4 150.1.4.4 403 0x80000003 0x009FDF
>>>
>>> Summary Net Link States (Area 1)
>>>
>>> Link ID ADV Router Age Seq# Checksum
>>> 150.1.5.5 150.1.4.4 1168 0x80000002 0x007148
>>> 150.1.5.5 155.1.1.1 244 0x80000002 0x006B4F
>>> 155.1.0.0 150.1.4.4 1168 0x80000004 0x008B32
>>> 155.1.0.0 155.1.1.1 244 0x80000002 0x008937
>>> R1#
>>> R1#
>>>
>>>
>>> Could anyone explain why this route (160.1.1.0) is not being
>>>
>> advertised or
>>
>>> is this a mistake in the documentation?
>>>
>>> Thanks for your assistance.
>>>
>>> Regards, Ernst
>>>
>>>
>>> Pass the CCIE in six weeks, Guaranteed!
>>> http://www.certscience.com/CCIE
>>>
>>>
>> _______________________________________________________________________
>>
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>
>>
>> Pass the CCIE in six weeks, Guaranteed!
>> http://www.certscience.com/CCIE
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Pass the CCIE in six weeks, Guaranteed!
>> http://www.certscience.com/CCIE
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Pass the CCIE in six weeks, Guaranteed!
>> http://www.certscience.com/CCIE
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Pass the CCIE in six weeks, Guaranteed!
>> http://www.certscience.com/CCIE
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Pass the CCIE in six weeks, Guaranteed!
>> http://www.certscience.com/CCIE
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Pass the CCIE in six weeks, Guaranteed!
> http://www.certscience.com/CCIE
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Pass the CCIE in six weeks, Guaranteed!
http://www.certscience.com/CCIE
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:51 ART