[j-nsp] Media issue or some bug

Junaid junaid.x86 at gmail.com
Fri Aug 1 05:35:27 EDT 2008


Hi,

Three of my E3s (on two different PICs) from my core M320 towards my
remote M7 went down all of sudden (at the same time) and stayed down.
I am receiving similar logs on all the routers:


05:00:46  M7i /kernel: e3-0/1/0.0 up: received keepalive
05:01:22  M7i /kernel: e3-0/1/0 down:
send=0x4846fa64/reflected=0x00002089 sequence numbers differ by 3 or
more
05:01:22  M7i mib2d[3068]: SNMP_TRAP_LINK_DOWN: ifIndex 36,
ifAdminStatus up(1), ifOperStatus down(2), ifName e3-0/1/0
05:01:34  M7i /kernel: e3-0/1/0 down:
send=0x4846fa65/reflected=0x0000208b sequence numbers differ by 3 or
more
05:01:43  M7i /kernel: e3-0/1/0 down:
send=0x4846fa66/reflected=0x0000208b sequence numbers differ by 3 or
more
05:01:52  M7i /kernel: e3-0/1/0 down:
send=0x4846fa67/reflected=0x0000208d sequence numbers differ by 3 or
more
05:02:00  M7i /kernel: e3-0/1/0 down:
send=0x4846fa67/reflected=0x0000208d sequence numbers differ by 3 or
more
05:02:10  M7i /kernel: e3-0/1/0 down:
send=0x4846fa68/reflected=0x0000208e sequence numbers differ by 3 or
more
05:02:20  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6a/reflected=0x0000208f sequence numbers differ by 3 or
more
05:02:29  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6a/reflected=0x00002090 sequence numbers differ by 3 or
more
05:02:42  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6c/reflected=0x00002091 sequence numbers differ by 3 or
more
05:02:51  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6d/reflected=0x00002092 sequence numbers differ by 3 or
more
05:03:02  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6e/reflected=0x00002093 sequence numbers differ by 3 or
more
05:03:10  M7i /kernel: e3-0/1/0 down:
send=0x4846fa6f/reflected=0x00002094 sequence numbers differ by 3 or
more
05:03:18  M7i /kernel: e3-0/1/0 down:
send=0x4846fa70/reflected=0x00002095 sequence numbers differ by 3 or
more


After a few hours, they came back online - and we did not change any
configuration on any of the routers. Can anyone give me a clue as to
what caused this error message to surface?



Regards,

Junaid


More information about the juniper-nsp mailing list