Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hyperflex Connect received the following alarm.
[HXA-NOD-0008]I searched the document for this content, but I didn't get matching results.
Can I ask for advice?There is no problem with the current service.
Installing Linux KVMs on Hyperflex hardware.FI 6332 is connected to the VIC card through QSFP-40G-SR-BD.On the server port of the FI, it looks like 40G, but on the Linux interface it looks like 10G.Why is that?
I am currently using only one FI as a single. Three chassis are connected, of which only one has four cables. Chassis No. 2 and No. 3 have two cables.It also uses external SAN storage over a FI-SAN switch-to-storage connection.ESXi on the server in c...
When upgrading from HX 3.0 to 3.5, the board firmware on the node was not upgraded in the middle, so the board firmware was manually upgraded. Next comes the phrase below. I need your help.
Checking ESX Host Version on Cluster Nodes with NVMe Disks...
I analyzed the log by doing TAC CASE OPEN, but TAC's opinion speculated that OS driver was an issue.However, the customer has no problem with the service and the alarm continues to occur, but they do not want to install the driver for uncertain reaso...
Problem solved. Once it appeared to be 10G, the link was down and down because the uplink interface was down in the FI. Regardless of the presence or absence of communication, if the FI's uplink is not activated, it is not pinning, so the phrase ENM ...
I checked the Linux configuration and tried to change it manually, but it didn't apply 40G.For further verification, I changed the OS to VMware and installed it, but this time the Vic link is down and cannot be verified.
