In this module, we will cover troubleshooting and debugging. Resetting the expert password on locally managed gateway, there are two options for that. Option one is to connect through expert mode, access this directory right here, and delete the experts_pass file. Second option is for when expert is the default shell and then you can just do the same procedure but over an SEP connection. You can use WinSCP for example, its very easy. On a centrally managed appliance, you can use the cprid_util, and delete the expert_pass file. Here are some key processes. When something doesn't work, you want to make sure that these processes are up and functioning properly, and if not, you would like to debug those processes. Starting with the Watchdog, it launches and monitors all other critical processes. If a process is down, Watchdog will bring it back up. cpd uses port 1891. It is used for many services such as installing and fetching policies. fwd is used for logging and vpnd that is used for IPsec VPN. You can refer to these sks for further information. Here are some basic commands for troubleshooting. If you want to check enforcement on a local managed gateway, you can run the configload_status command. If you want to change the default shell on appliance, you need to run this command the bashUser on. If you want to check some of the core logs, you would like to go and visit this folder right here, Is-la/logs folder. Check load per CPU core, it can run the mpstat command. Check the number of connections in memory with #fw ctl pstat. Check memory and a lot more information with the vmstat command. You can display the file system usage with the df command, and you can mount SD card or USB with the mount command. If you want to run CPinfo, you can either run it through the webUI or through the actual CLI. You can still run Dmesg and if you want to check the policy status, you can just run fw stat. Here are some of the most common log files. Large ping, if it's over 1000 bytes, it will not pass the gateway. We can see the log here, and from the SMB webUI, I can go all the way down here to troubleshooting. Here I can go to monitor system resources and have a live map with nice timelines. I can display the routing table. I can test Cloud services ports to verify that the appliance could connect to any Cloud services. The CPinfo as I mentioned, you can just generate it straight from here. If you want to check connectivity using a ping, you can do it here. You can even do a trace route. You can perform a DNS lookup to make sure that you do have a DNS server functioning and if you want to run a packet capture, you can also run it through this web interface as well. If you want to download the driver for USB-C console, you can download it straight from here. Under support, we have some contact information and some downloads are available as well for a local manual or again, the windows driver for USB-C. This concludes this module.
