From: Kevin M. Woods (kev@xxxxxxx)
Date: Fri Jun 02 2000 - 03:19:17 GMT-3
This is a bug (CSCdm75819). The description states:
If OSPF is configured using a "network x.x.x.x 0.0.0.0 area x"
command (explicitly identifying and interface), then the connected
interface information may not be properly redistributed into other
protocols (configured to "redistribute ospf xxx...").
Workaround: use a general mask instead ("network x.x.x.0 0.0.0.255
area x", for example).
Kevin
// hi,all:
//
// I have a quession about route redis following :
//
// e0 e0 s0 s0
// r1---------------r2---------------r3
// ospf100 eigrp 100
//
//
// r1:
//
// int e0
// ip add 137.20.20.1 255.255.255.0
//
// router ospf
// netw 137.20.20.1 0.0.0.0 area 0
//
//
// r2:
//
// int e0
// ip add 137.20.20.2 255.255.255.0
// int s0
// ip add 192.168.1.1 255.255.255.0
//
// router eigrp 100
// netw 192.168.1.1
// redis ospf 100 metric 10000 100 255 1 1500
//
// router ospf 100
// netw 137.20.20.2 0.0.0.0 area 0
//
//
// r3:
// int s0
// ip add 192.168.1.2 255.255.255.0
//
// router eigrp 100
// netw 192.168.1.0
//
// apply this config on router,i haven't seen 137.20.20.0 in r3 route table.
// i change my config in r2:
// r2:
//
// int e0
// ip add 137.20.20.2 255.255.255.0
// int s0
// ip add 192.168.1.1 255.255.255.0
//
// router eigrp 100
// netw 192.168.1.1
// redis ospf 100 metric 10000 100 255 1 1500
//
// router ospf 100
// netw 137.20.20.2 0.0.0.255 area 0 //changed//
//
// After changed,i can see this route about 137.20.20.0 in r3 route table,i fee
l puzzle, sb will give me idea about it?
//
//
//
//
//
//
//
// --------------------------
// Paul Wang (CCIE Candidate)
// E-Mail:chinawy@etang.com
// --------------------------
// 赶快参加CNNIC有奖调查，亿唐需要您的支持。
// http://fsurvey.cnnic.net.cn/survey/index.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:40 GMT-3