The values on the M3UA tab report the processing measurements for the M3UA layer and the SCTP associations in a UMTS and HSS Node test cases.
In the default view, the Reports tab displays the Summary view, which summarizes the measurements for the test session. If your test includes multiple test cases, you can view the report for a single test case by changing the report view...
Unless otherwise noted, cumulative values report the number of occurrences or rates calculated since the start of the test, and per-interval values report the number of occurrences or rates calculated during the interval. You can view either by changing the measurement values...
Elapsed Time is the first measurement on every tab. It reports the amount of time between the start of the test and the end of the report interval.
Test Iteration reports the current iteration in a repeating test session. It is only displayed when a Number of Iterations is defined for the test session.
The following measurements record all M3UA traffic processed by the RNC nodes.
Associations Established — The number of SCCP associations established
Establishment Timeout — The number of times an SCTP association could not be established because the Number of Retries was exhausted.
Total Packets Sent — The number of packets sent by the RNC node
Total Packets Received — The number of packets received from the RNC node
Total Packets — The number of packets processed by the RNC node
Total Packets/Sec — The data throughput rate of the previous interval in packets per second.
Total Invalid Packets — The number of packets received that contained an unknown protocol type or an invalid checksum.
The following measurements record the number of packets discarded when Packet Discard error injection is used.
Received Packets Discarded — The number of incoming packets discarded.
Sent Packets Discarded — The number of outgoing packets discarded.
Total Discarded Packets — The total number of packets discarded.
The following measurements record the number and types of M3UA messages exchanged between the RNCs and the SGSN.
DAUD Sent — The number of Destination State Audit messages sent in order to audit the availability or congestion state of a route.
DAVA Sent — The number of Destination Available messages sent.
DAVA Received — The number of Destination Available messages received.
DUNA Received — The number of Destination Unavailable messages received.
ASPAC Sent — The number of ASP Active messages sent to notify the SUT that an RNC is ready to process signalling traffic.
ASPAC Received — The number of ASP Active messages received.
ASPAC Acknowledgements Received — The number of ASP Active Acknowledgement messages received.
ASPAC Acknowledgements Sent — The number of ASP Active Acknowledgement messages sent in response to an ASP Active.
ASPUP Sent — The number of ASP Up messages sent by the RNCs to notify the SUT that M3UA is ready to receive ASP messages.
ASPUP Received — The number of ASP Up messages received.
ASPUP Acknowledgements Received — The number of ASP Up Acknowledgements messages received.
ASPUP Acknowledgements Sent — The number of ASP Up Acknowledgements messages sent in response to an ASP Up.
ASPIA Sent — The number of ASP Inactive messages sent by the RNCs to notify the SUT that it is no longer an active application server.
ASPIA Received — The number of ASP Inactive messages received.
ASPIA Acknowledgements Received — The number of ASP Inactive Acknowledgement messages received.
ASPIA Acknowledgements Sent — The number of ASP Inactive Acknowledgement messages sent in response to an ASP Inactive.
ASPDN Sent — The number of ASP Down messages sent by the RNCs to notify the SUT that M3UA is not ready to receive any messages.
ASPDN Received — The number of ASP Down messages received.
ASPDN Acknowledgements Received — The number of ASP Down Acknowledgement messages received.
ASPDN Acknowledgements Sent — The number of ASP Down Acknowledgement messages sent in response to an ASP Down.
Total Packets Sent — The number of bearer plane packets sent.
Total Packets Sent/Sec — The number of bearer plane packets sent per second.
Total Packets Received — The number of bearer plane packets received.
Total Packets Received/Sec — The number of bearer plane packets received per second.
Total Packets — The total number of packets processed by the nodes.
Total Packets/Sec — The data throughput rate as of the previous interval in packets per second.
Total Packets Invalid — The number of packets received that contained an unknown protocol type or an invalid IP checksum, and any packets recorded by Command Messages Invalid.
Total Fragments Sent — The number of fragmented data packets sent. By default, fragmentation occurs when the total bytes in the data packet exceeds 1400 bytes. You can control fragmentation by defining the MTU.
Total Fragments Received — The number of fragmented packets received.
Total Fragmented Packets Received — The total number of fragmented packets received. For example, if one IP packet was broken up into 3 fragments, the counter considers it as 1 fragmented packet.
Total Non-Fragmented Packets Received — The total number of non-fragmented packets received. That is, Total Packets Received - Total Fragmented Packets Received.
Total Fragmented Packets Sent — The total number of fragmented packets sent. For example, if one IP packet was broken up into 3 fragments, the counter considers it as 1 fragmented packet.
Total Non-Fragmented Packets Sent — The total number of non-fragmented packets sent. That is, Total Packets Sent - Total Fragmented Packets Sent.
|
NOTE: When fragmentation occurs at the IP layer in packets sent by MNs, the receiving test server's OS will re-assemble the fragments and forward a re-assembled packet to the Network Host. In this case, the Network Host tab will not record Total Fragments Received, and the Total Packets Received and Total Bytes Received counters will record the counts for the re-assembled packets, not the fragmented packets. |
Data Verify Attempts — The number of Data Verify attempts.
Data Verify Successes — The number of Data Verify successes.
Data Verify Failures — The number of Data Verify failures.
Total Pings Received — The number of Ping Requests Received by the UE or Network Host.
Total Pings Sent — The number of Ping Requests and Ping Replies Sent by the UE or Network Host.
Total Ping Replies Received — The number of Ping Replies Received by the UE or the Network Host.
Total Bytes Sent — The number of bytes sent.
Total Bits Sent/Sec — The number of bits sent per second.
Total Bytes Received — The number of bytes received.
Total Bits Received/Sec — The number of bits received per second.
Total Bytes — The total number of bytes processed by the nodes.
Total Bits/Sec — The data throughput rate as of the previous interval in bits per second.
Average Packet Size (B/p) — The Total Bytes divided by (/ ) Total Packets.
Average Sent Packet Size (B/p) — The Total Bytes Sent / Total Packets Sent.
Average Received Packet Size (B/p) — The Total Bytes Received / Total Packets Received.
Socket FIN Messages Sent — The number of Socket Fin messages sent.
Socket FIN Messages Received — The number of Socket Fin messages received.
Socket FIN ACK Messages Sent — The number of Socket Fin ACK messages sent.
Socket FIN ACK Messages Received — The number of Socket Fin ACK messages received.
Echo Requests Sent — The number of Echo Request messages sent.
Echo Requests Received — The number of Echo Request messages received.
Echo Responses Sent — The number of Echo Response messages sent.
Echo Responses Received — The number of Echo Response messages received.
Heartbeat Requests Sent — The total number of Heartbeat Requests sent received.
Heartbeat Requests Received — The total number of Heartbeat Requests received.
Heartbeat Responses Sent — The total number of Heartbeat Responses sent.
Heartbeat Responses Received — The total number of Heartbeat Responses received.
Max Missing Heartbeat Req Exceeded — The number of Heartbeat Requests that exceeded the Maximum Number of Consecutive Heartbeat Requests allowed.
Total Ethernet Bytes Sent — The total number of Ethernet bytes sent.
Total Ethernet Bits Sent/Sec — The total number of Ethernet bits sent per second.
Total Ethernet Bytes Received — The total number of Ethernet bytes received.
Total Ethernet Bits Received/Sec — The total number of Ethernet bits received per second.
See SCTP Measurement for the following Socket measurements
The following measurements report the number and type of errors encountered during the test.
Establishment Timeout — The number of times an SCTP association could not be established because the Number of Retries was exhausted.
Invalid Packets — The number of packets received that contained an unknown protocol type or an invalid checksum.
Socket Window Full — The number of times an SCTP window reached its maximum size before an acknowledgement was received.
The following measurements record the number of times the Retry Time expired before an appropriate response was received for the subject message.
DAUD Timeouts — The number of times a DAUD message was sent without receiving a response from the SGP.
Destination State Audit (DAUD) message is sent from the ASP to the SGP to audit the availability/congestion state of SS7 routes from the SG to one or more affected destinations.
ASPAC Timeouts — The number of times ASPAC message was sent without receiving a response from the remote M3UA peer.
The ASP Active (ASPAC) message is sent by an ASP to indicate to a remote M3UA peer that it is ready to process signalling traffic for a particular Application Server. The ASP Active message affects only the ASP state for the Routing Keys identified by the Routing Contexts, when present.
ASPUP Timeouts — The number of times ASPUP message was sent without receiving a response from the remote M3UA peer.
The ASP Up (ASPUP) message indicated to a remote M3UA peer that the adaptation layer is ready to receive any ASPSM/ASPTM messages for all Routing Keys that the ASP is configured to serve.
ASPIA Timeouts — The number of times ASPIA message was sent to indicate ASP inactive state to the remote M3UA peer.
The ASP Inactive (ASPIA) message is sent by an ASP to indicate to a remote M3UA peer that it is no longer an active ASP to be used from within a list of ASPs. The ASP Inactive message affects only the ASP state in the Routing Keys identified by the Routing Contexts, when present.
ASPDN Timeouts — The number of times ASPDN message was sent to the remote M3UA peer.
The ASP Down (ASPDN) message is used to indicate to a remote M3UA peer that the adaptation layer is NOT ready to receive DATA, SSNM, RKM or ASPTM messages.