Configuration naming conventions: ERL, ASA, etc
-
For my Edge Router Lite, I'm considering whether or not I want to create address groups for single hosts. My reasoning for "yes" would be I'd configure an IP address in one place (the address group), and then multiple configuration aspects can reference that address group. If the IP address of the host in question changes, then I only have to update one thing.
I'm curious to know if you folks do the same for your devices. I know ASA's have objects, which function similarly to the idea of an address group.
-
@eddiejennings said in Configuration naming conventions: ERL, ASA, etc:
For my Edge Router Lite, I'm considering whether or not I want to create address groups for single hosts. My reasoning for "yes" would be I'd configure an IP address in one place (the address group), and then multiple configuration aspects can reference that address group. If the IP address of the host in question changes, then I only have to update one thing.
I'm curious to know if you folks do the same for your devices. I know ASA's have objects, which function similarly to the idea of an address group.
I make that a judgment call each time it comes up. But yes, in general, it is the best way to handle it. You only need to update one thing later.
-
@eddiejennings said in Configuration naming conventions: ERL, ASA, etc:
For my Edge Router Lite, I'm considering whether or not I want to create address groups for single hosts. My reasoning for "yes" would be I'd configure an IP address in one place (the address group), and then multiple configuration aspects can reference that address group. If the IP address of the host in question changes, then I only have to update one thing.
I'm curious to know if you folks do the same for your devices. I know ASA's have objects, which function similarly to the idea of an address group.
Sonicwall are Address Objects and there are groups as well. So yeah I do that.
