03-16-2018 07:03 AM
Curious if anyone is successfully using the commvault application within their Palo Alto application policies? We tried it and it is not working at all to detect our CommVault application traffic. The details on the application itself seem quite old.
03-16-2018 08:01 AM
was there a related question about custom signatures? 😛
the commvault app was last updated in august, so it's possible something was changed in the latest incarnation that causes it to not be identigfied properly in App-ID, you could reach out to support to have this investigated (they'll need packetcaptures and logs to verify)
03-16-2018 10:05 AM
Or if you really hate dealing with support and simply want the traffic to identify as CommVault, you could do like I've done and simply utilize an Application override policy and setup the traffic to match to commvault. It's lazy and stops the inspection at Layer4, but I still get to yell at my backup admin for using an ass-ton of bandwidth 😉
03-19-2018 08:51 AM
I'm just confused as to why the standard ports are: tcp/dynamic and not itimized out ports\protocols.
03-19-2018 08:57 AM
I don't know enough about how commvault is actually configured to properly answer that question. I would assume that it's to do with the fact that you can customize commvault's ports and that it doesn't utilize only a standard set of ports by default?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
