Hi Robin,
Not all trap types are relevant to PacketFence, and so the switches modules are
not written to handle all possible cases.
The message you see is the one that’s logged when a trap is not handled.
It does not in itself mean there is a bug either in the switch or in
PacketFence.
Tell us more about the problem you are trying to debug and we’ll see what we
can do about it.
Regards,
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
On Jan 16, 2015, at 10:28 , Kundert, Robin <[email protected]> wrote:
> I had tried to post this last week but something apparently went awry so I’m
> trying again.
>
> ---
>
> We are investigating problems some users are experiencing on the wired
> portion of our PacketFence (v4.2.2) controlled network. Along the way I
> noticed that certain switches (Edge-corE 4510 series) were involved and have
> been throwing errors like these since we hooked them up:
>
> Jan 11 06:55:54 pfsetvlan(5) WARN: unable to parse trapLine.. here's the
> line: 10.11.12.13||||||||| (main::startTrapHandlers)
>
> These also seem to be accompanied by things like:
>
> Jan 11 06:55:54 pfsetvlan(5) ERROR: Use of uninitialized value $ifType in
> numeric eq (==) at /usr/local/pf/lib/pf/vlan.pm line 137.
> Jan 11 06:55:54 pfsetvlan(5) ERROR: Use of uninitialized value $ifType in
> numeric eq (==) at /usr/local/pf/lib/pf/vlan.pm line 137.
> Jan 11 06:55:54 pfsetvlan(5) INFO: trap received on 10.11.12.13 ifindex
> which is not ethernetCsmacd (pf::vlan::doWeActOnThisTrap)
> Jan 11 06:55:54 pfsetvlan(5) INFO: doWeActOnThisTrap returns false. Stop
> handling (main::handleTrap)
> Jan 11 06:55:54 pfsetvlan(5) INFO: finished (main::cleanupAfterThread)
> Jan 11 06:55:54 pfsetvlan(25) WARN: SNMP trap handling not implemented for
> this type of switch. (pf::Switch::EdgeCore::parseTrap)
> Jan 11 06:55:54 pfsetvlan(25) ERROR: Use of uninitialized value $trapType in
> string eq at /usr/local/pf/sbin/pfsetvlan line 670.
> Jan 11 06:55:54 pfsetvlan(25) ERROR: Use of uninitialized value $switch_port
> in concatenation (.) or string at /usr/local/pf/sbin/pfsetvlan line 729.
> Jan 11 06:55:54 pfsetvlan(25) ERROR: Use of uninitialized value $trapType in
> concatenation (.) or string at /usr/local/pf/sbin/pfsetvlan line 729.
>
> This may all just be noise I can safely ignore but I fear that there is
> either a bug or that I’ve goofed something up. Any wisdom someone may have
> to offer would be appreciated.
>
> -- Robin Kundert
> Sr. Network Analyst/Administrator
> Seattle Pacific University
> Computer & Information Systems Dept.
> 3307 Third Ave. West, Suite 206, Seattle, WA 98119-1950
> email: [email protected]
> voice: 206.281.2507
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet_______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
