VLAN - what am I missing?

nutcase · 2 Mar 2017 at 14:49

I did try double checking that earlier as I did initially set the DHCP scope to use the router but couldn't find anything. However, I *think* I've cracked it - plug a device into a VLAN20 access port, it gets an IP and can contact the internet.

I ended up using a console cable and connecting up to the switch. When I viewed the config it wasn't showing the static routes I had manually added using the GUI. Added them using the CLI (which I hate) and low and behold, we're off...

After some head scratching it dawned on me - Apply does not Equal Save. I was applying the static routes on the switch but not actually saving them...

Sorry guys and thanks for the help!

Sp00n · 2 Mar 2017 at 15:07

Glad you got it sorted

nutcase · 3 Mar 2017 at 07:46

Bit embarrassing really - I've always done it properly on our other switches but this is our first comware (?) based one. So the answer to the thread title - I was missing out saving the config. D'oh!

Caged · 3 Mar 2017 at 20:28

nutcase_1uk said:
comware

nutcase · 4 Mar 2017 at 06:59

Something tells me you're not a fan

Caged · 4 Mar 2017 at 15:00

The CLI is horrific

nutcase · 6 Mar 2017 at 08:28

I still don't use the CLI much so I hate all CLIs

Spent most of Sunday expanding the VLAN out through the other switches as required. Or tried to. The link to two buildings went straightforward enough but one is causing me trouble. The core switch (HPE 5130) is linked to a second switch (Netgear GS748Tv5) that feeds some of the less critical devices - and also uses one of the SFP ports to connect via fibre to another building. Initially the connection between the two switches was an active LACP dual link. I couldn't for the life of me get it to act as a trunk connection for both VLANs. After a lot of trial and error I ended up with one standalone link carrying the default VLAN traffic (need another quiet time to revert to a LACP link) and a second standalone link for the VoIP VLAN. Yet when I connect from the 5130 to an older FS750T2 it does so without any issue whatsoever. Very frustrating, took about 10 minutes to do two connections and about 2 hours to get what should have been the most straightforward one done - by bodging it.

Caged · 6 Mar 2017 at 22:09

Throw the Netgear in the bin and replace it with something that doesn't eat two hours of your time to make a simple config change.

Also double-check the VLAN configurations on both sides of the link - were they both just tagged or did you have an untagged and a tagged VLAN? Was the PVID set to the same value as the untagged VLAN because Netgears are horrible for doing this.

nutcase · 7 Mar 2017 at 08:17

Caged said:
Throw the Netgear in the bin and replace it with something that doesn't eat two hours of your time to make a simple config change.

Also double-check the VLAN configurations on both sides of the link - were they both just tagged or did you have an untagged and a tagged VLAN? Was the PVID set to the same value as the untagged VLAN because Netgears are horrible for doing this.

Would love to - I have a list of "projects" I want to do (ie. go to the directors Oliver Twist style) and it's number 3 to replace the netgear with another 5130. By get rid it would actually mean the netgear ends up at a satellite office as all we have there are unmanaged switches. The only reason I have the one 5130 is that the netgear WAS the core switch and it was getting overloaded.

I tried just about every combination of things - Both VLANs tagged as a trunk, one tagged, one untagged as a hybrid etc. with the PVID (agreed, what a stupid way of doing it...) and nothing worked. It was strange that a much older netgear worked straight away.