Configuration Network Management using NNCLI, CLI, and Device Manager

Transcription

1 Configuration Network Management using NNCLI, CLI, and Device Manager NN ( C Rev 01)

2 Document status: Standard Document version: 0301 Document date: 27 August 2007 All Rights Reserved Sourced in Canada and the United States of America The information in this document is subject to change without notice The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty Users must take full responsibility for their applications of any products specified in this document 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 accordance with the terms of that license The software license agreement is included in this document Restricted rights legend Use, 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 Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR Statement of conditions In the interest of improving internal design, operational function, and/or reliability, Nortel Networks reserves the right to make changes to the products described in this document without notice Nortel Networks does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein Portions of the code in this software product may be Copyright 1988, Regents of the University of California All rights reserved Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties) Nortel Networks software license agreement This Software License Agreement ("License Agreement") is between you, the end-user ("Customer") and Nortel Networks Corporation and its subsidiaries and affiliates ("Nortel Networks") PLEASE READ THE FOLLOWING CAREFULLY YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT If you do not accept these terms and conditions, return the Software, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price "Software" is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is copyrighted and licensed, not sold Software consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole

3 or partial copies Nortel Networks grants you a license to use the Software only in the country where you acquired the Software You obtain no rights other than those granted to you under this License Agreement You are responsible for the selection of the Software and for the installation of, use of, and results obtained from the Software 1 Licensed Use of Software Nortel Networks grants Customer a nonexclusive license to use a copy of the Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever is applicable To the extent Software is furnished for use with designated hardware or Customer furnished equipment ("CFE"), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or disseminate Customer will ensure that anyone who uses the Software does so only in compliance with the terms of this Agreement Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software Licensors of intellectual property to Nortel Networks are beneficiaries of this provision Upon termination or breach of the license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction Nortel Networks may audit by remote polling or other reasonable means to determine Customer s Software activation or usage levels If suppliers of third party software included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks with respect to such third party software 2 Warranty Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer, Software is provided "AS IS" without any warranties (conditions) of any kind NORTEL NETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT Nortel Networks is not obligated to provide support of any kind for the Software Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the above exclusions may not apply 3 Limitation of Remedies IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMER S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIR POSSIBILITY The foregoing limitations of remedies also apply to any developer and/or supplier of the Software Such developer and/or supplier is an intended beneficiary of this Section Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply 4 General a If Customer is the United States Government, the following paragraph shall apply: All Nortel Networks Software available under this License Agreement is commercial computer software and commercial computer software documentation and, in the event Software is licensed for or on behalf of the United States Government, the respective rights to the software and software documentation are governed by Nortel Networks standard commercial license in accordance with US Federal Regulations at 48 CFR Sections (for non-dod entities) and 48 CFR (for DoD entities) b Customer may terminate the license at any time Nortel Networks may terminate the license if Customer fails to comply with the terms and conditions of this license In either event, upon termination, Customer must either return the Software to Nortel Networks or certify its destruction c Customer is responsible for payment of any taxes, including personal property taxes, resulting from Customer s use of the Software Customer agrees to comply with all applicable laws including all applicable export and import laws and regulations d Neither party may bring an action, regardless of form, more than two years after the cause of the action arose e The terms and conditions of this License Agreement form the complete and exclusive agreement between Customer and Nortel Networks f This License Agreement is governed by the laws of the country in which Customer acquires the Software If the Software is acquired in the United States, then this License Agreement is governed by the laws of the state of New York

4

5 5 Contents New in this release 11 Features 11 Other changes 11 Preface 13 Before you begin 13 Text conventions 14 Acronyms 16 How to get help 16 Getting help from the Nortel web site 16 Getting help over the phone from a Nortel Solutions Center 17 Getting help from a specialist using an Express Routing Code 17 Getting help through a Nortel distributor or reseller 17 Switch management 19 Switch management tools 19 Device Manager 19 Web management interface 20 CLI 20 NNCLI 20 Dynamic network applications 24 SNMP 24 SNMP communities 25 RMON 26 CANA 26 FEFI 27 FEFI operation 27 Synchronizing the real-time and system clocks 29 Configuring RMON using Device Manager 31 Overview 31 RMON configuration using Device Manager 32 Enabling RMON globally using Device Manager 32 Configuring Ethernet statistics using Device Manager 32 Understanding RMON history using Device Manager 36 Configuring RMON alarms using Device Manager 40 NN Standard August 2007

6 6 Contents Understanding RMON events using Device Manager 47 Creating alarms 51 HP OpenView 53 RMON configuration using the CLI 55 Overview 55 Enabling remote access services using the CLI 55 RMON configuration 56 Enabling RMON globally using the CLI 56 Ethernet statistics using the CLI 57 Understanding RMON history using the CLI 60 Understanding RMON events using the CLI 68 Configuring RMON information using the CLI 70 RMON configuration using the NNCLI 75 Overview 75 RMON configuration using the NNCLI 75 Enabling RMON globally using the NNCLI 76 Ethernet statistics using the NNCLI 77 Understanding RMON history using the NNCLI 80 Configuring RMON alarms using the NNCLI 82 Understanding RMON events using the NNCLI 88 Configuring RMON information using the NNCLI 90 Viewing RMON settings using the NNCLI 91 Configuring the Web management interface using Device Manager 95 Monitoring the switch using Web management 95 Requirements 95 Installing Help files 96 Enabling the Web server using Device Manager 97 Accessing the Web interface 100 Troubleshooting Web interface access to a switch 101 Configuring the Web management interface using the CLI 103 Enabling the Web server using the CLI 103 Showing Web-server status 104 Configuring the Web management interface using the NNCLI 107 Enabling the Web server using the NNCLI 107 Configuring and graphing ports using Device Manager 109 Configuring a port using Device Manager 109 Editing ports using Device Manager 110 Setting a basic configuration using Device Manager 110 Viewing port state using Device Manager 114 Configuring and monitoring port mirroring using Device Manager 114 Configuring routing operations using Device Manager 117 NN Standard August 2007

7 Contents 7 Configuring VLANs using Device Manager 117 Configuring spanning tree groups (STG) using Device Manager 118 Configuring MAC learning parameters using Device Manager 120 Setting rate limits using Device Manager 121 Testing ports using Device Manager 123 Testing cables with the virtual cable tester (VCT) using Device Manager 124 Configuring transmit queue (TxQueue) using Device Manager 126 Configuring EAPoL using Device Manager 127 Configuring mroute stream limit using Device Manager 130 Graphing a port using Device Manager 131 Graphing port statistics using Device Manager 132 Graphing interface statistics using Device Manager 132 Graphing Ethernet error statistics using Device Manager 134 Graphing spanning tree statistics using Device Manager 136 Graphing RMON statistics using Device Manager 137 Graphing RMON History statistics using Device Manager 139 Configuring ports using the CLI 143 Configuring and monitoring port mirroring using the CLI 143 Creating an ingress port-mirror using the CLI 144 Deleting a port-mirror using the CLI 145 Changing the mode of a port-mirror 145 Changing a mirrored port using the CLI 145 Changing a mirroring/analyzer port using the CLI 145 Displaying information of port-mirror configuration in a switch using the CLI 146 Disabling a mirroring/analyzer port using the CLI 146 Configuring port parameters using the CLI 146 Setting rate limits using the CLI 149 Enabling rate limits on ingress traffic for a port using the CLI 149 Disabling broadcast and multicast rate limits using the CLI 150 Displaying rate limiting for a port using the CLI 151 Configuring port states using the CLI 151 Viewing port states using the CLI 152 Showing port statistics using the CLI 156 Showing port information using the CLI 156 Showing port stats information using the CLI 156 Showing port error information using the CLI 156 Showing RMON stats information using the CLI 157 Showing STG stats information 157 Configuring ports using the NNCLI 159 Configuring and monitoring port mirroring using the NNCLI 159 Creating an ingress port-mirror using the NNCLI 160 Deleting a port-mirror using the NNCLI 161 Changing a mode of a port-mirror using the NNCLI 161 NN Standard August 2007

8 8 Contents Changing a mirrored port using the NNCLI 161 Disabling a port-mirroring using the NNCLI 162 Changing a mirroring/analyzer port using the NNCLI 162 Configuring port parameters using the NNCLI 163 Configuring default auto-negotiation-advertisements using the NNCLI 165 Setting rate limits using the NNCLI 165 Showing rate limiting information using the NNCLI 166 Configuring port states using the NNCLI 168 Viewing port states using the NNCLI 168 Showing port statistics using the NNCLI 171 Showing port information using the CLI 171 Showing port stats information using the CLI 172 Configuring and graphing chassis information using Device Manager 177 Editing the chassis 177 Editing system information 178 Editing chassis information 180 Viewing the boot configuration 181 Editing trap receivers 182 Checking system performance 183 Setting the time 184 Editing cards 185 Editing card information 186 Editing the boot file 188 Displaying flash and PCMCIA statistics 190 Displaying flash file information 192 Displaying PCMCIA file information 193 Editing objects 193 Editing management port 194 Editing management port route table 196 Editing serial ports 197 Editing fans 199 Editing power supplies 200 Editing FileSystem 201 Copying a PCMCIA or flash file 202 Displaying flash and PCMCIA statistics 203 Displaying flash file information 204 Displaying PCMCIA file information 205 Graphing chassis statistics 206 Graphing system statistics 206 Graphing SNMP statistics 207 Graphing IP statistics 210 Graphing ICMP In statistics 212 NN Standard August 2007

9 Contents 9 Graphing ICMP Out statistics 213 Viewing 10 GbE interface statistics 215 Configuring the administrative status of a port 216 Appendix A RMON alarm variables 219 NN Standard August 2007

10 10 Contents NN Standard August 2007

11 11 New in this release See the following sections for details about what s new in Nortel Ethernet Routing Switch 8300 Configuration Network Management using NNCLI, CLI, and Device Manager (NN ) for Release 40: "Features" (page 11) "Other changes" (page 11) Features There are no new feature-related changes for this document release Other changes This document is reformatted to comply with Nortel Customer Documentation Standards NN Standard August 2007

12 12 New in this release NN Standard August 2007

13 13 Preface The is a flexible and multifunctional Layer 2/Layer 3 switch that supports diverse network architectures and protocols The Ethernet Routing Switch 8300 provides security and control features such as Extensible Authentication Protocol over LAN (EAPoL), Simple Network Management Protocol, Version 3 (SNMP3), and Secure Shell (SSH) The Ethernet Routing Switch 8300 provides quality of service (QoS) for a high number of attached devices and supports future network requirements for QoS for critical applications, such as Voice over IP (VoIP) This guide to network management for the Ethernet Routing Switch 8300 provides information about: the four switch management tools Java Device Manager (Device Manager) Web management interface Nortel Networks Command Line Interface (NNCLI) Command Line Interface (CLI) the Dynamic network applications feature Simple Network Management Protocol (SNMP) Remote Monitoring (RMON) configuring the Web management interface graphing port and chassis statistics initializing and customizing features Before you begin This guide is intended for network administrators who have the following background: basic knowledge of networks, Ethernet bridging, and IP and IPX routing familiarity with networking concepts and terminology experience with windowing systems or GUIs NN Standard August 2007

14 14 Preface basic knowledge of network topologies Before using this guide, you must complete the following procedures For a new switch: Step Action 1 Install the switch For installation instructions, see Installation Chassis Installation and Maintenance (NN ) and Installation Modules (NN ) 2 Connect the switch to the network For more information, see Installation and Commissioning Quick Start (NN ) End Ensure that you are running the latest version of Nortel Ethernet Routing Switch 8300 software For information about upgrading the Ethernet Routing Switch 8300, see Upgrades Software Release 30 (NN ) Text conventions This guide uses the following text conventions: angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets Do not type the brackets when entering the command bold body text bold Courier text Example: If the command syntax is ping <ip_address>, you enter ping Indicates objects such as window names, dialog box names, and icons, as well as user interface objects such as buttons, tabs, and menu items Indicates command names, options, and text that you must enter Example: Use the dinfo command Example: Enter show ip {alerts routes} NN Standard August 2007

15 Text conventions 15 braces ({}) Indicate required elements in syntax descriptions where there is more than one option You must choose only one of the options Do not type the braces when entering the command brackets ([ ]) Example: If the command syntax is show ip {alerts routes}, you must enter either show ip alerts or show ip routes, but not both Indicate optional elements in syntax descriptions Do not type the brackets when entering the command ellipsis points ( ) Example: If the command syntax is show ip interfaces [-alerts], you can enter either show ip interfaces or show ip interfaces -alerts Indicate that you repeat the last element of the command as needed italic text Example: If the command syntax is ethernet/2/1 [<parameter> <value>], you enter ethernet/2/1 and as many parameter-value pairs as needed Indicates variables in command syntax descriptions Also indicates new terms and book titles Where a variable is two or more words, the words are connected by an underscore plain Courier text Example: If the command syntax is show at <valid_route>, valid_route is one variable and you substitute one value for it Indicates command syntax and system output, for example, prompts and system messages Example: Set Trap Monitor Filters NN Standard August 2007

16 16 Preface separator ( > ) vertical line ( ) Shows menu paths Example: Protocols > IP identifies the IP command on the Protocols menu Separates choices for command keywords and arguments Enter only one of the choices Do not type the vertical line when entering the command Example: If the command syntax is show ip {alerts routes}, you enter either show ip alerts or show ip routes, but not both Acronyms This guide uses the following acronyms: ARP CANA DHCP DVMRP FEFI ICMP IGMP IP IPX MAC MIB OSPF PGM PIM RIP RMON SNMP Address Resolution Protocol Configurable Auto-Negotiation Advertisement Dynamic Host Configuration Protocol Distance Vector Multicast Routing Protocol Far End Fault Indication Internet Control Message Protocol Internet Gateway Message Protocol Internet Protocol Internetwork Packet Exchange media access control Management Information Base Open Shortest Path First Pragmatic General Multicast Protocol Independent Multicast Routing Information Protocol Remote Monitoring Simple Network Management Protocol How to get help This section explains how to get help for Nortel products and services Getting help from the Nortel web site The best way to get technical support for Nortel products is from the Nortel Technical Support web site: wwwnortelcom/support NN Standard August 2007

17 How to get help 17 This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products From this site, you can: download software, documentation, and product bulletins search the Technical Support Web site and the Nortel Knowledge Base for answers to technical issues sign up for automatic notification of new software and documentation for Nortel equipment open and manage technical support cases Getting help over the phone from a Nortel Solutions Center If you do not find the information you require on the Nortel Technical Support web site, and you have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center In North America, call NORTEL ( ) Outside North America, go to the following web site to obtain the phone number for your region: wwwnortelcom/callus Getting help from a specialist using an Express Routing Code To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service To locate the ERC for your product or service, go to: wwwnortelcom/erc Getting help through a Nortel distributor or reseller If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller NN Standard August 2007

18 18 Preface NN Standard August 2007

19 19 Switch management This chapter describes the four management tools that are available to monitor and manage your routing switch, and provides overviews for Simple Network Management Protocol (SNMP), Remote Monitoring (RMON), Configurable Auto-Negotiation Advertisements (CANA), and Far End Fault Indication (FEFI) Navigation "Switch management tools" (page 19) "Dynamic network applications" (page 24) "SNMP" (page 24) "RMON" (page 26) "CANA" (page 26) "FEFI" (page 27) "Synchronizing the real-time and system clocks" (page 29) Switch management tools Four management tools are available to monitor and manage your routing switch: "Device Manager" (page 19) "Web management interface" (page 20) "CLI" (page 20) "NNCLI" (page 20) Device Manager Device Manager is an SNMP-based graphical user interface (GUI) used to configure and manage 8300 Series switches You install it on a management station in the network To use Device Manager, you must have network connectivity to a management station running Device Manager in one of the supported environments NN Standard August 2007

20 20 Switch management Web management interface The Web management interface is a Web-based GUI tool that operates in conjunction with a Web browser It is designed to monitor a single device and is intended for use as a tool to access and monitor devices on your network from various locations within the network To configure the switch, use the Device Manager, CLI, or NNCLI To access the Web interface, you need a Web browser and an IP address for the switch For information about the Web interface, see "Configuring the Web management interface using Device Manager" (page 95), "Configuring the Web management interface using the CLI" (page 103), or"configuring the Web management interface using the NNCLI" (page 107) CLI To access the CLI initially, you need a direct connection to the switch from a terminal or PC After Telnet access is enabled, you can access the CLI from a Telnet session on the network The CLI consists of two sets of commands that are accessed in different ways While the switch is booting, you can interrupt the boot process and display the Boot Monitor CLI, which contains commands used to configure boot options and to manage files in flash memory When the switch completes its boot sequence, the login screen for the Run-Time CLI is displayed The Run-Time CLI contains commands to configure switch operations and management access To learn the basic structure and operation of the Ethernet Routing Switch 8300 CLI, refer to Command Reference CLI (NN ) This reference guide describes the function and syntax of each CLI command For information about connecting a console terminal, see Nortel Ethernet Routing Switch 8300 Installation and Commissioning Quick Start (NN ) For information about the Boot Monitor and Run-Time CLIs, see Configuration Platform Operations (NN ) and Performance Management Diagnostics Tools using NNCLI and CLI (NN ) NNCLI You can access the NNCLI using the following methods: Telnet session rlogin local console port NN Standard August 2007

21 Switch management tools 21 To access the NNCLI initially, you need a direct connection to the switch from a terminal or PC After Telnet access is enabled, you can access NNCLI from a Telnet session on the network The NNCLI consists of two sets of commands that are accessed in different ways While the switch is booting, you can interrupt the boot process and display the Boot Monitor NNCLI, which contains commands used to configure boot options and to manage files in flash memory When the switch completes its boot sequence, the login screen for the Run-Time NNCLI is displayed The Run-Time NNCLI contains commands to configure switch operations and management access To learn the basic structure and operation of the NNCLI, refer to Command Reference NNCLI (NN ) This reference guide describes the function and syntax of each NNCLI command For information about connecting a console terminal, see Nortel Ethernet Routing Switch 8300 Installation and Commissioning Quick Start (NN ) For information about the Boot Monitor and Run-Time NNCLIs, see Configuration Platform Operations (NN ) and Performance Management Diagnostics Tools using NNCLI and CLI (NN ) NNCLI command modes The NNCLI has four major command modes, listed in order of increasing privileges: User EXEC Privileged EXEC Global configuration Interface configuration Each mode provides a specific set of commands The command set of a higher-privilege mode is a superset of a lower-privilege mode That is, all lower-privilege mode commands are accessible when using a higher-privilege mode The command modes are as follows: User EXEC mode This is the initial mode of access By default, the User Access Verification Password for this mode is empty, and password checking is disabled The password can be changed (and password checking NN Standard August 2007

22 22 Switch management enabled) by the system administrator in Global configuration mode Once the password is changed, it is activated immediately Privileged EXEC mode This mode is accessed from the User EXEC mode When accessing this mode, you are prompted to provide a login name and password The login name and password combination determines your access level in the Privileged EXEC mode and other higher modes Global configuration mode This mode allows you to make changes to the running configuration If the configuration is saved, these settings survive reboots of the switch Interface configuration mode This mode allows you to modify either a logical interface, such as a VLAN, or a physical interface, such as a port/slot From either the Global configuration mode or the Interface configuration mode, all the configuration parameters (both global and interface) can be saved to a file The default name for the configuration parameters file is configcfg Alternative filenames can also be used "NNCLI command modes" (page 22) lists the NNCLI command modes, the prompts for each mode, the abbreviated name for each mode, and how to enter and exit each mode Prompts are expressed in this table using the format ERS-8300:5; however, prompts returned from your switch typically reflect the specific chassis you use For example, if you use the 8310 chassis, the prompts use the format ERS-8310:5 Prompts can be customized, also, using the NNCLI command snmp-server name <prompt> Refer to Nortel Ethernet Routing Switch 8300 Installation and Commissioning Quick Start (NN ) for more information NNCLI command modes Command mode Prompt Mode name Command/mode to enter or exit mode User EXEC ERS-8300:5> exec Default mode when NNCLI is started logout to exit Privileged EXEC ERS-8300:5# privexec enable to enter from User EXEC mode disable to exit to User EXEC mode NN Standard August 2007

23 Switch management tools 23 Command mode Prompt Mode name Command/mode to enter or exit mode Global configuration ERS- 8300:5(config)# config configure to enter from Privileged EXEC mode exit to exit to Privileged EXEC mode Interface configuration ERS- 8300:5(configif)# config-if interface to enter from Global configuration mode exit to exit to Global configuration mode Accessing the NNCLI When you first power up the Ethernet Routing Switch 8300, the default interface is the Ethernet Routing Switch 8300 CLI To switch from the CLI to the NNCLI, you must change the NNCLI boot flag to true and save the boot configuration file using the following commands: ERS-8310:5# config boot flags nncli true ERS-8310:5# save boot You must reboot the switch for this change to take effect After you reboot the switch, access the NNCLI using Telnet, rlogin, or the local console port You can log in to the switch using your password and the default privilege password nortel Use the following commands to: log in to the software using the default user name and password access Global configuration mode Login: xxxxx Password: xxxxx ERS-8310:5> enable Password: nortel ERS-8310:5# configure terminal ERS-8310:5(config)# Returning to the CLI The configcfg file for the CLI and the configcfg file for the NNCLI are not compatible If you decide to change the CLI mode to NNCLI, or the reverse, you must use the configcfg file for the selected mode To switch from the NNCLI to the CLI, enter the following commands: ERS-8310:5(config)# no boot flags nncli ERS-8310:5(config)# exit ERS-8310:5(config)# save boot NN Standard August 2007

24 24 Switch management You must reboot the switch for this change to take effect Dynamic network applications The remote access services supported on the Ethernet Routing Switch 8300 (ftp, tftp, rlogin, and Telnet) use daemons When a remote access service is enabled, the daemon begins accepting connection requests When a remote access service is disabled, all existing connections are abruptly terminated, and the daemon remains idle (does not accept connection requests) All these services are potential security holes and should remain disabled if not required The remote access services are enabled and disabled by setting flags, either from the Boot Monitor CLI or from the Run-Time CLI The default setting for these flags is false (disabled) You can use the following Dynamic network applications to manage the remote access services: access policies port lock CLI or NNCLI access SNMP community strings Web management interface access For information on enabling remote access services, refer to "Configuring RMON using Device Manager" (page 31) For information about setting access policies, locking a port, accessing the CLI or NNCLI, and setting SNMP community strings, see Nortel Ethernet Routing Switch 8300 Configuration Security using CLI and NNCLI (NN ) and Configuration Security using Device Manager (NN ) For information about accessing the Web management interface, see "Configuring RMON using Device Manager" (page 31) SNMP SNMP is a simple request/response protocol that communicates management information between two types of SNMP software entities: SNMP applications (also called SNMP managers) and SNMP agents SNMP applications contain manager software that runs on a network management station (also known as an SNMP client), such as a PC or a workstation The manager software implements the protocols used to exchange data with SNMP agents SNMP applications issue queries to NN Standard August 2007

25 SNMP 25 gather information about the status, configuration, and performance of external network devices, called network elements in SNMP terminology Network elements contain an agent and perform the network management function that the network management stations request The SNMP agent is a software entity that responds to information and action request messages (SNMP get and set requests) sent by a network management station (for example, a Device Manager workstation) The messages exchanged between manager and switch SNMP agents enable you to access and manage objects in an active or inactive (stored) management information base (MIB) on a switch The agents also send unsolicited reports, called traps, back to the network management station when certain network activity occurs An example of a trap is an overload condition as defined by the packet load s crossing some threshold You use the management station to configure, monitor, and receive trap messages from other network devices configured as SNMP agents The management station can get and set objects in the agents and can receive traps from the agents The management station, therefore, has the capability to "manage" a number of agents SNMP communities For security reasons, the SNMP agent validates each request from an SNMP manager before responding to the request by verifying that the manager belongs to a valid SNMP community An SNMP community is a logical relationship between an SNMP agent and one or more SNMP managers (the manager software implements the protocols used to exchange data with SNMP agents) You define communities locally at the agent The agent establishes one community for each combination of authentication and access control characteristics that you choose You assign each community a unique name (within the agent), and all members of a community have the same access privileges, either read-only or read-write: Read-only members can view configuration and performance information Read-write members can view configuration and performance information, and also change the configuration By defining a community, an agent limits access to its MIB to a selected set of management stations By using more than one community, the agent can provide different levels of MIB access to different management stations For more information about configuring SNMP settings (including creating community strings and setting traps) using Device Manager, see Nortel Ethernet Routing Switch 8300 Configuration Security using Device Manager (NN ) NN Standard August 2007

