Reset CoreID of Management Server - OMU v8

Lets jump a few step ahead. I wanted to share something that I learnt today.
Suppose the CoreID of the management server got reset or deleted by some reason, we would need to reset it to the value that was there previously.

To get the previous CoreID, we can run the following command either on the management server or on the management node. 
On the management server :


[root@management_server:/root]
# ovcert -list
+---------------------------------------------------------+
| Keystore Content                                        |
+---------------------------------------------------------+
| Certificates:                                           |
|     0e86<******>5 (*)                                   |
|     9109<******>d (*)                                   |
+---------------------------------------------------------+
| Trusted Certificates:                                   |
|     CA_0e86<******>5                                    |
|     CA_543b<******>a                                    |
|     CA_7ac7<******>5                                    |
|     CA_d385<******>e                                    |
+---------------------------------------------------------+

+---------------------------------------------------------+
| Keystore Content (OVRG: server)                         |
+---------------------------------------------------------+
| Certificates:                                           |
|     0e86<******>5 (*)                                   |
+---------------------------------------------------------+
| Trusted Certificates:                                   |
|     CA_0e86<******>5 (*)                                |
|     CA_543b<******>a                                    |
|     CA_7ac7<******>5                                    |
|     CA_d385<******>e                                    |
+---------------------------------------------------------+

On the Managed node 


[root@managed_node:/root]
# ovcert -list
+---------------------------------------------------------+
| Keystore Content                                        |
+---------------------------------------------------------+
| Certificates:                                           |
|     beb5<******>1 (*)                                   |
+---------------------------------------------------------+
| Trusted Certificates:                                   |
|     CA_0e86<******>5                                    |
|     CA_543b<******>a                                    |
|     CA_7ac7<******>5                                    |
|     CA_d385<******>e                                    |
+---------------------------------------------------------+

Usually, if there is one management server in the environment, there would be only certificate listed under the  'Trusted Certificates' list. 
Note : On the management server, under 'Trusted Certificates' the certificate listed with (*) at the end is the CoreID of that particular server.
Similarly on the managed node, the certificate marked with (*) is the CoreID of that particular managed node.

Since I have got multiple management server in my environment, there are a whole lot listed here.

So, lets proceed with the output from the managed node.
"0e86<******>5" is the CoreId of this managed node's primary management server.

To reset your management server's CoreID, go to the management server and

[root@management_server:/root]

#ovcoreid -set < Certificate ID > -force


[root@management_server:/root]

#ovcoreid -set 0e86<******>5 -force

Another Procedure would be to use the config file to set the CoreID.

[root@management_server:/root]

#ovconfchg -ns sec.core -set CORE_ID 0e86<******>5