7: Services
SecureLinx SLC User Guide
57
diaglog
<off|error|warning|info|debug>
genlog
<off|error|warning|info|debug>
includesyslog <enable|
disable
>
location <Physical Location>
netlog <off|error|warning|info|debug>
nms <IP Address or Name>
portssh <TCP Port>
rocommunity <Read-Only Community Name>
rwcommunity <Read-Write Community Name>
servlog
<off|error|warning|info|debug>
smtpserver <IP Address or Hostname>
snmp
<enable|
disable
>
ssh <
enable
|disable>
syslogserver1 <IP Address or Name>
syslogserver2 <IP Address or Name>
telnet
<enable|
disable
>
timeoutssh
<
disable
or 1-30>
timeouttelnet <
disable
or 1-30>
traps <enable|
disable
>
v1ssh <
enable
|disable>
v3password <Password for v3 auth>
v3user <User for v3 auth>
webssh <enable|
disable
>
webtelnet <enable|
disable
>
To view current services:
show services
NFS and SMB/CIFS
Use the NFS & SMB/CIFS page if you want to save configuration and logging data onto a
remote NFS server, or export configuration and logging data by means of an exported
CIFS share.
Mounting an NFS shared directory on a remote network server
onto a local SLC
directory
enables the SLC to store device port logging data on that network server. This
configuration avoids possible limitations in the amount of disk space on the SLC available
for the
logging
file(s). You may also save SLC configurations on the network server.
Similarly, use SMB/CIFS (Server Message Block/Common Internet File System),
Microsoft’s file-sharing protocol, to export a directory on the SLC as an SMB/CIFS share.
The SLC exports a single read-write CIFS share called "public,
"
with two subdirectories:
The
logs
directory, which contains the system logs and the device port local
buffers (see
System Logs
on page 145) and is read-only.