[j-nsp] j-series: EoMPLS vc goes mad after overheating ?

Alexandre Snarskii snar at snar.spb.ru
Mon Aug 31 12:01:15 EDT 2009


Hi!

May be it sounds crazy, but situation is repeated... 

After overheating (temperature on RE got to 54C/129F due to air 
condition failure), our j-2320 stopped to encapsulate unicast 
ethernet frames into EoMPLS vc.

Symptoms: DHCP over EoMPLS vc working (because requests sent 
broadcast), ARP works, but client is unable to ping gateway,
and on gateway I can see both DHCP and ARP(broadcast) packets 
but no pings(unicast). 
PPPoE client is able to receive offer (PADO), but gateway never 
sees PADR that is sent unicast. 
When trying to ping 255.255.255.255 over the link - other
side receives that packets (sent broadcast). 
More than, counter of received frames does not increments
when there should be unicast frames received, looks like
port does not hear unicast on this port anymore...

Well, first time when I saw such behaviour (also after overheating), 
reboot helped, and i considered it as 'curious madness', but now 
situation is repeated.. 

PS: J-2320, JunOS 9.3R3.8 "classic" (non-ES). Situation is 
on only one port, ge-0/0/3, other ports working well. 
However, ge-0/0/3 is configured for EoMPLS edge only, 
and other interfaces configured as IP/MPLS core and IP/L3VPN Edge,
so I cannot be sure is it hardware or software problem. 

PPS: configuration of ge-0/0/3 is pretty straightforward: 

snar at RT100-001> show configuration interfaces ge-0/0/3    
description "DOWNLINK EoMPLS";
vlan-tagging;
mtu 4470;
encapsulation extended-vlan-ccc;
unit 451 {
    vlan-id 451;
    family ccc;
}
unit 913 {
    vlan-id 913;
    family ccc;
}
unit 3007 {
    vlan-id 3007;
    family ccc;
}

all three vc's is up/up, and all three shows the same symptoms. 



More information about the juniper-nsp mailing list