Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] Syslog message - "Uninitialized EDMEM[0x16f2580] Read (0x6db6db6d6db6db6d)" after adding a VCP link

0

0

Article ID: KB37353 KB Last Updated: 09 Aug 2021Version: 1.0
Summary:

After adding a VCP link to the Virtual Chassis (VC), the log message "Uninitialized EDMEM[0x16f2580] Read (0x6db6db6d6db6db6d)" appears on multiple Flexible PIC Concentrators (FPCs) of the backup member.

This article explains that the log message is triggered by corrupt packets coming from the newly added VCP link.

Symptoms:

After adding a VCP link to the VC, the log message "Uninitialized EDMEM[0x16f2580] Read (0x6db6db6d6db6db6d)" appears on multiple FPCs of the backup member.

{backup:member1-re0}
JTAC-re0> show log messages.1.gz | match "Uninitialized EDMEM"  
JTAC-re0 : %PFE-3: member1-fpc3 LUCHIP(1) RMC 1  Uninitialized EDMEM[0x16f2d81] Read (0x6db6db6d6db6db6d)
JTAC-re0 : %PFE-3: member1-fpc3 LUCHIP(0) RMC 0  Uninitialized EDMEM[0x16f25ce] Read (0x6db6db6d6db6db6d)
< Snip… >

Multiple PPE Trap/Ttrace files are also generated when the above logs are reported:

{backup:member1-re0}
JTAC-re0> file list /var/tmp detail | match "Jul 9"
-rw-r--r--  1 root  wheel       4548 Jul 9  04:04 ppe_trap_fpc1_LU_0_00.0
-rw-r--r--  1 root  wheel       4536 Jul 9  03:36 ppe_trap_fpc2_LU_0_00.2
-rw-r--r--  1 root  wheel       4113 Jul 9  00:38 ppe_trap_fpc3_LU_0_00.0
-rw-r--r--  1 root  wheel     137092 Jul 9  12:18 ppe_trap_fpc3_LU_0_01.0
-rw-r--r--  1 root  wheel       4549 Jul 9  00:29 ppe_trap_fpc3_LU_1_00.0
-rw-r--r--  1 root  wheel     139708 Jul 9  11:58 ppe_trap_fpc3_LU_1_01.0
-rw-r--r--  1 root  wheel       4547 Jul 9  02:18 ppe_trap_fpc8_LU_1_00.1
-rw-r--r--  1 root  wheel      33898 Jul 9  04:04 ttrace_fpc1_LU_0_00.0
<snip..>

The log messages continue to appear even after all affected FPCs are rebooted.

Upon analysis of the PPE/TTRACE files, most of the traffic is seen to come across the VCP link.

Also the following "lsp checksum error" log is always seen immediately before the EDMEM error log:

JTAC-re0 vccpd[18603]: %DAEMON-4-VCCPD_PROTOCOL_LSPCKSUM: LSP checksum error, interface vcp-5/1/0.32768, LSP id cce1.7fab.f800.00-00, sequence 0x2edde2, checksum 0xc84a, lifetime 118
JTAC-re0 : %PFE-3: member1-fpc3 LUCHIP(1) RMC 0  Uninitialized EDMEM[0x16f2cbd] Read (0x6db6db6d6db6db6d)
 
JTAC-re0 vccpd[18603]: %DAEMON-4-VCCPD_PROTOCOL_LSPCKSUM: LSP checksum error, interface vcp-5/1/0.32768, LSP id cce1.7fab.f800.00-00, sequence 0x2eddf1, checksum 0x92ef, lifetime 118
JTAC-re0 : %PFE-3: member1-fpc8 LUCHIP(0) PLCT INT_STAT 0x00000001 Uninitialized  EDMEM Read 0x6db6db6d6db6db6d @ 0x009c6802
Solution:

This log is triggered by corrupt packets coming from the newly added VCP link. Further the memory information inside does not exist.

When you remove the newly added VCP link, the EDMEM error log will no longer be seen. 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search