- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-15-2011 02:40 AM
Since application and threads update 241-941 we get the warning:
"Application 'snmp' requires 'ldap' allowed in the policy, but 'ldap' is denied in ...last rule"
In my humble opinion is "snmp" udp:161 while "ldap" is tcp:389, and of course the applications behind this ports are totally different. What could be the meaning of this weird warning?
greetings
Manfred
04-15-2011 03:55 AM
This is probably because the data is encoded in the same way and the decoder is shared. Since the two protocols have applicatiion-wise nothing to do with each other IMHO it is not acceptable to require ldap when only snmp is to be allowed.
04-15-2011 07:33 AM
I, too, have recently seen this. I became aware of it, though, when I upgraded from 3.1.6 to 3.1.8 a couple days ago.
-mike
04-15-2011 05:29 PM
We are aware of this issue and are currently investigating a fix.
04-17-2011 04:33 AM
may be PA thinks it is SNMPV3 ,that need authentication
04-20-2011 06:53 AM
Yeah i noticed this on my systems this morning. It doesn't make me happy that i have to add an extra service through when all i am needing is *gasp* snmp.
04-28-2011 02:00 PM
Do we have an ETA on when this will be fixed?
04-28-2011 03:14 PM
Fix will be available in the next content update version 244 on 5/3.
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!