<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: AP 9120 temperature in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953622#M262533</link>
    <description>&lt;P&gt;The datasheet specs are for the environment the AP is installed in, not the AP internal temperatures.&lt;/P&gt;
&lt;P&gt;The internal temperatures depend on where the sensor is measuring - CPU is usually the hottest.&lt;BR /&gt;You can tell from those logs "Current-status : good" that the temp is within normal operating thresholds for that component so nothing to worry about.&lt;/P&gt;
&lt;P&gt;For a better understanding of Spatial Streams take a look at:&lt;BR /&gt;&lt;A href="https://www.netally.com/network-performance/spatial-streams/" target="_blank" rel="noopener"&gt;https://www.netally.com/network-performance/spatial-streams/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.mbreviews.com/what-are-spatial-streams/" target="_blank" rel="noopener"&gt;https://www.mbreviews.com/what-are-spatial-streams/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.digitalairwireless.com/articles/blog/wi-fi-spatial-streaming-explained" target="_blank" rel="noopener"&gt;https://www.digitalairwireless.com/articles/blog/wi-fi-spatial-streaming-explained&lt;/A&gt;&lt;BR /&gt;You can find plenty of other blogs, videos etc with more info.&lt;BR /&gt;Short answer 2x2 = lower speed and capacity.&lt;/P&gt;
&lt;P&gt;&amp;gt; "&lt;SPAN&gt;Many&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;IPad clients&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;have complained about bad connection&lt;/SPAN&gt;"&lt;BR /&gt;Can you define bad connection?&lt;BR /&gt;This could mean slow, high packet loss, frequent disconnection etc etc etc.&amp;nbsp; You need to be really specific about the problem.&lt;BR /&gt;Again plenty of docs to refer to but at a very high level make sure software is up to date (refer to TAC recommended link below) and make sure client OS and drivers are up to date.&lt;BR /&gt;Check your WLC config with the Config Analyzer (link below).&lt;BR /&gt;Make sure clients are using 5GHz bands not 2.4GHz.&lt;BR /&gt;If you're trying to use 80MHz or 160MHz channel width that's generally pointless and more likely to cause problems - reduce to 40MHz channel width.&lt;BR /&gt;Make sure you have enough AP capacity for the number of clients and the bandwidth they're using.&lt;BR /&gt;Optimise the data rates to improve airtime utilisation.&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Lowdatarates" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Lowdatarates&lt;/A&gt;&lt;BR /&gt;Also refer to:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/dam/en_us/solutions/industries/docs/education/cisco_wlan_design_guide.pdf" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/dam/en_us/solutions/industries/docs/education/cisco_wlan_design_guide.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 05 Nov 2023 12:42:34 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2023-11-05T12:42:34Z</dc:date>
    <item>
      <title>AP 9120 temperature</title>
      <link>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4952451#M262423</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Many of 9120 APs shows very high temperature. Even if schools are closed this week, the APs still generate logs about very high temperature. Here is an example.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ov  1 19:26:44 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 60 C, Highest-recorded : 63 C
Nov  1 19:26:44 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 46 C, Highest-recorded : 49 C
Nov  1 19:56:45 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 60 C, Highest-recorded : 63 C
Nov  1 19:56:45 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 46 C, Highest-recorded : 49 C

Nov  2 00:26:52 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 60 C, Highest-recorded : 63 C
Nov  2 00:26:52 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 46 C, Highest-recorded : 49 C
Nov  2 00:56:52 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 60 C, Highest-recorded : 63 C
Nov  2 00:56:52 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 46 C, Highest-recorded : 49 C&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;What is the difference between local and remote. These APs are in schools where the room temperature is not exeeding 22 Celsius degrees.&lt;/P&gt;&lt;P&gt;This is a different AP:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Nov  2 04:28:34 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 47 C, Highest-recorded : 51 C
Nov  2 04:58:34 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 60 C, Highest-recorded : 64 C
Nov  2 04:58:34 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 47 C, Highest-recorded : 51 C
Nov  2 05:28:35 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 59 C, Highest-recorded : 64 C&lt;/LI-CODE&gt;&lt;P&gt;According to Cisco:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Cisco Catalyst 9120AXI

●  Nonoperating (storage) temperature: -22° to 158°F (-30° to 70°C)
●  Nonoperating (storage) altitude test: 25˚C, 15,000 ft.
●  Operating temperature: 32° to 122°F (0° to 50°C)
●  Operating humidity: 10% to 90% (noncondensing)
●  Operating altitude test: 40˚C, 9843 ft.
Note: When the ambient operating temperature exceeds 40°C, the access point will shift from 4x4 to 2x2 on both the 2.4-GHz and 5-GHz radios, uplink Ethernet will downgrade to 1 Gigabit Ethernet; however, the USB interface will remain enabled

Cisco Catalyst 9120AXE and 9120AXP

