IOS XR lost configuration on reload

[andrewmcca]

Following a reload, a ASR 9001 boots up it has lost all of its config and gives the error below:

cfgmgr-rp[160]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Configuration Namespace Version History module. Error: 'Result too large'.

This reappears every minute, I've tried all combinations of "clear configuration" EXEC command without luck.  I've also tried everything else I could think of to resolve the error, but I'm unable to do anything with the router.  When I try and configure it it gives an error saying:

SYSTEM CONFIGURATION IS STILL IN PROGRESS

And I'm unable to commit any config.  Has anyone come across this before?  Its running IOS XR 4.2.3.

Thanks in advance for your help

[smailmilak]

It's an ACL

ipv4 access-list XXX
no 10 deny tcp any 31.176.240.0 0.0.15.255 eq smtp
no 15 deny tcp any 31.176.240.0 0.0.15.255 eq 587
no 20 deny tcp any 37.203.120.0 0.0.3.255 eq smtp
no 25 deny tcp any 37.203.120.0 0.0.3.255 eq 587
no 30 deny tcp any 92.36.208.0 0.0.15.255 eq smtp
no 35 deny tcp any 92.36.208.0 0.0.15.255 eq 587
no 40 deny tcp any 109.175.40.0 0.0.7.255 eq smtp
no 45 deny tcp any 109.175.40.0 0.0.7.255 eq 587
no 50 deny tcp any 109.175.48.0 0.0.15.255 eq smtp
no 55 deny tcp any 109.175.48.0 0.0.15.255 eq 587
no 60 deny tcp any 109.175.64.0 0.0.31.255 eq smtp
no 65 deny tcp any 109.175.64.0 0.0.31.255 eq 587
no 70 permit ipv4 any any

[smailmilak]

Hi,

upgrade from 5.1.3. to 5.3.3 + SP2 went fine this morning. VRF config was not lost this time.

Configuration on both RSP is now consistent.

sh configuration inconsistency replica location 0/RSP1/CPU0
Thu Jul 7 12:45:28.101 GMT
Replica is consistent

show configuration failed startup
Thu Jul 7 12:43:50.592 GMT
!!03:34:28 UTC Thu Jul 07 2016

After reload I saw this message about filesystem that was repaired. Not sure if this was the issue where the config was inconsistent on standby RSP before the upgrade.

RP/0/RSP1/CPU0:Jul 7 05:31:49.457 : mediasvr[70]: %MEDIA-MEDIASVR-5-DEVICE_REPAIRED : Media storage device /disk0: was repaired. Check fsck log at /dev/disk0:/chkfs_repair.log
RP/0/RSP1/CPU0:Jul 7 05:31:49.496 : mediasvr[70]: %MEDIA-MEDIASVR-5-DEVICE_REPAIRED : Media storage device /disk1: was repaired. Check fsck log at /dev/disk1:/chkfs_repair.log

[Aleksandar Vidakovic]

hi Smail,

happy to hear that the upgrade went well!

%MEDIA-MEDIASVR-5-DEVICE_REPAIRED message indicates that there was a file system corruption. The repair log should have more information. The file system corruption is a SW issue. There were several related fixes between 5.1.3 and 5.3.3 SP2. If the corruption happens again on 5.3.3+SP2, we should analyse it.

/Aleksandar