Question on operation of "static" command...

[abatson]

I have a requirement to protect a single system using the Max. Embryonic Connections tag on the end of the 'static' command. However, the entire class-C subnet this machine is on, already is covered under a broad static for the entire subnet.

Question: Are static commands like routing commands in IOS, where the more specific route trumps the more generic route? See---->

If I have a static that publishes 10.1.1.0 (class-C), but I put another static in, with *different parameters* for 10.1.1.27/32, which one takes affect??

-Alex

[scoclayton]

Alex,

Statics are parsed top to bottom in the order they appear in your config. This would be similar to how IOS parses ACL's rather than routes. So, to answer your question, if the more specific static is higher in the list than the more general static, it will be used.

Hope this makes sense.

Scott

[abatson]

I understand; everything is parsed in order. With this, If I put the more specific line under the more general line, that will buy me what I want. I'll have 10.1.1.0 (class C) with one set of properties, and the 10.1.1.27/32 with a seperate set of proprties, correct?

-Alex

[scoclayton · Accepted solution]

Based on my understanding of what you are trying to accomplish, I would think you would want it the other way around - the specific static for 10.1.1.27 should be higher in the order than the more general 10.1.1.0 static. This way, if an xlate needs to be built for the 10.1.1.27 host, the specific static will take it. If the xlate is for something else in the 10.1.1.0 subnet, it will bypass the specific static and hit the more general one. Make sense?

Scott