Home

Unlike NSX-V, NSX-T configuration for logging is done manually. Syslog configurations are not propagated to objects (Edge, Transport Nodes) created from the manager. (this true with the current version: NSX-T 2.5.1) Anyway, here are the steps on how to configure: Manager / Edge Nodes: SSH to the Management IP. I’m using root Switch to admin to start working with NSX CLI (cmd: su admin) Issue command: set-loggin

I was with a GSS Support today troubleshooting NSX issue on one of my engagement. He did a packet trace from ESXi hosts to see if there is traffic leaving/ entering the physical NIC which really nice. This will be helpful in establishing if the issue is somewhere in the environment or not. Here’s the command Receive: pktcap-uw –uplink vmnic0 –capture UplinkRcvKernel -o -| tcpdump-uw -nr – Send

When doing an upgrade via LCM of vRA from 8.0 to 8.0.1, you might encounter this error: Disk space on root partition (/) on VM Disk 1 (/dev/sda4) should have atleast 20 GB of free disk space. This is because initial installation of vRA only has small disk not enough for upgrade. The issue is documented in the Known Issue for vRA 8.0.1 here To resolve, WITHOUT POWERING OFF your Virtual Appliance, go to each of the vRA

Ok. This took awhile to look for so might as well blog about it. This application rule redirects ALL HTTP traffic to HTTPS using the same URI. redirect scheme https if !{ ssl_fc } To use this, you just need to create the Virtual Server that serves HTTP, attach the application rule containing the string – and youre all set 🙂 Enjoy!

Ever since they announced VMware Hackathon 4 years ago – I knew wanted to experience this first hand if given the opportunity! Fortunately, THAT opportunity came this VMworld 2019 thanks to vExpert Pro and VMware! It’s been 10 years since my last VMworld and alot has changed – with content from different VMware units (more on this on another post). One of this is unit is VMware Code which hosted gee

Some kubernetes action 🙂 I’ve just installed prometheus-grafana monitoring on my kubeadm built k8s cluster. This is the repo i used to do such: https://github.com/giantswarm/prometheus After installing, there was an error getting node metrics. The error: Get http://172.16.20.14:10255/metrics: dial tcp 172.16.20.14:10255: getsockopt: connection refused To fix this, you need to allow kubelet read-only port by spe