3 If all goes well the commands and its responses looks like this:
6 demx8as6@oam.orbit-lab.org$ docker-compose -f smo/common/docker-compose.yml up -d
7 Creating zookeeper ... done
8 Creating identity ... done
9 Creating persistence ... done
10 Creating kafka ... done
11 Creating onap-dmaap ... done
13 demx8as6@oam.orbit-lab.org$ python smo/common/identity/config.py
15 User leia.organa created!
17 User luke.skywalker created!
18 User jargo.fett created!
19 User martin.skorupski created!
20 User demx8as6 created!
21 User role demx8as6 administration created!
22 User role jargo.fett supervision created!
23 User role leia.organa administration created!
24 User role luke.skywalker provision created!
25 User role martin.skorupski administration created!
26 User role r2.d2 administration created!
28 demx8as6@oam.orbit-lab.org$ docker-compose -f smo/oam/docker-compose.yml up -d
29 WARNING: Found orphan containers (kafka, persistence, identity, zookeeper, onap-dmaap) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
30 Creating sdnc-web ... done
31 Creating sdnr ... done
32 Creating ves-collector ... done
34 demx8as6@oam.orbit-lab.org$ docker-compose -f network/docker-compose.yml up -d
35 Creating ntsim-ng-o-du-1122 ... done
36 Creating ntsim-ng-o-ru-fh-11223 ... done
37 Creating ntsim-ng-o-ru-fh-11221 ... done
38 Creating ntsim-ng-o-ru-fh-11222 ... done
40 demx8as6@oam.orbit-lab.org$ docker restart ntsim-ng-o-du-1122
43 demx8as6@oam.orbit-lab.org$ python network/config.py
49 demx8as6@oam.orbit-lab.org$
52 # Verification with ODLUX
54 The ODLUX web application is accessible at port 8453.
57 https://sdnc-web:8453/
62 At the 'Connect' page, 4 connections to the simulated network should be in state 'connected'. This validates the secure (TLS) VES:PNF-Registration and NETCONF CallHome onboarding is correctly configured for IPv6.
64 ![Automated onboarding using NETCONF CallHome or VES:PNF-Registration](docs/smo-oam-test-01.png "Automated onboarding using NETCONF CallHome or VES:PNF-Registration")
68 The simulated Network is configured in a way that spontaneous fault messages are send to the SMO using the VES or the NETCONF protocol.
70 At the 'Fault' page on tab 'Alarm Log' NETCONF and VES fault notification should be visible.
72 ![Fault notification (NETCONF and VES)](docs/smo-oam-test-02.png "Fault notification (NETCONF and VES)")