Host Power-On issue in Oracle T4-1 server from ILOM prompt : Solved

It is the first time i am facing such an issue with Oracle T-series servers. Starting from T1000, i have worked on different T-series SPARC machines like T2000, T3-1, T3-2, T4-1.... and they are all like my pets. It is something more than a normal pleasure that i feel when i work on  T-series and M-series SPARC servers. Unfortunate that M-series servers are no more into market except its support and that too, EOSL is almost reached

While working on these servers, I came to know that  if any small hardware issue is there, ILOM prompt doesn't allow the host to run the POST itself and it will stay in the same prompt.

There is an easy way to solve this issue which i have already done and got a positive output. Its just like "Cheating the server". Everything is mentioned in detail below with the commands and  outputs

When you try to start the Server, the issue appears like the below mentioned


-> start /SYS
Are you sure you want to start /SYS (y/n)? y
start: System faults or hardware configuration prevents power on.

What you need to do is:

1) Go to the Fault management shell to use the fmadm utility, so that we can find if any hardware issues are 

    there

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

*********************************************************************************

2) You can see the hardware issues after entering the command fmadm faulty and its the same that you  can         

     see from run level3

faultmgmtsp> fmadm faulty

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

Time                UUID                                 msgid          Severity

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

2012-09-26/07:24:59 dc873a7b-f661-ca2f-ae23-f59753bff70c SPT-8000-DH    Critical

Fault class : fault.chassis.voltage.fail

FRU         : /SYS/MB

              (Part Number: 7015924)

              (Serial Number: 465769T+1220BW09L3)

Description : A chassis voltage supply is operating outside of the

              allowable range.

Response    : The system will be powered off.  The chassis-wide service

              required LED will be illuminated.

Impact      : The system is not usable until repaired.  ILOM will not allow

              the system to be powered on until repaired.

Action      : The administrator should review the ILOM event log for

              additional information pertaining to this diagnosis.  Please

              refer to the Details section of the Knowledge Article for

              additional information.

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

Time                UUID                                 msgid          Severity

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

2012-10-03/04:47:56 47f0af46-19ce-c28d-ae6e-a01e19522e79 SPT-8000-5X    Major

Fault class : fault.chassis.env.power.loss

FRU         : /SYS/PS0

              (Part Number: 300-2235)

              (Serial Number: B70386)

Description : A power supply AC input voltage failure has occurred.

Response    : The service-required LED on the affected power supply and

              chassis will be illuminated.

Impact      : Server will be powered down when there are insufficient

              operational power supplies.

Action      : The administrator should review the ILOM event log for

              additional information pertaining to this diagnosis.  Please

              refer to the Details section of the Knowledge Article for

              additional information.

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

Time                UUID                                 msgid          Severity

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

2012-07-17/10:03:18 01877670-70dc-667e-928b-c13be3cac7da SPT-8000-MJ    Critical

Fault class : fault.chassis.power.fail

FRU         : /SYS/PS1

              (Part Number: 300-2235)

              (Serial Number: B70387)

Description : A Power Supply has failed and is not providing power to the

              server.

Response    : The service required LED on the chassis and on the affected

              Power Supply may be illuminated.

Impact      : Server will be powered down when there are insufficient

              operational power supplies

Action      : The administrator should review the ILOM event log for

              additional information pertaining to this diagnosis.  Please

              refer to the Details section of the Knowledge Article for

              additional information.

faultmgmtsp>

*********************************************************************************

3) After getting the outputs, please note the faulty FRU's and set the property "clear_fault_action=true" for 

    all these faulty ones going back to the ILOM prompt

faultmgmtsp> exit

-> set /SYS/MB clear_fault_action=true

Are you sure you want to clear /SYS/MB (y/n)? y

Set 'clear_fault_action' to 'true'

-> set /SYS/PS0 clear_fault_action=true

Are you sure you want to clear /SYS/PS0 (y/n)? y

Set 'clear_fault_action' to 'true'

-> set /SYS/PS1 clear_fault_action=true

