VMware Networking Community
LucianoPatrão
Jump to solution

NSX-T v2.4.1 corfu DB logs issues

Struggling with NSX issues. Need to fix corfu DB and the logs (it was corrupted after lack of space in /var/log),

In the a previous blog post by Niram he explain to use a command corfu_logReader display that could fix my problem, but in v2.4.1 cannot find it. Anyone knows a different command or an alternative to fix the issue?

Thank You

LP

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
1 Solution

Accepted Solutions
LucianoPatrão
Jump to solution

Problem is fixed.

Just information to future need.

After putting the cluster working with only one node Cluster, then power on second one I was able to check that the node 03 was the corrupted one and was put cluster down. Removing node 03 from the Cluster did the trick.

Thank You

LP

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT

View solution in original post

Reply
0 Kudos
5 Replies
daphnissov
Immortal
Immortal
Jump to solution

If you have a break/fix issue, this is better directed at GSS, especially for corruption issues.

Reply
0 Kudos
LucianoPatrão
Jump to solution

If I get the answer I may could fix the issue Smiley Happy

These are NFR/Trial licenses.

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
LucianoPatrão
Jump to solution

These are the commands that exists

root@nsxt-manager-2:/config/corfu/log# corfu_

corfu_add_node              corfu_layout                corfu_management_bootstrap  corfu_remove_node           corfu_server                corfu_tool_runner.py

corfu_as                    corfu_layouts               corfu_ping                  corfu_reset                 corfu_smrobject             corfu_tool_runner.sh

corfu_bootstrap_cluster     corfu_logunit               corfu_query                 corfu_sequencer             corfu_stream

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
LucianoPatrão
Jump to solution

It seems that VMware removed tool corfu_logReader from NSX Smiley Sad

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos
LucianoPatrão
Jump to solution

Problem is fixed.

Just information to future need.

After putting the cluster working with only one node Cluster, then power on second one I was able to check that the node 03 was the corrupted one and was put cluster down. Removing node 03 from the Cluster did the trick.

Thank You

LP

Luciano Patrão

VCP-DCV, VCAP-DCV Design 2023, VCP-Cloud 2023
vExpert vSAN, NSX, Cloud Provider, Veeam Vanguard
Solutions Architect - Tech Lead for VMware / Virtual Backups

________________________________
If helpful Please award points
Thank You
Blog: https://www.provirtualzone.com | Twitter: @Luciano_PT
Reply
0 Kudos