Stopped a remote Blade for Backup, After backing up....

Dan Loring · ‎03-31-2011

After backing up a blade I went into the CM, edit Device, Admin, Virtualization, Actions, Start Blade. It is up and running, I can ping it, but I cannot RDP to the server to verify that it is backup. It seems like the server is shut down still. What options do I have to restart this remote virtual server???

Michael Korenbaum · ‎03-31-2011

Dan,

Verify the virtual blade is running and the vnc server is active on the CLI of the WAAS deivce

Example output:

pdi-274-sj#sh virtual-blade 1

virtual-blade 1

config:

device cpu qemu64

device nic virtio

device disk IDE

device keyboard en-us

memory 1024

disk 20

interface 1 bridge GigabitEthernet 1/0 mac-address 00:21:D8:AB:5A:C7

cpu-list 1

no boot fd-image

boot cd-image disk /local1/vbs/virtio-drivers.iso

boot from disk

autostart

state:

running

serial console session inactive

vnc server active

no vnc client connected

current cd /local1/vbs/virtio-drivers.iso

current floppy [not inserted]

If it is running and vnc server is active, try using VNC to console to the VB; maybe RDP was disabled in Windows for some reason?

If you don't have a VNC client on your PC you can download something like TightVNC for free.

http://www.tightvnc.com/download.php

Then connect to the management IP of the WAAS device on port 1.

Regards,

Mike Korenbaum

Cisco WAAS PDI Help Desk

http://www.cisco.com/go/pdihelpdesk

Dan Loring · ‎03-31-2011

Here is my output from the CM. It looks like it is booting from the cd ROM, is there a way of shutting down that option? I have a vnc client, but was not able to connect, probabley because it is at the server setup screen???

virtual-blade 1

config:

description Needham DC

device cpu qemu64

device nic rtl8139

device disk IDE

device keyboard en-us

memory 1024

disk 30

interface 1 bridge GigabitEthernet 1/0 mac-address 00:21:D8:AC:2C:6F

cpu-list 1

no boot fd-image

boot cd-image disk /local1/vbs/en_ws_2003_std_sp1_vl.iso

boot from cd-rom

autostart

state:

running

serial console session inactive

vnc server active

no vnc client connected

current cd /local1/vbs/en_ws_2003_std_sp1_vl.iso

current floppy [not inserted]

Michael Korenbaum · ‎03-31-2011

Dan,

Stop the VB and change the boot paramter to boot from disk.

Ex.

pdi-274-sj#virtual-blade 1 stop

pdi-274-sj#conf t

pdi-274-sj(config)#virtual-blade 1

pdi-274-sj(config-vb)#boot from disk

pdi-274-sj#virtual-blade 1 start

Regards,

Mike

Dan Loring · ‎03-31-2011

Mike,

I applied those settings, as well as "no boot cd-image" , but it seems the server itself is still shutdown. I have a vnc client and a RDP client and they both fail, and the server is not pinging, I was pinging the device earlier and not the server IP. Here is my output now after putting new commands to boot from disc. It seems the blade is started, but the virtual machine is still shutdown.......

virtual-blade 1

config:

description Needham DC

device cpu qemu64

device nic rtl8139

device disk IDE

device keyboard en-us

memory 1024

disk 30

interface 1 bridge GigabitEthernet 1/0 mac-address 00:21:D8:AC:2C:6F

cpu-list 1

no boot fd-image

no boot cd-image

boot from disk

autostart

state:

running

serial console session inactive

vnc server active

no vnc client connected

current cd [not inserted]

current floppy [not inserted]

Michael Korenbaum · ‎03-31-2011

Dan,

Can you ping the Gig 1/0 interface of the WAVE?

When you attempt to connect to the VB console via VNC are you using WAVE IP or the Windows IP? It should be the IP address of the Gig 1/0 on the WAVE on port 1.

Regardless of the state of the Windows VM I would expect you do have some output on your VNC console session.

Are you local to the WAVE or remote? Is it possible that something is blocking your VNC session between you and the WAVE?

Dan Loring · ‎03-31-2011

Yes I can ping the gig 1/0. I can also connect SSH via putty, and it is showing up in the VM in regards to acceleration and optimization.

When I try to connect to the gig 1/0 interface via VNC it just flashes and goes away, no error. I have always just used RDP to connect to that server, but when I try to RDP it errors out and says the server is turned off. Unfortunately I am remote to the device. Would a reboot of the entire device be out of the question at this point?

Michael Korenbaum · ‎03-31-2011

Maybe you can try from a local PC? Or try with a different VNC client? You had to at one point use VNC during the initial setup of Windows, prior to enabling RDP in Windows.

I wouldn't think you would want to reload the device in the middle of the day, but certainly can try that after hours if you want.

