Avaya QoS Manager 2.0 Uživatelská příručka stáhnout pdf (Strana 17)

Avaya QoS Manager User Guide 11

Getting Started with Avaya QoS Manager

Saving Configuration Changes

Policies are stored on the modules for which they were created. There

are two levels of applying policy changes to Avaya QoS Manager:

 Running Changes

- Changes are applied to the Policy, but are

not saved.

 Committed Changes

- Changes are saved to the module.

Running Changes

After finalizing all changes to the Policy, the changes must be applied to

the Policy List.

To apply the changes to the module, click . The configuration

changes are applied to the module.

The changes will remain in effect until the module is reset. When the

module is reset, it is configured with the last saved configuration. All

changes that are applied, but not saved, are lost.

Committed Changes

To make configuration changes permanent, the changes must be

committed (saved) to the module.

To commit the configuration to the module:

Click .

Select

File > Commit

. The changes are saved to the module.

* Note: The commit operation may take up to 20 seconds. Avoid

running other operations while committing polices to the

module.

* Note: Commit can only be used when a specific module is selected

in the Tree View.

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 64 65

Žádné komentáře

Avaya QoS Manager 2.0 Uživatelská příručka Strana 17