The reference between physical and traffic/communication view is provided by physical-port-reference parameter. Further reference:  SDNC-774 - Getting issue details... STATUS .

The example shows the parameter, that is part of the ltp parameters and is referencing one or more "equipment" objects, identified by uuid.

A more complete example as XML file can be found here: https://github.com/Melacon/WirelessTransportEmulator/blob/master/NetconfServerSimulator/xmlNeModel/equipment.xml.

For creating a helpfull information for the user, the equipment/name and equipment/label should be used.

The important points are shown in the XML parts:


<network-element>
        ..something..
        <ltp>
            <uuid>LTP-MWPS-TTP-01</uuid>
            ..something..
             <client-ltp>LTP-MWS-TTP-01</client-ltp>
             <!-- SDNC-774: list contains 0 .. N references to related "equipment" objects, identified by uuid -->
             <physical-port-reference>a2.module-1.65.1.2</physical-port-reference> 
             <lp>
               ..something..
             </lp>
</network-element>

<mw-air-interface-pac xmlns="urn:onf:params:xml:ns:yang:microwave-model">
	<layer-protocol>LP-MWPS-TTP-01</layer-protocol>
	<air-interface-capability>
        ..something..
	</air-interface-capability>
</mw-air-interface-pac>

<equipment>
  <uuid>a2.module-1.65.1.2</uuid>
  <name>
    <value-name>name</value-name>
    <value>a2.module attached to Port 1.2 of Subrack connected at WS Shelf, Slot 6, Port 5</value>
  </name>
  <label>
    <value-name>label</value-name>
    <value>MWR#65Ch#1/a2.moduletraff</value>
  </label>
</equipment>




  • No labels