20 CHAPTER 2: RELEASE HIGHLIGHTSSampleConfigurations andSystem BehaviorThis section describes how the system behaves in certain featureconfigurations. Refer to Table 3 when reading the correspondingparagraphs below.Configuration APorts autonegotiate connections according to the IEEE 802.3uspecification. Error conditions are not monitored. No alerts are sent andpreventive actions are not taken. If the remote port (the port to which theswitch is connected) is fixed in full duplex mode or uses a non-compliantversion of autonegotiation, duplex mismatches are likely to occur, causingproblems for the link, switch, and portions of the network that rely onthat switch. However, if standard autonegotiation is enabled on theswitch and the remote port, the speed and duplex modes will be setcorrectly.Configuration BPorts autonegotiate connections according to the IEEE 802.3uspecification. The system monitors specified ports for errors and sendsalerts through traps and console messages. If the remote port is fixed infull duplex mode or uses a non-compliant version of autonegotiation,duplex mismatches are possible. However, the Port Monitoring featurecan partition ports with high error rates (which, incidentally, may also becaused by factors other than duplex mismatches such as damagedcabling).The error threshold is fixed in system software; it is not user-configurable.The initial time period in which a port is partitioned (disabled) is 30seconds. When the system reenables the port, it also immediatelymonitors the error conditions. If the error threshold is reached again, theport is partitioned again. The time that the port is partitioned increaseswith each incidence, up to a maximum of 5 minutes.Table 3 Sample ConfigurationsStandardAutonegotiationEnabledPortMonitoringEnabledAdvancedAutonegotiationEnabledConfiguration A Yes No NoConfiguration B Yes Yes NoConfiguration C Yes No YesConfiguration D No Yes NoConfiguration E No No Yes
