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:
In the IPv6 HA Nodal and IPv6 CN Node test cases, the values on the CN tab report the number and types of Mobile IPv6 control messages sent and received by the CN emulator.
In the HSGW Nodal test case, the values on the PMIPv6 tab report the number and types of Proxy Mobile IPv6 control messages sent and received by the LMA node.
In SGW Nodal test case, the values on the S5-S2a tab report the number and types of Proxy Mobile IPv6 control messages sent and received by the PDN GW Node.
During SGW Nodal testing when Test Activity is Inter-Technology Mobility, Handoff Protocol is eHRPD, and S5/S8 protocol is PMIPv6, the S5-S2a tab also lists the MAG measurements.
In PGW Node test case, these measurements are displayed when Protocol is PMIPv6.
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 the number and types of messages exchanged between the CN and the MNs.
CN BA Sent — The number of Binding Acknowledgement messages sent by the CN.
CN BE Sent — The number of Binding Error messages sent by 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.
CN BR Sent — The number of Binding Refresh requests sent by the CN.
CN HT Sent — The number of Home Test messages sent to the MN's home address.
CN COT Sent — The number of Care of Test messages sent to the MN's care-of address.
CN BU Received — The number of Binding Update messages received from the MNs.
CN BUL0 Received — The number of Binding Update messages with a lifetime of 0 (de-registrations) received from the MNs.
CN HTI Received — The number of Home Test Init messages received from the MNs.
CN COTI Received — The number of Care of Test Init messages received from the MNs.
CN BA00 — The number of Binding Acknowledgement messages sent by the CN with a Status value of 0, indicating that the MN's Binding Update was accepted.
CN BRI Sent — The number of Binding Refresh Ignore requests sent by the CN.
CN BRI Retries Exceeded — The number of times the Binding Refresh Ignore retries was exceeded.
CN BRA Received — The number of Binding Refresh Advice requests sent by the CN.
CN BRA Timer Expired — The number of times a Binding Refresh Advise timer expired.
CN MPA Sent — The number of Mobile Prefix Advertisement messages received from the CN.
CN HADR Sent — The number of Home Address Discovery Reply messages received from the CN.
CN MPS Received — The number of Mobile Prefix Advertisement messages received from the CN.
CN HAD Received — The number of Home Address Discovery requests sent by the CN.
The following measurements report the number of times the CN has rejected a Binding Update received from an MN and replied with one of the listed error codes in the Status field of the Binding Acknowledgement:
CN BA128 — Unspecified reason
CN BA129 — Administratively prohibited
CN BA130 — Insufficient resources
CN BA131 — Home registration is not supported
CN BA132 — Unpredictable behavior
CN BA133 — Cache Parity Errors
CN BA134 — Uncorrectable error has been logged (the Corrected Error Count Overflow indication will be lost if the overflow occurs after an uncorrectable error has been logged)
CN BA135 — Sequence number out of window
CN BA136 — Expired home nonce index
CN BA137 — Expired care of nonce index
CN BA138 — Expired nonces
CN BA139 — Registration type change disallowed
CN BA146 —
Any messages received by the CN that fail validation checks and cause the CN to discard the message, or that would cause the CN to reply with an ICMP Parameter Problem message are reported in the Unknown Error counter.
CN Unknown Error
CN Attempts — The number of times Route Optimization is attempted between an MN and the CN.
See also MN Measurements.