[j-nsp] Weird Port Problem

[Christian]

Just to be sure, if you want the port to be forced also disable auto-neg 
on the combo interface.
Looks like a duplex mismatch at first sight.

Christian


Le 21/10/2010 18:26, Paul Stewart a écrit :
> Hi there..
>
>
>
> We have a customer we migrated off a Cisco 7600 over to an MX480.
>
>
>
> Long story short we're having performance issues and have isolated it down
> to some questions ;)
>
>
>
> This is a 20GE+2X10GE linecard - customer port is using a copper 10/100/1000
> SFP.  Port is hard coded to 100/full on both sides.
>
>
>
>    MAC statistics:                      Receive         Transmit
>
>      Total octets                     586682576        135778876
>
>      Total packets                       616114           506951
>
>      Unicast packets                     616114           506616
>
>      Broadcast packets                        0              335
>
>      Multicast packets                        0                0
>
>      CRC/Align errors                      9895                0
>
>      FIFO errors                          10490                0
>
>      MAC control frames                       0                0
>
>      MAC pause frames                         0                0
>
>      Oversized frames                         0
>
>      Jabber frames                            0
>
>      Fragment frames                        682
>
>      VLAN tagged frames                       0
>
>      Code violations                          0
>
>    Filter statistics:
>
>      Input packet count                  616114
>
>      Input packet rejects                  9895
>
>      Input DA rejects                         0
>
>      Input SA rejects                         0
>
>      Output packet count                                  506951
>
>      Output packet pad count                                   0
>
>      Output packet error count                                 0
>
>      CAM destination filters: 0, CAM source filters: 0
>
>
>
>
>
> Opened ticket with JTAC and so far not getting anywhere despite requesting
> an escalation - they have been "analyzing" this for over 24 hours now with
> no idea.
>
>
>
> According to some docs, FIFO errors mean "replace the PIC immediately" which
> I find hard to believe - this could be a classic cat5 issue or an SFP issue
> but before knocking the customer down would rather get some feedback
> please..
>
>
>
> Customer side is a watchguard firewall unfortunately
>
>
>
> Thanks,
>
>
> Paul
>
>
>
>
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp