27 Aralık 2017 Çarşamba

Nexus Loader Mistake, License Problem

Nexus sw

http://www.dslreports.com/faq/15836

If for some reason a Nexus 3000 switch is stuck on loader prompt, then reviving process is in order. Similar to Catalyst lines, Nexus models comprise of three components in regards of reviving. One is the kickstart image, two is the main image, and three is the license file. You also need cables (straight-trough patch cable and console cable) and TFTP server in order to handle the reviving process.

The concept of having kickstart and main images are similar to legacy Cisco equipments (i.e. switches, routers), which the kickstart image is the basic boot image and main image is the actual image. In planning of reviving, you must have the following

* Both kickstart and main images
* Both kickstart and main images are stable and are of the same version

An example is a Nexus 3048 model with n3000-uk9-kickstart.5.0.3.U2.1.bin as the kickstart image and a n3000-uk9.5.0.3.U2.1.bin as the main image.

Steps to Revive

Phase 1: TFTP boot

1. Verify that you have the following in working order

* Kickstart image
* Main image
* TFTP server
* Straight-through patch cable
* Console access
* Bootflash (the flash memory hardware which resides inside the switch)

2. Ensure the kickstart and main images are stored in TFTP server and set the TFTP server to use the directory or folder which the three files are located.

3. Connect the switch's MGMT port (by the power supply) to the network where the TFTP server resides

4. Configure the switch's IP reachability to be able to communicate with the TFTP server. Following is illustration

* Enter the switch MGMT port's local IP address and subnet mask
1
loader> set ip 172.16.1.2 255.255.255.0

* Depending on your network, you may need to define default gateway
1
loader> set gw 172.16.1.1


5. Boot the kickstart image file from the TFTP server
1
loader> boot tftp://[ENTER TFTP SERVER IP ADDRESS HERE]/[ENTER KICKSTART IMAGE FIL E NAME HERE]


6. Assuming the TFTP boot is successful, the switch will then have a switch(boot)# prompt

Phase 2: Local boot

1. Issue dir bootflash: command to show the content of bootflash. If the bootflash is empty, then you need to copy the three files (kickstart image, main image, and license file) over the TFTP server. 

2. You may need to format the bootflash in case of corrupted condition. This corrupted condition is identified by the result of dir bootflash: command where showing no files but the number in bytes used and bytes total don't match. 


Note:
A bootflash format also means erasing entire content of the bootflash, including existing configuration, NX-OS images, and license file. Only to format when you are sure it is necessary.


When (and only when) there is discrepancy between the number in bytes used and total while the bootflash is empty, the following is to show how format to the bootflash.
1
2
switch(boot)# init system check-filesytem
switch(boot)# init system


3. Assuming that you don't see proper two image files (kickstart and main images), you need to copy the files over the TFTP server. Following is an illustration.

* Enter the switch MGMT port's local IP address and subnet mask
1
2
3
switch(boot)# config t
switch(boot)(config)# interface mgmt0
switch(boot)(config-mgmt0)# ip address 172.16.1.2 255.255.255.0

* Depending on your network, you may need to define default gateway
1
switch(boot)(config-mgmt0)# ip default-gateway 172.16.1.1

* Complete the port configuration
1
2
switch(boot)(config-mgmt0)# no shutdown
switch(boot)(config-mgmt0)# end

* Copy over the two image files (kickstart image and main image)
1
2
switch(boot)# copy tftp://[ENTER TFTP SERVER IP ADDRESS HERE]/[ENTER KICKSTART IMAGE  FILE NAME HERE] bootflash:/[ENTER KICKSTART IMAGE FILE NAME HERE]
switch(boot)# copy tftp://[ENTER TFTP SERVER IP ADDRESS HERE]/[ENTER MAIN IMAGE FILE NAME  HERE] bootflash:/[ENTER MAIN IMAGE FILE NAME HERE]


4. Verify that both images are in the bootflash
1
switch(boot)#dir bootflash:


5. See if the switch is able to boot up using the main image
1
switch(boot)#load bootflash:/[ENTER MAIN IMAGE FILE NAME HERE]


6. Assuming the boot is successful, you may see something like this
1
2
3
4
Uncompressing system image: bootflash:/system-image1
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Would you like to enter the initial configuration mode? (yes/no):


7. It is suggested that you enter y and default value, just to get some basic switch configuration.

8. Once the switch is configured, verify the running-config content of the last lines where the kickstart and main image file names are. 
1
switch#show running-config


9. If you don't see the kickstart and main image file names as part of the running-config, you need to add them.
1
2
3
4
5
switch#conf t
switch(config)#boot kickstart bootflash:/[ENTER KICKSTART IMAGE FILE NAME HERE]
switch(config)#boot system bootflash:/[ENTER MAIN IMAGE FILE NAME HERE]
switch(config)#end
switch#copy running-config startup-config


10. Reload the switch to ensure that the switch is able to boot up normally
1
switch#reload


Phase 3: License Installation

It is always suggested that you backup the kickstart image, main image, and license file in case of corrupted bootflash. If for some reason you don't have license file, you need to retrieve the file from either Cisco directly or through Cisco's partner. Here is Cisco link of further info.






License Problem

You can this output for clear all license

clear license scope

Hiç yorum yok:

Yorum Gönder