Startup and Configuration Files

This appendix contains information about the agent startup files. The agent startup script file contains information that you enter and modify that reflects the configuration of a specific SwitchProbe device.

The following sections provide additional information:

Overview of Startup and Configuration Files

Startup files reconfigure the device to normal operation after a reset. Startup files reinstall all domains and other parameters you have specified on the device and in the startup file.

Configuration files include any files in the $NSHOME/usr directory that:

Contain agent, Frame Relay agent, switch or agent group, domain, or report parameters you define.
Contain parameters that control the number of hosts defined in the TrafficDirector application.
Contain lists of protocols or parent child protocol relationships.
Contain lists of device name mappings.

Agent Startup File

When you define an agent by clicking the Add button in Configuration Manager, one of the fields is the Startup File. This field specifies the name of a script file to be executed when the dvtrapd daemon receives a configuration request from an agent that has reset.

A default startup script file, named startup, ships with the TrafficDirector software. The default path is $NSHOME/usr. This standard startup file is shown here:

#
# Default startup script file "startup"
#
# Note: "%1" is a macro replaced by the agent name.
 
dvcfg %1

The agent name is passed as an argument, so you can use the same startup script for multiple agents. You use the startup script to configure or reconfigure an agent to a specific domain setup. The default startup does this by running the dvcfg utility. The arguments you pass to dvcfg are the name of a configuration file, the appropriate properties file(s), and the name of the agent.

Configuration Files

Configuration files can be specific to a particular TrafficDirector installation or available at any installation.

Specific to a particular TrafficDirector installation---The file may contain unique configurations that are specific to the agent or agents local to that installation of the TrafficDirector software.
Available at any installation---The file contains parameters that are common to all agents regardless of their location relative to the TrafficDirector software.

Note Some files are not suitable for editing. Where applicable, this restriction is indicated in the file description.

Table C-1 describes the various configuration files found in the $NSHOME/usr directory.

Table C-1: Configuration Files in $NSHOME/usr Directory
File Name Description

appgrp.cfg

Available for use at any installation, this file contains a list of the parent-child relationships between a domain group and individual protocols at the TrafficDirector Application level. You can edit this file with an ASCII text editor.

autorpt.cfg

Available for use at any installation, this file contains the list of reports scheduled to run automatically. You can edit this file with an ASCII text editor or build it incrementally using the Trend Reporter application.

dbupdate.cfg

Available for use at any installation, this file contains the detail and summary aging intervals and thresholds used for Protocol, Segment, Host, Conversation, Proxy SNMP, IP Ping, ALL NL, ALL AL, ART, ART SUMM, Host Threshold, Conversation Threshold, Baseline A, Baseline B, and Hour Range. You can edit this file with an ASCII text editor or the Config Rollup application.

The dbupdate configuration file contains the following aging parameters:

Detail Aging---Shows the number of days that information ages before the Aging daemon determines it to be obsolete and deletes it from the details table. Detail aging must be greater than one day. The default value for protocol and segment statistics from the detail table is 31 days; for host, conversation, IP Ping, Proxy SNMP, ALL NL, ALL AL, ART, and ART Server, it is 7 days.

Summary Aging---Shows the number of days that information ages before the Aging daemon determines it to be obsolete and deletes it from the daily table. Daily aging must be greater than one day. The default value for protocol and segment statistics from the Summary (Daily) table is 366 days; for host, conversation, IP Ping, Proxy SNMP, ALL NL, ALL AL, ART, and ART Server, it is 31 days.

dbupdate.cfg
(continued)

Host Threshold---Configures the minimum utilization percentage that a host (combined inbound and outbound utilization) must meet before it is included in the host details table. The Snapshot daemon compares a host segment utilization percentage to this number and logs data to the host bin details binary file only if the utilization percentage meets or exceeds this value.

Baseline Time Range---You can configure each database table to participate in the baseline time-range. Baseline A and Baseline B time range data is maintained (protected against purge) so that baseline data will be available at report time.

By default, all database tables are enabled to participate in the baseline time range. However, both Baseline A and Baseline B time ranges default to None. When you set the Baseline A or Baseline B time range (enabled, other than None), all database tables are initially set enabled. This may result in logging more data than you expect.

dept.cfg

Available for use at any installation, this file contains a list of the Department/Alias name mapping for Trend Reporter Billing Reports. You can edit this file using an ASCII text editor. Cisco Systems recommends that you create a new file for each different department list you want for Trend Reporter Billing Reports.

Host Address Department/ Alias Name Address Family

5.128
6.129
00-0A-C9-08-14-98
204.204.244.100
0002.00aa08
0002.a0

Eng-A
Eng-D
Eng-MAC
Eng-IP
Eng-IPX
Eng-V

ATALK
DECnet
DLC
IP
IPX
VINES

dlciinfo.cfg

Available for use at any installation, this file contains an example of a properly formatted configuration file containing DLCI information to be downloaded to an agent using the dvftp command-line utility.

ipdfilt.cfg

Available for use at any installation, this file contains an example of a properly formatted configuration file containing data reduction information to de downloaded to an agent using the dvftp command-line utility.

nsconfig.cfg

Available for use at any installation, this file contains the maximum number of: host MAC addresses allowed in the macaddr.nam file and vendors allowed in the vendorid.nam file. You can edit this file with an ASCII text editor. Sufficient memory must be available if you are increasing the number of hosts or vendors. The default limit on the number of entries in each file is 4096.

protogrp.cfg

Available for use at any installation, this file contains a list of the parent-child relationships between a domain group and individual protocols at the TrafficDirector Protocol level. You can edit this file with an ASCII text editor.

tariff.cfg

Available for use at any installation, this file (see sample) contains a billing rate for Trend Reporter Billing Reports. You can edit this file using an ASCII text editor. However, it is recommended that you create a new file for each different billing rate you want for Trend Reporter Billing Reports using the vi copy feature.

# ----------------------- # Rate in US $ per 1KByte # ----------------------- # Max precision #-rate 0.1234567 # Default #-rate 0.01 Default if file or -rate not found

agent.lst

Specific to a particular installation, this file contains agent definitions. Each line within the file defines a unique SNMP agent that the TrafficDirector application can access. Agent names you specify can be up to 15 characters. You create and update this file through using the TrafficDirector application, although you can edit the file directly. You can define up to 1000 agents in this file.

agegroup.lst

Specific to a particular installation, this file contains agent group definitions. Each line within the file defines a unique group of SNMP agents that the TrafficDirector application can access. To be included in this file, you must first set up the agent definitions in the agent.lst file. Agent group names you specify can be up to 15 characters. You create and update this file through the TrafficDirector application, although you can edit the file directly. You can define up to 100 agent groups in this file; each agent group can contain up to 60 agents.

domain.lst

Available for use at any installation, this file contains domain definitions (see partial sample list). Each line within the file defines a unique domain which represents a characterization of traffic. The TrafficDirector application supports two types of domains:

Protocol domains---Provide the means to classify network traffic by protocols that reside in the top five layers of the OSI model (network layer through application layer; for example, IP, IPX, TCP, and TFTP).

Generic domains---Provide a means to classify network traffic by protocols that reside in the data link layer of the OSI model (layer 2). For example, RMON, SMT, and TRMAC.

Generic domains are represented using a collection of filters. You create and update this file using the Domain Editor application. Domain names you specify can be up to 8 characters. You can define up to 200 domains in this file.

# #List of all Domains (File: domain.lst). # #Name Type Family Param Protocol Dir Info / Filter List #---- -------- ------ ---- ------- ----------- ------------ # ARP Protocol DLC NET 0.1 1.0.0.1 0.0.8.6 ATALK Protocol ATALK NET 0.0 1.0.0.1 0.0.128.155 DECDIAG Protocol DLC NET 0.0 0.0.0.1.0.0.96.5 IPX_SNP Protocol IPX NET 0.0.0 0.0.0.3.0.0.129.55

fragent.lst

Specific to a particular installation, this file contains a list of all of the Frame Relay agents definitions (see sample list). Each line within the file defines a unique agent that the TrafficDirector application can access. Agent names you specify can be up to 15 characters. This file is created and updated using the TrafficDirector application.

# #List of all frame-relay agents (File: fragent.lst). # # Read Write Startup Properties #Name IP address IFN Community Community Retry Timeout File Description Topology File #---- ---------- --- --------- --------- ----- ------- ---- ----------- -------- ----------- # Agent1: "204.240.143.102" 1 public public 2 5 "fstartup" "" "FR" "default"

serloc.lst

Available for use at any installation, this file contains a list of Agents/Switches and their SQL servers.

switch.lst

Specific to a particular installation, this file contains a list of defined switches you can use with the TrafficDirector application. Each line within the file defines a unique switch. You create and update this file using various TrafficDirector applications. Each agent in this file represents a switched SNMP agent that the TrafficDirector application can access. A switch is represented by all of its ports, applicable attached dedicated agents, or roving agents. Switch names you specify can be up to 15 characters. To be included in this file, you must first define the switch type (vendor-specific) in the switch.def file. You can define up to 1000 switches in this file.

domtree.inf

Available for use at any installation, this file lists the domain names of the parent-child relationships that display when you start the Protocol Zoom application. You can edit this file using any ASCII text editor. If you add a domain name to this file, no activity is reported unless you have defined the domain with the Domain Editor application, and installed it on an agent using Configuration Manager. You use the domtree.inf utility to create a protocol destination report.

pvartrap.inf

Specific to a particular installation, this file contains definitions for MIB variables whose trap characteristics should be modified by Trap Manager. Each line within the file contains a variable name, trap numbers that indicate trap type, rising threshold, and falling threshold, and the sysoid.

dllayer.inf

Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the physical (data link) layer. If necessary, you can edit this file with an ASCII text editor.

nllayer.inf

Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the network layer. If necessary, you can edit this file with an ASCII text editor.

allayer1.inf

Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the transport layer. If necessary, you can edit this file with an ASCII text editor.

allayer2.inf

Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the session layer. If necessary, you can edit this file using an ASCII text editor.

macaddr.nam

Specific to a particular installation, this file contains unique MAC address-to-name mapping information. Each line within the file contains a MAC address and the corresponding name you have defined for a host. You can create this file by using an ASCII text editor. You can specify name mappings for up to 4096 MAC addresses in this file as long as sufficient memory is available.

vendorid.nam

Available for use at any installation, this file contains unique vendor ID-to-name mapping information. Each line within the file contains a vendor name and the corresponding vendor ID. The limit on the number of entries is 4096. Do not edit this file.

vlan.nam

Specific to each application, this file contains unique VLAN (Virtual LAN) to name mapping information. Each line within the file contains a VLAN ID and the corresponding VLAN name you have defined. You can create this file by using an ASCII text editor. You can specify up to 500 VLAN IDs and names in this file.

switch.def

Available for use at any installation, this file contains a list of switch vendors that the TrafficDirector application supports. Each line in the file defines a vendor-specific switch, and information about whether the switch contains any RMON support. You can define up to 100 switch types in this file. Do not edit this file, as it contains critical data.

default.dvp

Available for use at any installation, this file contains unique agent-domain configuration parameters. See Table C-4.

filtername.fil

Available for use at any installation, this file contains parameters set for a specific filter. This file name is derived from the first 15 characters of the filter name. The number of lines in this file depends upon the parameters you specify for the filter when you create it using the Filter Editor application. To edit an x.fil file, you can use a text editor, or edit a filter definition through the Filter Editor application. Each filter you define must also have a corresponding x.fil file. You can specify up to 200 filters in the TrafficDirector database.

frame-relay- agent-name.frp

Specific to a particular installation, this file contains a listing of DLCI numbers and the CIR definition for a specific Frame Relay agent. This file name is derived from the first 15 characters of the Frame Relay agent name. The number of lines in this file equals the number of discovered DLCI ports. The TrafficDirector application automatically creates this file, if it is not already present when you use either the TrafficDirector application (before you launch Traffic Monitor for a frame relay agent), Domain Manager, or the dvlearn command-line tool. You can also create this file an ASCII text editor, or build it incrementally by adding Frame Relay agents using Configuration Manager.

mibname.mib

Available for use at any installation, this file contains variable names and corresponding object ID information. Each line within the file contains a variable name and the corresponding object ID (oid). This file name is derived from the first 15 characters of the MIB name. The number of lines in this file equals the number of variables in the MIB. The TrafficDirector application includes several x.mib files.
Note *.mib files are created when MIB/RFC is compiled with a standard MIB compiler; this means that x.mib files do not contain comment lines or headers. This is an important distinction, because other configuration files that are created do contain comment lines and headers.

routername.rtp

Specific to a particular installation, this file contains unique logical router name-to-interface number mapping. Each line within the file contains interface number and the corresponding name you have defined for the router. This file name is derived from the first 15 characters of the corresponding agent name. You can specify interface-to-name mappings for up to 1000 routers in this file.

switchname.swp

Contains a list of port names, port numbers, interface numbers, slot numbers, virtual interface numbers, interface types, and interface speeds for a specific switch. This file name is derived from the first 15 characters of the switch name. The number of lines in this file equals the number of discovered ports. The TrafficDirector application discovers Ethernet, Fast Ethernet, and Token Ring ports, and automatically creates this file when you use the TrafficDirector Learn function (before you start Traffic Monitor for a defined switch), Domain Manager, or the dvlearn command-line utility. To be included in this file, you must first define the switch in the switch.lst file. Each switch listed in the switch.lst file must also have a corresponding x.swp file.

switchname.vln

Contains a list of VLANs configured in the switch. The TrafficDirector application creates this file for Cisco Catalyst 5000-series switches when you add the switch.

# Sample switch_name.vln file # # List of switch vlans for switch: name_of_switch, type: # # switch_type # # Vlan Name Vlan Number # -------------- -------------- "myVlan_1000" 1 "yourVlan_1001" 2 "ourVlan_1002" 3

**Table C-1: Configuration Files in $NSHOME/usr Directory**
File Name	Description
appgrp.cfg	Available for use at any installation, this file contains a list of the parent-child relationships between a domain group and individual protocols at the TrafficDirector Application level. You can edit this file with an ASCII text editor.
autorpt.cfg	Available for use at any installation, this file contains the list of reports scheduled to run automatically. You can edit this file with an ASCII text editor or build it incrementally using the Trend Reporter application.
dbupdate.cfg	Available for use at any installation, this file contains the detail and summary aging intervals and thresholds used for Protocol, Segment, Host, Conversation, Proxy SNMP, IP Ping, ALL NL, ALL AL, ART, ART SUMM, Host Threshold, Conversation Threshold, Baseline A, Baseline B, and Hour Range. You can edit this file with an ASCII text editor or the Config Rollup application. The dbupdate configuration file contains the following aging parameters:
Detail Aging---Shows the number of days that information ages before the Aging daemon determines it to be obsolete and deletes it from the details table. Detail aging must be greater than one day. The default value for protocol and segment statistics from the detail table is 31 days; for host, conversation, IP Ping, Proxy SNMP, ALL NL, ALL AL, ART, and ART Server, it is 7 days.
Summary Aging---Shows the number of days that information ages before the Aging daemon determines it to be obsolete and deletes it from the daily table. Daily aging must be greater than one day. The default value for protocol and segment statistics from the Summary (Daily) table is 366 days; for host, conversation, IP Ping, Proxy SNMP, ALL NL, ALL AL, ART, and ART Server, it is 31 days.
dbupdate.cfg (`continued`)	Host Threshold---Configures the minimum utilization percentage that a host (combined inbound and outbound utilization) must meet before it is included in the host details table. The Snapshot daemon compares a host segment utilization percentage to this number and logs data to the host bin details binary file only if the utilization percentage meets or exceeds this value.
Baseline Time Range---You can configure each database table to participate in the baseline time-range. Baseline A and Baseline B time range data is maintained (protected against purge) so that baseline data will be available at report time.
By default, all database tables are enabled to participate in the baseline time range. However, both Baseline A and Baseline B time ranges default to None. When you set the Baseline A or Baseline B time range (enabled, other than None), all database tables are initially set enabled. This may result in logging more data than you expect.
dept.cfg	Available for use at any installation, this file contains a list of the Department/Alias name mapping for Trend Reporter Billing Reports. You can edit this file using an ASCII text editor. Cisco Systems recommends that you create a new file for each different department list you want for Trend Reporter Billing Reports.
Host Address	Department/ Alias Name	Address Family
5.128 6.129 00-0A-C9-08-14-98 204.204.244.100 0002.00aa08 0002.a0	Eng-A Eng-D Eng-MAC Eng-IP Eng-IPX Eng-V	ATALK DECnet DLC IP IPX VINES
dlciinfo.cfg	Available for use at any installation, this file contains an example of a properly formatted configuration file containing DLCI information to be downloaded to an agent using the dvftp command-line utility.
ipdfilt.cfg	Available for use at any installation, this file contains an example of a properly formatted configuration file containing data reduction information to de downloaded to an agent using the dvftp command-line utility.
nsconfig.cfg	Available for use at any installation, this file contains the maximum number of: host MAC addresses allowed in the macaddr.nam file and vendors allowed in the vendorid.nam file. You can edit this file with an ASCII text editor. Sufficient memory must be available if you are increasing the number of hosts or vendors. The default limit on the number of entries in each file is 4096.
protogrp.cfg	Available for use at any installation, this file contains a list of the parent-child relationships between a domain group and individual protocols at the TrafficDirector Protocol level. You can edit this file with an ASCII text editor.
tariff.cfg	Available for use at any installation, this file (see sample) contains a billing rate for Trend Reporter Billing Reports. You can edit this file using an ASCII text editor. However, it is recommended that you create a new file for each different billing rate you want for Trend Reporter Billing Reports using the vi copy feature. # ----------------------- # Rate in US $ per 1KByte # ----------------------- # Max precision #-rate 0.1234567 # Default #-rate 0.01 Default if file or -rate not found
agent.lst	Specific to a particular installation, this file contains agent definitions. Each line within the file defines a unique SNMP agent that the TrafficDirector application can access. Agent names you specify can be up to 15 characters. You create and update this file through using the TrafficDirector application, although you can edit the file directly. You can define up to 1000 agents in this file.
agegroup.lst	Specific to a particular installation, this file contains agent group definitions. Each line within the file defines a unique group of SNMP agents that the TrafficDirector application can access. To be included in this file, you must first set up the agent definitions in the agent.lst file. Agent group names you specify can be up to 15 characters. You create and update this file through the TrafficDirector application, although you can edit the file directly. You can define up to 100 agent groups in this file; each agent group can contain up to 60 agents.
domain.lst	Available for use at any installation, this file contains domain definitions (see partial sample list). Each line within the file defines a unique domain which represents a characterization of traffic. The TrafficDirector application supports two types of domains: Protocol domains---Provide the means to classify network traffic by protocols that reside in the top five layers of the OSI model (network layer through application layer; for example, IP, IPX, TCP, and TFTP). Generic domains---Provide a means to classify network traffic by protocols that reside in the data link layer of the OSI model (layer 2). For example, RMON, SMT, and TRMAC. Generic domains are represented using a collection of filters. You create and update this file using the Domain Editor application. Domain names you specify can be up to 8 characters. You can define up to 200 domains in this file. # #List of all Domains (File: domain.lst). # #Name Type Family Param Protocol Dir Info / Filter List #---- -------- ------ ---- ------- ----------- ------------ # ARP Protocol DLC NET 0.1 1.0.0.1 0.0.8.6 ATALK Protocol ATALK NET 0.0 1.0.0.1 0.0.128.155 DECDIAG Protocol DLC NET 0.0 0.0.0.1.0.0.96.5 IPX_SNP Protocol IPX NET 0.0.0 0.0.0.3.0.0.129.55
fragent.lst	Specific to a particular installation, this file contains a list of all of the Frame Relay agents definitions (see sample list). Each line within the file defines a unique agent that the TrafficDirector application can access. Agent names you specify can be up to 15 characters. This file is created and updated using the TrafficDirector application. # #List of all frame-relay agents (File: fragent.lst). # # Read Write Startup Properties #Name IP address IFN Community Community Retry Timeout File Description Topology File #---- ---------- --- --------- --------- ----- ------- ---- ----------- -------- ----------- # Agent1: "204.240.143.102" 1 public public 2 5 "fstartup" "" "FR" "default"
serloc.lst	Available for use at any installation, this file contains a list of Agents/Switches and their SQL servers.
switch.lst	Specific to a particular installation, this file contains a list of defined switches you can use with the TrafficDirector application. Each line within the file defines a unique switch. You create and update this file using various TrafficDirector applications. Each agent in this file represents a switched SNMP agent that the TrafficDirector application can access. A switch is represented by all of its ports, applicable attached dedicated agents, or roving agents. Switch names you specify can be up to 15 characters. To be included in this file, you must first define the switch type (vendor-specific) in the switch.def file. You can define up to 1000 switches in this file.
domtree.inf	Available for use at any installation, this file lists the domain names of the parent-child relationships that display when you start the Protocol Zoom application. You can edit this file using any ASCII text editor. If you add a domain name to this file, no activity is reported unless you have defined the domain with the Domain Editor application, and installed it on an agent using Configuration Manager. You use the domtree.inf utility to create a protocol destination report.
pvartrap.inf	Specific to a particular installation, this file contains definitions for MIB variables whose trap characteristics should be modified by Trap Manager. Each line within the file contains a variable name, trap numbers that indicate trap type, rising threshold, and falling threshold, and the sysoid.
dllayer.inf	Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the physical (data link) layer. If necessary, you can edit this file with an ASCII text editor.
nllayer.inf	Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the network layer. If necessary, you can edit this file with an ASCII text editor.
allayer1.inf	Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the transport layer. If necessary, you can edit this file with an ASCII text editor.
allayer2.inf	Available for use at any installation, this file contains protocol name and ID information. Each line within the file contains a protocol name and the associated ID number. This file, used only in the Domain Editor application, specifies the available protocols you can select for the session layer. If necessary, you can edit this file using an ASCII text editor.
macaddr.nam	Specific to a particular installation, this file contains unique MAC address-to-name mapping information. Each line within the file contains a MAC address and the corresponding name you have defined for a host. You can create this file by using an ASCII text editor. You can specify name mappings for up to 4096 MAC addresses in this file as long as sufficient memory is available.
vendorid.nam	Available for use at any installation, this file contains unique vendor ID-to-name mapping information. Each line within the file contains a vendor name and the corresponding vendor ID. The limit on the number of entries is 4096. `Do not edit this file.`
vlan.nam	Specific to each application, this file contains unique VLAN (Virtual LAN) to name mapping information. Each line within the file contains a VLAN ID and the corresponding VLAN name you have defined. You can create this file by using an ASCII text editor. You can specify up to 500 VLAN IDs and names in this file.
switch.def	Available for use at any installation, this file contains a list of switch vendors that the TrafficDirector application supports. Each line in the file defines a vendor-specific switch, and information about whether the switch contains any RMON support. You can define up to 100 switch types in this file. `Do not edit this file,` as it contains critical data.
default.dvp	Available for use at any installation, this file contains unique agent-domain configuration parameters. See Table C-4.
`filtername`.fil	Available for use at any installation, this file contains parameters set for a specific filter. This file name is derived from the first 15 characters of the filter name. The number of lines in this file depends upon the parameters you specify for the filter when you create it using the Filter Editor application. To edit an x.fil file, you can use a text editor, or edit a filter definition through the Filter Editor application. Each filter you define must also have a corresponding x.fil file. You can specify up to 200 filters in the TrafficDirector database.
`frame-relay- agent-name`.frp	Specific to a particular installation, this file contains a listing of DLCI numbers and the CIR definition for a specific Frame Relay agent. This file name is derived from the first 15 characters of the Frame Relay agent name. The number of lines in this file equals the number of discovered DLCI ports. The TrafficDirector application automatically creates this file, if it is not already present when you use either the TrafficDirector application (before you launch Traffic Monitor for a frame relay agent), Domain Manager, or the dvlearn command-line tool. You can also create this file an ASCII text editor, or build it incrementally by adding Frame Relay agents using Configuration Manager.
`mibname`.mib	Available for use at any installation, this file contains variable names and corresponding object ID information. Each line within the file contains a variable name and the corresponding object ID (oid). This file name is derived from the first 15 characters of the MIB name. The number of lines in this file equals the number of variables in the MIB. The TrafficDirector application includes several x.mib files. Note *.mib files are created when MIB/RFC is compiled with a standard MIB compiler; this means that x.mib files do not contain comment lines or headers. This is an important distinction, because other configuration files that are created do contain comment lines and headers.
`routername`.rtp	Specific to a particular installation, this file contains unique logical router name-to-interface number mapping. Each line within the file contains interface number and the corresponding name you have defined for the router. This file name is derived from the first 15 characters of the corresponding agent name. You can specify interface-to-name mappings for up to 1000 routers in this file.
`switchname`.swp	Contains a list of port names, port numbers, interface numbers, slot numbers, virtual interface numbers, interface types, and interface speeds for a specific switch. This file name is derived from the first 15 characters of the switch name. The number of lines in this file equals the number of discovered ports. The TrafficDirector application discovers Ethernet, Fast Ethernet, and Token Ring ports, and automatically creates this file when you use the TrafficDirector Learn function (before you start Traffic Monitor for a defined switch), Domain Manager, or the dvlearn command-line utility. To be included in this file, you must first define the switch in the switch.lst file. Each switch listed in the switch.lst file must also have a corresponding x.swp file.
`switchname`.vln	Contains a list of VLANs configured in the switch. The TrafficDirector application creates this file for Cisco Catalyst 5000-series switches when you add the switch. # Sample switch_name.vln file # # List of switch vlans for switch: name_of_switch, type: # # switch_type # # Vlan Name Vlan Number # -------------- -------------- "myVlan_1000" 1 "yourVlan_1001" 2 "ourVlan_1002" 3

SQL Database File Parameters

The sqldb.dvp file contains some of the parameters used for configuring logging.

Table C-2 summarizes the information contained in this file.

Table C-2: Logging Parameters in sqldb.dvp File
Tag Default
Value Description

Trend_Reporter_logging_on

yes

Turns logging on.

hide_dbsnapdm_icon

yes

Hides snapshot daemon (dbsnapd) icons.

TopNHosts

50

Threshold for hosts in the detail table.

TopNConversations

50

Threshold for conversations in the detail table.

switch_host_daemon

off

host_conv snapshot daemon for switches.

min_disk_space

10

Minimum disk space (10 Mb) needed for logging to continue.

num_interval_for_skipping_logs

5

Number of skipped logging intervals allowed before binary file data gets discarded.

**Table C-2: Logging Parameters in sqldb.dvp File**
Tag	Default Value	Description
Trend_Reporter_logging_on	yes	Turns logging on.
hide_dbsnapdm_icon	yes	Hides snapshot daemon (dbsnapd) icons.
TopNHosts	50	Threshold for hosts in the detail table.
TopNConversations	50	Threshold for conversations in the detail table.
switch_host_daemon	off	host_conv snapshot daemon for switches.
min_disk_space	10	Minimum disk space (10 Mb) needed for logging to continue.
num_interval_for_skipping_logs	5	Number of skipped logging intervals allowed before binary file data gets discarded.

The num_interval_for_skipping_logs tag specifies the number of logging intervals that the msqld/dbextrad daemon has to migrate the detail binary files to the database. By default, this value is set to five intervals.

For example, if you are logging RMON domain every 1 minute, and you start logging at 10:00 a.m., the msqld/dbextrad daemon has until 10:05 to migrate the file created at 10:00 a.m. If the daemon fails to migrate the file before 10:05, the logging at 10:05 is discarded.

Limits and Constraints

Table C-3 and Table C-4 describe the numerical limitations imposed by the TrafficDirector application.

These limits are divided into two groups:

Hard limits---Cannot be changed without a modification to the TrafficDirector source code.
Configurable limits---Can be modified by the user by editing one or more configuration files.

Table C-3: Hard Limits
Name Limitation Description

NSHOME length

64

Max string length of NSHOME environment variable.

Agent name

1 to 15 alphanumeric characters plus
underscore (_)
and hyphen (-)

Name of an agent, agent group, switch, or Frame Relay agent set using Configuration Manager.
Note All 15 characters are significant. (Prior to this release, only the first 8 characters were significant.)

Domain name

1 to 15 alphanumeric characters plus
underscore (_)
and hyphen (-)

Name of domain.

Domains

1000

Maximum number of domains (Domain Editor).

Domains learned

512

Maximum number of domains per interface.

Community string

31

Maximum length of community string.

Resource variable

39

Maximum length of resource variable.

Agents

1000

Maximum number of agents.

Frame Relay Agents

1000

Maximum number of Frame Relay agents.

DLCIs

1000

Maximum number of DLCIs per Frame Relay agent.

Switch Agents

1000

Maximum number of switches.

Switch Ports

1000

Maximum number of switch ports per switch.

Agent Groups

500

Maximum number of agent groups.

Agents per Group

60

Maximum umber of agents in an agent group.

Net <-> MAC
mappings

4096

Maximum number of Net to MAC address mappings.

Agents per Switch

4

Maximum number of attached agent for switch.

ifn and PVC

4096

Maximum number of ifn and PVCs in database.

Router Interfaces

4096

Maximum number of router interfaces.

VLANs

1024

Maximum number of VLANs.

Filters

500

Maximum number of filters (Filter Editor).

Filter formats

100

Maximum number of filter formats (Filter Editor).

DLCI/VLAN names

1024

Number of entries in dlci.nam, and vlan.nam.

Max Switch types

50

Maximum number of switch types.

Password

1 to 10 alphanumeric characters

Password for admin (alphanumeric).

Host Zoom (text)
hosts

256

Number of Hosts that can be shown in the window.

Host Zoom (graph)
data points

16

Max points in each dataset. Tunable, limited by display resolution.

Host Zoom (graph)
hosts

256

Max Matrix Entries to retrieve. Tunable, limited by display resolution.

Conv History
data points

61

Limited by the resolution of display. These are maximum points on the x axis.

TopN Talkers
max hosts

4000

Maximum hosts allowed in the application.

TopN Talkers
disp hosts

20

Maximum hosts to display. This limit comes from the graph display; the graph looks cluttered with a number higher than this.

All Conv
max conversations

512

Maximum conversations allowed for the application.

Filters per data
capture

8

Maximum number of filters per data capture.

Filters per generic domain

8

Maximum number of filters per generic domain.

Data captures
per probe

16

Maximum simultaneous data captures per SwitchProbe device.

Proto/App Monitor
Proto Zoom max domains

20

Maximum number of domains that can be monitored, including parent domain group.

Segment Detail
max buckets

60

Maximum number of buckets displayed in Segment Detail app.

Proxy Ping

64

\QMaximum number of proxy ping entries per SwitchProbe device.

Proxy SNMP

64

Maximum number of proxy SNMP entries per SwitchProbe device.

Alerts

4000

Maximum number of alerts per day (Alert Monitor).

Traps per interface

8

Maximum number of traps per interface.
Note 7 for ifn 1.

Traps per resource variable

2

Maximum number of traps per resource variable.

Resource MIB files

100

Maximum number of resource MIB files.

Remote logins

2

Maximum number of remote logins per SwitchProbe device.

Trap destinations

8

Maximum number of trap destinations per SwitchProbe device.

**Table C-3: Hard Limits**
Name	Limitation	Description
NSHOME length	64	Max string length of NSHOME environment variable.
Agent name	1 to 15 alphanumeric characters plus underscore (_) and hyphen (-)	Name of an agent, agent group, switch, or Frame Relay agent set using Configuration Manager. Note All 15 characters are significant. (Prior to this release, only the first 8 characters were significant.)
Domain name	1 to 15 alphanumeric characters plus underscore (_) and hyphen (-)	Name of domain.
Domains	1000	Maximum number of domains (Domain Editor).
Domains learned	512	Maximum number of domains per interface.
Community string	31	Maximum length of community string.
Resource variable	39	Maximum length of resource variable.
Agents	1000	Maximum number of agents.
Frame Relay Agents	1000	Maximum number of Frame Relay agents.
DLCIs	1000	Maximum number of DLCIs per Frame Relay agent.
Switch Agents	1000	Maximum number of switches.
Switch Ports	1000	Maximum number of switch ports per switch.
Agent Groups	500	Maximum number of agent groups.
Agents per Group	60	Maximum umber of agents in an agent group.
Net <-> MAC mappings	4096	Maximum number of Net to MAC address mappings.
Agents per Switch	4	Maximum number of attached agent for switch.
ifn and PVC	4096	Maximum number of ifn and PVCs in database.
Router Interfaces	4096	Maximum number of router interfaces.
VLANs	1024	Maximum number of VLANs.
Filters	500	Maximum number of filters (Filter Editor).
Filter formats	100	Maximum number of filter formats (Filter Editor).
DLCI/VLAN names	1024	Number of entries in dlci.nam, and vlan.nam.
Max Switch types	50	Maximum number of switch types.
Password	1 to 10 alphanumeric characters	Password for admin (alphanumeric).
Host Zoom (text) hosts	256	Number of Hosts that can be shown in the window.
Host Zoom (graph) data points	16	Max points in each dataset. Tunable, limited by display resolution.
Host Zoom (graph) hosts	256	Max Matrix Entries to retrieve. Tunable, limited by display resolution.
Conv History data points	61	Limited by the resolution of display. These are maximum points on the x axis.
TopN Talkers max hosts	4000	Maximum hosts allowed in the application.
TopN Talkers disp hosts	20	Maximum hosts to display. This limit comes from the graph display; the graph looks cluttered with a number higher than this.
All Conv max conversations	512	Maximum conversations allowed for the application.
Filters per data capture	8	Maximum number of filters per data capture.
Filters per generic domain	8	Maximum number of filters per generic domain.
Data captures per probe	16	Maximum simultaneous data captures per SwitchProbe device.
Proto/App Monitor Proto Zoom max domains	20	Maximum number of domains that can be monitored, including parent domain group.
Segment Detail max buckets	60	Maximum number of buckets displayed in Segment Detail app.
Proxy Ping	64	\QMaximum number of proxy ping entries per SwitchProbe device.
Proxy SNMP	64	Maximum number of proxy SNMP entries per SwitchProbe device.
Alerts	4000	Maximum number of alerts per day (Alert Monitor).
Traps per interface	8	Maximum number of traps per interface. Note 7 for ifn 1.
Traps per resource variable	2	Maximum number of traps per resource variable.
Resource MIB files	100	Maximum number of resource MIB files.
Remote logins	2	Maximum number of remote logins per SwitchProbe device.
Trap destinations	8	Maximum number of trap destinations per SwitchProbe device.

Table C-4: Configurable Limits in $NSHOME/usr/default.dvp
Name Default
Value Description

probe-read-community

public

Default read community for SwitchProbe device.

probe-write-community

public

Default write community for SwitchProbe device.

switch-read-community

public

Default read community for switch.

switch-write-community

public

Default write community for switch.

cm-prop-file-default

fw45prop

CM Prop File (Add Agent default).

short-history-buckets

50

Number of short-term history buckets.

short-history-interval

30

Short-term history interval in seconds.

long-history-buckets

50

Number of long-term history buckets.

long-history-interval

600

Long-term history interval in seconds.

topn-hosts

10

Number of top hosts.

topn-convs

10

Number of top conversations.

nl-hosts

1000

Number of Network Hosts.

al-hosts

10000

Number of Application Hosts.

nl-convs

2000

Number of Network Conversations.

al-convs

10000

Number of Application Conversation.

net-to-mac-hosts

1000

Number of Network to MAC addresses.

enable-fast-upload:

yes

Yes/No.

enable-dte-dce

yes

Yes/No.

default-printer

lp

Default printer.

lines-per-page

60

Lines per page while printing or writing to a file.

snmp-trap-port

162

Additional Trap port.

default-domain

IP

Default domain for All/TopN Talkers.

enable-start-end-util-calc

1

0---Util by samples
1---Util by end-start.

map-conversations

0

0---Src->Dst
1---Support A<->B.

inc-dr-to-show-500-ds

1

0---Truncate
1---Inc Display Resolution.

max-hosts

5000

Maximum number hosts processed by host-based applications (TopN Talkers, All Talkers).

max-convs:

10000

Maximum number of conversations processed by conversation-based applications (All Conversations).

max-arts

10000

Used in bulk retrieval.

snapshot-get-bulk

yes

Yes/No.

host-conv-get-bulk

yes

Yes/No.

max-trafmon-agents

32

Maximum number of agents/ports/DLCIs/VLANSs to display for Traffic Monitor and SMON Monitor applications. Corresponds to N for TopN ports in Traffic Monitor.

landscape-reports

0

1 for forced landscape printing.

topn-ratebase

1

Ratebase for topn AL/NL.

topn-duration

30

Duration for topn AL/NL (in minutes).

art-duration:

30

ART report time duration (in minutes).

art-rsptime1

25

ART response-time bucket 1 (in milliseconds).

art-rsptime2

50

ART response-time bucket 2 (in milliseconds).

art-rsptime3

100

ART response-time bucket 3 (in milliseconds).

art-rsptime4

200

ART response-time bucket 4 (in milliseconds).

art-rsptime5

400

ART response-time bucket 5 (in milliseconds).

art-rsptime6

800

ART response-time bucket 6 (in milliseconds).

art-rsptimeout

1000

ART response-timeout (in milliseconds).

art-rsptimeout

1000

ART response-timeout (in milliseconds).

art-rsptimeout

1000

ART response-timeout (in milliseconds).

uhist-samples

50

User History samples.

uhist-interval

30

User History interval (in minutes).

summary-util-by-24hours

0

#1 for summary by 24 hours.

Name	Default Value	Description
probe-read-community	public	Default read community for SwitchProbe device.
probe-write-community	public	Default write community for SwitchProbe device.
switch-read-community	public	Default read community for switch.
switch-write-community	public	Default write community for switch.
cm-prop-file-default	fw45prop	CM Prop File (Add Agent default).
short-history-buckets	50	Number of short-term history buckets.
short-history-interval	30	Short-term history interval in seconds.
long-history-buckets	50	Number of long-term history buckets.
long-history-interval	600	Long-term history interval in seconds.
topn-hosts	10	Number of top hosts.
topn-convs	10	Number of top conversations.
nl-hosts	1000	Number of Network Hosts.
al-hosts	10000	Number of Application Hosts.
nl-convs	2000	Number of Network Conversations.
al-convs	10000	Number of Application Conversation.
net-to-mac-hosts	1000	Number of Network to MAC addresses.
enable-fast-upload:	yes	Yes/No.
enable-dte-dce	yes	Yes/No.
default-printer	lp	Default printer.
lines-per-page	60	Lines per page while printing or writing to a file.
snmp-trap-port	162	Additional Trap port.
default-domain	IP	Default domain for All/TopN Talkers.
enable-start-end-util-calc	1	0---Util by samples 1---Util by end-start.
map-conversations	0	0---Src->Dst 1---Support A<->B.
inc-dr-to-show-500-ds	1	0---Truncate 1---Inc Display Resolution.
max-hosts	5000	Maximum number hosts processed by host-based applications (TopN Talkers, All Talkers).
max-convs:	10000	Maximum number of conversations processed by conversation-based applications (All Conversations).
max-arts	10000	Used in bulk retrieval.
snapshot-get-bulk	yes	Yes/No.
host-conv-get-bulk	yes	Yes/No.
max-trafmon-agents	32	Maximum number of agents/ports/DLCIs/VLANSs to display for Traffic Monitor and SMON Monitor applications. Corresponds to N for TopN ports in Traffic Monitor.
landscape-reports	0	1 for forced landscape printing.
topn-ratebase	1	Ratebase for topn AL/NL.
topn-duration	30	Duration for topn AL/NL (in minutes).
art-duration:	30	ART report time duration (in minutes).
art-rsptime1	25	ART response-time bucket 1 (in milliseconds).
art-rsptime2	50	ART response-time bucket 2 (in milliseconds).
art-rsptime3	100	ART response-time bucket 3 (in milliseconds).
art-rsptime4	200	ART response-time bucket 4 (in milliseconds).
art-rsptime5	400	ART response-time bucket 5 (in milliseconds).
art-rsptime6	800	ART response-time bucket 6 (in milliseconds).
art-rsptimeout	1000	ART response-timeout (in milliseconds).
art-rsptimeout	1000	ART response-timeout (in milliseconds).
art-rsptimeout	1000	ART response-timeout (in milliseconds).
uhist-samples	50	User History samples.
uhist-interval	30	User History interval (in minutes).
summary-util-by-24hours	0	#1 for summary by 24 hours.

Table of Contents