just as i thought...
an eigrp enterprise does not necessarily have to migrate to opsf to include juniper in a cisco environment... as i surmised in the last post, just set up an ospf interface on the eigrp router, connect that to the juniper equipment and redistribute on the cisco side...
r1#sh ip route eigrp
Gateway of last resort is not set
1.0.0.0/24 is subnetted, 1 subnets
D 1.1.1.0 [90/156160] via 10.1.1.2, 01:07:49, FastEthernet1/0
2.0.0.0/24 is subnetted, 1 subnets
D 2.2.2.0 [90/156160] via 10.1.1.2, 01:07:49, FastEthernet1/0
r1#sh ip eigrp neigh
EIGRP-IPv4 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.1.1.2 Fa1/0 13 01:07:58 236 1416 0 4
r1 is connected to eigrp 1 on r2... i set up f1/1 on r1 to connect to a juniper router to bridge the gap, and redistributed eigrp into ospf, and vice versa...
root@junos1> show route
inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.1.0/24 *[Direct/0] 00:58:53
> via em0.0
192.168.1.2/32 *[Local/0] 00:58:53
Local via em0.0
224.0.0.5/32 *[OSPF/10] 00:51:44, metric 1
MultiRecv
after two way redistribution on the cisco side...
router eigrp 1
network 10.1.1.0 0.0.0.255
redistribute ospf 1 metric 1 0 1 1 1500
!
router ospf 1
redistribute eigrp 1 subnets
network 192.168.1.0 0.0.0.255 area 0
we have...
r2#sh ip route eigrp
Gateway of last resort is not set
D EX 192.168.1.0/24 [170/2560002560] via 10.1.1.1, 00:01:35, FastEthernet1/0
root@junos1> show route
inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.0/24 *[OSPF/150] 00:02:06, metric 20, tag 0
> to 192.168.1.1 via em0.0
2.2.2.0/24 *[OSPF/150] 00:02:06, metric 20, tag 0
> to 192.168.1.1 via em0.0
10.1.1.0/24 *[OSPF/150] 00:02:06, metric 20, tag 0
> to 192.168.1.1 via em0.0
192.168.1.0/24 *[Direct/0] 01:02:59
> via em0.0
192.168.1.2/32 *[Local/0] 01:02:59
Local via em0.0
224.0.0.5/32 *[OSPF/10] 00:55:50, metric 1
MultiRecv
root@junos1> ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes
64 bytes from 2.2.2.2: icmp_seq=0 ttl=254 time=57.377 ms
64 bytes from 2.2.2.2: icmp_seq=1 ttl=254 time=62.538 ms
64 bytes from 2.2.2.2: icmp_seq=2 ttl=254 time=63.248 ms
^C
--- 2.2.2.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 57.377/61.054/63.248/2.616 ms
no problem... as expected... like peas and carrots...
