Network Management

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

Another thing I've tried is bringing the old APs back online.  I did this in another building and their info updated in AirWave (switch/upstream port).  After taking them back offline one of the APs correctly updated as down but two still report as up.  

I also noticed that in the AirWave events, the APs continue to show as UP after being taken offline but once brought back online they show: "Device has rebooted" then "Down" then "Up" in that order but with the same timestamp.  It seems AirWave does not register they were offline until they come back online.  

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

That is strange. Haven't seen that before. Are you Ok to restart services? If so, i suggest doing 'Restart AMP' which will restart the services and UI may be inaccessible for 5 mins. This will NOT reboot the server, its the services only. Can you also send me screenshot of AMON statistics section from System > Performance page to make sure there is no backlog.

Another thing I've tried is bringing the old APs back online.  I did this in another building and their info updated in AirWave (switch/upstream port).  After taking them back offline one of the APs correctly updated as down but two still report as up.  

I also noticed that in the AirWave events, the APs continue to show as UP after being taken offline but once brought back online they show: "Device has rebooted" then "Down" then "Up" in that order but with the same timestamp.  It seems AirWave does not register they were offline until they come back online.  

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

I'll check to see if I can restart AMP.  Here's a screenshot of our AMON statistics.

Original Message:
Sent: Mar 10, 2025 04:20 PM
From: Gowri Amujuri
Subject: AirWave not updating down status of AP

That is strange. Haven't seen that before. Are you Ok to restart services? If so, i suggest doing 'Restart AMP' which will restart the services and UI may be inaccessible for 5 mins. This will NOT reboot the server, its the services only. Can you also send me screenshot of AMON statistics section from System > Performance page to make sure there is no backlog.

------------------------------
Regards
Gowri Amujuri

Original Message:
Sent: Mar 10, 2025 01:47 PM
From: bwoodroof
Subject: AirWave not updating down status of AP

Another thing I've tried is bringing the old APs back online.  I did this in another building and their info updated in AirWave (switch/upstream port).  After taking them back offline one of the APs correctly updated as down but two still report as up.  

I also noticed that in the AirWave events, the APs continue to show as UP after being taken offline but once brought back online they show: "Device has rebooted" then "Down" then "Up" in that order but with the same timestamp.  It seems AirWave does not register they were offline until they come back online.  

Original Message:
Sent: Mar 07, 2025 04:06 PM
From: bwoodroof
Subject: AirWave not updating down status of AP

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Original Message:
Sent: Mar 07, 2025 12:48 PM
From: Gowri Amujuri
Subject: AirWave not updating down status of AP

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

------------------------------
Regards
Gowri Amujuri

Original Message:
Sent: Mar 07, 2025 12:14 PM
From: bwoodroof
Subject: AirWave not updating down status of AP

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

Looks good. There are no packet losses and the packets are processed in time. I believe there may be something stuck in SNMP service. AP status is through SNMP and AP details are through AMON.  I expect Restart services will fix the issue. If not, I would suggest to open a ticket with TAC to check.

I'll check to see if I can restart AMP.  Here's a screenshot of our AMON statistics.

That is strange. Haven't seen that before. Are you Ok to restart services? If so, i suggest doing 'Restart AMP' which will restart the services and UI may be inaccessible for 5 mins. This will NOT reboot the server, its the services only. Can you also send me screenshot of AMON statistics section from System > Performance page to make sure there is no backlog.

Another thing I've tried is bringing the old APs back online.  I did this in another building and their info updated in AirWave (switch/upstream port).  After taking them back offline one of the APs correctly updated as down but two still report as up.  

I also noticed that in the AirWave events, the APs continue to show as UP after being taken offline but once brought back online they show: "Device has rebooted" then "Down" then "Up" in that order but with the same timestamp.  It seems AirWave does not register they were offline until they come back online.  

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?

Restart services fixed the issue.  Thanks!

Looks good. There are no packet losses and the packets are processed in time. I believe there may be something stuck in SNMP service. AP status is through SNMP and AP details are through AMON.  I expect Restart services will fix the issue. If not, I would suggest to open a ticket with TAC to check.

I'll check to see if I can restart AMP.  Here's a screenshot of our AMON statistics.

That is strange. Haven't seen that before. Are you Ok to restart services? If so, i suggest doing 'Restart AMP' which will restart the services and UI may be inaccessible for 5 mins. This will NOT reboot the server, its the services only. Can you also send me screenshot of AMON statistics section from System > Performance page to make sure there is no backlog.

Another thing I've tried is bringing the old APs back online.  I did this in another building and their info updated in AirWave (switch/upstream port).  After taking them back offline one of the APs correctly updated as down but two still report as up.  

I also noticed that in the AirWave events, the APs continue to show as UP after being taken offline but once brought back online they show: "Device has rebooted" then "Down" then "Up" in that order but with the same timestamp.  It seems AirWave does not register they were offline until they come back online.  

All APs, old and new, have unique IP addresses.  They also currently have different AP names. 

The new APs were provisioned before install, so they didn't show up as new.  I moved them into the same building folder as the old APs and after coming up they showed their new/correct IP addresses and switch information.  So polling is working on the new APs.

Does the Old AP and new AP have same IP Address? If so, that is possible the old AP still shows up as it uses IP to ping. Do you see new AP's as new devices or see a message 'Duplicate MAC found' on old AP Manage page?

I recently replaced 7 APs.  All of the old APs are disconnected, and down on MM, but in AirWave only 3 of them show as down.  I tried polling the controllers and deleted one of the down APs from MM but these 4 still show as up in AirWave.  It's been over 24 hours since the APs were replaced, and the last contacted date/time is correct for when they were removed, but the APs still show as UP.

I know I could remove the old APs from AirWave, but I'd like to use the replace hardware functionality to keep the AirWave stats and visual RF data.  Has anyone seen this issue before or know of a workaround?