I'm not HP savvy but I did some quick Googling (hp irf ring topology) and found a couple of docs that indicate it does support a ring topology.
Quote from page 5:
Create an IRF virtual device in daisy chain topology,
or more reliably, ring topology, as shown in Figure 2. In ring chain
topology, the failure of one ...
I opened a case with HP concerning this issue. After escalating past the useless Level 1 tech, the Level 2 tech very alertly spotted something that I had not.
The SRX is sending its DHCPDISCOVER packet with a TTL of 1. The Procurve's apparently will decrement the TTL and use the resulting TTL in the relay'ed packet to the DHCP server. In this case, the ...
This took less than 2 seconds on Google:
HP networking portal
HP ProCurve 5400zl Switch Series - High CPU Utilization (99-100%) after Startup
Right after the switch is started, high (99-100%) CPU utilization is
When the switch boots, one of the initialization tasks is creation of
encryption keys. Having the keys ...
I attempted to stack the switches referencing the guides provided, but the commands were invalid, seemingly not applying to this device. I upgraded to the latest firmware to be sure it wasn't from having an old version. No luck.
I contacted HP support which told me this:
The stacking on this switch is different than the other procurve switches. There ...
According to the Access Security Guide for your device, the first address and mask of an ACE is source and the second address and mask is the destination. (Just in case, an ACE is an Access Control Entry; that is any line an access-list is made of)
ACE 20 of your ACL states source 192.168.50.0/24 and destination 192.168.101.0/24, then you apply the ACL at ...
If my memory serves, the older Procurve switches used to accept and forward any CoS/DSCP markings they received. You couldn't modify them unless you were on a 5400xl or better switch.
It looks like the 2520 and the 3800 allow you to modify whether or not you're using CoS or DiffServ TOS for classification. The top level command you want is qos type-of-...
Cisco PVST uses a non-standard destination MAC for BPDUs on all VLANs, so HP will not understand it. To the Cisco switch, it is the only switch on VLANs 2-14, which is why it thinks it is the root.
Cisco sends BPDUs with the standard MAC (01:80:C2:00:00:00) untagged on VLAN 1, even if VLAN 1 is not allowed on the trunk.
So HP will only see BPDUs for VLAN ...
This isn't necessarily a misconfiguration, but likely is.
LLDP carries primary vlan id in one of its attributes to help switches identify mismatches like this.
We have a number of cases were VLAN ids are only locally significant in our equipment and on completely untagged ports, with lldp enabled, the procurves will log these messages periodically because ...
The HP ProCurve switches can have 802.1p CoS Priorities or DSCP Policies set, honored, changed or honored with new priority.
By default, Quality of Service is ENABLED and operates based on
802.1p settings in the packet.
Classification is configured primarily on a global basis; but can be configured by VLAN and port.
Marking is configured primarily on a ...
I'd use a patch panel protector if port security was a real issue.
Of course, this depends on the access needed, frequency of physical port changes, and the composition of the rest of the rack/enclosure.
The switches in a MSTP domain do agree which VLANs are mapped to which instances. Altering the mapping will change the configuration digest. The result of that will be two separate, degenerate MSTP domains. Any configuration applied to the internal spanning tree will become moot.
They way you are supposed to do it is to create a 'pending' configuration on ...
2 of those 3 ports are ports that connect to another switch. If you don't know which ones, I don't know HP command syntax but there is probably a command like show mac port xx, if that show multiple mac addresses then it is (most likely) an inter-switch link; if it has only one then it is your PC.
There can be variations e.g. if your pc connects to a phone ...
The 2910al supports 802.1X port security as authenticator, using RADIUS over EAP or PEAP. Depending on your exact goals, an additional router is not required but you do need a RADIUS server. Check the 2910's "Access and Security Guide" chapter 13. If you've got nothing local to use as a RADIUS server you'll need a router to connect elsewhere - however, you ...
P1.17 is ancient (March 2010). Our 1810Gs - v1 and v2 - show MAC addresses as 48 bit. I'd update the firmware; P2.23 is latest for v1.
If you do need an answer to what the two additional octets represent we'd need to know what they look like - as probably no one's running P1.17 any more. If guessing wasn't off-topic here my bet would be on the VLAN ID (with ...
I tried to upload a visio picture that shows what I think you are trying to accomplish, but I guess I need more reputation! You basically need to enable IP routing on the HP switch that will be the gateway, and add a default route. I definitely recommend using separate VLANs for your different networks. You will also need to make sure that your ISP router ...
You also need to consider console port security - ie making sure AAA is enabled on the console. If the ProCurve doesn't support AAA on the console port, then make sure the login password for the console line is strong (and maybe rotated every 90 days or so).
When you say "unmanaged," I think you mean "default configuration." Yes, it works, but almost certainly not the way you would like it to. By default, all the ports are up and in a single VLAN (vlan 1). There is no routing enabled. You can type "show interfaces brief" to see the status of all the ports.
You obviously have something more complex on your ...
I was able to get it working with this command
sudo screen /dev/ttyS0 38400,cs8,-ixon,ixoff
Before running the command, I had to use dmesg to find which of the ttyS or ttyU devices was to be used.
Also the parameters after the ttyS device are the exact ones specified in the the HP 1910 manuals.
There are other programs such as cu and minicom. I chose GNU ...
The only standards compliant STP method common to all switches is MST. You don't have to go nuts with it, 'tho -- running everything from the CIST is fine. (I do just that between half a dozen vendors.)
End your headache and switch them all to MST. Yes, there will be a small disruption while things are in transition, but It Has To Be Done.
LACP is a protocol where both side negotiate the trunk - if either side doesn't use LACP both (all) links will stay separate. STP may step in and prevent a bridge loop.
A static trunk uses no protocol. Once the links are up they are regarded as being trunked, whether or not the other side is set up in the same way.
It's a good idea to use LACP whenever ...
The 468508-002 is a short-wave (850 nm) 8Gb SFP+ transceiver for Fibre Channel. It is not compatible with Ethernet switches and won't ever work in a 2520.
Provision switches like the 2520 series accept their own family of transceivers, e.g. J4858C (1000BASE-SX), J4859C (1000BASE-LX), J8177C (1000BASE-T). Check the transceiver compatibility guide and the ...
The 5400 series supports DHCP snooping with ARP protection which is your best option. Those force a client to use the IP address it is assigned by the authorized DHCP server(s). Any other traffic is dropped (with an optional SNMP trap).
Using reservations on your DHCP server allows you to assign and centrally manage specific IP addresses for each client - ...
You need to upgrade to the K.15 series. I also have a 3500yl-48G, and prior to K.15 I definitely saw bugs.
sh mac-a never worked properly for me in K.14, but does in K.15.
HP-3500yl-48G# sh mac-address 46
Status and Counters - Port Address Table - 46
MAC Address VLANs
Then I was going to enable IP routing on the HP switch and assign our
current IP subnet as well as new subnets to the current vlan
Despite this is possible, I would recommend you to use a different VLAN for each subnet. This is considered a best practice as it provides several advantages. For instance: it reduces the amount of broadcast traffic that ...
You can do virtually anything Cisco does on ProCurves. It's just a tiny little bit of a different logic when implementing the configuration. You can setup VRRP (and of course different STP root bridges) on distribution layer switches, which will perform inter-vlan routing, to load balance the traffic from different VLANs between the switches.
For example, ...