<?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: Configuring SSO on a pair of 9800-L issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5254020#M280384</link>
    <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;DIV&gt;High Availability: Redundancy management interface has overlapping address with wireless management, this can cause serious network problems&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Modify the command redun-management using non-overlapping addresses.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230078&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;High Availability: Redundancy state indicates a possible problem. Please check status of the other unit&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;RMI configuration was detected, and the current redundancy state indicates a problem. Check the status of the other unit&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230124&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Management: HTTP server does not have an IPv4 access class set. To improve security, it is advisable to set ACL explicitly allowing address that can configure the controller&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;For better WebUI security, set access class with ip http access-class command. For more information: &lt;A href="https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xe-17/221107-filter-traffic-destined-to-cisco-ios-xe.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xe-17/221107-filter-traffic-destined-to-cisco-ios-xe.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230001&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Version: IOS-XE Controller with not recommended code:17.9.4a, please check software download page for the current version for your hardware&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Controller is running not recommended code and should be upgraded, better, similar code is available.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230023&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;NTP: Controller with no valid time source (sync has not happened) or file without NTP information, please check if controller has valid NTP server configured&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;No active time source detected for this controller. It could be incomplete configuration. Command: config time ntp server&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230038&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Management: To prevent WebUI issues while using some large GUI options (VLANs for example), it is advisable to increase the VTY count to 50&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Use the command 'line vty 0 50' to increase the VTY count&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230056&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Management: Service tcp-keepalive in/out, should be enabled to reduce lingering inactive connections to management points&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Add: service tcp-keepalives in/service tcp-keepalives out to configuration&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230065&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Webauth: The Webauth Global parameter map, does not have IPv6 virtual address. It is advisable to add one&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Depending on your client types, it is good idea to define IPv6 virtual address for Webauth. It can reduce redirection errors. Use 'parameter-map type webauth global' config command, then 'virtual-ip ipv6 ADDRESS'&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230085&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;LAG: LAG was detected in use, and port channel load balancing is not set to src-dst-mixed-ip-port. Per best practices, please change both the controller and the switch for optimal port balancing&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Best practices recommend to use command port-channel load-balance src-dst-mixed-ip-port, for best port balancing. This must be configured as well on the switch side&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230129&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Security: Current configuration is vulnerable to CVE-2023-48795/CSCwi59338, Chacha20 should be removed from SSH encryption options&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;CVE-2023-48795 describes a security problem on some SSH extensions present in OpenSSH for specific encryption protocols. It is recommended to remove this option from SSH configuration. Use command: ip ssh server algorithm encryption aes128-gcm@openssh.com aes256-gcm@openssh.com aes128-gcm aes256-gcm aes128-ctr aes192-ctr aes256-ctr.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230140&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Interfaces: More than one Port Channel interface with same allowed VLAN list&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Allowing same VLANs across Port Channels, may cause traffic loop, and possible instability issues. It is advisable to filter out vlans that are not required to be duplicated. Check your topology, as this may depend on switch side configuration as well, and could be fine for your config. Command: switchport trunk allowed vlan&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230057&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;DHCP: If DHCP helper (relay) is defined, the interface should have dhcp relay source interface command pointing to wireless management interface, to avoid asymmetric DHCP routing scenarios. Interfaces: Vlan1&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Add: ip dhcp relay source-interface to the interface SVI/Vlan configuration&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;240020&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;11k: 11k Neighbor List is in use, but dual band is disabled. if not using single-band devices, enable both for best results. WLAN(s): JAYHAWK&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;For best results, it is better to enable dual band support for 11k. This should only be avoided, if single band devices are present on the network. This is part of the WLAN profile&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;250014&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;ARP: ARP proxy is disabled. To save client battery and other performance improvements, it is recommended to enable. Profiles: default-policy-profile&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Go to the policy profile and enable ARP proxy setting. This is available from 17.3&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;250015&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Security: Profile with vlan set to default or 1. This is not recommended, even for AAA override scenarios. Profiles: default-policy-profile&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Go to the policy profile configure a VLAN. Default should only be used on small network, with low security requirements&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;290004&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Syslog: Syslog host is not set (using default broadcast value). For best practices, it is recommended to use a syslog server. AP Profiles: default-ap-profile&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;To ensure data is available for future troubleshooting in case of problems, it is best practices to define a syslog server for all APs on the Join profile&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230026&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;11b: Legacy rate enabled in Global Config . Disabling low data rates/11b can help to optimise the channel utilisation on the 2.4 band. Depending on RF coverage, or if using legacy clients, this may cause problems. Please validate before enforcing the changes, as this may have important RF dependencies.&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;In most scenarios, it is good idea to disable 11b data rates (1,2,5.5,11), as they would use more RF time, and be more sensible to interference, it is advisable to only enable 11g rates, unless you need to support legacy devices. Command:config 802.11b rate disabled X&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230045&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Client Profiling: Device Classification (client profiling) is not globally enabled, it is recommended to use it&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Use Device classification as best practice, to help on troubleshooting, network characterization or problem isolation&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230046&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;RRM: ED-RRM is not in use. It is recommended to enable for enterprise environments. Band(s): 2.4 GHz 5 GHz&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;This is purely a general recommendation, please validate if applicable in your environment. ED-RRM could provide fast reaction to severe RF issues&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230042&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Security: Password Encryption is not enabled. This is optional feature to protect keys/passwords in configuration&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Use password encryption aes command.For more information, check 9800 Best practices guide&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230083&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Tags: For versions 17.6 and higher, it is advisable to use AP tag persistency command, to ensure tags are preserved if AP is temporarily moved to another controller&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Configure ap tag persistency enable, this is specially important for N+1 redundancy scenarios&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;230099&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Rogues: Rogue AP policies and rules should be defined, specially around managed SSIDs&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Rogue rules can improve alerting for possible rogues impersonating managed SSID. It is advisable to enable them. For more information: &lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-3/config-guide/b_wl_17_3_cg/m_classify_rogue_aps_ewlc.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-3/config-guide/b_wl_17_3_cg/m_classify_rogue_aps_ewlc.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;290005&lt;/TD&gt;&lt;TD&gt;&lt;DIV&gt;Monitoring: AP system monitoring statistics are not enabled. To improve AP status visibility it would be recommended to use it. AP Profiles: default-ap-profile&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Action:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Monitor System Statistics is a feature in 17.5 and higher, to enable AP CPU and memory monitoring , you can enable it on AP profile, AP tab, AP statistics section&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;RF Stats WLC Level Summary&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 29 Jan 2025 02:23:04 GMT</pubDate>
    <dc:creator>tdennehy</dc:creator>
    <dc:date>2025-01-29T02:23:04Z</dc:date>
    <item>
      <title>Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253474#M280302</link>
      <description>&lt;P&gt;I am trying to configure what should be a very simple setup.&amp;nbsp; Two 9800-Ls on a bench with a switch in between.&amp;nbsp; They can ping each other when I configure SSO on both boxes, and I can ping the secondary.&amp;nbsp; But neither will ever become the standby.&lt;/P&gt;&lt;P&gt;I'm wondering if there is "something else", that everyone always forgets to do when configuring SSO.&amp;nbsp; Its so simple, just using vlan1 on both, with 192.168.1.x addresses.&lt;/P&gt;&lt;P&gt;Waiting for remote chassis to join&lt;BR /&gt;#######################################################################################&lt;/P&gt;&lt;P&gt;wc01:&lt;/P&gt;&lt;P&gt;interface Port-channel1&lt;BR /&gt;description ** uplink **&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel2&lt;BR /&gt;description ** uplink **&lt;BR /&gt;switchport mode trunk&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;interface TenGigabitEthernet0/1/0&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;no negotiation auto&lt;BR /&gt;no mop enabled&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet0/1/1&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;no negotiation auto&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0&lt;BR /&gt;vrf forwarding Mgmt-intf&lt;BR /&gt;ip address 192.168.1.100 255.255.255.0&lt;BR /&gt;negotiation auto&lt;BR /&gt;no mop enabled&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;ip address 192.168.1.249 255.255.255.0 secondary&lt;BR /&gt;ip address 192.168.1.251 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.1.254&lt;BR /&gt;no mop enabled&lt;BR /&gt;!&amp;nbsp;&lt;BR /&gt;ip tftp source-interface GigabitEthernet0&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.1.254&lt;BR /&gt;ip route vrf Mgmt-intf 0.0.0.0 255.255.255.0 192.168.1.254&lt;BR /&gt;redun-management interface Vlan1 chassis 2 address 192.168.1.249 chassis 1 address 192.168.1.250&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;wc02:&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;interface Port-channel1&lt;BR /&gt;description ** uplink **&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel2&lt;BR /&gt;description ** uplink **&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;&lt;BR /&gt;interface TenGigabitEthernet0/1/0&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;speed 1000 (its a 1gig SFP)&lt;BR /&gt;no negotiation auto&lt;BR /&gt;no snmp trap link-status&lt;BR /&gt;no mop enabled&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface TenGigabitEthernet0/1/1&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;speed 10000&lt;BR /&gt;no negotiation auto&lt;BR /&gt;no snmp trap link-status&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0&lt;BR /&gt;vrf forwarding Mgmt-intf&lt;BR /&gt;ip address 192.168.1.101 255.255.255.0&lt;BR /&gt;negotiation auto&lt;BR /&gt;no mop enabled&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;ip address 192.168.1.250 255.255.255.0 secondary&lt;BR /&gt;ip address 192.168.1.252 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.1.254&lt;BR /&gt;no mop enabled&lt;BR /&gt;!&amp;nbsp;&lt;BR /&gt;!&lt;BR /&gt;ip tftp source-interface GigabitEthernet0&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.1.254&lt;BR /&gt;ip route vrf Mgmt-intf 0.0.0.0 255.255.255.0 192.168.1.254&lt;/P&gt;&lt;P&gt;redun-management interface Vlan1 chassis 1 address 192.168.1.250 chassis 2 address 192.168.1.249&lt;/P&gt;&lt;P&gt;Could I be missing something?&amp;nbsp; This should not be that difficult!!!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 02:42:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253474#M280302</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T02:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253476#M280303</link>
      <description>&lt;P&gt;When I plug in the uplink, I get this output on wc02:&lt;/P&gt;&lt;P&gt;*Jan 27 19:35:29.618: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to up&lt;BR /&gt;*Jan 27 19:35:29.621: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up&lt;BR /&gt;*Jan 27 19:35:30.425: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down&lt;BR /&gt;*Jan 27 19:35:34.150: %RIF_MGR_FSM-6-RMI_GW_DECISION_DEFERRED: Chassis 1 R0/0: rif_mgr: High CPU utilisation on active or standby, deferring action on gateway-down event&lt;BR /&gt;*Jan 27 19:35:54.151: %RIF_MGR_FSM-6-GW_REACHABLE_ACTIVE: Chassis 1 R0/0: rif_mgr: Gateway reachable from Active&lt;BR /&gt;*Jan 27 19:35:56.798: %RIF_MGR_FSM-6-RMI_LINK_UP: Chassis 1 R0/0: rif_mgr: The RMI link is UP.&lt;BR /&gt;*Jan 27 19:35:56.798: %STACKMGR-1-DUAL_ACTIVE_CFG_MSG: Chassis 1 R0/0: stack_mgr: Dual Active Detection link is available now&lt;/P&gt;&lt;P&gt;edh001-001-wc02#sho chassis&lt;BR /&gt;Chassis/Stack Mac Address : 8c1e.806e.9080 - Local Mac Address&lt;BR /&gt;Mac persistency wait time: Indefinite&lt;BR /&gt;Local Redundancy Port Type: Twisted Pair&lt;BR /&gt;H/W Current&lt;BR /&gt;Chassis# Role Mac Address Priority Version State IP&lt;BR /&gt;-------------------------------------------------------------------------------------&lt;BR /&gt;*1 Active 8c1e.806e.9080 1 V02 Ready 169.254.1.250&lt;/P&gt;&lt;P&gt;wc01: (when I plug in the uplinks, changes its name)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;edh001-001-wc01(recovery-mode)_2_RP_0(diag)#&lt;BR /&gt;edh001-001-wc01(recovery-mode)_2_RP_0(diag)#&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 02:47:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253476#M280303</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T02:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253477#M280304</link>
      <description>&lt;P&gt;Both units are Chassis 1?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 02:49:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253477#M280304</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-01-28T02:49:36Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253478#M280305</link>
      <description>&lt;P&gt;I don't know which guide you followed, but when you ener this command, use a vlan that is not on your network, you just want the redundancy management on its own vlan.&amp;nbsp; You don't need to route this. Keep in mind, there are various way's this is done.&amp;nbsp; The docs show different way's. You didn't show all the commands that are required also.&lt;/P&gt;
