Template for catalyst 3750 and catalyst 3560G

terry.ble · Post by **terry.ble** » Wed Mar 21, 2007 6:01 am

HEllo I'm looking for templates for this both Cisco equipments:

WS-C3560G-24TS OR 48TS

WS-C3750-48P

Generic SNMP can not give me something.

This materiel status is marked as unknow

thanks for your help

Howie · Post by **Howie** » Wed Mar 21, 2007 7:04 am

terry.ble wrote:HEllo I'm looking for templates for this both Cisco equipments:

WS-C3560G-24TS OR 48TS

WS-C3750-48P

Generic SNMP can not give me something.

This materiel status is marked as unknow

thanks for your help

I'm using the Cisco Router host template for our 3750G-24TS and 3650G-24TS switches with no problems... what is the "something" that you want? I get CPU usage OK from that template, and interface stats from the generic SNMP template (with 64-bit counters and SNMP 2c for the gig-e).

adrianmarsh · Post by **adrianmarsh** » Mon Apr 16, 2007 5:12 pm

Howie, Which template are you using for the 64-bit counters?

Howie · Post by **Howie** » Mon Apr 16, 2007 5:21 pm

adrianmarsh wrote:Howie, Which template are you using for the 64-bit counters?

The regular Interface Traffic one - "bits/sec 64-bit counters". Make sure you have SNMP 2c at least on the device, from what I remember. I don't have any special config for that on these switches, so I guess it just works - just the usual "snmp-server community".

aleu · Post by **aleu** » Sat Apr 28, 2007 9:18 pm

Howie wrote: I'm using the Cisco Router host template for our 3750G-24TS and 3650G-24TS switches with no problems... what is the "something" that you want? I get CPU usage OK from that template, and interface stats from the generic SNMP template (with 64-bit counters and SNMP 2c for the gig-e).

Could somebody explain me why sometimes it is required to use v1 and sometimes v2 of SNMP? Why for the GIG ports it is required to use the 64 bit counters? Sorry for the lame question, but I just do not get it.

Thanks

adrianmarsh · Post by **adrianmarsh** » Sun Apr 29, 2007 3:40 am

Well,

64-bit counters are needed when theres a chance that a normal 32-bit counter could roll-over quickly before the next poll. A Gigabit port is an example of this.

I'm not sure why Howie says to use SNMP 2e, but it could be because theres better 64-bit support in that version.

Howie · Post by **Howie** » Sun Apr 29, 2007 4:46 am

adrianmarsh wrote:Well,

64-bit counters are needed when theres a chance that a normal 32-bit counter could roll-over quickly before the next poll. A Gigabit port is an example of this.

I'm not sure why Howie says to use SNMP 2e, but it could be because theres better 64-bit support in that version.

My memory was that there isn't any 64-bit counter support in 1. Maybe I'm just losing it though.

Aside from anything else 2c gets you bulk requests, which makes any SNMP requests a bit more efficient though.

Howie · Post by **Howie** » Sun Apr 29, 2007 4:42 pm

Howie wrote:My memory was that there isn't any 64-bit counter support in 1. Maybe I'm just losing it though.

Indeed, according to these guys, 2c adds 64-bit counters.
http://www.paessler.com/manuals/prtg_tr ... 2cand3.htm
and they should know a thing or two about snmp.

Howie wrote: Aside from anything else 2c gets you bulk requests, which makes any SNMP requests a bit more efficient though.

aleu · Post by **aleu** » Sun Apr 29, 2007 9:31 pm

adrianmarsh wrote:Well,

64-bit counters are needed when theres a chance that a normal 32-bit counter could roll-over quickly before the next poll. A Gigabit port is an example of this.

Thanks for your response, but when does a counter roll-over? How can I know whether it is needed to change the SNMP version to 2?

Howie · Post by **Howie** » Mon Apr 30, 2007 2:33 am

aleu wrote:
adrianmarsh wrote:Well,

64-bit counters are needed when theres a chance that a normal 32-bit counter could roll-over quickly before the next poll. A Gigabit port is an example of this.
Thanks for your response, but when does a counter roll-over? How can I know whether it is needed to change the SNMP version to 2?

If you start to see strange 'steps' in your gig interfaces, then that's time to use 64-bit counters. You will find a bunch of messages on here talking about clipping on gig interfaces around 120Mb (here's one, for example). Basically, you should really use 64-bit counters from the start, if you expect to get above 100M or so, otherwise the 32-bit counters will wrap around within the 5 minutes of the polling cycle. The other solution is to shorten the poller cycle, but that means patching Cacti, and (if I did my math right) doesn't let you get up to a full gig still.

aleu · Post by **aleu** » Mon Apr 30, 2007 8:56 am

Howie wrote:If you start to see strange 'steps' in your gig interfaces, then that's time to use 64-bit counters. You will find a bunch of messages on here talking about clipping on gig interfaces around 120Mb (here's one, for example). Basically, you should really use 64-bit counters from the start, if you expect to get above 100M or so, otherwise the 32-bit counters will wrap around within the 5 minutes of the polling cycle. The other solution is to shorten the poller cycle, but that means patching Cacti, and (if I did my math right) doesn't let you get up to a full gig still.

I see, thanks. It is more clear to me now.

Cacti

Template for catalyst 3750 and catalyst 3560G

Template for catalyst 3750 and catalyst 3560G

Re: Template for catalyst 3750 and catalyst 3560G

Re: Template for catalyst 3750 and catalyst 3560G

Who is online