I've got 2 local controllers setup in an HA pair conneced to Juniper 4500's. I've had a problem with the APs jumping back and forth at random times during the week. None of the devices ever go down but its triggering a storm control at certain times when the error happens. Probably all the reauths.
Looking through the logs, I found this error repeating. I've noticed that it corresponds withe the errors on the Juniper and the APs jumping.
Could any configuration be causing this before I contact TAC?
Jan 5 13:28:17 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 7 00:31:13 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 7 00:31:13 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 7 00:31:13 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 7 00:31:13 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1624: link becomes ready
Jan 7 00:31:13 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1600: link becomes ready
Jan 7 16:47:59 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 7 16:47:59 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 7 16:47:59 KERNEL: 7:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 8 04:46:53 KERNEL: 1:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 8 04:46:53 KERNEL: 1:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 8 04:46:53 KERNEL: 1:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 8 06:52:43 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 8 06:52:43 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 8 06:52:43 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 8 06:52:43 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1624: link becomes ready
Jan 8 06:52:43 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1600: link becomes ready
Jan 8 06:55:09 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 8 06:55:09 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 8 06:55:09 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1600: link becomes ready
Jan 8 06:55:09 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 8 06:55:09 KERNEL: 6:<6>ADDRCONF(NETDEV_CHANGE): eth1.1624: link becomes ready
Jan 8 16:46:31 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.3218: link becomes ready
Jan 8 16:46:31 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.3216: link becomes ready
Jan 8 16:46:31 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.3220: link becomes ready
Jan 9 08:45:46 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 9 08:45:46 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 9 08:45:46 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.1624: link becomes ready
Jan 9 08:45:46 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.1600: link becomes ready
Jan 9 08:45:46 KERNEL: 0:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 9 10:38:10 KERNEL: 3:<6>ADDRCONF(NETDEV_CHANGE): eth1.1620: link becomes ready
Jan 9 10:38:10 KERNEL: 3:<6>ADDRCONF(NETDEV_CHANGE): eth1.1608: link becomes ready
Jan 9 10:38:10 KERNEL: 3:<6>ADDRCONF(NETDEV_CHANGE): eth1.1600: link becomes ready
Jan 9 10:38:10 KERNEL: 3:<6>ADDRCONF(NETDEV_CHANGE): eth1.1616: link becomes ready
Jan 9 10:38:10 KERNEL: 3:<6>ADDRCONF(NETDEV_CHANGE): eth1.1624: link becomes ready
(Aruba-Local1-DC-35K) #