SD-Wan as a Service Demo
Test using the following ova containing a running version of OSM with vim-emu.
-
Run ./init.sh to create networks that are external to OSM
-
Start the VNX scenario vnx/sdedge_nfv.xml
sudo vnx -f vnx/sdedge_nfv.xml -t- Create docker images in img
cd img/vnf-access
sudo docker build -t vnf-access .
cd ../vnf-cpe
sudo docker build -t vnf-cpe .
cd ../vnf-wan
sudo docker build -t vnf-wan .
cd ..-
Onboarding on OSM of vnfs and network service from pck folder. To create the sdedge network service description, edit the provided corpcpe and include the wan-vnf.
-
Registration of two vim-emu instances
bin/osm-restart-vimemu2 -
Instantiation of sdedge1 on central1-x and sdedge2 on central2-x with OSM
-
Run
./sdedge1
./sdedge2 # sdedge2 script not distributed. Create it by cloning and adapting sdedge1.
./policies- Start vnf consoles
bin/sdw-manage-vnf-consoles open- Test connectivity
- From host capture isp1-isp2 traffic:
tshark -i isp1-e2-
Between remote sites:
-
From h1 to h2 ping 10.20.2.2 Traffic goes through isp1 and isp2
-
From t1 to t2 ping 10.20.2.200 Traffic is not captured, it is forwarded through MPLS
-
-
From a site to a central voip-gw: from h1, ping 10.20.0.254 Traffic is forwarded throuh MPLS
- Terminate instances using:
./ns_terminate.sh sdedge1
./ns_terminate.sh sdedge2