Diagnose commands for WAN Optimization
The following get and diagnose commands are available for troubleshooting WAN optimization, web cache, explicit proxy and WCCP.
get test {wad | wccpd} <test_level>
Display usage information about WAN optimization, explicit proxy, web cache, and WCCP applications. Use <test_level> to display different information.
get test wad <test_level> get test wccpd <test_level>
| Variable | Description |
| wad | Display information about WAN optimization, web caching, the explicit web proxy, and the explicit FTP proxy. |
| wccpd | Display information about the WCCP application. |
Examples
Enter the following command to display WAN optimization tunnel protocol statistics. The http tunnel and tcp tunnel parts of the command output below shows that WAN optimization has been processing HTTP and TCP packets.
get test wad 1
WAD manager process status: pid=113 n_workers=1 ndebug_workers=0 Enter the following command to display all test options:
get test wad
WAD process 82 test usage:
1: display process status 2: display total memory usage.
99: restart all WAD processes 1000: List all WAD processes.
1001: dispaly debug level name and values 1002: dispaly status of WANOpt storages 1068: Enable debug for all WAD workers.
1069: Disable debug for all WAD workers.
2yxx: Set No. xx process of type y as diagnosis process. 3: display all fix-sized advanced memory stats
4: display all fix-sized advanced memory stats in details
500000..599999: cmem bucket stats (599999 for usage)
800..899: mem_diag commands (800 for help & usage)
800000..899999: mem_diag commands with 1 arg (800 for help & usage) 80000000..89999999: mem_diag commands with 2 args (800 for help & usage) 60: show debug stats.
diagnose wad
61: discard all wad debug info that is currently pending
62xxx: set xxxM maximum ouput buffer size for WAD debug. 0, set back to default.
68: Enable process debug
69: Disable process debug
98: gracefully stopping WAD process
9xx: Set xx workers(0: default based on user configuration.)
diagnose wad
Display diagnostic information about the WAN optimization daemon (wad).
diagnose wad console-log {disable | enable) diagnose wad debug-url {disable | enable)
diagnose wad filter {clear | dport | dst | list | negate | protocol | sport | src | vd} diagnose wad history {clear | list} diagnose wad session {clear | list}
diagnose wad stats {cache | cifs | clear | crypto | ftp | http | list | mapi | mem | scan | scripts | summary | tcp | tunnel}
diagnose wad user {clear | list} diagnose wad tunnel {clear | list}1
diagnose wad webcache {clear | list} {10min | hour | day | 30days}
| Variable | Description |
| console-log | Enable or disable displaying WAN optimization log messages on the CLI console. |
| filter | Set a filter for listing WAN optimization daemon sessions or tunnels. clear reset or clear the current log filter settings. dport enter the destination port range to filter by. dst enter the destination address range to filter by.
list display the current log filter settings |
| history | Display statistics for one or more WAN optimization protocols for a specified period of time (the last 10 minutes, hour, day or 30 days). |
| session | Display diagnostics for WAN optimization sessions or clear active sessions. |
| stats | Display statistics for various parts of WAN optimization such as cache statistics, CIFS statistics, MAPI statistics, HTTP statistics, tunnel statistics etc. You can also clear WAN optimization statistics and display a summary. |
| tunnel | Display diagnostic information for one or all active WAN optimization tunnels. Clear all active tunnels. Clear all active tunnels. |
| webcache | Display web cache activity for the specified time period. |
wad
Example diagnose wad tunnel list
Enter the following command to list all of the running WAN optimization tunnels and display information about each one. The command output shows 10 tunnels all created by peer-to-peer WAN optimization rules (autodetect set to off).
diagnose wad tunnel list
Tunnel: id=100 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=100 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=348 bytes_out=384
Tunnel: id=99 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=99 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=348 bytes_out=384
Tunnel: id=98 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=98 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=348 bytes_out=384
Tunnel: id=39 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=39 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1068 bytes_out=1104
Tunnel: id=7 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=7 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
Tunnel: id=8 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=8 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
Tunnel: id=5 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=5 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
Tunnel: id=4 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=4 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
diagnose wad
Tunnel: id=1 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=1 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
Tunnel: id=2 type=manual vd=0 shared=no uses=0 state=3
peer name=Web_servers id=2 ip=172.20.120.141
SSL-secured-tunnel=no auth-grp= bytes_in=1228 bytes_out=1264
Tunnels total=10 manual=10 auto=0
Example diagnose wad webcache list
This following command displays the web caching stats for the last 10 minutes of activity. The information displayed is divided into 20 slots and each slot contains stats for 30 seconds:
20 * 30 seconds = 600 seconds = 10 minutes
diagnose wad webcache list 10min web cache history vd=0 period=last 10min
The first 20 slots are for HTTP requests in the last 10 minutes. Each slot of stats has four numbers, which is the total number of HTTP requests, the number of cacheable HTTP requests, the number of HTTP requests that are processed by the web cache (hits), and the number of HTTP requests that are processed without checking the web cache (bypass). There are many reasons that a HTTP request may bypass web cache.
| total cacheable hits bypass
———— ————- ———— ————- |
||
| 36 | 10 3 | 1 |
| 128 | 92 1 | 10 |
| 168 | 97 2 | 3 |
| 79 | 56 0 | 3 |
| 106 | 64 5 | 3 |
| 180 | 118 6 | 11 |
| 88 | 53 7 | 3 |
| 80 | 43 4 | 4 |
| 107 | 44 9 | 2 |
| 84 | 12 0 | 2 |
| 228 | 139 52 | 10 |
| 32 | 2 0 | 5 |
| 191 | 88 13 | 7 |
| 135 | 25 40 | 3 |
| 48 | 10 0 | 8 |
| 193 | 13 7 | 7 |
| 67 | 31 1 | 2 |
| 109 35 24 | 6 | |
| 117 36 10 | 5 | |
| 22 0 0 | 4 | |
wacs
The following slots are for video requests in the last 10 minutes. Each slot has two numbers for each 30 seconds: total number of video requests, and the number of video requests that are processing using cached data.
video total video hit
———— ————-
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
The following 20 slots are for traffic details in last 10 minutes. Each slot has four numbers for 30 seconds each.
— LAN — — WAN —
bytes_in bytes_out bytes_in bytes_out
———— ————- ———— ————-
34360 150261 141086 32347
105408 861863 858501 100670
128359 1365919 1411849 127341
60103 602813 818075 59967
105867 1213192 1463736 97489
154961 1434784 1344911 158667
73967 370275 369847 70626
129327 602834 592399 123676
115719 663446 799445 111262
58151 724993 631721 59989
175681 2092925 1092556 166212
37805 33042 41528 37779
183686 1255118 1114646 172371
106125 904178 807152 81520
66147 473983 543507 66782
170451 1289530 1201639 165540
69196 544559 865370 68446
134142 579605 821430 132113
96895 668037 730633 89872
59576 248734 164002 59448 diagnose wacs
Display diagnostic information for the web cache database daemon (wacs).
diagnose wacs clear diagnose wacs recents diagnose wacs restart diagnose wacs stats
diagnose wadbd
| Variable | Description |
| clear | Remove all entries from the web cache database. |
| recents | Display recent web cache database activity. |
| restart | Restart the web cache daemon and reset statistics. |
| stats | Display web cache statistics. |
diagnose wadbd
Display diagnostic information for the WAN optimization database daemon (waddb).
diagnose wadbd {check | clear | recents | restart | stats}
| Variable | Description |
| check | Check WAN optimization database integrity. |
| clear | Remove all entries from the WAN optimization database. |
| recents | Display recent WAN optimization database activity. |
| restart | Restart the WAN optimization daemon and reset statistics. |
| stats | Display WAN optimization statistics. |
diagnose debug application {wad | wccpd} [<debug_level>]
View or set the debug level for displaying WAN optimization and web cache-related daemon debug messages. Include a <debug_level> to change the debug level. Leave the <debug_level> out to display the current debug level. Default debug level is 0.
diagnose debug application wad [<debug_level>] diagnose debug application wccpd [<debug_level>]
| Variable | Description |
| wad | Set the debug level for the WAN optimization daemon. |
| wccpd | Set the debug level for the WCCP daemon. |
test application wad 2200
diagnose test application wad 2200
The debug level 2200 switches the debug to explicit proxy mode. You have to enter this debug level first. After that you have to type the command again with a different debug level to check the different explicit proxy statistics. To list what each debug level shows, follow these steps in any FortiGate device:
- Enable explicit proxy globally and in one interface, to start the wad process. If the wad process is not running, you cannot list the options.
- Once the wad process starts, type:
diagnose test application wad 2200 diagnose test application wad ///// Do not type any debug level value to list all the options.
This is the output you will get:
# diagnose test application wad 2200
Set diagnosis process: type=wanopt index=0 pid=114 # diagnose test application wad WAD process 114 test usage:
1: display process status
2: display total memory usage
99: restart all WAD processes
1000: List all WAD processes
1001: dispaly debug level name and values
1002: dispaly status of WANOpt storages
1068: Enable debug for all WAD workers
1069: Disable debug for all WAD workers
2yxx: Set No. xx process of type y as diagnosis process
3: display all fix-sized advanced memory stats
4: display all fix-sized advanced memory stats in details
500000..599999: cmem bucket stats (599999 for usage)
800..899: mem_diag commands (800 for help & usage)
800000..899999: mem_diag commands with 1 arg (800 for help & usage)
80000000..89999999: mem_diag commands with 2 args (800 for help & usage)
60: show debug stats
61: discard all wad debug info that is currently pending
62xxx: set xxxM maximum ouput buffer size for WAD debug (0: set back to default)
68: Enable process debug
69: Disable process debug
98: gracefully stopping WAD process
20: display all listeners 21: display TCP port info
22: display SSL stats
23: flush SSL stats
24: display SSL mem stats
70: display av memory usage
71xxxx: set xxxxMiB maximum AV memory (0: set back to default)
72: toggle av memory protection
73: toggle AV conserve mode (for debug purpose)
90: set to test disk failure
91: unset to test disk failure
92: trigger a disk failure event
100: display explicit proxy settings
101: display firewall policies
102: display security profile mapping for regular firewall policy
diagnose test application wad 2200
103: display Web proxy forwarding server and group
104: display DNS stats
105: display proxy redirection scan stats
106: list all used fqdns
107: list all firewall address
110: display current web proxy users
111: flush current web proxy users
112: display current web proxy user summary
113: display WAD fsso state
114: display HTTP digest stats
115: display URL patterns list of cache exemption or forward server
116: toggle dumping URL when daemon crashes
120: display Web Cache stats
121: flush Web Cache stats
122: flush idle Web cache objects
123: display web cache cache sessions
130: display ftpproxy stats
131: clear ftpproxy stats
132: list all current ftpproxy sessions
133: display all catched webfilter profiles
200: display WANopt profiles
201: display all peers
202: display video cache rules (patterns)
203: display all ssl servers
210: toggle disk-based byte-cache
211: toggle memory-based byte-cache
212: toggle cifs read-ahead
221: display tunnel protocol stats
222: flush tunnel protocol stats
223: display http protocol stats
224: flush http protocol stats
225: display cifs protocol stats
226: flush cifs protocol stats
227: display ftp protocol stats
228: flush ftp protocol stats
229: display mapi protocol stats
230: flush mapi protocol stats
231: display tcp protocol stats
232: flush tcp protocol stats
233: display all protocols stats
234: flush all protocols stats
240: display WAD tunnel stats
241: display tunnel compressor state
242: flush tunnel compressor stats
243: display Byte Cache DB state
244: flush Byte Cache DB stats
245: display Web Cache DB state
246: flush Web Cache DB stats
247: display cache state
248: flush cache stats
249: display memory cache state
250: flush memory cache stats
261yxxx: set xxx concurrent Web Cache session for object storage y
262yxxx: set xxxK(32K, 64K,…) unconfirmed write/read size per Web Cache object for object storage y
263yxxxx: set xxxxK maximum ouput buffer size for object storage y
test application wad 2200
264yxx: set lookup lowmark (only if more to define busy status) to be xx for object storage y
265yxxx: set xxxK maximum ouput buffer size for byte storage y
266yxxx: set number of buffered add requests to be xxx for byte storage y
267yxxxx: set number of buffered query requests to be xxxx for byte storage y
268yxxxxx: set number of concurrent query requests to be xxxxx for byte storage y