Prime 1.4, WLC 7.6, Cisco 3700…. when will an end be near!?

As I am preparing for an uprade to a high density area using Cisco equipment, I am looking to implement 802.11ac. I must future proof this project for 5 years. With wave 2 on the horizon and wave 1 in the books, utilizing ac for this deployment made sense.

Or so it would seem……

I, like many others am facing the challenge of preparing my infrastructure for supporting the 3700.

Here is my environment today:
Prime 1.3
MSE 7.4
WLC 7.4 (& 7.0)

I will be upgrading my PI to 1.4 first, installing patch 1.4.1. Then, upgrade MSE to 7.6 and finally my WLCs to 7.6 (starting with a single controller for just the 3700 APs).

This upgrade path will allow us to have minimal impact to clients an begin supporting the new 3700 AP. However, many undocumented features (bugs) have been seen with the 7.6 WLC code. Many not yet ID’d by Cisco yet.

I hope to share these challenges in this post as I work through them and will keep you updated on the progress.

One thought on “Prime 1.4, WLC 7.6, Cisco 3700…. when will an end be near!?

  1. TJ McClinticTJ McClintic

    Well, certain enough I ran into a bug with TFTP’ing to the new 1.4 Prime Installation.

    I was entering an incorrect filename, but the error was that the server was unreachable. I did not review my tftp server for the error log at first, but this was shown there.

    I dropped into root mode (root_enable/set pass) then root.
    I then ran the command modprobe ip_conntrack_tftp
    Typed exit and I was back into the NCS admin OS

    Now I am seeing the error incorrect filename. I resolved that issue and am running the upgrade after creating my respository.


Leave a Reply to TJ McClintic Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>