Cabletron Systems EMM-E6 manual Total Errors, Alignment Errors, CRC Errors, OOW Collisions

Page 39

Using the EMM-E6 Hub View

“legal” collisions, as opposed to the OOW collisions described below) are a natural by-product of a busy network; if you are experiencing high numbers of collisions, it may be time to redirect network traffic by using bridges or routers. Extremely high collision rates can also indicate a data loop (redundant connections) or a hardware problem (some station transmitting without listening first).

Total Errors

The total number of errors of all types recorded by this network (channel), module, or port since the statistics window was opened or the Reset button was pressed.

Alignment Errors

The total number of misaligned packets recorded since the statistics window was opened or the Reset button was pressed. Misaligned packets are those which contain any unit of bits which is less than a byte — in other words, any group of bits fewer than 8. Misaligned packets can result from a packet formation problem, or from some cabling problem that is corrupting or losing data; they can also result from packets passing through more than two cascaded multi-port transceivers (a network design which does not meet accepted Ethernet spec).

CRC Errors

CRC, or Cyclic Redundancy Check, errors occur when packets are somehow damaged in transit. When each packet is transmitted, the transmitting device computes a frame check sequence (FCS) value based on the contents of the packet, and appends that value to the packet. The receiving station performs the same computation; if the FCS values differ, the packet is assumed to have been corrupted and is counted as a CRC error. CRC errors can result from a hardware problem causing an inaccurate computation of the FCS value, or from some other transmission problem that has garbled the original data. The CRC error counter shows the total number of CRC errors that were recorded since the statistics window was opened or the Reset button was pressed.

OOW Collisions

The total number of out-of-window collisions recorded since the statistics window was opened or the Reset button was pressed. OOW collisions occur when a station receives a collision signal while still transmitting, but more than

51.2∝sec (the maximum Ethernet propagation delay) after the transmission began. There are two conditions which can cause this type of error: either the network’s physical length exceeds IEEE 802.3 specifications, or a node on the net

is transmitting without first listening for carrier sense (and beginning its illegal transmission more than 51.2 ∝s after the first station began transmitting). Note that in both cases, the occurrence of the errors can be intermittent: in the case of excessive network length, OOW collisions will only occur when the farthest stations transmit at the same time; in the case of the node which is transmitting without listening, the malfunctioning node may only fail to listen occasionally,

and not all of its failures to listen will result in OOW collisions — some may simply result in collisions (if the 51.2 ∝s window has not yet closed), and some will get through fine (if no one else happens to be transmitting).

Monitoring Hub Performance

2-23

Image 39
Contents EMM-E6 Page Virus Disclaimer Restricted Rights Notice Contents Chapter Security Chapter Source AddressingAppendix a EMM-E6 MIB Structure Chapter Front Panel RedundancyContents Introduction Using the EMM-E6 User’s GuideUsing the EMM-E6 User’s Guide UPS What’s not in the EMM-E6 User’s GuideConventions Window Conventions Screen DisplaysButton Using the MouseGetting Help Year 2000 Compliance EMM-E6 FirmwareUsing the Hub View Using the EMM-E6 Hub ViewHub View Front Panel Navigating Through the Hub ViewDevice Location UptimeDate and Time Device NameUsing the EMM-E6 Hub View EMM-E6 Ports Display Brim Ports Using the Mouse in a Hub View ModulePort Display Form Hub View Port Color CodesMonitoring Hub Performance Port Display Form Collisions ErrorsLoad TrafficProtocols Frame SizesPort Type Using the EMM-E6 Hub View Checking Device Status and Updating Front Panel Info Name and LocationContact Chassis Type Checking Network StatusActive Users NameModule Type Checking Module StatusLink Status Checking Port StatusMedia Type StatusTopology Type Viewing the IP Address TableChecking Statistics Launching the Global Find MAC Address ToolUsing the EMM-E6 Hub View Broadcast Packets Received BytesTotal Packets Avg Packet SizeOOW Collisions Total ErrorsAlignment Errors CRC ErrorsGiant Frames Runt FramesProtocols/Frames Statistics Viewing the Port Source Address ListUsing the EMM-E6 Hub View Managing the Hub Setting the Polling IntervalsDevice General Status Contact StatusStatistics Configuring FNB ConnectionsDevice Configuration Port Operational StateConfiguring RIC MIM Connections To configure FNB connectivity for an individual port 15. Tpxmim Channel Selection Window Setting a Port’s Trunk TypeTo change a port’s topology status Enabling/Disabling MIM Ports Alarm Configuration From the Hub View Using Alarm ConfigurationFrom the command line stand-alone mode From the iconCRC Configuring AlarmsBroadcast Setting Repeater AlarmsSet Repeater Alarms Window Setting and Changing AlarmsSetting Module Alarms Setting Module and Port AlarmsSet the Status to Enabled Set Module Alarms WindowSet Port Alarms Window Setting Port AlarmsSet the Status to Enabled Alarm Configuration Setting Module and Port Alarms Link/Seg Traps What is a Segmentation Trap?Enabling and Disabling Link/Seg Traps What is a Link Trap?Spmarun r4hwtr IP address community name Viewing and Configuring Link/Seg Traps for Hub Modules Configuring Link/Seg Traps for the RepeaterModule Traps Window Port Traps Window Viewing and Configuring Link/Seg Traps for PortsLink/Seg Traps Link/Seg Traps Enabling and Disabling Link/Seg Traps Repeater Redundancy Setting Network Circuit RedundancySpmarun r4red IP address community name Configuring a Redundant CircuitChannel X Redundancy Window Add Circuit Address Window Repeater Redundancy To set the Poll Interval Monitoring RedundancyDisplaying the Source Address List Source AddressingDisplaying the Source Address List Source Addressing Setting the Aging Time Setting the Hash TypeLocking Source Addresses Source Address Locking on Older Devices Configuring Source Address Traps Repeater-level Traps Module- and Port-level Traps Source Addressing Port Source Address Traps Window Finding a Source AddressClick on to exit the window Security Spmarun r4sec IP address SU community name What is LANVIEWSECURE?New definitions for station and trunk ports Secure address assignmentTrunk port security Full or partial security against eavesdropping Newest Lanviewsecure FeaturesContinuous learning mode Configurable violation responseLearned addresses reset Security on Non-LANVIEWSECUREMIMsForced non-secure status Configuring Security Security To assign secure addresses to a port Addresses Window Add MAC Address Window Boards with Multiple CachesTips for Successfully Implementing Eavesdropper Protection Resetting Learned AddressesEnabling Security and Traps Security Channel X Security Window Repeater-level Security and TrapsModule-level Security and Traps Channel X Module Security Window Channel X Port Security Window Port-level Security and TrapsSecurity Front Panel Redundancy Setting Front Panel RedundancySetting Front Panel Redundancy Add Circuit Address Window Front Panel Redundancy Setting Front Panel Redundancy EMM-E6 MIB Structure Ietf MIB SupportChassis MGR MIB ComponentsCtron Use Only Host ServicesIP Services Repeater One, Repeater Two, and Repeater ThreeRmon Host Rmon DefaultDistributed LAN Monitor MIB NavigatorBrief Word About MIB Components and Community Names EMM-E6 MIB Structure Index Index-2 Index-3 Index Index-4
Related manuals
Manual 64 pages 974 b