...
git clone https://github.com/onap-oof-pci-poc/ran-sim/Netconf-Agents/hc_50000
cd Netconf-Agents/hc_50000
...
./honeycomb
Check the honeycomb.log in the below folder
<Your_Folder>/hc_50001/var/log/honeycomb/
tail -f honeycomb.log
Successful start yield below log entries,
2018-10-16 14:02:19.975 IST [main] INFO i.f.h.i.d.i.InitializerRegistryAdapter - Honeycomb initialized
For multiple instance,
Copy the EnodebSimSetup.py, start.sh and stop.sh from <Your_Folder>/Netconf-Agents/ folder to the folder in which hc_50000 is copied,
- Run EnodebSimSetup.py with the number of instances required.
./EnodebSimSetup.py 24 (for 24 instances) - Then run start.sh, which will start all the honeycomb servers in the folder(in this case all 24 agents will be started)
- Use stop.sh, to stop all the netconf servers.
Use netstat command to verify all the honeycomb servers are started.
netstat -navp | grep 500
Check the honeycomb.log in the below folder
<Your_Folder>/hc_50001/var/log/honeycomb/
tail -f honeycomb.log
Successful start yield below log entries,
2018-10-16 14: 2018-10-16 14:02:19.975 IST [main] INFO ioi.fdf.h.i.d.i.InitializerRegistryAdapter - Honeycomb initialized
2018-10-16 14:02:19.975 IST [main] INFO io.fd.honeycomb.honeycomb.infra.distro.Main - Configuration initialized successfully
...
And search for below keyword, to make sure the successful connectivity with Ransim Controller:
“Message received: SetConfigTopology:”
This line of log will print the configuration topology of RAN network pulled from Ransim Controller.
Connecting to device from console:
ssh admin@localhost -p 50001 -s netconf
password: admin
After capabilities listed, enter the following command input to connect to device.
received: SetConfigTopology:”
This line of log will print the configuration topology of RAN network pulled from Ransim Controller.
Connecting to device from console:
ssh admin@localhost -p 50001 -s netconf
password: admin
After capabilities listed, enter the following command input to connect to device.
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
</capabilities>
</hello>
]]>]]>
Netconf commands validation:
get:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="102">
<get/>
</rpc>
]]>]]>
This should show the complete topology dumped or simulated from Ransim Controller.
get-config(with filter):
<rpc message-id="m-1" <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
</capabilities>
</hello>
]]>]]>
Netconf commands validation:
get:
<rpc xmlns <get-config>
<source>
<running/>
</source>
<filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="102"> <get/>" ns0:type="subtree">
<radio-access xmlns="org:onap:ccsdk:features:sdnr:northbound:oofpcipoc">
<fap-service>
<alias>Chn0001</alias>
</fap-service>
</radio-access>
</filter>
</get-config>
</rpc>
]]>]]>This should show the complete topology dumped or simulated from Ransim Controller.
edit-config:
<rpc
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
...