ICP/PBX Networking Issue

[Mitelmike2010]

I have a clustered site where one of the elements on an MXe Controller has been set to YES for the Local ICP/PBX. Basically another element in the table has been set to local and not the PBX that the configuration is on.

Any suggestions on an easy change. When you try and change the incorrect one it says "Local to Remote update not allowed. Must First Delete Instance".

If you try and delete the instance it says it is referenced by by a Network Element!

Any suggestions would be greatfully received.

Thanks

 

[Lundah]

I believe that form chooses which element is for the local record based on what IP is programmed in the IP Network tab. Try changing the values there.

 

[kwbMitel]

I've had that issue, and fixed it, but I'll be damned if I remember how.

I do remember it was quite difficult.

It may have involved Mitel support.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[bribob]

Mitelmike, did you resolve this issue?

I've just spun up a remote vMCD and foolishly imported the ICP/PBX Networking from from another system without changing the Local ICP/PBX value. Kept programming and have just realized my mistake. If you have a procedure to change the Local ICP/PBX setting, I'm very interested in it.

Unless your solution was to wipe and start fresh...

 

[AlphaMann]

Call Mitel. They have to go into the SX2000 interface I believe and muck around to get it done. And no you cannot just leave it, causes some major cluster issues.

 

[Supernova99]

Sorry to be the bearer of bad news but unfortunately it will probably involve a full rebuild.
What version MCD are you running? if 4.0 or below it is possible to rectify via the SX2000 console but once GDM SDS sync is enabled then it is not possible to edit the SX2000 console forms anymore.

Share what you know - Learn what you don't

 

[AlphaMann]

No I did this just a few months ago on an mcd 6 build. It may not have been sx 2000 but it was through a terminal session of some sort (and no not on port 2002). It took them about 20 minutes and the tech I had knew exactly what to do. Good luck!

 

[Mitelmike2010]

Sorry,appears there is no easy way out. I had to rebuild the controller with the error. Just exported all the forms I needed and started again. After doing this for 20 years it was a lesson learned the hard way.

 

[bribob]

I'm on 7 years. And yes, I also learned a lesson. Luckly with export and flag, 2 hours and the system was back up.

 

[kwbMitel]

@bribob, if by flag you mean that you turned the initialized flag to off, then be aware that does not scrub everything.

You probably had not built enough to have any issues but I would've rebuilt from the .ova.

I actually think this is what I ended up doing when I ran into this. (26 years if we're counting)

**********************************************
What's most important is that you realise ... There is no spoon.