Using the Node Management Services (NMS) Utilities (32022-90053)

278 AppendixA
NMS Error Messages
NMMGRVER Messages, Errors and Warnings
MESSAGE: An error has occurred during LAN LINK CONVERSION.
(NMMGRVERERR 88)
NMMGRVERERR
88
CAUSE: An error occurred during the LAN LINK part of the conversion
process. The actual error is listed in an error message which should be
displayed along with this one.
ACTION: Restore a backup copy of the configuration file if possible. Use
the version of NMMGR that created the configuration file to make sure
that each data screen in the configuration file has data associated with
it and that its data flag is set to Y. Run NMMGRVER again. If the same
error occurs again, check any accompanying error message and take the
action listed for it in this appendix. If this fails, submit a Service
Request. See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Duplicate host luname (!) found in node !.
(NMMGRVERERR 89)
NMMGRVERERR
89
CAUSE: The configuration file contains an SNANODE that contains
two or more lus that have the same name. Only the first lu found is
converted. The other names are skipped, and the conversion will
continue.
ACTION: Use the same version of NMMGR that created it to modify
the unconverted configuration file. Delete the duplicate lu names or
change them to unique names and then convert the configuration file.
MESSAGE: Can’t find host luname. Nau = !, Node = !.
(NMMGRVERERR 90)
NMMGRVERERR
90
CAUSE: The host luname is not configured in the configuration file.
Therefore, this nau is not converted.
ACTION: Use the same version of NMMGR that created it to modify
the unconverted configuration file. Either delete the host luname or add
the host lu and then convert the configuration file.
MESSAGE: An error has occurred during LINK CONVERSION.
(NMMGRVERERR 91)
NMMGRVERERR
91
CAUSE: An error occurred during the LINK part of the conversion
process. The actual error is listed in an error message which should be
displayed along with this one.
ACTION: Restore a backup copy of the configuration file if possible. Use
the version of NMMGR that created the configuration file to make sure
that each data screen in the configuration file has data associated with
it and that its data flag is set to Y. Run NMMGRVER again. If the same
error occurs again, check any accompanying error message and take the
action listed for it in this appendix. If this fails, submit a Service
Request. See “Submitting an SR” at the beginning of this appendix.