|
|
This chapter explains how to use the FastHub 400 series Hub Manager on the FastHub 400M models to change the configuration settings and to monitor the hub or hub stack. This chapter assumes that you have already performed the following tasks described in this guide or in the FastHub 400 10/100 Series Cabling and Start Up:
At the top of each hub manager page is a menu bar. Figure 3-1 describes the functions of the pages accessible from the menu bar.
You can change the hub settings by entering information into fields, adding and removing list items, or selecting and deselecting check boxes. Click Apply to save your changes. Click Revert to discard all your unsaved changes and return the previous settings to the page.
You can assign or change basic descriptions about the hub from the hub manager Home Page (Figure 3-2). You can also assign a password to the hub management interfaces
(hub manager and CLI-privileged commands) and monitor network activity through the live hub image. This page also provides a hotlink that opens a Telnet session to the hub command-line interface (CLI), in addition to hotlinks for contacting Cisco Systems resources.
Click HOME on the menu bar to display the Home Page (Figure 3-2) and check and change hub information.
You can assign or change the following information about the hub (be sure to click Apply to save changes):
By default, no password is assigned to the hub management interfaces. You can restrict access to the hub manager or CLI-privileged commands by assigning a password. If a user fails to enter the password within a set number of attempts, the hub sends an SNMP trap to the SNMP trap manager to alert you, via in-band management messages, of the failed attempts. (For information about trap managers, see the "Changing the SNMP Settings" section.)
When a password is assigned, the password prompt is displayed when you or any other user opens a hub manager session and displays the Home Page. The Home Page is redisplayed only after you enter the correct password. If the password prompt reappears, reenter the correct password.
To assign or change the password to the hub manager or CLI-privileged commands:
Step 1 Enter a character string (4 to 8 characters, case sensitive) in the Assign/Change Password field.
Step 2 Enter the same character string in the Reconfirm Password field.
Step 3 Click Apply.
The connection with the hub is broken. The browser prompts you for the new password.
Step 4 Enter the new password at the password authentication prompt, and click OK.
If you have forgotten or do not know the password, see the "Recovering from a Lost or Forgotten Password" section.
The Home Page displays the front-panel image of the hub (Figure 3-3). The following sections provide information on how to use the hub image.
The hub image on the Home Page shows the front-panel LED colors at the last poll interval and refreshes every 30 seconds. The LEDs show system and RPS status, port status, and port speed.
The SYSTEM LED on the hub image always displays green, showing that the hub is operating normally. It does not turn amber if a nonfatal POST failure exists. To verify that there are no nonfatal POST failures, check the actual SYSTEM LED on the hub or use the Diagnostic Console - Systems Engineering Menu (see the "Using the Diagnostic Console - Systems Engineering Menu" section).
The colors of the RPS LED on the hub image show the RPS status (Table 3-1).
| LED Color | Description |
|---|---|
Blue (off) | Internal power supply is powered up. RPS is not powered up. |
Solid green | RPS is powered up and operational. Internal power supply is not powered up. |
Flashing green | Internal power supply and RPS are both powered up and the internal power supply is powering the hub. If the internal power supply fails, the hub powers down and, after 15 seconds, restarts by using the power from the RPS. The hub goes through its normal boot sequence when it restarts. |
Solid amber | RPS is connected but not functioning properly. One of the power supplies in the RPS could be powered down or a fan on the RPS could have failed. |
Click the Mode button on the hub image to change the mode of the port LEDs (Table 3-2). The default mode for the port LEDs is port status. The colors of the port LEDs on the hub image display the status or speed of the individual port (Table 3-3). When you select the port speed mode, the hub remains in that mode for approximately 30 seconds before returning to the default mode, port status.
| For this Mode... | Push the Mode Button Until... |
|---|---|
Port status | The STAT LED is green. |
100BaseT connections | The SPD LED is green. |
| LED Color | Description | |
|---|---|---|
| Port Status |
| |
| Blue (off) | No link. |
| Solid green | Link operational. |
| Solid amber | The port is partitioned. After a packet is successfully sent over this port, the LED is green (normal operating state). |
| Port Speed |
| |
| Blue (off) | Port is connected to a 10BaseTX network device. |
| Green | Port is connected to a 100BaseTX network device. |
The image also shows if there is a 10BaseT/100BaseTX or 100BaseFX switched uplink module installed in the rear-panel expansion slot (Figure 3-4). The colors of the LEDs above the 10BaseT/100BaseTX switched uplink module show port status, duplex mode, and speed (Table 3-4). The colors of the LEDs above the 100BaseFX switched uplink module show port status and duplex mode (Table 3-5).
| LED Color | Description | |
|---|---|---|
| 10/100 Module Port Status (left LED above the module port) | ||
| Blue (off) | No link. |
| Solid green | 10BaseT or 100BaseTX link operational. |
| Flashing green | 10BaseT or 100BaseTX link operational (with activity). |
| 10/100 Module Port Duplex Mode (middle LED above the module port) | ||
| Blue (off) | Operating at half-duplex mode. |
| Solid green | Operating at full-duplex mode. |
| 10/100 Module Port Speed (right LED above the module port) | ||
| Blue (off) | Operating at 10 Mbps. |
| Solid green | Operating at 100 Mbps. |
| LED Color | Description | |
|---|---|---|
| 100BaseFX Module Port Status (left LED above the module port) | ||
| Blue (off) | No link. |
| Solid green | 100BaseFX link operational. |
| 10/100 Module Port Duplex Mode (right LED above the module port) | ||
| Blue (off) | Operating at half-duplex mode. |
| Solid green | Operating at full-duplex mode. |
The Home Page displays an image of the hub stack if you have interconnected hubs (Figure 3-4). The stacking connectors on the stack image is green, showing which stacking connector on each hub is interconnected to another hub. Otherwise, the stacking connector is blue (off).
A radio button appears next to each hub in the stack image. If you click the radio button next to a specific hub and click PORT from the menu bar, the Port Management Page for that hub is displayed. The Port Management Page is also displayed when you select the radio button next to a specific hub on the stack image and then click on a port on that specific hub image.
By default, the radio button next to the top hub in the stack image is selected, whether the top hub is a management hub or not.
For more information about hub stacks and managing them, see the "Managing the Hub Segments" section and "FastHub Stacks."
Click Telnet to open a session on the hub command-line interface (CLI).
The Home Page provides these hotlinks to connect to Cisco Systems' resources:
By default, each 10/100 network port and the 10/100 uplink port on the hub are enabled to transmit packets to and receive them from the device to which it is connected, automatically matching its speed.
Click PORT on the menu bar or click the port on the hub image on the Home Page to display the Port Management Page (Figure 3-5), check the status of the port, and change the port settings.
If you have a hub stack, click the radio button next to the specific hub image on the Home Page, and either click PORT from the menu bar or click the port on the specific hub image. The Port Management Page displays the port settings for the specific hub.
By default, all ports are enabled. To disable a port:
Step 1 In the Link Status: Requested/Actual column, deselect the Enable check box.
Step 2 Click Apply.
A linkDown trap is sent to the management station if you configured an SNMP manager.
To reenable a port:
Step 1 In the Link Status: Requested/Actual column, select the Enable check box.
Step 2 Click Apply.
A linkUp trap is sent to the management station if you configured an SNMP manager.
The Link Status: Requested/Actual column displays the actual status of the port. Each port is always in one of these link states:
Port can transmit and receive data. | |
Port is unable to transmit or receive data. |
The Partition Status column displays whether or not the port has been partitioned by the hub, which usually happens as a result of excessive collisions or a network loop. Each port is always in one of these partition states:
Port is isolated from the network communications. | |
Port is not isolated from the network communications. |
By default, the ports automatically match the transmission speed of the attached device. To change the port speed:
Step 1 From the Speed: Requested/Actual drop-down list, select 10 Mbps, 100 Mbps, or Auto (autonegotiate). The default is Auto.
Step 2 Click Apply.
To assign a name or description to a port:
Step 1 In the Port Name/Description column, enter the port name or a description
(up to 20 characters) of how the port is connected.
Step 2 Click Apply.
Click Switched Uplink Module to display this page.
From the Port Management Page, select a port, and click View to see the statistics for a particular port on the hub. The Detailed Port Statistics Page (Figure 3-6) for the selected port displays the port statistics. Table 3-6 lists the statistics displayed on the page.
Click Reset Port Statistics to reset the statistics.
The hub manager does not automatically refresh the statistics shown on this page. Click Reload to refresh the statistics shown on this page.
Packets | Total number of packets received by the port. |
Bytes | Total number of bytes received by the port. |
FCS Errors | Number of frame check sequence (FCS) errors indicating that frames of data are being corrupted during transmission. |
Alignment Errors | Number of alignment errors (caused if all bytes are not received whole) received by the port. |
Packets Too Long | Number of packets received by the port that exceed the maximum size for IEEE 802.3 frames. |
Short Events | Number of packets received by the port that are smaller than runts, which are smaller than the minimum size for IEEE 802.3 packets. |
Packets Too Short | Number of frames received by the hub that are smaller than the minimum size for IEEE 802.3 frames. |
Collisions | Number of times the hub and the connected device attempt to transmit at the same time. |
Late Events | Number of frames that experienced a collision late in transmission. |
Very Long Events | Number of packets that exceed the maximum length prescribed in IEEE 802.3. |
Data Rate Mismatches | Number of frames whose timing no longer matches the transmit frequency between the hub and the connected device. |
Autopartitions | Number of times the port automatically partitions the segments attached to it. |
Total Errors | Total number of errors received by the port. |
If you have an optional switched uplink module installed in the rear-panel expansion slot on the hub, you can manage the module port as you would the 10/100 network and uplink ports.
Click PORT on the menu bar, and click Switched Uplink Module from the Port Management Page to display the Switched Uplink Module Management Page (Figure 3-7) and check and change the settings. You can also click the module port on the hub image on the Home Page to display the Switched Uplink Module Management Page.
For more information about the switched uplink modules, see "Switched Uplink Modules."
By default, the module port is enabled. To disable the module port:
Step 1 In the Status: Requested/Actual column, deselect the Enable check box.
Step 2 Click Apply.
A linkDown trap is sent to the management station if you configured an SNMP manager.
To reenable the module port:
Step 1 In the Status: Requested/Actual column, select the Enable check box.
Step 2 Click Apply.
A linkUp trap is sent to the management station if you configured an SNMP manager.
The Status: Requested/Actual column displays the actual status of the module port. The module port is always in one of these link states:
Port can transmit and receive data. | |
Port is unable to transmit or receive data. |
The Medium column displays the type of switched uplink module installed in the hub:
10BaseT/100BaseTX | 10BaseT/100BaseTX switched uplink module is installed. |
100BaseFX-SC | 100BaseFX switched uplink module is installed. |
By default, the 10BaseT/100BaseTX module port automatically matches the transmission speed of the attached device. To change the module port transmission speed:
Step 1 From the Speed: Requested/Actual drop-down list, select 10 Mbps, 100 Mbps, or Auto (autonegotiate).
The default is Auto. The 10-Mbps and Auto options are available only to the 10BaseT/100BaseTX module port.
Step 2 Click Apply.
When autonegotiation is selected on the module port, it automatically configures for full-duplex operation if the connected device also supports full duplex. If the attached device does not support full-duplex operation, the module port automatically configures to half-duplex operation.
To change the module port duplex mode:
Step 1 From the Duplex Mode: Requested/Actual drop-down list, select Half, Full, or Auto (autonegotiate).
The default for the 10BaseT/100BaseTX module port is Auto. The default for the 100BaseFX module port is Half.
Step 2 Click Apply.
To assign a name or description to a module port:
Step 1 In the Port Name/Description column, enter the port name or a description
(up to 20 characters) of how the module port is connected.
Step 2 Click Apply.
From the Switched Uplink Module Management Page, select the hub on which the module is installed, and click View to see the statistics of the module. The Detailed Switched Uplink Module Statistics Page (Figure 3-8) displays the module statistics. Table 3-7 lists the statistics displayed on the page.
Click Reset Switched Uplink Module Statistics to reset the statistics.
The hub manager does not automatically refresh the statistics shown on this page. Click Reload to refresh the statistics shown on this page.
Total Bytes Received | Total number of bytes received by the port. |
Total Packets Received | Total number of packets received by the port. |
Broadcast Packets Received | Total number of broadcast packets received by the port. |
Multicast Packets Received | Total number of multicast packets received by the port. |
CRC/Alignment Errors | Number of frames received by the port that are not an integral number of octets in length and do not pass the frame check sequence (FCS) test. |
Undersize Packets | Number of packets less than 64 bytes received by the port. |
Oversize Packets | Number of packets longer than 1518 bytes received by the port. |
Fragments | Number of SMT packets received by the port. |
Very Long Events | Number of packets that exceed the maximum length prescribed in IEEE 802.3. |
Collisions | Number of times the port and the connected device attempt to transmit at the same time. |
64-Byte Packets | Number of packets received in these lengths in bytes. |
You can interconnect up to four FastHub 400 models (a maximum of 96 ports) and manage that hub stack as a single logical repeater. To provide management to the stack, the stack must include at least one FastHub 412M or FastHub 424M hub. You can have a second management hub in the stack to act as a redundant stack manager in case the primary manager fails. For complete information and guidelines on stacking hubs, see "FastHub Stacks."
By default, each hub in the stack is connected to the network. Click GROUP on the menu bar to display the Group Management Page (Figure 3-9), isolate a hub from the network, and display the statistics of each hub in the stack.
This page displays the number of active hubs (groups) in the hub stack. Group 1 always represents the hub at the top of the stack, and the hub below Group 1 is Group 2, and so on. If you remove a hub from the stack, this page automatically renumbers the hubs accordingly.
If a hub stack has more than one management hub, the upper management hub in the stack is the primary management hub. The lower management hub is the secondary management hub.
To manage the hub stack, you can use the system information (such as the IP, CDP, and SNMP information) assigned to the primary management hub. The primary management hub also stores the port settings of each hub in the stack. If the primary management hub becomes inactive or is disconnected from the stack, the secondary management hub becomes the primary management hub and uses the same stack information.
By default, each hub in the stack is connected to the network. To isolate a hub from the network:
Step 1 Select Isolated from the Isolation Status drop-down list.
You can use the Isolated option if you need to troubleshoot a specific hub in the stack and do not want to affect the devices to which that particular hub is connected.
When you isolate a hub, keep the following considerations in mind:
Step 2 Click Apply.
To reconnect an isolated hub to the network:
Step 1 Select Connected from the Isolation Status drop-down list.
Step 2 Click Apply.
From the Group Management Page, select the hub, and click View to see the statistics of a single hub or a hub in the hub stack. The Detailed Group Statistics Page (Figure 3-10) for the hub (group) you selected displays the hub statistics. Table 3-8 lists the statistics displayed on the page.
Click Reset Group Statistics to reset the statistics.
The hub manager does not automatically refresh the statistics shown on this page. Click Reload to refresh the statistics shown on this page.
Packets | Total number of packets received by the port. |
Bytes | Total number of bytes received by the port. |
FCS Errors | Number of frame check sequence (FCS) errors indicating that frames of data are being corrupted during transmission. |
Alignment Errors | Number of alignment errors (caused if all bytes are not received whole) received by the port. |
Packets Too Long | Number of packets received by the port that exceed the maximum size for IEEE 802.3 frames. |
Short Events | Number of packets received by the port that are smaller than runts, which are smaller than the minimum size for IEEE 802.3 packets. |
Packets Too Short | Number of frames received by the hub that are smaller than the minimum size for IEEE 802.3 frames. |
Collisions | Number of times the hub and the connected device attempt to transmit at the same time. |
Late Events | Number of frames that experienced a collision late in transmission. |
Very Long Events | Number of packets that exceed the maximum length prescribed in IEEE 802.3. |
Data Rate Mismatches | Number of frames whose timing no longer matches the transmit frequency between the hub and the connected device. |
Autopartitions | Number of times the port automatically partitions the segments attached to it. |
Total Errors | Total number of errors received by the port. |
IP information identifies the hub (or managed hub stack) to the network and is necessary to manage the hub (or hub stack) through the hub manager, the CLI, or SNMP. This information is usually assigned to the management hub after it is installed and initially started up. (See the "Assigning IP Information to the Hub (FastHub 400M Models)" section.)
The IP Address field displays the current IP address of the hub. Click IP on the menu bar to display the IP Management Page (Figure 3-11) and change hub IP information.
 | Caution Changing the hub IP address on this page will end your hub manager session. To open a new session, enter the new IP address in the URL field if you are using Communicator (the Address field if you are using Internet Explorer). |
