Thanks Francois,
You were correct I had replaced rather than appended the configuration
mentioned in the admin guide.
I have now replaced the original and modified it as I think it should be
for our environment. But still I get the same error. Could you please have
a look at the complete switches.conf file and let me know if I have made a
mistake:
#
# Copyright 2006-2008 Inverse inc.
#
# See the enclosed file COPYING for license information (GPL).
# If you did not receive this file, see
# http://www.fsf.org/licensing/licenses/gpl.html
[default]
vlans = 1,2,3,4,5
normalVlan = 1
registrationVlan = 2
isolationVlan = 3
macDetectionVlan = 4
guestVlan = 5
customVlan1 =
customVlan2 =
customVlan3 =
customVlan4 =
customVlan5 =
VoIPEnabled = no
voiceVlan =
mode = testing
macSearchesMaxNb = 30
macSearchesSleepInterval = 2
uplink = dynamic
#
# Command Line Interface
#
# cliTransport could be: Telnet, SSH or Serial
cliTransport = Telnet
cliUser = admin
cliPwd = admin
cliEnablePwd = admin
#
# SNMP section
#
# PacketFence -> Switch
SNMPVersion = 2c
SNMPCommunityRead = public
SNMPCommunityWrite = private
#SNMPEngineID = 0000000000000
#SNMPUserNameRead = readUser
#SNMPAuthProtocolRead = MD5
#SNMPAuthPasswordRead = authpwdread
#SNMPPrivProtocolRead = DES
#SNMPPrivPasswordRead = privpwdread
#SNMPUserNameWrite = writeUser
#SNMPAuthProtocolWrite = MD5
#SNMPAuthPasswordWrite = authpwdwrite
#SNMPPrivProtocolWrite = DES
#SNMPPrivPasswordWrite = privpwdwrite
# Switch -> PacketFence
SNMPVersionTrap = 2c
SNMPCommunityTrap = public
#SNMPAuthProtocolTrap = MD5
#SNMPAuthPasswordTrap = authpwdread
#SNMPPrivProtocolTrap = DES
#SNMPPrivPasswordTrap = privpwdread
#
# Web Services Interface
#
# wsTransport could be: http or https
wsTransport = http
wsUser =
wsPwd =
#
# RADIUS NAS Client config
#
# RADIUS shared secret with switch
radiusSecret=
[127.0.0.1]
type = PacketFence
mode = production
uplink = dynamic
# SNMP Traps v1 are used for internal messages
SNMPVersionTrap=1
SNMPCommunityTrap=public
[192.168.1.101]
type = Cisco::Catalyst_2970
mode = production
uplink = 23,24
#SNMPVersion = 2c
#SNMPEngineID = 0000000000000
#SNMPUserNameRead = readUser
#SNMPAuthProtocolRead = MD5
#SNMPAuthPasswordRead = authpwdread
#SNMPPrivProtocolRead = DES
#SNMPPrivPasswordRead = privpwdread
#SNMPUserNameWrite = writeUser
#SNMPAuthProtocolWrite = MD5
#SNMPAuthPasswordWrite = authpwdwrite
#SNMPPrivProtocolWrite = DES
#SNMPPrivPasswordWrite = privpwdwrite
#SNMPVersionTrap = 2c
#SNMPUserNameTrap = readUser
#SNMPAuthProtocolTrap = MD5
#SNMPAuthPasswordTrap = authpwdread
#SNMPPrivProtocolTrap = DES
#SNMPPrivPasswordTrap = privpwdread
On Wed, Mar 14, 2012 at 12:43 PM, Francois Gaudreault <
[email protected]> wrote:
> Hi,
>
> > The IOS version is 12.2(44)SE6 which is the latest available for this
> > model.
> > After your suggestion I also tried with a CISCO 3560 and it does the
> > same thing.
> > Could it be something in my configuration causing the problem.
> Maybe (see below). The 3560s are well supported in PF. In fact, we
> have them in production in a *lot* of deployments.
>
> >
> > In the configuration check-up log it has a warning about switches.conf
> > 'Switch SNMP Trap version is missing for switch 192.168.1.101 please
> > provide one specific to the switch or in default' I do have trap version
> > in the file. SO not sure why it is warning. Switches.conf below:
> You have the trap version/community config missing. Is this your actual
> switches.conf or you stripped it for the mailing list? There are a lot
> of stuff missing. You should not strip this file in any cases (even if
> it can be a pain to edit sometimes when you have 1k switches in it).
>
> Please, put back the original switches.conf, and modify the fields you
> need. After that, it should work.
>
> Thanks.
>
> --
> Francois Gaudreault, ing. jr
> [email protected] :: +1.514.447.4918 (x130) :: www.inverse.ca
> Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
> (www.packetfence.org)
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Packetfence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
