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

236 AppendixA
NMS Error Messages
NMGR Error and Warning Messages
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Select stack underflow probably missing SELECT.
(NMGRERR 223)
NMGRERR 223 CAUSE: This is an internal guided configuration error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Missing ENDSELECT statement. (NMGRERR 224)
NMGRERR 224 CAUSE: This is an internal guided configuration error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Unknown statement in Guided Configuration driver.
(NMGRERR 226)
NMGRERR 226 CAUSE: This is an internal guided configuration error.
ACTION: Restore NMMGRCAT.PUB.SYS from back-up tape. If this fails
see “Submitting an SR” at the beginning of this appendix.
MESSAGE: Command not allowed on error or version screen.
(NMGRERR 227)
NMGRERR 227 CAUSE: Certain commands are only allowed on states which contain a
path. This is likely to occur when the user types STOP on the errors
screen or the version screen during guided configuration.
ACTION: Move to a state which contains a path and retype the stop
command.
MESSAGE: The network interface data and the topology key must
match. (NMGRERR 228)
NMGRERR 228 CAUSE: The type of the network interface does not match the topology
key which you selected.
ACTION: Make sure you pressed the correct topology key and have the
correct network interface name. Check the type of the network interface
name by going to NEXPORT.NI (do a direct branch).
MESSAGE: The Network interface must of type POINT-TO-POINT.
(NMGRERR 229)
NMGRERR 229 CAUSE: The Network Interface must be of type POINT-TO-POINT.
ACTION: Check the type of the network interface name by going to
NETXPORT.NI (do a direct branch).
MESSAGE: The Network interface may not be of type LOOPBACK.
(NMGRERR 230)
NMGRERR 230 CAUSE: There is no Internet data to configure under the loopback
network interface.
ACTION: Do not use this function with loopback.