In a network, as a network engineer or a network administrator, you need to know the various states of the network to determine if the network is in a healthy state or at any time, the traffic of the network, the traffic of each router, the traffic of each switch port ... Provide detailed data and graphics reports to the superior leadership at the annual report. Here, I will explain myself to everyone about how to get network traffic. If necessary, you can do it immediately, do your company's network traffic monitoring map. The monitoring of network traffic needs to be related to SNMP, Perl, MRTG, and a little web page. Now I will explain how the step by step gives you how to implement it. My level is limited, if there is a mistake or better solution, please ask everyone, thank you!
Note: Some information in the text is collected from the Internet.
table of Contents
Install MRTG Raiders under Windows - Network Traffic Monitor 1
Sequential 1
Directory 1
SNMP introduction 2
MRTG Introduction 4
Step by step teaches you to install Perl 7
Step by Step teaches you to set SNMP 11
Step by Step teaches you to install MRTG 14
Add traffic graph to your website 19
SNMP introduction
A network management system generally includes the following elements: 1 Several (possibly a number) requires managed network device nodes, such as routers, servers, etc., each node is running a device representation (Agent) The application process, its collection of information such as traffic such as traffic such as traffic such as traffic, etc., and supports these managed objects; 2 at least one management workstation, the management station runs the management platform application system, Implementation provides administrators with visual graphical interfaces of the managed equipment, enabling administrators to manage; 3 A management protocol to define the management information transfer between device proxy and management workstations. The operation of the management protocol is conducted in the management framework, the management framework defines a variety of security protection frameworks such as security-related authentication, authorization, access control, and encryption policies.
In an Internet environment running the TCP / IP protocol, the management protocol standard is a Simple Network Management Protocol (SNMP) that defines the protocol message format and management station and device proxy for transmission management information. Procedure.
For the industry's urgent requirements for the standardization of network management protocols, IETF issued the formal RFC document of SNMPv1 in 1990; its design idea focuses on the simplicity, flexibility and scalability of the protocol, and hopes to use SNMP as A transitional network management protocol comes as a standard that implements the interconnection of network devices to manage, the development, implementation, and standardization of the network management protocol of OSIP - CMIP can be used after the industry is promoted. Replace SNMP. However, due to various reasons, CMIP did not replace SNMP, while SNMP developed as the industry standard.
SNMP has three main versions of SNMPv1, SNMPv2, and SNMPv3, respectively. Where SNMPv2 is divided into several subprins, where SNMPv2c is the most widely used:
SNMPv1: is the first formal protocol version, defined in RFC1155-RFC1158, which uses a community-based security mechanism;
SNMPv2C: This version is called a common-friendly SNMPv2, which uses the expansion of protocol operation based on the security mechanism based on common name and SNMPv2P, which is defined by RFC1901-RFC1906;
SNMPv3: This protocol version adopts user-based security mechanism, and its security mechanism is updated after SNMPv2U and SNMPv2 *, and has been updated after a large number of reviews, and the logical function module of the protocol has ensured good. The expansion is defined by RFC2271-RFC2275. The principle and SNMP protocol running the SNMP management system
The network management system management structure of the SNMP protocol generally includes: the management process transmits a query request message (in polling mode) to each device, to track the status of each device (in polling mode), and an abnormal event such as device When cold start, the device proxy process actively transmits a trap message to the management process, and report an exception event that appears. These polling messages and trap messages and their formatted definitions are defined by the SNMP protocol; and the information managed by the managed device puts the information of various management objects in a management information base. In the library structure.
Where the SNMP protocol is running over the UDP protocol, it uses the 161/162 port of the UDP protocol. The 161 port is listened by the device agent, waiting for the management information query request message sent by the administrator process; 162 ports Mon the manager to listen to the exception event report trap messages sent by the device agent process, such as TRAP.
All of the device's information is managed is considered a collection of various managed objects, which are defined in the virtual information library called Management Information Base (MIB) in a virtual information library.
Manage object library MIB
The MIB is a tree structure (definition method similar to the domain name system) according to the hierarchical structure (defined by the domain name system), and the management object is defined as the corresponding leaves node in the tree. The management object is organized according to the form of the module, and the parent node of each object indicates which module belongs to the upper layer. Moreover, OSI is defined a unique digital identifier for each node of each layer in the tree, and the number identifier in each layer begins to increment, so that each node in the tree can be used from the beginning to the destination node. Identify the corresponding series of numbers, as 1.3.6.1.2.1.1 represents the system group tree in the MIBII, and 1.3.6.1.2.1.1.1.0 represent the system description object in the system group. A series of string numbers for each object is called an object identifier (Object Indentifier, OID).
A collection of related groups of objects is defined as a MIB module. These modules are written using a subset of Abstract Syntax Notation One, ASN.1) using OSI's abstract syntax tags. This subset is defined as a management information structure (SMI).
The message of SNMP is encoded for the message using the Basic Coding Rules (BER) when sending and transferring.
SNMP basic standard MIB library is MIBII, please refer to RFC 1213 for details.
SNMP protocol operation
SNMP provides three types of operations, which are GET, SET, and TRAP, respectively.
The GET operation implements a read operation of the management information represented by the managed object. In SNMPv1, there are two forms in the GET operation.
GET and GetNext Actions: The GET operation indicates the management information value of the managed object represented by the OID specified by the operation parameter. The GetNext operation indicates the value of the managed object represented by the OID specified by the read operation parameter in the MIB tree in the MIB tree, according to the management information of the management information of the management object. In SNMPv2, a getBulk operation is added, which is a comprehensive integrated GET and GetNext, which is increasing to increase access to the access to managed information.
The SET operation implementation writes the management information of the managed object, which implements the setting of the value corresponding to the management information corresponding to the OID specified by the operating parameter.
The previous message is a variety of information that is sent to the managed device to get the managed device by active implementation of the management station to obtain the managed device; when the abnormality event in the managed device needs to report to the management station report, it is necessary to TRAP operation. This action implements an exception event that is managed on the management of the management workstation, such as faulty or recovery work, and device restarts, such as network interfaces. An additional SNMPv2 adds an inform operation to implement communication between the management station and the management station. The above operations can specify one or more management object OID information at a time in the operational parameter, that is, a message can be implemented at a time.
SNMPv1 and SNMPv2c use a simple commonly used security mechanism:
The management station and the tube device are stored on the tangible function. The message sender (typically manager) fill in the common body name corresponding to the recipient in the Community Name field in the message to be sent, and then The apparent manner is sent on the network, and after receiving the message, if the message format is correct, read the field, compare the sympathy of the self-saving, to realize the authentication of the sender . In some implementations, there is a list of machine address list corresponding to each common name, which means that only messages sent by the address in this list is only trusted. The common name here serves as a password. At the same time, there is an access control permission corresponding to each common body name, and the value is read or read or written. Only the right to operate and the permissions of the common names used will only be permitted.
For details, please refer to RFC 1157, RFC 1902, RFC 2273, RFC 2274.
Introduction to MRTG
MRTG has the following features:
Portability: It is currently running on most UNIX systems and Windows NT.
Source opening: MRTG is written in Perl, and the source code is fully open.
High-profit SNMP support: MRTG uses high-portability SNMP implementation modules prepared by Simon Leiner, which is not supported by SNMP module of the operating system.
Support SNMPv2c: MRTG can read the 64-bit integer of SNMPv2c, which greatly reduces the number of revolutions.
Reliable interface ID: The interface of the monitored device can be identified by the IP address, device description, SNMP to the interface number and MAC address.
Constant size log file: MRTG's log will not be large, because the unique data merge algorithm is used here.
Auto Configuration Function: MRTG itself has a configuration tool kit that makes the configuration process very simple.
Performance: Time-sensitive part is written using C code, so it has good performance.
PNG format graphics: Graphics use GD libraries to generate PNG formats.
Destative: The web page generated by the MRTG is fully customized.
MRTG's homepage is http://www.mrtg.org, you can download the software from here.
MRTG compatibility
The MRTG software can run on the following operating system:
Linux 1.2.x, 2.0.x, 2.2.x, 2.4.x (Intel And Alpha And Sparc and PowerPC)
Linux MIPS, Linux S / 390
Sunos 4.1.3
Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8
AIX 4.1.4, 4.2.0, 4.3.2
HPUX 9, 10, 11
WindowsNT 3.51, 4.0, 2K, XP
Irix 5.3, 6.2
BSDI BSD / OS 2.1, 4.x, 3.1
NetBSD 1.5.x
FreeBSD 2.1.x, 2.2.x, 3.1, 3.4, 4.x
OpenBSD 2.x
Digital UNIX 4.0
SCO Open Server 5.0
Reliant UNIXNextstep 3.3
Openstep 4.2
Mac OS X 10.1
And About And Other Sensible Unix
It can be monitored by MRTG (most products on the market support SNMP protocol, as long as the device supporting the SNMP protocol can be used to monitor):
3Com NetBuilders, LANPLEX 6012 and 2500
3COM Etherswitches and hubs
3COM LINKSWITCH 1000 1100 3300
3Com SuperStack II Switch 3900, 3300 MX
3COM 812 ADSL ROUTER
Alantec Powerhub 7000
Allied Telesyn - 8224xl and 8324xl 24 Port Managed Switches
Annex Terminal Server
Asante Hub
Ascend (Lucent) max 600, [24] 00X, PIPELINE 50, TNT, APX-8000, MAX-6000
Alcatel (Assured Access) x1600, Omnisr9, Omnicore 5022
AT & T Wave Point, LAN
BayNetworks (Wellfleet) 7.80 and Up, Baystack 350T, Instant Internet, See Nortel
BreezeCom AP, SA
Cabletron ESX-820 Etherswitch, Smartswitch 2000, 6000 and Router
Centillion Token Ring Speedswtich 100 (IBM 8251 Token Ring Switch)
About Every Cisco Kit there is ...
CENTRECOM 8116
Compatible Systems
Decbridge 620, Dec 900ef, 900ee, Gigaswitch
ELSA LANCOM L 11 (Wireless Router)
Enterasys Matrix E5, VH-4802 and VH-2402S Switche
Ericsson Tirgis Series Ras Servers
Extreme NetWorks - BlackDiamond 6808 & Alpine 3808 Layer 3 Switches
Fore asx200 ATM
FlowPoint 2200 ATM / DSL ROUTER
Formula 8200 Series
Foundry Bigiron 8000 GigaBit, Fastiron Switch, Serveriron Switch
Cable Modems from lant, terayon and docsis
HP - NetWork Interfaces, Disks, Database INFORMIX
HP AdvanceStack / Procurve Switch 2000 and 2524, Advancestack Switch 200
HP Procurve Switches, Model 4000M, 2424M and 2400M
IBM 8260 SWTICH (with 155MB ATM Blades Installed), IBM 2210 ISDN Routers.
Intel Switches (Details) - 510T, Intel GigaBit Server Adapter
IMV VICTRON NETPRO 3000 UPS
Kentrox Pacesetter Pro
Lantronix Bridge
Lucent / Xedia Access Pointt 450, 1000Livingston (Lucent) IRX 3.2.1R, IRX 114, PM2E (R) PM3-2E OR-U
Motorola 6560 Regional Node, SB3100 Cablemodem, 320, 6430 and 6455 Routers
Morningstar Terminal Servers / Routers
MGE (Merlin Gerin) Upses (Details)
Network Appliance
NETOPIA R7100C SDSL
Netscreen 5/10/100
Nortel Networks, Bay Routers BCN, BLN, ASN, ARN, AN, PASSPORT 1K AND Passport 8k3 Series L3 Switches, Baystack 450 L2 Switches.
Nortel NetWorks, Accelar L3 Switches
NOKIA IP 330/440/650
NBase Ethernet Switch
Novell 3.11, 4.11
RMON Probes
SGI-Server (Irix 5.3)
Any Server Server Running HP-UX, Ultrix, Solaris, Sunos, OSF, NetBSD, FreeBSD, BSDI, Linux, AIX, OpenBSD, IRIX OREVEN Windows Operating Systems (Badly), WHEN Using Net-SNMP (FORMER UCD-SNMP).
Apple Mac (AN SNMP Service Is Included on the OS CD> = 8.5)
Shiva Accesport
Solaris Server
Squid Web Cache
US-Robotics Total Control Modemracks
Wellflet (Later Bay Networks): See Nortel Routers
Wavewireless Speedlan 8x00 RF Routers
Winnt, MS Proxy
XYLAN (Today Alcatel) 4024C 24port 10/100 Omnistack Switch, 9k Devices, Including ATM Links.
Yamaha RT100i
Zyxel PRESTIGE P310, 153X, 642.
MRTG device does not support:
D-Link Switches (DETAILS)
Step by step teaches you to install Perl
Perl installation is relatively simple, usually Active Perl for Windows, now the latest version is 5.8.0, it requires the user to install IIS or Apache and other common web server platforms. Here, I will install the most commonly used IIS, if you need to install Perl in the Apache platform, the result will be slightly different.
Perl is suitable for all kinds of work platforms of the five flowers, including all known UNIX / Linux
And Microsoft's operating system, as well as the following platforms that support POSIX: BEOS, CYGWIN, NETWARE, MPE / IX, OS / 2, QNX, VMS, VOS, and Z / OS. Macintower Macos Classic users can also in HTTP : / (Dev.macperl.org/ Download the exclusive transplanted version.
In this example, we take ActivePerl-5.6.1 as a installation example to teach how to install, Perl for Windows version is MSI installation package, general case, such as ActivePerl-5.6.1.633-mswin32-x86.msi, you can go to HTTP : //downloads.activestate.com/activeperl/windows/5.8/ActivePerl-5.8.0.805-mswin32- x86.msi Download the latest version of ActivePerl. The process of installing Perl is simple, but still want to explain:
My current environment is Windows 2000 Server English version Pack3, IIS5.0 platform.
1. Open Perl installation file, click Next,
2, no choice, only agree to the agreement will be next step.
3, there must be noticed here, the system is installed in the Perl directory by default, but for our future use, you must remember to modify the USR directory, the drive letter should generally be the same as the root of the web. The results are as follows:
4, the next picture will make you confirm whether you use [PPM3 send personal information to ASPN], or save some, don't choose it, directly press the next step.
5, here can all choose, next.
6. The prompt is ready to start installing, the next step.
7, start installing
8, after a hard disk, the system is successful! Probably waiting for a few minutes
9. Installing Perl to end, is it super simple.
After Perl is installed, you can open [Internet Information Services] -> [DEFAULT Website] -> [Properties] -> [Home Directory] -> [configuration] to see the following screen
When I saw PL, PLX, I said that the installation was successful, the other .cgi is my own manual plus, the method is to click on the other [add ...]
Enter the string as shown in the dialog that appears.
Then we can test the results of the installation, usually use the so-called CGI probe, you can find it online. As shown in the above figure, our Perl installation configuration is successful, you can go to the next step.
Step by Step teaches you to set up SNMP
After we installed Perl, we must first set the device you need to monitor traffic, which may be routers, switches ... Even a computer installed Win2K. As long as it supports traps of SNMP, they can use to function as monitored objects. I will introduce you to a Cisco 2950 switch and Huawei 2600 router. Because IOS versions and other uncertainties are involved, I hope that everyone can use it flexibly. Of course, the following example is that I adopted by my hand, you only need to change the relevant name, you can use it normally.
In order to facilitate everyone to read, I briefly explain: When setting the Community string, don't use the default public because it is not easy to listen by some hackers, or there is a security vulnerability, you can choose the string you think meaningful; Host It is a host IP name that receives Traps, which can be adjusted according to your actual needs.
The following command is debugged in the Cisco 2950 environment:
C: / telnet IP of your switch
User Access Verification
PASSWORD:
TNKSW> EN
PASSWORD:
TNKSW # conf T
TNKsw (config) # nmp-server community chinatnk Rotnksw (config) # snmp-server trap-source FasteThernet0 / 1
TNKSW (config) # snmp-server contact cqfanli@163.com
TNKSW (config) # snmp-server host 192.168.0.6 chinatnk
TNKsw (config) # snmp-server enable traps
TNKSW # sh Run
TNKSW # WR
(The following is a partial extract show run command)
......
......
It can be seen that the SNMP of our switch has been working properly. Of course, the most important thing is to save the preservation. Otherwise, it will give up, huh, huh ...
Look at the configuration of Huawei 2600 router, it is also almost the same, but Huawei's product seems to be a little different, ^ _ ^
C: / telnet IP of your switch
User Access Verification
PASSWORD:
QJRouter> EN
PASSWORD:
Qjrouter # conf (Huawei products do not take terminal parameters, * _ *)
Qjrouter (config) # snmp-server?
Community Enable SNMP; SET COMMUNITY STRING
Contact text for Mib Object Syscontact
ENABLE ENABLE SNMP TRAPS
Host Specify Hosts To Receive SNMP Traps
Location Text for MIB Object Syslocation
Trap-Authentication Send Trap on Receipt of IncorRect Community String
Qjrouter (config) # snmp-server enable traps
Qjrouter # snmp-server contact cqfanli@163.com
Qjrouter (config) # SNMP-Server Location Chinatnk
Qjrouter # snmp-server communication?
Ro Read-Only Access with this Community String
RW Read-Write Access with this Community String
Qjrouter (config) # SNMP-Server Community Ro chinatnk
Qjrouter (config) #
Qjrouter # WR
Qjrouter # sh ru
(The following is a partial extract show run command)
......
......
Friendly Tips: Be sure to save, don't forget, ^ _ ^
Step by Step teaches you to install MRTG
We must first download the latest MRTG from the Internet, the official website of MRTG is: http://people.ee.ethz.ch/~Oetiker/webtools/mrtg/ mrtg China Mirror Website is: http: // mrtg .openunion.org / mrtg download URL is: http://people.ee.thz.ch/~Oetiker/webtools/mrtg/pub/, the latest version is: mrtg-2.9.27.zip If you are using Is Linux or UNIX system, you can download MRTG-2.9.27.tar.gz directly. After the software is downloaded back, we must first decompressed it first. Since MRTG is a PERL write program, it is not necessary to install. Some installation processes will be completed in DOS, so it is recommended to decompress the path to C: / MRTG. The following is given to the detailed installation steps:
1. Run the CMD to enter the DOS status;
2, C: /> CD / MRTG / BIN enters the MRTG directory that just decompressed, ready to execute the command;
3. Use the perl mrtg command to test whether the MRTG is correct;
4, execute the command line Perl cfgmaker chinatnk@192.168.0.254 - Global "Workdir: C: / WWW / MRTG" --output mrtg.cfg
This line ordered me to explain:
Chinatnk@192.168.0.254 Used is the community of the device that you need to get SNMP data and its IP address;
Workdir: C: / WWW / MRTG Used is used to properly install MRTG, you need to use the web directory to change according to the actual situation;
Output mrtg.cfg is the output post-output configuration file name;
After changing it, press Enter to the bus, and the system began to implement the configuration. Since I first used the SNMP source, the above command is executed, it will bind 24 ports, there are some information displayed, and there is not much binding port on the router, so the amount of information will be slightly slightly less.
After this step is performed normally, the system will generate the specified MRTG.cfg file in the MRTG directory, and the next step is to modify the MRTG file to make it in line with our requirements.
Some equipment does not support SNMP protocols, and there will be an error message here, please pay attention to you.
Note that if you need to monitor traffic to multiple devices, you need to modify the configuration file names behind the Output parameter, which is mrtg.cfg.
The details are as follows:
C: / MRTG / BIN> Perl cfgmaker chinatnk@192.168.0.4 --global "Workdir: E: / Webroot / MRT
g "--output mrtg4.cfg
--BASE: Get Device Info on chinatnk@192.168.0.4:
--BASE: VENDOR ID: Cisco
--BASE: Populating Confcache
- Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 1 -> 1
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 2 -> 2
- Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 3 -> 3
- Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 4 -> 4 - Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 5 -> 5
--Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 6 -> 6
--Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 7 -> 7
--Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 8 -> 8
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 9 -> 9
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 10 -> 10
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 11 -> 11
--Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 12 -> 12
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 13 -> 13
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 14 -> 14
- Snpo: Confcache chinatnk@192.168.0.4: Name FA0 / 15 -> 15
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 16 -> 16
- Snpo: confcache chinatnk@192.168.0.4: name fa0 / 17-> 17
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 18 -> 18
- Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 19 -> 19
--Snpo: confcache chinatnk@192.168.0.4: Name FA0 / 20 -> 20
--Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 21 -> 21
- Snpo: confcache chinatnk@192.168.0.4: Name Fa0 / 22 -> 22
- Snpo: confcache chinatnk@192.168.0.4: name fa0 / 23 -> 23
- Snpo: confcache chinatnk@192.168.0.4: name fa0 / 24 -> 24
- Snpo: confcache chinatnk@192.168.0.4: name nu0 -> 25
--Snpo: confcache chinatnk@192.168.0.4: name VL1 -> 26
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 1 -> 1
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 2 -> 2
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 3 -> 3
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 4 -> 4 - Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 5 -> 5
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 6 -> 6
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 7 -> 7
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 8 -> 8
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 9 -> 9
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 10 -> 10
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 11 -> 11
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 12 -> 12
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 13 -> 13
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 14 -> 14
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 15 -> 15
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 16 -> 16
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 17 -> 17
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 18 -> 18
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 19 -> 19
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 20 -> 20
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 21 -> 21
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 22 -> 22
--Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 23 -> 23
- Snpo: confcache chinatnk@192.168.0.4: Descr Fastethernet0 / 24 -> 24
- Snpo: confcache chinatnk@192.168.0.4: Descr Null0 -> 25
- Snpo: confcache chinatnk@192.168.0.4: Descr Vlan1 -> 26 - Snpo: confcache chinatnk@192.168.0.4: ip 192.168.0.4 -> 26
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 1
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 2 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 3 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 4 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 5 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 6 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 7 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 8 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 9 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 10 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 11 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 12 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 13 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 14 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 15 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 16 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 17 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 18 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 19 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 20 (duplicate)
- Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 21 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 22 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 23 (duplicate) - Snpo: confcache chinatnk@192.168.0.4: Type 6 -> 24 (duplicate)
--Snpo: confcache chinatnk@192.168.0.4: Type 1 -> 25
--Snpo: confcache chinatnk@192.168.0.4: Type 53 -> 26
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-81 -> 1
--Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-82 -> 2
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-83 -> 3
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-84 -> 4
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-85 -> 5
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-86 -> 6
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-87 -> 7
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-88 -> 8
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-89 -> 9
--Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8A -> 10
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8B -> 11
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8C -> 12
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8D -> 13
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8E -> 14
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-8F -> 15
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-90 -> 16
--Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-91 -> 17
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-92 -> 18
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-93 -> 19
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-94 -> 20 - Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-95 -> 21
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-96 -> 22
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-97 -> 23
--Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-98 -> 24
- Snpo: confcache chinatnk@192.168.0.4: Eth -> 25
- Snpo: confcache chinatnk@192.168.0.4: Eth 00-0B-BE-B2-B8-80 -> 26
--BASE: GET INTERFACE INFO
--BASE: WALKING IFINDEX
--BASE: WALKING IFTYPE
--BASE: WALKING IFADMINSTATUS
--BASE: WALKING IFOPERSTATUS
--BASE: WALKING OFALIAS
--BASE: WALKING IFSPEED
--BASE: Writing mrtg4.cfg
C: / mrtg / bin> Perl mrtg mrtg4.cfg
C: / mrtg / bin>
C: / mrtg / bin> Perl cfgmaker chinatnk@192.168.0.254 - Global "Workdir: E: / Webroot / M
RTG "--output mrtg5.cfg
--BASE: Get Device Info on chinatnk@192.168.0.254:
--BASE: VENDOR ID:
--BASE: Populating Confcache
- Snpo: confcache chinatnk@192.168.0.254: Descr Ethernet0 -> 1
- Snpo: confcache chinatnk@192.168.0.254: Descr Serial0 -> 2
- Snpo: confcache chinatnk@192.168.0.254: descr bri0 -> 3
- Snpo: confcache chinatnk@192.168.0.254: Descr loopback0 -> 4
--Snpo: confcache chinatnk@192.168.0.254: IP 127.0.0.1 -> 4
- Snpo: confcache chinatnk@192.168.0.254: ip 192.168.0.254 -> 1
- Snpo: confcache chinatnk@192.168.0.254: IP 202.104.141.177 -> 1
- Snpo: confcache chinatnk@192.168.0.254: Type 6 -> 1
- Snpo: confcache chinatnk@192.168.0.254: Type 23 -> 2
--Snpo: confcache chinatnk@192.168.0.254: Type 23 -> 3 (duplicate)
- Snpo: confcache chinatnk@192.168.0.254: Type 24 -> 4 - Snpo: confcache chinatnk@192.168.0.254: Eth 00-E0-FC-06-D4-21 -> 1
- Snpo: confcache chinatnk@192.168.0.254: Eth 00-00-00-00-00-00 -> 2
- Snpo: confcache chinatnk@192.168.0.254: Eth 00-00-00-00-00-00 -> 3 (Duplicate
)
--Snpo: confcache chinatnk@192.168.0.254: Eth 00-00-00-00-00-00 -> 4 (duplicate
)
--BASE: GET INTERFACE INFO
--BASE: WALKING IFINDEX
--BASE: WALKING IFTYPE
--BASE: WALKING IFADMINSTATUS
--BASE: WALKING IFOPERSTATUS
--BASE: WALKING IFSPEED
--BASE: Writing mrtg5.cfg
C: / mrtg / bin> Perl mrtg mrtg5.cfg
C: / mrtg / bin>
5, start generating traffic graphs and profiles
6,
C: / mrtg / bin> Perl mrtg mrtg.cfg
After the command is successfully executed, it will generate a web page named by IP port in the web directory specified by our previous command, which is the traffic chart of the network. We can open this page directly to check it, see if it is normal. Many after the beginning of the generation is blank, you need to let it run for a while, you can have graphics.
7. To make MRTG can get the latest traffic chart at any time, we also need to modify the configuration script, mainly the file name MRTG.cfg that just tested by the Output parameter, open it with the text editor.
The file head has explained the different configuration methods inside the Windows system or in the UNIX system. Now because it is a new version of MRTG, a working directory has been automatically added to the end, and does not need to be edited.
In order to make the network traffic map can be automatically updated every 5 minutes, we still need
### Global Config Options Join one command:
RunasDaemon: YES
The action of this command is to enable MRTG to automatically obtain a SNMP data and update network traffic graphics every 5 minutes.
Save the file and exit.
8. When we need more than one device simultaneously or more than one or more, it will involve generating multiple profiles, which looks more difficult, then we need to use the indexmaker command to multiply Collect it into a file.
Perform the following command:
C: / mrtg / bin> Perl indexmaker --output = index.htm mrtg.cfg
At this point, the system will automatically generate index.htm in our designated web directory, we can now open the web file to see if it is normal.
9. In order to enable the system to automatically run this command after each boot, we also need to join this shortcut in the startup.
1), right click on the desktop, select shortcuts.
2), enter a shortcut to run command behavior start / d c: / mrtg / bin wperl mrtg -logging = eventlog mrtg.cfg
3) Enter a good file name, such as "MRTG traffic monitoring".
9, to this, MRTG can be running normally and will give us a 5-minute traffic diagram, daily traffic diagram, weekly traffic diagram, monthly traffic diagram, annual traffic diagram. More detailed installation of MRTG methods in MRTG official website: http://people.ee.ethz.ch/ ooetiker/webtools/mrtg/nt-guide.html
Add traffic graph to your website
In front, we have generated a map file file, now beautify it, and join your website.
We use the DreamWaver MX and other web making software to open it, and beautify it according to the messenger you need or the website, you can use it.
(Full text)
