5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Thanks, gael01- I do have File Analytics however I couldn’t find any obvious report or widget to provide what I was looking for. However, I did just stumble on the answer when navigating within the newer built-in ‘Files Console’. From the ‘Shares’ tab, there’s an option to select ‘View by Metrics’ (shown below). This view gives me exactly what I was after.
I opened a support case and will advise what the fix was once resolved.
Good question - I can’t even pull that report up to view its settings - I continually get this error instead;
Hi Raaji - thanks for the feedback. Here is my output from PC;nutanix@NTNX-PCVM:~$ grep -i LCM ~/data/logs/genesis.out2021-12-07 01:14:37,734Z ERROR 13346864 lcm_helper.py:56 No LCM leader available to check if LCM operation is in progress File "build/bdist.linux-x86_64/egg/cluster/client/lcm/lcm_helper.py", line 56, in is_lcm_update_in_progressnutanix@NTNX-PCVM:~$ python --versionPython 2.7.5nutanix@NTNX-PCVM:~$ cat ~/cluster/config/lcm/version.txt2.4.3.3.28012 Let me know if you think I should open a support case - thanks!
Thank you, Raaji. I am curious to know if each of the CVM’s forward their syslog messages to the destination server individually or if a single CVM in the cluster forwards every syslog messages for all of the other CVM’s in the cluster. I am only asking this because it appears that way in our cluster - where one CVM is active with sending syslog messages but our syslog server hasn’t received messages from the other CVM’s in the same cluster for several days or weeks.
Thanks, Neel - The SQL 2017 version of the powershell modules was installed however the local SQLPS that is installed with SQL Server (native to each version) was NOT uninstalled. Could this be a matter of adding this newer path for the 2017 versions to the PSModulePath environment variables for Powershell?
Thanks, Alona- so, based on your response, my 3 PCVM’s should just be kept in a local storage container and not included in any Protection Domain for replication to a remote site, correct?
Thanks, @nim - with regards to CALM, we did license it however we’re not actively using it. If we did migrate the PC-VM’s when 5.1.17.1 is released, I assume that we could then just install CALM from scratch?
Thank you, @nim - I was intending on keeping the same ip addresses so that’s not a concern. Also, I was not planning on using any Protection Domains for these migrations but rather just performing a ‘vmotion’ and ‘storage vmotion’ in VMware on one PC-VM at a time. I will let my management know that we should wait until AOS 5.17.1 is released - do you know have an estimated timeline for it’s release? Thanks!
@Tapati - I am just looking to migrate the (3) PC CVM’s - not their physical nodes. @AnishWalia20 - we have CALM licensed but are not actually using it. The PC-VM’s that I want to migrate are NOT part of the same Nutanix cluster. Thanks!
Thanks, kovitking. It turns out that the FSVM’s weren’t included as protected entities on the Async PD - so that explains why I never saw them failover when the PD was migrated.
Thank you for confirming that boot iso is required to stay with the additional PC appliances. I have a few follow up questions but first I’ll answer yours;Yes, all 3 PC’s are active and working. I am able to migrate PC from one datastore to another however the iso file stays in the original datastore. I presume that I’d need to power down the appliance since the seems to be locked when it’s running, unmount the iso file, migrate the iso to the destination datastore, remount it to the appliance, and then power it back up. Lastly, I don’t really have a good reason to move these to a different datastore within the same cluster, however, I would ultimately like to separate these PC appliances across sites and on different AOS clusters. Do you know if this feature is still on the roadmap for PC Scaleout?Now my questions are; Strangely, one of the 2 new PC appliances has multiple folders that host its vmdk disk files. I’m not sure how or why that happened but it’s only on this one PC appl
Thanks, Alona.I attempted to disconnect the iso and recieved this message in vCenter;The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?I responded with ‘No’. For whatever it’s worth, I see the following active Task in PC that has stayed at 83% for a while...; "Changing metadata fault tolerance from 0 to 1" with a subtask "Synchronizing metadata replicas"
Does anyone know if there's a way to do this when a cluster has more than 1,000 alerts? We had some network issue the other day and our 3-node cluster has over 150,000 alerts as a result.
Agreed - I don't want to lose our monkey with his banana. Maybe at least replace him with something like a dog with a bone? Or a seal with a beach ball? Or a prisoner with a metal file?
Sorry, I found the nCLI commands in the manual. ncli> virtual-disk { update-pinning } id="id" tier-name="tier_name" pinned-space="pinned_space"
I have completed the failover and found that the manually taken snapshots completed rather quickly. So I think it's safe to assume that these manual snapshots on a Metro PD use the initial full copy as a reference point thus making the time-to-complete rather small.
Thanks, dlink7- it appears that the Genesis log was indicating the following message; 2016-10-20 05:51:48 ERROR command.py:156 Failed to execute sudo service iptables status: [Errno 12] Cannot allocate memoryIt was about 20 hours afterwards though that I found the issue and sent the start command which made everything happy again.
Thanks, Jon. I'm running AOS 4.7.1 and NCC 2.2.7 in this cluster.
Well, as luck would have it, everything reappeared after performing a reboot of my Prism Central CVM and waiting about 5-10 minutes. And no data was lost - I like easy fixes!
The message appears on the runway page (as shown below) and is the same for any/all of my clusters in Prism Central.[img]https://d1qy7qyune0vt1.cloudfront.net/nutanix-us/attachment/1597iBD2F7FF09F4235D8.png[/img]
Yes, I just saw it today and I had upgraded Prism Central to v4.7.1 a couple of weeks ago and I know that it was working as recent as yesterday. I haven't tried rebooting Prism Central but I'm all for it if we think it will help. For what it's worth, the version of PC that I upgraded from was my Windwos 7 workstation.
I am seeing this now on our v4.7.1 Prism Central. I tried Chrome and IE browsers with the same message. Any suggestions? Let me know if I would be better off starting a new thread. Thanks!
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.