26 26 Switch management For more information about configuring SNMP settings using the CLI or NNCLI, see Configuration Security using CLI and NNCLI (NN ) RMON Remote Monitoring (RMON) is a MIB or a group of "management objects" that can be used to "get" or "set" values using SNMP You can enable RMON globally for devices on the switch using the CLI, NNCLI, or Device Manager When RMON is enabled globally, you can then enable monitoring for individual devices on a port-by-port basis RMON has four major functions: setting alarms for user-defined events gathering real-time and historical Ethernet statistics logging events sending traps for events Within Device Manager, you set RMON alarms that relate to specific events or variables simply by selecting these variables from a drop-down menu You can set the events associated with alarms to either trap or log-and-trap In turn, when tripped, these alarms are trapped or logged All RMON information is viewable within the Device Manager, CLI, and NNCLI Alternatively, any management application that supports SNMP traps (such as Optivity NMS and HP OpenView) can be used to view RMON trap information CANA Auto-negotiation for each port occurs under the following conditions: The port is placed in the up state from the down state The port link is lost and then recovers The port is reset During the auto-negotiation process, each port advertises its capabilities to the far-end port to which it is connected The highest possible speed that the ports are capable of supporting is selected For duplex mode, full duplex is selected first if both ports support it; otherwise, half duplex is selected if both ports support it In earlier software releases, for all ports that have auto-negotiation configured, the speed and duplex values of each port advertised during the auto-negotiation process were always the maximum possible supported by the specific port hardware For example, on a 1000/100/10 Mbps port, the 1000 Mbps and full duplex were always advertised With CANA, provides NN Standard August 2007

27 FEFI 27 greater port management control CANA allows you to configure the speed and duplex capabilities advertised during auto-negotiation for each port You can configure this feature using the CLI, NNCLI, or Device Manager CANA is supported on the 8348TX and the 8324TX modules For the 8348TX module, the advertised speed is either 100 or 10 Mbps, and the duplex is advertised as either full or half For the 8324TX module, the advertised speed is either 1000, 100, or 10 Mbps, and the duplex is advertised as either full or half ATTENTION CANA does not support the SFP ports on the 8303CP because they are fixed at 1000 Mbps As well, the Ethernet Routing Switch 8300 does not support CANA on copper SFP ports because the speed and duplex on copper SFP ports are fixed at 1000 Mbps and full duplex Once configured and saved, the configured advertisements remain set on the port If you change the configured values, the port restarts auto-negotiation in order to negotiate the port operation using the newly configured capabilities If you configure auto-negotiation on a port that is part of an MLT group, all ports in the group reflect the configuration changes For more information about configuring auto-negotiation on a port using the CLI or NNCLI, see "Configuring port parameters using the CLI" (page 146) and "Configuring port parameters using the NNCLI" (page 163) FEFI The FEFI feature is available only on the 8324FX module, which is a 100BaseFX interface that does not support auto-negotiation In accordance with the IEEE 8023 standard, far end fault indication can only be implemented for media that are not capable of supporting auto-negotiation For FEFI to function on the 8324FX module, the other end of the fiber link must also comply with the FEFI standard Interoperability depends on the PHY device used in the other hardware FEFI operation FEFI allows a local station to notify its link partner that a remote fault has occurred The remote station then diagnoses which end of the link has the fault NN Standard August 2007

28 28 Switch management A remote fault is a fault that the station at one end of the link can detect but the station at the far end cannot For example, if there is an error in a station s Tx link but the Rx link is functioning normally, the station will continue to receive valid data and there will be nothing to alert its link monitor to the error The FEFI feature operates as follows to identify and diagnose remote faults (see Figure 1 "FEFI operation" (page 29)): 1 With FEFI enabled at both ends, the two stations continuously transmit an idle stream pattern to each other When one station (the local station) detects a fault because it stops receiving the signal, it modifies its idle stream pattern and begins to transmit the FEFI idle pattern (The normal pattern is all ones; the FEFI pattern is a group of 84 ones followed by one zero) 2 When the other station (the remote station) detects the FEFI pattern, it drops the link 3 The switch displays the following log message: Slot x fefitask: port y link fault detected The port Receive (RX) LED on the front of the local 8324FX module displays as Amber/Steady while the fault condition exists The port Transmit (TX) LED on the front of the remote 8324FX module displays as Amber/Steady while the fault condition exists When a good link is detected, the LED reverts to Green/Blinking FEFI detection can be triggered by conditions other than link faults For example, if the receive cable is disconnected on the local PHY, the local station will drop the link and start sending out the FEFI idle pattern The RX LED will display as Amber/Steady until the cable is replaced The FEFI indicators are not always accurate Because of the steps the software performs to diagnose the faulty end, the log message and LED indicator do not display as soon as the hardware detects the fault It may take 2 5 seconds to identify and report the link fault If link flapping occurs during the detection period, it can cause FEFI to misrepresent link status Figure 1 "FEFI operation" (page 29) illustrates how FEFI operates NN Standard August 2007

29 Synchronizing the real-time and system clocks 29 Figure 1 FEFI operation Synchronizing the real-time and system clocks The Ethernet Routing Switch 8300 automatically synchronizes the real-time clocks (hardware) on the master and standby CPUs, and synchronizes the real-time and system (software) clocks Synchronizing the real-time and system clocks occurs at regular intervals that you define To configure the synchronization time, use the following command: config sys set clock-sync-time <minutes> where minutes is the number of minutes between synchronizations The range is 15 to 3600 minutes; the default is 60 minutes Log messages are generated when the drift between the real-time clock and the system clock is more than 5 seconds NN Standard August 2007

30 30 Switch management NN Standard August 2007

31 31 Configuring RMON using Device Manager This chapter describes how to configure and use Remote Network Monitoring (RMON) using Device Manager Navigation "Overview" (page 31) "Configuring RMON using Device Manager" (page 32) "HP OpenView" (page 53) Overview The Remote Network Monitoring (RMON) MIB is an interface between the RMON agent on the Ethernet Routing Switch 8300 switch and an RMON management application, such as the Device Manager It defines objects that are suitable for the management of any type of network Some groups are targeted for Ethernet networks in particular Enabling RMON on the switch allows the RMON agent to continuously collect statistics and actively monitor switch performance You can view this data using Device Manager, CLI, or NNCLI 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 Before using RMON functions, RMON must be globally enabled In addition, certain options should be specified to control how RMON operates on the switch NN Standard August 2007

32 32 Configuring RMON using Device Manager RMON configuration using Device Manager The following sections describe how to configure RMON using Device Manager "Enabling RMON globally using Device Manager" (page 32) "Configuring Ethernet statistics using Device Manager" (page 32) "Understanding RMON history using Device Manager" (page 36) "Configuring RMON alarms using Device Manager" (page 40) "Understanding RMON events using Device Manager" (page 47) Enabling RMON globally using Device Manager Enable RMON globally before using any RMON function If you attempt to enable any functions when the global flag is disabled, Device Manager informs you that the flag is disabled and prompts for automatic enabling of the flag See the appropriate sections about RMON functionality for details on other RMON parameters that will be automatically created and set to default parameters Step Action 1 To enable and set RMON options, from the Device Manager menu bar, choose RMON > Options The RMONOptions dialog box opens displaying the default values End If you want to use non-default RMON parameter values, you should set them before enabling RMON or when you create the specific RMON function Configuring Ethernet statistics using Device Manager You can use Device Manager to gather and graph Ethernet statistics in a variety of formats, or you can save them to a file and export them into an outside presentation or graphing application This implementation of RMON requires a "control" row for Ethernet statistics This control row appears as "port" 0/1 when you choose RMON > Control > Ethernet Statistics The row ID is reserved for the control row Therefore, some automated tests, such as ANVL, may fail when the test attempts to create a row 1 Enabling RMON statistics using Device Manager (default) To enable RMON statistics: NN Standard August 2007

33 RMON configuration using Device Manager 33 Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose RMON > Options The RmonOptions dialog box opens 3 Select Enable to enable RMON statistics 4 Click Apply End If RMON statistics have not yet been globally enabled, Device Manager prompts you to do so "RMON Options dialog box fields" (page 33) describes the RMON options dialog box fields RMON Options dialog box fields Field Enable Utilization Method Description Enables RMON statistics on the port Specifies the utilization method The choices are: halfduplex fullduplex NN Standard August 2007

34 34 Configuring RMON using Device Manager Field TrapOption MemSize Description Specifies the trap option The choices are: toowner toall Specifies the maximum allowable memory allotted for RMON statics on the port The rang is 250k4000K Verifying RMON statistics using Device Manager To verify that RMON statistics are enabled: Step Action 1 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed 2 Click the Ethernet Statistics tab The Ethernet Statistics tab opens ("RmonControl dialog box Ethernet Statistics" (page 34)) Note that the default owner displayed is the host name on which Device Manager is running The Ethernet Statistics tab opens Note that the default owner displayed is the host name on which Device Manager is running RmonControl dialog box Ethernet Statistics End "RmonControl Ethernet Statistics tab fields" (page 34) describes the RmonControl Ethernet Statistic tab fields RmonControl Ethernet Statistics tab fields Field Index Description An index that uniquely identifies an entry in the historycontrol table Each such entry defines a set of samples at a particular interval for an interface on the device NN Standard August 2007

35 RMON configuration using Device Manager 35 Field Port Owner Description The source from which historical data was collected and placed in a media-specific table on behalf of this historycontrolentry This source can be any interface on this deviceto identify a particular interface, this object must identify the instance of the ifindex object for the desired interface For example, if an entry were to receive data from interface #1, this object is set to ifindex1 The statistics in this group reflect all packets on the local network segment attached to the identified interface This object may not be modified if the associated historycontrolstatus object is equal to valid(1) The person who configured this entry and is therefore using the resources assigned to it Enabling RMON statistics using Device Manager (non-default) The default owner of the RMON statistics port is the host name on which the Device Manager software is running To insert another host name: Step Action 1 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed 2 Click the Ethernet Statistics tab The Ethernet Statistics tab opens 3 On the RmonControl dialog box, click Insert The RmonControl, Insert Ethernet Statistics dialog box opens "RmonControl and Insert Ethernet Statistics dialog boxes" (page 35) 4 Click the Port ellipsis button, and select a port 5 On the RmonControl, Insert Ethernet Statistics dialog box, click Insert RmonControl and Insert Ethernet Statistics dialog boxes NN Standard August 2007

36 36 Configuring RMON using Device Manager End "RmonControl, Insert Ethernet Statistics tab fields" (page 36) describes the RmonControl, Insert Ethernet Statistics dialog box fields RmonControl, Insert Ethernet Statistics tab fields Field Index Port Owner Description An index that uniquely identifies an entry in the Ethernet Statistics table This object identifies the source of the data that this etherstats entry is configured to analyze The entity that configured this entry and is therefore using the resources assigned to it Disabling RMON statistics using Device Manager When you no longer want to monitor a port, you can disable RMON on that port To disable RMON statistics on a port: Step Action 1 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed 2 Click the Ethernet Statistics tab The Ethernet Statistics tab opens 3 Select the row that contains the port ID you want to disable 4 Click Delete End Understanding RMON history using Device Manager The RMON History group records periodic statistical samples from a network A sample is called a history and is gathered in time intervals referred to as "buckets" By enabling and creating histories, you establish a time-dependent method for gathering RMON statistics on a port Following are the default values for history: Buckets are gathered at 30-minute intervals NN Standard August 2007

37 RMON configuration using Device Manager 37 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 a new bucket of statistics Then bucket 2 is dumped, and so forth Enabling RMON history using Device Manager (default) To enable RMON history on a port basis: Step Action 1 On the device view, select a port or multiple ports 2 Right-click on the selected ports 3 In the port shortcut menu, select Enable Rmon History 4 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed ("RmonControl and RmonControl, Insert History dialog boxes" (page 38)) Rows with RMON history enabled are displayed End Verifying history is enabled To use RMON history, it must be enabled Step Action 1 To verify that RMON history is enabled, from the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed ("RmonControl and RmonControl, Insert History dialog boxes" (page 38)) Rows with RMON history enabled are displayed End Enabling RMON history using Device Manager (non-default) You can use RMON to collect statistics at intervals For example, if you wanted RMON statistics to be gathered over the weekend, you would want enough buckets to cover two days To do this, you would set the history to gather one bucket over every hour, thus covering a 48-hour period After you set history characteristics, you cannot modify them; you must delete the history and create another one NN Standard August 2007

38 38 Configuring RMON using Device Manager To establish a history for a port and set the bucket interval: Step Action 1 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed 2 Click Insert The RmonControl, Insert History dialog box opens ("RmonControl and RmonControl, Insert History dialog boxes" (page 38)) 3 In the Port field, select a port 4 Click OK 5 In the Buckets Requested field, enter the number of discrete time intervals to save data 6 Enter the Interval in seconds 7 Click Insert End RmonControl and RmonControl, Insert History dialog boxes "Insert History tab fields" (page 39) describes the Insert History dialog box fields NN Standard August 2007

39 RMON configuration using Device Manager 39 Insert History tab fields Field Index Port BucketsRequested BucketsGranted Interval Owner Description An index that uniquely identifies an entry in the historycontrol table Each such entry defines a set of samples at a particular interval for an interface on the device Identifies the source of the data for which historical data is collected and placed in a media-specific table on behalf of this historycontrolentry This source can be any interface on this device In order to identify a particular interface, this object shall identify the instance of the ifindex object, defined in [4,6], for the desired interface For example, if an entry were to receive data from interface #1, this object would be set to ifindex1 The statistics in this group reflect all packets on the local network segment attached to the identified interface This object may not be modified if the associated historycontrolstatus object is equal to valid(1) The requested number of discrete time intervals over which data is to be saved The number of discrete sampling intervals over which data is saved When the associated BucketsRequested object is created or modified, the probe should set this object as closely to the requested value as possible The interval in seconds over which the data is sampled This object may not be modified if the associated historycontrolstatus object is equal to valid(1) The entity that configured this entry and is therefore using the resources assigned to it Disabling RMON history using Device Manager To disable RMON history on a port: Step Action 1 From the Device Manager menu bar, choose RMON > Control The RmonControl dialog box opens with the History tab displayed ("RmonControl and RmonControl, Insert History dialog boxes" (page 38)) 2 Select the row that contains the port ID you want to delete NN Standard August 2007

40 40 Configuring RMON using Device Manager 3 Click Delete End Configuring RMON alarms using Device Manager Alarms are useful when the network administrator needs to know when the value of some variable goes out of range RMON alarms can be defined on any MIB variable that resolves to an integer value In other words, string variables (such as system description) cannot be used as alarm variables All alarms share the following characteristics: An upper and lower threshold value defined on it A corresponding rising and falling event An alarm interval or polling period 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 beeping a console, sending , or calling a pager The alarm variable is polled and the result is compared against upper and lower limit values selected when the alarm is created If either limit is reached or crossed during the polling period, then the alarm fires and generates an event that you can view in the event log or the trap log The alarm s upper limit is called the rising value, and its lower limit is called the falling value RMON periodically samples the data based upon the alarm interval During thefirst interval that the data passes above the rising value, the alarm fires as a rising event During the first interval that the data drops below the falling value, the alarm fires as a falling event (Figure 2 "How alarms fire" (page 40)) Figure 2 How alarms fire NN Standard August 2007

41 RMON configuration using Device Manager 41 It is important to note that the alarm fires during the first interval that the sample goes out of range No additional events are generated for that threshold until the opposite threshold is crossed Therefore, it is important to carefully define the rising and falling threshold values for alarms to work as expected Otherwise, incorrect thresholds will cause an alarm to fire at every alarm interval A general "rule of thumb" is to define one of the threshold values to an expected, baseline value, then define the opposite threshold as the out-of-bounds limit Because of sample averaging, the value may be equal to ±1 of the baseline units For example, assume an alarm is defined on octets going out of a port as the variable The intent of the alarm is to provide notification to the system administrator when excessive traffic occurs on that port If spanning tree is enabled, then 52 octets are transmitted out of the port every 2 seconds, which is equivalent to baseline traffic of 260 octets every 10 seconds This alarm should provide the notification the system administrator needs if the lower limit of octets going out is defined at 260 and the upper limit is defined at 320 (or at any value greater than = 312) The first time outbound traffic other than spanning tree Bridge Protocol Data Units (BPDUs) occurs, the rising alarm fires When outbound traffic other than spanning tree ceases, the falling alarm fires This process provides the system administrator with time intervals of any non-baseline outbound traffic If the alarm is defined with a falling threshold less than 260 (assuming the alarm polling interval is 10 seconds), say 250, then the rising alarm can fire only once (Figure 3 "Alarm example threshold less than 260" (page 41)) The reason is that for the rising alarm to fire a second time, the falling alarm (the opposite threshold) must fire Unless the port goes inactive or spanning tree is disabled (which would cause the value for outbound octets to drop to zero), the falling alarm cannot fire because the baseline traffic is always greater than the value of the falling threshold By definition, the failure of the falling alarm to fire prevents the rising alarm from firing a second time Figure 3 Alarm example threshold less than 260 NN Standard August 2007

42 42 Configuring RMON using Device Manager Creating alarms using Device Manager When you create an alarm, you select a variable from the variable list (Appendix "RMON alarm variables" (page 219)) and a port, or other switch component, to which it is connected Some variables require port IDs, card IDs, or other indexes (for example, spanning tree group IDs) You then select a rising and a falling threshold value The rising and falling values are compared against the actual value of the variable that you choose If the variable falls outside of the rising or falling value range, an alarm is triggered and an event is logged or trapped When you create an alarm, you also select a sample type, which can be either absolute or delta Absolute alarms are defined on the cumulative value of the alarm variable An example of an alarm defined with absolute value is card operating status Because this value is not cumulative, but instead represents states, such as card up (value 1) and card down (value 2), you set it for absolute value Therefore, an alarm could be created with a rising value of 2 and 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 Delta alarms are defined based on the difference in the value of the alarm variable between the start of the polling period and the end of the polling period Delta alarms are sampled twice per polling period For each sample, the last two values are added together and compared to the threshold values This process increases precision and allows for the detection of threshold crossings that span the sampling boundary Therefore, if you keep track of the current values of a given delta-valued alarm and add them together, the result is twice the actual value (This result is not an error in the software) ATTENTION The example alarm described here will generate at least one alarm every five minutes The example is intended only to demonstrate how alarms fire; it is not a useful alarm Because of the high frequency, you may want to delete this alarm in a real world scenario To create an alarm using default values and to receive statistics and history: Step Action 1 Make sure that RMON is globally enabled When you enable RMON globally, you also create a default rising and falling event The default for the events is log-and-trap, meaning you will receive notification through a trap as well as through a log file 2 From the Device Manager menu bar, choose RMON > Alarm Manager NN Standard August 2007

43 RMON configuration using Device Manager 43 The Alarm Manager dialog box opens "Alarm Manager dialog box" (page 43) Alarm Manager dialog box 3 In the Variable field, select a variable for the alarm and a port (or other ID) on which you want to set an alarm Alarm variables are in three formats, depending on the type: A chassis, power supply, or fan-related alarm ends in x where the x index is hard-coded No further information is required A card, spanning tree group (STG), RIP or OSPF, or EtherStat alarm ends with 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 the port shortcut menu An example of a port alarm would be ifinoctets (interface incoming octet count) In the example displayed in "Alarm Manager dialog box" (page 43), "rcsyscpuutil0" has been selected from the variable list under Utilization (A list of variable definitions is located in "Configuring RMON using Device Manager" (page 31)") For this example, select a rising value of 4 and a falling value of 0 4 Leave the remaining fields at their default values, including a sample type of Delta, and click Insert (If you want to make field changes, refer to the field descriptions in "Alarm Manager dialog box fields" (page 44)) End NN Standard August 2007

44 44 Configuring RMON using Device Manager Alarm Manager dialog box fields Field Variable Sample Type Sample Interval Index "Alarm Manager dialog box fields" (page 44) describes the Alarm Manager dialog box fields Description Name and type of alarm indicated by the format: alarmnamex, where x=0 indicates a chassis alarm, x=1 or 2 indicates a power supply or fan alarm with 1 being the primary unit and 2 the secondary unit alarmname, where the user must specify the index This value is a card number for module-related alarms, an STG ID for spanning tree group alarms (the default STG is 1; other STG IDs are user configured), an IP address for RIP or OSPF alarms (RIP/OSPF must be enabled on the VLAN or router port and enabled globally), or the Ether Statistics Control Index for RMON Stats alarms alarmname with no dot or index is a port-related alarm and results in display of the port picker tool Can be either absolute or delta Time period (in seconds) over which the data is sampled and compared with the rising and falling thresholds Uniquely identifies an entry in the alarm table Each such entry defines a diagnostic sample at a particular interval for an object on the device Threshold Type Rising Value Falling Value Value Event Index When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, generates a single event Index of the event entry that is used when a rising threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object (Generally, accept the default that is already filled in) When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, generates a single event Index of the event entry that is used when a falling threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object (Generally, accept the default that is already filled in) Creating a port history alarm using Device Manager To create a port history alarm: Step Action 1 Select the port on which you want to create an alarm NN Standard August 2007

45 RMON configuration using Device Manager 45 2 Right-click the port The Port shortcut menu opens "Enabling RMON statistics and history" (page 45) Enabling RMON statistics and history 3 Choose Enable Rmon Stats and Enable Rmon History 4 On the Device Manager menu bar, choose Edit > Chassis, and then click on the Trap Receivers tab (see "Chassis dialog box Trap Receivers tab" (page 45)) Two trap versions are available: Version 1 (v1) and Version 2c (v2c) In general, select Version 2c trapping If you are using HP OpenView or other network managers that are RMON management applications, select Version 1 Chassis dialog box Trap Receivers tab NN Standard August 2007

46 46 Configuring RMON using Device Manager 5 Click Insert The Chassis, Insert Trap Receivers dialog box opens "Chassis, Insert Trap Receivers dialog box" (page 46) Chassis, Insert Trap Receivers dialog box 6 Click V1 7 Click Insert 8 Click Close End Viewing log files using Device Manager You can monitor the RMON alarms, events, and log information To view the Rmon Alarms, Events, or Log information: Step Action 1 From the Device Manager menu bar, choose RMON > Alarms 2 Click the Alarms, Events, orlog tab An example is shown in "RmonAlarms dialog box Events tab" (page 47) End NN Standard August 2007

47 RMON configuration using Device Manager 47 RmonAlarms dialog box Events tab Deleting alarms using Device Manager To delete an alarm: Step Action 1 From the Device Manager menu bar, choose RMON > Alarms The RmonAlarms dialog box opens with the Alarms tab displayed "Deleting an alarm" (page 47) 2 Select the alarm you want to delete 3 Click Delete End Deleting an alarm Understanding RMON events using Device Manager RMONevents and alarms work together to notify you when values in your network go out of a specified range When a value passes the specified range, the alarm is triggered and "fires" The event specifies how the activity is recorded NN Standard August 2007

48 48 Configuring RMON using Device Manager An event specifies whether a trap, a log, or a trap and a log will be generated to view alarm activity When RMON is globally enabled, two default events are generated: RisingEvent FallingEvent The default events specify that when an alarm goes out of range, both a trap and a log track the "firing" of the alarm For example, when an alarm fires at the rising threshold, the rising event specifies that this information be sent to both a trap and a log Likewise, when an alarm passes the falling threshold, the falling event specifies that this information be sent to a trap and a log Creating events using Device Manager (default) To create a default rising and falling event: Step Action 1 From the Device Manager menu bar, choose RMON > Alarms The RmonAlarms dialog box opens with the Alarms tab displayed 2 Click the Events tab The Events tab opens 3 Click Insert If Rmon is not globally enabled, a dialog box displays the following message: "RMON is currently disabled Do you want to enable it now?" 4 Click Yes End When you create events in this manner, you create two default events (a rising event and a falling event) Creating events using Device Manager (non-default) To create events with nondefault parameter values: Step Action 1 From the Device Manager menu bar, choose RMON > Alarms The RmonAlarms dialog box opens with the Alarms tab displayed 2 Click the Events tab NN Standard August 2007

49 RMON configuration using Device Manager 49 The Events tab opens 3 Click Insert The RmonAlarms, Insert Events dialog box opens ("RmonAlarms, Insert Events dialog box" (page 49)) RmonAlarms, Insert Events dialog box 4 Type a name for the event in the Description field 5 Select the type of event you want The default setting is log-and-trap You may opt to set the event type to log to save memory or to snmp-log to reduce traffic from the switch If you select snmp-trap or log, you must set trap receivers 6 Click Insert The new event is displayed in the Events tab of the RmonAlarms dialog box ("RmonAlarms dialog box Events tab" (page 49)) RmonAlarms dialog box Events tab End Viewing events using Device Manager To view a table of Rmon Alarm events: NN Standard August 2007

50 50 Configuring RMON using Device Manager Step Action 1 From the Device Manager menu bar, choose RMON > Alarms The RmonAlarms dialog box opens with the Alarms tab displayed 2 Click the Events tab The Events tab opens "RmonAlarms dialog box Events tab" (page 49) End Deleting events using Device Manager To delete an event: Step Action 1 From the Device Manager menu bar, choose RMON > Alarms The RmonAlarms dialog box opens with the Alarms tab displayed 2 Click the Events tab The Events tab opens 3 Select the event you want to delete 4 Click Delete End "RmonAlarms dialog box Events tab fields" (page 50) describes the RmonAlarms dialog box Events tab fields RmonAlarms dialog box Events tab fields Field Index Description Description An index that uniquely identifies an entry in the event table Each entry defines one event that is to be generated when the appropriate conditions occur Specifies whether the event is a rising or falling event NN Standard August 2007

51 Creating alarms 51 Field Type Community LastTimeSent Owner Description The type of notification that the Device Manager provides about this event In the case of log, an entry is made in the log table for each event In the case of trap, an SNMP trap is sent to one or more management stations Possible notifications follow: none log trap log-and-trap The SNMP community string acts as a password Only those management applications with this community string can view the alarms The value of sysuptime at the time this event entry last generated an event If this entry has not generated any events, this value is zero If traps are specified to be sent to the owner, then this is the name of the machine that will receive alarm traps Creating alarms To configure alarms in the alarm manager: Procedure steps Step Action 1 Ensure that RMON is globally enabled When you enable RMON globally, you also create a default rising and falling event The default for the events is log-and-trap, which means that you receive notification through a trap as well as through a log file 2 From the Device Manager menu bar, choose RMON > Alarm Manager The Alarm Manager dialog box appears 3 In the Variable menu, select a variable for the alarm Depending on the variable you select, you may be prompted for a port (or other ID) on which you want to set an alarm Alarm variables exist in three formats, depending on the type: A chassis, power supply, or fan-related alarm ends in x where the x index is hard-coded No further information is required NN Standard August 2007

52 52 Configuring RMON using Device Manager A card, spanning tree group (STG), RIP or OSPF, or EtherStat alarm ends with 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 the port shortcut menu An example of a port alarm would be ifinoctets (interface incoming octet count) 4 Select a Sample type 5 Enter a Sample interval in seconds 6 Enter a number in the Index field 7 In the Threshold Type section, enter rising and falling values 8 Click Insert End Variable definitions Variable Variable SampleType Sample Interval Index Value Name and type of alarm indicated by the format: alarmnamex, where x=0 indicates a chassis alarm, x=1 or 2 indicates a power supply or fan alarm with 1 being the primary unit and 2 the secondary unit alarmname, where the user must specify the index This value is a card number for module-related alarms, an STG ID for spanning tree group alarms (the default STG is 1; other STG IDs are user configured), an IP address for RIP or OSPF alarms (RIP/OSPF must be enabled on the VLAN or router port and enabled globally), or the Ether Statistics Control Index for RMON Stats alarms alarmname with no dot or index is a port-related alarm and results in display of the port picker tool Can be either absolute or delta Time period (in seconds) over which the data is sampled and compared with the rising and falling thresholds Uniquely identifies an entry in the alarm table Each such entry defines a diagnostic sample at a particular interval for an object on the device NN Standard August 2007

53 HP OpenView 53 Variable Threshold type Value Event Index Value Rising Value Index of the event entry that is used when a rising threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object (Generally, accept the default that is already filled in) Rising value When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, generates a single event Index of the event entry that is used when a rising threshold is crossed HP OpenView You can integrate RMON into HP OpenView To do so, you must set the HP OpenView path to include the UNIX environment variable The path is set in the cshrc file To see the path, enter the following: setenv grep PATH A path is displayed similar to this: PATH=/usr/local/ xemacs/bin/sparc-sun-solaris24: bin:/sbin:/usr/sbin:/usr/ccs/bin:/usr/dt/bin:/usr/openwin/bin:/ usr/etc:/usr/ucb:/usr/local/bin:/usr/local/share/lib:/usr/local/ share/bin:/opt/ov/bin:/home/jblogs/bin: Ensure that the HP OpenView directory is in path /opt/ov/bin MIB files are shipped with the Device Manager, and you can find them at the following path: dm/dmdb/acc/ov/mibs/p83a2100mibzip Load the MIB files Now you can start HP OpenView NN Standard August 2007

54 54 Configuring RMON using Device Manager NN Standard August 2007

55 55 RMON configuration using the CLI This chapter describes how to configure and use Remote Network Monitoring (RMON) using the CLI Navigation Overview "Overview" (page 31) "Enabling remote access services using the CLI" (page 55) "Configuring RMON using the CLI" (page 56) "Viewing RMON settings using the CLI" (page 72) The Remote Network Monitoring (RMON) MIB is an interface between the RMON agent on the Ethernet Routing Switch 8300 switch and an RMON management application, such as the Device Manager It defines objects that are suitable for the management of any type of network, but some groups are targeted for Ethernet networks in particular Enabling RMON on the switch allows the RMON agent to continuously collect statistics and proactively monitor switch performance This data can then be viewed using Device Manager, CLI or NNCLI 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 Enabling remote access services using the CLI You enable or disable access services by setting flags, either from the Boot Monitor CLI or from the Run-Time CLI You can access the boot monitor CLI while the switch is booting To enable an access service from the Boot Monitor CLI, use the following procedure: NN Standard August 2007

56 56 RMON configuration using the CLI Step Action 1 While the switch is booting, press any key to interrupt the autoboot process 2 Enable or disable the access service by using the following command: flags <ftpd rlogind telnetd tftpd sshd> <true false> 3 To set up these access services from the Run-Time CLI, use the following command: config bootconfig flags <ftpd rlogind telnetd tftpd sshd> <true false> 4 To save the state of the access services that you set up, use the following command: save bootconfig End RMON configuration The following sections describe how to configure RMON using the CLI Navigation "Enabling RMON globally using the CLI" (page 56) "Configuring Ethernet statistics using the CLI" (page 57) "Understanding RMON history using the CLI" (page 60) "Configuring RMON alarms using the CLI" (page 62) "Understanding RMON events using the CLI" (page 68) Enabling RMON globally using the CLI Enable RMON globally before using any RMON function If attempts are made to enable any functions when the global flag is disabled, the CLI informs you that the flag is disabled See the appropriate sections about RMON functionality for details on other RMON parameters that will be automatically created and set to default parameters If you are using non-default RMON parameter values, set them before you enable RMON or when you create the specific RMON function NN Standard August 2007

57 RMON configuration 57 Step Action 1 To enable RMON globally, use the following command: config rmon enable 2 To disable (RMON) globally, use the following command: config rmon disable End Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon enable ERS-8310:5# config rmon info Sub-Context: clear config monitor show test trace Current Context: rmon : enable memsize : trap-option : toowner util-method : half ERS-8310:5# config rmon disable ERS-8310:5# config rmon info Sub-Context: clear config monitor show test trace Current Context: rmon : disable memsize : trap-option : toowner util-method : half Ethernet statistics using the CLI You can gather Ethernet statistics, or you can save them to a file and export them to another location Enabling RMON statistics using the CLI To enable RMON Ethernet statistics globally, use the following command: config rmon ether-stats create <id> <ports> where id is the index number of the ether-stats control interface and ports is the slot/port on which you want to enable RMON statistics The command includes the following parameters: NN Standard August 2007

58 58 RMON configuration using the CLI config rmon ether-stats create followed by: <id> Specifies the index number of the ether-stats control interface The range of values is 1 to <ports> Specifies the port(s) in the portlist form: {slot/port [-slot/port][, ]} Optional parameter: Specifies the name of the owner The default owner of the RMON statistics port is the host [owner <value>] name on which the CLI is running The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon ether-stats create 12 7/5 ERS-8310:5# config rmon ether-stats info Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : owner : ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor 12 7/5 cli Disabling RMON statistics using the CLI When you no longer want to monitor a port, you can disable RMON on that port To disable an ether-stats control interface for the RMON functions on a port, use the following command: config rmon ether-stats delete <id> where id specifies the index number of the ether-stats control interface with a value range of 1 to Configuration example After configuring the parameters, use the info command to show a summary of the results NN Standard August 2007

59 RMON configuration 59 ERS-8310:5# config rmon ether-stats delete 12 ERS-8310:5# config rmon ether-stats info Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : owner : ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor Configuring an owner for RMON statistics using the CLI The default owner of the RMON statistics port is the host name on which the statistics were configured To specify another host name, enter the following command: config rmon ether-stats owner <id> <name> where id is the index number of the ether-stats control interface and name is the name of the owner you want to specify The command uses the following parameters: config rmon ether-stats owner followed by: <id> Specifies the index number of the ether-stats control interface The range of values is 1 to <name> Specifies the owner name The range of values is a string of 1 to 48 characters Configuration examples After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon ether-stats owner 13 johnfw ERS-8310:5# config rmon ether-stats info Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : owner : ===================================================== Rmon Ether Stats NN Standard August 2007

60 60 RMON configuration using the CLI ===================================================== INDEX PORT OWNER cpp monitor 13 7/5 johnfw Viewing RMON statistics using the CLI After you have collected statistics, you can view the data on the RMON ports you have configured Enter this command to verify that RMON statistics are enabled: show rmon ether-stats Understanding RMON history using the CLI The RMON History group records periodic statistical samples from a network A sample is called a history and is gathered in time intervals referred to as "buckets" By enabling and creating histories, you establish a time-dependent method for gathering RMON statistics on a port Following are the default values for history: 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 a new bucket of statistics Then bucket 2 is dumped, and so forth Enabling RMON history using the CLI To enable RMON history on a port, enter the following command: config rmon history-control create <id> <ports> where id specifies the index number of the history control interface and ports specifies the slot/port on which you want to enable history config rmon history-control create followed by: <id> Specifies the index number of the history control interface The range of values is 1 to <ports> Specifies the port(s) in the portlist form: {slot/port [-slot/port][, ]} Optional parameters: NN Standard August 2007

61 RMON configuration 61 config rmon history-control create followed by: [buckets <value>] Specifies the number of buckets requested The range of values is 1 to 350 [intv <value>] Specifies the time interval in seconds over which the data is sampled for each bucket The range of values is 1 to 3600 [owner <LINE>] Specifies the name of the owner The range of values is a string of 1 to 48 characters Configuration examples After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# rmon history-control create 13 7/5ERS-8310:5# config rmon history-control info Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER / cli Viewing RMON statistics using the CLI After you have collected statistics, you can view the data on the RMON ports you have configured Enter this command to verify that RMON statistics are enabled: show rmon history-control Modifying RMON history using the CLI RMON can collect statistics at intervals For example, if you wanted RMON statistics to be gathered over the weekend, you would want enough buckets to cover two days To do this, the history could be set to gather one bucket over every hour, thus covering a 48-hour period After the history characteristics are set, they cannot be modified; the history id must be deleted and another one must be created Disabling RMON history using the CLI To disable RMON history on a port, use the following command: config rmon history-control delete <id> NN Standard August 2007

62 62 RMON configuration using the CLI where id specifies the index number of the history control interface you want to delete Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon history-control delete 13 ERS-8310:5# config rmon history-control info Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER / cli Viewing RMON history using the CLI After you have collected history statistics, you can view the data Enter this command to view RMON history: show rmon history-control Configuring RMON alarms using the CLI Alarms are useful when the network administrator needs to know when the value of some variable goes out of range RMON alarms can be defined on any MIB variable that resolves to an integer value In other words, string variables (such as system description) cannot be used as alarm variables All alarms share the following characteristics: An upper and lower threshold value defined on it A corresponding rising and falling event An alarm interval or polling period When alarms are "fired," or activated, you can view the activity in a log or a trap log, or you can create a script to notify you by beeping a console, sending , or calling a pager The alarm variable is polled and the result is compared against upper and lower limit values selected when the alarm is created If either limit is reached or crossed during the polling period, then the alarm fires and generates an event that you can view in the event log or the trap log NN Standard August 2007

63 RMON configuration 63 The alarm s upper limit is called the rising value, and its lower limit is called the falling value RMON periodically samples the data based upon the alarm interval During the first interval that the data passes above the rising value, the alarm fires as a rising event During the first interval that the data drops below the falling value, the alarm fires as a falling event (Figure 4 "How alarms fire" (page 63)) Figure 4 How alarms fire It is important to note that the alarm fires during the first interval that the sample goes out of range No additional events are generated for that threshold until the opposite threshold is crossed Therefore, it is important to carefully define the rising and falling threshold values for alarms to work as expected Otherwise, incorrect thresholds will cause an alarm to fire at every alarm interval A general "rule of thumb" is to define one of the threshold values to an expected, baseline value, then define the opposite threshold as the out-of-bounds limit Because of sample averaging, the value may be equal to ±1 of the baseline units For example, assume an alarm is defined on octets going out of a port as the variable The intent of the alarm is to provide notification to the system administrator when excessive traffic occurs on that port If spanning tree is enabled, then 52 octets are transmitted out of the port every 2 seconds, which is equivalent to baseline traffic of 260 octets every 10 seconds This alarm should provide the notification the system administrator needs if the lower limit of octets going out is defined at 260 and the upper limit is defined at 320 (or at any value greater than = 312) The first time outbound traffic other than spanning tree Bridge Protocol Data Units (BPDUs) occurs, the rising alarm fires When outbound traffic other than spanning tree ceases, the falling alarm fires This process provides the system administrator with time intervals of any non-baseline outbound traffic NN Standard August 2007

64 64 RMON configuration using the CLI If the alarm is defined with a falling threshold less than 260 (assuming the alarm polling interval is 10 seconds), say 250, then the rising alarm can fire only once (Figure 5 "Alarm example threshold less than 260" (page 64)) The reason is that for the rising alarm to fire a second time, the falling alarm (the opposite threshold) must fire Unless the port goes inactive or spanning tree is disabled (which would cause the value for outbound octets to drop to zero), the falling alarm cannot fire because the baseline traffic is always greater than the value of the falling threshold By definition, the failure of the falling alarm to fire prevents the rising alarm from firing a second time Figure 5 Alarm example threshold less than 260 Creating alarms When you create an alarm, you select a variable from the variable list (Appendix "RMON alarm variables" (page 219)) and a port, or other switch component, to which it is connected Some variables require port IDs, card IDs, or other indexes (for example, spanning tree group IDs) You then select a rising and a falling threshold value The rising and falling values are compared against the actual value of the variable that you choose If the variable falls outside of the rising or falling value range, an alarm is triggered and an event is logged or trapped When you create an alarm, you also select a sample type, which can be either absolute or delta Absolute alarms are defined on the cumulative value of the alarm variable An example of an alarm defined with absolute value is card operating status Because this value is not cumulative, but instead represents states, such as card up (value 1) and card down (value 2), you set it for absolute value Therefore, an alarm could be created with a rising value of 2 and a falling value of 1 to alert a user whether the card is up or down Most alarm variables related to Ethernet traffic are set to delta value Delta alarms are defined based on the difference in the value of the alarm variable between the start of the polling period and the end of the polling period Delta alarms are sampled twice per polling period For each sample, the last two values are added together and compared to the threshold values This process increases precision and allows for the detection of threshold NN Standard August 2007

65 RMON configuration 65 crossings that span the sampling boundary Therefore, if you keep track of the current values of a given delta-valued alarm and add them together, the result is twice the actual value (This result is not an error in the software) Creating an RMON alarm using the CLI To create an alarm using default values and to receive statistics and history, use the following command: config rmon alarm create <id> type <value> intv <value> This command includes the following parameters: config rmon alarm create followed by: <id> Specifies the alarm interface index number The index value is a card number for module-related alarms, an STG ID for spanning tree group alarms (the default STG is 1; other STG IDs are user configured), an IP address for RIP or OSPF alarms (RIP/OSPF must be enabled on the VLAN or router port and enabled globally), or the Ether Statistics Control Index for RMON Stats alarms The range of values is 1 to type <value> intv <value> [variable <value>] Specifies the sample type The options are: absolute and delta Specifies the sample interval The sample interval is a time period (in seconds) over which the data is sampled and compared with the rising and falling thresholds The range of values is 1 to 3600 Specifies the alarm name Uses format alarmnamex, where x=0 indicates a chassis alarm, x=1 or 2 indicates a power supply or fan alarm with 1 being the primary unit and 2 the secondary unit An alarmname with no dot or index is a port-related alarm and results in a display of the port picker tool The range of values is a string of 1 to 1536 characters NN Standard August 2007

66 66 RMON configuration using the CLI config rmon alarm create followed by: Optional Parameters: [r_th <value>] [r_ev <value>] [f_th <value>] [f_ev <value>] [owner <value>] A list of alarm names is located in Appendix "RMON alarm variables" (page 219) Specifies the rising threshold Generates a single event when the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold The range of values is to Specifies the rising event number Index of the event entry that is used when a rising threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object The range of values is 1 to Generally, accept the default that is already filled in Specifies the falling threshold Generates a single event when the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold The range of values is to Specifies the falling event number Index of the event entry that is used when a falling threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object The range of values is 1 to Generally, accept the default that is already filled in Specifies the name of the owner The range of values is a string of 1 to 48 characters NN Standard August 2007

67 RMON configuration 67 Configuration example After configuring the parameters, use the info command to show a summary of the results Creating a port history alarm using the CLI To create a port history alarm, use the following command: config rmon history-control create <id> <ports> where id is the index number of the history control interface and ports is the slot/port on which you want to enable a port history alarm config rmon history-control create followed by: <id> Specifies the index number of the history control interface The range of values is 1 to <ports> Specifies the port in the portlist form: {slot/port [-slot/port][, ]} Optional parameters: [buckets <value>] [intv <value>] [owner <value>] Specifies the number of buckets requested The range of values is 1 to 350 Specifies the time interval in seconds over which the data is sampled for each bucket The range of values is 1 to 3600 Specifies the name of the owner The range of values is a string of 1 to 48 characters NN Standard August 2007

68 68 RMON configuration using the CLI Configuration example This configuration example uses the commands listed above to enable RMON It also uses the info command to display RMON function information ERS-8310:5# config rmon ERS-8310:5/config/rmon# enable ERS-8310:5/config/rmon# Info Sub-Context: alarm ether-stats event history-control Current Context: rmon : enable mansize : trap-option : toowner ERS-8310:5/config/rmon# Viewing RMON statistics using the CLI To view RMON alarms statistics, enter the following command: show rmon alarm Viewing log files using the CLI To display the RMON log information, use the following commands: show rmon event show rmon log Deleting alarms using the CLI To delete an alarm, entering the following command: config rmon alarm delete <id> where id specifies the alarm interface index number with a value range of 1 to Understanding RMON events using the CLI RMON events and alarms work together to notify you when values in your network go out of a specified range When a value passes the specified range, the alarm is triggered and "fires" The event specifies how the activity is recorded An event specifies whether a trap, a log, or a trap and a log will be generated to view alarm activity When RMON is globally enabled, two default events are generated: RisingEvent FallingEvent NN Standard August 2007

69 RMON configuration 69 The default events specify that when an alarm goes out of range, both a trap and a log track the "firing" of the alarm For example, when an alarm fires at the rising threshold, the rising event specifies that this information be sent to both a trap and a log Likewise, when an alarm passes the falling threshold, the falling event specifies that this information be sent to a trap and a log Creating events using the CLI To create a default rising and falling event, enter the following command: config rmon event create <id> trap_src <value> trap_dest <value> config rmon event create followed by: <id> Specifies the event index number The range of values is 1 to trap_src <value> Specifies the trap source IP address trap_dest <value> Optional parameters: [desc <value>] [type <value>] [community <value>] [owner <value>] Specifies the trap destination IP address Specifies the event description The range of values is a string of 0 to 127 characters Specifies the event type The options are: none, log, snmp-trap, or log-and-trap The default setting is log-and-trap If you select snmp-trap or log, you must set trap receivers Specifies the event community The range of values is a string of 0 to 127 characters Specifies the owner The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the info command to show a summary of the results NN Standard August 2007

70 70 RMON configuration using the CLI Viewing events using the CLI You can monitor the RMON alarms, events, and log information To view a table of RMON events, enter the following command: show rmon event Deleting events using the CLI To delete an event, enter the following command: config rmon event delete <id> where id specifies the event index number with a value range of 1 to Configuring RMON information using the CLI You can specify values for the following RMON parameters: Memory size Trap option Utilization methods Specifying memory allocationusing the CLI To specify the maximum allowable memory allotted for RMON statics, enter the following command: config rmon memsize <memsize> NN Standard August 2007

71 RMON configuration 71 where memsize is the maximum allowable memory allotted for RMON statics on the port The range in bytes is Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon memsize WARNING!!! For taking this change effect, please save run-time config and reset the device ERS-8310:5# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toowner Util-method : half ERS-8310:5# Specifying the trap optionusing the CLI To specify the trap option, enter the following command: config rmon trap-option <toowner toall> where toowner toall can be either toowner or toall Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config rmon trap-option toall ERS-8310:5# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toall Util-method : half Specifying the utilization methodusing the CLI To specify the utilization method, enter the following command: config rmon util-method <half full> where: the utilization method choices are half or full Configuration example After configuring the parameters, use the info command to show a summary of the results NN Standard August 2007

72 72 RMON configuration using the CLI ERS-8310:5# config rmon util-method full ERS-8310:5# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toall Util-method : full Viewing RMON settings using the CLI The following CLI command lets you view the various RMON settings: show rmon The show rmon command options are: show rmon followed by: info alarm ether-stats event history-control log Displays the status of RMON on the switch Displays the RMON alarm table Displays the RMON Ethernet statistics table Displays the RMON event table Displays the RMON history control table Displays the RMON log table Example The following example shows sample output from each of the show rmon options NN Standard August 2007

73 Viewing RMON settings using the CLI 73 NN Standard August 2007

74 74 RMON configuration using the CLI NN Standard August 2007

75 75 RMON configuration using the NNCLI This chapter describes how to configure and use Remote Network Monitoring (RMON) using the NNCLI Navigation Overview "Overview" (page 75) "Configuring RMON using the NNCLI" (page 75) "Viewing RMON settings using the NNCLI" (page 91) The Remote Network Monitoring (RMON) MIB is an interface between the RMON agent on the Ethernet Routing Switch 8300 switch and an RMON management application, such as the Device Manager It defines objects that are suitable for the management of any type of network, but some groups are targeted for Ethernet networks in particular Enabling RMON on the switch allows the RMON agent to continuously collect statistics and proactively monitor switch performance This data can then be viewed using Device Manager, CLI or NNCLI 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 Before using RMON functions, RMON must be globally enabled In addition, certain options should be specified to control how RMON operates on the switch RMON configuration using the NNCLI The following sections describe how to configure RMON using the NNCLI It includes the following topics: NN Standard August 2007

76 76 RMON configuration using the NNCLI Navigation "Enabling RMON globally using the NNCLI" (page 76) "Configuring Ethernet statistics using the NNCLI" (page 77) "Configuring RMON alarms using the NNCLI" (page 82) "Understanding RMON events using the NNCLI" (page 88) Enabling RMON globally using the NNCLI Enable RMON globally before using any RMON function If attempts are made to enable any functions when the global flag is disabled, the CLI informs you that the flag is disabled See the appropriate sections about RMON functionality for details on other RMON parameters that will be automatically created and set to default parameters If you are using non-default RMON parameter values, set them before you enable RMON or when you create the specific RMON function To enable RMON globally, in Global configuration mode, use the following command: rmon Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#rmon ERS-8310:6(config)#show rmon info RMON Info : Status : enable MemorySize : TrapOption : toowner Util-method : half ERS-8310:6(config)# Disabling RMON globally using the NNCLI To disable (RMON) globally, use the following command: no rmon Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#no rmon ERS-8310:6(config)#show rmon info RMON Info : Status : disable MemorySize : TrapOption : toowner NN Standard August 2007

77 RMON configuration using the NNCLI 77 Util-method ERS-8310:6(config)# : half Ethernet statistics using the NNCLI You can gather Ethernet statistics, or you can save them to a file and export them to another location Enabling RMON statistics using the NNCLI To enable RMON ethernet statistics globally, use the following command: rmon stats < > <ports> where id is the index number of the ether-stats control interface and ports is the slot/port on which you want to enable RMON statistics The command includes the following parameters: config rmon ether-stats create followed by: < > Specifies the index number of the ether-stats control interface The range of values is 1 to <ports> Specifies the port(s) in the portlist form: {slot/port [-slot/port][, ]} Optional parameter: [owner <value>] Specifies the name of the owner The default owner of the RMON statistics port is the host name on which the CLI is running The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#rmon stats 87 1/13 ERS-8310:6(config)#show rmon info RMON Info : Status : enable MemorySize : TrapOption : toowner Util-method : half ERS-8310:6(config)#show rmon stats ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor NN Standard August 2007

78 78 RMON configuration using the NNCLI 3 1/1 cli 87 1/13 cli ERS-8310:6(config)# Viewing RMON statistics Enter this command to verify that RMON statistics are enabled: show rmon stats < > Disabling RMON statistics using the NNCLI When you no longer want to monitor a port, you can disable RMON on that port To disable RMON statistics on a port use the following command: no rmon stats <id> where id> specifies the index number of the ether-stats control interface with a value range of 1 to Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#show rmon stats ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor 3 1/1 cli 87 1/13 cli ERS-8310:6(config)#no rmon stats 3 ERS-8310:6(config)#show rmon stats ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor 87 1/13 cli ERS-8310:6(config)# Configuring an owner for RMON statistics using the NNCLI The default owner of the RMON statistics port is the host name on which the statistics were configured To specify another host name, enter the following command: NN Standard August 2007

79 RMON configuration using the NNCLI 79 rmon stats owner <id> <name> where id is the index number of the ether-stats control interface and name is the name of the owner you want to specify The command uses the following parameters: rmon stats owner followed by: <id> Specifies the index number of the stats control interface The range of values is 1 to <name> Specifies the owner name The range of values is a string of 1 to 48 characters Configuration examples After configuring the parameters, use the show command to display a summary of the results ERS-8310:5# rmon stats 87 johnfw ERS-8310:5# show rmon stats Sub-Context: clear config monitor show test trace Current Context: delete : N/A create : owner : ===================================================== Rmon Ether Stats ===================================================== INDEX PORT OWNER cpp monitor 13 7/5 johnfw Viewing RMON statistics using the NNCLI After you have collected statistics, you can view the data on the RMON ports you have configured To view RMON statistics, enter the following command: show rmon stats NN Standard August 2007

80 80 RMON configuration using the NNCLI Understanding RMON history using the NNCLI The RMON History group records periodic statistical samples from a network A sample is called a history and is gathered in time intervals referred to as "buckets" By enabling and creating histories, you establish a time-dependent method for gathering RMON statistics on a port Following are the default values for history: 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 a new bucket of statistics Then bucket 2 is dumped, and so forth Enabling RMON history using the NNCLI To enable RMON history on a port, enter the following command: rmon history < > <ports> [buckets <value>] [intv <value>] [owner <LINE>] where specifies the index number of the history control interface and ports specifies the slot/port on which you want to enable history rmon history followed by: < > Specifies the index number of the history control interface The range of values is 1 to <ports> Specifies the port(s) in the portlist form: {slot/port [-slot/port][, ]} Optional parameters [buckets <value>] [intv <value>] [owner <LINE>] Specifies the number of buckets requested The range of values is 1L to 350L Specifies the time interval in seconds over which the data is sampled for each bucket The range of values is 1L to 3600L Specifies the name of the owner The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#rmon history 12 1/13 NN Standard August 2007

81 RMON configuration using the NNCLI 81 ERS-8310:6(config)#show rmon history ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER / cli Modifying RMON history using the NNCLI RMON can collect statistics at intervals For example, if you wanted RMON statistics to be gathered over the weekend, you would want enough buckets to cover two days To do this, the history could be set to gather one bucket over every hour, thus covering a 48-hour period After the history characteristics are set, they cannot be modified; the history id must be deleted and another one must be created Disabling RMON history using the NNCLI To disable RMON history on a port, enter the following command: no rmon history < > where < > specifies the index number of the history control interface with a value range of 1 to Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#show rmon history ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER / cli ERS-8310:6(config)#no rmon history 12 ERS-8310:6(config)#show rmon history ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER ERS-8310:6(config)# Viewing history using the NNCLI After you have collected statistics, you can view the data on the RMON ports you have configured NN Standard August 2007

82 82 RMON configuration using the NNCLI Enter this command to view RMON history: show rmon history Configuring RMON alarms using the NNCLI Alarms are useful when the network administrator needs to know when the value of some variable goes out of range RMON alarms can be defined on any MIB variable that resolves to an integer value In other words, string variables (such as system description) cannot be used as alarm variables All alarms share the following characteristics: An upper and lower threshold value defined on it A corresponding rising and falling event An alarm interval or polling period When alarms are "fired," or activated, you can view the activity in a log or a trap log, or you can create a script to notify you by beeping a console, sending , or calling a pager The alarm variable is polled and the result is compared against upper and lower limit values selected when the alarm is created If either limit is reached or crossed during the polling period, then the alarm fires and generates an event that you can view in the event log or the trap log The alarm s upper limit is called the rising value, and its lower limit is called the falling value RMON periodically samples the data based upon the alarm interval During the first interval that the data passes above the rising value, the alarm fires as a rising event During the first interval that the data drops below the falling value, the alarm fires as a falling event (Figure 6 "How alarms fire" (page 82)) Figure 6 How alarms fire NN Standard August 2007

83 RMON configuration using the NNCLI 83 It is important to note that the alarm fires during the first interval that the sample goes out of range No additional events are generated for that threshold until the opposite threshold is crossed Therefore, it is important to carefully define the rising and falling threshold values for alarms to work as expected Otherwise, incorrect thresholds will cause an alarm to fire at every alarm interval A general "rule of thumb" is to define one of the threshold values to an expected, baseline value, then define the opposite threshold as the out-of-bounds limit Because of sample averaging, the value may be equal to ±1 of the baseline units For example, assume an alarm is defined on octets going out of a port as the variable The intent of the alarm is to provide notification to the system administrator when excessive traffic occurs on that port If spanning tree is enabled, then 52 octets are transmitted out of the port every 2 seconds, which is equivalent to baseline traffic of 260 octets every 10 seconds This alarm should provide the notification the system administrator needs if the lower limit of octets going out is defined at 260 and the upper limit is defined at 320 (or at any value greater than = 312) The first time outbound traffic other than spanning tree Bridge Protocol Data Units (BPDUs) occurs, the rising alarm fires When outbound traffic other than spanning tree ceases, the falling alarm fires This process provides the system administrator with time intervals of any non-baseline outbound traffic If the alarm is defined with a falling threshold less than 260 (assuming the alarm polling interval is 10 seconds), say 250, then the rising alarm can fire only once Figure 7 "Alarm example threshold less than 260" (page 83) The reason is that for the rising alarm to fire a second time, the falling alarm (the opposite threshold) must fire Unless the port goes inactive or spanning tree is disabled (which would cause the value for outbound octets to drop to zero), the falling alarm cannot fire because the baseline traffic is always greater than the value of the falling threshold By definition, the failure of the falling alarm to fire prevents the rising alarm from firing a second time Figure 7 Alarm example threshold less than 260 NN Standard August 2007

84 84 RMON configuration using the NNCLI Creating alarms using the NNCLI When you create an alarm, you select a variable from the variable list (Appendix "RMON alarm variables" (page 219)) and a port, or other switch component, to which it is connected Some variables require port IDs, card IDs, or other indexes (for example, spanning tree group IDs) You then select a rising and a falling threshold value The rising and falling values are compared against the actual value of the variable that you choose If the variable falls outside of the rising or falling value range, an alarm is triggered and an event is logged or trapped When you create an alarm, you also select a sample type, which can be either absolute or delta Absolute alarms are defined on the cumulative value of the alarm variable An example of an alarm defined with absolute value is card operating status Because this value is not cumulative, but instead represents states, such as card up (value 1) and card down (value 2), you set it for absolute value Therefore, an alarm could be created with a rising value of 2 and a falling value of 1 to alert a user whether the card is up or down Most alarm variables related to Ethernet traffic are set to delta value Delta alarms are defined based on the difference in the value of the alarm variable between the start of the polling period and the end of the polling period Delta alarms are sampled twice per polling period For each sample, the last two values are added together and compared to the threshold values This process increases precision and allows for the detection of threshold crossings that span the sampling boundary Therefore, if you keep track of the current values of a given delta-valued alarm and add them together, the result is twice the actual value (This result is not an error in the software) Creating an RMON alarm using the NNCLI To create an alarm using default values and to receive statistics and history, use the following command: rmon alarm <id> <WORD> <interval> <absolute delta> rising-threshold < > [<rising-event>] falling-threshold < > [<falling-event>] [owner <value>] rmon alarm followed by: <id> Specifies the alarm interface index number The index value is a card number for module-related alarms, an STG ID for spanning tree group alarms (the default STG is 1; other STG IDs are user configured), an IP address for RIP or OSPF alarms (RIP/OSPF must be enabled on the NN Standard August 2007

85 RMON configuration using the NNCLI 85 rmon alarm followed by: <WORD> <interval> {absolute delta} rising-threshold < > VLAN or router port and enabled globally), or the Ether Statistics Control Index for RMON Stats alarms The range of values is 1 to Specifies the alarm name Uses format alarmnamex, where x=0 indicates a chassis alarm, x=1 or 2 indicates a power supply or fan alarm with 1 being the primary unit and 2 the secondary unit An alarmname with no dot or index is a port-related alarm and results in a display of the port picker tool The range of values is a string of 1 to 1536 characters A list of alarm names is located in Appendix "RMON alarm variables" (page 219) Specifies the sample interval The sample interval is a time period (in seconds) over which the data is sampled and compared with the rising and falling thresholds The range of values is 1 to 3600 Specifies the sample type The options are: absolute and delta Specifies the rising threshold Generates a single event when the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold The range of values is to NN Standard August 2007

86 86 RMON configuration using the NNCLI rmon alarm followed by: [<rising-event>] falling-threshold < > [<falling-event>] [owner <value>] Specifies the rising event number Index of the event entry that is used when a rising threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object The range of values is 1 to Generally, accept the default that is already filled in Specifies the falling threshold Generates a single event when the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold The range of values is to Specifies the falling event number Index of the event entry that is used when a falling threshold is crossed The event entry identified by a particular value of this index is the same as identified by the same value of the event index object The range of values is 1 to Generally, accept the default that is already filled in Specifies the name of the owner The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the show command to display a summary of the results NN Standard August 2007

87 RMON configuration using the NNCLI 87 Creating a port history alarm using the NNCLI To create a port history alarm, use the following command: rmon history <id> <ports> [buckets <value>] [intv <value>] [owner <value>] rmon history followed by: <id> <ports> Optional parameters: [buckets <value>] [intv <value>] [owner <value>] Specifies the index number of the history control interface The range of values is 1 to Specifies the port in the portlist form: {slot/port [-slot/port][, ]} Specifies the number of buckets requested The range of values is 1 to 350 Specifies the time interval in seconds over which the data is sampled for each bucket The range of values is 1 to 3600 Specifies the name of the owner The range of values is a string of 1 to 48 characters Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)#rmon history 7 1/37 ERS-8310:6(config)#show rmon history ===================================================== Rmon Control-History ===================================================== INDEX PORT BUCKET_REQUEST INTERVAL OWNER / cli Viewing RMON statistics using the NNCLI To view RMON alarms statistics, enter the following command: show rmon alarm Viewing log files using the NNCLI To display the RMON log information, use the following commands: show rmon event show rmon log Deleting alarms using the NNCLI To delete an alarm, enter the following command: NN Standard August 2007

88 88 RMON configuration using the NNCLI no rmon alarm < > where < > specifies the alarm interface index number value Understanding RMON events using the NNCLI RMONevents and alarms work together to notify you when values in your network go out of a specified range When a value passes the specified range, the alarm is triggered and "fires" The event specifies how the activity is recorded An event specifies whether a trap, a log, or a trap and a log will be generated to view alarm activity When RMON is globally enabled, two default events are generated: RisingEvent FallingEvent The default events specify that when an alarm goes out of range, both a trap and a log track the "firing" of the alarm For example, when an alarm fires at the rising threshold, the rising event specifies that this information be sent to both a trap and a log Likewise, when an alarm passes the falling threshold, the falling event specifies that this information be sent to a trap and a log Creating events using the NNCLI To create a default rising and falling event: Step Action 1 Display the RMON event information: rmon event info 2 Create a RMON event on the switch: rmon event < > trap_src <value> trap_dest <value> [log-type <value>] [description <LINE>] [community <value>] [owner <LINE>] This command includes the following parameters: rmon event followed by: <id> trp_src <value> trap_dest <value> Optional parameters: Specifies the event index number The range of values is 1 to Specifies the trap source IP address Specifies the trap destination IP address NN Standard August 2007

89 RMON configuration using the NNCLI 89 rmon event followed by: [community <value>] [description <value>] [log-type <value>] Specifies the event community The range of values is a string of 0L to 127L characters Specifies the event description The range of values is a string of 0L to 127L characters Specifies the event type The options are: none, log, snmp-trap, or log-and-trap [owner <value>] The default setting is log-and-trap If you select snmp-trap or log, you must set trap receivers Specifies the owner The range of values is a string of 1 to 48 characters End Configuration example After configuring the parameters, use the show command to display a summary of the results Viewing events using the NNCLI You can monitor the RMON alarms, events, and log information To view a table of RMON events, enter the following command: show rmon event Deleting events using the NNCLI To delete an event, enter the following command: no rmon event [< >] NN Standard August 2007

90 90 RMON configuration using the NNCLI where < > specifies the event index number with a value range of 1 to Configuring RMON information using the NNCLI You can specify values for the following RMON parameters: Memory size Trap status Trap option Specifying memory allocation using the NNCLI To specify the maximum allowable memory allotted for RMON statics, enter the following command: rmon memsize <memsize> where memsize is the maximum allowable memory allotted for RMON statics on the port The range in bytes is Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)# config rmon memsize WARNING!!! For taking this change effect, please save run-time config and reset the device ERS-8310:6(config)# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toowner Util-method : half ERS-8310:5# Specifying the trap option using the NNCLI To specify the trap option, enter the following command: config rmon trap-option <toowner toall> where toowner toall can be either toowner or toall Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)# rmon trap-option toall NN Standard August 2007

91 Viewing RMON settings using the NNCLI 91 ERS-8310:6(config)# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toall Util-method : half Specifying the utilization method To specify the utilization method, enter the following command: rmon util-method <half full> where: the utilization method choices are half or full Configuration example After configuring the parameters, use the show command to display a summary of the results ERS-8310:6(config)# rmon util-method full ERS-8310:6(config)# show rmon info RMON Info : Status : enable MemorySize : TrapOption : toall Util-method : full Viewing RMON settings using the NNCLI The following NNCLI command lets you view the various RMON settings: show rmon The show rmon NNCLI commands and options are: show rmon followed by: info alarm stats event history log Displays the status of RMON on the switch Displays the RMON alarm table Displays the RMON Ethernet statistics table Displays the RMON event table Displays the RMON history control table Displays the RMON log table Example The following example shows sample output from each of the show rmon options NN Standard August 2007

92 92 RMON configuration using the NNCLI NN Standard August 2007

93 Viewing RMON settings using the NNCLI 93 NN Standard August 2007

94 94 RMON configuration using the NNCLI NN Standard August 2007

95 95 Configuring the Web management interface using Device Manager This chapter describes how to enable the Web management interface using Device Manager Navigation "Monitoring the switch using Web management" (page 95) "Accessing the Web interface" (page 100) Monitoring the switch using Web management The Ethernet Routing Switch 8300 switch includes a Web management interface that lets you monitor your switch through a World Wide Web browser from anywhere on your network The Web interface provides many of the same monitoring features as the Device Manager software The Web management interface is protected by a security mechanism that requires you to log in to the device using a user name and password The switch is shipped with the default user name and password both specified as ro For security, the default state of the Web Server is disabled The Web interface provided by the Ethernet Routing Switch 8300 uses HTTP only Nortel strongly recommends using the Device Manager interface with SNMPv3 providing authentication and encryption for traffic management Note that because HTTP is used, Read Only capabilities are provided through the Web agent Navigation "Requirements" (page 95) "Installing Help files" (page 96) "Enabling the Web server using Device Manager" (page 97) Requirements To use the Web-based management interface, you need: A computer connected to any of the network ports NN Standard August 2007

96 96 Configuring the Web management interface using Device Manager One of the following browsers: Netscape Navigator, version 47 or later Microsoft Internet Explorer Web browser, version 50 or later The IP address of the Ethernet Routing Switch 8300 switch For instructions about assigning an IP address to the management port, see Installation and Commissioning Quick Start (NN ) Access to the Web management interface must also be enabled for the switch (the default setting) In Device Manager, you can enable or disable Web access by choosing Edit > Chassis > System On the System tab, set the EnableWebServer parameter to true If you have a route to the switch and there are no filters or access policies in effect, you can monitor the switch using the Web interface To access the Web management interface, enter your switch IP address as the URL in your Web browser and log onsee"accessing the Web interface" (page 100) for instructions Installing Help files Online Help for the Web interface consists of a separate set of files included on the Ethernet Routing Switch 8300 Switch Software CD The files must be installed on a TFTP server in the network and the IP address of the server and the path to the file must be specified, using either the Device Manager, CLI, or NNCLI Installing Help files in a Windows environment To install the Help files in a Windows environment: Step Action 1 Insert the Software CD into the CD driver of your computer 2 Navigate to the CD and double-click the wm_windows folder 3 Double-click the installer icon or in WinZip, extract the file, and click wmexe 4 Follow the screen prompts End NN Standard August 2007

97 Monitoring the switch using Web management 97 Installing Help files in a UNIX environment To install the Help files in a UNIX environment, use the command: install_ers_wmfiles [wm-version] [target-directory] where [wm-version] specifies the file name [target-directory] specifies the system directory where you are installing the files For example: install_ers_wmfiles wm_v300 /opt/ers8300/wm Specifying the Help file location If you install the Help files on a PC, place the files in the same drive as the one specified under TFTP server options for your system To specify the file location using Device Manager: Step Action 1 From the Device Manager menu bar, choose Edit > Security > Web 2 In the HelpTftpSourceDir field, type the path and file name for the Help files End To specify the file location using the CLI, enter: config web-server html-source-dir help-tftp <file> where file specifies the path and file name in the format abcd:<file> To specify the file location using the NNCLI, enter: web-server help-tftp <file> where file specifies the path and file name in the format abcd:<file> Enabling the Web server using Device Manager To enable the Web Server using Device Manager: NN Standard August 2007

98 98 Configuring the Web management interface using Device Manager Step Action 1 From the Device Manager menu bar, select Edit > Chassis The Chassis dialog box opens with the System tab displayed Chassis dialog box System tab 2 Select EnableWebServer 3 Click Apply 4 Close the dialog box The Web Server is enabled End NN Standard August 2007

99 Monitoring the switch using Web management 99 In Device Manager, use the Web tab to set Web access parameters, including passwords To set Web access: Step Action Security dialog box Web tab 1 From the Device Manager menu bar, choose Edit > Security The Security dialog box opens with the EAPOL tab displayed 2 Click the Web tab The Web tab opens ("Security dialog box Web tab" (page 99)) The ROUserName and ROPassword fields allow you to specify the user name and password for access to the Web interface (All Web pages are read-only pages) The other fields allow you to specify the path and file name for the Web Help files and to set the number of rows allowed in the Web display End NN Standard August 2007

100 100 Configuring the Web management interface using Device Manager "Web tab fields" (page 100) describes the Web tab fields Field ROUserName ROPassword PrimaryHtmlSourceDir Description Specifies the user name for the read-only Web server account Specifies the password for the read-only Web server account Specifies the primary HTML source directory SecondaryHtmlSourceDirSpecifies the secondary HTML source directory TertiaryHtmlSourceDir HelpTftpSourceDir DefaultDisplayRows LastChange NumHits NumAccessChecks Specifies the tertiary HTML source directory Specifies the TFTP source directory for Help files Specifies the default display rows for the HTML pages Specifies the time of the most recent change to the switch configuration using the Web interface This field always reads none Specifies the number of times pages in the Web interface have been accessed Specifies the number of times access attempts have been authenticated Accessing the Web interface To access the Web interface: Step Action 1 Start your Web browser 2 Enter the switch IP address as the URL in the Web address field The Web logon page opens "Web logon page" (page 100) Web logon page 3 In the User Name and Password text boxes, type ro NN Standard August 2007

101 Accessing the Web interface Click Log On The System page opens This page provides general information about the switch as a whole and its configuration parameters End The Web interface has a 15-minute timeout period If there is no activity for 15 minutes, the system logs off the switch Web interface, and you must reenter the password information To access a Web browser from Device Manager, on the toolbar, click the Browse Device s Home Page button Troubleshooting Web interface access to a switch If the switch and the PC running the Web browser are in the same network, you may find that even though other applications (such as Device Manager or Telnet) can access a particular switch, the Web management interface cannot This situation can occur if the Web browser has a proxy server that resolves the www path and returns the "reachable" IP address to the browser If there is no route from the proxy server to the switch, the http query does not reach the switch, and there is no response To prevent this problem, make sure that if your Web browser uses a proxy server, a route is specified from the proxy server to the switch NN Standard August 2007

102 102 Configuring the Web management interface using Device Manager NN Standard August 2007

103 103 Configuring the Web management interface using the CLI You can monitor your Ethernet Routing Switch 8300 switch using a Web management interface that lets you monitor your switch through a World Wide Web browser from anywhere on your network The Web interface provides many of the same monitoring features as the Device Manager software Navigation "Enabling the Web server using the CLI" (page 103) "Showing Web-server status" (page 104) Enabling the Web server using the CLI To enable and manage the Web Server using the CLI, use the following commands: Step Action 1 Display the enabled or disabled status of the Web-server functions on the switch: config web-server info 2 Specify the http port for the Web server: config web-server http-port <integer> where <integer> is a value from 1 to Define the file location and name for the Web server HTML Help file: config web-server html-source-dir help-tftp <file> where <file> specifies the path and file name of the HTML source in the format abcd:<file> NN Standard August 2007

104 104 Configuring the Web management interface using the CLI If non-default Web-server parameter values are to be used, they should be set before enabling Web server or when the specific Web-server function is created 4 Set the default display row width for the Web server: config web-server def-display-rows <integer> where <integer> is a value from 10 to Enable the Web-server functions on the switch: config web-server enable The Web interface provided by the Ethernet Routing Switch 8300 uses HTTP only Nortel strongly recommends using the Device Manager interface with SNMPv3 providing authentication and encryption for traffic management Note that because HTTP is used, Read Only capabilities are provided through the Web agent The Web-server functions can be globally disabled on the switch with command: web-server disable 6 Set a password for access to the Web interface: config web-server password <ro> <username> <passwd> End This command includes the following parameters: config web-server followed by: <ro> Specifies read only access for the Web pages <username> Specifies the user s login name, up to 20 characters long <passwd> Specifies the password associated with the login name, up to 20 characters long Showing Web-server status To display Web access enabled status, as well as password and access information, enter the following command: show web-server NN Standard August 2007

105 Showing Web-server status 105 Configuration example This configuration example uses the above command to display Web-server status ERS-8310:5/config/web-server# show web-server Web Server Info : Status : on RO Username : ro RO Password : ro Def-display-rows : 25 Html help tftp source-dir : HttpPort : 80 NumHits : 0 NumAccessChecks : 0 NumAccessBlocks : 0 NumRxErrors : 0 NumTxErrors : 0 NumSetRequest : 0 ERS-8310:5/config/web-server# NN Standard August 2007

106 106 Configuring the Web management interface using the CLI NN Standard August 2007

107 107 Configuring the Web management interface using the NNCLI You can monitor your Ethernet Routing Switch 8300 switch using a Web management interface that lets you monitor your switch through a World Wide Web browser from anywhere on your network The Web interface provides many of the same monitoring features as the Device Manager software Enabling the Web server using the NNCLI To enable and manage the Web Server using the NNCLI, use the following commands: Step Action 1 Enable the Web-server functions on the switch: web-server [def-display-rows <integer>] [help-tftp <file>] [http-port <integer>] This command includes the following options: web-server followed by: def-display-rows <integer> Sets the default display row width for the Web server integer is 10L to 100L NN Standard August 2007

108 108 Configuring the Web management interface using the NNCLI web-server followed by: help-tftp <file> http-port <integer> Specifies the file location and name for the Web server HTML Help file file specifies the path and file name of the HTML source in the format abcd:<file> Specifies the http port of the Web server integer is a value from 1L to 49151L If non-default Web-server parameter values are to be used, they should be set before enabling Web server or when the specific Web-server function is created The Web-server functions can be globally disabled on the switch with command: web-server disable 2 Set a password for access to the Web interface: web-server password <ro> <username> <passwd> End This command includes the following parameters: web-server followed by: <ro> Specifies read only access for the Web pages <username> Specifies the user s login name, up to 20 characters long <passwd> Specifies the password associated with the login name, up to 20 characters long NN Standard August 2007

109 Configuring and graphing ports using Device Manager 109 This chapter describes editing and graphing layer 2 port functions using Device Manager Navigation "Configuring a port using Device Manager" (page 109) "Graphing a port using Device Manager" (page 131) "Graphing RMON statistics using Device Manager" (page 137) "Graphing RMON History statistics using Device Manager" (page 139) Configuring a port using Device Manager This section describes the following topics: "Editing ports using Device Manager" (page 110) "Setting a basic configuration using Device Manager" (page 110) "Configuring VLANs using Device Manager" (page 117) "Configuring spanning tree groups (STG) using Device Manager" (page 118) "Configuring MAC learning parameters using Device Manager" (page 120) "Setting rate limits using Device Manager" (page 121) "Testing ports using Device Manager" (page 123) "Testing cables with the virtual cable tester (VCT) using Device Manager" (page 124) "Configuring transmit queue (TxQueue) using Device Manager" (page 126) "Configuring EAPoL using Device Manager" (page 127) "Configuring mroute stream limit using Device Manager" (page 130) NN Standard August 2007

110 110 Configuring and graphing ports using Device Manager Editing ports using Device Manager For instructions about configuring EAPoL statistics, see Nortel Ethernet Routing Switch 8300 Configuration Security using Device Manager To edit a single port or multiple ports: Step Action 1 Select the port or ports you want to edit 2 Do one of the following: Double-click a port Right-click a port On the shortcut menu, choose Edit From the Device Manager menu bar, choose Edit > Port On the Device Manager toolbar, choose the Edit Selected button When you edit a single port, dialog boxes and tabs that are not applicable are not available for selection When you edit multiple ports, some options are not available, and other options appear to be available even when the dialog box or tab is not applicable When a dialog box or tab does not apply for a given port, NoSuchObject is displayed End Setting a basic configuration using Device Manager You can set options for a basic port configuration through the Interface tab in the Port dialog box ("Port dialog box Interface tab" (page 111)) Additional tabs and screen entries for module-specific functions appear when applicable For example, on the Interface dialog box for a port, tabs for layer 3 (routing) functions would appear if Device Manager were accessing an Ethernet Routing Switch 8600 module To set a basic configuration: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) NN Standard August 2007

111 Configuring a port using Device Manager 111 End Port dialog box Interface tab The 10/100BASE-TX ports may not autonegotiate correctly with older 10/100BASE-TX equipment You can sometimes upgrade the older devices with new firmware or driver revisions If an upgrade does not allow autonegotiation to correctly identify the link speed and duplex settings, you can manually configure the settings for the link in question Check the Nortel Web site (wwwnortelcom) for the latest compatibility information "Interface tab fields" (page 112) describes the Interface tab fields NN Standard August 2007

112 112 Configuring and graphing ports using Device Manager Interface tab fields Field Index Name Descr Type Mtu PhysAddress VendorDescr AdminStatus OperStatus LastChange LinkTrap Description A unique value assigned to each interface The value ranges between 64 and 703 The name given to the port The port type of this interface The media type of this interface The size of the largest packet, in octets, that can be sent/received on the interface The MAC address assigned to a particular interface The name of the interface chipset (May not apply to all port types) One of the following states: up down testing When a managed system initializes, all interfaces start with AdminStatus in the up state As a result of either explicit management action or per configuration information retained by the managed system, AdminStatus is then changed to either the down or the testing state (or remains in the down state) The testing state indicates that no operational packets can be passed The current operational state of the interface One of the following states: up down testing The testing state indicates that no operational packets can be passed If AdminStatus is down, then OperStatus should be down If AdminStatus is changed to up, then OperStatus should change to up if the interface is ready to transmit and receive network traffic It should remain in the down state if and only if there is a fault that prevents it from going to the up state The value of sysuptime at the time the interface entered its current operational state If the current state was entered prior to the last reinitialization of the local network management subsystem, the value is zero Indicates whether or not link Up/link Down traps should be generated for this interface NN Standard August 2007

113 Configuring a port using Device Manager 113 Field AutoNegotiate AdminDuplex OperDuplex AdminSpeed OperSpeed AutoNegAdCapability AutoNegAd MltId Locked UnknownMacDiscard DirectBroadcastEnable Action Result Description Indicates whether this port is enabled for autonegotiations (only 10/100BASE ports) Nortel recommends that you use autonegotiation whenever it is supported by the devices on both ends of a Gigabit fiber link When the Ethernet Routing Switch 8300 is connected to a device that does not support it, autonegotiation should be disabled and SFFD enabled For more information, see Nortel Ethernet Routing Switch 8300 Planning and Engineering Network Design Guidelines (NN ) Indicates the port s current duplex value (half-duplex or full-duplex mode) The current operational duplex mode of the port (half or full) Indicates the port s speed (10 Mb/s or 100 Mb/s) The current operating speed of the port Indicates the speed and duplex capabilities of the port Allows you to select the speed and duplex capabilities of the port The valid options are 10Mbps half duplex, 10Mbps full duplex, 100Mbps half duplex, 100Mbps full duplex, 1000 half duplex, and 1000 full duplex Unsupported speed and duplex capabilities for the selected port are grayed out The MultiLink Trunk to which the port is assigned (if any) Indicates whether or not the port is locked When locked, the port configuration cannot be changed To lock or unlock a port, select Edit > Security > Port Lock If rcunknownmacdiscard is set to True, then a packet with an unknown source MAC address is dropped on that port, and other ports then will discard any packets with this MAC address in the destination field For example, suppose 11:22:33:44:55:66 is an unknown source MAC Packets with source MAC 11:22:33:44:55:66 coming from this port are discarded; furthermore, packets with destination MAC 11:22:33:44:55:66 coming from other ports are also discarded, unless this address is later learned on another port or the restriction ages out You cannot set the unknown-mac-discard lock-autolearn-mac disable parameter when autolearn is disabled Used to indicate whether this interface should forward direct broadcast traffic One of the following port-related actions: none flushmacfdb flush MAC forwarding table for port flushall flush all tables for port The result of port-related actions NN Standard August 2007

114 114 Configuring and graphing ports using Device Manager Viewing port state using Device Manager The ability to view a port s state is important for network administration and debugging When you view port states, you can determine the port configuration, the port speed, and whether it is half duplex or full duplex etc You can also obtain information on QoS, filter, route-discovery, rate-limit, tx-queue, and unknown-mac-discard configuration of the ports To view the state of a port: Step Action 1 On the device view, select a port 2 Right-click on the port and choose Edit The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) 3 Click any tab, for example, TxQueue The TxQueue tab opens ("Port Mirrors tab" (page 116)) with the port state displayed End Configuring and monitoring port mirroring using Device Manager Port mirroring is a method of monitoring network traffic that forwards a copy of each incoming (ingress) and outgoing (egress) packet from one port of a network switch to another port where the packet can be studied A network administrator uses port mirroring as a diagnostic tool or debugging feature, especially when fending off an attack It enables the administrator to closely monitor switch performance and alter it, if necessary Port mirroring can be managed locally or remotely When you enable port mirroring, you must specify a: The source ports from which traffic is mirrored A destination port to see mirrored traffic Any packet entering or exiting the specified ports is forwarded normally, and a copy of the packet is sent out the mirror port When this feature is active, all packets received on the specified ports are copied to the port specified as the out port The mirroring operation is nonintrusive NN Standard August 2007

115 Configuring a port using Device Manager 115 Although you can configure Ethernet Routing Switch 8000 Series switches to monitor both ingress and egress traffic, some restrictions apply: You can configure up to 383 total entries in the port mirroring table for mirroring, and you can have up to 383 entries active at any given time This total is the combination of the maximum number of entries in egress port mirroring (8 maximum) and the number of entries in ingress port mirroring For ingress port mirroring, you can configure only one port as the mirroring (destination) port and any number (up to the above maximum) of ingress ports as mirrored (source) ports Therefore, all ingress mirrored traffic is sent to the single mirroring destination) port For egress mirroring, you can configure only one port as the mirroring (destination) port You can configure a maximum of 8 ports in egress For ingress and egress mirroring, you can configure the mirroring port as the same port for both ingress and egress mirroring You can enable egress port mirroring separately, allowing you to monitor packets as they leave specified ports In addition, you can monitor traffic for MAC addresses, where traffic with a given MAC source address (SA) or MAC destination address (DA) is copied to the specified mirroring port To avoid seeing unintended traffic, remove mirroring (destination) ports from all virtual local area networks (VLAN) and spanning tree groups (STG) If you are mirroring ports where VLAN tagging is enabled, the VLAN tags are not included in the packets received at the mirroring (destination) port You can observe and analyze packet traffic at the mirroring port using a network analyzer a copy of the packet can be captured and analyzed Unlike other methods that are used to analyze packet traffic, the packet traffic is uninterrupted and packets flow normally through the mirrored port Configuring port mirroring To configure a mirrored port: Step Action 1 On the device view, select a port 2 From the Device Manager menu bar, choose Edit > Diagnostics The Diagnostics dialog box opens with the Link Flap tab displayed "Port dialog box Interface tab" (page 111) 3 Click the Port Mirrors tab The Port Mirrors tab displays ("Port Mirrors tab" (page 116)) NN Standard August 2007

116 116 Configuring and graphing ports using Device Manager Port Mirrors tab 4 Click Insert The Diagnostics, Insert Port Mirrors dialog box displays ("Insert Port Mirrors dialog box" (page 116)) Insert Port Mirrors dialog box 5 Click on the MirroredPort button to display the available ports The DiagMirrorByPortMirroredPort dialog box displays ("DiagMirrorByPortMirroredPort dialog box fields" (page 116)) DiagMirrorByPortMirroredPort dialog box fields 6 Click a slot on the port you want to mirror by 7 Click OK 8 The slot/port you selected appears in the Insert Port Mirrors dialog box 9 Repeat steps 5 through 7 on the MirroringPort button NN Standard August 2007

117 Configuring a port using Device Manager Click Insert End Configuring routing operations using Device Manager The following tabs in the Port dialog box are used for layer 3 routing: IP Address tab VLAN tab STG tab MAC Learning tab Test tab ARP tab IGMP tab Configuring VLANs using Device Manager You can configure VLANs to tag or untag discarded frames for a port To configure VLANs: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed 3 Click the VLAN tab The VLAN tab opens ("Port dialog box VLAN tab" (page 117)) Port dialog box VLAN tab 4 Click Apply NN Standard August 2007

118 118 Configuring and graphing ports using Device Manager 5 Click Close End "VLAN tab fields" (page 118) describes the VLAN tab fields VLAN tab fields Field PerformTagging Description Enable or disable the port on the current VLAN to perform tagging on the incoming and outgoing traffic DiscardUntaggedFrames Determines how to process untagged frames received on this tagged port When the flag is set, these frames are discarded by the forwarding process When the flag is reset, these frames are assigned to the VLAN specified by the DefaultVlanId UntagPortDefaultVlanEnables or disables the port to send tag for default VLAN The port must be configured with PerformTagging Enable All other VLANs will send the tag if not default VLAN DefaultVlanId VLAN ID assigned to untagged frames Configuring spanning tree groups (STG) using Device Manager You can configure a port s spanning tree parameters through the STG tab in the Port dialog box When you edit multiple ports, the spanning tree options are not displayed To configure a spanning tree group: Step Action 1 On the device view, select a port 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed 3 Click the STG tab The STG tab opens ("Port dialog box STG tab" (page 118)) Port dialog box STG tab NN Standard August 2007

119 Configuring a port using Device Manager 119 End "STG tab fields" (page 119) describes the STG tab fields STG tab fields Field StgID Priority State EnableStp FastStart PathCost DesignatedRoot DesignatedCost DesignatedBridge DesignatedPort Description The spanning tree group ID The value of the priority field that is contained in the first (in network byte order) octet of the (2-octet long) Port ID The other octet of the Port ID is given by the value of dot1dstpport The port s current state as defined by application of the Spanning Tree Protocol This state controls what action a port takes on reception of a frame If the bridge has detected a port that is malfunctioning, it will place that port into the broken state For ports that are disabled (see EnableStp), this object will have a value of disabled The enabled/disabled spanning tree status of the port, which will affect only the operation of the Spanning Tree Protocol on the port Disabling STP at the spanning tree group will take precedence over what is configured here When FastStart is true, the port is enabled in the Forwarding state upon being enabled If the port receives a spanning tree BPDU, the port will start normal STP negotiations The contribution of this port to the cost of paths toward the spanning tree root, which include this port The IEEE 8021D-1990 standard recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN The unique Bridge Identifier of the bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached The path cost of the Designated Port of the segment connected to this port This value is compared to the Root Path Cost field in received bridge PDUs The Bridge Identifier of the bridge that this port considers to be the Designated Bridge for this port s segment The Port Identifier of the port on the Designated Bridge for this port s segment NN Standard August 2007

120 120 Configuring and graphing ports using Device Manager Field ForwardTransitions ChangeDetection Description The number of times this port has transitioned from the Learning state to the Forwarding state If this field is disabled, topology change notifications are not sent for the port Configuring MAC learning parameters using Device Manager You can configure the MAC learning parameters to control high-security environments that restrict access to the network This feature is based on the layer 2 media access control (MAC) address of the network devices connected to the Ethernet Routing Switch 8300 switch To configure the MAC learning parameters: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed 3 Click the MAC Learning tab The MAC Learning tab opens ("The MAC Learning tab opens Port dialog box MAC Learning tab" (page 120)) Port dialog box MAC Learning tab 4 Click the Interface tab 5 Activate the Unknown MAC Discard by checking the box The MAC can now be learned and populate the Allowed MAC Table NN Standard August 2007

121 Configuring a port using Device Manager 121 End Without activating the unknown MAC Discard after enabling AutoLearn, the Allowed MAC Table does not learn any MACs "MAC Learning tab fields" (page 121) describes the MAC Learning tab fields MAC Learning tab fields Field AutoLearnEnable AutoLearnMode AutoLearnTableMode LogViolations SendTrap DisablePort MacCountMax MacCountCur Description Sets the port to autolearn addresses for the allowed MAC table Sets the autolearn mode on the port for populating the allowed MAC table The two autolearn modes are: one-shot and continuous Sets the allowed MAC table to current state When locked, no new MAC addresses will be learned Enables the system to create a system log entry when a disallowed MAC address attempts to send traffic through the selected port Indicates whether a trap should be sent to the management station when a MAC address violation is detected on the selected port The default is disable Indicates whether the selected port should be disabled if a MAC address violation is detected enable means that the port should be disabled if this event occurs The default is disable The maximum number of MAC addresses that can be added to the selected port The valid values are 0 to 2048 The current number of MAC addresses that have been added to the selected port Setting rate limits using Device Manager You can set the rate limit of broadcast packets for a port Changing the broadcast rate limit affects both the broadcast and the multicast rate limits To set the rate limit: NN Standard August 2007

122 122 Configuring and graphing ports using Device Manager Step Action 1 On the device view, select a port 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed 3 Click the Rate Limiting tab The Rate Limiting tab opens ("Port dialog box Rate Limiting tab" (page 122)) Port dialog box Rate Limiting tab End "Rate Limiting tab fields" (page 122) describes the Rate Limiting tab fields Rate Limiting tab fields Field Index TrafficType AllowedRate Description The port number The type of traffic being rate limited (broadcast-multicast} This variable is the allowed traffic rate limit for the port Ethernet Routing Switch 8300 switches, 1100 sets the limit in a percentage of the total bandwidth on the port between 1% and 100% Ethernet Routing Switch 8100 switches, 125 sets the limit in a percentage of the total bandwidth on the port between 1% and 25% Ethernet Routing Switch 8600 switches, sets the limit in packets per second NN Standard August 2007

123 Configuring a port using Device Manager 123 Field Description On Ethernet Routing Switch 8100 gigabit ports and MDAs, there may be up to a 2% difference between the configured and actual rate limiting values Enable Right click in the field and select to enable (True) or disable (False) rate limiting Testing ports using Device Manager A DRAM memory test and an internal loopback test are run during the automatic boot sequence However, you can also run external and internal loopback tests on the port You can run only one loopback test at a time You must stop a loopback test before you start one on another port To open the Test tab: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) 3 Click the Test tab The Test tab opens ("Port dialog box Test tab" (page 123)) Port dialog box Test tab End "Test tab fields" (page 124) describes the Test tab fields NN Standard August 2007

124 124 Configuring and graphing ports using Device Manager Test tab fields Field Result Code PassCount FailCount Description The result of the most recently run (or current) test: None Success InProgress NotSupported unabletorun Aborted Failed The code contains more specific information on the test result (for example, an error code after a failed test): NoReceive (timeout on a send) BadSeq (packets received out of sequence) BadLen (packet length mismatch) BadData (packet data mismatch) This object contains a code which contains more specific information on the test results, for example an error-code after a failed test Error codes and other values this object may take are specific to the type of interface and/or test The value may have the semantics of either the Autonomous Type or InstancePointer textual conventions as defined in RFC 1443 The identifier: testcodeunknown OBJECT IDENTIFIER :={0 0} is defined for use if no additional result code is available The number of iterations of the loopback test completed successfully The number of iterations of the loopback test failed Testing cables with the virtual cable tester (VCT) using Device Manager To start VCT: Step Action 1 Select a port 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) 3 Click the VCT tab NN Standard August 2007

125 Configuring a port using Device Manager 125 Port dialog box VCT tab The VCT tab opens ("Port dialog box VCT tab" (page 125)) Use the VCT dialog box to test the cable connected to a selected port 4 Select the Start Test box to test the cable connected to the previously selected port with the virtual cable tester 5 Click Apply 6 View the results of the cable test shown in the VCT dialog box 7 Click Close End "VCT tab fields" (page 125) describes the VCT tab fields VCT tab fields Field Start Test TestDone Description Starts a test on the cable connected to a previously selected port with virtual cable tester True indicates the test is completed and false indicates the test is not in progress NormalCableLength Indicates the length of the tested cable PhyType CableStatus Indicates the physical type of cable which was tested Indicates if the cable was tested or not tested NN Standard August 2007

126 126 Configuring and graphing ports using Device Manager Field Pair Status Pair ErrLength Description Indicates if a pair in the cable was tested or not tested Indicates the length where a problem was detected in the tested cable Configuring transmit queue (TxQueue) using Device Manager Use the TxQueue dialog box to set up the transmit queue for a selected port To configure TxQueue: Step Action 1 Select a port Port dialog box TxQueue tab 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) 3 Click the TxQueue tab The TxQueue tab opens ("Port dialog box TxQueue tab" (page 126)) 4 The TxQueue menu displays the default values of the TxQueue fields 5 Change the value of the fields which do not apply to this application "TxQueue tab fields" (page 127) displays descriptions of the TxQueue fields 6 Click Apply 7 Click Close NN Standard August 2007

127 Configuring a port using Device Manager 127 End "TxQueue tab fields" (page 127) describes the TxQueue tab fields TxQueue tab fields Field PortIndex Id TrafficClass TxEnable Size SchedulingGroup Weight ShaperEnable ShaperMaxRate ShaperBurstSize Description An index value that uniquely identifies a port An index value that uniquely identifies an egress queue Identifies the traffic class (0 to 7) of the queue Enables or disables transmission on the queue Specifies the number of packet descriptors allocated for the queue There are 3 scheduling Arbitration groups: StrictPriority - This Arbitration Group is served first, where the priority goes from the highest queue index to the lowest dwrr1 - This Arbitration Group may transmit packets when there is no traffic from the SP Arbitration Group dwrr0 - This Arbitration Group may transmit packets when there is no traffic from the DWRR Group 1 Within each DWRR Arbitration Group, each queue is guaranteed its proportional minimal bandwidth according to its configured weight Specifies the proportion (in units of 256 bytes) of bandwidth assigned to this queue relative to the other queues in the arbitration group The range is from 1 to 256 The default is 8, which is 8 * 256 (2048) Nortel recommends that the minimum weight (N * 256) be greater than the port MTU Enables or disables shaper on the port Sets the shaping rate in Mbps Note that the actual shaping rate might be different from the configured rate due to the rate granularity of the shaper The range is from 1 to 10000, and the default is 10 Sets the burst size in Kbps Note that the actual burst size might be different from the configured size due to the granularity of the shaper The range is from 4 to 16000, and the default is 4 Configuring EAPoL using Device Manager Use the EAPOL dialog box to set up the extensible authentication protocol parameters for a selected port To configure Extensible Authentication Protocol over LAN (EAPoL): NN Standard August 2007

128 128 Configuring and graphing ports using Device Manager Step Action 1 Select a port Port dialog box EAPOL tab 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed ("Port dialog box Interface tab" (page 111)) 3 Click the EAPOL tab The EAPOL tab opens ("Port dialog box EAPOL tab" (page 128)) 4 The EAPOL menu displays the default values of the EAPOL fields 5 Change the value of the fields which do not apply to this application 6 Click Apply 7 Click Close End "EAPOL tab fields" (page 129) describes the EAPOL tab fields NN Standard August 2007

129 Configuring a port using Device Manager 129 EAPOL tab fields Field PortProtocolVersion PortCapabilities PortInitialize PortReauthenticate PaeState BackendAuthState AdminControlledDirections OperControlledDirections AuthControlledPortStatus AuthControlledPortControl Description Read-only field that indicates the protocol version number Read-only field that indicates that PAE is supported on this port When checked, initializes EAPoL authentication on this port When checked, re-authenticates the Supplicant connected to this port immediately The default is disabled Displays the current Authenticator PAE state Possible states are: initialized disconnected connecting authenticating authenticated aborting held forceauth forceunauth Displays current Backend Authentication state Possible states are: request response success fail timeout idle initialize Indicates the control direction Control direction can be either in (incoming-only) or both (incoming-and-outgoing) If the port is unauthorized, traffic is blocked, based on this setting If AdminControlledDirections is set to in, ingressing traffic is blocked; egress traffic is forwarded normally If AdminControlledDirections is set to both, traffic is blocked in both directions Read-only field that indicates the current control direction The options are in and both Displays the port s current state: unauthorized, auto, or authorized Sets the port authentication status The default is forceauthorized forceunauthorized - port is always unauthorized auto - port authorization depends on the results of the EAPoL authentication by the RADIUS server forceauthorized - port is always authorized NN Standard August 2007

130 130 Configuring and graphing ports using Device Manager Field QuietPeriod TxPeriod SuppTimeout ServerTimeout MaxReq ReAuthPeriod ReAuthEnabled Description Sets the time interval (in seconds) between authentication failure and the start of a new authentication The allowed range is 1 to (default is 60) Sets the time (in seconds) to wait for a response from a Supplicant for EAP Request/Identity packets The allowed range is 1 to 6553 (default is 30) Sets the time (in seconds) to wait for a response from a Supplicant for all EAP packets except EAP Request/Identity packets The allowed range is 1 to (default is 30) Sets the time (in seconds) to wait for a response from the RADIUS server The allowed range is 1 to (default is 30) Sets the maximum number of times to retry sending packets to the Supplicant The range is 1 to 10 (default is 2) Sets the time interval (in seconds) between successive re-authentications The range is 1 to (default is hour) When checked, re-authenticates an existing Supplicant at the time interval specified in ReAuthPeriod Configuring mroute stream limit using Device Manager To configure the mroute stream limit: Step Action 1 Select a port 2 From the Device Manager menu bar, choose Edit > Port The Port dialog box opens with the Interface tab displayed (see "Port dialog box Interface tab" (page 111)) 3 Click the Mroute Stream Limit tab The Mroute Stream Limit tab opens ("Port dialog box Mroute Stream Limit tab" (page 131)) NN Standard August 2007

131 Graphing a port using Device Manager 131 Port dialog box Mroute Stream Limit tab 4 Update the value of the fields as required 5 Click Apply 6 Click Close End Mroute Stream Limit tab fields Field StreamLimitEnable StreamLimit StreamTimerCheck "Mroute Stream Limit tab fields" (page 131) describes the Mroute Stream Limit tab fields Description Enables or disables Mroute Stream Limiting Specifies the maximum number of multicast streams that are allowed to ingress the CPU through this port Valid values range from , with a default of 1984 Specifies a sampling period (in seconds) for checking the number of multicast streams that has entered the CPU through this port Valid values range from seconds, with a default of 10 Graphing a port using Device Manager The following sections discuss the different port statistics tabs in the Graph Port dialog box with descriptions of the statistics fields Navigation "Graphing port statistics using Device Manager" (page 132) "Graphing interface statistics using Device Manager" (page 132) "Graphing Ethernet error statistics using Device Manager" (page 134) "Graphing spanning tree statistics using Device Manager" (page 136) NN Standard August 2007

