How_to_Use_Ant-20

Fix the ‘missing slave cfcard’ in the Slave MPU Board of an NE-40E router Phenomenon Description: The cfcard of the slave MPU Board of an NE-40E router is disappearing from the VRP OS although the Slave MPU board is functioning perfectly. Defects of this problem: 1.If there is a hardware failure of Master Board and power reboot of the chassis, the router cannot recover because it cannot read the VRP OS and configuration files of the router, hence causing network down for a significant of time. 2.Performing Software upgrade of Router in a redundant (Master and Slave) MPU board situation is not possible. The cfcard must be seen in both Master and Slave MPU board, and the same copies of VRP OS, patch ,and configuration files must always exist in both board at the same time. Details When performing the command of dir slave#cfcard: , an error messages appeared, dir slave#cfcard: Error: The device is invalid. "slave#cfcard:" although under the ‘display health’ , ‘display device’ and ‘display version’ commands, the MPU slave board looks functioning well. 1. display health Slot CPU Usage Memory Usage(Used/Total) ---------------------------------------------------- 9 MPU(Master) 12% 52% 993MB/1901MB 2 LPU 5% 46% 189MB/405MB 3 LPU 7% 44% 407MB/917MB 5 SPU 4% 27% 253MB/917MB 7 LPU 5% 46% 190MB/405MB 8 LPU 5% 46% 190MB/405MB 10 MPU(Slave) 4% 11% 225MB/1901MB 2. display version …. …. MPU 10(Slave) : uptime is 400 days, 1 hour, 12 minutes StartupTime 2009/06/29 12:49:29 SDRAM Memory Size : 2048M bytes Flash Memory Size : 32M bytes NVRAM Memory Size : 512K bytes CF Card1 Memory Size: 487M bytes CF Card2 Memory Size: 489M bytes MPU version information: 1. PCB Version : CR52SRUA REV C 2. EPLD1 Version : 106 3. EPLD2 Version : 108 4. FPGA Version : 009 5. BootROM Version : 74.0 6. BootLoad Version : 216.0 7. Software Version : Version 5.50 RELEASE 0041 MIF version information: 1. PCB Version : CR52MIFB REV C 2. FPGA Version : 009 MonitorBUS version information: 1. PCB Version : CR31MBSA REV A 2. EPLD Version : 019 3. Software Version : 3.8 3. ===============display device==================== ================================================== NE40E's Device status: Slot # Type Online Register Status Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2 LPU Present Registered Normal NA 3 LPU Present Registered Normal NA 5 SPU Present Registered Normal NA 7 LPU Present Registered Normal NA 8 LPU Present Registered Normal NA 9 MPU Present NA Normal Master 10 MPU Present Registered Normal Slave 11 SFU Present Registered Normal NA 12 SFU Present Registered Normal NA 13 SFU Present Registered Normal NA 14 SFU Present Registered Normal NA 15 CLK Present Registered Normal Master 16 CLK Present Registered Normal Slave 17 PWR Present NA Normal NA 18 PWR Present NA Normal NA 19 FAN Present Registered Normal NA Troubleshooting plan: 1. Unplug the Slave MPU Board from the chassis of NE-40E router. 2. Wait for 5 minutes. Ensure everything is normal during the 5 minutes time. 3. Insert the Slave MPU Board back to the chassis again. 4. If the file information appears after entering the ‘dir slave#cfcard:’ command, dir slave#cfcard: Directory of slave#cfcard:/ Idx Attr Size(Byte) Date Time(LMT) FileName 0 -rw- 160,102,672 Jan 22 2009 10:42:36 v300r003c02b382.cc 1 -rw- 13,995 Dec 10 2009 13:40:00 license.txt 2 -rw- 72,583 Dec 10 2009 13:38:40 paf.txt 3 -rw- 396 Aug 25 2008 15:12:56 patchnpstate.dat 4 -rw- 16,267 Jun 16 2008 16:03:44 paf.txt.bak 5 -rw- 525,065 Dec 10 2009 17:00:16 private-data.txt 6 -rw- 1,653 Sep 14 2010 07:29:42 vrpcfg.zip 7 -rw- 65,572 Aug 25 2008 11:42:52 paf20080825.txt 8 -rw- 12,757 Aug 25 2008 11:43:12 license20080825.txt 9 -rw- 2,304 Feb 19 2010 00:03:42 $_patchstate_a 10 -rw- 196 Dec 10 2009 16:25:04 picdrvcfg.ini 11 -rw- 632 Aug 25 2008 12:37:36 $_patchstate_a.backup 12 -rw- 66,301 Jan 22 2009 10:46:30 paf20090122.txt 13 -rw- 12,996 Jan 22 2009 10:46:38 license20090122.txt 14 -rw- 214,717,888 Dec 10 2009 13:18:28 ne40e80ev300r006c01spc003.cc 15 -rw- 396 Dec 10 2009 17:43:56 rsahostkey.dat 16 -rw- 540 Dec 10 2009 17:43:56 rsaserverkey.dat 17 -rw- 1,071,416 Feb 19 2010 00:02:44 v3r6c01sph007.pat 498,680 KB total (130,688 KB free) Then, the cfcard has become normal again. 5. If the cfcard still does not appear in the slave MPU board, then get ready to replace the Slave MPU Board with a new Slave MPU, due to this cfcard internal hardware failure in the board. Lessons Learned: It’s worth try out unplugging the MPU board from the chassis and then plug it back to the main chassis (after a period of time) to see if problem can be resolved, before we doing a replacement of the entire MPU board.