McAfee M4050 Troubleshooting Guide - Page 34

Rebooting a Sensor via the Manager, Rebooting a Sensor using the reboot command, Sensor doesn’t boot

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 34 highlights

McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform  Certain internal software errors may cause the Sensor to reboot itself. See a description of Sensor fault messages later in this chapter. For more information on Operational Status Viewer, see System Status Monitoring Guide.  Enabling/disabling SSL requires a Sensor reboot.  Enabling/disabling parsing and detection of attacks in IPv6 traffic passing through the Sensor monitoring port requires a manual reboot of the Sensor. In the Manager user interface, you can enable/disable parsing and detection of attacks in IPv6 traffic with the Scan IPv6 traffic for attacks option from the IP Settings tab (IPS Settings/Sensor_Name > Advanced Scanning > IP Settings). For more information, see Configuring IP Settings for IPv4 and IPv6 traffic, IPS Configuration Guide.  Upgrading Sensor software requires a manual reboot of the Sensor. Rebooting a Sensor via the Manager The Reboot Sensor action restarts a Sensor. You perform this action in the Manager interface. To reboot a Sensor, do the following: 1 Select / Device List/ Device_Name Node>Physical Device>Reboot. 2 Click Reboot Now. Rebooting a Sensor using the reboot command The reboot command restarts a Sensor. You perform this action in the Sensor CLI: 1 At the prompt, type: reboot 2 Confirm the reboot. Sensor doesn't boot If you cannot get the Sensor to boot, try the following:  Check to ensure that the Sensor is powered on. Check the LEDs on the front of the Sensor.  Check the front panel LEDs to ensure that the Sensor temperature is normal. For more information on Sensor LEDs, see the Sensor Product Guide for your Sensor model.  If you receive an error message in the CLI: "OS not found," you may have a corrupted internal flash. If you see this error, contact Technical Support to obtain help in recovering the Sensor. Debugging critical Sensor issues CLI commands in the debug mode are used to improve supportability of the Sensor for better debugging of critical issues. This section is a detailed reference to the CLI debugging commands available in the debug mode. 25

  • 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
25
Certain internal software errors may cause the Sensor to reboot itself. See a
description of Sensor fault messages later in this chapter. For more information on
Operational Status Viewer, see
System Status Monitoring Guide
.
Enabling/disabling SSL requires a Sensor reboot.
Enabling/disabling parsing and detection of attacks in IPv6 traffic passing through the
Sensor monitoring port requires a manual reboot of the Sensor.
In the Manager user interface, you can enable/disable parsing and detection of
attacks in IPv6 traffic with the
Scan IPv6 traffic for attacks
option from the
IP Settings
tab (
IPS
Settings/Sensor_Name > Advanced Scanning > IP Settings
). For more information, see
Configuring IP Settings for IPv4 and IPv6 traffic
,
IPS Configuration Guide
.
Upgrading Sensor software requires a manual reboot of the Sensor.
Rebooting a Sensor via the Manager
The
Reboot Sensor
action restarts a Sensor. You perform this action in the Manager
interface.
To reboot a Sensor, do the following:
1
Select
<root admin domain>/ Device List/ Device_Name Node>Physical Device>Reboot.
2
Click
Reboot Now
.
Rebooting a Sensor using the reboot command
The
reboot
command restarts a Sensor. You perform this action in the Sensor CLI:
1
At the prompt, type:
reboot
2
Confirm the reboot.
Sensor doesn’t boot
If you cannot get the Sensor to boot, try the following:
Check to ensure that the Sensor is powered on. Check the LEDs on the front of the
Sensor.
Check the front panel LEDs to ensure that the Sensor temperature is normal. For
more information on Sensor LEDs, see the
Sensor
Product Guide
for your Sensor model.
If you receive an error message in the CLI: “OS not found,” you may have a corrupted
internal flash. If you see this error, contact Technical Support to obtain help in
recovering the Sensor.
Debugging critical Sensor issues
CLI commands in the debug mode are used to improve supportability of the Sensor for
better debugging of critical issues. This section is a detailed reference to the CLI
debugging commands available in the debug mode.