- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- MSM460. Clients on different VSC can't communicate...
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
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
07-16-2013 09:42 PM
07-16-2013 09:42 PM
MSM460. Clients on different VSC can't communicate. Firmware 6.0.1.
MSM460
Firmware 6.0.1
Autonomous mode
There're two VSC. For each of them:
-- Radio 1 (5GHz)
-- Broadcast filtering - Unchecked
-- Allow traffic between - all
-- Priority mechanism - Disabled
-- Egress VLAN - default (no VLAN)
-- Wireless security filters - Unchecked
All clients on both VSC are on the same subnet (192.168.0.0/255.255.255.0).
The problem is client from one VSC can't communicate with client on another VSC (no ping, no any other protocol).
Diagnosys points:
-- Clients on the same VSC can communicate with each other without any problem. This communication obviously occures inside AP, because no any ARP packet goes outside of AP (tcpdump shows).
-- When client on VSC_1 tries to ping client on VSC_2, broadcast ARP request goes out of AP, but no answer.
-- When client on VSC_1 tries to ping client on VSC in another egress VLAN (VSC_3), ping is OK.
So, is this behavior normal or it's a bug ?
From my point of view, When client on VSC_1 tries to ping client on VSC_2, AP must manage such requests inside itself without asking LAN (Autonomous mode).