VRP (R) software, Version 5.30 (NE40E&80E V300R002C02B21B).
TW_Customer has juniper routers and NE80E routers.
When they run traceroute 221.X.X.X from juniper routers towards NE80E. J company router shows MPLS Lables but when it passes through NE80E than NE80E do not show MPLS lables.
Below is the trace result showing label only at 1st hop which is Juniper router the second and third hop are Huawie routers where labels are now visible in the trace output
traceroute to 126.96.36.199 (188.8.131.52), 30 hops max, 40 byte packets
1 184.108.40.206 (220.127.116.11) 1.217 ms 1.174 ms 18.104.22.168 (22.214.171.124) 1.161 ms
MPLS Label=112528 CoS=0 TTL=1 S=1
2 126.96.36.199 (188.8.131.52) 1.917 ms 1.771 ms 2.187 ms
3 184.108.40.206 (220.127.116.11) 26.188 ms 46.677 ms 26.893 ms
Currently our devices do not support display mpls labels in traceroute. C and J company support this function.It's normal when traceroute segment send by juniper device passing through our router, our router will not respond icmp packet include mpls ldp label info.To control the generation of the time-to-live (TTL) field in the MPLS header when labels are first added to an IP packet, we can use command ttl propagate public or ttl propagate vpn on HUAWEI NE routers, but both of these two command can only affect local packets.
Cisco router can modify the behavior of ICMP reply to respond forwarded packets.
We should support these features as our competitor are already supports these features.