v5.1 hangs in /export

Hi,

I have two routerboard. RB433AH and RG450G. Both hangs when I issue the /export or /interface export command:

[admin@RB433AH] > /interface export                                                                                                            
# jan/02/1970 07:36:19 by RouterOS 5.1
# software id = XXXX-XXXX
#
/interface ethernet
set 0 arp=enabled auto-negotiation=yes disabled=no full-duplex=yes l2mtu=1526 mac-address=00:0C:42:2F:8A:8F mtu=1500 name=ether1 speed=\       
    100Mbps                                                                                                                                    
set 1 arp=enabled auto-negotiation=yes bandwidth=unlimited/unlimited disabled=yes full-duplex=yes l2mtu=1522 mac-address=00:0C:42:2F:8A:90 \
    master-port=none mtu=1500 name=ether2 speed=100Mbps                                                                                        
set 2 arp=enabled auto-negotiation=yes bandwidth=unlimited/unlimited disabled=yes full-duplex=yes l2mtu=1522 mac-address=00:0C:42:2F:8A:91 \
    master-port=none mtu=1500 name=ether3 speed=100Mbps                                                                                        
/interface bridge
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes disabled=no forward-delay=15s l2mtu=1526 max-message-age=20s mtu=\     
    1500 name=bridge priority=0x8000 protocol-mode=none transmit-hold-count=6                                                                  
/interface ethernet switch
...hang...

Then I can’t login to the routerboard with any method:

$ telnet 192.168.5.2
Trying 192.168.5.2...
Connected to 192.168.5.2.
Escape character is '^]'.

MikroTik v5.1
Login: admin
Password: 








  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 5.1 (c) 1999-2011       http://www.mikrotik.com/

...hang...

What happens?

Confirmed on my RB433AH
Console process eats up to 100% CPU and make router unresponsible to telnet and SSH.
Only reboot via Winbox helps in this case.

Regards,

For support from Mikrotik staff, write to support@mikrotik.com - Mikrotik does not generally offer support on the forum, this is a user forum.

Please, send us report with your configuration support output file.
I have tried export on my RB433, it works fine for me. So there is specific configuration, which does not work properly on export.

please send supout.rif files to support.

I started creation of ‘supout.rif’ 30 minutes ago and I’m still waiting for finish.
How long this process could be?

Regards,

do it from telnet

It’s ready, after 40 minutes :slight_smile:

Regards,

I did it from telnet on my RouterBOARD 433.
Both commands worked without any problems.

export
system sup-output

Maybe this is a relation between these two problems.
During creation of ‘supout.rif’ file and after finish, ‘console’ process was 99-100%.
There was need to restart router.

Regards,

ditonet, yes you are correct.
We need to find out, which piece of configuration causes the particular problem.

I have the same issue (RB450G), should I also send in the supout.rif?

I started the sup-output process for 2 hours. I hope it will finish till I should go to work…

It’s still running…

I can’t generate supout.rif but I will try again today…

Not sure if it is related, but RB1100’s spike to 100% when generating a supout.rif and do not appear to go down
damnbug.jpg

oreggin and nz_monkey, please contact support with support output file from the router.

Ok, I will send e-mail to support soon.

My 450g also got this problems, support.rif sent.

I can’t generate supout.rif :frowning:
I was tried over SSH and serial console…

Thank you very much for your reports.
We found the problem and working on the fix. It will be fixed in the next RouterOS version.