[j-nsp] OSPF default problem
Felix Schueren
felix.schueren at hosteurope.de
Tue Jan 20 04:30:20 EST 2009
that looks about right, assuming that 10.0.0.31 is your ex4200 (out of
curiosity, why do you manually set the router id? I usually just use a
"preferred" lo0 address).
Ah, I think I see it now.
10.0.0.0/23 is your transfer between 10.0.0.1 and 10.0.0.2, yes? So
10.0.0.1 will ARP for all the router loopbacks on the connection between
itself and the Ex4200 and will never route the packets toward the EX..
kind regards,
Felix
Cord MacLeod wrote:
> inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 0.0.0.0/0 *[OSPF/150] 02:34:38, metric 1, tag 0
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.0/23 *[OSPF/150] 08:26:48, metric 0, tag 0
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.13/32 *[Direct/0] 1d 23:32:36
> > via lo0.0
> 10.0.0.14/32 *[OSPF/10] 08:58:23, metric 2
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.31/32 *[OSPF/10] 08:58:32, metric 1
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.47/32 *[OSPF/10] 07:51:58, metric 2
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.48/30 *[Direct/0] 08:59:27
> > via ge-1/3/0.0
> 10.0.0.49/32 *[Local/0] 1d 23:41:16
> Local via ge-1/3/0.0
> 10.0.0.52/30 *[OSPF/10] 08:58:32, metric 2
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.56/30 *[OSPF/10] 07:51:48, metric 2
> > to 10.0.0.50 via ge-1/3/0.0
> 10.0.0.60/30 *[OSPF/10] 07:09:00, metric 2
> > to 10.0.0.50 via ge-1/3/0.0
> 224.0.0.5/32 *[OSPF/10] 1d 23:32:36, metric 1
> MultiRecv
>
>
>
> On Jan 20, 2009, at 12:28 AM, Felix Schueren wrote:
>
>> Cord MacLeod wrote:
>>> Below is a configuration for my ex4200. I'm trying to make it the
>>> gateway for all my traffic temporarily. All devices connected to it are
>>> running ospf, 2 m7s and another ex4200. All devices connected can hit
>>> all other devices on loopback and /30 addresses. However, only the
>>> switch with the configuration below can get to the internet. It is the
>>> only switch which can hit 10.0.0.1, all others cannot ping this address,
>>> they can however ping 10.0.0.2. Any ideas?
>>>
>>>
>>> version 9.3R2.8;
>>>
>>> ge-1/0/1 {
>>> unit 0 {
>>> family inet {
>>> address 10.0.0.2/23;
>>> }
>>> }
>>> }
>>> routing-options {
>>> static {
>>> route 0.0.0.0/0 {
>>> next-hop 10.0.0.1;
>>> retain;
>>> readvertise;
>>> metric 1;
>>> }
>>> }
>>> router-id 10.0.0.31;
>>> }
>>> protocols {
>>> ospf {
>>> export ospf_policy;
>>> area 0.0.0.0 {
>>> interface ge-0/0/23.0;
>>> interface ge-1/0/23.0;
>>> interface lo0.0 {
>>> passive;
>>> }
>>> interface ge-1/0/0.0;
>>> interface ge-0/0/0.0;
>>> }
>>> }
>>> lldp {
>>> interface all;
>>> }
>>> rstp;
>>> }
>>> policy-options {
>>> policy-statement ospf_policy {
>>> term term1 {
>>> from protocol static;
>>> then accept;
>>> }
>>> term term2 {
>>> from protocol direct;
>>> then accept;
>>> }
>>> }
>>> }
>>>
>>>
>>>
>>>
>>> inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
>>> + = Active Route, - = Last Active, * = Both
>>>
>>> 0.0.0.0/0 *[Static/5] 00:36:24, metric 1
>>>> to 10.0.0.1 via ge-1/0/1.0
>>> 10.0.0.0/23 *[Direct/0] 06:44:44
>>>> via ge-1/0/1.0
>>> 10.0.0.2/32 *[Local/0] 06:44:44
>>> Local via ge-1/0/1.0
>>> 10.0.0.13/32 *[OSPF/10] 07:00:20, metric 1
>>>> to 10.0.0.49 via ge-1/0/0.0
>>> 10.0.0.14/32 *[OSPF/10] 07:00:10, metric 1
>>>> to 10.0.0.53 via ge-0/0/0.0
>>> 10.0.0.31/32 *[Direct/0] 07:01:20
>>>> via lo0.0
>>> 10.0.0.47/32 *[OSPF/10] 05:10:42, metric 1
>>>> to 10.0.0.58 via ge-1/0/23.0
>>> to 10.0.0.62 via ge-0/0/23.0
>>> 10.0.0.48/30 *[Direct/0] 07:01:15
>>>> via ge-1/0/0.0
>>> 10.0.0.50/32 *[Local/0] 07:01:18
>>> Local via ge-1/0/0.0
>>> 10.0.0.52/30 *[Direct/0] 07:01:07
>>>> via ge-0/0/0.0
>>> 10.0.0.54/32 *[Local/0] 07:01:16
>>> Local via ge-0/0/0.0
>>> 10.0.0.56/30 *[Direct/0] 05:54:18
>>>> via ge-1/0/23.0
>>> 10.0.0.57/32 *[Local/0] 07:01:18
>>> Local via ge-1/0/23.0
>>> 10.0.0.60/30 *[Direct/0] 05:10:47
>>>> via ge-0/0/23.0
>>> 10.0.0.61/32 *[Local/0] 05:10:47
>>> Local via ge-0/0/23.0
>>> 224.0.0.5/32 *[OSPF/10] 07:01:22, metric 1
>>> MultiRecv
>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>> what does the routing table on one of the other devices look like?
>>
>> -felix
>>
>> --
>> Felix Schüren
>> Head of NOC
>>
>> ------------------------------------------------------------------
>> Host Europe GmbH - http://www.hosteurope.de
>> Welserstraße 14 - D-51149 Köln - Germany
>> Telefon: (0800) 4 67 83 87 - Telefax: (01805) 66 32 33
>> HRB 28495 Amtsgericht Köln - UST ID DE187370678
>> Geschäftsführer:
>> Uwe Braun - Alex Collins - Mark Joseph - Patrick Pulvermüller
>
>
--
Felix Schüren
Head of NOC
------------------------------------------------------------------
Host Europe GmbH - http://www.hosteurope.de
Welserstraße 14 - D-51149 Köln - Germany
Telefon: (0800) 4 67 83 87 - Telefax: (01805) 66 32 33
HRB 28495 Amtsgericht Köln - UST ID DE187370678
Geschäftsführer:
Uwe Braun - Alex Collins - Mark Joseph - Patrick Pulvermüller
More information about the juniper-nsp
mailing list