Aruba JL852AAE Configuration Guide

HPE IMC Orchestrator 6.3

Service Configuration Guide in Non-Cloud

Scenarios

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

i 
Contents 
Overview ························································································1 
Configure basic controller settings ·······················································1 
Log in to the controller··················································································································· 2 
Add a fabric ································································································································ 2 
Configure a VDS ·························································································································· 3 
Configure global parameters ·········································································································· 4 
Add a device group ······················································································································ 5 
Configure VLAN-VXLAN mapping ··································································································· 6 
Add a tenant ······························································································································· 8 
Add a border gateway ··················································································································· 8 
Bind the border gateway to the tenant ······························································································ 9 
Configure direct egresses ································································ 10 
Configure a direct egress in static route mode ················································································· 10 
Network planning ················································································································ 10 
Deployment workflow ··········································································································· 13 
Procedure ·························································································································· 13 
Verify the configuration ········································································································· 20 
Configure a BGP direct egress ····································································································· 21 
Network planning ················································································································ 21 
Deployment workflow ··········································································································· 25 
Procedure ·························································································································· 25 
Verify the configuration ········································································································· 34 
Configure an OSPF direct egress (DRNI interface) to the external network ··········································· 44 
Network planning ················································································································ 44 
Deployment workflow ··········································································································· 48 
Procedure ·························································································································· 48 
Verify the configuration ········································································································· 73 
Configure an OSPF direct egress (non-DRNI interface) to the external network ····································· 73 
Network planning ················································································································ 73 
Deployment workflow ··········································································································· 76 
Procedure ·························································································································· 76 
Configure an OSPF direct egress to the internal network ··································································· 90 
Network planning ················································································································ 90 
Deployment workflow ··········································································································· 94 
Procedure ·························································································································· 94 
Verify the configuration ······································································································· 117 
Configure a BGP direct egress to a directly connected external network ············································· 118 
Network planning ·············································································································· 118 
Deployment workflow ········································································································· 121 
Procedure ························································································································ 121 
Configure a direct egress (static route) to a directly connected external network ·································· 135 
Network planning ·············································································································· 135 
Deployment workflow ········································································································· 139 
Procedure ························································································································ 139 
Verify the configuration ······································································································· 154 
Configure the service chain ···························································· 156 
Configure a third-party FW service chain ······················································································ 156 
Network planning ·············································································································· 156 
Deployment workflow ········································································································· 158 
Procedure ························································································································ 158 
Verify the configuration ······································································································· 162 
Configure a third-party LB service chain ······················································································· 163 
Network planning ·············································································································· 163 
Deployment workflow ········································································································· 165 

ii 
Procedure ························································································································ 165 
Verify the configuration ······································································································· 171 
Configure the EPG denylist and allowlist ··········································· 172 
Network planning ····················································································································· 173 
Network topology ·············································································································· 173 
Resource plan ·················································································································· 175 
Deployment flow ······················································································································ 176 
EPG allowlist deployment flow ····························································································· 176 
EPG denylist deployment flow ····························································································· 177 
Procedure ······························································································································· 177 
Configure the basic environment of the controller ···································································· 177 
Add an EPG allowlist ········································································································· 188 
Add an EPG denylist ·········································································································· 199 
Configure the EPG service chain for third-party devices ······················· 211 
Network planning ····················································································································· 211 
Network topology ·············································································································· 211 
Resource plan ·················································································································· 212 
Deployment workflow ················································································································ 213 
Procedure ······························································································································· 213 
Configure the basic environment ·························································································· 213 
Configure an IPv4 EPG service chain ···················································································· 216 
Configure an IPv6 EPG service chain ···················································································· 222 
Configure the controller connected to non-cloud VMware platforms ········ 229 
Network planning ····················································································································· 229 
Network topology ·············································································································· 229 
Resource plan ·················································································································· 231 
Deployment workflow ················································································································ 231 
Procedure ······························································································································· 232 
Configure basic settings of the underlay network ····································································· 232 
Configure basic controller settings ························································································ 232 
Configure the tenant overlay network ···················································································· 232 
Manage the vCenter and configure basic settings of vCenter ····················································· 234 
Add a VDS ······················································································································· 236 
Add hosts to the vCenter ···································································································· 238 
Add a distributed port group and bring a VM online based on the VLAN-VXLAN mapping ··············· 242 
Add a distributed port group and bring a VM online based on automatic VLAN allocation and bound 
interface availability zone ···································································································· 254 
Add a distributed port group and bring a VM online based on manual VLAN allocation and bound interface 
availability zone ················································································································ 257 
Add a distributed port group and bring a VM online based on manual VLAN trunk allocation and bound 
interface availability zone ···································································································· 259 
Add a distributed port group and bring VMs online in a hierarchical manner·································· 261 
Add a distributed port group and bring VMs online in a hierarchical manner (PVLAN) ····················· 263 
Verify the configuration ······································································································· 267 
Migrate a VM ···················································································································· 268 
Audit and synchronization ··································································································· 268 
Pull inventory ···················································································································· 270 
Configure the controller connected to RHVM ······································ 274 
Network planning ····················································································································· 274 
Network topology ·············································································································· 274 
Resource plan ·················································································································· 276 
Deployment workflow ················································································································ 277 
Procedure ······························································································································· 277 
Configure basic settings of the underlay network ····································································· 277 
Configure basic controller settings ························································································ 277 
Configure the tenant overlay network ···················································································· 278 
Connect to the RHVM ········································································································ 282 
Add a logical network ········································································································· 283 

