[ Parse ASCII OID ] JunOS VCP

Templates, scripts for templates, scripts and requests for templates.

Moderators: Developers, Moderators

Post Reply
ZuZuD
Posts: 1
Joined: Tue Feb 14, 2017 12:41 pm

[ Parse ASCII OID ] JunOS VCP

Post by ZuZuD »

Hello there,

I have a project on which I need to monitor the VCP between 4 EX-4500 switch. My final goal is to display it on a MAP using the famous WeatherMap plugin.

As the default MIB isn't included in the version of my EX-54500 JunOS, I followed these instructions to implement them : https://kb.juniper.net/InfoCenter/index ... id=KB27711

That's my current output :

Code: Select all

root@XXXsw02p-0> show snmp mib walk jnxUtilCounter64Value
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110 = 8469
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.111.117.116 = 1265
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.105.110 = 13998917090
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.111.117.116 = 15416213439
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.105.110 = 13886
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117.116 = 1713
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.105.110 = 24251112925
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.111.117.116 = 49998816709
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110 = 4878
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.111.117.116 = 3216
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.105.110 = 15404370392
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.111.117.116 = 13985368568
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.52.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.105.110 = 5363
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117.116 = 1774
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.105.110 = 4978645681
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.111.117.116 = 10018269436
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.49.45.118.99.112.45.50.53.53.47.48.47.50.53.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110 = 15309
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.111.117.116 = 2861
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.105.110 = 16541895363
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.111.117.116 = 15520623633
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.52.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.105.110 = 89896
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117.116 = 7730
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.105.110 = 49995451874
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.111.117.116 = 24247397617
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.50.45.118.99.112.45.50.53.53.47.48.47.50.53.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110 = 12285
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.111.117.116 = 6052
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.105.110 = 15520619133
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.121.116.101.115.45.111.117.116 = 16541891619
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.52.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.105.110 = 6049
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117.116 = 3080
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.105.110 = 2120343888
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.121.116.101.115.45.111.117.116 = 4978642493
jnxUtilCounter64Value.52.55.52.51.45.102.112.99.51.45.118.99.112.45.50.53.53.47.48.47.50.53.45.99.114.99 = 0
jnxUtilCounter64Value.52.55.52.51.45.116.114.97.99.107.101.114 = 1
Or in ASCII :

Code: Select all

{master:0}
root@XXXsw02p-0> show snmp mib walk jnxUtilCounter64Value ascii
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/24-bps-in" = 8469
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/24-bps-out" = 1265
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/24-bytes-in" = 13998917090
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/24-bytes-out" = 15416213439
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/24-crc" = 0
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/25-bps-in" = 13886
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/25-bps-out" = 1713
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/25-bytes-in" = 24251112925
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/25-bytes-out" = 49998816709
jnxUtilCounter64Value."4743-fpc0-vcp-255/0/25-crc" = 0
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/24-bps-in" = 4878
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/24-bps-out" = 3216
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/24-bytes-in" = 15404370392
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/24-bytes-out" = 13985368568
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/24-crc" = 0
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/25-bps-in" = 5363
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/25-bps-out" = 1774
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/25-bytes-in" = 4978645681
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/25-bytes-out" = 10018269436
jnxUtilCounter64Value."4743-fpc1-vcp-255/0/25-crc" = 0
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/24-bps-in" = 15309
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/24-bps-out" = 2861
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/24-bytes-in" = 16541895363
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/24-bytes-out" = 15520623633
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/24-crc" = 0
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/25-bps-in" = 89896
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/25-bps-out" = 7730
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/25-bytes-in" = 49995451874
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/25-bytes-out" = 24247397617
jnxUtilCounter64Value."4743-fpc2-vcp-255/0/25-crc" = 0
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/24-bps-in" = 12285
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/24-bps-out" = 6052
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/24-bytes-in" = 15520619133
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/24-bytes-out" = 16541891619
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/24-crc" = 0
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/25-bps-in" = 6049
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/25-bps-out" = 3080
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/25-bytes-in" = 2120343888
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/25-bytes-out" = 4978642493
jnxUtilCounter64Value."4743-fpc3-vcp-255/0/25-crc" = 0
jnxUtilCounter64Value."4743-tracker" = 1
Great! I'm able to snmpwalk through my VCP interfaces!

