Thanks for the response - sorry for my impatience. :-)
I dont mind the viewing discrepancy, its the fact that vyatta doesn't
recognize the existance of the routes - so I can't do anything with
them. So you're saying load config.boot should fix the problem? Will
that cause any downtime
No problem - I know exactly how you feel some days!
And I'd missed the point that it didn't make into the system route table, so the
first question I'd ask is whether the next hop you're specifying is
directly connected?
If it isn't, try using the IP address of the directly connected next hop
