7 Replies Latest reply on Mar 3, 2015 9:00 AM by Alba

    epo with vsphere and aws connectors

    glearning2000

      I'm evaluating DCC integration with epo but it's not working as claimed in the docs then I dig up from this site that there are issues with the synchronization with AWS and it requires a Critical patch etc. How can someone download the patch during evaluation? It defeats the purpose of evaluation if I need to be a customer to download broken RTW software for basic functionality, the whole purpose of having a AWS connector extension imported into the ePO is to do this sync and do host discovery!

       

      Is there anyway one can get access to the patches or SP during evaluation?

        • 1. Re: epo with vsphere and aws connectors
          Richard Carpenter

          Hi glearning2000

           

          Welcome to McAfee Communities!

           

          Could I ask which Critical Patch you are referring to. I am a VSphere Data Centre Connector user so I may be able to get the patch you are refering too.

           

          Regards

          Rich

          Volunteer Moderator

          Certified McAfee Product Specialist - ePO

          • 2. Re: epo with vsphere and aws connectors
            glearning2000

            Thanks for the follow-up. Sorry I should have provided some details.

             

            I've downloaded an evaluation version of "McAfee Server Security Suite Advanced" which comes with the;

             

            - AWS DCC version 3.5.0.116

            - Azure DCC version 3.5.0.131

            - VSphere DCC version 3.5.0.116.

             

            I'm not able to connect to the AWS and getting " Failed: Sync Operation Complete, Account Name : my AWS Account, Sync Status : Failure, Reason : Status Code: 401, AWS Service: AmazonEC2, AWS Request ID: 1b9ee55f-aa29-4b28-9f6f-3edaa7f31d7c, AWS Error Code: AuthFailure, AWS Error Message: AWS was not able to validate the provided access credentials"

             

            I found this KB article;

             

            https://kc.mcafee.com/corporate/index?page=content&id=KB82167

             

            Under Known Issues:

             

            It states;

             

            Issue:  Synchronization failures resulting from the addition of a new region on AWS. The new region is not authenticated and the synchronization fails.

            NOTE: Previously resolved in the DCC 3.5 Hotfix 1017068 for AWS release (extension build 3.5.0.122).

            Patches are available by logging in to the ServicePortal at:https://support.mcafee.com/downloads.

             

            as you see I need a higher build# then 116 which I currently have.

             

            I was hoping to get DCC 3.6.xxxx pack to avoid any further issues later in the evaluation but I can't find it either via evaluation route hence the post here....if you can provide a 3.6.xxxx pack for DCC that would be good other wise I've to skip this part and look for other features and continue with what ever I can at this point.

            • 3. Re: epo with vsphere and aws connectors
              Richard Carpenter

              hi glearning2000

               

              I can confirm your assumptions.

               

              I also have been 'trailing' the AWS Data Centre Connector and have been experiencing the same 401 errors you have described.

               

              I have downloaded the Hot fix you have identified DCC 3.5 Hot fix 1017068 for AWS release (extension build 3.5.0.122) and I can confirm that this DOES fix the issue.

               

              Do you use other McAfee Products and have a grant number?

              If you do you can sign up for a support account which will give you access to the Patches.

               

              If you do not we will try and track down the Product Manager and ask if we can provide you with te HotFix to be able to complete your Evaluation.

               

              Regards

              Rich

              Volunteer Moderator

              Certified McAfee Product Specialist - ePO

              • 4. Re: epo with vsphere and aws connectors
                glearning2000

                Thanks. At least now I don't worry about why it's not working for "me" ? part. I don't have access to portal for patch downloads so if it's not available for evaluations purposes then I guess I can move on from this functions and focus on other parts. let's hope the Azure and vSphere connectors work.

                • 5. Re: epo with vsphere and aws connectors
                  Richard Carpenter

                  Hi glearning2000

                   

                  I am trying to identify if we can get the Patch to you for you to test with.

                   

                  Regards

                  Rich

                  • 6. Re: epo with vsphere and aws connectors
                    glearning2000

                    Thanks. The Azure Connector does work .

                     

                    The vSphere connector is working "sort off" but I don't know if this is expected behavior?

                     

                    I was expecting to see under system tree the tree structure that I had in VC but it's incomplete. It stops at Hosts and doesn't expand after it, see below

                     

                    DCC_vSphere.png

                     

                    Under Hosts it should have two hosts esx03 and esx04 but it doesn't then I have to look at on the right.

                     

                    Lastly, why SVA's are placed in Lost and found?

                     

                    Lost and found.png

                     

                    Any ideas?

                    • 7. Re: epo with vsphere and aws connectors
                      Alba

                      The issue you experience with DCCON AWS is reported here:
                      Synchronization failure after a new infrastructure region is introduced by Amazon Web Services,  KB83250


                      The DCCON vsphere appears to work as expected, the HOST structure in your screenshot is accurate, on the left the HOSTS group and on the right the hosts list.

                      For the SVA is best to create a group called 'SVA' and you move them there.

                       

                      For the trial version I will check if possible to provide latest DCCON 3.6.0