5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Please try this one:https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2052-Cisco-ACI:BP-2052-Cisco-ACI
Hi etr.eric, I consult with a dev guy, he told me you need to do an import in phyton: from fiql_parser import parse_str_to_expression Then : if "string" in category_name and if "string" not in category_name Must work well, please let me know if this helps. Regs Antonio
Hi Dotex, *Free Technical Exams Through July 31, 2020* In an effort to bring you financial relief during this challenging time, Nutanix is offering our partners free NCP, NCAP, and NCSE L1 certification exams through July 31, 2020. This offer includes one free exam attempt per individual per certification for the NCP, NCAP, and NCSE Level 1 certifications only. Your organization must be an authorized Nutanix partner at the time of your exam registration to be eligible for this offer. Partner individuals who have previously passed these exams are ineligible to attempt again as a part of this offer. The free exam offer period is April 22-July 31, 2020. Regarding sample questions, there is a test exam for NCP and a buch of material that you can take from the nutanix nuschool portal https://nuschool.portal.relayware.com/?eid=Register You need to be Nutanix user, partner or employee to get access to the material. Regs. Antonio
I agree MrMike, To ask for a RFE you must open a case and select issue type RFE, Request for Enhancement. The RFE will be added to an ENG or FEAT. The ENG number can be referenced to the customer to watch for their release in the release notes. We use the cases to upvote the ENG/FEAT tickets. Regs. Antonio
Sorry Mike, Here is the content of the KB. Let me know if this helps. This issue can be found when a customer is using Prism Central to connect Xi-Leap or Leap PC-PC, and is attempting to protect or take a snapshot of a VM from Prism Central when the VM is already protected by a legacy DR (Async). When attempting to take the snapshot of the VM from PC, the "snapshot" option will be greyed out and a message will be displayed saying "One of more of the selected VMs are protected via Legacy DR". This is an expected behavior as Nutanix Engineering do not want to mix up the PC workflows with those of PE. In future releases of PC, the error message displayed will be more descriptive to what the corrective actions are with respect to the issue. If customer wants to move from Legacy DR and start using the Leap (PC) workflows, they will need to first come out of legacy workflow and from that point, start using PC-based workflows.
Hi @Anand_Saw I got a couple of opinions from the team, hope they help: 1) The Best Practice for this scenario, for an Enterprise enviroment is to have a separate DEV (Test) Cluster.For those scenarios where you are unable to following an appropriate data center design, or common sense. One common way to do this in an vSphere enviroment would be to have two separate vSphere Clusters .Cluster A 3-Node with Production VMs, Cluster B 1-Node or more for Test/Dev VMs. In this scenario all 4+ nodes would be part of the same Nutanix Cluster. They have to be aware that vSphere HA may be configured to support 1 node failure in each vSphere Cluster, however, only 1 node failure would be survivable in the Nutanix Cluster. 2)One other solution is to create a rule in vCenter saying that all DEV/TEST VMs can run only in one or 2 particular hosts. So if those hosts become constraint, critical VMs will be migrated by DRS but dev/test VMs will remain there. Regs. Antonio
Hi MrMike. This kb describes the issue you are having, pleae check if this is your case an let me know if you need additional assistance. VM cannot be snapshot from PC when protected by legacy DR https://portal.nutanix.com/kb/7722 Note: Legacy DR = legacy DR/Async, refer to the following kb to know more about DR/Async ASYNC DR PROTECTION DOMAIN CONFIGURATION Regs. Antonio
Hi Luther I think I will go to 5.15 LTS unless you are looking for an specific 5.16 feature. Also please review the relese notes for both versions. Regs. Antonio
Please also correct the following FATAL alarm reported : FAIL: CVM is not uplinked to any 10Gbps nics on bridge/vSwitch br0.Node 172.16.1.32:FAIL: CVM is not uplinked to any 10Gbps nics on bridge/vSwitch br0.Refer to KB 1584 (http://portal.nutanix.com/kb/1584) for details on 10gbe_check Follow the KB 1584 on AHV section. This will allow to have 10gb on vSwitch on the affected host (172.16.1.32) as the AHV Network Best Practices recommend. Regs, Antonio
I need more specific information regrading your cluster, could you please add the following: Screenshot of the Create File Server Screen from Prism From any CVM, please provide the output from the following commands: ncli cluster info ncli host ls ncli alert ls cluster status | grep -v UP nodetool -h 0 ring ncli cluster get-domain-fault-tolerance-status type=node ncc health_checks run_all Note: For a two node cluster It is only possible to deploy one one Files FSVM with no Distributed shared. Please also review the prerequisites for Files Regs. Antonio
The ERROR message: Cannot upgrade two node cluster when cluster has a leader fixed… means that the cluster is under-replicated. Curator is responsible for kicking off replication for all extent groups that are not adequately replicated. A Curator full scan is needed to replicate the under-replicated data. Solution: Refer to KB 2826. Wait for cluster data to be rebalanced across nodes and Current Fault Tolerance to show 1. Once the curator scan has completed, run the pre-upgrade check again. It could be that it takes a couple of scans dependent on the number of underreplicated egroups. Regs. Antonio
I would recommend to upgrade the cluster to AOS 5.10.7 or 5.11.1 because restarting genesis on a two node cluster with AOS 5.10.6 could lead to cluster instabillity. After Upgrade ty to Re-Deploy the File Server using Prism and let us know. Meanwhile I am searching for an alternate solution. Regs.
Hi kovitking If you have the following error: The cause here is that manually updating the CVM's netmask will not update the value of 'external_subnet' in Zeus. This prevents the Data Services IP from communicating with the FSVMs and in turn not being able to mount the zpools. Note: The proper way to update CVM IP and/or subnet mask configuration is documented here. Please have the following information ready : 1) Verify the CVM IP and subnet via ifconfig. allssh "ifconfig eth0 | grep inet\ " Example: nutanix@cvm:~$ allssh "ifconfig eth0 | grep inet\ " ================== 10.58.85.39 ================= inet 10.58.85.39 netmask 255.255.255.0 broadcast 10.58.85.255 ================== 10.58.85.40 ================= inet 10.58.85.40 netmask 255.255.255.0 broadcast 10.58.85.255 ================== 10.58.85.41 ================= inet 10.58.85.41 netmask 255.255.255.0 broadcast 10.58.85.255 2) Verify what zookeeper has for the external_subnet: zeus_config_printer | grep ^external_s
No yet, last status (30/Mar/2020) on ESX 7.0 and vSphere 7.0 Qualification Engineering tickets are still open, They are working on Qualify and certify all Nutanix components with vSphere 7.0 Stay tune..
Hi hienle I was searching about it and it is really limited by network bandwidth between Foundation and all the parallel nodes. In the past the limit was 20 nodes max but this limitation was removed a long time ago. One of our top customers did 32 nodes from a single foundation instance over 10Gb, and it took about 40m per instance. They gave foundation plenty of resources. Hope this helps.
Reach out PSI.Nutanix using the mail psi.nutanix@psionline.com they are having issues now with the identity module, they will be sending you en email asking for a phone number and a shift available to call you.
Hi Carlos, I saw there is an action plan from Cesar Navarro from the caso you already open, did it work? Action plan: ==== ++Check the team modes: nutanix@cvm$ ssh root@192.168.5.1 ssh root@192.168.5.1 "ovs-appctl bond/show br0-up" ++If enabled lldpctl command will give you more info [root@Prolix2 log]# lldpctl ++ Never do changes with running vms in the node. Move the vms first. ++ If active-backup is used, you could change the active slave and check. To check and change the active slave interface on the non-working node: nutanix@cvm$ ovs-appctl bond/show # note the "active slave" nutanix@cvm$ ovs-appctl bond/set-active-slave bond0 eth2 If it is eth3, try to change it the other member in the bond, for example eth2. ++ To check interface change you can look at this log [root@ ~]# tail -F /var/log/openvswitch/ovs-vswitchd.log
With the new Witness capability, the process of disabling Metro Availability and Promoting the Container in case of a site outage or a network failure is fully automated which ensures the fastest possible RTO. The Witness functionality is only used in case of a failure, meaning a Witness failure itself will not affect VMs running on either site. Metro Guide with 5.0 considerations including the Metro Witness is available : https://portal.nutanix.com/page/documents/solutions/details/?targetId=BP-2009_Metro_Availability:BP-2009_Metro_Availability
NGT version 1.5.2 is the latest for the AOS you are running (5.9.2.4)
Follow the troubleshooting steps on the KB article : NCC Health Check : check_ntp Specially those in the section: “If the check reports "FAIL: The hypervisor is not synchronizing with any NTP server" If the issue is still not resolved, consider engaging Nutanix Support, providing the results and any output from general troubleshooting and current cluster NTP configuration.
There is a post that also cover this requirement: How to Get NCC Health Check report on Email
Hi chenzh4. The issue stems from the ethtool version in current AHV versions, which does not include parsing logic for some of the link modes of newer cards, and we can't update to a newer ethtool version until we upgrade to a newer userspace (CentOS 7). All the current GA AHV versions are still using a CentOS 6 userspace, so we still have the older ethtool version. So until that happens we'll have some reporting problems sometimes when using newer model NICs in AHV. as long as the speed value is correct, then there shouldn't be any production-impacting issues from that, just a display/reporting problem.
Hi Rossana, I hope this information regarding sizing and deploying SAP on Nutanix will be useful to you. Sizing SAP on Nutanix Sizing and deploying SAP on Nutanix is simple by design and risk-free. Whether running Nutanix AHV, VMware ESXi, or Microsoft Hyper-V, the Nutanix platform provides all the enterprise features that customers expect in terms of scalability, performance, high availability, and disaster recovery. The process for sizing an SAP environment on Nutanix is straightforward and well established, and Nutanix sales teams are available to assist with selecting the optimal infrastructure for customers’ current and future needs. At a high level, sizing involves the following points: For new and existing SAP environments, follow standard application sizing guidance from SAP (SAP account required). Perform compute sizing using the hardware’s SAPS (SAP Standard Application Benchmarks) rating, which SAP publishes on its benchmarks page. Use best practice guidance from Nutanix, VM
The following command can be used to debug login problems and verify IPMI connectivity from SCOM server (default location: C:\Program Files\Nutanix Inc\SCOM\ipmiutil-3.0.2-win64): (please define IpmiIp, IpmiUsername and IpmiPassword for the three variables and execute the command) ipmiutil.exe sensor -s -N $IpmiIp -U $IpmiUsername -P $IpmiPassword -F lan2 -V 2 The output of the command may show the following: Opening lanplus connection to node XX.XX.XX.XX ... ERROR: user name too long. (Exceeds 16 characters) LANPLUS error in RAKP1 It appears "ipmiutil" is failing to validate user account due to username length limitation. Username for BMC is limited to 16 characters. Password limitation is set to the following:ipmitool version 1.5 is 16 characters ipmitool version 2.0 is 20 characters. Please make sure and verify if username / password length does not exceed the above mentioned limits.
Please involve the Hardware Vendor to confirm if the procedure is possible on the Platform concerned and the configuration is approved before proceeding. An additional consideration in a mixed cluster is to verify the number of All Flash nodes as there is a minimum requirement. Procedure: 1. Remove the Node from Cluster using steps mentioned in Prism Web Console Guide. 2. Once Node removal completes, Shutdown the Node. 3. Replace all HDD with SSDs in the node physically. 4. ReImage the Node using Foundation with AOS and Hypervisor Version of the cluster its going to be added to using Field Installation Guide. 5. Once Imaging completes, follow Cluster Expansion procedure using Prism Web Console Guide.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
