After loading a configuration on another PacketShaper, I get a matching rule configuration error.

Products

• PacketShaper

Issue/Introduction

My PacketShaper has the following traffic tree:

Inbound
  SubnetClassA (subnet-based) <--Discovery is enabled
     SSL
     HTTP
     Default

After I loaded this configuration on another PacketShaper, each of the auto-discovered child classes of Inbound/SubnetClassA had the following configuration error message:

Matching Rule incompatible with parent...

However, on the original PacketShaper I didn't see this error message and classification worked perfectly.

 

Resolution

Check the matching rules of the parent class (Inbound/SubnetClassA). Is the Server Location set to Inside, Outside, or Any? If the Server Location is set to Inside or Outside (not Any), this will cause problems when loading the configuration on another PacketShaper. The matching rules of the auto-discovered child classes will have the Server Location set to Any, which is seen as an incompatible matching rule with the parent's Inside or Outside Server Location matching rule.

To fix this problem, you can either:

• Edit the matching rule of the parent class and change the Server Location to Any.
• Delete the auto-discovered child classes (the ones with configuration errors) and let them re-discover.

To avoid this problem in the future, set the Server Location of the parent class to Any (not Inside or Outside).