- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: 5406zl+MSM765+MSM422
M and MSM Series
1753971
Members
7714
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
тАО03-03-2010 11:54 AM
тАО03-03-2010 11:54 AM
5406zl+MSM765+MSM422
Hi all! Im starting with WIFI implementation in our HQ office. I have got 5406 switch with 765 controller and around 10 422 ap's.
Generally its all clear for me how ot works, but what mades me mad is the VLAN explaination in the manuals. And im facing with this problems.
765 LAN port i made an untagged member for VLAN "A" and tagged member of VLAN "B"
All vlans are routable and exist in working environment. Then i configured a VSC for internal employees with LOCAL / AD AUTH and WPA.
The first 422 i attached to port that is a untagged member of vlan "A" and tagged member of vlan "B". In both vlans exist its own DHCP server serving subnets in these vlans. 765 discovered the first AP without problem and assigned an ip from lan "A" (I suppose because of untagged membership)
Then i "binded vsc" this 422 to a "Controlled AP" group (not default)... and after that, happens things i cannot understand:
If i use "Use egress VLAN" with UNTAGGED VLAN "A" configured traffic normally flows and NOTEBOOK assigns appropriate IP ADDRESS from DHCP server located in VLAN "A".
BUT if i use egress VLAN with tagged VLAN "B", client still receives a valid IP ADDRESS from DHCP server located in VLAN "B" but traffic doesn't flow. I see valid ARP's in ARP table of default gateway and other stations located in vlan "B" but it is all. No traffic flows.
This shit :) happens when i confugure a dynamic vlan assignment for the user too..
Your advices?
Generally its all clear for me how ot works, but what mades me mad is the VLAN explaination in the manuals. And im facing with this problems.
765 LAN port i made an untagged member for VLAN "A" and tagged member of VLAN "B"
All vlans are routable and exist in working environment. Then i configured a VSC for internal employees with LOCAL / AD AUTH and WPA.
The first 422 i attached to port that is a untagged member of vlan "A" and tagged member of vlan "B". In both vlans exist its own DHCP server serving subnets in these vlans. 765 discovered the first AP without problem and assigned an ip from lan "A" (I suppose because of untagged membership)
Then i "binded vsc" this 422 to a "Controlled AP" group (not default)... and after that, happens things i cannot understand:
If i use "Use egress VLAN" with UNTAGGED VLAN "A" configured traffic normally flows and NOTEBOOK assigns appropriate IP ADDRESS from DHCP server located in VLAN "A".
BUT if i use egress VLAN with tagged VLAN "B", client still receives a valid IP ADDRESS from DHCP server located in VLAN "B" but traffic doesn't flow. I see valid ARP's in ARP table of default gateway and other stations located in vlan "B" but it is all. No traffic flows.
This shit :) happens when i confugure a dynamic vlan assignment for the user too..
Your advices?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2010 11:57 AM
тАО03-03-2010 11:57 AM
Re: 5406zl+MSM765+MSM422
Just forgot: in this VSC i dont use ACCESS control
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2010 12:31 PM
тАО03-03-2010 12:31 PM
Re: 5406zl+MSM765+MSM422
also Wireless Security is disabled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2010 11:13 PM
тАО03-05-2010 11:13 PM
Re: 5406zl+MSM765+MSM422
for vlan B remove the tagging from the LAN port of the controller plz.
only tag the AP port on that vlan.
Also when binfing the VSC that uses VLAN B with the AP, check "use egress vlan" and put the VLAN B number hen save & sync (just to make sure :)
And for confirmation when you mentioned "wireless security" you were talking about "Wireless security filters." on the VSC right ? then this should be unchecked for sure :)
only tag the AP port on that vlan.
Also when binfing the VSC that uses VLAN B with the AP, check "use egress vlan" and put the VLAN B number hen save & sync (just to make sure :)
And for confirmation when you mentioned "wireless security" you were talking about "Wireless security filters." on the VSC right ? then this should be unchecked for sure :)
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