- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Traffic leaks between vlans, procurve 2626
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО05-24-2008 11:03 AM
тАО05-24-2008 11:03 AM
Vlan 2 have subnet 192.168.1.0/24, with a router at 192.168.1.1, and switch configured with ip in this subnet, so it can reach ntp servers.
I first discovered that a dhcp request in vlan 1 reached vlan 2 and got ip from a router in that net. Then I set up a computer with a 192.168.1.x address in vlan 1, and was able to ping all computers etc in vlan 2, _except_ the gateway.
Problem goes away if I unset the ip address the switch have in vlan 2, but then it won't reach the ntp servers any more.
IP routing is turned off after I noticed the problem, but didn't make any difference.
Switch is configured like this (slightly edited and stripped):
ip default-gateway 192.168.1.1
sntp server x.x.x.x
sntp server y.y.y.y
timesync sntp
sntp unicast
snmp-server community "public"
vlan 1
name "vlan1"
forbid 1-8,19-24
untagged 9-18,25-26
ip address 192.168.255.2 255.255.255.0
no untagged 1-8,19-24
exit
vlan 2
name "vlan2"
forbid 9-26
untagged 1-8
ip address 192.168.1.2 255.255.255.0
exit
vlan 3
name "vlan3"
forbid 1-18,25-26
untagged 19-24
ip address 192.168.254.2 255.255.255.0
exit
no stack
primary-vlan 2
management-vlan 2
ProCurve Switch 2626# show ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
127.0.0.0/8 reject static 0 250
127.0.0.1/32 lo0 connected 0 0
192.168.1.0/24 vlan2 2 connected 0 0
192.168.254.0/24 vlan3 3 connected 0 0
192.168.255.0/24 vlan1 1 connected 0 0
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2008 11:33 AM
тАО05-24-2008 11:33 AM
Re: Traffic leaks between vlans, procurve 2626
you can make forbid port config on vlans
why ??
forbid port for gvrp you can use gvrp
you want use gvrp(dynamic vlan)you make use vlan id aware ethernet card
you can make connect normal ethernet card to forbit port all forbit port be happen vlan 1 member.
*you want make gvrp (dynamic vlan )on your network gvrp enable on your switch and use vlan aware nic.
*you dont make use gvrp(dynamic vlan)remove all forbid port command.
cenk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2008 11:46 AM
тАО05-24-2008 11:46 AM
Re: Traffic leaks between vlans, procurve 2626
Untagged Allows VLAN connection to a device that is configured for an untagged VLAN instead of a tagged VLAN. The switch allows no more than one untagged VLAN assignment per port.
No No: Appears when the switch is not GVRP-enabled; prevents the port from - or -joining that VLAN. Auto Auto: Appears when GVRP is enabled on the switch; allows the port to dynamically join any advertised VLAN that has the same VID
Forbid Prevents the port from joining the VLAN, regardless of whether GVRP is enabled on the switch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2008 12:09 PM
тАО05-24-2008 12:09 PM
Re: Traffic leaks between vlans, procurve 2626
Can it be some arp-protect setting that is missing?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2008 05:03 PM
тАО05-24-2008 05:03 PM
SolutionTry enabling spanning-tree and see if that blocks any ports and solves the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2008 12:36 PM
тАО05-25-2008 12:36 PM
Re: Traffic leaks between vlans, procurve 2626
The STP suggestion set me in right direction, thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2008 03:17 AM
тАО05-26-2008 03:17 AM
Re: Traffic leaks between vlans, procurve 2626
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2008 03:19 AM
тАО05-26-2008 03:19 AM