Server 2012 R1/R2 Creating a Network Team and enable Jumbo Frames

Server 2012 now supports NIC teaming, previously you could use HP tools to achieve this in Server 2008 R2 and below, but officially it was never supported by Microsoft. Network teaming Setting up a NIC team in Server 2012 is really simple. You just need to know where your Server is plugged into first on … Continue reading Server 2012 R1/R2 Creating a Network Team and enable Jumbo Frames

VMware ESXi 5.5 u1 PSOD on HP ProLiant G7 PSOD

For the past few weeks I’ve been working with a customer to resolve an issue with a re-purposed host where it PSOD every week. Issue: We installed a new HP Gen8 server as a production host in their main site, installed with VMware ESX 5.5 u1, and then took the HP G7 ESXi 5 box … Continue reading VMware ESXi 5.5 u1 PSOD on HP ProLiant G7 PSOD

helm header image

Helm upgrade –reuse-values Fails with Nil Pointer Error After a Chart Version Bump

If you have been running a Helm chart for a while and using –reuse-values to carry your previous configuration forward on upgrades, you may have hit an error like the one below after bumping to a new chart version: Running the same upgrade with an explicit values file works without issue: Read on to understand … Continue reading Helm upgrade –reuse-values Fails with Nil Pointer Error After a Chart Version Bump

Cisco Live Header

Bridging Old Hypervisors to Cloud Native Platforms: What You’ll Learn at Cisco Live Amsterdam

Are you planning or already facing a migration from legacy hypervisors to modern, cloud native platforms? The toughest part usually isn’t compute or storage, it’s networking. If static IPs, subnet constraints, and complex topologies are slowing you down, Cisco Live Amsterdam is the place to fix that. This year, I’m delivering two brand-new sessions focused … Continue reading Bridging Old Hypervisors to Cloud Native Platforms: What You’ll Learn at Cisco Live Amsterdam

Kubernetes Header Image

How to Increase CPU & Memory Limits and Set Node Selector for Splunk Operator on Kubernetes

The Issue When deploying a Splunk instance using the Splunk Operator on Kubernetes, the default resource limits are set to 4 CPUs and 8GB of RAM. Users often want to increase these limits to better utilize available hardware resources. Additionally, users may want to schedule the Splunk pods on a specific Kubernetes node by using … Continue reading How to Increase CPU & Memory Limits and Set Node Selector for Splunk Operator on Kubernetes