NamingStandards

Physical,logical,services&organizations

Date:
VersionNo.:

AllRightsReserved

31102008
1.5

NORDUnetA/S

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Namingstandardscontents

Objective..................................................................................................4

Targetgroup.............................................................................................4

Introduction..............................................................................................4
3.1

Examplesonabbreviationsthatcouldbeused.........................................5

3.1.1Runningseriessystem.......................................................................7
4

Physicalnamingstandard...........................................................................9
4.1

SITEID............................................................................................12

4.1.1SITESYNTAX..................................................................................12
4.1.2HowtomaketheSITEIDunique......................................................12
4.2

RackID............................................................................................13

4.2.1RackSYNTAX..................................................................................13
4.2.2HowtomaketherackspaceIDunique..............................................15
4.3

SubRackID......................................................................................16

4.3.1SubrackSYNTAX............................................................................16
4.4

Heightunits......................................................................................17

4.4.1HeightunitSYNTAX.........................................................................17
4.5

Equipment,SlotandPortID................................................................17

4.5.1EquipmentSYNTAX.........................................................................18
4.5.2Virtualequipment............................................................................18
4.5.3ExternalNetworkEquipment............................................................18
4.5.4Equipmentshelf..............................................................................19
4.5.5EquipmentshelfSYNTAX..................................................................19
4.5.6Slot,cardandports.........................................................................19
4.5.7Slot,cardandportSYNTAX..............................................................21
4.6

ConnectionandCableID.....................................................................22

4.6.1CableID........................................................................................23
4.6.2CableIDSYNTAX............................................................................24
4.6.3HowtomakethecableIDunique......................................................24
4.6.4TubeandDuctID............................................................................24
4.6.5TubeandDuctIDSYNTAX................................................................25
4.6.6HowtomakethetubeandductIDunique..........................................25
Page2of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Logicalnamingstandards.........................................................................26
5.1

LinkID.............................................................................................29

5.1.1ThelinkIDnamingSYNTAX..............................................................30
5.1.2HowtomakethelinkIDunique........................................................30
5.1.3ExamplesofusedlinkIDs................................................................30
5.2

PathID.............................................................................................31

5.2.1ThepathIDnamingSYNTAX............................................................31
5.2.2HowtomakethepathIDunique.......................................................32
5.2.3ExamplesofusedpathIDs..............................................................32
5.3

CircuitID..........................................................................................33

5.3.1ThecircuitIDnamingSYNTAX..........................................................34
5.3.2HowtomakethecircuitIDunique....................................................34
5.3.3ExamplesofusedcircuitIDs............................................................34
5.4

ServiceID.........................................................................................35

5.4.1TheserviceIDnamingSYNTAX.........................................................35
5.4.2HowtomaketheserviceIDunique...................................................36
5.4.3ExamplesofusedserviceIDs...........................................................36
5.5
6

Logicalsummary................................................................................36

Linkinglogicalnamingstandardstoorganizations........................................38
6.1

Organization.....................................................................................38

6.1.1TheorganizationnamingSYNTAX......................................................38
6.2

Contact.............................................................................................39

6.2.1ThecontactnamingSYNTAX.............................................................39
7

Documentation........................................................................................40

Abbreviations..........................................................................................41

Page3of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

1 Objective

Thisguideistobeusedforcreationofnetworkdocumentationnamingstandards
withinNORDUnetOperations.Thedocumentalsoservesasabuildingdocumentfor
relatedappendixesrelatedtonetworkdocumentation.

2 Targetgroup

ThisdocumentisintendedforstaffinNORDUnetOperations,andrelatedpersonnel
totheNORDUnetnetwork.

3 Introduction

ThenamingstandardshavebeendevelopedbyNORDUnettobeasgenericas
possible.Theworktomakethesestandardshavetakenalittleoverayear,andis
theresultsofinputandcollaborationwithmanyofNORDUnetpartnersboth
internallyandexternally.Thedocumentcanbeusedasaguidelinewithinall
NORDICNRENs.

Thenamingstandardscanbefullyorpartlyimplementedifpartsofthestandardare
notneeded.Thespecificationofnames,codes,etc.andwhatnamingstandardsare
implementedwithintheindividualNRENnetworkshallbeseparatelyspecifiedinthe
allocatedappendix.

Thedocumenthasbeendividedintomainlytwonamingparts
1. Physicalparts:Namingofthephysicalpartsrefertothelabellingofallinstalled
partsofthenetwork.Allphysicalelementsonasiteandbetweensitesare
coveredbythephysicalpartsnamingstandard.
2. Logicalparts:Namingofthelogicalpartsrefertotheusageofthenetwork
resources.Theresourcesprovidedbythenetworkcanbenamedonseveral
levels.AllthelogicalpartsarevirtualandnonphysicalnamingwithintheNMS.

Thephysicalnamingstandardcanbeexpandedintodeeperlevelsofinformation,as
illustratedinFigure1,ifrequiredandthedifferentlevelsofnamingcanbe
individuallyspecifiedbytheNRENintheallocatedappendix.
Page4of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Figure1

Thelogicalnamingstandardisexpandablethroughareservationofnumberseries
thatallowstheNRENtodefineadditionallevelsofinformationifrequired.Specific
informationonseriesusedforlogicalnamingshallbestatedintheappendices.Read
moreontherunningseriesinsection3.1.1.
Section6describestheusagefororganizationsandcontacts,whichcanberelated
totheservicesprovided.

3.1 Examplesonabbreviationsthatcouldbeused

TheNRENsarerequiredtospecifythenamesusedonalllevelsintheappendicesof
thedocument.
Nospecificthoughtsonwhytouseabbreviationsonsitenamesandnetworknames
wasdone,justthatanidentifierhadtobefoundforeachsiteandnetwork,that
wouldnotbeinconflictwithothernetworksthattheNRENconnectsto.
Theabbreviationsmustbemeaningfulpreferablyamnemonicnamesoittellsthe
operatorswhattheequipmentisusedfor.Thelistmustbesimple,andcoveras
manyreleasesofanytypeofequipment,tobefutureproof.Someexamplescanbe
seenintable1.

