[j-nsp] MX480 with new RE's -- Memory mismatch alarms

William McLendon wimclend at gmail.com
Tue Nov 29 10:45:52 EST 2016


hey all,

curious if anyone has seen this and knows why it happens or if its anything to be concerned about.  we received new MX480s with the new 64G Routing Engines where Junos is in a VM, and on both MX480s we have seen messages like the following:

MX480-2-re0> show system alarms 
2 alarms currently active
Alarm time               Class  Description
2016-11-28 21:25:07 UTC  Minor  RE 1 Mismatch in total memory detected
2016-11-28 21:25:02 UTC  Minor  RE 0 Mismatch in total memory detected

with syslog messages like this:

Nov 28 19:10:20.919 2016  MX480-2-re0 craftd[4836]: Minor alarm cleared, RE 0 Mismatch in total memory detected
Nov 28 19:10:20.919 2016  MX480-2-re0 craftd[4836]: Minor alarm cleared, RE 1 Mismatch in total memory detected
Nov 28 21:23:26.518 2016  MX480-2-re0 kernel: real memory  = 51539607552 (49152 MB)
Nov 28 21:23:26.518 2016  MX480-2-re0 kernel: avail memory = 50002657280 (47686 MB)
Nov 28 21:23:40.941 2016  MX480-2-re0 chassisd[4833]: re_rainier_perform_misc_checks:RE memory size mismatch expected 65536 M , actual 0 M
Nov 28 21:25:02.051 2016  MX480-2-re0 alarmd[5155]: Alarm set: RE color=YELLOW, class=CHASSIS, reason=RE 0 Mismatch in total memory detected
Nov 28 21:25:02.090 2016  MX480-2-re0 craftd[4836]:  Minor alarm set, RE 0 Mismatch in total memory detected
Nov 28 21:25:07.372 2016  MX480-2-re0 alarmd[5155]: Alarm set: RE color=YELLOW, class=CHASSIS, reason=RE 1 Mismatch in total memory detected
Nov 28 21:25:07.372 2016  MX480-2-re0 craftd[4836]:  Minor alarm set, RE 1 Mismatch in total memory detected


going to open a TAC ticket, but was curious if anyone else had seen this and had any insight.

Thanks,

Will


More information about the juniper-nsp mailing list