Add proto opt (TCP) to Data Input Methods [Get SNMP data]

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
huck
Posts: 1
Joined: Mon Nov 08, 2004 6:49 pm

Add proto opt (TCP) to Data Input Methods [Get SNMP data]

Post by huck »

Hey folks,
I've got a situation where the only access I have to a several remote hosts I need to graph data for is ssh. So currently what I have setup is a system on my lan with ssh sessions out to the remote systems, each tunneling tcp/161 back through the ssh connections as gateway ports (note, each remote system is given its own sub-interface/IP on the local system).

The remote hosts are all running net-snmp and listening on tcp/161 on the loopback addresses.

So running commands like,
snmpget -O vUq -v 1 -c my_string tcp:Local_IP:161 HOST-RESOURCES-MIB::hrSystemNumUsers.0
work great, and I've got several graphs collecting data this way.

The one problem I'm running into is setting up templates and such to handle this scenario. I'm sure that after enough random clicking I'll figure that part out…

But my real question is, to someone who is familiar w/ the Cacti, would my time be better spent trying to change the way Cacti uses snmpget to allow for a specific IP protocol type to be declared?

For example, in Data Input Methods [edit: Get SNMP Data], add an Input Field like 'management_ip_proto' so that perhaps instead of just pulling in the 'hostname' value, you could provide a value like 'tcp:hostname:port'. If this were to work I could then use all the great existing graph templates, etc.

I’m gonna continue to monkey around with the above idea, but hopefully there are others out there who have already solved an issue like this.

So any thoughts, comments and suggestions are all welcome!
Huck
Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests