Hands-On Lab: Configuring SXP to Propagate SGT Information

This hands-on lab configures the SGT Exchange Protocol (SXP) between two switches, allowing SGT-to-IP mapping information to reach a device that lacks the hardware capability to carry SGT tags inline, extending the SGT-based segmentation covered in an earlier lab across non-SGT-capable infrastructure.

SXP Speaker and Listener ConfigurationSGT-to-IP Binding PropagationLegacy Hardware SGT Support

~4 min read · Updated Sep 26, 2026

Lab Objective

Configure SXP between a switch with SGT-capable hardware and a second switch lacking that capability, verify SGT-to-IP bindings propagate over the SXP session, and confirm the receiving switch can still enforce SGACL policy despite never seeing an inline SGT tag on the wire.

Lab Purpose

The SGT lab covered earlier in this series relied on inline tagging, where the SGT travels embedded directly within each frame — a capability requiring specific hardware support. SXP solves the problem of extending SGT-based policy to switches, routers, or firewalls that lack this inline tagging hardware, by propagating the SGT-to-IP binding information out-of-band instead.

Lab Topology

Switch1 (SGT-capable, inline tagging,
         configured with SGT assignments
         from the earlier SGT lab)
  ---- SXP session ---- Switch2 (legacy
                        hardware, cannot
                        carry inline SGT
                        tags on its uplinks)

Employee-PC (SGT 10) connects to Switch1
Enforcement point exists on Switch2 for
traffic destined to a server there

Task 1: Configure Switch1 as an SXP Speaker

Configure Switch1 to speak SXP, advertising its locally learned SGT-to-IP bindings to Switch2.

Task 2: Configure Switch2 as an SXP Listener

Configure Switch2 to listen for SXP updates from Switch1.

Task 3: Verify the SXP Session Establishes

Confirm the SXP connection between the two switches reaches an established state.

Task 4: Verify SGT-to-IP Bindings Propagate

Confirm Switch2 learns Employee-PC's SGT-to-IP binding via SXP, despite never seeing an inline SGT tag.

Task 5: Verify SGACL Enforcement Works on Switch2

Apply the same SGACL policy from the earlier lab on Switch2 and confirm it enforces correctly using the SXP-learned binding.

Solution and Verification

Switch1(config)# cts sxp enable
Switch1(config)# cts sxp default password SxpKey2026
Switch1(config)# cts sxp connection peer [Switch2-address] password default mode local speaker

-- "speaker" means Switch1 will advertise
-- its bindings TO the peer -- it does not
-- expect to receive bindings back over
-- this session

Switch2(config)# cts sxp enable
Switch2(config)# cts sxp default password SxpKey2026
Switch2(config)# cts sxp connection peer [Switch1-address] password default mode local listener

-- "listener" means Switch2 only receives
-- bindings, matching the speaker role
-- Switch1 was configured with

Switch1# show cts sxp connections

SXP Peer IP    Source IP      Conn Status
[Switch2-addr] [Switch1-addr]  On
-- Connection established, confirmed by
-- "On" status

Switch2# show cts sxp sgt-map

SGT   IP Address
10    192.168.100.10
-- Switch2 learned Employee-PC's SGT (10)
-- mapped to its IP address purely through
-- the SXP session -- no inline tagging
-- hardware was involved anywhere in this
-- propagation path

Switch2(config)# cts role-based sgt-map [SharedServer-address] sgt 30
Switch2(config)# ip access-list role-based DENY-GUESTS
Switch2(config-rb-acl)# deny ip
Switch2(config-rb-acl)# exit
Switch2(config)# cts role-based permissions from 20 to 30 DENY-GUESTS

-- Identical policy structure to the
-- earlier SGT lab, applied on a switch
-- that never handles an inline SGT tag
-- for this traffic at all

Guest-PC> ping SharedServer
-- (Guest-PC's SGT 20 binding also
--  propagated via SXP from Switch1)

Request timed out.
Success rate is 0 percent (0/5)
-- Enforcement on Switch2 works correctly,
-- using only the SXP-learned binding
-- information rather than any inline tag
-- carried in the packet itself

Key Takeaway

SXP separates the propagation of SGT-to-IP binding information from the inline tagging mechanism itself — a switch running SXP as a listener can enforce SGACL policy using IP-based lookups against learned bindings, entirely independent of whether it has the hardware capability to read or write an inline SGT tag, making SXP the standard mechanism for extending SGT-based segmentation across a mixed environment of SGT-capable and legacy infrastructure.

Written & researched by Dr. Shahin Siami

Related Articles

Hands-On Lab: Configuring EIGRP Stub Routing

This hands-on lab configures a branch router as an EIGRP stub, verifying it advertises only its own connected and summary routes while the hub router correctly avoids querying the stub during a topology change elsewhere in the network.

Continue

Hands-On Lab: Configuring EIGRP Named Mode

This hands-on lab reconfigures a classic EIGRP setup into EIGRP named mode, organizing address-family and interface-specific configuration into a more structured hierarchy, and verifies functional equivalence with the classic configuration style used throughout earlier EIGRP labs in this series.

Continue

Hands-On Lab: Configuring ERSPAN Across a Routed Network

This hands-on lab configures Encapsulated RSPAN (ERSPAN) to mirror traffic across a Layer 3-routed network rather than a single Layer 2 trunk, extending the RSPAN concept from the previous lab beyond the boundaries of a single VLAN or switched domain.

Continue

Hands-On Lab: Configuring RSPAN Across Switches

This hands-on lab configures Remote SPAN (RSPAN) using a dedicated RSPAN VLAN carried across a trunk, allowing traffic mirrored on one switch to be monitored by a capture device connected to an entirely different switch, extending the local SPAN concept covered in an earlier lab across the network.

Continue

Hands-On Lab: Configuring In-Service Software Upgrade (ISSU) on a Stack

This hands-on lab performs an In-Service Software Upgrade across a StackWise stack, upgrading each member's IOS image one at a time while the stack continues forwarding traffic throughout, verifying zero downtime compared to the disruptive reload approach used in earlier IOS upgrade labs.

Continue

Hands-On Lab: Configuring Cisco Catalyst StackWise Traditional Stacking

This hands-on lab configures traditional Catalyst stacking (StackWise) across three switches using stack cables, contrasting its single-tier, chassis-proximity requirement against the StackWise Virtual pair covered in the previous lab, which allows switches to be located much farther apart.

Continue