Capwap Mailing List: Re: [Couter32 issue] If it is ok, I would follow the Dan's suggestion

(continued)

works for me.

Bert

young wrote:
> Hi, All:
>
> If it is ok, I would follow the Dan's suggestion. 
> The new text would be:
> capwapBaseWtpEventsStatsRebootCount OBJECT-TYPE
>     SYNTAX      Counter32
>     MAX-ACCESS  read-only
>     STATUS      current
>     DESCRIPTION
>         "Represents the number of reboots that have occurred due to a
>          WTP crash. 
>          Note that the CAPWAP field [RFC 5415] modelled by this counter 
>          takes the value 65535 to indicate that the information is not
> available
>          on the WTP. This MIB object does not follow this behaviour which 
>          would not be standard in SMIv2. If the WTP does not have the
> information, 
>         the agent will not instantiate the object."
>     REFERENCE
>         "Section 4.6.47. of CAPWAP Protocol Specification, RFC 5415."
>     ::= { capwapBaseWtpEventsStatsEntry 1 }
>
> Same change would be done to the capwapBaseWtpEventsStatsInitCount.
>
> Regards
> Richard
>
>   

Re: [Couter32 issue] If it is ok, I would follow the Dan's suggestion	<– Date –> <– Thread –>
From: Bert (IETF) Wijnen (bertietfbwijnen.net)
Date: Tue, 8 Dec 2009 00:35:22 -0800 (PST)