|
|
This manual describes how to configure and manage the FastHub using a standard SNMP-based network-management application. The manual also describes the standard MIB objects and MIB object extensions supported by the FastHub.
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.
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 your authorized Cisco sales representative for detailed information on CiscoWorks.
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:
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 FastHub 300 Series Installation and Configuration Guide.
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.
The network management module (NMM) SNMP agent implements SNMP version 1, specifically supporting:
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.
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).
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:
The MIB object mrNetMgmtEnableAuthenTraps can be set to suppress the generation of the authenticationFailure traps.
To configure a trap client, use the following MIB objects:
This table contains four entries that list the management workstations that are to receive traps generated from this agent.
This read-only MIB object provides identification of a trap client entry.
This read-write MIB object specifies the trap client's name or IP address.
This read-write MIB object specifies the community string used for traps sent to this trap client.
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.
The FastHub generates the following traps:
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.
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.
This trap is issued when either the internal power supply or the redundant power supply (RPS) fails.
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.
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.
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.
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).
This SNMP trap is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.
This SNMP trap is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.
Generated when the repeater is reset or after the completion of a firmware upgrade.
Generated upon a power-on reset.
This trap is currently not generated by the FastHub.
This trap is currently not generated by the FastHub.
Generated when the FastHub receives an SNMP message that is not accompanied by a valid community string.
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.
There are two ways to perform an in-band upgrade:
Follow these steps to upgrade the FastHub firmware:
Step 1 Determine the size of the upgrade file to be loaded, then use mrUpgradeFlashSize to ensure that there is available FLASH memory.
Step 2 If necessary, use the following MIB objects to obtain information about the last upgrade performed:
mrUpgradeLastUpgradeTime--displays the date and time of the last upgrade.
mrUpgradeLastUpgradeSource--displays the IP address of the TFTP server or client that sent the last upgrade file. If the last upgrade was out-of-band through the NMM console port, 0.0.0.0 is displayed.
mrUpgradeLastUpgradeStatus--displays the status of the last upgrade.
Step 3 Use mrUpgradeTFTPServerAddress to specify the name of the TFTP server where the upgrade file is located. Note that if the first non-blank character specified is a NetASCII numeral, the name is assumed to be an IP address. If the first non-blank character is not a NetASCII numeral, it is assumed to be a fully qualified domain name server name, and the Domain Name System (DNS) protocol is used to resolve it to an IP address.
You can also (optionally) provide a name or IP address of a default gateway, as in the case of the TFTP server being located on a non-local IP network.
Step 4 Use mrUpgradeTFTPLoadFilename to specify the name of the firmware upgrade file.
Step 5 Use mrUpgradeTFTPInitiate to initiate the firmware upgrade.
Once initiated, the FastHub-directed method begins issuing a file-open request to the TFTP server. Read requests then follow to obtain the file content. The transfer mode used is octet, the opposite of the text transfer mode. The upgrade process either completes successfully or times out. The time-out interval is approximately 30 seconds. After a successful transfer of the upgrade file, the FastHub resets and executes the new firmware.
In the workstation-directed upgrade, you need a workstation equipped with a TFTP client application. Internet-based UNIX computers such as the Sun workstation usually come configured with such an application. On DOS, these types of applications are available from a number of different vendors.
Using a TFTP client application, you direct the upgrade by issuing write requests to send an upgrade file to the FastHub. After a successful transfer of the upgrade file, the FastHub resets and executes the new firmware.
Although the workstation-directed upgrade gives you extra flexibility, it can present a security issue. Because there is no file authentication involved, the existing FastHub firmware might be overwritten with outdated firmware. To prevent this, upgrade the firmware, and then set the MIB object mrUpgradeTFTPAccept to disabled; the FastHub ignores future workstation-directed upgrade requests.
The XMODEM protocol is used to perform this upgrade. Refer to the FastHub 300 Series Installation and Configuration Guide for detailed information on using the out-of-band management interface to perform a firmware upgrade.
This section provides brief descriptions of individual MIB implementations. Also included for each MIB group are the actions used to configure and manage the FastHub and the MIB objects associated with each action.
The Internet Activities Board recommends that all TCP/IP implementations be network-manageable. Aspects of managing various components of the Internet are specified in RFC 1156, Management Information Base for Network Management of TCP/IP-based Internets. This MIB is referred to as the MIB-II.
The FastHub implements all groups in the MIB-II except the Exterior Gateway Protocol (EGP) group. MIB-II objects are used to control and monitor the management protocol operations of the NMM SNMP agent.
The standard Ethernet transmission MIB is used to supplement the MIB-II.
The RS-232 MIB is used to configure the NMM RS-232 serial port (console port).
| Action | Associated MIB Objects |
|---|---|
| View/Configure RS-232 Port Characteristics | rs232Number rs232PortIndex rs232PortType rs232PortInSigNumber rs232PortOutSigNumber rs232PortInSpeed rs232PortOutSpeed |
| View RS-232 Port Input/Output Signals | rs232InSigPortIndex rs232InSigName rs232InSigState rs232InSigChanges rs232OutSigPortIndex rs232OutSigName rs232OutSigState rs232OutSigChanges |
| View/Configure RS-232 Async Port Characteristics | rs232AsyncPortIndex rs232AsyncPortBits rs232AsyncPortStopBits rs232AsyncPortParity rs232AsyncPortAutobaud |
| View RS-232 Async Port Statistics | rs232AsyncPortParityErrs rs232AsyncPortFramingErrs rs232AsyncPortOverrunErrs |
This is the standard Repeater MIB for managing IEEE 802.3 repeaters. The FastHub supports this MIB as it is defined in RFC 1516, Definitions of Managed Objects for IEEE 802.3 Repeater Devices.
| Action | Associated MIB Objects |
|---|---|
| View FastHub Operational Status | rptrGroupCapacity rptrOperStatus rptrHealthText rptrTotalPartitionedPorts rptrMonitorTransmitCollisions |
| Reset/Test FastHub | rptrReset rptrNonDisruptTest |
| View/Configure FastHub Ports | rptrPortGroupIndex rptrPortIndex rptrPortAdminStatus rptrPortAutoPartitionState rptrPortOperStatus rptrPortConnectorType rptrPortLinkbeatStatus rptrPortName |
| View/Configure FastHub Groups | rptrGroupIndex rptrGroupDescr rptrGroupObjectID rptrGroupOperStatus rptrGroupLastOperStatusChange rptrGroupPortCapacity |
| View FastHub Group Statistics | rptrMonitorGroupIndex rptrMonitorGroupTotalFrames rptrMonitorGroupTotalOctets rptrMonitorGroupTotalErrors |
| View FastHub Port Statistics | rptrMonitorPortGroupIndex rptrMonitorPortIndex rptrMonitorPortReadableFrames rptrMonitorPortReadableOctets rptrMonitorPortFCSErrors rptrMonitorPortAlignmentErrors rptrMonitorPortFrameTooLongs rptrMonitorPortShortEvents rptrMonitorPortRunts rptrMonitorPortCollisions rptrMonitorPortLateEvents rptrMonitorPortVeryLongEvents rptrMonitorPortDataRateMismatches rptrMonitorPortAutoPartitions rptrMonitorPortTotalErrors rptrMonitorPortIsolates rptrMonitorPortSymbolErrors |
| View Address Tracking Information | rptrAddrTrackGroupIndex rptrAddrTrackPortIndex rptrAddrTrackLastSourceAddress rptrAddrTrackSourceAddrChanges rptrAddrTrackNewLastSrcAddress |
The FastHub implements extensions to the standard MIB-II in the form of the enterprise-specific MIB. These extensions are used to manage unique characteristics of the FastHub architecture.
| Action | Associated MIB Objects |
|---|---|
| View/Configure Hub Stack | mrStackUnit Capacity mrStackNumberofUnitsPresent mrStackSelectPrimarySupervisorUnit mrStackUnitSupervisorIsPrimary |
| Clear Stack Statistics | mrStackClearStatistics |
| View/Configure POST | mrStackPOSTSelect mrStackUnitPOSTResult |
| Reset Hub Stack | mrStackReset mrStackDefaultReset |
| View/Configure Supervisor Log | mrSupervisorClearLogTable mrSupervisorLogIndex mrSupervisorLogTime mrSupervisorLogInfo |
| View/Configure FastHub (Unit) | mrStackUnitIndex mrStackUnitPresent mrStackUnitFirstGroupIndex mrStackUnitLastGroupIndex mrStackUnitSupervisorPresent mrStackUnitSupervisorMajorVersion mrStackUnitSupervisorMinorVersion mrStackUnitSupervisorBootstrapMajorVersion mrStackUnitSupervisorBootstrapMinorVersion mrStackUnitPortVisualIndicatorSelect mrStackUnitBasePortVisualIndicatorGreenMap mrStackUnitBasePortVisualIndicatorAmberMap mrStackUnitActivityVisualIndicator mrStackUnitCollisionVisualIndicator |
| View/Configure 100BaseTX/16 Port Expansion Module | mrStackUnitExpansionModulePresent mrStackUnitExpansionPortVisualIndicatorGreenMap mrStackUnitExpansionPortVisualIndicatorAmberMap |
| View Unit Redundant Power Supply (RPS) Status | mrStackUnitRPSStatus mrStackUnitRPSVisualIndicator |
| View/Configure Network Management Module (NMM) | mrNetMgmtIpAddress mrNetMgmtIpSubnetMask mrNetMgmtDefaultGateway mrNetMgmtEnableAuthenTraps mrNetMgmtEnableRIP |
| View/Configure Domain Name Servers | mrNetMgmtDomainServer1IpAddress mrNetMgmtDomainServer2IpAddress mrNetMgmtDefaultSearchDomain |
| Configure the Management Console | mrNetMgmtConsoleInactTime mrNetMgmtConsolePasswordThreshold mrNetMgmtConsoleSilentTime |
| View/Configure Set Clients | mrNetMgmtSetClientIndex mrNetMgmtSetClientName mrNetMgmtSetClientStatus |
| View/Configure Trap Clients and Traps | mrNetMgmtTrapClientIndex mrNetMgmtTrapClientName mrNetMgmtTrapClientComm mrNetMgmtTrapClientStatus logonIntruder hubStackDiagnostic powerSupplyFailure ipAddressChange |
| Configure a Modem (RS-232 port) | mrNetMgmtModemInitString mrNetMgmtModemDialString mrNetMgmtModemDialDelay mrNetMgmtModemAutoAnswer |
| Upgrade FastHub Firmware | mrUpgradeFlashSize mrUpgradeLastUpgradeTime mrUpgradeLastUpgradeSource mrUpgradeLastUpgradeStatus mrUpgradeTFTPServerAddress mrUpgradeTFTPLoadFilename mrUpgradeTFTPInitiate mrUpgradeTFTPAccept |
The FastHub implements the first four object groups of the standard Remote Monitoring (RMON) MIB.
| Action | Associated MIB Objects |
|---|---|
| View/Configure Ethernet Statistics Group | etherStatsIndex etherStatsDataSource etherStatsDropEvents etherStatsOctets etherStatsPkts etherStatsBroadcastPkts etherStatsMulticastPkts etherStatsCRCAlignErrors etherStatsUndersizePkts etherStatsOversizePkts etherStatsFragments etherStatsJabbers etherStatsCollisions etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octets etherStatsPkts1024to1518Octets etherStatsOwner etherStatsStatus |
| View/Configure History Control Group | historyControlIndex historyControlDataSource historyControlBucketsRequested historyControlBucketsGranted historyControlInterval historyControlOwner historyControlStatus |
| View History Group Statistics | etherHistoryIndex etherHistorySampleIndex etherHistoryIntervalStart etherHistoryDropEvents etherHistoryOctets etherHistoryPkts etherHistoryBroadcastPkts etherHistoryMulticastPkts etherHistoryCRCAlignErrors etherHistoryUndersizePkts etherHistoryOversizePkts etherHistoryFragments etherHistoryJabbers etherHistoryCollisions etherHistoryUtilization |
| View/Configure Alarm Group | alarmIndex alarmInterval alarmVariable alarmSampleType alarmValue alarmStartupAlarm alarmRisingThreshold alarmFallingThreshold alarmRisingEventIndex alarmFallingEventIndex alarmOwner alarmStatus |
| View/Configure Event Group | eventIndex eventDescription eventType eventCommunity eventLastTimeSent eventOwner eventStatus logEventIndex logIndex logTime logDescription |
| View Remote Monitoring Traps | risingAlarm fallingAlarm |
The CDP MIB is a media- and protocol-independent device-discovery protocol that runs on all Cisco-manufactured equipment including routers, access servers, bridges, and switches. Using CDP, a device can advertise its existence to other devices and receive information about other devices on the same local-area network (LAN) or on the remote side of a wide-area network (WAN). CDP runs on all media that support Subnetwork Access Protocol (SNAP), including LANs, Frame Relay, and Asynchronous Transfer Mode (ATM) media.
| Action | Associated MIB Objects |
|---|---|
| View/Configure CDP Interfaces | cdpInterfaceIfIndex cdpInterfaceEnable cdpInterfaceMessageInterval cdpInterfaceGroup cdpInterfacePort |
| View CDP Cache | cdpCacheIfIndex cdpCacheDeviceIndex cdpCacheAddressType cdpCacheAddress cdpCacheVersion cdpCacheDeviceId cdpCacheDevicePort cdpCachePlatform cdpCacheCapabilities |
|
|