I'm hoping this is now resolved by removing all the databases and removing/adding the server back to the DAG. I didn't need to re-seed - all databases are showing as Healthy again, after a period of re-syncing the changes. I guess this was because the EDB and all log files were intact, and Exchange was nice and clever.
I'd still like to know how I could have removed the rogue IP address from the cluster network. Thanks, Richard From: [email protected] [mailto:[email protected]] On Behalf Of Sobey, Richard A Sent: 09 September 2013 15:48 To: [email protected] Subject: [Exchange] RE: Heeelp - Exchange server networking in DAG Thanks MBS, but can you elaborate on that? What do I remove and from where in EMC? From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: 09 September 2013 15:38 To: [email protected] Subject: [Exchange] RE: Heeelp - Exchange server networking in DAG Remove all IP addresses. Add them back. Use EMC, not FCM. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sobey, Richard A Sent: Monday, September 9, 2013 10:28 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Heeelp - Exchange server networking in DAG All, Need some help, gah. I'm going through a patching cycle of SP3+RU2 and, as well as that, upgrading the NIC drivers amongst some other firmware on the hardware. On the first mailbox server I've done, after following HP advice, I've dissolved the NIC team, run the software upgrades, then put the team back together. I don't think the NIC team used the same name, although that's now been corrected. Unfortunately this server is no longer part of its DAG, that is, it is a DAG member but not operational. It seems to be very confused about the network. In the EMC, it has an IPv6 address listed as DOWN, where all the other servers have an IPv4 address listed as UP. In Failover Cluster Manager, the server is DOWN. The cluster service is also crashing repeatedly. I appreciate this is very sparse information, but is there anything I can do to reset the DAG network info on this server without resorting to ripping out all its databases and starting again? The databases it does have all list as Healthy copies. Any other specific information available on request. Thanks, Richard
