giovedì 8 novembre 2012

Memory Limits on Microsoft OS


Physical Memory Limits: Windows 8

The following table specifies the limits on physical memory for Windows 8.
VersionLimit on X86Limit on X64
Windows 8 Enterprise
4 GB
512 GB
Windows 8 Professional
4 GB
512 GB
Windows 8
4 GB
128 GB

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.
VersionLimit on X64
Windows Server 2012 Datacenter
4 TB
Windows Server 2012 Standard
4 TB
Windows Server 2012 Essentials
64 GB
Windows Server 2012 Foundation
32 GB
Windows Storage Server 2012 Workgroup
32 GB
Windows Storage Server 2012 Standard
4 TB
Hyper-V Server 2012
4 TB

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.
VersionLimit on X86Limit on X64
Windows 7 Ultimate
4 GB
192 GB
Windows 7 Enterprise
4 GB
192 GB
Windows 7 Professional
4 GB
192 GB
Windows 7 Home Premium
4 GB
16 GB
Windows 7 Home Basic
4 GB
8 GB
Windows 7 Starter
2 GB
N/A

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.
VersionLimit on X64Limit on IA64
Windows Server 2008 R2 Datacenter
2 TB
Windows Server 2008 R2 Enterprise
2 TB
Windows Server 2008 R2 for Itanium-Based Systems
2 TB
Windows Server 2008 R2 Foundation
8 GB
Windows Server 2008 R2 Standard
32 GB
Windows HPC Server 2008 R2
128 GB
Windows Web Server 2008 R2
32 GB

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2008 Datacenter
64 GB
1 TB
Windows Server 2008 Enterprise
64 GB
1 TB
Windows Server 2008 HPC Edition
128 GB
Windows Server 2008 Standard
4 GB
32 GB
Windows Server 2008 for Itanium-Based Systems
2 TB
Windows Small Business Server 2008
4 GB
32 GB
Windows Web Server 2008
4 GB
32 GB

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.
VersionLimit on X86Limit on X64
Windows Vista Ultimate
4 GB
128 GB
Windows Vista Enterprise
4 GB
128 GB
Windows Vista Business
4 GB
128 GB
Windows Vista Home Premium
4 GB
16 GB
Windows Vista Home Basic
4 GB
8 GB
Windows Vista Starter
1 GB

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit on X86Limit on X64
Windows Server 2003 R2 Datacenter Edition
64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Enterprise Edition
64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Standard Edition
4 GB
32 GB

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition
64 GB
(16 GB with 4GT)
1 TB
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition
64 GB
(16 GB with 4GT)
1 TB
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition
4 GB
32 GB

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition
64 GB
(16 GB with 4GT)
X64 1 TB
1 TB
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition
64 GB
(16 GB with 4GT)
X64 1 TB
1 TB
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition
4 GB
32 GB

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit on X86Limit on IA64
Windows Server 2003, Datacenter Edition
64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Enterprise Edition
64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Standard Edition
4 GB
Windows Server 2003, Web Edition
2 GB
Windows Small Business Server 2003
4 GB
Windows Compute Cluster Server 2003
32 GB
Windows Storage Server 2003, Enterprise Edition
8 GB
Windows Storage Server 2003
4 GB

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.
VersionLimit on X86Limit on X64Limit on IA64
Windows XP
4 GB
128 GB
128 GB (not supported)
Windows XP Starter Edition
512 MB
N/A
N/A

Physical Memory Limits: Windows Embedded

The following table specifies the limits on physical memory for Windows Embedded.
VersionLimit on X86Limit on X64
Windows XP Embedded
4 GB
Windows Embedded Standard 2009
4 GB
Windows Embedded Standard 7
4 GB
192 GB

mercoledì 10 ottobre 2012

Vmware Guest mount USB external Disk


