OTU4 data import
•OTU4 List will be fetched from connectivityData-Export-*.xml. Where the element <Path> child node Layer contains “otu4“
•Otu4,Odu4 and ODU2 topology will be “Point/Point“ and Operation type will be “Duplex“
•Following rules will be included for further to filter out OTU4 element creation and given element parent route constrution
oUnavailable OCHs and Opticals will be created
oWhen parent path created it will start from module name contains “CSP“ and finish the element module name contains “CSP“ and Inital parent route will be Optical then it routed via OCH and then finishes on Optical route
▪Primary path starts on point “2“ or point “5“ and finishes either on point “2“ or point “5“ (Both ways path will to active)
▪Secondary path starts on point “3“ or point “6“ and finishes either on point “3“ or point “6“
▪
▪
oIgnore parent element rule
▪Element A module name and Z module name are same
▪Element A module name contains “CSP“ and Z module Contains “IO2“
▪Element A module name “CSP“ and Z module name contains “MDS“ and OCH list not contains A element’s same port number
▪Element Z module name “CSP“ and A module name contains “MDS“ and OCH list not contains A element’s same port number
o(**) OMS parent route will be created for OCHs, which are parents of given OTU4 and following conditions will be considerd at the time of OMS creation(When OMS not exist in oms.json list)
▪Element A module name contains “MDS“ and Z module Contains “LAMIC“
▪Element Z module name contains “MDS“ and A module Contains “LAMIC“
▪Element A module name contains “LAMPBC“ and Z module Contains “LAMIC“
▪Element Z module name contains “LAMPBC“ and A module Contains “LAMIC“
▪Element A module name contains “MDS“ and Z module Contains “LAMPBC“
▪Element Z module name contains “MDS“ and A module Contains “LAMPBC“
▪Element A module name contains “LAMIC“ and Z module Contains “LAMPBC“
▪Element Z module name contains “LAMIC“ and A module Contains “LAMPBC“
▪Element A orZ module name contains “CSP or MDS“ related Optical will be fetched
▪For all above mentioned senarios the A port will be set to “Tx“ and Z port will be set to “Rx“
•Standard attribute mapping in DSE Manager
•OTU4.json element as follows
•Port name will be mapped via intermediate files.(Please refer OTS.Json element section)