HP-UX Mobile IPv4 A.03.01 Administrator's Guide

8GTKH[KPICPF6TQWDNGUJQQVKPI
%QOOQP2TQDNGOU
Chapter 8
105
AAA Registration Fails because of AAA Key Extension Type or Subtype
Mismatch (Unrecognized extension, Unrecognized subtype)
The IETF is still defining AAA type and subtype values for AAA Generalized Key
Request/Reply message extensions. A AAA Mobile Node client may use type or subtype
values that do not match the values used by HP-UX Mobile IPv4. If the type values do
not match, you will see entries similar to the following on the Home Agent:
Jan 29 15:35:29 ERROR: Unrecognized extension (type = 42)
encountered
Jan 29 15:35:29 ERROR: ha_prcocessHARmsg: bad format in
registration request AVP
Jan 29 15:35:29 WARN: sending HAA for session
aaa://hpindwqt.home.com:1812;transport=tcp;1043172648;99 with
non-success result code (4005)
If the subtype values do not match, you will see entries similar to the following:
Jan 29 15:09:58 ERROR: Unrecognized subtype (7) for extension
type=43
If you are using Foreign Agent Care-of Addresses, you will also log entries similar to the
following on the Foreign Agent:
Jan 29 15:07:24 ERROR: Unrecognized extension (type = 40)
encountered
Jan 29 15:07:24 WARN: Replying with Error ‘FOR_REQ_FORMAT’
Jan 29 15:07:24 WARN: FA: No AAA distributed FA-MN security
association is recorded for MN ([e-mail])
Jan 29 15:07:24 WARN: FA: rejected request from MN
([e-mail]) to HA(11.11.11.2) 50 sec - FOR_REQ_FORMAT
Solution When the mipd daemon starts, it reads AAA key type and subtype definitions
from the /var/adm/mip/AAAKeyTypes.conf file. This file contains type and subtype
definitions from the following IETF documents:
• Type values: Generalized Key Distribution Extensions for Mobile IP, Draft 0
(draft-ietf-mobileip-gen-key-00).
• Subtype values: AAA Registration Keys for Mobile IP, Draft 10
(draft-ietf-mobileip-aaa-key-10). (This draft defines the key type values as “tbd.”)
If the AAAKeyTypes.conf file does not exist, mipd will use the values defined in the
above IETF documents.
If the Mobile Node clients are using different type or subtype values, edit the file
/var/adm/mip/AAAKeyTypes.conf to match the values used by the client and re-start
mipd.