cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
7304
Views
3
Helpful
7
Replies

9800-CL VLAN interfaces

SamBurgess44786
Frequent Visitor
Frequent Visitor

Hello Cisco Community,

I am building a 9800-CL which is running on ESXi but I am struggling to reach any of the configured VLAN interfaces from our core switches (except for the management(VLAN50)).

My thinking was the first vWLC port Gi1 would be routed for management purposes and the second Gi2 would be a trunk carrying all the AP control and data traffic, however this trunk configuration doesn't seem to be working. The only way I can get connectivity from my core to any other VLAN except management is to configure a second Gi2 port as routed and stick a static route in the vWLC. I also don't understand why the routed port has to be in a separate subnet to my SVI, so even then, despite being able to ping the interface, I still can't get to my SVI. 

There are clearly some gaps in my understanding here so any help would be appreciated.

IntVLAN8.pngEth2.pngVMsettings.pngVMnetwork.pngpings.png

I do recognise that in the pictures there is a trunk on Gi2 and the network adapter in vSphere is in access mode. I have tried changing Gi2 to access but saw no difference. Do I need to get our VMware guys to create a new trunked network adapter for me to use?

Thanks 

 

1 Accepted Solution

Accepted Solutions

Hi @SamBurgess44786 

 You are right related to the ports:

  • Gigabit1: Out of Band Management (Service Port)
  • Gigabit2: Main Network Interface for client traffic
  • Gigabit3: Heartbeat interface for SSO HA

But in order to support trunk, which interface must be connected in a separated vSwitch.

You may check this guide.

https://www.wifireference.com/2019/08/24/cisco-catalyst-9800-cl-deployment-guide/

 

View solution in original post

7 Replies 7

Hi @SamBurgess44786 

 You are right related to the ports:

  • Gigabit1: Out of Band Management (Service Port)
  • Gigabit2: Main Network Interface for client traffic
  • Gigabit3: Heartbeat interface for SSO HA

But in order to support trunk, which interface must be connected in a separated vSwitch.

You may check this guide.

https://www.wifireference.com/2019/08/24/cisco-catalyst-9800-cl-deployment-guide/

 

Hi @Flavio Miranda 

Thank you for your prompt response.

Yes the article has cleared things up, our VMware guys are going to create a new port group for me which I can move my vNIC to (in VM Settings) and then configure with our required VLANs.

Will hopefully sort things out!

 

  - You may find this command useful on the 9800-cl :
                          show platform hardware chassis active qfp datapath pmd ifdev

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

SamBurgess44786
Frequent Visitor
Frequent Visitor

Just a quick update, this is working after creating a port group (trunk) with the required VLANs in VMware and configuring that on network adapter 2 in the VM settings. Simply then configure vWLC Gi2 as a trunk. 

Also required - within Networking properties of VMware, the Promiscuous mode and Forged transmits are set to Reject by default. These both need to be set to Accept for the port group.

 

 - Great ! Have (final) checkup of the 9800-CL controller configuration with the CLI command show tech wireless ; feed the output into :
                                                                              https://cway.cisco.com/wireless-config-analyzer/
      Strongly advised!

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

Yes I was going to point that out after seeing your VMware screenshots.  That's made very clear in the config guide and the best practice guide https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/guide-c07-743627.html#C9800CLconsiderations

------------------------------
Please click Helpful if this post helped you and Accept 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
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
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
Review Cisco Networking for a $25 gift card