Industrial-managed switches with SSH CLI and SIMULand GUI configuration are equipped with COMBO ports, SFP slots, RS485 buses, digital / alarm inputs, and a programmable relay. In addition to supporting common network standards, they also contain Event management with 64 automatic actions, making these switches the ideal solution for complex applications with high demands on security and flexibility of the equipment used. The switches support redundant MESH / RING topologies with link recovery below 30ms and redundant power supply. The highly resilient hardware allows the switches to be deployed in harsh environments over a wide operating temperature range.
Some of the listed features will be released during 2025!
The current list of available features is available upon request at info@metel.eu.
Devices are developed and manufactured in the EU and meet the requirements of the NDAA.
Industrial managed switches with configuration via SSH CLI and SIMULand GUI are equipped with 2x COMBO port (SFP/RJ45), 8x SFP slot 100BASE-X, 2x DI with balanced loop support, 1x programmable output NO/NC RELAY, 2x RS485 / 1x RS422 BUS (support for MIOS modules, TCP server, UDP mode), USB port for local management, redundant power input, surge protection on all inputs, EVENT MANAGEMENT: SMTP, TCP events, ETH events, HTTP client (camera control), 8x IPWatchdog.... , operating temperature -40...+75°C, VLAN, QoS, SNMP, SMTP, SNTP, IGMPv1/2, RSTP, LLDP, 802.1X, installation on flat surface or DIN35, 12VDC/24VDC/48VDC/12VAC/24VAC/56VDC
Order code: 1-178-220
Availability: Full-scale production
| COMBO PORT | |
|---|---|
| Number of | 2 |
| SFP slot | 100/1000 BASE-LX, BASE-BX |
| RJ45 | 10/100/1000 BASE-T |
| SFP SLOT | |
|---|---|
| Number of | 8 |
| Supported formats | 100 BASE-LX, BASE-BX |
| RS485 | |
|---|---|
| Number of | 2 |
| Speed | max. 115200 bps |
| Surge protection | 1500 W waveform 10/1000 μs |
| DI/BI INPUTS | |
|---|---|
| Number of | 2 |
| Digital mode | NC / NO |
| Alarm mode | Analog 0 - 30 kΩ for balanced loops |
| RELÉ OUTPUT | |
|---|---|
| Number of | 1 |
| Contact type | Switching |
| Max. Load | 62.5 VA (30 W) / 1 A / 60 V (resistive load) |
| POWER | |
|---|---|
| Number of | 2 |
| Connector | WAGO 734-205 |
| Input voltage range | 10 - 30 VAC / 10 - 60 VDC |
| Energy consumption | Max. 13 W |
| Surge protection | 1500 W waveform 10/1000 μs |
| ENVIRONMENT | |
|---|---|
| Operating temperature | -40...+75 °C |
| Storage temperature | -40...+75 °C |
| Humidity | Max. 100% (non-condensing) |
| MECHANICS | |
|---|---|
| Weight | 1.1 kg |
| Dimensions - h / w / d | 60 x 255 x 113 mm |
| IP protection | IP 30 |
| Cooling | Passive |
| SECURITY | |
|---|---|
| Firmware Booting | The code is encrypted and signed |
| Secure Boot decrypt and verify the signature | |
| Firmware Upgrade | The FW image is encrypted and signed using AES-256, RSA-4096, SHA-512 |
| SNMP | SNMPv3 - SHA-512 / AES-256 (recommended) |
| SNMPv2c (obsolete) | |
| GUI Application | Digitally signed installation file using SHA-256, RSA 4096 |
| IEEE 802.1X-2004 | RFC3748 - EAP Packet Format, Authenticator PAE, Supplicant PAE |
| SSH | SSH v2, OpenSSH, OpenSSL |
| Tacacs+ | Authentication, Authorisation, Accounting |
| MANAGEMENT | |
|---|---|
| Application | SIMULand.v4 |
| SNMPv3 | Encrypted |
| SSH | CLI |
| SWITCH | |
|---|---|
| Number of MAC addresses | 8 K |
| Maximum frame size | 1632 B |
| Packet buffer | 1 Mbit |
| Switching | Store-and-forward, full wire-speed, non-blocking on all ports |
| Switching capacity | 5.6 Gbps |
| EMC and safety | ||
|---|---|---|
| EN 55032 | EMC of multimedia devices - emission requirements | |
| EN 55035 | EMC of multimedia devices - immunity requirements | |
| EN 62368-1 | Safety requirements of Information technology equipment | |
| EN IEC 63000 | The Assessment Of Electrical And Electronic Products With Respect To The ROHS | |
| EN 61000-4-2 | 8 kV | Air discharge |
| EN 61000-4-2 | 4 kV | Contact discharge |
| EN 61000-4-3 | 10 V/m | Radiated HF field |
| EN 61000-4-4 | 1 kV | Bursty |
| EN 61000-4-5 | 1 kV | Shock impulses |
| EN 61000-4-6 | 3 V | Resistance to RF field induced line disturbances |
| EN 61000-4-8 | 30 A/m | Magnetic field |
| EN 50121-4 ed.4 | Railway applications - EMC Emission and immunity of signalling and communication equipment | |
| Standards and protocols | |
|---|---|
| IEEE 802.3i | 10BASE-T 10 Mbit/s (1.25 MB/s) over twisted pair IEEE 802.3u for 100BaseT(X) and 100BaseFX |
| IEEE 802.3u | 100BASE-TX, 100BASE-T4, 100BASE-FX Fast Ethernet at 100 Mbit/s (12.5 MB/s) with autonegotiation |
| IEEE 802.3ab | 1000BASE-T Gbit/s ethernet over twisted pair at 1 Gbit/s (125 MB/s) |
| IEEE 802.3z | 1000BASE-X Gbit/s ethernet over optical fiber at 1 Gbit/s (125 MB/s) |
| IEEE 802.3ac | Max. frame size 1522 bytes (allow 802.1Q tag) |
| IEEE 802.3x | Flow Control |
| IEEE 802.1p | Class of Service |
| IEEE 802.1X | Port-based Network Access Control (PNAC) |
| IEEE 802.1q | VLAN tagging |
| Modbus TCP/RTU | Master / Slave |
| SNMP v2c/v3 | Simple Network Management Protocols |
| IGMP v1/v2 | Internet Group Management Protocols |
| SMTP | Simple Mail Transfer Protocol |
| SNTP | Simple Network Time Protocol |
| RSTP | Rapid Spanning Tree Protocol |
| LAN-RING.v1, v2 | Ring topology with a very short time reconfiguration of max. 30ms |
| Management | GUI SIMULandv4 - USB C / Encrypted management via LAN |
| LACP | IEEE 802.3ad, Link Aggregation Control Protocol |
| MSTP | Multiple Spanning Tree Protocol |
| Tacacs+ | Terminal Access Controller Access-Control System for Authentication, Authorization, and Accounting (AAA) in network security |
| Syslog | Standard for message logging |
SNMPv3 (read and write)
Username:"master"
Authentication algorithm: SHA1
Authentication password:"mastermaster"
Private algorithm: AES128
Private password:"mastermaster"
SNMPv3 (read only)
Username:"user"
Authentication algorithm: SHA1
Authentication password:"useruser"
Private algorithm: AES128
Private password:"useruser"
SNMPv2c (read and write)
Community:"write"
SNMPv2c (read only)
Community:"read"
SSH (ethernet)
User:"metel"
Password:"metel"
SSH (USB)
Service:"metel"
User:"metel"
Password:"metel"
Yes. A USB factory reset will restore the device to factory settings.
Default parameters
IP address - printed on the switch label
Mask - 255.0.0.0
Gateway - 10.1.0.1
YES, the configuration should be preserved even after a system upgrade, but it is always a good idea to backup the current configuration beforehand. I recommend making a complete backup to avoid any problems that may occur during the upgrade.
The mechanical and electrical parameters of SFP modules and slots are defined in the MSA (multi-source agreement). This ensures mutual compatibility between SFP module manufacturers and SFP slots of network elements. The SFP module includes an EEPROM. It stores information about the module type, supported speed, optical interface type, etc. The most widely used standards in IT are 100BASE-LX and 1000BASE-LX standards (LC connectors) with 2-fiber communication. This has probably also led to the fact that some commercial switches do not support the more modern single-fiber 100BASE-BX and 1000BASE-BX standards. Specifically, this refers to Byte 6 in the EEPROM (Ethernet Compliance Codes). For the above reasons, all BX-1000-...SFP modules have bit 1 (1000BASE-LX) set in Byte 6 and BX-1000-...SFP modules have bit 4 (100BASE-LX) set in Byte 6. The modules are then easily detected even by a switch that does not implement 100/1000BASE-BX support.
For modules with bidirectionaldata transmission over a singlefiber (wave multiplex), it is necessary to connect the optical modules correctlyto each other. Thismeans that, for example, inMETELWDM modules,the modulemarkedW4can only be interconnected with the modulemarkedW5. It is not possible to connect W4 with W4 or W5 with W5.
BX-100(0)-20-Wx-L
WavelengthsW4: TX:1310 / RX:1550 nm
WavelengthsW5: TX:1550 / RX:1310 nm
BX-10G-20-Wx
WavelengthsW4: TX:1270 / RX:1330 nm
Wavelengths W5: TX:1330 / RX:1270 nm
YES, ifyouare using the LAN-RING protocol. In terms of the LAN-RING protocol, the port with thelowerindex is thetransmitportand the port with thehigherindex is thereceiveport.Therefore,the rulemustbefollowedthat the optics will be connected from thelowerindex portto thehigherindex port.Therefore,inallswitchesin a ring,SFP modulesmustbeinserted in thesameway, e.g., an SFP with theW4 tag at the endwill be inserted into slot G1and anSFP with theW5 tag will be inserted into slot G2.
NO, ifyoudisable the LAN-RING protocol oruse the RSTP protocol. Inthiscase,it does not matter how the SFPs are inserted.
Yes, they have support.
For example, we can recommend the following tested types:
MICROTIK S-RJ01
BEL SFP-1GBT-05
RJ45 SFP modules are not supported in the 2G-2C.8S.0.0.F(G)-BOX switch on ports P1-P8.
SNMPv3-enabled switches have SHA1 and AES128 methods enabled by default. You can change to SHA512 and AES256c in the configuration.
The recommended line load is 75% of the total data throughput.
Yes, of course, this option is available for the LAN-RING system. Only in this case, we recommend disabling the ringing function in the switch configuration (None) or switching LAN-RING to Rapid Spanning Tree Protocol (RSTP-M).
If the distance between the camera and the switch is longer than 100 m, we use a LAN-EXT solution. This is a device that can repeat the route of the link, even several times in a row.
I have observed different RSTP behavior of your switch compared to a competing switch in the following situation. There are two switches in the network connected to each other by a fiber optic link. Egress filtering is enabled on one of these devices (Egress filtering: No unknown destination address). However, only one switch is available at this time because the link is blocked by the RSTP protocol. However, if I replace the unavailable switch with a competing device with a similar configuration, both switches are available.
Egress filtering causes BPDU frames to be sent only in one direction because the other direction is filtered. This causes the first switch to know about the second, but the second switch does not know about the first. This condition is handled by the so-called "contention mechanism". This was incorporated into the 802.1D-2004 standard and solves the problem you mentioned by blocking the link to prevent loops. Our implementation of the RSTP protocol complies with this standard. Other vendors may have a different implementation of the RSTP protocol based on an older standard that did not include a "dispute mechanism".