●  Nonoperating (storage) temperature: -22° to 158°F (-30° to 70°C)
●  Nonoperating (storage) altitude test: 25˚C, 15,000 ft.
●  Operating temperature: -4° to 122°F (-20° to 50°C)
●  Operating humidity: 10% to 90% (noncondensing)
●  Operating altitude test: 40˚C, 9843 ft.&lt;/LI-CODE&gt;&lt;P&gt;What is the effect of changing from &lt;STRONG&gt;4x4&lt;/STRONG&gt; to &lt;STRONG&gt;2x2&lt;/STRONG&gt; on clients. Many &lt;STRONG&gt;IPad clients&lt;/STRONG&gt; have complained about bad connection specially in classrooms with 9120 AP!&lt;/P&gt;&lt;P&gt;Here is another AP log:&lt;/P&gt;&lt;LI-CODE lang="python"&gt; 2 07:25:15 root: Thermal-Control-Unit - Sensor : Local , Current-status : good, Current-Temperature: 61 C, Highest-recorded : 66 C
Nov  2 07:25:15 root: Thermal-Control-Unit - Sensor : Remote, Current-status : good, Current-Temperature: 47 C, Highest-recorded : 52 C&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2023 07:58:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4952451#M262423</guid>
      <dc:creator>Moudar</dc:creator>
      <dc:date>2023-11-02T07:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: AP 9120 temperature</title>
      <link>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953622#M262533</link>
      <description>&lt;P&gt;The datasheet specs are for the environment the AP is installed in, not the AP internal temperatures.&lt;/P&gt;
&lt;P&gt;The internal temperatures depend on where the sensor is measuring - CPU is usually the hottest.&lt;BR /&gt;You can tell from those logs "Current-status : good" that the temp is within normal operating thresholds for that component so nothing to worry about.&lt;/P&gt;
&lt;P&gt;For a better understanding of Spatial Streams take a look at:&lt;BR /&gt;&lt;A href="https://www.netally.com/network-performance/spatial-streams/" target="_blank" rel="noopener"&gt;https://www.netally.com/network-performance/spatial-streams/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.mbreviews.com/what-are-spatial-streams/" target="_blank" rel="noopener"&gt;https://www.mbreviews.com/what-are-spatial-streams/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.digitalairwireless.com/articles/blog/wi-fi-spatial-streaming-explained" target="_blank" rel="noopener"&gt;https://www.digitalairwireless.com/articles/blog/wi-fi-spatial-streaming-explained&lt;/A&gt;&lt;BR /&gt;You can find plenty of other blogs, videos etc with more info.&lt;BR /&gt;Short answer 2x2 = lower speed and capacity.&lt;/P&gt;
&lt;P&gt;&amp;gt; "&lt;SPAN&gt;Many&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;IPad clients&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;have complained about bad connection&lt;/SPAN&gt;"&lt;BR /&gt;Can you define bad connection?&lt;BR /&gt;This could mean slow, high packet loss, frequent disconnection etc etc etc.&amp;nbsp; You need to be really specific about the problem.&lt;BR /&gt;Again plenty of docs to refer to but at a very high level make sure software is up to date (refer to TAC recommended link below) and make sure client OS and drivers are up to date.&lt;BR /&gt;Check your WLC config with the Config Analyzer (link below).&lt;BR /&gt;Make sure clients are using 5GHz bands not 2.4GHz.&lt;BR /&gt;If you're trying to use 80MHz or 160MHz channel width that's generally pointless and more likely to cause problems - reduce to 40MHz channel width.&lt;BR /&gt;Make sure you have enough AP capacity for the number of clients and the bandwidth they're using.&lt;BR /&gt;Optimise the data rates to improve airtime utilisation.&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Lowdatarates" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#Lowdatarates&lt;/A&gt;&lt;BR /&gt;Also refer to:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-campus-lan-wlan-design-guide.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/dam/en_us/solutions/industries/docs/education/cisco_wlan_design_guide.pdf" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/dam/en_us/solutions/industries/docs/education/cisco_wlan_design_guide.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 12:42:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953622#M262533</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-11-05T12:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: AP 9120 temperature</title>
      <link>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953746#M262560</link>
      <description>&lt;P&gt;What makes me think about these logs first is that they are coming much often, so I need to exclude that these logs mean a problem.&lt;/P&gt;&lt;P&gt;If the logs about temperature are excluded, what about this last one which also comes often:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Nov  4 12:56:47 kernel: [*11/04/2023 12:56:47.2736] chatter: simple_action packet too short (expected 0xec00, payload 28)
Nov  4 13:08:42 kernel: [*11/04/2023 13:08:42.2008] chatter: simple_action packet too short (expected 0xd300, payload 18)
Nov  4 15:32:16 kernel: [*11/04/2023 15:32:16.5033] chatter: simple_action packet too short (expected 0x3200, payload 18)
Nov  4 20:40:36 kernel: [*11/04/2023 20:40:36.9308] chatter: simple_action packet too short (expected 0x2700, payload 18)
Nov  4 20:48:32 kernel: [*11/04/2023 20:48:32.8159] chatter: simple_action packet too short (expected 0x2000, payload 34)
Nov  4 20:48:38 kernel: [*11/04/2023 20:48:38.8579] chatter: simple_action packet too short (expected 0x5700, payload 34)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 09:01:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953746#M262560</guid>
      <dc:creator>Moudar</dc:creator>
      <dc:date>2023-11-05T09:01:05Z</dc:date>
    </item>
    <item>
      <title>Re: AP 9120 temperature</title>
      <link>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953800#M262564</link>
      <description>&lt;P&gt;Might be significant, might not be.&amp;nbsp; If you start looking at debug logs you'll see all sorts of messages that only have meaning to the software developers.&amp;nbsp; If you want those investigated then open a TAC case but they'll probably say to ignore those.&lt;/P&gt;
&lt;P&gt;Did you make sure your software is up to date?&lt;BR /&gt;Currently AireOS should be 8.10.190.0 and current IOS-XE (9800) should be 17.9.4 + SMUs + APSPs but always refer to TAC recommended for latest info.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 12:46:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-9120-temperature/m-p/4953800#M262564</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-11-05T12:46:18Z</dc:date>
    </item>
  </channel>
</rss>

