Ethernet Switching
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 20
Registered: ‎08-10-2009
0
Accepted Solution

Redundant MAN connections between two EX Stacks

I'm trying to understand the configuration options for routing between two separate EX stacks connected through a MAN Ethernet connection...

 

Currently... I have two connections, one 200Mbit and a second thats 100Mbit  connecting to remote buildings together.  I have static routes setup currently on each switch like so:

 

----Core

static {
    route 10.6.0.0/16 {
        qualified-next-hop 10.6.1.6 {
            metric 10;
        }
        qualified-next-hop 10.6.1.2 {
            metric 100;
        }
    }
}

 

--- Remote Office

static {
    route 0.0.0.0/0 {
        qualified-next-hop 10.6.1.5 {
            metric 10;
        }
        qualified-next-hop 10.6.1.1 {
            metric 100;
        }
    }
}

Which routing protocol should I use to make the link failover between the two lines based on complete link state... I was looking at OSPF and is-is but... from the examples online I'm not seeing how to configure them correctly.

Recognized Expert
Posts: 392
Registered: ‎01-05-2008

Re: Redundant MAN connections between two EX Stacks

Hi,

 

OSPF should be fine (IS IS needs an extra license). The only thing that we have to take into account is that OSPF needs different interfaces for different links. That means that the primary link should be connected to a different interface as the backup link.

 

I would suggest, you configure these uplink interfaces as layer 3 interfaces. Let's say you use ge-0/0/0 as the uplink for the primary and ge-0/0/1 as uplink for the backup.

 

then you sould configure

 

interfaces {
    ge-0/0/0 {
        unit 0 {
            family inet {
                address 10.6.1.17/30;
            }
        }
    }
    ge-0/0/1 {
        unit 0 {
            family inet {
                address 10.6.1.5/30;
            }
        }
    }

}

 

Then you can activate OSPF on these interfaces. We have just on thing to consider: Both interfaces have equal cost from OSPF point of view. That these line are rate limited by the provider is not obvious to the switch/router. We have to manually adjust the metrics:

 

protocols {
    ospf {
        area 0.0.0.0 {
            interface ge-0/0/0.0 {
                metric 10;
            }
            interface ge-0/0/1.0 {
                metric 20;
            }
        }
    }
}

 

You could also consider using authentication with OSPF. Or you could activate BFD for fast link down detection.

 

On your other switch, you have to mirror your configuration.

 

I hope this helps.

 

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

Thanks for the detailed reply.  How are the proper routes transfered?

 

the one side only needs to know how to go to 0.0.0.0, but the core side only needs to know that anything 10.6.0.0/16 is accross those links?  How does OSPF know about the local networks on the remote side?  or is that just something built into it... and its going to work as you put it? 

Recognized Expert
Posts: 392
Registered: ‎01-05-2008
0

Re: Redundant MAN connections between two EX Stacks

[ Edited ]

Hi,

 

OSPF is a link state protocol. That means, all routers within the same area have to maintain the same graph where the shortest path algorithm runs on.

 

If you want to filter routers, you can introduce areas different to the root area (id 0), let's say area 1, 2 and so on. So you could put your remote office router/switch in area 1 and your main office router in area 0. The be accorate, you put the interfaces facing the remote side into area 1 in the main office and you have to assign at least one interface into area 0, possibly a loopback interface.

 

If a router belongs to more then one area, it is called an area border router (ABR). On an ABR you can do filtering. If you want that the router in the rmeote office receives only a default route, area 1 would be called totally stub area. On the other hand, in area 0 you will still find the routes of area 1.

 

To explain everything in detail would exceed the possibilities of this thread. But you should be able continue working with this.

 

Here is a short example:

 

protocols {
    ospf {
        area 0.0.0.0 {
            interface lo0.0 {
                passive;
            }
        }
        area 0.0.0.1 {
            stub default-metric 10 no-summaries;
            interface ge-0/0/0.0 {
                metric 10;
            }
            interface ge-0/0/1.0 {
                metric 20;
            }
        }
    }
}

On your router in the remote area, you have to just mention the stub statement, without the default metric and no-summaries verbs.

 

I hope this helps a bit.

 

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

I did this... however I never saw any routes get pushed to either side... how are the routes published?

 

Recognized Expert
Posts: 392
Registered: ‎01-05-2008
0

Re: Redundant MAN connections between two EX Stacks

Does the OSPF adjacency get established? You can verify this by issuing a show ospf interface command in operational mode.

 

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

This is what I have currently on both switches:

 

> show ospf interface
Interface           State   Area            DR ID           BDR ID          Nbrs
ge-1/0/1.0          DR      0.0.0.1         10.2.1.254      0.0.0.0            0
ge-3/0/8.0          DR      0.0.0.1         10.2.1.254      0.0.0.0            0

 

> show ospf interface
Interface           State   Area            DR ID           BDR ID          Nbrs
ge-0/0/0.0          DR      0.0.0.1         10.6.1.2        0.0.0.0            0
ge-1/0/2.0          DR      0.0.0.1         10.6.1.2        0.0.0.0            0

 

 

Recognized Expert
Posts: 392
Registered: ‎01-05-2008
0

Re: Redundant MAN connections between two EX Stacks

Hi,

 

first, there must always be a root area in OSPF (=area with id 0). Different areas with id > 0 can be created,e.g. to reduce the size of the link state database, to filter out routes etc. As it seems you don't have other OSPF enabled interfaces, please change your area id from 1 to 0 on both routers.

 

You can see from the column neighbor, that no interface has established an adjacency to its neighbor. If this remains the same once you change the area id to 0 we can do the following checks:

 

I assume, that the virtual chassis stacks are connected this way:

 

VC1             VC2

 

ge-1/0/1 <-> ge-0/0/0

ge-3/0/8 <-< ge-1/0/2

 

First verify the link between the two interfaces by using ping and specify the IP address of the remote if as target and the local IP address of the link interface as source. And vice verse, for both links.

 

Then verify the MTU on both interfaces. They must match so that a adjacancy can be formed. The MTU size is displayed when issuing a show interface ge-x/y7z command in the third line.

 

If even these three steps don't help, we have to make use of the traceoptions. Issue these commands on both VC stacks and then post the content of the trace file:

 

set protocols ospf traceoptions file ospf.debug
set protocols ospf traceoptions flag hello detail
set protocols ospf traceoptions flag error detail

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

I think we are almost there...

 

mitcha@mkt-core# run show ospf route
Topology default Route Table:

Prefix             Path  Route      NH       Metric NextHop       Nexthop      
                   Type  Type       Type            Interface     Address/LSP
10.6.1.2           Intra Router     IP           10 ge-1/0/1.0    10.6.1.6
10.6.1.0/30        Intra Network    IP           20 ge-3/0/8.0
10.6.1.4/30        Intra Network    IP           10 ge-1/0/1.0

 

I'm seeing some routes now... they aren't showing up in the actual routing table... nor is the default route showing up on the remote switch...

 

mitcha@pnt-sw01# run show ospf neighbor
Address          Interface              State     ID               Pri  Dead
10.6.1.1         ge-0/0/0.0             Full      10.2.1.254       128    34
10.6.1.5         ge-1/0/2.0             Full      10.2.1.254       128    32

{master:0}[edit]
mitcha@pnt-sw01# run show ospf interface
Interface           State   Area            DR ID           BDR ID          Nbrs
ge-0/0/0.0          DR      0.0.0.0         10.6.1.2        10.2.1.254         1
ge-1/0/2.0          DR      0.0.0.0         10.6.1.2        10.2.1.254         1

{master:0}[edit]
mitcha@pnt-sw01# run show ospf route        
Topology default Route Table:

Prefix             Path  Route      NH       Metric NextHop       Nexthop      
                   Type  Type       Type            Interface     Address/LSP
10.2.1.254         Intra Router     IP           10 ge-1/0/2.0    10.6.1.5
10.6.1.0/30        Intra Network    IP           20 ge-0/0/0.0
10.6.1.4/30        Intra Network    IP           10 ge-1/0/2.0

 

The correct connection topology is:

 

VC1(mkt-core)   VC2(pnt-sw01)

 

ge-1/0/1 <-> ge-1/0/2

ge-3/0/8 <-< ge-0/0/0

 

 

mkt-core having many 10.x/16 networks on it including being the gateway out... and pnt-sw01 having the 10.6.0.0/16 network, with the mkt-core switch being its gateway.

 

I'm adding the trace options, I will post those results in a bit.

Recognized Expert
Posts: 392
Registered: ‎01-05-2008
0

Re: Redundant MAN connections between two EX Stacks

Hi,

 

if the routes your are missing are e.g. static routes, you won't see them on the other stack unless you export them into OSPF that transport it to its neighbors!

 

I can give you an example if you tell me what routes you like to leak into OSPF. All static ones?

 

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

Here is the tracelog from the mkt-core switch:

 

mitcha@mkt-core> show log ospf.debug
Jul 11 09:07:35 trace_on: Tracing to "/var/log/ospf.debug" started
Jul 11 09:07:35.952640 OSPF sent Hello 10.6.1.5 -> 224.0.0.5 (ge-1/0/1.0 IFL 182 area 0.0.0.0)
Jul 11 09:07:35.954194   Version 2, length 48, ID 10.2.1.254, area 0.0.0.0
Jul 11 09:07:35.954242   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:35.954601   dead_ivl 40, DR 10.6.1.6, BDR 10.6.1.5
Jul 11 09:07:35.955186 OSPF sent Hello 10.6.1.1 -> 224.0.0.5 (ge-3/0/8.0 IFL 230 area 0.0.0.0)
Jul 11 09:07:35.955226   Version 2, length 48, ID 10.2.1.254, area 0.0.0.0
Jul 11 09:07:35.955248   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:35.955954   dead_ivl 40, DR 10.6.1.2, BDR 10.6.1.1
Jul 11 09:07:35.958656 OSPF DR is 10.6.1.2, BDR is 10.2.1.254
Jul 11 09:07:35.960777 OSPF sent Hello 10.6.1.5 -> 224.0.0.5 (ge-1/0/1.0 IFL 182 area 0.0.0.0)
Jul 11 09:07:35.960837   Version 2, length 48, ID 10.2.1.254, area 0.0.0.0
Jul 11 09:07:35.960860   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:35.960880   dead_ivl 40, DR 10.6.1.6, BDR 10.6.1.5
Jul 11 09:07:36.011184 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:36.011430 OSPF DR is 10.6.1.2, BDR is 10.2.1.254
Jul 11 09:07:36.011505 OSPF sent Hello 10.6.1.1 -> 224.0.0.5 (ge-3/0/8.0 IFL 230 area 0.0.0.0)
Jul 11 09:07:36.011531   Version 2, length 48, ID 10.2.1.254, area 0.0.0.0
Jul 11 09:07:36.011554   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:36.011574   dead_ivl 40, DR 10.6.1.2, BDR 10.6.1.1
Jul 11 09:07:36.013687 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:37.960642 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:39.963688 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:07:40.966869 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:41.285564 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:07:41.285907 OSPF rcvd Hello 10.6.1.2 -> 224.0.0.5 (ge-3/0/8.0 IFL 230 area 0.0.0.0)
Jul 11 09:07:41.286013   Version 2, length 48, ID 10.6.1.2, area 0.0.0.0
Jul 11 09:07:41.286035   checksum 0x0, authtype 0
Jul 11 09:07:41.286056   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:41.286076   dead_ivl 40, DR 10.6.1.2, BDR 10.6.1.1
Jul 11 09:07:41.808669 OSPF rcvd Hello 10.6.1.6 -> 224.0.0.5 (ge-1/0/1.0 IFL 182 area 0.0.0.0)
Jul 11 09:07:41.808731   Version 2, length 48, ID 10.6.1.2, area 0.0.0.0
Jul 11 09:07:41.808751   checksum 0x0, authtype 0
Jul 11 09:07:41.808772   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jul 11 09:07:41.808792   dead_ivl 40, DR 10.6.1.6, BDR 10.6.1.5
Jul 11 09:07:45.779034 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:07:45.779990 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:45.951731 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:07:51.266177 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:07:51.266516 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:07:51.573379 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:07:54.637182 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:07:54.637376 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:07:55.586561 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:00.123910 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:00.124254 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:01.208924 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:03.170425 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:03.950169 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:03.950639 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:08.791930 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:09.436658 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:09.436977 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:12.520058 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:13.275834 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:13.276248 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:18.141588 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:18.762673 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:18.762821 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:22.088906 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:22.089765 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:22.438820 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:27.576236 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:27.576650 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:28.060363 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:30.355550 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:30.671184 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:30.671537 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:35.977283 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:36.158022 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:36.158360 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:38.319166 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:38.319371 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:39.714793 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:43.806987 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:43.810036 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:45.327076 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:47.807779 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:47.807988 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:48.649085 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:53.294517 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:08:53.294857 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:54.271740 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:08:56.342416 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:08:56.342614 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:08:57.803991 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:01.829694 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:01.830262 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:03.425444 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:04.155290 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:04.155636 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:06.391677 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:09.642038 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:09.642384 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:12.014369 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:12.247098 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:12.247424 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:15.321379 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:17.733923 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:17.734262 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:20.944725 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:21.143934 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:21.144280 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:25.144080 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:26.630801 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:26.631147 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:30.765899 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:31.137417 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:31.137767 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:34.630974 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:36.628557 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:36.638524 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:40.253532 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:41.017666 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:41.017884 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:44.274019 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:46.504270 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:46.504678 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:48.813161 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:48.813366 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:49.896371 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:53.311311 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:54.300043 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:09:54.300385 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:09:58.627881 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:09:58.628098 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:09:58.933009 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:01.088146 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:04.114897 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:04.115278 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:06.709939 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:07.413663 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:07.413869 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:09.760431 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:12.900566 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:12.900909 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:15.381514 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:17.308383 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:17.308591 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:17.858659 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:22.795205 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:22.795553 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:23.480518 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:26.048161 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:26.048365 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:27.103405 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:31.534088 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:31.534412 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:32.725189 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:35.744203 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:35.956197 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:35.956368 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:41.367051 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:41.441793 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:41.442106 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:43.785995 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:44.428629 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:44.428847 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:49.407737 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:49.915671 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:49.915962 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:10:52.827782 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:54.304042 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:10:54.304531 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:10:58.450583 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:59.790268 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:10:59.790594 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:11:01.433461 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:02.818294 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:02.818508 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:11:07.056323 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:08.304118 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:11:08.304462 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:10.252241 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:12.459745 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:12.460133 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:11:15.873955 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:17.920098 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:17.946668 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:11:17.947162 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:21.573579 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:21.573782 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:11:23.542005 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:26.133814 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:27.062298 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:11:27.062642 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:29.832845 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:29.833304 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:11:31.755770 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:34.177604 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:35.320113 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162
Jul 11 09:11:35.320456 OSPF hello from 10.6.1.2 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:39.443953 OSPF periodic xmit from 10.6.1.1 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:39.444294 OSPF packet ignored: no matching interface from 10.6.1.1, IFL 162
Jul 11 09:11:39.799649 OSPF hello from 10.6.1.6 (IFL 2684275732, area 0.0.0.0) absorbed
Jul 11 09:11:42.243395 OSPF periodic xmit from 10.6.1.5 to 224.0.0.5 (IFL 2684276196 area 0.0.0.0)
Jul 11 09:11:44.932062 OSPF packet ignored: no matching interface from 10.6.1.2, IFL 162


