The number and types of Mobile IPv6 control messages sent and received by an emulator is reported on different tabs depending on the test cases. The following lists the tabs and the test cases that display the MIPv6 messages:
During PGW Nodal test case these measurements are displayed when Network Interface is S2a/S2b.
During MME Nodal test case these measurements are displayed when Test Activity is Inter-Technology Mobility, Handoff Protocol is eHRPD, and Initial Network is Target.
During SGW Nodal test case these measurements are displayed when Test Activity is Inter-Technology Mobility, Handoff Protocol is eHRPD, and S5/S8 protocol is GTPv2.
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.
Total Packets Received — The number of packets received by all emulated MNs.
Total Packets Sent — The number of packets sent by all emulated MNs.
Total Bytes Received — The number of bytes received by all emulated MNs.
Total Bytes Sent — The number of bytes sent by all emulated MNs.
Total Packets — The aggregate throughput of packets of all emulated MNs.
Total Packets/Second — The aggregate throughput of the previous interval, in packets per second, of all emulated MNs.
Total Bits/Second — The aggregate throughput of the previous interval, in bits per second, of all emulated MNs.
Total Bits Sent/Sec — The aggregate throughput sent of the previous interval, in bits per second, of all emulated MNs.
Total Received Fragments — The number of fragmented packets received by all emulated MNs.
Total Received Fragmented Packets — 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 Received Non-Fragmented Packets — The total number of non-fragmented packets received. That is, Total Packets Received - Total Fragmented Packets Received.
Total Sent Fragments — 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 Sent Fragmented Packets — 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 Sent Non-Fragmented Packets — The total number of non-fragmented packets sent. That is, Total Packets Sent - Total Fragmented Packets Sent.
The following measurements record the number and types of messages exchanged between the MNs and the HA and CN.
MN BA Received — The number of Binding Acknowledgement messages received by the MNs.
MN BE Received — The number of Binding Error messages received from the CN. A Binding Error can be generated by the use of an MN home address that is not associated with a binding on the CN, indicated by a 1 in the BE Status field, or by an invalid Mobility Header type in the Binding Update, indicated by a 2 in the BE Status field.
MN BR Received — The number of Binding Refresh requests received from the HA and the CN.
MN MPA Received — The number of Mobile Prefix Advertisement messages received from the HA.
MN HADR Received — The number of Home Address Discovery Reply messages received from the HA.
MN HT Received — The number of Home Test messages received from the CN.
MN COT Received — The number of Care of Test messages received from the CN.
MN HOTI Sent — The number of Home Test Init messages sent to the CN.
MN COTI Sent — The number of Care of Test Init messages sent to the CN.
MN BU Sent — The number of Binding Update messages sent to the HA and CN.
MN BUL0 Sent - Deregistration Attempt — The number of Binding Update messages with a Lifetime of 0 that were sent by the MNs.
MN MPS Sent — The number of Mobile Prefix Solicitation messages sent by the MNs.
MN HAD Sent — The number of Home Address Discovery requests sent by the MNs.
MN BA00 — The number of Binding Acknowledgements received by the MNs with a Status value of 0, indicating that the Binding Update was accepted.
MN BA00 - Deregistration Accept — The number of Binding Deregistration requests accept received by the MNs with a Status value of 0, indicating that the Binding Deregistration was accepted.
MN BA01 — The number of Binding Acknowledgements received by the MNs from the HA with a Status value of 1, indicating that the Binding Update was accepted but that prefix discovery is necessary.
The following counters report the number of messages discarded by the MNs while the test server was in an overload condition.
Total Received Packets Discarded — The number of packets received that could not be processed.
Total Sent Packets Discarded — The number of packets that could not be sent.
Total Discarded Packets — The total number of packets discarded.
The following counters report the number of messages received with errors that prevented further processing.
Total Invalid Received Packets — The number of IP packets received that contained an unknown protocol type or an invalid IP checksum.
MN Unknown Error — The number of messages received by the MN that would cause it to reply with an ICMP Parameter Problem message.
The following counters report the number of communication errors and failures by message type. The Retry counters record the number of times a message was re-transmitted because a response was not received by the MN. The Retry Exceeded counters record the number of times the defined Retries was exceeded.
|
Message Type |
Retry Counter |
Retry Exceeded Counter |
|---|---|---|
|
Home Test Init |
MN HTI Retry |
MN HTI Retry Exceeded |
|
Care of Test Init |
MN COTI Retry |
MN COTI Retry Exceeded |
|
Mobile Prefix Solicitation |
MN MPS Retry |
MN MPS Retry Exceeded |
|
Binding Update |
MN BA Retry |
MN BA Retry Exceeded |
The following counters report the number of Binding Acknowledgements received by the MNs from either an HA or a CN with the listed error code in the Status field, which indicates that the node has rejected a Binding Update.
MN BA128 — Unspecified reason
MN BA129 — Administratively prohibited
MN BA130 — Insufficient resources
MN BA131 — Home registration is not supported
MN BA132 — Not home subnet
MN BA133 — Not home agent for this mobile node
MN BA134 — Duplicate address detection failed
MN BA135 — Sequence number out of window
MN BA136 — Expired home nonce index
MN BA137 — Expired care of nonce index
MN BA138 — Expired nonces
MN BA139 — Registration type change disallowed
MN BA146
MN Attempts — The number of times an MN attempts to register with an HA.
MN Successes — The number of times an MN successfully registers with an HA and a session is established.
MN RO Attempts — The number of times the MNs attempt to establish Route Optimization by registering with the CN.
MN RO Successes — The number of times the MNs establish Route Optimization with the CN.
MN IPSec Attempts — The number of times the MNs attempt to establish an IPSec tunnel with the HA.
MN IPSec Successes — The number of times the MNs successfully establish an IPSec tunnel with the HA.
MN IPSec Failures — The number of times the MNs fail to establish an IPSec tunnel with the HA.
IPSec Tunnel Attempts — The number of times the MN attempts to establish an IPSec tunnel.
IPSec Tunnel Successes — The number of times the MN successfully establish an IPSec tunnel.
IPSec Tunnel Failures — The number of times the MN failed to establish an IPSec tunnel.
IPSEC Unhandled Packets — The number of packets which should have been encrypted, but were not handled because no tunnel was found for it. (If the IP does not fall within the specified ranges of the Traffic Selectors, it will go unencrypted and unhandled).
Pings Sent —The number of ping requests sent by the MN or ping replies sent by the Network Host.
Pings Received — The number of times a peer received a ping.
MN Move Attempts — The number of times an MN attempts to register a new care-of address with an HA in a Mobile Node Mobility test or attempts to return home.
MN Move Successes — The number of move attempts that were successful.