Deployment IP Office Server Edition R9 - Prolem

[wfranklin]

Hello Guys,

Today I tried configure a IPO Server Edition R9 w/ two Ctrl Units as Module Expansion. Well, I had a problem when I tried add the Module Expansion on the Server... The Server report me that dont have a license valid.
But, I checked the file license and there are licenses, when I applied the licenses are "Invalid". After several attempts the "Module Expansion 01" has been added, even the license "Server Edition" w/ error (invalid) and I saw the licenses and show me a new license "Virtual Server Edition R9". Whats this license? This automatic? Why the other Ctrl Unit (Module Expansion) dont created this virtual license??

While this, the Expansion Module 02 arent configured, because the same error persisted.

Any idea?

All systems are the same release 9.0.0.829

Thanks

 

[wfranklin]

Explain more about my topology

In the Server I need only H323 Extensions and on the Module Expansions (Control Unit) I need E1 and some analog extensions... So, I need one lincese "Server Edition" for each system correct? One license on the Server, one license Module 01 and one license Modulo 02, correct?

If yes, the Avaya sent me incorrect files, dont have other explanation! or Have?

 

[tlpeter]

Almost all licenses go on the server, keep that in mind.
So the server edition licenses are all on the server, also the licenses for the expansion systems.
When the expansion systems are connected then they will show a virtual server edition license so that is good.

The only licenses that you can put on the expansion systems are these licenses:
Additional PRI channels
CTI pro
CTI wav users
IPSec tunneling

All the other licenses should be on the primary server.
After adding an expansionsystem you must also reboot the server to add it to the config.



BAZINGA!

I'm not insane, my mother had me tested!

 

[iramipo]

Hi wfranklin,

Make sure that you have 3 server edition R9 licenses for each system module(Server, Control Unit1, Control Unit2). And all these server edition licenses has to be loaded in the server(Primary) only. And the H.323 IP phone licenses also should be loaded in server.
The E1 trunk licenses you can load any of the control unit where you are going to terminate the E1 link.

Hope this clear..

rgds
iramipo

 

[wfranklin]

@tlpeter

Hi man !

So, I thought this but reading the guide (

https://downloads.avaya.com/css/P8/documents/100175142

- pag 31) we can see that all systems must have the license.

And how can I added the the Module Expansion? I think I'm doing wrong...

- reccriate SD CARD
- Initial Configuration set to "Expansion" and here all informations (IP, IP from server etc)...

After all this, the module has conected, but give me error about license... And on the Server I've 3 licenses "Server Edition" (Primary and each Module).

Thanks for your attention

[]´s

 

[tlpeter]

Yes every system must be licenses but through the primary server
Check system status and go to licenses and then you will see what i mean.
The primary server allocates the licenses where it needs to.


BAZINGA!

I'm not insane, my mother had me tested!

 

[jmperry]

I have a similar issue - One of my Expansions is not able to get the License from the Primary. I think there is a Port blocked but cant figure out which one.

Does anyone know what Port that would be?

 

[wfranklin]

@iramipo

Hi bro!

So, I've cheked the licenses man! This seems that the license on the server is wrong... because when I added the module the error still.
With erros my H323 trunks (on the module) are disable, and I cannot make calls.

Is there any way/chance that the licenses is wrong?

Thanks man, regards

 

[wfranklin]

tlpeter

I cheked... and show me "active". But the Module cannot get the "license".

 

[wfranklin]

any idea ?

 

[jmperry]

I am still having the same issue - Something is blocking the Remote site from seeing the Server Ed License on the Primary Server. Just cant figure out what it is. Trunk shows ok on the Primary Server - Remote IP500V2 shows disabled since it does not have the License.

 

[wfranklin]

Jmperry

Oh man, so we have the same problem.
I cannot solve this.

 

[jmperry]

I am trying just for fun, as I have nothing better to do on my Sunday- Upgrading to the latest Service Pack for 9.0 - I will let you know if I have any change

 

[wfranklin]

Good luck man.
Please, dont forget rs.

 

[wfranklin]

jmperry

Hi bro ! Do you have news? Today I can to do a new test, and I saw that when I remove the "remote license server" with IP Address set for my Server Primary the trunk is changed to "down". Can you verify this on you enviroment??

Regards

 

[wfranklin]

any updates?

 

[VTTD1870]

How did this get resolved?

 

[smokinjoe2938]

We are also having this same issue, didn't see any resolution on this, can anyone tell me why my 6th expansion control module does not get a license, all licenses are loaded on the primary server and we do have an available license for this. Currently this is set up in a lab enviroment, any help most appreciated.

 

[derfloh]

I'm pretty sure it is a network issue. Something is blocking a port I don't know about (should be 50795 IIRC) or some kind of ALG changes packets. I had the same issue with R9.1 SE. Servers and two expansions at the main site (even if in different VLANs connected through routing core switch) everything was fine. All remote sites (connected through VPN tunnels) didn't get licenses with the exception of one expansion system. That one system had a different VPN router than all the others. But we had not been able what little 'switch' we would have had to use in the VPN router to solve it.

Glad that we have 9.1 so I could solve it by changing trunk type from proprietary to WebSocket where every single packet will go through a HTTP/HTTPS tunnel.

 

[smokinjoe2938]

in a lab right now so could be a flaky port on data switch, we will change data ports and are upgrading to the latest manager 9.1.1 and will see what happens.