- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: MSM765zl - Odd routing table issue (Add a VLAN...
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
Discussions
Discussions
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
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
08-04-2011 04:27 PM
08-04-2011 04:27 PM
MSM765zl - Odd routing table issue (Add a VLAN, get two routing entries instead of one)
Here's an example. The LAN port is 172.16.0.1, which is disjointed from our 10.x.x.x network.
I added VLAN 400 to the Internet port and configured as Static (10.24.8.2/24), and when I went to the IP route page, this is what I saw. Obviously this is a huge problem because it means that half the time the packets get lost (I just spent hours trying to figure out why it worked half the time).
Interface Destination Mask Gateway Metric
LAN port 172.16.0.0 255.255.255.240 * 0
Internet port 10.16.128.0 255.255.255.0 * 0
LAN port 10.16.128.0 255.255.255.0 * 0
Employee Wireless 10.24.8.0 255.255.255.0 * 0
Highlighting is for emphasis.
Is there something that I'm doing wrong?
Information for troubleshooting purposes:
MSM765zl installed in slot L in a 5412zl chassis switch.
Current firmware version: 5.5.2.1-01-10012
Internet port (L1) is untagged on VLAN 60 (Wireless infrastructure) and tagged on VLAN 400 (Employee Wireless). LAN port (L2) is untagged on VLAN 4000 (which goes nowhere).
Was trying to do a setup similar to the Education example in the deployment guide (but without using radius to hand out VLANs, we are just using unique SSIDs that go to specific VLANs).
On a possibly related issue. If I set the VSC binding egress network to VLAN 400, the traffic still comes out on VLAN 60 (the untagged port on the AP and MSM).
Any help would be most appreciated.
- Tags:
- VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2011 07:26 PM
08-07-2011 07:26 PM
Re: MSM765zl - Odd routing table issue (Add a VLAN, get two routing entries instead of one)
So far it makes sense, however to get a better idea of what's going on I need some clarification:
-Do you have IP's assigned to the specific VLAN interfaces in the controller?
-Where is the 10.16.128.0/24 network assigned in the controller network settings?
-Are any of your VSC's set to 'Authentication' and 'Access Control'?
-Where are you setting the egress VLAN binding, in the VSC or in the AP group configuration?
HP ASE (Mobility), Infrastructure Engineer