Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Example of container reprovisioning - expanding the private data network


As an organization grows, so does its need for IP addresses. At some point, you may realize that you are running out of addresses.

Warning

With the exception of Network Address Translation (NAT) pool expansion, any networking component added to a blueprint targeted for container reprovisioning must be in a disabled state, otherwise the reprovisioning operation might fail.

The following example shows how you can scale out the number of public IP addresses supported within a network container if the initial container was created with a limiting blueprint. You accomplish this expansion by adding a new NIC segment.

To expand the private data network

  1. Inject a new NIC segment into the network container blueprint, as shown in the example below. 


    <nicSegmentBlueprint xsi:type="containerNicNetworkSegmentBlueprint" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        
    <addressPoolName>AccessC</addressPoolName>
        
    <customerFlag>true</customerFlag>
        
    <defaultEnabledFlag>false</defaultEnabledFlag>
        
    <lockedFlag>false</lockedFlag>
        
    <managementFlag>false</managementFlag>
        
    <name>AccessC</name>
        
    <networkName>AccessC</networkName>
        
    <tag>Purpose[Application]</tag>
        
    <vlanName>AccessC</vlanName>
    </nicSegmentBlueprint>

     For information about reprovisioning network containers in BMC Network Automation, see Reprovisioning-network-containers-in-BMC-Network-Automation and Configuring-a-reprovisioning-operation-for-network-containers.

  2. Import the new blueprint revision into BMC Network Automation by using the import script. See Creating-network-container-blueprints.
  3. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  4. Re-onboard the blueprint.
  5. Under Quick Links on the left, click Network Containers under the General section.
  6. Select the network container to which you want to add the new NIC segment.
  7. Click the Reprovision Network Container icon reprovision_NC.gifto launch the Reprovision Network Container dialog.
     The Reprovision Network Container dialog is displayed.
    reprovision_NC_screen.gif
  8. Select the blueprint version to which you want to reprovision the network container.
  9. Click Reprovision.
  10. After the network container is reprovisioned, you can edit the container and add enable the new NIC segment:
    1. On the Edit network container dialog box, click Next to proceed to the Dynamic Containers dialog box.
    2. On the Networks tab, select the new NIC segment from the network list and click the Enable icon.
    3. Click Save.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*