Jump to content
Калькуляторы

mse.rus77

Активный участник
  • Content Count

    328
  • Joined

  • Last visited

1 Follower

About mse.rus77

  • Rank
    Студент
  • Birthday 12/17/1985

Контакты

  • ICQ
    144208975

Информация

  • Пол
    Мужчина

Город

  • Город
    Москва

Recent Profile Visitors

2322 profile views
  1. Провел анализ графиков, всплеск трафика тут не при делах, это штатное и регулярное явление, это аплинк на с3750
  2. И, кстати, интересный момент, что не рисует только графики по интерфейсам, а вот по остальному есть и там ничего необычного   Да, документация об этом гласит, да и проверял специально.
  3. так давно уже term accept-icmp { from { destination-prefix-list { LOCALS-v4; } icmp-type [ echo-reply echo-request time-exceeded unreachable source-quench router-advertisement parameter-problem ]; } then { policer management-1m; count accept-icmp; accept; } }
  4. Так исторически сложилось, нужно будет подумать в выходные над этим моментом. Я настроил фильтры, проверил и спал спокойно, до сегодня.
  5. Здравствуйте! Есть MX240 с JUNOS Base OS Software Suite [11.2R2.4] и контролплейн прикрыт: на lo0 unit 0 { family inet { filter { input-list [ accept-ospf accept-bgp accept-common-services discard-all-to-locals-v4 ]; } } } Ночью началось: Mar 19 02:15:03 MX240 pfed: ipc_pipe_write wrote only 36 out of 0 bytes Mar 19 02:19:13 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:23:54 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:24:14 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 02:24:14 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 02:29:14 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:29:35 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 68 bytes, actually sent 8 bytes Mar 19 02:29:35 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 60 bytes Mar 19 02:33:55 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:34:15 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:35:15 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 02:35:15 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 02:44:16 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:44:26 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 02:44:26 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 02:48:56 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 02:53:57 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:03:58 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:04:18 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:09:18 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:09:38 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:09:38 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:13:59 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:18:59 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:24:20 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:24:40 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:24:40 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:29:00 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:29:20 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:29:20 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:34:01 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:34:11 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:34:11 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:39:21 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:39:41 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:39:41 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:44:02 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:45:42 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:45:42 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 03:54:03 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:54:23 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 03:54:33 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 03:54:33 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 04:04:44 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:05:04 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:05:24 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:05:44 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 04:05:44 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 04:14:35 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 04:14:35 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 04:19:36 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 04:19:36 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 04:24:06 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:25:36 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 80 bytes, actually sent 8 bytes Mar 19 04:25:36 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 72 bytes Mar 19 04:34:07 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:35:07 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:42:55 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 60 bytes, actually sent 16 bytes Mar 19 04:42:55 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 44 bytes Mar 19 04:44:58 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:49:19 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:53:39 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 04:57:59 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 05:00:03 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 1820 bytes, actually sent 828 bytes Mar 19 05:00:03 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 992 bytes Mar 19 05:01:03 MX240 mgd[92391]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 05:06:40 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 05:13:38 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 60 bytes, actually sent 36 bytes Mar 19 05:13:38 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 24 bytes Mar 19 05:16:21 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 05:20:03 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 1820 bytes, actually sent 828 bytes Mar 19 05:20:03 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 992 bytes Mar 19 05:25:02 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 05:27:08 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_FRAG: Attempted to send 60 bytes, actually sent 44 bytes Mar 19 05:27:08 MX240 snmpd[1404]: LIBJSNMP_SA_PARTIAL_SEND_REM: Queuing message remainder, 16 bytes Mar 19 05:29:23 MX240 mib2d[1403]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping. Attempting to re-register. Mar 19 05:31:03 MX240 mgd[92554]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 06:31:04 MX240 mgd[92876]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 08:01:04 MX240 mgd[93354]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 09:01:04 MX240 mgd[93673]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 10:31:04 MX240 mgd[94151]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 11:01:04 MX240 mgd[94311]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 11:31:04 MX240 mgd[94471]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 12:31:04 MX240 mgd[94794]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 13:01:04 MX240 mgd[94954]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 13:31:04 MX240 mgd[95114]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated Mar 19 14:01:05 MX240 mgd[95274]: UI_RECONN_READ_FAILED: Invalid response from peer 'mib-process': 421 Connection unexpectedly terminated какти с того момента графики не рисует, а одном из аплинков перед началом всей петрушки - всплеск ИСХОДЯЩЕГО трафика до 220М. Что бы это все значило?
  6. Коллеги, приветствую! Вчера делал правки в firewall family inet filter, добавил term и сделал commit confirmed 5 и после этого моргнули xe порты на fpc5,fpc6 и что-то произошло на fpc7. Само восстановилось, но стремный момент, подскажите, куда копать? Информация о стеке: show system software all-members | match "JUNOS Base OS Software" JUNOS Base OS Software Suite [12.3R9.4] JUNOS Base OS Software Suite [12.3R9.4] JUNOS Base OS Software Suite [12.3R9.4] JUNOS Base OS Software Suite [12.3R9.4] JUNOS Base OS Software Suite [12.3R9.4] JUNOS Base OS Software Suite [12.3R9.4] show chassis firmware Part Type Version FPC 2 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 FPC 3 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 FPC 4 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 FPC 5 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 FPC 6 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 FPC 7 uboot U-Boot 1.1.6 (Jul 5 2012 - 11:58:22) 1.0.0 loader FreeBSD/PowerPC U-Boot bootstrap loader 2.4 show chassis hardware | match FPC FPC 2 REV 07 750-033064 *329 EX4200-48P, 48 POE CPU BUILTIN BUILTIN FPC CPU FPC 3 REV 17 750-033063 *468 EX4200-48T, 8 POE CPU BUILTIN BUILTIN FPC CPU FPC 4 REV 17 750-033063 *467 EX4200-48T, 8 POE CPU BUILTIN BUILTIN FPC CPU FPC 5 REV 18 750-021255 *226 EX4200-48P, 48 POE CPU BUILTIN BUILTIN FPC CPU FPC 6 REV 14 750-033064 *497 EX4200-48P, 48 POE CPU BUILTIN BUILTIN FPC CPU FPC 7 REV 12 750-033064 *213 EX4200-48P, 48 POE CPU BUILTIN BUILTIN FPC CPU show virtual-chassis status Preprovisioned Virtual Chassis Virtual Chassis ID: 6c74.beb7.f5e4 Virtual Chassis Mode: Enabled Mstr Mixed Neighbor List Member ID Status Serial No Model prio Role Mode ID Interface 2 (FPC 2) Prsnt *329 ex4200-48p 129 Master* N 3 vcp-0 7 vcp-1 3 (FPC 3) Prsnt *468 ex4200-48t 129 Backup N 4 vcp-0 2 vcp-1 4 (FPC 4) Prsnt *467 ex4200-48t 0 Linecard N 5 vcp-0 3 vcp-1 5 (FPC 5) Prsnt *226 ex4200-48p 0 Linecard N 6 vcp-0 4 vcp-1 6 (FPC 6) Prsnt *497 ex4200-48p 0 Linecard N 7 vcp-0 5 vcp-1 7 (FPC 7) Prsnt *213 ex4200-48p 0 Linecard N 2 vcp-0 6 vcp-1 Лог: Как я понимаю, ноги у проблемы растут с fpc7 - там образовалась корка show system core-dumps member 7 fpc7: -------------------------------------------------------------------------- /var/crash/*core*: No such file or directory -rw-rw---- 1 root field 3439701 Nov 16 17:55 /var/tmp/pfem.core-tarball.0.tgz /var/tmp/pics/*core*: No such file or directory /var/crash/kernel.*: No such file or directory total files: 1 и на нем меня смущает member 0 с NotPrsnt в virtual-chassis device-topology fpc7: -------------------------------------------------------------------------- Neighbor List Member Device Status System ID Member Device Interface 0 0 NotPrsnt 7819.f783.b480 0 1 NotPrsnt 7819.f783.b481 0 2 NotPrsnt 7819.f783.b482 2 6 Prsnt 50c5.8dba.7f80 2 8 internal-0/24 3 10 vcp-0 2 7 Prsnt 50c5.8dba.7f81 2 8 internal-1/25 7 21 vcp-1 2 8 Prsnt 50c5.8dba.7f82 2 6 internal-2/24 2 7 internal-2/27 3 9 Prsnt b0a8.6e02.3800 3 11 internal-0/24 4 13 vcp-0 3 10 Prsnt b0a8.6e02.3801 2 6 vcp-1 3 11 internal-1/25 3 11 Prsnt b0a8.6e02.3802 3 9 internal-2/24 3 10 internal-2/27 4 12 Prsnt b0a8.6e02.3980 5 16 vcp-0 4 14 internal-0/24 4 13 Prsnt b0a8.6e02.3981 3 9 vcp-1 4 14 internal-1/25 4 14 Prsnt b0a8.6e02.3982 4 12 internal-2/24 4 13 internal-2/27 5 15 Prsnt 0026.8867.1400 5 17 internal-0/24 6 19 vcp-0 5 16 Prsnt 0026.8867.1401 5 17 internal-1/25 4 12 vcp-1 5 17 Prsnt 0026.8867.1402 5 15 internal-2/24 5 16 internal-2/27 6 18 Prsnt 7819.f782.ba80 6 20 internal-0/24 7 22 vcp-0 6 19 Prsnt 7819.f782.ba81 5 15 vcp-1 6 20 internal-1/25 6 20 Prsnt 7819.f782.ba82 6 18 internal-2/24 6 19 internal-2/27 7 21 Prsnt 7819.f783.b480 2 7 vcp-0 7 23 internal-0/24 7 22 Prsnt 7819.f783.b481 6 18 vcp-1 7 23 internal-1/25 7 23 Prsnt 7819.f783.b482 7 21 internal-2/24 7 22 internal-2/27 На других fpc такого нет, все member-ы верные, все в Prsnt.
  7. Спасибо! А правильно понимаю, аплинк ловим в комбо SFP порт (комбо тут следует понимать не как SFP/Copper, а 100/1000 Mbps)? А с любого из 4-х других SFP кидать линк на медный коммутатор (оптическим или медным SFP трансом)? И там есть все плюшки RouterOS ? Хотя, надо-то пару вланов, дхцп сервер + нат
  8. Коллеги, приветствую! Есть 100Mbps ВО линк, на стороне абонента SFP - LinkCare CL-SFP-WDM-20-55/155SC DD Заведется ли оно в Mikrotik hEX S? Меня смущает The device has a USB 2.0, PoE output for Ethernet port #5 and a 1.25Gbit/s SFP cage. Если нет, то на какой микрот можно приземлить этот канал? Спасибо!
  9. А разве не два микротика минимум нужно рассматривать? ))) А по делу, не рассматривают, потому, что вменяемые.
  10. XYZ упал

    Коллеги, Мегафон в МСК сейчас уже штатно работает, скажите пожалуйста? Можно ли препенд снимать)
  11. XYZ упал

    Коллеги, с МГТС все норм? Не детектировали сегодня проблем никаких? В наш сапорт поступают заявки, что наши ресурсы недоступны с МГТС (шпд).
  12. Эх, выбор на RB2011 упал из-за наличия возможности получить железку 4free, подгон от друга)) Попробую пообщаться с провайдером, даже интересно, как общение сложится по такому не стандартному вопросу.
  13. Печально, остается тогда только поменять конвертер на другой 100М, не думаю, что пров будет заниматься модернизацией абонентского линка с 100М до 1Г, а с текущим конвертером проблемы - рандомно отваливается связь, перестает пакеты пропускать, по питанию его дергают, оживает на время. Спасибо за информацию.
  14. Коллеги, приветствую! Есть подключение в частном секторе, волокно приходит в медиаконвертер Rubytech Single Fiber 10/100M SC 1550nm (дальность удаленно выяснить не смог, но думаю 10 км.) Хочется перевести подключение на MIkrotik RB2011UiAS-2HnD-IN и исключить медюк из схемы, в связи с этим, прошу подсказать, с каким трансивером WDM 1550 SC километров на 10 заведется 100М линк в микротике? Спасибо!