Bootvar and boot command

Hi all,
I have recently upgrade our Failover Active/Standby ASA software. Everything works flawlessly. Except I have the following question regarding the boot and bootvar command.
After the upgrade, both devices come with the new IOS image. However, when I issue show bootvar command, it displays the old image. I also in the running config, the command boot system dish0/.... still points to the old image. Yet show run config, and show ver display the new image.
Now, concerns... If the ASA reboots, would it come back with the new image, even though the boot system in the running config is pointed to the old config?
2. IS it better not taking the risk, and just update the running config with the new image?
Thanks,

1) If you reboot it as it is then the firewall will used the image set in the boot'system/bootvar variable.
Make sure you fix this before rebooting.
How to:
configure terminal
clear configure boot
boot system flash://new-image.bin
wr
Then
sh run boot
If it's showing the new image you are good to go.
Regards,
Jcarvaja

Similar Messages

How can i install snow leopard on my mac G5 using a command line and booting from an external usb rom, since my disk i have is not a bootable media

How can i install snow leopard on my mac G5 using a command line and booting from an external usb rom, since my disk i have is not a bootable media

Hi.
You simply can't. Snow Leopard is compiled in Intel binary only.
Good Luck.

Boot bootldr, boot bootstrap and boot system command?

Hello All,
Could anyone please explain me what the boot bootldr and boot bootstrap are? And how do they different from the boot system command?
I did not understand the description of these commands in the Cisco command reference document.
Thanks a lot,
Nitass

Hi Nitass.
Boot system is used to specify the system image that loads at startup i.e the full IOS image that system will load.
boot bootldr command is used to specified a boot loader image which is an image with only booting featues and few limited commands, this image is like a safe mode for the system where we fall back on if system is unable to boot from main image.
bootstrap is the minimum software that is required to recongnize and run the hardware. It comes both in software and hardwares with the software.Like in cat 6K on Sup's is a special hardware with an image on it.
HTH,
-amit singh

Won't Boot to Apple Hardware Test or accept Boot Commands

Hi All,
I would appreciate some help with this issue, I am trying to boot up to the Apple Hardware Test on my Install Disk 1 that shipped with my MacBook Pro 2.4GHz Model #A1226 ordered new with 4 gigs of memory (around Aug. 2007). I am currently running 10.5.6 and the install disk of course contains the Tiger OS. I have nothing plugging into my computer, other than the Power Adapter. I have the proper install disk inserted in the computer and am holding down the "d" key on my built in keyboard throughout startup, but it will not go to the AHT. It simply boots to the normal login screen for Leopard. In fact the only boot commands that I see any visible or audible confirmation that it has taken effect is the option key, taking me to selecting a Startup Manager and holding down the Power Button gives me a tone from the internal speaker after a few seconds.
Below are what I have tried with seemingly no effect:
"d"
"c"
"t"
Option-Command-"p"-"r" (no beeps)
Command-"v"
Command-"s"
Shift (not sure I should see or hear any confirmation, I don't have any login items set right now so I can't tell if it has any effect)
I have not tried an of the networked drive boot commands as I don't have any networked drives
The only way I have been able to boot from either the optical drive or another disk is either holding down the option key during boot up or selecting the drive from the startup manager in system preferences.
I can't seem to access the AHT an in any way. The reason I am trying to access it is because I have had a few weird intermittent problems that I can't put my finger on and would like to be able to rule hardware out.
I also just replaced my HD with a WD 320 gig drive after my original drive failed due to a physical error. I just restored my data, and all seems to be running well after a permissions repair and a disk repair while booted up on my install disk.
The intermittent problems I was talking about are very vague and rare so I is difficult to describe them other that just a hunch that something is still a bit off. One is the display, every once in a while, showing what looks like a massive bar code or UPC code on my screen. This is not like the bands with soft edges that seem to be a well documented issue with the early MBP but transparent lines of alternating width and brightness with hard edges. Again it looks just like a UPC code transposed on my screen. The other items are random freezing of the OS or the mouse and the fact that my keyboard does not respond to any but a few boot commands. Again all the things are either rare and intermittent or do not come up in daily use of my machine. But when taken together, seem to add up to the conclusion there is still some issue present (at least in my mind).
To recap my specific questions relate to not being able to run the Apple Hardware Test and many of the boot commands having no effect. If you can shed light on the other items mentioned, great!
Thank you!

