5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
The cluster is running 4.0.1.1. It's still showing the alert in Prism for weeks now. Here's the output of cat /proc/meminfo: MemTotal: 16466964 kBMemFree: 937664 kBBuffers: 272600 kBCached: 1109760 kBSwapCached: 0 kBActive: 14200700 kBInactive: 863396 kBActive(anon): 13682816 kBInactive(anon): 2180 kBActive(file): 517884 kBInactive(file): 861216 kBUnevictable: 24536 kBMlocked: 8184 kBSwapTotal: 0 kBSwapFree: 0 kBDirty: 812 kBWriteback: 0 kBAnonPages: 13706708 kBMapped: 436092 kBShmem: 352 kBSlab: 206088 kBSReclaimable: 108460 kBSUnreclaim: 97628 kBKernelStack: 6768 kBPageTables: 89756 kBNFS_Unstable: 0 kBBounce: 0 kBWritebackTmp: 0 kBCommitLimit: 8233480 kBCommitted_AS: 15552704 kBVmallocTotal: 34359738367 kBVmallocUsed: 302668 kBVmallocChunk: 34359372536 kBHardwareCorrupted: 0 kBAnonHugePages: 11448320 kBHugePages_Total: 0HugePages_Free: 0HugePages_Rsvd: 0HugePages_Surp: 0Hugepagesize: 2048 kBDirectMap4k: 10240 kBDirectMap2M: 16766976 kB Thanks.
We did check DNS in Prism and both had the same entry. We checked with our TRM and SE and my understanding was 4.1.x versions were pulled off of the downloads site due to some bugs, but if they pulled 4.0.3 as well then it makes perfect sense as to why one of the clusters didn't have 4.0.3 on the list as I had only checked the "auto download" yesterday. Thanks all for the responses.
Still on 4.0.1
Hello - For partial scans, which component does the scans - Stargate, Curator, other? Thanks,
Hello All - Thank you for all the replies. Much appreciated. It turned out that the ports were hard coded to run at 100. Switching them to auto negotiate resolved the problem. DLINK7 - you were right on the money!!! Thanks. RV
Thank you!!!
After much troubleshooting, it turned out that the IPMIs were tagged under the 802.1q VLAN ID setting. Unfortunately, this isn't too obvious in the IPMI interface when consoled onto the system via a crash cart. We had to run the ipmitool utility in ESXi. Ran "/ipmitool lan print". Instead of showing it as "disabled" it had the VLAN ID instead. Then, we found this blog (and thanks to it) that shows that command to run: http://shanseworld.blogspot.com/2014/09/adding-vlan-id-to-ipmi-address-in.html The fix was to run: "~#ipmitool lan set 1 vlan id off"
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.
