Hi Steve, To me this looks like you are missing the SNMPVersionTrap parameter either in section [default] or in your switch's section of conf/switches.conf.
Error message is obscure, I filed a bug to fix that: http://www.packetfence.org/bugs/view.php?id=993 May I suggest that you use the web admin to configure PacketFence, you'll avoid mistakes like that as it will do the config files for you. Keep us posted on your progress and thanks for trying out 1.8.8! Steve Wittstruck wrote: > Hello All, > > My scratch 1.8.7 install followed by 1.8.8 seems to have broke SNMP trap > initialization or I'm getting further along than before and uncovered a new > problem: > > './pfcmd service pf restart' gives the following messages: > ======================================== > service|command > pfdhcplistener|stop > pfmon|stop > httpd|stop > snmptrapd|stop > pfsetvlan|stop > Checking configuration sanity... > network xxx.xx.0.0/18 is larger than a /22 - you may want to consider > registration queueing! at > /usr/lib/perl5/vendor_perl/5.8.8/Log/Log4perl/Logger.pm line 866 > internal IP space is very large - you may want to consider registration > queueing! at /usr/lib/perl5/vendor_perl/5.8.8/Log/Log4perl/Logger.pm line 866 > service|command > config files|start > pfdhcplistener|start > pfmon|start > httpd|start > Use of uninitialized value in string eq at /usr/local/pf/lib/pf/services.pm > line 823 (#1) > (W uninitialized) An undefined value was used as if it were already > defined. It was interpreted as a "" or a 0, but maybe it was a mistake. > To suppress this warning assign a defined value to your variables. > > To help you figure out what was undefined, perl tells you what operation > you used the undefined value in. Note, however, that perl optimizes your > program and the operation displayed in the warning may not necessarily > appear literally in your program. For example, "that $foo" is > usually optimized into "that " . $foo, and the warning will refer to > the concatenation (.) operator, even though there is no . in your > program. > > snmptrapd|start > Use of uninitialized value in pattern match (m//) at > /usr/local/pf/lib/pf/services.pm line 988 (#1) > pfsetvlan|start > ======================================== > > Looking at line 823 in services.pm I see: > if ( $switch->{_SNMPVersionTrap} eq '3' ) { > <-------------------- the PF restart error suggests 'SNMPVersionTrap' hasn't > been initialized? > > Here's my switch config: > snmp-server community xxxxxxxx RO 2 > snmp-server community yyyyyyyy RW 2 > snmp-server enable traps port-security > snmp-server enable traps port-security trap-rate 1 > snmp-server host xx.xx.xx.xx version 2c zzzzzzzz port-security > > And here's my switches.conf: > [default] > SNMPVersion = 2c > SNMPCommunityRead = xxxxxxxx > SNMPCommunityWrite = yyyyyyyy > SNMPCommunityTrap = zzzzzzzz > [1.2.3.4] > type = Cisco::Catalyst_3750 <------------------------ note > I am using a newly support Catalyst 3750 > uplink = 3 > mode = production > > Am I doing something wrong? > > Thanks a million! > Steve Wittstruck > Colorado School of Mines > ------------------------------------------------------------------------------ > > _______________________________________________ > Packetfence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users -- 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) ------------------------------------------------------------------------------ _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
