Bob,
If the secondary server is active, then I wouldn't worry about changing
any failover settings. To check this goto an SSH session and run:
/perfigo/common/bin/fostate.sh
If it says "My node is active" then don't worry about the failover
settings. There is something else going wrong on the secondary server.
Make sure the DHCP scopes are defined on that second CAS. If so, check
the DHCP logs at:
/var/log/dhcplog
And see if there are errors.
Nate
Bob Lavner wrote:
Bruce we are running 4.1.2. I have shut down CCA server one (primary) and
left CCA server 2 running. Should I cleanly shut down both? Then start up
CCA server2? I am surprised this is not working. Our students are not
happy...
Bob
On 4/7/08 12:45 PM, "Osborne, Bruce W. (NS)" <[EMAIL PROTECTED]> wrote:
Bob,
If the failed server is offline, reboot the other one. If the HA pair
are not directly connected, but thorough a dedicated vlan, I have seen
HA only work if the active CAS is cleanly shut down. Disaster failover
does not appear to work, at least in 4.1.1, unless there is a direct
connection. Perhaps it needs the linkup / linkdown.
Bruce Osborne
Liberty University
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Lavner
Sent: Monday, April 07, 2008 12:40 PM
To: [email protected]
Subject: [CLEANACCESS] CCA server forced failover
Due to a hardware problem on the Primary CCA server, it failed and our
students cannot get DHCP info thus not getting out to the network. The
secondary CCA server is not performing this task. Is there a way to
force
the secondary to perform as the primary? Can this be done through CLI?
Any
info would be appreciated.
Bob Lavner
Network/Server Manager
Assumption College
508-767-7006
[EMAIL PROTECTED]