USB can be used by Guest OS by editing the settings of a Virtual Machine and then choosing the "Hardware" TAB Once you are at the HARDWARE Tab you can click "ADD" and select a USB Controller.
Once you have added a USB Controller you then repeat the same process, except this tieme add a USB Device instead of a controller.

You will see any attached USB devices in a list to choose from.

Once added you then need to open the console of the Virtual Machine, and Mount it to the USB connector. (the little USB icon at the top of the Console Window).

Login the windows system and it should find the disk automaticaly.

lunedì 8 ottobre 2012

Linux partitioning with fdisk

I start fdisk from the shell prompt:
# fdisk /dev/hdb 
which indicates that I am using the second drive on my IDE controller. (See Section 2.1.) When I print the (empty) partition table, I just get configuration information.
Command (m for help): p

Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders
Units = cylinders of 4032 * 512 bytes
I knew that I had a 1.2Gb drive, but now I really know: 64 * 63 * 512 * 621 = 1281982464 bytes. I decide to reserve 128Mb of that space for swap, leaving 1153982464. If I use one of my primary partitions for swap, that means I have three left for ext2 partitions. Divided equally, that makes for 384Mb per partition. Now I get to work.
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-621, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-621, default 621): +384M
Next, I set up the partition I want to use for swap:
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (197-621, default 197):
Using default value 197
Last cylinder or +size or +sizeM or +sizeK (197-621, default 621): +128M
Now the partition table looks like this:
   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1             1       196    395104   83  Linux
/dev/hdb2           197       262    133056   83  Linux
I set up the remaining two partitions the same way I did the first. Finally, I make the first partition bootable:
Command (m for help): a
Partition number (1-4): 1
And I make the second partition of type swap:
Command (m for help): t
Partition number (1-4): 2
Hex code (type L to list codes): 82
Changed system type of partition 2 to 82 (Linux swap)      
Command (m for help): p
The end result:
Disk /dev/hdb: 64 heads, 63 sectors, 621 cylinders
Units = cylinders of 4032 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1       196    395104+  83  Linux
/dev/hdb2           197       262    133056   82  Linux swap
/dev/hdb3           263       458    395136   83  Linux
/dev/hdb4           459       621    328608   83  Linux          
Finally, I issue the write command (w) to write the table on the disk.
to format disk:

mkfs.ext3 (for ext3 file system)
mkfs.ext4 (for ext4 file system)
mkfs.swap (for swap file system)



martedì 25 settembre 2012

VMware Import Export OVA files


About OVF (Open Virtualization Format)
It is an open standard used across different virtualization platform. An OVF virtual machine consists of a directory containing virtual machine files and a file describing them.
About OVA (Open Virtualization Appliance)
It is a single compressed file containing the contents of an OVF directory.
VMware OVF tool
VMware OVF tool is a command line utility that supports import and export of OVF packages to and from vSphere infrastructure.


ExportC:\Program Files\VMware\VMware OVF Tool>ovftool.exe "vi://username:password@vCenterIP:443/DataCenter_Name/vm/Demo-W7-VM" "C:\VM-Backup\Demo-W7-VM.ova"
ImportC:\Program Files\VMware\VMware OVF Tool>ovftool.exe "--datastore=datastore1" "--network=VM-Network" "C:\VM-Backup\Demo-W7-VM.ova" "vi://username:password@vCenterIP/DataCenter_Name/host/Cluster_Name/hostIP"

lunedì 9 luglio 2012

VMware Manually Assigning a MAC Address to Virtual machine Cisco CUOM


Operations Manager supports VMware ESX 3.5, ESXi 4.x, and ESXi 5.0. Operations Manager musthave the same system resources available to it, inside the virtualization environment that it has for astandard (nonvirtual) installation.While determining the performance of Operations Manager in your virtual setup, you should be awarethat the VMware instance will use some system resources that would normally be available to OperationsManager in a standard installation. Additional requirements for running Operations Manager in avirtualization environment might vary with your environment and system load.Operations Manager can be installed on a virtual machine with dynamic MAC address for evaluation.However, you must configure the virtual machine with a static MAC address to purchase the permanentlicense for Operations Manager.

The static MAC address is required because licensing uses node-locking technology. The license file can
only be used with the static MAC address that you supply.
Note The static MAC address must be within the following range: 00:50:56:00:00:00 to 00:50:56:3F:FF:FF.
To set up a static MAC address:
Step 1 Power down the virtual machine.
Step 2 In the Inventory panel, select the virtual machine.
Step 3 Click the Summary tab and then click Edit Settings.
Step 4 In the Hardware list, select Network Adapter.
Step 5 For MAC address, select Manual.
Step 6 Change the current MAC address of the virtual machine to a static MAC address in the following range:
00:50:56:00:00:00 to 00:50:56:3F:FF:FF.
Step 7 Click OK.

Enable Automatic Start Up for Guest OS on VMware ESX


This one had me tearing my hair out. We needed to enable auto startup on some of our Virtual Machines on the VMware ESX server, but I couldn’t for the life of me work out how. After a stupid amount of Googling around, turning up nothing, I actually RTFM! Page 177-178 had the answers ;)
Here’s how to do it:
Launch the Virtual Infrastructure Client. If you don’t have it, just http:// to your VMware ESX host and grab it from the front page.
Go to the Configuration tab of your ESX Server, then click on Virtual Machine Startup/Shutdown.
By default (I’m pretty sure) automatic startup is disabled. To enable it, click on “Properties…” on the far upper right of the window.
You’ll now see this window:
Check/Tick “Allow virtual machines to start and stop automatically with the system”.
Now, this is the bit where I nearly cried…
You know you want to “enable” your Guest OSes to automatically boot, but how? I tried clicking and dragging, right clicking for a context menu to enable “Automatic start up” and gave up.
Turns out, you need to click on the Guest OS you’d like to enable, and then click “Move Up” until it sits underneath the “Automatic startup” title. Argh!
I really hope this helps someone out! :)

lunedì 2 luglio 2012

Controllo bad blocks sul disco con linux

