Hi Kurtis,

Thanks for the snmpwalk. Everything was fine. Now let's try to do a 
manual set to change the interface status from access to trunk.

Let's pick interface 17 so ifIndex 10017:

snmpset -v 2c -c <your write community string>  192.168.10.228 
1.3.6.1.4.1.9.9.46.1.6.1.1.13.10017 i 1

(all on one line)

Then recheck the 17 if it changed:

snmpwalk -v 2c -c<your read community string>  192.168.10.228 
1.3.6.1.4.1.9.9.46.1.6.1.1.13.10017

Now it should be trunk (1). I am expecting an error with the set command 
since your trace didn't work and you are going to perform the same exact 
command as in the code.

>> Feb 03 09:13:28 pfsetvlan(17) INFO: secureMacAddrViolation trap received on 
>> 192.168.10.228 ifIndex 10015 for ac:67:06:15:30:30 (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(17) INFO: The floating network device 
>> ac:67:06:15:30:30 has just plugged into 192.168.10.228  port 10015. Enabling 
>> floating network device configuration on the port. (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(17) INFO: Disabling port-security on port 10015 
>> (pf::floatingdevice::enablePortConfig)
>> Feb 03 09:13:28 pfsetvlan(17) DEBUG: opening SNMP v2c write connection to 
>> 192.168.10.228 (pf::SNMP::connectWrite)
>> Feb 03 09:13:28 pfsetvlan(17) INFO: Setting port 10015 as trunk. 
>> (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk)
>> Feb 03 09:13:28 pfsetvlan(17) ERROR: An error occured while enabling port 
>> 10015 as multi-vlan (trunk) 
>> (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk)
>> Feb 03 09:13:28 pfsetvlan(17) INFO: An error occured while enabling floating 
>> network device configuration on port 10015. It may not work! 
>> (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(17) INFO: finished (main::cleanupAfterThread)
>> Feb 03 09:13:28 pfsetvlan(17) DEBUG: closing SNMP v2c read connection to 
>> 192.168.10.228 (pf::SNMP::disconnectRead)
>> Feb 03 09:13:28 pfsetvlan(17) DEBUG: closing SNMP v2c write connection to 
>> 192.168.10.228 (pf::SNMP::disconnectWrite)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: nb of items in queue: 1; nb of threads 
>> running: 0 (main::startTrapHandlers)
>> Feb 03 09:13:28 pfsetvlan(18) DEBUG: opening SNMP v2c read connection to 
>> 192.168.10.228 (pf::SNMP::connectRead)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: secureMacAddrViolation trap received on 
>> 192.168.10.228 ifIndex 10015 for ac:67:06:15:30:30 (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: The floating network device 
>> ac:67:06:15:30:30 has just plugged into 192.168.10.228  port 10015. Enabling 
>> floating network device configuration on the port. (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: Disabling port-security on port 10015 
>> (pf::floatingdevice::enablePortConfig)
>> Feb 03 09:13:28 pfsetvlan(18) DEBUG: opening SNMP v2c write connection to 
>> 192.168.10.228 (pf::SNMP::connectWrite)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: Setting port 10015 as trunk. 
>> (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk)
>> Feb 03 09:13:28 pfsetvlan(18) ERROR: An error occured while enabling port 
>> 10015 as multi-vlan (trunk) 
>> (pf::SNMP::Cisco::Catalyst_2950::enablePortConfigAsTrunk)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: An error occured while enabling floating 
>> network device configuration on port 10015. It may not work! 
>> (main::handleTrap)
>> Feb 03 09:13:28 pfsetvlan(18) INFO: finished (main::cleanupAfterThread)
>> Feb 03 09:13:28 pfsetvlan(18) DEBUG: closing SNMP v2c read connection to 
>> 192.168.10.228 (pf::SNMP::disconnectRead)
>> Feb 03 09:13:28 pfsetvlan(18) DEBUG: closing SNMP v2c write connection to 
>> 192.168.10.228 (pf::SNMP::disconnectWrite)
>>

Thanks,
-- 
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)

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to