HP Procurve configuration

I have a configuration that I need some assistance with for a client. At their location, they have a Cisco ASA with one port configured as the inside interface. Connected to that is an HP Procurve. The first procurve that is connected to the ASA is also connected to 3 other procurve switches. At this time, there are a total of 4 procurve switches sitting behind the firewall on one single vlan. IP addresses are assigned by a Windows box. Since all worked when they were plugged in, the client did no configuration changes to these devices. Now, for my problem.

1. I need to create a trunk between two of the switches.
2. I need to create 2 vlans on 2 of the switches.
3. I need to tag vlan traffic between these 2 switches.

The issue is that they are using a /24 for the DHCP server and have run out of addresses.
They want a new vlan created so that the wireless is no longer part of the original lan and segregated from all of the wired connections.

I have already built out a new interface on the ASA, created a new DHCP scope and tested connectivity to the internet on this new interface and all is working with no issues.

Of the 4 switches, they are broken down as 2 on each floor. We do not care about the way the second switch on each floor is connected to the other switch as they can remain on the same vlan as the original. It is just the 1 switch on floor 2 that is connected to the 1 switch on floor 3 that is my concern. I cannot get into the switch via the web interface so I am going to have to use the console on this. Anything that I need to know about?
INV_supportAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
jburgaardConnect With a Mentor Commented:
On a Procurve to Enable/disable the BPDU filter feature on the specified port(s):
syntax: [no] spanning-tree <port-list | all> bpdu-filter

For example, to configure BPDU filtering on port 8, enter:
ProCurve(config)# spanning-tree 8 bpdu-filter

Ports configured with the BPDU filter mode remain active (learning and forward frames); however, spanning-tree cannot receive or transmit BPDUs on the port. The port remains in a forwarding state, permitting all broadcast traffic. This can create a network storm if there are any loops (that is, trunks or redundant links) using these ports. If you suddenly have a high load, disconnect the link and remove ("no") the bpdu-filter.

Links HP to HP should have both vlans tagged on ports in both ends.
Easiest to do in menu , easiest to communicate in CLI-syntax
HTH
0
 
jburgaardCommented:
"Anything that I need to know about?"
If there are to be 2 links between ASA and HP you should be sure spanning tree will not block the one link.
If you need more specific help fx. on using the CLI-interface and menu-interface it would be helpful if you told more specified what you do not know, model of switch, ports involved in linking ...
0
 
INV_supportAuthor Commented:
This is a 4108gl switch. I know Cisco and nothing of HP switches. I have played with the smaller HP switches but not this size. Ultimately, I would like to create a port channel using the two links that are connected between the switches right now. That would be my preference on this. I have the configuration guide from HP but nothing too specific in there.
0
 
INV_supportAuthor Commented:
That was what I was looking for on the switches. Thank you.
0
All Courses

From novice to tech pro — start learning today.