View Application Statistics for Service-Based Interface Packet Order Enforcement (SBIPOE) Application

To view the application Statistics for the SBIPOE application, follow the given steps:

1. Go to Traffic > Virtual > Orchestrated Flows > Select your cloud platform. The Monitoring Sessions Overview page appears.
2. Navigate to the TRAFFIC PROCESSING tab. In the canvas page, click the menu button on the Sbipoe application and select Details. The Application quick view appears.
3. Click on STATISTICS tab.

You can view the following statistics for the SBIPOE application in the Statistics tab:

1.

RXPackets: Number of packets received by the SBIPOE application.

2.

RXBytes: Number of bytes received by the SBIPOE application.

3.

TXPackets: Number of packets transmitted by the SBIPOE application.

4.

TXBytes: Number of bytes transmitted by the SBIPOE application.

5.

GetFlows: Number of times a new flow (an XactFlow structure used to track SBI transactions) is pulled from the free pool.

6.

FreeFlows: Number of XactFlow structures returned to the free pool.

7.

InsertFlows: Number of XactFlow structures added to the active transaction list.

8.

DeleteActiveFlows: Number of XactFlow structures removed from the active transaction list; these are returned to the free pool.

9.

TimeoutActiveFlows: Number of XactFlow structures that timed out while active; timed-out flows are returned to the free pool.

10.

GetFlowErrors: Number of times GetFlows failed because the free pool had no available XactFlow structures.

11.

FreeFlowErrors: Number of errors during FreeFlows processing.

12.

InsertFlowErrors: Number of times a new active flow could not be added to the active transaction list. Should always be 0 - a nonzero value signals a serious issue.

13.

FlowAllocationErrors: Number of times GetFlows failed due to no free XactFlow structures being available in the pool.

14.

PktsWithVLAN: Number of received packets carrying a VLAN tag. Should normally be 0.

15.

IPV4Pkts: Number of received packets that are IPv4. Since production traffic should be IPv6-only, this should be 0.

16.

IPV6Pkts: Number of received packets that are IPv6. Since production traffic should be IPv6-only, this should equal RXPackets.

17.

TCPPkts: Number of received packets that are TCP. Since production traffic should be TCP-only, this should equal RXPackets.

18.

PktsWithIPPayloadLenError: Number of received packets whose IP length (IPv4 or IPv6) doesn't match the actual packet length, indicating the packet was truncated upstream. Should be 0.

19.

PktsTooShort: Number of received packets shorter than expected. Related to, but distinct from, the IP payload length error. Should be 0.

20.

Http2Pkts: Number of received packets containing HTTP/2 frames. Should account for all received packets.

21.

Http2Magic: Number of received packets containing an HTTP/2 Magic frame. Each HTTP/2 request should have exactly one.

22.

Http2Frames: Number of HTTP/2 frames received across all HTTP/2 packets.

23.

Http2HeadersFrames: Number of HTTP/2 Headers frames received across all HTTP/2 packets.

24.

Http2DataFrames: Number of HTTP/2 Data frames received across all HTTP/2 packets.

25.

Http2FrameLenError: Number of HTTP/2 frames with a frame-length error, indicating malformed HTTP/2 data. Should be 0.

26.

Http2ReqHeadersFrames: Number of HTTP/2 Headers frames in request messages. Each transaction should have one request and one response Headers frame.

27.

Http2RespHeadersFrames: Number of HTTP/2 Headers frames in response messages. Each transaction should have one request and one response Headers frame.

28.

Http2HeadersFramesPadding: Number of HTTP/2 Headers frames received with padding. Allowed by the protocol but should be infrequent.

29.

Http2HeadersFramesPriority: Number of HTTP/2 Headers frames received with priority bits set. Allowed by the protocol but should be infrequent.

30.

Http2ReqHeadersEH: Number of request Headers frames received with the End Headers flag set.

31.

Http2RespHeadersFramesEH: Number of response Headers frames received with the End Headers flag set.

32.

Http2ReqHeadersFramesES: Number of request Headers frames received with the End Stream flag set.

33.

Http2RespHeadersFramesES: Number of response Headers frames received with the End Stream flag set.

34.

Http2RequestDataFrames: Number of HTTP/2 Data frames received in request messages.

35.

Http2ResponseDataFrames: Number of HTTP/2 Data frames received in response messages.

36.

Http2DataFramsPadding: Number of HTTP/2 Data frames received with padding. Allowed by the protocol but should be infrequent.

37.

Http2DataFramesPriority: Number of HTTP/2 Data frames received with priority set. Allowed by the protocol but should be infrequent.

38.

Http2ReqDataFramesTooLarge: Number of request Data frames larger than the packet size, indicating a serious issue. Should not occur.

39.

Http2RespDataFramesTooLarge: Number of response Data frames larger than the packet size, indicating a serious issue. Should not occur.

40.

Http2ReqDataFramesES: Number of request Data frames received with the End Stream flag set.

41.

Http2ReqDataFramesESClr: Number of request Data frames received with the End Stream flag not set. Occurs occasionally, but rare.

42.

Http2RespDataFramesES: Number of response Data frames received with the End Stream flag set.

43.

Http2RespDataFramesESClr: Number of response Data frames received with the End Stream flag not set. Occurs occasionally, but rare.

44.

Http2ReqDataFramesLenZero: Number of Data frames received with a zero-length HTTP/2 frame. Occurs occasionally, but rare.

45.

XactPktsInclude: Number of received packets where the client or server TCP port is on the include list for transaction processing.

46.

XactPktsExcluded: Number of received packets where neither the client nor server TCP port is on the include list for transaction processing.

47.

XactPktsBothPorts: Number of received packets where both the client and server TCP ports are on the include list. Should not occur.

48.

XactIPV4Success: Number of successfully processed HTTP/2 transactions with IPv4 client and server addresses.

49.

XactIPV4Total: Total number of HTTP/2 transactions with IPv4 client and server addresses.

50.

XactIPV6Success: Number of successfully processed HTTP/2 transactions with IPv6 client and server addresses.

51.

XactIPV6Total: Total number of HTTP/2 transactions with IPv6 client and server addresses.

52.

XactSuccessInOrder: Number of successfully processed transactions where all packets arrived in the correct sequence.

53.

XactSuccessOutOfOrder: Number of successfully processed transactions where one or more packets arrived out of sequence.

54.

XactReqSent: Number of received HTTP/2 transaction requests forwarded to the SBIPOE output.

55.

XactReqRecv: Number of HTTP/2 transaction requests received by the SBIPOE application.

56.

XactRespSent: Number of received HTTP/2 transaction responses forwarded to the SBIPOE output.

57.

XactRespRecv: Number of HTTP/2 transaction responses received by the SBIPOE application.

58.

XactRequestsFailedHttp2DecodeError: Number of request Headers frames that failed HTTP/2 decoding, indicating corrupted frame data. Should not occur.

59.

XactRespoFailedHttp2DecodeError: Number of response Headers frames that failed HTTP/2 decoding, indicating corrupted frame data. Should not occur.

60.

XactDuplicatePkts: Number of received packets whose data duplicates previously received HTTP/2 frame data - distinct from standard deduplication, and suggests duplication occurred between the GCB and the V Series hosting SBIPOE. Should not occur.

61.

XactFailedNoReq: Number of timed-out transactions where no packet data was seen for the request, causing an incomplete transaction. Should be infrequent.

62.

XactFailedNoResp: Number of timed-out transactions where no packet data was seen for the response, causing an incomplete transaction. Should be infrequent.

63.

XactFailedTcpSynHSMissing: Number of timed-out transactions where no part of the TCP SYN handshake was observed, causing an incomplete transaction. Should be infrequent.

64.

XactFailedTcpFinHSMisssing: Number of timed-out transactions where no part of the TCP FIN handshake was observed, causing an incomplete transaction. Should be infrequent.

65.

XactFailedReqNoMagic: Number of timed-out transactions where the HTTP/2 Magic frame was never observed, causing an incomplete transaction. Should be infrequent.

