Cisco 2950
Moderators: Developers, Moderators
Cisco 2950
Ok, I am sure this has to have been addressed by now, but I just realized that several of my 2950 switches had not been showing any MACs on them. After some inspection I found this to be because the mactrack_scanner.php was throwing this error:
Device Type Not Found in Device Type Table.
when run in debug mode.
After looking through the mactrack_scanner.php I found that it only looks at the first 40 characters of the system description. These dumb 2950s (at least with the code we are running on them) have the following system description:
Cisco Internetwork Operating System Software IOS (tm) C2950 Software (C2950-I6K2L2Q4-M), etc...
A bit of basic math showed me that the part of the system description I was looking for: C2950-I6K2L2Q4-M was some 20+ characters beyond where the scanner was stopping. I changed this limit in the mactrack_scanner.php to 100, and now my 2950s are behaving as expected.
I will leave it to Larry to update his code if he believes I am not way off. The line in the mactrack_scanner.php I modified is: 162.
I am using the latest SVN. I downloaded just to make sure that the fix was not already included.
Device Type Not Found in Device Type Table.
when run in debug mode.
After looking through the mactrack_scanner.php I found that it only looks at the first 40 characters of the system description. These dumb 2950s (at least with the code we are running on them) have the following system description:
Cisco Internetwork Operating System Software IOS (tm) C2950 Software (C2950-I6K2L2Q4-M), etc...
A bit of basic math showed me that the part of the system description I was looking for: C2950-I6K2L2Q4-M was some 20+ characters beyond where the scanner was stopping. I changed this limit in the mactrack_scanner.php to 100, and now my 2950s are behaving as expected.
I will leave it to Larry to update his code if he believes I am not way off. The line in the mactrack_scanner.php I modified is: 162.
I am using the latest SVN. I downloaded just to make sure that the fix was not already included.
One more thing. I keep getting devices going into 'error' state lately. If I click on them (in the devices view) I get the following:
SNMP Information
System: U
Uptime: U
Hostname: U
ObjectID: U
Then, if I simply click 'save', and then come back to view that same device again, I get all the correct info, and the next polling cycle the status goes to 'up'... Weird..
I am running an OPTIMIZE TABLE on the mac_track_ports table now, and probably on some of the others, but this is baffling me. Anyone have any suggestions?
SNMP Information
System: U
Uptime: U
Hostname: U
ObjectID: U
Then, if I simply click 'save', and then come back to view that same device again, I get all the correct info, and the next polling cycle the status goes to 'up'... Weird..
I am running an OPTIMIZE TABLE on the mac_track_ports table now, and probably on some of the others, but this is baffling me. Anyone have any suggestions?
Re: Cisco 2950
Apparently I was way off on this, because, well, I don't know.. I will post a fix if I ever find one, but if anyone else can help me out, I would appreciate it. Thanks.chadd wrote:Ok, I am sure this has to have been addressed by now, but I just realized that several of my 2950 switches had not been showing any MACs on them. After some inspection I found this to be because the mactrack_scanner.php was throwing this error:
Device Type Not Found in Device Type Table.
when run in debug mode.
After looking through the mactrack_scanner.php I found that it only looks at the first 40 characters of the system description. These dumb 2950s (at least with the code we are running on them) have the following system description:
Cisco Internetwork Operating System Software IOS (tm) C2950 Software (C2950-I6K2L2Q4-M), etc...
A bit of basic math showed me that the part of the system description I was looking for: C2950-I6K2L2Q4-M was some 20+ characters beyond where the scanner was stopping. I changed this limit in the mactrack_scanner.php to 100, and now my 2950s are behaving as expected.
I will leave it to Larry to update his code if he believes I am not way off. The line in the mactrack_scanner.php I modified is: 162.
I am using the latest SVN. I downloaded just to make sure that the fix was not already included.
I'm using MacTrack with several (dozens) 2950 of different types. The way I got it working was downloading the CISCO-PRODUCTS-MIB from Cisco's website and then add the OID for every 2950 model in MacTrack.
For this, just go to "Device Types", "Add" and when filling the fields, put nothing in System Description Match and the OID you found in the MIB in Vendor snmp Object ID Match.
A bit of hassle but works like a charm. Someone with better coding skills than me could write a small script taking every entry in the MIB and adding them to the MacTrack database.
For this, just go to "Device Types", "Add" and when filling the fields, put nothing in System Description Match and the OID you found in the MIB in Vendor snmp Object ID Match.
A bit of hassle but works like a charm. Someone with better coding skills than me could write a small script taking every entry in the MIB and adding them to the MacTrack database.
Sure, cat CISCO-PRODUCTS-MIB.oid | grep 2950 does the trick :
"catalyst295012" "1.3.6.1.4.1.9.1.323"
"catalyst295024" "1.3.6.1.4.1.9.1.324"
"catalyst295024C" "1.3.6.1.4.1.9.1.325"
"catalyst2950t24" "1.3.6.1.4.1.9.1.359"
"catalyst295012G" "1.3.6.1.4.1.9.1.427"
"catalyst295024G" "1.3.6.1.4.1.9.1.428"
"catalyst295048G" "1.3.6.1.4.1.9.1.429"
"catalyst295024S" "1.3.6.1.4.1.9.1.430"
"catalyst295024GDC" "1.3.6.1.4.1.9.1.472"
"catalyst295024SX" "1.3.6.1.4.1.9.1.480"
"catalyst295024LRESt" "1.3.6.1.4.1.9.1.482"
"catalyst29508LRESt" "1.3.6.1.4.1.9.1.483"
"catalyst295024LREG" "1.3.6.1.4.1.9.1.484"
"catalyst2950St24LRE997" "1.3.6.1.4.1.9.1.551"
"catalyst295048T" "1.3.6.1.4.1.9.1.559"
"catalyst295048SX" "1.3.6.1.4.1.9.1.560"
Note that I imported them all. Hope it helps.
"catalyst295012" "1.3.6.1.4.1.9.1.323"
"catalyst295024" "1.3.6.1.4.1.9.1.324"
"catalyst295024C" "1.3.6.1.4.1.9.1.325"
"catalyst2950t24" "1.3.6.1.4.1.9.1.359"
"catalyst295012G" "1.3.6.1.4.1.9.1.427"
"catalyst295024G" "1.3.6.1.4.1.9.1.428"
"catalyst295048G" "1.3.6.1.4.1.9.1.429"
"catalyst295024S" "1.3.6.1.4.1.9.1.430"
"catalyst295024GDC" "1.3.6.1.4.1.9.1.472"
"catalyst295024SX" "1.3.6.1.4.1.9.1.480"
"catalyst295024LRESt" "1.3.6.1.4.1.9.1.482"
"catalyst29508LRESt" "1.3.6.1.4.1.9.1.483"
"catalyst295024LREG" "1.3.6.1.4.1.9.1.484"
"catalyst2950St24LRE997" "1.3.6.1.4.1.9.1.551"
"catalyst295048T" "1.3.6.1.4.1.9.1.559"
"catalyst295048SX" "1.3.6.1.4.1.9.1.560"
Note that I imported them all. Hope it helps.
Ok, so I tried that too - no luck. I tried both cisco scanning functions, both 'switch/hub' and 'switch/router'. I tried snmp v1 and v2. I am starting to think there is something else wrong here. Just for the sake of trying, what are your exact settings? Scanning function, type (switch/hub, switch/router), snmp version, etc.?? Any help is appreciated. FYI, my problem is no active MACs are showing up. Thanks,
-chadd.
-chadd.
"vendor","description","device_type","sysDescr_match","sysObjectID_match","scanning_function","serial_number_oid","lowPort","highPort"
"Cisco","Catalyst 2948G","1","WS-C2948",".1.3.6.1.4.1.9","get_catalyst_dot1dTpFdbEntry_ports","","0","0"
"Cisco","Catalyst 2950","1","C2950",".1.3.6.1.4.1.9.1.427","get_IOS_dot1dTpFdbEntry_ports","","0","0"
This works fine for me.
"Cisco","Catalyst 2948G","1","WS-C2948",".1.3.6.1.4.1.9","get_catalyst_dot1dTpFdbEntry_ports","","0","0"
"Cisco","Catalyst 2950","1","C2950",".1.3.6.1.4.1.9.1.427","get_IOS_dot1dTpFdbEntry_ports","","0","0"
This works fine for me.
I read a lot of post regarding catalyst 2950 and I hope I didn't missing anything.
I have switches 2950 that matches my device type correctly but they show only 2 mac address active. I'm sure it's not correct.
After reading how collect cam table with snmp I noticed that 3524 are different from 2950.
The 2950 are using snmp community string indexing (community@vlanid) to retrieve not only cam dynamic for each vlan, but also interface up for each vlan.
This is my output with snmpwalk without snmp indexing
minuz71@minuz71-lin:~$ snmpwalk -v 2c -c public 10.8.10.113 .1.3.6.1.2.1.17.1.4.1.2
SNMPv2-SMI::mib-2.17.1.4.1.2.49 = INTEGER: 49
SNMPv2-SMI::mib-2.17.1.4.1.2.50 = INTEGER: 50
and this is my output with snmp indexing for vlan id 113:
minuz71@minuz71-lin:~$ snmpwalk -v 2c -c public@113 10.8.10.113 .1.3.6.1.2.1.17.1.4.1.2
SNMPv2-SMI::mib-2.17.1.4.1.2.1 = INTEGER: 1
SNMPv2-SMI::mib-2.17.1.4.1.2.2 = INTEGER: 2
SNMPv2-SMI::mib-2.17.1.4.1.2.7 = INTEGER: 7
SNMPv2-SMI::mib-2.17.1.4.1.2.8 = INTEGER: 8
SNMPv2-SMI::mib-2.17.1.4.1.2.11 = INTEGER: 11
SNMPv2-SMI::mib-2.17.1.4.1.2.14 = INTEGER: 14
SNMPv2-SMI::mib-2.17.1.4.1.2.15 = INTEGER: 15
SNMPv2-SMI::mib-2.17.1.4.1.2.16 = INTEGER: 16
SNMPv2-SMI::mib-2.17.1.4.1.2.21 = INTEGER: 21
SNMPv2-SMI::mib-2.17.1.4.1.2.22 = INTEGER: 22
SNMPv2-SMI::mib-2.17.1.4.1.2.25 = INTEGER: 25
SNMPv2-SMI::mib-2.17.1.4.1.2.26 = INTEGER: 26
SNMPv2-SMI::mib-2.17.1.4.1.2.49 = INTEGER: 49
SNMPv2-SMI::mib-2.17.1.4.1.2.50 = INTEGER: 50
It' seems that mactrack don't use snmp indexing to retrieve ports up, so it collect only port up for vlan 1, tipically trunk port (49, 50), missing other mac address on other vlans.
Best regards
I have switches 2950 that matches my device type correctly but they show only 2 mac address active. I'm sure it's not correct.
After reading how collect cam table with snmp I noticed that 3524 are different from 2950.
The 2950 are using snmp community string indexing (community@vlanid) to retrieve not only cam dynamic for each vlan, but also interface up for each vlan.
This is my output with snmpwalk without snmp indexing
minuz71@minuz71-lin:~$ snmpwalk -v 2c -c public 10.8.10.113 .1.3.6.1.2.1.17.1.4.1.2
SNMPv2-SMI::mib-2.17.1.4.1.2.49 = INTEGER: 49
SNMPv2-SMI::mib-2.17.1.4.1.2.50 = INTEGER: 50
and this is my output with snmp indexing for vlan id 113:
minuz71@minuz71-lin:~$ snmpwalk -v 2c -c public@113 10.8.10.113 .1.3.6.1.2.1.17.1.4.1.2
SNMPv2-SMI::mib-2.17.1.4.1.2.1 = INTEGER: 1
SNMPv2-SMI::mib-2.17.1.4.1.2.2 = INTEGER: 2
SNMPv2-SMI::mib-2.17.1.4.1.2.7 = INTEGER: 7
SNMPv2-SMI::mib-2.17.1.4.1.2.8 = INTEGER: 8
SNMPv2-SMI::mib-2.17.1.4.1.2.11 = INTEGER: 11
SNMPv2-SMI::mib-2.17.1.4.1.2.14 = INTEGER: 14
SNMPv2-SMI::mib-2.17.1.4.1.2.15 = INTEGER: 15
SNMPv2-SMI::mib-2.17.1.4.1.2.16 = INTEGER: 16
SNMPv2-SMI::mib-2.17.1.4.1.2.21 = INTEGER: 21
SNMPv2-SMI::mib-2.17.1.4.1.2.22 = INTEGER: 22
SNMPv2-SMI::mib-2.17.1.4.1.2.25 = INTEGER: 25
SNMPv2-SMI::mib-2.17.1.4.1.2.26 = INTEGER: 26
SNMPv2-SMI::mib-2.17.1.4.1.2.49 = INTEGER: 49
SNMPv2-SMI::mib-2.17.1.4.1.2.50 = INTEGER: 50
It' seems that mactrack don't use snmp indexing to retrieve ports up, so it collect only port up for vlan 1, tipically trunk port (49, 50), missing other mac address on other vlans.
Best regards
Who is online
Users browsing this forum: No registered users and 4 guests