For some reason, floating network devices have stopped working after the
upgrade from 3.8 to 4.0.5.
All floating network devices are configured to have a trunk port and allow
a set of vlans in the port.
However, when a floating network device with a trunk port is connected to a
switch managed by PacketFence, the port-security mac address violation is
not received, thus no action is handled by PF.
On the other hand, if the port of the floating network device is in access
mode, the MAC is discovered.
But when PF tries to find the MAC in the switch, it complains with:
Aug 29 15:18:03 pfsetvlan(15) WARN: couldn't get MAC at ifIndex 10039. This
is a problem. (pf::SNMP::_getMacAtIfIndex
Trying to run:
/usr/local/pf/bin/pfcmd_vlan -switch 192.168.0.254 -ifIndex 10116 -getMAC
-verbose 4
show the same error:
DEBUG - instantiating new SwitchFactory object
DEBUG - creating new pf::SNMP::Cisco::Catalyst_2960 object
DEBUG - start handling 'getMac' command
WARN - couldn't get MAC at ifIndex 10116. This is a problem.
Should a floating network device that will be multi-vlan have the port in
trunk mode by default?
Will PF configure the uplink port on the floating network device?
If I force to finish the setup on the switch port (set the native vlan),
the floating network device works as expected.
Any hint?
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
