SummaryThis KB can be referred while troubleshooting New or Existing Fiber NIC
OverviewThe Most Basic troubleshooting for any Fiber NIC is to Check which mode the Card supports.
# It is very important to verify If the card is multi-mode or single-mode and coherently the type of Fiber installed in the Network.
After Installing a new Fiber NIC or changing the Slot for a previously Existing Fiber NIC
1. Check if the interfaces that are in the bridge are up.
If they are administratively shutdown, re-enable them.
Using Br10 as an example:
#int eth10 shutdown
#no int eth10 shutdown
#int eth 11 shutdown
#no int eth 11 shutdown
2. Check if the bridge is enabled.
Go to Configuration-->System-->Network-->IP Address tab and check if there is a check mark on the bridge.
# no interface br10 shutdown.
3. The bridge is enabled and interfaces are up, but the bridge is administratively down
Do an administrative shutdown and then re-enable the interface
#int br10 shutdown
#no int br10 shutdown
After these troubleshooting steps if the Card is still not UP as shown below
Please Verify the Speed , MTU and Duplex of the NIC and the corresponding Devices.
Refer to KB 000001122
Refer to KB 000002042
After verifying the speed Make Sure to verify the Bridge's Mode
Please refer to KB 000001417
Additional Causes for A Fiber NIC not working can narrowed down by
1. Swapping the Ports on the Switch and the Router.
2. Connecting the LAN and WAN ports directly to each other using the correct mode of cable (Single/Multi)
If All the above steps Fail Please Contact Exinda Support / TAC Team
CauseOne of the Main Causes for the Fiber NIC issue can be specification mismatch.
If the Fiber NIC on the Exinda is 10 Gbps and the LAN/ WAN device is 1 Gbps,
This set up will not work. The Fiber NICs are not compatible for different speeds.
Internal NotesIf All the above step Fail.
1. Request the system diagnostic and analyse the logs for any errors messages.
2. There are a few reasons and error messages that you may see:
- Watchdog may fail to restart.
- Link may come up and down.
- Bypass may kick in and out.
3. Look at the sysinfo.txt file.
4. Scroll down to the NIC card .
5. Look for Errors, both RX and TX.
6. Look for Discards, both RX and TX.
7. See if there are any message relating to port connection lost.
8. Check the logs to see if there are any messages relating to conntrack or any tables being overwhelmed.
9. Check the PDF to see if there are a lot of new connections per second and a high max concurrent flows.
10. Verify the numbers with the benchmarks.
11. If the benchmarks are still in check, you should request the RMA and follow the RMA procedure.