In the previous lesson, you learned the five fabric roles.
Now you need to see how they work together when a user actually sends traffic.
Everything starts with one simple question: how does the fabric know where every user is?The Topology You Will Follow
Throughout this lesson, you will follow a small fabric with three Fabric Edges.
PC1 sits behind Edge 1 on Floor 1.
You want it to reach PC3, which sits behind Edge 3 on Floor 3.
Figure 1 – The fabric topology
PC1 has the IP address 10.1.1.10.
PC3 has 10.3.3.30.
In LISP terms, these user IPs are called EIDs (Endpoint Identifiers).
Each Fabric Edge also has a routable IP, the RLOC (Routing Locator).You already saw both terms in the LISP Fundamentals lesson.
SD-Access uses LISP for its control plane: every user is identified by its EID and reached through its Edge's RLOC.RLOCs reach each other through the underlay, a routed Layer 3 network.
Catalyst Center provisions it for you, so you do not have to worry about it in this lesson.Map-Register
When PC1 connects to Edge 1, the switch learns its MAC and IP address through ARP.
But that knowledge stays local to Edge 1.
The rest of the fabric does not know PC1 exists.To fix this, Edge 1 sends a Map-Register message to the Control Plane Node.
It declares: "PC1 (10.1.1.10) is reachable through my RLOC (1.1.1.1)."
Figure 2 – Edge 1 registers PC1
The Control Plane Node stores this binding in its mapping database.
Map-Registers are sent every time a new endpoint connects.
They are also refreshed periodically to keep the entry alive.Answer the question below
Which fabric component receives the Map-Register from Edge 1?
The Mapping Database
Every Fabric Edge does the same thing for its own users.
Once they have all registered, the Control Plane Node holds a complete picture of the fabric.
Figure 3 – The mapping database after registration
This mapping database is the foundation of SD-Access.
The Control Plane Node is the single source of truth for endpoint location.When a user moves from one floor to another, only the mapping database entry is updated.
If you have read the LISP Fundamentals lesson, the Fabric Edge plays the role of an xTR (ITR + ETR), and the Control Plane Node plays the role of MS/MR.
Answer the question below
Which message does a Fabric Edge send to register a connected user with the Control Plane Node?
The mapping database is built.
Now PC1 wants to talk to PC3.
How does Edge 1 figure out where to send the traffic?Cache Miss and Map-Request
PC1 sends a packet to 10.3.3.30.
It arrives at Edge 1 as it would on any switch.Edge 1 checks its local cache first.
Does it already know where 10.3.3.30 is?
Figure 4 – Cache miss and Map-Request
The first time, the answer is no.
Edge 1 only knows about its own connected users.So Edge 1 sends a Map-Request to the Control Plane Node.
It asks the same thing you would ask a directory: "Where does 10.3.3.30 live?"Answer the question below
Which address represents a Fabric Edge's location in the underlay?
Map-Reply
The Control Plane Node looks up 10.3.3.30 in its mapping database.
It finds that PC3 lives behind Edge 3, which has the RLOC 3.3.3.3.It returns a Map-Reply to Edge 1 with this binding.

Figure 5 – Map-Reply and caching
Edge 1 stores the binding in its local cache.
Every following packet from PC1 to PC3 reuses this cache.
There is no new lookup on the second packet.This is the LISP control plane you saw before, now running inside a campus.
The fabric never floods, never broadcasts, and never asks twice for the same answer.Answer the question below
Where does Edge 1 store the binding it received in the Map-Reply?
Answer the question below
From an empty cache, PC1 sends to PC3, PC2 (Edge 2), PC4 (Edge 1) then PC3 again: how many Map-Requests?
Edge 1 now knows where to send the traffic.
But the underlay only routes between RLOCs, not between user IPs.
The data plane needs a way to wrap the user's packet so the underlay can carry it, and to tag who sent it.Where the Group Identity Comes From
When PC1 connected to its port, the user authenticated through 802.1X.
This happened at the same time as the Map-Register from section 1.Edge 1 wraps the credentials in a RADIUS Access-Request and sends them to Cisco ISE, the Cisco identity server.

