Already a qualifying Patreon member? Refresh to access this content.
8 thoughts on “VRF Lab 2”
admin
Migrated Comment:
Missing command
Pablo (unverified) 2018-06-21 01:56
Hi Luke, I just found your videos throug a mention in the CLN and found them very interesting and helpful for my studies.
I am building this topoloty in GNS3 and the BGP neighbor relationship was not coming up for me, the command “vrf forwarding CustB” was missing in the interface in the Core router towards the CustB-Wan router. I did not see you entering this command in the video or in the snips above. So spent a bit of time trying to figure out, then added it and saw the BGP coming UP.
interface FastEthernet1/0
vrf forwarding CustB
ip address 10.254.254.9 255.255.255.252
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.254.254.10 4 65001 8 10 6 0 0 00:04:30 2
Missing Command
Luke Robertson 2018-06-21 16:05
Nicely spotted. The reason you don’t see it here or on the video, is this builds on the config in part 1.
The command was already in there from the previous config.
I’ll add a note to this page to make this more clear for anyone else who comes across this issue.
But I bet you understand VRF well now 🙂
Missing Command
Pablo (unverified) 2018-06-22 00:40
Yes it helped me better understand it definitely. Also through your videos I found the “ip ospf network point-to-point” on the loopback interface fixes the issue on advertising the full subnet instead of a /32, I can now finally fix my OSPF topology in GNS3 !!!
Would be nice also if you could put an e-mail notification once you reply to a comment 🙂
Look for a section called ‘Lab Files’ and download the archive.
When you extract it, you will find the config files in there, which can be opened in notepad
Unlock with Patreon
Migrated Comment:
Missing command
Pablo (unverified) 2018-06-21 01:56
Hi Luke, I just found your videos throug a mention in the CLN and found them very interesting and helpful for my studies.
I am building this topoloty in GNS3 and the BGP neighbor relationship was not coming up for me, the command “vrf forwarding CustB” was missing in the interface in the Core router towards the CustB-Wan router. I did not see you entering this command in the video or in the snips above. So spent a bit of time trying to figure out, then added it and saw the BGP coming UP.
interface FastEthernet1/0
vrf forwarding CustB
ip address 10.254.254.9 255.255.255.252
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.254.254.10 4 65001 8 10 6 0 0 00:04:30 2
Migrated Comment:
Missing Command
Luke Robertson 2018-06-21 16:05
Nicely spotted. The reason you don’t see it here or on the video, is this builds on the config in part 1.
The command was already in there from the previous config.
I’ll add a note to this page to make this more clear for anyone else who comes across this issue.
But I bet you understand VRF well now 🙂
Migrated Comment:
Missing Command
Pablo (unverified) 2018-06-22 00:40
Yes it helped me better understand it definitely. Also through your videos I found the “ip ospf network point-to-point” on the loopback interface fixes the issue on advertising the full subnet instead of a /32, I can now finally fix my OSPF topology in GNS3 !!!
Would be nice also if you could put an e-mail notification once you reply to a comment 🙂
Hi,
Maybe I missed it. but I can’t seem to configure EIGRP in name mode. Can you please help? Thank you in advance.
That depends on what issues you’re facing.
Named mode uses some different syntax, mostly around address-families.
Try these links and see if they help:
https://www.ciscozine.com/cisco-eigrp-named-vs-classic-mode/
https://www.packetflow.co.uk/how-to-configure-eigrp-named-mode/
How do I download the configs on notepad?
Look for a section called ‘Lab Files’ and download the archive.
When you extract it, you will find the config files in there, which can be opened in notepad
so I did all the config right, but I forgot to add this on core1:
Core1(config-router)#address-family ipv4 vrf custB
Core1(config-router-af)#network 10.254.254.4 mask 255.255.255.252
Before adding the command customer B R1 router wasn’t able to ping WAN B 172.20.10.0/24 but WANB could ping CustB R1, can you please explain why?