To see the number of “keepalives” sent to the other AppNav Controllers and received from the other AppNav Controllers and other statistics related to the AppNav Controller group, use the following command:

router# show service-insertion statistics appnav-controller-group
Appnav Controller Group 			: acg
Number of AppNav Controllers 			: 2
Members:
	IP Address
	21.0.0.36
	21.0.0.160
Aggregate Appnav Controller statistics
--------------------------------------
Time since statistics were last reset/cleared			: 0d 5h 47m 14s
Aggregate number of keepalives sent to ACs			: 168484
Aggregate number of keepalives received from ACs 	: 166372
Aggregate number of invalid keepalives received :
	Total 		: 0
	Incompatible ICIMP version 		: 0
	Authentication Failed 		: 0
	Stale keepalive 		: 0
	Malformed keepalive 		: 0
	Unknown keepalive 		: 0
	Inactive keepalive 		: 0
Aggregate number of times liveliness lost with ACs 			: 1
Aggregate number of times liveliness gained with ACs	: 2

To show the connections, packets, and bytes sent to each service node, use the following command:

router# show service-insertion statistics service-node
 [IP_address

To show the aggregated connections, packets, and bytes sent to each service node group, use this command:

router# show service-insertion statistics service-node-group [
NAME
]

Here is an example:

router# show service-insertion statistics service-node
Statistics for Service Node 21.0.0.149
-------------------------------------------------------
Time since statistics were last reset/cleared: 0d 18h 7m 54s
Number of probe requests sent to SN			: 326024
Number of probe responses received from SN			: 326014
Number of invalid probe responses received:
	Total		: 0
	Incompatible DMP version		: 0
	Authentication failed		: 0
	Stale response		: 0
	Malformed response		: 0
	Unknown response:		 0
Number of times liveliness lost with SN	: 0
Number of times liveliness regained with SN	:1
Cluster IPC statistics
----------------------
Time since statistics were last reset/cleared: 0d 18h 8m 24s
Number of load updates received from CMM: 4
Number of erroneous load updates: 0
Time since last load update was received: 0d 14h 32m 43s
Load stats for Service Node 21.0.0.149
---------------------------------------------
Accelerator state transition statistics
---------------------------------------
Time since Accl load stats were last cleared: 0d 18h 8m 24s
Accl		Current 			Previous			Red		Yellow			Green
tcp		GREEN 			RED			0		0			1
epm		GREEN 			RED			0		0			1
cifs		GREEN 			RED			0		0			1
mapi		GREEN 			RED			0		0			1
http		GREEN 			RED			0		0			1
video		GREEN 			RED			0		0			1
nfs		GREEN 			RED			0		0			1
ssl		YELLOW 			RED			0		1 			0
ica		RED			RED			0		0			0
Traffic distribution statistics for service node 21.0.0.149
----------------------------------------------------------
Time since distribution stats were last cleared: 0d 18h 8m 24s
Packet and byte counts
----------------------
Redirected Bytes			: 2338
Redirected Packets			: 50
Received Bytes			: 3350
Received Packets			: 50
Occurences
-----------
Initial Redirects			: 2
Initial Redirects Accepted			: 2
Initial Redirect -> Passthrough			: 0
Redirect -> Passthrough			: 0

The important statistics are as follows:

• Probe Requests: The number of heartbeats sent to the service node.
• Probe Responses: The number of heartbeats received from the service node.
• Redirected Bytes: The number of bytes redirected to the service node.
• Redirected Packets: The number of data packets redirected to the service node.
• Received Bytes: The number of bytes received from the service node.
• Received Packets: The number of data packets received from the service node.
• Initial Redirects: The number of times that the SYN packet (the first packet for requesting connection in a TCP flow) was redirected to the service node.
• Initial Redirects Accepted: The number of times that the service node decided to optimize on SYN packet.
• Initial Redirects -> Passthrough: The number of times that the service node decided to pass-through on SYN packet.
• Redirect -> Passthrough: The number of times that the service node decided to pass-through a flow after it was initially accepted for optimize (e.g. due to lack of peer).

To display statistics about the service context, use the show service-insertion statistics service-context [name] command. The output of this command displays the time spent in each FSM state by the CMM and the amount of time that each service context has been in each FSM state.

Here is an example:

Router# show service-insertion statistics service-context
Time spent in various FSM states
Converging     :       0d 0h 0m 31s
Initializing   :       0d 0h 0m 0s
Operational    :       1d 19h 27m 53s
Degraded       :       0d 0h 0m 0s
Internal Error :       0d 0h 0m 0s
Admin Disabled :       0d 0h 0m 0s
Number of entries into Converging State:      3
Number of entries into Initializing State:    1
Number of entries into Operational State:     3
Number of entries into Degraded State:        0
Number of entries into Internal Error State:  0
Number of entries into Admin Disabled State:  0

To query the flows in the flow table and to optionally filter the output by using specific criteria, use the following command:

router# show service-insertion statistics connection [[summary] | [vrf-name
 name
] [client-ip 
IP_address
] [client-port 
port_number
] [server-ip 
IP_address
] [server-port 
port_number
] [detail]]

As part of the flow query, the following information for every flow is available:

• Client IP address, client TCP port and server IP address, server TCP port number
• Service node IP address, passthrough
• VRF name

Here is an example:

router# show service-insertion statistics connection
Collecting Records. Please wait...
Client                Server                SN-IP 	VRF-Name
51.0.222.4:64234      11.0.0.3:80           21.0.0.104	br_vrf
51.0.222.4:22415      11.0.0.3:80           21.0.0.104
51.0.222.4:15264      11.0.0.3:80           21.0.0.104
51.0.222.4:37759      11.0.0.3:80           21.0.0.104
51.0.222.4:55408      11.0.11.2:23          Passthrou

If you include the detail keyword, the report also displays the following on a per flow basis:

• Presence of session (3T) or App (2T) association
• Application ID
• Peer ID

The following is an example:

router# show service-insertion statistics connection detail
Collecting Records. Please wait...
Client: 192.168.80.4:60973
Server: 192.168.180.4:135
Service Node IP: 172.16.0.2
Flow association: 2T:No,3T:No
VRF-Name:
Application ID: 0
Peer-ID: 00:21:5e:76:65:08
 
Client: 192.168.80.4:60959
Server: 192.168.180.4:1092
Service Node IP: 172.16.0.2
Flow association: 2T:Yes,3T:Yes
VRF-Name:
Application ID: 78
Peer-ID: 00:21:5e:76:65:08

If you include the summary keyword, the report displays only the number of 2T and 3T entries, the number of optimized flows, and the number of passthrough flows and the number of flow synchronization failures due to VRF config mismatch on the AppNav Controllers.

The following is an example:

router# show service-insertion statistics connection summary
Number of 2T optimized flows    = 0
Number of 3T optimized flows    = 0
Number of optimized flows       = 3
Number of pass-through flows    = 1
Flow sync failures due to vrf-mismatch = 0

You can also use the show platform software command. It works exactly the same as the show service-insertion statistics command, but it can also be used to query the flows on the standby FP.

router# show platform software appnav-controller <f0 | f1 | fp active | fp standby> connections ...

To query the application and session entries and to optionally filter the output by using specific criteria, use the following command:

router# show service-insertion statistics sessions [[vrf-name 
name
] [client-ip 
IP_address
][server-ip 
IP_address
] [server-port 
port_number
] [detail]]

Application entries do not have client or service node IP addresses.

Here is an example:

router# show service-insertion statistics sessions
Collecting Records. Please wait...
Client					Server						SN-IP				VRF-Name
N/A					192.168.180.4:1092						N/A
192.168.80.4:0					192.168.180.4:1092						172.16.0.2

If you include the detail keyword, the report also displays the application ID and the time since the last activity.

Here is an example:

Router# show service-insertion statistics sessions detail
Collecting Records. Please wait...
Client: 192.168.80.4:0
Server: 192.168.180.4:1098
Service Node IP: 172.16.0.2
VRF-Name:
Application ID: 78
Time since last activity : 0hr 36min 30sec
 