Dan Loring · ‎03-31-2011

okay, so I downloaded the tightvnc, and was able to connect, but it is just a blank screen... Would a virtual-blade reset kick start the virtual machine, or would that not be a good command to try.

Michael Korenbaum · ‎03-31-2011

I would connect to the console with TightVNC, then issue that command and see if you get any output on the screen, maybe some errors during bootup?

If it's not operational right now/ serving clients I don't see any reason why you couldn't reset the VB.

Dan Loring · ‎03-31-2011

okay so I issued the reset command and it came up with the attached screen, basically hit F12 for a boot device, If I hit F12 I get hard drive, cd, network and floppy options, and none of them boot. I also at this point have issued a reload command and we are back at the blank screen. any other ideas???? Am I at the point of trying to reload the image that I backed up, or are there other steps I can take before going down this road? What are the chances the backup got pushed without corruption, or do you think the image is okay, but there is some other issue with the system?

Michael Korenbaum · ‎03-31-2011

Dan,

You can certainly try restoring your VB disk as per the instructions here:

http://www.cisco.com/en/US/prod/collateral/contnetw/ps5680/ps6870/white_paper_c11-609580.html#wp9000241

If you don't get anything after "Press F12" it would seems that the VB is not finding your virtual disk to load the OS.

Regards,

Mike

Dan Loring · ‎03-31-2011

Where should the virtual disc be? If I where to go in and point it to the virtual disc what directory would it be located in? Here is my local1 dir.(see below) In the vbs dir there is an iso, I tried pointing the boot to that, but got no luck. I also attached my current show virtual blade1(see bottom) any of this obviousely out of whack??

##################################################################################

Needham-AA(config-vb)#boot from disk

Needham-AA(config-vb)#boot cd-image disk /local1/vbs/en_ws_2003_std_sp1_vl.iso

###################################################################################

Needham-AA#cd local1

Needham-AA#dir

size time of last change name

-------------- ------------------------- -----------

125052 Tue Mar 29 12:58:00 2011 UcliEvt.bak

58752 Thu Mar 31 13:53:01 2011 UcliEvt.log

4096 Wed Nov 3 21:18:39 2010

actona

4096 Thu Mar 31 12:37:28 2011

cliTemp

4096 Wed Nov 3 21:20:57 2010

core_dir

4096 Wed Nov 3 21:22:27 2010

crash

0 Thu Mar 31 12:48:52 2011 db-downgrade.log

3066 Sun Jan 23 20:11:39 2011 dbupgrade.log

634 Wed Mar 16 16:01:27 2011 diagnostic_report.txt

1002 Wed Mar 16 16:01:27 2011 diagnostic_report.xml

4096 Mon Mar 28 12:58:15 2011

downgrade

4096 Thu Mar 31 12:52:19 2011

errorlog

5574 Thu Mar 31 12:50:28 2011 irqbal_debug.txt

4096 Thu Mar 31 12:51:08 2011

logs

16384 Wed Nov 3 21:14:31 2010

lost+found

4096 Wed Nov 3 21:20:55 2010

pki

4096 Thu Mar 31 03:26:00 2011

sa

24576 Thu Mar 31 13:54:15 2011

service_logs

4096 Wed Nov 3 21:22:25 2010

spool

715287 Thu Mar 31 13:51:25 2011 syslog.txt

4096 Wed Nov 3 21:20:53 2010

var

4096 Fri Jan 7 07:39:39 2011

vbs

508 Wed Nov 3 21:20:54 2010 wdd.sh.signed

####################################################################################

Needham-AA#sh virtual-blade 1

virtual-blade 1

config:

description Needham DC

device cpu qemu64

device nic rtl8139

device disk IDE

device keyboard en-us

memory 1024

disk 30

interface 1 bridge GigabitEthernet 1/0 mac-address 00:21:D8:AC:2C:6F

cpu-list 1

no boot fd-image

boot cd-image disk /local1/vbs/en_ws_2003_std_sp1_vl.iso

boot from disk

autostart

state:

running

serial console session inactive

vnc server active

vnc client connected

current cd /local1/vbs/en_ws_2003_std_sp1_vl.iso

current floppy [not inserted]

Michael Korenbaum · ‎03-31-2011

The virtual disk file(s) are not exposed via the directories available on the CLI.

However, you are able to restore the disk file(s) that were previously backed up per the process listed here:

http://www.cisco.com/en/US/prod/collateral/contnetw/ps5680/ps6870/white_paper_c11-609580.html#wp9000241

Were you able to restore your previous backup?

Dan Loring · ‎04-01-2011

In the process of restoring the blade that I backed up. Hopefully it backed up a good one and not the corrupted one that is there now. If this process fails do you have an article that walks you through building a new blade server?