User's Manual 4. Device Initialization & Configuration Files
Version 6.6 29 MediaPack Series
Items_Table 0 = Computer, 678678, 6;
Items_Table 6 = Computer-page, 127979, 9;
Items_Table 2 = Computer-pad, 111111, $$;
[\Items_Table]
4.4.1.2.2 Secret Tables
A table is defined as a secret table if it contains at least one secret data field or if it
depends on such a table. A secret data field is a field that must not be revealed to the user.
An example of a secret field can be found in an IPSec application. The IPsec tables are
defined as secret tables because the IKE table contains a pre-shared key field, which must
not be revealed. The SPD table depends on the IKE table. Therefore, the SPD table is
defined as a secret table.
There are two major differences between tables and secret tables:
The secret field itself cannot be viewed via SNMP, Web Server or any other tool.
ini File behavior: These tables are never uploaded in the ini File (e.g., 'Get INI-File from
Web'). Instead, there is a commented title that states that the secret table is present at the
blade, and is not to be revealed.
Secret tables are always kept in the blade’s non-volatile memory, and may be over-written
by new tables that should be provided in a new ini File. If a secret table appears in an ini
File, it replaces the current table regardless of its content. The way to delete a secret table
from a blade is, for example, to provide an empty table of that type (with no data lines) as
part of a new ini File. The empty table replaces the previous table in the blade.
4.4.1.2.3 Tables in the Uploaded ini File
Tables are grouped according to the applications they configure.
When uploading the ini file, the policy is to include only tables that belong to applications,
which have been configured. (Dynamic tables of other applications are empty, but static
tables are not.) The trigger for uploading tables is further documented in the applications'
specific sections.
4.4.1.2.4 Secret Tables
A table is defined as a secret table if it contains at least one secret data field or if it
depends on such a table. A secret data field is a field that must not be revealed to the user.
An example of a secret field can be found in an IPSec application. The IPsec tables are
defined as secret tables because the IKE table contains a pre-shared key field, which must
not be revealed. The SPD table depends on the IKE table. Therefore, the SPD table is
defined as a secret table.
There are two major differences between tables and secret tables:
The secret field itself cannot be viewed via SNMP, Web Server or any other tool.
ini File behavior: These tables are never uploaded in the ini File (e.g., 'Get INI-File
from Web'). Instead, there is a commented title that states that the secret table is
present at the blade, and is not to be revealed.
Secret tables are always kept in the blade’s non-volatile memory, and may be over-written
by new tables that should be provided in a new ini File. If a secret table appears in an ini
File, it replaces the current table regardless of its content. The way to delete a secret table
from a blade is, for example, to provide an empty table of that type (with no data lines) as
part of a new ini File. The empty table replaces the previous table in the blade.
To Next Page
Loading...
