PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001284PacketFencehardware modulespublic2011-09-27 11:472011-11-21 12:05
Reporterobilodeau 
Assigned Toobilodeau 
PrioritylowSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.0.3Fixed in Version3.0.3 
fixed in git revision
fixed in mtn revisionf546d64318f6e8f5d441dd895a1e3460c507d748
Summary0001284: SNMPv3 with Cisco Catalyst 2950
DescriptionIOS running on Cisco 2950 don't support SNMPv3 contexts. These are used by Cisco to query the CAM (mac to port) table of switches in more recent IOSes. This is a Cisco issue not a PacketFence one.

What this means is that we don't support 2950's using SNMPv3 in linkup/linkdown and MAC Notification modes.

For port-security, we can work without querying the CAM but it doesn't work, we will need to investigate.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filespatch Cisco-SNMPv3-port-security-fixes.patch (2,429) 2011-11-01 10:31
https://www.packetfence.org/bugs/file_download.php?file_id=119&type=bug
Issue History
Date ModifiedUsernameFieldChange
2011-09-27 11:47obilodeauNew Issue
2011-09-27 11:47obilodeauFile Added: cisco-2950-snmpv3-port-security-setVlan-fix.patch
2011-09-27 11:48obilodeauStatusnew => confirmed
2011-09-27 12:06obilodeauNote Added: 0002298
2011-10-24 10:49obilodeauNote Added: 0002375
2011-10-31 15:28obilodeauNote Added: 0002409
2011-10-31 15:28obilodeauStatusconfirmed => assigned
2011-10-31 15:28obilodeauAssigned To => obilodeau
2011-10-31 16:00obilodeauNote Added: 0002410
2011-11-01 10:29obilodeauDescription Updated
2011-11-01 10:31obilodeauFile Deleted: cisco-2950-snmpv3-port-security-setVlan-fix.patch
2011-11-01 10:31obilodeauFile Added: Cisco-SNMPv3-port-security-fixes.patch
2011-11-01 10:32obilodeauNote Added: 0002412
2011-11-01 10:39obilodeaumtn revision => f546d64318f6e8f5d441dd895a1e3460c507d748
2011-11-01 10:39obilodeauNote Added: 0002413
2011-11-01 10:39obilodeauStatusassigned => resolved
2011-11-01 10:39obilodeauFixed in Version => +1
2011-11-01 10:39obilodeauResolutionopen => fixed
2011-11-21 12:04obilodeauNote Added: 0002458
2011-11-21 12:04obilodeauTarget Version+2 => 3.0.3
2011-11-21 12:05obilodeauStatusresolved => closed
2011-11-21 12:05obilodeauFixed in Version+1 => 3.0.3

Notes
(0002298)
obilodeau   
2011-09-27 12:06   
committed more documentation regarding the SNMPv3 issues in the 2950 module at revno: eb70eb365b97300d33b0019692f9a2984b676349
(0002375)
obilodeau   
2011-10-24 10:49   
Ok, found out more about this issue. Turns out that if you add a v3 context to a query, subsequent queries will fail. Not sure if this affect specifically only the 2950 or all of our v3.

Going straight to getVlan works:
# perl -d sbin/pfsetvlan
$switch = $switchFactory->instantiate('10.0.0.15');
$x = $switch->getVlan(15);
x \$x
0 SCALAR(0xaccf2a0)
   -> 103

Calling a context-setting method first will fail:
# perl -d sbin/pfsetvlan
$switch = $switchFactory->instantiate('10.0.0.15');
%y = $switch->getMacBridgePortHash();
$x = $switch->getVlan(15);
x \$x
0 SCALAR(0xaccf2a0)
   -> undef

To fix I want to read a bit more about Net::SNMP v3 context's and I've got the feeling that i'll need to disable them after using them.
(0002409)
obilodeau   
2011-10-31 15:28   
Turns out "The contextName stays with the object until it is changed.". So I want to unset them after doing a query with a context. Turns out there's no easy way to do so in Net::SNMP so I'll poke directly into a 'private method' to do so: ->_context_name(...)

Filed an upstream ticket to get a supported hook:
Bug #72075 for Net-SNMP: Method to change the contextName
https://rt.cpan.org/Public/Bug/Display.html?id=72075 [^]
(0002410)
obilodeau   
2011-10-31 16:00   
private method didn't work, poking at the internal hash with ->{_context_name} did work though. I'll do some more testing tomorrow then update the ticket.
(0002412)
obilodeau   
2011-11-01 10:32   
Deleted old patch added new patch. Tests in the labs are positive.
(0002413)
obilodeau   
2011-11-01 10:39   
Fix committed into 3_0 branch will be part of our next version.
(0002458)
obilodeau   
2011-11-21 12:04   
Fixed released in 3.0.3 today.