Creating network containers
Failed to execute the [bmc-contextid] macro.
A network container is a VLAN that provides network isolation for tenants in the cloud. You must have at least one network container, and if you have multiple tenants, you might want to create a network container for each tenant. See Network-resources-overview for more information.
The configuration of a network container is specified in a network container blueprint. Network container blueprints are created in BMC BladeLogic Network Automation.
You must create at least one network container in BMC Cloud Lifecycle Management.
Before you begin
- BMC BladeLogic Network Automation (BBNA) must be registered as a provider.
- One or more pods, created by the registered BMC BladeLogic Network Automation provider, must exist on the network.
- One or more network blueprints must exist within the registered BMC BladeLogic Network Automation provider.
- One or more network blueprints must have been imported, as described in Importing-network-container-blueprints.
To create a network container
The container will be provisioned on the network by BMC BladeLogic Network Automation using the specified network container blueprint.
You can now:
- Onboard compute resources, as described Onboarding-compute-resources.
- Manage firewalls, as described in Managing-virtual-firewall-rules.
- Manage load balancers, as described in Managing virtual load balancers.
After the activity is marked as complete, you can click the Refresh icon 
in the upper-right corner of the window to refresh the Resources table so that the newly created network containers appear in the list of network containers.
Related topics