A proper naming convention can help shorten the time for troubleshooting as well as inventory and safeguard your network from future problems.

1. Network Devices
Naming Conventions
By Tekno Budi
tekno.budi@fvtex.ca
June 6th, 2016

2. Why Need A Good Naming
Convention for your network
 A proper naming convention can help
shorten the time for troubleshooting as
well as inventory.
 Good naming conventions can safeguard
your network from future problems

3. When to Consider Implementing
a Naming Convention
 A structured naming convention will be
most useful in a large, dynamic
environment that more complex and
therefore require to be more organized.
 If you are managing only a handful of
computers, a naming convention may not
be critical, but you may still need to give
it some thought.

4. Whatever Naming Convention
Make Sure Stick To It
 Having a naming convention, and sticking to it at
all times, is more important than what your
naming convention entails.
 As long as there is sound logic in your convention
and it provides specific device information at a
glance, you’re on the right track.
 Consistency is important here. Having an erratic or
non-existent naming scheme might not seem a
problem on a small-scale network, but consider the
hurdle on a large-scale network (WAN) such as in
an ISP.

5. Key Features of
Effective Naming Conventions
 Parsability - Name made up of acronyms or
identifiers that represent meaningful information to
anyone reading the name.
 Character Count - Standardised number of
character count
 Permanence - your devices – as well as your
workspace – may move or change from time to
time.
 Logic - A logical framework should underpin every
decision regarding your naming conventions.
 Consistency - Whatever naming convention you
decide on, stick to it at all times.

6. Common Language Location
Identifier Codes (CLLI Codes)
 A CLLI code is an 11-character, standardized, geographic
identifier that uniquely identifies the geographic location
of places and certain functional categories of equipment
unique to the telecommunications industry.
 To identify and describe three types of locations:
 Network sites: network locations as central office buildings,
business offices, microwave radio structures and earth
stations.
 Network support sites: International boundaries or crossing
points, end points, fiber nodes, cable and facility junctions,
manholes, poles and repeaters.
 Customers’ sites: Customer locations and associated circuit
terminations, facilities or equipment for each specific
customer.

7. Who uses CLLI Codes?
 CLLI code (pronounced as silly) is a Common
Language Information Services Identifier used
within the North American telecommunications
industry to specify the location and function of
telecommunications equipment or of a relevant
location such as an international border or a
supporting equipment location, like a manhole or
pole.
 Originally, they were used by Bell Telephone
companies, but since all other
telecommunications carriers needed to
interconnect with the dominant Bell companies,
CLLI code adoption eventually became universal.
CLLI codes are now maintained and issued by
Telcordia

8. Why CLLI Codes
 CLLI codes offer a unique way of unambiguously identifying a
location and its function. The code itself is concise and meaningful,
enabling:
 Process automation within and between service providers
 Rapid understanding of the network through an enforced coding
standard for network sites and entities. Reports may be compiled by
finance and engineering using the same data, ensuring consistency.
 A CLLI Code is required to obtain an NPA NXX code.
 A CLLI codes are required in the ASR/LSR process.
 The CLLI code is also used as a primary key into the database to
enable further details to be understood about a location.
 The CLLI code enables departments within an organization to refer
to the same location in the same way, without risk of ambiguity
where mistakes communicating location information can lead to
expensive work around or litigation.

9. CLLI Code Basic Formats
1.Geographical Codes
 cities, towns, suburbs, villages
 Typically characters 1-4 in CLLI
 Example: Calgary- CLGR
2.Geopolitical Codes
 countries, states and provinces
 Typically characters 5-6 in CLLI
 Example: Alberta - AB

10. CLLI Code Basic Formats
3. Network-Site Codes
 buildings, structures, enclosures
 Typically characters 7-8 in CLLI
 Example: Central Office - CO
4.Network-Entity Codes
 identify and describe functional categories
of equipment, administrative groups
 Typically characters 9-11 in CLLI
 Example: Digital Switch – DS0

11. CLLI Code Basic Formats
 Network Support-Site Codes
 Identify and describe the location of
international boundaries or crossing points, end
points, fiber nodes, cable and facility junctions,
manholes, poles, radio-equipment sites,
repeaters and toll stations.
 Typically characters 7-11 in CLLI.
 Example: Telephone PoleXXXX - P1234

12. CLLI Code Basic Formats
 Customer Site Codes
 Identify and describe customer locations
associated with switched-service networks,
centrex installations; trunk forecasting, cable,
carrier or fiber terminations, NCTE, CPE and
PBX equipment, military installations, shopping
malls, universities and hospitals.
 Typically characters 7-11 in CLLI.
 Example: A Customer - 1A101

13. CLLI Examples
npa-nxx State Rate Center CLLI Misc
403-200 AB Calgary CLGRAB124MD
Prefix Type: WIRELESS
Switch Type: POI
LATA: Manitoba (888)
Detailed Switch Info
403-201 AB Calgary CLGRAB49DS0
Prefix Type: CLEC
Switch Type: Northern Telecom DMS100
(Digital) Host
LATA: Manitoba (888)
Detailed Switch Info
403-202 AB Calgary CLGRAB09DS0
Prefix Type: CLEC
Switch Type: Northern Telecom DMS100
(Digital) Host
LATA: Manitoba (888)
Detailed Switch Info

14. References
To look up switches by CLLI's
http://www.telcodata.us/
CLLI Code Description -
http://etler.com/docs/BSP/795/795-
100-100_I5.pdf
Where CLONES, the CLLI database
is stored- http://www.telcordia.com/