Cisco Sg3008 Manual

							Administration: System Log
Setting Remote Logging Settings
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)  31
3
 
•Originator Identifier—Enables adding an origin identifier to SYSLOG 
messages. The options are:
-None—Do not include the origin identifier in SYSLOG messages.
-Hostname—Include the system hostname in SYSLOG messages.
-IPv4 Address—Include the IPv4 address of the sending interface in 
SYS LO G messages.
-IPv6 Address—Include the IPv6 address of the sending interface in 
SYS LO G messages.
-User Defined—Enter a description to be included in SYSLOG messages.
•RAM Memory Logging—Select the severity levels of the messages to be 
logged to the RAM.
•Flash Memory Logging—Select the severity levels of the messages to be 
logged to the Flash memory.
STEP  3Click Apply. The Running Configuration file is updated.
Setting Remote Logging Settings
The Remote Log Servers page enables defining remote SYSLOG servers where 
log messages are sent (using the SYSLOG protocol). For each server, you can 
configure the severity of the messages that it receives.
To  d e f i n e  S Y S L O G  s e r v e r s :
STEP 1Click Administration > System Log > Remote Log Servers.
STEP  2Enter the following fields:
•IPv4 Source Interface—Select the source interface whose IPv4 address will 
be used as the source IP v4 address of SYS LO G messages sent to SYS LO G 
servers. 
•IPv6 Source Interface—Select the source interface whose IPv6 address will 
be used as the source IP v6 addres s of SYS LOG mes sages sent to SYS LOG 
servers. 
						

							Administration: System Log
Setting Remote Logging Settings
32 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 
3
NOTEIf the Auto option is selected, the system takes the source IP address 
from the IP address defined on the outgoing interface.
STEP  3Click Add.
STEP  4Enter the parameters.
•Server Definition—Select whether to identify the remote log server by IP 
address or name.
•IP Version—Select the supported IP format.
•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The 
options are:
-Link Local—The IPv6 address uniquely identifies hosts on a single 
network link. A link local address has a prefix of FE80, is not routable, and 
can be used for communication only on the local network. Only one link 
local address is supported. If a link local address exists on the interface, 
this entry replaces the address in the configuration.
-Global—The IPv6 address is a global Unicast IPV6 type that is visible and 
reachable from other networks.
•Link Local Interface—Select the link local interface (if IPv6 Address Type 
Link Local is selected) from the list. 
•Log Server IP Address/Name—Enter the IP address or domain name of the 
log server.
•UDP Port—Enter the UDP port to which the log messages are sent.
•Facilit y—Select a facility value from which system logs are sent to the 
remote server. Only one facility value can be assigned to a server. If a second 
facility code is assigned, the first facility value is overridden.
•Description—Enter a server description.
•Minimum Severity—Select the minimum level of system log messages to 
be sent to the server. 
STEP  5Click Apply. The Add Remote Log Server page closes, the SYSLOG server is 
added, and the Running Configuration file is updated. 
						

							Administration: System Log
Viewing Memor y Lo gs
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)  33
3
 
Viewing Memory Logs 
The device can write to the following logs:
•Log in RAM (cleared during reboot).
•Log in Flash memory (cleared only upon user command). 
You can configure the messages that are written to each log by severity, and a 
message can go to more than one log, including logs that reside on external 
SYSLO G ser vers.
RAM Memory
The RAM Memory page displays all messages that were saved in the RAM 
(cache) in chronological order. Entries are stored in the RAM log according to the 
configuration in the Log Settings page.
To view log entries, click Status and Statistics > View Log > RAM Memory.
The top of the page has a button that allows you to Disable Alert Icon Blinking. 
Click to toggle between disable and enable.
This page contains the following fields:
•Log Index—Log entry number.
•Log Time—Time when message was generated.
•Severity—Event severity.
•Description—Message text describing the event.
To clear the log messages, click Clear Logs. The messages are cleared.
Flash Memory
The Flash Memory page displays the messages that were stored in the Flash 
memory, in chronological order. The minimum severity for logging is configured in 
the Log Settings page. Flash logs remain when the device is rebooted. You can 
clear the logs manually.
To view the Flash logs, click Status and Statistics > View Log > Flash Memory. 
						

							Administration: System Log
