Amer Networks E5Web GUI - Manual (Page 56)

File type Upload possible Download possible
System Backup (full.bak) Yes (also with WebUI) Yes (also with WebUI)
Firmware upgrades Yes No
Licenses (license.lic) Yes (also with WebUI) No
Certificates Yes No
SSH public keys Yes No
Web auth banner files Yes Yes
Web content filter banner files Yes Yes
cOS Core File organization
cOS Core maintains a simple 2 level directory structure which consists of the top level root and a
number of sub-directories. However, these "directories" such as sshlclientkey should be more
correctly thought of as object types. All the files stored in the cOS Core root as well as all the
object types can be displayed using the CLI command ls.
The resulting output is shown below:
Device:/> ls
HTTPALGBanners/
HTTPAuthBanners/
certificate/
config.bak
full.bak
license.lic
script/
sshclientkey/
Apart from the individual files, the objects types listed are:
• HTTPALGBanners/ - The banner files for user authentication HTML. Uploading these is
described further in Section 6.3.4.4, “Customizing WCF HTML Pages”.
• HTTPAuthBanner/ - The banner files for HTML ALG dynamic content filtering. Uploading these
is described further in Section 6.3.4.4, “Customizing WCF HTML Pages”.
• certificate/ - The object type for all digital certificates.
• script/ - The object type for all CLI scripts. Scripts are described further in Section 2.1.5, “CLI
Scripts”.
• sshclientkey/ - The SSH client key object type.
Examples of Uploading and Downloading
In some cases, a file is located in the cOS Core root. The license file (license.lic) falls into this
category, as well as configuration backup files (config.bak) and the complete system backup files
(full.bak).
When uploading, these files contain a unique header which identifies what they are. cOS Core
checks this header and ensures the file is stored only in the root (all files do not have a header).
If an administrator username is admin1 and the IPv4 address of the Clavister Security Gateway is
10.5.62.11 then to upload a configuration backup, the SCP command would be:
> scp config.bak [email protected]:
Chapter 2: Management and Maintenance
56