- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 4104gl routing and VLAN basics
Switches, Hubs, and Modems
1753614
Members
6039
Online
108797
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
Go to solution
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-14-2003 08:28 PM
тАО02-14-2003 08:28 PM
Hello once again.
I have a small network of 300 or so nodes. Most of which are located at branch offices. We need to segment my current branch on two subnets. I thought about using a router in between, but this would be a huge bottleneck in my opinion. I purchased a 4104gl because of the new layer3 routing ability. I need to allow all traffic from subnet_A thru to subnet_B. I tried using vlan_A and vlan_B on the same router to do this, but when I need to route the traffic from one side to the other, I can only ping one way:
vlan_A= 192.168.11.0
vlan_B= 207.30.123.0
vlan_A | vlan_B
|
untagged | auto
auto | untagged
this allows me to ping from one side to another, but no back across the same interface.
I do have 2 other 4000m's that I can setup vlans on, but I was looking for some strategic advice from the forum before doing so!
Thanks in advance
Michael
I have a small network of 300 or so nodes. Most of which are located at branch offices. We need to segment my current branch on two subnets. I thought about using a router in between, but this would be a huge bottleneck in my opinion. I purchased a 4104gl because of the new layer3 routing ability. I need to allow all traffic from subnet_A thru to subnet_B. I tried using vlan_A and vlan_B on the same router to do this, but when I need to route the traffic from one side to the other, I can only ping one way:
vlan_A= 192.168.11.0
vlan_B= 207.30.123.0
vlan_A | vlan_B
|
untagged | auto
auto | untagged
this allows me to ping from one side to another, but no back across the same interface.
I do have 2 other 4000m's that I can setup vlans on, but I was looking for some strategic advice from the forum before doing so!
Thanks in advance
Michael
speak "friend" and enter
Solved! Go to Solution.
- Tags:
- VLAN
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2003 06:50 AM
тАО02-15-2003 06:50 AM
Re: 4104gl routing and VLAN basics
Let me try to simplify...
I just want to talk across two subnets. I can split the two networks onto 2 4000m's if needed. But i need to use the 4104's ip routing ability. I will take ANY suggestions....
TIA
Michael
I just want to talk across two subnets. I can split the two networks onto 2 4000m's if needed. But i need to use the 4104's ip routing ability. I will take ANY suggestions....
TIA
Michael
speak "friend" and enter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2003 06:02 AM
тАО02-16-2003 06:02 AM
Solution
Assign an IP address to each VLAN on the 4104GL. Use the appropriate VLAN's IP address as the default gateway for the hosts on that VLAN. Make sure that IP routing is turned on on the 4104. Do not use tagging on any ports. Assign a default gateway pointing to the router or internet connection device. Make sure the router has a route pointing to the 4104 for the IP address ranges that are on the 4104. (make sure the router can ping the VLAN address for the 4104 which it should be using as a gateway for the second IP address range) That should be all that you need to do. I'm not sure how the router is involved but setting up a trunk on a router is a bit more complex and should be unnecessary if the 4104GL is doing the routing.
Ron
Ron
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