Page5of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

SITEnameabbreviation

Fullname

CSC

CSCHelsinki

FRE

Fredhll

HMB1

HamburgWendelstrasse1

HMB2

HamburgWendelstrasse2

HEU

HelsinkiUniversity

ORE

restaden

OSC

OsloCentrum

TUG

Tulegatan

UNI

UniC

USI

OsloUniversity

Countryname
abbreviation

Fullname

DK

Denmark

SE

Sweden

NO

Norway

FI

Finland

IS

Iceland

Networkname
abbreviation

Fullname

FK

Forskningsnettet

FU

FUNET

NU

NORDUnet

RH

RHnet

SU

SUNET

UN

UNINETT

Page6of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Equipmentname
abbreviation

Fullname

LM

LightManager

TSS

TransportServiceSwitch

ILA

InLineAmplifier

RAM

RamanAmplifier

Table1

3.1.1 Running series system

The running series system is a generalisation for this document, and is, as this
document, intended as a guidance for producing appendixes of all kinds related to
namingstandards.Therunningseriessystemshouldbeusedasitisdesigned,but
there are no limitations as to how to use the running series system in a new
appendix.
Therunningseriessystemisbasicallyarunningnumberwithanidentifierstarting
fromthedigitfrom0to9followingaletteridentifierfromAtoZ.Thesenumbers
andlettersareusedtodifferentiatebetweencircuits,paths,links,patchcablesand
soforth.Iftheidentifiernumbersorlettersareexhausted,asecondnumberor
lettercanbeappliedtomeettheneeds.
Thiswillgivethefollowingsyntaxforarunningseriessystem.

<x><incrementingnumberstart=0>
Andifneeded
<xx><incrementingnumberstart=0>

WhereXandXXisrepresentedbyanumberoraletter.

Havingidentifierseriesrunningfrom0toZ,leavesroomtodefinenewtypesof
connectivitysinthenetwork,aswellasworkingasadirectidentifiertowhattypeof
connectivityitrepresents.
Pleaserefertotable2fordefinitionstothisdocument.

Page7of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Runningseries

Useof

Remarks

0000000

Cables

ReservedcableIDs

1000000

Links

ReservedlinkIDs

2000000

N/A

Notinuse

3000000

N/A

Notinuse

4000000

Paths

ReservedpathIDs

5000000

Circuits

ReservedcircuitIDs

6000000

N/A

Notinuse

7000000

N/A

Notinuse

8000000

N/A

Notinuse

9000000

N/A

Notinuse

S000000

Services

ReservedserviceIDs

Table2

Table2definitionsinboldarefixed,andcannotbeoverruledbyanyappendix.
Anyappendixisfreetouseanyidentifierfree,orinventanewidentifierfromthe
syntaxdescription.

Page8of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4 Physicalnamingstandard

ThereferencedrawingsforthephysicalnamingstandardsareillustratedinFigure2,
thetextintable3showstheitemsthatcanbenamedwithinanetwork.

Thephysicalitemsthatcanbelabelledare:
Reference
chapter

Item

Explanation

Network

Ownernaming:NRENorServiceProvider
naming

3.1

Site

Asiteisabuildingthatmaycontainequipment

4.1

Specificsiteusedfortrafficexchange
Intermediatesiteusedfortraffichandling
Anysitethatispartofanetwork.
Rack

Arackisapositionofamechanicalstorageitem

4.2

Anyrackplacedatasiteusedasapartofthe
network
Anyrackplacedatasiteconnectedtothe
network
Standaloneracks
Subrack

Asubrackisarackthatisplacedwithinarack

4.3

HightUnits

AHUisaphysicallabelinsidearack,thatshow
theverticalplacementofainstalledequipment.

4.4

Equipment

Equipmentisalltypesofactiveandpasiveunits
connectedtoorpartofthenetwork.

4.5

Equipment
shelf

Abuildinsmallerpartofaequipmentthatcan
holdslotsandorcards.

4.5.2

Slot

Slotreferstoaspecificpositionwithinaspecific
equipment

4.5.3

Card

Specificcardtype

4.5.3

Port

Specificportpositionand/ortype

4.5.3

Patchcable

Fibreconnectionsovershortdistances

4.6
Page9of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Leased
circuit

Referstoathirdpartycommunication
connections

4.6

Fibre

Physicalfibrestringconnectingsites

4.6

Trunk

Acollectionofpatchcables,leasedcircuitsor
fibres

4.6

AtrunkcanbefullyusedbytheNREN
Cable

Cablescontainingmanyopticalfibres

4.6

Cablescontainingmanyelectricalwires
Acablecancontaintrunks
Acablecanbesharedbetweenmanyproviders
Tube

Tubescancontaincables

4.6.5

Tubescancontainsinglefibres
Duct

Ductsareconstructedchannelsthatcontainsthe 4.6.5
tubesorcables

Table3

Page10of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

TheillustrationsinFigure2areagenericrepresentationofelementsandmedia
usedinanetwork.Allelementsorsomespecificelementscanbeuseddependingon
theNRENrequirement.

Nomenclatures
Site: Site ID
Rack: Rack ID
Sub rack: Sub rack ID
Unit: EQ type-EQ no.
Power rack: Rack ID
Breaker: Sub rack ID
Power cable: Cable ID
Aux unit: EQ type-EQ no.
Aux cable: Cable ID
ODR: EQ type-EQ no.
ODR tray: Sub rack ID
Patch cable: Cable ID
DDF: Rack ID
DDF plate: Sub rack ID
Coax cable: Cable ID

Country: Country code

Site: Site ID
Unit: EQ type-EQ no.
Patch cable: Cable ID

Leased circuit: Cable ID

Fibre: Cable ID
Trunk: Cable ID
Cable: Cable ID
Tube: Tube ID
Duct: Duct ID

