I have three redundant routes being advertised in OSPF. Two from one SRX and the thrid on another SRX. How can I setup preference to the larger 10G circut, then to the 1G and then to the Flex100mb/1gb circut ? I tried adding the metric to the interface but that didn't seam to add the metric to the route. The routes are being advertised as directly connected. There are no static routes being advertised.
Please post the "show route protocol ospf <blah/blah> extensive" for each of the redundant routes You are concerned about.
Secondly, You want to assign metric to links, not routes.
Generally, if You want to ALWAYS prefer 10G link over 1G link over 100/1000 link, then :
1/ make sure these routes are NOT LSA-5/Type-5 External with Type 2 metric. Either LSA-1/Type-1, LSA-3/Type-3 or LSA-5/Type-5 with External Type-1 metric will do. Your OSPF design (single area/multiarea/multiarea with stub/NSSA areas) would dictate what LSA/Type is appropriate.
2/ assign metric in ascending fashion to ALL Your 10G/1G/100 links, such as
10G - metric 1000
1G - metric 10000
100 - metric 100000
You could use bandwidth-based metric with "reference-bandwidth" statement but
(a) it has limited applicability - 100G link can only have min metric 1 meaning 100GE LAG with 2 or more links also will get auto-assigned metric 1,
(b) it prevents load-balance across unequal-bandwidth links, such as if You have 2 parallel LAGs of 3x10GE and 4x10GE, You'd want to load-balance in order not to waste that expensive BW but if You used bandwidth-based link metrics, OSPF won't allow You to do that. There are ways to LB across unequal-BW unequal-cost links but it involves MPLS (RSVP-TE or SRTE) and is probably too much at this point.
Anyway, back to topic - the route printouts You shared earlier indicate Your SRXes receive 0/0 LSA5 Type-2 routes from the interfaces I mentioned. If this is indeed the case and not a result of some left-behind config from previous t'shooting attempts, then You need to contact the admins for the boxes that are connected to aforementioned SRX interfaces and tell them to change the 0/0 route to be advertised to Your SRXes as LSA5 Type-1. Then You can add metric to Your links and live happily ever after.