What are the files in the /cfg directory?

book

Article ID: 167159

calendar_today

Updated On:

Products

PacketShaper

Issue/Introduction

These files store the PacketShaper/AppVantage traffic configuration.

Resolution

All the classes, partitions, and policies are stored in a binary file format and are not human readable. The configuration files are in the cfg directory on the unit's flash drive (9.256/cfg). The names of the configuration files differ slightly for each PacketWise version.

PacketWise 4.x

traffic.cfg  Contains your current working traffic tree configuration, including all classes, class IDs, partitions, and policies.

measure.cfg  Stores your current measurement engine settings.

settings.cfg  Stores your basic setup configuration, such as IP address and passwords.

basic.cfg  Stores the unit's factory settings, such as serial number and software keys. This file can never be used on another unit.

---------------------------

PacketWise 5.0/5.1

traffic.cfg  Contains your current working traffic tree configuration, including all classes, class IDs, partitions, policies, host lists, and events.

measure.cfg  Stores your current measurement engine settings.

settings.cfg  Stores your basic setup configuration, such as IP address and password.

basic.cfg  Stores the unit's factory settings, such as serial number and software keys. This file can never be used on another unit.

config.ldi  Stores the host list configuration.

---------------------------

PacketWise 5.2 and up

config.ldi  Contains your current working traffic tree configuration, including all classes, class IDs, partitions, policies, host lists, and events. Also contains all sharable configuration settings such as passwords, site router, SNMP, email, SNTP, and Syslog.

measure.cfg  Stores your current measurement engine settings.

settings.cfg  Stores your basic setup configuration, such as IP address, DNS server, NIC information, and domain name.

basic.cfg  Stores the unit's factory settings, such as serial number and software keys. This file can never be used on another unit.

---------------------------

In addition to the configuration files listed above, there are files with the following extensions:

.sav  The .sav file is created when you upgrade to a new "major" release version. When any significant changes are made to the file structure of the .cfg file, the old version is saved as .sav while its contents are converted to the new format and saved as the new .cfg file. Examples: traffic.sav, measure.sav, settings.sav, basic.sav.

.new  This is a temporary file. Any time a change is made to the configuration (via the browser or command-line interface), the new working configuration is saved to the .new file. The file is then checked for integrity and is renamed to replace the .cfg file. Examples: traffic.new, measure.new settings.new, basic.new.

.old  This file is created immediately after the process above (see .new). Just before the .cfg file is replaced by the .new file, the old pre-change configuration is saved with a .old extension. Examples: traffic.old, measure.old, settings.old, basic.old.

.bad  This file is created in the event that the unit fails to load a .cfg file. This process would occur at startup if the integrity check for the file fails. Because the unit cannot operate with a corrupted configuration, the damaged file is renamed with a .bad extension. A new .cfg file is then created with the default blank traffic tree. Example: traffic.bad, measure.bad, settings.bad, basic.bad.

 

Note:  While this information is provided for your convenience, under no circumstances should you attempt