User guide

Troubleshooting Policies and Profile Management Overview (QoS Deployments Table)
AlliedView NMS Administration Guide (Configuring Network Services)
6-130
6.12 Troubleshooting Policies and Profile Management
6.12.1 Overview (QoS Deployments Table)
Since QoS Deployment has interrelationships with Profiles and Ports, there are some help procedures to understand these rela-
tionships and to use them to troubleshoot problems that may occur.
To view the status of policies, there is the QoS Deployments table, which lists the attributes of the policies and their deploy-
ment status. To access this table select Network Services Data -> QoS Deployments, as shown in the following figure.
FIGURE 6-110 QoS Deployment Status
This table is used in many of the procedures below.
6.12.2 Determine which QoS Policy is Assigned to a Port
1. Locate the port in the Network Inventory -> Ports table.
2. The “Profile” column will indicate which NMS Profile is assigned to the port.
3. If the Profile Name has a “*” after it, then the NMS Profile is out-of-sync with the deployed port parameters. It should be
redeployed to the port so that the port is in-sync with the Profile configuration.
4. Once the NMS Profile is in-sync, locate the Profile in the Network Services -> Profiles table and right-click on the Profile
and select the View Profile item.
5. The “QOS Policy” parameter will show the name of the QoS Policy that has been assigned to the port.
6.12.3 Determine Whether a QoS Policy is Deployed and In-sync on a Device
1. Locate the Node (i.e. device) and NMS Policy in the Network Services Data -> QoS Deployments table.
2. If there is not a row for this in the table, then the QoS Policy has not yet been deployed to the device. If so, go to the Net-
work Services Data -> Profiles table, select/create a Profile that assigns the desired QoS Policy and right-click to deploy
the profile to the desired device.
3. If there is a row in the QoS Deployments table associated with the Policy and device, then verify that the QoS Policy
deployment is in-sync with the QoS components on the device. This is reflected in the Deployment Status column. The sta-
tus should show “no_changes”.
4. To re-check that the device policy has not been recently removed, right-click on the deployment row and select Update
Deployment Status. This will cause the NMS to go to the device and verify that the policy is still there.
Caution: QoS components on the device that are associated with an NMS policy should not be edited via CLI. These changes
may not be detected by the NMS, in which case the status will continue to show “no_changes”. For efficiency
reasons, the NMS will 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 rede-
ploy 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.