Allot Netenforcer

xeon · Post by **xeon** » Fri Feb 24, 2006 11:46 am

Hi all.

I'm trying to setup some traffic monitoring on an Allot NetEnforcer using Cacti.
To accomplish this, I was trying to follow the "Howto: from snmptable to XML Graphs (Data Query walkthrough)" ... but I've failed miserabily on the 1st step

Here's the snmtable command output:
$> snmptable -c mypass -v 1 my.host.domain PIPE-MIB::pipeStatTable
SNMP table: PIPE-MIB::pipeStatTable

pipePosition pipeInstancePosition pipeName pipeByteCountIn pipeByteCountOut pipeByteCountTotal pipeLiveConnections pipeNewConnections pipePacketsIn pipePacketsOut pipePacketsTotal
1 0 PIPNAME1 25938332888 7678099821 33616432709 20891 1662241 34496499 29072369 63571501
2 0 PIPENAME2 80461483612 25588656778 106050140391 66133 4831554 98258659 85408409 183667068
3 0 Fallback Pipe 1051706 5077003 6128709 13 5921 12876 22264 35140

And the snmpwalk output:
$> snmpwalk -c mypass -v 1 my.host.domain PIPE-MIB::pipeStatTable
.1.3.6.1.4.1.2603.1.2.1.1.1.1.1.0 = INTEGER: 1
.1.3.6.1.4.1.2603.1.2.1.1.1.1.2.0 = INTEGER: 2
.1.3.6.1.4.1.2603.1.2.1.1.1.1.3.0 = INTEGER: 3
.1.3.6.1.4.1.2603.1.2.1.1.1.2.1.0 = INTEGER: 0
.1.3.6.1.4.1.2603.1.2.1.1.1.2.2.0 = INTEGER: 0
.1.3.6.1.4.1.2603.1.2.1.1.1.2.3.0 = INTEGER: 0
.1.3.6.1.4.1.2603.1.2.1.1.1.3.1.0 = STRING: PIPENAME1
.1.3.6.1.4.1.2603.1.2.1.1.1.3.2.0 = STRING: PIPENAME2
.1.3.6.1.4.1.2603.1.2.1.1.1.3.3.0 = STRING: Fallback Pipe
.1.3.6.1.4.1.2603.1.2.1.1.1.4.1.0 = Counter64: 26783668350
.1.3.6.1.4.1.2603.1.2.1.1.1.4.2.0 = Counter64: 83313825514
.1.3.6.1.4.1.2603.1.2.1.1.1.4.3.0 = Counter64: 1073161
.1.3.6.1.4.1.2603.1.2.1.1.1.5.1.0 = Counter64: 7930753997
.1.3.6.1.4.1.2603.1.2.1.1.1.5.2.0 = Counter64: 26515688406
.1.3.6.1.4.1.2603.1.2.1.1.1.5.3.0 = Counter64: 5170836
.1.3.6.1.4.1.2603.1.2.1.1.1.6.1.0 = Counter64: 34717154487
.1.3.6.1.4.1.2603.1.2.1.1.1.6.2.0 = Counter64: 109839200694
.1.3.6.1.4.1.2603.1.2.1.1.1.6.3.0 = Counter64: 6244063
.1.3.6.1.4.1.2603.1.2.1.1.1.7.1.0 = Counter64: 20952
.1.3.6.1.4.1.2603.1.2.1.1.1.7.2.0 = Counter64: 66267
.1.3.6.1.4.1.2603.1.2.1.1.1.7.3.0 = Counter64: 24
.1.3.6.1.4.1.2603.1.2.1.1.1.8.1.0 = Counter64: 1695133
.1.3.6.1.4.1.2603.1.2.1.1.1.8.2.0 = Counter64: 4938721
.1.3.6.1.4.1.2603.1.2.1.1.1.8.3.0 = Counter64: 6162
.1.3.6.1.4.1.2603.1.2.1.1.1.9.1.0 = Counter64: 35627776
.1.3.6.1.4.1.2603.1.2.1.1.1.9.2.0 = Counter64: 101641327
.1.3.6.1.4.1.2603.1.2.1.1.1.9.3.0 = Counter64: 13126
.1.3.6.1.4.1.2603.1.2.1.1.1.10.1.0 = Counter64: 29968606
.1.3.6.1.4.1.2603.1.2.1.1.1.10.2.0 = Counter64: 88334597
.1.3.6.1.4.1.2603.1.2.1.1.1.10.3.0 = Counter64: 22760
.1.3.6.1.4.1.2603.1.2.1.1.1.11.1.0 = Counter64: 65596382
.1.3.6.1.4.1.2603.1.2.1.1.1.11.2.0 = Counter64: 189975924
.1.3.6.1.4.1.2603.1.2.1.1.1.11.3.0 = Counter64: 35886

My "basic" XML:

<interface>
<name>Get Allot Pipe information</name>
<description>Get SNMP based Pipe Information</description>
<index_order_type>numeric</index_order_type>
<oid_index>.1.3.6.1.4.1.2603.1.2.1.1.1.1</oid_index>

<fields>
<pipePosition>
<name>Index</name>
<method>walk</method>
<source>value</source>
<direction>input</direction>
<oid>.1.3.6.1.4.1.2603.1.2.1.1.1.1</oid>
</pipePosition>
</fields>
</interface>

My "verbose query output":
+ Running data query [10].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/servers/cacti/resource/snmp_queries/allot-pipe.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.2603.1.2.1.1.1.1'
+ Located input field 'pipePosition' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.2603.1.2.1.1.1.1'
+ Found item [pipePosition='1'] index: 0 [from value]
+ Found item [pipePosition='2'] index: 0 [from value]
+ Found item [pipePosition='3'] index: 0 [from value]
+ Found data query XML file at '/servers/cacti/resource/snmp_queries/allot-pipe.xml'
+ Found data query XML file at '/servers/cacti/resource/snmp_queries/allot-pipe.xml'
+ Found data query XML file at '/servers/cacti/resource/snmp_queries/allot-pipe.xml'

Now ... I guess those "index: 0 [from value]" aren't quite correct .. because I get "Success [1 Item, 1 Row]" and I guess I shoud be getting 3, right ?

I've tried changing the "<oid_index> and <oid> values to different ones ( basically "going up" on the MIB, removing "1"'s from the end) but no success...

Any hints ?

Regards,

Paulo Pinto

Allen K · Post by **Allen K** » Sat Feb 25, 2006 12:34 am

What hardware and software versions do you have for your NE, I run a 402 for a University Dorm network of 500 students (very interesting at times)
I am graphing a few things on it, current connections and the like, but have also had issues trying to graph VC's and pipes

Post by **gandalf** » Sat Feb 25, 2006 10:54 am

xeon wrote: And the snmpwalk output:
$> snmpwalk -c mypass -v 1 my.host.domain PIPE-MIB::pipeStatTable
.1.3.6.1.4.1.2603.1.2.1.1.1.1.1.0 = INTEGER: 1
.1.3.6.1.4.1.2603.1.2.1.1.1.1.2.0 = INTEGER: 2
.1.3.6.1.4.1.2603.1.2.1.1.1.1.3.0 = INTEGER: 3

Harm is done by the trailing .0 of each OID. I'm discussing this with the devs
Reinhard

xeon · Post by **xeon** » Mon Feb 27, 2006 10:47 am

lvm wrote:
xeon wrote: And the snmpwalk output:
$> snmpwalk -c mypass -v 1 my.host.domain PIPE-MIB::pipeStatTable
.1.3.6.1.4.1.2603.1.2.1.1.1.1.1.0 = INTEGER: 1
.1.3.6.1.4.1.2603.1.2.1.1.1.1.2.0 = INTEGER: 2
.1.3.6.1.4.1.2603.1.2.1.1.1.1.3.0 = INTEGER: 3
Harm is done by the trailing .0 of each OID. I'm discussing this with the devs
Reinhard

Hello !

So... have I stumble on a bug .. or there is any way around it ?

Regards,

Post by **gandalf** » Mon Feb 27, 2006 12:09 pm

AFAIK from the docs, this is not a supported feature; so no bug but perhaps an enhancement request. Let's wait for the devs to comment
Reinhard

Post by **rony** » Thu Mar 02, 2006 1:06 pm

Please do an snmpget on the following OIDs:

.1.3.6.1.4.1.2603.1.2.1.1.1.1.1
.1.3.6.1.4.1.2603.1.2.1.1.1.1.1.0

I want to see the results.

xeon · Post by **xeon** » Thu Mar 02, 2006 1:31 pm

Here goes:

$> snmpget -c mycommunity -v 1 host.dom.dom .1.3.6.1.4.1.2603.1.2.1.1.1.1.1
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-SMI::enterprises.2603.1.2.1.1.1.1.1

$> snmpget -c mycommunity -v 1 host.dom.dom .1.3.6.1.4.1.2603.1.2.1.1.1.1.1.0
SNMPv2-SMI::enterprises.2603.1.2.1.1.1.1.1.0 = INTEGER: 1

Regards,

xeon · Post by **xeon** » Mon Mar 06, 2006 11:04 am

*bump*

Post by **gandalf** » Wed Mar 08, 2006 2:40 pm

Sorry, I was blind. Please refer to SNMP Query XML Syntax and search for <oid_index_parse>.
Please add

Code: Select all

<oid_index_parse>OID/REGEXP:.*\.2603\.1\.2\.1\.1\.1([0-9]*\.0)$</oid_index_parse>

to your XML file just after

Code: Select all

 <oid_index>.1.3.6.1.4.1.2603.1.2.1.1.1</oid_index>

. This should result in indices like
1.0
2.0
3.0
These indices will now be appended to the OIDs given in the fields description. If in doubt, please post your XML file and a Verbose Query Output for more help
Reinhard

xeon · Post by **xeon** » Thu Mar 09, 2006 7:20 am

lvm wrote:Sorry, I was blind. Please refer to SNMP Query XML Syntax and search for <oid_index_parse>.
Please add
Code: Select all
<oid_index_parse>OID/REGEXP:.*\.2603\.1\.2\.1\.1\.1([0-9]*\.0)$</oid_index_parse>
to your XML file just after
Code: Select all
 <oid_index>.1.3.6.1.4.1.2603.1.2.1.1.1</oid_index>
. This should result in indices like
1.0
2.0
3.0
These indices will now be appended to the OIDs given in the fields description. If in doubt, please post your XML file and a Verbose Query Output for more help
Reinhard

Hello !

Now I'm getting somewhere

BTW, your regex isn't correct, as it returns the full OID as the index.
The correct one should be: <oid_index_parse>OID/REGEXP:.*\.([0-9]{1,3}\.[0-9]{1,3})$</oid_index_parse>

I'll get back here to post the results (as there seems to be other people trying to graph their Allots )

Thank you very much

Regards,

xeon · Post by **xeon** » Thu Mar 09, 2006 12:12 pm

Well... I think I got it running.

Here are the 2 xml files I'm using for the allot.

Corrections/additions are welcome.

Regards,

Post by **gandalf** » Thu Mar 09, 2006 3:34 pm

xeon wrote:BTW, your regex isn't correct, as it returns the full OID as the index.
The correct one should be: <oid_index_parse>OID/REGEXP:.*\.([0-9]{1,3}\.[0-9]{1,3})$</oid_index_parse>

Thank you for the correction. Would it be an option to post a screenshot of the graphs?
Reinhard
btw
Moving this to Scripts and Templates

Teecee · Post by **Teecee** » Fri Mar 10, 2006 4:26 pm

I have a netenforcer and I am going to try this out and let you know how it works. I would LOVE cacti to report info from the netenforcer.

Teecee · Post by **Teecee** » Mon Mar 13, 2006 1:11 pm

I cannot import the XML templates.

krap_rz · Post by **krap_rz** » Thu Jun 01, 2006 12:31 am

xeon wrote:Well... I think I got it running.

Here are the 2 xml files I'm using for the allot.

Corrections/additions are welcome.

Regards,

Thanks xeon for making allot working here. I am very new to cacti so can you help me on step by step installing and making xml work? Pleaaaeesssee?

Cacti

Allot Netenforcer

Allot Netenforcer

Re: Allot Netenforcer

Re: Allot Netenforcer

Installation Process

Who is online