Aruba JL849AAE Configuration Guide

IMC Orchestrator 6.2 Underlay Network

Configuration Guide

The information in this document is subject to change without notice.

i 
Contents 
Overview ························································································1 
Restrictions and guidelines ·································································2 
Management network configuration ······················································3 
Network configuration ··················································································································· 3 
Configuration example ·················································································································· 4 
Manual underlay network deployment ···················································6 
Network plan ······························································································································· 6 
Network plan for spine-border integration scenario ······································································ 6 
Network plan for spine-border separation scenario ···································································· 10 
Deployment workflow ·················································································································· 14 
Deployment workflow for spine-border integration scenario ························································· 14 
Deployment workflow for spine-border separation scenario ························································· 17 
Procedure (spine-border integration scenario) ················································································· 20 
Configure Spine Border 1 ······································································································ 20 
Configure Spine Border 2 ······································································································ 33 
Configure Server Leaf 1 ········································································································ 47 
Configure Server Leaf 2 ········································································································ 59 
Configure Service Leaf 1 ······································································································ 71 
Configure Service Leaf 2 ······································································································ 82 
Procedure (spine-border separation scenario) ················································································· 93 
Configure Spine 1················································································································ 93 
Configure Spine 2·············································································································· 100 
Configure Server Leaf 1 ······································································································ 107 
Configure Server Leaf 2 ······································································································ 118 
Configure Service Leaf 1 ···································································································· 130 
Configure Service Leaf 2 ···································································································· 141 
Configure Border 1 ············································································································ 152 
Configure Border 2 ············································································································ 165 
Automatic underlay network deployment ··········································· 180 
Network plan ··························································································································· 180 
Networking diagram and IP address plan ··············································································· 180 
IP address pool plan ·········································································································· 184 

ii 
Deployment workflow ················································································································ 185 
Traditional automatic deployment workflow ············································································ 185 
Wizard-based automatic deployment workflow ········································································ 185 
Traditional automatic deployment procedure ················································································· 186 
Configure IMC Orchestrator basic settings ············································································· 186 
Configure automatic deployment ·························································································· 187 
Configure automatic device deployment ················································································ 198 
Verify the configuration ······································································································· 201 
Wizard-based automatic deployment procedure ············································································· 202 
Configure IMC Orchestrator basic settings ············································································· 202 
Configure automatic deployment ·························································································· 203 
Configure device information ······························································································· 210 
Check device deployment ··································································································· 213 
Configure automatic device deployment ················································································ 213 
Verify the configuration ······································································································· 217 
Scale up the network ········································································································· 218 
Configure link expansion ····································································································· 222 
Underlay network deployment in four-in-one scenario ·························· 225 
Automatic underlay configuration ································································································ 225 
Manual underlay configuration ···································································································· 225 
Network plan ···················································································································· 225 
Deployment workflow ········································································································· 228 
Configure four-in-one device 1 ····························································································· 230 
Configure four-in-one device 2 ····························································································· 241 
Configure Server Leaf 1 ······································································································ 253 
Configure Server Leaf 2 ······································································································ 262 
Manual underlay network deployment in five-in-one scenario ················· 273 
Network plan ··························································································································· 273 
Deployment workflow ················································································································ 275 
Configure five-in-one device 1 ···································································································· 275 
Reboot the device without a startup configuration file ······························································· 275 
Configure hardware resource parameters ·············································································· 276 
Configure the management network······················································································ 276 
Configure basic settings for L2VPN and VXLAN ······································································ 277 
Configure the underlay routing protocol ················································································· 277 
Configure the VTEP address ······························································································· 278 
Configure the overlay BGP ·································································································· 278 
Enable the OVSDB VTEP service ························································································· 278 
Configure the global MAC address ······················································································· 278 
Configure the DRNI physical address ···················································································· 278 

iii 
Configure the DRNI virtual address ······················································································· 279 
Configure DR system parameters ························································································· 279 
Configure the DRNI IPP aggregate interface ·········································································· 279 
Configure DRNI MAD ········································································································· 280 
Configure the IPL escape channel ························································································ 280 
Configure the IPL bypass channel ························································································ 281 
Configure VXLAN default decapsulation ················································································ 281 
Configure automatic recovery time of DRNI device after startup ················································· 281 
Configure the DR interface connected to FW ·········································································· 281 
Configure the DR interface connected to LB ··········································································· 282 
Configure the DR interface connected to the external LACP aggregate link ·································· 283 
Configure the DR interface connected to Server 1 LACP aggregate link ······································ 284 
Configure the physical interface connected to Server 2 primary and secondary links ······················ 284 
Save the configuration ········································································································ 285 
Incorporate devices on the controller ····················································································· 285 
Configure five-in-one device 2 ···································································································· 288 
Reboot the device without a startup configuration file ······························································· 288 
Configure hardware resource parameters ·············································································· 288 
Configure the management network······················································································ 289 
Configure basic settings for L2VPN and VXLAN ······································································ 290 
Configure the underlay routing protocol ················································································· 290 
Configure the VTEP address ······························································································· 290 
Configure the overlay BGP ·································································································· 290 
Enable the OVSDB VTEP service ························································································· 290 
Configure the global MAC address ······················································································· 291 
Configure the DRNI physical address ···················································································· 291 
Configure the DRNI virtual address ······················································································· 291 
Configure DR system parameters ························································································· 291 
Configure the DRNI IPP aggregate interface ·········································································· 292 
Configure DRNI MAD ········································································································· 292 
Configure the IPL escape channel ························································································ 293 
Configure the IPL bypass channel ························································································ 293 
Configure VXLAN default decapsulation ················································································ 293 
Configure automatic recovery time of DRNI device after startup ················································· 294 
Configure the DR interface connected to FW ·········································································· 294 
Configure the DR interface connected to LB ··········································································· 295 
Configure the DR interface connected to the external LACP aggregate link ·································· 296 
Configure the DR interface connected to Server 1 LACP aggregate link ······································ 296 
Configure the physical interface connected to Server 2 primary and secondary links ······················ 296 
Save the configuration ········································································································ 297 
Incorporate devices on the controller ····················································································· 298 

iv

(Optional) Enhance network security ················································ 302

Configure packet suppression ···································································································· 302

Configure ARP attack protection ································································································· 302

Configure BPDU guard ············································································································· 302

O&M monitoring ··········································································· 304

1

Overview

The underlay network of the data center is a physical network that carries overlay services and

contains switches such as spine and leaf devices. To deploy overlay services, incorporate underlay

network devices on the data center controller first. This document describes how to incorporate

underlay network devices on the controller.

There are two methods to incorporate underlay network devices on the controller:

• Manual underlay network deployment—This method requires manual pre-configuration on

the devices. After pre-configuration, the underlay network devices can be incorporated by the

controller.

• Automatic underlay network deployment—This method does not require pre-configuration

of underlay devices. You only need to configure templates on the controller and start the

devices without a startup configuration file. The devices can be automatically incorporated by

the controller.

As a best practice, use DRNI to deploy the underlay network for the IMC Orchestrator solution.

2

Restrictions and guidelines

• The addresses in this document are for reference only. Please plan the addresses used in

actual network deployment in advance.

• To facilitate subsequent fabric expansion, adopt Layer 3 networking when you deploy the

management network.

• When you use DRNI to deploy the underlay network, follow these guidelines:

 The DR member devices in a DR system must use the same DR system MAC address.

Make sure the DR system MAC address is unique across the whole network.

As a best practice, use the bridge MAC address of one DR member device in the DR

system as the DR system MAC address.

 The DR member devices in a DR system must use different DR system numbers.

For example, set the system number to 1 for DR member device 1 and to 2 for DR

member device 2.

 The DR system priority for the DR member devices in a DR system must be the same.

• You must enable the allowlist function and configure the device list for auto device

deployment in DRNI scenario. Only the devices added to the device list can be automatically

deployed and be incorporated by the controller.

• To avoid DRNI dual-active issues and ensure high availability when both the DRNI keepalive

link and the IPL are down, configure a DRNI MAD DOWN action as follows:

 In an aggregation scenario, enable DRNI standalone mode for the DR member devices:

<Sysname> system-view

[Sysname] drni standalone enable

 In a primary/secondary scenario, enable DRNI MAD DOWN state persistence for the DR

member devices:

<Sysname> system-view

[Sysname] drni mad persistent

• After you enable DRNI MAD DOWN state persistence, a DRNI dual-active issue will occur if

the keepalive link goes down earlier than the IPL does. In this situation, contact Technical

Support.

• Note: The default VXLAN ID range for a switch is 0 to 16777215. If you use the l2vpn drni

peer-link ac-match-rule vxlan-mapping command on a switch in the DMI scenario,

the IDs of the VXLANs created on the switch cannot exceed 16000000. #

• When S12500X acts as a border or leaf device, use the ip load-sharing mode per-flow tunnel

all global command on the device. The device can then perform per-flow load sharing based

on both outer and inner IP header information.

3

Management network configuration

Network configuration

In the data center network, a separate switch is usually used to connect devices and the

management network of the IMC Orchestrator controller. Such a switch is called a management

switch. The management switch requires manual configuration and is not incorporated by the IMC

Orchestrator controller.

The management network of the data center can adopt either Layer 2 networking or Layer 3

networking. For Layer 2 networking, the management network of physical devices and the IMC

Orchestrator management network are located in the same network segment. For Layer 3

networking, the management networks are located in different segments.

Layer 2 networking applies to single-fabric networks. The management network of multi-fabric

networks must use the Layer 3 networking mode. For Layer 3 networking, you need to configure

VLANs for the fabric on the management switch, and manually configure the gateway and DHCP

relay agent commands.

As a best practice to facilitate future fabric expansion, use Layer 3 networking in a single-fabric

network. This section takes the deployment of a management network with Layer 3 networking in a

multi-fabric scenario as an example. The typical network diagram is shown in Figure 1.

Note: To perform automatic underlay network deployment, make sure the IP version of the

management network is the same as that of the underlay network (IPv4 or IPv6). #

4

Figure 1 Management network diagram

Configuration example

In a multi-fabric network, the interfaces that connect the management switch to the devices in

different fabrics must belong to different VLANs. As shown in Figure 1, the interface connected to

the controller management network belongs to VLAN 10, the one connected to Fabric 1 device

management network belongs to VLAN 20, and the one connected to Fabric 2 device management

network belongs to VLAN 30. In addition, you must configure the gateway address of the physical

management network corresponding to the fabric under the VLAN interfaces.

Perform the following tasks on the management switch:

1. Create the VLANs for the controller management network, Fabric 1 device management

network, and Fabric 2 device management network. In this example, the VLAN IDs are 10,

20, and 30, respectively.

[device] vlan 10

[device-vlan10] quit

[device] vlan 20

[device-vlan20] quit

[device] vlan 30

[device-vlan30] quit

2. Assign the interfaces that connect the management switch to the devices in Fabric 1 to VLAN

20. This section uses the interface Ten-GigabitEthernet 1/0/33 as an example.

[device] interface Ten-GigabitEthernet1/0/33

[device-Ten-GigabitEthernet1/0/33] port link-mode bridge

Related components

Management switch

DHCP Relay

VLAN 10

Border1 Border2

Leaf1 Leaf2 Leaf3 Leaf4

Server1 Server2

IPL

IPL IPL

Spine1 Spine2

Fabric1

Border1 Border2

Leaf3 Leaf4Leaf1 Leaf2

Server3 Server4

IPL

IPL IPL

Spine1 Spine2

Fabric2

VLAN 20 VLAN 30

Server3 Server4 Server1 Server2

Management network

（VLAN 10）

Management network

（VLAN 20）

Management network

（VLAN 30）

Management network link description

L3 Network

IMC Orchestrator

5

[device-Ten-GigabitEthernet1/0/33] port access vlan 20

[device-Ten-GigabitEthernet1/0/33] quit

3. Assign the interfaces that connect the management switch to the devices in Fabric 2 to VLAN

30. This section uses the interface Ten-GigabitEthernet1/0/26 as an example.

[device] interface Ten-GigabitEthernet1/0/26

[device-Ten-GigabitEthernet1/0/26] port link-mode bridge

[device-Ten-GigabitEthernet1/0/26] port access vlan 30

[device-Ten-GigabitEthernet1/0/26] quit

4. Configure the VLAN interface of the controller management network.

[device] interface Vlan-interface10

[device-Vlan-interface10] ip address 192.168.12.1 255.255.0.0

[device-Vlan-interface10] quit

5. Configure the VLAN interface of the Fabric1 management network. Configure the DHCP relay

agent, and specify the controller cluster IP address as the relay server IP address.

[device] interface Vlan-interface20

[device-Vlan-interface20] ip address 192.168.11.1 255.255.255.0

[device-Vlan-interface20] dhcp select relay

[device-Vlan-interface20] dhcp relay server-address 192.168.12.101

[device-Vlan-interface20] quit

6. Configure the VLAN interface of the Fabric 2 management network. Configure the DHCP

relay agent, and specify the controller cluster IP address as the relay server IP address.

[device] interface Vlan-interface30

[device-Vlan-interface30] ip address 192.168.21.1 255.255.255.0

[device-Vlan-interface30] dhcp select relay

[device-Vlan-interface30] dhcp relay server-address 192.168.12.101

[device-Vlan-interface30] quit

6

Manual underlay network deployment

Network plan

Network plan for spine-border integration scenario

In this scenario, the spine and border are integrated as one device, and the two spine-border devices

form a DR system, as shown in Figure 2.

Figure 2 Network diagram for underlay spine-border integration scenario

Table 1 IP address and interface description for spine-border integration scenario

Device

IP address planning

Interfaces

Spine Border 1

Management IP address: 192.168.11.2/24

Gateway: 192.168.11.1

HGE 4/0/1 (connecting to HGE 4/0/1 on

Spine Border 2)

HGE 4/0/2 (connecting to HGE 4/0/2 on

Spine Border 2)

XGE 6/0/48 (connecting to XGE 6/0/48

on Spine Border 2)

VTEP address: 10.1.1.2/32

DRNI virtual address: 10.20.1.2/32

DRNI system MAC address: 0002-0003-

Internet

Spine-

Border1 Spine-

Border2

Server-

Leaf1 Server-

Leaf2 Service-

Leaf1 Service-

Leaf2

Server1 Server2 FW3 FW4

FW1 FW2 LB1 LB2

IPL

IPL IPL

Primary

Backup

Related components

IMC Orchestrator

7

0001 (or use the bridge MAC of the device)

XGE 6/0/1 (connecting to XGE 1/2/0 on

FW 1)

XGE 6/0/2 (connecting to XGE 1/2/0 on

FW 2)

XGE 6/0/3 (connecting to XGE 1/2/0 on

LB 1)

XGE 6/0/4 (connecting to XGE 1/2/0 on

LB 2)

XGE 6/0/5 (connecting to external

network device)

HGE 1/0/5 (connecting to HGE 1/0/25 on

Server Leaf 1)

HGE 1/0/6 (connecting to HGE 1/0/25 on

Server Leaf 2)

HGE 1/0/7 (connecting to HGE 1/0/27 on

Service Leaf 1)

HGE 1/0/8 (connecting to HGE 1/0/27 on

Service Leaf 2)

DRNI MAD address: 10.10.1.1/30

DRNI IPL escape address: 10.30.1.1/30

Spine Border 2

Management IP address: 192.168.11.3/24

Gateway: 192.168.11.1

HGE 4/0/1 (connecting to HGE 4/0/1 on

Spine Border 1)

HGE 4/0/2 (connecting to HGE 4/0/2 on

Spine Border 1)

XGE 6/0/48 (connecting to XGE 6/0/48

on Spine Border 1)

XGE 6/0/1 (connecting to XGE 1/2/1 on

FW 1)

XGE 6/0/2 (connecting to XGE 1/2/1 on

FW 2)

XGE 6/0/3 (connecting to XGE 1/2/1 on

LB 1)

XGE 6/0/4 (connecting to XGE 1/2/1 on

LB 2)

XGE 6/0/5 (connecting to external

network device)

HGE 1/0/5 (connecting to HGE 1/0/27 on

Server Leaf 1)

HGE 1/0/6 (connecting to HGE 1/0/27 on

VTEP address: 10.1.1.3/32

DRNI virtual address: 10.20.1.2/32

DRNI system MAC address: 0002-0003-

0001 (or use the bridge MAC of the device)

DRNI MAD address: 10.10.1.2/30

DRNI IPL escape address: 10.30.1.2/30

8

Server Leaf 2)

HGE 1/0/7 (connecting to HGE 1/0/25 on

Service Leaf 1)

HGE 1/0/8 (connecting to HGE 1/0/25 on

Service Leaf 2)

Server Leaf 1

Management IP address: 192.168.11.4/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Server Leaf 2)

XGE 1/0/10 (connecting to XGE 1/0/10

on Server Leaf 2)

XGE 1/0/11 (connecting to Server 1)

XGE 1/0/12 (connecting to Server 2)

HGE 1/0/30 (connecting to HGE 1/0/30

on Server Leaf 2)

HGE 1/0/25 (connecting to HGE 1/0/5 on

Spine Border 1)

HGE 1/0/27 (connecting to HGE 1/0/5 on

Spine Border 2)

