Cabletron Systems CSX200, CSX400 manual Bridging

Page 49

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. The task of both packet types is to get the destination station to return speciÞc route information to the sending station (by including an identiÞer for each ring the explorer packet traversed and for each bridge between any rings).

Since the data ßow on a Source Routed network is determined by end stations (unlike a Transparently bridged network), a looped bridge topology is not an issue for data ßow. APE packets are sent from the source station over every possible bridge path to the end station. The original APE frame contains no routing information (e.g., bridge numbers and ring numbers). As the frame is propagated along all available paths to the destination station, each bridge along the way adds its own bridge and ring numbers to the packetÕs RIF before forwarding it, thereby providing route information.

In response to each received APE packet, the destination station directs a reply to the sending station. On receiving the replies, the sending station ideally assumes that the Þrst returned reply contains the most efÞcient route. The sending station then stores the route information and uses it to send subsequent transmissions to the same station.

Because APE frames do increase network trafÞc, some sites may use STE explorer frames as an alternate method of route discovery. With STE exploration, a Spanning Tree Algorithm (either conÞgured automatically via BPDUs or manually via management) is maintained for the sole purpose of determining how to direct an explorer frame during route discovery.

During the discovery process, a source station will send out STE explorer frames into a bridged topology. If a bridge is in a forwarding state according to Spanning Tree, it will forward an explorer frame onto its attached LAN segment (appending the Bridge and LAN Segment IdentiÞers in the appropriate area of the RIF); if the bridge is Þltering, it will discard the explorer frames. In this fashion, only a single explorer frame will reach each individual LAN segment.

Ultimately, the destination station will receive only a single STE packet, and will respond with APE packets (that return to the sending station on all possible bridge paths) or an STE packet (that returns to the sending station via in the reverse route of the STE explorer packet).

Although the Spanning Tree Algorithm determines the bridge path an STE takes to the destination station, during future communication between the stations, bridges along the route will use Source Routing to forward the packet (i.e., the bridges will read the Routing Information Field in the header of speciÞcally routed frames to decide whether to forward them).

Bridging Basics

4-3

Image 49
Contents CSX200 and CSX400 User’s Guide Page Virus Disclaimer Page Restricted Rights Notice Page Contents Chapter Bridging Vii Token Ring Physical Status Fields IndexIntroduction HSIM-W6 and HSIM-W84 Using the CSX 200 and CSX400 User’s GuideRelated Manuals Common Window Fields Software ConventionsDevice Name IP Address Using the MouseLocation MAC AddressUsing Window Buttons Getting Help Using On-line HelpGetting Help from the Cabletron Systems Global Call Center CSX200 and CSX400 Firmware CSX200 and 400 Chassis View CSX200 and CSX400 Chassis View Windows Viewing Chassis InformationFront Panel Information Time Menu StructureDate Port Status Menu Device MenuHelp Menu Utilities MenuPort Menus Selecting a Port Status View CSX200/400 Port Status DisplaysStatus Load Port Status Color Codes Chassis Manager WindowDevice Type Viewing Hardware TypesViewing the Port Description Managing the DeviceViewing I/F Summary Information Using the Find Source Address FeatureDescription IndexLogical Status Physical StatusInterface Performance Statistics/Bar Graphs Raw CountsRate Detail Interface Statistics Viewing Interface DetailAddress ErrorUnicast Non-UnicastPackets Transmitted Transmit only Enabling and Disabling PortsMaking Sense of Detail Statistics CSX200 and 400 Chassis View CSX200 and 400 Chassis View Managing the Device About the CSX200 Series CSX200 and CSX400 WAN ConfigurationWAN Redundancy About the CSX400WPIM-DDS CSX WPIMsEIA-RS449 WAN Logical View Window WAN Logical ViewWAN Logical View Window Fields Changing WAN Logical SettingsCSX200 and CSX400 WAN Configuration CSX200 and CSX400 WAN Configuration WAN Logical View Bridging Basics BridgingAbout Source Route Bridging About Transparent BridgingBridging About Source Route-Translational Bridges About Source Route-Transparent BridgesBridging Viewing and Managing Bridging Interfaces Bridging Bridge Status Window Information Fields Bridge Status WindowBridge State on Interface Up TimeInterface Type Accessing Other Options from the Bridge Status WindowBridge Address Bridging Bridging Bridging Enabling and Disabling Individual Interfaces Enabling and Disabling BridgingFrom the Bridge Status window Bridge Statistics Enabling and Disabling All Installed InterfacesPerformance Graphs From the Chassis View windowFrom the Bridge Status window Frames Forwarded Green Bridge Performance Graph Window FieldsFiltered Magenta Xmitted Blue Errors RedConfiguring the Bridge Performance Graphs Bridge Detail Breakdown WindowFiltered Frames ForwardedBridge Port Detail Breakdown Window XmittedForwarded to Forwarded fromI/F Statistics Window Interface Statistics WindowStatistics Window Fields Unknown Protocol Csmacd Statistics WindowPackets Received Transmit Queue SizeAlignment Receive ErrorsTransmission Errors PPP Link Statistics Window Collision ErrorsBad Addresses ErrorsBad Controls Packets Too LongStatistics Dot5 Errors Statistics Window Burst Errors Line ErrorsCongestion Errors Internal ErrorsToken Errors Soft ErrorsSource Route Statistics Received Frames Bridge Source Routing Window FieldsSpecif. Routed All Paths ExplDiscards Transmitted FramesHop Cnt. Exceeded Bridge Spanning TreeBridge Level Fields Configuring the Bridge Spanning Tree WindowBridge Priority Root Cost Root BridgeRoot Port Bridge Port Level Fields Designated Cost Path CostDesignated Root Designated BridgeChanging Bridge Priority Changing Bridge Spanning Tree ParametersChanging the Spanning Tree Algorithm Protocol Type Changing Hello Time Changing Forwarding Delay TimeChanging Max Age Time Changing Port Priority Filtering DatabaseChanging Path Cost Bridging From the Bridge Status window List Filtering Database Window FieldsNumber CapacityAging Time Configuring the Filtering DatabaseSource Port Receive PortChanging the Type of Entry Altering the Aging TimeChanging the Port Filtering Action Changing the Receive PortAdding or Deleting Individual Entries Clearing All Permanent, Static, or Dynamic Entries Ethernet and Token Ring Special Filter DatabasesEthernet Special Filter Database Window 13. Ethernet Special Filter Database Window Token Ring Special Filter Database WindowSpecial Filter Database Window Fields EnableFile Destination AddressDefining and Editing Filters in the Special Database This Changing the Receive Ports Setting the Port Filtering ActionChanging the Port Filtering Action Saving a Set of Filters to a File Enabling and Disabling a FilterClearing the Port Filtering Action Source Route Configuration 16. Source Route ConÞguration Window Information on Source RoutingSource Route Configuration Fields Source Route Configuration WindowLocal Segment Subnet MaskTarget Segment Hop Count LimitBridge Number Spanning Tree ExplSpanning Tree Mode Making and Setting Changes Using the Find Source Address FeaturePort Source Addresses Window Setting the Aging Time Duplex Modes Duplex Modes Window Fields Duplex Modes WindowInterface Full Duplex Setting the Duplex ModeEthernet Port Configuration Window Standard ModeFast Ethernet Port Configuration Port Type Current Operational ModeLink State Advertised Abilities Desired Operational ModeRemote Capabilities Setting the Desired Operational Mode for the FE-100FX Setting the Desired Operational Mode for the FE-100TXSONET/SDH Configuration Sonet Port ConfigurationSonet SONET/SDH Statistics Window Bridging 24. The SONET/SDH Statistics Window Loss of Pointer Loss of SignalLoss of Frame Errored SecondsSeverely Errored Framing Seconds Severely Errored SecondsCode Violations Configuring Broadcast Suppression Token Ring Bridge Mode Defining the Bridge Modes Setting The Token Ring Bridge ModeTransparent Source RoutingEtwmim Ethernet Port Physical View Using the Physical View WindowsEthernet Port Physical Status Fields Active PortEpim Type Etwmim Token Ring Port Physical ViewRing Speed Token Ring Physical Status FieldsRing State Active Monitor FNB StateUsing the Interface Configuration Window 29. Interface ConÞguration Window Defining the Bridge MethodNetBIOS Setting the Bridge MethodDefining the Protocol Transmission OtherUsing the Bridge and Port Configuration Windows From the Bridge Status window Ring Number Virtual Ring NumberNovell Translation Port ModeBridge Mode/Explorer Type Configuring SmartTrunking Name PortSmartTrunk State ModeInstance # SmartTrunksBridging Bridging 100 Configuring SmartTrunking Index Index-2 Index-3 Index-4
Related manuals
Manual 88 pages 62.16 Kb Manual 275 pages 3.4 Kb

CSX200, CSX400 specifications

Cabletron Systems was a leading developer of networking solutions, and its CSX400 and CSX200 series of high-performance switches represent some of the key innovations in the field of enterprise networking during their time. Both models were geared towards enhancing network reliability, efficiency, and speed, particularly in environments where heavy data traffic and complex networking demands were prevalent.

The CSX400, designed for larger enterprises, boasts a robust architecture capable of handling significant throughput. One of its standout features is its stackable design, allowing multiple switches to be interconnected and managed seamlessly as a single unit. This scalability provides organizations with the flexibility to expand their networks without significant infrastructure overhauls. The CSX400 supports various Ethernet standards, including 10/100 Ethernet and Gigabit Ethernet, positioning it to effectively manage both legacy and modern networking requirements.

In addition to its scalability, the CSX400 is distinguished by its advanced Layer 2 and Layer 3 routing capabilities. This dual-layer functionality enables efficient data handling and is instrumental in managing traffic between different network segments. Moreover, the switch incorporates features like VLAN (Virtual Local Area Network) support and Quality of Service (QoS) prioritization, allowing for enhanced performance of critical applications and streamlined bandwidth allocation.

On the other hand, the CSX200 series is tailored for smaller enterprises or branch offices needing a reliable yet efficient networking solution. Despite its compact design, the CSX200 is equipped with essential features that promote effective network management and security. It offers a simplified management interface, making it user-friendly for network administrators. The switch also provides essential access control measures, employing technologies like IEEE 802.1X for network access security.

Both the CSX400 and CSX200 prioritize performance through the incorporation of advanced switching technologies. They support features such as Spanning Tree Protocol (STP), enabling loop-free topologies and enhanced network resilience. These attributes are particularly crucial in dynamic networking environments where downtime can have significant repercussions on business operations.

Overall, Cabletron Systems' CSX400 and CSX200 series represent a blend of scalability, advanced routing capabilities, and user-friendly management, making them vital assets for organizations looking to optimize their network infrastructure during a period of rapid technological evolution. With their rich feature sets and unwavering performance, these switches helped pave the way for modern networking solutions that cater to diverse enterprise needs.