- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
understanding inter-VLAN routing
02-01-2010 07:33 AM
The APs get IP addresses from VLAN 99. Even though my management server is placed in the same VLAN as the APs, I cannot ping them as long as inter-VLAN routing is disabled. I need to enable inter-VLAN routing for VLAN 99 to make this work.
I thought that is for routing between different VLANs. I seems, however, that this feature does also some routing between the LAN and the wireless.
Am I correct? Is there some more detailed information on inter-VLAN routing?
Regards
Dirk
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Inter-Vlan Routing
02-01-2010 07:39 AM
If a client has a default gateway that is the Aruba controller and you want the Aruba Controller to route traffic for that client, leave inter-vlan routing on (default).
If the Aruba controller simply has an IP interface on a layer2 network, but clients have a default gateway OTHER than the Aruba controller, AND you want clients to be forced to use their default gateway for that secondary device, you should DISABLE inter-vlan routing on that interface.
Does that make sense?
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: understanding inter-VLAN routing
02-01-2010 07:45 AM
However, I cannot reach my APs from the LAN sending a simple ping command. Here I need inter-VLAN routing to be turned on even though my management server is on the same VLAN.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: understanding inter-VLAN routing
02-01-2010 07:53 AM
Sorry for not being clear: This is true for remote APs but not for inhouse APs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Leave it on
02-01-2010 07:55 AM
You might not be able to ping your APs from the LAN because of how your LAN is segmented or a firewall. Only the controller really needs to reach the APs and vice-versa, anyways.
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: understanding inter-VLAN routing
02-01-2010 08:00 AM
You might want to think of a larger organization with APs all over the place. They have network management systems and monitor their equipment with software like HP OpenView or so. If an AP fails, a dot on a map turns red and a technician without any access to the Aruba system replaces the AP. So not only the controller needs to reach the APs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Network Management
02-01-2010 08:09 AM
All of the information that is needed about access points, however, like whether they are up or down, how many users are on them, etc. can be obtained via SNMP to the controller's IP address alone in a centralized deployment like Aruba. Aruba APs do not run an SNMP daemon, so they cannot be polled individually for any information.
You can manage each individual AP as a single element through ping, but it yields very little information besides if a particular IP address is answering a ping or not. If an AP reboots and gets a different IP address, the NMS will then lose it's correlation. Utilizing SNMP to the Aruba controller yields the most information without the overhead of individual element management.
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: understanding inter-VLAN routing
02-01-2010 08:13 AM
Thanks for showing me the way.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Support Site MIB Guide
02-01-2010 08:19 AM
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator
Re: understanding inter-VLAN routing
02-02-2010 02:00 PM
vieregg, if you cannot ping from your LAN, try a traceroute. Follow the path until you can see where it breaks down. It could be a routing problem at your network or a misconfiguration in the forwarding path. These are guesses since I have no idea how your network is setup. This doesn't sound like an Aruba issue (yet) but rather a networking issue.
Ryan Holland, ACDX #1 ACMX #1
The Ohio State University
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Alert a Moderator