Russian equipment. Part 3. qBRIDGE
Once again I was lucky to deal with a Russian piece of iron. The review will be quite small, introductory.
This time the inverse multiplexer / converter from NSGate is qBRIDGE401 .
They replaced several Mlinks.
Briefly about the technical characteristics.
')
A blue box with a height of one unit and a width of 25 cm can be installed in a 19 inch rack by fastening the ears to it. On board, there is a 4-hport Ethernet switch, 4 E1 ports, a bunch of status indicators for these ports, a switch to configure the device, a console port, and connectors / power connector.
The device is made in the Soviet way simple and clear. Apart from the name of the model, no design elements or identifying marks and “excesses of any bad” were found on the surface.
The power supply can be organized both from the mains 220V through the adapter and from -48V.
The indicators on the front panel show us:
PWR : On with power supply,
LAN SPEED 1-4 : Enabled when the Ethernet port is operating in 100 Mbps mode,
LAN FDX / COL 1-4 : Enabled when the Ethernet port is operating in full duplex mode, flashes if there is a collision when the Ethernet port is operating in half duplex mode,
L AN LNK / ACT 1-4 : Enabled, if the Ethernet port is connected, flashes when receiving / transmitting data
E1 CRC 1-4 : Enabled when receiving from the E1 line a CRC4 superframe with a CRC4 error,
E1 RAL 1-4 : Enabled when a remote symptom is detected in a received signal
devices including LOS (no signal at reception), LOF (loss of frame synchronization) and AIS remote device,
E1 LOF 1-4 : Enabled when the receiver loses E1 frame alignment cyclic timing.
sync FAS / NFAS (LOF, loss of frame).
I must say that the piece of iron is the dumbest. The converter has two versions: with control and without. In the first case, we can connect to it through the DB9 port and then the switch is not used, in the second the port is not used, and all settings are limited to the position of the switches. There is no question of any remote control.
Why it is necessary to refuse Mlink'a in favor of qBRIDGE? Because it has the ability to combine E1 channels to transmit Ethernet traffic. Mlink could not do this and in fact was limited to 2 Mb / s to the point (1.92, in fact). Thus, the total bandwidth using qBRIDGE can reach 7.68 Mb / s.
If one of the E1 links drops, then the Ethernet runs over the remaining ones. The converter automatically turns on the channel when the connection is restored.
The device supports QoS and VLAN. In the case of a managed device, the parameters can be configured.
In our hands fell unmanaged device, but despite this console cable was included.
A little about the configuration. The port number of the remote device must match the number on the local. When making changes (using switches), you must manually turn the power.
Switch assignment:
From the 6th to the 8th are used to configure the synchronization source,
The 5th switch on and off the mode in which the data arriving at the E1 ports are returned without changes to the same ports,
The 4th is used to manage the frame buffer. The maximum size is 4 Mbit. When the switch is turned off, the entire buffer is used, with only a part turned on (according to the documentation, 512 kbps by default).
The remaining three are reserved and must be in the off position.
Management through the console is limited to configuring the same parameters, plus switch ports, VLAN and QoS. The settings are deep enough, but in the absence of the opportunity to test, I will not describe them.
Testing in the laboratory has not revealed any problems so far.
Soon the piece of iron will go to the front and join the ranks of our telecommunication equipment.
<In the meantime, sad statistics on Mlink and LANTASIC are collected . In the near future, a small post about this>
This time the inverse multiplexer / converter from NSGate is qBRIDGE401 .
They replaced several Mlinks.
Briefly about the technical characteristics.
')
Iron
A blue box with a height of one unit and a width of 25 cm can be installed in a 19 inch rack by fastening the ears to it. On board, there is a 4-hport Ethernet switch, 4 E1 ports, a bunch of status indicators for these ports, a switch to configure the device, a console port, and connectors / power connector.
The device is made in the Soviet way simple and clear. Apart from the name of the model, no design elements or identifying marks and “excesses of any bad” were found on the surface.
The power supply can be organized both from the mains 220V through the adapter and from -48V.
The indicators on the front panel show us:
PWR : On with power supply,
LAN SPEED 1-4 : Enabled when the Ethernet port is operating in 100 Mbps mode,
LAN FDX / COL 1-4 : Enabled when the Ethernet port is operating in full duplex mode, flashes if there is a collision when the Ethernet port is operating in half duplex mode,
L AN LNK / ACT 1-4 : Enabled, if the Ethernet port is connected, flashes when receiving / transmitting data
E1 CRC 1-4 : Enabled when receiving from the E1 line a CRC4 superframe with a CRC4 error,
E1 RAL 1-4 : Enabled when a remote symptom is detected in a received signal
devices including LOS (no signal at reception), LOF (loss of frame synchronization) and AIS remote device,
E1 LOF 1-4 : Enabled when the receiver loses E1 frame alignment cyclic timing.
sync FAS / NFAS (LOF, loss of frame).
Software and management
I must say that the piece of iron is the dumbest. The converter has two versions: with control and without. In the first case, we can connect to it through the DB9 port and then the switch is not used, in the second the port is not used, and all settings are limited to the position of the switches. There is no question of any remote control.
Why it is necessary to refuse Mlink'a in favor of qBRIDGE? Because it has the ability to combine E1 channels to transmit Ethernet traffic. Mlink could not do this and in fact was limited to 2 Mb / s to the point (1.92, in fact). Thus, the total bandwidth using qBRIDGE can reach 7.68 Mb / s.
If one of the E1 links drops, then the Ethernet runs over the remaining ones. The converter automatically turns on the channel when the connection is restored.
The device supports QoS and VLAN. In the case of a managed device, the parameters can be configured.
In our hands fell unmanaged device, but despite this console cable was included.
A little about the configuration. The port number of the remote device must match the number on the local. When making changes (using switches), you must manually turn the power.
Switch assignment:
From the 6th to the 8th are used to configure the synchronization source,
The 5th switch on and off the mode in which the data arriving at the E1 ports are returned without changes to the same ports,
The 4th is used to manage the frame buffer. The maximum size is 4 Mbit. When the switch is turned off, the entire buffer is used, with only a part turned on (according to the documentation, 512 kbps by default).
The remaining three are reserved and must be in the off position.
Management through the console is limited to configuring the same parameters, plus switch ports, VLAN and QoS. The settings are deep enough, but in the absence of the opportunity to test, I will not describe them.
Testing in the laboratory has not revealed any problems so far.
Soon the piece of iron will go to the front and join the ranks of our telecommunication equipment.
<In the meantime, sad statistics on Mlink and LANTASIC are collected . In the near future, a small post about this>
Source: https://habr.com/ru/post/81671/
All Articles