CM 8 - Can't add stations

[wpetilli]

New CM 8 deployment in AWS. Getting 'duplicate entry' when trying to add any IP stations. Confirmed they don't exist in the system and are setup as extensions in CM.

 

[Sean655]

List extension xxxx
List usage digit xxxx

See if anything comes up.

 

[wpetilli]

no data in the system to list.

 

[kyle555]

Are you licensed? Iff you "add" and do "help", is "station" a thing you can add?

have you done a reset 4 since the first time it came up?

Duplicate entry is most certainly a wrong error, but there are a few reasons you can't add stations to a brand spanking new CM.

 

[wpetilli]

It was a backup of a 6.3 and restore to 8 a few weeks ago. The license looks fine and has plenty of capacity. I've made tons of changes to it in the last few weeks. Last week I had an issue with the dup command working intermittently and a reset 4 was done. That seemed to alleviate, but now I can't add or dup w/o that 'duplicate entry' error. I can remove and change, but the other commands don't work. They are available for commands and I enter all the info of what I want to add, but after hitting enter that's what spits out. After removing, I run the list usage command and disp stat commands and the station I removed is not in the system. However, can't add it back or any other for that matter. Not that it mattered, but I went into SMGR and tried the element cut through and had the same issue.

 

[kyle555]

Call them. That sounds ugly.

Hindsight being 20/20, if I ever have to do that, I'll restore that 6.3 on a 8.1 VMware first and back that up and restore to AWS!

 

[wpetilli]

In the list history log I see DENIED -10817 not finding that error anywhere I search.

Yea, have to reach out. I know they (bp) restored to an 8.x first, then upgraded to 8.1. Since they did it in on a test system I'd hesitantly assume it was on a VMware build.

 

[wpetilli]

Out of nowhere this started working again. what the heck. Same thing last week.

 

[wpetilli]

I was able to trigger it again by trying to change my set type. Once I tried changing it, it logged my phone out, I logged back in and it didn't update. Tried again and got dup entry. Then all of dup stopped working.

 

[dialtonebone]

Any chance that your duplex is interchanging? This issue sounds bizarre and interesting all at once.

 

[wpetilli]

nah, been checking that. BP opened an avaya ticket. They indicated they saw this issue with another customer and it resolved itself after the cutover. I guess the new environment was spun up and a restore of data was done. Then, during that change freeze, the new system had tons of alarms because everything was still pointing to the old system. They thought it was the alarms, logs filling up and resources being utilized that was causing it. That 'could' be true, but I'm not waiting for a large cutover to have an issue with the administration. no sir

 

[AvayaTier3]

The errors indicate you have software corruption.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[wpetilli]

The BP reported back that avaya has other tickets with the same issue supposedly.