Context-sensitive command whitelisting for centralized troubleshooting tool
View Patent ↗Some embodiments provide a method for troubleshooting a virtual network that is implemented across a plurality of computing devices. The method provides a command line interface (CLI) for receiving and executing commands for debugging and monitoring the virtual network. Each command is for communicating with a set of the computing devices in order to monitor a network service being provided by the set of computing devices. The CLI operates in multiple different contexts for monitoring multiple different types of network services. While the CLI is operating in a particular context for a particular type of network service, the method receives a command comprising a set of identifiers. The method determines the validity of the received command under the particular context. When the received command is valid under the particular context, the method transmits data to a computing device identified by the received command.
1. A method for troubleshooting a distributed logical resource that is implemented by a plurality of physical endpoints, the method comprising:
receiving, through a unified command line interface (CLI) for display on a display screen and for managing the distributed logical resource (DLR), a command for the DLR;
identifying a set of different physical endpoints that implement the DLR;
for each identified physical endpoint, translating the command to a format specific to the physical endpoint for transmission to the physical endpoint; and
to troubleshoot the DLR, providing a presentation of data collected in response to the translated commands from each of the physical endpoints.
2. The method of claim 1 , wherein the collected data comprises (i) a first set of configuration data received from a configuration database that defines the desired configuration of the DLR and (ii) a second set of configuration data that defines the actual configuration of the DLR, wherein the presentation comprises a discrepancy between the first set of configuration data and the second set of configuration data.
3. The method of claim 1 , wherein the collected data comprises status data associated with at least one service rule enforced by at least one physical endpoint for the DLR.
4. The method of claim 3 , wherein the service rule is a firewall rule.
5. The method of claim 1 , wherein the collected data comprises a set of statistics regarding packets being accepted and rejected by at least one physical endpoint for the DLR.
6. The method of claim 1 , wherein the collected data comprises a set of eligible destination addresses for the DLR that are dispatched by at least one physical endpoint.
7. The method of claim 6 , wherein the collected data further comprises a set of statistics regarding packets being dispatched to a set of addresses that serve as eligible next-hop destinations of the DLR.
8. The method of claim 1 , wherein at least a subset of the physical endpoints are part of host computers on which machines connected through the DLR execute.
9. The method of claim 8 , wherein the set of physical endpoints comprises at least one virtual network interface controller (VNIC) of a machine executing on a host computer.
10. The method of claim 1 , wherein providing the presentation comprises providing the presentation through the CLI.
11. A non-transitory machine readable medium storing a program which when executed by at least one processing unit troubleshoots a distributed logical resource that is implemented by a plurality of physical endpoints, the program comprising sets of instructions for:
receiving, through a unified command line interface (CLI) for display on a display screen and for managing the distributed logical resource (DLR), a command for the DLR;
identifying a set of different physical endpoints that implement the DLR;
for each identified physical endpoint, translating the command to a format specific to the physical endpoint for transmission to the physical endpoint; and
to troubleshoot the DLR, providing a presentation of data collected in response to the translated commands from each of the physical endpoints.
12. The non-transitory machine readable medium of claim 11 , wherein the collected data comprises (i) a first set of configuration data received from a configuration database that defines the desired configuration of the DLR and (ii) a second set of configuration data that defines the actual configuration of the DLR, wherein the presentation comprises a discrepancy between the first set of configuration data and the second set of configuration data.
13. The non-transitory machine readable medium of claim 11 , wherein the collected data comprises status data associated with at least one service rule enforced by at least one physical endpoint for the DLR.
14. The non-transitory machine readable medium of claim 13 , wherein the service rule is a firewall rule.
15. The non-transitory machine readable medium of claim 11 , wherein the collected data comprises a set of statistics regarding packets being accepted and rejected by at least one physical endpoint for the DLR.
16. The non-transitory machine readable medium of claim 11 , wherein the collected data comprises a set of eligible destination addresses for the DLR that are dispatched by at least one physical endpoint.
17. The non-transitory machine readable medium of claim 16 , wherein the collected data further comprises a set of statistics regarding packets being dispatched to a set of addresses that serve as eligible next-hop destinations of the DLR.
18. The non-transitory machine readable medium of claim 11 , wherein at least a subset of the physical endpoints are part of host computers on which machines connected through the DLR execute.
19. The non-transitory machine readable medium of claim 18 , wherein the set of physical endpoints comprises at least one virtual network interface controller (VNIC) of a machine executing on a host computer.
20. The non-transitory machine readable medium of claim 11 , wherein providing the presentation comprises providing the presentation through the CLI.