Link Power
One of the first things to check when bringing up a link on fiber is to check the link power levels. This is how much power the transceivers are using
Use the following fmadiocli command
fmadiocli show interface statusExample output is shown below shows a 100G SR4 link on cap0, and cap1 disconnected
fmadio@ny2-fmadio200v4-prod0:~$ fmadiocli show interface status
[Fri Nov 6 22:34:05 2026] Cmd [show interface status ]
[Fri Nov 6 22:34:05 2026] Port Description Status Speed Transceiver RxPower TxPower Temperature FEC Vendor Vendor PN
[Fri Nov 6 22:34:05 2026] -----------------------------------------------------------------------------------------------------------------------------------------------------------
[Fri Nov 6 22:34:06 2026] cap0 connected 100G 100G-SR4 VCSEL 8.154 mW 3.496 mA 45.452 C auto-on FS QSFP28-SR4-100G
[Fri Nov 6 22:34:06 2026] cap1 notconnected 100G 100G CR 0.000 mW 0.000 mA 0.000 C auto-off FS QSFP-100G-PC02
fmadio@ny2-fmadio200v4-prod0:~$Alternatively direct CLI interaction using
cat /opt/fmadio/status/qsfp0_link_powercat /opt/fmadio/status/qsfp1_link_powerExample output shown below
fmadio@ny2-fmadio200v4-prod0:~$ cat /opt/fmadio/status/qsfp0_link_power
RxPower0: 8.154 mW
RxPower1: 8.912 mW
RxPower2: 8.365 mW
RxPower3: 9.417 mW
TxPower0: 3.496 mA
TxPower1: 3.493 mA
TxPower2: 3.505 mA
TxPower3: 3.496 mALink Bounce
FW: 8224+
Getting 100G links link up either works no problem out of the box or be fickle to setup and get a link.
Usually the main source of problems is FEC vs non-FEC setting on both the switch and on the FMADIO system. FMADIO Packet Capture systems will try detect if FEC is on the link by alternating FEC enable / FEC disabled when trying to link up.
This can cause problems if the switch its connected to is also cycling thru the different combinations.
To check the current status the fmadiocli utility provides the easiest way to monitor the state. Use the command, below to get the current link state.
show interface status.png?sv=2026-02-06&spr=https&st=2026-11-13T18%3A22%3A16Z&se=2026-11-13T18%3A35%3A16Z&sr=c&sp=r&sig=V%2FeYrquUN5Dd3c2moKPTcQhyiJTDNyOeCgU%2BCXoFetA%3D)
In the above we see capture port 0 (cap0) is link down and capture port 1(cap1) is link up
The link may be bounced by shutting down using the command as follows
config interface shutdown cap0
config interface shutdown cap1It may take 1min for the link to go down, use the show interface status command to wait for link down to complete.
.png?sv=2026-02-06&spr=https&st=2026-11-13T18%3A22%3A16Z&se=2026-11-13T18%3A35%3A16Z&sr=c&sp=r&sig=V%2FeYrquUN5Dd3c2moKPTcQhyiJTDNyOeCgU%2BCXoFetA%3D)
Once the link is down, disable the shutdown using the command
config interface no shutdown cap0
config interface no shutdown cap1NOTE: status currently takes 30-60sec to update. Please be patient.
FEC Link Config
he default setting of FMADIO Packet Capture system is FEC running in "auto" mode. This means the system will try link up without FEC, if it fails FEC is enabled and link up is tried again. This process is repeated indefinitely.
For some switchs and NICs this works for others it has problems. e.g. if both end points are cycling like this its possible it will ever link up due to phase/offset of the cycles.
Its best to force the FEC setting if your expecting FEC to run on the link. This is done as follows
config interface fec cap0
config interface fec cap1.png?sv=2026-02-06&spr=https&st=2026-11-13T18%3A22%3A16Z&se=2026-11-13T18%3A35%3A16Z&sr=c&sp=r&sig=V%2FeYrquUN5Dd3c2moKPTcQhyiJTDNyOeCgU%2BCXoFetA%3D)
After forcing FEC on the links the interface status will show a "force-" option as follows
.png?sv=2026-02-06&spr=https&st=2026-11-13T18%3A22%3A16Z&se=2026-11-13T18%3A35%3A16Z&sr=c&sp=r&sig=V%2FeYrquUN5Dd3c2moKPTcQhyiJTDNyOeCgU%2BCXoFetA%3D)
This indicates FEC has been forced on for the specific interfaces.
NOTE: bouncing the port on the switch may be required, it depends what state the switch port is. It may have entered an error mode, or backed off on the autoneg. Bouncing the port on the switch most of the time will resolve the issue.
Additional Link Up Debug
If the link is still failing to link up, you can trace the state machine for link up procedure using the command
fnic_test --trans-trace -vBy default it runs on cap0 using the --port 1 can run the trace on the other port. This prints out the realtime event history of the link up process, below is an example of a link bounce.
.png?sv=2026-02-06&spr=https&st=2026-11-13T18%3A22%3A16Z&se=2026-11-13T18%3A35%3A16Z&sr=c&sp=r&sig=V%2FeYrquUN5Dd3c2moKPTcQhyiJTDNyOeCgU%2BCXoFetA%3D)
In the above output we see the link state go from State 1 -> State 7. Where state 7 is a stable link up.
For additional assistance on link problems, please run the above and pipe to a logfile. Send the logfile to support @ fmad . io for further assistance.