Hardware troubleshooting guides for VMware SD-WAN
Article ID: 333909
Updated On:
Products
Issue/Introduction
Environment
VMware SD-WAN by VeloCloud
Resolution
In the event an Edge needs to be returned to VMware for further investigation, VMware support may request additional information about the issue. The information required may vary from one issue to another, therefore each article will include a list of questions that should be answered prior to opening a support case.
Common Issues:
1. Edge is powered off and cannot be powered on.
2. Edge either stuck booting up, or will not come online.
3. Dead Ethernet Port--no link LED illuminated.
4. Not able to factory reset a the SD-WAN Edge
To verify the reset was completed, follow these steps:
- Connect a client device locally through Wi-Fi or a LAN port
- Open up a web browser and navigate to 192.168.2.1
- In the web portal, confirm if the edge is unactivated and using an older factory image.
5. Fan noise on an Edge 540.
- The sound of the fan of an Edge 540 may resemble that of a failing fan with bad bearings. This is actually the expected sound for this fan when operating at low RPM and not an indication of a defect or imminent fan failure.
- Here is a short clip with the expected sound of an Edge 540 fan operating at low RPM post-boot up. Compare this to the sound on the Edge 540 in the field:
6. VMware SD-WAN Edge clock is not retaining the correct time.
- This is an indication that the SD-WAN Edge's coin cell battery has died. This battery keeps the Real Time Clock alive during power off conditions. The time could be set manually, or if NTP is working this will also set it, but at the next power off the clock will reset again.
- The battery is not field replaceable and the VMware SD-WAN Edge would need to be replaced.
7. SFP Interface is not coming up
8. Disk hardware issues
- You can identify disk hardware issues in SD-WAN edges by checking the logs and console messages errors:
Console errors:
[507316.780223] EXT4-fs: 303954 callbacks suppressed[507316.780225] EXT4-fs (sda5): previous I/O error to superblock detected[507316.791489] EXT4-fs (sda5): I/O error while writing superblock[507316.791490] EXT4-fs (sda5): I/O error while writing superblock[507316.791500] EXT4-fs (sda5): I/O error while writing superblock[507316.791543] EXT4-fs (sda5): previous I/O error to superblock detected[507316.791549] EXT4-fs (sda5): I/O error while writing superblock[507316.791604] EXT4-fs (sda5): I/O error while writing superblock[507316.791622] EXT4-fs (sda5): I/O error while writing superblock[507316.791641] EXT4-fs (sda5): I/O error while writing superblock[507316.791655] EXT4-fs (sda5): I/O error while writing superblock[507317.297948] EXT4-fs error (device sda7): __ext4_find_entry:1585: inode #2: comm vc_procmon: reading directory lblock 0[507317.308783] EXT4-fs (sda7): I/O error while writing superblock[507320.962202] scsi_io_completion_action: 1127010 callbacks suppressed[507320.999251] print_req_error: 1423784 callbacks suppressed[507320.999253] blk_update_request: I/O error, dev sda, sector 4242688 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0[507320.999263] blk_update_request: I/O error, dev sda, sector 4274888 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0[507320.999286] blk_update_request: I/O error, dev sda, sector 4242432 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 0[507320.999290] blk_update_request: I/O error, dev sda, sector 4242680 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
VCO events errors:
Look for: "EDGE_DISK_IO_ERROR" or "Remounting filesystem read-only":
Additional Information
Guide to the Front LED Status Light of a VMware SD-WAN Edge
Feedback
