User guide

35
Release Notes for Cisco Router and Security Device Manager 2.5
OL-5009-20
Caveats
memory. The Cisco SDM Update feature uses RCP protocol to upload the new Cisco SDM files to
the router, but the RCP Server misinterprets the “flag” sent by the RCP Client for the above
mentioned file systems.
Workaround: If the current Cisco SDM files were loaded into flash memory, update to the new
Cisco SDM version by manually copying the new Cisco SDM files to the file system of the router
using a TFTP server. To make use of the automatic Cisco SDM Update feature, always install
Cisco SDM files on the flash disk or Compact Flash disks (disk0, disk1, disk2).
• CSCed31085
Cisco SDM should not get invoked from boot images such as kboot images on 72xx routers. Such
boot images are a subset of the Cisco IOS software and do not support all router functions.
Workaround: Boot the router with an Cisco SDM-supported Cisco IOS image, and then invoke
Cisco SDM. See Table 2 on page 7 for the Cisco IOS releases that Cisco SDM supports.
• CSCed26049
On 72xx platforms, encryption is not supported on PA-4T port adapters. Because the CLI does not
support crypto maps for these types of interfaces, Cisco SDM will fail to assign crypto maps to these
interfaces. The PA-4T port adapter will not support future compression and encryption features.
Workaround: Upgrade your 72xx router hardware to the 4t+ PA port adapter.
• CSCed30721
Whenever any unconfigured interface contains the description $FW_INSIDE$, on a router
configured with a firewall, adding a new NTP server will not modify the firewall ACLs to allow NTP
passthrough traffic. Instead, when the user edits the firewall’s outside interface in the Interfaces and
Connections window, Cisco SDM prompts the user to add the NTP passthrough traffic.
Workaround: Use the CLI to manually remove the description $FW_INSIDE$ from the
unconfigured interface.
• CSCin63613
If the interface used for the primary backup connection is configured for PPPoE encapsulation, the
backup connection will not function properly if the next hop address is specified during
configuration. A Cisco IOS caveat (CSCin64336) has been filed for this problem. If the interface
used for the primary backup connection is an Ethernet interface configured without encapsulation,
the backup connection will not function properly if the next hop address is not specified during
configuration.
Workaround: Do one of the following:
– For PPPoE connections: Do not provide the next hop IP address when you configure the primary
backup connection.
– For Ethernet connections without encapsulation: Do provide the next hop IP address when you
configure the primary backup connection.
• CSCin63415
If the WAN wizard is used to configure an analog modem connection as a primary backup
connection, and the analog modem connection is deleted, Cisco SDM may report that the interface
contains unsupported configuration parameters.
Workaround: Click Refresh on the Cisco SDM toolbar, and delete the connection.
• CSCed18560
The Interfaces and Connections window may display the Backup option in disabled state for
asynchronous interfaces on Cisco 831 and Cisco 837 routers. This will occur when the following
operations have been performed: