Supported Registration Reply Codes

The following section describes the registration reply codes supported by the system for the HA service.

HA Service Reply Codes

The following registration reply codes are supported by the system’s HA service in accordance with the following Request For Comments (RFCs):

  • RFC-2002, IPv4 Mobility, May 1995
  • RFC-2344, Reverse Tunneling for Mobile IP, May 1998

Table 1. Supported HA Service Registration Reply Codes
Reply Code (Hex / Base 10) Description Note
80H / 128 Registration Denied - reason unspecified Sent when internal errors are encountered when processing the Request packet.
81H / 129 Registration Denied - administratively prohibited Sent when a newcall policy is set to reject calls or the subscriber is not permitted to use Mobile IP HA services.
82H / 130 Registration Denied - insufficient resources Sent when no memory or session managers are available to process the session.
83H / 131 Registration Denied - mobile node failed authentication Sent when the mobile node failed authentication.
84H / 132 Registration Denied - foreign agent failed authentication Sent when an FA attempted to communicate with the HA service using an incorrect security parameter index (SPI).
85H / 133 Registration Denied - registration Identification mismatch Sent when the ID sent by the mobile node in the RRQ is different from the expected value.
86H / 134 Registration Denied - poorly formed request Sent when the registration request is poorly formed (i.e. missing an Authentication extension).
87H / 135 Registration Denied - too many simultaneous mobility bindings Sent when the mobile node has exceeded the maximum number of mobile bindings that the HA service supports for a single subscriber.
88H / 136 Registration Denied - unknown home agent address Sent when HA redirect policy is invoked.
89H / 137 Registration Denied - reverse tunneling unavailable Sent when reverse tunneling is requested by the mobile node but it is not enabled on the system.
8AH / 138 Registration Denied - reverse tunneling mandatory Sent when reverse tunneling is enabled on the system but is not supported by the mobile node.
8BH / 139 Registration Denied - reverse tunneling encapsulation style unavailable Sent if the Encapsulating Delivery Style Extension sent by the mobile is not supported by the HA service.
8DH / 141 Registration Denied - unsupported Vendor-ID or unable to interpret Vendor-CVSE-Type. Sent if the Vendor Identification is unsupported or the HA is unable to interpret the Vendor-CVSE-Type in the CVSE sent by the Foreign Agent to the Home Agent.
8EH/142 Registration Denied - Requested UDP tunnel encapsulation unavailable Sent by the HA if a UDP tunneling mode is not available.