You should be OK adding the node. The 'cleanup was not done' indicates that
teh cluster wizard was unable to connect to the evicted node and make
changes on it. Not a real problem.

Make sure you have run the SQL installer and removed the node from SQL as
well. Evicting the node rom the cluster does not clean up the SQL
installation. See 'Maintaining a Failover Cluster' in BOL for details on
how to clean up a SQL installation when you have evicted a node. If you do
not do this step, installing SQL to the 'new' node will likely fail.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Pat Hall" <PatHall (AT) discussions (DOT) microsoft.com> wrote

the last win2k node to rebuild it as win2k3 and upgrade the drivers/firmware
for the HBA connecting to the shared storage in the SAN as well. I got a
message when the node was evicted that said "the node was evicted but
cleanup was not done". Will I have any problems with the cluster or adding
the new node to the cluster?

Yes you can remove the node from SQL even after it has been evicted from the
cluster. You will have to manually uninstall SQL from the node if you don't
do a complete OS reload on that hardware. Treat it as replacing a failed
node and follow the BOL instructions. You will likely get some errors, but
you can clean up the remaining node(s). If you don't clean them up using
the SQL install tool, subsequent installs will still think that node is part
of the cluster. and try to install to it.

--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com

I support the Professional Association for SQL Server
www.sqlpass.org

"Pat Hall" <PatHall (AT) discussions (DOT) microsoft.com> wrote

Win2k3 and the evicted node is win2k. What are my problems likely to be
when I try to add the node back?