Nortel Ethernet Routing Switch 2500 Series Configuration ... · Nortel Ethernet Routing Switch 2500 Series Conﬁguration — System Monitoring NN47215-502

Nortel Ethernet Routing Switch 2500 Series

Configuration — SystemMonitoring

NN47215-502.

Document status: StandardDocument version: 03.01Document date: 27 October 2008

Copyright © 2007-2008, Nortel NetworksAll Rights Reserved.

The information in this document is subject to change without notice. The statements, configurations, technicaldata, and recommendations in this document are believed to be accurate and reliable, but are presented withoutexpress or implied warranty. Users must take full responsibility for their applications of any products specified in thisdocument. The information in this document is proprietary to Nortel Networks.

The software described in this document is furnished under a license agreement and may be used only in accordancewith the terms of that license. The software license agreement is included in this document.

Trademarks*Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Adobe and Adobe Reader are trademarks of Adobe Systems Incorporated.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.

Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

All other trademarks are the property of their respective owners.

Restricted rights legendUse, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computersoftware, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forthin the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

3

Contents

New in this release 7Features 7

Introduction 9NNCLI command modes 9

System Monitoring Fundamentals 11CPU and memory utilization 11Trap Web page 12Light Emitting Diode display 12System Log 12Port mirroring 12

Port mirroring configuration rules 13Stack monitor 14Chassis and port statistics 14Remote Monitoring 15

RMON alarms 15

Network monitoring configuration using NNCLI 19CPU utilization 19Memory utilization 19System log 20

Viewing the system event log 20Configuring system logging 21Disabling logging 22Setting default logging 22Clearing log messages 22

Port mirroring 23Displaying the port-mirroring configuration 23Configuring port-mirroring 24Disabling port-mirroring 24

Port statistics 24Displaying port-statistics 25Clearing statistical information 26

Stack health 27Viewing stack health 27

Nortel Ethernet Routing Switch 2500 SeriesConfiguration — System Monitoring

NN47215-502 03.01 Standard4.2 27 October 2008

Copyright © 2007-2008, Nortel Networks

.

4 Contents

Viewing stack monitor information 27Configuring the stack monitor 28Disabling the stack monitor 28

Network monitoring configuration using Device Manager 29CPU and memory utilization 29Viewing the system log settings 30Viewing the Remote System Log tab 32Graphing chassis statistics 33

Viewing IP statistics 34Viewing ICMP In statistics 36Viewing ICMP Out statistics 37Viewing TCP statistics 38Viewing UDP statistics 40

Graphing port statistics 41Graphing the Interface tab 41Graphing the Ethernet Errors tab 43Misc. Stats tab 46

Configuring the stack monitor 47

Network monitoring configuration using Web-basedmanagement 49

CPU and memory utilization 49Using the trap Web page to identify trap receivers 49Stack Health 50Viewing the system log 51Configuring port mirroring 52Viewing statistics 53

Viewing port statistics 53Zeroing ports 56Zeroing all ports 56Viewing interface statistics 57Viewing Ethernet error statistics 58Viewing transparent bridging statistics 59

Monitoring MLT traffic 60

RMON using the NNCLI 63Viewing the RMON alarms 63Viewing the RMON events 64Viewing the RMON history 64Viewing the RMON statistics 64Configuring RMON alarms 65Deleting RMON alarms 66Configuring RMON events settings 66Deleting RMON events settings 67Configuring RMON history settings 67




.

Contents 5

Deleting RMON history settings 68Configuring RMON statistics settings 69Deleting RMON statistics 69

RMON using Device Manager 71Working with RMON information 71

Viewing statistics 71Viewing history 74Creating history items 74Disabling history 76Viewing RMON history statistics 77Enabling Ethernet statistics gathering 78Disabling Ethernet statistics gathering 79

Creating an alarm 79Deleting an alarm 81Viewing RMON statistics and history 82Using RMON events 84

Viewing an event 84Deleting an event 86

Viewing RMON log information 86

RMON using Web-based management 89Configuring RMON fault threshold parameters 89

Creating an RMON fault threshold 89Deleting an RMON threshold configuration 92

Viewing the RMON fault event log 93Viewing RMON Ethernet statistics 94Viewing RMON history 95




.

6 Contents




.

7

New in this release

The following sections detail what’s new in Configuration — SystemMonitoring (NN47215-502) for Release 4.2:

FeaturesFor information about changes that are feature related, see the section:

• "Stack monitor" (page 14)

• "Stack health" (page 27)

• "CPU and memory utilization" (page 11)

• "Trap Web page " (page 12)

• "System Log" (page 12)




.

8 New in this release




.

9

Introduction

This guide provides information about system logging, displaying systemstatistics, and configuring network monitoring on the Nortel EthernetRouting Switch 2500 Series. This guide describes the features of thefollowing Nortel switches.

• Nortel Ethernet Routing Switch 2526T

• Nortel Ethernet Routing Switch 2526T-PWR

• Nortel Ethernet Routing Switch 2550T

• Nortel Ethernet Routing Switch 2550T-PWR

The term "Ethernet Routing Switch 2500 Series" is used in this document todescribe the features common to the switches mentioned above.

A switch is referred to by its specific name while describing a featureexclusive to the switch.

NNCLI command modesNNCLI provides the following command modes:

• User EXEC

• Privileged EXEC

• Global Configuration

• Interface Configuration

Mode access is determined by access permission levels and passwordprotection.

If no password is set, you can enter NNCLI in User EXEC mode and usethe enable command to move to the next level (Privileged EXEC mode).However, if you have read-only access, you cannot progress beyond UserEXEC mode, the default mode. If you have read-write access you canprogress from the default mode through all of the available modes.




.

10 Introduction

With sufficient permission, you can use the rules in the following table tomove between the command modes.

Table 1NNCLI command modes

Command mode and sampleprompt

Entrance commands Exit commands

User EXEC2526T>

No entrance command, defaultmode

exit

orlogout

Privileged EXEC2526T#

enable exit

orlogout

Global Configuration2526T(config)#

From Privileged EXEC mode,enter:configure

To return to Privileged EXECmode, enter:end

orexit

To exit NNCLI completely,enter:logout

Interface Configuration2526T(config-if)#

From Global Configurationmode:To configure a port, enter:interface fastethernet <portnumber>To configure a VLAN, enter:interface vlan <vlan number>

To return to GlobalConfiguration mode, enter:exit

To return to Privileged EXECmode, enter:end

To exit NNCLI completely,enter:logout

See Nortel Ethernet Routing Switch <2500/4500/5000> SeriesFundamentals <NN47215-102/NN47205-102/NN47200-104>




.

11

System Monitoring Fundamentals

The Ethernet Routing Switch 2500 Series provide features that allowyou to monitor your network, display switch statistics, log system events,and provide Remote Network Monitoring (RMON). This chapter containsinformation about the following topics:

Navigation• "CPU and memory utilization" (page 11)

• "Trap Web page " (page 12)

• "Light Emitting Diode display" (page 12)

• "System Log" (page 12)

• "Port mirroring" (page 12)

• "Stack monitor" (page 14)

• "Chassis and port statistics" (page 14)

• "Remote Monitoring" (page 15)

CPU and memory utilizationThe CPU utilization feature provides data for CPU and memory utilization.You can view CPU utilization information for the past 10 seconds (s),1minute (min), 1 hour (hr), 24 hr, or since system startup. The switchdisplays CPU utilization as a percentage. With CPU utilization informationyou can see how the CPU was used during a specific time interval.

The memory utilization provides information about the percentage ofthe dynamic memory currently used by the system. The switch displaysmemory utilization in terms of the lowest percentage of dynamic memoryavailable since system startup.

No configuration is required for this display-only feature.




.

12 System Monitoring Fundamentals

Trap Web pageTrap Web page in Web-based management provides a graphical method toenable or disable traps you want to send. In the case multiple trap receiversare selected you can map which traps are sent to which receiver. Youcan group traps by event type to send to persons who have roles such assecurity or network connectivity.

You can access a Web page, for every host, from which you can enable ordisable every trap for a specific host. The access to those pages is throughthe SNMP Trap Web page, which page contains two options for every trap.The first option enables the trap. The second option disables the trap.Select an option to enable or disable a specific trap for a specific host.

Light Emitting Diode displayThe ERS 2500 Series displays diagnostic and operation information thoughthe LEDs on the unit. Familiarize yourself with the interpretation of theLEDs on the 2500 series device. SeeNortel Ethernet Routing Switch 2500Series — Installation (NN47205-300) for detailed information regarding theinterpretation of the LEDs.

System LogThe System Log displays messages obtained from system Non VolatileRandom Access Memory (NVRAM) or Dynamic Random Access Memory(DRAM). The System Log displays only the data for the Ethernet RoutingSwitch 2500 Series through the Console or Comm port, WEB, or Telnet.

System Log messages operate as follows:

• NVRAM messages are retrievable after a system reset.

• DRAM messages can be viewed while the system is operational.

• All NVRAM and DRAM messages are time stamped.

• When you restart your system after a reset, the DRAM messages aredeleted.

• After a reset, all messages stored in NVRAM are copied to DRAM(DRAM messages are not copied to NVRAM). The messages copied toDRAM are time stamped to zero (0).

Port mirroringThe Port mirroring feature, also referred to as conversation steering, lets youallocate a single switch port (monitor port) as a traffic monitor for anotherswitch port (mirror port). All incoming traffic on the mirrored port is copied tothe monitor port. This operation excludes traffic forwarded by the switch.This feature is helpful in network troubleshooting.




.

Port mirroring 13

You can specify port-based monitoring for ingress to a specific port. Youcan also attach a probe device or equivalent, to the designated monitorport. When a port is operating as a monitor port, forwarding is not allowedon that port.

Ethernet Routing Switch 2500 Series supports ingress, egress, andingress/egress port-based mirroring.

Port mirroring configuration rulesThe following configuration rules apply to the various port mirroring modes:

Port mirroring ingress mode (XRX or ->Port X)

In the Port mirroring ingress mode, packets received on mirror port X arecopied to the monitor port.

Standalone

On a standalone switch, there is no limitation for ingress port mirroring.

Stack

To enable ingress port mirroring in a stack environment, the mirror port andthe monitor port can be on any unit in the stack.

Duplex Stack

Ingress port mirroring is not supported in duplex stacking.

Port mirroring egress mode (XTX or Port X ->)

In the Port mirroring egress mode, packets transmitted on mirror port X arecopied to the monitor port.

Standalone


Stack

To enable egress port mirroring in a stack environment, the mirror port andthe monitor port can be on any unit in the stack .

Port mirroring ingress and egress mode (XRX or XTX or <->Port X)




.


In the Port Mirroring ingress and egress mode, packets that are eithertransmitted or received on mirror port X are copied to the monitor port.

Standalone


Stack

Ingress and egress port mirroring is not supported in stack configurations.

Stack monitorThe Stack Monitor uses a set of control values to enable its operation, toset the expected stack size, and to control the frequency of trap sending.The stack monitor, if enabled, detects problems with the units in the stackand sends a trap.

The stack monitor sends a trap for the following events.

• The number of units in a stack changes.

• The trap sending timer expires.

Each time the number of units in a stack changes, the trap sending timerresets and the stack monitor compares the current number of stack unitswith the configured number of stack units. If the values are not equal, theswitch sends a trap and logs a message to syslog. The stack monitor sendstraps from a stand-alone unit or the base unit of the stack.

After the trap sending timer reaches the configured number of seconds atwhich traps are sent, the switch sends a trap and logs a message to syslogand restarts the trap sending timer. The syslog message is not repeatedunless the stack configuration changes. To prevent the log from being filledwith stack configuration messages.

After you enable the stack monitor on a stack, the stack monitor capturesthe current stack size and uses it as the expected stack size. You canchoose a different value and set it after you enable the feature.

Chassis and port statisticsChassis and port statistics allow you to view detailed information about anyswitch or port. The port statistics are divided by received and transmitted sothat you can compare and evaluate throughput or other port parameters.




.

Remote Monitoring 15

Remote MonitoringRMON MIB is an interface between the RMON agent on an EthernetRouting Switch 2500 Series and an RMON management application, suchas the Device Manager.

The RMON agent defines objects that are suitable for the management ofany type of network, but some groups are targeted for Ethernet networksin particular.

The RMON agent continuously collects statistics and proactively monitorsswitch performance. You can view this data through the CLI, web-basedmanagement, and Device Manager.

RMON has three major functions:

• creating and displaying alarms for user-defined events

• gathering cumulative statistics for Ethernet interfaces

• tracking a history of statistics for Ethernet interfaces

RMON alarmsAlarms are useful when you need to know when the values of a variable goout of range. You can define an RMON alarm for any MIB variable thatresolves to an integer value. You cannot use string variables (such assystem description) as alarm variables.

All alarms share the following characteristics:

• An upper and lower threshold value is defined.

• A corresponding rising and falling event occurs.

• An alarm interval or polling period is reached.

When alarms are activated, you can view the activity in a log or a trap log,or you can create a script to notify you by sending an audible sound to aconsole, sending e-mail, or calling a pager.

How RMON alarms workThe alarm variable is polled and the result is compared against upper andlower limit values you select when you create the alarm. If either limit isreached or crossed during the polling period, then the alarm triggers andgenerates an event that you can view in the event log or the trap log.

The upper limit of the alarm is called the rising value, and its lower limitis called the falling value. RMON periodically samples the data basedupon the alarm interval. During the first interval in which the data passesabove the rising value, the alarm triggers as a rising event. During the firstinterval in which the data drops below the falling value, the alarm triggersas a falling event.




.


The following figure describes how alarms are triggered.

The alarm fires during the first interval that the sample goes out of range.No additional events are generated for that threshold until the oppositethreshold is crossed. Therefore, it is important to carefully define the risingand falling threshold values for alarms to work as expected. Otherwise,incorrect thresholds cause an alarm to fire at every alarm interval.

A general guideline is to define one of the threshold values to an expectedbaseline value, and then define the opposite threshold as the out-of-boundslimit. Because of sample averaging, the value may be equal to ±1 of thebaseline units. For example, assume an alarm is defined on octets going outof a port as the variable. The intent of the alarm is to provide notification toyou after excessive traffic occurs on that port. If spanning tree is enabled, 52octets are transmitted out of the port every 2 seconds, which is equivalentto baseline traffic of 260 octets every 10 seconds. This alarm providesnotification to you if the lower limit of octets going out is defined at 260 andthe upper limit is defined at 320 (or at a value greater than 260 + 52 = 312).

The first time outbound traffic other than spanning tree Bridge Protocol DataUnits (BPDU) occurs, the rising alarm fires. After outbound traffic other thanspanning tree ceases, the falling alarm fires. This process provides you withtime intervals of a non-baseline outbound traffic.

If the alarm is defined with a falling threshold less than 260 (assuming thealarm polling interval is 10 seconds) the rising alarm can fire only once.For the rising alarm to fire a second time, the falling alarm (the oppositethreshold) must fire. Unless the port becomes inactive or spanning tree isdisabled (which will cause the value for outbound octets to drop to zero), thefalling alarm cannot fire because the baseline traffic is always greater thanthe value of the falling threshold. By definition, the failure of the falling alarmto fire prevents the rising alarm from firing a second time.

The following figure describes an alarm with a threshold less than 260.




.

Remote Monitoring 17

Creating alarmsSelect a variable from the variable list and a port, or other switch component,to which it is connected. Some variables require port IDs, card IDs, orother indices (for example, spanning tree group IDs). Then select a risingand a falling threshold value. The rising and falling values are comparedagainst the actual value of the variable that you choose. If the variable fallsoutside of the rising or falling value range, an alarm is triggered and anevent is logged or trapped.

After an alarm is created a sample type is also selected, which can be eitherabsolute or delta. Absolute alarms are defined on the cumulative value ofthe alarm variable. An example of an alarm defined with absolute value iscard operating status. Because this value is not cumulative, but insteadrepresents states, such as card up (value 1) and card down (value 2), youset it for absolute value. You can create an alarm with a rising value of 2and a falling value of 1 to alert a user to whether the card is up or down.

Most alarm variables related to Ethernet traffic are set to delta value. Deltaalarms are defined based on the difference in the value of the alarm variablebetween the start of the polling period and the end of the polling period.Delta alarms are sampled twice for each polling period. For each sample,the last two values are added together and compared to the thresholdvalues. This process increases precision and allows for the detection ofthreshold crossings that span the sampling boundary. If you track thecurrent values of a delta-valued alarm and add them together, therefore, theresult is twice the actual value. (This result is not an error in the software.)

How events workAn event specifies whether a trap, a log, or a trap and a log is generatedto view alarm activity. When RMON is globally enabled, two default eventsare generated:

• RisingEvent

• FallingEvent




.


The default events specify that when an alarm goes out of range, the firingof the alarm is tracked in both a trap and a log. For example, when analarm triggers at the rising threshold, the rising event specifies that thisinformation be sent to both a trap and a log. Likewise, when an alarmpasses the falling threshold, the falling event specifies that this informationbe sent to a trap and a log.




.

19

Network monitoring configurationusing NNCLI

This chapter describes how to configure network monitoring using NNCLI.

Navigation• "CPU utilization" (page 19)

• "Memory utilization" (page 19)

• "System log" (page 20)

• "Port mirroring" (page 23)

• "Port statistics" (page 24)

• "Stack health" (page 27)

CPU utilizationUse this procedure to view CPU utilization.

Procedure Steps

Step Action

1 Enter Privileged exec mode.

2 Enter the show cpu-utilization command.

3 Observe the displayed information.

—End—

Memory utilizationUse this procedure to view memory utilization.




.

20 Network monitoring configuration using NNCLI

Procedure Steps

Step Action


2 Enter the show memory-utilization command.


—End—

System logThis section describes the NNCLI commands that you use to configureand manage the system log.

Navigation

• "Viewing the system event log" (page 20)

• "Configuring system logging " (page 21)

• "Disabling logging" (page 22)

• "Disabling logging" (page 22)

• "Setting default logging " (page 22)

• "Clearing log messages" (page 22)

Viewing the system event logThe show logging command displays the configuration and the currentcontents of the system event log.

Procedure Steps

Step Action

1 Enter Privileged EXEC mode.

2 Enter the show logging command.


—End—

Run the show logging command in Privileged EXEC command mode.




.

System log 21

Variable definitionsThe following table describes the command parameters

Variable Definition

config Display the configuration of event logging.

critical Display critical log messages.

serious Display serious log messages.

informational Display informational log messages.

sort-reverse Display informational log messages in reversechronological order (beginning with mostrecent).

unit Display log messages for a certain unit.

Configuring system loggingUse this command to configure the system settings for the system event log.

Procedure Steps

Step Action

1 Enter Global Configuration mode.

2 Enter the logging [enable | disable] [level critical| serious | informational | none] [nv-levelcritical | serious | none] remote [address |enable | level] volatile [latch | overwrite]command.

—End—

Variable definitionsThe following table describes the command parameters.

Variable Definition

enable | disable Enables or disables the event log (enabled isthe default setting).

level critical | serious |informational | none

Specify the level of logging stored in DRAM.

nv-level critical | serious |none

Specify the level of logging stored in NVRAM.




.


Variable Definition

remote Configure remote logging parameters.

Address: configure remote syslog address.Enable: enable remote logging.

Level: configure remote logging level.

volatile Configure options for logging to DRAM.

Latch: latch DRAM log when it is full.Overwrite: overwrite DRAM log when it is full.

Disabling loggingUse this procedure to disable the system event log.

Procedure Steps

Step Action


2 Enter the no logging command.

—End—

Setting default loggingUse this procedure to configure the system settings as the factory defaultsettings for the system event log.

Procedure Steps

Step Action


2 Enter the default logging command.

—End—

Clearing log messagesUse this procedure to clear all log messages in DRAM.

Procedure Steps

Step Action

1 Enter Privileged EXEC mode.




.

Port mirroring 23

2 Enter the clear logging [non-volatile] [nv][volatile] command.

—End—

Variable DefinitionsThe following table describes the command parameters.

Variable Definition

non-volatile Clear log messages from NVRAM.

nv Clear log messages from NVRAM and DRAM.

volatile Clear log messages from DRAM.

Port mirroringThis section describes how to configure and display port mirroring

• "Displaying the port-mirroring configuration" (page 23)

• "Configuring port-mirroring " (page 24)

• "Disabling port-mirroring" (page 24)

Displaying the port-mirroring configurationUse this command to display the configuration and the current contents ofthe system event log.

Procedure Steps

Step Action


2 Enter the show port-mirroring command.


—End—

Job aidThe following figure shows the command output.




.


Configuring port-mirroringUse this procedure to configure port mirroring.

Procedure Steps

Step Action


2 Enter the port-mirroring mode {disable | Xrx|Xtx|Xrx-OrXtx} monitor-port <portlist> mirror-port-X<portlist> command.


—End—

Variable definitionsThe following table describes the command variables.

Variable Definition

disable Disables port-mirroring.

Xrx Mirror packets received on port X.

Xtx Mirror packets transmitted on port X.

XrxOrXtx Mirror packets received or transmitted on port X.

Disabling port-mirroringUse this procedure to disable port mirroring.

Procedure Steps

Step Action


2 Enter the no port-mirroring command.

—End—

Port statisticsThis section contains information about how you can display the statisticsfor a port for both received and transmitted traffic.




.

Port statistics 25

Navigation

• "Displaying port-statistics " (page 25)

• "Clearing statistical information" (page 26)

Displaying port-statisticsUse this procedure to display port statistics.

Procedure Steps

Step Action

1 Enter Interface configuration mode.

2 Enter the show port-statistics [port <portlist>]command.

—End—


Variable Definition

port <portlist>Specifies the port numbers to display statistics about.

ATTENTIONIf you omit this parameter, the system uses the portnumber you specified when selecting the interface.

Job aidThe following image is an example of the command output.




.


Clearing statistical informationUse this command to clear all statistical information for the specified portand set all counters to zero (0).

Procedure Steps

Step Action

1 Enter Interface configuration mode.

2 Enter the clear-stats [port <portlist>] command.

—End—





.

Stack health 27

Variable Definition

port <portlist>Specifies the port numbers to display statistics about.

ATTENTIONIf you omit this parameter, the system uses the portnumber you specified when selecting the interface.

Stack healthThis section describes how you can view and configure stack healthparameters.

Navigation

• "Viewing stack health" (page 27)

• "Viewing stack monitor information" (page 27)

• "Configuring the stack monitor" (page 28)

Viewing stack healthUse this procedure to display the stack health information.

Procedure Steps

Step Action

1 Enter the show stack health command.

2 Observe the NNCLI output.

—End—

Viewing stack monitor informationUse this procedure to display the current configuration values for the stackmonitor.

Procedure Steps

Step Action

1 Enter the show stack-monitor command.





.


—End—

Configuring the stack monitorUse this procedure to configure the values for the stack monitor.

Procedure Steps

Step Action

1 Enter the config stack-monitor {enable [stack-size<2-8>][trap-interval <30-300>]} command.


—End—

Variable definitionsThe following table describes the command parameters.

Variable Definition

enable Enable stack monitoring.

stack-size <2-8> Set stack size to be monitored in the range of 2 to 8.

trap-interval <30-300> Set interval between traps in the range of 30 to 300seconds.

Disabling the stack monitorUse this procedure to disable the stack monitor.

Procedure Steps

Step Action

1 Enter the no stack-monitor command to disable stackmonitoring.

2 Observe the command output.

—End—




.

29

Network monitoring configurationusing Device Manager

This chapter describes how to use Device Manager to configure systemlogging and to display chassis and port statistics for the Ethernet RoutingSwitch 2500 Series.


• "Viewing the system log settings " (page 30)

• "Viewing the Remote System Log tab" (page 32)

• "Graphing chassis statistics" (page 33)

• "Graphing port statistics" (page 41)

• "Configuring the stack monitor " (page 47)

CPU and memory utilizationUse this procedure to view both CPU and memory utilization.

Procedure Steps

Step Action

1 Navigate to Edit, Chassis

2 Select the CPU/Mem Utilization tab

3 Click the Refresh button to update the data.

—End—

Job AidThe following table describes the fields on the CPU/Mem Utilization tab.




.

30 Network monitoring configuration using Device Manager

Field Description

Unit The numerical representation of theunit.

Last10Seconds CPU usage, in percentage, for the last10 seconds.

Last1Minute CPU usage, in percentage, for the lastminute.

Last10Minutes CPU usage, in percentage, for the last10 minutes.

Last1Hour CPU usage, in percentage, for the lasthour.

Last24Hours CPU usage, in percentage, for the last24 hours.

TotalCPUUsage Memory usage in megabytes.

MemoryTotalMB Total memory present, in megabytes,on the unit.

MemoryAvailableMB Memory remaining available on theunit.

Viewing the system log settingsUse this procedure to view System Log Settings information.

Procedure Steps

Step Action

1 From the Device Manager menu bar, select Edit, Diagnostics,System Log.

2 Select the System Log Settings tab if it is not already displayed.

—End—

Job aidThe following table describes the System Log Settings fields.




.

Viewing the system log settings 31

Field Description

OperationEnables you to store or discard generated logmessages.

Specifying on stores log messages in thelog message buffer facility according to theparameters specified by related managementobjects. Specifying off discontinues log messageaccumulation.

ATTENTIONThis does not affect operation of the remotesyslog facility, it only determines whether logmessages are stored locally.

BufferFullAction Specifies the action to take when buffer space isexhausted.

Overwrite causes the previous messages to be overwritten. Messages are overwritten based on First InFirst Out (FIFO). Specifying latch causes no moremessages to be saved until this object is changed tooverwrite or until the buffer space is made availablethrough some other means (for example, clearingthe buffer).

Volatile—CurSize Displays the current number of log messages in thevolatile portion of the system log message facility.Messages that are classified as volatile are lostupon system reinitialization.

Volatile—SaveTargets Determines the type of log messages that are savedin the log message buffer facilities. Messages areclassified based on their type.

Selecting the type - Critical(1), Serious(2), orInformational(3), causes all log messages with anassociated value less than or equal to the typevalue specified to be saved when the log messageis entered into the system.

For example, specifying the value Critical(1) causesonly messages classified as critical to be savedto nonvolatile storage. Specifying Serious(2)




.


Field Description

causes critical and serious messages to be saved.Specifying a value of None(4) means no logmessages are stored in volatile memory.

non-Volatile—CurSize Displays the current number of log messages thatare present in the nonvolatile portion of the systemlog message facility.

Messages that are classified as nonvolatile aresaved across system reinitializations.

non-Volatile—SaveTargets

Determines the type of log messages that are savedto nonvolatile storage when they occur. Messagesare classified based on their type.

Selecting a type value causes all log messages withan associated value less than or equal to the typevalue specified to be saved when the log messageis entered into the system.

For example, specifying the value Critical(1) causesonly messages classified as critical to be savedto nonvolatile storage. Specifying Serious(2)causes critical and serious messages to be saved.Specifying None(4) causes no messages to besaved.

ClearMessageBuffers Indicates that the messages currently saved inthe log message buffer are to be deleted. Allmessages of types matching the specified bits aredeleted. For example, specifying volInformationaldeletes all informational messages and specifyingnonVolCritical deletes all critical messages fromnonvolatile storage.

Viewing the Remote System Log tabUse this procedure to view Remote System Log information.

Procedure Steps

Step Action

1 From the Device Manager menu bar, select Edit, Diagnostics,System Log.

2 Click the Remote System Log tab.

—End—




.

Graphing chassis statistics 33

Job aidThe following table describes the Remote System Log tab fields.

Field Description

Address Specifies the IP address of the remote system.

Enabled Determines whether remote logging is enabled ordisabled.

SaveTargets Determines the type of log messages that are savedin the log message buffer facilities. Messages areclassified based on their type.

Selecting a type of critical, critical/serious, orcritical/serious/inform causes all log messages withthe type value specified to be saved when the logmessage is entered into the system.

For example, specifying the value critical causesonly messages classified as critical to be sentto the remote system. Specifying critical/seriouscauses critical and serious messages to be saved.Specifying a value of none means no log messagesare sent to the remote system.

Graphing chassis statisticsUse the following procedure to graph chassis statistics

Procedure Steps

Step Action

1 From the Device Manager main menu, select Edit, Select, Chassis.

2 Do one of the following:

• From the Device Manager main menu, select Graph, Chassis.

• From the toolbar, selectGraph Selected.

—End—

The following sections contains information about the Graph Chassis dialogbox tabs with descriptions of the statistics on each tab.

• "Viewing IP statistics" (page 34)




.


• "Viewing ICMP In statistics" (page 36)

• "Viewing ICMP Out statistics" (page 37)

• "Viewing TCP statistics" (page 38)

• "Viewing UDP statistics" (page 40)

For more information about the SNMP tab, see Nortel Ethernet RoutingSwitch 2500 Series Security — Configuration and Management(NN47215-505).

Viewing IP statisticsUse this procedure to view the IP tab.

Step Action

1 Select Edit, Select, Chassis.


• From Device Manager main menu, select Graph, Chassis.

• On the toolbar, click Graph.

The Chassis dialog box appears with the SNMP tab displayed.

3 Click the IP tab.

The IP tab appears.

—End—

Job aidThe following table describes the Chassis IP tab fields.

Field Description

InReceives The total number of input datagrams received frominterfaces, including those received in error.

InHdrErrors The number of input datagrams discarded due to errorsin their IP headers, including bad checksums, versionnumber mismatch, other format errors, time-to-liveexceeded, errors discovered in processing their IPoptions.




.


Field Description

InAddrErrors The number of input datagrams discarded because theIP address in the IP header destination field was not avalid address. This count includes invalid addresses(for example, 0.0.0.0) and addresses of unsupportedClasses (for example, Class E). For addresses thatare not IP Gateways and therefore do not forwarddatagrams, this counter includes datagrams discardedbecause the destination address was not a localaddress.

ForwDatagrams The number of input datagrams for which this entity wasnot their final IP destination, as a result of which anattempt was made to find a route to forward them tothat final destination. For addresses that do not act asIP Gateways, this counter includes only those packetsSource-Routed by way of this address with successfulSource-Route option processing.

InUnknownProtos The number of locally addressed datagrams receivedsuccessfully but discarded because of an unknown orunsupported protocol.

InDiscards The number of input IP datagrams for which noproblems are encountered to prevent their continuedprocessing, but that are discarded (for example, for lackof buffer space). Note that this counter does not includeany datagrams discarded while awaiting reassembly.

InDelivers The total number of input datagrams successfullydelivered to IP user-protocols (including ICMP).

OutRequests The total number of IP datagrams that local IPuser-protocols (including ICMP) supplied to IP inrequests for transmission. Note that this counter doesnot include any datagrams counted in ipForwDatagrams.

OutDiscards The number of output IP datagrams for which noproblem was encountered to prevent their transmissionto their destination, but that are discarded (for example,for lack of buffer space). Note that this counter caninclude datagrams counted in ipForwDatagrams if anysuch packets met this (discretionary) discard criterion.

OutNoRoutes The number of IP datagrams discarded because noroute can be found to transmit them to their destination.Note that this counter also includes any packets countedin ipForwDatagrams that have no route. Note that thisincludes any datagrams a host cannot route because allof its default gateways are down.

FragOKs The number of IP datagrams successfully fragmentedat this entity.




.


Field Description

FragFails The number of IP datagrams that are discarded becausethey need to be fragmented at this entity but cannot be,for example, because their Don’t Fragment flag was set.

FragCreates The number of generated IP datagram fragmentsbecause of a fragmentation at this entity.

ReasmReqds The number of IP fragments received that needed to bereassembled at this entity.

ReasmOKs The number of IP datagrams successfully reassembled.

ReasmFails The number of failures detected by the IP reassemblyalgorithm (for example, timed out, errors). Note that thisis not necessarily a count of discarded IP fragmentsbecause some algorithms (notably the algorithm inRFC 815) can lose track of the number of fragments bycombining them as they are received.

Viewing ICMP In statisticsUse this procedure to to open the ICMP In tab and show ICMP In statistics.

Procedure Steps

Step Action






3 Click ICMP In .

The ICMP In tab appears.

—End—

Job aidThe following table describes the ICMP In tab fields.

Field Description

SrcQuenchs The number of ICMP Source Quench messagesreceived.

Redirects The number of ICMP Redirect messages received.




.


Field Description

Echos The number of ICMP Echo (request) messagesreceived.

EchoReps The number of ICMP Echo Reply messages received.

Timestamps The number of ICMP Timestamp (request) messagesreceived.

TimestampReps The number of ICMP Timestamp Reply messagesreceived.

AddrMasks The number of ICMP Address Mask Request messagesreceived.

AddrMaskReps The number of ICMP Address Mask Reply messagesreceived.

ParmProbs The number of ICMP Parameter Problem messagesreceived.

DestUnreachs The number of ICMP Destination Unreachablemessages received.

TimeExcds The number of ICMP Time Exceeded messagesreceived.

Viewing ICMP Out statisticsThe chassis ICMP Out shows ICMP Out statistics.

To open the ICMP Out tab, use the following procedure:

Step Action






3 Click ICMP Out .

The ICMP Out tab appears.

—End—

ICMP Out tab fieldsThe following table describes the ICMP Out tab fields.




.


Field Description

SrcQuenchs The number of ICMP Source Quench messages sent.

Redirects The number of ICMP Redirect messages received. Fora host, this object is always zero because hosts do notsend redirects.

Echos The number of ICMP Echo (request) messages sent.

EchoReps The number of ICMP Echo Reply messages sent.

Timestamps The number of ICMP Timestamp (request) messagessent.

TimestampReps The number of ICMP Timestamp Reply messages sent.

AddrMasks The number of ICMP Address Mask Request messagessent.

AddrMaskReps The number of ICMP Address Mask Reply messagessent.

ParmProbs The number of ICMP Parameter Problem messagessent.

DestUnreachs The number of ICMP Destination Unreachablemessages sent.

TimeExcds The number of ICMP Time Exceeded messages sent.

Viewing TCP statisticsUse this procedure to open the TCP tab and view TCP statistics.

Procedure Steps

Step Action






3 Click TCP.

The TCP tab appears.

—End—




.


Job aidThe following table details the fields in the TCP tab.

Field Description

ActiveOpens The number of times TCP connections make a directtransition to the SYN-SENT state from the CLOSEDstate.

PassiveOpens The number of times TCP connections make a directtransition to the SYN-RCVD state from the LISTENstate.

AttemptFails The number of times TCP connections make adirect transition to the CLOSED state from eitherthe SYN-SENT state or the SYN-RCVD state, plusthe number of times TCP connections make a directtransition to the LISTEN state from the SYN-RCVDstate.

EstabResets The number of times TCP connections make adirect transition to the CLOSED state from either theESTABLISHED state or the CLOSE-WAIT state.

CurrEstab The number of TCP connections for which the currentstate is either ESTABLISHED or CLOSE-WAIT.

InSegs The total number of segments received, includingthose received in error. This count includes segmentsreceived on currently established connections.

OutSegs The total number of segments sent, including those oncurrent connections but excluding those containing onlyretransmitted octets.

RetransSegs The total number of segments retransmitted, that is, thenumber of TCP segments transmitted containing one ormore previously transmitted octets.

InErrs The total number of segments received in error (forexample, bad TCP checksums).

OutRsts The number of TCP segments sent containing the RSTflag.

HCInSegs The number of segments received, including thosereceived in error. This count includes segmentsreceived on currently established connections. Thisobject is the 64-bit equivalent of InSegs.

HCOutSegs The number of segments sent, including those oncurrent connections, but excluding those containing onlyretransmitted octets. This object is the 64-bit equivalentof OutSegs.




.


Viewing UDP statisticsUse this procedure to open the UDP tab and view UDP statistics.

Procedure Steps

Step Action






3 Click UDP.

The UDP tab appears.

—End—

Job aidThe following table details the fields on the UDP tab.

Field Description

InDatagrams The total number of UDP datagrams delivered to UDPusers.

NoPorts The total number of received UDP datagrams for whichthere was no application at the destination port.

InErrors The number of received UDP datagrams that cannotbe delivered for reasons other than the lack of anapplication at the destination port.

OutDatagrams The total number of UDP datagrams sent from thisentity.

HCInDatagrams The number of TCP connections for which the currentstate is either ESTABLISHED or CLOSE-WAIT.

HCOutDatagrams The number of UDP datagrams sent from this entity,for devices that can transmit more than 1 million UDPdatagrams for each second.Discontinuities in the value of this counter can occurat reinitialization of the management system, and atother times as indicated by discontinuities in the valueof sysUpTime.




.

Graphing port statistics 41

Graphing port statisticsYou can graph the following statistics for either a single port or multipleports from the graphPort dialog box:

• AbsoluteValue

• Cumulative

• Average/sec

• Minimum/sec

• Maximum/sec

• LastVal/sec

The windows that appear when you configure a single port differ from theones appearing when you configure multiple ports. However, the optionsare similar.

The figures in this section show graphs for multiple ports.

Use this procedure to open the graphPort dialog box for graphing.

Procedure Steps

Step Action

1 Select the port or ports you want to graph.

To select multiple ports, press Ctrl+left-click the ports that you wantto configure. A yellow outline appears around the selected ports.


• From the Device Manager main menu, select Graph, Port.

• From the shortcut menu, select Graph.


—End—

The graphPort dialog box for a single port or for multiple ports appears withthe Interface tab displayed.

ATTENTIONSome statistics are only available when you graph a single port.

Graphing the Interface tabThe Interface tab shows interface parameters for graphing a port or ports.




.


Use the following procedure to open the Interface tab for graphing.

Procedure Steps

Step Action

1 Select a single or multiple ports you want to graph.






The Port dialog box for a single port or for multiple ports appearswith the Interface tab displayed.

—End—

Job aidThe following table describes the Interface tab fields for graphing ports.

Field Description

InOctets The total number of octets received on the interface,including framing characters.

OutOctets The total number of octets transmitted out of theinterface, including framing characters.

InUcastPkts The number of packets delivered by this sublayer to ahigher sublayer that are not addressed to a multicast orbroadcast address at this sublayer.

OutNUcastPkts The total number of packets that higher-level protocolsrequested be transmitted, and that are addressedto a multicast or broadcast address at this sublayer,including those that are discarded or not sent.

InDiscards The number of inbound packets chosen to be discardedeven though no errors were detected to prevent theirbeing deliverable to a higher-layer protocol. Onepossible reason for discarding such a packet can be tofree up buffer space.




.


Field Description

OutDiscards The number of outbound packets chosen to bediscarded even though no errors were detected toprevent their being transmitted. One possible reason fordiscarding such a packet can be to free up buffer space.

InErrors For packet-oriented interfaces, the number of inboundpackets that contained errors preventing them frombeing deliverable to a higher-layer protocol. Forcharacter-oriented or fixed-length interfaces, the numberof inbound transmission units that contained errorspreventing them from being deliverable to a higher-layerprotocol.

OutErrors For packet-oriented interfaces, the number of outboundpackets that cannot be transmitted because of errors.For character-oriented or fixed-length interfaces, thenumber of outbound transmission units that cannot betransmitted because of errors.

InUnknownProtos For packet-oriented interfaces, the number ofpackets received via the interface that are discardedbecause of an unknown or unsupported protocol. Forcharacter-oriented or fixed-length interfaces that supportprotocol multiplexing, the number of transmission unitsreceived via the interface that are discarded because ofan unknown or unsupported protocol. For any interfacethat does not support protocol multiplexing, this counteris always zero.

InMulticastPkts The number of packets delivered by this sublayer toa higher sublayer that were addressed to a multicastaddress at this sublayer. For a MAC layer protocol, thisnumber includes both group and functional addresses.

OutMulticastPkts The number of packets that higher-level protocolsrequested be transmitted, and that are addressed toa multicast address at this sublayer, including thosethat were discarded or not sent. For a MAC layerprotocol, this number includes both group and functionaladdresses.

InBroadcastPkts The number of packets delivered by this sublayer toa higher sublayer that are addressed to a broadcastaddress at this sublayer.

OutBroadcastPkts The number of packets that higher-level protocolsrequested be transmitted, and that were addressed to abroadcast address at this sublayer, including those thatwere discarded or not sent.

Graphing the Ethernet Errors tabThe Ethernet Errors tab shows port Ethernet Errors statistics.




.


Use the following procedure to open the Ethernet Errors tab for graphing,

Procedure Steps

Step Action







The Graph Port dialog box for a single port or for multiple portsappears with the Interface tab displayed.

3 Click Ethernet Errors.

The Ethernet Errors tab appears.

—End—

Job aidThe following table describes the Ethernet Errors tab fields.

Field Description

AlignmentErrors A count of frames received on a particular interfacethat are not an integral number of octets in length anddo not pass the FCS check. The count representedby an instance of this object is incremented when theAlignmentError status is returned by the MAC service tothe LLC (or other MAC user). Received frames for whichmultiple error conditions occur are, according to theconventions of IEEE 802.3 Layer Management, countedexclusively according to the error status presented tothe LLC.




.


Field Description

FCSErrors A count of frames received on a particular interfacethat are an integral number of octets in length, but donot pass the FCS check. The count represented byan instance of this object is incremented when theFCSErrors status is returned by the MAC service to theLLC (or other MAC user). Received frames for whichmultiple error conditions occur are, according to theconventions of IEEE 802.3 Layer Management, countedexclusively according to the error status presented tothe LLC.

InternalMacTransmitErrors

A count of frames for which transmission on a particularinterface fails due to an internal MAC sublayer transmiterror. A frame is only counted by an instance ofthis object if it is not counted by the correspondinginstance of either the LateCollisions object, theExcessiveCollisions object, or the CarrierSenseErrorsobject.

InternalMacReceiveErrors

A count of frames for which reception on a particularinterface fails due to an internal MAC sublayer receiveerror. A frame is only counted by an instance ofthis object if it is not counted by the correspondinginstance of either the FrameTooLongs object, theAlignmentErrors object, or the FCSErrors object.

The precise meaning of the count represented by aninstance of this object is implementation specific. Inparticular, an instance of this object can represent acount of receive errors on a particular interface that arenot otherwise counted.

CarrierSenseErrors The number of times that the carrier sense conditionwas lost or never asserted when attempting to transmita frame on a particular interface. The count representedby an instance of this object is incremented at mostonce per transmission attempt, even if the carrier sensecondition fluctuates during a transmission attempt.

FrameTooLongs A count of frames received on a particular interface thatexceed the maximum permitted frame size. The countrepresented by an instance of this object is incrementedwhen the FrameTooLongs status is returned by theMAC service to the LLC (or other MAC user). Receivedframes for which multiple error conditions occur are,according to the conventions of IEEE 802.3 LayerManagement, counted exclusively according to the errorstatus presented to the LLC.




.


Field Description

SQETestErrors A count of times that the SQE Test Errors message isgenerated by the PLS sublayer for a particular interface.The SQE TEST ERROR message is defined in section7.2.2.2.4 of ANSI/IEEE 802.3-1985 and its generation isdescribed in section 7.2.4.6 of the same document.

DeferredTransmissions

A count of frames for which the first transmission attempton a particular interface is delayed because the mediumis busy. The count represented by an instance of thisobject does not include frames involved in collisions.

SingleCollisionFrames

A count of successfully transmitted frames on aparticular interface for which transmission is inhibitedby exactly one collision. A frame that is countedby an instance of this object is also counted by thecorresponding instance of either the ifOutUcastPkts,ifOutMulticastPkts, or ifOutBroadcastPkts, and isnot counted by the corresponding instance of theMultipleCollisionFrames object.

MultipleCollisionFrames

A count of successfully transmitted frames on aparticular interface for which transmission is inhibitedby more than one collision. A frame that is countedby an instance of this object is also counted by thecorresponding instance of either the ifOutUcastPkts,ifOutMulticastPkts, or ifOutBroadcastPkts, and isnot counted by the corresponding instance of theSingleCollisionFrames object.

LateCollisions The number of times that a collision is detected on aparticular interface later than 512 bit-times into thetransmission of a packet. Five hundred and twelvebit-times corresponds to 51.2 microseconds on a 10Mb/s system. A (late) collision included in a countrepresented by an instance of this object is alsoconsidered as a (generic) collision for purposes of othercollision-related statistics.

ExcessiveCollisions A count of frames for which transmission on a particularinterface fails due to excessive collisions.

Misc. Stats tabThe Misc. Stats tab shows miscellaneous port statistics.

Use the following procedure to open the Misc. Stats tab for graphing.

Procedure Steps

Step Action





.

Configuring the stack monitor 47

2 From the Device Manager main menu, select Graph, Port.

The Graph Port dialog box appears with the Interface tab displayed.

3 Click Misc. Stats.

The Misc. Stats tab appears.

—End—

Job aidThe following table describes the Misc. Stats tab fields.

Field Description

NoResourcesPktsDropped

The number of packets dropped due to switch memoryshortage.

Configuring the stack monitorUse this procedure to configure stack monitor parameters with DM.

Procedure Steps

Step Action

1 Select Edit, Chassis in DM

2 Select the Stack Monitor tab.

3 Input the required parameters.

4 Click Apply to apply new settings.

—End—

Job aidThe following table describes the fields on the Stack Monitor tab.

Parameter Description

StackErrorNotificationEnabled Enable or disable stack monitoring.

ExpectedStackSize Set stack size to be monitored in therange of 2 to 8.

StackErrorNotificationInterval Set interval between traps in the rangeof 30 to 300 Seconds.




.





.

49

Network monitoring configurationusing Web-based management

This chapter describes how you can configure network monitoring featuresusing web-based management.


• "Using the trap Web page to identify trap receivers" (page 49)

• "Viewing the system log" (page 51)

• "Configuring port mirroring" (page 52)

• "Viewing statistics" (page 53)

• "Monitoring MLT traffic" (page 60)

CPU and memory utilizationUse this procedure to view both CPU and memory utilization.

Procedure Steps

Step Action

1 Navigate to Administration, CPU / Memory Utilization

2 Observe the information displayed.

—End—

Using the trap Web page to identify trap receiversUse the following procedure to identify the trap receivers.




.

50 Network monitoring configuration using Web-based management

Configuring traps using the Trap Web Page

Step Action

1 Navigate to Configuration, SNMP Trap to view the SNMP trap page.

2 In the Trap Web Page area, select the trap receiver you wish to view.

3 Enable or disable the traps as required.

4 Click the Submit button.

—End—

Stack HealthUse this procedure to view stack health information.

Procedure Steps

Step Action

1 Navigate to Summary, Stack Health

2 Observe the information displayed.

—End—

Job AidThe following table describes the fields on the Stack Health Web page,Stack Links section.

Field Description

Unit Unit number in the stack.

Description Description of the unit.

Cascade Up Status of the stacking connection forthe up link.

Cascade Down Status of the stacking connection forthe down link.

Stack Role Identifies the role of the unit. In thecase of a base unit, the field will displaybase

.




.

Viewing the system log 51

The following table describes the fields on the Stack Health Web page,Diagnosis section.

Field Description

Stack Units Found Total number of units found in the stack.

Stack Health Check Health check for the stack.

Stack Diagnosis Description of the stack health.

Viewing the system logYou can view a display of messages in Nonvolatile Random Access Memory(NVRAM) or Dynamic Random Access Memory (DRAM) and NVRAM.

Use the following procedure to open the System Log page.

Step Action

1 From the main menu, select Fault, System Log.