But the problem begin here, as you probably noticed looking the 2nd output, it's an ASCII OID Tree.
I've followed those instructions for non indexed OID Tree : http://docs.cacti.net/howto:data_query_templates but I'm stuck testing different variations.

I don't need all the fields, so here is my Data Query :

Code: Select all

<query>
<name>VCP Link</name>
<description>Get all VCP Link informations</description>
<oid_index>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50</oid_index>
<oid_index_parse>OID/REGEXP:.*\.([0-9]{1,3}\.[0-9]{1,3})$</oid_index_parse>
<index_order_type>oid</index_order_type>

<fields>
   
   <indexVCP>
   <name>Index_VPC</name>
   <method>walk</method>
   <source>value</source>
   <direction>input</direction>
   <oid>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50</oid>
   </indexVCP>

   <fcp0024in>
   <name>FCP0 0/24 IN</name>
   <method>walk</method>
   <source>value</source>
   <direction>output</direction>
   <oid>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110</oid>
   </fcp0024in>

   <fcp0024out>
   <name>FCP0 0/24 OUT</name>
   <method>walk</method>
   <source>value</source>
   <direction>output</direction>
   <oid>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.111.117.116</oid>
   </fcp0024out>
   
   <fcp0025in>
   <name>FCP0 0/25 IN</name>
   <method>walk</method>
   <source>value</source>
   <direction>output</direction>
   <oid>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.105.110</oid>
   </fcp0025in>
   
   <fcp0025out>
   <name>FCP0 0/25 OUT</name>
   <method>walk</method>
   <source>value</source>
   <direction>output</direction>
   <oid>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117.116</oid>
   </fcp0025out>
</fields>
</query>
But output is not relevant :

Code: Select all

+ Running data query [16].
+ Found type = '4' [Script Query].
+ Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/vcp_link.xml'
+ XML file parsed ok.
+ <arg_num_indexes> missing in XML file, 'Index Count Changed' emulated by counting arg_index entries
+ Executing script for list of indexes ' ' Index Count: 0
+ Executing script query ' '
I tried something different, 1 file per interface maybe ?

Code: Select all

<interface>
	<name>Get VCP Informations</name>
	<index_order_type>numeric</index_order_type>
	<oid_index>.1.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.53.45.98.112.115.45.111.117</oid_index>
	<oid_index_parse>OID/REGEXP:.*\.([0-9]{1,3})$</oid_index_parse> 
	<index_order>Index</index_order>
	<index_order_type>alphabetic</index_order_type>

	<fields>
		<Index>
			<name>fpc0-vcp-255/0/25-bps-out</name>
			<source>index</source>
			<direction>input</direction>
		</Index>
	</fields>

</interface>
The output seems better...

Code: Select all

Data Query Debug Information
+ Running data query [14].
+ Found type = '3' [SNMP Query].
+ Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/fpc0_24_out.xml'
+ XML file parsed ok.
+ <oid_num_indexes> missing in XML file, 'Index Count Changed' emulated by counting oid_index entries
+ Executing SNMP walk for list of indexes @ 'iso.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105' Index Count: 1
+ Index found at OID: 'iso.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110' value: '1750730'
+ index_parse at OID: 'iso.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110' results: '110'
+ Located input field 'bps-in' [get]
+ Executing SNMP get for data @ 'iso.3.6.1.4.1.2636.3.47.1.1.2.1.2.52.55.52.51.45.102.112.99.48.45.118.99.112.45.50.53.53.47.48.47.50.52.45.98.112.115.45.105.110' [value='1750730']
But managing Graph template and Data templates this way would be more complex. Therefore, this is for sure the wrong way of doing it.
So dear community, can you give me a hand on this?
smcline06
Posts: 27
Joined: Mon Apr 22, 2013 1:30 pm

Re: [ Parse ASCII OID ] JunOS VCP

Post by smcline06 »

By chance does the files in http://forums.cacti.net/viewtopic.php?f=12&t=56634 answer or cover your needs?
smcline06
Posts: 27
Joined: Mon Apr 22, 2013 1:30 pm

Re: [ Parse ASCII OID ] JunOS VCP

Post by smcline06 »

By chance does the files in http://forums.cacti.net/viewtopic.php?f=12&t=56634 answer or cover your needs?
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests