Client GUI warning message overview

Warning message scenarios

Warning messages in the NFM-P client GUI provide an error recovery mechanism to inform you when:

• information has been entered incorrectly

• additional information is required

• the operation you are attempting cannot be completed

• a change to a configuration sub-form is not committed until the parent form is committed

• an operation that may result in service disruption is requested

• a configuration form for an object is open that can potentially conflict with a previously opened form

When an error condition is encountered that the NFM-P client has not anticipated, a Problems Encountered form is displayed. See Overview for more information.

You can use the client GUI to suppress warning messages within containing windows. See the NSP NFM-P Classic Management User Guide for more information.

Incorrect data entry

When incorrect information is entered for a parameter, a warning message that describes the error is displayed. For example, when you configure a password for a site user, the value entered for the Password parameter and the Confirm Password parameter must match. If they do not match, a warning message is displayed.

Additional information required

When the value selected for a parameter has a condition that requires another parameter to be configured, a warning message indicates the missing information that is required. For example, when you configure a new or existing user with MD5 or SHA as the value for the Authentication Protocol parameter, a password must be configured. If you do not configure a password, a warning message is displayed.

The warning message indicates the information that is required. In this case, click OK to close the dialog box, and configure the New Authentication Password and Confirm New Auth Password parameters.

Unable to complete requested action

Warning messages are used to indicate that a specific action cannot be completed. These warnings may occur when you try to create a new object or modify an existing object that results in an unsupported configuration. For example, the message “Can't bind LSP to a non-mpls service tunnel“ indicates that you cannot bind an LSP to a service tunnel that is not configured with the MPLS protocol.

These errors can be difficult to resolve and may require that you retrace your steps to determine the cause of the warning. Check the documentation to ensure that you are following procedures correctly.

Commitment of changes from a form and its sub-forms

From a configuration form, you can open sub-forms that require completion before you continue with the parent form. For example, when you create a VLL service, the Create Service Site form opens during one of the configuration steps. After you configure parameters in this sub-form and click on the Finish button, a warning message is displayed.

Changes entered in the sub-form are not committed until you click OK or Apply on the parent form. When you click OK or Apply on the parent form, a final confirmation is displayed.

When you click Yes for the last confirmation, the changes to the parent or sub-forms are committed.

Service disruption warning

A service disruption dialog box is displayed when you perform an action that may be service-affecting. For example, if you attempt to shut down a daughter card, a warning message is displayed.

As indicated by the warning message, the action you are about to perform may cause a disruption to customer service because of a potential dependency that another object or service has on the current object. Click View Dependencies to indicate the number of services that may be affected by the action.

Verify that the requested action is appropriate. Click on the checkbox beside the statement “I understand the implications of this action” to continue with the action.

Duplicate configuration form conflicts

There are multiple ways to access a configuration form for the same object. For example, you can view the configuration form for a port by choosing Manage→Equipment, or you can access the port by clicking on the port object in the expanded navigation tree. When you try to perform both accesses, a warning message is displayed.

When this warning message is displayed, another form is open for the same object. When two forms are open concurrently for the same object, there may be unexpected results because changes committed from one form are not reflected in the other form.