[j-nsp] Juniper RPM - do not fragment
Hello everyone; I am trying to set up 1900 byte mtu tests using Juniper RPM. I am running into an issue where the packets are getting fragmented if the link does not support the MTU. Could not figure out a do-not-fragment knob for RPM. Has anyone had any success with these or any pointers for what I could try? I am using SNMP to create the tests and collect the data. Thank you, - Gaurav ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4550 L2Circuit/VPN to MX80/lt Interface SOLVED
So to end this thread with some kind of success :)
And to sum up what work and what didn't.
So basic l2circuit (CCC/Ldp signaling) between my EX and MX with lt
interface finally work with a config as simple as :
EX side :
ge-0/0/10 {
encapsulation ethernet-ccc;
unit 0 {
family ccc;
}
}
l2circuit {
neighbor 10.10.176.10 {
interface ge-0/0/10.0 {
virtual-circuit-id 10666;
no-control-word;
}
}
}
MX side :
lt-1/1/10 {
unit 0 {
encapsulation ethernet-ccc;
peer-unit 1;
family ccc;
}
unit 1 {
encapsulation ethernet;
peer-unit 0;
family inet {
address 10.1.1.6/24;
}
}
}
l2circuit {
neighbor 10.10.176.13 {
interface lt-1/1/10.0 {
virtual-circuit-id 10666;
no-control-word;
}
}
}
What's wrong with my EX was the interco between the EX and the next core
router. When It was tagged everything work (ISIS, MBGP, LDP, L3VPN),
except the l2circuit ?!
Even if it was a bad idea to use tagged interco it's a bit surprising
(and remember the original idea was to backhaul transit customer to core
with vlan).
Little experiment with EX4550 give me also some result I can share :
- l2circuit with vlan-ccc encapsulation work as well, but with a liltte
trick in the interface configuration on the ex-side (unless the
l2circuit report Encapsultion Invalid) ex :
ge-0/0/10 {
encapsulation vlan-ccc;
vlan-tagging;
unit 66 {
encapsulation vlan-ccc; this is redundant but needed
vland-id 66;
family ccc;
}
}
- connections ccc (rsvp based) seems to works as well, but I don't want
to use rsvp in my network by now.
- l2vpn ccc (bgp signalling) didn't work on EX, configuration passed
with ethernet-ccc encapsulation, not vlan-ccc so I think it was not
supported. This is uncool since I think it was the better approach.
Anyway the cool thing with l2circuit is that there was inter operable
with other vendor.
- vpls didn't work at all on EX4550 (but that's clear on the specsheat)
- l3vpn is quite limited in term of routing instance and route, but work.
Another things I try is to separate fib/rib to show how much route an
ex4550 can manage in his rib. OK I know this is bad idea :)
The answer is 300K route approx before rpd crash.
So no full view, even only in RIB.
After all this cheap switch was making his job. Good value for money.
Thks for all.
--
Raphael Mazelier
AS39605
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Juniper T640 FIB
Hi Guys, I am trying to find out what the FIB limits on the T640 are but as usual all the numbers that really matter are kept safe like nuclear launch codes by Juniper. I have googled around but didn't find anything but a post on this mailing list form 2011 which implies it depends on the type FPC's. Does anyone have any ideas about FIB/RIB limits on the T640 (current config is RE-2000s and FPC3-E's) or is anyone with a T640 in service willing to share their jtree memory usage stats? Thanks! Scott ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Juniper T640 FIB
Does anyone have any ideas about FIB/RIB limits on the T640 (current config is RE-2000s and FPC3-E's) or is anyone with a T640 in service willing to share their jtree memory usage stats? Possibly relevant, since they share the same architecture according to http://juniper.cluepon.net/index.php/Gibson_architecture, here is some info from one of our M320s with a full routing table: inet.0: 528834 destinations, 2124526 routes (528817 active, 16 holddown, 1 hidden) Direct: 10 routes, 9 active Local: 9 routes, 9 active BGP: 2123678 routes, 527971 active IS-IS:826 routes,825 active IGMP: 1 routes, 1 active PIM: 2 routes, 2 active It has FPC2s with 1G PICs in slots 0 and 3, and FPC3s with 10G PICs in slots 5,6 and 7. show jtree 1 memory shows very similar results for all of the slots: 0 M320-FPC2 16777216 bytes total 9226704 bytes used 7544624 bytes available (7508480 bytes from free pages) 3 M320-FPC2 16777216 bytes total 9226952 bytes used 7544360 bytes available (7507456 bytes from free pages) 5 M320-FPC3 16777216 bytes total 9226864 bytes used 7544464 bytes available (7507456 bytes from free pages) 6 M320-FPC3 16777216 bytes total 9227008 bytes used 7544320 bytes available (7510528 bytes from free pages) 7 M320-FPC3 16777216 bytes total 9226904 bytes used 7544416 bytes available (7507968 bytes from free pages) Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
