Wireless Water Cooler

My Central license server (NBP-WLC-Aruba-01)  is running 6.4.3.7 and I recently upgraded 2 controllers (NBP-WLC-Aruba-03 and -04) to  Version 6.5.0.2 and since that time they are not picking up thier licenses from the Central Licensing server/controller.

(NBP-WLC-Aruba-01) #show license heartbeat stats

License Heartbeat Table
-----------------------
Client IP Address  HB Req      HB Resp     Total Missed  Last Update (secs. ago)
-----------------  ------      -------     ------------  -----------------------
172.24.1.4         392230      392230      0             607425   
172.24.1.3         401999      401999      0             607410   
10.3.252.46        480790      480790      0             8        
10.3.252.45        480771      480771      0             7   

(nbp-wlc-aruba-04) #show license heartbeat stats

License Heartbeat Table
-----------------------
Server IP Address  HB Req      HB Resp     Total Missed  Last Update (secs. ago)
-----------------  ------      -------     ------------  -----------------------
10.3.252.45        20211       0           20211         607122

On the Licensing server I see log such as these but i have not been able to find out any information on these yet:.

Nov 1 11:13:32 <licensemgr 399816>  <ERRS> |licensemgr|  Unable to unmarshall TLV received from client
Nov 1 11:13:57 <licensemgr 399816>  <ERRS> |licensemgr|  Unable to unmarshall TLV received from client
Nov 1 11:14:32 <licensemgr 399816>  <ERRS> |licensemgr|  Unable to unmarshall TLV received from client
Nov 1 11:15:57 <licensemgr 399816>  <ERRS> |licensemgr|  Unable to unmarshall TLV received from client
Nov 1 11:16:57 <licensemgr 399816>  <ERRS> |licensemgr|  Unable to unmarshall TLV received from client

(NBP-WLC-Aruba-01) #show datapath session table | include 8389

         
172.24.1.4      10.3.252.45     17   8211  8389   1/0     0    0   0   pc2         2    0          0          FYCI           
10.3.252.45     172.24.1.3      17   8389  8211   0/0     0    0   0   pc2         8    0          0          FYI            
172.24.1.3      10.3.252.45     17   8211  8389   1/0     0    0   0   pc2         8    0          0          FYCI           
10.3.252.45     10.3.252.46     17   8389  8211   0/0     0    0   1   pc2         12   1          430        FI             
10.3.252.45     172.24.1.4      17   8389  8211   0/0     0    0   0   pc2         2    0          0          FYI            
10.3.252.46     10.3.252.45     17   8211  8389   0/0     0    0   1   pc2         12   0          0          FYCI                  

(nbp-wlc-aruba-04) #show datapath session table | include 8389
10.3.252.45     172.24.1.4      17   8211  8389   1/0     0    0   0   local       5    0          0          FYI            
172.24.1.4      10.3.252.45     17   8389  8211   0/0     0    0   0   local       5    1          446        FCI            

I'm thinking it is the code version but I'm getting ready to upgrade my code WLCs as well and want to make sure I don't break the licensing on my core controllers.

 update....

I bit the bullet and did the code upgrade on my 2 Master controllers and it does appear that the code version have to match, or at least there was something that changed from 6.4 to 6.5.

When I upgrade one of the core controllers it too lost access to the Central License controller.  I then upgraded the License server and all the other Master controllers were able to communicate again and all the controllers now have access to the Shared licenses again.

old topic, but for reference the 6.5 documentation says something about multi version, 6.4 didn't so it might have indeed changed

http://www.arubanetworks.com/techdocs/ArubaOS_65x_WebHelp/Content/ArubaFrameStyles/New_Licenses/Multi__Network.htm

Multi-Version Licensing
ArubaOS supports multi-version licensing, which allows centralized licensing clients to run a different version of ArubaOS than the primary and backup licensing servers. If a license is introduced in a newer version of ArubaOS, the primary and backup licensing servers set can still distribute licenses to licensing clients running an older version of ArubaOS, even if the licensing client does not recognize the newer license type.
This feature is only supported in deployment topologies where all are configured as master controllers. Both the licensing server(s) and licensing clients must be running a version of that supports this feature. The multi-version licensing feature is not supported in a topology where a single licensing server or a pair of primary and backup licensing servers are connected to one or more local controllers.

Thanks do36874, for this info. 

I ran into the same issue and after running licensemgr debug, it was obvious you had already hit this problem and did the dirty work :-D

Just wanted to say thanks for providing the info to the community!!