Peripherals

Peripherals

Summary

This article describes supported add-on peripherals for RouterBOARD hardware devices. MikroTik routers support a wide range of peripherals that extend their functionality beyond basic routing, including cellular modems for mobile connectivity, SFP and SFP+ transceivers for fiber and copper connections, and storage drives for RouterOS Disk Storage (RDS) systems. Understanding peripheral compatibility and configuration requirements ensures successful integration of these components into your MikroTik deployment.

Cellular modems enable primary or backup internet connectivity through mobile networks, supporting 4G LTE and 5G technologies depending on the modem model and RouterOS version. SFP modules provide gigabit fiber or copper connectivity for devices lacking native ports or requiring specific connection types, with native MikroTik modules supported automatically and third-party modules validated for compatibility. SFP+ modules extend this capability to 10 gigabit speeds for high-throughput deployments. U.2 solid-state drives expand storage capacity for devices supporting RouterOS Disk Storage, enabling additional logging, Dude server data, or container storage.

Not all peripherals are listed in official compatibility tables, as modem manufacturers frequently reuse hardware identifiers and third-party modules may work despite not being explicitly tested. Localized, locked, or customized units may experience compatibility issues even when their hardware identifiers match supported devices. When integrating peripherals, verify RouterOS version requirements, review manufacturer-specific notes, and test thoroughly before production deployment.

Cellular Modems

Overview

RouterOS v7 supports cellular modems in several categories: MikroTik’s own modems, third-party modems using standard device class interfaces, and additional modems listed in the compatibility table with specific vendor and device identifiers. Understanding these categories helps in selecting and configuring appropriate hardware for your deployment.

Modems using standard interfaces connect through USB and present themselves as familiar device classes that RouterOS handles uniformly. The MBIM (Mobile Broadband Interface Model) class provides modern, well-supported modem communication with extensive feature access. The USB-CDC (Communication Device Class) presents modems as serial devices with AT command interfaces. The RNDIS (Remote Network Driver Interface Specification) type presents the modem as a network interface without requiring PPP configuration. Modems in these categories often work automatically or with minimal configuration once connected.

MikroTik devices with built-in LTE modems, such as the SXT LTE, provide integrated cellular connectivity without requiring additional hardware. These integrated solutions are tested and supported as complete systems rather than as separate components.

Supported Modem Classes

Cellular modems connecting via USB present standardized interfaces that RouterOS recognizes and manages automatically. Understanding these interface types helps diagnose connectivity issues and select appropriate modems for your deployment.

MBIM (Mobile Broadband Interface Model) represents the modern standard for cellular modem communication. Modems presenting an MBIM interface receive comprehensive support in RouterOS v7, including data channel configuration, signal monitoring, and SMS functionality. Many newer modems from manufacturers like Quectel, Sierra Wireless, and Dell ship with MBIM support or can be configured to expose this interface. MBIM modems typically appear as LTE interfaces requiring no additional configuration beyond specifying the APN provided by your mobile carrier.

USB-CDC (Communication Device Class) presents the modem as a traditional serial device accessed through AT commands. These modems establish connectivity through PPP (Point-to-Point Protocol), creating a ppp interface in RouterOS. While CDC modems require additional configuration compared to MBIM devices, they offer broad compatibility with legacy hardware. Configuration involves setting the correct data and info channels, dial command, and optionally modem initialization strings.

RNDIS (Remote Network Driver Interface Specification) presents the modem as an Ethernet device, allowing direct IP connectivity without PPP encapsulation. RNDIS modems in RouterOS v7 may require specific firmware versions to function correctly, and some hardware presents different interfaces depending on firmware configuration. RouterOS v6 does not support RNDIS modems, requiring users of that version to select alternative interface types.

Configuration Methods

Cellular modem configuration in RouterOS varies based on the interface type presented by the modem and the RouterOS version in use. Two primary configuration approaches exist: config-less LTE interfaces that require minimal setup, and traditional PPP or AT-based configurations requiring specific parameters.