Highlighted
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

mkt-core has the following networks branching off of it:

10.2.0.0/16 (local)

10.8.0.0/16 (another MAN connection)

10.12.0.0/16 (another MAN connection)

 

pnt-sw01 has a few local networks,

10.6.32.0/24

10.6.52.0/24

10.6.22.0/24

10.6.36.0/24

 

I would like mkt-core to know about all of the local networks on pnt-sw01

 

I would like pnt-sw01 to know its gateway is mkt-core.

 

Recognized Expert
Posts: 392
Registered: ‎01-05-2008

Re: Redundant MAN connections between two EX Stacks

As a supplemental to my previous post, here is a short example to export all static routes into OSPF. Per default, only OSPF routes are flooded to other OSPF neighbors, all other routes (like statics) have to be first exported into OSPF:

 

[edit]
+  protocols {
+      ospf {
+          export export_statics_into_ospf;
+      }
+  }
+  policy-options {
+      policy-statement export_statics_into_ospf {
+          term term1 {
+              from protocol static;
+              then accept;
+          }
+          term term2 {
+              then reject;
+          }
+      }
+  }

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Recognized Expert
Posts: 392
Registered: ‎01-05-2008

Re: Redundant MAN connections between two EX Stacks

If you wan't that a specific local interface (and its associated network) appear in OSPF, you have to add the interface in OSPF. If you know that there will be no OSPF router on this network you want to form an adjacency with, just add the passive option:

 

