Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
fortiwlc [2019/03/01 16:59]
mswanson [Best Practices]
fortiwlc [2019/03/06 20:27] (current)
mswanson [Best Practices]
Line 63: Line 63:
  
 === How to Properly Deploy WLC VM image in ESXi === === How to Properly Deploy WLC VM image in ESXi ===
 +From the Wireless Technical Newsletter February 2019
  
 ** Basic ESXi Best Practices for WLC VM ** ** Basic ESXi Best Practices for WLC VM **
Line 71: Line 72:
   * the FGT or FortiSwitch Ethernet port facing the ESXi interface has its native vlan in the management vlan of the FWLC, and allows for all vlans used by WLC to be trunked to the vSwitch.   * the FGT or FortiSwitch Ethernet port facing the ESXi interface has its native vlan in the management vlan of the FWLC, and allows for all vlans used by WLC to be trunked to the vSwitch.
   *VLAN ID 4095 is created on the Port Group, to allow the Port Group to become a Trunk Port for the multiple VLANs of WLC, with the native administrative VLAN for WLC management untagged.   *VLAN ID 4095 is created on the Port Group, to allow the Port Group to become a Trunk Port for the multiple VLANs of WLC, with the native administrative VLAN for WLC management untagged.
 +
 +{{:​fortiwlc:​pasted:​20190306-201953.png}}
  
 ** Best Practices for Dual Bonding Configurations on WLC VM ** ** Best Practices for Dual Bonding Configurations on WLC VM **
Line 79: Line 82:
  
 === How to properly configure Port Aggregation / LACP on FortiAP-U managed by WLC === === How to properly configure Port Aggregation / LACP on FortiAP-U managed by WLC ===
 +From the Wireless Technical Newsletter February 2019
  
 This process must be properly followed step by step for success. You first need to make sure that the combined Patch for 8.4-3 released in February 2019 is installed. This AP consolidated patch includes an important Tx stuck fix also. This process must be properly followed step by step for success. You first need to make sure that the combined Patch for 8.4-3 released in February 2019 is installed. This AP consolidated patch includes an important Tx stuck fix also.
Line 88: Line 92:
   * Connect LAN 1 only then – it will appear in Disabled state   * Connect LAN 1 only then – it will appear in Disabled state
   * On GUI, go to ‘Configuration->​Devices->​APs’,​ select the AP->​Ethernet interface, and eventually click interface 1 and enable LACP:   * On GUI, go to ‘Configuration->​Devices->​APs’,​ select the AP->​Ethernet interface, and eventually click interface 1 and enable LACP:
 +
 +{{:​fortiwlc:​pasted:​20190306-202028.png}}
  
 You should see this below output where LAN2 will be the uplink and LAN1 will be the LACP port: You should see this below output where LAN2 will be the uplink and LAN1 will be the LACP port: