Junjie Tong, China Unicom This presentation explores our experience with the tests on NFVI in China Unicom's SDN/NFV lab.We have done the tests on both the hardware and VIM and discuss the lessones and painis about NFVI testing.We also discuss the sepcial requirements from NFV perspectives, what further improvements are needed for indusrty products and the working progress and plans on NFVI in China Unicom.

2. Test and Perspectives on NFVI
from China Unicom SDN/NFV Lab
Junjie,Tong
China Unicom
June, 2017

3. Content
• Our works in SDN/NFV lab
• Problems we encountered in tests
• Perspectives from the tests

4. Content
• Our works in SDN/NFV lab
• Problems we encountered in tests
• Perspectives from the tests

5.  Goal
• Implement NB-IoT with vEPC in decoupled mode
• Integrate with legacy OSS/BSS
• Mange physical and virtual resources both

6.  Test works
vEPC
Hypervisor
Hardware
VNFM
NFVO
VIM
vEPC
Hypervisor
Hardware
VNFM
NFVO
VIM
Option A
(Step 1)
Option B
(Step 2)
• Compatibility between software
(Virtualized layer) and hardware (sever)
• Hardware management
(configuration&performance&falut)
• MANO functional test (NS&VNF lifecycle
management)
• Virtualized layer functional test
• vEPC functional test (for NB-IoT)

7.  Test progress
2017.2 2017.3 2017.42016.12 2017.6
Preparation
Test cases
Hardware preparation
Option A test
10 servers
4 software vendors
Option B- phase 2
Four combinations
Install and Debug
VIM install and debug
Pre-test of option 1
Option B- phase 1
Four combinations
Option B- phase 3
Two combinations
2017.5

8. Content
• Our works in SDN/NFV lab
• Problems we encountered in tests
• Perspectives from the tests

9.  Maturity problems
Low barriers for industry vendors to involve
Standards have not covered all
Lack test experience & Engineer not proficient
VNFs are virtualized but not cloudified
Too many vendors &large number combinations
Different implementations & hard to justify
Waste a lot of time.
Big VMs flavors without hot migration

10.  Technical problems (Option 1- two layers)
• Compatibility with NICs.
• Compatibility with storage.
• Compatibility with BIOS version of the server.
Most virtualization layer vendors just support one type chip of 10GE.
40GE is not widely supported by hardware and software vendors.
VNFs’ storage implementations are different.
SAN storage’s compatibility is different for software vendors.
Different BIOS tool and command for automatic configuration.
Some software vendors can’t boot with unsuitable BIOS version.

11.  Technical problems (Option 2- three layers)
• 16 combinations with 144 technical problems so far
30%
44%
26%
Problems distribution
Functional support
problem
Parameter configuration
problem
Implementation
differently problem
Most of the problems are about configuration.

12.  Technical problems (Option 2- three layers)
• Transport protocol between MANO
• Keystone
• Support acceleration abilities
For considering the security, HTTPs is a better choice than HTTP.
Certificates interrupt a lot.
Different version.
One version with different comprehension and implementation..
Some vendors cannot support or have a long time to deploy.
Some VNFs cannot use the acceleration abilities right.

13.  Technical problems (Option 2- three layers)
• Suggestions on some key parameters of configuration before test
MTU
Large page in memory
Number of VFs
Openstack version
CPU pinning
OVS
OVS+DPDK
SR-IOV
Vlan
Vxlan
……

14.  Operation and maintenance problem: with legacy OSS/BSS
VNF
Virtualise
d
Infrastruct
ure
Manager
(VIM)
NFV
I
EM
VNF
Catal
ogue
Or-Vi
Ve-Vnfm-vnf
Ve-Vnfm-em
Nf-Vi
Vn-Nf
NFV Orchestrator (NFVO)
NFV-MANO
OSS/BSS
NFVI
Reso
urces
Or-Vnfm
Vi-Vnfm
NFV
Insta
nces
NS
Catal
ogue
VNF
Manager
(VNFM)
VNF
Virtualised
Infrastruct
ure
Manager
(VIM)
NFVI
EM
VNF
Catal
ogue
Or-Vi
Ve-Vnfm-vnf
Ve-Vnfm-em
Os-Ma-nfvo
Nf-Vi
Vn-Nf
NFV Orchestrator (NFVO)
NFV-MANO
OSS/BSS
NFVI
Reso
urces
Or-Vnfm
Vi-Vnfm
NFV
Insta
nces
NS
Catal
ogue
VNF
Manager
(VNFM)
No interface between NFVO and legacy
OSS/BSS
• EMS correlates the virtualization resources with
VNF, and VNF FCAPS can be managed in
OSS/BSS
• Independent operation and management.
With Interface between NFVO and legacy
OSS/BSS
• VNF and PNF are both managed in OSS/BSS.
• OSS/BSS has the overall view of the resource
and NFs.

15.  Operation and maintenance problem: hardware management
HP LenovoDell other
Hardware Mgt.
VIM
VNFM
NFVO
Hypervisor
VNFVNF
EMSEMS
OSS/BSS
Hardware management integrated with
VIM
• VIM can manage the physical and virtual
resource both including the correlation
• VIM has to adapt to different servers
Hardware mgt
VNF
EM
HW
Hypervisor
MANOVNF
EM
Hypervisor
HW
MANO
Independent system for hardware
management
• Standard interfaces for MANO
• Standard south and north interfaces are difficult
to defined

16. Content
• Our works in SDN/NFV lab
• Problems we encountered in tests
• Perspectives from the tests

17.  Perspective 1 : Some barriers or pre-test platforms for vendors
• Maybe some fundamental tests about the products
• CSPs accept the results and use them to select the vendors roughly
• OPNFV maybe a good platform to build this
• Standard/Automatic test methods and environment are needed

18.  Perspective 2 : Standards and open sources need to be
accelerated and harmonized
• Standards are not mature enough for industry solution
designing and commercial deployment
• Open sources are not mature enough for interoperable
with industry solutions
• Standards and open sources are not synchronized

19.  Perspective 3 : Re-construct of VNFs
• VNFs have large VM flavors which makes resource
fragmented
• VNFs have its own fault management which wastes resource
• There are no data or common service sharing between VNFs

20. The end, thanks !