Country: Country code

Site: Site ID
ODR: EQ type-EQ no.
ODR tray: Sub rack ID
Patch cable: Cable ID

Physical Layer
Site

Site

Site

ODR

Rack
Subrack

Unit

Power
cable

Unit Unit

Power rack

ODF tray
3rdpartyNetwork

Breaker

Patch
cable

ODR

Aux

Aux
cable

Aux
unit
ODR

ODF tray

Leased circuit

Fibre

Trunk
Cable

Tube

ODR tray
Duct

DDF

Coax
cable

DDF Plate

Rack

Sub rack

Rack: Rack ID
Sub rack: Sub rack ID
Unit: EQ type-EQ no.

Slot

Slot

Slot

Unit

Slot: Slot ID

Port
Port

Port: Port ID

Figure2

Page11of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.1 SITEID

ASITEisdefinedasaplacewithactiveorpassiveequipment,fromwhere
connectionscanbemadetoothernetworksorotherequipments.

EverySITEmustbeuniquelylabelledanddocumentedwithinthenetwork.
ThenamingstandardisusingacountryIDanduptofour(4)characterIDfor
eachsite.
TheSITEIDshouldbeuniquewithoutthecountrycode.
SITEscanhaveasecondnameforidentificationaswell,suchasthelongname
itisgiven.
TheSITEIDneverchanges.
AllSITEIDsmustbedocumented.

4.1.1 SI T E SY N T A X

TheSYNTAXfornamingaSITEis:
<COUNTRYIDSITEID>
Thisgivesthefollowingexamples:
DKORE(Denmarkrestad)
DKUNI(DenmarkUNIC)
SETUG(SwedenTulegatan)
SEFRE(SwedenFredhll)

4.1.2 How to make the SI T E I D unique

Thelistbelowisaguidelinewhengeneratingthesitenames:
1. Startbytypingthecountryidentificationusingthe2letterIDaccordingtothe
ISO31661alpha2document.(Directlinkhttp://www.iso.org/iso/en/prods
services/iso3166ma/02iso3166codelists/listen1.html)
2. Separatewithminussign().
3. Typeupto4characterssiteID
4. UpdatethedocumentationwiththenewsiteID.

Page12of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.2 RackID

Arackisacontainerofpassiveandactiveequipmentinallforms.Theracksare
foundinallshapesandforms,bothwallandfloormountable,ETSIand19inch
nativeracks.Commonforallracktypesare,theyuseaHU(HeightUnit)indicator,
orcanhaveanindicatorlabelledtothefrontoftherack.WiththeHUindicatora
rackcanbedesignedtouseitscapacitytothefullest.

Everyrackmustbelabelledanddocumenteduniquelywithinthenetwork.
NamingstandardisusingstaticfloortileobjectstomaketheIDuniqueforeach
rackwithinasite.
IfthesiteisnotwithfloortilesoralreadyhaveadifferentIDsystem
assignedinthissite,thisisacceptedastheracksID(aslongasthereisa
knownsystemfortheIDofarack)
ArackIDdefinesapositioninthesite.
RowsaredefinedbylettersstartingfromAZ
Columnsaredefinedbydigitsstartingfrom1to99aleadingzeromustbe
usedfornumbers1to9.
Rowsandcolumnsaredividableinto4,forexplanationseesection4.2.2and
Figure3,andmustthereforebedefinedwithminimum0aftertherow
indicatortoindicatethetileisnotdivided.
Rowsandcolumnsmustbeseparatedbyfullstop(.).
AmovedrackmustchangeID.
AllrackIDsmustbedocumented.

4.2.1 Rack SY N T A X

TheSYNTAXfornamingarackis:
<XY.ZZ>
Reserved
Syntax
numbersand
symbol
letters

Explanation

AZ

Definedrowatthesite

Undefinedrowatthesite

A+B

Definesthepositionandorientationofahalfrack
(300x600mm)

C+D

Definesthepositionandorientationofahalfrack

Page13of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

(300x600mm)

NRENspecified
letter

Specifiedalternativeracktypesintheallocated
NRENappendix

Afullrack(600x600mm)

Ahalfrack(300x600mm).Unknown
orientation.

ZZ

199

Definedcolumnatthesite

00

Undefinedcolumnatthesite

Table4

Thesyntaxintable4isalsoillustratedinFigure3.
TheNRENcanifrequired,andspecifiedintheallocatedappendix,expandthe
syntaxtohigherleveloflettersandnumbers,e.g.XXYY.ZZZ.

Thisgivesthefollowingexamples:
C0.01(60x60cmrackatrowCandposition1,ref.figure3)
C0.02(60x60cmrackatrowCandposition2,ref.figure3)
C0.03(60x60cmrackatrowCandposition3,ref.figure3)
CA.04(30x60cmrackatrowCandposition4,ref.figure3)
CB.04(30x60cmrackatrowCandposition4,ref.figure3)
CC.05(60x30cmrackatrowCandposition5,ref.figure3)
CD.05(60x30cmrackatrowCandposition5,ref.figure3)
01.00(30x60cmrack,undefinedrow,columnandorientation,ref.figure3)
0C.00(60x30cmrackatundefinedrowandcolumn.Definedorientation,
ref.figure3)
00.00(undefinedrack,row,columnandorientation)

Page14of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.2.2 How to make the rack space I D unique

Thisappliestositeswithelevatedfloorsusingfloortilesof600*600mm,butcan
alsobeappliedtositeswithothersizetilesorsiteswherealetteranddigitsprint
canbemountedonthewalls.
Ifafloorplandoesnotexisttoaspecificsite,itisadvisabletomakeanoutlined
floorplanforthesite.

