html5-img
1 / 22

Module 2

Module 2. From WiNG 4.x to WiNG 5.x Migration, Comparison and Licensing. Objectives. Indentify the older AP Models and the new Model that they will be migrating to. Describe the migration features supported in the new models. Describe the Migration Procedures.

nijole
Télécharger la présentation

Module 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Module 2 From WiNG4.x to WiNG5.x Migration, Comparison and Licensing

  2. Objectives • Indentify the older AP Models and the new Model that they will be migrating to. • Describe the migration features supported in the new models. • Describe the Migration Procedures. • Discuss the Configuration Migration Tool and the steps to perform the process. • Discuss the license capabilities for WiNG5.x • Compare the WiNG5.x IDS/IPS. • Identify the new features in WiNG5.1.

  3. Migrating From 4.x to 5.x

  4. What is 5.x is improving on?

  5. Migrating From The Old Hardware

  6. Migrating From Old Hardware • AP621 / AP650 • Single (AP621) and Dual (AP650) radio • Dependent versions of AP6521 & 6532 • Networks with a Local Controller • AP 300 • 802.11 a/b/g AP • Indoor Dual Radio • Dependent AP • AP6521 • Single radio 802.11n AP • MIMO 2x2:2, 150 Mbps • Independent and adaptive • 802.3af PoE • Ideal for Hotspot deployments • AP6532 • Dual radio 802.11n AP • MIMO 2x3:2, 300 Mbps • Independent and adaptive • 802.3af PoE • Same level of services as AP 7131 • AP 5131 • 802.11 a/b/g AP • Indoor Dual Radio • Dependent AP • WiNG 4.x Only • AP7161 • Dual radio Independent 802.11n AP • 802.3af Power-over-Ethernet (PoE) • 300 Mbps at the 11n mesh layer • Nema 4X / IP67 Enclosure • WiNG 5 and MeshConnex (Q3) • AP / VMM Dual Mode RevB • AP 5181 • 802.11 a/b/g AP • Outdoor Dual Radio • Independent AP • Wing

  7. Migration: Feature Support

  8. Migration: Feature Support WiNG5.1 Single Hop Mesh Deployment and Diagram • AP650 • Stops behaving like AP300 and becomes full-fledged WiNG5 Dependent AP • Has local services, can now locally bridge traffic SECURELY, but still needs the controller • Can provide concurrent Access and AD sensor functionality • AP-7131 • Becomes full WiNG5 Independent AP • Different UI/CLI/Config Model • Capable of becoming a Virtual Controller • AP300 • Maintains WiNG4 behavior (forwards everything to the controller) • Limited legacy level support (more later in the AP300 Module) • RFS Controllers • Full WiNG5 Support • Different UI/CLI/Config Model • Not Supported: • AP-5131, AP-5181, AP-4131 in AP300 mode • WS Series of Controllers • Limited Mesh Support • Single-hop, until later releases with full MeshConnex(!) and other great features AP-7181 (now) / WiNG5.x (future) MeshConnex Mesh Deployment

  9. Migration: Under the Bonnet • WiNG5 Controller is the point of configuration of all profiles and functional policies across locations • Encryption/Decryption is now at the AP (Dependent and Independent) • All functional policies are enforced at the AP • APs are able to bridge traffic locally and securely • New Config Modeldeveloped to be able to cater to major architecture change • Same Feature set, Config Model, CLI/GUI across all APs and controllers • Changes in CLI to accommodate the new configuration model • Nice, sleek, Flash-based GUI (No More JAVA) • Because of these major changes, config is not preserved during migration (discussed later)

  10. Migration: Under the Bonnet • WiSPe/WiSPH is now replaced by MiNT protocol • Underlying protocol for • Device Discovery (AP discovery, Forming cluster) • Inter-device communications (AP-AP, AP-Controller) • Device Management (AP Adoption, config changes) • Aggregation of statistics/events • Remote debugging • Roaming coordination • Distributed Firewall and IPS • Tunnelling traffic (if tunnelled) • Data and Control flows are separated • L2 routing protocol inside • Automated - user does not have to configure MiNT, but it is possible • Discussed in detail later

  11. Migration Procedures

  12. Migration: Procedures • AP-7131 upgrades are be supported from AP v4.1 • Special image to upgrade to WiNG5 provided • Special image to fall back to WiNG4 provided • RFS Controllers: upgrades are supported from WiNG v4.1 onwards • May have WiNG4 in one FW bank and WiNG5 in another • Because of the major the Configuration Model differences the config will not be preserved • Information sustained through the upgrade will be around connectivity: • IP address • Gateway Information • Route Information • Username/Password • For other parameters • Rebuild the configuration from scratch • Use Configuration Migration Tool (CMT) (WiNG5.2+)

  13. Configuration Migration Tool

  14. MOTOROLA PROPRIATARY AND CONFIDENTIAL CMT:Configuration Migration Overview Power On • WiNG 5.2 offers configuration migration functionality in a 2-step process • Automated script that runs after a 4.x to 5.2 upgrade (very early in the boot sequence) • An Windows utility for more precise conversion • Used to upgrade 4.3 configurations to 5.2 and vice versa • Converts most of configuration commands • Some manual intervention is still required because of substantial config model differences • There will be an error message for commands that do not carry over Config Migration Tool Printer Parser Daemons Run-Time

  15. MOTOROLA PROPRIATARY AND CONFIDENTIAL CMT: Windows Executable • Installs to “C:\Program Files\WiNG4_to_WiNG5”. • Enter that directory from a dos prompt and run cfgcv.bat: cfgcv four_three_sample.txt C:\Program Files\WiNG4_to_WiNG5> C:\Program Files\WiNG4_to_WiNG5>cfgconvert four_three_sample.txt commands.txt four_three_sample.txt.out FULL 4x to 5x configuration conversion in process 4x to 5x configuration conversion in process C:\Program Files\WiNG5_to_WiNG5>

  16. MOTOROLA PROPRIATARY AND CONFIDENTIAL CMT: Output ! wlan 6 no answer-broadcast-probes wpa-wpa2 psk 0 123456789 broadcast-ssid bridging-mode tunnel ! !! No WiNG5 support for: detector !! No WiNG5 support for: detector !! No WiNG5 support for: detector !! No WiNG5 support for: detector !! No WiNG5 support for: detector !! No WiNG5 support for: detector !! No WiNG5 support for: detector ap300 00-15-70-D3-69-D9 country-code ca interface radio 1 placement indoor channel 6 power 4 description AP25_DR_85_Shp data-rates custom basic-1 basic-2 5.5 11 24 36 48 54 interface radio 2 placement indoor channel 48 power 16 • There is a sample 4.x configuration file that can be used for demonstration. • Output of tool will be the same name as the input file with “.out” extension • Notice commands that do not transfer to a 5.x equivalent

  17. MOTOROLA PROPRIATARY AND CONFIDENTIAL CMT: Configuration Migration Process 1 User makes backup (offline) copy of WiNG 4 configuration 2 User performs upgrade as normal to WiNG 5 3 4 5 6 During reboot, the migration script determines if conversion is needed and runs minimal connectivity conversion (IP’s, Default-Gateway, etc.) For further detailed conversion, an offline Windows utility is used against the backup copy, which carry over additional settings, such as configured WLAN’s. To complete, some parameters will need to be created, as they are foreign to a 4.x config; i.e. rf-domains, policies, etc. Copy of old config will be created, named according to previous version

  18. Licenses in WiNG5

  19. Licenses in WiNG5

  20. WiNG5 IDS/IPS Comparison

  21. WiNG5 IDS/IPS Comparison

  22. Indentify the older AP Models and the new Model that they will be migrating to. • Describe the migration features supported in the new models. • Describe the Migration Procedures. • Discuss the Configuration Migration Tool and the steps to perform the process. • Discuss the license capabilities for WiNG5.x • Compare the WiNG5.x IDS/IPS. • Module Summary

More Related