Overview

Using the Simple Network Management Protocol (SNMP), the FastHub communicates with the third-party network-management application through its in-band management interface (the SNMP agent). The management information used to configure and monitor a FastHub are represented as objects in a database called a Management Information Base (MIB). The FastHub can be managed in-band through any SNMP-compatible workstation or through Telnet. The FastHub supports standard MIB-II objects as well as custom extensions found in the enterprise-specific MIB. The extensions provide access to unique FastHub features and other management functions.

The complete set of FastHub MIB objects are listed by function (user action) in the "FastHub MIB Implementation" section in this chapter.

FastHub and SNMP Management Platforms

In general, you use SNMP network-management applications to locate the FastHub icon and access the table of FastHub objects. You can then view the characteristics and counters describing the FastHub and set object values as defined in the FastHub-supported MIBs.

CiscoWorks applications, one method of SNMP network management, are integrated on several SNMP-based network management platforms, including SunNet Manager, HP Open View, and IBM NetView. Contact Cisco Systems or your authorized reseller for detailed information on CiscoWorks.

Supported TCP/IP Protocols

The FastHub uses a subset of the Transmission Control Protocol/Internet Protocol (TCP/IP) suite as the underlying mechanism to transport the SNMP. The following protocols are implemented in the FastHub:

• Internet Protocol (IP)
  

• Internet Control Message Protocol (ICMP)
  

• User Datagram Protocol (UDP)
  

• Transmission Control Protocol (TCP)
  

• Trivial File Transfer Protocol (TFTP)
  

• Bootstrap Protocol (BOOTP)
  

• Address Resolution Protocol (ARP)
  

• Dynamic Host Configuration Protocol (DHCP)
  

• Routing Information Protocol (RIP)
  

• Domain Name Service (DNS)
  

Before Beginning...

Before beginning any in-band management, the FastHub must be configured for SNMP management. To do this, assign an IP address to the FastHub, using the IP Configuration Menu described in the "Out-of-Band Management" chapter of the Catalyst FastHub 100+ Series Installation and Configuration Guide. Also included in the guide is a procedure to assign an IP address using BOOTP/DHCP.

Using Telnet

You can use any Telnet TCP/IP package to access the in-band interface. The FastHub supports up to seven simultaneous Telnet sessions. The Telnet TCP/IP package must support VT-100 terminal emulation.

SNMP Agent

The network management module (NMM) SNMP agent implements SNMP version 1, specifically supporting:

• Trivial authentication using community strings with no privacy.
  

• Get, Get-Next, and Set operations, as well as the ability to generate traps.
  

Community Strings

The SNMP agent implements two separate community strings. The first community string, the Get community string, has a default ASCII value of public and can be used by a management workstation to send Get and Get-Next requests to the agent.

The second string, the Set community string, has a default ASCII value of private and can be used in Get, Get-Next, and Set requests.

These strings are modifiable only through the out-of-band management console. If configured to do so, the SNMP agent generates authenticationFailure traps whenever it receives a request with an invalid community string.

Set Clients

To provide additional security, the NMM SNMP agent uses "set client" IP addresses. Up to four IP addresses can be defined as set clients, giving workstations the authority to issue Set requests and add other set clients. The list of set clients is initially empty, and any set client workstation can set the first address. After the first address (or addresses) are set, only management workstations having the same IP address as those on the list can add more addresses or set other MIB objects. If a management workstation does not have the same IP address as the address on the list, Set requests are dropped (without notification).

Trap Clients

Traps use their own community strings and receiver addresses. A trap receiver, also called a "trap client," is a management workstation configured to receive and process traps. The method by which a trap client workstation is configured is management-platform dependent. The NMM firmware maintains a list with up to four trap IP addresses and four trap community strings, one for each possible trap client. The trap client list is shipped empty from the factory. An empty trap client list disables the generation of all traps.

The FastHub can generate the following traps:

• Five standard MIB-II traps
  

• Three repeater MIB traps
  

• Two remote monitoring (RMON) MIB traps
  

• Four enterprise-specific traps
  

The MIB object mrNetMgmtEnableAuthenTraps can be set to suppress the generation of the authenticationFailure traps.

Configuring a Trap Client

To configure a trap client, use the following MIB objects:

mrNetMgmtTrapClientTable

This table contains four entries that list the management workstations that are to receive traps generated from this agent.

mrNetMgmtTrapClientIndex

This read-only MIB object provides identification of a trap client entry.

mrNetMgmtTrapClientName

This read-write MIB object specifies the trap client's name or IP address.

mrNetMgmtTrapClientComm

This read-write MIB object specifies the community string used for traps sent to this trap client.

mrNetMgmtTrapClientStatus

Setting this read-write MIB object to "invalid" invalidates the corresponding entry. That is, it disassociates the IP address or community string identified with that entry from the table. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management workstations must be prepared to receive tabular information from agents that corresponds to entries not currently in use.

FastHub Traps

The FastHub generates the following traps:

Enterprise-Specific Traps

logonIntruder

A user is repeatedly trying to log on to the management console using an invalid password. You can define the number of invalid passwords permitted before this trap is generated. The FastHub can shut down the management console following the generation of this trap.

hubStackDiagnostic

The FastHub issues this trap when its power-on self-test (POST) does not pass all tests. However, note that some failures are catastrophic, preventing the generation of this trap.

powerSupplyFailure

This trap is issued when either the internal power supply or the redundant power supply (RPS) fails.

ipAddressChange

This trap is issued when the NMM SNMP agent is unable to complete its DHCPDISCOVER/DHCPREQUEST process, when it fails to extend the lease for the current address, or when it accepts an address change from the user.

Repeater Traps

rptrHealth

This trap conveys information related to the operational status of the FastHub. This trap is sent either when the value of rptrOperStatus changes or when a nondisruptive test completes.

rptrGroupChange

This trap is sent when a change occurs in the group structure of the FastHub. This occurs only when a group is logically or physically removed from or added to a repeater.

rptrResetEvent

This trap conveys information related to the operational status of the FastHub. This trap is sent on completion of a reset action (such as an SNMP Set on the rptrReset object).

Remote Network Monitoring Traps

risingAlarm

This SNMP trap is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.

fallingAlarm

This SNMP trap is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.

MIB II Traps

warmStart

Generated when the repeater is reset or after the completion of a firmware upgrade.

coldStart

Generated upon a power-on reset.

linkDown

This trap is currently not generated by the FastHub.

linkUp

This trap is currently not generated by the FastHub.

authenticationFailure

Generated when the FastHub receives an SNMP message that is not accompanied by a valid community string.

Upgrading Firmware

Firmware upgrades transfer (download) an upgrade file directly into the FastHub FLASH memory.

The in-band upgrade is done through a FastHub 100BaseT port using TFTP and requires that the NMM be configured with an IP address. The out-of-band upgrade uses a serial link to the NMM's console port.

Only one upgrade attempt can be in progress at any one time. FastHub firmware returns an error indication when it detects an upgrade conflict.