HA Error Codes

These measurements record errors received by an FA node from an HA SUT. Some or all of these measurements are available in the FA Emulation, Mobile IP, and Open RP report tabs.

• HA Reason Unspecified (128) — The total number of registration and re-registration reply messages received with an error code value of 128. This error code indicates that the HA is rejecting the MIP registration request for unknown reasons.

• HA Admin Prohibited (129) — The total number of registration reply messages received with an error code value of 129. This error code indicates that provisioning on the HA is rejecting the MIP registration request.

  NOTE: In the FA Nodal test case, the HA emulator will reject registration requests containing an invalid MN-NAI Extension, and will reply with error code 129.

• HA Insufficient Resources (130) — The total number of registration reply messages received with an error code value of 130. This error code indicates that the HA is rejecting the MIP registration request because of a shortage of resources such as memory.

• HAMN Authorization Failures (131) — The total number of registration reply messages received with an error code value of 131. This error code indicates that the HA is rejecting the MIP registration request because the MN failed authentication with the HA.

• HAFA Authorization Failures (132) — The total number of registration reply messages received with an error code value of 132. This error code indicates that the HA is rejecting the MIP registration request because the FA failed authentication with the HA.

  TROUBLESHOOT: Authorization failures can occur when the authentication parameters provisioned in the test do not supply values acceptable to the SUT or when an invalid encryption type is selected. Authorization failures can also occur when the SUT is running in a mode that is not RFC compliant. Normally a vendor provides the option to operate either in their custom mode or with full RFC compliance. When this is the case, configure the SUT to operate in RFC 3344 mode (when RFC 3344 Enable is selected) or in RFC 2002 mode (the default mode for the test system).

• Registration Identification Mismatch (133) — The total number of registration reply messages received with an error code value of 133. This error code indicates that the HA is rejecting the MIP registration request because it failed replay protection.

• HA Poorly Formed Request (134) — The total number of registration reply messages received with an error code value of 134. This error code indicates that the HA is rejecting the MIP registration request because of a problem with the message such as a missing mandatory extension.

• Too Many Simultaneous Bindings (135) — The total number of registration reply messages received with an error code value of 135. This error code indicates that the HA is rejecting the MIP registration request because the number of current registrations for the MN exceeds the maximum number of bindings provisioned on the HA for that MN.

• Unknown Home Agent Address (136) — The total number of registration reply messages received with an error code value of 136. This error code indicates that the MN is performing dynamic home agent address resolution and the home agent is providing the MN with its IP address.

• Reverse Tunnel Unavailable (137) — The total number of registration reply messages received with an error code value of 137. This error code indicates that the HA is rejecting the MIP registration request because the requested reverse tunneling is not supported.

• Reverse Tunnel Is Mandatory And T Bit Not Set (138) — The total number of registration reply messages received with an error code value of 138. This error code indicates that the HA is rejecting the MIP registration request because reverse tunneling is required but the T bit in the registration request is not set.

• Requested Encapsulation Not Available (139) — The total number of registration reply messages received with an error code value of 139. This error code indicates that the HA is rejecting the MIP registration request because the requested mode of encapsulation is not supported.

• HA Error 1 (140) — The total number of registration reply messages received with an error code value of 140.This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the MN to the HA.

• HA Error 2 (141) — The total number of registration reply messages received with an error code value of 141. This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the FA to the HA.

• HA UDP Encapsulation Unavailable (142) — The total number of registration reply messages received with an error code value of 142. This is used by the HA to distinguish a registration denial caused by an unavailable UDP tunnel encapsulation mode from a denial caused by an unavailable standard tunnel encapsulation (requested by use of the T bit together with either M or G bit).