Are you sure you want to clear /SYS/PS1 (y/n)? y

Set 'clear_fault_action' to 'true'

*********************************************************************************

4) Once this property is set to true, we need to go back to fault management shell and repair the FRU's using 

     the below mentioned command

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm repair /SYS/MB

faultmgmtsp> fmadm repair /SYS/PS0

faultmgmtsp> fmadm repair /SYS/PS1

*********************************************************************************

5) Check for any more faults are there in the server

faultmgmtsp> fmadm faulty

faultmgmtsp>

faultmgmtsp> exit

*********************************************************************************

6) Try startin the System, you can find the error is resolved and the server is up and running

-> start /SYS

Are you sure you want to start /SYS (y/n)? y

Starting /SYS

-> start /HOST/console

Are you sure you want to start /HOST/console (y/n)? y

Serial console started.  To stop, type #.

[CPU 0:0:0] NOTICE:  Initializing TOD: 2012/10/03 05:44:10

[CPU 0:0:0] NOTICE:  Loaded ASR status DB data. Ver. 3.

[CPU 0:0:0] NOTICE:  Initializing TPM with:

                        tpm_enable = false

                        tpm_activate = false

                        tpm_forceclear = false

[CPU 0:0:0] NOTICE:  TPM found: Ver 1.2, Rev 1.2, SpecLevel 2, errataRev 0, VendorId 'IFX'

[CPU 0:0:0] NOTICE:  TPM initialized successfully. Current state is: disabled

[CPU 0:0:0] NOTICE:  Serial#:     000000000000002a.015948c07cda22a6

[CPU 0:0:0] NOTICE:  Version:     003e003012030607

[CPU 0:0:0] NOTICE:  T4 Revision: 1.2

..............................................................

bash-3.2# prtdiag -v |more

System Configuration:  Oracle Corporation  sun4v SPARC T4-1

*********************************************************************************

That's it.. Very simple....huh.... :P

Lun Allocation from VMAX Storage

Today i got a chance to allocate some storage luns from VMAX Symmetrix storage Array to a Solaris SPARC host. VMAX storage systems are the best Enterprise level storages and the most popular flagships products of EMC. These Storage Systems replaced the DMX arrays which once ruled the world of storage, another old EMC product. They are fast, reliable and gives a better performance

Allocating Luns from VMAX has a different method and its not like that in DMX. Here comes something new called Port-group, storage-group, initiator-group and a masking view

Initiator Group : Its a group which consists of
                                Host HBA wwn                                                                                                      
Port Group : Its a group which consists of  
                                front end ports of the array
Storage Group : Its a group which consists of all the luns that need to be assigned to                         host
Masking view : Its a view created with a port-group, Initiator group and storage group
            When we want to allocate luns to host, we create a masking view for it..
        Entire host-storage communication takes place through this masking view

Below i have mentioned on creation and deletion of Port Group,Storage Group, Initiator Group & Masking view.

*********************************************************************************


INITIATOR GROUP CREATION
***************************
The initiator group name i am going to create is ig_libg162 which consists of 2 HBA wwn no.


1) Check if the host WWN no. is visible in the Symmetrix at the ports that is zoned from the
    switch end. Here i have zoned it to ports 7e:1 and 8g:1

 bash-3.2# symaccess list logins -dirport 7e:1 -sid 016

Symmetrix ID            : 000194901016

Director Identification : FA-7E
Director Port           : 1

                                                            User-generated                      Logged On
Identifier                    Type          Node Name               Port Name               FCID   In     Fabric
----------------         -----          --------------------------------- ------ ------ ------
50000972081a3519  Fibre          NULL                       NULL                    6f1b00   No     Yes
50000972c00fe19d   Fibre          NULL                       NULL                    6e0600   No     Yes
2100001b320f5448   Fibre          NULL                      NULL                     612a13 Yes    Yes
210000e08b9472a0   Fibre        210000e08b9472a0 210000e08b9472a0 6d0500  Yes    Yes
2101001b322f5448   Fibre          NULL                      NULL                     612813 Yes    Yes
210100e08bb472a0   Fibre         NULL                       NULL                     6d0400 Yes    Yes
21fd006069e21a14    Fibre          NULL                      NULL                     fffc6e     No     Yes

*************************************************************

2) Select the particular WWN no. required and create the initiator Groups with the command given
    below. Check if the initiator group is created and the required wwn no. got added or not.


bash-3.2# symaccess -sid 016 create -name ig_libj162 -type initiator -wwn 210000e08b9472a0
bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID          : 000194901016

Initiator Group Name  : ig_libj162
Last updated at       : 02:11:07 PM on Fri Aug 31,2012

   Host Initiators
     {
       WWN  : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]
     }

   Masking View Names
     {
       None
     }

   Parent Initiator Groups
     {
       None
     }

***************************************************
3) Add the next wwn no. of the host using the command given below and check if it got added or
    not.



bash-3.2# symaccess -sid 016 -name ig_libj162 -type initiator -wwn  210100e08bb472a0 add
bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID          : 000194901016

Initiator Group Name  : ig_libj162
Last updated at       : 02:13:12 PM on Fri Aug 31,2012

   Host Initiators
     {
       WWN  : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]
       WWN  : 210100e08bb472a0 [alias: 210100e08bb472a0/210100e08bb472a0]
     }

   Masking View Names
     {
       None
     }

   Parent Initiator Groups
     {
       None
     }
*********************************************************************************
DELETING INITIATOR GROUP 
*****************************
We should first remove the HBA wwn no. first one by one and then we should delete the entire Initiator Group


bash-3.2# symaccess -sid 016 -name ig_libj162 -wwn  210000e08b9472a0 remove -type initiator

bash-3.2# symaccess -sid 016 show ig_libj162 -type initiator

Symmetrix ID          : 000194901016

Initiator Group Name  : ig_libj162
Last updated at       : 01:11:40 PM on Fri Aug 31,2012

   Host Initiators
     {
       None
     }

   Masking View Names
     {
       None
     }

   Parent Initiator Groups
     {
       None
     }

bash-3.2# symaccess -sid 016 delete -name ig_libj162 -type initiator

Delete Initiator group 'ig_libj162' (y/[n])? y

*********************************************************************************

CREATING PORT GROUP
************************
Here i am going to create a port group with Symmetrix Front End ports 7e:1 and 8g:1

1) first check which all ports are used and what all are the port names given

bash-3.2# symcfg -sid 016 list -fa all

Symmetrix ID: 000194901016

           S Y M M E T R I X    F I B R E   D I R E C T O R S

    Dir         Port        WWN                 ACLX     Volume Set   Pnt to Pnt
                                                            Enabled   Addressing

    FA-7E   0    50000972C00FE118   Yes           No               Yes
    FA-7E   1    50000972C00FE119   Yes           No               Yes
    FA-8E   0    50000972C00FE11C  Yes           No                Yes
    FA-8E   1    50000972C00FE11D  Yes           No                Yes
    FA-7F   0    50000972C00FE158   Yes           No                Yes
    FA-7F   1    50000972C00FE159   Yes           No                Yes
    FA-8F   0    50000972C00FE15C  Yes           No                Yes
    FA-8F   1    50000972C00FE15D  Yes           No                Yes
    FA-8G   0    50000972C00FE19C  Yes          No                Yes
    FA-8G   1    50000972C00FE19D  Yes          No               Yes

******************************************
2) Create port group using the command mentioned below and check if the port got added or not.

bash-3.2# symaccess -sid 016 create -name pg_7e1_8g1 -type port -dirport 7e:1
bash-3.2# symaccess list -sid 016 -type port

Symmetrix ID          : 000194901016


Port Group Name
--------------------------------
pg_7e0_8e0
pg_7e1_8g1

bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID          : 000194901016

Port Group Name       : pg_7e1_8g1
Last updated at       : 02:40:21 PM on Fri Aug 31,2012

   Director Identification
     {
       FA-7E:1
     }

   Masking View Names
     {
       None
     }




********************************************
3) Add the required ports to this port group depending upon the reliability u need using the
    below command.

bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 8g:1 add
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID          : 000194901016

Port Group Name       : pg_7e1_8g1
Last updated at       : 02:44:02 PM on Fri Aug 31,2012

   Director Identification
     {
       FA-7E:1
       FA-8G:1
     }

   Masking View Names
     {
       None
     }

*********************************************************************************

 DELETING PORT GROUP 

************************

We should first remove the front end ports one by one and then we should delete the entire Port Group.


bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 7E:1 remove
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID          : 000194901016

Port Group Name       : pg_7e1_8g1
Last updated at       : 02:45:19 PM on Fri Aug 31,2012

   Director Identification
     {
       FA-8G:1
     }

   Masking View Names
     {
       None
     }

bash-3.2# symaccess -sid 016 -name pg_7e1_8g1 -type port -dirport 8g:1 remove
bash-3.2# symaccess -sid 016 show pg_7e1_8g1 -type port

Symmetrix ID          : 000194901016

Port Group Name       : pg_7e1_8g1
Last updated at       : 02:47:12 PM on Fri Aug 31,2012

   Director Identification
     {
       None
     }

   Masking View Names
     {
       None
     }
bash-3.2# symaccess -sid 016 delete -name pg_7e1_8g1 -type port -nop

Delete Port group 'pg_7e1_8g1' (y/[n])? y

*********************************************************************************

CREATING STORAGE GROUP

****************************

Here i am creating a storage group with 25 Luns of 5 Gb size each.

1) Add a storage group using a device as shown with the below command and check if the devices 

    are visible in the storage group

bash-3.2# symaccess -sid 016 create -name sg_libj162 -type storage dev 0087

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID                : 000194901016

Storage Group Name          : sg_libj162

Last updated at             : 02:54:22 PM on Fri Aug 31,2012

   Number of Storage Groups : 0

   Storage Group Names      : None

   Devices                  : 0087

   Masking View Names

     {

       None

     }

***************************************

2) After this u can keep on adding devices to the storage group depending on the requirement using the below command

bash-3.2# symaccess -sid 016 add devs 0088:009F -name sg_libj162 -type storage

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID                : 000194901016

Storage Group Name          : sg_libj162

Last updated at             : 02:57:37 PM on Fri Aug 31,2012

   Number of Storage Groups : 0

   Storage Group Names      : None

   Devices                  : 0087:009F

   Masking View Names

     {

       None

     }

*********************************************************************************

DELETING STORAGE GROUP

****************************

In Similar way like what we did for  port group and initiator group, remove the luns first from the storage group and then delete the storage group

1) bash-3.2# symaccess -sid 016 remove devs 0087:009F -name sg_libj162 -type storage

bash-3.2# symaccess -sid 016 show sg_libj162 -type storage

Symmetrix ID                : 000194901016

Storage Group Name          : sg_libj162

Last updated at             : 02:59:55 PM on Fri Aug 31,2012

   Number of Storage Groups : 0

   Storage Group Names      : None

   Devices                  : None

   Masking View Names

     {

       None

     }

****************************************************************

2) Delete the storage group as shown with the below command

bash-3.2# symaccess -sid 016 delete -name sg_libj162 -type storage

Delete Storage group 'sg_libj162' (y/[n])? y

*********************************************************************************

CREATING MASKING VIEW 

**************************

1) Create the masking view with the proper storage group in which all the luns are added, with 

the port group where all the ports are added and with the initiato group where all the HBA wwn 

no.s of the hosts are added. as shown in the below command

bash-3.2# symaccess -sid 016 create view -name mv_libj162 -storgrp sg_libj162 -portgrp 

pg_7e1_8g1 -initgrp ig_libj162

bash-3.2# symaccess -sid 016 show view mv_libj162

Symmetrix ID                : 000194901016

Masking View Name           : mv_libj162

Last updated at             : 03:05:17 PM on Fri Aug 31,2012

Initiator Group Name        : ig_libj162

   Host Initiators

     {

       WWN  : 210000e08b9472a0 [alias: 210000e08b9472a0/210000e08b9472a0]

       WWN  : 210100e08bb472a0 [alias: 210100e08bb472a0/210100e08bb472a0]

     }

Port Group Name             : pg_7e1_8g1

   Director Identification

     {

       FA-7E:1

       FA-8G:1

     }

Storage Group Name          : sg_libj162

   Number of Storage Groups : 0

   Storage Group Names      : None

Sym                                     Host

Dev     Dir:P  Physical Device Name     Lun   Attr  Cap(MB)

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

0087    07E:1  Not Visible                 0          20481

            08G:1  Not Visible                 0

0088    07E:1  Not Visible                 1          20481

            08G:1  Not Visible                 1

0089    07E:1  Not Visible                 2          20481

            08G:1  Not Visible                 2

008A    07E:1  Not Visible                 3          20481

            08G:1  Not Visible                 3

008B    07E:1  Not Visible                 4          20481

            08G:1  Not Visible                 4

008C    07E:1  Not Visible                 5          20481

            08G:1  Not Visible                 5

008D    07E:1  Not Visible                 6          20481

             08G:1  Not Visible                 6

008E    07E:1  Not Visible                 7          20481

            08G:1  Not Visible                 7

008F    07E:1  Not Visible                 8          20481

           08G:1  Not Visible                 8

0090    07E:1  Not Visible                 9          20481

           08G:1  Not Visible                 9

0091    07E:1  Not Visible                 a          20481

           08G:1  Not Visible                 a

0092    07E:1  Not Visible                 b          20481

           08G:1  Not Visible                 b

0093    07E:1  Not Visible                 c          20481

           08G:1  Not Visible                 c

0094    07E:1  Not Visible                 d          20481

           08G:1  Not Visible                 d

0095    07E:1  Not Visible                 e          20481

           08G:1  Not Visible                 e

0096    07E:1  Not Visible                 f          20481

           08G:1  Not Visible                 f

0097    07E:1  Not Visible                10          20481

            08G:1  Not Visible                10

0098    07E:1  Not Visible                11          20481

            08G:1  Not Visible                11

0099    07E:1  Not Visible                12          20481

           08G:1  Not Visible                12

009A    07E:1  Not Visible                13          20481

           08G:1  Not Visible                13

009B    07E:1  Not Visible                14          20481

           08G:1  Not Visible                14

009C    07E:1  Not Visible                15          20481

           08G:1  Not Visible                15

009D    07E:1  Not Visible                16          20481

            08G:1  Not Visible                16

009E    07E:1  Not Visible                17          20481

           08G:1  Not Visible                17

009F    07E:1  Not Visible                18          20481

            08G:1  Not Visible                18

                                                    -------

Total Capacity                                       512025

*********************************************************************************

DELETING MASKING VIEW

**************************

bash-3.2# symaccess -sid 016 delete view -name mv_libj162

Delete masking view 'mv_libj162' from symmetrix 000194901016 (y/[n])? y

solutions for Unix,backup and storage: C4 TAPE LIBRARY CONFIGURATION ON SOLARIS WITH NETW...

solutions for Unix,backup and storage: C4 TAPE LIBRARY CONFIGURATION ON SOLARIS WITH NETW...:  9 Today i have configured a C4 tape Library to a solaris server. We are running backup using networker 7.2. The C4 tape library has got 38...

Adding SWAP space and DUMP space to a ZFS installe...

solutions for Unix,backup and storage: Adding SWAP space and DUMP space to a ZFS installe...: Its very easy to add swap space in ZFS installed machine and the concept is same as that of UFS. In UFS we make use of commands 'mkfile' an...

Crack Admin Password for Cisco Nexus 5020 Switch

Recently i changed my employer. I was so desperate to explore the world of Storage, Where i was working on only Hitachi VSP and low end emc storages and thank god now i got a job under the World Leader of Storage.
The very first  task given to me was to configure a SAN fabric out of

1)Cisco Nexus 5020
2)Cisco MDS 9509 &
3)Brocade DCX-B switches.Where my nexus switch is gonna be the director switch.

I was stuck up with the nexus SAN switch where i didn't knew the admin password. Below i have explained in a step by step way on how to break the admin password for the same.

1)Power on the Cisco Nexus switch and observe the output in console. If we know the boot procedure we can see that first it will run the BIOS, then it will load the kickstart image from the boot loader prompt, Once the kickstart image verification is done without error then from the switch(boot) prompt the switch will boot to the init level 3 loading the system image, where we can do the normal switch operations. The important images required for the switch to boot is
                             a) Kickstart image &
                             b) System Image which resides in the bootflash: directory of the switch.

But  we should not allow the switch to boot to the run level 3 nor load the System image.Before that we should break it and bring the switch to switch (boot) prompt.Below is the output that shows while a nexus switch boots up.





Booting kickstart image: bootflash:/n5000-uk9-kickstart.4.1.3.N2.1.bin....
.......................................................................Image ve
rification OK


Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
Starting Nexus5020 POST...
  Executing Mod 1 1 SEEPROM Test......done
  Executing Mod 1 1 GigE Port Test.......done
  Executing Mod 1 1 Inband GigE Test.....done
  Executing Mod 1 1 NVRAM Test....done
  Executing Mod 1 1 PCIE Test..............................done
  Mod 1 1 Post Completed Successfully
  Executing Mod 1 2 SEEPROM Test....done
  Mod 1 2 Post Completed Successfully
POST is completed
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
Checking all filesystems..... done.
.
Loading system software
Uncompressing system image: bootflash:/n5000-uk9.4.1.3.N2.1.bin


Loading plugin 0: core_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
Loading plugin 1: eth_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/1, tar_log = /isan/plugin_extract_log/1
plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
INIT: Entering runlevel: 3
Exporting directories for NFS kernel daemon...done.
Starting NFS kernel daemon:rpc.nfsd.
rpc.mountddone.


Setting envvar: SYSMGR_SERVICE_NAME to muxif_service
Set envvar SYSMGR_SERVICE_NAME to muxif_service
/isan/bin/muxif_config: argc:2
muxif_init....vacl: ret: 0
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
2012 Mar 13 11:29:11 Securitty %$ VDC-1 %$ %KERN-2-SYSTEM_MSG: Starting kernel... - kernel
Executing Port Power On Tests........................Done


2012 Mar 13 11:31:39 Securitty %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online


Nexus 5000 Switch
admin login :




*****************************************************************************

2)To break the boot sequence once the POST is completed either press Cntrol and ']' (Cntrl + ]) or Control and Sihft alongwith 'b'.
This depends on the models of switch you are working on. In the Latest Nexus switch  should work and that worked for me.Cntrl + ]


Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
Starting Nexus5020 POST...
  Executing Mod 1 1 SEEPROM Test......done
  Executing Mod 1 1 GigE Port Test.......done
  Executing Mod 1 1 Inband GigE Test.....done
  Executing Mod 1 1 NVRAM Test....done
  Executing Mod 1 1 PCIE Test..............................done
  Mod 1 1 Post Completed Successfully
  Executing Mod 1 2 SEEPROM Test....done
  Mod 1 2 Post Completed Successfully
POST is completed
^]Creating /callhome..                             (Here by giving 'Cntrl + ]' i am breaking the boot sequence)
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
Checking all filesystems....r. done.
.
INIT: Sending processes the KILL signal kernel daemon...don
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
switch(boot)# 



*********************************************************************************

3) Once you reach the sitch(boot) prompt, there are only few commands that can be performed here. Here itself you have to change the admin password with command. admin-password.



Switch(boot)# config t
Enter configuration commands, one per line.  End with CNTL/Z.
switch(boot)(config)# admin-password password123there 
Password is not strong enough: Password should contain characters from at least three of the following classes: lower case letters, upper case letters, digits and special characters.
switch(boot)(config)# admin-password P@ssword123
switch(boot)(config)# exit

*****************************************************************************

4) Once the password is rest then we have to load the system image from this prompt using the load command.



switch(boot)# dir bootflash:
bootflash:license_SSI14190KEY_15.lic
bootflash:lost+found
bootflash:mts.log
bootflash:n5000-uk9-kickstart.4.1.3.N2.1.bin
bootflash:n5000-uk9.4.1.3.N2.1.bin
bootflash:vdc_2
bootflash:vdc_3
bootflash:vdc_4
switch(boot)# dir bootflash:
        497  Aug 11 2010 21:20:20  license_SSI14190KEY_15.lic
      16384  Aug 11 2010 21:07:16  lost+found/
       1418  Mar 13 2012 10:43:18  mts.log
   21680640  Aug 11 2010 21:12:03  n5000-uk9-kickstart.4.1.3.N2.1.bin
  136255825  Aug 11 2010 21:12:37  n5000-uk9.4.1.3.N2.1.bin
       4096  Jan 01 2005 00:02:30  vdc_2/
       4096  Jan 01 2005 00:02:30  vdc_3/
       4096  Jan 01 2005 00:02:30  vdc_4/


           Usage for bootflash: filesystem
                  219824128 bytes total used
                  663527424 bytes free
                  883351552 bytes available
switch(boot)# load bootflash:n5000-uk9.4.1.3.N2.1.bin



INIT: Unexporting directories for NFS kernel daemon...done.
Stopping NFS kernel daemon: rpc.mountd rpc.nfsddone.
Unexporting directories for NFS kernel daemon...
done.
Stopping portmap daemon: portmap.
Stopping kernel log daemon: klogd.
Sending all processes the TERM signal... done.
Sending all processes the KILL signal... done.
Unmounting remote filesystems... done.
Deactivating swap...done.
Unmounting local filesystems...done.
mount: you must specify the filesystem type
Starting reboot command: reboot
Rebooting...
Restarting system.




Booting kickstart image: bootflash:/n5000-uk9-kickstart.4.1.3.N2.1.bin....
.......................................................................Image ve
rification OK


Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
Starting Nexus5020 POST...
  Executing Mod 1 1 SEEPROM Test......done
  Executing Mod 1 1 GigE Port Test.......done
  Executing Mod 1 1 Inband GigE Test.....done
  Executing Mod 1 1 NVRAM Test....done
  Executing Mod 1 1 PCIE Test..............................done
  Mod 1 1 Post Completed Successfully
  Executing Mod 1 2 SEEPROM Test....done
  Mod 1 2 Post Completed Successfully
POST is completed
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
Checking all filesystems..... done.
.
Loading system software
Uncompressing system image: bootflash:/n5000-uk9.4.1.3.N2.1.bin


Loading plugin 0: core_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
Loading plugin 1: eth_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/1, tar_log = /isan/plugin_extract_log/1
plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
INIT: Entering runlevel: 3
Exporting directories for NFS kernel daemon...done.
Starting NFS kernel daemon:rpc.nfsd.
rpc.mountddone.


Setting envvar: SYSMGR_SERVICE_NAME to muxif_service
Set envvar SYSMGR_SERVICE_NAME to muxif_service
/isan/bin/muxif_config: argc:2
muxif_init....vacl: ret: 0
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
2012 Mar 13 11:29:11 Securitty %$ VDC-1 %$ %KERN-2-SYSTEM_MSG: Starting kernel... - kernel
Executing Port Power On Tests........................Done


2012 Mar 13 11:31:39 Securitty %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

**********************************************************************************

5) Now the switch is booted in run level 3 and is up.You can give the admin login and password and login to the switch.

login as: admin

Using keyboard-interactive authentication.

Password:

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under

license. Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or the GNU

Lesser General Public License (LGPL) Version 2.1. A copy of each

such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://www.opensource.org/licenses/lgpl-2.1.php

