Jump to content

Recommended Posts

Posted
I have a couple of HP 1920-24G (JG924A) switches that we previously used in a small off site complex that i want to reuse as basic dumb switches so I ran the initialize process on them to factory reset the config. This completed fine however when I connect the switch to a network port on the main network and then connect a device to the switch the device is only getting a 169.254.*.* IP address, the management IP of the switch is also showing a 169 address as well (this is set to configure by DHCP in the settings). I can access the web management of the switch from the attached device so the switch appears to be working, does anything need to be specifically configured on the switch before it will allow basic switching to work?
Posted
Do you have spanning tree enabled on your main network? If I plug a switch into a regular configured port on our main switches (one not set as a trunk) the port will instantly disable and give the same symptoms you're seeing. I have to edit the switch config, or plug the port into a trunk-configured port on the switch.
  • Thanks 1
Posted

VLANs. Assuming the switch you're connecting to has VLANs setup you'll need to set them up on this switch as well.

 

You can run a bunch of managed switches with no config changes together as they'll all be running on VLAN 1 but as soon as any other VLANs come into play they'll need setting up.

Posted
VLANs. Assuming the switch you're connecting to has VLANs setup you'll need to set them up on this switch as well.

 

You can run a bunch of managed switches with no config changes together as they'll all be running on VLAN 1 but as soon as any other VLANs come into play they'll need setting up.

 

You should be able to run a dumb switch as long as whatever VLAN on the uplink port you want the new switch to run on is set as "Untagged" or "Native" with no other Vlans Tagged.

It's when you start tagging multiple vlans onto the uplink port that dumb(er) switches get confused.

  • Thanks 1
Posted

As @3s-gtech mentions. Also some spanning tree protocols don't play nicely together.

 

I do have a few HP1920 units at home but I never encountered an issue but if you can get onto on of the ones you have reset jus disable the spanning tree see if it fixes the issue and look at the logs.

Posted
Thanks for pointing me in the right direction, it was indeed Spanning Tree causing the issue, once I disabled this setting on the 1920's they started working fine.
  • Thanks 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...