Cisco Sg3008 Manual
Have a look at the manual Cisco Sg3008 Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 53 Cisco manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Status and Statistics Managing RMON Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 21 2 •Fragments—Number of fragments (packets with less than 64 octets, excluding framing bits, but including FCS octets) received. •Jabbers—Total number received packets that were longer than 1632 octets. This number excludes frame bits, but includes FCS octets that had either a bad FCS (Frame Check Sequence) with an integral number of octets (FCS Error) or a bad FCS with a non-integral octet (Alignment Error) number. A Jabber packet is defined as an Ethernet frame that satisfies the following criteria: -Packet data length is greater than MRU. -Packet has an invalid CRC. -Received (Rx) Error Event has not been detected. •Collisions—Number of collisions received. If Jumbo Frames are enabled, the threshold of Jabber Frames is raised to the maximum size of Jumbo Frames. •Frames of 64 Bytes—Number of frames, containing 64 bytes that were received. •Frames of 65 to 127 Bytes—Number of frames, containing 65-127 bytes that were received. •Frames of 128 to 255 Bytes—Number of frames, containing 128-255 bytes that were received. •Frames of 256 to 511 Bytes—Number of frames, containing 256-511 bytes that were received. •Frames of 512 to 1023 Bytes—Number of frames, containing 512-1023 bytes that were received. •Frames of 1024 Bytes or More—Number of frames, containing 1024-2000 bytes, and Jumbo Frames, that were received. To clear statistics counters: •Click Clear Interface Counters to clear the selected interfaces counters. •Click View All Interfaces Statistics to see all ports on a single page. Configuring RMON History The RMON feature enables monitoring statistics per interface.
Status and Statistics Managing RMON 22 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 2 The History Control Table page defines the sampling frequency, amount of samples to store and the port from where to gather the data. After the data is sampled and stored, it appears in the History Table page that can be viewed by clicking History Table. To enter RMON control information: STEP 1Click Status and Statistics > RMON > History. The fields displayed on this page are defined in the Add RMON History page, below. The only field is that is on this page and not defined in the Add page is: •Current Number of Samples—RMON is allowed by standard to not grant all requested samples, but rather to limit the number of samples per request. Therefore, this field represents the sample number actually granted to the request that is equal or less than the requested value. STEP 2Click Add. STEP 3Enter the parameters. •New History Entry—Displays the number of the new History table entry. •Source Interface—Select the type of interface from which the history samples are to be taken. •Max No. of Samples to Keep—Enter the number of samples to store. •Sampling Interval—Enter the time in seconds that samples are collected from the ports. The field range is 1-3600. •Owner—Enter the RMON station or user that requested the RMON information. STEP 4Click Apply. The entry is added to the History Control Table page, and the Running Configuration file is updated. STEP 5Click History Table to view the actual statistics. Viewing the RMON History Table The History Table page displays interface-specific statistical network samplings. The samples were configured in the History Control table described above. To view RMON history statistics:
Status and Statistics Managing RMON Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 23 2 STEP 1Click Status and Statistics > RMON > History. STEP 2Click History Table. STEP 3From the History Entry No. list, select the entry number of the sample to display. The fields are displayed for the selected sample. •Owner—History table entry owner. •Sample No.—Statistics were taken from this sample. •Drop Events—Dropped packets due to lack of network resources during the sampling interval. This may not represent the exact number of dropped packets, but rather the number of times dropped packets were detected. •Bytes Received—Octets received including bad packets and FCS octets, but excluding framing bits. •Packets Received—Packets received, including bad packets, Multicast, and Broadcast packets. •Broadcast Packets—Good Broadcast packets excluding Multicast packets. •Multicast Packets—Good Multicast packets received. •CRC Align Errors—CRC and Align errors that have occurred. •Undersize Packets—Undersized packets (less than 64 octets) received. •Oversize Packets—Oversized packets (over 2000 octets) received. •Fragments—Fragments (packets with less than 64 octets) received, excluding framing bits, but including FCS octets. •Jabbers—Total number of received packets that were longer than 2000 octets. This number excludes frame bits, but includes FCS octets that had either a bad FCS (Frame Check Sequence) with an integral number of octets (FCS Error) or a bad FCS with a non-integral octet (Alignment Error) number. •Collisions—Collisions received. •Utilization—Percentage of current interface traffic compared to maximum traffic that the interface can handle.
Status and Statistics Managing RMON 24 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 2 Defining RMON Events Control You can control the occurrences that trigger an alarm and the type of notification that occurs. This is performed as follows: •Events Page—Configures what happens when an alarm is triggered. This can be any combination of logs and traps. •Alarms Page—Configures the occurrences that trigger an alarm. To define RMON events: STEP 1Click Status and Statistics > RMON > Events. This page displays previously defined events. STEP 2Click Add. STEP 3Enter the parameters. •Event Entry—Displays the event entry index number for the new entry. •Community—Enter the SNMP community string to be included when traps are sent (optional). Note that the community must be defined using the Defining SNMPv1,2 Notification Recipients or Defining SNMPv3 Notification Recipients pages for the trap to reach the Network Management Station. •Description—Enter a name for the event. This name is used in the Add RMON Alarm page to attach an alarm to an event. •Notification Type—Select the type of action that results from this event. Va lue s a re : -None—No action occurs when the alarm goes off. -Log (Event Log Table)—Add a log entry to the Event Log table when the alarm is triggered. -Trap (SNMP Manager and SYSLOG Server)—Send a trap to the remote log server when the alarm goes off. -Log and Trap—Add a log entry to the Event Log table and send a trap to the remote log server when the alarm goes off. •Time—Displays the time of the event. (This is a read-only table in the parent window and cannot be defined). •Owner—Enter the device or user that defined the event.
Status and Statistics Managing RMON Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 25 2 STEP 4Click Apply. The RMON event is saved to the Running Configuration file. STEP 5Click Event Log Table to display the log of alarms that have occurred and that have been logged (see description below). Viewing the RMON Events Logs The Event Log Table page displays the log of events (actions) that occurred. Two types of events can be logged: Lo g or Log and Trap. The action in the event is performed when the event is bound to an alarm (see the Alarms page) and the conditions of the alarm have occurred. STEP 1Click Status and Statistics > RMON > Events. STEP 2Click Event Log Table. This page displays the following fields: •Event Entry No.—Event’s log entry number. •Log No.—Log number (within the event). •Log Time—Time that the log entry was entered. •Description—Description of event that triggered the alarm. Defining RMON Alarms RMON alarms provide a mechanism for setting thresholds and sampling intervals to generate exception events on any counter or any other SNMP object counter maintained by the agent. Both the rising and falling thresholds must be configured in the alarm. After a rising threshold is crossed, no rising events are generated until the companion falling threshold is crossed. After a falling alarm is issued, the next alarm is issued when a rising threshold is crossed. One or more alarms are bound to an event, which indicates the action to be taken when the alarm occurs. The Alarms page provides the ability to configure alarms and to bind them with events. Alarm counters can be monitored by either absolute values or changes (delta) in the counter values.
Status and Statistics Managing RMON 26 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 2 To enter RMON alarms: STEP 1Click Status and Statistics > RMON > Alarms. All previously-defined alarms are displayed. The fields are described in the Add RMON Alarm page below. In addition to those fields, the following field appears: •Counter Value—Displays the value of the statistic during the last sampling period. STEP 2Click Add. STEP 3Enter the parameters. •Alarm Entry—Displays the alarm entry number. •Interface—Select the type of interface for which RMON statistics are displayed. •Counter Name—Select the MIB variable that indicates the type of occurrence measured. •Sample Type—Select the sampling method to generate an alarm. The options are: -Absolute—If the threshold is crossed, an alarm is generated. -Delta—Subtracts the last sampled value from the current value. The difference in the values is compared to the threshold. If the threshold was crossed, an alarm is generated. •Rising Threshold—Enter the value that triggers the rising threshold alarm. •Rising Event—Select an event to be performed when a rising event is triggered. Events are created in the Events page. •Falling Threshold—Enter the value that triggers the falling threshold alarm. •Falling Event—Select an event to be performed when a falling event is triggered. •Startup Alarm—Select the first event from which to start generation of alarms. Rising is defined by crossing the threshold from a low-value threshold to a higher-value threshold. -Rising Alarm—A rising value triggers the rising threshold alarm. -Falling Alarm—A falling value triggers the falling threshold alarm. -Rising and Falling—Both rising and falling values trigger the alarm.
Status and Statistics View Lo g Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 27 2 •Interval—Enter the alarm interval time in seconds. •Owner—Enter the name of the user or network management system that receives the alarm. STEP 4Click Apply. The RMON alarm is saved to the Running Configuration file. View Log See Viewing Memory Logs.
Status and Statistics View Lo g 28 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 2
3 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 29 Administration: System Log This section describes the System Log feature, which enables the device to generate multiple independent logs. Each log is a set of messages describing system events. The device generates the following local logs: •Log sent to the console interface. •Log written into a cyclical list of logged events in the RAM and erased when the device reboots. •Log written to a cyclical log-file saved to the Flash memory and persists across reboots. In addition, you can send messages to remote SYSLOG servers in the form of SNMP traps and SYSLOG messages. This section covers the following sections: •Setting System Log Settings •Setting Remote Logging Settings •Viewing Memory Logs Setting System Log Settings You can enable or disable logging on the Log Settings page, and select whether to aggregate log messages. You can select the events by severity level. Each log message has a severity level marked with the first letter of the severity level concatenated with a dash (-) on each side (except for Emergency that is indicated by the letter F). For example, the log message %INIT-I-InitCompleted: … has a severity level of I, meaning Informational.
Administration: System Log Setting System Log Settings 30 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 3 The event severity levels are listed from the highest severity to the lowest severity, as follows: •Emergency—System is not usable. •Aler t—Action is needed. •Critical—System is in a critical condition. •Error—System is in error condition. •Warning—System warning has occurred. •Notice—System is functioning properly, but a system notice has occurred. •Informational—Device information. •Debug—Detailed information about an event. You can select different severity levels for RAM and Flash logs. These logs are displayed in the RAM Memory page and Flash Memory page, respectively. Selecting a severity level to be stored in a log causes all of the higher severity events to be automatically stored in the log. Lower severity events are not stored in the log. For example, if Warning is selected, all severity levels that are Warning and higher are stored in the log (Emergency, Alert, Critical, Error, and Warning). No events with severity level below Warning are stored (Notice, Informational, and Debug). To set global log parameters: STEP 1Click Administration > System Log > Log Settings. STEP 2Enter the parameters. •Logging—Select to enable message logging. •Syslog Aggregator—Select to enable the aggregation of SYSLOG messages and traps. If enabled, identical and contiguous SYSLOG messages and traps are aggregated over the specified Max Aggregation Time and sent in a single message. The aggregated messages are sent in the order of their arrival. Each message states the number of times it was aggregated. •Max Aggregation Time—Enter the interval of time that SYSLOG messages are aggregated.