About Alex

Alex · ‎10-19-2020

The CDP Upgrade Advisor is a utility available on MyCLoudera for Cloudera customers. This tool performs an evaluation of diagnostic data to determine the CDP readiness of your CDH or HDP cluster environment. Running the upgrade advisor against the cluster in question is one of your first steps to adopting CDP, followed by an in-depth conversation with your Cloudera account team to review the specific results. This utility raises awareness of clusters that may present risks during an upgrade to CDP due to, for example, an unsupported of the operating system currently in use. The upgrade advisor utility is focused on the environment and platform in use but doesn’t take into consideration use-cases, the actual cluster data, or workflows in use. Analysis of these critical areas occurs as part of your CDP Journey Workshop with your Cloudera account team and Professional Services. To run the Upgrade Advisor: Click Upgrade Path once logged in to https://my.cloudera.com to begin the evaluation based on your diagnostic data The first thing you’ll see is a list of your active assets (CDH, DataFlow, HDP, Key Trustee, and CDP assets). The upgrade advisor is available only for CDH and HDP environments. Click the respective CDP Upgrade Advisor link on the right-hand side of a CDH or HDP asset to obtain the evaluation results The Upgrade Advisor determines a recommended upgrade path for the asset in question. You may see a recommendation to upgrade to CDP Data Center (Private Cloud Base), Public Cloud, or not to upgrade at this time due to the environmental failures identified. Beneath the recommendations are details of the cluster asset being evaluated along with contact details for your Cloudera account team. The Evaluation Details section includes the results of the validation checks being performed against your diagnostic data. This includes risks and recommendations such as a particular service or version of 3rd party software that will not be supported after an upgrade to CDP. Each category of the evaluation details also features icons that will take you to the relevant CDP documentation. You can view a video (recommended) about the Upgrade Advisor here.

Alex · ‎04-07-2020

Hi Tim, Thank you for reaching out to Cloudera Support. Based on your user's registration in our support system, and the account of which you're part, I agree that raising a support case for issues with CDH is a valid request. Having said that, at this time, the account of which you're part has a restriction to not allow every user, by default, the ability to file support cases. To enable the access you're requesting, we would ask that you have a colleague/manager who presently has case access file a non-technical support case (using the instructions here: https://my.cloudera.com/faq.html#support) noting that you are approved to file cases too. The team who handles those requests will then make the necessary changes to your account and your access will then be enabled. If you have any questions or concerns please message me privately and I'll be happy to help. Thank you. Best, Alex

Alex · ‎03-16-2020

Hello Venkatesh, Have you already registered on cloudera.com from this URL: https://sso.cloudera.com/register.html If you have, please privately message me your email address and I'll check on it. Thank you sir. Best, Alex

Alex · ‎03-03-2020

This issue has been remedied. For anyone following along experiencing the same problem, the best possible path forward in order to have this type of account association problem fixed is to have one of your colleagues (with working access to the correct account) file a non-technical case in the MyCloudera Portal. The case will be accepted and the account association for the "broken" user will be fixed. Thank you kindly. Best, Alex

Alex · ‎03-03-2020

Hi Rajan, thank you for reaching out to Cloudera. Please privately message me with your email address along with the company to which you should be aligned. Any questions or concerns please let me know. Best, Alex

Alex · ‎01-13-2020

Hello @liang , does the following help? This link explains the SLAs in place for the various contractual service levels: https://my.cloudera.com/support/subscription-value-center.html#sla_based_technical_support This link explains the EOM (end of support) dates for the various versions of Cloudera software: https://www.cloudera.com/legal/policies/support-lifecycle-policy.html Thank you kindly. Best, Alex

Alex · ‎12-30-2019

I can confirm that the "company" information cannot be changed by the user on MyCloudera. Please ping me offline and I'll be happy to assist: alavoie@cloudera.com. Thank you kindly.

Alex · ‎05-07-2019

One important point: If the version of the software in use is 6.2, please let me know as I'll have additional license-related information to provide. Thank you kindly. Best, Alex

Alex · ‎05-07-2019

Thank you for reaching out to Cloudera Support via our Community. My name is Alex and I'm a member of the Customer Advocacy team. I can confirm the following 2 very important points: In accordance with our general policies and procedures, new enterprise license keys are provided to customers on the start date of the renewal/contract in question. Because of this, the expiration of an enterprise license key causes no product impact aside from a banner message in Cloudera Manager. You can be assured that a Cloudera Enterprise cluster will exhibit absolutely no adverse effects due to key expiration. If you would like to provide me specifics of the customer/partner contract in question, I'll be happy to deliver additional details regarding when the key will be delivered and to whom it will be sent. Please provide me a contact email address and I will respond directly. Thank you kindly. Best, Alex

Alex · ‎01-29-2018

Thank you Michael. I appreciate the links.

Alex · ‎01-23-2018

Completely agreed sir. +1

Alex · ‎01-22-2018

Hi Michael, Based on what I see in the script/code, it's the presence of inet6 in the ifconfig output, which is included in the diagnostic bundle. If inet6 is present and in use, I believe that's the basis for the alert that was issued. Best, Alex

Alex · ‎01-19-2018

Hi @mjarnold, I can comment on this on behalf of Ben. The docs received a minor improvement that advises the OS vendor to be contacted for complete information or any necessary assistance regarding disabling ipv6: Networking Protocols Support CDH requires IPv4. IPv6 is not supported and must be disabled. Note: Contact your OS vendor for help disabling IPv6. This was the resulting improvement in the docs stemming from the jira I filed after we first spoke about this issue. I know this isn’t much of a change, but we felt it was the most sound advice we could provide on the next-steps necessary. If you have any feedback please do let us know. We sincerely appreciate your long-running excellent partnership here with us in Cloudera Support. Best, Alex

Alex · ‎08-02-2017

Once the Enterprise License Key is removed, all of the enterprise functionality that is enabled by the Key is no longer going to be available. The functionality is documented here. For example, the Enterprise version of the software enables the following (as well as other very important services such as Encryption and Key Management) => ========== Advanced Features: Operational Reporting; Multi-Tenant Quota Management; Configuration History & Rollbacks; Rolling Updates & Service Restarts; SNMP Support; Support Integration (including scheduled diagnostics & proactive maintenance); Fine-Grained User Roles; & Automated Backup & Disaster Recovery ========== In terms of preparing your cluster for the removal of the Enterprise License Key, it's going to depend on what/which advanced features, or, other functionality you're using that is only available by virtue of using the Key. Without knowing the specifics of how the cluster is configured or running, it's not possible to confirm the steps that should be performed in order to ensure you won't have an impact once the Key is removed. If your cluster is dependent on any of the advanced features or other Enterprise functionality noted in the sheet I linked above, I would recommend proceeding with extreme caution before removing the License Key. If that is the case, I would recommend speaking to your Sales Representative at Cloudera to discuss options for being able to continue using the Enterprise version of the software. Hope this helps. Best, Alex

Alex · ‎05-25-2017

This question has also been addressed here, just FYY Tina: http://community.cloudera.com/t5/Cloudera-Manager-Installation/From-Cloudera-Manager-trial-to-Cloudera-Manager-Express/m-p/55005#M1385?eid=1&aid=1

Alex · ‎05-25-2017

Here's a page that describes the differences between the "Cloudera Enterprise" and "Cloudera Express" versions: https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_feature_differences.html#cmfeig_topic_5_1 To specifically answer your question, the expiration of a trial license key will indeed remove features such as LDAP authentication to Cloudera Manager, as noted in the table on the above-referenced document. So, if your CM had been set up and configured to authenticate against an LDAP store it's possible that, yes, this will no longer be working correctly. But, generally speaking, the expiration of a trial license key will not render a cluster un-usable, it's just simply that the enterprise functionality is no longer going to be available. Best, Alex

Alex · ‎05-24-2017

Thank you for looping me in, @cjervis. I can confirm that if a trial license key has expired, there's 2 possible paths forward. If by "trial" you're speaking of a formal enterprise support trial issued by Cloudera, the key does indeed need to be removed as noted earlier in this the thread linked by Cy. If by "trial" you're referring to the 60-day key that is capable of being downloaded directly from cloudera.com, there is no action needed. Upon the 60 days expiring, the cluster will revert back to express. If I can be of any further assistance please let me know. Thank you kindly. Best, Alex

Alex · ‎05-01-2017

https://www.cloudera.com/documentation/enterprise/5-6-x/topics/cm_ig_feature_differences.html Here's a nice side-by-side showing the functionality that's enabled by using the enterprise license key. In summary, those items will no longer be available. Does it mean the cluster will be inoperable? Definitely not. But, any functionality tied to the specific items in the document will be impacted. Hope this helps. Any further questions please let us know.

Alex · ‎05-01-2017

Removal of the enterprise license key will revert the cluster back to express. The documentation details the enterprise functionality that is enabled with the key in use. That functionality would no longer be available once the key isn't in place.

Alex · ‎05-01-2017

As per the contractual enterprise license agreement's language, the enterprise license key must be removed as per the instructions here if there's no further enterprise contract in place: https://cloudera-portal.force.com/articles/KB_Article/Removing-Cloudera-Manager-Enterprise-License Hope this helps.

Alex · ‎03-06-2017

Thank you Ben.

Alex · ‎05-19-2015

Rebooting the cluster resolved the error message/warning. If you experience this same error message after upgrading to 5.4.1 please open a support case with Cloudera. Thank you kindly.

Online	Offline
Last Visited	‎01-18-2021 09:10 AM

Date Registered	‎06-25-2014 07:40 AM
Last Visited	‎01-18-2021 09:10 AM
Total Messages Posted	31

Re: How to change the company in the profile

Re: Change-company-information-in-support-profile

Re: Disabling IPv6

Re: zookeeper test Maximum Request Latency is fail...

Adoption of CDP by using the CDP Upgrade Advisor u...

Re: Is it possible for a partner to open a support...

Re: Cloudera support page -access restricted error

Re: How to change the company in the profile

Re: How to change the company in the profile

Re: maintenance for Cloudera enterprise data hub e...

Re: Change-company-information-in-support-profile

Re: How long does it take to get a license renewed...

Re: How long does it take to get a license renewed...

Re: Disabling IPv6

Re: Disabling IPv6

Re: Disabling IPv6

Re: Disabling IPv6

Re: From Cloudera Manager trial to Cloudera Manage...

Re: What happens to a cluster after Cloudera Enter...

Re: From Cloudera Manager trial to Cloudera Manage...

Re: From Cloudera Manager trial to Cloudera Manage...

Re: What happens to a cluster after Cloudera Enter...

Re: What happens to a cluster after Cloudera Enter...

Re: What happens to a cluster after Cloudera Enter...

Re: Disabling IPv6

Re: zookeeper test Maximum Request Latency is fail...