3300 MCD certificate errors

[Billz66]

3300 MCD 10.2.0.26_2
- was having big problems with anything sip on our controller.
- I used a dummy system to keep our office going whilst I did a manual reload.

- Originally our controller was 172.16.10.2 so I used this on loan controller.

- Whilst reloading our controller I used a different IP address and when ready , took it off the network , changed its ip address to be 172.16.10.2 and swapped them.
- Sip is now working again .

- The problem i am having is that intermittantly , IE is throwing up certificate errors and the certificate seems to be showing the temporary address.
- it appears that the controller seems to have 2 certificates , each with a different IP address .

I dont want to go through the whole reload drama again.
is there any certificate management commands that I can use to check whats going on?

 

[Supernova99]

The important thing here is to keep the IP addresses the same.
Build the new controller off net with the same IP address. remove the old controller then connect the temp controller.
As you will be using the same database to restore it should also restore the same certificate.

Share what you know - Learn what you don't

 

[kwbMitel]

If you upload a DB that was created with 1 IP to another box with a different IP you have a good change of corrupting your DB. Especially if ACD applications are enabled/configured.

Additionally, unless the boxes are compatible hardware types you could be creating unrecoverable errors associated with modules and optional hardware.

Learn from my mistakes.

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

 

[Billz66]

I didnt restore a database this time .
I had exported the forms manually and then reimported
- any references to GUID were removed before importing.

No forms containing any ip address data were imported ,

Its this part in the startup that concerns me

adding names to certificate
added CN = mitel networks icp web server
added CN = test68:8080
added CN = 10.100.10.67:8080
added CN = 172.16.10.2:8080

Those are the 2 ip addresses that have appeared in the certificate.

 

[sarond]

I did something similar, from memory I think a backup then restore and reboot fixed it.

 

[Billz66]

I managed to get another outage window System reset seems to have fixed it . Thanks for the suggestions.