Connecting Cloud Innovators: Building Community at .NEXT 2024
Access to all the advanced monitoring pages including stargate are disabled by default, to access them you need to disable the firewall on CVM/s for each individual port/s, in this case 2009. I personally wouldn't worry about viewing 2009 at least for this issue, we know how Exchange/Jetstress behaves, if the cluster/networking etc is working correctly, Jetstress will pass as per my blog posts. Let's follow up in the support ticket as we like to track all issues so we can better assist customers in future support requests.
Sorry yes, Compression only for Real world deployment not Jetstress.
Hi RItchie There is no issues mixing nodes, in fact in many cases we recommend it when scaling or designing solutions with large mailbox capacity. What is the Jetstress configuration? How many databases, what size per database, how many vDisks per VM (one per DB and one per logs is our recommendation, with In-Line Compression for DBs and no compression/dedupe/EC-X for logs). If you can provide this info to our support organisation, let them know to contact me and I can provide assistance and see what is happening. If you are getting network alerts its possible a network bandwidth/configuration or teaming issue is causing the issue, but I can only speculate at this stage. We'll get it resolved.
Hi Ritchie, A few things, firstly have you seen this post regarding Jetstress testing on tiered storage devices? [url=http://www.joshodgers.com/2016/01/26/jetstress-testing-with-intelligent-tiered-storage-platforms/]http://www.joshodgers.com/2016/01/26/jetstress-testing-with-intelligent-tiered-storage-platforms/[/url] I would recommend you review and follow the recommendations here. Second: Checkout this series showing Jetstress performance testing which shows vMotion (and soon) failure scenario testing videos of Jetstress on Nutanix. [url=http://www.joshodgers.com/2016/02/01/microsoft-exchange-20132016-jetstress-performance-testing-on-nutanix-acropolis-hypervisor-ahv/]http://www.joshodgers.com/2016/02/01/microsoft-exchange-20132016-jetstress-performance-testing-on-nutanix-acropolis-hypervisor-ahv/[/url] Third: If you have followed our recommendations and have N+1 setup, meaning 1 less Exchange server than total nodes in the cluster, you should simply be able to shutdown a
With the introduction of Load Based Teaming (LBT) on the Virtual Distributed Switch in vSphere 4.0, the requirement to consisder other forms of NIC teaming & load balancing in my opinion have all but been eliminated which is why when releasing our vNetworking Best Practices, the numerous VCDXs involved including myself, concluded LBT (Option 1 in the BPG) should be our recommendation. There are many reasons LBT is excellent including: 1. Simplicity No dependancy on the switch type or configuration. Stardard Access points with 802.1q is all that is required for LBT and multiple VLAN support. No requirement to design IP address ranges around IP Hash to ensure the hash from the IPs ensures a balance of traffic. 2. Performance LBT detects NIC utilization of >=75% and dynamically load balances VMs across the available NICs in real time. 3. LBT works with "Link Status" failover policy No complexity with failover and failback, Link Status and (if supported by physical switch)
Hi Tjagoda, I'd like to echo Tony's comments, the issue your experiencing is surprising as this is not what we're seeing at other customers, or personally in my performance lab. Definatley open a ticket with our support team, and I'll work with them and you to ensure this is resolved.
Sylvain is correct, you could simply use iSCSI to host Exchange workloads, to be strictly compliant with Microsofts support policy. However, this would simply add unnessasary complexity to your environment, which is what Nutanix is designed to avoid. As the various blog / technet posts explain, the issue is not a technical one, so I would recommend customers continue to run Exchange on Nutanix containers presented via NFS. The support issue is actively being discussed with Microsoft, and we are gaining some traction and hope to pressure MS into updating their support policy.
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.