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.
|
|