VTEP address: 10.1.1.4/32

DRNI virtual address: 10.20.1.4/32

DRNI system MAC address: 0002-0003-

0002 (or use the bridge MAC of the device)

DRNI MAD address: 10.10.1.5/30

DRNI IPL escape address: 10.30.1.5/30

Server Leaf 2

Management IP address: 192.168.11.5/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Server Leaf 1)

XGE 1/0/10 (connecting to XGE 1/0/10

on Server Leaf 1)

XGE 1/0/11 (connecting to Server 1)

XGE 1/0/12 (connecting to Server 2)

HGE 1/0/30 (connecting to HGE 1/0/30

on Server Leaf 1)

HGE 1/0/25 (connecting to HGE 1/0/6 on

Spine Border 1)

HGE 1/0/27 (connecting to HGE 1/0/6 on

Spine Border 2)

VTEP address: 10.1.1.5/32

DRNI virtual address: 10.20.1.4/32

DRNI system MAC address: 0002-0003-

0002 (or use the bridge MAC of the device)

DRNI MAD address: 10.10.1.6/30

DRNI IPL escape address: 10.30.1.6/30

Service Leaf 1

Management IP address: 192.168.11.6/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Service Leaf 2)

XGE 1/0/10 (connecting to XGE 1/0/10

on Service Leaf 2)

XGE 1/0/11 (connecting to XGE 1/2/0 on

FW 3)

XGE 1/0/12 (connecting to XGE 1/2/0 on

VTEP address: 10.1.1.6/32

DRNI virtual address: 10.20.1.6/32

DRNI system MAC address: 0002-0003-

0003 (or use the bridge MAC of the device)

9

DRNI MAD address: 10.10.1.9/30

FW 4)

HGE 1/0/30 (connecting to HGE 1/0/30

on Service Leaf 2)

HGE 1/0/25 (connecting to HGE 1/0/7 on

Spine Border 1)

HGE 1/0/27 (connecting to HGE 1/0/7 on

Spine Border 2)

DRNI IPL escape address: 10.30.1.9/30

Service Leaf 2

Management IP address: 192.168.11.7/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Service Leaf 1)

XGE 1/0/10 (connecting to XGE 1/0/10

on Service Leaf 1)

XGE 1/0/11 (connecting to XGE 1/2/1 on

FW 3)

XGE 1/0/12 (connecting to XGE 1/2/1 on

FW 4)

HGE 1/0/30 (connecting to HGE 1/0/30

on Service Leaf 1)

HGE 1/0/25 (connecting to HGE 1/0/8 on

Spine Border 1)

HGE 1/0/27 (connecting to HGE 1/0/8 on

Spine Border 2)

VTEP address: 10.1.1.7/32

DRNI virtual address: 10.20.1.6/32

DRNI system MAC address: 0002-0003-

0003 (or use the bridge MAC of this

device)

DRNI MAD address: 10.10.1.10/30

DRNI IPL escape address: 10.30.1.10/30

10

Network plan for spine-border separation scenario

Figure 3 Network diagram for underlay spine-border separation scenario

Table 2 IP address and interface description for spine-border separation scenario

Device

IP address planning

Interfaces

Border 1

Management IP address: 192.168.11.8/24

Gateway: 192.168.11.1

HGE 4/0/1 (connecting to HGE 4/0/1

on Border 2)

HGE 4/0/2 (connecting to HGE 4/0/2

on Border 2)

XGE 6/0/48 (connecting to XGE 6/0/48

on Border 2)

HGE 4/0/3 (connecting to HGE 1/0/3

on Spine 1)

HGE 4/0/4 (connecting to HGE 1/0/3

on Spine 2)

XGE 6/0/1 (connecting to XGE 1/2/0 on

FW 1)

XGE 6/0/2 (connecting to XGE 1/2/0 on

FW 2)

VTEP address: 10.1.1.8/32

DRNI virtual address: 10.20.1.8/32

DRNI system MAC address: 0002-0003-

0004 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.13/30

DRNI IPL escape address: 10.30.1.13/30

Internet

Spine-

Border1 Spine-

Border2

Server-

Leaf1 Server-

Leaf2 Service-

Leaf1 Service-

Leaf2

Server1 Server2 FW3 FW4

FW1 FW2 LB1 LB2

IPL

IPL IPL

Primary

Backup

Related components

IMC Orchestrator

11

