lowfell
asked on
HP5304 intervlan routing HELP 500 POINTS
I have defined 3 vlans on an HP5304 and want to route between these vlans
The three vlans are
vlan1 192.168.0.217 255.255.255.0
vlan2 160.213.X.X 255.255.255.0 and 10.41.2.253 255.255.255.0
vlan3 192.168.96.253 255.255.252.0
I have a host on vlan2 with a 160.213.X.X address plugged into a vlan2 port which for some reason is unable to contact another host in the same vlan2 on a 10.41.2.X address???
Can someone point me in the right direction as to why this doesn't work & also have I done enough to configure inter vlan routing between these VLANS ?
I have included the routing table of the switch as well as the switch config. This was configured my my predecessor so I was unfamiliar with the initial setup
Switch Config
HP ProCurve Switch 5304XL# sho ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.0.241 1 static 1 1
10.41.2.0/24 VLAN_2 2 connected 0 0
10.41.196.0/26 192.168.96.254 3 static 1 1
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
160.213.71.0/24 VLAN_2 2 connected 0 0
192.168.0.0/24 VLAN_1 1 connected 0 0
192.168.96.0/22 VLAN_3 3 connected 0 0
Startup configuration:
; J4850A Configuration Editor; Created on release #E.08.42
hostname "HP ProCurve Switch 5304XL"
snmp-server contact
module 1 type J4820A
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "VLAN_1"
untagged A1
ip address 192.168.0.217 255.255.255.0
no untagged A2-A24
exit
vlan 2
name "VLAN_2"
untagged A2-A6
ip address 160.213.X.X 255.255.255.0
ip address 10.41.2.253 255.255.255.0
exit
vlan 3
name "VLAN_3"
untagged A7-A24
ip address 192.168.96.253 255.255.252.0
exit
ip route 10.41.196.0 255.255.255.192 192.168.96.254
ip route 0.0.0.0 0.0.0.0 192.168.0.241
primary-vlan 3
spanning-tree
The three vlans are
vlan1 192.168.0.217 255.255.255.0
vlan2 160.213.X.X 255.255.255.0 and 10.41.2.253 255.255.255.0
vlan3 192.168.96.253 255.255.252.0
I have a host on vlan2 with a 160.213.X.X address plugged into a vlan2 port which for some reason is unable to contact another host in the same vlan2 on a 10.41.2.X address???
Can someone point me in the right direction as to why this doesn't work & also have I done enough to configure inter vlan routing between these VLANS ?
I have included the routing table of the switch as well as the switch config. This was configured my my predecessor so I was unfamiliar with the initial setup
Switch Config
HP ProCurve Switch 5304XL# sho ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.0.241 1 static 1 1
10.41.2.0/24 VLAN_2 2 connected 0 0
10.41.196.0/26 192.168.96.254 3 static 1 1
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
160.213.71.0/24 VLAN_2 2 connected 0 0
192.168.0.0/24 VLAN_1 1 connected 0 0
192.168.96.0/22 VLAN_3 3 connected 0 0
Startup configuration:
; J4850A Configuration Editor; Created on release #E.08.42
hostname "HP ProCurve Switch 5304XL"
snmp-server contact
module 1 type J4820A
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "VLAN_1"
untagged A1
ip address 192.168.0.217 255.255.255.0
no untagged A2-A24
exit
vlan 2
name "VLAN_2"
untagged A2-A6
ip address 160.213.X.X 255.255.255.0
ip address 10.41.2.253 255.255.255.0
exit
vlan 3
name "VLAN_3"
untagged A7-A24
ip address 192.168.96.253 255.255.252.0
exit
ip route 10.41.196.0 255.255.255.192 192.168.96.254
ip route 0.0.0.0 0.0.0.0 192.168.0.241
primary-vlan 3
spanning-tree
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you have any 160.213.w.Y-PC working like you want it to?
If so , find out how it is confgd. and change the non-working in that direction;
to see config:
1) at DOS prompt: ipconfig /all
2) at DOS prompt: PRINT ROUTE
-from IPCONFIG, how is DefaultGateWay?
-in the route table, is the network 10.41.2.0 mentioned ?
If no inspiration is to get here, I would try changing routing info on involved PC's:
on the 160.213.71.X-PC with mask 255.255.255.0 and defaultGW:160.213.71.Z [=IP-adr on sw.'vlan2]
ROUTE -P ADD 10.41.2.0 MASK 255.255.255.0 160.213.71.X [use this netcard to access 10.41.2.0-network directly]
on the 10.41.2.q-PC with mask 255.255.255.0 and defaultGW:10.41.2.253
ROUTE -P ADD 160.213.71.0 MASK 255.255.255.0 10.41.2.q [use this netcard to access 160.213.71.0-network]
hope this is to some help