10G SFP+ DAC cable on RT-BE88U - link doesn't come up

[NonAlex]

Hello community,

I'm trying to get RT-BE88U (running Merlin SW) connected to my LAN switch over 10G SPF+ DAC cable. Switch and DAC cable vendor is the same, so I assume it's OK there, however the link does not come up.
I'm seeing this on the router, and the line in red doesn't look good. However there are no parameters in GUI to manipulate 10G SFP+ port parameters, like autoneg parameters.. Are there any known tweaks/gotchas with using DAC cables on ASUS ?

Jul 2 11:21:35 kernel: Opticaldet Unknown Transceiver
Jul 2 11:21:35 kernel: Module Form Factor: SFP/SFP+
Jul 2 11:21:35 kernel: Module Type : UNKNOWN
Jul 2 11:21:35 kernel: Vendor Name : Amphenol
Jul 2 11:21:35 kernel: Part Number : 588680003
Jul 2 11:21:35 kernel: Part REV : E
Jul 2 11:21:35 kernel: ************************************************************************
Jul 2 11:21:35 kernel: * Opticaldet: Unknown optical module - using default configuration *
Jul 2 11:21:35 kernel: * Please make sure the optical module is correct for your connection *
Jul 2 11:21:35 kernel: ************************************************************************
Jul 2 11:21:37 kernel: SFP Module is Plugged in at Serdes address 7 core 0 lane 0
Jul 2 11:21:37 kernel: --- Step 0 powerup/reset sequence of core #0 at address 7
Jul 2 11:21:37 kernel: Toggle Serdes Core #0 PMD and uC reset.
Jul 2 11:21:37 kernel: INFO MerlinSupport::merlin_core_init(): END. Core #0 with PRTAD = 7, ln_offset_stap = 0
Jul 2 11:21:37 kernel: MerlinSupport::merlin16_serdes_init(): Step 6. Micro code load and verify
Jul 2 11:21:37 kernel: MerlinSupport::merlin_load_firmware(): ret = 0
Jul 2 11:21:37 kernel: MerlinSupport::merline_speed_set_core(): Step 7 Config Speed to 2
Jul 2 11:21:37 kernel: --- Step 8 PLL/PMD setup configuration for speed 0, mode 2.
Jul 2 11:21:37 kernel: MerlinSupport::merline_speed_set_core(): PMD Setup 50MHz, 10.3125GHz VCO programming
Jul 2 11:21:37 kernel: MerlinSupport::merlin_wait_uc_active(): wait 50us comclks for micro to be up...
Jul 2 11:21:37 kernel: MerlinSupport::merlin_wait_uc_active(): Checking uc_active passed ...
Jul 2 11:21:38 kernel: MerlinSupport::merlin_wait_uc_active(): micro is ready for command ...
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): Step 9. Configure Core level regsiter
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): Step 10. Set core_congif_from_pcs
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): RAM variable vco_rate is 19
Jul 2 11:21:38 kernel: MerlinSupport::merlin_cfg_core_ram_var(): program core_config_word 0x26 to ram address 0x20000200 ...
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): Step 12. Reset Datapath (core)
Jul 2 11:21:38 kernel: MerlinSupport::merlin_reset_datapath_core(): Datapath Reset (core) in progress
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): Step 13. Lane Configuration
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): Step 13.a. Configure lane registers
Jul 2 11:21:38 kernel: MerlinSupport::merline_speed_set_core(): RAM variable an_enabled is 0
Jul 2 11:21:38 kernel: MerlinSupport::merlin_cfg_lane_ram_var(): program lane_config_word 0x4 to ram address 0x20000300 ...
Jul 2 11:21:38 kernel: MerlinSupport::merlin_lane_config_speed(#2):
Jul 2 11:21:38 kernel: MerlinSupport::CONFIGURING FOR FORCE 1G
Jul 2 11:21:38 kernel: MerlinSupport::merlin_lane_config_speed(): Core #0 Lane #0 PMD Lock Speed Up programming
Jul 2 11:21:38 kernel: INFO MerlinSupport::merlin_lane_config_speed(): END Merlin core #0 lane #0 Initialization procedure
Jul 2 11:21:38 kernel: MerlinSupport::merlin_chk_pll_lock(): Checking Core #0 PLL Lock Status
Jul 2 11:21:38 kernel: MerlinSupport::merlin_chk_pll_lock(): PLL Locked
Jul 2 11:21:38 kernel: INFO MerlinSupport::merlin16_serdes_init(): END Merlin Initialization procedure

 

[Ripshod]

You'll be surprised what's compatible and what's not. I've seen Cisco modules fail whilst cheap (Planet) modules are readily accepted. If a module is not working there's not a lot you can do other than trying something else, or going for something proven to work with the router - there's a thread somewhere.
I'm currently using 10Gtec modules for both ends into a Sodola switch with zero issues.
What is the log from the other end of the link say as the log you posted doesn't state any actual failure beyond forcing a 1Gig connection?

 

[NonAlex]

You'll be surprised what's compatible and what's not. I've seen Cisco modules fail whilst cheap (Planet) modules are readily accepted. If a module is not working there's not a lot you can do other than trying something else, or going for something proven to work with the router - there's a thread somewhere.
I'm currently using 10Gtec modules for both ends into a Sodola switch with zero issues.
What is the log from the other end of the link say as the log you posted doesn't state any actual failure beyond forcing a 1Gig connection?

On the other end - nothing. Port is admin up/ready, but link is not active
Are there any proven SFP+ DAC cables ?

 

[Ripshod]

Are there any proven SFP+ DAC cables ?

Not that I'm aware of. I keep it modular - seperate SR modules and OM3 fibre.
I can't even remember it being mentioned on here before now.

 

[Ripshod]

Compare your log with mine. Does your log go any further than what you posted or is the port not being configured for the network?
Edit - (note that I also get the force 1g notice. It's a normal part of the initiallzation before the actual link is negotiated)

Jul  4 12:31:06 ripshod kernel: brcm_sfp sfp1: module inserted
Jul  4 12:31:06 ripshod kernel: brcm_sfp sfp1: module OEM              SFP-10G-SR       rev 02   sn CS106NC5630      dc 231227
Jul  4 12:31:06 ripshod kernel: Opticaldet Unknown Transceiver
Jul  4 12:31:06 ripshod kernel: Module Form Factor: SFP/SFP+
Jul  4 12:31:06 ripshod kernel: Module Type       : UNKNOWN
Jul  4 12:31:06 ripshod kernel: Vendor Name       : OEM          
Jul  4 12:31:06 ripshod kernel: Part Number       : SFP-10G-SR  
Jul  4 12:31:06 ripshod kernel: Part REV          : 02
Jul  4 12:31:06 ripshod kernel: ***********************************************************************
Jul  4 12:31:06 ripshod kernel:  Opticaldet: Unknown optical module - using default configuration     *
Jul  4 12:31:06 ripshod kernel:  Please make sure the optical module is correct for your connection   *
Jul  4 12:31:06 ripshod kernel: ***********************************************************************
Jul  4 12:31:07 ripshod kernel: Fiber SFP Module is Plugged in at Serdes address 7 core 0 lane 0
Jul  4 12:31:07 ripshod kernel: --- Step 0 powerup/reset sequence of core #0 at address 7
Jul  4 12:31:07 ripshod kernel: Toggle Serdes Core #0 PMD and uC reset.
Jul  4 12:31:07 ripshod kernel: INFO MerlinSupport::merlin_core_init(): END. Core #0 with PRTAD = 7, ln_offset_stap = 0
Jul  4 12:31:07 ripshod kernel: MerlinSupport::merlin16_serdes_init(): Step 6. Micro code load and verify
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_load_firmware(): ret = 0
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 7 Config Speed to 2
Jul  4 12:31:08 ripshod kernel: --- Step 8 PLL/PMD setup configuration for speed 0, mode 2.
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): PMD Setup 50MHz, 10.3125GHz VCO programming
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_wait_uc_active():    wait 50us comclks for micro to be up...
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_wait_uc_active():  Checking uc_active passed ...
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_wait_uc_active():  micro is ready for command ...
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 9. Configure Core level regsiter
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 10. Set core_congif_from_pcs
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): RAM variable vco_rate is 19
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_cfg_core_ram_var():  program core_config_word 0x26 to ram address 0x20000200 ...
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 12. Reset Datapath (core)
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_reset_datapath_core(): Datapath Reset (core) in progress
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 13. Lane Configuration
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): Step 13.a. Configure lane registers
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merline_speed_set_core(): RAM variable an_enabled is 0
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_cfg_lane_ram_var():  program lane_config_word 0x4 to ram address 0x20000300 ...
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_lane_config_speed(#2):
Jul  4 12:31:08 ripshod kernel: MerlinSupport::CONFIGURING FOR FORCE 1G
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_lane_config_speed(): Core #0 Lane #0 PMD Lock Speed Up programming
Jul  4 12:31:08 ripshod kernel: INFO MerlinSupport::merlin_lane_config_speed(): END Merlin core #0 lane #0 Initialization procedure
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_chk_pll_lock(): Checking Core #0 PLL Lock Status
Jul  4 12:31:08 ripshod kernel: MerlinSupport::merlin_chk_pll_lock(): PLL Locked
Jul  4 12:31:08 ripshod kernel: INFO MerlinSupport::merlin16_serdes_init(): END Merlin Initialization procedure
Jul  4 12:31:09 ripshod BWDPI: fun bitmap = 3
Jul  4 12:31:11 ripshod kernel: eth9 (Int switch port: 6) (Logical Port: 6) (phyId: 7) Link Up at 10000 mbps full duplex AN: Off
Jul  4 12:31:11 ripshod kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth9: link becomes ready
Jul  4 12:31:11 ripshod kernel: br0: port 9(eth9) entered blocking state
Jul  4 12:31:11 ripshod kernel: br0: port 9(eth9) entered listening state
Jul  4 12:31:11 ripshod kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth9.52: link becomes ready
Jul  4 12:31:11 ripshod kernel: br54: port 12(eth9.52) entered blocking state
Jul  4 12:31:11 ripshod kernel: br54: port 12(eth9.52) entered listening state
Jul  4 12:31:11 ripshod kernel: dev eth9.52 is sdn_ignore
Jul  4 12:31:13 ripshod kernel: br0: port 9(eth9) entered learning state
Jul  4 12:31:15 ripshod kernel: br0: port 9(eth9) entered forwarding state
Jul  4 12:31:15 ripshod kernel: br0: topology change detected, propagating
Jul  4 12:31:26 ripshod kernel: br54: port 12(eth9.52) entered learning state
Jul  4 12:31:42 ripshod kernel: br54: port 12(eth9.52) entered forwarding state
Jul  4 12:31:42 ripshod kernel: br54: topology change detected, propagating

ie - does your log not contain any network cofiguration info after "kernel: INFO MerlinSupport::merlin16_serdes_init(): END Merlin Initialization procedure"?