Panorama object service search not finding objects when searching on destination port

Running Panorama 8.1.3

Having an issue that when in Panorama that when I put a destination port in the search bar, it only matches against the name.

When I go to the gateway, and do the same search it will find the service objects with the detination

App id “Non-syn-tcp”

I see a lot of non- syn-tcp from from few specific zone. I am sure that there is no asymmetric routing. If that has to be the case how to determine exact causing factor.

Thanks

leaf and spine and security

Hi,

In a spine and leaf ( vpc ) ,where we should place the firewall  to protect the data center ? 

If  we use layer 3 firewall  all routing  process will be shifted to the fw, spending huge amount on spine won't be beneficial ? 

Layer 3 or layer 2  reco

Route & Path Selection

I have a Cisco backround & I am currently studying Virtual Routers & Static Routes in the PA 8.0 admin guide.  I am trying to understand how Metrics are used in the firewall because it sounds like Administrative Distance does the same thing.  Can som

Global Protect Certificate

Hi

I configured global protect, but when clients try to connect through the agent, they got "Gateway "name":The server certificate is invalid, please contact your IT administrator".

For the configured certificates, I configured self-signed certificat

Change Management IPs

Hi

We have Panorama managing 6 PA FWs (3 HA Clusters). We want to change the management net of Panorama and Firewalls.

Now logically we will change management IP of Panorama first. Then the Firewalls will lose connectivity and probably logs will be lo

PA-200 HA Sync

Hi,

I have a message when I attempt to run a commit:

"The running configuration is not currently synchronized to the HA peer, and therefore, this commit will only be applied to the local device.

Please synchronize the peers by going to the dashboard an

FQDN refresh problems

Hell guys,

We have a problem that the FQDN refresh fails nearly everytime. What I mean with "nearly" everytime is, that there are periods in which the FQDN refresh is running smoothly, and then suddenly it fails again.

Example: A few days ago the FQDN