I’ve got a client that has a couple of Storwize V5000 storage arrays. I needed to get the serial numbers for them today, but I could not find them in the GUI?
Solution
As usual things are much simpler at command line, SSH into the storage array and simply use the following command;
[box]lsenclosure[/box]
Note: As you can see, I’ve got one Controller (with the cans in it,) and one expansion shelf. The first part of the serial denotes the model e.g. 2078-24C denotes v5000 Series controller, so in this case the serial number would be 2078-24C / 78A3381 and I’ve got an Expansion Shelf 2078-24E / 78D2CTT.
Related Articles, References, Credits, or External Links
Note: This procedure allows you to reset the password WITHOUT LOSING THE CONFIG
You need to access a Cisco ASA device and do not have the passwords, there can be lots of reasons for this, lack of good documentation, bought a second hand firewall, the last firewall admin never told anyone etc.
This method does require physical access to the ASA, a console cable, and a machine running some terminal emulation software.
Note: This procedure is for Cisco ASA 5500-X and ASA 5500 Firewalls, for Cisco PIX go here, and Cisco Catalyst go here.
Password Recovery ASA5505-X
Password Recovery ASA 5500
Password Recovery / Reset Procedure for ASA 5500-X/5500 Firewalls
Below is a run though on changing the Cisco ASA passwords (setting them to blank then changing them to something else). Basically you boot the ASA to its very basic shell operating system (ROMMON) then force it to reboot without loading its configuration. At this point you can load the config, without having to enter a password, manually change all the passwords, and finally set the ASA to boot properly again.
Below I’ve used both HyperTerminal and Putty to do the same thing, you can use either, or another terminal emulation piece of software, the procedure is the same.
1. Connect to the the ASA via a console cable (settings 9600/8/None/1/None).
2. Reboot the ASA, and as it boots press Esc to interrupt the normal boot sequence and boot to ROMMON mode.
3. Execute the “confreg” command and take a note of the number that’s listed (copy it to notepad to be on the safe side).
4. Answer the questions as follows (Note: Just pressing Enter will supply the default answer). Answer no to all apart from the TWO listed below:
ON AN ASA 5500-X (Slightly Different)
do you wish to change the configuration? y/n [n]: Y<<< THIS ONE disable “password recovery”? y/n [n]: n disable “display break prompt”? y/n [n]: n enable “ignore system configuration”? y/n [n]: Y<<< AND THIS ONE disable “auto-boot image in disks”? y/n [n]: n change console baud rate? y/n [n]: n select specific image in disks to boot? y/n [n]: n
ON AN ASA 5500
Do you wish to change this configuration? y/n [n]:Y<<< THIS ONE enable boot to ROMMON prompt? y/n [n]:
enable TFTP netboot? y/n [n]:
enable Flash boot? y/n [n]:
select specific Flash image index? y/n [n]: disable system configuration? y/n [n]: Y<<< AND THIS ONE go to ROMMON prompt if netboot fails? y/n [n]:
enable passing NVRAM file specs in auto-boot mode? y/n [n]:
disable display of BREAK or ESC key prompt during auto-boot? y/n [n]:
5. You may notice, that the configuration register has changed, on an ASA 5500 to 0x00000040, or on an ASA5505-X to 0x00000041, to boot the firewall execute the “boot” command.
6. This time when the ASA boots it will start with a {blank} enable password, you can load the normal config into memory with a “copy startup-config running-config” command.
7. Now you are in enable mode with the correct config loaded, you can change the passwords, and once completed, change the configuration register setting back with a config-register {paste in the number you saved earlier} command, or simply a no config-register command. Save the changes, (write mem) and reboot the firewall.
Related Articles, References, Credits, or External Links
A while back I ran though “Managing Cisco ASA devices via the ASDM with Ubuntu“, I prefer to work at command line, with a new firewall my only choice is via the console port, In a windows environment I can fire up Hyperterminal and I’m away. With Linux there a couple of things to do first.
Solution
Step 1 (Get the Serial / RS232 / COM Port working)
As pictured above, this is being done on my Acer Netbook so I don’t have a serial port. I need to use a USB to Serial converter, If your machine has a serial port then simply skip this section.
1. Plug in your serial converter and wait a few seconds, open a terminal window (Applications > Accessories > Terminal) and issue the following command,
[box]dmesg[/box]
2. Amazingly it looks like been installed with the correct driver, without any effort by me at all! Lets make sure, unplug the USB to serial converter then issue the following command,
[box]lusb[/box]
Then plug the device back in and run the same command, notice the serial port has popped onto the list.
Note: If you not as lucky as me follow the excellent advice here to install the drivers you need.
Step 2 Install and Configure Minicom
1. Open a terminal window and issue the following command,
[box]sudo apt-get install minicom[/box]
Tap in your password, then enter “Y” for yes when prompted.
4. We need to know the connection name for the USB to Serial converter, issue the following command (See mines called ttyUSB0).
[box]dmesg | grep tty[/box]
5. Now lets fire up Minicom with the following command,
[box]sudo minicom[/box]
Tap in your password again, then as requested press CTRL+A, then Z.
6. To configure the serial settings press O (that’s O for Oscar not zero).
7. Select “Serial Port Setup”.
8. Press A to set the device.
9. As we discovered (above) ours is called ttyUSB0, so change the device to /dev/ttyUSB0.
10. Press C to change the connection speed to 9600 baud, Press Q (to set 8 bits, no stop bit, and 1 parity bit. On mine this was set by default), press {enter} to exit.
11. Press F to turn off hardware flow control (Some posts will say leave it on, I generally turn if off and I’ve never seen anything break!). Press G to disable software flow control (if enabled).
12. Then Select “Save setup as..”, and give is a sensible name. (If you went back too far simply press O again to get back here).
13. Now the settings are saved you can launch them at anytime with,
[box]sudo minicom {filename}[/box]
Note: Sometimes your serial drive gets locked up but a reboot will solve the problem.
14. Here’s me connected to an ancient old catalyst switch.
Some versions of Windows 8 (Windows 8 Pro for example) ask for the unlock code as soon as you install them, I installed Windows 8 Enterprise on my PC at home today, and I couldn’t even change my user photo, because Windows hadn’t activated. When I tried, this is what happened.
Solution
As I had not yet installed a Windows unlock code, it’s safe to assume it had it’s in built KMS code, so I would need to change it to my own Windows code.
1. Press Windows Key+X to bring up the Advanced Context Menu >Select ‘Command Prompt (Admin)’.
2. Run the following command (where 12345-ABCDE-12345-ABCDE-12345 is YOUR Windows code);
I installed one of these a couple of weeks ago, and there’s some good documentation with the module itself so installing it into the UPS and giving it an IP address was easy, getting the right client software to talk to it was a pain.
Solution
Configure the Network Module
1. Physically install the module in the UPS, it’s fixed with two screws and you can install it with the UPS powered on.
2. It takes a while for the card to boot, pop in the console cable that came with it (into the Settings/AUX socket – see above). Fire up PuTTy and connect via serial.
Note: Standard Serial Settings,
Bits per second—9600
Data bits—8
Parity—None
Stop bits—1
Flow control—None
3. The default password is ‘admin’
4. Use the menus presented to change the IP details, you MUST restart the module when you are finished or the IP address WONT change.
5. Once its rebooted (again this takes a while) you can login with a web browser, (username admin password admin).
Configure the Client Machines.
1. Download HP Power Protector, (Note: there is no client and administrator software any more, this software will do BOTH. The network module has the administration software built in).
2. Install the software on your machine, and login (again username admin password admin).
3. Select client > Save.
4. Select the Device Discovery tab. The software usually detects the network module on its own quite quickly, if it does not you can use the options on right to do a scan.
Ports Required for HP UPS Network Module
If you are connecting through a firewall (or you machine has a software firewall), make sure the following six ports are open.
5. When it’s fully detected, select the network module and select ‘Configure power source’, supply the login credentials for the network module, and the load segment the machine is plugged into (see below) > Save.
6. Back in the web console of the network module > Open ‘Notified Applications’ and in about 5-10 minutes your server should appear.
Related Articles, References, Credits, or External Links
