| commit | 7bce769758fb0212bb30e445c8478226802f42e4 | [log] [tgz] |
|---|---|---|
| author | Keita NISHIMOTO <nishimoto@opennetworking.org> | Sat Jan 19 09:31:09 2019 +0900 |
| committer | Keita NISHIMOTO <nishimoto@opennetworking.org> | Thu Jan 24 17:33:58 2019 +0900 |
| tree | 4f094c36bc0180e10fca758b79e23905755f1515 | |
| parent | 9dbdad44251b1e7119571e0c03525b972b389909 [diff] |
VOL-1357 BBSim - OMCI status management AddFlow() triggers the update of ONU status into ONU_OMCIACTIVE. The ONU status update is notified to the mediator, and then, it activates the tester. Change-Id: I1a077026b872868a74a4b5d9849b65cf52baeaa4
The BBSim (Broadband Simulator) is for emulating the control message response (e.g. OLTInd, DHCP, EAPOL, OpenOMCI messages etc..) sent from OLT and ONUs which are connected to VOLTHA Adapter (OpenOLT Adapter). It is implemetend as a software process which runs outside VOLTHA, and acts as if it was a OLT connected to multiple ONUs. This enables the scalability test of VOLTHA / ONOS without actual hardware OLT / ONUs. The BBSim container contains wpa_supplicants and dhcp clients inside, so that you can try to test AAA/DHCPL2Relay Apps on ONOS using BBSim. The difference from the existing PONsim is to focus on emulating control messages, not data-path traffic which PONsim targets.
============== VOLTHA OpenOLT Adapter ============== | | gRPC connections | ============== BBSim containers (Each BBSim container corresponds to a single olt) ==============
※ You need to configure SADIS before you start to run BBSim, if you want to test AAA/DHCP (Refer to section 3).
# Build and Run Docker container
git clone https://github.com/opencord/voltha-bbsim
cd voltha-bbsim
make docker
docker run -it --rm --privileged=true --expose=50060 --network=compose_default voltha/voltha-bbsim ./bbsim -n 16
# After this, execute the following commands from VOLTHA-CLI
(voltha) health
{
"state": "HEALTHY"
}
(voltha) preprovision_olt -t openolt -H <BBSim Docker container IP>
success (device id = <deviceid>)
(voltha) enable
enabling <deviceid>
waiting for device to be enabled...
success (device id = <deviceid>)
(voltha) devices
## You can see the list of devices (OLT/ONUs) ##
You need to configure a few parameters for AAA/DHCPL2Relay app before running BBSim. You only need to set 1. device id assigned to BBSim (i.e. of:*********), 2. IP Address of BBSim container and 3. c/sTag with BBSim ONU instance device id, in .netconf file. (Please refer to https://wiki.onosproject.org/display/ONOS/NETCONF about netconf support in ONOS)
"org.opencord.dhcpl2relay" : {
"dhcpl2relay" : {
"dhcpServerConnectPoints" : [ "<device id assigned to BBSim>/65536" ],
"useOltUplinkForServerPktInOut" : true
}
},
....
"org.opencord.sadis" : {
"sadis" : {
"entries":[
{
"id" : "<IP Address of BBSim Container>:50060",
"hardwareIdentifier" : "de:ad:be:ef:ba:11",
"uplinkPort" : 65536
},
//BBSim generates both device id and c/stag assigned to each ONU while incrementing them by 1 from BBSM00000100, 900.
//The following lines are an example when we use for configuring 2 ONUs.
{"id" : "BBSM00000100", "cTag" : 900, "sTag" : 900, "nasPortId" : "BBSM00000100"},
{"id" : "BBSM00000101", "cTag" : 901, "sTag" : 901, "nasPortId" : "BBSM00000101"},
......
Usage of ./bbsim:
-H string
IP address:port (default ":50060")
-aw int
Wait time (sec) for activation WPA supplicants (default 10)
-dw int
Wait time (sec) for activation DHCP clients (default 20)
-i int
Number of PON-IF ports (default 1)
-id int
OLT-ID (default: 0)
-m string
Emulation mode (default, aaa, both (aaa & dhcp)) (default "default")
-n int
Number of ONUs per PON-IF port (default 1)
-s string
DHCP Server IP Address (default "182.21.0.1")