grace period 3

[sheldoom]

Installing SE R11.1.3.1 with 2 IP500 expansions. No calls were made on the expansion shipped to Mexico, yet I still get the message that the grace period has expired. The expansion is not getting the SE license or SIP trunks licenses from the server. How do I get it out of this Grace period expiry mode, so it will take the needed licenses?

Thank you,

 

[sheldoom]

Using PLDS licensing not WebLM.

 

[sheldoom]

Should I run the initial configuration again?

 

[Diya Freahat]

Do you see the grace period days and grace plds host id on manager-license for the primary server?

 

[sheldoom]

No. I do see a System ID has changed: You must acquire a license based on the new System ID days remaining 24, but this was 20 days ago and it's in black not red. The other IP500 expansion had license errors on 11/14 but those have cleared and it shows a valid SE license that expires - Never. The licenses on the Server Edition and 1st IP500 expansion all look good at the moment.

 

[sheldoom]

SE -
IP500 Expansion in Mexico -
IP500 Expansion in US -

 

[sheldoom]

I tried running the initial configuration and also regenerated a new PLDS license and neither of these resolved the issue

 

[sheldoom]

As you could see from the one snip that the time was off on the Mexico IP500, but that has been resolved now. Time is poling good. License errors remain.

Thank you,

 

[derfloh]

You have to resolve the error that communication with license server (primary server) doesn’t work.

Maybe a firewall or a misconfiguration at the expansion. Either in license settings or in the IP Office line

 

[sheldoom]

Thank you Derfloh

It's connected and green in the Solution -


Here is the license Form -


If it was firewall, what would I have the customer look for in their firewall?

 

[biv343]

The last couple times I've added expansion systems to a SE solution, I've had to restart the IP Office service on the primary server before the new expansion would get a license. That was on 11.0.4, not 11.1, so may not apply in your case.

 

[sheldoom]

Restarting the IP Office service on the SE resolved this. Thank you!