Author Archives: Allen Rodriguez
MPLS Layer 3 VPN diagrams often show customer edges connected to provider edges, a cloud in the middle, and colored VPNs that appear perfectly isolated. The real control boundary is created by VRFs, route distinguishers, route targets, MP-BGP policy, MPLS forwarding, PE-CE routing, and the operational processes that prevent one customer’s routes from entering another […]
MPLS is easiest to understand when the label is treated as forwarding context rather than as a replacement for IP routing. The current 350-501 SPCOR v1.0 blueprint still includes MPLS, LDP, traffic engineering, VPN services, and related provider-core behavior. Routers use routing information to establish reachability, label-distribution mechanisms advertise label bindings, and the data plane […]
IS-IS is often harder to learn than it is to operate because its terminology feels unfamiliar to engineers who first learned OSPF. In a provider core, however, the useful mental model is simple: IS-IS is a link-state IGP that distributes topology information so routers can calculate shortest paths to infrastructure prefixes and next hops. The […]
BGP in a service-provider network is not simply a protocol for exchanging internet routes. It is a policy system that connects customer reachability, infrastructure, MPLS VPNs, peering, transit, route reflection, traffic engineering, and security. Cisco’s current 350-501 SPCOR exam remains the core requirement for CCNP and CCIE Service Provider, and the current v1.1 blueprint explicitly […]
Modern data centers produce more telemetry than most teams can interpret comfortably: interface counters, routing state, fabric faults, flow records, streaming telemetry, logs, APIs, host metrics, storage events and application traces. The current 350-601 DCCOR v1.2 blueprint includes implementing Network-domain monitoring with NetFlow, SPAN and Cisco Nexus Dashboard (Network 25%), explaining streaming telemetry and Nexus […]
NX-API and REST automation should be treated as a verified state-control loop, not a faster way to send CLI commands. The current 350-601 DCCOR v1.2 Automation and Artificial Intelligence domain is weighted at 15% and explicitly includes implementing REST APIs (NX-API with JSON/XML encodings), NX-OS Bash/Guest Shell, on-box Python, EEM and scheduler tasks. It separately […]
Leaf-spine fabrics are often described as inherently resilient because each leaf can reach multiple spines and ECMP can use parallel paths. That is a useful starting property, not a complete high-availability design. The current 350-601 DCCOR v1.2 Network domain (25%) includes applying OSPFv2/v3, MP-BGP, PIM and first-hop redundancy; switching concepts such as LACP and vPC; […]
Data-center network security is strongest when the architecture starts with the assets and trust relationships that matter, not with a list of controls. The active 350-601 DCCOR v1.1 blueprint includes management security, authentication/authorization/accounting, ACI security, infrastructure protection, and network/data-center control boundaries. The operational question is which path an attacker or accidental change can use and […]
Cisco UCS is best understood as a system for composing server identity, connectivity, firmware policy and lifecycle, rather than as an inventory of blade and rack hardware. The current 350-601 DCCOR v1.2 Compute domain (25% of the 120-minute core exam) still covers UCS rack and blade implementation, infrastructure/network/storage/server policies, software updates, backup/restore and infrastructure monitoring. […]
Choosing between Fibre Channel and IP-based storage is not a contest between an old technology and a modern one. It is a decision about latency, loss behavior, operational skill, scale, failure domains, convergence, cost, and what the application expects from block storage. Those trade-offs remain directly relevant to 350-601 DCCOR, whose active v1.2 blueprint covers […]
Storage networking carries traffic whose performance and failure behavior can directly determine whether applications remain available. The current 350-601 DCCOR v1.1 blueprint includes storage networking as a core domain, and the useful design review starts with the data path: host initiator, fabric, target, logical storage, multipathing, and the application that depends on the I/O. The […]
Data-center routing design has to move traffic quickly and predictably while limiting failure scope. The current 350-601 DCCOR v1.1 blueprint includes OSPFv2/OSPFv3, MP-BGP, PIM, first-hop redundancy, packet flow, VXLAN EVPN, and external connectivity. The important design decision is which protocol owns each layer and how much state each device must carry when the fabric grows […]
Nexus switching diagrams usually show leafs, spines, vPC pairs, uplinks, and servers. They rarely show software lifecycle, feature dependencies, control-plane limits, configuration checkpoints, logging, telemetry, automation, and the operational work required when a switch is partially healthy. The current 350-601 DCCOR v1.2 blueprint includes switching protocols, software updates, configuration management, monitoring, streaming telemetry, and Nexus […]
VXLAN EVPN is designed to make large Layer 2 and Layer 3 fabrics more scalable and controllable, but the security and operational value depends on how the underlay, overlay, endpoint learning, route distribution, anycast gateways, and external connectivity are designed. The current 350-601 DCCOR v1.1 blueprint explicitly includes VXLAN EVPN, MP-BGP, packet flow, and routing/switching […]
Cisco ACI policy becomes confusing when operators treat every object as a mandatory configuration checklist instead of part of one forwarding decision. The current 350-601 DCCOR v1.2 blueprint includes ACI fabric setup, access policies and VMM integration within its Network domain (25%), as well as analyzing unicast, multicast and broadcast packet flow. ACI contracts and […]
