Thanks I figured out the problem... it was using the wrong snmptrapd.conf 
file.. 

Thanks,
Dan


-----Original Message-----
From: Olivier Bilodeau [mailto:[email protected]] 
Sent: Monday, March 14, 2011 4:00 PM
To: [email protected]
Subject: Re: [Packetfence-users] A couple of problems..

Hi Dan,

Your earlier "Can't determine Uplinks for the switch -> do nothing" 
message could mean that snmp read / write communities are not correctly 
configured.

As for

> Mar 09 10:01:08 pfcmd(0) WARN: Can't change VLAN for mac
> 00:e0:4c:07:51:a8 because no open locationlog entry was found
> (main::vlan_reevaluation)

No open locationlog entry means that PacketFence doesn't know where the node 
resides. This should not happen if everything is properly configured (SNMP Trap 
communities, ...).

Can you connect to the database run the following query and send us the output 
it generates:

SELECT * FROM locationlog WHERE mac = '00:e0:4c:07:51:a8' ORDER BY start_time;

Thanks,
--
Olivier Bilodeau
[email protected]  ::  +1.514.447.4918 *115  ::  www.inverse.ca Inverse inc. 
:: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit for your organization - 
today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to