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 ...
Ciscocmd is another option like RANCID which has already been mentioned;
Alternatively you could use SNMP. You can send an SNMP write to the device with the location of a config server using an TFTP URL or HTTP URL and setting the "Pull config" option via SNMP;
You have a fundamental problem with your configuration, which is that the configuration digests on core and access switches don't match.
[Core-sw]dis stp region-configuration
Format selector : 0
Region name : ***edited***
Revision level : 0
Configuration digest : 0x950fe4b63ba3d47dc4a539d00f613bb9
You can either adjust the screen length as Konstantin has suggested (screen-length disable isn't available on many switches though) or you can disable paging altogether using
Re-enable with page.
This depends entirely on the switch model.
Simple layer-2 switches, "not likely". The issue is the inability to enter an atomic set of commands. Each configuration change will be active the instant it's entered. So, when you enter primary-vlan xx, the minute you hit enter your connection will fail.
With layer-3 switches, "Yes". But it takes a careful ...
Your problem is, indeed, with routing. Things in VLAN 1 are using 5.1 as the gateway, right? 5.1 doesn't know about any other internal networks. (i.e. VLAN 10) Likewise, the hosts in VLAN 1 don't know about VLAN 10.
When clientA tries to ping serverA, the packets go to the ASA and die as it doesn't know where to send them. (it's default route would send ...
This sounds like an optical problem in the transceiver module - for whatever reason the optics are not lining up correctly when the connector is clicked into place, but are managing to focus when the connector is pushed in further.
I do kinda wonder if everything is clean - filth at a very small scale is the bane of fiber optics in general. If you can't ...
MST (IEEE 802.1s) exchanges BPDUs only on instance 0. Don't expect BPDUs on the other instances.
VLAN-to-instance mapping must be identical on all MST switches (ref: richardb's answer) for the topology to converge.
With MST (802.1s), only instance 0 is meant to exchange BPDUs. One of the best writeups about MST I could find is ...
First you define the rule, e.g. deny 192.168.1.1 DNS access anywhere, permit everything else:
ip access-list extended "rulename"
10 deny udp 192.168.1.1/32 any eq 53 log
9999 permit ip any any
Then you apply the rule to the VLAN 99:
vlan 99 ip access-group "rulename"
Edit: There's an implicit last entry deny ip any any that will drop all remaining ...
HPE switches with pre-16.x firmware require original or HP-compatible transceivers. A transceiver that's not HPE branded is not activated when inserted, as indicated by LED and in the device log. You don't necessarily need an original HPE module, there's a large "compatible" market with SFPs that electronically claim to be original.
With 16.x ...
Since i do not know what type of HP switch you have, the general command to use, as you describe is:
Switch(config)# password manager user-name admin
When pressing enter, you will be prompted to enter password:
New password: ********
Please retype new password: *******
Switch(config)# write mem
That should be it. The command might change on newer ...
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 ...
This isn't Distributed Trunking. The described topology is:
| | | |
| 8200A |--| 8200B |
| | | |
| sw e |--| sw f |
Since it's said that the 8200s are connected with "DT-LACP trunks" I assume the Inter-switch ...
Straight from Cisco’s Campus Network for High Availability Design Guide, L3 is superior because:
– Faster convergence around a link or node failure.
– Increased scalability because neighbor relationships and meshing are
– More efficient bandwidth utilization.
From Cisco: Campus Network for High Availability Design Guide - Core Layer
These are normal log messages for a port bouncing on a HP Procurve/Aruba switch. The normal sequence of events for a port (connected to a non-STP edge host as most IP phones are) coming on-line and then off-line is:
Port is Blocked by STP
Port is now on-line
Port is now off-line
The port enters STP blocked when it is first brought up. There is a 3 second ...
All ports of any VLAN-capable switchs are always in a VLAN.
Generally by default, and/or it there's no specific configuration on the port it is in VLAN 1
But you may want to further diagnose the issue. If a port is correctly configured as access for a VLAN, for the device connected on this port there's absolutely no difference with an unmanaged switch.
On the 1910, you can't simply "permit all VLAN IDs". You need to create each VLAN and assign it as tagged or untagged to the interfaces as required (creating all VLANs first and then assigning them to the ports as a second step is advisable).
For instance, if port 1 is your trunk port and 44-47 are access ports associated with VLAN 10 you would assign VLAN ...
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 ...
There are many variables to consider when configuring LAN Authentication, but here is a page from the HP manual on configuring 802.1x,
and here is one from the Freeradius Wiki.
These two links should get you started.
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 - ...
Media type is stack wire,Port hardware type is STACK_SFP_PLUS
You haven't said what's being connected to the port, or if there are any syslog errors (presumably of an "unsupported" SFP) Run "display transceiver interface" to see what it thinks about the module(s). Your output shows a direct-attach cable is plugged in.
Like Ryan said, it's a layer-2 device first. If you don't configure any layer-3 features, it won't have any. Out of the box, it has no ip interfaces (maybe a default management address, not sure with the 1910) and all ports are in the default vlan (1).
The automatic default gateway can be removed, or replaced. But it has zero effect on switching of traffic. ...
Hope I understand what you are asking here (your writing is long and my memory is short :))
The HP untagged VLAN on a tagged interface functions similarly as the native VLAN you configure on Cisco switch trunk interface (actually tag/untag makes more sense than access/trunk technically speaking), the VLAN 8 in your case.
On your router interface facing HP ...
When you are using SSH to access the switch you are using a certain username and password. The fact that you need to elevate your privilege level by using the super command means that the account you are using doesn't have the highest privilege level.
So in order to prevent elevating your privilege level via the super command you should already have a ...
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
It can be problematic to change an address remotely. The best option is to do it in person from the directly attached console. To move the switch to a different subnet, that is indeed what is required. In your case, it's still in the same subnet with the same gateway, so you can just telnet in and change it. The instant the command is entered, your telnet ...