[j-nsp] Unable to transmit traffic after software upgrade

[Gökhan Gümüş]

Hi George,

Actually my problem is how to identify it rather than looking at " monitor
interface ge-x/x/x " output for every single interface.
Because shut/ no shut is fixing my problem without changing vlan on customer
end.

Thanks and regards,
Gokhan Gumus

2011/4/7 George Vlachos <g.vlachos at kestrel-is.gr>

> Hello Gokhan,
>


> We had a similar case, and this happened when different vlan had been
> configured on the ends of the cirtuit.
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Gokhan Gumus
> Sent: Thursday, April 07, 2011 2:28 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Unable to transmit traffic after software upgrade
>
> Hi all,
>
> I need some advice.
> We are currently in a process of upgrading our Juniper MX960 series
> routers.
>
> Some of our customers are not able to transmit traffic after we performed
> maintenance.
> Circuits are connected as Layer2 circuit with ethernet-ccc configuration.
> It seems circuits are hanging off. It is not a negotiation issue first of
> all.
> After we shut/ no shut interfaces, customers are able to transmit traffic.
> This issue is not occuring on all Layer 2 ccc circuits.In order to
> determine
> which customer is not able to transmit traffic, either we need to monitor
> traffic on all interfaces or wait for customer complaints.
>
> My question is,
>
> Is there any other way to determine this situation?
>
> Thanks and regards,
> Gokhan Gumus
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>