- Cisco Community
- Technology and Support
- Service Providers
- Service Providers Knowledge Base
- ASR9000/XR Understanding Turboboot and initial System bring up
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-14-2013 08:10 AM
- Introduction
- File System overview
- Summary steps for using turboboot
- Steps to Turboboot
- Clear the ROM Monitor environmental variables on all RSPs
- Clear disk mirroring variables
- Disable the CPU watchdog
- Define the network and IP settings on the mgmt interface
- Set TFTP environment variables
- Set the Turboboot variable on the RSP
- ASR9K/CRS-PRP Additional Information
- Boot the remote mini.vm file
- Restore disk mirroring
- How to boot from the external USB port
- How to update the FPD's
- Related Information
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.
| Volume | RSP2 | RSP440 | Trident | Typhoon |
| disk0: | Embedded USB | SSD (SATA) | ||
| disk0a: | Embedded USB | SSD (SATA) | ||
| disk1: | Embedded USB | SSD (SATA) | ||
| disk1a: | Embedded USB | SSD (SATA) | ||
| harddisk: | Harddisk (SAS) | Embedded USB | ||
| harddiska: | Harddisk (SAS) | Embedded USB | ||
| harddiskb: | Harddisk (SAS) | Embedded USB | ||
| compactflash: | Compactflash1 | External USB1 | ||
| lcdisk0: | Embedded USB | Embedded USB | ||
| lcdisk0a: | Embedded USB | Embedded USB | ||
| bootflash: | NOR Flash | NOR Flash | NOR Flash | |
| configflash: | NOR Flash | |||
| nvram: | NVSRAM | NVSRAM | ||
| Kernel dump | Harddisk (SAS) | SSD (SATA) | TFTP | bootflash: |
| 1. Removable | ||||
| Access (Mount) Points (in /dev) | ||||
| Volume | RSP2 | RSP440 | Trident | Typhoon |
| disk0: | disk00t77 | hd0t77 | qsm to active rsp | qsm to active rsp |
| disk0a: | disk00t78 | hd0t78 | qsm to active rsp | qsm to active rsp |
| disk1: | disk10t77 | hd1t77 | qsm to active rsp | qsm to active rsp |
| disk1a: | disk10t78 | hd1t78 | qsm to active rsp | qsm to active rsp |
| harddisk: | hd0t79 | usb00t77 | qsm to active rsp | qsm to active rsp |
| harddiska: | hd0t77 | usb00t78 | qsm to active rsp | qsm to active rsp |
| harddiskb: | hd0t78 | usb00t11 | ||
| compactflash: | disk20t6,11,121 | usb10t6,11,121 | ||
| lcdisk0: | lcdisk00t77 | lcdisk00t77 | ||
| lcdisk0a: | lcdisk00t78 | lcdisk00t78 | ||
| bootflash: | fs0p1 | fs0p1 | fs0p1 | |
| configflash: | fs1p1 | |||
| nvram: | nvram | nvram | ||
| Kernel dump | hd0t80 | hd0t80 or hd1t802 | fs0p2 | |
| 1. Any one | 2. Either one | |||
| Usage | ||||
| Volume | RSP2 | RSP440 | Trident | Typhoon |
| disk0: | IOS-XR Packages, Configs | IOS-XR Packages, Configs | ||
| disk0a: | sysmgr_debug | sysmgr_debug | ||
| disk1: | IOS-XR Packages (if Mirrored) | IOS-XR Packages (if Mirrored) | ||
| disk1a: | wdsysmon_debug | wdsysmon_debug | ||
| harddisk: | Crash files, logs | Crash files, logs | ||
| harddiska: | NP logs, crash files | NP logs, crash files | ||
| harddiskb: | ||||
| compactflash: | File Copy | File Copy | ||
| lcdisk0: | Kernel dump files | Kernel dump files | ||
| lcdisk0a: | ||||
| bootflash: | MBI Images | |||
| configflash: | OBFL | |||
| nvram: | Configs | Configs | ||
| Kernel dump | Raw kernel dumps | Raw kernel dumps | Raw kernel dumps | |
| Filesystems | ||||
| Volume | RSP2 | RSP440 | Trident | Typhoon |
| disk0: | QNX4 | QNX4 | ||
| disk0a: | QNX4 | QNX4 | ||
| disk1: | QNX4 | QNX4 | ||
| disk1a: | QNX4 | QNX4 | ||
| harddisk: | QNX4 | QNX4 | ||
| harddiska: | QNX4 | QNX4 | ||
| harddiskb: | QNX4 | FAT | ||
| compactflash: | FAT1 | FAT1,2 | ||
| lcdisk0: | QNX4 | QNX4 | ||
| lcdisk0a: | QNX4 | QNX4 | ||
| bootflash: | FFSv3 | FFSv3 | FFSv3 | |
| configflash: | FFSv3 | |||
| nvram: | Cisco | Cisco | ||
| Kernel dump | Raw | Raw | File | Raw |
| 1. FAT F/S only | 2. Flash Media only | |||
| Approximate Parition Size (minimum) | ||||
| Volume | RSP2 | RSP440 | Trident | Typhoon |
| disk0: | 1.6GB | 11.0GB | ||
| disk0a: | 0.4GB | 2.2GB | ||
| disk1: | 1.6GB | 11.0GB | ||
| disk1a: | 0.4GB | 2.2GB | ||
| harddisk: | 35GB | 3.1/6.2GB | ||
| harddiska: | 8GB | 0.4/0.8GB | ||
| harddiskb: | 8GB | 0.4/0.8GB | ||
| compactflash: | 1GB | 1-32GB | ||
| lcdisk0: | 1.6GB | 1.6GB | ||
| lcdisk0a: | 0.4GB | 0.4GB | ||
| bootflash: | 44MB | 56MB | 56MB | |
| configflash: | 28MB | |||
| nvram: | 220K | 500K | ||
| Kernel dump | 21GB | 500MB 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
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
generally caused by image corruption. seen that when the image is transferred to a tftp server with ascii instead of binary.
tftp download has a checksum for xferring from tftp svr to mem.
xander
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
here we are using the usb to copy the file any we have directly downloaded the file from cisco site and installed it. now tell me is their any option to recover it
thanks for your support
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
In Windows 7 you can use the "netsh" utility to determine what your MTU is set to.
Use a CMD prompt or Powershell window and use
netsh interface ipv4 show interfaces
This will display a list of your interfaces and their MTU sizes.
The TFTP blocksize should be equal to or smaller than the MSS of the interface through which you are accessing the TFTP server.
MSS(Payload for TCP = MTU - 40 Bytes (20 Byte IP Header + 20 Byte TCP header)
eg. If your MTU was 1300 use
TFTP_BLKSIZE=1260
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Xander
For ASR 9006 with RSP-4G
We have trouble with the tftp download. We are pretty sure that the server works fine (tftpd32), since we have followed the procedure and updated sucessfully one ASR9010 and two ASR 9904 with RSP440.
We usually get to a point where the transmission ends with the message tftp timeout.
Do you have any suggestions?
Thanks!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Xander,
After turboboot, the image is getting automatically copied to disk0: even when the turboboot rommon variable is set ON.
The following is given as input is rommon when turboboot:
rommon B25 > TURBOBOOT=on,disk0,format
But still after the bootup, it shows the following error:
RP/0/RSP0/CPU0:Aug 5 03:08:14.515 : easybake3[186]: %INSTALL-TURBOBOOT-4-ROMMON_VARIABLE_NOT_SET : TURBOBOOT rommon variable not set; system is membooting. Set TURBOBOOT rommon variable to 'on' to diskboot the system.!! Memboot is unsupported. Behavior could be undefined !!
Is there anything needs to be added?
Warm regards.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Disk0 is the default, and in some instances other disks can't be used at all (depending on which RP/RSP/PRP you are using).
The syslog message indicates that you likely did not 'sync' the ROMMON config before booting, so while you did boot the image you only loaded it into memory, without the TURBOBOOT variable the writing to disk step will never happen.
Sam
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
yeah that was going to be my suggestion on this also Sam.
just to explain: the "sync" keyword in rommon "saves" the vars from rommon into a file so that when rommon resets the right vars are taken back, which is necessary for turboboot to operate.
xander
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thanks Sam & xander,
It worked after 'sync'ing.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Xander/Experts
I recently performed a turboboot from 3.9.2 to 5.1.3 on ASR9010.
The router has come up fine and it seems to be functioning normally, however, the following issue is causing great concern to me:
I receive a warning from wdsysmon:
wdsysmon[428]: %HA-HA_WD-4-DISK_WARN : A monitored device /bootflash: is above 80% utilization. Current utilization = 89. Please remove unwanted user files and configuration rollback points.
The bootflash shows that it has only around 5 mb free space and 44 mb total space (???). I donot understand how that is possible.
RP/0/RSP0/CPU0:KTM-IR3#dir bootflash:
Wed Aug 12 13:06:27.960 NTP
Directory of bootflash:
5701638 drwx 108 Wed Aug 12 00:59:55 2015 disk0
6291488 -rw- 0 Wed Aug 12 01:00:45 2015 mbi_image
44695552 bytes total (5198200 bytes free)
When i check the free memory available, i find that there is 2gb free space.
RP/0/RSP0/CPU0:KTM-IR3#show watchdog memory-state
Wed Aug 12 13:10:54.929 NTP
Memory information:
Physical Memory: 4096 MB
Free Memory: 1990.656 MB
Memory State: Normal
RP/0/RSP0/CPU0:KTM-IR3#show watchdog memory-state location 0/rSP0/CPU0
Wed Aug 12 13:11:05.810 NTP
Memory information:
Physical Memory: 4096 MB
Free Memory: 1990.652 MB
Memory State: Normal
I am concerned that this might lead to issues in the future, at worst, a reload.
Are my concerns justified or is this normal behavior?
Any help would be greatly appreciated.
Thanks.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
The message with bootflash is fine. Have you committed the install and such to make sure we only keep the last committed version in there?
Thanks,
Bryan
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
ASR9006
Cisco IOS XR Software for the Cisco XR ASR9K, Version 5.2.4
Copyright (c) 2015 by Cisco Systems, Inc.
Does someone know why I get the following error? Thanks in advance.
Al ready run the following command: check fsck
RP/0/RSP0/CPU0:ios#cfs check
Wed Aug 12 20:20:10.225 UTC
Creating any missing directories in Configuration File system...OK
Initializing Configuration Version Manager...OK
Syncing commit database with running configuration...OK
and install verify packages repair
Install operation 23 '(admin) install verify packages repair' started by user
'cisco' via CLI at 19:38:04 UTC Wed Aug 12 2015.
The install operation will continue asynchronously.
RP/0/RSP0/CPU0:ios(admin)#Info: This operation can take up to 2 minutes per package being verified.
Info: Please be patient.
Info: 0/RSP0/CPU0 [RP] [SDR: Owner]
Info: meta-data: [SUCCESS] Verification Successful.
Info: /install/asr9k-optics-supp-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/asr9k-mgbl-supp-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/iosxr-mgbl-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-mcast-supp-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/iosxr-mcast-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-li-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-li-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-k9sec-supp-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/iosxr-security-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-mpls-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-fpd-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-services-infra-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/asr9k-scfclient-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/asr9k-diags-supp-5.2.4: [SUCCESS] Verification
Info: Successful.
Info: /install/asr9k-ce-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-fwding-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-base-5.2.4: [SUCCESS] Verification Successful.
Info: /install/asr9k-cpp-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-ce-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-diags-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-routing-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-fwding-5.2.4: [SUCCESS] Verification Successful.
Info: /install/iosxr-infra-5.2.4: [SUCCESS] Verification Successful.
Info: Verification Summary:
Info: 0/RSP0/CPU0: SUCCESSFUL. No anomalies found.
Info: The system needs no repair.
Info: Repair begins
Info: No need to repair: The system needs no repair.
Info: Repair ends
Install operation 23 completed successfully at 19:47:34 UTC Wed Aug 12 2015.
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 IOS XR Software for the Cisco XR ASR9K, Version 5.2.4
Copyright (c) 2015 by Cisco Systems, Inc.
Media storage device /harddiskb: corrupted beyond repair. Check fsck log at /tmp/chkfs_hd0a.log
Aug 12 19:59:21.754: Install Setup: Booting with committed software
FPD ltrace_file_name => fpd-agent/fiarsp
FPD ltrace_file_name => fpd-agent/tempo
FPD ltrace_file_name => fpd-agent/longbeach
RP/0/RSP0/CPU0:Aug 12 19:58:52.835 : mediasvr[73]: %MEDIA-MEDIASVR-4-DEVICE_CORRUPT : Media storage device /harddiskb: corrupted beyond repair. Check fsck log at /tmp/chkfs_hd0a.log
RP/0/RSP0/CPU0:Aug 12 20:00:13.273 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
RP/0/RSP0/CPU0:Aug 12 20:00:53.745 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Set|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.748 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Clear|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.748 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Set|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.748 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Clear|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.748 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Set|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.749 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Clear|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.749 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Set|hd_drv[49186]|0x100b000|Hard disk device error
RP/0/RSP0/CPU0:Aug 12 20:00:53.749 : pfm_node_rp[359]: %PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR : Clear|hd_drv[49186]|0x100b000|Hard disk device error
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Martine,
You got error messages for harddiskb: which generally is not used. but before that concern is repeatedly hang signature of HD.
Possibility of embedded USB failure is high. can you help me with output of below commands please ?
more disk0:/umass.log
more harddisk:ahci.log loc location <0/RSP0/CPU0>
show filesystem disk0: location <0/RSP0/CPU0>
Thanks
Nitin Pabbi
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello, Nitin,
Thanks for the prompt response! Thanks again for your help, Much appreciated.
I was able to fix that error by changing the config-register x102 had it set up at x2102.
But I still get two error message from booting up:
This (D)RP Node is not ready or active for login /configuration
FPD ltrace_file_name => fpd-agent/tempo
FPD ltrace_file_name => fpd-agent/fiarsp
RP/0/RSP0/CPU0:Aug 12 22:06:57.143 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
FPD ltrace_file_name => fpd-agent/longbeach
RP/0/RSP0/CPU0:Aug 12 22:08:02.035 : wdsysmon[443]: %HA-HA_WD-4-DISK_ALARM : A monitored device alarm set by /disk0:
RP/0/RSP0/CPU0:Aug 12 22:08:02.041 : wdsysmon[443]: %HA-HA_WD-4-DISK_WARN : A monitored device /disk0: is above 80% utilization. Current utilization = 87. Please remove unwanted user files and configuration rollback points.
Which Files do I need to delete?
RP/0/RSP0/CPU0:ios#dir disk0:
Wed Aug 12 22:14:50.558 UTC
Directory of disk0:
6298 -r-- 401404 Wed Aug 12 16:39:26 2015 .bitmap
17 -r-- 614400 Wed Aug 12 16:39:26 2015 .inodes
18 -rw- 0 Wed Aug 12 16:39:26 2015 .boot
19 -rw- 0 Wed Aug 12 16:39:26 2015 .altboot
6303 drwx 4096 Wed Aug 12 16:39:31 2015 LOST.DIR
6304 -r-- 32768 Wed Aug 12 16:39:26 2015 .longfilenames
6305 drwx 4096 Wed Aug 12 16:55:37 2015 config
6306 drwx 4096 Wed Aug 12 16:39:56 2015 eem_rdsfs
6362 drwx 4096 Wed Aug 12 16:40:07 2015 asr9k-scfclient-5.2.4
6308 drwx 4096 Wed Aug 12 22:07:58 2015 instdb
6368 drwx 4096 Wed Aug 12 16:40:08 2015 asr9k-diags-supp-5.2.4
6380 drwx 4096 Wed Aug 12 16:40:09 2015 asr9k-ce-5.2.4
6415 drwx 4096 Wed Aug 12 16:41:25 2015 asr9k-fwding-5.2.4
577088 drwx 4096 Wed Aug 12 16:42:58 2015 asr9k-base-5.2.4
1187393 drwx 4096 Wed Aug 12 16:43:13 2015 asr9k-os-mbi-5.2.4
1187402 drwx 4096 Wed Aug 12 16:43:30 2015 asr9k-cpp-5.2.4
2097658 drwx 4096 Wed Aug 12 16:43:38 2015 iosxr-ce-5.2.4
2266010 drwx 4096 Wed Aug 12 16:43:39 2015 iosxr-diags-5.2.4
2266033 drwx 4096 Wed Aug 12 16:43:58 2015 iosxr-routing-5.2.4
2378172 drwx 4096 Wed Aug 12 16:45:56 2015 iosxr-fwding-5.2.4
3309657 drwx 4096 Wed Aug 12 16:47:53 2015 iosxr-infra-5.2.4
4288749 drwx 4096 Wed Aug 12 16:47:55 2015 asr9k-mini-px-5.2.4
6321 -rw- 18728 Wed Aug 12 16:47:56 2015 sam_certdb
6322 -rw- 126 Wed Aug 12 16:47:56 2015 sam_crldb
6323 drwx 4096 Wed Aug 12 16:54:21 2015 aaa
6324 drwx 4096 Wed Aug 12 16:54:25 2015 onepk_cli_rdsfs
6325 drwx 4096 Wed Aug 12 16:54:49 2015 sla
6326 drwx 4096 Wed Aug 12 16:54:59 2015 license
6327 drwx 4096 Wed Aug 12 16:55:38 2015 snmp
6328 drwx 4096 Wed Aug 12 16:56:27 2015 sm_rdsfs
6329 drwx 4096 Wed Aug 12 16:56:26 2015 var
6330 drwx 4096 Wed Aug 12 16:56:27 2015 virtual-instance
4288793 drwx 4096 Wed Aug 12 18:16:44 2015 asr9k-asr901-supp-5.2.4
4288802 drwx 4096 Wed Aug 12 18:16:45 2015 asr9k-asr901-nV-px-5.2.4
4288809 drwx 4096 Wed Aug 12 18:16:59 2015 iosxr-bng-5.2.4
5061677 drwx 4096 Wed Aug 12 18:17:00 2015 asr9k-bng-5.2.4
5061692 drwx 4096 Wed Aug 12 18:17:01 2015 asr9k-bng-px-5.2.4
5061698 drwx 4096 Wed Aug 12 18:17:05 2015 iosxr-li-5.2.4
5061715 drwx 4096 Wed Aug 12 18:17:07 2015 asr9k-li-5.2.4
5061722 drwx 4096 Wed Aug 12 18:17:08 2015 asr9k-li-px-5.2.4
5061728 drwx 4096 Wed Aug 12 18:17:15 2015 iosxr-service-5.2.4
5116251 drwx 4096 Wed Aug 12 18:17:18 2015 asr9k-service-supp-5.2.4
5116306 drwx 4096 Wed Aug 12 18:17:19 2015 asr9k-services-px-5.2.4
5116314 drwx 4096 Wed Aug 12 18:17:26 2015 asr9K-doc-supp-5.2.4
5116400 drwx 4096 Wed Aug 12 18:17:27 2015 asr9k-doc-px-5.2.4
5116406 drwx 4096 Wed Aug 12 18:17:40 2015 iosxr-mpls-5.2.4
5234193 drwx 4096 Wed Aug 12 18:17:42 2015 asr9k-mpls-px-5.2.4
5234198 drwx 4096 Wed Aug 12 18:21:38 2015 asr9k-services-infra-5.2.4
5234206 drwx 4096 Wed Aug 12 18:22:07 2015 asr9k-optics-supp-5.2.4
5234209 drwx 4096 Wed Aug 12 18:22:09 2015 asr9k-optic-px-5.2.4
5234215 drwx 4096 Wed Aug 12 18:22:24 2015 asr9k-9000v-nV-supp-5.2.4
5234226 drwx 4096 Wed Aug 12 18:22:27 2015 asr9k-9000v-nV-px-5.2.4
5234232 drwx 4096 Wed Aug 12 18:22:33 2015 iosxr-adv-video-5.2.4
5234295 drwx 4096 Wed Aug 12 18:22:35 2015 asr9k-adv-video-supp-5.2.4
5234310 drwx 4096 Wed Aug 12 18:22:37 2015 asr9k-video-px-5.2.4
5234318 drwx 4096 Wed Aug 12 18:24:49 2015 asr9k-fpd-5.2.4
13401925 drwx 4096 Wed Aug 12 18:24:52 2015 asr9k-fpd-px-5.2.4
13401930 drwx 4096 Wed Aug 12 18:25:43 2015 iosxr-mcast-5.2.4
17628725 drwx 4096 Wed Aug 12 18:25:46 2015 asr9k-mcast-supp-5.2.4
17628753 drwx 4096 Wed Aug 12 18:25:48 2015 asr9k-mcast-px-5.2.4
17628761 drwx 4096 Wed Aug 12 18:25:59 2015 iosxr-mgbl-5.2.4
18308625 drwx 4096 Wed Aug 12 18:26:03 2015 asr9k-mgbl-supp-5.2.4
18308634 drwx 4096 Wed Aug 12 18:26:06 2015 asr9k-mgbl-px-5.2.4
18308641 drwx 4096 Wed Aug 12 18:27:58 2015 asr9k-asr903-supp-5.2.4
18308647 drwx 4096 Wed Aug 12 18:28:00 2015 asr9k-asr903-nV-px-5.2.4
18308653 drwx 4096 Wed Aug 12 18:28:21 2015 iosxr-security-5.2.4
22163944 drwx 4096 Wed Aug 12 18:28:25 2015 asr9k-k9sec-supp-5.2.4
22163952 drwx 4096 Wed Aug 12 18:28:27 2015 asr9k-k9sec-px-5.2.4
1644150784 bytes total (222057472 bytes free)
RP/0/RSP0/CPU0:ios#
____________________________
Show version:
Cisco IOS XR Software, Version 5.2.4[Default]
Copyright (c) 2015 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 1.06(20120210:003513) [ASR9K ROMMON],
ios uptime is 4 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-5.2.4/0x100000/mbiasr9k-rp.vm"
cisco ASR9K Series (MPC8641D) processor with 4194304K bytes of memory.
MPC8641D processor at 1333MHz, Revision 2.2
ASR 9006 DC Chassis with PEM Version 2
2 Management Ethernet
219k bytes of non-volatile configuration memory.
977M bytes of compact flash card.
33994M bytes of hard disk.
1605616k bytes of disk0: (Sector size 512 bytes).
1605616k bytes of disk1: (Sector size 512 bytes).
Configuration register on node 0/RSP0/CPU0 is 0x102
Boot device on node 0/RSP0/CPU0 is disk0:
Package active on node 0/RSP0/CPU0:
asr9k-fpd, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-fpd-5.2.4
Built on Tue Apr 28 15:19:18 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-fpd-px, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-fpd-px-5.2.4
Built on Tue Apr 28 15:19:46 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-mpls, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-mpls-5.2.4
Built on Tue Apr 28 14:02:31 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-mpls-px, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-mpls-px-5.2.4
Built on Tue Apr 28 14:02:49 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-infra, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-infra-5.2.4
Built on Tue Apr 28 13:55:42 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-fwding, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-fwding-5.2.4
Built on Tue Apr 28 13:55:42 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-routing, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-routing-5.2.4
Built on Tue Apr 28 13:55:44 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-diags, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-diags-5.2.4
Built on Tue Apr 28 13:55:45 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
iosxr-ce, V 5.2.4[Default], Cisco Systems, at disk0:iosxr-ce-5.2.4
Built on Tue Apr 28 13:55:46 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-cpp, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-cpp-5.2.4
Built on Tue Apr 28 13:55:46 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-os-mbi, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-os-mbi-5.2.4
Built on Tue Apr 28 13:58:02 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-base, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-base-5.2.4
Built on Tue Apr 28 13:55:49 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-fwding, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-fwding-5.2.4
Built on Tue Apr 28 13:56:11 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-ce, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-ce-5.2.4
Built on Tue Apr 28 13:56:11 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-diags-supp, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-diags-supp-5.2.4
Built on Tue Apr 28 13:56:14 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-scfclient, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-scfclient-5.2.4
Built on Tue Apr 28 13:56:15 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
asr9k-mini-px, V 5.2.4[Default], Cisco Systems, at disk0:asr9k-mini-px-5.2.4
Built on Tue Apr 28 14:00:33 UTC 2015
By iox-lnx-010 in /auto/srcarchive13/production/5.2.4/all/workspace for pie
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Martine,
There are few points :-
1) Seems you have turboboot the box because confreg 0x102 set by default after it.
2) Its good if messages are not appearing after changing confreg but that confreg is for bootup operations.
3) If its not again appearing the possible reason is clearing of error condition. If you find same logs again and repetitive then should investigate ahci.log and umass.log file.
4) Error message :- RP/0/RSP0/CPU0:Aug 12 22:06:57.143 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
Indicates that central_services is not included or part of process group of Route-Proxy process.
can you share
RP/0/RSP0/CPU0:ios# run
cat /pkg/startup/route_proxy.startup
It don't look having potential to impact any service.
5) Seems you are using RSP2. you can check sh install summary and if you are not using specific packages i.e. service infra, LI, doc etc. You have ~ quarter to 2GB for operations.
Thanks
Nitin Pabbi
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello Nitin,
Thanks for the reply.
1) Its good if messages are not appearing after changing confreg but that confreg is for bootup operations.Should I have it set to something else? what would be the default config?
2) I would like to remove unnecessary files so the following error will not appear: What commands do I need to execute and what files I can delete?
A monitored device /disk0: is above 80% utilization. Current utilization = 87. Please remove unwanted user files and configuration rollback points. wdsysmon[441
3.Error message :- RP/0/RSP0/CPU0:Aug 12 22:06:57.143 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
I was not able to execute: P/0/RSP0/CPU0:ios# run
cat /pkg/startup/route_proxy.startup
after reload I still the this message:
RP/0/RSP0/CPU0:Aug 13 15:41:29.500 : wdsysmon[441]: %HA-HA_WD-4-DISK_ALARM : A monitored device alarm set by /disk0:
RP/0/RSP0/CPU0:Aug 13 15:41:29.502 : wdsysmon[441]: %HA-HA_WD-4-DISK_WARN : A monitored device /disk0: is above 80% utilization. Current utilization = 87. Please remove unwanted user files and configuration rollback points.
RP/0/RSP0/CPU0:Aug 13 15:40:24.979 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
RP/0/RSP1/CPU0:Aug 13 15:40:20.653 : sysmgr[97]: %OS-SYSMGR-3-ERROR : /pkg/startup/route_proxy.startup: No proc_group name set in placeable startup file - default to central-services
RP/0/RSP1/CPU0:Aug 13 15:41:25.164 : wdsysmon[441]: %HA-HA_WD-4-DISK_ALARM : A monitored device alarm set by /disk0:
RP/0/RSP1/CPU0:Aug 13 15:41:25.168 : wdsysmon[441]: %HA-HA_WD-4-DISK_WARN : A monitored device /disk0: is above 80% utilization. Current utilization = 87. Please remove unwanted user files and configuration rollback points.
RP/0/RSP0/CPU0:ios#sh install summary
Thu Aug 13 15:45:05.294 UTC
Default Profile:
SDRs:
Owner
Active Packages:
disk0:asr9k-mini-px-5.2.4
disk0:asr9k-services-infra-5.2.4
disk0:asr9k-services-px-5.2.4
disk0:asr9k-fpd-px-5.2.4
Inactive Packages:
disk0:asr9k-asr901-nV-px-5.2.4
disk0:asr9k-bng-px-5.2.4
disk0:asr9k-li-px-5.2.4
disk0:asr9k-doc-px-5.2.4
disk0:asr9k-mpls-px-5.2.4
disk0:asr9k-optic-px-5.2.4
disk0:asr9k-9000v-nV-px-5.2.4
disk0:asr9k-video-px-5.2.4
disk0:asr9k-mcast-px-5.2.4
disk0:asr9k-mgbl-px-5.2.4
disk0:asr9k-asr903-nV-px-5.2.4
disk0:asr9k-k9sec-px-5.2.4
Committed Packages:
disk0:asr9k-mini-px-5.2.4
disk0:asr9k-services-infra-5.2.4
disk0:asr9k-services-px-5.2.4
disk0:asr9k-fpd-px-5.2.4
Superceded Packages:
No packages.
RP/0/RSP0/CPU0:ios#
Best Regards,
Martine
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: