<?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 Cat9548 vs Cat9516 SWV console session differences in Switching</title>
    <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627329#M525411</link>
    <description>&lt;P&gt;We are doing switch testing in a network with C9548 and C9516 SWV-stacked switches (2 switches per stack).&amp;nbsp; All switches are currently running 16.12.04.&amp;nbsp; We notice a difference in behavior between the two models.&amp;nbsp; On the 9548 stacks, when we console into the Standby switch, we get a switch prompt with the switch's hostname with a "-stby" suffix.&amp;nbsp; You cannot enter any commands at this prompt, the CLI just tells you it's the standby switch.&lt;/P&gt;
&lt;P&gt;But, when we console into either switch in a 9516 stack, both console ports work identically, there is no "-stby" suffix on the standby's switch prompt and you can execute commands at will on the standby.&lt;/P&gt;
&lt;P&gt;So we're just trying to understand if this is expected behavior?&amp;nbsp; If so, why do switches in the same family behave so differently?&amp;nbsp; If not, can anyone provide a clue what might be different between the 9548 &amp;amp; 9516 stacks that could cause this behavior?&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jun 2022 16:30:04 GMT</pubDate>
    <dc:creator>RB6502</dc:creator>
    <dc:date>2022-06-07T16:30:04Z</dc:date>
    <item>
      <title>Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627329#M525411</link>
      <description>&lt;P&gt;We are doing switch testing in a network with C9548 and C9516 SWV-stacked switches (2 switches per stack).&amp;nbsp; All switches are currently running 16.12.04.&amp;nbsp; We notice a difference in behavior between the two models.&amp;nbsp; On the 9548 stacks, when we console into the Standby switch, we get a switch prompt with the switch's hostname with a "-stby" suffix.&amp;nbsp; You cannot enter any commands at this prompt, the CLI just tells you it's the standby switch.&lt;/P&gt;
&lt;P&gt;But, when we console into either switch in a 9516 stack, both console ports work identically, there is no "-stby" suffix on the standby's switch prompt and you can execute commands at will on the standby.&lt;/P&gt;
&lt;P&gt;So we're just trying to understand if this is expected behavior?&amp;nbsp; If so, why do switches in the same family behave so differently?&amp;nbsp; If not, can anyone provide a clue what might be different between the 9548 &amp;amp; 9516 stacks that could cause this behavior?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 16:30:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627329#M525411</guid>
      <dc:creator>RB6502</dc:creator>
      <dc:date>2022-06-07T16:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627451#M525432</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Maybe someone accidentally has enabled standby console access using this command "standby console enable" on the 9516s. So, you may want to try and disable it with "&lt;STRONG&gt;no standby console enable"&amp;nbsp;&lt;/STRONG&gt;and then test again.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 19:46:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627451#M525432</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2022-06-07T19:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627509#M525442</link>
      <description>&lt;P&gt;Avoid using 16.12.4 on 9300/9400/9500/9600.&amp;nbsp; It is a very toxic release.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 23:02:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627509#M525442</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2022-06-07T23:02:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627544#M525457</link>
      <description>&lt;P&gt;Thanks Reza, will try it.&amp;nbsp; But I think the actual command sequence I need is:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Switch(config)# redundancy&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Switch(config-red)# main-cpu&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Switch(config-r-mc)# standby console enable&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 01:27:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4627544#M525457</guid>
      <dc:creator>RB6502</dc:creator>
      <dc:date>2022-06-08T01:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4628020#M525505</link>
      <description>&lt;P&gt;Well, we tried those commands today &amp;amp; there was no difference in operation.&amp;nbsp; Wondering if maybe that's a bug in this IOS version.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 16:39:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4628020#M525505</guid>
      <dc:creator>RB6502</dc:creator>
      <dc:date>2022-06-08T16:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cat9548 vs Cat9516 SWV console session differences</title>
      <link>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4628111#M525509</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Well, we tried those commands today &amp;amp; there was no difference in operation.&amp;nbsp; Wondering if maybe that's a bug in this IOS version.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It could be, but before you upgrade open a ticket with TAC as they may have more info on this issue.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;HTH&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 20:02:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/cat9548-vs-cat9516-swv-console-session-differences/m-p/4628111#M525509</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2022-06-08T20:02:02Z</dc:date>
    </item>
  </channel>
</rss>