To manually change the hub IP information:
Step 1 Select User-Configured from the IP State drop-down list.
The default is User-Configured.
Step 2 Enter a new IP address for the hub in the IP Address field.
| Caution If you enter a new address and click Apply, the hub manager loses contact with the hub. Enter the new IP address of the hub in the Location field if you are using Communicator (the Address field if you are using Internet Explorer) to redisplay the hub manager. |
Step 3 Enter the subnet mask for the hub.
The subnet mask must be in the same subnet as the IP address.
Step 4 Enter the IP address of the default gateway.
The default gateway is the router that the hub uses to reach IP subnets other than the local subnet to which the hub is attached.
Step 5 Click Apply.
SNMP provides the means to manage and monitor the hub (or managed hub stack) through the Management Information Base (MIB) objects. Additional information about SNMP and MIB objects is provided in the "Overview of SNMP" section and the "Accessing the MIB Files through SNMP" section.
Click SNMP on the menu bar to display the SNMP Management Page (Figure 3-12) and check and change the SNMP settings.
Community strings serve as passwords for SNMP messages. You can assign community strings that enable the hub to validate SNMP read and read-write requests from a management station.
To change the SNMP Read community string:
Step 1 Enter up to 32 characters in the Read Community String field. The default is public.
Step 2 Click Apply.
To change the SNMP Write community string:
Step 1 Enter up to 32 characters in the Write Community String field. The default is private.
Step 2 Click Apply.
A trap manager is an SNMP management station that receives traps, which are the system alerts generated by the hub. If no trap manager is defined, no traps are issued. Up to four trap managers and their accompanying community strings can be entered.
To assign a trap manager:
Step 1 Enter the IP address and a community string (up to 32 characters) in the IP Address and Trap Manager Community String fields.
Step 2 Click Add.
To remove a trap manager:
Step 1 Select the manager from the Current list.
Step 2 Click Remove.
By default, the Enable Authentication Trap Generation check box is selected (meaning this parameter is enabled). When this check box is selected, the hub generates authentication traps that alert a management station to SNMP requests that are not accompanied by a valid community string. However, even if this parameter is enabled, no trap can be generated if no trap manager addresses are specified. (For information about trap manager settings, see the "Assigning or Changing Trap Managers" section). If you change this check box, click Apply to save your changes.
The hub generates linkDown traps when a port is suspended or disabled for these reasons:
The hub generates linkUp traps when a port is enabled for these reasons:
A write manager is an SNMP management station that can issue write requests to the hub. Up to four IP addresses of stations can be defined.
To assign a write manager:
Step 1 Enter the management station IP address in the IP Address field.
Step 2 Click Add.
To remove a write manager:
Step 1 Select the manager from the Current list.
Step 2 Click Remove.
By default, the hub is CDP-enabled. Click CDP on the menu bar to display the CDP Management Page (Figure 3-13) and check and change the CDP settings.
Step 1 From the Discovered Neighboring Devices list, select a device.
Step 2 Click one of these buttons:
By default, CDP is enabled on the hub. If you do not want the hub to exchange information with Cisco devices, you can disable CDP on the hub. To disable CDP:
Step 1 Deselect the Enable CDP check box.
Step 2 Click Apply.
To reenable CDP:
Step 1 Select the Enable CDP check box.
Step 2 Click Apply.
To change the global CDP settings for the hub:
If a neighboring device does not receive a CDP message before the hold time expires, the device drops this hub as a neighbor. The packet hold time should be higher than the packet transmission time.
Step 3 Click Apply.
Cisco periodically provides new firmware to implement enhancements and maintenance releases. New firmware releases can be downloaded from Cisco Connection Online (CCO), the Cisco Systems' customer web site available at the following URLs: www.cisco.com, www-china.cisco.com, and www-europe.cisco.com.
| Caution If you interrupt the transfer by turning the hub off and on, the firmware could get corrupted. For recovery procedures, see the "Recovering from Corrupted Firmware" section. |
If you want to upgrade the firmware of the management hub, click SYSTEM on the menu bar to display the System Configuration Page (Figure 3-14).
The console port on the hub provides terminal and PC access to the hub. After the hub is installed, be sure to configure the console port settings of the hub to match the settings of the terminal or PC.
These are the default settings of the hub console port:
If you change any of these settings, click Apply to save your changes.
You can change the number of seconds that the CLI can wait without activity before it times out. After timeout, you must reenter the password.
To change the inactivity timeout parameter:
Step 1 Enter the number of seconds (0, or 30 to 65500) in the CLI Inactivity Timeout field. The default is 0 (which means the console session does not time out).
Step 2 Click Apply.
Step 1 In the Server IP Address field, enter the IP address of the TFTP server on which the upgrade file is located.
Step 2 Enter the upgrade filename (up to 80 characters) in the Filename for Firmware Upgrades field.
Step 3 Select one of these download modes:
The default is Permanent.
Step 4 Click System TFTP Upgrade to download the upgrade file from the TFTP server to the hub.
Step 5 Click OK on the confirmation prompt.
| Caution If you interrupt the transfer by turning the hub off and on, the firmware could get corrupted. For recovery procedures, see the "Recovering from Corrupted Firmware" section. |
Posted: Wed Feb 24 11:00:28 PST 1999
Copyright 1989-1999©Cisco Systems Inc.