HP E3800 vLAN Routing Trouble
I bought a new l3 hp3800 to serve as our core switch. I am doing some preconfigurations and want to test the intervlan routing. I am able to ping both of the vlan interface ips from the individual clients but not able to ping client to client? Here is the running config. I will create an access port with a separate vlan to have our Cisco ASA (192.168.120.1) to connect for the default route to the internet, but have not configured that at this point. I just want to make sure the routing between vlans is functioning and go from there. I am more of a Dell switch so HP is a bit new to me. I have not enable RIP or done much with the static routing tables. I wasnt sure if that was necessary?
Running configuration:
; J9576A Configuration Editor; Created on release #KA.15.09.0012
; Ver #03:01.1f.ef:f2
hostname "B244_3800"
module 1 type j9576y
module 2 type j9576x
ip routing
snmp-server community "public" unrestricted
snmp-server location "B244"
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1,10
untagged 2-9,11-52
no ip address
exit
vlan 100
name "Workstations"
untagged 1
ip address 192.168.100.1 255.255.254.0
exit
vlan 106
name "Printers"
untagged 10
ip address 192.168.106.1 255.255.254.0
exit
spanning-tree
spanning-tree mode rapid-pvst
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator
B244_3800#
Running configuration:
; J9576A Configuration Editor; Created on release #KA.15.09.0012
; Ver #03:01.1f.ef:f2
hostname "B244_3800"
module 1 type j9576y
module 2 type j9576x
ip routing
snmp-server community "public" unrestricted
snmp-server location "B244"
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1,10
untagged 2-9,11-52
no ip address
exit
vlan 100
name "Workstations"
untagged 1
ip address 192.168.100.1 255.255.254.0
exit
vlan 106
name "Printers"
untagged 10
ip address 192.168.106.1 255.255.254.0
exit
spanning-tree
spanning-tree mode rapid-pvst
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator
B244_3800#
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also can you please post the routing table.
ASKER
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
192.168.100.0/23 Workstations 100 connected 1 0
192.168.106.0/23 Printers 106 connected 1 0
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
192.168.100.0/23 Workstations 100 connected 1 0
192.168.106.0/23 Printers 106 connected 1 0
ok,
Did you try setting the default gateway on the switch yet? I dont see it listed
Did you try setting the default gateway on the switch yet? I dont see it listed
ASKER
With IP Routing enabled, I wasnt able to set the default gateway on the switch unless I turn off IP routing. I'd like to keep routing on the switch and not the Cisco...
The switch is currently isolated from the network so what I did was.
I have added "ip route 0.0.0.0 0.0.0.0 192.168.120.1" to the config for the default route out.
The route shows in the running config but not the routing table. Would it be best for me to turn on RIP? Alternatively I can go ahead and add static routes if that would be another good idea. I'll still need to add my additional vlans for the wireless, etc but can work on that after these are up and running.
The switch is currently isolated from the network so what I did was.
I have added "ip route 0.0.0.0 0.0.0.0 192.168.120.1" to the config for the default route out.
The route shows in the running config but not the routing table. Would it be best for me to turn on RIP? Alternatively I can go ahead and add static routes if that would be another good idea. I'll still need to add my additional vlans for the wireless, etc but can work on that after these are up and running.
ASKER
Updated Running Config:
; J9576A Configuration Editor; Created on release #KA.15.09.0012
; Ver #03:01.1f.ef:f2
hostname "B244_3800"
module 1 type j9576y
module 2 type j9576x
ip route 0.0.0.0 0.0.0.0 192.168.120.1
ip routing
snmp-server community "public" unrestricted
snmp-server location "B244"
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1,10
untagged 2-9,11-52
no ip address
exit
vlan 2
name "Legacy"
ip address 192.168.55.253 255.255.252.0
ip helper-address 192.168.55.10
exit
vlan 100
name "Workstations"
untagged 1
tagged 52
ip address 192.168.100.1 255.255.254.0
ip helper-address 192.168.55.10
exit
vlan 106
name "Printers"
untagged 10
tagged 52
ip address 192.168.106.1 255.255.254.0
exit
spanning-tree
spanning-tree mode rapid-pvst
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator
B244_3800(config)#
; J9576A Configuration Editor; Created on release #KA.15.09.0012
; Ver #03:01.1f.ef:f2
hostname "B244_3800"
module 1 type j9576y
module 2 type j9576x
ip route 0.0.0.0 0.0.0.0 192.168.120.1
ip routing
snmp-server community "public" unrestricted
snmp-server location "B244"
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1,10
untagged 2-9,11-52
no ip address
exit
vlan 2
name "Legacy"
ip address 192.168.55.253 255.255.252.0
ip helper-address 192.168.55.10
exit
vlan 100
name "Workstations"
untagged 1
tagged 52
ip address 192.168.100.1 255.255.254.0
ip helper-address 192.168.55.10
exit
vlan 106
name "Printers"
untagged 10
tagged 52
ip address 192.168.106.1 255.255.254.0
exit
spanning-tree
spanning-tree mode rapid-pvst
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator
B244_3800(config)#
If you want to keep it completely isolated right now, I would just use static routes between vlans.
Generally speaking though, to do inter-vlan routing, you would use one switch as an access switch and configure a trunk port to a router with subinterfaces on each vlan, then use that interfaces as the gateway for each respective subnet.
Im not sure how this HP operates exactly.
Im not sure how this HP operates exactly.
ASKER
Added the routes in the static table. Wireless NIC was apparently acitve on one of the test machines performing ping which was interfering with the vlan communiction via cat6.
Thanks for your input G!
Thanks for your input G!
1. Configure default gateway to the ASA
2. Each respective VLAN should use the Switch IP for their gateway IP.
This should work.