cc/td/doc/product/10_100hb/1538m_mh
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Overview

Overview

This chapter describes the features and components of the Cisco 1538 series Micro Hubs 10/100 (hereafter collectively referred to as the "Micro Hubs"). These class-II repeaters are a part of the Cisco Networked Office stack, a family of stackable, desktop networking platforms designed for small workgroups.

Overview of the Micro Hubs

The Micro Hubs are stackable, 8-port, 10/100-Mbps, autosensing Fast Ethernet class II repeaters with internal bridging.

Either hub model can be a standalone networking device or can connect to other routers, switches, and hubs to form a larger network. You can also stack and connect up to four hubs through the rear-panel ports to form a larger network.

Features

Table 1-1 summarizes the features of the Micro Hubs.
Table 1-1: Feature Summary of the Micro Switch
Feature Description
Management

  • Simple Network Management Protocol (SNMP) and Remote Monitoring (RMON) provides configuration, management and monitoring on a per-port and per-hub basis.

  • Three management interface options:

    • The Cisco ConfigMaker configuration application provides a single configuration interface for all products in the Cisco Networked Office stack.

    • Cisco 1538 Hub Manager with an embedded HTTP server provides an interface for all supported management functions.

    • A command-line interface (CLI) supports management through Telnet in-band or console port out-of-band connections.

  • Menu-based diagnostic console for hub recovery tasks.

  • Cisco Discovery Protocol (CDP) enables network management stations to discover the hub in a network topology.

  • Manages up to 32 ports in a 4-hub stack with one IP address.

Stacking

  • Integrated stacking ports allow up to four hubs in a single collision domain.

  • Two managed hubs can be deployed for management backup.

Performance

  • Autosensing on all ports allows automatic configuration for either 10BaseT or 100BaseT connections.

  • Built-in high-speed bridge function automatically connects 10BaseT and 100BaseT workstations without an external switch or router.

  • Embedded switch supports store-and-forward switching and filtering and forwarding rate at full-wire speed.

MDI/MDI-X connectivity

  • MDI/MDI-X option for port 5 inter-hub connectivity without crossover cables.

  • Class II repeater supports a two-hub daisy chain.

Connectivity

  • Complies to the IEEE 802.3 10BaseT and 802.3u 100BaseTX specifications.

Security slot

  • The switch can be secured to a desktop or other surface using lockdown equipment.

Front-Panel LEDs

This section describes the hub front-panel LEDs.


Figure 1-1: Front-Panel LEDs

Rear-Panel Components

Figure 1-2 shows the rear-panel ports, connectors, and LEDs for the Cisco 1538M and Cisco 1538 Micro Hubs.


Figure 1-2: Rear-Panel LEDs and Components of the Cisco 1538M Managed Hub
Figure 1-3: Rear-panel Components of the Cisco 1538 Manageable Hub

Stack Management

Micro Hubs can be interconnected by using the stacking cable and the stacking connectors on the rear panel of the hubs, creating a stack of up to four Micro Hubs (Figure 1-4). The interconnected units in that stack appear to the rest of the network and to the management interface as a single logical repeater. You can have a second managed hub in the stack act as a redundant stack manager in case the primary manager fails.

Note You need at least one managed hub in your stack if you want to manage the stack.

Figure 1-4: Stacking Micro Hubs to Create Larger Managed Networks

For more information about stacking Micro Hubs, see "Installing Micro Hubs in a Stack".

Management Options (Cisco 1538M Hub)

The Cisco 1538M hub can manage a single hub or a hub stack. You can use the default settings shipped with the hub, or you can customize the configuration through the Cisco 1538 Hub Manager web-based interface, the CLI, or SNMP.

The Cisco 1538 Hub Manager is the easiest interface to use for the basic configuration and monitoring tasks. To perform all the configuration and monitoring tasks, use the CLI and SNMP.

This section provides the following information:

Note The menu-based diagnostic console is described in the "Recovery Procedures Using the Diagnostic Console" section.

Default Configuration Settings

The hub is designed to operate with little or no user intervention. After you assign the IP information, the hub uses its default settings (Table 1-2) and begins forwarding packets as soon as it is powered up and connected to compatible devices.

.
Table 1-2: Default Settings and Cisco 1538 Hub Manager Pages
Feature Default Setting Hub Manager Page
Management

IP information

0.0.0.0

IP Management Page

