AP7372 has an up time of 3 hours+

  • 1
  • Question
  • Updated 2 years ago
AP7372 has an up time of 3 hours+ whereby some amounted to days. This has caused slow connectivity. Please help to identify potential issue.
Photo of Jayne Chin

Jayne Chin

  • 2 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of JS

JS

  • 9 Posts
  • 1 Reply Like
Jayne Chin, What uptime do you normally experience?
Photo of Jayne Chin

Jayne Chin

  • 2 Posts
  • 0 Reply Likes
What is ruckus standard of usual uptime. However, But normally, all network devices (other brands) should register their uptime since the day they were turned on or the day they were rebooted, or crashed.
So, at that day, there's no manual power cycle or power failure, no one did any firmware upgrade which might cause the AP to reboot itself. So the only explanation left is that device crashed?
Is this is the standard experienced by all Ruckus users.
Photo of Sean

Sean

  • 342 Posts
  • 87 Reply Likes
is this AP managed or stand alone?
Photo of Monnat Systems

Monnat Systems, AlphaDog

  • 714 Posts
  • 151 Reply Likes
Jayne,

uptime on Ruckus device you see is primarily after last reboot. if you are not able to make out what would have caused so it would be power reboot, software crash (many reasons within it)

you should pull a AP support of this AP and report it to support dept so that they can review it
Photo of Sean

Sean

  • 342 Posts
  • 87 Reply Likes
if the AP has rebooted and you dont have himem enabled you'll get nothing from the AP and the support log will be useless
Photo of JS

JS

  • 9 Posts
  • 1 Reply Like

Jayne,

     Did you get your uptime and connectivity issue resolved?  If so, could you share your findings?