At a guess, I would think this error code has to do with the video artifacts you are experiencing. You might try reseating all the cables to the display. If the position of the screen makes a difference, there may be damage to a cable, particularly where it goes through the hinge.
Apple is the keeper of the error codes. If you have access to an Apple Store, you could probably ask about this.
Don't know about the other intermittent problems. Does an external keyboard work? If so, there's likely a problem with the internal, maybe even again, a cable or connection.
You could also try creating a new use account and see if the keyboard and mouse problems persist. If not, there could be some sort of software corruption in your usual account. Ditto with the freezing.
Good luck!

Invalid node structure and Boot Camp 1.1.2

I downloaded Boot Camp 1.1.2 and during the installation of Mac Drivers I kept getting dialog boxes that the software i'm installing did not pass Windows Logo testing- I just ignored it.
After that Windows XP didn't recognise my keyboard, airport, ...
I prepared a new instalation with Boot Camp Assistant and i had an error message when the disk partition was processing.
I run Disk Utility from my Mac OS X install disk DVD and I got the following:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid node structure
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Please give me some help to repair my disk and to understand what happened.
MacBook Pro 2 GHz Mac OS X (10.4.8)

If you are unable to repair the drive you will need to repartition and reformat the drive.
I recommend a cloned backup to an external FW drive. You can use this procedure:
How to Clone Using Restore Option of Disk Utility
1. Select the destination drive on the Desktop and press COMMAND-I to open the Get Info window. At the bottom in the Ownership and Permissions section be sure the box labeled "Ignore Permissions on this Volume" is unchecked. Set Ownership and Permissions as follows: Owner=system with read/write; Group=admin with read/write; Other with read-only.
2. Open Disk Utility from the Utilities folder.
3. Select the backup or destination volume from the left side list.
4. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button.
5. Click on the Restore tab in the DU main window.
6. Select the backup or destination volume from the left side list and drag it to the Destination entry field.
7. Select the startup or source volume from the left side list and drag it to the Source entry field.
8. Double-check you got it right, then click on the Restore button.
For added precaution you can boot into safe mode before doing the clone.
You will only have to reinstall your third-party applications. All standard OS X applications will be reinstalled except for bundled applications such as iMovie, iDVD, Garageband, etc. These can be reinstalled using the Bundled Applications installer on the OS X Installer Disc.
If you make a cloned backup all your data will be on the backup. You can restore it afterwards by copying the folders to their respective locations on the startup volume.

How do I remove partitions "PV2" and "Boot Camp"?

I tried installing Windows 7 in Boot Camp and lost power during install. I want to completely start over but have partitions "PV2" and "Boot Camp" that I can't seem to remove. I have tried to remove partitions in Disk Utility but everything is grayed out. Boot Camp Assistant says "The disk appears to have been partitioned by another utility and can't be removed."

When I boot to recovery (Command+R) it gives me four options: Restore with Time Machine Backup, Reinstall OS X, Get Help Online, and Disk Utility. I am assuming I should erase the drives usings Disk Utility. I am able to select the PV2 and Boot Camp but when I select the "partition" tab the +/- buttons on the bottom is grayed out. I am not sure how exactly to "erase the entire drive." If you couldn't tell, I am a novice imac owner. I did make a backup using Time Machine earlier today.

How can I get rid of The Grey screen and boot my macbook?

Today I was on my MacBook Pro (bought July 2011) and it went to a blank blue screen. I powered it off and tried to restart it. It loaded the apple and spinning circle but it went to a grey screen and froze there. I've read and tried a lot of different things already but nothing has worked. I did the hardware test and it found no problems. I tried to safeboot it. I tried everything on here: http://support.apple.com/kb/TS2570 except the last suggestion (I'd rather not have to lose all my files unless absolutely nesseccary). I also tried the "hold Command + R keys" to try and get to utilities. Anything else out there that I could try? Not sure what the exact operating system is either.