1. Startbyenteringthemostobviousdoortothesite(ifmorethanone
entrance).
2. Gotothefarleftcornerfromthatdoorandmarkthestartingpointforthe
site.SeeFigure3.Astatingpointcanjustbedefinedifthisiseasier.
3. Alwaysstartwithrow,thencolumn.
4. Ifhalfsizeracksaretobeinstalled,therowsandcolumnsneedtobedivided.
5. DividingasshownonFigure3fromlefttoright,ortoptobottom,willdividea
tileintoA,B,CorDsides.
6. DefinerowsbyaletterAZfollowedbydivisionindicatorzerofornodivision
orA,B,CorDasshownonFigure3.

Figure3

TherackspaceIDstartswithrowletter,indicatorofdivisionandendingwith
columnnumber.
HalfsizerackcanbedividedasdepictedonpositionC.04andC.05.
WhendividingarowAandBmustbeused,ifdividingbycolumn,useCandD.

Page15of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.3 SubRackID

Thesubrackisamechanicalelementthatsubdividestherackintomultiplesections
whichcouldbeusedforequipment,seeFigure4.Thefinaldefinitionisdoneinthe
allocatedappendix.

ThesubrackIDshallprimarilyidentifythesubrackwithinarack.TheIDisnot
uniquewithinanetworkandnewIDsmustbegeneratedifthesubrackpositionis
changed.

Subracksarecountedfromthetopdowninsidearack.
AmovedsubrackmustchangeID.
AllsubrackIDsmustbedocumented.

4.3.1 Sub rack SY N T A X

TheSYNTAXfornamingasubrackis:
<SRID>
Thisgivesthefollowingexamples:
SR01(Subracknumber01)
SR02(Subracknumber02)
SR03(Subracknumber03)

Figure4

Page16of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.4 Heightunits

Typicalracksorcabinetsare43HUhigh,andcomesinwidthsizesof19inchand21
inch.Othersizesareavailableonthemarket,butcommonforallis,theyhavea
unitplacementdefinitionavailablethroughthemountingholesfromtoptobottom.
Someracksaredeliveredwithalabelsystemtotherailofmountingholes,some
arenot.Inordertofurthermakeiteasytofindsmallorlargeequipmentsinstalled
insideracks,thefollowingapplies.

Allracksinstalledtosites,musthaveaHUlabelonthemountingrails.
AllequipmentIDsmustbedocumentedwithaHUID.
Aleadingzeromustbeusedforthefirst9numbers,makingallnumberson
thelabelconsistof2digits.
HUshallstartfromthefloorandup,beginningwith00/01uptoxx.This
ensuresunitsinstalledinHU10isalwaysinstalledthesameheightfromthe
floor.

4.4.1 H eight unit SY N T A X

TheSYNTAXfornamingheightunitsis:
<Leadingzeroforx<10><x>
Thisgivesthefollowingexamples:
0102030405303132

4.5 Equipment,SlotandPortID

ThedefinitionofequipmentcanincludepassiveODRs,passiveopticalequipments,
andactiveequipmentssuchasSDHequipments,WDMterminalsandIProuters.
Commondenominatorforallkindofequipmentsisthattheyareinstalledonasite.
Theremightbeauseforsecondarynamestoanydefinedequipment,ifused,this
nameandhowtodefineit,shouldbedescribedinarelevantdocumentforthe
documentinquestion.Thisdocumentdoesnotdictateastandardforusing
secondarynames.

Allequipmentsmustbelabelledanddocumenteduniquelywithinthenetwork.
Page17of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

TheNRENsspecificnamingstandardshallbespecifiedintheallocatedappendix
statingthetypenameoftheequipmentmustindicatetheequipmentuseand
purpose.
AllequipmentIDsmustbedocumented.

4.5.1 E quipment SY N T A X

TheSYNTAXfornamingequipmentis:
<<EQTYPE><EQNo.>>
Thisgivesthefollowingexamples:
LM01(DWDMOADM,referencenumberone)
TSS01(SDH,platformreferencenumberone)
RTR03(Router7600,referencenumberthree)

4.5.2 V irtual equipment

Virtualequipmentsuchasvirtualrouters,switchesandthelikemayormaynotbe
assignedtoaspecificsite,butfreefloatinginsidetheactualnetwork,canbenamed
likenormalequipment.
Thiskindofequipmentshouldbeseenandnamedaseithervirtualequipmentwith
usageoftheequipmentnamingsyntaxfromsection4.5.1orasaserviceusingthe
servicesnamingsyntaxfromsection5.4.1,dependingonitsusage.
Theinformationontheequipmentbeingvirtual,shouldbenotedtotheequipments
attributes,ordocumentationfollowingit.Thenamingonvirtualequipmentshould
bebetterdescribedinanappendix.

4.5.3 E xternal Networ k E quipment

Unlikethevirtualequipment,anamingschemeforunmanageableequipmentby
otherproviders/suppliersmayalsobeneeded.
Again,thesamesyntaxassection4.5.1shouldbeused,heretheequipmenttype
shouldbefixedtoENE.
<<ENE><EQNo.>>

Page18of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.5.4 E quipment shelf

Manydifferenttypesofequipmentstakeupdifferentspaceinarack.Theycanbe
definedbyaspecificsize,orexpandable.Thelatterraisingtheneedforashelf
definition.
Ashelfisanexpandablepartofactiveequipment.
Typicallyashelfcorrespondstoashelf,orinsomecasestoasubrack,within
anactiveequipmentmanagementsystem.

4.5.5 E quipment shelf SY N T A X

TheSYNTAXfornamingequipmentshelfis:
<SHNo.>
Thisgivesthefollowingexamples:
SH1(Equipmentshelf1)
SH2(Equipmentshelf2)
SH3(Equipmentshelf3)

4.5.6 Slot, card and ports

Becauseallequipmentsarenotthesame,theNRENmustmaketheunderstanding
ofanequipmentnomenclatureunique.Thisisdonebyputtinganoverlappingmatrix
overtheequipmentfrontandthencountinganddividingthematrixlikereadinga
book,fromupperleftcornertolowerright
corner,seeFigure5.
Thematrixshouldbeappliedonlytothestatic
partsoftheequipment.Meaningwhennew
equipmentisinstalled,itispresumedtobe
empty,leavingslotsorplugsforinstallation.
Theequipmentmighthavestaticportsaswell.
Thisgivesanoptiontoapplythematrixfor
everypartontheequipmentinneedfor
documenting.
Thematrixshowninfigure5isnottobetaken
literallytheonlytruth,butmeantasaguide
Figur5

Page19of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

intoreadingtheslots,plugs,portsandsoforththatneedsdocumented.
Iftheequipmenthasclearslot,plugandportnumberingtheusageofthissection
mightnotbeapplicabletotheparticularequipment.Thatdecisionisuptothe
designteam.
Takealookattheequipmentonfigure6,andthenapplythematrixonthat.

Figure6

1. Startbycountingtheverticalslotsinthetopshelfofequipmentfromleftto
right.

2. Thencounttheamountofpartsthefirstslotcanbedividedinto,thenthesecond
slotandsoon.

3. Thencounttheamountofpossiblepluginportsinthefirstslot,thenthesecond
slotandsoon.

4. Lastlycountthepossibletrafficportsinthefirstslot,thenthesecondslot,then
thirdandsoon.

5. Restarttheprocessbycountingthehorizontalslotsintheequipmentstarting
fromthetopanddown.

Page20of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

6. Thencounttheamountdivisionofthefirstslot,thensecondslot,thenthirdand
soon.

7. Thencountamountofpossiblepluginportsinthefirstslot,thensecondslot,
thenthirdandsoon.

8. Lastlycountthepossibletrafficportsinthefirstslot,thensecondslot,thenthird
andsoon.

9. Iftheequipmenthaspermanentportsasshowninredonfigure5,startinleft
topcornertotheright,andthendownwardscountingtheports.

Thedefinitionmethodisnotasubstitutionfortherealvendornumberingscheme
butshouldbeseenasanoverlayingmatrix,inordertomakeallequipmentsfitany
namingstandardandNetworkInventorysystemregardlessofvendorornumbering
scheme.Twovaluesshouldalwaysbedocumented,thevendorandthematrix
definition.
Figure6resultsin:
9slotpositions,1plugport,and6staticports.
Ofthe9slotpositions,3slotpositionscanbedividedin2partswhile3othercanbe
dividedin3partseach.

Thedefinitionofslots,cardsandportscanbecontinuedendlesslyuntilthedesired
resultisachievedfromusingthenamingstandard,theonlythingchangingisthe
stringinsection3.0Figure1.

Amovedslot,cardorportmustchangeID.
Allmovedslot,cardorportmustbedocumented.

4.5.7 Slot, card and port SY N T A X

TheSYNTAXfornamingequipmentslotis:
<SLNo.>

Thisgivesthefollowingexamples:
SL32(Slotinposition3andsubposition2,markedinFigure2)
SL83(Slotinposition8andsubposition3,markedinFigure2)
SL10(Slotinposition1andnosubpositions,markedinFigure2)
Page21of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

TheSYNTAXfornamingequipmentcardis:
<CARDTYPE>
Thisgivesthefollowingexamples:

10GE2(10GEcardshortrange1310nmclient)
8XGE(8x1GEcard)
TheSYNTAXfornamingequipmentportis:
<PortNo.>
Thisgivesthefollowingexamples:
P01(Systematicportone)
P02(OpticalODRporttwo)
P12(DigitalDDFporttwelve)

4.6 ConnectionandCableID

Theconnectionisapartofthecircuitryinthenetwork.Thetermconnectioncovers
anyphysicalornonphysicalconnectionbetweentwonetworknodesthis
connectioncouldbeofoptical,electrical,wirelessorrentedtype,andmustbe
identifiedwhethertheconnectionisa5mcableor500kmcable.SeeFigure6.

Figure7

Whendefiningthetypeofconnection,thetermcoversallcablesputtogetherfrom
siteAtositeBwherethenetworknodesarelocated.CablescantaketheIDfrom
Page22of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

thecableproviderofarentedcable,oruseanamingsyntaxtogiveacableitsID.
Cablesmustbeidentifiableatbothends.

Thebestandmostefficientwaytoidentifyarentedcable,istomaintainthename
orIDgivenbythecableprovider,e.g.fromTelenororGlobalCrossing.

4.6.1 C able I D

ThenetworkproviderstypicaluseofacableIDisforinternalcablesofanytype,
butasshowninFigure8italsocoversexternalcables.
HoweverthecableIDcanalsobeusedformasterlines,installationcablesandall
othertypesofcablesthatthenetworkmakesuseof.

Figure8

Allcablesmustbelabelledanddocumented.
AcableIDisuniqueandmustnotbereused.
Namingstandardisusinganownerabbreviationandthena1digitIDwhichfor
opticalpatchcablesalwaysiszero(0)thena6digitincrementingnumber
startingfrom(0)000001.
PatchcablescanbemovedwithoutchangingID,aslongitiswithinthesame
network.
AllcableIDsmustbedocumented.
Page23of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

4.6.2 C able I D SY N T A X

TheSYNTAXfornamingcableis:

<<CABLEOWNER><1digitID><6DIGITRUNNINGNUMBER>>

Thisgivesthefollowingexamples:
(PleasenotethatthefirsttwoIDsarekeptfromthedifferentprovidersofoptical
fibres)

1050001(Telenoristheproviderdeliverynumber105sectionrunning
numberis0001)
45031023(GlobalCrossingistheproviderprovidergivennumber,no
explanation)
NU0000001(NORDUnetpatchcable0000001)
SU0000001(SUNETpatchcable0000001)
FU0000001(FUNETpatchcable0000001)

4.6.3 How to make the cable I D unique

1.
2.
3.
4.
5.

AlwaysstartacableIDwithanownerid.
Separatetheowneridusingaminussign().
Type0asanindicationforcables
Addthenextincrementinguniquenumber.
Makesurethatthenamingisdoneinbothendsofthecableanddocumented.

4.6.4 T ube and Duct I D

Tubesandductsarenormallynamedbytheowneroftheinstallationshowevera
namingconventioncanbefollowedincasethetubesandductsarelackingthis
information.
Bothtubesandductmustbelabelledwithauniqueidentifier.

Alltubesandductsmustbelabelledanddocumented.
Page24of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

AtubeorductIDisuniqueandmustnotbereused.
Namingstandardisusinganownerabbreviationandthena6digitincrementing
numberstartingfrom000001.
MovedtubesandductsmustchangeID.
AlltubeandductIDsmustbedocumented.

4.6.5 T ube and Duct I D SY N T A X

TheSYNTAXfornamingtubeorductis:

<<TUBEOWNER><6DIGITRUNNINGNUMBER>>
<<DUCTOWNER><6DIGITRUNNINGNUMBER>>

4.6.6 How to make the tube and duct I D unique

1. Checkthedocumentationforlastusedrunningnumberforthenetworkthetube
orducthastobecreatedto.
2. Incrementtherunningnumberoneup.
3. StartatubeorductIDwithanownerid.
4. Separatetheowneridusingaminussign().
5. Typetheincrementeduniquerunningnumber.
6. Makesurethatthenamingisdoneinbothendsofthetubeorductand
documented.

Page25of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5 Logicalnamingstandards

Thefollowingchapterexplainstherelationsbetweenservices,circuits,pathsand
links,seeFigure9.
InordertoestablishsynergywiththesoftwareofaNMS,somepartsofthe
documentationiskeptinthesoftwareonly,whichleavesthephysicalpartandsome
ofthelogicalpartofthenetworktoanetworkinventoryandthefulllogicalpartof
thenetworktotheNMSsoftware.
ThecommondefinitionsofthelogicalpartsareillustratedinFigure9.Aservice
typicallycoverstransmissionfromAtoZ,usingthreetransmissionoptionscircuits,
pathsandlinks,aswellascables.Acircuitismadeofoneormorepathsandcan
havesameendingpointsastheservice.Apathismadeofoneormorelinksaswell
ascables.Thetextintable5showstheitemsthatcanbenamedwithinanetwork.

Figure9

Commonlyforallservicesandthethreetransmissiontypesisthatallusesasixdigit
runningnumberwithaonetypeidentifier.Therunningnumberisincrementedfor
eachnewservice,circuit,pathandlink.
Whilelookingatthecustomerend,thecustomercouldhavemorethanoneservice
runningoverthesamecircuitthereforethismustbeheldaccordinglytothe
customerinaseparatedocumentortablewithinaNetworkInventorydatabase.

Page26of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Thelogicalitemsthatcanbelabelledare:
Reference
chapter

Item

Explanation

Link

Definestheconnectivitybetweentwo
equipments.Linkusesphysicalpatchcablesor
transportmediaonthephysicallevel.

3.1

Path

Isthelogicalconnectivitybetweentwo
endpointequipments,usingoneormorelinks.

3.2

Circuit

Istheendtoendconnectivityforaserviceto
acustomer,usinglinksandpaths.

3.3

Service

Theservicecoversfromthedeliveryoffibers
toanyorganization,topaths,tocircuitsto
participationininternationalservices.

3.4

Table5

Ultimatelythecustomercouldrequestaservicespanningovermanydifferent
networks,e.g.fromUNINETT,toNORDUnet,toSurfnet,toCanarieandfurtheron.
ThissetupcouldbewithintheGLIFnetwork.See.Figure10.

Figure10

Page27of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Thisapproachresultsinanamingconventionthatislikeatreestructurewherethe
samecircuit,pathandlinkcanbeusedmorethanonce,leavingtheserviceintactif
thethreeshouldneedtochangeroutesorbereplacedwithnewcircuits,pathsor
links.
Figure11showshowandwhereaservice,circuit,pathandlinkaretobeidentified
inanetwork.

Figure11

Thedefinitionsoflinks,paths,circuitsandservicesareonlyconsideredasguidelines
toconventionalnetworksthefuturebringsnetworks,withWSSorsimilar
technologies,whichcanmaketheneedfordefiningpathsobsolete.

Page28of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.1 LinkID

Thelinkisthephysicaland/orlogicalconnectionbetweentwoequipments.See
Figure12.
Thelinkisthefirstphysicaland/orlogicalbuildingblocktothenetwork,andpartof
thebackbonenetwork.
Alinkmaybeusedmultipletimesbypaths,circuitsandservices.
Thelinkmustalwaysstartwiththeidentifyingnumber1(accordingtosection3.1.1,
table2)followedby6runningnumberstoatotalof7digitsforthelinkID.

Everylinkmustbeuniquelyidentifiedwithinthenetwork.
AlllinkIDsmustbedocumented.

Figure12

Page29of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.1.1 T he link I D naming SY N T A X

TheSYNTAXfornaminglinkis:

<<LINKOWNER>1<6DIGITRUNNINGNUMBER>>

Thisgivesthefollowingexamples:

NU1000001(NORDUnetLink1)
NU1000002(NORDUnetLink2)
SU1000001(SUNETLink1)

5.1.2 How to make the link I D unique

1. Checkthedocumentationforlastusedrunningnumberforthenetworkthe
linkhastobecreatedto.
2. Incrementtherunningnumberoneup(last6digits).
3. StartwithanetworkID.
4. SeparatethenetworkIDusingaminussign().
5. Typetheidentifierdigit1forlink.
6. Typetheincrementeduniquerunningnumber(last6digits).
7. UpdatethedocumentationwiththenewlinkID.

5.1.3 ExamplesofusedlinkIDs

LinkIDresultsshouldlooklikethis:

NU1000105:ThenetworkisNORDUnet,uniquerunningnumberis1000105
NU1000104:ThenetworkisNORDUnet,uniquerunningnumberis1000104
NU1999999:ThenetworkisNORDUnet,uniquerunningnumberis1999999

Page30of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.2 PathID