The System Log page appears.

2 In the System Log (View By) section do one or more of thefollowing:

• select where you want to display messages.

• select to clear messages from Volatile or Non Volatile memory.

3 Click Submit.

The results of your request are displayed in the System Log section.

—End—

Job AidThe following table describes the fields on the System Log page.

Section Field Range Description

DisplayMessagesFrom

(1) Non Volatile(2) Volatile + NonVolatile

Choose to display messagesfrom NVRAM or DRAM andNon Volatile memory.

The default setting is NonVolatile.

SystemLog (ViewBy)

Clear Messages From

(1) Volatile(2) Volatile + NonVolatile

Choose to clear messagesfrom Volatile memory orVolatile and Non Volatilememory.




.


Section Field Range Description

(3) None If you clear Volatile messages,existing Non Volatilemessages are copied intoVolatile memory. After asystem reset, all existing NonVolatile messages are alsocopied to Volatile memory.The default settings is None(does not clear messages).

Index The number of the event.

Time Stamp

The time, in hundreths ofa second, between systeminitialization and the time thelog messages entered thesystem.

MessageType

The type of message. Theoptions are Critical (1), Serious(2), and Informational (3).

SystemLog

Message A character string thatidentifies the origin of themessage and the reason whythe message was generated.

Configuring port mirroringThe Ethernet Routing Switch 2500 Series supports port mirroring to analyzetraffic. You can view existing port mirroring activity and configure a specificswitch port to mirror one specified port.

Use this procedure to configure port mirroring.

Procedure Steps

Step Action

1 From the main menu, select Applications, Port Mirroring.

The Port Mirroring page appears.

2 Type information in the text boxes, or select from a list.

3 Click Submit.

—End—




.

Viewing statistics 53

Job aidThe following table describes the items on the Port Mirroring page.

Item Range Description

MonitoringMode

Disabled--> Port XPort X --><--> Port X

The default setting is Disabled.Monitor all traffic received by Port X.Monitor all traffic transmitted by Port X.Monitor all traffic received andtransmitted by Port X.

Monitor Port 1..52 Choose the switch port to designate asthe monitor port.

Port X 1..52 Choose the switch port to be monitoredby the designated monitor port. Thisport is monitored according to the valueX in the Monitoring Mode field.

Viewing statisticsThis section describes the use of Web-based management to monitorsystem statistical data.

• "Viewing port statistics" (page 53)

• "Viewing interface statistics" (page 57)

• "Viewing Ethernet error statistics" (page 58)

• "Viewing transparent bridging statistics" (page 59)

• "Viewing port statistics" (page 53)

• "Viewing interface statistics" (page 57)

• "Viewing Ethernet error statistics" (page 58)

• "Viewing transparent bridging statistics" (page 59)

Viewing port statisticsYou can view detailed statistics about a selected switch port. Both receivedand transmitted statistics are displayed so that you can compare throughputor other port parameters.

Use the following procedure to view statistical data about a selected switchport.

Procedure Steps

Step Action

1 From the main menu, select Statistics, Port.

The Port page appears. .




.


2 In the Port Statistics section, select the port number.

3 Click Submit.

The Port Statistics Table is updated with information about theselected device and port.

4 To update the statistical information, click Update.

—End—

Job aidThe following table describes the items on the Port page, Port Statistics(View By) section.

Item Description

Port The switch port number to monitor.

The following table describes the items on the Port page, Port Statistic Tablesection.

Item Description

Packets The number of packets received and transmittedon this port, including bad packets, broadcastpackets, and multicast packets.

Multicasts The number of good multicast packets receivedand transmitted on this port, excluding broadcastpackets.

Broadcasts The number of good broadcast packets receivedand transmitted on this port.

Total Octets The number of octets of data received andtransmitted on this port, including data in badpackets and FCS octets, and framing bits.

Pause Frames The number of pause frames received andtransmitted on this port.Pause frames cause the transmitting port totemporarily suspend the transmission of packetswhen the receiving port’s frame buffer is full(gigabit ports only).

FCS/Frame Errors The number of valid-size packets received on thisport with proper framing but discarded becauseof FCS Errors.




.


Item Description

Undersized Packets The number of packets received on this port withfewer than 64 bytes and with proper CRC andframing (also known as short frames or runts).

Oversized Packets The number of packets that are received on thisport with proper CRC and framing that meet thefollowing requirements:

• 1518 bytes if no VLAN tag exists

• 1522 bytes if a VLAN tag exists

Filtered Packets The number of packets that are received onthis port and discarded because of the specificconfiguration. This counter does not count theFCS or Frames error packets. This countercounts packets discarded because STP is not setto forwarding, the frame setting in VLAN directsdiscarding, or there is a mismatch in ingress oregress port speeds.

Frame Errors The number of valid-size packets received on thisport with proper framing but discarded because ofFrame Errors.

Collisions The number of collisions detected on this port.

Single Collisions The number of packets that are transmittedsuccessfully on this port after a single collision.

Multiple Collisions The number of packets that are transmittedsuccessfully on this port after more than onecollision.

Excessive Collisions The number of packets lost on this port due toexcessive collisions.

Deferred Packets The number of frames that are delayed on thefirst transmission attempt, but never incurred acollision.

Late Collisions The number of packets collisions that occurredafter a total length of time that exceeded 512bit-times of packet transmission.

The following table describes the items on the Port page, Packets Receivedand Transmitted section.

Item Description

64 bytes The number of packets this size received andtransmitted successfully on this port.




.


Item Description

65-127 bytes The number of packets this size received andtransmitted successfully on this port.





1522- 9216 bytes (Jumbo) The number of packets this size received andtransmitted successfully on this port.

Zeroing portsUse the following procedure to clear the statistical information for a specificport.

Procedure Steps

Step Action




3 Select the Zero Port button to zero the data on the port.

—End—

Zeroing all portsUse the following procedure to clear the statistical information for all ports.

Procedure Steps

Step Action




3 Select the Zero All Ports button to zero all the data on all ports.




.


—End—

Viewing interface statisticsYou can view selected switch interface statistics.

Use this procedure to view an interface’s statistical information.

Procedure steps

Step Action

1 From the main menu, select Statistics, Interface.

The Interface page appears.

2 To update the statistical information, select the Update button.

—End—

Job aidThe following table describes the Interface page items.

Item Description

Port The port number corresponding to the selected switch.

In Octets The number of octets received on the interface, includingframing characters.

Out Octets The number of octets transmitted out of the interface, includingframing characters.

In Unicast The number of subnetwork-unicast packets delivered to ahigher-layer protocol.

Out Unicast The number of packets that higher-layer protocols requested betransmitted to a subnetwork-unicast address, including thosethat are discarded or not sent.

In Non-Unicast

The number of non-unicast packets, for example,subnetwork-broadcast or subnetwork-multicast packets,delivered to a higher protocol.

OutNon-Unicast

The number of packets that higher-level protocols requestedbe transmitted to a non-unicast address. For example, asubnetwork-broadcast or a subnetwork multicast address,including those that are discarded or not sent.




.


Item Description

In Discards The number of inbound packets that were selected to bediscarded even though no errors were detected to prevent theirbeing delivered to a higher-layer protocol. Packet discardingis not arbitrary. One reason for discarding packets is to freebuffer space.

Out Discards The number of outbound packets that were selected to bediscarded even though no errors were detected to preventtheir being transmitted. Packet discarding is not arbitrary. Onereason for discarding packets is to free buffer space.

In Errors The number of inbound packets that contained errors preventingthem from being deliverable to a higher-layer protocol.

Out Errors The number of outbound packets that could not be transmittedbecause of errors.

In UnknownProtocols

The number of packets received through the interface that werediscards due to an unknown or unsupported protocol.

Viewing Ethernet error statisticsYou can view Ethernet error statistics for each monitored interface linked tothe Ethernet Routing Switch 2500 Series.

Use the following procedure to view Ethernet error statistics.

Procedure Steps

Step Action

1 From the main menu, select Statistics, Ethernet Errors.

The Ethernet Errors page appears. .

2 To refresh the statistical information, click Update.

—End—

Job aidThe following table describes the Ethernet Errors page items.

Item Description

Port The port number corresponding to the selected switch.

FCS/Frame Errors The number of frames received on a particular interfacethat are an integral number of octets in length, but donot pass the FCS check.




.


Item Description

Internal MAC TransmitErrors

The number of frames for which transmission on aparticular interface fails due to an internal MAC sublayertransmit error. A frame only is counted by an instanceof this object if it is not counted by the correspondinginstance of either the dot3StatsLateCollisions object,the dot3StatsExcessiveCollisions object, or thedot3StatsCarrierSenseErrors object.

Internal MAC ReceiveErrors

The number of frames for which reception on aparticular interface fails due to an internal MAC sublayertransmit error. A frame only is counted by an instanceof this object if it is not counted by the correspondinginstance of either the dot3StatsLateCollisions object,the dot3StatsExcessiveCollisions object, or thedot3StatsCarrierSenseErrors object.

Carrier Sense Errors The number of times that the carrier sense conditionswere lost or never asserted when attempting to transmita frame on a particular interface.

SQE Test Errors The number of times that the SQE TEST ERRORmessage is generated by the PLS sublayer for aparticular interface. The SQE TEST ERROR is definedin section 7.2.2.2.4 of ANSI/IEEE 802.3-1985, and itsgeneration is described in section 7.2.4.6 of the samedocument.

DeferredTransmissions

The number of frames for which the first transmissionattempt on a particular interface is delayed because themedium is busy.

Single CollisionFrames

The number of successfully transmitted frames on aparticular interface for which transmission is inhibitedby more than one collision.

Multiple CollisionFrames

The number of successfully transmitted frames on aparticular interface for which transmission is inhibitedby a single collision.

Late Collisions The number of times a collision is detected on aparticular interface later than 512 bit-times into thetransmission of a packet.

Excessive Collisions The number of frames for which transmission on aparticular interface fails due to excessive collisions.

Viewing transparent bridging statisticsYou can view the transparent bridging statistics measured for eachmonitored interface on the device.

Use this procedure to view transparent bridging statistics.




.


Step Action

1 From the main menu, select Statistics, Transparent Bridging.

The Transparent Bridging page appears.

2 To refresh the statistical information, click Update.

—End—

Job aidThe following table describes the Transparent Bridging page items.

Item Description

Port The port number that corresponds to theselected switch.

InFrames The number of frames this port receives fromits segment. A frame received on the interfacecorresponding to this port is counted only if itis for a protocol being processed by the localbridging function, including bridge managementerrors.

OutFrames The number of frames this port transmits fromits segment. A frame received on the interfacecorresponding to this port is counted only if itis for a protocol being processed by the localbridging function, including bridge managementerrors.

InDiscards The number of valid frames received whichwere discarded by the forwarding process.

Monitoring MLT trafficYou can monitor the bandwidth usage for the MultiLink Trunk member portswithin each trunk in your configuration by selecting the traffic type to monitor.

Use this procedure to monitor MultiLink Trunk traffic.

Procedure Steps

Step Action

1 From the main menu, select Applications, MultiLink Trunk,Utilization.

The Utilization page appears.




.

Monitoring MLT traffic 61

2 In the MultiLink Trunk Utilization Selection section, type the Trunknumber and traffic type to be monitored.

3 Click Submit.

The results of your request are displayed in the MultiLink TrunkUtilization Table. .

—End—

Job aidThe following table describes the Utilization page items.

Section Item Range Description

Trunk 1..6 Choose the trunk to bemonitored.

MultiLink TrunkUtilization Selection(View By) Traffic

Type(1) RXand TX(2) RX(3) TX

Choose the traffic type to bemonitored for percentage ofbandwidth utilization.

Port A list of the trunk memberswitch ports that correspondto the trunk specified in theTrunk column.

Last 5Minutes%

The percentage of packets (ofthe type specified in the TrafficType field) used by the port inthe last five minutes. This fieldprovides a running averageof network activity, and isupdated every 15 seconds.

Last 30Minutes%

The percentage of packets (ofthe type specified in the TrafficType field) used by the port inthe last 30 minutes. This fieldprovides a running averageof network activity, and isupdated every 15 seconds.

MultiLink TrunkUtilization Table

Last Hour%

The percentage of packets (ofthe type specified in the TrafficType field) used by the port inthe last 60 minutes. This fieldprovides a running averageof network activity, and isupdated every 15 seconds.




.





.

63

RMON using the NNCLI

This section describes the CLI commands used to configure and manageRMON. For details see the following section:

• "Viewing the RMON alarms" (page 63)

• "Viewing the RMON events" (page 64)

• "Viewing the RMON history" (page 64)

• "Viewing the RMON statistics" (page 64)

• "Configuring RMON alarms" (page 65)

• "Deleting RMON alarms" (page 66)

• "Configuring RMON events settings" (page 66)

• "Deleting RMON events settings" (page 67)

• "Configuring RMON history settings" (page 67)

• "Deleting RMON history settings" (page 68)

• "Configuring RMON statistics settings" (page 69)

• "Deleting RMON statistics " (page 69)

Viewing the RMON alarmsUse this procedure to display information about RMON alarms.

Procedure Steps

Step Action

1 Enter Global Configuration mode

2 Enter the show rmon alarm command.


—End—




.

64 RMON using the NNCLI

Viewing the RMON eventsUse this procedure to display information about RMON events.

Procedure Steps

Step Action


2 Enter the show rmon event command.


—End—

Viewing the RMON historyUse this procedure to display information about the configuration of RMONhistory.

Procedure Steps

Step Action


2 Enter the show rmon history command.


—End—

Viewing the RMON statisticsUse this procedure to display information about the configuration of RMONstatistics.

Procedure Steps

Step Action


2 Enter the show rmon stats command.


—End—




.

Configuring RMON alarms 65

Configuring RMON alarmsUse this procedure to set RMON alarms and thresholds.

Procedure Steps

Step Action


2 Enter the rmon alarm <1-65535> <WORD> <1-2147483647>{absolute | delta}rising-threshold <-2147483648-2147483647>[<1-65535>]falling-threshold <-2147483648-2147483647>[<1-65535>][owner <LINE>] command.


—End—

Variable DefinitionsThe following table describes the parameters for this command.

Variable Definition

<1-65535> Unique index for the alarm entry.

<WORD> The MIB object to be monitored. This is an objectidentifier, and for most available objects, an Englishname can be used.

<1-2147483647> The sampling interval, in seconds.

absolute Use absolute values (value of the MIB object iscompared directly with thresholds).

delta Use delta values (change in the value of the MIB objectbetween samples is compared with thresholds).

rising-threshold<-2147483648-2147483647 >[<1-65535>]

The first integer value is the rising threshold value. Theoptional second integer specifies the event entry tobe triggered when the rising threshold is crossed. Ifomitted, or if an invalid event entry is referenced, noevent is triggered.Unique index for the alarm entry.




.


Variable Definition

falling-threshold<-2147483648-2147483647 >[<1-65535>]

The first integer value is the falling threshold value. Theoptional second integer specifies the event entry tobe triggered when the falling threshold is crossed. Ifomitted, or if an invalid event entry is referenced, noevent is triggered.Unique index for the alarm entry.

[owner <LINE>] Specify an owner string to identify the alarm entry.

Deleting RMON alarmsUse this procedure to delete RMON alarm table entries. When the variableis omitted, all entries in the table are cleared.

Deleting the RMON alarms using NNCLI

Step Action


2 Enter the no rmon alarm [<1-65535>] command.


—End—


Variable Definition

<1-65535> Unique identifier of the alarm.

Configuring RMON events settingsUse this procedure to configure RMON event log and trap settings.

Procedure Steps

Step Action


2 Enter the rmon event <1-65535> [log] [trap][description <LINE>] [owner <LINE>] command.





.

Configuring RMON history settings 67

—End—

Variable DefinitionsThe following table describes the command parameters

Variable Definition

<1-65535> Unique index for the event entry.

[log] Record events in the log table.

[trap] Generate SNMP trap messages for events.

[description <LINE>] Specify a textual description for the event.

[owner <LINE>] Specify an owner string to identify the event entry.

Deleting RMON events settingsUse this procedure to delete RMON event table entries. When the variableis omitted, all entries in the table are cleared.

Procedure Steps

Step Action


2 Enter the no rmon alarm [<1-65535>] command.


—End—


Variable Definition


Configuring RMON history settingsUse this procedure to configure RMON history settings.




.


Procedure Steps

Step Action


2 Enter the rmon history <1-65535> <LINE> <1-65535><1-3600> [owner <LINE>] command.


—End—


Variable Definiton

<1-65535> Unique index for the history entry.

<LINE> Specify the port number to be monitored.

<1-65535> The number of history buckets (records) to keep.

<1-3600> The sampling rate (how often a history sample iscollected).

[owner <LINE>] Specify an owner string to identify the history entry.

Deleting RMON history settingsUse this procedure to delete RMON history table entries.

Procedure Steps

Step Action


2 Enter the no rmon history [<1-65535>] command.


—End—


Variable Definition





.

Deleting RMON statistics 69

Configuring RMON statistics settingsUse this procedure to configure RMON statistics settings.

Configuring RMON statistics settings using NNCLI

Step Action


2 Enter the rmon stats <1-65535> <LINE> [owner <LINE>]command.


—End—

Run the rmon stats command in Global Configuration command mode.

Variable DefinitionThe following table describes the command parameters.

Variable Definition

<1-65535> Unique index for the stats entry.

[owner <LINE>] Specify an owner string to identify the stats entry.

Deleting RMON statisticsUse this procedure to disable RMON statistics. When the variable isomitted, all entries in the table are cleared.

Procedure StepsI

Step Action


2 Enter the no rmon stats [<1-65535>] command.


—End—





.


Variable Definition





.

71

RMON using Device Manager

The Remote Network Monitoring (RMON) MIB is an interface between theRMON agent on an Ethernet Routing Switch 2500 Series and an RMONmanagement application, such as the Device Manager.

The RMON agent defines objects that are suitable for the management ofany type of network, but some groups are targeted for Ethernet networksin particular.

The RMON agent continuously collects statistics and monitors switchperformance. You can view this data through the Device Manager.

RMON has three major functions:

• creating and displaying alarms for user-defined events

• gathering cumulative statistics for Ethernet interfaces

• tracking a history of statistics for Ethernet interfaces

Navigation• "Working with RMON information" (page 71)

• "Creating an alarm" (page 79)

• "Deleting an alarm" (page 81)

• "Viewing RMON statistics and history" (page 82)

• "Using RMON events" (page 84)

• "Viewing RMON log information" (page 86)

Working with RMON informationYou can view RMON information by looking at the Graph informationassociated with the port or chassis.

Viewing statisticsYou can use Device Manager to gather Ethernet statistics that you cangraph in a variety of formats. You can save them to a file and export thestatistics to an outside presentation or graphing application.




.

72 RMON using Device Manager

Use the following procedure to view RMON Ethernet statistics.

Procedure Steps

Step Action

1 Select an object (port).




The Graph Port dialog box appears with the Interface tab displayed.

3 Click RMON.

The RMON tab appears.

—End—

Job aidThe following table describes RMON tab fields.

Field Description

Octets The total number of octets of data (including thosein bad packets) received on the network (excludingframing bits but including FCS octets). You can use thisobject as a reasonable estimate of Ethernet utilization.For greater precision, sample the etherStatsPkts andetherStatsOctets objects before and after a commoninterval.

Pkts The total number of packets (including bad packets,broadcast packets, and multicast packets) received.

BroadcastPkts The total number of good packets received that aredirected to the broadcast address. Note that this doesnot include multicast packets.

MulticastPkts The total number of good packets received that aredirected to a multicast address. Note that this numberdoes not include packets directed to the broadcastaddress.

CRCAlignErrors The total number of packets received with a length(excluding framing bits, but including FCS octets) ofbetween 64 and 1518 octets, inclusive, but with eithera bad FCS with an integral number of octets (FCSError) or a bad FCS with a nonintegral number of octets(Alignment Error).




.

Working with RMON information 73

Field Description

UndersizePkts The total number of packets received that are less than64 octets long (excluding framing bits but including FCSoctets) and were otherwise well formed.

OversizePkts The total number of packets received that are longerthan 1518 octets (excluding framing bits but includingFCS octets) and were otherwise well formed.

Fragments The total number of packets received that are less than64 octets in length (excluding framing bits but includingFCS octets) and with either a bad FCS with an integralnumber of octets (FCS Error) or a bad FCS with anonintegral number of octets (Alignment Error). ForetherStatsFragments to increment is normal because itcounts both runts (which are normal occurrences due tocollisions) and noise hits.

Collisions The best estimate of the total number of collisions onthis Ethernet segment.

Jabbers The total number of packets received that are longerthan 1518 octets (excluding framing bits, but includingFCS octets), withd either a bad FCS with an integralnumber of octets (FCS Error) or a bad FCS with anon-integral number of octets (Alignment Error). Jabberis defined as the condition where any packet exceeds20 ms. The allowed range to detect jabber is between20 ms and 150 ms.

1 to 64 The total number of packets (including bad packets)received that are less than or equal to 64 octets in length(excluding framing bits but including FCS octets).

65 to 127 The total number of packets (including bad packets)received that are greater than 64 octets in length(excluding framing bits but including FCS octets).


256 to 511 The total number of packets (including bad packets)received that are greater than 255 octets in length(excluding framing bits but including FCSoctets).


1024..1518 The total number of packets (including bad packets)received that are greater than 1023 octets in length(excluding framing bits but including FCS octets).

The following table describes the types of statistics.




.


Statistic Description

Absolute The total count since the last time counters were reset.A system reboot resets all counters.

Cumulative The total count since the statistics tab was first opened.The elapsed time for the cumulative counter is displayedat the bottom of the graph window.

Average/sec The cumulative count divided by the cumulative elapsedtime.

Min/sec The minimum average for the counter for a given pollinginterval over the cumulative elapsed time.

Max/sec The maximum average for the counter for a given pollinginterval over the cumulative elapsed time.

LastVal/sec The average for the counter over the last polling interval.

Viewing historyEthernet history records periodic statistical samples from a network. Asample is called a history and is gathered in time intervals referred to asbuckets. Histories establish a time-dependent method for gathering RMONstatistics on a port. The default values for history are:

• Buckets are gathered at 30-minute intervals.

• Number of buckets gathered is 50.

Both the time interval and the number of buckets is configurable. However,when the last bucket is reached, bucket 1 is dumped and recycled to hold anew bucket of statistics. Then bucket 2 is dumped, and so forth.

To view RMON history, use the following procedure:

Step Action

1 From the Device Manager main menu, select RMON, Control.

2 The RMON Control dialog box appears, with the History tabdisplayed.

—End—

Creating history itemsYou can use RMON to collect statistics at intervals. For example, if youwant cntRMON statistics to be gathered over the weekend, enough bucketsto cover two days is required. To do this, set the history to gather one




.


bucket each hour, thus covering a 48-hour period. After you set historycharacteristics, you cannot modify them; you must delete the history andcreate another one.

Use the following procedure to establish a history for a port and set thebucket interval.

Procedure Steps

Step Action


The RMONControl dialog box appears with the History tab displayed.

2 Click Insert button.

The RMONControl, Insert History dialog box appears.

3 Select the port from the port list or type the port number.

4 In the Buckets Requested box, type the number of buckets.

The default is 50.

5 In the Interval box, type the interval.

The default is 1800 seconds.

6 Type the owner, the network management system that created thisentry.

7 Click Insert.

—End—

RMON collects statistics using the index, port, bucket, and interval thatyou specified.

Job AidThe following table describes fields on the History tab.

Field Description

Index A unique value assigned to each interface. An indexidentifies an entry in a table.

Port Any Ethernet interface on the device.




.


Field Description

BucketsRequested The requested number of discrete time intervalsover which data is to be saved in the part of themedia-specific table associated with this entry.

BucketsGranted The number of discrete sampling intervals over whichdata is saved in the part of the media-specific tableassociated with this entry. The actual number of bucketsassociated with this entry can be less than the value ofthis object. In this case, at the end of each samplinginterval, a new bucket is added to the media-specifictable.

Interval The interval in seconds over which the data is sampledfor each bucket in the part of the media-specific tableassociated with this entry. You can set this interval toany number of seconds between 1 and 3600 (1 hour).Because the counters in a bucket can overflow at theirmaximum value with no indication, note the possibility ofoverflow in any of the associated counters. Consider theminimum time in which any counter could overflow on aparticular media type and set the historyControlIntervalobject to a value less than this interval. This minimumtime is typically most important for the octets counter inany media-specific table. For example, on an Ethernetnetwork, the etherHistoryOctets counter could overflowin about 1 hour at the maximum utilization of theEthernet.

Owner The network management system that created thisentry.

Disabling historyTo disable RMON history on a port, use the following procedure:

Step Action


The RMONControl dialog box appears with the History tab displayed.

2 Select the row that contains the port ID you want to delete.

3 Click Delete.

The entry is removed from the table.

—End—




.


Viewing RMON history statisticsDevice Manager lets you view RMON history statistics.

To display RMON History statistics, use the following procedure:

Step Action

1 In the RMON history tab, select an entry and click Graph.

2 The RMON history statistics dialog box appears.

—End—

RMON History fieldsThe following table describes the RMON History fields.

Field Description

SampleIndex An index that uniquely identifies the particular samplethis entry represents among all the samples associatedwith the same entry. This index starts at 1 and increasesby one as each new sample is taken.

Utilization The best estimate of the mean physical layer networkutilization on this interface during the sampling interval(in hundredths of a percent).

Octets The total number of octets of data (including thosein bad packets) received on the network (excludingframing bits but including FCS octets). You can use thisobject as a reasonable estimate of Ethernet utilization.For greater precision, sample the etherStatsPkts andetherStatsOctets objects before and after a commoninterval.

Pkts The total number of packets (including bad packets,broadcast packets, and multicast packets) received.

BroadcastPkts The total number of good packets received that aredirected to the broadcast address. Note that this doesnot include multicast packets.

MulticastPkts The total number of good packets received that aredirected to a multicast address. Note that this numberdoes not include packets directed to the broadcastaddress.

DropEvents The total number of events in which packets aredropped by the probe due to lack of resources duringthis sampling. This number is not necessarily thenumber of packets dropped; it is the number of timesthis condition has been detected.




.


Field Description

CRCAlignErrors The total number of packets received with a length(excluding framing bits, but including FCS octets)between 64 and 1518 octets, inclusive, but with eithera bad FCS with an integral number of octets (FCSError) or a bad FCS with a nonintegral number of octets(Alignment Error).

UndersizePkts The total number of packets received that are less than64 octets long (excluding framing bits but including FCSoctets) and were otherwise well formed.

OversizePkts The total number of packets received that are longerthan 1518 octets (excluding framing bits but includingFCS octets) and were otherwise well formed.

Fragments The number of packets received during the samplinginterval were less than 64 octets long (including FCSoctets, but not framing bits. The packets had a bad FCSwith either an integral number of octets (FCS Error), ora nonintegral number of octets (Alignment Error).

Collisions The best estimate of the number of collisions on anEthernet segment during a sampling interval.

Enabling Ethernet statistics gatheringUse this procedure to use RMON to gather Ethernet statistics.

Procedure Steps

Step Action


The RMON Control dialog box appears with the History tabdisplayed.

2 Click Ether Stats.

The Ether Stats tab appears.

Ether Stats tab fields

The following table describes the Ether Stats tab fields.

3 Click Insert.

The RMONControl, Insert Ether Stats dialog box appears.

4 Select the port(s).

Enter the port number you want or select the port from the list menu. The Device Manager assigns the index.




.

Creating an alarm 79

5 Click OK.

6 Click Insert.

The new Ethernet Statistics entry is displayed in the Ether Stats tab.

—End—

Job AidThe following table describes the fields in the Ether Stats tab.

Field Description

Index A unique value assigned to each interface. An indexidentifies an entry in a table.

Port Any Ethernet interface on the device.

Owner The network management system which created this entry.

Disabling Ethernet statistics gatheringUse the following procedure to disable Ethernet statistics that you have set.

Step Action


The RMONControl dialog box appears with the History tabdisplayed. .

2 Click Ether Stats.

The Ether Stats tab appears.

3 Select the row that contains the port ID you want to delete.

4 Click Delete.

The Ether Stats entry is removed from the table.

—End—

Creating an alarmUse this procedure to create an alarm to receive statistics and historyusing default values.




.


Procedure Steps

Step Action


• From the Device Manager main menu, select RMON, AlarmManager.

• On the toolbar, click Alarm Manager.

The Alarm Manager dialog box appears.

2 In the variable field, select a variable for the alarm from the list and aport (or other ID) on which you want to set an alarm.

Alarm variables are in three formats:

• A chassis alarm ends in .x where the x index is hard-coded. Nofurther information is required.

• A card, Spanning Tree Group (STG) or EtherStat alarm endswith a dot (.). You must enter a card number, STG ID, IP address,or EtherStat information.

• A port alarm ends with no dot or index and requires using theport shortcut menu. An example of a port alarm is ifInOctets(interface incoming octet count).

For this example, select Bridge, dot1dStpTopChanges.0 from thevariable list. This example is a chassis alarm, indicated by the.0 in the variable.

For this example, select Bridge, dot1dStpTopChanges.0 from thevariable list. This example is a chassis alarm, indicated by the.0 in the variable.

3 Select a rising and falling value.

4 Select the Insert button.

—End—

Job AidThe following table describes the RMON Insert Alarm dialog box field.




.

Deleting an alarm 81

Field Description

Variable Name and type of alarm—indicated by the format:

alarmname.x where x=0 indicates a chassis alarm.

alarmname. where the user must specify the index. Theindex is a card number for module-related alarms, anSTG ID for spanning tree group alarms (the default STGis 1, other STG IDs are user-configured), or the EtherStatistics Control Index for RMON Stats alarms.

alarmname with no dot or index is a port-related alarmand results in display of the port selection tool.

Sample Type Can be either absolute or delta.

Sample Interval Time period (in seconds) over which the data is sampledand compared with the rising and falling thresholds.

Index Uniquely identifies an entry in the alarm table. Eachsuch entry defines a diagnostic sample at a particularinterval for an object on the device.

Threshold Type Rising Value Falling Value

Value When the current sampledvalue is greater than orequal to this threshold,and the value at the lastsampling interval was lessthan this threshold, thealarm generates a singleevent.

When the current sampledvalue is less than or equalto this threshold, and thevalue at the last samplinginterval was greater thanthis threshold, the alarmgenerates a single event.

Event Index Index of the event entrythat is used when a risingthreshold is crossed. Theevent entry identified bya particular value of thisindex is the same asidentified by the samevalue of the event indexobject. (Generally, acceptthe default that is alreadyfilled in.)

Index of the event entrythat is used when a fallingthreshold is crossed. Theevent entry identified bya particular value of thisindex is the same asidentified by the samevalue of the event indexobject. (Generally, acceptthe default that is alreadyfilled in.)

Deleting an alarmUse this procedure to delete an alarm




.


Step Action

1 From the Device Manager main menu, select RMON, Alarms.

The RMONAlarms dialog box appears with the Alarms tab displayed.

2 Select any field for the alarm that you want to delete.

3 Click Delete.

—End—

Viewing RMON statistics and historyUse this procedure to view the RMON statistics and history for an alarmyou have created.

Procedure Steps

Step Action

1 Select the port on which you have created an alarm.


The RMONAlarms dialog box appears with the Alarms tab displayed.

—End—

Job AidThe following table describes the RMON Alarms dialog box fields.

Field Description

Index Uniquely identifies an entry in the alarm table. Each suchentry defines a diagnostic sample at a particular interval foran object on the device

Interval The interval in seconds over which data is sampled andcompared with the rising and falling thresholds. Whensetting this variable, note that in the case of deltaValuesampling, you should set the interval short enough so thatthe sampled variable is unlikely to increase or decrease bymore than 2^31 - 1 during a single sampling interval.

Variable The object identifier of the particular variable to be sampled.Only variables that resolve to an ASN.1 primitive type ofINTEGER (INTEGER, Counter, Gauge, or TimeTicks) maybe sampled.




.

Viewing RMON statistics and history 83

Field Description

Sample Type The method of sampling the selected variable andcalculating the value to be compared against the thresholds.If the value of this object is absoluteValue(1), the value of theselected variable is compared directly with the thresholds atthe end of the sampling interval. If the value of this objectis deltaValue(2), the value of the selected variable at thelast sample is subtracted from the current value, and thedifference compared with the thresholds.

Value The value of the statistic during the last sampling period. Forexample, if the sample type is deltaValue, this value is thedifference between the samples at the beginning and end ofthe period. If the sample type is absoluteValue, this valueis the sampled value at the end of the period. This value iscompared with the rising and falling thresholds. The valueduring the current sampling period is not made availableuntil the period is completed and remains available until thenext period is complete.

StartupAlarm The alarm that can be sent when this entry is first set to valid.If the first sample after this entry becomes valid is greaterthan or equal to the risingThreshold and alarmStartupAlarmis equal to risingAlarm(1) or risingOrFallingAlarm(3), thena single rising alarm is generated. If the first sampleafter this entry becomes valid is less than or equal tothe fallingThreshold and alarmStartupAlarm is equal tofallingAlarm(2) or risingOrFallingAlarm(3), then a singlefalling alarm is generated.

RisingThreshold A threshold for the sampled statistic. When the currentsampled value is greater than or equal to this threshold,and the value at the last sampling interval was lessthan this threshold, a single event is generated. Asingle event is also generated if the first sample afterthis entry becomes valid is greater than or equal to thisthreshold and the associated alarmStartupAlarm is equalto risingAlarm(1) or risingOrFallingAlarm(3). After a risingevent is generated, another such event is not generated untilthe sampled value falls below this threshold and reachesthe alarmFallingThreshold.

RisingEventIndex The index of the eventEntry that is used when a risingthreshold is crossed. The eventEntry identified by aparticular value of this index is the same as identified bythe same value of the eventIndex object. If there is nocorresponding entry in the eventTable, then no associationexists. In particular, if this value is zero, no associated eventis generated, because zero is not a valid event index.




.


Field Description

FallingThreshold A threshold for the sampled statistic. When the currentsampled value is less than or equal to this threshold,and the value at the last sampling interval is greaterthan this threshold, a single event is generated. A singleevent is also generated if the first sample after this entrybecomes valid is less than or equal to this threshold and theassociated alarmStartupAlarm is equal to fallingAlarm(2)or risingOrFallingAlarm(3). After a falling event isgenerated, another such event is not generated until thesampled value rises above this threshold and reaches thealarmRisingThreshold.

FallingEventIndex The index of the eventEntry that is used when a fallingthreshold is crossed. The eventEntry identified by aparticular value of this index is the same as identified bythe same value of the eventIndex object. If there is nocorresponding entry in the eventTable, then no associationexists. In particular, if this value is zero, no associated eventis generated, because zero is not a valid event index.

Owner The network management system which created this entry.

Status The status of this alarm entry.

Using RMON eventsThis section describes how RMON events and alarms work together tonotify you when values in your network are outside of a specified range.When values pass the specified ranges, the alarm is triggered and ittriggers. The event specifies how the activity is recorded.

Navigation

• "Viewing an event" (page 84)

• "Creating an event" (page 85)

• "Deleting an event" (page 86)

Viewing an eventUse this procedure to view a table of events.

Procedure Steps

Step Action


The RMONAlarms dialog box appears displaying the Alarms tab.

2 Click Events.




.

Using RMON events 85

The Events tab appears.

—End—

.

Job aidThe following table describes the RMONAlarms Events tab fields.

Field Description

Index This index uniquely identifies an entry in the event table.Each entry defines one event that is to be generated whenthe appropriate conditions occur.

Description Specifies whether the event is a rising or a falling event.

Type The type of notification that the Device Manager providesabout this event. In the case of log, an entry is made inthe log table for each event. In the case of trap, an SNMPtrap is sent to one or more management stations. Possiblenotifications are as follows:

• none

• log

• trap

• log-and-trap

Community The SNMP community string acts as a password. Onlythose management applications with this community stringcan view the alarms.

LastTimeSent The value of sysUpTime at the time this event entry lastgenerated an event. If this entry has not generated anyevents, this value is zero.

Owner If traps are specified to be sent to the owner, then this is thename of the machine that receives alarm traps.

Creating an eventUse this procedure to create an event.

Procedure Steps

Step Action

1 In the RMONAlarms dialog box Events tab, click Insert.

The RMONAlarms, Insert Events dialog box appears.




.


2 . In the Description field, type a name for the event.

3 Select the type of event you want.

You can set the event type to log to save memory or to snmp-trap toreduce traffic from the switch or for better CPU utilization.

If you select snmp-trap or log-and-trap, you must set trap receivers.

4 Click Insert.

The new event is displayed in the Events tab.

—End—

Deleting an eventUse this procedure to delete an event.

Procedure Steps

Step Action

1 In the Events tab, select an event Description.

2 Click Delete.

The event is removed from the table.

—End—

Viewing RMON log informationThe Log tab chronicles and describes the alarm activity, which is thengenerated to viewed.

Use the following procedure to view the Log tab.

Procedure Steps

Step Action


The RMONAlarm dialog box appears with the Alarms tab displayed.

2 Click Log.

The Log tab appears.

—End—




.

Viewing RMON log information 87

Job aidThe following table describes the Log tab fields.

Field Description

Time The value of sysUpTime when this log entry was created.

Description An implementation-dependent description of the event thatactivated the log entry.




.





.

89

RMON using Web-based management

The Remote Network Monitoring (RMON) Management Information Base(MIB) is an interface between the RMON agent on a Ethernet RoutingSwitch 2500 Series and RMON management applications such as theWeb-based management user interface. RMON MIB defines objects thatare suitable for the management of any type of network. Some groups arespecifically targeted for Ethernet networks.

The RMON agent continuously collects statistics and proactively monitorsthe switch.

Navigation• "Configuring RMON fault threshold parameters" (page 89)

• "Viewing the RMON fault event log" (page 93)

• "Viewing RMON Ethernet statistics" (page 94)

• "Viewing RMON history" (page 95)

Configuring RMON fault threshold parametersAlarms are useful when you need to know when the value of some variablegoes out of range. RMON alarms can be defined on any MIB variable thatresolves to an integer value. String variables (such as system description)cannot be used as alarm variables.

Navigation

• "Creating an RMON fault threshold" (page 89)

• "Deleting an RMON threshold configuration" (page 92)

Creating an RMON fault thresholdYou can create the RMON threshold parameters for fault notification(alarms).




.

90 RMON using Web-based management

ATTENTIONRMON threshold configurations are not modifiable. They must be deleted and theinformation recreated.

Use this procedure to create an RMON threshold.

Procedure Steps

Step Action

1 From the main menu, select Fault, RMON Threshold.

The RMON Threshold page appears.

2 In the RMON Threshold Creation section, type information in thetext boxes, or select from a list.

3 Click Submit.

—End—

Job aidThe following table describes the items on the RMON Threshold page.


Deletes the row.

Index/EventRisingIndex/EventFalling Index

1..10 Type the unique number to identify thealarm entry.

Target Integer The port number.

Port 1..25 The port on which to set an alarm.

Parameter (1) Good-Bytes(2) Good-Packets(3) Multicast(4) Broadcast(5) CRC-Errors(6) Runts(7) Fragments(8) Frame-Too-Long(9) Collisions

The sampled statistic.




.

Configuring RMON fault threshold parameters 91


Current Level IntegerThe value of the statistic during the lastsampling period.

ATTENTIONIf the sample type is delta, the value isthe difference between the samples atthe beginning and end of the period.If the sample type is Absolute, thevalue is the sampled value at the endof the period.

Rising Level IntegerType the event entry to be used when arising threshold is crossed.

ATTENTIONWhen the current sampled value isgreater than or equal to this threshold,and the value at the last samplinginterval was less than this threshold,a single event is generated. After arising event is generated, anothersuch event is not generated untilthe sampled value falls below thisthreshold and reaches the FallingThreshold.

Rising Action (1) Log(2) SNMP Trap(3) Log and Trap

Choose the type of notification for theevent. Selecting Log generates an entryin the RMON Event Log table for eachevent. Selecting SNMP Trap sends anSNMP trap to one or more managementstations.

Falling Level Integer Type the event entry to be used when aFalling Threshold is crossed.




.



Interval Type the time period (in seconds) tosample data and compare the data to therising and falling thresholds.

Sample/AlarmSample

(1) Absolute(2) Delta

Choose the sampling method.

Absolute: Absolute alarms are definedon the current value of the alarm variable.An example of an alarm defined withabsolute value is card operating status.Because this value is not cumulative, butinstead represents states, such as cardup (value 1) and card down (value 2), youset it for absolute value. Therefore, analarm can be created with a rising valueof 2 and a falling value of 1 to alert a userto whether the card is up or down.

Delta: Most alarm variables related toEthernet traffic are set to delta value.Delta alarms are defined based on thedifference in the value of the alarmvariable between the start of the pollingperiod and the end of the polling period.Delta alarms are sampled twice per pollingperiod. For each sample, the last twovalues are added together and comparedto the threshold values. This processincreases precision and allows for thedetection of threshold crossings that spanthe sampling boundary. Therefore, ifyou keep track of the current values of agiven delta-valued alarm and add themtogether, the result is twice the actualvalue. (This result is not an error in thesoftware.)

Deleting an RMON threshold configurationUse this procedure to delete an existing RMON threshold configuration.

Procedure Steps

Step Action

1 From the main menu, select Fault, RMON Threshold.

The RMON Threshold page appears.




.

Viewing the RMON fault event log 93

2 In the RMON Threshold Table, click theDelete icon for the entryyou want to delete.

A message appears prompting you to confirm your request.


• Click Yes to delete the RMON threshold configuration.

• Click Cancel to return to the RMON Threshold page withoutmaking changes.

—End—

Viewing the RMON fault event logRMON events and alarms work together to notify you when values in yournetwork go out of a specified range. When values pass the specifiedranges, the alarm triggers and triggers. The event specifies how the activityis recorded.

An event specifies whether a trap, a log, or a trap and a log are generatedto view alarm activity. When RMON is globally enabled, two default eventsare generated:

• Rising Event

• Falling Event

Default events specify that when an alarm goes out of range, the firing ofthe alarm is tracked in both a trap and a log. For example, when an alarmtriggers at the rising threshold, the rising event specifies that this informationbe sent to both a trap and a log. The RMON Event Log page works inconjunction with the RMON Threshold page to enable you to view a historyof RMON fault events.

Use the following procedure to view a history of RMON fault events.

Procedure Steps

Step Action

1 From the main menu, select Fault, RMON Event Log.

2 The RMON Event Log page appears.

—End—




.


Job aidThe following table describes the fields on the RMON Event Log page fields.

Field Description

Time Stamp The time the event occurred.

Description An implementation dependent description of the event thatactivated this log entry.

Triggered By A comment describing the source of the event.

ID The event that generated this log entry.

Viewing RMON Ethernet statisticsYou can gather and graph RMON Ethernet statistics in a variety of formats.

Use this procedure to gather and graph RMON Ethernet statistics.

Step Action

1 From the main menu, select Statistics, RMON Ethernet.

The RMON Ethernet page appears.

2 Click Submit.

The RMON Ethernet Statistics Table is updated with informationabout the selected device. .

—End—

Job aidThe following table describes the items on the RMON Ethernet page.

Item Description

Port The port number that corresponds to the selected switch.

Drop Events The number of events in which packets were dropped by theinterface due to a lack of resources.

Octets The number of octets of data (including those in bad packets)received on the network (excluding framing bits, but includingFrame Check Sequence (FCS) octets).

Packets The number of packets received and transmitted on a port,including bad, broadcast and multicast packets.

Broadcast The number of good packets received that are directed to thebroadcast address. This does not include multicast packets.




.

Viewing RMON history 95

Item Description

Multicast The number of good packets received that are directed to themulticast address. This does not include packets sent to thebroadcast address.

CRC AlignErrors

The number of packets received with a length (excluding and1518 octets, inclusive, but with either a bad Frame FCS with anintegral number of octets [FCS errors] with a nonintegral numberof octets [alignment error]).

Undersize The number of packets received that are less than 64 octetslong (excluding framing bits, but including FCS octets) and areotherwise well-formed.

Fragments The number of packets received that are less than 64 octets inlength (excluding framing bits, but including FCS octets) and hadeither a bad FCS with an integral number of octets (FCS Error)or a bad FCS with a non-integral number of octets (AlignmentError).

Collisions The best estimate number of collisions on this Ethernet segment.

Jabbers The number of packets received that are longer than 1518 octetsin length (excluding framing bits, but including FCS octets),and with either a bad FCS with an integral number of octets(FCS Error) or a bad FCS with a nonintegral number of octets(Alignment Error).

Packets< = 64 bytes65-127 bytes128-255 bytes256-511 bytes512-1023bytes1024-1518bytes1522- 9216bytes

The number of octets received (including bad packets) in length(excluding framing bits, but including FCS octets).

Viewing RMON historyYou can view a periodic statistical sampling of data from various types ofnetworks.

Use this procedure to view periodic statistical data.

Procedure Steps

Step Action

1 From the main menu, select Statistics, RMON History.

The RMON History page appears.




.


2 In the RMON History Statistics section, select the port number tobe monitored.

3 Click Submit.

The RMON History Statistics Table is updated with information aboutthe selected device and port.

—End—

Job aidThe following table describes the items on the RMON History page,Statistics Table (View By) section.

Item Description

Port The port number to be monitored.

The following table describes the items on the RMON History page,Statistics Table section.

Item Description

Start The value of the sysUPTime at the start of the interval overwhich this sample was measured.

Drop Events The number of events in which packets were dropped by theinterface due to a lack of resources.

Octets The number of octets of data (including those in badpackets) received on the network (excluding framing bits,but including FCS octets).

Packets The number of packets received and transmitted on a port,including bad, broadcast and multicast packets.

Broadcast The number of good packets received that are directed to thebroadcast address. This does not include multicast packets.

Multicast The number of good packets received that are directed tothe multicast address. This does not include packets sent tothe broadcast address.

CRC Align Errors The number of packets received with a length between 64and 1518 octets, but with either a bad Frame FCS with anintegral number of octets (FCS errors) with a nonintegralnumber of octets (alignment error).




.

Viewing RMON history 97

Item Description

Undersize The number of packets received that are less than 64 octetslong (excluding framing bits, but including FCS octets) andwere otherwise well-formed.

Oversize The number of packets received that are longer than 1518octets long (excluding framing bits, but including FCS octets)and were otherwise well-formed.




.





.

Nortel Ethernet Routing Switch 2500 Series

Configuration — System MonitoringCopyright © 2007-2008, Nortel NetworksAll Rights Reserved.

Publication: NN47215-502Document status: StandardDocument version: 03.01Document date: 27 October 2008

To provide a report a problem in this document, go towww.nortel.com/feedback

Sourced in Canada, India and the United States of America

The information in this document is subject to change without notice. Nortel Networks reserves the right to make changes in designor components as progress in engineering and manufacturing may warrant.

*Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Adobe and Adobe Reader are trademarks of Adobe Systems Incorporated.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.

Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

All other trademarks are the property of their respective owners.

http://support.avaya.com/supportfaqs

Documents

Nortel Ethernet Routing Switch 2500 Series Configuration ... · Nortel Ethernet Routing Switch 2500 Series Conﬁguration — System Monitoring NN47215-502