E
DITING
A
L
OG
P
ROCESS
7-3
Editing a Log Process
EliteView’s powerful Log Manager gathers a wide variety of network statistics based
upon rules (i.e., log processes) you define. Using the Log Manager, you can monitor any
MIB variable for a target SNMP device. Each log process defines the parameters under
which data related to the specified MIB variable is collected and placed in the central
database. The Log Manager controls the data collection activity, as well as allowing you to
display and manipulate the data gathered as described in the section on “Viewing Log
Data”
Adding a New Log Process
1. Click the
Add a new record
toolbar button.
2. Fill in the parameters in the Log Information dialog box. Process
parameters are defined in the table on the next page.
Not all parameters are required. Only Protocol, Target Address
and Variable are mandatory.
Protocol
– Click the down arrow to choose from UDP (default),
IPX or Ethernet.
Target Address
– Use appropriate notation for selected
protocol.
Community
– Community strings control access rights to
network resources. Define your own community string to prevent
unauthorized access to critical resources. However, if you do not
have any special security concerns, then retain the default
community string of public. Refer to the description for object
editing in Chapter 4 “Defining the Network Configuration.”
MIB Modul
e – Includes standard MIBs based on the RFCs,
device-specific MIBs, and private MIBs. For variable names not
duplicated in other MIB modules, the default of Any is sufficient.
3. Choose
OK
to add the new log process or
Cancel
to abort your
selections.
Add/Delete/Edit a
Log Process
Summary of Contents for ELITEVIEW
Page 1: ...MANAGEMENT GUIDE EliteViewTM 6 20 SNMP Based Network Management Softwarefor Windows ...
Page 2: ......
Page 8: ...iv ...
Page 20: ...INTRODUCTION 1 4 ...
Page 66: ...NETWORK TOOLS 5 18 ...
Page 106: ...COLLECTING DATA WITH LOG MANAGER 7 22 ...
Page 121: ...RMON UTILITIES 9 7 ...
Page 156: ...TYPICAL ELITEVIEW APPLICATIONS A 8 ...
Page 180: ...TECHNICAL REFERENCES D 4 ...
Page 188: ...SPECIFICATIONS F 4 ...
Page 222: ...ERROR MESSAGES I 30 ...
Page 231: ......