<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>9800 on Boldly Going Nowhere</title>
    <link>https://martynrees.github.io/tags/9800/</link>
    <description>Recent content in 9800 on Boldly Going Nowhere</description>
    <image>
      <title>Boldly Going Nowhere</title>
      <url>https://martynrees.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://martynrees.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.140.2</generator>
    <language>en</language>
    <lastBuildDate>Tue, 10 Oct 2023 12:21:35 +1030</lastBuildDate>
    <atom:link href="https://martynrees.github.io/tags/9800/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>9800 WLC Cat9k AP Default Console Baud Rate</title>
      <link>https://martynrees.github.io/post/console-speed/</link>
      <pubDate>Tue, 10 Oct 2023 12:21:35 +1030</pubDate>
      <guid>https://martynrees.github.io/post/console-speed/</guid>
      <description>&lt;p&gt;The current long term 17.12 release of the IOS-XE 9800 WLC is feature packed, but tucked away in the &lt;a href=&#34;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#behavior-changes&#34;&gt;release notes&lt;/a&gt; is a one liner that is sure to catch people out in the near future(or me the other day): &lt;br /&gt;
&lt;em&gt;&lt;strong&gt;From this release, the default console baud rate of the 802.11AX APs is changed from 9600 bps to 115200 bps.&lt;/strong&gt;&lt;/em&gt;
&lt;img alt=&#34;115200&#34; loading=&#34;lazy&#34; src=&#34;https://martynrees.github.io/img/115200.png&#34;&gt;
&lt;strong&gt;What does this mean?&lt;/strong&gt; &lt;br /&gt;
Well, digging a  bit deeper, it only covers the Cat9k range of AP&amp;rsquo;s, so 9120, 9130,9136, 916x, etc&lt;br /&gt;
&lt;em&gt;&lt;strong&gt;AND&lt;/strong&gt;&lt;/em&gt; &lt;br /&gt;
It &lt;strong&gt;only&lt;/strong&gt; impacts new (or factory reset) AP&amp;rsquo;s when they join the controller running 17.12 or higher. So if AP&amp;rsquo;s are already joined to the controller and are upgraded from 17.9.x to 17.12.x then they will still use the old 9600bps rate, but then if you add a new AP to the controller, that will use the new setting of 115200bps. &lt;br /&gt;
If an upgraded AP is set back to factory default though and joins the controller again, it will assume the new 115200bps config. So you could/will end up with some AP&amp;rsquo;s on the old 9600bps config and some on the new 115200bps config. Or, once upgraded to 17.12 or higher then factory reset all AP&amp;rsquo;s from the CLI/GUI (not recomended unless you are bored and have a lot of time and a real reason to do this), and then you&amp;rsquo;ll have a standard across the board, no matter which AP you connect to (that&amp;rsquo;s a Cat9k AP anyway, Wave1/2 are not impacted by this!).&lt;br /&gt;
&lt;strong&gt;WHY?&lt;/strong&gt; &lt;br /&gt;
Turns out the reasoning for this is simple, it&amp;rsquo;s so that the AP can boot faster!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