Stack management

---

Group Management Page

Cisco Discovery Protocol (CDP)

Enabled

CDP Management Page

Performance Tuning

Speed of ports

Autonegotiate

Port Management Page

Security

Hub password

None

Home Page

Community string

public/private

SNMP Management Page

Trap manager

None

SNMP Management Page

Write manager

None

SNMP Management Page

Diagnostics

Usage reports

---

Detailed Group Statistics Page

Detailed Port Statistics Page

Remote monitoring

Enabled

---

Upgrades

Firmware

---

System Configuration Page

For procedures on how to reset all hub console port settings to the factory defaults, see the "Resetting the Hub to the Factory Defaults" section.

Overview of the Cisco 1538 Hub Manager

The Cisco 1538 Hub Manager (hereafter referred to as the hub manager) is a web-based graphical user interface for basic hub configuration and monitoring. Using the hub manager, you can configure and monitor the hub from anywhere on your intranet.

Each hub manager page

To use the hub manager, you must have one of these web browsers installed on your management station:

Management Tasks Supported on the Hub Manager

The management tasks you can perform from the hub manager can be grouped as described in Table 1-3.

Procedures for accessing and using the hub manager are provided in

Note Information provided in "Configuring and Monitoring from the Hub Manager," is also provided in the hub manager online help.


Table 1-3: Configuration and Monitoring Tasks
Changing Hub and Port Configuration Settings

Assigning or Changing Basic Hub Information

Changing the Port Settings

Managing the Hub Segments

Changing the Hub IP Information

Changing the CDP Settings

Changing the System Configuration

Changing Hub Security

Assigning or Changing the Hub Password

Changing the SNMP Settings

Monitoring Hub and Port Conditions

Using the Hub Image to Monitor the Hub

Checking or Resetting Port Statistics

Checking or Resetting Hub Statistics

Remote Monitoring

Overview of the Command-Line Interface

Using the CLI, you can access the hub software and perform the same basic system configuration and system monitoring tasks available through the hub manager. You can also perform privileged configuration and troubleshooting tasks available only through the CLI and SNMP.

Procedures describing how to access the CLI are in the "Accessing the CLI" section. For complete information about using the CLI, refer to the Cisco 1538 Series Micro Hub 10/100 Command Reference.

Overview of SNMP

You can configure and monitor the hub by accessing the Management Information Base (MIB) variables through Simple Network Management Protocol (SNMP), an application-layer protocol facilitating the exchange of management information between network devices. The hub supports a comprehensive set of MIB objects, including four Remote Monitoring (RMON) groups. (The "Accessing the MIB Files through SNMP" section provides information about the MIB files and about accessing them.)

The SNMP system consists of three parts: SNMP manager, SNMP agent, and the MIB files. SNMP places all operations in a get-request, get-next-request, and set-request format. For example, an SNMP manager can get a value from an SNMP agent or store a value into that SNMP agent. The SNMP manager can be part of a network management system (NMS), and the SNMP agent can reside on a networking device such as a hub. You can compile the hub MIB files with your network management software. The SNMP agent can respond to MIB-related queries being sent by the NMS.

An example of an NMS is the CiscoWorks network management software. CiscoWorks uses the hub MIB variables to set device variables and to poll devices on the network for specific information. The results of a poll can be displayed as a graph and analyzed in order to troubleshoot internetworking problems, increase network performance, verify the configuration of devices, monitor traffic loads, and more.

Figure 1-5 shows how the SNMP agent gathers data from the MIB file, which holds information about device parameters and network data. The agent can send traps, or notification of certain events, to the manager.


Figure 1-5: SNMP Network
Note Make sure you use the correct Read and Write community strings so that your SNMP request does not fail. Refer to the online help SNMP Management Page for the correct community strings.

The SNMP manager uses information in the MIB files to perform the operations described in Table 1-4.


Table 1-4: SNMP Manager Operations
Operation Description

get-request

Retrieves a value from a specific variable.

get-next-request

Retrieves a value from a variable within a table.1

get-response

Reply to a get-request, get-next-request, and set-request sent by an NMS.

set-request

Store a value in a specific variable.

trap

Send an unsolicited message from an SNMP agent to an SNMP manager indicating that some event has occurred.

1An SNMP manager does not need the exact variable name. It sequentially searches to find the needed variable from within a table.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Jul 18 10:52:30 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.