badblocks is a Linux utility to check for bad sectors on a disk drive (A bad sector is a sector on a computer's disk drive or flash memory that cannot be used due to permanent damage or an OS inability to successfully access it.). It creates a list of these sectors that can be used with other programs, like mkfs, so that they are not used in the future and thus do not cause corruption of data. It is part of the e2fsprogs project.

It can be a good idea to periodically check for bad blocks. This is done with the badblocks command. It outputs a list of the numbers of all bad blocks it can find. This list can be fed to fsck to be recorded in the filesystem data structures so that the operating system won’t try to use the bad blocks for storing data. The following example will show how this could be done.

From the terminal, type following command:

$ sudo badblocks -v /dev/hda1 > bad-blocks
The above command will generate the file bad-blocks in the current directory from where you are running this command.

Now, you can pass this file to the fsck command to record these bad blocks
$ sudo fsck -t ext3 -l bad-blocks /dev/hda1
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Check reference counts.
Pass 5: Checking group summary information.

/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****

/dev/hda1: 11/360 files, 63/1440 blocks
If badblocks reports a block that was already used, e2fsck will try to move the block to another place. If the block was really bad, not just marginal, the contents of the file may be corrupted.

Looks at badblocks man pages for more command line options.

venerdì 29 giugno 2012

Upgrade ios su cisco 6500


Step 1: Provide TCP/IP Connectivity to the L3 Module

The L3 module has the ability to receive new Cisco IOS images through the TFTP. To use TFTP with the image, you must ensure that the TFTP server (the computer that runs TFTP server software) can reach the L3 engine through TCP/IP. If you are able to ping the computer from the command-line interface (CLI) of the L3 module, you have successfully completed this step.
Setup of the L3 engine for IP connectivity is beyond the scope of this document.
To configure IP connectivity for each specific L3 module, refer to:

Step 2: Copy the Image into the L3 Module Through the TFTP

Verify Free Space on the Bootflash
At this point, you need to verify that you have enough space in the bootflash to copy the new image. If there is not enough room, you have to delete some files to make space. In some situations, if the image is very large, you must delete the current image in the bootflash. On the MSFC, this deletion can be made safely if you also have the boot image in the bootflash. You use the boot image if the main image is corrupt or not available.
Note: The main image is the full feature set Cisco IOS image, whereas the boot image is essentially a scaled-down version of the main image. The boot image has limited sub-IP functionality with the intent to provide TFTP capabilities.
To determine the amount of free space and whether there is a boot image in the bootflash, issue the dir [device:]command.
Example:
In this example, the bootflash has 1,265,440 bytes free, and there is a boot image present (c6msfc2-boot-mz.121-6.E1). The word "boot" in the file name indicates a boot image.
c-MSFC15# dir bootflash:

Directory of bootflash:/ 
    1  -rw-     1667488   Apr 20 2001 20:56:41 c6msfc2-boot-mz.121-6.E1
    2  -rw-    12269412   Feb 05 2002 18:08:32  c6msfc2-jsv-mz.121-8a.E2 

15204352 bytes total (1265440 bytes free)
Note: The Catalyst 4500/4000 4232-L3 module does not have boot image functionality. However, you are likely to find adequate space on the bootflash for the image. Also, as long as you do not reload the device, the module continues to function correctly. The module continues to work because the image is loaded into the DRAM upon boot and does not rely on the bootflash image once the system is up.
If you find that there is not enough space, you can delete the file. The delete [device:][file_name] command deletes the file.
Example:
c-MSFC15# delete bootflash:c6msfc2-jsv-mz.121-8a.E2 
Delete filename [c6msfc2-jsv-mz.121-8a.E2]? c6msfc2-jsv-mz.121-8a.E2
Delete bootflash:c6msfc2-jsv-mz.121-8a.E2? [confirm]y 
c-MSFC15#
The file is removed once it is deleted and squeezed.
Copy the Image into Bootflash
At this stage, you have IP connectivity and can ping between the computer that acts as a TFTP server and the L3 module. Now, copy the image into the bootflash. If you cannot ping between devices, see the Step 1: Provide TCP/IP Connectivity to the L3 Module section of this document. Step 1 provides appropriate links for IP connectivity.
At the enable prompt, issue this command to copy from the TFTP server to your bootflash:
c-MSFC15# copy tftp bootflash
You see a prompt with this information:
Address or name of remote host []? 172.16.84.119
Address or name of remote host is the IP address of the TFTP server. The ping test in Step 1: Provide TCP/IP Connectivity to the L3 Module confirms the IP.
Source filename []? c6msfc2-jsv-mz.121-8a.E5
Source filename is the image file name. The file must be in your TFTP directory path so that the TFTP server can locate the file.
Note: The file name must be spelled exactly the same, which includes any capitalization.
Destination filename [flash]? c6msfc2-jsv-mz.121-8a.E5
Destination filename is the file name of the image that you intend to save onto the bootflash. Use of the same file name as the source name ensures that, in the future, you can correctly identify the software features and version run.
If you do not have enough space in the bootflash, Cisco IOS Software asks if you want to delete the current image to make room for the new image.
The transfer can take some time, which depends on the speed of the connection and the size of the image. During the transfer, you see exclamation marks ("!" ) for good packets. The appearance of periods (".") indicates that the link has taken some hits. Investigate the problem afterward.
A successful TFTP transfer reports an OK, along with the number of bytes transferred. If you do not receive an OK, investigate IP connectivity and possible TFTP server issues.
Example:
c-MSFC15# copy tftp bootflash 
Address or name of remote host []? 172.16.84.119
Source filename []? c6msfc2-jsv-mz.121-8a.E5 
Destination filename [flash]? c6msfc2-jsv-mz.121-8a.E5 
Accessing tftp://172.16.84.119/c6msfc2-jsv-mz.121-8a.E5... 
Loading c6msfc2-jsv-mz.121-8a.E5 from 172.16.84.119 (via Vlan1): 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!--- Output suppressed. 
[OK - 12269412/24538112 bytes] 
12269412 bytes copied in 523.852 secs (23459 bytes/sec) 
c-MSFC15#
After you have successfully transferred the file, verify that the file is in the bootflash:
Issue the dir [device:] command to show files that are currently in the bootflash.
Example:
c-MSFC15# dir bootflash: 
Directory of bootflash:/ 
    1    -rw-    1667488            Apr 20 2001 20:56:41        c6msfc2-boot-mz.121-6.E1 
    2    -rw-    12269412            Feb 05 2002 18:08:32        c6msfc2-jsv-mz.121-8a.E5
Verify that the name and the file size are correct.

Step 3: Set Boot Statement

After you copy the image through TFTP, you must provide the L3 module with the name of the image to load upon boot.
Check Current Boot Statements
The image is now in the bootflash. You must set the L3 module to boot the new image. By default, the L3 module boots the first available image. (An absence of boot commands in the configuration enables the default.) There is a possibility that you have a previous boot statement defined.
There are two ways to determine the current boot parameter settings.
  • Method 1 is to issue the show config command:
    Example:
    c-MSFC15# show config 
    Building configuration... 
    
    Current configuration : 1625 bytes 
    ! 
    version 12.1 
    service timestamps debug datetime msec localtime 
    ! 
    hostname c-MSFC15 
    ! 
    boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4 
    boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1 
    ! 
    ip subnet-zero 
    ! 
    --More--
    Check to see if the configuration has any boot commands. The commands appear toward the top of the configuration.
  • Method 2 is to issue the show boot command:
    Example:
    c-MSFC15# show boot 
    BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E4,1 
    CONFIG_FILE variable = 
    BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1 
    Configuration register is 0x102
    Check to see if the boot statements appear under the parameter BOOT variable.
    If you have boot entries, you must remove them from the configuration. For more information on the removal of boot entries, see the Remove Previous Boot Statements section of this document.
Remove Previous Boot Statements
To remove the statements, enter into configuration terminal mode. From the configuration mode, you can negate any command with the issue of no in front of each boot statement.
This example illustrates the removal of a boot statement:
Example:
c-MSFC15# show config 
Building configuration... 

Current configuration : 1625 bytes 
! 
version 12.1 
service timestamps debug datetime msec localtime 
! 
hostname c-MSFC15 
! 
boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4
boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1 
! 
ip subnet-zero 
! 
--More--
At this point, you have the boot statement that you want to remove. The statement to remove is boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4.
c-MSFC15# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
c-MSFC15(config)# no boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E4
c-MSFC15(config)# ^Z 
c-MSFC15#
Verify that you have removed the command:
Example:
c-MSFC15# show config 
Building configuration... 

Current configuration : 1625 bytes 
! 
version 12.1 
service timestamps debug datetime msec localtime 
! 
hostname c-MSFC15 
! 
boot bootldr bootflash:c6msfc2-boot-mz.121-6.E1 

!--- Note: Now the boot statement no longer appears in the configuration. 
! 
ip subnet-zero 
! 
--More--
Once the commands are removed, you can issue the copy run start command or the write memory command to save the configuration to NVRAM.
Example:
c-MSFC15# write memory 
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11) 
Building configuration... 
c-MSFC15#
Set the New Boot Statement
You must add the boot statement to indicate which image the L3 module needs to load.
Issue this command to set the boot parameter:
  • boot system flash bootflash:[image_name]
    Note: In this command, image_name is the name of the new Cisco IOS image.
Example:
c-MSFC15# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
c-MSFC15(config)# boot system flash bootflash:c6msfc2-jsv-mz.121-8a.E5
c-MSFC15(config)# ^Z
c-MSFC15# write memory 
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11) 
Building configuration... 
c-MSFC15#
Be sure to verify that the config-register value is set to 0x2102 with the issue of the show boot command. If config-register is set to a different value, you can change it with the issue of this command in configuration mode:
  • config-register 0xvalue
Example:
c-MSFC15# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
c-MSFC15(config)# config-register 0x2102 
c-MSFC15(config)# ^Z
c-MSFC15# write memory
Verify the boot parameters with the issue of the show boot command:
c-MSFC15# show boot 
BOOT variable = bootflash:c6msfc2-jsv-mz.121-8a.E5,1 
CONFIG_FILE variable = 
BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-6.E1 
Configuration register is 0x102 (will be 0x2102 at next reload) 
c-MSFC15#
After you change the config-register, the change takes place at the next reload, as the example shows.

Step 4: Reload the L3 Module

For the L3 module to run the new Cisco IOS image, you must reload the module. Make sure that you have saved the configuration. Issue the copy run start command or the write memory to save the configuration.
Example:
c-MSFC15# write memory 
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11) 
Building configuration... 
c-MSFC15#
Issue the reload command to soft reset the L3 module, as this example shows:
Example:
c-MSFC15# reload 
Proceed with reload? [confirm] 
00:00:40: %SYS-5-RELOAD: Reload requested 
System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1) 
Copyright (c) 20 0 0 by cisco Systems, Inc. 
Cat6k-MSFC2 platform with 131072 Kbytes of main memory 
Self decompressing the image :
######################################################### [OK] 
%SYS-6-BOOT_MESSAGES: Messages above this line are from the boot loader. 
Self decompressing the image :
################################################################################### [OK] 
Restricted Rights Legend 
Use, duplication, or disclosure by the Government is 
subject to restrictions as set forth in subparagraph 
(c) of the Commercial Computer Software - Restricted 
Rights clause at FAR sec. 52.227-19 and subparagraph 
(c) (1) (ii) of the Rights in Technical Data and Computer 
Software clause at DFARS sec. 252.227-7013. 
cisco Systems, Inc. 
170 West Tasman Drive 
San Jose, California 95134-1706 
Cisco Internetwork Operating System Software 
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE 
SOFTWARE (fc2) 
TAC Support: http://www.cisco.com/tac 
Copyright (c) 1986-2001 by cisco Systems, Inc. 
Compiled Mon 22-Oct-01 21:51 by eaarmas 
Image text-base: 0x40008980, data-base: 0x418D2000 
cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory. 
Processor board ID SAD042106RN 
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache 
Last reset from power-on 
Bridging software. 
X.25 software, Version 3.0.0. 
SuperLAT software (copyright 1990 by Meridian Technology Corp). 
TN3270 Emulation software. 
509K bytes of non-volatile configuration memory. 
16384K bytes of Flash internal SIMM (Sector size 512K). 
Press RETURN to get started! 
00:00:02: Currently running ROMMON from S (Gold) region 
00:00:04: %SYS-5-CONFIG_I: Configured from memory by console 
00:00:04: %SYS-5-RESTART: System restarted -- 
Cisco Internetwork Operating System Software 
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY DEPLOYMENT RELEASE 
SOFTWARE (fc2) 
TAC Support: http://www.cisco.com/tac 
Copyright (c) 1986-2001 by cisco Systems, Inc. 
Compiled Mon 22-Oct-01 21:51 by eaarmas 
00:00:06: %SCP-5-ONLINE: Module online 
00:00:09: %LINK-3-UPDOWN: Interface Vlan1, changed state to up 
00:00:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up 
c-MSFC15>

Step 5: Verify the Upgrade

After the L3 module comes up, make sure that you run the new version of code. Issue the show version command to check.
Example:
c-MSFC15# show version 
Cisco Internetwork Operating System Software 
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(8a)E5, EARLY 
DEPLOYMENT RELEASE SOFTWARE (fc2) 

!--- Note: Now the MSFC runs the new software image. 
TAC Support: http://www.cisco.com/tac 
Copyright (c) 1986-2001 by cisco Systems, Inc. 
Compiled Mon 22-Oct-01 21:51 by eaarmas 
Image text-base: 0x40008980, data-base: 0x418D2000 
ROM: System Bootstrap, Version 12.1(2r)E, RELEASE SOFTWARE (fc1) 
BOOTFLASH: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(6)E1, EARLY DEPLOYMENT RELEASE 
SOFTWARE (fc1) 
c-MSFC15 uptime is 0 minutes 
System returned to ROM by power-on 
Running default software 
cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory. 
Processor board ID SAD042106RN 
R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache 
Last reset from power-on 
Bridging software. 
X.25 software, Version 3.0.0. 
SuperLAT software (copyright 1990 by Meridian Technology Corp). 
TN3270 Emulation software. 
4 Virtual Ethernet/IEEE 802.3 interface(s) 
509K bytes of non-volatile configuration memory. 
16384K bytes of Flash internal SIMM (Sector size 512K). 
Configuration register is 0x2102 
c-MSFC15#
Verify that the version (12.1(8a)E5) is correct and that the config-register is set (0x2102).
The upgrade is complete.
Note: If you have dual MSFCs, you must download the image onto the second MSFC bootflash: device. The image does not automatically download to the second MSFC. This requirement is also applies to config-sync mode and Single Router Mode (SRM). In config-sync mode and SRM, changes in the boot variables automatically propagate to the nondesignated or standby MSFC. To copy an image from bootflash to the bootflash of a nondesignated or standby MSFC, issue the copy bootflash:source_filename slavebootflash:target_filenamecommand.

