[j-nsp] Ignorant EX4200

Paul Stewart paul at paulstewart.org
Thu Feb 25 11:58:29 EST 2010


So when you do a commit (which you are obviously doing for it to survive a
reboot) then the interface doesn't come up?  Can you ping the interface once
committed?

Never seen this kind of behavior although just using EX4200's in the past
couple of months...

Paul


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Bjørn Tore
Sent: Thursday, February 25, 2010 11:48 AM
To: jnsp
Subject: [j-nsp] Ignorant EX4200

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;
    }
}

root at ex4200f <mailto:root at kg-trafo-ex>> show configuration interfaces vlan.2
family inet {
    address 10.20.13.2/24;
}

root at ex4200f <mailto:root at kg-trafo-ex>> show vlans sort-by tag
Name           Tag     Interfaces
default
                       ge-0/0/23.0
vlan10         10
                       ge-0/0/0.0*, ge-0/0/2.0, ge-0/0/3.0, ge-0/0/4.0
vlan20         20
                       ge-0/0/0.0*, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0,
                       ge-0/0/4.0
vlan21         21
                       ge-0/0/0.0*, ge-0/0/1.0, ge-0/0/2.0, ge-0/0/3.0,
                       ge-0/0/4.0
(...)

root at ex4200f <mailto:root at kg-trafo-ex>> show route

__juniper_private1__.inet.0: 4 destinations, 6 routes (1 active, 0
holddown, 3 )
+ = Active Route, - = Last Active, * = Both

128.0.0.0/2        *[Direct/0] 00:19:53
                    > via bme0.32768
                    [Direct/0] 00:19:53
                    > via bme0.32768
                    [Direct/0] 00:12:15
                    > via bme0.32768



A quick reboot did the trick:


root at ex4200f <mailto:root at kg-trafo-ex>> show route

inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/5] 00:00:13
                    > to 10.20.13.1 via vlan.20
10.0.0.0/8         *[Static/5] 00:00:16
                    > to 10.0.0.1 via vme.0
10.0.0.0/20        *[Direct/0] 00:00:16
                    > via vme.0
10.0.0.19/32       *[Local/0] 00:00:16
                      Local via vme.0
10.20.13.0/24      *[Direct/0] 00:00:13
                    > via vlan.20
10.20.13.2/32      *[Local/0] 00:00:16
                      Local via vlan.20




-- 
Bjørn Tore Paulen




_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp




More information about the juniper-nsp mailing list