Network Management

Hi,

I can't seem to find a way to generate a simple Up vs Down count of APs., or if there is one I'm simply not seeing it - so can anyone advise what options I need to be able to have this. I mean, there s uptime, but that's not the same as "is that AP up when the report was run", instead it shows how long it has been up. We are on v8.2.15.1

So, then I decide, let's take the headline count that shows:

Make sure there are no filters applied and directly export that data, only when imported to Excel the down count is out by 100 too many, and the UP count is out by 1,095 and also too many. I guess the question here is why does the headline show 3465 UP when the exported data is only 2,370 nodes? Even factoring in the 31 new nodes doesn't get us anywhere near the headline up.

Anybody have any thoughts / comments on this please?

Hi,

I can't seem to find a way to generate a simple Up vs Down count of APs., or if there is one I'm simply not seeing it - so can anyone advise what options I need to be able to have this. I mean, there s uptime, but that's not the same as "is that AP up when the report was run", instead it shows how long it has been up. We are on v8.2.15.1

So, then I decide, let's take the headline count that shows:

Make sure there are no filters applied and directly export that data, only when imported to Excel the down count is out by 100 too many, and the UP count is out by 1,095 and also too many. I guess the question here is why does the headline show 3465 UP when the exported data is only 2,370 nodes? Even factoring in the 31 new nodes doesn't get us anywhere near the headline up.

Hi Stuart,

I also saw the discrepancies of the AP up/down count for our environment and opened up a ticket with TAC. They had me reboot the mobility conductor and stated "As best practices, it is recommended to reboot the MM once or twice a year to keep SC-MON process up to date and provide accurate accounting." After reboot, the numbers were still not 100% exact but 'better' so not sure if that'll help you.

Bergson

Anybody have any thoughts / comments on this please?

Hi,

I can't seem to find a way to generate a simple Up vs Down count of APs., or if there is one I'm simply not seeing it - so can anyone advise what options I need to be able to have this. I mean, there s uptime, but that's not the same as "is that AP up when the report was run", instead it shows how long it has been up. We are on v8.2.15.1

So, then I decide, let's take the headline count that shows:

Make sure there are no filters applied and directly export that data, only when imported to Excel the down count is out by 100 too many, and the UP count is out by 1,095 and also too many. I guess the question here is why does the headline show 3465 UP when the exported data is only 2,370 nodes? Even factoring in the 31 new nodes doesn't get us anywhere near the headline up.

Interesting and thanks for the reply. 

As you suggest, it is not really an answer but it might go some way to alleviating the low hanging fruit.

Hi Stuart,

I also saw the discrepancies of the AP up/down count for our environment and opened up a ticket with TAC. They had me reboot the mobility conductor and stated "As best practices, it is recommended to reboot the MM once or twice a year to keep SC-MON process up to date and provide accurate accounting." After reboot, the numbers were still not 100% exact but 'better' so not sure if that'll help you.

Bergson

Anybody have any thoughts / comments on this please?

Hi,

I can't seem to find a way to generate a simple Up vs Down count of APs., or if there is one I'm simply not seeing it - so can anyone advise what options I need to be able to have this. I mean, there s uptime, but that's not the same as "is that AP up when the report was run", instead it shows how long it has been up. We are on v8.2.15.1

So, then I decide, let's take the headline count that shows:

Make sure there are no filters applied and directly export that data, only when imported to Excel the down count is out by 100 too many, and the UP count is out by 1,095 and also too many. I guess the question here is why does the headline show 3465 UP when the exported data is only 2,370 nodes? Even factoring in the 31 new nodes doesn't get us anywhere near the headline up.

 Reports are always historical data. It doesn't mean the AP count fluctuates. But it wont show currently up and down but rather last hour or day etc so is the uptime info the report.

Have you tried CSV export of Device > List page with all folders expanded with Status column? This will show the current info with IP and down status.  I do not see the issue on QA server with ~2K devices. There may be stale entries on the server. In the past, was there device replacements with same IP but the AP's are replaced?

Interesting and thanks for the reply. 

As you suggest, it is not really an answer but it might go some way to alleviating the low hanging fruit.

Hi Stuart,

I also saw the discrepancies of the AP up/down count for our environment and opened up a ticket with TAC. They had me reboot the mobility conductor and stated "As best practices, it is recommended to reboot the MM once or twice a year to keep SC-MON process up to date and provide accurate accounting." After reboot, the numbers were still not 100% exact but 'better' so not sure if that'll help you.

Bergson

Anybody have any thoughts / comments on this please?

Hi,

I can't seem to find a way to generate a simple Up vs Down count of APs., or if there is one I'm simply not seeing it - so can anyone advise what options I need to be able to have this. I mean, there s uptime, but that's not the same as "is that AP up when the report was run", instead it shows how long it has been up. We are on v8.2.15.1

So, then I decide, let's take the headline count that shows:

Make sure there are no filters applied and directly export that data, only when imported to Excel the down count is out by 100 too many, and the UP count is out by 1,095 and also too many. I guess the question here is why does the headline show 3465 UP when the exported data is only 2,370 nodes? Even factoring in the 31 new nodes doesn't get us anywhere near the headline up.