DHCP Scope Naming Convention

At my company we are looking to utilize the IPAM feature in Orion. As of right now our DHCP scope names are very inconsistent and we don't have a standard for naming them. Does anyone have any recommendations on how to go about standardizing them? We want to be able to sort and filter through IPAM to help us locate certain subnets easier and just overall be more consistent with what we decide to call things.

Find more posts tagged with

dhcp

scope

ipam

Accepted answers

All comments

jm_sysadmin

We include 3 things in our DHCP naming convention, and it aligns with how we use subnets.

Function - basically a designation for general use, or identify a specfic one, say guest wireless, dmz for iot devices, etc. We started with plain English descriptions, now we are moving to using a letter and number code to identify it, and yes we use a spreadsheet to track it. But the code shortens the name, and all the normal uses you learn pretty quickly.

Location - Campus, building, floor, whatever you need to understand where the scope will be allowed. Currently we use Engineering building/floor codes with a plain text campus prefix.

Vlan - just the number of the vlan we associate with this.

Anything else we store in custom properties in IPAM.

Jpdis3

Thank you for the response! I was thinking of including similar info. I want our names to be meaningful, but not overly busy at the same time. I think your 3 categories will be perfect for what we are looking to do.