Cisco SD-WAN 007 - Templates Overview, Single vEdge Sites Setup and Deployment
Вставка
- Опубліковано 23 сер 2024
- In this video, we will transition from using the CLI to configure, manage and operate the vEdge devices over to templates. Templates offer the ability to setup and deploy a new device within minutes versus hours. They are often used to logically group sites together for ease of management.
Thank you very much Rob for this wonderful series - fantastic job
Tq sir for the tutorial
System Template 7:46
Banner Template 9:59
VPN0 Template 13:59
VPN512 Template 18:19
VPN0 Interface Template 19:31 biz-internet
VPN0 Interface Template 22:54 mpls
VPN512 Interface Template 24:03
BGP Template 26:53 vpn0 mpls
Device Template 29:42 single device
Config push successful 38:15
I need to get to this level lol I'm labbing and studying everyday, great channel!!
Great job. Very logical layout
Rob - You are Great Mentor :) Salute Sir
Cheers Rob! Very informative
Personally, I still prefer the cli template because in Gui template you still need to put the necessary details like system IP and WAN IP of your vEdge, in cli template you can create one in your notepad.
Hi Thank you for providing such nice videos. Wondering if you also had a look at CLI template ? I may be wrong but I didn 't see it. thank you. What do you think is better CLI compared to web template ? pros and cons ?
I think the worst part about Templates is having OCD as an Engineer. It would be nice if we could stack templates. Things like VPN 0 and 512 will more than likely be the same config from site to site, but the LAN side of the vEdge could and most likely will be different if not deploying greenfield. So things like overlay VPN1 might be different from site to site, so more templates to make. How can we back these templates up out of vManage so later if vManage hits the dirt we dont have recreate?
Hello Rob..
Great Video, great contents, thank you so much buddy. Big Big Bummer!! I cannot lab it up simply because don't have access to downloading SD-WAN images from Cisco's Website..
By the way, do you know any organization that rents-out access to online EVE-NG (or any other convenient method) to get some hand-one experience with setting up SD-WAN technology?
same here
Cisco Devnet
Rob, sorry for "good" question. How do you think, Is your labs enough for ENSDWI exam preparation? If it is not enough, please define percent of your labs that covers ENSDWI exam. Thanks!
I had to remove ge0/0 from vpn0 for vEdge5 to go from partial to control up! Just disabling did not work.
Hi Rob, great viedo! Made it all the way to video07. I got this lab on eve but somehow , only site 5's got the bfd sessions to the rest, the rest has connections also only to site 5. I understand bfds are on by default and cannot be turned off. Kinda of puzzled why this isnt working for the rest of the sites. i am using viptela 19.2.3. Would appreciate any insights on the troubelshooting? Thanks in advance.
if you execute "show bfd sessions", site 5 is connected to MPLS only, so will only connect to the other sites over MPLS. the other sites will connect to each other over public internet.
@@RobRikerTechChannel Thanks for the prompt reply! The other site's connection over public internet isnt coming up... besides 'sh bfd sessions', what else could i check?
sounds like you need a default route setup for VPN0. You should be able to ping between the vEdges over both transports. I added "restrict" to both transport as well. Make sure that each interface has it's own color, "public-internet" and "mpls". Add restrict to each. Beyond that, I would need to look to find the issue.
@@RobRikerTechChannel Thanks Rob. I've got all of that checked. Like you said, it could be something else.
Hi Rob, got an intersting quetion. Before I raise the question, I would like let you know I got a DNS server running on my LAB, controllers using vbond domain name to find vbond, but vEdges all using vbond IP. That works good in CLI mode. When I applied the device tempate followed by your video, the template changed vEdge's vbond IP to vbond domain name automatically. Because I do not set primary DNS on vEdges template so it cannot reach vBond domain name, results all control connections down. I don't find a place to enabe my chnage vbond domain to vbond IP on device /feature tempate, and if there is no place to change that why once I applied the template it changes my vbond configs?
I never deployed it that way. I have no idea why it does that. I would suggest looking into the zero touch provisioning aspect and see if that helps you out.
@@RobRikerTechChannel Thanks for the advice, I will try