Wireless Access

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks ! 

Have you opened a case with TAC?

If you are running a single campus, is there a reason not to run everything as a single cluster?

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks ! 

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks ! 

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks ! 

each NPS has own CERT , is not 'shared' or wild-card cert

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks ! 

each NPS has own CERT , is not 'shared' or wild-card cert

Good day all

we have 3 main controller-based locations (7210 , 7205 , 7205) where we have same-named SSID ('company') and all using same back-end NPS servers (3 spread-shot across campuses)

the problem we have had for a long time is that as a user moves from one bldg that is based on 7210 , to another based on 7205-A ,  many-times they need to 'forget' the 'Company' SSID , in order to re-connect to 'same SSID' that's being controlled by different controller.

it is basically a 'walking with a pebble in your shoe' for past couple YEARS now...and mgmt would really like to get this snafu FIXED, so it's more seamless (read: no forget/re-connect operation when traveling state-to-state , or , in case of a campus, needing to do same when moving one bldg to another).

Each Controller is in its own ManagedNetwork of MobilityMaster ..and we have used same inside CA Cert for Windows Auth on each controller config

any suggestions on what to look for as a differentiator ? 

thanks !