Cannot remove old VPN static route from Pix

Recently I removed a vpn that was routing traffic for a few subnets out my pix.
It looks like the pix will not remove the static routes that it created automatically.
Below are my static routes that are in the config and below that is the current routing table
The BOLD ones are the ones that should just go away.
On the peer firewall they went away as soon as I got rid of the access list pertaining to the vpn.  I have tried clear xlates, clear ip route ouside....but still cannot get it to go away.

Any help is appreciated.

route outside 0.0.0.0 0.0.0.0 99.123.123.1 1
route inside 10.0.0.0 255.255.255.0 192.168.13.1 1
route inside 10.0.10.0 255.255.255.0 192.168.13.1 1
route inside 10.0.11.0 255.255.255.0 192.168.13.1 1
route inside 10.0.13.0 255.255.255.0 192.168.13.1 1
route inside 10.0.14.0 255.255.255.0 192.168.13.1 1
route inside 10.0.16.0 255.255.255.0 192.168.13.1 1
route inside 192.168.0.0 255.255.0.0 192.168.13.1 1
route inside 192.168.1.164 255.255.255.255 192.168.13.1 1


Gateway of last resort is 99.123.123.1 to network 0.0.0.0

R    192.168.12.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
C    192.168.13.0 255.255.255.0 is directly connected, inside
R    192.168.14.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.15.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.8.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.9.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.10.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
C    99.123.123.0 255.255.255.192 is directly connected, outside
R    192.168.40.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.11.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.4.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
R    192.168.5.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:22, inside
S    10.0.10.0 255.255.255.0 [1/0] via 192.168.13.1, inside
S    10.0.11.0 255.255.255.0 [1/0] via 192.168.13.1, inside
S    10.0.14.0 255.255.255.0 [1/0] via 192.168.13.1, inside
S    10.0.13.0 255.255.255.0 [1/0] via 192.168.13.1, inside
S    10.0.0.0 255.255.255.0 [1/0] via 192.168.13.1, inside
C    10.1.0.0 255.255.255.0 is directly connected, dmz
S    10.0.16.0 255.255.255.0 [1/0] via 192.168.13.1, inside
S    10.10.254.0 255.255.255.0 [1/0] via 99.123.123.1, outside
R    192.168.6.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:23, inside
R    192.168.7.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:23, inside
S    192.168.254.0 255.255.255.0 [1/0] via 99.123.123.1, outside
R    192.168.1.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:23, inside
S    192.168.1.164 255.255.255.255 [1/0] via 192.168.13.1, inside
R    192.168.2.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:23, inside
R    192.168.3.0 255.255.255.0 [120/1] via 192.168.13.1, 0:00:23, inside
S*   0.0.0.0 0.0.0.0 [1/0] via 99.123.123.1, outside
S    192.168.0.0 255.255.0.0 [1/0] via 192.168.13.1, inside
LVL 2
brian_appliedcpuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Matt VCommented:
Have you tried:

no route outside 10.10.254.0 255.255.255.0  99.123.123.1
no route outside 192.168.254.0 255.255.255.0 99.123.123.1
0
brian_appliedcpuAuthor Commented:
Yes, it said they did not exist.
We eventually rebooted the firewall and it cleared the routes.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
brian_appliedcpuAuthor Commented:
Rebooting the router flushed the routes.   I think the firewall was just being stupid.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VPN

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.