Overview

Functions that require CLI

You can perform most NE management functions using the NFM-P client GUI. Functions such as the following, however, require CLI access to a managed NE:

• validating GUI configuration actions

• configuring items that the GUI cannot, such as LI user access

• troubleshooting using device debug files

The NFM-P client GUI provides CLI access to the managed NEs from the main menu and from NE contextual menus in topology maps and navigation trees.

Security

Scope of command roles and user permissions on the cli package control CLI command access on an NE. The user permissions are set when security is configured on the NE locally or by using NFM-P configuration forms. See the section on NE user and device security in the NSP System Administrator Guide for information about setting NE access privileges.

Note: When you use a CLI to change security parameters on an NE, the changes may not be synchronized with the NFM-P and subsequently not displayed in the GUI. For security reasons, the NFM-P cannot retrieve parameters such as passwords from an NE. To ensure that the security parameters are synchronized, you must use the client GUI to change the values.

Note: One CLI login failure from the NFM-P client GUI may generate more than one login failure message in the NE session logs. This is because the CLI window is opened using an internal utility rather than a command shell, and the utility may attempt the login more than once for various reasons, for example, excessive retries or the use of multiple authentication sources.

vi editor support

On a 7450 ESS, 7750 SR, or 7950 XRS, you can use the vi editor to modify local files. The vi editor is available in NFM-P Telnet and SSH sessions. The vi editor supports the standard vi navigation keys as well as the cursor keys (which are often called the arrow keys). See the appropriate device documentation for information about the supported vi commands and functions for a specific device.