Jump to content

Recommended Posts

Posted

Здравствуйте!

Есть 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М.

 

Что бы это все значило?

 

 

 

 

 

Posted
10 минут назад, VolanD666 сказал:

А зачем у вас CP в мир то смотрит?

Так исторически сложилось, нужно будет подумать в выходные над этим моментом. Я настроил фильтры, проверил и спал спокойно, до сегодня.

Posted

Может, зашейпить echo-request из внешнего мира? Жестко зашейпить.


И, похоже, что еще и PMTU играются. Интересная пляска по нагрузке процессора атакуемого...

Posted
5 минут назад, snvoronkov сказал:

Может, зашейпить echo-request из внешнего мира? Жестко зашейпить.


И, похоже, что еще и PMTU играются. Интересная пляска по нагрузке процессора атакуемого...

так давно уже

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;
    }
}

 

Posted
13 минут назад, snvoronkov сказал:

Может, зашейпить echo-request из внешнего мира? Жестко зашейпить.


И, похоже, что еще и PMTU играются. Интересная пляска по нагрузке процессора атакуемого...

И, кстати, интересный момент, что не рисует только графики по интерфейсам, а вот по остальному есть и там ничего необычного

 

mx240.png

 

7 минут назад, VolanD666 сказал:

Простите, не совсем помню как там у Juniper по интерфейсам, но вы точно уверены что трафик идет на lo0 ?

Да, документация об этом гласит, да и проверял специально.

Posted

Провел анализ графиков, всплеск трафика тут не при делах, это штатное и регулярное явление, это аплинк на с3750

 

cisco_po20_to_MX240.png

Posted

Я тут, наверное, сольюсь. Таки 240-й штука заметно более сложная, чем 80-й. Может есть в нем какие штатные грабельцы с интерфесными картами/процессорами/шиной, только мне сие неведомо. :-(

Posted

Попробуйте pfed перезапустить , это безболезнено и на трафике не скажется.  А вообще обновились бы, стыдно должно быть на таком софте сидеть. Хотябы до последнего 12.3 или 13.3

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...
На сайте используются файлы cookie и сервисы аналитики для корректной работы форума и улучшения качества обслуживания. Продолжая использовать сайт, вы соглашаетесь с использованием файлов cookie и с Политикой конфиденциальности.