HP 3000 Manuals HP 3000 Manuals
NMGRERR Messages (contd.)
NMGRERR 262 MESSAGE Must be a number from 0 to 5. (NMGRERR 262)
CAUSE At the DTC Configuration screen, the user
entered an invalid character in the field
specifying the card to be configured and pressed
the Config Card key.
ACTION Enter the number of the card to be configured
and press Config Card again. The number must be
between 0 and 5 and must correspond to the DTC
slot number of the card being configured.
--------------------------------------------------------------------------
NMGRERR 263 MESSAGE Data saved, but the home Network Interface does
not exist. (NMGRERR 263)
CAUSE The user specified a nonexisting NI name as the
home network interface and saved the data on the
screen.
ACTION If an incorrect NI name was specified, correct
the NI name and press Save Data again. If the
NI name is correct but the NI has not yet been
configured, configure the NI. There is no need
to re-enter the information on the current
screen since it has already been saved.
--------------------------------------------------------------------------
NMGRERR 264 MESSAGE Data saved, but the SNA Node does not exist.
(NMGRERR 264)
CAUSE The user specified a nonexisting SNA node and
saved the data on the screen.
ACTION If an incorrect SNA node was specified, correct
the SNA node name and press Save Data again. If
the SNA node name is correct but the SNA node
has not yet been configured, configure the SNA
node. There is no need to re-enter the
information on the current screen since it has
already been saved.
--------------------------------------------------------------------------
NMGRERR 265 MESSAGE This link name does not exist for this router
NI. (NMGRERR 265)
CAUSE The user entered a nonexisting link name and
pressed the Link Routing key.
ACTION If an incorrect link name was specified, correct
the link name and try again. If link name is
correct but the link has not yet been
configured, configure the link.
--------------------------------------------------------------------------
NMGRERR 266 MESSAGE The path report for the node is full; no new
address can be added. (NMGRERR 266)
CAUSE The user attempted to add an address to the
network directory for a node whose path report
is already full. No additional addresses can be
added.
ACTION Go to the Network Directory Data screen for the
node and delete some of the addresses assigned
to the node name.
--------------------------------------------------------------------------
NMGRERR 267 MESSAGE The node name must be configured first.
(NMGRERR 267)
CAUSE The node name was not configured.
ACTION Go to the Main screen and configure the node
name.
--------------------------------------------------------------------------
NMGRERR 268 MESSAGE Missing IP address. (NMGRERR 268)
CAUSE The user neglected to enter the IP address in
the appropriate field.
ACTION Enter the IP address and try again.
--------------------------------------------------------------------------
NMGRERR 269 MESSAGE You must enter a backup configuration file name.
(NMGRERR 269)
CAUSE The user pressed the Open Config or Create
Config key with no file name specified in the
backup configuration file name field.
ACTION Enter a valid file name in the backup
configuration file name field and press Open
Config or Create Config again.
--------------------------------------------------------------------------
NMGRERR 270 MESSAGE Cannot open node information file for ADDVC or
PURGEVC. (NMGRERR 270)
CAUSE NMMGR was unable to open the file whose name was
specified in the ADDVC or PURGEVC command,
either because the file does not exist or
because a more serious file system error
occured.
ACTION 1. The file name specified may not exist. Try
the command again with a file that exists.
2. A more serious file system error may have
occured. See the accompanying file system error
message for resolution.
--------------------------------------------------------------------------
NMGRERR 271 MESSAGE You must open the configuration and directory
files first. (NMGRERR 271)
CAUSE The user attempted to perform an ADDVC or
PURGEVC command without first opening the
configuration and/or directory files.
ACTION Open a configuration file with the OPENCONF
command and a directory file with the OPENDIR
command.
--------------------------------------------------------------------------
NMGRERR 272 MESSAGE The link exists, but its type is not correct for
this NI. (NMGRERR 272)
CAUSE The user specified an existing link name on one
of the custom NI update screens. The selected
link's type was not correct; that is, a LAPB
type link was specified for an X.25 NI.
ACTION Enter the name of a link with the correct type
or delete the link configuration.
--------------------------------------------------------------------------
NMGRERR 273 MESSAGE The selected card number is not configured with
a card type. (NMGRERR 273)
CAUSE At the DTC Configuration screen, the user
selected a card number and pressed the Config
Card key. No type was entered in the Type field
associated with the selected card.
ACTION Fill in a card type in the Type field for the
selected card and press the Save Data key. Type
must be "D" for direct connect, "M" for modem,
or "P" for PAD. Once the data has been saved,
select the card and press the Config Card key
again.
--------------------------------------------------------------------------
NMGRERR 274 MESSAGE The config is valid, but could not be backed up;
Type ERR for info. (NMGRERR 274)
CAUSE The user pressed the validate key and the
configuration validated correctly, but NMMGR
could not back up the configuration file because
an error occured while writing the backup file.
ACTION Type ERR on the command line and view the errors
that occured. After correcting the errors,
retry the validate operation.
--------------------------------------------------------------------------
NMGRERR 275 MESSAGE You must specify either a switched or permanent
virtual circuit address. (NMGRERR 275)
CAUSE The user failed to enter either a valid switched
virtual circuit address or a valid permanent
virtual circuit address. One or the other must
be entered.
ACTION Enter a valid address as appropriate for the VC,
either switched or permanent.
--------------------------------------------------------------------------
NMGRERR 276 MESSAGE The NI name exists, but its type is not X.25.
(NMGRERR 276)
CAUSE The user entered the name of an existing NI and
specified the type as X.25. The NI exists but
its type is not X.25.
ACTION If you are updating an existing NI, enter the
correct NI name and the correct type and try
again. If you are configuring a new NI, enter a
name that has not already been used and try
again.
--------------------------------------------------------------------------
NMGRERR 277 MESSAGE Duplicate address key; it must be unique for the
X.25 NI. (NMGRERR 277)
CAUSE The user specified an address key that was not
unique for the NI specified at the VC
Configuration screen or through the ADDVC
command.
ACTION Go to the SVC and PVC paths screens for the NI
to see the names that are already configured.
Choose an address key that is not used in either
of these screens.
--------------------------------------------------------------------------
NMGRERR 278 MESSAGE Missing quote; the IP address must be enclosed
in quotes. (NMGRERR 278)
CAUSE While using the ADDVC command in maintenance
mode, the user forgot to enter the IP address
with either an opening or a closing quote.
ACTION Re-issue the command with the correct IP address
enclosed in quotes.
--------------------------------------------------------------------------
NMMGRERR 280 MESSAGE The source path was not found. (NMGRERR 280)
CAUSE The path to the subtree to copy was not found.
ACTION Check to make sure you have the correct file and
check the source path spelling.
--------------------------------------------------------------------------
NMGRERR 281 MESSAGE The destination path was not found. (NMGRERR
281)
CAUSE The destination path, which is created by
substituting any destination IDs into the source
path, was not accessible. The path in the file
was not an exact match, or the destination path
was missing.
ACTION Check the source and destination path spelling
and make sure you have the correct file.
--------------------------------------------------------------------------
NMGRERR 282 MESSAGE The destination path exists. Use the overwrite
option to replace. (NMGRERR 282)
CAUSE The destination path already exists in the file.
ACTION Enter 'Y' in the overwrite option.
--------------------------------------------------------------------------
NMGRERR 283 MESSAGE Source and destination do not map with each
other correctly. (NMGRERR 283)
CAUSE The source and destination paths must start at
the same spot in the NMMGR schema. Most likely
the user attempted to change the name of an item
in the destination of a subtree copy.
ACTION Check to see if the item that was changed was a
select or type select identifier. If not, that
will cause the subcopy to fail.
Check to make sure that any destination type
select items, if changed, were changed to items
of the same type (as in LAN to LAN, instead of
LAN to router).
--------------------------------------------------------------------------
NMMGRERR 284 MESSAGE Internal ERROR in subtree copy. (NMGRERR 284)
CAUSE Internal error.
ACTION See "Submittting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 285 MESSAGE A non select screen id was changed in the
destination path. (NMGRERR 285)
CAUSE Incorrect ids in the destination path.
ACTION Check ids in the destination path. Make sure
that they are all select nodes.
--------------------------------------------------------------------------
NMGRERR 286 MESSAGE Illegal path name identifier in destination path
name. (NMGRERR 286)
CAUSE A path id in the destination pathname is not
legal.
ACTION Check the destination path id for typing
mistakes.
--------------------------------------------------------------------------
NMGRERR 287 MESSAGE Invalid destination path--path too long.
(NMGRERR 287)
CAUSE The source and destination paths must be the
same length. When entering data on the subtree
copy screen, the source path may appear longer,
but should this be the case, the destination
path uses IDs from the source path. This error
is generated in the other case when the
destination path is longer than the source path.
ACTION Check to make sure that you are not missing path
ids in the source path.
--------------------------------------------------------------------------
NMGRERR 288 MESSAGE Source path contains empty path identifiers.
(NMGRERR 288)
CAUSE This occurs when the user leaves path IDs empty
in the middle of the source path field on the
copy subtree screen.
ACTION Check the source path, and fix the path, so that
none of the source path IDs in the middle of the
source path are blank.
--------------------------------------------------------------------------
NMMGRERR 289 MESSAGE The source and destination may not be the same
file and path. (NMGRERR 289)
CAUSE The user is attempting to copy over the source
data, which is not allowed.
ACTION Select another file or path to copy into.
--------------------------------------------------------------------------
NMGRERR 290 MESSAGE The file does not exist or cannot be opened.
(NMGRERR 290)
CAUSE An NMCONF file to be opened for a copy could not
be accessed.
ACTION Check the spelling of the filename. Do a "listf
<filename>" to see if file exists.
--------------------------------------------------------------------------
NMGRERR 291 MESSAGE Source path is not allowed to be copied.
(NMGRERR 291)
CAUSE The source path is not permitted to be copied by
the subtree command.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 300 MESSAGE Internal NMMGR error: cannot close current
Network Directory. (NMGRERR 300)
CAUSE This is an internal error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 301 MESSAGE Internal NMMGR error: corrupt file likely.
(NMGRERR 301)
CAUSE This an internal error.
ACTION The directory file is probably corrupt and
should be replaced by a copy from a back-up
tape. Restore both data and key files. See
"Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 302 MESSAGE No next page of node names. (NMGRERR 302)
CAUSE This is an informative message that is issued
when the user hits NEXT PAGE and there are no
subsequent names in the directory, or when the
name supplied does not exist.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 303 MESSAGE No previous page of node names. (NMGRERR 303)
CAUSE This is an informative message that is issued
when the user hits PREV PAGE and there are none,
or when the name supplied does not exist.
ACTION None.
--------------------------------------------------------------------------
NMGRERR 304 MESSAGE A node with the same name, type, and
global/local setting already exists. (NMGRERR
304)
CAUSE This is an informative message that is issued
when the user tries to add a node name that
already exists into the directory. The name is
probably misspelled, or the wrong global/local
setting was given.
ACTION Correct the node name, the global/local setting,
the type, and/or the enable flag.
--------------------------------------------------------------------------
NMGRERR 305 MESSAGE Cannot find a node with this name, type, and
setting. (NMGRWARN 305)
CAUSE This is an informative message that is issued
when the user tries to delete or update a node
name that does not exist. The name is probably
misspelled, or the wrong global/local setting
was given.
ACTION Correct the node name, the global/local setting,
the type, and/or the enable flag.
--------------------------------------------------------------------------
NMGRERR 306 MESSAGE RENAME requires a new node name and/or new
global/local setting. (NMGRERR 306)
CAUSE This is an informative message that is issued
when the user tries to rename a node name
(global/local setting), but both the new node
name and new global/local setting were omitted.
ACTION Specify the missing information.
--------------------------------------------------------------------------
NMGRERR 307 MESSAGE The current node name entry has been deleted by
another user. (NMGRERR 307)
CAUSE The user attempted to delete or update a network
address, or path data, but another user who is
modifying the same directory file has just
deleted the entry.
ACTION Coordinate update activities with other user(s).
--------------------------------------------------------------------------
NMGRERR 308 MESSAGE Duplicate IP address. (NMGRERR 308)
CAUSE The user attempted to add a network address that
already exists in the current path report.
ACTION Either choose a different network address, or
make sure you are updating the correct node name
global/local setting.
--------------------------------------------------------------------------
NMGRERR 321 MESSAGE Not enough room in the path report list for this
addition. (NMGRERR 321)
CAUSE This is an informative message that is issued
when the user attempts to add or update a path
in a very large path report list. This can
happen only on very large gateway nodes, such as
a node with more than 15 network addresses.
ACTION See "Submitting an SR" at the beginning of this
appendix. (Request an expansion on the limit on
path reports.)
--------------------------------------------------------------------------
NMGRERR 322 MESSAGE Internal NMMGR error - corrupt path report list
data. (NMGRERR 322)
CAUSE Severe error indicating an internal logic error.
ACTION See "Submitting an SR" at the beginning of this
appendix.
--------------------------------------------------------------------------
NMGRERR 323 MESSAGE No directory file open. (NMGRERR 323)
CAUSE Maintenance mode interface: An informative
message that is issued when a user gives a
command prior to completing a successful OPENDIR
command.
ACTION Open or create a directory file using OPENDIR,
then reissue the command.
--------------------------------------------------------------------------
NMGRERR 324 MESSAGE Cannot find this entry in the directory.
(NMGRWARN 324)
CAUSE Maintenance mode interface: An informative
message that is issued when no directory entry
(either global, local, or neither - if no
;GLOBAL or ;LOCAL keyword given) could be found
in the directory matching the specified node
name.
ACTION Correct the node name.
--------------------------------------------------------------------------
NMGRERR 325 MESSAGE Cannot open source file / wrong file type.
(NMGRERR 325)
CAUSE Maintenance mode interface: An informative
message issued when an invalid file was
specified in a MERGEDIR command. Possible
causes are:
* Nonexistent file
* Wrong type of file (not directory or
configuration file)
* Security violation
* A system file name was given
* Other file system problem
ACTION Correct the filename.
--------------------------------------------------------------------------