Cisco Cisco IPS 4255 Sensor Notas de publicación

Descargar
Página de 38
 
36
Release Notes for Cisco Intrusion Prevention System 7.0(6)E4
OL-25700-01
  Caveats
sensor(config-hos)#
Troubleshooting Password Recovery
To troubleshoot password recovery, pay attention to the following:
You cannot determine whether password recovery has been disabled in the sensor configuration 
from the ROMMON prompt, GRUB menu, switch CLI, or router CLI. If password recovery is 
attempted, it always appears to succeed. If it has been disabled, the password is not reset to cisco
The only option is to reimage the sensor.
You can disable password recovery in the host configuration. For the platforms that use external 
mechanisms, such as the AIM IPS and NME IPS bootloader, ROMMON, and the maintenance 
partition for the IDSM2, although you can run commands to clear the password, if password 
recovery is disabled in the IPS, the IPS detects that password recovery is not allowed and rejects the 
external request.
To check the state of password recovery, use the show settings | include password command. 
When performing password recovery on the IDSM2, you see the following message: 
Upgrading 
will wipe out the contents on the storage media
. You can ignore this message. Only the 
password is reset when you use the specified password recovery image.
For More Information
For more information on reimaging sensors, refer to 
For the procedure for disabling password recovery, see 
.
For the procedure for verifying the state of password recovery, see 
Caveats
This section lists the resolved caveats, relevant unresolved caveats, and contains the following topics:
Resolved Caveats
The following known issues have been resolved in the 7.0(6)E4 release:
CSCsy29638—Sensor should alert user when going into bypass due to reputation update
CSCta43555—Network Security Level not functioning
CSCtc80016—packet capture can lock up sensor
CSCte50759—sensorApp aborts during signature update
CSCtf02842—ntp daemon may lose synchronization with server
CSCtg22575—Unexpected Behavior using Exact-Match-Offset In Atomic ip