We're a small school, so we can be fairly simplistic.  APs are named for the 
building they are in along with the room number they are in or the room number 
they are closest to.  In some cases, it's not a number but a name, so you will 
see names such as

Vaughn-101
JaneFreeman-204
Washington-Parlor

If we have a large space with multiple APs, the we have letter designators
Harris-Lecture-A
Harris-Lecture-B

Controllers are equally simplistic.  We are not so large as to require multiple 
controllers one a single campus, so they are simply named by campus 
location-Misenheimer, Charlotte, RTP.

For switches, it's a bit more varied.  In the server facility, they are named 
by model # and a designator, so dc4500X-1.  When you get into the network 
switches, it's back to building names in the format building-floor-designator.  
Let's say we are in Merner Hall on the second floor in a rack with 3 switches.  
If each switch is managed individually (not stacked for some reason), from top 
to bottom they would be

MernerHall-2-1
MernerHal-l2-2
MernerHal-l2-3

If they are stacked, it would be MernerHall-2-Stack.

One thing I have mandated is to physically label each switch with its name and 
IP address.  Sounds foolish; you'd think everyone would do it.  They didn't do 
it when I arrived, and you'd be amazed how much extra effort was expended 
because of that.  We also label interconnect cables on both ends with the name 
of what is on the other end.  So a fiber run from Administration to Physical 
Plant is labeled Physical Plant on the Admin end and Administration on the 
Plant Ops end.  From my point of view, you can never document too much.

Bill Seward   |   Director of Information Technology

Office of Information Technology
P.O. Box 960   |   48380 US Hwy 52
Misenheimer, NC  28109
Office  704-463-3066   |   Fax  704-463-1363
pfeiffer.edu<http://www.pfeiffer.edu/>   |   
facebook.com/PfeifferUniversity<http://www.facebook.com/pfeifferuniversity>   | 
  @Pfeiffer1885<http://www.twitter.com/pfeiffer1885>
instagram/PfeifferUniversity  <http://www.instagram.com/pfeifferuniversity>  |  
 
youtube.com/PfeifferUniversity<http://www.youtube.com/channel/UClrggh7TvtboLiHdS-kKHzQ>

For assistance with an IT-related issue, call Tech Support at 704-463-3002 or 
email us at [email protected]
[advancement:public:GARY:stationary:Pfeiffer BB color logo email sig 
logo.jpg]<http://www.pfeiffer.edu/>

This email, including attachments, is intended for the person(s) or company 
named and may contain legally privileged information. Unauthorized disclosure, 
copying or use of this information is prohibited. If you are not an intended 
recipient, you may not review, copy or distribute this message. If you received 
this communication in error, please notify the sender immediately by email and 
delete the original message.

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]] On Behalf Of Norman Chu
Sent: Tuesday, February 2, 2016 12:38 PM
To: [email protected]
Subject: [WIRELESS-LAN] Naming conventions for WLAN devices

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/.

Reply via email to