Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Keegan Holley
On Dec 1, 2010, at 6:32 PM, "James S. Smith" wrote: > I don't see this as being possible. The whole point of OSPF is to provide > consistent routing data across all routers in the area. If Juniper allowed > filtering of internal routes being imported then that model could be broken. > Ev

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Phill Jolliffe
If your end goal is to prevent the ospf prefixes from becoming active in the PFE on a single chassis for then apply an export policy to the forwarding table under routing-options. The routes can sit active in the RIB but never make to the linecard. This is a dirty hack for several reason. Show rou

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Giuliano Cardozo Medalha
I have tested here. It does not work. I have tried to install a REJECT or DISCARD next-hop for OSPF Internal Routes. It does not work too. JUNOS does not support this features for OSPF Internal Routes, only IOS I was thinking trying to put some of the OSPF Internal routes in another

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Payam Chychi
is there a chance to use policy-statements here to accomplish this? say for example: from { protocol ospf route-type internal ... } then { reject; } ? -Payam Phill Jolliffe wrote: Only external LSA can be prevented from entering the RIB via ospf import policy. On Thu, Dec 2, 2010 at

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Giuliano Cardozo Medalha
Is it possible to put the internal LSA routes pointing to discard next-hop ? We need to invalidate some routes ... Or is not possible to process it ? Is it only possible to set priority to the route ? Thanks a lot, Only external LSA can be prevented from entering the RIB via ospf import pol

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread James S. Smith
I don't see this as being possible. The whole point of OSPF is to provide consistent routing data across all routers in the area. If Juniper allowed filtering of internal routes being imported then that model could be broken. Everything I've read say JunOS can't filter internal routes from be

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Phill Jolliffe
Only external LSA can be prevented from entering the RIB via ospf import policy. On Thu, Dec 2, 2010 at 12:10 AM, Giuliano Cardozo Medalha wrote: > People, > > Hi, > > We are trying to filter OSPF Internal Routers from being installed into the > RIB (Routing Table). > > JUNIPER has the correct c

Re: [j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Diogo Luiz Montagner
Hi Giuliano, This command allows you to filter external routes type only. Rgs Sent from my iPod On 02/12/2010, at 07:10, Giuliano Cardozo Medalha wrote: People, Hi, We are trying to filter OSPF Internal Routers from being installed into the RIB (Routing Table). JUNIPER has the corr

[j-nsp] OSPF IMPORT POLICIES

2010-12-01 Thread Giuliano Cardozo Medalha
People, Hi, We are trying to filter OSPF Internal Routers from being installed into the RIB (Routing Table). JUNIPER has the correct command to filter input routes. set protocols ospf import But when we create an import policy on our environment ... all the internal routes are not filtere

Re: [j-nsp] Files tcpdump of Junos on Wireshark.

2010-12-01 Thread David Lockuan
Thanks for all tips, i will test on my lab. After I will comment you. Best regards, On Wed, Dec 1, 2010 at 1:08 PM, Phill Jolliffe wrote: > l2-header option during capture? > > I know without real L2 headers are eaten by L chip/B chip/I chips > Lchip logic block. > > Maybe adding the switch he

Re: [j-nsp] Angry EX (STP?)

2010-12-01 Thread Corey Bryndal [PR]
Whilst I though we had awoken the Spanning-tree Gods, we were simply victim to a failed XFP upstream from EX4500#1 below. Observed frame errors inbound to the EX4500#1. When the link would fail, this msg would be found in the logs of EX4500#2. Exhale! Thx for the help! CB. On Dec 1, 2010, at

Re: [j-nsp] Angry EX (STP?)

2010-12-01 Thread Keegan Holley
I don't think the protocols are the problem. According to the log messages the link is actually flapping. Aug 25 12:13:36 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_DOWN: ifIndex 536, ifAdminStatus up(1), ifOperStatus down(2), ifName xe-0/0/16 Aug 25 12:41:11 ALBQ_EX4500 mib2d[861]: SNMP_TRAP_LINK_

Re: [j-nsp] Angry EX (STP?)

2010-12-01 Thread Will McLendon
CB, for STP to be detecting a loop, I assume either EX4500#1 is also directly connected to EX4500#3? or does it form a ring with the MX80 bridging between EX4500#1 and EX4500#3? if there is a physical loop, but not a logical one as I believe you stated all links are p2p VLANs, you could eithe