02-14-2017 10:18 PM - edited 03-08-2019 09:20 AM
See the attached:
Cant figure out why the tunnel had a 'down' protocol.
If you need more info from the routers...Let me know. Thanx Team.
02-19-2017 01:43 PM
Hi Jason,
hahaha that is ok my friend, If you like you could share the config of your routers here in order to verify them. Also a picture of your topology.
:-)
02-20-2017 11:26 AM
02-20-2017 11:44 AM
Thanks, Im checking the config, also add the route-distiguisher under the vrf definition PIPE on all the routers using VRF PIPE
vrf definition PIPE
rd 1:1
Also you sent the echo2 config instead Fox14, but I noted that you are using passive-interface default and only one interface is allowed to receive routing traffic, but I think it has 2 serial interface to pass routing traffic, passive-interface default should be disabled for testing purposes.
02-20-2017 11:56 AM
02-20-2017 12:02 PM
No worries Jason, thank you.
Well i have seen an ACL on the fast ethernet, But I think first you should add the route distinguisher as I mentioned previously and also verify the interfaces configured on passive, I suggest remove them to discard it as root cause.
02-20-2017 12:50 PM
02-20-2017 01:08 PM
hehehe thats ok my friend, I remember a passive interface default on Echo2, was it removed too? is Echo4 configured with passive interface default?
If the tunnels dont go up after removing the passive default, could you please provide me the configs on a file text to verify them.
Thank you in advance.
02-20-2017 01:08 PM
Good catch... I will remove all passive interface config's from Echo2 and Echo4
02-20-2017 01:13 PM
Thank you, please keep me posted. Just a brief explanation:
Is good practice the LAN interface are not required to receive routing information, it is a good security practice so you can use passive-interface default but you must configure: no passive-interface <interface>, for the interfaces used to create adjacency with other routers otherwise you will be isolating the router.
:-)
02-20-2017 01:30 PM
02-20-2017 01:35 PM
Ok perfect,
Please execute this command line on FOX3 or 4. With this command you should see if these routers are knowing the source or destination IPs
show ip route vrf PIPE
or
show ip route vrf PIPE ospf
02-20-2017 01:47 PM
02-20-2017 01:58 PM
Hi
As we can see, FOX14 does not know how to reach the subnet 10.13.2.0/30, so the problem could be originated by routing.
You should verify if:
- They are on the Area 0
- If the point to point subnets between the routers is being advertised under the ospf process into the vrf.
Could provide me the config of the routers on a txt file.
Thank you.
02-20-2017 02:20 PM
02-20-2017 02:35 PM
I found that ECHO 4 was not config'd for Area 0.. I changed it and now we are looking good
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide