10400589-001 ©2008-14 Overland Storage, Inc. 76
SnapServer / GuardianOS 7.6 Administrator’s Guide 4 - Network Settings
• To connect via a Web browser, enter:
ftp://server_name
(where server_name is the name or IP address of the server)
• For secure FTPS, configure your FTPS client application to use explicit FTPS (such
as, FTPES or “Auth TLS”) and enter the name of the server or IP address.
NOTE: With anonymous login enabled, access to folders is determined by the share access
settings for the guest account. With anonymous login disabled, log into the server using a
valid local user name and password.
2. Press
Enter
to connect to the FTP root directory.
All shares and subdirectories appear as folders.
NOTE: FTP users cannot manage files or folders in the FTP root directory.
SNMP Configuration
The SnapServer can act as an SNMP agent. SNMP managers collect data from agents and
generate statistics and other monitoring information for administrators. Agents respond to
managers and may also send traps, which are alerts that indicate error conditions. The server
communicates with SNMP managers in the same community. A community name is a
password that authorizes managers and agents to interact. The server only responds to
managers that belong to the same public or private community.
Default Traps
A trap is a signal from the SnapServer informing an SNMP manager program that an event
has occurred. SnapServer supports the default traps shown in this table:
Trap Initiating Action
coldStart Whenever SNMP is enabled and
the server boots.
linkDown A server’s Ethernet interface has gone offline.
linkUp A server’s Ethernet interface has come back online.
authenticationFailure An attempt to query the SNMP agent using an incorrect read-only
or read-write community string was made and resulted in a failure.
enterpriseSpecific SnapServer-generated traps that correspond to the error-level,
warning-level, and fatal-error-level traps of GuardianOS. These
traps contain a descriptive message that helps to diagnose a
problem using the following OIDs:
• 1.3.6.1.4.1.6411.2000.1000.1:loglevel 0 syslog messages
(emergency)
• 1.3.6.1.4.1.6411.2000.1001.1:loglevel 1 syslog messages
(alert)
• 1.3.6.1.4.1.6411.2000.1002.1:loglevel 2 syslog messages
(critical)
• 1.3.6.1.4.1.6411.2000.1003.1:loglevel 3 syslog messages
(error)
NOTE: There is no specific MIB that defines traps sent by
SnapServer.
To Next Page
Loading...
