@@ -393,6 +393,20 @@ In current implementation, we still have two manual steps to perform after each
* Edit the **src/service/resources/GraphAPI/network_clusters.json** file (on the CLMC container) which maps the IP address of a service router to the host name of the cluster that is connected to this service router
* Edit the **src/service/resources/GraphAPI/network_ues.json** file (on the CLMC container) which maps the IP address of a service router to the host name of a user equipment that is connected to this service router
The information for these files can be retrieved by looking into the platform infrastructure slice, e.g. on the sandpit run `openstack server list`. Then, we can see that cluster 20-sr1-cluster1-cluster is connected through 20-sr1-cluster1-sr. Hence in the **network_clusters.json** we need an entry like the following:
```json
"<ip of 20-sr1-cluster1-sr>":"20-sr1-cluster1-cluster"
```
Similar for the emulated UEs, ue20 is connected through 20-sr2-sr. Hence in the **network_ues.json** we need an entry like the following:
```json
"<ip of 20-sr2-sr>":"ue20"
```
The IP addresses mentioned above must be the IP addresses the service routers receive on the SDN controller network (e.g. flame-sdnctrl)
Afterwards, the platform operator must build the network topology graph by either:
* sending a post request to the graoh API - `curl -X POST http://<clmc-host>/clmc-service/graph/network`