XGE 6/0/3 (connecting to XGE 1/2/0 on

LB 1)

XGE 6/0/4 (connecting to XGE 1/2/0 on

LB 2)

XGE 6/0/5 (connecting to external

network device)

Border 2

Management IP address: 192.168.11.9/24

Gateway: 192.168.11.1

HGE 4/0/1 (connecting to HGE 4/0/1

on Border 1)

HGE 4/0/2 (connecting to HGE 4/0/2

on Border 1)

XGE 6/0/48 (connecting to XGE 6/0/48

on Border 1)

HGE 4/0/3 (connecting to HGE 1/0/4

on Spine 1)

HGE 4/0/4 (connecting to HGE 1/0/4

on Spine 2)

XGE 6/0/1 (connecting to XGE 1/2/1 on

FW 1)

XGE 6/0/2 (connecting to XGE 1/2/1 on

FW 2)

XGE 6/0/3 (connecting to XGE 1/2/1 on

LB 1)

XGE 6/0/4 (connecting to XGE 1/2/1 on

LB 2)

XGE 6/0/5 (connecting to external

network device)

VTEP address: 10.1.1.9/32

DRNI virtual address: 10.20.1.8/32

DRNI system MAC address: 0002-0003-

0004 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.14/30

DRNI IPL escape address: 10.30.1.14/30

Spine 1

Management IP address: 192.168.11.2/24

Gateway: 192.168.11.1

HGE 1/0/3 (connecting to HGE 4/0/3

on Border 1)

HGE 1/0/4 (connecting to HGE 4/0/3

on Border 2)

HGE 1/0/5 (connecting to HGE 1/0/25

on Leaf 1)

HGE 1/0/6 (connecting to HGE 1/0/25

on Leaf 2)

HGE 1/0/7 (connecting to HGE 1/0/27

on Leaf 3)

HGE 1/0/8 (connecting to HGE 1/0/27

VTEP address: 10.1.1.2/32

12

on Leaf 4)

Spine 2

Management IP address: 192.168.11.3/24

Gateway: 192.168.11.1

HGE 1/0/3 (connecting to HGE 4/0/4

on Border 1)

HGE 1/0/4 (connecting to HGE 4/0/4

on Border 2)

HGE 1/0/5 (connecting to HGE 1/0/27

on Leaf 1)

HGE 1/0/6 (connecting to HGE 1/0/27

on Leaf 2)

HGE 1/0/7 (connecting to HGE 1/0/25

on Leaf 3)

HGE 1/0/8 (connecting to HGE 1/0/25

on Leaf 4)

VTEP address: 10.1.1.3/32

Server Leaf 1

Management IP address: 192.168.11.4/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Server Leaf 2)

XGE 1/0/10 (connecting to XGE 1/0/10

on Server Leaf 2)

XGE 1/0/11 (connecting to Server 1)

XGE 1/0/12 (connecting to Server 2)

HGE 1/0/30 (connecting to HGE 1/0/30

on Server Leaf 2)

HGE 1/0/25 (connecting to HGE 1/0/5

on Spine 1)

HGE 1/0/27 (connecting to HGE 1/0/5

on Spine 2)

VTEP address: 10.1.1.4/32

DRNI virtual address: 10.20.1.4/32

DRNI system MAC address: 0002-0003-

0002 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.5/30

DRNI IPL escape address: 10.30.1.5/30

Server Leaf 2

Management IP address: 192.168.11.5/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Server Leaf 1)

XGE 1/0/10 (connecting to XGE 1/0/10

on Server Leaf 1)

XGE 1/0/11 (connecting to Server 1)

XGE 1/0/12 (connecting to Server 2)

HGE 1/0/30 (connecting to HGE 1/0/30

on Server Leaf 1)

HGE 1/0/25 (connecting to HGE 1/0/6

on Spine 1)

HGE 1/0/27 (connecting to HGE 1/0/6

on Spine 2)

VTEP address: 10.1.1.5/32

DRNI virtual address: 10.20.1.4/32

DRNI system MAC address: 0002-0003-

0002 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.6/30

DRNI IPL escape address: 10.30.1.6/30

13

Service Leaf 1

Management IP address: 192.168.11.6/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Service Leaf 2)

XGE 1/0/10 (connecting to XGE 1/0/10

on Service Leaf 2)

XGE 1/0/11 (connecting to XGE 1/2/1

on FW 3)

XGE 1/0/12 (connecting to XGE 1/2/1

on FW 4)

HGE 1/0/30 (connecting to HGE 1/0/30

on Service Leaf 2)

HGE 1/0/25 (connecting to HGE 1/0/7

on Spine 1)

HGE 1/0/27 (connecting to HGE 1/0/7

on Spine 2)

VTEP address: 10.1.1.6/32

DRNI virtual address: 10.20.1.6/32

DRNI system MAC address: 0002-0003-

0003 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.9/30

DRNI IPL escape address: 10.30.1.9/30

Service Leaf 2

Management IP address: 192.168.11.7/24

Gateway: 192.168.11.1

XGE 1/0/9 (connecting to XGE 1/0/9 on

Service Leaf 1)

XGE 1/0/10 (connecting to XGE 1/0/10

on Service Leaf 1)

XGE 1/0/11 (connecting to XGE 1/2/1

on FW 3)

XGE 1/0/12 (connecting to XGE 1/2/1

on FW 4)

HGE 1/0/30 (connecting to HGE 1/0/30

on Service Leaf 1)

HGE 1/0/25 (connecting to HGE 1/0/8

on Spine 1)

HGE 1/0/27 (connecting to HGE 1/0/8

on Spine 2)

VTEP address: 10.1.1.7/32

DRNI virtual address: 10.20.1.6/32

DRNI system MAC address: 0002-0003-

0003 (or use the bridge MAC of this device)

DRNI MAD address: 10.10.1.10/30

DRNI IPL escape address: 10.30.1.10/30

14

Deployment workflow

Deployment workflow for spine-border integration scenario

Spine border deployment workflow

Figure 4 Spine border deployment workflow

Integration scenario

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure the

underlay routing

protocol

Configure the VTEP

address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Service leaf

Configure the

interface connected

to the spine

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Configure the DR

interface

connected to the

FW device 4 LACP

aggregate link

Configure the DR

interface

connected to the

FW device 3 LACP

aggregate link

Incorporation by

controller

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

Configure the DR

interface connected

to Server 1 LACP

aggregate link

Configure the

physical interface

connected to

Server 2 primary

and secondary

links

Incorporation by

controller

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure the

interface connected

to the spine

Configure the

underlay routing

protocol

Configure the VTEP

address

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Server leaf

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure interfaces

connected to the

leaf

Configure the

underlay routing

protocol

Configure the VTEP

address

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Configure the DR

interface connected

to LB

Configure the DR

interface connected

to FW

Configure the DR

interface connected

to the external

LACP aggregate link

Incorporation by

controller

Spine border

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

15

Server leaf deployment workflow

Figure 5 Server leaf deployment workflow

Integration scenario

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure the

underlay routing

protocol

Configure the VTEP

address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Service leaf

Configure the

interface connected

to the spine

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Configure the DR

interface

connected to the

FW device 4 LACP

aggregate link

Configure the DR

interface

connected to the

FW device 3 LACP

aggregate link

Incorporation by

controller

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

Configure the DR

interface connected

to Server 1 LACP

aggregate link

Configure the

physical interface

connected to

Server 2 primary

and secondary

links

Incorporation by

controller

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure the

interface connected

to the spine

Configure the

underlay routing

protocol

Configure the VTEP

address

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Server leaf

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

Underlay basic

settings

Start DRNI configuration DR interface

configuration

Reboot the device

without a startup

configuration file

Configure hardware

resource

parameters

Configure the

management

network

Configure basic

settings for L2VPN

and VXLAN

Configure interfaces

connected to the

leaf

Configure the

underlay routing

protocol

Configure the VTEP

address

Enable the OVSDB

VTEP service

Configure the

overlay BGP

Configure the global

MAC address

Configure the DRNI

physical address

End

Configure the DRNI

virtual address

Configure DRNI

system parameters

Configure the DRNI

IPP aggregate

interface

Configure DRNI

MAD

Configure the IPL

escape channel

Configure the IPL

bypass channel

Configure VXLAN

default

decapsulation

Configure the DR

interface connected

to LB

Configure the DR

interface connected

to FW

Configure the DR

interface connected

to the external

LACP aggregate link

Incorporation by

controller

Spine border

Mandatory main process

Optional main process

Mandatory subprocess

Optional subprocesses

Page is loading ...

Aruba JL849AAE Configuration Guide

This manual is also suitable for

Aruba JL849AAE Configuration Guide

Related papers

Other documents