Sub-interface e1's in this box flaps many times.
No service impact, but it seems abnormal.
May 3 19:15:25.795 2025 JTAC_RE0 mib2d[99642]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 1930, ifAdminStatus up(1), ifOperStatus down(2), ifName e1-0/2/3:1.0
May 3 19:16:38.247 2025 JTAC_RE0 mib2d[99642]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 1375, ifAdminStatus up(1), ifOperStatus down(2), ifName e1-0/2/3:59.0
May 3 19:18:00.010 2025 JTAC_RE0 mib2d[99642]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 1786, ifAdminStatus up(1), ifOperStatus down(2), ifName e1-0/2/3:14.0
May 3 19:18:42.973 2025 JTAC_RE0 mib2d[99642]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 1368, ifAdminStatus up(1), ifOperStatus down(2), ifName e1-0/2/3:52.0
May 3 19:18:43.073 2025 JTAC_RE0 mib2d[99642]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 1337, ifAdminStatus up(1), ifOperStatus down(2), ifName e1-0/2/3:13.0
Customer is using STM1 interface with 63 E1 interfaces, connected to TX equipment.
FPC 0 BUILTIN BUILTIN MPC BUILTIN
MIC 0 REV 08 750-045104 CAEJ6382 1xCOC12/4xCOC3 CH-CE
PIC 0 BUILTIN BUILTIN 1xCOC12/4xCOC3 CH-CE
Xcvr 0 REV 01 740-016063 PT41ZZF SFP-IR
When the E1 flaps, corresponding l2ckt flaps & we do not see this in logs.
The physical interface & E1 interface uptime is not hcanging with these flaps either.
We can add traceoptions at specific interface level & global interface level, to see what is happening in trace level when the interface goes down.
Note: Specific interface trace will be recorded in dcd logs.
set interfaces e1-<fpc/pic/port> traceoptions flag all
set interfaces traceoptions file int.txt files 10 size 5m
set interfaces traceoptions flag all
Customer observed that these sub-e1 is configured for the unused 2G BTS stations.
Every few minutes, the unused BTS station will send a signal to trigger down ckt on router, which bring down l2-vc connections & trigger down sub-e1 in the local PE.
Once customer removed the T-LDP sessions & the flaps were not seen anymore.