OITIN030101 SDN Commonly Used Protocols
OITIN030101 SDN Commonly Used Protocols
OITIN030101 SDN Commonly Used Protocols
Contents
Typical Application Scenario of SDN ...................................................................................... 1
Configure Interconnection between SNC and Netmatrix
Task Description ............................................................................................................................................. 4
Objectives ....................................................................................................................................................... 4
Networking Topology ...................................................................................................................................... 4
Configuration Tasks ........................................................................................................................................ 5
Configuration Flowchart.................................................................................................................................. 6
Preparation ...................................................................................................................................................... 6
Configuration Procedures and Verification ....................................................................................................... 7
Summary .................................................................................................................................... 22
In conjunctions with the rapid growth and emergence of SDN networks, various types of protocols are
deployed, which might vary based on different SDN solutions applied according to live network
applications. This section generally describes the commonly used protocols in SDN applications, such as
Openflow, SNMP, Netconf etc.
Diagrams below show the examples of a few types of Huawei SDN solutions. The similarities of each
solution here is that all the SDN solutions will definitely comprise of the SDN network elements such as
SNC controller, NetMatrix Orchestrator, and the forwarding device, which is also known as forwarder. In
certain solutions such as IP + Optical solution or TSDN solutions, there are some other additional SDN
elements being deployed, which are the U2000 and utraffic. To allow all these elements to be able to
communicate with each other, different communication protocols are deployed and will be discussed
briefly on the section below.
In RR+ networking solution, SNC serves as the controller in control plane, which is used to manage
topology information, calculate traffic control results and delivers the calculated routes to the forwarder
using BGP or IGP. Netmatrix serves as the orchestrator used to configure traffic policy to trigger traffic
controller towards SNC. The SNC uses NETCONF to send automatically calculated traffic control paths to
the NetMatrix, which then displays these paths for users to confirm. Utraffic serves as the flow acquisition
and analysis equipment which uses traffic analysis results to identify traffic. Its communication protocol
with forwarders is SNMP. SFTP is used to allow data exchange between Netmatrix and utraffic.
As for VxLAN networking solution, NETCONF protocol is used as the communication protocol between
Netmatrix and SNC controller while Openflow protocol is used for communication between SNC controller
and forwarder.
Besides, as we have already discussed in the previous topics, the control channel built between SNC
controller and forwarder can be divided into 2 types, which are inband and outband networking. As for
outband networking, dedicated network is built for control traffic between controller and forwarders; while
for inband networking, control channel and service data network are shared in the same network topology.
Regardless of inband or outband networking methods, the reach-ability between SNC controller and
forwarders can be realized through traditional layer 2 networking technologies such as VLAN or MSTP, or
layer 2 networking protocols such as OSPF, ISIS, BGP etc. In layer 2 networking, controller and forwarders
are located in the same network segments and VLAN technology can be used to segregate control and data
traffic. As for layer 3 networking, routing protocols such as OSPF or ISIS helps in achieving route
reach-ability between SNC controller and every forwarders even they are located in different network
segments.
Task Description
This lab practice describe NETCONF configuration between Netmatrix and SNC.
Objectives
Upon completion of this course, you will be able to:
Verify the NETCONF communication channel between SNC controller and Netmatrix
Networking Topology
NETCONF ensures security and extensibility. When the NMS is used to manage network devices, you can
use NETCONF to ensure communication between the NMS and the devices.
As shown in the topology diagram below, the NMS is deployed on the NETCONF manager that functions
as the SSH client. The NETCONF agent functions as the SSH server that receives connection requests from
and establishes the connection with the SSH client. SSH is a security protocol at the application layer,
enhancing the reliability of NETCONF. In this networking, NETCONF is used to manage the configuration
of the SSH server.
Configuration Tasks
Task Description
1. Configure a local user account for logging Configure the local user name and password for login.
in to the SNC
Configure the access type of the local user
Configuration Flowchart
Preparation
To complete the configuration, you need to prepare the following:
2. All interconnection IP address between SNC and Netmatrix have been configured
correctly. SNC is able to ping to Netmatrix and vice versa.
[*SNC] aaa
[*SNC-aaa] local-user huawei password irreversible-cipher Changeme_123
[*SNC-aaa] local-user huawei service-type ftp terminal telnet ssh
[*SNC-aaa] commit
[*SNC-aaa] quit
[~SNC] quit
Configuring NetMatrix
NETCONF is the communication protocol used by NetMatrix to send configuration information such as
topology information, calculation parameter, path information and constraints parameters to SNC.
Pre-requisite Configuration
Before performing NE, you have to pre-define the SNC equipment role under the selection Network >
Physical Network Resources > Device > RR+ Device. After this configuration, SNC device defined will
automatically be shown under “Netconf Configuration”
Configuration Step
Step 1 Choose Network from the main menu
Step 2 Choose Physical Network Resource > Netconf Configuration from the navigation tree
Step 3 Set IP, Port, User Name, and Password, and click Password
Parameter Remarks
IP SNC server login IP. The SNC login IP is one of the pre-requisite
information that should be obtained earlier.
Port SSH login port number. The default port number for SSH is 22.
Parameter Remarks
3. Click “Create”; Configure affinity attributes such as color and value (for example, red, 20), and
click “save”
4. Click “Deploy”; if message “Operation succeeds” appear, it means that Netconf is configured
properly on both SNC and Netmatrix.
Step 2 Run the “display ssh server status” command to view global configuration of the SSH server.
Step 3 Run the “display ssh server session” command to view sessions between the SSH server and the SSH
client.
Step 4 Run the “display netconf capability” command to view the capabilities that the NETCONF agent
supports.
Task Description
There might have different communication protocols used to configure the interconnection between SNC
and forwarders based on different types of SDN solutions. This lab mainly focuses only on Openflow
configuration between SNC and forwarders, which is used in VxLAN scenario.
Objectives
Upon completion of this course, you will be able to:
Networking Topology
The use of an SDN controller simplifies network operation and maintenance. A controller and a forwarder
establish a neighbor relationship using the OpenFlow protocol over an OpenFlow channel. After an OpenFlow
channel is established, the controller manages forwarders using OpenFlow. The forwarder reports its node and
interface information to the controller, and the controller delivers configurations to the forwarder.
Configuration Tasks
Task Description
1 Configure routing protocol, (OSPF is used in this lab practice) to achieve route reach-ability
between SNC and forwarders which are directly or indirectly connected.
Preparation
To complete the configuration, you need to prepare the following:
2. All interconnection IP address, and loopback IP address as per stated in the topology
diagram above has been configured properly based on the IP address planning shown in
the diagram above
<HUAWEI> system-view
[~HUAWEI] sysname SNC
[*HUAWEI] commit
<HUAWEI> system-view
[~HUAWEI] sysname FP3
[*HUAWEI] commit
OSPF Verification
After performing OSPF configuration, perform ping test from SNC controller to every forwarder to verify
route reach-ability is established. If the ping test is successful like the verification result below, it means
that OSPF is configured correctly.
3. Configure FP ID for each forwarder; in this configuration, FP1 is configured as FP ID 1; FP2 is configured
as FP ID 2; FP3 is configured as FP ID3. Configuration below is for configuring peer to FP1
[*SNC-sdn-controller] fp-id 1
4. Configure SDN controller type; Huawei-default is referring to Huawei equipment serves as the SDN
controller; ovs-default is referring to Openvswitch equipment serves as the SDN controller
[*SNC-sdn-controller-fp1] type huawei-default
7. Configure the control channel between SDN controller and forwarders to use Openflow protocol and enter
Openflow interface view
[*SNC-sdn-controller-fp1] openflow controller
8. Specify the loopback IP address of the forwarder FP1 in Openflow interface view
[*SNC-sdn-controller-fp1-openflow] peer-address 1.1.1.1
[*SNC-sdn-controller-fp1-openflow] quit
[*SNC-sdn-controller-fp1] quit
[*SNC-sdn-controller] quit
[*SNC] commit
Repeat the configuration to configure SNC to establish OpenFlow peer connection to FP2 and FP3. The
configuration scripts are shown as below:-
[*SNC-sdn-controller] fp-id 3
[*SNC-sdn-controller-fp3] type huawei-default
[*SNC-sdn-controller-fp3] version default
[*SNC-sdn-controller-fp3] role default
[*SNC-sdn-controller-fp3] openflow controller
[*SNC-sdn-controller-fp3-openflow] peer-address 3.3.3.3
[*SNC-sdn-controller-fp3-openflow] quit
[*SNC-sdn-controller-fp3] quit
[*SNC-sdn-controller] quit
[*SNC] commit
The configuration on FP1, FP2 and FP3 are similar and explanation on the configuration below is based on
configuration on FP1
2. Specify SNC controller Loopback IP address and enter SDN controller view
[*FP1-sdn-agent] controller-ip 4.4.4.4
3. Configure the control channel between SDN controller and forwarders to use Openflow protocol and enter
Openflow agent view
[*FP1-sdn-agent-ctrl-1.1.1.1] openflow agent
Repeat the similar configuration on FP2 and FP3, as shown on the configuration scripts below:-
Configuration on FP2:
<FP2> system-view
[~FP2] sdn agent
[*FP2-sdn-agent] controller-ip 4.4.4.4
[*FP2-sdn-agent-ctrl-1.1.1.1] openflow agent
[*FP2-sdn-agent-ctrl-1.1.1.1-openflow] transport-address 2.2.2.2
[*FP2-sdn-agent-ctrl-1.1.1.1-openflow] quit
[*FP2-sdn-agent-ctrl-1.1.1.1] quit
[*FP2-sdn-agent] quit
[*FP2] commit
Configuration on FP3:
<FP3> system-view
[~FP3] sdn agent
[*FP3-sdn-agent] controller-ip 4.4.4.4
[*FP3-sdn-agent-ctrl-1.1.1.1] openflow agent
[*FP3-sdn-agent-ctrl-1.1.1.1-openflow] transport-address 3.3.3.3
[*FP3-sdn-agent-ctrl-1.1.1.1-openflow] quit
[*FP3-sdn-agent-ctrl-1.1.1.1] quit
[*FP3-sdn-agent] quit
[*FP3] commit
OpenFlow Verification
After completing all configurations, execute the command “display sdn openflow session” on SDN
controller and forwarder. If the status of the result is shown “REGISTERED”, it represents the OpenFlow
control channel has been established successfully. Below shows and example of the verification result:
Summary
Upon completion of this integrated lab practice, you should be able to configure:-