I wouldn't assume that's the hard drive. The fact that the screen turned blue all of a sudden isn't necessarily an indication of a hard drive failure. Check out this post I made yesterday:
https://discussions.apple.com/message/21756819#21756819
My personal opinion would be to try and boot from an external hard drive with the appropriate OS installed. With a 2011 model, I would assume that should be Snow Leopard or later. AHT doesn't catch everything, and I don't know if it even does drive scans for bad blocks. I do know for a fact that it pretty much limits itself to digital interfaces and can't go beyond analog driver stages. For example, if the driver stages of a FireWire port or ethernet port are blown, AHT will report them as being OK.
If you got hit by a transient, which could indicate an internal supply problem or a line problem if you were connected to the internet via a wired connection or you were running off the charger, there's no telling what it might have caused the drive to do (if it's the drive) and it could easily cause the screen to suddenly go to blue, but what other damage was done?
My point is that you need to confirm what the source of the problems are. If there's a logic board problem, your drive and data may be OK. If the drive is bad, some of it may still be recoverable. The problem may very well be drive related, but I wouldn't go out and start throwing money at new parts without first confirming what the cause of the problems is.
Hope this helped, and good luck.

Correct Use of Boot Command

I was wondering what is the correct way to use the boot command.
If an image is installed on every switch in the stack, should each switch load it's own image or just the Masters image? Or, does it really matter if they are really the same image. But, if a switch in the stack dies for whatever reason then if there were 8 switches in the stack, number 8 would become 7 and it would have a incorrect boot statement as there wouldn't be a switch 8 anymore. Since flash: will always exist in the stack wouldn't it be better to use flash: in the boot statement?
For instance:
Switch 8
BOOT path-list : flash8:/c3750e-universalk9-mz.150-2.SE/c3750e-universalk9-mz.150-2.SE.bin
or
Switch 8
BOOT path-list : flash:/c3750e-universalk9-mz.150-2.SE/c3750e-universalk9-mz.150-2.SE.bin
Thank you - Pat

Thanks for the response Jody
Just so I understand -
you are saying that each switch should be configured to boot from flash: rather than flash:# in the switch stack?
So, no matter what the number switch a switch is in the stack, it's individual boot statement should be flash:Image
Hope that is clear - Pat

Mtrr: type mismatch for d8000000 / Grub boot command line

Hi,
Dmesg is showing:
mtrr: type mismatch for d8000000,2000000 old: uncachable new: write-combining
(DL380 G5 - generic KVM/LCD Monitor)
I googled for the problem found
Disable MTRR for vesafb. iirc, there's a boot command line option to do it.video=vesafb:nomtrr
Does anyone know this problem, how to fix it, how to put this into Grub to avoid the error on next boot?
Best regards

Is that for the video card you are using? In that case you can just edit "/etc/grub.conf" and add that clause to the line beginning with "kernel" and reboot.

Problem with boot commands on G3 iMac

My iMac G3 will not accept any boot commands like "C" or "CMD, ALT, P, R" etc... etc... when using the original Apple PRO keyboard.
The Pro keyboard is fine and all the keys work in OS X. For the sake of it i tried another keyboard from my Power Mac and the boot commands worked perfectly.
What could the problem be so?

Macintosh: How to Troubleshoot the Apple Pro Keyboard and Mouse
Apple Pro Keyboard: System Requirements

Macbook Air won't boot command prompts

So, my friend bought a macbook air from another friend and that friend cannot remember their admin password. I tell her no problem I can reformat it for you since I have the boot disk by using utilities. Here is where I run into my problem. I hold down the option key on startup and the screen comes up with only a lock and a spot for a password, that I dont' know.
So I try to enter single user mode (Command + S) so I can enter the commands to reset the password that way, but it does nothing and boots the computer as if I weren't pressing any buttons. My next thought was try resetting pram to make sure there are no problems there, well I booted with all the keys pressed but to be 100% hoenst not even sure if it reset.
Long story short I need to reformat w/o knowing the admin password and/or reset the admin password so I can reformat. Any thoughts or ideas?
Mac is a MacBook Air with OSX 10.6
1.6 GHz intel core 2 duo processor
2GB 667 MHz DDR2 SDRAM
Thanks in advanced for any advice.

The seller implemented a Firmware Password. You need that password to boot the computer as well as to remove the firmware password. This is not the same as the admin password. Ask the "friend" what the password is.

MacMini won't accept boot commands - HELP!

My MacMini recently had a fresh Leopard installation. Yesterday it wouldn't open any applications (click icon on dock and it would load the application and immediately quit) so I rebooted the machine. Now it boots, displays the apple symbol, blue screen and then Leopard standard background, the mouse cursor toggles between mouse pointer and colourful circle. Here it stops!
I have attempted to use the boot commands such as Command-T to access it via firewire but it ignores all commands (I cannot even boot from a bootable installation DVD). I have tested the keyboard and it isn't that.
Please HELP!

I had a similar experience where a brand new Mac Mini (Model Identifier: Macmini2,1) would intermittently fail to recognize the pre-boot command keys. Apple support decided it needed a new system board, which it got, but that did not fix the problem.
In this case an Apple aluminum/white keyboard worked as expected at the Apple store.
I was using a PC keyboard and mouse through a cheap PS/2 to USB adapter and the folks at the Apple store were quick to suggest that was the problem, but connecting my keyboard and adapter to another Mini of the same model at the Apple store worked perfectly.
In the end, the 'official' recommendation was to buy a 'USB 2.0 compatible keyboard'.
Well, a plain Logitech ($20 at Fry's) also failed! I decided to return the Mini and buy one that worked!
While carefully documenting the problem, it began working as expected!
It turned out that, in my case, the pre-boot commands only worked if the keyboard was connected to the outside USB port. That's the port nearest the right side of the mini when viewed from the back, under the audio out port.
This configuration has been working now for over a year with the original keyboard and adapter.
Try connecting the keyboard to the right-most USB port.
Regards,
-Glen

Sunfire 480R + boot command does not boot from disk

Hi All,
I'm trying to work out why when I type ok>boot
the server keeps booting off the network. It's almost as it does not find any disks and then since diag-device is set to net it tries that instead. The same happens even if I do an init 6 or reboot from solaris??
the output from eeprom looks like:
# eeprom
test-args: data not available.
diag-passes=1
local-mac-address?=false
silent-mode?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya
auto-boot-on-error?=false
load-base=16384
auto-boot?=true
boot-command=boot disk
diag-file: data not available.
diag-device=net
boot-file: data not available.
boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f124c1,0:a rootmirro
r disk net
use-nvramrc?=true
nvramrc=devalias rootmirror /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f232
61,0:a
security-mode=none
security-password: data not available.
security-#badlogins=0
fcode-debug?=false
diag-out-console=false
post-trigger=error-reset power-on-reset
diag-script=normal
diag-level=min
diag-switch?=false
obdiag-trigger=error-reset power-on-reset
error-reset-recovery=boot

Hello,
Sun Fire 480R ?
Maybe Fire v480 ?
This is device path for the two internal disks (per InfoDoc 21216):
Disk 1 /pci@9,600000/SUNW,qlc@2/fp@0,0
Disk 2 /pci@9,600000/SUNW,qlc@2/fp@1,0
These are your current settings in the OBP
boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f124c1,0:a rootmirror disk net
nvramrc=devalias rootmirror /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010f23261,0:a
Both point the the same first slot (location in the fc-al backplane), but use different WWNs.
Use show-disks to display the available disks and re-assign the boot-device accordingly.
Michael
P.S.: I just noticed that you never provided feedback in previous posts.

OPEN FIRM WARE SCREEN, ENTER MAC-BOOT COMMAND, GETS WEIRD SCREEN, ......

HELP- HELP- HELP-..."OPEN FIRMWARE/WON'T START-UP".....( IT WAS RUNNING, BUT DIED LIKE THE CORD WAS CUT )....G3 B&W 400MHZ OS 9.2.2, BATTERY GOOD, STARTS UP TO "OPEN FIRMWARE" SCREEN, ENTER "MAC-BOOT" COMMAND, GOES TO A BLUE-ISH/PURPLE TOP 1/2, YELLOW BOTTOM 1/2 SCREEN W/SMALL-ISH (APPROX. 2") MAC FACE THAT THEN GETS ABOUT 5 FOLDERS (STACKED FRT. TO BACK) COVERING MOST OF THE MAC FACE, WON'T GO BEYOND THIS WEIRD SCREEN, HAVE FOUND IMAC OPEN FIRMWARE COMMANDS I'M GOING TO TRY BUT DOUBT WILL WORK BEING THEIR FOR AN IMAC, I HAVE ALREADY DONE A TAP DANCE ON THE KEYBOARD HOPING TO STUMBLE ON TO AN UNKNOWN MYSTERY FIX COMMAND, ALSO DONE PRAM, CUDA, PROGRAMMER RESETS IN ORDER / OUT OF ORDER...AND SPOKE TO LOCAL MAC EXPERT REPAIRMAN, SAID HE'S NEVER SEEN SUCH A SCREEN...ANY IDEAS ANYONE ????..THANKS.. I WONDER IF IT'S BEYOND FIXING, IT'S NOT MY PRIMARY MACHINE & IT WAS NEAR FREE, BUT I HATE TO BE DEFEATED & TOSS IT TO RECYCLING. ....THANKS AGAIN...I'M AN EX-PORSCHE MECHANIC AND HAVE BEEN SELF TEACHING MYSELF ABOUT JUST OPERATING A MAC FOR 4 YRS., SO I'M NOT ALL THAT SHARP IN THE GEEK AREA......WAYNE146

Sorry about the "CAPS", old eyes & tired brain, + in hunt & peck typing method I forget to cap at start of new sentence.....I don't have camera capability at this time. I re-read my discription of the screen and it is worded very accurately, as I close my eye's and imagine the words I see this weird screen as described. When this first occured I tried booting from cd (holding c key down) 5+ minutes and nothing (x5). I pulled the battery a week ago to clear cache, also disconnected power sup. from mother board, hoping for a magical self healing effect from complete discharge of residual currents in board or cache. I'm going to try bring life back to it today. and try the Imac boot commands just for fun (?). I may have lacked the patience needed when doing CUDA, programmers resets, so I will approach with a more zen like mind set this time. Do you think I should re-type my original question in lower case, to get more responces ??....Thank you, All, And Thank you, Allen Jones, for the first responce.

Mac Pro and Boot Camp Woes

I had installed the retail version of leopard yesterday... Which i might add that I enjoyed thoroughly! However, this morning I had a hankering to play some Windows based games. So I went ahead and used boot camp.... Everything seemed to start off swimmingly with repartioning my drive. (Also took heed on keeping the new partition as FAT32 and not NTFS) Got to the point where Windows was copying files necessary for setup and finished. Rebooted my computer to begin setup and of course the cd was still in the drive so I got the infamous "Press any key to boot from CD" so i waited and received the msg "DISK ERROR" my system was completely locked up. So i held the power button in for 5 seconds to shut off the computer and tried restarting it. Now all i get is no video signal and the steady flashing light on the front of the Mac Pro (fans and drives are powering up). I've tried the following to resolve the issue (all resulting in the same black screen):
1) Held down "C" and booted up with my leopard install disc in the drive
2) Held down the option button to specify the boot device
3) Removed internal battery and held the power button on for 5 seconds to clear
4) Resetting the PRAM with command, option, p, and r keys pressed
5) Tried a different monitor (off another working computer)
6) Held down the shift key while booting up
No success! Like i said before i hear the drives spinning and fans humming just fine. Does anyone have any suggestions?

With a Mac Pro, and with a new OS... I would have advised to create your Windows partition on another disk drive and not on your boot drive.
I would also then pull either or both OS X drives (assuming you kept Tiger on another drive somewhere).
Microsoft would like to see customers move to the NTFS, it is a better file system, use FAT for when you need to share files, or use MacDrive7 even. Took heed not to use NTFS? don't understand. I have to use it of course (Vista) and I have one small 100GB FAT volume. Now most of my files are on NTFS (readable from OS X side if needed).
Did Windows update or never got that far (there should be a lot of updates, patches, etc) and at some point you would need your Leo DVD to install the Apple BootCamp patches, drivers, and services.
I prefer using the SMC Reset button - not PRAM reset.
Probably another X1900 issue?

Bootvar and boot command

Similar Messages

Maybe you are looking for