[c-nsp] Measuring Routers temperature

[Arie Vayner]

look at this one:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d2d26.html

Arie

On 7/12/05, Kim Onnel <karim.adel at gmail.com> wrote:
> I mean setting a trap for CPU utilization ?
> 
> > Could there be anything similar for CPU utilization ?
> >
> > Yes
> 
> 
> Can i do the same for pps on interfaces, so if it goes higher than a certain
> number, a trap would be sent, NOC notified ?
> 
> One question about the memory OIDs, what am i exactly looking for when i
> graph the memory, what does it offer more than CPU ?
> 
> .1.3.6.1.4.1.9.9.13.1.3.1.3.1 = cisco inlet temp in C
> > .1.3.6.1.4.1.9.9.48.1.1.1.5.1 gives proc memory used
> > .1.3.6.1.4.1.9.9.48.1.1.1.5.2 gives i/o memory used
> > .1.3.6.1.4.1.9.9.48.1.1.1.6.1 = proc mem free
> > .1.3.6.1.4.1.9.9.48.1.1.1.6.2 = i/o mem free
> > .1.3.6.1.4.1.9.9.48.1.1.1.7.1 gives proc largest contiguous block free
> > .1.3.6.1.4.1.9.9.48.1.1.1.7.2 gives i/o largest contiguous block free
> >
> > .1.3.6.1.4.1.9.9.109.1.1.1.1.3.1 = cpmCPUTotal5sec
> > .1.3.6.1.4.1.9.9.109.1.1.1.1.4.1 = cpmCPUTotal1min
> > .1.3.6.1.4.1.9.9.109.1.1.1.1.5.1 = cpmCPUTotal5min
> 
> 
> 
> Thanks, it had almost all you mentioned above.
> 
> You might want to visit:
> >
> > http://www.ansdell.demon.co.uk/networks/monitor.html
> >
> >
> > --
> > Jared Mauch | pgp key available via finger from jared at puck.nether.net
> > clue++; | http://puck.nether.net/~jared/ My statements are only mine.
> 
> 
> 
> Regards
> _______________________________________________
> 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/
>