Network Definitions (Layer 2 and 3)

Table 1 is intended to be used as a template for recording your Ultra M network Layer 2 and Layer 3 deployments.

Some of the Layer 2 and 3 networking parameters identified in Table 1 are configured directly on the UCS hardware via CIMC. Other parameters are configured as part of the VIM Orchestrator or VIM configuration. This configuration is done through various configuration files depending on the parameter:

  • undercloud.conf

  • network.yaml

  • layout.yaml

  • AutoDeploy Configuration file for the pod

Table 1. Layer 2 and 3 Network Definition

VLAN ID / Range

Network

Gateway

IP Range Start

IP Range End

Description

Where Configured

Routable?

External-Internet Meant for OSP-D Only

100

192.168.1.0 /24

192.168.1.1

Internet access required:

- 1 IP Address for OSP-D

- 1 IP for default gateway

On Ultra M Manger Node hardware

Yes

External – Floating IP Addresses (Virtio)*

101

192.168.10.0 /24

192.168.10.1

Routable addresses required:

- 3 IP addresses for Controllers

- 1 VIP for master Controller Node (Horizon IP address)

4 Floating IP Addresses per VNF for management VMs (CF, VNFM, UEM, and UAS software modules)

- 1 IP for default gateway

network.yaml and/or layout.yaml**

Yes

Provisioning

105

192.0.0.0/ 8

192.200.0. 100

192.200.0. 254

Required to provision all configuration via PXE boot from OSP-D for Ceph, Controller and Compute. Intel- On-Board Port 1 (1G).

undercloud. conf

No

IPMI-CIMC

105

192.0.0.0/ 8

192.100.0. 100

192.100.0. 254

On UCS servers through CIMC

No

Tenant (Virtio)

17

11.117.0.0/ 24

All Virtio based tenant networks. (MLOM)

network.yaml and/or layout.yaml**

No

Storage (Virtio)

18

11.118.0.0/ 24

Required for Controllers, Computes and Ceph for read/write from and to Ceph. (MLOM)

network.yaml and/or layout.yaml**

No

Storage-MGMT (Virtio)

19

11.119.0.0/ 24

Required for Controllers and Ceph only as Storage Cluster internal network. (MLOM)

network.yaml and/or layout.yaml**

No

Internal-API (Virtio)

20

11.120.0.0/ 24

Required for Controllers and Computes for openstack manageability. (MLOM)

network.yaml and/or layout.yaml**

No

Mgmt (Virtio)

21

172.16.181.0/ 24

172.16.181. 100

172.16.181. 254

Tenant based virtio network on openstack.

network.yaml and/or layout.yaml**

No

Other-Virtio

1001:

1500

Tenant based virtio networks on openstack.

network.yaml and/or layout.yaml**

No

SR-IOV (Phys-PCIe1)

2101:

2500

Tenant SRIOV network on openstack. (Intel NIC on PCIe1)

NOTE: A unique VLAN from this range is used by each VNF for the DI-internal network.

network.yaml and/or layout.yaml**

Yes

SR-IOV (Phys-PCIe4)

2501:

2900

Tenant SRIOV network on openstack. (Intel NIC on PCIe4)

NOTE: Ensure that the same DI-internal nework VLAN ID is configured for both PCIe1 and PCIe4 for the same VNF. (For example, if VLAN ID 2111 is configured for VNF1 on PCIe1, VLAN ID 2111 must be configured on PCIe4 for VNF1)

network.yaml and/or layout.yaml**

Yes

NOTE: Bold underlined text is provided as example configuration information. Your deployment requirements will vary. The IP addresses in bold text are the recommended address used for internal routing between VNF components. All other IP addresses and VLAN IDs may be changed/assigned.

* You can ensure that the same floating IP address can assigned to the AutoVNF, CF, UEM, and VNFM after a VM restart by configuring parameters in the AutoDeploy configuration file or the UWS service delivery configuration file. Refer to Table 2 for details.

** For Hyper-converged Ultra M models based on OpenStack 10, these parameters must configured in the both the networks.yaml and the layout.yaml files unless the VIM installation automation feature is used. Refer to the Ultra Services Platform Deployment Automation Guide for details.

Caution

 
IP address ranges used for the Tenant (Virtio), Storage (Virtio), and Internal-API (Virtio) in network.yaml cannot conflict with the IP addresses specified in layout.yaml for the corresponding networks. Address conflicts will prevent the VNF from functioning properly.
Table 2. Floating IP address Reuse Parameters

Component

Construct

AutoDeploy Configuration File Parameters

UWS Service Deployment Configuration File

AutoVNF

autovnfd

networks management floating-ip true

networks management ha-vip<vip_address>

networks management floating-ip-address <floating_address>

<management>

<---SNIP--->

<floating-ip>true </floating-ip>

<ha-vip> vip_address</ha-vip>

<floating-ip-address> floating_address </floating-ip-address>

</management>

VNFM

vnfmd

floating-ip true

ha-vip <vip_address>

floating-ip-address <floating_address>

<management>

<---SNIP--->

<floating-ip>true </floating-ip>

<ha-vip> vip_address</ha-vip>

<floating-ip-address>floating_address </floating-ip-address>

</management>

UEM

vnfd

vnf-em ha-vip <vip_address>

vnf-em floating-ip true

vnf-em floating-ip-address <floating_address>

<vnf-em>

<---SNIP--->

<ha-vip> vip_address</ha-vip>

<---SNIP--->

<floating-ip>true </floating-ip>

<floating-ip-address> floating_address </floating-ip-address>

<---SNIP--->

</vnf-em>

CF

vnfd

interfaces mgmt

<---SNIP--->

enable-ha-vip <vip_address>

floating-ip true

floating-ip-address <floating_address>

<---SNIP--->

<interfaces>

<---SNIP--->

<enable-ha-vip> vip_address</enable-ha-vip>

<floating-ip>true </floating-ip>

<floating-ip-address> floating_address </floating-ip-address>

<---SNIP--->

</interfaces>

Controllers

networking network-types external

<---SNIP--->

ip-prefix<floating_address_ network >/<mask_bits>

vlan-id <vlan_id>

allocation-pool start<1st_floating_address_for_controllers>

allocation-pool end <4th_floating_address_for_ controllers >

default-route<actual_gw_Ip_ddress of_floating_ip_network>

<---SNIP--->

Note

 

This functionality is disabled by default. Set the floating-ip and/or <floating-ip> parameters to true to enable this functionality.

Note

 

Prior to assigning floating and virtual IP addresses, make sure that they are not already allocated through OpenStack. If the addresses are already allocated, then they must be freed up for use or you must assign a new IP address that is available in the VIM.