[c-nsp] interpretation of sysTrafficPeakTime

[Tassos Chatzithomaoglou]

Arie,

Actually i was using "sh platform hardware capacity fabric" to see it through the cli.

Still, my main concern is... should i stick to my 1st explanation or the 2nd one?

--
Tassos

Arie Vayner (avayner) wrote on 29/7/2008 11:22 μμ:
> Tasso,
> 
> Your analysis makes sense.
> It seems that this OID is basically what you can see with this command:
> Router#show catalyst6000 traffic-meter
>   traffic meter =   1%  Never cleared
>            peak =   1%        reached at 20:14:17 UTC Tue Jul 29 2008 
> 
> Arie
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tassos
> Chatzithomaoglou
> Sent: Tuesday, July 29, 2008 20:22 PM
> To: cisco-nsp
> Subject: [c-nsp] interpretation of sysTrafficPeakTime
> 
> 
> According to the cisco-stack-mib:
> 
> sysTrafficPeakTime OBJECT-TYPE
>          SYNTAX        TimeTicks
>          MAX-ACCESS    read-only
>          STATUS        current
> DESCRIPTION   "The time (in hundredths of a second) since the peak
> traffic meter value
> occurred."
>          ::= { systemGrp 20 }
> 
> 
> Can someone please interpret the above description?
> 
> 
> I'm thinking of 2 different values here:
> 
> 1) current time (present) <=== peak time (past)     : the value should
> increase as time passes by (*)
> 
> 2) power-on/reset time (past) ===> peak time (past) : the value should
> stay constant as time passes by (*)
> 
> 
> If i was to interpret it, i would probably choose the 1st one, but
> according to my sample snmp outputs on some 6500s/7600s the 2nd seems to
> be the correct one.
> 
> (*) having only one peak traffic time
> 
> --
> Tassos
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>