HCP System Management Help


Tagged and untagged networks

A tagged network is one that has a specified VLAN ID. The VLAN ID is an identifier that’s attached to each packet routed to HCP over that network. This function is performed by the switches in the physical network.

The routing tables in the switches that route requests to the HCP front end must include each VLAN ID you assign to a network. The routing tables associate the VLAN IDs with the network subnets.

A network carries only the packets that have its VLAN ID and ignores all other packets, thereby segregating the traffic on each tagged network from the traffic on other networks.

An untagged network is one for which you don’t specify a VLAN ID. An untagged network ignores all packets that have VLAN IDs.

HCP can have at most one untagged front-end network, including the [hcp_system] network. All other networks must have a VLAN ID.

An untagged network uses the bond0 front-end network interface. When you assign a VLAN ID to a network, HCP creates a logical network interface for the network. This interface is named bond0.xxxx, where xxxx is the VLAN ID, with leading zeroes added if needed to create a four-digit number.

The figure on the next page shows a configuration in which:

HCP uses the [hcp_system] network with VLAN ID 999 for system-level management purposes

The tenant named Tenant-1 uses a network named t1 with VLAN ID 7 for tenant management purposes and a network named t1-data with VLAN ID 8 for data access purposes

HCP uses a network named replication with VLAN ID 200 for replication traffic

© 2017 Hitachi Vantara Corporation. All rights reserved.