Flings

 View Only
  • 1.  after power outage in data center I canot start any vCLS VM.

    Posted 18 days ago

    how can I fix this issue to bring my cluster in healty state. I have tried retreat mode , tried regenerate certificate. but I still cannot bring vCLS created  in cluster, I have checked vpx log file and found these entry. see below

    2024-08-22 13:09:12.199 UTC 66c728f5.19b4 72847242 VCDB vc [local] 6580 12 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:09:42.188 UTC 66c728f5.19b4 72847262 VCDB vc [local] 6580 15 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:10:12.191 UTC 66c728f5.19b2 72847283 VCDB vc [local] 6578 117 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:10:42.194 UTC 66c728f5.19b2 72847303 VCDB vc [local] 6578 120 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:11:12.185 UTC 66c728f5.19b4 72847331 VCDB vc [local] 6580 18 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:11:42.192 UTC 66c728f5.19b2 72847357 VCDB vc [local] 6578 123 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"
    2024-08-22 13:12:12.190 UTC 66c728f5.19b4 72847382 VCDB vc [local] 6580 21 ERROR:  duplicate key value violates unique constraint "pk_vpx_auth_tenant_mgmt_rs"

    and 

    2024-08-22 13:35:25.104 UTC 66c73e43.ab08 72873920 VCDB vc [local] 43784 4 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:35:31.852 UTC 66c73e43.ab0b 72873946 VCDB vc [local] 43787 4 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:36:01.843 UTC 66c73e43.ab08 72874766 VCDB vc [local] 43784 7 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:36:31.875 UTC 66c73e43.ab08 72882765 VCDB vc [local] 43784 10 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:37:01.816 UTC 66c73e43.ab08 72882814 VCDB vc [local] 43784 13 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:37:31.829 UTC 66c73e43.ab08 72882854 VCDB vc [local] 43784 16 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:38:01.832 UTC 66c73e43.ab08 72891068 VCDB vc [local] 43784 19 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:38:31.817 UTC 66c73e43.ab08 72891112 VCDB vc [local] 43784 22 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:39:01.814 UTC 66c73e43.ab08 72894813 VCDB vc [local] 43784 25 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:39:31.815 UTC 66c73e43.ab0b 72894846 VCDB vc [local] 43787 7 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:40:01.819 UTC 66c73e43.ab0b 72894904 VCDB vc [local] 43787 10 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:40:31.827 UTC 66c73e43.ab08 72894943 VCDB vc [local] 43784 28 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:41:01.815 UTC 66c73e43.ab08 72894955 VCDB vc [local] 43784 31 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:41:31.827 UTC 66c73e43.ab08 72894997 VCDB vc [local] 43784 34 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:42:01.812 UTC 66c73e43.ab0b 72895015 VCDB vc [local] 43787 13 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:42:31.804 UTC 66c73e43.ab0b 72895052 VCDB vc [local] 43787 16 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:43:01.826 UTC 66c73e43.ab0b 72895100 VCDB vc [local] 43787 19 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:43:31.814 UTC 66c73e43.ab08 72895117 VCDB vc [local] 43784 37 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:44:01.809 UTC 66c73e43.ab08 72895147 VCDB vc [local] 43784 40 DETAIL:  Key (entity_id)=(141482) already exists.
    2024-08-22 13:44:31.818 UTC 66c73e43.ab0b 72895181 VCDB vc [local] 43787 22 DETAIL:  Key (entity_id)=(141482) already exists.



  • 2.  RE: after power outage in data center I canot start any vCLS VM.

    Posted 18 days ago

    Have you tried putting your clusters in retreat mode, giving it 10 minutes, then re-enable them?  8U2 I believe, this is a check box in the GUI.  Before that, you had to set an advanced parameter for vCenter for each cluster.

    https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-F98C3C93-875D-4570-852B-37A38878CE0F.html



    ------------------------------
    -FrostByteVA
    ------------------------------



  • 3.  RE: after power outage in data center I canot start any vCLS VM.

    Posted 18 days ago

    I have followed al this KB but I still have no luck.

    https://knowledge.broadcom.com/external/article/340947/vcenter-server-does-not-automatically-p.html

    https://knowledge.broadcom.com/external/article/318806/vcenter-server-65-crashes-with-error-dup.html

    https://knowledge.broadcom.com/external/article/326304/vcls-vms-are-not-recreated-in-a-vsan-clu.html

    and retreat mode article too.