CrackedTech

HP Procurve 8200 and 5400 modular switches have a USB port which can be used to upgrade the firmware without the need of TFTP or XMODEM (in case you erased both images from both flash (primary and secondary), which takes very long time (up to 3-4 hours)). You can put your new firmware in USB, plug it in the USB port of Switch and copy it into flash of the switch. HP-8212zl# copy usb flash K_15_10_0009.swi primary In case you are getting error like " Error accessing USB device ", then you can check the solution below: Try accessing the usb device by issuing "dir" command from the priviledge mode: HP-8212zl# dir Error accessing USB device The most common cause of this issue is that the USB device that we use is formatted as Fat 32. The Procurve devices are still not able to read the FAT 32 file systems and hence, the switch will not be able to access anything in that USB device. To make the USB device work in the switch, you need to format the USB device as FAT 16...

You can download latest firmwares for HP networking devices (FREE and Original from HP) from the link below: https://h10145.www1.hpe.com/downloads/ProductsList.aspx?lang=&cc=&prodSeriesId= This link includes the firmwares for ALL HP networking devices including firmware for Procurve switches (E-series), H3C switches (A-series), MSR Routers, H3C SecPath UTMs, etc. Just type the model (or part number) you are looking to upgrade in the search box as shown (Click to enlarge).

Telnet failed: Can't send after socket shutdown. If you are getting this error on HP Procurve switch, it means that the Procurve switch is not accepting telnet sessions. A common reason for this is that you might have enabled SSH (and disabled telnet), or telnet on the swtich is not enabled at all (by default, telnet is disabled on Procurve switches). Telnet can be enabled on a Procurve switch as follows: Procurve-Switch (config)# telnet-server Thats it. Now you should be able to telnet your Procurve switch. Note: If you are in a different vlan than the management IP address of the switch, you need to set the correct default-gateway on the switch (only for edge switches).

So recently, a new flavor of Linux had been introduced as Kali Linux and is being advertised on Backtrack website. What is this fuss all about? What is Kali Linux and why are Backtrack guys advertising it. To know the answer, read below. Kali Linux is the Next-Generation Backtrack Linux. Or as some people might say, Backtrack Linux 6.0 = Kali Linux 1.0 So why did they changed the name of the distribution and created the confusion in the first place? The main reason was that the new release of Backtrack (i.e., Kali Linux now onwards) is a very different and advance version . It has many differences as compared to the original Backtrack distribution, and hence, using the same name with new version number would not do justice to their work. Hence they came up with a new name. Now the question arises, what are the main differences (upgrades) in Kali Linux as compared to the original Backtrack Linux? To know the answer, see what the documentation at Kali Linux says here ...

Use the password recovery method outlined below to define a new password for the admin username:  (This method works for most of the 3-Com switches) 1. Access the Command Line Interface and enter the user name "recover" and password "recover" to place your unit in password recovery mode. The unit will remain in password recovery mode for a maximum of 30 seconds, before it returns to the CLI login prompt.  2. During these 30 seconds, perform a hard reboot on the unit while it is still in password recovery mode by turning it off, waiting for a few seconds, and then switching it on again.  3. When the unit has rebooted following the hard reboot enter a new password for the "admin" user account.  4. Enter enable to leave password recovery enabled (to enable recovery of the password next time if you forget), or enter disable to turn it off (not recommended). You are now logged in as the default "admin" user. 

In case you are configuring H3C SecPath UTM for stateful failover, and the state is stuck in "Independence" state, then make sure your backup link is configured properly  (it should NOT show in "Device Management > Interface").  Although this is not documented by H3C, running different firmware versions on both the H3C SecPath UTMs will also cause them to remain in "Independence" state and the "Synchronized" state will never be reached.

A new blog/website for "Helping Hands Kuwait" for Morba, Dahiwali and Kond is launched at  http://helpinghandskuwait.wordpress.com  on 9th Feb 2013.