Forum Discussion
Deon
Nimbostratus
NimbostratusLTM Object Naming Conventions
What naming conventions do people have in use for LTM objects - particularly VIPs and pools? When it comes to a VIP or pool name, where is the balance struck between cramming as much information into...
Hamish
Cirrocumulus
CirrocumulusVirtual servers and pools I tend to standardise on FQDN-port. That way if people know what they're connecting to (URL) then I know which VS it'll be hitting.
network VS's tend to be named net-net.num.dot.ed-masklen. e.g. net-0.0.0.0-0 is the default address. Where they conflict (e.g. two defaults depending on src clan, it gets an extra descriptor between net- and the ip address. e.g. net-wireless-0.0.0.0-0 (Default network VS for a wireless VLAN). I don't currently have any network VS's for specific ports. But they'd be something like net-0.0.0.0-0-port
Profiles tend to be default name and a short descriptor to show why they're different. e.g. fastL4-tmo86400 for fastL4 with a 1 day idle timeout.
Whatever you choose though. Be consistent. And have an index document. And diagrams. A diagram is worth it's weight in gold. Or more.
H
