This topic is pretty straightforward, so I’m trying to think of ways they can over-complicate it on the exam, maybe with some obscure setting you would never, ever configure in a production environment. 1.1.a i Managing MAC address table The best I can come up with is modifying the aging time on the mac addressContinue reading “1.1.a Switch Administration”
Tag Archives: CCIE
1.1.e Spanning Tree Protocol
I’m getting beat up pretty bad by SD-WAN, so I’m taking a break to bang out some easy stuff off the blueprint. I want to give myself a false sense of progress. The topology is super simple: 1.1.e i PVST+, Rapid PVST+, MST Super-quick summary on the versions:PVST+: 30-50 seconds before a port transitions toContinue reading “1.1.e Spanning Tree Protocol”
2.2.c Configuration templates
I’m probably going to come back here and do a ton more with Configuration Templates, because it seems like the possibilities are endless. But for now, I just want to do a quick local password, NTP, and Loopback0 interface config and attach it to the ASR 1001-X. On vManage, go to Configuration > Templates. ClickContinue reading “2.2.c Configuration templates”
2.2.b WAN edge deployment
For this lab, the plan is to convert an ASR 1001-X over to SD-WAN code (I’m using 16.12.5 SD-WAN code, instead of the 17.x universal code, so I can test upgrading the router later.) and get it added to the SD-WAN deployment. The steps are pretty straightforward: Re-image the device. Stop the PNP service. ApplyContinue reading “2.2.b WAN edge deployment”
SD-WAN: Organization Name Blunder
It turns out I really screwed up by using the organization name of “lab”. When I tried to do anything with PNP, I was stopped dead in my tracks because someone already used that name. Luckily this is just a lab, so changing the organization name shouldn’t be a big deal… except there’s no optionContinue reading “SD-WAN: Organization Name Blunder”
2.2.a iv Data plane (vEdge/cEdge)
The data plane is simple. It’s just an IPSec overlay. The big difference is that there’s a central key manager, the vSmart, which cuts down on overhead. There are two options, symmetric keys and pairwise. Using symmetric keys, each WAN Edge sends its key to the vSmart, then the vSmart sends that key to allContinue reading “2.2.a iv Data plane (vEdge/cEdge)”
2.2.a iii Control plane (vSmart, OMP)
vSmart The vSmart is the centralized control plane of the SD-WAN deployment. It provides routing and data plane policies to the WAN Edge routers. The vSmart takes in all of the routing and topology information from the WAN Edge clients, calculates the best-path, then advertises the results back to the WAN Edge routers. The communicationContinue reading “2.2.a iii Control plane (vSmart, OMP)”
2.2.a ii Management plane (vManage)
vManage The vManage server is the central manager for the SD-WAN deployment. This is where you’ll configure templates, onboard and provision devices, monitor everything with the fancy dashboards. It’s kind of like DNAC for the WAN, or it’s similar to the Admin Node in ISE. Just like everything else these days, it also supports RESTContinue reading “2.2.a ii Management plane (vManage)”
2.2.a i Orchestration plane (vBond, NAT)
vBond The vBond component is pretty much the key to the whole SD-WAN solution working. When a WAN Edge comes online, the only thing it’ll know about (learned from PNP, Zero-Touch Provisioning, or Manual or Bootstrap config) is the vBond. The vBond then directs the WAN Edge routers on how to get to vManage (ManagementContinue reading “2.2.a i Orchestration plane (vBond, NAT)”
2.2.a Design a Cisco SD-WAN solution
I’m not sure how this blueprint item can translate into a lab task, but I’m going to use it to do a brief SD-WAN overview, which may help with any troubleshooting of later “deployment” tasks. I won’t be going into the history of SD-WAN or all of the benefits. For that you can read chapterContinue reading “2.2.a Design a Cisco SD-WAN solution”
Oscorp Labs 