- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- HP ProCurve 9300m Routing Switch configuration: mi...
-
- 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
04-28-2018 09:03 AM - edited 04-28-2018 09:49 AM
04-28-2018 09:03 AM - edited 04-28-2018 09:49 AM
HP ProCurve 9300m Routing Switch configuration: migration to Aruba 5400R zl2
Hello all,
I've had the opportunity to have hands on a old - still running - HP ProCurve 9308m Routing Switch which is acting as a core switch.
Plans require we transfer core features to newer Aruba 5400R zl2 so we are evaluating acutal HP ProCurve 9308m running configuration to see what we need to migrate into new ArubaOS-Switch configuration.
There isn't anything special running on HP ProCurve 9308m apart from various SVIs (IP Protocol based VLANs) and some others manually added IP Routes.
As example, with regards to defined SVI, I generally saw Virtual Interface configuration like this:
! interface ve n ip address x.x.x.x y.y.y.y !
where VLAN n has this configuration:
! vlan n name VLAN_n by port tagged ethe 4/5 ethe 5/5 untagged ethe 3/2 ethe 3/8 to 3/16 ethe 4/2 ethe 4/8 to 4/16 router-interface ve n spanning-tree !
even if, with respect to the example provided above, almost all considered VLANs haven't any ethe port defined as untagged port member (instead listed ethe ports are basically all tagged members of considered VLAN, as required).
To me the point is to understand the router-interface ve n command in relationship with the
vlan n name VLAN_n by port
definition.
Does it mean that, in ArubaOS-Switch terms, a translated configuration could be something like this?
vlan n
name "VLAN_n" untagged port(s)-list tagged port(s)-list ip address x.x.x.x y.y.y.y exit
I'm not an HPE Employee

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP