02-04-2015 04:03 AM - edited 07-05-2021 02:26 AM
What are upcoming issues if we installed WLC 2504 software 7.6.130 or 8.0 with Cisco 3700 access points?
02-04-2015 04:41 AM
Hi Fahad,
There is not such a big issue with this code as i am using it from long time.
check the open caveats:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html#pgfId-1163097
Regards
Don't forget to rate helpful posts
02-04-2015 09:03 AM
Thanks for your response, actually we have WLC 2504 running software version 7.5.102.0 and we have 50 APs AIR-CAP3602e-x-K9. Now we want to add 25 more APs but this time we are going with 3700 series APs. For 3700 we should have software version 7.6.130 or 8.0. whether it will effect our current environment and what type of issue we can face...?
we are also looking for HA solution i want to know how it will work? Our service contract with cisco has already expire.. we have to renew that as well to upgrade and ait-ct2504-HA-K9 for HA of controller. and for license which option i have to choose
L-LIC-CT2504-UGP ?? whether its mandatory to license upgrade??
L-LIC-CT2504-25A
LIC-CT2504-UGP ?? whether its mandatory to license upgrade??
LIC-CT2504-25A
which package i have to choose to increase license??
02-05-2015 11:52 AM
A good idea to update the WLC, 7.5 code is no longer supported. Go to 7.6.130 or 8.0.110 and don't forget the upgrade the FUS as well.
"LIC-CT2504-UGP" is the "main" SKU where "LIC-CT2504-25A" has to be added under when ordering the license from Cisco. You can implement a N+1 redundancy model with the AIR-CT2504-HA-K9, which means that the access-points can join another WLC when the primary WLC fails. So really active/standby not active/active. With the 2504's there is also no synchronizing between the two WLC's about AP or client information, which means that there is no seamless fail over. Remember that the 2504 will allow an maximum of 75 access-points, so if you expect more growth in the near future maybe an other WLC type is a better choice.
02-06-2015 01:41 AM
Hi fahad,
As I understood that you want to install a 25 AP adder license to your WLC.
so you need to buy this: L-LIC-CT2504-25A
For HA you can buy a new controller: AIR-CT2504-HA-K9* (This will come with 0 AP license)
*** Make sure both WLC have the same software version (either 7.6.130 or 8.0)
How to configure both WLC, check this post: https://rscciew.wordpress.com/2014/06/07/n1-high-availability-configuration-on-cisco-2504wlc/
Reagrds
Dont forget to rate helpful posts
02-04-2015 06:19 AM
Hi,
Fahad can you further elaborate what you trying to achieve. what software version currently installed on your WLC ?
Regards
Zohaib
02-05-2015 09:26 PM
CLI Upgrade Procedure
In this section, you are presented with the information to upgrade the WLC with use of the CLI on the controller.
Step-by-Step Instructions
Complete these steps:
Make sure that the TFTP server is reachable from the controller, and make sure the upgrade file resides in the Root directory of the TFTP server.
Refer to the Wireless Software Center (registered customers only) in order to download the latest software images. Copy the files to the default directory on the TFTP server.
It is best to complete this procedure via the console port, but you can also SSH or Telnet (if enabled) to the controller's management IP address in order to complete the procedure. The use of SSH or Telnet results in the loss of connectivity with the controller during the reboot process following the image download. Therefore, console access should be available in order to expedite troubleshooting and recovery of the controller if the upgrade fails. Login to the controller and issue the show sysinfo command in order to verify the current software that runs on the controller.
This is sample output of the show sysinfo command, which shows that the controller runs 4.0.217.0:
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 5.0.148.0
RTOS Version..................................... 5.0.148.0
Bootloader Version............................... 4.2.99.0
Build Type....................................... DATA + WPS
System Name...................................... Cisco_48:53:c3
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.14179.1.1.4.3
IP Address....................................... 10.77.244.204
System Up Time................................... 0 days 0 hrs 1 mins 58 sec
System Timezone Location.........................
Current Boot License Level.......................
Next Boot License Level..........................
Configured Country............................... IN - India
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Complete these steps in order to define the download parameters:
Issue the transfer download mode tftp command in order to define the mode of file transfer.
Issue the transfer download serverip TFTP_server_IP_address command in order to define the TFTP server IP address.
Issue the transfer download path 'TFTP_server_path' command in order to define the path of the TFTP default directory where the controller OS software is located.
Issue the transfer download filename filename command in order to specify the name of the image.
Here is an example:
(Cisco Controller) >transfer download datatype code
(Cisco Controller) >transfer download mode tftp
(Cisco Controller) >transfer download serverip 10.77.244.196
(Cisco Controller) >transfer download path .
(Cisco Controller) >transfer download filename AIR-WLC4400-K9-5-2-178-0.aes
Issue the transfer download start command in order to initiate the upgrade process.
Here is an example of the upgrade process:
(Cisco Controller) >transfer download start
Mode............................................. TFTP
Data Type........................................ Code
TFTP Server IP................................... 10.77.244.196
TFTP Packet Timeout.............................. 6
TFTP Max Retries................................. 10
TFTP Path........................................ ./
TFTP Filename.................................... AIR-WLC4400-K9-5-2-178-0.aes
This may take some time.
Are you sure you want to start? (y/N) y
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Executing backup script.
Writing new RTOS to flash disk.
Writing new Code to flash disk.
Writing new APIB to flash disk.
Executing install_apib script.
Executing fini script.
TFTP File transfer is successful.
Reboot the switch for update to complete.
Reboot the controller after the upgrade process is complete in order for the new code to take effect.
Issue the reset system command, and enter y or yes in response to the question "Would you like to save them now?".
Upgrade the bootloader version (4.1 and later version upgrades only) using the AIR-WLCxxxx-K9-5-2-157-0-ER.aes file. The process is identical to steps 1 through 6 of this procedure.
Note: In the 2100 Series WLC, you cannot upgrade the bootloader version due to hardware limitations. Also, this model does not require a bootloader upgrade as do the larger WLC models.
Note: You can upgrade the boot image before or after the main image.
Here is an example of the boot image CLI upgrade process:
(Cisco Controller) >transfer download start
Mode....................... TFTP
Data Type.................. Code
TFTP Server IP............. 10.77.244.196
TFTP Packet Timeout........ 6
TFTP Max Retries........... 10
TFTP Path.................. ./
TFTP Filename.............. AIR-WLC4400-K9-5-2-157-0-ER.aes
This may take some time.
Are you sure you want to start? (y/N) y
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Writing new Emergency Bootloader to flash disk.
Writing new Emergency Bootloader RTOS to flash disk.
TFTP File transfer is successful.
Reboot the switch for update to complete.
The configuration is not kept when you downgrade versions of controller code. Controllers can be upgraded from one release to another. Should you require a downgrade from one release to another, you possibly cannot use the higher release configuration. The workaround is to reload the previous controller configuration files that were saved on the backup server or reconfigure the controller.
05-26-2015 05:22 PM
Please refer to the link :
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide