Wireless Access

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Hi,
on first with poor health:

(lzarubamc1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer 192.168.96.53 128 L3-Connected CONNECTED (Member, last HBT_RSP 65ms ago, RTD = 0.508 ms)
self 192.168.96.52 128 N/A CONNECTED (Leader)

and on the second:

(lzarubamc2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 192.168.96.53 128 N/A CONNECTED (Member)
peer 192.168.96.52 128 L3-Connected CONNECTED (Leader, last HBT_RSP 39ms ago, RTD = 0.000 ms)
Original Message:
Sent: Oct 15, 2022 07:22 PM
From: Colin Joseph
Subject: MC 7210 poor health

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

This is your problem: peer 192.168.96.53 128 L3-Connected CONNECTED  

There is probably a client VLAN that is not connected between the clusters in your controller and you need to either (1) exclude the VLAN from the cluster profile or (2) make sure the controllers can see each other on that VLAN.

Use the command " show lc-cluster vlan-probe status" to find out which VLAN that is.  L3-Connected means that your cluster doesn't have a proper failover functionality.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Oct 16, 2022 01:53 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Hi,
on first with poor health:

(lzarubamc1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer 192.168.96.53 128 L3-Connected CONNECTED (Member, last HBT_RSP 65ms ago, RTD = 0.508 ms)
self 192.168.96.52 128 N/A CONNECTED (Leader)

and on the second:

(lzarubamc2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 192.168.96.53 128 N/A CONNECTED (Member)
peer 192.168.96.52 128 L3-Connected CONNECTED (Leader, last HBT_RSP 39ms ago, RTD = 0.000 ms)
Original Message:
Sent: Oct 15, 2022 07:22 PM
From: Colin Joseph
Subject: MC 7210 poor health

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Okay, I fixed that and now I have L2-connected on both controllers but at the GUI controller 1 is still on poor health.

(arubamc1) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.53 27784 0 5 0 5 13 0 L2 Conn 3/ 3

(arubamc2) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.52 27773 0 13 0 13 5 0 L2 Conn 2/ 2


Original Message:
Sent: Oct 16, 2022 07:48 AM
From: Colin Joseph
Subject: MC 7210 poor health

This is your problem: peer 192.168.96.53 128 L3-Connected CONNECTED

There is probably a client VLAN that is not connected between the clusters in your controller and you need to either (1) exclude the VLAN from the cluster profile or (2) make sure the controllers can see each other on that VLAN.

Use the command " show lc-cluster vlan-probe status" to find out which VLAN that is.  L3-Connected means that your cluster doesn't have a proper failover functionality.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 16, 2022 01:53 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Hi,
on first with poor health:

(lzarubamc1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer 192.168.96.53 128 L3-Connected CONNECTED (Member, last HBT_RSP 65ms ago, RTD = 0.508 ms)
self 192.168.96.52 128 N/A CONNECTED (Leader)

and on the second:

(lzarubamc2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 192.168.96.53 128 N/A CONNECTED (Member)
peer 192.168.96.52 128 L3-Connected CONNECTED (Leader, last HBT_RSP 39ms ago, RTD = 0.000 ms)
Original Message:
Sent: Oct 15, 2022 07:22 PM
From: Colin Joseph
Subject: MC 7210 poor health

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Please see if you can drill down using this article:  https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=b04a34e1-4410-4993-98b0-ece2375a8888

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Oct 17, 2022 06:19 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Okay, I fixed that and now I have L2-connected on both controllers but at the GUI controller 1 is still on poor health.

(arubamc1) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.53 27784 0 5 0 5 13 0 L2 Conn 3/ 3

(arubamc2) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.52 27773 0 13 0 13 5 0 L2 Conn 2/ 2


Original Message:
Sent: Oct 16, 2022 07:48 AM
From: Colin Joseph
Subject: MC 7210 poor health

This is your problem: peer 192.168.96.53 128 L3-Connected CONNECTED

There is probably a client VLAN that is not connected between the clusters in your controller and you need to either (1) exclude the VLAN from the cluster profile or (2) make sure the controllers can see each other on that VLAN.

Use the command " show lc-cluster vlan-probe status" to find out which VLAN that is.  L3-Connected means that your cluster doesn't have a proper failover functionality.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 16, 2022 01:53 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Hi,
on first with poor health:

(lzarubamc1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer 192.168.96.53 128 L3-Connected CONNECTED (Member, last HBT_RSP 65ms ago, RTD = 0.508 ms)
self 192.168.96.52 128 N/A CONNECTED (Leader)

and on the second:

(lzarubamc2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 192.168.96.53 128 N/A CONNECTED (Member)
peer 192.168.96.52 128 L3-Connected CONNECTED (Leader, last HBT_RSP 39ms ago, RTD = 0.000 ms)
Original Message:
Sent: Oct 15, 2022 07:22 PM
From: Colin Joseph
Subject: MC 7210 poor health

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Problem solved.
There was a WAN Uplink configured with no connection. Who ever did that in the past..
After deleting health is good now.
Original Message:
Sent: Oct 17, 2022 11:34 AM
From: Colin Joseph
Subject: MC 7210 poor health

Please see if you can drill down using this article:  https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=b04a34e1-4410-4993-98b0-ece2375a8888

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 17, 2022 06:19 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Okay, I fixed that and now I have L2-connected on both controllers but at the GUI controller 1 is still on poor health.

(arubamc1) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.53 27784 0 5 0 5 13 0 L2 Conn 3/ 3

(arubamc2) *#show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 192.168.96.52 27773 0 13 0 13 5 0 L2 Conn 2/ 2


Original Message:
Sent: Oct 16, 2022 07:48 AM
From: Colin Joseph
Subject: MC 7210 poor health

This is your problem: peer 192.168.96.53 128 L3-Connected CONNECTED

There is probably a client VLAN that is not connected between the clusters in your controller and you need to either (1) exclude the VLAN from the cluster profile or (2) make sure the controllers can see each other on that VLAN.

Use the command " show lc-cluster vlan-probe status" to find out which VLAN that is.  L3-Connected means that your cluster doesn't have a proper failover functionality.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 16, 2022 01:53 AM
From: Dirk Rzimski
Subject: MC 7210 poor health

Hi,
on first with poor health:

(lzarubamc1) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
peer 192.168.96.53 128 L3-Connected CONNECTED (Member, last HBT_RSP 65ms ago, RTD = 0.508 ms)
self 192.168.96.52 128 N/A CONNECTED (Leader)

and on the second:

(lzarubamc2) *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "lzcluster"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 20%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 50
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 192.168.96.53 128 N/A CONNECTED (Member)
peer 192.168.96.52 128 L3-Connected CONNECTED (Leader, last HBT_RSP 39ms ago, RTD = 0.000 ms)
Original Message:
Sent: Oct 15, 2022 07:22 PM
From: Colin Joseph
Subject: MC 7210 poor health

Go on the commandline of one controller and type "show lc-cluster group-membership" and see if it sees the other controller.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?

Hi, have you defined a lacp port-channel and ended up using just 1 cable (like you metion)? 

If you have a 2-port lacp defined and only 1 cable connected, the controller may tell you poor healt.


I hope this helps
Original Message:
Sent: Oct 15, 2022 05:22 PM
From: Dirk Rzimski
Subject: MC 7210 poor health

hi gents,
I am running a two node cluster of 7210 on 8.6.0.17 with 250 access points.
Each controllers is connected with one interface to a data center switch.
But one controllers is on poor health saying: "Controller has at least one uplink with poor health".
Looking on the switch interface everything is looking fine at my pov.

How is poor health for one uplink defined? What needs to happen on an interface to get rated as poor?

I just updated from 8.6.0.9 to 8.6.0.17 but nothing changed.
Looking at the mobility conductor dashboard, it says no client is connected to the controller with poor health but 177 are connected to the one with good health. Is that normal or are the clients getting connected to the good controller because the other one is on poor health?