[rtg] Fwd: Results with RTG

[Harry Marcson]

>
> Also, so you sent that reply directly to me, and not the list. You might
> want to send it again ;)
>
> Jacob


OOPS...... :)

Thanks everyone for the responses so far! I

@ Matt S.

RTG::Report looks neat! Especially the record_consolidator. I am no perl
programmer, but does the targetmaker pick the port description too? It seems
the only way to match the interface id with the actual switch port.

Is netflow actually more accurate? Our cisco gear does support netflow, but
we have never tested it, I could not find an opensource solution to try, but
will do some more searching.

@ John S.

How does your cronjob look like? Are sending a HUP signal like: kill -HUP
... ?

@ Jacob S.

I have discussed this with our programmer and the plan would be as follow:
- Every time a switch is added to our system, an additional write to a text
file (example: router.add) somwewhere on the server is stored which mentions
the new ip. Incase of a switch is removed, the same thing is done, but to a
different file, like router.rm.
- A cronjob is ran every 3hours or so, checking the content of both files
(router.add and router.rm). Incase of content, the RTG router file is
changed accordingly. Once done, the two files are emptied.
- Once the above step is performed (with or without changes to the files),
the targetmaker is ran and RTG is restarted.

3. I am going to give the new rtgplot a try, hopefully it corrects at least
the issue with the continued high peek, despite a server being down. It will
affect credibility if a customer would think that we would bill non-existing
bandwidth usage.

4. The interface id is an incremental value. If you use port 7 first on a
particular switch, it is given the lowest interface id value. This makes the
interface id useless for matching the correct port id from RTG with the port
id from the switch (in our system). The description seems to mention the
actual port id however, so I guess that would be the only way to do the
correct matching.

See attachement:
interface id 1 is actually port 7
interface id 2 is actually port 9
etc.

Best regards,

Harry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.grdata.com/pipermail/rtg/attachments/20090309/9185226f/attachment.htm>