Good morning, I have several 1910 24P JE008A switches, I am trying to update them to software version 5.20 release 1519P06 from version 5.20 release 1513P07, so far I have tried 5 of them, 3 successfully but lost 2 of them, someone knows What could be happening? How could I recover those that do not respond? There is no activity on any ethernet port and the console port is not responding.
Thank you in advance.
Hi
If the console port does not respond, I am afraid there is no much you can do in this case. First we need to fix this issue. Please, check the console connection - use the same PC, same terminal client software, same cable (and the same USB-to-Serial adapter if applicable) to connect to working switches just to confirm the issue is not outside failed switches.
The following are the required terminal settings:
•Bits per second—9,600
•Data bits—8
•Parity—None
•Stop bits—1
•Flow control—None
•Emulation—VT100
If you see garbled output, try to change the speed of the port, try 38,400, 115,200 and other values.
If there still will be no output, I am afraid there is no recovery possible and switches can be considered dead.
Hello Ivan B, and thanks for your quick response,
The connection by console is the same for all cases, the thing is that I have more than 100 switches to update to be able to activate Radius and SSH (with the current version it does not allow me), there is a stable version compatible with the current one that allows me do this?
Thank you very much
1519P06 is the latest from stable versions. To be honest, I have checked our internal s/w repository and do not see anything newer for this model - no betas, no hotpatches... And it is more than a year old, so it must be stable enough for production usage.
I have seen it many times before when perfectly working old equipment breaks on reboot. Just a reboot, no updates, nothing fancy. It is a specific of electronic equipment that some modules that already have defect just die on power cycle. And some 1910 are quite old, especially if we take into account that many switches work in sub-optimal environmental conditions - humidity, temperature etc. etc. Maybe before proceeding with an upgrade you can perform a reboot to verify that the device has potential to survive the upgrade...
Taking all this into account I would not jump into conclusions that the upgrade was the trigger. Even if it was, it could be a defective flash memory that currupted newly uploaded image. But in this case console ports would work and you would see certain error messages. But if after upgrade console ports go down and switches do not light up port LEDs on connection, I would definitely suspect a hardware issue rather that a software one. Another point - if that would be an incompatibility between releases, why 3 of your switches were successfully upgraded and ? Of course, this point makes sense if initial s/w versions before the upgrade were the same on working and non-working devices.
I am not excluding a possibility of an unkown incompatibility problem that you may hit, just one thing does not fit into this scheme - dead console ports. Normally you should see at least a POST test result on a bootup. And if there is an issue with s/w image, the bootrom should inform you that the image has failed to load. BTW, try the following test - leave the console connected with terminal client open and reboot the switch. Let's see if you get a POST test results at least.
Hi,
Has my solution helped you resolve the query or do you need more assistance?
Thanks!
After updating the firmware the switch does not enter the interface and shows an error message when loading the firmware file. Right after this message he enters a screen with 10 options, we downloaded the firmware using the first option on that screen. the switch also shows that the .cfg and .txt files are missing. How can I solve this problem because I need the switch to connect the company floors. Thank you for your cooperation.
Hello
The screen with 10 options is called bootrom menu or bootware. In order to understand the situation, please clarify the following:
1. What was the initial version of the Comware installed before the last upgrade attempt?
2. What is the version you are trying to upgrade to? The latest one 2222P11 or older?
Also, please, connect a console cable to the switch, start the terminal program (PuTTY, SecureCRT, etc.), reboot the switch while the console session is active and wait the the bootrom menu to appear.
The bootrom menu will look like this:
BOOT MENU
1. Download application file to flash
2. Select application file to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter bootrom upgrade menu
7. Skip current configuration file
8. Reserved
9. Set switch startup mode
0. Reboot
Ctrl+F:Format File System
Ctrl+D: Enter Debugging Mode
Ctrl+T: Enter Board Test Environment
Select option 3. Check if you get the list of files on the flash memory.
Copy ALL output of the console session (from the reboot event till the boorom option 3 list) and paste it here as I need to see what is the current situation over there.
I won't be able to help you if you don't follow the instructions in my last message. I don't have any idea what you have done so far and the only way to understand the current state of the switch is to collect the data in a proper way.
If you don't have time for information collection, then try to resolve the issue by yourself reading the release notes https://support.hpe.com/hpesc/public/docDisplay?docId=a00061838en_us , section "Upgrading software from the Boot menu", page 67. Access the bootmenu, delete the .bin file you have already uploaded, re-upload it again, set the file's attribute as Main and reboot. Also, I would consider updating the bootrom itself, in the zip file with s/w you can find .btm file. The bootrom has the option "6. Enter bootrom upgrade menu", enter this menu and use .btm file for update.
The captioned switch is situated on the far side of a wifi bridge with wifi devices landing on trunk ports and carrying tagged traffic.
On the remote switch there is at present only one acess port configured which is receiving vlan traffic for a subnet and all is working as it should with remote pcs getting address from dhcp server and able to access gateway and WAN. So there are only two ports connected to the switch, one for the wifi device and one for the PCs.
The management port, Port 1 has been given a fixed IP within my management subnet for fixed devices and is Un-tagged on the management Vlan. My problem is that when I try and connect to the remote switch using browser from an access port on another managed switch on the management subnet with management Vlan I can make a connection and log in but the connection is very slow and drops very frequently. I am sure I have forgotten something and seek help please.
Good day. I apologize in advance for my level of English, I am from Russia. I am using an HP 1810-48G J9660A Switch. Power outage occurred during the firmware update process. Now, after startup and initialization, all ports of the switch are inactive, none of the ports are working, resetting to factory settings did not help. How can I restore the firmware of the switch? There is no external console port, but there is a connector labeled COM on the switch board. I understand that through this port I can restore the device, but I need instructions on how to proceed. An RS-232 cable is available, but I do not know how to establish a connection with the device.
Hi,
Kindly go through below link for HP V1810-48G Switch Installation and Getting Started Guide and refer pg.5 for reset and clear button.
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c02879280
Thanks!
Hi All
I have seen some posts regarding this on different forums, all with different outcomes and none of which have worked.
I have just purchased 4 new 1920s JL381A switches to replace some aged and unfriendly 1810's.
I their configurations they are end of point and feed either 24 or 48 desktop's. I have always made sure there is at least 2 Link Agregated ports from the parent switch which is either a 1910 or 2920 (1910's all have 4 Links and 2920's 10gb fibre)
I have never had any issues with the 1910s or 2920 creating links or trunks, either in CLI or web mode. However introduce the 1920's and they point blank refuse to work. I have a feel it could be STP linked, but no matter what I try it will not talk in a agregated form.
Example of setup 1
2920, TRK1 on Port 42-43. Vlan 3 Untagged, Vlan 8-10 Tagged.
1920s, TRK1 on Port 47-48, Vlan 3 Untagged, Vlan 8-10 Tagged. Admin mode enabled, STP enabled, Static Mode Enabled, Load Balance, Source/Dest Mac, VLAN, Ethertype, Incomoning port.
Save both configs and then plug in cables. No traffic is passed and the 2920 reports there is an issue with this configuration, and thats it. It I remove the trunks and have a single port link it works as normal.
I am not that up on networking as its seldom I have to use it, but these switches have never let me down before. I am sure it is a simple mistake but no idea where to start
Thanks,
Hello,
I think you can start with checking if both switches have compatible trunking mode. It can be static or dynamic (with LACP). From your description of the 1920s configuration, it seems like you have configured static mode there. So please check if the trunk on the 2920 is also in static mode. You can use the command "show trunk" in the CLI of the 2920.
The last column of the output will indicate the type of the trunk. It will be either LACP (which means dynamic) or trunk (which means static). If you see LACP then the settings are incompatible at the moment.
You can either make the trunk static on the 2920.
Or disable static mode on the 1920s which will enable dynamic mode.
Dynamic mode has the adventage that it uses LACP PDUs to verify that the cables are connected correctly to the same device on the other side. If it identifies that both ports connect to different switches it will disable the ports and prevent issues.
no, this method does not help now. most likely, the firmware of the switch is damaged. none of the switch port is working, so there is no way to connect to the web interface
Hi
Is this your connectivity ?
PC1<-->Switch1<-->WifiBridge1 (( )) WifiBridge2 <-->Switch2<-->PC2
And are you trying to connect to Swich2 from PC1 and you see that the connection is slow and drops frequently? If yes, there are many thing to check in between, the Wifi signal strength between both the bridges, if there are any faulty patch cords betwenn the devices, if there is an broadcast storm in the network etc.
Hello Guys, good morning!
I have a JL381A and i have a setup that sometimes i need to send a public ip adress to my client from my ISP, and i have to setup a bandwitch direct from my switch.. and i cant find anywhere " usable " to do it from this switch.
I have the latest firmware PD.02..14
I already looked everywhere, since manual and looked on the internet.. and i can`t find a thing.. i am missing something?
Theres a way i can control like.. i want this port to do only 10 MB ?
Thanks in Advantage.
wrote: I have a JL381A and i have a setup that sometimes i need to send a public ip adress to my client from my ISP, and i have to setup a bandwitch direct from my switch.. and i cant find anywhere " usable " to do it from this switch.
Hi! please...are you able to rephrase your highlighted statement above? what are you meaning? what is your exact purpose?
Sure...
Im not the ISP.. i work in IT that recieves the link from a isp.. and the clients buy from me a link, and i create a vlan and make bandwitch and distribute the way the client wants.. cable.. wifi.. it works like that 99% of the cases.
Somethimes a client want a public ip adress , to make a video call, or anything he wants.. and i cant make the bandwitch from my router.. so i want to lock the bandwidth from the switch..
do i make myself more clear?
Thanks!
Now it's more clear than before.
I'm supposing your VLAN IDs (one for each of your clients) at access level (untagged) are going to match the VLAN IDs tagged into the uplink to your Router (which should do the routing and NAT - and PAT - to Internet).
If so you should play with COS or ACL and committing rate (but you should be careful about the direction - incoming to the Switch or outgoing from the Switch - on which the ACL applies because that has an impact on traffic outgoing to your Router from the matching VLAN ID or traffic incoming from your Router with destination the matched VLAN ID). Personally I never tried on a HPE OfficeConnect 1920S.
Have a look at HPE OfficeConnect Support Portal (filter for "1920S") for all released documentation/software and directly HPE OfficeConnect 1920S Switch Series Management and Configuration guide for configuration details.