08-14-2014 04:05 PM - edited 08-14-2014 04:05 PM
I have two CP VMs configured in a cluster with a vIP using only the MGMT interface. I am testing radius pointed to the vIP and it looks like it bounces between the publisher and subscriber for authentication. I was watching the access tracker and couldn't see authenication requests come through even though they were suceeding. I found that I had to actually change the filter to both servers to see all the requests because it was bouncing between the two. I also verified that sometimes the subscriber would show the vIP active in the virutal IP settings.
These VMs are in an pretty robust ESX enviroment next to each other connected via 10Gb switches and I don't see any reported issues on the network or software side.
Solved! Go to Solution.
08-14-2014 04:06 PM
Do you have each individual server listed in your server group or just the VIP?
08-14-2014 04:16 PM
Right now I am just testing off of a cisco switch configured with just the single vIP address. I'm not aware of any radius load balancing features on clearpass? Or did you mean an Aruba controller?
08-14-2014 05:55 PM
What's the value you have setup to switchover to the backup ?
What version of ClearPass do you have installed ?
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
08-14-2014 07:06 PM
I could be a number of issues.
The main thing to look at is that the VIP is bouncing between the servers. That means that there is a connectivity issue or the radius is locking up.
1. Connectivity between the cluster.
2. If they are VMs make sure you built them to spec.
3. The VIP does not do any fail over it is designed to be for failover only....
4. The main purpose of the VIP in my opinion should be used if you need HTTP failover for guest and onboarding. I would use the capabilities of the NAS device for load balancing.
--Give Kudos: found something helpful, important, or cool? Click Kudos Star in a post.
--Problem Solved? Click "Accepted Solution" in a post.
08-18-2014 01:06 PM
Thanks for the help guys, I am still having issues with this.
The VMs are built to spec and haven't been moved to production so utilization is very very low. They live in a pretty robust vSphere enviorment and resources are not an issue. These ESX hosts are connected via 2 x 10Gb cables to Nexus Switches and currently host a variety of other production VMs that do not report or so any signs of network related problems.
I have done continuous ping tests to both VMs MGMT addresses as well as the vIP and I haven't seen a single drop. I'm not sure where to set the vIP settings for failover timeouts or preempt but right now they are set to default. The VMs live on different ESX hosts but in the same datacenter on the same Nexus switches (super close together).
I dont see any events in event viewer referencing the failover, here are the logs showing the server changing.
10.103.160.11 = Primary
10.103.160.12 = Secondary
vIP = 10.103.160.10 which is what the NADs are pointed to
|1.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:23|
|2.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:22|
|3.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:22|
|4.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:21|
|5.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:21|
|6.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:21|
|7.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:20|
|8.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:19|
|9.||10.103.160.12||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:01:19|
|10.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:08|
|11.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:07|
|12.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:06|
|13.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:06|
|14.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:05|
|15.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:04|
|16.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:03|
|17.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 12:00:03|
|18.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 11:59:57|
|19.||10.103.160.11||RADIUS||test||IT Cisco [Administra||ACCEPT||2014/08/18 11:59:56|