McAfee M4050 Troubleshooting Guide - Page 24

Starting your troubleshooting, Difficulties connecting Sensor and Manager, Network connectivity - image

Page 24 highlights

McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform Starting your troubleshooting Before you get too deep into troubleshooting techniques, it is a good practice to consider the following questions:  Were there physical changes to your network that occurred recently?  If another device is placed in the Sensor's position, does that device receive traffic?  If the Sensor is in L2 mode, are your network's services still affected?  Are you using approved McAfee GBICs or SFPs or XFPs with your Sensor? [For a list of approved hardware, see McAfee KnowledgeBase article KB56364 (Go to http://mysupport.mcafee.com/Eservice/, and click Search the KnowledgeBase)] Difficulties connecting Sensor and Manager If you experience problems getting the McAfee® Network Security Manager (Manager) and Sensor to communicate, see if one of the following situations may be the cause. Network connectivity  Ensure that the Sensor and Manager server have power and are appropriately connected to the network.  Verify the link LEDs on both devices to indicate they have an active link.  Ping the Sensor and Manager server to ensure that they are available on the network. Inconsistency in Sensor and Manager configuration  Check to ensure that the Sensor name that was entered in the CLI is identical to that entered in the Manager. Ensure the same for the shared secret key value. If these values do not match, the two cannot communicate. Note: The Sensor name is case-sensitive.  Check the network addresses for the Manager, the Manager's gateway, and the Sensor to ensure everything is configured correctly by typing show at the Sensor CLI command prompt. Software or signature set incompatibility Check to ensure that the Sensor software image, Manager software version, and signature set version are compatible.  A compatibility matrix is provided in the release notes that accompany each product release. 15

  • 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
15
Starting your troubleshooting
Before you get too deep into troubleshooting techniques, it is a good practice to consider
the following questions:
Were there physical changes to your network that occurred recently?
If another device is placed in the Sensor’s position, does that device receive traffic?
If the Sensor is in L2 mode, are your network’s services still affected?
Are you using approved McAfee GBICs or SFPs or XFPs with your Sensor? [For a list
of approved hardware, see McAfee KnowledgeBase article KB56364 (Go to
, and click
Search the KnowledgeBase
)]
Difficulties connecting Sensor and Manager
If you experience problems getting the McAfee
®
Network Security Manager (Manager) and
Sensor to communicate, see if one of the following situations may be the cause.
Network connectivity
Ensure that the Sensor and Manager server have power and are appropriately
connected to the network.
Verify the link LEDs on both devices to indicate they have an active link.
Ping the Sensor and Manager server to ensure that they are available on the network.
Inconsistency in Sensor and Manager configuration
Check to ensure that the Sensor name that was entered in the CLI is identical to that
entered in the Manager. Ensure the same for the shared secret key value. If these
values do not match, the two cannot communicate.
Note:
The Sensor name is case-sensitive.
Check the network addresses for the Manager, the Manager’s gateway, and the
Sensor to ensure everything is configured correctly by typing
show
at the Sensor CLI
command prompt.
Software or signature set incompatibility
Check to ensure that the Sensor software image, Manager software version, and signature
set version are compatible.
A compatibility matrix is provided in the release notes that accompany each product
release.