So the new version of the sflowtools from inmon is now fixed for
Opterons. I tried (shot in the dark) to see if the same thing would
work for the sflowplugin.c file (change the "u_long" with "u_int32_t")
and it does make the plugin work for a little bit, but now it
segfaults. So obviously there is more that needs to be done besides
just that.
Help
Bret
Bret Jordan wrote:
I got this information from InMon on their Sflow tools. So do we
need to do the same thing for the Sflow plugin for Ntop??
Bret
-- Begin message --
I compiled it on an Opteron here and got the same problem. It turns
out that sizeof(u_long) is 8 bytes on this platform instead of 4, so
the fix is to edit sflowtool.c and replace all occurrences of "u_long"
with "u_int32_t" and then run "make" and "make install" again. I'll
post the new sources later today.
-- End Message --
Bret Jordan wrote:
Okay I have some more information... On a Dual Intel Xeon box RH9.0
this works fine. But on a Dual AMD Opteron box SuSE9.1 this does not
work. Has anyone seen any problems with a 2.6.x kernel and this? Or
is this an Opteron issue or just a SuSE issue?
Thanks
Bret
Bret Jordan wrote:
I am trying to use NTOP with my Foundry BigIron. But it is not
working as I would expect. As I mentioned earlier, I have turned on
the Sflow plugin and set the port and such. When I turn on
debugging I get the following in my logs.
I have started ntop with: ./ntop -w 3000 --ipv4 -m 155.98.0.0/20
--skip-version-check
Tue Jul 13 15:35:48 2004 SFLOW_DEBUG: rawSampleLen: 184
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: startDatagram
=================================
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: datagramSourceIP 155.98.0.1
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: datagramSize 404
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: unixSecondsUTC 1089754550
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: datagramVersion 2
Tue Jul 13 15:35:50 2004 **WARNING** SFLOW: currently only support
INMADDRESSTYPE_IP_V4 as the agent IP address type (source IP =
155.98.0.1) 00-00-00-02-00-00-00-01-9B-62-00-01-00-00-58-10-<*>-48
BC-C2-10-00-00-00-02-00-00-00-01-00-00-09-30-00
00-00-07-00-00-08-00-00-5F-60-00-00-00-00-00-00
00-00-07-00-00-00-08-00-00-00-01-00-00-00-01-00
00-01-FB-00-00-00-80-00-D0-FF-EE-18-00-00-01-02
77-4F-92-08-00-45-00-01-ED-68-02-40-00-80-06-FD
FF-9B-62-00-0C-80-6E-77-2C-00-50-0B-FD-39-FA-D4
7E-02-53-0D-66-50-18-FF-FF-22-65-00-00-48-54-54
50-2F-31-2E-31-20-33-30-32-20-46-6F-75-6E-64-0D
0A-44-61-74-65-3A-20-54-75-65-2C-20-31-33-20-4A
75-6C-20-32-30-30-34-20-32-31-3A-34-33-3A-34-36
20-47-4D-54-0D-0A-53-65-72-76-65-72-3A-20-41-70
61-63-68-65-0D-0A-4C-00-00-00-02-00-00-00-01-00
00-00-64-00-00-00-00-00-00-00-01-00-00-00-00-00
00-00-02-00-00-00-01-9B-62-7F-35-00-00-00-00-00
00-00-00-00-00-00-02-00-00-0C-DF-00-00-00-07-00
00-00-14-00-00-00-02-00-00-00-07-00-00-00-06-00
00-00-00-3B-9A-CA-00-00-00-00-01-00-00-00-03-00
00-00-04-
Tue Jul 13 15:35:50 2004 SFLOW_DEBUG: rawSampleLen: 404
The only place that NTOP reports anything about my SFLOW session is
Summary->Netflows. Please help..
BTW, when I run the Sflow tools from InMon on the Linux box that is
acting as the collector I see:
startDatagram =================================
datagramSourceIP 155.98.0.1
datagramSize 244
unixSecondsUTC 1089754402
datagramVersion 2
agent 48ba:7ff0:0000:0001:0000:0001:0000:1729
packetSequenceNo 8
sysUpTime 1
samplesInPacket 1434
startSample ----------------------
sampleType_tag 526:110
unexpected sample type (source IP = 155.98.0.1)
00-00-00-02-00-00-00-01-9B-62-00-01-00-00-57-D6-48
BA-7F-F0-00-00-00-01-00-00-00-01-00-00-17-29-00
00-00-08-00-00-08-00-01-83-F0-00-00-00-00-00-00
00-00-08-00-00-00-46-00-00-00-01-00-00-00-01-00
00-05-9A-00-00-00-80-00-20-E0-6E-CF-A9-00-D0-<*>-FF
EE-18-00-08-00-45-00-05-8C-0A-14-40-00-70-06-30
D0-D0-FE-4F-14-80-6E-2A-07-00-50-10-C5-08-A7-64
5A-02-34-EE-A2-50-10-FF-FF-30-AB-00-00-3A-1D-80
3E-C7-08-C3-89-21-B6-1A-54-9F-93-38-1A-BF-EB-F0
AA-BB-8E-86-BD-81-8C-B9-01-59-9A-8B-03-F2-0D-45
8E-98-DD-EF-B7-68-FD-5D-EC-38-E1-F1-9C-8A-CC-31
FD-D6-FB-DD-F1-0C-4C-00-D3-9D-00-A0-87-C4-1E-99
CB-F3-F5-E3-7A-DC-1D-00-00-00-02-00-00-00-01-00
00-00-01-00-00-00-00-00-00-02-15-00-00-00-00-00
00-00-02-00-00-00-01-00-00-00-00-00-00-00-00-00
00-00-00
caught exception: 2
endDatagram =================================
Thanks in advnace for your help.
Bret
Luca Deri wrote:
Bret Jordan wrote:
Is anyone using NTOP as a SFLOW collector? If so can I ask you
some questions?
Thanks
Bret
Bret,
please ask.
Cheers, Luca
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Bret Jordan Dean's Office
Director of Networking College of Engineering
801.585.3765 University of Utah
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
