Fortinet black logo

Handbook

diagnose wad

6.0.0
Copy Link
Copy Doc ID 4afb0436-a998-11e9-81a4-00505692583a:423997
Download PDF

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.

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 (auto-detect 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

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


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 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.

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 (auto-detect 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

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


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