This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
PAN-OS 9.0 Static Route Commit Warning
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- Discussions
- General Topics
- PAN-OS 9.0 Static Route Commit Warning
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
PAN-OS 9.0 Static Route Commit Warning
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
02-15-2019 08:48 AM
Just a note here that I am getting a cosmetic warning during commit of a newly-upgraded PA-220 (my lab box) to PAN-OS 9.0.
Prior to the upgrade, I had a static route in my virtual router, to redirect all traffic going to 192.168.1.0/24 to my tunnel.4 interface (which is an IPSec tunnel to another firewall). The route does not specify a next-hop IP, just to throw it on the tunnel interface and be done with it. This has always worked fine (and still does, in fact), but when I commit, I get the following warning in the commit log:
- Static route AmericanEagle next hop IP 0.0.0.0 is not in subnet of outgoing interface tunnel.4
- (Module: routed)
Again, it's not a problem, but I know a LOT of people do this. It's a cosmetic error, and my routing is still working as-expected. I just wanted to notify people...
Mark Rosenecker
6 REPLIES 6
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
02-19-2019 03:01 AM
did you reach out to support about this ?
Tom Piens
PANgurus - SASE and Strata specialist; (co)managed services, VAR and consultancy
PANgurus - SASE and Strata specialist; (co)managed services, VAR and consultancy
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
04-02-2019 02:37 AM
@holbem @MarkRosenecker have either of you reported this to support already?
It can't be resolved until TAC is informed and let investigate the issue
Tom Piens
PANgurus - SASE and Strata specialist; (co)managed services, VAR and consultancy
PANgurus - SASE and Strata specialist; (co)managed services, VAR and consultancy
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
04-05-2019 03:35 AM
I got the same warning a couple of times, now it stopped even though I didn't change routing configuration.
Related Content
- shadowed rules not showing in cli commit in General Topics
- How to form alerting on AIOps in AIOps for NGFW Discussions
- Announcing AIOps for NGFW 2.5 in AIOps for NGFW Discussions
- Cannot connect Log Collector to Panorama in Panorama Discussions
- No Valid DNS Security License - Resolved in General Topics
Like what you see?
Show your appreciation!
Click Like if a post is helpful to you or if you just want to show your support.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks