One Touch Data Policies

The PolicyView One Touch Data Screen displays all of the Data Servers that have been configured with a One Touch Data Policy and the status of the policy on the LDAP Server:

• Saved - The policy has been successfully written to the LDAP Server.
• Unsaved - The new policy, or modified policy has not been saved to the LDAP Server
• Error - An error condition has made it impossible to write the policy to the LDAP Server.

The screen is used to create, edit, or delete one of the following One Touch Data Policies:

• Platinum - provides the highest quality of service (and maps to a firmware priority of 7)
• Gold - provides the next-highest quality of service (and maps to a firmware priority of 5)
• Silver - provides the next-highest quality of service (and maps to a firmware priority of 3)
• Bronze - provides the same quality of service as best effort (and maps to a firmware priority of 1)

Creating a One Touch Data Policy

Select a Priority from the drop-down menu, then click on the Create icon. Enter the IP address of the Data Server in the Server IP Address field, and click Create. The Data Server will appear in the table with the Status "Unsaved". Click on the Save icon, to save the Policy to the LDAP Server. The Priority selected will be applied to all Data Servers in the table. When you are finished, click on Notify All to apply the policy to all of the switches in the network.

Important Note: Clicking the Notify All button causes all QoS-enabled switches to flush their policy tables and reload policies from the LDAP Server, which is very expensive in terms of switch resources and time. If any One Touch Data policy has already been defined, the switch(es) to which the policy is assigned will also re-cache its policy tables. It is recommended that you verify all policies that you have created and apply them at the same time to minimize switch downtime.

Applying a One Touch Data Policy

When you click the Notify All button, the policy(ies) is applied to all switches in the network. To view the status of the re-cache operation, click on the Status button to view the Devices Pending Notification Table. In addition, you can view the success or failure of the re-cache operation for each switch in the policy.log file of the Audit application, including an indication of any error that may have occurred. Any errors that occur will also be reported in the server.txt file, in the Audit application. Note that the re-cache operation for each switch occurs in a separate thread and may take some time.

Editing a One Touch Data Policy

Select a Priority from the drop-down menu. The status of all of the Data Servers in the table will change to "Unsaved". Click on the Save icon, to save the Policy to the LDAP Server. The Priority selected will be applied to all Data Servers in the table. When you are finished, click on Notify All to apply the policy to all of the switches in the network.

Important Note: Clicking the Notify All button causes all QoS-enabled switches to flush their policy tables and reload policies from the LDAP Server, which is very expensive in terms of switch resources and time. If any One Touch Data policy has already been defined, the switch(es) to which the policy is assigned will also re-cache its policy tables. It is recommended that you verify all policies that you have edited and apply them at the same time to minimize switch downtime.

Deleting One Touch Data Policy

To delete a One Touch Data Policy(ies), select the server(s) in the table and click on the Delete icon, then click OK at the confirmation prompt. When you click the OK button:

• All One Touch Data policies for the servers you selected are removed from the LDAP Server.
• All One Touch Data policies for the servers you selected are removed from switch attributes in the LDAP "role" objects.
• The server(s) are removed from the table.
• A confirmation message is displayed when the LDAP Server has been successfully updated. The success of the operation is also reported in the policy.log file in the Audit application.
• An SNMP message is sent to each QoS-qualified device in the List of All Discovered Devices, informing that the information in the LDAP repository has changed and commanding the devices to update their cached policies with the current information from the LDAP repository. Note that the re-cache operation for each switch occurs in a separate thread and may take some time. Be sure to check the policy.log file in the Audit application for the re-cache status of each switch.

Example of a New One Touch Policy (or Edit Policy) Operation

Let's say Platinum was selected as the priority for the following two Server IP addresses:

164.178.32.107
164.178.33.51

When saved, the following policies are created and written to the LDAP Server:

OneTouchDR$S164.178.32.107
Condition specifies traffic originating from source IP address 164.178.32.107
Action specifies Platinum QoS for this traffic

OneTouchDR$D164.178.32.107
Condition specifies traffic transmitted to destination IP address 164.178.32.107
Action specifies Platinum QoS for this traffic

OneTouchDR$S164.178.33.51
Condition specifies traffic originating from source IP address 164.178.33.51
Action specifies Platinum QoS for this traffic

OneTouchDR$D164.178.33.51
Condition specifies traffic transmitted to destination IP address 164.178.33.51
Action specifies Platinum QoS for this traffic

Please note that the names beginning with "OneTouchDR" are the names used for the policies in the LDAP Server. Within the PolicyView QoS application, all One Touch Data policies are referred to by the generic composite name OneTouchDR, no matter how many individual One Touch Data policies have been written to the LDAP Server. One Touch Data rules that have been created automatically by PolicyView can be viewed in the Expert mode window.