66.

XactFailedReqEH: Number of timed-out transactions where the End Headers flag was never seen in the request's Headers frame(s), causing an incomplete transaction. Should be infrequent.

67.

XactFailedReqES: Number of timed-out transactions where the End Stream flag was never seen in the request's Headers or Data frames, causing an incomplete transaction. Should be infrequent.

68.

XactReqNoHeaders: Number of timed-out transactions where no Headers frames were seen for the request, causing an incomplete transaction. Should be infrequent.

69.

XactFailedRespEH: Number of timed-out transactions where the End Headers flag was never seen in the response's Headers frame(s), causing an incomplete transaction. Should be infrequent.

70.

XactFailedRespES: Number of timed-out transactions where the End Stream flag was never seen in the response's Headers or Data frames, causing an incomplete transaction. Should be infrequent.

71.

XactRespNoHeaders: Number of timed-out transactions where no Headers frames were seen for the response, causing an incomplete transaction. Should be infrequent.

72.

XactReqTimedout: Number of timed-out transactions where the full request was observed but no response data was seen. Should be infrequent.

73.

XactRespTimedout: Number of timed-out transactions where the full response was observed but no request data was seen. Should be infrequent.

74.

XactPartialTimedout: Number of timed-out transactions where only part of the transaction was observed. Should be infrequent.

75.

Http2SynthReq: Number of synthesized transaction requests sent to the SBIPOE output.

76.

Http2SynthReqTrunc: Number of synthesized requests with truncated Headers or Data fields, indicating the transaction exceeded the XactFlow structure's capacity.

77.

Http2SynthReqSeg: Number of synthesized requests segmented before output because the transaction exceeded the ToolMTU size. Normal operation.

78.

Http2SynthReqOversized: Number of synthesized requests with oversized Headers or Data fields, indicating the transaction exceeded the XactFlow structure's capacity.

79.

Http2SynthResp: Number of synthesized transaction responses sent to the SBIPOE output.

80.

Http2SynthRespTrunc: Number of synthesized responses with truncated Headers or Data fields, indicating the transaction exceeded the XactFlow structure's capacity.

81.

Http2SynthRespSeg: Number of synthesized responses segmented before output because the transaction exceeded the ToolMTU size. Normal operation.

82.

Http2SynthRespOversized: Number of synthesized responses with oversized Headers or Data fields, indicating the transaction exceeded the XactFlow structure's capacity.

83.

KeepalivePkts: Number of keepalive messages sent by the SBIPOE application to keep the OVS path between the V Series and the probe active, preventing OVS flow ageouts that could cause out-of-order packet delivery.

84.

XactCloseDrops: Number of transactions dropped due to a transaction-close error.

85.

NumXLFlowPktsDropped: Number of dropped packets belonging to extra-large flows. Added to confirm that this condition would otherwise cause the segmentation faults seen in past SBIPOE crashes.

86.

NumXLFlows: Number of extra-large flows detected.

87.

FlowDeleteDuplicatePackets: Number of flows deleted and returned to the free pool after a duplicate packet was detected in the transaction. Should not occur.

88.

XactFailedInvalidHeader: Number of errors decoding HTTP/2 headers in request or response packets. Error condition; should not occur.

89.

Http2ReqCorrupt: Number of times request memory corruption was detected while processing an HTTP/2 request frame. Has previously caused SBIPOE segmentation-fault crashes.

90.

Http2RespCorrupt: Number of times response memory corruption was detected while processing an HTTP/2 response frame. Has previously caused SBIPOE segmentation-fault crashes.

91.

Http2ExceedMaxTCPSeg: Number of Headers or Data frames where the number of input TCP segments exceeded the maximum supported per transaction.

92.

Http2ErrorFlowProcessing: Number of errors encountered while processing a transaction. Error condition; should not occur.

93.

Http2PaddingOffsetError: Number of Headers or Data frames with an improperly formed padding offset, indicating a malformed HTTP/2 frame. Should not occur; has previously caused SBIPOE segmentation-fault crashes.