Guest

Cisco Catalyst 6500 Series Switches

Catalyst 6000 Family Network Analysis Module Installation and Configuration Note 2.2

Table Of Contents

Catalyst 6500 Series Network Analysis Module Installation and Configuration Note

Contents

Before You Begin

Overview

Understanding How the NAM Works

Managing the NAM

New NAM Features

Front Panel Description

STATUS LED

SHUTDOWN Button

Specifications

Safety Overview

Software Requirements

Hardware Requirements

Required Tools

Installing and Removing the NAM

Slot Assignments

Removing a Module

Installing a Module

Verifying the Installation

Cisco IOS Software

Catalyst OS Software

Configuring the NAM

Cisco IOS Software

Initial Configuration

Configuring VLANs

Using NetFlow Data Export as a Traffic Source

Using SPAN as a Traffic Source

Catalyst OS Software

Initial Configuration

Configuring VLANs

Using NetFlow Data Export as a Traffic Source

Using SPAN as a Traffic Source

Configuring the SNMP Agent

Operating-System-Independent Configuration

Configuring Automatic RMON Collections

Configuring the HTTP or HTTP Secure Server

Configuring the HTTP Server

Installing a Strong Crypto Patch

Generating Certificates

Installing Certificates

Using a TACACS+ Server

Administering the NAM

Cisco IOS Software

Logging in to the NAM

Changing the NAM CLI Passwords

Resetting the NAM

Upgrading the NAM Software

Configuring mini-RMON

Catalyst OS Software

Logging in to the NAM

Changing the NAM CLI Passwords

Resetting the NAM

Upgrading the NAM Software

Configuring mini-RMON

Operating-System-Independent NAM Administration

Adding NAM Patch Software

Additional NAM Software Administrative Commands

Cisco IOS Commands

EXEC Commands

Configuration Commands

Unsupported Supervisor Engine CLI Commands

Troubleshooting the NAM

Web Username and Password Guidelines

Supported MIB Objects

Standards Compliance Specifications

FCC Class B Compliance

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Catalyst 6500 Series Network Analysis Module Installation and Configuration Note


WS-SVC-NAM-1
WS-SVC-NAM-2

This publication describes how to install the Catalyst 6500 series and how to configure the NAM using the Catalyst command-line interface (CLI), or the NAM Traffic Analyzer application, or both. See the "Related Documentation" section for more information about software configuration for the switch.

This publication does not describe the WS-X6380-NAM. For additional information about the WS-X6380-NAM, refer to the Catalyst 6000 Family Network Analysis Module Installation and Configuration Note, Software Release 2.1.


Note For translations of the warnings in this publication, see the "Safety Overview" section and refer to the Regulatory Compliance and Safety Information for the Catalyst 6500 series switches.



Note Third-party software used under license accompanies the Network Analysis Module software, Release 2.2(1a). Notices that may apply to the license and to the use of such third-party software are listed in the Release Notes for Catalyst 6500 Family Network Analysis Module, Software Release 2.2(1a).


Contents

This publication consists of these sections:

Before You Begin

Overview

Safety Overview

Software Requirements

Hardware Requirements

Required Tools

Installing and Removing the NAM

Configuring the NAM

Administering the NAM

Troubleshooting the NAM

Supported MIB Objects

FCC Class B Compliance

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

Before You Begin

To help you get started using the NAM, refer to this roadmap:

Overview

This section describes the Catalyst 6500 series and Catalyst 6000 family NAM, how it operates, and how to manage it, and includes these sections:

Understanding How the NAM Works

Managing the NAM

New NAM Features

Front Panel Description

Specifications

Understanding How the NAM Works

The NAM monitors and analyzes network traffic for the Catalyst 6500 series and Catalyst 6000 family switches using remote monitoring (RMON), RMON extensions for switched networks (SMON), and other management information bases (MIBs). The NAM supports the following RMON groups:

RMON groups defined in RFC 1757

RMON2 groups defined in RFC 2021

The NAM also can monitor individual Ethernet VLANs, which allows it to serve as an extension to the basic RMON support provided by the Catalyst 6500 series and Catalyst 6000 family supervisor engine.

You can use any other IETF-compliant RMON application to access link, host, protocol, and response-time statistics for capacity planning, departmental accounting, and real-time application protocol monitoring. You also can use filters and capture buffers to troubleshoot the network.

The NAM can analyze Ethernet VLAN traffic from one or both of the following sources:

Ethernet, Fast Ethernet, Gigabit Ethernet, trunk port, or Fast EtherChannel SPAN or RSPAN source port

For more information about SPAN and RSPAN, refer to the "Configuring SPAN and RSPAN" chapter in the Catalyst 6000 Family Software Configuration Guide.

Netflow Data Export (NDE)

For more information about NDE, refer to the Catalyst 6000 Family Software Configuration Guide.

Managing the NAM

The NAM is managed and controlled from the embedded web-based NAM Traffic Analyzer application (directing a web browser to the NAM) or a Simple Network Management Protocol (SNMP) management application, such as those bundled with CiscoWorks2000, or both.

The NAM Traffic Analyzer application provides access to the management features and monitoring features for NAM data and voice traffic through a web browser. To use the NAM Traffic Analyzer application, you first need to do some basic configuration tasks on the NAM using the CLI. You then can start the NAM Traffic Analyzer application with a single command.

With NAM Traffic Analyzer, you can do the following tasks:

Configure SPAN resources

Configure collections

Monitor statistics

Capture and decode packets

Set and view alarms

For added security, you can use the NAM Traffic Analyzer application to configure the NAM to use a remote TACACS+ server. A TACACS+ server can be used for authentication and authorization for your web-based users. You also can use a local database on the NAM for security.

You also can manage the NAM using an SNMP management application such as the Cisco NetScout nGenius Real-Time Monitor (RTM). For more information about using RTM, refer to the CiscoWorks2000 documentation or refer to the following URL:

http://www.Cisco.com/univercd/cc/td/doc/product/lan/cat6000/fam_mod/rel2_1_2/ol_2428.htm

To use RMON and SNMP agent support, you configure the NAM using the CLI.

If you have a NAM that is already configured and running in the switch, and you are familiar with the NAM, you can begin using the NAM Traffic Analyzer application by entering the ip http server enable CLI command, and then starting NAM Traffic Analyzer in your browser.

Refer to the User Guide for the Catalyst 6500 Network Analysis Module Traffic Analyzer for more information about using the NAM Traffic Analyzer application.

New NAM Features

These are the new features for the NAM-1 and NAM-2 platforms in software release 2.2:

Support for the new, high-performance, NAM-1 and NAM-2 hardware platforms with interfaces to the crossbar-based architecture in Catalyst 6500 series switches and interfaces to the bus-based architecture.

Automatic detection of up to 100 unknown protocols to identify applications that are consuming bandwidth.

The capability to isolate traffic sources by identifying hosts running particular applications.

Correlation of hosts and applications by DiffServ Code Points (DSCPs) to better identify Quality of Service (QoS) violations.

GUI enhancements in the NAM Traffic Analyzer application. For example, changes were made to the Setup->SPAN Sources menu.

The hard disk can be formatted and reinstalled because the maintenance image is now located in the compact flash, and the application image is located on the hard disk.

Secure shell (SSH) support to provide secure access to NAM through CLI.

CLI automatic completion for ease of use.

Mini-RMON can be used through the NAM without a separate license.


Note The NAM software release 2.2 is not supported on WS-X6380-NAM hardware platform.


Front Panel Description

The NAM front panel (see Figure 1) includes a STATUS LED and SHUTDOWN button.

Figure 1 Network Analysis Module

STATUS LED

The STATUS LED indicates the operating states of the NAM. Table 1 describes the LED operation.

Table 1 STATUS LED Description 

Color
Description

Green

All diagnostic tests pass. The NAM is operational.

Red

A diagnostic other than an individual port test failed.

Orange

Indicates one of three conditions:

The NAM is running through its boot and self-test diagnostic sequence.

The NAM is disabled.

The NAM is in the shutdown state.

Off

The NAM power is off.


SHUTDOWN Button


Caution Do not remove the NAM from the switch until the NAM has shut down completely and the STATUS LED is orange. You can damage the NAM if you remove it from the switch before it completely shuts down.

To avoid corrupting the NAM hard disk, you must correctly shut down the NAM before you remove it from the chassis or disconnect the power. This shutdown procedure is normally initiated by commands entered at the supervisor engine CLI prompt or the NAM CLI prompt.

If the NAM fails to respond to these commands properly, you must use the SHUTDOWN button on the front panel to initiate the shutdown procedure. To push the button, use a small pointed object (such as a paper clip).

The shutdown procedure may require several minutes. The STATUS LED turns off when the NAM shuts down.

Specifications

Table 2 describes the specifications for the NAM.

Table 2 WS-SVC-NAM-1 and WS-SVC-NAM-2 Specifications 

Specification
Description

Dimensions (H x W x D)

1.2 x 14.4 x 16 in. (3.0 x 35.6 x 40.6 cm)

Weight

Minimum: 3 lb (1.36 kg)

Maximum: 5 lb (2.27 kg)

Environmental conditions:

Operating temperature

Nonoperating temperature

Humidity

Humidity - Ambient
(Noncondensing) Nonoperating and Storage

Altitude

32 to 104×F (0 to 40×C)

-40 to 158×F (-40 to 70×C)

10 to 90%, noncondensing

5 to 95%

Sea level to 10,000 ft (3050 m)


Safety Overview

Safety warnings appear throughout this document in procedures that may harm you if performed incorrectly.

For additional safety information, refer to documents listed in the "Related Documentation" section.


Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device.



Warning Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information (Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit toestel is ingesloten.



Warning Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät laitteen mukana olevasta Regulatory Compliance and Safety Information -kirjasesta (määräysten noudattaminen ja tietoa turvallisuudesta).



Warning Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez le document Regulatory Compliance and Safety Information (Conformité aux règlements et consignes de sécurité) qui accompagne cet appareil.



Warning Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information (Informationen zu behördlichen Vorschriften und Sicherheit), das zusammen mit diesem Gerät geliefert wurde.



Warning Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento Regulatory Compliance and Safety Information (Conformità alle norme e informazioni sulla sicurezza) che accompagna questo dispositivo.



Warning Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av deadvarslene som finnes i denne publikasjonen, kan du se i dokumentet Regulatory Compliance and Safety Information (Overholdelse av forskrifter og sikkerhetsinformasjon) som ble levert med denne enheten.



Warning Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte o documento Regulatory Compliance and Safety Information (Informação de Segurança e Disposições Reguladoras) que acompanha este dispositivo.



Warning ¡Advertencia! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar el documento titulado Regulatory Compliance and Safety Information (Información sobre seguridad y conformidad con las disposiciones reglamentarias) que se acompaña con este dispositivo.



Warning Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du varamedveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Se förklaringar av de varningar som förkommer i denna publikation i dokumentet Regulatory Compliance and Safety Information (Efterrättelse av föreskrifter och säkerhetsinformation), vilket medföljer denna anordning.



Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment.


Software Requirements

Table 3 lists the NAM software versions supported by Catalyst OS and Cisco IOS software.

Table 3 NAM Software Compatibility 

Application Image
Maintenance Image
Catalyst OS Software
Cisco IOS Software
Supported Browsers

2.2(1a)

1.1(1)m

7.3(1) or later releases with Supervisor Engine 1A or 2

12.1(13)E or later releases with a Supervisor Engine 2 with an MSFC2

Netscape 4.7 on Windows 2000 and Solaris

Internet Explorer 5.0 and higher on Windows 2000


Hardware Requirements

Table 4 lists the NAM hardware versions supported by Catalyst OS and Cisco IOS software.

Table 4 NAM Hardware Compatibility

Catalyst OS Software
Cisco IOS Software

Supervisor Engine 1A or 2

Supervisor Engine 2 with an MSFC2


Required Tools


Note Before installing the NAM, you must install the Catalyst 6500 series and Catalyst 6000 family switch chassis and at least one supervisor engine. For information on installing the switch chassis, refer to the Catalyst 6000 Family Installation Guide.


These tools are required to install the NAM in the Catalyst 6500 series and Catalyst 6000 family switches:

Flat-blade screwdriver

Phillips-head screwdriver

Wrist strap or other grounding device

Antistatic mat or antistatic foam

Whenever you handle the NAM, always use a wrist strap or other grounding device to prevent electrostatic discharge (ESD).

Installing and Removing the NAM


Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.


All the Catalyst 6500 series and Catalyst 6000 family switches support hot swapping, which allows you to install, remove, replace, and rearrange modules without turning off the system power. For more information on removing the NAM from a switch, see the "Removing a Module" section.


Caution We recommend that you shut down the NAM before you remove the module.

When the system detects that a module has been installed or removed, the system automatically runs diagnostic and discovery routines, acknowledges the presence or absence of the module, and resumes system operation.

To install and use the NAM, you need to complete the following actions:

Perform the initial installation by placing the NAM in a switch.

At the switch CLI, session to the NAM CLI and provide a basic configuration.

Send a data source to the NAM (Netflow data, switch port analyzer [SPAN] ports, VLANs, or EtherChannels).

Configure collection types that you want to monitor (RMON, voice, application response time, and other collection monitoring as required for your network).

Configure alarms.

View monitored statistics, alarms, and use packet capture or decode functionality.

This section describes how to install and verify the operation of the NAM in the Catalyst 6000 family switches and contains the following sections:

Slot Assignments

Removing a Module

Installing a Module

Verifying the Installation

Slot Assignments

The Catalyst 6006 and 6506 switch chassis have six slots, the Catalyst 6009 and 6509 switch chassis have nine slots, and the Catalyst 6513 switch chassis has thirteen slots. The module can occupy any slot in the Catalyst 6500 series or 6000 family chassis.


Note The Catalyst 6509-NEB switch has vertical slots numbered 1 to 9 from right to left. Install the modules with the component side facing to the right.


Slot 1 is reserved for the supervisor engine.

Slot 2 can contain an additional redundant supervisor engine in case the supervisor engine in slot 1 fails.

If a redundant supervisor engine is not required, slots 2 through 6 on the 6-slot chassis, (slots 2 through 9 on the 9-slot chassis and slots 2 through 13 on the 13-slot chassis) are available for switching modules, such as the NAM.

Install switching-module filler plates, which are blank switching-module carriers, in the empty slots to maintain consistent airflow through the switch chassis.

Removing a Module

This section describes how to remove an existing module from a chassis slot.


Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.



Warning Before you install, operate, or service the system, read the Site Preparation and Safety Guide. This guide contains important safety information you should know before working with the system.



Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.


To remove a supervisor engine or module from the chassis, perform these steps:


Step 1 Disconnect any network interface cables attached to the supervisor engine or module.


Note The NAM does not have any interface cable connections.


Step 2 Verify that the captive installation screws on all of the modules in the chassis are tight.

This action ensures that the space created by the removed module is maintained.


Note If the captive installation screws are loose, the electromagnetic interference (EMI) gaskets on the installed modules will push the modules toward the open slot, reducing the opening size and making it difficult to install the replacement module.


Step 3 Loosen the two captive installation screws on the supervisor engine or module.

Step 4 Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of the following sets of steps:

Horizontal slots

a. Place your thumbs on the left and right ejector levers, and simultaneously rotate the levers outward to unseat the module from the backplane connector.

b. Grasp the front edge of the module and slide the module part of the way out of the slot. Place your other hand under the module to support the weight of the module. Do not touch the module circuitry.

Vertical slots

a. Place your thumbs on the ejector levers located at the top and bottom of the module, and simultaneously rotate the levers outward to unseat the module from the backplane connector.

b. Grasp the edges of the module, and slide the module straight out of the slot. Do not touch the module circuitry.

Step 5 Place the module on an antistatic mat or antistatic foam, or immediately reinstall it in another slot.

Step 6 If the slot is to remain empty, install a module filler plate to keep dust out of the chassis and to maintain proper airflow through the chassis.



Warning Blank faceplates (filler panels) serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards and faceplates are in place.


Installing a Module

This section describes how to install modules in the Catalyst 6500 series and Catalyst 6000 family switches.


Caution To prevent ESD damage, handle modules by the carrier edges only.


Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.



Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.



Warning Before you install, operate, or service the system, read the Site Preparation and Safety Guide. This guide contains important safety information you should know before working with the system.


To install a supervisor engine or module in the chassis, perform these steps:


Step 1 Choose a slot for the supervisor engine or module.

Step 2 Verify that there is enough clearance to accommodate any interface equipment that you will connect directly to the supervisor engine or module ports. If possible, place modules between empty slots that contain only module filler plates.

Step 3 Verify that the captive installation screws are tightened on all modules installed in the chassis.

This action ensures that the EMI gaskets on all modules are fully compressed in order to maximize the opening space for the new module or the replacement module.


Note If the captive installation screws are loose, the EMI gaskets on the installed modules will push adjacent modules toward the open slot, reducing the opening size and making it difficult to install the replacement module.


Step 4 Remove the module filler plate by removing the two Phillips pan-head screws from the filler plate.

To remove a module, refer to "Removing a Module" section.

Step 5 Fully open both ejector levers on the new or replacement module. (See Figure 2.)

Figure 2 Positioning the Module in a Horizontal Slot Chassis

Step 6 Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of these sets of steps:

Horizontal slots

a. Position the supervisor engine or module in the slot. (See Figure 2.) Make sure that you align the sides of the module carrier with the slot guides on each side of the slot.

b. Carefully slide the supervisor engine or module into the slot until the EMI gasket along the top edge of the module makes contact with the module in the slot above it and both ejector levers have closed to approximately 45 degrees in relation to the module faceplate. (See Figure 3.)

Figure 3 Clearing the EMI Gasket in a Horizontal Slot Chassis

c. Using the thumb and forefinger of each hand, grasp the two ejector levers and press down to create a small (0.040 inch [1 mm]) gap between the module's EMI gasket and the module above it. (See Figure 3.)


Caution Do not press down too hard on the levers because they can bend and be damaged.

d. While pressing down, simultaneously close the left and right ejector levers to fully seat the supervisor engine or module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate. (See Figure 4.)

Figure 4 Ejector Lever Closure in a Horizontal Slot Chassis


Note Failure to fully seat the module in the backplane connector can result in error messages.


e. Tighten the two captive installation screws on the supervisor engine or module.


Note Make sure that the ejector levers are fully closed before tightening the captive installation screws.


Vertical slots

a. Position the supervisor engine or switching module in the slot. (See Figure 5.) Make sure that you align the sides of the switching module carrier with the slot guides on the top and bottom of the slot.

Figure 5 Positioning the Module in a Vertical Slot Chassis

b. Carefully slide the supervisor engine or module into the slot until the EMI gasket along the right edge of the module makes contact with the module in the slot adjacent to it and both ejector levers have closed to approximately 45 degrees with respect to the module faceplate. (See Figure 6.)

c. Using the thumb and forefinger of each hand, grasp the two ejector levers and exert a slight pressure to the left, moving the module approximately 0.040 inches (1 mm) to create a small gap between the module's EMI gasket and the module adjacent to it. (See Figure 6.)

Figure 6 Clearing the EMI Gasket in a Vertical Slot Chassis


Caution Do not exert too much pressure on the ejector levers. They will bend and be damaged.

d. While pressing on the ejector levers, simultaneously close them to fully seat the supervisor engine or module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate. (See Figure 7.)

Figure 7 Ejector Lever Closure in a Vertical Slot Chassis

e. Tighten the two captive installation screws on the module.


Note Make sure that the ejector levers are fully closed before tightening the captive installation screws.



Verifying the Installation

This section describes how to verify the NAM installation.

Cisco IOS Software

To verify that the system acknowledges the new module and has brought it online, enter the show module [mod-num | all] command.

This example shows the output of the show module command:

Router#  show module 
Mod Slot Ports Module-Type               Model               Sub Status
--- ---- ----- ------------------------- ------------------- --- --------
1   1    2     1000BaseX Supervisor      WS-X6K-S2U-MSFC2    yes ok
15  1    1     Multilayer Switch Feature WS-F6K-MSFC2        no  ok
2   2    3     Network Analysis Module   WS-SVC-NAM-1        no  ok
Router#  

When the NAM initially boots, by default it runs a partial memory test. To perform a full memory test, enter the hw-module module module_number reset device:partition mem-test-full command. This command is specific to Cisco IOS software and is not available in Catalyst OS software.

A full memory test takes more time to complete than a partial memory test depending on the memory size. Table 5 lists the memory test time and approximate boot time for a long memory test.

Table 5 Module Boot Time

Module
Boot Time

WS-SVC-NAM-1

3 minutes

WS-SVC-NAM-2

6 minutes


You also can use the hw-module module module_number mem-test-full command in a Cisco IOS system. This example shows how to do a full memory test for module 5:

Router(config)#  hw-module module 5 mem-test-full

Catalyst OS Software

To verify that the switch acknowledges the new NAM and has brought it online, enter the show module or show port [mod/port] command.

This example shows the output of the show module command:

Console> (enable) show module
Mod Slot Ports Module-Type               Model               Sub Status
--- ---- ----- ------------------------- ------------------- --- --------
1   1    2     1000BaseX Supervisor      WS-X6K-SUP1A-2GE    yes ok
15  1    1     Multilayer Switch Feature WS-F6K-MSFC         no  ok
3   3    2     Network Analysis Module   WS-SVC-NAM-1        no  ok
5   5    48    10/100BaseTX Ethernet     WS-X6248-RJ-45      no  ok
.
.
.
Console> (enable) 

When the NAM initially boots, by default it runs a partial memory test. For Catalyst OS software, you can perform a full memory test when you enter the set boot device bootseq mod# mem-test-full command. This command is specific to Catalyst OS software and is not available in Cisco IOS software. This example shows how to do a partial memory test:

Console (enable) set boot device cf:1 4 mem-test-full 
Device BOOT variable = cf:1 
Memory-test set to FULL 
Warning:Device list is not verified but still set in the boot string. 

Console> (enable) show boot device 4 
Device BOOT variable = cf:1 
Memory-test set to FULL 

When you next reset the NAM, the full memory test runs. A full memory test takes more time to complete than a partial memory test. Table 5 shows the time for memory tests.

This example shows how to reset the partial memory test:

Console> (enable) set boot device cf:1 4 
Device BOOT variable = cf:1 
Memory-test set to PARTIAL 
Warning:Device list is not verified but still set in the boot string. 
Console> (enable) 
Console> (enable) show boot device 4 
Device BOOT variable = cf:1 
Memory-test set to PARTIAL 

Configuring the NAM

How you configure the NAM on your switch depends on whether you are using Cisco IOS software or the Catalyst OS software. Several NAM configuration tasks are common to both switch operating systems.

The following sections describe how to configure the NAM from the CLI for each switch operating system:

Cisco IOS Software

Catalyst OS Software

When you have completed configuring the software-dependent attributes for the NAM, you can configure the software-independent attributes in this section:

Operating-System-Independent Configuration

Cisco IOS Software

These sections describe how to configure the NAM from the Catalyst 6500 series and Catalyst 6000 family switch when using Cisco IOS:

Initial Configuration

Configuring VLANs

Using NetFlow Data Export as a Traffic Source

Using SPAN as a Traffic Source

Initial Configuration

Before you can use the NAM for network analysis, you must log into the NAM root account and configure the following:

IP address

Subnet mask

IP broadcast address

IP host name

Default gateway

Domain name

If applicable, the DNS name server

If you are using an external SNMP manager to communicate with the NAM, configure the following:

SNMP MIB variables

Access control for the SNMP agent

System group settings on the NAM

To start the web server, use the ip http server enable command.

To configure these parameters for the NAM, follow these steps:


Step 1 Enter this command to verify that the NAM is installed and that the power is on:

Router#  show module mod

Step 2 Establish a console session with the NAM by entering:

Router#  session slot module_number processor 1

Step 3 At the login prompt, type root to log in to the root account.

Step 4 At the password prompt, type root as the root password.


Note If you have not changed the password from the factory-set default, a warning message displays. If you decide to change the password from the default, see the "Changing the NAM CLI Passwords" section for more information.


Step 5 Configure the IP address and subnet mask by entering:

root@localhost# ip address ip-address subnet-mask

Step 6 Configure the IP broadcast address by entering:

root@localhost# ip broadcast broadcast-address

Step 7 Configure the IP host name used in the CLI prompt, show commands, and log messages by entering:

root@localhost# ip host [host-name]

Step 8 Configure the default gateway by entering:

root@localhost# ip gateway default-gateway

Step 9 Configure the domain name for the NAM by entering:

root@localhost# ip domain domain-name

Step 10 Configure one or more IP addresses as DNS name servers by entering:

root@localhost# ip nameserver ip-address [name-server1] [name-server2]


Note The ip nameserver command can accept up to a maximum of three name server addresses (two addresses are optional).


Step 11 Verify the NAM configuration by entering:

root@localhost# show ip

Step 12 Configure the SNMP syslocation MIB variable by entering:

root@localhost# snmp location location-string


Note The MIB variables in Step 13 and Step 14 must be valid DisplayString texts, each with a maximum length of 64 characters.


Step 13 Set the SNMP sysContact MIB variable by entering:

root@localhost# snmp contact contact-string

Step 14 Set the SNMP sysName MIB variable by entering:

root@localhost# snmp name name-string


Note You can delete the SNMP location, SNMP contact, or SNMP name by entering the respective command without any parameters.


Step 15 Set the SNMP agent community string parameter password for read-write access by entering:

root@localhost# snmp community community-string rw

Step 16 Set the SNMP agent community string parameter password for read-only access by entering:

root@localhost# snmp community community-string ro


Note Clear the SNMP community string with the snmp delete community community-string command.


Step 17 Verify the SNMP access controls and settings by entering:

root@localhost# show snmp


After completing this configuration, the NAM is ready to use with any other IETF-compliant RMON application.


Note If you are using the Real Time Monitor (RTM), you need to input the community strings in RTM exactly as you enter them in the NAM.


This example shows how to configure the NAM:

Router#  session slot 8 processor 1
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 127.0.0.81 ... Open

Cisco Network Analysis Module (WS-SVC-NAM-1)

login: root
Password: 

Network Analysis Module (WS-SVC-NAM-1) Console, 2.1(1)
Copyright (C) 1999, 2000, 2001 Cisco Systems, Inc.

WARNING! Default password has not been changed!

root@localhost# ip address 172.18.52.29 255.255.255.224
root@localhost# ip broadcast 172.18.52.31
root@localhost# ip host nam1
root@localhost# ip gateway 172.69.2.132
root@localhost# ip domain cisco.com
root@localhost# ip nameserver 171.62.2.132
root@localhost# show ip
IP address:        172.20.98.182
Subnet mask:       255.255.255.192
IP Broadcast:      172.20.255.255
DNS Name:          namlab-kom6.cisco.com
Default Gateway:   172.20.98.129
Nameserver(s):     171.69.2.133
HTTP server:       Enabled
HTTP secure server:Disabled
HTTP port:         80
HTTP secure port:  443
TACACS+ configured:No
Telnet:            Enabled
SSH:               Disabled
root@localhost# 
root@localhost# snmp location "Cisco Lab, Building X, Floor 1"

root@localhost# snmp contact "Jane Doe, Cisco Systems, (408) 111-1111"
root@localhost# snmp name "6k-NAM - Slot 2"
root@localhost# snmp community public ro
root@localhost# snmp community private rw

root@localhost# show snmp

SNMP Agent:   nam1.cisco.com   172.18.52.29

SNMPv1:  Enabled
SNMPv2C: Enabled
SNMPv3:  Disabled

community public 	read
community private 	write

sysDescr         "Catalyst 6500 Network Management Module (WS-SVC-NAM-1)"
sysObjectID      enterprises.9.5.1.3.1.1.2.914
sysContact       "Jane Doe, Cisco Systems, (408) 111-1111"
sysName          "6k-NAM - Slot 2"
sysLocation      "Cisco Lab, Building X, Floor 1"
root@localhost# 

Configuring VLANs

To configure a VLAN for the NAM management port, you must use the analysis module mod_num management-port access-vlan vlan_id command.

Using NetFlow Data Export as a Traffic Source

To use NetFlow Data Export (NDE) as a traffic source for the NAM, enable the NetFlow Monitor option to allow the NAM to receive the NDE stream. The statistics are presented on reserved ifIndex.3000.

NDE makes traffic statistics available for analysis by an external data collector. You can use NDE to monitor all Layer 3-switched and all routed IP unicast traffic. In a Catalyst 6500 series and Catalyst 6000 family switch, both the PFC and the MSFC maintain NetFlow caches that capture flow-based traffic statistics. The cache on the PFC captures statistics for Layer 3-switched flows. The cache on the MSFC captures statistics for routed flows.


Note For information on configuring NDE, refer to the switch software configuration guide.


To configure NDE for the Cisco IOS software, follow these steps:


Step 1 Determine the current NDE configuration by entering:

Router#  show running-config | include mls
mls rp nde-address 172.18.27.229
mls rp ip route-map
mls rp ip
no mls ip multicast aggregate
no mls ip multicast non-rpf cef
mls aging fast
mls flow ip full
mls flow ipx destination-source
mls nde flow include protocol tcp
mls nde sender
mls qos statistics-export interval 300
mls qos statistics-export delimiter |

Router# show running-config | include flow
mls flow ip full
mls flow ipx destination-source
mls nde flow include protocol tcp
 ip route-cache flow
 ip route-cache flow
 ip route-cache flow
ip flow-export source Vlan2
ip flow-export destination 172.18.27.229 3000
ip flow-aggregation cache as

Step 2 Determine the configured NDE exports by entering:

Router# show mls nde
 Netflow Data Export enabled
 Exporting flows to 172.18.27.229 (3000)
 Exporting flows from 172.18.27.221 (57675)
 Version:7
 Include Filter is:
   protocol:TCP
 Exclude Filter not configured
 Total Netflow Data Export Packets are:
    0 packets, 0 no packets, 0 records
 Total Netflow Data Export Send Errors:
        IPWRITE_NO_FIB = 0
        IPWRITE_ADJ_FAILED = 0
        IPWRITE_PROCESS = 0
        IPWRITE_ENQUEUE_FAILED = 0
        IPWRITE_IPC_FAILED = 0
        IPWRITE_MTU_FAILED = 0
        IPWRITE_ENCAPFIX_FAILED = 0

Router# show ip flow export
Flow export is enabled
  Exporting flows to 172.18.27.229 (3000)
  Exporting using source interface Vlan2
  Version 1 flow records
  0 flows exported in 0 udp datagrams
  0 flows failed due to lack of export packet
  0 export packets were sent up to process level
  0 export packets were dropped due to no fib
  0 export packets were dropped due to adjacency issues
  0 export packets were dropped due to fragmentation failures
  0 export packets were dropped due to encapsulation fixup failures
  0 export packets were dropped enqueuing for the RP
  0 export packets were dropped due to IPC rate limiting

Step 3 Configure NDE as follows:

Router(config)# mls nde sender
Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# mls rp nde-address 172.18.27.229

Router(config)# mls flow ip full

Router(config)# mls nde flow include protocol tcp

Router(config)# ip flow-export destination 172.18.27.229 3000


Note The UDP port number must be set at 3000.


Router(config)# ip flow-export source vlan 2

Router(config)# ip flow-aggregation cache as

Router(config-flow-cache)#enable

Router(config)# interface GigabitEthernet8/6
Router(config)# interface vlan 22
Router(config-if)# ip address 1.2.3.4 255.255.255.0

Router(config-if)# ip route-cache flow

When you configure a NAM module as an NDE collector, you should use the IP address of the NAM (set up by sessioning into the NAM module).

Step 4 Synchronize NDE-related information with the NAM by entering:

Router# hw-module module 5 sync nde-info

This command may prompt you to reset the module. Use this command whenever the NDE configuration and the NAM configuration are completed (such as NAM management port VLAN and that VLAN interface's IP address and other configuration information).


Note If the NAM is not being used as an NDE collector, this step is not required. This step only applies to the NAM that has version 1.2(xx). (NAM version 1.1(xx) is not supported).


Using SPAN as a Traffic Source

You can configure SPAN as a traffic source using both the CLI and the NAM Traffic Analyzer application.

The NAM can analyze Ethernet traffic from Ethernet, Fast Ethernet, Gigabit Ethernet, trunk port, or Fast EtherChannel SPAN source ports. You can also specify an Ethernet VLAN as the SPAN source.

For more information on SPAN, refer to the Catalyst 6000 Family IOS Software Configuration Guide at the following website:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/index.htm

You cannot use ports on the NAM module as SPAN source ports.

 
Command
Purpose
 
Router (config)# monitor session {session_number} 
{source {interface type slot/port} | {vlan vlan_ID}} 
[, | - | rx | tx | both]

Sets the source interfaces and VLANs for the monitor session.

 
Router (config)# monitor session {session_number} 
{destination analysis module NAM module number 
data-port port}

Enables port 1 of the NAM as a SPAN destination.

 
Router (config)# no monitor session session_number

Disables the monitor session.

 
Router (config)# monitor session {session_number} 
{filter {vlan_ID} [, | - ]}

Filters the SPAN session so that only certain VLANs are seen from switch port trunks.

 
Router # show monitor session {session_number}

Shows current monitor sessions.

To enable SPAN on the NAM, perform one of these tasks:

This example shows how to enable SPAN on the NAM:

Router#  show monitor
Session 1
---------
Source Ports:
    RX Only:      None
    TX Only:      None
    Both:         None
Source VLANs:
    RX Only:      None
    TX Only:      None
    Both:         None
Destination Ports:None
Filter VLANs:     None

Session 2
---------
Source Ports:
    RX Only:      None
    TX Only:      None
    Both:         None
Source VLANs:
    RX Only:      None
    TX Only:      None
    Both:         None
Destination Ports:None
Filter VLANs:     None

Router#  conf t
Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# monitor session 1 source vlan 1 both


Note If you are using the switch CLI to configure SPAN as a traffic source to NAM-1,the SPAN destination port for NAM-1 is data port 1. The SPAN destination port (SPAN Port 1) for NAM-2 is data port 1. The destination data port 2 is not available in this NAM release although switch and the hardware support is available.


Router# 
00:21:10:%SYS-5-CONFIG_I:Configured from console by console
Router# conf t
Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)#  monitor session 1 destination analysis-module 8 data-port 1
Router#  show monitor
Session 1
---------
 Type       :Local Session
Source Ports:
    RX Only:      None
    TX Only:      None
    Both:         None
Source VLANs:
    RX Only:      None
    TX Only:      None
    Both: