[j-nsp] High latency and slow connections
Blaz Zupan
blaz at inlimbo.org
Sat Nov 8 03:27:45 EST 2003
> > Where is the chip with the B3 label? EFPC or GigE?
> The B chip is on the FPC, which in the case of the M5 is build in to the
> FEB.
>
> If you have a E-FEB (show chassis hardward should say so if I remeber
> correct), you have the B3 chip.
We just put in the replacement M10 and are waiting for the traffic to go above
130 Mbps on the gigabit. Unfortunatelly saturday mornings are very slow going,
so we'll have to wait some time. The box is new, but the gigabit ethernet PIC
stayed the same. Unfortunatelly I found out the hard way that this M10 only
has the non-enhanced FEB. It's very badly documented, I only noticed because
the previously working configuration produced this:
blaz at maribor3> show interfaces queue ge-0/0/0
Queue statistics are not applicable to this interface.
So I started investigating and found out that the M10 has the non-E FEB (it
was bought used). Curiously enough, it accepted all the CoS commands from the
previous configuration which included queue priorities and DSCP marking, both
of which are unsupported on the non-E FEB according to www.juniper.net.
Even weirder, "show interface extensive" shows this:
...
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % bytes
0 data 55 550000000 55 0 low none
1 voice 20 200000000 20 0 high none
2 vpn 20 200000000 20 0 low none
3 network 5 50000000 5 0 high none
...
Look at the Priority column. This is what I have configured. But why is it
displayed, if the hardware does not support it? Anybody have a spare
FEB-M10-E-S that they're willing to trade for a FEB-M10-S? :-(
More information about the juniper-nsp
mailing list