[cisco-voip] CCX 9.0.2 Licensing Issues

[Erick Bergquist]

Is NTP stratum part of the hash?    I can't wait for UCCX to use PLM
so we get away from the license hash.


On Tue, Dec 1, 2015 at 7:15 PM, Dan Mason <dmason at winxnet.com> wrote:
> 192.5.41.209 is the ntp server.  Ive been using it without issue for years
>
> Sent from my iPhone
>
> On Dec 1, 2015, at 8:11 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>
> There was a terminated bug report in 8.5 for this, not much detail though:
> https://tools.cisco.com/bugsearch/bug/CSCto67019/?referring_site=bugquickviewredir
>
> I would be curious as to what the clock strata on the primary server was at,
> prior to the reboot and the type of reference server?
>
> If you have root access and are familiar with the CET tool, you can change
> the server's MAC. The official (and supported) way to do it is through a TAC
> case; sometimes faster than GLO.
>
> -Ryan
>
> On Dec 1, 2015, at 7:33 PM, Erick Bergquist <erickbee at gmail.com> wrote:
>
> I've seen it once or twice on reboots. There is a licensemacchanges file
> under the install folder you can view.
>
> File view install ...
>
> I've also had the license Mac change in 8.5.1 when applying just a SU patch
> and no changes to the variables making up the hash.
>
>
> Erick
>
>
> On Tuesday, December 1, 2015, Ryan Huff <ryanhuff at outlook.com> wrote:
>>
>> Dan,
>>
>>
>> The server's licensing MAC address is a hashed hexadecimal value based on
>> several key settings in the operating system. Any changes to the following
>> list of OS settings will cause the License MAC on the server to change,
>> thereby invalidating the provisioned license file (which is bound to the
>> server's licensing MAC address). Did anything change on the server, that
>> would effect the licensing MAC, prior to the reboot? As you mentioned,
>> re-hosting the license through GLO (or reverting the change) are the only
>> remedial courses of action.
>>
>>
>> Things that impact the server's licensing MAC:
>>
>> Time zone
>> NTP server 1 (or none)NIC speed (or auto)
>> Hostname
>>
>> IP Address
>>
>> IP Mask
>>
>> Gateway Address
>>
>> Primary DNS
>>
>> SMTP server
>>
>> Certificate Information (Organization, Unit, Location, State, Country)
>>
>>
>> = Ryan =
>>
>>
>>
>> Email: ryanthomashuff at outlook.com
>>
>> Spark: ryanthomashuff at outlook.com
>>
>> Twitter: @ryanthomashuff
>>
>> LinkedIn: ryanthomashuff
>>
>> Web ryanthomashuff.com
>>
>>
>>
>> ________________________________
>> From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Dan
>> Mason <dmason at winxnet.com>
>> Sent: Tuesday, December 1, 2015 10:23 AM
>> To: cisco-voip at puck.nether.net
>> Subject: [cisco-voip] CCX 9.0.2 Licensing Issues
>>
>>
>> Hi,
>>
>>
>> Has anyone run into licensing not working due to invalid MAC address after
>> server reboot?  Ive had this occur twice over the last 12 months.  Single
>> CCX server on VMWare using Cisco .ova template.  I had to get the licensing
>> rehosted to resolve the issue.  I didn't see anything in caveats for the
>> release.
>>
>>
>>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> This E-mail and any of its attachments may contain Winxnet, Inc.
>> proprietary information, which is privileged, confidential, or subject to
>> copyright belonging to Winxnet, Inc.. This E-mail is intended solely for the
>> use of the individual or entity to which it is addressed. If you are not the
>> intended recipient of this E-mail, you are hereby notified that any
>> dissemination, distribution, copying, or action taken in relation to the
>> contents of and attachments to this E-mail is strictly prohibited and may be
>> unlawful. If you have received this E-mail in error, please notify the
>> sender immediately and permanently delete the original and any copy of this
>> E-mail and any printout.
>
>
> ________________________________
>
> This E-mail and any of its attachments may contain Winxnet, Inc. proprietary
> information, which is privileged, confidential, or subject to copyright
> belonging to Winxnet, Inc.. This E-mail is intended solely for the use of
> the individual or entity to which it is addressed. If you are not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may be
> unlawful. If you have received this E-mail in error, please notify the
> sender immediately and permanently delete the original and any copy of this
> E-mail and any printout.