This post continues my series on the differences between these three manufacturers and how they implement L2 and L3 VLANs.
vlan 10
vlan 10
vlan database
vlan 10
interface vlan 10
ip address 192.168.1.After working with all three switch manufacturers in a short period of time, I figured I would do a quick post on how each chooses how to implement VLANs at the interface level.
interface GigabitEthernet1/1
switchport mode access
switchport access vlan 10
After working with ProCurve switches for a while, I figured I would post my general configuration for others to use as a template. This configuration will be a simple setup with two VLAN's, please replace IP addreses and VLAN ID's with what fits your environment:
hostname HP-PROCURVE-CORE
time timezone -480
time daylight-time-rule Continental-US-and-Canada
sntp server priority 1 128.138.140.Coming from a Cisco QoS background, I wanted to get a good grasp on HP QoS with the ProCurve switches, but there isn't much information out there (besides the Advanced Traffic Management Guide by HP). This post should should consolidate some of that information, and is based on the the Advanced Traffic Management Guide, various vendor HP interopability guides, and
To run OSPF on HP Procurve switches, you will most likely need the "Premium" software license. Once you have that, configuring OSPF is fairly easy, although different from the Cisco approach:
For example, I want to enable OSPF in area 0 on my HP core switch (HP 5406):
(config)#router ospf
The topic of how VLANs work and untagging/tagging ports has come up, so I am attempting to write a simplified post based off some of the questions I have received:
VLANs are typically assigned to a single subnet. This is done to limit the broadcast domain and to implement access control. For example, my network could look like this:
To create a LACP trunk on an HP 2910 switch, follow these commands:
On both switches:
trunk 25-26 trk1 lacp