Thenetworkpathisanoverlayonthelinksalreadycreatedinthenetwork.Apath
canbeusedformultipleservicesandcircuitsifnecessary.SeeFigure13.
ApathisaccordingtoFigure11thenetworkendingpointsandcanserveasa
componentdirectlytoaserviceskippingacircuitusage.
Thepathmustalwaysstartwiththeidentifyingnumber4(accordingtosection
3.1.1,table2)followedby6runningnumberstoatotalof7digitsforthepathID.

Everypathmustbeuniquelyidentifiedwithinthenetwork.
Theuniquepathmusthaverelationstoalllinksusedtobuildthepath.
AllpathIDsmustbedocumented.

Figure13

5.2.1 T he path I D naming SY N T A X

TheSYNTAXfornamingpathis:

<<PATHOWNER>4<6DIGITRUNNINGNUMBER>>

Thisgivesthefollowingexamples:

NU4000001(NORDUnetPath1)
Page31of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

NU4000002(NORDUnetPath2)
SU4000001(SUNETPath1)

5.2.2 How to make the path I D unique

1. Checkthedocumentationforlastusedrunningnumberforthenetworkthe
pathhastobecreatedto.
2. Incrementtherunningnumberoneup(last6digits).
3. StartwithanetworkID.
4. SeparatethenetworkIDusingaminussign().
5. Typetheidentifierdigit4forpath.
6. Typetheincrementeduniquerunningnumber(last6digits).
7. UpdatethedocumentationwiththenewpathID.

5.2.3 ExamplesofusedpathIDs

PathIDresultsshouldlooklikethis:

NU4000005:ThenetworkisNORDUnet,thepathsuniquerunningnumberis
4000005,andthepathistheworkingpath.
NU4001104:ThenetworkisNORDUnet,thepathsuniquerunningnumberis
4001104,andthepathistheworkingpath.
NU4000308:ThenetworkisNORDUnet,thepathsuniquerunningnumberis
4000308,andthepathistheworkingpath.

Page32of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.3 CircuitID

Circuitscomesinmanyvariations,butcommonlyforallis,thatitmustbeusingone
ormanypathsinordertoreachfromAtoZ.
Thecircuitisdefinedassomethingthatcanbecontrolledwithinthesamenetwork,
e.g.inaprovidernetwork.
Thecircuitmustalwaysstartwiththeidentifyingnumber5(accordingtosection
3.1.1,table2)followedby6runningnumberstoatotalof7digitsforthecircuitID.

Everycircuitmustbeuniquelyidentifiedwithinthenetwork.
Everycircuitmusthaverelationstoallpathsitisusing.
Everycircuitmusthaverelationstowhichcustomerserviceitbelongsto.
Everycircuitmustbeuniquelyidentifiedtodeliveringnetwork.
AllcircuitIDsmustbedocumented.

InFigure14acircuitdescribesendtoendconnectivity,followingthegreenline,
fromAtoZ.

Figure14

Page33of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.3.1 T he circuit I D naming SY N T A X

TheSYNTAXfornamingcircuitis:

<<CIRCUITOWNER>5<6DIGITRUNNINGNUMBER>>

Thisgivesthefollowingexamples:

NU5000001(NORDUnet,Circuit1)
NU5000002(NORDUnet,Circuit2)
SU5000001(SUNET,Circuit1)

5.3.2 How to make the circuit I D unique

Ashortdescriptionhowtousethenamingsyntax:

1. Checkthedocumentationforlastusedrunningnumberforthenetworkthe
circuithavetobecreatedto.
2. Incrementtherunningnumber1.
3. Startwiththenetworkid.
4. SeparatethenetworkIDusingaminussign().
5. Typethedigit5forcircuit.
6. Typetheincrementeduniquerunningnumber(last6digits).
7. UpdatethedocumentationwiththenewcircuitID.

5.3.3 E xamples of used circuitIDs

CircuitIDresultsshouldlooklikethis:

NU5000005:ThenetworkisNORDUnet,thecircuitsuniquerunningnumberis
5000005,andthecircuitistheworkingcircuit.
NU5001104:ThenetworkisNORDUnet,thecircuitsuniquerunningnumberis
5001104,andthecircuitistheworkingcircuit.
NU5000308:ThenetworkisNORDUnet,thecircuitsuniquerunningnumberis
5000308,andthecircuitistheworkingcircuit.

Page34of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

5.4 ServiceID

TheserviceisderivedfromFigure15,asaresultofthenamingstandardsasa
whole.Theservicecoversrentingoutarackspace,tocables,toequipmentto
transmissionfromAtoZ.PleasenotethatFigure15onlyillustratestherelationsfor
thelogicaltransmissionandcables(connection,seesection4.6).
Theservice,presumingitis
logical,isoverlayingcircuits,
pathsandlinks.Thesame
servicenumbercanoverlay
orcovermanycircuits,
paths,linksandphysical
elements,suchaspowerand
patchcables.Therelations
toalltheseindividual
elementsareeasilyhandled
withinaNetworkInventory
system,theycanhowever
alsobehandledinany
documentsystem.
Theservicemustalways
startwiththeidentifying
letterS(accordingtosection
3.1.1,table2)followedby6
runningnumberstoatotal
of7digitsfortheserviceID.

Figure15

Everyservicemustbeuniquelyidentifiedtoaspecificorganization/contact.
Theuniqueservicemusthaverelationstoallcircuits,paths,linksandso
forth,whichbuildtheservice.
AllserviceIDsmustbedocumented.

5.4.1 T he service I D naming SY N T A X

TheSYNTAXfornamingaserviceis:

<<SERVICEOWNER>S<6DIGITRUNNINGNUMBER>>
Page35of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

Thisgivesthefollowingexamples:

NUS000001(NORDUnetService1)
NUS000002(NORDUnetService2)
SUS000001(SUNETService1)

5.4.2 How to make the service I D unique

1. Checkthedocumentationforlastusedrunningnumberforthenetworkthe
servicehastobecreatedto.
2. Incrementtherunningnumberoneup(last6digits).
3. StartwithanetworkID.
4. SeparatethenetworkIDusingaminussign().
5. TypetheletterSforservice.
6. Typetheincrementeduniquerunningnumber(last6digits).
7. UpdatethedocumentationwiththenewserviceID.

5.4.3 E xamples of used service IDs

ServiceIDresultsshouldlooklikethis:

NUS000005:ThenetworkisNORDUnet,theservicesuniquerunningnumberis
S000005.
NUS001104:ThenetworkisNORDUnet,theservicesuniquerunningnumberis
S001104.
NUS000308:ThenetworkisNORDUnet,theservicesuniquerunningnumberis
S000308.

5.5 Logicalsummary

ReturningtoFigure11inthebeginningofthischapterasummaryofhowto
documentaserviceshouldendupinanydocumentingsystemisexplainedhere.

Page36of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

NoticeNUS000001isusingacircuitNU
5000001,thiscircuitmightinothercasesbe
replacedbytheusageofpathsandlinksalone.
NU5000001istheonlycircuitfortheservice,
inothercasestheuseofacircuitcouldobsolete
dependingontheservice.
Thecircuithas3underlyingpaths,and2links.
Noticethelast2linksarenotrelatedtothe
pathsused.
Eachpathhas1to4linksinuse.
WhatisnotcoveredinFigure16istheuseof
patchcablesofeitherelectricaloropticaltype,
granteditcouldbeexpandedtoalsocoverthis
itisnottheintentionwiththissummary.
ForeachpathshowninFigure11,theremight
beseveralNMSsystems,oratleastoneper
network.

Thiscouldbethesamewiththecircuit,butnot
likely,rememberFigure11isanexampleusing
generalityforthenamingstandard,whichmightnotalwaysbetheonlytruthinreal
lifesituations.
Figure15

Thenamingstandardisgenericallybuild,meaningthatforeachequipmentbranch,
IP,Ethernet,Opticalandsoforthaexplanatoryappendixmustbewritten,making
themappingfromthestandardstowhatshouldbeunderstoodwhenlookingatthis
particularequipmentanditslinks,pathsandcircuits.

Page37of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

6 Linkinglogicalnamingstandardstoorganizations

Asservicescoversthedeliveryofacables,links,pathsandcircuits,theneedtobind
thenamingtoproviderorcustomer.
Theorganizationcoverscustomerandprovider,aswellasanypartnersinthe
future.Theorganizationcanalsobeaproject,astheinternationalradioastronomy
project.
Withineachorganizationthereisxamountofcontacts.Dependingonthecontacts
relationshiptoorganizationsheorshecanappearascontacttoservicesspanning
manyorganizations.
Inshort,aservicehasrelationtoanorganizationwhichagainhasrelationtoa
contact.

6.1 Organization

Thereisnostandardfornamingorganization,exceptthenamemustbeshortand
precise.Anyotherinformationtotheorganizationmustbedescribedinthe
organizationattributes.Theorganizationcanbeallofthebelowstated:
Projectname
Customername
Providername
Partnername

6.1.1 T he organization naming SY N T A X

TheSYNTAXfornaminganorganizationis:

<ORGANIZATIONname>

Thisgivesthefollowingexamples:

GLORIAD(GLORIAD,project)
Page38of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

SUNET(SUNET,customer)
SURFnet(SURFnet,partner)

6.2 Contact

Thecontactnamingstandardistousethecontactsfullname.
Thecontactnamewillprobablynotbeuniqueinsomecases,buttherelationand
attributesforthecontactmakethecontactunique.

6.2.1 T he contact naming SY N T A X

TheSYNTAXfornamingacontactis:

<<FIRSTname><LASTname>>

Thisgivesthefollowingexamples:

HeinoRadmer(HeinoRadmer)
LarsLangeBjrn(LarsLangeBjrn)
StefanListrm(StefanListrm)

Page39of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

7 Documentation

ItisverycriticalthattheNamingStandardisbeingfollowed,onlybydoingthatwill
ensurethatadocumentingsystemwillwork,alsoinpractice.Byfollowinganaming
standard,searchingforinformationandrunningscriptsandsoforth,isalsoensured
torunwithoutcomplications.Furthermore,integrationswithotherautomatic
systemshaveabetterchancetosucceed.
ItisstronglyemphasizedtoimplementanduseadedicatedNetworkInventory
system.Aspecificsystemshouldnotbedictated,butathroughoutinvestigationofa
suitablesystemshouldbeconductedwellinadvance.
IfthereisnoNetworkInventorySystemavailableupontheimplementationofthe
namingstandardtothelivenetwork,asimpleexcelsheettypeofstaticdocumentis
advisable.ThiswillensureaquicktransitiontoadatabasedrivenInventorySystem,
sincealldatawithinthesheetcanbeconvertedtoCVSdata.Thebackdrawby
doingsoisthelayoutofthesheettypecouldbeunreadabletocommonpeoplenot
usedtoworkwithdatabases.
IfaNetworkInventorysystemisnotinplace,thedocumentationmustbedonebya
dedicatedstaffonly.

Morehelpwithcreatingaexcelsheettypedocumentcanberequestedto
NORDUnet.

Page40of41

NamingStandards

Date:

Version:

AllRightsReserved:

31102008

1.5

NORDUnetA/S

8 Abbreviations
DDF

DigitalDistributionFrame

FSKnet

Forskningsnettet

FUNET

FinnishUniversityNetwork

ID

IdentifierasspecifiedbytheNREN

MGNT

Management

NI

NetworkInventory

NMS

NetworkManagementSystem

NORDUnet

NordicUniversityNetwork

NREN

NationalResearchandEducationalNetwork

ODF

OpticalDistributionFrame

ODR

OpticalDistributionRack

RM/BM

Managementsoftware

SUNET

SwedenUniversityNetwork

UNINETT

UniversityNetworkNorway

Page41of41