search

NetAppDocs / bluexp-classification

https://docs.netapp.com/us-en/bluexp-classification/
0 stars 0 forks source link

Please at a section under "Prepare the Linux host system" for NTP time sync #102

Closed virtualhawk closed 7 months ago

virtualhawk commented 7 months ago

Page URL

https://docs.netapp.com/us-en/bluexp-classification/task-deploy-compliance-onprem.html

Page title

Install BlueXP classification on a host that has internet access

Summary

Hi Ben,

We ran into an error "Unable to load Data Sense, Authorization error" during an implementation of Data Sense.  The issue is caused due to BlueXP and Data Sense VM times are not synced.  This issue has been seen at other customers also.  Please add a section referencing that NTP will need to be enabled and the BlueXP connector VM and Data Sense VM times must be synced.

Public issues must not contain sensitive information

netapp-tonacki commented 7 months ago

Hi David, Thanks for bringing this to our attention. I will add this information into the docs shortly and let you know when it is live. This is great information to add.

Thanks, Tom

netapp-tonacki commented 7 months ago

Hi David, Would a user need to configure NTP for the connector when initially setting up the connector system? We're thinking we might want to add info about enabling NTP in the connector docs too if the user is planning to also set up BlueXP classification.

virtualhawk commented 7 months ago

Hi Tom,

           Apologies for the delay.  I completely agree with adding it to the Connector docs also as both VM's need to be in time sync or it causes the UI issues.

Thanks,

David Hawkins Professional Service Consultant Global Services Solutions Center

NetApp 330.892.7057 Direct Phone @.**@.>

[A logo with a white square on it Description automatically generated with medium confidence]

[A black circle with white letters Description automatically generated] [A black and white logo Description automatically generated] [A black and white logo Description automatically generated] [A black circle with a white play button Description automatically generated] [A black circle with white letters in it Description automatically generated] [A black circle with white x in it Description automatically generated] [A black circle with white logo Description automatically generated]

"We're committed to providing our customers with the best products and services. Scan the QR code or click on this linkhttps://listening.netapp.com/jfe/form/SV_3n6lnfKz33d6feC to provide your feedback. All responses will be anonymous and kept confidential. Thank you!"

From: Tom Onacki @.> Sent: Thursday, January 25, 2024 3:49 PM To: NetAppDocs/bluexp-classification @.> Cc: Hawkins, David @.>; Author @.> Subject: Re: [NetAppDocs/bluexp-classification] Please at a section under "Prepare the Linux host system" for NTP time sync (Issue #102)

You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

EXTERNAL EMAIL - USE CAUTION when clicking links or attachments

Hi David, Would a user need to configure NTP for the connector when initially setting up the connector system? We're thinking we might want to add info about enabling NTP in the connector docs too if the user is planning to also set up BlueXP classification.

- Reply to this email directly, view it on GitHubhttps://github.com/NetAppDocs/bluexp-classification/issues/102#issuecomment-1910973083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APSWSMOHHKQMH2D5F4QTDVLYQLAKBAVCNFSM6AAAAABCLA4VYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQHE3TGMBYGM. You are receiving this because you authored the thread.Message ID: @.**@.>>

netapp-tonacki commented 7 months ago

Thanks David. We've updated the BlueXP classification docs and the Connector setup docs (Ben did this) with this requirement for enabling NTP. We made changes in a few locations - here are 2 examples:

Thanks again for bringing this to our attention.

Tom

virtualhawk commented 7 months ago

Awesome! Thank you both as always! The quick turnaround on updating the docs is greatly appreciated!

Thanks,

David Hawkins Professional Service Consultant Global Services Solutions Center

NetApp 330.892.7057 Direct Phone @.**@.>

[A logo with a white square on it Description automatically generated with medium confidence]

[A black circle with white letters Description automatically generated] [A black and white logo Description automatically generated] [A black and white logo Description automatically generated] [A black circle with a white play button Description automatically generated] [A black circle with white letters in it Description automatically generated] [A black circle with white x in it Description automatically generated] [A black circle with white logo Description automatically generated]

"We're committed to providing our customers with the best products and services. Scan the QR code or click on this linkhttps://listening.netapp.com/jfe/form/SV_3n6lnfKz33d6feC to provide your feedback. All responses will be anonymous and kept confidential. Thank you!"

From: Tom Onacki @.> Sent: Wednesday, January 31, 2024 7:23 PM To: NetAppDocs/bluexp-classification @.> Cc: Hawkins, David @.>; Author @.> Subject: Re: [NetAppDocs/bluexp-classification] Please at a section under "Prepare the Linux host system" for NTP time sync (Issue #102)

You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

EXTERNAL EMAIL - USE CAUTION when clicking links or attachments

Thanks David. We've updated the BlueXP classification docs and the Connector setup docs (Ben did this) with this requirement for enabling NTP. We made changes in a few locations - here are 2 examples:

Thanks again for bringing this to our attention.

Tom

- Reply to this email directly, view it on GitHubhttps://github.com/NetAppDocs/bluexp-classification/issues/102#issuecomment-1920241614, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APSWSMIJXPH4A5XOWBTSXADYRLN57AVCNFSM6AAAAABCLA4VYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRQGI2DCNRRGQ. You are receiving this because you authored the thread.Message ID: @.**@.>>