Editing the pod and network container XML blueprints to be compatible with LPAR

Because BMC Network Automation does not directly support LPAR, you must create a ROGUE_DEVICE in the pod blueprint.

Then you must make the the pod and network container XML blueprints compatible with LPAR by editing the <nameWithinSwitch> tag for fetching the VLAN ID instead of VLAN name.

You then use these blueprints to create pods and network containers in BMC Network Automation.

To create a ROGUE_DEVICE in the pod blueprint

You must make the following important changes to the pod blueprint to create a rogue device.

For rogue devices, you must have a management network on the POD level and a porttype defined for the rogue device

  1. Open the pod blueprint.
  2. Scroll to <nodeBlueprints>.
  3. Insert the following text:

    <paramBlueprints>
      <paramBlueprint>
        <description>ROGUE DEVICE ADDRESS</description>
        <name>ROGUE_DEVICE_ADDRESS</name>
        <type>String</type>
      </paramBlueprint>
    </paramBlueprints>
    

    See the following section on <nodeBlueprint> constructs  for an example of where to place the <paramBlueprints> section.

  4. For ROGUE_DEVICE_ADDRESS, enter the rogue device address in the following format:

    <switch_name>@<frame_name>@AMO Name/<frame_name>


    For example:

    <paramBlueprints>
      <paramBlueprint>
        <description>ROGUE DEVICE ADDRESS</description>
        <name>ROGUE_DEVICE_ADDRESS</name>
        <type>String</type>
      </paramBlueprint>
    </paramBlueprints>
    

    Note

    An example of a ROUGE DEVICE ADDRESS is ETHERNET0(Default)@pun-rds-aix05@pun-rds-aix05.

    Here, ETHERNET0(Default)is a switch name and pun-rds-aix05 is the IBM Frame Name.

    The Rogue Device address for your environment might be different than the one shown in the example.

  5. Scroll to <namewithintheswitch>.
  6. Change the code from:

    <portTypeBlueprints>
      <portTypeBlueprint>
        <name>Management</name>
        <nicSegmentName>Management</nicSegmentName>
        <nameWithinSwitch>Management</nameWithinSwitch>
      </portTypeBlueprint>
    </portTypeBlueprints>
    

    to:

    <portTypeBlueprints>
      <portTypeBlueprint>
        <name>Management</name>
        <nicSegmentName>Management</nicSegmentName>
        <nameWithinSwitch>${pod.vlans[Management Vlan]}</nameWithinSwitch>
      </portTypeBlueprint>
    </portTypeBlueprints>
    
  7. Save the file.
    You can then import the pod blueprint into BMC Network Automation.

Example of nodeBlueprint construct

In the pod blueprint, the <paramBlueprints> construct must be placed within the applicable <nodeBlueprint> construct, as shown in the following example:

<nodeBlueprints>
       <nodeBlueprint xsi:type="podHypervisorSwitchBlueprint" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <balancedParamBlueprints/>
            <category>2</category>
            <defaultShareableFlag>false</defaultShareableFlag>
            <name>Access Switch 1</name>
            <optionalFlag>false</optionalFlag>
 
<!-- ========== Place it here ============================= -->
 
            <paramBlueprints>
                <paramBlueprint>
                    <description>Rogue device address</description>
                    <name>ROGUE_DEVICE_ADDRESS</name>
                    <type>String</type>
                </paramBlueprint>
            </paramBlueprints>
 
<!-- ========== Done ============================= -->
 
            <role>Access Switch 1</role>
            <portTypeBlueprints>
                <portTypeBlueprint>
                    <name>Management</name>
                    <nicSegmentName>Management</nicSegmentName>
                    <nameWithinSwitch>${pod.vlans[Management Vlan]}</nameWithinSwitch>
                </portTypeBlueprint>
            </portTypeBlueprints>
        </nodeBlueprint>     
    </nodeBlueprints>

To edit the network container blueprint XML

You must make the following changes to the network container blueprint.

  1. Open the container blueprint.
  2. Scroll down to <nodeBlueprints>.
  3. Insert the following text to take no action in BMC Network Automation on this node:

    <configureActionInfoBlueprints/>
    <unconfigureActionInfoBlueprints/>
  4. Scroll to the <nameWithinSwitch> tag.
  5. Change the code from:

    <portTypeBlueprints>
      <portTypeBlueprint>
        <name>Customer</name>
        <nicSegmentName>Customer</nicSegmentName>
        <nameWithinSwitch>${container.name}.Customer</nameWithinSwitch>
      </portTypeBlueprint>
    </portTypeBlueprints>
    

    to:

    <portTypeBlueprints>
      <portTypeBlueprint>
        <name>Customer</name>
        <nicSegmentName>Customer</nicSegmentName>
        <nameWithinSwitch>${container.vlans[Customer]</nameWithinSwitch>
      </portTypeBlueprint>
    </portTypeBlueprints>
    
  6. Save the file.

    MultiExcerpt named 'createpod' was not found
The multiexcerpt named 'createpod' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro. 

Was this page helpful? Yes No Submitting... Thank you

Comments