Viewing Memory Logs
34 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 
3
This page contains the following fields:
•Log Index—Log entry number.
•Log Time—Time when message was generated.
•Severity—Event severity.
•Description—Message text describing the event.
To clear the messages, click Clear Logs. The messages are cleared. 
						

							4
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)  35
 
Administration: File Management
This section describes how system files are managed. 
The following topics are covered:
•System Files
•Upgrade/Backup Firmware/Language
•Active Image 
•Download/Backup Configuration/Log
•Configuration Files Properties
•Copy/Save Configuration
•Auto Configuration via DHCP
System Files
System files are files that contain configuration information, firmware images or 
boot code.
Various actions can be performed with these files, such as: selecting the firmware 
file from which the device boots, copying various types of configuration files 
internally on the device, or copying files to or from an external device, such as an 
external ser ver.
The possible methods of file transfer are:
•Internal copy.
•HTTP/HTTPS that uses the facilities that the browser provides.
•TFTF/SCP client, requiring a TFTP/SCP server. 
						

							Administration: File Management
System Files
36 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 
4
Configuration files on the device are defined by their type, and contain the 
settings and parameter values for the device.
When a configuration is referenced on the device, it is referenced by its 
configuration file type (such as Star tup Configuration or Running Configuration), 
as opposed to a file name that can be modified by the user. 
Content can be copied from one configuration file type to another, but the names 
of the file types cannot be changed by the user. 
Other files on the device include firmware, boot code, and log files, and are 
referred to as operational files.
The configuration files are text files and can be edited in a text editor, such as 
Notepad after they are copied to an external device, such as a PC. 
Files and File Types
The following types of configuration and operational files are found on the device:
•Running Configuration—Contains the parameters currently being used by 
the device to operate. This is the only file type that is modified when you 
change parameter values on the device.
If the device is rebooted, the Running Configuration is lost. The Startup 
Configuration, stored in Flash, overwrites the Running Configuration, stored 
in RAM. 
To preserve any changes you made to the device, you must save the 
Running Configuration to the Startup Configuration, or another file type.
•Startup Configuration—The parameter values that were saved by copying 
another configuration (usually the Running Configuration) to the Startup 
Configuration. 
The Startup Configuration is retained in Flash and is preserved when the 
device is rebooted. At this time, the Startup Configuration is copied to RAM 
and identified as the Running Configuration.
•Mirror Configuration—A copy of the Startup Configuration, created by the 
device when the following conditions exist: 
-The device has been operating continuously for 24 hours.
-No configuration changes have been made to the Running Configuration 
in the previous 24 hours.
-The Startup Configuration is identical to the Running Configuration.  
						

							Administration: File Management
System Files
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)  37
4
 
Only the system can copy the Startup Configuration to the Mirror 
Configuration. However, you can copy from the Mirror Configuration to other 
file types or to another device. 
The option of automatically copying the Running Configuration to the mirror 
configuration can be disabled in the Configuration Files Properties page. 
•Backup Configuration—A manual copy of a configuration file used for 
protection against system shutdown or for the maintenance of a specific 
operating state. You can copy the Mirror Configuration, Startup 
Configuration, or Running Configuration to a Backup Configuration file. The 
Backup Configuration exists in Flash and is preserved if the device is 
rebooted. 
•Firmware—The program that controls the operations and functionality of 
the device. More commonly referred to as the image. 
•Boot Code—Controls the basic system startup and launches the firmware 
image.
•Language File—The dictionary that enables the web-based configuration 
utility windows to be displayed in the selected language. 
•Flash Log—SYSLOG messages stored in Flash memory.
File Actions
The following actions can be performed to manage firmware and configuration 
files:
•Upgrade the firmware or boot code, or replace a second language, as 
described in Upgrade/Backup Firmware/Language section.
•View the firmware image currently in use or select the image to be used in 
the next reboot as described in the Active Image  section.
•Save configuration files on the device to a location on another device as 
described in the Download/Backup Configuration/Log section.
•Clear the Startup Configuration or Backup Configuration file types as 
described in the Configuration Files Properties section.
•Copy one configuration file type to another configuration file type as 
described in the Copy/Save Configuration section. 
•Enable automatically uploading a configuration file from a DHCP server to 
the device, as described in the Auto Configuration via DHCP section. 
						

							Administration: File Management
Upgrade/Backup Firmware/Language
38 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 
4
This section covers the following topics:
•Upgrade/Backup Firmware/Language
•Active Image 
•Download/Backup Configuration/Log
•Configuration Files Properties
•Copy/Save Configuration
•Auto Configuration via DHCP
Upgrade/Backup Firmware/Language
The Upgrade/Backup Firmware/Language process can be used to:
•Upgrade or backup the firmware image.
•Upgrade or backup the boot code.
•Import or upgrade a second language file.
The following methods for transferring files are supported: 
•HTTP/HTTPS that uses the facilities provided by the browser
•TFTP that requires a TFTP server 
•Secure Copy Protocol (SCP) that requires an SCP server
If a new language file was loaded onto the device, the new language can be 
selected from the drop-down menu. (It is not necessary to reboot the device). 
There are two firmware images stored on the device. One of the images is 
identified as the active image and other image is identified as the inactive image. 
When you upgrade the firmware, the new image always replaces the image 
identified as the inactive image.
Even after uploading new firmware on the device, the device continues to boot by 
using the active image (the old version) until you change the status of the new 
image to be the active image by using the procedure in the Active Image  section. Then boot the device. 
						

							Administration: File Management
Upgrade/Backup Firmware/Language
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)  39
4
 
Upgrade/Backing Firmware or Language File
To upgrade or backup a software image or language file:
STEP 1Click Administration > File Management > Upgrade/Backup Firmware/
Language.
STEP  2Click the Transfer Method. Proceed as follows:
•If you selected TFTP, go to STEP 3. 
•If you selected via HTTP/HTTPS, go to STEP 4. 
•If you selected via SCP, go to STEP 5. 
STEP  3If you selected via TFTP, enter the parameters as described in this step. 
Otherwise, skip to STEP 4.
Select one of the following Save Actions:
•Upgrade—Specifies that the file type on the device is to be replaced with a 
new version of that file type located on a TFTP server. 
•Backup—Specifies that a copy of the file type is to be saved to a file on 
another device. 
Enter the following fields: 
•File Type—Select the destination file type. Only valid file types are shown. 
(The file types are described in the Files and File Types section).
•TFTP Server Definition—Select whether to specify the TFTP server by IP 
address or domain name.
•IP Version—Select whether an IPv4 or an IPv6 address is used.
•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The 
options are:
-Link Local—The IPv6 address uniquely identifies hosts on a single 
network link. A link local address has a prefix of FE80, is not routable, and 
can be used for communication only on the local network. Only one link 
local address is supported. If a link local address exists on the interface, 
this entry replaces the address in the configuration.
-Global—The IPv6 address is a global Unicast IPV6 type that is visible and 
reachable from other networks.  
						

							Administration: File Management
Upgrade/Backup Firmware/Language
40 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 
4
•Link Local Interface—Select the link local interface (if IPv6 is used) from the 
list. 
•TFTP Server IP Address/Name—Enter the IP address or the domain name 
of the TFTP server.
•(For Upgrade) Source File Name—Enter the name of the source file.
•(For Backup) Destination File Name—Enter the name of the backup file. 
STEP  4If you selected via HTTP/HT TPS, you can only Upgrade. Enter the parameters as 
described in this step. 
•File Type—Select one of the following file types:
-Firmware Image—Select this to upgrade the firmware image.
-Language—Select this to upgrade the language file.
•File Name—Click Browse to select a file or enter the path and source file 
name to be used in the transfer.
STEP  5If you selected via SCP (Over SSH), see SSH Client Authentication for 
instructions. Then, enter the following fields: (only unique fields are described, for 
non-unique fields, see the descriptions above)
•Remote SSH Server Authentication—To enable SSH server authentication 
(which is disabled by default), click Edit. This takes you to the SSH Server 
Authentication page to configure the SSH server, and return to this page. 
Use the SSH Server Authentication page to select an SSH user 
authentication method (password or public/private key), set a username and 
password on the device (if the pas sword method is selected) , and generate 
an RSA or DSA key if required.
SSH Client Authentication—Client authentication can be done in one of the 
following ways:
•Use SSH Client System Credentials—Sets permanent SSH user 
credentials. Click System Credentials to go to the SSH User Authentication 
page where the user/password can be set once for all future use.
•Use SSH Client One-Time Credentials—Enter the following:
-Username—Enter a username for this copy action.
-Password—Enter a password for this copy.
NOTEThe username and password for one-time credential will not saved in 
configuration file.