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

[william.dolbow]

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 port match.

This is important as for some reason many of our service names dont have the port number in the name.

Anyone have a reasonable workaround to this.  I dont want to always have to jump down to a gateway to find the service name to jump back up to the panorama level to stage the rule.

[Rajesh12]

Hello @william.dolbow,

If I understand correctly, when you are doing global search on panorama with destination port number, corresponding service name created for that port is not showing up? I do tested it on my panorama (7.1.16) and it had given me all its references on all firewalls. Is this what you are looking for? Also what type of admin role access do you have on Panorama?

[JW6224]

Could be a bug in 8.1.3.  You'd need to check with TAC.  To confirm, you're not using Global Find's Search, right?

I am afraid it shows my roots in PIX/ASA, but I always prefer the CLI, even on Panorama:

admin> set cli pager off
admin> set cli config-output-format set
admin> configure
Entering configuration mode
[edit]
admin# show device-group Your_DG_Goes_Here service | match ldap
set device-group Your_DG_Goes_Here service ldap protocol tcp port 389
[edit]
admin# show device-group Your_DG_Goes_Here service | match "port 389"
set device-group Your_DG_Goes_Here service ldap protocol tcp port 389
set device-group Your_DG_Goes_Here service tcp-389 protocol tcp port 389