We see the mac_local_fault on multiple random ports and we also see the HOST_LOOPBACK_MAKE_CMERROR_ID[0] (0x20001)
>show version detail no-forwarding
Model: ptx10002-60c
fpc0 CMError: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[0] (0x20001), scope: pfe, category: functional, severity: major, module: Host Loopback, type: Host Loopback Path Id 0, oc_category: default
fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[0] (0x20001) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
alarmd[29686]: Alarm set: FPC id=150995048, color=RED, class=CHASSIS, reason=FPC 0 Major Errors
craftd[29712]: Receive FX craftd set alarm message: color: 1 class: 100 object: 104 slot: 0 silent: 0 short_reason=FPC 0 Major Errors long_reason=FPC 0 Major Errors id=150995048 reason=150994944
craftd[29712]: Major alarm set, FPC 0 Major Errors
fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[0] (0x20001) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
fpc0 Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID 0 (URI: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[0])
fpc0 CMError: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[1] (0x20002), scope: pfe, category: functional, severity: major, module: Host Loopback, type: Host Loopback Path Id 1, oc_category: default
fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[1] (0x20002) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[1] (0x20002) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
fpc0 Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID 1 (URI: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[1])
fpc0 CMError: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[2] (0x20003), scope: pfe, category: functional, severity: major, module: Host Loopback, type: Host Loopback Path Id 2, oc_category: default
fpc0 Performing action get-state for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[2] (0x20003) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
fpc0 Performing action cmalarm for error /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[2] (0x20003) in module: Host Loopback with scope: pfe category: functional level: major, oc_category: default
fpc0 Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID 2 (URI: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[2])
fpc0 CMError: /fpc/0/pfe/0/cm/0/Host_Loopback/0/HOST_LOOPBACK_MAKE_CMERROR_ID[3] (0x20004), scope: pfe, category: functional, severity: major, module: Host Loopback, type: Host Loopback Path Id 3, oc_category: default
fpc0 T6E(0/0) link[3 0] DOWN, phy_link_ok: 0 mac_local_fault:1 mac_remote_fault: 0 asic_fault: 0
fpc0 T6E(0/0) link[4 0] DOWN, phy_link_ok: 0 mac_local_fault:1 mac_remote_fault: 0 asic_fault: 0
fpc0 T6E(0/0) link[5 0] DOWN, phy_link_ok: 0 mac_local_fault:1 mac_remote_fault: 0 asic_fault: 0
fpc0 T6E(0/0) link[6 0] DOWN, phy_link_ok: 0 mac_local_fault:1 mac_remote_fault: 0 asic_fault: 0
This error typically indicates a problem with the packet forwarding readiness from WAN interfaces to the host, causing the Host Loopback Path to be compromised.
Solution:
1. Check for Additional Errors:
-Look for the system uptime and FPC uptime.
>show chassis fpc details
-Check for any active alarms on the chassis related to the FPC.
>show chassis alarms
-Look for additional syslog events that might have triggered this error. Use the following commands:
>show log messages >show log chassisd
2. Inspect PFE (Packet Forwarding Engine) Status:
start shell network pfe <fpc#> show nvram show syslog messages exit
3.Restart the FPC:
request chassis fpc restart slot <slot-number>
Replace <slot-number> with the appropriate slot number for your FPC (e.g., fpc0).
<slot-number>
fpc0
If the issue persists after performing the above steps, contact Juniper Networks support for further assistance.