McAfee M4050 Troubleshooting Guide - Page 33

Checking whether a signature or software update was successful

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

McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform Checking whether a signature or software update was successful To see if your Sensor successfully received a signature update or software upgrade, you can use the status command as shown in the following procedure, or the downloadstatus command, described later in this chapter. To use the status command: 1 On the Sensor, type status at the command prompt before updating the signature set on the Sensor. Note the signature version. 2 Update the signature set on the Sensor using the Manager screens. 3 On the Sensor, again type status at the command prompt after the update from Manager is complete. Verify that the signature version number has incremented. The new signature version should match with the signature set version that has been updated from the Manager and applied to the Sensor. Checking status of a download or upload To see the progress of an upload or download, use the downloadstatus command. The downloadstatus command displays the status of various download/upload operations: signature, software image, and DoS profile downloads (from Manager to Sensor) and DoS profile and debug trace uploads (from Sensor to Manager). It also lists the number of times you have performed the operation, status of your previous attempt to perform the operation (including-if the operation failed-the cause of failure), and the time the command was executed. Do the following: On the Sensor, type downloadstatus at the command prompt. Conditions requiring a Sensor reboot The following situations either cause or require a Sensor reboot. You have two options for rebooting the Sensor. You can reboot the Sensor from the NSM interface, or you can issue the reboot CLI command. Note: A Sensor reboot can take up to five minutes.  Issuing the following CLI commands causes an automatic reboot of the Sensor:  resetconfig  deletesignatures  factorydefaults For more information on the Sensor CLI commands, see CLI Guide.  Changing the Sensor's management port IP address (IPv4 or IPv6) requires a manual reboot of the Sensor, before the change takes into effect. 24

  • 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
24
Checking whether a signature or software update was
successful
To see if your Sensor successfully received a signature update or software upgrade, you
can use the
status
command as shown in the following procedure, or the
downloadstatus
command, described later in this chapter.
To use the
status
command:
1
On the Sensor, type
status
at the command prompt before updating the signature
set on the Sensor. Note the signature version.
2
Update the signature set on the Sensor using the Manager screens.
3
On the Sensor, again type
status
at the command prompt after the update from
Manager is complete. Verify that the signature version number has incremented. The
new signature version should match with the signature set version that has been
updated from the Manager and applied to the Sensor.
Checking status of a download or upload
To see the progress of an upload or download, use the
downloadstatus
command.
The
downloadstatus
command displays the status of various download/upload
operations: signature, software image, and DoS profile downloads (from Manager to
Sensor) and DoS profile and debug trace uploads (from Sensor to Manager). It also lists
the number of times you have performed the operation, status of your previous attempt to
perform the operation (including—if the operation failed—the cause of failure), and the
time the command was executed.
Do the following:
On the Sensor, type
downloadstatus
at the command prompt.
Conditions requiring a Sensor reboot
The following situations either cause or require a Sensor reboot. You have two options for
rebooting the Sensor. You can reboot the Sensor from the NSM interface, or you can issue
the
reboot
CLI command.
Note:
A Sensor reboot can take up to five minutes.
Issuing the following CLI commands causes an automatic reboot of the Sensor:
resetconfig
deletesignatures
factorydefaults
For more information on the Sensor CLI commands, see
CLI Guide
.
Changing the Sensor’s management port IP address (IPv4 or IPv6) requires a manual
reboot of the Sensor, before the change takes into effect.