SEARCH DOCS
info central: your site for Collage technical info
  CASSATT.COM   INFO CENTRAL
ACTIVE RESPONSE 5.0 TOPICS BLUEPRINTS TROUBLESHOOTING DOC INDEX


Common Setup Mistakes
Application nodes
Cassatt Active Response Controller
Control nodes
Network
arrow Virtualization Manager
Diagnostics
troubleshooting:

 

Common Setup Mistakes

Topic

Common Mistake

Description/Solution

Reserved IP address range

Assigning a static IP address from the Cassatt Active Response DCHP range to servers or other devices that should not be controlled by Cassatt Active Response.

If your site has devices with static IP addresses that are inside the Cassatt Active Response DHCP range, reserve those addresses from the Controller so that Cassatt Active Response does not assign those addresses to servers issuing DHCP requests.

See: Network Addresses: Calculating Requirements

Not setting one of the control node power controllers to a static IP address.

If you fail to set a static IP address for control nodes, the following errors can occur:

  • A control node can be discovered as an application node.
  • Failover does not work.

See: Network Addresses: Calculating Requirements

Booting order of application nodes

Specifying the hard drive in the boot order for a dynamically allocated resource.

If the network boot fails for some reason, and the hard drive has an OS loaded on it and it is in the boot order, Cassatt Active Response attempts to boot that OS. Depending on the OS, and whether it successfully boots, unexpected things can result.

We recommend that you disable booting from the hard drive and specify "Network" first in the boot order. Specifying "Network" optimizes the speed with which Cassatt Active Response discovers nodes and incorporates them into the Cassatt Active Response free pool. If you are operating in a test environment or you expect frequent administrative access to the application nodes, you can set the order to 1) Floppy, 2) CD-ROM 3) Network.

See:
Application Node Setup: Dell

Application Node Setup: HP

Application Node Setup: IBM

Number of application nodes to boot

Booting too many application nodes at a time.

For best performance, do not boot more than a rack of application nodes at a time.

Power controller firmware

Using an unsupported version of the power controller firmware.

If you are leveraging Cassatt Active Response's remote management feature, you must use a supported version of the power controller firmware. See: Recommended Hardware and Firmware

Cassatt Active Response Controller

 

Running the Controller in more than one browser window on the same computer.

Some older browsers do not maintain different sessions per browser window (for example, older Mozilla versions). If you run Cassatt Active Response in more than one browser window, you may experience synchronization issues between the two windows and other undesirable behaviors. We recommend opening only one browser session of Cassatt Active Response at a time.

When adding user accounts, not setting up a user account on the standby control node (if using dual-control nodes).

If you are using dual-control nodes, you must set up user accounts for both the active and standby control nodes to accommodate the case of failover; if you don't, users may not be able to log into the Controller if a failover occurs.
See: User Authentication and Management.

Power controller user ids and passwords

Forgetting to create user ids and passwords on power controllers or having a mismatch.

If you forget to set power controller user ids and passwords, or have a mismatch between what was set on the power controllers and what was set during Cassatt Active Response installation, nodes will not be discovered and Cassatt Active Response won't be able to manage the application nodes.

NOTE: Power controller user ids/ passwords can be set during Cassatt Active Response installation or in the Controller.

Cassatt Active Response files

Using Linux commands to manage Cassatt Active Response instead of the Controller.

Using Linux commands on files that belong to Cassatt Active Response can cause problems. For example, using the rm command to remove an image can disrupt services and leave behind clutter. Editing image files can also affect upgrade. Because the Cassatt Active Response Controller has all the utilities you need to manage Cassatt Active Response-related files, it is the recommended utility.

Application nodes

Topic

Description

Discovery

General

IBM BladeCenter

HP hardware with iLO remote management

IBM servers using RSA II controller

Inventory

Inventory fails after fixing switches on BCMM

Delete nodes

Deleting IBM blades causes them to rediscover

Permission problems

SPARC/Solaris nodes fail with permission problems

Failure

Power operation fails on properly configured device

Boot failure

Nodes on their own application network do not boot

HP DL 360 intermittently fail on boot

Cassatt Active Response Controller

Topic

Description

Alerts log

Number of alerts in Alerts log tab and alerts list do not match

/usr files

Conflicts in /usr when updating Solaris 9 image

Refresh failure

Controller pages fail to refresh

Control nodes

Topic

Description

Failover

Continual failover

Disabled control node clusters

Network

Topic

Description

Network

BladeCenter's internal network interfaces in "err-disabled" state

Virtualization Manager

Topic

Description

VMs, general

Diagnosing and repairing virtual application nodes

ESX virtual application nodes fail to boot

ESX VM fails to boot when a VMware Console is attached

SAN

LUN disconnection results in virtual application node failure

Running out of file space on the SAN

Failures on VM host tier nodes

Ping monitoring shows false failures

Activation: ESX image

An ESX image does not activate completely

Capture

"Exporting disk" errors when capturing Windows images

Delete tier

Deleting a VM guest tier

Diagnostics

Seeing unusual behaviors in Cassatt Active Response? Cassatt Active Response provides a tool, ccdiagnostic, which packages up system configuration information, Cassatt Active Response log files, and system log files, and sends them via ftp to the Cassatt Customer Support site for analysis. For more information, see: Sending Log Files to Cassatt Customer Support.

If you have other difficulties with your Cassatt Active Response software, please contact our Customer Support organization at support@cassatt.com.