Re: [j-nsp] Policy to Manipulate the Local Preference of VPNV4 routes
Do you mean the same route being announced from two different PE's? A unique RD for each VPN on each PE will help. Then I assume you working with BGP import policy on the PE ... learning routes from the CE? On 30/05/2010, at 9:16 PM, Sorilla, Edmar (NSN - AE/Dubai) wrote: Hi Experts, Please share if you know how to manipulate local preference of vpnv4 route Thanks, Edmar ___ 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] Sampling filter with ifIndex
On Mon, May 31, 2010 at 11:20:10AM +0545, Ramesh Karki wrote: Hi, Thank you for your kind Response. The issue is on Sampling traffic filter by interface ?ifIndex? on JunOS 9.2 running on M10i. I have flow collector called ?RansNet MNA? running on my VM, it has many options to filter the traffic and get output, but I am having problem on ifIndex filter with few interfaces IDs. we are unable to get the data with the option Interface ID filter, RansNet show errors ?such record not found?. But SNMP---MRTG is okay on these interface. Even enabling local-dump on the router, flow on these interfaces (input/output)collect on ID 0 instead of correct iFindex ID. There was a really long-standing bug (my case was open for well over a year) where netflow ifindex fields would be incorrectly set to 0, and IIRC at least some versions of 9.2 were affected. Supposedly this was an I-chip specific issue though, and I don't think I-Chip based CFEBs were supported until 9.4, so it might not be related to your issue. Still, I'd be highly suspicious and try some newer code. We had some absolutely horrific experiences with bugs (both netflow, and otherwise) all throughout 9.2, and I THINK this one might not have been fixed until 9.3R3, but I try to repress those days so my memory may be a little foggy. -- 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] Policy to Manipulate the Local Preference of VPNV4 routes
Thanks for the prompt reply Truman. What about if the PE is peered to two route reflector and we want to manipulate the local preference to only one RR. Br, Edmar -Original Message- From: ext Truman Boyes [mailto:tru...@suspicious.org] Sent: Monday, May 31, 2010 10:56 AM To: Sorilla, Edmar (NSN - AE/Dubai) Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Policy to Manipulate the Local Preference of VPNV4 routes Do you mean the same route being announced from two different PE's? A unique RD for each VPN on each PE will help. Then I assume you working with BGP import policy on the PE ... learning routes from the CE? On 30/05/2010, at 9:16 PM, Sorilla, Edmar (NSN - AE/Dubai) wrote: Hi Experts, Please share if you know how to manipulate local preference of vpnv4 route Thanks, Edmar ___ 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] Logical Tunnels IPv6
Hi Chuck -
On Sun, May 30, 2010 at 09:01:10PM -0400, Chuck Anderson wrote:
Yes, and I believe the reason why this is the case is because
logical-tunnels use the same MAC address on each end. Since IPv6 uses
the MAC address to generate the link-local address by default, that
may be why they prevent you from configuring inet6 on lt.
Actually, with my setup, it looks like the MACs are unique. It
certainly reuses MAC addresses, but they are unique per peering of
logical interfaces. For example:
{master}
l...@mx240-lab01-re0 show arp
MAC Address Address Name Interface Flags
[...snip]
00:22:83:32:cd:35 10.0.4.110.0.4.1 lt-2/0/10.6 none
00:22:83:32:cd:34 10.0.4.210.0.4.2 lt-2/0/10.7 none
00:22:83:32:cd:34 10.0.4.510.0.4.5 lt-2/0/10.1 none
00:22:83:32:cd:35 10.0.4.610.0.4.6 lt-2/0/10.0 none
[...snip]
lt-2/0/10.0 and lt-2/0/10.1 are connected, and so are lt-2/0/10.6 and
lt-2/0/10.7. /30s.
For another data point, I've got an SRX 210 (10.1R1.8) doing something
similar, it just uses different addresses:
p...@orb show arp no-resolve
MAC Address Address Interface Flags
00:26:88:e9:54:80 10.3.7.160 lt-0/0/0.1 none
00:26:88:e9:54:81 10.3.7.161 lt-0/0/0.0 none
00:26:88:e9:54:81 10.3.7.162 lt-0/0/0.2 none
00:26:88:e9:54:80 10.3.7.163 lt-0/0/0.3 none
[...snip]
/31s.
At least for this (simple) setup, it shouldn't be a reason why IPv6
can't be used.
- Mark
--
Mark Kamichoff
p...@prolixium.com
http://www.prolixium.com/
signature.asc
Description: Digital signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] OSPF LFA and LDP LSPs
Hello, An update on this thread for anyone who might find it in the future. It appears the problem (or design) is with the traceroute mpls ldp command. It will test both the primary and backup LSP paths setup by OSPF LFA. Per JTAC, I simulated customer traffic over my lab network and the backup LSP path was never used. As a resolution to the case JTAC has agreed to update the traceroute command documentation. Serge - Original Message From: Serge Vautour sergevaut...@yahoo.ca To: Alex alex.arsen...@gmail.com; juniper-nsp@puck.nether.net Sent: Tue, March 16, 2010 3:25:38 PM Subject: Re: [j-nsp] OSPF LFA and LDP LSPs Hello, Well that command explains a few things. Thanks! I do want the LDP LSPs to follow the OSPF shortest path. I had never really noticed that the inet.3 table entries had a different metric than my inet.0 entries. That helped make the metrics match however I still have the same problem. Note the matching metrics: - se36...@pe1-stjhlab-re0 show route 10.10.80.2 logical-system PE10 detail inet.0: 34 destinations, 34 routes (34 active, 0 holddown, 0 hidden) 10.10.80.2/32 (1 entry, 1 announced) *OSPF Preference: 10 Next hop type: Router Next-hop reference count: 26 Next hop: 10.10.81.10 via xe-0/3/0.0 weight 0x1, selected Next hop: 10.10.81.23 via ge-1/3/3.0 weight 0xf000 State: Active Int Local AS: 855 Age: 8:04 Metric: 2 Area: 0.0.0.0 Task: OSPF Announcement bits (3): 2-LDP 3-KRT 5-Resolve tree 2 AS path: I inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden) 10.10.80.2/32 (1 entry, 1 announced) State: FlashAll *LDPPreference: 9 Next hop type: Router Next-hop reference count: 3 Next hop: 10.10.81.10 via xe-0/3/0.0 weight 0x1, selected Label operation: Push 300064 Next hop: 10.10.81.23 via ge-1/3/3.0 weight 0xf000 Label operation: Push 30 State: Active Int Local AS: 855 Age: 8:04 Metric: 2 --- Matches inet.0 Task: LDP Announcement bits (2): 2-Resolve tree 1 3-Resolve tree 2 AS path: I - The same problem exists: se36...@pe1-stjhlab-re0 show ldp route 10.10.80.2 logical-system PE10 Destination Next-hop intf/lspNext-hop address 10.10.80.2/32 xe-0/3/0.0 10.10.81.10 ge-1/3/3.0 10.10.81.23 se36...@pe1-stjhlab-re0 traceroute 10.10.80.2 no-resolve logical-system PE10 traceroute to 10.10.80.2 (10.10.80.2), 30 hops max, 40 byte packets 1 10.10.81.10 0.347 ms 0.268 ms 0.279 ms 2 10.10.80.2 36.471 ms 0.480 ms 0.436 ms se36...@pe1-stjhlab-re0 traceroute mpls ldp 10.10.80.2 no-resolve logical-system PE10 Probe options: ttl 64, retries 3, wait 10, paths 16, exp 7, fanout 16 ttlLabel ProtocolAddress Previous Hop Probe Status 1 300064 LDP 10.10.81.10 (null) Success 23 LDP 10.10.81.1 10.10.81.10 Egress Path 1 via xe-0/3/0.0 destination 127.0.0.64 ttlLabel ProtocolAddress Previous Hop Probe Status 1 30 LDP 10.10.81.23 (null) Success 23 LDP 10.10.81.20 10.10.81.23 Egress Path 2 via ge-1/3/3.0 destination 127.0.1.64 - Note that the LDP LSP is still taking both paths?!? Thanks, Serge - Original Message From: Alex alex.arsen...@gmail.com To: Serge Vautour se...@nbnet.nb.ca; juniper-nsp@puck.nether.net Sent: Tue, March 16, 2010 1:44:13 PM Subject: Re: [j-nsp] OSPF LFA and LDP LSPs Serge, Do you have track-igp-metric configured under LDP? I am pretty sure it does not since your OSPF and LDP metrics are different but I'd like to confirm. Please try to configure track-igp-metric for LDP and re-run MPLS traceroute. Rgds Alex - Original Message - From: Serge Vautour sergevaut...@yahoo.ca To: Clarke Morledge chm...@wm.edu; juniper-nsp@puck.nether.net Sent: Tuesday, March 16, 2010 2:54 PM Subject: Re: [j-nsp] OSPF LFA and LDP LSPs Hello, Thanks for your comments. I agree with your theory. It's my understanding as well. What I don't get is why the traceroute mpls ldp command uses both paths and yet traceroute ip uses 1 path. It's like the backup path is being used by the LDP LSP when it shouldn't be... Serge - Original Message From: Clarke Morledge chm...@wm.edu To: juniper-nsp@puck.nether.net Cc: Serge Vautour sergevaut...@yahoo.ca Sent: Tue, March 16, 2010 11:35:30 AM Subject:
[j-nsp] Ewwwww/ ww
Wwrwweqqqqqakwwxjkkkjajjkvkkpokllgzi ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ewwwww/ ww
Totally. On May 31, 2010 2:49 PM, Mike Teeman mike.tee...@gmail.com wrote: Wwrwweqqqqqakwwxjkkkjajjkvkkpokllgzi ___ 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] Ewwwww/ ww
Hi Mike, On Tue, Jun 1, 2010 at 4:36 AM, Mike Teeman mike.tee...@gmail.com wrote: Wwrwweqqqqqakwwxjkkkjajjkvkkpokllgzi That feature is currently scheduled for inclusion in in JUNOS 10.4. cheers, Dale ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] EX4200 24 SFP ports not showing
Hi, I have a EX4200 24 SFPs switch. When I try show interface terse only the port with SFP is shown. If I do a show inter ge-0/0/7 I get device not found if there is no SFP plugged in. Is it possible to change this? This is causing me trouble when I want to setup graphs for this switch. The interfaces don't show up in SNMP either. It would be nice to add all ports and as soon as I start using one port I'll get the graphs. Thanks, Olof ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 24 SFP ports not showing
Configure the other ports - even if it's just setting them to family Ethernet-switching for now ... this will cause them to show up and be part of the configuration Paul -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Olof Kasselstrand Sent: May-31-10 6:53 PM To: juniper-nsp Subject: [j-nsp] EX4200 24 SFP ports not showing Hi, I have a EX4200 24 SFPs switch. When I try show interface terse only the port with SFP is shown. If I do a show inter ge-0/0/7 I get device not found if there is no SFP plugged in. Is it possible to change this? This is causing me trouble when I want to setup graphs for this switch. The interfaces don't show up in SNMP either. It would be nice to add all ports and as soon as I start using one port I'll get the graphs. Thanks, Olof ___ 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] EX4200 24 SFP ports not showing
On Tue, Jun 01, 2010 at 08:52:53AM +1000, Olof Kasselstrand wrote: Hi, I have a EX4200 24 SFPs switch. When I try show interface terse only the port with SFP is shown. If I do a show inter ge-0/0/7 I get device not found if there is no SFP plugged in. Is it possible to change this? This is causing me trouble when I want to setup graphs for this switch. The interfaces don't show up in SNMP either. It would be nice to add all ports and as soon as I start using one port I'll get the graphs. On the EX-series the ports don't actually show up until you insert an optic (this is true for GE and 10GE on all EX's AFAIK). As soon as you do insert the SFP, the port will show up, and you'll start graphing it. This is really only a problem if you use some horrible SNMP poller with static ifindex mappings (like MRTG), in which case the answer should be to upgrade your SNMP poller as fast as is humanly possible. -- 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] EX4200 24 SFP ports not showing
You've been able to specify #some-int-name:community@IP|host[:2|3] as a target in MRTG for some time now. Static ifIndex mappings are soo last decade. David On 31 May 2010 19:57, Richard A Steenbergen r...@e-gerbil.net wrote: On Tue, Jun 01, 2010 at 08:52:53AM +1000, Olof Kasselstrand wrote: Hi, I have a EX4200 24 SFPs switch. When I try show interface terse only the port with SFP is shown. If I do a show inter ge-0/0/7 I get device not found if there is no SFP plugged in. Is it possible to change this? This is causing me trouble when I want to setup graphs for this switch. The interfaces don't show up in SNMP either. It would be nice to add all ports and as soon as I start using one port I'll get the graphs. On the EX-series the ports don't actually show up until you insert an optic (this is true for GE and 10GE on all EX's AFAIK). As soon as you do insert the SFP, the port will show up, and you'll start graphing it. This is really only a problem if you use some horrible SNMP poller with static ifindex mappings (like MRTG), in which case the answer should be to upgrade your SNMP poller as fast as is humanly possible. -- 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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
