Management Network Plan (Recommended)

When deploying an SDN DCN, plan the service network and management network separately.

A management network is used by DC administrators to remotely manage servers and network devices. This dedicated network may provide in-band or out-of-band management. For in-band management, which applies to small-scale networks, management traffic and service traffic share forwarding links. For out-of-band management, which applies to large-scale and complex networks, dedicated devices carry management traffic that is separated from the service network. The following uses out- of-band management as an example to describe how to plan a management network.

Management Network Deployment Plan

As shown in Figure 9.17, the SDN controller server cluster, SecoManager server cluster, cloud platform controller nodes, and VMM controller nodes are deployed on a management network, separate from the service network.

• The NICs of the SDN controller server cluster, SecoManager server cluster, cloud platform controller nodes, and VMM controller nodes are connected to the management access switches in active/standby or load balancing mode.

Independent deployment of the management network

FIGURE 9.17 Independent deployment of the management network.

  • • If the controller node of the cloud platform must provide the DHCP function, independent cables need to be deployed to connect this node to the server leaf nodes on the service network. The administrator needs to perform only basic configurations, and the SDN controller will automatically deliver other configurations.
  • • The SDN controller and SecoManager are connected to the server leaf nodes of the service network with independent cables. To implement Layer 3 interconnections for the managed IP addresses of devices, the southbound network segment of the controller is deployed and advertised in the routing protocol on the underlay network.
  • • The SDN controller northbound gateway, SecoManager northbound gateway, Fabriclnsight (not shown in the figure) external access plane gateway, cloud platform, and VMM-related network planes are manually deployed on the management network using VLANIF interfaces. In this case, a dedicated management VPN is planned. The northbound network segment of the SDN controller, northbound network segment of the SecoManager, network plane used by the cloud platform, and VMM-related network plane are reachable at Layer 3, facilitating system interconnections.
  • • On the service network, network devices’ management ports and servers’ Baseboard Management Controller (BMC) ports are connected to the access switches (not shown in the figure) on the management network. An independent network plane is planned so that the administrator can perform unified remote management.
  • • On the service network, the compute node of the cloud platform or VMM is connected to a management access switch with an independent cable, and communicates with the controller node of the cloud platform or VMM, respectively. In addition, independent cables are deployed to connect to the storage network (not shown in the figure). [1]

SDN Controller Deployment Plan (Recommended)

An SDN controller cluster is typically deployed on three physical servers and, based on the services that are carried, can be divided into the following three network planes:

  • • Network plane for the internal communication zone: used for internal communication in the cluster, such as communication between different nodes and communication with the database.
  • • Network plane for northbound management: used for northbound communication and Linux management, including interconnections with the cloud platform, web access, and Linux login.
  • • Network plane for the southbound service zone: used to communicate with network devices through protocols such as NETCONF, SNMP, and OpenFlow.

The first two planes can be combined for deployment, whereas two independent network planes should be planned for the southbound service zone. For each network plane, allocate two physical network ports.

Figure 9.18 shows the cable connections when SDN controller is deployed.

Table 9.3 describes the dual-plane plan of server ports.

Connection between the SDN controller and SecoManager servers

FIGURE 9.18 Connection between the SDN controller and SecoManager servers.

Server

Network Port

IP Address (Example)

Description

Server1

bondO (ethO & ethl)

192.168.12.1/24

Internal communication and northbound management

bondl (eth2 & eth3)

192.168.2.1/24

Southbound service

Server2

bondO (ethO & ethl)

192.168.12.2/24

Internal communication and northbound management

bondl (eth2 & eth3)

192.168.2.2/24

Southbound service

Server3

bondO (ethO & ethl)

192.168.12.3/24

Internal communication and northbound management

bondl (eth2 & eth3)

192.168.2.3/24

Southbound service

  • [1] If conditions permit, you are advised to deploy management accessand aggregation switches in a stack or M-LAG in order to improvereliability. On the management network, VLANIF interfaces areconfigured on the aggregation switches and VLAN on the accessswitches.
 
Source
< Prev   CONTENTS   Source   Next >