iii 
Bring VMs online and ping between VMs ··············································································· 285 
Pull inventory ···················································································································· 290 
Audit and synchronization ··································································································· 291 
Configure the controller connected to Microsoft System Center ·············· 295 
Network planning ····················································································································· 295 
Network topology ·············································································································· 295 
Resource plan ·················································································································· 296 
Deployment workflow ················································································································ 297 
Procedure ······························································································································· 297 
Configure basic settings of the underlay network ····································································· 297 
Configure basic controller settings ························································································ 297 
Configure the tenant overlay network ···················································································· 298 
Connect to the System Center ····························································································· 302 
Add a logical switch ··········································································································· 308 
Add a VM network ············································································································· 311 
Onboard VMs and verify connectivity between VMs ································································· 315 
Audit and synchronization ··································································································· 323 
Configure EVPN multicast ······························································ 327 
Network planning ····················································································································· 327 
Network topology ·············································································································· 327 
Resource plan ·················································································································· 329 
Deployment workflow ················································································································ 330 
Procedure ······························································································································· 330 
Configure basic settings of the underlay network ····································································· 330 
Configure basic controller settings ························································································ 330 
Intra-VPN Layer 2 multicast in a DC ······················································································ 332 
Configure a vRouter link ································································ 337 
Distributed vRouter link ············································································································· 337 
Network planning ·············································································································· 337 
Deployment workflow ········································································································· 340 
Procedure ························································································································ 340 
Verify the configuration ······································································································· 344 
Centralized vRouter link ············································································································ 347 
Network planning ·············································································································· 347 
Deployment workflow ········································································································· 352 
Procedure ························································································································ 352 
Verify the configuration ······································································································· 361 
Configure the remote leaf ······························································· 363 
Network planning ····················································································································· 363 
Network topology ·············································································································· 363 
Resource plan ·················································································································· 365 
Deployment workflow ················································································································ 366 
Procedure ······························································································································· 366 
Configure the network for communication between the central DC and remote DC ························ 366 
Implement automatic deployment of the remote underlay network ·············································· 369 
Deploy the remote leaf overlay service ·················································································· 377 
Deploy multiple primary/backup egresses for the remote leaf (extended external network) ·············· 381 
Verify the configuration ······································································································· 382 
Monitoring ······················································································0 
FAQ ······························································································0 
 

1

Overview

In non-cloud scenarios, cloud platforms such as OpenStack are unavailable, and a controller acts as

the network, computing, and security configuration entry to implement network management and

service orchestration.

In the IMC Orchestrator solution, a controller supports multi-fabric management. A fabric network

adopts the Spine-Leaf or Spine-Aggregation-Leaf structure.

Figure 1 shows the typical networking in a non-cloud scenario. When a spine device is connected to

leaf devices, the spine device forwards data on the underlay network between the leaf devices.

