QoS Manager - How to define a Traffic Class filter

Products

• CA Spectrum

Issue/Introduction

This article explains the rules and provide some examples on how to define a Traffic Class Filter, in order to prevent specific QoS's to be displayed under QoS Manager after running a QoS discovery.

Environment

Release : Any supported Spectrum version.

Resolution

Let's consider the contents of the following screenshot for reference:

Resolution:

We can see in the above image that the parent name ("system-cpp-policy_QOS_Policy") is the prefix for all the child items displayed in the QoS tree.

In the OneClick view, we are prefixing with the parent name "system-cpp-policy_QoS_Policy" for every child... But when discovering the QoS, we receive only the child names.

So, basically we CANNOT refer to the parent name/prefix when creating a Traffic Class Filter. But only to the suffixes (displayed in green).

Example 1: Preventing the "system-cpp-policy_Qos_Policy_system-cpp-default_Class" to be discovered/displayed.

Here we have the following structure:

system-cpp-policy_Qos_Policy -> Prefix
system-cpp-default_Class -> Suffix

The Traffic Class Type must be defined as "exclusive".

The filter to be configured should be :

system-cpp-default*

Example 2 - Preventing a single QOS  (system-cpp-policy_QoS_Policy_system-cpp-default_Sim37552:S10057P0ED1.xxx.com)  to be displayed:

 

The following 2 filters could be used:

system-cpp-default_Sim37552*

or

system-cpp-default_Sim37552:S10057P0ED1.xxx.com

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/22-2/managing-network/qos-manager/qos-manager-discovery-and-modeling.html#concept.dita_6e1aedb5ac596c28ab0f05ebb08913fbdae3a405_RunanOnDemandQoSDiscovery