VLAN - what am I missing?

nutcase

nutcase

nutcase

Soldato
Joined
18 Oct 2002
Posts
7,626
Location
SX, unfortunately
Having a bit of a brain fart here. Flat network, trying to add a VLAN. Created on switch, created an interface for it (VLAN 1 interface is 10.0.11.251 and VLAN 20 interface is 10.0.12.251). Switched on DHCP helper to point to the DHPC server (10.0.11.13) and have added a 10.0.12.x scope to the DHCP server.

Two ports on switch set to be access for VLAN 20. If I connect a device, it does not pick up an IP. If I give it a static, I can ping both 10.0.12.251 and 10.0.11.251 but nothing else on the 10.0.11.0 network.

I've obviously missed something but what? :(
 
Yes that's a grab from the switch GUI.

he DHCP is on 10.0.11.x and the vlan interface is indeed 10.0.11.251 (both vlan interfaces are on the same switch).
 
I don't think I can do the "or" - router not in our control.

I've added the static route in my above picture, set a device on VLAN 1 to use 10.0.11.251 as it's default gateway and no internet :( If I set the DG to 10.0.11.10 it has internet access. So the static route is not working?
 
I can now ping inter-vlan yes. When I say I can't access the ISP router at present I can - it's a temporary draytek thing - the real one is being switched over to on Tuesday. I've added a static route on the router:

Destination IP Address 10.0.12.0
Subnet Mask 255.255.255.0
Gateway IP Address 10.0.11.251

From Tuesday I won't have access though (guess I could request it if it does turn out to be required)

But no difference at present :(
 
Hmm, it's that entry on the Draytek that is allowing the inter-vlan communication. If I disable it, I can no longer ping from VLAN 20 to VLAN 1 nor communicate with the DHCP server. So I need that route on the Switch somehow?
 
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!
 
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!
 
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 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.
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top Bottom