WLC 5508 rebooted but still showing high uptime

Question

Hi all,
I had to reboot our production WLC 5508 last night to apply a new adder license, which increased our AP count by 25.
We run a DMZ mobility controller alongside the primary controller, which handles our mobile/guest WLANs using a Mobility Anchor. Normally we would reboot both of these due to issues with the anchor after the primary is rebooted.
So last night I rebooted the primary after installing the new adder license. Once it came back up, I checked the license count and it had increased as per the new license. After that I rebooted the mobility controller, and waited to ensure that this came back up.
Almost straight away, all the AP's had re-associated with the primary (all 96 of them), and clients were starting to show up. I checked the same on the mobility controller (although this does not manage any AP's) and I could see mobility clients associating with this also.
The problem came this morning, when none of the mobility clients that were connected to the mobiltiy WLANs were able to get to the Internet, or any kind of outside connection. This is the typical issue we see when our core switch gets rebooted, or the primary on its own, without rebooting the secondary.
So to troubleshoot this morning the first thing I suddenly noticed was the uptime on the primary controller. It showed 298 days!!
Anyone seen this behaviour before? The WLC DID reboot - I watched it go down and POST again. Why would the uptime counter not reset?
We're on firmware 7.2.111.3 - which I realise is pretty old, but due to CIsco screwing us over with a limited upgrade path, we are not able to upgrade it yet (AP hardware not supported on any of the newer code above this version).
Any help appreciated!

Answer 1

In response to Sandeep, here's the sh sysinfo output:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.2.111.3
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... UK***********
System Location.................................. Slough CoLo
System Contact................................... Greg Dent
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 172.17.1.40
Last Reset....................................... Software reset
System Up Time................................... 0 days 3 hrs 42 mins 23 secs
System Timezone Location.........................
Configured Country............................... Multiple Countries:GB,RU,US
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +44 C
External Temperature............................. +26 C
--More-- or (q)uit
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 794
Burned-in MAC Address............................ **************
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 125
As you may notice, the uptime has now reset, but thats because I had to reboot it again this morning. I didnt grab the output before the second reboot. It seems whatever issue caused the uptime counter not to reset didnt occur this time.
Very odd.