This display can be used for troubleshooting network port issues when there is a configuration change. ConnectivityĬonnectivity - display the port config list with index It will try to ping the App IP address to see if it is 'Up', it will get the DHCP info of the application, and iptable rules related to the application. Besides the above information, it gets more networking information from the application. For example, if the app name is 'cluster-k3s-2-agent1', one can use 'app/agent' to query. The 'app-string>' is a subset of the App name string regardless of cases. If the '/' is supplied in the command, it will display the specific user application with more detail information. For each application, it displays the App number, UUID, network bridge information, status in terms of boot time, CPU and memory, it also displays the VNC and App log settings. If the command is issued without the '/', it will display all the user (or DomU) applications running on the device. AppĪpp - to display all the app or one specific appĪpp/iot - display a specific app, which app name has substring of iot in more detail This '/etc/hosts' is in the EdgeView container, and not in EVE device's host and not in other EVE containers. This can be useful if there is no DNS entry for the hostname and the user knows the static mapping. The 'addhost' command adds one entry of specified hostname to IP address mapping into the EdgeView container's '/etc/hosts' for. AddhostĪddhost/host-name/host-IP - to add a host entry in EdgeView container's /etc/hosts file The filter string can be 'raw', 'filter', 'nat' or 'mangle'. To see a subset on iptables, use the filter string. It will display the access list for running ACL and also configured ACL of the EVE device.

AclĪcl - to display all filters of running and configured ACL The EdgeView networking related commands are the items printed from the '-h' output:

Users just need to insert the '-inst ' if the EdgeView session is a multi-instance type. In this document, the instance-ID will not be used in the command descriptions. The above command uses the 'instance 2' for EdgeView session to the device to query for the routes on the system. For the multi-instance session, the user needs to supply the 'instance ID' when issuing EdgeView command, for example with the above 'edgeview.sh' script, an instance number is needed: The multi-instance case is used when there is a need for multiple users to access the device or applications at the same time. When the EdgeView is started based on the configuration on the controller, it can be a single instance or multiple instance session. The rest of this document will have more detailed information on each of the EdgeView commands. flow/sport=53 - display all the ip flow matches source port of 53 flow/10.1.0.2 - display all the ip flow matches ip address of 10.1.0.2 log/search-pattern pub/ įor more detail help on EdgeView commands, see įor help on a specific command, for example on 'flow' (assume it's a multiple instance, need to specify '-inst 1'):įlow - display ip flow information in the kernel search pattern e.g.

edgeview.sh, your script name may vary) with the '-h' or '-help', it will display the output like:Įve-edgeview query options: