|
|
The following topics in this chapter describe the benefits and features of the Catalyst 1900 series Ethernet switches, also referred to as the Catalyst 1900 switches:
The Catalyst 1900 switches (shown in Figure 1-1) can improve network performance to the desktop, server, and backbone, especially in networks that use high-performance workstations and servers, use bandwidth-intensive applications, transfer large graphic, audio, and video files, and require access to the same network resources and the Internet.
These switches have up to 25 10BaseT switched Ethernet ports (including the AUI switch port on the back panel), each port providing users or groups of users dedicated 10-Mbps bandwidth to resources within the network. These ports connect to other 10BaseT-compatible devices, such as single workstations and 10BaseT hubs. The switches also have two 100BaseT switched ports for delivering maximum performance to high-speed servers and to backbone switches and routers.
Each Catalyst 1900 switch is designed for plug-and-play operation, requiring only that you assign basic IP information to the switch and connect it to the other devices in your network. If you have specific network needs, you can also configure the switch through its various management interfaces. The switch can be configured and monitored individually or as part of a switch cluster that is managed by a Catalyst 2900 series XL or Catalyst 3500 series XL command switch.
In Figure 1-1, switches shipped with the standard software features (listed in Table 1-1) are indicated by "-A" in the part number. Switches shipped with the Cisco Catalyst 1900/2820 Enterprise Edition Software are indicated by "-EN." For information about the enterprise edition software features (such as support for up to 1005 virtual LANs (VLANs); VLAN, Inter-Switch Link (ISL), and Asynchronous Transfer Mode (ATM) LAN emulation (LANE) trunk connections; ATM permanent virtual connections (PVCs); Fast EtherChannel connections; and TACACS+ authentication), refer to the Catalyst 1900 Series and Catalyst 2820 Series Enterprise Edition Software Configuration Guide.
| Feature | Description |
|---|---|
| Performance and Configuration |
|
| |
| |
| |
| |
| |
| |
| |
| |
| Management |
|
| |
| |
| |
| |
|
The front panel of a Catalyst 1900 switch provides 12 or 24 10-Mbps and two 100-Mbps switched ports (Figure 1-2) to connect to other network devices and a set of LEDs and a Mode button for monitoring the switch and its ports (Figure 1-3).
The 10BaseT network ports on the switch (1x through 12x or 1x through 24x) use standard RJ-45 connectors. These ports can connect to 10BaseT-compatible devices, such as individual workstations and hubs, with Category 3, 4, or 5 cabling. Using this type of cabling, the distance between the switch and the attached device can be up to 100 meters. For connection information, see the "Connecting to the Switched 10BaseT Ports" section.
Depending on the model, the switch can have the following high-speed network ports:
The model with the 100BaseTX ports (Ax and Bx) use standard RJ-45 connectors. These ports can connect to 100BaseTX-compatible servers, hubs, switches, and routers, with Category 5 cabling. Using this type of cabling, the distance between the switch and the attached device can be up to 100 meters. For connection information, see the "Connecting to the Switched 100BaseTX Ports" section.
The model with one 100BaseFX port (A) uses a duplex square connector (SC). This port can connect to other 100BaseFX-compatible devices with 50/125- or 62.5/125-micron multimode fiber-optic cabling. For connection information, see the "Connecting to the Switched 100BaseFX Port" section.
The fiber-optic connections between the switch and the attached device can be as follows:
The model with two fiber-optic ports (A and B) use MT-RJ connectors and have a fiber-optic wavelength of 1300 nanometers. To connect each fiber-optic port on the switch to an SC or ST port on a 100BaseFX-compatible device on your network, you must use the appropriate MT-RJ fiber-optic patch cable. You can order MT-RJ patch cables from your cable vendor, or you can order these cables from Cisco:
For connection information, see the "Connecting to the Switched 100-Mbps Fiber-Optic Ports" section.
You can use the LEDs to monitor switch activity and performance by using the Mode button to select the modes in which the port LEDs operate (Figure 1-3).
The colors of the system status (SYSTEM) LED show that the switch is receiving power and functioning properly (Table 1-2).
| Color | System Status |
|---|---|
Off | Switch is not powered up. |
Solid green | Switch is operating normally. |
Solid amber | Switch is receiving power, but might not be functioning properly. One or more power-on self-test (POST) errors occurred. The Management Console Logon Screen message identifies which nonfatal test(s) failed. Note If a fatal error occurs, the switch is not operational, and no message is displayed. (See the "Powering Up and Using POST to Test the Switch" section and the "Understanding POST Failures" section.) |
The colors of the redundant power system (RPS) LED show the status (Table 1-3) of a connected Cisco RPS (model PWR600-AC-RPS). For more information about the RPS, see the "Power Connectors" section.
| Color | RPS Status |
|---|---|
Off | RPS is off or is not installed. |
Solid green | RPS is operational. |
Blinking green | RPS and the switch AC power supply are both powered up. Note This is not a recommended configuration. For more information, see the "Power Connectors" section. |
Solid amber | RPS is connected, but is not functioning properly. One of the power supplies in the RPS could be powered down, or a fan in the RPS could have failed. |
Each port has an LED above it. These LEDs, as a group or individually, display information about the switch and about individual ports (Table 1-4).
| Mode | LED | Determines... |
|---|---|---|
Port status (default) | STAT | Status of individual ports |
Bandwidth utilization | UTL | Percentage of the switch total bandwidth being used at any one time |
Full-duplex operation | FDUP | Which ports are operating in half- or full-duplex mode |
Pressing the Mode button on the front panel changes the mode of the port LEDs. The STAT, UTL, and FDUP LEDs show which mode is active (Table 1-5). The selected mode remains on approximately for 30 seconds before returning to the default mode (port status). You can change the default mode from the Console Settings Menu.
| For this Mode... | Push the Mode Button Until... |
|---|---|
Port status | Only the STAT LED is on. |
Bandwidth utilization | Only the UTL LED is on. |
Full-duplex operation | Only the FDUP LED is on. |
This is the factory default mode. The colors of the LEDs above the ports show the status of the corresponding ports (Table 1-6).
| Color | Port Status |
|---|---|
Off | No link. |
Solid green | Link operational (with no link activity). |
Flashing green | Link operational (with activity). |
Alternating green | Link fault. Error frames can affect connectivity. Excessive collisions and cyclic redundancy check (CRC), alignment, and jabber errors are monitored for a link-fault indication. |
Solid amber | Port is not forwarding. This could be because the port was disabled by management, suspended because of an address violation, or suspended by Spanning-Tree Protocol (STP) because of network loops. |
In the UTL mode, the port LEDs as a group show the switch bandwidth being used at any one time (see Figure 1-4 and Figure 1-5). The more LEDs that are lit, the higher the bandwidth being used. The peak utilization is recorded in the bandwidth-capture interval, described in the "Bandwidth Usage Report" section.
The colors of the LEDs in FDUP mode show which 10BaseT and 100BaseT ports are operating in full-duplex mode (Table 1-7).
| Color | Full-Duplex |
|---|---|
Off | Half-duplex mode is operational. |
Solid green | Full-duplex mode is operational. |
The rear panel of a Catalyst 1900 switch has an AC power connector, a console port, a redundant power system (RPS) connector, and a switched AUI port (see Figure 1-6).
![]() | Warning Attach only the Cisco RPS (model PWR600-AC-RPS) to the RPS connector. |
You can provide power to the switch either by using the switch internal AC power supply or by connecting the optional Cisco 600W AC Redundant Power System (RPS) to the RPS connector on the switch.
The internal power supply is an autoranging unit that supports input voltages of 90 to 127 VAC or 200 to 250 VAC. To use the internal power supply, connect one end of the supplied power cord to the AC power connector on the switch and the other end of the power cord to an AC power outlet.
For information about the RPS LED, see the "Redundant Power Supply LED" section. For complete information about the RPS, refer to the Cisco RPS documentation.
To configure and manage the switch through the menu-based management and diagnostic consoles and the command-line interface (CLI), you can connect the console port to a management station or modem with the supplied RJ-45-to-RJ-45 rollover console cable and an appropriate adapter. For additional information, see the "Connecting to the Console Port" section.
You can connect the switched AUI port to an Ethernet transceiver, which is then connected to a 10-Mbps Ethernet device through the following cable types:
For connection information, see the "Connecting to the Switched AUI Port" section.
You can use the default settings shipped with the Catalyst 1900 switch, or you can customize the switch configuration through the management options described in this section. The Catalyst 1900 Switch Manager is the easiest interface to use for basic configuration and monitoring tasks. To perform all the configuration and monitoring tasks, use the management console, the SNMP, or the command-line interface (CLI).
If your switch is or will be part of a switch cluster, you can also configure and monitor it from the Cluster Management applications of a cluster command switch.
Access to the management console or CLI requires a direct connection to the switch console port or a Telnet session. Access to the Catalyst 1900 Switch Manager, Cluster Management applications, or SNMP requires a connection to one of the switch network ports. For more information about accessing the management interfaces, see the "Accessing the Management Interfaces" section.
This section describes the hardware and software requirements and provides the following overviews:
This section describes the requirements and recommended configurations for using the Catalyst 1900 Switch Manager and the management console.
The following operating systems are supported for web-based management:
Table 1-8 lists the configurations that yield the best results for web-based management:
| Operating System | Processor Speed | DRAM | Number of Colors | Resolution | Font Size |
|---|---|---|---|---|---|
Windows NT 4.0 | Pentium 300 MHZ | 128 MB | 65536 | 1024 x768 | Small |
SunOS 5.6 | Sparc 333 MHz | 128 MB | Most colors for applications | --- | Small (3) |
To use the management console, you must have terminal emulation software (such as ProComm, HyperTerminal, tip, or minicom) installed on your management station.
To use the Catalyst 1900 Switch Manager, you must have one of these web browsers installed on your management station:
| Browser | Minimum Version | Supported Versions |
|---|---|---|
4.5 | 4.5, 4.51, 4.61 | |
4.01a | 4.01a, 5.0 |
For information about how to configure your browser for web-based management, see the "Accessing the Switch Manager" section.
As with previous Catalyst 1900 releases, you can configure and monitor the switch as an individual device in your network. To do this, you must assign it an IP address and password and then use the options available from the Catalyst 1900 Switch Manager, management console, SNMP, or the CLI. (See "Configuring and Monitoring from the Switch Manager," and "Configuring and Monitoring from the Management Console.")
The switch can also be a member of a switch cluster. A cluster is a group of connected switches that are managed as a single entity. A cluster has a command switch and member switches. The Catalyst 1900 switches can only be member switches. Certain models of the Catalyst 2900 XL switches can be command switches, and all models of the Catalyst 3500 XL switches can be command switches.
The command switch is the central management point used to configure and monitor the switch cluster. All communication with member switches is through the command switch IP address. Clustering can simplify your network management tasks. For example, from a command switch, you can manage and monitor member switches regardless of their geographic location, and you can perform cluster-wide firmware upgrades.
Not all Catalyst 1900 configuration and monitoring options are available from the Cluster Management applications of the command switch; however, you can access the Catalyst 1900 management interfaces (switch manager, management console, and CLI) from the command switch at any time.
Each switch in a cluster can belong to only one cluster at a time. The switches in a cluster can be in the same location, or they can be distributed across a network. The Catalyst 1900 switches can be connected to a cluster in a star or daisy-chain topology through copper or fiber-optic cables.
To configure and monitor a Catalyst 1900 switch as a cluster member, the following requirements must be met:
When the Catalyst 1900 switch joins a cluster, the following configuration settings change:
![]() | Caution Do not use "@es" in the community strings you define for the switch. When the switch joins a cluster, any community string containing "@es" is deleted. |
For complete information about cluster management and membership, refer to the Cisco IOS Desktop Switch Software Configuration Guide, Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
The Catalyst 1900 Switch Manager (hereafter referred to as the switch manager) is a web-based, graphical user interface for basic switch configuration and monitoring. Using the switch manager, you can configure and monitor the switch from anywhere on your intranet.
Each switch manager page
For information about using the switch manager, see "Configuring and Monitoring from the Switch Manager."
Table 1-10 lists the configuration settings, including default values, available from the switch manager.
| Feature | Default Setting | Switch Manager Page | |
|---|---|---|---|
| Management | |||
| IP address, subnet mask, and default gateway | 0.0.0.0 | |
| Cisco Discovery Protocol (CDP) | Enabled | |
| Performance Tuning | |||
| Switching mode | FragmentFree | |
| Enhanced congestion control on 10BaseT ports | Disabled | |
| Enhanced congestion control on 100BaseT ports | Disabled | |
| Duplex mode on 10BaseT ports | Half duplex | |
| Half-duplex back pressure on 10BaseT ports | Disabled | |
| Duplex mode on switched 100BaseFX ports | Half duplex | |
| Duplex mode on switched 100BaseTX port | Autonegotiate | |
| Flooding/Traffic Control |
|
| |
| Broadcast storm control | Disabled | |
| Store-and-forward on multicast | Disabled | |
| Network port | None | |
| Cisco Group Management Protocol (CGMP) | Enabled | |
| Flooding unknown unicast packets | Enabled | |
| Flooding unregistered multicast packets | Enabled | |
| Network Redundancy/Fault Tolerance |
|
| |
| Spanning-Tree Protocol (STP) | Enabled | |
| Port Fast mode on 10BaseT ports | Enabled | |
| Port Fast mode on 100BaseT ports | Disabled | |
| Diagnostics |
|
| |
| Port monitoring (SPAN) | Disabled | |
| Remote monitoring (RMON) | Enabled | --- |
| Usage reports | --- | |
| Security |
|
| |
| Password | None | |
| Action on address violation | Suspend | |
| Address security | Disabled | |
| Trap managers | None | |
| Write (read/write) managers | None | |
| Community strings | Public/Private | |
| Upgrades |
|
| |
| Firmware | --- | |
For procedures on how to reset all switch settings to the factory defaults, see the "System Configuration Menu" section or the "Resetting the Switch to the Factory Defaults" section.
The management console is a menu-driven interface for configuring and monitoring the switch. If your management station is directly connected to the switch console port, you can use the management console even when the network is down because your direct connection to the console bypasses the network and communicates directly with the switch.
For information about using the management console, see "Configuring and Monitoring from the Management Console."
Table 1-11 lists the configuration settings, including default values, available from the management console.
| Feature | Default Setting | Console Menu | |
|---|---|---|---|
| Management | |||
| IP address, subnet mask, and default gateway | 0.0.0.0 | |
| Cisco Discovery Protocol (CDP) | Enabled | |
| Performance Tuning | |||
| Switching mode | FragmentFree | |
| Enhanced congestion control on 10BaseT ports | Disabled | |
| Enhanced congestion control on 100BaseT ports | Disabled | |
| Duplex mode on 10BaseT ports | Half duplex | |
| Half-duplex back pressure on 10BaseT ports | Disabled | |
| Duplex mode on 100BaseFX port | Half duplex | |
| Duplex mode on 100BaseTX ports | Autonegotiate | |
| Flooding/Traffic Control |
|
| |
| Broadcast storm control | Disabled | |
| Network port | None | |
| Cisco Group Management Protocol (CGMP) | Enabled | |
| Overlapping bridge groups | Disabled | |
| Store-and-forward on multicast | Disabled | |
| Flooding unknown unicast packets | Enabled | |
| Flooding unregistered multicast packets | Enabled | |
| Network Redundancy/Fault Tolerance |
|
| |
| Spanning-Tree Protocol (STP) | Enabled | |
| Port Fast mode on 10BaseT ports | Enabled | |
| Port Fast mode on 100BaseT ports | Disabled | |
| Diagnostics |
|
| |
| Port monitoring (SPAN) | Disabled | |
| Remote monitoring (RMON) | Enabled | --- |
| Usage reports | --- | Port Status Report |
| Security |
|
| |
| Password | None | |
| Action on address violation | Suspend | |
| Address security | Disabled | |
| Trap managers | None | |
| Write (read/write) managers | None | |
| Community strings | Public/Private | Network Management (SNMP) READ Configuration Menu |
| Upgrading |
|
| |
| Firmware | --- | |
For procedures on how to reset all switch settings to the factory defaults, see the "System Configuration Menu" section or the "Resetting the Switch to the Factory Defaults" section.
For switches shipped or upgraded with the Cisco Catalyst 1900/2820 Enterprise Edition Software, you can use the command-line interface (CLI) to access the configuration options and perform the same configuration and monitoring tasks available through the Catalyst 1900 Switch Manager and management console. You can also perform privileged configuration and monitoring tasks available only through the CLI and SNMP.
For complete information about the CLI, refer to the online-only Catalyst 1900 Series and Catalyst 2820 Series Command Reference.
You can configure and monitor the switch by accessing the Management Information Base (MIB) variables through Simple Network Management Protocol (SNMP), an application-layer protocol designed to facilitate the exchange of management information between network devices. The switch supports a comprehensive set of MIB objects, including four Remote Monitoring (RMON) groups.
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 switch. You can compile the switch 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 switch 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-7 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.
The SNMP manager uses information in the MIB files to perform the operations described in Table 1-12.
| 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. |
RMON is enabled by default on the switches and is not displayed on the Catalyst 1900 Switch Manager or management console. The switch supports four RMON groups (Table 1-13) as defined in RFC 1757. You can obtain information about the four supported groups by using any SNMP management application.
| Group Name | Description |
|---|---|
Statistics | This group collects utilization and error statistics for the monitored switch. Statistics include information about collisions, cyclic redundancy checks (CRCs) and alignment; undersized or oversized packets, jabber, fragments, broadcast, multicast, and unicast messages; and bandwidth utilization. For example, you could use this group to determine how many error packets have been seen on a given port. Statistics from this group can be used by the history group to record historical views of network performance. A statistics row is established by default for each switch port. |
History | This group takes periodic samples from the statistics section and stores them for later retrieval. This sampling includes information such as utilization, error counts, and packet counts. This information can be used to establish baseline information regarding network activity. You can define the intervals you want to record information for, and you can define how many of the samples are to be stored. Note RMON statistics gathering has a maximum limit of 540 history tables that can be allocated among all switch ports. |
Alarm | This group generates alarms according to user-defined thresholds. You could, for example, configure RMON to generate an alarm when alignment errors on a port exceeded a predefined limit. Rising and falling thresholds can be defined, and the events group can generate traps and automated responses based on the alarms. |
Event | This group sends traps (events) to the management station based on information (alarms) received from the alarm group. The time and date are recorded with each logged event. You can use the events group to create customized reports that are based on alarm types. |
As your network users compete for network bandwidth, it takes longer to send and receive data. Network performance can degrade for reasons such as:
You can design your network to increase the bandwidth available to your network users by using one or more of the following methods:
This section provides network configuration examples for using the Catalyst 1900 switches in your network to create dedicated network segments and interconnecting the segments through its high-speed ports:
Figure 1-8 illustrates a standard configuration in which bandwidth is shared by all attached devices. The nodes (workstations, hubs, and servers) in the workgroup are divided into smaller groups to increase the bandwidth available to each of them and to improve server response time. Grouping servers in a centralized location can provide benefits such as security and easier maintenance.
Network resources (such as web and mail servers) are connected to the 100BaseT ports on the Catalyst 1900 switch, allowing 100-Mbps throughput to users when needed. When the switch and server ports are configured for full-duplex operation, the links provide 200 Mbps of bandwidth.
Bandwidth-intensive workstations, such as computer-aided design (CAD) users or other power users, are connected to the switch 10BaseT ports for their own 10-Mbps bandwidth access to servers. Single workstations, configured for full-duplex operation, receive 20 Mbps of dedicated bandwidth from each switched port.
Other workstations are connected to 10BaseT hubs, which provide 10-Mbps shared bandwidth to users with multiple workstations or to workgroups that require minimal network bandwidth. These workstations share the available 10-Mbps of bandwidth available from the switched link. Because hubs run only in half-duplex, each connected port provides 10 Mbps of bandwidth.
Connecting a router to a 100BaseT switch port provides multiple, simultaneous links to the Internet through one line.
Figure 1-9 illustrates a network configuration that uses the 100BaseT ports on multiple Catalyst 1900 switches to interconnect workgroups and network resources. All workgroups have full access to the network resources (such as a Dynamic Host Configuration Protocol (DHCP)/Bootstrap Protocol (BOOTP) server or an IPTV multicast server).
You optimize your network performance by placing workstations on the same logical segment as the servers they access most often. This configuration reduces the amount of traffic that travels over a network backbone, which is a high-bandwidth (such as Fast Ethernet) connection between the segments. A backbone is required if numerous users access the servers.
When the 100BaseT ports are configured for full-duplex operation, they provide a total of 200 Mbps of bandwidth on each switch port. Switched 10BaseT ports configured for full-duplex operation provide 20 Mbps of bandwidth to workstations.
For increased performance to the workstations, replace the hubs shown in Figure 1-9 with Catalyst 1900 switches. In place of the Catalyst 1900 switches, you can add Catalyst 2900 XL or Catalyst 3500 XL switches and form a switch cluster of Catalyst 1900, Catalyst 2900 XL, and Catalyst 3500 XL switches. A Catalyst 3500 XL switch can be the command switch, the central point of network management. As your network grows, you can add more switch clusters.
Figure 1-10 illustrates a Fast Ethernet collapsed-backbone configuration in which all segments and subnetworks are connected to a single device, such as a hub, switch, or router, to form the enterprise internetwork. A collapsed backbone network is easy to manage and troubleshoot, as it provides a single point for monitoring and controlling the network.
Two different workgroups, perhaps located in different buildings, are connected by Catalyst 1900 switches connected to a 100BaseT backbone switch or router (such as a Catalyst 5000 switch or Cisco 7000 router). In full-duplex mode, 200 Mbps of bandwidth is available to both Catalyst 1900 switches.
The distance between each Catalyst 1900 switch and the backbone switch or router can be increased to 2 kilometers by using fiber-optic ports in full-duplex mode. The Catalyst 1900 models---WS-C1924C, WS-C1912C, and WS-C1924F---provide one duplex SC port or two fiber-optic MT-RJ ports. Connections through the 100BaseTX switch ports with Category 5 cabling can be up to a distance of 100 meters.
Figure 1-11 illustrates how network redundancy provides two advantages:
A 100-Mbps (200 Mbps in full-duplex) redundant backbone is created by connecting Catalyst 1900 switches to 100BaseT backbone switches or routers, such as Catalyst 5000 switches or Cisco 7000 routers. Each Catalyst 1900 switch connects to the two backbone devices, shown in the top-left and top-right corners, in a redundant configuration. If connectivity is lost to one of the backbone routers or switches, the network uses the redundant connection.
Spanning-Tree Protocol, available only on switches, ensures that only one of the two connections from each switch is active (the primary link), ensuring that there are no loops in the network paths. If the primary link fails, the secondary link becomes active.
A system of routers, switches, and hubs can be combined to create a high-performance network that extends beyond the main office LAN to connect to branch offices, remote sites, mobile users, and the Internet. Figure 1-12 is an example of an extended network.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Oct 28 19:57:36 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.