From: Timothy Ouellette (timoue@cogeco.ca)
Date: Thu Oct 24 2002 - 04:28:08 GMT-3
Tried to match on length and that didn't work. I then did the following on router 3
3#sh access-list
Standard IP access list 1
permit 1.0.0.0, wildcard bits 0.255.255.255 log check=3
r3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
r3(config)#no access-list 1
r3(config)#access-list 1 permit any
r3#sh access-list 1
Standard IP access list 1
permit any (1 matche)
Was checked 3 times but no match. So I redid the last to match all.
Still shows up in r2 with no external tag data?
r2#sh ip ospf d e
OSPF Router with ID (192.168.1.2) (Process ID 1)
Type-5 AS External Link States
Routing Bit Set on this LSA
LS age: 219
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 3.3.3.0 (External Network Number )
Advertising Router: 3.3.3.3
LS Seq Number: 80000001
Checksum: 0x8A10
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 5
Forward Address: 0.0.0.0
External Route Tag: 0
Tim
Jason Sinclair wrote:
> Tim,
>
> Sent you a note offline - but there is a caveat that the route-map must have
> a match statement.
>
> Cheers,
>
> Jason Sinclair CCIE #9100
> Manager, Network Control Centre
> POWERTEL
> 55 Clarence Street,
> SYDNEY NSW 2000
> AUSTRALIA
> office: + 61 2 8264 3820
> mobile: + 61 416 105 858
> email: sinclairj@powertel.com.au
>
> -----Original Message-----
> From: Timothy Ouellette [mailto:timoue@cogeco.ca]
> Sent: Thursday, 24 October 2002 16:28
> To: ccielab@groupstudy.com; cisco@groupstudy.com
> Subject: BGP/OSPF table-map tag question????
>
> table-map/bgp/ospf/origin code question. I'm having some trouble
> getting it to work. r1 has a loopback 1.1.1.1
> and has a network statement in BGP for it, i'm taking the bgp routes,
> putting them into ospf and trying to tag them (with origin code) and
> then when that route makes it over to r3, trying to read the tag and set
> it again so it shows "i" and not incomplete but I can't seem to get the
> external tag data into ospf.
>
> Here's the setup..
>
> 1.1.1.1 (lo1 in BGP as 1) R1---ospf0----r2----ospf0------r3(3.3.3.3 in
> bgp as 3)
>
> here's the relevant configs
>
> r1
> nterface Loopback1
> ip address 1.1.1.1 255.255.255.0
> !
> interface Serial0
> ip address 192.168.1.1 255.255.255.0
> encapsulation frame-relay
> !
> router ospf 1
> log-adjacency-changes
> redistribute bgp 1 subnets
> network 192.168.1.0 0.0.0.255 area 0
> neighbor 192.168.1.2 priority 1
> !
> router bgp 1
> table-map autotag
> bgp log-neighbor-changes
> network 1.1.1.0 mask 255.255.255.0
> redistribute ospf 1 metric 5 match internal external 1 external 2
> route-map tags
> no auto-summary
> !
> route-map tags permit 10
> set as-path tag
> !
> route-map autotag permit 10
> set automatic-tag
>
> r2
>
> interface Ethernet0
> ip address 172.16.1.2 255.255.255.0
> !
> interface Serial0
> ip address 192.168.1.2 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 192.168.1.1 201 broadcast
> !
> router ospf 1
> log-adjacency-changes
> network 172.16.1.0 0.0.0.255 area 0
> network 192.168.1.0 0.0.0.255 area 0
> neighbor 192.168.1.1
>
> r3
>
> nterface Loopback0
> ip address 3.3.3.3 255.255.255.0
> !
> interface Ethernet0
> ip address 172.16.1.3 255.255.255.0
> !
> router ospf 1
> log-adjacency-changes
> redistribute bgp 3 subnets
> network 172.16.1.0 0.0.0.255 area 0
> !
> router bgp 3
> table-map autotag
> bgp log-neighbor-changes
> network 3.3.3.0 mask 255.255.255.0
> redistribute ospf 1 metric 5 match internal external 1 external 2
> route-map tags
> no auto-summary
> !
> route-map tags permit 10
> set as-path tag
> !
> route-map autotag permit 10
> set automatic-tag
>
> here's the info about 1.1.1.0/24 from r1 but from r3's perspective.
> r3#sh ip bgp 1.1.1.0
> BGP routing table entry for 1.1.1.0/24, version 7
> Paths: (1 available, best #1, table Default-IP-Routing-Table)
> Not advertised to any peer
> Local
> 172.16.1.2 from 0.0.0.0 (3.3.3.3)
> Origin incomplete, metric 5, localpref 100, weight 32768, valid,
> sourced, best
> r3#
> 3#sh ip ospf data e
>
> OSPF Router with ID (3.3.3.3) (Process ID 1)
>
> Type-5 AS External Link States
>
> Routing Bit Set on this LSA
> LS age: 879
> Options: (No TOS-capability, DC)
> LS Type: AS External Link
> Link State ID: 1.1.1.0 (External Network Number )
> Advertising Router: 1.1.1.1
> LS Seq Number: 80000001
> Checksum: 0xE6C5
> Length: 36
> Network Mask: /24
> Metric Type: 2 (Larger than any link state path)
> TOS: 0
> Metric: 1
> Forward Address: 0.0.0.0
> External Route Tag: 0
>
> LS age: 815
> Options: (No TOS-capability, DC)
> LS Type: AS External Link
> Link State ID: 3.3.3.0 (External Network Number )
> Advertising Router: 3.3.3.3
> LS Seq Number: 80000001
> Checksum: 0x623C
> Length: 36
> Network Mask: /24
> Metric Type: 2 (Larger than any link state path)
> TOS: 0
> Metric: 1
> Forward Address: 0.0.0.0
> External Route Tag: 0
>
> r3#
>
> **********************************************************************
> PowerTel Limited, winners of
> Best Corporate/Wholesale Broadband Initiative, Australian Telecom Awards 2002
> Broadband Wholesale Carrier of the year, CommsWorld Telecomms Awards 2001
> Best Emerging Telco, Australian Telecom Awards 2001
>
> **********************************************************************
> This email (including all attachments) is intended solely for the named
> addressee. It is confidential and may contain commercially sensitive
> information. If you receive it in error, please let us know by reply email,
> delete it from your system and destroy any copies.
>
> This email is also subject to copyright. No part of it should be reproduced,
> adapted or transmitted without the prior written consent of the copyright owner.
>
> Emails may be interfered with, may contain computer viruses or other defects
> and may not be successfully replicated on other systems. We give no
> warranties in relation to these matters. If you have any doubts about
> the authenticity of an email purportedly sent by us, please contact us
> immediately.
>
> **********************************************************************
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:55 GMT-3