This Knowledge Base article describes a scenario where a newly configured Application Policy, which uses a non-directly connected host as the source criteria, is not being pushed to the device. It provides troubleshooting steps to resolve it.

• The Application Policy configurations can be seen in the Audit Logs section.
• Multiple attempts to reconfigure the Application Policy in different ways have been made without success.
• The policy works fine with directly connected hosts as source criteria.
• Only some routing instances configurations are pushed to the device, but the rest of the policy is not.
• Since the policy is not being pushed, the traffic hits the default policy and is therefore dropped.
• The configuration is managed by the Mist Cloud.
• Configuring a security policy directly on the CLI works, indicating that routing and security configurations are correct.
• A health check on the device does not reveal any related issues.

To address the misconfiguration issue where a non-directed connected host is not being pushed to the device as part of the Application Policy, follow these steps:

• 1. Add Non-Directed Host to Users Section:
  • Using the Network attached to the source of this traffic, add the non-directed connected host to the Users section.
  • 
• 2. Ensure Network Reference in LAN Configuration:
  • Ensure that the Network used in step 1 is already referenced in the LAN configuration. If it is not, configure it accordingly.
  • 
• 3. Reference the Network in the Application Policy:
  • In the Application Policies section, reference the same Network configured in step 1 and 2 as the source criteria, assuming that the rest of the criteria are ready.
  • 

Following these steps should resolve the misconfiguration issue and allow the Application Policy to be successfully pushed to the device.