From: Pun, Alec CL (Alec.CL.Pun@pccw.com)
Date: Thu Nov 06 2003 - 07:35:10 GMT-3
The prefix 180.100.13.0/24 can not seen as a best route. Synchronization is
enabled in R6. I guess it should be the synchronization problem (maybe the
ADV router ID ??), but the prefix already exist on both the BGP and routing
table.
Can anyone advise the rule of thumb ? How can I know OSPF & BGP ADV router
of prefix from the below extract ?
Many thanks
alec
R6#sh ip bgp
BGP table version is 61, local router ID is 153.3.6.6
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i180.100.13.0/24 153.3.1.1 0 100 0 113 ?
*> 208.0.0.0/4 153.3.5.5 0 100 65007 i
R6#sh ip bgp 180.100.13.0
BGP routing table entry for 180.100.13.0/24, version 61
Paths: (1 available, no best path)
Flag: 0x208
Not advertised to any peer
113
153.3.1.1 (metric 12) from 153.3.35.35 (153.3.35.35)
Origin incomplete, metric 0, localpref 100, valid, internal, not
synchronized
Originator: 153.3.1.1, Cluster list: 153.3.35.35
R6#sh ip route ospf | inc 180.100.13.0
O E2 180.100.13.0 [110/1] via 153.3.66.35, 00:18:37, Ethernet0/0
R6#sh ip ospf data ex | be 180.100.13.0
Link State ID: 180.100.13.0 (External Network Number )
Advertising Router: 153.3.1.1
LS Seq Number: 80000001
Checksum: 0x2657
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: 113
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:08 GMT-3