All Posts

Detailed Error: [error while bootstrapping the machine [/EPHEMERAL-TEMP-VM]; unable to wait for post customization phase [guestinfo.cloudinit.antrea.manifest.download.status] : [invalid postcustomization phase: [failed] for key [guestinfo.cloudinit.antrea.manifest.download.status] for vm [EPHEMERAL-TEMP-VM] due to :[<13>Jul 17 12:44:36 test1@System/administrator: + wget -O /root/v1.6.1-antrea.yaml.template <13>Jul 17 12:44:36 test1@System/administrator: --2023-07-17 12:44:36-- <13>Jul 17 12:44:36 test1@System/administrator: Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.111.133, 185.199.108.133, ... <13>Jul 17 12:44:36 test1@System/administrator: Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected. <13>Jul 17 12:44:36 test1@System/administrator: HTTP request sent, awaiting response...  

Symptoms Attempts to upload the Tanzu Mission Control Self-Managed ISO file fail for any reason. Diagnosis The TMC-SM solution is bundled into a single ISO file. The size of this file may present challenges to upload via the browser in some environments. Alternatively, the ISO may be transferred to the Installer VM and mounted directly from there. There are some changes to the "Deploy Installer VM" section of the Installation Guide when following this guide. Skip the step named "Attach the Solution Add-On ISO to the VM" Skip this command when preparing the VM # mount /dev/sr0 /mnt/cdrom -t udf -o ro Solution Open the Tenant UI for Cloud Provider of the Solutions Organization. Browse to the TMC-SM Installer vApp. Browse to the Photon OS VM in the vApp. Browse to Hardware -> Hard Disks. Edit the disks and add a new 64 GB disk. SSH into the TMC-SM Installer VM. Confirm the new disk is mounted as /dev/sdb # fdisk -l /dev/sdb Format the new disk and mount it to /solutions. Replace /dev/sdb with the appropriate name if needed. # sfdisk /dev/sdb <<EOF 2048,67108864 ; EOF # mkfs.ext4 /dev/sdb1 # mkdir /solutions # echo "/dev/sdb1 /solutions ext4 defaults 1 3" >> /etc/fstab # mount /solutions Confirm that `/solutions` is mounted with 32GB of space # df -h /solutions Filesystem Size Used Avail Use% Mounted on /dev/sdb1 32G 0 24G 0% /solutions Transfer the ISO to the TMC-SM Installer using SCP or other tools scp vmware-vcd-tmc-0.1.0-21897297.iso root@192.168.116.130:/solutions Mount the solution ISO to the existing /mnt/cdrom directory mount /solutions/vmware-vcd-tmc-0.1.0-21897297.iso /mnt/cdrom -t udf -o ro The solution ISO is now mounted and ready to use. There are no other changes to be made to the Installation Guide. Proceed to the "Create a self-signed certificate authority" section.    

Introduction The TMC Self-Managed VCD solution has a CLI for manual or automated access. The configuration steps may vary from the TMC documentation because they include some VCD specific information. All other CLI commands should be the same. Prerequisites CA used for TMC-SM services - Not required if you used an external certificate authority CA used for VCD - Not required if you used an external certificate authority TMC DNS zone (e.g.; tmc.slz.vcd.local) VCD hostname (e.g.; vcd.local) VCD OIDC Client ID - This can be retrieved from the Cloud Director Provider UI VCD tenant organization name (e.g.; company) VCD API Token - This should be created for a user that has the `tmc:admin` or `tmc:member` role Installation Browse to the TMC-SM UI directly or through the VCD UI link Browse to "Automation center" in the lower-left corner of the screen Download the TMC CLI for your platform Follow the on-screen instructions, or take the appropriate steps, to make the `tmc` CLI available in your PATH Configuration Configure certificates You may skip this step if VCD or TMC-SM does not use self-signed certificates. Follow the appropriate steps for your OS to install the VCD and/or TMC-SM CA to your system. Alternatively, you can specify an environment variable pointing to these certificates. # mkdir $HOME/tmc-ssl # cp tmcCA.pem $HOME/tmc-ssl # cp VCD.pem $HOME/tmc-ssl # export SSL_CERT_DIR=$HOME/tmc-ssl The `tmc` CLI will use the `SSL_CERT_DIR` value to load additional trusted certificates when it is executed. Configure TMC CLI tmc login --self-managed --vcd --no-configure \ --name tmc-admin \ --vcd-org company \ --vcd-api-token 24ljsajf2j342j4ljsalfjasflj23j4lkasf \ --endpoint tmc.slz.vcd.local:443 \ --vcd-issuer-url https://vcd.local/oidc \ --vcd-oidc-client-id f14f2242-dc18-4d93-a9a9-07c39570e287 This process can be repeated with different names for multiple users or TMC-SM deployments. # tmc system context list NAME ORG ID ENDPOINT tmc-admin tmc.slz.vcd.local:443 tmc-member tmc.slz.vcd.local:443 # tmc system context use tmc-admin  

Our partner is trying to confirm we support the 5xx models in Woodford 5.2.0.0, specifically related to testing the Enhanced Firewall features. Can someone confirm the 5xx models are supported in Woodford? Thanks!

We are trying to test the Advance Threat Protection using vco58 which already has 5.2 version using Edges with 5.2 version too. We have been doing some testing but the Edge does not detect any malware.   I’ve tried to download malware files using curl on a client behind an Edge from  http://www.tekdefense.com/downloads/malware-samples/ https://www.eicar.org/download-anti-malware-testfile/  https://docs.paloaltonetworks.com/advanced-wildfire/administration/configure-advanced-wildfire-analysis/verify-wildfire-submissions/test-a-sample-malware-file   but nothing is detected by the Edge. Are we missing anything important? What is the expected behaviour?     We are using the following configuration  which enables Enhanced Firewall Services and IDS/IPS is enabled on the allowAny firewall rule.