Re: [j-nsp] Strange IS-IS Problem
-Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of Shane Ronan Sent: Tuesday, March 09, 2010 8:46 AM To: Chuck Anderson Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Strange IS-IS Problem On Mar 8, 2010, at 1:54 PM, Chuck Anderson wrote: I wonder if that is because the IS-IS Hello PDUs are being sent as Ethernet Multicast frames This had been my suspicion as well. Is it possible to disable igmp- snooping on the EX2500's? -Shane As a follow-up to this problem, the above is exactly what was happening and the switch was dropping them. The only workaround was to configure point-to-point. That said, this problem is going to be fixed in the next version of BladeOS. I have a pre-release version installed at the moment and it seems to work fine. -evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mar 8, 2010, at 1:54 PM, Chuck Anderson wrote: I wonder if that is because the IS-IS Hello PDUs are being sent as Ethernet Multicast frames This had been my suspicion as well. Is it possible to disable igmp- snooping on the EX2500's? -Shane ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
-Original Message- From: Stefan Fouant [mailto:sfou...@shortestpathfirst.net] Sent: Sunday, March 07, 2010 8:04 AM To: Eric Van Tol; juniper-nsp-boun...@puck.nether.net; Derick Winkworth; Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem I could be wrong but if I recall correctly the Hello PDU uses a padding TLV to pad the initial hello to the maximum MTU size. I don't believe these packets are fragmentable if I recall considering it's a CLNS frame, i.e. no IP header and thus no fragment options. I think it's already been said but the fact that you are using jumbo frames and also because you are using EX 2500s (not native JUNOS) makes it extremely suspect that you are likely running into some form of MTU issue. But if I can push through a baby giant packet without even configuring anything, wouldn't that mean that large packets are allowed through? One other thing you might want to check on the EX 2500 - interface counters - look for L2 Channel errors or other inconsistencies which might indicate the EX doesn't recognize the Ethertype, etc. I checked the various counter stats and could not find any errors on any of the ports. In fact, I see this: Received valid L2 unicast packets: 18473 Received valid IPv4 unicast packets: 18473 Received valid L2 multicast packets: 123024 Received valid non-IP multicast packets: 123000 Received valid IPv4 multicast packets: 24 Received 64 byte packets: 23 Received 65-127 byte packets: 123032 Received 128-255 byte packets: 1 Received 1024-1522 byte packets: 8393 Received 1523-2047 byte packets: 10048 Received octets: 48192973 Received octets in valid non-IP packets: 15127879 Received octets in valid IPv4 packets: 33065094 As an aside, it appears that OSPF works fine if I set that up. Not a long term solution, though. I do believe that you are on to something, though. Unfortunately, I can't see anywhere to configure the EX2500 ports to accept specific ethertypes. Does anyone else have ISIS running _through_ an EX2500? Stefan Fouant -evt --Original Message-- From: Eric Van Tol Sender: juniper-nsp-boun...@puck.nether.net To: Derick Winkworth To: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem Sent: Mar 7, 2010 4:42 AM From: Derick Winkworth [mailto:dwinkwo...@att.net] Sent: Sunday, March 07, 2010 1:26 AM To: Eric Van Tol; Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem If its JUNOS, then just configure the MTU normally in the interface config on the switch. It does not run JUNOS and there is no config option for MTU that I can find. I don't believe that it's configurable, but it just works. Without configuring anything on the EX2500, I was able to pass 2000-byte sized IP packets between the Junipers. -evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp Sent from my Verizon Wireless BlackBerry ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Sun, Mar 7, 2010 at 8:04 AM, Stefan Fouant sfou...@shortestpathfirst.net wrote: I could be wrong but if I recall correctly the Hello PDU uses a padding TLV to pad the initial hello to the maximum MTU size. I don't believe these packets are fragmentable if I recall considering it's a CLNS frame, i.e. no IP header and thus no fragment options. This is also my understanding. And, this makes me think that you really should make the MTUs on both sides consistent before you try to troubleshoot anything else. -Jon ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
Both MTUs are consistent and always have been. I started out with 9216 physical MTU and 1500 inet MTU, but have since just deleted the custom MTU and went with the defaults. I am quite sure now that this is not an MTU issue, but rather a deficiency with the EX2500. I've opened up a JTAC case and will let the list know what the problem turns out to be. -evt From: Jonathan Looney [mailto:jonloo...@gmail.com] Sent: Monday, March 08, 2010 10:57 AM To: Eric Van Tol Cc: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem On Sun, Mar 7, 2010 at 8:04 AM, Stefan Fouant sfou...@shortestpathfirst.netmailto:sfou...@shortestpathfirst.net wrote: I could be wrong but if I recall correctly the Hello PDU uses a padding TLV to pad the initial hello to the maximum MTU size. I don't believe these packets are fragmentable if I recall considering it's a CLNS frame, i.e. no IP header and thus no fragment options. This is also my understanding. And, this makes me think that you really should make the MTUs on both sides consistent before you try to troubleshoot anything else. -Jon ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
-Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of Eric Van Tol Sent: Monday, March 08, 2010 11:58 AM To: Jonathan Looney Cc: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem Both MTUs are consistent and always have been. I started out with 9216 physical MTU and 1500 inet MTU, but have since just deleted the custom MTU and went with the defaults. I am quite sure now that this is not an MTU issue, but rather a deficiency with the EX2500. I've opened up a JTAC case and will let the list know what the problem turns out to be. -evt Sorry for responding to my own post here. Another helpful tip came in to use 'point-to-point' in the ISIS config, which had been brought up before but never tried. It appears that this actually works. The person who suggested it also mentioned having similar problems on Force10 switches. Unfortunately, the point-to-point solution won't work for me in the long term :-( -evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mon, Mar 08, 2010 at 11:57:55AM -0500, Eric Van Tol wrote: Both MTUs are consistent and always have been. I started out with 9216 physical MTU and 1500 inet MTU, but have since just deleted the custom MTU and went with the defaults. I am quite sure now that this is not an MTU issue, but rather a deficiency with the EX2500. I've opened up a JTAC case and will let the list know what the problem turns out to be. But you didn't have the iso mtu set. Which means iso was probably using 9216-6-6-4-2-3 = 9195 (or 9192-6-6-4-2-3 = 9171) by default for a VLAN encapsulated 802.2 LLC frame. Changing the inet MTU doesn't affect any non-IP protocols' MTUs. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mon, Mar 08, 2010 at 12:51:33PM -0500, Eric Van Tol wrote: Sorry for responding to my own post here. Another helpful tip came in to use 'point-to-point' in the ISIS config, which had been brought up before but never tried. It appears that this actually works. The person who suggested it also mentioned having similar problems on Force10 switches. Unfortunately, the point-to-point solution won't work for me in the long term :-( Ah. I wonder if that is because the IS-IS Hello PDUs are being sent as Ethernet Multicast frames. L1 LAN Hellos, L2 LAN Hellos, and P2P Hellos use different destination Ethernet Multicast addresses that the EX2500 might not be flooding like it should. Or could it be that you have a Level or Area mismatch (I guess not because you haven't turned off any Levels, and Level 2 adjacencies don't require matching Area IDs)? What does monitor traffic interface xe-1/2/0 no-resolve layer2-headers extensive show? When I tested with and without point-to-point, I see the following: normal ethernet, Level 1 LAN Hello: 0:90:69:bc:2c:7e 1:80:c2:0:0:14, ethertype 802.1Q (0x8100), length 69: vlan 999, p 6, LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI NLPID IS-IS (0x83): length 48 L1 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0) normal ethernet, Level 2 LAN Hello: 0:90:69:bc:2c:7e 1:80:c2:0:0:15, ethertype 802.1Q (0x8100), length 75: vlan 999, p 6, LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI NLPID IS-IS (0x83): length 54 L2 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0) point-to-point, P2P Hello: 0:90:69:bc:2c:7e 9:0:2b:0:0:5, ethertype 802.1Q (0x8100), length 69: vlan 999, p 6, LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI NLPID IS-IS (0x83): length 48 p2p IIH, hlen: 20, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
-Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of Chuck Anderson Sent: Monday, March 08, 2010 12:55 PM To: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem On Mon, Mar 08, 2010 at 11:57:55AM -0500, Eric Van Tol wrote: Both MTUs are consistent and always have been. I started out with 9216 physical MTU and 1500 inet MTU, but have since just deleted the custom MTU and went with the defaults. I am quite sure now that this is not an MTU issue, but rather a deficiency with the EX2500. I've opened up a JTAC case and will let the list know what the problem turns out to be. But you didn't have the iso mtu set. Which means iso was probably using 9216-6-6-4-2-3 = 9195 (or 9192-6-6-4-2-3 = 9171) by default for a VLAN encapsulated 802.2 LLC frame. Changing the inet MTU doesn't affect any non-IP protocols' MTUs. Another person had previously suggested setting iso MTU, which I did, and that did not change anything. The issue seems to be that the EX2500 is dropping the ISIS hellos upon ingress. I've updated the JTAC case and they are attempting to replicate it in the lab. - evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mon, Mar 08, 2010 at 12:55:29PM -0500, Chuck Anderson wrote:
On Mon, Mar 08, 2010 at 11:57:55AM -0500, Eric Van Tol wrote:
Both MTUs are consistent and always have been. I started out with
9216 physical MTU and 1500 inet MTU, but have since just deleted the
custom MTU and went with the defaults. I am quite sure now that
this is not an MTU issue, but rather a deficiency with the EX2500.
I've opened up a JTAC case and will let the list know what the
problem turns out to be.
But you didn't have the iso mtu set. Which means iso was probably
using 9216-6-6-4-2-3 = 9195 (or 9192-6-6-4-2-3 = 9171) by default for
a VLAN encapsulated 802.2 LLC frame. Changing the inet MTU doesn't
affect any non-IP protocols' MTUs.
Just to confirm this I tested with a physical mtu 9192, family inet
mtu 1500 and no family iso mtu configured:
interfaces {
fe-1/0/0 {
vlan-tagging;
mtu 9192;
unit 999 {
vlan-id 999;
family inet {
mtu 1500;
}
family iso;
}
}
}
You can see that iso is using an MTU of 9171:
l...@main show interfaces fe-1/0/0 extensive | match mtu
Link-level type: Ethernet, MTU: 9192, Speed: 10m, Loopback: Disabled,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Protocol inet, MTU: 1500, Generation: 283, Route table: 3
Flags: User-MTU
Protocol iso, MTU: 9171, Generation: 282, Route table: 3
But even so, the Hellos don't look to be padded out to the MTU
(ethernet length is only 75):
0:90:69:bc:2c:7e 1:80:c2:0:0:15, ethertype 802.1Q (0x8100),
length 75: vlan 999, p 6, LLC, dsap OSI (0xfe) Individual, ssap OSI
(0xfe) Command, ctrl 0x03: OSI NLPID IS-IS (0x83): length 54
L2 Lan IIH, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0)
This contradicts what it says in the JNCIA Study Guide, page 291:
Therefore, each interface must support the transmission of the
maximum IS-IS PDU of 1492 bytes. To enforce this requirement, the
IS-IS Hello PDUs are padded to this maximum value. If the hello gets
to the neighboring router, the connecting interface supports the
maximum PDU size. Should the hello not be received by the neighboring
router, no adjacency forms and this link is not used by IS-IS.
I'm not seeing the IIH's being padded at all (JUNOS 8.4R3.3).
-Chuck, in the middle of preparing for the JNCIE exam.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
Only the first few hellos are padded, please see link from Jeff Doyle's ISIS OSPF book: http://gyazo.com/1b872a14f35bd27f859a722ecc3849c5.png (I have a hard copy of that book as well) -- Sergio Danelli JNCIE #170 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mon, Mar 08, 2010 at 01:43:57PM -0700, Sergio D. wrote: Only the first few hellos are padded, please see link from Jeff Doyle's ISIS OSPF book: http://gyazo.com/1b872a14f35bd27f859a722ecc3849c5.png (I have a hard copy of that book as well) I was testing with a not-yet-up adjacency, with no neighboring routers available. So these were initial hellos I was looking at. None were padded at all. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Mon, Mar 08, 2010 at 01:43:57PM -0700, Sergio D. wrote: Only the first few hellos are padded, please see link from Jeff Doyle's ISIS OSPF book: http://gyazo.com/1b872a14f35bd27f859a722ecc3849c5.png (I have a hard copy of that book as well) Of course most people claim isis hello padding is deprecated, including Juniper. :) http://www.nanog.org/meetings/nanog19/presentations/katz.ppt Also, turning on isis point-to-point also eliminates all of that DR election nonsense as well as getting rid of the pesky multicast hello packets which occasionally break things, but it's always a pain to remember to turn it on. Personally I wish there was just an interface unit level point-to-point flag you could set that told all associated protocols this was a p2p even if it's over ethernet. -- Richard A Steenbergen r...@e-gerbil.net http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
From: Derick Winkworth [mailto:dwinkwo...@att.net] Sent: Sunday, March 07, 2010 1:26 AM To: Eric Van Tol; Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem If its JUNOS, then just configure the MTU normally in the interface config on the switch. It does not run JUNOS and there is no config option for MTU that I can find. I don't believe that it's configurable, but it just works. Without configuring anything on the EX2500, I was able to pass 2000-byte sized IP packets between the Junipers. -evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
I could be wrong but if I recall correctly the Hello PDU uses a padding TLV to pad the initial hello to the maximum MTU size. I don't believe these packets are fragmentable if I recall considering it's a CLNS frame, i.e. no IP header and thus no fragment options. I think it's already been said but the fact that you are using jumbo frames and also because you are using EX 2500s (not native JUNOS) makes it extremely suspect that you are likely running into some form of MTU issue. One other thing you might want to check on the EX 2500 - interface counters - look for L2 Channel errors or other inconsistencies which might indicate the EX doesn't recognize the Ethertype, etc. Stefan Fouant --Original Message-- From: Eric Van Tol Sender: juniper-nsp-boun...@puck.nether.net To: Derick Winkworth To: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem Sent: Mar 7, 2010 4:42 AM From: Derick Winkworth [mailto:dwinkwo...@att.net] Sent: Sunday, March 07, 2010 1:26 AM To: Eric Van Tol; Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem If its JUNOS, then just configure the MTU normally in the interface config on the switch. It does not run JUNOS and there is no config option for MTU that I can find. I don't believe that it's configurable, but it just works. Without configuring anything on the EX2500, I was able to pass 2000-byte sized IP packets between the Junipers. -evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp Sent from my Verizon Wireless BlackBerry ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Strange IS-IS Problem
Hi all,
I've got a strange ISIS problem and I'm hoping another set of eyes can help me
identify what is wrong here. I've got an MX960 logically connected to a J2320
through two EX2500 switches:
MX960 == EX2500 == EX2500 == J2320
I'm simply trying to get ISIS working between the two routers and it's not
coming up. Traceoptions don't show anything out of the ordinary.
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.74/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface xe-1/2/0.1;
interface lo0.0 {
passive;
}
}
}
J2320:
ge-0/0/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.100/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.75/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface ge-0/0/0.1;
interface lo0.0 {
passive;
}
}
}
I can ping fine between the two:
r...@router1# run ping x.x.x.99 source x.x.x.100
PING x.x.x.99 (x.x.x.99): 56 data bytes
64 bytes from x.x.x.99: icmp_seq=0 ttl=64 time=4.890 ms
64 bytes from x.x.x.99: icmp_seq=1 ttl=64 time=2.098 ms
64 bytes from x.x.x.99: icmp_seq=2 ttl=64 time=2.095 ms
64 bytes from x.x.x.99: icmp_seq=3 ttl=64 time=2.130 ms
64 bytes from x.x.x.99: icmp_seq=4 ttl=64 time=4.217 ms
^C
--- x.x.x.99 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.095/3.086/4.890/1.217 ms
If I monitor traffic on either of the interfaces, I see ISIS packets leaving,
but nothing coming in. The EX2500s have a very vanilla config and I'm doing no
filtering on them.
Any ideas?
Thanks,
evt
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
Hi
- If you have an aggregate between switches, routers... make sure they
are correctly configured from both sides?
- Also Try to check duplex.
- Is there is possibility to connect the routers directly? This will
isolate the problem.
Best Regards,
Walaa Abdel Razzak
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Eric Van Tol
Sent: Saturday, March 06, 2010 3:54 PM
To: Juniper-Nsp
Subject: [j-nsp] Strange IS-IS Problem
Hi all,
I've got a strange ISIS problem and I'm hoping another set of eyes can
help me identify what is wrong here. I've got an MX960 logically
connected to a J2320 through two EX2500 switches:
MX960 == EX2500 == EX2500 == J2320
I'm simply trying to get ISIS working between the two routers and it's
not coming up. Traceoptions don't show anything out of the ordinary.
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.74/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface xe-1/2/0.1;
interface lo0.0 {
passive;
}
}
}
J2320:
ge-0/0/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.100/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.75/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface ge-0/0/0.1;
interface lo0.0 {
passive;
}
}
}
I can ping fine between the two:
r...@router1# run ping x.x.x.99 source x.x.x.100
PING x.x.x.99 (x.x.x.99): 56 data bytes
64 bytes from x.x.x.99: icmp_seq=0 ttl=64 time=4.890 ms
64 bytes from x.x.x.99: icmp_seq=1 ttl=64 time=2.098 ms
64 bytes from x.x.x.99: icmp_seq=2 ttl=64 time=2.095 ms
64 bytes from x.x.x.99: icmp_seq=3 ttl=64 time=2.130 ms
64 bytes from x.x.x.99: icmp_seq=4 ttl=64 time=4.217 ms
^C
--- x.x.x.99 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.095/3.086/4.890/1.217 ms
If I monitor traffic on either of the interfaces, I see ISIS packets
leaving, but nothing coming in. The EX2500s have a very vanilla config
and I'm doing no filtering on them.
Any ideas?
Thanks,
evt
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
__ Information from ESET Smart Security, version of virus
signature database 4920 (20100306) __
The message was checked by ESET Smart Security.
http://www.eset.com
__ Information from ESET Smart Security, version of virus
signature database 4920 (20100306) __
The message was checked by ESET Smart Security.
http://www.eset.com
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
What happens when you reduce the physical MTUs on the MX and the J-Series to
something smaller? Same behavior?
Stefan Fouant
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Eric Van Tol e...@atlantech.net
Date: Sat, 6 Mar 2010 07:53:41
To: Juniper-Nspjuniper-nsp@puck.nether.net
Subject: [j-nsp] Strange IS-IS Problem
Hi all,
I've got a strange ISIS problem and I'm hoping another set of eyes can help me
identify what is wrong here. I've got an MX960 logically connected to a J2320
through two EX2500 switches:
MX960 == EX2500 == EX2500 == J2320
I'm simply trying to get ISIS working between the two routers and it's not
coming up. Traceoptions don't show anything out of the ordinary.
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.74/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface xe-1/2/0.1;
interface lo0.0 {
passive;
}
}
}
J2320:
ge-0/0/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.100/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.75/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface ge-0/0/0.1;
interface lo0.0 {
passive;
}
}
}
I can ping fine between the two:
r...@router1# run ping x.x.x.99 source x.x.x.100
PING x.x.x.99 (x.x.x.99): 56 data bytes
64 bytes from x.x.x.99: icmp_seq=0 ttl=64 time=4.890 ms
64 bytes from x.x.x.99: icmp_seq=1 ttl=64 time=2.098 ms
64 bytes from x.x.x.99: icmp_seq=2 ttl=64 time=2.095 ms
64 bytes from x.x.x.99: icmp_seq=3 ttl=64 time=2.130 ms
64 bytes from x.x.x.99: icmp_seq=4 ttl=64 time=4.217 ms
^C
--- x.x.x.99 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.095/3.086/4.890/1.217 ms
If I monitor traffic on either of the interfaces, I see ISIS packets leaving,
but nothing coming in. The EX2500s have a very vanilla config and I'm doing no
filtering on them.
Any ideas?
Thanks,
evt
___
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] Strange IS-IS Problem
Are the EX2500's configured for jumbos?
-b
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Stefan Fouant
Sent: Saturday, March 06, 2010 6:41 AM
To: Eric Van Tol; juniper-nsp-boun...@puck.nether.net; Juniper-Nsp
Subject: Re: [j-nsp] Strange IS-IS Problem
What happens when you reduce the physical MTUs on the MX and the J-Series to
something smaller? Same behavior?
Stefan Fouant
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Eric Van Tol e...@atlantech.net
Date: Sat, 6 Mar 2010 07:53:41
To: Juniper-Nspjuniper-nsp@puck.nether.net
Subject: [j-nsp] Strange IS-IS Problem
Hi all,
I've got a strange ISIS problem and I'm hoping another set of eyes can help me
identify what is wrong here. I've got an MX960 logically connected to a J2320
through two EX2500 switches:
MX960 == EX2500 == EX2500 == J2320
I'm simply trying to get ISIS working between the two routers and it's not
coming up. Traceoptions don't show anything out of the ordinary.
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.74/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface xe-1/2/0.1;
interface lo0.0 {
passive;
}
}
}
J2320:
ge-0/0/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.100/28;
}
family iso;
}
}
lo0 {
unit 0 {
family inet {
address 127.0.0.1/32;
address x.x.x.75/32;
}
family iso {
address 47.0001....00;
}
}
}
...
protocols {
isis {
interface ge-0/0/0.1;
interface lo0.0 {
passive;
}
}
}
I can ping fine between the two:
r...@router1# run ping x.x.x.99 source x.x.x.100
PING x.x.x.99 (x.x.x.99): 56 data bytes
64 bytes from x.x.x.99: icmp_seq=0 ttl=64 time=4.890 ms
64 bytes from x.x.x.99: icmp_seq=1 ttl=64 time=2.098 ms
64 bytes from x.x.x.99: icmp_seq=2 ttl=64 time=2.095 ms
64 bytes from x.x.x.99: icmp_seq=3 ttl=64 time=2.130 ms
64 bytes from x.x.x.99: icmp_seq=4 ttl=64 time=4.217 ms
^C
--- x.x.x.99 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.095/3.086/4.890/1.217 ms
If I monitor traffic on either of the interfaces, I see ISIS packets leaving,
but nothing coming in. The EX2500s have a very vanilla config and I'm doing no
filtering on them.
Any ideas?
Thanks,
evt
___
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
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Sat, Mar 06, 2010 at 07:53:41AM -0500, Eric Van Tol wrote:
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
Can you try configuring family iso mtu 1500?
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Strange IS-IS Problem
On Sat, Mar 06, 2010 at 11:06:16AM -0500, Chuck Anderson wrote:
On Sat, Mar 06, 2010 at 07:53:41AM -0500, Eric Van Tol wrote:
MX960:
xe-1/2/0 {
vlan-tagging;
mtu 9192;
unit 1 {
vlan-id 1;
family inet {
mtu 1500;
address x.x.x.99/28;
}
family iso;
}
}
Can you try configuring family iso mtu 1500?
Actually, you may need mtu 1497:
http://www.juniper.net/techpubs/software/junos/junos56/swconfig56-interfaces/html/interfaces-physical-config5.html
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