Client: N/A
Server: 192.168.180.4:1098
Service Node IP: N/A
VRF-Name:
Application ID: 78
Time since last activity : 0hr 36min 30sec

You can also use the show platform software command. It works exactly the same as the show service-insertion statistics command, but it can also be used to query the application and session entries on the standby FP.

router# show platform software appnav-controller <f0 | f1 | fp active | fp standby> sessions ...

Use the show policy-map target service-context [service_context_name] command to view the flow level statistics of all the class maps and policy maps that are configured under a service context. If you do not enter a service context name, the system displays all the configured class maps and policy map output.

The following are examples:

router# show policy-map target service-context waas/1
Service-policy appnav input: p1
Class-map: c1 (match-all)
      Match: access-group 101
      distribute service-node-group sng
        Distributed: 313450 packets, 135820480 bytes
        Passed through: 0 packets, 0 bytes
       Aggregate: 313450 packets, 135820480 bytes
	monitor-load http
    Class-map: c2 (match-all)
      Match: access-group 102
	Pass-through
		Distributed: 0 packets, 0 bytes
        Passed through: 40 packets, 30000 bytes
       Aggregate: 40 packets, 30000 bytes
    Class-map: class-default (match-any)
      Match: any
router# show policy-map target service-context
Service-policy appnav input: p1
      Class-map: c1 (match-all)
         Match: access-group 101
       distribute service-node-group sng1
         Distributed: 0 packets, 0 bytes
         Passed through: 0 packets, 0 bytes 
       Aggregate: 0 packets, 0 bytes
       monitor-load http
      Class-map: class-default (match-any)
         Match: any
    Service-policy appnav input: p3
Class-map: c3 (match-all)
      Match: access-group 101
      distribute service-node-group sng3
         Distributed: 0 packets, 0 bytes
         Passed through: 0 packets, 0 bytes 
       Aggregate: 0 packets, 0 bytes
    Class-map: class-default (match-any)
       Match: any

To view the passthrough reason statistics aggregated for all the classes of a policy associated with the specified service context, use the following command:

router# show policy-map target service-context 
context_name
 passthru-reason

To view the passthrough reason statistics for a particular class of a policy associated with the specified service context, use the following command:

router# show policy-map target service-context 
context_name
 class 
class_name
 passthru-reason

Here is an example:

router# show policy-map target service-context waas/1 class c4 passthru-reason
Service-policy appnav input: p4
Class-map: c4 (match-all)
	Match: access-group 101
	distribute service-node-group sng4
		Distributed: 11 packets, 222 bytes
		Passed through: 100 packets, 22000 bytes
	Aggregate: 111 packets, 22222 bytes
Collected by SC:
Passthrough Reasons	Packets		Bytes
------------------------	------- 	-	------
PT Flow Learn Failure		0	0
PT SNG Overload		0	0
PT Appnav Policy		0	0
PT Cluster Degrade		0	0
PT ZBFW		0	0
PT NAT ALG		0	0
PT Unknown		0	0
Indicated by SN:
Passthrough Reasons	Packet		 Bytes
------------------------	-------	-	------
PT No Peer		100	22000
PT Rjct Capabilities		0	0
PT Rjct Resources		0	0
PT Rjct No License		0	0
PT App Config		0	0
PT Global Config		0	0
PT Asymmetric		0	0
PT In Progress		0	0
PT Intermediate		0	0
PT Overload		0	0
PT Internal Error		0	0
PT App Override		0	0
PT Server Black List		0	0
PT AD Version Mismatch		0	0
PT AD AO Incompatible		0	0
PT AD AOIM Progress		0	0
PT DM Version Mismatch		0	0
PT Peer Override		0	0
PT Bad AD Options		0	0
PT Non-optimizing Peer		0	0
PT SN Interception ACL 		0	0
PT IP Fragment Unsupported		0	0
	-----------		-------
PT Overall		100	22000