Command Processing
You can access both local or remote Node Manager services through the User Interface modules. Typical user command entry processing is illustrated in Figure 4"2.
Command Entry
NM |
|
|
| NM2 | Command Formatting | ||
|
|
| |||||
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local Command Execution
NMGR
Command Transmission
To Remote NMGR
Figure 4%2. Typical User Command Processing Through Node Manager Modules
NM and NM2 Modules
The NM module provides the direct user interface for command entry. It provides the NM> prompt on a user terminal, and awaits a user command input.
The NM2 module is scheduled by NM and is primarily used for command parsing. NM2 deciphers a command and verifies that the command is valid. In addition, NM2 provides default values for optional parameters not specified on command entry. If the command is valid, it is mapped into a packet that conforms to the IEEE 802.2 and 802.3 Standards, and the HP Network Management protocol. Subsequently, the packet is returned to NM and is passed to the NMGR module for execution.
For commands that require a response to the user, the local NMGR module (see discussion below) returns an appropriate message to NM where it is formatted and displayed on the user's terminal.
Command Entry Errors
For unrecognized commands, or commands improperly entered, NM2 returns one or more descriptive error messages to the user.
Any system or software error that NM or NM2 cannot handle is returned to the user terminal.
4%2 Node Manager Operations