Allied Telesis AT-iMG606BD Especificaciones descargar pdf (Pagina 183)

100

101

8. Troubleshooting Policies and Profile Management Determine whether a QoS Policy has the Desired Configuration

174

AlliedView NMS Administration Guide

not attempt to re-deploy policies that are determined to be in-sync. As a result, if underlying CLI QoS component changes

are suspected, you must force the NMS to redeploy the NMS policy.

To redeploy the NMS policy can be done in one of several ways:

• If the redeployment is only required on a single device, then right-click on the desired row of the QoS Deployment table

and select Undeploy Policy. This will remove the corrupt QoS components from the device. At this point redeploying the

port Profile will automatically update the QoS Policy on the device.

• If, on the other hand, you would like to update the QoS Policy on all devices, the simplest way to force the NMS to

redeploy the policy is to modify the QoS Policy definition and resave it. This will cause all deployments of that policy to

be flagged with a status of “policy_changed”, which will force all policies to be redeployed on the next Profile

deployment.

After the Update Deployment Status operation is performed, if the Deployment Status indicates a policy or device change

has been detected, then this may be the source of the problem. If so, go to the Network Services Data -> Profiles table, select

the associated Profile that assigns the desired QoS Policy and right-click to redeploy the profile to all of its assigned ports.

This will bring the devices back in-sync with the NMS Policy.

8.4 Determine whether a QoS Policy has the Desired Configuration

1. Locate the desired QoS Policy in the Network Services Data -> QoS Policies table, and right-click on it, selecting the View/

Edit Policy item. This will bring up the details of the Policy.

2. Confirm that the Policy Rules appear as intended. You can select the Show Errors button to re-check for any obvious

errors.

3. Analyze the Flow, Priority, and Traffic Descriptor definitions, by selecting their respective buttons at the bottom of the

window. Browse through the definitions associated with the policy.

4. Review the Flows and identify any rules with intersecting flows. Different devices/interfaces handle multi-rule matches

differently. Some interfaces will perform the actions only on the first rule to be matched by the incoming packet, while

others will perform actions from multiple matching rules, provided the actions do not conflict with each other.

Note: Please see the device specific details for handling intersecting rules.

5. If a configuration problem is discovered, modify the QoS Policy (including any flow or action descriptors that need to be

changed) to correct the problem, then save and close the window. This will flag all affected QoS Deployments to have a

Deployment Status of “policy_changed”.

Since Flows and Actions may be shared among multiple QoS Policies, you may find that changes to them will affect other

policies as well. These will also be reflected in the status entries of the QoS Deployments table, as explained in the next

subsection.

8.5 Redeploying Policies

To redeploy a policy for a device or set of devices, right-click on a row of the deployment table and select Redeploy Policy.

Refer to the following figure.

1 2 ... 178 179 180 181 182 183 184 185 186 187 188 ... 994 995

Comentarios a estos manuales

Sin comentarios

Allied Telesis AT-iMG606BD Especificaciones Pagina 183

Comentarios a estos manuales

Relacionado con productos y manuales para Gateways / Controladores Allied Telesis AT-iMG606BD