132 132 Configuring and graphing ports using Device Manager Graphing port statistics using Device Manager All graphing port tables have the following buttons: Line Chart, Area Chart, Bar Chart, Pie Chart, Export Data, Print table, Clear Counter, Close, and Help To reset the statistics counters, use the "Clear Counter" button When you click this button, all Cumulative, Average, Minimum, Maximum, and LastVal columns are reset to zero and automatically begin to recalculate statistical data The Clear Counter function in Device Manager does not affect the AbsoluteValue counter in the switch Instead, the Clear Counter function clears all cached data in Device Manager (except AbsoluteValue) To reset AbsoluteValue(s), use the Reset Counter function (Edit > Chassis > System) Some statistics are available only when you graph a single port For information on graphing EAPOL statistics, see Nortel Ethernet Routing Switch 8300 Configuration Security using Device Manager To graph port statistics for a single or multiple ports: Step Action 1 Select the port or ports you want to graph 2 Do one of the following: Right-click a port or ports On the shortcut menu, choose Graph From the Device Manager menu bar, choose Graph > Port On the Device Manager toolbar, click the Graph Selected button End Graphing interface statistics using Device Manager Use the Graph Interface tab to graph interface statistics To graph interface statistics: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Graph > Port The Graph Port dialog box opens with the Interface tab displayed ("Graph Port dialog box Interface tab" (page 133)) NN Standard August 2007

133 Graphing a port using Device Manager 133 Graph Port dialog box Interface tab End Graph Interface tab fields Field InOctets OutOctets InUcastPkts OutUcastPkts InMulticastPkts OutMulticastPkts InBroadcastPkts "Graph Interface tab fields" (page 133) describes the Interface tab fields in the Graph Port dialog box Description The total number of octets received on the interface, including framing characters The total number of octets transmitted out of the interface, including framing characters The number of packets delivered by this sublayer to a higher sublayer that were not addressed to a multicast or broadcast address at this sublayer The number of packets that higher-level protocols requested be transmitted that were not addressed to a multicast address at this sublayerthis total number includes those packets discarded or not sent The number of packets delivered by this sublayer to a higher sublayer that were addressed to a multicast address at this sublayer For a MAC layer protocol, this number includes both Group and Functional addresses The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a multicast address at this sublayer, including those that were discarded or not sent For a MAC layer protocol, this number includes both Group and Functional addresses The number of packets delivered by this sublayer to a higher sublayer that were addressed to a broadcast address at this sublayer NN Standard August 2007

134 134 Configuring and graphing ports using Device Manager Field OutBroadcastPkts InErrors InFlowCtrlPkts OutFlowCtrlPkts Description The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a broadcast address at this sublayer, including those that were discarded or not sent For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol The total number of flow control packets received by this interface The total number of flow control packets transmitted by this interface Graphing Ethernet error statistics using Device Manager Use the Ethernet Errors tab to graph Ethernet error statistics To graph Ethernet Error statistics: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Graph > Port The Graph Port dialog box opens with the Interface tab displayed 3 Click the Ethernet Errors tab The Ethernet Errors tab opens ("Graph Port dialog box Ethernet Errors tab" (page 134)) Graph Port dialog box Ethernet Errors tab End NN Standard August 2007

135 Graphing a port using Device Manager 135 "Ethernet Errors tab fields" (page 135) describes the Ethernet Errors tab fields Ethernet Errors tab fields Field FCSErrors InternalMacTransmitErrors InternalMacReceiveErrors Description A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check The count represented by an instance of this object is incremented when the framecheckerror status is returned by the MAC service to the LLC (or other MAC user) Received frames for which multiple error conditions obtained are, according to the conventions of IEEE 8023 Layer Management, counted exclusively according to the error status presented to the LLC A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3statslatecollisions object, the dot3statsexcessivecollisions object, or the dot3statscarriersenseerrors object The precise meaning of the count represented by an instance of this object is implementation specific In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3statsframetoolongs object, the dot3statsalignmenterrors object, or the dot3statsfcserrors object The precise meaning of the count represented by an instance of this object is implementation specific In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted NN Standard August 2007

136 136 Configuring and graphing ports using Device Manager Field FrameTooLongs SingleCollisionFrames LateCollisions ExcessiveCollisions FrameTooShorts LinkFailures Description A count of frames received on a particular interface that exceed the maximum permitted frame size The count represented by an instance of this object is incremented when the frametoolong status is returned by the MAC service to the LLC (or other MAC user) Received frames for which multiple error conditions obtained are, according to the conventions of IEEE 8023 Layer Management, counted exclusively according to the error status presented to the LLC A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifoutucastpkts, ifoutmulticastpkts, or ifoutbroadcastpkts, objects and is not counted by the corresponding instance of the dot3statsmultiplecollisionframes object The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet; 512 corresponds to 512 microseconds on a 10 Mb/s system A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics A count of frames for which transmission on a particular interface fails due to excessive collisions The total number of frames that are too short that were encountered on this interface The total number of link failures encountered on this interface Graphing spanning tree statistics using Device Manager Use the Spanning Tree tab to graph port spanning tree statistics To graph spanning tree statistics: Step Action 1 On the device view, select a port or multiple ports 2 From the Device Manager menu bar, choose Graph > Port The Graph Port dialog box opens with the Interface tab displayed 3 Click the Spanning Tree tab NN Standard August 2007

137 Graphing RMON statistics using Device Manager 137 Graph Port dialog box Spanning Tree tab The Graph Port dialog box opens with the Spanning Tree tab displayed ("Graph Port dialog box Spanning Tree tab" (page 137)) End "Spanning Tree tab fields" (page 137) describes the Spanning Tree tab fields Spanning Tree tab fields Field InConfigBpdus InTcnBpdus InBadBpdus OutConfigBpdus OutTcnBpdus Description The number of Config BPDUs received The number of Topology Change Notification BPDUs received The number of unknown or malformed BPDUs received The number of Config BPDUs transmitted The number of Topology Change Notification BPDUs transmitted Graphing RMON statistics using Device Manager Use the following procedure to enable RMON globally, enable Rmon Stats on a selected port, and use the RMON tab to graph RMON statistics To graph RMON statistics for a single port or multiple ports: Step Action 1 Right-click on the port you want to graph 2 Select Enable Rmon Stats 3 From the Device Manager menu bar, choose Graph > Port NN Standard August 2007

138 138 Configuring and graphing ports using Device Manager The Graph Port dialog box opens with the Interface tab displayed 4 Click the RMON tab The RMON tab opens (see "Graph Port dialog box RMON tab" (page 138)) Graph Port dialog box RMON tab 5 Select the statistic(s) you want to graph 6 In the Poll Interval box, select the polling interval 7 Click the Graph button (bar, pie, chart, line) End "RMON tab fields" (page 138) describes the fields in the RMON tab RMON tab fields Field DropEvents Description Number of events in which packets were dropped by the probe due to lack of resources during this interval Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected NN Standard August 2007

139 Graphing RMON History statistics using Device Manager 139 Field Octets Pkts BroadcastPkts MulticastPkts CRCAlignErrors UndersizePkts OversizePkts Fragments Jabbers Collisions Pkts64Octets Pkts65to127Octets Pkts128to255Octets Pkts256to1023Octets Pkts1024to1518Octets Description Number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets) You can use this object as a reasonable estimate of Ethernet utilization For greater precision, sample the etherstatspkts and etherstatsoctets objects before and after a common interval Number of packets (including bad packets, broadcast packets, and multicast packets) received Number of good packets received that were directed to the broadcast address Note that this number does not include multicast packets Number of good packets received that were directed to the multicast address Note that this number does not include packets directed to the broadcast address Number of packets received that had a length (excluding framing bits but including FCS octets) of between 64 and 1518 octets inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error) Number of packets received that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed Number of packets received that were more than 1518 octets long (excluding framing bits but including FCS octets) and were otherwise well formed Number of packets received that were less than 64 octets long (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error) It is entirely normal for etherstatsfragments to increment because it counts both runts (which are normal occurrences due to collisions) and noise hits The number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had a bad Frame Check Sequence (FCS) with either an FCS error or an Alignment error Estimated number of collisions on this Ethernet segment Number of packets received containing 64 octets Number of packets received containing between 65 and 127 octets Number of packets received containing between 128 and 255 octets Number of packets received containing between 256 and 1023 octets Number of packets received containing between 1024 and 1518 octets Graphing RMON History statistics using Device Manager To graph RMON History statistics for a single port or multiple ports: NN Standard August 2007

140 140 Configuring and graphing ports using Device Manager Step Action 1 If you have not already done so, enable RMON by choosing RMON > Options from the Device Manager menu bar 2 Right click on the port you want to graph 3 Select Enable Rmon History 4 From the Device Manager menu bar, choose Graph > Port The Graph Port dialog box opens with the Interface tab displayed 5 Click the RMON History tab The RMON History tab opens ("Graph Port dialog box RMON History tab" (page 140)) Graph Port dialog box RMON History tab 6 Select the statistic(s) you want to graph 7 In the Poll Interval box, select the polling interval 8 Click the Graph button (bar, pie, chart, line) End RMON History tab fields "RMON History tab fields" (page 140) describes the fields in the RMON History tab Field Description SampleIndex Uniquely identifies a specific etherstats entry The value range is 1 to NN Standard August 2007

141 Graphing RMON History statistics using Device Manager 141 Field Utilization Description If greater precision is required, you should sample the etherststspkts and etherstatsoctets objects before and after a common interval The differences in the sampled values are Pkts and Octets, respectively The number of seconds in the interval is Interval These values are used to calculate the utilization as follows: Octets Packets BroadcastPkts MulticastPkts DropEvents CRCAlignErrors UndersizePkts OversizePkts Fragments Collisions The result of this equation is the value Utilization, which is the percent utilization of the Ethernet segment on a scale of 0 to 100 percent The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets) You can use this object as a reasonable estimate of Ethernet utilization For greater precision, sample the etherstatspkts and etherstatsoctets objects before and after a common interval The total number of packets (including bad packets, broadcast packets, and multicast packets) received The total number of good packets received that were directed to the broadcast address Note that this number does not include multicast packets The total number of good packets received that were directed to a multicast address Note that this number does not include packets directed to the broadcast address The total number of events in which packets were dropped by the probe due to lack of resources during this interval Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error) The total number of packets received that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed The total number of packets received that were longer than 1518 octets (excluding framing bits but including FCS octets) and were otherwise well formed The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a nonintegral number of octets (Alignment Error) It is entirely normal for etherstatsfragments to increment because it counts both runts (which are normal occurrences due to collisions) and noise hits The best estimate of the total number of collisions on this Ethernet segment NN Standard August 2007

142 142 Configuring and graphing ports using Device Manager NN Standard August 2007

143 143 Configuring ports using the CLI This section describes editing and graphing layer 2 port functions on the Ethernet Routing Switch 8000 Series For a complete description of the CLI commands you can use to configure network management, see the appropriate CLI chapter in this guide The 10/100BASE-TX ports may not autonegotiate correctly with older 10/100BASE-TX equipment You can sometimes upgrade the older devices with new firmware or driver revisions If an upgrade does not allow autonegotiation to correctly identify the link speed and duplex settings, you can manually configure the settings for the link in question Check the Nortel Web site (wwwnortelcom) for the latest compatibility information Navigation "Configuring and monitoring port mirroring using the CLI" (page 143) "Configuring port parameters using the CLI" (page 146) "Setting rate limits using the CLI" (page 149) "Configuring port states using the CLI" (page 151) "Showing port statistics using the CLI" (page 156) Configuring and monitoring port mirroring using the CLI Port mirroring is a method of monitoring network traffic that forwards a copy of each incoming (ingress) and outgoing (egress) packet from one port of a network switch to another port where the packet can be studied A network administrator uses port mirroring as a diagnostic tool or debugging feature, especially when fending off an attack It enables the administrator to closely monitor switch performance and alter it, if necessary Port mirroring can be managed locally or remotely When you enable port mirroring, you must specify a: The source ports from which traffic is mirrored A destination port to see mirrored traffic NN Standard August 2007

144 144 Configuring ports using the CLI Any packet entering or exiting the specified ports is forwarded normally, and a copy of the packet is sent out the mirror port When this feature is active, all packets received on the specified ports are copied to the port specified as the out port The mirroring operation is nonintrusive Creating an ingress port-mirror using the CLI To create an ingress port mirror, use the following command: config diag mirror-by-port <id> where id is the mirror by port entry id This command uses the following parameters: config diag mirror-by-port <id> followed by: info create enable <true false> delete mirrored-port mirroring-port mode <rx tx both> Shows current level parameter settings and next level directories Creates a new mirror-by-port table entry Enables or disables this port mirroring instance The default value is true Deletes an entry from mirror by port table Allows you to specify a port to be mirrored (source port) You can select ports from any module in your configuration by clicking the ellipses button to the right of the field Specifies a destination port (the port to which the mirrored packets are forwarded) You can select ports from any module in your configuration by clicking the ellipses button to the right of the field Specifies the traffic direction of the packet being mirrored--rx, Tx, or both The default configuration is Rx Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5# config diag mirror-by-port 13 ERS-8310:5/config/diag/mirror-by-port/13# create in-port 7/1 out-port 7/5 mode rx enable true ERS- 8310:5/config/diag/mirror-by-port/13# info Sub-Context: Current Context: create : NN Standard August 2007

145 Configuring and monitoring port mirroring using the CLI 145 enable : true mirrored-port : 7/1 mirroring-port : 7/5 mode : rx delete : N/A ERS-8310:5/config/diag/mirror-by-port/13# Deleting a port-mirror using the CLI To delete a port mirror, use the following command: ERS-8310:5/config/diag/mirror-by-port/13# delete Changing the mode of a port-mirror To change the mode of a port-mirror, use the following command: ERS-8310:5/config/diag/mirror-by-port/13# mode both ERS-8310:5/config/diag/mirror-by-port/13# info Sub-Context: Current Context: create : enable : true mirrored-port : 7/1 mirroring-port : 7/5 mode : both delete : N/A Changing a mirrored port using the CLI To change the mirrored port, use the following command: ERS-8310:5/config/diag/mirror-by-port/13# mirrored-port 7/13 ERS-8310:5/config/diag/mirror-by-port/13# info Sub-Context: Current Context: create : enable : true mirrored-port : 7/13 mirroring-port : 7/5 mode : both delete : N/A Changing a mirroring/analyzer port using the CLI To change a mirroring port, use the following command: ERS-8310:5/config/diag/mirror-by-port/13# mirroring-port 7/25 ERS-8310:5/config/diag/mirror-by-port/13# info Sub-Context: Current Context: NN Standard August 2007

146 146 Configuring ports using the CLI create : enable : false mirrored-port : 7/13 mirroring-port : 7/25 mode : both delete : N/A ERS-8310:5/config/diag/mirror-by-port/13# Displaying information of port-mirror configuration in a switch using the CLI ERS-8310:5/config/diag/mirror-by-port/13# show diag mirror-by-port ============================================================ Diag Mirror-By-Port ============================================================ ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /13 7/25 false both ERS-8310:5/config/diag/mirror-by-port/13# Disabling a mirroring/analyzer port using the CLI To disable a mirroring port, use the following command: ERS-8310:5/config/diag/mirror-by-port/13# enable false ERS-8310:5/config/diag/mirror-by-port/13# info Sub-Context: Current Context: create : enable : false mirrored-port : 7/13 mirroring-port : 7/5 mode : both delete : N/A Configuring port parameters using the CLI To configure port parameters, including the speed and duplex capabilities of the port, use the following command config ethernet <port> where port is the slot/port number of the port you want to configure This command uses the following parameters: NN Standard August 2007

147 Configuring port parameters using the CLI 147 config ethernet <port> followed by: info action <action choice> auto-negotiate <enable disable> auto-negotiationadvertisements [10-full 10- half 100- full 100- half 1000-full half default none] bcast-mcast-rate-limit cp-limit default-vlan-<vid> duplex <half full> linktrap <enable disable> lock <true false> name perform-tagging <enable disable> speed < > state <enable disable test> Displays rate limit information Creates a new mirror by port table entry Enables or disables autonegotiation Allows you to select the speed and duplex capabilities of the port The valid options are: 10-full - Advertise 10Mbps at full duplex 10-half - Advertise 10Mbps at half duplex 100-full - Advertise 100Mbps at full duplex 100-half - Advertise 100Mbps at half duplex 1000-full - Advertise 1000Mbps at full duplex 1000-half - Advertise 1000Mbps at half duplex default - Enables all advertisements supported by the port none - Disables auto-negotiation You can enter any combination of speed/duplex; the capabilities can be entered in any order that they appear (eg, 10-full 100-full) Specifies broadcast and multicast rate limits Specifies cp rate limits Specifies a default VLAN id Sets duplex to either half or full Enables or disables link trapping Enables or disables a lock Specifies a name Enables or disables performance tagging Specifies a speed in seconds Enables, disables, or tests a port state NN Standard August 2007

148 148 Configuring ports using the CLI tx-queue <queue-id> [transmit <value>] [size <value>] [scheduler <value>] [weight <value>] [shaper <value>] [rate <value>] [burst-size <value>] untag-port-defaultvlan <enable disable> untaggedframes-discard <enable disable> Configures traffic queuing on a port Enables or disables a tag to be sent for the default VLAN ID When enabled, all other VLAN IDs other then default VLAN ID will send a tag Enables or disables the discarding of untagged frames on a perform-tagging enabled port Configuration example After configuring the parameters, use the info command to show a summary of the results ERS-8310:5/config/ethernet/1/1# info Sub-Context: Current Context: Port 1/1 : eapol filter qos stg unknown-mac-discard vct lock : false name : auto-negotiate : true auto-negotiate-ads : 10-full 10-half 100-full 100-half unknown-mac-discard : disable default-vlan-id : 1 perform-tagging : disable untag-port-default-vlan : disable untagged-frames-discard : disable state : up linktrap : enable bcast-mcast-rate-limit : disabled cp-limit : enabled multicast-limit 5000 broadcast-limit 5000 ======================================================================== Port Transmit Queue ======================================================================== PORT QUEUE TRAFFIC TX BUFFER SCHED WEIGHT SHAPER SHAPER BURST NUM ID CLASS ENABLE SIZE GROUP ENABLE RATE SIZE /1 0 0 enable 32 DWRR1 3 disable /1 1 1 enable 32 DWRR1 3 disable 10 4 NN Standard August 2007

149 Setting rate limits using the CLI 149 Setting rate limits using the CLI Multicast/broadcast traffic is usually forwarded from a port or MLT to other ports and MLTs in the same VLAN Rate limiting allows you to set the ingress rate of multicast/broadcast traffic on a port and MLT You can also use rate limits to prevent excessive traffic ingress to the other ports and MLTs on the VLAN Broadcast and multicast rate limiting configurations are performed in the interface level Enabling rate limits on ingress traffic for a port using the CLI To configure rate limits, use the following command config ethernet <port> bcast-mcast-rate-limit <value> enable where port is the slot/port number of the port you want to configure value is the percentage Broadcast and Multicast of port speed Configuration example To enable rate limits on ingress traffic rate for a port (for example, 7/15) to 1% Broadcast and Multicast of port speed, use the following command Then, use the info command to show a summary of the results ERS-8310:5/config/ethernet/1/1# bcast-mcast-rate-limit 1 enable ERS-8310:5/config/ethernet/1/1# info Sub-Context: eapol filter qos stg unknown-mac-discard vct Current Context: ERS-8310:5/config/ethernet/1/1# info Sub-Context: Current Context: Port 1/1 : eapol filter qos stg unknown-mac-discard vct lock : false name : auto-negotiate : true auto-negotiate-ads : 10-full 10-half 100-full 100-half unknown-mac-discard : disable default-vlan-id : 1 perform-tagging : disable untag-port-default-vlan : disable untagged-frames-discard : disable state : up linktrap : enable bcast-mcast-rate-limit : disabled cp-limit : enabled multicast-limit 5000 NN Standard August 2007

150 150 Configuring ports using the CLI ========================================================================== ========================================================================== broadcast-limit Port Transmit Queue PORT QUEUE TRAFFIC TX BUFFER SCHED WEIGHT SHAPER SHAPER BURST NUM ID CLASS ENABLE SIZE GROUP ENABLE RATE SIZE 7/ enable 32 DWRR1 3 disable / enable 32 DWRR1 3 disable / enable 32 DWRR1 6 disable / enable 32 DWRR1 8 disable / enable 16 DWRR1 10 disable / enable 16 DWRR1 12 disable / enable 16 DWRR1 36 disable / enable 16 Priority N/A disable 10 4 Disabling broadcast and multicast rate limits using the CLI To disable Broadcast and Multicast rate limit for a port, use the following command: bcast-mcast-rate-limit 1 disable Configuration example After disabling broadcast and multicast rate limits for a port, use the info command to show a summary of the results ERS-8310:5/config/ethernet/1/1# bcast-mcast-rate-limit 1 disable ERS-8310:5/config/ethernet/1/1# info Sub-Context: eapol filter qos stg unknown-mac-discard vct Current Context: Port 1/1 : ERS-8310:5/config/ethernet/1/1# info Sub-Context: eapol filter qos stg unknown-mac-discard vct Current Context: Port 1/1 : lock : false name : auto-negotiate : true auto-negotiate-ads : 10-full 10-half 100-full 100-half unknown-mac-discard : disable default-vlan-id : 1 NN Standard August 2007

151 Configuring port states using the CLI 151 ========================================================================== ========================================================================== perform-tagging : disable untag-port-default-vlan : disable untagged-frames-discard : disable state : up linktrap : enable bcast-mcast-rate-limit : disabled cp-limit : enabled multicast-limit 5000 broadcast-limit 5000 Port Transmit Queue PORT QUEUE TRAFFIC TX BUFFER SCHED WEIGHT SHAPER SHAPER BURST NUM ID CLASS ENABLE SIZE GROUP ENABLE RATE SIZE 7/ enable 32 DWRR1 3 disable / enable 32 DWRR1 3 disable / enable 32 DWRR1 6 disable / enable 32 DWRR1 8 disable / enable 16 DWRR1 10 disable / enable 16 DWRR1 12 disable / enable 16 DWRR1 36 disable / enable 16 Priority N/A disable 10 4 Displaying rate limiting for a port using the CLI To display rate limiting info for a port: ERS-8310:5# show ports info rate-limit 7/15 ================================================================== Port Rate Limiting ================================================================== PORT TYPE PERCENT ENABLED/DISABLED /15 BROADCAST-MULTICAST 1 DISABLED ERS-8310:5# Configuring port states using the CLI It will give the information of port status How the port has been configured, what s the port speed, whether it is half duplex or full duplex etc We can also get the information on qos, filter, route-discovery, rate-limit, tx-queue, NN Standard August 2007

152 152 Configuring ports using the CLI unknown-mac-discard configuration of the ports These information are important for network administrative purpose and for debugging network issues Viewing port states using the CLI The ability to view a port s state is important for network administration and debugging When you view port states, you can determine the port configuration, the port speed, and whether it is half duplex or full duplex etc You can also obtain information on QoS, filter, route-discovery, rate-limit, tx-queue, and unknown-mac-discard configuration of the ports To view a port s state, use the following command: show ports info This command uses the following parameters: show ports info followed by: all [<ports>] [by <value>] auto-negotiateadvertisements [<ports>] auto-negotiate-adcapability [<ports>] config [<ports>] filter [<ports>] interface [<ports>] name [<ports>] qos [<ports>] route-discovery [<ports>] rate-limit [<ports>] tx-queue [<ports>] Shows all information for the port Shows the configured speed and duplex capabilities for the specified port(s), or for all ports Shows the speed and duplex capabilities for the specified port(s), or for all ports Specifies port specific configuration and operational information, such as autoneg, speed, duplexity, QoS, mltid, etc Shows the filter configuration on the port Shows the basic interface parameters; for example, ifindex, description (port type), link trap, lock, MTU, MAc address, admin, and operating status Specifies the name, port type, operating status, speed, duplexity and tagging info Shows the QoS parameters Not supported for this release Shows the rate limiting information Shows the port transmit queue configuration parameters NN Standard August 2007

153 Configuring port states using the CLI 153 unknown-mac-discard [<ports>] vlans [<ports> Shows the unknown MAC discard parameters Shows the vlan related parameters configured on the port For each of these options, you can specify a port number or a port list optionally If you do not specify a port number or port list, the command displays information for all ports in the system Configuration examples The following are examples of output from several of the show ports info output ERS-8310:5# show ports info config 5/1 ERS-8310:5# show ports info filter ERS-8310:5# show ports info interface 5/1 ERS-8310:5# show ports info name 5/1 NN Standard August 2007

154 154 Configuring ports using the CLI ERS-8310:5# show ports info qos 5/1 ERS-8310:5# show ports info route-discovery 5/1 ERS-8310:5# show ports info tx-queue 5/1 ERS-8310:5# show ports info unknown-mac-discard 5/1 NN Standard August 2007

155 Configuring port states using the CLI 155 ERS-8310:5# show ports info vlans 5/1 ========================================================================== ========================================================================== ========================================================================== ========================================================================== ERS-8310:5/show/ports/info# auto-negotiate-advertisements Port Auto-Neg Ads PORT AUTO-NEGOTIATION NUM ADVERTISEMENTS 1/1 10-full 10-half 100-full 100-half 1/2 10-full 10-half 100-full 100-half 1/3 10-full 10-half 100-full 100-half 1/4 10-full 10-half 100-full 100-half 1/5 10-full 10-half 100-full 100-half 1/6 10-full 10-half 100-full 100-half 1/7 10-full 10-half 100-full 100-half 1/8 10-full 10-half 100-full 100-half 1/9 10-full 10-half 100-full 100-half 1/10 10-full 10-half 100-full ERS-8310:5/show/ports/info# auto-negotiate-ad-capability Port Auto-Neg Ad Capability PORT AUTO-NEGOTIATION NUM ADVERTISEMENTS 1/1 10-full 10-half 100-full 100-half 1/2 10-full 10-half 100-full 100-half 1/3 10-full 10-half 100-full 100-half 1/4 10-full 10-half 100-full 100-half 1/5 10-full 10-half 100-full 100-half 1/6 10-full 10-half 100-full 100-half NN Standard August 2007

156 156 Configuring ports using the CLI 1/7 10-full 10-half 100-full 100-half 1/8 10-full 10-half 100-full 100-half 1/9 10-full 10-full 100-full 100-half 1/10 10-full 10-half 100-full Showing port statistics using the CLI Statistical data information for a port is important for network administration and for network debugging The port statistics feature provides statistical results of data traffic through a particular port It provides in-coming and outgoing data information of that port in terms of octets, packets, unicast, multicast, and broadcast No only can you obtain the absolute data value of a particular port, but you can obtain cumulative data as well as average, minimum, maximum, and the current data rate of that port Port statistics also provides information on discarded packets, error packets, and oversize-undersize packets You can also obtain the statistical data of STG BPDU packets Showing port information using the CLI To display port information, enter the following commands: ERS-8310:5# show ports ERS-8310:5/show/ports#? Sub-Context: error info stats Current Context: ERS-8310:5/show/ports# Showing port stats information using the CLI To display port information, enter the following commands: ERS-8310:5/show/ports# stats ERS-8310:5/show/ports/stats#? This command uses the following parameters: show ports info followed by: rmon stg Shows port RMON information Shows port STG informations Showing port error information using the CLI To display port error information, enter the following commands: ERS-8310:5/show/ports# error ERS-8310:5/show/ports/stats#? NN Standard August 2007

157 Showing port statistics using the CLI 157 This command uses the following parameters: show ports error followed by: collision extended main ospf Shows port collision information Shows port extended information Shows port main information Shows port OSPF information Showing RMON stats information using the CLI To display port information, enter the following commands: ERS-8310:5/show/ports# stats ERS-8310:5/show/ports/stats# rmon 8/13 Sub-Context:interface Current Context: rmon [<ports>] stg [<ports>] ========================================================================== Port Stats Rmon ========================================================================== PORT OCTETS PKTS MULTI BROAD CRC UNDER OVER FRAG COLLI NUM CAST CAST ALLIGN SIZE SIZE MENT SION / Showing STG stats information To display port information, enter the following commands: ERS-8310:5/show/ports# stats ERS-8310:5/show/ports/stats# stg 7/13 ========================================================================== Port Stats Stg ========================================================================== PORT IN_CONFIG IN_TCN IN_BAD OUT_CONFIG OUT_TCN NUM BPDU BPDU BPDU BPDU BPDU / NN Standard August 2007

158 158 Configuring ports using the CLI NN Standard August 2007

159 159 Configuring ports using the NNCLI This chapter describes editing and graphing layer 2 port functions on the Ethernet Routing Switch 8000 Series switch using the NNCLI The 10/100BASE-TX ports may not autonegotiate correctly with older 10/100BASE-TX equipment You can sometimes upgrade the older devices with new firmware or driver revisions If an upgrade does not allow autonegotiation to correctly identify the link speed and duplex settings, you can manually configure the settings for the link in question Check the Nortel Web site (wwwnortelcom) for the latest compatibility information For a complete description of the NNCLI commands you can use to configure network management, see the appropriate NNCLI chapter in this guide Navigation "Configuring and monitoring port mirroring using the NNCLI" (page 159) "Configuring port parameters using the NNCLI" (page 163) "Configuring port states using the NNCLI" (page 168) "Showing port statistics using the NNCLI" (page 171) Configuring and monitoring port mirroring using the NNCLI Port mirroring is a method of monitoring network traffic that forwards a copy of each incoming (ingress) and outgoing (egress) packet from one port of a network switch to another port where the packet can be studied A network administrator uses port mirroring as a diagnostic tool or debugging feature, especially when fending off an attack It enables the administrator to closely monitor switch performance and alter it, if necessary Port mirroring can be managed locally or remotely When you enable port mirroring, you must specify: The source ports from which traffic is mirrored A destination port to see mirrored traffic NN Standard August 2007

160 160 Configuring ports using the NNCLI Any packet entering or exiting the specified ports is forwarded normally, and a copy of the packet is sent out the mirror port When this feature is active, all packets received on the specified ports are copied to the port specified as the out port The mirroring operation is nonintrusive Creating an ingress port-mirror using the NNCLI Port mirroring is set in the Configuration Terminal mode To create an ingress port mirror, use the following command: port-mirroring <id> <mode> <mirrored -port> <mirroringport> enable where id is the mirror by port entry id <mode> is the direction of traffic being mirrored <mirrored-port> is the slot/ports of the mirrored port <mirroring-port> is the slot/ports of the mirroring port This command uses the following parameters: port-mirroring <id> followed by: id enable disable mirrored-port mirroring-port mode <rx tx both> The ID of the new mirror-by-port table entry Enables this port mirroring instance Disables this port mirroring instance Allows you to specify a port to be mirrored (source port) You can select ports from any module in your configuration by clicking the ellipses button to the right of the field Specifies a destination port (the port to which the mirrored packets are forwarded) You can select ports from any module in your configuration by clicking the ellipses button to the right of the field Specifies the traffic direction of the packet being mirrored--rx, Tx, or both The default configuration is Rx Configuration example After configuring the parameters, use the sho command to show a summary of the results ERS-8306:5(config)#port-mirroring 1 rx 1/3 1/13 enable ERS-8306:5(config)#sho port-mirroring ================================================================== NN Standard August 2007

161 Configuring and monitoring port mirroring using the NNCLI 161 Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 1/13 true rx Deleting a port-mirror using the NNCLI To delete a port-mirror, use the following command: no port-mirroring 1 where id is the port entry ID of the port-mirror you want to delete Configuration example After configuring the parameters, use the sho command to show a summary of the results ERS-8306:5(config)#no port-mirroring 1 ERS-8306:5(config)#sho port-mirroring ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE Changing a mode of a port-mirror using the NNCLI To change the mode of a port-mirror, use the following command: port-mirroring 1 mode tx where id is the port entry ID of the port-mirror whose mode you want to change Configuration example After configuring the parameters, use the sho command to show a summary of the results ERS-8306:5(config)#port-mirroring 1 mode tx ERS-8306:5(config)#sho port-mirroring ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 1/13 true tx Changing a mirrored port using the NNCLI To change a mirrored port, use the following command: port-mirroring 1 monitor-port 2/2 NN Standard August 2007

162 162 Configuring ports using the NNCLI where id is the port entry ID of the port-mirror whose mode you want to change Configuration example After configuring the parameters, use the sho command to show a summary of the results ERS-8306:5(config)#port-mirroring 1 monitor-port 2/3 ERS-8306:5(config)#sho port-mirroring ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 1/13 true tx Disabling a port-mirroring using the NNCLI To change a mirrored port, use the following command: port-mirroring 1 disable where id is the port entry ID of the port-mirroring you want to disable Configuration example After configuring the parameters, use the sho command to show a summary of the results ERS-8306:5(config)#port-mirroring 1 disable ERS-8306:5(config)#show port-mirroring ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 1/13 false tx Changing a mirroring/analyzer port using the NNCLI To change a mirroring analyzer port, use the following command: port-mirroring <id> mirror-port <port> where id is the port entry ID and <port> is the slot/port of the new mirroring port Configuration example After configuring the parameters, use the show command to show a summary of the results ERS-8306:5(config)#port-mirroring 1 mirror-port 2/37 ERS-8306:5(config)#show port-mirroring NN Standard August 2007

163 Configuring port parameters using the NNCLI 163 ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 2/37 true tx Displaying information of port-mirror configuration in a switch using the NNCLI To display port-mirror configuration information, use the following command: ERS-8306:5(config)# show port-mirroring ================================================================== Diag Mirror-By-Port ================================================================== ID MIRRORED_PORT MIRRORING_PORT ENABLE MODE /3 2/37 true tx Configuring port parameters using the NNCLI To configure port parameters, including the speed and duplex capabilities of the port, navigate to Interface configuration mode from Global configuration mode using the following command: interface <FastEthernet GigabitEthernet> <port> where <port> is the slot/port of the port you want to configure This command uses the following parameters: interface fastethernet <port> followed by: info Displays rate limit information action <action choice> auto-negotiate <enable disable> Creates a new mirror by port table entry Enables or disables autonegotiation NN Standard August 2007

164 164 Configuring ports using the NNCLI interface fastethernet <port> followed by: auto-negotiationadvertisements [10-full 10-half 100-full 100-half 1000-full 1000-half none] Allows you to select the speed and duplex capabilities of the port The valid options are: 10-full - Advertise 10Mbps at full duplex 10-half - Advertise 10Mbps at half duplex 100-full - Advertise 100Mbps at full duplex 100-half - Advertise 100Mbps at half duplex 1000-full - Advertise 1000Mbps at full duplex 1000-half - Advertise 1000Mbps at half duplex none - Disables auto-negotiation bcast-mcast-rate-limit cp-limit default <autonegotiationadvertisements eapol mroute-stream-limit> default-vlan-<vid> duplex <half full> linktrap <enable disable> lock <true false> name perform-tagging <enable disable> speed < > You cannot use this command to apply different speed and duplex capabilities within a group of ports If a group of ports are specified, the speed and duplex capabilities entered are applied to all ports Specifies broadcast and multicast rate limits Specifies cp rate limits Specifies default values for parameters The valid options are: auto-negotiation-advertisements - specifies default auto negotiation advertisements eapol - sets the default EAPOL protocol setting mroute-stream-limit - this is the global mroute stream limit Specifies a default VLAN id Sets duplex to either half or full Enables or disables linktrapping Enables or disables a lock Specifies a name Enables or disables performance tagging Specifies a speed in seconds NN Standard August 2007

165 Setting rate limits using the NNCLI 165 interface fastethernet <port> followed by: state Enables, disables, or tests a port state <enable disable test> tx-queue <queue-id> [transmit <value>] [size <value>] [scheduler <value>] [weight <value>] [shaper <value>] [rate <value>] [burst-size <value>] untag-port-defaultvlan <enable disable> untaggedframes-discard <enable disable> Configures traffic queuing on a port Enables or disables a tag to be sent for the default VLAN ID When enabled, all other VLAN IDs, other then default VLAN ID, will send a tag Enables or disables the discarding of untagged frames on a perform-tagging enabled port Configuring default auto-negotiation-advertisements using the NNCLI To configure default auto-negotiation-advertisements port parameters, navigate to Interface configuration mode from Global configuration mode using the following command: interface <FastEthernet GigabitEthernet> <port> auto-negotiation-advertisements where <port> is the slot/port of the port you want to configure To restore default values for auto-negotiation-advertisements, enter the following: default auto-negotiation-advertisements Setting rate limits using the NNCLI Multicast/broadcast traffic is usually forwarded from a port or MLT to other ports and MLTs in the same VLAN Rate limiting allows you to set the ingress rate of multicast/broadcast traffic on a port and MLT You can also use rate limits to prevent excessive traffic ingress to the other ports and MLTs on the VLAN Rate limits are set in the Configuration Terminal mode NN Standard August 2007

166 166 Configuring ports using the NNCLI To enable rate limiting on ingress traffic for a port, use the following command from Interface Configuration mode: bcast-mcast-rate-limit <value> where value is the percentage Broadcast and Multicast of port speed Configuration example The commands in this example enable a rate limit on ingress traffic for port 2/25 to 1% Broadcast and Multicast of port speed ERS-8306:5(config)#interface fastethernet 2/25 ERS-8306:5(config-if)# bcast-mcast-rate-limit 1 ERS-8306:5(config-if)# Showing rate limiting information using the NNCLI To show rate limiting information, use the following command: show interfaces fastethernet <port> where <port> is the slot/port of the port for which you want to display rate limits Example NN Standard August 2007

167 Setting rate limits using the NNCLI 167 NN Standard August 2007

168 168 Configuring ports using the NNCLI Configuring port states using the NNCLI Configure the port to ensure optimum performance Viewing port states using the NNCLI The ability to view a port s state is important for network administration and debugging When you view port states, you can determine the port configuration, the port speed, and whether it is half duplex or full duplex etc You can also obtain information on QoS, filter, route-discovery, rate-limit, tx-queue, and unknown-mac-discard configuration of the ports To view a port s state, use the following command: show GigabitEthernet This command uses the following parameters: show ports info followed by: all [<ports>] [by <value>] config [<ports>] filter [<ports>] interface [<ports>] name [<ports>] qos [<ports>] route-discovery [<ports>] rate-limit [<ports>] tx-queue [<ports>] Shows all information for the port Specifies port specific configuration and operational information, such as autoneg, speed, duplex mode, QoS, mltid, etc Shows the filter configuration on the port Shows the basic interface parameters; for example, ifindex, description (port type), link trap, lock, MTU, MAc address, admin, and operating status Specifies the name, port type, operating status, speed, duplexity and tagging info Shows the QoS parameters Not supported for this release Shows the rate limiting information Shows the port transmit queue configuration parameters NN Standard August 2007

169 Configuring port states using the NNCLI 169 show ports info followed by: unknown-mac-discard [<ports>] vlans [<ports> Shows the unknown MAc discard parameters Shows the vlan related parameters configured on the port Configuration examples The following are examples of output from several of the show ports info output NN Standard August 2007

170 170 Configuring ports using the NNCLI NN Standard August 2007

171 Showing port statistics using the NNCLI 171 Showing port statistics using the NNCLI Statistical data information for a port is important for network administration and for network debugging The port statistics feature provides statistical results of data traffic through a particular port It provides in-coming and outgoing data information of that port in terms of octets, packets, unicast, multicast, and broadcast No only can you obtain the absolute data value of a particular port, but you can obtain cumulative data as well as average, minimum, maximum, and the current data rate of that port Port statistics also provides information on discarded packets, error packets, and oversize-undersize packets You can also obtain the statistical data of STG BPDU packets Showing port information using the CLI To display port information, enter the following commands: ERS-8310:5# show ports ERS-8310:5/show/ports#? Sub-Context: error info stats Current Context: ERS-8310:5/show/ports# NN Standard August 2007

172 172 Configuring ports using the NNCLI Showing port stats information using the CLI To display port information, enter the following commands: ERS-8310:5/show/ports# stats ERS-8310:5/show/ports/stats#? Sub-Context: interface Current Context: rmon [<ports>] stg [<ports>] ERS-8310:5/show/ports/stats# This command uses the following parameters: show ports info followed by: config [<ports>] eapol [<ports>] error [<ports>] filter [<ports>] igmp interface [<ports>] name [<ports>] qos [<ports>] statistics tx-queue [<ports>] unknown-mac-discard [<ports>] vlan [<slot/port>] rmon stg Shows port config information Shows port EAP informations Shows port general error information Shows port filter information Shows port IP IGMP information Shows general port information Shows port names Shows QoS status of each port Shows port statistics Shows transmit queue information Shows port unknown MAC discard information Shows port VLAN information Shoes port RMON statistics Shows port STG statistics Configuration example This example uses the show command to display statistics on a port NN Standard August 2007

173 Showing port statistics using the NNCLI 173 NN Standard August 2007

174 174 Configuring ports using the NNCLI NN Standard August 2007

175 Showing port statistics using the NNCLI 175 NN Standard August 2007

176 176 Configuring ports using the NNCLI NN Standard August 2007

177 177 Configuring and graphing chassis information using Device Manager This chapter describes editing and graphing the Ethernet Routing Switch 8000 Series chassis using Device Manager The first three sections describe how you can use Device Manager to configure your Ethernet Routing Switch 8300 switch The last section describes how to use Device Manager to graph switch statistics Navigation "Editing the chassis" (page 177) "Editing cards" (page 185) "Editing objects" (page 193) "Graphing chassis statistics" (page 206) Editing the chassis Use the tabs in the chassis dialog box to edit the Ethernet Routing Switch 8000 Series chassis To edit the Ethernet Routing Switch 8000 Series chassis: Step Action 1 Select the chassis 2 From the Device Manager menu bar, choose Edit > Chassis End The following sections provide a description of the chassis tabs in the Edit > Chassis dialog box and details about each field on the tab NN Standard August 2007

178 178 Configuring and graphing chassis information using Device Manager Editing system information You can edit system information such as the contact person, the name of the device and where it is located Other information cannot be edited, but is very useful, such as what version of the software is running on the device To open the System tab: Chassis dialog box System tab â On the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed ("Chassis dialog box System tab" (page 178)) "System tab fields" (page 179) describes the System tab fields NN Standard August 2007

179 Editing the chassis 179 System tab fields Field sysdescr sysuptime syscontact sysname syslocation VirtualIPAddr VirtualNetMask ReadWriteLevel: AuthenticationTraps Description The system assigned name and the software version it is running The time since the system was last booted The contact information (in this case, an address) for the Nortel support group The name of this device The physical location of this device The virtual IP address is the IP address advertised by the master CPU Unlike the management port IP address, this address is stored in the switch configuration file and not the boot configuration file The net mask of the virtual management IP address Displays the access level of the trusted host (readonly, readwrite, or readwriteall) Enables or disables authentication traps When you enable, SNMP traps are sent to trap receivers for all SNMP access authentication EnableWebServer EnableAccess Policy LastChange LastVlanChange LastStatisticsReset LastRunTimeConfigSave To view traps, click the Trap Log button on the Device Manager toolbar Enables or disables the Web HTML server When enabled, it allows the system to be monitored using a Web browser Enables or disables Access Policy settings The time since the last configuration change The time since the last VLAN change The time since the statistics counters were last reset The last run-time configuration that was saved LastRunTimeConfigSaveToSlave The last run-time configuration that was saved to the standby device LastBootConfigSave LastBootConfigSaveOnSlave The last boot configuration that was saved The last boot configuration that was saved on the standby device DefaultRuntimeConfigFileName The default Runtime Configuration File directory name NN Standard August 2007

180 180 Configuring and graphing chassis information using Device Manager Field DefaultBootConfigFileName ConfigFileName Action Description The default Boot Configuration File directory name Allows you to type the name of a new configuration file Can be one of the following actions: LastActionResult hardreset Resets the device and runs power-on tests softreset Resets the device without running power-on tests resetcounters Resets all statistics counters cpuswitchover Switch control from one CPU to another resetconsole Reinitializes the hardware UART drivers Use only if the console or modem connection is hung saveruntimeconfig Saves the current run-time configuration saveruntimeconfigtoslave Saves the current run-time configuration to the standby CPU savebootconfig Saves the current boot configuration saveslavebootconfig Saves the current boot configuration to the standby CPU Displays a message after you click Apply Editing chassis information To edit the chassis information: Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the Chassis tab The Chassis tab opens ("Chassis dialog box Chassis tab" (page 181)) NN Standard August 2007

181 Editing the chassis 181 Chassis dialog box Chassis tab End "Chassis tab fields" (page 181) describes the Chassis tab fields Chassis tab fields Field Type SerialNumber HardwareRevision NumSlots NumPorts BaseMacAddr MacAddrCapacity Temperature Description The 8300 Series module type A unique chassis serial number The current hardware revision of the device chassis The number of slots (or cards) this device can contain The number of ports currently on this device Starting point of the block of MAC addresses used by the switch for logical and physical interfaces Specifies a MAC address capacity The current temperature of the chassis Viewing the boot configuration You can view the boot source and the source from which the switch booted last To view the boot configuration: NN Standard August 2007

182 182 Configuring and graphing chassis information using Device Manager Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the Boot Config tab The Boot Config tab opens (Figure 42) End Chassis dialog box Boot Config tab "Boot Config tab fields" (page 182) describes the Boot Config tab fields Boot Config tab fields Field Slot SwVersion LastBootConfigSource LastRuntimeImageSource LastRuntimeConfigSource Description The slot number of the device The software version that is currently running The last source from which the switch booted The last source from which the run-time image was taken The last source from which the run-time configuration was taken Editing trap receivers You can edit howmachines will receive SNMP traps by editing the community strings and the SNMP version format When Device Manager opens a device, it automatically adds the machine on which it is running to the Trap Receivers list only if the Register for Traps box on the Properties dialog box is checked If the Trap Receivers tab takes a long time to open, it may be that the IP address of a trap receiver cannot be resolved to a DNS name By default, Device Manager attempts to resolve IP addresses to DNS names To edit how traps will be received: NN Standard August 2007

183 Editing the chassis 183 Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the Trap Receivers tab The Trap Receivers tab opens ("Chassis dialog box Trap Receivers tab" (page 183)) Chassis dialog box Trap Receivers tab End "Trap Receivers tab fields" (page 183) describes the Trap Receivers tab fields Trap Receivers tab fields Field IpAddress Community Version Description IP address for the trap receiver (This value may be displayed as a DNS host name, but it was entered originally as an IP address) Community string used for trap messages to this trap receiver By default, traps are sent in SNMP V2c format If you are using an older NMS that supports only V1 traps (for example, HP OpenView) you should select that field Note that UNIX management stations must run Device Manager as Root to receive traps Checking system performance You can check system performance with theperformance tab To open the Performance tab: NN Standard August 2007

184 184 Configuring and graphing chassis information using Device Manager Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the Performance tab The Performance tab opens ("Chassis dialog box Performance tab" (page 184)) Chassis dialog box Performance tab End "Performance tab fields" (page 184) describes the Performance tab fields Performance tab fields Field DramSize DramUsed DramFree CpuUtil SwitchFabricUtil OtherSwitchFabricUtil Description The DRAM size in megabytes The percentage of DRAM space used The amount of DRAM free in kilobytes Percentage of CPU utilization Percentage of switch fabric utilization Percentage of other switch fabric utilization Setting the time You can set the date and time on the switch with the User Set Time tab To open the User Set Time tab: NN Standard August 2007

185 Editing cards 185 Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the User Set Time tab The User Set Time tab opens ("Chassis dialog box User Set Time tab" (page 185)) Chassis dialog box User Set Time tab End "User Set Time tab fields" (page 185) describes the User Set Time tab fields User Set Time tab fields Field Description Year The year (integer ) Month The month (integer 112) Date The day (integer 131) Hour The hour (integer 023) Minute The minute (integer 059) Second The second (integer 059) Editing cards For instructions about configuring PoE cards, refer to Nortel Ethernet Routing Switch 8300 Configuration Power over Ethernet (NN ) NN Standard August 2007

186 186 Configuring and graphing chassis information using Device Manager Use Device Manager card editing capabilities to view status information for two types of cards, I/O cards and CPU cards To edit the Ethernet Routing Switch 8300 modules (cards): Step Action 1 Select one or more modules 2 Do one of the following: Double-click the module Right-click the module On the shortcut menu, choose Edit From the Device Manager menu bar, choose Edit > Card From the Device Manager menu bar, choose Edit > Select All > Cards Then choose Edit > Card On the Device Manager toolbar, choose the Edit Selected button End The following sections provide a description of the two different card types in the Edit> Card dialog box and details about each field on the tabs Editing card information You can use the Card tab on the Card dialog box to view status for all I/O cards except the CPU card To open the Card tab: Step Action 1 Select the card 2 From the Device Manager menu bar, choose Edit > Card The Card dialog box opens with the Card tab displayed ("Card dialog box Card tab" (page 187)) NN Standard August 2007

187 Editing cards 187 Card dialog box Card tab End "Card tab fields" (page 187) describes the Card tab fields Card tab fields Field FrontType BackType FrontDescription BackDescription FrontAdminStatus FrontOperStatus FrontSerialNum BackSerialNum FrontHwVersion BackHwVersion Description Used to indicate card types in the Ethernet Routing Switch 8300 Front refers to the I/O portion of the module, the I/O card Model number of the module (for example, 8608GT) Indicates the administrative status of the card Indicates the operational status of this module Serial number of the I/O card Hardware version of the I/O card NN Standard August 2007

188 188 Configuring and graphing chassis information using Device Manager Field FrontPartNumber BackPartNumber FrontDateCode BackDateCode FrontDeviations BackDeviations PCMCIAType PCMCIADescr Description Part number of the I/O card Manufacturing date code for the I/O card Deviations Used to indicate the type of PCMCIA card currently installed in this CPU card, if any For non-cpu cards, this variable has no meaning and will always be set to none PCMCIA description Editing the boot file The Boot tab is used to specify the information the switch uses to reboot To edit these boot instructions using the JDM, perform the following procedure: Step Action 1 Select a CPU card 2 From the Device Manager menu bar, choose Edit > Card The Card dialog box opens with the Card tab displayed 3 Select the Boot tab The Boot tab opens NN Standard August 2007

189 Editing cards 189 Card dialog box Boot tab End The following table describes the fields on this tab Boot tab fields Field SwVersion LastBootConfigSource LastRuntimeImageSource LastRuntimeConfigSource PrimaryImageSource Description The currently loaded software version The boot configuration file used during the last boot sequence The runtime image most recently loaded The runtime configuration most recently loaded The primary image source file NN Standard August 2007

190 190 Configuring and graphing chassis information using Device Manager Field PrimaryConfigSource PrimaryBackupConfigSource SecondaryImageSource SecondaryConfigSource Description The primary configuration source file The primary backup configuration source file The secondary image source file The secondary configuration source file SecondaryBackupConfigSource The secondary backup configuration source file TertiaryImageSource TertiaryConfigSource TertiaryBackupConfigSource PrimaryLicenseSource SecondaryLicenceSource TertiaryLicenceSource EnableAutoBoot EnableFactoryDefaults EnableDebugMode EnableHwWatchDogTimer EnableRebootOnError EnableTelnetServer EnableRloginServer EnableFtpServer EnableTftpServer EnableSshServer The tertiary image source file The tertiary configuration source file The tertiary backup configuration source file The primary location of the switch license file A license file is required to enable certain software features The secondary location of the switch license file The tertiary location of the switch license file Enables the autoboot option When you apply power, the switch waits 5 seconds and then boots If this option is set to false, the boot process stops at the Boot Monitor Enables factory defaults option Enables debug mode option Enables hardware watchdog timer option Enables reboot on error option Enables Telnet server option Enables Rlogin server option Enables FTP server option Enables TFTP server option Enables SSH server option Displaying flash and PCMCIA statistics The Ethernet Routing Switch 8300 switch has two types of flash memory, the onboard flash memory, and an optional installed PCMCIA card You can view device flash and PCMCIA file information on the Device tab in the Card dialog box To open the Device tab: Step Action 1 Select a CPU card NN Standard August 2007

191 Editing cards From the Device Manager menu bar, choose Edit > Card The Card dialog box opens with the Card tab displayed 3 Click the Device tab The Device tab opens ("Card dialog box Device tab" (page 191)) Card dialog box Device tab End "Device tab fields" (page 191) describes the Device tab fields Device tab fields Field FlashBytesUsed FlashBytesFree FlashNumFiles PcmciaBytesUsed PcmciaBytesFree PcmciaNumFiles PcmciaAction Result Description Number of flash bytes used Number of flash bytes not used Number of files in flash memory Number of PCMCIA bytes used Number of PCMCIA bytes not used Number of PCMCIA files Option to reset the PCMCIA card Result of the last action taken on the device The values are none, in progress, success, or fail NN Standard August 2007

192 192 Configuring and graphing chassis information using Device Manager Displaying flash file information You can obtain information about the files in flash memory from the Flash Files tab To open the Flash Files tab: Step Action 1 Select a CPU card 2 From the Device Manager menu bar, choose Edit > Card The Card dialog box opens with the Card tab displayed 3 Click the Flash Files tab The Flash Files tab opens ("Card dialog box Flash Files tab" (page 192)) Card dialog box Flash Files tab End "Flash Files tab fields" (page 192) describes the Flash Files tab fields Flash Files tab fields Field Name Date Size Description Directory name of the flash file Creation or modification date of the flash file Size of the flash file NN Standard August 2007

193 Editing objects 193 Displaying PCMCIA file information You can use the PCMCIA Files tab to provide information about the files stored in the switch PCMCIA card It includes the same information as the Flash tab To open the PCMCIA Files tab: Step Action 1 Select a CPU card 2 From the Device Manager menu bar, choose Edit > Card The Card dialog box opens with the Card tab displayed 3 Click the PCMCIA Files tab The PCMCIA Files tab opens ("Card dialog box PCMCIA Files tab" (page 193)) Card dialog box PCMCIA Files tab End "PCMCIA Files tab fields" (page 193) describes the PCMCIA Files tab fields PCMCIA Files tab fields Field Name Date Size Description The directory name of the PCMCIA file The creation or modification date of the PCMCIA file The size of the PCMCIA file Editing objects The following sections describe each hardware and software object of the Ethernet Routing Switch 8300 switch NN Standard August 2007

194 194 Configuring and graphing chassis information using Device Manager For instructions about configuring PoE objects, refer to Nortel Ethernet routing Switch 8300 Configuration Power over Ethernet (NN ) Navigation "Editing management port" (page 194) "Editing management port route table" (page 196) "Editing serial ports" (page 197) "Editing fans" (page 199) "Editing power supplies" (page 200) "Editing FileSystem" (page 201) Editing management port The management port on the switch fabric/cpu module is a 10/100 Mb/s Ethernet port that can be used for an out-of-band management connection to the switch You can use the Mgmt Port dialog box to specify, among other things, management information for the device and to set device configuration To edit the Ethernet Routing Switch 8300 switch Management port: Step Action 1 Select the management port 2 Do one of the following: Double-click the Management port Right-click the Management port; click Edit From the Device Manager menu bar, choose Edit > MgmtPort From the Device Manager menu bar, choose Edit > Select All > MgmtPort Then choose Edit > Mgmt Port On the Device Manager toolbar, click the Edit Selected button End To open the Mgmt Port dialog box: Step Action 1 Select the management port object 2 From the Device Manager menu bar, choose Edit > Mgmt Port NN Standard August 2007

195 Editing objects 195 The Mgmt Port dialog box opens ("Mgmt Port dialog box" (page 195)) Mgmt Port dialog box End "Mgmt Port dialog box fields" (page 195) describes the Mgmt Port dialog box fields Mgmt Port dialog box fields Field Ifindex Descr AdminStatus OperStatus MgmtMacAddr Addr Mask AutoNegotiate AdminDuplex Description The slot and port number of the management port The description of the management port The administrative status of the device The operational status of the device The MAC address of the management device The IP address of the device The subnet IP mask The autonegotiate value Specifies the administrative duplex setting for this port NN Standard August 2007

196 196 Configuring and graphing chassis information using Device Manager Field OperDuplex AdminSpeed OperSpeed EnableBootp Description The operational duplex setting for this port Specifies the administrative speed setting for this port Indicates the operational duplex setting for this port Enables or disables BootP Editing management port route table You can use the Mgmt Port Route Table dialog box to view and specify network and gateway IP addresses used to remotely manage the device To open the Mgmt Port Route Table dialog box: Step Action 1 Select the management port object 2 From the Device Manager menu bar, choose Edit > Mgmt Port The Mgmt Port dialog box opens ("Mgmt Port dialog box" (page 195)) 3 On the Mgmt Port dialog box, click Route The Mgmt Port Route Table dialog box opens ("Mgmt Port Route Table, Insert CPU Route Table dialog box" (page 196)) Mgmt Port Route Table, Insert CPU Route Table dialog box End To add more Network and Gateway IP addresses: NN Standard August 2007

197 Editing objects 197 Step Action 1 On the Mgmt Port Route Table dialog box, click Insert The Mgmt Port Route Table, Insert CPU Route Table dialog box opens ("Mgmt Port Route Table, Insert CPU Route Table dialog box" (page 196)) 2 In the Mgmt Port Route Table, Insert CPU Route Table dialog box; enter new Network and Gateway IP addresses 3 In the Mgmt Port Route Table, Insert CPU Route Table dialog box, click Insert End "Mgmt Port Route Table, Insert CPU Route Table dialog box fields" (page 197) describes the Mgmt Port Route Table, Insert CPU Route Table dialog box fields Mgmt Port Route Table, Insert CPU Route Table dialog box fields Field Network Gateway Description The network IP address The gateway IP address of the device Editing serial ports The serial ports on the switch fabric/cpu module include the console port Use the Serial Port dialog box to specify serial port communication settings To edit the Ethernet Routing Switch 8300 switch serial ports: Step Action 1 Select the serial port 2 Do one of the following: Double-click the serial port Right-click the serial port and click Edit From the Device Manager menu bar, choose Edit > Serial Port From the Device Manager menu bar, choose Edit > Select All > Serial Ports Then choose Edit > Serial Port On the Device Manager toolbar, click the Edit Selected button NN Standard August 2007

198 198 Configuring and graphing chassis information using Device Manager End To open the Serial Port dialog box: Step Action 1 Select the serial port object 2 From the Device Manager menu bar, choose Edit > Serial Port The Serial Port dialog box opens ("Serial Port dialog box" (page 198)) Serial Port dialog box End "Serial Port dialog box fields" (page 198) describes the Serial Port dialog box fields Serial Port dialog box fields Field IfIndex Descr BaudRate DataBits Description The slot and port number of the serial port The description of the serial port Specifies the baud rate of this port Specifies the number of data bits, per byte of data, this port should send/receive NN Standard August 2007

199 Editing objects 199 Editing fans The Fan dialog box provides read-only information about the operating status of the switch fans To view the fan information: Step Action 1 Select the fan object 2 Do one of the following: Double-click the fan object Right-click the fan object and click Edit From the Device Manager menu bar, choose Edit > Fan From the Device Manager menu bar, choose Edit > Select All > Fan Then choose Edit > Fan On the Device Manager toolbar, click the Edit Selected button End To open the Fan dialog box: Step Action 1 Select the Fan object 2 From the Device Manager menu bar, choose Edit > Fan The Fan dialog box opens ("Fan dialog box" (page 199)) Fan dialog box End "Fan dialog box fields" (page 200) describes the Fan dialog box fields NN Standard August 2007

200 200 Configuring and graphing chassis information using Device Manager Fan dialog box fields Field Id OperStatus AmbientTemperature Description The fan ID Actual status of the Fan: unknown(1) - status cannot be determined up(2) - present and supplying power down(3) - present, but failure indicated Used to indicate the temperature of the air entering the fan Editing power supplies The Power Supply dialog box provides read-only information about the operating status of the switch power supplies The "p" indicator on the 8348TX-PWR module changes between red and orange to indicate that the associated port is searching for a PoE device: orange indicates searching; red indicates no PoE power To view the power supply information: Step Action 1 Select the power supply object 2 Do one of the following: Double-click the power supply object Right-click the power supply object and click Edit From the Device Manager menu bar, choose Edit > Power Supply From the Device Manager menu bar, choose Edit > Select All > Power Supplies Then choose Edit > Power Supply On the Device Manager toolbar, click the Edit Selected button End To open the PowerSupply dialog box: Step Action 1 Select the power supply object NN Standard August 2007

201 Editing objects On the Device Manager menu bar, choose Edit > Power Supply The PowerSupply dialog box opens ("PowerSupply dialog box" (page 201)) PowerSupply dialog box End "PowerSupply Detail tab fields" (page 201) describes the PowerSupply Detail tab fields PowerSupply Detail tab fields Field Type Description SerialNumber HardwareRevision PartNumber PowerSupplyOperStatus Description Describes the type of power used AC or DC Provides a description of the power supply Defines the serial number of the power supply Displays the hardware revision number Displays the part number of the power supply Displays the status of the power supply, on (up) or off (down) Editing FileSystem The FileSystem dialog box allows you to copy files and provides information about flash and PCMCIA files File copying and file information are all related to files on the switch CPU module The following sections provide a description of the tabs in the Edit > File System dialog box and details about each field on the tabs NN Standard August 2007

202 202 Configuring and graphing chassis information using Device Manager Copying a PCMCIA or flash file To copy files between the flash and the PCMCIA: From the Device Manager menu bar, choose Edit > File System The FileSystem dialog box opens with the Copy File tab active ("FileSystem dialog box Copy File tab" (page 202)) FileSystem dialog box Copy File tab "Copy File tab fields" (page 202) describes the Copy File tab fields Copy File tab fields Field Source Destination Action Result Description The source file to copy from flash memory, PCMCIA, or a TFTP server Configuration files can also be copied from NVRAM or a trace file The device (and file name if applicable) to which the source file is to be copied The destination can be flash, PCMCIA or the NVRAM Trace files are not a valid destination Select start to begin the copy process or none to cancel the copy process Displays the result of the copy process: none inprogress success fail invalidsource invaliddestination NN Standard August 2007

203 Editing objects 203 Field Description outofmemory outofspace filenotfound Displaying flash and PCMCIA statistics Use the Device Info to display flash and PCMCIA file statistics To open the Device Info tab: Step Action 1 From the Device Manager menu bar, choose Edit > File System The FileSystem dialog box opens with the Copy File tab active 2 Click the Device Info tab The Device Info tab opens ("FileSystem dialog box Device Info tab" (page 203)) End FileSystem dialog box Device Info tab "Device Info tab fields" (page 203) describes the Device Info tab fields Device Info tab fields Field Description Slot This is the slot number of the CPU module FlashBytesUsedThe number of Flash bytes used FlashBytesFree The number of Flash bytes free FlashNumFiles The number of Flash files PcmciaBytesUsedThe number of PCMCIA bytes used PcmciaBytesFreeThe number of PCMCIA bytes free PcmciaNumFilesThe number of PCMCIA files NN Standard August 2007

204 204 Configuring and graphing chassis information using Device Manager Field PcmciaAction Result Description The type of action None or reset PCMCIA The results of the last action taken on the device The valid values are none, in progress, success, or fail Displaying flash file information Use the Flash Files tab to display Flash file information To open the Flash Files tab: Step Action 1 From the Device Manager menu bar, choose Edit > File System The FileSystem dialog box opens with the Copy File tab active 2 Click the Flash Files tab The Flash Files tab opens ("FileSystem dialog box Flash Files tab" (page 204)) End FileSystem dialog box Flash Files tab "Flash Files tab fields" (page 204) describes the Flash Files tab fields Flash Files tab fields Field Description Slot The slot number of the CPU module Name The name of the Flash file NN Standard August 2007

205 Editing objects 205 Field Date Size Description The date and time the Flash file was created or modified The size of the Flash file in bytes Displaying PCMCIA file information Use the PCMCIA Files tab to display PCMCIA file information To open the PCMCIA Files tab: Step Action 1 From the Device Manager menu bar, choose Edit > File System The FileSystem dialog box opens with the Copy File tab active 2 Click the PCMCIA Files tab The PCMCIA Files tab opens ("FileSystem dialog box PCMCIA Files tab" (page 205)) End FileSystem dialog box PCMCIA Files tab "PCMCIA Files tab fields" (page 205) describes the Flash Files tab fields PCMCIA Files tab fields Field Description Slot The slot number of the CPU module Name The name of the PCMCIA file Date The date and time the PCMCIA file was created or modified Size The size of the PCMCIA file in bytes NN Standard August 2007

206 206 Configuring and graphing chassis information using Device Manager Graphing chassis statistics The following sections discuss the different chassis statistics tabs in the Graph Chassis dialog box with descriptions of the statistics fields All graphing chassis tables have the following buttons: Line Chart, Area Chart, Bar Chart, Pie Chart, Export Data, Print table, Clear Counter, Close, and Help To reset the statistics counters, use the "Clear Counter" button When you click this button, all Cumulative, Average, Minimum, Maximum, and LastVal columns are reset to zero and automatically begin to recalculate statistical data The Clear Counter function in Device Manager does not affect the AbsoluteValue counter in the switch Instead, the Clear Counter function clears all cached data in Device Manager (except AbsoluteValue) To reset AbsoluteValue(s), use the Reset Counter function (Edit > Chassis > System) To graph chassis statistics: â Select the chassis On the shortcut menu, choose Graph From the Device Manager menu bar, choose Graph > Chassis On the Device Manager toolbar, choose the Graph Selected button Navigation "Graphing system statistics" (page 206) "Graphing SNMP statistics" (page 207) "Graphing IP statistics" (page 210) "Card dialog box PCMCIA Files tab" (page 193) "Graphing ICMP Out statistics" (page 213) Graphing system statistics You can check system performance with the Performance tab To open the Performance tab: Step Action 1 From the Device Manager menu bar, choose Edit > Chassis The chassis dialog box opens with the System tab displayed 2 Click on the Performance tab The Performance tab opens ("Chassis dialog box Performance tab" (page 207)) NN Standard August 2007

207 Graphing chassis statistics 207 End Chassis dialog box Performance tab "Performance tab fields" (page 207) describes the Performance tab fields Performance tab fields Field DramUsed DramFree CpuUtil SwitchFabricUtil OtherSwitchFabricUtil Description The percentage of DRAM space used The amount of DRAM free in kilobytes Percentage of CPU utilization Percentage of switch fabric utilization This field will display 0% when the Ethernet Routing Switch 8100 module is installed Percentage of other switch fabric utilization This field will display 0% when the Ethernet Routing Switch 8100 module is installed Graphing SNMP statistics You can graph statistics for all SNMP packets that enter the chassis from different interfaces To graph SNMP statistics: Step Action 1 From the Device Manager Menu bar, choose Graph > Chassis The Graph Chassis dialog box opens with the SNMP tab displayed ("Graph Chassis dialog box SNMP tab" (page 208)) NN Standard August 2007

208 208 Configuring and graphing chassis information using Device Manager End Graph Chassis dialog box SNMP tab "SNMP tab fields" (page 208) describes the SNMP tab fields SNMP tab fields Field InPkts OutPkts InTotalReqVars InTotalSetVars InGetRequests Description The total number of messages delivered to the SNMP entity from the transport service The total number of SNMP messages passed from the SNMP protocol entity to the transport service The total number of MIB objects retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs The total number of MIB objects altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs The total number of SNMP Get-Request PDUs that have been accepted and processed by the SNMP protocol entity NN Standard August 2007

209 Graphing chassis statistics 209 Field InGetNexts InSetRequests InGetResponses OutTraps OutTooBigs OutNoSuchNames OutBadValues OutGenErrs InBadVersions Description The total number of SNMP Get-Next PDUs accepted and processed by the SNMP protocol entity The total number of SNMP Set-Request PDUs accepted and processed by the SNMP protocol entity The total number of SNMP Get-Response PDUs accepted and processed by the SNMP protocol entity The total number of SNMP Trap PDUs generated by the SNMP protocol entity The total number of SNMP PDUs generated by the SNMP protocol entity for which the value of the error-status field is toobig The total number of SNMP PDUs generated by the SNMP protocol entity for which the value of the error-status field is nosuchname The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is badvalue The total number of SNMP PDUs generated by the SNMP protocol entity for which the value of the error-status field is generr The total number of SNMP messages delivered to the SNMP protocol entity for an unsupported SNMP version InBadCommunityNames The total number of SNMP messages delivered to the SNMP protocol entity that used an SNMP community name not known to said entity InBadCommunityUses InASNParseErrs InTooBigs InNoSuchNames InBadValues The total number of SNMP messages delivered to the SNMP protocol entity that represented an SNMP operation not allowed by the SNMP community named in the message The total number of ASN1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP messages The total number of SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is toobig The total number of SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is nosuchname The total number of SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is badvalue NN Standard August 2007

210 210 Configuring and graphing chassis information using Device Manager Field InReadOnlys InGenErrs Description The total number of SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is readonly It is a protocol error to generate an SNMP PDU containing the value "readonly" in the error-status field This object is provided to detect incorrect implementations of the SNMP The total number of SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is generr Graphing IP statistics You can graph statistics for all IP packets that enter the chassis from different interfaces To graph IP statistics: Step Action 1 From the Device Manager Menu bar, choose Graph > Chassis The Graph Chassis dialog box opens with the SNMP tab displayed 2 Click the IP tab The IP tab opens ("GraphChassis dialog box IP tab" (page 210)) End Graph Chassis dialog box IP tab NN Standard August 2007

211 Graphing chassis statistics 211 "IP tab fields" (page 211) describes the IP tab fields IP tab fields Field InReceives InHdrErrors InAddrErrors Description The total number of input datagrams received from interfaces, including those received in error The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options The number of input datagrams discarded because the IP address in their IP header s destination field was not a valid address to be received at this entity This count includes invalid addresses (for example, 0000) and addresses of unsupported Classes (for example, Class E) For entities that are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address ForwDatagrams The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination In entities that do not act as IP Gateways, this counter will include only those packets that were Source-Routed by way of this entity and had successful Source-Route option processing InUnknownProtosThe number of locally addressed datagrams received successfully but discarded because of an unknown or unsupported protocol InDiscards InDelivers OutRequests OutDiscards The number of input IP datagrams for which no problems were encountered to prevent their continued processing but that were discarded (for example, for lack of buffer space) Note that this counter does not include any datagrams discarded while awaiting reassembly The total number of input datagrams successfully delivered to IP user-protocols (including ICMP) The total number of IP datagrams that local IP user-protocols (including ICMP) supplied to IP in requests for transmission Note that this counter does not include any datagrams counted in ipforwdatagrams The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but that were discarded (for example, for lack of buffer space) Note that this counter would include datagrams counted in ipforwdatagrams if any such packets met this (discretionary) discard criterion NN Standard August 2007

212 212 Configuring and graphing chassis information using Device Manager Field OutNoRoutes FragOKs FragFails FragCreates ReasmReqds ReasmOKs ReasmFails Description The number of IP datagrams discarded because no route could be found to transmit them to their destination Note that this counter includes any packets counted in ipforwdatagrams that meet this no-route criterion This counter includes any datagrams a host cannot route because all of its default gateways are down The number of IP datagrams that have been successfully fragmented at this entity The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, for example, because their Don t Fragment flag was set The number of IP datagram fragments that have been generated as a result of fragmentation at this entity The number of IP fragments received that needed to be reassembled at this entity The number of IP datagrams successfully reassembled The number of failures detected by the IP reassembly algorithm (for whatever reason: timed out, errors, and so on) Note that this number is not necessarily a count of discarded IP fragments because some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received Graphing ICMP In statistics You can graph statistics for all ICMP packets received into the chassis from different interfaces To graph ICMP In statistics: Step Action 1 From the Device Manager menu bar, choose Graph > Chassis The Graph Chassis dialog box opens with the SNMP In tab displayed 2 Click the ICMP In tab The ICMP In tab opens ("GraphChassis dialog box ICMP In tab" (page 213)) End NN Standard August 2007

213 Graphing chassis statistics 213 Graph Chassis dialog box ICMP In tab "ICMP In tab fields" (page 213) describes the ICMP In tab fields ICMP In tab fields Field Description SrcQuenchs The number of ICMP Source Quench messages received Redirects The number of ICMP Redirect messages received Echos The number of ICMP Echo (request) messages received EchoReps The number of ICMP Echo Reply messages received Timestamps The number of ICMP Timestamp (request) messages received TimestampRepsThe number of ICMP Timestamp Reply messages received AddrMasks The number of ICMP Address Mask Request messages received AddrMaskReps The number of ICMP Address Mask Reply messages received ParmProbs DestUnreachs TimeExcds The number of ICMP Parameter Problem messages received The number of ICMP Destination Unreachable messages received The number of ICMP Time Exceeded messages received Graphing ICMP Out statistics You can graph statistics for all ICMP messages sent To graph ICMP Out statistics: Step Action 1 From the Device Manager menu bar, choose Graph > Chassis NN Standard August 2007

214 214 Configuring and graphing chassis information using Device Manager The Graph Chassis dialog box opens with the SNMP Out tab displayed 2 Click the ICMP Out tab The ICMP Out tab opens ("GraphChassis ICMP Out tab" (page 214)) End Graph Chassis ICMP Out tab "ICMP Out tab fields" (page 214) describes the ICMP Out tab fields ICMP Out tab fields Field SrcQuenchs Redirects Echos EchoReps Timestamps Description The number of ICMP Source Quench messages sent The number of ICMP Redirect messages received For a host, this object will always be zero, because hosts do not send redirects The number of ICMP Echo (request) messages sent The number of ICMP Echo Reply messages sent The number of ICMP Timestamp (request) messages sent TimestampRepsThe number of ICMP Timestamp Reply messages sent AddrMasks The number of ICMP Address Mask Request messages sent AddrMaskReps The number of ICMP Address Mask Reply messages sent ParmProbs DestUnreachs TimeExcds The number of ICMP Parameter Problem messages sent The number of ICMP Destination Unreachable messages sent The number of ICMP Time Exceeded messages sent NN Standard August 2007