Title Page CSX200 and CSX400 User’s Guide
Notice Cabletron Systems reserves the right to make changes in speciÞcations and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, Þrmware, or software described in this manual is subject to change without notice.
AppleTalk, Apple, Macintosh, and TokenTalk are registered trademarks; and Apple Remote Access and EtherTalk are trademarks of Apple Computer, Inc. SmartBoost is a trademark of American Power Conversion ST is a registered trademark and C++ is a trademark of AT&T Banyan and VINES are registered trademarks of Banyan Systems, Inc. cisco, ciscoSystems, and AGS+ are registered trademarks; and cBus, cisco Router, CRM, IGS, and MGS are trademarks of cisco Systems, Inc.
ANNEX, ANNEX-II, ANNEX-IIe, ANNEX-3, ANNEX-802.5, MICRO-ANNEX-XL, and MICROANNEX-ELS are trademarks of Xylogics, Inc. MAXserver and Xyplex are trademarks of Xyplex, Inc. Restricted Rights Notice (Applicable to licenses to the United States Government only.) 1. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Cabletron Systems, Inc.
iv
Contents Chapter 1 Introduction HSIM-W6 and HSIM-W84 ........................................................................................... 1-2 Using the CSX 200 and CSX400 UserÕs Guide .......................................................... 1-2 Related Manuals............................................................................................................ 1-3 Software Conventions ..................................................................................................
Contents WAN Logical View Window Fields..................................................................... 3-6 Changing WAN Logical Settings ......................................................................... 3-6 Chapter 4 Bridging Bridging Basics .............................................................................................................. 4-1 About Transparent Bridging.................................................................................
Contents Changing Path Cost...................................................................................... 4-42 Filtering Database ....................................................................................................... 4-42 Filtering Database Window Fields .................................................................... 4-45 ConÞguring the Filtering Database................................................................... 4-46 Altering the Aging Time ...........................
Contents Token Ring Physical Status Fields .............................................................. 4-87 Using the Interface ConÞguration Window ............................................................ 4-89 DeÞning the Bridge Method............................................................................... 4-90 Setting the Bridge Method.................................................................................. 4-91 DeÞning the Protocol Transmission .....................................
Chapter 1 Introduction How to use this guide; related guides; software conventions; getting help; CSX200 and CSX400 firmware versions Welcome to the Cabletron SystemsÕ SPECTRUM Element Manager for the CSX200 and CSX400 UserÕs Guide. We have designed this guide to serve as a simple reference for using SPECTRUM Element Manager for the CSX200 and CSX400. SPECTRUM Element Manager provides management support for both the CyberSWITCH CSX200 and CyberSWITCH CSX400 stand-alone LAN-to-WAN access devices.
Introduction simultaneous communication, or the pair can be conÞgured to provide redundant channels if desired. Connectivity is available for Point to Point Protocol (PPP), as well as Frame Relay and leased lines. NOTES It is also important to note a Windows 95- and NT-based utility called QuickSET was shipped with your CyberSwitch. This program is designed for point-and-click installation and set-up of CSX200 and CSX400 devices.
Introduction primary window menus, consult the SPECTRUM Element Manager UserÕs Guide and the SPECTRUM Element Manager Tools Guide. Following is a description of the applications covered in this guide.
Introduction For more information about the capabilities of the CSX200 and CSX400 management modules, consult the appropriate hardware documentation. Software Conventions SPECTRUM Element ManagerÕs device user interface contains a number of elements which are common to most windows and which operate the same regardless of which window they appear in.
Introduction IP Address Displays the deviceÕs IP (Internet Protocol) Address; this will be the IP address used to deÞne the device icon. The IP address is assigned via Local Management to the CSXÕs internal Host interface; it cannot be changed via SPECTRUM Element Manager. Location Displays the user-deÞned location of the device. The location is entered through the System Group window; see the Generic SNMP UserÕs Guide for details.
Introduction Instructions to perform a mouse operation include the following terms: ¥ Pointing means to position the mouse cursor over an area without pressing either mouse button. ¥ Clicking means to position the mouse pointer over the indicated target, then press and release the appropriate mouse button. This is most commonly used to select or activate objects, such as menus or buttons.
Introduction Getting Help This section describes two different methods of getting help for questions or concerns you may have while using SPECTRUM Element Manager. Using On-line Help You can use the buttons to obtain information speciÞc to a particular window. When you click on a Help button, a window will appear which contains context-sensitive on-screen documentation that will assist you in the use of the windows and their associated command and menu options.
Introduction For additional information about Cabletron Systems products, visit our World Wide Web site: http://www.cabletron.com/. For technical support, select Service and Support. CSX200 and CSX400 Firmware SPECTRUM Element Manager support for the CSX200 has been tested against Þrmware version 1.02.06. The CSX400 has been tested against Þrmware version 2.00.11. If you have an earlier version of Þrmware and experience problems, contact Cabletron Systems Global Call Center for upgrade information.
Chapter 2 CSX200 and 400 Chassis View Information displayed in the Chassis View window; the Chassis Manager window; Hub management functions The CSX200/400 Chassis View window is the main screen that immediately informs you of the current condition of individual ports on your switch via a graphical display. The Chassis View window also serves as a single point of access to all other CSX windows and screens, which are discussed throughout this manual.
CSX200 and 400 Chassis View Viewing Chassis Information The desired CSX200/400 Chassis View window (Figure 2-1) provides a graphical representation of the device, including a color-coded port display which immediately informs you of the current conÞguration and status of the switch and its ports. Figure 2-1. CSX200 and CSX400 Chassis View Windows NOTES At the time of this release, the Chassis View windows will only display the bridge ports on a CSX device.
CSX200 and 400 Chassis View Front Panel Information The areas surrounding the main chassis area provide the following device information: IP The Internet Protocol address assigned to the CSX appears in the title bar of the Chassis View window. IP addresses are assigned via Local Management. Connection Status This color-coded area indicates the current state of communication between SPECTRUM Element Manager and the CSX200/400.
CSX200 and 400 Chassis View Time The current time, in a 24-hour hh:mm:ss format, set in the CSX200/400Õs internal clock. Date The current date, in an mm/dd/yy format, set in the CSX200/400Õs internal clock. NOTE In accordance with Year 2000 compliance requirements, SPECTRUM Element Manager now displays and allows you to set all dates with four-digit year values.
CSX200 and 400 Chassis View The Device Menu From the Device Menu at the Chassis View window menu bar, you can access the following selections: ¥ Device Type..., which displays a window containing a description of the device being modeled: CSX200/400 - CyberSWITCH. ¥ Edit Device Time/Edit Device Date..., which allows you set the deviceÕs internal clock. ¥ System Group..., which allows you to manage the CSX200/400 via SNMP MIB II. Refer to the Generic SNMP Guide for further information.
CSX200 and 400 Chassis View ¥ I/F Speed will display the speed (10 or 100 Mbits/sec) of the network segment attached to each port. The speed of the network management port will be displayed in Kbits/sec. ¥ I/F Type will display the interface type of each port in the CSX200/400 Ñ i.e., Eth (ethernet-csmacd) for the bridging interfaces, and PPP for the network management port.
CSX200 and 400 Chassis View ¥ Connection Type... opens a window displaying a description of the connection type of the selected bridge interface. This description is comprised of text based on the ctIfConnectionType MIB. ¥ Description..., which brings up a window describing the selected port; see Viewing the Port Description, later in this chapter. ¥ Performance Graph..., which allows you to view the trafÞc going through a selected bridge.
CSX200 and 400 Chassis View ¥ ¥ ¥ ¥ Bridge Ñ FWD, DIS, LRN, LIS, BLK, BRK, or UNK Bridge Mapping Ñ bridge interface index numbers Admin Ñ ON or OFF Operator Ñ ON or OFF If you have selected the Bridge status mode, a port is considered: ¥ FWD (Forwarding) if the port is on-line and forwarding packets across the CSX200/400 from one network segment to another.
CSX200 and 400 Chassis View connected to the port compared to the theoretical maximum load (10 or 100 Mbits/sec) of an Ethernet network. Errors If you choose the Errors mode, the interface boxes will display the percentage of the total number of valid packets processed by each port during the last polling interval that were error packets.
CSX200 and 400 Chassis View example, CSX200/400 bridging information is organized into its own component. Note, too, that there is no one-to-one correspondence between MIBs and MIB components. A single MIB component might contain objects from several different proprietary MIBs and RFCs. The Chassis Manager window, Figure 2-3, is a read-only window that displays the MIBs and the MIB components Ñ and, therefore, the functionality Ñ supported by the currently monitored device.
CSX200 and 400 Chassis View Figure 2-4. Device Type Windows Viewing the Port Description Choosing the Description... option on the individual port interface menus brings up a window that describes the interface you have selected. This description is based on a value returned by the ifDescr MIB. Two possibilities for a CSX interface description are shown in Figure 2-5. Figure 2-5.
CSX200 and 400 Chassis View Management for the CSX200/400 through SPELÕs Chassis View is comprised of source address location, viewing interface statistics, and enabling and disabling ports. Using the Find Source Address Feature You can select the Find Source Address option to discover which bridging interface a speciÞed source MAC address is communicating through. When you select the Find Source Address option, a search is made of the 802.
CSX200 and 400 Chassis View window also provides access to a detailed statistics window that breaks down Transmit and Receive trafÞc for each interface. To access the I/F Summary window: 1. From the Module View, click on the Device option from the menu bar. 2. Click again to select I/F Summary, and release. The I/F Summary window, Figure 2-7, will appear. Figure 2-7.
CSX200 and 400 Chassis View Physical Status Displays the current physical status Ñ or operational state Ñ of the interface: Online or Ofßine. Logical Status Displays the current logical status Ñ or administrative state Ñ of the interface: Up or Down. Interface Performance Statistics/Bar Graphs The statistical values (and, where available, the accompanying bar graphs) in the far-right columns of the I/F Summary window provide a quick summary of interface performance.
CSX200 and 400 Chassis View In Errors Packets received by the device interface that contained errors that prevented them from being delivered to a higher-layer protocol. In Unknown Packets received by the device interface that were discarded because of an unknown or unsupported protocol. Out Octets Octets transmitted by the interface, including framing characters.
CSX200 and 400 Chassis View Viewing Interface Detail The Interface Statistics window (Figure 2-8) provides detailed MIB-II interface statistical information Ñ including counts for both transmit and receive packets, and error and buffering information Ñ for each individual port interface. Colorcoded pie charts also let you graphically view statistics for both received and transmitted Unicast, Multicast, Discarded, and Error packets. To open the Interface Statistics window: 1.
CSX200 and 400 Chassis View Address Displays the MAC (physical) address of the selected interface. Type Displays the interface type of the selected port: ethernet-csmacd, sdlc, or other. The lower portion of the window provides the following transmit and receive statistics (the Þrst four statistics are also graphically displayed in the pie charts). Unicast Displays the number of packets transmitted to or received from this interface that had a single, unique destination address.
CSX200 and 400 Chassis View Packets Transmitted (Transmit only) Displays the number of packets transmitted by this interface.
CSX200 and 400 Chassis View 1. Click on the desired Port index. The Port menu will appear. 2. Click on Enable to enable the port, or Disable to disable the port. Your port will now be enabled or disabled as desired. NOTE For more information about bridging functions and how to determine the current state of each bridge port, see Chapter 4 of this manual.
CSX200 and 400 Chassis View 2-20 Managing the Device
Chapter 3 CSX200 and CSX400 WAN Configuration Physical CSX device information; CSX WPIMs; the WAN Logical View window The CSX200 devices have one WAN interface, a Cabletron Wide Area Port Interface Module (WPIM) installed at the factory. The CSX400 has two swappable WAN interfaces, which can currently consist of any combination of CabletronÕs T1/E1/DI, HDSL, DDS, or synchronous WPIMs. NOTE ItÕs important to note that a Windows 95- and NT-based utility called QuickSET was shipped with your CyberSWITCH.
CSX200 and CSX400 WAN Configuration pair cable, along with a WPIM slot to provide one WAN interface. The model number depends on the type of Wide Area Networking interface installed: NOTE CSX201 Provides a T1/E1 Wide Area uplink CSX202 Provides a Serial interface (V.35, X.21, RS449, RS232. or RS530) CSX203 Provides a DDS WAN uplink At the time of this release, SPECTRUM Element Manager does not support a DDS interface on a CSX device.
CSX200 and CSX400 WAN Configuration as the backup. If the primary link should fail for some reason, the other WAN interface will take over as the wide area link until the primary is restored. When a WPIM-S/T is installed as the backup interface, that connection will activate and provide an ISDN connection to the wide area network, if the primary WAN link fails. The ISDN WPIM can also provide backup for single or multiple Data Link Connection Interfaces (DLCIs).
CSX200 and CSX400 WAN Configuration Multiplexing (TDM) allows for the channelization of up to 31 links of a single physical interface. (CSX201) WPIM-HDSL This WPIM is designed for campus environments and provides a connection for sending LAN trafÞc over existing telephone lines at rates up to 1.544Mbps. It can communicate reliably up to a distance of 12,000 feet over Unshielded Twisted Pair (UTP) cabling. WPIM-S/T For the CSX400 only.
CSX200 and CSX400 WAN Configuration For more information on these WPIMs, consult the appropriate hardware documentation or your QuickSET documentation. WAN Logical View The WAN Logical View window displays information about the interfaces that are part of your physical port. The windows are identical for the T1 and the Synchronous ports. The number of entries is dependent on the type of port. The T1 port, for example, will have 24 entries. To open this window: 1.
CSX200 and CSX400 WAN Configuration WAN Logical View Window Fields IF Displays the interface index; a unique value for each interface that this device connects to. Protocol Displays the active Link Layer protocol. This Þeld displays PPP (Point to Point), Frame Relay, or Other. Compression Indicates whether data compression is activated or de-activated. NOTE Data compression is not supported by the CSX at this time; therefore, compression will always be de-activated or ÒOffÓ.
CSX200 and CSX400 WAN Configuration Figure 3-2. WAN Logical Settings Window 2. Click on the Protocol button to select PPP, Frame Relay, or None. LEX (LAN Extender) may also appear in the Protocol menu, but it is not applicable to a CSX device. 3. After making your changes, click on OK to exit the window and save the changes, or Cancel to exit the window without saving the changes. Note that this window also displays the state of compression on the interface.
CSX200 and CSX400 WAN Configuration 3-8 WAN Logical View
Chapter 4 Bridging A brief explanation of bridging methods; viewing and managing bridging interfaces; using the Bridge Status window; enabling and disabling bridging; viewing bridge statistics; using Spanning Tree; using the Filtering Database; using the Source Route Configuration window; using the Find Source Address feature; using the Port Source Addresses window; configuring duplex modes; using SONET port configuration options; configuring broadcast suppression; using the Token Ring Bridge Mode window;
Bridging About Transparent Bridging Transparent bridges are most common in Ethernet networks. Individual Transparent bridges monitor packet trafÞc on attached network segments to learn where end stations reside in relation to each segment by mapping the Source Address of each received frame to the port (and segment) it was detected on. This information gets stored in the bridgeÕs Filtering Database.
Bridging If the sending station does not receive a response to the test packet, it will send explorer packets to the destination; the explorer packets will be propagated by the networkÕs bridges as either All Paths Explorer (APE) packets or as Spanning Tree Explorer (STE) packets.
Bridging About Source Route-Transparent Bridges Because network topologies have developed in which bridges must be able to handle network trafÞc from end stations which support source routing and others which do not, a hybrid type of bridgeÑSource Route-Transparent (SRT)Ñcombines elements of both bridging methods.
Bridging For data that is restricted to the Token Ring networks available from the SR-TB bridgeÕs front panel, the bridging method used is user-conÞgurable via local management to be Source Route-only (bridged packets must include RIF information and will be source routed; no transparent bridging is enabled), Source Route-Transparent (bridging method will be determined by whether the RII bit is set), or Transparent only (no source routed packets will be bridged).
Bridging Viewing and Managing Bridging Interfaces With SPECTRUM Element Manager, you can view and manage each bridging interface supported by your device, including any installed interface modules, such as BRIMs (Bridge/Router Interface Modules) and HSIMs (High Speed Interface Modules).
Bridging NOTE ¥ The SmartTrunk option invokes the SmartTrunk ConÞguration and Status window, which enables you to group interfaces logically to achieve greater bandwidth between devices, if both devices support the SmartTrunk feature. There is no limit to the number of ports that can be included in a single Òtrunk,Ó nor is there a limit to the number of trunked ÒinstancesÓ that can be supported (see ConÞguring SmartTrunking, page 4-96).
Bridging The Bridge Status Window The Bridge Status window provides you with basic information about the current status of bridging across your device. Color-coding of each port display allows you to quickly ascertain the status of each interface. The Bridge Status window also lets you access further windows to control bridging at your device. To access the Bridge Status window from the Chassis View window: 1. Click on the Device selection in the menu bar. A pull-down menu will appear. 2.
Bridging Figure 4-1. The Bridge Status Window Up Time At the top of the Bridge Status window, you can see the time period (in a days, hours, minutes, seconds format) that has elapsed since the device was last reset or initialized. Bridge State on Interface Indicates the state of bridging over the port interface. Possible bridge states and their corresponding colors are: ¥ Forwarding (green)ÑThe port is on-line and forwarding packets across the bridge from one network segment to another.
Bridging ¥ Blocking (orange)ÑThe port is on-line, but Þltering trafÞc from going across the bridge from one network segment to another. Bridge topology information will be forwarded by the port. Interface Type Indicates the interface type which applies to each device bridging port interface (e.g., ethernet). The interface type (ifType) is a mandatory object type from the SNMP MIB II Interface (if) Group. Bridge Address Indicates the physical address of the bridge interface.
Bridging ¥ The Ethernet Special Filter DatabaseÉ window lets you conÞgure a special Þltering scheme at your bridge. With this scheme, you can enter Þlter parameters for a frame based on the contents of its source or destination address Þeld, type Þeld, or data Þeld (with offset)Ñthen specify the bridging action to take place at each port when a frame matching your speciÞcations is encountered (see Ethernet and Token Ring Special Filter Databases, page 4-49).
Bridging 4-12 ¥ The PPP Link StatusÉoption invokes the PPP Link Statistics Window, which enables you to view color-coded statistics related to the PPP (Point-to-Point Protocol) link at the selected interface (see The PPP Link Statistics Window, page 4-26). ¥ The Source Route StatisticsÉ option opens a window that allows you to view statistics for source routed trafÞc passing between bridging ports.
Bridging to the Statistics chapter in the SPECTRUM Element Manager Remote Monitoring (RMON) UserÕs Guide, and/or the appropriate device-speciÞc UserÕs Guide. ¥ The RMON Alarm ConÞgurationÉ invokes the Basic Alarm ConÞguration window that enables you to create alarms or actions at a speciÞc bridge interface based on rising and falling thresholds for Kilobits, Broadcast/Multicast packets, or Total Errors.
Bridging ¥ The Sonet/SDH ConÞgurationÉ window enables you to determine whether any installed FE-100Sx Fast Ethernet Port Interface Modules or APIM-2x ATM Port Interface Modules, both of which provide direct access to SONET (Synchronous Optical Network) networks, will operate according to SONET or SDH (Synchronous Digital Hierarchy) standards (see SONET/SDH ConÞguration, page 4-74).
Bridging from the Chassis View window: 1. Click on the appropriate port index to access the Port menu. 2. Drag down to Enable to restart bridging on the selected interface, or Disable to halt bridging across the selected interface. Enabling and Disabling All Installed Interfaces Similarly, there are two ways to disable bridging across all interfaces installed in a device: from the Bridge Status window: 1. Click on to display the Bridge menu. 2.
Bridging At the device level, a Detail button on the window allows you to compare the packets forwarded, Þltered, or transmitted on all networks supported by the device, as well as errors on all networks. For a selected bridged network, the Detail button allows you to view the number of packets forwarded to, or received from, each other network supported by the device. To access the device-level Bridge Performance Graph window from the Bridge Status window: 1. Click on to display the Bridge menu. 2.
Bridging Figure 4-2. Bridge Performance Graph Bridge Performance Graph Window Fields You can select the following statistics to display in the Bridge Performance Graph or Bridge Port Performance Graph. Statistics are provided numerically (as an average or peak value) and graphically. The device is polled for the graphed information every 2 seconds, and numeric values are updated based on this poll. The graph updates at the Þxed two second interval.
Bridging Errors (Red) Total Errors Nothing Xmitted (Blue) Xmitted Nothing The total number of errors that all bridging interfaces on the device, or an individual bridge interface, has experienced during bridging. The Errors scale is currently not measuring any type of error packets coming through the device or port. The total number of frames transmitted by the selected bridge interface, or all bridge interfaces.
Bridging To access this window from the Bridge performance graph, click on Bridge Detail Breakdown window, Figure 4-3, will appear. . The Figure 4-3. The Bridge Detail Breakdown Window The following information is available for the network segments connected to each of the bridge ports on the device, and any installed BRIM or HSIM port. The information is expressed both numerically and in pie charts. Each portÕs network segment has a corresponding color for its statistics or pie chart segments.
Bridging Xmitted The total number of frames transmitted over each portÕs network segment, as read from the device after each poll interval. The Bridge Port Detail Breakdown Window For the selected bridge interface, the Bridge Port Detail Breakdown window allows you to view the number of packets forwarded to or received from each of the other interfaces on your device. To access the Bridge Port Detail Breakdown window from the port Bridge performance graph, click .
Bridging The Interface Statistics Window You can use the interface Statistics window to view color-coded statistical information for each individual bridge port on your device. Statistics are provided for both transmit and receive packets at each port, as well as error and buffering information. Color-coded pie charts in the middle of the window lets you graphically view statistics for Unicast, Non-Unicast, Discarded and Error packets. To access the Statistics window from the Bridge Status window: 1.
Bridging Statistics Window Fields The following informational and statistics Þelds appear in the interface Statistics window. Three informational Þelds appear in the upper portion of the window: Description Describes the interface description for the currently selected port. Address Displays the MAC (physical) address of the selected port. Type Displays the interface type of the selected port. The following transmit and receive statistics Þelds are displayed in the lower portion of the window.
Bridging Unknown Protocol Displays the number of packets received which were discarded because of an unknown or unsupported protocol. The device bridge interface will discard the packet and increment this counter if it canÕt recognize the packet. Packets Received Displays the number of packets received by this interface. Transmit Queue Size The number of packets currently queued by the device for transmission from this interface.
Bridging Figure 4-6. CSMACD Statistics Window Each of the receive, transmission, and collision errors are described in detail below. Receive Errors Alignment The number of frames received on a particular interface that contain a nonintegral number of bytes (color-coded green). Misaligned packets can result from a MAC layer packet formation problem, or from a cabling problem that is corrupting or losing data.
Bridging SQE Test Displays the number of times that the SQE Test Error message is generated by the PLS sublayer on the selected interface. The SQE (Signal Quality Error) Test tests the collision detect circuitry after each transmission. If the SQE Test fails, a SQE Test Error is sent to the interface to indicate that the collision detect circuitry is malfunctioning.
Bridging Collision Errors Single Displays the number of successfully transmitted frames on the selected interface for which transmission was prevented by one collision. Multiple Displays the number of successfully transmitted frames on the selected interface for which transmission was prevented by more than one collision. Late Displays the number of times that a collision has been detected on this interface later than 51.
Bridging Figure 4-7. PPP Link Statistics Window Each of the errors and statistics related to the PPP Link at the selected bridging interface is described in detail below. Errors Bad Addresses The Bad Addresses Þeld displays the number of packets received with an incorrect Address Þeld. Bad Controls The Bad Controls Þeld displays the number of packets received on the selected interface that have an incorrect Control Þeld.
Bridging Bad FCSs The Bad FCSs Þeld displays the number of received packets that were discarded due to having an incorrect FCS (Frame Check Sequence) value. Total Errors The Total Errors Þeld displays the total number of errors of all types: Bad Addresses, Bad Controls, Packets Too Long, and Bad FCSs. Statistics Local MRU The Local MRU Þeld displays the current value of the MRU (Maximum Receive Unit) for the local PPP entity.
Bridging Local to Remote Protocol Compression The Local to Remote Protocol Compression Þeld determines whether or not the local PPP entity uses Protocol Compression when transmitting packets to the remote PPP entity. Remote to Local Protocol Compression The Remote to Local Protocol Compression Þeld determines whether or not the remote PPP entity uses Protocol Compression when transmitting packets to the local PPP entity.
Bridging from the Chassis View window: 1. Click on the appropriate port index to access the Port menu. 2. Drag down to select Dot5 Errors…. The device port Dot5 Errors Statistics window, Figure 4-8, will appear. Figure 4-8. Dot5 Errors Statistics Window Each type of IETF 802.5 error detected by the selected station port is described in detail below. Line Errors The Line Errors Þeld displays the number of the line errors detected by the selected port.
Bridging A. C. Errors The A. C. Errors Þeld displays the number of A. C. errors detected by the selected port. These errors count protocol data units (PDUs) that contain errors in the A or C bits. Abort Sequences The Abort Sequences Þeld displays the number of abort sequences transmitted by the selected port. Internal Errors The Internal Errors Þeld displays the number of recoverable internal errors detected by the selected port.
Bridging Transmit Beacons The Transmit Beacons Þeld displays the number of beacon frames transmitted by the selected station. Recoveries The Recoveries Þeld displays the number of frames the ring has been purged and recovered into a normal operating state. Lobe Wires The Lobe Wires Þeld displays the number of open or short circuits detected in the lobe data path. Removes The Removes Þeld displays the number of Remove Ring Station MAC frame requests detected by the selected port.
Bridging Figure 4-9. The Bridge Source Routing Window Bridge Source Routing Window Fields The Bridge Source Routing window provides basic statistics for source routed trafÞc passing between the bridging ports. Pie charts graphically break down the statistical information. The following frame types are provided for frames transmitted, received, and discarded by the bridge ports. All statistics are calculated since the device was last reset or powered up. Received Frames Specif.
Bridging When a sending station needs to determine the best route to an intended destination, it transmits an All Paths Explorer (APE) frame. The APE frame contains no routing information; it is propagated along all available paths to the destination station, which then directs a reply back to the source. The Þrst reply received by the original sending station is considered the most efÞcient route and is used in subsequent transmissions. Span. Tree Expl.
Bridging Hop Cnt. Exceeded Displays the number of All Paths Explorer frames discarded at the speciÞed port because they exceeded the number of routing descriptors (bridge hops) speciÞed by the Hop Count Limit. Bridge Spanning Tree The Bridge Spanning Tree window allows you to display and modify the deviceÕs bridge port information and protocol parameters relating to the Spanning Tree Algorithm. In a network design with multiple bridges placed in parallel (i.
Bridging Figure 4-10. Bridge Spanning Tree Window Configuring the Bridge Spanning Tree Window The Bridge Spanning Tree window displays STA parameters and allows you to alter parameters for the device bridge as a whole, and for each individual bridging interface. The currently selected bridging interface is highlighted in the lower right quadrant of the window. To alter the parameters of another interface, click on the appropriate Port X name listed in the quadrant.
Bridging TIP Part of a bridgeÕs IdentiÞer is based on its MAC address. In most network installations, performance differences between bridges may be negligible. You may, however, Þnd your data bottle-necked in installations where both a low-performance bridge and a high-performance bridge are attached to the same LAN segment and the two (or more) bridges have the same Priority component set (e.g., at the default 8000 Hex).
Bridging Hello Time This parameter indicates, in seconds, the length of time the Root Bridge (or bridge attempting to become the Root) waits before resending ConÞguration BPDUs. The range for this Þeld is 1 to 10 seconds, with a default value of 2 seconds. The Root Bridge sets the Hello Time. Max Age This parameter displays the bridgeÕs BPDU aging timer. This controls the maximum time a BPDU can be retained by the bridge before it is discarded.
Bridging A lower assigned value gives the port a higher Priority when BPDUs are compared. The allowable range is 0ÑFF hexadecimal (0Ñ255 decimal); the default is 80 hexadecimal. Path Cost Displays the cost that this port will contribute to the calculation of the overall Root path cost in a ConÞguration BPDU transmitted by this bridge port.
Bridging Changing Bridge Spanning Tree Parameters The Bridge Spanning Tree window allows you to update the following parameters for your device bridge. When you have Þnished making changes to the following individual parameters, you must click on at the bottom of the Spanning Tree window to write the changes to the device. NOTE Any values you set at the bridge will cause a Topology Change ßag to be issued in the next ConÞguration BPDUs it transmits.
Bridging Changing Hello Time If the bridge is the Root Bridge, or is attempting to become the Root, and you want to change the length of time the bridge waits between sending conÞguration BPDUs: 1. Highlight the Hello Time field, and type in a new value. 2. Click on . The IEEE 802.1d speciÞcation recommends that Hello Time = 2 seconds, with an allowable range of 1 to 10 seconds.
Bridging Changing Port Priority To change the part of the Port Priority used in priority comparisons: 1. If necessary, select the desired port by clicking the mouse to highlight the port in the lower right quadrant of the window. The lower left quadrant of the window will now allow you to edit parameters for the selected port. 2. Highlight the port Priority field, and enter the new priority identifier. Only valid hexadecimal numbers (0 to FF) are allowed in this field. The default is 80 hexadecimal. 3.
Bridging The Filtering Database consists of two separate databases: the Static and the Learned Databases. The Static Database contains addresses that are entered by a network administrator. You add these addresses directly to the database while the bridge is powered up, or to the deviceÕs battery-backed RAM so that they are stored on shutdown until the next power-up. The Learned Database consists of addresses that accumulate as part of the bridgeÕs learning process as it is up and running.
Bridging A scrollable Address Entry panel allows you to: ¥ View the address entries in the Filtering Database. ¥ Alter an entryÕs type (e.g., from Learned to Permanent, Dynamic, or Static). ¥ View and conÞgure the bridging action taking place on the packets entering each of the bridging ports. In addition, you can use buttons to add individual addresses to, or delete them from, these databases, or clear all Permanent, Static, or Dynamic entries in the database.
Bridging Figure 4-11. The Filtering Database Window Filtering Database Window Fields The following Þelds are listed in the top portion of the Filtering Database window. List The List checkboxes indicate whether the associated entry type (Permanent, Static, Dynamic, or Learned) will be displayed in the scrollable table of address entries. A check next to the entry type indicates that it will be displayed. Type Indicates the type of entry in the database.
Bridging Aging Time Indicates the length of time, in seconds, that Dynamic and Learned Addresses in the Source Address Table are allowed to remain inactive before they are dropped from the database. The allowable time range for these entries is 10 to 1,000,000 seconds. Aging time is not applicable to Static or Permanent entries. You can conÞgure this Þeld, as described in the next section. The following Þelds are applicable to the scrollable Address Entry panel of Filtering Database entries.
Bridging ¥ Changing the Receive port for the Þlter. ¥ Changing the Port Filtering action at each bridge port. ¥ Adding or deleting individual Filtering Database entries. ¥ Clearing all Permanent, Static, or Dynamic entries from the Filtering Database. Note that although conÞguration changes will appear in the window, no action actually takes place in the bridgeÕs Filtering Database until you click on the OK button in the bottom right of the window. This saves the new conÞguration.
Bridging Changing the Receive Port You can change the Receive port of an address entry in the scrollable panel, so that a frame must be received at the speciÞed port for the Þltering action to apply. To do so, click on the Receive port in the panel. With each click, the Receive port will cycle to the next port (e.g., from * (promiscuous), to 1, to 2, to 3, to 4, to 5, up to 32, back to *).
Bridging To delete an address: 1. Click to highlight the address entry in the Address Entry panel that you wish to delete from the filtering database. 2. Click on . Clearing All Permanent, Static, or Dynamic Entries To erase all Permanent, Static, or Dynamic entries from the Filtering Database, click on the associated button in the upper portion of the window.
Bridging Filters provide broad conÞguration ßexibility. For example, you can deÞne multiple scenarios for a single Þlter by specifying different combinations of receive port/destination port. You can use wildcard characters in Þlter Þelds to force a match with particular bits of the received packetÕs destination address, source address, type, or data. You can specify an offset for the data Þeld, to specify the starting point in the data where the bridge looks for the match.
Bridging Figure 4-13. Ethernet Special Filter Database Window Token Ring Special Filter Database Window At the Token Ring Special Filter Database window, Figure 4-14, you can view a list of the special Þlters for the selected bridge. There are 19 available Þlters in the Token Ring Special Filter Database. You can not add any additional Þlters. You can view Þve of these Þlters at a time in the Token Ring Special Filter Database window. Use the scroll bars to view the other fourteen Þlters.
Bridging from the Chassis View window: 1. Click on the Board Index of the device of interest; the Board menu will appear. 2. Drag down to select Token Ring Special Filter Database…. The Token Ring Special Filter Database window, Figure 4-14, will appear. Figure 4-14. Token Ring Special Filter Database Window Special Filter Database Window Fields File An X in this checkbox indicates that the Þlter is associated with the Þle name shown in the title bar of the window.
Bridging Data Type Displays the hexadecimal two-byte Þeld for the Þlter which can be used to mask out a speciÞed protocol type Þeld. Examples of protocol type are: ¥ ¥ ¥ ¥ 0800 = IP 8137 = Novell 0bad = Banyan 80f3 = AppletalkARP Data Offset Indicates the offset (in bytes, from the beginning of the data in the packet) where the Data Mask will be applied. The default for this Þeld is 0000 (no data offset). An example of a valid offset to enter into this Þeld is 0016 (16 bytes).
Bridging 2. Click . The Special Database Filter window, Figure 4-15, will appear with the following fields: • Destination Address (six-byte hexadecimal field) • Source Address (six-byte hexadecimal field) • Type (two-byte hexadecimal field) • Data Offset (decimal field) • Data Mask (64-byte hexadecimal data mask) Figure 4-15. The Special Database Filter Window 3. If you are editing an existing filter, the fields will reflect the current configuration.
Bridging 6. Click on to save the changes you have made and exit the Special Database Filter window. Changing the Receive Ports You can set the receive ports in the Special Filter Database window either before or after you deÞne a Þlter. These are the ports at which the frame must be received for the Þltering parameters to apply. The default selection is Port 1. To designate a receive port, click on the receive port icon ( ) for the Þlter. As you click on the icon, it will cycle though the ports (e.g.
Bridging Clearing the Port Filtering Action When you clear the port Þltering action of a Þlter, all ports that were conÞgured to forwarding or blocking will be reset to no action. Note that when you clear port Þltering for a Þlter, the Þltering or blocking action will be simultaneously cleared at all of its receive ports. In order to clear the port Þltering action, use the following steps. 1. Click to select the filter whose port filtering action you would like to disable. 2. Click on .
Bridging To open an existing Þle containing a Þlter set: 1. Click on . A menu will appear. 2. Click on Open…. A standard Microsoft Windows Open File window will appear. 3. To specify the file: • In the File name field, specify the file to open by path and name, or • Use the Look in drop-down list box and associated file list to select the desired file, and click to highlight it. 4. Click on Open.
Bridging Figure 4-16. Source Route ConÞguration Window Information on Source Routing Source Routing is a bridging technique developed by IBM and the 802.5 standards committee in which a bridge routes frames based on the contents of their media access control frame header, rather than by maintaining a Þltering database to determine whether a packet should be forwarded or Þltered.
Bridging ¥ When a source routing bridge processes the explorer frame, it adds a unique identiÞer to the frame in a reserved portion of the frame. This identiÞes the segment the frame was received from, followed by the speciÞc bridge, and Þnally the segment it was forwarded onto. ¥ When the discovery frame (or frames if more than one route is possible) reaches its destination, it contains a complete record of bridge hops on its route.
Bridging Subnet Mask A subnet mask is used by a device to determine whether a destination address exists within its own subnetwork (logical division of the network by router or gateway) and can be reached directly, or whether it is unknown and therefore must be delivered to a router (as speciÞed by the deviceÕs IP routing table or default gateway address).
Bridging You can use the Set button at the bottom of the window to change the Hop Count for the port, as explained in the section Making and Setting Changes, page 4-63. The permissible value for this Þeld is 0 to 28. Spanning Tree Expl. This read-only Þeld displays the action currently being applied to Spanning Tree Explorer frames received by the indicated port.
Bridging Spanning Tree Mode Indicates how a port on the device will behave with an incoming single-route broadcast (Spanning Tree ExplorerÑSTE) frame. You can conÞgure this Þeld with the radio buttons and checkboxes, or via the MIBTools utility or local management. This Þeld allows you to conÞgure a Spanning Tree for your network. You can set the Spanning Tree Mode to Auto or Manual using the radio buttons.
Bridging Making and Setting Changes The Source Route ConÞguration window allows you to affect changes for the following Source Route Bridging parameters: Bridge Number, Local Segment, Target Segment, Hop Count Limit, and the deviceÕs Spanning Tree Mode. To make a change to Bridge Number, Local Segment, Target Segment, or Hop Count Limit, use the mouse to highlight the existing value in the desired Þeld, and type in a new value.
Bridging Figure 4-17. Find Source Address Window 3. In the text field in the middle of the window, enter a valid MAC address in hexadecimal format and then click OK. If the address is found in the 802.1d Bridge Filtering Database, the port through which the address is communicating will ßash in the front panel Chassis View display. If the address is not found in the Filtering Database, a separate window will appear with a ÒCanÕt Find Source AddressÓ message.
Bridging Figure 4-18. Port Source Addresses Window The Port Source Addresses window displays the MAC addresses of all devices that have transmitted packets that have been forwarded through the selected bridging interface during the last cycle of the Filtering DatabaseÕs deÞned aging timer (learned addresses that have not transmitted a packet during one complete cycle of the aging timer are purged from the Source Address Table).
Bridging Figure 4-19. Device Aging Time Window 2. Type in the new Aging Time, in seconds, then click on . The allowable range is 10 to 1000000 seconds; the default is 300 seconds. Duplex Modes Some of the bridge interfaces on a device will support Full Duplex Switched Ethernet (FDSE) mode. Enabling full duplex mode on an interface allows the interface to receive and transmit packets at the same time, effectively doubling the available bandwidth.
Bridging The Duplex Modes Window The bridge-level Duplex Modes window allows you to enable and disable full duplex mode capability for each bridging interface on your device. The window lists each interface on the device and whether full duplex is ÒONÓ or ÒOFFÓ for each interface. To access the Duplex Modes window from the Bridge Status window: 1. Click on to display the Bridge menu. 2. Drag down to select Duplex Modes…. The Duplex Modes window, Figure 4-20, will appear. from the Chassis View window: 1.
Bridging Full Duplex Displays the current state of full duplex on each interface. Possible values for this Þeld are as follows: Connect A Indicates that the interface is connected to MMAC Channel A and does not support full duplex mode (Interface 1 only). You will not be able to change the value of this Þeld from this window. ON Indicates that full duplex mode is being used on this interface. OFF Indicates that full duplex mode is not being used on this interface.
Bridging Ethernet Port Configuration Window You can also conÞgure duplex modes from the Port ConÞguration window. To access the Port ConÞguration window: from the Bridge Status window: 1. Click on the desired Port button ( ) to display the port menu. 2. Drag down to select Configuration…. The Port Configuration window for the selected Ethernet interface, Figure 4-21, will appear. from the Chassis View window: 1. Click on the appropriate port index to access the Port menu. 2.
Bridging You set an interface to use standard or full duplex by selecting the appropriate mode from this window. When you open the Port ConÞguration window the currently used mode appears selected. To change the mode from standard to full duplex mode or from full duplex to standard mode, click in the radio button of the appropriate option and then click on Apply. To cancel the action without applying any changes, click on Cancel.
Bridging Figure 4-22. Fast Ethernet ConÞguration Port X Window From this window you can manually set the operational mode of the port, orÑfor 100Base-TX interfacesÑset the port to auto-negotiation so that the appropriate operational mode can be determined automatically. The mode you set will determine the speed of the port and whether it uses full duplex or standard mode bridging.
Bridging Desired Operational Mode Displays the operational mode that you want to conÞgure for this port. The following operational modes are available for each port: FE-100TX Auto-Negotiation, 10Base-T, 10Base-T Full Duplex, 100Base-TX, and 100Base-TX Full Duplex. FE-100FX 100Base-FX and 100Base-FX Full Duplex See Setting the Desired Operational Mode for the FE-100TX and Setting the Desired Operational Mode for the FE-100FX, following, for more information.
Bridging Setting the Desired Operational Mode for the FE-100TX You can manually set the FE-100TX to use any one of four operational modes. You can also set the port to auto-negotiation, which allows the port to determine for itself the best operational mode using the Advertised Abilities and Remote Capabilities of the local and remote interface, respectively. If you want to manually conÞgure the mode: 1.
Bridging SONET Port Configuration The FE100-Sx series of Fast Ethernet Port Interface Modules and the APIM-2x series of ATM Port Interface Modules provide SONET (Synchronous Optical Network) access for some of CabletronÕs devices. The FE100-Sx Port Interface Modules and the APIM-2x Port Interface Modules link high-speed local or metropolitan area networks by using an OC-3 connection (leased from your local telco or Internet service provider) to a SONET ring.
Bridging Table 4-1. SONET/SDH Transmission Hierarchies SONET Bit Rate SDH STS-1/OC-1 51.84 Mbps Ñ STS-3/OC-3 (supports FE-100Sx and APIM-2x in SONET operational mode) 155.52 Mbps STM-1 (supports FE-100Sx and APIM-2x in SDH operational mode) STS-12/OC-12 622.08 Mbps STM-4 STS-24/OC-24 1244.16 Mbps Ñ STS-48/OC-48 2588.32 Mbps STM-16 STS-192/OC-192 9953.
Bridging To set the operational mode of the SONET port via the SONET/SDH ConÞguration window: 1. Click in the radio box adjacent to the appropriate selection, SONET or SDH, to choose the data transmission standard to be used by the interface. 2. Click on Apply to set your change at the interface, or Cancel to exit the SONET/SDH Configuration window without applying any changes.
Bridging These errors can occur in any of the four optical layers of a SONET network, which are (in order from lowest to highest layer in the hierarchy) the physical Medium, Section, Line, and Path layers. ¥ The Medium layer is the Photonic layer that physically converts electrical signals to optical signals.
Bridging To access the SONET/SDH Statistics window from the Bridge Status window: 1. Click on the desired Port button ( ) to display the port menu. 2. Drag down to select SONET/SDH Statistics…. The SONET/SDH Statistics window for that interface, Figure 4-24, will appear. from the Chassis View window: 1. Click on the appropriate port index to access the Port menu. 2. Drag down to select SONET/SDH Statistics…. The SONET/SDH Statistics window for that interface, Figure 4-24, will appear. Figure 4-24.
Bridging Note also that these indicators simply show which error conditions have been detected during the last 15-minute interval; they do not alter the display of the statistics above. Loss of Pointer SONET uses ÒpointersÓ to compensate for frequency and phase variations as data is being transmitted across the optical network, so that data is not delayed or lost on the network.
Bridging A Loss of Signal may also be detected if the received signal level (e.g., the incoming optical power) falls below a Bit Error Rate (BER) threshold of 1 in 103. A BER is the number of coding violations detected in an interval of time (usually one second). A predicted BER of 1 in 103 means that during each second, there is an error ratio of 1 errored bit per 1,000 bits sent.
Bridging Coding Violations are Bit Interleaved Parity (BIP) errors that are detected in the incoming signal (as described below). Severely Errored Seconds The number of Severely Errored Seconds, or Far-End Severely Errored Seconds, encountered by a SONET/SDH Path in the speciÞed interval.
Bridging Configuring Broadcast Suppression Excessive broadcasts to all ports, or broadcast storms, can result in severe network performance problems, and possibly cause the network to crash. Devices which support the broadcast suppression feature provide automatic protection against broadcast/multicast storms. In many ways, broadcast suppression is similar to Þltering. To protect against storms, an acceptable rate for broadcast trafÞc across a port is deÞned.
Bridging To conÞgure a port for broadcast storm protection: 1. Click to highlight the entry for the port you wish to configure for automatic broadcast storm protection. 2. In the Time on Selected Ports field, enter the desired time period in seconds. Note that a value of 0 will disable the threshold alarm. 3. In the Transmit (Frames Per Second) Threshold on Selected Ports field, enter the number of broadcast packets that will be the threshold for the time period set in Step 2. 4.
Bridging Figure 4-26. Token Ring Bridge Mode Window Defining the Bridge Modes Transparent When the bridge is set to Transparent mode, the bridge will only transmit transparent frames from the Token Ring connection. If a source route frame is received by the bridge, the Source Route information in the frame will be dropped from the packet. (A transparent frame is the same as a source route frame without a RIFÑRouting Information Field.
Bridging Using the Physical View Windows ETWMIM Ethernet Port Physical View The Physical View allows you to view the physical state of the Ethernet port when you are monitoring an ETWMIM via SPECTRUM Element Manager. To use the Physical View option from the Bridge Status window: 1. Click on the Ethernet bridge port (Port 1). The Ethernet bridge port pull-down menu will appear. 2. Drag down to select Physical View…. The ETWMIM EtherPhysStatus (Ethernet Physical Status) window, Figure 4-27, will appear.
Bridging ¥ If you have opted to use a front panel EPIM for your Ethernet connection, the X will appear in the EPIM checkbox. You cannot change your active port conÞguration from the window. It must be changed physically on the ETWMIM itself. Epim Type This Þeld will show the type of EPIM you have installed via the front panel of your ETWMIM, if applicable. The types of EPIMs are listed below, along with the type of segment each will be connected to.
Bridging from the Chassis View window: 1. Click on the Token Ring bridge port (Port 2). The Token Ring bridge port pull-down menu will appear. 2. Drag down to select Physical View…. The ETWMIM Token Ring Phys(ical) Status window, Figure 4-28, will appear. Figure 4-28. Token Ring Port Physical View Token Ring Physical Status Fields Ring Speed Displays the current ring speed conÞgured for your Token Ring port.
Bridging FNB State The FNB State section displays, and lets you conÞgure, the state of the backplane FNB connectors on the ETWMIM. The right-hand side of the window displays the current connection conÞguration for the FNB connectors on the ETWMIM, and lets you alter those options by using the appropriate radio button selections: ¥ Connect Left indicates that the ETWMIM is/will be connected on the FNB to the Þrst board to its left in the MMAC chassis with a valid right FNB connection.
Bridging Using the Interface Configuration Window The I/F ConÞguration port-level menu option invokes the Interface ConÞguration window, which allows you to select a bridging method for a Token Ring bridging interface. You can also make this selection via the Token Ring Bridge Mode window; see Token Ring Bridge Mode, page 4-83, for more information.
Bridging Figure 4-29. Interface ConÞguration Window Defining the Bridge Method Transparent When the bridge is set to Transparent mode, the bridge will only transmit transparent frames from the Token Ring connection. If a source route frame is received by the bridge, the Source Route information in the frame will be dropped from the packet. (A transparent frame is the same as a source route frame without a RIFÑRouting Information Field.
Bridging Source Route Transparent When the bridge is set to Source Route Transparent, the bridge will transmit both transparent and source route frames. The frames received which have source route information will be transmitted as source route, while frames received that are transparent will be transmitted as transparent. Setting the Bridge Method 1.
Bridging To select Transparent as the transmission method for TCP/IP, IPX, SNA, NetBIOS or Other protocols: 1. Click on the radio button next to the transmission method you would like your Token Ring bridge port to use: Transparent, Source Route, or Auto. 2. Click on Set to apply the desired mode.
Bridging Figure 4-30. Bridge ConÞguration Window To access the Port ConÞguration window from the Bridge Status window: 1. Click on the desired Port button ( ) to display the port menu. 2. Drag down to select Port Configuration…. The Port Configuration window, Figure 4-31, will appear. from the Chassis View window: 1. Click on the appropriate port index to access the Port menu. 2. Drag down to select Port Configuration…. The Port Configuration window, Figure 4-31, will appear.
Bridging Figure 4-31. Port ConÞguration Window The Bridge ConÞguration and Port ConÞguration window Þelds are deÞned as follows: Bridge Number Displays the number of the Token Ring bridge. This value is limited to the range of 0 through 15; a value of 65535 signiÞes there is no bridge number assigned. This Þeld is settable in the Bridge ConÞguration window and read-only in the Port ConÞguration window.
Bridging Port Mode Displays the two port mode options that are available, Lobe or Station. Novell Translation Displays the three bit-order options that are availableÑEnable LLC (Logical Link Control Translation), Enable DLC (Data Link Layer Translation), and Disable (No translation will take place) at the bridge or bridge interface. Ring Speed Displays the selected ring speed, 4 Mb/s or 16 Mb/s.
Bridging To set the Novell Translation method globally for all bridge interfaces on a device in the Bridge ConÞguration window or for an individual interface in the Port ConÞguration window: 1. Click on the empty radio button adjacent to one of the three choices in the Novell Translation field, Enable LLC, Enable DLC, or Disable. When the radio button is filled ( ), the selected choice will be enabled. 2. Click on Set to apply the change, or click on Cancel to exit the window without applying the change.
Bridging To access the SmartTrunk ConÞguration and Status window from the Bridge Status window: 1. Click on to display the Bridge menu. 2. Drag down to select SmartTrunk…. The SmartTrunk Configuration and Status window, Figure 4-32, will appear. from the Chassis View window: 1. Click on the Board Index of the device of interest; the Board menu will appear. 2. Drag down to select SmartTrunk…. The SmartTrunk Configuration and Status window, Figure 4-32, will appear. Figure 4-32.
Bridging Mode Displays the connection type for each port, either User or Network. User connections do not participate in SmartTrunking; Network connections do. At least two ports (from two separate chassis) must be designated as Network connections to participate in SmartTrunking. All FNB interfaces must be designated as User connections. SmartTrunk State Displays the current operating state of each listed port. The possible states include: ¥ NoneÑThe port is operating as a normal switch port.
Bridging To enable or disable Load Sharing on an individual bridge port: 1. Click to select the interface number under the Port column in the list box. The interface number will then be listed as “X” in the Enable/Disable Port # X field. 2. Click on the empty radio button adjacent to one of the two choices in the field: LoadSharing or Disable. When the radio button is filled ( ), the selected choice will be enabled. 3.
Bridging 4-100 Configuring SmartTrunking
Index A Accessing Other Management Options Duplex Modes window 4-11 Ethernet Special Filter Database window 4-11 Filtering Database window 4-10 Module Type window 4-10 Performance Graph 4-10 Spanning Tree window 4-10 Active Monitor 4-88 Active Port 4-85 Address 4-22, 4-46 Admin 2-8 Admin/Link 2-8 Ageing Time 4-46 Altering 4-47 Alarm ConÞguration window 4-13 All Paths Explorer (APE) packet 4-3 APIM-2x 4-74 B Bit Interleaved Parity 4-81 Boot Prom, revision 2-3 Bridge 2-8 Bridge Address 4-10 Bridge ConÞgurat
Index Destination Address 4-52, 4-54 Device Menu 2-5 Device Name 1-4 Device Type 2-10 disable a bridge port 4-14 Discarded 4-22 Discarded packets 2-17 Dot5 Error Statistics window 4-6 Dot5 Errors window 4-12 Duplex Mode Setting 4-68 Duplex Modes 4-66 Duplex Modes window 4-6, 4-67 Duplex Modes Window Fields 4-67 Dynamic entries 4-43 E edit 4-53 Edit button 4-53 Enable 4-52 Entries Clearing All 4-49 Epim Type 4-86 Error 4-22 Errored Seconds 4-80 Errors 4-18, 4-19 Ethernet Port Physical View 4-85 Ethernet Sp
Index Logical Settings 3-7 Logical Status 2-14 Logical View 3-5 Loss of Frame 4-80 Loss of Pointer 4-79 Loss of Signal 4-79 M MAC address 1-5, 2-3 Max Age 4-38 Max Age Time Changing 4-41 menu structure 2-4 MIB components 2-9 Mode 4-98 mouse usage 1-5 MTU 3-6 Multicast (Non-Unicast) 2-17 N N/A 4-68 Name 4-97 Network design 4-35 New button 4-48 New Filter Window 4-48 Non-Unicast 4-22 Non-Unicast (Multicast) 2-17 Number 4-45 O OFF 2-8, 4-68 OK button 1-6 ON 2-8, 4-68 P Packets Received 2-17, 4-23 Packets
Index SmartTrunk ConÞguration and Status window 4-96 SmartTrunk State 4-98 SmartTrunks 4-98 SONET 4-74 Sonet Statistics window 4-14 SONET/SDH 4-74 Coding Violations 4-81 configuration 4-74 Errored Second 4-80 errors 4-76 Errors indicators 4-78 Loss of Frame 4-80 Loss of Pointer 4-79 Loss of Signal 4-79 optical layers 4-77 Severely Errored Framing Second 4-81 Severely Errored Second 4-81 Statistics 4-76, 4-80 Statistics window 4-78 SONET/SDH conÞguration 4-74 Sonet/SDH ConÞguration window 4-14 SONET/SDH tra
