Re: [j-nsp] ssh-key issue / MX 16.1R5

2018-01-30 Thread Bjørn Skovlund
Hi, On Tue, Jan 30, 2018 at 11:06 AM, Theo Voss wrote: > Has anybody seen this behavior before? > Seen the same on 15.1X53-D57 for EX-3400. Reverted to D56 as we didn't have anything critically needed in D57, nor the time to chase down JTAC for it. Cheers, Bjorn

Re: [j-nsp] Fwd: MX80 Q-in-Q

2013-01-21 Thread Bjørn Skovlund
Your question is still a bit ambiguous. If you have an inner-list and want to bind it to a L3 interface, then you need to make a bridge domain and attach the IRB to that. Alternatively, depending on what you want, we're doing something along the lines of the below, where we bind customers

Re: [j-nsp] EX4200 Air Flow

2010-11-03 Thread Bjørn Skovlund
Hi Bill, We have around 80 EX-3200 (24 port RJ-45, with SFP module) and 30 EX-4200 (24 port SFP, with XFP module) in production. They're all located at telco pops, an environment with cooling, but not from the floor and also quite densely populated locations. Not ideal environment, so to say.

Re: [j-nsp] Stuck access-internal route

2010-09-10 Thread Bjørn Skovlund
Hi Nitzan, I hope it's OK I copy the list on your reply, as it was very useful to solve a single customer without impact on the rest. In short, it works this way! I'm still waiting on a servicewindow to solve the overall situation. Cheers, Bjørn 2010/9/9 Nitzan Tzelniker

[j-nsp] Stuck access-internal route

2010-09-09 Thread Bjørn Skovlund
Hi list, I've come across a situation on an MX where an access-internal route is stuck. I was hoping someone had an idea on how to clear it - my best bet so far is rebooting. I've tried clearing dhcp relay binding, but that's not possible as the entry is already out of the DB. Here's the

Re: [j-nsp] MPLS in the Access

2010-07-27 Thread Bjørn Skovlund
On Sat, Jul 24, 2010 at 3:27 AM, Pavel Lunin plu...@senetsy.ru wrote: Another approach can be a large VC ring of EX4200s built with VCE (ethernet) links: http://www.juniper.net/us/en/local/pdf/implementation-guides/8010045-en.pdf Seems to be a reasonable solution when scale of up to 9 nodes

[j-nsp] Multicast - missing S,G's upstream?

2010-07-21 Thread Bjørn Skovlund
Hi all, I have a problem with multicasting on my Brocade/Foundry MLX core (yes yes, I know I'm - so far - on the wrong maillist). It's a very simple PIM-SM on top of an OSPF topology. The problem is that after a while of running multicast fine, it suddenly freezes channels, leaving only the *,G

[j-nsp] MX commit time. was: EX 4200 stability with BGP and OSPF redistribution ?

2010-06-28 Thread Bjørn Skovlund
On Tue, Jun 22, 2010 at 9:38 AM, sth...@nethelp.no wrote: Guess you never had a heavily configured M10 or M20 if you think that 20 seconds is a long time to commit. I'll admit that I have gotten spoiled by the speed of the MX series, though. Yup - but how long will it stay that way? Juniper

[j-nsp] Filtering for the ARP database

2010-06-04 Thread Bjørn Skovlund
Hi all, I have a little issue with some MX-240s running static subscribers and some DHCP relay. The issue is that our subscribers (delviered in Q-in-Q) have a tendency to leak out their LAN side to the WAN - causing situations like this: b...@eca1-hoer show arp no-resolve | grep 192.168.1.1 |

Re: [j-nsp] Ewwwww/ ww

2010-06-01 Thread Bjørn Skovlund
I'm sure his cat will appreciate your response to its query. I don't know how often my cats have been renaming my folders, files and at times been writing emails - so far they have yet to send them though! But my cats are quite retarded. On Mon, May 31, 2010 at 11:15 PM, Dale Shaw

[j-nsp] EX and mirroring (ideally to GRE)

2010-05-07 Thread Bjørn Skovlund
Hi all, I was wondering if someone has found a good solution to remote mirror/analyze all traffic to/from a single IP? I see that GRE tunnels is now working, but setting it as output to an analyzer is not possible it seems. My Juniper rep. suggested a CCC, but buying 100+ AFLs doesn't seem

[j-nsp] DHCP relaying/snooping and proxy-arp on MX-240

2009-10-22 Thread Bjørn Skovlund
Hi, I got an MX-240 running JUNOS 9.6R1.13. This terminates layer 3 for a range of customers arriving in double-tagged VLANs like this: ge-0/0/1 { flexible-vlan-tagging; encapsulation flexible-ethernet-services; unit 567 { proxy-arp; vlan-tags outer 1310 inner 12;