[Nav-users] How to add Cisco 6506 in MetaNAV

-- mvh Morten Brekkevold UNINETT >From vidar.stokke at ntnu.no Fri Apr 13 16:56:45 2007 From: vidar.stokke at ntnu.no (Vidar Stokke) Date: Fri Apr 13 15:56:47 2007 Subject: [Nav-users] Cisco Wireless Lan Controller and NAV In-Reply-To: 8EEE7738AEDF6947B3E5508A0244D1C2DE14F6@stam.himolde.no References: 4ddd24660703121031h716cb122q8cee4ba790fc632@mail.gmail.com 45F93D04.4080707@uninett.no 8EEE7738AEDF6947B3E5508A0244D1C2631EDE@stam.himolde.no 461F48A8.3040705@uninett.no 8EEE7738AEDF6947B3E5508A0244D1C2DE14F6@stam.himolde.no Message-ID: 461F8C1D.6020405@ntnu.no 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