Controllerless Networks

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

generally I would always disable spanning tree on the controllers, I think it is enabled by default.

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

Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

@cjoseph attached is the diagram together with interface configs of core switch and controller. ​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

We have already disconnected the Controller as it was causing  loop. Originally the controller was working fine before we upgraded the software version from version 6.5.X.X to version 8.X.X .Upgrading the firmware also wiped out the controller configs. So we had to build the config again on the controller,,  Initially, we had it configured as trunk ports(original configs) between core switch and controller but that caused an outage. We then configured the interfaces as access ports between core switch and controller, but that also caused an outage.
Original Message:
Sent: Oct 12, 2022 03:13 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

Did the log on the switch have any clues?

------------------------------
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 12, 2022 03:28 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

We have already disconnected the Controller as it was causing  loop. Originally the controller was working fine before we upgraded the software version from version 6.5.X.X to version 8.X.X .Upgrading the firmware also wiped out the controller configs. So we had to build the config again on the controller,,  Initially, we had it configured as trunk ports(original configs) between core switch and controller but that caused an outage. We then configured the interfaces as access ports between core switch and controller, but that also caused an outage.
Original Message:
Sent: Oct 12, 2022 03:13 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

Here's the syslog from core switch.



I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk6 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/6 is Blocked by LACP
I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk2 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/2 is Blocked by LACP
I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk7 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/7 is Blocked by LACP
I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk8 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/8 is Blocked by LACP
I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk12 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/12 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/5 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/9 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/4 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/3 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/11 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/1 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/6 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/13 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/2 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/7 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/8 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/12 is Blocked by LACP
I 10/04/22 19:00:41 00079 ports: ST1-CMDR: trunk Trk14 is now inactive
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 1/14 is Blocked by LACP
I 10/04/22 19:00:41 00435 ports: ST1-CMDR: port 2/14 is Blocked by LACP
W 10/04/22 19:00:36 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 19:00:36 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 18:58:48 00179 mgr: ST1-CMDR: SME SSH from x,.x.x.x- MANAGER Mode
I 10/04/22 18:58:45 03362 auth: ST1-CMDR: User 'xxxx' logged in from
x.x.x.xto SSH session
I 10/04/22 18:53:37 00025 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 configured on vlan 1
I 10/04/22 18:53:34 00001 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN enabled
I 10/04/22 18:53:34 00076 ports: ST1-CMDR: port 2/39 is now on-line
W 10/04/22 18:53:24 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 18:53:24 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 18:53:24 00077 ports: ST1-CMDR: port 2/39 is now off-line
I 10/04/22 18:33:37 00025 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 configured on vlan 1
I 10/04/22 18:33:34 00001 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN enabled
I 10/04/22 18:33:34 00076 ports: ST1-CMDR: port 2/39 is now on-line
W 10/04/22 18:28:54 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 18:28:53 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 18:28:53 00077 ports: ST1-CMDR: port 2/39 is now off-line
I 10/04/22 18:22:29 00025 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 configured on vlan 1
I 10/04/22 18:22:26 00001 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN enabled
I 10/04/22 18:22:26 00076 ports: ST1-CMDR: port 2/39 is now on-line
W 10/04/22 18:18:12 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 18:18:11 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 18:18:11 00077 ports: ST1-CMDR: port 2/39 is now off-line
I 10/04/22 18:06:54 00025 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 configured on vlan 1
I 10/04/22 18:06:51 00001 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN enabled
I 10/04/22 18:06:51 00076 ports: ST1-CMDR: port 2/39 is now on-line
W 10/04/22 18:02:15 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 18:02:15 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 18:02:15 00077 ports: ST1-CMDR: port 2/39 is now off-line
W 10/04/22 17:38:32 04242 auth: ST1-CMDR: User xxxx logout from X.X.X.X
due to inactivity timer timeout for SSH session
I 10/04/22 17:28:23 00179 mgr: ST1-CMDR: SME SSH from X.X.X.X - MANAGER Mode
I 10/04/22 17:28:19 03362 auth: ST1-CMDR: User 'XXXXX' logged in from
x.x.x.xto SSH session
I 10/04/22 17:17:25 00025 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 configured on vlan 1
I 10/04/22 17:17:22 00001 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN enabled
I 10/04/22 17:17:22 00076 ports: ST1-CMDR: port 2/39 is now on-line
W 10/04/22 17:12:42 00026 ip: ST1-CMDR: DEFAULT_VLAN: ip address
fe80::1a7a:3bff:xxx.xxx/64 removed from vlan 1
I 10/04/22 17:12:42 00002 vlan: ST1-CMDR: DEFAULT_VLAN virtual LAN disabled
I 10/04/22 17:12:42 00077 ports: ST1-CMDR: port 2/39 is now off-line
Original Message:
Sent: Oct 12, 2022 03:34 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Did the log on the switch have any clues?

------------------------------
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 12, 2022 03:28 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

We have already disconnected the Controller as it was causing  loop. Originally the controller was working fine before we upgraded the software version from version 6.5.X.X to version 8.X.X .Upgrading the firmware also wiped out the controller configs. So we had to build the config again on the controller,,  Initially, we had it configured as trunk ports(original configs) between core switch and controller but that caused an outage. We then configured the interfaces as access ports between core switch and controller, but that also caused an outage.
Original Message:
Sent: Oct 12, 2022 03:13 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

@cjoseph, as always, thanks for the great feedback. Just wanted to know, suppose STP is enabled on the controller why would we see LACP port blocks if a convergence happening. We dont run STP on Aruba Core Layer and rely on loop protect but we do run it on access since Access is Cisco. If a new root bridge election starts wouldnt the switches block their ports connected to the Aruba core and Aruba should just see port down alarms rather than LACP alarms.

​
Original Message:
Sent: Oct 12, 2022 03:34 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Did the log on the switch have any clues?

------------------------------
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 12, 2022 03:28 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

We have already disconnected the Controller as it was causing  loop. Originally the controller was working fine before we upgraded the software version from version 6.5.X.X to version 8.X.X .Upgrading the firmware also wiped out the controller configs. So we had to build the config again on the controller,,  Initially, we had it configured as trunk ports(original configs) between core switch and controller but that caused an outage. We then configured the interfaces as access ports between core switch and controller, but that also caused an outage.
Original Message:
Sent: Oct 12, 2022 03:13 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G

That is a very good question.  I would open a Technical Support case so that Aruba/HPE can troubleshoot this in realtime.  There are too many variables to troubleshoot it here.

------------------------------
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 20, 2022 08:45 PM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph, as always, thanks for the great feedback. Just wanted to know, suppose STP is enabled on the controller why would we see LACP port blocks if a convergence happening. We dont run STP on Aruba Core Layer and rely on loop protect but we do run it on access since Access is Cisco. If a new root bridge election starts wouldnt the switches block their ports connected to the Aruba core and Aruba should just see port down alarms rather than LACP alarms.

​
Original Message:
Sent: Oct 12, 2022 03:34 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Did the log on the switch have any clues?

------------------------------
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 12, 2022 03:28 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

We have already disconnected the Controller as it was causing  loop. Originally the controller was working fine before we upgraded the software version from version 6.5.X.X to version 8.X.X .Upgrading the firmware also wiped out the controller configs. So we had to build the config again on the controller,,  Initially, we had it configured as trunk ports(original configs) between core switch and controller but that caused an outage. We then configured the interfaces as access ports between core switch and controller, but that also caused an outage.
Original Message:
Sent: Oct 12, 2022 03:13 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

That doesn't look like controller syntax.  Is the act of connecting the controller causing a loop or it something else?

On the controller, what is the output of "show trunk"?

------------------------------
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 12, 2022 03:07 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

@cjoseph attached is the diagram together with interface configs of core switch and controller.

​
Original Message:
Sent: Oct 11, 2022 10:15 AM
From: Colin Joseph
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

A physical and/or topology diagram along with the Aruba interface configuration would be good.  Also, when it doubt, just single connect, first.


------------------------------
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 11, 2022 07:30 AM
From: Gaius Manera
Subject: We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Hi Guys,

We were only trying to connect an aruba controller to the core switch? what could have cause a loop?

Aruba Core switch is connected to a number of cisco access switches via LACP.
Aruba controller is also connected to Aruba coreswitch using a single LAN cable.
Access switch ports are both configured in interfaces of Aruba Controller and Core switch where the controller is connected.
Loop protect is enabled on switchport where the Aruba Controller is connected to the core switch.
Attach is the core switch configuration. Really appreciate if you can point out the root cause and if added switch configs are needed to prevent this issue from happening again.

Thanks,
G