[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 698
  • Last Modified:

Simple Routing on 2910AL Procurve

I am setting up 2 Procurve Switches for an iScsi network but want any devices I attach to these switches to be able to access other networks as well.   I thought this would be simple but I am missing something if anyone has any ideas.  Berlow is my running config.  From my understanding, having the IP Default-Gateway does not affect the situation since I have routing turned on.  I can ping 192.168.1.1 from the switch itself but cannot from any clients attached to that default VLAN so it is routing between VLANS but no further except from the switch.

hostname "Procurve 1"
time timezone -5
module 1 type J9145A
ip default-gateway 192.168.1.19
ip routing
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-22,24
   ip address 192.168.3.5 255.255.255.0
   no untagged 23
   exit
vlan 30
   name "Vlan30"
   untagged 23
   ip address 192.168.1.19 255.255.255.0
   exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
router rip


0
bubbler86
Asked:
bubbler86
  • 2
  • 2
1 Solution
 
jburgaardCommented:
Default gateway of clients should point to IP of their vlan (192.168.3.5 or 192.168.1.19 )
on the 192.168.1.1-router there shoud be routes back
like 192.168.3.0 mask 255.255.255.0  via 192.168.1.19

I think I woud try changing 'ip default-gateway 192.168.1.19' to
ip default-gateway 192.168.1.1

HTH
0
 
bubbler86Author Commented:
I do have that route added on 192.168.1.1 (route back).

It was my understanding that the switch does not use that default gateway command anyway once routing is turned on but I started the config over and did not put a default gateway in and have same result.  From the Procurve itself I can ping any client in the 192.168.3.x or 192.168.1.x subnets but clients in eithger subnet cannot ping each other or access each...basically the switch is routing its own traffic but not the clients.  I do have the default gateway set on the IP of the VLAN.  
0
 
jburgaardCommented:
So clients do respond to ping.
No firewall-rules?
From your config I see no sign of management vlan config .
I see no ACL's
so everything seems fine
are netmasks 255.255.255.0 all over?
0
 
bubbler86Author Commented:
Ok, I had a typo on the firewall route.  I can now ping from a client in the 192.168.3.x subnet back to 192.168.1.1.  Can't go any further to any other 192.168.1.x clients nor the internet but I suspect that is a rule on the firewall blocking that.  Thanks for your guidance.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now