- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve 4108gl multiple vlans.
Switches, Hubs, and Modems
1752538
Members
4745
Online
108788
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
12-07-2002 11:04 AM
12-07-2002 11:04 AM
ProCurve 4108gl multiple vlans.
The divices are not working in multiple vlans.
I have the following config:
HP Crocurve 4108gl
HP NetServer lp1000r ??? 2 x NetServer 10/100TX PCI Lan adapters (82559 ??? 802.1q compatible as stated in the manual), Operating system ??? Windows 2000.
Cisco 1760
I have created the following config for the switch:
Port 1 ??? lp1000r Lan1 (10.0.0.1)
Port 2 ??? lp1000r Lan2 (192.168.0.1)
Port 3 ??? Cisco 1760 Lan 0/1 (192.168.0.2)
Vlan 1 ??? port 1 ??? untagged
Vlan 2 ??? port 2 ??? untagged
Vlan 3 ??? port 3 ??? untagged
Vlan 3 ??? port 2 ??? tagged
Also there is ProSet II installed on the Win2K server and the 802.1q support turned on for LAN adapeters
when i try to ping 192.168.0.2 from the server - there is no reply. The same thing with Cisco - ping 192.168.0.1
Should there be a setting in the Win2K that indicates the Van ID to the interface?
Please, help me!
I have the following config:
HP Crocurve 4108gl
HP NetServer lp1000r ??? 2 x NetServer 10/100TX PCI Lan adapters (82559 ??? 802.1q compatible as stated in the manual), Operating system ??? Windows 2000.
Cisco 1760
I have created the following config for the switch:
Port 1 ??? lp1000r Lan1 (10.0.0.1)
Port 2 ??? lp1000r Lan2 (192.168.0.1)
Port 3 ??? Cisco 1760 Lan 0/1 (192.168.0.2)
Vlan 1 ??? port 1 ??? untagged
Vlan 2 ??? port 2 ??? untagged
Vlan 3 ??? port 3 ??? untagged
Vlan 3 ??? port 2 ??? tagged
Also there is ProSet II installed on the Win2K server and the 802.1q support turned on for LAN adapeters
when i try to ping 192.168.0.2 from the server - there is no reply. The same thing with Cisco - ping 192.168.0.1
Should there be a setting in the Win2K that indicates the Van ID to the interface?
Please, help me!
- Tags:
- VLAN
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2002 03:22 PM
12-09-2002 03:22 PM
Re: ProCurve 4108gl multiple vlans.
I think you have to install the official HP drivers for the LAN adapters in order to get the vlan choices.
See Page 13:
http://h200002.www2.hp.com/bc/docs/support/SupportManual/lpn10823/lpn10823.pdf
Then you can use HPSET to configure the VLAN assignments as per Page 35 in the above.
Can't say I've ever done this on a PC. Much easier to do on the router. If you can't get it to work then get back to me and I will tell you how to configure your router to switch between the VLANs. I will need to know the IOS version you are running.
One note: when you have multiple VLANs on a port that is considered a trunk and normally on a trunk only VLAN 1 is untagged. That's the way it works in Cisco stuff anyway. If you try trunking to the Cisco you will need to make sure it is set to use 802.1q since a Cisco by default prefers to use ISL.
Another thing: The server on port 1 has no one to talk to. There is no other device in the same subnet and no other device in the same VLAN anyway so it's not clear how that is supposed to work. Either the router or possibly the other netserver could be given a secondary address in the same subnet but you would still have to tell the switch to let them talk.
Ron
See Page 13:
http://h200002.www2.hp.com/bc/docs/support/SupportManual/lpn10823/lpn10823.pdf
Then you can use HPSET to configure the VLAN assignments as per Page 35 in the above.
Can't say I've ever done this on a PC. Much easier to do on the router. If you can't get it to work then get back to me and I will tell you how to configure your router to switch between the VLANs. I will need to know the IOS version you are running.
One note: when you have multiple VLANs on a port that is considered a trunk and normally on a trunk only VLAN 1 is untagged. That's the way it works in Cisco stuff anyway. If you try trunking to the Cisco you will need to make sure it is set to use 802.1q since a Cisco by default prefers to use ISL.
Another thing: The server on port 1 has no one to talk to. There is no other device in the same subnet and no other device in the same VLAN anyway so it's not clear how that is supposed to work. Either the router or possibly the other netserver could be given a secondary address in the same subnet but you would still have to tell the switch to let them talk.
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