Chapter 1 FAQs and Troubleshooting

Firmware FAQs and Troubleshooting

Symptom An SCP job fails with username having 15 privilege.

Possible Cause If the device is having the following configuration:

aaa new-model

no aaa authentication login default no aaa authorization exec default

Logging in with privilege 15 username/password, requires that the enable secret/password be entered in exec mode.

Recommended Action Configure the authentication to use local or server level authentication.

Firmware FAQs and Troubleshooting

Firmware FAQs, page 1-27

Firmware Troubleshooting, page 1-28

Firmware FAQs

Q.I have an AP 1232, but under Firmware > Images > Import, there is no AP1232 Device Type to select. Which one should I choose?

Q.How can firmware images be imported?

Q.Are firmware jobs run by using both HTTP and SNMP?

Q.What kinds of job logs are available?

Q.How many devices can I have in one firmware job?

Q.Can I give a firmware job a name that is used for a configuration or radio management job?

Q.I have an AP 1232, but under Firmware > Images > Import, there is no AP1232 Device Type to select. Which one should I choose?

A.AP1210.

Q.How can firmware images be imported?

A.Firmware images can be imported to WLSE from the desktop as well as Cisco.com. While importing any image from Cisco.com, the WLSE reads the version string and the device type for the image attributes. For imports from the desktop, you must make sure that the version and the device type strings are correctly entered in the image attributes.

Q.Are firmware jobs run by using both HTTP and SNMP?

A.No. Firmware upgrades use SNMP only. Make sure the following setup parameters are in place before running the upgrade job:

SNMP credentials for the device (with admin and firmware privileges on the AP) must match those entered on the WLSE SNMP device credentials screen.

FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine

 

OL-8376-01

1-27

 

 

 

Page 39
Image 39
Cisco Systems OL-8376-01 manual Firmware FAQs and Troubleshooting