cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

ASR9000/XR Understanding Turboboot and initial System bring up

65007
Views
60
Helpful
154
Comments



Introduction

This document provides an understanding of what Turboboot is and how to bring up a system running IOS-XR from scratch

There are two ways to upgrade the system:

  • One is to install add and activate the new XR software version. At a minimum this would require that mini.pie file
  • The second way is by performing a turboboot, fresh install, by booting the mini.vm file from rommon

This executable mini.vm file needs to be transferred via TFTP (on the RSP2) or can be loaded from the external USB port or TFTP (on the RSP440 and CRS-PRP). On the 9001 the USB ability is added in rommon 2.03 (5.1.1 release version).

No other media or protocols are possible to be used for a turboboot other then the ones specified above. Ex FTP is not allowed

File System overview

XR devices have multiple medias for storage and they all have their individual purpose.

 
VolumeRSP2RSP440TridentTyphoon
disk0:Embedded USBSSD (SATA)  
disk0a:Embedded USBSSD (SATA)  
disk1:Embedded USBSSD (SATA)  
disk1a:Embedded USBSSD (SATA)  
harddisk:Harddisk (SAS)Embedded USB  
harddiska:Harddisk (SAS)Embedded USB  
harddiskb:Harddisk (SAS)Embedded USB  
compactflash:Compactflash1External USB1  
lcdisk0:  Embedded USBEmbedded USB
lcdisk0a:  Embedded USBEmbedded USB
bootflash:NOR Flash NOR FlashNOR Flash
configflash:NOR Flash   
nvram:NVSRAMNVSRAM  
Kernel dumpHarddisk (SAS)SSD (SATA)TFTPbootflash:
 1. Removable   
     
Access (Mount) Points (in /dev)
VolumeRSP2RSP440TridentTyphoon
disk0:disk00t77hd0t77qsm to active rspqsm to active rsp
disk0a:disk00t78hd0t78qsm to active rspqsm to active rsp
disk1:disk10t77hd1t77qsm to active rspqsm to active rsp
disk1a:disk10t78hd1t78qsm to active rspqsm to active rsp
harddisk:hd0t79usb00t77qsm to active rspqsm to active rsp
harddiska:hd0t77usb00t78qsm to active rspqsm to active rsp
harddiskb:hd0t78usb00t11  
compactflash:disk20t6,11,121usb10t6,11,121  
lcdisk0:  lcdisk00t77lcdisk00t77
lcdisk0a:  lcdisk00t78lcdisk00t78
bootflash:fs0p1 fs0p1fs0p1
configflash:fs1p1   
nvram:nvramnvram  
Kernel dumphd0t80hd0t80 or hd1t802 fs0p2
 1. Any one2. Either one  
     
Usage
VolumeRSP2RSP440TridentTyphoon
disk0:IOS-XR Packages, ConfigsIOS-XR Packages, Configs  
disk0a:sysmgr_debugsysmgr_debug  
disk1:IOS-XR Packages (if Mirrored)IOS-XR Packages (if Mirrored)  
disk1a:wdsysmon_debugwdsysmon_debug  
harddisk:Crash files, logsCrash files, logs  
harddiska:NP logs, crash filesNP logs, crash files  
harddiskb:    
compactflash:File CopyFile Copy  
lcdisk0:  Kernel dump filesKernel dump files
lcdisk0a:    
bootflash:MBI Images   
configflash:OBFL   
nvram:ConfigsConfigs  
Kernel dumpRaw kernel dumpsRaw kernel dumps Raw kernel dumps
     
Filesystems
VolumeRSP2RSP440TridentTyphoon
disk0:QNX4QNX4  
disk0a:QNX4QNX4  
disk1:QNX4QNX4  
disk1a:QNX4QNX4  
harddisk:QNX4QNX4  
harddiska:QNX4QNX4  
harddiskb:QNX4FAT  
compactflash:FAT1FAT1,2  
lcdisk0:  QNX4QNX4
lcdisk0a:  QNX4QNX4
bootflash:FFSv3 FFSv3FFSv3
configflash:FFSv3   
nvram:CiscoCisco  
Kernel dumpRawRawFileRaw
 1. FAT F/S only2. Flash Media only  
     
Approximate Parition Size (minimum)
VolumeRSP2RSP440TridentTyphoon
disk0:1.6GB11.0GB  
disk0a:0.4GB2.2GB  
disk1:1.6GB11.0GB  
disk1a:0.4GB2.2GB  
harddisk:35GB3.1/6.2GB  
harddiska:8GB0.4/0.8GB  
harddiskb:8GB0.4/0.8GB  
compactflash:1GB1-32GB  
lcdisk0:  1.6GB1.6GB
lcdisk0a:  0.4GB0.4GB
bootflash:44MB 56MB56MB
configflash:28MB   
nvram:220K500K  
Kernel dump21GB500MB x 2 24MB
 

Note that unlike many IOS devices, nvram is NOT used for the configuration storage. Configurations are stored in a database on the boot disk (often disk0). Typically only rommon variables and license info are stored in nvram.

Summary steps for using turboboot

Because a  turboboot can erase configuration, SSH keys, and other items such as  licenses the following should be done to check and backup any files

1. Run a cfs check in admin & non-admin mode

2. Copy active licenses and SNMP files to tftp server

3. Copy running config to a tftp-server or laptop

4. Capture "show ipv4 int brief" output to a text file

5. Capture "show ipv6 int brief | i Up/Up" output to a text file

6.  Offline. Edit the saved RSP config - add "no shutdown" for all physical  interfaces that are up/up from the above IPv4 & IPv6 interface  captures and save cfg changes. Note that it is not necessary to “no  shut” sub-interfaces, only the main physical interface.

7. Connect a laptop console cable to the RSP in RSP0 slot and enable a log file to monitor and capture the RSP bootup logs.

8 . Turn the power supplies on to power up the asr9k system. (approx. 7-12 minutes)

9.  After the LED's indicate IOS-XR on the LC's, and ACTV or STBY on the  RSP’s, log in via the console of the RSP that is ACTV and run some  preliminary checks to check system stability.

NOTE: The default root-system username and password on the RSP440 are root/root

(if root/root does not work also try cisco/cisco, or admin/admin or viking/viking)

 

10. Verify the ASR9K IOS XR version

11. Run a cfs check in admin & non-admin mode

12. (Optional) Install add & commit any missing SW packages (pies) or required SMU’s

13. Upgrade FPD in admin mode

14. Reload any nodes that had FPD upgrades

15.  Configure the Mgmt ethernet interface with an IP address to reach tftp  server & load and commit the saved RSP config from tftp server or  laptop

a) or log into the console and cut & paste a saved cfg from laptop

b) or copy saved cfg from laptop to usb, then insert usb into RSP440 and copy and commit cfg

c) copy licenses and snmp files back to the RSP’s

16. (Optional) create and generate new crypto keys if required.

Steps to Turboboot

 

As mentioned Turbobooting means that you load the "VM" (virtual machine) XR base OS image.

Turboboot is started from Rommon and is essentially the same as putting a disk with the desired OS in your laptop, reboot the machine to boot from CDROM, and installing the base OS.

Before the Turboboot process starts, you can instruct the system to wipe all files from the system and start clean or install the image to be turbobooted along side with any existing releases currently found on the disk. (see Set the Turboboot variables on the RSP)

Turbobooting may be required if you want to sweep clean your system, or we also had some issues in XR4.2.0 with the RSP2 whereby the upgrade pie could not be loaded. A turboboot was required in that case also.

Some or all of these procedures below are needed.

The command "set" gives you an overview of all the rommon environment variables currently set to their values.

Clear the ROM Monitor environmental variables on all RSPs

unset BOOT
unset TFTP_FILE
sync

the command *unset* clears the variable value from rommon.

the command *sync *saves or writes the newly set and unset variables to persistent memory so they are saved cross reloads and power cycles.

Clear disk mirroring variables

unset BOOT_DEV_SEQ_OPER
unset MIRROR_ENABLE
sync

By default, the two internal USB partitions (disk0 and disk1) are mirrored to each other, if you break the mirror, turboboot will only affect the disk

that you are turbobooting target to and not the other one (nice if you want to fall back).

Disable the CPU watchdog

priv
diswd <- Disable the CPU watchdog

If you omit this step and the TFTP download for the turboboot mini-vm image takes longer than 30 minutes due to network delays etc, then the RSP might reset and you'll have to start over. Disabling this watchdog makes sure the system is not going to reload during the transfer of the image in rommon.

Define the network and IP settings on the mgmt interface

IP_ADDRESS=ip_address
IP_SUBNET_MASK=mask
DEFAULT_GATEWAY=ip_address

Set TFTP environment variables

TFTP_RETRY_COUNT=4

sets the number of retries to contact the tftp server

TFTP_TIMEOUT=6000

sets the TFTP timeout for the transfer, you may need to set this larger to prevent abort during xfer if there are network delays

TFTP_CHECKSUM=1

whether checksum on the transfer is needed, this is adviceable in case the image gets corrupted during transfer.

TFTP_SERVER=server_ip_addr

the server address can also be specified in the boot statement, or fixed in the rommon variable.

TFTP_MGMT_INTF=0

which of the 2 mgmt interfaces you want to use, either 0 or 1 with 0 being the default.

TFTP_BLKSIZE=1400

Setting a larger TFTP block size is recommended to pack larger packets and transfer the VM image quicker. Note that for CRS this variable is TFTP_BLOCK_SIZE.

Set the Turboboot variable on the RSP

TURBOBOOT=on, {boot-device},[format | clean],[nodisablebreak]

on tells us to install add and install activate the packages when we boot from the VM image.

boot-device is which device we want to use to install the OS, typically disk0

format tells us to replace the OS completely except for the admin configuration

clean tells us to replace the OS completely, but other files such as the admin or exec configuration are saved

nodisablebreak allows us to terminate the turboboot via a break signal. The default is to ignore breaks

Example:

TURBOBOOT=on,disk0,format
sync

This will instruct the system to do a turboboot with disk0 as the selected boot device and to use the format option. The format key is optional.

Currently today we only support targeted install to disk0 but this will change likely in XR4.3.1 whereby you can use disk1 as install target.

NOTE: a recent tac case showed that the command for turboboot failed on the ASR9001.

Supposedly this was made to work by omitting the colon after disk0:

Suggesting to try the disk0 (without colon) if the command with colon fails.

 

ASR9K/CRS-PRP Additional Information

 

In CRS the format option works with FAT16 but not FAT32 or QNX4 so a new variable must also be used.

In ASR9K the format and clean options do work but in order to erase the exec configuration, admin configuration, and every other file this additional variable must be used.

 

For these scenarios the following must be set.

TURBOBOOT=on,disk0

MEDIA_FORMAT=disk0:,QNX4

 

Note: If the format or clean options are set in turboboot or confreg 0x2142 is set when also having the MEDIA_FORMAT variable set then when prompted for a new username/password we will be unable to write this to the disk. To fix this go back to rommon and properly set the variables.

 

Boot the remote mini.vm file

(Works only with the VM image, not the TAR file or mini.pie)

rommon> boot tftp://server/directory/filename

During the boot process the image is copied first on to the memory(RAM) and is installed from memory(RAM). Once it is insalled from memory, it will copy the image back on to disk0: and reload the device. Wait till you get the message "SYSTEM CONFIGURATION COMPLETED"

Output of show install active when in memory,

RP/0/RSP0/CPU0:ios#sh install active
<SNIP>
Active Packages:
mem:asr9k-mini-p-4.2.0

Output of show install active after image copied on to disk0:,

RP/0/RSP0/CPU0:ios#sh install active
<SNIP>
Active Packages:
disk0:asr9k-mini-p-4.2.0

The system will also self unset the TURBOBOOT rommon variable.

Restore disk mirroring

To restore disk mirroring, use the mirror command in the global configuration mode. For more information on the mirror command, see the "Boot Commands on Cisco IOS XR Software" module in Cisco ASR 9000 Series Aggregation Services Router System Management Command Reference.

How to boot from the external USB port

The RSP-440 (and 9001 with rommon 2.03) can boot from the USB front panel port. Instead of using "boot tftp:// or boot disk0:/" you need to use a different command, mediaboot.

The command is:

rommon> mediaboot usb:\release_mini.vm

In later revisions of the rommon, the mediaboot has been superseded to boot usb:/<file>

so make sure you try them both.

 

NOTE:

Some newer rommon versions on the 9001 want to use the boot usb:/ directive. (see Q&A/comment section below this article).

It is also seen in rommon versions post 2.04 that the usb is referred to as disk1 in which case you can use: boot disk1:/...

To find out the mapping of the usb disk use the rommon "dev" command to see all filesystem devices.

 

On the CRS-PRP use boot disk2:hfr-mini-px.vm<image>

CRS does not use the mediaboot command.

How to update the FPD's

FPD upgrade for all ASR9K devices using FPD.

a) Enter admin mode via the admin command, and capture the output of the current firmware versions using CLI show hw-module fpd location all. save this output to a text file. Notice any LC that has a “yes” in the Upg/Dng?  column. This indicates the FPD should be upgraded or downgraded to match the current FPD version.

b) From admin mode upgrade FPD using the CLI: upgrade hw-module fpd location r/s/m

or if all locations require FPD upgrade (suggested) use CLI:* upgrade hw-module fpd location all *

Disk Space occupied for each image

Simplest way is to use the ksh df utility.

Install a release and packages and run df:

# df /disk0:

/dev/disk00t77           3813344    733477   3079867      20%  /dev/disk0:/   

Divide the highlighted number by 2000. That gives the approximate size in MB. 366MB in this case.

Repeat for any other releases we should be interested in.

If you do an upgrade, gather the df output before and after upgrade and compute the difference in df output.

Related Information

Xander Thuijs, CCIE #6775

Principal Engineer ASR9000

Sam Milstead,

Customer Support Engineer TAC XR

Comments

Thank you, just to be clear, is it the 'asr9k-mini-px-4.3.4' file below or not? 

RP/0/RP0/CPU0:#sh install active summary 
Thu May 28 11:55:09.011 EDT
Default Profile:
  SDRs:
    Owner
  Active Packages:
    disk0:asr9k-mini-px-4.3.4
    disk0:asr9k-fpd-px-4.3.4
    disk0:asr9k-k9sec-px-4.3.4
    disk0:asr9k-9000v-nV-px-4.3.4
    disk0:asr9k-doc-px-4.3.4
    disk0:asr9k-mcast-px-4.3.4
    disk0:asr9k-mgbl-px-4.3.4
    disk0:asr9k-mpls-px-4.3.4
    disk0:asr9k-px-4.3.4.CSCug75299-1.0.0
    disk0:asr9k-px-4.3.4.CSCui94441-1.0.0
    disk0:asr9k-px-4.3.4.CSCul39674-1.0.0
Cisco Employee

No, your output is that of the decompressed directory.

 

Packages come in the form of a .pie file and a new system image comes in the form of a .vm. For .pie files we use install add to decompress the files needed onto disk which is shown in your output. As well with a .vm when you turboboot the files are decompressed onto disk, the .vm is needed and slightly larger than the mini.pie as it needs to perform some additional functions.

 

Thanks,

Sam

So Sam if I look into CCO, I only see these two files for download for 4.3.4

Cisco ASR 9000 IOS XR Software 
ASR9K-iosxr-px-4.3.4.tar

Cisco ASR 9000 IOS XR Software 3DES 
ASR9K-iosxr-px-k9-4.3.4.tar

Si, just that I understand correctly, the .vm Turbo image is included in either one of the above files?

And where can I locate the specific Turbo image file on a production box?

 

Cisco Employee

Correct, the .vm file for turboboot is in both .tar files. The only difference in the two is the k9sec package.

 

You should never find a .vm file on the router itself, as turboboot is done via USB or TFTP and we do not copy the .vm itself onto the router, just into memory.

 

Sam

Sam excellent. One last question.

Is the turbo boot image 'needed'?

We're installing brand new ASR9922s, what's the need for the turbo boot? Is it required or it's just a last resport if something happens?

Cisco Employee

Brand new routers from the factory should come with images already on them, this is selected when doing the PO. After this if you need to upgrade or downgrade the .pie files can be used http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html

 

Turboboot is needed when there is no image or some corruption has occurred.

 

Sam

Beginner

Hi Xander

How about turbobooting a standby RSP? We did the active RSP as you described but when we entered the boot tftp command on the standby RSP, we get the following error message:

This node has been booted with the wrong image type. Composite has already been used to boot dSC at [chars]. Please boot this node with an MBI image.

What did we do wrong?

The software version we are trying to install is the 4.2.3 on a new ASR 9010 V2 chassis.

Cisco Employee

hi tom,

technically there is no need to turboboot the standby RSP, because when it is inserted, the active will sync to the standby.

obviously the active and standby cannot run different versions.

if you want to turboboot the standby you will likely need to "keep it down" via rommon, priv, diswd (which disables the watchdog) because the active will likely try to kick the stnadby to bring it up so it can sync.

 

cheers!

xander

Hi

 

I can confirm that is not possible to boot asr9001 with any other TFTP_BLKSIZE then 1024.

I have tried 6 or 7 different TFTP servers for windows 7 and more then 10 different TFTP_BLKSIZE from 64 to 2048.

 

This only work with TFTP_BLKSIZE=1024 

I finaly used tftpd64 ( free ).

I have made TURBOOT for 5.1.3 version.

 

It's really big problem, when you have SPARE box replacement after faulty.

Any comments from Cisco to this ?

 

 

Cisco Employee

hmm this is new(s) to me! obviously that should not happen. do you have any details on the failure reason for using any other value then 1024? I mean is it halting, or not transfering at all or timing out?

xander

Hi

 

Transfer was halting in most cases.

I also had problem that file was not transfering at all.

System advice to change value to 1400 but it not helped.

 

example log :

Performing tftpdnld
TFTP: Enabling cache

Mgt LAN 0 interface is selected
dtsec_init_hw: configuring DTSEC (port 8) for: 1GB, Full Duplex

tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 100.
Receiving /asr9k-mini-px.vm-5.1.3 from 1.1.1.1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
tftp_service_timeout: ACK RETRY! Block=46944, retry=18.
tftp_service_timeout: ACK RETRY! Block=46944, retry=17.
tftp_service_timeout: ACK RETRY! Block=46944, retry=16.
tftp_service_timeout: ACK RETRY! Block=46944, retry=15.
tftp_service_timeout: ACK RETRY! Block=46944, retry=14.
tftp_service_timeout: ACK RETRY! Block=46944, retry=13.
tftp_service_timeout: ACK RETRY! Block=46944, retry=12.
tftp_service_timeout: ACK RETRY! Block=46944, retry=11.
tftp_service_timeout: ACK RETRY! Block=46944, retry=10. [CTRL-C]
TFTP: Operation aborted.

TFTP: Disabling cache

 

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

Performing tftpdnld
TFTP: Enabling cache

Mgt LAN 0 interface is selected
dtsec_init_hw: configuring DTSEC (port 8) for: 1GB, Full Duplex

tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
tftp_service_timeout: CONNECT RETRY! retry=18.
tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
tftp_service_timeout: CONNECT RETRY! retry=17.
tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
tftp_service_timeout: CONNECT RETRY! retry=16.
tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
tftp_service_timeout: CONNECT RETRY! retry=15.
tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.
tftp_service_timeout: CONNECT RETRY! retry=14.
tftp_process_packet: received OACK.
tftp_process_packet: Change blksize to 1400.
ip_sanity_check: ip fragment, rejected.
ip_sanity_check: ip fragment, rejected.

Cisco Employee

yikes, there is a hop/device or something that is fragmenting packets and since rommon doesnt have reassembly capability, this "high" value of 1400 block size is resulting in that problem. in order to select higher block sizes we need to ensure the MTU of the interface can accommodate that since we cannot have tftp fragments.

the other issue of the halting I have seen before which is caused by certain TFTP servers that have a hock on a number of blocks they can transmit it has seemed and since the XR images are quite large we will need a large number of blocks.

The number of blocks used is a factor of the blocksize inherently also together with the image size.

So yeah as you noticed it is a fine art selecting that block size that reduces the number of blocks to be transmitted, but preventing that fragmentation which cannot occur.

I have had good success with the tftpd32 windows application and redhat embedded tftp server also I see little issues with.

xander

Thank for response

 

I had my windows 7 laptop directly connected to asr9001 without any device between.

 

Cisco Employee

I stopped using windows after XP, so I dont know the win7 specific setting there, but at least in XP the default MTU (for whatever reason) in teh registry was set to 1300, which could explain the fragmentation of the block size when set to 1400.

There was a nifty tool (drTCP) that could be used to adjust the mtu tuning of the nic so that you can bypass that problem.

Believe that windows set to that low mtu value to prevent fragmentation for dialup/vpn stuff (pptp), but since TFTP block size config is a "hard setting" and not negotiated like tcp's mss the router in this case may ask for that large block size which is what the windows will honor, but resulting in frag because of that mtu registry setting...

cheers!

xander

Beginner

HI,

    when i was loading the VM file it is getting copied on RAM and installing but  it is not starting.

I am getting the below error

"Process 4098 (startmini) terminated SIGSEGV code=1 fltno=11 ip=4000de88 ref=c901d0d0"

 

rommon B2 > unset BOOT
unset: "BOOT" does not exist
rommon B3 > unset TFTP_FILE
unset: "TFTP_FILE" does not exist
rommon B4 > unset BOOT_DEV_SEQ_OPER
rommon B5 > unset MIRROR_ENABLE
unset: "MIRROR_ENABLE" does not exist
rommon B6 > priv
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon B7 > diswd
Watchdog Disabled
rommon B8 > TURBOBOOT=on,disk0,format
rommon B9 > sync

 

rommon B10 > boot disk1:/asr9k-mini-px.vm-5.1.2

 Boot Status 16
Located asr9k-mini-px.vm-5.1.2, start cluster is 13725
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
program load complete, entry point: 0x20261c, size: 0x18bda336

 Boot Status 17
Config = SMP, Running = SMP
Board type: 0x00100401
Card Capability = 0x00000000
BSP: Board type : ASR9K-RSP-I
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
czip:326:mount=/dev/shmem, image=0, remove=0x1
czip: strings=ffff23f8, as=ffff28a0, num=0x340
czip: 356:start_addr=60185000, in_size=0x15e452da

Process 4098 (startmini) terminated SIGSEGV code=1 fltno=11 ip=4000de88 ref=c901d0d0     

 

 

 

 

 

 

Content for Community-Ad