Just had this come up in a meeting and it sounds very reasonable.
When entering a static route, use the "name" function, if available, to comment what the route is for. This can be very helpful when troubleshooting L3 issues and in understanding connectivity patterns.
Too bad ASA firewalls can't do that, but at least our core and distro switches can do it.
Quote from: deanwebb on June 05, 2017, 10:09:24 AM
Just had this come up in a meeting and it sounds very reasonable.
When entering a static route, use the "name" function, if available, to comment what the route is for. This can be very helpful when troubleshooting L3 issues and in understanding connectivity patterns.
Too bad ASA firewalls can't do that, but at least our core and distro switches can do it.
:zomgwtfbbq:
on the ASA
access-list OUTSIDE_IN remark *****************************************************
Quote from: ristau5741 on June 05, 2017, 10:37:23 AM
Quote from: deanwebb on June 05, 2017, 10:09:24 AM
Just had this come up in a meeting and it sounds very reasonable.
When entering a static route, use the "name" function, if available, to comment what the route is for. This can be very helpful when troubleshooting L3 issues and in understanding connectivity patterns.
Too bad ASA firewalls can't do that, but at least our core and distro switches can do it.
:zomgwtfbbq:
on the ASA
access-list OUTSIDE_IN remark *****************************************************
:doh:
I was looking for the "name" command in the syntax! :lol:
My ex colleague introduced this to our configuration guidelines and I must admit it's pretty damn handy. But for some reason I seem to remember from some syntax guide that it was intended to specify the name of the next-hop. Could be remembering it wrong though.
We started doing this on our retail routers. Oddly enough the command does not work when adding static routes for DHCP. No problem with static or PPPoE routes. I agree that it is helpful.
Definitely helps track static routes! Especially at a time when you're debugging and you go "WTF is that in there"... and then you read "... name Static route for XXX" - and then you just know. :smug: