JNCIP-DC key terms

A BGP EVPN route that advertises a specific MAC address, optionally with its IP binding, so remote leaf switches learn end-host location and populate their MAC and ARP tables.

A BGP EVPN route that advertises an IP prefix rather than a host MAC, letting the fabric carry routed subnets and enabling prefix-based overlay routing between VRFs.

A per-VLAN bridging instance on a PE that holds learned MAC addresses and is bound to an EVPN instance, mapping local VLANs to a shared overlay segment.

The configuration that ties a local VLAN identifier to a VXLAN network identifier, so frames from that VLAN are encapsulated with the matching VNI on egress.

A configuration where every leaf uses the same virtual MAC and IP for a distributed SVI, so hosts keep one default gateway while traffic is routed locally on the attached leaf.

An SVI configured identically on all leaf switches for a given VLAN, allowing first-hop routing at the edge instead of tromboning traffic to a central pair of spines.

An EVPN routing model where both the ingress and egress PE use the same VNI for a given VRF, so routed traffic is encapsulated once with the L3 VNI.

An EVPN routing model where the ingress PE bridges into the destination VLAN's L2 VNI and the egress PE routes, so different VNIs are used on each side.

A VXLAN network identifier dedicated to a routing instance (VRF), used to carry routed traffic between leaf switches in a symmetric IRB overlay design.

A tunneling protocol that encapsulates original Layer 2 frames inside UDP, using a 24-bit VNI to stretch many isolated segments across an IP-routed underlay.

The tunnel endpoint that performs VXLAN encapsulation and decapsulation, typically a leaf switch, identified by a loopback address reachable through the routed underlay.

The IP-routed physical network of spines and leaves that provides loopback-to-loopback reachability and equal-cost paths, carrying overlay traffic without knowing tenant addresses.

The logical tunneled network built on top of the underlay, carrying tenant Layer 2 and Layer 3 traffic in VXLAN with control-plane learning from BGP EVPN.

A two-tier Clos topology where every leaf connects to every spine, giving predictable latency and uniform equal-cost paths between any pair of access switches.

An IP fabric design where each spine and leaf is a separate autonomous system and BGP advertises loopbacks and point-to-point links, providing multipath routing with simple policy.

Equal-cost multipath, the forwarding behavior that hashes flows across several equally preferred next hops, multiplying bandwidth and resilience in a spine-leaf fabric.

A device, often the spine, that reflects BGP EVPN routes between leaf clients so every leaf learns all overlay routes without a full iBGP mesh.

A BGP extended community attached to EVPN routes that controls which VRFs or EVIs import them, effectively steering tenant routes to the correct receiving instances.

An identifier prepended to EVPN or VPN prefixes so the same tenant prefix advertised by different switches becomes a unique route in BGP.

A proxy behavior where the leaf answers ARP requests from a cached control-plane table instead of flooding them across the overlay, reducing broadcast and unknown-unicast load.

Broadcast, unknown-unicast, and multicast frames that VXLAN must flood to every VTEP in a segment, usually via multicast or ingress replication head-end lists.

A Cisco technology that pairs two switches into one logical endpoint using a peer link and peer keepalive, offering active-active links without spanning-tree blocking.

A bundle of physical links treated as one logical interface, providing aggregated bandwidth and link redundancy while running LACP or static channel negotiation.

A Cisco ACI construct that links two separate ACI fabrics at the spine or border level, allowing endpoints and policies to extend across data centers.

An ACI deployment where several pods share one APIC cluster and control plane, connected over an IPN, so endpoints in different pods behave as one fabric.

An ACI design connecting independent fabrics, each with its own APIC cluster, through an intersite network so policies and stretched endpoints can span sites.

The Cisco Application Policy Infrastructure Controller, the cluster that manages ACI fabric policy, endpoint inventory, and fabric-wide configuration through a centralized model.

A logical container in ACI that isolates policy, VRFs, bridge domains, and EPGs for one application or customer, similar to a separate administrative partition.

An Endpoint Group in ACI: a collection of endpoints that share the same policy and are attached through a common bridge domain, used as the policy enforcement unit.

An ACI policy object that defines which protocols and ports one EPG may use to reach another, enforcing segmentation through a provider-consumer relationship.

An ACI L2 forwarding domain that groups subnets and SVIs, analogous to a VLAN, and determines whether routing between its subnets is enabled.

A virtual routing and forwarding instance that keeps separate routing tables on shared hardware, isolating tenant or application subnets from one another.

An ACI abstraction that inserts one or more L4-L7 devices, such as firewalls or load balancers, into the traffic path between EPGs by redirecting flows through them.

Policy-based routing, which forwards traffic according to configured match criteria rather than the destination-based routing table, often used to steer traffic to a firewall.

A set of switch features such as DHCP snooping, dynamic ARP inspection, and IP source guard that block rogue servers and spoofed addresses at the access edge.

A feature that limits or restricts the MAC addresses allowed on an interface, optionally shutting it down or dropping offending frames when a violation occurs.

Streaming export of operational data such as interface counters, queue drops, and hardware statistics at short intervals, enabling near-real-time monitoring instead of polling.

A flow-export technology that summarizes traffic by source, destination, ports, and volume, used for capacity planning, accounting, and anomaly detection.

Switched Port Analyzer, a feature that copies traffic from selected ports or VLANs to a monitoring destination for packet capture and analysis.

Encapsulated Remote SPAN, which carries mirrored traffic in a GRE tunnel to a remote analyzer across a routed network rather than a local port.

An approach where applying the same configuration repeatedly yields the same result, so rerunning a playbook or script does not create drift or duplicate objects.

Managing network and compute configuration through version-controlled declarative files rather than manual CLI changes, enabling review, repeatability, and rollback.

An agentless automation tool that pushes modules over SSH or API to devices, commonly used to template and deploy switch configurations at scale.

An HTTP-based interface where clients read or change objects using standard methods and structured payloads, the basis for programmatic control of controllers and switches.

A data modeling language that defines the structure and constraints of device configuration and state, used by NETCONF and RESTCONF for programmatic access.