0 Replies Latest reply on Dec 21, 2017 1:53 AM by Mahesh Doke

    Container Upgradation

    Mahesh Doke

      Hello Experties,

       

      I am upgrading the clm 2.1 to during the upgration of BNA component I need to place upgrade_properties file for the upgrade of version 8.1 of BNA can anyone please confirm the content in that file is developed on  which basis , Please let me know if anyone know it.

      Please find attached file for reference.

       

      Thanks in advance.

       

       

      ############################################################
      # CONTAINER INFO
      ############################################################
      # ***************************
      # Container : Sample Container
      # ****************************
      #
      # Names of the VFW'S inside the zones in "Sample Container"
      # 1. VFW stacking of "Sample Container" is of the following form from north to south.
      # 2. The vfw name in the key is represented in the form <zoneName>.<vfwName>
      # 3. The bridged interface names are represented in the form <zoneName>.<vfwName>.<interfaceName>
      # 4. For the serviced segments, either the NIC segment names (port types in 8.1.x) and/or the address pool name
      #     of the vip segments (associated with the load balancer pool type in that zone) can be provided.
      #
      #                   OUTSIDE.VFW
      #                       |
      #         --------------|-----------
      #         |             |           |
      #   SMB-ADMIN.VFW    LB.VFW     SMB-VPN.VFW
      #                       |
      #                -------|---------
      #                |      |        |
      #           WEB.VFW    APP.VFW   DB.VFW
      #
      containers[Sample\ Container].vfws[OUTSIDE.VFW].interfaces[OUTSIDE].servicedSegments=Default External Network
      containers[Sample\ Container].vfws[OUTSIDE.VFW].interfaces[OUTSIDE].bridgedInterfaces=
      containers[Sample\ Container].vfws[OUTSIDE.VFW].interfaces[inside].servicedSegments=
      containers[Sample\ Container].vfws[OUTSIDE.VFW].interfaces[inside].bridgedInterfaces=SMB-ADMIN.VFW.SMB-ADMIN, SMB-VPN.VFW.SMB-VPN, LB.VFW.INTF4-LB
      
      
      containers[Sample\ Container].vfws[SMB-ADMIN.VFW].interfaces[SMB-ADMIN].servicedSegments=
      containers[Sample\ Container].vfws[SMB-ADMIN.VFW].interfaces[SMB-ADMIN].bridgedInterfaces=OUTSIDE.VFW.inside
      containers[Sample\ Container].vfws[SMB-ADMIN.VFW].interfaces[inside].servicedSegments=
      containers[Sample\ Container].vfws[SMB-ADMIN.VFW].interfaces[inside].bridgedInterfaces=
      
      
      containers[Sample\ Container].vfws[SMB-VPN.VFW].interfaces[SMB-VPN].servicedSegments=
      containers[Sample\ Container].vfws[SMB-VPN.VFW].interfaces[SMB-VPN].bridgedInterfaces=OUTSIDE.VFW.inside
      containers[Sample\ Container].vfws[SMB-VPN.VFW].interfaces[inside].servicedSegments=
      containers[Sample\ Container].vfws[SMB-VPN.VFW].interfaces[inside].bridgedInterfaces=
      
      
      containers[Sample\ Container].vfws[LB.VFW].interfaces[INTF4-LB].servicedSegments=
      containers[Sample\ Container].vfws[LB.VFW].interfaces[INTF4-LB].bridgedInterfaces=OUTSIDE.VFW.inside
      containers[Sample\ Container].vfws[LB.VFW].interfaces[inside].servicedSegments=
      containers[Sample\ Container].vfws[LB.VFW].interfaces[inside].bridgedInterfaces=WEB.VFW.INTF1-WEB, APP.VFW.INTF2-APP, DB.VFW.INTF3-DB
      
      
      containers[Sample\ Container].vfws[WEB.VFW].interfaces[INTF1-WEB].servicedSegments=
      containers[Sample\ Container].vfws[WEB.VFW].interfaces[INTF1-WEB].bridgedInterfaces=LB.VFW.inside
      containers[Sample\ Container].vfws[WEB.VFW].interfaces[inside].servicedSegments=WEB
      containers[Sample\ Container].vfws[WEB.VFW].interfaces[inside].bridgedInterfaces=
      
      
      containers[Sample\ Container].vfws[APP.VFW].interfaces[INTF2-APP].servicedSegments=
      containers[Sample\ Container].vfws[APP.VFW].interfaces[INTF2-APP].bridgedInterfaces=LB.VFW.inside
      containers[Sample\ Container].vfws[APP.VFW].interfaces[inside].servicedSegments=APP
      containers[Sample\ Container].vfws[APP.VFW].interfaces[inside].bridgedInterfaces=
      
      
      containers[Sample\ Container].vfws[DB.VFW].interfaces[INTF3-DB].servicedSegments=
      containers[Sample\ Container].vfws[DB.VFW].interfaces[INTF3-DB].bridgedInterfaces=LB.VFW.inside
      containers[Sample\ Container].vfws[DB.VFW].interfaces[inside].servicedSegments=DB
      containers[Sample\ Container].vfws[DB.VFW].interfaces[inside].bridgedInterfaces=
      
      
      # *****************************
      # VLB Info for Sample Container
      # *****************************
      # This is only necessary if there is a VLB sitting in a zone all by itself originally,
      # with no NIC segments defined in that zone
      # 1. The VLB name in the key is represented in the form <zoneName>.<vlbName>
      # 2. The pool type name in the key is represented in the form <zoneName>.<vlbName>.<vipPool_networkName>
      # 3. If the VIP pool network name is not there, then provide the name of the vip pool.
      #     e.g poolTypes[LB.VLB.LB]
      #
      containers[Sample\ Container].vlbs[LB.VLB].poolTypes[LB.VLB.LB].servicedNicSegments=WEB, APP, DB
      
      
      ###################################################
      # Network Paths Information of the Sample Container
      ###################################################
      # The endpoints in the network paths are the network segment names in the container.
      # The serviced node names are represented in the form <zoneName>.<vfwName> or <zoneName>.<vlbName>
      # To provide network paths to a VIP segment, you can specify the address pool name of the VIP
      # segment as the endpoint.
      
      
      containers[Sample\ Container].endpoint1[Default\ External\ Network].endpoint2[WEB].servicedNodes=OUTSIDE.VFW, LB.VFW, WEB.VFW
      containers[Sample\ Container].endpoint1[Default\ External\ Network].endpoint2[APP].servicedNodes=OUTSIDE.VFW, LB.VFW, APP.VFW
      containers[Sample\ Container].endpoint1[Default\ External\ Network].endpoint2[DB].servicedNodes=OUTSIDE.VFW, LB.VFW, DB.VFW
      containers[Sample\ Container].endpoint1[Default\ External\ Network].endpoint2[LB].servicedNodes=OUTSIDE.VFW, LB.VFW
      containers[Sample\ Container].endpoint1[WEB].endpoint2[APP].servicedNodes=WEB.VFW, LB.VFW, APP.VFW
      containers[Sample\ Container].endpoint1[APP].endpoint2[DB].servicedNodes=APP.VFW, LB.VFW, DB.VFW
      containers[Sample\ Container].endpoint1[WEB].endpoint2[DB].servicedNodes=WEB.VFW, LB.VFW, DB.VFW
      containers[Sample\ Container].endpoint1[Default\ External\ Network].endpoint2[VIPS1].servicedNodes=WEB.VLB
      Copy the content of the following container blueprint information example, paste it into the the upgrade_8_2.propertiesfile, and update it with the specifics for your BMC Network Automation system. The instructions in the comments provide details on the information required.
      
      
      Notes
      
      
      The keys and values in the upgrade_8_2.properties file are case-sensitive.
      If a key in the upgrade_8_2.properties file has a space in the name, the space must be preceded by a backward slash. For example: containers[Sample\ Container].
      Container blueprint information example
      ############################################################
      # CONTAINER BLUEPRINT INFO
      ############################################################
      
      
      # ************************************************
      # Container Blueprint : Sample Container Blueprint
      # ************************************************
      #
      # Names of the VFW blueprints either in Firewall Host Blueprints or in
      # Pair blueprints in Sample Container Blueprint.
      #
      # 1. The vfw blueprint name in the key is represented in the form <firewallHostBlueprint>.<vfwBlueprintGuestNodeName>
      #    or as <firewallHostPairBlueprint>.<vfwBlueprintGuestNodeName>
      # 2. The bridged interface names are represented in the form <zoneBlueprintName>.<vfwGuestNodeName>.<interfaceBlueprintName>
      # 3. For the serviced segment names, either the NIC segment blueprint names (port type blueprints in 8.1.x) and/or the address pool name
      #     of the vip segment blueprints (associated with the load balancer pool type blueprint in that zone blueprint) can be provided.
      #
      #
      #                         FIREWALL-OUTSIDE.VFW
      #                                |
      #                   -------------|--------------
      #                  |             |             |
      # FIREWALL-SMB-ADMIN.VFW  FIREWALL-LB.VFW   FIREWALL-SMB-VPN.VFW
      #                                |
      #               -----------------|-----------------
      #               |                |                |
      #    FIREWALL-WEB.VFW    FIREWALL-APP.VFW      FIREWALL-DB.VFW
      #
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-OUTSIDE.VFW].interfaceBlueprints[OUTSIDE].servicedSegmentNames=Default External Network
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-OUTSIDE.VFW].interfaceBlueprints[OUTSIDE].bridgedInterfaceNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-OUTSIDE.VFW].interfaceBlueprints[inside].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-OUTSIDE.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=SMB-ADMIN.VFW.SMB-ADMIN, SMB-VPN.VFW.SMB-VPN, LB.VFW.INTF4-LB
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-ADMIN.VFW].interfaceBlueprints[SMB-ADMIN].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-ADMIN.VFW].interfaceBlueprints[SMB-ADMIN].bridgedInterfaceNames=OUTSIDE.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-ADMIN.VFW].interfaceBlueprints[inside].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-ADMIN.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-VPN.VFW].interfaceBlueprints[SMB-VPN].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-VPN.VFW].interfaceBlueprints[SMB-VPN].bridgedInterfaceNames=OUTSIDE.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-VPN.VFW].interfaceBlueprints[inside].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-SMB-VPN.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-LB.VFW].interfaceBlueprints[INTF4-LB].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Fire wall-LB.VFW].interfaceBlueprints[INTF4-LB].bridgedInterfaceNames=OUTSIDE.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-LB.VFW].interfaceBlueprints[inside].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-LB.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=WEB.VFW.INTF1-WEB, APP.VFW.INTF2-APP, DB.VFW.INTF3-DB
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-WEB.VFW].interfaceBlueprints[INTF1-WEB].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-WEB.VFW].interfaceBlueprints[INTF1-WEB].bridgedInterfaceNames=LB.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-WEB.VFW].interfaceBlueprints[inside].servicedSegmentNames=WEB
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-WEB.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-APP.VFW].interfaceBlueprints[INTF2-APP].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-APP.VFW].interfaceBlueprints[INTF2-APP].bridgedInterfaceNames=LB.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-APP.VFW].interfaceBlueprints[inside].servicedSegmentNames=APP
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-APP.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=
      
      
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-DB.VFW].interfaceBlueprints[INTF3-DB].servicedSegmentNames=
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-DB.VFW].interfaceBlueprints[INTF3-DB].bridgedInterfaceNames=LB.VFW.inside
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-DB.VFW].interfaceBlueprints[inside].servicedSegmentNames=DB
      containerBlueprints[Sample\ Container\ Blueprint].vfwBlueprints[Firewall-DB.VFW].interfaceBlueprints[inside].bridgedInterfaceNames=
      
      
      # ***************************************************
      # VLB Blueprint Info for Sample Container Blueprint
      # ***************************************************
      # This is only necessary if there is a VLB blueprint sitting in a zone blueprint all by itself originally,
      # with no NIC segments defined in that zone blueprint
      # The vlb blueprint name in the key is represented in the form <loadBalancerHostBlueprint>.<vlbBlueprintGuestNodeName>
      # or as <firewallHostPairBlueprint>.<vlbBlueprintGuestNodeName>
      # The pool type blueprints are identifed with the Vip Pool Name.
      #
      containerBlueprints[Sample\ Container\ Blueprint].vlbBlueprints[Load\ Balancer.VLB].poolTypeBlueprints[LB].servicedNicSegmentNames=WEB, APP, DB
      

      Regards,

      Mahesh