Cisco 4.2.209.0 Controller Code Release

  

Cisco released a new rev for the controllers, 4.2.209.0. I'm not really surprised Cisco is still supporting 4.2. There are a number of large healthcare systems still on the 4.2 rev. 

Table 3 Resolved Caveats 

ID Number	Caveat Title
CSCtb31111	Memory Leak in EAP framework task
CSCsl22707	AP1250 Resets During Boot Using POE from 3550 Switch
CSCsm84048	AP1250 does not get 20 W power if switch is configure for trunk port
CSCso50723	WLC2106 EAP-FAST PAC provision failed due to slow DiffieHellman
CSCsq09933	Converted AP w/ static IP ignores DNS after downloading full image
CSCsv77658	AP reset from watchdog timer expired
CSCsw31160	Lobby Admin username can be used for webauthentication
CSCsx07150	Voice gap when phone roams, if CAC is not configured on APs
CSCsx50408	LWAP DOS Attack trap message does not record the source MAC address
CSCsx69535	AP on different subnet lost connetion with WLC
CSCsx70889	Crash due to stack corruption caused by recursive tunnels
CSCsx71175	WLC broadcast dhcp does not comply with RFC 1542
CSCsy06464	H-REAP AP obtains IP via DHCP on wrong interface
CSCsy06689	Memory leak on 3.2.210.0
CSCsy30722	Next hop address stored in capwap doesn't get updated on rcving GRAT ARP
CSCsy97077	WLC Controller 'show run-config' is truncated, not complete, incomplete
CSCsz03148	Talwar crashes @ EAP Framework
CSCsz14243	Unable to enable the WLAN while the APs are joining
CSCsz26858	WLC crash Task Name: dot11b (usmDbSnmpRrmProfileFailureTrapSend)
CSCsz32424	Rogue not detected on wire using the arp
CSCsz38828	AMAC radio core dumps: transmitter seems to have stopped
CSCsz48244	4.2 Mobility Control path flapping up/down
CSCsz48460	AP crashing on dot11_tx
CSCsz49863	WLC Local EAP auth periodically fails with 792x phone using EAP-FAST
CSCsz58995	Reaper reset crash on WLC with 1 monitor AP
CSCsz64049	WLC crash - nf_iterate causes kernel panic/exception
CSCsz72416	Unexpected vlan is assigned due to failed to aaa override
CSCsz76796	PMK cache isn't updated
CSCsz82548	Clients can communicate even though clients auth status is "No"
CSCsz88241	Per user bandwidth contracts stop functioning
CSCsz89606	AP unable to perform DNS based on given DHCP DNS options
CSCta09996	Sometimes LAP can't join to WLC via alternative port in port redundancy
CSCta13941	AP rejecting association request with status code 13
CSCta19001	AP1000 reboots continously when applying fix for CSCsl90630
CSCta29484	Radio stops beaconing for 10-second period
CSCta40160	Dropping primary discovery request from an AP already joined to the WLC
CSCta45156	Upgrade to 6.0.182.0 Webauth login page text views as one long sentence
CSCta93380	WLC on 4.2.205.0 drops bootp packet
CSCtb12031	1142 / 1252 inconsistently ACKs Vocera (gen1) badge
CSCtb29243	ARP storm on inter-controller NAC scenario for quarantined client
CSCtb34971	WLC WISM loading 3rd party cert for web-auth disables HTTPS port 443
CSCtb36010	Lightweight AP responds on port 22 when SSH is disabled
CSCtb52563	WLC 4.2.205.0 crashes at spam_CCM_decrypt+124
CSCtb58091	WLC CPU Spike with emWeb - Controller Not Responding - No crash
CSCtb64994	Intermittent Webadmin and Webauth access on WiSM running 5.2.193
CSCtb74239	WISM crashed on task sshpmMainTask System Crash
CSCtc03575	Controller fails to redirect web authentication to external server
CSCtc15346	AP1252 fails to retransmit missing AMPDU packet in response to block ack
CSCtc45090	Controller sends wrong mac in ARP response, can cause mobility flapping
CSCtc91431	ReadOnly local management user can change H-REAP VLAN mapping
CSCtc97595	Only one of many Gratitous ARP packets are forwarded to client
CSCtd01611	Important TLS/SSL security update
CSCtd16938	WLC crash after passing invalid arguments to emweb
CSCtd26408	WCS 4.2.110.0 cannot modify external web auth redirection URL for WLANs
CSCte40517	WLC2106 reboots at pemReceiveTask
CSCte55458	Web-Auth: Web page takes a long time to display under heavy load
CSCte89891	Radio may stop transmitting beacons periodically
CSCtf63030	Radio may get stuck in RESET or DOWN state

Comments

[revolutionwifi]

It's also no surprise 4.2 is still around because of its stability. Version 5.0 was a feature release train and version 6.0 is a maintenance release train but has proven to be riddled with bugs which are still being resolved. In most large enterprises stability is golden.

Andrew