Server Edition - Invalid Licenses 2

[VTTD1870]

Installing Server Edition on R210 physical servers. Ignited Primary and Secondary servers. Input licenses (ADI Nodal) into the primary server and they are showing up with Status: Invalid. What am I missing?

 

[shardian]

Are the licenses for the correct server? If you did the ignition process yourself, perhaps the SID that the licenses were ordered against is what you setup as the secondary...
EG disti ordered keys against one server (primary), shipped your 2 servers, and you have setup what they meant to be the secondary as the primary.

Hope that made sense...

 

[tlpeter]

Did you order the licenses before or after the ignition?
When you do the ignition then it will create the ID based on different configurable items as well.


BAZINGA!

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

 

[shardian]

Peter - thats only true when virtualised isn't it?
The SID should remain the same on a physical server. The SID is on one of the labels of the server, so if it changed, there'd be all sorts of issues.

 

[tlpeter]

I am only familiar with the virtual SE so you could be right.
If this is the case then it is not your problem at all and i would make a call right now

BAZINGA!

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

 

[VTTD1870]

I have two servers. The licenses were issued against what I have setup as the secondary server. Hopefully I can have a new set of licenses issued. Do you see any problems with this?

 

[tlpeter]

The licenses should be on the primary server.
You could reinstall the server and make the secondary the primary server and the primary the secondary.


BAZINGA!

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

 

[VTTD1870]

I was hoping to avoid having to reinstall and just have the licenses recreated against the Primary Server's Serial Number. Thoughts? And, thanks for your responses.

 

[tlpeter]

You could request them but it takes time and you could have been done already

BAZINGA!

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

 

[shardian]

I'd just reinstall the ISO again and do the ignition again.

It'd be good if they gave us a way to run ignition again....

 

[AvayaNACR]

There are 4 factors that control the SID:
1. Lan 1 IP Address
2. Lan 2 IP Address
3. Host Name/ ID
4. Time Zone

Avaya's stance is changing these could change the SID. In reality we have changed IP routes on a system and had the SID change.

A R210 is still a 3rd party server and I suspect subject to similar issues. I would confirm he SID against what you used on the order...

 

[VTTD1870]

I ended up reinstalling rather than changing the licenses around. All is good. Thank you for the responses.

 

[tlpeter]

AvayaNACR (Vendor) 16 Oct 14 16:32
There are 4 factors that control the SID:
1. Lan 1 IP Address
2. Lan 2 IP Address
3. Host Name/ ID
4. Time Zone

This is for a virtual server i think.
Because the hardware server has the id on a sticker the IP addresses and hostname should not matter.

BAZINGA!

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

 

[VTTD1870]

Yes. That is my understanding as well.

 

[DrDrayAvaya]

shouldn't the licenses be from within PLDS, so should let you change the license entitlement to a different host address anyhow? not sure on how this all works completely yet, but my understanding is that it should allow reallocation to new host (in event of hardware failure for instance?) I understand there is no strict policy on this, rather fair interval between changes. brave new world.

 

[tlpeter]

This is still ADI.
PLDS is used when the IPO is a branch edition on to a CM.
I guess that it all will move to PLDS in the future.


BAZINGA!

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