Video Screencast Help

Policy Manager Connected: NO on LAN Enforcer

Created: 19 Oct 2012 | 1 comment

As stated in the title, we have a LAN Enforcer showing as following:

Enforcer# show status
Enforcer Status:                ONLINE
Policy Manager Connected:       NO
Policy Manager:        HTTP 8014
Packets Received:               77719
Packets Transmitted:            68600
Packet Receive Failed:          0
Packet Transfer Failed:         0
Enforcer Health:                EXCELLENT
Enforcer Uptime:                0 days 17:30:00
Policy ID:                      18/10/2012  16:26:47

Enforcer# show configure
Please wait for a moment...

Network Interface Setting:
eth0      Link encap:Ethernet  HWaddr 00:E0:ED:1E:5C:38
          inet addr:  Bcast:  Mask:
          RX packets:78667 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69249 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14898989 (14.2 MiB)  TX bytes:10874583 (10.3 MiB)

lo        Link encap:Local Loopback
          inet addr:  Mask:
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:726 (726.0 b)  TX bytes:726 (726.0 b)

Route Table:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface   U     0      0        0 eth0         UG    0      0        0 eth0

DNS Setting:

Policy Manager Settings:
Port:                     8014
Protocol:                 HTTP
Hash of Preshared Secret: B5066AAB000A2B5370E88C9D05B37990
Preferred Group:          NAC-BLAH-B

NTP: disabled

On the SEPM, inside the scm-server-0.log we see many NullPointerException like this

2012-10-18 22:46:44.793 THREAD 25 SEVERE: Unknown Exception in: com.sygate.scm.server.task.EnforcerCompilerTask
    at com.sygate.scm.server.task.EnforcerCompilerTask.compileCommonProfile(
    at com.sygate.scm.server.task.EnforcerCompilerTask.compileProfile(
    at java.util.TimerThread.mainLoop(

What's wrong between them?

Comments 1 CommentJump to latest comment

cemilebaşak's picture


Restart the enforcer and after that you can see it connected.

If not you must look the logs in enforcer as well.


Cemile Denerel BAŞAK

Note: Please mark as solution if its help you.