Anecdotally, we have an MX480 with RE-2000 in a very similar space as
you're describing: taking in 4x full v4 tables, 3x full v6 tables, and a
chunk of v4 and v6 peering routes at a couple of exchanges. No issues.
--
Hugo
h...@slabnet.com: email, xmpp/jabber
PGP fingerprint (B178313E):
CF18 1
On 19 October 2015 at 17:33, james list wrote:
Hey James,
> I currently have a wan link between two MXs that sometimes is experiencing
> errors.
>
> I’ve on top of the link OSPF (timer 1/3) as routing protocol and I’d like
> to find out any possible way to exclude the link when errors are in pl
Dear Adam
Very interesting.
So you suggest to use OAM LFM to detect pkt loss and to put down physical
interface, then to use hold-time to wait the storm is gone and put again up
the interface after some secs/mins.
I'm not so familiar with OAM, how does it works on a metro ethernet link
provided b
Dear James,
You can use LFM to detect errors on the link
Edit protocols oam
ethernet {
link-fault-management {
action-profile detect-loss {
event {
link-adjacency-loss;
protocol-down;
}
action {
sy
If that's CRC errors which cause the OSPF across the link to flap, then
You could configure a RMON event with appropriate thresholds, the OID is
in the ifJnxTable:
aarseniev@labrouter> show snmp mib walk ifJnxTable ascii | grep crc
ifJnxInHslCrcErrors.1 = 0
ifJnxInHslCrcErrors.4 = 0
ifJnxInHslC
5 matches
Mail list logo
