[j-nsp] Ignorant EX4200

Dan Farrell danno at appliedi.net
Thu Feb 25 14:03:49 EST 2010


I've seen the same behavior. Config your me0 interface, upgrade JUNOS, and you should be fine.

Dan
danno at appliedi.net


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Chuck Anderson
Sent: Thursday, February 25, 2010 12:00 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Ignorant EX4200

On Thu, Feb 25, 2010 at 05:47:47PM +0100, Bjørn Tore wrote:
> Somebody seen this behaviour? Seems that either the EX doesn't take the
> config until reboot, or that it silently ignores the IP config. Has
> happened with a couple of brand-new units.
>
> root at ex4200f <mailto:root at kg-trafo-ex>> show configuration interfaces vme
> unit 0 {
>    family inet {
>        address 10.0.0.19/20;
>    }
> }

Yes, I've seen this issue on the crappy version of JUNOS
(9.2-something) shipped from the factory on these boxes.  Sometimes
using me0 instead of vme makes it work, saving you the extra reboot
just so you can get newer JUNOS on there, at which point the bug is
gone and you can again use vme.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4895 (20100225) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4896 (20100225) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4896 (20100225) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com




More information about the juniper-nsp mailing list