I have a weird problem. I have two Unity 4.0(3) systems consisting of four servers, which are two pairs, a primary and secondary failover for each. Digital networking is setup, but even though everything seems to work fine, failover etc. One pair of servers seems to see a different view of the network and see's the other secondary as if it wasn't a failover server. Where as if viewed from the other primary, it sees everything is fine. I've re-run the failover wizard on both pairs and it still persists. Global subscriber Manager on one pair see's the secondary of the other pair as if it isn't a member of the common dialing domain.
What's probably going on is that you have an orphaned location object in the directory. You should only have two objects based on what you have explained as your configuration.
If you are using Active Directory you can check the ciscoEcsbuUMServer value using ADSIEdit to see the hostname of the server it's associated with. If you find a location object with the name of one of the secondary servers you can safely remove it. Once it is removed and the Unity servers synch with the GC you shouldn't see the object anymore in the SA.
Let me know if you are using Exchange 5.5 and I will give you the step for that.
You were spot on. I opened a case with the Brussels TAC and we ended up removing an entry in the global location table in SQL. Once we removed that, it replicated across and everything is sweet. I don't know how this happened, but you may have been right in the first place about an orphaned location in AD.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.