eNSP 1.0.210 stability

hi~ wo have test the OSPF on AR and LSW, and it worked well, the loopback IP advertised with network statement.

Could you tell me the OSPF scene you have tested ?

About the eNSP crashed:

I think that the memory may be not enough,  you can check it when the device start up.

When the eNSP crashed, you can use the keyboard of Esc to stop it, then you can continue do

some other operation.

There is a memory clean tool, and you can use it clean the memory when start many device of eNSP.

You can get the tool here, thank you ~~

Please, see my post here:

http://forum.huawei.com/enterprise/thread-221977.html

I will try it, many thanks.

-->about the lab: the OSPF is working without problems. Generally BGP  works  without "BGP Problems", as well. But if I activate and configure BGP, then the eNSP seems to crash when I want to close or save the scenario. 

When I killed the process with taskmanager (by the way, my computer has 8GB mem) and reloaded the lab, all BGP configuration had been lost.

When the eNSP hung (crasched) I could not use the ESC Key to cancel any action.

I have seen that if I closed all vrp consoles first, stopped then device by device, then I could close the eNSP without problems.

About the memory tool:
Question: When should I use the tool ? Just before I startup the eNSP, or when a problem is coming  up? Is there an explanation in english avaliable? Please, take into account that we cannot use any software in our enterprise network I we do not know what the tool does (security policy).

Again: Language
The Memory tool comes with chineese menues. We can not use or promote this. Please, you should very strictly design your software in and international language.

Best regards

Klaus Dieter Wolfinger

www.itconsulting-wolfinger.de

hi~~We are ***yzing this problem, wo will notify you if there is any progress ~~

thanks~~

hi~~ I'm sorry about that it is not work well.

About the crashed: The reason is that some logfile is  too big and we application memory is not enough.We fixed it in next version.

And now you can avoid the crash by this method:

1. find the big logfile, I have found the big logfile device:

AR13、AR1、AR8、AR7、AR10、AR9、AR3、AR2

2. delete the logfile. like this:

Ag： AR13

<R1_10_AS17000>dir /all
Directory of flash:/

  Idx  Attr     Size(Byte)  Date        Time       FileName
    0  drw-              -  Dec 07 2012 10:03:34   src
    1  drw-              -  Dec 07 2012 10:03:36   logfile
    2  drw-              -  Dec 07 2012 10:03:39   pmdata
    3  -rw-              4  Dec 07 2012 10:03:41   snmpnotilog.txt
    4  drw-              -  Dec 07 2012 10:03:45   dhcp
    5  -rw-            603  Dec 12 2012 11:42:19   private-data.txt
    6  drw-              -  Dec 07 2012 10:18:51   mplstpoam
    7  -rw-            522  Dec 07 2012 11:34:49   vrpcfg.zip
    8  drw-              -  Dec 11 2012 21:24:37   lam

32,004 KB total (31,092 KB free)

<R1_10_AS17000>

<R1_10_AS17000>dir

Directory of flash:/logfile/

  Idx  Attr     Size(Byte)  Date        Time       FileName
    0  -rw-        917,188  Dec 11 2012 20:58:41   log.dblg

32,004 KB total (31,092 KB free)

<R1_10_AS17000>

And By the way, About the memory tool:

This software is not our development, it just a memory clean tools .

The problem will be resolve by the way that delete the big logfile~~

hi~ This is the topo file that I have deleted the big logfile~~

Thank you for posting this information!)
192.168.1.1