2G-2S.0.3.FC

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"

For security reasons, there is no reset button on the switches. If you need to reset the switch to factory settings, you will need a USB C cable (B - older models) and SIMULand.v4 configuration software.

Procedure

Click USB in the Conectivity menu, click Reset (Factory Default) in the following window and reset the switch to factory settings.

Note: For Windows 8.1 and earlier operating systems, you may need to install the USB driver.

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

In Simuland.v4, which always contains the latest firmware available for the switch.

After upgrading the switch, the switch will be set to its default settings, except for the IP, mask, gateway and ring.

Not really. After the switch upgrade, only the settings, IP, mask, gateway and ring will be preserved. The rest of the configuration will be default.

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.

LAN extenders

To answer this question, it is useful to refer to EN62305-1 (Lightning protection, Part 1 - General principles).

Switches, connected metallic cabling and equipment (cameras) should be located in the LPZ0B zone, i.e. in a zone protected by a lightning arrester against direct lightning strikes.

Table E.2 gives the expected utility current for LPL I-II (Lightning Protection Levels) under indirect lightning strike up to 100A (8/20µs) and for LPL (III-IV) up to 50A (8/20µs).

However, the standard recommends that magnetic cable shielding be included in the protection of electronic systems.

Therefore, if the switch will be in our OH65 steel enclosure and routed through the inside of a steel pole or steel protector (all under the arrester and grounded), 150A (8/20µs) is sufficient protection.

If any of the above precautions are not followed, switches with 1000A (8/20µs) protection on the FE ports must be used.

The most important thing is to make every effort to prevent direct lightning strikes, where the standard assumes a current of up to 2000A (10/350µs). Such a current is a major problem for the RJ45 connectors themselves. In our experience, the maximum level of current that RJ45 contacts can withstand is somewhere between 1-2kA (8/20µs).

‌

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".

Yes, the switch allows you to respond to the input state of a remote device by data shutting down the port. PoE remains active, so there is no need to wait for camera initialization on recovery, it is available immediately.