9-8
User Guide for Cisco Security Manager 4.4
OL-28826-01
Chapter 9 Troubleshooting Device Communication and Deployment
Resolving Red X Marks in the Device Selector
On the Device Properties General page, ensure that the hostname, domain name, and IP address are
correct. Keep in mind that the Hostname and Accounts and Credentials policies for the device define
the actual names and credentials that get configured on the device. However, the policies are not
used for device communication. If you make changes to the policies that affect the credentials you
are using for device communication, you must also manually update the device properties.
Make sure DNS names can be resolved from the Security Manager server. You might need to fix the
DNS settings on the server.
Check the credentials for the device in Security Manager and ensure that they are correct and that
there is a route between the server and device. Right-click the device, select Device Properties,
select the Credentials tab, and click the Test Connectivity button. If the connection fails, check
error messages to determine whether the problem is connectivity or credentials. Update the
credentials in the device properties if necessary.
When adding new devices the credentials are defined within the New Device wizard if your method
of adding the device requires credentials. Keep the following in mind:
The primary credentials are used for SSH and Telnet connections.
The HTTP/HTTPS credentials are used for HTTP and SSL connections unless you select Use
Primary Credentials, in which case the primary credentials are also used for these
connections.
Related Topics
Adding Devices to the Device Inventory, page 3-6
Understanding Device Communication Requirements, page 2-1
Chapter 2, “Preparing Devices for Management”
Device Communication Page, page 11-17
Device Credentials Page, page 3-44
Resolving Red X Marks in the Device Selector
If a device is marked with a red X in the device selector in Device view, it means that the Auto Update
Server (AUS) or Configuration Engine server assignment for the device was lost during an upgrade from
a Security Manager release prior to 3.2.0. AUS and Configuration Engines are not migrated during an
upgrade from 3.1.x, and devices managed by them need to be reassigned to them after the upgrade using
the following procedure.
Step 1 Do one of the following in Device view:
From the Device selector, right-click a device with a red X icon, then select Update Server Info.
Click any red X icon in the device selection tree. A warning message is displayed stating that AUS
and Configuration Engine information was not migrated after the upgrade process. Click Yes to add
these servers manually.
The Device Server Assignment dialog box opens.
Step 2 From the Available Devices list, select all the devices that use the same AUS or Configuration Engine
server and click >> to move them to the selected list. The Available Devices list includes all devices that
are managed by AUS or Configuration Engine that are marked with a red X.