Out of the blue, the ospf routes failed on our ER-8Pro today.
I started getting calls that the customers had no access, yet we could see them. it took a few minutes to realize that there were no ospf routes in the ER-8Pro.
Network:
[Bunch of Networks] <---> ERx [192.168.0.254] <---> HP Switch <---> ER-8Pro [192.168.0.1] <---> Internet
The ER-8Pro fed a default route through ospf through the rest of the network. I know the network's ospf is working because I have servers attached to the HP switch running ospf daemons due to the odd network. (Since the Internet is the default route, all the servers see a redirect as they try the router first and then are redirected to the ERx for Network IPs. With ospf on the servers, they know that 192.168.0.254 is the gateway to the network. All ospf routes from the ERx are still showing up on the servers. All routers on the other side of the ERx see all ospf routes as they should.
The issue seems to have cropped up after one of the servers was upgraded. However, I can find no errors in the server config and the ERx is still passing routes to them. It is only the ER-8Pro that can't see the routes.
The ER-8Pro cannot see any neighbors or routes. It's as though the daemon isn't running, but it is. The router wasn't touched during the server upgrade. (all routers are running 1.8.0).
We have bandaided it with static routes, but I'd sure like ospf back.
Any ideas?