- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve 2910al Routing
Switches, Hubs, and Modems
1819806
Members
2754
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2011 01:10 AM
тАО02-11-2011 01:10 AM
Procurve 2910al Routing
HI,
I am trying to configure a number of HP procurve switches on 2 sites linked via 2 asa firewalls. I am having problems getting the routing to work correctly.
Switch 1 has 2 vlans 1 & 10 both have ip address configured. I can connect a PC to vlan 10 and ping both vlan IP address on the switch.
From the switch command line I can ping out to other lans on the network. However from the PC I can't ping anyhting out side the 2 vlans on the 2910. The PC has a def-gateway configured for the vlan 10 IP address on the switch.
Why can the PC ping other networks when the switch can. On a cisco 3560 this work easily and without error. The IP routing command is this only between vlans on the switch itself? Then you apply static routes to try and across other networks.
Any help would be appreciated.
Regards,
Gary
I am trying to configure a number of HP procurve switches on 2 sites linked via 2 asa firewalls. I am having problems getting the routing to work correctly.
Switch 1 has 2 vlans 1 & 10 both have ip address configured. I can connect a PC to vlan 10 and ping both vlan IP address on the switch.
From the switch command line I can ping out to other lans on the network. However from the PC I can't ping anyhting out side the 2 vlans on the 2910. The PC has a def-gateway configured for the vlan 10 IP address on the switch.
Why can the PC ping other networks when the switch can. On a cisco 3560 this work easily and without error. The IP routing command is this only between vlans on the switch itself? Then you apply static routes to try and across other networks.
Any help would be appreciated.
Regards,
Gary
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2011 05:16 AM
тАО02-11-2011 05:16 AM
Re: Procurve 2910al Routing
Hi
can you post configurations?
Switch ping inside interface, PC no.
Regards, Jorge
can you post configurations?
Switch ping inside interface, PC no.
Regards, Jorge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2011 06:33 AM
тАО02-11-2011 06:33 AM
Re: Procurve 2910al Routing
If you configure ip-routing on Procurve Switches you must not use "ip gefault-gateway".
you have to add an ip route 0.0.0.0/0 to gateway.
i.e. ip route 0.0.0.0/0 192.168.1.1
you have to add an ip route 0.0.0.0/0 to gateway.
i.e. ip route 0.0.0.0/0 192.168.1.1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2011 11:34 PM
тАО02-13-2011 11:34 PM
Re: Procurve 2910al Routing
your desription is very brief.
there are lots of point to check.
"ip routing" is to enable the switch as a router.
you can just let the switch pass vlan's to a real router and do no routing itself
(or pass both vlan's to the ASA).
This case you configure the default gateway of the client to the dedicated router.
The procurve switch basically does not behave differently than a 3560!
so compare the configs carefully (or post them on the forum) you deffinitely have overlooked something.
By the way there is an ASA in the path, you'll have to check it's config too!
NB! two asa's => check both
Also check the router config on the remote side.
As an ASA is a real firewall you may not just replace the 3560 with a procurve without other config adjustment!
or without cache-timers to expire.
so please tell us more about the setup if you want us to help.
there are lots of point to check.
"ip routing" is to enable the switch as a router.
you can just let the switch pass vlan's to a real router and do no routing itself
(or pass both vlan's to the ASA).
This case you configure the default gateway of the client to the dedicated router.
The procurve switch basically does not behave differently than a 3560!
so compare the configs carefully (or post them on the forum) you deffinitely have overlooked something.
By the way there is an ASA in the path, you'll have to check it's config too!
NB! two asa's => check both
Also check the router config on the remote side.
As an ASA is a real firewall you may not just replace the 3560 with a procurve without other config adjustment!
or without cache-timers to expire.
so please tell us more about the setup if you want us to help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP