Welcome to Mohamed Fouad blog

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

 VMware vRealize Operations 8.x reboot sequence Rebooting the cluster means the services will be down until the cluster boots back up again. Oower off in the below order 1.       Remote Collectors 2.       Data Nodes 3.       Replica node 4.       Master node Then you will need to power on in reverse order: 1.       Master  node 2.       Replica  node 3.       Data  Nodes 4.       Remote collectors

  Environment setup : Three Workspace one nodes per site and have AVI load balancer with external Database. Here are the steps for testing that failover: Change the LB to point to the DR site. You will need to clear caches in the primary datacenter by following the steps listed here: https://docs.vmware.com/en/VMware-Workspace-ONE-Access/21.08/workspace_one_access_install/GUID-A794E38F-974E-48B9-8BFF-3737472BC1BB.html Restart all connector services from both the primary and DR site Stop the horizon-workspace service on the primary nodes. As we can only have 1 read/write cluster on at a time. Promote the DR site to the primary by editing: /usr/local/horizon/conf/runtime-config.properties in the following ways on each of the nodes: read.only.service=true to read.only.service=false cache.service.type=ehcache to cache.service.type=rds Save Restart the horizon-workspace server on each node in DR. restart the connectors again (to e

  How to deploy an OVA in Cloud Director Yesterday I was in a call with a customer and we discussed uploading OVA’s into Cloud Director. I said sure that is no problem at all. Well then I started thinking how are you supposed to deploy an OVA in Cloud Director because I do not even remember how this is done. So I opened up Cloud Director and tried it for myself. I decided to make this blog post along the way to show you how to deploy an OVA in Cloud Director. As an added bonus I will also show you how to upload an OVA to the catalog. This way I can deploy the OVA over and over again. Environment information Cloud director 10.3 OVA How to deploy an OVA in Cloud Director In Cloud director I opened up the Applications section and selected “NEW” I am deploying an OVA so I selected “Add vApp From OVF”. In the screenshot below you can see all the steps involved with (in my case) deploying and customising the Usagemeter. Options to customise are for instance: Network settings, vApp naming, Li

  It’s a great command reference when you working with certificate issues   And I will add this section when you working with STS certificate : https://kb.vmware.com/s/article/79248  - Check STS Certificate expiry on VCSA & Windows VC https://kb.vmware.com/s/article/76719  - Replace STS Certificate on VCSA https://kb.vmware.com/s/article/79263  - Replace STS Certificate on Windows VC If you need to get a quick summary for all Cert use a bellow command #for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list | grep -v TRUSTED_ROOT_CRLS); do echo "[*] Store :" $store; /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store $store --text | grep -ie "Alias" -ie "Not After";done Check this pdf https://file.io/vCxR7K4vms0q

  ESXTOP not displaying properly? I’ve seen quite a few posts lately about ESXTOP not displaying properly. Long story short, esxtop does not display the interactive UI and displays the CSV output instead. If your esxtop looks like this, then you need to change the terminal declaration to something like xterm. Notice here (red rectangle), how the terminal is set to xterm-256color.   You can change the terminal declaration from the cli, but this is not persistent through sessions. To do this simply type “ TERM=xterm “. To display the current terminal declaration type “ echo $TERM ”     This will display esxtop interface properly.               If you want this change to persist, just change your favorite terminal settings to xterm from its current setting. For example, I use my Mac’s terminal to ssh into my lab, the terminal is set to xterm-256color, which causes the display issue. So, I just opened the terminal preferences and changed the declaration to xterm. By default, putty identifi

    Symptoms Host has lost connection with the data store. In the vmkernel.log you see message similar to: 2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397) [HB state abcdef02 offset 3616768 gen 33 stampUS 17643062981621 uuid 5783c299-eea160ad-aae8-e0db550386c6 jrnl <FB 0> drv 14.61 lockImpl 4] 2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: FSAts: 1498: Denying reservation access on an ATS-only vol 'SYN01' 2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: HBX: 2227: ATS-Only VMFS volume 'SYN01' is not mounted. This host does not support ATS, or ATS ini tialization failed. 2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 56f52615-c7d247e4-e688-90b11c26 8865: Not supported 2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)Vol3: 3147: Failed to get object 28 type 1 uuid 56f52615-c7d247e4-e688-90b11c268865 FD 0 gen 0 :Not support ed 2017-01-31T20:49:15.992Z cpu13:34

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the device.   Resolution Depending on the device cond