IPO Server Edition 11 - License issue

[Mattatron]

I know I am probably missing a simple step here and we all know Avaya docs are not helpful.

I have an IPO SE Release 11 I am configuring with an Avaya supplied server. I have the licenses installed on weblm, I have the IPO Server updated to the latest service pack, and I have the license tab remote server tab set to weblm pointed to the ip entered in the weblm enterprise tab.

In weblm, i have the entreprise config IP address set to 192.168.42.10 which is the IP of my LAN 1 on the server. In weblm allocations, I can see all the licenses available but not allocated.

When I log into manager to assign/reserve the licenses, all the IP Endpoint licenses are greyed out and it looks like I am running of the grace period licenses. System status says WEBLM is normal and connected. Manager says the server unit license mode, weblm error

I could use some help and don't mind calling myself an id_10_T when it is determined to be something stupid that i am doing.

FYI my end goal is to have a primary and secondary server, each with an expansion control unit attached. The set design is a mix of ip, digital and analog running on PRI. I do not have the secondary connected yet

FYI 2 I have also contacted Avaya support and talked to them, they are looking into it on their end

 

[Mattatron]

For the sake of trying everything, i setup an IP user anyways. Weblm is now showing 1 endpoint reserved.

However my prime server license mode is still saying Weblm error

My expansion control unit says it is connected to weblm

Update
The phone has registered and pulled its information. System status shows 1 (1 reserved) in the licenses in use
and
The server unit shows 1 IP Endpoint license assigned in manager but still grayed out

Update 2
No word of a lie, after 3 reboots and no additional changes, maanger is now saying that the server unit is connected to Weblm. Other issues points above still exist though

 

[critchey]

Are there are errors like like to many IP phones created compared to how many licenses you have or to many receptionists configured for how many licenses you have? If you do something like this the WebLM will not allocate ANY licenses to that system. Make sure you do not have any kind of configuration issue that would cause you to be trying to use more licenses then you actually have. I ran into this issue myself first time using Server Edition.

The truth is just an excuse for lack of imagination.

 

[Mattatron]

@critchey,

There are no other errors showing up on Manager minus the standard voicemail code warnings because i haven't done anything with those yet.

I have only created 1 IP user (SIP Extension on a j179). I have no other users created

Total licensed to the Weblm is 160 IP Endpoints, 10 PU, 3 Reception, 16 PRI. Not of which have been assigned.

 

[critchey]

The IP endpoints will always be grayed out they get allocated automatically. Does system status say WebLM is connected or show an error? If error you would need to run monitor and see if there is something to figure out why. If it is connected (sounds like it since you created an extension and it allocated an IP endpoint) then it sounds like it is working normally. Some licenses are automatically allocated(like IP endpoints) and some you allocate (like SIP trunk channels).

The truth is just an excuse for lack of imagination.

 

[Mattatron]

Thanks critchey,

The Weblm error is gone now. I didn't do anything besides multiple reboots.

I think i have to agree with you about licenses not showing. I noticed a key word in one of the documents that may explain it, they called it "floating licenses". That is the only explanation i can find that is close to explaining this

Now hopefully Avaya will confirm this and I can begin my programming/install without having to worry about the system going down in 30 days.

I am almost thinking it may be easier (and provide peace of mind) just going back and rehosting in PLDS and keeping the licenses local.

 

[critchey]

Ya sometimes it takes some reboots it happens. As long as system status is not showing an error you should be fine and it does give you 30 days to fix an error with any kind of connection to the WebLM which is pretty good.

If you are running a virtual environment one issue I ran into was the time on my vmware was off and it would randomly make my time on my Server Edition off which would cause the WebLM to error out. Once I fixed that our test system has had no issues with any licensing and what I learned has helped with customers sites and have not run into much issues with their machines. It works pretty well to just let the WebLM allocate licenses as needed to be honest. It is a good idea to have the system sending you emails on errors so you know if it loses connection and you should never be surprised and hit the end of that 30 day grace period which is plenty of time to resolve issues.

The truth is just an excuse for lack of imagination.