...

Typical Errors and Solutions

SDNC DG

...

error

If you run vcpe.py customer and see an error similar to the following:

...

It is most likely due to an error in vnf-topology-assign DG. This happends in R2 and should have been fixed in R3 (refer 

• Enter the SDNC docker

• 1. make a copy of GENERIC-RESOURCE-API_vnf-topology-operation-assign.xml in the sdnc_controller_container under /opt/sdnc/svclogic/graphs/generic-resource-api

  2. edit GENERIC-RESOURCE-API_vnf-topology-operation-assign.xml to replace "<break> </break>" with "<break/>" or "<break></break>"

  a. optionally you can change the version to something like 1.3.3-SNAPSHOT-FIX and update graph.versions to match but that is not needed if the xml failed to load .

  3. run /opt/sdnc/svclogic/bin/install.sh 

  this will install the edited DG and make it active as long as the version in the xml and the version in graph.versions match

  4. re-run /opt/sdnc/svclogic/bin/showActiveGraphs.sh and you should see the active DG

DHCP server doesn't work

1. ssh to the dhcp server
2. systemctl status kea-dhcp4-server.service
3. If the service is not installed, do 'apt install kea-dhcp4-server.service'
4. If the service is installed, most likely /usr/local/lib/kea-sdnc-notify.so is missing. Download this file from the following link and put it in /usr/local/lib.  Link: kea-sdnc-notify.so
5. systemctl restart kea-dhcp4-server.service