Junos OS

   Hi junos Jedi Masters,

   I'm trying to redistribute a garden-variety IPv4 static route into OSPF3.  I'm annoyed to see that the route is redistributed via OSPF (ver 2) and the IPv6 counterpart of the route is redistributed via OSPF3.  But I need the v4 stat route viaible inside OSPF3.  For right now, my test static route is for 101.101.101.101/32:

root@MY-VSRX> show configuration | display set | match ...blah blah...
set routing-options static route 101.101.101.101/32 discard
set protocols ospf3 export testStaticToOSPF3
set policy-options policy-statement testStaticToOSPF3 term 1 from protocol static
set policy-options policy-statement testStaticToOSPF3 term 1 then accept
root@MY-VSRX>

I would have thought the above would do it; the counterpart commands work for redistributing IPv4 stat's into OSPF and IPv6 stat's into OSPF3.  So why not IPv4 stat's into OSPF3?  Do I have to expressly enable IPv4 in OSPF3 or something?  I thought no, because I do already see non-static IPv4 routes advertised within OSPF3.  So why are the IPv4 static routes not redistributing?

BTW, here's my version info:

root@MY-VSRX> show version
Hostname: MY-VSRX
Model: vsrx
Junos: 15.1X49-D64
JUNOS Software Release [15.1X49-D64]
root@MY-VSRX>

Any insight and/or advice will be wildly appreciated.

          -P

Try this

set protocols ospf3 realm ipv4-unicast export testStaticToOSPF3

HTH

Thanks Singhh,

   No luck, I'm afraid.  Here's my current config for this:

root@MY-VSRX> show configuration | display set | match ...blah blah...
set routing-options static route 101.101.101.101/32 discard
set protocols ospf3 realm ipv4-unicast export testStaticToOSPF3
set protocols ospf3 export testStaticToOSPF3
set policy-options policy-statement testStaticToOSPF3 term 1 from protocol static
set policy-options policy-statement testStaticToOSPF3 term 1 then accept
root@MY-VSRX>

I'm sensing this is not a quick, one-command fix.  Would a JTAC case be a better way to deep dive on this?

     Thanks,

         -RAO

Hi Rao,

Can you share your ospf3 configuration? and the interface configuration which is configured in ospf3

Thanks Singhh,

   I did open a JTAC case with my company's support contract.  It turns out the issue is more complex than I realized, prob too in-depth for a forum post.  In fact, my engineer is currently lab'ing up my topology.  But thanks for being willing to take a look.

      Yrs,

          -ROA

Are you running both IPv6 and Ipv4 between your ospf neighbors?

root@R1_re# show protocols ospf3
realm ipv4-unicast {
export test;
area 0.0.0.0 {
interface ge-0/0/4.0;
}
}
area 0.0.0.0 {
interface ge-0/0/4.0;
}

[edit]
root@R1_re#

root@R1_re# show policy-options
policy-statement test {
from {
protocol static;
route-filter 10.100.100.100/32 exact;
}
then accept;
}

[edit]
root@R1_re#

root@R2_re# show protocols ospf3
realm ipv4-unicast {
area 0.0.0.0 {
interface ge-0/0/1.0;
}
}
area 0.0.0.0 {
interface ge-0/0/1.0;
}

[edit]
root@R2_re#

[edit]
root@R2_re# run show route 10.100.100.100

inet.0: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.0.0/8 *[Static/5] 5d 06:48:10
> to 10.49.127.254 via fxp0.0

[edit]
root@R2_re# activate interfaces ge-0/0/1.0 family inet

[edit]
root@R2_re# commit
commit complete

[edit]
root@R2_re# run show route 10.100.100.100

inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.100.100.100/32 *[OSPF3/150] 00:00:05, metric 0, tag 0
> to 10.0.0.2 via ge-0/0/1.0

You need to enable realm ipv4-unicast neighborship as well between your ospf3 neighbours.

HTH.