Ez Cacti Setup V1.1 PDF

EZCACTI SETUP V1.
1
Eur-Ing David Shephard CEng MIET CCDP® CCNP® CCIP®
Global Domain Expert, Networks and Infrastructure
16 DEC 2016 (V1.0 was 05FEB2015)
This document is available from:

http://avid.force.com/pkb/articles/en_US/Compatibility/en24419
Intended audience: General distribution
Centre of Excellence
Abstract
This document outlines the fundamental requirements to Deploy EZCACTI in a
VIRTUALBOX VM. This is a ZERO cost solution.
© Avid Technology (Europe) ltd. This document is the property of Avid. The information contained in this document has been provided to
the intended recipients for evaluation purposes only. The information contained in this document should not be discussed with any other
party or persons without the express prior written permission of Avid. If the intended recipient does not accept these terms, this document
and any copies should be returned to the nearest Avid office. If you are not the intended recipient, employee or agent you are hereby
notified that any dissemination or copying of this document is strictly prohibited. If you have received this document in error, please return
it to the nearest Avid Technology office ( www.avid.com ).
EZ_CACTI_SETUP_V1.1.docx Page 1 of 128

Table of Contents
ABSTRACT .......................................................................................................................................................... 1
Revision history ............................................................................................................................................. 3
1.0 BASIC REQUIREMENTS ............................................................................................................................ 4
1.1 HARDWARE PLATFORM ................................................................................................................................ 4
1.2 VM HOST ..................................................................................................................................................... 5
1.3 EZ CACTI - DOWNLOAD .............................................................................................................................. 6
1.4 BROWSER ACCESS ........................................................................................................................................ 6
2.0 INSTALLATION OF ELEMENTS .............................................................................................................. 9
2.1 HOW TO INSTALL VM VIRTUALIZATION APPLICATION. ................................................................................. 9
2.2 HOW TO INSTALL APPLICATION ..................................................................................................................... 9
2.2.1 Static IP Address steps ....................................................................................................................... 10
2.3 EXTRA NECESSARY TOOLS ....................................................................................................................... 12
2.3.1 SSH client ........................................................................................................................................... 12
2.3.2 NANO Editor ...................................................................................................................................... 12
2.3.3 System time ......................................................................................................................................... 13
2.3.4 Shutdown and restart ......................................................................................................................... 13
2.3.4 Restart a service ................................................................................................................................. 13
2.3.6 SYSLOG Generator ............................................................................................................................ 13
2.3.6 Alternative SYSLOG Viewer............................................................................................................... 14
3.0 CONFIGURATION ..................................................................................................................................... 15
3.1 INITIAL SETUP ........................................................................................................................................ 15
3.1.2 Changing Title length in Graphs ........................................................................................................ 17
3.2 SETUP GRAPH TREES .................................................................................................................................. 19
3.2.1 setting a graph tree step-by step ........................................................................................................ 20
3.2.2 Setting a graph tree the quick way ..................................................................................................... 24
3.3 CONFIGURE A DEVICE ................................................................................................................................. 24
3.4 CONFIGURE DEVICE PRE-REQUISITES .......................................................................................................... 27
3.5 CONFIGURE DEVICE AND GRAPHS FOR A C4900M ...................................................................................... 31
3.5.1 Basic graphs and first steps ............................................................................................................... 31
3.5.2 Creating detailed data sources for graph sets. .................................................................................. 36
3.5.3 Creating graph sets from data sources. ............................................................................................. 44
3.6. CONFIGURE DEVICE AND GRAPHS FOR A C4948 ......................................................................................... 55
3.7. CONFIGURE DEVICE AND GRAPHS FOR A C4500-X ..................................................................................... 85
3.8. GRAPHS CREATION – THE QUICK WAY! .................................................................................................. 108
3.8.1 Viewing interfaces . .......................................................................................................................... 109
3.9. CONFIGURE DEVICE AND GRAPHS FOR A WINDOWS SERVER .................................................................... 112
3.10. CONFIGURE LOGGING SERVER............................................................................................................... 112
3.10.1 Cisco Switch Essential Logging Commands .................................................................................. 112
3.10.2 Cisco Switch Optional Logging Commands ................................................................................... 112
3.10.3 Configuring Centos Firewall ......................................................................................................... 113
3.10.4 Configuring and Viewing in CACTI ............................................................................................... 114
3.11 USING CACTI WITH DELL FORCE 10 DEVICES .................................................................................. 116
3.11.1 Importing and DELL/F10 MIB ...................................................................................................... 116
3.11.2 FORCE 10 Templates .................................................................................................................... 117

4.0 ADDITIONAL FUNCTIONS .................................................................................................................... 118
4.1 LOCATING CACTI FILES AND DISK USAGE................................................................................................ 118
4.1.1 Disk Free and Disk Utilization......................................................................................................... 118
4.1.2 Adding MIB files to CACTI .............................................................................................................. 119
4.1.3 Creating a Viewer account ............................................................................................................... 120
4.1.4 Downloading NANO as an RPM ...................................................................................................... 122
4.1.5 Using WINSCP ................................................................................................................................. 123
4.1.9 DATA storage ................................................................................................................................... 124
4.2 ADDING INTERFACE DESCRIPTIONS TO GRAPHS ........................................................................................ 124
5.0 FUTURE SECTIONS FOR NEXT VERSION ........................................................................................ 128
Revision history
Version Name Date Comment
D.Shephard
Version 1.0 D.SHEPHARD 06 FEB 2015 First release
V1.1 D.SHEPHARD 16 DEC 2016
Add3.1.2 Changing Title length in Graphs
Add 3.11 Using CACTI with DELL
FORCE 10 Devices
Add 4.0 Additional functions

1.0 Basic Requirements
Monitoring of Cisco network Switches and Windows servers which are part of an Avid
solution is often overlooked, and hence valuable historic information is lost which could be
of great benefit when diagnosing a system problem. This is often due to cost, or perceived
cost. The solution described in this document is a zero cost solution, in terms of software and
hardware, as and existing hardware platform can be leveraged.
CACTI is an open-source SNMP solution, which has excellent support for Cisco switches
and Windows servers. There are several other open-source SNMP products.
In this initial document version does not consider loading MIB information for other vendor
switches.
In some cases the compiled (open-source) software can be found for Linux, Unix and
Windows, however, as with many open-source solutions the installation can be quite
complex. The chosen solution eliminates most of the initial setup variables leaving the
administrator with just the setup of the devices to be monitored.
The basic elements are described in a little more detail below, but can be summarized as:
1. 64 bit VM hosting application
2. One static IP address
3. The application software
1.1 Hardware Platform

The first task is to identify a 64-bit capable hardware platform that has available resources.
This might be a device in which is part of the Avid systems but has low utilization such as a
General Purpose Server, or legacy workstation or server which is no longer used.
Suitable devices might be a Z800/400/200, or XW8600 workstation, an Intel SR2500 or

AS3000 server running Windows 7x64 or Windows Server 2008, or a Apple MAC PRO
running 10.8.x or higher.
The testing for this document has in fact been executed on a MAC PRO running OSX 10.9.2
Mavericks.
Note: BEWARE of some silly issues with Virtual Box 4.3 for windows not
running as 64 bit due to BISO settings. Maybe go back to use V-Box 4.2.x
https://forums.virtualbox.org/viewtopic.php?f=6&t=57871
How to enable virtualization support on HP Z820 Workstation
http://h30499.www3.hp.com/t5/Workstations-z-series-xw-series/How-to-
enable-virtualization-support-on-HP-Z820-Workstation/td-
p/5719065#.VXATr2RVhBc

1.2 VM Host
VirtualBox from Oracle is the suggested virtualization solution.
VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise

as well as home use. Not only is VirtualBox an extremely feature rich, high
performance product for enterprise customers, it is also the only professional solution
that is freely available as Open Source Software under the terms of the GNU General
Public License (GPL) version 2. See "About VirtualBox" for an introduction.
Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and
supports a large number of guest operating systems including but not limited to
Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8),
DOS/Windows 3.x, Linux (2.4, 2.6 and 3.x), Solaris and OpenSolaris, OS/2, and
OpenBSD.
https://www.virtualbox.org/wiki/Downloads
This EZCACTI solution needs a single CPU and just 20GB of (virtual) disk.

1.3 EZ CACTI - Download
This pre-packaged solution will install itself into the VM.
http://cactiez.cactiusers.org/docs/installation.html
EASY CACTI useful URLs
http://blog.cactiusers.org/2012/10/14/cactiez-0-7-released/
http://community.spiceworks.com/how_to/show/2391-easy-cacti-with-cactiez
http://pathandy.com/cactiez/92-how-to-install-ezcacti
1.4 Browser Access Centre of Excellence

This CACTI solution used a Web browser for all communication. The colors will differ
between browsers and this can make operation harder as can be seen in the screenshots
below, The ADD and NEXT/PREVIOUS “buttons” are much more difficult to see in Safari
than in Chrome.

CACTI using Safari
CACTI using Google Chrome
CACTI using IE8 on WIN XP 32

CACTI using FF33 on WIN XP 32
ADD EXAMPLES FROM WIN7 IE11

2.0 Installation of Elements
Some articles have been written and are freely available on the Internet, so there is little to be
gained from making new ones here.
Key first steps before beginning the installation are:
Decide on a root password for the Centos based system, this must be AT LEAST 6
characters, but a short password will be highlighted as insecure and not advisable, but will be
accepted.
Decide on a Cacti password, this can be the same as the root password above if it is desired to
keep things simple. The SNMP system does not contain sensitive data so high security may
not be necessary, however it may be necessary to consider site policies for password
administration. In first access to Cacti you will be force to change from admin/admin
Decide on a Static IP address and default gateway. Full DNS identification is not required
but may be desirable.
Obtain the details of the DNS server or servers, which will be required for a STATIC IP
install and when setting up CACTI at first login
2.1 How to install VM virtualization application.

This is covered by the Virtual box website and will vary by host O/S
https://www.virtualbox.org/wiki/Downloads
2.2 How to install application
The URL below provides an in depth description on how to do this for a DYNAMIC IP
address. The steps for using a static IP address differ very slightly and are detail in section
2.2.1
MAKE SURE BEFORE YOU START VM THAT TOU MAKE ADAPTER INTEL, and
BRIDGED (it should automatically map to eth0) AND WITH custom mac address like
0800aabbccdd

http://pathandy.com/cactiez/92-how-to-install-ezcacti
2.2.1 Static IP Address steps

The addition screen shots that will be seen are:

THERE MUST BE NO SPACES
also make sure that before a reboot after installing the basic EZ CACTI that you disconnect
the ISO form the “CD” drive

2.3 Extra Necessary TOOLS
The It will be necessary to obtain a few tools and add some to the implementation, these are
described below.
2.3.1 SSH client

Having access to the CLI using a SSH client is a MUST-HAVE. Applications such as
PUTTY (Windows) or iTERM2 (MAC OSX), that are both freeware, or a multitude of other
solutions for various operating system versions will be suitable.
http://en.wikipedia.org/wiki/Comparison_of_SSH_clients
2.3.2 NANO Editor

It will be necessary to edit some files within Centos, and Linux built in tools are fearsome
beasts.
The nano editor is very easy to use and install
yum install nano

CENTSO INSTALL NANO
https://fuzzyhosts.com/account/knowledgebase.php?action=displayarticle&id=71
2.3.3 System time

Accurate time on your CACTI systesm is also a MUST-HAVE. Details below of various
solutions.
http://serverfault.com/questions/368602/how-do-i-update-a-centos-servers-time-from-an-
authoritative-time-server
Try /sbin/service ntpd stop,

followed by ntpdate time.apple.com
and then /sbin/service ntpd start
yum install ntp
chkconfig ntpd on
ntpdate pool.ntp.org
service ntpd start
2.3.4 Shutdown and restart

In most cases services can be restarted but if needed, the command below can be issued at the
CLI
SHUTDOWN
/sbin/shutdown -h now
RESTART
/sbin/shutdown -r now
**** CENTOS SHUTDOWN

https://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-boot-init-shutdown-
shutdown.html
2.3.4 Restart a service

It is unlikely that services will need to be stopper or started but if it does the command type
below is used
service rsyslog stop
service rsyslog start
2.3.6 SYSLOG Generator

If using CACTI for syslog it will be handy to test with a message generator. The KIWI
SYSLOG GENERATOR is a great free tool for Windows. It gives some “funky” hostnames

in Select Hosts window of CACTI, based on message string, which cannot be deleted so used
this tool sparingly.
http://www.kiwisyslog.com/downloads.aspx
Of course Google can provide many options depending on host O/S demands
2.3.6 Alternative SYSLOG Viewer

It if using CACTI you do not want to use CACTI as a syslog viewer The KIWIW SYSLOG
daemon is a nice free tool, However, now that SOLARWINDS own KIWI SYSLOG version
9.x free versions only supports up to data form 5 hosts. If one can obtain version 8.3.x this is
not limited, but does not save its file to disk, hence data does not persist through a reboot.
http://www.kiwisyslog.com/downloads.aspx

3.0 Configuration
As for the installation, some articles have been written and are freely available on the
Internet. The URL below provides a good introduction but each solution will vary slightly.
http://pathandy.com/cactiez/93-setting-up-cactiez
One key required element is that the Cisco Switch must be configured with an SNMP
community to allow the READ ONLY access from CACTI. One simple Cisco CLI
command as shown below will permit an SNMP device using the community name aviddiva
to interrogate the Cisco switch for information.
snmp-server community aviddiva RO
3.1 INITIAL SETUP
Things that will be needed in advance are the detail of Primary and Secondary DNS server.
Also the settings can be changed later if you don’t know or get them wrong.
FIRST PLUG-Ins
Setup all the plugins you think you will use. If you don't know what the plugin means, the
chances are, it is not required for your needs. I consider that this is not a large site
implementation do have not loaded BOOST – LARGE SITE PERFROMANCE BOOSTER
in the screenshot below.

Then it is optional templates, as we are not monitoring Barrcuda Firewall queues or
VMWARE or WEBSITES so they can be delisted

Next DNS settings, not REALLY REQUIRED if you will be monitoring using the
IPADDRESS only on a small systems, and some settings might get inherited by the earlier
(DHCP) configuration, others might not be parsed from OS to CACTI application.
AFTER PRESSING SAVE >>> Onto graph trees
3.1.2 Changing Title length in Graphs

The various vendor switches will report their interfaced designation differently.

For example Cisco will report the interface names as Te1/8 while F10 will provide
TenGigabitEthernet 0/25 this has an impact on how the graphs will be represented
Console -> Configuration | Settings | Visual
Maximum Title Length

The maximum number of characters to display for a data source title.
This parameter needs to have the value increased from 45 to 60 to cope with the longer
names, also this will help with interface descriptions. It is also worth increasing
Maximum Title Length from 80 to 100

The maximum number of characters to display for a graph title.
Maximum Field Length from 15 to 30
The maximum number of characters to display for a data query field.
This change should be performed early on because it does not get applied retrospectively
DEFAULT INSTALL
Adjusted INSTALL

3.2 Setup Graph Trees
Even before setting up devices is it very beneficial to think of what you will want to show in
the graphs. Using the default tree is not a scalable option and it VERY RAPIDLY becomes
unmanageable.
Graph trees can have multiple levels. The depth depends on the quantity and complexity of
the elements for be monitored. Hence it might be:
1. Geographic, e.g. LONDON, PARIS, NEW YORK, with sublevels for devices or
departments
2. Departmental, with sub levels for devices
3. Device based with sublevels for graph type, which is the basis of the screenshot
below.
The device type will define what levels are appropriate. For a network switch
The screenshot below shows the default allocation of a single level tree.
The platform shown above is for a WIN XP 32 based Intel SR2500 server, it shows the
availability of CPU utilization for each core, and drive space. The OS version and the setup
of the local SNMP agent will define what data sources are presented to the SNMP
application.
The screenshot below shows a C4948-10GE (the older GREEN device with two X2
interfaces) with primary CPU & Uplink information on the first level, and secondary levels
containing details on all interface ports.

The screenshot below shows a geographical with a secondary tree level for primary CPU
information on the first level, and tertiary levels containing details on all interface ports.
3.2.1 setting a graph tree step-by step
This is the starting point. If using SAFARI the ADD button will be well hidden as black text
on dark blue banner!!!
SO CLICK ON ADD for next screen, adding the TREE NAME and press CREATE.

Manual ordering is fine for the top level, but natural ordering is probably better for the sub
trees, interfaces can be moved (up or down) but it is a laborious and repetitive process.
Now to add some sub trees. The things we need to monitor are link speed and errors, I like to
see link speed and bits per second and bytes per seconds, so that will mean three sub –trees of
BITS/SEC
BYTES/SEC
ERRORS
I might decide to add some key interfaces to the main screen too.
So press ADD on the screen above and enter BITS/SEC in the title field;
Select Natural Ordering
Press CREATE
Voila, ready for the next one

So press ADD on the screen above and enter BYTES/ SEC in the title field;
Press CREATE
And now for Errors
So press ADD on the screen above and enter ERRORS in the title field;
Press CREATE

And now press SAVE
If we go back to GRAPH TREES w now see the new tree
As can be seen the RED X will allow a whole tree to be deleted
The process cab be repeated for different switches, if that is the top-level tree item we want<
However the sun trees can also themselves have sub trees
So for example if we have a system with two Core C4500-X switches and four C4948E
switches we might have tree names of:
AVID C4500X-CORE01
AVID C4500X-CORE02
AVID C4948E-ACCESS01
AVID C4948E-EDGE03
AVID C4948E-EDGE04
Or maybe the tree names will use the switches hostname based on rack position and floor
location.
TVC1CORE01R1P4F3
TVC1CORE02R2P4F3
TVC1ACCE01R1P6F3
TVC1ACCE02R2P6F3
TVC1EDGE03R1P4F6
TVC1EDGE04R1P9F7

3.2.2 Setting a graph tree the quick way
The sections below show the long and structured way of doing graphs. But the faster way can
also be used, but you then have to search for the interfaces of interest rather than having them
presented in a predetermined orderly fashion. The quick way is covered in section 3.8.
3.3 Configure a device

Before a device can be monitored it must be created. From Console|Devices choose <ADD>
The form below is presented:

Enter appropriate details, and press <CREATE>.
Screen shots below show and example for a Cisco Switch and example for a Windows server.
Make sure to use SNMP V2, otherwise it is not possible to use 64 bit counters which are
necessary for 10G interfaces (and beneficial for 1G interfaces)


3.4 Configure device Pre-requisites
One key required element is that the Cisco Switch must be configured with an SNMP
community to allow the READ ONLY access from CACTI. One simple Cisco CLI
command as shown below will permit an SNMP device using the community name aviddiva
to interrogate the Cisco switch for information.
snmp-server community aviddiva RO
Also may need the snmp server user to be set up
snmp-server user avidtech aviddiva v1

snmp-server user avidtech aviddiva v2c
Servers and workstations also need to be configured, and below are various URL that will
help with the necessary tasks.
HOW TO: Configure the Simple Network Management Protocol (SNMP) Service in
Windows Server 2003
http://support.microsoft.com/kb/324263

This article can also be used for Windows XP.
Other useful articles for SNMP Agent Installation and Configuration:
SNMP Agent Installation (for Windows and Solaris)

http://www.manageengine.com/products/applications_manager/help/appendix/snmp-agent-
discovery.html
SNMP Agent Configuration (for Windows and Solaris)

http://www.manageengine.com/products/applications_manager/help/appendix/snmp-agent-
configuration.html#windows-2000
YOUTUBE: How to install and configure SNMP in windows 7

http://www.youtube.com/watch?v=3xRh1K-kd7Y
Below is EXTRACT FROM:
http://www.schneider-
electric.us/sites/us/en/support/faq/faq_main.page?page=content&country=ITB&lang=en&id=
FA159596&locale=en_US&redirect=true
Solution:
1. In Windows XP and Windows 2003 click Start button, then go to Control Panel and
run Add or Remove Programs. In the Add or Remove Programs window,
click Add/Remove Windows Components to open Windows Components wizard. In
Windows 7 or Vista, click Start button, then go to Control Panel. Click on
Programs And Features link and then click on Turn Windows features on or off. If
you’re prompted with User Account Control dialog, click “Continue”.
2. In Components of Windows XP and 2003, click on the Management and
Monitoring Tools (make sure that you do not select or clear, tick or untick its check
box to change the existing selection), and then click Details. In Windows 7 or Vista,
locate Simple Network Management Protocol (SNMP).
3. Select and tick the check box of Simple Network Management Protocol or SNMP
feature.
4. Click OK. Also click Next if you’re in Windows XP or 2003. SNMP service will be
installed on the system. You may require inserting the Windows setup CD/DVD disc
into optical drive.
5. SNMP will start automatically after installation. But it’s recommended to verify the
service status from Services in Control Panel, and if it’s stopped, you can start the
SNMP service from there. Two new services will be created:
SNMP Service which is the main engine with agents that monitor the activity in the
network devices and report the information to the monitoring console workstation.
SNMP Trap Service which receives trap messages generated by local or remote
SNMP agents and forwards the messages to SNMP management programs running on this
computer.

Windows doesn't assign any community string to the SNMP service by default, and also only
allow access from localhost or local devices. Further configuration is needed to add in desired
community string, which act as the password to grant reply to any SNMP request from
remote system.
1. Go to Control Panel->Administration Tools->Services->SNMP service. The following

screen will appear. The startup type should be set to automatic.
2. Click on the Agent tab, make sure all service boxes are checked, enter any relevant contact
information and location information here:
3. Click on the security tab, enter the appropriate read, and read-write community names to
the accepted community names list. In the lower box, click ""Accept SNMP packets from
these hosts"" and click the add button. The IP Address or Host Name of the ISX Central(or

other NMS) should be entered. This will enhance security allowing only ISX Central or
another NMS to access information via SNMP.
4. Click the Traps tab, and you can create your own trap community name and manually enter
the IP Address of NMS as a trap destination.

5.) Click ""Apply"". Following these configuration changes, it is best practice to verify the
functionality of the software SNMP agent using a SNMP utility or network management
system. Using an NMS or SNMP utility, query the OID .iso.org.dod.internet.mgmt.mib-
2.system.sysDescr (.1.3.6.1.2.1.1.1) to verify the system description (note: this is a standard
MIB-2 OID, no other MIB is required). The return string for a Intel/Microsoft SNMP agent
should be something similar to: ""Hardware: x86 Family 6 Model 7 Stepping 3 AT/AT
COMPATIBLE - Software: Windows 2000 Version 5.0 (Build 2195 Uniprocessor Free)"".
3.5 Configure device and graphs for a C4900M

There are two steps to creating graphs. Basic graphs get “presented” elements, and detailed
graphs need the Administrator to create the sources.
3.5.1 Basic graphs and first steps
The first time you select data sources, data for all sources is shown, so this needs to be
narrowed down. Also when narrowed down it will appear not much data is available, but
there are a few further steps needed, to get the detailed information. For now we will just put

primary information at the top of the graph tree. Remember that any counter you choose
should be 64BIT otherwise data will be “lost” when counter rolls over.
In the host DROP DOWN select the C4900M
Information on the VLANS is pretty irrelevant, and G3/20 on this config is a routed link. In
fact the interfaces being offered here are all Layer 3 interfaces.

I will just choose the CPU and MEMORY information to go at top of graph tree, so click in
the tick box, set CHOOSE AN ACTION to Enable and click go, and then CONTINUE
Now go to GRAPH MANAGEMENT and select the host C4900M
Select CPU USAGE, FREE MEMORY and PROCMEM USAGE, in <Choose and action>
select the graph template you want (in this case C4900M example) and press <GO>

The select destination branch I want to put these on the ROOT of this graph tree
press <CONTINUE>
then Click on the graphs TAB, select C4900M and we have our first graphs, with not much
data, because data sources are “new”.
Even if graphs are not placed on pages the data source is collected, and summarized
depending on the time that data has been collected for. So a graph create for a source which
has been collecting for 1 months will have a lots of data.

Click on a graph and you will get data for Daily (5 Minute Average), Weekly (30 Minute
Average), Monthly (2 Hour Average) and Yearly (1 Day Average). Obviously no data here
but it will collect over time. These collated average are available for EVERY GRAPH you
decide to plot.

NO data collected Here is one that has been collected for two
months
INTERFACE EXAMPLE #1 INTERFACE EXAMPLE #2
3.5.2 Creating detailed data sources for graph sets.

This is a more laborious process, and repetitive too, but it is the fundamental purpose for this
document. Each switch is a little different and will list its interfaces differently.
If we have setup graph trees as mentioned above we will want to plot BITS/SEC,
BYTES/SEC and ERRORS. It is a key point to remember that we want 64 bit counters, and
will plot the information of branches of the desired root tree. The bit depth of 32 bit counters
is insufficient for 10Gbps interfaces.

Select the CONSOLE tab, click on MANAGEMENT | DATA SOURCES | DEVICES and
select the desired device from the available sources. Then select CREATE GRAPHS (YES
!!!)

Tick the box at the top to select all interfaces and then un-tick the interfaces you do not want.
MAKE SURE you select 64 bit counters BITS this time.

Press <CREATE>, then after graphs are created press <NEXT>. Notice we cannot create
graph for G3/20 on this switch, as it is a layer 3 interfaces an already created (auto-
magically).
Next to the graphs for BYTES/SEC, Press <PREVIOUS> to get back to first interfaces.


Next to the graphs for ERRORS, press <PREVIOUS> to get back to first interfaces. Centre of Excellence



3.5.3 Creating graph sets from data sources.
This as can be seen there are now lots more data sources associated with this switch. It has
increased from 8 to 132.
This screen will allow us to delete, disable, create thresholds from the data, but we do not
need to do any of this for the basic graphing.
click on GRAPH management, the screen looks very similar

3.5.3.1 BITS/SEC GRAPHS
The data set is shown in an illogical semi-random order so it is best to select the graph
template at the top. I will select BITS/SEC as I will first populate the BITS/SEC branch of
my graph tree.

The screen below shows the selection of all the interfaces and the setting of the destination
trees as C4900M EXAMPLE
NOW press <GO>

SELECT BITS/SEC and then press <CONTINUE>
Now press <NEXT>, select the interfaces that you want to graph, and also the tree destination
and press <GO>

Select the BITS/SEC branch and press <CONTINUE>
3.5.3.2 BYTES/SEC GRAPHS

After the SAVE SUCESSFUL, select <PREVIOUS> and then from the drop TEMPLATE
selection BYTES/SEC

Select desired interfaces, PLACE on desired tree of C4900M, and press <GO>
SELECT BYTES/SEC branch and press <CONTINUE>
Select NEXT for additional interfaces, use tick boxes to choose interfaces to graph, and press
<GO>

SELECT BYTES/SEC branch and press ,CONTINUE
3.5.3.3 ERRORS AND DISCARDS GRAPHS

After the SAVE SUCESSFUL, select <PREVIOUS> and then from tike drop TEMPLATE
selection ERRORS
Select the desired interfaces.

Select the ERRORS branch
And press <CONTINUE>
Select <NEXT> for additional interfaces, use tick boxes to choose interfaces to graph, and
press <GO>

3.5.3.4 VIEWING GRAPHS
After all the config is done selected graphs tab.
Select BITS/SEC or other branch
Page of day up to 100 deep can be created, and data on this page can be shown by preset or
custom time intervals.

decide to plot.

Thumbnails will double up on the graphs per page

3.6. Configure device and graphs for a C4948
Configure Graph trees is the first step this may already have been done as per the example
above in section 3.2.1 above but it will be repeated here.
There are two steps to creating graphs. Basic graphs got “presented” elements, and detailed
graphs
Now to add some sub trees. The things we need to look at are link speed and errors, I like to
BITS/SEC
BYTES/SEC
ERRORS
So press <ADD> on the screen above and enter BITS/SEC

Press <CREATE>

So press <ADD> on the screen above and enter BYTES/SEC
Press <CREATE>
And now for Errors

So press <ADD> on the screen above and enter ERRORS
Press <CREATE>

And now press <SAVE>
However the sub-trees can also themselves have sub trees
AVID C4500X-CORE01
AVID C4500X-CORE02
AVID C4948E-EDGE03
AVID C4948E-EDGE04
location.
TVC1CORE01R1P4F3
TVC1CORE02R2P4F3
TVC1ACCE01R1P6F3

TVC1ACCE02R2P6F3
TVC1EDGE03R1P4F6
TVC1EDGE04R1P9F7

narrowed down. Also when narrowed does it will appear not much data is available, but
Unless you have configured a device you will see NO data sources for the C4948E,
configuring devices is covered in section 3.3.
In the host DROP DOWN select the C4948
The basic graph sources offered are already enabled, so no need to do it again, but no harm
done if you do.

the tick box, set CHOOSE AN ACTION to Enable and click go, and then <CONTINUE>
Now go to GRAPH MANANAGEMENT and select the host C4948
select the graph template you want (in this case C4948 example) and press <GO>
The select Destination branch I want to put these on the ROOT of this graph tree.
Press <CONTINUE>

Then click on the graphs TAB, select C4948 and we have our first graphs, but (as expected)
with not much data.
decide to plot.

months

This is a more laborious process and repetitive, but it is the fundamental purpose for this
BYTES/SEC and ERRORS. It a key point to remember that we want 64 bit counters, and
will plot the information of branches of the desired root tree.
select the desired switch then select CREATE GRAPHS (YES !!!).



Press <CREATE>, then after graphs are created press <NEXT>.

Next to the graphs for BYTES/SEC, Press <PREVIOUS> to get back to first interfaces


Press <NEXT> for higher port numbers

Next to the graphs for ERRORS, press <PREVIOUS> to get back to first interfaces.




increased from 4 to 153.
This screen will allow us to delete, disable create thresholds from the data, but we do not
click on GRAPH management, the screen looks very similar

The data set is shown in a illogical semi-random order so it is best to select the graph
my graph tree.

trees as C4948 EXAMPLE
NOW press <GO>


Now press <NEXT>, select the interfaces that you want to graph, and also the tree destination
and press <GO>
Select the BITS/SEC branch and press <CONTINUE>

After the SAVE SUCESSFUL, select <PREVIOUS> and then from TEMPLATE selection
BYTES/SEC
Select desired interfaces, PLACE on desired tree of C494 , and press <GO>.

<GO>.

SELECT BYTES/SEC branch and press ,CONTINUE

After the SAVE SUCESSFUL, select <PREVIOUS> and then from take from TEMPLATE
selection ERRORS
Select the desired interfaces.

and press <CONTINUE>
<GO>


After all the config is done selected graphs tab

Page of day up to 100 deep can be created, and data on this page can be shown by preset of
decide to plot.

3.6.3.5 Adding key interfaces to ROOT Graph tree
If this is an edge switch it might be that the 10G links are of particular importance, and we
want to add them to the ROOT of the graph tree as well.
This screen show searching for just one interface and then adding only the variables we want
to see.

3.6.3.6 Moving items on a Graph tree
This screen shows default graphs tree (with branches collapsed), sorted using the manual
ordering.
Clicking on the blue arrows will move items up or down the graph tree. Only one step at a
time is possible so for “large trees” moving around many interfaces is laborious /
Here is the thumbnail view before adjustment
After a few presses of the blue arrows the tree looks like this and the view has changed too


3.7. Configure device and graphs for a C4500-X
Configure Graph trees is the first step this may already have been done as per the example
above in section 3.2.1 above but it will be repeated here.
For a new TREE, Click on <ADD> in upper right corner of GUI,
Fill in the names and click <CREATE>
There are two steps to creating graphs. Basic graphs get “presented” elements, and detailed
graphs
Now to add some sub trees. The things we need to look at are link speed and errors, I like to
BITS/SEC
BYTES/SEC
ERRORS
So press <ADD> on the screen above and enter BITS/SEC

Press <CREATE>

So press <ADD> on the screen above and enter BYTES/SEC
Press <CREATE>
And now for Errors

So press ADD on the screen above and enter ERRORS
Press CREATE

And now press SAVE
However the sun trees can also themselves have sub trees
AVID C4500X-CORE01
AVID C4500X-CORE02
AVID C4948E-EDGE03
AVID C4948E-EDGE04
location.
TVC1CORE01R1P4F3
TVC1CORE02R2P4F3
TVC1ACCE01R1P6F3
TVC1ACCE02R2P6F3
TVC1EDGE03R1P4F6
TVC1EDGE04R1P9F7

narrowed down. Also when narrowed down it will appear not much data is available, but
Unless you have configured a device you will see NO data sources for the C44500-X,
configuring devices is covered in section 3.3.
In the host DROP DOWN select the C4500X

Notice that VLAN 147 is shown here, that is because the layer 3 interfaces are auto-
magically enabled as data sources, but we do not want to elect it for display on the ROOT of
this graph tree
the tick box, set CHOOSE AN ACTION to Enable and click go, and then <CONTINUE>
Now go to GRAPH MANANAGEMENT and select the host C4500-X
select the graph template you want (in this case C4948 example) and press <GO>

Then select Destination branch I want to put these on the ROOT of this graph tree
Press <CONTINUE>
Then Click on the graphs TAB, select C4500-X and we have our first graphs, with not much
data

decide to plot.
months

This is a more laborious process and repetitive, but it is the fundamental purpose for this

BYTES/SEC and ERRORS. It is a key point to remember that we want 64 bit counters, and
will plot the information of branches of the desired root tree.
select CREATE GRAPHS (YES !!!).

The switch in this EXAMPLE is a 16 port C4500-X, for a 32 port device, multiple screens
would be necessary, to plot all interfaces, also only physical interfaces will ne chosen,
excluding Fa1 which is the management interface, but you may choose to plot that too if it is
used.

press <CREATE>,, then after graphs are created press NEXT.
Next to the graphs for BYTES/SEC, Press PREVIOUS to get back to first interfaces

Press <CREATE>

Next to the graphs for ERRORS, Press PREVIOUS to get back to first interfaces


increased from 4 to 45 (on this 16 port C4500X with an 8 port add-in module).

This screen will allow us to delete, disable create thresholds from the data, but we do not
Click on GRAPH management, the screen looks very similar; this one is showing entries for
host C4500-X EXAMPLE only

The data set is shown in a illogical semi-random order so it is best to select the graph
my graph tree.
trees as C4948 EXAMPLE

NOW press <GO>

If additional interfaces now press <NEXT>, select the interfaces that you want to graph, and
also the tree destination and press <GO>, repeating the above process.

After the SAVE SUCESSFUL, select <PREVIOUS> and then from tike drop TEMPLATE
selection BYTSE/SEC

Select desired interfaces, PLACE on desired tree of C4500X, and press <GO>


After the SAVE SUCESSFUL, select <PREVIOUS> and then from TEMPLATE drop down
selection ERRORS
Select the desired interfaces. And press <GO>

and press <CONTINUE>

After all the config is done selected graphs tab
Page of day up to 100 deep can be created, and data on this page can be shown by preset or

decide to plot.


3.8. Graphs Creation – The Quick Way!
There is no way, or I have not found it yet- to duplicate a graph tree for another similar
device. For example spend time on creating C4948E and want to do 3 more.
There is a quick way to set a graph tree that make graphs for all the data sources you have
created. Creating data sources for C4948E for example is covered in section 3.6.2.
Note: Its is still necessary to create the data sources! See 3.5.2/3.6.2/3.7.2
SELECT CONSOLE | GRAPH TREES, then PRESS <ADD>
GIVE IT A NAME

And select the ordering, I will select natural, then press <CREATE>. But the sorting order
seems to have no impact in how the data is presented.
Then press <ADD>
GRAPH TREE {select desired e.g. TV-STATION} then ADD, then TREE-TYPE-HOST-
THEN HOST-IP
Then Select the host
Then press <CREATE>
Then Press <SAVE>
3.8.1 Viewing interfaces .

Clicking on the top of the graph tree will get you this screen, VERY LITTLE

Clicking on the HOST underneath gives the information graphs
But probably not the one you want, you must search for the data. Enter the interface and
press <GO>
And the selected information will be displayed. As the sensors for Errors, Bits/sec (64 Bit)
and Bytes per second (64 bit) has been previously set up these are shown on the web page.

Just as with the structured graphs it is possible to zoom on any main graph or show the
collated averages, and chose specific time windows.

3.9. Configure device and graphs for a Windows Server
For any Windows service the SNMP agent must be setup as described in the SECTION
NUMBER above.
TEXT To Be Created – Next version hopefully
3.10. Configure Logging Server

Configuring a Cisco switch to send information to a logging server is a single command,
however deciding what to send needs additional commands, usually at an interface level.
Interface level commands can be applied to multiple interfaces
3.10.1 Cisco Switch Essential Logging Commands
The five key commands are below. To be of any use, all log entries must be reference to the
REAL date and time, a reference to UPTIME is of little use. Also the switch must be
referenced to a reliable and accurate time source, and the switch must be told where to send
the LOGGING
service timestamps debug datetime localtime show-timezone

service timestamps log datetime localtime show-timezone
logging trap debugging <<<< THIS IS THE DEFAULT LEVEL, WHAT TO SEND
logging host 10.10.10.10 <<<< THIS IS WHERE TO SEND
ntp server 10.10.10.10
Note the as Logging is a low intensity service it may co exist on the same server as NTP, or it
may use a different shared platform.
Note some old switches will only send to a single logging server,
TESTED OK with multiple logging host entries on these devices:
C4948-10GE System image file is "bootflash:cat4000-i9s-mz.122-25.EWA8.bin

C4900M System image file is "bootflash:cat4500e-ipbase-mz.122-46.SG.bin",
C4500-X Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software
(cat4500e-UNIVERSALK9-M), Version 03.04.03.SG RELEASE SOFTWARE
3.10.2 Cisco Switch Optional Logging Commands

There are may commands and URLs in this section below provide a verbose description
It is important to log key interfaces, a but also consider that some interfaces will routinely
change state, so using it on all interfaces is to be avoided, otherwise there may be too much
irrelevant information. The interface-level command will enable logging of status changes.

logging event link-status
Applying to multiple interfaces does not have to be done individually. A RANGE command
can do multiple interfaces at the same time. Interfaces have to be in the same “slot”
ACE-4900(config)#interface range te1/1 - 8

ACE-4900(config-if-range)#logging event link-status
ACE-4900(config-if-range)#exit
ACE-4900(config)#
It is important to SIMULATE/TRIGGER conditions you would like to log, such as changes

in Spanning Tree status, or FHRP changes or port channel status.
Two helpful URLS that explain logging in more detail, which will not be duplicated here are:
http://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-
2/system_monitoring/command/reference/b_sysmon_cr42crs/b_sysmon_cr42crs_chapter_01
00.html#wp3359494668__tab_1365648
And
https://supportforums.cisco.com/document/24661/how-configure-logging-cisco-ios
3.10.3 Configuring Centos Firewall

Linux being a secure O/S is not going to let it unsolicited IP communication by default, and
syslog messages are just that. They used UDP port 514
The default Setup of EZCACTI already permits incoming SYSLOG as shown below by the
iptables command.
[root@localhost ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
DROP icmp -- anywhere anywhere icmp timestamp-request
Chain FORWARD (policy ACCEPT)

RH-Firewall-1-INPUT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)

DROP icmp -- anywhere anywhere icmp timestamp-reply
Chain RH-Firewall-1-INPUT (2 references)

ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
ACCEPT udp -- anywhere anywhere state NEW udp dpt:tftp
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:http
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:https
ACCEPT udp -- anywhere anywhere state NEW udp dpt:syslog
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ndmp
ACCEPT udp -- anywhere anywhere state NEW udp dpt:iop

REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
[root@localhost ~]#
http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers#Well-known_ports
http://www.kiwisyslog.com/help/syslog/index.html?syslogportsused.htm
Two methods for configuring the firewall are given below

http://wiki.centos.org/HowTos/Network/IPTables
http://beginlinux.com/server/centos/using-a-simple-firewall-in-centos-6
Hence it is not necessary to configure the firewall to permit incoming messages on port UDP
514.
Accessing the GUI is much easier using SSH that trying to scrabble around in the VM CLI on
the Virtual box. This will allow you to access all functions like copy paste.
ssh user@ipaddress
3.10.4 Configuring and Viewing in CACTI

The SYSLOG tab should already be pre-configured as part of EZCACTI …. It can be seen
collecting info from itself via 127.0.0.1, but it will not receive from outside without the steps
below.
It is necessary to amend the file called rsyslog.conf in /etc/
This should be done with a text editor (perhaps using NANO as described adobe) and the
RSYSLOG service has to be restarted
The command are shown below, and essentially it is just removing the # (comment out line)
character on two lines:
#$ModLoad imudp BECOMES $ModLoad imudp
#$ModLoad imtcp BECOMES $ModLoad imtcp
[root@localhost ~]# find / -name rsyslog.conf

/usr/share/dracut/modules.d/98syslog/rsyslog.conf
/etc/rsyslog.conf
[root@localhost ~]#

[root@localhost plugins.d]# cd /etc/
[root@localhost etc]# nano rsyslog.conf
[root@localhost etc]#
BEFORE - DEFAULT
#### MODULES ####
$ModLoad imuxsock # provides support for local system logging (e.g. via logger
command)
$ModLoad imklog # provides kernel logging support (previously done by rklogd)
#$ModLoad immark # provides --MARK-- message capability
# Provides UDP syslog reception

#$ModLoad imudp
$UDPServerRun 514
# Provides TCP syslog reception

#$ModLoad imtcp
$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
AFTER- ACCEPTS EXTERNAL SYSLOG

#### MODULES ####
$ModLoad imuxsock # provides support for local system logging (e.g. via logger
command)
$ModLoad imklog # provides kernel logging support (previously done by rklogd)
#$ModLoad immark # provides --MARK-- message capability
# Provides UDP syslog reception

$ModLoad imudp
$UDPServerRun 514
# Provides TCP syslog reception

$ModLoad imtcp
$InputTCPServerRun 514
#### GLOBAL DIRECTIVES ####
Edit this in NANO
Use CTRL + O to write the file

Use CTRL + X to exit the file

service rsyslog stop
service rsyslog start
or
[root@localhost ~]# service rsyslog restart

Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
3.11 Using CACTI with DELL FORCE 10 Devices
It is possible to connect to Dell/F10 devices with a default Cisco TEMPLATE which used the
RFC1213 MIB structure, however only Interface statistics are provide and it appears that the
full interface numbers are not presented, But as a quick & dirty setup up it is minimally
workable.
Each Family of DELL F10 devices appears to have a different MIB and they also vary by
software version, hence it is a little more challenging.
The Basic netwok port information can be accesses with the standard SNMP INTERFACES
MIB used by cvati
3.11.1 Importing and DELL/F10 MIB

The MIB files can be downloaded via the F10 website as ZIP files or TAR
http://www.force10networks.com/CSPortal20/KnowledgeBase/Documentation.aspx
F10 MIBS
http://www.force10networks.com/CSPortal20/KnowledgeBase/Documentation.aspx

just a reminder...the force10-etherstats.xml gets copied to your directory:
$CACTI/resource/snmp_queries/
then import the host templates.
3.11.2 FORCE 10 Templates

The URL below is a great resource for templates that can be used on Various F10 devices
http://forums.cacti.net/about29019.html

4.0 Additional functions
This section contains details on additional functions.
4.1 Locating CACTI files and disk usage

The Linux Command locate cacti will list a lot of location where elements exists
Common locations for EZCACTI are:

/var/lib/mysql/cacti/
/var/lib/yum/yumdb/c/
/var/www/backups/
/var/www/html/
/var/www/html/plugins/hmib/templates/
/var/www/html/plugins/weathermap/
/var/www/templates/
THE RRD files are located in
/var/www/html/rra/
Finding a file
The example below will look for a file with the extension *.rrd form the root (or /)
downward
find / -name '*.rrd'
The example below will look for a file with the ace as part of the file name, form the root (or
/) downward
find / -name 'ace*'
4.1.1 Disk Free and Disk Utilization

Two commands which will ne very useful are df and du
[root@localhost rra]# df --help

Usage: df [OPTION]... [FILE]...
Show information about the file system on which each FILE resides,
or all file systems by default.
Mandatory arguments to long options are mandatory for short options too.
-h, --human-readable print sizes in human readable format (e.g., 1K 234M 2G)
[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
18G 1.5G 15G 10% /
tmpfs 499M 0 499M 0% /dev/shm

/dev/sda1 485M 32M 428M 7% /boot
[root@localhost rra]# du --help

Usage: du [OPTION]... [FILE]...
or: du [OPTION]... --files0-from=F
Summarize disk usage of each FILE, recursively for directories.
-h, --human-readable print sizes in human readable format (e.g., 1K 234M 2G)
[root@localhost rra]# pwd

/var/www/html/rra
[root@localhost rra]# du -h
124M .
[root@localhost rra]#
This shows that the RRD files in this directory have used just 124MB of the allocated 20GB
of DISK allocated to this virtual machine
4.1.2 Adding MIB files to CACTI

The MIB files exist in the location
/usr/share/snmp/mibs
All the files are TXT files and not MIB files, a search for .MIB or .mib files shows none
exist. But the text files in this directory are exactly the same structure.
New MIB flies can be copied in here using CYBERDUCK s drag and drop between MAC
Finder, or FilesZilla with SFTP SSH File Transfer protocol
WinSCP – www.winscp.net Transfer files from windows OS to Linux easily
CACTI ROOT PATH in CENTOS EZCACTI is

/var/www/html
SNMP queries are in

/var/www/html/resource/snmp_queries
https://afnog.org/archives/2011-September/007020.html
https://wiki.bath.ac.uk/display/~ccsnjf/cacti+how-to
http://forums.cacti.net/viewtopic.php?f=6&t=4143
http://forums.cacti.net/about29019.html

4.1.3 Creating a Viewer account
To add an additional viewer that can only see graphs.
The steps below show adding a user called “viewer” with a restricted set of functions. The
functions need to be defined in REAL PERMISSIONS, and the devices which can be seen
must be defined in GRAPH PERMISIONS. Most of the GRAPH SETTINGS can be lefts as
default/inherited.
TEXT HERE


It is also possible to add syslog access
4.1.4 Downloading NANO as an RPM

As NANO is a much more friendly editor than VI but cannot be loaded with YUM without an
internet connection it is necessary to download the RPM files for the appropriate version of
LINUX from a repository.
This file was downloaded
nano-2.0.9-7.el6.x86_64.rpm
Create a directory called installers in root folder

Use Win SCP to copy the file form a windows host with Internet access to repository
[root@localhost ~]# cd /installers/

[root@localhost installers]# ls

nano-2.0.9-7.el6.x86_64.rpm
[root@localhost installers]# rpm -ivh nano-2.0.9-7.el6.x86_64.rpm
Preparing... ################# (100%)
[root@localhost installers]# nano /etc/hosts
GNU nano 2.0.9 File: /etc/hosts
[root@localhost installers]#
Now you can use Nano
4.1.5 Using WINSCP

This is needed to transfer files into the VM. This is necessary if you want add new packages
to a Linux VM, which has NO internet connection.
This is a ssh secure copy utility (a bit like putty)
https://winscp.net/eng/docs/guide_install

4.1.9 DATA storage
FROM http://www.cacti.net/downloads/docs/html/data_storage.html
There are lots of different approaches for this task. Some may use an (SQL) database, others
flat files. Cacti uses RRDTool to store data.
RRD is the acronym for Round Robin Database. RRD is a system to store and display time-
series data (i.e. network bandwidth, machine-room temperature, server load average). It
stores the data in a very compact way that will not expand over time, and it can create
beautiful graphs. This keeps storage requirements at bay.
Likewise, rrdtool will perform some specific tasks. It performs consolidation to combine raw
data (a primary data point in rrdtool lingo) to consolidated data (a consolidated data point).
This way, historical data is compressed to save space. rrdtool knows different consolidation
functions: AVERAGE, MAXIMUM, MINIMUM and LAST.
The URL below explains how the efficiencies are made.
http://www.mad-hacking.net/documentation/linux/management/cacti/rrd-rra-settings.xml
4.2 Adding Interface Descriptions to graphs

The web page below is the correct procedure for CACTI 0.8.8 as used by t
http://paulgporter.net/2012/12/12/enhanced-cacti-graph/
3. Modify the Title field in the “Interface – Traffic (bits/sec)” Graph Template
Add some variables to the Title field and tell Cacti to name all of the graphs it creates
accordingly. Please note that you need to un-check the box for “Use Per-Graph Value (Ignore
this Value)”, otherwise it won’t be displayed. Here’s the string to paste in:
|host_description| – |query_ifName| – |query_ifAlias| – Traffic

This will be applied to existing graphs
Template Title**
Cacti Poller Statistics - Boost Memory

Cacti Poller Statistics - Boost Runtime
Cacti Poller Statistics - Boost Updates
Host MIB - Available Disk Space
Host MIB - CPU Utilization
Host MIB - Disk IO - Bytes per Second
Host MIB - Disk IO - Transactions per Second
Host MIB - hrSystemUptime (Unix)
Host MIB - hrSystemUptime (Windows)
Host MIB - Logged in Users
Host MIB - Processes
Interface - Traffic (bits/sec)
Interface - Traffic (bits/sec, 95th Percentile)
Interface - Traffic (bits/sec, Total Bandwidth)
Interface - Traffic (bytes/sec)
Interface - Traffic (bytes/sec, Total Bandwidth)
RFC1213 - Combined protocol traffic

Interface - Traffic (bits/sec)
Interface - Traffic (bytes/sec)
|host_description| - Traffic - |query_ifName|
change to
|host_description| - Traffic - |query_ifName| |query_ifAlias|
Template Title**
Interface - Errors/Discards
|host_description| - Errors/Discards - |query_ifName|
change to
|host_description| - Errors/Discards - |query_ifName| |query_ifAlias|


5.0 Future sections for next version
If this document is utilized, it is planned to update this documents with additional sections
such as those below.
Importing and using the ISIS MIB

Configure device and graphs for a Windows Server
~END~
Note:
Note:
~END~ ~END~

Ez Cacti Setup V1.1 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ez Cacti Setup V1.1 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

EZCACTI SETUP V1.

This document is available from:

EZ_CACTI_SETUP_V1.1.docx Page 1 of 128

EZ_CACTI_SETUP_V1.1.docx Page 2 of 128

EZ_CACTI_SETUP_V1.1.docx Page 3 of 128

1.1 Hardware Platform

Suitable devices might be a Z800/400/200, or XW8600 workstation, an Intel SR2500 or

How to enable virtualization support on HP Z820 Workstation

EZ_CACTI_SETUP_V1.1.docx Page 4 of 128

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise

EZ_CACTI_SETUP_V1.1.docx Page 5 of 128

EASY CACTI useful URLs

1.4 Browser Access Centre of Excellence

EZ_CACTI_SETUP_V1.1.docx Page 6 of 128

CACTI using IE8 on WIN XP 32

EZ_CACTI_SETUP_V1.1.docx Page 7 of 128

ADD EXAMPLES FROM WIN7 IE11

EZ_CACTI_SETUP_V1.1.docx Page 8 of 128

Key first steps before beginning the installation are:

2.1 How to install VM virtualization application.

2.2 How to install application

EZ_CACTI_SETUP_V1.1.docx Page 9 of 128

2.2.1 Static IP Address steps

EZ_CACTI_SETUP_V1.1.docx Page 10 of 128

THERE MUST BE NO SPACES

EZ_CACTI_SETUP_V1.1.docx Page 11 of 128

2.3.1 SSH client

2.3.2 NANO Editor

The nano editor is very easy to use and install

yum install nano

EZ_CACTI_SETUP_V1.1.docx Page 12 of 128

2.3.3 System time

Try /sbin/service ntpd stop,

2.3.4 Shutdown and restart

**** CENTOS SHUTDOWN

2.3.4 Restart a service

service rsyslog stop

service rsyslog start

2.3.6 SYSLOG Generator

EZ_CACTI_SETUP_V1.1.docx Page 13 of 128

2.3.6 Alternative SYSLOG Viewer

EZ_CACTI_SETUP_V1.1.docx Page 14 of 128

snmp-server community aviddiva RO

EZ_CACTI_SETUP_V1.1.docx Page 15 of 128

EZ_CACTI_SETUP_V1.1.docx Page 16 of 128

AFTER PRESSING SAVE >>> Onto graph trees

3.1.2 Changing Title length in Graphs

EZ_CACTI_SETUP_V1.1.docx Page 17 of 128

Console -> Configuration | Settings | Visual

Maximum Title Length

Maximum Title Length from 80 to 100

EZ_CACTI_SETUP_V1.1.docx Page 18 of 128

EZ_CACTI_SETUP_V1.1.docx Page 19 of 128

EZ_CACTI_SETUP_V1.1.docx Page 20 of 128

Voila, ready for the next one

EZ_CACTI_SETUP_V1.1.docx Page 21 of 128

EZ_CACTI_SETUP_V1.1.docx Page 22 of 128

As can be seen the RED X will allow a whole tree to be deleted

EZ_CACTI_SETUP_V1.1.docx Page 23 of 128

3.3 Configure a device

EZ_CACTI_SETUP_V1.1.docx Page 24 of 128

EZ_CACTI_SETUP_V1.1.docx Page 25 of 128

EZ_CACTI_SETUP_V1.1.docx Page 26 of 128