Configuration and generated files – Force10 Networks PSeries 100-00055-01 User Manual

Page 61

Advertising
background image

P-Series Installation and Operation Guide, version 2.3.1.2

61

Configuration and Generated Files

Table 9

describes the files that are used or generated by the pnic-Compiler.

Table 9 Configuration and Generated Files

File

Description

Location

pnic_*.bit

Generated after compiling static rules. They
are then renamed and copied to /usr/local/
pnic/firmware. When selecting firmware, the
.bit files are symbolically linked to the
corresponding renamed files in the firmware
directory.

/usr/local/pnic/0

pnic_*.mapping

Generated after compiling static rules. They
are then renamed and copied to /usr/local/
pnic/firmware. When selecting firmware, the
.mapping files are symbolically linked to the
corresponding renamed files in the firmware
directory.

/usr/local/pnic/0

<firmware_filename>.bit

Firmware files for Channel 0 and Channel 1.
They are the renamed .bit files that were
generated after compiling static rules. When
selecting firmware, these are the files to
which the .bit files in /usr/local/pnic/0 are
symbolically linked.

/usr/local/pnic/firmware/
<firmware_filename>

<firmware_filename>.mapping

Firmware files for Channel 0 and Channel 1.
They are the renamed .mapping files that
were generated after compiling static rules.
When selecting firmware, these are the files
to which the .mapping files in /usr/local/pnic/
0
are symbolically linked.

/usr/local/pic/firmware/
<firmware_filename>

pnic_*.bin

Contain compiled dynamic rules for Channel
0 and Channel 1.

/usr/local/pnic/0

pnic_*.custmapping

Contain the capture/forward policies for each
rule on Channel 0 and Channel 1.

/usr/local/pnic/0

rules.custom

Contains dynamic rules written in Snort
syntax.

/usr/local/pnic/0

Advertising