Hi All,

I'm trying to upgrade to PF 2.2, and am running into a weird error.

I read through the upgrade docs, and made (I thought) the necessary
changes, but I must be missing something as Packetfence is complaining
that my VLANs are not "defined" when I connect a device.  (see log entry
below.)

This worked prior to the upgrade, but I can't find anything in the
UPGRADING document about needing to "define" VLANs prior to using them.

I would assume that this needs to be done in switches.conf, so I looked
through the switches.conf.rpmnew and couldn't spot anything.  My entry
for my test switch is below.

Can anyone tell me how exactly to "define" a VLAN?

Thanks,
Karl

[10.232.0.70]
type=HP::Procurve_2600
mode=production
vlans=7,8,9,10,11,30,31,32,37,39
normalVlan=9
registrationVlan=37
isolationVlan=11
macDetectionVlan=7
guestVlan=7
customVlan1=8
customVlan2=10
customVlan3=30
customVlan4=32
customVlan5=39
uplink=49,50
cliTransport=SSH
cliUser=XXX
cliPwd=XXX
cliEnablePwd=XXX
SNMPVersionTrap=2c
SNMPVersion=2c
SNMPCommunityWrite=XXX


May 18 14:30:25 pfsetvlan(1) INFO: nb of items in queue: 1; nb of
threads running: 0 (main::startTrapHandlers)
May 18 14:30:25 pfsetvlan(1) INFO: reAssignVlan trap received on
10.232.0.70 ifIndex 45 (main::handleTrap)
May 18 14:30:25 pfsetvlan(1) INFO: security traps are configured on
10.232.0.70 ifIndex 45. Re-assigning VLAN for 00:1f:16:18:e5:61
(main::handleTrap)
May 18 14:30:25 pfsetvlan(1) INFO: MAC: 00:1f:16:18:e5:61, PID: 1,
Status: reg. Returned VLAN: 9 (pf::vlan::fetchVlanForNode)
May 18 14:30:25 pfsetvlan(1) WARN: new VLAN 9 is not defined on switch
10.232.0.70 -> replacing VLAN 9 with MAC detection VLAN 7
(pf::SNMP::setVlan)
May 18 14:30:25 pfsetvlan(1) WARN: MAC detection VLAN 7 is also not
defined on switch 10.232.0.70 -> Do nothing (pf::SNMP::setVlan)
May 18 14:30:25 pfsetvlan(1) INFO: no VoIP phone is currently connected
at 10.232.0.70 ifIndex 45. Flipping port admin status (main::handleTrap)
May 18 14:30:29 pfsetvlan(2) INFO: nb of items in queue: 1; nb of
threads running: 1 (main::startTrapHandlers)
May 18 14:30:29 pfsetvlan(1) INFO: finished (main::cleanupAfterThread)
May 18 14:30:29 pfsetvlan(3) INFO: nb of items in queue: 1; nb of
threads running: 0 (main::startTrapHandlers)
May 18 14:30:29 pfsetvlan(3) INFO: down trap received on 10.232.0.70
ifIndex 45 (main::handleTrap)
May 18 14:30:29 pfsetvlan(3) INFO: security traps are configured on this
switch port. Stopping DOWN trap handling here (main::handleTrap)
May 18 14:30:29 pfsetvlan(3) INFO: finished (main::cleanupAfterThread)

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to