set protocols ospf area 0 interface vlan.xx passive

 

For the default route, use my example but change it to only match on the default route, like this way:

 

[edit]
+  policy-options {
+      policy-statement export_default_route_into_ospf {
+          term term1 {
+              from {
+                  route-filter 0.0.0.0/0 exact;
+              }
+              then accept;
+          }
+          term term2 {
+              then reject;
+          }
+      }

+ }

 

and apply this filter under the [protocols ospf export] stanza.


Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

Thank you very much for helping figure this out....

 

I'm now seeing the routes on the mkt-core switch for the remote office... which I've changed its config to look like this:

 

mitcha@pnt-sw01# show protocols ospf                   
area 0.0.0.0 {
    interface ge-1/0/2.0 {
        metric 10;
    }
    interface ge-0/0/0.0 {
        metric 20;
    }
    interface vlan.632 {
        passive;
    }
    interface vlan.652 {
        passive;
    }
    interface vlan.690 {
        passive;
    }
    interface vlan.622 {
        passive;
    }
    interface vlan.662 {
        passive;
    }
    interface vlan.636 {
        passive;
    }
}

However... in your example for the default route... on which switch to I put that...

 

I've put it on the mkt-core switch... it doesn't seem to be making a difference...

 

mitcha@mkt-core# show protocols ospf
area 0.0.0.0 {
    network-summary-export export_default_route_into_ospf;
    interface ge-1/0/1.0 {
        metric 10;
    }
    interface ge-3/0/8.0 {
        metric 20;
    }
}

mitcha@mkt-core# show policy-options    
policy-statement export_default_route_into_ospf {
    term term1 {
        from {
            route-filter 0.0.0.0/0 exact;
        }
        then accept;
    }
    term term2 {
        then reject;
    }
}

Recognized Expert
Posts: 392
Registered: ‎01-05-2008

Re: Redundant MAN connections between two EX Stacks

[ Edited ]

Hi,

 

not "network-summary-export" but just "export" Smiley Happy under [protocols ospf]

 

Regards,

Dominik

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
Contributor
Posts: 20
Registered: ‎08-10-2009
0

Re: Redundant MAN connections between two EX Stacks

THANK YOU!  been reading on this and it hasn't really made sense till now.

 

Its working, and for completness I'll repost what config I ended up with.

 

mitcha@mkt-core# show protocols ospf
export export_default_route_into_ospf;
area 0.0.0.0 {
    interface ge-1/0/1.0 {
        metric 10;
    }
    interface ge-3/0/8.0 {
        metric 20;
    }
}

 

mitcha@mkt-core# show policy-options                                                    
policy-statement export_default_route_into_ospf {
    term term1 {
        from {
            route-filter 0.0.0.0/0 exact;
        }
        then accept;
    }
    term term2 {
        then reject;
    }
}

 

And the remote office switch:

 

mitcha@pnt-sw01# show protocols ospf
area 0.0.0.0 {
    interface ge-1/0/2.0 {
        metric 10;
    }
    interface ge-0/0/0.0 {
        metric 20;
    }
    interface vlan.632 {
        passive;
    }
    interface vlan.652 {
        passive;
    }
    interface vlan.690 {
        passive;
    }
    interface vlan.622 {
        passive;
    }
    interface vlan.662 {
        passive;
    }
    interface vlan.636 {
        passive;
    }
}

Recognized Expert
Posts: 392
Registered: ‎01-05-2008

Re: Redundant MAN connections between two EX Stacks

[ Edited ]

Hi,

 

a great resource for how to configure OSPF are the learning books for the service provider track. You find them under:

 

https://www.juniper.net/us/en/training/certification/books.html

 

The first book gives you a good intro (chapter 6)

 

https://www.juniper.net/training/certification/JNCIA_studyguide.pdf

 

Regards,

Dominik

 

 

JNCIE et al.

--
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?