<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ios-Xe on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/ios-xe/</link><description>Recent content in Ios-Xe on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/ios-xe/index.xml" rel="self" type="application/rss+xml"/><item><title>The TACACS+ Lockout That Taught Me Three Things About IOS-XE AAA</title><link>https://blog.it-learn.io/posts/2026-05-13-tacacs-lockout-ios-xe-aaa-lessons/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-05-13-tacacs-lockout-ios-xe-aaa-lessons/</guid><description>&lt;p&gt;A short engineering story about the kind of failure that humbles you, and the diagnostic process that turns a humiliation into a useful artifact.&lt;/p&gt;
&lt;p&gt;In the &lt;a href="https://blog.it-learn.io/posts/2026-05-12-cisco-ise-automation-ansible-claude-deployment/"&gt;previous post&lt;/a&gt; I walked through building a Cisco ISE 3.4 deployment as code in one evening. End-to-end working: AD-integrated wireless 802.1X, MAB for IoT, TACACS+ for device admin. Smoke tests green. Repo public. Felt good.&lt;/p&gt;
&lt;p&gt;A few sessions later I went back to tighten the screws — replace the broad &lt;code&gt;PermitAllCommands&lt;/code&gt; TACACS shell with &lt;strong&gt;per-command authorization&lt;/strong&gt;, the proper way: Helpdesk gets &lt;code&gt;show / ping / traceroute&lt;/code&gt;, NetworkOps gets safe troubleshooting verbs, Admins get everything. The kind of thing audit teams ask for.&lt;/p&gt;</description></item></channel></rss>