Learn Editor: Update troubleshoot-resource-bridge.md

Author: alt-key

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

@@ -13,25 +13,32 @@ This article provides information on troubleshooting and resolving issues that c
 
 ### Logs collection
 
-For issues encountered with Arc resource bridge, collect logs for further investigation using the Azure CLI [`az arcappliance logs`](/cli/azure/arcappliance/logs) command. This command needs to be run from the same management machine that was used to run commands to deploy the Arc resource bridge. If there's a problem collecting logs, most likely the management machine is unable to reach the Appliance VM, and the network administrator needs to allow communication between the management machine to the Appliance VM. You can collect the Arc resource bridge logs by passing either the appliance VM IP or the kubeconfig in the logs command.
+For issues encountered with Arc resource bridge, collect logs for further investigation using the Azure CLI [`az arcappliance logs`](/cli/azure/arcappliance/logs) command. This command needs to be run from the same management machine that was used to run commands to deploy the Arc resource bridge. If you are using a different machine to collect logs, you will need to run the `az arcappliance get-credentials` command first before collecting logs.
 
-An example to collect Arc resource bridge logs on VMware using the appliance VM IP address: 
+If there's a problem collecting logs, most likely the management machine is unable to reach the Appliance VM, and the network administrator needs to allow SSH communication between the management machine to the Appliance VM on TCP port 22. 
+
+You can collect the Arc resource bridge logs by passing either the appliance VM IP or the kubeconfig in the logs command.
+
+To collect Arc resource bridge logs on VMware using the appliance VM IP address: 
 
    ```azurecli
-   az arcappliance logs vmware --ip 192.168.0.2 --username usrnm1@domain --password vsexample --address vcenter.address
+   az arcappliance logs vmware --ip <appliance VM IP> --username <vSphere username> --password <vSphere password> --address <vCenter address> --out-dir <path to output directory>
    ```
 
-An example to collect Arc resource bridge logs for Azure Stack HCI using the appliance VM IP address: 
+To collect Arc resource bridge logs for Azure Stack HCI using the appliance VM IP address: 
 
    ```azurecli
-   az arcappliance logs hci --ip 192.168.02 --cloudagent 192.168.05 --loginconfigfile c:\clusterstorage\moc\workingdir\kvatoken.tok
+   az arcappliance logs hci --ip <appliance VM IP> --cloudagent <cloud agent service IP/FQDN> --loginconfigfile <file path of kvatoken.tok> 
    ```
 
-If you are unsure of your appliance VM IP, there is also the option to use the kubeconfig. You can retrieve the kubeconfig by running the [get-credentials command](/cli/azure/arcappliance) then run the logs command. 
+If you are unsure of your appliance VM IP, there is also the option to use the kubeconfig. You can retrieve the kubeconfig by running the [get-credentials command](/cli/azure/arcappliance) then run the logs command.
+
+To retrieve the kubeconfig and log key then collect logs for Arc-enabled VMware from a different machine than the one used to deploy Arc resource bridge for Arc-enabled VMware:
 
    ```azurecli
-   az arcappliance get-credentials --resource-group my-rg-01 --name arb-name --credentials-dir c:\user\arbcreds
-   az arcappliance logs vmware --kubeconfig c:\user\arbcreds\kubeconfig --username usrnm1@domain --password vsexample --address vcenter.address
+az account set -s <subscription id>
+az arcappliance get-credentials -n <Arc resource bridge name> -g <resource group name> 
+az arcappliance logs vmware --kubeconfig kubeconfig --out-dir <path to specified output directory>
    ```
 
 ### Arc resource bridge is offline