McAfee M4050 Troubleshooting Guide - Page 26

Setting the management port speed and duplex mode - manual

Get McAfee M4050 - Network Security Platform PDF manuals and user guides
UPC - 731944582832
View all McAfee M4050 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform Setting the management port speed and duplex mode 1 Set the speed of the Management port and whether the port should be set to half-or full-duplex. At the prompt, type: set mgmtport speed duplex where indicates 10 Mbps, indicates 100 Mbps, and indicates 1000 Mbps indicates half-duplex and indicates full-duplex. Note: 1000 Mbps is applicable only for M-series Sensors. I-Series sensors support only 10/100 Mbps for Management port Example: set mgmtport speed 100 duplex half Connectivity issues between the Sensor and other network devices The most common Sensor problems relate to configuration of the speed and duplex settings. Speed determination issues may result in no connectivity between the Sensor and the switch. Duplex mismatches A duplex mismatch (for example, one end of the link in full-duplex and the other in halfduplex) may result in performance issues, intermittent connectivity, and loss of communication. It can also create subtle problems in applications. For example, if a Web server is talking to a database server through an Ethernet switch with a duplex mismatch, small database queries may succeed, while large ones fail due to a timeout. Manually setting the speed and duplex to full-duplex on only one link partner generally results in a mismatch. This common issue results from disabling auto-negotiation on one link partner and having the other link partner default to a half-duplex configuration, creating a mismatch. This is the reason why speed and duplex cannot be hard-coded on only one link partner. If your intent is not to use auto-negotiation, you must manually set both link partners' speed and duplex settings to full-duplex. Valid auto-negotiation and speed configurations The table below summarizes all possible settings of speed and duplex for Sensors and Cisco catalyst switch ports. 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
McAfee® Network Security Platform 6.0
Troubleshooting Network Security Platform
17
Setting the management port speed and duplex mode
1
Set the speed of the Management port and whether the port should be set to half-or
full-duplex. At the prompt, type:
set mgmtport speed <10 | 100 | 1000> duplex <half | full>
where
<
10
> indicates 10 Mbps, <
100
> indicates 100 Mbps, and <
1000
> indicates 1000
Mbps
<
half
> indicates half-duplex and <
full
> indicates full-duplex.
Note:
1000 Mbps is applicable only for M-series Sensors. I-Series sensors
support only 10/100 Mbps for Management port
Example:
set mgmtport speed 100 duplex half
Connectivity issues between the Sensor and other network
devices
The most common Sensor problems relate to configuration of the speed and duplex
settings. Speed determination issues may result in no connectivity between the Sensor
and the switch.
Duplex mismatches
A duplex mismatch (for example, one end of the link in full-duplex and the other in half-
duplex) may result in performance issues, intermittent connectivity, and loss of
communication. It can also create subtle problems in applications. For example, if a Web
server is talking to a database server through an Ethernet switch with a duplex mismatch,
small database queries may succeed, while large ones fail due to a timeout.
Manually setting the speed and duplex to full-duplex on only one link partner generally
results in a mismatch. This common issue results from disabling auto-negotiation on one
link partner and having the other link partner default to a half-duplex configuration, creating
a mismatch. This is the reason why speed and duplex cannot be hard-coded on only one
link partner. If your intent is not to use auto-negotiation, you must manually set both link
partners' speed and duplex settings to full-duplex.
Valid auto-negotiation and speed configurations
The table below summarizes all possible settings of speed and duplex for Sensors and
Cisco catalyst switch ports.