Mailing List Archive

Issue with RX-4 running 02900b
A few questions if I may? or maybe you can point me in the right direction.

The FIB limit is 524288. What happens to excess routes? I understand they won't be installed into FIB but will traffic (Using a route not in FIB) have its traffic passed via software or not at all?

I'm having a bit of trouble getting IS-IS to stand to our existing Juniper core. I believe it is because IS-IS isn't using the interface MTU value. "hello padding" appears to be enabled by default but doesn't appear to work. Are there limiations to using IS-IS on L2 interfaces?

Interface : v55 Local Circuit Number: 00000002
Circuit Type : BCAST Circuit Mode : LEVEL-1-2
Circuit State: UP Passive State: FALSE
MTU : 1497

show int v55
<snip>
Internet address is 103.52.116.43/29, IP MTU 9174 bytes, encapsulation ethernet


Thanks

Carlos Alfaro Tech / Sales Support

Townsend Networks

35 Reed Blvd., Suite A Mill Valley, CA 94941

415-384-4208

mailto:carlos@townsendnetworks.com
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: Issue with RX-4 running 02900b [ In reply to ]
Hi Carlos,

As far as I know the router will drop traffic for prefixes that are not in the FIB rather than attempt to route packets in software. However, to keep everything predictable I'd recommend supplementing your BGP table with a default route to more capable routers and/or filter out more specific prefixes you don't need so as to reclaim FIB space.

Best regards,
Martijn

On 3 August 2015 21:34:03 CEST, Carlos Alfaro <Carlos@townsendnetworks.com> wrote:
>
>
>
>A few questions if I may? or maybe you can point me in the right
>direction.
>
>The FIB limit is 524288. What happens to excess routes? I understand
>they won't be installed into FIB but will traffic (Using a route not in
>FIB) have its traffic passed via software or not at all?
>
>I'm having a bit of trouble getting IS-IS to stand to our existing
>Juniper core. I believe it is because IS-IS isn't using the interface
>MTU value. "hello padding" appears to be enabled by default but doesn't
>appear to work. Are there limiations to using IS-IS on L2 interfaces?
>
>Interface : v55 Local Circuit Number: 00000002
> Circuit Type : BCAST Circuit Mode : LEVEL-1-2
> Circuit State: UP Passive State: FALSE
> MTU : 1497
>
>show int v55
><snip>
>Internet address is 103.52.116.43/29, IP MTU 9174 bytes, encapsulation
>ethernet
>
>
> Thanks
>
>Carlos Alfaro Tech / Sales Support
>
>Townsend Networks
>
>35 Reed Blvd., Suite A Mill Valley, CA 94941
>
>415-384-4208
>
>mailto:carlos@townsendnetworks.com
>_______________________________________________
>foundry-nsp mailing list
>foundry-nsp@puck.nether.net
>http://puck.nether.net/mailman/listinfo/foundry-nsp

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.