Cisco Wireless Lan Controller and NAV
I am running version 4-0-216-0. - odd arne hauge
-----Original Message----- From: Vidar Stokke [mailto:vidar.stokke@ntnu.no] Sent: Friday, April 13, 2007 3:57 PM To: Hauge Odd Arne Cc: Morten Brekkevold; nav-users@itea.ntnu.no Subject: Re: [Nav-users] Cisco Wireless Lan Controller and NAV
Hauge Odd Arne wrote:
When I do a snmpwalk I get the following result: snmpwalk -v2c -On lan-controllers ip -c community system
.1.3.6.1.2.1.1.1.0 = STRING: Cisco Controller .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.14179.1.1.4.3
Without the -On option: snmpwalk -v2c lan-controllers ip -c community system SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14179.1.1.4.3
So it seems to me that NAV is the problem not the controller.
- odd arne hauge
I did the same thing towards one of our controllers:
snmpwalk -v2c -On lan-controllers ip -c community system
.1.3.6.1.2.1.1.1.0 = STRING: Cisco Controller .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.14179.1.1.4.4 .1.3.6.1.2.1.1.3.0 = Timeticks: (386918800) 44 days, 18:46:28.00 .1.3.6.1.2.1.1.4.0 = STRING: .1.3.6.1.2.1.1.5.0 = STRING: wlan_gsw_wism_1_2 .1.3.6.1.2.1.1.6.0 = STRING: .1.3.6.1.2.1.1.7.0 = INTEGER: 2
snmpwalk -v2c -On lan-controllers ip -c community system
SNMPv2-MIB::sysDescr.0 = STRING: Cisco Controller SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14179.1.1.4.4 SNMPv2-MIB::sysUpTime.0 = Timeticks: (386927900) 44 days, 18:47:59.00 SNMPv2-MIB::sysContact.0 = STRING: SNMPv2-MIB::sysName.0 = STRING: wlan_gsw_wism_1_2 SNMPv2-MIB::sysLocation.0 = STRING: SNMPv2-MIB::sysServices.0 = INTEGER: 2
What version of software are you running on your controllers?
-- Regards Vidar Stokke NTNU, ITEA, Networking
-----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Friday, April 13, 2007 11:09 AM To: Hauge Odd Arne Cc: nav-users@itea.ntnu.no Subject: Re: [Nav-users] Cisco Wireless Lan Controller and NAV
Hauge Odd Arne wrote, On 02-04-2007 15:52:
Hi.
Has NAV any support for Cisco Wireless Lan Controller 440x ? Trying to add my own device using editDb gives following output: [...]
Snmp error 2 at 1 (.1.3.6.1.2.1.1.2.0, NULL: ) This is NAV's somewhat cryptic way of telling you that the remote SNMP agent doesn't know the OID. (The code was recently changed to give a more friendly error message in this case, and it will be in place for NAV 3.3).
The OID in this case is sysObjectID.0; if your Cisco Wireless Lan Controller 440x reports a noSuchName error for this OID, then I'd say something is seriously wrong with your controller.
NTNU reports that they have added a Cisco WLAN controller to their NAV with no problems, so I'm not sure what causes your problem.
As to your question of "any support for" the Cisco WLAN Controller 440x, the answer is yes. I.e., it is an IP device, and can be status monitored by NAV. The box should support SNMP (although something about that seems broken in your case), so you will be able to retrieve some basic SNMP data from it. But that is all.
When it comes to actually retrieving info about the slaves controlled by the box, NAV has no idea. We are working on better support for autonomous Cisco WLAN AP's this year, in fact Andreas Knudsen from the University College of ?stfold is coming up here next week to work on this support. Unfortunately, we have no current plans of supporting the special case of a Cisco WLAN Controller, as we currently haven't enough resources to work on it. We are aware, though, that they are growing more popular and should be supported, but we have no idea yet how they can best be supported by NAV, and not sure how the controller/slave concept maps into NAV's existing data model. Whoever is going to work out some support for this box, must have access to one and the proper Cisco documentation for it.
-- mvh Morten Brekkevold UNINETT
_______________________________________________ nav-users mailing list nav-users@itea.ntnu.no http://mailman.itea.ntnu.no/mailman/listinfo/nav-users
Hi. I've actually managed to reproduce your error, Odd Arne. It seems that you have to enable SNMPv1 on your controllers. If this is the correct way of doing things, is up to the NAV-developers to decide. I honestly thought that SNMPv2 was enough. We have enabled SNMPv1 on our controllers due to the fact that we had an old version of NAV (version 2) running for quite som time. But the workaround is to enable SNMPv1 on controllers. -- mvh Vidar Stokke NTNU, ITEA IT-drift, Nettgruppen
From morten.brekkevold at uninett.no Wed Apr 18 09:35:19 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Wed Apr 18 08:35:22 2007 Subject: [Nav-users] Cisco Wireless Lan Controller and NAV In-Reply-To: <4625B8F4.7010906@ntnu.no> References: <4ddd24660703121031h716cb122q8cee4ba790fc632@mail.gmail.com> <45F93D04.4080707@uninett.no> <8EEE7738AEDF6947B3E5508A0244D1C2631EDE@stam.himolde.no> <461F48A8.3040705@uninett.no> <8EEE7738AEDF6947B3E5508A0244D1C2DE14F6@stam.himolde.no> <461F8C1D.6020405@ntnu.no> <8EEE7738AEDF6947B3E5508A0244D1C2DE150D@stam.himolde.no> <4625B8F4.7010906@ntnu.no> Message-ID: <4625BC27.4060605@uninett.no>
Vidar Stokke wrote, On 18-04-2007 08:21:
It seems that you have to enable SNMPv1 on your controllers. If this is the correct way of doing things, is up to the NAV-developers to decide. I honestly thought that SNMPv2 was enough. We have enabled SNMPv1 on our controllers due to the fact that we had an old version of NAV (version 2) running for quite som time.
But the workaround is to enable SNMPv1 on controllers.
This is a very good observation, Vidar! I do believe EditDB makes some assumption that all SNMP-enabled devices can speak SNMPv1, but apparently this is not the case. I've filed a bug for this [1], so I won't forget to check up on this issue. I'm glad to hear there's a workaround in this case. http://sourceforge.net/tracker/index.php?func=detail&aid=1702676&group_id=10... -- mvh Morten Brekkevold UNINETT
From gwc2004 at gmail.com Wed Apr 18 18:04:21 2007 From: gwc2004 at gmail.com (Greg Cooper) Date: Thu Apr 19 00:04:27 2007 Subject: [Nav-users] Cisco 3560 and 3750 Switch problems Message-ID: <4ddd24660704181504h5239bf43s8eb5bfe6b8608891@mail.gmail.com>
Hello, I am having trouble with 3560 and 3750 switches not adding their port information into the database. When I search for ports with a particular VLAN through the reporting page, it won't register any ports with that VLAN on a 3560 or 3750. If you browse to the switch, it will show you what ports are on what VLAN, though. Any ideas? Thanks! Lok1
From odd.hauge at hiMolde.no Thu Apr 19 19:40:32 2007 From: odd.hauge at hiMolde.no (Hauge Odd Arne) Date: Thu Apr 19 18:40:39 2007 Subject: [Nav-users] Report: Switch ports with trunk ports expanded In-Reply-To: <4625BC27.4060605@uninett.no> References: <4ddd24660703121031h716cb122q8cee4ba790fc632@mail.gmail.com> <45F93D04.4080707@uninett.no> <8EEE7738AEDF6947B3E5508A0244D1C2631EDE@stam.himolde.no> <461F48A8.3040705@uninett.no> <8EEE7738AEDF6947B3E5508A0244D1C2DE14F6@stam.himolde.no> <461F8C1D.6020405@ntnu.no> <8EEE7738AEDF6947B3E5508A0244D1C2DE150D@stam.himolde.no> <4625B8F4.7010906@ntnu.no> <4625BC27.4060605@uninett.no> Message-ID: <8EEE7738AEDF6947B3E5508A0244D1C290E975@stam.himolde.no>
Hi. The "Switch ports with trunk ports expanded" report gives the following error: Configuration error! The report generator is not able to do such things.FEIL: column reference "swportid" is ambiguous SELECT b1.sysname,s1.ifindex,s1.interface,m1.module,s1.port,s1.link,s1.speed,s1.duplex,s1.media,CASE WHEN s1.trunk THEN 'Y' ELSE '' END as trunk,vlan.vlan,CASE direction WHEN 'o' THEN 'Up' WHEN 'n' THEN 'Down' ELSE 'N/A' END as direction,s1.portname,b2.sysname AS to_netboxid,s2.interface AS remote_interface,s1.swportid,b1.netboxid AS netboxid,b1.catid FROM swport AS s1 JOIN module AS m1 USING (moduleid) JOIN netbox AS b1 USING (netboxid) LEFT JOIN netbox AS b2 ON (to_netboxid=b2.netboxid) LEFT JOIN swportvlan ON (s1.swportid=swportvlan.swportid) LEFT JOIN vlan using(vlanid) LEFT JOIN swport AS s2 ON (s1.to_swportid=s2.swportid) WHERE swportid = 'some id' ORDER BY b1.sysname,ifindex LIMIT 1000 OFFSET 0 Switch ifindex interface module port link Mbps duplex media trunk vlan direction Description Connected to Remote if Configuration error! The report generator is not able to do such things.FEIL: column reference "swportid" is ambiguous SELECT b1.sysname,s1.ifindex,s1.interface,m1.module,s1.port,s1.link,s1.speed,s1.duplex,s1.media,CASE WHEN s1.trunk THEN 'Y' ELSE '' END as trunk,vlan.vlan,CASE direction WHEN 'o' THEN 'Up' WHEN 'n' THEN 'Down' ELSE 'N/A' END as direction,s1.portname,b2.sysname AS to_netboxid,s2.interface AS remote_interface,s1.swportid,b1.netboxid AS netboxid,b1.catid FROM swport AS s1 JOIN module AS m1 USING (moduleid) JOIN netbox AS b1 USING (netboxid) LEFT JOIN netbox AS b2 ON (to_netboxid=b2.netboxid) LEFT JOIN swportvlan ON (s1.swportid=swportvlan.swportid) LEFT JOIN vlan using(vlanid) LEFT JOIN swport AS s2 ON (s1.to_swportid=s2.swportid) WHERE swportid = 'some id' ORDER BY b1.sysname,ifindex LIMIT 1000 OFFSET 0 Any errors in report.conf or is mine outdated ? Regards Odd Arne Hauge
participants (2)
-
odd.hauge＠hiMolde.no -
vidar.stokke＠ntnu.no