Hi Cesar - This may not be the answer to your question but we've had problems with our CASes where, after rebooting them, they will not be pingable or reconnect to the network. The solution, as discovered by me after an all nighter where I rebuild one CAS twice, was to clear the ARP cache on the 6500 switch they were attached to. Apparently there's a known bug where CASes using Virtual Gateways will have this problem. Now whenever I bring down a CAS I always clear the ARP cache on the switch to get it back running. Once running, the issue will not return.
Just thought this might help. - Sean ---- Sean Hennessey Networking and Information Security Systems Administrator The University of Portland -----Original Message----- From: Cisco Clean Access Users and Administrators [mailto:[EMAIL PROTECTED] On Behalf Of Cesar A Nau Sent: Thursday, August 21, 2008 10:13 AM To: [email protected] Subject: Cannot access Clean Access Server after reinstalling software from CD Hello all, I've just recently encountered a problem while setting up a pair of Clean Access servers. After installing via CD and configuring each server, I am unable to communicate to the servers via eth0 (NIC1). I've cleanly installed CCA v4.1.3.1 of the software now on 4 different hp Proliant GL360 servers, and they all experience the same issue. I cannot ping the server via eth0. If I connect the servers via eth1 (NIC2), I am able to ping them. The odd thing is that all 4 servers have been used previously in production with CCA, and I never had this problem with any of these servers before. It is almost as if eth0 is disabled. I have tried ifconfig eth0 up / down / and up again to no avail. I stopped by Cisco's discussion forums and noticed that a couple of individuals have experienced this problem before, but I was not able to find a solution. If anyone can help me resolve this issue, I would greatly appreciate it. Cesar A. Nau Help Desk Manager Fordham University / Fordham IT 718.817.4598 [EMAIL PROTECTED] www.fordham.edu/ITHelp
