McAfee M4050 Troubleshooting Guide - Page 27
Gigabit auto-negotiation (no link to connected device)
UPC - 731944582832
View all McAfee M4050 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 27 highlights
McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform Network Security Platform Configuration 10/100/1000 port (Speed/Duplex) Configuration of Switch Resulting Resulting (Speed/Duplex) Sensor Catalyst (Speed/Duplex) (Speed/Duplex) Comments 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Half-duplex 10 Mbps Half-duplex 10 Mbps Half-duplex 1000 Mbps Full-duplex AUTO 1000 Mbps Full-duplex AUTO AUTO 1000 Mbps Half-duplex No Link 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Half-duplex 100 Mbps Half-duplex No Link No Link 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Half-duplex 100 Mbps Half-duplex No Link Neither side establishes link, due to speed mismatch Correct configuration Correct Manual Configuration Link is established, but switch does not see any autonegotiation information from McAfee Network Security Platform and defaults to halfduplex when operating at 10/100 Mbps. Link is established, but switch does not see Fast Link Pulse (FLP) and defaults to 10 Mbps half-duplex. Neither side establishes link, due to speed mismatch. Gigabit auto-negotiation (no link to connected device) Gigabit Ethernet has an auto-negotiation procedure that is more extensive than that which is used for 10/100 Mbps Ethernet (per Gigabit auto-negotiation specification IEEE 802.3z1998). The Gigabit auto-negotiation negotiates flow control, duplex mode, and remote fault information. You must either enable or disable link negotiation on both ends of the link. Both ends of the link must be set to the same value or the link will not connect. If either device does not support Gigabit auto-negotiation, disabling Gigabit autonegotiation forces the link up. Troubleshooting a Duplex Mismatch with Cisco Devices When troubleshooting connectivity issues with Cisco switches or routers, verify that the Sensor and the switch/routers are using a valid configuration. The show intfport command on the Sensor CLI will help reveal errors. 18