libh250#

**********************************************************************

New articles on restoring san switch from loader prompt, Upgrading images of Cisco SANswitches and configuring fabric using ISL are all yet to published in my next few updates here. 

solutions for Unix,backup and storage: How to Break Admin Password for Cisco Nexus 9000 S...

solutions for Unix,backup and storage: How to Break Admin Password for Cisco Nexus 9000 S...: Recently i changed my employer. I was so desperate to explore the world of Storage, Where i was working on only Hitachi VSP and low end emc ...

solutions for Unix,backup and storage: C4 TAPE LIBRARY CONFIGURATION ON SOLARIS WITH NETW...

solutions for Unix,backup and storage: C4 TAPE LIBRARY CONFIGURATION ON SOLARIS WITH NETW...: 9 Today i have configured a C4 tape Library to a solaris server. We are running backup using networker 7.2. The C4 tape library has got 38...

solutions for solaris,backup and storage: X-Manager Configuration in Solaris 10

solutions for solaris,backup and storage: X-Manager Configuration in Solaris 10: I was asked to install oracle client. but then i found it difficult as i was not able to login to server through X-Manager.The server was Or...

solutions for solaris,backup and storage: Hardware RAID configuration in T3-1 Oracle server

solutions for solaris,backup and storage: Hardware RAID configuration in T3-1 Oracle server: Today I got a chance to configure Hardware RAID in T3-1 oracle server. T3-1 servers are recently launched Chip Multithread servers (CMT) fr...

solutions for solaris,backup and storage: solutions for solaris,backup and storage: Hardware...

solutions for solaris,backup and storage: solutions for solaris,backup and storage: Hardware...: solutions for solaris,backup and storage: Hardware RAID configuration in T3-1 Oracle server : "Today I got a chance to configure Hardware RA...

solutions for solaris,backup and storage: DYNAMIC RECONFIGURATION IN E20k

solutions for solaris,backup and storage: DYNAMIC RECONFIGURATION IN E20k: Today I learnt a very interesting thing,that i got a chance for Dynamic Reconfiguration in E20k.For these many days i have heard about board...

solutions for solaris,backup and storage: solutions for solaris,backup and storage: DYNAMIC ...

solutions for solaris,backup and storage: solutions for solaris,backup and storage: DYNAMIC ...: solutions for solaris,backup and storage: DYNAMIC RECONFIGURATION IN E20k : "Today I learnt a very interesting thing,that i got a chance for...

solutions for solaris,backup and storage: Adding SWAP space and DUMP space to a ZFS installe...

solutions for solaris,backup and storage: Adding SWAP space and DUMP space to a ZFS installe...: Its very easy to add swap space in ZFS installed machine and the concept is same as that of UFS. In UFS we make use of commands 'mkfile' an...

solutions for solaris,backup and storage: Creating Alternate Boot Enviornment for ZFS

solutions for solaris,backup and storage: Creating Alternate Boot Enviornment for ZFS: Today i learned how to create an alternate boot enviornment for a ZFS installed solaris SPARC machine. I follwed the below steps: ...

solutions for solaris,backup and storage: Creating Alternate Boot Enviornment for ZFS

solutions for solaris,backup and storage: Creating Alternate Boot Enviornment for ZFS: Today i learned how to create an alternate boot enviornment for a ZFS installed solaris SPARC machine. I follwed the below steps: ...

solutions for solaris,backup and storage: Breaking ROOT Password in ZFS Solaris SPARC machin...

solutions for solaris,backup and storage: Breaking ROOT Password in ZFS Solaris SPARC machin...: Today i learnd how to reset the root password for a ZFS installed OS on a sparc machine.The concept is same as in UFS except for the com...

solutions for solaris,backup and storage: Adding SWAP space and DUMP space to a ZFS installe...

solutions for solaris,backup and storage: Adding SWAP space and DUMP space to a ZFS installe...: Its very easy to add swap space in ZFS installed machine and the concept is same as that of UFS. In UFS we make use of commands 'mkfile' an...