Aruba 2540 Unable to get Internet on the VLANs

[ricardoalcg]

Hi. I have a network where the Modem/Router is on the IP 192.168.20.9 with 255.255.0.0 mask. The DHCP Server of this subnet is a Windows Server in the IP 192.168.20.1.

My switchs is Arubas 2540. The "management" IP of the Aruba is 192.168.0.20 mask 255.255.0.0.

I've created the VLAN 100 on the switch with DHCP to separate devices on the network.

I've tested and devices on VLAN 100 can ping devices on VLAN1 independent of it is on 192.168.0x or 192.168.20.x and vice versa but I get no Internet on VLAN 100.

After this I've tested by telnet on the switch and from the 192.168.0.20 when I ping google.pt it gives "Request time out"

If I do a traceroute to google.pt it gives: 

Aruba-2540-24G-4SFPP(vlan-1)# traceroute google.pt
traceroute to 172.217.16.227 ,
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 192.168.20.9 11 ms 1 ms 1 ms
2 * * *
3 * * *

This is the configs of the switch:

"hostname "Aruba-2540-24G-4SFPP"
module 1 type jl354a
trunk 28 trk3 trunk
trunk 7-10 trk20 lacp
timesync ntp
no sntp
ntp unicast
ntp server 192.168.20.1 iburst
ntp enable
ip default-gateway 192.168.20.9
ip dns server-address priority 1 192.168.20.1
ip route 0.0.0.0 0.0.0.0 192.168.20.9
ip routing
interface 28
name "uplink rackswitch1"
exit
snmp-server community "public" unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 1-6,11-27,Trk3,Trk20
ip address 192.168.0.20 255.255.0.0
ipv6 enable
ipv6 address dhcp full
exit

vlan 100
name "VLAN100"
tagged 25-26
ip address 172.16.100.1 255.255.255.0
dhcp-server
exit
spanning-tree
spanning-tree Trk3 priority 4
spanning-tree Trk20 priority 4
allow-unsupported-transceiver
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
dhcp-server pool "POOLVLAN100"
default-router "172.16.100.1"
dns-server "192.168.20.9"
network 172.16.100.0 255.255.255.0
range 172.16.100.20 172.16.100.254

exit
dhcp-server enable
password manager"

Can anyone help me with this issue.

Thank you 

[parnassus]

I don't see the DHCP IP Helper Address defined on VLAN 100. Your DHCP Server belongs to VLAN 1 (192.168.0.0/16)...so, in very basic terms, you have to instruct (via the DHCP IP Helper Address) clients on VLAN 100 how to reach it on VLAN 1.

Into VLAN 100 context, try:

ip helper-address 192.168.20.1

[ricardoalcg]

Hi. I've added the ip helper-address as you said and when I try to do traceroute to google.com into VLAN 100 context it gives me the same same result as showed below.

I've also tried the traceroute from vlan 1 and the result is the same:

Aruba-2540-24G-4SFPP(vlan-100)# traceroute google.com
traceroute to 216.58.211.238 ,
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 192.168.20.9 2 ms 1 ms 4 ms
2 * * *
3 Operation aborted.
Aruba-2540-24G-4SFPP(vlan-100)# quit
Aruba-2540-24G-4SFPP(config)# vlan 1
Aruba-2540-24G-4SFPP(vlan-1)# traceroute google.com
traceroute to 216.58.211.238 ,
1 hop min, 30 hops max, 5 sec. timeout, 3 probes
1 192.168.20.9 1 ms 1 ms 1 ms
2 * * *

[parnassus]

Hi, I don't understand what you're testing, why you're testing and how you're testing it.

Positioning on a VLAN context (being it vlan id 1 or 100 really doesn't matter) doesn't mean the ping/traceroute command is sourced by that particular VLAN id...at least from my (limited) knowledge...if you're testing traceroute and you want use a particular source IP Address (of the routing switch) or a particular VLAN id...then there is the source option on that command.

So you're obtaining the same results because you're just executing one command two times.

Was the DHCP Server reachability issue resolved or not?

Did your gateway 192.168.20.9 know how to reach back your VLAN id 100's subnet? ...you need to define a static route on it to instruct the gateway how to reach VLAN 100! ...something like: destination 172.16.100.0 mask 255.255.255.0 via 192.168.0.20.