&lt;P&gt;Also, take a look at this guide, there are others that are good and some videos out there.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;redun-management interface VlanXXX chassis 1 address 192.168.1.250 chassis 2 address 192.168.1.249&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://howiwifi.com/2021/01/17/cisco-9800-rmirp-high-availability-best-practice-configuration/" target="_blank" rel="noopener"&gt;https://howiwifi.com/2021/01/17/cisco-9800-rmirp-high-availability-best-practice-configuration/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.wiresandwi.fi/blog/cisco-wlc-9800-high-availability-sso-rmi-rp-cli-configuration" target="_blank" rel="noopener"&gt;https://www.wiresandwi.fi/blog/cisco-wlc-9800-high-availability-sso-rmi-rp-cli-configuration&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220277-configure-high-availability-sso-on-catal.html#toc-hId-1451838582" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220277-configure-high-availability-sso-on-catal.html#toc-hId-1451838582&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:01:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253478#M280305</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-01-28T03:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253485#M280306</link>
      <description>&lt;P&gt;I tend to watch some videos before I try anything.&amp;nbsp; It's easier to follow at times. The GUI is very easy and you should probably try that first and then wipe the units and try again from the cli.&amp;nbsp; That way you can learn and document both process.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:08:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253485#M280306</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-01-28T03:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253489#M280307</link>
      <description>&lt;P&gt;Share your topology&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:29:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253489#M280307</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-01-28T03:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253493#M280309</link>
      <description>&lt;P&gt;Ugghhh.&amp;nbsp; I hope not.&amp;nbsp; &amp;nbsp;I will go look!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:52:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253493#M280309</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T03:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253494#M280310</link>
      <description>&lt;P&gt;Two wlcs on a bench, side by side with a switch configured with uplinks.&amp;nbsp; Literally a flat network.&amp;nbsp; I have been messing with it all day, and I have gotten this to work in production boxes.&amp;nbsp; For some reason I'm having an issue with the two on the bench with a switch with vlan 1&amp;nbsp;@ 192.168.1.254.&lt;/P&gt;&lt;P&gt;The two WLCs have IPs in the .249&amp;nbsp; .250&amp;nbsp; .251 and .252&amp;nbsp; &amp;nbsp; Its the simplest of networks, so I figured I missed something very simple.&amp;nbsp; Leo suggests both Chassis 1, so I will go look at that.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:58:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253494#M280310</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T03:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253495#M280311</link>
      <description>&lt;P&gt;I am following this link:&amp;nbsp;&amp;nbsp;&lt;A href="https://justdowifi.blogspot.com/search?updated-max=2023-08-28T17:44:00-07:00&amp;amp;max-results=7" target="_blank"&gt;https://justdowifi.blogspot.com/search?updated-max=2023-08-28T17:44:00-07:00&amp;amp;max-results=7&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 03:59:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253495#M280311</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T03:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253496#M280312</link>
      <description>&lt;P&gt;edh001-001-wc02#sho chassis&lt;BR /&gt;Chassis/Stack Mac Address : 8c1e.806e.9080 - Local Mac Address&lt;BR /&gt;Mac persistency wait time: Indefinite&lt;BR /&gt;Local Redundancy Port Type: Twisted Pair&lt;BR /&gt;H/W Current&lt;BR /&gt;Chassis# Role Mac Address Priority Version State IP&lt;BR /&gt;-------------------------------------------------------------------------------------&lt;BR /&gt;*1 Active 8c1e.806e.9080 1 V02 Ready 169.254.1.250&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;edh001-001-wc01#sho chassis&lt;BR /&gt;Chassis/Stack Mac Address : 687d.b4fd.4640 - Local Mac Address&lt;BR /&gt;Mac persistency wait time: Indefinite&lt;BR /&gt;Local Redundancy Port Type: Twisted Pair&lt;BR /&gt;H/W Current&lt;BR /&gt;Chassis# Role Mac Address Priority Version State IP&lt;BR /&gt;-------------------------------------------------------------------------------------&lt;BR /&gt;*2 Active 687d.b4fd.4640 2 V02 Ready 169.254.1.249&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:02:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253496#M280312</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T04:02:39Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253500#M280313</link>
      <description>&lt;P&gt;I have gotten this to work in the past, but for some reason, I cannot get it to work on the bench.&amp;nbsp; I figured I missed a vrf or something.&amp;nbsp; The last time I have touched a pair of 9800s was a year ago, and I'm trying to refresh my memory on how to do it and I cannot get it to work.&amp;nbsp; I have followed this link before with success:&amp;nbsp;&amp;nbsp;&lt;A href="https://justdowifi.blogspot.com/search?updated-max=2023-08-28T17:44:00-07:00&amp;amp;max-results=7" target="_blank"&gt;https://justdowifi.blogspot.com/search?updated-max=2023-08-28T17:44:00-07:00&amp;amp;max-results=7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;There must be something I am missing, and its going to be blatantly stupid when I find it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:06:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253500#M280313</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T04:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253502#M280314</link>
      <description>&lt;P&gt;Switch config:&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface Port-channel1&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;!&lt;BR /&gt;interface Port-channel2&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;interface GigabitEthernet0/25&amp;nbsp; &amp;lt;wlc01&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/26&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;channel-group 1 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/27&amp;nbsp; &amp;lt;- WLC02&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet0/28&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;switchport nonegotiate&lt;BR /&gt;logging event trunk-status&lt;BR /&gt;logging event bundle-status&lt;BR /&gt;channel-group 2 mode on&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;description bench network&lt;BR /&gt;ip address 192.168.1.254 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:09:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253502#M280314</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T04:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253503#M280315</link>
      <description>&lt;P&gt;&lt;SPAN&gt;utilisation on active or standby, deferring action on gateway-down event &amp;lt;&amp;lt;-&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;This important,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;RMI and WMI in same subnet&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In SW do you config&amp;nbsp; SVI for mgmt VLAN?&lt;/P&gt;
&lt;P&gt;RMI of both unit must point this IP&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:12:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253503#M280315</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-01-28T04:12:13Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253504#M280316</link>
      <description>&lt;P&gt;I bet.... you try to just connect the RP ports direct?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:18:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253504#M280316</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2025-01-28T04:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253509#M280320</link>
      <description>&lt;P&gt;This SSO, there must be no PO from SW toward both WLC!!&lt;/P&gt;
&lt;P&gt;This wrong,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need single link from SW to each of wlc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That make issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 04:36:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253509#M280320</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-01-28T04:36:31Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253557#M280328</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Also validate the&lt;STRONG&gt; configuration&lt;/STRONG&gt; of the (primary) 9800-L controller using the CLI command &lt;FONT color="#008000"&gt;&lt;STRONG&gt;show tech &lt;U&gt;wireless&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; (not a simple &lt;FONT color="#FF0000"&gt;&lt;EM&gt;show tech&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;) and feed the output from that into&amp;nbsp;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 07:45:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253557#M280328</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-01-28T07:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253565#M280330</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1065752"&gt;@MHM Cisco World&lt;/a&gt;&amp;nbsp;- all of our 9800 HA SSO pairs run on port channels - it's part of the standard HA design&lt;BR /&gt;It's shown in all the guides like page 45 &amp;amp; 49 in&amp;nbsp;&lt;BR /&gt;&lt;A href="https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2023/pdf/BRKEWN-2846.pdf" target="_blank"&gt;https://www.ciscolive.com/c/dam/r/ciscolive/global-event/docs/2023/pdf/BRKEWN-2846.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 08:03:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253565#M280330</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2025-01-28T08:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253621#M280343</link>
      <description>&lt;P&gt;Friend&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your link is correct but check it'&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The PO is from WLC to SW&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In his case PO is from SW to both WLC !!!!&lt;/P&gt;
&lt;P&gt;That not work.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 10:22:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253621#M280343</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-01-28T10:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253829#M280357</link>
      <description>&lt;P&gt;Yes, RMI and WMI in same subnet.&amp;nbsp; VLAN 1.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Switch SVI is vlan1, IP = 192.168.1.254&lt;/P&gt;&lt;P&gt;As soon as I plug the interfaces to the switch, the switch name changes to the one in the output in the thread.&amp;nbsp; I'm not sure what I'm missing.&lt;/P&gt;&lt;P&gt;The interfaces in trunks and POs are supported.&amp;nbsp; &amp;nbsp; I guess my next step is to create another vlan and assign interfaces for SSO in there to see if that fixes it.&amp;nbsp; This is ridiculous, its the most simple config and I must be missing something very, very basic.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 15:54:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253829#M280357</guid>
      <dc:creator>tdennehy</dc:creator>
      <dc:date>2025-01-28T15:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring SSO on a pair of 9800-L issue</title>
      <link>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253835#M280359</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291632"&gt;@tdennehy&lt;/a&gt;&amp;nbsp;wrote :&lt;EM&gt; &amp;gt;....I guess my next step is to create another vlan and assign interfaces for SSO in there to see if that fixes it.&amp;nbsp; This is ridiculous, its the most simple config and I must be missing something very, very basic.&lt;/EM&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Well in general it is not advises to stick to vlan1 for all 9800 operations and use&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Remember to always use the &lt;STRONG&gt;WirelessAnalyzer&lt;/STRONG&gt; procedure when configuring the 9800 ; it is &lt;STRONG&gt;vital&lt;/STRONG&gt; for these cases.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;I repeat it here :&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;using the CLI command&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#008000"&gt;&lt;STRONG&gt;show tech&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;U&gt;wireless&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;(not a simple&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#FF0000"&gt;&lt;EM&gt;show tech&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;SPAN&gt;) and feed the output from that into&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cway.cisco.com/wireless-config-analyzer/" target="_blank" rel="nofollow noopener noreferrer"&gt;Wireless Config Analyzer&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2025 16:00:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/configuring-sso-on-a-pair-of-9800-l-issue/m-p/5253835#M280359</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-01-28T16:00:18Z</dc:date>
    </item>
  </channel>
</rss>

