cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post

Identity Awareness' is not responding

I noticed  users are being shown in my logs. When I check the Device Stats I am getting this error message. 

Warning ('Identity Awareness' is not responding. Verify that 'Identity Awareness' is installed on the gateway. If 'Identity Awareness' should not be installed verify that it is not selected in the Products List of the gateway (SmartDashboard > Security Gateway > General Properties > Software Blades List).)

The blade is turned on and  AD is  connect. 

# adlog a dc
Domain controllers:
Domain Name IP Address Events (last hour) Connection state
============================================================================================================
x.local 192.168.100.X 28 has connection
x.local 192.168.100.X 601 has connection

x.local 192.168.100.X 36 has connection

I am in production right now and cant restart the firewall.  How do I restart just Identity Awareness?

Thank you,

Greg

0 Kudos
3 Replies

Re: Identity Awareness' is not responding

According to the Daemons page you can only do this via cpstop/cptart. Disabling the blade, pushing policy at enabling it again might do the trick.

Check $FWDIR/log/pepd.elg and $FWDIR/log/pdpd.elg for additional clues also.

____________
https://www.linkedin.com/in/federicomeiners/
0 Kudos

Re: Identity Awareness' is not responding

I opened pdpd.elg. 

Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory
Unable to open '/dev/fw6v0': No such file or directory

Is just keeps repeating. 

 

pepd.elg says the same thing. 

0 Kudos
Alex_Gilis
Silver

Re: Identity Awareness' is not responding

I've had this issue too when everything seemed to be working with Identity (rulebase, users in logs), it typically happened after a version upgrade or hotfix installation of the SMS. A reboot of the SMS solved the issue.

0 Kudos