CINXE.COM

<!doctype html> <html lang="en-US" class="no-touch js "> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="blogsPostDate" content="2022-07-15 08:00:31"/><meta name="blogsPostTags" content="6ghz,cisco-wi-fi-6e,legacy-aps,legacy-controllers,migration-scenarios,wi-fi-6,wi-fi-6e"/><meta name="blogsPostCat" content="Networking"/><meta name="article:category" content="Networking"/> <meta name="wordCount" content="1989" /> <meta name="readTime" content="477" />  <script type='text/javascript' src="//www.cisco.com/etc/designs/cdc/clientlibs/responsive/js/web-component-foundation.min.js"></script> <script> /** * Invokes appropriate private methods based on input parameters based on needs of web component architecture * @param {Array} wcAssets array of strings that correlate to the names of web components or array of objects containing asset name and corresponding locale/path * @param {String} localePath specifies where web component should be retrieved from (expected format: en/us or en_au for all other locales); false if wcAssets, is array of objects * @param {Boolean} isWem [Optional] specifies if assets are being loaded on a WEM environment * @param {Boolean} needTargetter [Optional] specifies need for targetter bundle to be loaded (generally needed on external sites) * @param {Boolean} isRelative [Optional] specifies if asset path(s) should be relative * @param {String} env [Optional] specifies enviornment to append to relative path (should not be used with isRelative) * @param {Boolean} hasEnvOverride [Optional] specifies if environment needs to be overridden (should be used with env) */ cdc.wcAncillaryAssetAllocator.init(['cdc-template-blogs'], 'en/us', false, true, false, 'prod'); if (window.cdc === undefined) { window.cdc = {}; } if (cdc.cdcMasthead === undefined) { cdc.cdcMasthead = {}; } if (cdc.cdcMasthead.additional === undefined) { cdc.cdcMasthead.additional = {}; } cdc.cdcMasthead.additional.env = 'prod'; </script> <script type="text/javascript"> if ( typeof cdc === "undefined")cdc = {}; if ( typeof cdc.util === "undefined")cdc.util = {}; cdc.util.ensureNamespace = function (namespaceStr) { if (!namespaceStr) { return; var parts = namespaceStr.split("."); var o = window; var i; var aPart; for (i = 0; i < parts.length; i++) aPart = parts[i]; if (typeof (o[aPart]) != "object"){ o[aPart] = {}; } o = o[aPart]; } }; cdc.dm = {}; cdc.dm.util = {}; cdc.dm.util.ensureNamespace = cdc.util.ensureNamespace; </script> <meta name="author" content="Javier Contreras" /><meta name="blogsPostAuthor" content="Javier Contreras" /><meta name='robots' content='index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1' /> <script type="text/javascript" src="//www.cisco.com/c/dam/cdc/t/ctm-core.js"></script>  <title>Migrating to 6GHz - Cisco Blogs</title> <meta name="description" content="In view of the new Wi-Fi 6E and 6GHz adoption push, it is critical to evaluate what are the best ways to do a migration from existing Cisco on-prem legacy networks into the new world of 6GHz deployments." /> <link rel="canonical" href="https://blogs.cisco.com/networking/migrating-to-6ghz" /> <meta property="og:locale" content="en_US" /> <meta property="og:type" content="article" /> <meta property="og:title" content="Migrating to 6GHz" /> <meta property="og:description" content="In view of the new Wi-Fi 6E and 6GHz adoption push, it is critical to evaluate what are the best ways to do a migration from existing Cisco on-prem legacy networks into the new world of 6GHz deployments." /> <meta property="og:url" content="https://blogs.cisco.com/networking/migrating-to-6ghz" /> <meta property="og:site_name" content="Cisco Blogs" /> <meta property="article:published_time" content="2022-07-15T15:00:31+00:00" /> <meta property="article:modified_time" content="2022-08-30T15:49:12+00:00" /> <meta property="og:image" content="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/Screen-Shot-2022-07-07-at-1.42.22-PM.png" /> <meta property="og:image:width" content="1574" /> <meta property="og:image:height" content="756" /> <meta property="og:image:type" content="image/png" /> <meta name="author" content="Javier Contreras" /> <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:label1" content="Written by" /> <meta name="twitter:data1" content="Javier Contreras" /> <meta name="twitter:label2" content="Est. reading time" /> <meta name="twitter:data2" content="11 minutes" /> <script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#article","isPartOf":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz"},"author":{"name":"Javier Contreras","@id":"https://blogs.cisco.com/#/schema/person/f0c7efe95f7449296cbba72ca69cab32"},"headline":"Migrating to 6GHz","datePublished":"2022-07-15T15:00:31+00:00","dateModified":"2022-08-30T15:49:12+00:00","mainEntityOfPage":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz"},"wordCount":1932,"publisher":{"@id":"https://blogs.cisco.com/#organization"},"image":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#primaryimage"},"thumbnailUrl":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/Screen-Shot-2022-07-07-at-1.42.22-PM.png","keywords":["6GHz","Cisco Wi-Fi 6E","Legacy APs","legacy controllers","Migration Scenarios","Wi-Fi 6","Wi-Fi 6E"],"articleSection":["Networking"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https://blogs.cisco.com/networking/migrating-to-6ghz","url":"https://blogs.cisco.com/networking/migrating-to-6ghz","name":"Migrating to 6GHz - Cisco Blogs","isPartOf":{"@id":"https://blogs.cisco.com/#website"},"primaryImageOfPage":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#primaryimage"},"image":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#primaryimage"},"thumbnailUrl":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/Screen-Shot-2022-07-07-at-1.42.22-PM.png","datePublished":"2022-07-15T15:00:31+00:00","dateModified":"2022-08-30T15:49:12+00:00","description":"In view of the new Wi-Fi 6E and 6GHz adoption push, it is critical to evaluate what are the best ways to do a migration from existing Cisco on-prem legacy networks into the new world of 6GHz deployments.","breadcrumb":{"@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://blogs.cisco.com/networking/migrating-to-6ghz"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#primaryimage","url":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/Screen-Shot-2022-07-07-at-1.42.22-PM.png","contentUrl":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/Screen-Shot-2022-07-07-at-1.42.22-PM.png","width":1574,"height":756},{"@type":"BreadcrumbList","@id":"https://blogs.cisco.com/networking/migrating-to-6ghz#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Cisco Blogs","item":"https://blogs.cisco.com/"},{"@type":"ListItem","position":2,"name":"Networking","item":"https://blogs.cisco.com/networking"},{"@type":"ListItem","position":3,"name":"Migrating to 6GHz"}]},{"@type":"WebSite","@id":"https://blogs.cisco.com/#website","url":"https://blogs.cisco.com/","name":"Cisco Blogs","description":"","publisher":{"@id":"https://blogs.cisco.com/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://blogs.cisco.com/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https://blogs.cisco.com/#organization","name":"Cisco Systems","url":"https://blogs.cisco.com/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https://blogs.cisco.com/#/schema/logo/image/","url":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2020/10/Cisco_Logo_no_TM_Sky_Blue-RGB.png","contentUrl":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2020/10/Cisco_Logo_no_TM_Sky_Blue-RGB.png","width":912,"height":482,"caption":"Cisco Systems"},"image":{"@id":"https://blogs.cisco.com/#/schema/logo/image/"}},{"@type":"Person","@id":"https://blogs.cisco.com/#/schema/person/f0c7efe95f7449296cbba72ca69cab32","name":"Javier Contreras","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https://blogs.cisco.com/#/schema/person/image/","url":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/jacontre.jpeg","contentUrl":"https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/jacontre.jpeg","caption":"Javier Contreras"},"description":"Javier Contreras (CCIE 10749, Security and Wireless) is Principal Engineer for the Enterprise Business Unit, for Wireless and SDWAN, focused on the EMEA region for the last 16 years. He previously worked in security consultancy and training. Javier has been involved mostly in high priority support cases for wireless and SDWAN infrastructures, CCIE Wireless development, Maintenance Releases, Wireless security testing, leading the WLC Config Analyzer, Wireless Analyzer Express, WiFi Hawk, and vManage Log analysis applications. Javier has over 20 years of experience in the IT and networking industry and has also contributed to the Cisco Press book \"Deploying and Troubleshooting Wireless Networks\" He has directly reported more than 1300 defects and feature requests and currently live in Barcelona, and does Taichi Chuan as a hobby.","url":"https://blogs.cisco.com/author/jacontre"}]}</script>  <link rel='dns-prefetch' href='//www.cisco.com' /> <link rel='dns-prefetch' href='//s.w.org' /> <link rel="alternate" type="application/rss+xml" title="Cisco Blogs » Feed" href="https://blogs.cisco.com/feed" /> <link rel="alternate" type="application/rss+xml" title="Cisco Blogs » Comments Feed" href="https://blogs.cisco.com/comments/feed" /> <link rel="alternate" type="application/rss+xml" title="Cisco Blogs » Migrating to 6GHz Comments Feed" href="https://blogs.cisco.com/networking/migrating-to-6ghz/feed" /> <script type="text/javascript"> window._wpemojiSettings = {"baseUrl":"https:\/\/s.w.org\/images\/core\/emoji\/13.1.0\/72x72\/","ext":".png","svgUrl":"https:\/\/s.w.org\/images\/core\/emoji\/13.1.0\/svg\/","svgExt":".svg","source":{"concatemoji":"https:\/\/blogs.cisco.com\/wp-includes\/js\/wp-emoji-release.min.js?ver=5.9.2"}}; /*! This file is auto-generated */ !function(e,a,t){var n,r,o,i=a.createElement("canvas"),p=i.getContext&&i.getContext("2d");function s(e,t){var a=String.fromCharCode;p.clearRect(0,0,i.width,i.height),p.fillText(a.apply(this,e),0,0);e=i.toDataURL();return p.clearRect(0,0,i.width,i.height),p.fillText(a.apply(this,t),0,0),e===i.toDataURL()}function c(e){var t=a.createElement("script");t.src=e,t.defer=t.type="text/javascript",a.getElementsByTagName("head")[0].appendChild(t)}for(o=Array("flag","emoji"),t.supports={everything:!0,everythingExceptFlag:!0},r=0;r<o.length;r++)t.supports[o[r]]=function(e){if(!p||!p.fillText)return!1;switch(p.textBaseline="top",p.font="600 32px Arial",e){case"flag":return s([127987,65039,8205,9895,65039],[127987,65039,8203,9895,65039])?!1:!s([55356,56826,55356,56819],[55356,56826,8203,55356,56819])&&!s([55356,57332,56128,56423,56128,56418,56128,56421,56128,56430,56128,56423,56128,56447],[55356,57332,8203,56128,56423,8203,56128,56418,8203,56128,56421,8203,56128,56430,8203,56128,56423,8203,56128,56447]);case"emoji":return!s([10084,65039,8205,55357,56613],[10084,65039,8203,55357,56613])}return!1}(o[r]),t.supports.everything=t.supports.everything&&t.supports[o[r]],"flag"!==o[r]&&(t.supports.everythingExceptFlag=t.supports.everythingExceptFlag&&t.supports[o[r]]);t.supports.everythingExceptFlag=t.supports.everythingExceptFlag&&!t.supports.flag,t.DOMReady=!1,t.readyCallback=function(){t.DOMReady=!0},t.supports.everything||(n=function(){t.readyCallback()},a.addEventListener?(a.addEventListener("DOMContentLoaded",n,!1),e.addEventListener("load",n,!1)):(e.attachEvent("onload",n),a.attachEvent("onreadystatechange",function(){"complete"===a.readyState&&t.readyCallback()})),(n=t.source||{}).concatemoji?c(n.concatemoji):n.wpemoji&&n.twemoji&&(c(n.twemoji),c(n.wpemoji)))}(window,document,window._wpemojiSettings); </script> <style type="text/css"> img.wp-smiley, img.emoji { display: inline !important; border: none !important; box-shadow: none !important; height: 1em !important; width: 1em !important; margin: 0 0.07em !important; vertical-align: -0.1em !important; background: none !important; padding: 0 !important; } </style> <link rel='stylesheet' id='wp-block-library-css' href='https://blogs.cisco.com/wp-includes/css/dist/block-library/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='wp-components-css' href='https://blogs.cisco.com/wp-includes/css/dist/components/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='wp-block-editor-css' href='https://blogs.cisco.com/wp-includes/css/dist/block-editor/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='wp-nux-css' href='https://blogs.cisco.com/wp-includes/css/dist/nux/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='wp-reusable-blocks-css' href='https://blogs.cisco.com/wp-includes/css/dist/reusable-blocks/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='wp-editor-css' href='https://blogs.cisco.com/wp-includes/css/dist/editor/style.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='mux_video_block_style-css' href='https://blogs.cisco.com/wp-content/plugins/ilab-media-tools/public/blocks/mediacloud-mux.blocks.style.css' type='text/css' media='all' /> <style id='global-styles-inline-css' type='text/css'> body{--wp--preset--color--black: #000;--wp--preset--color--cyan-bluish-gray: #abb8c3;--wp--preset--color--white: #ffffff;--wp--preset--color--pale-pink: #f78da7;--wp--preset--color--vivid-red: #cf2e2e;--wp--preset--color--luminous-vivid-orange: #ff6900;--wp--preset--color--luminous-vivid-amber: #fcb900;--wp--preset--color--light-green-cyan: #7bdcb5;--wp--preset--color--vivid-green-cyan: #00d084;--wp--preset--color--pale-cyan-blue: #8ed1fc;--wp--preset--color--vivid-cyan-blue: #0693e3;--wp--preset--color--vivid-purple: #9b51e0;--wp--preset--color--cisco-midnight-blue: #0d274d;--wp--preset--color--cisco-ocean-blue: #1e4471;--wp--preset--color--cisco-sky-blue: #00bceb;--wp--preset--color--cisco-green: #6abf4b;--wp--preset--color--cisco-orange: #fbab18;--wp--preset--color--cisco-red: #e2231a;--wp--preset--color--dark-gray: #495057;--wp--preset--color--medium-gray: #9e9ea2;--wp--preset--color--light-gray: #ced4da;--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);--wp--preset--duotone--dark-grayscale: url('#wp-duotone-dark-grayscale');--wp--preset--duotone--grayscale: url('#wp-duotone-grayscale');--wp--preset--duotone--purple-yellow: url('#wp-duotone-purple-yellow');--wp--preset--duotone--blue-red: url('#wp-duotone-blue-red');--wp--preset--duotone--midnight: url('#wp-duotone-midnight');--wp--preset--duotone--magenta-yellow: url('#wp-duotone-magenta-yellow');--wp--preset--duotone--purple-green: url('#wp-duotone-purple-green');--wp--preset--duotone--blue-orange: url('#wp-duotone-blue-orange');--wp--preset--font-size--small: 13px;--wp--preset--font-size--medium: 20px;--wp--preset--font-size--large: 36px;--wp--preset--font-size--x-large: 42px;}.has-black-color{color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-color{color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-color{color: var(--wp--preset--color--white) !important;}.has-pale-pink-color{color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-color{color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-color{color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-color{color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-color{color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-color{color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-color{color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-color{color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-color{color: var(--wp--preset--color--vivid-purple) !important;}.has-black-background-color{background-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-background-color{background-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-background-color{background-color: var(--wp--preset--color--white) !important;}.has-pale-pink-background-color{background-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-background-color{background-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-background-color{background-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-background-color{background-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-background-color{background-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-background-color{background-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-background-color{background-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-background-color{background-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-background-color{background-color: var(--wp--preset--color--vivid-purple) !important;}.has-black-border-color{border-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-border-color{border-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-border-color{border-color: var(--wp--preset--color--white) !important;}.has-pale-pink-border-color{border-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-border-color{border-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-border-color{border-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-border-color{border-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-border-color{border-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-border-color{border-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-border-color{border-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-border-color{border-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-border-color{border-color: var(--wp--preset--color--vivid-purple) !important;}.has-vivid-cyan-blue-to-vivid-purple-gradient-background{background: var(--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple) !important;}.has-light-green-cyan-to-vivid-green-cyan-gradient-background{background: var(--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan) !important;}.has-luminous-vivid-amber-to-luminous-vivid-orange-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange) !important;}.has-luminous-vivid-orange-to-vivid-red-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-orange-to-vivid-red) !important;}.has-very-light-gray-to-cyan-bluish-gray-gradient-background{background: var(--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray) !important;}.has-cool-to-warm-spectrum-gradient-background{background: var(--wp--preset--gradient--cool-to-warm-spectrum) !important;}.has-blush-light-purple-gradient-background{background: var(--wp--preset--gradient--blush-light-purple) !important;}.has-blush-bordeaux-gradient-background{background: var(--wp--preset--gradient--blush-bordeaux) !important;}.has-luminous-dusk-gradient-background{background: var(--wp--preset--gradient--luminous-dusk) !important;}.has-pale-ocean-gradient-background{background: var(--wp--preset--gradient--pale-ocean) !important;}.has-electric-grass-gradient-background{background: var(--wp--preset--gradient--electric-grass) !important;}.has-midnight-gradient-background{background: var(--wp--preset--gradient--midnight) !important;}.has-small-font-size{font-size: var(--wp--preset--font-size--small) !important;}.has-medium-font-size{font-size: var(--wp--preset--font-size--medium) !important;}.has-large-font-size{font-size: var(--wp--preset--font-size--large) !important;}.has-x-large-font-size{font-size: var(--wp--preset--font-size--x-large) !important;} </style> <link rel='stylesheet' id='category-css-css' href='https://blogs.cisco.com/wp-content/plugins/cisco-category-page-enhancement/css/category-css.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='multiauthor_custom_front_style-css' href='https://blogs.cisco.com/wp-content/plugins/cisco-multiple-authors/css/multiauthor.css?ver=1.1' type='text/css' media='all' /> <link rel='stylesheet' id='parent-style-css' href='https://blogs.cisco.com/wp-content/themes/ciscowordpress/style.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='child-style-css' href='https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/style.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='ciscowordpress-style-css' href='https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/style.css?ver=5.9.2' type='text/css' media='all' /> <style id='ciscowordpress-style-inline-css' type='text/css'> @media only screen and (min-width: 930px){ ul#featured_categories li{ width: calc(100%/ ); }} </style> <link rel='stylesheet' id='cui-standard-css' href='https://www.cisco.com/web/fw/cisco-ui/1.3.5/dist/css/cui-standard.min.css?ver=5.9.2' type='text/css' media='all' /> <link rel='stylesheet' id='style_login_widget-css' href='https://blogs.cisco.com/wp-content/plugins/miniorange-oauth-oidc-single-sign-on/resources/css/style_login_widget.css?ver=5.9.2' type='text/css' media='all' /> <script type='text/javascript' src='https://blogs.cisco.com/wp-content/plugins/cisco-multiple-authors/js/custom-multiauthor.js?ver=5.9.2' id='multiauthor_custom_js-js'></script> <script type='text/javascript' src='https://blogs.cisco.com/wp-content/themes/ciscowordpress/js/card-dropdown.js?ver=5.9.2' id='ciscowordpress-card-tag-dropdown-js'></script> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://blogs.cisco.com/xmlrpc.php?rsd" /> <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="https://blogs.cisco.com/wp-includes/wlwmanifest.xml" /> <meta name="generator" content="WordPress 5.9.2" /> <link rel='shortlink' href='https://blogs.cisco.com/?p=410042' /> <link rel="alternate" type="application/json+oembed" href="https://blogs.cisco.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fblogs.cisco.com%2Fnetworking%2Fmigrating-to-6ghz" /> <link rel="alternate" type="text/xml+oembed" href="https://blogs.cisco.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fblogs.cisco.com%2Fnetworking%2Fmigrating-to-6ghz&format=xml" /> <link rel="icon" href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2024/09/cropped-Cisco-logo-thumb-sky-blue-150x150.jpg" sizes="32x32" /> <link rel="icon" href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2024/09/cropped-Cisco-logo-thumb-sky-blue-300x300.jpg" sizes="192x192" /> <link rel="apple-touch-icon" href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2024/09/cropped-Cisco-logo-thumb-sky-blue-300x300.jpg" /> <meta name="msapplication-TileImage" content="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2024/09/cropped-Cisco-logo-thumb-sky-blue-300x300.jpg" /> </head> <body class="post-template-default single single-post postid-410042 single-format-standard no-sidebar"> <div id="page" class="site"> <cdc-template-micro lang="en" search-set-context="blogs"> <a class="skip-link screen-reader-text" href="#content">Skip to content</a> <header id="masthead" class="site-header"> </header> <div id="content" class="site-content"> <div id="primary" class="content-area"> <main id="main" class="site-main"> <p id="breadcrumbs"><span><span><a href="https://blogs.cisco.com/">Cisco Blogs</a> / <span><a href="https://blogs.cisco.com/networking">Networking</a> / <span class="breadcrumb_last" aria-current="page">Migrating to 6GHz</span></span></span></span></p> <div class="blog-post-header"> </div> <article id="post-410042" class="post-410042 post type-post status-publish format-standard has-post-thumbnail hentry category-networking tag-6ghz tag-cisco-wi-fi-6e tag-legacy-aps tag-legacy-controllers tag-migration-scenarios tag-wi-fi-6 tag-wi-fi-6e"> <div class="main-content"> <header class="entry-header"> <div class="entry-meta"> July 15, 2022 <a id="post-comments" href="https://blogs.cisco.com/networking/migrating-to-6ghz#comments">2 Comments</a> <hr> </div> </header> <div class="blog-post-header"> <div class="thumbnail-avatar"> <div class="post-thumbnail" style="background-image:url(https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/IL20220707184411-Screen-Shot-2022-07-07-at-1.42.22-PM-600x200.png);"> <img src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/IL20220707144148-jacontre-150x150.jpeg" width="102" height="102" alt="Avatar" class="avatar avatar-102 wp-user-avatar wp-user-avatar-102 photo avatar-default"> </div> </div> <div class="blog-cat-post-author-container"> <a href=https://blogs.cisco.com/networking><h5>Networking</h5></a> <h1 class="entry-title">Migrating to 6GHz</h1><p class="wordcount"><span class="black">8 min read</span></p> <p> <a href="https://blogs.cisco.com/author/jacontre" title="Posts by Javier Contreras" rel="author">Javier Contreras</a> </p> </div> </div>  <div class="entry-content"> <p>With more than 18 billion devices in use and 4.2 billion more to be shipping in 2022, the sheer size of existing Wi-Fi deployments worldwide is just mind-boggling. In view of the new Wi-Fi 6E and 6GHz adoption push, it is critical to evaluate what are the best ways to do a migration from existing Cisco on-prem legacy networks into the new world of 6GHz deployments.</p> <p>For Cisco Enterprise customers, there are several aspects that need to be evaluated for any successful migration planning:</p> <ul> <li>Existing controller type: <ul> <li>is it AireOS?</li> <li>Model? (Basically, can it run 8.5 or 8.10?)</li> <li>is it IRCM capable (2504/wism2 can’t do mobility to 9800)</li> </ul> </li> <li>Access point Inventory: <ul> <li>Are there any 802.11n models still in use? (per example, 2600, 3600, 1520, 1600, etc)</li> <li>Are there any Wave1 APs? (last generation of IOS, per example 1700, 2700, 3700)</li> <li>Mesh deployments?</li> </ul> </li> <li>PoE support: <ul> <li>What is the maximum supported power standard? (802.3bt, 802.3at, etc)</li> <li>Any power budged constraints per port?</li> <li>Or APs are powered by power injectors?</li> </ul> </li> <li>Current 5GHz TX power <ul> <li>Is my network running on average at power level 3-4?</li> <li>or it is around 1-2?</li> </ul> </li> </ul> <p>6GHz adoption is only supported in the Catalyst 9800 IOS-XE controllers, running 17.7 or higher. This imposes some additional considerations either on controller type migration, or about legacy access points that may need to either be migrated, or supported through Inter Release Controller Mobility (IRCM) solutions</p> <div class="wp-block-image"> <figure class="alignright"> <figure id="attachment_410043" aria-describedby="caption-attachment-410043" style="width: 294px" class="wp-caption alignright"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_aps.jpg" target="_blank" rel="noopener"><img class="wp-image-410043 size-full" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_aps.jpg" alt="Legacy APs" width="294" height="171" /></a><figcaption id="caption-attachment-410043" class="wp-caption-text">Figure 1. Legacy APs</figcaption></figure> </figure> </div> <h2 id="h-legacy-access-points"><strong>Legacy Access Points</strong></h2> <p>Over the years, it has always been possible to do co-existence of previous generations of access points with the newly introduced models, ensuring both smooth network upgrades and capacity expansion. Adding new APs is normally not an issue until we hit the scenario of inter-generation gaps.</p> <p>If a network that for any reason is still running devices 2 generations away (for example, a 2602 AP), and now needs to include new 802.11ax models (for example 9130) or jump to the 9136/9166/9164 for 6GHz support, this will need more complex migration paths.</p> <p>When there are multiple generation gaps, if the legacy controllers can support IRCM to the IOS-XE 9800, it is perfectly possible to design a migration plan, without the need to do a “forklift” installation. This will ensure very little pain to users, and keep the network running until everything is migrated to the new hardware and standards</p> <p>In the following table, we can see a summary of software support ranges and migration options for most access points models from 11n generation models:</p> <p> </p> <p> </p> <figure class="wp-block-table is-style-stripes"> <table> <thead> <tr> <th>Model/Series</th> <th class="has-text-align-center" data-align="center">Last AireOS Support</th> <th class="has-text-align-center" data-align="center">IOS-XE support</th> <th class="has-text-align-center" data-align="center">IOS-XE AP equivalent</th> <th>Migration Notes</th> </tr> </thead> <tbody> <tr> <td>700/700W Series</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Not supported</td> <td class="has-text-align-center" data-align="center">9105</td> <td>Migration through IRCM</td> </tr> <tr> <td>1040</td> <td class="has-text-align-center" data-align="center">8.3</td> <td class="has-text-align-center" data-align="center">Not supported</td> <td class="has-text-align-center" data-align="center">9115</td> <td>AP needs to be replaced</td> </tr> <tr> <td>1260</td> <td class="has-text-align-center" data-align="center">8.3</td> <td class="has-text-align-center" data-align="center">Not supported</td> <td class="has-text-align-center" data-align="center">9115</td> <td>AP needs to be replaced</td> </tr> <tr> <td>1600</td> <td class="has-text-align-center" data-align="center">8.5</td> <td class="has-text-align-center" data-align="center">Not supported</td> <td class="has-text-align-center" data-align="center">9115</td> <td>Either 8.5 IRCM, or Hardware replaced</td> </tr> <tr> <td>1700</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">17.3</td> <td class="has-text-align-center" data-align="center">9115</td> <td>Migration through IRCM</td> </tr> <tr> <td>2700</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">17.3</td> <td class="has-text-align-center" data-align="center">9120</td> <td>Migration through IRCM</td> </tr> <tr> <td>3700</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">17.3</td> <td class="has-text-align-center" data-align="center">9130</td> <td>Migration through IRCM</td> </tr> <tr> <td>1810/1810W</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Up to 17.3</td> <td class="has-text-align-center" data-align="center">9105</td> <td>Hardware replaced or IRCM between IOS-XE versions</td> </tr> <tr> <td>1830/1840/1850</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Supported</td> <td class="has-text-align-center" data-align="center">9105</td> <td>Directly supported</td> </tr> <tr> <td>AP802/AP802H</td> <td class="has-text-align-center" data-align="center">8.5</td> <td class="has-text-align-center" data-align="center">Not Supported</td> <td class="has-text-align-center" data-align="center">ISR10xx</td> <td>Migration through IRCM</td> </tr> <tr> <td>2600</td> <td class="has-text-align-center" data-align="center">8.5</td> <td class="has-text-align-center" data-align="center">Not Supported</td> <td class="has-text-align-center" data-align="center">9120</td> <td>Migration through IRCM</td> </tr> <tr> <td>2800/3800/4800</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Supported</td> <td class="has-text-align-center" data-align="center"> </td> <td>Directly supported</td> </tr> <tr> <td>1540</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Supported</td> <td class="has-text-align-center" data-align="center"> </td> <td>Directly supported</td> </tr> <tr> <td>1550</td> <td class="has-text-align-center" data-align="center">8.5</td> <td class="has-text-align-center" data-align="center">Not supported</td> <td class="has-text-align-center" data-align="center"> </td> <td>Migration through IRCM</td> </tr> <tr> <td>1560</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Supported</td> <td class="has-text-align-center" data-align="center"> </td> <td>Directly supported</td> </tr> <tr> <td>1570</td> <td class="has-text-align-center" data-align="center">8.10</td> <td class="has-text-align-center" data-align="center">Up to 17.3</td> <td class="has-text-align-center" data-align="center"> </td> <td>Migration through IRCM</td> </tr> </tbody> </table> </figure> <p> </p> <p>For a complete list, you can check the <a href="https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#ctr-ap_support" target="_blank" rel="noreferrer noopener">Cisco Wireless Solutions Software Compatibility Matrix</a>, alternatively, you can run the <a href="https://developer.cisco.com/docs/wireless-troubleshooting-tools/#%21wireless-troubleshooting-tools/wireless-config-analyzer-express---wcae">Wireless Config Analyzer Express</a>, to check your migration readiness</p> <p> </p> <p> </p> <p> </p> <div class="wp-block-image"> <figure class="aligncenter"> <figure id="attachment_410047" aria-describedby="caption-attachment-410047" style="width: 800px" class="wp-caption aligncenter"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/ap_flow.png" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410047" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/ap_flow-1024x869.png" sizes="(max-width: 1024px) 100vw, 1024px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/ap_flow-300x255.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/ap_flow-768x652.png 768w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/ap_flow-1024x869.png 1024w" alt="AP Migration Decision Flow" width="800" height="679" /></a><figcaption id="caption-attachment-410047" class="wp-caption-text">Figure 2. AP Migration Decision Flow</figcaption></figure> </figure> </div> <p> </p> <div class="wp-block-image"> <figure class="alignright size-full"> <figure id="attachment_410052" aria-describedby="caption-attachment-410052" style="width: 445px" class="wp-caption alignright"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_wlc.jpg" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410052 size-full" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_wlc.jpg" sizes="(max-width: 445px) 100vw, 445px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_wlc-300x76.jpg 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/legacy_wlc.jpg 445w" alt="AireOS 5508" width="445" height="113" /></a><figcaption id="caption-attachment-410052" class="wp-caption-text">Figure 3. Legacy Controller</figcaption></figure> </figure> </div> <p> </p> <h2><strong>Legacy Controllers</strong></h2> <p> </p> <p>Depending on the existing controller type, the migration may take different paths. Some scenarios will be simple, allowing a smooth transition. Others may need additional steps to successfully migrate into a Wi-Fi 6E network</p> <p> </p> <p>What to expect:</p> <p> </p> <ul> <li>“Generation 1” controllers: 5508, 8510. They can support up to 8.5 AireOS version, which will allow mobility scenarios between them and new IOS-XE 9800 controllers (Inter-release Controller Mobility, IRCM support). Also, they will support both IOS and AP-COS access points, from 1700 to 3800 models (Wave1, Wave2 802.11ac )</li> <li>“Generation 2” controllers: 5520, 8540, 3504 . All of these can support up to 8.10 AireOS, also allowing IRCM scenarios with 9800. AP support will additionally include 802.11ax models, like the new Catalyst 9105, 9120, and 9130. etc.</li> <li>“Generation 1” controllers without IRCM: 2504, WiSM2, vWLC, 7510. No mobility is possible between them and IOS-XE, so additional steps with different migration scenarios are needed</li> </ul> <p> </p> <p> </p> <p> </p> <div class="wp-block-image"> <figure class="aligncenter size-large"> <figure id="attachment_410053" aria-describedby="caption-attachment-410053" style="width: 800px" class="wp-caption aligncenter"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/controller_flow.png" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410053" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/controller_flow-1024x969.png" sizes="(max-width: 1024px) 100vw, 1024px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/controller_flow-300x284.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/controller_flow-768x727.png 768w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/controller_flow-1024x969.png 1024w" alt="Controller Migration Decision Flow" width="800" height="757" /></a><figcaption id="caption-attachment-410053" class="wp-caption-text">Figure 4. Controller Migration Decision Flow</figcaption></figure> </figure> </div> <p> </p> <h2 id="migration-scenarios"><strong>Migration Scenarios</strong></h2> <p> </p> <p>In general, we should try to migrate “per RF blocks”, defining it as a roaming area or domain where clients can move normally between access points, before hitting idle timeout. Basically, move these RF blocks completely, into the new APs, and IOS-XE controllers. For example, either move a building or a complete floor into the new hardware and software. We should avoid “salt & pepper” deployments, mixing APs on different controllers at the same time. Not because it is not supported, but because mobility will be more complex, and it may lead to issues sooner or later (just a problem prevention action)</p> <p> </p> <p>For scenarios where it is impossible to break the RF environment into differentiated blocks (for example a very large building like an airport, or a fully open space office), we will have to either set up artificial boundaries based on roaming frequency and usage or do a forklift upgrade</p> <p> </p> <div class="wp-block-image"> <figure class="aligncenter size-full"> <figure id="attachment_410054" aria-describedby="caption-attachment-410054" style="width: 800px" class="wp-caption aligncenter"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/buildings.png" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410054" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/buildings.png" sizes="(max-width: 720px) 100vw, 720px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/buildings-300x169.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/buildings.png 720w" alt="Example of RF area/building migration" width="800" height="450" /></a><figcaption id="caption-attachment-410054" class="wp-caption-text">Figure 5. Example of RF area/building migration</figcaption></figure> </figure> </div> <p> </p> <h2 id="what-happens-if-ap-model-is-not-supported-in-any-ircm-version"><strong>What happens if the AP model is not supported in any IRCM version?</strong></h2> <p> </p> <p>This could be the scenario of a legacy controller, still working in 8.3, with some AP models that are not supported beyond that version. For example, the scenario of 20 APs of 2700 Series, and 10 APs of 1042 Series.</p> <p> </p> <p>The 1040s are not supported in 8.5. In this case, the preferred option is to prioritize the replacement of those APs first, moving the impacted area into 9800 as the first step. Sometimes, customers have mixed models across a given building. For example, the mix of 2700 and 2600. In those scenarios, the best option is to consolidate models per supported version, moving all APs of a given type together, so they are contained in a specific RF space in order to facilitate migration in blocks</p> <p> </p> <p> </p> <p> </p> <h3 id="scenario-1-legacy-controller-supports-ircm"><strong>Scenario 1: Legacy Controller supports IRCM</strong></h3> <p> </p> <p>This will be the most common scenario, where we have either 8.5 (5508/8510) or 8.10 (5520/3504/8540) AireOS controller. The migration picture will start with the <a href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-8/b_c9800_wireless_controller-aireos_ircm_dg.html">creation of IRCM setup between AireOS and 9800 controllers</a>, then either replace APs in RF areas connecting them to the new controller, allowing mobility to act when a client needs to roam between legacy and new RF areas.</p> <p> </p> <p>This method allows the smooth coexistence of both controllers, with RF areas migrated as needed, without any overnight switchover.</p> <p> </p> <p>Things to keep in mind:</p> <p> </p> <ul> <li>If the controller is limited to 8.5 (5508, 8510), we will need a special IRCM version (8.5.182.104), to connect them to IOS-XE</li> <li>In general, it is best to split the RF network into different areas, configuring different RF group names between the legacy and IOS-XE controllers. This way each group can do the best calculations that their respective version allows. We should make sure that “Avoid Foreign AP Interference” is enabled on RRM/DCA configuration (it is by default)</li> <li>Always configure the primary/secondary controller name in access points. The new controllers will reject unsupported APs, but if any AP could work in both controller types, this will avoid APs joining the wrong one, or flip-flopping between them, until the migration is ready to proceed</li> </ul> <p> </p> <p> </p> <h3 id="scenario-2-legacy-controller-not-supporting-ircm"><strong>Scenario 2: Legacy Controller not supporting IRCM</strong></h3> <p> </p> <p>If the legacy network is running on a controller model WiSM2, 2504, 7510, vWLC, it is not possible to establish an IRCM connection between the old controller to the new 9800 handling the 6E APs. This limits significantly the options that are available, and it forces a more aggressive migration process</p> <p> </p> <p>Migration alternatives:</p> <p> </p> <ul> <li>Keep the two networks separated, and migrate physical RF areas as new APs are added, replacing the old ones. No roaming is possible, and it is very important to keep client VLANs different between controllers, to avoid ARP proxy issues between both controllers. During this process, we must take care on preventing roaming events as client identity, address, etc, will be lost on the change between controller types. For example, the ideal scenario is to move a complete building from one controller to the new one, doing a forklift AP replacement overnight.</li> <li>Avoid migrations “per floor”, as in most building types, it is normal to see clients roaming between APs on different floors</li> <li>Temporarily, replace the legacy controller with one that supports IRCM</li> </ul> <p> </p> <p> </p> <h3 id="scenario-3-ap-is-supported-up-to-17.3-but-not-in-later-versions"><strong>Scenario 3: AP is supported up to 17.3 but not in later versions</strong></h3> <p> </p> <p>This will happen when “Wave1” APs are still present, for example, 1700/2700/3700 AP models. For this type of migration, it is possible to move all APs into IOS-XE, with the 17.3 release, then add a secondary wlc to host the new Wi-Fi 6E APs, using 17.9, and establish an IRCM link between both controllers.</p> <p> </p> <p>On this option, it is possible to do a graceful AP replacement from Wave1, into Wi-Fi 6E models, always trying to do the technology migration, per physical roaming RF area as described (per building, floor, etc). Once all APs are migrated, the 17.3 controllers can be decommissioned</p> <p> </p> <p>In some instances, the customer may deploy a 9800-CL in 17.3 as a temporary controller to host the legacy APs</p> <p> </p> <h2 id="6ghz-rf-coverage-vs-5ghz.-ap-replacement-scenarios"><strong>6GHz RF Coverage vs 5GHz. AP replacement scenarios</strong></h2> <p> </p> <p>One common discussion point is: <em>How different is going to be the cell coverage, in 6GHz, when compared to a 5GHz AP?</em></p> <p> </p> <p>People will want to take a 5GHz AP and do a 1:1 replacement with a 6GHz supported AP, this may seem reasonable, but there are some aspects to consider:</p> <p> </p> <ul> <li>As WiFi-6E uses a higher frequency, the propagation characteristics are different, the signal drops slightly faster in 6 than in 5GHz. The difference should be around 2 dBm on measurements over the same distance. Material absorption will be different as well.</li> <li>6GHz has different regulatory power constraints than 5GHz. Currently, most deployments will be using Low Power APs (for simplicity sake’s, let’s say 24dBm in FCC, 23 dBm in ETSI). This means that depending on the current network AP radio’s power levels, using 6GHz may result in a slightly lower power output</li> </ul> <p> </p> <p>Rule of thumb:</p> <p> </p> <ul> <li>If your power level average is around 3-4, it is possible to do a 1:1 AP replacement, and have a similar coverage level in 5 and 6 GHz</li> <li>If the power level is in 1-2, then you may need around 10 to 20% additional access points</li> </ul> <p> </p> <p>The easiest way to know the average power level per site is to use <a href="https://developer.cisco.com/docs/wireless-troubleshooting-tools/#%21wireless-config-analyzer-express">WCAE tool </a>and check the “Channel Stats 5GHz” tab. This will present a summary per channel, either at controller, or site tag level, of the average power levels (among other information). For example, this is a network where migration to 6GHz may need additional access points:</p> <p> </p> <p> </p> <p> </p> <div class="wp-block-image"> <figure class="aligncenter size-full"> <figure id="attachment_410059" aria-describedby="caption-attachment-410059" style="width: 600px" class="wp-caption aligncenter"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/badpower.png" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410059" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/badpower.png" sizes="(max-width: 623px) 100vw, 623px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/badpower-300x116.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/badpower.png 623w" alt="Example of site with low 5GHz coverage" width="600" height="232" /></a><figcaption id="caption-attachment-410059" class="wp-caption-text">Figure 6. Example of site with low 5GHz coverage</figcaption></figure> </figure> </div> <p> </p> <p>Versus this other one, where the deployment is running on low power, so fitting without issues into 6GHz requirements:</p> <p> </p> <p> </p> <p> </p> <div class="wp-block-image"> <figure class="aligncenter size-full"> <figure id="attachment_410060" aria-describedby="caption-attachment-410060" style="width: 600px" class="wp-caption aligncenter"><a href="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/goodpower-545x200.png" target="_blank" rel="noopener"><img loading="lazy" class="wp-image-410060" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/goodpower-545x200.png" alt="Example of site with good 5GHz coverage" width="600" height="249" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/goodpower-300x124.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/goodpower.png 545w" sizes="(max-width: 600px) 100vw, 600px" /></a><figcaption id="caption-attachment-410060" class="wp-caption-text">Figure 7. Example of site with good 5GHz coverage</figcaption></figure> </figure> </div> <p> </p> <p>If you use the latest version (0.9.11) of WCAE, you can also get a “6GHz predictive” view of how the power distribution, Nearby relationships, and RSSI for clients would look, if you replaced your current APs with 6GHz capable hardware. The tool will match ETSI or FCC regulatory requirements, adapting powers and differences as needed. This is useful to get a taste of how the network would look, doing a direct migration, without adding any APs.</p> <figure id="attachment_410161" aria-describedby="caption-attachment-410161" style="width: 1024px" class="wp-caption aligncenter"><img loading="lazy" class="wp-image-410161" src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/predicted-1024x484.png" sizes="(max-width: 1024px) 100vw, 1024px" srcset="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/predicted-300x142.png 300w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/predicted-768x363.png 768w, https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/predicted-1024x484.png 1024w" alt="6GHz Predictive RRM modeling" width="1024" height="484" /><figcaption id="caption-attachment-410161" class="wp-caption-text">Figure 8. 6GHz Predictive RRM modeling</figcaption></figure> <p>For complex or demanding deployment scenarios, the recommendation will always be: do a site survey</p> <p> </p> <blockquote> <h3 class="p1" style="text-align: center;"><strong><span class="s1">For general information on Wi-Fi 6E products</span></strong></h3> <h2 class="p1" style="text-align: center;"><strong><span class="s1">visit <a href="https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9100ax-access-points/nb-06-wifi-6e-aag-cte-en.html">Wi-Fi 6E At-a-Glance</a></span></strong></h2> </blockquote> <p> </p> <p class="p1"><strong><span class="s1">Additional Resources</span></strong></p> <p class="p1"><span class="s1">For 6GHz troubleshooting and modeling tool visit <a href="https://developer.cisco.com/docs/wireless-troubleshooting-tools/#!wireless-config-analyzer-express">WCAE</a></span></p> <p> </p> <figure class="wp-block-image size-large"></figure> <p></p> <div id="share_bar_desktop"> <span class = "share_title">Share</span> <div class="twitter"> <div class = "box"> <a class = "share" href="https://twitter.com/intent/tweet?url=https://blogs.cisco.com/networking/migrating-to-6ghz&text=Migrating to 6GHz&via=Cisco" target='_blank' data-config-metrics-group='social_shares' data-config-metrics-title='twitter_shares' data-config-metrics-item='twitter_share'> <img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_X_white.svg" alt="share on twitter"></a> </div> </div> <div class="facebook"> <div class = "box"> <a class = "share" href = "http://www.facebook.com/sharer/sharer.php?u=https://blogs.cisco.com/networking/migrating-to-6ghz&title=Migrating to 6GHz" data-config-metrics-group='social_shares' data-config-metrics-title='facebook_shares' data-config-metrics-item='facebook_share' onclick="javascript:window.open(this.href, '', 'menubar=no,toolbar=no,resizable=yes,scrollbars=yes,height=600,width=600');return false;"><img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_fb_white.svg" alt="share on facebook"></a> </div> </div> <div class="linkedin"> <div class = "box"> <a class = "share" href = "https://www.linkedin.com/cws/share?url=https://blogs.cisco.com/networking/migrating-to-6ghz" data-title=" " data-config-metrics-group='social_shares' data-config-metrics-title='linkedin_shares' data-config-metrics-item='linkedin_share' onclick="javascript:window.open(this.href, '', 'menubar=no,toolbar=no,resizable=yes,scrollbars=yes,height=600,width=600');return false;"><img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_li_white.svg" alt="share on linkedin"></a> </div> </div> <div class = "mail"> <div class = "box"> <a class="share" href="mailto:?subject=Cisco Blog: Migrating to 6GHz&body=I saw this post on Cisco Blogs and thought you might like to read it.%0A%0AMigrating to 6GHz%0A%0Ahttps://blogs.cisco.com/networking/migrating-to-6ghz%0A%0A****Disclaimer****%0A%0ACisco is not responsible for the content of this email, and its contents do not necessarily reflect Cisco’s views or opinions. Cisco has not verified the email address or name of the sender." data-config-metrics-group='social_shares' data-config-metrics-title='email_shares' data-config-metrics-item='email_share'> <img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_email_white.svg"> </a> </div> </div> <div class = "clear"></div> </div> <br> <div class = "share_text">Share:</div> <div id="share_bar_mobile"> <div class="twitter"> <div class = "box"> <a class = "share" href="https://twitter.com/intent/tweet?url=https://blogs.cisco.com/networking/migrating-to-6ghz&text=Migrating to 6GHz&via=Cisco" target='_blank' data-config-metrics-group='social_shares' data-config-metrics-title='twitter_shares' data-config-metrics-item='twitter_share'> <img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_X_white.svg" alt="share on twitter"></a> </div> </div> <div class="facebook"> <div class = "box"> <a class = "share" href = "http://www.facebook.com/sharer/sharer.php?u=https://blogs.cisco.com/networking/migrating-to-6ghz&title=Migrating to 6GHz" data-config-metrics-group='social_shares' data-config-metrics-title='facebook_shares' data-config-metrics-item='facebook_share' onclick="javascript:window.open(this.href, '', 'menubar=no,toolbar=no,resizable=yes,scrollbars=yes,height=600,width=600');return false;"><img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_fb_white.svg" alt="share on facebook"></a> </div> </div> <div class="linkedin"> <div class = "box"> <a class = "share" href = "https://www.linkedin.com/cws/share?url=https://blogs.cisco.com/networking/migrating-to-6ghz" data-title=" " data-config-metrics-group='social_shares' data-config-metrics-title='linkedin_shares' data-config-metrics-item='linkedin_share' onclick="javascript:window.open(this.href, '', 'menubar=no,toolbar=no,resizable=yes,scrollbars=yes,height=600,width=600');return false;"><img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_li_white.svg" alt="share on linkedin"></a> </div> </div> <div class = "mail"> <div class = "box"> <a class="share" href="mailto:?subject=Cisco Blog: Migrating to 6GHz&body=I saw this post on Cisco Blogs and thought you might like to read it.%0A%0AMigrating to 6GHz%0A%0Ahttps://blogs.cisco.com/networking/migrating-to-6ghz%0A%0A****Disclaimer****%0A%0ACisco is not responsible for the content of this email, and its contents do not necessarily reflect Cisco’s views or opinions. Cisco has not verified the email address or name of the sender." data-config-metrics-group='social_shares' data-config-metrics-title='email_shares' data-config-metrics-item='email_share'> <img class="share_image" src="https://blogs.cisco.com/wp-content/themes/ciscowordpress-child/svg/share_email_white.svg"> </a> </div> </div> <div class = "clear"></div> </div> <br> </div> <div class="author-section"> <div><h2>Authors</h2></div> <div class="auth-row"> <div class="blog-row author-bio"> <div class="item-thirds-1 author-bio-box" > <div class="author-image" > <a href="https://blogs.cisco.com/author/jacontre"><img src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2022/07/IL20220707144148-jacontre-150x150.jpeg" width="150" height="150" alt="Avatar" class="avatar avatar-150wp-user-avatar wp-user-avatar-150 alignnone photo avatar-default"> </a> </div> <div class="author-info"> <h3><a href="https://blogs.cisco.com/author/jacontre"> Javier Contreras</a> </h3> <h4 class="title">Principal Engineer – Wireless Escalation </h4> <h4>Engineering</h4> </div> </div> </div> </div> </div> <footer class="entry-footer"> </footer> </article> <div id="tags-container">Tags: <a href="https://blogs.cisco.com/tag/6ghz" rel="tag">6GHz</a> <a href="https://blogs.cisco.com/tag/cisco-wi-fi-6e" rel="tag">Cisco Wi-Fi 6E</a> <a href="https://blogs.cisco.com/tag/legacy-aps" rel="tag">Legacy APs</a> <a href="https://blogs.cisco.com/tag/legacy-controllers" rel="tag">legacy controllers</a> <a href="https://blogs.cisco.com/tag/migration-scenarios" rel="tag">Migration Scenarios</a> <a href="https://blogs.cisco.com/tag/wi-fi-6" rel="tag">Wi-Fi 6</a> <a href="https://blogs.cisco.com/tag/wi-fi-6e" rel="tag">Wi-Fi 6E</a> <hr id="comment-break-line"> </div> <div id="comments" class="comments-area"> <h2 class="comments-title"> 2 Comments </h2> <ul class="comment-list"> <li id="comment-2556835" class="comment even thread-even depth-1"> <article id="div-comment-2556835" class="comment-body"> <footer class="comment-meta"> <div class="comment-author vcard"> <b class="fn">Kowsalya</b> <span class="says">says:</span> </div> <div class="comment-metadata"> <a href="https://blogs.cisco.com/networking/migrating-to-6ghz#comment-2556835"><time datetime="2022-07-16T07:23:28-07:00">July 16, 2022 at 7:23 am</time></a> </div> </footer> <div class="comment-content"> <p>Very Informative..</p> </div> </article> </li> <li id="comment-2556900" class="comment odd alt thread-odd thread-alt depth-1"> <article id="div-comment-2556900" class="comment-body"> <footer class="comment-meta"> <div class="comment-author vcard"> <b class="fn">Dan Davis</b> <span class="says">says:</span> </div> <div class="comment-metadata"> <a href="https://blogs.cisco.com/networking/migrating-to-6ghz#comment-2556900"><time datetime="2022-07-20T05:42:00-07:00">July 20, 2022 at 5:42 am</time></a> </div> </footer> <div class="comment-content"> <p>Great to see you call out RF differences that can sometimes be expected with 6GHz, and even better, a nice way to view the data!</p> </div> </article> </li> </ul> <p class="no-comments">Comments are closed.</p> </div> </main> </div> <div class="blog-row cui cta"> <div class="item-halves-1"> <div class="cta-container"> <div class="cta-image"> <img src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2021/11/IL20211110162602-Cisco-Networking-2-150x150.jpg"> </div>  <div class="cta-description"> <h2>Get More from Cisco Networking</h2> <p>Customer stories, technical demos and more await!</p> <div class="btn--parent"> <button class="btn--primary1" onclick="window.location.href = 'https://video.cisco.com/category/videos/networking';">  Check out our Networking video channel </button> </div>  </div>    </div>  </div>  <div class="item-halves-2"> <div class="cta-container"> <div class="cta-image"> <img src="https://storage.googleapis.com/blogs-images-new/ciscoblogs/1/2020/02/f7553bb4-av28722-150x150-1.jpg"> </div>  <div class="cta-description"> <h2>Multidomain Architecture</h2> <p>Learn how to integrate your networking domains and get more out of an enterprise-wide, intent-based network.</p> <div class="btn--parent"> <button class="btn--primary1" onclick="window.location.href = 'https://www.cisco.com/go/multidomain';">  Discover multidomain integration </button> </div>  </div>    </div>  </div>  </div> </div>  <div id="social-footer" class="blog-row"> <ul class="social-footer-item item-full"> <h5> CONNECT WITH US </h5> <ul id="social-icons-list"> <li> <a href="https://www.linkedin.com/company/cisco/" target="_blank" rel=”noopener noreferrer” tabindex="0" alt="Go to Cisco's LinkedIn"><svg width="32" height="32" viewBox="0 0 32 32" role="img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><path d="m24.80382,24.53603l-3.70694,0l0,-5.62559c0,-1.34209 -0.02431,-3.06801 -1.92709,-3.06801c-1.92986,0 -2.22361,1.46262 -2.22361,2.97171l0,5.72189l-3.70347,0l0,-11.56902l3.55417,0l0,1.58181l0.05069,0c0.49445,-0.90976 1.70486,-1.86868 3.50903,-1.86868c3.75347,0 4.44722,2.39528 4.44722,5.51111l0,6.34478zm-15.74236,-13.1495c-1.19097,0 -2.15139,-0.934 -2.15139,-2.08552c0,-1.15084 0.96042,-2.08485 2.15139,-2.08485c1.18611,0 2.14931,0.93401 2.14931,2.08485c0,1.15152 -0.9632,2.08552 -2.14931,2.08552l0,0zm1.85486,13.1495l0,-11.56902l-3.71111,0l0,11.56902l3.71111,0zm15.73403,-20.65724l-21.30556,0c-1.01736,0 -1.84444,0.78249 -1.84444,1.74815l0,20.74545c0,0.96499 0.82708,1.74882 1.84444,1.74882l21.30556,0c1.02014,0 1.84931,-0.78383 1.84931,-1.74882l0,-20.74545c0,-0.96566 -0.82917,-1.74815 -1.84931,-1.74815l0,0z" fill="#fff" fill-rule="evenodd"></path></svg></a></li> <li> <a href="https://twitter.com/Cisco/" target="_blank" rel=”noopener noreferrer” tabindex="0" alt="Go to Cisco's Twitter"><svg width="32" height="32" viewBox="0 0 32 32" role="img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <path d="M25.2019 2H30.1087L19.3887 13.8605L32 30H22.1254L14.3913 20.2115L5.54174 30H0.631901L12.0981 17.3138L0 2H10.1252L17.1162 10.9471L25.2019 2ZM23.4797 27.1569H26.1987L8.64785 4.69374H5.73013L23.4797 27.1569Z" fill="#fff"/> </svg></a></li> <li> <a href="https://www.facebook.com/cisco/" target="_blank" rel=”noopener noreferrer” tabindex="0" alt="Go to Cisco's Facebook"><svg width="32" height="32" viewBox="0 0 32 32" role="img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><path d="m26.62006,4l-22.2403,0c-0.7622,0 -1.37976,0.59894 -1.37976,1.33804l0,21.56635c0,0.73891 0.61756,1.33803 1.37976,1.33803l11.97343,0l0,-9.38796l-3.25793,0l0,-3.65868l3.25793,0l0,-2.69815c0,-3.13113 1.97213,-4.83613 4.85266,-4.83613c1.37975,0 2.56571,0.09955 2.91135,0.14415l0,3.2722l-1.99788,0.00091c-1.56654,0 -1.86993,0.72183 -1.86993,1.7812l0,2.33582l3.7362,0l-0.48652,3.65868l-3.24968,0l0,9.38796l6.37067,0c0.76191,0 1.37975,-0.59912 1.37975,-1.33803l0,-21.56635c0,-0.7391 -0.61784,-1.33804 -1.37975,-1.33804" fill="#fff"></path></svg></a></li> <li> <a href="https://www.instagram.com/cisco/?hl=en" target="_blank" rel=”noopener noreferrer” tabindex="0" alt= "Go to Cisco's Instagram"><svg width="32" height="32" viewBox="0 0 32 32" role="img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><g fill="#fff"><path d="m22.23823,2.07724l-12.4768,0c-4.23706,0 -7.68419,3.44729 -7.68419,7.68435l0,12.4768c0,4.23723 3.44713,7.68436 7.68419,7.68436l12.4768,0c4.23739,0 7.68452,-3.4473 7.68452,-7.68436l0,-12.4768c0.00016,-4.23706 -3.44713,-7.68435 -7.68452,-7.68435zm5.21409,20.16115c0,2.87494 -2.33899,5.21377 -5.21393,5.21377l-12.47696,0c-2.87478,0.00016 -5.2136,-2.33883 -5.2136,-5.21377l0,-12.4768c0,-2.87477 2.33882,-5.21376 5.2136,-5.21376l12.4768,0c2.87494,0 5.21393,2.33899 5.21393,5.21376l0,12.4768l0.00016,0z"></path><path d="m15.99999,8.82524c-3.9564,0 -7.17508,3.21868 -7.17508,7.17508c0,3.95624 3.21868,7.17476 7.17508,7.17476c3.9564,0 7.17509,-3.21852 7.17509,-7.17476c0,-3.9564 -3.21869,-7.17508 -7.17509,-7.17508zm0,11.87908c-2.59395,0 -4.70449,-2.11021 -4.70449,-4.70416c0,-2.59412 2.11038,-4.7045 4.70449,-4.7045c2.59412,0 4.7045,2.11038 4.7045,4.7045c0,2.59395 -2.11054,4.70416 -4.7045,4.70416z"></path><path d="m23.47599,6.73035c-0.476,0 -0.9436,0.1927 -1.27976,0.53035c-0.33781,0.336 -0.532,0.80376 -0.532,1.28141c0,0.47617 0.19435,0.94377 0.532,1.28141c0.336,0.336 0.80376,0.53036 1.27976,0.53036c0.47765,0 0.94377,-0.19436 1.28141,-0.53036c0.33765,-0.33764 0.53036,-0.80541 0.53036,-1.28141c0,-0.47765 -0.19271,-0.94541 -0.53036,-1.28141c-0.336,-0.33765 -0.80376,-0.53035 -1.28141,-0.53035z"></path></g></svg></a></li> <li> <a href="https://www.youtube.com/user/Cisco/welcome" target="_blank" rel=”noopener noreferrer” tabindex="0" alt="Go to Cisco's Youtube"><svg width="32" height="32" viewBox="0 0 32 32" role="img" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><path d="m12.73901,19.93335l-0.00144,-8.54172l8.47104,4.28574l-8.4696,4.25598zm18.59878,-10.02146c0,0 -0.30631,-2.09493 -1.24635,-3.01746c-1.19214,-1.21081 -2.52842,-1.21682 -3.14122,-1.28769c-4.38704,-0.30753 -10.96784,-0.30753 -10.96784,-0.30753l-0.01363,0c0,0 -6.58064,0 -10.96784,0.30753c-0.61283,0.07087 -1.94862,0.07688 -3.14119,1.28769c-0.93998,0.92253 -1.24586,3.01746 -1.24586,3.01746c0,0 -0.31352,2.46013 -0.31352,4.92024l0,2.30635c0,2.46008 0.31352,4.92018 0.31352,4.92018c0,0 0.30588,2.09496 1.24586,3.01749c1.19257,1.21085 2.7591,1.17254 3.45682,1.29945c2.50808,0.23321 10.65906,0.30539 10.65906,0.30539c0,0 6.58758,-0.00962 10.97462,-0.31712c0.6128,-0.07089 1.94908,-0.07687 3.14122,-1.28772c0.94004,-0.92253 1.24635,-3.01749 1.24635,-3.01749c0,0 0.31306,-2.4601 0.31306,-4.92018l0,-2.30635c0,-2.46011 -0.31306,-4.92024 -0.31306,-4.92024l0,0z" fill="#fff"></path></svg></a></li> </ul> </ul> </div>  </cdc-template-micro>  </div> <script type="text/javascript" src="//www.cisco.com/c/dam/cdc/t/ctm.js"></script> <script> function convert_to_url(obj) { return Object .keys(obj) .map(k => `${encodeURIComponent(k)}=${encodeURIComponent(obj[k])}`) .join('&'); } function pass_to_backend() { if(window.location.hash) { var hash = window.location.hash; var elements = {}; hash.split("#")[1].split("&").forEach(element => { var vars = element.split("="); elements[vars[0]] = vars[1]; }); if(("access_token" in elements) || ("id_token" in elements) || ("token" in elements)) { if(window.location.href.indexOf("?") !== -1) { window.location = (window.location.href.split("?")[0] + window.location.hash).split('#')[0] + "?" + convert_to_url(elements); } else { window.location = window.location.href.split('#')[0] + "?" + convert_to_url(elements); } } } } pass_to_backend(); </script> <script type='text/javascript' src='https://blogs.cisco.com/wp-content/themes/ciscowordpress/js/navigation.js?ver=20151215' id='ciscowordpress-navigation-js'></script> <script type='text/javascript' src='https://blogs.cisco.com/wp-content/themes/ciscowordpress/js/skip-link-focus-fix.js?ver=20151215' id='ciscowordpress-skip-link-focus-fix-js'></script> </body> </html>