3 Replies Latest reply on Oct 18, 2018 10:20 AM by Akshay D

    Failed to Re - provisioning NC with VDS

    Akshay D
      Share This:

      Hi Team,

       

      This is CLM 4.6.05 windows platform configured with vCenter and we have POD & NC configured with Standard switches having 18 nodes in it.

      Now we want to re-provision this container with VDS.

       

      What approach we can choose to perform this activity because it failed to reprovision with following error:

        Error occurred while reprovisioning the network container: NC-name Error: MissingEntityInBlueprintException: Component instance containerNode[name=Access] in container[name=NC-name] is missing in blueprint used to reprovision container.,

       

      Steps followed:

      1. Added VDS in BNA and its node in respective POD

      2. Modified the NC blueprint with new revision, new node.

      3. Imported and tried to re-provision container - failed to re-provision.

       

      Any help will be appreciated. Thank you in advance.

       

      Regards,

      Akshay

        • 1. Re: Failed to Re - provisioning NC with VDS
          Akshay D

          So, we come to conclusion that NC can not be re-provision by removing existing nodes and adding new node in blueprint, coz it gives the MissingEntityInBlueprintException and if you add new node by keeping all previous nodes then re - provisioning NC will be successful.

           

          Here we added vDS in Blueprint and re-provisioned container. Now, the container having 18 nodes with Standard switch and 1 additional vDS node.

          Soon the the standard switches will be completely removed from vCenter, so its configuration inside NC will not be useful. How to remove its configuration from NC is still a question, without impacting other dependencies.

           

          From BMC support, we received following recommendation,

          Off-board SOI from CLM, Migrate the VMs on vDS in vCenter and on-board SOI in CLM on respective container.

           

          Please add your comments if any by considering following scenario:

                    If cluster having 5 hosts with standard switches and we configured 5 nodes in NC, later 1 host is added in the same cluster then we can easily re-provision the network container by adding new device and node in blueprint. In reverse, if 2 hosts are removed from that cluster then how we can remove its respective nodes & config from network container.

           

           

           

          Regards,

          Akshay

          • 2. Re: Failed to Re - provisioning NC with VDS
            Thomas Stiefel

            Akshay D schrieb:

             

            Please add your comments if any by considering following scenario:

                      If cluster having 5 hosts with standard switches and we configured 5 nodes in NC, later 1 host is added in the same cluster then we can easily re-provision the network container by adding new device and node in blueprint. In reverse, if 2 hosts are removed from that cluster then how we can remove its respective nodes & config from network container.

            It´s not possible to remove nodes from an existing network container which is in use! We are having same issue while migrating from Nexus 1000v to vDS and for me this is clearly a design issue, because it works as designed and therefore it´s getting broken by design. ;-)

             

            If you set old and unsed devices offline or remove them from Pod, then BNA will recognize this and will not try to configure this old devices anymore, but they will stay in blueprint and container forever!

             

            After my investigation you have just one alternative option:

            1. Offboard all VMs in network container.
            2. Remove network container.
            3. Recreate network container with just new devices in blueprint.
            4. Onboard all VM again.

             

            Not a cool way, but the only one.

             

            Best Regards,

            Tom

            • 3. Re: Failed to Re - provisioning NC with VDS
              Akshay D

              Hey Thomas Stiefel

              Thanks for an information, we also considering this off-board VM option.

               

              Regards,

              Akshay