I'm looking at the 2 Aruaba switches, and these are their configs (not full, only the port configs), and I don't really see anything different.
The 10.0.0.3 have port security enabled , and 10.0.0.4 doesn't (it used to, but I removed it for testing)
10.0.0.3 (Netgear switch works on this one), and port 17 was the old uplink to Netgearinterface 17
name "Switch in Ceiling"
untagged vlan 1
port-security learn-mode static address-limit 14 action send-disable
mac-address 00c04e-491738
exit
aaa port-access authenticator 2-4,7-8,11,15,19,23-24,26-27,33-38,42-43,50
aaa port-access authenticator active
10.0.0.4 (Netgear switch won't work on this one), and port 3 is the new uplink to Netgearinterface 3
name "Gerald Switch"
untagged vlan 1
exit
aaa port-access authenticator 4
aaa port-access authenticator active
Original Message:
Sent: Jul 28, 2022 08:05 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
OK, I didn't setup these switches, so I need to look into it. It make sense changes from WebUI triggers a 'write memory'
Original Message:
Sent: Jul 28, 2022 07:39 AM
From: Herman Robers
Subject: Aruba to Netgear managed switch, port down
If you made changes from the WebUI as well, those may have triggered a 'write memory'. Changes from the CLI will not be saved to the startup config, unless saved. If someone else logged in, many admins do a 'write memory' 'automatically', without actually thinking (not good, but happens).
If you make a change to the running config, and you lock youself out, you can ask someone to power-cycle the switch to return to the previously saved config.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 28, 2022 07:27 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
By coincidence, we had a power outage yesterday, and the switches all were shutdown. I did not do a write-memory when I made changes two days ago, but it kept the settings.
I guess the switches must have some kind of auto save from CLI.
Original Message:
Sent: Jul 27, 2022 03:24 PM
From: Davide Poletto
Subject: Aruba to Netgear managed switch, port down
Hi, I chime in just to say my 2 Cents:
48 port Aruba 2390F WC.16.02.0014 (BootROM WC.16.01.0003)
24 port Aruba 2390F WC.16.03.0005 (BootROM WC.16.01.0003)
are de-facto different versions (ArubaOS-Switch 16.02 versus ArubaOS-Switch 16.03...even if the two softwares share the same BootROM version), both are quite old and - considering those build levels - basically unsupported.
If I were you I would upgrade both Aruba 2930F to latest software build of WC.16.11 software branch...along with checking any relevant difference between both running configurations.
Original Message:
Sent: 7/27/2022 10:28:00 AM
From: t.antony
Subject: RE: Aruba to Netgear managed switch, port down
So it wouldn't hurt to run the write memory command
Original Message:
Sent: Jul 27, 2022 08:33 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
Ok because when I make the changes in CLI, its updating in the web gui and I'm not entering write memory. Is this normal behavior? Because according to my collegue (I'm new to this company), I don't need to do a write-memory since its updating on the web gui.
Update on my original issue,
I got the Netgear managed switch to work, but only on the Aruba 48 port switch, but not on the Aruba 24 port switch.
Both of the Aruba switches have the same firmware version, and the ports are set exactly the same (VLAN 1, Tagged, no port-security)
So may be GS108T is not compatible with the Aruba 24 port?
48 port 2390F WC.16.02.0014, ROM WC.16.01.0003
24 port 2390F WC.16.03.0005, ROM WC.16.01.0003
Original Message:
Sent: Jul 27, 2022 08:00 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
Yes, if you want it to persist through a reboot. Write memory copies the running configuration to the startup configuration which is used when rebooted.
Original Message:
Sent: Jul 27, 2022 07:49 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
Thank you, I'll do that. One more unrelated question.
When I do commands from the CLI, and if I refresh the web gui, it shows up on there.
For example, if I name interface 5 to 'test' from the cli, when I refresh the web gui of the switch, it shows interface 5 named 'test'
so do I have to do a write memory command from CLI? Because it looks like its writing to flash automatically.
Original Message:
Sent: Jul 27, 2022 03:16 AM
From: Herman Robers
Subject: Aruba to Netgear managed switch, port down
It may be best to work with your Aruba partner or Aruba support. There is not enough information on what the exact configuration, exact logging is. It's just easier to do interactive troubleshooting instead of posting fragments of information on this forum.
At least remove all complexity, like port security, and see if it works with a minimum port configuration. Then, if needed start adding additional config. Also check the logs on the Netgear switch to see if that switch isn't bringing the link down for some reason.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 26, 2022 09:46 PM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
I did add the Netgear mac as static
Original Message:
Sent: Jul 26, 2022 03:39 PM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
I put port 3 on the Aruba on Tagged VLAN 1
Then port 8 of the Netgear managed switch on Tagged VLAN
Still, when I connect them together, no link lights, and port is down.
I even tried removing the port-security from that port, so that its no continuous mode, and no violation action, but still same thing.
Original Message:
Sent: Jul 26, 2022 01:17 PM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
That is correct.
Original Message:
Sent: Jul 26, 2022 12:54 PM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
just to make sure, after I make the changes in the CLI, I need to do 'write memory' so it will save the changes right?
So if the switch restarts, it will save the config.
Original Message:
Sent: Jul 26, 2022 12:14 PM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
I don't think so. It does show that the switch considers that port to be an end device, (access mode).
I would kill the POE.
conf t
int 3
no power-over-ethernet
Original Message:
Sent: Jul 26, 2022 11:49 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
Would that be causing the issue? I don't think so.
Original Message:
Sent: Jul 26, 2022 11:45 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
Looks like it is trying to negotiating POE.
Original Message:
Sent: Jul 26, 2022 10:56 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
I haven't tried putting them on Trunk mode yet, but these are the logs from port 3
What is PD? I'm not sure if that's causing the problem.
07/25/22 12:16:19 00076 ports: port 3 is now on-line
I 07/25/22 12:14:56 00077 ports: port 3 is now off-line
I 07/25/22 12:14:51 00076 ports: port 3 is now on-line
I 07/25/22 12:11:47 00565 ports: port 3 PD Removed.
W 07/25/22 12:11:47 00563 ports: port 3 PD MPS Absent indication.
I 07/25/22 12:11:46 00561 ports: port 3 Applying Power to PD.
I 07/25/22 12:11:46 00560 ports: port 3 PD Detected.
Original Message:
Sent: Jul 26, 2022 10:22 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
Ok, I'll try putting the Netgear and Aruba ports on Trunk mode VLAN 1
But I still don't understand why it worked earlier then. Because when this same managed switch was connected to another Aruba switch, both sides were on Access mode VLAN 1. Just trying to clarify.
Original Message:
Sent: Jul 26, 2022 10:12 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
I tried to connect the Cisco switches in access mode to a 3810M, untagged and it would not connect. When I changed the Cisco configuration to trunk mode it connected. Just my experience.
Original Message:
Sent: Jul 26, 2022 10:02 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
Thank you, but may I ask why I even need to put the Aruba and Netgear on Trunk mode?
Because this same Netgear managed switch was connected to a 48 port 2390f switch two days ago, and it was working fine (both sides on untagged vlan 1). I removed the Netgear managed switch from this 48 port switch, because I needed more ports.
I'm connecting the Netgear managed switch to another 24 port 2390f switch and now its not working for some reason (both sides on untagged vlan 1)
Original Message:
Sent: Jul 26, 2022 09:52 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
Correction:
This is how I got the Cisco to work and it untagged on both ends:
interface TenGigabitEthernet1/0/2
switchport trunk native vlan 1
switchport trunk allowed vlan 1
switchport mode trunk
Original Message:
Sent: Jul 26, 2022 09:45 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
Try it in trunk mode with vlan 1 tagged at both ends.
Original Message:
Sent: Jul 26, 2022 09:32 AM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
The Netgear managed switch is on VLAN 1, on ports on access mode. Same as the Aruba uplink port.
This same managed switch was working before connected to another Aruba switch on same configuration (VLAN 1, all ports unmanaged)
Original Message:
Sent: Jul 26, 2022 09:12 AM
From: Larry Baysinger
Subject: Aruba to Netgear managed switch, port down
What is the configuration on your Netgear managed switch? I suspect you need to enable trunking mode. I have tried to connect Cisco switches in access mode to Aruba switches and had the same results. When I switched to trunk mode the connection was made.
Original Message:
Sent: Jul 25, 2022 01:37 PM
From: Tony Antony
Subject: Aruba to Netgear managed switch, port down
On port 3 of the Aruba switch, there's port-security enabled. This port had a Netgear unmanaged dummy switch connected, and everything was fine.
But, when I connected a Netgear managed switch to this port, the Netgear switch is not getting any connection from Aruba. I did add the Netgear switch's MAC address, but its still down. But, if I connect it back to the Netgear dummy switch, its fine. I even tried doing a factory reset on the Netgear managed switch, but its not working. This managed switch is acting as a dummy switch, meaning no VLANs, except the native VLAN 1.
When I do a show mac-address 3 (this is the uplink port to the Netgear switch), I get this
Ridge-Core-24# show mac-address 3
Status and Counters - Port Address Table - 3
MAC Address VLANs
------------- ------------
0000ba-20269e 1
1866da-050134 1
64006a-5f696c 1
702084-09654c 1
But when I login to the webgui, I can see 9 MAC address, because that's the limit is set to. I also have the Netgear managed switch's MAC on there.
This is show running-config interface 3
interface 3
name "Gerald Switch"
untagged vlan 1
port-security learn-mode static address-limit 9 action send-disable
mac-address 0000ba-20269e
exit
https://www.netgear.com/support/product/GS308T.aspx