Server leaf devices are connected to computing devices such as servers, VMware VMs, RedHat

VMs, and Kubernetes containers. Service leaf devices are connected to third-party devices.

Figure 1 Typical networking in a non-cloud scenario

Fabric ED devices implement Layer 2/Layer 3 interconnection between fabrics. DCI ED devices

implement Layer 2/Layer 3 interconnection between data centers (DCs).

Border devices are connected to external devices to realize communication between the internal and

external networks. Third-party devices are connected to the border devices in hairpin mode to

enable internal network devices to access the external network through the security devices.

The leaf devices, ED devices, and border devices adopt the DRNI mode for networking. Spine

devices use more nodes for networking, and spine border devices adopt DRNI for networking.

Configure basic controller settings

This chapter describes only the general operation steps for configuring basic controller settings. For

the specific configuration content and data, see "Configure basic controller settings" in each

scenario.

Internet

Border1 Border2

Server-

Leaf1 Server-

Leaf2 Service-

Leaf1 Service-

Leaf2

Server1 Server2

peer-link

peer-link peer-link

Spine1 Spine2 Fabric ED1

Fabric1

Internet

Border1 Border2

Server-

Leaf1 Server-

Leaf2 Service-

Leaf1 Service-

Leaf2

Server1 Server2

peer-link

peer-link peer-link

Spine1 Spine2

Fabric2

Fabric ED2

DCI ED

Other DC

Third-party FW Third-party FW

2

Log in to the controller

After the controller is deployed, the corresponding menu items are loaded in IMC PLAT, and you can

use the controller functions by logging in to IMC PLAT.

IMC PLAT provides a user-friendly GUI. The login method is as follows:

1. Enter http://ip_address:30000/central/index.html in the address bar of the browser, and

press Enter to open the login page as shown in Figure 2.

 Ip_address is the virtual IP address of the cluster northbound service of the Installer where

IMC PLAT is located.

 30000 is the port number.

Figure 2 IMC PLAT login page

Add a fabric

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Fabrics > Fabrics. Click Add. On the

page for adding a fabric, configure the fabric parameters:

 Name: fabric1

 AS number: 100. It is mandatory, and must be the same as the BGP AS number of each

device in the fabric.

 Multicast network: Off (default). If multicast is used, set this parameter to On.

 Epg controller: Off (default). If End Point Group (EPG) is used, set this parameter to On.

 Configure other parameters based on the networking requirements. The default

configuration is used as an example here.

3

Figure 3 Adding a fabric

2. Click OK to create the fabric.

3. Click the icon in the Actions column, and then click the Settings tab to open the fabric

settings page. On this page, complete the advanced configuration of the fabric based on the

actual networking requirements. To reduce packet flood on the network, you are advised to

select Unknown Unicast Suppression, Unknown Multicast Suppression, and Broadcast

Suppression. For other parameters, the default configuration is used as an example here.

Figure 4 Advanced settings of the fabric

Configure a VDS

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Common Network Settings > Virtual

Distributed Switches. Click the Modify icon in the Actions column, and modify VDS 1 by

adding the created fabric fabric1 on the Carrier Fabric tab.

4

Figure 5 Adding a fabric for the VDS

2. Click the Advanced Settings tab, and configure the following parameters of VDS 1:

 Bridge name: vds1-br

 VXLAN tunnel interface name: vxlan_vds1-br

 vSwitch Learned Flow Entries Aging Time (seconds): 300

 Configure other parameters based on the networking requirements. The default

configuration is used as an example here.

Figure 6 Advanced settings

3. Click Apply to save the settings.

Configure global parameters

1. To ensure the normal use of IPv6 services (if any), enable the global IPv6 configuration on the

controller as follows:

a. Navigate to Automation > Data Center Networks > Fabrics > Parameters, and click the

Controller Global Settings tab.

b. Set IPv6 to On.

2. To reduce ACL resource occupation by switches, disable Deploy Security Policy Flow Table

to Switching Devices as follows:

a. Navigate to Automation > Data Center Networks > Fabrics > Parameters, and click the

Controller Global Settings tab.

b. Set Deploy Security Policy Flow Table to Switching Devices to Off.

5

3. If it is required to generate the VRF names according to rules, select the VRF autonaming mode

in the controller as follows:

a. Navigate to Automation > Data Center Networks > Fabrics > Parameters, and click the

Controller Global Settings tab.

b. Set VRF Autonaming Mode to Rule-based. The generated VRF name is in the following

format: Tenant name_Router name_Segment ID.

Figure 7 Controller global settings

Add a device group

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Fabrics > Fabrics, click the icon in

the Actions column for fabric1, and click the Device group tab.

2. Click Add to go to the page for adding a device group, and configure the following parameters

in the Basic Info area:

 Device Group Name: Custom name of the device group.

 Remote Device Group: Specify whether the device group is remote. Once configured, this

parameter cannot be modified. Therefore, you must plan this parameter.

 Position: Network position of the device group. You can select multiple positions. Once

configured, this parameter cannot be modified. Therefore, you must plan this parameter.

 HA Mode: Specify the deployment mode.

3. In the Border Gateway Settings area, configure the following parameters:

 Third-Party Firewall: Off. Configure this parameter based on the networking requirements.

 Firewall Deployment Mode: Inline. Configure this parameter based on the networking

requirements.

 Connection Mode: Specify the mode of connection between the border device and service

device. Once configured, this parameter cannot be modified. Therefore, you must plan this

parameter.

 IPAddress Pool List: Configure this parameter based on the networking requirements.

 VLAN Pool List: Configure this parameter based on the networking requirements.

6

Figure 8 Adding a device group

4. Add the border device in the Device Group Members area.

5. Click Apply in the upper right corner to add the device group.

6. If you use the automatic deployment mode to configure the underlay network, the controller

automatically performs DRNI deployment on the two member devices of the added device

group. To manually add the DR interface configuration on the controller, see IMC Orchestrator

6.3 Solution Underlay Network Configuration Guide.

Configure VLAN-VXLAN mapping

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Resource Pools > VNID Pools >

VLAN-VXLAN Mappings. Click Add, select VLAN-VXLAN Mapping to go to the Add

VLAN-VXLAN Mapping page, and perform the following operations:

a. Enter the mapping name map1.

Figure 9 VLAN-VXLAN mapping settings

b. Click Add Mapping, and configure the following parameters in the dialog box that opens:

− Name: map001

− Start VLAN ID: 2001

7

− Start VXLAN ID: 2001

− Mapping Range Length: 4

− Access Mode: VLAN

Figure 10 Adding a VLAN-VXLAN mapping

c. Click Apply.

2. On the Apply to Device or Apply to Interface tab, apply the mapping to a device or an

interface. For example, to apply the mapping to an interface:

a. Select map1 on the VLAN-VXLAN mapping page.

b. Click Interface in the Apply to Interfaces area to go to the Apply to Interfaces page.

3. Select a device from the device list. Select an access interface (or an aggregate interface) of

the device, and add the selected interface to the selected interface list on the right. Click Apply.

NOTE:

For devices onboarded in manual mode, you need to click Add VTEPs to add the downlink

aggregate interfaces of the devices to the available interfaces list. For devices onboarded

automatically, the controller can automatically obtain the aggregate interfaces. In this example,

the automated device onboarding mode is used.

Figure 11 Selecting an interface

4. View the created mapping in the list.

8

Figure 12 Mapping information

Add a tenant

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Tenant Management > All Tenants.

Click Add, and configure the following parameters on the Add Tenant page:

 Tenant Name: Custom tenant name, for example, tenant1

 VDS Name: VDS1

Figure 13 Adding a tenant

2. Click Apply.

Add a border gateway

This chapter describes only the configuration example. For the specific configuration content and

data, see "Configure basic controller settings" in each scenario.

1. Navigate to Automation > Data Center Networks > Common Network Settings > Border

Gateway. Click Add, and configure the following parameters on the Add Border Gateway

page:

 Name: Custom border gateway name, for example, gw1.

 Gateway Sharing: Off. Configure this parameter based on the networking requirements.

 Gateway Type: Composite gateway. Configure this parameter based on the networking

requirements.

9

 Configure other parameters based on the networking requirements. The default

configuration is used as an example here.

Figure 14 Adding a border gateway

