- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- COMWARE Bridged VLAN vs Procurve/Aruba Bridged VLA...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
09-14-2017 07:44 AM
09-14-2017 07:44 AM
COMWARE Bridged VLAN vs Procurve/Aruba Bridged VLAN
Hi, I'm having an issue with one of our configurations since I migrated from a COMWARE to Procurve/Aruba. We're using a physical webfilter in a Virtual VMWARE environment. To get this working, we basically loop the webfilter through two VLANs. Here is the configuration that was working fine on the COMWARE:
vlan 333 name "WEBFILTER BRIDGE for IN-LINE" # vlan 666 name FW # stp bpdu-protection stp enable # interface Vlan-interface333 # interface Vlan-interface666 ip address 192.168.253.2 255.255.255.240 # interface GigabitEthernet1/0/18 port link-mode bridge description Barracuda LAN Interface port access vlan 666 bpdu-drop any # interface GigabitEthernet1/0/20 port link-mode bridge description Barracuda WAN Interface port access vlan 333 bpdu-drop any #
Here is what I configured on the Procurve/Aruba. It works for a few minutes but then suddenly stops. I'm thinking it may have something to do with the difference in spanning-tree or perhaps something with ARP.
vlan 333 name "WEBFILTER BRIDGE for IN-LINE" untagged C20 tagged Trk11-Trk12 no ip address exit vlan 666 name "FW" untagged C18 ip address 192.168.253.2 255.255.255.240 interface C18 name "Barracuda LAN" exit interface C20 name "Barracuda WAN" exit spanning-tree spanning-tree C18 bpdu-filter spanning-tree C19 bpdu-filter
The ports always stay in a FORWARDING state even when things stop working. Really not sure where the issue is.
Here are some images of what I'm trying to accomplish to give you a better idea:
What I wanted to accomplish: http://i.imgur.com/4rFQj7E.jpg
What I'm trying to do physically: https://imgur.com/ggR7EJ1
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP