|
Initially, Ethernet switches work like Ethernet hubs, with all traffic being echoed to all ports. However, as the switch "learns" the end-points associated with each port, it ceases to send non-broadcast traffic to ports other than the intended destination. In this way, Ethernet switching can allow the full wire speed of Ethernet to be used by any given pair of ports on a single switch. Since packets are typically only delivered to the port they are intended for, traffic on a switched Ethernet is slightly less public than on shared-medium Ethernet. Despite this, switched Ethernet should still be regarded as an insecure network technology, because it is easy to subvert switched Ethernet systems by means such as ARP spoofing and MAC flooding, as well as for network administrators to use monitoring functions to copy traffic from the network. When only a single device (anything but a hub) is connected to a switch port, full-duplex Ethernet becomes possible. With only two devices on the Ethernet segment, collision detection is not required and both devices can transmit at the same time. This doubles the aggregate bandwidth of the link (although the bandwidth for each direction remains the same), but more importantly the lack of collisions allows nearly the entire bandwidth to be used. It is essential that both the switch port and the device connected to it use the same duplex setting. Most 100BASE-TX and 1000BASE-T devices support auto-negotiation, where they signal the speed and duplex to use. However, if auto-negotiation is disabled or not supported, the duplex must be set by auto-detection or manually on both the switch port and the device to prevent duplex mismatch, a common cause of problems with Ethernet (the device set to half-duplex will report late collisions and the device set to full-duplex will report runts). Many low-end switches lack the ability for manual speed and duplex setting, so ports always try to auto-negotiate. When auto-negotiation is enabled but does not succeed (e.g., because the other device does not support it), auto-detection sets the port to half-duplex. The speed can be automatically sensed, so connecting a 10BASE-T device to a 10/100 switch port with auto-negotiation enabled will correctly result in a half-duplex 10BASE-T connection. But connecting a device configured for full duplex 100 Mbit operation to a switch port configured to auto-negotiate (or vice versa) will result in a duplex mismatch. Even when both ends of a cable are capable of autosensing speed and duplex settings, it is very common for them to guess wrongly and fall back to 10 Mbit mode. Therefore, if performance is worse than expected, one should check whether a computer has put itself into 10 Mbit mode, and if one knows the other end is 100 Mbit capable, manually force it into the correct mode. Problems also occur when two nodes try to operate at speeds faster than the cable can support, such as attempting 100BASE-T on Category 3 cable or 1000BASE-T on Category 3 or Category 5 cable. Unlike ADSL and conventional dialup modems, which perform an elaborate "training" sequence to determine the maximum data rate supported by the link, Ethernet nodes merely exchange speed capability messages and choose the highest speed supported by both ends. No attempt is made to see if the link can actually run at that speed, so if it's beyond the cable's capability, then the link will fail. The solution is to force either or both ends down to a speed supported by the cable.
The following sections provide a brief summary of all the official ethernet media types. In addition to these official standards, many vendors have implemented proprietary media types for various reasons—often to support longer distances over fiber optic cabling. 很多以太网卡和交换设备都支持多速率,设备之间通过自动协商设置最佳的连接速度和双工方式。如果协商失败,多速率设备就会探测另一方使用的速率但是默认为半双工方式。10/100以太网端口支持10BASE-T和100BASE-TX。10/100/1000支持10BASE-T,100BASE-TX,和1000BASE-T。 早期以太网varieties
10 Mbps以太网
|
信息搜索
相关新闻
以太网(Ethernet)
- 添加日期:2006-2-20 16:47:54 来源:本站原创 点击:
A
D
