- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Who Me Too'd this topic
Switches, Hubs, and Modems
1753487
Members
4668
Online
108794
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2008 07:42 PM
07-02-2008 07:42 PM
Setting up Layer 3 VLAN routing
We have three physically separated locations. We just connected them via an AT&T CSME or Opt-E-Man. It’s fiber, but what AT&T provides is a port on an AT&T owned HP Switch in the MPOE. We then plug our switches into the AT&T switch.
We have several VLANS on each switch: Default, 100, 103, 108, 111, 120
We’ve made the connection between sites by connecting ports tagged for all VLANS on our switches to the AT&T switches. The issue is AT&T. They limit the number of MAC addresses on each of the Opt-E-Man ports.
To prevent AT&T from seeing all the MACs on each side of the Opt-E-Man we need to set the switches to route all the VLANS on layer 3. Then all AT&T sees are the MACs of the three connected switch ports.
This is new territory for us, but probably very simple to others. Can anyone provide an example of how this is set up? We have HP Procurve 2650’s at the two remote sites and an HP Procurve 5304xl at the main location. The default gateway for all the VLANS is on a SonicWall NSA E-6500 at the main site. Each VLAN has a physical port on the SonicWall. VLAN 108 is passing VOIP traffic.
It’s working, however we have too many MAC addresses for AT&T – they can solve the issue, it just cost 5 bucks a month for each additional MAC.
Thanks,
K Conde
Sutter County Schools
We have several VLANS on each switch: Default, 100, 103, 108, 111, 120
We’ve made the connection between sites by connecting ports tagged for all VLANS on our switches to the AT&T switches. The issue is AT&T. They limit the number of MAC addresses on each of the Opt-E-Man ports.
To prevent AT&T from seeing all the MACs on each side of the Opt-E-Man we need to set the switches to route all the VLANS on layer 3. Then all AT&T sees are the MACs of the three connected switch ports.
This is new territory for us, but probably very simple to others. Can anyone provide an example of how this is set up? We have HP Procurve 2650’s at the two remote sites and an HP Procurve 5304xl at the main location. The default gateway for all the VLANS is on a SonicWall NSA E-6500 at the main site. Each VLAN has a physical port on the SonicWall. VLAN 108 is passing VOIP traffic.
It’s working, however we have too many MAC addresses for AT&T – they can solve the issue, it just cost 5 bucks a month for each additional MAC.
Thanks,
K Conde
Sutter County Schools
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