Network Management

 View Only
  • 1.  Bootstraps vs Reboots

    Posted 10 hours ago

    Hey all,

    I'm trying to understand if the figures our NMS shows is meaningful in anyway.

    We are using the following two OID's:

    • 1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.20.160.37.215.199.232.14 - wlanAPNumBootstraps
    • 1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.21.160.37.215.199.232.14 - wlanAPNumReboots

    My basic understanding is that Reboots is just that, the number of times the AP has restarted, but I'm unsure of bootstraps. My presumption is that it is to do with the number of times an AP has tried to renegotiate its connection with the controller. As such, I absolutely understand that bootstraps could easily be larger than reboots.

    But what if it's the other way around. Does a reboot not also require a bootstrap meaning that bootstraps should at least equal reboots - yes? Or no? If not can you clarify my understanding please as these figures are throwing me:

    Whereas these ones scream out to me that AP01 is having issues:

    Thoughts and any immediate advice on how to start tracking down what the issue(s) are given my assumptions being correct?



    ------------------------------
    Stuart D
    ------------------------------


  • 2.  RE: Bootstraps vs Reboots

    Posted 9 hours ago

    Your instinct is right that a reboot should produce a bootstrap, but the two counters don't share a source or a lifetime, which is why the comparison misbehaves. Reboots is the AP's own restart count reported up to the controller. Bootstraps counts registrations with the controller, and it moves without any reboot at all: a heartbeat loss, an image sync, a failover, or a cluster re-home each add one, which is why bootstraps usually runs higher. When you see the reverse, you're looking at counter lifetime rather than events: the controller's bootstrap count starts over when the AP's state gets rebuilt or the AP re-homes, while the reboot number rides along with the AP.

    So don't read the absolutes, watch the deltas. A quiet AP moves neither counter. An AP adding bootstraps without reboots has a connectivity or failover problem. An AP adding both is actually restarting, and that first AP in your list sounds like the middle case.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------