Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: HP ProCurveSR7102dl & Unable to Ping VLANS
Switches, Hubs, and Modems
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- 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
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
- Email to a Friend
- Report Inappropriate Content
10-08-2009 08:08 AM
10-08-2009 08:08 AM
Re: HP ProCurveSR7102dl & Unable to Ping VLANS
UPDATE!
I was able to try the following config last night, but I am still not able to get my phones to "jump" onto VLAN 70.
On the ZyXEL switches I configured all the ports as VLAN Trunking, & "Normal", "Untagged". The only port I tagged was port 27 on SW1 which connects to the HP "int eth 0/1".
On the HP I did the following...
int eth 0/1
description Connects to Data Network
encapsulation 802.1q
no shutdown
int eth 0/1.70
vlan-id 70
no shutdown
ip address 192.168.10.254 255.255.255.0
interface eth 0/2
description Connects to Phone Network
encapsulation 802.1q
no shutdown
interface eth 0/2.70
vlan-id 70
no shutdown
ip address 192.168.2.254 255.255.255.0
ip helper-address 192.168.10.254
What the heck am I doing wrong? Is the HP capable of tagging ports as well? I'm going to download the cli guide and double check if I can tag ports on the HP router... But the whole tagged untagged is not making sense to me.
Here is my understanding of it. When a port is tagged, it adds data to the frame when transmitting on that port that contains, vlan id, priority etc.. So any device connected to that port is able to be a "member" of that vlan.
Can someone please take a close look at the diagram I am attaching, maybe a visual aspect of my network will help find a resolution.
Thank you so much all the contributors of the site. You guys are amazing!
~TJ
I was able to try the following config last night, but I am still not able to get my phones to "jump" onto VLAN 70.
On the ZyXEL switches I configured all the ports as VLAN Trunking, & "Normal", "Untagged". The only port I tagged was port 27 on SW1 which connects to the HP "int eth 0/1".
On the HP I did the following...
int eth 0/1
description Connects to Data Network
encapsulation 802.1q
no shutdown
int eth 0/1.70
vlan-id 70
no shutdown
ip address 192.168.10.254 255.255.255.0
interface eth 0/2
description Connects to Phone Network
encapsulation 802.1q
no shutdown
interface eth 0/2.70
vlan-id 70
no shutdown
ip address 192.168.2.254 255.255.255.0
ip helper-address 192.168.10.254
What the heck am I doing wrong? Is the HP capable of tagging ports as well? I'm going to download the cli guide and double check if I can tag ports on the HP router... But the whole tagged untagged is not making sense to me.
Here is my understanding of it. When a port is tagged, it adds data to the frame when transmitting on that port that contains, vlan id, priority etc.. So any device connected to that port is able to be a "member" of that vlan.
Can someone please take a close look at the diagram I am attaching, maybe a visual aspect of my network will help find a resolution.
Thank you so much all the contributors of the site. You guys are amazing!
~TJ
- « Previous
-
- 1
- 2
- Next »
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP