corrupt extension

[ghost]

Hi

Wondering if anyone has any ideas how to remove a corrupt extension

I have a cluster for 4 controllers and I have one extension that when I log into controller 1 it says that its primary element is controller 2 and its secondary element is controller 1. On Controller 2 that same extension reports its primary element is controller 1 and its secondary element is controller 2

As such I cant delete this extension because both controllers tell me to go to the primary element

[martyn]

Are there any SDS sync errors between the two?

Only way will probably be to delete it from the DB through the back end, which would require Mitel assistance to do so "technically"

[august]

You will have to do it with sdsdebug on.

[ralph]

What happens if you resync the elements?

Ralph

[pmhaynes]

Have u heard the one about changing a name of one of your elements. Just add a 1 or something. After u done that you'll see in the logs all elements syncing


Sent from my iPhone using Tapatalk

[ghost]

Hi Guy

Thanks for the help pointing me in the right direction.

A device level resiliency sync with primary and secondary host appears to have resolved the issue.

Extension is now deleted.