- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Routing Issues with Procurve 5412
Switches, Hubs, and Modems
1754186
Members
4185
Online
108811
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
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-10-2010 10:08 AM
тАО02-10-2010 10:08 AM
Routing Issues with Procurve 5412
I am trying to get these VLANS to talk to the VLAN 101 production. The TRK1 carries the information to the router. When I get on the ports for VLAN 111, it does not speak to the 10.1.101.0 network.. I need help with this intervlan routing.
ip routing
vlan 1
name "Management"
untagged Trk1
no untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F22
no ip address
exit
vlan 101
name "Production"
untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F14,F21-F22
ip address 10.1.101.248 255.255.255.0
tagged Trk1
exit
vlan 111
name "WirelessInfrastructure"
untagged F15-F20
ip address 10.1.111.2 255.255.255.0
tagged Trk1
exit
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 10.1.101.254 101 static 1 1
10.1.101.0/24 Production 101 connected 1 0
10.1.111.0/24 WirelessInfr... 111 connected 1 0
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
ip routing
vlan 1
name "Management"
untagged Trk1
no untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F22
no ip address
exit
vlan 101
name "Production"
untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F14,F21-F22
ip address 10.1.101.248 255.255.255.0
tagged Trk1
exit
vlan 111
name "WirelessInfrastructure"
untagged F15-F20
ip address 10.1.111.2 255.255.255.0
tagged Trk1
exit
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 10.1.101.254 101 static 1 1
10.1.101.0/24 Production 101 connected 1 0
10.1.111.0/24 WirelessInfr... 111 connected 1 0
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 11:13 AM
тАО02-10-2010 11:13 AM
Re: Routing Issues with Procurve 5412
hi Jason
for routing between vlan's unneccessary another router
for example
ip routing
vlan 101
name "Production"
untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F14,F21-F22
ip address 10.1.101.248 255.255.255.0
exit
vlan 111
name "WirelessInfrastructure"
untagged F15-F20
ip address 10.1.111.2 255.255.255.0
exit
vlan 101 member pc connect vlan 101 untag port and this pc default gateway address must have vlan 101 ip address (10.1.101.248)
and connect
vlan 111 member pc connect vlan 111 untag port and this pc default gateway address must have vlan 111 ip address (10.1.111.2)
if you want use another router for this operation
in this way use tagged port
trunk port unlike cisco trunk command
trunk command on hp switch for link agregation
for routing between vlan's unneccessary another router
for example
ip routing
vlan 101
name "Production"
untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F14,F21-F22
ip address 10.1.101.248 255.255.255.0
exit
vlan 111
name "WirelessInfrastructure"
untagged F15-F20
ip address 10.1.111.2 255.255.255.0
exit
vlan 101 member pc connect vlan 101 untag port and this pc default gateway address must have vlan 101 ip address (10.1.101.248)
and connect
vlan 111 member pc connect vlan 111 untag port and this pc default gateway address must have vlan 111 ip address (10.1.111.2)
if you want use another router for this operation
in this way use tagged port
trunk port unlike cisco trunk command
trunk command on hp switch for link agregation
cenk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 11:21 AM
тАО02-10-2010 11:21 AM
Re: Routing Issues with Procurve 5412
Im sorry that is confusing.
Here is whats going on.
When I get on a PC that is on the 111 vlan, I am not able to ping 10.1.101.254 (vlan 101 gateway)
All the internet works on the 101 vlan, but I cannot access internet connectivity of the 111 Vlan.. yet I have the Trk1 port tagged..
Here is whats going on.
When I get on a PC that is on the 111 vlan, I am not able to ping 10.1.101.254 (vlan 101 gateway)
All the internet works on the 101 vlan, but I cannot access internet connectivity of the 111 Vlan.. yet I have the Trk1 port tagged..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2010 01:33 PM
тАО02-11-2010 01:33 PM
Re: Routing Issues with Procurve 5412
If you are on the same switch, Tagging should 'nt have anything to do with it as you have ip routing enabled on the switch
Can you're PC in the 111 VLAN ping itself and its gateway?
because you want to do interrvlan routing and the switch has routing enabled, keep your default route to your router and your Default gateway for you PC's etc pointing to each vlan ip you have assigned to each vlan on the switch. remove the tag to your router and make it an untagged member of the vlan you want it to be in (i'm assuming vlan 101)and make sure it has a route on it to get to vlan 111 via the switches vlan 101 address.
Trev.
Can you're PC in the 111 VLAN ping itself and its gateway?
because you want to do interrvlan routing and the switch has routing enabled, keep your default route to your router and your Default gateway for you PC's etc pointing to each vlan ip you have assigned to each vlan on the switch. remove the tag to your router and make it an untagged member of the vlan you want it to be in (i'm assuming vlan 101)and make sure it has a route on it to get to vlan 111 via the switches vlan 101 address.
Trev.
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