Config-less LTE interfaces represent the simplest configuration method, automatically handling modem initialization and network connection without manual parameter specification. These interfaces work with modems presenting standard MBIM or RNDIS interfaces and identified as config-less compatible in the modem table. To configure a config-less LTE interface:

/interface lte apn
add apn=internet

/interface lte
add apn-profiles=default name=lte1

The router automatically detects modem capabilities and configures appropriate parameters. This method works for most modern modems and is the recommended approach when supported.

PPP interfaces require manual specification of communication parameters including data channel, info channel, and dial command. These parameters identify how RouterOS communicates with the modem’s AT command interface and establishes the data connection:

/interface ppp-client
add dial-command="ATD*99#" info-channel=2 data-channel=1 \
    port=usb1 name=ppp-out

Modem-specific initialization commands may be required for some hardware to operate correctly. The at-chat feature sends AT commands to the modem during initialization:

/interface lte at-chat [find] input="AT+QSIMDET=0,1"

Initialization strings disable features that interfere with RouterOS operation or configure modem-specific behaviors required for reliable connectivity.

MikroTik Modems

MikroTik produces several cellular modem options designed for seamless integration with RouterBOARD devices. These modems receive native support with automatic recognition and require no special configuration beyond standard LTE interface setup.

The R11e-LTE provides LTE connectivity for mini-PCIe slots, supporting multiple APN passthrough for complex mobile connectivity requirements. The R11e-LTE6 offers enhanced LTE capabilities with improved performance and broader band support. The R11e-4G provides LTE connectivity with vendor ID 0x2cd2 and device ID 0x0003, requiring RouterOS v6.42 or higher. These MikroTik modems are tested and supported as complete systems, with RouterOS handling all configuration automatically.

MikroTik modems appear in the /interface lte menu once installed and detected, with the router automatically creating the appropriate interface type based on modem capabilities. The status monitoring commands provide signal strength, network registration, and connection state information for troubleshooting.

Third-Party Modems

Numerous third-party cellular modems work with RouterOS, though compatibility varies by modem model, firmware version, and RouterOS version. The following table summarizes tested modems with their identifiers and configuration requirements:

Model	Vendor ID	Device ID	RouterOS Version	Interface	Notes
Quectel EG25-G	0x2c7c	0x0125	6.48.3+	MiniPCI-e	CDC-ECM in v6, MBIM in v7
Quectel EC25-EU	0x2c7c	0x0125	6.42+	MiniPCI-e	PPP/LTE interface
Quectel BG96	-	-	6.45+	mini-PCIe	Serial/PPP, 2x AT channels
Quectel EM12-G	0x2c7c	0x0512	7.1beta5+	m.2	MBIM driver
Quectel RM500Q-GL	0x2c7c	0x0800	7.1beta6+	m.2	MBIM driver
Quectel RM510Q-GL	0x2c7c	0x0800	7.9+	m.2	MBIM driver
Sierra Wireless MC7455	-	-	7.3beta37+	mini-PCIe	MBIM with USB compositions
Dell DW5821e	-	-	7.4beta4+	M.2	MBIM driver
Dell DW5821e-eSIM	0x413c	0x81e0	7.11+	M.2	MBIM, at-chat support
Fibocom FM150-AE	0x2cb7	0x0111	7.1beta5+	M.2	MBIM driver
Huawei E3372h	0x12d1	0x14db	6.8+	USB	Config-less LTE interface
Huawei K5160	-	-	6.37+/7.0beta6+	USB	Config-less LTE interface

Many additional modems appear in the full compatibility table, though not all possible modems are listed. Manufacturers frequently reuse hardware identifiers across product lines, meaning untested modems may function correctly if they share identifiers with supported models. Conversely, localized, locked, or customized units may fail despite appearing in compatibility tables.

USB Pin Isolation Requirements

Some modems with USB 3.0 support experience initialization issues when installed in slots providing USB 2.0 connectivity. The USB 3.0 data pins (SSRX and SSTX pairs) can generate interference that prevents correct modem initialization during router boot. Modems experiencing this issue require physical isolation of the USB 3.0 pins using non-conductive tape (Kapton tape is commonly used).

The pins requiring isolation vary by mini-PCIe slot keying but typically include pins 23, 25, 27, 29, 31, and 33 depending on the slot type. Visual inspection of the modem board reveals which pins connect to USB 3.0 circuitry. Applying tape to these pins before installation prevents the interference while allowing USB 2.0 communication required for modem operation.

This requirement primarily affects mini-PCIe modems with USB 3.0 capability installed in older RouterBOARD models with USB 2.0-only mini-PCIe slots. M.2 modems typically use different pin configurations and are less commonly affected.

Troubleshooting Cellular Connectivity

Cellular modem connectivity issues stem from several categories: physical installation problems, firmware or configuration issues, and network-related problems. Systematic troubleshooting identifies the root cause and guides remediation.

Verify physical installation by confirming the modem is fully seated in its slot and any necessary antennas are connected. Loose connections prevent communication with the modem hardware. Check that antennas use the correct connectors (main vs. diversity) and that antenna placement provides adequate signal strength. Weak signal often indicates antenna issues rather than modem problems.

Examine modem detection using RouterOS commands:

/interface lte info [find] verbose
/system resource usb print

Detected modems appear in these outputs with their identification information. If the modem does not appear, the hardware may be defective, incorrectly installed, or require firmware updates.

Test signal strength and network registration:

/interface lte monitor [find]

The output shows received signal strength indicator (RSSI), network registration status, and connection state. Weak signal (RSSI below -100 dBm) suggests antenna or cellular coverage issues. “No service” or “Not registered” indicates network access problems requiring carrier configuration review.

Confirm APN configuration matches carrier requirements. Incorrect APN settings prevent data connection establishment even when the modem successfully registers with the network. Contact your mobile carrier to verify the correct APN for your service plan.

SFP Modules

Overview

Small Form-factor Pluggable (SFP) modules provide gigabit connectivity through fiber optic cable or copper connections, enabling flexible network topology design and long-distance connections beyond Ethernet’s 100-meter limit. MikroTik devices with SFP cages support standard SFP modules, while SFP+ cages support both SFP and SFP+ modules at appropriate speeds.

MikroTik produces its own SFP modules optimized for RouterOS compatibility, designated by the “S-” prefix (S-85DLC05D, S-31DLC20D, etc.). These native modules are automatically recognized and fully supported without configuration. Third-party modules from manufacturers like Cisco, Finisar, TP-Link, and others have been tested for compatibility and work with RouterOS, though functionality should be verified before production deployment.

SFP modules support various fiber types and connection standards. Single-mode fiber (SMF) supports long-distance connections up to tens of kilometers, while multimode fiber (MMF) serves shorter runs within buildings or campuses. BiDi (bidirectional) modules use different wavelengths for transmit and receive on a single fiber strand, effectively doubling fiber capacity. RJ45 SFP modules provide copper connectivity for devices lacking native Ethernet ports.

Module Types and Specifications

Understanding SFP module specifications ensures proper selection for your network requirements. Key specifications include data rate, connector type, fiber wavelength, and maximum distance.

Data rate specifies the maximum transmission speed, typically 1.25 Gbps for standard SFP modules. SFP+ modules support 10 Gbps while maintaining backward compatibility with SFP modules at lower speeds.

Connector type determines physical connection and cable requirements. Dual LC connectors use matched pairs for transmit and receive on separate fiber strands. SC connectors appear in some BiDi applications. RJ45 connectors accept standard Ethernet copper cables (Cat5e or better for gigabit speeds).

Wavelength specifies the light frequency used for transmission, determining compatibility with fiber types and maximum distance. Common wavelengths include 850nm for multimode fiber (short-reach), 1310nm for single-mode fiber (long-reach), and various BiDi wavelengths using paired Tx/Rx frequencies.

Maximum distance depends on fiber quality, module specifications, and network topology. Multimode modules typically reach 550 meters to 2 kilometers, while single-mode modules extend from 10 kilometers to 100+ kilometers depending on optical power and receiver sensitivity.

MikroTik SFP Modules

MikroTik’s native SFP modules receive automatic recognition and full support in RouterOS. These modules are tested for compatibility and work immediately upon installation:

Model	Rate	Connector	Fiber Type	Wavelength	Distance
S-85DLC05D	1.25G	Dual LC	MM	850nm	550m
S-31DLC20D	1.25G	Dual LC	SM	1310nm	20km
S-35LC20D	1.25G	BiDi LC	SM	Tx:1310nm/Rx:1550nm	20km
S-53LC20D	1.25G	BiDi LC	SM	Tx:1550nm/Rx:1310nm	20km
S-RJ01	1000M	RJ45	Copper	N/A	100m

Native modules require no configuration and appear immediately in /interface print upon installation. The router reads module EEPROM data and configures appropriate transmit/receive parameters automatically.

Third-Party SFP Compatibility

Numerous third-party SFP modules have been tested for RouterOS compatibility. The following tables summarize tested modules with their specifications:

Gigabit SFP Modules:

Brand	Model	Rate	Connector	Wavelength	Tested With	Status
Finisar	FCLF-8521-3	1.25G	RJ45	N/A	RB2011LS-IN	Works
Cisco	GLC-T	1.25G	RJ45	N/A	RB2011LS-IN	Works
Cisco	GLC-SX-MM	1.25G	Dual LC	850nm	RB2011LS-IN	Works
Cisco	GLC-SX-MM	1.25G	Dual LC	850nm	RB2011LS-IN	Works
TP-Link	TL-SM311LM	1.25G	Dual LC	850nm	CCR1036 12G-4S	Works
TP-Link	TL-SM311LS	1.25G	Dual LC	1310nm	RB2011LS-IN	Works
Dell	FTLX8571D3BCL	1.25G	Dual LC	850nm	RB2011LS-IN	Works
6COM	6C-SFP-T	1.25G	RJ45	N/A	RB2011LS-IN	Works
Ingellen	INSP-T	1.25G	RJ45	N/A	RB2011LS-IN	Works

BiDi SFP Modules:

Brand	Model	Rate	Wavelength	Tested With	Status
6COM	6C-WDM-0210BSD	1.25G	Tx:1550nm/Rx:1310nm	RB2011LS-IN	Works
6COM	6C-WDM-0210ASD	1.25G	Tx:1310nm/Rx:1550nm	RB2011LS-IN	Works
ROBOFiber	SFP-7120-WA	1.25G	Tx:1490nm/Rx:1550nm	CCR, RB2011	Works
ROBOFiber	SFP-7120-WB	1.25G	Tx:1550nm/Rx:1490nm	CCR, RB2011	Works
OPTIC	OPTIC-SFP-3524S-02-SC	1.25G	Tx:1310nm/Rx:1550nm	RB2011UAS-RM	Works
Proline	GLC-BX-D20-PRO	1.25G	Tx:1490nm/Rx:1310nm	CRS125	Works

Not all possible third-party modules are tested or listed. Modules using standard SFP specifications generally function correctly, though some may report errors or warnings in RouterOS log output without affecting operation.

SFP Module Monitoring

RouterOS provides tools for monitoring SFP module status and diagnosing connectivity issues:

/interface ethernet monitor sfp1

This command displays link status, speed, duplex, fiber optical signal levels, and module temperature. The output includes receive power (rx-power) and transmit power (tx-power) measurements useful for diagnosing fiber path problems:

/interface print
/interface ethernet print stats

The print commands show current interface status including bytes sent/received and errors. Unexpected error counts indicate physical layer problems requiring fiber inspection or module replacement.

Fiber optic signal levels should fall within the module’s specified operating range. Received power below the sensitivity threshold causes intermittent connectivity or link failures. Transmit power at or near zero indicates module failure or fiber disconnection.

Common SFP Issues

Several common issues affect SFP module operation and connectivity.

Link flapping occurs when the physical connection repeatedly establishes and drops. This typically indicates marginal signal strength from dirty or damaged fiber connectors, incompatible module pairings, or fiber path problems. Clean fiber connectors with appropriate cleaning tools and verify both ends use compatible modules.

No link despite connected fiber suggests incorrect fiber type (using single-mode fiber with multimode modules or vice versa), incorrect wavelength pairing in BiDi configurations, or failed modules. Verify module specifications match your fiber infrastructure.

Speed mismatch occurs when SFP modules negotiate lower than expected speeds. This usually indicates incompatible modules at each end or cable quality insufficient for the target speed. Replace cables or modules as needed.

DDM/DOM warnings (Digital Diagnostic Monitoring) report marginal optical levels or temperature concerns. These warnings appear in log output and indicate conditions that may lead to failures. Investigate environmental factors or module degradation.

SFP+ Modules

Overview

SFP+ modules extend SFP capabilities to 10 gigabit per second data rates, enabling high-throughput connections for backbone links, server connections, and aggregation switches. SFP+ cages support both SFP+ modules (10G) and legacy SFP modules (1G), with automatic speed negotiation.

MikroTik’s native SFP+ modules (S+ prefix) receive automatic recognition and full support. The module family includes short-reach multimode modules (S+85DLC03D), long-reach single-mode modules (S+31DLC10D), BiDi modules for single-fiber operation (S+23LC10D, S+32LC10D), and copper twinax cables (S+DA0001, S+DA0003) for short connections within racks.

RJ45 SFP+ modules (S+RJ10) provide 10G connectivity over copper cabling, supporting various categories (Cat5e, Cat6, Cat7) with distances varying by cable quality. These modules enable 10G connectivity without fiber infrastructure, though distance limitations (typically 30 meters) restrict them to within-rack or adjacent-rack connections.

MikroTik SFP+ Modules

The following native SFP+ modules receive automatic support:

Model	Distance	Rate	Connector	Wavelength
S+85DLC03D	300m	10G	Dual LC, MM	850nm
S+31DLC10D	10km	10G	Dual LC, SM	1310nm
S+23LC10D	10km	10G	BiDi LC, SM	Tx:1270nm/Rx:1330nm
S+32LC10D	10km	10G	BiDi LC, SM	Tx:1330nm/Rx:1270nm
S+DA0001	1m	10G	Twinax Copper	N/A
S+DA0003	3m	10G	Twinax Copper	N/A
S+RJ10	varies	10G	RJ45	N/A

Native modules work immediately upon installation and appear in the interface list with full monitoring support. Twinax copper cables (S+DA0001, S+DA0003) provide reliable short-reach connections ideal for linking devices within the same rack without fiber infrastructure.

Third-Party SFP+ Compatibility

Tested third-party SFP+ modules include:

Brand	Model	Distance	Rate	Connector	Wavelength	Status
Cisco	SFP-10G-LR	10km	10G	Dual LC, SM	1310nm	Works
Dell	FTLX8571D3BCL	300m	10G	Dual LC, MM	850nm	Works
Fiberstore	SFP-10G31-40	40km	10G	Dual LC, SM	1310nm	Works
Fiberstore	SFP-10G55-40	40km	10G	Dual LC, SM	1550nm	Works
Fiberstore	SFP-10G32-40	40km	10G	BiDi LC, SM	Tx:1330nm/Rx:1270nm	Works
Fiberstore	SFP-10G23-40	40km	10G	BiDi LC, SM	Tx:1270nm/Rx:1330nm	Works
Optech	OPAK-TX1-00-C	30m	10G	RJ45	N/A	Works (RouterOS v6.40+)
ProLabs	SFP-10G-T-C	30m	10G	RJ45	N/A	Works (RouterOS v6.40+)

Note that one module (Atop APSP55B30CDL40, 40km) was tested and does not work with MikroTik devices. Avoid this specific model for RouterOS deployments.

SFP+ Configuration and Monitoring

SFP+ modules use the same monitoring infrastructure as SFP modules, with additional statistics relevant to 10G operation:

/interface ethernet monitor sfp-plus1

The output shows link status at 10G speed, optical levels, and module temperature. High-speed connections benefit from regular monitoring to detect degradation before complete failure.

Configure interface parameters for SFP+ ports:

/interface ethernet
set sfp-plus1 auto-negotiation=no speed=10Gbps

Auto-negotiation typically works correctly for SFP+ connections, but manual configuration may be necessary when connecting to devices with incompatible negotiation implementations.

U.2 Disks for RDS

Overview

RouterOS Disk Storage (RDS) enables using external storage drives with supported MikroTik devices for expanded logging, Dude server data, and container storage. The RDS2216-2XG-4S+4XS-2XQ Cloud Router Switch supports U.2 solid-state drives, providing high-capacity storage in a compact form factor.

U.2 drives (also known as SFF-8639) connect via PCIe and provide SATA or NVMe interface compatibility. The RDS2216 supports U.2 drives of any capacity, limited only by physical 7mm height requirements. This limitation excludes thicker 15mm drives common in enterprise storage.

Supported U.2 Drives

The following U.2 drives have been verified for compatibility with the RDS2216:

• Samsung PM9A3
• Samsung PM983
• Micron 7300 series
• Micron 7400 series
• WD DC SN640
• Transcend UTE210T
• Innodisk DGEU2

Any U.2 drive meeting the 7mm height specification should function correctly, though performance and reliability may vary by manufacturer and model. Enterprise-grade drives with power-loss protection and high endurance ratings are recommended for critical storage applications.

U.2 Drive Installation

Installing U.2 drives in the RDS2216 requires physical access to the device:

1. Power off the device and disconnect all cables
2. Remove the top cover screws and lift the cover
3. Locate the U.2 drive bay on the mainboard
4. Insert the drive with the connector facing the slot
5. Secure the drive with mounting screws
6. Replace the cover and reconnect cables

After physical installation, configure the drive in RouterOS:

/disk
print
/disk set 1 name=storage1

The drive should appear immediately in /disk print. Format the drive for use:

/disk format-drive 1

Formatting creates the necessary filesystem structures and prepares the drive for storage use. The drive then appears in /file operations and can be used for log storage, Dude data, or container mounts.

Quick Reference

Essential Commands

# View installed LTE interfaces
/interface lte print

# Monitor LTE connection status
/interface lte monitor [find]

# Configure LTE APN
/interface lte apn add apn=internet

# View SFP/SFP+ module status
/interface ethernet monitor sfp1

# View installed disks
/disk print

# Format disk for RDS
/disk format-drive 1

Peripheral Compatibility Summary

Peripheral Type	MikroTik Modules	Third-Party Support	RouterOS Version
Cellular Modems	R11e series	Extensive table	v6.x / v7.x
SFP Modules	S- series	Tested list	All versions
SFP+ Modules	S+ series	Tested list	RouterOS v6.40+ (RJ45)
U.2 Disks	RDS2216 only	Verified list	RDS capable

Related Topics

• USB Features - USB peripheral configuration
• RouterOS Disk Storage - Storage configuration
• Interface Configuration - Basic interface setup

Configuration Commands

• /interface lte add - Create LTE interface
• /interface ppp-client add - Create PPP cellular interface
• /interface ethernet monitor - Check SFP module status
• /disk format-drive - Initialize storage drive
• /interface lte at-chat - Send AT commands to modem