/images/logo.png

Welcome to 288clouds

288clouds is a personal blog focused on virtualization and cloud technologies.

The views and opinions expressed on this blog are my own and do not reflect the views and opinions of my employer (VMware).

Carbon Black Cloud Sensor Install on a Linux Machine

Let’s manually install a Carbon Black Cloud (CBC) sensor on a CentOS 7 machine! Prerequisites Carbon Black Cloud access (Note: the environment I’m using is Carbon Black Cloud Enterprise) CentOS 7 machine (can be Ubuntu as well) Process Overview Download the Carbon Black Cloud sensor kit on the linux machine. Install the sensor via terminal. Verify that the endpoint shows up in Carbon Black Cloud. Demo / Example Download Carbon Black Cloud Sensor Kit Log into Carbon Black Cloud from the linux machine where you want to install the sensor.

Remote VCDX Defense Tips

Remote VCDX defense option has normally been reserved for candidates attempting to achieve their second, third, or even fourth VCDX. But in the midst of the COVID-19 pandemic, having a remote VCDX defense seems to be a possibility for candidates trying to receive their first VCDX in some cases. I got my VCDX in January 2020 through a remote defense, and I thought it may be valuable to share what I’ve used during my defense for candidates who may have remote defenses in the future.

Considerations When Using Layer 2 Bridges for NSX-V to NSX-T Migration

I recently had a customer who asked for some general feedback on their high-level plan to migrate from NSX-V to NSX-T using layer 2 bridges. Although every environment is different and the details of migration procedures should be tailored to each environment, I thought I’d share the general guidance I gave to this customer in case there are some points here that may be transferrable to other similar NSX-V to NSX-T migration plans.

vRA 8 + NSX-T Blog Series Part 6: vRA 8 Blueprint with On-demand Security Group

You can create a vRA 8 blueprint to deploy machines and place them in an on-demand NSX-T security group. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: logical network(s) configured Process Overview Create or edit a network profile. Select which existing security groups you’d like to use.

vRA 8 + NSX-T Blog Series Part 5: vRA 8 Blueprint with Existing Security Group (segment port tag)

You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) by putting tags on the machine segment port(s). Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: Security group(s) configured Process Overview Configure Membership Criteria of the existing security group(s).

vRA 8 + NSX-T Blog Series Part 4: vRA 8 Blueprint with Existing Security Group (vRA tag)

You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) using vRA tags. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: security group(s) configured Process Overview Create a tag on the existing security group(s).

vRA 8 + NSX-T Blog Series Part 3: vRA 8 Blueprint with Existing Security Group (network profile)

You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) using a network profile. Note that with this method, however, any and all security groups that you select in the network profile will be applied to the machines. If you have multiple machines in a blueprint and want to specify which security group each machine should use, then use vRA tag or segment port tag (refer to series part 4 & 5 for those methods).

Customize Machine and On-demand Network Names

vRA 8 blueprint gives random names and numbers to the VMs and on-demand NSX-T networks deployed if you do not specify a naming convention. This blog will cover how you can customize the names of your VMs and on-demand NSX-T networks when they are deployed from a vRA 8 blueprint. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8:

vRA 8 + NSX-T Blog Series Part 2: vRA 8 Blueprint with On-demand Routed NSX-T Networks

You can create a vRA 8 blueprint to create an on-demand routed NSX-T network and deploy machines connected to these newly created network. When you tell the blueprint to create an on-demand routed NSX-T network, vRA 8 actually creates a tier-1 gateway that connects to the pre-existing tier-0 gateway. It then creates an on-demand network and attaches it to the tier-1 gateway that it has created. Demo Product Versions vSphere 6.

vRA 8 + NSX-T Blog Series Part 1: vRA 8 Blueprint with Existing NSX-T Networks

You can create a vRA 8 blueprint to deploy machines on existing NSX-T networks. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: logical router (tier-0 or tier-1) configured logical segment(s) attached to a logical router Process Overview Set up the existing networks with IP ranges you want to use for the machines.