Aruba IMC Orchestrator 6.3 Service Configuration Guide

Category
Networking
Type
Configuration Guide

This manual is also suitable for

HPE IMC Orchestrator 6.3
Service Configuration Guide in Non-Cloud
Scenarios
The information in this document is subject to change without notice.
© Copyright 2023 Hewlett Packard Enterprise Development LP
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
Border1
EVPN border
device
192.168.11.8
Border2
EVPN border
device
192.168.11.9
Spine1
Underlay physical
192.168.11.2
Border1 Border2
Leaf1 Leaf2
Server1 Server2
Peer link
Peer link
Spine1 Spine2
Leaf3 Leaf4
Server3 Server4
Peer link
Internet
External network switch
Controller
Related component
12
Device
Function
Management
IP address
device
Spine2
Underlay physical
device
192.168.11.3
Leaf1
EVPN access
device
192.168.11.4
Leaf2
EVPN access
device
192.168.11.5
Leaf3
EVPN access
device
192.168.11.6
Leaf4
EVPN access
device
192.168.11.7
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 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166
  • Page 167 167
  • Page 168 168
  • Page 169 169
  • Page 170 170
  • Page 171 171
  • Page 172 172
  • Page 173 173
  • Page 174 174
  • Page 175 175
  • Page 176 176
  • Page 177 177
  • Page 178 178
  • Page 179 179
  • Page 180 180
  • Page 181 181
  • Page 182 182
  • Page 183 183
  • Page 184 184
  • Page 185 185
  • Page 186 186
  • Page 187 187
  • Page 188 188
  • Page 189 189
  • Page 190 190
  • Page 191 191
  • Page 192 192
  • Page 193 193
  • Page 194 194
  • Page 195 195
  • Page 196 196
  • Page 197 197
  • Page 198 198
  • Page 199 199
  • Page 200 200
  • Page 201 201
  • Page 202 202
  • Page 203 203
  • Page 204 204
  • Page 205 205
  • Page 206 206
  • Page 207 207
  • Page 208 208
  • Page 209 209
  • Page 210 210
  • Page 211 211
  • Page 212 212
  • Page 213 213
  • Page 214 214
  • Page 215 215
  • Page 216 216
  • Page 217 217
  • Page 218 218
  • Page 219 219
  • Page 220 220
  • Page 221 221
  • Page 222 222
  • Page 223 223
  • Page 224 224
  • Page 225 225
  • Page 226 226
  • Page 227 227
  • Page 228 228
  • Page 229 229
  • Page 230 230
  • Page 231 231
  • Page 232 232
  • Page 233 233
  • Page 234 234
  • Page 235 235
  • Page 236 236
  • Page 237 237
  • Page 238 238
  • Page 239 239
  • Page 240 240
  • Page 241 241
  • Page 242 242
  • Page 243 243
  • Page 244 244
  • Page 245 245
  • Page 246 246
  • Page 247 247
  • Page 248 248
  • Page 249 249
  • Page 250 250
  • Page 251 251
  • Page 252 252
  • Page 253 253
  • Page 254 254
  • Page 255 255
  • Page 256 256
  • Page 257 257
  • Page 258 258
  • Page 259 259
  • Page 260 260
  • Page 261 261
  • Page 262 262
  • Page 263 263
  • Page 264 264
  • Page 265 265
  • Page 266 266
  • Page 267 267
  • Page 268 268
  • Page 269 269
  • Page 270 270
  • Page 271 271
  • Page 272 272
  • Page 273 273
  • Page 274 274
  • Page 275 275
  • Page 276 276
  • Page 277 277
  • Page 278 278
  • Page 279 279
  • Page 280 280
  • Page 281 281
  • Page 282 282
  • Page 283 283
  • Page 284 284
  • Page 285 285
  • Page 286 286
  • Page 287 287
  • Page 288 288
  • Page 289 289
  • Page 290 290
  • Page 291 291
  • Page 292 292
  • Page 293 293
  • Page 294 294
  • Page 295 295
  • Page 296 296
  • Page 297 297
  • Page 298 298
  • Page 299 299
  • Page 300 300
  • Page 301 301
  • Page 302 302
  • Page 303 303
  • Page 304 304
  • Page 305 305
  • Page 306 306
  • Page 307 307
  • Page 308 308
  • Page 309 309
  • Page 310 310
  • Page 311 311
  • Page 312 312
  • Page 313 313
  • Page 314 314
  • Page 315 315
  • Page 316 316
  • Page 317 317
  • Page 318 318
  • Page 319 319
  • Page 320 320
  • Page 321 321
  • Page 322 322
  • Page 323 323
  • Page 324 324
  • Page 325 325
  • Page 326 326
  • Page 327 327
  • Page 328 328
  • Page 329 329
  • Page 330 330
  • Page 331 331
  • Page 332 332
  • Page 333 333
  • Page 334 334
  • Page 335 335
  • Page 336 336
  • Page 337 337
  • Page 338 338
  • Page 339 339
  • Page 340 340
  • Page 341 341
  • Page 342 342
  • Page 343 343
  • Page 344 344
  • Page 345 345
  • Page 346 346
  • Page 347 347
  • Page 348 348
  • Page 349 349
  • Page 350 350
  • Page 351 351
  • Page 352 352
  • Page 353 353
  • Page 354 354
  • Page 355 355
  • Page 356 356
  • Page 357 357
  • Page 358 358
  • Page 359 359
  • Page 360 360
  • Page 361 361
  • Page 362 362
  • Page 363 363
  • Page 364 364
  • Page 365 365
  • Page 366 366
  • Page 367 367
  • Page 368 368
  • Page 369 369
  • Page 370 370
  • Page 371 371
  • Page 372 372
  • Page 373 373
  • Page 374 374
  • Page 375 375
  • Page 376 376
  • Page 377 377
  • Page 378 378
  • Page 379 379
  • Page 380 380
  • Page 381 381
  • Page 382 382
  • Page 383 383
  • Page 384 384
  • Page 385 385
  • Page 386 386
  • Page 387 387
  • Page 388 388

Aruba IMC Orchestrator 6.3 Service Configuration Guide

Category
Networking
Type
Configuration Guide
This manual is also suitable for

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI