VMware Cloud Community
Wolfbrother_KC
Contributor
Contributor
Jump to solution

vShield Zones In Depth CLI Documentation

Hey Guys (Carlos specifically if you read this),

I was on the vShield Zones VMTN Podcast just a bit ago and as the call was ending had a question come up. Do you have any "detailed" documentation on the CLI for the vShield AGents? I've taken a look at the CLI section of the vShield Admin guide, but was wanting a bit more detail on the usage of the commands and more detailed description of what the commands are and how they would be used in configuration or troubleshooting. For example, wondering what the esx-watchdog is all about.

Thanks,

Lane Leverett

Reply
0 Kudos
1 Solution

Accepted Solutions
carlosVSZ
VMware Employee
VMware Employee
Jump to solution

At this time the Administration guide is the only document that goes over the CLI. As you can see from the Admin guide, several CLI commands have been deprecated or the functionality has moved to the GUI. The CLI and documentation will be updated with the next update/release. Regarding the esx-watchdog, it is a feature that allows the ESX host to reboot the vShield in case it becomes unresponsive. The way it works is that the vShield is configured to to talk to an ESX host via the 'esx-watchdog' command, also a daemon is installed on each ESX host that allows them to listen to this heartbeat. Once the daemon is installed and the vShield is configured, the vShield will send a heartbeat every 3 seconds. If no heartbeat is received for 30 seconds, the vShield is rebooted.

We can go over this in more details during the call we are scheduled for.

Carlos

View solution in original post

Reply
0 Kudos
2 Replies
carlosVSZ
VMware Employee
VMware Employee
Jump to solution

At this time the Administration guide is the only document that goes over the CLI. As you can see from the Admin guide, several CLI commands have been deprecated or the functionality has moved to the GUI. The CLI and documentation will be updated with the next update/release. Regarding the esx-watchdog, it is a feature that allows the ESX host to reboot the vShield in case it becomes unresponsive. The way it works is that the vShield is configured to to talk to an ESX host via the 'esx-watchdog' command, also a daemon is installed on each ESX host that allows them to listen to this heartbeat. Once the daemon is installed and the vShield is configured, the vShield will send a heartbeat every 3 seconds. If no heartbeat is received for 30 seconds, the vShield is rebooted.

We can go over this in more details during the call we are scheduled for.

Carlos

Reply
0 Kudos
Wolfbrother_KC
Contributor
Contributor
Jump to solution

Thanks Carlos! Exactly what I was looking for and we can go into more depth on the call. Thanks!

Reply
0 Kudos