New to VLANS & DHCP

[Wolverine1994]

Thanks for the reply, I have removed the IP addresses from the other switches 192.168.1.5

I did not think a trunk was necessary (if Iam understanding it).

I have port 24 tagged on the 2910 and tagged port 47 on 2530 for VLan 100 & untagged vlan 1

When I had the static ip on the laptop, I could ping either switch (why I thought I needed the addresses).

On the Native vlan 1 10.25.0.0 /16 gw is 10.25.0.10 sonicwall   dhcp 10.25.0.2 all works, always has.

On Vlan 100 dhcp (new scope on 10.25.0.2)  192.168.1.0/24 I i have the GW set as the switch 192.168.1.1

trying to ping from the 2910 using source 100 I cannot ping the dhcp 10.25.0.2 or the gateway 10.25.0.10

but as a test  I was more worried about getting the dhcp address than internet at this time.

And at this point I can just start over, I left the default vlan in place so everthing else can work.

[Vince-Whirlwind]

So your connectivity issues were caused by,

 - the hosts on your VLAN1 subnet were not using the layer-3 switch as a default gateway, but were using the Sonicwall on 10.25.0.10

 - the Sonicwall on 10.25.0.10 does not have a route for 192.168.1.0/24, so pings to it from VLAN100 can't be replied to

[Wolverine1994]

This makes no sense to me.  The original network was just one vlan.

We have 2 new switches now the 2910 & a 2530, plugged them in all works. (vlan 1)

I can unplug the connection to my GW and I can ping my DC and everything else

I just wanted to try adding another vlan, vlan 100 and see if I could get DHCP address

from the new scope.   I am not seeing this....

[Michael Patmon · Accepted solution]

Ok, so your server thinks 192.168.1.0/24 is directly reachable (on-link):

192.168.1.0 255.255.255.0 On-link 10.25.0.2 6
192.168.1.0 255.255.255.255 On-link 10.25.0.2 6
192.168.1.1 255.255.255.255 On-link 10.25.0.2 6
192.168.1.255 255.255.255.255 On-link 10.25.0.2 261

Not sure what installed those routes but it thinks that network is local.  Install a route on the server (route add 192.168.1.0 mask 255.255.255.0 10.25.6.1) and see if you can ping 192.168.1.1.  You may need to delete the currently installed routes (route delete 192.168.1.0) to get that installed as the preferred route. 

If you want other hosts who are also using 10.25.0.10 as a gateway to reach 192.168.1.0/24 you will need to install a route on 10.25.0.10 as well.  Hosts on 10.25.0.0/16 using that gateway will get ICMP redirected to 10.25.6.1 but you won't have to install a bunch of routes manually.

[Wolverine1994]

It Worked!!! Thank You!   (And everyone who answered!)

It helps to have a working example.....

so now I can play with the new scope for testing...

So eventually if I want to have the new scope access the internet,

do I add the route you suggested at the Gateway?

I will have to sit down with your example to fully understand, but I see a little 

light at the end of the tunnel, Thank You

[hp2920]

Hi all

I have problem with routing between VLAN`s

Can anybody help me with advice how to make connectivity between VLANs

hostname "HP-2920-24G"
module 1 type j9726a
ip route 0.0.0.0 0.0.0.0 10.22.1.1
snmp-server community "public" unrestricted
openflow
controller-id 1 ip 10.22.1.26 port 6653 controller-interface vlan 3
instance "test"
listen-port 6653
member vlan 2
controller-id 1
version 1.3
enable
exit
enable
exit
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 17-24
untagged 1-16,A1-A2,B1-B2
ip address 10.22.1.28 255.255.255.0
exit
vlan 2
name "hosts"
untagged 17-22
ip address 10.23.1.1 255.255.255.0
ip helper-address 10.22.1.1
voice
exit
vlan 3
name "controller"
untagged 23-24
ip address 10.24.1.1 255.255.255.0
ip helper-address 10.22.1.1
exit
password manager

[EricAtHP]

you need the "ip routing" command at the global config context to enable routing.