Boot the MSFC with CatOS Software from Flash PC

When you run Catalyst OS (CatOS) software on the Supervisor Engine, you can choose to boot the MSFC from an image in the Supervisor Engine slot0 Flash PC Card slot. Your boot system statement refers to the Flash device as sup-slot0. Although there is support for such a boot process, avoid use of it. Use this boot process only as a temporary step, such as when you test an image. Be aware of Cisco bug ID CSCdr35304  ( registered customers only) .
You cannot issue commands such as the dir sup-slot0: command or the show sup-slot0: commands from the MSFC because the MSFC does not consider slot0 to be a local file system. If you specify sup-slot0 as the source of the operating system image, the switch transfers the file through TFTP across the internal switching bus between the sc0 interface on the Supervisor Engine and a special loopback IP address on the MSFC.
From the MSFC CLI, you can issue this command:
FIRE-MSFC1# copy tftp ?
  bootflash:      Copy to bootflash: file system
  ftp:            Copy to ftp: file system
  microcode:      Copy to microcode: file system
  null:           Copy to null: file system
  nvram:          Copy to nvram: file system
  rcp:            Copy to rcp: file system
  running-config  Update (merge with) current system configuration
  slavenvram:     Copy to slavenvram: file system
  startup-config  Copy to startup configuration
  sup-slot0:      Copy to sup-slot0: file system
  system:         Copy to system: file system
  tftp:           Copy to tftp: file system
The sup-slot0 device also appears in the show file systems command output:
FIRE-MSFC1# show file systems
    File Systems: 

         Size(b)     Free(b)      Type  Flags  Prefixes
         4395600           0    opaque     ro   microcode:
               -           -    opaque     rw   null:
               -           -    opaque     rw   system:
               -           -   network     rw   sup-slot0:
               -           -   network     rw   tftp:
          126968      124130     nvram     rw   nvram:
    *   15990784     2028888     flash     rw   bootflash:
               -           -   network     rw   rcp:
               -           -   network     rw   ftp:
               -           -     nvram     rw   slavenvram: