Connecting Cloud Innovators: Building Community at .NEXT 2024
I'm looking at using Cisco IP Communicator on a Horizon View persistant desktop and would like some input on what others suggest for voice traffic prioritization. Some options I see: 1> Saying "It's on 10GB, it's fine" 2> Using a separate network (port group and VLAN) specifically for voice on a VSS with 1GB uplinks 3> Using a separate network (port group and VLAN) specifically for voice on a VDS with 1GB uplinks pinned to the port group 4> Using a separate network (port group and VLAN) specifically for voice on a VDS with 10GB uplinks 5> Using a separate network (port group and VLAN) specifically for voice on a VDS with 10GB uplinks and traffic prioritization on the TOR switches for the voice VLAN using IP Precedence (differentiated services code point [dscp]) audio priority. Any thoughts community?
I have 3 x 3000 series node each with 256GBs of RAM, and 1 cluster. - 7.2TB Total SSD Flash (2.4TBx3 nodes)- 12TB Usable HDD (before de-duplication/compression)- 2.6GHz/20 Cores, 6 Physical CPUs: 60 Total cores- 768GB Total memory We are running pure Acropolis. The monster VM workload is a Progress database that is 7TB in size and has 200GB RAM allocated to it. We are setting this up as a PoC to migrate off a standalone ESXi host with a Violin all flash array. Previously, the VM on VMware was only pushing 12,000 IOPs. What should we be doing to optimize the performance for this VM? Multiple virtual scsi adapters? Also, is there a way to see if the working set is exceeding the node cache capability?
I'm putting together a design for a 3 node cluster with the 6000 series nodes. The first block is 6235-G4, the second block, I'm a bit confused. I could get another identicle block with 1 node ( 6135-G4), but there is also the option of getting a 6135C, which is single socket, less RAM, smaller SSD and crappier CPU. It's cheaper and will make the min 3 node cluster, but I'm wondering what kind of performance hit it will have for the overall solution. Am I better off getting a 6135-G4 and being done with it?
We have a single 3 node 1350 with starter licensing running VMware vSphere. Is it possible to configure replication to another non-NDFS datastore with any available built in tools or processes? What would be the best method that does not incur additional costs. In this sort of instance, would vSphere replication make sense backup to another datastore?
With the release of cloud connect, you can backup to Amazon using a CVM running as an instance. Is the CVM cloud agnostic? Can we run it in other environments, such as vCloud Air, Azure or partner vClouds?
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.