hi,
SRX can be a OSPF ABR, no problem. But there is no need for additional area if you want to send just summary route.
What's the source of contributing routes (10.66.x.x/24 ?) Static routes, direct/interface ?
If 10.66.x.x/24 is direct route, just add the interface as a passive under OSPF. - you already know it works.
The universal solution is it too create OSPF export policy and redistribute any route you want, including summary (aggregate) route 10.66.x.x/16.
Example config, use it as a template (using routing-instances for testing - VR2 and VR3 as OSPF peers).
// VR2 - interface routes matching 10.64/16
admin@srx> show route table VR2 protocol direct 10.64/16 terse
VR2.inet.0: 18 destinations, 21 routes (18 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination P Prf Metric 1 Metric 2 Next hop AS path
* 10.64.0.0/24 D 0 >fe-0/0/4.100
* 10.64.1.0/24 D 0 >fe-0/0/4.101
* 10.64.2.0/24 D 0 >fe-0/0/4.102
// create aggregate ('route to null')
admin@srx> show configuration routing-instances VR2 routing-options
aggregate {
route 10.64.0.0/16 discard;
}
// verifying - please notice 'Contributing Routes' below
admin@srx> show route table VR2 10.64/16 exact detail
VR2.inet.0: 18 destinations, 21 routes (18 active, 0 holddown, 0 hidden)
10.64.0.0/16 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop type: Discard
Address: 0x13cd8ec
Next-hop reference count: 12
State: <Active Int Ext>
Local AS: 65002
Age: 14:03
Task: Aggregate
Announcement bits (4): 0-KRT 1-BGP RT Background 3-Resolve tree 2 4-VR2-OSPF
AS path: I (LocalAgg)
Flags: Discard Depth: 0 Active
AS path list:
AS path: I Refcount: 3
Contributing Routes (3):
10.64.0.0/24 proto Direct
10.64.1.0/24 proto Direct
10.64.2.0/24 proto Direct
// policy - what we want to inject into OSPF (external route)
admin@srx> show configuration policy-options policy-statement VR2-exp-aggr
term 10 {
from {
protocol aggregate;
route-filter 10.64.0.0/16 exact;
}
then accept;
}
// apply the export policy under OSFP
admin@srx> show configuration routing-instances VR2 protocols ospf
export VR2-exp-aggr;
area 0.0.0.0 {
interface lt-0/0/0.123;
interface lt-0/0/0.121;
}
// OSPF LSDB have the 10.64.0.0/16 route now, exported by VR2
admin@srx> show ospf database instance VR2 external lsa-id 10.64.0.0
OSPF AS SCOPE link state database
Type ID Adv Rtr Seq Age Opt Cksum Len
Extern *10.64.0.0 10.64.0.1 0x80000001 611 0x22 0x1904 36
The OSPF peer VR3 got the 10.64.0.0/16:
// the route is seen on a OSPF peer route
admin@srx> show route table VR3 protocol ospf terse 10.64.0.0
VR3.inet.0: 8 destinations, 9 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination P Prf Metric 1 Metric 2 Next hop AS path
* 10.64.0.0/16 O 150 0 >lt-0/0/0.132
Please digest it carefully,
jtb