- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Routing Problem between Procurve 9300 and 5308 swi...
Switches, Hubs, and Modems
1753510
Members
5586
Online
108795
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
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
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-09-2008 12:53 AM
02-09-2008 12:53 AM
Routing Problem between Procurve 9300 and 5308 switches
I have this problem that I just can't seem to figure out, maybe I've been looking at it to long in a uncomfortable little server room. I thought I would ask the forum to see if anyone else had ideas.
A rundown of the setup is as follows. There is a HP Procurve 9300 switch as a core with quite a few HP Procurve 5308 switches as edge switches. Most of the configurations are identical with the exception of a few test switches.
On the 9300 we have some core devices landed on it that are Linux and windows boxes. On the edge we have 90% linux boxes and a few windows pc's. There's really nothing special going on here.
The problem is we are getting timeouts when communicating from one end to the other. Additionally if I do a traceroute from any machine to the other end on the core the hop that goes through the core switch will timeout until finally getting to the destination.
Basically in the system that is in place this is causing a ton of false alarms and failover devices to kick in when they shouldn't be.
I don't have the configurations handy on this computer but will try to attach them later. A rundown is as follows:
On the core switch there are several /24 networks with a default gateway of .254 in each of them. The network ranges are essentially all 192.168.x.0/24
Interconnecting the switches are /30 subnets in the 192.168.10.x/30 range.
OSPF is the routing protocol in use, spanning tree is enabled as well as PIM-DM.
On the edge it is all /24 subnets with the default gateway being .1 in the range they are all addressed in the 192.168.x.0/24 manner.
The trunks between the switches are just setup as trunks with no lacp and the trunk is untagged in a respective vlan on each edge switch and the core switch.
The default vlan is unaddressed and has no ports tagged or untagged.
I sort of inherited this design and it is in a mission critical application that makes changing this nearly impossible. Sorry I was not able to attach some network configurations but I gave you the majority of the information.
Thanks in advance.
A rundown of the setup is as follows. There is a HP Procurve 9300 switch as a core with quite a few HP Procurve 5308 switches as edge switches. Most of the configurations are identical with the exception of a few test switches.
On the 9300 we have some core devices landed on it that are Linux and windows boxes. On the edge we have 90% linux boxes and a few windows pc's. There's really nothing special going on here.
The problem is we are getting timeouts when communicating from one end to the other. Additionally if I do a traceroute from any machine to the other end on the core the hop that goes through the core switch will timeout until finally getting to the destination.
Basically in the system that is in place this is causing a ton of false alarms and failover devices to kick in when they shouldn't be.
I don't have the configurations handy on this computer but will try to attach them later. A rundown is as follows:
On the core switch there are several /24 networks with a default gateway of .254 in each of them. The network ranges are essentially all 192.168.x.0/24
Interconnecting the switches are /30 subnets in the 192.168.10.x/30 range.
OSPF is the routing protocol in use, spanning tree is enabled as well as PIM-DM.
On the edge it is all /24 subnets with the default gateway being .1 in the range they are all addressed in the 192.168.x.0/24 manner.
The trunks between the switches are just setup as trunks with no lacp and the trunk is untagged in a respective vlan on each edge switch and the core switch.
The default vlan is unaddressed and has no ports tagged or untagged.
I sort of inherited this design and it is in a mission critical application that makes changing this nearly impossible. Sorry I was not able to attach some network configurations but I gave you the majority of the information.
Thanks in advance.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP