Re: C1240 AP

lni1 · ‎10-16-2006

Hello,

Recently we installed some C1240 AP's, unfortunately in Ciscoworks they are not recognized as AP, they remain in the section unknown devices. When I try to download a device package, Cisco responds that there are no packages availabe, what can be the problem ? In the classifications of CW I can't find it either.

David Stanford · ‎10-16-2006

This sounds similar to bug CSCsc68458

In this case the AP's were reporting an incorrect sysObjectID. What is the sysObjectID reported for the AP?

This happens when the AP's go from lwapp to IOS conversion and affects code 12.3(07)JA02.

This makes it unmanageable by NMS apps

including WLSE and LMS. The fix for this problem is a code upgrade.

---------------------------------------------

However, it could also be due to snmp timeouts while querying the CISCO-FLASH-MIB on these devices. try increasing snmp timeout to 60 seconds and resubmit the devices.

lni1 · ‎10-17-2006

Hello Davistan,

I tried to increase the snmp value, but no result.

On the back is noted : AP1242AG, in CW I found :

1100 series WLAN Access Point with 1 10/100TX port, 1 IEEE 802.11 radio port

IOS is 12.3(7)JA1

What do you mean by code upgrade ? (soft upgrade ?)

David Stanford · ‎10-17-2006

Can you do an snmpwalk of sysObjectID? What value does it return?

lni1 · ‎10-17-2006

Hello Davistan,

system.sysObjectID.0 : OBJECT IDENTIFIER: .iso.org.dod.internet.private.enterprises.cisco.ciscoProducts.685

So it corresponds with the Cisco Aironet 1240 series access points, it's in the list of supported devices, now what, any thoughts ?

Many thanks

Lieven Stubbe

Belgian Railways

David Stanford · ‎10-18-2006

what value did you increase the snmp timeout to? What version of RME are you running?

lni1 · ‎10-19-2006

RME 4.0.3

In "Admin > System Preferences > RME Device Attributes" I increased the value from 15 to 60

Many thanks for your contribution

Lieven Stubbe

Belgian Railways

lni1 · ‎10-25-2006

In the devicelist I can't find an OID like

1.3.6.1.4.1.9.1.685

I tried everything, still no change.

I really need a solution for this problem, we have already deployed 50+ such AP's and I don't feel to configure these manually !!

Many thanks

Lieven Stubbe

David Stanford · ‎10-25-2006

What does Check device credentials report for these devices?

you might want to turn on some inventory debugs and remove/add these problems devices (start with one only)

Remove it from the DCR

Then go to:

RME-->Admin-->System Preferences-->Loglevel Settings

Select ICServer and change from Info to Debug for all 3 items. Then try

to add the AP again and look in the IC_Server.log file to see if there are any errors.

lni1 · ‎10-25-2006

The CDR says failed everywhere.

I changed the Loglevel settings for the ICServer to Debug and here are the results when I do a delete/create of the node,

it doesn't say much to me, perhaps you see more,

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-24],com.cisco.nm.rmeng.inventory.ics.core.ICSCore,173,Got Async Request, User Name :admin

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-24],com.cisco.nm.rmeng.inventory.ics.core.ICSCore,179,Request ID is : 1161350734458

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,155,Started processing device ID: 2471

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,194,Started processing device Name: 10.2.51.200

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,239,DP time is 0 seconds for 10.2.51.200

[ Thu Oct 26 09:49:19 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,882,New device added

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,995,About to update DM for DeviceID 2471

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.server.InvDataProcessor,1001,Updated DM for DeviceID 2471

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,454,Total time before Callback is 1 seconds for 10.2.51.200

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.util.logger.RMELogger,724,com.cisco.nm.rmeng.inventory.ics.dm.ICSDMCallback,icsCallBack,82,Called DM, status 5 for Device 2471

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,457, Finished processing device 2471 10.2.51.200

[ Thu Oct 26 09:49:20 MEST 2006 ],INFO ,[Thread-20],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,463,Total time is 1 seconds for 10.2.51.200

I also did NMS to device :

Test Results

HTTP Okay

sent: 5 recvd: 5 min: 36 max: 36 avg: 36 timeout: 2 size: 33 protocol: http port: 80

TFTP Failed

sent: 5 recvd: 0 min: 0 max: 0 avg: 0 timeout: 2 size: 25 protocol: tftp port: 69

SNMPRv1/v2c Okay

sent: 5 recvd: 5 min: 1 max: 2 avg: 1 timeout: 2 size: 91 protocol: snmp_get port: 161

SNMPWv1/v2c Okay

sent: 5 recvd: 5 min: 1 max: 1 avg: 1 timeout: 2 size: 99 protocol: snmp_set port: 161

SSH Okay

TELNET Okay

Here everything is fine, but in DCR everything marks failed, I don't get it !!!

Anyway, many thanks in advance for your support

Lieven Stubbe

Belgian Railways

Joe Clarke · ‎10-26-2006

AP1240 support wasn't added until RME 4.0.5. If you do not have version 3.0 of the RME AP1200 device package, then you do not have support for this AP.

You should upgrade to LMS 2.6 which is a free download on Cisco.com. That release comes with AP1240 support out-of-the-box.