We do the following. Subnet = 3rd octect of ip
IP= 4th octect of IP
all gear is in the cc.buffalo.edu domain.
ex. AP 10.3.80.1 = wls-capen80-1.cc.buffalo.edu
Terminal Server tsx-(building)(subnet)-(IP#).cc.buffalo.edu
Switch on VLAN 1 sw-(building)(subnet)-(IP#).cc.buffalo.edu
Building Switch bsw-(building)(subnet)-(IP#).cc.buffalo.edu
Console Server tsx-(building)(subnet)-(IP#).cc.buffalo.edu
Layer 3 Switch l3sw-(building)(subnet)-(IP#).cc.buffalo.edu
Wireless Access Point wls-(building)(subnet)-(IP#).cc.buffalo.edu
On 02/02/2016 12:38 PM, Norman Chu wrote:
We’re looking for ideas to improve our current naming convention for
network devices.
For an access point, it currently consists of:
<buildingName>-<floornumber>-ap<arbitrarynumber>
e.g. burnside-1-ap24
For controllers, we use:
wireless-<its role>-wmc
e.g. wireless-local1-wmc
(wmc = wireless mobility controller)
For access points, we’re thinking of adding location info instead of
the arbitrary number, so something like: burnside-1-ap101a where 101a
is the first AP in room 101 (101b would be the second AP, etc.)
Switches: burnside-sw1, burnside-sw2
UPS’s: burnside-ups-1, burnside-ups2-1
PoE midspans: burnside-poe-1, burnside-poe2-1
What do other organizations use for naming conventions for their
network devices?
Thanks.
Norman Chu
Network Analyst – Network Infrastructure group
Systems Engineering – McGill NCS
(514) 398-7299
********** Participation and subscription information for this
EDUCAUSE Constituent Group discussion list can be found at
http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
