[j-nsp] Outbound collision errors ?
Hi, This issue appears to be beyond the collective intellect of JTAC (I'm getting the usual wall of silence you get when the poor engineer is stumped !). So before I complain to Juniper and escalate to someone who knows their * from their elbow, I thought I would ask here first ! Mr Google is also not being particularly useful, apart from one potential hit saying its a hardware fault. Under show int stat detail on an EX4200, I'm seeing the following for a copper gige interface : Output errors: Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 33174940, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 I have swapped cables and ports on our side and it makes no difference, the outbound collisions are still rising. The carrier partner on the other side says they are seeing no errors whatsoever on their kit. We have tried both hard coding and autoneg, same result in both instances. Help ! ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Outbound collision errors ?
Hello, Before anything, make sure both ends have identical autoneg or duplex/speed settings. Also you can run a tdr test (request diagnostic tdr) from the EX. Christian. Le 15/10/2013 15:33, Ben a écrit : Hi, This issue appears to be beyond the collective intellect of JTAC (I'm getting the usual wall of silence you get when the poor engineer is stumped !). So before I complain to Juniper and escalate to someone who knows their * from their elbow, I thought I would ask here first ! Mr Google is also not being particularly useful, apart from one potential hit saying its a hardware fault. Under show int stat detail on an EX4200, I'm seeing the following for a copper gige interface : Output errors: Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 33174940, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 I have swapped cables and ports on our side and it makes no difference, the outbound collisions are still rising. The carrier partner on the other side says they are seeing no errors whatsoever on their kit. We have tried both hard coding and autoneg, same result in both instances. Help ! ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Peering Configuration
Thanks everyone for your on and off list replies, everyone's help has been greatly appreciated. This is the configuration I have come up with [1]. If anyone has any further input on this I'm all ears. Kind regards, James. [1] http://paste.org/flat/68022 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Outbound collision errors ?
On 15/10/2013 15:18, Christian de Balorre wrote: Hello, Before anything, make sure both ends have identical autoneg or duplex/speed settings. Also you can run a tdr test (request diagnostic tdr) from the EX. Christian. Will try a TDR test, forgot about that in all the troubleshooting mist ... ;-) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] EX2200 rate limiting per port ?
I'm looking for a small switch that can rate limit traffic in and out per port with a granularity of 5mb or less. Typical application would be ethernet distribution within a building where each office gets a (possibly different) amount of bandwidth. Can the EX2200 do this? Thanks, Joe ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
