- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 06:55 AM
Hello,
I am currently deploying a cluster of 2 9800CL controllers, and the customer asks me bundle Gi1 and Gi2 in a Port-Channel to use it as the WMI.
I didn't find anything talking about that case in the Configuration Guide, the HA SSO Deployment guide and the best practices aswell.
I tried to set up this architecture in my lab, but this is what happened when I tried :
(config-if)#switchport mode trunk
Command rejected: Po1 is not a switching port.
(config-if)#switchport
Command rejected: Not a convertible port.
I don't know if there is a need to configure something on the VMWare side, or if it's possible at all.
Does anyone had this case already ?
Thank for reading me.
Nicolas
Solved! Go to Solution.
- Labels:
-
Wireless LAN Controller
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 05:37 AM
Bundling interfaces on 9800-CL is completely pointless - it's a virtual port!
If you want physical port redundancy then that should be done on the ports between your ESX server and the physical switch(es) - not on the VM.
The reason you got that error is because G1 and G2 have specific functions on CL. G1 is the management interface - like Gig0 on a physical 9800 - it's not intended to be used for customer traffic at all - purely for WLC out of band management access. G2 is for WMI use and supports trunk and VLANs. So in the same way you could not form an etherchannel with Gi0 and Te0/0/0 on a 9800-80, you cannot form an etherchannel from G1 and G2 on 9800-CL.
"By default, the 9800-CL comes with three network interfaces. Below is an example of interface mapping:
● GigabitEthernet1 à Device management interface: Map it to the out-of-band management network. This is the equivalent of the service port on the physical appliance.
● GigabitEthernet2 à Wireless management interface: Map it to the network to reach APs and services. Usually this interface is a trunk to carry multiple VLANs.
● GigabitEthernet3 à High Availability interface: Map it to a separate network for peer-to-peer communication for HA SSO. This is the equivalent of the RP port. This port is not needed if HA SSO is not going to be configured.
Note: Do not connect two interfaces to a single network, as that may cause network loops. When a trunk port is used, you must either prune VLANs from vCenter or have the GigabitEthernet interfaces in a different vSwitch."
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 08:22 AM - edited 07-27-2023 08:22 AM
- That isn't supported , you need to stick to the native HA SSO setup for the two 9800CL controller which is supported ,
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 08:34 AM
Thanks Marce for the reply, that's what I thought.
It is a case of Multi Chassis LAG, right ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 09:59 AM
>....It is a case of Multi Chassis LAG, right ?
Right ,
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 05:37 AM
Bundling interfaces on 9800-CL is completely pointless - it's a virtual port!
If you want physical port redundancy then that should be done on the ports between your ESX server and the physical switch(es) - not on the VM.
The reason you got that error is because G1 and G2 have specific functions on CL. G1 is the management interface - like Gig0 on a physical 9800 - it's not intended to be used for customer traffic at all - purely for WLC out of band management access. G2 is for WMI use and supports trunk and VLANs. So in the same way you could not form an etherchannel with Gi0 and Te0/0/0 on a 9800-80, you cannot form an etherchannel from G1 and G2 on 9800-CL.
"By default, the 9800-CL comes with three network interfaces. Below is an example of interface mapping:
● GigabitEthernet1 à Device management interface: Map it to the out-of-band management network. This is the equivalent of the service port on the physical appliance.
● GigabitEthernet2 à Wireless management interface: Map it to the network to reach APs and services. Usually this interface is a trunk to carry multiple VLANs.
● GigabitEthernet3 à High Availability interface: Map it to a separate network for peer-to-peer communication for HA SSO. This is the equivalent of the RP port. This port is not needed if HA SSO is not going to be configured.
Note: Do not connect two interfaces to a single network, as that may cause network loops. When a trunk port is used, you must either prune VLANs from vCenter or have the GigabitEthernet interfaces in a different vSwitch."
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 06:14 AM
Hello Richard,
Thanks for the very complete answer.
Indeed, that was my opinion, that bundling virtual interface is useless, but even after telling that to the customer, he insisted about that. Also, as a junior I have a lack of assurance to tell him to follow my advices.
I knew about the Gi1 being SP, Gi2 WMI and Gi3 RP, but even after telling him that, he insisted, so I wanted to be sure.
Thanks again for taking the time to elaborate a complete and sourced answer.
Have a good day
