[j-nsp] PE-4FE-TX not transmitting anything...faulty?
Jonas Frey
jf at probe-networks.de
Mon Apr 16 17:43:09 EDT 2007
Ebben,
it sounds related but i am not sure if it really is.
When i run monitor traffic interface fe...
i do see incoming packets and i do see that the interface is (trying to)
transmitting arp replys:
23:37:47.921802 Out arp reply x.x.x.x is-at 0:90:69:53:79:1b
However this does never arrive at the remote station nor does it
increase the transmit packet counter. It seems the software is doing
everything it should but the hardware is (silently) dropping the
packets.
I also do not have "drops" on the interface:
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards:
9822, L3 incompletes: 682, L2 channel errors: 0, L2 mismatch timeouts:
0, FIFO errors: 0,
Resource errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged
packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0,
Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped
packets
0 best-effort 150 150 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
As you can see...the queue counters say there has been something
transmitted but on the other hands the MAC says it didnt:
MAC statistics: Receive Transmit
Total octets 32422297 0
Total packets 504050 0
Unicast packets 1811 0
Broadcast packets 493497 0
Multicast packets 8742 0
CRC/Align errors 0 0
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Very strange....
Regarding your problem: I bet cycling (request... off/on) the pic will
do the job.
Regards,
Jonas
On Mon, 2007-04-16 at 23:30, Ebben Aries wrote:
> I have ran into this regarding my post on 3/29. Attached is a copy of the
> thread.
>
> My problem however was only with 1 port on the P-4FE-TX. I have not had the
> chance to power cycle the PIC or swap into a different FPC as of yet. Are
> you seeing the drop counters increase at all or just no traffic sent at all?
> Also, are you seeing any RE bound traffic attempting to be sent when you
> issue 'monitor traffic interface fe-x/x/x' ?
>
> Anyone else out there ran into this? I am also anxiously awaiting any
> insight.
>
> Thanks,
>
> Ebben
>
>
> ----
>
> From:
> Ebben Aries <earies at uci.net> (United Communications, Inc.)
> To:
> juniper-nsp at puck.nether.net
> Date:
> 2007-03-29 1:09 pm
>
> Hello all,
>
> This is a weird one...... I have a P-4FE-TX that has one interface that is
> displaying the following.
>
> Output errors:
> Carrier transitions: 0, Errors: 0, Drops: 29052, Collisions: 0, Aged
> packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource
> errors: 0
> Egress queues: 4 supported, 4 in use
> Queue counters: Queued packets Transmitted packets Dropped packets
> 0 best-effort 3278 0 0
> 1 expedited-forwarding 0 0 0
> 2 assured-forwarding 0 0 0
> 3 network-control 29782 0 29052
>
> This is strictly a p2p ethernet link that was working until the
> following...... This interface was put into an 802.3ad bundle attached to
> ae0.0 (this is when it started to drop everything). The interface was then
> removed and now displays the above.
>
> It appears that BE is neither transmitting nor dropping the packets while
> network-control is dropping virtualy everything. The interface can RX
> traffic just fine.
>
> BTW, other interfaces on the same P-4FE-TX work fine and there are no firewall
> filters attached to this interface.
>
> Anyone ran into this before ??
>
> --
>
> Ebben
>
>
>
>
> On Monday 16 April 2007 1:48 pm, Jonas Frey wrote:
> > Hello,
> >
> > i've got a PE-4FE-TX here which is not working, it is receiving traffic
> > but not transmitting anything.
> > See below:
> > MAC statistics: Receive Transmit
> > Total octets 26985313 0
> > Total packets 419556 0
> > Unicast packets 1458 0
> > Broadcast packets 411000 0
> > Multicast packets 7098 0
> > CRC/Align errors 0 0
> > FIFO errors 0 0
> > MAC control frames 0 0
> > MAC pause frames 0 0
> > Oversized frames 0
> > Jabber frames 0
> > Fragment frames 0
> > VLAN tagged frames 0
> > Code violations 0
> > Filter statistics:
> > Input packet count 419556
> > Input packet rejects 0
> > Input DA rejects 8556
> > Input SA rejects 0
> > Output packet count 0
> > Output packet pad count 0
> > Output packet error count 0
> > CAM destination filters: 1, CAM source filters: 0
> >
> > I've tried everything to get this pic to send out anything...
> > It seems it does receive packets but its not transmitting anything. It
> > doesnt matter what port i use, none works.
> >
> > I've tried various devices, duplex/speed settings, tried the PIC in
> > various FPCs and even in various M-series.
> >
> > Does anyone have any idea how i can debug this further or did anyone
> > happen to run into the same problem?
> >
> > Regards,
> > Jonas Frey
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list