<div dir="ltr">Thanks Donald, that did the trick. I had put the 42 in there out of habit, thinking the process ID was required. I did try to use the network command originally, but I got an error message saying that it can't be used with multi-instance OSPF. That should have clued me in that I had done something I didn't intend...<div><br></div><div>Thanks,</div><div>Chuck</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 14, 2019 at 6:15 AM Donald Sharp <<a href="mailto:sharpd@cumulusnetworks.com">sharpd@cumulusnetworks.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Chuck -<br>
<br>
As a side note-> subscribing to the frog alias will prevent me from<br>
having to approve your post.<br>
<br>
1) Make it `router ospf vrf WAN`. I am not aware of ospf views and<br>
vrf's actually being tested when mixed.<br>
2) Use `network A.B.C.D/M area 0.0.0.0` to tell ospf what mask to use<br>
to select interfaces for being used. The range command is about<br>
summarization of data that ospf already knows about.<br>
<br>
<a href="http://docs.frrouting.org/en/latest/ospfd.html" rel="noreferrer" target="_blank">http://docs.frrouting.org/en/latest/ospfd.html</a><br>
<br>
odnald<br>
<br>
On Thu, Mar 14, 2019 at 8:07 AM Chuck Cox <<a href="mailto:chuck@chezcox.net" target="_blank">chuck@chezcox.net</a>> wrote:<br>
><br>
> Hi folks,<br>
><br>
> I'm trying to set up a lab environment to test some OSPF stuff. I installed the FRR 6.0.2-0~ubuntu18.04.1 package on top of Ubuntu 18.10.<br>
><br>
> I elected to leave my management interface (ens3) in the default VRF and put the others in a VRF called "WAN", shown as item #10 below:<br>
> $ ip link<br>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000<br>
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br>
> 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:68:bb:72 brd ff:ff:ff:ff:ff:ff<br>
> 3: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:ed:f8:ad brd ff:ff:ff:ff:ff:ff<br>
> 4: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:07:11:c7 brd ff:ff:ff:ff:ff:ff<br>
> 5: ens11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:6e:51:76 brd ff:ff:ff:ff:ff:ff<br>
> 6: ens12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:bf:5d:f3 brd ff:ff:ff:ff:ff:ff<br>
> 7: ens13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:f5:24:55 brd ff:ff:ff:ff:ff:ff<br>
> 8: ens14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:d3:1d:30 brd ff:ff:ff:ff:ff:ff<br>
> 9: ens15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master WAN state UP mode DEFAULT group default qlen 1000<br>
> link/ether 52:54:00:e3:cf:dd brd ff:ff:ff:ff:ff:ff<br>
> 10: WAN: <NOARP,MASTER,UP,LOWER_UP> mtu 65536 qdisc noqueue state UP mode DEFAULT group default qlen 1000<br>
> link/ether 06:6a:07:90:27:3a brd ff:ff:ff:ff:ff:ff<br>
><br>
> "ip route" correctly shows only the connected subnet route for the management net and a default:<br>
> $ ip route<br>
> default via 192.168.42.1 dev ens3 proto static<br>
> <a href="http://192.168.42.0/24" rel="noreferrer" target="_blank">192.168.42.0/24</a> dev ens3 proto kernel scope link src 192.168.42.153<br>
><br>
> And the other connected routes in the VRF:<br>
> $ ip route show vrf WAN<br>
> unreachable default metric 4278198272<br>
> <a href="http://172.16.1.0/24" rel="noreferrer" target="_blank">172.16.1.0/24</a> dev ens9 proto kernel scope link src 172.16.1.1<br>
> <a href="http://172.17.1.0/24" rel="noreferrer" target="_blank">172.17.1.0/24</a> dev ens14 proto kernel scope link src 172.17.1.1<br>
> <a href="http://192.0.2.0/24" rel="noreferrer" target="_blank">192.0.2.0/24</a> dev ens10 proto kernel scope link src 192.0.2.1<br>
> <a href="http://198.51.100.0/24" rel="noreferrer" target="_blank">198.51.100.0/24</a> dev ens11 proto kernel scope link src 198.51.100.1<br>
> <a href="http://203.0.113.0/24" rel="noreferrer" target="_blank">203.0.113.0/24</a> dev ens12 proto kernel scope link src 203.0.113.1<br>
><br>
> What I see inside vtysh matches:<br>
> $ ip route show vrf WAN<br>
> unreachable default metric 4278198272<br>
> <a href="http://172.16.1.0/24" rel="noreferrer" target="_blank">172.16.1.0/24</a> dev ens9 proto kernel scope link src 172.16.1.1<br>
> <a href="http://172.17.1.0/24" rel="noreferrer" target="_blank">172.17.1.0/24</a> dev ens14 proto kernel scope link src 172.17.1.1<br>
> <a href="http://192.0.2.0/24" rel="noreferrer" target="_blank">192.0.2.0/24</a> dev ens10 proto kernel scope link src 192.0.2.1<br>
> <a href="http://198.51.100.0/24" rel="noreferrer" target="_blank">198.51.100.0/24</a> dev ens11 proto kernel scope link src 198.51.100.1<br>
> <a href="http://203.0.113.0/24" rel="noreferrer" target="_blank">203.0.113.0/24</a> dev ens12 proto kernel scope link src 203.0.113.1<br>
> router# sho ip ro vrf WAN<br>
> Codes: K - kernel route, C - connected, S - static, R - RIP,<br>
> O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,<br>
> T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,<br>
> F - PBR,<br>
> > - selected route, * - FIB route<br>
><br>
><br>
> VRF WAN:<br>
> K * <a href="http://0.0.0.0/0" rel="noreferrer" target="_blank">0.0.0.0/0</a> [255/8192] unreachable (ICMP unreachable), 04:04:10<br>
> C>* <a href="http://172.16.1.0/24" rel="noreferrer" target="_blank">172.16.1.0/24</a> is directly connected, ens9, 04:04:10<br>
> C>* <a href="http://172.17.1.0/24" rel="noreferrer" target="_blank">172.17.1.0/24</a> is directly connected, ens14, 04:04:10<br>
> C>* <a href="http://192.0.2.0/24" rel="noreferrer" target="_blank">192.0.2.0/24</a> is directly connected, ens10, 04:04:10<br>
> C>* <a href="http://198.51.100.0/24" rel="noreferrer" target="_blank">198.51.100.0/24</a> is directly connected, ens11, 04:04:10<br>
> C>* <a href="http://203.0.113.0/24" rel="noreferrer" target="_blank">203.0.113.0/24</a> is directly connected, ens12, 04:04:10<br>
><br>
><br>
> So far so good. Now I enabled ospfd in /etc/frr/daemons and restarted FRR. The ospfd process is running:<br>
> $ ps -ef|grep frr<br>
> root 2045 1 0 13:31 ? 00:00:02 /usr/lib/frr/watchfrr -d -r /usr/lib/frr/watchfrr.sh restart %s -s /usr/lib/frr/watchfrr.sh start %s -k /usr/lib/frr/watchfrr.sh stop %s zebra ospfd staticd<br>
> frr 2059 1 0 13:31 ? 00:00:00 /usr/lib/frr/zebra -d -A 127.0.0.1 -s 90000000<br>
> frr 2064 1 0 13:31 ? 00:00:01 /usr/lib/frr/ospfd -d -A 127.0.0.1<br>
> frr 2069 1 0 13:31 ? 00:00:00 /usr/lib/frr/staticd -d -A 127.0.0.1<br>
><br>
> Then I put in some seemingly basic OSPF config shown below. Yes, I really only want to speak OSPF on one of the interfaces (ens14) for now.<br>
> router# sho run<br>
> Building configuration...<br>
><br>
> Current configuration:<br>
> !<br>
> frr version 6.0.2<br>
> frr defaults traditional<br>
> hostname router<br>
> log syslog informational<br>
> no ipv6 forwarding<br>
> service integrated-vtysh-config<br>
> !<br>
> interface ens3<br>
> description MGMT<br>
> !<br>
> interface ens9 vrf WAN<br>
> description ServerLAN<br>
> ip address <a href="http://172.16.1.1/24" rel="noreferrer" target="_blank">172.16.1.1/24</a><br>
> !<br>
> interface ens10 vrf WAN<br>
> description MPLS<br>
> ip address <a href="http://192.0.2.1/24" rel="noreferrer" target="_blank">192.0.2.1/24</a><br>
> !<br>
> interface ens11 vrf WAN<br>
> description PtP<br>
> ip address <a href="http://198.51.100.1/24" rel="noreferrer" target="_blank">198.51.100.1/24</a><br>
> !<br>
> interface ens12 vrf WAN<br>
> description Satellite<br>
> ip address <a href="http://203.0.113.1/24" rel="noreferrer" target="_blank">203.0.113.1/24</a><br>
> !<br>
> interface ens13 vrf WAN<br>
> description Inet<br>
> !<br>
> interface ens14 vrf WAN<br>
> description SD-WAN<br>
> ip address <a href="http://172.17.1.1/24" rel="noreferrer" target="_blank">172.17.1.1/24</a><br>
> !<br>
> interface ens15 vrf WAN<br>
> description XAXD-LAN<br>
> !<br>
> router ospf 42 vrf WAN<br>
> ospf router-id 172.17.1.1<br>
> redistribute connected<br>
> passive-interface ens9<br>
> passive-interface ens10<br>
> passive-interface ens11<br>
> passive-interface ens12<br>
> passive-interface ens13<br>
> passive-interface ens15<br>
> area 0.0.0.0 range <a href="http://10.0.0.0/8" rel="noreferrer" target="_blank">10.0.0.0/8</a><br>
> area 0.0.0.0 range <a href="http://172.16.0.0/20" rel="noreferrer" target="_blank">172.16.0.0/20</a><br>
> area 0.0.0.0 range <a href="http://192.0.2.0/24" rel="noreferrer" target="_blank">192.0.2.0/24</a><br>
> area 0.0.0.0 range <a href="http://192.168.0.0/16" rel="noreferrer" target="_blank">192.168.0.0/16</a><br>
> area 0.0.0.0 range <a href="http://198.51.100.0/24" rel="noreferrer" target="_blank">198.51.100.0/24</a><br>
> area 0.0.0.0 range <a href="http://203.0.113.0/24" rel="noreferrer" target="_blank">203.0.113.0/24</a><br>
> default-information originate<br>
> !<br>
> line vty<br>
> !<br>
> end<br>
><br>
><br>
> Now here's the problem: OSPF appears to be running but it's not doing anything and none of the show commands give any output, except "sho ip ospf vrf/vrfs":<br>
> router# sho ip ospf vrf<br>
> Name Id RouterId<br>
> Default-IP-Routing-Table 0 0.0.0.0<br>
> WAN 10 172.17.1.1<br>
><br>
> Total number of OSPF VRFs: 2<br>
> router# sho ip ospf vrfs<br>
> Name Id RouterId<br>
> Default-IP-Routing-Table 0 0.0.0.0<br>
> WAN 10 172.17.1.1<br>
><br>
> Total number of OSPF VRFs: 2<br>
> router# sho ip ospf vrf WAN dat<br>
> router# sho ip ospf vrf WAN int<br>
> router# sho ip ospf vrf WAN nei<br>
> router# sho ip ospf vrf WAN route<br>
> router# sho ip ospf dat<br>
> router# sho ip ospf int<br>
> router# sho ip ospf nei<br>
> router# sho ip ospf route<br>
><br>
> Any suggestions? I've restarted FRR a couple of times and rebooted the box too, same results...<br>
><br>
> Thanks,<br>
> Chuck<br>
><br>
><br>
> _______________________________________________<br>
> frog mailing list<br>
> <a href="mailto:frog@lists.frrouting.org" target="_blank">frog@lists.frrouting.org</a><br>
> <a href="https://lists.frrouting.org/listinfo/frog" rel="noreferrer" target="_blank">https://lists.frrouting.org/listinfo/frog</a><br>
</blockquote></div>