Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No License Available - Move a "Virtual Avaya IP Endpoints" License from one IPO500 to anot 2

Status
Not open for further replies.

stownsend

Technical User
Aug 11, 2004
355
US
We lost one of our IPOffice 500v1 until after a power hit. (took out UPSs too)
We have a way to run the phones from the remote office on the HQ IPO and I have created Extensions and copied the Users, Incoming call routes, etc over to the other IPO and things are working except some users are not getting "No License Available"

Each IPO has 84 "Virtual Avaya IP Endpoints" and I'm guessing that I jut hit that Limit after adding over the 20 people form the Remote Office.

How can I take the 84 Virtual Avaya IP Endpoints License from the Dead IPO and move it to the HQ IPO to support the other users?

Thanks!
 
Moved over the VCM Module and went from 84 to 96 Avaya End Points.

Yeah!
 
So R9.1 was Released and I have a New IPO 500v2 Chassis. My BP transferred the Licenses from the Existing Chassis to the new SD Card. We were all set to do the Upgrade on Monday and then one of the Techs Noticed that I have 20 Valid Avaya IP Endpoint Licenses and 96 Virtual IP Endpoint Licenses (There are two VCM64 Cards in the system) And said that the 96 Licenses wont be able to be Transferred from one System to the other and that I would need to Purchase another 96 IP Endpoint Licenses if I wanted all of them on the new system. We Currently have 83 in use, though I know we unplugged phones when the Remote Office System Crashed and we migrated those IP endpoints to the main IPO.

So Are the 96 Virtual IP Endpoints not Transferrable to the new IPO 500v2 Chassis? Won't I atleast get 2x12 per VCM64 card in R9.1?

Thanks,
 
96 virtual endpoints, 24 of them comes from the VCM cards.
The remaining 72 are converted from 24x VCM ch licences.

You should get these licenses in the dongle swap.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
Grabbing Popcorn... Is this a 9.1 "feature", or is the BP wrong.
 
Has been like this since R6.0.
Before that, VCM cards gave only 4 ch out of the box.
If you needed more, you bought VCM ch licenses.

When stepping up to R6.0+, all VCM ch are converted to IP endpoints, multiplied by 3. (That's why a VCM card gives 12 endpoints, 4ch x 3)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
Wanted to update you all, Hold onto your hats... Sad, the first time I worked with this BP from R5 to R8, it was smooth sailing. This time not so much...

So the BP sent out a new SD Card and v2 500 Chassis for the upgrade. The v2 Chassis came Damaged, though in a way that seemed like they took it apart as the cover screws were loose and parts rattling around inside. I asked for a replacement, they asked for the unit and the SD Card back.

So they sent a new Chassis, then sent the SD Card. It seems as though they either sent the same SD Card back, or they don't know what they are doing as the SD Card SN and the Chassis SN are not the same so going into System Status, All of the License Status show as Malformed, so the VCM Channel Migration licenses [(8+16)*3=72 + 12*2 VCM64 = 96 Virtual IP Endpoints) were not registering so no Virtual IP end point licenses.

They still have not figured all of this out, I'm having to point it out to them. Sad, sad, sad...

Wish you guys were here in California... Would of saved me all this grief...
 
The SD card holds the licenses so why did you send that back???
A chassis that is taken apart is odd as this should never ever be the case (ha ha word joke) with a new chassis.

BAZINGA!

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

 
I sent it back as the SD Crd was for the Broken Chassis. Thought they would need to return that as its Serial number was for the Broken Chassis and the new Chassis would need a new SD with the new Serial number associated to it.

Yeah, there was one internal support that was completely missing, one was loose with the screw and the case screws were all loose. Sad...

Scott<-
 
The chassis and card are not related to each other in any way, they are designed to be interchangeable otherwise it would just be hard wired memory :)

 
I thought that the Card had to have the Serial number of the Chassis embedded in it? Or at least the Licenses on it had to be Keyed for the SN of the Chassis? So I could not just take my SD Card and Pop it into a new IPO500v2 Chassis without having to transfer the Licenses on the SD to the new SN of the new Chassis.

When I looked in System Status with old SD and new Chassis, the SN from the SD Card was not the same as the SN of the Chassis, all of the Licenses showed with a Status of Malformed.
 
Licenses are tied to the S/N of the SD card, often referred to as dongle number.
You had a Smart card before, so you needed a dongle swap to get the licenses transfered to your New chassis type.

An SD can be moved to any 500v2 chassis.


Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
They already moved the Licenses form the IPO500v1 to the SD Card. That was the Card that Came with Broken Chassis.

The SD Card I had Was for the Damaged Chassis, they sent a new Chassis and the old SD Card back with the new Chassis. System Status was with old SD in the new Chassis, all of the Licenses showed with a Status of Malformed.

Looking up reasons for Malformed pointed me to a Serial number mismatch between the 'Dongle' and Chassis.
 
Well, SD card has never been tied to a chassis number, ever.

Tell you what, why don't you post the S/N of the SD card you have now here.
Some members have access to the Avaya database and if they're in the mood for it, they might look it up for you.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
They said they needed to send out a new SD Card and it should be here today or tomorrow and that would fix the Malformed License Issue.

This is the Card that I have in the System now that shows everything as Malformed.
Local, Serial Number 1371524442 PLDS Host ID 111371524442
Avaya ID: 700476005
Chassis SN: 14WZ41400343

Sad thing is that I've been trying to get upgraded since Last November. It got so late that It was Close enough to the 9.1 Release so I said to wait for that. It came out in January some time I believe and we are no further along here in May. )-:

My IPO 500v1 Chassis rebooted on its own again today. It have been doing this once or twice a month for the past 3-4 months. The other reason we have wanted to upgrade, once we lost our SF office IPO to a Power Hit we knew this was was not far along.
 
Actually, waiting this long before stepping up has probably saved you from a ton of frustration, it's not exactly flawless :)

Best way to kick off on this release is to build a new config from scratch.
Check the PCS label on the chassis, 14 and lower needs to be booted on R9.0, then upgraded to R9.1
Don't do anything with the IPO before you have reached R9.1, or else you need to buy an upgrade license as well.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top