Figure 6 – ISE assigns the SGT
ISE authenticates the user and replies with a RADIUS Access-Accept.
The reply carries a Security Group Tag (SGT) (also called Scalable Group Tag in some Cisco docs) representing the user's group, for example "Employee" or "Contractor".Edge 1 now holds three pieces of information about PC1: the MAC address (learned through ARP), the IP address or EID (10.1.1.10), and the SGT (10, received from ISE). Together, these tell the Edge where the user is, and who the user is.
Every packet from PC1 will carry this tag, no matter where the user moves in the fabric.The SGT lets the fabric apply policy based on who the user is, not where they are.
It is the foundation of Cisco TrustSec inside SD-Access.Answer the question below
Which Cisco component assigns the SGT to a user during 802.1X authentication?
VXLAN Encapsulation
Edge 1 has everything it needs.
PC3's RLOC came from the mapping database.
PC1's SGT came from ISE.
Edge 1 now wraps the original packet using VXLAN (RFC 7348).SD-Access actually uses VXLAN-GPO, a Cisco extension that adds the SGT next to the VNI in the header.
In SD-Access, every Fabric Edge and the Border Node act as VTEPs (VXLAN Tunnel Endpoints).
They wrap and unwrap VXLAN traffic when it enters or leaves the overlay.
Figure 7 – VXLAN-GPO encapsulation
Reading the packet from left to right, this is the order on the wire:
Outer IP from Edge 1's RLOC to Edge 3's RLOC. The underlay uses this part to route the packet.
Outer UDP with destination port 4789, the IANA-assigned VXLAN port.
VXLAN-GPO header carrying the VNI (VXLAN Network Identifier) and the SGT (PC1's group identity).
Inner IP and payload, the original packet from PC1 to PC3, untouched.
The VNI keeps traffic isolated, the same way different VRFs do in a traditional network.
Because the SGT travels in every packet, Edge 3 can apply policy without using IP-based ACLs.Answer the question below
Which encapsulation does the SD-Access data plane use to carry user traffic?
End-to-End Packet Flow
You can now follow a single packet from PC1 to PC3.

Figure 8 – End-to-end packet flow
PC1 sends a regular IP packet destined to 10.3.3.30.
Edge 1 looks up its cache, finds the binding to RLOC 3.3.3.3, and encapsulates the packet in VXLAN-GPO with PC1's SGT.
The underlay forwards the encapsulated packet from 1.1.1.1 to 3.3.3.3, hop by hop, like any IP packet.
Edge 3 receives the VXLAN packet, strips the outer headers, reads the SGT for policy enforcement, and recovers the inner destination 10.3.3.30.
Edge 3 delivers the original packet to PC3 on its local port.
From PC1's perspective, nothing changed.
It sent an IP packet and got a reply.
But the fabric did three things in parallel: it kept the user identity stable, isolated the traffic per virtual network, and carried the SGT for policy.Answer the question below
Which Fabric Edge decapsulates the VXLAN packet before delivering it to the destination user?
Verification on the Fabric Edge
You can confirm all of this on a Fabric Edge with a single command.
Runshow lisp instance-id 4099 ipv4 map-cacheon Edge 1 to see the cached bindings.Edge1# show lisp instance-id 4099 ipv4 map-cache LISP IPv4 Mapping Cache for EID-table vrf USER (IID 4099), 2 entries 10.3.3.30/32, uptime: 00:00:42, expires: 23:59:18, via map-reply, complete Locator Uptime State Pri/Wgt Encap-IID 3.3.3.3 00:00:42 up 10/10 -The output confirms what you just saw.
Edge 1 has cached the binding for 10.3.3.30, learned via a Map-Reply, pointing to RLOC 3.3.3.3 (Edge 3).Answer the question below
Looking at the output, which RLOC does Edge 1 use to reach 10.3.3.30?
Reaching a Server Outside the Fabric
Now imagine a different destination.
PC1 wants to reach a legacy server at 10.99.0.10, in a traditional VLAN outside the fabric.
That server is not registered with the Control Plane Node.
It has no SGT, no RLOC, and no entry in the mapping database.When Edge 1 sends a Map-Request for 10.99.0.10, the Control Plane Node returns the RLOC of the Border Node (4.4.4.4) instead of a Fabric Edge.
The Border Node is the gateway to everything outside the fabric.
Figure 9 – Reaching a legacy server
From there, the VXLAN mechanics you already know apply, with one difference at the end:
Edge 1 encapsulates PC1's packet in VXLAN with the Border Node's RLOC (4.4.4.4) as the outer destination.
The underlay forwards the VXLAN packet to the Border Node.
The Border Node decapsulates the VXLAN packet and recovers PC1's original IP packet.
The Border Node forwards it as standard IP into the legacy network, like any traditional router.
The SGT travels in the VXLAN packet up to the Border Node.
Once the packet leaves the fabric as standard IP, the tag is dropped.
The legacy network sees it as regular IP traffic.The reply takes the opposite path.
Standard IP from the server to the Border Node, then VXLAN re-encapsulation back into the fabric toward Edge 1.
Neither side knows the other runs on a different architecture.Answer the question below
Which fabric component lets a user inside the fabric reach a server in a traditional VLAN?