This document describes some commonly used CLI (Command Line Interface) commands for Cisco Finesse.
In order to collect the logs for the majority of application issues, enter this commmand into the CLI:
file get activelog desktop recurs compress
The date/time range is specified with relative or absolute time. For example:
file get activelog desktop recurs compress reltime hours 2
file get activelog desktop recurs compress abstime 00:00:03/17/13 23:59:03/19/13
Enter this command into the CLI in order to perform a packet capture:
utils network capture file <filename> count 1000000
There are additional filters, but when you set the count to the maximum (1000000), it delivers the best results. This is the packet count, so it captures 1000000 packets and then stops.
The file is saved in platform/cli/<filename>.cap. In order to collect the file, enter this command:
file get activelog platform/cli/<filename>.cap
Enter this command into the CLI in order to perform a ping:
utils network ping
Enter this command into the CLI in order to perform a traceroute:
utils network traceroute
Enter this command into the CLI in order to perform a Domain Name System (DNS) lookup:
utils network host
Enter this command into the CLI in order to look up the version/build number, date/time, CPU, memory, and disk utilization:
show status
Enter this command into the CLI in order to ensure that the DNS is configured or get basic network information:
show network eth0
Enter this command into the CLI in order to view the overall Virtual Origin Server (VOS) process statuses (this command does not signify if Finesse is in service):
utils service list
Important processes to Finesse are Cisco Tomcat and Cisco Finesse Notification Service.
Enter this command into the CLI in order to ensure that the Network Time Protocol (NTP) is properly synched (this is a requirement of Finesse):
utils ntp status
Enter this command into the CLI in order to view the port utilization, or "netstat" equivalent:
show tech network sockets