2. Click Add Border Gateway Members, and configure the following parameters on the Add

Border Gateway Members page:

 Name: Custom name of the border gateway member, for example, gw1member.

 Fabric: fabric1.

 Device Group: bdgroup1. Select the device group created for the fabric.

 Priority: 1. Set this parameter to a value between 0 and 99 based on the networking

requirements. A larger number indicates a higher priority.

3. Click Apply to add a border gateway member. Click Apply on the Add Border Gateway page

to add a border gateway.

Bind the border gateway to the tenant

1. Navigate to Automation > Data Center Networks > Tenant Management > All Tenants,

select tenant1, and click to open the Edit Tenant page.

Figure 15 Adding a gateway resource

10

2. Click Add in the Allocate Gateway Resources area. In the dialog box that opens, select the

border gateway, and click Apply to add the border gateway.

Figure 16 Binding the border gateway to the tenant

3. Click Apply.

Configure direct egresses

Configure a direct egress in static route mode

Network planning

Network topology

For more information about connections between switches, see IMC Orchestrator 6.3 Underlay

Network Configuration Guide.

11

Figure 17 Network diagram for the direct egress in static route mode

Table 1 IP addresses and interfaces

Device

Function

Management

IP address

Service IP address and interface

Border1

EVPN border

device

192.168.11.8

Loopback0: 10.1.1.8/32

HGE4/0/1 (connecting to HGE4/0/1 on Border2)

HGE4/0/2 (connecting to HGE4/0/2 on Border2)

XGE6/0/48 (connecting to XGE6/0/48 on Border2)

HGE4/0/3 (connecting to HGE1/0/3 on Spine1)

HGE4/0/4 (connecting to HGE1/0/3 on Spine2)

XGE6/0/1 (connecting to external network switch)

Border2

EVPN border

device

192.168.11.9

Loopback0 10.1.1.9/32

HGE4/0/1 (connecting to HGE4/0/1 on Border1)

HGE4/0/2 (connecting to HGE4/0/2 on Border1)

XGE6/0/48 (connecting to XGE6/0/48 on Border1)

HGE4/0/3 (connecting to HGE1/0/4 on Spine1)

HGE4/0/4 (connecting to HGE1/0/4 on Spine2)

XGE6/0/1 (connecting to external network switch)

Spine1

Underlay physical

192.168.11.2

Loopback0 10.1.1.2/32

Border1 Border2

Leaf1 Leaf2

Server1 Server2

Peer link

Spine1 Spine2

Leaf3 Leaf4

Server3 Server4

Peer link

Internet

External network switch

Controller

Related component

12

Device

Function

Management

IP address

Service IP address and interface

device

HGE1/0/3 (connecting to HGE4/0/3 on Border1)

HGE1/0/4 (connecting to HGE4/0/3 on Border2)

HGE1/0/5 (connecting to HGE1/0/25 on Leaf1)

HGE1/0/6 (connecting to HGE1/0/25 on Leaf2)

HGE1/0/7 (connecting to HGE1/0/25 on Leaf3)

HGE1/0/8 (connecting to HGE1/0/25 on Leaf4)

Spine2

Underlay physical

device

192.168.11.3

Loopback0 10.1.1.3/32

HGE1/0/3 (connecting to HGE4/0/4 on Border1)

HGE1/0/4 (connecting to HGE4/0/4 on Border2)

HGE1/0/5 (connecting to HGE1/0/27 on Leaf1)

HGE1/0/6 (connecting to HGE1/0/27 on Leaf2)

HGE1/0/7 (connecting to HGE1/0/27 on Leaf3)

HGE1/0/8 (connecting to HGE1/0/27 on Leaf4)

Leaf1

EVPN access

device

192.168.11.4

Loopback0 10.1.1.4/32

XGE1/0/9 (connecting to XGE1/0/9 on Leaf2)

HGE1/0/29 (connecting to HGE1/0/29 on Leaf2)

HGE1/0/30 (connecting to HGE1/0/30 on Leaf2)

HGE1/0/25 (connecting to HGE1/0/5 on Spine1)

HGE1/0/27 (connecting to HGE1/0/5 on Spine2)

Leaf2

EVPN access

device

192.168.11.5

Loopback0 10.1.1.5/32

XGE1/0/9 (connecting XGE1/0/9 on Leaf1)

HGE1/0/29 (connecting HGE1/0/29 on Leaf1)

HGE1/0/30 (connecting to HGE1/0/30 on Leaf1)

HGE1/0/25 (connecting to HGE1/0/6 on Spine1)

HGE1/0/27 (connecting to HGE1/0/6 on Spine2)

Leaf3

EVPN access

device

192.168.11.6

Loopback0 10.1.1.6/32

XGE1/0/9 (connecting to XGE1/0/9 on Leaf4)

HGE1/0/29 (connecting to HGE1/0/29 on Leaf4)

HGE1/0/30 (connecting to HGE1/0/30 on Leaf4)

HGE1/0/25 (connecting to HGE1/0/7 on Spine1)

HGE1/0/27 (connecting to HGE1/0/7 on Spine2)

Leaf4

EVPN access

device

192.168.11.7

Loopback0 10.1.1.7/32

XGE1/0/9 (connecting to XGE1/0/9 on Leaf3)

HGE1/0/29 (connecting to HGE1/0/29 on Leaf3)

HGE1/0/30 (connecting to HGE1/0/30 on Leaf3)

HGE1/0/25 (connecting to HGE1/0/8 on Spine1)

HGE1/0/27 (connecting to HGE1/0/8 on Spine2)

NOTE:

In this topology, the 12900E Type X Fabric Module switch acts as a spine device or a border device,

and the 5945 switch acts as a leaf device. You can plan other device types (if any) as needed. The

interfaces are for reference only, and you must plan interfaces as needed.

13

Resource plan

Table 2 Resource plan

Planning item

Configuration example

Description

Fabric

• Name: fabric1

• AS number: 100

N/A

VDS

• Name: VDS1

• Carrier fabric: fabric1

• VXLAN ID range: 1 to 16777215

This range must cover

the VXLAN IDs of all

subnets in the VDS.

VXLAN IDs are unique in

the LAN. Different VDSs

must be configured with

different VXLAN IDs.

External network

• Name: extnet1

• IPv4: v4extsubnet1, 100.0.1.0/24

• IPv6: v6extsubnet1,

2001:100:0:1::/64

N/A

Deployment workflow

Figure 18 Deployment workflow

Start End

Mandatory process

Optional process

Mandatory sub-process

Optional sub-process

Configure basic

settings of the

underlay network

Configure basic

controller settings

Add a vNetwork

Add a vRouter

Bind a border

gateway to the

vRouter

Add an external

network

Bind an external

network to the

vRouter

Configure external

network switches

Configure a border

device

Configure tenant

network resources Configure the

external network

Add a fabric

Configure a VDS

Configure global

parameters

Add a border

device group

Add a VLAN-VXLAN

mapping

Add a tenant

Add a border

gateway

Bind the border

gateway to the tenant

Configure a direct egress in static route mode

Procedure

Configure basic settings of the underlay network

Configure switches

14

Configure and manage all switches in the network. For more information, see IMC Orchestrator 6.3

Underlay Network Configuration Guide.

Configure external network switches

The following information takes the device commands as an example. For more information about

commands, see the product manual of the third-party device.

1. Configure the IP address of the VLAN interface interconnected with the border device.

[device] vlan 4001

[device-vlan4001] quit

[device] ip vpn-instance external_vpn_4001

[device-vpn-instance-external_vpn_4001] quit

[device] interface vlan 4001

[device-Vlan-interface4001] ip binding vpn-instance external_vpn_4001

[device-Vlan-interface4001] ip address 100.0.1.1 24

[device-Vlan-interface4001] ipv6 address 2001:100:0:1::1 64

[device-Vlan-interface4001] quit

2. Configure the IP address of the aggregate interface interconnected with the border device.

[device] interface Bridge-Aggregation2

[device-Bridge-Aggregation2] port link-type trunk

[device-Bridge-Aggregation2] undo port trunk permit vlan 1

[device-Bridge-Aggregation2] port trunk permit vlan 4001

[device-Bridge-Aggregation2] link-aggregation mode dynamic

[device-Bridge-Aggregation2] quit

3. Configure a static route. The next hop is the IP address of the egress interface of the external

subnet bound to the vRouter. Assume that the IPv4 address is 100.0.1.2 and the IPv6 address

is 2001:100:0:1::2.

[device] ip route-static vpn-instance external_vpn_4001 11.2.1.0 24 100.0.1.2

[device] ipv6 route-static vpn-instance external_vpn_4001 2001:11:2:1:: 64

2001:100:0:1::2

Configure basic controller settings

Complete the following basic configuration as described in "Configure basic controller settings."

Table 3 Configuring basic controller settings

Configuration item

Configuration example

Description

Add a fabric

• Basic settings

 Name: fabric1

 AS number: 100

• Advanced settings

 Unknown Unicast Suppression:

Selected

 Unknown Multicast Suppression:

Selected

 Broadcast Suppression: Selected

N/A

Configure a VDS

• Name: VDS1

• Carrier fabric: fabric1

• VXLAN ID range: 1 to 16777215

This range must cover the

VXLAN IDs of all subnets in the

VDS. VXLAN IDs are unique in

the LAN. Different VDSs must be

configured with different VXLAN

IDs.

Configure the same VXLAN IDs

Configure global

• IPv6: On

N/A

15

Configuration item

Configuration example

Description

parameters

• Deploy Security Policy Flow Table to

Switching Devices: Off

• VRF Autonaming Mode: Rule-based

Add a device group

• Name: bdgroup1

• Position: Border Gateway

• HA mode: DRNI

• Connection mode: IPs from Different

Networks

• Address pools: Default

• VLAN pools: Default

• Device group members: Border1 and

Border2

Position, Remote Device Group,

Firewall Deployment Mode, and

Connection Mode cannot be

modified after they are

configured. The settings of

Position and Firewall Deployment

Mode affect fabric expansion in

future. Therefore, plan these

parameters properly before

configuration.

Add a VLAN-VXLAN

mapping

• Name: map1

• VLAN-VXLAN mapping:

 Name: map201

 Start VLAN ID: 2005

 Start VXLAN ID: 2005

 Mapping range length: 1

 Access mode: VLAN

• Apply to interfaces: Apply to all

aggregate interfaces that connect the

server-leaf devices to the server in

the network.

N/A

Add a tenant

• Name: tenant1

• VDS name: VDS1

N/A

Add a border gateway

• Name: gw1

• Member name: gw1member

• Fabric: fabric1

• Device group: bdgroup1

• Priority: 1

N/A

Bind the border gateway

to the tenant

• Allocate gateway resource: gw1

N/A

Add a vNetwork

1. Navigate to Automation > Data Center Networks > Tenant [tenant1] Network > Virtual

Network. Click Add, and configure the following parameters on the Add Virtual Network

page:

 Name: network201

 Segment ID: 2005

 Type: VXLAN

 Network Sharing: Off

2. On the Subnets tab, click Add, and configure the following parameters in the dialog box that

opens:

 IP Version: IPv4

 Name: subnetv4-201

 Subnet Address: 11.2.1.0/24

 Gateway IP: 11.2.1.1

3. Click Apply to add an IPv4 subnet.

4. Repeat steps 2 to 3 to add an IPv6 subnet, and configure parameters as follows:

16

 IP Version: IPv6

 Name: subnetv6-201

 Subnet Address: 2001:11:2:1::/64

 Gateway IP: 2001:11:2:1::1

Figure 19 Configuring a vNetwork

5. On the Advanced Configuration tab, configure parameters such as the suppression functions.

In this network, the default configuration is used.

6. Click Apply to add the vNetwork.

Figure 20 Advanced settings

Add a vRouter

1. Navigate to Automation > Data Center Networks > Tenant [tenant1] Network > Virtual

Router. Click Add, and configure the following parameters on the Add Virtual Router page:

 Name: router201

 Segment ID: 11005

2. On the Subnets tab, click Add to add subnets, for example, subnetv4-201 and subnetv6-201,

to the vRouter.

Page is loading ...

Aruba JL852AAE, IMC Orchestrator 6.3 Service, JL849AAE, JL850AAE, JL851AAE, JL853AAE Configuration Guide

Related papers

Other documents