- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Routing issue within stack
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
09-16-2015 05:13 PM - edited 09-17-2015 06:14 AM
09-16-2015 05:13 PM - edited 09-17-2015 06:14 AM
Routing issue within stack
I have two HP E3800's in a stack (Ring).
I am setting these up brand new as our new core switch. The config of the new core is modelled after our old core.
I have programmed the stack, and setup 6 workstations to test vlan communication in the stack.
plugged
PC# vlan into IP address Subnet Mask Gateway 1 3 2/2 172.18.3.10 255.255.255.240 172.18.3.2 2 4 1/45 172.18.4.10 255.255.255.0 172.18.4.1 3 5 1/48 172.18.5.12 255.255.255.0 172.18.5.1 4 8 1/2 172.20.4.11 255.255.0.0 172.20.4.254 5 15 2/40 172.18.15.10 255.255.255.128 172.18.15.1 6 801 2/44 192.168.2.10 255.255.255.0 192.168.2.1
each test PC is able to ping all of the gateways, but none of the PCs on other vlans. as a test I moved PC3 from vlan 5 to vlan 4, plugged it into a vlan4 port, gave it a vlan 4 IP address subnet mask and gateway, and it was able to talk to PC2 (the other vlan 4 PC). I assumed that because the vlans have been given IP addresses they are routable, and therefore each vlan should be able to talk to the others (please correct me if I am mistaken, I'm not exactly an HP networking guru :))
I have attached the switch config, Any help would be greatly appreciated.
Thanks much,
RW-Network
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-17-2015 05:02 AM
09-17-2015 05:02 AM
Re: Routing issue within stack
You're right. Routing between VLAN interfaces occurs automatically.
ATP FLEXNETWORK V3 | ACSA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-17-2015 08:42 AM
09-17-2015 08:42 AM
Re: Routing issue within stack
I think all you are missing is the global command "ip routing".
If that doesn't do it, next make sure that all of your clients point to this switch as their default gateway and you may have to turn off any firewalls. Windows firewall can block pings from off subnet while allowing local pings, for example.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP