|
|
Catalyst 2100 can be managed in-band through any SNMP-compatible workstation or through Telnet. This chapter describes how to use the pre-compiled MIBs supplied on the Catalyst 2100 diskettes. Catalyst 2100 supports standard SNMP MIB II objects as well as SNMP extensions designed to maximize Catalyst 2100's manageability and configurability.
The complete set of Catalyst 2100 MIB objects and other SNMP-based management techniques are described in a separate manual, Catalyst 2000 MIB Reference Manual, available on request from Cisco Systems.
You can use any Telnet TCP/IP package to invoke the management console. Catalyst 2100 supports up to seven simultaneous Telnet sessions. See the "Out-of-Band Management" chapter for details on using the Catalyst 2100 management console.
This section describes how to configure the following platforms for Catalyst 2100 in-band management:
Catalyst 2100 must be configured with an IP address before it can make available any in-band management. You can assign an individual address to each Catalyst 2100, or you can use the BOOTP protocol to maintain a centralized database of such addresses.
A host machine with a BOOTP server program is needed to use BOOTP. A database containing a list of physical MAC addresses and corresponding IP addresses must be set up on this host. Other information such as the corresponding subnet masks, default gateway addresses and host names, can also be stored in the database but are optional. The Catalyst 2100 must be able to access the BOOTP server through one of its ports.
After a system reset, Catalyst 2100 looks into its Non-Volatile Random Access Memory (NVRAM) for a configured IP address, and if they exist, a default gateway address and IP subnet mask.
If an IP address has not been configured, Catalyst 2100 transmits a BOOTP broadcast request to all of its ports having a physical connection, requesting a mapping for its physical MAC address. A valid response will include the IP address, which is mandatory, along with the subnet mask, the default gateway and the host name, which are all optional.
The reception of a valid BOOTP response immediately activates the rest of the system's protocol suite, without requiring a system reset. The information is also saved in the NVRAM so the next reset will not have to redeploy BOOTP.
As long as its IP address remains undiscovered, Catalyst 2100 will resend BOOTP requests for up to 30 minutes.
For more information about using BOOTP, refer to the BOOTP server documentation.
The following tables list the MIB objects from the following MIBs:
| Action | Associated MIB Objects |
| View Self-Test Results | sysInfoPOSTResult sysInfoPOSTPortFailedPostMap |
| View System Information | sysInfoFwdEngineRevision sysInfoBoardRevision sysInfoTotalNumberOfPorts sysInfoNumberOfSwitchPorts sysInfoNumberOfInstalledModules sysInfoNumberofSwitchPorts sysInfoNumberOfSharedPorts sysInfoAddrCapacity sysInfoRestrictedStaticAddrCapacity |
| View/Configure RS-232 Port for an Attached Modem | netMgmtModemInitString netMgmtModemAutoAnswer netMgmtModemDialString netMgmtModemDialDelay |
| View/Configure Logon Security | netMgmtConsolePasswordThresh netMgmtConsoleSilentTime netMgmtConsoleInactTime |
| View/Configure Switching Mode | sysConfigSwitchingMode sysConfigMulticastStoreAndForward |
| View/Configure Port Monitoring Mode | sysConfigMonitor sysConfigMonitorPort sysConfigHigherProtocolMonitor swPortMonitoring |
| Action | Associated MIB Objects |
| View/Configure Virtual LAN Information | vlanMaxSupported vlanAllowMembershipOverlap |
| View/Configure Virtual LAN membership | vlanIndex vlanName vlanMemberPorts vlanMemberIndex vlanMemberPortIndex vlanMemberPortOfVlan |
| View/Configure Address Security | swPortAddressingSecurity swPortAddressTableSize swPortSecuredAddressViolations sysConfigAddressViolationAlert sysConfigAddressViolationAction |
| View/Configure Performance Information | sysInfoBuffersUsed sysInfoMaxBuffers sysInfoUtilDisplay swPortTxQueueFullDiscards swPortRxNoBufferDiscards bandwidthUsageCurrent bandwidthUsageMaxPeakEntries bandwidthUsagePeakInterval bandwidthUsagePeakRestart bandwidthUsageCurrentPeakEntry bandwidthUsagePeakIndex bandwidthUsageStartTime bandwidthUsagePeak bandwidthUsagePeakTime |
| View/Configure Port Characteristics | swPortIndex swPortName swPortMediaCapability swPortControllerRevision swPortMtu swPortSpeed swPortConnectorType sysConfigPort25Connector swPortFullDuplex |
| Action | Associated MIB Objects |
| View/Configure Port Address Status | swPortNumberOfLearnedAddresses swPortNumberOfStaticAddresses swPortEraseAddresses swPortFloodUnregisteredMulticasts swPortFloodUnknownUnicasts |
| View Port Receive Statistics | swPortRxStatIndex swPortRxTotalOctets swPortRxTotalOctetsWraps swPortRxTotalFrames swPortRxUnicastFrames swPortRxUnicastlOctets swPortRxUnicastOctetsWraps swPortRxBroadcastFrames swPortRxBroadcastOctets swPortRxBroadcastOctetsWraps swPortRxMulticastFrames swPortRxMulticastOctets swPortRxMulticastOctetsWraps swPortRxForwardedFrames swPortRxFilteredFrames swPortRxNoBufferDiscards swPortRxFCSErrors swPortRxAlignmentErrors swPortRxFrameTooLongs swPortRxRunts |
| View/Configure Port Status | swPortStatus swPortAdminStatus swPortLastStatus swPortStatusChanges swPortLinkbeatStatus swPortLinkbeatLosses swPortJabberStatus swPortJabbers |
| Action | Associated MIB Objects |
| View Port Transmit Statistics | swPortTxStatIndex swPortTxTotalOctets swPortTxTotalOctetsWraps swPortTxTotalFrames swPortTxUnicastFrames swPortTxUnicastlOctets swPortTxUnicastOctetsWraps swPortTxBroadcastFrames swPortTxBroadcastOctets swPortTxBroadcastOctetsWraps swPortTxMulticastFrames swPortTxMulticastOctets swPortTxMulticastOctetsWraps swPortTxDeferrals swPortTxSingleCollisions swPortTxMultipleCollisions swPortTxLateCollisions |
| View/Configure Collision Histograms | swPortTxCollIndex swPortTxCollCount swPortTxCollFrequencies |
| View/Configure Spanning-Tree Protocol | sysConfigEnableSTP |
| View/Configure for In-Band Management | netMgmtIpAddress netMgmtDefaultGateway netMgmtIpSubnetMask vlanIpAddress vlanIpSubnetMask |
| View/Configure Set Clients | netMgmtSetClientIndex netMgmtSetClientAddr netMgmtSetClientStatus |
| View/Configure Trap Clients and Traps | netMgmtTrapClientIndex netMgmtTrapClientAddr netMgmtTrapClientComm netMgmtTrapClientStatus netMgmtEnableLinkTraps netMgmtEnableAuthenTraps logonIntruder topologyChange switchDiagnostic newRoot |
| Action | Associated MIB Objects |
| View/Configure Firmware Upgrades | upgradeFirmwareSource upgradeEPROMRevision upgradeFlashSize upgradeFlashBankStatus upgradeTFTPServerAddress upgradeTFTPLoadFilename upgradeTFTPInitiate upgradeAutoExecute upgradeTFTPAccept |
| Reset System | sysConfigReset sysConfigDefaultReset |
| Clear Port Statistics | sysConfigClearPortStats swPortClearStatistics |
This section describes how to load and integrate the Catalyst 2100 MIB extensions into Novell's NetWare Management System (NMS). These files are located with the NMS profiles on the Catalyst 2100 DOS-formatted diskette included with the Catalyst 2100. The diskette contains the following MIB files:
The files with .prf are NMS profiles. They are described in the section "Using the Supplied NMS Profiles" in this chapter and can be integrated into Novell NMS after performing step 2 in the following procedure. These instructions are specific to Novell NMS version 2.0 and 2.1. For other versions or for additional information, consult your Novell NMS documentation.
With a properly configured Catalyst 2100 on' an accessible local network, you are now ready to browse and set the Catalyst 2100 objects that are included in this Profile.
The Catalyst 2100 diskette contains a number of NMS Profiles that have been set up with Catalyst 2100 MIB objects. These files are provided for convenience and can be used without change. Steps 1 and 2 listed above must be completed before these profiles can be used.
Copy the files *.PRF to the directory \nms\snmpmibs\profiles for a standard NMS installation. The supplied NMS profiles are as follows:
This section describes how to load, integrate and use the Catalyst 2100 MIB extensions with SunNet Manager. These files are archived in TAR format on the UNIX TAR diskette included with Catalyst 2100. Along with the precompiled schema files, the diskette contains the following MIB files:
The schema files can be immediately integrated into SunNet Manager without requiring additional compilation, following the instructions below.
These instructions are specific to SunNet Manager versions 2.1 and 2.2. For other versions or for additional information, consult your SunNet Manager documentation.
SunNet Manager is typically installed in the default directory /opt/SUNWconn/snm or in the directory designated by the environment variable $SNMHOME. Using the UNIX TAR command, extract all files on the Catalyst 2100 UNIX diskette into the directory $SNMHOME/agents on the SunNet Manager workstation as follows:
cd $SNMHOME/agents
tar xvf /dev/fd0
On some UNIX platforms, the name of the floppy device may be different. On SunOS 5.3, it may be necessary to stop the Volume Manager before the TAR diskette can be read. Become the root user and type the following:
/etc/init.d/volmgt stop
cd $SNMHOME/agents
tar xvf /dev/rdiskette
/etc/init.d/volmgt start
The following schemas are also included on the diskette:
Locate the keyword na.snmp.hostfile in the file /etc/snm.conf. This keyword points to the file the SNMP proxy agent and SNMP trap proxy use to obtain target-specific information. In this file, add an entry for each target Catalyst 2100 to be managed. The following are the relevant schema file names to be specified:
Refer to the SunNet Manager reference documentation for detailed specification of the file named by the keyword na.snmp.hostfile.
The SunNet Manager will now understand the Catalyst 2100 Enterprise Specific MIB and trap schemas, the RFC-1317 MIB schema and the RFC-1493 MIB and trap schemas.
Use the SunNet Manager Discover tool to locate and map Catalyst 2100. Once
Catalyst 2100 is discovered and added as an icon to the network map, set up the icon properties to process the Catalyst 2100 schema, RFC-1317 schema and RFC-1493 schema. These schemas will be displayed with the names CATALYST-2000-MIB, BRIDGE-MIB and RFC1317-MIB, respectively, on the icon properties window.
Catalyst 2100 is now manageable using the various facilities provided by SunNet Manager. These include the Quick Dump, Data Report, Event Report and Set Request facilities.
This section describes how to load, integrate and use the Catalyst 2100 MIB extensions with the HP OpenView SNMP Management Platform. The MIB extension files are archived in TAR format on the UNIX TAR diskette that is included with the Catalyst 2100.
The diskette contains the following MIB files:
These instructions are specific to version 3.31 of the HP OpenView SNMP Platform for SunOS 4.1.x or 5.x. For other versions or additional information, consult your applicable HP OpenView documentation.
cd /usr/OV/snmp_mibs
tar xvf /dev/fd0
/etc/init.d/volmgt stop
cd /usr/OV/snmp_mibs
tar xvf /dev/rdiskette
/etc/init.d/volmgt start
A trap client is a management workstation configured to receive and process traps. Catalyst 2100 supports up to four trap clients with separate community strings. At least one trap client must be defined before any traps are generated. See the section "Network Management (SNMP) Configuration" in the "Out-of-Band Management" chapter for instructions on defining trap clients with the Catalyst 2100 management console. See the section "Standard MIBs and MIB Extensions" in this chapter for the MIB objects to use.
Catalyst 2100 can generate the following traps:
|
|