GBE2 Switch locked with tacacs

[Steven Mitchell_1]

I have a GBE2 switch and I want to get it back to factory default. I try hitting +M during memory testing to start a hardware reset. The switch has tacacs enabled and the back doors closed so it will not respond to +M during mem test. Is there another way to get back to factory default? It drops quickly into production mode and then asks for the tacacs username and password. I tried hitting the # key during self test and nothing happens.

The following shows the startup messages:

Memory Test ................

Production Mode

Starting POST...
Checking PCI bus.................................. PASSED.
Checking MP I2c................................... PASSED.
Checking Interrupt................................ PASSED.

Post Passed.

## Booting image at fff30010 ...
Image Name: vmlinux.bin.gz
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 450563 Bytes = 440 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Current stack ends at 0x07B7FBB0 => set upper limit to 0x00800000
## cmdline at 0x007FFF00 ... 0x007FFF08
## Loading RAMDisk Image at ff000010 ...
Image Name: RootFileSystem
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 3059325 Bytes = 2987 kB = 2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## initrd at 0xFF000050 ... 0xFF2EAECC (len=3059325=0x2EAE7D)
Loading Ramdisk to 06115000, end 063ffe7d ... OK
## Transferring control to Linux (at address 00000000) ...
.......................................
Board set to boot into production.

Found AppOS image1, Length = 3140777.

Press -o to use the other image...
Checking CRC over AppOS image1... Image1 CRC checked.

Initializing Production Mode ...
System booted on soft reset
now clear MPM grant
PCI unit 0: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI unit 1: Dev 0x5671, Rev 0x02, Chip BCM5671_A1, Driver BCM5670_A0
PCI unit 2: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI device BCM5690_A2 attached as unit 0.
PCI device BCM5671_A1 attached as unit 1.
PCI device BCM5690_A2 attached as unit 2.

GEA initialized for unit 0 . . . . . . . . . . . . . . . . . . . . DONE
GEA initialized for unit 1 . . . . . . . . . . . . . . . . . . . . DONE
GEA initialized for unit 2 . . . . . . . . . . . . . . . . . . . . DONE
HP ProLiant BL p-Class GbE2 Interconnect Switch A
Rebooted because of power cycle.
Booting complete
Comparing the newly updated rack info

Current
=======
RackID: unknown
Enclosure ID: unknown
RackName: unknown
EnclosureName: unknown
6:43:41 Thu Jan 21, 2010:
Version 3.1.0 from FLASH image1, active config block.
Note: Port 19 mode is changed to full duplex for 1000 Mbps operation.
Note: Port 20 mode is changed to full duplex for 1000 Mbps operation.
No saved HTTPS certificate - generating.....

Jan 21 6:44:10 INFO ufd: Uplink Failure Detection enabled

HP ProLiant BL p-Class GbE2 Interconnect Switch A.

Copyright(C)2003 Hewlett-Packard Development Company, L.P.


***************************************************************
* !!!WARNING!!! *
* Unauthorized access to this system is prohibited. *
* System access tracking is enabled. *
* IAG Network Services *
***************************************************************


Enter tacacs username:
Jan 21 6:44:20 WARNING ufd: Link to monitor is down.

Jan 21 6:44:20 WARNING ufd: Link to disable is auto-disabled.


Enter tacacs username: tacacs
Enter tacacs password:

[Lmm_1]

Are both Backdoor and Secure Backdoor disabled? If so, you might want to try this:

- Reboot the switch
- During boot memory test, while it is doing the dots, do a shift + t

The switch should boot on diagnostic mode, use password "admin" if needed, then change conf block to default and reset the switch again:


>> Diagnostics# .

[Diagnostics Menu]
- System ---------------------------------------------------------------------
system - System Menu
ports - Port Menu
eeprom - Manufacturing EEPROM Menu
flash - Flash Memory Menu
manu - Manufacturing Test Menu
global - Global Commands Menu
boot - Boot Menu
- Devices --------------------------------------------------------------------
i2c - I2C Utilities Menu
mp - MP Complex Tests Menu
helix - Helix Complex Tests Menu
- Ports ----------------------------------------------------------------------
extn - External Ports Tests Menu
mgmt - Management Module Ports Tests Menu
serdes - SerDes Ports Tests Menu
isl - InterSwitch Links Tests Menu
- Other ----------------------------------------------------------------------
led - LEDs Test Menu
path - Datapath Tests Menu
traf - Traffic Tests Menu
emi - Emission Tests Menu
bcm - Broadcom Low Level Utils Menu

>> Diagnostics# boot

[Boot Menu]
image - Select BLADEOS image 1 or 2
conf - Set Production Mode Config Block (f, a, or b)
reset - Reset The Switch

>> Diagnostics# conf
Next boot will use switch FACTORY (f) config block.

>> Diagnostics# reset
Confirm reset [y/n]: y
Resetting the System ...


.Lmm

[Steven Mitchell_1]

Thankyou for your response.

I have some switches that have not been locked and configured with tacacs and your method works fine with these.

The switches configured with tacacs and with the backdoors locked just ignore the shift + t command and go into production mode.

[Lmm_1]

I'm not aware of any other mechanism with Backdoor disabled.

[Steven Mitchell_1]

My apologies...

On the third go with hitting shift + t multiple times it went into manufacturing mode.

I was then able to reset the conf. This still left the tacacs enabled but now shift + m worked to push the switch into monitor mode.

Then logged in with ottawa and used i2c snd d0 9 66 1 followed by reset and the system came up in factory default.

Thanks for solving my problem.

[Lmm_1]

Ok cool

http://forums11.itrc.hp.com/service/forums/helptips.do?admit=109447626+1264112954316+28353475

[connardo]

Hi sir,

thanks for the post,

i have tried on the Gbe2 c and the procedure related here did not work

Shift +t does not do any thing....

event typing this many time : no reaction of the system

the boot process continues without any interrruption.

have you got as solution ?