Documente Academic
Documente Profesional
Documente Cultură
Connecting to the Console Port (FastHub 400M Models) section on page 2-14
Assigning IP Information to the Hub (FastHub 400M Models) section on page 2-16
Accessing the FastHub 400 Series Hub Manager section on page 2-21
Note Procedures for changing the configuration settings and detailed descriptions of the
Figure 3-1
3-2
14524
When you enter information in fields and select or deselect check boxes, the changes
are saved and immediately take effect after you click Apply.
When you add items to or remove them from lists, the changes take effect immediately.
It is not necessary to click Apply.
Note Wait approximately 30 seconds before turning off the hub to be sure the changes are
saved.
changing the settings. When you are using the hub manager, click Help from the Home
Page to access this information online.
3-4
Figure 3-2
Home Page
HOME
15364
Procedures and
detailed field
descriptions are
provided here.
Step 2
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 on page 4-13.
3-6
Hub Image
HOME
Procedures and
detailed field
descriptions are
provided here.
Note The hub image on the Home Page does not display both the last fixed 10/100
network port and the uplink port (which are ports 12x and 12 on the FastHub 412 models
or ports 24x and 24 on the FastHub 424 models). The last fixed port on the hub image
represents both ports 12x and 12 or ports 24x and 24, depending on the model.
In Figure 3-3, the hub image shows that a 10BaseT/100BaseTX switched uplink module is
installed in the hub.
any of the hub ports are operating at 10 or 100 Mbps, check the actual 10 and 100 LEDs on
the hub, or click the specific port on the image to display the settings on the Port
Management Page.
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 on page 4-8).
The colors of the RPS LED on the hub image show the RPS status (Table 3-1).
Table 3-1
3-8
LED Color
Description
Blue (off)
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.
Note The hub image on the Home Page does not display both the last 10/100 network port
and the uplink port (ports 12x and 12 on the FastHub 412 models or ports 24x and 24 on
the FastHub 424 models). The LED above port 12 or 24 on the hub image represents both
ports 12x and 12 or ports 24x and 24.
Table 3-2
Port status
100BaseT connections
Table 3-3
LED Color
Port Status
Blue (off)
No link.
Solid green
Link operational.
Solid amber
Port Speed
Blue (off)
Green
LED Color
Description
10/100 Module Port Status (left LED above the module port)
Blue (off)
No link.
Solid green
Flashing green
10/100 Module Port Duplex Mode (middle LED above the module port)
Blue (off)
Solid green
10/100 Module Port Speed (right LED above the module port)
Blue (off)
Operating at 10 Mbps.
Solid green
Table 3-5
LED Color
100BaseFX Module Port Status (left LED above the module port)
Blue (off)
No link.
Solid green
10/100 Module Port Duplex Mode (right LED above the module port)
3-10
Blue (off)
Solid green
Otherwise, if a hub in the stack is powered down, the stack image shows one less hub in the
stack even if the hub is still interconnected to the stack. However, the image does not show
which specific hub is no longer active. You must check the actual hub stack to find out.
If the stack image does not change after you have removed or added a hub to the stack, click
the browser Reload button to refresh the stack image. Be sure you set the caching of pages
to Every time in Netscape Communicator or Every visit to the page in Microsoft Internet
Explorer.
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 on page 3-27 and Appendix C, FastHub Stacks.
Figure 3-4
17757
Note In Figure 3-4, the top hub on the stack image is a management hub, as indicated by
the label Master, and is the primary management hub. The third hub in the stack is the
secondary management hub. The second and fourth hubs are not management hubs.
A 10BaseT/100BaseTX switched uplink module is installed in the second hub, and a
100BaseFX switched uplink module is installed in the fourth.
3-12
Click Cisco Connection Online (CCO) to display the CCO home page
(www.cisco.com), which contains links to the support sites for downloading the latest
software and displaying the latest Cisco documentation.
Click Technical Assistance Center (TAC) to open a new message composition
window to send e-mail to TAC (tac@cisco.com). You can also phone TAC at
800-553-2447 or 408-526-7209.
Click HTML Interface Development Group to open a new message composition
window to send e-mail to the hub manager development group (cs-html@cisco.com).
changing the settings. When you are using the hub manager, click Help from the Port
Management Page to access this information online.
3-14
Figure 3-5
Displays the
Switched Uplink Module
Management page.
15368
Procedures and
detailed field
descriptions are
provided here.
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.
Link Down
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:
3-16
Partitioned
Not Partitioned
From the Speed: Requested/Actual drop-down list, select 10 Mbps, 100 Mbps,
or Auto (autonegotiate). The default is Auto.
Step 2
Click Apply.
Note If the other device does not autonegotiate, the hub port automatically negotiates to
10 Mbps.
Step 2
Click Apply.
15369
Procedures and
detailed field
descriptions are
provided here.
3-18
Table 3-6
Packets
Bytes
FCS Errors
Alignment Errors
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.
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
Autopartitions
Total Errors
changing the settings. When you are using the hub manager, click Help on the Switched
Uplink Module Management Page to access this information online.
For more information about the switched uplink modules, see Appendix D, Switched
Uplink Modules.
3-20
Figure 3-7
Shows on which
hub in the stack
the module is
installed.
15367
Procedures and
detailed field
descriptions are
provided here.
Shows when the module port is operating at halfor full-duplex mode. Autonegotiation allows the
module port to match the duplex mode of the
device to which it is connected.
Shows when the module port is operating at 10 or 100 Mbps.
Autonegotiation allows the 10BaseT/100BaseTX module port
to match the speed of the device to which it is connected.
Speed negotiation is not applicable to the 100BaseFX module port.
Note Figure 3-7 shows the Switched Uplink Module Management Page. This example
shows that hubs 1, 3, and 4 have modules installed. Hub 2 is powered down but still
interconnected to the stack.
Step 2
Click Apply.
A linkDown trap is sent to the management station if you configured an SNMP
manager.
Step 2
Click Apply.
A linkUp trap is sent to the management station if you configured an SNMP
manager.
Link Down
3-22
10BaseT/100BaseTX
100BaseFX-SC
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.
Note If the other device does not autonegotiate, the hub port automatically negotiates to
10 Mbps. Speed negotiation does not apply to the 100BaseFX switched uplink module.
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.
Note If the other device does not autonegotiate, the hub port automatically negotiates to
half duplex.
Step 2
Click Apply.
3-24
Figure 3-8
17609
Procedures and
detailed field
descriptions are
provided here.
Table 3-7
3-26
CRC/Alignment Errors
Undersize Packets
Oversize Packets
Fragments
Collisions
64-Byte Packets
65-127-Byte Packets
128-255-Byte Packets
256-511-Byte Packets
512-1023-Byte Packets
1024-1518-Byte Packets
changing the settings. When you are using the hub manager, click Help from the Group
Management Page to access this information online.
Figure 3-9
Procedures and
detailed field
descriptions are
provided here.
15362
Note Figure 3-9 shows the Group Management Page when there are at least two hubs 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.
Note Every hub in the stack must be powered up for it to be displayed on the Home Page
and on the Group Management Page. Otherwise, if a hub in the stack is powered down, the
stack image shows one less hub in the stack even if the hub is still interconnected to the
stack. However, the image does not show which specific hub is no longer active. You must
check the actual hub stack to find out.
If the stack image does not change after you have removed or added a hub to the stack, click
the browser Reload button to refresh the stack image. Be sure you set the caching of pages
to Every time in Netscape Communicator or Every visit to the page in Microsoft Internet
Explorer.
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.
If a stack has only one management hub and another management hub is added to the
stack, the system information from the management hub that has the longest system-up
time is used by the topmost management hub. This happens if the new management hub
is added either above or below the preexisting management hub.
If you replace the only management hub in the stack with a different management hub,
the stack will use the settings of the newly installed management hub.
Note If you have a stack that has two management hubs and you remove one management
hub from the stack, it will have the same IP address as the stack. Avoid IP conflict by
changing the IP address of the removed management hub before you reuse it and connect
it to another hub stack in the network.
3-28
If you isolate a hub in the stack, the hubs above and below the isolated hub
will still communicate with each other as long as the isolated hub is
interconnected to the stack.
If you isolate a hub in the stack other than the primary management hub, and
your management station is not connected to the isolated hub, the Home Page
will display the stack image, including the isolated hub. You can still manage
the stack, including the isolated hub, from the hub manager.
If your hub stack has only one management hub and you isolate that
management hub, the Home Page will display only the image of the
management hub (not the stack image). You will not be able to manage the
stack from the hub manager.
Note If you do not isolate a hub and if you keep it interconnected to the stack
but only power down that hub, the hubs above and below that powered-down hub
will still communicate with each other. However, you will not be able to manage
that hub, and it will not be displayed from the hub manager.
Step 2
Click Apply.
Step 2
Click Apply.
15363
Procedures and
detailed field
descriptions are
provided here.
3-30
Table 3-8
Packets
Bytes
FCS Errors
Alignment Errors
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.
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
Autopartitions
Total Errors
hub from the stack, it will have the same IP address as the stack. Avoid IP conflict by
changing the IP address of the removed management hub before you reuse it and connect
it to another hub stack in the network. For complete information and guidelines on
managing hub stacks, see the Managing the Hub Segments section on page 3-27 and the
Managing a Hub Stack section on page C-6.
Note This section provides detailed information about this page and procedures on
changing the settings. When you are using the hub manager, click Help on the IP
Management Page to access this information online.
Figure 3-11
IP Management Page
HOME
Procedures and
detailed field
descriptions are
provided here.
3-32
15366
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
Note Use the BootP Get IP option if you want the BootP (Boot Protocol) server
to assign the IP information. The hub must be connected to a network that has a
BootP server. The BootP Get IP option becomes active when you restart the hub.
If this option is enabled, you cannot manually change IP information.
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
Step 4
Step 5
Click Apply.
changing the settings. When you are using the hub manager, click Help on the SNMP
Management Page to access this information online.
Figure 3-12
Up to four management
stations can receive traps
(alerts of certain events)
generated by the hub.
Use the traps to monitor
the hub.
15370
3-34
Step 2
Click Apply.
Step 2
Click Apply.
Step 2
Click Add.
Step 2
Click Remove.
The hub generates linkUp traps when a port is enabled for these reasons:
Presence of linkbeat.
Management intervention enables the port.
Step 2
Click Add.
3-36
Step 1
Step 2
Click Remove.
changing the settings. When you are using the hub manager, click Help on the CDP
Management Page to access this information online.
Figure 3-13
Allow or not
allow exchanging
CDP messages
between the hub
and other
Cisco devices.
15361
Procedures and
detailed field
descriptions are
provided here.
Step 2
Step 2
Click Apply.
To reenable CDP:
3-38
Step 1
Step 2
Click Apply.
In the Packet Hold Time field, enter the number of seconds (between 10 and 255)
that a neighboring device retains the CDP neighbor information received from
this hub. The default setting is 180 seconds.
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 2
Step 3
Click Apply.
respond to commands for approximately 1 minute. This is normal and correct. Do not turn
off the hub. The hub then resets and begins using the new firmware.
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 on page 4-10.
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).
Note This section provides detailed information about this page and procedures on
changing the settings. When you are using the hub manager, click Help on the System
Configuration Page to access this information online.
3-40
Procedures and
detailed field
descriptions are
provided here.
15371
Figure 3-14
If you change any of these settings, click Apply to save your changes.
3-42
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.
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
Click System TFTP Upgrade to download the upgrade file from the TFTP
server to the hub.
Step 5
Note When you download the firmware permanently to Flash memory, the hub does not
respond to commands for approximately 1 minute. This is normal and correct. Do not turn
off the hub. The hub then resets and begins using the new firmware.
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 on page 4-10.
3-44